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
10 reports, showing 1 to 10.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-10112 v2 | ADS | Waymo LLC | 2025-02 03:39 | Phoenix, AZ | 2024 Jaguar I-PACE | ADS | Passenger Car | Serious | 44 | Street | The content of this report is unchanged from the initial report submitted on March [XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On February [XXX], 2025 at 3:39 AM MT a Waymo Autonomous Vehicle …The content of this report is unchanged from the initial report submitted on March [XXX], 2025 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On February [XXX], 2025 at 3:39 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an SUV on [XXX]. The Waymo AV was traveling northbound on [XXX] in the left lane towards the intersection of [XXX]. An SUV traveling northbound in the right lane passed the Waymo AV on the right and continued into the dedicated right turn lane as it approached [XXX] Street. The SUV crossed into the intersection with W. Flint Street from the dedicated right turn lane and continued traveling straight onto the far-side sidewalk. The SUV then departed the roadway, striking a fire hydrant and a utility bollard before making contact with a street light. The impact with the street light resulted in the SUV coming to a stop and re-entering the roadway on [XXX] in the Waymo AV's path of travel. The rear side of the SUV made contact with the front passenger side corner of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the SUV was transported to a local hospital for treatment. One of the two passengers in the Waymo AV reported minor injuries but refused medical treatment. Both passengers, who had been seated in the rear of the Waymo AV, were not belted at the time of the collision, having had buckled their belts behind them. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-8968 v2 | ADS | Waymo LLC | 2024-10 08:58 | San Francisco, CA | 2024 Jaguar I-Pace | ADS | SUV | Serious | 0 | Street | The content of this report is unchanged from the initial report submitted on October 29, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2024 at 8:52 AM PT a Waymo Autonomous Vehicle ("…The content of this report is unchanged from the initial report submitted on October 29, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On October [XXX], 2024 at 8:52 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV came to a stop in a queue of traffic for a red traffic light in the rightmost lane of the two eastbound lanes on [XXX] at the intersection with [XXX]. A passenger car traveling west on [XXX] crossed the double yellow line and made contact with an SUV that was alongside the Waymo AV in the left lane of eastbound [XXX]. The impact caused the passenger side of the SUV to make contact with the driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-7681 v2 | ADS | Waymo LLC | 2024-05 00:58 | Los Angeles, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | Serious | 34 | Highway / Freeway | Other than an update to Highest Injury Severity Alleged from Unknown to Serious in reflection of notice of an allegation of injury received by Waymo, the content of this report is unchanged from the initial report submit…Other than an update to Highest Injury Severity Alleged from Unknown to Serious in reflection of notice of an allegation of injury received by Waymo, the content of this report is unchanged from the initial report submitted on May 14, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On May [XXX], 2024 at 12:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, CA was in a collision involving a passenger car on eastbound [XXX] between [XXX] and [XXX]. The Waymo AV was traveling with a test driver present behind a box truck in the number 3 lane of eastbound [XXX] near the [XXX] when a passenger car traveling at a high rate of speed approached the Waymo AV from behind. The passenger car partially entered the number 2 lane as the front right corner of the passenger car made contact with the rear left corner of the Waymo AV. The passenger car then made contact with the center median and came to a stop. The Waymo AV was transitioned into manual mode, and the test driver stopped the Waymo AV to the right-hand shoulder. 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. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, a vehicle involved was towed away, and an airbag deployed. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-6579 v2 | ADS | Waymo LLC | 2023-11 22:43 | San Francisco, CA | 2021 Jaguar I-Pace | ADS | Passenger Car | Serious | 18 | Intersection | Other than correcting the Mileage to 64,204, adding law enforcement investigation details, adding the ADS Software Version, and adding the Waymo AVs Pre-Crash Speed, the content of this report is unchanged from the initi…Other than correcting the Mileage to 64,204, adding law enforcement investigation details, adding the ADS Software Version, and adding the Waymo AVs Pre-Crash Speed, the content of this report is unchanged from the initial report submitted on November 4, 2023 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On November [XXX], 2023 at 10:43 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound in the left lane on [XXX] and stopped at a red light at the intersection with [XXX] alongside a passenger vehicle in the right lane. After the light turned green, both the Waymo AV and the adjacent passenger car proceeded into the intersection. While in the intersection, a passenger car traveling west on [XXX] ran the red light and the front left corner and left side of this vehicle made contact with the front right of the Waymo AV and the front of the adjacent passenger car. After impact, the vehicle that ran the red light struck pedestrians that had been standing on the sidewalk on the northwest corner of the intersection. At the time of the impact, the Waymo AVs Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage and were towed from the scene. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30412-6395 v4 | TMR-0119 | ADS | Cruise LLC | 2023-10 21:29 | San Francisco, CA | 2023 Cruise AV | ADS | Non-Motorist: Pedestrian | Serious | 14 | Intersection | Redacted by NHTSA as confidential business information |
| 540-6400 v4 | ADS | General Motors, LLC | 2023-10 21:29 | San Francisco, CA | 2023 Cruise AV | ADS | Non-Motorist: Pedestrian | Serious | 14 | Intersection | On December 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) ma…On December 15, 2023, GM Cruise Holdings LLC ("Cruise") filed an update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6395-4). | |
| 30412-6144 v3 | ADS | Cruise LLC | 2023-08 22:22 | San Francisco, CA | 2023 Cruise AV | ADS | First Responder Vehicle | Serious | 13 | Intersection | Redacted by NHTSA as confidential business information | |
| 540-6148 v3 | ADS | General Motors, LLC | 2023-08 22:22 | San Francisco, CA | 2023 Cruise AV | ADS | First Responder Vehicle | Serious | 13 | Intersection | On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) m…On September 14, 2023, GM Cruise Holdings LLC ("Cruise") filed an update Incident Report (the "Report") under the Second Amended Standing General Order 2021-01, dated April 5, 2023 (the "Order") General Motors LLC (GM) manufactured the Cruise-operated motor vehicle involved in the incident summarized in the Incident Report. Because GM is also a Reporting Entity under the Order, GM is submitting a duplicate of the redacted public copy of the Report. GM has selected "Unknown" in the "ADS version" and "ODD time" fields solely to avoid a second submission of nonpublic Cruise CBI GM is in possession of Cruise's responses to these fields, and incorporates Cruise's responses into this submission by reference. GM's submission is based on facts supplied to GM by Cruise. GM has not investigated the alleged incident and currently believes, based on a reasonable inquiry, that it has no independent knowledge of the facts in the Report. (Reference file: 30412-6144-3). | |
| 30412-2588 v2 | ADS | Cruise LLC | 2022-03 13:24 | San Francisco, CA | 2022 Cruise AV | ADS | Non-Motorist: Cyclist | Serious | 4 | Street | Redacted by NHTSA as confidential business information | |
| 540-2590 v2 | ADS | General Motors, LLC | 2022-03 13:24 | San Francisco, CA | 2022 Cruise AV | ADS | Non-Motorist: Cyclist | Serious | 4 | Street | On April [XXX], 2022, 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 Cruis…On April [XXX], 2022, 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-2588-2). |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.