The bill prohibits federal agencies—including the Department of Defense and Department of Homeland Security—from using specified military or military‑derived unmanned aircraft vehicles (UAVs) inside the United States to conduct surveillance of United States persons who are engaged in protests or civil disobedience. It accomplishes this by denying the use of funds authorized for those agencies to operate such covered UAVs for that surveillance purpose beginning in fiscal year 2026.
The measure also creates a mandatory annual presidential report to several congressional oversight committees cataloguing instances where covered UAVs were used for novel or unauthorized purposes. The reporting requirements demand granular operational details—dates, locations, vehicle models, sensors and weapons, justification for use, and any identification, dissemination, or retention of United States person data—though the report or an annex may be classified.
The bill tightens transparency while raising practical and definitional questions about which platforms and missions are affected and how agencies will document compliance.
At a Glance
What It Does
The bill bars use of appropriated funds to operate 'covered unmanned aircraft vehicles' in the U.S. for surveillance of U.S. persons engaged in protests or civil disobedience, starting FY2026. It requires the President to provide an annual report to specific congressional committees detailing any novel or unauthorized domestic uses of those vehicles and a set list of operational data points.
Who It Affects
Primary targets are federal executive agencies that operate or task long‑endurance, military‑developed UAVs—explicitly named is the MQ‑9 Reaper—and any entity that receives such surveillance support from those agencies. Congress, oversight committees, civil‑liberties groups, and manufacturers of military‑style UAVs will also be affected by the operational and reporting changes.
Why It Matters
This is a precedent-setting domestic restriction on military‑derived drone use for protest surveillance, pairing a funding ban with a detailed transparency regime. Compliance will require agencies to map which platforms qualify as 'covered,' to change operational plans where necessary, and to produce technically detailed reports that could expose internal decisionmaking or remain classified.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The statutory approach is twofold: an appropriations‑based prohibition and an annual reporting obligation. The prohibition works by forbidding agencies from using funds they are authorized to spend to operate certain unmanned aircraft inside the United States when those aircraft are being used to surveil U.S. persons taking part in protests or civil disobedience.
Because the bar is on use of funds rather than an outright equipment ban, agencies retain ownership of systems but cannot fund the operation of covered UAVs for the specified surveillance activity.
'Covered unmanned aircraft vehicles' are defined in three overlapping ways: the MQ‑9 Reaper or variants; any airframe first developed for Armed Forces use; and long‑endurance platforms that are medium‑altitude or high‑altitude long‑endurance, or that can fly at 10,000 feet or higher. That definition reaches many military and many military‑derived systems used domestically.
The bill does not prohibit all UAV use in the U.S.—it targets only surveillance of 'United States persons' engaged in protests or civil disobedience, and it leaves other mission types and non‑covered platforms untouched.On transparency, the President must deliver an annual report to a specific set of congressional committees (Armed Services, Homeland Security, Intelligence committees in both chambers and Senate Governmental Affairs). The report must list every instance where a covered UAV was used for a novel purpose or in a way not authorized by Congress, and for each instance provide granular details: purpose, an operational justification that explains why a covered UAV was necessary instead of alternatives, timing, location, vehicle model, sensors and weapons onboard, the approval process used, and whether any U.S. persons were identified, shared, or retained.
The statute permits submission of a classified annex, so some details may remain secret while Congress still receives a formal accounting.Practically, agencies will need internal processes to detect when a planned or actually conducted flight meets the statute's trigger (surveillance of U.S. persons at protests) and whether the platform qualifies as covered. They will also need to assemble documentation addressing the report elements—technical inventories of sensors and weapons, legal and operational justifications, and data on retention and dissemination.
Because the prohibition attaches to funds, agencies may adjust by shifting to non‑covered platforms, using alternative air assets, or changing assistance to state and local partners. The bill leaves unanswered how to treat incidental collection, preemptive monitoring, or cases where protest activity and counterterrorism objectives overlap, which will shape implementation and interagency coordination.
The Five Things You Need to Know
The prohibition applies to funds authorized for fiscal year 2026 and each fiscal year thereafter and blocks those funds from being used to operate covered UAVs in the U.S. to surveil U.S. persons engaged in protests or civil disobedience.
The statute explicitly names the MQ‑9 Reaper and also covers any airframe initially developed for Armed Forces use, any medium‑altitude or high‑altitude long‑endurance aircraft, and any unmanned aircraft capable of flying at 10,000 feet or higher.
The President must submit an annual report to specific congressional committees listing each 'novel' or 'unauthorized' domestic use of a covered UAV and, for each instance, provide details including dates, locations, vehicle model, sensors and weapons onboard, and the approval process used.
Reports must explain why a covered UAV was required versus traditional civilian alternatives (helicopters, smaller UA) and must state whether any United States persons were identified, how many, the purpose of identification, whether their data were shared, and how long those records will be retained.
Congress may receive the report in classified form or with a classified annex, allowing operational details to remain secret while satisfying the statutory transparency requirement.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Provides the act's common name: 'Ban Military Drones Spying on Civilians Act.' This is purely nominal but important for how the measure will be cited in legislative and implementation materials.
Funding prohibition on operating covered UAVs for protest surveillance
Denies use of funds authorized to be appropriated for FY2026 and later for DHS, DOD, or any other executive agency to operate a covered unmanned aircraft vehicle in the U.S. to conduct surveillance of U.S. persons engaged in protests or civil disobedience. Because the statute targets use of funds rather than title to equipment, agencies could still possess systems but not use appropriated funds to operate them for the proscribed surveillance purpose; they could instead seek alternative platforms or funding models unless further restricted elsewhere.
Annual presidential report—what must be disclosed
Mandates a yearly report from the President to named congressional committees cataloguing every instance a covered UAV was used for a novel purpose or a purpose not authorized by Congress. For each instance the report must include operational justification, timing, duration, location, vehicle model, inventory of sensors and weapons, the approval process applied, and a explicit accounting of whether any U.S. persons were surveilled—if so, how many, why they were identified, dissemination recipients, and retention periods. This creates a detailed documentary trail that committees can use for oversight and potential legislative follow‑up.
Classification carve‑out for reporting
Permits the required annual report to be delivered in classified form or to include a classified annex. That allows agencies to protect operationally sensitive data while still meeting the statute’s formal transparency obligation; it also means oversight may occur behind closed doors and public accountability will depend on how much is redacted or withheld.
Key definitions and scope—committees, covered UAVs, and U.S. person
Defines the 'appropriate congressional committees' that will receive reports, lists what counts as a covered UAV (MQ‑9, airframes first developed for military use, MALE/HALE platforms, and aircraft capable of 10,000 ft+), adopts the statutory definition of 'executive agency' from Title 5, and references an existing statutory definition of 'United States person.' These definitions drive the statute's reach and will be the focus of agency legal analysis when determining whether a given platform or mission falls within the prohibition.
This bill is one of many.
Codify tracks hundreds of bills on Privacy across all five countries.
Explore Privacy in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Participants in protests and civil disobedience: The prohibition reduces the risk that long‑endurance, military‑style drones will be deployed to monitor individuals exercising First Amendment rights, lowering the chance of federal aerial surveillance targeting attendees.
- Civil liberties and privacy organizations: The annual reporting requirement and the funding bar provide oversight levers and data for advocacy and litigation aimed at limiting intrusive domestic surveillance.
- Local communities and journalists: Communities that host protests and reporters covering demonstrations gain protections against being systematically tracked from high‑altitude, long‑endurance platforms.
- Congressional oversight committees: The bill provides committees with a structured, recurring flow of operational information—vehicles, sensors, justifications, and dissemination practices—enabling more informed oversight and potential legislative fixes.
Who Bears the Cost
- Department of Defense and Department of Homeland Security: Both agencies will lose an option—operation of covered, long‑endurance military‑style UAVs—for monitoring protests, and will need to document past uses and adapt operations, training, and mission planning.
- Intelligence community components and other executive agencies: Agencies that relied on either direct operation or interagency support from operators of covered UAVs will face operational constraints and the administrative burden of compiling detailed reports.
- Manufacturers and contractors of military‑style UAVs: Reduced domestic operational use for certain platforms may lower demand for some services or require reconfiguration for civil markets, affecting business models tied to domestic deployments.
- State and local law enforcement that relied on federal aerial assistance: Agencies that obtained situational awareness support from federal long‑endurance platforms may find assistance curtailed or shifted to other assets, complicating joint operations at large events.
- Agency budgets and compliance offices: Preparing the level of detail the statute requires—especially technical inventories and retention/dissemination accounting—will impose personnel and systems costs on agencies responsible for reporting.
Key Issues
The Core Tension
The bill pits protection of civil liberties—preventing use of robust, military‑grade aerial surveillance against protesters—against legitimate public‑safety and national‑security needs that sometimes rely on high‑end, long‑endurance platforms; the tougher the restriction on surveillance, the more it may limit the government’s ability to monitor large events for serious threats, while looser rules risk enabling intrusive monitoring of lawful political activity.
Several implementation challenges and trade‑offs are embedded in the bill. First, the definitions of 'covered unmanned aircraft vehicle' (airframe developed for the Armed Forces, MALE/HALE, or capable of 10,000 ft) are broad and technology‑driven; they risk sweeping in platforms that are functionally common in domestic use or that have dual civil/military origins.
Agencies will need legal and technical analyses to classify aircraft, and small changes in airframe origin or altitude capability could change whether an asset is covered.
Second, the statute targets surveillance of 'United States persons engaged in protests or civil disobedience,' but it does not explain how agencies determine when an activity qualifies as protest versus another civil‑order event, nor how to treat incidental collection of passersby or members of the press. Operationally, distinguishing targeted protest surveillance from broader public safety monitoring can be difficult in real time and could chill legitimate monitoring of public safety risks.
The reporting regime demands granular operational justification and sensor inventories, but the allowance for a classified annex means the public transparency the bill promises can be substantially limited in practice.
Finally, tying the restriction to appropriations creates both strength and weakness: it gives Congress a clear enforcement tool but may simply redirect operations (for example, to contractors, non‑covered platforms, or non‑Federal actors) rather than eliminating aerial surveillance in practice. The reporting burden will also require agencies to build new documentation systems.
Together, these factors create implementation complexity and raise the prospect of unintended shifts in how aerial surveillance is sourced or performed domestically.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.