OHIO ROBOTAXI POLICY TRACKER
Ohio robotaxi laws and legislation: what is pending?
No standalone Ohio robotaxi or autonomous-driving bill is currently pending. Ohio has a testing framework, several adjacent human-driver rideshare bills and one directly relevant federal proposal.
No operation should rely on this page as an approval. A proposed driverless fleet should obtain written classifications from the relevant agencies and review by qualified Ohio transportation counsel.
LEGISLATION WATCH
No direct Ohio bill is pending. These measures are worth tracking.
We searched the current 136th Ohio General Assembly docket for robotaxi, autonomous-vehicle, automated-driving-system and related measures. We found no standalone state bill that would authorize or regulate passenger robotaxis. The tracker below separates one direct federal proposal from Ohio bills that concern conventional human-driver rideshare services.
- Direct Ohio bill
- NONE PENDING
- Closest Ohio bill
- H.B. 604
- Newest Ohio bill
- H.B. 980
- Direct federal bill
- H.R. 7390
- Docket checked
- AUG. 19, 2026
H.R. 7390 — SELF DRIVE Act of 2026
Would create a federal safety framework for automated-driving systems and includes provisions addressing vehicles built without traditional manual driving controls.
Why it matters: This is the most directly relevant pending measure for a steering-wheel-free vehicle such as Cybercab. Its sponsor, Rep. Bob Latta, represents Ohio’s 5th District.
H.B. 604 — Transportation network company laws
Would modify product-liability, vicarious-liability and common-carrier treatment for transportation network companies.
Why it matters: It is Ohio’s closest pending bill, but its operative language concerns rideshare platforms and human TNC drivers—not autonomous-driving systems.
H.B. 980 — Rideshare Sexual Assault Prevention Act
Would add recurring driver background checks, safety policies, optional trip recording, incident reporting and related passenger protections.
Why it matters: It is useful context for future robotaxi passenger-safety policy, although its current provisions are structured around human drivers.
H.B. 674 — School transportation by TNC
Would let schools use transportation network companies while imposing background checks, inspections, GPS monitoring and parent-notification requirements.
Why it matters: It could inform future automated passenger-safety debates, but the bill expressly assumes a human driver and is not a robotaxi authorization.
H.B. 840 — Pay and workers’ compensation for TNC drivers
Would establish minimum driver compensation, workers’ compensation, pay disclosures, anti-retaliation protections and deactivation appeals.
Why it matters: This is evidence that Ohio’s current TNC debate remains driver-centered; it would not itself authorize or regulate driverless service.
Last verified: . “Pending” means the measure has not become law. Committee activity can change, so follow the linked official status pages for the latest action.
LEGISLATIVE HISTORY
Ohio considered—but removed—a heavy automated-vehicle rule.
A superseded Senate committee draft of the 2025 transportation budget, H.B. 54, proposed a physically present licensed safety driver for automated motor vehicles weighing at least 10,000 pounds. Lawmakers removed that provision before passage, and it is absent from the enrolled act. It is not pending, is not current law and would not have covered a two-seat Cybercab.
TESTING FRAMEWORK
Ohio permits testing subject to DriveOhio requirements.
Executive Order 2018-04K established requirements for Level 3 through Level 5 autonomous-vehicle testing and pilot programs on Ohio public roads. Before testing, a company must register with DriveOhio and provide vehicle, operator, insurance, safety and planned-operating information.
For higher-automation testing, the order also addresses minimal-risk behavior after a failure, compliance with traffic laws and cooperation with law enforcement following a collision or violation.
OFF-BOARD MONITORING
The designated operator may be outside the test vehicle.
Ohio’s testing order allows an operator to monitor remotely, but the operator must actively monitor the vehicle, recognize unsafe operation, be able to bring the vehicle to a minimal-risk condition and hold a driver’s license recognized by Ohio.
Testing without an operator inside must be disclosed to DriveOhio, including the routes and people monitoring the vehicles. That testing framework does not by itself authorize paid public rides.
FEDERAL VEHICLE STATUS
A novel vehicle still needs a lawful federal path.
NHTSA administers Federal Motor Vehicle Safety Standards. A new vehicle manufactured for sale or introduced into U.S. commerce must be certified to applicable standards or covered by a lawful exemption. The Part 555 process can authorize limited numbers of noncompliant vehicles when the required safety and public-interest findings are made; it is not automatic approval for every vehicle without manual controls.
NHTSA announced additional rulemaking in 2026 concerning brake-pedal requirements for vehicles intended to be driven only by an automated system. A proposal is not a blanket Cybercab approval.
PAID PASSENGER SERVICE
Ohio’s TNC statutes define a human driver.
Ohio’s transportation-network-company statutes cover permits, fares, receipts, records, nondiscrimination and other duties. Related definitions describe an individual driver and that person’s vehicle.
In our reading, a company-owned fleet with no human driver does not fit that wording cleanly. That is an interpretation—not a regulatory ruling. Classification should be confirmed with the Public Utilities Commission of Ohio, Ohio BMV, DriveOhio and applicable local or airport authorities before service is planned.
PRELAUNCH CHECKLIST
Questions to resolve before buying or operating vehicles
- Tesla’s authorizationConfirm third-party purchase and commercial-use terms.
- Federal vehicle documentationObtain applicable compliance or exemption records.
- DriveOhio coordinationComplete any testing registration and safety process.
- Service classificationConfirm permitting with PUCO, BMV and relevant Columbus or airport officials.
- Commercial risk programSecure coverage, remote support, incident reporting and emergency-response procedures designed for autonomous rides.
PRIMARY SOURCES
Check the source material.
- Ohio Executive Order 2018-04K archive
- U.S. DOE summary of Ohio AV requirements
- Ohio Executive Order 2019-26D archive
- Ohio Revised Code 3942.01 — TNC definitions
- Ohio Revised Code 3942.02 — TNC insurance
- Ohio Revised Code Chapter 4925 — TNCs
- Ohio Administrative Code TNC rules
- Ohio H.B. 604 — official bill page
- Ohio H.B. 674 — official bill page
- Ohio H.B. 840 — official bill page
- Ohio H.B. 980 — official bill page
- Federal H.R. 7390 — status and actions
- Federal H.R. 7390 — introduced text
- Ohio H.B. 54 — superseded Senate committee draft
- Ohio H.B. 54 — enrolled act without AV provision
- NHTSA automated driving systems
- NHTSA Part 555 exemption process
- NHTSA 2026 brake-pedal rulemaking