The SHIELD U Act would create a nationwide framework to detect, identify, and mitigate drone (unmanned aircraft) threats at and around commercial service airports, and also allow for similar counter-drone activities off airport property in certain cases. The bill authorizes the Department of Homeland Security, state and local law enforcement, and airport law enforcement to conduct Counter-UAS activities to protect airport safety and security. It also establishes a process for testing, procurement, training, and coordination with the Federal Communications Commission (FCC), National Telecommunications and Information Administration (NTIA), and the Federal Aviation Administration (FAA). The act seeks to balance security needs with civil liberties, by requiring airport operator consent for on-airport activities, creating standardized emergency plans, and ensuring coordination across federal, state, and local agencies. It also creates pathways for federal contracting for Counter-UAS gear and requires regular updates on best practices. In short, if enacted, SHIELD U would enable a structured, multi-agency approach to drone threats near airports and other areas, including specialized equipment, training, testing, and interagency coordination, while trying to protect privacy and keep traditional police powers intact.
Key Points
- 1On-airport Counter-UAS authority with consent: DHS, state/local law enforcement, and the airport’s own law enforcement can conduct Counter-UAS activities on commercial service airport property to detect, identify, and mitigate drone threats, but only with hospital-consented coordination with the airport operator.
- 2Off-airport testing and authority: State and local authorities and private entities may establish testing areas for Counter-UAS equipment off airport property, subject to safety considerations for the national airspace and coordination with the FAA.
- 3Non-kinetic equipment and FCC/NTIA coordination: Use of non-kinetic counter-drone tools (like jamming or intercepting communications) requires consultation with the FCC and NTIA, a formal notification process for approved designees to report usage, and designated offices to handle notifications; efforts should be coordinated to avoid duplicative requirements.
- 4Tactical Response Plans and best practices: Airports must form a task force to develop or modify emergency action plans for drone threats, defining threat levels, standard operating procedures, roles, and first responders, with an emphasis on minimizing collateral damage. FAA/Transportation and other agencies must be involved. FAA and TSA will publish and update best-practice guidance for Counter-UAS use.
- 5Procurement, training, and funding: The bill authorizes certain federal departments to contract for Counter-UAS activities (DOD, DHS, DOJ, DOE) and requires the Federal Acquisition Regulation (FAR) to be updated to implement this authority. It also requires annual lists of eligible vendors and recommended equipment, plus annual risk assessments. Federal training programs would include Counter-UAS curricula for federal, state, local, tribal, and private sector security personnel.