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
Not graded by the source2025-07-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-33093da 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 CHOLECYSTECTOMY PROCEDURE, A SMALL PIECE OF A UNIVERSAL SEAL BROKE OFF AND FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED. HOWEVER, IT IS UNCLEAR HOW THE FRAGMENT WAS RETRIEVED AND THE PROCEDURE OUTCOME IS UNKNOWN. THE OR STAFF INDICATED THAT THAT THE UNIVERSAL SEAL HAD LOOKED INTACT. THE FRAGMENT WAS NOT SAVED.
cause not established2955842-2025-33093Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-33620da 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-33620Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-30370da 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 BLADE OF THE HARMONIC ACE INSTRUMENT BROKE WHILE THE SURGEON WAS DISSECTING. A DEVICE FRAGMENT FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME SURGICAL PROCEDURE WHICH WAS COMPLETED ROBOTICALLY WITH A BACKUP HARMONIC ACE INSTRUMENT. THERE WAS A 20 MINUTE PROCEDURE DELAY DUE TO THE REPORTED ISSUE. NO POST-OPERATIVE TESTS, SUCH AS AN X-RAY OR ULTRASOUND, WERE PERFORMED TO CHECK FOR REMAINING FRAGMENTS. FURTHERMORE, THE PATIENT HAS NOT RETURNED TO THE HOSPITAL DUE TO ANY POST-SURGICAL COMPLICATIONS.
cause not established2955842-2025-30370Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-45540da 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, THE MONOPOLAR CURVED SCISSORS MCS (MCS) TIP COVER ACCESSORY CAME OFF THE INSTRUMENT AND FELL INTO A PATIENT. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY WAS NOT INSPECTED PRIOR TO USE. THE MCS TIP COVER ACCESSORY WAS NOT RETRIEVED. THE SURGEON WAS MOVING THE MCS WHEN THE MCS TIP COVER ACCESSORY FELL INSIDE THE PATIENT. THE SURGEON DID NOT NOTICE ANY ISSUES WITH THE FUNCTIONALITY OF THE MCS INSTRUMENT DURING THE PROCEDURE. THE MCS COLLIDED WITH ANOTHER INSTRUMENT DURING THE PROCEDURE. THE MCS TIP COVER ACCESSORY APPEARED TO BE PROPERLY INSTALLED DURING THE PROCEDURE, AND NO ORANGE SURFACE WAS VISIBLE WHEN INSTALLED. THE MCS TIP COVER ACCESSORY WAS NOT INSTALLED BEYOND THE ORANGE SURFACE. THE INSTALLATION TOOL WAS USED. NO ELECTROLUBE OR OTHER LUBRICANT WAS APPLIED TO THE MCS PRIOR TO MCS TIP COVER ACCESSORY INSTALLATION. THERE WAS NO DIFFICULTY IN REMOVING THE MCS AND THE MCS TIP COVER ACCESSORY THROUGH THE CANNULA. THE INSTRUMENT WAS REM
cause not established2955842-2025-45540Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-30375da 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-30375Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07-03FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00268ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THERE WAS A RADIAL ERROR >1.5MM AT ENTRY FOR I' J'AND K'. DEFLECTION VERBALIZED BY CSR DURING DRILLING. J' DRILL BIT WAS RE-DRILL AND REPOSITIONED ONE TIME.
cause not established3004142400-2025-00268Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2025-07-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-31860da 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-31860Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-31450da 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 THAT A NON-RECOVERABLE FAULT OCCURRED. THE CUSTOMER POWER-CYCLED THE SYSTEM MULTIPLE TIMES; HOWEVER, THE ERROR RETURNED. THE CUSTOMER UNDOCKED AND POWER CYCLED THE SYSTEM AGAIN. THE ERROR RETURNED. THE INTUITIVE SURGICAL, INC. (ISI) TECHNICAL SUPPORT ENGINEER (TSE) ASKED THE CALLER TO HARD POWER CYCLE THE SYSTEM AND PERFORM AN EMERGENCY POWER OFF (EPO) OF THE PATIENT SIDE CART (PSC). THE SYSTEM POWERED UP AND AN ERROR AGAINST PATIENT SIDE MANIPULATOR (PSM) #2 WAS PRESENT. THE TSE HAD THE CALLER PERFORM A HARD POWER CYCLE AND PERFORM AN EPO AGAIN, KEEPING THE SYSTEM OFF LONGER. THE ERROR(S) RETURNED. THE TSE ADVISED TO CONTINUE TO PERFORM HARD CYCLES TO SEE IF THE ERROR WOULD CLEAR, AND ALSO ADVISED THAT THE ERRORS COULD RETURN. THE PROCEDURE WAS ULTIMATELY ABORTED AFTER ANESTHESIA HAD BEEN ADMINISTERED TO THE PATIENT AND PORTS HAD BEEN PLACED.
cause not established2955842-2025-31450Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-35767da 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: Intraoperative complications consisted of five vaginal injuries and one small bowel serosa injury requiring simple suturing. Vaginal injuries occurred in three patients in the FR group and two in the SR group (P = 0.7) and were closed in two layers; the mesh was trimmed to avoid the repaired site. The FR group had one grade 3 complication, a small bowel obstruction caused by an adhesion and released by laparotomy.The author responded and reported that there were no complications mentioned in the article that were caused/contributed by an Intuitive product and no da Vinci device malfunctions.
cause not established2955842-2026-35767Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Property damage only2025-07NHTSAWaymoBeverly Hills30270-11404Passenger Car · struck on the rear · parked
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- 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 12:01 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Beverly Hills, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked at the curb facing east on [XXX] after a passenger drop-off when a passenger car that was traveling northbound in an alley behind the Waymo AV made a right turn onto eastbound [XXX]. As the passenger car was completing its turn, the passenger side 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. 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-11404WaymoSource file ↗Property damage only2025-07NHTSAWaymoInglewood30270-11374Passenger Car · struck on the front right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- 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 2:11 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 northbound on [XXX] and proceeding straight at a green light at the intersection with [XXX]. As the Waymo AV began to enter the intersection, a passenger car that was traveling eastbound in the second to the right lane on [XXX] entered the intersection against a red light and crossed perpendicularly into the Waymo AV's lane of travel. The Waymo AV stopped to yield to the passenger car, and the passenger side of the passenger car 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-11374WaymoSource file ↗Minor injury2025-07NHTSAWaymoInglewood30270-11273Heavy Truck · struck on the front · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Parking Maneuver
- CP Contact Area
- Rear Left
- 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 4:19 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped at the curb facing north on [XXX] for a passenger pick-up. A heavy truck traveling northbound on [XXX] passed the Waymo AV, and partially turned left towards southwestbound [XXX] in order to position the heavy truck for reversing into a parking location. As the heavy truck turned left, the rear passenger side of the heavy truck made contact with the front driver side of the stationary Waymo AV. After this contact, the heavy truck maneuvered forward towards southwestbound [XXX], then reversed again, maneuvering behind the stationary Waymo AV, and the rear of the heavy truck made contact with a utility pole located on the east side of [XXX]. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV and the utility pole sustained damage. The passenger in the Waymo AV reported a minor injury. 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-11273WaymoSource file ↗Minor injury2025-07NHTSAWaymoSan Francisco30270-11280Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- 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
- 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 9:35 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 southwestbound on [XXX] and stopped in the right lane for a red traffic light at the intersection with [XXX]. The traffic light then turned green and the Waymo AV proceeded a short distance before stopping again to yield to an oncoming active emergency vehicle. A passenger car traveling behind the Waymo AV also proceeded from the green light and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The rider of the Waymo AV alleged a minor injury. 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-11280WaymoSource file ↗Property damage only2025-07NHTSAWaymoAustin30270-11451Heavy Truck · struck on the front left · proceeding straight
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 3
- CP Pre-Crash Movement
- Parking Maneuver
- 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 11:08 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in the left lane. A heavy truck that was stopped facing west in the right lane began to reverse into an alley on the north side of [XXX], and then came to a stop with its front left positioned partially within the left lane of [XXX]. The Waymo AV was proceeding in the left lane and maneuvered towards the left side within the left lane. The heavy truck then proceeded forward and further into the left lane, and the front left side of the heavy truck made contact with the front right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11451WaymoSource file ↗Property damage only2025-07NHTSAWaymoLos Angeles30270-11467struck 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 July [XXX], 2025 at 4:11 AM PT a Waymo Autonomous Vehicle ("Waymo AV:) operating in Los Angeles, California was in a collision involving a barrier arm at the entrance of a parking lot at [XXX]. The Waymo AV was traveling westbound at the southeastern entrance to a parking lot at [XXX] and came to a stop for a closed barrier arm. The Waymo AV proceeded forward at a low speed and the front of the Waymo AV made contact with the closed barrier arm. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and barrier arm 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-11467WaymoSource file ↗Property damage only2025-07NHTSAWaymoAustin30270-11330Pickup Truck · struck on the rear · parked
- Crash With
- Pickup 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
- 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 July [XXX], 2025 at 1:42 AM 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 parked in-lane facing northeast on [XXX] with hazards activated for a passenger drop off. While the Waymo AV remained parked, a pickup truck that had been parked at the curb approached the Waymo AV from behind, and proceeded to pass to the left of the Waymo AV. As the pickup truck passed the Waymo AV, the passenger side of the pickup 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-11330WaymoSource file ↗Property damage only2025-07NHTSAWaymoLos Angeles30270-11282Bus · 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
- 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 July [XXX], 2025 at 2:40 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was stopped in the right turn lane facing northwest on [XXX] at the intersection with [XXX], yielding to pedestrians standing inside of the crosswalk while waiting to cross. A bus traveling northwestbound on [XXX] passed the Waymo AV and the passenger side of the bus made contact with the 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 passengers seated in the rear of the Waymo AV were not belted at the time of the collision. 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-11282WaymoSource file ↗Property damage only2025-07NHTSAWaymoPhoenix30270-11432Heavy Truck · struck on the left · making right turn
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 3
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- 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 10:25 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was stopped facing north at the exit of a parking lot at [XXX]. At the same time, a semi tractor-trailer was incorrectly stopped to the left of the Waymo AV in the entrance lane of the parking lot driveway. The Waymo AV waited for a pedestrian to finish crossing the driveway before initiating a right turn onto eastbound [XXX]. As the Waymo AV proceeded forward into the turn, the semi tractor-trailer initiated a right turn onto eastbound [XXX] from the entrance lane of the parking lot driveway. The right side of the trailer then made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11432WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11279Passenger Car · struck on the rear left · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front 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 July [XXX], 2025 at 6:03 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 southeastbound on [XXX] in the second to the right lane when it slowed to yield to a taxicab in the rightmost dedicated transit lane attempting to merge into the Waymo AV's lane of travel. A passenger car traveling behind the Waymo AV approached the Waymo AV from behind, 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. 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-11279WaymoSource file ↗Minor injury2025-07NHTSAWaymoAustin30270-11328Heavy Truck · struck on the rear right · stopped
- Crash With
- Heavy Truck
- 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
- 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:54 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was stopped facing west in the right lane on [XXX] for a red light at the intersection at [XXX]. When the traffic light turned green, the Waymo AV proceeded a short distance into the intersection, activated its left turn signal, and slowed to a stop. A box truck that was initially stopped directly behind the Waymo AV proceeded forward and the front of the box 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. 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-11328WaymoSource file ↗Not graded by the source2025-07-01FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-30182da 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-30182Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07-01FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-29458da 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 HYSTERECTOMY SURGICAL PROCEDURE, THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY CAME OFF THE MCS INSTRUMENT INTRAOPERATIVELY. DURING THE EXCHANGE BETWEEN 2 INSTRUMENTS ON ARM #3, THE CUSTOMER NOTICED THAT THE MCS TIP COVER ACCESSORY WAS MISSING FROM THE MCS INSTRUMENT. THE CUSTOMER FOUND THE MCS TIP COVER ACCESSORY STUCK IN THE PERITONEAL WALL. LONGER ANESTHESIA TIME AND WIDENING OF THE INCISION WERE REQUIRED TO FIND/REMOVE THE MCS TIP COVER ACCESSORY.
cause not established2955842-2025-29458Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-07NHTSAWaymoMesa30270-11361struck on the front right · proceeding straight
- Crash With
- Other, see Narrative
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 4
- 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 July [XXX], 2025 at 6:20 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was in a collision involving a detached object from a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling northbound in the left turn lane on [XXX] and slowing for a queue of traffic at the intersection with [XXX]. A pickup truck was traveling southbound in the leftmost lane on the west side of [XXX] without its rear driver side tire. As the SUV continued to proceed straight, an object detached from the pickup truck's rear axle and rolled into the Waymo AV's lane of travel, making 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. The passenger in the Waymo AV later alleged an injury of unspecified nature and severity. 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-11361WaymoSource file ↗No injury reported2025-07NHTSAZooxWinchester30610-11513Non-Motorist: Cyclist · struck on the rear left · making right turn
- Crash With
- Non-Motorist: Cyclist
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Other, see Narrative
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- None
- Make
- ZOOX
- Model
- Zoox
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
An unoccupied Zoox vehicle in autonomous mode was traveling in the right turn lane on southbound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. At that time, an e-cyclist was traveling south on the sidewalk adjacent to southbound [XXX]. As the Zoox vehicle slowed to execute its turn, the e-cyclist rapidly approached the crosswalk in the path ahead of the Zoox vehicle. The Zoox vehicle braked to yield to the approaching e-cyclist. The e-cyclist then veered left and accelerated into the roadway, making contact with the right rear side of the nearly stopped Zoox vehicle. The e-cyclist fell to the ground behind the Zoox vehicle. The Zoox vehicle then started to move and completed the right turn onto [XXX] and completed its mission. The cyclist appears to have ridden away from the scene. A bystander reported the event to Zoox. There was minor damage to the Zoox vehicle, and information was not exchanged with the e-cyclist. The police were later notified.
cause not established30610-11513ZooxSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11468SUV · 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
- 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:04 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] when it slowed to a stop for a stop sign at the intersection at [XXX]. While the Waymo AV was stopped, 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 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-11468WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11362Passenger Car · struck on the front right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- 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 6:36 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the left lane on [XXX] and came to a stop in a queue of traffic for a red light at the intersection with [XXX]. When the light turned green, a passenger car that was stopped directly in front of the Waymo AV reversed, and the rear of the passenger car made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11362WaymoSource file ↗Property damage only2025-07NHTSAWaymoTempe30270-11426struck on the front · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 5
- 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 July [XXX], 2025 at 11:40 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a line of shopping carts in a parking lot at [XXX]. The Waymo was parked at the curb facing south in a parking lot at [XXX] for a passenger pick-up. The AV completed its pick-up and began moving forward as a pedestrian pushing a line of shopping carts towards the curb approached the AV from the left. As the Waymo AV began moving forward, the pedestrian continued pushing the shopping carts forward and the front left of the Waymo AV made contact with the shopping carts. 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 was not belted at the time of the collision, having just entered the vehicle. 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-11426WaymoSource file ↗Property damage only2025-07NHTSAWaymoAustin30270-11371Passenger Car · struck on the rear right · making right turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 12:07 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 southwest on [XXX] in a queue of traffic for a red light at the intersection of [XXX] with its right turn signal activated in preparation to make a right turn onto northwestbound [XXX]. As traffic ahead advanced, the Waymo AV initially proceeded forward and then began to slow down to yield to a pedestrian that was crossing [XXX] within the marked crosswalk. 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. 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-11371WaymoSource file ↗Property damage only2025-07NHTSAWaymoWest Hollywood30270-11344Bus · struck on the rear · parked
- Crash With
- Bus
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- 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:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was parked at the curb facing west on [XXX] for a passenger drop-off with its hazard lights activated. While the Waymo AV remained parked, a bus traveling in the adjacent lane on [XXX] passed the Waymo AV on the left and the passenger side of the bus 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 passenger in the Waymo AV was not belted at the time of the collision, as they were preparing to exit the Waymo AV. 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-11344WaymoSource file ↗Property damage only2025-07NHTSAWaymoAtlanta30270-11383Passenger Car · struck on the front · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 23
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- 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 10:07 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane. A passenger car, which was traveling behind an SUV heading northbound on [XXX] that had stopped in the second to the right lane, braked and maneuvered into the Waymo AV's lane of travel (the rightmost lane). 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 engaged in autonomous mode. Both the passenger car and 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-11383WaymoSource file ↗Property damage only2025-07NHTSAWaymoMesa30270-11334struck on the bottom · making u-turn
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making U-Turn
- SV Contact Area
- Bottom
- SV Precrash Speed (MPH)
- 4
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Rain
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 11:11 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona made contact with the raised pavement of a median on [XXX] near [XXX]. The Waymo AV was stopped facing east in the rightmost lane at an active railroad crossing on [XXX], where the train appeared to be stopped on the tracks. While the railroad gate remained down, the Waymo AV initiated a U-turn onto westbound [XXX] and proceeded across the second from the right and the leftmost lane of eastbound [XXX]. As the Waymo AV was completing its U-turn, the undercarriage of the Waymo AV made contact with the concrete median between eastbound and westbound [XXX]. 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-11334WaymoSource file ↗Minor injury2025-07NHTSATeslaAustin13781-11375SUV · struck on the rear right · making right turn
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Partly Cloudy
- 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 in the right turn only slip lane with a yield sign yielding for cross traffic from the left. The ADS was stopped then creeped forward up to 2MPH while continuing to yield for cross traffic and was rear-ended by an SUV behind the ADS. The ADS had a safety monitor present with no passengers in the vehicle. On 07/29 Tesla received notice that the safety monitor reported a minor complaint of pain and later sought medical evaluation.
cause not established13781-11375TeslaSource file ↗Property damage only2025-07NHTSATeslaAustin13781-11507SUV · 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
- Partly Cloudy
- 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 at a red light at an intersection. An SUV that had been stopped behind the ADS crept forward and rear ended the ADS. Safety monitor was present and no passengers were inside the vehicle.
cause not established13781-11507TeslaSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11428SUV · 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 July [XXX], 2025 at 10:45 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 northwest in the second from the left lane on [XXX] for a red light at the intersection at [XXX]. When the light turned green, the Waymo AV began to move forward momentarily and then stopped to yield to an active emergency vehicle traveling southwestbound on [XXX] with emergency lights activated. While the Waymo AV was stopped, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 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-11428WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11329Bus · struck on the rear · parked
- Crash With
- Bus
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- 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 6:47 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was parked in-lane for a passenger pick-up facing south on [XXX] with its hazard lights activated. A bus traveling southbound on [XXX] began to maneuver around the stationary Waymo AV by crossing the yellow center line, entering the opposing lane of travel. As the bus proceeded to the left of the stationary Waymo AV, the right side of the bus made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11329WaymoSource file ↗Minor injury2025-07NHTSAWaymoTempe30270-11323Passenger Car · struck on the rear right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 16
- 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 2:51 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound in the right lane on [XXX], slowing for a queue of traffic near the intersection of [XXX]. A passenger car traveling southbound in the right lane on [XXX] approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The rider of the Waymo AV alleged a minor injury. 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-11323WaymoSource file ↗Property damage only2025-07NHTSAWaymoLos Angeles30270-11401SUV · 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 July [XXX], 2025 at 4:49 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX], The Waymo AV was traveling northwestbound on [XXX] and came to a stop for a stop sign 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. 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-11401WaymoSource file ↗Property damage only2025-07NHTSAWaymoSanta Monica30270-11418SUV · struck on the front right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- 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.
July [XXX], 2025 at 9:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on [XXX] and made a left turn onto [XXX]. After completing its turn, the Waymo AV came to a stop, yielding to an SUV stopped in-lane. The SUV began reversing and the rear of the SUV made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11418WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11358First Responder Vehicle · struck on the rear · stopped
- Crash With
- First Responder Vehicle
- 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 July [XXX], 2025 at 11:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fire truck vehicle on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] with vehicles parked on both sides when it came to a stop to yield to a fire truck, which did not have lights or sirens activated, traveling southbound on [XXX]. As the fire truck passed the stationary Waymo AV, the driver side of the fire 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 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-11358WaymoSource file ↗Minor injury2025-07NHTSAWaymoLos Angeles30270-11327Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- 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
- Intersection
- Weather
- Clear
- Investigating Agency
- Los Angeles Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
Other than an update to the highest severity injury alleged field to reflect a minor injury, the content of this report is unchanged from the initial report submitted on July 18, 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2025 at 1:05 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling southbound on [XXX] and came to a stop for a red traffic light at the intersection at [XXX]. A passenger car approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11327WaymoSource file ↗Property damage only2025-07NHTSAWaymoScottsdale30270-11381Passenger Car · struck on the rear · 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
- SV Precrash Speed (MPH)
- 22
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Scottsdale 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:12 AM 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 facing north in the second from the right lane on [XXX] for a red light at the intersection at [XXX]. When the light turned green, the Waymo AV proceeded straight, and a passenger car that was facing south in the left turn lane on [XXX] proceeded to make an unprotected left turn onto eastbound [XXX]. As the passenger car crossed into the Waymo AV's lane of travel, the Waymo maneuvered to the right and the front driver side 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. 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-11381WaymoSource file ↗Property damage only2025-07NHTSAWaymoTempe30270-11379struck on the front right, bottom · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right, Bottom
- SV Precrash Speed (MPH)
- 7
- 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 12:16 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a small piece of concrete at a parking lot at [XXX]. The Waymo AV was stopped facing north at the entrance of a parking lot at [XXX] for a passenger drop-off. After the passengers had exited, the Waymo AV traveled northbound to enter the parking lot and the front and undercarriage of the Waymo AV made contact with a small piece of concrete on the pavement in the center of the driveway and attached to a chain at the entrance 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-11379WaymoSource file ↗Property damage only2025-07NHTSAWaymoTempe30270-11412Passenger Car · struck on the left · stopped
- Crash With
- Passenger Car
- 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
- Crossing into Opposing Lane
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Tempe Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 11:39 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] and slowing to a stop in response to a passenger car that was traveling westbound on [XXX] and turning right onto northbound [XXX]. As the passenger car was completing its turn, it crossed the center line into the Waymo AV's lane of travel and the driver side of the passenger car made contact with the 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-11412WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11402Passenger 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 12:07 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 west in the left turn lane of [XXX] for a red left arrow light at the intersection at [XXX] with its left turn signal activated. While the left turn light remained red, a passenger car 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-11402WaymoSource file ↗No injury reported2025-07NHTSAMay MobilityPeachtree Corners30413-11487Passenger Car · struck on the front · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 20
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Gwinnett County Police Department
- Make
- TOYOTA
- Model
- Sienna
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
The May autonomous vehicle was travelling in an autonomous vehicle (AV) only lane, on [XXX], approaching the intersection at [XXX] A vehicle travelling to the left of the May shuttle in the non-AV lane attempted to perform a right hand turn across the May vehicles path and collided with the May AV. The primary factor that led to this collision was human error on the part of the other vehicle that was required to yield to through traffic in the AV lane but did not. Right turns across a straight lane are uncommon, and drivers are typically not used to them, however there is a metal street sign that instructs other traffic to yield to the vehicles in the AV lane. There were no autonomy faults or errors which led to this incident. Additionally, there is a second traffic light at this intersection that warns public drivers to yield to the AV shuttle. This light was not operating as it should during this incident. We are working with our partner to maintain the operation of this light and have implemented a mitigation policy of daily inspections of this light and implementing an AVO in service if this light is not functioning.
cause not established30413-11487May MobilitySource file ↗Minor injury2025-07NHTSAWaymoSan Francisco30270-11452Non-Motorist: Scooter - Skateboard · struck on the right · stopped
- Crash With
- Non-Motorist: Scooter - Skateboard
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- 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 [XXX] at 10:31 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a scooterist on [XXX] at [XXX]. The Waymo AV was stopped at the curb facing north on [XXX] for a passenger drop-off when the passenger in the Waymo AV opened the rear right door. As the rear right door was being opened by the passenger, a scooterist that was traveling northbound in the rightmost lane on [XXX] proceeded to pass to the right of the Waymo AV. The left handlebar of the scooter made contact with the open rear right door of the stationary Waymo AV, and the scooterist remained standing after the impact. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The scooterist alleged a minor injury and that the scooter sustained damage. The passenger in the Waymo AV was not belted at the time of the collision, as the passenger was 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-11452WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11400Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 9:18 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 traveling southwestbound in the left lane on [XXX] when it slowed to a stop in a queue of traffic ahead. While the Waymo AV was stopped, a passenger car 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. 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-11400WaymoSource file ↗Property damage only2025-07NHTSAWaymoSan Francisco30270-11333Bus · struck on the rear · stopped
- Crash With
- Bus
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Rear
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July[XXX], 2025 at 11:55 AM 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 stopped facing north on a narrow portion of [XXX] for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, a bus that was traveling westbound on [XXX] made a left turn onto southbound [XXX]. As the bus proceeded to pass by the stationary Waymo AV and complete its turn, the rear driver side of the bus 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. 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-11333WaymoSource file ↗Not graded by the source2025-07-01FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-35101da 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: During a Robot-assisted Partial Nephrectomy (RAPN) surgery, the patient experienced an accidental massive hemorrhage and hypotension due to sudden iatrogenic rupture of the IVC. The procedure was converted to open nephrectomy. The patient was transferred to the Intensive Care Unit on Synchronized Intermittent Mandatory Ventilation (SIMV) ventilator mode.The patient remained hemodynamically stable and was extubated and subsequently discharged from the hospital on postoperative day 7.Intuitive Surgical Inc. (ISI) has made multiple attempts to obtain additional information; however, as of the date of this report, no new information has been obtained.
cause not established2955842-2026-35101Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Property damage only2025-07NHTSAWaymoPhoenix30270-11424SUV · struck on the front · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On July [XXX], 2025 at 1:27 PM MT two Waymo Autonomous Vehicles ("Waymo AV") operating in Phoenix, Arizona were involved in a collision in the West Parking Lot off of [XXX] at the [XXX]. The Waymo AV was parked facing north in a parking stall in the West Parking Lot off of [XXX]. The Waymo AV proceeded to reverse to exit the parking stall, and came to a stop, preparing to maneuver forward and to the left. While the Waymo AV was stopped, a second Waymo AV ([XXX]) that was parked in the left adjacent parking stall proceeded to reverse to exit its parking stall. While the second Waymo AV was reversing, the initial Waymo AV proceeded forward and the front left of the Waymo AV made contact with the right side of the second Waymo AV. At the time of the impact, both Waymo AV's Level 4 ADS were 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-11424WaymoSource file ↗