US government agency will consider Google's autonomous car system as the driver of the car for the purposes of federal safety standards
Feds declare that Google's self-driving car is its own driver — In a letter to Google, the National Highway Traffic Safety Administration determined …
Context & Ripple Effects
Google has spent 2015 building the case that its pod-style vehicle needs no human fallback: cars hit public roads with safety drivers aboard and speeds capped at 25mph, the company began publishing accident data on a public website, and the unit was set to become an Alphabet company in 2016. The friction point was regulators — Google publicly objected to proposed DMV rules mandating steering wheels, pedals, and specially certified drivers as progress-inhibiting.
First-order effects
- NHTSA's letter gives Google the federal interpretation it wanted: if the software is legally 'the driver,' safety standards written for human operators cannot be read to require controls like steering wheels — directly undercutting the premise of the California DMV rules Google called inhibitive.
Second-order effects
- State regulators now face a federal benchmark that contradicts their own draft requirements, forcing California's DMV to either defend its hardware mandates or concede ground; automakers pursuing similar designs gain a template for petitioning NHTSA for the same treatment.
Third-order effects
- The ruling begins decoupling 'driver' from 'human' in US safety law — a shift NHTSA itself extended eight years later when it proposed easing rules for fully driverless cars while demanding more operational data from operators, moving the industry toward regulation of the autonomy system rather than the person behind the wheel.
The trend: US auto regulation is migrating from certifying human drivers to certifying autonomous systems as the driver, with NHTSA's interpretive letters setting the pace ahead of formal rulemaking.