To amend sections 4561.01 and 4561.11 and to enact sections 4561.60, 4561.61, 4561.62, 4561.63, 4561.64, and 5501.84 of the Revised Code to establish requirements related to the use and purchase of an unmanned aerial vehicle by law enforcement and other public entities and to expressly incorporate additional aviation facilities into the Aeronautics Law.
HB251 amends Ohio’s Aeronautics Law to update definitions and approval rules for aviation facilities, expressly adding vertiports, spaceports, heliports, seaplane bases, and landing areas to the statutory framework. It also creates a new set of provisions governing how law enforcement may use unmanned aerial vehicles (UAVs), or drones, for surveillance and related public-safety purposes.
The bill requires a search warrant when police would otherwise need one to physically enter a house or place, but instead seek to enter or observe the interior using a drone. It also bars warrantless drone surveillance evidence from being used in criminal proceedings unless a statutory exception applies. At the same time, the bill lists several warrant exceptions, including border patrol within 50 miles of a national border, exigent circumstances, disaster and emergency response, traffic enforcement, crime-scene documentation, and research or training uses with educational or public/private collaborators. It further prohibits arming law-enforcement drones with lethal weapons and restricts surveillance of one private individual by another private individual unless consent is obtained.
HB251 also imposes recordkeeping and disclosure requirements on law enforcement agencies. Agencies must document and verify flight data for each surveillance flight, retain relevant surveillance and flight data for ongoing matters, and make flight data public records unless another exemption applies. Defendants may obtain certain surveillance-related information through subpoena and discovery, but the bill protects technical operational capabilities and physical-security details from disclosure.
The bill’s impact on state law is to create a detailed statutory regime for police drone use, evidence admissibility, and public-records access, while also modernizing aviation statutes to reflect newer facility types. It would affect law enforcement agencies, criminal defendants, privacy interests, and public entities involved in aviation infrastructure. The bill also appears to anticipate future public-entity drone purchasing and use rules through the broader caption, though the introduced text provided focuses primarily on surveillance and aviation definitions.
The general sentiment reflected in the available voting history is strongly favorable: the bill passed House committee 13-0 and later passed the House 94-2. That suggests broad bipartisan support for setting guardrails around police drone use while preserving operational exceptions for emergencies and public safety. The main points of contention likely center on privacy and warrant requirements versus law-enforcement flexibility, especially the scope of warrantless exceptions, the public-records treatment of flight data, and the limits on disclosure of drone capabilities and operational security.
HB251 would amend sections 4561.01 and 4561.11 of the Revised Code and add new sections 4561.60 through 4561.64, creating a new legal framework for law-enforcement use of unmanned aerial vehicles. It would require warrants for drone-based entry or interior observation when a warrant would otherwise be needed for physical entry, establish exceptions for specified public-safety and enforcement situations, prohibit armed police drones, and require documentation, retention, and partial public disclosure of drone flight data. It also updates Ohio aviation definitions and approval rules to expressly include additional aviation facilities such as vertiports and spaceports.
The available vote history indicates strong support for the bill. It received unanimous favorable passage in House committee and then passed the House by a wide margin, 94-2. That pattern suggests lawmakers broadly agreed on the need for drone-use standards and privacy protections, while accepting limited exceptions for emergencies, border enforcement, and other public-safety uses.
The likely areas of disagreement are the balance between privacy rights and law-enforcement discretion, especially the warrant requirement for drone surveillance of homes and other places, and the breadth of the bill’s warrant exceptions. Another possible point of contention is the public-records treatment of flight data versus the bill’s protection for technical and security-sensitive operational information. The prohibition on lethal weapons on drones and the consent requirements for surveillance of private individuals also reflect privacy and civil-liberties concerns that may have been weighed against operational needs.