Congress’s annual defense bill for fiscal 2025 has become an important battleground for drone policy. Multiple pieces of legislation and amendments filed earlier this year signal that the NDAA could reshape procurement, counter-UAS authorities, and the commercial drone market — even before the final conference text is agreed. The most consequential items to watch are threefold: targeted measures aimed at China-origin manufacturers, expanded counter-UAS authorities and coordination, and directives intended to strengthen domestic supply chains and testing. These trends create both risk and opportunity for industry, public safety, and civil liberties.

First, several House measures have sought to use existing national-security authorities to restrict certain foreign-produced telecommunications and video surveillance equipment, language that would capture drone systems and related software. The Countering CCP Drones Act, as reported by the House, would amend the Secure and Trusted Communications Networks Act of 2019 to add specified DJI equipment to the FCC’s covered list. That House text passed the House earlier in the cycle and was carried as a stand-alone bill and as proposals to be folded into NDAA discussions.

At the same time, the broader NDAA vehicle includes drone-specific language in other places. The House version of the FY25 defense bill (H.R. 8070) contains a surprising mix of provisions: it establishes a concept for a “Drone Corps” within the Army and directs the Department of Defense to conduct forensic disassembly and reporting on a DJI-manufactured aircraft, among other measures aimed at assessing vulnerabilities. Those provisions signal congressional interest in both operationalizing unmanned systems and cataloging potential supply chain and technical risks.

Those House actions have not gone unchallenged. The Senate Armed Services Committee’s markup of the NDAA omitted the most sweeping DJI-targeted language from the committee text, reflecting a more cautious approach in the Senate toward an outright or immediate ban. That divergence between House and Senate drafts is why the final conference negotiations will be consequential. If House-origin language survives in conference, it could trigger administrative processes with real downstream effects for imports, federal procurement, and FCC equipment authorizations. If the Senate approach carries, changes could be narrower and more focused on testing, mitigation, and transition assistance.

Parallel to debates over vendor targeting, lawmakers have pushed to reauthorize and expand counter-UAS authorities for DHS and DOJ and to clarify FAA roles for detection and mitigation. A bipartisan Counter-UAS Authority Security, Safety, and Reauthorization bill introduced in June proposes to extend critical counter-UAS authorities, set minimum performance requirements for counter-UAS systems, and create training and operator-qualification standards. That proposal was floated as an amendment to NDAA and highlights a bipartisan intent to give federal agencies clearer tools to detect and respond to hostile unmanned aircraft operations while simultaneously adding privacy protections in some drafts.

Taken together, these parallel threads in the NDAA process point to several likely impacts, depending on which provisions survive final negotiations:

  • Procurement and market effects. If NDAA language leads to FCC or procurement restrictions on equipment from specifically named firms, federal agencies and government contractors would face accelerated transition requirements. That would increase demand for vetted domestic or allied suppliers but impose near-term replacement costs for agencies and public-safety partners that currently rely on incumbent systems. The potential for broad supply-chain disruption is real, and smaller local governments and first responders are particularly exposed. Public-safety organizations and advocacy groups have already publicly warned that blunt prohibitions or rushed transitions could disrupt emergency response capabilities.

  • Operationalization of counter-UAS. Expect clearer legal frameworks for when and how federal agencies, and possibly authorized state or local partners, may detect and mitigate threatening UAS operations. Proposals aim to standardize performance, training, and privacy safeguards. That will likely spur procurement of more detection and mitigation technologies, and increase demand for operator certification and standardized protocols.

  • Supply chain and industrial policy. Several NDAA provisions and related bills emphasize building domestic resiliency in small UAS components and increasing RDT&E investment in trusted suppliers. If enacted, that creates incentives and potential funding streams for domestic manufacturers and integrators; but it will take time for the industrial base to scale to replace low-cost imports at parity for many civil uses.

  • Legal and administrative uncertainty. Even narrowly targeted statutory directives can produce broad administrative consequences. For example, statutes that instruct an executive agency to add equipment to a covered list force the FCC and other agencies into technical reviews and procedural work that can last months. The shape of those processes matters: statutory deadlines, transparency requirements, and appeal or waiver mechanisms will determine whether the outcome is a managed transition or a disruptive cliff.

What should industry, public-safety agencies, and policymakers do now?

  • Industry should document supply chains and develop contingency plans. Companies that rely on global components need pragmatic mitigation strategies, including multi-source sourcing and clear timelines for replacing restricted components.

  • Public-safety agencies and contractors should engage with lawmakers and the executive branch to secure transition funding and phased compliance paths. Abrupt procurement bans without replacement funding risk operational gaps for first responders.

  • Policymakers should insist on technically rigorous, transparent reviews rather than unilateral, opaque listings. Where national-security risk is asserted, agencies should be required to publish threat assessments and remediation options so affected stakeholders and alternative suppliers can respond.

  • Civil liberties advocates and technologists should press for strong safeguards in any expanded counter-UAS authorities: narrow scopes for data collection, strict retention limits, auditing requirements, and oversight of any kinetic or intrusive mitigation tools.

Bottom line: by the end of 2024 the NDAA process had elevated drones from a peripheral procurement topic to a core national-security and industrial policy issue. Which House provisions survive conference, and how agencies implement statutory directives, will determine whether the NDAA causes a managed shift toward trusted suppliers and clearer counter-UAS tools, or a disruptive scramble that strains public-safety and commercial operations. The most constructive path blends rigorous technical review, phased transitions with funding support, and clear privacy and training standards. Absent that balance, the bill could achieve strategic goals in theory while imposing heavy costs in practice.