Ohio Gov. Mike DeWine signed House Bill 251 on July 7, giving the state its first statewide rulebook for how police departments can fly drones. The law, codified at ORC 4561.60 through 4561.64, takes effect October 6 and requires law enforcement agencies to get a warrant when a drone flight is used as a substitute for what would otherwise be an in-person search. It also bans mounting lethal weapons on police drones and sets documentation requirements for surveillance flights.
But in Cleveland, the state law arrives after the fact. The city's police department has operated under its own drone policy, General Police Order 4.06.17, since July 11, 2025 — more than a year before HB 251 takes effect — and that policy already goes considerably further than what Columbus just mandated statewide.
A comparison of the two documents, along with a year of Cleveland's own drone flight logs, shows the gap clearly. Where HB 251 sets a floor, GPO 4.06.17 sets a substantially higher one, and several of the restrictions Cleveland imposes on its own officers have no equivalent anywhere in the new state law.
What the state law actually requires
HB 251's core mechanism is the warrant trigger: if a drone flight functions as a search that would otherwise require a warrant under the Fourth Amendment, police need one. That is a meaningful baseline for a state that previously had no statewide drone-specific statute governing law enforcement at all. The bill also addresses circumstances where warrantless surveillance is permitted, and it requires agencies to document and verify data for surveillance flights, according to a summary published by Government Technology on September 16 and modified the following day.
On weapons, the law bans arming police drones with lethal weapons. It says nothing about facial recognition software, gait-analysis software, or other biometric identification tools that can be run against drone footage after the fact. It also does not address surveillance of demonstrations or protests, and it does not impose a specific deletion timeline for footage that is captured incidentally — footage of bystanders or uninvolved property swept up during a flight aimed at something else.
What Cleveland already requires
Cleveland's GPO 4.06.17, the Division of Police's official policy governing its unmanned aircraft systems program, closes each of those gaps. According to the policy document and the comparison built from it, the Cleveland Division of Police:
- Bans the use of facial recognition software on drone footage.
- Bans gait-analysis software, a biometric technique that attempts to identify individuals by the way they walk rather than by their face.
- Bans mounting any weapon on a police drone — not just lethal weapons, the narrower category HB 251 addresses.
- Restricts drone surveillance of demonstrations and protests.
- Requires deletion of footage unrelated to the purpose of a flight within 30 days.
- Restricts use of "Blackout Mode" — a stealth setting that turns off the drone's LED, infrared and other electronic identifying markers while it keeps recording — to situations where officers have a warrant.
Put side by side, the pattern is consistent: everywhere HB 251 is silent or narrow, Cleveland's local policy is specific and broader. The state law's weapons ban covers only lethal weapons; Cleveland's covers all weapons. The state law has no biometric-software provision at all; Cleveland bans two specific categories of it by name. The state law sets no retention clock; Cleveland sets one at 30 days.
How the fleet has actually been used
The policy comparison is paired with a year of real flight data. Cleveland's Skydio X10 drones logged 200 flight entries between September 10, 2025, and September 10, 2026, according to a cleveland.com review of the city's flight dashboard, as reported by DroneXL. Three categories accounted for 190 of those 200 entries: 71 flights tied to written safety plans for events such as sports games and other public gatherings, 63 call-ups for suspect searches and SWAT support, and 56 training flights, most of them clustered in four days of manufacturer training shortly after the program launched. The same review found no flights logged over a demonstration in the year of records it examined.
The comparison between the state law, Cleveland's policy, and the flight logs was compiled by cleveland.com through a review of both documents and a full year of flight records, as reported by DroneXL on September 20.
Why It Matters
HB 251 is a real step for Ohio — the state previously had no dedicated statutory framework governing police drone use, and a warrant requirement tied to search-equivalent flights gives residents statewide a baseline Fourth Amendment protection that didn't exist in state law before October 6. Government Technology's coverage frames the bill accordingly, noting it addresses search warrants, warrantless-surveillance circumstances, and flight documentation.
But the Cleveland comparison is a useful reminder that a statewide floor is not a ceiling, and it is not uniform protection. Residents of cities with less restrictive local policies than Cleveland's will get exactly what HB 251 provides and nothing more: a warrant requirement for search-equivalent flights and a ban on lethal weapons. Residents of Cleveland get that plus a ban on facial recognition and gait analysis, a ban on any weapon at all, protest-surveillance restrictions, and a 30-day deletion clock on incidental footage — protections that exist only because Cleveland's police department chose to adopt them locally, a year before the state acted at all.
That gap matters for two reasons. First, it means the strength of drone oversight in Ohio will vary significantly by jurisdiction even after HB 251 takes effect, since the new law does not preempt or require matching the stricter protections some departments have already put in place. Second, it puts pressure on the question of durability: local policies like GPO 4.06.17 can be amended by a police department or city administration without legislative action, in either direction, while HB 251's protections are now written into the Ohio Revised Code. Cleveland residents currently have the broader protections, but they rest on a police general order rather than a statute.
