Congress finished the FY2025 NDAA as Public Law 118-159. The law layers new oversight, procurement priorities, and reporting requirements onto an already busy counter-uncrewed aircraft systems portfolio. That matters because Congress did two things at once: it pushed money and demanded answers. The result is a stopgap posture that improves some material shortfalls while leaving legal and operational friction unresolved.

First, the money. Lawmakers authorized notable increases for fielded intercept capabilities and advanced development. The enacted text and accompanying CRS analysis show Congress added hundreds of millions for Army and other counter-UAS programs relative to the Department of Defense request, including substantial added procurement for the Low, Slow, Small Integrated Defeat System family and extra funds to accelerate the Next Generation Counter-UAS Missile. Those topline adjustments will speed fielding of kinetic interceptors and effectors that military commanders want. But money alone does not solve sensor gaps, information sharing, or rules of engagement.

Second, the architecture. The NDAA requires creation or designation of a counter‑UAS task force and directs the Joint Counter‑Small Unmanned Aircraft Systems Office to establish a threat library containing classified and unclassified threat data, proposed countermeasures, and a global incidents log. The mandate to collate threats and share a single library is overdue. A curated repository brings operational value if it is kept current, accessible to the right stakeholders, and paired with hard performance metrics. If it becomes another bureaucratic silo, it will only add paperwork.

Third, the accountability timeline. The statute and explanatory language force the Department of Defense into near-term deliverables: assessments of the DOD counter‑UAS enterprise, briefings on task force actions, and plans to procure additional kinetic effectors for Army LIDS with deadlines staggered into 2025. Those timelines are purposeful. Congress is not buying vague promises. It wants measurable plans and procurement roadmaps. Expect quick reallocation requests, accelerated contracts, and firm deadlines for production briefs. That pressure helps procurement but will create short-term supply chain and testing bottlenecks.

Fourth, domestic deployment and interagency friction. The NDAA includes pilot authorities and direction for DOD to better utilize existing counter‑UAS authorities in coordination with the Federal Aviation Administration. That pushes the Department toward limited domestic deployments at select DOD facilities using higher-energetic defeat options such as high-powered microwave or directed energy in certain cases. The policy intent is clear: protect installations and sensitive assets. The execution will be harder. Civil airspace regulators, law enforcement, and privacy advocates will demand strict boundaries. Legal authorities for counter‑UAS in domestic airspace remain compartmentalized across DOJ, DHS, FAA, and DOD. The statute nudges coordination but does not fully reconcile competing statutes and civil liberties concerns. Expect operational caution and delays while agencies negotiate policy and technical safety standards.

Fifth, capability tradeoffs and the technology pipeline. Congress funded interceptors and electronic support but left some other lines unchanged or trimmed. That reflects a pragmatic choice: buy the weapons that kill or disable hostile small UAS now, while accepting risk that sensor modernization and data fusion work must catch up on a compressed timetable. The threat library and the requirement for a holistic assessment are intended to guide those decisions. But technology gaps cannot be closed by directives alone. Integrating commercial sensor networks, securing supply chains for radars and EW payloads, and retrofitting existing C2 architectures will take time and operating risk.

Bottom line and recommendations. The FY2025 NDAA buys important capacity and forces transparency. That is a defensible and necessary step. But three realities follow:

  • Funding additions will improve short-range defeat options but will not immediately fix nationwide detection, attribution, or command and control for distributed low-cost UAS threats. Congressional pressure should be followed by measurable sensor and data‑fusion milestones, not only procurement totals.

  • Interagency friction remains the single largest nontechnical vulnerability. Congress required coordination. Now agencies must translate guidance into binding agreements that define when and how DOD can act inside the United States, who authorizes kinetic defeats, and how to protect civil liberties while defending critical infrastructure. Policymakers should push for a narrow pilot program with clear ROE, mitigation plans for collateral effects, and an after‑action review requirement.

  • The threat library is a smart move if it is treated as an operational tool. To be useful it must be accessible to combatant commands, installations, relevant federal agencies, and cleared industry partners. Congress should attach follow‑on funding for the library’s sustained staffing, classification handling, and continuous technical ingestion pathways from deployments and allied sources.

The legal, operational, and technical gaps are not novel. What is new is that Congress tied procurement increases to specific deliverables and timelines. That creates momentum. If the Department and interagency partners convert these directives into hardened, interoperable C‑UAS architectures—with transparent metrics and safe domestic pilot rules—the U.S. will be measurably more resilient against low-cost drone threats. If they do not, the money will buy incremental systems while adversaries continue to exploit sensors, networks, and legal seams. The next 12 months will show whether congressional pressure produced durable capability or just a faster acquisition treadmill.