Counter-UAS Authority Security, Safety, and Reauthorization Act
Sponsored By: Representative Garbarino
In Committee
Summary
Expands federal authority to detect, control, and disable unmanned aircraft systems (UAS). It would set FAA performance standards, create approval pathways for airports and critical sites to run approved detection systems, and stand up a time‑limited pilot letting State and local law enforcement operate mitigation systems under strict conditions.
Show full summary
- Airports and the national airspace would face new FAA powers to detect, identify, seize, disrupt, or destroy UAS and gain an Office of Counter‑UAS Activities to coordinate safety, testing, and approvals. The bill would require FAA site‑specific determinations and an airspace hazard testing program at five airports and other locations.
- Covered entities and State or local law enforcement would gain application pathways to deploy approved detection systems and mitigation tools. DHS must approve or reject applications within 45 days or 90 days with a waiver and the initial mitigation pilot would include up to five participating agencies.
- Manufacturers and operators would face new duties and limits. Small UAS makers must provide a safety statement at first activation that operators must acknowledge, and the bill restricts use of systems from certain foreign "covered manufacturers." Oversight includes joint Inspector General audits every 18 months and semiannual briefings to Congress.
Your PRIA Score
Personalized for You
How does this bill affect your finances?
Sign up for a PRIA Policy Scan to see your personalized alignment score for this bill and every other piece of legislation we track. We analyze your financial profile against policy provisions to show you exactly what matters to your wallet.
Bill Overview
Analyzed Economic Effects
9 provisions identified: 6 benefits, 1 costs, 2 mixed.
Drone detection at major airports
If enacted, the FAA would test and deploy drone detection and mitigation at major airports. Up to 5 covered airports would get mitigation pilots within 2 years after the performance rules publish. Detection would roll out at large hubs within 30 months, at least 3 high-cargo airports within 12 months after guidance, and all medium hubs within 4 years. Before deployment, the FAA must check site spectrum and consult FCC and NTIA. Using mitigation would need both DHS and FAA approval, with case-by-case emergency options.
FAA counter-drone standards and office
If enacted, the FAA must set minimum performance rules for counter-drone systems within 270 days and an airport plan within 1 year, with yearly updates. An FAA Office of Counter-UAS Activities would be created to lead planning and interagency work. The FAA could not hand off these new authorities to another agency, and could suspend covered-entity actions that threaten airspace safety, with notice to Congress within 48 hours.
Let critical sites deploy drone detectors
If enacted, DHS would set up an application within 180 days so critical sites and certain events can run approved drone detection systems. Applicants would need to show a credible threat, a deployment plan, a law-enforcement agreement (or a waiver), and training. DHS must decide in 45 days (90 days if a waiver is sought), can authorize some pre-existing systems, and can revoke approvals for safety, privacy, or training failures. This authority would end on October 1, 2030.
Pilot: police can disable risky drones
If enacted, DHS would run a pilot, funded by Congress, that lets State and large local police use approved systems to mitigate risky drones for covered sites. The pilot would start within 60 days after the first system meets FAA performance rules, begin with up to 5 agencies (max 4 sites each), and require case-by-case federal approvals for the first 270 days. Expansion could add 10 agencies no sooner than 18 months after deployment, then 12 more after another 18 months, if trained staff are available. A covered local agency would serve an area of at least 650,000 people, systems must meet 49 U.S.C. 44810(e), and the pilot ends October 1, 2030. DHS must brief Congress within 6 months and every 6 months; each missed briefing or report would delay pilot expansion by 6 months.
Time-limited powers to stop dangerous drones
If enacted, the FAA would be able to detect, track, seize, disable, or destroy drones when needed to protect the national airspace or for testing. It could intercept drone-control communications only as allowed by the Constitution and federal law, and only as needed for the action. Records from interceptions would be destroyed right away unless needed for an investigation or otherwise allowed by law. These expanded powers would end on October 1, 2030.
More public reports on drone defenses
If enacted, DHS would post an unclassified report within 180 days and every year on counter-drone actions and any communications interceptions. The FAA would brief Congress at least every 6 months and start notifying committees about new authorizations 180 days after enactment. Inspectors General from DOT, DHS, and DOJ would audit the program within 18 months and every 18 months, with reports due to Congress within 90 days of each audit.
Higher fines for rule violators
If enacted, individuals and small businesses who break new detection or mitigation rules could face a higher maximum civil fine, equal to the cap used for larger entities.
Limits on buying some foreign systems
If enacted, the FAA could not acquire or approve counter-drone systems from certain foreign-tied covered manufacturers, unless the Transportation Secretary allows it for safety. No Federal agency could force an airport to buy or run these systems. Careless or reckless operation that harms airport safety would be banned, and the FAA could act on violations.
Safety notice when activating small drones
If enacted, small-drone makers would have to show you a safety statement at first activation and collect your electronic OK. The statement would explain key laws, flight restrictions, how to check if a flight is legal, safety tips, and penalties. The FAA must publish an example within 120 days and update it within 18 months and then each year.
Sponsors & CoSponsors
Sponsor
Garbarino
NY • R
Cosponsors
Thompson (MS)
MS • D
Sponsored 8/29/2025
Graves
MO • R
Sponsored 8/29/2025
Larsen (WA)
WA • D
Sponsored 8/29/2025
Raskin
MD • D
Sponsored 8/29/2025
Gray
CA • D
Sponsored 10/21/2025
Van Drew
NJ • R
Sponsored 3/3/2026
Roll Call Votes
No roll call votes available for this bill.
View on Congress.govTake It Personal
Get Your Personalized Policy View
Start a Free Government Policy Watch to see how policy affects your household, then upgrade to PRIA Full Coverage for year-round monitoring.
Already have an account? Sign in