H.R. 5061 rewrites and reauthorizes federal counter‑unmanned aircraft system (UAS) authorities across DHS, DOJ, and the FAA. It preserves and narrows operational authorities to detect, track, seize, or mitigate UAS, but conditions those activities on FAA determinations about aviation safety, formal interagency coordination, new approved‑systems lists, operator training standards, and expanded reporting and oversight.
The bill matters because it shifts operational control toward a structured approval process: the FAA becomes a gatekeeper for systems that may affect national airspace; DHS administers approvals for non‑federal covered entities and runs pilot programs enabling some State/local law enforcement mitigation; and Congress gets recurring briefings, public reports, and IG audits. For compliance officers, airport operators, law enforcement, and system vendors, the bill creates new application, training, and documentation obligations, while also carving out a formal exclusion for certain foreign‑affiliated manufacturers and setting an October 1, 2030 sunset for most authorities.
At a Glance
What It Does
The bill consolidates counter‑UAS authority into coordinated DHS/DOJ/FAA processes: it requires a public, government approved list of detection/mitigation systems, tasks the FAA with minimum performance requirements and testing, and authorizes DHS to permit covered entities and select law enforcement agencies to deploy approved detection and (in pilot programs) mitigation systems under negotiated agreements.
Who It Affects
Covered airports, owners of critical facilities and large public event organizers; State and large local law enforcement agencies that may join mitigation pilots; FAA and DHS program offices and inspectors general; manufacturers and vendors of counter‑UAS systems (with exclusions for certain foreign‑related firms); and verified UAS operators seeking routine airspace access.
Why It Matters
It creates clearer gatekeeping and technical validation (FAA performance standards, site testing, and an approved‑systems list), but also expands real‑world mitigation authorities beyond federal actors via structured pilot programs—changing who can lawfully disrupt or seize UAS near airports, critical sites, and major events while increasing compliance, reporting, and civil‑liberties safeguards.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
H.R. 5061 reorganizes how the federal government manages counter‑UAS tools and operations. The bill amends DHS’s existing Section 210G authority to require prior FAA determinations about aviation safety before DHS or DOJ may seize, disrupt, or otherwise mitigate UAS; it also forces joint research, testing, and a requirement that the government publish and maintain an internal approved list of makes and models for counter‑UAS detection and mitigation equipment.
That list must describe functions, authorized uses, terminal‑airspace suitability, and any conditions; the FAA must sign off that listed systems meet minimum performance and won’t harm aviation or that identified harms can be mitigated.
Concurrently, the bill rewrites 49 U.S.C. 44810 to give the FAA explicit counter‑UAS authorities for detecting, identifying, monitoring, tracking, and—where authorized—disrupting or seizing UAS to address credible threats to the national airspace system. The FAA must create an Office of Counter‑UAS Activities with a director to coordinate deployments, lead strategic planning, and be the central point of contact for airports and other stakeholders.
The FAA also must set minimum performance requirements (deadlineed), run testing and validation activities (including demonstration processes for manufacturers or end users), and stand up a voluntary verified‑operator program to streamline lawful UAS access to sensitive airspace.The bill enables non‑federal actors to participate under tight controls. DHS may authorize covered entities (owners/operators of covered sites or events) to acquire and operate approved detection systems under an application and written agreement process that requires threat justification, operational plans, and trained operators; applications must be approved or rejected within statutorily short windows (45 days, 90 days when a law‑enforcement waiver is requested).
Separately, once FAA performance criteria are met, DHS will establish a law‑enforcement mitigation pilot program allowing selected State and large local law enforcement agencies—working under DHS/DOJ/FAA oversight—to operate approved mitigation systems at covered sites and events. That pilot is limited in size, contains specific pre‑approval and reporting requirements for each mitigation event, and includes a special pathway for multinational sporting events with a mechanism to transfer select agencies into the main pilot after the event.Airports receive tailored treatment: the FAA and DHS must produce a coordinated airport counter‑UAS plan and conduct spectrum and suitability assessments before deploying approved detection systems in terminal airspace, and the bill authorizes discrete airport pilots to test mitigation capabilities.
The statute imposes training and certification standards to be issued within set timelines, requires repeated IG audits and semi‑annual briefings to congressional committees, mandates public annual reports on activities (with unclassified content where possible), and establishes retention and sharing rules for intercepted communications (including a 90‑day cap unless retention is needed for investigation or litigation). The bill also bars inclusion of counter‑UAS systems from certain “covered manufacturers” tied to specified foreign economic designations, while permitting narrow research exceptions.
Most authorities created or extended by the bill expire on October 1, 2030.
The Five Things You Need to Know
The FAA must publish minimum performance requirements for counter‑UAS detection and mitigation systems within 270 days of enactment.
DHS, DOJ, and FAA must maintain an internal approved list of counter‑UAS makes/models within one year, and the list may exclude systems from specified foreign‑affiliated manufacturers.
Applications by covered entities to acquire and operate approved detection systems must be approved or rejected within 45 days, or within 90 days when a law‑enforcement waiver is requested.
The law‑enforcement mitigation pilot initially includes up to five State or large local agencies (with staged expansion rules) and separate airport mitigation pilots for up to five covered airports.
Most authorities created or reauthorized by the bill terminate on October 1, 2030.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
DHS/DOJ counter‑UAS authority restructured and constrained
This section revises DHS’s Section 210G authority: DHS and DOJ may still seize, control, or mitigate UAS, but only after coordination with the FAA and only if the FAA determines the action will not adversely affect aviation safety, aircraft airworthiness, or national airspace operations—or if any identified adverse impacts can be mitigated. It also requires joint DHS/DOJ/FAA testing and creates a mandatory internal list of approved counter‑UAS systems. Practically, DHS can no longer act unilaterally in many operational scenarios without prior FAA safety clearance and listed equipment, forcing operational planning and pre‑deployment validation.
FAA counter‑UAS authority, Office, and performance regime
The bill recasts 44810 to make the FAA an operational actor and technical gatekeeper: the FAA may detect/identify/track and, under narrow and coordinated circumstances, disrupt, seize, or disable UAS to counter credible threats. It creates an Office of Counter‑UAS Activities, requires FAA minimum performance requirements and testing/validation regimes, and sets up a voluntary verified‑operator program to ease lawful access. The FAA also must consult FCC/NTIA about spectrum impacts and may exclude certain foreign‑affiliated systems from FAA acquisition or use. The provision centralizes aviation safety review before any mitigation technology is used in airspace that could affect flight operations.
Authorized limited detection by covered entities (applications and agreements)
DHS may authorize covered entities—owners of critical fixed sites, certain airports, and organizers/ security entities for covered events—to acquire and operate approved counter‑UAS detection systems (not mitigation) under an application/approval framework. Applications must justify the threat, include deployment plans, agreements with law enforcement (subject to waiver), and proof of operator certification. DHS enters a binding agreement specifying dates, locations, and safety conditions; DHS can revoke authorization for safety, training, privacy, or compliance failures. This creates a path for non‑federal actors to detect UAS under federal oversight while preserving FAA primacy over airspace safety.
Law‑enforcement mitigation pilot program and special multinational event authority
Once the FAA has validated mitigation systems, DHS must run a pilot enabling selected State and large local law enforcement agencies, in partnership with covered entities, to acquire and operate approved mitigation systems for authorized events/sites. The application package is robust (training proof, TFRs or equivalent airspace restrictions, state endorsement) and DHS must approve mitigation on a case‑by‑case basis until an initial evaluation period elapses. The pilot is deliberately limited (initially up to five agencies) with phased expansion rules, detailed post‑event reporting, recurring briefings to Congress, and an express pathway for temporary operations at major multinational sporting events with post‑event evaluations and possible transfers into the pilot program.
Airport planning, predeployment spectrum checks, and airport mitigation pilots
The FAA, DHS, and DOJ must produce a strategic airport counter‑UAS plan (annual updates required) covering roles, operational protocols, funding responsibilities, spectrum suitability, airport‑specific vulnerability assessments, and site plans developed with local stakeholders (including ATC representatives). The bill directs FAA deployments of approved detection systems to large hub and medium hub airports on prescribed timelines and establishes an airport mitigation pilot (up to five covered airports) with strict FAA/DHS authorization prior to any mitigation and required site‑specific coordination.
Enforcement, reporting, safety statements, and audits
The bill creates a new statutory prohibition (49 U.S.C. 44815) penalizing careless or reckless operation of detection/mitigation tech that interferes with safe aviation, elevating potential civil penalties for individuals and small businesses. It requires annual public reports summarizing detections/mitigations, intercepted communications, and civil‑liberties protections; semi‑annual classified/unclassified briefings to specified congressional committees; IG joint audits every 18 months; and mandates that small UAS manufacturers provide operators an FAA‑style safety statement at first activation. It also provides that certain administrative‑procedure requirements (5 U.S.C. 553/554) do not apply to selected determinations in the Act.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Large and medium hub airports and designated covered airports — receive FAA‑led planning, spectrum assessments, and a path to deploy approved detection systems to improve situational awareness and respond to persistent UAS disruptions under FAA oversight.
- Federal agencies (DHS, FAA, DOJ) — gain clearer interagency procedures, a dedicated FAA Office of Counter‑UAS Activities, a validated equipment list, and formal reporting/audit mechanisms that standardize operations and reduce ad‑hoc risk.
- Verified UAS operators and commercial UAS service providers — the voluntary verified‑operator program offers streamlined routine access to restricted airspace and creates a recognized compliance path that can reduce ad‑hoc denials and speed approvals.
- Manufacturers of vetted systems from non‑excluded countries — benefit from a formal FAA/DHS validation process, potential inclusion on the approved list, and clarified market channels for airports and government customers.
- State and large local law enforcement agencies participating in the pilot — gain a legal framework, training requirements, and federal oversight to lawfully deploy mitigation tools for high‑threat covered sites and events.
Who Bears the Cost
- DHS, FAA, and DOJ program offices — must resource testing, interagency coordination, the approved‑systems list, extensive briefings, IG audits, and ongoing oversight, increasing personnel and technical workloads.
- Airport operators and covered entities — face procurement, planning, and potential operational costs (spectrum assessments, site‑specific integration, and meeting FAA/DHS conditions), even where deployments are subject to appropriations.
- Certain foreign‑affiliated manufacturers (’covered manufacturers’) — may be excluded from the approved list, losing access to U.S. federal and some non‑federal customers; exclusion criteria are tied to trade and economic designations.
- Individual operators and small businesses operating detection/mitigation tech — face elevated civil penalty exposure if they operate systems recklessly or in a manner that interferes with safe aviation, because the bill broadens enforcement reach and sets high maximum penalties.
- State and local agencies in the pilot program — must meet training, certification, reporting, TFR or airspace‑restriction requirements, and may have deployment limited or revoked if they fail to comply, imposing administrative and operational burdens.
Key Issues
The Core Tension
The central dilemma is protecting people, critical infrastructure, and airports from dangerous or disruptive UAS operations while simultaneously preserving aviation safety, civilian communications networks, and civil liberties: the bill grants broader detection and mitigation pathways to non‑federal actors under federal oversight, but every gain in on‑the‑ground mitigation power increases the risk of unintended interference with aircraft, telecom networks, or privacy—forcing agencies to choose between speed/effectiveness and cautious, safety‑first deployment.
The bill attempts to thread competing objectives—enable real‑world mitigation capability for certain non‑federal actors while preserving FAA primacy over national airspace safety—but leaves several operational frictions. First, the FAA’s role as safety gatekeeper means many DHS/DOJ mitigation options will be contingent on FAA technical findings; where the FAA identifies an ‘‘adverse impact,’’ the statute requires mitigation steps but does not prescribe who pays for mitigation or how fast complex spectrum or airworthiness mitigations will be implemented.
Second, the approved‑systems list and exclusion of systems from ‘‘covered manufacturers’’ use trade and foreign‑policy criteria to shape procurement; that reduces supply chain risk but can shrink vendor choices and complicate interoperability and maintenance planning for airports and law enforcement. Third, the statute expands authorities for interception and access to communications from UAS control links while setting only limited retention rules (90 days absent investigation/litigation exceptions) and reporting obligations; operational practice will need careful policy and systems controls to avoid over‑collection, unauthorized disclosures, or chilling effects on lawful aviation data flows.
Implementation capacity is another unresolved pressure point. The bill puts many near‑term deadlines on agencies—performance standards, lists, training standards, application process timelines, and IG audits—yet contains multiple subject‑to‑appropriation provisions.
The pilot programs limit initial scale (five law‑enforcement agencies, five airport mitigation pilots) and permit expansion only after periodic reviews, which reduces immediate risk but may also slow lessons learned for broader rollout. Finally, the interplay between spectrum protection (FCC/NTIA consultations), civil‑liberties safeguards, and rapid response needs at major events creates real trade‑offs: minimizing radio disruption favors non‑kinetic detection methods, but the most effective mitigation options may entail radio or electronic actions that risk collateral communications disruption.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.