QuorumCivic. Hidden in plain sight Get the app
Bill intelligence

New drone-surveillance power for police — with no public oversight list

S. 663 — DEFENSE Act · Filed by Tom Cotton (R-AR) · 1 cosponsor · Introduced Feb 20, 2025 · Referred to committee

45%
Transparency
Typical bill: 85%
35/100
Hidden-provision risk
Typical bill: 15/100
High concernLaw Enforcement Drone Countermeasure…

Your members of Congress

Enter a ZIP to see where your representative and both senators stood on this bill.

Looked up on this device — your ZIP is never stored on our servers.

What it does

This bill amends federal law to allow the Department of Homeland Security or Department of Justice to deputize state and local police officers to use drone-detection and counter-drone equipment at major public events and locations with flight restrictions (like stadiums, airports, and large gatherings). Officers must complete federal training, and the equipment used must be on an approved federal list maintained by DHS, DOJ, FAA, FCC, and NTIA.

Why we flagged it

The bill's core function is to expand federal authority to deputize state/local officers to use drone-detection and counter-drone equipment at protected events. While framed as security, the mechanism is regulatory delegation with minimal guardrails.

What the text implies

  • The bill does not define what 'counter' measures are authorized — it only specifies detection, identification, monitoring, or tracking. This ambiguity may permit jamming, spoofing, or destruction of civilian drones without explicit statutory language.
  • State and local officers gain federal deputization authority, but oversight is delegated to federal agencies 'in coordination' — a vague standard that may not prevent misuse or ensure accountability to the public.
  • The 'authorized equipment' list is maintained by five federal agencies but the bill does not require public disclosure of that list, meaning citizens cannot know what surveillance or counter-drone tools are being deployed in their communities.
  • The bill applies to 'eligible large public gatherings' at FAA discretion, which is undefined and could expand surveillance authority to protests, political rallies, or other assemblies without legislative specificity.
  • No explicit prohibition on data retention, sharing, or use of drone-detection information for purposes beyond the immediate event — potential for mission creep into broader surveillance.

Who it affects

The bill may enhance security at major public events by giving law enforcement tools to detect and counter unauthorized drones, which is a legitimate public safety interest. However, it creates new surveillance and enforcement authority at the state/local level with minimal transparency requirements, and the bill does not clearly define what 'counter' measures are permitted, raising concerns about privacy, due process, and potential overreach.

Who stands to gain

  • drone-detection technology manufacturers
  • counter-UAS equipment vendors
  • defense contractors specializing in airspace security
  • telecommunications and RF monitoring equipment suppliers

Named in the bill

Department of Homeland Security, Department of Justice, Federal Aviation Administration, Federal Communications Commission, National Telecommunications and Information Administration, State and local law enforcement, Section 210G of the Homeland Security Act of 2002, Section 521 of Consolidated Appropriations Act 2004, Section 44812 of title 49 USC, Section 40103 of title 49 USC

Where it stands

1 cosponsor: 1 Democrats.

  • Feb 20, 2025 — Introduced · Congress.gov: “Introduced in Senate”
  • Feb 20, 2025 — Referred to Senate Committee on Homeland Security and Governmental Affairs · Congress.gov: “Read twice and referred to the Committee on Homeland Security and Governmental Affairs”

Dates and quoted wording are Congress.gov's action record; the timeline shows status changes, not every procedural step.

Money around this bill

2 lobbying clients named this bill on 2 disclosure filings across 1 quarter, Jun 2026 to Jun 2026. Those filings disclosed $820,000 in lobbying spend. A filing names 24 bills on average, so that figure is what each filing reported, not a share belonging to this bill.

More lobbying clients named this bill than 41% of bills with at least one filing.

Tom Cotton, the sponsor, reported $1,292,206 in PAC receipts in the 2026 cycle.

  • Nuclear Energy Institute, Inc — $560,000 on 1 filing
  • National Collegiate Athletic Association — $260,000 on 1 filing

Lobbying Disclosure Act filings through Jul 20, 2026. A filing shows who paid to lobby on a bill it names, not what changed.

How this was measured

Analysis — Quorum's AI read the full bill text on Jun 11, 2026; transparency and hidden-provision scores are compared against the median of 16,222 analysed bills.

Status and sponsors — Congress.gov's bill record — actions, committee referrals and cosponsors — loaded nightly. The timeline shows status changes, not every procedural action.

Money — Senate Lobbying Disclosure Act filings whose specific-issue field names this bill for quarters ending Jun 2026 to Jun 2026. A filing's amount is reported whole beside the median number of bills a filing names; it is never divided across them. PAC receipts are FEC-reported contributions to the sponsor's candidate committee in the 2026 cycle.

As of — lobbying records through Jul 20, 2026 · page rendered 2026-10-20.

“New drone-surveillance power for police — with no public oversight list” QuorumCivic. https://share.quorumcivic.app/bill/119/s663 Report an error

Correlative observation from public records — not evidence of coordination or wrongdoing, and not financial advice.
This page is the record as of today. The app tells you when it changes.
Quorum analysis of the full bill text · 119th Congress · public record

The week in bills

One email, Sunday: what Congress passed, what it changed, and who paid.

One link arrives to confirm the address. It is used for this email and nothing else, and every issue carries an unsubscribe link.