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
639 records match
10 death reports20254 registriesClear
Narrow it down
What happened
Country
Year
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 ↗Property damage only2025-11NHTSAWaymoAtlanta30270-13275Passenger 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
- 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 November [XXX], 2025 at 11:46 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped at the curb facing west on [XXX] for a passenger pick-up when a passenger car traveling westbound in the right lane on [XXX] approached the Waymo AV from behind, and the front 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-13275WaymoSource file ↗No injury reported2025-11NHTSAAvrideAustin31101-13441Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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.
Avride car was rear-ended at the intersection.
cause not established31101-13441AvrideSource file ↗Property damage only2025-11NHTSAWaymoPhoenix30270-13084SUV · struck on the front · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- 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 11:20 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was parked at the curb facing east on [XXX] for a passenger drop-off with hazard lights activated and an SUV was traveling eastbound on [XXX]. As the SUV approached the stationary Waymo AV, the Waymo AV activated its left turn signal and the SUV proceeded to pass the Waymo AV on the left. As the SUV was passing the Waymo AV, the Waymo AV proceeded forward at the curb while the SUV maneuvered right to approach the curb, entering the Waymo AV's lane of travel, and the right side of the SUV 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. 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-13084WaymoSource file ↗Property damage only2025-11NHTSAWaymoAtlanta30270-13148Passenger 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 November [XXX], 2025 at 3:15 AM 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 came to a stop in the left lane facing south on [XXX] at a red light. Two pedestrians approached the Waymo AV and tried unsuccessfully to board the Waymo AV while it was stopped. While the Waymo AV remained stopped, the traffic light turned green and a passenger car traveling southbound on [XXX] in the left lane 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. 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-13148WaymoSource file ↗Property damage only2025-11NHTSAWaymoScottsdale30270-13194Passenger Car · struck on the left · parked
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- 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 November [XXX], 2025 at 1:26 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 parked facing east at the south curb on [XXX]. While the Waymo AV was parked, a passenger car traveling eastbound on [XXX] proceeded past the left of the Waymo AV and the right side of the passenger car made contact with the 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-13194WaymoSource file ↗No injury reported2025-11NHTSAAvrideAustin31101-13438Passenger Car · struck on the rear right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 15
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front 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.
Rear end collision, another vehicle hit Avride car from behind when traffic light became to be yellow.
cause not established31101-13438AvrideSource file ↗Property damage only2025-11NHTSAWaymoLos Angeles30270-13099Passenger 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
- Changing Lanes
- 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 November [XXX], 2025 at 3:15 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west in the second from right lane on [XXX] for a red light at the intersection at [XXX]. While the Waymo AV was stopped, a passenger car traveling westbound in the rightmost lane on [XXX] approached a van that was traveling directly in front of the passenger car and began to maneuver left into the second from right lane. The van was coming to a stop for a red light as the passenger car approached. As the passenger car crossed the dashed white lane line, the front right side of the passenger car made contact with the rear left side of the van, and 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. The Waymo AV, the passenger car, and the van 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-13099WaymoSource file ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-12061SUV · 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 November [XXX], 2025 at 10:26 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 northbound in the second from the right lane on [XXX] and proceeding straight through a green light at the intersection with [XXX]. As the Waymo AV was about to exit the intersection, it began to slow, yielding to a flock of birds flying low across [XXX]. While the Waymo AV was slowing, an SUV traveling northbound on [XXX] directly behind the Waymo AV 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. 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-12061WaymoSource file ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-13062Passenger 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 November [XXX], 2025 at 2:22 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 eastbound on [XXX] with its right turn signal activated when it slowed to a stop in-lane, to yielding to a passenger car that was reversing at the curb where the AV intended to pull over for a passenger pick up. While the Waymo AV was stopped, a passenger car that was traveling eastbound 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. 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-13062WaymoSource file ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-13155Bus · struck on the rear · parked
- Crash With
- Bus
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Right
- 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 November [XXX], 2025 at 9:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was parked in-lane facing southwest in the right lane on [XXX] with hazard lights activated for a passenger drop-off. While the Waymo AV was parked, a bus traveling southeastbound on [XXX] made a right turn into the left lane on southwestbound [XXX]. While the bus was completing the right turn and passing the Waymo AV on the left, the right side of the bus 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. 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-13155WaymoSource file ↗Property damage only2025-11NHTSAWaymoPhoenix30270-13135Heavy Truck · struck on the rear left · stopped
- Crash With
- Heavy 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
- Backing
- CP Contact Area
- Right
- 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 November [XXX], 2025 at 7:36 PM 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 eastbound in the parking lot at [XXX] with its right turn signal activated when it slowed to a stop to yield to a heavy truck that was facing south and reversing to turn into a loading dock parking stall at the east side of the parking lot. As the heavy truck was reversing, the Waymo AV momentarily proceeded forward and to the left before coming to a stop. While the Waymo AV was stopped, the heavy truck continued to reverse and the right side of the heavy truck trailer 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-13135WaymoSource file ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-13066Bus · struck on the rear · stopped
- Crash With
- Bus
- 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
- 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 November [XXX], 2025 at 4:40 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was stopped facing south in the designated right turn lane on [XXX] in a queue of traffic waiting to turn right at the intersection with [XXX]. As traffic ahead advanced, the Waymo remained stopped to yield to a bus traveling southbound in the adjacent bus lane in close proximity to the Waymo AV. While the Waymo AV was stopped, the bus passed the Waymo AV and the right side of the bus 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. 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-13066WaymoSource file ↗Minor injury2025-11NHTSAWaymoLos Angeles30270-13063SUV · struck on the front right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- 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
- Intersection
- Weather
- Cloudy
- 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 November[XXX], 2025 at 6:22 AM 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 eastbound in the second from the right lane on [XXX] when an SUV passed the Waymo AV on the left, changed lanes in front of the Waymo AV into the Waymo AV's lane of travel, and came to a stop directly in front of the Waymo AV at the intersection with [XXX] at a green light. The Waymo AV came to a stop to yield to the stopped SUV, and the SUV then reversed and the rear of the SUV made contact with the front of the stationary Waymo AV. The SUV then proceeded forward momentarily, came to a stop, and reversed again into 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-13063WaymoSource file ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-13189SUV · 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 November [XXX], 2025 at 11:37 PM 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 southbound on [XXX] when it slowed to a stop for a stop sign at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling southbound 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. 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-13189WaymoSource file ↗Minor injury2025-11NHTSAWaymoAustin30270-13060Passenger Car · struck on the front · parked
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Traveling Wrong Way
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 November [XXX], 2025 at 12:37 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 southwest in the designated left turn lane on [XXX] at the intersection with [XXX] with hazard lights activated. A passenger car traveling northeastbound on [XXX], in the Waymo AV's lane of travel and against the proper direction of traffic, approached the front of 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 and 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-13060WaymoSource file ↗Property damage only2025-11NHTSAWaymoAtlanta30270-13090struck on the front 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
- Front Right
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- 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 November [XXX], 2025 at 4:14 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a gate on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it approached a gated entrance separating [XXX] from [XXX]. The Waymo AV slowed to a stop to yield to the closed gate, and began proceeding slowly forward again. As it did so, the gate began swinging open into the roadway towards the Waymo AV and 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. 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-13090WaymoSource file ↗Property damage only2025-11NHTSAWaymoLos Angeles30270-13254Bus · 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
- 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 November [XXX], 2025 at 11:31 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was traveling southeastbound in the left lane on [XXX] when it began slowing for a bus that had come to a stop facing southeast in the left lane on [XXX] and began reversing. While the Waymo AV was stopped, the bus continued to reverse and the rear of the bus 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-13254WaymoSource file ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-13235Van · struck on the rear right · stopped
- Crash With
- Van
- 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
- Making Right Turn
- 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 November [XXX], 2025 at 10:36 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was stopped facing south with its right turn signal activated on [XXX] for a stop sign at the intersection with [XXX]. While the Waymo AV remained stopped for westbound traffic on [XXX], a van that was traveling eastbound on [XXX] and making a right turn towards the intersection with [XXX] 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. 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-13235WaymoSource file ↗No injury reported2025-11NHTSAAvrideAustin31101-13439Passenger Car · struck on the front · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 30
- 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.
Avride car was traveling on the side road next to an off ramp with a vehicle attempting to lane change into our lane. The other driver had the blinker ON indicating to lane change. Avride car drove past it leading the other vehicle to have to wait to lane change. As Avride car approaches the intersection at a red light, the other vehicle then comes out from behind the rover to the left lane again, cuts the rover off and then drives off.
cause not established31101-13439AvrideSource file ↗Property damage only2025-11NHTSAWaymoPhoenix30270-13165Passenger 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
- 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 3:27 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 northbound on [XXX] in the left lane on [XXX] when it slowed to a stop to yield to a pedestrian that had begun crossing the roadway from the east side of [XXX]. While the pedestrian continued to cross the Waymo AV's lane of travel and the Waymo AV remained stopped, a passenger car that was traveling northbound in the left lane 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-13165WaymoSource file ↗Property damage only2025-11NHTSAWaymoWest Hollywood30270-13243Bus · struck on the rear · stopped
- Crash With
- Bus
- 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
- Investigating Agency
- West Hollywood Sheriff's 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 4:58 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was parked at the curb with its hazard lights activated for a passenger drop-off facing east on [XXX] just east of the intersection with [XXX] and [XXX] when a bus traveling eastbound in the rightmost lane on [XXX] passed the Waymo AV on the left, and the right side of the bus 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-13243WaymoSource file ↗Minor injury2025-11NHTSAWaymoLos Angeles30270-13195SUV · struck on the rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- 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
- 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 November [XXX], 2025 at 10:15 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 stopped facing north in the left turn lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the light turned green and traffic ahead advanced, the Waymo AV proceeded forward before coming to a stop partially in the marked crosswalk with hazard lights activated. An SUV that was initially stopped directly behind the Waymo AV proceeded forward and came to a stop directly behind the stationary Waymo AV. While the Waymo AV and the SUV were stopped, a pickup truck that was initially stopped directly behind the SUV approached the stopped SUV from behind and the front of the pickup truck made contact with the rear of the stationary SUV. The front of the SUV 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. The passenger in the Waymo AV alleged minor injury. 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-13195WaymoSource file ↗No injury reported2025-11NHTSATeslaAustin13781-13237struck on the rear left, rear right · stopped
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left, Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TESLA
- Model
- Model Y
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.
Summary: This updated report does not report a new incident or make any material changes to the factual record. It only removes confidential or personally identifying information to make the incident narrative publicly available. The Tesla ADS was stopped behind traffic at an intersection with a red light. A person on a motor scooter (VRU) approached the ADS from behind and moved into a gap directly behind the ADS. As the VRU was directly behind the stopped ADS, the VRU steered right and made contact with the ADS's rear end. Afterwards the VRU hopped the right curb and continued to proceed straight on the sidewalk. Safety monitor and passenger were present in the vehicle.
cause not established13781-13237TeslaSource file ↗Property damage only2025-11NHTSAWaymoWest Hollywood30270-13199Pickup Truck · struck on the rear · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 November [XXX], 2025 at 2:48 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing south with its right turn signal activated, partially in the right turn lane and partially in the second from the right lane, on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a pickup truck that was initially stopped in the second from the right lane directly behind the Waymo AV proceeded forward and the front right side of the pickup truck 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-13199WaymoSource file ↗Property damage only2025-11NHTSAWaymoLos Angeles30270-13373Passenger Car · struck on the 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
- Right
- SV Precrash Speed (MPH)
- 22
- CP Pre-Crash Movement
- Entering Traffic
- 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 November [XXX], 2025 at 12:14 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 northwestbound on [XXX] when it approached a passenger car slowly exiting a driveway in front of and to the right of the Waymo AV. As the Waymo AV passed the passenger car, the passenger car proceeded forward into the roadway and 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. 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-13373WaymoSource file ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-13206Heavy Truck · struck on the rear · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- 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 November [XXX], 2025 at 8:32 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on a narrow portion of [XXX] when it came to a stop to yield to a heavy truck traveling northeastbound on [XXX]. As the heavy truck was passing the Waymo AV, the rear left side of the heavy truck 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. 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-13206WaymoSource file ↗Property damage only2025-11NHTSAWaymoSan Francisco30270-13201First Responder Vehicle · struck on the front right · stopped
- Crash With
- First Responder Vehicle
- 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
- 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 November [XXX], 2025 at 6:08 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] and came to a stop to yield to a police SUV that was traveling southbound on [XXX] and had stopped in-lane. While the Waymo AV was stopped, the police SUV reversed and the rear of the police SUV 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-13201WaymoSource file ↗Property damage only2025-11NHTSAWaymoTempe30270-13085Passenger Car · struck on the 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
- Left
- SV Precrash Speed (MPH)
- 33
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 November [XXX], 2025 at 8:35 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 traveling westbound in the second from the right lane on [XXX], proceeding straight at a green light through the intersection with [XXX]. As the Waymo AV approached the exit of the intersection, a passenger car traveling eastbound on [XXX] in the leftmost designated left turn lane proceeded to make an unprotected left turn against a red light onto [XXX], entered the Waymo AV's lane of travel, the Waymo AV braked and maneuvered to the right, and the front of the passenger car made contact with the 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. 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-13085WaymoSource file ↗