The SGO file, in a form you can search
NHTSA publishes the crash reports as three CSV files of 116 columns each, with several versions of the same report mixed in. This is the same data as one table: driverless systems (ADS) and Level 2 driver assistance side by side, 2021 to today including NHTSA's archive, one row per report at its latest version, every row traceable to its NHTSA report number. Free, CC BY 4.0, refreshed from NHTSA on every pipeline run.
- Reports
- 8612
- Fatal
- 87
- Of them Level 2
- 79
- Reporting entities
- 64
- Incidents
- 2019-08 to 2026-09
443 reports, showing 401 to 443.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 | TMR-0204 | 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) | |
| 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. | |
| 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-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) | |
| 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. | |
| 30270-4768 v2 | ADS | Waymo LLC | 2023-01 13:38 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | Motorcycle | No Injuries Reported | 8 | Intersection | Other than updating the Law Enforcement Investigating? field, the content of this report is unchanged from the initial report submitted on January 25, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On J…Other than updating the Law Enforcement Investigating? field, the content of this report is unchanged from the initial report submitted on January 25, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On January [XXX], 2023 at 1:38 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision with a minibike whose rider was no longer on it on [XXX] at [XXX]. The Waymo AV was traveling in the leftmost lane on eastbound [XXX], with a group of smaller motorcycles, more commonly known as minibikes, traveling in the right adjacent lane next to and ahead of the Waymo AV. A minibike rider in the group lost control and fell off the minibike a short distance ahead of the Waymo AV in the adjacent lane and the minibike, without a rider, tumbled into the Waymo AV's lane. The Waymo AV applied maximum brake force but made contact with the riderless minibike just before coming to a stop. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The minibike was damaged but it is not possible to determine whether all or some of that damage occurred when the minibike fell to the road before the collision. Because we checked on the minibike riders well-being shortly after the crash, Waymo is aware that the individual sustained minor injuries when they fell from the minibike but the subsequent collision with the riderless minibike did not cause those injuries. Although we do not believe this event falls under Request No. 1 of Standing General Order 2021-01, we consulted NHTSA and submitted this report at the agencys request on the day of the consultation. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-4880 | ADS | Waymo LLC | 2023-01 17:36 | Phoenix, AZ | 2021 Jaguar I-Pace | ADS | First Responder Vehicle | No Injuries Reported | 0 | Parking Lot | On January [XXX], 2023 at 5:36 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a tow truck in a parking lot near [XXX] and [XXX]. While the Waymo AV stopped in a pa…On January [XXX], 2023 at 5:36 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a tow truck in a parking lot near [XXX] and [XXX]. While the Waymo AV stopped in a parking lot in autonomous mode, a tow truck approached from behind the Waymo and attempted to complete a multi-point turn. While performing a multi-point turn, the tow truck reversed into the rear left sensor of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. The Waymo sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-4881 | ADS | Waymo LLC | 2023-01 17:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 34 | Intersection | On January [XXX], 2023 at 5:08 PM 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 north on […On January [XXX], 2023 at 5:08 PM 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 north on [XXX] when, upon entering the intersection at [XXX], a passenger vehicle which had previously been stopped at a red light, proceeded through the red light. The passenger vehicle approached from the left and made contact with the left rear bumper of the Waymo AV. The other vehicle immediately left the scene of the collision. 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. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-4882 | ADS | Waymo LLC | 2023-01 13:53 | Chandler, AZ | 2017 Chrysler Pacifica | ADS | Pickup Truck | No Injuries Reported | 0 | Intersection | On January [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a pickup truck on [XXX] and [XXX]. While attempting a right turn from [XXX] onto [XX…On January [XXX], 2023 at 1:53 PM PST a Waymo Autonomous Vehicle (Waymo AV) operating in Chandler, Arizona was in a collision involving a pickup truck on [XXX] and [XXX]. While attempting a right turn from [XXX] onto [XXX], the Waymo AV was stopped at a stop sign while yielding to traffic approaching from the left. A truck that had previously been stopped behind the Waymo AV proceeded forward and made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. 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-7598 | ADS | Waymo LLC | 2023-01 17:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 34 | Intersection | On January [XXX], 2023 at 5:08 PM 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 north on […On January [XXX], 2023 at 5:08 PM 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 north on [XXX] when, upon entering the intersection at [XXX], a passenger vehicle which had previously been stopped at a red light, proceeded through the red light. The passenger vehicle approached from the left and made contact with the left rear bumper of the Waymo AV. The other vehicle immediately left the scene of the collision. 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. 2 of Standing General Order 2021-01. This is an update to the previously submitted report 30270-7257 submitted on 2/15/2023, which had incorrectly provided the DRIVER / OPERATOR TYPE as "None and the MILEAGE as 22991. | |
| 30410-4799 | ADS | Motional | 2023-01 13:17 | Las Vegas, NV | 2021 Hyundai Ioniq 5 | ADS | Passenger Car | No Injuries Reported | 18 | Street | Redacted by NHTSA as confidential business information | |
| 30531-4883 | ADS | Transdev Alternative Services | 2023-01 17:08 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | No Injuries Reported | 34 | Intersection | On January [XXX], 2023 at 5:08 PM 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 north on…On January [XXX], 2023 at 5:08 PM 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 north on [XXX] when, upon entering the intersection at [XXX], a passenger vehicle which had previously been stopped at a red light, proceeded through the red light. The passenger vehicle approached from the left and made contact with the left rear bumper of the Waymo AV. The other vehicle immediately left the scene of the collision. 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. | |
| 30610-4814 v2 | ADS | Zoox, Inc. | 2023-01 15:00 | Las Vegas, NV | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 24 | Street | A Zoox vehicle was proceeding northbound on [XXX]. towards [XXX]. when a passenger vehicle in the right adjacent lane swerved into the Zoox vehicles lane and made contact with the right passenger side door. The other veh…A Zoox vehicle was proceeding northbound on [XXX]. towards [XXX]. when a passenger vehicle in the right adjacent lane swerved into the Zoox vehicles lane and made contact with the right passenger side door. The other vehicle also made contact with the vehicle in front of them after contacting the Zoox vehicle. There were no injuries reported at that time and police were not called. Zoox is submitting this updated report to include new information of a claim dated [XXX], 2023, including unspecified "personal injury." This update provides complete information to date for this incident. | |
| 30610-4815 | ADS | Zoox, Inc. | 2023-01 18:40 | San Francisco, CA | 2016 Toyota Highlander | ADS | Passenger Car | No Injuries Reported | 3 | Street | A Zoox vehicle in autonomous mode was proceeding straight in its lane on [XXX] in San Francisco, CA when an occupant of a parallel parked car (Vehicle 2) abruptly opened its rear passenger side door into the side of the …A Zoox vehicle in autonomous mode was proceeding straight in its lane on [XXX] in San Francisco, CA when an occupant of a parallel parked car (Vehicle 2) abruptly opened its rear passenger side door into the side of the Zoox vehicle, causing minor damage to both vehicles. The Zoox operator disengaged as a result of the contact. There were no injuries and the police were not called. This a resubmission of the same report and information submitted February 14, 2023. | |
| 30690-4793 | ADS | Robotic Research | 2023-01 11:01 | Peachtree Corners, GA | 2018 Local Motors 2.0 | ADS | Other Fixed Object | No Injuries Reported | 9 | Street | On January [XXX], 2023, RRAI received a support request through their Customer Support Portal from Beep, Inc., the owner of the vehicle, regarding their Olli 2.0 vehicle bumping into the curb in Peachtree Corners, GA. At…On January [XXX], 2023, RRAI received a support request through their Customer Support Portal from Beep, Inc., the owner of the vehicle, regarding their Olli 2.0 vehicle bumping into the curb in Peachtree Corners, GA. At 11:01 am, while running the normal route, the Olli contacted the adjacent curb on the front right side, causing tie rod and cosmetic damage. No one was injured and the only damage was to the vehicle itself. The customer contacted RRAI through the client support portal shortly after the incident. No injuries occurred, there were no passengers besides the safety operator, no other vehicles were involved, and no emergency systems were engaged. Olli 2.0 (S/N 2-18) is an 8-passenger shuttle that is no longer manufactured. The vehicle manufacturer, Local Motors, dissolved in 2022. Local Motors contracted RRAI to install autonomy kits for several Olli shuttles during the period of 2018 - 2020. RRAI provided some support for initial site deployment and ensured customer safety operators were trained on the autonomy system. Since the Local Motors dissolution in 2022, almost all Olli vehicles have been decommissioned. To date, we have concluded the following: 1. There were no updates or alterations made by RRAI in the months prior to Jan [XXX]. In previous operations, including the immediately preceding operations on January 20th, 2023, Olli 2-18 ran the route as normal with no anomalies. There were no software updates or other system changes before it was run again on January [XXX], 2023, the date of curb contact. 2. The root cause of the curb contact was a communication error with the HD Map registration module. HD Map registration utilizes real-time lidar and positioning data and compares that to a-priori HD maps stored within the autonomy system. A communication problem occurred between the computer running the map registration software and the computer running the navigation algorithms. The cause for the communication problem has been identified and a fix has been implemented to prevent the issue from happening again (see below). 3. Steering was out of calibration. It was noted through data collection that the steering was out of calibration at time of incident. The autonomy system was attempting to correct this issue, but the vehicular steering system could not achieve the required turn radius. This is a vehicular maintenance concern managed by the customer. It was determined that the HD map registration issue had not been observed during autonomous operations in the previous four years. The solution to prevent further occurrences includes: 1. Implementing a self-diagnostic routine upon system boot, which ensures the communication connection is established. If the connection is not established, this diagnostic will prevent the vehicle from driving autonomously. 2. Updating the error checks to ensure that during run time, the vehicle will come to a controlled stop in event of a communication problem. 3. Working with the customer to recalibrate the steering, and assisting in reviewing customer's vehicle maintenance checks for steering calibration if necessary. 4. Continuing to review data to determine other concerns or improvements. |
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.