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
8612 reports, showing 1501 to 1600.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30413-15464 | ADS | May Mobility | 2026-05 16:38 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | Other, see Narrative | No Injured Reported | 32 | Street | On May [XXX], 2026 at 4:38 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX]. The May Mobility AV was traveling Eastbound on [XX…On May [XXX], 2026 at 4:38 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX]. The May Mobility AV was traveling Eastbound on [XXX]. As the May Mobility AV passes [XXX] a loop of an unsecured, low-hanging utility cable that was dangling above the right lane of travel struck the windshield and roof of the May Mobility AV. At the time of impact, the May Mobility AV was in autonomous mode, traveling at 32 MPH. The May Mobility AV sustained damage on the top, front, and right side of the vehicle that is estimated to be more than $1,000. Damage to the utility cable beyond the original state of disrepair is unknown. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. |
| 30571-15197 | Level 2 | NVIDIA CORP | 2026-05 14:00 | Humble, TX | 2026 MERCEDES-BENZ CLA-Class | Verified Engaged | Passenger Car | No Injured Reported | 35 | Street | The Mercedes-Benz vehicle was traveling eastbound on [XXX] with the Level 2 ADAS system engaged less than one second prior to contact when a black Honda Civic entered the roadway from [XXX], an adjacent street to the rig…The Mercedes-Benz vehicle was traveling eastbound on [XXX] with the Level 2 ADAS system engaged less than one second prior to contact when a black Honda Civic entered the roadway from [XXX], an adjacent street to the right, and crossed into the path of the Mercedes-Benz vehicle. The operator of the Mercedes-Benz was unable to brake or maneuver sufficiently to avoid the collision. Contact occurred between the front passenger-side area of the Mercedes-Benz vehicle and the Honda Civic. The airbags in the Honda Civic deployed as a result of the collision. No injuries were reported. |
| 30571-15807 | Level 2 | NVIDIA CORP | 2026-05 14:00 | Humble, TX | 2026 MERCEDES-BENZ CLA-Class | Verified Engaged | Passenger Car | No Injured Reported | 35 | Street | The Mercedes-Benz vehicle was traveling eastbound on [XXX] with the Level 2 ADAS system engaged less than one second prior to contact when a black Honda Civic entered the roadway from [XXX], an adjacent street to the rig…The Mercedes-Benz vehicle was traveling eastbound on [XXX] with the Level 2 ADAS system engaged less than one second prior to contact when a black Honda Civic entered the roadway from [XXX], an adjacent street to the right, and crossed into the path of the Mercedes-Benz vehicle. The operator of the Mercedes-Benz was unable to brake or maneuver sufficiently to avoid the collision. Contact occurred between the front passenger-side area of the Mercedes-Benz vehicle and the Honda Civic. The airbags in the Honda Civic deployed as a result of the collision. No injuries were reported. |
| 30571-15825 | Level 2 | NVIDIA CORP | 2026-05 14:00 | Humble, TX | 2026 MERCEDES-BENZ CLA-Class | Verified Engaged | Passenger Car | No Injured Reported | 35 | Street | The Mercedes-Benz vehicle was traveling eastbound on [XXX] with the Level 2 ADAS system engaged less than one second prior to contact when a black Honda Civic entered the roadway from [XXX], an adjacent street to the rig…The Mercedes-Benz vehicle was traveling eastbound on [XXX] with the Level 2 ADAS system engaged less than one second prior to contact when a black Honda Civic entered the roadway from [XXX], an adjacent street to the right, and crossed into the path of the Mercedes-Benz vehicle. The operator of the Mercedes-Benz was unable to brake or maneuver sufficiently to avoid the collision. Contact occurred between the front passenger-side area of the Mercedes-Benz vehicle and the Honda Civic. The airbags in the Honda Civic deployed as a result of the collision. No injuries were reported. |
| 30610-15018 | ADS | Zoox, Inc. | 2026-05 23:04 | San Francisco, CA | 2026 ZOOX Zoox | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 8 | Intersection | An unoccupied Zoox autonomous vehicle was traveling south on [XXX] on a green light at [XXX] in San Francisco when a pickup truck (Vehicle 2) executed an abrupt left turn from northbound [XXX] and accelerated into the Zo…An unoccupied Zoox autonomous vehicle was traveling south on [XXX] on a green light at [XXX] in San Francisco when a pickup truck (Vehicle 2) executed an abrupt left turn from northbound [XXX] and accelerated into the Zoox vehicle's right-of-way. The Zoox vehicle braked hard, but contact was unavoidable. Vehicle 2's front bumper struck the Zoox vehicle's left side door and body panels. After reversing, Vehicle 2 cleared the intersection, pulled over temporarily, and then left without exchanging information. Shortly afterward, the Zoox vehicle cleared the intersection, pulled over, and was towed for inspection. It was found to have sustained moderate damage. No injuries were reported, and police were not called. |
| 30610-15295 | ADS | Zoox, Inc. | 2026-05 14:26 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | Passenger Car | Unknown | 3 | Street | An unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling north on [XXX], having just completed a left turn from [XXX] in Las Vegas, when it encountered debris in its path. The Zoox vehicle attempted to steer right…An unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling north on [XXX], having just completed a left turn from [XXX] in Las Vegas, when it encountered debris in its path. The Zoox vehicle attempted to steer right, then executed hard braking to avoid the debris, at which point it was rear-ended by a passenger car (Vehicle 2) traveling directly behind it. Both vehicles came to a stop following the impact and were subsequently towed due to the damage sustained. Vehicle 2 suffered front-end damage and its driver-side frontal airbags deployed, while the Zoox vehicle sustained moderate damage to its rear. Law enforcement was notified of the event, but did not respond to the scene. Following the impact, Zoox staff inquired if emergency medical services should be called; the driver replied that the police had already been contacted. The driver of Vehicle 2 informed Zoox staff at the scene that they were "shaken" and "pretty bruised". |
| 30610-15480 | ADS | Zoox, Inc. | 2026-05 13:38 | Miami, FL | 2019 TOYOTA Highlander | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 1 | Street | A Zoox vehicle operating in autonomous mode was gradually slowing for oncoming traffic while preparing to turn left onto westbound [XXX] from [XXX] in Miami, when a pickup truck (Vehicle 2) rear-ended it while executing …A Zoox vehicle operating in autonomous mode was gradually slowing for oncoming traffic while preparing to turn left onto westbound [XXX] from [XXX] in Miami, when a pickup truck (Vehicle 2) rear-ended it while executing a right turn from [XXX] onto [XXX]. The Zoox vehicle sustained moderate damage, and no injuries were reported. Law enforcement was notified but did not arrive at the scene. |
| 30610-15481 | ADS | Zoox, Inc. | 2026-05 19:01 | San Francisco, CA | 2019 TOYOTA Highlander | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 10 | Street | A Zoox vehicle (Vehicle 1) operating in manual mode was traveling south on [XXX] past [XXX] in San Francisco when it made contact was made with the left side quarter panel and rear bumper of a parked passenger car (Vehic…A Zoox vehicle (Vehicle 1) operating in manual mode was traveling south on [XXX] past [XXX] in San Francisco when it made contact was made with the left side quarter panel and rear bumper of a parked passenger car (Vehicle 2). The Zoox vehicle's front passenger-side fender sustained damage. No injuries were reported, and police were not notified. |
| 31101-14898 | ADS | Avride Inc. | 2026-05 08:46 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 21 | Street | On May [XXX], 2026 at 8:46 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling northbound on [XXX] in autonomous mode as it approached a ho…On May [XXX], 2026 at 8:46 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling northbound on [XXX] in autonomous mode as it approached a hotel parking lot exit located on the left side of the roadway. As the AVRIDE AV proceeded straight ahead in the left lane, a pickup truck exiting the parking lot began making a left turn onto [XXX] without stopping as required before entering the roadway. This maneuver resulted in the right front of the pickup truck making contact with the left front of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-14974 | ADS | Avride Inc. | 2026-05 17:51 | Dallas, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 17 | Street | On May [XXX], 2026 at 5:51 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling westbound on [XXX] in autonomous mode in the right lane. [XX…On May [XXX], 2026 at 5:51 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling westbound on [XXX] in autonomous mode in the right lane. [XXX] consists of three lanes in the direction of travel. As the AVRIDE AV proceeded straight ahead, a passenger car traveling in the far left lane attempted to move across two lanes simultaneously into the far right lane, cutting off the AVRIDE AV. This maneuver resulted in the front right of the passenger car making contact with the left front of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-15093 | ADS | Avride Inc. | 2026-05 14:10 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other Fixed Object | No Injured Reported | 10 | Intersection | On May [XXX], 2026 at 2:10 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling northwestbound in autonomous mode on [XXX] when it approached…On May [XXX], 2026 at 2:10 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling northwestbound in autonomous mode on [XXX] when it approached a red light at a railroad crossing. After stopping at the red light and waiting for the railroad crossing gate to raise, the AVRIDE AV began to drive forward. As the AVRIDE AV drove forward, the railroad crossing gate began to lower again. As the railroad crossing gate lowered, the AVRIDE AV continued to drive forward. This maneuver resulted in the top of the AVRIDE AV making contact with the railroad crossing gate. Neither the AVRIDE AV nor railroad crossing gate sustained damage. No injuries were reported. |
| 31101-15099 | ADS | Avride Inc. | 2026-05 15:42 | Dallas, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 7 | Street | On May [XXX], 2026 at 3:42 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was adjacent to a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in the center lane in autonomous mode on…On May [XXX], 2026 at 3:42 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was adjacent to a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in the center lane in autonomous mode on [XXX] when it stopped at a red traffic signal at the intersection of [XXX] and [XXX]. The AVRIDE AV was being followed by a passenger car. When the traffic signal turned green, the AVRIDE AV proceeded into the intersection and activated its left turn signal to initiate a lane change. The trailing passenger car also moved into the left lane and attempted to overtake the AVRIDE AV while the AVRIDE AV was moving left. Upon detecting the presence of the passenger car, the AVRIDE AV applied its brakes to avoid a collision. The passenger car also braked. A box truck traveling behind the passenger car was unable to stop in time and struck the rear of the passenger car. The passenger car and the box truck sustained damage. No injuries were reported. |
| 31101-15100 | ADS | Avride Inc. | 2026-05 12:43 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On May [XXX], 2026 at 12:43 PM, an AVRIDE autonomous vehicle was involved in a collision in Dallas, Texas, on [XXX] near [XXX]. The AVRIDE vehicle was traveling southwest in autonomous mode when it began merging from the…On May [XXX], 2026 at 12:43 PM, an AVRIDE autonomous vehicle was involved in a collision in Dallas, Texas, on [XXX] near [XXX]. The AVRIDE vehicle was traveling southwest in autonomous mode when it began merging from the right lane into the middle lane. At the same time, a passenger car in the left lane also began entering the middle lane without signaling. To avoid a collision, the AVRIDE vehicle stopped. The vehicles behind it, including another AVRIDE autonomous vehicle and two passenger cars, also stopped. During the stop, one passenger car made contact with the rear of the second AVRIDE vehicle. The passenger car that entered the middle lane left the scene. The second AVRIDE vehicle was damaged. No other vehicles were damaged, and no injuries were reported. |
| 31101-15148 | ADS | Avride Inc. | 2026-05 21:05 | Austin, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 11 | Intersection | On May [XXX], 2026 at 9:05 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Austin, TX at the intersection of East [XXX] and South [XXX]. The AVRIDE AV was traveling westbound in autonomous mode on…On May [XXX], 2026 at 9:05 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Austin, TX at the intersection of East [XXX] and South [XXX]. The AVRIDE AV was traveling westbound in autonomous mode on [XXX] as it approached a traffic light at the intersection with South [XXX]. The traffic light showed green as the AVRIDE AV approached the intersection and began to proceed straight through the green traffic light. As the AVRIDE AV began to enter the intersection, an SUV traveling southbound on [XXX] also entered the intersection from the right of the AVRIDE AV. While entering the intersection, the SUV went against traffic rules and drove through a red light. This maneuver resulted in the left side of the SUV making contact with the front of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-15189 | ADS | Avride Inc. | 2026-05 14:43 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 26 | Intersection | On May [XXX], 2026 at 2:43 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northeastbound in the left lane on [XXX] i…On May [XXX], 2026 at 2:43 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northeastbound in the left lane on [XXX] in autonomous mode as it approached the green showing traffic light at the intersection with [XXX]. As the AVRIDE AV approached the intersection, an SUV traveling southeastbound on [XXX] also approached the intersection from the left of the AVRIDE AV. The SUV went against traffic rules and entered the intersection without stopping at the traffic light which was showing red. This maneuver by the SUV resulted in the front of the SUV making contact with the left side of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 502-14985 | Level 2 | Ford Motor Company | 2026-05 | UNK | 2025 FORD Expedition | Verified Engaged | Unknown | Unknown | 55 | Unknown | Telematics data from a 2025 Ford Expedition indicates that, on May [XXX], 2026, a Level 2 ADAS feature was engaged and active at the time of a frontal collision that resulted in the deployment of multiple airbags. The da…Telematics data from a 2025 Ford Expedition indicates that, on May [XXX], 2026, a Level 2 ADAS feature was engaged and active at the time of a frontal collision that resulted in the deployment of multiple airbags. The data identifies the primary impact location as the right front of the vehicle and indicates that the driver was belted at the time of the crash. The data further indicates that airbags deployed on both the driver and passenger sides, including frontal, side, and curtain airbags. The location of the crash, and occupant injury status are unknown. Ford will continue to evaluate any new information regarding this incident as it becomes available. |
| 502-15072 | Level 2 | Ford Motor Company | 2026-05 21:45 | Livonia, MI | 2026 FORD F-150 | Verified Engaged | SUV | Serious W/ Hospitalization | 8 | Highway / Freeway | The driver of a 2026 Ford F-150 reported that they were traveling westbound on [XXX], just before the [XXX] intersection (near Livonia, Michigan) on May [XXX] 2026 at approximately 9:45 p.m. The Ford driver reported that…The driver of a 2026 Ford F-150 reported that they were traveling westbound on [XXX], just before the [XXX] intersection (near Livonia, Michigan) on May [XXX] 2026 at approximately 9:45 p.m. The Ford driver reported that they were traveling with BlueCruise engaged at a very slow speed or not moving at all in stop and go traffic, when they were struck from behind by another vehicle, which the police estimated was traveling at approximately 60 mph. The Ford driver reported that there were no skid marks and that the other vehicle did not appear to brake prior to the collision. The Ford driver reported that the driver of the other vehicle smelled of marijuana when he got out of his vehicle and that he admitted to the police that he had been at "looking at his phone" prior to the collision. The Ford driver reported that airbags on the other vehicle deployed and that the person in other vehicle was injured and left the scene in an ambulance. The [XXX] police department responded to the accident. Ford has confirmed that the Ford F-150 is equipped with Ford Co-Pilot360 Assist 2.0, which includes Adaptive Cruise Control (ACC), Lane Centering Assist (LCA), and BlueCruise. Ford also has obtained telematics data showing that, on the date and at the time of the collision: 1) the Ford vehicle was traveling with BlueCruise engaged and was decelerating to a pre-collision speed of approximately 8 mph; 2) the BlueCruise feature disengaged upon impact; 3) the collision triggered a fuel-cutoff event; and 4) post-collision braking engaged, bringing the vehicle to a complete stop. Ford's investigation continues. |
| 540-14961 | Level 2 | General Motors, LLC | 2026-05 13:39 | Minocqua, WI | 2024 CHEVROLET Traverse | Verified Engaged | Other, see Narrative | Unknown | 55 | Rural Road | On May [XXX], 2025, a 2024 Chevrolet Traverse was travelling eastbound on [XXX] in Minocqua, Wisconsin with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat be…On May [XXX], 2025, a 2024 Chevrolet Traverse was travelling eastbound on [XXX] in Minocqua, Wisconsin with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pretensioners and driver airbags. The driver was wearing their seat belt at the time of crash. According to OnStar audio recordings, the driver reported that they swerved to avoid an oncoming vehicle traveling in the opposite lane. The driver further reported that the oncoming vehicle then moved back into the subject vehicle's path, resulting in the collision. System data indicates that Super Cruise entered an Override state approximately 3 seconds before the crash when the driver took steering control and transitioned to a Disabled/Not Ready state approximately 2 seconds before the crash following a driver brake application. |
| 540-15241 v2 | Level 2 | General Motors, LLC | 2026-05 21:35 | Fort Worth, TX | 2025 GMC Yukon | Verified Engaged | Other Fixed Object | Unknown | 47 | Highway / Freeway | On May [XXX], 2026, a 2025 GMC Yukon was travelling southbound on [XXX] in Fort Worth, Texas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the airbag and front seat …On May [XXX], 2026, a 2025 GMC Yukon was travelling southbound on [XXX] in Fort Worth, Texas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the airbag and front seat belt pretensioners. The driver was wearing their seat belt at the time of crash. According to OnStar audio recordings, the driver reported the vehicle veered off the road because it was raining and collided with the median. System Data indicates that Super Cruise changed to Disabled/Not ready 4 second prior to the crash due to brake press and/or steering wheel torque based on system design. Update: Corrected the date above to May [XXX], 2026. Initial submission had March [XXX], 2026 in the narrative. |
| 540-15242 v2 | Level 2 | General Motors, LLC | 2026-05 03:45 | Wethersfield, CT | 2024 CADILLAC Lyriq | Verified Engaged | Passenger Car | Unknown | 91 | Highway / Freeway | On May [XXX], 2026, a 2024 Cadillac LYRIQ was travelling northbound on [XXX] in Wethersfield, Connecticut, with Super Cruise engaged and active. Crash data indicates there was a left impact that did not deploy the airbag…On May [XXX], 2026, a 2024 Cadillac LYRIQ was travelling northbound on [XXX] in Wethersfield, Connecticut, with Super Cruise engaged and active. Crash data indicates there was a left impact that did not deploy the airbag or front seat belt pretensioners. The driver was wearing their seat belt at the time of crash. According to OnStar audio recordings, the driver reported that they were traveling in the middle lane when a vehicle from the left lane moved into their lane, struck the subject vehicle and following the impact, the subject vehicle collided with the guardrail. The driver also claims that the airbags were deployed. GM does not have crash data that indicates airbag deployment but it is possible that the airbags deployed as a result of the second collision with the guardrail. Out of an abundance of caution, GM is reporting this crash. System Data indicates that Super Cruise changed to Disabled/Not Ready 2 seconds prior to the crash due to brake pedal press per system design. Weather condition at the time of the crash is unknown. Update: Corrected the date above to May [XXX], 2026. Initial submission had March [XXX], 2026 in the narrative. |
| 540-15264 | Level 2 | General Motors, LLC | 2026-05 10:47 | Little Rock, AR | 2026 CHEVROLET Traverse | Verified Engaged | Unknown | Unknown | 21 | Highway / Freeway | On May [XXX], 2026, a 2026 Chevrolet Traverse was travelling westbound on [XXX] in Little Rock, Arkansas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the frontal ai…On May [XXX], 2026, a 2026 Chevrolet Traverse was travelling westbound on [XXX] in Little Rock, Arkansas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the frontal airbags and front seat belt pretensioners. The driver and front passenger were wearing their seat belts at the time of crash. According to the OnStar audio recordings, an occupant of the subject vehicle referenced another vehicle entering their lane; however, no additional details regarding the incident were provided. System Data indicates that Super Cruise changed to Override 4 second prior to the crash due to driver takeover with steering input and then changed to Disabled/Not Ready 2 seconds prior with the driver still in control of the vehicle. |
| 540-15284 | Level 2 | General Motors, LLC | 2026-05 06:29 | Whitehall, MI | 2026 CHEVROLET Traverse | Verified Engaged | Animal | Unknown | 75 | Highway / Freeway | On May [XXX], 2026, a 2026 Chevrolet Traverse was travelling northbound on [XXX} in Whitehall, Michigan with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the driver airb…On May [XXX], 2026, a 2026 Chevrolet Traverse was travelling northbound on [XXX} in Whitehall, Michigan with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the driver airbag and front seat pretensioners. The driver was wearing their seatbelt at the time of the crash. According to OnStar recordings, the driver indicated they hit a deer. System data indicates that Super Cruise changed to Disabled/Not ready one second prior to the crash due to brake pedal press. |
| 540-15297 v2 | Level 2 | General Motors, LLC | 2026-05 14:39 | Forsyth, GA | 2024 GMC Sierra | Verified Engaged | Pickup Truck | Minor W/ Hospitalization | 25 | Highway / Freeway | On May [XXX], 2026, a 2024 GMC Sierra was travelling southbound on [XXX] in Forsyth, Georgia with Super Cruise engaged and active. Crash data indicates there was a left impact and rollover that deployed airbags and fron…On May [XXX], 2026, a 2024 GMC Sierra was travelling southbound on [XXX] in Forsyth, Georgia with Super Cruise engaged and active. Crash data indicates there was a left impact and rollover that deployed airbags and front seat pretensioners. The driver and front passenger were wearing their seatbelts at the time of the crash. According to OnStar recordings, the driver indicated the vehicle hydroplaned off the road, striking a guard rail and entering a ditch. System data indicates that Super Cruise changed to Disabled/Not ready 5.8 seconds prior to the crash due to a degraded condition. Based on a police report reviewed by GM on August [XXX], 2026, the subject vehicle hydroplaned and struck the rear-left of a pickup truck in the adjacent lane. The subject vehicle then slid across the highway, down a hill, and struck a guardrail and power pole. The police report did not mention a rollover and noted that the driver was transported to Monroe County ER for leg pain. |
| 62-15355 v2 | Level 2 | Honda (American Honda Motor Co.) | 2026-05 | Wrightsville, GA | 2026 HONDA HR-V | Alleged Engaged | Unknown | Serious W/ Hospitalization | 65 | Highway / Freeway | Honda Customer Service received a rollover crash report from the customer on June [XXX], 2026. The customer did not indicate the road conditions or weather present at the time of the incident. The customer reported that …Honda Customer Service received a rollover crash report from the customer on June [XXX], 2026. The customer did not indicate the road conditions or weather present at the time of the incident. The customer reported that she was driving at 65MPH in a 55MPH zone with the Adaptive Cruise Control and Lane Keeping Assist Systems engaged. She stated that she was making a turn (unknown direction), and she believed the LKAS "auto-corrected" when one of the tires hit the lane marker. The customer reported that the vehicle rolled over approximately eight times and multiple airbags deployed. The customer was injured during the incident, and she requested information on obtaining the Event Data Recorder download for the insurance claim. UPDATE 8/27/26: Honda inspected the vehicle on August 24, 2026. We were unable to power up the vehicle, so we downloaded the SRS data directly from the unit. There were four data impact events and one rollover event recorded. The rollover event was found to be the first event recorded. The Adaptive Cruise Control and Lane Keep Assist features were on and engaged, and LKAS was providing minimal steering input. At the -2.5 timestamp, LKAS was no longer engaged, and the steering wheel angle became 65 degrees to the right and stability control engaged. No vehicle defects were identified. Photos from the inspection are available for review. |
| 945-15066 v2 | Level 2 | Nissan North America, Inc. | 2026-05 22:40 | New Canaan, CT | 2025 NISSAN Murano | Alleged Engaged | Other Fixed Object | Minor W/ Hospitalization | Highway / Freeway | The information contained in this report is based on Nissan's understanding of the allegations received during Claimant's discussions with Nissan's Consumer Affairs representatives. The incident vehicle is equipped with …The information contained in this report is based on Nissan's understanding of the allegations received during Claimant's discussions with Nissan's Consumer Affairs representatives. The incident vehicle is equipped with ProPilot Assist 1.0. On 5/[XXX]/2026, Nissan Technical Compliance received notification of an incident communicated via email to Nissan Consumer Affairs stating "My car crashed itself due to a malfunction with propilot assistance in which the driver had to go to the hospital. Need to make official report." On 5/[XXX]/2026, the claimant stated husband was using ProPilot Assist and the steering wheel locked. Claimant stated the driver attempted to use the brake and push the button to cancel ProPilot Assist. Claimant stated that the vehicle struck a guard rail and all airbags deployed. Claimant stated that the husband had minor concussion, cuts, and bruises. Claimant stated the vehicle was towed from the scene. Claimant stated that the vehicle is in the possession of the insurance company and the claimant is unaware of the vehicle's current location. ------- On 5/18/2026, the case was closed. Nissan had offered an inspection, but the vehicle had been surrendered to the insurance company, and the location of the vehicle was unknown. On 5/27/2026, a new CA file was opened requesting gap insurance information. The agent provided a phone number, and the case was closed on the same day. Nissan is continuing to monitor this incident for additional details. | |
| 10039-14963 | Level 2 | BMW of North America, LLC | 2026-04 15:45 | North Brunswick, NJ | 2026 BMW X7 | Verified Engaged | Passenger Car | Serious W/ Hospitalization | 67 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 10039-16087 | Level 2 | BMW of North America, LLC | 2026-04 05:49 | Council Grove, KS | 2026 BMW X5 | Verified Engaged | SUV | Minor W/O Hospitalization | 68 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-14567 | Level 2 | Tesla, Inc. | 2026-04 05:27 | Hayward, CA | 2025 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 73 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14568 | Level 2 | Tesla, Inc. | 2026-04 11:14 | Columbia, MO | 2024 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-14569 | Level 2 | Tesla, Inc. | 2026-04 13:39 | Bridgeville, PA | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14570 | Level 2 | Tesla, Inc. | 2026-04 06:37 | Kansas City, MO | 2023 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 49 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14571 | Level 2 | Tesla, Inc. | 2026-04 20:45 | Oklahoma City, OK | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 29 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14572 | Level 2 | Tesla, Inc. | 2026-04 21:42 | Orlando, FL | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 30 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14573 | Level 2 | Tesla, Inc. | 2026-04 22:46 | Glendale, CA | 2016 TESLA Model X | Verified Engaged | Unknown | Unknown | 63 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14574 | Level 2 | Tesla, Inc. | 2026-04 23:52 | Salem, OR | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 21 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14588 | Level 2 | Tesla, Inc. | 2026-04 22:45 | Granada Hills, CA | 2025 TESLA Model Y | Verified Engaged | SUV | Unknown | 83 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14589 | Level 2 | Tesla, Inc. | 2026-04 19:36 | Florence, NJ | 2022 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 66 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14590 | Level 2 | Tesla, Inc. | 2026-04 17:10 | Asheville, NC | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 40 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-14591 | Level 2 | Tesla, Inc. | 2026-04 12:32 | Boerne, TX | 2020 TESLA Model 3 | Verified Engaged | SUV | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14592 | Level 2 | Tesla, Inc. | 2026-04 18:41 | Indianapolis, IN | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-14593 | Level 2 | Tesla, Inc. | 2026-04 18:25 | Seaford, NY | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 50 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14594 | Level 2 | Tesla, Inc. | 2026-04 17:13 | Knightstown, IN | 2021 TESLA Model Y | Verified Engaged | Unknown | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-14595 | Level 2 | Tesla, Inc. | 2026-04 16:53 | Atlanta, GA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 58 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14596 | Level 2 | Tesla, Inc. | 2026-04 15:30 | Fredericksburg, TX | 2024 TESLA Cybertruck | Verified Engaged | Passenger Car | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-14597 | Level 2 | Tesla, Inc. | 2026-04 14:52 | Stillwater, OK | 2026 TESLA Model 3 | Verified Engaged | Van | Unknown | 43 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14598 | Level 2 | Tesla, Inc. | 2026-04 23:08 | Ellicott City, MD | 2026 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 27 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14599 | Level 2 | Tesla, Inc. | 2026-04 22:00 | Sacramento, CA | 2023 TESLA Model X | Verified Engaged | Passenger Car | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14600 | Level 2 | Tesla, Inc. | 2026-04 20:58 | Scottsdale, AZ | 2023 TESLA Model S | Verified Engaged | Unknown | Unknown | 15 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14601 | Level 2 | Tesla, Inc. | 2026-04 15:27 | Las Vegas, NV | 2026 TESLA Model X | Verified Engaged | Pole / Tree | Unknown | 22 | Parking Lot | Redacted by NHTSA as confidential business information |
| 13781-14602 | Level 2 | Tesla, Inc. | 2026-04 12:00 | Byron, CA | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 50 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14603 | Level 2 | Tesla, Inc. | 2026-04 04:36 | Kissimmee, FL | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 30 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14604 | Level 2 | Tesla, Inc. | 2026-04 13:32 | Austin, TX | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14605 | Level 2 | Tesla, Inc. | 2026-04 09:56 | Tucson, AZ | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 22 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14606 | Level 2 | Tesla, Inc. | 2026-04 06:10 | Diamond Bar, CA | 2019 TESLA Model S | Verified Engaged | Unknown | Unknown | 18 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14607 | Level 2 | Tesla, Inc. | 2026-04 05:07 | Gardena, CA | 2023 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 39 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14608 | Level 2 | Tesla, Inc. | 2026-04 03:46 | Salem, NH | 2021 TESLA Model S | Verified Engaged | Pole / Tree | Unknown | 73 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14610 | Level 2 | Tesla, Inc. | 2026-04 20:22 | Gold Beach, OR | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 29 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14611 | Level 2 | Tesla, Inc. | 2026-04 01:53 | Fort Lauderdale, FL | 2023 TESLA Model 3 | Verified Engaged | Pole / Tree | Unknown | 13 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14612 | Level 2 | Tesla, Inc. | 2026-04 17:53 | La Crescenta, CA | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 19 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14613 | Level 2 | Tesla, Inc. | 2026-04 11:13 | Tinley Park, IL | 2023 TESLA Model Y | Verified Engaged | Pickup Truck | Unknown | 30 | Street | Redacted by NHTSA as confidential business information |
| 13781-14614 | Level 2 | Tesla, Inc. | 2026-04 03:46 | Atlanta, GA | 2021 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 51 | Street | Redacted by NHTSA as confidential business information |
| 13781-14615 | Level 2 | Tesla, Inc. | 2026-04 02:17 | Kissimmee, FL | 2022 TESLA Model 3 | Verified Engaged | SUV | Unknown | 56 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14616 | Level 2 | Tesla, Inc. | 2026-04 01:28 | Pasadena, CA | 2018 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | Intersection | Redacted by NHTSA as confidential business information | |
| 13781-14632 | Level 2 | Tesla, Inc. | 2026-04 07:40 | Sherman Oaks, CA | 2023 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 72 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14633 | Level 2 | Tesla, Inc. | 2026-04 19:52 | Anaheim, CA | 2022 TESLA Model X | Verified Engaged | Passenger Car | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14634 | Level 2 | Tesla, Inc. | 2026-04 20:32 | San Antonio, TX | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 17 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14635 | Level 2 | Tesla, Inc. | 2026-04 21:31 | Chattanooga, TN | 2022 TESLA Model 3 | Verified Engaged | SUV | Unknown | 19 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-14636 | Level 2 | Tesla, Inc. | 2026-04 23:15 | Temecula, CA | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 40 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14637 | Level 2 | Tesla, Inc. | 2026-04 13:28 | Richmond, TX | 2023 TESLA Model Y | Verified Engaged | SUV | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14638 | Level 2 | Tesla, Inc. | 2026-04 15:18 | Montgomery, AL | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 27 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14639 | Level 2 | Tesla, Inc. | 2026-04 18:49 | Escondido, CA | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 71 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14641 | Level 2 | Tesla, Inc. | 2026-04 20:03 | Orange, NJ | 2023 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 23 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14642 | Level 2 | Tesla, Inc. | 2026-04 21:08 | Spicewood, TX | 2024 TESLA Cybertruck | Verified Engaged | Unknown | Unknown | 57 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14643 | Level 2 | Tesla, Inc. | 2026-04 22:09 | Morrow, OH | 2022 TESLA Model Y | Verified Engaged | Unknown | Unknown | 45 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14669 | Level 2 | Tesla, Inc. | 2026-04 16:45 | Buda, TX | 2022 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14670 | Level 2 | Tesla, Inc. | 2026-04 18:31 | Bridgewater, NJ | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 71 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14671 | Level 2 | Tesla, Inc. | 2026-04 21:42 | Edison, NJ | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 11 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14672 | Level 2 | Tesla, Inc. | 2026-04 21:50 | Tucson, AZ | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 66 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14673 | Level 2 | Tesla, Inc. | 2026-04 07:21 | Renton, WA | 2026 TESLA Model Y | Verified Engaged | Other, see Narrative | Unknown | 34 | Street | Redacted by NHTSA as confidential business information |
| 13781-14674 | Level 2 | Tesla, Inc. | 2026-04 08:43 | Los Angeles, CA | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 124 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14675 | Level 2 | Tesla, Inc. | 2026-04 14:02 | Thermal, CA | 2024 TESLA Model Y | Verified Engaged | Pickup Truck | Unknown | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14676 | Level 2 | Tesla, Inc. | 2026-04 17:33 | Nashville, TN | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14677 | Level 2 | Tesla, Inc. | 2026-04 22:07 | MA | 2026 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 68 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14678 | Level 2 | Tesla, Inc. | 2026-04 02:49 | San Diego, CA | 2022 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 66 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14679 | Level 2 | Tesla, Inc. | 2026-04 18:40 | Mission Viejo, CA | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-14680 | Level 2 | Tesla, Inc. | 2026-04 17:01 | Irvine, CA | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-14681 | Level 2 | Tesla, Inc. | 2026-04 16:05 | Claremont, CA | 2018 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 68 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14682 | Level 2 | Tesla, Inc. | 2026-04 05:25 | TX | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 79 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14683 | Level 2 | Tesla, Inc. | 2026-04 04:54 | Martinez, CA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 38 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14684 | Level 2 | Tesla, Inc. | 2026-04 21:45 | West Bloomfield, MI | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 43 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14685 | Level 2 | Tesla, Inc. | 2026-04 19:24 | Los Angeles, CA | 2026 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 0 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14686 | Level 2 | Tesla, Inc. | 2026-04 19:17 | Forest Hills, NY | 2016 TESLA Model S | Verified Engaged | Unknown | Unknown | 9 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14687 | Level 2 | Tesla, Inc. | 2026-04 16:56 | Snohomish, WA | 2026 TESLA Model Y | Verified Engaged | SUV | Unknown | 55 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14688 | Level 2 | Tesla, Inc. | 2026-04 09:13 | Phoenix, AZ | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 28 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14689 | Level 2 | Tesla, Inc. | 2026-04 05:01 | CA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14691 | Level 2 | Tesla, Inc. | 2026-04 11:57 | Gustine, CA | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14692 | Level 2 | Tesla, Inc. | 2026-04 01:11 | Garden Prairie, IL | 2022 TESLA Model Y | Verified Engaged | Heavy Truck | Unknown | 54 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-14693 | Level 2 | Tesla, Inc. | 2026-04 12:35 | Gary, IN | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-14694 | Level 2 | Tesla, Inc. | 2026-04 12:07 | Meriden, CT | 2021 TESLA Model 3 | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-14695 | Level 2 | Tesla, Inc. | 2026-04 12:54 | Orange, CT | 2018 TESLA Model X | Verified Engaged | Passenger Car | Unknown | 16 | Intersection | 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. 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.