US agencies form ‘whole-of-government’ pact to counter drone threats
Airforce Technology · · 5 min read
This memorandum formalizes what operators have improvised for years: fragmented counter-UAS authorities across DHS, DoD, DOJ, FAA and others. The decision-relevant element is the pre-deployment technology evaluation process, which could become a de facto gateway for vendors seeking federal counter-drone dollars. For industry, the pact signals that interoperability and certification evidence will matter as much as detection range. We expect procurement to consolidate around validated systems rather than bespoke departmental buys.
The announcement that five federal departments have agreed an expanded, whole-of-government approach to counter-uncrewed aircraft system operations reads at first like bureaucratic housekeeping. It is not. The detail that matters is buried in the phrase about evaluating technologies before deployment. That is the difference between a coordination charter and a procurement gate, and it tells us where the counter-drone market is heading.
Start with the problem the pact addresses. Counter-UAS has been a genuinely fragmented mission in the United States. Domestic airspace falls under FAA authorities that were not written with hostile drones in mind. Critical infrastructure protection sits with DHS components. Military installations operate under DoD rules that differ from civilian practice. Law enforcement faces its own legal constraints on detection and mitigation. The result has been a patchwork in which individual agencies bought individual systems, often with overlapping capabilities and incompatible reporting. A drone crossing a jurisdictional boundary could pass from one agency's detection coverage into another's blind spot. The new agreement, covering coordination of counter-UAS operations and a shared evaluation process, is an attempt to close those seams.
The mechanics deserve attention. A pre-deployment evaluation process implies a common baseline: shared test criteria, shared standards for what counts as detection performance, and presumably shared expectations for how systems integrate with command-and-control and reporting architectures. That is harder than it sounds. Counter-UAS chains combine radio-frequency detection, radar, electro-optical and infrared sensors, acoustic arrays, and mitigation effectors, each with different performance envelopes and false-alarm behavior. Evaluating a system in isolation tells you little about how it performs in a layered architecture. If the new process is serious, it will test integration and interoperability, not just individual sensor specifications. Vendors should assume that demonstrating a clean interface to government-furnished command-and-control will become a prerequisite rather than a differentiator.
The demand picture explains why this is happening now. Small unmanned systems have proliferated across the threat spectrum, from hobby-grade quadcopters used for surveillance of sensitive sites to more capable fixed-wing platforms. The conflict in Ukraine has made clear to every procurement office that cheap attritable drones can impose disproportionate costs on defenders, and that counter-drone is not a niche capability but a continuous, layered requirement. At the same time, the domestic counter-UAS mission has grown in visibility, with repeated incidents around airports, prisons, and critical infrastructure. Agencies have been buying urgently, often through rapid acquisition authorities, and the resulting inventory is heterogeneous. A whole-of-government evaluation framework is the natural next step after an urgent-buy phase: it is how an organization moves from fielding what it can get to standardizing what it keeps.
Premium assessment
This forward assessment and the rest of the analysis belong to the Premium tier — available soon. Join the list on the Premium page and read it at launch.
Five US federal departments have agreed an expanded approach to coordinating counter-uncrewed aircraft system operations, including a process for evaluating technologies before their deployment.