UAS and Wildfire Airspace Situations
Updated as of 9/20/15
The following are short capsule briefings intended for the FAA of current
UAS Wildfire Airspace situations in 2014 and 2015. Information has been
gathered from our SAFECOM system, personal interviews and news
report. Questions may be directed to Julie J. Stewart – BLM (Bureau of
Land Management) and USFS (US Forest Service) National Airspace
Program Manager at 503-780-0097 or at j5stewar@blm.gov. It is my
intention that this master list will be updated when necessary with updates.
SAFECOMs may be seen on the “public” side of our SAFECOM system.
2015
3/28/15 Minnesota Department of Forestry. Local Fire chief used personal UAS at
wildfire with no Emergency COA or coordination with DOF.
Update from the Minnesota DNR Wildfire Aviation Supervisor: FSDO said that they were
aware that the local Fire Chief was operating a UAS without a COA and they were going to talk
to him. That was about it, other than they understood my concerns and forwarded me
information that I included in our briefing info.
4/12/15 BIA. Colorado: SAFECOM 15-0166 During initial attack of the 213 Fire south of
Durango, CO a hobbyist flew his camera-equipped drone over the fire and gave the video to the
local fire department. There was no COA or coordination with BIA. There was no TFR in place
6/22/15 CalFire CALIFORNIA Corrine Fire (FCC-119 on file) Unmanned aircraft spotted at
1800 over Division M on the Corrine Fire where two fire helicopters were flying. UAS was flying
over a residential property 40-80 feet. Person stated they were a commercial independent film
company and that they lived at the residence. They were “advised and cooperated, action
discontinued.” TFR was in effect over the fire and notifications were made.
6/24/15 California: Lake Fire. SAFECOMs 15-0339 and 15-0327. Air Attack was performing a
transition (outgoing Air Attack transitions to an incoming Air Attack) at 1745 Pacific. Two close
encounters with a UAS that grounded firefighting aircraft and hampered progress against the
fire. The UAS was first spotted flying between two firefighting aircraft. Operator was not
located; the drone flew under the Air Attack between the Air Attack and Lead Plane. A second
drone was spotted 500’ below the outgoing Air Attack. Air Attack performed an evasive
maneuver. The drone then descended to the east. The Airtankers were shut down for 2.5
hours. The helicopters remained working. Additional Law Enforcement was ordered to patrol
the area. There was no TFR in place at the time however a TFR was logged into our Resource
Ordering Status System (ROSS) as filled at 2151 PST.
For additions to this document, please contact Julie Stewart (National Airspace Program Manager) at
j5stewar@blm.gov or 503-780-0097.
6/25/15 USFS California: The Sterling Fire: SAFECOM 15-0340. At 1851 Pacific Air Attack
was working 60 acre fire. Airtanker was on final when Operations notified Air Attack that there
was a drone over the fire at 1910 local. The Airtanker was instructed to “go around” and all
aircraft were instructed to fly to the west. A dedicated spotter was assigned to the drone. When
it was out of the immediate area, the Helicopters were brought back to work the fire. It was
thought that Law Enforcement located the operator but the Forest Aviation Officer confirmed it
was not the UAS operator in question. UAS operator was not found. (Actual time of TFR
issuance by the FAA is unconfirmed but it was recorded into our Resource Ordering Status
System (ROSS) as filled at 1936 local.)
6/29/15 BLM California SAFECOM 15-0357 Fire Reconnaissance flight on the Lassen National
Forest had a near md air collision with an UAS. The Recon Ship was flying in a southerly
direction when both the pilot and observer noticed what appeared to them to be a UAV
approximately 200 feet off their left wing at the same altitude {5500 Ft. MSL, 1500 Ft. AGL.}
Law Enforcement and Dispatch notified. UAS Operator not found. Note from Julie – this was a
Recon flight. There was a Lightning complex of wildfires on the neighboring forest but it did not
have a TFR.
Update from the USFS California Aviation Safety Officer: No UAS Operators were located.
7/11/15 BLM Washington SAFECOM 15-0425. UAV was observed flying within TFR by Air
Attack at the end of the shift. Air Attack established orbit above UAV when the operator landed
the UAV. Air Attack then orbited the operator’s vehicle and followed the vehicle. Operator was
not apprehended though a local production company posted a video of the wildfire the next day.
7/12/15 California Mill 2 fire: SAFECOM 15-0457 (Update from original list) UAS spotted flying
over fire delaying take off clearance for firefighting aircraft. Structures were threatened. 8
wildfire aircraft were grounded for 30 minutes at San Bernardino Air Tanker Base causing the
fire to grow rapidly and threaten structures. Law Enforcement made contact with the drone
operator but was not able to detain him. The drone operator was upset, and maintained he was
within rights to be there with his aircraft. The Sheriff’s office, Highway Patrol and Local FS Law
Enforcement were thought to have talked to the suspect. It is unknown at this time as to the
outcome regarding citations. There was no TFR in place.
Update from the USFS California Aviation Safety Officer: “In spite of the rumor mill and
misinformation reported, no UAS Operators that caused the delay of aerial suppression efforts were
located. “
7/15/15 BLM Utah: SAFECOM 15-0448 Air Attack responding to fire within R-6407 under
Clover Control when they experienced a Near Mid Air Collision with an UAS. Clover Control
was notified and is investigating the incident. There were no known UAS flights scheduled
within their airspace. There was no TFR involved.
Update from the BLM State Aviation Officer: “I talked with Cecelia Nackowski from Clover
Control today and they have nothing new. The Air Force Office of Special Investigations is
investigating now though. Cecilia will call me when OSI gets done with their investigation”
For additions to this document, please contact Julie Stewart (National Airspace Program Manager) at
j5stewar@blm.gov or 503-780-0097.
7/16/15 USFS California: SAFECOM 15-0453: Wildfire helicopter came into Placerville airport
for fuel and landed at heliport at 17:30. They noticed three men standing outside a hangar
flying a drone over 15 small parked fix wing on the ramp. As they taxied to the fuel island, the
drone approached them and they had to gain altitude to avoid it. The helicopter rose to 50 feet
and the drone flew underneath them. After refueling, the helicopter manager approached the
three men at the hanger. They had packed the drone away. They said they were pilots. This
SAFECOM is going to be processed by the US Forest Service as an Incident with Potential.
Reno FSDO and Riverside FSDO have been notified. This situation did not require a TFR.
Update from the USFS California Regional Aviation Safety Officer: “The only time anything was
reported to the FSDO was the event that took place at Placerville Airport, as we knew who the
UAS operators were. Both Reno and Sacramento FSDO (FAA Scott Harris) have been
excellent in response. All the other events, in spite of the rumor mill and misinformation
reported, no UAS Operator that caused the delay of aerial suppression efforts were located.”
Note – USFS Regional Aviation Safety Officer is meeting with FAA Sacramento FSDO Security
Specialist Scott Harris on July 27th.
7/17/15 USFS and CalFire Unified Command CALIFORNA: SAFECOM 15-0458. The “North”
Wildfire in El Cajon pass shut down I-15 northbound and southbound lanes with 20 vehicles on
fire and structures threatened. Air Attack arrived at 1500 local and reported drone activity.
FIVE drones were reported over the fire. Fire aircraft were removed from the area and left in
orbit. Helicopter carefully approached the drone operators on a Forest Service Road and three
of the drones crashed due to rotor wash. Forest Service Law Enforcement was informed. Two
additional drones were spotted pursuing our Lead Plane. When the airspace cleared of drones,
our firefighting aircraft returned after a delay of 20 minutes. This was during Initial Attack.
There was no TFR in place at the time however a TFR went into effect later at 1811 Pacific. LA
ARTCC was notified. Riverside FSDO has also been notified.
Update from the USFS California Aviation Safety Officer: “All the other events, in spite of the
rumor mill and misinformation reported, no UAS Operators that caused the delay of aerial
suppression efforts were located.”
7/22/15 CalFire CALIFORNIA (FCC-119 has been filed) Baxter Fire. Air Attack responded at
1925 local and was notified by Grass Valley Emergency Command Center that there was a
drone flying over the Baxter fire. The Air Tanker was told to return to base. Three additional
airtankers at Grass Valley Air Attack Base were instructed to hold because of the drone hazard.
Two helicopters on site remained operational with reduced speed, use of caution and remained
to support ongoing fire suppression efforts. Air Attack remained and continued supervision of
helicopters. Law Enforcement responded. The drone was never actually witnessed by any of
the fire aviation personnel. At the time of the drone report, structures were threatened and
evacuations were in effect.
7/27/15 US Forest Service WASHINGTON (SAFECOM 15-0513) While conducting a forest
flight survey over the Gifford Pinchot National Forest, in the vicinity of the Indian Heaven
Wilderness, the right side observer saw a quad copter UAS fly past the aircraft, within 200’. .
The survey aircraft was flying at approximately 7000’ msl, which was about 1500-2000 ft AGL.
For additions to this document, please contact Julie Stewart (National Airspace Program Manager) at
j5stewar@blm.gov or 503-780-0097.
The pilot did not notice any traffic on the TCAS, so the UAS did not have a transponder. There
wasn’t any fire activity in the area and it is unclear what the UAS was doing. We decided to
continue with the survey. (No TFR as this was not a fire flight.)
8/9/15 CalFire CALIFORNIA (FC-119) 3 miles SW of Calistoga, CA. Airtanker (DC-7) departed
the air attack base at Sonoma County Airport (California) and reaching a transit altitude of 3000
feet. The pilot noticed what he thought to be balloon or a landing light from another aircraft at a
long distance. The pilot maneuvered the aircraft to the right and immediately realized it was a
drone that passed approximately 50 feet from the aircraft. The air tanker had been taking the
same route from the air attack base to the fire all afternoon. Event did not happen within a
TFR. I do not believe (but have not ascertained) that ATC was not notified. Type of Unmanned
Aircraft System at time of this report is unknown. Law Enforcement involvement is unknown.
8/23/15 US Forest Service CALIFORNIA Walker Fire, Inyo National Forest. A drone operator
intruded into the Walker Fire TFR. There was 1 helicopter flying at the time. Helicopter
operations was suspended for 30-45 minutes until the fire airspace was clear of the drone. The
Inyo, BLM Ranger/LEO Chris Mason made contact with the operator who was located at Tufa
South parking lot at Mono Lake. The operator was taking footage of Mono Lake area for a
shoot. He was very apologetic and left the area, He said that he didn’t know there was a
TFR. A SAFECOM will be filed. (Note from Julie – the new UAS reporting Script was used by
the South Ops GACC to report the intrution to the ARTCC. The SAFECOM number will be
added when received.)
8/21/15 OREGON US Forest Service No SAFECOM: At 16:45, a law enforcement ranger on
the Umatilla NF called Blue Mountain Dispatch, and reported he had spotted a drone over the
Northeast corner of the fire. The Air Ops Branch Director was immediately advised by dispatch.
He immediately contacted Air Attack who was flying over the fire. Air Attack could not confirm
the sighting. The AOBD stated that was the last he had heard of the incident.
8/23/15 WASHINGTON USFS Okanogan Fire A You-Tube video filmed by a “drone” has
been posted three times by an individual that shows a home that was destroyed by the
Okanogan complex wildfire. It has been ascertained that the drone flight occurred inside the
TFR 5/7315. Information has been turned over to the USFS Regional Aviation Safety Officer
and he has been in contact with FSDO. There is no SAFECOM filed at the present time.
8/29/15 9/4/15 UTAH BLM SAFECOM 15-0754 “Drone Event, “I was watching aviation and
ground operations on the Cedar Mountain fire approximately 1 mile from the fire line. Between
1600 and 1630, while aviation operations were ongoing, an unmanned aircraft system {UAS
or drone} flew overhead and continued toward the fire line. I located the individual flying the
UAS, informed him that his actions were compromising the safety of the men and women
fighting the fire, and asked that he stop flying the UAS. He immediately complied with my
request and apologized.” Additional details are unknown at this time.
9/1/15 OREGON Bureau of Indian Affairs SAFECOM 15-0760. At 1320, The Air Ops Branch
Director (AOBD) was alerted to a “drone” flying near the Warm Springs helibase and the County
Line 2 Incident Command Post. When he stepped out to get a view, he observed a large (3-4
foot wingspan) radio controlled airplane circling a mile or less from camp. It appeared to remain
For additions to this document, please contact Julie Stewart (National Airspace Program Manager) at
j5stewar@blm.gov or 503-780-0097.
under 400 – 500 feet AGL. The helibase was informed and the Air Support Group Supervisor
(ASGS) drove to the area where we thought the aircraft must have been controlled from. The
operator was not found. No incident aircraft were flying at the time. The AOBD notified the
Airspace Coordinator at the Northwest Coordination Center who coached the Aircraft Dispatcher
through the new UAS reporting Script to the Seattle ARTCC who reported it in turn to the DEN.
ASGS returned and reported no luck in finding any one who was engaged in model aircraft
activity. We are aware the Warm Springs is a “pilot” drone testing range but had not been
informed of any activity. We will continue conversations with Warm Springs to gather
information and share the “dangers of drones in fire airspace” message.
9/8/15 UTAH USFS Wheeler Fire: A flying bright orange object was spotted at 1850L flying
300-500’ Above Ground Level (AGL) over the Wheeler fire. The object was seen orbiting over
the fire for somewhere between 5-15 mins by the flight crew. As soon as the Aerial Supervision
Module (ASM) crew saw the object, they had one helicopter hold at the dip sight and they
attempted to contact the other helitanker while it was in the drop. They were unable to make
contact with the helitanker until after the drop. They told the helitanker pilot to go back to the
helibase along with the other helicopter. As soon as the helitanker left the location where it
performed its drop, the orange object flew to the drop location and orbited. By 1852L the ASM
crew had shut down air operations due to the object. At this point a large airtanker reported on
scene. The ASM crew elected to have the tanker expend 500 gallons of retardant over the fire,
not necessarily on the fire, so they could make landing weight back at Hill ATB. A SAFECOM
with further details will be submitted. Utah DNR contacted the media about the event and there
was coverage on three different evening news programs. There is no documentation that the
UAS was reported to the Great Basin GACC at Salt Lake City. There is no documentation that
the UAS incident was reported to the Salt Lake ARTCC Watch Desk (and the DEN) via the
GACC UAS reporting script. There was a TFR (5/6423) for the Wheeler Fire that went into
effect at 0005 UTC. (Note from Julie – there were three UAS situations reported for the Wheeler
fire. The second situation is reported below on 9/11. The third situation is believed to have
been mylar balloons and is also reported below.)
9/9/15 CALIFORNIA Cal Fire FC-119 on file. At approximately 1322 local. While flying the
Antelope Incident in Kern County, the Air Attack noticed a small white object between the Air
Attack aircraft and the helicopters. He pointed it out to his pilot who confirmed it was a UAV.
They had just dropped on a tanker and had another tanker in orbit. He notified the Incident
Commander of the UAS incursion and shut down aviation operations. He asked that the IC
notify Law Enforcement. The air tanker in orbit was sent back to the tanker base and all
helicopters were set down at the helibase. The drone disappeared and was not seen again.
After 30 minutes of no drone activity, we resumed helicopter activity on the fire. The IC stated
that the local law enforcement as well as Kern County personnel were in the area searching for
the operator.
9/11/15 UTAH State - SAFECOM 15-0794 Wheeler Fire: “Upon arrival over the Wheeler Fire,
we were in a right hand orbit, having just taken control of the fire from the departing ATGS, and
we were also determining retardant runs for two returning air tankers. We also had control of
two helicopters doing bucket drops in Division Whiskey. As one helicopter was approaching the
drop area, I spotted a small bright orange object circling in Division Whiskey. When it was in the
sun it showed up bright orange, when it was in shadow it completely disappeared from view. We
determined it was a small to medium size drone, and it was at approximately 300 to 500 ft. AGL.
We were circling at 8000 ft MSL initially. The drone hovered approximately one eighth to one
For additions to this document, please contact Julie Stewart (National Airspace Program Manager) at
j5stewar@blm.gov or 503-780-0097.
quarter mile in front of the helicopter as it was dropping water. Initial attempts to contact the
helicopter were unsuccessful. After the helicopter departed the drop area I was able to tell the
pilot about the drone and we held them and the other helicopter at the dip site which was a large
lake below the fire. We decided to shut down aerial operations and had both helicopters return
immediately to the Heber McDonald Airport, which was approximately five miles to the
Northeast. We contacted Dispatch and put all air tankers on hold. We had the object in sight for
approximately twenty minutes. At one point it flew to the exact location where the helicopter had
dropped water. Just prior to losing visual contact, the ATS observed the object fly right down the
middle of the fire. We then lost contact with the drone but this also coincided with the entire fire
being in shadow, so we were unable to positively determine if the object had left the fire area.
Ground personnel were unable to spot the object. We had climbed to nine thousand feet. We
departed the fire approximately thirty minutes after losing visual contact with the object. This
was a state DNR fire with a unified USFS command. Both state PIO and USFS PIO had a
media event and made extensive contact with both television and radio outlets to get coverage
of the event that evening. Geographic dispatch was made aware to notify FAA. No culprit was
identified by fire or law enforcement personnel the day of. RASM and FAO Spent 12 Aug visiting
the fire and talking to personnel involved in the event. Nothing significant to report from the visit.
ASM made a good decision to ground flight operations until the next day. No further UAS was
spotted on the fire.”
9/12/15 UTAH – Wheeler Fire. I was contacted by George Long of the Great Basin GACC that
there was on ongoing UAS situation on the Wheeler fire. I was later contacted by Mr. Long and
informed that it was a mylar balloon situation. However on Sept 15th, I received a copy of the
UAS Script for reporting a UAS incident to the ARTCC that was used on Sept 12th for a wildfire
in the Mill Creek Canyon East area of Utah that had a TFR (5/9806). It describes a drone as
silver with red small in size quad copter. Law Enforcement was not informed. Operator was not
located. I can not ascertain if this was one of the UAS situations reported via SAFECOM. Nor
can I ascertain that it was reported to Salt Lake Center when the situation actually occurred.
9/12/15 UTAH – USFS SAFECOM 15-0803 Church Fork Fire. Single Engine Air Tanker
(SEAT) Pilot reported that while flying over the fire and preparing to drop a load of retardant, he
noticed a small airplane shaped drone that flew approximately 10 feet under the left wing of the
airtanker. The drone was white in color with a red mark and had a wing span of about 20 – 24
inches. At the time of the incident, the Airtanker was approximately 500’ AGL. After the
sighting, the pilot started a climb directly away from the fire and notified air attack of the incident.
Air Attack instructed the pilot to return to the SEAT base after jettisoning his load. Forest
Aviation Officer and Regional Aviation Officer were notified. The GACC notified the ARTCC of
the incident. The incident Public Information Officer informed the local media that the flight
operations were shut down due to the drone presence. Flight operations were resumed later
after it was determined that the UAS was no longer airborne.
9/13/15 CALIFORNIA CalFire FC-119 on file. At approximately 1800 local. While flying the
Sundance Incident, the pilot noticed what he thought was a UAS. He pointed it out to the Air
Attack and they confirmed it was. Air Attack held two helicopters at the dip site and notified
Operations of the UAS incursion. All fixed wing were on hold at the tanker base. The UAS
made 6 to 8 orbits over the wildfire while we were observing it. We lost sight of it as it headed
away from the fire North on Highway 41. They noticed a white sedan in the area but lost sight
of the UAS. The sedan left shortly thereafter heading towards Oakhurst. Once they confirmed
that the UAS had departed the area, they resumed helicopter operations.
For additions to this document, please contact Julie Stewart (National Airspace Program Manager) at
j5stewar@blm.gov or 503-780-0097.
2014
6/7/14 Oregon: Two Bulls Fire. 14 year old teenager made international news for his repeated
UAS flights from his home flying his UAS outside the Two Bulls Fire TFR at an altitude of 800
and posted his videos on You-Tube. .
7/28/14 California: Sand Fire in El Dorado County: Aerial wildfire operation had to be
suspended because of a drone intrusion. It took nearly 40 minutes to isolate and ground the
hobby drone so that the aerial assets could re-engage and support the firefighters on the
ground. Hobbyist was identified and asked to cease operations.
9/7/14 California CalFire Near Mid Air Collision between firefighting helicopter and UAS.
Evasive action taken. UAS passed 10 feet off the windshield. UAS was a “bigger four rotor
system type drone.”
11/8/14 Wyoming: SAFECOM 15-0042: UAS in the West Range Fire in Buffalo, WY. TFR was
instituted the next day and the UAS returned. Operator was located and instructed by the
Incident Commander to cease operations.
Note – there are additional UAS Airspace situations in 2013 and beyond.
For additions to this document, please contact Julie Stewart (National Airspace Program Manager) at
j5stewar@blm.gov or 503-780-0097.