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

1995 reports, showing 1601 to 1700.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
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-6044ADSCruise LLC2023-07 22:41San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported1IntersectionRedacted by NHTSA as confidential business information
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-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-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-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).
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.
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
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.
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-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).
540-5940ADSGeneral Motors, LLC2023-06 09:36San Francisco, CA2022 Cruise AVADSOther, see NarrativeUnknown7Street
On July 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…On July 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-5782-1)
540-5941ADSGeneral Motors, LLC2023-06 22:37San Francisco, CA2022 Cruise AVADSSUVNo Injuries Reported0Street
On July 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…On July 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-5828-1)
540-5942ADSGeneral Motors, LLC2023-06 23:30San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported1Street
On July 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…On July 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-5831-1)
540-5948ADSGeneral Motors, LLC2023-06 00:50San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported1Street
On July 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…On July 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-5832-1)
540-5950ADSGeneral Motors, LLC2023-06 23:08San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported6Street
On July 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…On July 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-5833-1)
30270-5429 v2ADSWaymo LLC2023-05 10:32San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported4Street
The content of this report is unchanged from the initial report submitted on May 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle (Waymo AV…The content of this report is unchanged from the initial report submitted on May 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling in autonomous mode in the middle lane on westbound [XXX] between [XXX] and [XXX]. A slower traveling van in the left adjacent lane began to initiate a right lane change in front of the Waymo AV, and the Waymo AV test driver transitioned to manual mode and braked. The SUV 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 not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV and SUV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5456 v2ADSWaymo LLC2023-05 15:27San Francisco, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported0Street
Other than a correction to the reported mileage, the content of this report is unchanged from the initial report submitted on May 8, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at …Other than a correction to the reported mileage, the content of this report is unchanged from the initial report submitted on May 8, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2023 at 3:27 PM PDT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was traveling westbound in the left lane on [XXX] and had just passed [XXX] when it detected an oncoming pickup truck traveling eastbound in the Waymo AVs lane. The Waymo AV stopped and the pickup truck re-entered the correct lane for eastbound traffic and passed the Waymo AV. The pickup truck was immediately followed by a large group of cyclists traveling eastbound in multiple lanes of the roadway, including the right lanes and on the wrong side of the double-yellow centerline. The Waymo AV remained stopped as the oncoming cyclists rode around both sides of the Waymo AV. One cyclist then made contact with the front of the stationary Waymo AV, and then immediately left the scene. 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. 1 of Standing General Order 2021-01 because a vulnerable road user was involved. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5758ADSWaymo LLC2023-05 20:48San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported6Street
On[XXX], 2023 at 8:48 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}. While traveling west on [XXX}, the Waymo AV was…On[XXX], 2023 at 8:48 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}. While traveling west on [XXX}, the Waymo AV was executing a pullover maneuver in autonomous mode and made contact with the left rear bumper of a parked vehicle. 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-5762ADSWaymo LLC2023-05 10:56San Francisco, CA2021 Jaguar I-PaceADSAnimalNo Injuries Reported23Street
On [XXX] at 10:56 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small …On [XXX] at 10:56 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog, which did not survive. 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. 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-5422 v3ADSCruise LLC2023-05 02:44San Francisco, CA2022 Cruise AVADSOther Fixed ObjectMinor7IntersectionRedacted by NHTSA as confidential business information
30412-5430 v2ADSCruise LLC2023-05 09:32San Francisco, CA2023 Cruise AVADSOther, see NarrativeMinor5IntersectionRedacted by NHTSA as confidential business information
30412-5624ADSCruise LLC2023-05 21:24San Francisco, CA2022 Cruise AVADSPassenger CarMinor15StreetRedacted by NHTSA as confidential business information
30412-5697ADSCruise LLC2023-05 03:34San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported9StreetRedacted by NHTSA as confidential business information
30531-5440 v2ADSTransdev Alternative Services2023-05 10:32San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported4Street
The content of this report is unchanged from the initial report. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [X…The content of this report is unchanged from the initial report. On May [XXX], 2023 at 10:32 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was fraveling in autonomous mode in the middle lane on westbound [XXX] between [XXX] and [XXX]. A slower traveling van in the left adjacent lane began to initiate a right lane change in front of the Waymo AV, and the Waymo AV test driver transitioned to manual mode and braked. The SUV 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 not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV and SUV sustained damage. This is a duplicate of report 30270-5429-1.
30531-5770ADSTransdev Alternative Services2023-05 10:56San Francisco, CA2021 Jaguar I-PaceADSAnimalNo Injuries Reported23Street
On [XXX], 2023 at 10:56 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when …On [XXX], 2023 at 10:56 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a small dog on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] when a small dog ran into the street in front of the Waymo AV. The Waymo AV then made contact with the dog, which did not survive. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of NHTSA report ID 30270-5762-1.
30610-5716ADSZoox, Inc.2023-05 11:40San Francisco, CA2017 Toyota HighlanderADSSUVMinor1Street
A Zoox vehicle in autonomy was coming to a gradual stop for traffic ahead when it was rear ended by vehicle 2 at low speed. There was minor damage to the striking vehicle and police were not called. A Zoox operator repor…A Zoox vehicle in autonomy was coming to a gradual stop for traffic ahead when it was rear ended by vehicle 2 at low speed. There was minor damage to the striking vehicle and police were not called. A Zoox operator reported "sore neck and back".
30792-5565ADSWeRide Corp2023-05 11:41San Francisco, CA2023 Nissan LeafADSNon-Motorist: CyclistNo Injuries Reported0Street
On Monday May [XXX] at 11:41am a Weride autonomous vehicle (Vehicle 1) was in Autonomous Mode stopped at the intersection of [XXX] towards [XXX] appropriately yielding to a illegally U turning skateboard on [XXX] North t…On Monday May [XXX] at 11:41am a Weride autonomous vehicle (Vehicle 1) was in Autonomous Mode stopped at the intersection of [XXX] towards [XXX] appropriately yielding to a illegally U turning skateboard on [XXX] North to South direction in front of the AV (Vehicle 1). While yielding, a bicyclist was coming from behind our AV (Vehicle 1) head was turned left possibly looking for cross traffic. When the cyclist turned his head forward, it was too late to react in time to our stopped vehicle(Vehicle 1) with the given distance and speed they were traveling at in which the cyclist collided with our vehicle (Vehicle 1). Our Weride safety officer immediately disengaged and hand signaled to the bicyclist to pull over to the closest safe place to park as to not obstruct traffic. As our safety officer parked and got out of the car to check on the bicyclist, the bicyclist was already on in motion on his bicycle and "fist bumped" our safety officer while passing by him and leaving the scene without exchanging any information.
540-5425 v3ADSGeneral Motors, LLC2023-05 02:44San Francisco, CA2022 Cruise AVADSOther Fixed ObjectMinor7Intersection
On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Crui…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5422-3)
540-5445 v2ADSGeneral Motors, LLC2023-05 09:32San Francisco, CA2023 Cruise AVADSOther, see NarrativeMinor5Intersection
On May 10, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured th…On May 10, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10-day updated Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5430-2)
540-5639ADSGeneral Motors, LLC2023-05 21:24San Drancisco, CA2022 Cruise AVADSPassenger CarMinor15Street
On May 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 May 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-5624-1)
540-5726ADSGeneral Motors, LLC2023-05 03:34San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported9Street
On June 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…On June 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-5697-1)
30270-5202 v2ADSWaymo LLC2023-04 10:46San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report submitted on April 6, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle (Waym…The content of this report is unchanged from the initial report submitted on April 6, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the leftmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding south on [XXX] was green for the Waymo AV as it approached the intersection. As the Waymo AV approached, an individual riding a motorized scooter traveling north on [XXX] proceeded to turn left onto westbound [XXX], across the paths of the Waymo AV and other oncoming vehicles. The Waymo AV began to brake, and the Waymo AV test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car traveling directly behind the Waymo AV then made contact with the rear of the Waymo AV. The individual riding the scooter was not contacted by the Waymo AV or any other vehicle. 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, and the individual on the motorized scooter left the scene. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a Vulnerable Road User was involved. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5208 v2ADSWaymo LLC2023-04 10:48San Francisco, CA2021 Jaguar I-PaceADSHeavy TruckNo Injuries Reported0Street
The content of this report is unchanged from the initial report submitted on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:48 AM PST a Waymo Autonomous Vehicle (Waymo …The content of this report is unchanged from the initial report submitted on [XXX], 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On April [XXX], 2023 at 10:48 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was proceeding northwest on [XXX] near the intersection with [XXX] when it came to a stop to yield to a heavy truck traveling southeast on [XXX]. As the heavy truck drove past the Waymo AV, the drivers side section of the heavy truck made contact with the rear drivers side sensor of the Waymo AV. The heavy truck then left the scene. 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. 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-5584ADSWaymo LLC2023-04 22:56San Francisco, CA2021 Jaguar I-PACEADSSUVNo Injuries Reported0Intersection
On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV ca…On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV came to a stop to yield to an oncoming SUV in a narrow passageway. The SUV proceeded around the Waymo AV and made contact with the left rear sensor housing 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 driver of the SUV stopped briefly but left before sharing their information. The Waymo 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-5586ADSWaymo LLC2023-04 17:29Santa Monica, CA2021 Jaguar I-PACEADSSUVNo Injuries Reported0Intersection
On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in th…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in the rightmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding southwest on [XXX] was red as the Waymo AV approached the intersection and came to a stop. The signal for traffic proceeding southwest on [XXX] then turned green, and traffic in adjacent lanes began moving while the Waymo AV waited for traffic in its lane to begin to move. The SUV that had been stopped directly behind the Waymo AV began moving forward and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo 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-5592ADSWaymo LLC2023-04 17:29San Francisco, CA2021 Jaguar I-PACEADSSUVNo Injuries Reported0Street
On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] between [XXX…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling east on [XXX] between [XXX] and [XXX] when it approached an SUV that was stopped in the lane in front of the Waymo AV. The Waymo AV began passing the stopped SUV on the left when the SUV began reversing in the lane. The Waymo AV then stopped behind and to the left of the SUV, and the SUV continued reversing and began a turning maneuver to enter a parking space. The left side of the SUV made contact with the front right corner of the Waymo AV. At the time of the impact, the Waymo AV was stopped and the 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-5593ADSWaymo LLC2023-04 13:53San Francisco, CA2021 Jaguar I-PACEADSSUVNo Injuries Reported0Intersection
On April [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While the Waymo AV was parked at the right side cu…On April [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While the Waymo AV was parked at the right side curb of the road on [XXX], an SUV that was passing the parked Waymo AV in the rightmost lane made contact with the rear drivers side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV did not sustain damage 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.
30412-5220 v2ADSCruise LLC2023-04 4:45San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported3IntersectionRedacted by NHTSA as confidential business information
30412-5458ADSCruise LLC2023-04 00:35San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-5459ADSCruise LLC2023-04 23:35San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported10IntersectionRedacted by NHTSA as confidential business information
30412-5460ADSCruise LLC2023-04 20:13San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-5461ADSCruise LLC2023-04 21:59San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported4IntersectionRedacted by NHTSA as confidential business information
30531-5205 v2ADSTransdev Alternative Services2023-04 10:46San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
The content of this report is unchanged from the initial report. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenge…The content of this report is unchanged from the initial report. On April [XXX], 2023 at 10:46 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the leftmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding south on [XXX] was green for the Waymo AV as it approached the intersection. As the Waymo AV approached, an individual riding a motorized scooter traveling north on [XXX] proceeded to turn left onto westbound [XXX], across the paths of the Waymo AV and other oncoming vehicles. The Waymo AV began to brake, and the Waymo AV test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car traveling directly behind the Waymo AV then made contact with the rear of the Waymo AV. The individual riding the scooter was not contacted by the Waymo AV or any other vehicle. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both the Waymo AV and the passenger car sustained damage, and the individual on the motorized scooter left the scene. Transdev Alternative Services is reporting this crash under Request No 1 of Standing General Order 2021 01 because a Vulnerable Road User was involved. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30531-5088-1.
30531-5604ADSTransdev Alternative Services2023-04 17:29Santa Monica, CA2021 Jaguar I-PACEADSSUVNo Injuries Reported0Intersection
On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in th…On April [XXX], 2023 at 5:29 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwest on [XXX] in the rightmost lane as it was approaching the intersection with [XXX]. The signal for traffic proceeding southwest on [XXX] was red as the Waymo AV approached the intersection and came to a stop. The signal for traffic proceeding southwest on [XXX] then turned green, and traffic in adjacent lanes began moving while the Waymo AV waited for traffic in its lane to begin to move. The SUV that had been stopped directly behind the Waymo AV began moving forward and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo 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 report ID 30270-5586-1.
30531-5605ADSTransdev Alternative Services2023-04 22:56San Francisco, CA2021 Jaguar I-PACEADSSUVNo Injuries Reported0Intersection
On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV …On April [XXX], 2023 at 10:56 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While traveling northwest on [XXX], the Waymo AV came to a stop to yield to an oncoming SUV in a narrow passageway. The SUV proceeded around the Waymo AV and made contact with the left rear sensor housing 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 driver of the SUV stopped briefly but left before sharing their information. The Waymo sustained damage. Transdev Alternative Serivces 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 ID 30270-5584-1.
30610-5232 v2ADSZoox, Inc.2023-04 11:19San Francisco, CA2017 Toyota HighlanderADSOther, see NarrativeNo Injuries Reported0Intersection
A Zoox vehicle in autonomy was proceeding northbound on [XXX] in stop-and-go traffic through an active construction zone. At the same time, an e-scooter traveling near the right curb was passing other slow traffic behind…A Zoox vehicle in autonomy was proceeding northbound on [XXX] in stop-and-go traffic through an active construction zone. At the same time, an e-scooter traveling near the right curb was passing other slow traffic behind the Zoox vehicle. Before the e-scooter could also pass the Zoox vehicle on the right, the e-scooter weaved away from the curb, seemingly to avoid a drainage grate, and came within a close following distance behind the Zoox vehicle. As the Zoox vehicle came to a stop again for traffic ahead the e-scooter rider did not stop, and the e-scooter made contact with the right rear tail light of the Zoox vehicle. The e-scooter rider remained upright, did not stop to exchange information, and immediately rode off while the Zoox vehicle was still stopped. There were no injuries and police were not called. The damage to the Zoox vehicle was limited to a cracked tail light lens. This 10-Day update provides complete information for this incident.
540-5227 v2ADSGeneral Motors, LLC2023-04 4:45San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported3Intersection
On April 18, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufact…On April 18, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file:30412-5220-2)
540-5488ADSGeneral Motors, LLC2023-04 00:35San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported0Street
On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5458-1)
540-5489ADSGeneral Motors, LLC2023-04 23:35San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported10Intersection
On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5459-1)
540-5490ADSGeneral Motors, LLC2023-04 20:13San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0Street
On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5460-1)
540-5491ADSGeneral Motors, LLC2023-04 21:59San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported4Intersection
On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-opera…On May 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5461-1)
30270-5114 v2ADSWaymo LLC2023-03 20:04San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries ReportedStreet
The content of this report is unchanged from the initial report submitted on March 21, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On March [XXX], 2023 at approximately 8:04 PM PST a Waymo Autonomous…The content of this report is unchanged from the initial report submitted on March 21, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On March [XXX], 2023 at approximately 8:04 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pothole on [XXX] near [XXX]. The Waymo AV was traveling in the second lane on a four-lane section of northbound [XXX] when the passenger side rear tire made contact with a pothole. The tire began to deflate and the Waymo AV pulled over on a side street. At the time of impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. 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-5318ADSWaymo LLC2023-03 20:26San Francisco, CA2021 Jaguar I-PaceADSOther Fixed ObjectNo Injuries Reported2Parking Lot
On March [XXX], 2023 at 8:27 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco was in a collision involving a fixed object on [XXX] near [XXX]. As the Waymo AV was leaving a parking lot to turn left…On March [XXX], 2023 at 8:27 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco was in a collision involving a fixed object on [XXX] near [XXX]. As the Waymo AV was leaving a parking lot to turn left onto [XXX], the front of the Waymo AV made contact with a chain that was connected between a parking lot road sign and a temporary pole. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The road sign fell down due to tension on the chain. 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-5320ADSWaymo LLC2023-03 21:28San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On March [XXX], 2023 at 9:28 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the dedicated l…On March [XXX], 2023 at 9:28 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane facing west on [XXX], awaiting a green signal to turn onto [XXX]. The signal for traffic proceeding west on [XXX] turned green, and traffic in adjacent lanes began moving. The left turn arrow signal for the dedicated turn lane occupied by the Waymo AV remained red. The passenger car that had been stopped directly behind the Waymo AV began moving forward. 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, and a test driver was present (in the drivers seating position). The passenger car sustained minor damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-5322ADSWaymo LLC2023-03 2:19San Bruno, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported64Highway / Freeway
On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was travelin…On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was traveling south on [XXX] in the rightmost exit lane for [XXX] towards [XXX] when it made contact with road debris (tire scrap). 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. 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-5323ADSWaymo LLC2023-03 17:10San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported8Intersection
On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling …On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] in autonomous mode, merging into the rightmost lane. As the Waymo AV merged, the test driver transitioned from autonomous mode to manual mode and began accelerating. The front of the Waymo AV made contact with the rear of a passenger car that was stopped in the rightmost lane. 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-5325ADSWaymo LLC2023-03 10:43Los Angeles, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Intersection
On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a thre…On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a three-lane road behind a passenger vehicle for a red light facing southwest on [XXX] at [XXX] in autonomous mode. The light turned green while cross-traffic remained backed up in the intersection. The Waymo AV nudged forward and slowed to a stop, yielding for the blocking cross traffic. An SUV that had been stopped behind the Waymo AV proceeded forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained 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.
30412-4960 v2ADSCruise LLC2023-03 01:06San Francisco, CA2022 Cruise AVADSPassenger CarNo Injuries Reported3IntersectionRedacted by NHTSA as confidential business information
30412-5101 v2ADSCruise LLC2023-03 3:26San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported21IntersectionRedacted by NHTSA as confidential business information
30412-5136 v2ADSCruise LLC2023-03 04:29San Francisco, CA2022 Cruise AVADSOther, see NarrativeNo Injuries Reported15StreetRedacted by NHTSA as confidential business information
30412-5140 v2ADSCruise LLC2023-03 14:46San Francisco, CA2023 Cruise AVADSBusNo Injuries Reported10StreetRedacted by NHTSA as confidential business information
30412-5229ADSCruise LLC2023-03 04:23San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-5240ADSCruise LLC2023-03 23:51San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-5241ADSCruise LLC2023-03 21:49San Francisco, CA2023 Cruise AVADSOther, see NarrativeNo Injuries Reported10StreetRedacted by NHTSA as confidential business information

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.