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
785 records match
6 death reports20267 registriesClear
Narrow it down
What happened
Country
Year
Not graded by the source2026-02NHTSAWaymoScottsdale30270-13955Passenger Car · struck on the left · changing lanes
- Crash With
- Passenger Car
- SV Pre-Crash Movement
- Changing Lanes
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 56
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Highway / Freeway
- Weather
- Clear
- Investigating Agency
- Arizona Department of Public Safety
- 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:09 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane. A passenger car traveling northbound in the second to the left lane, in front of and to the left of the Waymo AV, began to slow and change lanes to the right when a second passenger car made contact with the rear right side of the first passenger car. The second passenger car continued forward and made contact with an SUV stopped in the queue of traffic in the second from the left lane. As a result of the initial contact with the second passenger car, the first passenger car was pushed east across two lanes of travel, and entered the Waymo AV's lane of travel. The Waymo AV slowed and maneuvered to the right to avoid the oncoming passenger car and the front left side of the passenger car made contact with the left side of the Waymo AV. The Waymo AV rotated to the left and came to rest facing southwest in the second and third from the left lanes. During two subsequent maneuvers in which the Waymo AV pulled forward and to the right in an attempt to navigate off the freeway, the front left corner of the Waymo AV made contact with an "Oversized Load" sign attached to a heavy truck stopped in the second from the left lane. At the time of all impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage. The driver of the first passenger car was transported to a hospital by an ambulance with unknown injuries, and the passenger of the Waymo AV alleged minor injuries. 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-13955WaymoSource file ↗Property damage only2026-02NHTSAWaymoAustin30270-13982struck on the rear left, front 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, Front Left
- 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
- 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 2:19 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a flat wooden object on [XXX] near [XXX]. The Waymo AV was traveling southeastbound on [XXX] when the front right and rear right tires of the Waymo AV made contact with a flat wooden object that was laying in the roadway. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 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-13982WaymoSource file ↗Property damage only2026-02NHTSAWaymoAustin30270-14149Passenger 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 February [XXX], 2026 at 8:41 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing northwest in the left lane on [XXX] at a green light at the intersection with [XXX]. While the light remained green, the Waymo AV proceeded forward into the intersection then slowed to a stop, and 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. 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-14149WaymoSource file ↗Not graded by the source2026-01-30FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00033ExcelsiusGPS
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 WHEN DOING AN SI JOINT FUSION WITH OUR SURGEON, OUR MERGE SEEMED TO BE GOOD. HOWEVER, UPON STARTING THE FIRST SCREW, THE HIGHSPEED DRILL WAS NOTICEABLY DEEPER THAN ITS ACTUAL DEPTH. WE TRIED TO FIX IT AND WHEN STANDARD TROUBLE SHOOTING WAS DONE NOTHING CHANGED BUT THE SURGEON WANTED TO PROCEED. THE SCREW PLACED WAS POSTERIOR AND INFERIOR TO THE PLAN. WE DECIDED TO COMPLETELY REMERGE. SIMILAR SHOTS WERE TAKEN AND THE SCREWS WERE PLACED TO PLAN WITH NO DEPTH ISSUES.
cause not established3004142400-2026-00033Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2026-01-29FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00035ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM, PEDICLE SCREWS WERE NOT PLACED AS PLANNED WITH THE E3D INTRAOP EXCELSIUS CASE.
cause not established3004142400-2026-00035Globus MedicalExcelsiusGPSRead the record ↗Death reported2026-01-29FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-14792da Vinci Surgical System
da Vinci Surgical System — Death report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT AFTER A DA VINCI-ASSISTED SINGLE-PORT UNSPECIFIED ¿HEAD AND NECK¿ SURGICAL PROCEDURE, THE PATIENT DEVELOPED A POSTOPERATIVE HEMORRHAGE AND ULTIMATELY EXPIRED. THE SURGEON INFORMED THE INTUITIVE CLINICAL SALES REPRESENTATIVE THAT THE ROBOTIC PROCEDURE WAS COMPLETED WITHOUT ANY INTRAOPERATIVE COMPLICATIONS; HOWEVER, THE PATIENT DEVELOPED POST-OPERATIVE COMPLICATIONS DUE TO UNSPECIFIED BLEEDING FROM THE NON-SPECIFIC PROCEDURE. NO ADDITIONAL EVENT INFORMATION WAS PROVIDED. THE SURGEON STATED THAT THE ADVERSE EVENT ¿HAD NOTHING TO DO WITH THE DA VINCI SP SYSTEM¿. ATTEMPTS TO OBTAIN ADDITIONAL INFORMATION FROM THE SURGEON WERE MADE; HOWEVER, NO RESPONSE WAS RECEIVED.
cause not established2955842-2026-14792Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-01-27FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00026ExcelsiusGPS
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 THE SURVEILLANCE HAS BEEN UNABLE TO HOLD GREEN STATUS AND DRIFTS TO YELLOW AND RED CONSTANTLY FOR THE LAST SEVERAL WEEKS. TODAY ANOTHER SCREW WAS PLACED LATERAL TO THE PEDAL SIMILAR TO WHAT HAPPENED TWO WEEKS AGO ON THE SAME UNIT EXHIBITING THE SAME PROBLEMS. THIS HAPPENED ONE OTHER TIME A FEW WEEKS EARLIER. THE SURGEON REMOVED THE BREACHED SCREW AND REPLACED USING TRADITIONAL NON-ROBOTIC/NAVIGATED MANNER. THE SURGEON HAS PUT OVER A THOUSAND SCREWS IN WITH THE ROBOT AND THIS IS THE SECOND TIME THIS HAS HAPPENED IN THE LAST TWO WEEKS WITH THE SAME UNIT EXHIBITING THE SAME ISSUE.
cause not established3004142400-2026-00026Globus MedicalExcelsiusGPSRead the record ↗Death reported2026-01-26FDA MAUDEIntuitive Surgical, Inc.da Vinci Surgical System2955842-2026-05349da Vinci Surgical System
da Vinci Surgical System — Death 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 LOBECTOMY PROCEDURE, AN INADVERTENT PERFORATION OF THE PULMONARY ARTERY OCCURRED WHILE USING A THIRD-PARTY LAPAROSCOPIC STAPLER INSTRUMENT, RESULTING IN SIGNIFICANT HEMORRHAGE AND THE PATIENT ULTIMATELY EXPIRED. THE EXACT VOLUME OF BLOOD LOSS IS UNKNOWN. THE SURGEON DOES NOT BELIEVE THAT THE DA VINCI SYSTEM, INSTRUMENTS, OR ACCESSORIES CAUSED OR CONTRIBUTED TO THE EVENT. ADDITIONAL INFORMATION WAS REQUESTED, BUT THE CUSTOMER HAS INDICATED THAT THEY WILL NOT GRANT PERMISSION FOR FURTHER ACCESS TO THE EVENT INFORMATION.
cause not established2955842-2026-05349Intuitive Surgical, Inc.da Vinci Surgical SystemRead the record ↗Not graded by the source2026-01-23FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00031ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE E3D TO PRE OP MERGE, NAVIGATION LOOKED CORRECT BUT UPON TAKING X-RAYS, NAVIGATION WAS OFF A SIGNIFICANTLY ANTERIORLY. THE DISC PREP THAT WAS DONE BASED OFF THE GPS NAVIGATION ON THE ROBOT RESULTED IN VIOLATING THE INFERIOR ENDPLATE OF THE SUPERIOR VERTEBRAL BODY, WHICH CAUSE THE SABLE CAGE TO SUBSIDE. ON THE NAVIGATION, THE CAGE LOOKED LIKE IT WAS WELL WITHIN THE DISC SPACE, BUT UNDER X-RAY IT WAS CLEARLY NOT. WE TRIED TO RE-PLACE THE CAGE BUT HAD THE SAME RESULT.
cause not established3004142400-2026-00031Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2026-01-20FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00023ExcelsiusGPS
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 IN AN EXCELSIUS GPS SURGERY, IT WAS NOTICED THAT AFTER TAKING X-RAYS IN THE OR FOR THE PRE OP CT WORKFLOW AND DOING THE MERGE, THE PLANNED SCREWS WERE TOTALLY WRONG IN THE X-RAY. WE TOOK THEM OUT TO BE NOT HASSITATED. WHEN WE PLACED THE FIDUCIALS INTO THE LATERAL VIEW VERTEBRA, THE AP ONES WERE COMPLETELY OFF AND NEEDED TO BE PLACED IN THE CENTRE. THEN WE HAD AN ANATOMICAL SHIFT IN LATERAL VIEW. WE COULD NOT CHOOSE ALL THE DIFFERENT VIEWS LIKE STANDARD OR STANDARD OPTIMIZED OR L2 SEED AUTOMATICALLY.
cause not established3004142400-2026-00023Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2026-01-16FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00024ExcelsiusGPS
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 DURING AN EXCELSIUS GPS SURGERY THE ROBOT WOULD NOT START. IT TURNED ON, BUT THE SCREEN WAS BLACK. THIS HAPPENED TWICE. THE THIRD TIME IT STARTED WITHOUT ANY PROBLEMS. IT UNDOCKED ITSELF DURING THE OPERATION. WE DOCKED IT MANUALLY AND CONTINUED THE OPERATION. EVERYTHING WENT WELL. HOWEVER, AFTER THE INTRAOPERATIVE CT SCAN, 3 OUT OF 8 SCREWS WERE INCORRECTLY INSERTED. WE CLOSED THE CASE IN THE ROBOT AND STARTED A NEW ONE AS IF IT WERE A NEW OPERATION. WE DID A 3D SCAN AGAIN, PLANNED THE SCREWS AND INSERTED THEM. EVERYTHING WENT WELL AND AFTER THE CONTROL SCAN THE SCREWS WERE ALREADY INSERTED CORRECTLY. THE PATIENT DID NOT SUFFER ANY HARM.
cause not established3004142400-2026-00024Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2026-01-15FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00039ExcelsiusGPS
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 DURING A L1-L5 OPEN TLIF, USING INTEROP WORKFLOW WITH E3D. WE PLACED L1 LEFT SCREW FIRST. THEN CHECKED ALL SCREWS WITH FLUORO AFTER THEY WERE ALL PLACED AND BOTH L1 SCREWS WERE SHIFTED TO THE LEFT. WE THEN WENT IN TO FIX THEM AND DID ANOTHER SPIN, AND IT WAS STILL OFF. WE ENDED UP PLACING BOTH TOP SCREWS FREEHAND WITHOUT NAVIGATION.
cause not established3004142400-2026-00039Globus MedicalExcelsiusGPSRead the record ↗Property damage only2026-01-15Press recordsCoco Robotics
the robot "experienced a rare hardware failure while crossing railroad tracks"
cause not establishedCoco RoboticsRead the record ↗Not graded by the source2026-01-08FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2026-00013ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT WHILE USING THE EXCELSIUS GPS SYSTEM ROBOT-PLANNED SCREWS WERE NOT ACCURATE. THE PLAN AND MERGER LOOK FINE. I CAN MAIL OR TRANSFER THE FILE LOG FROM THE ROBOT.
cause not established3004142400-2026-00013Globus MedicalExcelsiusGPSRead the record ↗Property damage only2026-01NHTSAWaymoAustin30270-13636Bus · struck on the rear · parked
- Crash With
- Bus
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Rain
- Investigating Agency
- Texas University 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 January [XXX], 2026 at 9:06 AM 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 parked facing south on [XXX], partially in the parking lane and partially in the rightmost lane, with its hazard lights activated for a passenger drop-off. While the Waymo AV was stopped, a bus traveling southbound on [XXX] in the rightmost lane proceeded to pass to the left of the parked Waymo AV. As the bus was passing the Waymo AV, a passenger in the Waymo AV opened the rear left door and the right side of the bus 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. The Waymo AV sustained damage. The two passengers in the Waymo AV were not belted at the time of the collision as they were exiting the vehicle. 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-13636WaymoSource file ↗Property damage only2026-01NHTSATeslaAustin13781-13646struck on the bottom · backing
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Backing
- SV Contact Area
- Bottom
- SV Precrash Speed (MPH)
- 2
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- Weather
- Clear
- Investigating Agency
- None
- Make
- TESLA
- Model
- Model Y
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
Summary: This updated report does not report a new incident or make any material changes to the factual record. It only removes confidential or personally identifying information to make the incident narrative publicly available. The Tesla ADS was reversing in a parking lot. As the ADS was reversing into an empty parking space, the ADS's right rear tire made contact with a corner of a curb. Safety monitor was present and no passengers were inside the vehicle.
cause not established13781-13646TeslaSource file ↗Property damage only2026-01NHTSAWaymoPhoenix30270-13786SUV · struck on the rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On January [XXX], 2026 at 5:45 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX] off-ramp. The Waymo AV was stopped facing north on [XXX] in the third from the right lane for a red light at the intersection with State Route [XXX]off-ramp. While the Waymo AV was stopped, an SUV traveling northbound on [XXX] in the third from the right lane 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. 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-13786WaymoSource file ↗Property damage only2026-01NHTSAWaymoSan Francisco30270-13783Passenger 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)
- 10
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On January [XXX], 2026 at 12:45 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] in the second to the left designated left turn lane as it approached a green light at the intersection with [XXX]. As the Waymo AV entered the intersection with [XXX] and initiated a left turn, a passenger car that was traveling in the adjacent leftmost designated left turn lane began to proceed straight as it entered the intersection with [XXX] and crossed the dashed white lane line into the Waymo AV's lane of travel. The right side of the passenger car made contact with the front 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-13783WaymoSource file ↗Property damage only2026-01NHTSAWaymoAustin30270-13769Passenger 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)
- 23
- CP Pre-Crash Movement
- Making Left Turn
- 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.
On January [XXX], 2026 at 11:22 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on [XXX] when it approached the exit of a parking garage at [XXX]. As the Waymo AV proceeded forward, a passenger car proceeded to exit the parking garage and, without stopping, initiated a left turn onto [XXX] and entered the Waymo AV's lane of travel. The front right side of the passenger car then 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-13769WaymoSource file ↗Property damage only2026-01NHTSAWaymoSan Francisco30270-13925Passenger Car · struck on the front · stopped
- Crash With
- Passenger Car
- 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
- Crossing into Opposing Lane
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On January [XXX], 2026 at 2:50 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 on [XXX] in the left lane in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV that was stopped facing northwest near the east curb of [XXX] began to maneuver to the left in preparation to enter northbound traffic on [XXX]. The SUV merged into the northbound lane as a passenger car traveling northbound on [XXX] was adjacent to the SUV on the left. The passenger car maneuvered to the left to avoid the SUV and crossed the double yellow lane line, and the front left side of the passenger car 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 availa
cause not established30270-13925WaymoSource file ↗Property damage only2026-01NHTSAWaymoSunnyvale30270-13810Passenger 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 January [XXX], 2026 at 7:07 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Sunnyvale, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southwestbound in the second from the right lane on Fair Oaks Avenue when it began to slow for a red light at the intersection with [XXX]. As the Waymo AV continued slowing, a passenger car traveling southwestbound on [XXX] in the same lane as 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-13810WaymoSource file ↗Property damage only2026-01NHTSAWaymoLos Angeles30270-13861Passenger Car · struck on the front left, right
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Other, see Narrative
- SV Contact Area
- Front Left, Right
- SV Precrash Speed (MPH)
- 12
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Rear
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Los Angeles Police Department
- 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 January [XXX], 2026 at 11:02 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving multiple vehicles on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it maneuvered to the right and came to a stop near the curb, perceiving that there may be insufficient clearance to traverse past the vegetation on the left of the roadway ahead. The test driver then transitioned the Waymo AV to manual mode by pressing the accelerator pedal, steered to the left to reenter the lane of travel and accelerated, and the front right of the Waymo AV made contact with the rear left of a passenger car that was parked at the curb. The test driver then continued to accelerate, resulting in the vehicle travelling down a hill, making contact with vegetation to the left of the roadway and three parked vehicles: the open door of a parked passenger car, the left side of an SUV, and the rear of another SUV. 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. All involved 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-13861WaymoSource file ↗Minor injury2026-01NHTSAWaymoSanta Monica30270-13850Non-Motorist: Pedestrian · struck on the front right · proceeding straight
- Crash With
- Non-Motorist: Pedestrian
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 6
- CP Pre-Crash Movement
- NM Crossing Roadway
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Santa Monica 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 January [XXX], 2026 at 8:28 AM a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a pedestrian on [XXX] near [XXX]. The Waymo AV was proceeding northwestbound on [XXX], with vehicles stopped in the opposing lane of travel to the left of the Waymo AV. As the Waymo AV was approaching an SUV in the southwestbound travel lane, a pedestrian emerged from behind the SUV to cross [XXX], entering the Waymo AV's lane of travel. The Waymo AV applied hard braking, and the front of the Waymo AV made contact with the pedestrian. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The pedestrian reported minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vulnerable road user was struck by an involved vehicle. Waymo may supplement or correct its reporting with additional information as it may become available..
cause not established30270-13850WaymoSource file ↗Property damage only2026-01NHTSAWaymoBeverly Hills30270-13770Passenger 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
- Proceeding Straight
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Beverly Hills 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 January [XXX], 2026 at 11:11 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Beverly Hills, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped in the left lane facing northeast on [XXX] in a queue of traffic for the intersection with [XXX]. While the Waymo AV was stopped, a passenger car traveling northeastbound on [XXX] at a high rate of speed approached the Waymo AV from behind. The passenger car maneuvered to the left towards the curb as it approached the Waymo AV, and the front 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. Three of the passengers in the Waymo AV were 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-13770WaymoSource file ↗Minor injury2026-01NHTSAWaymoSan Francisco30270-13852Passenger Car · struck on the rear right · making right turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 3
- 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 January [XXX], 2026 at 2:24 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] for a red light at the intersection with [XXX] with its right turn signal activated. After the light turned green and traffic cleared, the Waymo AV proceeded forward to initiate the right turn. As the Waymo AV entered the intersection, it began to yield to pedestrians crossing [XXX] from the north side of the street in the marked crosswalk. As 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. The passenger in the Waymo AV alleged 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-13852WaymoSource file ↗Property damage only2026-01NHTSAWaymoLos Angeles30270-13560Passenger 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 January [XXX], 2026 at 4:28 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] and came to a stop at a red light in the dedicated right turn lane at the intersection with [XXX]. The Waymo AV proceeded from the stop line, 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. 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-13560WaymoSource file ↗Property damage only2026-01NHTSAWaymoSan Francisco30270-13607struck 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)
- 20
- 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 January [XXX], 2026 at 2:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a traffic cone on [XXX] near [XXX]. The Waymo AV was traveling northwestbound on [XXX] in the right lane when it slowed to a stop for 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 proceeded forward. A pickup truck traveling northwestbound on [XXX] in the left lane proceeded forward and a rear seat passenger of the pickup truck threw a traffic cone from the window and into the roadway, and the traffic cone landed in the Waymo AV's lane of travel. As the Waymo AV proceeded forward the front of the Waymo AV made contact with the traffic cone. 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-13607WaymoSource file ↗Property damage only2026-01NHTSAWaymoLos Angeles30270-13905Passenger Car · struck on the front right · 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 Right
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- 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 January [XXX], 2026 at 7:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing north on [XXX] with its left turn signal activated preparing to make an unprotected left turn onto [XXX]. While the Waymo AV remained stopped, yielding to eastbound and westbound traffic with the front of the Waymo AV partially in the rightmost lane of eastbound [XXX] a bus traveling eastbound on [XXX] in the rightmost lane began to slow as it approached the Waymo AV to the left. The Waymo AV proceeded forward momentarily into the intersection and came to a stop, and the bus came to a stop in its lane of travel. The Waymo AV then proceeded forward to pass in front of the bus in preparation to turn left and began to yield. As the Waymo AV continued to yield, a passenger car traveling eastbound on [XXX] in the left lane emerged from behind the stopped bus, and the front right side of the passenger car made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-13905WaymoSource file ↗Property damage only2026-01NHTSAWaymoSan Francisco30270-13848Pickup Truck · struck on the front · stopped
- Crash With
- Pickup 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
- Backing
- CP Contact Area
- Rear 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 January [XXX], 2026 at 6:59 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] when it slowed to a stop to yield to a pickup truck stopped facing north in the lane of travel. The Waymo AV momentarily proceeded forward and began to slow to a stop. At the same time, the pickup truck reversed, and the rear right side of the pickup truck made contact with the front 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-13848WaymoSource file ↗Property damage only2026-01NHTSAWaymoLos Angeles30270-13762Passenger Car · struck on the front · passing
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Passing
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 6
- CP Pre-Crash Movement
- Stopped
- 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 January [XXX], 2026 at 7:37 AM 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 stopped facing southwestbound on a narrow portion of [XXXX], yielding to a passenger car stopped at the curb in front of and to the left of the Waymo AV. While the passenger car was stopped, the Waymo AV slowly proceeded forward and to the right. The passenger car proceeded forward along the curb and slowed to a stop, and the Waymo AV proceeded to pass the passenger car to the right. While the Waymo AV was passing the passenger car, a passenger in the passenger car opened the front right door, and the open front right door made contact with the front 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 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13762WaymoSource file ↗Property damage only2026-01NHTSAWaymoPhoenix30270-13979Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On January [XXX], 2026 at 9:57 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] for a red light at the intersection with [XXX] with its left turn signal activated. When the light turned green the Waymo AV proceeded forward and stopped to yield to oncoming northbound traffic on [XXX], waiting to make an unprotected left turn at the intersection at [XXX]. While the Waymo AV was stopped, a passenger car that was initially stopped behind the Waymo AV approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV'sLevel 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-13979WaymoSource file ↗Property damage only2026-01NHTSAWaymoLos Angeles30270-13948SUV · 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
- 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 January [XXX], 2026 at 9:00 AM 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 stopped facing northeast on [XXX] in the second from the right lane in a queue of traffic for a red light at the intersection with [XXX] when a pedestrian approached the stationary Waymo AV and making contact with the front right sensor, causing the Waymo AV to remain stopped in lane. While the Waymo AV was stopped, an SUV that was stopped directly behind the Waymo AV proceeded to change lanes to the left lane 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. 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-13948WaymoSource file ↗Property damage only2026-01NHTSAWaymoTempe30270-13551SUV · struck on the rear · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On January [XXX], 2026 at 4:48 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 northbound on [XXX] in the designated left turn lane, in autonomous mode with its left turn signal activated and began to slow as it approached a yellow light at the intersection with [XXX]. As the Waymo AV approached the intersection, the test driver transitioned the Waymo AV to manual mode. An SUV traveling northbound on [XXX] in the adjacent lane behind and to the right of the Waymo AV proceeded to change lanes. The SUV approached the Waymo AV from behind, and began to maneuver to the left, and the front right side 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 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-13551WaymoSource file ↗Property damage only2026-01NHTSAWaymoSunnyvale30270-13869SUV · struck on the rear right · backing
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Backing
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 3
- 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 January [XXX], 2026 at 6:10 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Sunnyvale, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in autonomous mode on [XXX] when it came to a stop on a hill and then began reversing into a vacant parallel parking space in front of a parked SUV. The Waymo AV transitioned to manual mode and briefly rolled backwards at a low speed, and the rear of the Waymo AV made contact with the front of the parked SUV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and the Waymo AV was in manual mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13869WaymoSource file ↗No injury reported2026-01NHTSAAurora InnovationEl Paso30530-14071struck on the front left · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 55
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Highway / Freeway
- Weather
- 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 5:03 PM CDT on January [XXX], 2026 in El Paso, Texas, an Aurora vehicle was traveling east on [XXX] at approximately 55 MPH during a development mission. The Aurora vehicle was in autonomy. The Aurora vehicle was traveling straight in its lane. A pickup truck was present ahead. A loose object from the pickup truck struck the Aurora vehicle. After impact, the vehicle operator elected to disengage autonomy and returned to the Aurora terminal. The Aurora vehicle was driveable from the location. No injuries were reported. The Aurora vehicle sustained damage. Aurora will supplement or modify its reporting should additional relevant information become available.
cause not established30530-14071Aurora InnovationSource file ↗Property damage only2026-01NHTSAWaymoLos Angeles30270-14025SUV · struck on the rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- 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 January [XXX], 2026 at 6:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing northeast on [XXX] in the third from the right lane for a red light at the intersection with [XXX]. When the light turned green, the Waymo AV proceeded a short distance and then slowed down before entering the intersection to yield to an active emergency vehicle traveling northeastbound on [XXX] against the proper direction of traffic with its emergency lights activated. While the Waymo AV was stopped, an SUV that was initially stopped directly behind the Waymo AV proceeded forward, and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-14025WaymoSource file ↗Property damage only2026-01NHTSAWaymoSan Francisco30270-13623Pickup 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
- 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 January [XXX], 2026 at 10:22 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southeastbound in the second to the right lane on [XXX] when it changed lanes to the rightmost lane and slowed to a stop to yield to a pickup truck that was stopped facing southeast in the Waymo AV's lane of travel. While the Waymo AV was stopped, the pickup truck reversed, came to a stop, and then reversed again, 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. 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-13623WaymoSource file ↗Property damage only2026-01NHTSAAvrideDallas31101-14069Passenger 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)
- 16
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Right
- 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 January [XXX], 2026 at 2:34 PM, 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. Uber passengers were present in the AVRIDE AV. No injuries were reported. both vehicles sustained damage. The ride was cancelled.
cause not established31101-14069AvrideSource file ↗Property damage only2026-01NHTSAWaymoSan Francisco30270-13799Heavy 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
- 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 January [XXX], 2026 at 11:29 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 stopped facing west at the north curb, on a narrow portion of [XXX] for a passenger pick-up. While the Waymo AV was stopped, a box truck traveling eastbound on [XXX] passed the Waymo AV to the left, and the left side of the box 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-13799WaymoSource file ↗Property damage only2026-01NHTSAWaymoMesa30270-13565struck on the front 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
- Front Left
- SV Precrash Speed (MPH)
- 65
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Highway / Freeway
- 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 January [XXX], 2026 at 7:07 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was in a collision involving a trash can on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in the rightmost lane. An SUV that was traveling westbound on [XXX] ahead of the Waymo AV in the second from the right lane made contact with a trash can that was in the roadway. The trash can deflected off the SUV and rolled across the roadway into the Waymo AV's lane of travel, and the trash can made contact with the front right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-13565WaymoSource file ↗Property damage only2026-01NHTSAZooxSan Francisco30610-13662Heavy Truck · struck on the front left, front right · stopped
- Crash With
- Heavy Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Left, Front Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear, Rear 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 unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling east on [XXX] near [XXX] in San Francisco. It began to slow down for a stopped box truck (Vehicle 2) in the same lane, which had an open liftgate. As the Zoox vehicle was preparing to maneuver around, Vehicle 2 began to reverse. The Zoox vehicle came to a stop however, Vehicle 2 continued reversing. The Zoox vehicle honked, but Vehicle 2's open liftgate made contact with the right front fender and front fascia of the Zoox vehicle. The Zoox vehicle was towed from the scene and was found to have sustained minor damage. The police were notified, and no injuries were reported.
cause not established30610-13662ZooxSource file ↗Property damage only2026-01NHTSAWaymoVenice30270-13582Passenger 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)
- 11
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On January [XXX], 2026 at 6:38 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Venice, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southwestbound on [XXX] when it came to a stop for a stop sign at the intersection with [XXX] as a passenger car slowed near the stop sign on eastbound [XXX]. After stopping, the Waymo AV began to enter the intersection at a slow speed as an SUV traveling northbound on [XXX] executed its left turn onto [XXX]. As the Waymo AV was proceeding through the intersection, the passenger car continued through the stop sign on [XXX] without coming to a complete stop and began accelerating into the intersection. The Waymo AV began to maneuver to the left to avoid the oncoming passenger car. The passenger car continued to proceed forward, and the front right 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-13582WaymoSource file ↗Property damage only2026-01NHTSAWaymoSan Francisco30270-13571Van · struck on the rear · stopped
- Crash With
- Van
- 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 January [XXX], 2026 at 6:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was parked in-lane facing west on [XXX] with hazard lights activated for a passenger pick-up. While the Waymo AV remained parked, a van that was initially stopped directly behind the Waymo AV proceeded to pass the Waymo AV to the left, and the right side of the van 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-13571WaymoSource file ↗Not graded by the source2026-01-01FDA MAUDEDePuy SynthesVELYS™ Robotic-Assisted Solution1818910-2026-12358VELYS
VELYS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THE SURGEON BELIEVED A DISTAL FEMUR FRACTURE MAY HAVE BEEN CAUSED BY BICORTICAL VELYS ARRAY PINS, WHICH CREATED A STRESS RISER. HE STATED THAT HE PLANNED TO PLACE PINS MORE DISTALLY AND UNICORTICALLY PER VELYS RAS STANDARD PIN PLACEMENT. ONE PATIENT WAS TREATED NONOPERATIVELY. ONE PATIENT WAS TREATED WITH A RETROGRADE NAIL. AS STATED IN THE REPORT, LOT NUMBERS WERE NOT AVAILABLE. PINS WERE DISCARDED AT THE CONCLUSION OF THE SURGERY. THE FRACTURES OCCURRED AT A LATER TIME. THERE WAS NO SIGNIFICANT DELAY. ALL AVAILABLE INFORMATION HAS BEEN DISCLOSED.
cause not established1818910-2026-12358DePuy SynthesVELYS™ Robotic-Assisted SolutionRead the record ↗Property damage only2026-01NHTSAWaymoLos Angeles30270-13556Pickup Truck · struck on the rear · stopped
- Crash With
- Pickup 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
- Passing
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On January [XXX], 2026 at 4:24 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing north, partially on the double yellow lane line, on a narrow portion of [XXX] with vehicles parked at the curb in both directions, for a red traffic light at the intersection with [XXX]. While the Waymo AV was stopped, a pickup truck traveling eastbound in the right lane on [XXX] proceeded to turn right onto [XXX]. As the pickup truck passed the stationary Waymo AV the front left side of the pickup 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. 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-13556WaymoSource file ↗Property damage only2026-01NHTSAWaymoSan Francisco30270-13641Bus · struck on the rear · stopped
- Crash With
- Bus
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- 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 January [XXX], 2026 at 7:31 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 traveling northwestbound on [XXX] in the second from the right lane with its right turn signal activated to change lanes to the designated right turn lane. While changing lanes, the Waymo AV slowed to a stop, partially in the designated right turn lane and partially in the commencement of the bus lane, to yield to a queue of traffic in the designated right turn lane. A bus initially stopped behind the Waymo AV began to pass to the left side of the Waymo AV. As the bus was passing the Waymo AV the right side of the bus 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-13641WaymoSource file ↗No injury reported2026-01NHTSAAvrideDallas31101-13761Pickup Truck · struck on the right · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 30
- CP Pre-Crash Movement
- Entering Traffic
- CP Contact Area
- Front
- 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 January [XXX] at approximately 2:15 p.m., an AVRIDE autonomous vehicle (the AVRIDE AVâ) was involved in a collision in Dallas, Texas, on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in the right lane with autonomous mode engaged when it approached a pickup truck exiting a parking lot on the right side of the roadway. The pickup truck entered the roadway without stopping or yielding, cutting off the AVRIDE AV and contacting the right side of the AVRIDE AV with the pickup truckâs front-left area. The AVRIDE AVâs airbags deployed and the vehicle required towing. Both vehicles sustained damage. No injuries were reported.
cause not established31101-13761AvrideSource file ↗Property damage only2026-01NHTSAWaymoPhoenix30270-13653SUV · struck on the rear left · stopped
- Crash With
- SUV
- 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
- 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 January [XXX], 2026 at 11:39 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] in the left lane for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling southbound on [XXX] in the left lane approached the Waymo AV from behind and maneuvered to the right in lane, and the front left side of the SUV made contact with the rear 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-13653WaymoSource file ↗Property damage only2026-01NHTSAWaymoLos Angeles30270-13650Motorcycle · struck on the front left · proceeding straight
- Crash With
- Motorcycle
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 14
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
On January [XXX], 2026 at 1:53 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was traveling southeastbound on [XXX] in the left lane and proceeding straight through the intersection with [XXX] at a green light. As the Waymo AV was exiting the intersection, a motorcycle traveling northwestbound on [XXX] in the designated left turn lane began to execute a left turn towards a parking lot at the southwest curb by crossing the double yellow line. As the motorcycle executed this left turn, it emerged from behind a pickup truck stopped in the queue of traffic in the designated left turn lane, entered the Waymo AV's lane of travel, and began to slow. The Waymo AV braked and began to maneuver to the left to yield to the motorcycle, and the front right side of the Waymo AV made contact with the right side of the motorcycle. 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-13650WaymoSource file ↗Property damage only2026-01NHTSAWaymoDenver30270-13816Pickup Truck · struck on the front right · parking maneuver
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Parking Maneuver
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 6
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Rear 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 January [XXX], 2026 at 1:18 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Denver, Colorado was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound through a construction zone on [XXX] in autonomous mode when it began to maneuver to the right, towards the south curb. As the Waymo AV was maneuvering, the test driver transitioned the Waymo AV to manual mode. The test driver began maneuvering the Waymo AV closer to the curb, briefly accelerated forward, and then began braking. The front of the Waymo AV then made contact with the rear of a pickup truck that was parked facing east at the curb in 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-13816WaymoSource file ↗