S-4768-119
Read twice and referred to the Committee on Armed Services.
Sponsored by John Cornyn (R-TX)
What it does
This bill would direct the Secretary of the Army to establish requirements for a networked, autonomous system capable of detecting, tracking, and physically destroying small enemy drones (specifically Group 1 and Group 2 unmanned aircraft systems) that threaten ground combat and support vehicles. The system would need to work across different brigade combat team units using common hardware and software architectures. The bill would also require the Secretary to submit a report to congressional defense committees detailing hardware and software components and an implementation timeline covering fiscal years 2028–2032.
Who benefits
U.S. Army soldiers and ground combat units who would gain automated protection against small drone threats. Brigade combat team commanders who would benefit from interoperable, networked defense systems. Defense contractors and technology companies specializing in autonomous systems, counter-drone technology, sensors, and mesh networking who may compete for development and procurement contracts. Indirectly, U.S. allies who operate alongside American ground forces and could benefit from shared defensive capabilities.
Who is hurt
Taxpayers who would bear the cost of developing and fielding a new weapons system, though no specific dollar amount is authorized in this bill. Existing counter-drone program offices or contractors whose current systems may be displaced or deprioritized if the Army adopts a new common architecture. Smaller defense firms that may lack the scale to compete for a large, interoperability-focused procurement. Adversaries who currently exploit small drone vulnerabilities in U.S. ground forces.
Supporters argue
Supporters argue that small commercial and military drones have become a decisive battlefield threat, as demonstrated in conflicts in Ukraine and the Middle East, where inexpensive Group 1 and Group 2 drones have destroyed armored vehicles and disrupted logistics. They contend that the Army currently lacks a standardized, networked kinetic counter-drone capability across brigade combat teams, leaving ground forces exposed, and that requiring a common architecture would prevent the costly, fragmented procurement of incompatible systems that has historically plagued Army modernization efforts.
Opponents argue
Opponents argue that the bill's use of "should" rather than "shall" in the core requirement makes it legally non-binding, potentially rendering the mandate unenforceable and the legislation largely symbolic. They contend that mandating specific technical features — passive/active sensors, mesh networking, autonomous kinetic effects — in statute risks locking the Army into a particular design approach before the technology has matured, potentially wasting development resources or foreclosing more effective solutions that emerge during the 2028–2032 timeframe.
Constitutional context
Congress's authority to establish military requirements and direct Army procurement flows from the Military Powers clauses (Art. I, §8, cls. 12–14), which give Congress broad power to raise and equip armies. The reporting requirement and implementation timeline also engage the Appropriations Clause (Art. I, §9, cl. 7), as any future procurement would require separate congressional funding. No active constitutional tension is implicated here.
Checks and balances
Congress gains oversight authority through the mandatory report requirement; the Executive Branch (Secretary of the Army) retains discretion over specific system design and acquisition decisions, and any actual procurement would require a separate congressional appropriation.
Historical precedent
Congress has previously directed the Army to develop and field specific counter-drone capabilities through National Defense Authorization Acts, including provisions in the FY2020 and FY2022 NDAAs that established counter-UAS programs and reporting requirements.