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

443 reports, showing 201 to 300.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
540-6190ADSGeneral Motors, LLC2023-08 01:39San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported0Intersection
On August 29, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 29, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6181-1)
540-6199ADSGeneral Motors, LLC2023-08 00:39Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported5Street
On September 1, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On September 1, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6191-1)
540-6293 v2ADSGeneral Motors, LLC2023-08 14:53San Francisco, CA2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6271-1)
540-6294 v2ADSGeneral Motors, LLC2023-08 16:06San Francisco, CA2023 Cruise AVADSPassenger CarMinor1Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6270-1)
540-6295ADSGeneral Motors, LLC2023-08 20:33San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported8Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6268-1)
540-6302ADSGeneral Motors, LLC2023-08 13:47San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported5Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6269-1)
540-6304 v2ADSGeneral Motors, LLC2023-08 09:05San Francisco, CA2023 Cruise AVADSPassenger CarMinor5Street
On October 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) ma…On October 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6167-2)
540-6305ADSGeneral Motors, LLC2023-08 23:36Austin, TX2023 Cruise AVADSSUVNo Injuries Reported10Street
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6273-1)
540-6306ADSGeneral Motors, LLC2023-08 22:32San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6275-1)
540-6307ADSGeneral Motors, LLC2023-08 23:34San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported0Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6272-1)
540-6308ADSGeneral Motors, LLC2023-08 10:37San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6276-1)
540-6310ADSGeneral Motors, LLC2023-08 00:21Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6274-1)
540-6311ADSGeneral Motors, LLC2023-08 11:59San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported1Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6279-1)
540-6313ADSGeneral Motors, LLC2023-08 16:45San Francisco, CA2023 Cruise AVADSPickup TruckNo Injuries Reported0Street
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6278-1)
540-6315ADSGeneral Motors, LLC2023-08 22:55San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported6Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6280-1)
540-6316ADSGeneral Motors, LLC2023-08 16:31San Francisco, CA2022 Cruise AVADSPickup TruckNo Injuries Reported1Street
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6281-1)
540-6317ADSGeneral Motors, LLC2023-08 08:37San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6277-1)
540-6318ADSGeneral Motors, LLC2023-08 04:53San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported7Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6282-1)
855-6288ADSMercedes-Benz USA, LLC2023-08 13:40Los Angeles, CA2021 Mercedes-Benz S 580 4MaticADSVanMinor0Highway / FreewayRedacted by NHTSA as confidential business information
30270-5855 v2ADSWaymo LLC2023-07 15:08Los Angeles, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported2Intersection
The content of this report is unchanged from the initial report submitted on July 10, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle (Waymo A…The content of this report is unchanged from the initial report submitted on July 10, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and preparing to make a right turn onto westbound [XXX]. As the Waymo AV was yielding to cross-traffic and preparing to make a right turn, a cyclist was traveling eastbound on [XXX] and heading the wrong way in the bike lane. The cyclist then turned left, northbound, onto [XXX], continuing to travel the wrong direction in the bike lane. As the Waymo AV slowly proceeded forward, the cyclist passed the Waymo AV and made contact with the rear passenger side 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). The Waymo AV sustained damage and the cyclist did not stop, leaving the scene without exchanging information. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a cyclist was involved. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5896ADSWaymo LLC2023-07 18:13Chandler, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On July [XXX], 2023 at 6:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and ju…On July [XXX], 2023 at 6:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and just passed [XXX] when an oncoming passenger car crossed into the Waymo AVs lane, toward the Waymo AV. The Waymo AV then stopped as the passenger vehicle continued to approach. The passenger vehicle then made contact with the front of the Waymo AV, and then made contact with the side of the Waymo AV as it left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5997ADSWaymo LLC2023-07 15:34Tempe, AZ2021 Jaguar I-PaceADSPassenger CarMinor3Street
On July [XXX], 2023 at 3:34 PM PT 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 westbound on [XXX] in …On July [XXX], 2023 at 3:34 PM PT 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 westbound on [XXX] in the left lane with a vehicle overtaking it in the right adjacent lane when it detected a large, fallen tree branch in part of its lane and applied braking in response. As the Waymo AV was braking and had slowed to 3 mph, a passenger vehicle behind the Waymo made contact with the rear of the Waymo AV. Moments later, an SUV behind the passenger vehicle made contact with the rear of the passenger vehicle. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. All vehicles sustained damage. Rather than wearing the seat belt, the passenger in the Waymo AV was sitting on the buckled seat belt at the time of the collision. The passenger declined medical attention. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5998ADSWaymo LLC2023-07 15:04San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported9Intersection
On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the cu…On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] at [XXX] when it began to pull away from the curb and into traffic. As the Waymo AV pulled away from the curb, a pickup truck that was traveling behind the Waymo AV then 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. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6129ADSWaymo LLC2023-07 13:13San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported4Street
On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XX…On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it began to brake as it approached a stopped van on the oncoming side of the narrow roadway. The Waymo AV test driver transitioned to manual mode and began proceeding straight when the passenger side front sensor housing of the Waymo AV made contact with the driver side mirror of a passenger car parked along the curb on southbound [XXX]. 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. Both the Waymo AV and the passenger car 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-6130ADSWaymo LLC2023-07 10:13San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] i…On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] in autonomous mode, the Waymo AV slowed to a stop while entering a narrow roadway. The test driver transitioned the vehicle to manual mode and proceeded forward, making contact with a parked SUV. 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. 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-6131ADSWaymo LLC2023-07 9:02Phoenix, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On July [XXX], 2023 at 9:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was parallel parked along the right-hand …On July [XXX], 2023 at 9:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was parallel parked along the right-hand curb on eastbound [XXX] when a passenger car reversed out of a driveway across the street from the Waymo AV and made contact with the driver side rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6132ADSWaymo LLC2023-07 9:51San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On July [XXX], 2023 at 9:51 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The collision occurred while the Waymo AV w…On July [XXX], 2023 at 9:51 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The collision occurred while the Waymo AV was stopped in the leftmost lane of a two-lane, one-way road at the intersection of [XXX] at [XXX]. The Waymo AV was facing a green light, but stopped before entering the intersection because traffic was stacked on the other side of the intersection, leaving no space for the AV. When the light turned yellow, a passenger car that had been stopped behind the Waymo AV passed the Waymo AV on the left and proceeded into the intersection. While passing the Waymo AV, the passenger cars rear passenger side door made contact with the driver side rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The passenger car did not stop but appears to have 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-6133ADSWaymo LLC2023-07 11:11San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Street
On July [XXX], 2023 at 11:11 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] east of [XXX]. The Waymo AV was facing east, waiting to merge t…On July [XXX], 2023 at 11:11 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] east of [XXX]. The Waymo AV was facing east, waiting to merge to the left back into eastbound traffic on [XXX], and stopped to the left of the right turn slip lane on [XXX], with stopped traffic to the right. After waiting to merge, the Waymo AV started reversing to reroute and while doing so, a sensor on the right front of the Waymo AV made contact with the left rear side of an SUV in the right turn lane. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The SUV 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-6134ADSWaymo LLC2023-07 14:57Santa Monica, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported0Street
On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbo…On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbound [XXX] when a cyclist that had been traveling behind the Waymo AV passed the Waymo AV on the right. As the cyclist passed the Waymo AV, the cyclist made contact with the front passenger side 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). The Waymo AV sustained damage and the cyclist did not stop, leaving the scene without exchanging 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.
30412-5848ADSCruise LLC2023-07 22:47San Francisco, CA2023 Cruise AVADSPickup TruckNo Injuries Reported4StreetRedacted by NHTSA as confidential business information
30412-5968ADSCruise LLC2023-07 23:08San Francisco, CA2023 Cruise AVADSSUVMinor15IntersectionRedacted by NHTSA as confidential business information
30412-5980ADSCruise LLC2023-07 19:50Austin, TX2023 Cruise AVADSSUVNo Injuries Reported20IntersectionRedacted by NHTSA as confidential business information
30412-5981ADSCruise LLC2023-07 01:56San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-5982 v2ADSCruise LLC2023-07 06:41San Francisco, CA2023 Cruise AVADSPassenger CarUnknown0IntersectionRedacted by NHTSA as confidential business information
30412-5989ADSCruise LLC2023-07 20:38Tempe, AZ2022 Cruise AVADSPassenger CarMinor27StreetRedacted by NHTSA as confidential business information
30412-5992ADSCruise LLC2023-07 05:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported22IntersectionRedacted by NHTSA as confidential business information
30412-5993ADSCruise LLC2023-07 14:45San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported10IntersectionRedacted by NHTSA as confidential business information
30412-6006ADSCruise LLC2023-07 23:51San Francisco, CA2022 Cruise AVADSPickup TruckNo Injuries Reported2IntersectionRedacted by NHTSA as confidential business information
30412-6037ADSCruise LLC2023-07 01:52San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported6StreetRedacted by NHTSA as confidential business information
30412-6038ADSCruise LLC2023-07 20:56San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6039 v2ADSCruise LLC2023-07 22:34San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported1Street
A Cruise autonomous vehicle ("AV"), operating in driverless autonomous mode, was at a complete stop in response to a red light in the leftmost turn lane on westbound [XXX] at the intersection with [XXX]. When the light t…A Cruise autonomous vehicle ("AV"), operating in driverless autonomous mode, was at a complete stop in response to a red light in the leftmost turn lane on westbound [XXX] at the intersection with [XXX]. When the light turned green, both the AV and a GMC Yukon in the adjacent lane attempted a left turn onto southbound [XXX]. The AV veered slightly to the right into the [XXX] before attempting its left turn, making contact as the Yukon began its turn. This caused damage to the AV's front passenger side radar assembly. The driver of the GMC Yukon left the scene without exchanging information. There were no reported injuries.
30412-6040ADSCruise LLC2023-07 00:07San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported23StreetRedacted by NHTSA as confidential business information
30412-6041ADSCruise LLC2023-07 10:47San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported2StreetRedacted by NHTSA as confidential business information
30412-6042ADSCruise LLC2023-07 16:16San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6043ADSCruise LLC2023-07 02:29Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6044ADSCruise LLC2023-07 22:41San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported1IntersectionRedacted by NHTSA as confidential business information
30413-6032ADSMay Mobility2023-07 17:25Grand Rapids, MN2021 Toyota SiennaADSPickup TruckNo Injuries Reported0Street
The May vehicle came to a gentle stop at the railroad crossing (about -0.8 m/s2 deceleration) as designed, but the agent behind did not come to a stop and made contact with the AV. The May shuttle behaved as expected and…The May vehicle came to a gentle stop at the railroad crossing (about -0.8 m/s2 deceleration) as designed, but the agent behind did not come to a stop and made contact with the AV. The May shuttle behaved as expected and slowed down to a stop in a safe manner. The collision was unavoidable from the shuttle side.
30530-6125ADSAurora Operations, Inc.2023-07 09:35BUFFALO, TX2022 Peterbilt 579mADSOther, see NarrativeNo Injuries Reported64Highway / Freeway
At 09:35 AM CDT on July [XXX], 2023, an Aurora Class 8 truck was traveling southbound in autonomy mode on [XXX] near [XXX] when the front windshield was struck by an unknown object. The bottom of the windshield had a ho…At 09:35 AM CDT on July [XXX], 2023, an Aurora Class 8 truck was traveling southbound in autonomy mode on [XXX] near [XXX] when the front windshield was struck by an unknown object. The bottom of the windshield had a hole about 3 inches in diameter. The vehicle operator disengaged autonomy and pulled over. The vehicle was able to be driven from the scene, and there were no reported injuries.
30531-5871 v2ADSTransdev Alternative Services2023-07 15:08Los Angeles, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported2Intersection
The content of this report in unchanged from the initial report submitted on July 10, 2023 (Report ID # 30531-5871-1) On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, Ca…The content of this report in unchanged from the initial report submitted on July 10, 2023 (Report ID # 30531-5871-1) On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and preparing to make a right turn onto westbound [XXX]. As the Waymo AV was yielding to cross-traffic and preparing to make a right turn, a cyclist was traveling eastbound on [XXX] and heading the wrong way in the bike lane. The Cyclist then turned left, northbound, onto [XXX], continuing to travel the wrong direction in the bike lane. As the Waymo AV slowly proceeded forward, the cyclist passed the Waymo AV and made contact with the rear passenger side sensor 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 sustained damage and the cyclist did not stop. Transdev Alternative Services is reporting a duplicate report from report number: 30270-5855-1.
30531-5999ADSTransdev Alternative Services2023-07 15:04San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported9Intersection
On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the c…On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] at [XXX] when it began to pull away from the curb and into traffic. As the Waymo AV pulled away from the curb, a pickup truck that was traveling 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 damage.
30531-6136ADSTransdev Alternative Services2023-07 14:57Santa Monica, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported0Street
On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwest…On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbound [XXX] when a cyclist that had been traveling behind the Waymo AV passed the Waymo AV on the right. As the cyclist passed the Waymo AV, the cyclist made contact with the front passenger side sensor 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 sustained damage and the cyclist did not stop, leaving the scene without exchanging 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 report id: 30270-6134-1.
30531-6137ADSTransdev Alternative Services2023-07 10:13San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX…On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] in autonomous mode, the Waymo AV slowed to a stop while entering a narrow roadway. The test driver transitioned the vehicle to manual mode and proceeded forward, making contact with a parked SUV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. 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-6130-1.
30531-6138ADSTransdev Alternative Services2023-07 13:13San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported4Street
On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [X…On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it began to brake as it approached a stopped van on the oncoming side of the narrow roadway. The Waymo AV test driver transitioned to manual mode and began proceeding straight when the passenger side front sensor housing of the Waymo AV made contact with the driver side mirror of a passenger car parked along the curb on southbound [XXX]. At the time of the impact, the Waymo's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both the Waymo AV and the passenger car 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 is a duplicate of report 30270-6129-1.
540-5875ADSGeneral Motors, LLC2023-07 22:47San Francisco, CA2023 Cruise AVADSPickup TruckNo Injuries Reported4Street
On July 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the Order). General Motors LLC (GM) manufactured t…On July 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5848-1)
540-5971ADSGeneral Motors, LLC2023-07 23:08San Francisco, CA2023 Cruise AVADSSUVMinor15Intersection
On July 19,2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the Order). General Motors LLC (GM) manufactured th…On July 19,2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5968-1)
540-5987 v2ADSGeneral Motors, LLC2023-07 06:41San Francisco, CA2023 Cruise AVADSPassenger CarUnknown0Intersection
On August 2, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-Day Updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the Order). General Motors LLC (GM)…On August 2, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-Day Updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5982-2)
540-5988ADSGeneral Motors, LLC2023-07 19:50Austin, TX2023 Cruise AVADSSUVNo Injuries Reported20Intersection
On July 24, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 24, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5980-1)
540-5990ADSGeneral Motors, LLC2023-07 01:56San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On July 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5981-1)
540-5991ADSGeneral Motors, LLC2023-07 20:38Tempe, AZ2022 Cruise AVADSPassenger CarMinor27Street
On July 26, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cr…On July 26, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5989-1)
540-6002ADSGeneral Motors, LLC2023-07 05:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported22Intersection
On July 27, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured …On July 27, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5992-1)
540-6003ADSGeneral Motors, LLC2023-07 14:45San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported10Intersection
On July 27, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured …On July 27, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5993-1).
540-6011ADSGeneral Motors, LLC2023-07 23:51San Francisco, CA2022 Cruise AVADSPickup TruckNo Injuries Reported2Intersection
On August 2, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured…On August 2, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6006-1)
540-6058ADSGeneral Motors, LLC2023-07 01:52San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported6Street
On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6037-1).
540-6069ADSGeneral Motors, LLC2023-07 20:56San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6038-1).
540-6070 v2ADSGeneral Motors, LLC2023-07 22:34San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported1Street
On September 26, 2024, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) …On September 26, 2024, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6039-2)
540-6072ADSGeneral Motors, LLC2023-07 00:07San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported23Street
On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6040-1).
540-6073ADSGeneral Motors, LLC2023-07 10:47San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported2Street
On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6041-1).
540-6074ADSGeneral Motors, LLC2023-07 16:16San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6042-1).
540-6076ADSGeneral Motors, LLC2023-07 02:29Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6043).
540-6079ADSGeneral Motors, LLC2023-07 22:41San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported1Intersection
On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-6044-1).
28349-5694 v5ADSLucid USA, Inc.2023-06 14:59Foster, RI2023 Lucid Air TouringADASPickup TruckUnknown53Highway / FreewayRedacted by NHTSA as confidential business information
30270-5650 v2ADSWaymo LLC2023-06 13:17Phoenix, AZ2021 Jaguar I-PACEADSPassenger CarModerate13Highway / Freeway
After submitting the previous 1-Day report on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], Waymo received notice that the test driver was not transported from the scene to the hospital for medic…After submitting the previous 1-Day report on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION], Waymo received notice that the test driver was not transported from the scene to the hospital for medical treatment, but did seek medical treatment at a hospital at a later time. As such, this event could have qualified for a 5-Day report. The narrative below has been updated to reflect this information. This updated report also now lists the Highest Injury Severity Alleged as moderate, and Transdev Alternative Services as an entity that may be aware of this incident. On [XXX], 2023 at 1:17 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, AZ was in a collision involving a passenger car on [XXX] in the southbound direction near the [XXX]. The Waymo AV was traveling in the rightmost lane (out of 5 lanes) in the southbound direction of [XXX], and the left 3 lanes were closed due to a work zone. The vehicle traveling ahead in the same lane as the ADV made an abrupt lane change to the left, revealing a stack of slow-moving vehicles in the Waymo AVs lane. The test driver of the Waymo AV took manual control of the vehicle and started to decelerate and steer toward the right shoulder in response to slow traffic ahead. A passenger vehicle approached the Waymo AV 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 not engaged and a test driver (in the drivers seating position) was operating the Waymo AV in manual mode. The Waymo AV and the other vehicle sustained damage. The test driver reported an injury, for which they later sought medical treatment. Waymo reported this crash under Request No. 1 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5813ADSWaymo LLC2023-06 20:58Phoenix, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported35Street
On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and prepar…On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and preparing to make a right lane change. As it initiated the lane change, the rear passenger side tire struck small debris in the road. 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 AVs tire immediately deflated. Waymo is reporting this event 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.
30270-5817 v2ADSWaymo LLC2023-06 23:18Los Angeles, CA2021 Jaguar I-PaceADSPickup TruckMinor0Intersection
Other than adding the law enforcement investigation details, the content of this report is unchanged from the initial report submitted on July 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On June […Other than adding the law enforcement investigation details, the content of this report is unchanged from the initial report submitted on July 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On June [XXX], 2023 at 11:18 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving a pick-up truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and stopped at a stop sign at the intersection of [XXX] when a pick-up truck approached the Waymo AV 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). The Waymo AV test driver then took manual control of the Waymo AV and the pick-up truck then made contact with the rear of the Waymo AV again. The Waymo AV test driver pulled towards the side of the road and stopped. TThe pick-up truck then made contact with the rear of the Waymo AV again and when the test driver of the Waymo AV resumed movement, the pick-up truck followed the Waymo AV and repeatedly made further contact with the Waymo AV. At one point the pick-up truck driver verbally harassed the Waymo AV test driver. The Waymo AV test driver was eventually able to elude the pickup truck and wait nearby for law enforcement to arrive. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5957ADSWaymo LLC2023-06 12:35San Francisco, CA2021 Jaguar I-PaceADSVanNo Injuries Reported0Parking Lot
On June [XXX], 2023 at 12:53 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot at [XXX]. The Waymo AV came to a stop while yielding to …On June [XXX], 2023 at 12:53 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot at [XXX]. The Waymo AV came to a stop while yielding to a pickup truck which was reversing into a perpendicular parking space in front of the Waymo AV. While the Waymo AV was stopped, a van which was in a parking space immediately to the right of the Waymo AV began reversing out of the parking space. The rear of the van made contact with the right side of the Waymo AV. The Waymo AV sustained damage. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. 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-5958ADSWaymo LLC2023-06 15:44San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On June [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parallel parked along the …On June [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] when a passenger car pulled up behind the Waymo AV. The front of the passenger car 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. 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-5959ADSWaymo LLC2023-06 17:06San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported1Intersection
On June [XXX], 2023 at 5:06 PM PT 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 stopped for a red light …On June [XXX], 2023 at 5:06 PM PT 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 stopped for a red light on [XXX] at [XXX] with its turn signal activated to indicate intent to turn left onto [XXX]. The traffic light turned green, and the Waymo AV slowly moved forward, yielding to oncoming traffic, when the vehicle that had been previously stopped behind the Waymo AV proceeded forward, making contact with the rear bumper of the Waymo AV. The other party immediately left the scene of the event. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5960ADSWaymo LLC2023-06 21:19San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Street
On June [XXX], 2023 at 9:19 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was parallel parked along the …On June [XXX], 2023 at 9:19 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was parallel parked along the curb on southbound [XXX] when a pickup truck that was initially parked directly behind the Waymo AV began to maneuver out of its parking spot. As the pickup truck pulled out of the parking spot, it initiated a multi-turn maneuver and reversed into the parked Waymo AV. The rear passenger's side corner of the pickup truck made contact with the driver side rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5961ADSWaymo LLC2023-06 07:50San Francisco, CA2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Intersection
On June [XXX], 2023 at 7:50 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and sto…On June [XXX], 2023 at 7:50 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and stopped at a stop sign at the intersection of [XXX]. While yielding to pedestrians crossing the street, a pickup truck traveling directly behind the Waymo AV 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. 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-5962ADSWaymo LLC2023-06 21:39Tempe, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported56Highway / Freeway
On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane when …On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane when road debris appeared from under the passenger vehicle in front of the Waymo AV. The Waymo AV test driver transitioned to manual mode just before the Waymo AV made contact with the road debris. 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.
30410-5786 v2ADSMotional2023-06 21:42Las Vegas, NV2021 Hyundai Ioniq 5ADSPassenger CarMinor3Intersection
On June [XXX], 2023, at 9:42 PM PDT, a Motional Hyundai Ioniq 5 was operating in autonomous mode with a safety driver at the wheel and a safety operator in the front passenger seat. The Motional vehicle was northbound …On June [XXX], 2023, at 9:42 PM PDT, a Motional Hyundai Ioniq 5 was operating in autonomous mode with a safety driver at the wheel and a safety operator in the front passenger seat. The Motional vehicle was northbound on [XXX], in the left-most of two left turn lanes, turning onto [XXX] at 10 MPH. The Motional vehicle then braked for an approaching taxi in the adjacent turn lane that was perceived to be crossing into the lane of the Motional vehicle and was rear-ended by a silver Toyota traveling behind it.
30412-5661ADSCruise LLC2023-06 04:31Chandler, AZ2020 Cruise AVADSHeavy TruckNo Injuries Reported14IntersectionRedacted by NHTSA as confidential business information
30412-5687 v2ADSCruise LLC2023-06 22:22San Francisco, CA2022 Cruise AVADSVanUnknown0IntersectionRedacted by NHTSA as confidential business information
30412-5782ADSCruise LLC2023-06 09:36San Francisco, CA2022 Cruise AVADSOther, see NarrativeNo Injuries Reported7StreetRedacted by NHTSA as confidential business information
30412-5799ADSCruise LLC2023-06 22:37San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported7StreetRedacted by NHTSA as confidential business information
30412-5828ADSCruise LLC2023-06 22:37San Francisco, CA2022 Cruise AVADSSUVNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-5831ADSCruise LLC2023-06 23:30San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30412-5832ADSCruise LLC2023-06 00:50San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30412-5833ADSCruise LLC2023-06 23:08San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported6StreetRedacted by NHTSA as confidential business information
30412-5836ADSCruise LLC2023-06 21:04Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30531-5669ADSTransdev Alternative Services2023-06 13:17Phoenix, AZ2021 Jaguar I-PACEADSPassenger CarUnknown13Highway / Freeway
On [XXX], 2023 at 1:17 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, AZ was in a collision involving a passenger car on [XXX] in the southbound direction near the [XXX]. The Waymo AV was traveling i…On [XXX], 2023 at 1:17 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, AZ was in a collision involving a passenger car on [XXX] in the southbound direction near the [XXX]. The Waymo AV was traveling in the rightmost lane (out of 5 lanes) in the southbound direction of [XXX], and the left 3 lanes were closed due to a work zone. The vehicle traveling ahead in the same lane as the ADV made an abrupt lane change to the left, revealing a stack of slow-moving vehicles in the Waymo's lane. The test driver of the Waymo AV took manual control of the vehicle and started to decelerate and steer toward the right shoulder in response to slow traffic ahead. A passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo's Level 4 ADS was not engaged and a test driver (in the driver's seating position) was operating the Waymo AV in manual mode. The Waymo AV and the other vehicle sustained damage. Transdev Alternative Services is reporting this collision under the 5-day reporting guidelines because a vehicle was towed but nobody was transported to the hospital from the scene of the collision and there was no Vulnerable Road User involved. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of collision report ID: 30270-5650-1.
30531-5814ADSTransdev Alternative Services2023-06 20:58Phoenix, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported35Street
On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle ( Waymo AV ) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and prep…On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle ( Waymo AV ) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and preparing to make a right lane change. As it initiated the lane change, the rear passenger side tire struck small debris in the road. 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 s tire immediately deflated. Transdev Alternative Services is reporting this event under Request No 1 of Standing General Order 2021 01 because a vehicle involved was towed away. This is a duplicate report to Waymo 30270-5813-1 report.
30531-5818ADSTransdev Alternative Services2023-06 23:18Los Angeles, CA2021 Jaguar I-PaceADSPickup TruckMinor0Intersection
On June [XXX], 2023 at 11:18 PM PT a Waymo Autonomous Vehicle ( Waymo AV ) operating in Los Angeles, California was in a collision involving a pick-up truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX…On June [XXX], 2023 at 11:18 PM PT a Waymo Autonomous Vehicle ( Waymo AV ) operating in Los Angeles, California was in a collision involving a pick-up truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and stopped at a stop sign at the intersection of [XXX] when a pick-up truck approached the Waymo AV 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). The Waymo AV test driver then took manual control of the Waymo AV and the pick-up truck then made contact with the rear of the Waymo AV again. The Waymo AV test driver pulled towards the side of the road and stopped. The pick-up truck followed the Waymo AV and repeatedly made further contact with the Waymo AV. At one point the pick-up truck driver verbally harassed the Waymo AV test driver. The Waymo AV test driver was eventually able to elude the pickup truck and wait nearby for law enforcement to arrive. The Waymo AV sustained damage. Transdev Alternative Services is reporting a duplicate report from Waymo LLC report number: 30270-5817-1.
30531-5966ADSTransdev Alternative Services2023-06 21:39Tempe, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported56Highway / Freeway
On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane whe…On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane when road debris appeared from under the passenger vehicle in front of the Waymo AV. The Waymo AV test driver transitioned to manual mode just before the Waymo AV made contact with the road debris. 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 is a duplicate of 30270-5962-1.
30711-5675ADSPony.ai2023-06 11:39Fremont, CA2021 Hyundai Kona EVADSPassenger CarNo Injuries Reported0Street
On [XXX], 2023, while in supervised ("Drivered") autonomous mode with Pony.ai's ADS engaged, a Pony.ai AV was rear-ended twice, in quick succession, by a passenger vehicle. The incident occurred at the intersection of [X…On [XXX], 2023, while in supervised ("Drivered") autonomous mode with Pony.ai's ADS engaged, a Pony.ai AV was rear-ended twice, in quick succession, by a passenger vehicle. The incident occurred at the intersection of [XXX] and [XXX] in Fremont, CA. At the time of the incident, the Pony.ai AV was stopped at a red light on [XXX] at the intersection with [XXX], heading west-southwest. The incident occurred when a passenger vehicle directly behind the Pony.ai AV proceeded to rear-end the Pony.ai AV two times in quick succession. Following the incident, the Pony.ai safety operator disengaged the AV from autonomous mode. Concerned for his safety, the Pony.ai operator immediately drove the vehicle back to the Pony.ai Fremont office (a distance of approximately 1 mile). The passenger vehicle which had rear-ended the Pony.ai AV followed it back to Pony.ai's Fremont office. After a brief interaction during which the driver of the striking vehicle threatened Pony.ai employees, the driver of that vehicle drove away. The Fremont police were called by Pony.ai staff, and they responded and took a report about the incident. There were no injuries reported. The Fremont Police Department report number is [XXX].
30792-5747ADSWeRide Corp2023-06 14:06san jose, CA2019 NISSAN LEAFADSHeavy TruckModerate0Street
At 2:06pm a WeRide driverless vehicle (car 1) was stopped behind a big rig truck (vehicle 2). As our vehicle (car 1) was stopped behind the big rig truck, the big rig truck proceeded to reverse backwards and eventually c…At 2:06pm a WeRide driverless vehicle (car 1) was stopped behind a big rig truck (vehicle 2). As our vehicle (car 1) was stopped behind the big rig truck, the big rig truck proceeded to reverse backwards and eventually collided into the WeRide vehicle (car 1). Both parties pulled over both involved vehicles and cooperated to exchange information. The damage sustained to the WeRide vehicle was moderate and the big rig truck did not have any damage.
33495-6720ADSApollo Autonomous Driving USA2023-06 15:39San Francisco, CA2020 Chrysler PacificaADSNon-Motorist: OtherNo Injuries Reported9Intersection
On June [XXX], 2023 at 3:39 PM PDT, an Apollo Autonomous Vehicle ("Apollo AV") operating in San Francisco, California, was in a collision involving a scooter on [XXX] near [XXX]. The Apollo AV was traveling westbound on…On June [XXX], 2023 at 3:39 PM PDT, an Apollo Autonomous Vehicle ("Apollo AV") operating in San Francisco, California, was in a collision involving a scooter on [XXX] near [XXX]. The Apollo AV was traveling westbound on [XXX] passing the intersection with [XXX]. The intersection has stop signs clearly installed at all four ways, which require vehicles to make full stop before entering the intersection. The Apollo AV made a full stop, entered and passed approximately 75% of the intersection. A person on scooter coming southbound from [XXX], approached the intersection. The person on scooter entered the intersection without stopping, then made contact with the passenger rear-side of Apollo AV. Our Apollo AV operator immediately disengaged the AV, pulled over to the closest safe place to park, got out of the car to check the person on scooter, who already left the scene on his scooter without exchanging any information. The Apollo AV had small minor paint scratch, which do not need repair. The police were not called.
540-5667ADSGeneral Motors, LLC2023-06 04:31Chandler, AZ2020 Cruise AVADSHeavy TruckNo Injuries Reported14Intersection
On June 6, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the Order). General Motors LLC (GM) manufactured th…On June 6, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5661-1)
540-5688 v2ADSGeneral Motors, LLC2023-06 22:22San Francisco, CA2022 Cruise AVADSVanUnknown0Intersection
On June 16, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufact…On June 16, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5687-2)
540-5805ADSGeneral Motors, LLC2023-06 22:37San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported7Street
On June 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On June 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (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-5799).

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.