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
12 reports, showing 1 to 12.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-16259 | ADS | Waymo LLC | 2026-07 02:26 | Detroit, MI | 2025 ZEEKR RT | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 16 | Street | On July [XXX], 2026 at 2:26 AM EDT a Waymo Autonomous Vehicle (Waymo AV) operating in Detroit, Michigan was in a collision involving a pothole on [XXX] near [XXX]. The Waymo AV was traveling southeast bound on [XXX] nea…On July [XXX], 2026 at 2:26 AM EDT a Waymo Autonomous Vehicle (Waymo AV) operating in Detroit, Michigan was in a collision involving a pothole on [XXX] near [XXX]. The Waymo AV was traveling southeast bound on [XXX] near [XXX]. As the Waymo AV exited the intersection with [XXX], the Waymo AV drove over a pothole and the undercarriage of the Waymo AV made contact with the pavement. 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 became aware of the tow on August [XXX], 2026 after an additional review of available information. 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. | |
| 30413-10762 | ADS | May Mobility | 2025-04 11:28 | Detroit, MI | 2023 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | A large semi-trailer truck is making a left turn from a street on the right into the oncoming lane in Detroit, MI. As the May autonomous shuttle (Ego) is slowing, the Autonomous Vehicle Operator (AVO) intervenes to stop…A large semi-trailer truck is making a left turn from a street on the right into the oncoming lane in Detroit, MI. As the May autonomous shuttle (Ego) is slowing, the Autonomous Vehicle Operator (AVO) intervenes to stop earlier. The manually controlled Ego remains stationary for five seconds. The AVO then manually reverses two meters to create more space for the trailer intruding into the Egos lane, making contact with a rear vehicle at 0.6 m/s. Our team looked at the incident and determined that this event was caused by human error - no autonomy software defects led to this incident. | |
| 30413-10764 | ADS | May Mobility | 2025-04 8:33 | Ann Arbor, MI | 2024 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | A May autonomous shuttle (ego) was stopped at a traffic light in autonomous mode. A vehicle approaching from behind coasted into the ego vehicle. Our system responded with a software Health Drop, which immediately took t…A May autonomous shuttle (ego) was stopped at a traffic light in autonomous mode. A vehicle approaching from behind coasted into the ego vehicle. Our system responded with a software Health Drop, which immediately took the ego out of autonomous mode (for safety). Minor damage was reported to our rear sensor and bumper. | |
| 30413-9949 | ADS | May Mobility | 2025-01 12:34 | Ann Arbor, MI | 2024 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 0 | Street | The May vehicle was involved in a rear-end collision shortly after completing a right-hand turn. As the vehicle proceeded through its turn, it encountered exhaust fumes from vehicles waiting at a stoplight in the adjacen…The May vehicle was involved in a rear-end collision shortly after completing a right-hand turn. As the vehicle proceeded through its turn, it encountered exhaust fumes from vehicles waiting at a stoplight in the adjacent lane. Due to environmental conditions and sensor limitations, the vehicle's lidar system interpreted the exhaust plume as a solid object in its path. In response, the autonomous vehicle first tried to adjust its position. When this maneuver proved insufficient, the system initiated a hard stop response. The vehicle behind, which was following at approximately 7-8 meters, was unable to stop in time and collided with the rear of the autonomous vehicle. The collision occurred at relatively low speeds (the autonomous vehicle had decelerated from approximately 7.6 m/s to 0 m/s), though exact impact speeds of the following vehicle were not recorded. The primary factor that led to this incident is that Lidar does not pierce through exhaust so the exhaust cloud appears to be a large, solid object. Some corrective actions that will be implemented: consider weather implication in future platform sensor selection and continue working on the software to improve a neural network to classify lidar points, which will use temporal information, radar, and camera features to make a decision on whether a lidar point is truly an object. | |
| 753-7780 v2 | ADS | Kia America, Inc. | 2024-04 02:50 | ST. CLAIR TOWNSHIP, MI | 2023 KIA SPORTAGE | ADAS | Passenger Car | Moderate | 55 | Street | **1-Day Incident Report 5/25/2024** Customer contacted Kia Customer Care (KCC) to report an incident involving his 2023MY Kia Sportage. Specifically, the customer called to thank Kia "for saving [REDACTED, MAY CONTAIN CO…**1-Day Incident Report 5/25/2024** Customer contacted Kia Customer Care (KCC) to report an incident involving his 2023MY Kia Sportage. Specifically, the customer called to thank Kia "for saving [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] life." Customer explained he was in a head-on collision when a drunk driver suddenly veered into his lane. Customer reported he suffered "cuts, bumps & bruises" and stated he "believes that [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] lack of injuries is due to the plethora of safety features my Sportage had." KCC subsequently contacted the customer to obtain additional details regarding the incident. Customer stated that he was driving on a two-lane highway around 3AM, with cruise control engaged, when the car he was following veered into a ditch and a drunk driver veered into his lane. Customer did not see the drunk driver until the last second and as a result did not have time react. When asked by KCC, the customer responded that Highway Driving Assist (HDA) was not engaged, but that his Smart Cruise Control and Lane Following Assist were engaged at the time of the incident. The customer reported that the Sportage's airbags deployed, both the customer and driver of the other vehicle (unclear if the drunk driver or the driver of the vehicle that veered into the ditch) were transported to the hospital and that the Sportage was towed. Customer stated he was not asking anything from Kia and that he had called only to share his appreciation. This incident is being reported as precautionary measure since the incident meets the requirements under the SGO. However, based on the description of the incident provided by the customer, the incident was not caused by a failure and/or disengagement of smart cruise control and/or LFA. **10-Day Update 6/3/2024** No additional information to be provided as the 1-Day was reported as a precautionary measure and submitting this 10-Day Update per the reporting requirements under the SGO. | |
| 30413-7307 | ADS | May Mobility | 2024-02 11:40 | Ann Arbor, MI | 2022 Toyota Sienna | ADS | SUV | No Injuries Reported | 29 | Street | The May vehicle was in autonomous mode on experimental test software (not deployed to the Commercial fleet), in light snow conditions. A vehicle behind the AV was traveling approximately the same speed as the May shuttl…The May vehicle was in autonomous mode on experimental test software (not deployed to the Commercial fleet), in light snow conditions. A vehicle behind the AV was traveling approximately the same speed as the May shuttle. The May AV began to slow for an object ahead. Due to weather conditions, the AV misclassified a speed limit sign as a pedestrian, which intersected with the predicted trajectory of the AV. This caused the May AV to apply additional braking to avoid the projected collision with the misclassified object. The following vehicle did not react promptly when the May AV started to slow down, resulting in the following vehicle braking too late to avoid collision and impacting the May AV from behind. The following vehicle then pulled around the May vehicle and drove away. Resimulation of this event with an upcoming software version shows that the May AV would not misidentify the non-exist object so would not have decelerated unnecessarily. This improved software is set to be deployed to the full commercial fleet soon. In addition, per May policy, the commercial fleet would not operate in weather conditions like those present in this incident. | |
| 30413-5396 | ADS | May Mobility | 2023-04 16:16 | Ann Arbor, MI | 2020 Lexus RX450h | ADS | Passenger Car | No Injuries Reported | 18 | Street | On Friday April [XXX] at 16:16 local time, the May shuttle was driving Westbound on [XXX] in Ann Arbor, MI in autonomous mode and was followed by another vehicle. The following vehicle was traveling approximately twice a…On Friday April [XXX] at 16:16 local time, the May shuttle was driving Westbound on [XXX] in Ann Arbor, MI in autonomous mode and was followed by another vehicle. The following vehicle was traveling approximately twice as fast as the May shuttle and catching up to the May shuttle from behind. The May shuttle began to slow for traffic ahead, which was stopping for a red light, but the following vehicle did not decelerate. While slowing, the May shuttle identified a bollard on the side of the road as a likely pedestrian and added a safety buffer which intersected with the predicted trajectory of the shuttle. This caused the shuttle to increase deceleration to avoid the projected collision with the buffer. The following vehicle started braking late and impacted the May shuttle from behind with a relative velocity of 6.2 m/s. Re-simulation of this event with a future software version shows that the May shuttle would have decelerated less abruptly. | |
| 30413-4352 | ADS | May Mobility | 2022-12 18:38 | Ann Arbor, MI | 2020 Lexus RX450h | ADS | SUV | No Injuries Reported | 0 | Street | Operator turned onto [XXX] headed westbound approaching the stop sign at the intersection with [XXX]. In autonomy, the subject vehicle came to a stop. An SUV behind the subject vehicle then rear-ended the subject vehicle…Operator turned onto [XXX] headed westbound approaching the stop sign at the intersection with [XXX]. In autonomy, the subject vehicle came to a stop. An SUV behind the subject vehicle then rear-ended the subject vehicle. No injuries were reported by the operator or the driver of the other vehicle and there was no damage to the SUV and a small crack in the bumper for the subject vehicle. | |
| 1306-4389 v2 | ADS | Toyota Motor Engineering & Manufacturing | 2022-11 15:43 | Ann Arbor, MI | 2020 Lexus RX450H | Unknown, see Narrative | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | This report is being submitted because May Mobility notified Toyota on Dec. 9, 2022 of 1-Day Report submission 30413-4170-1,related to an incident that occurred on Nov. [XXX], 2022. Toyota has no additional information o…This report is being submitted because May Mobility notified Toyota on Dec. 9, 2022 of 1-Day Report submission 30413-4170-1,related to an incident that occurred on Nov. [XXX], 2022. Toyota has no additional information on this incident beyond what was submitted in the aforementioned 1-Day Report. Please refer to the report from May Mobility for details. This report is a 10 Day update. The original report ID is 1306-4389-1. | |
| 30413-4170 | ADS | May Mobility | 2022-11 15:43 | Ann Arbor, MI | 2020 Lexus RX450H | Unknown, see Narrative | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | Operator was approaching stop sign at the intersection of [XXX] westbound and [XXX] northbound, which is a planned disengagement (this unprotected turn is outside of our ODD). If left in autonomy, the vehicle would have …Operator was approaching stop sign at the intersection of [XXX] westbound and [XXX] northbound, which is a planned disengagement (this unprotected turn is outside of our ODD). If left in autonomy, the vehicle would have come to a full stop before the stop line and remained stopped until the operator took over. 6 seconds prior to incident, operator took the vehicle over manually before it could have stopped in autonomy. Operator moved the vehicle manually passed the stop line, colliding with a bicyclist's back tire. No injuries reported from the bicyclist or the operator and no damage to the vehicle or bicycle. | |
| 273-2632 v2 | ADS | Chrysler (FCA US, LLC) | 2022-04 03:30 | Saint Clair, MI | 2022 Jeep Grand Cherokee | ADAS | Other Fixed Object | No Injuries Reported | 50 | Unknown | Redacted by NHTSA as confidential business information | |
| 30413-1207 | ADS | May Mobility | 2021-08 11:30 | Ann Arbor, MI | 2020 Lexus RX450H | ADS | Other, see Narrative | No Injuries Reported | 22 | Street | Vehicle was moving forward and veered slightly to the left, making contact with the curb, resulting in a blown tire. Curb strike occurred during testing. There was human error involved in defining the desired vehicle pos…Vehicle was moving forward and veered slightly to the left, making contact with the curb, resulting in a blown tire. Curb strike occurred during testing. There was human error involved in defining the desired vehicle pose in the lane, which led to a curb strike. We have since resolved this by fixing the desired pose. |
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.