Ohio’s first statewide police drone law takes effect October 6, and Cleveland’s own drone policy already outlaws four things the state law leaves legal: facial recognition, gait analysis, surveillance of demonstrations, and any weapon on a police drone. House Bill 251, signed by Gov. Mike DeWine on July 7, requires a warrant when police would need one to enter a building in person and use a drone to look inside instead. Cleveland’s rules, in force since July 11, 2025, go further on nearly every point the state law touches.
The comparison comes from a cleveland.com review of both documents and of a year of Cleveland flight records. The city’s Skydio X10 fleet logged 200 flight entries between September 10, 2025, and September 10, 2026. Most were sports events and call-ups for suspect searches and SWAT support, plus a block of manufacturer training.
DroneXL has followed this policy since Cleveland police flew a drone over a protest in November 2024 while their draft rules were still awaiting Department of Justice review. Nearly two years later, that incident’s fingerprints are all over the final document.
Cleveland Bans Identification Tech and All Weapons on Police Drones
Cleveland’s policy prohibits automated analytics that can identify individuals or groups, naming facial recognition and gait analysis, and bans any weapon system on a police drone. Ohio’s HB 251 bans only lethal weapons on law enforcement drones and says nothing about identification technology.
The city’s general police order, GPO 4.06.17, directs pilots to minimize collecting information on people and places unrelated to a mission. Anything captured anyway must be deleted within 30 days under the city’s retention schedule. HB 251 makes surveillance and flight data a public record but sets no comparable clock on destroying footage of bystanders.
On warrants, the two documents point the same direction with different wording. The state law, codified at Ohio Revised Code 4561.60 through 4561.64, requires a warrant when a drone enters or observes the interior of a house or another place where an in-person search would need one. Cleveland requires a warrant wherever someone has a reasonable expectation of privacy, including yards and enclosures, and bars officers from intentionally recording those places without one.
Cleveland also regulates what the policy calls “Blackout Mode,” a setting that switches off the aircraft’s lights and electronic markers while the cameras keep recording. The city permits it only after police obtain a search warrant. The state law does not mention it.
Cleveland Restricts Drone Flights Over Demonstrations
HB 251 lists nine circumstances in which Ohio police may fly a drone without a warrant, among them a threat assessment before a large event. Cleveland’s policy prohibits using drones to surveil individuals or groups at public demonstrations or other large gatherings, and prohibits any drone use for crowd control.
The city does allow drones in written safety plans for outdoor public events with command-level approval, and it allows some flights over large crowds when police have probable cause that a crime is occurring or when public safety is endangered, provided the circumstances meet Fourth Amendment requirements for a warrantless search.
That carve-out was written after the November 24, 2024, flight over a protest outside Cuyahoga County Executive Chris Ronayne’s home, which DroneXL covered in Cleveland Police Deploy Drone at Pro-Palestine Protest Despite Lacking DOJ Approval. The fleet had already been sitting idle pending policy approval, and after the protest flight Police Chief Dorothy Todd committed to keeping it grounded until the policy cleared the Community Police Commission and the federal consent decree monitors. The drones did not fly again on official business until August 10, 2025, more than eight months later, when Cleveland’s Skydio X10 program finally launched.
The broadest state exception drew the most fire in Columbus. HB 251 lets police fly without a warrant in navigable airspace, in a physically nonintrusive manner, to observe what is otherwise visible to the naked eye. Gary Daniels, legislative director of the ACLU of Ohio, told lawmakers the provision “is a blank check for law enforcement,” according to cleveland.com’s report on the signing. Cleveland’s policy contains no naked-eye exception.
Cleveland Logged 200 Drone Flights in Its First Year
Cleveland requires a public map showing the date, time and flight path of every deployment within 48 hours. Ohio’s law requires agencies to document and verify flight data for surveillance flights, and makes those records public unless an exemption applies. It sets no posting deadline and requires no map.
Cleveland.com’s review of the city’s UAS Team Flights dashboard found 200 entries with distinct timestamps over the year to September 10, after removing duplicates created by overlapping dashboard views. The dashboard shows no more than 25 flights at a time, so the count took some assembly.
Three categories covered 190 of the 200 entries: 71 “Event Action Plan” flights, 63 “Assignment Call-Up” flights and 56 training flights. Event flights included sports and other public gatherings. Call-ups included suspect searches and SWAT support.
One operation can produce many entries. The dashboard shows 11 separately timed flights during a Browns event on December 21, 2025, and nine during a Browns detail on August 27, 2026. Training clustered too: 37 of the 56 training entries fell on four days of manufacturer training, September 22 through 25, 2025, right after the program launched with nine aircraft and seven Part 107 pilots.
The policy also requires quarterly reports to the police chief and the Community Police Commission covering all drone use by incident type, and says those reports will be posted on the city website. Asked where they were, the Cleveland Division of Police Office of Public Affairs pointed cleveland.com to the flight dashboard and did not identify a separate report.
HB 251 Delays Its Chinese Drone Purchase Ban Until 2030
HB 251 also bars Ohio public entities from buying drones made or assembled by a foreign adversary, and cleveland.com reported in July that the law gives them four years to comply. The enrolled text is narrower: the ban starts 48 months after October 6 and touches nothing bought before then.
Section 3 of the enrolled act makes the new Ohio Revised Code 5501.84 effective 48 months after the rest of the law, which lands in October 2030. From that date a public entity may not purchase or otherwise acquire a foreign-adversary drone system, no state funds may go toward one, and no public entity may operate one that was purchased on or after that date. Aircraft bought before October 2030 are not mentioned, so nothing already in an Ohio hangar is grounded by this law. The section also stands down entirely if federal law or regulations allow continued purchase and operation of the equipment.
“Foreign adversary” means a country on a registry the Ohio secretary of state must compile every six months from four federal lists, including the Commerce Department’s Executive Order 13873 list, which names China. Cleveland’s all-Skydio fleet is untouched either way. The two Ohio DFR programs DroneXL compared in December went opposite ways on hardware: Dublin chose DJI docks and Columbus chose Skydio. Under the enrolled text, Ohio law lets Dublin keep buying DJI for four more years, and Ohio’s statewide drone as first responder pilot, launched in February, faces no state-level hardware constraint before 2030.
DroneXL’s Take
Cleveland got the hard part right, and it got there the embarrassing way. The demonstration ban, the 48-hour map, the 30-day deletion rule and the Blackout Mode warrant requirement all exist because the department flew a drone over a protest in November 2024 under a policy the Department of Justice had not yet approved.
A civilian commission with real authority then wrote the rules the department had resisted. The Community Police Commission has final say over Cleveland police policy under the consent decree, and that is the only reason this document reads the way it does. Most departments that buy an X10 answer to a chief and a council, not to a commission with veto power over policy.
Ohio’s law is a floor, and a low one. The warrant requirement for looking inside a house is fine. The naked-eye exception swallows most of what a police drone actually does, because a drone at 400 feet (122 meters) sees what a helicopter at 400 feet sees, and the Supreme Court has treated that as public view since Florida v. Riley in 1989. Daniels called it a blank check. My read is that it is a blank check with a public records requirement attached, and that requirement is the only part with teeth. If the flight logs are public, a reporter can do what cleveland.com just did: pull a year of records and count.
Two hundred flights, 190 of them in three routine categories, nine of them during a single Browns game. The 10 entries outside those categories are not described in cleveland.com’s report, and that report, which set out to test the policy against the records, describes none over a demonstration. That is the pro-drone case made with the department’s own data: give police a capable aircraft, publish every flight, ban the uses that poison public trust, and the program runs. The 48-hour map did not stop a single suspect search.
The reports are the loose thread. Cleveland’s own policy promises quarterly reports by incident type on the city website, and when a reporter asked for them, the department pointed at the dashboard. A dashboard that shows 25 flights at a time and needs deduplication is not a quarterly report. The commission wrote that requirement for a reason, and when cleveland.com asked, the department could not point to one. Cleveland.com asked once. The commission should ask next, in public, before October 6.
The foreign-adversary clause is the part most likely to be misread. A four-year window to comply sounds like a replacement mandate. What Ohio passed is a four-year delay before a purchase ban that grandfathers every aircraft bought in the meantime and defers to Washington if federal rules ever loosen. As far as Ohio law is concerned, Dublin can order DJI docks through September 2030 and fly them for the rest of their service life. The FCC Covered List, not Columbus, is the constraint that decides what Ohio agencies fly, and the legislature wrote that deference into the statute. I suspect lawmakers wanted a China clause in the bill without a replacement bill for the counties, and the 48-month fuse is how they got both. Even the registry of adversary countries sits inside the delayed section, so Ohio will not publish its own list until 2030 either. Whether the General Assembly tightens the fuse before then is the thing to watch, and the 137th General Assembly that convenes in January 2027 is the first chance.
Sources: cleveland.com, via GovTech; Ohio General Assembly, House Bill 251 and the enrolled act; Cleveland Division of Police, GPO 4.06.17
DroneXL uses automated tools to support research and source retrieval. All reporting and editorial perspectives are by Haye Kesteloo. Read our editorial standards.
