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
Minor injury2025-07NHTSAZooxParadise30610-11515Pickup Truck · struck on the rear left, rear, rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- 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
- Las Vegas Metro Police Department
- Make
- TOYOTA
- Model
- Highlander
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling south on [XXX] in the right lane and slowing for a red emergency traffic signal at [XXX] in Las Vegas. Shortly after the Zoox vehicle came to a stop, a pickup (Vehicle 2) following directly behind was rear ended by an SUV (Vehicle 3) that failed to stop. Vehicle 2 then rear ended the stopped Zoox vehicle. The police arrived at the scene. The driver of Vehicle 3 reported that their "head hurt" but declined medical attention. The Zoox vehicle sustained minor damage.
cause not established30610-11515ZooxSource file ↗Property damage only2025-07NHTSAWaymoSan Mateo30270-11415Pickup Truck · struck on the 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 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
- 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 July [XXX], 2025 at 8:05 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Mateo, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing northwest in the right lane on [XXX] for a red light in a queue of traffic at the intersection at [XXX]. While the Waymo AV was stopped, a pickup truck traveling northwestbound in the right lane on [XXX] approached the Waymo AV from behind and the front of the pickup truck 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-11415WaymoSource file ↗Serious injury2025-07NHTSAWaymoSanta Clara30270-11403SUV · struck on the right · making left turn
- Crash With
- SUV
- Highest Injury Severity Alleged
- Moderate W/ Hospitalization
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 25
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Santa Clara 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 July [XXX], 2025 at 1:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Clara, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped on [XXX], preparing to turn right onto northeastbound [XXX] while yielding to oncoming traffic. Once oncoming traffic had cleared, the Waymo AV began to turn right into the rightmost lane on northeastbound [XXX]. As the Waymo AV was completing the right turn, the test driver transitioned the Waymo AV to manual mode. The test driver changed lanes without a signal activated, crossing through the center travel lane and into the dedicated left turn lane where the test driver began to make an unprotected left across southwestbound [XXX]. During this unprotected left turn, an SUV was traveling in the leftmost southwestbound lane. The SUV began to maneuver towards the rightmost lane while the test driver was completing the left turn, and the front of the SUV made contact with the passenger 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. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, a vehicle involved was towed away, and airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11403WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11413Heavy Truck · struck on the rear left · parked
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear Left
- 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
- 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 July [XXX], 2025 at 9:02 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a box truck on [XXX] near [XXX]. The Waymo was parked in-lane facing east on [XXX] with hazard lights activated to yield to construction blocking the intersection at [XXX]. While the Waymo AV was parked, a box truck traveling eastbound on [XXX] approached the Waymo AV from behind, and the front driver side of the box truck made contact with the rear passenger side of the stationary Waymo AV, as well as the passenger side of a pickup truck parked at the curb to the right 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-11413WaymoSource file ↗Property damage only2025-07NHTSAWaymoPhoenix30270-11417Passenger Car · struck on the front left · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 12
- CP Pre-Crash Movement
- Traveling Wrong Way
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Phoenix Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 1:35 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] near the [XXX] entrance. The Waymo AV was traveling northeastbound on [XXX] in the right lane. A passenger car was traveling southwestbound on the wrong side of median-divided [XXX], directly in the Waymo AV's lane of travel. The Waymo AV braked and initially maneuvered left to avoid the oncoming passenger car. However, the passenger car continued to proceed, maneuvering towards the Waymo AV. The Waymo AV then continued to brake and maneuvered back to the right, to again attempt to avoid the passenger car, but the passenger car once more maneuvered towards the Waymo AV. As the Waymo AV continued to brake and the passenger car continued off the southeast side of [XXX], the front passenger side of the passenger car made contact with the front passenger 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-11417WaymoSource file ↗Property damage only2025-07NHTSAWaymoAustin30270-11419struck on the top · 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
- Top
- SV Precrash Speed (MPH)
- 3
- 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 July [XXX], 2025 at 7:36 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving the roof of a covered parking stall at [XXX]. The Waymo AV was traveling northwestbound in a parking lot at [XXX] when the test driver transitioned the Waymo AV to manual mode. The test driver proceeded to make a right turn into a covered parking stall and the sensor mounted on the roof of the Waymo AV made contact with the front edge of the roof covering the parking stall. 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. 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-11419WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11378Pickup Truck · struck on the 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 Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 4:46 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] when it slowed to a stop for a queue of traffic yielding to a pedestrian that was crossing [XXX] inside the marked crosswalk ahead. An SUV travelling directly behind the Waymo AV was approached by a pickup truck from behind and the front driver side of the pickup truck made contact with the rear passenger side of the passenger car causing the passenger car to be pushed to the left onto the flush median. The pickup truck continued to proceed straight, and the front of the pickup truck made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11378WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11422struck on the bottom · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Bottom
- SV Precrash Speed (MPH)
- 7
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- 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 July [XXX], 2025 at 7:29 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a small dumbbell on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on [XXX] and the front right tire of the Waymo AV made contact with a small dumbbell in the Waymo AV's lane of travel. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The dumbbell 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-11422WaymoSource file ↗Property damage only2025-07NHTSAWaymoLos Angeles30270-11284SUV · 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 Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 8:28 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the rightmost lane facing eastbound on [XXX] at a red traffic light at the intersection with [XXX]. An SUV traveling southbound on [XXX] made a left turn onto [XXX]. As the SUV approached the Waymo AV, the SUV continued turning and moving forward, turning slightly into the center lane and the front passenger side of the SUV made contact with the rear driver side corner of the stationary Waymo AV, and the front driver side of the SUV made contact with the rear passenger side corner of a passenger car that was stopped in the center lane. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both the Waymo AV and the SUV sustained damage, and Waymo cannot confirm the presence or absence of damage to the passenger car as of the date of this submission. 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-11284WaymoSource file ↗Property damage only2025-07NHTSAWaymoLos Angeles30270-11414Passenger 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
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 7:35 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northeastbound in the third from the right lane on [XXX] and attempting to merge into the left turn lane when it stopped to yield to a queue of traffic that filled the left turn lane at the intersection at [XXX]. A passenger car traveling northeastbound on [XXX] in the third from the right lane attempted to change lanes to the right as it approached the Waymo AV, and the front driver side of the passenger car made contact with the rear passenger 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-11414WaymoSource file ↗Property damage only2025-07NHTSAWaymoLos Angeles30270-11384SUV · 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
- Partly Cloudy
- Investigating Agency
- Los Angeles Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 10:53 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] at a green light at [XXX] with its right turn signal activated, yielding to a queue of westbound traffic in the second to the right lane on [XXX] that had extended to the intersection. While the Waymo AV remained stopped, an SUV that was traveling southbound on [XXX] proceeded to pass the Waymo AV to the left to continue south on [XXX], 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. 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-11384WaymoSource file ↗Property damage only2025-07NHTSAWaymo30270-11302Passenger Car · struck on the rear · making left turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 11
- CP Pre-Crash Movement
- Making Left Turn
- 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 July [XXX], 2025 at 1:15 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound in the left turn lane on [XXX] when it proceeded to make a protected left turn at the intersection with [XXX]. As the Waymo AV was completing its turn onto the leftmost lane on westbound [XXX], a passenger car that was also making a left turn from northbound [XXX] approached the Waymo AV from behind 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. 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-11302WaymoSource file ↗Property damage only2025-07NHTSAWaymoInglewood30270-11430Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 6:43 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] and came to a stop for a queue of traffic turning left at the intersection with [XXX]. A passenger car approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11430WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11365Passenger 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
- 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 July [XXX], 2025 at 9:19 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing east in the second to the right lane of [XXX] in a queue of traffic for an active HAWK pedestrian beacon at the intersection at [XXX]. As the beacon changed to flashing and traffic ahead advanced, the Waymo AV proceeded forward and came to a stop before entering the crosswalk. A passenger car that was initially stopped directly behind the Waymo AV 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-11365WaymoSource file ↗Property damage only2025-07NHTSAWaymoScottsdale30270-11370Passenger 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 July [XXX], 2025 at 7:59 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in a queue of traffic facing west in the left-turn lane on [XXX] for a red traffic light at the intersection with [XXX]. When the traffic light turned green, the Waymo AV began to proceed forward with the queue of traffic, then slowed behind a passenger car that was waiting in the turn lane to make the unprotected left turn. While the Waymo AV was slowing, a passenger car that was initially stopped directly behind the Waymo AV approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11370WaymoSource file ↗Not graded by the source2025-07NHTSAZooxSan Francisco30610-11514Animal · struck on the front right, bottom · proceeding straight
- Crash With
- Animal
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right, Bottom
- SV Precrash Speed (MPH)
- 13
- CP Pre-Crash Movement
- Other, see Narrative
- 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) in autonomous mode was traveling in the left lane on southwest-bound [XXX] toward [XXX] in San Francisco when a ball, immediately followed by a dog, entered the roadway from between parked cars on the left side of [XXX] directly into the path of the Zoox vehicle. The Zoox vehicle braked in response, but its underbody made contact with the dog. The Zoox vehicle operator then disengaged autonomous mode and brought the vehicle to a stop. The Zoox vehicle operator then reversed the vehicle to free the dog. The dog owner did not indicate injuries to the dog at the scene. The dog and its owner then returned to the sidewalk and the Zoox vehicle operator drove the vehicle from the scene. The police were not called. Zoox subsequently received an email alleging injuries to the dog, "abrasions behind its left front leg and a possible cracked rib."
cause not established30610-11514ZooxSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11373Heavy Truck · struck on the rear · parked
- Crash With
- Heavy Truck
- 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
- 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 July [XXX], 2025 at 4:32 PM 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 parked at the curb facing southeast on [XXX] for a passenger pick-up when a heavy truck traveling southeastbound in the rightmost lane on [XXX] passed the Waymo AV. As the heavy truck passed the parked Waymo AV, the passenger side of the heavy truck bed 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 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-11373WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11421Passenger 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
- 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 July [XXX], 2025 at 3:50 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 traveling northbound in the right lane on [XXX] when it came to a stop in a queue of traffic for a red light at the intersection at [XXX]. A passenger car that was traveling behind the Waymo approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and the passenger car 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-11421WaymoSource file ↗Minor injury2025-07NHTSATeslaAustin13781-11459struck on the front right
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Other, see Narrative
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 8
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TESLA
- Model
- Model Y
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
Summary: This updated report does not report a new incident or make any material changes to the factual record. It only removes confidential or personally identifying information to make the incident narrative publicly available. The Tesla ADS was stopped on the right side of the street. Safety monitor requested support to assist with the Tesla ADS not proceeding forward. The teleoperator took over vehicle control and gradually increased vehicle speed and turned the Tesla ADS left toward the left side of the street. The Tesla vehicle was driven up the curb and made contact with a metal fence. The safety monitor was present and no passengers were inside the vehicle. On 03/20/2026, while submitting this report and removing confidential or personally identifying information, the report was submitted in error indicating airbag deployment and tow for the subject vehicle. This is in error and the reports were updated to reflect that no airbags were deployed and no tow of the Tesla vehicle was conducted.
cause not established13781-11459TeslaSource file ↗Property damage only2025-07NHTSAWaymoInglewood30270-11372Passenger Car · struck on the rear right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Inglewood 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 July [XXX], 2025 at 3:53 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and slowing for a queue of traffic stopped for a stop sign at the intersection at [XXX]. While the Waymo AV was slowing, 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 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-11372WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11420Bus · struck on the left · stopped
- Crash With
- Bus
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Partly Cloudy
- Investigating Agency
- San Francisco Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 2:54 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was stopped facing east in the third from the right lane on [XXX] for a queue of traffic at the intersection at [XXX]. A bus that was stopped facing east in the fourth from the right lane on [XXX] with an open storage compartment door on the passenger side of the bus that extended into the Waymo AV's lane of travel. The bus proceeded forward as traffic ahead advanced, and the open storage compartment door made contact with the driver side mirror 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 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11420WaymoSource file ↗Not graded by the source2025-07-01FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-30181da 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 IN THE MATERNITY OPERATING ROOM, THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY SLIPPED AND ENDED UP IN THE PATIENT'S INTRAPERITONEAL CAVITY, WHICH THE SURGEON SUBSEQUENTLY REMOVED. THE MCS AND SHEATH WERE REPLACED, BUT THE SECOND MCS TIP COVER ACCESSORY ALSO SLIPPED FROM THE SECOND PAIR, AND IT WAS OBSERVED BY SEVERAL PEOPLE IN THE OPERATING ROOM. UPON VERIFICATION, IT WAS FOUND THAT BOTH SHEATHS HAD THE SAME LOT NUMBER. THE MCS INSTRUMENT DID NOT EXPERIENCE ANY ISSUES DURING USE. THE INCIDENT RESULTED IN PROLONGED SURGERY AND INCREASED STRESS FOR THE SURGEON. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE INSTRUMENT AND TIP COVER WERE INSPECTED BEFORE USE, AND THERE WAS NOTHING UNUSUAL NOTED. THE TIP COVER FELL DURING DISSECTION. IT WAS RETRIEVED USING GRASPING FORCEPS AND IT WAS REMOVED THROUGH THE CANNULA WITHOUT DIFFICULTY. THERE WAS NO COLLISION. THE MCS INSTRUMENT DID NOT EXPERIENCE ANY FUNCTIONALITY ISSUES. THE TIP COVER APPEARED TO BE PROPERLY INSTALLED; A FOUR EYES CHECK HAD BEEN PERFORMED TO VERIFY PROPER INSTALLATION. THE ORANGE SURFACE WAS NOT VISIBLE, AND THE TIP
cause not established2955842-2025-30181Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Property damage only2025-07NHTSAWaymoMiami Beach30270-11472Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 4:17 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami Beach, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the right lane and slowed to a stop for a red light at the intersection with [XXX]. A passenger car traveling directly behind the Waymo AV 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, 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-11472WaymoSource file ↗No injury reported2025-07NHTSANuro, Inc.Mountain View30291-11458Passenger Car · struck on the rear · making left turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 3
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 Wednesday, July [XXX], a Nuro vehicle operating in autonomous mode stopped at sign-controlled intersection, then began to cautiously proceed through the intersection to make a left turn. Just after the Nuro vehicle began to move into the intersection, it was struck from behind by another vehicle.
cause not established30291-11458Nuro, Inc.Source file ↗Minor injury2025-07NHTSAZooxSpring Valley30610-11405Passenger Car · struck on the rear left, left, front left, rear, front, right · making left turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear Left, Left, Front Left, Rear, Front, Right
- SV Precrash Speed (MPH)
- 16
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left, Front, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Las Vegas Police Department
- Make
- TOYOTA
- Model
- Highlander
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling south on [XXX] and initiating a left turn from a dedicated signalized turn lane onto [XXX] in Las Vegas with a flashing yellow. The Zoox vehicle operator disengaged just prior to the signal turning from flashing yellow to green arrow as they continued to execute the left turn. At that time, a passenger car (Vehicle 2) traveling north on [XXX] failed to stop for the red traffic signal and entered the intersection at a high speed, colliding with the passenger side of the Zoox vehicle. The side impact caused the Zoox vehicle to roll onto its driver's side. Both vehicles sustained major damage with airbag deployments. The police and EMS arrived at the scene. The Zoox vehicle operator was transported to a medical facility by an ambulance, and Vehicle 2's driver was reported to have declined medical attention. Both vehicles were towed from the scene.
cause not established30610-11405ZooxSource file ↗Property damage only2025-07NHTSAWaymoWest Hollywood30270-11360Passenger 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)
- 5
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Investigating Agency
- LA County Sheriff's Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July[XXX], 2025 at 7:58 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound in the left lane on [XXX] when it began to slow as it passed a bus that was stopped in the right lane. As the Waymo AV was slowing, a passenger car approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11360WaymoSource file ↗No injury reported2025-07NHTSAMay MobilityAtlanta30413-11489struck on the right · making right turn
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 18
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Sienna
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
While traveling north on [XXX], the Autonomous Vehicle Operator (AVO) engages autonomy 3.0 m before the planned right turn and 7.7 m before the break in the curb while traveling at 8.0 m/s. The May Autonomous Vehicle (ego) was planning to make a tight right turn into a parking lot, which the AVO was unaware of when engaging autonomy. The ego jerked to the right upon entering autonomy, hitting a curb and damaging both passenger-side front and rear tires and the right rear tire rim. The AV attempted the right turn despite not having time to slow sufficiently and mounted the curb. The AVO intervened by accelerating and steering back to the left upon striking the curb, manually maneuvering back to the street while striking a second curb on the opposite side of the parking lot driveway. Resimulations without the manual intervention show the ego slowing appropriately and making the right turn into the parking lot. The AVO should have been attentive to the planned route before engaging autonomy. As a result of this incident, planned improvements to the AVOs instructive dash and audio alerts for upcoming turns have begun to be implemented.
cause not established30413-11489May MobilitySource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11281Bus · 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 July [XXX], 2025 at 10:34 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was parked at the curb on the northeast side of [XXX] facing northwest for a passenger drop-off with its hazard lights activated. As a bus traveling in the adjacent right turn lane on [XXX] passed the Waymo AV, a passenger in the Waymo AV opened the rear driver side door and the rear driver side door made contact with the passenger side of the bus. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passengers in the Waymo AV were not belted at the time of the collision as they were preparing to exit the Waymo AV. 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-11281WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11455SUV · 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
- 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 July [XXX], 2025 at 2:00 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 southeastbound on a narrow portion of [XXX] when it came to a stop at the intersection at [XXX] to yield to an SUV that was traveling northwestbound on [XXX]. While the Waymo AV was stopped, the SUV proceeded to pass the Waymo AV and the left side of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-11455WaymoSource file ↗Not graded by the source2025-06-30FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-30220da 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 THE ARTICLE REPORTED THE FOLLOWING ADVERSE EVENT. ONE PATIENT DEVELOPED A TRACHEAL MICRO-PERFORATION AT BERRY¿S LIGAMENT A WEEK AFTER SURGERY, WHICH WAS SUCCESSFULLY MANAGED WITH COMPRESSION DRESSING AND CONSERVATIVE TREATMENT, ACHIEVING TRACHEAL HEALING WITHOUT INFECTION.
cause not established2955842-2026-30220Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-30FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-31444da 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-31444Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-27FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29791da 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 PRIOR TO THE START - POST ANESTHESIA DA VINCI-ASSISTED RENAL TUMORECTOMY PROCEDURE, THE SURGEON SIDE CONSOLE (SSC) WOULD NOT POWER ON, DESPITE BEING POWERED DURING SYSTEM INSTALLATION. THE PORTS WERE IN PLACE WHEN THE PROBLEM WAS DISCOVERED. VARIOUS TROUBLESHOOTING STEPS WERE TAKEN, INCLUDING CHANGING THE POWER CORD LOCATION MULTIPLE TIMES, TOGGLING THE SSC SWITCH BREAKER, SWAPPING THE POWER CORD LOCATION WITH A KNOWN WORKING ONE, WIGGLING THE POWER CORD, AND ENSURING THE POWER CORD WAS PROPERLY SEATED IN THE CONSOLE. THE CUSTOMER HAD ONLY ONE SSC, AND IT WAS DETERMINED THAT A REPLACEMENT OF THE CONSOLE POWER CORD WAS NOT POSSIBLE BY THE BIOMED OR ELECTRICAL DEPARTMENT. SUBSEQUENTLY, A SALES REPRESENTATIVE CALLED TO REQUEST AN UPDATE, AND IT WAS CONFIRMED THAT ON SITE TROUBLESHOOTING WITH SPARE PART REPLACEMENT WAS NECESSARY TO RESOLVE THE ISSUE. THE PROCEDURE WAS ABORTED POST-ANESTHESIA AND PORT PLACEMENT, AND IT WAS UNKNOWN IF OR WHEN THE PROCEDURE WOULD BE RESCHEDULED.
cause not established2955842-2025-29791Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-27FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-30186da 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 BENIGN HYSTERECTOMY SURGICAL PROCEDURE, A MONOPOLAR CURVED SCISSORS (MCS) TIP COVER FELL OFF WHILE INSTALLED ON AN MCS INSTRUMENT. THE CUSTOMER WAS ABLE TO SAFELY REMOVE THE MCS TIP COVER ACCESSORY FROM THE PATIENT AND PLACED A NEW ONE ON THE MCS INSTRUMENT. THE PROCEDURE WAS COMPLETED ROBOTICALLY. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE SURGEON WAS DOING A HYSTERECTOMY. THE MCS INSTRUMENT AND MCS TIP COVER ACCESSORY WERE INSPECTED AS USUAL. NO DAMAGE WAS NOTED. THE MCS TIP COVER ACCESSORY WAS INSTALLED CORRECTLY WITH NO LUBRICANT USED. THE UTERUS WAS VERY LARGE AND DIFFICULT TO MOVE AROUND. THE PROCEDURE WAS 2.5 HOURS LONGS AND THE MCS INSTRUMENT WAS USED THE ENTIRE CASE. THE ENTIRE MCS TIP COVER ACCESSORY WAS REMOVED WITHOUT DIFFICULTY. NO FRAGMENT WAS NOTED TO BE LEFT IN THE PATIENT. THERE WAS NO ISSUE WITH THE USE OF THE SCISSORS. THE MCS INSTRUMENT AND A TENACULUM FORCEPS INSTRUMENT WERE ON THE SAME SIDE OF THE PATIENT. THE MCS TIP COVER ACCESSORY WAS DISPOSED OF AND THE MCS INSTRUMENT IS STILL IN USE. NO PHOTOS WERE TAKEN.
cause not established2955842-2025-30186Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-27FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-30372da 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, A PORTION OF THE BLACK RUBBER ON THE TROCAR CAPS BREAKING OFF AND FALLING INSIDE OF THE PATIENT. NO FURTHER INFORMATION WAS AVAILABLE.
cause not established2955842-2025-30372Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-27FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29119da 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 PROSTATECTOMY PROCEDURE; WHILE USING THE MONOPOLAR CURVED SCISSORS (MCS) INSTRUMENT, THE PATIENT SUSTAINED A BLADDER BURN. PRIOR TO ACTIVATION, THE MCS TIP COVER ACCESSORY APPEARED TO BE PROPERLY INSTALLED. THE GROUNDING PAD WAS CONFIRMED TO BE CORRECTLY PLACED AND FREE OF DEFECTS. THE ERBE GENERATOR WAS IN USE AT THE TIME, WITH THE COAGULATION MODE SET TO SWIFT: 4. THE INJURY OCCURRED WHILE THE MCS INSTRUMENT WAS ACTIVELY DELIVERING ENERGY FOR DISSECTION OF THE BLADDER NECK. AT THE TIME OF ACTIVATION, THE INSTRUMENT¿S JAWS WERE NEITHER IMMERSED IN FLUID NOR CONTAMINATED WITH CARBONIZED TISSUE OR OTHER BIOLOGICAL DEBRIS. THE MCS TIP COVER ACCESSORY WAS OBSERVED TO HAVE COME INTO CONTACT WITH BLADDER TISSUE, RESULTING IN A THERMAL INJURY. THE BURN WAS ADDRESSED WHILE PERFORMING THE VESICOURETHRAL ANASTOMOSIS. NO ADDITIONAL TISSUE RESECTION WAS REQUIRED, AND THERE WAS NO BLEEDING AS A RESULT OF THE INJURY. AN INTUITIVE SURGICAL, INC. (ISI) TECHNICAL SUPPORT ENGINEER WAS CONSULTED AND SUGGESTED THE POSSIBILITY OF A SHORT CIRCUIT DUE TO COMPROMISED INSULATION. THIS MAY HAVE CAUSED ENERGY TO BE REDIRECTED TO THE INSTRUMENT¿S SHAFT OR MCS T
cause not established2955842-2025-29119Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-27FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-27516da 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-27516Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-27FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-37203da 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, THE HARMONIC ACE INSTRUMENT BROKE. THE BROKEN PART WAS REMOVED AND IT WAS NOTED THAT NO FRAGMENTS REMAINED IN THE PATIENT. HOWEVER, IT IS UNCLEAR IF ANY FRAGMENTS ACTUALLY FELL INSIDE THE PATIENT. THE PROCEDURE WAS COMPLETED ROBOTICALLY USING A BACKUP HARMONIC ACE INSTRUMENT.
cause not established2955842-2025-37203Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-26FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29290da 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 BILATERAL NIPPLE SPARING MASTECTOMY SURGICAL PROCEDURE. INTRA-OPERATIVELY, A SKIN BURN/THERMAL INJURY WAS OBSERVED ON THE LEFT BREAST BY THE CASE SUPPORT ENGINEER. THERE WAS NO REPORTED CAUSE OF THE BURN. THE PHYSICIAN REPORTED THE SEVERITY AS MILD, POSSIBLY RELATED TO THE STUDY DEVICE AND NOT RELATED TO THE RECONSTRUCTION PROCEDURE AND NOT RELATED TO THE PATIENT'S PRE-EXISTING CONDITION. THE TREATMENT WAS REPORTED AS XEROFORM DAILY TO THE BURNS AND THE EVENT OUTCOME IS DOCUMENTED AS ONGOING. THE PATIENT WAS DISCHARGED THE DAY AFTER SURGERY. THERE WERE NO DEVICE MALFUNCTIONS ASSOCIATED WITH THE EVENT.
cause not established2955842-2025-29290Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-25FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-34495da 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 DISTAL PANCREATECTOMY PROCEDURE, THE KNIFE HEAD ON A HARMONIC ACE INSTRUMENT SUDDENLY BROKE. IT WAS REPORTED THAT NO RESIDUE WAS LEFT IN THE PATIENT'S BODY. THE PROCEDURE WAS COMPLETED WITH NO REPORTED INJURY. IT IS UNCLEAR IF A FRAGMENT FELL INSIDE THE PATIENT AND WAS RETRIEVED.
cause not established2955842-2025-34495Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-25FDA MAUDEAccuray3003873069-2025-00001CyberKnife
CyberKnife — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: RECTAL TOXICITY DUE TO PROSTATE TREATMENT.
cause not established3003873069-2025-00001AccurayRead the record ↗Not graded by the source2025-06-25FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00218ExcelsiusGPS
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 ROBOTIC ERROR, AND SCREWS WERE THEN PLACED WITHOUT ROBOT.
cause not established3004142400-2025-00218Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-06-25FDA MAUDEAccuray3003873069-2025-00002CyberKnife
CyberKnife — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: RECTAL TOXICITY DUE TO PROSTATE TREATMENT.
cause not established3003873069-2025-00002AccurayRead the record ↗Not graded by the source2025-06-23FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29783da 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 THYROIDECTOMY PROCEDURE, ONE SIDE OF THE HARMONIC ACE INSTRUMENT JAW BROKE WHILE THE SURGEON WAS DISSECTING AND A FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS SUCCESSFULLY RETRIEVED DURING THE SAME PROCEDURE AND WAS VISUALLY CONFIRMED TO HAVE BEEN FULLY RECOVERED. NO ADDITIONAL SURGICAL PROCEDURE WAS REQUIRED FOR REMOVAL OF THE FRAGMENT AND NO POST-OPERATIVE TESTS WERE CONDUCTED TO CHECK FOR REMAINING FRAGMENTS. THE PROCEDURE WAS COMPLETED ROBOTICALLY USING A BACKUP HARMONIC ACE INSTRUMENT. THE PATIENT HAS NOT RETURNED TO THE HOSPITAL DUE TO ANY POST-SURGICAL COMPLICATIONS.
cause not established2955842-2025-29783Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-20FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-34201da 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 was performed that presented a retrospective review of experiences with robotic lymphadenectomy procedures. The article noted one man was diagnosed with inguinal panniculitis (on the side of radical inguinal lymph node dissection (rILND)), which was managed successfully with a 14-day course of cefditoren.The corresponding author was contacted and stated that the reported postoperative lymphoceles were not caused by, nor attributed to, any Intuitive Surgical device. They represent well-recognized complications following inguinal lymph node dissection. No da Vinci system or instrument malfunctions occurred during any of the procedures reported in the manuscript. Consequently, no corrective actions or interventions related to device malfunction were required. The patients were adult males undergoing robotic inguinal lymphadenectomy for penile cancer. No additional patient-specific information can be provided due to privacy regulations.
cause not established2955842-2026-34201Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-20FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29306da 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 MYOMECTOMY SURGICAL PROCEDURE, THE TIP WAS BENT, AND A PIECE OF THE BLACK PART FELL INSIDE THE PATIENT, BUT THE DOCTOR RETRIEVED IT. THE PROCEDURE WAS COMPLETED.
cause not established2955842-2025-29306Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-20FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-23185da 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 PERIOPERATIVE, ONCOLOGIC, AND FUNCTIONAL OUTCOMES OF SALVAGE TRANSORAL ROBOTIC SURGERY (TORS) WITH SUBMENTAL ISLAND FLAP RECONSTRUCTION FOR RECURRENT OROPHARYNGEAL SQUAMOUS CELL CARCINOMA (OPSCC) WAS PERFORMED. THE RETROSPECTIVE STUDY ANALYZED 8 PATIENTS UNDERGOING SALVAGE TORS WITH SUBMENTAL ISLAND FLAP RECONSTRUCTION BETWEEN DECEMBER 2019 AND FEBRUARY 2024. TWO PATIENTS EXPERIENCED POSTOPERATIVE COMPLICATIONS, INCLUDING NECK HEMATOMA REQUIRING INTERVENTION AND DEHYDRATION/FAILURE TO THRIVE REQUIRING READMISSION. TWO DEATHS WERE OBSERVED DURING LONG-TERM FOLLOW-UP (AT 4 MONTHS AND 27 MONTHS POSTOPERATIVELY), ACKNOWLEDGED BY THE AUTHORS AS PART OF OVERALL SURVIVAL OUTCOMES. NO DEVICE MALFUNCTIONS WERE REPORTED, AND THE AUTHORS DID NOT ATTRIBUTE ANY ADVERSE EVENTS TO AN INTUITIVE SURGICAL, INC. (ISI) DEVICE. FOLLOW-UP WITH THE AUTHOR PROVIDED THE FOLLOWING INFORMATION: "THOSE WERE ANTICIPATED ONCOLOGIC OUTCOMES, INDEPENDENT OF THE ROBOT. THERE WERE NO MALFUNCTIONS."
cause not established2955842-2026-23185Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-20FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-30187da 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-30187Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-20FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-34202da 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 was performed that presented a retrospective review of experiences with robotic lymphadenectomy procedures. The article noted four patients developed clinically evident lymphoceles, with one case requiring temporary percutaneous drainage under local anesthesia due to the risk of cutaneous ulceration.Intuitive Surgical, Inc. (ISI) followed up with the initial reporter and obtained the following additional information: The reported postoperative lymphoceles were not caused by, nor attributed to, any Intuitive Surgical device. They represent well-recognized complications following inguinal lymph node dissection. No da Vinci system or instrument malfunctions occurred during any of the procedures reported in the manuscript. Consequently, no corrective actions or interventions related to device malfunction were required. The patients were adult males undergoing robotic inguinal lymphadenectomy for penile cancer. No additional patient-specific information can be provided due to privacy regulations.
cause not established2955842-2026-34202Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-19FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29702da 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-29702Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-06-19FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29548da 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-29548Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗