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

1 report, showing 1 to 1.

Report IDCaseProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
30270-13606TMR-0194ADSWaymo LLC2026-01 12:36Santa Monica, CA2024 JAGUAR I-PACEVerified EngagedSUVProperty Damage. No Injured Reported0Parking Lot
On January [XXX], 2026 at 12:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV in a parking lot at [XXX]. The Waymo AV was parked facing northwes…On January [XXX], 2026 at 12:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving an SUV in a parking lot at [XXX]. The Waymo AV was parked facing northwest with its hazard lights activated for a passenger dropoff in a parking lot at [XXX]. While the Waymo AV was parked, an SUV that was parked facing northeast in a parking stall behind and to the right of the Waymo AV reversed, and the rear left side of the SUV made contact with the rear right side of the stationary 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 passenger in the Waymo AV was not belted at the time of the collision as they were preparing to exit the vehicle. 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.

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. The themed reading of the driverless narratives is on the reports page.