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
38 records match for Zoox
20261 registryClear
Narrow it down
What happened
Country
Year
Property damage only2026-07NHTSAAustin30610-15722Passenger Car · struck on the rear left, rear, rear right · stopped
- Crash With
- Passenger Car
- 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
- Cloudy
- Investigating Agency
- Austin 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 traveling west on [XXX] toward [XXX] in Austin when it braked to a stop for a pedestrian and dog on a leash entering the crosswalk. A passenger car (Vehicle 2) traveling directly behind failed to slow down and rear ended the stopped Zoox vehicle. Shortly after, the Vehicle 2 driver reversed, inspected both vehicles, then returned to their vehicle and remained at the scene. The Zoox vehicle passenger reported feeling "dazed" and "kind of woozy" and requested emergency services. The police were notified and arrived at the scene. The Zoox fleet response team also arrived, and information was exchanged with the other party. Just as the Zoox vehicle started moving, an audible noise came from its fender, so it pulled over and was towed for further inspection. The vehicle was found to have sustained moderate damage to its rear end.
cause not established30610-15722ZooxSource file ↗Property damage only2026-06NHTSALas Vegas30610-15638Passenger Car · struck on the rear, rear right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- 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
- Cloudy, Rain
- Investigating Agency
- Las Vegas Metro PD
- 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 heading south on [XXX] in Las Vegas, slowing down for a red traffic signal at the [XXX] intersection, when a trailing passenger car (Vehicle 2) rear-ended it. The Zoox vehicle operator subsequently disengaged from autonomy. The collision resulted in moderate rear-end damage to the Zoox vehicle and major frontal damage to Vehicle 2, including frontal airbag deployment. Both vehicles were towed from the scene. Police responded to the scene, and no injuries were reported.
cause not established30610-15638ZooxSource file ↗Minor injury2026-06NHTSALas Vegas30610-15541Pickup Truck · struck on the rear left, rear, rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Minor W/ 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 Right
- 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 north on [XXX], approaching the intersection of [XXX] in Las Vegas, when an active emergency vehicle, with lights and sirens, was westbound on [XXX] and rapidly approaching the intersection. The Zoox vehicle appropriately braked hard to a stop to yield to the approaching active emergency vehicle. A pickup truck (Vehicle 2), traveling behind the Zoox vehicle, failed to stop and rear ended the stopped Zoox vehicle. The police were notified and arrived at the scene. Zoox vehicle's camera footage shows that the driver of Vehicle 2 was holding a device in their right hand leading up to the collision. The driver of Vehicle 2 was cited for failing to decrease speed. The Zoox vehicle was towed from the scene and found to have sustained moderate damage. The passengers initially declined medical attention; however, after the Zoox fleet response team arrived, one passenger requested transport to a hospital.
cause not established30610-15541ZooxSource file ↗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 ↗Property damage only2026-06NHTSALas Vegas30610-15540Passenger Car · struck on the left, rear, 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
- Left, Rear, Front
- SV Precrash Speed (MPH)
- 25
- 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
- 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 north on [XXX] in the left through lane, approaching [XXX] in Las Vegas, when a passenger vehicle (Vehicle 2) in the outer left-turn lane (towards Aria Place) abruptly changed lanes to the right and cut in front of the Zoox vehicle. The Zoox vehicle braked and attempted to steer right to avoid the collision, but the right side of Vehicle 2 swiped the left side door and body panels, and fenders of the Zoox vehicle. The driver of Vehicle 2 departed the scene without exchanging information. The Zoox vehicle was towed from the scene and was found to have sustained moderate damage. There were no reported injuries.
cause not established30610-15540ZooxSource file ↗Property damage only2026-06NHTSALas Vegas30610-15628SUV · struck on the rear right · making left turn
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear Right
- 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
- 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 making a left turn from eastbound [XXX] onto northbound [XXX] in Las Vegas when an active emergency vehicle, with lights and sirens, was rapidly approaching the intersection and conducting a right turn onto northbound [XXX]. The Zoox vehicle was slowing to yield to the approaching active emergency vehicle, when an SUV (Vehicle 2) traveling behind it failed to stop, and rear ended the slowing Zoox vehicle. Two other passenger vehicles (Vehicles 3 & 4) were following behind Vehicle 2. Vehicle 4 appeared to have made contact with Vehicle 3 from behind. Neither Vehicle 3 nor Vehicle 4 contacted the Zoox vehicle, and it does not appear that either contacted Vehicle 2. The driver of Vehicle 2 then pulled over ahead and contacted Zoox support to exchange information. The police were notified, but did not arrive at the scene. The Zoox vehicle was towed from the scene and found to have sustained moderate damage.
cause not established30610-15628ZooxSource file ↗Property damage only2026-06NHTSAAustin30610-15465Pickup Truck · struck on the rear left · making left turn
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 7
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left
- 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, operating in autonomous mode, was stopped in the westbound left-turn lane of [XXX], yielding to oncoming traffic to turn left onto [XXX] in Austin under a flashing yellow arrow. Eastbound traffic on [XXX] was backed up and slowing down. After receiving a hand gesture from the driver of a slowing SUV in the oncoming lane, the Zoox vehicle operator disengaged from autonomy and proceeded with the left turn. At that time, a pickup truck (Vehicle 2) traveling in the right lane of eastbound [XXX] quickly approached the intersection. Although the driver of Vehicle 2 attempted to steer left, the vehicle collided with the rear right area of the Zoox vehicle in the intersection. Vehicle 2's left side subsequently made contact with the front right corner of the oncoming SUV. Both the Zoox vehicle and Vehicle 2 sustained moderate damage, and the Zoox vehicle was towed. No injuries were reported, and police were notified but did not respond to the scene.
cause not established30610-15465ZooxSource file ↗Property damage only2026-05NHTSAMiami30610-15480Pickup Truck · struck on the rear left · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 1
- 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
- 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 gradually slowing for oncoming traffic while preparing to turn left onto westbound [XXX] from [XXX] in Miami, when a pickup truck (Vehicle 2) rear-ended it while executing a right turn from [XXX] onto [XXX]. The Zoox vehicle sustained moderate damage, and no injuries were reported. Law enforcement was notified but did not arrive at the scene.
cause not established30610-15480ZooxSource file ↗Property damage only2026-05NHTSASan Francisco30610-15018Pickup Truck · struck on the left · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 8
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Front, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Cloudy
- 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 south on [XXX] on a green light at [XXX] in San Francisco when a pickup truck (Vehicle 2) executed an abrupt left turn from northbound [XXX] and accelerated into the Zoox vehicle's right-of-way. The Zoox vehicle braked hard, but contact was unavoidable. Vehicle 2's front bumper struck the Zoox vehicle's left side door and body panels. After reversing, Vehicle 2 cleared the intersection, pulled over temporarily, and then left without exchanging information. Shortly afterward, the Zoox vehicle cleared the intersection, pulled over, and was towed for inspection. It was found to have sustained moderate damage. No injuries were reported, and police were not called.
cause not established30610-15018ZooxSource file ↗Property damage only2026-05NHTSASan Francisco30610-15481Passenger Car · struck on the front left · 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 Left
- SV Precrash Speed (MPH)
- 10
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Rear
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- 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 manual mode was traveling south on [XXX] past [XXX] in San Francisco when it made contact was made with the left side quarter panel and rear bumper of a parked passenger car (Vehicle 2). The Zoox vehicle's front passenger-side fender sustained damage. No injuries were reported, and police were not notified.
cause not established30610-15481ZooxSource 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 ↗Minor injury2026-04NHTSASan Francisco30610-15062Passenger Car · struck on the rear left, rear, rear right · stopped
- Crash With
- Passenger Car
- 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
- 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 north on [XXX] was stopped for a signal at [XXX] in San Francisco, with a passenger vehicle (Vehicle 2) stopped directly behind it. As the light turned green, the Zoox vehicle began to proceed but stopped for traffic and was rear ended by Vehicle 2. Vehicle 2's driver immediately left the scene without exchanging information. Shortly after, the Zoox vehicle proceeded straight and pulled over in the right lane adjacent to the bike lane, and the passengers exited. One passenger reported feeling "whiplash" but declined medical treatment. The police were notified. The Zoox vehicle sustained minor rear-end damage.
cause not established30610-15062ZooxSource file ↗Property damage only2026-04NHTSASan Francisco30610-15063Passenger Car · struck on the left · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Left, Rear 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 operating in autonomous mode was stopped behind traffic at a red signal on northbound [XXX] at [XXX] in San Francisco. At this time, a passenger vehicle (Vehicle 2) was reversing from a parking spot on the left side of the roadway. The Zoox vehicle honked at the approaching Vehicle 2, but Vehicle 2's rear end made contact with the Zoox vehicle's driver door. The Zoox vehicle operator then disengaged from autonomous mode. The Zoox vehicle sustained minor damage. No injuries were reported, and police were not notified.
cause not established30610-15063ZooxSource file ↗Property damage only2026-04NHTSALas Vegas30610-14732Heavy Truck · struck on the front left, front, 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, Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- 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 in the left lane traveling north on [XXX] past [XXX] when it slowed for a tractor-trailer (vehicle 2) that was reversing from the roadway into a loading bay on the right side of the road. While reversing, the tractor-trailer swung over into the left lane, and the left side of Vehicle 2's trailer made contact with the stopped Zoox vehicle's front fascia and sensor pods. The Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
cause not established30610-14732ZooxSource file ↗Minor injury2026-04NHTSALas Vegas30610-15064Passenger Car · struck on the rear · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- 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 occupied Zoox autonomous vehicle, gradually slowed to a stop behind traffic on southbound [XXX] past [XXX] in Las Vegas, when it was rear ended by a passenger vehicle (Vehicle 2) traveling directly behind. The Zoox vehicle honked at the approaching Vehicle 2, but its driver failed to stop in time. Vehicle 2's driver left the scene without exchanging information. The Zoox vehicle did not sustain any damage. No injuries were reported at that time. Police were notified. One of the passengers later contacted Zoox support and stated, "I began experiencing significant neck pain consistent with a possible soft tissue injury." The passenger has not provided any documentation to Zoox regarding their alleged injury.
cause not established30610-15064ZooxSource file ↗Property damage only2026-04NHTSALas Vegas30610-15065Pickup Truck · struck on the 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, Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Making Right Turn
- 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 preparing to turn right from a hotel driveway onto southbound [XXX] in Las Vegas, and came to a gradual stop to yield to cross traffic when it was rear ended by a pickup (Vehicle 2) traveling directly behind. The Zoox vehicle honked at the approaching Vehicle 2, but Vehicle 2's driver failed to stop in time. Vehicle 2's driver then went around the stopped Zoox vehicle, briefly stopped in the right lane, activated their hazard lights, and then proceeded to leave the area. Upon inspection, the Zoox vehicle was found to have sustained moderate damage to its rear. No injuries were reported and police were not notified.
cause not established30610-15065ZooxSource file ↗Property damage only2026-04NHTSALas Vegas30610-14656Passenger Car · struck on the front left · 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 Left
- SV Precrash Speed (MPH)
- 21
- CP Pre-Crash Movement
- Entering Traffic
- 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 traveling north on [XXX] past [XXX] in Las Vegas when a passenger car (Vehicle 2) abruptly attempted to turn right onto [XXX] from a parking lot, violating the Zoox vehicle's right-of-way. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The Zoox vehicle's right-front fender, wheel, and fascia contacted Vehicle 2's left-front bumper and headlight. Both vehicles sustained damage, and the Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
cause not established30610-14656ZooxSource file ↗Property damage only2026-03NHTSASan Francisco30610-14388Passenger Car · struck on the front · changing lanes
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Changing Lanes
- SV Contact Area
- Front
- 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 (Vehicle 1), traveling southwest on [XXX] in San Francisco, was stopped mid-way through a lane-change maneuver (from lane #2 to lane #1) in stop-and-go traffic, when a passenger car (Vehicle 2) in lane #1 accelerated toward the stopped Zoox vehicle and struck its left front wheel. The Zoox vehicle was towed from the scene for inspection and was found to have sustained no damage. Vehicle 2's front bumper appears to have sustained minor damage. No injuries were reported. Police were notified but did not arrive at the scene. The Zoox vehicle's video footage shows that Vehicle 2's driver was not looking at the road ahead before or at the time of contact.
cause not established30610-14388ZooxSource file ↗Property damage only2026-03NHTSALas Vegas30610-14263Heavy Truck · struck on the front left · making left turn
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Lane / Road Departure
- CP Contact Area
- 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 occupied Zoox autonomous vehicle traveling southeast on [XXX] stopped behind traffic in the outer left turn lane (lane #2) for a red traffic signal at [XXX] in Las Vegas. A dumpster-hauling truck (Vehicle 2) was stopped in the adjacent through-lane (lane #3). Shortly after the light turned green and the Zoox vehicle began its left turn, the Vehicle 2 operator abruptly steered left, accelerated, and cut into the Zoox vehicle's path, violating its right of way. The Zoox vehicle braked hard; however, Vehicle 2 struck the Zoox vehicle's right-side front wheel, fender, roof-mounted sensor unit, and body panel. The Zoox vehicle was towed from the scene and sustained moderate damage. No injuries were reported, and police were not called.
cause not established30610-14263ZooxSource 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 ↗Property damage only2026-03NHTSALas Vegas30610-14342Passenger Car · struck on the front left, right · 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 Left, Right
- SV Precrash Speed (MPH)
- 25
- CP Pre-Crash Movement
- Making Right Turn
- 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 traveling northeast on [XXX], approaching [XXX] in Las Vegas, when a passenger car (Vehicle 2) abruptly turned right onto [XXX] from a parking lot on the right, violating the Zoox vehicle's right-of-way. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The Zoox vehicle's right front fender and wheel, and its right rear door panel, contacted Vehicle 2's left fender, wheel, headlight, and quarter panel. Both vehicles sustained damage, and the Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
cause not established30610-14342ZooxSource file ↗Property damage only2026-03NHTSALas Vegas30610-14662SUV · struck on the rear · stopped
- Crash With
- SUV
- 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
- Passing
- 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 LasVegas PUDO location when an SUV (Vehicle 2), that was stopped behind for passenger pick up, attempted to pass on the left and lightly swiped the left rear corner of the Zoox vehicle. The Vehicle 2 driver did not stop at the scene to exchange information. The Zoox vehicle resumed operation to return to base for inspection, where it was found to have sustained minor damage. There were no reported injuries.
cause not established30610-14662ZooxSource file ↗Property damage only2026-03NHTSALas Vegas30610-14519SUV · 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
- 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 started to move after a gradual stop at a 3-way stop sign preparing to turn right onto eastbound [XXX] in Las Vegas, when it braked to an abrupt stop as cross-traffic failed to stop and yield the right-of-way. It was then rear ended by an SUV (Vehicle 2) traveling directly behind. The Zoox vehicle was towed from the scene and was found to have sustained moderate damage to the rear. No injuries were reported and police were not notified. 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-14519ZooxSource file ↗Property damage only2026-03NHTSASan Francisco30610-14664Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Parking Maneuver
- 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 unoccupied Zoox autonomous vehicle (Vehicle 1), traveling northeast on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Shortly after, one of the parked vehicles (Vehicle 2) was attempting to pull out of the parking spot when the Zoox vehicle's passenger approached and activated its doors. The Zoox vehicle's right rear door contacted Vehicle 2's front bumper. The right rear door on the Zoox vehicle was damaged; no injuries were reported, and police were not notified.
cause not established30610-14664ZooxSource file ↗Property damage only2026-03NHTSASan Francisco30610-14663Passenger Car · struck on the right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Left, Rear, Rear 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 west on [XXX] past [XXX] in San Francisco when it encountered a Pickup truck reversing into its lane from a perpendicular parking spot ahead. The Zoox vehicle slowed to a stop, and while it waited for the lane to clear, a passenger car (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 passenger-side front door of the Zoox vehicle. The Zoox vehicle operator then disengaged from autonomous mode. Both vehicles sustained damage. No injuries were reported, and the police were not notified.
cause not established30610-14663ZooxSource file ↗Property damage only2026-03NHTSAAustin30610-14264Heavy Truck · struck on the 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
- Front
- SV Precrash Speed (MPH)
- 2
- 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
- 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, traveling southwest on [XXX] towards [XXX] in Austin, was slowing for a garbage truck (Vehicle 2) approaching from the opposite direction when Vehicle 2 struck it head-on. The Zoox vehicle sustained moderate damage to the left front area, including the hood, bumper, headlight, fender, A-pillar hinge, and driver door. Both parties exchanged information. Police were notified and arrived at the scene. No injuries were reported.
cause not established30610-14264ZooxSource file ↗Property damage only2026-03NHTSALas Vegas30610-14366SUV · struck on the right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Left, Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- 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 east at low speed in a parking lot along [XXX] in Las Vegas when an SUV (Vehicle 2) began reversing out of its parking spot. The Zoox vehicle slowed and attempted to steer left, but it could not before Vehicle 2 struck the Zoox vehicle's right-side rear door, body panel, and wheel. The Zoox vehicle sustained moderate damage and was towed from the scene. No injuries were reported, and police were not notified.
cause not established30610-14366ZooxSource file ↗Property damage only2026-03NHTSASan Francisco30610-14419Passenger Car · struck on the rear · stopped
- Crash With
- Passenger Car
- 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
- Passing
- 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.
A Zoox autonomous vehicle, traveling west on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Just after the passenger entered the Zoox vehicle, a passenger car (Vehicle 2) traveling behind attempted to pass on the left and swiped the Zoox vehicle's left rear fender. The Zoox vehicle was towed from the scene and was found to have sustained minor damage. No injuries were reported, and police were not notified.
cause not established30610-14419ZooxSource file ↗Property damage only2026-03NHTSASan Francisco30610-14665Passenger Car · struck on the front left, front, 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 Left, Front, Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Traveling Wrong Way
- CP Contact Area
- Rear 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 stopped behind traffic in the through lane on westbound [XXX] at a red traffic light at [XXX] in San Francisco with a passenger car (Vehicle 2), stopped directly ahead. After both vehicles were fully stopped, Vehicle 2 began moving backward toward the still-stopped Zoox vehicle, and even though the Zoox vehicle honked its horn, Vehicle 2 continued to move backward and made contact with the Zoox vehicle's front bumper. The Zoox vehicle operator then disengaged from autonomy. The Zoox vehicle sustained minor damage. No injuries were reported, and police were not notified.
cause not established30610-14665ZooxSource file ↗Minor injury2026-02NHTSASanta Monica30610-14167SUV · struck on the rear left, rear, rear right · changing lanes
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Changing Lanes
- SV Contact Area
- Rear Left, Rear, Rear Right
- SV Precrash Speed (MPH)
- 17
- CP Contact Area
- Front Left, Front, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- City of Santa Monica PD
- 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 southeast on [XXX], preparing to change lanes to the right to turn onto [XXX] in Santa Monica, when it was hit on the right rear corner (rear bumper, hatch, right rear wheel, and right rear quarter panel) by an SUV (Vehicle 2). The Zoox vehicle stopped facing southwest on [XXX], with the front of Vehicle 2 still engaged with the right rear of the Zoox vehicle. The Zoox vehicle sustained severe rear damage, including damage to data recording systems. Vehicle 2 had major damage to its front end. Airbags deployed in both vehicles, and they were towed from the scene. Police and emergency responders arrived to assist, and the driver of vehicle 2 was detained. The Zoox vehicle operator and two passengers reported soreness and a headache after the collision.
cause not established30610-14167ZooxSource file ↗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 ↗Property damage only2026-02NHTSASan Francisco30610-14339Non-Motorist: Cyclist · struck on the rear left · making right turn
- Crash With
- Non-Motorist: Cyclist
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- NM Crossing Roadway
- 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 was traveling in the right lane on northwest-bound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. Partway through the right turn, the Zoox vehicle further slowed to yield to a pedestrian crossing [XXX], and at that time, a cyclist traveling northwest on the adjacent sidewalk rapidly entered the crosswalk. The Zoox vehicle braked to yield to the approaching cyclist, and the cyclist made contact with the right rear side of the nearly stopped Zoox vehicle. The bicycle fell to the ground, but its rider remained upright. The cyclist picked up their bicycle and rode away from the scene. Shortly after, the Zoox vehicle resumed operation to return to base. There was minor damage to the Zoox vehicle. There were no reported injuries, and police were not notified.
cause not established30610-14339ZooxSource 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 ↗Property damage only2026-02NHTSASan Francisco30610-14152Passenger Car · struck on the rear left, rear, rear right · stopped
- Crash With
- Passenger Car
- 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
- Making Left Turn
- CP Contact Area
- Front Left, Front, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy, Rain
- 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 came to an abrupt stop on [XXX] just after turning left from northbound [XXX] in San Francisco, and was rear ended by a passenger vehicle (Vehicle 2) traveling directly behind it. The Zoox vehicle operator disengaged from autonomy after the impact. There were no reported injuries, and police were not called. The Zoox vehicle was towed from the scene and was found to have sustained moderate damage to its rear end.
cause not established30610-14152ZooxSource file ↗Property damage only2026-02NHTSASan Francisco30610-14026SUV · struck on the front left · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 9
- CP Pre-Crash Movement
- Entering Traffic
- 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 traveling east on [XXX] toward [XXX] in San Francisco when an SUV (Vehicle 2) that had been stationary while in an apparent attempt to parallel park along the right curb suddenly pulled out into the path of the approaching Zoox vehicle. The Zoox vehicle braked hard and attempted to steer left, but the right front wheel and body panel of the Zoox vehicle made contact with the left front wheel and panel of Vehicle 2. The Zoox vehicle was towed from the scene for inspection and was found to have sustained minor damage. There were no reported injuries, and police were not notified
cause not established30610-14026ZooxSource file ↗Property damage only2026-01NHTSASan Francisco30610-13662Heavy 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 (Vehicle 1) was traveling east on [XXX] near [XXX] in San Francisco. It began to slow down for a stopped box truck (Vehicle 2) in the same lane, which had an open liftgate. As the Zoox vehicle was preparing to maneuver around, Vehicle 2 began to reverse. The Zoox vehicle came to a stop however, Vehicle 2 continued reversing. The Zoox vehicle honked, but Vehicle 2's open liftgate made contact with the right front fender and front fascia of the Zoox vehicle. The Zoox vehicle was towed from the scene and was found to have sustained minor damage. The police were notified, and no injuries were reported.
cause not established30610-13662ZooxSource 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 ↗Minor injury2026-01NHTSASan Francisco30610-14090SUV · struck on the front left, right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left, Right
- SV Precrash Speed (MPH)
- 16
- CP Pre-Crash Movement
- Entering Traffic
- 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 autonomous mode was traveling northeast on [XXX] toward [XXX] in San Francisco. At that time, an SUV (Vehicle 2) traveling ahead pulled into the parking lane on the right. Just as the Zoox vehicle was approaching, Vehicle 2 suddenly swerved into the Zoox vehicle's lane without using a turn signal. The Zoox vehicle braked hard and attempted to steer left to avoid the collision. The vehicle operator then disengaged autonomy and continued braking, but contact was unavoidable. The left front of Vehicle 2 struck the right front of the Zoox vehicle. The Zoox vehicle sustained moderate damage, and the right rear passenger reported "experiencing soreness" after the collision. The police were not called.
cause not established30610-14090ZooxSource file ↗