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 801 to 900.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 31101-16197 | ADS | Avride Inc. | 2026-07 12:20 | Dallas, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 8 | Street | On July [XXX], 2026 at 12:20 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling westbound in the left lane on [XXX] in autonomous…On July [XXX], 2026 at 12:20 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling westbound in the left lane on [XXX] in autonomous mode. A passenger car was also traveling westbound slightly ahead of the AVRIDE AV in the right lane. As the AVRIDE AV proceeded straight ahead, the passenger car initiated an unsafe left turn, striking the AVRIDE AV. This maneuver resulted in the left side of the passenger car making contact with the right front of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 35021-16268 | ADS | MOIA America LLC | 2026-07 10:54 | Beverly Hills, CA | 2023 Volkswagen ID. Buzz | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 19 | Street | On July [XXX], 2026, at approximately 10:54 AM PDT, a MOIA autonomous vehicle ("MOIA AV") was operating in autonomous mode in Beverly Hills, California, with a safety driver in the driver's seat. The MOIA AV was traveli…On July [XXX], 2026, at approximately 10:54 AM PDT, a MOIA autonomous vehicle ("MOIA AV") was operating in autonomous mode in Beverly Hills, California, with a safety driver in the driver's seat. The MOIA AV was traveling southbound on [XXX] and completed a left turn onto eastbound [XXX]. As the MOIA AV proceeded eastbound approaching the intersection with [XXX], the automated driving system disengaged. Approximately nine seconds after the disengagement, and with the automated driving system no longer in control, the safety driver allowed the MOIA AV to drift to the right causing the front passenger side of the MOIA AV to make contact with the driver side of a passenger car that was parked and unoccupied at the south curb of [XXX], facing east. The MOIA AV was traveling at approximately 19 mph at the time of contact. At the time of contact, the MOIA AV's automated driving system was not engaged. Following the contact, the safety driver brought the MOIA AV to a controlled stop at the curb ahead of the parked vehicle. No injuries were reported. The parked vehicle was unoccupied at the time of contact. No airbags deployed. Both vehicles sustained minor damage, and neither vehicle was towed from the scene. Weather conditions were clear, and the roadway surface was dry. The registered owner of the parked vehicle was notified of the collision at the scene and provided appropriate contact and insurance information. Law enforcement was not contacted. MOIA is reporting this crash under Request No. 2 of Standing General Order 2021-01 because the subject vehicle struck another vehicle, and the automated driving system was engaged within the 30 seconds immediately prior to the crash. MOIA is reviewing the vehicle data and may supplement or correct this report as additional information becomes available. |
| 502-15630 | Level 2 | Ford Motor Company | 2026-07 15:14 | Jacksonburg, IN | 2025 FORD Expedition MAX | Verified Engaged | Unknown | Unknown | 31 | Highway / Freeway | On July 6, 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 3:14 PM, a 2025 Ford Expedition was involved in an incident while traveling westbound on [XXX] in Jacksonburg, Indiana.…On July 6, 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 3:14 PM, a 2025 Ford Expedition was involved in an incident while traveling westbound on [XXX] in Jacksonburg, Indiana. This data indicates that Level 2 Advanced Driver Assistance System (ADAS) functionality, specifically the combination of Adaptive Cruise Control (ACC) and Lane Centering Assist (LCA), was active within 30 seconds prior to the collision. The data indicates a frontal impact event that resulted in the deployment of both the driver and passenger front airbags. The data further indicates that both the driver and passenger seatbelts were "Belted" at the time of impact. The specific circumstances of the collision and the injury status of the occupants are currently unknown. Ford will continue to evaluate any new information regarding this incident as it becomes available. |
| 502-15784 | Level 2 | Ford Motor Company | 2026-07 16:58 | Newark, DE | 2025 FORD Expedition | Verified Engaged | Unknown | Unknown | 31 | Highway / Freeway | On July [XXX], 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 4:58 PM, a 2025 Ford Expedition was involved in an incident while traveling northeast on [XXX] in Newark, Delaware.…On July [XXX], 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 4:58 PM, a 2025 Ford Expedition was involved in an incident while traveling northeast on [XXX] in Newark, Delaware. The data preliminarily indicates that BlueCruise, a Level 2 Advanced Driver Assistance System (ADAS) feature, was engaged at the time of the collision. The data preliminarily indicates a frontal impact event and subsequent rollover that resulted in the deployment of the driver and passenger front, side and curtain airbags. The data preliminarily indicates that both the driver and front passenger seatbelts were buckled at the time of impact. The specific circumstances of the collision and the injury status of the occupants are currently unknown. Ford will continue to evaluate any new information regarding this incident as it becomes available. |
| 502-15791 | Level 2 | Ford Motor Company | 2026-07 21:58 | Trenton, NJ | 2025 FORD F-150 | Verified Engaged | Unknown | Unknown | 47 | Street | On July [XXX], 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 9:58 PM, a 2025 Ford F-150 was involved in an incident while traveling northwest on [XXX] in Trenton, New Jersey. …On July [XXX], 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 9:58 PM, a 2025 Ford F-150 was involved in an incident while traveling northwest on [XXX] in Trenton, New Jersey. This preliminarily indicates that Level 2 Advanced Driver Assistance System (ADAS) functionality, specifically the combination of Adaptive Cruise Control (ACC) and Lane Centering Assist (LCA), was active within the 30 seconds prior to the collision. The data preliminarily indicates a frontal impact event that resulted in the deployment of the driver front, side, curtain and knee airbags, and the passenger side and curtain airbags. The data preliminarily indicates that the driver seatbelt was buckled and front passenger seatbelt was unbuckled at the time of impact. The specific circumstances of the collision and the injury status of the occupants are currently unknown. Ford will continue to evaluate any new information regarding this incident as it becomes available. |
| 502-15929 | Level 2 | Ford Motor Company | 2026-07 14:16 | Indianapolis, IN | 2024 FORD F-150 | Verified Engaged | Unknown | Unknown | 68 | Highway / Freeway | On July 22, 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 2:16 PM, a 2024 Ford F-150 was involved in an incident while traveling westbound [XXX] in Indianapolis, Indiana. The …On July 22, 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 2:16 PM, a 2024 Ford F-150 was involved in an incident while traveling westbound [XXX] in Indianapolis, Indiana. The data preliminarily indicates that: 1. BlueCruise, a Level 2 Advanced Driver Assistance System (ADAS) feature, was engaged at the time of the collision. 2. A Frontal impact event resulted in the deployment of the driver and passenger side and curtain airbags. 3. The Driver seatbelt was buckled at the time of impact. The specific circumstances of the collision and the injury status of the occupants are currently unknown. Ford will continue to evaluate any new information regarding this incident as it becomes available. |
| 502-15995 | Level 2 | Ford Motor Company | 2026-07 23:58 | Detroit, MI | 2024 LINCOLN Navigator | Verified Engaged | Unknown | Unknown | 46 | Highway / Freeway | On July [XXX], 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 11:58 PM, a 2024 Lincoln Navigator was involved in an incident while traveling southwest [XXX] in Detroit, Michigan…On July [XXX], 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 11:58 PM, a 2024 Lincoln Navigator was involved in an incident while traveling southwest [XXX] in Detroit, Michigan. The data preliminarily indicates that: 1. BlueCruise, a Level 2 Advanced Driver Assistance System (ADAS) feature, was engaged at the time of the collision. 2. A Frontal impact event resulted in the deployment of the driver and passenger side and curtain airbags. 3. The Driver seatbelt was buckled at the time of impact. The specific circumstances of the collision and the injury status of the occupants are currently unknown. Ford will continue to evaluate any new information regarding this incident as it becomes available. |
| 502-15998 | Level 2 | Ford Motor Company | 2026-07 00:49 | Glyndon, MN | 2025 FORD Explorer | Verified Engaged | Unknown | Unknown | 74 | Highway / Freeway | On July [XXX], 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 12:49 AM, a 2025 Ford Explorer was involved in an incident while traveling west [XXX] in Glyndon, Minnesota. The da…On July [XXX], 2026, Ford received telematics data indicating that on July [XXX], 2026, at approximately 12:49 AM, a 2025 Ford Explorer was involved in an incident while traveling west [XXX] in Glyndon, Minnesota. The data preliminarily indicates that: 1. Adaptive Cruise Control (ACC) and Lane Centering Assist (LCA), which together constitute Level 2 Advanced Driver Assistance System (ADAS) functionality, was engaged at the time of the collision. 2. A Frontal impact event resulted in the deployment of the driver front, side, curtain and knee airbags, and the passenger side and curtain airbags. 3. The Driver seatbelt was buckled at the time of impact. The specific circumstances of the collision and the injury status of the occupants are currently unknown. Ford will continue to evaluate any new information regarding this incident as it becomes available. |
| 502-16127 v3 | Level 2 | Ford Motor Company | 2026-07 01:34 | Detroit, MI | 2024 FORD F-150 | Alleged Engaged | SUV | Serious W/ Hospitalization | 59 | Highway / Freeway | On August [XXX], 2026, Ford obtained the State of Michigan Traffic Crash Report relating to this incident. This report states that there were no automation systems engaged on any of the three vehicles involved in the inc…On August [XXX], 2026, Ford obtained the State of Michigan Traffic Crash Report relating to this incident. This report states that there were no automation systems engaged on any of the three vehicles involved in the incident and includes other information regarding the location of the vehicles and the sequence of events that was later clarified or expanded on in the subsequent Original Incident Report. On September [XXX], 2026, Ford obtained the Original Incident Report prepared by the Michigan State Police relating to this incident, together with supporting information. This report confirms that: 1) the Equinox was stopped on the right shoulder of the highway with its hazard lights turned on; 2) the Lightning left the roadway to the right, struck a concrete wall, and then struck the rear of the Equinox, pushing the Equinox into the right travel lane of the highway; and 3) the Escape struck the rear of the Equinox "moments after the initial crash" between the Lightning and the Equinox. The Original Incident Report also states that the driver of the Equinox, who incurred serious injuries, and the driver of the Lightning, who incurred minor injuries, were both taken to a hospital for medical treatment. |
| 540-15721 | Level 2 | General Motors, LLC | 2026-07 13:35 | Hampshire, IL | 2024 CHEVROLET Traverse | Verified Engaged | Unknown | Unknown | 51 | Rural Road | On July [XXX], 2026, a 2024 Chevrolet Traverse was travelling southbound on [XXX] near Pingree Grove, Illinois with Super Cruise engaged and active. Crash data indicates a front impact occurred that deployed driver and p…On July [XXX], 2026, a 2024 Chevrolet Traverse was travelling southbound on [XXX] near Pingree Grove, Illinois with Super Cruise engaged and active. Crash data indicates a front impact occurred that deployed driver and passenger airbags and front seat pretensioners and that the driver and passenger were wearing their seatbelts at the time of the incident. At 29 seconds prior to the incident, the vehicle provided warning that it was nearing the end of the Super Cruise operating domain and, at the same time, Super Cruise changed state to Disabled/Not Ready due to driver taking over control with steering wheel torque input. |
| 540-15787 v2 | Level 2 | General Motors, LLC | 2026-07 15:06 | Valentine, AZ | 2026 CHEVROLET Traverse | Verified Engaged | Unknown | Unknown | 77 | Rural Road | On July [XXX], 2026, a 2026 Chevrolet Traverse was travelling westbound on [XXX] near Valentine, AZ with Super Cruise engaged and active. Crash data indicates there was a frontal and left impact that deployed the airbag…On July [XXX], 2026, a 2026 Chevrolet Traverse was travelling westbound on [XXX] near Valentine, AZ with Super Cruise engaged and active. Crash data indicates there was a frontal and left impact that deployed the airbags and front seat pretensioners and that the driver and passenger were wearing their seatbelt at the time of the crash. System data indicates that Super Cruise was engaged and active at the time of the incident. Update: On August 20, 2026, GM reviewed updated system data which showed Super Cruise changed to Disabled/Not Ready 1 second prior to the crash due to a brake pedal press. |
| 540-15816 | Level 2 | General Motors, LLC | 2026-07 10:40 | Pikeville, KY | 2026 CHEVROLET Traverse | Verified Engaged | Passenger Car | Fatality | 62 | Rural Road | On July [XXX], 2026, a 2026 Chevrolet Traverse was travelling northbound on [XXX] in Pikeville, Kentucky with Super Cruise engaged and active. Crash data indicates a front impact and a left impact occurred that deployed …On July [XXX], 2026, a 2026 Chevrolet Traverse was travelling northbound on [XXX] in Pikeville, Kentucky with Super Cruise engaged and active. Crash data indicates a front impact and a left impact occurred that deployed the driver airbag and front seat pretensioners and that the driver was wearing their seat belt at the time of the incident. According to a local news article, the subject vehicle was struck by a Mitsubishi Eclipse traveling the wrong direction. System data indicates Super Cruise was engaged and active at the time of the incident. |
| 540-15843 | Level 2 | General Motors, LLC | 2026-07 10:25 | Shoshoni, WY | 2026 GMC Yukon XL | Verified Engaged | Heavy Truck | Unknown | 53 | Rural Road | On July [XXX], 2026, a 2026 GMC Yukon XL was travelling westbound on [XXX] in Shoshoni, Wyoming with Super Cruise engaged and active. Crash data indicates a front impact and a rollover with left and right impacts occurre…On July [XXX], 2026, a 2026 GMC Yukon XL was travelling westbound on [XXX] in Shoshoni, Wyoming with Super Cruise engaged and active. Crash data indicates a front impact and a rollover with left and right impacts occurred that deployed the front airbags and front seat pretensioners. Crash data indicates the driver and front passenger were wearing their seat belts at the time of the incident. According to a local news article, the subject vehicle was sideswiped by an eastbound semitrailer that suffered a blown tire and drifted into the westbound lane. System data indicates Super Cruise state changed to Disabled/Not Ready 1 second prior to the incident due to a brake pedal press. |
| 540-15905 | Level 2 | General Motors, LLC | 2026-07 03:52 | Goleta, CA | 2024 CHEVROLET Traverse | Verified Engaged | Pole / Tree | Minor W/O Hospitalization | 12 | Street | On July [XXX], 2026, a 2024 Chevrolet Traverse was travelling westbound on [XXX] in Solvang, California with Super Cruise engaged and active. Crash data recorded multiple front impacts that deployed the driver airbags an…On July [XXX], 2026, a 2024 Chevrolet Traverse was travelling westbound on [XXX] in Solvang, California with Super Cruise engaged and active. Crash data recorded multiple front impacts that deployed the driver airbags and front seat pretensioners. Crash data indicates the driver was wearing their seat belt at the time of the incident. According to OnStar recordings, the driver indicated he swerved to avoid a deer and struck a tree. The driver also indicated he had a bruise on his arm but that medical attention was not needed. System data indicates Super Cruise state changed to Disabled/Not Ready due to a brake press at the time of the incident. |
| 540-15907 | Level 2 | General Motors, LLC | 2026-07 22:01 | Jasper, FL | 2026 GMC Yukon | Verified Engaged | Unknown | Unknown | 81 | Highway / Freeway | On July [XXX], 2026, a 2026 GMC Yukon was travelling southbound on [XXX] in Jasper, Florida with Super Cruise engaged and active. Crash data recorded a left impact and rollover that deployed the driver airbags and front …On July [XXX], 2026, a 2026 GMC Yukon was travelling southbound on [XXX] in Jasper, Florida with Super Cruise engaged and active. Crash data recorded a left impact and rollover that deployed the driver airbags and front seat pretensioners. Crash data indicates the driver was wearing their seat belt at the time of the incident. System data indicates Super Cruise state changed to Enabled 4 seconds before the incident due to the driver taking control through steering input. |
| 540-15908 v2 | Level 2 | General Motors, LLC | 2026-07 10:22 | Henrietta, TX | 2025 GMC Yukon XL | Verified Engaged | Heavy Truck | Unknown | 82 | Highway / Freeway | On July [XXX], 2026, a 2026 GMC Yukon XL was travelling westbound on [XXX] in Henrietta, Texas with Super Cruise engaged and active. Crash data recorded a front impact that deployed the driver and passenger airbags and f…On July [XXX], 2026, a 2026 GMC Yukon XL was travelling westbound on [XXX] in Henrietta, Texas with Super Cruise engaged and active. Crash data recorded a front impact that deployed the driver and passenger airbags and front seat pretensioners. Crash data indicates the driver and front passenger were wearing their seat belts at the time of the incident. According to OnStar recordings, the driver indicated they "dozed off." System data indicates Super Cruise state changed to Degraded at the time of the incident due to meeting the criteria for a degraded condition, per system design. Based on a police report reviewed by GM on August 4, 2026, the subject vehicle struck the rear of a semitrailer after it moved into the lane ahead of the subject vehicle. The police report indicates the driver of the subject vehicle fell asleep and woke up immediately before collision and was unable to stop. According to the report, there were no reported injuries among the four occupants of the subject vehicle or the one occupant in the crash partner. |
| 540-15928 v2 | Level 2 | General Motors, LLC | 2026-07 09:17 | Boardman, OR | 2024 GMC Sierra | Verified Engaged | Other, see Narrative | No Injured Reported | 84 | Highway / Freeway | On July [XXX], 2026, a 2024 GMC Sierra was travelling eastbound on [XXX] in Boardman, Oregon with Super Cruise engaged and active. Crash data recorded multiple front impacts that deployed the driver and passenger airbags…On July [XXX], 2026, a 2024 GMC Sierra was travelling eastbound on [XXX] in Boardman, Oregon with Super Cruise engaged and active. Crash data recorded multiple front impacts that deployed the driver and passenger airbags and front seat pretensioners. Crash data indicates the driver and passenger were wearing their seat belt at the time of the incident. According to the OnStar recording, someone in the vehicle said they were "all right", but did not provide incident details. System data indicates Super Cruise state changed to Enabled 21 seconds prior to the incident due to inhibit conditions, per system design. On August 20, 2026, GM reviewed the police report which indicated that the driver turned to communicate with the right-front passenger. After turning back toward the roadway, the driver observed that the vehicle was traveling in the highway median. The vehicle subsequently became airborne between two bridge decks, landed on Laurel Lane, and came to an uncontrolled stop on the east-side embankment. No other vehicles were involved, no injuries were reported, and police issued the driver a warning for failure to maintain lane. GM reviewed system data again, after receiving the police report, and determined that Super Cruise state changed to Disabled/Not Ready 25 seconds prior to the incident due to the driver taking control. |
| 540-15935 | Level 2 | General Motors, LLC | 2026-07 13:15 | Fowler, IN | 2025 CHEVROLET Traverse | Verified Engaged | Other, see Narrative | Minor W/O Hospitalization | 61 | Rural Road | On July [XXX], 2026, a 2025 Chevrolet Traverse was travelling southbound on [XXX] in Fowler, Indiana, with Super Cruise engaged and active. Crash data indicates there were multiple front impacts that deployed the frontal…On July [XXX], 2026, a 2025 Chevrolet Traverse was travelling southbound on [XXX] in Fowler, Indiana, with Super Cruise engaged and active. Crash data indicates there were multiple front impacts that deployed the frontal airbags and front seat belt pretensioners, and that the driver and front passenger were wearing their seat belts at the time of crash. According to the OnStar audio recordings, the vehicle collided with a truck. System Data indicates that Super Cruise changed to Disabled/Not ready 1 second prior to the crash due to driver taking over vehicle control, per system design. Weather condition at the time of the crash is unknown. |
| 540-15936 | Level 2 | General Motors, LLC | 2026-07 19:05 | Pompano Beach, FL | 2025 GMC Yukon XL | Verified Engaged | Other Fixed Object | Minor W/O Hospitalization | 83 | Highway / Freeway | On July [XXX], 2026, a 2025 GMC Yukon XL was travelling northbound on [XXX] in Pompano Beach, Florida, with Super Cruise engaged and active. Crash data indicates there was a left impact that deployed the driver airbag an…On July [XXX], 2026, a 2025 GMC Yukon XL was travelling northbound on [XXX] in Pompano Beach, Florida, with Super Cruise engaged and active. Crash data indicates there was a left impact that deployed the driver airbag and front seat belt pretensioners, and that the driver was not wearing their seat belt at the time of crash. According to the OnStar audio recordings, the driver claims they reached over to grab something in the passenger seat and the vehicle hit the median on the highway. System Data indicates that Super Cruise changed to Disabled/Not ready 1 second prior to the crash due to steering torque input. Weather condition at the time of the crash is unknown. |
| 669-15814 | Level 2 | Hyundai Motor America | 2026-07 12:14 | Hanceville, AL | 2026 HYUNDAI Palisade | Verified Engaged | Other, see Narrative | Unknown | 57 | Street | Based on telematics data, a consumer was operating a 2026 Hyundai Palisade with Smart Cruise Control (SCC) and Lane Following Assist (LFA) engaged while traveling southeast at approximately 57 mph on [XXX] near Hancevill…Based on telematics data, a consumer was operating a 2026 Hyundai Palisade with Smart Cruise Control (SCC) and Lane Following Assist (LFA) engaged while traveling southeast at approximately 57 mph on [XXX] near Hanceville, Alabama. At no point prior to airbag deployment did the telematics data indicate any abnormal input or unexpected behavior from the SCC or LFA systems. Approximately one second prior to impact, the data shows a brake application and a right steering input, which resulted in disengagement of the SCC. The vehicle was involved in an impact event that resulted in deployment of both the driver and front passenger airbags. An automatic emergency SOS call was initiated by the vehicle's telematics system and routed to the Consumer Affairs hotline. During this call, it was reported that the vehicle had struck another vehicle. At this time, no additional information is available. This report will be updated as further information becomes available. |
| 669-15815 | Level 2 | Hyundai Motor America | 2026-07 22:27 | Charlevoix, MI | 2026 HYUNDAI Palisade | Verified Engaged | Unknown | Unknown | 61 | Street | Based on telematics data, a consumer was operating a 2026 Hyundai Palisade with Smart Cruise Control (SCC) and Lane Following Assist (LFA) engaged while traveling westbound at approximately 61 mph on [XXX] in Charlevoix,…Based on telematics data, a consumer was operating a 2026 Hyundai Palisade with Smart Cruise Control (SCC) and Lane Following Assist (LFA) engaged while traveling westbound at approximately 61 mph on [XXX] in Charlevoix, Michigan. At no point prior to airbag deployment did the telematics data indicate any abnormal input or unexpected behavior from the SCC or LFA systems. Approximately two seconds prior to impact, the data shows a brake application, which resulted in the disengagement of the SCC system, consistent with system operation. Approximately one second prior to impact, a right steering input was recorded. The vehicle was subsequently involved in an impact event that resulted in deployment of both the driver and front passenger airbags. An automatic emergency SOS call was initiated by the vehicle's telematics system and routed to the Consumer Affairs hotline. During the call, the nature of the object or vehicle impacted could not be determined. At this time, no additional information is available. This report will be updated as further information becomes available. |
| 669-15999 | Level 2 | Hyundai Motor America | 2026-07 19:20 | Buchanan, VA | 2026 HYUNDAI Palisade | Verified Engaged | Other, see Narrative | Unknown | 78 | Highway / Freeway | Based on telematics data, a consumer was operating a 2026 Hyundai Palisade with Highway Driving Assist 2 (HDA2) and Lane Following Assist (LFA) engaged while traveling southbound on Highway [XXX] in Buchanan, Virginia, a…Based on telematics data, a consumer was operating a 2026 Hyundai Palisade with Highway Driving Assist 2 (HDA2) and Lane Following Assist (LFA) engaged while traveling southbound on Highway [XXX] in Buchanan, Virginia, at approximately 78 mph. Beginning approximately 30 seconds prior to the collision and continuing until just before impact, the vehicle's Forward Attention Warning (FAW) in-cabin monitoring camera detected multiple prolonged instances of driver distraction. Approximately three seconds prior to impact, a Lane Keeping Assist (LKA) driver warning was issued, and the system provided steering torque assistance to help maintain the vehicle within its lane. Approximately two seconds prior to impact, the telematics data shows a left steering input by the driver, followed by a brake application, which resulted in the deactivation of HDA2, consistent with intended system operation. The vehicle was subsequently involved in an impact event that resulted in deployment of both the driver and front passenger airbags. An automatic emergency SOS call was initiated by the vehicle's telematics system and routed to the Consumer Affairs hotline. During the call, the operator overheard the driver state that the vehicle had struck a guardrail. At this time, no additional information is available. This report will be updated as further information becomes available. |
| 855-15937 | Level 2 | Mercedes-Benz USA, LLC | 2026-07 06:09 | Scotch Plains, NJ | 2025 MERCEDES-BENZ GLE-Class | Alleged Engaged | Other Fixed Object | Minor W/O Hospitalization | Intersection | The subject MY 2025 Mercedes-Benz GLE 450e 4MATIC is equipped with the Driver Assistance Package that includes L2 ADAS Active Distance Assist Distronic and Active Steering Assist. The driver of the subject vehicle initia…The subject MY 2025 Mercedes-Benz GLE 450e 4MATIC is equipped with the Driver Assistance Package that includes L2 ADAS Active Distance Assist Distronic and Active Steering Assist. The driver of the subject vehicle initially contacted the Mercedes-Benz USA (âÂÂMBUSAâÂÂ) Customer Care Center (âÂÂCCCâÂÂ) on July 20, 2026, and claimed he was driving the subject vehicle on 7/[XXX]/26, engaged the lane keeping assist, and remembers hitting a curb, then hitting an electrical post, then rolling over and landing right side up. He allegedly exited the vehicle by himself and called 911. The customer alleged no injuries at that time, and mentioned damage to the electrical post. The customer provided additional information to the CCC on July 21, 2026, where he alleged âÂÂengaging lane maintenance and steering control approx 200m from the accident zone just after crossing a signalâ while driving the subject vehicle, and that airbags deployed during the crash. The customer claims he did not go to a hospital and claimed not to have experienced any pain after the crash, however, allegedly experienced rib and right side back and neck pain a few days later. MBUSA learned on July 22, 2026, from the vehicle telematics that the subject vehicle was on [XXX] near [XXX] in Scotch Plains, New Jersey, at the time of the airbag deployment. Images from Google Maps show varying roadway markings along the referenced intersection. In accordance with the requirements of the NHTSA ADAS SGO, MBUSA is submitting this 5-day incident report. The narrative summary is based entirely on the customerâÂÂs description and allegations of the incident. MBUSA has not confirmed or verified this account or any of the customerâÂÂs allegations and has initiated a further investigation into the | |
| 945-16481 | Level 2 | Nissan North America, Inc. | 2026-07 18:33 | Louisa, VA | 2026 NISSAN Rogue | Verified Engaged | Unknown | Unknown | 63 | Highway / Freeway | The information contained in this report is based solely on Nissan's notification via telematics that a vehicle equipped with Pro Pilot Assist 2.1 was involved in an incident involving an air bag deployment. The system …The information contained in this report is based solely on Nissan's notification via telematics that a vehicle equipped with Pro Pilot Assist 2.1 was involved in an incident involving an air bag deployment. The system was active in "hands-on" mode within 30 seconds of the incident. Nissan is currently working through collected data will provide additional details in accordance with relevant consumer privacy laws. Nissan has not been contacted regarding this incident. We have been able to locate a photo of what we understand to be the vehicle, but we are unable to confirm whether the vehicle damage shown in the photo is related to the reported incident. Note: The incident occurred in July 2026, during a time that Nissan was receiving a near daily stream of false alerts due a telematics error. Nissan has since remedied the telematics issue, but was not been able to confirm the accuracy of this previously transmitted report until August [XXX], 2026 |
| 10039-15589 v2 | Level 2 | BMW of North America, LLC | 2026-06 14:06 | Whitney Point, NY | 2026 BMW X6 | Verified Engaged | Animal | No Injured Reported | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15322 | Level 2 | Tesla, Inc. | 2026-06 13:47 | Secaucus, NJ | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 65 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15323 | Level 2 | Tesla, Inc. | 2026-06 05:07 | Chattanooga, TN | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 53 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15324 | Level 2 | Tesla, Inc. | 2026-06 12:37 | Greenwich, CT | 2025 TESLA Model S | Verified Engaged | Unknown | Unknown | 19 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15325 | Level 2 | Tesla, Inc. | 2026-06 22:05 | Baton Rouge, LA | 2021 TESLA Model Y | Verified Engaged | Unknown | Unknown | 27 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15326 | Level 2 | Tesla, Inc. | 2026-06 13:14 | Olympia, WA | 2025 TESLA Model Y | Verified Engaged | Other, see Narrative | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15327 | Level 2 | Tesla, Inc. | 2026-06 15:56 | Waco, TX | 2024 TESLA Model Y | Verified Engaged | Van | Unknown | 10 | Traffic Circle | Redacted by NHTSA as confidential business information |
| 13781-15328 | Level 2 | Tesla, Inc. | 2026-06 17:06 | Mira Loma, CA | 2022 TESLA Model Y | Verified Engaged | Unknown | Unknown | 57 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15329 | Level 2 | Tesla, Inc. | 2026-06 18:50 | Reno, NV | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 43 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15330 | Level 2 | Tesla, Inc. | 2026-06 22:41 | Houston, TX | 2023 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 15 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-15331 | Level 2 | Tesla, Inc. | 2026-06 00:49 | Henderson, NY | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 31 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15333 | Level 2 | Tesla, Inc. | 2026-06 00:06 | Sparks, NV | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 43 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15334 | Level 2 | Tesla, Inc. | 2026-06 06:53 | Scotts Valley, CA | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 42 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15335 | Level 2 | Tesla, Inc. | 2026-06 06:49 | Lansing, IL | 2018 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15336 | Level 2 | Tesla, Inc. | 2026-06 16:49 | Detroit, MI | 2018 TESLA Model 3 | Verified Engaged | SUV | Unknown | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15337 | Level 2 | Tesla, Inc. | 2026-06 19:31 | Fuquay-Varina, NC | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 28 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15338 | Level 2 | Tesla, Inc. | 2026-06 21:28 | Holmdel, NJ | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 19 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15339 | Level 2 | Tesla, Inc. | 2026-06 21:26 | Los Angeles, CA | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 11 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15340 | Level 2 | Tesla, Inc. | 2026-06 16:43 | Kirkland, WA | 2026 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 13 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-15342 | ADS | Tesla, Inc. | 2026-06 14:32 | Austin, TX | 2026 TESLA Model Y | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Parking Lot | [Summary: The Tesla ADS was proceeding straight in a parking lot behind an SUV. As the SUV came to stop, the ADS came to a stop behind the SUV. The SUV proceeded to reverse and made contact with the ADS's front. The ADS …[Summary: The Tesla ADS was proceeding straight in a parking lot behind an SUV. As the SUV came to stop, the ADS came to a stop behind the SUV. The SUV proceeded to reverse and made contact with the ADS's front. The ADS had one passenger present in the vehicle.] |
| 13781-15367 | Level 2 | Tesla, Inc. | 2026-06 10:56 | Waxhaw, NC | 2026 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 38 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15368 | Level 2 | Tesla, Inc. | 2026-06 01:05 | Newport Coast, CA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 15 | Parking Lot | Redacted by NHTSA as confidential business information |
| 13781-15369 | Level 2 | Tesla, Inc. | 2026-06 11:48 | Rexford, NY | 2022 TESLA Model Y | Verified Engaged | Unknown | Unknown | 23 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15370 | Level 2 | Tesla, Inc. | 2026-06 12:25 | Melbourne, FL | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-15371 | Level 2 | Tesla, Inc. | 2026-06 14:43 | Milford, MA | 2020 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15372 | Level 2 | Tesla, Inc. | 2026-06 16:17 | Tampa, FL | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 39 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15375 | Level 2 | Tesla, Inc. | 2026-06 16:16 | Itasca, IL | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 64 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15376 | Level 2 | Tesla, Inc. | 2026-06 21:52 | Atlanta, GA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 24 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15377 | Level 2 | Tesla, Inc. | 2026-06 22:01 | Castaic, CA | 2024 TESLA Model Y | Verified Engaged | SUV | Unknown | 71 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15378 | Level 2 | Tesla, Inc. | 2026-06 23:54 | Indio, CA | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 57 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15379 | Level 2 | Tesla, Inc. | 2026-06 04:44 | Arcadia, CA | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 48 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15380 | Level 2 | Tesla, Inc. | 2026-06 08:02 | Stockton, CA | 2024 TESLA Model X | Verified Engaged | Other Fixed Object | Unknown | 80 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15381 | Level 2 | Tesla, Inc. | 2026-06 09:41 | Vancouver, WA | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 47 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15382 | Level 2 | Tesla, Inc. | 2026-06 12:48 | Johnstown, PA | 2026 TESLA Model Y | Verified Engaged | SUV | Unknown | 21 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-15383 | Level 2 | Tesla, Inc. | 2026-06 15:25 | Sacramento, CA | 2022 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 47 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15384 | Level 2 | Tesla, Inc. | 2026-06 19:43 | Albany, NY | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 42 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15385 | Level 2 | Tesla, Inc. | 2026-06 22:02 | Orlando, FL | 2026 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 11 | Street | Redacted by NHTSA as confidential business information |
| 13781-15386 | Level 2 | Tesla, Inc. | 2026-06 22:52 | Tomball, TX | 2023 TESLA Model X | Verified Engaged | Pickup Truck | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15408 | Level 2 | Tesla, Inc. | 2026-06 03:08 | Pacific, WA | 2024 TESLA Cybertruck | Verified Engaged | Pickup Truck | Unknown | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15409 | Level 2 | Tesla, Inc. | 2026-06 15:36 | Vassar, MI | 2023 TESLA Model 3 | Verified Engaged | SUV | Unknown | 1 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-15410 | Level 2 | Tesla, Inc. | 2026-06 15:54 | San Francisco, CA | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15411 | Level 2 | Tesla, Inc. | 2026-06 16:52 | MN | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-15412 | Level 2 | Tesla, Inc. | 2026-06 17:26 | Midvale, UT | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 77 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15413 | Level 2 | Tesla, Inc. | 2026-06 19:15 | Glenview, IL | 2024 TESLA Model S | Verified Engaged | Unknown | Unknown | 34 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15414 | Level 2 | Tesla, Inc. | 2026-06 20:09 | Argyle, TX | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 7 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15415 | Level 2 | Tesla, Inc. | 2026-06 21:11 | Costa Mesa, CA | 2026 TESLA Model Y | Verified Engaged | Pickup Truck | Unknown | 7 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-15416 | Level 2 | Tesla, Inc. | 2026-06 22:35 | Union City, CA | 2016 TESLA Model X | Verified Engaged | Unknown | Unknown | 26 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15417 | Level 2 | Tesla, Inc. | 2026-06 01:55 | Little Elm, TX | 2021 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 18 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15418 | Level 2 | Tesla, Inc. | 2026-06 03:01 | Charlotte, NC | 2026 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 26 | Street | Redacted by NHTSA as confidential business information |
| 13781-15419 | Level 2 | Tesla, Inc. | 2026-06 03:52 | Lancaster, PA | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 44 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15420 | Level 2 | Tesla, Inc. | 2026-06 04:45 | Bloomingdale, IL | 2020 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 20 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-15421 | Level 2 | Tesla, Inc. | 2026-06 09:13 | San Francisco, CA | 2019 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15422 | Level 2 | Tesla, Inc. | 2026-06 09:39 | Columbia, CA | 2020 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 15 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-15423 | Level 2 | Tesla, Inc. | 2026-06 09:30 | Grapevine, TX | 2023 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15424 | Level 2 | Tesla, Inc. | 2026-06 16:38 | Miami, FL | 2021 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15426 | Level 2 | Tesla, Inc. | 2026-06 17:30 | Forked River, NJ | 2026 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 22 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15427 | Level 2 | Tesla, Inc. | 2026-06 18:52 | Biloxi, MS | 2024 TESLA Model Y | Verified Engaged | SUV | Unknown | 25 | Street | Redacted by NHTSA as confidential business information |
| 13781-15428 | Level 2 | Tesla, Inc. | 2026-06 23:45 | Grand Prairie, TX | 2024 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15429 | Level 2 | Tesla, Inc. | 2026-06 23:34 | Grand Prairie, TX | 2025 TESLA Cybertruck | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15430 | Level 2 | Tesla, Inc. | 2026-06 03:10 | Canterbury, NH | 2016 TESLA Model S | Verified Engaged | Animal | Unknown | 76 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15431 | Level 2 | Tesla, Inc. | 2026-06 09:31 | Hollywood, FL | 2025 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15432 | Level 2 | Tesla, Inc. | 2026-06 10:36 | Lancaster, SC | 2025 TESLA Model Y | Verified Engaged | Pole / Tree | Unknown | 45 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-15433 | Level 2 | Tesla, Inc. | 2026-06 11:26 | Red Oak, TX | 2024 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15434 | Level 2 | Tesla, Inc. | 2026-06 13:08 | Plano, TX | 2024 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15435 | Level 2 | Tesla, Inc. | 2026-06 17:18 | Floyd County, GA | 2019 TESLA Model 3 | Verified Engaged | Other, see Narrative | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15436 | Level 2 | Tesla, Inc. | 2026-06 19:42 | Charlotte, NC | 2026 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 3 | Street | Redacted by NHTSA as confidential business information |
| 13781-15437 | Level 2 | Tesla, Inc. | 2026-06 00:18 | Riverside, CA | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 52 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15438 | Level 2 | Tesla, Inc. | 2026-06 01:04 | San Jose, CA | 2021 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 47 | Street | Redacted by NHTSA as confidential business information |
| 13781-15439 | Level 2 | Tesla, Inc. | 2026-06 02:40 | Edgewater, NJ | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 17 | Street | Redacted by NHTSA as confidential business information |
| 13781-15440 | Level 2 | Tesla, Inc. | 2026-06 07:15 | Nashville, TN | 2023 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15441 | Level 2 | Tesla, Inc. | 2026-06 16:46 | Delray Beach, FL | 2018 TESLA Model X | Verified Engaged | SUV | Unknown | 61 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15442 | Level 2 | Tesla, Inc. | 2026-06 19:04 | Houston, TX | 2019 TESLA Model X | Verified Engaged | Passenger Car | Unknown | 80 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15443 | Level 2 | Tesla, Inc. | 2026-06 20:52 | Atlanta, GA | 2023 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-15444 | Level 2 | Tesla, Inc. | 2026-06 21:01 | Silverado, CA | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-15445 | Level 2 | Tesla, Inc. | 2026-06 00:00 | Lawrenceville, GA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 7 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-15446 | Level 2 | Tesla, Inc. | 2026-06 00:40 | Saint Paul, MN | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 24 | Unknown | 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.