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
443 reports, showing 101 to 200.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30412-6363 | ADS | Cruise LLC | 2023-09 03:49 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 3 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6371 | ADS | Cruise LLC | 2023-09 20:14 | Houston, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 16 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6384 | ADS | Cruise LLC | 2023-09 09:20 | Houston, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 8 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6436 | ADS | Cruise LLC | 2023-09 22:16 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6437 | ADS | Cruise LLC | 2023-09 23:02 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6438 | ADS | Cruise LLC | 2023-09 17:32 | San Francisco, CA | 2022 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6439 v2 | ADS | Cruise LLC | 2023-09 00:05 | Tempe, AZ | 2022 Cruise AV | ADS | Animal | No Injuries Reported | 15 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6440 | ADS | Cruise LLC | 2023-09 04:59 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6441 | ADS | Cruise LLC | 2023-09 10:54 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6442 | ADS | Cruise LLC | 2023-09 23:56 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 10 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6444 | ADS | Cruise LLC | 2023-09 23:44 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 25 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6445 v2 | ADS | Cruise LLC | 2023-09 22:36 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 24 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6446 | ADS | Cruise LLC | 2023-09 09:37 | San Francisco, CA | 2020 Cruise AV | ADS | Van | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6447 | ADS | Cruise LLC | 2023-09 08:42 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | Redacted by NHTSA as confidential business information | |
| 30531-6354 | ADS | Transdev Alternative Services | 2023-09 20:34 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | 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-6533 | ADS | Transdev Alternative Services | 2023-09 21:00 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | 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-6382 | ADS | Apple Inc. | 2023-09 11:33 | Emeryville, CA | 2017 Lexus RX 450h | ADS | Pickup Truck | No Injuries Reported | 0 | Highway / 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-6373 | ADS | Zoox, Inc. | 2023-09 15:20 | San Francisco, CA | 2017 Toyota Highlander | ADS | Van | No Injuries Reported | 0 | Street | 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-6431 | ADS | Pony.ai | 2023-09 17:02 | Milpitas, CA | 2019 Lincoln MKZ | ADS | Other, see Narrative | No Injuries Reported | 58 | Highway / 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-6492 | ADS | WeRide Corp | 2023-09 13:54 | San Francisco, CA | 2023 Nissan Leaf | ADS | SUV | No Injuries Reported | 0 | Street | 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-6725 | ADS | Apollo Autonomous Driving USA | 2023-09 12:25 | San Francisco, CA | 2017 Lincoln MKZ Hybrid | Unknown, see Narrative | SUV | No Injuries Reported | 5 | Street | 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-6244 | ADS | General Motors, LLC | 2023-09 21:42 | Houston, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Street | 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-6290 | ADS | General Motors, LLC | 2023-09 02:35 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 2 | Intersection | 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-6369 | ADS | General Motors, LLC | 2023-09 03:49 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 3 | Intersection | 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-6372 | ADS | General Motors, LLC | 2023-09 20:14 | Houston, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 16 | Intersection | 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-6393 | ADS | General Motors, LLC | 2023-09 09:20 | Houston, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 8 | Intersection | 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-6451 | ADS | General Motors, LLC | 2023-09 22:16 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | 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-6452 | ADS | General Motors, LLC | 2023-09 23:02 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | 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-6453 | ADS | General Motors, LLC | 2023-09 17:32 | San Francisco, CA | 2022 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | 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 v2 | ADS | General Motors, LLC | 2023-09 00:05 | Tempe, AZ | 2022 Cruise AV | ADS | Animal | No Injuries Reported | 15 | Street | 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-6455 | ADS | General Motors, LLC | 2023-09 04:59 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 1 | Street | 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-6461 | ADS | General Motors, LLC | 2023-09 10:54 | Austin, TX | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | 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-6462 | ADS | General Motors, LLC | 2023-09 23:56 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 10 | Intersection | 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-6467 | ADS | General Motors, LLC | 2023-09 23:44 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 25 | Intersection | 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 v2 | ADS | General Motors, LLC | 2023-09 22:36 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 24 | Intersection | 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-6470 | ADS | General Motors, LLC | 2023-09 09:37 | San Francisco, CA | 2020 Cruise 8AV | ADS | Van | No Injuries Reported | 10 | Street | 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-6472 | ADS | General Motors, LLC | 2023-09 08:42 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | 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-6149 v2 | ADS | Waymo LLC | 2023-08 21:37 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Unknown | 0 | Intersection | The content of this report is unchanged from the initial report submitted on August 18, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2023 at 9:37 PM PT a Waymo Autonomous Vehicle (Way…The content of this report is unchanged from the initial report submitted on August 18, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On August [XXX], 2023 at 9:37 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was stopped in traffic at a red light for a pedestrian crosswalk, facing westbound on [XXX]. A passenger vehicle behind the Waymo AV approached 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. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-6150 | ADS | Waymo LLC | 2023-08 18:38 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 8 | Intersection | 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-6198 | ADS | Waymo LLC | 2023-08 20:56 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | 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-6335 | ADS | Waymo LLC | 2023-08 19:12 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | 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-6336 | ADS | Waymo LLC | 2023-08 22:10 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | Minor | 0 | Street | On August [XXX], 2023 at 10:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light on eastb…On August [XXX], 2023 at 10:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped at a red light on eastbound [XXX] at [XXX]. Shortly after the traffic light turned green and the Waymo AV began to proceed forward, the Waymo AV slowed to a stop. The SUV that was traveling closely 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, and the trailing SUV left the scene without exchanging information. A passenger in the Waymo AV reported injuries. 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-6337 | ADS | Waymo LLC | 2023-08 15:36 | Mesa, AZ | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Street | 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-6338 | ADS | Waymo LLC | 2023-08 19:23 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 1 | Intersection | 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-6339 | ADS | Waymo LLC | 2023-08 19:38 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 7 | Street | 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-6340 | ADS | Waymo LLC | 2023-08 21:01 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 13 | Intersection | 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-6341 | ADS | Waymo LLC | 2023-08 18:11 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 0 | Street | 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-6342 | ADS | Waymo LLC | 2023-08 13:05 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 17 | Street | 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-6343 | ADS | Waymo LLC | 2023-08 16:45 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | 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-6344 | ADS | Waymo LLC | 2023-08 17:48 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | 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-6346 | ADS | Waymo LLC | 2023-08 21:55 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Street | 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-6347 | ADS | Waymo LLC | 2023-08 16:38 | Santa Monica, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Traffic 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-6020 | ADS | Cruise LLC | 2023-08 09:48 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 5 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6051 | ADS | Cruise LLC | 2023-08 11:03 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6052 | ADS | Cruise LLC | 2023-08 11:41 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6139 | ADS | Cruise LLC | 2023-08 07:51 | San Francisco, CA | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 8 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6144 v3 | ADS | Cruise LLC | 2023-08 22:22 | San Francisco, CA | 2023 Cruise AV | ADS | First Responder Vehicle | Serious | 13 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6145 v2 | ADS | Cruise LLC | 2023-08 08:45 | San Francisco, CA | 2023 Cruise AV | ADS | Non-Motorist: Cyclist | Minor | 1 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6158 | ADS | Cruise LLC | 2023-08 00:12 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6159 v2 | ADS | Cruise LLC | 2023-08 00:19 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | Moderate | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6160 v2 | ADS | Cruise LLC | 2023-08 00:56 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 13 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6167 v2 | ADS | Cruise LLC | 2023-08 09:05 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | Minor | 5 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6175 v2 | ADS | Cruise LLC | 2023-08 01:42 | San Francisco, CA | 2022 Cruise AV | ADS | Non-Motorist: Pedestrian | Moderate | 1 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6179 | ADS | Cruise LLC | 2023-08 00:36 | Austin, TX | 2024 Cruise Origin | ADS | Other Fixed Object | No Injuries Reported | 6 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6180 v2 | ADS | Cruise LLC | 2023-08 21:22 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 2 | Intersection | 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-6181 | ADS | Cruise LLC | 2023-08 01:39 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6191 | ADS | Cruise LLC | 2023-08 00:39 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 5 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6268 | ADS | Cruise LLC | 2023-08 20:33 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 8 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6269 | ADS | Cruise LLC | 2023-08 13:47 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 5 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6270 | ADS | Cruise LLC | 2023-08 16:06 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | Minor | 1 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6271 | ADS | Cruise LLC | 2023-08 14:53 | San Francisco, CA | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6272 | ADS | Cruise LLC | 2023-08 23:34 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6273 | ADS | Cruise LLC | 2023-08 23:36 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6274 | ADS | Cruise LLC | 2023-08 00:21 | Austin, TX | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6275 | ADS | Cruise LLC | 2023-08 22:32 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6276 | ADS | Cruise LLC | 2023-08 10:37 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6277 | ADS | Cruise LLC | 2023-08 08:37 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6278 | ADS | Cruise LLC | 2023-08 16:45 | San Francisco, CA | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6279 | ADS | Cruise LLC | 2023-08 11:59 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6280 | ADS | Cruise LLC | 2023-08 22:55 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 6 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6281 | ADS | Cruise LLC | 2023-08 16:31 | San Francisco, CA | 2022 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 1 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6282 | ADS | Cruise LLC | 2023-08 04:53 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 7 | Intersection | Redacted by NHTSA as confidential business information | |
| 30413-6257 | ADS | May Mobility | 2023-08 10:10 | Arlington, TX | 2021 Toyota Sienna | Unknown, see Narrative | Passenger Car | No Injuries Reported | 18 | Street | The vehicle operator took the vehicle out of autonomy while driving NB on [XXX]. In manual the operator clipped the May vehicle's right sensor with the trunk of a diagonally parked car. The operator did not report the in…The vehicle operator took the vehicle out of autonomy while driving NB on [XXX]. In manual the operator clipped the May vehicle's right sensor with the trunk of a diagonally parked car. The operator did not report the incident, however based on video footage they were aware of physical damage to the May vehicle. Local staff noticed a vehicle health error regarding that sensor and called the operator back to base, where they saw the damage. The operator was sent home immediately and terminated upon video review due to not following proper procedure. | |
| 30450-6116 | ADS | Ghost Autonomy Inc. | 2023-08 14:20 | Sunol, CA | 2017 Toyota Camry | Unknown, see Narrative | Other, see Narrative | No Injuries Reported | 55 | Highway / Freeway | A Ghost autonomous vehicle was hit by crash debris while traveling on [XXX]. The Ghost vehicle neither hit nor was hit by another vehicle. The Ghost car was traveling in AV mode with two safety drivers. Traffic slowed…A Ghost autonomous vehicle was hit by crash debris while traveling on [XXX]. The Ghost vehicle neither hit nor was hit by another vehicle. The Ghost car was traveling in AV mode with two safety drivers. Traffic slowed quickly, apparently due to a crash ahead of the Ghost car. Consistent with their training, the Ghost driver took control of the car by manually braking and disengaging the autonomous system. The car was traveling 55.3 mph when the driver began to brake. The Ghost car stopped without impacting the preceding car. A Mercedes car immediately following the Ghost car also came to a stop without impacting the Ghost car. Ghost's understanding based on communications at the scene is that a Grand Cherokee traveling behind the Mercedes tried to swerve to avoid impacting the Mercedes but clipped the Mercedes and rolled over. To Ghost's knowledge, nobody in the Grand Cherokee was injured. The Ghost drivers heard a noise and then found that the rear bumper of the Ghost car had been damaged, which Ghost believes resulted from crash debris. The Ghost drivers drove the Ghost car back to the garage in conventional mode. | |
| 30490-6165 v2 | ADS | Beep, Inc. | 2023-08 12:54 | Orlando, FL | Navya ARMA Autonom DL | ADS | Bus | No Injuries Reported | Street | Redacted by NHTSA as confidential business information | ||
| 30490-6359 | ADS | Beep, Inc. | 2023-08 17:54 | San Francisco, CA | Navya Arma Autonom DL | ADS | Passenger Car | No Injuries Reported | Intersection | VIN # VG9A2CB2CIV[XXX] At approximately 5:54 p.m. on Wednesday, August [XXX], 2023, P84, travelling eastbound on [XXX], approached the three-way stop at [XXX] and [XXX]. P84 arrived at the intersection at the same time …VIN # VG9A2CB2CIV[XXX] At approximately 5:54 p.m. on Wednesday, August [XXX], 2023, P84, travelling eastbound on [XXX], approached the three-way stop at [XXX] and [XXX]. P84 arrived at the intersection at the same time as two other vehicles: a grey van heading northbound on [XXX] and a red sedan heading westbound on [XXX]. The safety driver yielded to the northbound vehicle, which proceeded to make a right-hand turn eastbound onto [XXX]. After allowing the intersection to clear, the safety driver onboard P84 confirmed that it was safe for the shuttle to proceed through the intersection. As the shuttle entered the intersection, a second vehicle travelling northbound on [XXX], a white sedan, entered the intersection intending a left-hand turn onto westbound [XXX]. Both vehicles entered the intersection simultaneously, subsequently colliding at a low rate of speed in the middle of the intersection. At approximately 5:57 p.m., the Beep Command Center (BCC) was informed by the safety driver that P84 was involved in a minor collision with another vehicle at the intersection of [XXX] and [XXX]. The incident response protocol was initiated, and a supervisor dispatched to the scene. Local law enforcement (San Francisco Police Department) was contacted to report the collision but declined to respond given the minor nature of the collision, directing both parties to exchange information. After the Beep supervisor arrived on scene at approximately 6:49 p.m., the safety driver and supervisor removed the shuttle from the roadway and exchanged insurance information with the driver of the other vehicle. Damage to both vehicles was noted to be very minor. The shuttle sustained light scuffs, chips, and small paint transfer. The other vehicle sustained a small dent on the fender. Neither vehicle required towing, and both were safely driven from the scene. Beeps safety driver was subsequently subjected to a standard post-collision drug & alcohol screening which has since cleared. Contributing Factors Based on an analysis of the available evidence, Beep has determined the following factors may have contributed to the higher likelihood of a collision occurring in this instance: 1.The white sedan failed to yield to P84 in accordance with California state law governing intersection priority. 2.The slight bend in P84s path to accommodate the lane shift through the intersection may have reduced the available stopping distance as the white sedan was not perceived as an obstacle in P84s path until it proceeded further into the intersection. Incident Findings Beep developed the following findings regarding this incident: 1.P84 behaved as expected, detecting and maintaining awareness of the white sedan in the moments preceding the collision, commanding hard braking maneuver, and achieving a 3m/s2 deceleration rate once the white sedan encroached on P84s path. 2.The safety driver observed California state law and had the right of way when releasing P84 into the intersection. 3.The safety driver could have avoided the collision by using the emergency stop. The safety driver indicated that they were aware of the other vehicle through the duration of the incident and were aware of the proper procedure in this scenario but panicked in the moment. Mitigation: Implement a priority zone to account for the slight bend in the shuttles path and for future vehicles that may fail to yield. | ||
| 30490-6360 | ADS | Beep, Inc. | 2023-08 13:54 | Orlando, FL | Navya Arma Autonom DL | ADS | Bus | No Injuries Reported | 9 | Street | At Approximately 12:39 PM, the Beep Command Center (BCC) informed the LYNX dispatch center that another autonomous shuttle operating on the same route (VIN: VG9A2CB2CJV[XXX]) was being taken out of service due to insuffi…At Approximately 12:39 PM, the Beep Command Center (BCC) informed the LYNX dispatch center that another autonomous shuttle operating on the same route (VIN: VG9A2CB2CJV[XXX]) was being taken out of service due to insufficient battery charge to continue operation. The BCC later informed LYNX dispatch at 12:49PM that the second shuttle operating on route, P131, would also be returning to storage after the operator completed its current loop. At Approximately 12:52 PM, P131 approached the [XXX] stop within the designated Bus Rapid Transit (BRT) operating lane. The shuttle remained stopped for approximately two (2) and a half minutes while three (3) passengers alighted, and two (2) additional passengers boarded the shuttle. During that period, approximately two (2) minutes after stopping to service passengers, a LYNX bus pulled behind P131. Approximately thirty (30) seconds later, the LYNX bus exited the BRT lane and proceeded into the public travel lane alongside the BRT lane. As the LYNX bus entered the public travel lane, the safety driver onboard P131 engaged the autonomous drive system, and the shuttle proceeded in the BRT lane. After both vehicles had begun moving, P131 in the BRT lane and the LYNX bus in the public travel lane, the LYNX bus reentered the BRT lane encroaching on the shuttles path. The bus failed to provide adequate clearance and contacted the left front side of P131. Both vehicles stopped in the BRT lane after the collision. Within five (5) minutes of the collision, all passengers had safely alighted from the shuttle with no reported injuries and left the scene without giving statements. At approximately 2:20PM, the City of Orlando Police Department (OPD) arrived on scene to investigate the incident. Beep and LYNX supervisors were on scene to support the investigation. OPD collected statements from both the Beep safety driver and LYNX bus driver. The LYNX supervisor provided OPD access to the LYNX bus camera footage on scene, at which point the investigating officer made a verbal indication that the LYNX bus driver appeared to be at fault for the collision. Beeps safety driver was subsequently subjected to a standard post-collision drug and alcohol screening. 1.The safety driver did not exhibit complete situational awareness and per their after-incident interview, failed to notice the bus prior to departing the station. Had the attendant continued to look and check behind/alongside P131 prior to departing the station, the collision may have been avoided. 2.The safety driver attempted to stop the shuttle by disengaging the ADS using the HMI rather than using the emergency stop button. Use of the emergency stop would have increased the deceleration rate to 5 m/s2, decreasing the stopping distance of the shuttle. However, it is not clear whether use of the emergency stop would have fully avoided the collision given the point at which the LYNX LYMMO bus entered the BRT lane. 3.Deficiencies in the standard operating procedures (SOP) between LYNX and Beep allowed for a bus to be deployed onto the service at the same time as P131. Beep communicated to LYNX that both shuttles were exiting the service area. However, LYNX did not wait for final confirmation that both vehicles had left the route prior to dispatching the LYMMO bus involved in the incident, nor did LYNX notify Beep that a bus had been dispatched. Additional information available upon request. | |
| 30792-6114 | ADS | WeRide Corp | 2023-08 13:45 | San Francisco, CA | 2023 Nissan LEAF | Unknown, see Narrative | Pickup Truck | No Injuries Reported | 0 | Street | At 1:45pm, a WeRide vehicle (Car 1) was parked at a [XXX] parking meter - between [XXX] and [XXX] when another vehicle (Car 2) began reversing in front of the vehicle in question. The reversing vehicle (Car 2) ultimatel…At 1:45pm, a WeRide vehicle (Car 1) was parked at a [XXX] parking meter - between [XXX] and [XXX] when another vehicle (Car 2) began reversing in front of the vehicle in question. The reversing vehicle (Car 2) ultimately collided with the front left corner of the WeRide vehicle (Car 1), causing minor damage to the front bumper. The reversing vehicle (Car 2) did not have any damage. Both drivers were able to confer with one another seconds after the incident took place. The reversing vehicle's driver did not possess any form of insurance or registration. WeRide vehicle (Car 1) ADS was not engaged. | |
| 540-6036 | ADS | General Motors, LLC | 2023-08 09:48 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 5 | Street | On August 7, 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 7, 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-6020-1). | |
| 540-6056 | ADS | General Motors, LLC | 2023-08 11:41 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | 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…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-6052-1) | |
| 540-6057 | ADS | General Motors, LLC | 2023-08 11:03 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | 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-6051-1). | |
| 540-6148 v3 | ADS | General Motors, LLC | 2023-08 22:22 | San Francisco, CA | 2023 Cruise AV | ADS | First Responder Vehicle | Serious | 13 | Intersection | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an update 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 September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an update 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-6144-3). | |
| 540-6151 v2 | ADS | General Motors, LLC | 2023-08 08:45 | San Frabcisco, CA | 2023 Cruise AV | ADS | Non-Motorist: Cyclist | Minor | 1 | Intersection | On August 25, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update 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 25, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update 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-6145-2) | |
| 540-6152 | ADS | General Motors, LLC | 2023-08 07:51 | San Francisco, CA | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 8 | Street | On August 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) manufacture…On August 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-6139-1) | |
| 540-6161 | ADS | General Motors, LLC | 2023-08 00:12 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 0 | Intersection | On August 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) manufacture…On August 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-6158-1) | |
| 540-6162 v2 | ADS | General Motors, LLC | 2023-08 00:19 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | Moderate | 0 | Intersection | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an update 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 September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an update 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-6159-2) | |
| 540-6163 v2 | ADS | General Motors, LLC | 2023-08 00:56 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 13 | Intersection | On September 14, 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) …On September 14, 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-6160-2) | |
| 540-6178 v2 | ADS | General Motors, LLC | 2023-08 01:42 | San Francisco, CA | 2022 Cruise AV | ADS | Non-Motorist: Pedestrian | Moderate | 1 | Intersection | On September 5, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (…On September 5, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 Day Update 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-6175-2). | |
| 540-6188 | ADS | General Motors, LLC | 2023-08 00:36 | Austin, TX | 2024 Cruise Origin | ADS | Other Fixed Object | No Injuries Reported | 6 | Street | On August 29, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 29, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6179-1) | |
| 540-6189 v2 | ADS | General Motors, LLC | 2023-08 21:22 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 2 | Intersection | 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-6180-2) |
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.