USCP Empowerment Act of 2025
- Sponsor
- Rep. Crane, Elijah [R-AZ-2]
- Committees
- Committee on House Administration (primary)
- Last action
- Jun 24, 2026
Bottom line
The bill expands the USCP's powers to counter drone threats around the Capitol, balancing enhanced security with civil liberties safeguards and inter-agency coordination.
What it actually does
This bill grants the United States Capitol Police (USCP) new authority to detect, identify, monitor, track, warn, disrupt, seize, and even destroy unmanned aircraft systems (UAS) that pose a credible threat to covered Capitol Police facilities or assets. It explicitly overrides certain existing federal laws related to aviation and electronic communications interception, while also establishing privacy protections and reporting requirements.
Proponents argue
Supporters argue that this legislation is crucial for enhancing the security of the Capitol Complex and its personnel against evolving threats posed by unmanned aircraft systems. They contend that existing laws do not adequately empower the USCP to respond effectively to such threats, and this bill provides necessary tools while including important privacy and oversight mechanisms.
Opponents contend
Critics might raise concerns about the broad authority granted to the USCP, particularly the ability to disrupt, seize, or destroy UAS, and the potential for unintended consequences on civilian aviation or privacy, despite the bill's stated protections. They may argue that such powers could be overused or lead to collateral damage.
The bill is relatively short and clearly structured, making it accessible for an informed reader to understand its core provisions within a reasonable timeframe.
Section 2(a)
Authorization for USCP to Mitigate UAS Threats
This section grants the Capitol Police Board the authority to take actions to mitigate credible threats from unmanned aircraft systems (UAS) to covered Capitol facilities or assets. It explicitly overrides several existing federal laws, including those related to aviation security (49 U.S.C. 46502) and electronic communications (18 U.S.C. 32, 1030, 1367, chapters 119, 206), to enable these actions.
Supporters argue
Proponents argue that this provision is essential for modernizing the USCP's capabilities to address specific and evolving security threats posed by drones, which current laws do not adequately cover. They emphasize the need for proactive measures to protect critical government infrastructure and personnel.
Critics contend
Opponents might contend that overriding existing federal laws, particularly those related to aviation and electronic communications, sets a dangerous precedent and could lead to unforeseen legal challenges or conflicts with other federal agencies' jurisdictions. They may question the necessity of such broad overrides.
Tradeoffs
This provision balances the urgent need for enhanced security against potential conflicts with established legal frameworks governing airspace and electronic privacy.
Section 2(b)(1)
Specific Authorized Actions Against UAS
This subsection details the specific actions the USCP is authorized to take against threatening UAS. These include detecting, identifying, monitoring, and tracking the UAS (even by intercepting communications), warning the operator, disrupting control of the UAS, seizing or exercising control over it, confiscating it, and using reasonable force to disable, damage, or destroy it.
Section 2(e)
Privacy Protection Requirements
This section mandates that regulations or guidance for implementing the UAS authority must ensure privacy protections. It requires that interception of communications is consistent with the First and Fourth Amendments and federal law, limited to what's necessary, records are maintained for no more than 180 days (unless for investigation or security), and disclosure outside USCP is restricted to specific legal or enforcement purposes. It also allows sharing of threat information (excluding communications) with state/local agencies.
Section 2(f)
Congressional Reporting Requirements
This subsection requires the Chief of the Capitol Police to submit a written report to appropriate congressional committees every six months. The report must detail activities under this section, including policies to mitigate impacts to the National Airspace System, instances of actions taken (especially those causing harm), privacy and civil liberties guidance, options considered to mitigate airspace impacts, instances of communication retention beyond 180 days or external sharing, public outreach efforts, and descriptions of new technology deployed.
Section 2(h)
Termination of Authority
This section states that the authority granted to the USCP under this Act, specifically concerning areas described in section 9A(a) of the 1946 Capitol Grounds Act (2 U.S.C. 1966(a)) as directed by the Capitol Police Board, will terminate on the date identified in section 210G(i) of the Homeland Security Act of 2002 (6 U.S.C. 124n). This links the USCP's authority to an existing sunset clause for similar federal UAS mitigation programs.
The bill explicitly overrides several existing federal laws (49 U.S.C. 46502, 18 U.S.C. 32, 1030, 1367, chapters 119 and 206) to grant the USCP its new UAS mitigation authority.
Section 2(a)
Why it matters:This is standard legislative practice for establishing new authority that conflicts with or expands upon existing statutes. It's not necessarily evasive but requires legal expertise to fully grasp.
Case for: Proponents argue that these overrides are absolutely necessary because existing laws, particularly those governing aviation and electronic communications, were not designed to address the unique and rapidly evolving threat posed by malicious drones. Without these explicit overrides, the USCP would be legally constrained from taking effective action.
Case against: Critics might contend that such broad overrides of established federal law, especially those related to privacy (Chapter 119, Wire and Electronic Communications Interception and Interruption) and computer fraud (18 U.S.C. 1030), should be approached with extreme caution. They could argue that it creates a carve-out that might be difficult to manage or could set a precedent for other agencies seeking similar broad exemptions.
Estimated impact: Significant expansion of USCP's legal operating space, potentially impacting federal aviation regulations and electronic privacy laws within the Capitol complex.
The authority is granted to mitigate a 'credible threat, as defined by the Capitol Police Board.'
Section 2(a)
Why it matters:This is a common legislative practice to provide agencies with flexibility to adapt to evolving threats without requiring statutory amendments for every change in threat assessment. It could also be seen as delegating significant power without explicit legislative guidance.
Case for: Proponents argue that allowing the Capitol Police Board to define 'credible threat' provides necessary operational flexibility. They contend that security threats evolve rapidly, and a static statutory definition would quickly become outdated, hindering the USCP's ability to respond effectively to new tactics or technologies.
Case against: Critics might argue that delegating the definition of 'credible threat' to the Capitol Police Board without further legislative guidance creates a potential for arbitrary or overly broad interpretations. They could contend that such a critical trigger for potentially forceful actions should have a clearer, more transparent, and perhaps statutorily defined standard to ensure accountability and prevent overreach.
Estimated impact: The operational scope and frequency of USCP interventions against UAS will be directly shaped by the internal policies of the Capitol Police Board.