The MachineRecord
NHTSA Standing General Order 2021-01

The SGO file, in a form you can search

NHTSA publishes the crash reports as three CSV files of 116 columns each, with several versions of the same report mixed in. This is the same data as one table: driverless systems (ADS) and Level 2 driver assistance side by side, 2021 to today including NHTSA's archive, one row per report at its latest version, every row traceable to its NHTSA report number. Free, CC BY 4.0, refreshed from NHTSA on every pipeline run.

Reports
8612
Fatal
87
Of them Level 2
79
Reporting entities
64
Incidents
2019-08 to 2026-09
Clear filters

1674 reports, showing 1401 to 1500.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
502-4026ADSFord Motor Company2022-09 10:23Miami, FL2020 Ford EscapeADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
540-4019 v3ADSGeneral Motors, LLC2022-09 05:14San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0Street
On September 26, 2024 GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the…On September 26, 2024 GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3978-3)
1306-4010ADSToyota Motor Engineering & Manufacturing2022-08 16:15Arlington, TX2020 Lexus RX450HADSPickup TruckNo Injuries Reported10Intersection
This report is being submitted because May Mobility notified Toyota on Sept. 8, 2022 of Monthly Report submission 1306-3355-1,related to an incident reported in July 2022. Toyota has no additional information on this inc…This report is being submitted because May Mobility notified Toyota on Sept. 8, 2022 of Monthly Report submission 1306-3355-1,related to an incident reported in July 2022. Toyota has no additional information on this incident beyond what was submitted in the aforementioned Monthly Report. Please refer to the report from May Mobility for details.
30270-3545 v2ADSWaymo LLC2022-08 10:25Tempe, AZ2017 Chrysler PacificaADSOther Fixed ObjectNo Injuries Reported18Intersection
The content of this report is unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 10:25 AM PST a Waymo Autonomous Vehicle…The content of this report is unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 10:25 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a road sign and crosswalk button post on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it passed [XXX]. As the Waymo AV was in the intersection of [XXX] and [XXX], and was approaching the right turn lane at the intersection of [XXX] and [XXX] and following the lane markings, the Waymo AV test driver transitioned the system to manual mode. The Waymo AV then made contact with the right curb on [XXX] as well as a road sign and a crosswalk button post located adjacent to the roadway. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor 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. This report was submitted from the Eastern time zone on the required date.
30270-3595 v2ADSWaymo LLC2022-08 03:09San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
The content of this report is unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 03:09 AM PST a Waymo Autonomous Vehicle…The content of this report is unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 03:09 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving an SUV on [XXX] at [XXX] The Waymo AV was traveling eastbound on [XXX] in autonomous mode when it slowed for a stop sign on [XXX]. As the Waymo AV slowed to almost a complete stop, an SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). 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. This report was submitted from the Eastern time zone on the required date.
30270-3837ADSWaymo LLC2022-08 11:03Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported45Street
On August [XXX], 2022 at 11:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XX…On August [XXX], 2022 at 11:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] and had passed [XXX] when a passenger vehicle approached the Waymo AV from behind. The passenger vehicle then made a lane change into its adjacent right lane, and passed the Waymo AV. As it passed the Waymo AV, the passenger vehicle made a lane change back into the left adjacent lane, and its driver side rear quarter panel made contact with the Waymo AV's passenger side front quarter panel. 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.
30270-3838ADSWaymo LLC2022-08 12:23Chandler, AZ2017 Chrysler PacificaADSPickup TruckNo Injuries Reported0Parking Lot
On August [XXX], 2022 at 12:23 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving a pick-up truck at [XXX]. The Waymo AV stopped in a parking lot to drop-off a pas…On August [XXX], 2022 at 12:23 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving a pick-up truck at [XXX]. The Waymo AV stopped in a parking lot to drop-off a passenger. Shortly after the Waymo AV pulled over, a pick-up truck that was parked perpendicular to the Waymo AV moved backward and its rear bumper made contact with the passenger side rear quarter panel of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and the passenger had just unbuckled their seat belt to deboard. 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.
30270-3841ADSWaymo LLC2022-08 23:30Phoenix, AZ2021 Jaguar I-PaceADSAnimalNo Injuries Reported23Street
On August [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a domestic dog on the 800 block of [XXX]. The Waymo AV was traveling eastbound on […On August [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a domestic dog on the 800 block of [XXX]. The Waymo AV was traveling eastbound on [XXX] when a domestic dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog and the dog died at the scene. 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). 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.
30270-3842ADSWaymo LLC2022-08 17:05San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On August [XXX], 2022 at 5:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While approaching a merge onto southbound [XXX] f…On August [XXX], 2022 at 5:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While approaching a merge onto southbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the left. While the Waymo AV was stopped, an SUV approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged. Both vehicles sustained minor 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.
30270-3843ADSWaymo LLC2022-08 18:08San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On August [XXX], 2022 at 6:08 PM PST 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 in traffic in…On August [XXX], 2022 at 6:08 PM PST 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 in traffic in the left-hand lane of [XXX], facing East. The passenger car that had been stopped behind the Waymo AV began moving forward. The front of the passenger car made contact with the rear of the Waymo AV. When the light turned green and traffic began moving, the passenger car left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-3844ADSWaymo LLC2022-08 03:52San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported2Intersection
On August [XXX], 2022 at 3:52 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling West on [XXX] and stopp…On August [XXX], 2022 at 3:52 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling West on [XXX] and stopped at the stop sign at the intersection with [XXX]. As the Waymo AV slowed to a stop, a SUV traveling in the opposite lane, East on [XXX], crossed the intersection with [XXX] and came to a stop in the opposite lane, next to the Waymo AV. After stopping, the SUV began moving again and the front left corner of the SUV made contact with the left side of the Waymo AV. The SUV then left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-3848ADSWaymo LLC2022-08 18:33Ennis, TX2021 Peterbilt 579 EpiqADSHeavy TruckNo Injuries Reported61Highway / Freeway
On August [XXX], 2022 at 6:33 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound…On August [XXX], 2022 at 6:33 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the middle lane on [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it began to execute a right lane change and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. 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.
30270-3851ADSWaymo LLC2022-08 00:06Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported10Street
On August [XXX], 2022 at 12:06 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle near [XXX]. The Waymo AV was traveling eastbound on [XXX] when i…On August [XXX], 2022 at 12:06 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it approached a passenger vehicle stopped along the right shoulder in the bike lane. As the Waymo AV passed the passenger vehicle, one of the passenger vehicle's driver side doors opened and made contact with the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-3852ADSWaymo LLC2022-08 18:15San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Intersection
On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came …On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came to a stop behind a double-parked vehicle in the right lane. Shortly after coming to a stop, a van approached from behind and made contact with the rear of the Waymo AV. The van then changed lanes and left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with Yadditional information as it may become available.
30290-3797ADSArgo AI2022-08 17:55Miami Beach, FL2020 Ford EscapeADSPickup TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30290-3800ADSArgo AI2022-08 12:31Miami, FL2020 Ford EscapeADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30310-3698ADSFirst Transit2022-08 16:23Rochester, MN2019 Ligier Group EZ10 Gen 3ADSSUVNo Injuries Reported0Intersection
Prior to the crash, on August [XXX], 2022 autonomous shuttle (MNCAV2, V005) for the Med City Mover was travelling southbound on [XXX]. in autonomous ADS mode. The vehicle was functioning normally prior to the event in au…Prior to the crash, on August [XXX], 2022 autonomous shuttle (MNCAV2, V005) for the Med City Mover was travelling southbound on [XXX]. in autonomous ADS mode. The vehicle was functioning normally prior to the event in autonomous mode. At 16:23 CT, the shuttle entered the intersection of [XXX] and [XXX]. The shuttle experienced an unknown e-stop. The vehicle behind the shuttle was following closely and attempting to pass the shuttle at this time and hit the rear left corner of the shuttle. No injuries reported to the two passengers on-board the shuttle or the operator or other vehicles two passengers. Seatbelts were used by the shuttle passengers at the time of the incident. 911 was called and the Minnesota Department of Public Safety was dispatched to file a report. Details of the event can be provided in video format, a police report and an operator summary. The GPX coordinates above are approximate at the time of the e-stop. The shuttle had experienced an unknown e-stop at 15:59 CT on [XXX] (no passengers).
30391-3678 v2ADSKodiak Robotics2022-08 18:00Palmer, TX2022 Kenworth Motor Truck Co T680ADSPickup TruckNo Injuries Reported15Highway / FreewayRedacted by NHTSA as confidential business information
30391-3808ADSKodiak Robotics2022-08 18:00Palmer, TX2022 Kenworth Motor Truck Co T680ADSPickup TruckNo Injuries Reported15Highway / FreewayRedacted by NHTSA as confidential business information
30412-3801ADSCruise LLC2022-08 07:04San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported14StreetRedacted by NHTSA as confidential business information
30413-3764ADSMay Mobility2022-08 16:15Arlington, TX2020 LExus RX450HADSPickup TruckNo Injuries Reported10Intersection
May Mobility vehicle is traveling westbound in autonomous mode on [XXX], stopped at a red light. When the traffic light turns green, the subject vehicle accelerates up to approximately 10mph. Approximately halfway throug…May Mobility vehicle is traveling westbound in autonomous mode on [XXX], stopped at a red light. When the traffic light turns green, the subject vehicle accelerates up to approximately 10mph. Approximately halfway through the intersection of [XXX], the subject vehicle begins to slow down due to construction fencing that is intruding into the lane, eventually coming to a complete stop. The safety operator takes over manual operation via the accelerator pedal, but is struck from the rear by a Toyota pickup that was following. The Toyota was first struck by the Chevy vehicle traveling behind it, pushing the Toyota into the subject vehicle.
30414-3650 v2ADSEasymile Inc.2022-08 16:23Rochester, MN2019 Ligier EZ10 Gen 3ADSSUVNo Injuries Reported0Intersection1- Day Report done in Error, Please delete this report
30414-3903ADSEasymile Inc.2022-08 16:23Rochester, MN2019 Ligier EZ10 Gen 3ADSSUVNo Injuries Reported0Intersection
Prior to the crash, on August [XXX], 2022 autonomous shuttle (MNCAV2, V005) for the Med City Mover was travelling southbound on [XXX]. in autonomous ADS mode. The vehicle was functioning normally prior to the event in a…Prior to the crash, on August [XXX], 2022 autonomous shuttle (MNCAV2, V005) for the Med City Mover was travelling southbound on [XXX]. in autonomous ADS mode. The vehicle was functioning normally prior to the event in autonomous mode. At 16:23 CT, the shuttle entered the intersection of [XXX] and [XXX]. The shuttle experienced an unknown e-stop. The vehicle behind the shuttle was following closely and attempting to pass the shuttle at this time and hit the rear left corner of the shuttle. No injuries reported to the two passengers on-board the shuttle or the operator or other vehicles two passengers. Seatbelts were used by the shuttle passengers at the time of the incident. 911 was called and the Minnesota Department of Public Safety was dispatched to file a report. Details of the event can be provided in video format, a police report and an operator summary. The GPX coordinates above are approximate at the time of the e-stop. The shuttle had experienced an unknown e-stop at 15:59 CT on [XXX] (no passengers).
30531-3546 v2ADSTransdev Alternative Services2022-08 10:25Tempe, AZ2017 Chrysler PacificaADSOther Fixed ObjectNo Injuries Reported18Intersection
The content of this report in unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 10:25 AM PST a Waymo Autonomous Vehicle …The content of this report in unchanged from the initial report submitted on August [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2022 at 10:25 AM PST a Waymo Autonomous Vehicle in Tempe, Arizona was in a collision involving a road sign and crosswalk button post on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it passed [XXX]. As the Waymo AV was in the intersection of [XXX] and [XXX], and was approaching the right turn lane at the intersection of [XXX] and [XXX] and following the land markings, the Waymo AV test driver transitioned the system to manual mode. The Waymo AV then made contact with the right curb on[XXX] as well as a road sign and a crosswalk button post located adjacent to the roadway. At the time of the impact, the Waymo Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle was towed. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of report ID 30270-345-1.
30531-3626 v2ADSTransdev Alternative Services2022-08 3:09San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
The content of this report is unchanged from the initial report submitted (30531-3626-1) On August [XXX] 2022 at 3:09 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision invol…The content of this report is unchanged from the initial report submitted (30531-3626-1) On August [XXX] 2022 at 3:09 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] in autonomous mode when it slowed for a stop sign on [XXX]. As the Waymo AV slowed to almost.a complete stop, an SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of report ID WaymoLLC-202208[XXX] (rev.202208[XXX]).
30531-3877ADSTransdev Alternative Services2022-08 11:03Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported45Street
On August [XXX], 2022 at 11:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle approached the Waymo AV from behind. The passenger vehicle then …On August [XXX], 2022 at 11:03 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle approached the Waymo AV from behind. The passenger vehicle then made a lane change into its adjacent right lane, and passed the Waymo AV. As it passed the Waymo AV, the passenger vehicle made a lane change back into the left adjacent lane, and its driver side rear quarter panel made contact with the Waymo AV's passenger side front quarter panel. 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. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is identical to WaymoLLC-202208[XXX]-0 (rev.202209[XXX]143732).
30531-3879ADSTransdev Alternative Services2022-08 23:30Phoenix, AZ2021 Jaguar I-PaceADSAnimalNo Injuries Reported23Street
On August [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a domestic dog on the 800 block of [XXX]. The Waymo AV was traveling eastbound on […On August [XXX], 2022 at 11:30 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a domestic dog on the 800 block of [XXX]. The Waymo AV was traveling eastbound on [XXX] when a domestic dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog and the dog died at the scene. 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). Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX-0 (rev.202209[XXX]162417).
30531-3880ADSTransdev Alternative Services2022-08 18:08San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On August [XXX], 2022 at 6:08 PM PST 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 in traffic in…On August [XXX], 2022 at 6:08 PM PST 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 in traffic in the left-hand lane of [XXX], facing East. The passenger car that had been stopped behind the Waymo AV began moving forward. The front of the passenger car made contact with the rear of the Waymo AV. When the light turned green and traffic began moving, the passenger car left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev.202209[XXX]205107).
30531-3881ADSTransdev Alternative Services2022-08 3:52San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported2Intersection
On August [XXX], 2022 at 3:52 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling West on [XXX] and stopp…On August [XXX], 2022 at 3:52 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling West on [XXX] and stopped at the stop sign at the intersection with [XXX]. As the Waymo AV slowed to a stop, a SUV traveling in the opposite lane, East on [XXX], crossed the intersection with [XXX] and came to a stop in the opposite lane, next to the Waymo AV. After stopping, the SUV began moving again and the front left corner of the SUV made contact with the left side of the Waymo AV. The SUV then left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev.202209[XXX]162446).
30531-3882ADSTransdev Alternative Services2022-08 18:33Ennis, TX2021 Peterbilt 579 EpiqADSHeavy TruckNo Injuries Reported61Highway / Freeway
On August [XXX], 2022 at 6:33 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound…On August [XXX], 2022 at 6:33 PM PST a Waymo Autonomous Vehicle ("Waymo AV") Peterbilt Class 8 semi-truck and trailer, operating in Ennis, Texas was in a collision involving a Class 8 semi-truck and trailer on northbound [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the middle lane on [XXX] when a Class 8 semi-truck and trailer began to pass it in the adjacent left lane. Before the adjacent Class 8 semi-truck and trailer had fully passed the Waymo AV, it began to execute a right lane change and its trailer (the right side, rear section) entered the lane in which the Waymo AV was traveling and made contact with the driver side of the Waymo AV cab. The Waymo AV transitioned to manual mode and the test driver took control. At the time of the impact, the Waymo AV's ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage and the third-party Class 8 semi-truck and trailer did not stop to exchange information. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev. 2022019[XXX]185808)
30531-3883ADSTransdev Alternative Services2022-08 00:06Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported10Street
On August [XXX], 2022 at 12:06 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it…On August [XXX], 2022 at 12:06 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle near [XXX]. The Waymo AV was traveling eastbound on [XXX] when it approached a passenger vehicle stopped along the right shoulder in the bike lane. As the Waymo AV passed the passenger vehicle, one of the passenger vehicle's driver side doors opened and made contact with the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev.202209[XXX]205246).
30531-3884ADSTransdev Alternative Services2022-08 18:15San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Intersection
On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came …On August [XXX], 2022 at 6:05 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] and came to a stop behind a double-parked vehicle in the right lane. Shortly after coming to a stop, a van approached from behind and made contact with the rear of the Waymo AV. The van then changed lanes and left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202208[XXX]-0 (rev.202209[XXX]162510).
30610-3719 v2ADSZoox, Inc.2022-08 21:20Las Vegas, CA2016 Toyota HighlanderADSNon-Motorist: PedestrianNo Injuries Reported2Parking Lot
A Zoox vehicle in autonomy was proceeding at approximately 2mph towards an exit of a private hotel driveway in Las Vegas, Nevada when it was struck on its right front fender by two individuals involved in an altercation …A Zoox vehicle in autonomy was proceeding at approximately 2mph towards an exit of a private hotel driveway in Las Vegas, Nevada when it was struck on its right front fender by two individuals involved in an altercation who had darted out from the side of the roadway. The right front fender of the Zoox vehicle was dented. The two individuals fled the scene and Zoox is not aware of any reported injuries. We question whether this interaction meets the reporting requirements nevertheless, we are submitting this report out of an abundance of caution. This 10-Day update provides complete information for this incident.
30610-3751ADSZoox, Inc.2022-08 21:01San Francisco, CA2016 Toyota HighlanderADSVanNo Injuries Reported0Street
A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, CA, in stop-and-go traffic. The Zoox vehicle came to a stop for a vehicle ahead when a following van made light contact with the Zoox vehicle'…A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, CA, in stop-and-go traffic. The Zoox vehicle came to a stop for a vehicle ahead when a following van made light contact with the Zoox vehicle's rear bumper from behind. There were no injuries and the police were not called.
502-3864ADSFord Motor Company2022-08 17:55Miami Beach, FL2020 Ford EscapeADSPickup TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
502-3866ADSFord Motor Company2022-08 12:31Miami, FL2020 Ford EscapeADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
540-3819ADSGeneral Motors, LLC2022-08 07:04San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported14Street
On September [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cru…On September [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3801-1)
988-3684 v2ADSPACCAR Incorporated2022-08 18:00Palmer, TX2022 Kenworth T680ADSPickup TruckNo Injuries Reported15Highway / Freeway
Monthly Report Update: A police report was issued after the original SGO incident reports were submitted and described the cause of the collision as the pick-up truck's failure to control its speed before rear-ending the…Monthly Report Update: A police report was issued after the original SGO incident reports were submitted and described the cause of the collision as the pick-up truck's failure to control its speed before rear-ending the Kodiak AV. The content of this report is otherwise unchanged from the initial incident report submitted on August [XXX], 2022. On August [XXX], 2022, Kodiak Robotics, Inc. ("Kodiak") filed an Incident Report (the "Report") under the Standing General Order 2021-01 (the "Order"). PACCAR, Inc. (Paccar) manufactured the Kodiak-operated motor vehicle involved in the incident summarized in the Incident Report. Because Paccar is also a Reporting Entity under the Order, Paccar is submitting a duplicate of the redacted public copy of the Report. Paccar has selected "Unknown" in the "ADS version" field solely to avoid the second submission of nonpublic Kodiak CBI. Paccar is in possession of Kodiak's response to this field and incorporates Kodiak's response into this submission by reference. Paccar's submission is based on facts supplied to Paccar by Kodiak. Paccar has not investigated the alleged incident and has no independent knowledge of the facts in the Report.
12381-3438 v2ADSDaimler Trucks North America, LLC2022-07 16:33ALBUQUERQUE, NM2021 FREIGHTLINER CascadiaADSOther, see NarrativeNo Injuries Reported58Highway / FreewayRedacted by NHTSA as confidential business information
12381-3557ADSDaimler Trucks North America, LLC2022-07 12:39Santa Rosa, NM2021 Freightliner CascadiaADSOther, see NarrativeNo Injuries Reported51Highway / FreewayRedacted by NHTSA as confidential business information
30270-3323 v2ADSWaymo LLC2022-07 15:26San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported3Intersection
The content of this report is unchanged from the initial report submitted on July [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 3:26 PM PST a Waymo Autonomous Vehicle (Way…The content of this report is unchanged from the initial report submitted on July [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2022 at 3:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it detected a siren from a nearby emergency vehicle. As the Waymo AV slowed, a passenger vehicle made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). 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. This report was submitted from the Eastern time zone on the required date.
30270-3625ADSWaymo LLC2022-07 10:08San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Parking Lot
On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]. The Waymo AV came to a stop whil…On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]. The Waymo AV came to a stop while yielding for an oncoming van in a narrow passageway in a parking lot. While attempting to pass the Waymo AV, the van made contact with the sensor housing on the left rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was stationary and engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor 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. This report was submitted from the Eastern time zone on the required date.
30270-3633ADSWaymo LLC2022-07 23:23San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported9Street
On July [XXX], 2022 at 11:23 PM PST 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 north on [XXX] i…On July [XXX], 2022 at 11:23 PM PST 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 north on [XXX] in the rightmost lane when a passenger car approached the Waymo AV from behind on the left. Just after passing the Waymo AV, the passenger car veered across the path of the Waymo AV into the entrance of a gas station on the right hand side of the roadway. The right rear corner of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor 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. This report was submitted from the Eastern time zone on the required date.
30270-3635ADSWaymo LLC2022-07 02:50San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported12Intersection
On July [XXX], 2022 at 2:18 AM PST 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 west on [XXX] and…On July [XXX], 2022 at 2:18 AM PST 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 west on [XXX] and preparing to make a left turn onto [XXX] to travel south. A passenger car passed the Waymo AV and the vehicle directly behind the Waymo AV by crossing into and driving in the opposing lane of traffic. As the passenger vehicle passed the Waymo on the left, the right side of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. At the time of impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor 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. This report was submitted from the Eastern time zone on the required date.
30270-3636ADSWaymo LLC2022-07 02:50Tempe, AZ2017 Chrysler PacificaADSPassenger CarNo Injuries Reported0Parking Lot
On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was st…On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was stopped to pick up a passenger when a passenger vehicle, parked perpendicular and to the right of the Waymo AV, reversed out of a parking spot. The rear of the passenger vehicle made contact with the front passenger side corner of the Waymo AV as the passenger was closing the door on the driver side of the Waymo AV prior to fastening their seat belt. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers 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. This report was submitted from the Eastern time zone on the required date.
30330-3482 v2ADSTORC Robotics, Inc.2022-07 16:33ALBUQUERQUE, NM2021 FREIGHTLINER CASCADIAADSOther, see NarrativeNo Injuries Reported58Highway / FreewayRedacted by NHTSA as confidential business information
30330-3561ADSTORC Robotics, Inc.2022-07 12:39Santa Rosa, NM2021 FREIGHTLINER CASCADIAADSOther, see NarrativeNo Injuries Reported51Highway / FreewayRedacted by NHTSA as confidential business information
30412-3580ADSCruise LLC2022-07 2:57San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-3581ADSCruise LLC2022-07 22:46San Francisco, CA2020 Cruise AVADSSUVNo Injuries Reported6IntersectionRedacted by NHTSA as confidential business information
30412-3582ADSCruise LLC2022-07 1:39San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported12StreetRedacted by NHTSA as confidential business information
30412-3584ADSCruise LLC2022-07 00:27San Francisco, CA2020 Cruise AVADSOther, see NarrativeNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30531-3661ADSTransdev Alternative Services2022-07 02:50Tempe, AZ2017 Chrysler PacificaADSPassenger CarNo Injuries Reported0Parking Lot
On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehice ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was s…On July [XXX], 2022 at 2:50 AM PST a Waymo Autonomous Vehice ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle in a parking lot at the corner of [XXX] and [XXX]. The Waymo AV was stopped to pick up a passenger when a passenger vehicle, parked perpendicular and to the right of the Waymo AV, reversed out of a parking spot. The rear of the passenger vehicle made contact with the front passenger side corner of the Waymo AV as the passenger was closing the door on the driver side of the Waymo AV prior to fastening their seat belt. 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. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3636-1.
30531-3662ADSTransdev Alternative Services2022-07 02:50San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported12Intersection
On July [XXX], 2022 at 2:18 AM PST 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 west on [XXX] and…On July [XXX], 2022 at 2:18 AM PST 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 west on [XXX] and preparing to make a left turn onto [XXX] to travel south. A passenger car passed the Waymo AV and the vehicle directly behind the Waymo AV by crossing into and driving in the opposing lane of traffic. As the passenger vehicle passed the Waymo on the left, the right side of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. At the time of 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3635-1.
30531-3663ADSTransdev Alternative Services2022-07 23:23San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported9Street
On July [XXX], 2022 at 11:23 PM PST 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 north on [XXX] i…On July [XXX], 2022 at 11:23 PM PST 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 north on [XXX] in the rightmost lane when a passenger car approached the Waymo AV from behind on the left. Just after passing the Waymo AV, the passenger car veered across the path of the Waymo AV into the entrance of a gas station on the right hand side of the roadway. The right rear corner of the passenger vehicle made contact with the front left corner of the Waymo AV, immediately after which the passenger car left the scene. 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3633-1.
30531-3665ADSTransdev Alternative Services2022-07 10:08San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Parking Lot
On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]t. The Waymo AV came to a stop while…On July [XXX], 2022 at 10:08 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot near [XXX] at [XXX]t. The Waymo AV came to a stop while yielding for an oncoming van in a narrow passageway in a parking lot. While attempting to pass the Waymo AV, the van made contact with the sensor housing on the left rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was stationary and engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-3625-1.
30610-3508 v2ADSZoox, Inc.2022-07 14:30San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported1Intersection
A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, Ca when a passenger vehicle turning left from [XXX] on to [XXX] struck the rear of the Zoox vehicle damaging the sensors. There were no injuri…A Zoox vehicle in autonomy was proceeding straight on [XXX] in San Francisco, Ca when a passenger vehicle turning left from [XXX] on to [XXX] struck the rear of the Zoox vehicle damaging the sensors. There were no injuries and the police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field.
540-3643ADSGeneral Motors, LLC2022-07 2:57San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0Street
On August [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-…On August [XXX], 2022 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3580-1)
540-3644ADSGeneral Motors, LLC2022-07 22:46San Francisco, CA2020 Cruise AVADSSUVNo Injuries Reported6Intersection
On August [XXX, 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-…On August [XXX, 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3581-1)
540-3645ADSGeneral Motors, LLC2022-07 1:39San Francisco, CA2020 Cruise AVADSPassenger CarNo Injuries Reported12Street
On August [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise…On August [XXX], 2022, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3582-1)
540-3647ADSGeneral Motors, LLC2022-07 00:27San Francisco, CA2020 Cruise AVADSOther, see NarrativeNo Injuries Reported0Street
On August [XXX], GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On August [XXX], GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-3584-1)
30270-3255 v2ADSWaymo LLC2022-06 12:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] A Waymo Autonomous Vehicle ("Waymo AV") operating in San Fra…A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot on [XXX] between [XXX] and [XXX]. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage 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. This report was submitted from the Pacific time zone on the required date.
30270-3435ADSWaymo LLC2022-06 07:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on ea…On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX], a pickup that had previously been stopped behind the Waymo AV rolled forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor 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. This report was submitted from the Eastern time zone on the required date.
30270-3437ADSWaymo LLC2022-06 10:07San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On June [XXX], 2022 at 10:07 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped in autonomous…On June [XXX], 2022 at 10:07 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped in autonomous mode behind stopped traffic facing east on [XXX]. The passenger vehicle ahead of the Waymo AV transitioned into reverse and began to accelerate, making contact with the front sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor 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. This report was submitted from the Eastern time zone on the required date.
30290-3135 v2ADSArgo AI2022-06 16:35Austin, TX2020 Ford EscapeADSNon-Motorist: CyclistNo Injuries Reported0Street2022-06-[XXX] - Submission of 10 Day Update for Report 30290-3135-1: Argo AI has not received notice of any material new or materially different information about this incident.
30290-3346ADSArgo AI2022-06 14:48Miami, FL2020 Ford EscapeADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30290-3347ADSArgo AI2022-06 13:30Pittsburgh, PA2020 Ford EscapeADSSUVNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30531-3256 v2ADSTransdev Alternative Services2022-06 12:50San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot. As the Waymo AV turned left and into the parking lot, the Waymo AV's…A Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA made contact with a parking lot driveway. The Waymo AV approached a parking lot. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did no contact any vehicle or road user). At the time of the contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX].
30531-3445ADSTransdev Alternative Services2022-06 7:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on ea…On June [XXX], 2022 at 7:26 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX], a pickup that had previously been stopped behind the Waymo AV rolled forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX]
30531-3446ADSTransdev Alternative Services2022-06 10:07San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On June [XXX], 2022 at 10:07 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped in autonomous…On June [XXX], 2022 at 10:07 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] and [XXX]. The Waymo AV was stopped in autonomous mode behind stopped traffic facing east on [XXX]. The passenger vehicle ahead of the Waymo AV transitioned into reverse and began to accelerate, making contact with the front sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX]
30590-3431ADSApple Inc.2022-06 15:15Mountain View, CA2016 Lexus RX 450hADSPassenger CarNo Injuries Reported0Intersection
Subject vehicle was on a testing mission in Mountain View, CA. The vehicle was traveling North-bound on [XXX] operated by the vehicle's Level 4 Automated Driving System and supervised by a safety driver in the driver's …Subject vehicle was on a testing mission in Mountain View, CA. The vehicle was traveling North-bound on [XXX] operated by the vehicle's Level 4 Automated Driving System and supervised by a safety driver in the driver's designated seating position, and with a safety operator in the front passenger seating position. Subject vehicle approached a red light to make a right turn East-bound onto [XXX]. The safety operator suggested that the safety driver disengage the ADS and make the turn in manual mode because the vehicle was hesitant in approaching the intersection. The safety driver disengaged the ADS, and, approximately 250ms later, subject vehicle was lightly struck from behind by a white Mazda3. Having seen debris on the roadway, the driver and operator believed they had run over a rock and did not realize they were hit by the vehicle. After concluding the mission, the driver and operator found damage to a sensor during an inspection. A subsequent review of video led to discovery of the crash. No injuries were reported, and law enforcement was not called to the scene. In addition to telematics and video, we also have photographs of the vehicle's damaged sensor.
30610-3215 v2ADSZoox, Inc.2022-06 10:45San Mateo, CA2016 Toyota HighlanderADSSUVNo Injuries Reported6Street
A Zoox vehicle was in autonomy exiting a parking space on [XXX] between [XXX] and [XXX] in San Mateo, CA, with a second vehicle stopped in the lane with its right turn indicator on, when a third vehicle overtook the seco…A Zoox vehicle was in autonomy exiting a parking space on [XXX] between [XXX] and [XXX] in San Mateo, CA, with a second vehicle stopped in the lane with its right turn indicator on, when a third vehicle overtook the second vehicle and cut in abruptly from the left, making contact with the front left side and sensors of the Zoox vehicle as it was exiting the space. The Zoox operator disengaged to manual mode just before the contact. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field.
30610-3320ADSZoox, Inc.2022-06 14:36San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported25Street
A Zoox vehicle in manual mode was proceeding straight and in its lane on [XXX] in San Francisco, when an occupant of a parallel parked car abruptly opened a rear door into the side of the Zoox vehicle, causing minor dama…A Zoox vehicle in manual mode was proceeding straight and in its lane on [XXX] in San Francisco, when an occupant of a parallel parked car abruptly opened a rear door into the side of the Zoox vehicle, causing minor damage to both vehicles. The Zoox vehicle had disengaged for unrelated traffic within 30 seconds of the contact. There were no injuries and the police were not called.
502-3140 v2ADSFord Motor Company2022-06 16:35Austin, TX2020 Ford EscapeADSNon-Motorist: CyclistNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
502-3413ADSFord Motor Company2022-06 14:48Miami, FL2020 Ford EscapeADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
502-3416ADSFord Motor Company2022-06 13:30Pittsburgh, PA2020 Ford EscapeADSSUVNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
1306-3355ADSToyota Motor Engineering & Manufacturing2022-05 16:11Arlington, TX2020 Lexus RX450HADSPickup TruckNo Injuries Reported11Street
This report is being submitted because May Mobility notified Toyota on July [XXX], 2022 of Monthly Report submission 30413-3138-1, related to an incident reported in May 2022. Toyota has no additional information on this…This report is being submitted because May Mobility notified Toyota on July [XXX], 2022 of Monthly Report submission 30413-3138-1, related to an incident reported in May 2022. Toyota has no additional information on this incident beyond what was submitted in the aforementioned Monthly Report. Please refer to the report from May Mobility for details.
30270-3055 v2ADSWaymo LLC2022-05 01:16San Francisco, CA2021 Jaguar I-PACEADSMotorcycleNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX] in the rightmost lane, a motorcycle approached the Waymo AV from behind and the front of the motorcycle made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a motorcyclist was involved. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-3056 v2ADSWaymo LLC2022-05 01:43Phoenix, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on May [XXX], 2022 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona made contact with a parking lot driveway on the 700 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AVs undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor undercarriage damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-3219ADSWaymo LLC2022-05 13:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a pickup truck approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor 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. This report was submitted from the Pacific time zone on the required date.
30270-3220ADSWaymo LLC2022-05 09:19San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from …On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from [XXX] and [XXX] while yielding to a pedestrian in the adjacent crosswalk in autonomous mode. A SUV approaching from behind the Waymo AV passed on the left side, making contact with the Waymo AVs rear left sensor housing. The Waymo AV operator transitioned the system from autonomous to manual mode just before the moment of impact. The SUV immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor 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. This report was submitted from the Pacific time zone on the required date.
30270-3221ADSWaymo LLC2022-05 13:26San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported1Intersection
On May [XXX], 2022 at 1:26 PM PST 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 proceeding south on [XXX] at…On May [XXX], 2022 at 1:26 PM PST 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 proceeding south on [XXX] at [XXX]. , [XXX] in autonomous mode, and preparing to make a left turn onto [XXX]. As the Waymo AV entered the intersection, it slowed to yield to northbound traffic on [XXX]. A passenger car approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained minor 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. This report was submitted from the Pacific time zone on the required date.
30290-3119ADSArgo AI2022-05 08:11WDC, DC2020 Ford EscapeADSHeavy TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30410-3043ADSMotional2022-05 12:58Las Vegas, NV2022 Hyundai Ioniq 5ADSOther, see NarrativeNo Injuries Reported8StreetRedacted by NHTSA as confidential business information
30413-3138ADSMay Mobility2022-05 16:11Arlington, TX2020 Lexus RX450HADSPickup TruckNo Injuries Reported11Street
The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passe…The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passenger-side mirror to contact the parked vehicle's driver-side mirror. The May vehicle's ground mapping module had fallen significantly behind in its processing of lidar data. As a result, actual objects were being filtered out of the lidar data during object detection. This filtering caused the truck to oscillate between being detected, detecting only the cab, detecting the cab and mirror, and not being detected at all. After assessing the issue, it has been determined that ground map latency alone will not cause safety issues. There is no risk to VRUs, or anything at ground level. The issue was with something in the air (mirror), above the ground. A permanent fix to address the ground map latency issue is in process and will be implemented in the entire fleet within the next 30 days. The second factor in the collision is that we were artificially constraining the vehicle to the right side of the road due to ambiguous and unpainted roadway. If we change that constraint to an advisory line (and allow the vehicle to cross the line to the left), we would have been far enough to the left to avoid collision (simulation success). Solution Implementation: AVO training for extra caution related to protruding items like mirrors (short term), software changes coming in the next update and hotfix (within 30 days), and further improvement in the following update (within 60 days). Until the tested software changes are implemented, we have advised the AVOs to take extra caution in these scenarios and to continue to disengage autonomy when desired. As always, we sacrifice autonomy for safety, as needed.
30490-3168ADSBeep, Inc.2022-05 12:30Dunedin, FLNavyaADSBusNo Injuries Reported7Intersection
Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Tel…Beep Event Level: 1 NHTSA: Reportable Employee: [XXX] Location: City of Dunedin/[XXX] Direction: Southbound Weather: Clear Passengers: 4 Witness Statements: 1 Operator report: Yes Investigating Supervisor: [XXX] Telemetry/Video: Requested and received Vehicle taken out of service: Yes temporary safety hold Photographs: Yes Substantial damage: No damages to report Vehicle placed on safety hold: Yes vehicle has been inspected and available for service Lead Investigator: Chief Safety Officer The Beep shuttle attendant was traveling Southbound on [XXX] at approx 7-12 mph in ADS and headed towards the intersection of [XXX]. Beep vehicle stopped at red light at intersection. As the Beep vehicle was crossing the intersection in manual and slowing to a stop to return to ADS in a southbound direction, the trailing bus made light contact with its bicycle rack to the Beep shuttle rear end. The trailing vehicle is a bus owned and operated by the Pinellas Suncoast Transit Authority (PSTA). According to video, as reported by the shuttle attendant and the PSTA Road Supervisor, the bus was tailgating. Root Cause: Trailing vehicle following too closely and not observing Navya slowing to a stop.
30531-3064 v2ADSTransdev Alternative Services2022-05 01:16San Francisco, CA2021 Jaguar I-PaceUnknown, see NarrativeMotorcycleNo Injuries Reported0Intersection
Aside from a typo in the location address, this report is unchanged from the previously submitted report (Report ID#: 30531-3064-1) On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Sa…Aside from a typo in the location address, this report is unchanged from the previously submitted report (Report ID#: 30531-3064-1) On May [XXX], 2022 at 1:16AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a motorcycle on [XXX] at [XXX]. While the Waymo AV was stopped at a red light on eastbound [XXX] in the rightmost lane, a motorcycle approached the Waymo AV from behind and the front of the motorcycle made contact with the rear of the Waymo AV. At the time of 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 minor damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a motorcyclist was involved. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202205[XXX]-0 (rev.202205[XXX]215904).
30531-3065 v2ADSTransdev Alternative Services2022-05 01:43Phoenix, AZ2021 Jaguar I-PaceUnknown, see NarrativeOther, see NarrativeNo Injuries Reported9Parking Lot
The content of this report is unchanged from the previously submitted report (Report ID#: 30531-3065-1) On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona made contact …The content of this report is unchanged from the previously submitted report (Report ID#: 30531-3065-1) On May [XXX], 2022 at 1:43AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona made contact with a parking lot driveway on the 700 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AVE did not contact any vehicle or road user). At the time of contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because the Waymo AV was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-202205[XXX]-0 (rev.202205[XXX]213041).
30531-3225ADSTransdev Alternative Services2022-05 13:26San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While at…On May [XXX], 2022 at 1:26 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck at the northbound merge lane on the 100 block of [XXX]. While attempting a merge onto northbound [XXX] from southbound [XXX] from southbound [XXX], the Waymo AV came to a stop to yield for approaching traffic on the right. While stopped, a pickup truck approached from behind and made contact with the rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-[XXX].
30531-3226ADSTransdev Alternative Services2022-05 09:19San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from …On May [XXX], 2022 at 9:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] and [XXX]. The Waymo AV was attempting to make a right turn from [XXX] and [XXX]. while yielding to a pedestrian in the adjacent crosswalk in autonomous mode. A SUV approaching from behind the Waymo AV passed on the left side, making contact with the Waymo AVs rear left sensor housing. The Waymo AV operator transitioned the system from autonomous to manual mode just before the moment of impact. The SUV immediately left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of WaymoLLC-[XXX].
30531-3227ADSTransdev Alternative Services2022-05 13:26San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported1Intersection
On May [XXX], 2022 at 1:26 PM PST 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 proceeding south on [XXX] …On May [XXX], 2022 at 1:26 PM PST 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 proceeding south on [XXX] in autonomous mode, and preparing to make a left turn onto [XXX]. As the Waymo AV entered the intersection, it slowed to yield to northbound traffic on [XXX]. A passenger car approached from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate to WaymoLLC-2022[XXX]-0 (rev.20220615[XXX])
30610-3158 v2ADSZoox, Inc.2022-05 13:30San Francisco, CA2016 Toyota HighlanderADSPassenger CarNo Injuries Reported25Street
A Zoox vehicle in autonomous mode was stopped on [XXX] facing [XXX], when a passenger vehicle from behind made contact with its rear sensors at low speed. The police were not called and there were no injuries. Zoox is su…A Zoox vehicle in autonomous mode was stopped on [XXX] facing [XXX], when a passenger vehicle from behind made contact with its rear sensors at low speed. The police were not called and there were no injuries. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field.
30711-3157ADSPony.ai2022-05 15:00Irvine, CA2021 Hyundai Kona EVADSPassenger CarNo Injuries Reported4Street
On May [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was proceeding straight at a low speed when a passenger vehicle reversed into the side of t…On May [XXX], 2022, while operating in autonomous mode with a safety operator in the driver's seat, a Pony.ai Autonomous Vehicle was proceeding straight at a low speed when a passenger vehicle reversed into the side of the Pony.ai vehicle. The Pony.ai vehicle did not suffer damage. There were no injuries, the police were not called to the scene, and the Pony.ai vehicle was driven back to Pony.ai's Irvine-area facility. Please note that the "UNK" checkbox was selected for the Pony.ai vehicle in the grid as there is no option to select "no damage" for the subject vehicle. The only minor damage in the incident was to the passenger vehicle.
502-2973 v2ADSFord Motor Company2022-05 08:11WDC, DC2020 Ford EscapeADSHeavy TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
855-3183 v2ADSMercedes-Benz USA, LLC2022-05 15:05Commerce, CA2022 Mercedes-Benz S350DADSHeavy TruckNo Injuries ReportedHighway / Freeway
While departing from a standstill in heavy traffic with L3 ADS engaged, the subject Mercedes-Benz vehicle was struck in the rear bumper by a large semi-truck. No injuries were reported and the contact from the truck resu…While departing from a standstill in heavy traffic with L3 ADS engaged, the subject Mercedes-Benz vehicle was struck in the rear bumper by a large semi-truck. No injuries were reported and the contact from the truck resulted in two minor scratches and two indentations on the rear bumper of the Mercedes-Benz. The driver of the truck did not pull over after the collision. The Mercedes-Benz was driven from the incident location, and further inspection of the vehicle concluded no additional damage beyond the cosmetic dents and surface scratches.
10003-3210ADSNavistar, Inc.2022-04 15:52Tucson, AZ2021 International LT625Unknown, see NarrativeOther Fixed ObjectNo Injuries Reported65Highway / Freeway
All of the data in this report and the following text is an excerpt from TuSimples original submission (30370-2949-1) and constitutes Navistars sole understanding of this event. TuSimple's position is that this event doe…All of the data in this report and the following text is an excerpt from TuSimples original submission (30370-2949-1) and constitutes Navistars sole understanding of this event. TuSimple's position is that this event does not meet the criteria for reporting under the SGO. Specifically, the L4 ADS was not in operation at any point in the 30 seconds prior to making contact with the concrete barrier. The event occurred as follows: As the truck was being operated on the highway, within its mapped ODD, the driver and test engineer attempted to engage the ADS. However, the ADS was not functional at that moment due to the computer unit not having been initialized, and should not have been attempted to be activated. In short, this was a failed attempt to engage the system as a result of human error. The system has now been modified to prevent the ADS from attempting to engage unless the health of the system is fully functional to prevent human error from repeating this event. When the erroneous attempt to engage occurred, the uninitialized vehicle control unit rotated the steering to the left, causing the truck to veer left. The safety driver took control of the steering, and was able to steer accordingly, but not before the left front truck tire and left front quarter panel came into contact with the concrete barrier to the left of the lanes of travel.
273-2632 v2ADSChrysler (FCA US, LLC)2022-04 03:30Saint Clair, MI2022 Jeep Grand CherokeeADASOther Fixed ObjectNo Injuries Reported50UnknownRedacted by NHTSA as confidential business information
30270-2610 v2ADSWaymo LLC2022-04 02:27San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported20Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2610-1]. On April [XXX], 2022 at 2:27 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2610-1]. On April [XXX], 2022 at 2:27 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was in autonomous mode and proceeding southbound on [XXX] in the rightmost lane, with a passenger vehicle traveling parallel in the left adjacent lane. As the two vehicles approached [XXX], the passenger vehicle cut into the Waymo's lane and braked before turning right on [XXX]. As the passenger vehicle executed the right turn, the Waymo AV test driver transitioned to manual mode, applied the brakes, but made contact with the passenger side rear corner of the passenger vehicle. 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 other party immediately left the scene of the event. The Waymo AV sustained minor 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. This report was submitted from the Pacific time zone on the required date.
30270-2646 v2ADSWaymo LLC2022-04 19:55San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Fra…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2646-1]. On April [XXX], 2022 at 7:55 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA was in a collision involving a passenger car on [XXX] at [XXX] The Waymo AV came to a stop at a stop sign on [XXX] at [XXX] and as it was about to proceed, a passenger vehicle behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained minor 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. This report was submitted from the Pacific time zone on the required date.
30270-2657 v2ADSWaymo LLC2022-04 18:29Phoenix, AZ2021 Jaguar I-PaceADSMotorcycleNo Injuries Reported3Intersection
The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2657-1]. On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix…The content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2657-1]. On April [XXX], 2022 at 6:29 PM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in Phoenix, Arizona was in a collision involving a motorcycle on [XXX] at [XXX]. The Waymo AV was preparing to make a right turn from southbound [XXX] onto westbound [XXX], when it slowed to yield to a pedestrian crossing [XXX]. As the Waymo AV yielded, a motorcycle directly behind the Waymo AV was rear-ended by a pick-up truck. The motorcycle was pushed forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV and the motorcycle sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and a motorcycle was damaged. Waymo may supplement or correct its reporting with additional information as it may become available. This report was submitted from the Pacific time zone on the required date.
30270-2793 v2ADSWaymo LLC2022-04 02:31San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported9Parking Lot
Other than the updated time zone of submission, the content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2793-1]. On April [XXX], 2022 at 2:31 AM PST a Waymo Auto…Other than the updated time zone of submission, the content of this report is unchanged from the initial report submitted on April [XXX], 2022 [Report ID # 30270-2793-1]. On April [XXX], 2022 at 2:31 AM PST a Waymo Autonomous Vehicle ('Waymo AV') operating in San Francisco, CA made contact with a parking lot driveway on the 200 block of [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a parking lot on the left side of the street. As the Waymo AV turned left and into the parking lot, the Waymo AV's undercarriage made contact with the driveway pavement (the AV did not contact any vehicle or road user). At the time of the contact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained minor undercarriage 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. This report was submitted from the Pacific time zone on the required date.

What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.