The USCP Empowerment Act of 2025 authorizes the Capitol Police Board to take a suite of counter‑UAS actions—ranging from electronic detection and interception of control signals to seizure and destruction—against unmanned aircraft systems that the Board determines pose a credible threat to Capitol facilities or assets. The bill carves out those activities from several federal statutes (including parts of title 18 and title 49), requires coordination with the Secretary of Transportation and the FAA, and makes seized UAS subject to forfeiture.
The law builds in procedural guardrails: it allows research, testing, and training before operational use; sets privacy and records‑retention limits (generally 180 days); requires semiannual unclassified reports to Congress (with a classified annex option) describing incidents, privacy protections, and airspace impact mitigation; and limits the program’s duration for certain assets. For compliance officers and aviation professionals, the bill creates a narrowly focused but operationally broad counter‑UAS authority with mandatory FAA coordination and explicit privacy and reporting obligations.
At a Glance
What It Does
The bill authorizes the Capitol Police Board to permit USCP personnel to detect, intercept communications used to control a drone, warn operators, disrupt or seize control, confiscate or destroy a drone, and conduct pre‑deployment testing and training. It expressly suspends certain federal criminal and aviation statutes to allow those actions when the Board identifies a credible threat to covered facilities.
Who It Affects
Primary actors are the United States Capitol Police and the Capitol Police Board, the Department of Transportation and FAA for coordination on airspace safety, drone operators whose devices operate near covered Capitol facilities, and federal oversight committees receiving mandated reports. Defense and federal law enforcement agencies may receive threat information in support roles.
Why It Matters
This bill formalizes a localized counter‑UAS program with statutory carve‑outs that would otherwise limit intercepting or jamming signals and handling seized equipment. It creates the practical and legal template for non‑military, law‑enforcement counter‑UAS operations on critical federal grounds while forcing interaction with the FAA over airspace safety and public transparency through recurring reporting.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
At its core, the bill gives the Capitol Police Board the power to decide when an unmanned aircraft system presents a ‘‘credible threat’’ to specified Capitol facilities and, when it does, to authorize USCP personnel to neutralize that threat using a wide range of tools. Those tools include detecting and tracking a drone in real time, intercepting or otherwise accessing the communications used to control it, warning the operator, interrupting or disrupting the control signals, taking physical control of the device, seizing it, and, if necessary, using reasonable force to disable or destroy it.
The statute explicitly permits these actions even where other federal statutes might otherwise prohibit interception or signal interference.
The bill does not leave the Capitol Police to act in isolation. It requires the Capitol Police Board to develop its operational approach in coordination with the Secretary of Transportation and to coordinate with the FAA whenever an action could affect aviation safety, civil aviation operations, aircraft airworthiness, or use of airspace.
The Board may also run research, testing, and training on equipment before operational deployment, which creates a defined pathway for evaluating counter‑UAS technologies and minimizing unintended impacts.Privacy and limits on retention are front‑loaded into the statute: guidance and regulations must ensure compliance with the First and Fourth Amendments and federal law; communications collected from a drone may be intercepted only to the extent necessary for a response; records are to be retained no longer than 180 days except for specific investigatory, operational, or legal reasons; and disclosures outside the USCP are tightly circumscribed to prosecutorial, defense, or required‑by‑law circumstances. Finally, the Act forces semiannual reporting to Congress—unclassified with an optional classified annex—covering incidents, harms, privacy practices, and measures taken to mitigate airspace impacts, and it specifies that authority over certain assets will terminate on a date tied to an existing Homeland Security Act provision.
The Five Things You Need to Know
The bill creates an explicit statutory exception to specified provisions of title 18 and title 49, allowing the Capitol Police Board to authorize intercepting or disrupting drone control signals that would otherwise implicate federal wire‑interception and aviation statutes.
Authorized operational tools include intercepting or accessing communications used to control a drone, active or passive warnings to operators, electronic disruption of control signals, seizure or physical takeover of a drone, forfeiture of seized drones, and the use of reasonable force to disable or destroy a drone.
The Capitol Police Board must develop its counter‑UAS actions in coordination with the Secretary of Transportation and coordinate with the FAA when operations might affect aviation safety, airworthiness, or civil aviation activities.
Privacy safeguards require that intercepted communications be limited to what’s necessary, that records be retained no more than 180 days unless needed for prosecution, operations, or litigation, and that disclosures outside USCP be narrowly limited to law enforcement, defense, or legal obligations.
The Chief of Capitol Police (or designee) must report to designated congressional committees within six months of enactment and every six months thereafter in unclassified form (with an optional classified annex), describing incidents, harms, privacy and civil liberties protections, airspace impact mitigation, interagency coordination, and newly deployed technologies.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Provides the Act’s name: ‘‘USCP Empowerment Act of 2025.’' This is purely stylistic but signals the bill’s narrow, operational focus on empowering the United States Capitol Police to address unmanned aircraft threats.
Board‑level authorization for counter‑UAS actions
Grants the Capitol Police Board the discretionary authority to permit USCP personnel whose duties include protection or security to carry out specified counter‑UAS measures when the Board determines there is a credible threat to covered facilities. The practical implication is that the Board, not individual officers, defines the threshold for action and controls program scope and deployment decisions.
Enumerated counter‑UAS tools (detection to destruction)
Lists the operational authorities: detect/track (including intercepting control communications), warn operators (passive or active), disrupt control signals, seize or take control, confiscate, and use reasonable force to disable/destroy. This is a broad menu that includes activities that can implicate wire‑interception rules and radio‑spectrum restrictions; the bill’s explicit language is intended to clear legal obstacles to those activities within covered areas.
Mandatory DOT/FAA coordination and pre‑deployment testing
Requires the Board to develop operations in coordination with the Secretary of Transportation and to coordinate with the FAA whenever aviation safety, airworthiness, or airspace use might be affected; it also authorizes pre‑use research, testing, training, and evaluation of equipment. That establishes a formal interface with aviation authorities and preserves a testing window to evaluate counter‑UAS technologies before live use.
Seized unmanned aircraft systems may be forfeited to the United States
Declares that any UAS seized under the authority is subject to forfeiture. This converts seizure into a potential permanent loss for operators and creates a downstream evidentiary and property‑management task for USCP and DOJ if forfeiture is pursued.
Regulatory authority plus statutory privacy and disclosure limits
Gives the Board authority to issue regulations and guidance (in coordination with DOT), and sets statutory privacy rules: interceptions must be consistent with constitutional and federal law, collection limited to necessary communications, retention capped at 180 days absent specific needs, and disclosure outside USCP narrowly authorized for investigations, prosecutorial needs, defense/military support, or as required by law. This provision tries to balance operational needs with civil liberties and records management.
Semiannual congressional reporting, construction limits, termination, and definitions
Imposes semiannual reporting to House and Senate committees (unclassified with optional classified annex) including incident descriptions, harms, privacy safeguards, airspace mitigation steps, and new technologies deployed. It also contains rules of construction preserving DOT/FAA authorities, limits the program’s scope to the statutory program only, ties termination for certain assets to a date in the Homeland Security Act, and supplies definitions for covered facilities, communications terms, and UAS.
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
- United States Capitol Police — Gains statutory cover to operate counter‑UAS tools that could otherwise implicate wire‑interception and spectrum‑interference prohibitions, enabling faster on‑site responses to drone threats and a legal framework for training and equipment testing.
- Members of Congress and congressional staff — Stand to benefit from increased protection of the Capitol Buildings, Grounds, and other designated areas and from formal reporting that documents threats and mitigation steps.
- Federal aviation and security partners (DOT, FAA, federal law enforcement, DOD when applicable) — Benefit from an explicitly coordinated mechanism that channels threat information and creates predictable interfaces for resolving airspace safety impacts and joint responses.
Who Bears the Cost
- Drone operators and hobbyists near the Capitol — Face risk of having devices seized, forfeited, disabled, or destroyed; they also face evidentiary and legal exposure if a Board‑declared credible threat is invoked.
- United States Capitol Police — Must absorb operational costs, procure and test counter‑UAS technologies, establish compliance with privacy limits, maintain records, and respond to recurring congressional oversight, all of which impose administrative and fiscal burdens.
- Federal aviation authorities (FAA/DOT) — Incur coordination and safety review burdens and may need to issue operational mitigations or temporary airspace adjustments; they also shoulder risk if USCP actions affect airworthiness or civilian flights and require mitigation measures.
- Civil liberties and privacy advocates — Bear the downstream burden of monitoring, litigating, and advocating where they view interceptions or retention policies as overbroad; increased USCP authority can shift enforcement and oversight costs onto advocacy and judicial systems.
- State and local law enforcement partners — May receive shared threat information and be drawn into joint operations or investigations, increasing their operational and legal obligations without additional federal funding.
Key Issues
The Core Tension
The bill confronts the classic trade‑off between rapid, localized security authority and the need to preserve airspace safety and constitutional protections: empowering USCP to intercept and disrupt drone operations increases the Capitol’s immediate security options but risks degrading broader aviation safety, interfering with civilian communications, and creating privacy and oversight gaps if thresholds and post‑action review are not tightly constrained.
The bill resolves one legal barrier—statutory prohibitions on intercepting communications and interfering with radio signals—by expressly authorizing those acts in covered circumstances. That fix creates new questions about operational limits and oversight.
The statute leaves ‘‘credible threat’’ undefined within the text itself and vests threshold judgment in the Capitol Police Board, creating a risk of subjectivity: different boards or future leadership could set markedly different thresholds for invoking sweeping counter‑UAS powers. The coordination requirement with DOT/FAA helps, but the pace of an urgent response and the FAA’s air‑safety mandate can pull in opposite directions when seconds matter.
Operationally, the bill permits signal disruption and jamming‑type activities that can have collateral effects on nearby civilian systems and aircraft; even with FAA coordination, mitigating those downstream impacts requires real‑time airspace management and clear technical limits on interference. The statutory privacy constraints (purpose‑limited interceptions, 180‑day retention cap, narrow disclosure rules) provide boundaries but leave open practical questions about how metadata and mixed‑content captures are handled, who audits compliance, and when a retention extension is justified.
Finally, the reporting regime improves transparency but allows an accompanying classified annex; crucial details about harms or near‑misses could end up hidden from public view while still forming the basis for policy and procurement decisions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.