Tesla Cybercab’s NHTSA Audit Tests U.S. Rules for Driverless Cars

Tesla’s paid Cybercab service in Austin is a consequential test of U.S. vehicle-safety law. The two-seat robotaxi has no permanently attached steering wheel, accelerator pedal, brake pedal, or conventional mirrors—equipment assumed by many long-standing federal motor-vehicle safety standards. 23

The National Highway Traffic Safety Administration’s audit does not itself determine that the Cybercab is unsafe or unlawful. Its immediate focus is narrower and more fundamental: whether Tesla properly certified roughly 1,000 vehicles as compliant with applicable Federal Motor Vehicle Safety Standards (FMVSS), and what technical data and legal reasoning supported that conclusion. 1214

What NHTSA is reviewing

NHTSA opened an audit query after the Austin rollout to examine Tesla’s certification process and supporting technical information. The agency said it would assess the basis for Tesla’s conclusion that the Cybercab meets the applicable FMVSS, including whether Tesla determined that particular standards do not apply to the driverless design. 215

That distinction matters. An audit of certification is not the same as a defect investigation, recall, or a final safety judgment. But it puts Tesla’s rationale for placing a purpose-built driverless vehicle into paid public-road service under federal scrutiny. 14

Why the Cybercab creates a regulatory clash

Federal rules provide two broad paths for vehicles equipped with automated-driving systems to operate on public roads:

1. A manufacturer can certify a vehicle as fully compliant with FMVSS.
2. A manufacturer can use an applicable statutory exception or seek an exemption for a vehicle that does not comply with one or more standards.

Tesla appears to be relying on the first route. That makes the central issue not simply whether automated driving is technologically advanced enough to operate the vehicle, but whether a car without conventional human controls can satisfy—or be outside the scope of—the relevant federal standards. NHTSA’s audit is examining that assertion. 12

The gap between an automated vehicle’s design and rules written for conventional cars is precisely where the dispute lies. A regulatory system can accommodate automated-driving systems on fully compliant vehicles, but a vehicle designed without a human driving position raises questions about how particular requirements apply.

Why self-certification can enable a launch before a final agency decision

The U.S. system generally relies on manufacturers to certify that their vehicles comply with applicable federal safety standards rather than requiring advance model-by-model approval before sale. NHTSA can subsequently review certifications and take action if it concludes a manufacturer’s position is unsupported. 12

For a new vehicle configuration, that structure can create a period in which the manufacturer operates under its own compliance certification while regulators test the underlying interpretation. It does not remove Tesla’s obligation to comply with FMVSS; it means the core disagreement may be resolved through an audit, potential enforcement action, and possibly litigation rather than through a pre-launch approval process. 12

The alternative: a temporary exemption with a scale limit

A manufacturer that cannot certify full compliance may seek a temporary exemption under Part 555. NHTSA says those exemptions can permit production of vehicles that do not meet certain FMVSS requirements, subject to statutory criteria and agency approval.

The production limit is important: for most grounds other than financial hardship, the program limits exempted vehicles to 2,500 in a 12-month period. NHTSA’s 2026 exemption for Zoox, for example, allowed commercial deployment of up to 2,500 robotaxis annually for two years under an enhanced oversight structure.

That cap explains the high stakes of Tesla’s approach. A successful full-compliance certification is potentially more scalable than relying on a temporary exemption. But if NHTSA rejects Tesla’s application of the standards, the company could face pressure to redesign the vehicle, pursue an exemption, limit deployment, or challenge the agency’s conclusion.

What this does—and does not—say about Full Self-Driving

Tesla’s broader claims about Full Self-Driving and robotaxi scale do not independently answer the certification question. For this audit, the relevant evidence is the vehicle’s compliance with applicable federal standards and the technical basis Tesla used to make that determination. 215

Likewise, the absence of a human fallback is an important practical concern for a vehicle intended to operate without a driver, but the audit’s announced purpose is not a final ruling on the overall safety or reliability of Tesla’s automated-driving system. 214

What happens next

The Cybercab review could clarify how existing FMVSS apply to vehicles designed exclusively for automated driving. If NHTSA accepts Tesla’s certification rationale, it would reinforce the full-compliance route for purpose-built robotaxis. If it does not, Tesla may need to alter its approach or contest the agency’s interpretation.

The immediate takeaway is straightforward: Tesla has launched a real-world test of a legal boundary. The question is whether a driverless vehicle with no manual controls can be treated as compliant under today’s federal safety framework—not whether an audit alone has already answered that question. 12