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
3 reports, showing 1 to 3.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30412-8748 | ADS | Cruise LLC | 2024-10 11:49 | Houston, TX | 2023 Cruise AV | ADS | Other Fixed Object | No Injuries Reported | 13 | Intersection | On October [XXX], 2024, at 11:48AM CDT, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode in Houston, Texas was traveling west on [XXX] when it entered into the left turn lane to make a left turn…On October [XXX], 2024, at 11:48AM CDT, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode in Houston, Texas was traveling west on [XXX] when it entered into the left turn lane to make a left turn onto [XXX]. As the AV began to make the left turn, it slowed in the intersection in response to an oncoming SUV on [XXX], and the Cruise safety driver disengaged the ADS and took manual control of the AV to accelerate and complete the left turn. As the safety driver completed the turn, the AV struck the right-hand curb on [XXX] at [XXX] CDT. The impact resulted in a flat tire on the front passenger side of the AV. The AV was towed from the scene. No other parties were involved, and no injuries were reported. | |
| 30412-6179 | ADS | Cruise LLC | 2023-08 00:36 | Austin, TX | 2024 Cruise Origin | ADS | Other Fixed Object | No Injuries Reported | 6 | Street | Redacted by NHTSA as confidential business information | |
| 30412-5422 v3 | ADS | Cruise LLC | 2023-05 02:44 | San Francisco, CA | 2022 Cruise AV | ADS | Other Fixed Object | Minor | 7 | 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. 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.