🚦

Zoox Self-Driving Crashes

170 crashes involving Zoox's self-driving vehicles were reported to the National Highway Traffic Safety Administration between July 2021 and September 2026, 5.6% of all reported self-driving crashes. In 37% of them the Zoox vehicle was stopped or parked; 21% involved a reported injury.

Crashes reported: 170
Share of all: 5.6%; #2 of 35 companies
Vehicle stopped or parked: 37%
Injury reported: 35
Serious or fatal: 0
Cities: 15

Crashes per month

Zoox crashes reported to NHTSA per month

Peak: March 2026, 12 crashes

View as a table

Month	Crashes
July 2021	2
August 2021	1
September 2021	2
October 2021	1
November 2021	0
December 2021	0
January 2022	1
February 2022	1
March 2022	2
April 2022	1
May 2022	1
June 2022	3
July 2022	1
August 2022	3
September 2022	1
October 2022	2
November 2022	4
December 2022	0
January 2023	2
February 2023	4
March 2023	2
April 2023	1
May 2023	2
June 2023	0
July 2023	0
August 2023	0
September 2023	1
October 2023	2
November 2023	1
December 2023	0
January 2024	3
February 2024	3
March 2024	2
April 2024	3
May 2024	1
June 2024	0
July 2024	4
August 2024	2
September 2024	0
October 2024	4
November 2024	0
December 2024	2
January 2025	7
February 2025	4
March 2025	4
April 2025	4
May 2025	6
June 2025	4
July 2025	4
August 2025	4
September 2025	3
October 2025	6
November 2025	2
December 2025	2
January 2026	3
February 2026	6
March 2026	12
April 2026	6
May 2026	4
June 2026	9
July 2026	6
August 2026	8
September 2026	1

A rising line usually means a growing fleet: more vehicles and more miles, in more cities. Without the miles, the count alone cannot say whether Zoox's vehicles crash more or less often over time.

Most serious injury reported

Moderate injury0.6% · 1 crashes
Minor injury20% · 34 crashes
No injuries reported73.5% · 125 crashes
Unknown5.9% · 10 crashes

What the Zoox vehicle collided with

Another vehicle84.7% · 144 crashes
Cyclist4.1% · 7 crashes
Other4.1% · 7 crashes
Scooter, skateboard or other road user2.9% · 5 crashes
Fixed object2.4% · 4 crashes
Animal1.2% · 2 crashes
Pedestrian0.6% · 1 crashes

Who could take the wheel

Safety driver on board67.6% · 115 crashes
No one on board to drive31.2% · 53 crashes
Remote operator only0.6% · 1 crashes
Unknown0.6% · 1 crashes

Where they happened

San Francisco, CA 84 crashes
Las Vegas, NV 45 crashes
Paradise, NV 12 crashes
Miami, FL 6 crashes
Spring Valley, NV 6 crashes
Austin, TX 5 crashes
San Mateo, CA 2 crashes
Santa Monica, CA 2 crashes
Seattle, WA 2 crashes
Culver City, CA 1 crash

Zoox in the news

Every story about Zoox, newest first, with the broadcasts that covered it.

Other companies

Waymo 2,382 crashes
Cruise 156 crashes
Avride 84 crashes
May Mobility 48 crashes
Tesla 36 crashes
Motional 28 crashes
Aurora 24 crashes
Argo AI 20 crashes

Every company, ranked.

How to read these numbers

A count is not a rate. A company that drives more miles reports more crashes. NHTSA does not publish the miles behind these reports, so nothing here is divided by distance, and a longer bar does not mean a less safe car.
Being in a crash is not causing it. The reports do not assign fault, and many of these crashes happened while the self-driving vehicle was stopped or parked, often hit from behind.
Companies file these reports themselves. NHTSA publishes them as filed: they may be incomplete or unverified, injuries are as alleged, and some details are withheld as confidential business information.
One crash, one row. A crash can get several reports, from updates or from more than one company (an operator and its fleet partner); we count it once, using NHTSA's own incident ID.
The rules changed in June 2025. NHTSA amended what must be reported and when, so counts before and after that month are not directly comparable.
Driver assistance is not here. Crashes with systems like Tesla Autopilot or GM Super Cruise in customers' cars are a separate NHTSA dataset with different rules. 15 reports filed in the self-driving file that name a driver-assistance system are left out.