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
2 reports, showing 1 to 2.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30412-6528 v2 | ADS | Cruise LLC | 2023-10 19:32 | San Francisco, CA | 2023 Cruise AV | ADS | Motorcycle | Moderate | 2 | Street | Redacted by NHTSA as confidential business information | |
| 30412-3748 v3 | ADS | Cruise LLC | 2022-09 18:46 | San Francisco, CA | 2022 Cruise AV | ADS | Motorcycle | Minor | 7 | Street | Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound on [XXX] between [XXX] and [XXX]. At the same time, a motorcyclist approaching from the rear began to merge into t…Cruise autonomous vehicle ("Cruise AV"), operating in supervised autonomous mode, was traveling westbound on [XXX] between [XXX] and [XXX]. At the same time, a motorcyclist approaching from the rear began to merge into the Cruise AV's lane behind the Cruise AV. As the motorcycle approached the AV's rear, the AV braked and the motorcycle subsequently made contact with the Cruise AV's rear passenger side bumper, damaging the motorcycle's front fender. The driver of the motorcycle reported minor injuries and police were not called. |
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.