NHTSA considers ending steering wheel mandate for robotaxis
NHTSA’s administrator says the agency will consider removing steering-wheel requirements for vehicles built never to be human-driven, following a narrower change involving manual brake controls.
The National Highway Traffic Safety Administration will consider whether federal vehicle standards should continue to require steering wheels in vehicles designed exclusively for automated operation. Administrator Jonathan Morrison said on July 9 that manual controls make little sense in a vehicle intended never to be driven by a human. The statement signals a possible rulemaking direction; it is not, by itself, a final rule or permission to deploy a steering-wheel-free robotaxi.
The discussion follows the agency’s update in the previous month removing a manual brake-pedal mandate for fully autonomous vehicles. That change was limited to vehicles designed to operate exclusively without a human driver and did not alter requirements for conventional vehicles. Morrison provided no schedule, proposed text or implementation details for a steering-wheel review.
Why the distinction matters
Federal Motor Vehicle Safety Standards were largely written around vehicles with a human driver, a driver’s seating position and manual controls. Purpose-built automated vehicles can challenge those assumptions. Removing a control requirement may simplify cabin design and manufacturing for companies developing dedicated robotaxis, including Tesla’s two-seat Cybercab, which lacks a steering wheel and foot pedals. Tesla has begun producing Cybercabs but had not broadly deployed them as of the report. Other major participants include Zoox and Waymo, the leading U.S. operator of paid robotaxi rides.
A standards change would address only one layer of the regulatory stack. It would not establish that an automated driving system is safe, authorize commercial service in every state or city, settle insurance obligations, or replace federal defect and recall authority. Vehicle manufacturers and fleet operators must separate design compliance from permission to operate. State licensing, local operating rules, reporting duties and any applicable exemption conditions remain independent questions.
Operator and fleet impact
For developers, eliminating a steering-wheel mandate could reduce the need to seek case-specific exemptions or build controls that passengers are not expected to use. It could also permit more flexible seating and interior layouts. Those benefits come with new operational dependencies: without manual controls, a disabled automated system cannot simply hand control to an onboard safety driver. Remote assistance, minimum-risk behavior, passenger support, recovery procedures and secure maintenance access become central elements of the safety case.
Carriers or logistics operators evaluating autonomous vehicles should avoid treating the administrator’s comments as a procurement green light. Contracts need to allocate responsibility for software updates, mapping limits, remote support, cybersecurity events, towing and recovery, regulatory reporting and periods when the automated system is unavailable. Insurance applications and customer disclosures should accurately describe whether the vehicle has manual controls and who can direct it when automation cannot continue.
Recommended compliance steps
- Track the formal docket rather than relying on interviews or product announcements; review the scope, vehicle definitions, effective date and transition provisions of any proposal.
- Maintain a requirements matrix separating federal vehicle certification, automated-driving-system obligations, state registration and local commercial operating authority.
- Require suppliers to identify the certified vehicle configuration and explain how each applicable safety standard is met or lawfully exempted.
- Test minimum-risk maneuvers, remote-assistance escalation, passenger communications and roadside recovery under loss of connectivity, sensor degradation and blocked-route conditions.
- Preserve software versions, maintenance records, operational-design-domain limits and intervention logs so the fleet can demonstrate which configuration operated on a given date.
- Do not remove or disable required controls on existing vehicles based on a policy statement. Any retrofit must follow the final legal framework and manufacturer instructions.
The policy direction may favor vehicles designed from the outset without traditional controls, but the compliance outcome remains unresolved. Until NHTSA publishes and completes a formal action, steering-wheel requirements remain a live certification issue. Prudent operators can prepare the evidence, contracts and procedures now without assuming the rule has already changed.