Find a safety record
Every incident, injury and recall on file, from the national registries that publish them. Search a maker, a model, a town or a reference number — or narrow by what happened. Each record is the registry's own text, reproduced without rewriting, with the reference that locates it at the source. Registries count different things, so a total is a count of FILINGS and never a measure of how dangerous something is. How the record was collected.
Or jump to a maker
3 records match for Zoox
2025–20261 registryClear
Narrow it down
What happened
Country
Year
No injury reported2026-02NHTSALas Vegas30610-14340Pickup Truck · struck on the rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- ZOOX
- Model
- Zoox
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
An occupied Zoox autonomous vehicle traveling south on [XXX] was stopped for a red signal at [XXX] in Las Vegas. After the light turned green, and before the Zoox vehicle started to move, a Pickup (Vehicle 2) traveling directly behind it rear-ended it. Shortly thereafter, both vehicles traveled a few feet ahead and pulled over. The passengers exited the Zoox vehicle onto the sidewalk. After exchanging information, the Zoox vehicle returned to base for inspection, where it was found to have sustained moderate damage. No injuries were reported, and police were not notified.
cause not established30610-14340ZooxSource file ↗No injury reported2025-07NHTSAWinchester30610-11513Non-Motorist: Cyclist · struck on the rear left · making right turn
- Crash With
- Non-Motorist: Cyclist
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Other, see Narrative
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- None
- Make
- ZOOX
- Model
- Zoox
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
An unoccupied Zoox vehicle in autonomous mode was traveling in the right turn lane on southbound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. At that time, an e-cyclist was traveling south on the sidewalk adjacent to southbound [XXX]. As the Zoox vehicle slowed to execute its turn, the e-cyclist rapidly approached the crosswalk in the path ahead of the Zoox vehicle. The Zoox vehicle braked to yield to the approaching e-cyclist. The e-cyclist then veered left and accelerated into the roadway, making contact with the right rear side of the nearly stopped Zoox vehicle. The e-cyclist fell to the ground behind the Zoox vehicle. The Zoox vehicle then started to move and completed the right turn onto [XXX] and completed its mission. The cyclist appears to have ridden away from the scene. A bystander reported the event to Zoox. There was minor damage to the Zoox vehicle, and information was not exchanged with the e-cyclist. The police were later notified.
cause not established30610-11513ZooxSource file ↗No injury reported2025-06NHTSASan Francisco30610-11331Passenger Car · struck on the rear · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 9
- CP Pre-Crash Movement
- Crossing into Opposing Lane
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Highlander
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
A Zoox vehicle (Vehicle 1), operating in manual mode, was heading south on [XXX], in the southbound lane, approaching [XXX] in San Francisco, when it encountered a passenger car (Vehicle 2) traveling north and occupying both the northbound and southbound lanes on [XXX]. The Zoox vehicle slowed and moved to the right for the oncoming Vehicle 2 however, as Vehicle 2 passed, its driver's side mirror made contact with the driver's side rear of the Zoox vehicle. The driver of Vehicle 2 failed to stop and exchange information. The Zoox vehicle did not sustain any damage, but Vehicle 2 appeared to have sustained minor damage to its driver's side mirror. There were no reported injuries, and the police were not notified.
cause not established30610-11331ZooxSource file ↗