S. 1250 (119th)Bill Overview

SHIELD U Act

Transportation and Public Works|Transportation and Public Works
Sponsor
Cosponsors
Support
Republican
Introduced
Apr 2, 2025
Discussions
Bill Text
Current stageCommittee

Read twice and referred to the Committee on Commerce, Science, and Transportation.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief

The bill authorizes federal, State, local, and airport law enforcement to detect, identify, mitigate, seize, or disable unmanned aircraft/systems (UAS) on commercial airport property and within State/local jurisdictions.

It creates procedural requirements: airport task forces and tactical response plans, consultation with the FCC and NTIA for non‑kinetic (electronic/jamming) equipment, FAA coordination and interim airspace notification, annual OMB vendor/equipment lists, contracting authority for certain federal agencies, and training requirements.

The bill amends communications statutes to carve out exceptions allowing use of covered equipment (including jamming/interception) in consultation with the FCC for UAS threats.

Passage45/100

Practical security goals and detailed safeguards help, but high controversy over jamming/interception and aviation safety/legal risks lower passage odds.

CredibilityPartially aligned

Relative to its intended legislative type, this bill is a clearly drafted substantive policy change that provides detailed definitions, delegated authorities, interagency coordination requirements, and implementation timelines. It integrates tightly with existing statutes through explicit amendments and prescribes concrete operational procedures for testing, notification, and procurement.

Contention70/100

Privacy and Fourth Amendment concerns versus security/tool availability.

02 · What it does

Who stands to gain, and who may push back.

Who this appears to help vs burden50% / 50%
Targeted stakeholdersPermitting process
Likely helped
  • Targeted stakeholdersClarifies legal authority for law enforcement to mitigate hazardous or hostile drone operations near airports.
  • Targeted stakeholdersRequires coordinated tactical plans and FAA notification, improving operational coordination and airspace deconfliction.
  • Targeted stakeholdersMakes Counter-UAS equipment eligible for airport funding, enabling procurement and infrastructure upgrades at airports.
Likely burdened
  • Permitting processPermits interception and disruption of control communications, raising significant Fourth Amendment and privacy concern…
  • Targeted stakeholdersAllows jamming and disabling drones, risking unintended interference with civilian communications and critical infrastr…
  • Targeted stakeholdersDisabling or destroying drones near airports could create debris and aviation safety hazards for manned aircraft.
03 · Why people split

Why the argument around this bill splits.

Privacy and Fourth Amendment concerns versus security/tool availability.
Progressive30%

Likely concerned that the bill grants broad surveillance and jamming powers without explicit judicial oversight or strong privacy safeguards.

Accepts the safety rationale for airports, but worries about Fourth Amendment, wire‑interception, and civil‑liberties risks unless stronger limits are added.

Likely resistant
Centrist55%

Views the bill as a pragmatic effort to close gaps in local and airport UAS response while establishing coordination mechanisms.

Sees value in task forces, FAA notification, and FCC/NTIA consultation but wants clearer guardrails on civil liberties, safety, and costs.

Split reaction
Conservative85%

Likely supportive because the bill empowers local and airport law enforcement to counter dangerous drones, includes exceptions to jamming rules, and emphasizes local control and operational authority.

Sees it as strengthening security and property protection.

Leans supportive
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood45/100

Practical security goals and detailed safeguards help, but high controversy over jamming/interception and aviation safety/legal risks lower passage odds.

Scope and complexity
52%
Scopemoderate
86%
Complexityhigh
Why this could stall
  • No cost estimate or formal CBO score included
  • FAA technical safety risk assessments absent
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Privacy and Fourth Amendment concerns versus security/tool availability.

Practical security goals and detailed safeguards help, but high controversy over jamming/interception and aviation safety/legal risks lower…

Unlocked analysis

Relative to its intended legislative type, this bill is a clearly drafted substantive policy change that provides detailed definitions, delegated authorities, interagency coordination requirements, and implementation ti…

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis