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
13 reports, showing 1 to 13.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-15667 | ADS | Waymo LLC | 2026-07 10:51 | Washington, DC | 2024 JAGUAR I-PACE | Verified Not Engaged | SUV | Minor W/ Hospitalization | 5 | Street | On July [XXX], 2026 at 10:51 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] NW near [XXX] NW. The Waymo AV was traveling northwestbound in the r…On July [XXX], 2026 at 10:51 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] NW near [XXX] NW. The Waymo AV was traveling northwestbound in the right lane on [XXX] NW in autonomous mode when it began to slow for a van, ahead in lane, turning right into a shopping center. While the Waymo AV was slowing, the test driver transitioned the Waymo AV into manual mode and continued to slow, and an SUV traveling northwestbound on [XXX] NW, partially in the right lane and partially in the left lane, maneuvered to the left as it approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The test driver of the Waymo AV alleged minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-14625 | ADS | Waymo LLC | 2026-03 19:27 | Washington, DC | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Minor W/O Hospitalization | 4 | Street | On March [XXX], 2026 at 7:27 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in the rightmost lan…On March [XXX], 2026 at 7:27 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in the rightmost lane on [XXX] when it began to slow for an emergency vehicle siren from an ambulance traveling northbound. While the Waymo AV was slowing, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. 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. | |
| 30490-14064 | ADS | Beep, Inc. | 2026-01 10:27 | Washington, DC | 2025 KARSAN Jest Electric, Jest EV, e-JEST | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 13 | Street | On January [XXX], 2026, a Beep-operated Karsan EJEST (BEEP-EJEST-0001) equipped with an automated driving system (ADS) develop by ADASTEC Corporation (ADASTEC) was involved in a collision with a third-party vehicle in Wa…On January [XXX], 2026, a Beep-operated Karsan EJEST (BEEP-EJEST-0001) equipped with an automated driving system (ADS) develop by ADASTEC Corporation (ADASTEC) was involved in a collision with a third-party vehicle in Washington, D.C. While traveling in autonomous mode westbound on [XXX] in the left-hand lane, the vehicle encountered a double-parked vehicle partially intruded into BEEP-EJEST-0001's lane of travel. BEEP-EJEST-0001 began to slow from its planned speed, and as decelerated, a human-driven Tesla Model Y (VEHICLE2) traveling parallel to BEEP-EJEST-0001 in the right-hand lane attempted to pull behind BEEP-EJEST-0001 to pass the double-parked vehicle in its lane of travel. VEHICLE2 encroached upon BEEP-EJEST-0001's predefined safety area of 5 cm, triggering an automated deceleration by BEEP-EJEST-0001 of approximately –2 m/s^2. VEHICLE2 began to further encroach upon BEEP-EJEST-0001's lane, triggering a higher-rate automated braking response consistent with system design. VEHICLE2 subsequently made contact with the rear of BEEP-EJEST-0001. Beep confirmed that the operator performed his duties as trained and expected by Beep's established policies and procedures. The vehicle operator was not referred for a post-accident drug and alcohol testing after the incident as the DOT criteria for such testing were not met. Available data indicated that VEHICLE2 followed BEEP-EJEST-0001 at a distance insufficient to respond to rapid deceleration and initiated a lane transition across a solid lane line immediately prior to contact. BEEP-EJEST-0001 reacted as expected to the environment it encountered, slowing down to appropriate speeds and operated within its defined ODD at the time of the incident. There were (7) seven passengers on board. No injuries were reported. Both vehicles sustained minor damage, no airbags were deployed, and both vehicles were driven from the scene. No law enforcement attended to the scene. Following the incident, the vehicle was inspected for damages to the vehicle or sensors. It has been determined that any damage incurred was minor and did not impact the operational integrity of the vehicle. | |
| 30270-13379 | ADS | Waymo LLC | 2025-12 18:25 | Washington, DC | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 1 | Street | On December [XXX], 2025 at 6:25 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] and [XXX] approaching the [XXX] overpass. The Waymo AV was traveling…On December [XXX], 2025 at 6:25 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] and [XXX] approaching the [XXX] overpass. The Waymo AV was traveling southbound on [XXX] and [XXX] in the left lane when it began to slow for traffic ahead. While the Waymo AV was slowing, an SUV that was traveling southbound behind the Waymo AV continued to proceed forward and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. 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. | |
| 30270-13252 | ADS | Waymo LLC | 2025-11 18:55 | Washington, DC | 2024 JAGUAR I-PACE | Verified Not Engaged | Other Fixed Object | Property Damage. No Injured Reported | 13 | Intersection | On November [XXX], 2025 at 6:55 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving a curb on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] in autonom…On November [XXX], 2025 at 6:55 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving a curb on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] in autonomous mode when it began to turn right at the intersection with [XXX]. As the Waymo AV proceeded to turn right, it approached the right hand curb. The test driver transitioned the Waymo AV to manual mode and the front right tire of the Waymo AV made contact with the curb. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-13026 | ADS | Waymo LLC | 2025-10 13:28 | Washington, DC | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 2 | Street | On October [XXX], 2025 at 1:28 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing south in the left lane …On October [XXX], 2025 at 1:28 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing south in the left lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the light turned green and traffic ahead advanced, the Waymo AV began to proceed forward at a low rate of speed and an SUV that was initially stopped directly behind the Waymo AV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present in the driver's seating position. Both vehicles sustained damage. 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. | |
| 30270-10971 | ADS | Waymo LLC | 2025-05 15:30 | Washington, DC | 2024 Jaguar I-Pace | ADS | Bus | No Injuries Reported | 0 | Street | On May [XXX], 2025 at 3:30 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, DC was in a collision involving a bus on [XXX] near [XXX] NW. The Waymo AV was traveling northwest in the right lane on [X…On May [XXX], 2025 at 3:30 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington, DC was in a collision involving a bus on [XXX] near [XXX] NW. The Waymo AV was traveling northwest in the right lane on [XXX], and stopped behind a bus that was parked at the curb directly in front of the Waymo AV. The bus then began to reverse and the test driver of the Waymo AV transitioned the Waymo AV to manual mode, and the rear of the bus made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. 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. | |
| 30290-3119 | ADS | Argo AI | 2022-05 08:11 | WDC, DC | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 502-2973 v2 | ADS | Ford Motor Company | 2022-05 08:11 | WDC, DC | 2020 Ford Escape | ADS | Heavy Truck | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 30290-2471 | ADS | Argo AI | 2022-02 8:51 | Washington DC, DC | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-2525 | ADS | Ford Motor Company | 2022-02 8:51 | Washington DC, DC | 2019 Ford Fusion | ADS | Passenger Car | No Injuries Reported | 0 | Street | Redacted by NHTSA as confidential business information | |
| 30290-15 v2 | ADS | Argo AI | 2021-07 09:26 | Washington DC, DC | 2019 Ford Fusion | ADS | Pickup Truck | Minor | 0 | Street | Redacted by NHTSA as confidential business information | |
| 502-18 v2 | ADS | Ford Motor Company | 2021-07 09:26 | Washington DC, DC | 2019 Ford Fusion | ADS | Pickup Truck | Minor | 0 | Street | 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.