Congress and the Defense Department are in a straightforward fight over priorities for countering unmanned aircraft systems. The Department of Defense asked for a baseline set of counter-UAS procurements and RDT&E in its FY2025 budget submission, but House and Senate committees proposed markedly different trajectories for how fast and where to spend. That divergence matters. The United States is being forced to decide whether to buy layered, pragmatic capabilities now or to bet on longer, costlier development programs that may miss the next set of threats.

Start with the numbers the Pentagon sent to Congress. In the March 2024 FY2025 P-1 procurement submission the Army’s request included roughly $117.4 million for counter-small UAS interceptors and about $280.1 million in other C-sUAS procurement lines, with additional RDT&E accounts supporting advanced development. Those are real dollars the services planned against a diverse threat set that ranges from hobbyist incursions to weaponized, one-way attack drones. Congress saw those requests and concluded they were insufficient in some areas and excessive in others.

The House Armed Services Committee moved to codify an executive agent role to centralize counter-small UAS training, requirements, and development. Section 902 of the House-passed NDAA (H.R. 8070) would require the Secretary of Defense to designate a senior official to perform that function. That is a useful reform if executed properly. Centralization reduces stove-piping, forces common standards, and speeds procurement choices. But an executive agent without clear authorities, metrics, and accountability will simply add another layer of bureaucracy. Congress and the Department need a crisp list of deliverables and deadlines for that office.

The Senate Armed Services Committee took a different tack in its S.4638 text. It pushed for a DOD-maintained threat library and considered extensions and adjustments to DOD’s limited domestic counter-UAS authorities under 10 U.S.C. §130i. The Senate language emphasizes institutional information sharing and legal authorities to protect covered facilities. That emphasis addresses a persistent operational problem: fragmented threat reporting and unclear authorities at installations. But extending or expanding authorities without commensurate oversight and civil liberties guardrails risks domestic mission creep. Both committees are right on different points. Congress must merge those strengths, not trade one for the other.

On the procurement side the debate is practical and painful. Army and Marine concepts feature LIDS variants, kinetic interceptors such as the Coyote family, and investments in NGCM-style interceptors and directed-energy experiments. The services argue for more interceptors and for production diversification to avoid single-vendor chokepoints. Committees highlighted unfunded priorities and pushed more procurement for interceptors and accelerated development for next-generation missiles and non-kinetic systems. Those priorities are defensible. But Congress has to balance interceptor buys against cheaper mitigation and detection options: electronic warfare payloads, hardened airspace architectures, hardened command-and-control, improved sensors, training, and rules of engagement. Buying only expensive interceptors is a losing cost curve against swarms of $500 commercial drones.

There is also an industrial base decision here. The Army and Congress have both signaled the need to certify additional interceptor manufacturers for LIDS-style solutions and to diversify suppliers for both kinetic and non-kinetic effectors. That is sensible. Reliance on a single production line creates strategic vulnerability in a crisis. If the goal is resilience, Congress should fund surge production pathways, small-volume contracts to multiple vendors, and rapid qualification lanes so newer entrants can scale. Otherwise we buy capability we cannot sustain.

Operational tradeoffs are unavoidable. Kinetic interceptors are visible and politically tidy but expensive per shot. Electronic attack and jamming are cheaper per engagement but risk collateral interference with friendly platforms and civilian spectrum users. Directed energy promises low marginal cost per engagement but remains immature for many operational contexts. The right posture is layered: detection and attribution, layered defeat options scaled to the threat, and rules to deploy the least escalatory and most cost-effective measure available. Training, doctrine, and exercises must be funded alongside hardware. Committees that pressed for training reports and task forces were on target.

Finally, a broader policy frame: DHS and DOJ authorities for domestic counter-UAS operations are being debated in parallel, and House Homeland Committee leaders introduced a bipartisan Counter-UAS Authority Security, Safety, and Reauthorization Act of 2024 to extend and clarify those civilian authorities. The FY2025 NDAA debate cannot be isolated to DOD funding lines. If DHS, DOJ, FAA, and DOD do not synchronize authorities, procurement, and standards, then installations and civilian infrastructure will face gaps and overlaps. Congress must insist on interoperability standards, minimum performance requirements for C-UAS systems used domestically, privacy limits, and clear lines of responsibility.

Bottom line and recommendations:

  • Fund layered capability now. Increase practical procurement for detection, EW, and scalable defeat options while holding a portion of funds for rapid prototype buys of promising directed-energy and NGCM efforts. Do not let headline interceptors eat the entire budget.

  • Codify one senior DOD executive agent with measurable deliverables, clear authorities, and an aggressive timeline to standardize training, certification, and approved mitigation options. Tie that designation to quarterly congressional briefings.

  • Require a shared threat library and common reporting standards across DOD, DHS, and DOJ. Make the library machine-readable and fund integration with base defense C2 systems. That will shrink sensor-to-shooter timelines.

  • Push for procurement diversity and surge capacity. Certify additional manufacturers through accelerated lanes, and fund small contracts to multiple vendors to build a resilient supply chain.

  • Insist on a domestic framework that balances operational authorities with privacy and civil liberties protections. Align FAA minimum performance requirements for C-UAS systems used in domestic airspace. The Homeland Committee bill provides a foundation that should be harmonized with NDAA language.

This is not a technical hobby. Adversaries are already putting low-cost air systems into the battlespace and onto critical infrastructure. The FY2025 debates are a choice between buying sensible, layered defenses now and spending the next decade playing catch-up with expensive single-solution buys. If Congress and the Department want to protect installations, forces, and civilians, they need to stop treating counter-UAS as an add-on and start funding it as an operational imperative with clear governance and measurable outcomes.