ROBNEWS
Through Sept. 1, 2026, the U.S. Wildland Fire Service logged 74 drone incursions near wildfires, and 78% of tanker runs diverted. The fix is a shared sky operating system.
When a DJI Phantom 4 crossed into the Temporary Flight Restriction (TFR) over the Face Canyon fire in Beaver, Utah on June 29, the retardant tanker on the first retardant run had to bank away. The drone stayed aloft for roughly an hour, and so did the ground order to stand down. The aircraft's owner, a juvenile whose father owned the drone, was unaware of the TFR or the Part 107 commercial-operator rule. The drone was seized. None of that tells the aerial fleet what they already know: the airspace around a wildfire is no longer a closed system.
The U.S. Wildland Fire Service (WFS), an agency of the Department of the Interior, counted 74 unauthorized drone incursions near wildfires through September 1, 2026, up from 53 across all of 2025 and 32 in 2024 (WFS via DroneLife). The 2026 season is not over, so the year-to-date number will move. The 78% diversion figure, the load-bearing one for this story, comes from the interagency Aviation Safety Communiqué, which pools incursion data across Interior, the USDA Forest Service, and state jurisdictions.
A TFR is the FAA's no-fly circle around an active incident, and the line a drone operator crosses when an aerial firefighter has to turn back. The cost of one diversion is not abstract. An air tanker that aborts a retardant run is grounded while air traffic control confirms the airspace is clear, and the next run requires a fresh approach into rising smoke and wind that may have already shifted. With 45 of this year's 74 incursions in Washington, most of them clustered around the Spokane-area urban-interface fires, and 7 in California, the pattern is not spread evenly across the map. It is following the same population edge that the fires themselves are following.
The Spokane-area cluster drew independent regional reporting in August. KUNC and the UPR Mountain West News Bureau both detailed how the urban-interface fires pulled in hobbyist drone operators, many of them new to the airspace rules around wildfires. WFS UAS Division Chief Brad Koeckeritz attributes the rise to a straightforward collision: more consumer drones in private hands, and more fires breaking out in the zone where houses meet fuel.
The federal posture is already sharp. The FAA can prosecute an incursion as a federal crime carrying up to two years in prison, layer on civil penalties up to $75,000, and suspend or revoke the operator's pilot certificate. WFS is coordinating with the Forest Service, FBI, FAA, and state and local law enforcement, some of which have picked up drone-detection capability, on referrals for enforcement (DOI WFS "No Drone Zone" page).
Enforcement is one of the systems being built. The other half is airspace coordination, and the work is uneven. TFRs are issued and broadcast, but the notice has to reach a hobbyist who bought a drone at a big-box store the week a fire breaks out. The DOI WFS "If you fly, we can't" campaign is the public-education layer. A NIFC UAS Detection System test and evaluation briefing lays out the detection and identification technology the agencies are evaluating. A 2026 federal bill would direct the FAA to formally study wildfire drone incursions and the operational data around them.
The constructive model that fits this problem has four moving parts. Mandatory manufacturer-side geofencing that activates when a TFR is issued, not a year after. Push notifications to registered operators whose aircraft enter a TFR's bounding box, before a tanker is in the air. Drone-detection capability at the incident command post, paired with the existing law-enforcement referral path. Urban-interface wildfire planning that treats the airspace as part of the fire perimeter, not separate from it. The first two pieces depend on the FAA and the manufacturers; the third is already being tested through NIFC; the fourth is a planning problem for cities like Spokane.
The 32-to-53-to-74 line shows the current system is not keeping up. The next data point to watch is whether the 2026 bill lands, whether the FAA standardizes TFR data with manufacturer geofencing databases, and whether the NIFC UAS detection work moves from evaluation to operational deployment in time for the 2027 season.