Counter-UAS Is an Integration Problem Before It Is an Interceptor Problem

A layered defense is not a shopping list

In July 2026, the Congressional Budget Office estimated that equipping one representative military installation with a layered counter-small-UAS defense would cost about $74 million, with another $5 million each year for support. CBO also concluded that no single detection or defeat method provides complete protection. Its most comprehensive option combines radar, radio-frequency detection and defeat, kinetic interceptors, handheld systems, and command and control.

That finding should be read as an integration warning. Adding more sensors and effectors does not necessarily create a better defense. It can create more tracks, more interfaces, more alerts, and more decisions for an operator to reconcile under pressure. The central question is whether the complete system can detect, understand, decide, act, and reassess before the threat completes its mission.

The threat is moving past RF assumptions

The Department of Defense strategy fact sheet published in December 2024 anticipates unmanned systems becoming more capable, affordable, autonomous, and networked, including the ability to operate in larger numbers and as swarms. It calls for integrated, open, modular countermeasures, realistic testing, and faster adaptation.

CBO notes that fiber-optic control and fully autonomous navigation can remove the radio link that radio-frequency sensors and jammers depend on. In those cases, an RF-centric defense can lose both a detection path and a defeat option. Layered sensing is therefore not redundancy for its own sake. It is protection against the failure of any one physical assumption.

Public documents define the problem and an evaluation framework, but they do not provide enough operational data to rank specific systems or determine how well a particular autonomous function performs against a current threat set. That limit should remain visible in any acquisition decision based on open sources.

Use autonomy to remove latency before judgment

JIATF 401 treats autonomy as a spectrum. Its 2026 handbook identifies useful functions such as automatic classification, sensor cueing, response recommendations, trajectory modeling, and interceptor guidance. It also states that people should retain authority over actions with legal, ethical, or escalatory consequences, especially in homeland settings.

The strongest early uses of autonomy are high-volume, time-sensitive, and reversible tasks. These include correlating tracks from several sensors, filtering likely false alarms, maintaining track continuity, cueing a better sensor, estimating engagement windows, and presenting a ranked set of response options.

A classification algorithm produces an estimate, not certainty. Operators need to see confidence, contradictory evidence, data age, and the reason a response is being recommended. The practical measure is not autonomy level as a marketing label. It is the amount of decision time gained without creating unacceptable identification, safety, or accountability risk.

Test the complete engagement chain

JIATF 401's Common Criteria for C-UAS Characterization addresses automated sensor fusion, weapons pairing, engagement zones, time to intercept, collateral effects, operator workload, software architecture, sensor and data integration, and operation in contested environments. The criteria also note that large amounts of counter-UAS test data remain difficult to compare because they sit in separate silos with inconsistent provenance and quality.

Testing should follow the complete sequence of detect, track, identify, decide, engage, and assess. Detection range matters, but so do false alarms, track continuity, classification accuracy, operator workload, decision-to-action latency, simultaneous engagement capacity, collateral risk, and post-engagement assessment. A system that performs well against one cooperative target may still fail when several ambiguous tracks arrive during degraded communications.

Degraded operation belongs inside the baseline. The handbook recommends local edge processing when backhaul fails, layered sensing to cover blind spots, and explicit playbooks for network and spectrum degradation. These are basic requirements against an adversary that can jam, spoof, maneuver behind terrain, or arrive from several directions.

Buy a learning loop

Procurement should require software update paths, accessible test telemetry, version control, threat-library refreshes, documented interfaces, and the ability to replace one component without rebuilding the entire defense. The government also needs rights sufficient to compare performance across vendors and retune algorithms as the threat changes.

The desired product is a repeatable learning cycle: observe new threat behavior, reproduce it in test, measure the end-to-end effect, update software or tactics, and return the improvement to operators. Hardware remains essential, but the rate of adaptation becomes part of operational effectiveness.

Authorities and people must be treated as system components. A January 2026 Defense Department inspector general advisory identified conflicting requirements across more than 20 counter-UAS policy documents and different service procedures for gaining operational approval in the United States. A technically available effect is not an operational option unless the commander, operator, and system all reflect the same authority.

Actual requirements will vary with terrain, airspace, mission, infrastructure, and acceptable collateral risk. Many operational details remain classified. What can be said with confidence is narrower and more useful: a credible counter-UAS defense is an integrated, measurable, and continuously adapting operational system.