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-10-15FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-00437da 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 SHEATH OF THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY FELL INTO A PATIENT AND THE ACCESSORY WAS RETRIEVED DURING THE SAME PROCEDURE. THE PROCEDURE WAS COMPLETED. AN UNSPECIFIED POST-OPERATIVE TEST WAS PERFORMED. THERE WERE NO CLINICAL CONSEQUENCES FOR THE PATIENT; THE SHEATH WAS REMOVED BEFORE THE PATIENT WAS SUTURED. THE TEAM NOTICED THAT THE SHEATH HAD REMAINED INSIDE THE PATIENT AND REMOVED IT BEFORE SUTURING. IT WAS NOTED THAT THIS INCIDENT OCCURRED AT LEAST TWICE, WITHOUT CONSEQUENCE FOR THE PATIENT BECAUSE THE SHEATH WAS SEEN AND REMOVED EACH TIME. HOWEVER, IT WAS NOTED THAT THIS WOULD PRESENT A RISK TO THE PATIENT IF THE TEAM DID NOT NOTICE IT BEFORE SUTURING.
cause not established2955842-2026-00437Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-14FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-03135da 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-2026-03135Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-14FDA MAUDEStryker3005985723-2025-00518Mako Robotic-Arm
Mako Robotic-Arm — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: DEEP LATERAL ANTERIOR CUT RELATIVE THE IMPLANT, OTHER CUTS FLUSH. GRAFTING REQUIRED UNDER THE CUT. ADDITIONAL INFORMATION RECEIVED ON 14/10/25: THERE WAS A GAP BETWEEN THE IMPLANT AND THE CUT THAT THE SURGEON SAID WAS 5MM. HOWEVER, IN THE PICTURE IT LOOKS SLIGHTLY LESS. THERE HAS NOT BEEN ANY IMPACT OR ADVERSE CONSEQUENCES REPORTED SINCE AS A RESULT OF THIS EVENT EXCEPT FOR THE REQUIRED GRAFTS AS MENTIONED.
cause not established3005985723-2025-00518StrykerRead the record ↗Not graded by the source2025-10-13FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-43842da 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-43842Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-08FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-45544da 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-45544Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-07FDA MAUDEStryker3005985723-2025-00499Mako Robotic-Arm
Mako Robotic-Arm — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: NO NEW INFORMATION.
cause not established3005985723-2025-00499StrykerRead the record ↗Not graded by the source2025-10-03FDA MAUDEMedtronic plc — Surgical Robotics3005075696-2025-00383Mazor X
Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MEDTRONIC RECEIVED INFORMATION REGARDING A GUIDANCE SYSTEM. IT WAS REPORTED THAT A CT REVEALED FORAMINAL STENOSIS DUE TO A FRACTURE OF THE PATIENT'S SUPERIOR ARTICULAR PROCESS POST-OPERATIVELY. ADDITIONALLY, THE PATIENT HAS INCREASED LEFT LEG PAIN. IT WAS NOTED THE GUIDANCE ROBOT WAS USED FOR THE DECORTICATION OF THE BONE. THE PROCEDURE PERFORMED WAS A INTERBODY FUSION FROM LEVELS L5-S1. ADDITIONAL SURGERY WAS PERFORMED THE DAY AFTER TO ADDRESS THE ADVERSE EVENT. ADDITIONAL INFORMATION RECEIVED FROM A MANUFACTURER REPRESENTATIVE REPORTED THE GUIDANCE SYSTEM WAS INVOLVED IN AN ABNORMAL DECORTICATION. THE SYSTEM WAS USED TO DECORTICATE AND CANNULATE THE PEDICLE. AN APPROPRIATE SIZED SCREW WAS PLACED. POST-OP, THE PATIENT INDICATED THAT THEY HAD EXTREME PAIN. THE FRACTURED PROCESS HAD BEEN CANNULATED BY THE GUIDANCE SYSTEM.
cause not established3005075696-2025-00383Medtronic plc — Surgical RoboticsRead the record ↗Not graded by the source2025-10-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-43221da 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 PIECE OF A UNIVERSAL SEAL POPPED OFF MID-PROCEDURE AND FELL INTO THE PATIENT. IT WAS CAUGHT AND REMOVED FROM THE ABDOMEN. THE CUSTOMER NOTED THAT THE LOT NUMBER WAS UNKNOWN DUE TO THE SEAL HAVING BEEN DISCARDED.
cause not established2955842-2025-43221Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-45543da 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-45543Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-42597da 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 DA VINCI-ASSISTED SURGICAL PROCEDURE, THE HARMONIC ACE INSTRUMENT WAS FOUND TO HAVE AN ISSUE WITH THE BLADE. A BACKUP INSTRUMENT WAS USED AND THE PROCEDURE WAS COMPLETED. AN UNSPECIFIED POST-OPERATIVE TEST WAS REPORTEDLY PERFORMED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE NURSE STATED THAT DURING A PROCEDURE USING THE HARMONIC ACE, THE BLADE BROKE AT THE TIP AND WAS COMPLETELY DETACHED FROM THE INSTRUMENT. THE BROKEN FRAGMENTS DROPPED INTO THE PATIENT¿S BODY BUT WERE ALL RETRIEVED WITHOUT RESIDUAL FOREIGN BODIES.
cause not established2955842-2025-42597Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-02FDA MAUDEMedtronic plc — Surgical Robotics3005075696-2025-00368Mazor X
Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MEDTRONIC RECEIVED INFORMATION REGARDING A GUIDANCE SYSTEM BEING USED DURING A SPINAL PROCEDURE. IT WAS REPORTED THAT THERE WAS AN ALLEGED INACCURACY. IT WAS STATED THAT DURING NAVIGATION, THE TRAJECTORIES APPEARED TO BE ACCURATE, BUT AFTER PLACING T4 SCREW ON THE RIGHT SIDE, THE SURGEON WAS NOTIFIED BY NEURO-MONITORING TEAM THAT THEY HAD LOST READINGS OF THE PATIENT'S RIGHT LEG. AFTER TAKING AN IMAGE TO CONFIRM SCREW PLACEMENT, THE SCREW APPEARED TO BE PLACED MEDIALLY BY AN UNKNOWN AMOUNT OF UNITS. THEY TOOK OUT THIS SCREW AND ABANDONED USE OF THE ROBOT AND CLOSED THE PATIENT. THEY RE-PLACED THIS SCREW USING THE MEDTRONIC NAVIGATION SYSTEM DURING A FOLLOW UP SURGERY ON (B)(6) 2025. THE PATIENT WAS BEING MONITORED FOR PARALYSIS ON THE RIGHT LEG. SURGICAL DELAY WAS NOTED AS 5-10 MINUTES. ADDITIONAL INFORMATION RECEIVED FROM A MANUFACTURER REPRESENTATIVE REPORTED THAT THE SITE REGISTERED ONCE, BUT THE C-ARM BUMPED THE ROBOT ON THE WAY OUT, SO THEY HAD TO REGISTER A SECOND TIME. IT WAS ALSO NOTED THAT THE PLANNED TRAJECTORY AT T4 ON THE RIGHT, WAS ORIGINALLY WITHIN THE PREFERRED PARAMETERS FOR AN OPEN CASE, HOWEVER, UPON DRILLING AT THE ORIGINAL TRAJECTORY THE DOCTOR FELT THEY WERE TO
cause not established3005075696-2025-00368Medtronic plc — Surgical RoboticsRead the record ↗Not graded by the source2025-10-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-44013da Vinci Surgical System
da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED SURGICAL PROCEDURE, MONOPOLAR CURVED SCISSORS (MCS) TIP COVER FELL INTO PATIENT INTRA-ABDOMINALLY ON (B)(6) 2025. LAPAROSCOPY AND EXPLORATION LAPAROTOMY DID NOT FIND THE FOREIGN BODY. THE COMPUTED TOMOGRAPHY (CT) SCAN WAS PERFORMED THE NEXT DAY CONFIRMED AN INTRA-ABDOMINAL FOREIGN BODY. REPEAT SURGERY WAS SCHEDULED FOR (B)(6) 2025 FOR REMOVAL OF THE FOREIGN BODY BUT WAS PERFORMED ON (B)(6) 2025. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE INSTRUMENT WAS CHECKED BY THE NURSE PRIOR TO USE, BUT NOT BY THE SURGEON. DURING INSTRUMENT REMOVAL, THE NURSE OBSERVED THE MCS TIP COVER ACCESSORY SLIPPING. IT WAS REMOVED AND INSPECTED FOR PROPER PLACEMENT, THEN REATTACHED. HOWEVER, ONCE INSIDE THE ABDOMEN, THE COVER BEGAN TO SLIP AGAIN, DEVELOPED A VISIBLE CRACK, AND ULTIMATELY FELL INTO THE ABDOMEN DURING WITHDRAWAL. THE SURGEON SUSPECTS THE CAUSE WAS ¿SNAGGING¿ OF THE PROTECTIVE SHEATH AT THE INTERNAL ORIFICE OF THE TROCAR. THE EXACT DURATION OF MCS USE WAS DIFFICULT TO ESTIMATE, BUT THREE TIP COVERS WERE REQUIRED, AS TWO CRACKED¿ONLY ONE
cause not established2955842-2025-44013Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-02FDA MAUDEAuris HealthMonarch Platform3014447948-2025-00029Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN ENCOUNTERED SYSTEM FAULT MESSAGES AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2025-00029Auris HealthMonarch PlatformRead the record ↗Not graded by the source2025-10-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2025-43024da 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-43024Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2025-10-02FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2025-00252ExcelsiusGPS
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 A PATIENT IS SUFFERING PARAPLEGIA POST EGPS SURGERY. THE SURGEON IMPLIED HE FELT EGPS INSTRUMENTATION MAY HAVE CONTRIBUTED TO THE OUTCOME. SEPARATE CASE SUMMARY SUBMITTED DETAILING OBSERVED SURGICAL EVENTS. FROM INITIAL INFORMATION GATHERING WE HAVE BEEN INFORMED THAT THERE APPEARS TO BE HEMATOMA AND BONE FRAGMENTS IN THE CANAL SPACE AT AROUND THE T9 ANATOMICAL AREA. FROM CONVERSATIONS WITH THE CLINICIAN'S SURGICAL IMPLANTATION FROM THE PROCEDURE APPEARS TO BE CORRECTLY POSITIONED AND IMPLANT ACCURACY APPEARS TO NOT BE IN QUESTION. INITIAL REPORTING FROM THE SURGEON USER APPEARED TO INDICATE HE FELT THAT THE HIGH-SPEED DRILL OR THE PILOT DRILL COULD HAVE MOVED BONE FRAGMENTS INTO THE CANAL AT THIS AREA. IT IS UNCLEAR WHETHER THERE IS ANY EVIDENCE OF INSTRUMENTATION BREACH E.G. CLEARLY DEFINED INSTRUMENT TRACKS, INTO THE CANAL, HOWEVER THE SUGGESTION APPEARED TO BE THE SURGEON FELT THAT THESE INSTRUMENTS MAY HAVE MECHANICALLY DISLODGED THE BONY ANATOMY AND HAD A CAUSATIVE EFFECT.
cause not established3004142400-2025-00252Globus MedicalExcelsiusGPSRead the record ↗Property damage only2025-10NHTSAWaymoPhoenix30270-11929Passenger 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 October [XXX], 2025 at 7:48 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing north in the rightmost lane on [XXX] in a queue of traffic for a red light at the intersection at [XXX]. A passenger car traveling northbound in the rightmost lane on [XXX] slowed to a stop directly behind the Waymo AV. After the traffic light turned green and traffic ahead advanced, the Waymo AV proceeded a short distance and came to a stop before entering the intersection, as it detected a siren from an emergency vehicle. The passenger car also proceeded forward initially and then came to a stop to yield to the Waymo AV. While the Waymo AV and the passenger car remained stopped, a second passenger car traveling northbound on [XXX] approached the first passenger car from behind and the front of the second passenger car made contact with the rear of the first passenger car. The front of the first passenger car then made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV, the first passenger car, and the second passenger car 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-11929WaymoSource file ↗Property damage only2025-10NHTSAWaymoAustin30270-11954Bus · 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
- Changing Lanes
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 2:45 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was traveling northwestbound on [XXX] in the right lane with its right turn signal activated when it slowed to a stop in-lane for a passenger drop-off with hazard lights activated. A bus that was traveling behind the Waymo AV in the right lane proceeded to change lanes to the left lane and the right side of the bus made contact with the left rear side of the stationary Waymo AV. The passenger in the Waymo AV was not belted at the time of the collision, as they were preparing to exit 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-11954WaymoSource file ↗Not graded by the source2025-10NHTSAWaymoLos Angeles30270-11849SUV · struck on the rear · parked
- Crash With
- SUV
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Los Angeles Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
Other than an update to the highest severity injury alleged field to reflect an unknown injury level, the content of this report is unchanged from the initial report submitted on October [XXX], 2025 [Report ID # 30270-11849-1]. On October [XXX], 2025 at 10:16 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was parked at the curb facing north on [XXX] for a passenger drop-off with hazard lights activated. An SUV traveling northbound on [XXX] maneuvered towards the parked Waymo AV. As the SUV approached the Waymo AV from behind, the front of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo later received notice of alleged unknown injuries from the passengers in the Waymo AV. 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-11849WaymoSource file ↗Property damage only2025-10NHTSAWaymoPhoenix30270-11905Heavy Truck · struck on the front · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- 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
- 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 October [XXX], 2025 at 6:56 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling east in a parking lot located at [XXX] when it approached a stopped heavy truck and trailer that was positioned facing north in the left-hand side of the parking lot exit lane. The Waymo AV made a left turn in the parking lot and came to a stop facing north alongside the heavy truck in the right-hand side of the parking lot exit lane when 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 made contact with the front left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11905WaymoSource file ↗Property damage only2025-10NHTSAWaymoPhoenix30270-11994SUV · struck on the left · parked
- Crash With
- SUV
- 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
- Passing
- 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 October [XXX], 2025 at 12:17 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV in a parking lot at [XXX]. The Waymo AV was stopped facing north in a parking lot at [XXX] for a passenger drop-off with its hazard lights activated. An SUV was traveling eastbound on [XXX], made a left turn into the parking lot and proceeded to pass the Waymo AV on the left. While the SUV was passing the Waymo AV, a passenger in the Waymo AV opened the rear left door and the open rear left door of the stationary Waymo AV made contact with the right side of the SUV. 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. 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-11994WaymoSource file ↗Property damage only2025-10NHTSAWaymoLos Angeles30270-11952Passenger Car · struck on the rear right · backing
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Backing
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- ZEEKR
- Model
- RT
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 October [XXX], 2025 at 11:33 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] in autonomous mode and came to a stop to stage a maneuver towards the curb and to yield to a passenger car traveling westbound on [XXX]. After the passenger car passed the Waymo AV, the Waymo AV proceeded forward, came to a stop, and then reversed into a vacant space at the curb in between two parked passenger cars. The Waymo AV came to a stop at the curb. The test driver of the Waymo AV then transitioned to manual mode and reversed, and the rear of the Waymo AV made contact with the front of the passenger car that was parked behind 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 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11952WaymoSource file ↗Property damage only2025-10NHTSAWaymoAustin30270-11957Heavy Truck · struck on the front · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- 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 October [XXX], 2025 at 6:00 PM 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 stopped facing southwest in the rightmost lane on [XXX] when it activated its left turn signal and proceeded to change lanes to the second from the right lane. While changing lanes, the Waymo AV came to a stop, partially in the rightmost lane and partially in the second to the right lane, to yield to traffic ahead and a heavy truck that was stopped facing southwest in the adjacent lane behind and to the left of the Waymo AV. The heavy truck proceeded forward momentarily and then stopped. As traffic ahead advanced, the heavy truck proceeded forward and the front right side of the heavy truck made contact with the front left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. 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-11957WaymoSource file ↗Property damage only2025-10NHTSAWaymoLos Angeles30270-12059struck on the rear · stopped
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 9:31 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a tow truck on [XXX] near [XXX]. The Waymo AV was traveling westbound on a narrow portion of [XXX] when it maneuvered to the right and came to a stop to yield to a tow truck that was traveling eastbound on [XXX]. While the Waymo AV remained stopped, the tow truck proceeded forward to pass the Waymo AV and the left side of the tow truck made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-12059WaymoSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-12063Passenger Car · struck on the rear · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- 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 October [XXX], 2025 at 4:58 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing south in the right lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car that was initially stopped directly behind the Waymo AV proceeded to change lanes to the left lane, and the right side of the passenger car made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-12063WaymoSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-11949SUV · 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.
On October [XXX], 2025 at 7:25 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound in the rightmost lane on [XXX] behind an SUV that was also traveling westbound in the rightmost lane. The SUV came to a stop and activated its right turn signal, and the Waymo AV came to a stop to yield to the stopped SUV. While the Waymo AV remained stopped, the SUV reversed 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-11949WaymoSource file ↗Property damage only2025-10NHTSAWaymoScottsdale30270-12052Passenger Car · struck on the rear · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 12:37 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car in an alley behind [XXX]. The Waymo AV was parked facing east in the alley behind [XXX] with hazard lights activated when a passenger car that was traveling southbound on [XXX] made a right turn into the alley. As the passenger car proceeded westbound in the alley to pass the parked Waymo AV on the left, the left side of the passenger car made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 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-12052WaymoSource file ↗Minor injury2025-10NHTSAZooxSan Francisco30610-13121Passenger Car · struck on the rear left, rear right · making left turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear Left, Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Cloudy
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Highlander
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
A Zoox vehicle (Vehicle 1) operating in autonomous mode was westbound on [XXX], preparing to make an unprotected left turn onto [XXX] in San Francisco. As the Zoox vehicle slowed approaching the intersection at [XXX], a left-turning vehicle in the oncoming lane accelerated abruptly. The Zoox vehicle braked in response to the oncoming vehicle, and was rear ended by a passenger car (Vehicle 2) traveling directly behind. The Zoox vehicle operator then disengaged from autonomy, and shortly after, continued through the intersection along [XXX] and pulled over to exchange information. The Zoox vehicle sustained minor damage to the rear end, and Vehicle 2 appears to have sustained moderate damage to the left front area and hood. The Zoox vehicle operator and the software operator, seated in the front passenger seat, reported injuries after the collision. The police were not called.
cause not established30610-13121ZooxSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-11842SUV · struck on the rear · parked
- Crash With
- SUV
- 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 October [XXX], 2025 at 6:38 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 eastbound on [XXX] when it slowed to a stop and parked partially in-lane for a passenger drop-off with hazard lights activated. While the Waymo AV was stopped, an SUV that was traveling eastbound on [XXX] proceeded to pass to the left of the parked Waymo AV. As the SUV was maneuvering around the Waymo AV, a passenger in the Waymo AV opened the rear left door and the right side of the SUV made contact with the open rear left door of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passengers in the Waymo AV were not belted at the time of the collision, likely as they were preparing to exit the Waymo AV. 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-11842WaymoSource file ↗No injury reported2025-10NHTSAWaymoPhoenix30270-11889struck on the front right · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 47
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Highway / Freeway
- 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 October [XXX], 2025 at 9:15 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a trash can on [XXX] near Exit [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane. A pickup truck that was traveling northbound on [XXX] in the third from the right lane made contact with a trash can that was in the roadway. The trash can deflected off the pickup truck and rolled across the roadway. As the trash can was entering the Waymo AV's lane of travel, the test driver transitioned the Waymo AV to manual mode and began to maneuver to the right and the trash can made contact with the front 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. 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-11889WaymoSource file ↗Property damage only2025-10NHTSAWaymoMountain View30270-12011Passenger 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
- Making Right 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 October [XXX], 2025 at 10:46 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mountain View, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west in the right turn lane on [XXX] for a red light at the intersection with [XXX]. The Waymo AV initiated a right turn and then came to a stop again before entering [XXX]. A passenger car that was making a right turn directly behind the Waymo AV proceeded forward 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-12011WaymoSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-11883Bus · struck on the front left · stopped
- Crash With
- Bus
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- San Francisco Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 6:20 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 right lane on [XXX] behind a bus in a queue of traffic. As traffic ahead advanced, the Waymo AV momentarily proceeded forward, then came to a stop again to yield to the bus, which had stopped in lane with its hazard lights active. The bus then began to reverse, maneuvering to parallel park at the curb on the right side of the roadway. As the bus continued to reverse, the rear left side of the bus made contact with the front right 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-11883WaymoSource file ↗Property damage only2025-10NHTSAAurora InnovationAledo30530-13119struck on the front left · 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 Left
- SV Precrash Speed (MPH)
- 7
- Within ODD?
- No, see Narrative
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Partly Cloudy
- Make
- PETERBILT
- Model
- 579
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.
At 1:54 PM CDT on October [XXX], 2025 in Aledo, Texas, an Aurora truck traveling at approximately 7 mph on an [XXX] frontage road in autonomy brushed against a temporary construction barrier. This was a development test using testing software, not Aurora's commercial driverless software. During development missions, Aurora tests new roads and conditions outside of its current ODD to prepare for safe driverless operations as Aurora expands its ODD. Two vehicle operators and a backseat rider were inside the vehicle. While traversing a very narrow lane between temporary barriers and a ditch, slowly and with support of remote assist, the Aurora truck brushed a roadside barrier, resulting in minor scraping on the side of the truck. The Aurora vehicle operator then disengaged autonomy and manually drove the truck to Aurora's Fort Worth terminal. No injuries were reported. No damage to the barrier was observed.
cause not established30530-13119Aurora InnovationSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-11998Passenger 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
- 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 October [XXX], 2025 at 10:24 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 southbound on [XXX] when it began to slow for a yellow light at the intersection with [XXX]. As the traffic light turned red and the Waymo AV continued slowing, a passenger car that was traveling southbound on [XXX] 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. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11998WaymoSource file ↗Property damage only2025-10NHTSAWaymoTempe30270-12044struck on the rear left · 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
- Rear Left
- 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 October [XXX], 2025 at 3:39 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a gate on [XXX] at [XXX]. The Waymo AV was stopped at the curb facing north in a cul-de-sac on [XXX] for a passenger pickup near the gated entrance separating [XXX] from [XXX]. While the Waymo AV was stopped, a passenger car approached the other side of the gated entrance and the north side of the swinging gate began swinging out into the roadway towards the Waymo AV. As the swinging gate was opening, the Waymo AV proceeded straight and the swinging gate made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and the gate 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-12044WaymoSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-12045Passenger 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)
- 2
- CP Pre-Crash Movement
- Making Right Turn
- 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 October [XXX], 2025 at 5:22 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 eastbound on [XXX] when it began to slow for a stop sign at the intersection with [XXX]. A passenger car traveling southwestbound on [XXX] proceeded to make a slight right turn at the intersection to continue on [XXX]. As the passenger car crossed through the intersection, it crossed the center double yellow line and the front left side of the passenger car 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. 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-12045WaymoSource file ↗Property damage only2025-10NHTSAWaymoAustin30270-11996struck on the rear right, front right, bottom · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right, Front Right, Bottom
- SV Precrash Speed (MPH)
- 20
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Rain
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 12:37 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas traveled through standing water on [XXX] at [XXX]. The Waymo AV was traveling southwestbound on [XXX] and proceeding straight through the intersection with [XXX] when it approached standing water in the Waymo AV''s lane of travel. As the Waymo AV traveled through the standing water, which made contact with the front, rear, and bottom 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-11996WaymoSource file ↗Property damage only2025-10NHTSAWaymoAustin30270-11992SUV · struck on the right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 9:48 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and came to a stop for a red light in the designated left turn lane at the intersection with [XXX]. While the Waymo AV was stopped, a pedestrian who was the previous passenger in the Waymo AV stood in front of the stationary Waymo AV, preventing the Waymo AV from moving. After receiving over-the-phone assistance from Waymo Rider Support, the prior passenger opened the rear right door of the Waymo AV and began searching the rear seats. The traffic light turned green, and the Waymo remained stopped with the rear right door open. An SUV that was initially stopped directly behind the Waymo AV reversed, then proceeded to pass to the right of the stationary Waymo AV, and the left of the SUV made contact with the open rear right door 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-11992WaymoSource file ↗Property damage only2025-10NHTSAWaymoWashington30270-13026SUV · struck on the rear right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Metropolitan Police Department of the District of Columbia
- 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 October [XXX], 2025 at 1:28 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing south in the left lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the light turned green and traffic ahead advanced, the Waymo AV began to proceed forward at a low rate of speed and an SUV that was initially stopped directly behind the Waymo AV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present in the driver's seating position. 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-13026WaymoSource file ↗Property damage only2025-10NHTSAWaymoSouth San Francisco30270-11926Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- South San Francisco Police
- 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 October [XXX], 2025 at 7:49 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in South San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing southeast on [XXX] in a queue of traffic for a red light for the intersection with [XXX]. While the Waymo AV remained 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. 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-11926WaymoSource file ↗Serious injury2025-10NHTSAWaymoAtlanta30270-11841Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Moderate W/ 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 October [XXX], 2025 at 9:55 AM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and came to a stop at the stop sign at the intersection with [XXX]. A passenger car traveling directly behind the Waymo AV proceeded without stopping, and the front driver side of the passenger car then made contact with the rear side of the stationary Waymo AV. First responders arrived at the scene and assisted the rider out of the Waymo AV. An ambulance was called to the scene and Waymo later learned that the rider was transported to the hospital. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV was not belted at the time of the collision they were in the process of locating the belt fastener for the seat they were occupying. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11841WaymoSource file ↗Not graded by the source2025-10NHTSAWaymoSan Francisco30270-13056stopped
- Crash With
- Other, see Narrative
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Unknown
- SV Precrash Speed (MPH)
- 0
- 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 October [XXX], 2025 at 8:17 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was alleged to have contributed to a collision between two SUVs on California State [XXX] near [XXX]. The Waymo AV was traveling northbound in the second from the right lane on California State [XXX] when it slowed to a stop in-lane with its left turn signal activated to stage a lane change into the designated left turn lane for the intersection with [XXX]. While the Waymo AV was stopped, a passenger car traveling northbound in the second from the right lane on California State [XXX] slowed to a stop behind the Waymo AV and an SUV slowed to a stop behind the passenger car. A second SUV traveling northbound in the second from the right lane on California State [XXX] then approached the first stopped SUV from behind, and the front left side of the second SUV made contact with the rear right side of the first SUV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both of the SUVs sustained damage. Waymo received notice of the alleged contribution on November 3, 2025. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13056WaymoSource file ↗Property damage only2025-10NHTSAWaymoMountain View30270-11906Passenger 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
- Making Right 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 October [XXX], 2025 at 3:51 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mountain View, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southwestbound on [XXX] in the dedicated right turn lane when it stopped for a red light at the intersection with [XXX]. The Waymo AV initiated the right turn and then came to a stop again before entering [XXX]. A passenger car that was making a right turn directly behind the Waymo AV continued forward 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-11906WaymoSource file ↗Minor injury2025-10NHTSAWaymoTempe30270-11908SUV · struck on the rear left · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 36
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Tempe Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 9:06 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling westbound in the leftmost lane on [XXX] and proceeding straight at a green light at the intersection with [XXX]. As the Waymo AV entered the intersection, an SUV traveling westbound in the second to the left lane on [XXX] slowed and maneuvered left into the Waymo AV's lane of travel. The front left side of the SUV made contact with the right rear 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. The passenger in 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-11908WaymoSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-12008Passenger Car · struck on the front right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 12:09 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 eastbound on [XXX] when it slowed to a stop to yield to a passenger car that slowed to stop in-lane facing east on [XXX]. While the Waymo AV was stopped, the passenger car reversed and the rear 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. 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-12008WaymoSource file ↗Property damage only2025-10NHTSAWaymoLos Angeles30270-11860Pickup 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
- 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 October [XXX], 2025 at 4:48 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] when it slowed to a stop to yield to a vehicle stopped in-lane facing north on [XXX]. While the Waymo AV was stopped, a pickup truck traveling northbound 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. 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-11860WaymoSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-11988Heavy Truck · struck on the left · stopped
- Crash With
- Heavy Truck
- 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
- Making Left Turn
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 11:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] when it came to a stop to yield to a heavy truck that was making a left turn from [XXX] onto eastbound [XXX]. As the heavy truck was completing the left turn, the heavy truck crossed the double yellow lane line into the Waymo AV's lane of travel, and the left side of the heavy truck made contact with the left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11988WaymoSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-11999struck on the rear · 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
- Rear
- SV Precrash Speed (MPH)
- 20
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On October [XXX], 2025 at 9:15 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a basketball on [XXX] at [XXX]. The Waymo AV was traveling northwestbound on [XXX], proceeding straight through the intersection with [XXX]. As the Waymo AV was exiting the intersection and continuing on [XXX], a basketball that rolled into the Waymo AV's lane of travel made contact with the left side rear tire of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The basketball 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-11999WaymoSource file ↗Property damage only2025-10NHTSAWaymoSan Francisco30270-11858Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- 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 October [XXX], 2025 at 7:12 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 west in the left lane on [XXX] with its left turn signal activated in a queue of traffic for a red light at the intersection of [XXX]. As the traffic light turned green and traffic ahead advanced, the Waymo AV initially proceeded forward and then came to a stop before entering the intersection, perceiving that there may be insufficient room to proceed fully through the intersection without blocking it, as the vehicle ahead of the Waymo AV had stopped within the intersection to yield to pedestrians crossing [XXX] in the marked crosswalk. While the Waymo AV was stopped, a passenger car traveling westbound in the left lane on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 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-11858WaymoSource file ↗Property damage only2025-10NHTSAZooxLas Vegas30610-11990SUV · 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)
- 14
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Highlander
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling east towards the Passenger Pick-up area in Terminal 3 of [XXX] in Las Vegas. An SUV (Vehicle 2), traveling behind in the left adjacent lane, abruptly attempted to overtake and cut in front of the Zoox vehicle in an apparent attempt to change lanes to the right towards Terminal 3 Departures. The Zoox vehicle braked hard in response to the encroaching vehicle, and the operator then disengaged from autonomy and continued to brake, but contact could not be avoided. The right rear side of Vehicle 2 swiped the left front area of the Zoox vehicle. Both operators stopped after the collision and exchanged information. Both vehicles sustained moderate damage, and the Zoox vehicle was subsequently towed from the scene. There were no reported injuries, and police were not called.
cause not established30610-11990ZooxSource file ↗Property damage only2025-10NHTSAWaymoPhoenix30270-12053Pickup 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
- 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 October [XXX], 2025 at 6:42 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the third from the right lane on [XXX]. As the Waymo AV approached the intersection at [XXX], it slowed to a stop prior to entering the intersection due to debris in the Waymo AV's lane of travel. A pickup truck traveling eastbound on [XXX] behind the Waymo AV 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. 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-12053WaymoSource file ↗