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
1,184 records match
7 death reports20264 registriesClear
Narrow it down
What happened
Country
Year
Not graded by the source2026-02-06FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-14646da 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 PULMONARY WEDGE RESECTION SURGICAL PROCEDURE, ERRORS OCCURRED REPEATEDLY DURING PATIENT SIDE CART (PSC) DOCKING. THE TECHNICAL SUPPORT ENGINEER (TSE) HAD CUSTOMERS PERFORM A HARD POWER-CYCLE, BUT THE ISSUE PERSISTED. THE TSE FOUND ERRORS ON THE PATIENT SIDE MANIPULATOR 1 (PSM) AND ON STAR IN THE LOGS. THE PROCEDURE WAS CONVERTED FROM A SINGLE PORT PROCEDURE TO LAPAROSCOPY. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE SURGICAL PROCEDURE WAS CONVERTED FROM A ROBOTIC TO A TRADITIONAL LAPAROSCOPIC APPROACH DUE TO AN UNRECOVERABLE SYSTEM ERROR WITH THE PATIENT SIDE CART (PSC), WHICH COULD NOT BE RESOLVED DESPITE TROUBLESHOOTING EFFORTS. THE SURGICAL TEAM PROCEEDED USING THE SAME PORT CONFIGURATION; THUS, THE CONVERSION DID NOT NECESSITATE INCREASED PORT SIZE OR THE ADDITION OF EXTRA PORTS. THERE WAS NO INFORMATION WHETHER THE PATIENT TOLERATED THE CHANGE.
cause not established2955842-2026-14646Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-02-06FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-14647da 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-14647Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-02-06FDA MAUDEAuris HealthMonarch Platform3014447948-2026-00013Monarch Platform
Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN ENCOUNTERED A SCOPE ISSUE AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED CLINICAL CONSEQUENCES TO THE PATIENT.
cause not established3014447948-2026-00013Auris HealthMonarch PlatformRead the record ↗Not graded by the source2026-02-04FDA MAUDEMedtronic plc — Surgical RoboticsMazor X3005075696-2026-00065Mazor X
Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: ADDITIONAL INFORMATION WAS RECEIVED. IT WAS REPORTED THAT THE SCREWS WERE REMOVED AFTER THE FAULTY POSITION WAS SEEN INTRA-OPERATIVELY AND WERE NOT SEEN ON POST-OPERATIVE THREE-DIMENSIONAL (3D) SCANS. THE AMOUNT OF DEVIATION WAS ESTIMATED TO BE 10-15MM.
cause not established3005075696-2026-00065Medtronic plc — Surgical RoboticsMazor XRead the record ↗Not graded by the source2026-02-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-02523da 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 FRAGMENT FROM A HARMONIC ACE INSTRUMENT BROKE OFF AND FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED AND NO INJURY WAS REPORTED. IT IS UNCLEAR HOW THE FRAGMENT WAS RETRIEVED. THE INSTRUMENT LOT # AND EVENT DATE ARE UNKNOWN ALTHOUGH THE INITIAL REPORTER INDICATED THAT THE EVENT OCCURRED IN 2025.
cause not established2955842-2026-02523Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-02-04FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-08624da 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, PART OF THE HARMONIC ACE INSTRUMENT TIP BROKE OFF. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED ADDITIONAL INFORMATION REGARDING THE REPORTED EVENT. THE HARMONIC ACE INSTRUMENT WAS INSPECTED PRIOR TO USE AND APPEARED NORMAL, WITH NO VISIBLE DAMAGE. WHILE DISSECTING, A FRAGMENT FELL INSIDE THE PATIENT. THE INSTRUMENT HAD ONLY BEEN IN USE FOR 2 OR 3 MINUTES, WITH NO NOTED FUNCTIONAL ISSUES OTHER THAN AN ERROR MESSAGE ON THE ROBOT SYSTEM, PROMPTING FURTHER INSPECTION. THERE WAS NO COLLISION WITH OTHER INSTRUMENTS OR HARD MATERIALS, AND PRIOR TO REMOVAL, NO RESISTANCE WAS FELT AND THE WRIST WAS STRAIGHTENED. AFTER REMOVAL, NO DAMAGE TO THE CANNULA OR INSTRUMENT WAS OBSERVED. THE FRAGMENT WAS RETRIEVED USING A LAPAROSCOPIC GRASPER BUT WAS ACCIDENTALLY DISCARDED. NO ADDITIONAL PROCEDURES OR POST-OPERATIVE IMAGING WERE REQUIRED, AND THE SURGERY WAS COMPLETED ROBOTICALLY. THERE WERE NO REPORTED PATIENT INJURIES OR COMPLICATIONS RELATED TO A RETAINED FOREIGN OBJECT, AND THE INSTRUMENT IS AVAILABLE FOR RETURN, THOUGH NO PHOTOS OR VIDEOS ARE AVAILABLE FOR REVIE
cause not established2955842-2026-08624Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-02-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-14643da 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 RIGHT COLECTOMY PROCEDURE, THERE WAS INADEQUATE ENERGY TO STOP BLEEDING. THE FOLLOWING INFORMATION IS UNKNOWN: THE SOURCE AND CAUSE OF THE BLEEDING, THE ESTIMATED BLOOD LOSS ASSOCIATED WITH THE COMPLICATION, AND WHAT SURGICAL/MEDICAL INTERVENTION WAS RENDERED DUE TO THE BLEEDING. ADDITIONALLY, IT WAS REPORTED THAT AN UNSPECIFIED INSTRUMENT WAS EXPERIENCING ISSUES CONNECTING TO THE ENERGY SHIELD MONITOR (ESM) VIA THE GREEN MONOPOLAR CORD. THE CUSTOMER WAS REPORTEDLY LOSING CONNECTION VIA THE MONOPOLAR CORD AND GETTING A "BAD CORD" MESSAGE. FURTHERMORE, ENERGY WOULD START AND THEN STOP. MULTIPLE CORDS AND INSTRUMENTS WERE TRIED WITHOUT SUCCESSFULLY RESOLVING THE ISSUE. THE PROCEDURE WAS COMPLETED USING THE SAME GENERATOR.
cause not established2955842-2026-14643Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-02-03FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-06522da 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, AN ERROR OCCURRED AND PATIENT SIDE MANIPULATOR (PSM) #2 LOOKED LIKE IT HAD NO POWER. AN INTUITIVE SURGICAL, INC. (ISI) TECHNICAL SERVICE ENGINEER (TSE) CONFIRMED AN ERROR INDICATING THAT PSM #2 HAD NO POWER. THE TSE ADVISED TO THE CUSTOMER TO PERFORM HARD POWER CYCLE OF THE SYSTEM. THE CUSTOMER TURNED OFF THE SYSTEM. HOWEVER, THE SYSTEM BOOTED BACK UP AUTOMATICALLY WITH ANOTHER ERROR. AS A RESULT, THE CUSTOMER ELECTED TO CONVERT THE CASE TO TRADITIONAL LAPAROSCOPIC SURGERY. ISI HAS ATTEMPTED TO GATHER ADDITIONAL INFORMATION REGARDING THE REPORTED EVENT; HOWEVER, NO RESPONSE HAS BEEN RECEIVED.
cause not established2955842-2026-06522Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Death reported2026-02-03FDA MAUDEMedtronic plc — Surgical RoboticsMazor X3005075696-2026-00049Mazor X
Mazor X — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: ADDITIONAL INFORMATION WAS RECEIVED. IT WAS REPORTED THAT THE SURGEON'S TECHNIQUE WAS DRILL, TAP, THEN SCREW. THE SURGEON OPERATED AND STARTED ON THE RIGHT SIDE. T3 AND T4 WERE PLACED WHEN AN INACCURACY WAS NOTICED. IT WAS ALSO NOTED THAT WITH REGISTRATION AND AFTER RE-IMAGING, THEY HAD A YELLOW VALUE BUT THEY WERE UNSURE WHAT LEVEL THIS WAS ON. ADDITIONALLY, IT WAS NOTED THAT THE PATIENT HAD A PRE-EXISTING FRACTURE AT T5.
cause not established3005075696-2026-00049Medtronic plc — Surgical RoboticsMazor XRead the record ↗Not graded by the source2026-02-03FDA MAUDEMedtronic plc — Surgical RoboticsMazor XMW5183641Mazor X
Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: AN 82-YEAR-OLD FEMALE UNDERWENT PLANNED THORACIC PERCUTANEOUS INSTRUMENTATION FOR AN UNSTABLE T5 FRACTURE USING ROBOTIC NAVIGATION. DURING THE PROCEDURE, ROBOTIC REGISTRATION WAS PROLONGED AND TECHNICALLY CHALLENGING. DURING PEDICLE SCREW PLACEMENT, LOSS OF RESISTANCE WITH CSF RETURN WAS NOTED AND INSTRUMENTATION WAS STOPPED. SHORTLY THEREAFTER, NEUROMONITORING SIGNALS WERE LOST, AND THE PATIENT EXPERIENCED A PULSELESS ELECTRICAL ACTIVITY (PEA) ARREST WITH RAPID RETURN OF SPONTANEOUS CIRCULATION FOLLOWING BRIEF RESUSCITATION. POST-EVENT EVALUATION DEMONSTRATED ACUTE MYOCARDIAL DYSFUNCTION WITH PATENT CORONARY ARTERIES AND IMAGING FINDINGS CONCERNING FOR THORACIC SPINAL CORD INJURY RELATED TO A MEDIAL PEDICLE BREACH. THE FOLLOWING DAY, THE SERVICE RECEIVED AN URGENT MANUFACTURER SAFETY NOTICE REGARDING ROBOTIC NAVIGATION SOFTWARE ACCURACY.
cause not establishedMW5183641Medtronic plc — Surgical RoboticsMazor XRead the record ↗Not graded by the source2026-02-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-15071da 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-15071Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-02-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-05346da 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 MONOPOLAR CURVED SCISSORS (MCS) INSTRUMENT ARCED, CAUSING A BURN ON THE MCS TIP COVER ACCESSORY AND THE SMALL INTESTINE. THE SURGEON PLACED A "SAFETY STITCH" DUE TO THE REPORTED SUPERFICIAL BURN(S) ON THE SMALL INTESTINE. THIS EVENT OCCURRED DURING DISSECTION WHILE THE SURGEON WAS USING COAG ENERGY WITH THE MCS INSTRUMENT. IT WAS REPORTED THAT THIS EVENT OCCURRED WITH TWO DIFFERENT MCS TIP COVER ACCESSORIES. THE MCS TIP COVER ACCESSORY WAS PROPERLY INSTALLED. THE E-200 GENERATOR WAS BEING USED TO SUPPLY ENERGY DURING THIS PROCEDURE. THE GROUNDING PAD DID NOT APPEAR TO HAVE ANY ISSUES/DEFECTS. THE BURNS WERE DISCOVERED IN THE LAST 30 MINUTES OF THE SURGERY. THE PATIENT WAS REPORTED TO BE IN GOOD CONDITION AND DID NOT EXPERIENCE ANY POST-OPERATIVE COMPLICATIONS. THE MCS INSTRUMENT DID NOT COLLIDE WITH OTHER INSTRUMENTS OR TOUCH STAPLES OR CLIPS WHILE ENERGIZED. ADDITIONALLY, THE MCS INSTRUMENT WAS NOT IMMERSED IN LIQUIDS WHEN THE EVENT OCCURRED. THE MCS INSTRUMENT WAS REPLACED AND THE PROCEDURE WAS COMPLETED AS PLANNED.
cause not established2955842-2026-05346Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-02-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-14961da 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 FRAGMENT BROKE OFF THE SYNCHROSEAL INSTRUMENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME PROCEDURE WHICH WAS COMPLETED ROBOTICALLY. INTUITIVE SURGICAL, INC. (ISI) HAS ATTEMPTED TO GATHER ADDITIONAL INFORMATION REGARDING THE REPORTED EVENT; HOWEVER, NO RESPONSE HAS BEEN RECEIVED.
cause not established2955842-2026-14961Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-02-02FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-05347da 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-05347Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Property damage only2026-02NHTSAAvrideDallas31101-14065Pickup Truck · struck on the right · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 25
- 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
- Dallas Police Department
- Make
- HYUNDAI
- Model
- Ioniq 5
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 February [XXX], 2026 at 9:06 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northbound on [XXX] engaged in autonomous mode entering the intersection at [XXX]. The AVRIDE AV entered the intersection with the green light when a pickup truck proceeded to enter the intersection from [XXX] after driving through a red light without stopping. In the intersection, the front of the pickup truck made contact with the right side of the AVRIDE AV. Airbags were deployed on the AVRIDE AV. Both vehicles sustained damage. No injuries were reported.
cause not established31101-14065AvrideSource file ↗Property damage only2026-02NHTSAWaymoSan Francisco30270-13985Passenger 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
- Other, see Narrative
- 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 February [XXX], 2026 at 12:54 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 south on [XXX] for a red light at the intersection with [XXX] with a passenger car stopped directly behind the Waymo AV. While both the Waymo AV and the passenger car were stopped, an SUV traveling southbound on [XXX] approached the stopped passenger car from behind, and the front of the SUV made contact with the rear of the passenger car. As a result of this contact, the passenger car was pushed 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. All three 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-13985WaymoSource file ↗Property damage only2026-02NHTSAWaymoCulver City30270-14153SUV · 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
- 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 February [XXX], 2026 at 2:29 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Culver City, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northeastbound in autonomous mode in the third from the right lane on [XXX] when it slowed to a stop for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling northeastbound in the third from the right lane on [XXX] 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, 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-14153WaymoSource file ↗Property damage only2026-02NHTSAWaymoLos Angeles30270-14198Pickup Truck · struck on the rear left · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- 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 February [XXX], 2026 at 3:19 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing southeast in the rightmost lane on [XXX] for a red light at the intersection with [XXX]. A pickup truck traveling southeastbound on [XXX] in the rightmost lane with its right turn signal activated approached the Waymo AV from behind, and the front of the pickup truck made contact with the right side of the rear of the stationary Waymo AV. At the time of 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-14198WaymoSource file ↗Property damage only2026-02NHTSAWaymoSan Francisco30270-13981Passenger Car · struck on the front right · parked
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On February [XXX], 2026 at 11:56 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked at the curb facing east on [XXX] when a passenger car traveling eastbound on [XXX] proceeded to parallel park at the curb directly in front of the Waymo AV. While the passenger car was maneuvering to park, the passenger car reversed and the rear of the passenger car made contact with the front of the parked 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-13981WaymoSource file ↗Property damage only2026-02NHTSAWaymoNashville30270-14151SUV · struck on the right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- 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
- Intersection
- Weather
- Clear
- Investigating Agency
- Metropolitan Nashville 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 February [XXX], 2026 at 2:01 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Nashville, Tennessee was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] and proceeding straight at the two-way stop intersection with [XXX]. As the Waymo AV was proceeding through the intersection, which had stop signs only on [XXX], an SUV traveling southbound on [XXX] entered the intersection without stopping at the stop sign, and the front of the SUV made contact with the right 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-14151WaymoSource file ↗Minor injury2026-02NHTSAWaymoAustin30270-14048SUV · struck on the rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Austin Fire 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 February [XXX], 2026 at 12:03 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 eastbound in the left lane on [XXX] when it slowed to a stop for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling eastbound in the left lane on [XXX] 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. 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-14048WaymoSource file ↗Property damage only2026-02NHTSAAvrideAustin31101-14235SUV · struck on the front left · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 20
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 February [XXX], 2026 at 10:39 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound in the left lane on [XXX] in autonomous mode when it approached the traffic light at the intersection with [XXX]. At the intersection, there was an SUV in the middle lane lane stopped at the red light traveling in the same direction as the AVRIDE AV on [XXX]. As the light turned green and the AVRIDE AV pulled beside the SUV, the SUV began to make a left turn across lanes without signalling. This turn caused the left front of the SUV to make contact with the right front of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported.
cause not established31101-14235AvrideSource file ↗Property damage only2026-02NHTSAWaymoSan Francisco30270-14304SUV · struck on the front left · stopped
- Crash With
- SUV
- 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
- 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 February [XXX], 2026 at 10:00 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 on [XXX] when it slowed to a stop to yield to an SUV stopped facing west, partially in the bicycle lane and partially in-lane, on [XXX] in front of the Waymo AV. While the Waymo AV was stopped, the SUV reversed, and the rear left side of the SUV 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. 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-14304WaymoSource file ↗Property damage only2026-02NHTSAWaymoLos Angeles30270-13975Pickup Truck · struck on the right · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 12
- CP Pre-Crash Movement
- Entering Traffic
- 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 February [XXX], 2026 at 5:52 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 eastbound on [XXX] and completing a right turn onto southbound [XXX] when it began to slow to yield to a pickup truck that was facing south on [XXX] and reversing near the curb. The pickup truck came to a stop and then proceeded forward towards the curb, and the Waymo AV slowed to a stop to yield to the pickup truck. The pickup truck maneuvered to the left momentarily and came to a stop, and the Waymo AV proceeded forward on the left to pass the pickup truck. As the Waymo AV was passing, the pickup truck maneuvered to the left and entered the Waymo AV's lane of travel, and the front left side of the pickup truck made contact with the 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. 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-13975WaymoSource file ↗Property damage only2026-02NHTSAWaymoSan Francisco30270-14045Heavy Truck · struck on the rear · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- 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 February [XXX], 2026 at 1:05 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] and completing a right turn onto southbound [XXX] when it maneuvered to the right towards the curb and slowed to a stop partially in lane, to yield to a heavy truck traveling northbound on [XXX]. While the heavy truck passed the stopped Waymo AV, the heavy truck maneuvered to the left, and the rear left side of the heavy truck trailer 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 involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-14045WaymoSource file ↗Minor injury2026-02NHTSAWaymoSan Francisco30270-13957Passenger 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
- 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 February [XXX], 2026 at 3:15 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 northwest on [XXX] in the designated left turn lane with its left turn signal activated in preparation for a left turn onto [XXX]. After the light turned green, the Waymo AV proceeded forward before coming to a stop, yielding to southeastbound traffic on [XXX]. While the Waymo AV was stopped, a passenger car initially stopped 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. Both vehicles sustained damage. The passenger 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-13957WaymoSource file ↗Property damage only2026-02NHTSAWaymoAustin30270-14096Passenger Car · struck on the 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
- Left
- SV Precrash Speed (MPH)
- 32
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Front 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.
Other than a correction to indicate that the automation system engaged was an ADS rather than an ADAS, the content of this report is unchanged from the initial report submitted on March 13, 2026 [Report ID # [XXX] On February [XXX], 2026 at 10:34 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 traveling eastbound in the second from the left lane on [XXX] as it approached the green light at the intersection with [XXX] when a passenger car that was initially stopped in a queue of traffic in the designated left turn lane of [XXX] maneuvered to the right to change lanes and entered the Waymo AV's lane of travel. The Waymo AV maneuvered to the right to avoid the incoming passenger car and the front right side of the passenger car 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. 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-14096WaymoSource file ↗Property damage only2026-02NHTSAWaymoTempe30270-14097Passenger 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 February [XXX], 2026 at 1:49 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] in a queue of traffic for a stop sign at the intersection with [XXX]. A passenger car that was stopped directly in front of the Waymo AV proceeded forward, entering the intersection, and the Waymo AV proceeded forward and came to a stop at the stop sign. While the Waymo AV was coming to a stop, the passenger car stopped and began to reverse, 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. 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-14097WaymoSource file ↗Minor injury2026-02NHTSAZooxSanta Monica30610-14167SUV · struck on the rear left, rear, rear right · changing lanes
- Crash With
- SUV
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Changing Lanes
- SV Contact Area
- Rear Left, Rear, Rear Right
- SV Precrash Speed (MPH)
- 17
- CP Contact Area
- Front Left, Front, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- City of Santa Monica PD
- 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 southeast on [XXX], preparing to change lanes to the right to turn onto [XXX] in Santa Monica, when it was hit on the right rear corner (rear bumper, hatch, right rear wheel, and right rear quarter panel) by an SUV (Vehicle 2). The Zoox vehicle stopped facing southwest on [XXX], with the front of Vehicle 2 still engaged with the right rear of the Zoox vehicle. The Zoox vehicle sustained severe rear damage, including damage to data recording systems. Vehicle 2 had major damage to its front end. Airbags deployed in both vehicles, and they were towed from the scene. Police and emergency responders arrived to assist, and the driver of vehicle 2 was detained. The Zoox vehicle operator and two passengers reported soreness and a headache after the collision.
cause not established30610-14167ZooxSource file ↗Property damage only2026-02NHTSAWaymoAtlanta30270-14074Passenger 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
- 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 February [XXX], 2026 at 8:00 PM 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 parked in-lane facing west on [XXX] with its hazard lights activated for a passenger dropoff. While the Waymo AV was parked, a passenger car that was initially stopped directly behind the Waymo AV proceeded to pass the Waymo AV on the left. As the passenger car was maneuvering around the Waymo AV, 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. 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-14074WaymoSource file ↗Property damage only2026-02NHTSAAvrideDallas31101-14166SUV · 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)
- 3
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Rear Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 February [XXX], 2026 at 7:31 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was parked in the far right lane facing east in autonomous mode on [XXX] waiting to pick up a robotaxi passenger. After the passenger entered the AVRIDE AV, the AVRIDE AV began to move forward in the right lane. As the AVRIDE AV began to move forward, an SUV driving in the left lane next to the AVRIDE AV started to move into the AVRIDE AV's lane in an attempt to move over two lanes simultaneously to park. While attempting this maneuver, the SUV cut off the AVRIDE AV, causing the rear right of the SUV to make contact with the left front of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported.
cause not established31101-14166AvrideSource file ↗Property damage only2026-02NHTSAWaymoAustin30270-14004Pickup 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
- 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 February [XXX], 2026 at 10:49 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling northwestbound on [XXX] in the third from the right lane when it slowed to a stop for a HAWK signal yellow light at the intersection with [XXX]. While the Waymo AV was stopped, a pickup truck traveling northwestbound on [XXX] in the same lane as 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-14004WaymoSource file ↗Property damage only2026-02NHTSAWaymoSan Francisco30270-14073Heavy Truck · struck on the rear · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- 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 February [XXX], 2026 at 11:08 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 stopped facing north in a queue of traffic on a narrow portion of [XXX] for a red light at the intersection with [XXX], with vehicles parked at the curb in both directions. While the Waymo AV was stopped, a heavy truck traveling westbound on [XXX] made a left turn onto southbound [XXX]. The Waymo AV proceeded forward and to the right momentarily before slowing to a stop to yield to the heavy truck, and the heavy truck proceeded forward, and the left side of the heavy truck trailer 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 involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-14073WaymoSource file ↗Property damage only2026-02NHTSAWaymoSan Jose30270-14079Passenger 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)
- 20
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Rain
- Investigating Agency
- San Jose 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 February [XXX], 2026 at 8:33 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Jose, California was in a collision involving a passenger car on [XXX] at the parking lot entrance at [XXX]. The Waymo AV was traveling northwestbound on [XXX] when a van that was traveling northwestbound in front of the Waymo AV with its right turn signal activated maneuvered right towards the curb and slowed at a parking lot entrance at [XXX]. The Waymo maneuvered slightly left to continue straight on [XXX]. As the Waymo AV passed the van, a passenger car traveling westbound in the parking lot at [XXX] exited the parking lot without stopping at the stop sign and entered the Waymo AV's lane of travel, and the front left side of the passenger car 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. 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-14079WaymoSource file ↗Property damage only2026-02NHTSAWaymoOrlando30270-14201Passenger 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 February [XXX], 2026 at 1:48 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing west on [XXX] in the third from the right lane in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car traveling westbound on [XXX] in the third from the right lane 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 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-14201WaymoSource file ↗Property damage only2026-02NHTSAWaymoOrlando30270-13976Passenger 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 Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Cloudy
- Investigating Agency
- Orange County Sheriff's Office
- 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 February [XXX], 2026 at 7:40 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound in the designated right turn lane on [XXX] when it slowed to make a right turn onto northbound [XXX]. As the Waymo AV was proceeding through the right turn, the Waymo AV slowed to a stop in response to a school bus that was stopped facing south in the second from the left lane on southbound [XXX]. While the Waymo AV was stopped, a passenger car traveling westbound on [XXX] and turning right onto northbound [XXX] approached the Waymo AV from behind, and the front right side 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-13976WaymoSource file ↗Property damage only2026-02NHTSAAvrideDallas31101-14150Pickup Truck · struck on the front · changing lanes
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Changing Lanes
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Rear Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
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 February [XXX], 2026 at 4:50 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in slow traffic in the right lane on [XXX] engaged in autonomous mode when it began to switch into the left lane. A pickup truck in the lane next to the AVRIDE AV began to drive next to and mostly past the AVRIDE AV as the AVRIDE AV began to switch lanes. While the AVRIDE AV was attempting to switch to the left lane, the left front of the AVRIDE AV made contact with the right rear of the pickup truck. Both vehicles sustained minor damage. No injuries were reported.
cause not established31101-14150AvrideSource file ↗Property damage only2026-02NHTSAWaymoLos Angeles30270-14118First 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
- Passing
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Partly Cloudy
- Investigating Agency
- Los Angeles Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On February [XXX], 2026 at 2:50 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was stopped facing southwest in the rightmost lane on [XXX] for an SUV which was in a prior collision stopped facing southeast, partially in the rightmost lane on [XXX] and partially on the curb. While the Waymo AV was stopped, an active emergency vehicle with emergency lights activated traveling eastbound on [XXX] proceeded to turn left onto [XXX] and travel northeastbound in the adjacent lane to the Waymo AV, against the proper direction of traffic. The emergency vehicle proceeded to pass the Waymo AV to the left and began to maneuver towards the curb on its left, and the left side of the emergency vehicle 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. The passenger in the Waymo AV was not belted at the time of the collision. 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-14118WaymoSource file ↗Property damage only2026-02NHTSAWaymoScottsdale30270-14012SUV · struck on the rear · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- 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 February [XXX], 2026 at 1:20 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV exited a parking garage on the west side of [XXX] and began to cross [XXX] to enter a parking lot on the east side of [XXX]. The Waymo AV slowed to a stop in the northbound lane to yield to westbound traffic exiting the parking lot. While the Waymo AV was stopped, an SUV traveling northbound on [XXX] in the opposing lane proceeded to pass several vehicles and the Waymo AV on the left, and the right side 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 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-14012WaymoSource file ↗Property damage only2026-02NHTSAWaymoPhoenix30270-14173Passenger Car · struck on the 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
- Left
- SV Precrash Speed (MPH)
- 35
- 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 February [XXX], 2026 at 1:22 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on [XXX] in the rightmost lane. A passenger car was traveling southwestbound, behind and to the left of the Waymo AV in the adjacent lane on [XXX]. The passenger car began to change lanes into the rightmost lane as it was passing the Waymo AV, and the right side of the passenger car 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. 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-14173WaymoSource file ↗Property damage only2026-02NHTSAWaymoSan Francisco30270-14099SUV · struck on the rear · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Cloudy
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On February [XXX], 2026 at 1:06 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 southbound in the rightmost lane on [XXX] with its right turn signal activated and preparing to make a right turn at a green light onto [XXX], when it began to slow before the crosswalk to yield to a pedestrian crossing [XXX] from the north curb within the marked crosswalk. Once the pedestrian was no longer in the Waymo AV's lane of travel, the Waymo AV continued to turn right momentarily, then slowed to a stop before the marked crosswalk to yield to a second pedestrian approaching the north curb at the [XXX] crosswalk. While the Waymo AV was stopped, an SUV that was traveling southbound on [XXX] in the rightmost lane approached the Waymo AV from behind, and the front right side 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 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-14099WaymoSource file ↗Property damage only2026-02NHTSAAvrideAustin31101-14202Pickup 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
- Rear Right, Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Austin Police Department
- Make
- HYUNDAI
- Model
- Ioniq 5
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 February [XXX], 2026 at 6:01 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was facing southeast on [XXX] in autonomous mode while stopped at the traffic light at the intersection with [XXX]. While stopped at the traffic light, a pickup truck approached the AVRIDE AV from the rear and did not stop. This resulted in the front of the pickup truck making contact with the rear of the AVRIDE AV. The pickup truck driver left the scene during post collision documentation and immediately rear ended another vehicle down the road. Both vehicles sustained damage. The AVRIDE AV safety driver went to the hospital for safe measure. No injuries were reported.
cause not established31101-14202AvrideSource file ↗No injury reported2026-02NHTSAZooxLas Vegas30610-14340Pickup Truck · struck on the rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- 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
- 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 occupied Zoox autonomous vehicle traveling south on [XXX] was stopped for a red signal at [XXX] in Las Vegas. After the light turned green, and before the Zoox vehicle started to move, a Pickup (Vehicle 2) traveling directly behind it rear-ended it. Shortly thereafter, both vehicles traveled a few feet ahead and pulled over. The passengers exited the Zoox vehicle onto the sidewalk. After exchanging information, the Zoox vehicle returned to base for inspection, where it was found to have sustained moderate damage. No injuries were reported, and police were not notified.
cause not established30610-14340ZooxSource file ↗Property damage only2026-02NHTSAAvrideDallas31101-14147Passenger Car · struck on the front · making left turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 14
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Dallas Police Department
- Make
- HYUNDAI
- Model
- Ioniq 5
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 February [XXX], 2026 at 7:59 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southwestbound on [XXX] engaged in autonomous mode in the rightmost left-turn lane, preparing to execute a left turn onto [XXX]. A passenger car in the lane to the left of the AVRIDE AV went against the lane turn rules and continued straight into the AVRIDE AVâs lane of travel, resulting in the right side of the passenger car making contact with the left front of the AVRIDE AV. No injuries were reported. both vehicles sustained damage.
cause not established31101-14147AvrideSource file ↗Property damage only2026-02NHTSAAvrideAustin31101-14142Passenger 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
- NM Waiting to Cross Roadway
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- HYUNDAI
- Model
- Ioniq 5
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 February [XXX], 2026 at 9:27 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE was traveling eastbound on [XXX] while in autonomous mode, when it stopped at the crosswalk of the intersection with [XXX] due to vehicles blocking its path from crossing the intersection completely. The safety operator disengaged from autonomous mode and began to reverse the vehicle to allow pedestrians to cross the street. During this reverse process, the rear of the AVRIDE AV made contact with the front of a passenger vehicle stopped behind it. Both vehicles sustained minor damage. No injuries were reported.
cause not established31101-14142AvrideSource file ↗Property damage only2026-02NHTSAZooxSan Francisco30610-14339Non-Motorist: Cyclist · struck on the rear left · making right turn
- Crash With
- Non-Motorist: Cyclist
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- NM Crossing Roadway
- 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 autonomous vehicle was traveling in the right lane on northwest-bound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. Partway through the right turn, the Zoox vehicle further slowed to yield to a pedestrian crossing [XXX], and at that time, a cyclist traveling northwest on the adjacent sidewalk rapidly entered the crosswalk. The Zoox vehicle braked to yield to the approaching cyclist, and the cyclist made contact with the right rear side of the nearly stopped Zoox vehicle. The bicycle fell to the ground, but its rider remained upright. The cyclist picked up their bicycle and rode away from the scene. Shortly after, the Zoox vehicle resumed operation to return to base. There was minor damage to the Zoox vehicle. There were no reported injuries, and police were not notified.
cause not established30610-14339ZooxSource file ↗Property damage only2026-02NHTSAWaymoSan Francisco30270-13980Passenger 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)
- 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 February [XXX], 2026 at 10:06 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was stopped facing west on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. As the light turned green, the Waymo AV momentarily proceeded forward before slowing for the queue of stop-and-go traffic ahead. While the Waymo AV was slowing, a passenger car that was initially stopped behind the Waymo AV proceeded forward and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-13980WaymoSource file ↗Property damage only2026-02NHTSAWaymoPhoenix30270-14141Pickup Truck · struck on the front right · stopped
- Crash With
- Pickup Truck
- 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
- Investigating Agency
- Phoenix Fire 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 February [XXX], 2026 at 6:55 PM 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 stopped facing east in the second from 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 pickup truck initially stopped directly in front of the Waymo AV reversed, and the rear of the pickup truck 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-14141WaymoSource file ↗Property damage only2026-02NHTSAWaymoLos Angeles30270-14029struck on the front right · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 28
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On February [XXX], 2026 at 3:26 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Culver City, California was in a collision involving a tree branch on [XXX] near [XXX]. The Waymo AV was traveling northeastbound in the second from the right lane on [XXX] when a tree branch broke off and fell onto the Waymo AV, making contact with the hood and windshield 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-14029WaymoSource file ↗Property damage only2026-02NHTSAAvrideDallas31101-14236SUV · 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
- HYUNDAI
- Model
- Ioniq 5
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 February [XXX], 2026 at 3:40 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was facing northwest on [XXX] in autonomous mode while stopped at the red light at the intersection with [XXX]. When the light turned green, the AVRIDE AV did not proceed forward because an SUV was blocking the path straight ahead. While the AVRIDE AV stayed stopped, a pickup truck behind the AVRIDE AV began to drive forward. This movement caused the front of the pickup truck to make contact with the rear of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported.
cause not established31101-14236AvrideSource file ↗