SHIELD U Act
- Bill Number
- S. 1250
- Origin Chamber
- Senate
- Congress
- 119th Congress, Session 1
- Policy Area
- Transportation and Public Works
- Status
- Introduced
- Latest Action
- 2025-04-02: Read twice and referred to the Committee on Commerce, Science, and Transportation.
- Last Updated
- 2026-02-26T20:07:41Z
AI-Generated Summary
Purpose of the Legislation
The SHIELD U Act (S. 1250) aims to enhance aviation and public safety by authorizing targeted actions against unauthorized drones (unmanned aircraft systems, or UAS) that pose threats, particularly near commercial airports. It expands permissions for detection, disruption, and mitigation of drone risks while ensuring coordination among federal, state, local, and private entities to minimize interference with legitimate air traffic and communications.
Key Provisions
- Definitions (Sec. 2): Establishes clear terms, such as "Counter-UAS activities" (e.g., detecting, tracking, warning, disrupting control, seizing, or using force against drones without owner consent); "commercial service airport" (public airports with scheduled passenger service, including surrounding airspace for safe takeoffs and landings); "non-kinetic equipment" (tools that interfere with drone communications electronically, without physical force); and "threats posed by UAS" (unauthorized drone actions risking human harm or severe economic damage to airports or state/local property).
- Counter-UAS at Airports (Sec. 3):
- Authorizes the Department of Homeland Security (DHS), state/local law enforcement, and airport police to perform Counter-UAS activities on airport property to address safety/security threats, in line with the Fourth Amendment (which protects against unreasonable searches and seizures).
- Requires airport operator consent and consultation for all activities; testing of equipment must involve the Federal Communications Commission (FCC) and National Telecommunications and Information Administration (NTIA) for non-kinetic tools.
- Mandates task forces at each commercial airport to update emergency plans with tactical response strategies, including threat levels, standard procedures to limit collateral damage, role assignments, and designation of first responders (state/local or airport law enforcement, coordinated with DHS).
- Makes Counter-UAS equipment purchases eligible for federal Airport Improvement Program funding.
- Requires the Federal Aviation Administration (FAA) and Transportation Security Administration (TSA), in collaboration with airports, to issue and annually update best practices guidance for these activities.
- Counter-UAS Off Airport Property (Sec. 4):
- Permits state and local law enforcement to conduct Counter-UAS activities within their jurisdictions to mitigate drone threats.
- Allows states, localities, and private entities to set up testing areas for equipment, with FAA cooperation unless it endangers airspace safety; non-kinetic testing requires FCC/NTIA consultation.
- Establishes notification processes for non-kinetic equipment use, with FCC/NTIA designating offices for consultations and follow-ups within set timelines (30 days for assignments, 180 days for processes).
- Amends the FAA Reauthorization Act of 2018 to require FAA coordination with state/local law enforcement on Counter-UAS actions and create collaboration processes.
- Directs the FAA to implement an interim notification plan for active threats, including warnings to manned/unmanned aircraft operators, which sunsets upon full UAS traffic management system rollout.
- Contracts and Vendor Support (Sec. 5): Authorizes DHS, Department of Defense (DOD), Department of Justice (DOJ), and Department of Energy to contract for Counter-UAS under existing authorities; updates the Federal Acquisition Regulation within 180 days. The Office of Management and Budget (OMB) must annually publish lists of eligible vendors and recommended equipment, based on risk assessments, for state/local use.
- Training Enhancements (Sec. 6): Amends the Homeland Security Act to require DHS to develop and provide training on Counter-UAS tactics (kinetic and non-kinetic), detection, and mitigation, available to federal, state, local, tribal, territorial, and private security agencies.
- Jamming Technology Exceptions (Sec. 7): Amends the Communications Act of 1934 to exempt state/local law enforcement and airport police from restrictions on radio interference when using approved equipment (in consultation with FCC) to counter drone threats, defining "covered equipment" as tools for intercepting or disrupting drone control signals.
- Preservation of Police Powers (Sec. 8): Clarifies that the Act does not limit state/local governments' traditional authority to address imminent public health/safety threats.
Significant Changes to Existing Law
- Expands Authorizations: Builds on prior laws (e.g., FAA Reauthorization Act, Homeland Security Act) by granting state/local entities and airports explicit Counter-UAS powers previously limited to federal agencies, including off-airport jurisdictions.
- Communications Law Amendments: Creates exceptions to longstanding prohibitions on signal jamming and device interference (under 47 U.S.C. §§ 301, 302, 333), allowing non-kinetic disruption of drone controls without FCC prior approval in emergencies.
- Funding and Planning: Adds Counter-UAS equipment to eligible federal airport grants and mandates integrated tactical plans in airport emergency protocols, streamlining what were previously fragmented responses.
- Coordination Mandates: Introduces required consultations with FCC/NTIA and FAA processes for notifications, reducing regulatory barriers while ensuring oversight.
Potential Impacts
- Government Agencies: Enhances capabilities for DHS, FAA, TSA, FCC, NTIA, DOD, DOJ, and state/local law enforcement to respond to drone threats, potentially reducing response times and costs through shared training, equipment lists, and testing. Federal agencies gain streamlined contracting, while locals benefit from federal guidance and funding access.
- Citizens and Airports: Improves safety at commercial airports (serving millions of passengers) by mitigating drone risks to flights, people, and infrastructure, potentially preventing accidents or disruptions. Citizens in states/localities may see better protection from rogue drones, but could face temporary airspace restrictions during responses.
- International Relations: Minimal direct impact, though it may influence global drone standards by demonstrating U.S. commitment to secure airspace, potentially affecting foreign air carriers operating in U.S. airports.
- Broader Economy: Supports aviation industry stability (e.g., fewer flight delays from drone incursions) and enables private sector testing, fostering innovation in counter-drone tech without significant new burdens.
Main Stakeholders Affected
- Federal Agencies: DHS, FAA, TSA, FCC, NTIA, DOD, DOJ, Department of Energy, and OMB (for oversight, training, and procurement).
- State, Local, and Airport Entities: Law enforcement, airport operators/directors, and localities (gaining new authorities and responsibilities for plans/testing).
- Industry and Private Sector: Covered air carriers (e.g., airlines), general aviation operators, telecommunications/broadband providers, drone manufacturers/operators, and private security firms (involved in coordination, testing, and equipment use).
- Public and Users: Drone hobbyists, commercial UAS operators, and travelers (affected by response activities but protected from threats).
Notable Legal, Constitutional, or Political Implications
- Constitutional Safeguards: Explicitly requires all activities to comply with the Fourth Amendment, emphasizing reasonable, consent-based, and narrowly tailored actions to avoid privacy invasions or excessive force.
- Federalism Balance: Empowers states/localities without overriding federal airspace authority (FAA retains veto on unsafe testing), preserving traditional police powers while promoting coordinated responses.
- Regulatory Shifts: Eases telecommunications restrictions for security purposes, potentially setting precedents for emergency tech use, but mandates consultations to prevent spectrum interference or unintended disruptions to legitimate communications.
- Political Considerations: Addresses rising drone threats (e.g., near airports or critical infrastructure) amid growing UAS adoption, likely garnering bipartisan support for safety but raising debates on civil liberties, innovation stifling, or overreach in jamming permissions; no partisan bias evident in the bill text.
This summary was generated by AI and may contain inaccuracies. Refer to the official source document for the authoritative text.
Sponsor
Recent Actions
- 2025-04-02: Read twice and referred to the Committee on Commerce, Science, and Transportation.
- 2025-04-02: Introduced in Senate
Bill Versions
- Stopping Harmful Incidents to Enforce Lawful Drone Use Act — issued 2025-04-02 — PDF (27 pages)