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
2,759 records match
351 death reports1987–20265 registriesClear
Narrow it down
What happened
Country
Year
Property damage only2025-12NHTSAWaymoSan Francisco30270-13331SUV · struck on the rear right · stopped
- Crash With
- SUV
- 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
- Proceeding Straight
- CP Contact Area
- Front Right
- 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 December [XXX], 2025 at 12:21 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] when it slowed to a stop for a flashing red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling in the same lane approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13331WaymoSource file ↗Property damage only2025-12NHTSAWaymoSan Francisco30270-13541Pickup Truck · struck on the front · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- 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
- Rain
- 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 December [XXX], 2025 at 6:35 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southbound in the second from the right lane on [XXX] with its left turn signal activated when it initiated a lane change to the leftmost lane. As the Waymo AV crossed the dashed white lane line, the Waymo AV slowed to a stop, partially in the leftmost lane and partially in the second from the right lane, to yield to a passenger car stopped in a queue of traffic in front of the Waymo AV. A pickup truck that was initially stopped in the leftmost lane facing south on [XXX] behind and to the left of the Waymo AV proceeded forward and the front right side of the pickup truck made contact with the front left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-13541WaymoSource file ↗Property damage only2025-12NHTSAWaymoLos Angeles30270-13549SUV · struck on the rear right · stopped
- Crash With
- SUV
- 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
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 December [XXX], 2025 at 5:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northeastbound on [XXX] in the designated left turn lane with its left turn signal activated when it began to slow to a stop for a yellow light at the intersection with [XXX]. As the traffic light turned red the Waymo AV remained stopped. An SUV traveling northeastbound on [XXX] approached the Waymo AV from behind and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13549WaymoSource file ↗Property damage only2025-12NHTSAWaymoPhoenix30270-13307Pickup Truck · struck on the front · 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
- Front
- SV Precrash Speed (MPH)
- 9
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 December [XXX], 2025 at 7:38 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] along the south curb in the rightmost lane with its right turn signal activated in preparation for a right turn at the intersection with [XXX]. At the same time, a pickup truck was centered in the rightmost lane of eastbound [XXX] and stopped at the intersection with [XXX] on a green light to yield to stopped traffic across the intersection. As the Waymo AV approached the intersection to make the right turn close to the curb, the pickup truck activated its right turn signal while initiating a right turn onto [XXX], and crossed in front of the Waymo AV. The front right side of the pickup truck then 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. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13307WaymoSource file ↗Property damage only2025-12NHTSAWaymoVenice30270-13328SUV · struck on the rear · making right turn
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 7
- CP Pre-Crash Movement
- Passing
- 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 December [XXX], 2025 at 11:31 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Venice, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southeastbound on [XXX] with its right turn signal activated and initiated a right turn onto [XXX]. While the Waymo AV was turning, an SUV traveling southeastbound on [XXX] proceeded to pass the Waymo AV on 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. The Waymo AV sustained damage. 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-13328WaymoSource file ↗Property damage only2025-12NHTSAAvrideDallas31101-13624Heavy Truck · struck on the front left · changing lanes
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Changing Lanes
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 7
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 December [XXX], 2025 at 11:11 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in the left lane on [XXX] engaged in autonomous mode when it began to change lanes to the right lane. A heavy truck traveling southbound in the right lane on [XXX] proceeded straight as the AVRIDE AV attempted to change lanes, and the front right side of the AVRIDE made contact with the rear left side of the heavy truck. The collision resulted in damage to the AVRIDE AV. No damage was reported to the dairy truck. No injuries were reported.
cause not established31101-13624AvrideSource file ↗Property damage only2025-12NHTSAWaymoSanta Monica30270-13402Passenger 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
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 December [XXX], 2025 at 9:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it slowed to a stop for a red light at the intersection with [XXX]. A passenger car traveling in the same lane approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-13402WaymoSource file ↗Property damage only2025-12NHTSAWaymoSan Francisco30270-13324Heavy Truck · struck on the left · stopped
- Crash With
- Heavy Truck
- 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
- Passing
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 December [XXX], 2025 at 12:15 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was stopped in the right lane of westbound [XXX] just before the intersection with [XXX] due to a queue of stopped traffic. A heavy truck traveling westbound in the left lane on [XXX] then passed the Waymo AV on the left, and the right rear side of the heavy truck made contact with the left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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-13324WaymoSource file ↗Minor injury2025-12NHTSAWaymoLos Angeles30270-13388Passenger Car · struck on the front · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- 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
- 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 December [XXX], 2025 at 10:50 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northeastbound on a narrowed portion of [XXX] with vehicles parked on both sides when it maneuvered to the right and came to a stop to yield to a passenger car traveling southwestbound on [XXX]. The passenger car continued to approach the Waymo AV and the front left side of the passenger car made contact with the front left side of the stationary 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 alleged minor 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-13388WaymoSource file ↗Property damage only2025-12NHTSAAvrideAustin31101-13619SUV · struck on the rear left
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Other, see Narrative
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 12
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 December [XXX], 2025 at 7:35 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the middle lane on [XXX] engaged in autonomous mode. [XXX] is a three-lane street. The AVRIDE AV approached a school bus located in the right lane that was stopping with its stop sign signals displayed. The AVRIDE AV and a passenger car in the right lane next to the AVRIDE AV began to slow in order to stop in compliance with applicable traffic rules. As the AVRIDE AV was in the process of slowing to a stop, an SUV traveling in the right lane directly behind the AVRIDE AV and passenger car attempted to pass the passenger car on the left side and AVRIDE AV on the right side in one maneuver. This caused the left front side of the SUV to make contact with the rear right side of the AVRIDE AV. Both vehicles stopped and pulled over after the incident. Both vehicles sustained damage. No injuries were reported.
cause not established31101-13619AvrideSource file ↗Property damage only2025-12NHTSAWaymoPhoenix30270-13542Heavy Truck · struck on the right · stopped
- Crash With
- Heavy Truck
- 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
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- 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 December [XXX], 2025 at 3:45 AM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling southbound in a parking lot at [XXX] when it slowed to a stop with its hazard lights activated to yield to a heavy truck that was facing south and executing a reversing turn into a loading dock parking stall at the east side of the parking lot. The heavy truck continued to reverse, and the rear left side of the heavy truck trailer made contact with the right side of the stationary Waymo AV. At the time of the impact, the Waymo AV' Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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-13542WaymoSource file ↗Property damage only2025-12NHTSAWaymoBrisbane30270-13447struck on the bottom · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Bottom
- SV Precrash Speed (MPH)
- 7
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Brisbane 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 December [XXX], 2025 at 5:08 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Brisbane, California was in a collision involving a hand truck dolly on [XXX] near [XXX]. The Waymo AV was traveling northeastbound on [XXX] in the right lane behind a heavy truck with its trailer door open. While the Waymo AV and the heavy truck were continuing northeastbound, a hand truck dolly fell from the back of the heavy truck trailer onto the roadway in the Waymo AV's lane of travel, and the undercarriage of the Waymo AV made contact with the hand truck dolly. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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-13447WaymoSource file ↗Property damage only2025-12NHTSAWaymoLos Angeles30270-13444Passenger 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
- Proceeding Straight
- CP Contact Area
- 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 December [XXX], 2025 at 3:41 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound on a narrow portion of [XXX] when it maneuvered to the right towards the curb and slowed to a stop to yield to a passenger car traveling northbound on [XXX]. While the Waymo AV was stopped, the passenger car proceeded to pass to the left of the Waymo AV and the left side of the passenger car made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-13444WaymoSource file ↗Property damage only2025-12NHTSAWaymoTempe30270-13408Passenger 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
- Right
- 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 December [XXX], 2025 at 3:09 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 stopped facing west in the right lane on [XXX] in a queue of traffic for an SUV that was stopped facing north in the intersection with [XXX]. While the Waymo AV was stopped, a passenger car that was initially stopped directly behind the Waymo AV proceeded to change lanes into the designated left turn lane. As the passenger car passed the Waymo AV to the left, the right side of the passenger car made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13408WaymoSource file ↗Minor injury2025-12NHTSAWaymoAtlanta30270-13488Passenger Car · struck on the right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 22
- 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
- Atlanta 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 December [XXX], 2025 at 10:24 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the right lane on [XXX] when a passenger car that was initially stopped facing north on [XXX], to the right and in front of the Waymo AV, proceeded forward into the intersection at [XXX]. As the passenger car entered the intersection the front of the passenger car made contact with the right 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 passengers of the Waymo AV were 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 and 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-13488WaymoSource file ↗Property damage only2025-12NHTSAWaymoAtlanta30270-13506struck on the front · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 25
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Atlanta 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 December [XXX], 2025 at 4:09 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving debris on [XXX] at [XXX]. The Waymo AV was traveling northwestbound on [XXX] in the the left lane proceeding through the intersection with [XXX] when the front left side tire of the Waymo AV made contact with a piece of debris in the roadway. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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-13506WaymoSource file ↗Property damage only2025-12NHTSAWaymoLos Angeles30270-13540Pickup Truck · struck on the rear left · stopped
- Crash With
- Pickup Truck
- 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
- Passing
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- Weather
- Rain
- 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 December [XXX], 2025 at 1:23 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pick-up truck in a parking lot at [XXX]. The Waymo AV came to a stop facing northwestbound after completing a multipoint turn in a parking lot at [XXX]. A pickup truck traveling southeastbound in the parking lot approached the Waymo AV and came to a stop to the right of the Waymo AV. The pickup truck then proceeded forward to pass the Waymo AV and the rear right side of the pickup truck made contact with the rear right side of the stationary Waymo AV. At the time of the impact, the Waymo AV' Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13540WaymoSource file ↗Property damage only2025-12NHTSAWaymoPalo Alto30270-13420SUV · struck on the rear 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 Right
- 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
- 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 December [XXX], 2025 at 11:40 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Palo Alto, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwestbound on [XXX] when it slowed to a stop for a stop sign at the intersection with [XXX]. As the Waymo AV began to proceed forward, an SUV that was traveling southwestbound on [XXX] approached the Waymo AV from behind and the front of the SUV made contact with the rear of the stationary 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 Waymo AV was not belted at the time of the collision. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13420WaymoSource file ↗Minor injury2025-12NHTSAWaymoLos Angeles30270-13490SUV · struck on the rear right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 9
- 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
- Los Angeles 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 December [XXX], 2025 at 10:17 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southwestbound in the right lane on [XXX] when it began to slow for a flashing red light at the intersection with [XXX]. While the Waymo AV was slowing, an SUV traveling southwestbound in the right lane on [XXX] began accelerating as it 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 passengers in the Waymo AV were not belted at the time of the collisions. The passengers in the Waymo AV alleged minor 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-13490WaymoSource file ↗Property damage only2025-12NHTSAWaymoAustin30270-13267struck on the right · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 6
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- Weather
- Cloudy
- 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 December [XXX], 2025 at 7:58 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a golf cart in a parking lot at [XXX]. The Waymo AV was traveling eastbound in a parking lot at [XXX] while a golf cart that was traveling eastbound in the parking lot turned right and stopped in a parking stall in front of and to the right of the Waymo AV. As the Waymo AV continued eastbound and passed behind the golf cart, the golf cart then reversed and the rear of the golf cart made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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-13267WaymoSource file ↗Property damage only2025-12NHTSAWaymoPhoenix30270-13278Heavy Truck · struck on the front · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- 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
- Partly Cloudy
- 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 December [XXX], 2025 at 9:59 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] when a heavy truck traveling westbound and exiting a truck parking bay behind [XXX] turned right onto [XXX] in front of the Waymo AV. As the heavy truck was completing its right turn, the heavy truck came to a stop in the Waymo AV's lane of travel and the Waymo AV stopped to yield to the heavy truck. The heavy truck then reversed, and the rear right side of the heavy truck trailer 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. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13278WaymoSource file ↗Property damage only2025-12NHTSAZooxSan 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 ↗Minor injury2025-12NHTSAWaymoPhoenix30270-13372Passenger Car · struck on the rear right · changing lanes
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Changing Lanes
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 9
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- 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 December [XXX], 2025 at 1:01 PM MT a Waymo Autonomous Vehicle (Waymo AVâ) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the second from the right lane on [XXX] when a dog entered the roadway from the south curb. The Waymo AV began slowing and maneuvering into the rightmost lane to yield to the dog. While the Waymo was slowing, a passenger car that was traveling behind the Waymo AV approached the Waymo AV 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. The passenger of the Waymo AV was transported from the scene to a hospital for medical treatment with 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-13372WaymoSource file ↗Property damage only2025-12NHTSAWaymoSan Francisco30270-13416Passenger 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
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Partly Cloudy
- 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 December [XXX], 2025 at 9:43 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] with its right turn signal activated when it slowed to a stop for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car traveling westbound on [XXX] approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13416WaymoSource file ↗Property damage only2025-12NHTSAWaymoAtlanta30270-13410Pickup Truck · struck on the front right · stopped
- Crash With
- Pickup Truck
- 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
- Parking Maneuver
- CP Contact Area
- Rear
- 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 December [XXX], 2025 at 2:04 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX], with vehicles parked at the curb on the right side when it slowed to a stop to yield to a pickup truck that was stopped facing south on[XXX]. The pickup truck began to reverse, maneuvering to parallel park at the curb on the right side of the roadway. As the pickup truck continued to reverse, the rear left side of the pickup truck made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13410WaymoSource file ↗No injury reported2025-12NHTSAMay MobilityAtlanta30413-13470SUV · struck on the right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Investigating Agency
- Atlanta Police Department
- Make
- TOYOTA
- Model
- Sienna
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.
The May Mobility vehicle (Ego) was operating in autonomy while waiting in slow traffic in the leftmost of two parallel lanes. Ahead, both lanes were obstructed by stopped vehicles, prompting traffic to move to the center turn lane to proceed. The Autonomous Vehicle Operator (AVO) intervened to move closer to the lead vehicle as another vehicle in the right lane attempted to merge left, preventing it. After the merging car stopped, the AVO pulled closer to the lead vehicle, removing any space to merge. As the lead vehicle began to move, both the AVO and the vehicle to the right immediately accelerated, while the merging vehicle moved left into the side of the May AV. Had the Ego remained in Autonomous mode, it would have maintained a safe distance allowing the merging vehicle to proceed safely. No software defects led to this event. This behavior goes against the training of May AVOs. Upon review of this AVOâs actions it was decided to remove this person from their role as an AVO.
cause not established30413-13470May MobilitySource file ↗Property damage only2025-12NHTSAWaymoSan Francisco30270-13514struck on the front right · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 25
- 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 December [XXX], 2025 at 8:20 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on [XXX] when the front of the Waymo AV made contact with a fallen utility line hanging in the travel lane. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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-13514WaymoSource file ↗Property damage only2025-12NHTSAWaymoScottsdale30270-13489Heavy Truck · struck on the front right · backing
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Backing
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- Weather
- Partly Cloudy
- 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 December [XXX], 2025 at 1:54 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling southbound on a driveway at a parking lot at [XXX] and a heavy truck was traveling southbound on the driveway ahead of the Waymo AV. The heavy truck came to a stop and the Waymo AV slowed to a stop to yield to the stopped heavy truck. The heavy truck reversed and the Waymo AV reversed momentarily before coming to a stop. The heavy truck continued to reverse, and the Waymo AV began to reverse again, and the rear of the heavy truck made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV' Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. 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-13489WaymoSource file ↗Property damage only2025-12NHTSAWaymoAustin30270-13515Passenger 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 Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Austin 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 December [XXX], 2025 at 12:04 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the leftmost lane when it slowed to a stop in a queue of traffic for a red light at the intersection with [XXX]. A passenger car that was initially stopped directly in front of the Waymo AV began to reverse and the Waymo AV activated its horn and hazard lights. The passenger car continued to reverse and the rear of the passenger car made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13515WaymoSource file ↗Property damage only2025-12NHTSAWaymoLos Angeles30270-13369Passenger Car · struck on the rear 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
- Rear Left
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- West Hollywood Sheriff 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 December [XXX], 2025 at 9:36 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling westbound in the left lane on [XXX] in stop-and-go traffic when a passenger car that was traveling westbound on F[XXX] directly behind the Waymo AV began merging into the right lane. As the passenger car was changing lanes, the front right side of the passenger car made contact with the left side of an SUV that was traveling westbound in the right lane on [XXX] and the left side of the passenger car made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage. The passenger in the Waymo AV was not belted at the time of the collision. 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-13369WaymoSource file ↗Minor injury2025-12NHTSAWaymoLos Angeles30270-13491Van · struck on the rear right · parked
- Crash With
- Van
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Parked
- 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
- Los Angeles 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 December [XXX], 2025 at 9:48 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was stopped at the curb facing southeast on [XXX] with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, a van traveling southeastbound on [XXX] maneuvered to the right and approached the Waymo AV from behind, and the front of the van made contact with the rear of the stationary 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 of the Waymo AV was transported to a hospital by an ambulance with 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 and 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-13491WaymoSource file ↗Property damage only2025-12NHTSAAvrideAustin31101-13615Passenger Car · struck on the front left · 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 Left
- SV Precrash Speed (MPH)
- 16
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Left, Rear
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 December [XXX], 2025 at 7:23 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas. The AVRIDE AV was traveling eastbound on [XXX] in autonomous mode engaged, preparing to turn left onto [XXX]. As the AVRIDE AV began to enter the turn lane on [XXX], a passenger car traveling in front of the AVRIDE AV moved into the AVRIDE AV¢ÂÂs lane of travel and the rear left side of the passenger car made contact with the front right fender of the AVRIDE AV. Both vehicles sustained damage. There were no reported injuries.
cause not established31101-13615AvrideSource file ↗No injury reported2025-12NHTSAAvrideDallas31101-13626Passenger Car · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Unknown
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 December [XXX], 2025 at 10:05 AM, an AVRIDE AV autonomous vehicle (the AVRIDE AVâ) was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling forward at a low speed on [XXX] in autonomous mode when the passenger car ahead of it began to reverse. The AVRIDE AV came to a stop, and the safety driver sounded the horn. The passenger car in front of the AVRIDE AV continued to reverse and the rear of the passenger car made contact with the front of the AVRIDE AV. The vehicles barely made contact. No damage to either vehicle and no injuries were reported.
cause not established31101-13626AvrideSource file ↗Property damage only2025-12NHTSAWaymoSan Francisco30270-13401Passenger 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 Right
- 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 December [XXX], 2025 at 3:58 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northwestbound in the leftmost lane on [XXX] when it began to slow for a queue of traffic for a red light at the intersection with [XXX]. The Waymo AV slowed to a stop behind a stopped passenger car and the passenger car then reversed and the rear of the passenger car made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13401WaymoSource file ↗Property damage only2025-12NHTSAAvrideAustin31101-13625Heavy Truck · struck on the front left · 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 Left
- SV Precrash Speed (MPH)
- 4
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 December [XXX], 2025 at 7:54 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southeastbound in autonomous mode in the center lane on [XXX] when it came to a stop at a red light at the intersection with [XXX]. While the AVRIDE AV was stopped, a tow truck traveling in the right lane began to enter the AVRIDE AVs lane of travel. There was sufficient space for the tow truck to move into the lane while the AVRIDE AV remained stopped. When the traffic signal turned green, both vehicles began to proceed slowly into the intersection. The tow truck then came to an abrupt stop while the light remained green. The safety driver of the AVRIDE AV applied the brakes, but due to the sudden stop by the tow truck, the front of the AVRIDE AV made contact with the rear of the tow truck. Both vehicles sustained damage. No injuries were reported.
cause not established31101-13625AvrideSource file ↗Property damage only2025-12NHTSAWaymoBeverly Hills30270-13395Passenger 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
- Proceeding Straight
- CP Contact Area
- Front Right
- 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 December [XXX], 2025 at 8:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Beverly Hills, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northeastbound on [XXX] in the second to the right lane when it slowed to a stop for a red light at the intersection with [XXX]. A passenger car traveling northeastbound on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13395WaymoSource file ↗Property damage only2025-12NHTSAWaymoLos Angeles30270-13443struck on the bottom · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Bottom
- SV Precrash Speed (MPH)
- 10
- 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 December [XXX], 2025 at 8:39 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision with the pavement on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] when the Waymo AV's undercarriage made contact with the pavement. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV was not belted at the time of the collision. 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-13443WaymoSource file ↗Property damage only2025-12NHTSAWaymoAustin30270-13399Passenger 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
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Austin 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 December [XXX], 2025 at 12:56 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing northwest in the leftmost lane on [XXX] for a red light at the intersection with [XXX], when a passenger car began to slow as it approached the stopped Waymo AV from behind. As the passenger car was slowing, a pickup truck traveling behind the passenger car made contact with the rear of the passenger car, and as a result of this contact, the front of the passenger car then made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage. 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-13399WaymoSource file ↗Minor injury2025-12NHTSAWaymoPalo Alto30270-13378Non-Motorist: Cyclist · struck on the right · stopped
- Crash With
- Non-Motorist: Cyclist
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- NM Crossing Roadway
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Palo Alto 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 December [XXX], 2025 at 8:26 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Palo Alto, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling northwestbound in the rightmost lane on [XXX] with its right turn signal activated and preparing to make a right turn at a green light onto [XXX]. As the Waymo AV began initiating the right turn, the Waymo AV came to a stop within the crosswalk to yield to a cyclist. The cyclist was traveling southbound on the east sidewalk of [XXX] and entered the crosswalk across [XXX] against a red pedestrian crosswalk light. As the cyclist entered the crosswalk, the front tire of the bicycle made contact with the right side of the stationary Waymo AV and the cyclist fell to the ground. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The cyclist was transported to a hospital in an ambulance. 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-13378WaymoSource file ↗Property damage only2025-12NHTSAWaymoLos Angeles30270-13322Motorcycle · struck on the left · stopped
- Crash With
- Motorcycle
- 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
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 December [XXX], 2025 at 4:30 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling southeastbound on [XXX] when it came to a stop for a stop sign at the intersection with [XXX]. The Waymo AV proceeded forward momentarily and then came to another stop to yield to a cyclist on an electric bicycle that was traveling southwestbound on [XXX] and entering the intersection at [XXX] without stopping at the stop sign. While the Waymo AV was stopped, the cyclist continued to proceed forward and the electric bicycle made contact with the left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13322WaymoSource file ↗Property damage only2025-12NHTSAAvrideAustin31101-13627SUV · struck on the rear right · merging
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Merging
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Merging
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Highway / Freeway
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 December [XXX], 2025 at 6:41 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX]. The AVRIDE AV was traveling eastbound in autonomous mode in the right lane on [XXX] East. The AVRIDE AV was stopped at a yield sign, attempting to merge into traffic onto [XXX] East, when an SUV approached from the AVRIDE AV from behind and the front of the SUV made contact with the rear of the AVRIDE AV. Following the collision, both vehicles came to a safe stop, and the drivers exchanged information. Both vehicles sustained minor damage. No injuries were reported.
cause not established31101-13627AvrideSource file ↗Property damage only2025-12NHTSAWaymoPalo Alto30270-13453Bus · struck on the front right · stopped
- Crash With
- Bus
- 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 Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Investigating Agency
- Stanford 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 December [XXX], 2025 at 3:45 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Palo Alto, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was stopped facing southwest in the designated left turn lane on [XXX] in a queue of traffic for the intersection with [XXX]. While the Waymo AV was stopped, a bus that was initially stopped directly in front of the Waymo AV reversed and the rear of the bus made contact with the front 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. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13453WaymoSource file ↗Not graded by the source2025-11-21FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00295ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM, T10-L2 OPEN FUSION INSTRAOP MERGE WITH E3D, T10/T11/T12 WERE ALL MEDIAL/LATERAL MISSED SCREWS, T12 RIGHT AND LUMBAR SCREWS WERE PERFECT. T10 BILATERAL AND T11 RIGHT WERE REMOVED AND REPLACED AFTER THE SECOND E3D SPIN.
cause not established3004142400-2025-00295Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-11-18FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00293ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM, THERE WAS AN ISSUE WITH THE END EFFECTOR AND ACCURACY, AND THERE WAS ALSO AN ISSUE WITH REHOMING AFTER INITIAL ACCURACY CONCERNS. WE PLANNED LEVELS L4, L5, AND S1 BUT ONLY COMPLETED THE LEVELS L4, L5 DURING THE PROCEDURE. ALL 4 SCREWS WERE NOT PLACED AS PLANNED; THEY WERE ALL CONSIDERED LOWER THAN THE INITIAL PLAN THE SURGEON CREATED. THEN WE DID X-RAYS AND CONFIRMED THE SCREWS WERE OUT OF PLACEMENT. ROBOT WAS REMOVED FROM THE PROCEDURE ARE BUT STILL IN THE OR UNTIL THE CASE WAS COMPLETED.
cause not established3004142400-2025-00293Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-11-17FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00289ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THERE WAS A RADIAL ERROR OF GREATER THAN 1.5MM AT MULTIPLE TRAJECTORIES. THE RIGHT OF ELECTRODE WAS REMOVED AND NO OTHER ELECTRODE WAS PLACED ALONG THIS PLANNED TRAJECTORY. NO FURTHER REVISION IS NEEDED.
cause not established3004142400-2025-00289Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-11-06FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00294ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE PLACING CRANIAL LEADS WITH THE EXCELSIUS GPS THE LEFT SIDE LEAD SHIFTED SUPERIOR AT THE VENTRICLE. THE SURGEON STATED THAT THE LEAD RAN ALONG THE SUPERIOR EDGE OF THE HIPPOCAMPUS BUT DECIDED TO PLACE THE LEAD AGAIN. THE EGPS WAS PUSHED BACK IN AFTER LMCS VERIFIED CONTINUED ACCURACY. THE EGPS ARM WAS ALIGNED TO THE LEFT TRAJECTORY AND THE PROCESS REPEATED. THE O-ARM WAS BROUGHT BACK IN AND THE SPIN WAS PERFORMED AND TRANSFERRED. THE LEAD WAS FOUND TO HAVE HIT THE VENTRICLE AND SHIFTED SUPERIOR AGAIN BUT WAS INFERIOR TO THE PREVIOUS LEAD PLACEMENT AND WAS THUS MORE ON TRAJECTORY. THE SURGEON WAS SATISFIED WITH THE PLACEMENT AND CLOSING BEGAN.
cause not established3004142400-2025-00294Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-11-05FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00009ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN EXCELSIUSGPS SURGERY THE FIRST SCREW LOOKED TO PLAN. THE SECOND SCREW, L4R, LOOKED LIKE IT WAS TO PLAN, BUT THE OFFSET WAS RED, AND DOC WAS WORRIED. THERE WERE NO NAV SHIFTS AFTER LANDMARK CHECK. HE DIDN'T LIKE, CAME BACK IN WITH DURA PRO, PUT IN SCREW AGAIN, BUT THIS TIME WAS LATERAL. HE DID A LANDMARK CHECK, EVERYTHING ACCURATE. HE DID THE SCREW FREEHAND NAV, WHICH WAS TO PLAN. THE L4L SCREW OFFSET WAS RED, AND SCREW LOOKED LATERAL, BUT DOC SAID THAT IT FELT GOOD TO HIM AND DURA PRO WAS GREEN AND RIGHT ON TRAJECTORY. THE SCREW WAS LATERAL. IT WAS POSSIBLY LATERAL DUE TO RETRACTOR, OR PATIENT MOVEMENT. THE DR. TOOK OUT SCREW, AND REPLACED SCREW FREEHAND WITHOUT NAVIGATION USING FLOUROSCOPY. ALL SCREWS TO PLAN AT END.
cause not established3004142400-2026-00009Globus MedicalExcelsiusGPSRead the record ↗Death reported2025-11-03FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00031Monarch Platform
Monarch Platform — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A ROBOTICALLY ASSISTED BRONCHOSCOPY PROCEDURE, AS THE PHYSICIAN WAS TAKING ANTERIOR/POSTERIOR SCOUT SHOTS USING A 3D C-ARM, THE PATIENT BEGAN TO EXHIBIT IRREGULAR HEART RHYTHMS. THE PHYSICIAN DECIDED TO ABORT THE PROCEDURE. THE PATIENT WENT INTO ATRIAL FIBRILLATION AND CODED. CHEST COMPRESSIONS WERE STARTED IMMEDIATELY. THE CODE CONTINUED FOR 30 - 35 MINUTES, AND THE PATIENT PASSED AWAY. NO BIOPSIES OR NEEDLE ASPIRATIONS WERE PERFORMED DURING THE PROCEDURE. NO ISSUES WERE REPORTED INVOLVING THE DEVICES USED DURING THE PROCEDURE.
cause not established3014447948-2025-00031Auris HealthMonarch PlatformRead the record ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-13251Passenger Car · struck on the 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 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
- Cloudy
- 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 November [XXX], 2025 at 10:17 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northwestbound in the leftmost lane on [XXX] and proceeding through the intersection at [XXX] to continue westbound on [XXX]. As the Waymo AV was entering [XXX], the Waymo AV began to yield for two pedestrians at the southwest curb. While the Waymo AV was slowing, a passenger car that was traveling northwestbound in the leftmost 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. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13251WaymoSource file ↗Property damage only2025-11NHTSAWaymoPhoenix30270-13092Passenger 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
- Stopped
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Phoenix 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 November [XXX], 2025 at 9:20 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car at [XXX], Terminal [XXX] at the [XXX]. The Waymo AV was traveling westbound in the right lane on [XXX], Terminal [XXX] when it slowed to a stop in a queue of traffic. A passenger car that was traveling westbound in the right lane of [XXX] slowed to a near stop directly behind the Waymo AV. While the Waymo AV was stopped and the passenger car slowly proceeded a second passenger car approached the first passenger car from behind, and the front of the second passenger car made contact with the rear of the first passenger car, and the front of the first passenger car then made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage. 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-13092WaymoSource file ↗