Google's self-driving car may have caused its first accident, hitting public bus in California at 2mph, according to company's report to DMV
at 2 mph. http://www.usatoday.com/... Danny Sullivan / @dannysullivan : After hitting a bus, Google's self-driving car started singing “Daisy” & “Like a good neighbor, State Farm is there” http://www.techmeme.com/... Steven Sinofsky / @stevesi : Google says it bears ‘some responsibility’ after self-driving car hit bus http://www.reuters.com/... via @Reuters Chris Ziegler / @zpower : statement from google on the recent car crash. tldr: the car made a very human assumption, and it was the wrong one http://www.theverge.com/... Mark Bergen / @mhbergen : Google car hit a bus. Human watching behind wheel thought bus would stop. What did the robot think? http://recode.net/... Sam Sabri / @samsabri : Still a better driving record than all drivers in Seattle http://twitter.com/...
Context & Ripple Effects
Google has spent two years building a public case that its self-driving car is the safest thing on California roads: after 1.7 million miles and just 11 minor accidents, the program insisted every collision was another driver's fault, and it even launched a dedicated site publishing its own accident data to make that argument. The state's own incident reports reinforced the pattern — six crashes, mostly caused by other drivers, no serious injuries.
The bus collision changes the framing: for the first time Google concedes 'some responsibility,' and the company's own intervention data shows how often humans have been catching the software before contact — 272 takeovers over 14 months. With the prototype design now road-tested and Google lobbying hard to shape driverless-car regulation, the first at-fault crash lands at a sensitive moment.
First-order effects
- Google can no longer cite a spotless fault record to regulators and the public; its report to the California DMV formally attributes responsibility to its own vehicle for the first time.
- The human overseer who failed to prevent the low-speed impact becomes evidence for critics that the safety-driver layer is unreliable exactly when the software misjudges.
Second-order effects
- California's DMV, already releasing prototype incident reports, gains its clearest case yet for tightening testing rules or disclosure requirements around autonomous vehicles.
- Rival programs testing in the state now face a benchmark shift: Google's 'other drivers' fault' talking point is gone, so safety comparisons will hinge on reported incident detail rather than headline counts.
Third-order effects
- If at-fault collisions become part of the record as fleets scale, liability assignment between operator, software, and the human monitor moves to the center of regulatory design — territory where Google's aggressive lobbying has positioned it to shape the rules.
- The episode pushes the industry toward treating rare machine errors not as PR problems but as data points to publish proactively, since transparency about failures becomes the price of operating permits.
The trend: Self-driving programs are entering the phase where their own vehicles cause accidents on public roads, shifting the debate from whether autonomous cars crash to who answers when they do.