The MachineRecord
NHTSA Standing General Order 2021-01

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
Clear filters

6 reports, showing 1 to 6.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
30412-7840 v2ADSCruise LLC2024-06 04:55Phoenix, AZ2023 Cruise AVADSPassenger CarModerate0Street
Cruise submits this updated report to add that the driver of the Chrysler PT Cruiser later claimed injuries related to the event. There are no other changes to Cruise's previous submission. On June [XXX], 2024 at 4:55AM …Cruise submits this updated report to add that the driver of the Chrysler PT Cruiser later claimed injuries related to the event. There are no other changes to Cruise's previous submission. On June [XXX], 2024 at 4:55AM MT, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode with three Cruise AV test operators onboard was traveling southbound on [XXX] in [XXX], Arizona when it approached a red light at the intersection with [XXX]. As the AV was stopping at the red light, a Chrysler PT Cruiser approached the AV from the rear but failed to stop and struck the rear of the nearly-stopped AV, causing severe damage to the Cruise AV and damage to the Chrysler PT Cruiser. The impact of the collision pushed the AV into the center of the intersection before the pair came to a stop. Police and Emergency Medical Services (EMS) were called and came to the scene. The three Cruise AV test operators reported minor injuries. No parties were transported to the hospital from the scene of the collision, but the three AVTOs were later examined at a health care facility. The Cruise AV was towed from the scene.
30412-6439 v2ADSCruise LLC2023-09 00:05Tempe, AZ2022 Cruise AVADSAnimalNo Injuries Reported15StreetRedacted by NHTSA as confidential business information
30412-5989ADSCruise LLC2023-07 20:38Tempe, AZ2022 Cruise AVADSPassenger CarMinor27StreetRedacted by NHTSA as confidential business information
30412-5661ADSCruise LLC2023-06 04:31Chandler, AZ2020 Cruise AVADSHeavy TruckNo Injuries Reported14IntersectionRedacted by NHTSA as confidential business information
30412-5462ADSCruise LLC2023-04 14:58Mesa, AZ2020 Cruise AVADSOther, see NarrativeNo Injuries Reported34StreetRedacted by NHTSA as confidential business information
30412-4996 v2ADSCruise LLC2023-03 13:01Tempe, AZ2023 Cruise AVADSPassenger CarMinor6IntersectionRedacted 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.