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 2101 to 2200.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-14511 | ADS | Waymo LLC | 2026-03 17:04 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On March [XXX], 2026 at 5:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near the westbound Interstate [XXX] on and off-ramps. …On March [XXX], 2026 at 5:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near the westbound Interstate [XXX] on and off-ramps. The Waymo AV was traveling northbound in the second from the right lane on [XXX] when it began to slow in a queue of traffic for a red light at the intersection with the westbound Interstate [XXX] on and off-ramps. While the Waymo AV was slowing, a passenger car traveling northbound in the rightmost lane changed lanes to the left and entered the second from the right lane, behind the Waymo AV. The Waymo AV slowed to a stop behind the queue of traffic as the passenger car continued to again change lanes to the left, entering the adjacent left lane, and as the passenger car proceeded to change lanes, the front right side of the passenger car made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger car sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-14512 | ADS | Waymo LLC | 2026-03 05:43 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 0 | Street | On March [XXX], 2026 at 5:43 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing west in the …On March [XXX], 2026 at 5:43 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing west in the second from the right lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a pickup truck facing east in the rightmost lane on eastbound [XXX] proceeded into the intersection, at a low rate of speed and crossed the double yellow lane lines into westbound [XXX], and the front left side of the pickup truck made contact with the front left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-14514 | ADS | Waymo LLC | 2026-03 15:49 | Tempe, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 20 | Street | On March [XXX], 2026 at 3:49 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a curb on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the right lane on […On March [XXX], 2026 at 3:49 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a curb on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the right lane on [XXX] when it began to slow and maneuver to the right, towards the south curb, and the front right tire of the Waymo AV made contact with the south curb. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-14558 | ADS | Waymo LLC | 2026-03 11:34 | Santa Monica, CA | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 0 | Street | On March [XXX], 2026 at 11:34 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped in-lane facing …On March [XXX], 2026 at 11:34 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped in-lane facing northwest on a narrow portion of [XXX]. While the Waymo AV was stopped, a pickup truck initially stopped directly behind the Waymo AV attempted to pass the Waymo AV to the left, and the front right side of the pickup truck made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-14566 | ADS | Waymo LLC | 2026-03 22:13 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 17 | Intersection | On March [XXX], 2026 at 10:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound o…On March [XXX], 2026 at 10:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the second to the left designated left turn lane as it approached a yellow light at the intersection with [XXX]. As the Waymo AV entered the intersection with [XXX] and initiated a left turn, a passenger car that was traveling in the adjacent leftmost designated left turn lane crossed the solid white lane line, into the Waymo AV's lane of travel, and the front right side of the passenger car made contact with the front left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-14577 | ADS | Waymo LLC | 2026-03 19:26 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 1 | Street | On March [XXX], 2026 at 7:26 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near[XXX]. The Waymo AV was traveling southeastbound on a nar…On March [XXX], 2026 at 7:26 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near[XXX]. The Waymo AV was traveling southeastbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions when it slowed to a stop to yield to a passenger car stopped in-lane facing southeast. While the Waymo AV was stopped, a pickup truck traveling northwestbound slowed to a stop to the left of the Waymo AV and an SUV traveling southwestbound on [XXX] turned left onto southeastbound [XXX]t and stopped behind the Waymo AV. The Waymo AV then began to reverse, detecting there was not sufficient room to proceed forward. As the Waymo AV was reversing, the SUV proceeded forward, and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-14625 | ADS | Waymo LLC | 2026-03 19:27 | Washington, DC | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Minor W/O Hospitalization | 4 | Street | On March [XXX], 2026 at 7:27 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in the rightmost lan…On March [XXX], 2026 at 7:27 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in the rightmost lane on [XXX] when it began to slow for an emergency vehicle siren from an ambulance traveling northbound. While the Waymo AV was slowing, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30413-14624 | ADS | May Mobility | 2026-03 10:18 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 6 | Intersection | On March [XXX], 2026, at 10:18 am, a third-party vehicle collided with a May Mobility Autonomous Vehicle (Ego) in Arlington, Texas, at the intersection of [XXX] and [XXX]. The May Ego was traveling north on [XXX], making…On March [XXX], 2026, at 10:18 am, a third-party vehicle collided with a May Mobility Autonomous Vehicle (Ego) in Arlington, Texas, at the intersection of [XXX] and [XXX]. The May Ego was traveling north on [XXX], making a right turn at a yield sign onto eastbound [XXX]. with its automated driving system engaged in autonomy mode. The May Ego stopped at the yield sign then held its position in order to confirm its prediction that an oncoming vehicle was not making a left turn across the ego's path. The third-party vehicle, traveling north on [XXX] behind the Ego, failed to stop at the yield sign and rear-ended the Ego. Vehicle telematics confirm the Autonomous Vehicle Operator intervened using the accelerator to avoid the collision; however, the collision was unavoidable. |
| 30610-14263 | ADS | Zoox, Inc. | 2026-03 00:55 | Las Vegas, NV | 2024 ZOOX Zoox | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 5 | Street | An occupied Zoox autonomous vehicle traveling southeast on [XXX] stopped behind traffic in the outer left turn lane (lane #2) for a red traffic signal at [XXX] in Las Vegas. A dumpster-hauling truck (Vehicle 2) was stop…An occupied Zoox autonomous vehicle traveling southeast on [XXX] stopped behind traffic in the outer left turn lane (lane #2) for a red traffic signal at [XXX] in Las Vegas. A dumpster-hauling truck (Vehicle 2) was stopped in the adjacent through-lane (lane #3). Shortly after the light turned green and the Zoox vehicle began its left turn, the Vehicle 2 operator abruptly steered left, accelerated, and cut into the Zoox vehicle's path, violating its right of way. The Zoox vehicle braked hard; however, Vehicle 2 struck the Zoox vehicle's right-side front wheel, fender, roof-mounted sensor unit, and body panel. The Zoox vehicle was towed from the scene and sustained moderate damage. No injuries were reported, and police were not called. |
| 30610-14264 | ADS | Zoox, Inc. | 2026-03 06:57 | Austin, TX | 2019 TOYOTA Highlander | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 2 | Street | A Zoox vehicle operating in autonomous mode, traveling southwest on [XXX] towards [XXX] in Austin, was slowing for a garbage truck (Vehicle 2) approaching from the opposite direction when Vehicle 2 struck it head-on. The…A Zoox vehicle operating in autonomous mode, traveling southwest on [XXX] towards [XXX] in Austin, was slowing for a garbage truck (Vehicle 2) approaching from the opposite direction when Vehicle 2 struck it head-on. The Zoox vehicle sustained moderate damage to the left front area, including the hood, bumper, headlight, fender, A-pillar hinge, and driver door. Both parties exchanged information. Police were notified and arrived at the scene. No injuries were reported. |
| 30610-14342 | ADS | Zoox, Inc. | 2026-03 10:57 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 25 | Street | An unoccupied Zoox autonomous vehicle was traveling northeast on [XXX], approaching [XXX] in Las Vegas, when a passenger car (Vehicle 2) abruptly turned right onto [XXX] from a parking lot on the right, violating the Zoo…An unoccupied Zoox autonomous vehicle was traveling northeast on [XXX], approaching [XXX] in Las Vegas, when a passenger car (Vehicle 2) abruptly turned right onto [XXX] from a parking lot on the right, violating the Zoox vehicle's right-of-way. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The Zoox vehicle's right front fender and wheel, and its right rear door panel, contacted Vehicle 2's left fender, wheel, headlight, and quarter panel. Both vehicles sustained damage, and the Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified. |
| 30610-14366 | ADS | Zoox, Inc. | 2026-03 15:03 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | SUV | Property Damage. No Injured Reported | 5 | Parking Lot | An occupied Zoox autonomous vehicle was traveling east at low speed in a parking lot along [XXX] in Las Vegas when an SUV (Vehicle 2) began reversing out of its parking spot. The Zoox vehicle slowed and attempted to stee…An occupied Zoox autonomous vehicle was traveling east at low speed in a parking lot along [XXX] in Las Vegas when an SUV (Vehicle 2) began reversing out of its parking spot. The Zoox vehicle slowed and attempted to steer left, but it could not before Vehicle 2 struck the Zoox vehicle's right-side rear door, body panel, and wheel. The Zoox vehicle sustained moderate damage and was towed from the scene. No injuries were reported, and police were not notified. |
| 30610-14388 | ADS | Zoox, Inc. | 2026-03 14:12 | San Francisco, CA | 2026 ZOOX Zoox | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | An unoccupied Zoox autonomous vehicle (Vehicle 1), traveling southwest on [XXX] in San Francisco, was stopped mid-way through a lane-change maneuver (from lane #2 to lane #1) in stop-and-go traffic, when a passenger car …An unoccupied Zoox autonomous vehicle (Vehicle 1), traveling southwest on [XXX] in San Francisco, was stopped mid-way through a lane-change maneuver (from lane #2 to lane #1) in stop-and-go traffic, when a passenger car (Vehicle 2) in lane #1 accelerated toward the stopped Zoox vehicle and struck its left front wheel. The Zoox vehicle was towed from the scene for inspection and was found to have sustained no damage. Vehicle 2's front bumper appears to have sustained minor damage. No injuries were reported. Police were notified but did not arrive at the scene. The Zoox vehicle's video footage shows that Vehicle 2's driver was not looking at the road ahead before or at the time of contact. |
| 30610-14419 | ADS | Zoox, Inc. | 2026-03 19:27 | San Francisco, CA | 2026 ZOOX Zoox | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | A Zoox autonomous vehicle, traveling west on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Just after the passenger entered the Zoox vehicle, a pas…A Zoox autonomous vehicle, traveling west on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Just after the passenger entered the Zoox vehicle, a passenger car (Vehicle 2) traveling behind attempted to pass on the left and swiped the Zoox vehicle's left rear fender. The Zoox vehicle was towed from the scene and was found to have sustained minor damage. No injuries were reported, and police were not notified. |
| 30610-14519 | ADS | Zoox, Inc. | 2026-03 15:30 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Intersection | An unoccupied Zoox autonomous vehicle started to move after a gradual stop at a 3-way stop sign preparing to turn right onto eastbound [XXX] in Las Vegas, when it braked to an abrupt stop as cross-traffic failed to stop …An unoccupied Zoox autonomous vehicle started to move after a gradual stop at a 3-way stop sign preparing to turn right onto eastbound [XXX] in Las Vegas, when it braked to an abrupt stop as cross-traffic failed to stop and yield the right-of-way. It was then rear ended by an SUV (Vehicle 2) traveling directly behind. The Zoox vehicle was towed from the scene and was found to have sustained moderate damage to the rear. No injuries were reported and police were not notified. Camera footage from the Zoox vehicle shows that the Vehicle 2 driver was not looking ahead at the roadway before the time of contact. |
| 30610-14554 | ADS | Zoox, Inc. | 2026-03 11:24 | Miami, FL | 2019 TOYOTA Highlander | Verified Engaged | Heavy Truck | Unknown | 17 | Street | A Zoox vehicle in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching…A Zoox vehicle in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching Zoox vehicle. The door struck the Zoox vehicle's right-side A-pillar, windshield, and sensor assembly. After the impact, the trailer's door rebounded and struck the operator behind it. The Zoox vehicle operator then disengaged from autonomous mode. The police and emergency personnel arrived at the scene. The operator was transported by an ambulance from the scene. |
| 30610-14662 | ADS | Zoox, Inc. | 2026-03 22:23 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Street | An unoccupied Zoox autonomous vehicle was stopped at a LasVegas PUDO location when an SUV (Vehicle 2), that was stopped behind for passenger pick up, attempted to pass on the left and lightly swiped the left rear corner …An unoccupied Zoox autonomous vehicle was stopped at a LasVegas PUDO location when an SUV (Vehicle 2), that was stopped behind for passenger pick up, attempted to pass on the left and lightly swiped the left rear corner of the Zoox vehicle. The Vehicle 2 driver did not stop at the scene to exchange information. The Zoox vehicle resumed operation to return to base for inspection, where it was found to have sustained minor damage. There were no reported injuries. |
| 30610-14663 | ADS | Zoox, Inc. | 2026-03 21:14 | San Francisco, CA | 2019 TOYOTA Highlander | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling west on [XXX] past [XXX] in San Francisco when it encountered a Pickup truck reversing into its lane from a perpendicular parking spot ahead. The Zoox…A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling west on [XXX] past [XXX] in San Francisco when it encountered a Pickup truck reversing into its lane from a perpendicular parking spot ahead. The Zoox vehicle slowed to a stop, and while it waited for the lane to clear, a passenger car (Vehicle 2) began to reverse. The Zoox vehicle honked at Vehicle 2, but Vehicle 2 continued to reverse and made contact at low speed with the passenger-side front door of the Zoox vehicle. The Zoox vehicle operator then disengaged from autonomous mode. Both vehicles sustained damage. No injuries were reported, and the police were not notified. |
| 30610-14664 | ADS | Zoox, Inc. | 2026-03 18:13 | San Francisco, CA | 2026 ZOOX Zoox | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | An unoccupied Zoox autonomous vehicle (Vehicle 1), traveling northeast on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Shortly after, one of the p…An unoccupied Zoox autonomous vehicle (Vehicle 1), traveling northeast on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Shortly after, one of the parked vehicles (Vehicle 2) was attempting to pull out of the parking spot when the Zoox vehicle's passenger approached and activated its doors. The Zoox vehicle's right rear door contacted Vehicle 2's front bumper. The right rear door on the Zoox vehicle was damaged; no injuries were reported, and police were not notified. |
| 30610-14665 | ADS | Zoox, Inc. | 2026-03 21:18 | San Francisco, CA | 2017 TOYOTA Highlander | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | A Zoox vehicle (Vehicle 1) operating in autonomous mode was stopped behind traffic in the through lane on westbound [XXX] at a red traffic light at [XXX] in San Francisco with a passenger car (Vehicle 2), stopped directl…A Zoox vehicle (Vehicle 1) operating in autonomous mode was stopped behind traffic in the through lane on westbound [XXX] at a red traffic light at [XXX] in San Francisco with a passenger car (Vehicle 2), stopped directly ahead. After both vehicles were fully stopped, Vehicle 2 began moving backward toward the still-stopped Zoox vehicle, and even though the Zoox vehicle honked its horn, Vehicle 2 continued to move backward and made contact with the Zoox vehicle's front bumper. The Zoox vehicle operator then disengaged from autonomy. The Zoox vehicle sustained minor damage. No injuries were reported, and police were not notified. |
| 30792-14655 | ADS | WeRide Corp | 2026-03 11:46 | San Jose, CA | 2024 NISSAN Ariya Hatchback | Verified Engaged | Pickup Truck | No Injured Reported | 0 | Street | On the morning of March [XXX], 2026, at approximately 11:46 a.m., a WeRide autonomous vehicle (Vehicle 1) was traveling along [XXX] in San Jose, California, proceeding straight in the second lane from the left as it appr…On the morning of March [XXX], 2026, at approximately 11:46 a.m., a WeRide autonomous vehicle (Vehicle 1) was traveling along [XXX] in San Jose, California, proceeding straight in the second lane from the left as it approached the intersection with [XXX]. Operating in autonomous mode, the vehicle came to a complete stop at a red traffic signal. While stopped, Vehicle 1 was struck from behind by a white 2012 Chevrolet Colorado pickup truck (Vehicle 2), whose driver failed to stop in time. Immediately following the collision, the In-vehicle safety operator of Vehicle 1 disengaged autonomous mode and assessed the situation. Both drivers then relocated their vehicles to a safe area nearby, where they exchanged information and performed a visual inspection of the damage. The damage to both vehicles was minor in nature. Vehicle 1 sustained a small scratch to its rear bumper, while Vehicle 2 sustained a corresponding minor scratch to its front bumper. No injuries were reported by either party, and emergency services were not requested. |
| 31101-14200 | ADS | Avride Inc. | 2026-03 12:33 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 5 | Street | On March [XXX], 2026 at 12:33 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was parked in the right lane facing southeast in autonomous mode on …On March [XXX], 2026 at 12:33 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was parked in the right lane facing southeast in autonomous mode on [XXX] waiting to pick up robotaxi passengers. [XXX] is part of a construction zone with cones being used to separate contraflow traffic lanes. The AVRIDE AV proceeded to drive forward after the robotaxi passengers were not permitted to enter the AVRIDE AV due to exceeding the passenger limit. As the AVRIDE AV began driving foward, an SUV entered the left line into opposing traffic in an attempt to pass the AVRIDE AV. While in the process of passing the AVRIDE AV, the SUV abruptly had to switch back to the right lane due to oncoming traffic. While moving back to the right lane, the rear right of the SUV made contact with the front left of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-14203 | ADS | Avride Inc. | 2026-03 08:08 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 2 | Street | On March [XXX], 2026 at 8:08 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was heading southwestbound on [XXX] in autonomous …On March [XXX], 2026 at 8:08 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was heading southwestbound on [XXX] in autonomous mode when it stopped at a stop sign before planning to turn left onto [XXX]. While the AVRIDE AV was beginning to turn left, the AVRIDE AV noticed an SUV approaching from the left and hesitated. The safety operator decided to then take over in manual mode, stopping the AVRIDE AV and reversing it. Before the AVRIDE AV began to travel in reverse, a Jeep which was at the stop sign behind the AVRIDE AV also began to proceed into the intersection without stopping at the stop sign. This resulted in the back of the AVRIDE AV making contact with the front of the Jeep. After the collision, the Jeep fled from the scene without stopping to speak with anyone. The AVRIDE AV sustained damage. No injuries were reported. |
| 31101-14286 | ADS | Avride Inc. | 2026-03 08:04 | Austin, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 22 | Street | On March [XXX], 2026 at 8:04 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on[XXX] near [XXX]. The AVRIDE AV was driving southeastbound in autonomous mode on [XXX] in the right la…On March [XXX], 2026 at 8:04 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on[XXX] near [XXX]. The AVRIDE AV was driving southeastbound in autonomous mode on [XXX] in the right lane. While the AVRIDE AV was driving straight ahead, an SUV began to enter traffic from a parking lot on the right side of the road without properly stopping, cutting off the AVRIDE AV. This resulted in left front of the SUV making contact with the right front of the AVRIDE AV. Both vehicles sustained damage. The AVRIDE AV required a tow. No injuries were reported. |
| 31101-14328 | ADS | Avride Inc. | 2026-03 13:48 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 27 | Street | On March [XXX], 2026 at 1:48 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX]and [XXX]. The AVRIDE AV was traveling westbound in autonomous mode on [XXX]…On March [XXX], 2026 at 1:48 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX]and [XXX]. The AVRIDE AV was traveling westbound in autonomous mode on [XXX] in the left lane approaching a traffic light at the intersection with [XXX]. The traffic light was changing from red to green as the AVRIDE AV approached the intersection. As the AVRIDE AV approached the intersection, an SUV on [XXX] in the right lane attempted to switch over two lanes and turn left onto [XXX]. This maneuver resulted in the left front of the SUV making contact with the right side of the AVRIDE AV. Both vehicles sustained damage. Both vehicles required a tow. No injuries were reported. |
| 31101-14418 | ADS | Avride Inc. | 2026-03 14:03 | Austin, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Intersection | On March [XXX], at 2:03 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was stopped facing northwest on [XXX] in autonomous mode, waiting to take …On March [XXX], at 2:03 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was stopped facing northwest on [XXX] in autonomous mode, waiting to take a right turn onto [XXX]. As the AVRIDE AV was waiting for traffic to clear to make the right turn, an SUV traveling northeastbound on [XXX] swerved right at the last minute and proceeded to drive directly towards the AVRIDE AV. This resulted in the front of the SUV making contact with the left side of the AVRIDE AV. Both vehicles sustained damage. Driver side airbags were deployed on the AVRIDE AV. Airbags were not deployed for the SUV. A tow was required for the AVRIDE AV. No tow was required for the SUV. No injuries were reported. |
| 31101-14509 | ADS | Avride Inc. | 2026-03 12:52 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 19 | Street | On March [XXX], 2026, at 12:52 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southeastbound on [XXX] in autonomous mode. As the AV…On March [XXX], 2026, at 12:52 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southeastbound on [XXX] in autonomous mode. As the AVRIDE AV drove straight ahead, an SUV on the right side of [XXX] from [XXX] began to turn right onto [XXX]. There was a stop sign on [XXX] that the SUV ignored before turning right onto [XXX].. This resulted in the left front of the SUV making contact with the right front of the AVRIDE AV. Both vehicles sustained damage. Both vehicles required a tow. No injuries were reported. |
| 31101-14518 | ADS | Avride Inc. | 2026-03 17:30 | Austin, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 11 | Intersection | On March [XXX], 2026 at 5:30 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound on [XXX] in autonomou…On March [XXX], 2026 at 5:30 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound on [XXX] in autonomous mode as it stopped at the red light at the intersection with [XXX]. As the light turned green, the AVRIDE AV began to enter the intersection to make a left hand turn. As the AVRIDE AV entered the intersection, a pickup truck also entered the intersection from the left on [XXX]. The pickup truck went against traffic rules and drove through the red light on [XXX] before proceeding into the intersection. This maneuver resulted in the front of the pickup truck making contact with the left side of the AVRIDE AV. The pickup truck drove away from the scene immediately after the incident. Both vehicles sustained damage. No injuries were reported. The AVRIDE AV required a tow. |
| 31101-14647 v2 | ADS | Avride Inc. | 2026-03 15:54 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other, see Narrative | No Injured Reported | 29 | Street | On March [XXX], 2026 at 3:54 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was driving northeastbound in the right lane on [XXX] in autonomous m…On March [XXX], 2026 at 3:54 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was driving northeastbound in the right lane on [XXX] in autonomous mode when it approached a traffic sign laying down in the right lane. Upon noticing the sign, the AVRIDE AV moved into the left lane. While moving into the left lane, the right front of the AVRIDE AV made contact with the road sign. The AVRIDE AV sustained minor damage. No injuries were reported. |
| 31101-14649 | ADS | Avride Inc. | 2026-03 13:26 | Austin, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | Van | No Injured Reported | 0 | Street | On March [XXX], 2026 at 1:26 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was facing northeast in autonomous mode while stopped at the red ligh…On March [XXX], 2026 at 1:26 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was facing northeast in autonomous mode while stopped at the red light on [XXX] at the intersection with [XXX]. While stopped at the red light, a van slowly approached the AVRIDE AV from behind. The front of the van then made light contact with the rear of the AVRIDE AV. Neither vehicle sustained damage. No injuries were reported. |
| 31101-14650 | ADS | Avride Inc. | 2026-03 15:41 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other, see Narrative | No Injured Reported | 23 | Street | On March [XXX], 2026 at 3:41 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in autonomous mode on [XXX] in the right lan…On March [XXX], 2026 at 3:41 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in autonomous mode on [XXX] in the right lane when it approached a road sign lying down in the middle of the right lane. As the AVRIDE AV proceeded straight ahead, the front of the AVRIDE AV made contact with the road sign which was already lying down on the road. The AVRIDE AV sustained minor damage. The road sign did not sustain damage. No injuries were reported. |
| 31101-14651 | ADS | Avride Inc. | 2026-03 22:12 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 22 | Intersection | On March [XXX], 2026 at 10:12 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in autonomous mode on [XXX] in the center l…On March [XXX], 2026 at 10:12 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in autonomous mode on [XXX] in the center lane entering the intersection with [XXX] after the red light turned green. The AVRIDE AV proceeded straight as it entered the intersection. Simultaneously, a passenger car in the left lane next to the AVRIDE AV entered the intersection and attempted to switch into the right lane, violating traffic line rules. This resulted in the right side of the passenger car making contact with the left side of the AVRIDE AV. Both vehicles sustained minor cosmetic damage. No injuries were reporte |
| 31101-14652 | ADS | Avride Inc. | 2026-03 10:23 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other, see Narrative | No Injured Reported | 13 | Intersection | On March [XXX], 2026, at 10:23 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound on [XXX] in autonom…On March [XXX], 2026, at 10:23 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound on [XXX] in autonomous mode approaching the intersection with [XXX] with a safety driver behind the wheel. As the AVRIDE AV approached the green light at the intersection, the AVRIDE AV planned to continue driving straightforward through the intersection. While entering the intersection, the safety driver took over the vehicle in manual mode and took a left turn onto the left lane on [XXX]. The right lane on [XXX] was blocked off by a temporary traffic control sign. As the safety driver made the left hand turn, the right front of the AVRIDE AV made contact with the traffic sign. The AVRIDE AV sustained minor damage. The traffic sign sustained zero damage. No injuries were reported. |
| 31101-14653 | ADS | Avride Inc. | 2026-03 13:44 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 24 | Street | On March [XXX], 2026 at 1:44 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling northbound in the right lane on [XXX] in autonomous mod…On March [XXX], 2026 at 1:44 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling northbound in the right lane on [XXX] in autonomous mode driving straightforward through the green light at the intersection with [XXX]. After the AVRIDE AV made it through the intersection, a passenger vehicle driving alongside the AVRIDE AV in the left lane on [XXX] attempted to make a last second right hand turn over two lanes into a parking garage. This maneuver resulted in the right side of the passenger vehicle to make contact with the left front of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-14654 | ADS | Avride Inc. | 2026-03 08:07 | Austin, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | Animal | Property Damage. No Injured Reported | 15 | Street | On March [XXX], 2026 at 8:07 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling northwestbound on [XXX] in autonomous mode when it appr…On March [XXX], 2026 at 8:07 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling northwestbound on [XXX] in autonomous mode when it approached a duck lying down in the road. As the AVRIDE AV proceeded straight ahead, it made contact with the duck. This collision resulted in the death of the duck. The AVRIDE AV did not sustain damage. No other injuries were reported. |
| 34971-14386 | Level 2 | Wayve.ai | 2026-03 17:28 | Sunnyvale, CA | 2023 FORD Mustang Mach-E | Verified Not Engaged | Passenger Car | Property Damage. No Injured Reported | 20 | Highway / Freeway | The subject vehicle was traveling northbound in lane 2 on a multi-lane highway when traffic ahead and in an adjacent lane began to slow. The vehicle was operating with Level 2 ADAS features engaged. Approximately 4 seco…The subject vehicle was traveling northbound in lane 2 on a multi-lane highway when traffic ahead and in an adjacent lane began to slow. The vehicle was operating with Level 2 ADAS features engaged. Approximately 4 seconds prior to the collision, the safety operator disengaged the ADAS and applied manual braking in response to slowing traffic, reducing the vehicle's speed to approximately 18-20 mph. A Mazda MX-5 was traveling directly behind the subject vehicle, with a Lexus SUV traveling behind the Mazda. The Lexus SUV subsequently collided with the rear of the Mazda MX-5. This resulted in a chain-reaction collision in which the Mazda MX-5 was propelled forward and struck the rear of the subject vehicle. The subject vehicle sustained minor rear-end damage and remained operable. The Mazda MX-5 sustained front and rear damage. The Lexus SUV sustained front-end damage and experienced airbag deployment. Emergency services were contacted following the collision, and law enforcement responded to the scene. No injuries were reported by occupants of the subject vehicle at the time of the incident. |
| 35021-16400 | ADS | MOIA America LLC | 2026-03 11:55 | Orlando, FL | 2023 Volkswagen ID.Buzz | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 9 | Parking Lot | On March [XXX], 2026, in Orlando, Florida, a MOIA America autonomous test vehicle ("MOIA AV") made contact with a curb while completing a left turn. The MOIA AV was operating on a curved section of roadway within the [XX…On March [XXX], 2026, in Orlando, Florida, a MOIA America autonomous test vehicle ("MOIA AV") made contact with a curb while completing a left turn. The MOIA AV was operating on a curved section of roadway within the [XXX] medical campus during validation testing of a new map release. While following the curve through the left turn, the rear driver-side wheel made contact with the adjacent curb. At the time of contact, the MOIA AV's automated driving system was engaged. The MOIA AV sustained abrasion along the rim lip of the rear driver-side wheel. No other vehicle, pedestrian, cyclist, or other road user was involved. No damage to third-party property was identified and no injuries were reported. MOIA America is reporting this crash under Request No. 2 of Standing General Order 2021-01. MOIA America may supplement or correct this report with additional information as it becomes available. This curb contact event initially was not identified as a property damage crash requiring SGO reporting. However, during a recent internal review of past incidents, this incident was escalated for further analysis of its reportability. On August 25, 2026, MOIA America spoke with NHTSA to seek clarification about this incident. NHTSA indicated its opinion that the incident should be reported, so MOIA America is submitting this report in accordance with that guidance. |
| 502-14241 | Level 2 | Ford Motor Company | 2026-03 07:42 | Dodge City, AL | 2026 FORD Explorer | Verified Engaged | Animal | No Injured Reported | 74 | Highway / Freeway | On March [XXX], 2026, at approximately 7:42 AM, an incident occurred involving a Ford Explorer traveling southbound in a heavily wooded area on [XXX] near Dodge City, south of exit [XXX]. The driver reported that a deer …On March [XXX], 2026, at approximately 7:42 AM, an incident occurred involving a Ford Explorer traveling southbound in a heavily wooded area on [XXX] near Dodge City, south of exit [XXX]. The driver reported that a deer entered the roadway from the oncoming lane, having jumped a fence, and subsequently ran in front of the vehicle. At the time of the incident, the vehicle's BlueCruise system was engaged. The driver reported the vehicle impacted with the deer on the left front corner of the vehicle. This impact resulted in the deployment of the knee airbag and damage to the headlamp. There were no reported injuries. Ford has confirmed that the Explorer is equipped with Co-Pilot 360 Active 2.0 including BlueCruise. Telemetry data confirms L2 engagement at the time of the collision. |
| 502-14293 | Level 2 | Ford Motor Company | 2026-03 11:13 | Lebanon Junction, KY | 2026 LINCOLN Aviator | Verified Engaged | Other Fixed Object | Minor W/O Hospitalization | 78 | Highway / Freeway | On March [XXX], 2026, at approximately 11:13 AM, a Lincoln Aviator was involved in an incident while traveling on [XXX] South near exit [XXX]. The driver alleged she was traveling at 78 mph with BlueCruise engaged when h…On March [XXX], 2026, at approximately 11:13 AM, a Lincoln Aviator was involved in an incident while traveling on [XXX] South near exit [XXX]. The driver alleged she was traveling at 78 mph with BlueCruise engaged when her leg contacted the steering wheel, causing the vehicle to steer and impact the center steel highway guardrail. According to the driver, airbags deployed, and a rear-row passenger was later treated at the hospital for a concussion. Ford's investigation confirmed the Aviator is equipped with Co-Pilot 360 Drive 2.0, including Adaptive Cruise Control (ACC), Lane Centering Assist (LCA), and BlueCruise. Telemetry connected vehicle data was retrieved, and Ford's initial analysis shows: 1) BlueCruise was engaged at the time of the incident; 2) the vehicle was traveling at a pre-collision speed of 78 mph; 3) the vehicle experienced a non-system initiated leftward steer input of 39 degrees resulting in impact with the steel guardrail; 4) side and curtain airbags deployed; and 5) a rightward steer input of 94 degrees was recorded after the impact. The initial rapid leftward angle change at a high vehicle speed (78 mph) far exceeds the steering input capabilities of the BlueCruise system. Ford's investigation is ongoing. |
| 502-14437 v2 | Level 2 | Ford Motor Company | 2026-03 19:34 | Broadview Heights, OH | 2025 FORD F-150 | Verified Engaged | Other Fixed Object | Minor W/O Hospitalization | 61 | Highway / Freeway | Update on Report [XXX]: Ford has received the police report regarding this incident. The report attributes the accident to an improper lane change by a semi-truck, which reportedly forced the F-150 to swerve off the road…Update on Report [XXX]: Ford has received the police report regarding this incident. The report attributes the accident to an improper lane change by a semi-truck, which reportedly forced the F-150 to swerve off the roadway and collide with a concrete median barrier. The report documents that tire marks on the roadway supported the driver's statement that he swerved to avoid the truck. Additionally, the report notes cloudy weather conditions and states that the driver reported minor injuries but declined emergency medical services at the scene. Ford has obtained physical access to the vehicle and extracted the Event Data Recorder (EDR) data from the Restraint Control Module (RCM) and the Image Processing Module A (IPMA). This data confirms that: (1) the driver's seatbelt was recorded as 'Unbelted' at the time of the event; (2) Adaptive Cruise Control (ACC) was active; (3) the driver applied manual leftward steering input, resulting in an impact with a concrete barrier; and (4) the driver's frontal and knee airbags deployed. Both the police report and the RCM EDR data confirm that the steering event was initiated by the driver's manual steering input in an attempt to avoid an encroaching semi-truck. |
| 502-14658 v3 | Level 2 | Ford Motor Company | 2026-03 07:41 | Bloomington, IN | 2025 FORD Explorer | Alleged Engaged | Other Fixed Object | Serious W/ Hospitalization | 66 | Highway / Freeway | Update on Report [XXX]: Ford has reviewed the EDR data obtained from the subject vehicle's Restraint Control Module (RCM). This review yielded no new material information beyond what was previously identified in the pol…Update on Report [XXX]: Ford has reviewed the EDR data obtained from the subject vehicle's Restraint Control Module (RCM). This review yielded no new material information beyond what was previously identified in the police-recovered RCM EDR report. Additionally, Ford successfully captured the Image Processing Module A (IPMA). The IPMA EDR data indicates that Level 2 ADAS features were not engaged two seconds prior to the collision. Furthermore, the Camera Module Rear (CMR) did not capture any data, which is consistent with an inactive Level 2 state, as the CMR is designed to record data only when Level 2 features are active. Based on the physical module data retrieved, Ford is unable to confirm whether any Level 2 ADAS features were active within the 30-second window prior to the incident. |
| 540-14273 v2 | Level 2 | General Motors, LLC | 2026-03 21:11 | Louisville, KY | 2023 GMC Sierra | Verified Engaged | Other Fixed Object | No Injured Reported | 50 | Highway / Freeway | On March [XXX], 2026, a 2023 GMC Sierra was traveling westbound on [XXX] in Louisville, Kentucky, with Super Cruise engaged and active. Crash data indicated a left side impact that resulted in deployment of the airbag an…On March [XXX], 2026, a 2023 GMC Sierra was traveling westbound on [XXX] in Louisville, Kentucky, with Super Cruise engaged and active. Crash data indicated a left side impact that resulted in deployment of the airbag and front seat belt pretensioners. The driver was wearing a seat belt at the time of the crash. Review of the OnStar audio recording indicates that the driver alleged the vehicle jerked laterally, the driver overcorrected, after which the vehicle impacted the highway retaining wall. The driver reported that no injuries were sustained. Telematics data shows that Super Cruise changed to Disabled/Not Ready 3 second prior to the crash due to a FCA event. Update: Corrected the date above to March [XXX], 2026. Initial submission had March [XXX], 2026 in the narrative. |
| 540-14288 | Level 2 | General Motors, LLC | 2026-03 22:37 | Seaside, OR | 2024 CHEVROLET Silverado | Verified Engaged | Other, see Narrative | No Injured Reported | 56 | Highway / Freeway | On March [XXX], 2026, a 2024 Chevrolet Silverado was traveling eastbound on [XXX] in Seaside, Oregon, with Super Cruise engaged and active. Crash data indicated a frontal impact that resulted in deployment of the driver …On March [XXX], 2026, a 2024 Chevrolet Silverado was traveling eastbound on [XXX] in Seaside, Oregon, with Super Cruise engaged and active. Crash data indicated a frontal impact that resulted in deployment of the driver front airbag and front seat belt pretensioners. The driver was wearing a seat belt at the time of the crash. Review of the OnStar audio recording indicates that the driver alleged departing the highway into a ditch after swerving to avoid a deer. Telematics data shows that Super Cruise changed state to Disabled/Not Ready at the time of the crash due driver take over with steering control and brake press. |
| 540-14347 | Level 2 | General Motors, LLC | 2026-03 00:56 | Hawthorne, FL | 2021 CADILLAC Escalade | Verified Engaged | Heavy Truck | No Injured Reported | 57 | Highway / Freeway | On March [XXX], 2026, a 2021 Cadillac Escalade was traveling southeast on [XXX] near Hawthorne, Florida, with Super Cruise engaged and active. Crash data recorded a frontal impact that resulted in deployment of the airba…On March [XXX], 2026, a 2021 Cadillac Escalade was traveling southeast on [XXX] near Hawthorne, Florida, with Super Cruise engaged and active. Crash data recorded a frontal impact that resulted in deployment of the airbag and front seat belt pretensioners. The driver was wearing a seat belt at the time of the crash. In a review of the OnStar audio recording, the driver refers to the ADAS system as "autopilot" and indicates he was using the system and the vehicle jerked to the left while he was reaching to get a drink. The driver indicated the vehicle crossed the median and struck a tractor trailer. He reported no injuries. System data shows that Super Cruise changed to an Override state 3 seconds prior to the crash due to driver applied steering torque. Super Cruise changed to a Disabled/Not Ready state 1.5 seconds prior to the crash due to driver applied braking. |
| 540-14353 v2 | Level 2 | General Motors, LLC | 2026-03 17:11 | Arlington, VA | 2024 CADILLAC Lyriq | Verified Engaged | Unknown | Unknown | 71 | Highway / Freeway | On March [XXX], 2026, a 2024 Cadillac LYRIQ was traveling north on [XXX], near Arlington, VA, with Super Cruise engaged and active. Crash data recorded a frontal impact that resulted in deployment of the airbag and front…On March [XXX], 2026, a 2024 Cadillac LYRIQ was traveling north on [XXX], near Arlington, VA, with Super Cruise engaged and active. Crash data recorded a frontal impact that resulted in deployment of the airbag and front seat belt pretensioners. The driver was wearing a seat belt at the time of the crash. The driver did not respond to calls from OnStar. System data shows that Super Cruise changed to a Degraded Escalation state 1 second prior to the crash. Update: Corrected narrative to read "traveling north on [XXX]..." The original narrative stated southeast. |
| 540-14451 | Level 2 | General Motors, LLC | 2026-03 12:57 | Perrysburg, OH | 2025 CHEVROLET Blazer | Verified Engaged | Other Fixed Object | Unknown | 17 | Highway / Freeway | On March [XXX], 2026, a 2025 Chevrolet Blazer EV was traveling eastbound on [XXX] in Perrysburg, Ohio, with Super Cruise engaged and active. Crash data indicated a left impact occurred that deployed the front seat belt …On March [XXX], 2026, a 2025 Chevrolet Blazer EV was traveling eastbound on [XXX] in Perrysburg, Ohio, with Super Cruise engaged and active. Crash data indicated a left impact occurred that deployed the front seat belt pretensioners and driver airbag. The driver was not wearing their seat belt at the time of the crash. Review of the OnStar audio recording indicates that the driver reports they were involved in a single-vehicle crash in a construction zone, in which the vehicle impacted the center highway barrier and subsequently came to rest on the opposite side of the roadway. System data shows that Super Cruise changed to Disabled/Not Ready 5 seconds prior to the incident. Per system design, this state change is due to the driver taking control of the vehicle due to a brake press or hand on the wheel. |
| 540-14487 | Level 2 | General Motors, LLC | 2026-03 21:02 | Stillwater, OK | 2026 CADILLAC CT5 | Verified Engaged | Unknown | Unknown | 49 | Intersection | On March [XXX], 2026, a 2026 Cadillac CT5 was traveling eastbound on [XXX] near Stillwater, Oklahoma. Crash data recorded a left side impact that resulted in deployment of the airbags and front seat belt pretensioners. T…On March [XXX], 2026, a 2026 Cadillac CT5 was traveling eastbound on [XXX] near Stillwater, Oklahoma. Crash data recorded a left side impact that resulted in deployment of the airbags and front seat belt pretensioners. The driver and passenger were wearing their seat belts at the time of the crash. A review of the OnStar audio recording indicates the subject vehicle was going through a traffic signal controlled intersection when a vehicle turning left in the opposite direction hit the driver's side of the subject vehicle. System data shows that Super Cruise changed state to "Enabled' 16 seconds before incident due to a driver take over. |
| 540-14489 | Level 2 | General Motors, LLC | 2026-03 07:00 | Jupiter, FL | 2026 CADILLAC CT5 | Verified Engaged | Other Fixed Object | Unknown | 68 | Highway / Freeway | On March [XXX], 2026, a 2026 Cadillac CT5 was traveling southbound on [XXX] in Jupiter, Florida with Super Cruise engaged and active. Crash data recorded a front-left impact that resulted in deployment of the driver airb…On March [XXX], 2026, a 2026 Cadillac CT5 was traveling southbound on [XXX] in Jupiter, Florida with Super Cruise engaged and active. Crash data recorded a front-left impact that resulted in deployment of the driver airbag and front seat belt pretensioners. Crash data also indicates the driver was not wearing a seat belt at the time of the crash. In a review of the OnStar audio recording, the driver indicates they struck a guard rail after the vehicle swerved to the left. An officer on the scene that witnessed the incident confirmed that the vehicle swerved to the left. No injuries were reported. |
| 669-14892 | Level 2 | Hyundai Motor America | 2026-03 04:30 | Lula, GA | 2025 HYUNDAI Tucson | Alleged Engaged | Other, see Narrative | Moderate W/ Hospitalization | 40 | Highway / Freeway | A Hyundai consumer reported operating a 2025 Tucson vehicle with what they allege as "Auto Drive" and "Lane Assist" features engaged. According to the customer's statement, after exiting a main road and making a left tur…A Hyundai consumer reported operating a 2025 Tucson vehicle with what they allege as "Auto Drive" and "Lane Assist" features engaged. According to the customer's statement, after exiting a main road and making a left turn, they continued driving with the following features active: Speed setting engaged Lane keeping function enabled Hands reportedly on the steering wheel The customer alleges that shortly thereafter, the vehicle began to depart from the roadway without warning. The customer alleges attempting to correct the vehicle's path by steering, at which point the vehicle lost control, rolled over multiple times, and ultimately came to rest approximately 40 feet down an embankment. The customer stated that a police report is available from the Georgia State Patrol with a number of [XXX]. |
| 669-16295 | Level 2 | Hyundai Motor America | 2026-03 17:19 | Lula, GA | 2025 HYUNDAI Tucson | Verified Engaged | Other, see Narrative | Unknown | 55 | Highway / Freeway | According to the EDR data, the vehicle was traveling at approximately 55 mph with Smart Cruise Control (SCC) engaged and Lane Following Assist (LFA) engaged. The EDR data indicates that LFA remained active from five sec…According to the EDR data, the vehicle was traveling at approximately 55 mph with Smart Cruise Control (SCC) engaged and Lane Following Assist (LFA) engaged. The EDR data indicates that LFA remained active from five seconds prior to the collision until approximately 2.5 seconds before impact, at which time driver steering input and accelerator pedal input were detected. Following those inputs, LFA steering assistance was no longer active. The EDR data further indicates that a steering input of approximately 105 degrees was recorded approximately 0.5 seconds prior to impact. The data also indicates subsequent Electronic Stability Control (ESC) intervention. According to the police report: "Vehicle #1 (Hyundai) was traveling west on [XXX]. Driver #1 (Hyundai consumer) stated his vehicle was in 'self drive mode'. While attempting to negotiate a curve, driver #1 failed to maintain his lane of travel, traveling off the north shoulder. After leaving the roadway, driver #1 over corrected causing vehicle #1 to rotate counter clockwise. After doing so, vehicle #1 struck a sharp curve sign with the front of the vehicle. After impact vehicle #1 continued west off the north shoulder traveling down an embankment. After doing so vehicle #1 overturned. Vehicle #1 came to an uncontrolled final rest off the north shoulder facing west, upright." Photographs of the vehicle and the police report are available and can be provided upon request. |
| 753-15460 v2 | Level 2 | Kia America, Inc. | 2026-03 02:35 | Ukiah, CA | 2026 KIA Carnival | Alleged Engaged | Other Fixed Object | Moderate W/ Hospitalization | 75 | Highway / Freeway | **6/13/2026 5-Day Report** On June [XXX], 2026, the customer called Kia's Customer Care Center to complain about a Kia dealer that had been nonresponsive to the customer's requests for warranty related information. Duri…**6/13/2026 5-Day Report** On June [XXX], 2026, the customer called Kia's Customer Care Center to complain about a Kia dealer that had been nonresponsive to the customer's requests for warranty related information. During that discussion, the customer reported she been in an accident involving her 2026 MY Kia Carnival on March 18, 2026 and that the vehicle caused her to swerve into a bridge. The customer stated that "as soon as I got off the freeway [XXX], I put on the cruise control and I put on the lane assist, and while I was driving something took over the wheel, like the electrical system took over or something, the wheel spun out of control. I tried to do from the right lane into the left, and something took control of the car, and it crashed into the bridge." The customer stated that she was traveling 75mph. As a result of the crash, the customer reported she suffered from a concussion and had pain in her chest, abdomen and stomach and was transported directly to the hospital. The customer stated that Smart Cruise Control, Lane Following Assist and Highway Driving Assist were on while "driving on [XXX] and on local streets." The customer reported the vehicle had been repaired by a third-party facility. The customer requested that Kia pay off her vehicle. The subject Kia Carnival is equipped with Lane Following Assist ("LFA"), Smart Cruise Control ("SCC") and Highway Driving Assist (HDA). LFA is a supplemental system that helps to detect lane markings and/or vehicles on the road and assists the driver's steering to help keep the vehicle between lanes. SCC is a supplemental system that detects a vehicle ahead and can help maintain the distance from the vehicle ahead and the set speed. The functionality of LFA and SCC are contingent upon several outside factors, and it is always the responsibility of the driver to safely steer the vehicle, to maintain the vehicle in its lane, and to maintain the vehicle's speed. HDA is a supplemental system that helps maintain a set distance and speed from the vehicle ahead when driving on certain highways and helps keep the vehicle between lanes while driving. In addition, HDA may not be able to recognize all traffic situations and may not detect possible collisions due to limitations of the system. **8/17/2026 Monthly (August) Update Report** On July [XXX], 2026, KA read the ACU for the subject Kia Carnival, which showed that the incident did not meet the threshold for the EDR to record an event. The damage observed to the vehicle is consistent with a minor scraping impact with a guard rail or barrier, which may not trigger a recordable event for the EDR given the lack of severe contact. Therefore, KA cannot further assess the customer's ADAS allegations. |
| 945-14508 | Level 2 | Nissan North America, Inc. | 2026-03 00:09 | Cleveland, OH | 2023 NISSAN Ariya Hatchback | Verified Engaged | Unknown | Unknown | 57 | 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.0 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.0 was involved in an incident involving an air bag deployment. The system was active in "hands-off" mode within 30 seconds of the incident. Nissan is currently examining its ability to provide additional details that may be protected by consumer privacy laws. Nissan has not been contacted regarding this incident. |
| 945-14515 | Level 2 | Nissan North America, Inc. | 2026-03 15:22 | Arlington, VA | 2023 NISSAN Ariya Hatchback | Verified Engaged | Unknown | Unknown | 3 | 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.0 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.0 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 examining its ability to provide additional details that may be protected by consumer privacy laws. Nissan has not been contacted regarding this incident. |
| 10039-14855 | Level 2 | BMW of North America, LLC | 2026-02 06:44 | Dover, DE | 2023 BMW i4 | Verified Engaged | Heavy Truck | Moderate W/O Hospitalization | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1243-14245 | Level 2 | Subaru of America, Inc. | 2026-02 | Spring, TX | 2021 SUBARU Outback | Alleged Engaged | Other, see Narrative | Minor W/ Hospitalization | 70 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-13992 | Level 2 | Tesla, Inc. | 2026-02 03:42 | Boca Raton, FL | 2022 TESLA Model X | Verified Engaged | Unknown | Unknown | 27 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-13993 | Level 2 | Tesla, Inc. | 2026-02 13:33 | Cherry Valley, IL | 2016 TESLA Model X | Verified Engaged | Unknown | Unknown | 65 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-13994 | Level 2 | Tesla, Inc. | 2026-02 01:47 | Waverly, AL | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 74 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-13995 | Level 2 | Tesla, Inc. | 2026-02 19:49 | Chester Springs, PA | 2023 TESLA Model X | Verified Engaged | Unknown | Unknown | 24 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-13996 | Level 2 | Tesla, Inc. | 2026-02 15:38 | Benicia, CA | 2021 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 51 | Street | Redacted by NHTSA as confidential business information |
| 13781-13997 | Level 2 | Tesla, Inc. | 2026-02 22:03 | Pratt, KS | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 39 | Unpaved Road | Redacted by NHTSA as confidential business information |
| 13781-14014 | Level 2 | Tesla, Inc. | 2026-02 21:00 | Cotati, CA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 71 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14015 | Level 2 | Tesla, Inc. | 2026-02 16:19 | Hawthorne, CA | 2025 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 27 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14016 | Level 2 | Tesla, Inc. | 2026-02 05:12 | Walnut, CA | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14017 | Level 2 | Tesla, Inc. | 2026-02 03:50 | Davenport, FL | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-14030 | Level 2 | Tesla, Inc. | 2026-02 00:34 | Talladega, AL | 2021 TESLA Model S | Verified Engaged | SUV | Unknown | 25 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14031 | Level 2 | Tesla, Inc. | 2026-02 00:18 | Blakely, GA | 2018 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 53 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14032 | Level 2 | Tesla, Inc. | 2026-02 01:27 | Irvine, CA | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 71 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14033 | Level 2 | Tesla, Inc. | 2026-02 05:12 | Mesa, AZ | 2025 TESLA Model 3 | Verified Engaged | SUV | Unknown | 24 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14034 | Level 2 | Tesla, Inc. | 2026-02 15:03 | Jones Mills, PA | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 79 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14035 | Level 2 | Tesla, Inc. | 2026-02 16:25 | New Orleans, LA | 2024 TESLA Model 3 | Verified Engaged | SUV | Unknown | 23 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14036 | Level 2 | Tesla, Inc. | 2026-02 18:09 | Millbrae, CA | 2025 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14037 | Level 2 | Tesla, Inc. | 2026-02 19:13 | Charlestown, MA | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14038 | Level 2 | Tesla, Inc. | 2026-02 23:55 | Chico, CA | 2023 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 18 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14039 | Level 2 | Tesla, Inc. | 2026-02 03:55 | Monterey, CA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 30 | Street | Redacted by NHTSA as confidential business information |
| 13781-14040 | Level 2 | Tesla, Inc. | 2026-02 13:46 | Carlsbad, CA | 2025 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 49 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14041 | Level 2 | Tesla, Inc. | 2026-02 13:43 | Manchaca, TX | 2022 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 50 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14042 | Level 2 | Tesla, Inc. | 2026-02 15:19 | Riverside, CA | 2026 TESLA Model X | Verified Engaged | Unknown | Unknown | 16 | Street | Redacted by NHTSA as confidential business information |
| 13781-14049 | Level 2 | Tesla, Inc. | 2026-02 02:48 | Chicago, IL | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 56 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14050 | Level 2 | Tesla, Inc. | 2026-02 04:26 | Banning, CA | 2025 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 59 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14051 | Level 2 | Tesla, Inc. | 2026-02 04:15 | Boxborough, MA | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 16 | Street | Redacted by NHTSA as confidential business information |
| 13781-14053 | Level 2 | Tesla, Inc. | 2026-02 20:42 | Irvine, CA | 2025 TESLA Cybertruck | Verified Engaged | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14054 | Level 2 | Tesla, Inc. | 2026-02 02:51 | Broomfield, CO | 2025 TESLA Model Y | Verified Engaged | SUV | Unknown | 22 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14055 | Level 2 | Tesla, Inc. | 2026-02 06:57 | Santa Clara, CA | 2023 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 25 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14056 | Level 2 | Tesla, Inc. | 2026-02 09:28 | Forney, TX | 2023 TESLA Model X | Verified Engaged | Pickup Truck | Unknown | 32 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14057 | Level 2 | Tesla, Inc. | 2026-02 14:58 | San Diego, CA | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14058 | Level 2 | Tesla, Inc. | 2026-02 19:19 | Thousand Oaks, CA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 64 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14059 | Level 2 | Tesla, Inc. | 2026-02 16:45 | Plover, WI | 2025 TESLA Model X | Verified Engaged | Unknown | Unknown | 66 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14060 | Level 2 | Tesla, Inc. | 2026-02 04:22 | McHenry, IL | 2025 TESLA Model 3 | Verified Engaged | Pole / Tree | Unknown | 41 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-14084 | Level 2 | Tesla, Inc. | 2026-02 04:43 | Sugar Land, TX | 2021 TESLA Model 3 | Verified Engaged | Other, see Narrative | Unknown | 48 | Street | Redacted by NHTSA as confidential business information |
| 13781-14085 | Level 2 | Tesla, Inc. | 2026-02 13:50 | Los Angeles, CA | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 56 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14086 | Level 2 | Tesla, Inc. | 2026-02 19:01 | Salem, OR | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 23 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14087 | Level 2 | Tesla, Inc. | 2026-02 22:07 | Monticello, NY | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 51 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14088 | Level 2 | Tesla, Inc. | 2026-02 22:42 | Miami, FL | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14089 | Level 2 | Tesla, Inc. | 2026-02 09:21 | Modesto, CA | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 48 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14100 | Level 2 | Tesla, Inc. | 2026-02 02:27 | Arcadia, CA | 2018 TESLA Model 3 | Verified Engaged | Pickup Truck | Unknown | 21 | Street | Redacted by NHTSA as confidential business information |
| 13781-14101 | Level 2 | Tesla, Inc. | 2026-02 08:41 | Los Angeles, CA | 2025 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14102 | Level 2 | Tesla, Inc. | 2026-02 10:47 | Miami, FL | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-14103 | Level 2 | Tesla, Inc. | 2026-02 15:59 | CA | 2021 TESLA Model 3 | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-14104 | Level 2 | Tesla, Inc. | 2026-02 16:54 | Mountain View, CA | 2018 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 35 | Highway / Freeway | 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.