Referred to the Committee on the Judiciary, and in addition to the Committees on Transportation and Infrastructure, Homeland Security, and Armed Services, for a period to be subse…
This bill (the "LANDED Act") creates a federal framework to let State (and delegated local) law enforcement agencies acquire, deploy, operate, and train with federally approved counter‑UAS (drone detection and mitigation) systems, subject to an application and agreement process with the Department of Homeland Security (DHS), the Department of Justice (DOJ), and the Federal Aviation Administration (FAA). It authorizes certain mitigation actions (including detecting, warning, disrupting control signals, seizing or disabling UAS, and using reasonable force) when approved, requires post‑event reporting and FAA notification, and mandates coordination with the FCC/NTIA to limit harmful interference.
Privacy and civil‑liberties vs. security: Progressive is most concerned about warrantless interception and surveillance; conservatives emphasize law‑enforcement capability.
Relative to its intended legislative type, this bill is a substantive policy change that is reasonably well-structured: it defines goals and threats, identifies responsible federal actors, specifies an application and agreement framework, enumerates authorized counter-UAS actions, creates a grant program, requires deconfliction reporting, and mandates an Inspector General review.
This bill (the "LANDED Act") creates a federal framework to let State (and delegated local) law enforcement agencies acquire, deploy, operate, and train with federally approved counter‑UAS (drone detection and mitigation) systems, subject to an application and agreement process with the Department of Homeland Security (DHS), the Department of Justice (DOJ), and the Federal Aviation Administration (FAA).
It authorizes certain mitigation actions (including detecting, warning, disrupting control signals, seizing or disabling UAS, and using reasonable force) when approved, requires post‑event reporting and FAA notification, and mandates coordination with the FCC/NTIA to limit harmful interference.
The bill establishes a Counter‑UAS Security Grant Program to fund acquisitions and training, a mandatory non‑emergency deconfliction reporting database for agency drones, a rapid response process for emergencies, and an Inspector General review and report on UAS activity related to military and homeland security.
On substantive grounds the bill targets a concrete national security and public safety problem and includes procedural safeguards, grant funding, and interagency coordination that increase its buy‑in potential. However, it also authorizes intrusive technical measures (signal interception/jamming, seizure, destruction) that implicate aviation safety, communications infrastructure, privacy, and criminal law carve‑outs; those factors raise stakeholder and legal concerns that are likely to require edits, oversight guarantees, or funding limits before final enactment. The ultimate outcome depends heavily on negotiations with FAA/FCC/Defense, civil‑liberties and industry pushback, and how appropriations are handled.
Relative to its intended legislative type, this bill is a substantive policy change that is reasonably well-structured: it defines goals and threats, identifies responsible federal actors, specifies an application and agreement framework, enumerates authorized counter-UAS actions, creates a grant program, requires deconfliction reporting, and mandates an Inspector General review. However, it relies heavily on delegated agency rulemaking for technical and procedural specifics, provides minimal fiscal authorization language, and omits several detailed safeguards and programmatic accountability measures that would be proportionate to the scale and intrusiveness of the new authorities it grants.
Privacy and civil‑liberties vs. security: Progressive is most concerned about warrantless interception and surveillance; conservatives emphasize law‑enforcement capability.
These are examples from the analysis, not a ranked list of the most-affected groups.
Privacy and civil‑liberties vs. security: Progressive is most concerned about warrantless interception and surveillance; conservatives emphasize law‑enforcement capability.
A mainstream liberal would recognize the bill's goal of addressing dangerous or malicious drone activity that can threaten life, public safety, and critical infrastructure.
They would be concerned that the bill permits warrantless interception of communications used to control drones and broad disruptive actions that could interfere with civilian communications or invade privacy if not strictly limited.
They would also worry about the militarization of local police through acquisition of disabling weapons, and want stronger, explicit civil‑liberties protections, transparency, community oversight, and limits on use.
A pragmatic centrist would appreciate the bill's effort to provide a coordinated federal‑state framework to address dangerous UAS activity while preserving aviation safety and communications networks.
They would view the DHS/DOJ/FAA joint application, site‑specific airspace assessments, and FCC/NTIA consultations as sensible safeguards, but would seek clearer, binding standards for privacy, use‑of‑force, and operational transparency rather than vague delegations.
The centrist would favor the grant program and deconfliction database as practical tools, while pressing for oversight, measurable metrics of effectiveness, and clear funding offsets or appropriations.
A mainstream conservative would generally welcome stronger tools for state and local law enforcement to stop malicious or dangerous drones that threaten people, infrastructure, or national security, and would favor the grant funding and the delegation to states/localities.
They may be wary of excessive federal micromanagement but will view the application/agreement process as an acceptable way to ensure safety and avoid interference with national airspace.
Some conservatives could have residual concerns about the involvement of multiple federal agencies and potential bureaucratic delays, but would likely prioritize empowering local authorities to act quickly against credible threats.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
On substantive grounds the bill targets a concrete national security and public safety problem and includes procedural safeguards, grant funding, and interagency coordination that increase its buy‑in potential. However, it also authorizes intrusive technical measures (signal interception/jamming, seizure, destruction) that implicate aviation safety, communications infrastructure, privacy, and criminal law carve‑outs; those factors raise stakeholder and legal concerns that are likely to require edits, oversight guarantees, or funding limits before final enactment. The ultimate outcome depends heavily on negotiations with FAA/FCC/Defense, civil‑liberties and industry pushback, and how appropriations are handled.
The bill has not accumulated any surfaced votes yet.
Privacy and civil‑liberties vs. security: Progressive is most concerned about warrantless interception and surveillance; conservatives emph…
On substantive grounds the bill targets a concrete national security and public safety problem and includes procedural safeguards, grant fu…
Relative to its intended legislative type, this bill is a substantive policy change that is reasonably well-structured: it defines goals and threats, identifies responsible federal actors, specifies an application and a…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.