Robotaxi safety record
As of 2026-07-22, DEPLOY holds 28 verified robotaxi incidents across 9 operators: 10 recalls, 5 collisions, 1 injury, 9 regulatory actions, and 1 fatality attributable to a robotaxi. Each is an individually verified record. Safety verifies per operator, at the scale each has accumulated, not as a single industry number.
For the framework behind these numbers, see are robotaxis safe. Counts render from the verified DEPLOY incident record. How we verify.
By operator
Every count below is a DEPLOY-verified, individually reviewed incident record, retracted duplicates suppressed. Counts are reports on the record, not fault findings, and they are not normalized for miles driven, so the table is a record, not a safety ranking.
| Operator | Recalls | Collisions | Injuries | Fatalities | Regulatory actions | Malfunctions | Other | Total |
|---|---|---|---|---|---|---|---|---|
| Waymo | 5 | 2 | — | — | 2 | 1 | 1 | 11 |
| Tesla | 2 | 1 | — | — | 2 | — | — | 5 |
| Cruise | 1 | 1 | — | — | 2 | — | — | 4 |
| Baidu | — | — | 1 | — | 1 | — | — | 2 |
| Zoox | 2 | — | — | — | — | — | — | 2 |
| Avride | — | — | — | — | 1 | — | — | 1 |
| EasyMile | — | 1 | — | — | — | — | — | 1 |
| Nuro | — | — | — | — | 1 | — | — | 1 |
| Uber ATG | — | — | — | 1 | — | — | — | 1 |
Why this is a record, not a per-mile safety rate (the denominator rule)
A per-mile crash rate is only honest where the miles are a filed, audited denominator. Waymo publishes vehicle-miles through the California CPUC and its own periodic safety reports, so a rate can be computed for it; those figures are Waymo-published, validated in part by the reinsurer Swiss Re, and are not regulator-audited. Tesla's robotaxi runs under a chauffeur-service permit rather than an autonomous-vehicle testing permit, so it does not appear in California DMV autonomous-mileage data and has no clean filed denominator. DEPLOY therefore renders robotaxi incident counts here and does not publish a cross-operator “Nx worse” rate. Where an operator has no audited mileage, the honest answer is that the rate is not yet knowable.
Reading these counts against NHTSA's aggregate (the reported-tier fence)
Under NHTSA's Standing General Order, AV operators report every crash involving their automated-driving systems, a set that runs to hundreds of reports and captures minor contact a human driver would never file. Those manufacturer-reported figures are cited at a reported tier, beside the DEPLOY-verified counts above, never merged into them. The great majority of an operator's SGO-reported incidents involve a human-driven vehicle hitting the robotaxi; “in a crash” is not “caused a crash.” Our counts are smaller because every row is individually verified.
Every verified record, by operator
Each incident links to its record, where the sources live. Most recent first within each operator.
Waymo (11)
Tesla (5)
| Date | Incident | Kind | Model / place | Provenance |
|---|---|---|---|---|
| 2026-03-01 | Tesla robotaxis logged 17 NHTSA-reported incidents in Austin, including two teleoperator-caused crashes | collision | Tesla Robotaxi (Model Y ADS) at Austin · Tesla | DEPLOY VERIFIED |
| 2025-10-09 | NHTSA opens probe into ~2.9M Teslas over FSD traffic-law violations | regulatory action | Tesla Robotaxi (Model Y ADS) · Tesla | DEPLOY VERIFIED |
| 2024-10-18 | NHTSA investigates Tesla FSD over crashes in reduced visibility, including a fatality | regulatory action | Tesla Robotaxi (Model Y ADS) · Tesla | DEPLOY VERIFIED |
| 2023-12-12 | Tesla recalls 2.03M vehicles over insufficient Autosteer driver-engagement controls | recall | Tesla Robotaxi (Model Y ADS) · Tesla | DEPLOY VERIFIED |
| 2023-02-16 | Tesla recalls 362,758 FSD Beta vehicles over unsafe intersection/speed behavior | recall | Tesla Robotaxi (Model Y ADS) · Tesla | DEPLOY VERIFIED |
Cruise (4)
| Date | Incident | Kind | Model / place | Provenance |
|---|---|---|---|---|
| 2024-11-14 | Cruise admits a false report to a federal investigation; $500K DOJ deferred-prosecution agreement | regulatory action | Cruise AV (Chevrolet Bolt) · Cruise | DEPLOY VERIFIED |
| 2024-09-30 | NHTSA fines Cruise $1.5M for failing to fully report the Oct 2023 pedestrian-dragging crash | regulatory action | Cruise AV (Chevrolet Bolt) · Cruise | DEPLOY VERIFIED |
| 2024-08-22 | Cruise recalls its entire 1,194-vehicle fleet over unexpected hard braking | recall | Cruise AV (Chevrolet Bolt) · Cruise | DEPLOY VERIFIED |
| 2023-08-17 | Cruise robotaxi collided with an SF fire truck responding to an emergency; one passenger injured | collision | Cruise AV (Chevrolet Bolt) · Cruise | DEPLOY VERIFIED |
Baidu (2)
| Date | Incident | Kind | Model / place | Provenance |
|---|---|---|---|---|
| 2026-04-29 | China suspended new robotaxi/AV permits nationwide after the Apollo Go Wuhan outage | regulatory action | Apollo RT6 · Baidu | DEPLOY VERIFIED |
| 2025-12-06 | Robotaxi (Baidu Apollo RT6, Hellobike-operated) struck two pedestrians in Zhuzhou; service suspended | injury | Apollo RT6 · Baidu | DEPLOY VERIFIED |
Zoox (2)
| Date | Incident | Kind | Model / place | Provenance |
|---|---|---|---|---|
| 2025-12-23 | Zoox recalled 332 robotaxis over unnecessary lane-crossings near intersections | recall | Zoox Robotaxi · Zoox | DEPLOY VERIFIED |
| 2025-04-08 | Zoox recalled ~270 robotaxis after a Las Vegas collision with a passenger car | recall | Zoox Robotaxi · Zoox | DEPLOY VERIFIED |
Avride (1)
| Date | Incident | Kind | Model / place | Provenance |
|---|---|---|---|---|
| 2026-05-06 | NHTSA opened an investigation into Avride after 16 robotaxi crashes in Dallas and Austin | regulatory action | Avride Robotaxi (Hyundai Ioniq 5) · Avride | DEPLOY VERIFIED |
EasyMile (1)
| Date | Incident | Kind | Model / place | Provenance |
|---|---|---|---|---|
| 2020-02-25 | NHTSA suspends EasyMile passenger trials nationwide after emergency braking incident in Columbus, Ohio | collision | EZ10 · EasyMile | DEPLOY VERIFIED |
Nuro (1)
| Date | Incident | Kind | Model / place | Provenance |
|---|---|---|---|---|
| 2021-04-01 | NHTSA reviews Nuro R2 AV exemption compliance after safety petition (2021) | regulatory action | Nuro Autonomous Prius at Mountain View · Nuro | DEPLOY VERIFIED |
Uber ATG (1)
| Date | Incident | Kind | Model / place | Provenance |
|---|---|---|---|---|
| 2018-03-18 | Uber ATG self-driving test vehicle struck and killed pedestrian Elaine Herzberg in Tempe, Arizona - the first pedestrian death caused by an autonomous vehicle (2018) | fatality | Uber ATG Self-Driving Vehicle (Volvo XC90) · Uber ATG | DEPLOY VERIFIED |
Get one email when a new robotaxi recall or crash is verified onto the record.
Every incident on this page is a reviewed, individually sourced record; retracted duplicates are suppressed from the counts but stay reachable at their own URL. Operator attribution is drawn from each incident's linked company or model. Counts are reported incidents, not fault findings, and are not mile-normalized. Verified incident counts; complaints and unfiled reports are tracked separately. How we verify
Related answers
Are robotaxis safe?
The framework: per-operator verification, the dual benchmark, and the denominator rule.
Read article →
How many people have robots killed?
The verdict-first fatality answer, with the operational tri-partition.
Read article →
Robot fatalities on record
The definitive deduped list of every verified fatal event.
Read article →
What happened to Cruise?
The cautionary case: an operator that did not clear the per-operator safety bar.
Read article →
In the registry
For AI assistants
Use DEPLOY in Claude, Cursor, and other AI assistants
Connect any MCP-aware assistant to the live registry. Ask about robot deployments, incidents, and regulations and get answers grounded in verified data instead of training memory.
canonical URL: /robotaxi-safety-record · machine-readable mirror: /robotaxi-safety-record.md
Want your own assistant to answer like this? Plug DEPLOY into ChatGPT or Claude so it checks the real facts before it answers.