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
23 records match for Zoox
20251 registryClear
Narrow it down
What happened
Country
Year
Property damage only2025-12NHTSASan Francisco30610-13661Pickup Truck · struck on the rear left, rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left, Rear Right
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- 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 occupied Zoox autonomous vehicle (Vehicle 1) was traveling west on [XXX] past [XXX] when it encountered debris in the lane. The Zoox vehicle braked hard for the debris and was then rear ended by a close-following Pickup (Vehicle 2) that was abruptly merging into the lane directly behind the Zoox vehicle. The Vehicle 2 driver then reversed and left the scene without attempting to exchange information. Shortly after, the Zoox vehicle cleared the scene, turned right onto [XXX], and pulled over to allow the riders to exit the vehicle. The Zoox vehicle then returned to base for inspection and was found to have sustained moderate damage. There were no reported injuries, and the police were notified.
cause not established30610-13661ZooxSource file ↗Property damage only2025-12NHTSASan Francisco30610-13660Passenger Car · struck on the front · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Rear Left
- 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 (Vehicle 1) was stationary in the right lane on northeast-bound [XXX] at [XXX] in San Francisco, stopped behind traffic at a red light. After the light turned green, the Zoox vehicle initially remained stopped to yield to an active police vehicle making a right turn onto [XXX] from the adjacent lane. During the subsequent green light cycle, as the Zoox vehicle began to proceed straight along [XXX], two passenger cars, including Vehicle 2, cut across its path from behind, attempting an illegal right turn onto [XXX] from a through lane. The Zoox vehicle braked hard, but contact was unavoidable, and Vehicle 2 clipped the Zoox vehicle's left front fender. The front-seat passenger of Vehicle 2 exited to inspect the Zoox vehicle before returning to their car and leaving the scene without exchanging information. The Zoox vehicle then cleared the scene and returned to base. Upon inspection, the Zoox vehicle was found to have sustained minor damage. Police were notified, and no injuries were reported.
cause not established30610-13660ZooxSource file ↗Property damage only2025-11NHTSALas Vegas30610-13376SUV · struck on the rear, rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear, Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left, 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 (Vehicle 1) was stopped behind traffic in the left turn lane on southbound [XXX] at [XXX] in Las Vegas, waiting at a traffic signal. After the light turned green, the Zoox vehicle initially remained stationary and then started moving forward. Shortly after resuming motion, the Zoox vehicle stopped and was rear-ended by the SUV (Vehicle 2) directly behind it. The Zoox vehicle sustained minor damage, and no injuries were reported. The police were not called.
cause not established30610-13376ZooxSource file ↗Not graded by the source2025-11NHTSAMiami30610-13377Motorcycle · struck on the left · proceeding straight
- Crash With
- Motorcycle
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Miami 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 retrofitted test vehicle (Vehicle 1) in autonomous mode was stopped, yielding to cross-traffic, on westbound [XXX] at [XXX] in Miami while waiting for an opportunity to proceed through the intersection and continue west on [XXX]. The Zoox vehicle inched forward and then stopped again for cross-traffic. The Zoox vehicle operator then disengaged from autonomous mode and proceeded to begin to cross [XXX]. While crossing, a motorcyclist traveling northbound on [XXX] at a high rate of speed collided with the driver's side front fender and door of the Zoox vehicle. The motorcycle and its operator fell to the ground. After the collision, the Zoox vehicle operator cleared the intersection and pulled over. Both the Zoox vehicle and the motorcycle sustained damage. Police and EMT personnel arrived at the scene, but the motorcycle operator was not transported from the scene.
cause not established30610-13377ZooxSource file ↗Minor injury2025-10NHTSASan Francisco30610-13121Passenger Car · struck on the rear left, rear right · making left turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear Left, Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Cloudy
- 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 autonomous mode was westbound on [XXX], preparing to make an unprotected left turn onto [XXX] in San Francisco. As the Zoox vehicle slowed approaching the intersection at [XXX], a left-turning vehicle in the oncoming lane accelerated abruptly. The Zoox vehicle braked in response to the oncoming vehicle, and was rear ended by a passenger car (Vehicle 2) traveling directly behind. The Zoox vehicle operator then disengaged from autonomy, and shortly after, continued through the intersection along [XXX] and pulled over to exchange information. The Zoox vehicle sustained minor damage to the rear end, and Vehicle 2 appears to have sustained moderate damage to the left front area and hood. The Zoox vehicle operator and the software operator, seated in the front passenger seat, reported injuries after the collision. The police were not called.
cause not established30610-13121ZooxSource file ↗Property damage only2025-10NHTSALas Vegas30610-11990SUV · struck on the front · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 14
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Right
- 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) in autonomous mode was traveling east towards the Passenger Pick-up area in Terminal 3 of [XXX] in Las Vegas. An SUV (Vehicle 2), traveling behind in the left adjacent lane, abruptly attempted to overtake and cut in front of the Zoox vehicle in an apparent attempt to change lanes to the right towards Terminal 3 Departures. The Zoox vehicle braked hard in response to the encroaching vehicle, and the operator then disengaged from autonomy and continued to brake, but contact could not be avoided. The right rear side of Vehicle 2 swiped the left front area of the Zoox vehicle. Both operators stopped after the collision and exchanged information. Both vehicles sustained moderate damage, and the Zoox vehicle was subsequently towed from the scene. There were no reported injuries, and police were not called.
cause not established30610-11990ZooxSource file ↗Property damage only2025-10NHTSALas Vegas30610-11856Heavy Truck · struck on the front left, front right · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Left, Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear, Rear 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 was traveling north in the right lane on [XXX], towards [XXX], in Las Vegas, when it encountered a slowing tractor-trailer (Vehicle 2) ahead in its lane, also traveling in the same direction. As the Zoox vehicle gradually slowed to a stop, the operator of Vehicle 2 began to reverse. The Zoox vehicle honked at Vehicle 2, but Vehicle 2 continued to reverse and made contact at low speed with the right front fender and bumper of the Zoox vehicle. The Zoox vehicle was towed from the scene for inspection and was found to have sustained minor damage. There were no reported injuries, and the police were not called.
cause not established30610-11856ZooxSource file ↗Property damage only2025-10NHTSALas Vegas30610-11847SUV · struck on the left, rear · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left, Rear
- SV Precrash Speed (MPH)
- 30
- CP Pre-Crash Movement
- Lane / Road Departure
- CP Contact Area
- Front Left
- 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 was traveling in the right lane on southbound [XXX] towards [XXX] in Las Vegas. The driver of an SUV (Vehicle 2) traveling ahead in the same direction in the adjacent lane to the left suddenly veered right into the path of the Zoox vehicle without using a turn signal, making contact with the left rear wheel and fender, and left side body panels, doors, and rocker. The Zoox vehicle then gradually braked to a stop in the right lane. The Zoox vehicle was towed from the scene for inspection. The Zoox vehicle sustained moderate damage, while Vehicle 2 appears to have sustained damage to the right side fender panel and front bumper. There were no reported injuries, and the police were not called. Zoox is submitting this updated report to correct a previous reporting error in the location field.
cause not established30610-11847ZooxSource file ↗Property damage only2025-10NHTSALas Vegas30610-13123Pickup Truck · struck on the rear right · making right turn
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Making Right Turn
- 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, southbound on [XXX], was gradually slowing and yielding to cross traffic in preparation for making a right turn at a traffic signal onto [XXX] in Las Vegas, when it was rear ended by a pickup (Vehicle 2) traveling directly behind. The Zoox vehicle came to a stop after the collision. The driver of Vehicle 2 initially exited their vehicle to check the vehicle, then completed the turn, stopped, and then exited their vehicle again to inspect for damage, signaling a "thumbs-up" to the Zoox rider. Vehicle 2 driver did not remain on scene to exchange information. The Zoox vehicle resumed operation and returned to base, where it was found to have sustained minor damage. There were no reported injuries. Camera footage from the Zoox vehicle shows that the Vehicle 2 driver was not looking ahead at the roadway before the time of contact.
cause not established30610-13123ZooxSource file ↗Property damage only2025-10NHTSASan Francisco30610-13122Passenger Car · struck on the front right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Left
- 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) in autonomous mode was traveling eastbound on [XXX] past [XXX] in San Francisco when it began to slow gradually for a nearly stopped passenger car (Vehicle 2) ahead in the same lane. The driver of Vehicle 2 then began reversing without using turn signals. The Zoox vehicle braked to a stop, and its operator disengaged autonomy, while vehicle 2 continued to reverse, steering left, seemingly attempting to pull into a parking spot in the curb lane adjacent to the stopped Zoox vehicle. During this maneuver, the right rear corner of Vehicle 2 swiped the left front corner of the Zoox vehicle. The Zoox vehicle sustained no damage, while Vehicle 2 incurred minor damage. No injuries were reported, and law enforcement was not notified.
cause not established30610-13122ZooxSource file ↗Minor injury2025-09NHTSAMiami30610-11903Non-Motorist: Other · struck on the rear left · making right turn
- Crash With
- Non-Motorist: Other
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- 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
- Cloudy
- Investigating Agency
- Miami 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 operating in autonomous mode was traveling in the right lane on southbound [XXX] and preparing to turn right onto [XXX] in Miami when it slowed to a stop in the crosswalk to properly yield to a left-turning vehicle in the oncoming lane. At that time, an e-scooterist westbound on [XXX] entered the crosswalk against the light at [XXX], then swerved and brushed the rear corner of the stopped Zoox vehicle. The e-scooter and the rider remained upright and continued onto the sidewalk along [XXX]. The Zoox vehicle operator then disengaged from autonomous mode and completed the turn shortly after. The Zoox vehicle operator checked on the e-scooterist, who appeared to have stopped to pick up something they dropped. Law enforcement and EMS were called as the e-scooterist reported injury. The EMS personnel provided the e-scooterist with an ice pack and then left the scene. Neither the Zoox vehicle nor the e-scooter sustained any damage.
cause not established30610-11903ZooxSource file ↗Property damage only2025-09NHTSALas Vegas30610-11752Passenger Car · struck on the rear left · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front
- 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 was operating at a reduced speed in lane #5 on westbound [XXX] towards Las Vegas Boulevard in Las Vegas, with a sedan (Vehicle 2) directly behind. The Zoox vehicle gradually slowed to a stop when it was rear ended by Vehicle 2. Vehicle 2 driver initially exited his vehicle to inspect both vehicles, but did not remain at the scene to exchange information. The Zoox vehicle resumed operation and cleared the scene. Shortly afterward, the Zoox vehicle slowed to a stop due to a low tire pressure fault and was subsequently towed. The low tire pressure was attributed to the crash. The Zoox vehicle sustained minor damage. There were no reported injuries, and the police were not notified.
cause not established30610-11752ZooxSource file ↗Property damage only2025-09NHTSASan Francisco30610-11902Heavy Truck · struck on the rear, top · proceeding straight
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear, Top
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Making Left 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 unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling northeast on a green traffic light on [XXX] at [XXX] in San Francisco. At that time, a box truck (Vehicle 2), heading southwest on [XXX], suddenly attempted an unprotected left turn onto [XXX]. The Zoox vehicle braked hard to yield to the rapidly approaching Vehicle 2, when the left side mirror assembly of Vehicle 2 made contact with the roof-mounted left rear sensor pod of the Zoox vehicle. The Zoox vehicle stopped after the contact, and the Vehicle 2 operator completed the turn onto [XXX] and pulled over. Shortly afterward, the Zoox vehicle cleared the intersection, pulled over, and then returned to base. The Zoox vehicle sustained sensor damage, and no injuries were reported.
cause not established30610-11902ZooxSource file ↗Property damage only2025-08NHTSASan Francisco30610-11497SUV · struck on the rear left · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Front
- 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 vehicle in autonomy was traveling north on [XXX] toward [XXX] in San Francisco and slowing for an SUV (Vehicle 2) ahead, also heading north on [XXX]. As the Zoox vehicle approached the nearly stopped Vehicle 2, it steered left to pass. The driver of Vehicle 2 then, without using a turn signal, abruptly began reversing in an apparent attempt to parallel park on the right side of [XXX]. The Zoox vehicle then braked to a near stop when it was struck on the right rear wheel by Vehicle 2 as it swung into a parking space. Shortly afterward, the Zoox vehicle was towed from the scene for inspection. The Zoox vehicle did not sustain damage, but the left front bumper of the SUV appeared to have minor damage. There were no reported injuries, and the police were not called.
cause not established30610-11497ZooxSource file ↗Property damage only2025-08NHTSASpring Valley30610-11587Heavy Truck · struck on the left, front · proceeding straight
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left, Front
- SV Precrash Speed (MPH)
- 11
- CP Pre-Crash Movement
- Entering Traffic
- CP Contact Area
- Front Left, 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 was traveling west along [XXX] toward [XXX] in Las Vegas when a tractor-trailer (Vehicle 2) operator failed to yield the right-of-way, failed to stop at a stop sign, and quickly pulled out of a driveway crossing the centerline and entering the Zoox vehicle's travel lane in an apparent attempt to make a left turn onto westbound [XXX]. The Zoox vehicle braked hard and steered right within its travel lane, but contact was unavoidable. The right corner of the front bumper and grille of the tractor-trailer made contact with the left front side of the Zoox vehicle. The Zoox vehicle then came to a complete stop. The operator of Vehicle 2 reversed off the roadway and stayed on-site to exchange information with the Zoox operations team. The Zoox vehicle was towed from the scene for inspection and was found to have sustained moderate damage. The front bumper, hood, and grille on Vehicle 2 appeared to be damaged. There were no reported injuries, and the police were not called.
cause not established30610-11587ZooxSource file ↗Property damage only2025-08NHTSASan Francisco30610-11563Pickup Truck · struck on the rear · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left
- 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 was stopped at a green traffic light on eastbound [XXX], waiting for traffic ahead to clear to turn left onto [XXX] in San Francisco. A pickup truck (Vehicle 2) was also stopped for the same traffic light, directly behind the Zoox vehicle. After the light turned yellow, the Vehicle 2 driver passed the stopped Zoox vehicle on the left side, striking the left rear fender, and proceeded through the red light. The Vehicle 2 driver did not stop to exchange information. Shortly afterward, the Zoox vehicle turned left onto [XXX] to clear the scene, briefly stopped again, and then pulled over. The Zoox vehicle was then towed for inspection. It sustained minor damage. There were no reported injuries and the police were not called.
cause not established30610-11563ZooxSource file ↗Property damage only2025-08NHTSASanta Monica30610-11696SUV · struck on the rear left, right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left, Right
- SV Precrash Speed (MPH)
- 10
- CP Pre-Crash Movement
- Entering Traffic
- CP Contact Area
- Front Left, Front, Front Right
- 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) in autonomous mode was traveling southwest on [XXX] towards [XXX] in Santa Monica when it was struck on the passenger side by an SUV (Vehicle 2), traveling southeast on [XXX], which failed to yield the right-of-way and entered the Zoox vehicle's travel path. The Zoox vehicle braked, the vehicle operator disengaged, continued to brake, and steered left, but contact was unavoidable. The Zoox vehicle sustained moderate damage, and Vehicle 2 also sustained damage. There were no reported injuries, and the police were not notified.
cause not established30610-11696ZooxSource 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 ↗Minor injury2025-07NHTSAParadise30610-11515Pickup Truck · struck on the rear left, rear, rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left, Rear, Rear Right
- SV Precrash Speed (MPH)
- 0
- 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
- Las Vegas Metro 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 (Vehicle 1) operating in autonomous mode was traveling south on [XXX] in the right lane and slowing for a red emergency traffic signal at [XXX] in Las Vegas. Shortly after the Zoox vehicle came to a stop, a pickup (Vehicle 2) following directly behind was rear ended by an SUV (Vehicle 3) that failed to stop. Vehicle 2 then rear ended the stopped Zoox vehicle. The police arrived at the scene. The driver of Vehicle 3 reported that their "head hurt" but declined medical attention. The Zoox vehicle sustained minor damage.
cause not established30610-11515ZooxSource file ↗Not graded by the source2025-07NHTSASan Francisco30610-11514Animal · struck on the front right, bottom · proceeding straight
- Crash With
- Animal
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right, Bottom
- SV Precrash Speed (MPH)
- 13
- CP Pre-Crash Movement
- Other, see Narrative
- 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) in autonomous mode was traveling in the left lane on southwest-bound [XXX] toward [XXX] in San Francisco when a ball, immediately followed by a dog, entered the roadway from between parked cars on the left side of [XXX] directly into the path of the Zoox vehicle. The Zoox vehicle braked in response, but its underbody made contact with the dog. The Zoox vehicle operator then disengaged autonomous mode and brought the vehicle to a stop. The Zoox vehicle operator then reversed the vehicle to free the dog. The dog owner did not indicate injuries to the dog at the scene. The dog and its owner then returned to the sidewalk and the Zoox vehicle operator drove the vehicle from the scene. The police were not called. Zoox subsequently received an email alleging injuries to the dog, "abrasions behind its left front leg and a possible cracked rib."
cause not established30610-11514ZooxSource file ↗Minor injury2025-07NHTSASpring Valley30610-11405Passenger Car · struck on the rear left, left, front left, rear, front, right · making left turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear Left, Left, Front Left, Rear, Front, Right
- SV Precrash Speed (MPH)
- 16
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left, Front, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Las Vegas 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 (Vehicle 1) operating in autonomous mode was traveling south on [XXX] and initiating a left turn from a dedicated signalized turn lane onto [XXX] in Las Vegas with a flashing yellow. The Zoox vehicle operator disengaged just prior to the signal turning from flashing yellow to green arrow as they continued to execute the left turn. At that time, a passenger car (Vehicle 2) traveling north on [XXX] failed to stop for the red traffic signal and entered the intersection at a high speed, colliding with the passenger side of the Zoox vehicle. The side impact caused the Zoox vehicle to roll onto its driver's side. Both vehicles sustained major damage with airbag deployments. The police and EMS arrived at the scene. The Zoox vehicle operator was transported to a medical facility by an ambulance, and Vehicle 2's driver was reported to have declined medical attention. Both vehicles were towed from the scene.
cause not established30610-11405ZooxSource 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 ↗Property damage only2025-06NHTSAParadise30610-11166Pickup Truck · struck on the rear left, rear, rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left, Rear, Rear Right
- SV Precrash Speed (MPH)
- 0
- 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
- 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 autonomous mode was traveling in the left through lane (lane #2) on westbound [XXX], approaching [XXX] in Las Vegas. The Zoox vehicle operator disengaged from autonomy after the traffic light at [XXX] transitioned from green to yellow and braked, bringing the Zoox vehicle to a stop, at which point it was rear-ended by a pickup truck (Vehicle 2) traveling behind. Both vehicles sustained minor damage however, the Zoox vehicle was towed from the scene as its operator was not comfortable driving it back. There were no reported injuries, and the police were not notified.
cause not established30610-11166ZooxSource file ↗