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
13 records match
20261 registryClear
Narrow it down
What happened
Country
Year
Not graded by the source2026-07NHTSAWaymoSan Francisco30270-15669SUV · struck on the rear · proceeding straight
- Crash With
- SUV
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 32
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
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.
On July [XXX], 2026 at 1:10 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northeastbound in the second to the rightmost lane on [XXX] when an SUV traveling northeastbound on [XXX] at a high rate of speed, partially in the second to the rightmost lane and partially in the left lane, began to change lanes to the left lane as it approached the Waymo AV from behind. The SUV attempted to pass the Waymo AV to the left, and the front right side of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the passenger car sustained unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-15669WaymoSource file ↗Not graded by the source2026-06NHTSAZooxSan Francisco30610-15707Non-Motorist: Cyclist · struck on the right · proceeding straight
- Crash With
- Non-Motorist: Cyclist
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- San Francisco Police Department
- Make
- ZOOX
- Model
- Zoox
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
An occupied Zoox autonomous vehicle was proceeding southbound on [XXX] after making a full stop at a 4-way-stop at [XXX] in San Francisco, when a fast-moving cyclist ran the stop sign from a downhill section of [XXX] from the right. The Zoox vehicle came to a stop in the intersection to yield to the approaching cyclist. The cyclist lost control, went over the handlebar, made contact with the left rear corner of the stopped Zoox vehicle, and then fell to the ground. The Zoox vehicle remained stopped in the intersection following the impact. Police and emergency services were notified and arrived at the scene. The cyclist was transported to a hospital via ambulance. The Zoox vehicle then resumed operation. There was no damage to the vehicle.
cause not established30610-15707ZooxSource file ↗Not graded by the source2026-06NHTSAWaymoSan Francisco30270-15636Non-Motorist: Pedestrian · struck on the rear left · proceeding straight
- Crash With
- Non-Motorist: Pedestrian
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 6
- CP Pre-Crash Movement
- Other, see Narrative
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
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.
On June [XXX], 2026 at 6:01 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger of the Waymo AV on [XXX] near [XXX]. The Waymo AV was travelling westbound on [XXX]. While the Waymo AV was in motion, a passenger seated in the rear right of the Waymo AV removed their seatbelt and opened the right rear passenger side door. The Waymo AV detected the opened door and began to slow in-lane. While the Waymo AV was slowing, the passenger seated in the right rear passenger seat exited the vehicle through the open door, placed their feet on the ground, and the rear right tire of the Waymo AV made contact with the Waymo AV passenger, who fell to the ground as the Waymo AV came to a stop. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger of the Waymo AV was transported from the scene to a hospital for medical treatment with unknown injuries. A passenger in the Waymo AV was not belted at the time of the collision as they were exiting the vehicle. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-15636WaymoSource file ↗Not graded by the source2026-06NHTSAWaymoSan Francisco30270-15301Motorcycle · struck on the rear left · stopped
- Crash With
- Motorcycle
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Rear Right, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- San Francisco Police Department
- Make
- JAGUAR
- Model
- I-PACE
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.
On June [XXX], 2026 at 1:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was involved in a collision involving a motorcycle and an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane for a red light on [XXX] at the intersection with [XXX]. While the Waymo AV remained stopped, a motorcycle traveling in the second from the right lane came to a stop adjacent to an SUV that was stopped in the rightmost lane. After both vehicles briefly remained stopped, the SUV and motorcycle began to proceed forward when the SUV changed lanes into the second from the right lane, towards the motorcycle. The motorcycle maneuvered left towards the dedicated left turn lane, and the SUV continued to change lanes across the second from the right lane, towards the motorcycle into the dedicated left turn lane. While the SUV continued to change lanes, the front right of the SUV made contact with the rear of the motorcycle, and the front left of the SUV made contact with the right side of a passenger car that was stopped behind the Waymo AV. As a result of this initial contact with the SUV, the motorcycle continued forward and the front of the motorcycle then made contact with the rear right of the Waymo AV. The SUV also continued forward, and the front left of the SUV then made contact with the rear right of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage, and the motorcyclist was transported to the hospital by ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital by ambulance. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-15301WaymoSource file ↗Not graded by the source2026-06NHTSAWaymoOrlando30270-15468Van · struck on the front · stopped
- Crash With
- Van
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Crossing into Opposing Lane
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Partly Cloudy
- Investigating Agency
- Florida Highway Patrol
- Make
- JAGUAR
- Model
- I-PACE
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.
On June [XXX], 2026 at 2:54 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] and approaching a curve in the road to the left, when a van traveling westbound on [XXX] along the curve in the road crossed the double yellow and entered the Waymo AV's lane of travel. The Waymo AV braked, maneuvered to the right and slowed to a stop as the van continued forward, and the left side of the van made contact with the front left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the van was transported to the hospital by ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-15468WaymoSource file ↗Not graded by the source2026-05NHTSAWaymoSan Francisco30270-15096SUV · struck on the rear right · proceeding straight
- Crash With
- SUV
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 3
- 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
- San Francisco Police Department
- Make
- JAGUAR
- Model
- I-PACE
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.
On May [XXX], 2026 at 11:59 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] with its right turn signal activated when it began to slow to yield to a passenger car stopped facing west near the north curb of [XXX] and partially in-lane. While the Waymo AV was slowing, an SUV traveling westbound on [XXX] at a high rate of speed approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-15096WaymoSource file ↗Not graded by the source2026-05NHTSAZooxLas Vegas30610-15295Passenger Car · struck on the rear, rear right · proceeding straight
- Crash With
- Passenger Car
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear, Rear Right
- SV Precrash Speed (MPH)
- 3
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left, Front, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- ZOOX
- Model
- Zoox
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
An unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling north on [XXX], having just completed a left turn from [XXX] in Las Vegas, when it encountered debris in its path. The Zoox vehicle attempted to steer right, then executed hard braking to avoid the debris, at which point it was rear-ended by a passenger car (Vehicle 2) traveling directly behind it. Both vehicles came to a stop following the impact and were subsequently towed due to the damage sustained. Vehicle 2 suffered front-end damage and its driver-side frontal airbags deployed, while the Zoox vehicle sustained moderate damage to its rear. Law enforcement was notified of the event, but did not respond to the scene. Following the impact, Zoox staff inquired if emergency medical services should be called; the driver replied that the police had already been contacted. The driver of Vehicle 2 informed Zoox staff at the scene that they were "shaken" and "pretty bruised".
cause not established30610-15295ZooxSource file ↗Not graded by the source2026-05NHTSAWaymoTempe30270-15022Passenger Car · struck on the rear right · making right turn
- Crash With
- Passenger Car
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Partly Cloudy
- Investigating Agency
- Tempe Police Department
- Make
- JAGUAR
- Model
- I-PACE
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.
On May [XXX], 2026 at 12:43 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the rightmost lane on [XXX] with its right turn signal activated when it began to slow to turn right into a parking lot at [XXX]. As the Waymo AV initiated the right turn, a passenger car traveling eastbound in the rightmost lane on [XXX] approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the passenger car was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-15022WaymoSource file ↗Not graded by the source2026-03NHTSAZooxMiami30610-14554Heavy Truck · struck on the front left · proceeding straight
- Crash With
- Heavy Truck
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 17
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Rear Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Miami Dade Police Department
- Make
- TOYOTA
- Model
- Highlander
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
A Zoox vehicle in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching Zoox vehicle. The door struck the Zoox vehicle's right-side A-pillar, windshield, and sensor assembly. After the impact, the trailer's door rebounded and struck the operator behind it. The Zoox vehicle operator then disengaged from autonomous mode. The police and emergency personnel arrived at the scene. The operator was transported by an ambulance from the scene.
cause not established30610-14554ZooxSource file ↗Not graded by the source2026-02NHTSAZooxLas Vegas30610-14341SUV · struck on the front left · proceeding straight
- Crash With
- SUV
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 7
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- None
- Make
- ZOOX
- Model
- Zoox
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
An occupied Zoox autonomous vehicle was traveling northeast on [XXX], passing through the intersection of [XXX] in Las Vegas, with a green signal, when an SUV (Vehicle 2) violated the Zoox vehicle's right of way and abruptly entered its travel path. The Zoox vehicle braked hard and attempted to veer left, but the right front fender of the Zoox vehicle made contact with the left front fender and bumper of Vehicle 2. The driver of Vehicle 2 briefly stopped and then drove away from the scene. The Zoox vehicle was found to have sustained minor damage. At the time of the incident, the passengers did not report any injuries, and police were not notified. On March 2, 2026, the passengers notified Zoox Support that they "sustained multiple injuries and have experienced persistent and worsening pain and cognitive symptoms since the impact".
cause not established30610-14341ZooxSource file ↗Not graded by the source2026-02NHTSAWaymoScottsdale30270-13955Passenger Car · struck on the left · changing lanes
- Crash With
- Passenger Car
- SV Pre-Crash Movement
- Changing Lanes
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 56
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Highway / Freeway
- Weather
- Clear
- Investigating Agency
- Arizona Department of Public Safety
- Make
- JAGUAR
- Model
- I-PACE
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.
On February [XXX], 2026 at 7:09 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane. A passenger car traveling northbound in the second to the left lane, in front of and to the left of the Waymo AV, began to slow and change lanes to the right when a second passenger car made contact with the rear right side of the first passenger car. The second passenger car continued forward and made contact with an SUV stopped in the queue of traffic in the second from the left lane. As a result of the initial contact with the second passenger car, the first passenger car was pushed east across two lanes of travel, and entered the Waymo AV's lane of travel. The Waymo AV slowed and maneuvered to the right to avoid the oncoming passenger car and the front left side of the passenger car made contact with the left side of the Waymo AV. The Waymo AV rotated to the left and came to rest facing southwest in the second and third from the left lanes. During two subsequent maneuvers in which the Waymo AV pulled forward and to the right in an attempt to navigate off the freeway, the front left corner of the Waymo AV made contact with an "Oversized Load" sign attached to a heavy truck stopped in the second from the left lane. At the time of all impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage. The driver of the first passenger car was transported to a hospital by an ambulance with unknown injuries, and the passenger of the Waymo AV alleged minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13955WaymoSource file ↗Not graded by the source2026-01NHTSAZooxSan 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 ↗Not graded by the source2026-01NHTSAWaymoTempe30270-13817Passenger Car · struck on the left · stopped
- Crash With
- Passenger Car
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Tempe Police Department
- Make
- JAGUAR
- Model
- I-PACE
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.
On January [XXX], 2026 at 3:53 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west in the rightmost lane of [XXX] in a queue of traffic for a red light at the intersection with [XXX]. A passenger car, traveling eastbound in the leftmost westbound travel lane at a high rate of speed, entered the intersection against a red light, and made contact with the front left of a second passenger car traveling northbound on [XXX] through a green light. As a result of this contact, the airbags in both passenger cars deployed. The initial eastbound passenger car continued to exit the intersection after contact, proceeded towards the rightmost westbound lane on [XXX], and the front left of the passenger car made contact with the left side of the stationary Waymo AV, resulting in airbag deployment in the Waymo AV. After making contact with the Waymo AV, the passenger car continued eastbound and the left side of the passenger car then made contact with an additional Waymo AV (VIN [XXX]) that was stopped behind the initial Waymo AV in traffic. At the time of the impact, both Waymo AVs' Level 4 ADS were engaged in autonomous mode. The two passenger cars and the initial Waymo AV (VIN [XXX]) sustained damage. An occupant of the northbound passenger car was transported from the scene for medical treatment with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13817WaymoSource file ↗