By Wesley Alexander • September 11, 2026 • 8 min read

The comment window on the counter-UAS interim final rule closed September 4. The argument phase is over. What starts now is the build-out, and the government has told you its size: roughly 1,500 state, local, tribal, and territorial agencies projected to certify at the detection tier within two years, running equipment drawn from lists hosted on a federal portal that you, the pilot whose aircraft that equipment points at, cannot read.

Two things happened in the last three weeks that make this the moment to update your operating posture. First, the Pentagon's counter-drone task force held its second interagency summit on August 21 and named its top near-term technology priority: low-cost detection and low-altitude air domain awareness covering, in its director's words, "the entire breadth of the United States." Second, the FBI's drone program lead put a number on the certification pipeline. According to reporting by DroneXL, roughly 500 officers have been trained since the rule took effect July 1.

If you fly commercially, for a public safety program, or for infrastructure clients, the question is no longer whether a local agency near your operation will have counter-UAS capability. It is when, and whether your flight will look legal to a sensor operator who finished an online course last month.

What actually changed on July 1

The SAFER SKIES Act, signed December 18, 2025 as part of the FY2026 NDAA, extended counter-drone authority to state, local, tribal, and territorial law enforcement and correctional agencies for the first time. The Justice and Homeland Security interim final rule implementing it took effect July 1 and published July 6. We covered the framework in detail when it landed: what the SAFER SKIES rule authorizes and where your lawful flight now carries mitigation exposure.

The short version is a two-tier certification structure run through the FBI's National Counter-UAS Training Center:

The rule carries real constraints: mitigation actions must be reported within 48 hours, air traffic control must be notified within five minutes of activating a mitigation system, records of intercepted communications are capped at 180 days, uncoordinated action can draw civil penalties of up to $100,000 per violation, and the entire authority sunsets December 31, 2031 absent reauthorization.

The part that should bother you: the equipment list is not public

Here is the structural problem for legal operators. The specific systems a certified agency may deploy live on two lists, an Authorized Technologies List defining approved categories and an Authorized Systems List naming specific products, maintained jointly by DOJ and DHS with the Defense Department, DOT, the FCC, and NTIA on a federal portal. The rule states outright that the mechanics of those lists are not codified in the regulation.

The departments expect early categories to include radio-frequency detection that reads a drone's control link and command-injection systems that can take an aircraft over. Which hardware clears the bar, what it collects, and how it behaves toward a compliant aircraft is not something a remote pilot can look up.

I spent a career flying test programs where every system that could touch my aircraft was documented, and the documentation was the safety case. What is being built here is the opposite arrangement: a distributed sensor and effector network, operated by hundreds of independent agencies at varying training levels, running hardware from a catalog the operators being sensed cannot inspect. From a C2 link integrity standpoint, that matters. RF detection is passive and should not affect your link. Command injection, by definition, is not. Your protection is the rule's credible-threat standard and its reporting requirements, plus the paper trail you carry. It is not technical transparency, because there is none.

The World Cup numbers are the template, and they cut both ways

The scale-up argument leans heavily on this summer's tournament. Federal agencies detected more than 1,600 unauthorized drones across the 11 host cities, seized more than 700 aircraft, opened around 120 federal cases, and arrested a dozen people. We broke down what those enforcement numbers mean for Part 107 pilots when the first figures came in.

Read the ratio carefully: 700 aircraft seized, 12 arrests. DHS officials have said teams talked to nearly every operator whose drone was seized because intent is unknowable until someone asks. The overwhelming majority of interdicted pilots were not threats. They were people who did not check a TFR. That is a compliance failure, and the honest fix is better warnings, better geofencing, and better preflight discipline. The institutional response, however, is interception capacity in more local hands, and Los Angeles 2028 is already expected to be larger on every axis.

For operators, both readings lead to the same place. Whether the net exists to catch bad actors or careless hobbyists, your job is to be instantly distinguishable from both.

Your preflight now includes the detection environment

Treat certified counter-UAS presence the way you treat controlled airspace: assume it, plan for it, and carry proof of your legitimacy. Concrete changes worth making now:

Fly with Remote ID actually working, not just installed. Detection-tier agencies lean on Remote ID as the first identification layer. A broadcast module with a dead battery or a firmware fault makes your legal flight look like an anonymous track. Verify broadcast before launch, log that you verified it, and spot-check your own aircraft with a receiver app periodically.

Carry your authority and make it reachable. Waiver, COA, LAANC approval, airspace authorization, exemption conditions: have them on the device in your hand, not on a server at the office. If an officer approaches mid-mission, the difference between a two-minute conversation and a seized aircraft is often how fast you can produce documentation.

Pre-coordinate where it makes sense. For recurring operations near stadiums, prisons, critical infrastructure, or event venues, a proactive call to the local agency's UAS or special-events unit changes your status from unknown track to known operator. Agencies deploying detection under FEMA counter-UAS grant funding are building operating pictures; being in the picture as a cooperative actor is cheap insurance.

Check TFRs like the seizure statistics depend on it, because they do. Most of the 700 seized aircraft belonged to pilots who failed this one step. Check NOTAMs and TFRs at planning time and again immediately before launch, and document both checks.

Decide your seizure protocol before you need it. If your aircraft is interdicted or confiscated, your recourse runs through the rule's reporting and records provisions. Know what you will say, know that mitigation actions must be documented and reported within 48 hours, and get the incident, agency, and officer details in writing. Then call counsel before negotiating for your airframe back.

Log defensively. Flight logs, firmware versions, crew assignments, and command link records tied to timestamps are how you prove after the fact that your aircraft was where it was authorized to be, doing what it was authorized to do.

Where the record goes from here

More than 46,000 filings landed on the docket before comments closed September 4, according to DroneXL's reporting. The departments specifically invited argument on certification expiration, mutual aid between certified and uncertified agencies, and the civil penalty structure. If you filed during the window we flagged in our comment-deadline briefing, your input is in the record the final rule must answer. The rulemaking questions that matter most for legal operators are whether the privacy and data-handling limits survive into the final rule, and whether the authorized-equipment process ever gains a public-facing component.

Meanwhile the technology side accelerates on its own track. The task force is running a year-long directed-energy pilot across five military installations, with a live shoot-off planned for December where systems that perform can convert directly into procurement. None of that touches civil operators directly today, but it tells you the direction: detection first, everywhere, with mitigation capacity growing behind it.

The operators who thrive in that environment will be the ones whose flights are boring to a sensor operator: broadcasting identity, matching an authorization, and documented end to end. If your program needs the enforcement and counter-UAS landscape distilled into working documents your crews can actually use, the UAVHQ Briefing Packs cover exactly this terrain, and the weekly UAVHQ dispatch on Substack is where we track the final rule, the equipment lists, and the December shoot-off as they develop.

This article is operator analysis, not legal advice. Consult your own counsel on interactions with law enforcement and on your obligations under your operating authority.

Sources

  1. DOJ/DHS, "Counter-UAS Authority for State, Local, Tribal, and Territorial Law Enforcement and Correctional Agencies," Interim Final Rule, Federal Register, July 6, 2026
  2. DefenseScoop, "One year in, America's counter-drone task force still has 'a ton of work to do,'" August 24, 2026
  3. DefenseScoop, "U.S. military to host directed energy 'shoot-off' amid governmentwide counter-drone push," August 21, 2026
  4. Department of War, "DOW Hosts 2nd Interagency Summit to Strengthen Counter-Drone Defense," September 9, 2026
  5. DroneXL, "1,500 US Agencies Are About To Get Counter-Drone Powers," September 10, 2026