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
1674 reports, showing 1101 to 1200.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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-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-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-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-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) | |
| 540-6190 | ADS | General Motors, LLC | 2023-08 01:39 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Intersection | On August 29, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufacture…On August 29, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6181-1) | |
| 540-6199 | ADS | General Motors, LLC | 2023-08 00:39 | Austin, TX | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 5 | Street | On September 1, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactu…On September 1, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6191-1) | |
| 540-6293 v2 | ADS | General Motors, LLC | 2023-08 14:53 | San Francisco, CA | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | 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-6271-1) | |
| 540-6295 | ADS | General Motors, LLC | 2023-08 20:33 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 8 | 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-6268-1) | |
| 540-6302 | ADS | General Motors, LLC | 2023-08 13:47 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 5 | 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-6269-1) | |
| 540-6305 | ADS | General Motors, LLC | 2023-08 23:36 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 10 | Street | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6273-1) | |
| 540-6306 | ADS | General Motors, LLC | 2023-08 22:32 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6275-1) | |
| 540-6307 | ADS | General Motors, LLC | 2023-08 23:34 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 0 | 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-6272-1) | |
| 540-6308 | ADS | General Motors, LLC | 2023-08 10:37 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | 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-6276-1) | |
| 540-6310 | ADS | General Motors, LLC | 2023-08 00:21 | Austin, TX | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | 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-6274-1) | |
| 540-6311 | ADS | General Motors, LLC | 2023-08 11:59 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | 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-6279-1) | |
| 540-6313 | ADS | General Motors, LLC | 2023-08 16:45 | San Francisco, CA | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Street | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6278-1) | |
| 540-6315 | ADS | General Motors, LLC | 2023-08 22:55 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 6 | 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-6280-1) | |
| 540-6316 | ADS | General Motors, LLC | 2023-08 16:31 | San Francisco, CA | 2022 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 1 | Street | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6281-1) | |
| 540-6317 | ADS | General Motors, LLC | 2023-08 08:37 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufact…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6277-1) | |
| 540-6318 | ADS | General Motors, LLC | 2023-08 04:53 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 7 | 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-6282-1) | |
| 30270-5855 v2 | ADS | Waymo LLC | 2023-07 15:08 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 2 | Intersection | The content of this report is unchanged from the initial report submitted on July 10, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle (Waymo A…The content of this report is unchanged from the initial report submitted on July 10, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Los Angeles, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and preparing to make a right turn onto westbound [XXX]. As the Waymo AV was yielding to cross-traffic and preparing to make a right turn, a cyclist was traveling eastbound on [XXX] and heading the wrong way in the bike lane. The cyclist then turned left, northbound, onto [XXX], continuing to travel the wrong direction in the bike lane. As the Waymo AV slowly proceeded forward, the cyclist passed the Waymo AV and made contact with the rear passenger side sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained damage and the cyclist did not stop, leaving the scene without exchanging information. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a cyclist was involved. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5896 | ADS | Waymo LLC | 2023-07 18:13 | Chandler, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On July [XXX], 2023 at 6:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and ju…On July [XXX], 2023 at 6:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and just passed [XXX] when an oncoming passenger car crossed into the Waymo AVs lane, toward the Waymo AV. The Waymo AV then stopped as the passenger vehicle continued to approach. The passenger vehicle then made contact with the front of the Waymo AV, and then made contact with the side of the Waymo AV as it left the scene. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5998 | ADS | Waymo LLC | 2023-07 15:04 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 9 | Intersection | On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the cu…On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] at [XXX] when it began to pull away from the curb and into traffic. As the Waymo AV pulled away from the curb, a pickup truck that was traveling behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-6129 | ADS | Waymo LLC | 2023-07 13:13 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 4 | Street | On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XX…On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it began to brake as it approached a stopped van on the oncoming side of the narrow roadway. The Waymo AV test driver transitioned to manual mode and began proceeding straight when the passenger side front sensor housing of the Waymo AV made contact with the driver side mirror of a passenger car parked along the curb on southbound [XXX]. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both the Waymo AV and the passenger car sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-6130 | ADS | Waymo LLC | 2023-07 10:13 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 1 | Intersection | On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] i…On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] in autonomous mode, the Waymo AV slowed to a stop while entering a narrow roadway. The test driver transitioned the vehicle to manual mode and proceeded forward, making contact with a parked SUV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-6131 | ADS | Waymo LLC | 2023-07 9:02 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On July [XXX], 2023 at 9:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was parallel parked along the right-hand …On July [XXX], 2023 at 9:02 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was parallel parked along the right-hand curb on eastbound [XXX] when a passenger car reversed out of a driveway across the street from the Waymo AV and made contact with the driver side rear bumper of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-6132 | ADS | Waymo LLC | 2023-07 9:51 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On July [XXX], 2023 at 9:51 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The collision occurred while the Waymo AV w…On July [XXX], 2023 at 9:51 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The collision occurred while the Waymo AV was stopped in the leftmost lane of a two-lane, one-way road at the intersection of [XXX] at [XXX]. The Waymo AV was facing a green light, but stopped before entering the intersection because traffic was stacked on the other side of the intersection, leaving no space for the AV. When the light turned yellow, a passenger car that had been stopped behind the Waymo AV passed the Waymo AV on the left and proceeded into the intersection. While passing the Waymo AV, the passenger cars rear passenger side door made contact with the driver side rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The passenger car did not stop but appears to have sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-6133 | ADS | Waymo LLC | 2023-07 11:11 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Street | On July [XXX], 2023 at 11:11 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] east of [XXX]. The Waymo AV was facing east, waiting to merge t…On July [XXX], 2023 at 11:11 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving an SUV on [XXX] east of [XXX]. The Waymo AV was facing east, waiting to merge to the left back into eastbound traffic on [XXX], and stopped to the left of the right turn slip lane on [XXX], with stopped traffic to the right. After waiting to merge, the Waymo AV started reversing to reroute and while doing so, a sensor on the right front of the Waymo AV made contact with the left rear side of an SUV in the right turn lane. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The SUV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-6134 | ADS | Waymo LLC | 2023-07 14:57 | Santa Monica, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbo…On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbound [XXX] when a cyclist that had been traveling behind the Waymo AV passed the Waymo AV on the right. As the cyclist passed the Waymo AV, the cyclist made contact with the front passenger side sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AV sustained damage and the cyclist did not stop, leaving the scene without exchanging information. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30412-5848 | ADS | Cruise LLC | 2023-07 22:47 | San Francisco, CA | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 4 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5980 | ADS | Cruise LLC | 2023-07 19:50 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 20 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5981 | ADS | Cruise LLC | 2023-07 01:56 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5992 | ADS | Cruise LLC | 2023-07 05:35 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 22 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5993 | ADS | Cruise LLC | 2023-07 14:45 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 10 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6006 | ADS | Cruise LLC | 2023-07 23:51 | San Francisco, CA | 2022 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 2 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6037 | ADS | Cruise LLC | 2023-07 01:52 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6038 | ADS | Cruise LLC | 2023-07 20:56 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6039 v2 | ADS | Cruise LLC | 2023-07 22:34 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 1 | Street | A Cruise autonomous vehicle ("AV"), operating in driverless autonomous mode, was at a complete stop in response to a red light in the leftmost turn lane on westbound [XXX] at the intersection with [XXX]. When the light t…A Cruise autonomous vehicle ("AV"), operating in driverless autonomous mode, was at a complete stop in response to a red light in the leftmost turn lane on westbound [XXX] at the intersection with [XXX]. When the light turned green, both the AV and a GMC Yukon in the adjacent lane attempted a left turn onto southbound [XXX]. The AV veered slightly to the right into the [XXX] before attempting its left turn, making contact as the Yukon began its turn. This caused damage to the AV's front passenger side radar assembly. The driver of the GMC Yukon left the scene without exchanging information. There were no reported injuries. | |
| 30412-6040 | ADS | Cruise LLC | 2023-07 00:07 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 23 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6041 | ADS | Cruise LLC | 2023-07 10:47 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 2 | Street | Redacted by NHTSA as confidential business information | |
| 30412-6042 | ADS | Cruise LLC | 2023-07 16:16 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6043 | ADS | Cruise LLC | 2023-07 02:29 | Austin, TX | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-6044 | ADS | Cruise LLC | 2023-07 22:41 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | Redacted by NHTSA as confidential business information | |
| 30413-6032 | ADS | May Mobility | 2023-07 17:25 | Grand Rapids, MN | 2021 Toyota Sienna | ADS | Pickup Truck | No Injuries Reported | 0 | Street | The May vehicle came to a gentle stop at the railroad crossing (about -0.8 m/s2 deceleration) as designed, but the agent behind did not come to a stop and made contact with the AV. The May shuttle behaved as expected and…The May vehicle came to a gentle stop at the railroad crossing (about -0.8 m/s2 deceleration) as designed, but the agent behind did not come to a stop and made contact with the AV. The May shuttle behaved as expected and slowed down to a stop in a safe manner. The collision was unavoidable from the shuttle side. | |
| 30530-6125 | ADS | Aurora Operations, Inc. | 2023-07 09:35 | BUFFALO, TX | 2022 Peterbilt 579m | ADS | Other, see Narrative | No Injuries Reported | 64 | Highway / Freeway | At 09:35 AM CDT on July [XXX], 2023, an Aurora Class 8 truck was traveling southbound in autonomy mode on [XXX] near [XXX] when the front windshield was struck by an unknown object. The bottom of the windshield had a ho…At 09:35 AM CDT on July [XXX], 2023, an Aurora Class 8 truck was traveling southbound in autonomy mode on [XXX] near [XXX] when the front windshield was struck by an unknown object. The bottom of the windshield had a hole about 3 inches in diameter. The vehicle operator disengaged autonomy and pulled over. The vehicle was able to be driven from the scene, and there were no reported injuries. | |
| 30531-5871 v2 | ADS | Transdev Alternative Services | 2023-07 15:08 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 2 | Intersection | The content of this report in unchanged from the initial report submitted on July 10, 2023 (Report ID # 30531-5871-1) On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, Ca…The content of this report in unchanged from the initial report submitted on July 10, 2023 (Report ID # 30531-5871-1) On July [XXX], 2023 at 3:08 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] and preparing to make a right turn onto westbound [XXX]. As the Waymo AV was yielding to cross-traffic and preparing to make a right turn, a cyclist was traveling eastbound on [XXX] and heading the wrong way in the bike lane. The Cyclist then turned left, northbound, onto [XXX], continuing to travel the wrong direction in the bike lane. As the Waymo AV slowly proceeded forward, the cyclist passed the Waymo AV and made contact with the rear passenger side sensor of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage and the cyclist did not stop. Transdev Alternative Services is reporting a duplicate report from report number: 30270-5855-1. | |
| 30531-5999 | ADS | Transdev Alternative Services | 2023-07 15:04 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 9 | Intersection | On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the c…On July [XXX], 2023 at 3:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] at [XXX] when it began to pull away from the curb and into traffic. As the Waymo AV pulled away from the curb, a pickup truck that was traveling behind the Waymo AV then made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. | |
| 30531-6136 | ADS | Transdev Alternative Services | 2023-07 14:57 | Santa Monica, CA | 2021 Jaguar I-Pace | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwest…On July [XXX], 2023 at 2:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a cyclist on [XXX] near [XXX]. The Waymo AV was stopped in traffic on southwestbound [XXX] when a cyclist that had been traveling behind the Waymo AV passed the Waymo AV on the right. As the cyclist passed the Waymo AV, the cyclist made contact with the front passenger side sensor of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage and the cyclist did not stop, leaving the scene without exchanging information. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of report id: 30270-6134-1. | |
| 30531-6137 | ADS | Transdev Alternative Services | 2023-07 10:13 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 1 | Intersection | On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX…On July [XXX], 2023 at 10:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. While completing a right turn from [XXX] onto [XXX] in autonomous mode, the Waymo AV slowed to a stop while entering a narrow roadway. The test driver transitioned the vehicle to manual mode and proceeded forward, making contact with a parked SUV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of 30270-6130-1. | |
| 30531-6138 | ADS | Transdev Alternative Services | 2023-07 13:13 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 4 | Street | On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [X…On July [XXX], 2023 at 1:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in autonomous mode when it began to brake as it approached a stopped van on the oncoming side of the narrow roadway. The Waymo AV test driver transitioned to manual mode and began proceeding straight when the passenger side front sensor housing of the Waymo AV made contact with the driver side mirror of a passenger car parked along the curb on southbound [XXX]. At the time of the impact, the Waymo's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both the Waymo AV and the passenger car sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of report 30270-6129-1. | |
| 540-5875 | ADS | General Motors, LLC | 2023-07 22:47 | San Francisco, CA | 2023 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 4 | Street | On July 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the Order). General Motors LLC (GM) manufactured t…On July 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the Order). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5848-1) | |
| 540-5988 | ADS | General Motors, LLC | 2023-07 19:50 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 20 | Intersection | On July 24, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 24, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5980-1) | |
| 540-5990 | ADS | General Motors, LLC | 2023-07 01:56 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On July 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured…On July 26, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5981-1) | |
| 540-6002 | ADS | General Motors, LLC | 2023-07 05:35 | Austin, TX | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 22 | Intersection | On July 27, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured …On July 27, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5992-1) | |
| 540-6003 | ADS | General Motors, LLC | 2023-07 14:45 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 10 | Intersection | On July 27, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured …On July 27, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5993-1). | |
| 540-6011 | ADS | General Motors, LLC | 2023-07 23:51 | San Francisco, CA | 2022 Cruise AV | ADS | Pickup Truck | No Injuries Reported | 2 | Intersection | On August 2, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured…On August 2, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6006-1) | |
| 540-6058 | ADS | General Motors, LLC | 2023-07 01:52 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 6 | 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) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6037-1). | |
| 540-6069 | ADS | General Motors, LLC | 2023-07 20:56 | 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) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6038-1). | |
| 540-6070 v2 | ADS | General Motors, LLC | 2023-07 22:34 | San Francisco, CA | 2023 Cruise AV | ADS | SUV | No Injuries Reported | 1 | Street | On September 26, 2024, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) …On September 26, 2024, GM Cruise Holdings LLC ("Cruise") filed an updated Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6039-2) | |
| 540-6072 | ADS | General Motors, LLC | 2023-07 00:07 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 23 | 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) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6040-1). | |
| 540-6073 | ADS | General Motors, LLC | 2023-07 10:47 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 2 | 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) manufacture…On August 11, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6041-1). | |
| 540-6074 | ADS | General Motors, LLC | 2023-07 16:16 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | 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-6042-1). | |
| 540-6076 | ADS | General Motors, LLC | 2023-07 02:29 | Austin, TX | 2023 Cruise AV | ADS | Pickup 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-6043). | |
| 540-6079 | ADS | General Motors, LLC | 2023-07 22:41 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 1 | 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-6044-1). | |
| 30270-5813 | ADS | Waymo LLC | 2023-06 20:58 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 35 | Street | On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and prepar…On June [XXX], 2023 at 8:58 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona impacted road debris on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the middle lane and preparing to make a right lane change. As it initiated the lane change, the rear passenger side tire struck small debris in the road. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the drivers seating position). The Waymo AVs tire immediately deflated. Waymo is reporting this event under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5957 | ADS | Waymo LLC | 2023-06 12:35 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Van | No Injuries Reported | 0 | Parking Lot | On June [XXX], 2023 at 12:53 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot at [XXX]. The Waymo AV came to a stop while yielding to …On June [XXX], 2023 at 12:53 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a van in a parking lot at [XXX]. The Waymo AV came to a stop while yielding to a pickup truck which was reversing into a perpendicular parking space in front of the Waymo AV. While the Waymo AV was stopped, a van which was in a parking space immediately to the right of the Waymo AV began reversing out of the parking space. The rear of the van made contact with the right side of the Waymo AV. The Waymo AV sustained damage. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5958 | ADS | Waymo LLC | 2023-06 15:44 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Street | On June [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parallel parked along the …On June [XXX], 2023 at 3:44 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parallel parked along the curb on eastbound [XXX] when a passenger car pulled up behind the Waymo AV. The front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5959 | ADS | Waymo LLC | 2023-06 17:06 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | On June [XXX], 2023 at 5:06 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped for a red light …On June [XXX], 2023 at 5:06 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger vehicle on [XXX] at [XXX]. The Waymo AV was stopped for a red light on [XXX] at [XXX] with its turn signal activated to indicate intent to turn left onto [XXX]. The traffic light turned green, and the Waymo AV slowly moved forward, yielding to oncoming traffic, when the vehicle that had been previously stopped behind the Waymo AV proceeded forward, making contact with the rear bumper of the Waymo AV. The other party immediately left the scene of the event. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5960 | ADS | Waymo LLC | 2023-06 21:19 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Street | On June [XXX], 2023 at 9:19 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was parallel parked along the …On June [XXX], 2023 at 9:19 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was parallel parked along the curb on southbound [XXX] when a pickup truck that was initially parked directly behind the Waymo AV began to maneuver out of its parking spot. As the pickup truck pulled out of the parking spot, it initiated a multi-turn maneuver and reversed into the parked Waymo AV. The rear passenger's side corner of the pickup truck made contact with the driver side rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5961 | ADS | Waymo LLC | 2023-06 07:50 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On June [XXX], 2023 at 7:50 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and sto…On June [XXX], 2023 at 7:50 AM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, CA was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] and stopped at a stop sign at the intersection of [XXX]. While yielding to pedestrians crossing the street, a pickup truck traveling directly behind the Waymo AV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-5962 | ADS | Waymo LLC | 2023-06 21:39 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 56 | Highway / Freeway | On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane when …On June [XXX], 2023 at 9:39 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, Arizona impacted road debris on [XXX] just past [XXX]. The Waymo AV was traveling eastbound on [XXX] in the far right lane when road debris appeared from under the passenger vehicle in front of the Waymo AV. The Waymo AV test driver transitioned to manual mode just before the Waymo AV made contact with the road debris. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30412-5661 | ADS | Cruise LLC | 2023-06 04:31 | Chandler, AZ | 2020 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 14 | Intersection | Redacted by NHTSA as confidential business information | |
| 30412-5782 | ADS | Cruise LLC | 2023-06 09:36 | San Francisco, CA | 2022 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 7 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5799 | ADS | Cruise LLC | 2023-06 22:37 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 7 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5828 | ADS | Cruise LLC | 2023-06 22:37 | San Francisco, CA | 2022 Cruise AV | ADS | SUV | No Injuries Reported | 0 | Street | Redacted 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.