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
4 reports, showing 1 to 4.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30412-9204 v2 | ADS | Cruise LLC | 2024-11 19:23 | Houston, TX | 2023 Cruise AV | ADS | Non-Motorist: Cyclist | No Injuries Reported | 4 | Street | Cruise submits this updated report to confirm there was no physical contact between the AV and the cyclist and to provide additional details about this incident. On November [XXX], 2024 at 7:23PM CST, a Cruise autonomous…Cruise submits this updated report to confirm there was no physical contact between the AV and the cyclist and to provide additional details about this incident. On November [XXX], 2024 at 7:23PM CST, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode in Houston, Texas was traveling west on [XXX] when it decelerated as it approached a speed bump. As the AV began to slowly traverse the speed bump, it maneuvered slightly left to provide room for a cyclist approaching from behind the AV on the right-hand side. As the cyclist approached quickly from behind the AV, they moved from the right side of the road to the left side and attempted to maneuver around the AV, between the AV and a parked vehicle. The cyclist then lost control of their bike while maneuvering the speed bump and fell to the ground in front of and to the left of the AV. The AV came to a complete stop and the Cruise safety driver took manual control of the AV, remaining stationary. The cyclist proceeded to get to their feet and spoke with the safety driver, but did not report any injuries when asked. There was no indication of property damage to the AV. | |
| 30412-9268 | ADS | Cruise LLC | 2024-11 09:10 | Houston, TX | 2023 Cruise AV | ADS | Heavy Truck | Moderate | 0 | Intersection | On November [XXX], 2024, at 9:10am CST, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode in Houston, Texas was traveling westbound on [XXX] between [XXX] and [XXX]. The AV came to a complete sto…On November [XXX], 2024, at 9:10am CST, a Cruise autonomous vehicle ("AV") operating in supervised autonomous mode in Houston, Texas was traveling westbound on [XXX] between [XXX] and [XXX]. The AV came to a complete stop behind a semi-trailer truck stopped at a traffic signal at the intersection with [XXX]. The semi-trailer truck reversed into the AV, making contact with the front of the AV twice. Prior to contact, the AV operator honked the horn to attempt to alert the truck driver After contact, the AV operator got out of the car to attempt to flag down the truck driver. However, the driver of the semi-trailer truck left the scene without exchanging information. The impact resulted in damage to the front end of the AV. The AV was driven away from the scene, and a police report was filed to document the incident. The AV operator later reported moderate injuries. | |
| 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-7840 v2 | ADS | Cruise LLC | 2024-06 04:55 | Phoenix, AZ | 2023 Cruise AV | ADS | Passenger Car | Moderate | 0 | Street | 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. |
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.