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
5 records match for Zoox
20261 registryClear
Narrow it down
What happened
Country
Year
Not graded by the source2026-06NHTSASan Francisco30610-15707Non-Motorist: Cyclist · struck on the right · proceeding straight
- Crash With
- Non-Motorist: Cyclist
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- San Francisco Police Department
- 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 was proceeding southbound on [XXX] after making a full stop at a 4-way-stop at [XXX] in San Francisco, when a fast-moving cyclist ran the stop sign from a downhill section of [XXX] from the right. The Zoox vehicle came to a stop in the intersection to yield to the approaching cyclist. The cyclist lost control, went over the handlebar, made contact with the left rear corner of the stopped Zoox vehicle, and then fell to the ground. The Zoox vehicle remained stopped in the intersection following the impact. Police and emergency services were notified and arrived at the scene. The cyclist was transported to a hospital via ambulance. The Zoox vehicle then resumed operation. There was no damage to the vehicle.
cause not established30610-15707ZooxSource file ↗Not graded by the source2026-05NHTSALas Vegas30610-15295Passenger Car · struck on the rear, rear right · proceeding straight
- Crash With
- Passenger Car
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear, Rear Right
- SV Precrash Speed (MPH)
- 3
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left, Front, 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 unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling north on [XXX], having just completed a left turn from [XXX] in Las Vegas, when it encountered debris in its path. The Zoox vehicle attempted to steer right, then executed hard braking to avoid the debris, at which point it was rear-ended by a passenger car (Vehicle 2) traveling directly behind it. Both vehicles came to a stop following the impact and were subsequently towed due to the damage sustained. Vehicle 2 suffered front-end damage and its driver-side frontal airbags deployed, while the Zoox vehicle sustained moderate damage to its rear. Law enforcement was notified of the event, but did not respond to the scene. Following the impact, Zoox staff inquired if emergency medical services should be called; the driver replied that the police had already been contacted. The driver of Vehicle 2 informed Zoox staff at the scene that they were "shaken" and "pretty bruised".
cause not established30610-15295ZooxSource file ↗Not graded by the source2026-03NHTSAMiami30610-14554Heavy Truck · struck on the front left · proceeding straight
- Crash With
- Heavy Truck
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 17
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Rear Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Miami Dade Police Department
- 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 in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching Zoox vehicle. The door struck the Zoox vehicle's right-side A-pillar, windshield, and sensor assembly. After the impact, the trailer's door rebounded and struck the operator behind it. The Zoox vehicle operator then disengaged from autonomous mode. The police and emergency personnel arrived at the scene. The operator was transported by an ambulance from the scene.
cause not established30610-14554ZooxSource file ↗Not graded by the source2026-02NHTSALas Vegas30610-14341SUV · struck on the front left · proceeding straight
- Crash With
- SUV
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 7
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front
- 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 occupied Zoox autonomous vehicle was traveling northeast on [XXX], passing through the intersection of [XXX] in Las Vegas, with a green signal, when an SUV (Vehicle 2) violated the Zoox vehicle's right of way and abruptly entered its travel path. The Zoox vehicle braked hard and attempted to veer left, but the right front fender of the Zoox vehicle made contact with the left front fender and bumper of Vehicle 2. The driver of Vehicle 2 briefly stopped and then drove away from the scene. The Zoox vehicle was found to have sustained minor damage. At the time of the incident, the passengers did not report any injuries, and police were not notified. On March 2, 2026, the passengers notified Zoox Support that they "sustained multiple injuries and have experienced persistent and worsening pain and cognitive symptoms since the impact".
cause not established30610-14341ZooxSource file ↗Not graded by the source2026-01NHTSASan Francisco30610-13818Passenger Car · struck on the right · proceeding straight
- Crash With
- Passenger Car
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 15
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- San Francisco Police Department
- 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 began to proceed on a fresh green traffic signal on westbound [XXX] at [XXX] when the driver of a stationary passenger vehicle (Vehicle 2), parallel-parked in the curb lane, rapidly opened the driver door into the path of the approaching Zoox vehicle. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The right side front fender, wheels, bodyside, and door panels made contact with the outside edge of the opening door of Vehicle 2. The Zoox vehicle came to an immediate stop and was later towed from the scene to be inspected for damage. First responders arrived at the scene. The passenger of the Zoox vehicle did not report any injuries. Later media stories reported the driver of Vehicle 2 had a "smashed hand" and his "hand was hurting, and that he was also experiencing pain to his neck area and lower back" based on a third party's account, and that the driver "declined their offer to take him to the hospital." Zoox vehicle camera footage shows clearly that no part of the robotaxi came into contact with the driver themselves, and that their hands, leg, and body did not interact with either the robotaxi or the parked vehicle's door at any moment during the contact event.
cause not established30610-13818ZooxSource file ↗