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
6,008 records on file
362 death reports1987–202614 registries
Narrow it down
What happened
Country
Year
Property damage only2025-06NHTSAWaymoAustin30270-11238Passenger Car · struck on the rear left · stopped
- Crash With
- Passenger Car
- 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
- Changing Lanes
- CP Contact Area
- Front
- 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 10:56 PM 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 northbound on [XXX] in the left lane at a red light at the intersection with [XXX]. A passenger car approached the Waymo AV from behind and began to change lanes to the right of the Waymo AV, and the front driver side of the passenger car made contact with the rear passenger 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-11238WaymoSource file ↗Property damage only2025-06NHTSAWaymoAustin30270-11291Heavy Truck · struck on the 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
- Left
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 June [XXX], 2025 at 9:20 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a heavy truck on an unnamed service road off [XXX] near the intersection with [XXX]. The Waymo AV was traveling northwestbound in the right-most turn lane on an unnamed service road off [XXX] when it slowed at the intersection at [XXXX] to yield to northbound traffic in preparation for right turn onto northbound [XXX]. While the Waymo AV was slowing, a heavy truck that was stopped facing northwest in the left-most turn lane on the unnamed service road proceeded to turn right onto northbound [XXX] and crossed into the Waymo AV's lane of travel. The passenger side of the heavy 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. 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-11291WaymoSource file ↗Property damage only2025-06NHTSAWaymoMiami30270-11215Passenger Car · struck on the front · passing
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Passing
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 4
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Miami 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 9:22 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode in the left lane when it approached a passenger car stopped in the left lane with its left turn signal activated at the intersection with [XXX]. The Waymo AV merged into the right lane to pass the passenger car and the test driver disengaged the Waymo AV's ADS as the Waymo AV began to merge back into the left lane. As the test driver attempted to merge in front of the passenger car, the passenger car proceeded straight and the passenger side of the passenger car made contact with the front driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual 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-11215WaymoSource file ↗Property damage only2025-06NHTSAWaymoAustin30270-11146struck on the front, 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, Bottom
- SV Precrash Speed (MPH)
- 31
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- 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 June [XXX], 2025 at 1:28 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving debris on [XXX] near [XXX]. The Waymo AV was traveling southeastbound on [XXX] in the right lane when the vehicle traveling ahead of the Waymo AV made contact with a stationary piece of debris that was in the roadway. The Waymo AV then made contact with the debris as it was moving 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. 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-11146WaymoSource file ↗Property damage only2025-06NHTSAWaymoLos Angeles30270-11193struck on the front right · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 2
- 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 2:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a chain in a parking lot at [XXX]. The Waymo AV was traveling southwestbound in a parking lot at [XXX] when the front of the Waymo AV made contact with a chain separating a section of the parking lot. 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-11193WaymoSource file ↗Property damage only2025-06NHTSAWaymoAustin30270-11173Pickup Truck · struck on the right, front right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Right, Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Rear Right, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- 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:36 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped in-lane facing west on [XXX] for a passenger pick-up with hazard lights activated. A pickup truck approached the Waymo AV from behind, and the front of the pickup truck made contact with the rear of the stationary Waymo AV. The pickup truck then reversed, maneuvered around the left of the Waymo AV, and stopped directly in front of the stationary Waymo AV. While the Waymo AV remained stopped, the pickup truck reversed again, and the rear of the pickup truck 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-11173WaymoSource file ↗No injury reported2025-06NHTSANuro, Inc.Santa Clara30291-11324struck on the front left · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 13
- CP Pre-Crash Movement
- Stopped
- CP Contact Area
- Front Right
- Within ODD?
- [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- TOYOTA
- Model
- Prius
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 Tuesday, June [XXX], 2025 a Nuro vehicle operating in autonomous mode encountered a trash bin that had been placed away from the curb, sticking out into the travel lane, and due to operator error, the side mirror tapped it. The bin was not damaged or moved, but a plastic attachment to the Nuro vehicle sustained negligible damage. Law enforcement was not involved and there were no injuries reported or VRUs present.
cause not established30291-11324Nuro, Inc.Source file ↗Property damage only2025-06NHTSAWaymoAustin30270-11217Passenger 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)
- 1
- 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 June [XXX], 2025 at 5:26 PM 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 southbound on [XXX] in the third from the right lane and came to a stop in a queue of traffic. As traffic in all lanes started to proceed forward, the Waymo AV slowly proceeded forward with its left turn signal activated, yielding to traffic and momentarily stopping in an attempt to merge into the left adjacent lane. A passenger car that was initially stopped directly behind the Waymo AV began to proceed forward 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, and a test driver was present (in the driver's seating position).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-11217WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11175SUV · struck on the rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On June [XXX], 2025 at 1:51 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo was traveling northbound in the right lane on [XXX] and came to a stop to yield to a vehicle with its hazard lights on stopped partially in-lane facing north on [XXX]. An SUV approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11175WaymoSource file ↗Property damage only2025-06NHTSAWaymoLos Angeles30270-11239struck 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)
- 7
- 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 12:18 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a chain in a parking lot at [XXX]. The Waymo AV was traveling southbound on [XXX] when it made a right turn into a parking lot at [XXX]. As the Waymo AV was traveling westbound into the parking lot, the front of the Waymo AV made contact with a hanging chain separating a section of the parking lot. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and the chain 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-11239WaymoSource file ↗Minor injury2025-06NHTSAWaymoAustin30270-11212SUV · 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
- 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 June [XXX], 2025 at 10:26 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the second lane from the right and came to a stop in a queue of traffic for a red light at the intersection at [XXX]. An SUV 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. The passenger in the Waymo AV alleged a 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-11212WaymoSource file ↗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 ↗Not graded by the source2025-06-01FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-35789da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: ON 06-JUN-2025, INTUITIVE SURGICAL, INC. (ISI) RECEIVED MEDWATCH REPORT (MDR) WITH UF/IMPORTER REPORT # (B)(4) STATING: "PATIENT HERE FOR ROBOTIC PROSTATECTOMY RETROPUBIC RADICAL WITH NERVE SPARING BY DR. [REDACTED]. WHEN SCOPE WAS BEING PLACED THROUGH THE UNIVERSAL SEAL "TOILET SEAT" UPON FIRST ENTRY THEY NOTICED A BLACK PIECE OF RUBBER INSIDE THE PATIENT. THE PIECE OF RUBBER WAS REMOVED WITH THE PIECE FULLY INTACT, AND A METHODICAL SWEEP OF THE CAVITY WAS PERFORMED BY THE SURGEON WITH NO OTHER PIECES FOUND. SURGEON CONTINUED THE SURGERY WITHOUT ANY COMPLICATIONS. AFTER THE PROCEDURE THE PIECE OF RUBBER WAS COMPARED TO THE MISSING PIECE UNDER THE UNIVERSAL SEAL AND BOTH PIECES MATCHED WITH NO OTHER MISSING PARTS AND SURGEON CONFIRMED. THE COMPANY WAS NOTIFIED. PER REPORTING CONTACT, "PER REPORTING CONTACT, THE COMPANY WAS MADE AWARE OF THE ISSUE AND CAME INTO THE HOSPITAL THE NEXT DAY. THERE WAS NO PATIENT HARM, BUT WE CANNOT RETURN TO MFG [MANUFACTURER] BECAUSE THE PRODUCT WAS TOSSED OUT AFTER THE SURGEON EXAMINED THE PRODUCT INTO A SHARPS CONTAINER."
cause not established2955842-2025-35789Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗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-31FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-04833da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF A LITERATURE ARTICLE "SURGICAL OUTCOMES OF ROBOTIC HYSTERECTOMY FOR LARGE UTERUS WEIGHING MORE THAN 1000 G: A RETROSPECTIVE STUDY FROM A HIGH-VOLUME CENTER" WAS PERFORMED. THIS RETROSPECTIVE STUDY DATA FROM THE HOSPITAL WAS REVIEWED BETWEEN JANUARY 2014 TO DECEMBER 2023 AND AIMED TO INVESTIGATE THE IMPACT OF VARIOUS RISK FACTORS ON SURGICAL OUTCOMES AND TO IDENTIFY THE MOST EFFECTIVE SURGICAL APPROACH FOR PERFORMING RADICAL HYSTERECTOMIES ON UTERI GREATER THAN 1000 G IN BENIGN CONDITIONS. A TOTAL OF 86 PATIENTS WERE INCLUDED IN THE ANALYSIS, AND THE AVERAGE AGE OF THE STUDY POPULATION WAS 47.1 +/- 4.5 YEARS, WITH A MEAN BODY MASS INDEX OF 25.1 +/- 4.0 KG/M2. THE ARTICLE DESCRIBES SOME SPECIFIC INTRA-OPERATIVE COMPLICATIONS WITH MINIMAL DETAILS. A SMALL PERCENTAGE OF PATIENTS (4.7%) REQUIRED CONVERSION TO OPEN SURGERY. A TOTAL OF 4 INCIDENTS OF ORGAN INJURIES WERE RECORDED; ONE PATIENT EXPERIENCED A BLADDER INJURY, AND THREE PATIENTS EXPERIENCED VAGINAL LACERATIONS, ALL OF WHICH REQUIRED INTRAOPERATIVE REPAIR WITHOUT SUBSEQUENT COMPLICATIONS. ADDITIONALLY, SIX CASES NECESSITATED INTRAOPERATIVE BLOOD TRANSFUSIONS. POST-OPERATIVELY, ONE PATIENT SUFFERED A CUFF INFECTION AN
cause not established2955842-2026-04833Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-05-31FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-29251da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF AN ARTICLE THAT EVALUATED THE COMPARISON OF SINGLE-PORT VERSUS MULTI-PORT ROBOTIC RADICAL PROSTATECTOMY IN ELDERLY PATIENTS, FOCUSING ON PERIOPERATIVE OUTCOMES AND POSTOPERATIVE COMPLICATIONS WAS PERFORMED. THE STUDY RETROSPECTIVELY ANALYZED 338 PATIENTS UNDERGOING ROBOT-ASSISTED RADICAL PROSTATECTOMY (SINGLE-PORT (SP-RARP)OR MULTI-PORT (MP-RARP) BETWEEN JANUARY 2018 AND DECEMBER 2023. ONE RECTAL INJURY OCCURRED IN THE MP GROUP, WHILE THE SP GROUP HAD TWO EVENTS (RECTAL AND BLADDER INJURY). IN ELDERLY PATIENTS, THE MP GROUP HAD TWO COMPLICATIONS (RECTAL INJURY AND CONVERSION TO OPEN SURGERY DUE TO HEMODYNAMIC INSTABILITY), WHEREAS THE SP GROUP HAD SIX COMPLICATIONS (RECTAL INJURY, BLADDER INJURY, OBTURATOR NERVE INJURY, AND PERSISTENT PNEUMOPERITONEUM); ALL WERE MANAGED INTRAOPERATIVELY. POSTOPERATIVE CLAVIEN¿DINDO GRADE 3 COMPLICATIONS INCLUDED PARALYTIC ILEUS AND LYMPHOCELES REQUIRING DRAINAGE IN THE MP GROUP AND LYMPHOCELES IN THE SP GROUP. ONE PATIENT IN THE MP GROUP DIED DUE TO POSTOPERATIVE UROSEPSIS (CLAVIEN¿DINDO GRADE 5); HOWEVER, THE REPORT DOES NOT CLEARLY DESCRIBE THE CLINICAL SEQUENCE OR ESTABLISH WHETHER THIS OUTCOME WAS DIRECTLY ATTRIBUTABLE TO A SPECIFIC
cause not established2955842-2026-29251Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-05-30FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-27515da Vinci Surgical System
da Vinci Surgical System — 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 DA VINCI-ASSISTED NIPPLE SPARING MASTECTOMY SURGICAL PROCEDURE, THE PATIENT SUFFERED A BURN. AT THIS TIME, IT IS UNKNOWN WHAT CAUSED THE THERMAL DAMAGE TO OCCUR OR THE EXTENT OF THE INJURY. THE PROCEDURE WAS COMPLETED ROBOTICALLY. INTUITIVE SURGICAL, INC. (ISI) ATTEMPTED FOLLOW-UP TO OBTAIN ADDITIONAL INFORMATION. HOWEVER, NO FURTHER DETAILS HAVE BEEN RECEIVED AS OF THE DATE OF THIS REPORT.
cause not established2955842-2025-27515Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-05-30FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-24661da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A REVIEW OF AN ARTICLE THAT EVALUATED THE CLINICAL EFFECT OF CONTINUOUS IMPROVEMENT OF PERIOPERATIVE NURSING QUALITY IN PATIENTS WITH DA VINCI ROBOT-ASSISTED LAPAROSCOPIC RADICAL PROSTATECTOMY. A TOTAL OF SEVEN PATIENTS EXPERIENCED COMPLICATIONS, INCLUDING DEEP VEIN THROMBOSIS. NO DEVICE MALFUNCTIONS WERE REPORTED, AND THE AUTHORS DID NOT REPORT ANY EVENTS CAUSED BY ANY ISI DEVICE. MULTIPLE ATTEMPTS WERE MADE TO CONTACT THE CORRESPONDING AUTHOR; HOWEVER, NO RESPONSE HAS BEEN RECEIVED.
cause not established2955842-2026-24661Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-05-30FDA MAUDEStryker3005985723-2025-00291Mako Robotic-Arm
Mako Robotic-Arm — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: AFTER BURRING THE AREA NEAR THE PROXIMAL INTERCONDYLAR EMINENCE OF THE TIBIA WITH MAKOPKA AND PLACING THE TRIAL, IT WAS DISCOVERED THAT THE INTERCONDYLAR EMINENCE HAD BEEN CUT DOWN BY ABOUT 5 MM (1/3) MORE THAN THE PLANNED LINE. THE ATTACHMENT SITE OF THE ACL HAD BECOME UNSTABLE, SO A BONE GRAFT WAS PERFORMED TO COMPLETE THE SURGERY.
cause not established3005985723-2025-00291StrykerRead the record ↗Not graded by the source2025-05-30FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-26518da Vinci Surgical System
da Vinci Surgical System — 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 DA VINCI-ASSISTED ADRENALECTOMY PROCEDURE, THE INTUITIVE SURGICAL, INC, (ISI) CLINICAL SALES REPRESENTATIVE (CSR) CONTACTED A TECHNICAL SUPPORT ENGINEER (TSE) AND REPORTED THAT THE CONSOLE WOULD NOT POWER ON AFTER THE CUSTOMER HAD ALREADY DOCKED TO THE PATIENT. THE CSR CHECKED THE WALL POWER, MOVED THE POWER CORD TO ANOTHER OUTLET, AND VERIFIED THAT THE WALL POWER WAS GOOD. THE CONSOLE BREAKER WAS CHECKED AND CYCLED ON AND OFF, BUT THE CONSOLE STILL DID NOT POWER ON. THE SYSTEM LOGS INDICATED THAT NO CONSOLE WAS CONNECTED, SUGGESTING A POSSIBLE MEDICAL GRADE POWER SUPPLY (MGPS) FAILURE. THE ENTIRE SYSTEM WAS SWAPPED OUT, AND THE PROCEDURE WAS CONVERTED FROM A SINGLE PORT TO A MULTI-PORT PROCEDURE. THE PROCEDURE WAS COMPLETED WITH A XI SYSTEM.
cause not established2955842-2025-26518Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗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 MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-24191da Vinci Surgical System
da Vinci Surgical System — 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 DA VINCI-ASSISTED INGUINAL HERNIA BILATERAL SURGICAL PROCEDURE, AT THE END OF THE PROCEDURE, THEY NOTICED A PLASTIC PIECE FROM THE CANNULA SEAL HAD FALLEN INTO THE PATIENT. THE ITEM WAS RETRIEVED WITHOUT ANY HARM. THE PROCEDURE WAS COMPLETED.
cause not established2955842-2025-24191Intuitive Surgical, Inc.da Vinci Surgical SystemRead 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 MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-23802da Vinci Surgical System
da Vinci Surgical System — 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 DA VINCI-ASSISTED SURGICAL PROCEDURE, MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY FELL INSIDE THE PATIENT. THE SURGEON DIDN'T REALIZE IT FELL UNTIL THEY FINISHED THE CASE AND WERE DOING THE COUNTING. THE PATIENT WAS STILL ON THE TABLE, SO A CT SCAN WAS DONE TO LOCATE THE MCS TIP COVER. THE CUSTOMER WAS ABLE TO RETRIEVE IT, HOWEVER, THEY SAID IT TOOK THEM A LONG TIME WHICH CAUSED A DELAY TO THE CASE. NOT SURE THE EXACT DELAY TIME BUT IT WAS LONG. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE INSTRUMENT AND THE MCS TIP COVER ACCESSORY WERE INSPECTED PRIOR TO USE AND NO DAMAGE WAS NOTED. THE SURGEON OPENED THE PATIENT AND FOUND THE MISSING MCS TIP COVER ACCESSORY. SURGERY WAS COMPLETED WHEN THE MCS TIP COVER WAS FOUND. THE SCRUB TECHNICIAN NOTICED A MISSING TIP COVER AT THE END OF THE CASE ONCE THE COUNT NUMBER WAS OFF ON THE MATERIALS USED IN THE CASE. IT IS UNKNOWN WHAT THE SURGEON BELIEVES WAS THE CAUSE OF THE INSTRUMENT ACCESSORY SLIP-OFF. THE MCS TIP COVERS ARE IN USE FOR 30 MINUTES. NO ISSUES WITH THE FUNCTIONALITY OF THE MCS INSTRUMENT
cause not established2955842-2025-23802Intuitive Surgical, Inc.da Vinci Surgical SystemRead 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-19FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-23045da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A PATIENT WHO WAS ENROLLED IN A STUDY UNDERWENT A DA VINCI ASSISTED NIPPLE SPARING MASTECTOMY SURGICAL PROCEDURE (MALIGNANT WITH ONE-STAGE IMPLANT RECONSTRUCTION) WITH CARBON DIOXIDE (CO2) INSUFFLATION. INTRA-OPERATIVELY, A SKIN BURN WAS OBSERVED ON THE LEFT BREAST. AFTER UNDOCKING THE ROBOT, TURNING LIGHTS ON AND INSPECTING SKIN FLAPS, THERE WERE THREE SITES NOTED (IN THE UPPER OUTER AND UPPER INNER QUADRANTS) WHERE A SUB CM BLISTER WAS NOTED, EVIDENCE OF THERMAL INJURY SUSTAINED DURING THE ROBOTIC ANTERIOR FLAP DISSECTION. AT THE END OF THE CASE, NITROPASTE AND XEROFORM GAUZE WERE APPLIED TO THESE AREAS TO ENHANCE PERFUSION AND MAINTAIN INTEGRITY OF THE SKIN FLAP, RESPECTIVELY. THE EVENT IS REPORTED AS ONGOING, NO FURTHER TREATMENT WAS PROVIDED, AND THERE WAS NO PROLONGED HOSPITALIZATION ATTRIBUTE TO THIS SPECIFIC EVENT. THE PATIENT WAS DISCHARGED ON POST-OPERATIVE DAY TWO. THERE WAS NO REPORT OF A DA VINCI DEVICE MALFUNCTION. THE STUDY INVESTIGATOR REPORTED THE EVENT AS MILD SEVERITY, NOT A SERIOUS ADVERSE EVENT (SAE), THERE WAS NO PROLONGED HOSPITALIZATION ATTRIBUTED TO THIS SPECIFIC EVENT, NOT RELATED TO A DA VINCI DEVICE, NOT RELATED TO THE RECONSTRUCTION PROCEDURE, NOT RELAT
cause not established2955842-2025-23045Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-05-19FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-23027da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A PATIENT WHO WAS ENROLLED IN A STUDY UNDERWENT A DA VINCI ASSISTED NIPPLE SPARING MASTECTOMY PROCEDURE. DURING SURGERY, THE PATIENT EXHIBITED CREPITUS IN THE ARMS ALONG WITH FACIAL AND NECK SWELLING; END-TIDAL CO2 AND ALL VITAL SIGNS REMAINED STABLE. INSUFFLATION PRESSURE, WHICH HAD BRIEFLY BEEN INCREASED FROM 10 MMHG TO 12 MMHG TO IMPROVE WORKING SPACE, WAS REDUCED BACK TO 10 MMHG, AND THE PROCEDURE WAS COMPLETED ROBOTICALLY WITHOUT ANY COMPROMISE TO THE PATIENT¿S HEMODYNAMIC STATUS. THE POST-PROCEDURE CHEST X-RAY NOTED A SMALL TO MODERATE RIGHT PNEUMOTHORAX. THE NEXT DAY, REPEAT CHEST X-RAY SHOWED A MODERATE SIZED RIGHT PNEUMOTHORAX, PNEUMOMEDIASTINUM, AND PNEUMOPERITONEUM IN THE SETTING OF EXTENSIVE SUBCUTANEOUS EMPHYSEMA. THE PATIENT DENIED DYSPNEA AND REMAINED HEMODYNAMICALLY STABLE WITH NORMAL OXYGEN SATURATION ON ROOM AIR. NO CHEST TUBE WAS PLACED AND THE PATIENT REMAINED HOSPITALIZED FOR OBSERVATION ONLY. A CHEST CT SCAN AND SERIAL CHEST X-RAYS SHOWED STABILITY OF THE SIZE OF THE PNEUMOTHORAX, PNEUMOMEDIASTINUM AND PNEUMOPERITONEUM. THE PATIENT REMAINED STABLE ON ROOM AIR WITH NO DYSPNEA AND WAS DISCHARGED HOME THREE DAYS POST-PROCEDURE.
cause not established2955842-2025-23027Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-05-16FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-23482da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.
cause not established2955842-2025-23482Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗