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
Minor injury2025-06NHTSAWaymoAtlanta30270-11219Heavy Truck · struck on the rear · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- 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 June [XXX], 2025 at 12:11 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and came to a stop to yield to a heavy truck traveling westbound on a portion of [XXX] with vehicles parked at both curbs. As the heavy truck passed the stationary Waymo AV, the driver side of the heavy truck made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger in the Waymo AV alleged a minor injury. 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-11219WaymoSource file ↗Property damage only2025-06NHTSAWaymoAustin30270-11246Pickup Truck · struck on the left · making left turn
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 10
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 June [XXX], 2025 at 6:59 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing east in the outer dedicated left turn lane on [XXX] for a red light at the intersection at [XXX]. When the light turned green, the Waymo AV initiated a left turn from the outer left turn lane into the center lane of northbound [XXX]. While the Waymo AV was completing its left turn, a pickup truck turning left from the inner dedicated left turn lane entered the center lane of northbound [XXX], crossing the dotted white lane line. The front passenger side of the pickup truck made contact with the driver 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. 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-11246WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11210Passenger 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
- Changing Lanes
- 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 June[XXX], 2025 at 3:09 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 northeastbound on [XXX] in the second from the right lane and stopped in a queue of traffic for a red light at the intersection at [XXX]. A passenger car traveling northeastbound on [XXX] approached the Waymo AV from behind and attempted to change lanes into the left lane. As the passenger car passed the Waymo AV, the passenger side of the passenger car made contact with the rear driver 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-11210WaymoSource file ↗Property damage only2025-06NHTSAWaymoPhoenix30270-11160Passenger 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
- 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 June [XXX], 2025 at 11:46 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and came to a stop for a red light at the intersection with [XXX]. A passenger car traveling southbound 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-11160WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11213Bus · struck on the left · parked
- Crash With
- Bus
- 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 June [XXX], 2025 at 11:17 AM 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 towards the curb, with the driver side rear of the vehicle partially in lane facing north on [XXX] for a passenger drop-off. As a bus traveling northbound on [XXX] attempted to pass to the left of the Waymo AV, a passenger in the Waymo AV opened the rear driver side door of the Waymo AV and the passenger side of the bus made contact with the rear driver side door of the stationary Waymo AV. The passengers in the Waymo AV were not belted at the time of the collision as they were exiting. 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-11213WaymoSource file ↗Property damage only2025-06NHTSAWaymoAustin30270-11247Heavy 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
- Left
- 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 June [XXX], 2025 at 6:11 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a box truck on [XXX] near [XXX]. The Waymo AV was traveling northwestbound on a narrow portion of [XXX] when it came to a stop to yield to an approaching box truck traveling southeastbound on [XXX]. While the Waymo AV remained stopped, the box truck proceeded forward to pass the Waymo AV and the driver side of the box truck made contact with the rear driver 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-11247WaymoSource file ↗No injury reported2025-06NHTSAWaymoPhoenix30270-11204Van · struck on the front · stopped
- Crash With
- Van
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Lane / Road Departure
- CP Contact Area
- Front 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 June [XXX], 2025 at 5:58 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a van at the entrance of a parking lot at [XXX]. The Waymo AV was stopped facing south at the entrance of a parking lot at [XXX] while yielding to traffic and preparing to make a left turn at the intersection at [XXX]. As the Waymo AV remained stopped, a van traveling westbound in the rightmost lane on [XXX] traveled onto the north sidewalk of [XXX]. It then entered the parking lot entrance from the sidewalk, traveling perpendicular to the standard direction of travel. The front of the van made contact with the front driver side of the Waymo AV, which was still stationary at intersection, causing the Waymo AV to spin and the front of the Waymo AV to then make contact with a sign pole. 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-11204WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11218Bus · struck on the left · parked
- Crash With
- Bus
- 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
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 June [XXX], 2025 at 6:48 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was parked facing south in the right lane on [XXX] at the intersection at [XXX] for a passenger drop-off with hazard lights activated. A bus was traveling southbound on [XXX] in the left adjacent lane. As the bus proceeded forward past the Waymo AV on the left, a Waymo AV passenger opened the rear driver side door and the front passenger side of the bus made contact with the rear driver side door of the Waymo AV. Three of the four passengers inside the Waymo AV were not belted at the time of impact. 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-11218WaymoSource file ↗Minor injury2025-06NHTSAWaymoSan Francisco30270-11192Passenger Car · struck on the rear · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- 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
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On June [XXX], 2025 at 2:27 PM 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 stopped facing north in the rightmost lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a passenger car that was stopped in the leftmost lane of [XXX], oriented diagonally relative to the roadway facing northeast after exiting a parallel parking spot at the west side curb of [XXX], proceeded northeastbound into the rightmost lane and the front of the passenger car made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Neither vehicle sustained damage. A passenger in the Waymo AV reported a minor injury 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-11192WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Bruno30270-11195struck 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)
- 6
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On June [XXX], 2025 at 6:34 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Bruno, California was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] when the front of the Waymo AV made contact with a fallen utility line hanging across 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. 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-11195WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11163Van · struck on the rear · parked
- Crash With
- Van
- 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
- 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 June [XXX], 2025 at 3:21 PM 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 parked towards the curb, with the driver side rear partially in lane on eastbound [XXX] at the designated passenger loading zone with its hazard lights activated for a passenger pick-up. A van traveling northbound on [XXX] began to turn right onto [XXX], and came to a stop mid turn behind the Waymo AV. The van then attempted to complete the right turn, passing the Waymo AV on the left side and the passenger side of the van made contact with the rear driver 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 two passengers did not have their seatbelts as they were entering the Waymo AV at the time of the collision. 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-11163WaymoSource file ↗Property damage only2025-06NHTSAWaymoTempe30270-11161struck on the front · backing
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Backing
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- 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 June[XXX], 2025 at 5:04 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a trailer hitch attached to a trailer in a parking lot at [XXX]. The Waymo AV was traveling southbound in the parking lot of [XXX] and came to a stop to complete a multi-point turn. A trailer was parked in a parking stall located on the driver side of the Waymo AV. As the Waymo AV initiated its multi-point maneuver, it reversed northbound and the front driver side of the Waymo AV made contact with the hitch of the trailer. 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-11161WaymoSource file ↗Property damage only2025-06NHTSAWaymoSanta Monica30270-11207Passenger 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 June [XXX], 2025 at 5:01 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked at the curb facing northeast on [XXX] for a passenger drop-off when a passenger car traveling northeast on [XXX] passed the Waymo AV. While the passenger car passed the parked Waymo AV, a passenger in the Waymo AV opened the rear driver side door, and the passenger side of the passenger car made contact with the opened rear driver side door 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 passengers in the Waymo AV were not belted at the time of the collision, as they were preparing to exit the Waymo AV. 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-11207WaymoSource file ↗Property damage only2025-06NHTSAWaymoScottsdale30270-11275struck on the front left, 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
- Front Left, Bottom
- SV Precrash Speed (MPH)
- 39
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On June [XXX], 2025 at 11:29 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving an unattended bicycle in the roadway on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the rightmost lane of [XXX] when the Waymo AV's front passenger side and undercarriage made contact with an unattended bicycle that was laying 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. 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-11275WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11189Heavy 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
- 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 June [XXX], 2025 at 9:00 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 southbound on a narrow portion of [XXX] and came to a stop to yield to a heavy truck traveling northbound on [XXX]. As the heavy truck passed the Waymo AV, the driver side of the heavy truck made contact with the rear driver 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-11189WaymoSource file ↗No injury reported2025-06NHTSAZooxSan Francisco30610-11331Passenger Car · struck on the rear · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 9
- CP Pre-Crash Movement
- Crossing into Opposing Lane
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Highlander
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
A Zoox vehicle (Vehicle 1), operating in manual mode, was heading south on [XXX], in the southbound lane, approaching [XXX] in San Francisco, when it encountered a passenger car (Vehicle 2) traveling north and occupying both the northbound and southbound lanes on [XXX]. The Zoox vehicle slowed and moved to the right for the oncoming Vehicle 2 however, as Vehicle 2 passed, its driver's side mirror made contact with the driver's side rear of the Zoox vehicle. The driver of Vehicle 2 failed to stop and exchange information. The Zoox vehicle did not sustain any damage, but Vehicle 2 appeared to have sustained minor damage to its driver's side mirror. There were no reported injuries, and the police were not notified.
cause not established30610-11331ZooxSource file ↗No injury reported2025-06NHTSAWaymoChandler30270-11209struck on the bottom · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- 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
- 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 June [XXX], 2025 at 9:05 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an elevated gate track in a parking lot at [XXX]. The Waymo AV was traveling eastbound in a parking lot at [XXX] through a gate opening when the bottom of the Waymo AV made contact with the elevated gate track. 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-11209WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11170Passenger Car · struck on the front right · parked
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- 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 June [XXX], 2025 at 9:26 AM 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 parked at the curb facing north on [XXX] when a passenger car attempting to parallel park directly in front of the Waymo AV proceeded to reverse, and the back 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-11170WaymoSource file ↗Property damage only2025-06NHTSAWaymoPhoenix30270-11177SUV · 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 June [XXX], 2025 at 12:45 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south in the second from the right lane on [XXX] for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, an SUV that was initially stopped directly behind the Waymo AV approached the Waymo AV 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-11177WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11194SUV · struck on the rear · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- 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 June [XXX], 2025 at 4:18 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 stopped facing southwest on [XXX] for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, an SUV that was initially stopped directly behind the Waymo AV proceeded to maneuver around the Waymo on the left, and the passenger side of the SUV made contact with the rear driver 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-11194WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11162SUV · struck on the rear · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- 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 June [XXX], 2025 at 4:47 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 northbound on [XXX] and making a slight right onto [XXX] when it came to a stop on the right side of its lane to yield to an SUV traveling southwestbound on [XXX]. The SUV attempted to pass the stationary Waymo AV, stopped momentarily, and then began to reverse. The SUV then continued its attempt to pass, and the front driver side of the SUV made contact with the rear driver 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-11162WaymoSource file ↗Property damage only2025-06NHTSAWaymoPhoenix30270-11206struck 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)
- 21
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- 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 June [XXX], 2025 at 11:04 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a tire on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] in the second from the right lane when several tires fell from a trailer pulled by a recreation vehicle traveling westbound on [XXX] in front of the Waymo AV. The tires rolled into the roadway and the front of the Waymo AV made contact with one of the tires, which then went under 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. The 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-11206WaymoSource file ↗Property damage only2025-06NHTSAZooxParadise30610-11166Pickup Truck · struck on the rear left, rear, rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left, Rear, Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left, Front, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Highlander
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling in the left through lane (lane #2) on westbound [XXX], approaching [XXX] in Las Vegas. The Zoox vehicle operator disengaged from autonomy after the traffic light at [XXX] transitioned from green to yellow and braked, bringing the Zoox vehicle to a stop, at which point it was rear-ended by a pickup truck (Vehicle 2) traveling behind. Both vehicles sustained minor damage however, the Zoox vehicle was towed from the scene as its operator was not comfortable driving it back. There were no reported injuries, and the police were not notified.
cause not established30610-11166ZooxSource file ↗Not graded by the source2025-05-29FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00127ExcelsiusGPS
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 EXCELSIUSHUB SYSTEM, AN INTRA-OPERATIVE CORRECTION WAS REQUIRED FOR A MISPLACED IMPLANT.
cause not established3004142400-2025-00127Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-05-21FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00021Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THE PHYSICIAN STARTED THE CASE WITH ENDOBRONCHIAL ULTRASOUND (EBUS) AND THEN SWITCHED TO MONARCH. DURING THE PROCEDURE, THE PHYSICIAN ENCOUNTERED SYSTEM FAULT MESSAGES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00021Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-05-20FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00020Monarch Platform
Monarch Platform — 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 A MONARCH BRONCHOSCOPY PROCEDURE, THE PHYSICIAN ENCOUNTERED NAVIGATION ISSUES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00020Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-05-20FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00019Monarch Platform
Monarch Platform — 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 A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN ENCOUNTERED SYSTEM FAULT MESSAGES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00019Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-05-12FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00143ExcelsiusGPS
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 IMPLANTS USING THE EXCELSIUS GPS SYSTEM WERE MISPLACED INTRA-OPERATIVELY AND THEN REMOVED AND REPLACED.
cause not established3004142400-2025-00143Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-05-06FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00018Monarch Platform
Monarch Platform — 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 A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN ENCOUNTERED NAVIGATION ACCURACY ISSUES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT..
cause not established3014447948-2025-00018Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-05-06FDA MAUDEAuris HealthMonarch PlatformMW5170510Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: DURING MULTIPLE PROCEDURES, THE MONARCH ROBOT NAVIGATION SYSTEM WAS UNSURE WHICH AREA OF THE LUNG IT WAS IN WITH DISTANCE MEASUREMENTS VARYING UP TO 30MM. BIOMED WAS ABLE TO RECREATE PRODUCT ISSUE IN DEMO ENVIRONMENT. PROBLEMS INTERMITTENTLY BEGAN AFTER SOFTWARE UPDATE 5 WEEKS AGO BUT BECAME MORE CONSISTENT LAST WEEK.
cause not establishedMW5170510Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-05-06FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00017Monarch Platform
Monarch Platform — 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 A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN ENCOUNTERED SYSTEM FAULT MESSAGES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00017Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-05-02FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00125ExcelsiusGPS
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, THE CASE WAS ABORTED DUE TO PATIENT INJURY.
cause not established3004142400-2025-00125Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-04-30FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00016Monarch Platform
Monarch Platform — 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 A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN ENCOUNTERED SYSTEM FAULT MESSAGES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00016Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-04-28FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00121ExcelsiusGPS
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 SCREWS USING THE EXCELSIUS GPS SYSTEM WERE MISPLACED INTRA-OPERATIVELY AND THEN REMOVED AND REPLACED.
cause not established3004142400-2025-00121Globus MedicalExcelsiusGPSRead the record ↗Death reported2025-04-22FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-45559da Vinci Surgical System
da Vinci Surgical System — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF AN ARTICLE WAS CONDUCTED, WHICH AIMED TO EVALUATE THE INITIAL EXPERIENCE AND FEASIBILITY OF ROBOTIC-ASSISTED PYLORUS-PRESERVING PANCREATICODUODENECTOMY PROCEDURES (PPPD) USING THE DA VINCI SP SYSTEM VERSUS THE DA VINCI XI SYSTEM. THE STUDY WAS A RETROSPECTIVE CASE SERIES ANALYZING 14 PATIENTS UNDERGOING PPPD FROM DECEMBER 2021 AND SEPTEMBER 2023. ONE PATIENT WITH COMMON BILE DUCT CANCER DIED DURING AT AN UNSPECIFIED TIME POST-PROCEDURE DUE TO THE PROGRESSION OF CANCER. THERE WAS NO REPORT OR INDICATION IN THE ARTICLE OF ANY DA VINCI SP SYSTEM MALFUNCTIONS. MULTIPLE ATTEMPTS TO OBTAIN ADDITIONAL INFORMATION FROM THE CORRESPONDING AUTHOR WERE MADE; HOWEVER, NO RESPONSE HAS BEEN RECEIVED.
cause not established2955842-2025-45559Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-04-21FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00109ExcelsiusGPS
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, THE CASE WAS ABORTED AFTER BLEEDING WAS NOTICED. SHORTLY AFTER, THE PATIENT DISPLAYED SUSPECTED PRESENCE OF STROKE AND/OR HEMATOMA.
cause not established3004142400-2025-00109Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-04-18FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00123ExcelsiusGPS
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 SCREWS USING THE EXCELSIUS GPS SYSTEM WERE MISPLACED INTRA-OPERATIVELY AND THEN REMOVED AND REPLACED.
cause not established3004142400-2025-00123Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-04-08FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00120ExcelsiusGPS
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 SCREWS USING THE EXCELSIUS GPS SYSTEM WERE MISPLACED.
cause not established3004142400-2025-00120Globus MedicalExcelsiusGPSRead the record ↗Property damage only2025-04NHTSAWaymoPhoenix30270-11297struck on the front right, 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
- Front Right, Bottom
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- 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 April [XXX], 2025 at 7:21 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a chain at a parking lot entrance at [XXX]. The Waymo AV was traveling westbound on [XXX] when it made a left turn into a parking lot at [XXX]. As the Waymo AV proceeded to enter the parking lot, the front of the Waymo AV made contact with a chain hanging across the entrance to the parking lot. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The chain sustained damage. Waymo became aware of damage to the chain on June 26th, 2025. 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-11297WaymoSource file ↗Not graded by the source2025-04-01FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00015Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT AFTER A SUCCESSFUL ROBOTIC BRONCHOSCOPY PROCEDURE, THE PATIENT DEVELOPED A PNEUMOTHORAX. A VALVE WAS PLACED AND PATIENT WAS HOSPITALIZED. NO DEVICE ISSUES WERE REPORTED.
cause not established3014447948-2025-00015Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-03-31FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00014Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT AFTER A SUCCESSFUL ROBOTIC BRONCHOSCOPY PROCEDURE, THE PATIENT DEVELOPED A PNEUMOTHORAX. A CHEST TUBE WAS PLACED. NO SYSTEM ISSUES WERE REPORTED.
cause not established3014447948-2025-00014Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-03-28FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00013Monarch Platform
Monarch Platform — 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 A ROBOTIC BRONCHOSCOPY PROCEDURE THE PHYSICIAN HAD DIFFICULTY WITH THE PATIENT SENSORS AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00013Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-03-26FDA MAUDEZimmer Biomet0009617840-2025-00011ROSA Robotic Surgery
ROSA Robotic Surgery — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THE PATIENT PRESENTED 3 WEEKS OR 3 MONTHS POST-OP WITH A FRACTURED FEMUR AT THE LOCATION WHERE THE FEMORAL REFERENCE PINS WERE INSTALLED. ADDITIONAL SURGICAL INTERVENTION WAS REQUIRED TO CORRECT THE FRACTURE. NO FURTHER EVENT INFORMATION AVAILABLE AT THE TIME OF THIS REPORT.
cause not established0009617840-2025-00011Zimmer BiometRead the record ↗Not graded by the source2025-03-21FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00012Monarch Platform
Monarch Platform — 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 THE MONARCH BRONCHOSCOPY PROCEDURE, THE PHYSICIAN WAS PERFORMING THE BRONCHOALVEOLAR LAVAGE (BAL) WHEN THE PATIENT HAD A CARDIAC ARREST. THE PHYSICIAN WAS ABLE TO CONFIRM A PULSE BACK ON THE PATIENT. THE PATIENT IS IN STABLE CONDITION.
cause not established3014447948-2025-00012Auris HealthMonarch PlatformRead the record ↗Recall2025-03-20CPSCAiper25187
Aiper Seagull Pro Cordless Robotic Pool Vacuum Cleaners Recalled Due to Burn and Fire Hazards; Distributed by Shenzhen Aiper Intelligent Co. — Hazard: The recalled pool vacuum cleaner has a large current adapter that can overheat, posing burn and fire hazards. Reported incidents: The firm has received 19 reports of the recalled pool vacuums melting, smoking or catching on fire while charging causing five incidents of property damage. No injuries have been reported.
cause attributed by source25187AiperRead the record ↗Not graded by the source2025-03-20FDA MAUDEZimmer Biomet0009617840-2025-00008ROSA Robotic Surgery
ROSA Robotic Surgery — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT HAS BEEN REPORTED THROUGH A MEDWATCH RECEIVED FROM THE FDA ALLEDGING OCCURANCES OF INACCURATE CUTS AND INCORRECT PLACEMENT OF IMPLANTS RESULTING IN PATIENT INJURIES. NO FURTHER INFORMATION IS CURRENTLY AVAILABLE.
cause not established0009617840-2025-00008Zimmer BiometRead the record ↗Not graded by the source2025-03-19FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00011Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THE PHYSICIAN USED EBUS TO TARGET THE RIGHT UPPER LOBE (RUL). THE PHYSICIAN NOTICED THROUGH HIS MANUAL SCOPE THAT THERE WAS A SMALL LACERATION ON THE MUCOSA OF THE POST INTERIOR WALL OF THE RIGHT MAIN STEM. THE PHYSICIAN WAS NOT SURE HOW THIS OCCURRED. THE PHYSICIAN DECIDED TO ABORT THE CASE BECAUSE THEY DID NOT WANT TO CAUSE ANY FURTHER INJURY. THE PATIENT DID NOT EXPERIENCE ANY BLEEDING UPON WAKING UP. NOTABLY, THE ANESTHESIOLOGIST SUGGESTED THAT THE PATIENT MAY HAVE HAD FRAIL TISSUE, AND THE PHYSICIAN RECALLED A SIMILAR INCIDENT FROM TWO YEARS PRIOR IN THE SAME LOCATION, WHICH HAD RESOLVED WITHOUT COMPLICATIONS.
cause not established3014447948-2025-00011Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-03-13FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00009Monarch Platform
Monarch Platform — 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 A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN ENCOUNTERED DIFFICULTY NAVIGATING AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00009Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-03-12FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00149ExcelsiusGPS
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 SCREWS USING THE EXCELSIUS GPS SYSTEM WERE MISPLACED AND ADJUSTED INTRA-OPERATIVELY.
cause not established3004142400-2025-00149Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-03-12FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00010Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT AFTER THE BRONCHOSCOPY PROCEDURE, THE PATIENT DEVELOPED MEDIASTINAL EMPHYSEMA, AS INDICATED BY THE POSTOPERATIVE CT EXAMINATION. AFTER A FOLLOW-UP CT SCAN DEMONSTRATED RECOVERY, THE PATIENT WAS DISCHARGED ON (B)(6), FOLLOWING A TOTAL HOSPITAL STAY OF 6 DAYS.
cause not established3014447948-2025-00010Auris HealthMonarch PlatformRead the record ↗