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
8612 reports, showing 7201 to 7300.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30412-5140 v2 | ADS | Cruise LLC | 2023-03 14:46 | San Francisco, CA | 2023 Cruise AV | ADS | Bus | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information |
| 30412-5229 | ADS | Cruise LLC | 2023-03 04:23 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5240 | ADS | Cruise LLC | 2023-03 23:51 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-5241 | ADS | Cruise LLC | 2023-03 21:49 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information |
| 30412-5242 | ADS | Cruise LLC | 2023-03 03:20 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 12 | Street | Redacted by NHTSA as confidential business information |
| 30412-5243 | ADS | Cruise LLC | 2023-03 23:30 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30530-5289 | ADS | Aurora Operations, Inc. | 2023-03 08:01 | Weatherford, TX | 2022 Peterbilt 579m | ADS | Passenger Car | No Injuries Reported | 65 | Highway / Freeway | At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicl…At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicle encroaching on the lane. This vehicle continued to veer toward Aurora's truck at over 65 miles per hour, causing a collision. Aurora disengaged autonomy before impact and pulled to the shoulder along with the involved vehicle. Both vehicles were able to be driven from the scene, and there were no reported injuries. |
| 30531-5328 v2 | ADS | Transdev Alternative Services | 2023-03 21:28 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | On March [XXX], 2023 at 9:28 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the dedicated…On March [XXX], 2023 at 9:28 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane facing west on [XXX], awaiting a green signal to turn onto [XXX]. The signal for traffic proceeding west on [XXX] turned green, and traffic in adjacent lanes began moving. The left turn arrow signal for the dedicated turn lane occupied by the Waymo AV remained red. The passenger car that had been stopped directly behind the Waymo AV began moving forward. The front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was prest (in the driver's seat). Transdev Alternative Services is reporting this crash under Request no. 2 of Standing Gneral Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of 30270-5320-1. |
| 30531-5329 v2 | ADS | Transdev Alternative Services | 2023-03 2:19 | San Bruno, CA | 2021 Jaguar I-Pace | ADS | Other, see Narrative | No Injuries Reported | 64 | Highway / Freeway | On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was travel…On March [XXX], 2023 at 2:19 AM PST a Waymo Autonomous Vehicle ("Waymo AV" ) operating in San Bruno, CA was in a collision involving road debris on [XXX] at the interchange ramp for [XXX] ([XXX]). The Waymo AV was traveling south on [XXX] in the rightmost exit lane for [XXX] towards [XXX] when it made contact with road debris (tire scrap). At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request No. 2 of Standing General 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of 30270-5322-1. |
| 30531-5330 v2 | ADS | Transdev Alternative Services | 2023-03 17:10 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 8 | Intersection | On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling…On March [XXX], 2023 at 5:10 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] between [XXX] and [XXX]. The Waymo AV was traveling north on [XXX] in autonomous mode, merging into the rightmost lane. As the Waymo AV merged, the test driver transitioned from autonomous mode to manual mode and began accelerating. The front of the Waymo AV made contact with the rear of a passenger car that was stopped in the rightmost lane. At the time of the impact, the Waymo'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 30270-5323-1. |
| 30531-5331 | ADS | Transdev Alternative Services | 2023-03 19:00 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | Minor | 1 | Street | On March [XXX], 2023 at 7:00 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX]…On March [XXX], 2023 at 7:00 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] behind traffic that was backed up from the intersection with [XXX]. As the Waymo AV was accelerating from a stop, a passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and. a test driver was present (in the driver's seating position). The Waymo AV test driver reported having a minor injury and the passenger vehicle left the scene. 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-5324-1. |
| 30531-5335 | ADS | Transdev Alternative Services | 2023-03 10:43 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 0 | Intersection | On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a th…On March [XXX], 2023 at 10:43 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the center lane of a three-lane road behind a passenger vehicle for a red light facing southwest on [XXX] at [XXX] in autonomous mode. The light turned green while cross-traffic remained backed up in the intersection. The Waymo AV nudged forward and slowed to a stop, yielding for the blocking cross traffic. An SUV that had been stopped behind the Waymo AV proceeded forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). The Waymo AV sustained damage. Transdev Alternative Services is reporting this crash under Request no. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of 30270-5325-1. |
| 30531-5336 | ADS | Transdev Alternative Services | 2023-03 13:35 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 2 | Intersection | On March [XXX], 2023 at 1:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. While attempting a right turn in autonomous mode fr…On March [XXX], 2023 at 1:35 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] and [XXX]. While attempting a right turn in autonomous mode from westbound [XXX] onto northbound [XXX], the Waymo AV was yielding to traffic approaching from the left. As the Waymo AV attempted to proceed, the test driver transitioned to manual mode and brought the Waymo AV to a stop. A passenger car behind the Waymo AV proceeded forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV and the passenger vehicle sustained damage. Transdev Alternative Services is reporting this crash under Request no. 2 of Standing General Order 2021-01. Transdev may supplement or correct its reporting with additional information as it may become available. This is a duplicate of 30270-5326-1. |
| 30610-5224 | ADS | Zoox, Inc. | 2023-03 22:45 | Paradise, NV | 2016 Toyota Highlander | ADS | Other Fixed Object | No Injuries Reported | 4 | Street | A Zoox vehicle in autonomous mode was traveling northbound on an access road towards [XXX] in Las Vegas, Nevada, when the driver disengaged for a vehicle in the oncoming lane rounding a tight curve. Approximately eleven …A Zoox vehicle in autonomous mode was traveling northbound on an access road towards [XXX] in Las Vegas, Nevada, when the driver disengaged for a vehicle in the oncoming lane rounding a tight curve. Approximately eleven seconds after disengaging, the driver proceeded in manual mode making a right turn and struck the curb at low speed. There were no injuries and police were not called. |
| 30610-5225 v2 | ADS | Zoox, Inc. | 2023-03 14:40 | Paradise, NV | 2016 Toyota Highlander | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | A Zoox vehicle in autonomous mode was stopped in a merge lane from northbound [XXX] onto [XXX] yielding and waiting for cross traffic. As it began to creep forward, it again came to a stop and it was struck by the vehicl…A Zoox vehicle in autonomous mode was stopped in a merge lane from northbound [XXX] onto [XXX] yielding and waiting for cross traffic. As it began to creep forward, it again came to a stop and it was struck by the vehicle behind at low speed. There were no injuries and police were not called. This report was updated to change the mileage section to "Highlander". |
| 540-4965 v2 | ADS | General Motors, LLC | 2023-03 01:06 | San Francisco, CA | 2022 Cruise AV | ADS | Passenger Car | No Injuries Reported | 3 | Intersection | On March 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On March 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-4960-2) |
| 540-5000 v2 | ADS | General Motors, LLC | 2023-03 13:01 | Tempe, AZ | 2023 Cruise AV | ADS | Passenger Car | Minor | 6 | Intersection | On March 20, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufac…On March 20, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day update to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-4996-2). |
| 540-5102 v3 | ADS | General Motors, LLC | 2023-03 3:26 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 21 | Intersection | On March 27, 2023 GM Cruise Holdings LLC ("Cruise") filed a 10 day update Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured th…On March 27, 2023 GM Cruise Holdings LLC ("Cruise") filed a 10 day update Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5101-2). |
| 540-5137 v2 | ADS | General Motors, LLC | 2023-03 04:29 | San Francisco, CA | 2022 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 15 | Street | On March 31, 2023 GM Cruise Holdings LLC ("Cruise") filed a 10 day Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruis…On March 31, 2023 GM Cruise Holdings LLC ("Cruise") filed a 10 day Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5136-2) |
| 540-5141 v2 | ADS | General Motors, LLC | 2023-03 14:46 | San Francisco, CA | 2023 Cruise AV | ADS | Bus | No Injuries Reported | 10 | Street | On March 31, 2023 GM Cruise Holdings LLC ("Cruise") filed a 10 day update Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured th…On March 31, 2023 GM Cruise Holdings LLC ("Cruise") filed a 10 day update Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5140-2) |
| 540-5261 | ADS | General Motors, LLC | 2023-03 04:23 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file:30412-5229-1) |
| 540-5262 | ADS | General Motors, LLC | 2023-03 23:51 | San Francisco, CA | 2023 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file:30412-5240-1) |
| 540-5263 | ADS | General Motors, LLC | 2023-03 21:49 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 10 | Street | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file:30412-5241-1) |
| 540-5264 | ADS | General Motors, LLC | 2023-03 03:20 | San Francisco, CA | 2023 Cruise AV | ADS | Other, see Narrative | No Injuries Reported | 12 | Street | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file:30412-5242-1) |
| 540-5265 | ADS | General Motors, LLC | 2023-03 23:30 | San Francisco, CA | 2023 Cruise AV | ADS | Passenger Car | No Injuries Reported | 0 | Street | On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On April 13, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file:30412-5243-1) |
| 62-8931 v2 | Level 2 | Honda (American Honda Motor Co.) | 2023-03 | COSTA MESA, CA | 2022 ACURA MDX | ADAS | Passenger Car | No Injuries Reported | 45 | Street | The customer contacted Honda Automobile Customer Service to discuss an unpaid balance on his totaled vehicle and requested to be connected with Honda Finance. When asked for details about the incident, the customer provi…The customer contacted Honda Automobile Customer Service to discuss an unpaid balance on his totaled vehicle and requested to be connected with Honda Finance. When asked for details about the incident, the customer provided the following information. On March [XXX], 2023, the customer was traveling at approximately 45 MPH on a curvy road with Adaptive Cruise Control (ACC), Lane Keeping Assist System (LKAS), and Collision Mitigation Braking System (CMBS) engaged. The vehicle allegedly collided with a car parked illegally in a red zone. The customer reported that CMBS did not engage the brakes before the collision. ACC controlled the vehicles speed, and both ACC and LKAS were activated 20-30 minutes before the incident. No disengagements were reported. The weather was clear, and the customer did not notice any steering corrections from LKAS before the crash. Following the collision, the vehicles airbags deployed, though the customer could not recall which ones. The vehicle was towed from the scene, and the insurance company later declared it a total loss. No previous report updates apply, and no media sources were used. |
| 988-5310 | ADS | PACCAR Incorporated | 2023-03 8:01 | Weatherford, TX | 2022 Peterbilt 579 | Unknown, see Narrative | Passenger Car | No Injuries Reported | 65 | Highway / Freeway | At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicl…At 8:01 AM CDT on 3/[XXX]/23, an Aurora Class 8 truck was traveling westbound in autonomy mode on [XXX] near [XXX] when a passing vehicle encroached on the Aurora trucks lane. The Aurora truck nudged right for the vehicle encroaching on the lane. This vehicle continued to veer toward Aurora's truck at over 65 miles per hour, causing a collision. Aurora disengaged autonomy before impact and pulled to the shoulder along with the involved vehicle. Both vehicles were able to be driven from the scene, and there were no reported injuries. |
| 10039-4932 v5 | Level 2 | BMW of North America, LLC | 2023-02 | Waltham, MA | 2020 BMW 745e xDrive | ADAS | Passenger Car | No Injuries Reported | 63 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1243-4930 v4 | Level 2 | Subaru of America, Inc. | 2023-02 09:40 | Jefferson, NC | 2021 Subaru Outback | ADAS | Heavy Truck | No Injuries Reported | 45 | Rural Road | Redacted by NHTSA as confidential business information |
| 1306-5139 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2023-02 13:13 | Richmond, VA | 2023 Toyota Corolla Hyrbid | ADAS | Other Fixed Object | No Injuries Reported | 30 | Highway / Freeway | On February 17, 2023, Toyota received an allegation related to this crash from the owner of the vehicle through a call to the Toyota Brand Engagement Center. The contact record indicates that the owner alleged that, "She…On February 17, 2023, Toyota received an allegation related to this crash from the owner of the vehicle through a call to the Toyota Brand Engagement Center. The contact record indicates that the owner alleged that, "She was driving home from work and was going down on a ramp from a highway. As she was turning on the ramp, she proceeded to turn the steering wheel to turn the vehicle along the ramp. When she was turning the steering wheel, she noticed that the wheels of the vehicle would not turn with it. She kept going straight and ended up hitting a wall and bounced into a ditch." On March 14, 2023, Toyota completed a vehicle inspection and field report on the incident. There were no allegations made related to the Dynamic Radar Cruise Control (DRCC) or Lane Trace Assist (LTA). However, on March 24, 2023, after additional analysis of the incident details, Toyota determined the case was reportable under the SGO. Toyota obtained Vehicle Control History (VCH) and Event Data Recorder (EDR) data from the subject vehicle. VCH provides an approximately 7 second pre-crash data recording, and EDR provides an approximately 4.7 second pre-crash data recording. Based on the data obtained, the following information was observed: LTA was engaged during the recording from approximately 6 seconds until approximately 3 seconds prior to the crash event, at which point the driver's steering input disengaged the system. At the time of LTA disengagement, the driver turned the vehicle right at a steering angle increasing from 53 degrees to 465 degrees. DRCC was engaged during the recording until approx. 1.7 seconds prior to the crash event. No FCW or AEB activation occurred. As a result of the crash incident, no airbags deployed in the subject vehicle and it was towed from the crash scene. This report is a 10-Day update. The original report ID is 1306-5139-1. |
| 13781-10523 | Level 2 | Tesla, Inc. | 2023-02 09:23 | Lakewood, CO | 2019 Tesla Model 3 | Unknown, see Narrative | Passenger Car | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-4807 v2 | Level 2 | Tesla, Inc. | 2023-02 00:44 | Chicago, IL | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 51 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4808 v2 | Level 2 | Tesla, Inc. | 2023-02 05:11 | Palm Beach Gardens, FL | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 57 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4824 v2 | Level 2 | Tesla, Inc. | 2023-02 04:10 | Phoenix, AZ | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 21 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4825 v2 | Level 2 | Tesla, Inc. | 2023-02 16:24 | Brea, CA | 2020 Tesla Model 3 | ADAS | Unknown | Unknown | 67 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-4830 v2 | Level 2 | Tesla, Inc. | 2023-02 19:42 | Silver Spring, MD | 2021 Tesla Model Y | ADAS | Unknown | Unknown | 27 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-4831 v2 | Level 2 | Tesla, Inc. | 2023-02 22:13 | Chicago, IL | 2022 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 57 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4835 v2 | Level 2 | Tesla, Inc. | 2023-02 11:03 | Baldwin Park, CA | 2023 Tesla Model 3 | ADAS | Passenger Car | Unknown | 97 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4908 v2 | Level 2 | Tesla, Inc. | 2023-02 07:35 | New Waverly, TX | 2023 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 81 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4909 v2 | Level 2 | Tesla, Inc. | 2023-02 14:08 | Tukwila, WA | 2018 Tesla Model X | ADAS | Other Fixed Object | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4910 v2 | Level 2 | Tesla, Inc. | 2023-02 17:38 | La Grange, TX | 2022 Tesla Model Y | ADAS | Other, see Narrative | Unknown | 37 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4911 v2 | Level 2 | Tesla, Inc. | 2023-02 05:29 | Gunnison, CO | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 40 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4912 v2 | Level 2 | Tesla, Inc. | 2023-02 16:00 | Fremont, CA | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 54 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4913 v2 | Level 2 | Tesla, Inc. | 2023-02 01:46 | Palmdale, CA | 2019 Tesla Model S | ADAS | Unknown | Unknown | 78 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4915 v2 | Level 2 | Tesla, Inc. | 2023-02 02:21 | Gold Run, CA | 2021 Tesla Model 3 | ADAS | SUV | Unknown | 34 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4916 v2 | Level 2 | Tesla, Inc. | 2023-02 22:34 | Santa Monica, CA | 2018 Tesla Model 3 | ADAS | Passenger Car | Unknown | 22 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4917 v2 | Level 2 | Tesla, Inc. | 2023-02 14:29 | Fort Smith, AR | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 33 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4918 v2 | Level 2 | Tesla, Inc. | 2023-02 13:01 | Anaheim, CA | 2020 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 49 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4923 v2 | Level 2 | Tesla, Inc. | 2023-02 14:29 | Orange, CA | 2021 Tesla Model 3 | ADAS | Other, see Narrative | Unknown | 40 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4924 v2 | Level 2 | Tesla, Inc. | 2023-02 21:48 | Princeton, NJ | 2021 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 38 | Street | Redacted by NHTSA as confidential business information |
| 13781-4925 v2 | Level 2 | Tesla, Inc. | 2023-02 04:27 | Irvine, CA | 2021 Tesla Model Y | ADAS | Passenger Car | Unknown | 61 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4926 v2 | Level 2 | Tesla, Inc. | 2023-02 14:27 | Santa Ana, CA | 2020 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4927 v2 | Level 2 | Tesla, Inc. | 2023-02 22:00 | Glastonbury, CT | 2021 Tesla Model Y | ADAS | Unknown | Unknown | 34 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-4928 v2 | Level 2 | Tesla, Inc. | 2023-02 22:55 | Buena Park, CA | 2021 Tesla Model S | ADAS | Other Fixed Object | Unknown | 8 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4929 v2 | Level 2 | Tesla, Inc. | 2023-02 | Reston, VA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-4933 v2 | Level 2 | Tesla, Inc. | 2023-02 13:43 | Orlando, FL | 2022 Tesla Model 3 | ADAS | Pickup Truck | Unknown | 17 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4944 v2 | Level 2 | Tesla, Inc. | 2023-02 14:41 | Buena Park, CA | 2023 Tesla Model 3 | ADAS | Passenger Car | Unknown | 0 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4951 v2 | Level 2 | Tesla, Inc. | 2023-02 10:59 | Fort Lauderdale, FL | 2022 Tesla Model Y | ADAS | Unknown | Unknown | 30 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-4963 v2 | Level 2 | Tesla, Inc. | 2023-02 11:53 | Walnut Creek, CA | 2014 Tesla Model S | ADAS | First Responder Vehicle | Fatality | 71 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-7228 v2 | Level 2 | Tesla, Inc. | 2023-02 | Wolf Trap, VA | 2019 Tesla Model 3 | Unknown, see Narrative | Other Fixed Object | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30270-4906 v2 | ADS | Waymo LLC | 2023-02 13:08 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 13 | Highway / Freeway | Other than removing the time zone from the narrative below and correcting the total number of lanes on the highway, the content of this report is unchanged from the initial report submitted on February 19, 2023 [REDACTED…Other than removing the time zone from the narrative below and correcting the total number of lanes on the highway, the content of this report is unchanged from the initial report submitted on February 19, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On February [XXX], 2023 at 1:08 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Tempe, AZ was in a collision involving a Passenger Car on [XXX] near [XXX] ([XXX]). The Waymo AV was traveling in the second lane from the right (lane 5 out of 6 lanes) in the eastbound direction of [XXX] when it started to decelerate in response to slow traffic ahead in the AVs lane. A passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. The other vehicle left the scene without exchanging information. 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-5081 | ADS | Waymo LLC | 2023-02 05:44 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Other Fixed Object | No Injuries Reported | 12 | Intersection | On February [XXX], 2023 at 5:43 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving road debris on [XXX] at [XXX]. The Waymo AV was proceeding East on [XXX] …On February [XXX], 2023 at 5:43 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving road debris on [XXX] at [XXX]. The Waymo AV was proceeding East on [XXX] through the intersection with [XXX] when the front of the Waymo AV made contact with cardboard debris. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5082 | ADS | Waymo LLC | 2023-02 17:27 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 40 | Street | On February [XXX], 2023 at 5:27 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling North on [XXX] in the rightmost…On February [XXX], 2023 at 5:27 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling North on [XXX] in the rightmost lane. As the Waymo AV approached the intersection of [XXX], traffic in the two lanes to the left of the Waymo AV was backed up and moving slowly or stopped. A SUV attempted to merge from the leftmost lane across a gap in traffic in the center lane and into the rightmost lane. While attempting to enter the Waymo AV's lane, the front right of the SUV made contact with the rear left 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. 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-5083 | ADS | Waymo LLC | 2023-02 00:15 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 14 | Intersection | On February [XXX], 2023 at 12:15 AM PST 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 traveling southw…On February [XXX], 2023 at 12:15 AM PST 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 traveling southwest on [XXX] in autonomous mode. While the Waymo AV was making a left turn onto [XXX], a passenger vehicle proceeded into the intersection from the left and made contact with the left side of the Waymo AV. The other vehicle immediately left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-5085 v2 | ADS | Waymo LLC | 2023-02 07:23 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | On February [XXX], 2023 at 7:23 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was proceeding East on [XX…On February [XXX], 2023 at 7:23 AM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was proceeding East on [XXX] near the intersection with [XXX] when it came to a stop to yield to a heavy truck traveling West on [XXX]. As the heavy truck moved past the Waymo AV, the front left tire of the heavy truck made contact with the rear left sensor of the Waymo AV. The heavy truck then left the scene. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo is submitting this correction to the GENERAL DAMAGE / CONTACT AREA for the Heavy Truck from Report 30270-5085-1 which was submitted earlier today. |
| 30391-4811 v2 | ADS | Kodiak Robotics | 2023-02 10:15 | Waxahachie, TX | 2023 Kenworth Motor Truck Co T680 | ADS | SUV | No Injuries Reported | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30391-5009 | ADS | Kodiak Robotics | 2023-02 10:15 | Waxahachie, TX | 2023 Kenworth Motor Truck Co T680 | ADS | SUV | No Injuries Reported | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 30410-5003 | ADS | Motional | 2023-02 14:18 | Las Vegas, NV | 2021 Hyundai Ioniq 5 | ADAS | Passenger Car | No Injuries Reported | 10 | Street | Redacted by NHTSA as confidential business information |
| 30412-4829 v2 | ADS | Cruise LLC | 2023-02 00:39 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 7 | Intersection | Redacted by NHTSA as confidential business information |
| 30412-5035 | ADS | Cruise LLC | 2023-02 02:05 | San Francisco, CA | 2022 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information |
| 30412-5036 | ADS | Cruise LLC | 2023-02 00:29 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 24 | Street | Redacted by NHTSA as confidential business information |
| 30531-4907 v2 | ADS | Transdev Alternative Services | 2023-02 13:08 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 13 | Highway / Freeway | On February [XXX], 2023 at 1:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, AZ was in a collision involving a Passenger Car on [XXX] near [XXX] ([XXX]). The Waymo AV was traveling in the second lan…On February [XXX], 2023 at 1:08 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, AZ was in a collision involving a Passenger Car on [XXX] near [XXX] ([XXX]). The Waymo AV was traveling in the second lane from the right (lane 5 out of 6 lanes) in the eastbound direction of [XXX] when it started to decelerate in response to slow traffic ahead in the AV's lane. A passenger vehicle approached the Waymo AV from behind and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. The other vehicle left the scene without exchanging information. Transdev Alternative Services is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Transdev may supplement or correct its reporting with additional information as it may become available. This report is a duplicate of Report ID: 30270-4906-1 |
| 30531-5088 | ADS | Transdev Alternative Services | 2023-02 17:27 | Tempe, AZ | 2021 Jaguar I-Pace | ADS | SUV | No Injuries Reported | 40 | Street | On February [XXX], 2023 at 5:27 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling North on [XXX] in the right most…On February [XXX], 2023 at 5:27 PM PST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was traveling North on [XXX] in the right most lane. As the Waymo AV approached the intersection of [XXX], traffic in the two lanes to the left of the Waymo AV was backed up and slow or stopped. A SUV attempted to merge from the leftmost lane across a gap in traffic in the center lane and into the rightmost lane. While attempting to enter the Waymo AV's lane, the front right of the SUV made contact with the rear left 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. 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. |
| 30610-4810 v2 | ADS | Zoox, Inc. | 2023-02 13:50 | Paradise, NV | 2016 Toyota Highlander | ADS | Non-Motorist: Cyclist | Minor | 0 | Intersection | A Zoox vehicle in autonomy was stopped in a merge lane yielding and waiting for cross traffic when a bicyclist approached the side of the vehicle on a parallel path and made a gesture to the driver. When the Zoox vehicle…A Zoox vehicle in autonomy was stopped in a merge lane yielding and waiting for cross traffic when a bicyclist approached the side of the vehicle on a parallel path and made a gesture to the driver. When the Zoox vehicle began to move and had reached approximately 5mph, the cyclist changed trajectory towards the Zoox vehicle, which braked, and the cyclist made low speed contact with the rear of the Zoox vehicle. The cyclist reported no injury at the scene, but later followed up with an email stating he was sore. Police were not called, contact information was exchanged, and the cyclist rode away. This 10-Day update provides complete information for this incident. |
| 30610-4993 v2 | ADS | Zoox, Inc. | 2023-02 14:28 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 7 | Intersection | A Zoox vehicle in autonomous mode was making a right turn to travel southwest onto [XXX] from [XXX] from lane 1 when Vehicle 2 crossed from lane 3 into the Zoox vehicle's lane and made contact with the Zoox vehicle's fro…A Zoox vehicle in autonomous mode was making a right turn to travel southwest onto [XXX] from [XXX] from lane 1 when Vehicle 2 crossed from lane 3 into the Zoox vehicle's lane and made contact with the Zoox vehicle's front sensors before making the right turn. Vehicle 2 did not stop before leaving the scene. No information was exchanged. There were no injuries and the police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. |
| 30610-4994 v2 | ADS | Zoox, Inc. | 2023-02 13:27 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 0 | Street | A Zoox vehicle in autonomy was stopped with brake lights illuminated in traffic southbound on [XXX] towards [XXX]. When traffic ahead began to move the Zoox vehicle was appropriately following the car ahead at low speed …A Zoox vehicle in autonomy was stopped with brake lights illuminated in traffic southbound on [XXX] towards [XXX]. When traffic ahead began to move the Zoox vehicle was appropriately following the car ahead at low speed when it was rear ended by Vehicle #2 at low speed. The other party did not stop to exchange information and left the scene. There were no injuries and police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. |
| 30610-4995 v2 | ADS | Zoox, Inc. | 2023-02 18:06 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 0 | Street | A Zoox vehicle in autonomous mode was slowing to a stop with brake lights illuminated behind traffic on northbound [XXX] near [XXX] when a vehicle behind made contact at approximately 10mph. There were no injuries and po…A Zoox vehicle in autonomous mode was slowing to a stop with brake lights illuminated behind traffic on northbound [XXX] near [XXX] when a vehicle behind made contact at approximately 10mph. There were no injuries and police were not called. Zoox is submitting this updated report to correct a previous reporting error in the HIGHEST INJURY SEVERITY field. |
| 540-4832 v2 | ADS | General Motors, LLC | 2023-02 00:39 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 7 | Intersection | On February 17, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manu…On February 17, 2023, GM Cruise Holdings LLC ("Cruise") filed a 10 day report to an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-4829-2) |
| 540-4898 v2 | Level 2 | General Motors, LLC | 2023-02 22:12 | San Jose, CA | 2022 Chevrolet Bolt EUV | ADAS | Unknown | Unknown | 53 | Highway / Freeway | GM has no updates to the original submission for the 10 day update from that which was submitted on February 17, 2023. The subject vehicle, a 2002 Bolt EUV, was in a crash in with two frontal impacts. GM's current unders…GM has no updates to the original submission for the 10 day update from that which was submitted on February 17, 2023. The subject vehicle, a 2002 Bolt EUV, was in a crash in with two frontal impacts. GM's current understanding of the crash is based on OnStar telematics data. The subject vehicle was traveling southwest on [XXX] when two front impacts were recorded. It is unknown what the subject vehicle contacted. Super Cruise was not active in the 11 seconds before the crash. The driver was the sole occupant of the vehicle and was buckled at the time of the crash. It is not known whether the driver was injured. The driver's airbag deployed in the crash. |
| 540-5060 | ADS | General Motors, LLC | 2023-02 02:05 | San Fancisco, CA | 2022 Cruise AV | ADS | Heavy Truck | No Injuries Reported | 0 | Street | On March 14, 2023 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-oper…On March 14, 2023 GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5035-1) |
| 540-5061 | ADS | General Motors, LLC | 2023-02 00:29 | San Francisco, CA | 2023 Cruise AV | ADS | Van | No Injuries Reported | 24 | Street | On March 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-ope…On March 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an Incident Report (the "Report") under the Standing General Order 2021-01 dated June 29, 2021 (the "Order"). General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-5036-1) |
| 753-4922 v4 | Level 2 | Kia America, Inc. | 2023-02 02:45 | CT | 2022 KIA SORENTO | Unknown, see Narrative | SUV | Minor | 64 | Highway / Freeway | *2/25/23: 1-Day Incident Report* Customer contacted Kia Customer Care on 2/[XXX]/23 & reported that he was driving his 22 Kia Sorento 65mph on [XXX] near Meridian, CT when he fell asleep. Customer stated he heard beepin…*2/25/23: 1-Day Incident Report* Customer contacted Kia Customer Care on 2/[XXX]/23 & reported that he was driving his 22 Kia Sorento 65mph on [XXX] near Meridian, CT when he fell asleep. Customer stated he heard beeping, went to hit the brakes but it was too late & his vehicle rear ended the vehicle in front of him. The driver & passenger airbags deployed. The customer reported him & his wife were taken to the ER via ambulance. He reported that his upper body was sore (mostly wrist & left hand) & that his wife sustained a swollen ankle & bruising on the right side of her body. The vehicle was towed. Customer stated that he believed the accident was his fault but claims the Forward Collision Avoidance (FCA) system in this vehicle was not working properly. The subject 22 Sorento is equipped with Highway Driving Assist (HDA). HDA is a supplemental system that helps maintain a set distance & speed from the vehicle ahead when driving on a highway & helps keep the vehicle between lanes while driving. HDA may not be able to recognize all traffic situations. Obstacles such as vehicles, motorcycles, bicycles, pedestrians, unspecified objects & structures that may collide with the vehicle may not be detected. Based on the information currently available, Kia is unable to rule out that HDA was not engaged at the time of the incident. Kia is currently working on obtaining the ACU for further evaluation. *3/6/23: 10-Day Update* There are no new updates. Kia continues to work to obtain the ACU. *3/15/23: Monthly Update* Kia has requested & is waiting for the ACU from the customer's body shop. *7/14/23: Monthly Update* Kia received the ACU from the subject 2022MY Kia Sorento and downloaded the vehicle's EDR data. The EDR data indicates that the incident did not occur during engagement of Level 2 ADAS. The EDR data shows that the driver was applying the throttle via the accelerator pedal (44% throttle application). As a result, the driver was overriding the vehicle's ADAS functionality (i.e., Smart Cruise Control and Front Collision Avoidance) at the time of the incident. Kia notes that the vehicle is designed with such override logic to give a driver's input priority over the ADAS features (e.g., perform emergency avoidance maneuvers, etc.) In light of the above, Kia believes that this incident is no longer eligible for continued updates. |
| 855-5055 | ADS | Mercedes-Benz USA, LLC | 2023-02 08:25 | Downey, CA | 2021 Mercedes-Benz S580 | ADS | Heavy Truck | No Injuries Reported | Highway / Freeway | Mercedes-Benz has conducted a review of the incident and the following is based on that review. The subject Mercedes-Benz Drive Pilot test vehicle was traveling between 15-20 mph in the #2 northbound lane on the [XXX] in…Mercedes-Benz has conducted a review of the incident and the following is based on that review. The subject Mercedes-Benz Drive Pilot test vehicle was traveling between 15-20 mph in the #2 northbound lane on the [XXX] in California in stop and go traffic with the L3 ADS activated by the driver. The vehicle's ADS determined that a truck traveling in the adjacent lane had a trajectory towards the Drive Pilot's lane, and so the Mercedes-Benz test vehicle autonomously applied the brakes to avoid a collision. After applying the brakes and bringing itself to a standstill, the Mercedes-Benz was then struck in the rear bumper by a trailing semi-truck that did not stop in time. No injuries were reported, no airbags deployed in either vehicle, and both vehicles were able to be driven from the scene of the incident. The Mercedes-Benz vehicle experienced minor damage to the rear bumper, and no damage was observed on the semi-truck at the scene. The CA Traffic Collision Report for the subject incident noted a violation of California Vehicle Code 22350 (unsafe speed for traffic conditions) by the semi-truck in the #2 lane that struck the rear bumper of the Mercedes-Benz. | |
| 855-5058 | ADS | Mercedes-Benz USA, LLC | 2023-02 15:10 | Gardena, CA | 2022 Mercedes-Benz S580 | Unknown, see Narrative | SUV | No Injuries Reported | Highway / Freeway | The subject Mercedes-Benz vehicle was driving in stop and go traffic on the [XXX] in Gardena, California with the L3 ADS activated. The test route selected by the driver in the vehicle's navigation system indicated an up…The subject Mercedes-Benz vehicle was driving in stop and go traffic on the [XXX] in Gardena, California with the L3 ADS activated. The test route selected by the driver in the vehicle's navigation system indicated an upcoming exit, so the driver began to prepare for a lane change towards the highway exit by deactivating the L3 ADS and activating the turn signal. Once the vehicle was in conventional driving mode, the driver looked for a gap in the adjacent lane to merge towards the exit lane, applied the brakes, and slowed the vehicle down. The SUV following the Mercedes-Benz vehicle did not respond in time to the vehicle's braking and contacted the rear of the Mercedes-Benz approximately 10 seconds after the L3 ADS was deactivated. The Mercedes-Benz vehicle experienced minor damage to the rear bumper. No injuries were reported, no airbags deployed in either vehicle, and both vehicles were driven from the scene of the incident. | |
| 988-4816 | ADS | PACCAR Incorporated | 2023-02 10:15 | Waxahachie, TX | 2023 Kenworth Motor Truck Co T680 | ADS | SUV | No Injuries Reported | 56 | Highway / Freeway | A police report was issued after the 1-Day SGO incident report was submitted. It determined the driver of the crossover SUV to be at fault and noted that the crossover SUV's driver advised officers that he fell asleep wh…A police report was issued after the 1-Day SGO incident report was submitted. It determined the driver of the crossover SUV to be at fault and noted that the crossover SUV's driver advised officers that he fell asleep while driving and caused the accident. The content of this incident report is otherwise unchanged from the initial incident report submitted on February 7, 2023. On February 7, 2023, Kodiak Robotics, Inc. ("Kodiak") filed an Incident Report (the "Report") under the Standing General Order 2021-01 (the "Order"). PACCAR, Inc. (Paccar) manufactured the Kodiak-operated motor vehicle involved in the incident summarized in the Incident Report. Because Paccar is also a Reporting Entity under the Order, Paccar is submitting a duplicate of the redacted public copy of the Report. Paccar has selected "Unknown" in the "ADS version" field solely to avoid a second submission of nonpublic Kodiak CBI. Paccar is in possession of Kodiak's response to this field and incorporates Kodiak's response into this submission by reference. Paccar's submission is based on facts supplied to Paccar by Kodiak. Paccar 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. |
| 12381-4852 v4 | Level 2 | Daimler Trucks North America, LLC | 2023-01 11:57 | Lexington, SC | 2022 FREIGHTLINER Cascadia | ADAS | Heavy Truck | No Injuries Reported | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1306-4717 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2023-01 10:15 | Nash, TX | 2020 Lexus UX200 | ADAS | Unknown | Unknown | 48 | Intersection | Some entries in this report are based on unconfirmed allegations. On January 18, 2023 Toyota completed a field report related to this crash incident, in which the owner's allegation was related to Pre-Collision System (P…Some entries in this report are based on unconfirmed allegations. On January 18, 2023 Toyota completed a field report related to this crash incident, in which the owner's allegation was related to Pre-Collision System (PCS) non-activation. The owner alleged she was driving on [XXX] through the [XXX], "when another vehicle entered the intersection to her left, driving at a high rate of speed." She also claimed that she, "had a green light, and the other vehicle ran a red light," and she, "struck the other vehicle in its right side with the front of her Lexus." After the initial impact, the owner's vehicle "spun to the right, then came to a stop." The owner alleged that her, "vehicle's Pre-Collision System should have stopped the car and avoided the accident," and the, "PCS system did not function." There were no allegations made related to the operation of Dynamic Radar Cruise Control (DRCC) or Lane Trace Assist (LTA). However, upon obtaining and reviewing VCH and EDR data from the crash event, Toyota became aware that the vehicle was operating with ADAS L2 engagement in the moments leading up to the crash event. VCH provides an approximately 7.9 second pre-crash data recording, and EDR provides an approximately 4.8 second pre-crash data recording. Based on the data obtained, the following information was observed: LTA was engaged from the start of the recording until approximately 1 second prior to the crash event. DRCC was engaged from the start of the recording until the crash event. The PCS warning (FCW) and Automatic Emergency Braking (AEB) did not activate during the recording of the event, because the Lexus Safety System generation of this vehicle (LSS + 2.0) does not support cross traffic PCS functions. As a result of the crash event, multiple airbags deployed in the owner's vehicle which was towed from the scene. The owner claimed that she, "could not breathe because of the accident. She said her left wrist was bruised, her left knee is sore and her ribcage hurts." |
| 13781-4583 v2 | Level 2 | Tesla, Inc. | 2023-01 17:44 | Milwaukee, WI | 2022 Tesla Model 3 | ADAS | Passenger Car | Unknown | 23 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4584 v2 | Level 2 | Tesla, Inc. | 2023-01 16:08 | Dublin, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-4587 v2 | Level 2 | Tesla, Inc. | 2023-01 00:15 | Kramer Junction, CA | 2023 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4590 v2 | Level 2 | Tesla, Inc. | 2023-01 23:07 | Hypoluxo, FL | 2022 Tesla Model S | ADAS | Pickup Truck | Unknown | 17 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4592 v2 | Level 2 | Tesla, Inc. | 2023-01 07:22 | Tinton Falls, NJ | 2020 Tesla Model 3 | ADAS | Animal | Unknown | 73 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4596 v2 | Level 2 | Tesla, Inc. | 2023-01 03:52 | Noble, KS | 2018 Tesla Model X | ADAS | Unknown | Unknown | 50 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-4597 v2 | Level 2 | Tesla, Inc. | 2023-01 01:36 | San Mateo, CA | 2021 Tesla Model S | ADAS | Unknown | Unknown | 49 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-4598 v2 | Level 2 | Tesla, Inc. | 2023-01 07:07 | Harbor City, CA | 2021 Tesla Model Y | ADAS | Other Fixed Object | Unknown | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4607 v2 | Level 2 | Tesla, Inc. | 2023-01 22:28 | Goldsboro, MD | 2022 Tesla Model Y | ADAS | SUV | Unknown | 4 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4608 v2 | Level 2 | Tesla, Inc. | 2023-01 02:59 | Chicago, IL | 2019 Tesla Model 3 | ADAS | Passenger Car | Unknown | 21 | Street | Redacted by NHTSA as confidential business information |
| 13781-4609 v2 | Level 2 | Tesla, Inc. | 2023-01 10:49 | City of New York, NY | 2020 Tesla Model 3 | ADAS | Pole / Tree | Unknown | 18 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-4610 v2 | Level 2 | Tesla, Inc. | 2023-01 01:16 | City of New York, NY | 2022 Tesla Model 3 | ADAS | Other Fixed Object | Unknown | 33 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-4611 v2 | Level 2 | Tesla, Inc. | 2023-01 01:58 | Yakima, WA | 2021 Tesla Model X | ADAS | Passenger Car | Unknown | 35 | Intersection | 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. 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. The themed reading of the driverless narratives is on the reports page.