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
10 reports, showing 1 to 10.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-16277 | ADS | Waymo LLC | 2026-08 15:49 | Philadelphia, PA | 2026 ZEEKR RT | Verified Engaged | Bus | Property Damage. No Injured Reported | 15 | Intersection | On August [XXX], 2026 at 3:49 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the left…On August [XXX], 2026 at 3:49 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving a bus on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the leftmost lane on [XXX] and proceeding straight at a green light at the intersection with [XXX]. As the Waymo AV began to enter the intersection, a bus traveling southbound in the leftmost lane on [XXX] proceeded to enter the intersection against a red light, entering the Waymo AV's lane of travel. The Waymo AV braked and began to maneuver to the right as the bus continued forward, and the right side of the bus made contact with the front 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away and airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-16646 | ADS | Waymo LLC | 2026-08 17:10 | Philadelphia, PA | 2025 ZEEKR RT | Verified Not Engaged | Passenger Car | Property Damage. No Injured Reported | 10 | Street | On August [XXX], 2026 at 5:10 PM EDT, a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing nor…On August [XXX], 2026 at 5:10 PM EDT, a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing northeast in autonomous mode in the third lane from the left on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, the test driver transitioned the Waymo AV into manual mode then proceeded forward, and the front of the Waymo AV made contact with the rear of a passenger car stopped in the queue of traffic in front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged in autonomous mode, 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. | |
| 30270-16115 | ADS | Waymo LLC | 2026-07 13:55 | Philadelphia, PA | 2025 ZEEKR RT | Verified Not Engaged | SUV | Property Damage. No Injured Reported | 5 | Street | On July [XXX], 2026 at 1:55 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling eastbound in autonom…On July [XXX], 2026 at 1:55 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling eastbound in autonomous mode on [XXX] and proceeding straight through the T-intersection with [XXX] when it began slowing to yield to a queue of traffic ahead. While the Waymo AV was slowing, and the test driver transitioned the Waymo AV into manual mode and proceeded forward, and the front of the Waymo AV made contact with the rear of an SUV stopped in the queue of traffic in front 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. 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-14702 | ADS | Waymo LLC | 2026-04 23:22 | Philadelphia, PA | 2025 ZEEKR RT | Verified Engaged | SUV | Minor W/O Hospitalization | 5 | Street | On April [XXX], 2026 at 11:22 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving an SUV on[XXX]. The Waymo AV was stopped facing south in the second from …On April [XXX], 2026 at 11:22 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving an SUV on[XXX]. The Waymo AV was stopped facing south in the second from the right lane on [XXX] for a red light at the intersection with [XXX]. After the light turned green, the Waymo AV began to proceed forward, and an SUV traveling in the adjacent left lane passed the Waymo AV to the left, and the front right side of the SUV made contact with the left side 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). The Waymo AV continued to proceed forward, and the test driver of the Waymo AV transitioned the Waymo AV to manual mode. The test driver continued to drive southbound on [XXX], and began to slow while approaching the intersection with [XXX] with the SUV proceeding southbound in the leftmost lane, adjacent to the Waymo AV. The test driver then proceeded forward through the intersection, and the SUV maneuvered to the right, crossing the dashed white lane lines into the Waymo AV's lane of travel. The test driver then maneuvered the Waymo AV to the right, and the front right side of the Waymo AV made contact with a pickup truck parked facing south on the west curb of [XXX]. At the time of the second impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. All involved vehicles sustained damage. 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-14046 | ADS | Waymo LLC | 2026-02 20:05 | Philadelphia, PA | 2025 ZEEKR RT | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 0 | Street | On February [XXX], 2026 at 8:05 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped facing south…On February [XXX], 2026 at 8:05 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Philadelphia, Pennsylvania was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped facing south on [XXX], partially in-lane and partially at the east curb, when a heavy truck traveling southbound on [XXX] proceeded to pass the Waymo AV on the right. As the heavy truck passed the Waymo AV, the left side of the heavy truck trailer made contact with the 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, and a test driver was present in the driver's seating position. 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. | |
| 30410-13069 | ADS | Motional | 2025-11 14:30 | Pittsburgh, PA | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 12 | Intersection | Redacted by NHTSA as confidential business information | |
| 34952-11803 | ADS | Stack AV | 2025-09 7:47 | Mount Pleasant, PA | 2025 PETERBILT 579 | Verified Engaged | Heavy Truck | No Injured Reported | 28 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 30290-3347 | ADS | Argo AI | 2022-06 13:30 | Pittsburgh, PA | 2020 Ford Escape | ADS | SUV | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 502-3416 | ADS | Ford Motor Company | 2022-06 13:30 | Pittsburgh, PA | 2020 Ford Escape | ADS | SUV | No Injuries Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | |
| 10003-2932 | ADS | Navistar, Inc. | 2021-11 19:57 | Maxatawny Township, PA | 2022 International LT | Unknown, see Narrative | Other Fixed Object | Unknown | Street | This vehicle is equipped with Lane Keep Assist feature. The posted speed limit the subject vehicle was operating at time of incident is 25 MPH and the Lane Keep Assist Feature cannot be activated at speeds below 37 MPH. …This vehicle is equipped with Lane Keep Assist feature. The posted speed limit the subject vehicle was operating at time of incident is 25 MPH and the Lane Keep Assist Feature cannot be activated at speeds below 37 MPH. This crash occurred as unit 1 was going North on [XXX] in Maxatawny Township, Berks County. Unit 1 then went off the right side of the roadway and struck a house. Unit 1 was towed from the scene. Operator 1 and homeowner were transported to nearby local hospital to be treated for minor injuries. |
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.