The MachineRecord
NHTSA Standing General Order 2021-01

The SGO file, in a form you can search

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

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

1674 reports, showing 1001 to 1100.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
30412-6525ADSCruise LLC2023-10 16:31San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported13StreetRedacted by NHTSA as confidential business information
30412-6596ADSCruise LLC2023-10 05:01Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6597ADSCruise LLC2023-10 02:24Houston, TX2023 Cruise AVADSPassenger CarNo Injuries Reported5StreetRedacted by NHTSA as confidential business information
30412-6598ADSCruise LLC2023-10 11:37San Francisco, CA2023 Cruise AVADSVanNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6613ADSCruise LLC2023-10 22:19San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported22IntersectionRedacted by NHTSA as confidential business information
30412-6614ADSCruise LLC2023-10 01:51Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6616ADSCruise LLC2023-10 08:23San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6617ADSCruise LLC2023-10 23:40San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6618ADSCruise LLC2023-10 01:29Santa Monica, CA2022 Cruise AVADSSUVNo Injuries Reported12IntersectionRedacted by NHTSA as confidential business information
30413-6684ADSMay Mobility2023-10 10:03Grand Rapids, MN2021 Toyota SiennaADSOther Fixed ObjectNo Injuries Reported27Street
The May vehicle was traveling eastbound on [XXX] in autonomy. The vehicles internal facing cameras show that the operator started to fall asleep while applying physical input to the steering wheel. The road started to be…The May vehicle was traveling eastbound on [XXX] in autonomy. The vehicles internal facing cameras show that the operator started to fall asleep while applying physical input to the steering wheel. The road started to bend to the left. The physical input from the operator was enough to deviate the vehicle from its intended path but not enough to trigger an intervention and take the vehicle out of autonomy. The vehicle, going straight as the road curved, then struck the curb, resulting in minor vehicle damage. Due to the vehicle being off path, the vehicle begins to stop. This occurs as the operator wakes up. The operator was not injured and no third parties were impacted or otherwise affected by the incident. The local May Mobility site staff did not notice any signs of fatigue from this operator prior to going out in the vehicle. The operator had responded to audio check-ins from site staff at a regular interval. We are exploring additional risk mitigation options for in-cabin health monitoring, in addition to the existing cameras and radio check-ins.
30531-6532 v2ADSTransdev Alternative Services2023-10 9:24San Francisco, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported13Intersection
The content of this report is unchanged from the initial report submitted [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating …The content of this report is unchanged from the initial report submitted [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was in autonomous mode on eastbound [XXX] preparing to make a right turn onto southbound [XXX] and had stopped to yield, first for pedestrians to cross [XXX] and then for a cyclist approaching from behind traveling eastbound on the sidewalk of [XXX]. As the pedestrians finished crossing [XXX] but before the cyclist had reached [XXX], the Waymo AV test driver took manual control of the Waymo AV and began to accelerate and perform the right turn onto [XXX]. After the Waymo AV entered the crosswalk, the cyclist entered the crosswalk and made contact with the passenger's rear quarter panel of the Waymo AVE. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the vehicle. Transdev Alternative Services is reporting a duplicate report from report number: 30270-6529-1.
30531-6691ADSTransdev Alternative Services2023-10 07:48San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported23Intersection
On October [XXX], 2023 at 7:48 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] i…On October [XXX], 2023 at 7:48 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in the rightmost lane. As the SUV in the left adjacent lane traveling alongside the Waymo AV initiated a right lane change, the front passenger's side of the SUV made contact with the front driver's side of the Waymo AV. At the time of the impact, the Waymo's Level 4 ADS was not engaged as the test driver transitioned the Waymo AV to manual mode just before the contact. Both vehicles sustained damage. This report is a duplicate of NHTSA Report ID: 30270-6665-1.
30610-6635ADSZoox, Inc.2023-10 09:53Seattle, WA2017 Toyota HighlanderADSPassenger CarNo Injuries Reported12Street
A Zoox vehicle in autonomy was traveling in the left travel lane of westbound [XXX] between [XXX] and [XXX] while passing a parked wide delivery truck, when a passenger car traveling ahead in the right lane abruptly stee…A Zoox vehicle in autonomy was traveling in the left travel lane of westbound [XXX] between [XXX] and [XXX] while passing a parked wide delivery truck, when a passenger car traveling ahead in the right lane abruptly steered into the Zoox travel lane without using a turn indicator. The Zoox vehicle braked aggressively in autonomy and the safety operator disengaged and conducted additional manual braking, but the collision was unavoidable. The driver of the passenger car left the scene without exchanging information. The Zoox vehicle sustained moderate damage. There were no injuries reported and the police were not called.
30610-6638ADSZoox, Inc.2023-10 20:12San Francisco, CA2017 Toyota HighlanderADSSUVNo Injuries Reported17Street
A Zoox vehicle was being driven in manual mode eastbound on [XXX] between [XXX] and [XXX] when contact was made with the left side mirror of a parked car. There was minor damage to the Zoox vehicle's sensor housing and p…A Zoox vehicle was being driven in manual mode eastbound on [XXX] between [XXX] and [XXX] when contact was made with the left side mirror of a parked car. There was minor damage to the Zoox vehicle's sensor housing and passenger side mirror. There were no injuries and police were not called.
31101-7044 v2ADSAvride Inc.2023-10 12:50Austin, TX2020 Hyundai SonataADSPassenger CarNo Injuries Reported25Street
Our car was moving down the street with approximate speed 25mph when it was tailgated. Our driver was not injured, and the driver in the other car showed no visible injuries. However, she called an ambulance due to her p…Our car was moving down the street with approximate speed 25mph when it was tailgated. Our driver was not injured, and the driver in the other car showed no visible injuries. However, she called an ambulance due to her pregnancy. The airbags did not deploy in either vehicle. The police report says following: AFTER VIEWING VIDEO FROM UNIT 2 WEEKS LATER, IT WAS DISCOVERED THAT UNIT 1 WAS TRAVELING EAST ON [XXX] IN THE LEFT LANE. UNIT 2 WAS IN FRONT OF UNIT 1 TRAVELING EAST ON [XXX] IN THE LEFT LANE. UNIT 2 SLOWED TO TURN LEFT INTO A DRIVE WAY. UNIT 1 THEN STRUCK THE BACK RIGHT OF UNIT 2. THIS DIFFERED FROM STATEMENTS GIVEN ON SCENE. There is also code 44 in the police report, which stays for Followed Too Closely
33495-6726ADSApollo Autonomous Driving USA2023-10 12:01San Francisco, CA2016 Lincoln MKZ HybridUnknown, see NarrativeOther, see NarrativeNo Injuries Reported15Intersection
An Apollo autonomous vehicle ("AV") was traveling westbound on [XXX] in San Francisco in conventional mode with a safety operator driving. At the intersection with [XXX], the right front of the AV made contact with the …An Apollo autonomous vehicle ("AV") was traveling westbound on [XXX] in San Francisco in conventional mode with a safety operator driving. At the intersection with [XXX], the right front of the AV made contact with the curb and the AV traveled onto the curb. The safety operator was able to drive off the curb and back onto the street. No other vehicles or property were involved. There were no injuries and the police were not called. The AV sustained minor damage to right wheel fender shield and the right lower bumper.
540-6531ADSGeneral Motors, LLC2023-10 16:31San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported13Street
On October 18, 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) manufactur…On October 18, 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-6525-1).
540-6629ADSGeneral Motors, LLC2023-10 01:51Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On November 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On November 13, 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-6614-1)
540-6630ADSGeneral Motors, LLC2023-10 08:23San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On November 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On November 13, 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-6616-1)
540-6632ADSGeneral Motors, LLC2023-10 23:40San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0Intersection
On November 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On November 13, 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-6617-1)
540-6633ADSGeneral Motors, LLC2023-10 01:29Santa Monica, CA2022 Crui9se AVADSSUVNo Injuries Reported12Intersection
On November 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On November 13, 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-6618)
540-6642ADSGeneral Motors, LLC2023-10 05:01Austin, TX2023 Cruise AVADSPickup TruckNo Injuries Reported0Intersection
On November 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On November 13, 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-6596-1). .
540-6644ADSGeneral Motors, LLC2023-10 02:24Houston, TX2023 Cruise AVADSPassenger CarNo Injuries Reported5Street
On November 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On November 13, 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-6597-1).
540-6645ADSGeneral Motors, LLC2023-10 11:37San Francisco, CA2023 Cruise AVADSVanNo Injuries Reported0Street
On November 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On November 13, 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-6598-1).
540-6646ADSGeneral Motors, LLC2023-10 22:19San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported22Intersection
On November 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On November 13, 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-6613-1).
988-6565ADSPACCAR Incorporated2023-10 15:08Fort Worth, TX2019 KENWORTH T680ADSHeavy TruckNo Injuries Reported34Highway / Freeway
On October 30, 2023, PACCAR was informed by Kodiak, Inc of the incident that occurred October [XXX]. On October [XXX], 2023 at 3:08 PM CT, a tractor-trailer entered the lane of Kodiak Autonomous Vehicle ("Kodiak AV"), K…On October 30, 2023, PACCAR was informed by Kodiak, Inc of the incident that occurred October [XXX]. On October [XXX], 2023 at 3:08 PM CT, a tractor-trailer entered the lane of Kodiak Autonomous Vehicle ("Kodiak AV"), Kenworth Class 8 semi-truck and made minor contact. The Kodiak AV was driving westbound on [XXX] in Fort Worth, Texas, near [XXX]. The Kodiak AV was operating with a safety driver (in the driver's seating position), who transitioned the vehicle from autonomous to manual mode approximately 5 seconds prior to impact, due to the other truck encroaching on the Kodiak AV's lane. At the time of impact, the Kodiak AV was in manual mode. No injuries occurred in the incident. The Kodiak AV pulled over after the incident, and the other driver continued down the road. The Kodiak AV's mirror-mounted SensorPod sustained minor scratches. PACCAR may supplement or correct reporting with additional information as it may become available from Kodiak.
30270-6351ADSWaymo LLC2023-09 20:34San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Street
On September [XXX], 2023 at 8:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. While the Waymo AV was pulled over in the righ…On September [XXX], 2023 at 8:34 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. While the Waymo AV was pulled over in the right lane on northbound [XXX], an SUV that was passing the parked Waymo AV made contact with the rear drivers side 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. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6352ADSWaymo LLC2023-09 18:26San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On September [XXX], 2023 at 6:26 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]. While the Waymo AV was stopped in park …On September [XXX], 2023 at 6:26 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]. While the Waymo AV was stopped in park waiting to pick up a passenger near the right side curb of the road on westbound [XXX], a passenger car that was passing the stopped Waymo AV 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. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6368ADSWaymo LLC2023-09 17:02Tempe, AZ2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported12Street
On September [XXX], 2023 at 5:02 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] towa…On September [XXX], 2023 at 5:02 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] toward [XXX] when a pickup truck drove alongside the Waymo AV. The passengers side of the pickup truck made contact with the drivers side of the Waymo AV. The pickup truck had been following and overtaking the Waymo AV for several minutes, and the pickup truck passengers occasionally threw items at the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 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-6405ADSWaymo LLC2023-09 19:12San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported8Intersection
On September [XXX], 2023 at 7:12 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 westbound on …On September [XXX], 2023 at 7:12 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 westbound on [XXX] and approached the stop sign intersection at [XXX]. As the Waymo AV came to a full stop, a city bus was proceeding through the intersection, traveling eastbound on [XXX]. As the city bus continued to proceed through the intersection, the Waymo AV began to proceed forward. The Waymo AV entered the intersection as the city bus proceeded through and exited the intersection, and at the same time, a passenger car traveling northbound on [XXX] that had been occluded by the city bus had also entered the intersection. The passenger car and the Waymo AV then made contact in the middle of the intersection. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6514ADSWaymo LLC2023-09 22:48San Francisco, CA2021 Jaguar I-PaceADSBusNo Injuries Reported0Street
On September [XXX], 2023 at 10:48 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was stopped on the right lane of a m…On September [XXX], 2023 at 10:48 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was stopped on the right lane of a multi-lane road when a city bus attempted to pass using the adjacent left lane. The rear right fender of the bus made contact with the left rear sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6515ADSWaymo LLC2023-09 19:41San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On September [XXX], 2023 at 7:41 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 parked facing north on …On September [XXX], 2023 at 7:41 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 parked facing north on [XXX] when a passenger vehicle that was parked on the opposite side of the street started reversing, and reversed into the left rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6516ADSWaymo LLC2023-09 15:07Tempe, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported1Street
On September [XXX], 2023 at 3:07 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] when the…On September [XXX], 2023 at 3:07 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] when the Waymo AV slowed for stopped traffic ahead. The vehicle immediately behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6517ADSWaymo LLC2023-09 09:24San Francisco, CA2021 Jaguar I-PaceADSHeavy TruckNo Injuries Reported0Street
On September [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a truck on [XXX] an [XXX]. The Waymo AV had pulled over to the curb and par…On September [XXX], 2023 at 9:24 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a truck on [XXX] an [XXX]. The Waymo AV had pulled over to the curb and parked on the right side of [XXX] when a truck directly in front of the Waymo AV reversed and made contact with the front of the Waymo AV. 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-6518ADSWaymo LLC2023-09 20:20San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On September [XXX], 2023 at 8:20 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 parked on the right sid…On September [XXX], 2023 at 8:20 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 parked on the right side on [XXX] when a passenger vehicle that had been previously parked in the driveway on the opposite side of the street began reversing and reversed into the left rear door 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-6519ADSWaymo LLC2023-09 19:49Phoenix, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported0Street
On September [XXX], 2023 at 7:49 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a food truck trailer on [XXX] at [XXX]. The Waymo AV stopped facing north on [XXX] a…On September [XXX], 2023 at 7:49 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a food truck trailer on [XXX] at [XXX]. The Waymo AV stopped facing north on [XXX] after a pickup truck hauling a food truck trailer ahead of the Waymo AV came to a stop. The pickup truck and food truck trailer then began to reverse into the stationary Waymo AV and the left rear bumper of the food truck trailer made contact with the front bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6520ADSWaymo LLC2023-09 01:40Scottsdale, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Parking Lot
On September [XXX], 2023 at 1:40 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, California was in a collision involving a passenger car in a parking lot on [XXX] at [XXX]. The Waymo AV was stopped i…On September [XXX], 2023 at 1:40 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Scottsdale, California was in a collision involving a passenger car in a parking lot on [XXX] at [XXX]. The Waymo AV was stopped in a parking lot when a vehicle exiting a row of parked cars attempted to pass through a narrow space behind the rear of the Waymo AV. The front left bumper of the passenger car made contact with the right rear sensor 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-6521ADSWaymo LLC2023-09 10:25Phoenix, AZ2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported0Street
On September [XXX], 2023 at 10:25 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a cargo trailer on [XXX] at [XXX]. The Waymo AV was traveling south on [XXX] when a…On September [XXX], 2023 at 10:25 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a cargo trailer on [XXX] at [XXX]. The Waymo AV was traveling south on [XXX] when a pickup truck hauling a cargo trailer immediately ahead of the Waymo AV stopped and began to reverse. The Waymo AV came to a stop and the rear of the cargo trailer made contact with the front bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6522 v2ADSWaymo LLC2023-09 21:00San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On September [XXX], 2023 at 9:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX]. The Waymo AV was…On September [XXX], 2023 at 9:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX]. The Waymo AV was proceeding south on [XXX] in the leftmost lane and entered the slip lane to proceed north on [XXX]. As the Waymo AV came to a stop for a red light at the intersection with [XXX], the front of the passenger car which was following behind the Waymo AV made contact with the rear 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, and a test driver was present. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. The previously submitted version of this report incorrectly listed the wrong zip code, and "September 20th" was noted as the date of this event in the narrative. This updated submission has been corrected to reflect the correct zip code and date.
30412-6242ADSCruise LLC2023-09 21:42Houston, TX2023 Cruise AVADSPassenger CarNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30412-6262ADSCruise LLC2023-09 02:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported2IntersectionRedacted by NHTSA as confidential business information
30412-6363ADSCruise LLC2023-09 03:49Austin, TX2023 Cruise AVADSSUVNo Injuries Reported3IntersectionRedacted by NHTSA as confidential business information
30412-6371ADSCruise LLC2023-09 20:14Houston, TX2023 Cruise AVADSSUVNo Injuries Reported16IntersectionRedacted by NHTSA as confidential business information
30412-6384ADSCruise LLC2023-09 09:20Houston, TX2023 Cruise AVADSSUVNo Injuries Reported8IntersectionRedacted by NHTSA as confidential business information
30412-6436ADSCruise LLC2023-09 22:16San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6437ADSCruise LLC2023-09 23:02Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported6StreetRedacted by NHTSA as confidential business information
30412-6438ADSCruise LLC2023-09 17:32San Francisco, CA2022 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6439 v2ADSCruise LLC2023-09 00:05Tempe, AZ2022 Cruise AVADSAnimalNo Injuries Reported15StreetRedacted by NHTSA as confidential business information
30412-6440ADSCruise LLC2023-09 04:59Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported1StreetRedacted by NHTSA as confidential business information
30412-6441ADSCruise LLC2023-09 10:54Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6442ADSCruise LLC2023-09 23:56San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported10IntersectionRedacted by NHTSA as confidential business information
30412-6444ADSCruise LLC2023-09 23:44Austin, TX2023 Cruise AVADSSUVNo Injuries Reported25IntersectionRedacted by NHTSA as confidential business information
30412-6445 v2ADSCruise LLC2023-09 22:36Austin, TX2023 Cruise AVADSSUVNo Injuries Reported24IntersectionRedacted by NHTSA as confidential business information
30412-6446ADSCruise LLC2023-09 09:37San Francisco, CA2020 Cruise AVADSVanNo Injuries Reported10StreetRedacted by NHTSA as confidential business information
30412-6447ADSCruise LLC2023-09 08:42San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported3IntersectionRedacted by NHTSA as confidential business information
30531-6354ADSTransdev Alternative Services2023-09 20:34San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported0Street
On September [XXX], 2023 at 8:34 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. While the Waymo AV was pulled over in the rig…On September [XXX], 2023 at 8:34 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. While the Waymo AV was pulled over in the right lane on northbound [XXX], an SUV that was passing the parked Waymo AV made contact with the rear driver's side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vechile involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report ID 30270-6351-1.
30531-6533ADSTransdev Alternative Services2023-09 21:00San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Intersection
On September [XXX], 2023 at 9:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX]. The Waymo AV was…On September [XXX], 2023 at 9:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX]. The Waymo AV was proceeding south on [XXX] in the leftmost lane and entered the slip lane to proceed north on [XXX]. As the Waymo AV came to a stop for a red light at the intersection with [XXX], the front of the passenger car which was following behind the Waymo AV made contact with the rear of the Waymo AV. The Waymo AV sustained damage. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present. Transdev Alternative Services is reporting this crash under Request No 2 of Standing General Order 2021-01. This is a duplicate of report ID 30270-6522-1.
30590-6382ADSApple Inc.2023-09 11:33Emeryville, CA2017 Lexus RX 450hADSPickup TruckNo Injuries Reported0Highway / Freeway
Subject vehicle was on a testing mission in Emeryville, CA. The vehicle was traveling Westbound on [XXX] operated by the vehicle's Automated Driving System and supervised by a safety driver in the driver's designated sea…Subject vehicle was on a testing mission in Emeryville, CA. The vehicle was traveling Westbound on [XXX] operated by the vehicle's Automated Driving System and supervised by a safety driver in the driver's designated seating position, and with a safety operator in the front passenger seating position. Subject vehicle decelerated and came to a complete stop in response to traffic. Approximately three seconds later, with traffic remaining stopped ahead, a white Chevrolet Silverado made contact from the rear. Almost simultaneous with the crash, the safety driver disengaged the Automated Driving System through brake pedal force. After the crash, both vehicles proceeded to the side of the road to exchange information, and then took the closest exit to a nearby parking lot. Subject vehicle was towed given damage to the rear window. No injuries were reported, and law enforcement was not called to the scene. In addition to telematics and video, we have photographs of the damaged vehicles.
30610-6373ADSZoox, Inc.2023-09 15:20San Francisco, CA2017 Toyota HighlanderADSVanNo Injuries Reported0Street
A Zoox vehicle in autonomy was slowing to a gradual stop on eastbound [XXX] for a red light at [XXX] when it was rear-ended by vehicle 2 at approximately 10 mph. There was minor damage, no reported injuries, and police w…A Zoox vehicle in autonomy was slowing to a gradual stop on eastbound [XXX] for a red light at [XXX] when it was rear-ended by vehicle 2 at approximately 10 mph. There was minor damage, no reported injuries, and police were not called.
30711-6431ADSPony.ai2023-09 17:02Milpitas, CA2019 Lincoln MKZADSOther, see NarrativeNo Injuries Reported58Highway / Freeway
On September [XXX], 2023, preparing to enter the [XXX] while traveling northbound on the [XXX] in Milpitas, California, a Pony.ai autonomous vehicle ("AV") collided with road debris while operating in supervised autonomo…On September [XXX], 2023, preparing to enter the [XXX] while traveling northbound on the [XXX] in Milpitas, California, a Pony.ai autonomous vehicle ("AV") collided with road debris while operating in supervised autonomous ("Drivered") mode. Immediately prior to the incident, the AV safety driver noticed a flat item in the center part of the AV's lane of travel. The AV safety driver disengaged from autonomous mode and attempted to dodge the debris. However, the debris made contact with the rear bumper, slightly damaging it. Following the collision, the AV safety driver promptly drove the AV to Pony.ai's Fremont facility. There were no injuries reported.
30792-6492ADSWeRide Corp2023-09 13:54San Francisco, CA2023 Nissan LeafADSSUVNo Injuries Reported0Street
At 1:54pm, a WeRide vehicle (Car 1) was stopped on [XXX] left turning lane to [XXX]. As our vehicle (Car 1) was stopped for red traffic light, the toyota suv (Car 2) approaching from behind collided with our vehicle (Car…At 1:54pm, a WeRide vehicle (Car 1) was stopped on [XXX] left turning lane to [XXX]. As our vehicle (Car 1) was stopped for red traffic light, the toyota suv (Car 2) approaching from behind collided with our vehicle (Car 1). Both parties pulled over both involved vehicles and cooperated to exchange information. The damage sustained to the WeRide vehicle (Car 1) and toyota suv (Car 2) are minor.
33495-6725ADSApollo Autonomous Driving USA2023-09 12:25San Francisco, CA2017 Lincoln MKZ HybridUnknown, see NarrativeSUVNo Injuries Reported5Street
An Apollo autonomous vehicle ("AV") was traveling westbound on [XXX] in San Francisco in autonomous mode and stopped for a double-parked vehicle near [XXX]. An Apollo safety operator disengaged the AV from autonomous mod…An Apollo autonomous vehicle ("AV") was traveling westbound on [XXX] in San Francisco in autonomous mode and stopped for a double-parked vehicle near [XXX]. An Apollo safety operator disengaged the AV from autonomous mode into conventional mode with use of the steering wheel. Then the AV side-swiped the double-parked vehicle while in conventional mode. There were no injuries, and emergency services were not needed. Both the AV and the second vehicle sustained minor damage.
540-6244ADSGeneral Motors, LLC2023-09 21:42Houston, TX2023 Cruise AVADSPassenger CarNo Injuries Reported1Street
On September 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 12, 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-6242-1).
540-6290ADSGeneral Motors, LLC2023-09 02:35Austin, TX2023 Cruise AVADSSUVNo Injuries Reported2Intersection
On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6262-1)
540-6369ADSGeneral Motors, LLC2023-09 03:49Austin, TX2023 Cruise AVADSSUVNo Injuries Reported3Intersection
On September 22, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 22, 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-6363-1)
540-6372ADSGeneral Motors, LLC2023-09 20:14Houston, TX2023 Cruise AVADSSUVNo Injuries Reported16Intersection
On September 28, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 28, 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-6371-1)
540-6393ADSGeneral Motors, LLC2023-09 09:20Houston, TX2023 Cruise AVADSSUVNo Injuries Reported8Intersection
On October 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) manufacture…On October 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-6384-1).
540-6451ADSGeneral Motors, LLC2023-09 22:16San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported0Street
On October 12, 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…On October 12, 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-6436-1)
540-6452ADSGeneral Motors, LLC2023-09 23:02Austin, TX2023 Cruise AVADSPassenger CarNo Injuries Reported6Street
On October 12, 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) manufactur…On October 12, 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-6437-1)
540-6453ADSGeneral Motors, LLC2023-09 17:32San Francisco, CA2022 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On .October 12, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On .October 12, 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-6438-1)
540-6454 v2ADSGeneral Motors, LLC2023-09 00:05Tempe, AZ2022 Cruise AVADSAnimalNo Injuries Reported15Street
On October 16, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) ma…On October 16, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6439-2).
540-6455ADSGeneral Motors, LLC2023-09 04:59Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported1Street
On October 12, 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) manufactur…On October 12, 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-6440-1).
540-6461ADSGeneral Motors, LLC2023-09 10:54Austin, TX2023 Cruise AVADSHeavy TruckNo Injuries Reported0Street
On October 12, 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) manufactur…On October 12, 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-6441-1).
540-6462ADSGeneral Motors, LLC2023-09 23:56San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported10Intersection
On October 12, 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) manufactur…On October 12, 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-6442-1).
540-6467ADSGeneral Motors, LLC2023-09 23:44Austin, TX2023 Cruise AVADSSUVNo Injuries Reported25Intersection
On October 12, 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) manufactur…On October 12, 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-6444-1).
540-6468 v2ADSGeneral Motors, LLC2023-09 22:36Austin, TX2023 Cruise AVADSSUVNo Injuries Reported24Intersection
On November 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) m…On November 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6445-2)
540-6470ADSGeneral Motors, LLC2023-09 09:37San Francisco, CA2020 Cruise 8AVADSVanNo Injuries Reported10Street
On October 12, 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) manufactur…On October 12, 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-6446-1).
540-6472ADSGeneral Motors, LLC2023-09 08:42San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported3Intersection
On October 12, 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) manufactur…On October 12, 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-6447-1)
30270-6150ADSWaymo LLC2023-08 18:38Phoenix, AZ2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported8Intersection
On August [XXX], 2023 at 6:38 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped at a red light in the middle…On August [XXX], 2023 at 6:38 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped at a red light in the middle lane, facing northbound on [XXX] at [XXX]. When the light turned green, the pickup truck in the left turn lane to the left of the Waymo AV did not immediately proceed, and the Waymo AV attempted to merge into the left lane and make a left turn onto westbound [XXX] to pick up a rider that had hailed the Waymo AV while the vehicle was waiting at the red light. As the Waymo AV moved into the left lane, the adjacent pickup truck began to proceed forward and made contact with the drivers side of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. This report was originally submitted to NHTSA on August 19, 2023 via emailed .pdf because NHTSAs online portal was offline for maintenance. Waymo submitted this report again via the re-opened portal on August 20, 2023.
30270-6198ADSWaymo LLC2023-08 20:56Phoenix, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported3Intersection
On August [XXX], 2023 at 8:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound in the center…On August [XXX], 2023 at 8:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound in the center lane on [XXX]. As the AV came to a stop for a red light at the intersection with [XXX], the front of the passenger car that was traveling 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. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6335ADSWaymo LLC2023-08 19:12Phoenix, AZ2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On August [XXX], 2023 at 7:12 PM PT a Waymo Autonomous Vehicle ("Waymo") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stationary adjacent to the curb on …On August [XXX], 2023 at 7:12 PM PT a Waymo Autonomous Vehicle ("Waymo") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stationary adjacent to the curb on the south side of [XXX]. A passenger car which had been parked in front of the Waymo AV began reversing and the rear of the passenger car made contact with the front of the Waymo AV. The passenger car then left the scene. At the time of the impact, the Waymo's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6337ADSWaymo LLC2023-08 15:36Mesa, AZ2021 Jaguar I-PaceADSPickup TruckNo Injuries Reported0Street
On August [XXX], 2023 at 3:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stationary adjacent to the curb on t…On August [XXX], 2023 at 3:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Mesa, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stationary adjacent to the curb on the West side of [XXX]. A pickup truck approached the Waymo from behind and slowed to a stop immediately behind the Waymo. The pickup truck then moved slowly forward until the front of the pickup truck was touching the rear of the Waymo AV. The pickup truck then slowly pushed into the rear of the Waymo AV for a few seconds before reversing, maneuvering around the Waymo AV, and leaving the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6338ADSWaymo LLC2023-08 19:23Phoenix, AZ2021 Jaguar I-PaceADSSUVNo Injuries Reported1Intersection
On August [XXX], 2023 at 7:23 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] through the inter…On August [XXX], 2023 at 7:23 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] through the intersection with [XXX]. An SUV traveling West on [XXX] entered the intersection without stopping at the two-way stop sign on [XXX]. The Waymo AV slowed to a stop in the intersection and the front left corner of the SUV made contact with the front right corner of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6339ADSWaymo LLC2023-08 19:38Los Angeles, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported7Street
On August [XXX], 2023 at 7:38 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a recycling bin on [XXX] at [XXX]. The Waymo AV was pulling over to the right…On August [XXX], 2023 at 7:38 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a recycling bin on [XXX] at [XXX]. The Waymo AV was pulling over to the right side of the road, when the test driver transitioned to manual mode and made contact with a recycling bin on the right side of the street. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6340ADSWaymo LLC2023-08 21:01San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported13Intersection
On August [XXX], 2023 at 9:01 PM 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 southwestbound …On August [XXX], 2023 at 9:01 PM 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 southwestbound on [XXX] in the second lane from the left as it was approaching [XXX]. As the Waymo AV was proceeding straight through the intersection, the passenger car in the right adjacent lane made a left turn from a straight-only lane onto southeastbound [XXX]. The rear of the passenger car made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was 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-6341ADSWaymo LLC2023-08 18:11San Francisco, CA2021 Jaguar I-PaceADSOther, see NarrativeNo Injuries Reported0Street
On August [XXX], 2023, Waymo received notice of an allegation that a Waymo Autonomous Vehicle ("Waymo AV") contributed to a low-speed collision between a fire engine and an SUV on [XXX] at [XXX]. On August [XXX], 2023…On August [XXX], 2023, Waymo received notice of an allegation that a Waymo Autonomous Vehicle ("Waymo AV") contributed to a low-speed collision between a fire engine and an SUV on [XXX] at [XXX]. On August [XXX], 2023 at 6:11 PM PT, a Waymo AV operating in San Francisco, California was stopped at a red light in the dedicated left turn lane on the left side of northeast-bound [XXX] at the intersection with [XXX]. While the light was red, a fire engine approached the Waymo AV from behind and the Waymo AV moved forward as far as possible before entering the intersection at [XXX]. After the light turned green and as the Waymo AV was calculating a path into the intersection to clear the way, the fire engine maneuvered around the Waymo AV on the right side. During this maneuver, the right side of the fire engine appears to have made contact with the front left corner of an SUV that was stopped in the through lane to the right of the Waymo AV. The fire engine then proceeded through the intersection, and shortly afterwards, another fire engine and a fire department SUV passed on the left side the Waymo AV of the stopped Waymo AV. The Waymo AV then proceeded through the intersection. At the time of the collision, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The SUV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6342ADSWaymo LLC2023-08 13:05San Francisco, CA2021 Jaguar I-PaceADSSUVNo Injuries Reported17Street
On August [XXX], 2023 at 1:05 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX]…On August [XXX], 2023 at 1:05 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX]. As the SUV was passing the Waymo AV to the left, it initiated a right lane change. 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. Both vehicles sustained damage, and the SUV left the scene without exchanging information. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6343ADSWaymo LLC2023-08 16:45San Francisco, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported0Street
On August [XXX], 2023 at 4:45 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 entered the slip lane which…On August [XXX], 2023 at 4:45 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 entered the slip lane which connects westbound [XXX] to northbound [XXX] and came to a stop to yield to cross-traffic on [XXX]. As the Waymo AV was stopped, the front of the passenger car which was traveling behind the Waymo AV 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 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-6344ADSWaymo LLC2023-08 17:48San Francisco, CA2021 Jaguar I-PaceADSNon-Motorist: CyclistNo Injuries Reported0Street
On August [XXX], 2023 at 5:49 PM PT the mirror of a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was struck by a cyclist on [XXX]. Drive at [XXX]. The Waymo AV was stopped in traffic on eastbound…On August [XXX], 2023 at 5:49 PM PT the mirror of a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, CA was struck by a cyclist on [XXX]. Drive at [XXX]. The Waymo AV was stopped in traffic on eastbound [XXX] Drive at the intersection with [XXX], when a cyclist that had been traveling behind the Waymo AV passed the Waymo AV on the left. As the cyclist passed the Waymo AV, the cyclist made contact with the driver side mirror 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. 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-6346ADSWaymo LLC2023-08 21:55San Francisco, CA2021 Jaguar I-PaceADSHeavy TruckNo Injuries Reported0Street
On August [XXX], 2023 at 9:54 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling northbound on […On August [XXX], 2023 at 9:54 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] when it approached a heavy truck and trailer that was stopped in the adjacent lane on the left side of the street. As the Waymo began to slowly pass the truck, the truck initiated a reversing turn maneuver into a loading bay on the left side of [XXX]. The Waymo AV then came to a stop, and as the Waymo AV was initiating its own reversing maneuver to clear the path for the truck, the right side of the trailer made contact with the front driver's side corner of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-6347ADSWaymo LLC2023-08 16:38Santa Monica, CA2021 Jaguar I-PaceADSPassenger CarNo Injuries Reported1Traffic Circle
On August [XXX], 2023 at 4:39 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traversing a roundabout…On August [XXX], 2023 at 4:39 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traversing a roundabout at the intersection of [XXX] at [XXX] when it slowed to a stop for other vehicles approaching and in the roundabout. The front of the passenger car that was in the roundabout behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
30412-6020ADSCruise LLC2023-08 09:48San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported5StreetRedacted by NHTSA as confidential business information
30412-6051ADSCruise LLC2023-08 11:03San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6052ADSCruise LLC2023-08 11:41San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported0StreetRedacted by NHTSA as confidential business information
30412-6139ADSCruise LLC2023-08 07:51San Francisco, CA2023 Cruise AVADSPickup TruckNo Injuries Reported8StreetRedacted by NHTSA as confidential business information
30412-6158ADSCruise LLC2023-08 00:12San Francisco, CA2023 Cruise AVADSVanNo Injuries Reported0IntersectionRedacted by NHTSA as confidential business information
30412-6160 v2ADSCruise LLC2023-08 00:56San Francisco, CA2023 Cruise AVADSPassenger CarNo Injuries Reported13IntersectionRedacted by NHTSA as confidential business information
30412-6179ADSCruise LLC2023-08 00:36Austin, TX2024 Cruise OriginADSOther Fixed ObjectNo Injuries Reported6StreetRedacted by NHTSA as confidential business information
30412-6180 v2ADSCruise LLC2023-08 21:22San Francisco, CA2023 Cruise AVADSHeavy TruckNo Injuries Reported2Intersection
A Cruise autonomous vehicle ("AV"), operating in driverless autonomous mode, was traveling southbound on [XXX] in the middle lane between [XXX] and [XXX]. At the same time, a backhoe loader was traveling behind and to th…A Cruise autonomous vehicle ("AV"), operating in driverless autonomous mode, was traveling southbound on [XXX] in the middle lane between [XXX] and [XXX]. At the same time, a backhoe loader was traveling behind and to the left of the AV. As the AV approached the intersection with [XXX], the AV began changing lanes into the left lane in front of the backhoe loader. The AV then braked and was hit from behind by the backhoe loader. This caused damage to the AV's rear bumper fascia, rear hatch and glass, rear driver side quarter panel and rear driver side door. Police were called to the scene. The parties exchanged information. There were no reported injuries and the AV was towed from the scene.
30412-6181ADSCruise LLC2023-08 01:39San Francisco, CA2023 Cruise AVADSSUVNo Injuries Reported0IntersectionRedacted 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.