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 1801 to 1900.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-14907 | ADS | Waymo LLC | 2026-04 16:00 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 1 | Street | On April [XXX], 2026 at 4:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northeastboun…On April [XXX], 2026 at 4:00 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northeastbound in the leftmost lane on [XXX] and slowing to yield to a queue of stop-and-go traffic ahead. While the Waymo AV was slowing, a passenger car initially traveling directly behind the Waymo AV proceeded to pass the Waymo AV to the left by crossing the double yellow center line and entering the opposing lane of travel. As the passenger car was passing the Waymo AV, the right side of the passenger car made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-14928 | ADS | Waymo LLC | 2026-04 01:02 | Atlanta, GA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 1:02 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south after making a right…On April [XXX], 2026 at 1:02 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south after making a right turn from [XXX] onto [XXX], to yield to a queue of traffic stopped facing southwest on [XXX]. While the Waymo AV was stopped, an SUV facing southwest on [XXX], against the proper direction of traffic, and reversing along the south curb of [XXX] approached the Waymo AV from the front and to the right, and the rear right side of the SUV made contact with the front 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-14929 | ADS | Waymo LLC | 2026-04 22:18 | Austin, TX | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 25 | Street | On April [XXX], 2026 at 10:18 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound in the secon…On April [XXX], 2026 at 10:18 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound in the second from the right lane on [XXX] when it initiated a lane change to the rightmost lane. As the Waymo AV was completing the lane change, a passenger car traveling ahead of the Waymo AV in the second from the right lane initiated a right turn into a parking garage on the west side of [XXX]t and entered the Waymo AV's lane of travel. As the passenger car continued turning right, the front right side of the passenger car made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-14930 | ADS | Waymo LLC | 2026-04 17:03 | Atlanta, GA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 1 | Street | On April [XXX], 2026 at 5:03 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing south in the le…On April [XXX], 2026 at 5:03 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing south in the leftmost lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the light turned green, an SUV with its left turn signal activated for an unprotected left turn, in front of the Waymo AV proceeded forward momentarily and slowed to a stop to yield to northbound traffic on [XXX]. The Waymo AV proceeded forward at a low rate of speed, slowing as it yielded to the SUV. As the Waymo AV was proceeding forward, a passenger car initially stopped behind the Waymo AV proceeded forward, and the front of the passenger car 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-14931 | ADS | Waymo LLC | 2026-04 20:19 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | Van | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 8:19 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was parked facing west towards the nor…On April [XXX], 2026 at 8:19 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was parked facing west towards the north curb of [XXX], partially in-lane, with its hazard lights activated for a passenger dropoff. While the Waymo AV was parked, a van traveling westbound on [XXX] proceeded to pass the Waymo AV to the left, and the right side of the van made contact with the rear left side 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-14932 | ADS | Waymo LLC | 2026-04 15:04 | Phoenix, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 3:04 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing east in the seco…On April [XXX], 2026 at 3:04 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing east in the second from the right lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car initially stopped behind the Waymo AV proceeded forward, and the front of the passenger car made contact with the rear 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-14933 | ADS | Waymo LLC | 2026-04 00:39 | Paradise Valley, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 36 | Intersection | On April [XXX], 2026 at 12:39 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Paradise Valley, Arizona was in a collision involving debris on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the left …On April [XXX], 2026 at 12:39 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Paradise Valley, Arizona was in a collision involving debris on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the left lane on [XXX] and proceeding straight through the intersection with [XXX]. As the Waymo AV was approaching the exit of the intersection, the front left tire of the Waymo AV made contact with debris in the roadway. 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-14934 | ADS | Waymo LLC | 2026-04 00:22 | San Antonio, TX | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 12:22 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Antonio, Texas was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing east in the right lane…On April [XXX], 2026 at 12:22 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Antonio, Texas was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing east in the right lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the traffic light turned green, the Waymo AV proceeded forward momentarily and stopped as the SUV initially stopped in front of the Waymo AV began to reverse, and the rear of the SUV made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-14935 | ADS | Waymo LLC | 2026-04 08:33 | Austin, TX | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 21 | Street | On April [XXX], 2026 at 8:33 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] and p…On April [XXX], 2026 at 8:33 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] and passing a parked SUV on the north curb. As the Waymo AV was passing the SUV a passenger car west of the SUV reversed out of a driveway on the north side of [XXX] and entered the Waymo AV's path of travel, and the rear of the passenger car made contact with the right side 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-14936 | ADS | Waymo LLC | 2026-04 07:54 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 7:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a heavy truck with a flatbed trailer on [XXX] near [XXX]. The Waymo AV was st…On April [XXX], 2026 at 7:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a heavy truck with a flatbed trailer on [XXX] near [XXX]. The Waymo AV was stopped facing west on [XXX] in the right lane for a red light in a queue of traffic at the intersection with [XXX]. After the light turned green, and traffic advanced the Waymo AV remained stopped, as a heavy truck with an attached flatbed trailer in the adjacent left lane, and overlapping the Waymo AV's lane of travel proceeded to pass the Waymo AV on the left, and the right side of the heavy truck's flatbed trailer made contact with the rear 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-14937 | ADS | Waymo LLC | 2026-04 00:03 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 12:03 AM 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 stopped facing north in the sec…On April [XXX], 2026 at 12:03 AM 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 stopped facing north in the second from the left lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the light turned green, the Waymo AV proceeded forward momentarily, then slowed to a stop to yield to a passenger car stopped directly in front of the Waymo AV. While the Waymo AV was stopped, an SUV that was initially stopped behind the Waymo AV proceeded forward, and the front of the SUV made contact with the rear of the stationary 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-14940 | ADS | Waymo LLC | 2026-04 15:55 | Houston, TX | 2024 JAGUAR I-PACE | Alleged Engaged | Heavy Truck | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 3:55 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Houston, Texas was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was stopped facing north on [XXX] with it…On April [XXX], 2026 at 3:55 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Houston, Texas was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was stopped facing north on [XXX] with its right turn signal activated in a queue of traffic for a stop sign at the intersection with [XXX]. While the Waymo AV was stopped, a heavy truck that was stopped directly in front of the Waymo AV activated its hazard lights and reversed, and the rear right side of the heavy truck trailer 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. 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-14941 | ADS | Waymo LLC | 2026-04 11:50 | Gilbert, AZ | 2025 ZEEKR RT | Verified Not Engaged | Other Fixed Object | Property Damage. No Injured Reported | 21 | Traffic Circle | On April [XXX], 2026 at 11:50 AM MT (a Waymo Autonomous Vehicle ("Waymo AV") operating in Gilbert, Arizona was in a collision involving a curb on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it ap…On April [XXX], 2026 at 11:50 AM MT (a Waymo Autonomous Vehicle ("Waymo AV") operating in Gilbert, Arizona was in a collision involving a curb on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it approached the roundabout at the intersection with [XXX]. As the Waymo AV entered the roundabout the test driver transitioned to manual mode and continued traversing the roundabout counter-clockwise when the front left side tire of the Waymo AV made contact with the northside curb at the intersection. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. 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-14943 | ADS | Waymo LLC | 2026-04 23:53 | Atlanta, GA | 2024 JAGUAR I-PACE | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 32 | Street | On April [XXX], 2026 at 11:53 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a downed utility line on [XXX] near [XXX]. The Waymo AV was traveling westbound in …On April [XXX], 2026 at 11:53 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a downed utility line on [XXX] near [XXX]. The Waymo AV was traveling westbound in the left lane on [XXX] when it encountered a downed utility line hanging across the roadway. As the Waymo AV proceeded straight, the front of the Waymo AV made contact with the downed utility line. 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-14944 | ADS | Waymo LLC | 2026-04 16:37 | Atlanta, GA | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 2 | Street | On April [XXX], 2026 at 4:37 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] when …On April [XXX], 2026 at 4:37 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] when it slowed to a stop for a stop sign at the intersection with [XXX]. As the Waymo AV began to proceed forward, a passenger car traveling eastbound on [XXX] made contact with the rear of a pickup truck that was traveling eastbound directly behind the Waymo AV. The pickup truck was pushed forward, and the front of the pickup truck 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. All three 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-15300 | ADS | Waymo LLC | 2026-04 10:33 | Atlanta, GA | 2024 JAGUAR I-PACE | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 10:33 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling westbound in the right…On April [XXX], 2026 at 10:33 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling westbound in the rightmost lane of [XXX] when it activated its left turn signal, shifted partially into the second from the rightmost lane, and came to a stop for a red traffic light at the intersection with [XXX]. A heavy truck that had been stationary in the second from the rightmost lane then began to proceed slowly, and after the traffic light turned green, attempted to pass the stationary Waymo AV on the left. The right side of the heavy truck then 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. The Waymo AV sustained damage. Waymo became aware of the increased level of damage on May 26, 2026 after an additional review of damages. 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. |
| 30291-14538 | ADS | Nuro | 2026-04 11:50 | Santa Clara, CA | 2022 TOYOTA Prius | Verified Engaged | Motorcycle | No Injured Reported | 19 | Street | On April [XXX], 2026, Nuro was operating a Prius test vehicle in auto mode on [XXX], a street in Santa Clara, CA with a single travel lane in the direction of travel, when a motorcycle attempted to overtake the Nuro vehi…On April [XXX], 2026, Nuro was operating a Prius test vehicle in auto mode on [XXX], a street in Santa Clara, CA with a single travel lane in the direction of travel, when a motorcycle attempted to overtake the Nuro vehicle from behind. In so doing, the motorcyclist clipped the side of the Nuro vehicle, causing some minor property damage to the Nuro vehicle. The motorcyclist then pulled over to the side of the road, and both parties exchanged information. Neither the motorcyclist nor the occupants of the Nuro vehicle were injured, and law enforcement was not called to the scene. |
| 30410-14562 | ADS | Motional | 2026-04 16:42 | Las Vegas, NV | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other Fixed Object | No Injured Reported | 23 | Street | On April [XXX], 2026, at approximately 4:42 PM local time, a Motional autonomous vehicle [XXX] was traveling southbound on [XXX] approaching [XXX] in Las Vegas, Nevada. While proceeding within its lane of travel, the ve…On April [XXX], 2026, at approximately 4:42 PM local time, a Motional autonomous vehicle [XXX] was traveling southbound on [XXX] approaching [XXX] in Las Vegas, Nevada. While proceeding within its lane of travel, the vehicle encountered a piece of concrete debris located in the roadway. The vehicle subsequently struck the debris, resulting in a punctured front tire and damage to the vehicle's undercarriage. Following the impact, the safety driver brought the vehicle to a controlled stop and pulled over to the side of the roadway. Due to the damage to the tire, the vehicle was not drivable. A tow truck was requested and the vehicle was subsequently removed from the scene. |
| 30413-14938 | ADS | May Mobility | 2026-04 13:59 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Other, see Narrative | Minor W/ Hospitalization | 21 | Intersection | On April [XXX], 2026, at 1:59 pm EST, a third-party vehicle, John Deere UTV Crossover Gator Utility Vehicle, collided with a May Mobility Autonomous Vehicle (AV) in Atlanta, Georgia, at the intersection of [XXX] and [XXX…On April [XXX], 2026, at 1:59 pm EST, a third-party vehicle, John Deere UTV Crossover Gator Utility Vehicle, collided with a May Mobility Autonomous Vehicle (AV) in Atlanta, Georgia, at the intersection of [XXX] and [XXX]. The May Mobility AV was traveling south on [XXX] in Atlanta, Georgia approaching the intersection of [XXX] on a green traffic light, with its automated driving system engaged in autonomous mode. The third- party vehicle was traveling west on [XXX] approaching a red light at [XXX] when it ran the red light and proceeded into the intersection without slowing, making contact with the May Mobility AV. The May Mobility AV began to apply the brakes as the third- party vehicle started to run the red light. During the May Mobility AVâs braking, the telematics confirm that the Autonomous Vehicle Operator also started to intervene, moving the steering wheel to the right and braking more forcefully. The collision was unavoidable with the third-party vehicle making contact with the front left bumper and the driver side rear passenger door of the May Mobility AV. The May Mobility AV was towed from the scene. May Mobility is reporting this crash under Request No. 1 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. |
| 30413-15019 | ADS | May Mobility | 2026-04 18:28 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 0 | Street | On April [XXX], 2026, at 6:28 PM ET, a passenger car collided with a May Mobility Autonomous Vehicle (AV) operating in Atlanta, Georgia on [XXX] near [XXX]. The May Mobility AV was traveling east on [XXX] in the left lan…On April [XXX], 2026, at 6:28 PM ET, a passenger car collided with a May Mobility Autonomous Vehicle (AV) operating in Atlanta, Georgia on [XXX] near [XXX]. The May Mobility AV was traveling east on [XXX] in the left lane. A passenger car traveling east on [XXX] in the right lane proceeded to change lanes from the right lane to the left lane. The May Mobility AV Operator began braking before a pedestrian crosswalk, which had an activated Rectangular Rapid Flashing Beacon and the presence of a pedestrian waiting to cross. After changing lanes, the passenger car failed to brake and the front of the passenger car made contact with the rear of the May Mobility AV. At the time of impact, the May Mobility AV was in manual mode. The May Mobility AV sustained a significant puncture in the rear, lower bumper with scratches, the passenger car sustained scratches on the front bumper. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it may become available. |
| 30530-15027 | ADS | Aurora Operations, Inc. | 2026-04 14:08 | Sheffield, TX | 2024 PETERBILT 579 | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 59 | Highway / Freeway | At 14:08 CST on April [XXX], 2026 in Sheffield, Texas, an Aurora vehicle was traveling east on [XXX] at approximately 59 MPH while operating in autonomy. The Aurora vehicle was traveling straight in the lane. Other veh…At 14:08 CST on April [XXX], 2026 in Sheffield, Texas, an Aurora vehicle was traveling east on [XXX] at approximately 59 MPH while operating in autonomy. The Aurora vehicle was traveling straight in the lane. Other vehicles were present, including a camper trailer which was adjacent to the Aurora vehicle. The collision occurred when a loose awning from the adjacent camper trailer detached and struck the Aurora vehicle. Following the collision, the Aurora Driver pulled over to a safe location. The Aurora vehicle was driveable from the location. No injuries were reported. The Aurora vehicle sustained damage. Aurora will supplement or modify its reporting should additional relevant information become available. |
| 30610-14656 | ADS | Zoox, Inc. | 2026-04 21:02 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 21 | Street | An unoccupied Zoox autonomous vehicle was traveling north on [XXX] past [XXX] in Las Vegas when a passenger car (Vehicle 2) abruptly attempted to turn right onto [XXX] from a parking lot, violating the Zoox vehicle's rig…An unoccupied Zoox autonomous vehicle was traveling north on [XXX] past [XXX] in Las Vegas when a passenger car (Vehicle 2) abruptly attempted to turn right onto [XXX] from a parking lot, 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, wheel, and fascia contacted Vehicle 2's left-front bumper and headlight. Both vehicles sustained damage, and the Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified. |
| 30610-14732 | ADS | Zoox, Inc. | 2026-04 14:12 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 0 | Street | An unoccupied Zoox autonomous vehicle was in the left lane traveling north on [XXX] past [XXX] when it slowed for a tractor-trailer (vehicle 2) that was reversing from the roadway into a loading bay on the right side of …An unoccupied Zoox autonomous vehicle was in the left lane traveling north on [XXX] past [XXX] when it slowed for a tractor-trailer (vehicle 2) that was reversing from the roadway into a loading bay on the right side of the road. While reversing, the tractor-trailer swung over into the left lane, and the left side of Vehicle 2's trailer made contact with the stopped Zoox vehicle's front fascia and sensor pods. The Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified. |
| 30610-15062 | ADS | Zoox, Inc. | 2026-04 18:44 | San Francisco, CA | 2026 ZOOX Zoox | Verified Engaged | Passenger Car | Minor W/O Hospitalization | 0 | Street | An occupied Zoox autonomous vehicle traveling north on [XXX] was stopped for a signal at [XXX] in San Francisco, with a passenger vehicle (Vehicle 2) stopped directly behind it. As the light turned green, the Zoox vehicl…An occupied Zoox autonomous vehicle traveling north on [XXX] was stopped for a signal at [XXX] in San Francisco, with a passenger vehicle (Vehicle 2) stopped directly behind it. As the light turned green, the Zoox vehicle began to proceed but stopped for traffic and was rear ended by Vehicle 2. Vehicle 2's driver immediately left the scene without exchanging information. Shortly after, the Zoox vehicle proceeded straight and pulled over in the right lane adjacent to the bike lane, and the passengers exited. One passenger reported feeling "whiplash" but declined medical treatment. The police were notified. The Zoox vehicle sustained minor rear-end damage. |
| 30610-15063 | ADS | Zoox, Inc. | 2026-04 18:38 | San Francisco, CA | 2019 TOYOTA Highlander | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | A Zoox vehicle operating in autonomous mode was stopped behind traffic at a red signal on northbound [XXX] at [XXX] in San Francisco. At this time, a passenger vehicle (Vehicle 2) was reversing from a parking spot on the…A Zoox vehicle operating in autonomous mode was stopped behind traffic at a red signal on northbound [XXX] at [XXX] in San Francisco. At this time, a passenger vehicle (Vehicle 2) was reversing from a parking spot on the left side of the roadway. The Zoox vehicle honked at the approaching Vehicle 2, but Vehicle 2's rear end made contact with the Zoox vehicle's driver door. The Zoox vehicle operator then disengaged from autonomous mode. The Zoox vehicle sustained minor damage. No injuries were reported, and police were not notified. |
| 30610-15064 | ADS | Zoox, Inc. | 2026-04 00:30 | Las Vegas, NV | 2024 ZOOX Zoox | Verified Engaged | Passenger Car | Minor W/O Hospitalization | 0 | Street | An occupied Zoox autonomous vehicle, gradually slowed to a stop behind traffic on southbound [XXX] past [XXX] in Las Vegas, when it was rear ended by a passenger vehicle (Vehicle 2) traveling directly behind. The Zoox ve…An occupied Zoox autonomous vehicle, gradually slowed to a stop behind traffic on southbound [XXX] past [XXX] in Las Vegas, when it was rear ended by a passenger vehicle (Vehicle 2) traveling directly behind. The Zoox vehicle honked at the approaching Vehicle 2, but its driver failed to stop in time. Vehicle 2's driver left the scene without exchanging information. The Zoox vehicle did not sustain any damage. No injuries were reported at that time. Police were notified. One of the passengers later contacted Zoox support and stated, "I began experiencing significant neck pain consistent with a possible soft tissue injury." The passenger has not provided any documentation to Zoox regarding their alleged injury. |
| 30610-15065 | ADS | Zoox, Inc. | 2026-04 01:13 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 0 | Street | An unoccupied Zoox autonomous vehicle was preparing to turn right from a hotel driveway onto southbound [XXX] in Las Vegas, and came to a gradual stop to yield to cross traffic when it was rear ended by a pickup (Vehicle…An unoccupied Zoox autonomous vehicle was preparing to turn right from a hotel driveway onto southbound [XXX] in Las Vegas, and came to a gradual stop to yield to cross traffic when it was rear ended by a pickup (Vehicle 2) traveling directly behind. The Zoox vehicle honked at the approaching Vehicle 2, but Vehicle 2's driver failed to stop in time. Vehicle 2's driver then went around the stopped Zoox vehicle, briefly stopped in the right lane, activated their hazard lights, and then proceeded to leave the area. Upon inspection, the Zoox vehicle was found to have sustained moderate damage to its rear. No injuries were reported and police were not notified. |
| 30634-14991 | ADS | PlusAI Inc | 2026-04 03:59 | TX | 2020 KENWORTH T680 | Unknown - see Narrative | Other, see Narrative | Unknown | 64 | Highway / Freeway | The subject vehicle was traveling at 64mph in the center eastbound lane on [XXX] near [XXX], having recently passed a pickup truck (vehicle #2) towing a trailer in the right lane. A large piece of road debris in the rig…The subject vehicle was traveling at 64mph in the center eastbound lane on [XXX] near [XXX], having recently passed a pickup truck (vehicle #2) towing a trailer in the right lane. A large piece of road debris in the right lane caused vehicle #2 to slow and veer onto the right shoulder. A second piece of large road debris was observed by the subject vehicle's operator ("VO") in the center lane approximately 80 meters ahead of the subject vehicle. The VO took control of the truck and began to steer the subject vehicle to the right, but upon seeing vehicle #2 accelerating and re-entering the right lane from the shoulder, the VO instead steered the subject vehicle into the left lane. After passing the debris, the subject vehicle returned to the center lane and continued driving eastbound on the highway. A post-event review of the subject vehicle's cameras showed an ambulance with its emergency lights off (vehicle #3) was traveling in the left lane to the rear of the subject vehicle as the subject vehicle began entering the left lane. When the subject vehicle entered the left lane, vehicle #3 maneuvered onto the left shoulder and came to a stop alongside the median. The subject vehicle made no contact with vehicle #2 or vehicle #3. PlusAI has not been contacted by any road user with regard to this event. |
| 31101-14813 v2 | ADS | Avride Inc. | 2026-04 22:39 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 29 | Street | On April [XXX], 2026 at 10:39 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northbound on [XXX] in autonomous mode…On April [XXX], 2026 at 10:39 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northbound on [XXX] in autonomous mode as it approached the traffic light at the intersection with [XXX]. As the AVRIDE AV entered the intersection with the yellow light showing, a passenger car began to enter the intersection at the same time from the right side of the AVRIDE AV from [XXX]. The passenger car went against traffic rules by driving through a red light as it entered the intersection. This maneuver resulted in the front of the passenger car making contact with the right side of the AVRIDE AV. Both vehicles sustained severe damage. Minor injuries were reported. Both vehicles required a tow. The AVRIDE AV had its right side airbags deploy. Update: At the time of the incident, there was initial concern about minor injuries for the Avride safety driver. After follow up, it has been reported that no injuries took place and no medical attention was needed as of May 21, 2026. |
| 31101-14815 | ADS | Avride Inc. | 2026-04 23:47 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 11:47 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was stopped at a red light facing westbound on [XXX] in autonomous mode …On April [XXX], 2026 at 11:47 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was stopped at a red light facing westbound on [XXX] in autonomous mode behind an SUV. While stopped at the red light, a passenger car approached the AVRIDE AV from behind at high speeds without slowing down or breaking as it approached the red light. This maneuver from the passenger car resulted in the front of the passenger car making contact with the rear of the AVRIDE AV. The force from the collision caused the AVRIDE AV to move forward which resulted in the front of the AVRIDE AV also making contact with the rear of the SUV stopped in front of it at the red light. All 3 vehicles sustained damage. No injuries were reported. |
| 31101-14818 | ADS | Avride Inc. | 2026-04 13:44 | Austin, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 11 | Street | On April [XXX], 2026 at 1:44 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Austin, TX on [XXX] near [XXX]. The AVRIDE AV was traveling westbound in the right lane in autonomous mode on [XXX] in …On April [XXX], 2026 at 1:44 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Austin, TX on [XXX] near [XXX]. The AVRIDE AV was traveling westbound in the right lane in autonomous mode on [XXX] in when it approached a work truck which was blocking its path forward in the right lane. The AVRIDE AV signaled to switch to the left lane as it approached the stationary work truck blocking the right lane. While attempting to switch to the left lane, the left side of the AVRIDE AV made contact with the right side of a pickup truck which was driving straightforward in the left lane. Both vehicles sustained damage. No injuries were reported. |
| 31101-14871 | ADS | Avride Inc. | 2026-04 15:27 | Austin, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 0 | Street | On April [XXX], 2026 at 3:27 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Austin, TX on [XXX] near [XXX]. The AVRIDE AV was in autonomous mode facing northbound, fully stopped in a line of traf…On April [XXX], 2026 at 3:27 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Austin, TX on [XXX] near [XXX]. The AVRIDE AV was in autonomous mode facing northbound, fully stopped in a line of traffic waiting to turn left at the red light on [XXX]. The traffic light turned green momentarily, allowing a few cars to make the left hand turn, but turned red again by the time the AVRIDE AV approached the intersection. After the AVRIDE AV had fully stopped at the red light, a pickup truck approached the AVRIDE AV from behind but failed to stop. This maneuver resulted in the front of the pickup truck making contact with the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-14899 | ADS | Avride Inc. | 2026-04 08:01 | Austin, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Highway / Freeway | On April [XXX], 2026 at 8:01 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, TX on [XXX] near West [XXX]. The AVRIDE AV was traveling southbound on [XXX] in autonomous mode as it approach…On April [XXX], 2026 at 8:01 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, TX on [XXX] near West [XXX]. The AVRIDE AV was traveling southbound on [XXX] in autonomous mode as it approached a traffic light at the intersection with West [XXX]. A passenger car was traveling behind the AVRIDE AV as it approached the traffic light. As the AVRIDE AV approached the traffic light, the light changed from green, to yellow to red. The AVRIDE AV slowed down and stopped accordingly at the red light. The passenger car behind the AVRIDE AV attempted to slow down and stop at the red light but hydroplaned due to the roads being wet at the time. This caused the front of the passenger car to make contact with the rear of AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-14909 | ADS | Avride Inc. | 2026-04 17:47 | Dallas, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Parking Lot | On April [XXX], 2026 at 5:47 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southwestbound on [XXX] in autonomous mode behind an SU…On April [XXX], 2026 at 5:47 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southwestbound on [XXX] in autonomous mode behind an SUV when the SUV came to an abrupt stop. The AVRIDE AV also stopped behind the SUV when the SUV then immediately began to reverse after stopping. This maneuver by the SUV resulted in the rear of the SUV making contact with the front of the stationary AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-14923 | ADS | Avride Inc. | 2026-04 12:16 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 6 | Parking Lot | On April [XXX], 2026 at 12:16 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the [XXX] dropoff circle. The AVRIDE AV was traveling southbound in autonomous mode at slow speeds i…On April [XXX], 2026 at 12:16 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the [XXX] dropoff circle. The AVRIDE AV was traveling southbound in autonomous mode at slow speeds in the left lane as it entered the dropoff zone at the [XXX]. As the AVRIDE AV entered the dropoff zone, an SUV parked and unloading in the right lane had its rear left door open. The AVRIDE AV began to slowly proceed past the parked SUV when the right mirror of the AVRIDE AV made contact with the open rear door of the SUV. Both vehicles sustained minor cosmetic damage. No injuries were reported. |
| 31101-14924 | ADS | Avride Inc. | 2026-04 14:53 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Non-Motorist: Cyclist | Property Damage. No Injured Reported | 0 | Intersection | On April [XXX], 2026 at 2:54 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 southeastbound on [XXX] in autonomou…On April [XXX], 2026 at 2:54 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 southeastbound on [XXX] in autonomous mode when it stopped at a stop sign at the intersection with [XXX]. The AVRIDE AV was being trailed by an SUV. It was raining at the time. After stopping at the stop sign, the AVRIDE AV began to initiate a right hand turn onto [XXX]. As the AVRIDE AV began to turn right, a cyclist approached the AVRIDE AV from behind. The cyclist disobeyed traffic rules and passed the SUV which was behind the AVRIDE AV while also driving through the stop sign without stopping. While attempting to pass the AVRIDE AV, the cyclist lost control due to the slick roads from the rain as the cyclist approached the intersection. This maneuver resulted in the front of the cyclist making contact with the rear of the AVRIDE AV. The cyclist left the scene following the incident. No injuries were reported. The AVRIDE AV sustained damage. |
| 31101-14925 | ADS | Avride Inc. | 2026-04 12:21 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 23 | Street | On April [XXX], 2026 at 12:21 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] West near [XXX]. The AVRIDE AV was traveling southbound on [XXX] in the left lane in autonomou…On April [XXX], 2026 at 12:21 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] West near [XXX]. The AVRIDE AV was traveling southbound on [XXX] in the left lane in autonomous mode when it approached a work truck parked ahead in the left lane. As the AVRIDE AV approached the work truck, it moved into the middle lane to its right to avoid the truck. After the AVRIDE AV successfully moved to the middle lane, a pickup truck in the right lane began to merge into the middle lane as well, cutting off the AVRIDE AV. This maneuver resulted in the left side of the pickup truck making contact with the right front of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-14926 | ADS | Avride Inc. | 2026-04 07:37 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 18 | Street | On April [XXX], 2026 at 7:37 AM, 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 it approa…On April [XXX], 2026 at 7:37 AM, 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 it approached the intersection with [XXX]. The AVRIDE AV proceeded straight ahead as there is no stop sign at the intersection for vehicles traveling on [XXX]. As the AVRIDE AV approached the intersection, a passenger car was stopped at the stop sign on the right side of the road on [XXX]. When the AVRIDE AV entered the intersection, the passenger car entered the intersection at the last second resulting in the front of the passenger car making contact with the right side of the AVRIDE AV. Both vehicles sustained damage. No injuries were reported. |
| 31101-15016 | ADS | Avride Inc. | 2026-04 21:29 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | SUV | Property Damage. No Injured Reported | 1 | Street | On April [XXX], 2026 at 9:29 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the left lane on [XXX] in autonom…On April [XXX], 2026 at 9:29 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was involved in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the left lane on [XXX] in autonomous mode when it began to slow down and come to a stop while staying in the left lane. An SUV was traveling further behind the AVRIDE AV in the left lane and a pickup truck was traveling in the right lane alongside the SUV on [XXX]. As the SUV approached the AVRIDE AV, it moved to the right lane to go around the AVRIDE AV. This maneuver resulted in the right side of the SUV making contact with the left side of the pickup truck. Neither the SUV nor pickup truck made contact with the AVRIDE AV. The SUV and pickup truck sustained damage. The AVRIDE AV sustained no damage. No injuries were reported. |
| 34952-14990 | ADS | Stack AV | 2026-04 14:46 | Edgewood, NM | 2025 PETERBILT 579 | Verified Not Engaged | Heavy Truck | No Injured Reported | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 35021-16401 v2 | ADS | MOIA America LLC | 2026-04 12:42 | Orlando, FL | 2023 Volkswagen ID.Buzz | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 10 | Parking Lot | Other than a correction to the model year field, the content of this report remains unchanged from the initial report submitted on August [XXX], 2026 [Report ID 35021-16401-1]. On April [XXX], 2026, in Orlando, Florida…Other than a correction to the model year field, the content of this report remains unchanged from the initial report submitted on August [XXX], 2026 [Report ID 35021-16401-1]. On April [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 Lake Nona 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 to the outer rim lip and the spoke faces of the rear driver-side wheel, consistent with curb contact. 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 [XXX], 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. |
| 35021-16402 | ADS | MOIA America LLC | 2026-04 18:15 | Austin, TX | 2023 Volkswagen ID.Buzz | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 11 | Intersection | On April [XXX], 2026, in Austin, Texas, a MOIA America autonomous test vehicle ("MOIA AV") made contact with a curb while completing a right turn. The MOIA AV was traveling eastbound on [XXX] and turning right onto south…On April [XXX], 2026, in Austin, Texas, a MOIA America autonomous test vehicle ("MOIA AV") made contact with a curb while completing a right turn. The MOIA AV was traveling eastbound on [XXX] and turning right onto southbound [XXX] when the passenger rear tire made contact with the curb at the corner of the intersection. At the time of contact, the MOIA AV's automated driving system was engaged. The in-vehicle operator recorded the event at the time it occurred, and the MOIA AV remained in autonomous operation and continued the route. Subsequent review of vehicle data confirmed the contact through the longitudinal acceleration signature recorded at that point in the drive. The MOIA AVâs passenger rear tire and wheel were scraped. 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-14852 | Level 2 | Ford Motor Company | 2026-04 15:18 | Temple, TX | 2025 FORD F-150 | Alleged Engaged | Other Fixed Object | Unknown | 25 | Highway / Freeway | A driver reported that they were traveling on a freeway in their 2025 Ford F-150 near Temple, Texas, on April [XXX], 2026, at approximately 10:15 a.m. The driver initially reported that, while traveling with the BlueCrui…A driver reported that they were traveling on a freeway in their 2025 Ford F-150 near Temple, Texas, on April [XXX], 2026, at approximately 10:15 a.m. The driver initially reported that, while traveling with the BlueCruise feature engaged, the vehicle steering wheel was getting "stuck" and that they could not control the vehicle. The driver subsequently reported that they lost control of the steering wheel or it "locked", causing the vehicle to hydroplane and hit a median. The driver reported that an airbag deployed in the incident. There were no reported injuries. Ford has verified that the vehicle is equipped with Ford Co-Pilot360 Assist 2.0, which includes Adaptive Cruise Control (ACC), Lane Centering Assist (LCA), and BlueCruise. Connected vehicle telemetry data confirm an airbag deployment at approximately 10:18 a.m. on the subject date. Ford's investigation continues. |
| 540-14657 | Level 2 | General Motors, LLC | 2026-04 10:34 | Richland, MO | 2024 CADILLAC CT5 | Verified Engaged | Unknown | Unknown | 0 | Highway / Freeway | On April [XXX], 2026, a 2024 Cadillac CT5 was traveling eastbound on [XXX] near Richland, Missouri. Crash data recorded a left side impact, a rear impact, and a rollover that resulted in deployment of the airbags and fro…On April [XXX], 2026, a 2024 Cadillac CT5 was traveling eastbound on [XXX] near Richland, Missouri. Crash data recorded a left side impact, a rear impact, and a rollover that resulted in deployment of the airbags and front seat belt pretensioners. The driver was wearing their seat belt at the time of the crash. A review of the OnStar audio recording indicates the subject vehicle left the wet roadway and crashed. System data indicates that the driver took control of the vehicle 18 seconds before the crash. |
| 540-14830 | Level 2 | General Motors, LLC | 2026-04 08:37 | Jasper, FL | 2025 CADILLAC Escalade | Verified Engaged | Unknown | Unknown | 76 | Highway / Freeway | On April [XXX], 2026, a 2025 Cadillac Escalade was travelling northbound on [XXX] in Jasper, Florida with Super Cruise engaged and and active. Crash data indicates a frontal impact occurred that deployed airbags and fro…On April [XXX], 2026, a 2025 Cadillac Escalade was travelling northbound on [XXX] in Jasper, Florida with Super Cruise engaged and and active. Crash data indicates a frontal impact occurred that deployed airbags and front seat belt pretensioners. The driver and passenger were wearing their seat belts at the time of the incident. Telematics data indicates Super Cruise changed to Disabled/Not Ready two seconds prior to the incident due to steering wheel input from the driver. Weather conditions are unknown for the time of the incident. |
| 540-14872 v2 | Level 2 | General Motors, LLC | 2026-04 08:22 | Marshall, MO | 2025 CHEVROLET Traverse | Verified Engaged | Other, see Narrative | No Injured Reported | 71 | Highway / Freeway | On April [XXX], 2026, a 2025 Chevrolet Traverse was travelling southbound on [XXX] in Marshall, Missouri, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the airbag and…On April [XXX], 2026, a 2025 Chevrolet Traverse was travelling southbound on [XXX] in Marshall, Missouri, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the airbag and front seat belt pretensioners. The driver was not wearing their seat belt at the time of crash. A review of the OnStar audio recordings did not provide any details of the incident. System Data indicates that Super Cruise changed to Disabled/Not ready 1 second prior to the crash due to driver takeover. Weather condition at the time of the crash is unknown. Update: On May 15, 2026, GM received the police report. In the police report, the driver claims they were reaching back to give their baby a toy and may have held onto the steering wheel and turned it. Baby was in a restrained rear facing car seat in the 2nd row passenger outboard side. In the crash report, the vehicle crossed the grass mound median and ended up in the northbound lane. |
| 540-14975 | Level 2 | General Motors, LLC | 2026-04 13:09 | Fort Worth, TX | 2025 GMC Sierra | Verified Engaged | Unknown | Unknown | 48 | Highway / Freeway | On April [XXX], 2026, a 2025 GMC Sierra was traveling eastbound on [XXX] in Fort Worth, Texas, with Super Cruise engaged and active. Crash data indicate a frontal impact that resulted in deployment of the airbag and fro…On April [XXX], 2026, a 2025 GMC Sierra was traveling eastbound on [XXX] in Fort Worth, Texas, with Super Cruise engaged and active. Crash data indicate a frontal impact that resulted in deployment of the airbag and front seat belt pretensioners. The driver was wearing their seat belt at the time of the incident. According to OnStar audio recordings, the driver reported that traffic ahead was stopped, and the Sierra was rear ended while slowing, causing it to be pushed into the vehicle in front. Telematics data indicate that the system entered a Disabled/Not Ready state 11 seconds prior to the crash after the driver took control of the vehicle via steering input and brake pedal application. Weather conditions at the time of the incident are unknown. |
| 753-14771 | Level 2 | Kia America, Inc. | 2026-04 08:36 | SC | 2026 KIA K4 | Verified Engaged | Passenger Car | Moderate W/ Hospitalization | 70 | Highway / Freeway | On April [XXX], 2026, the customer called Kiaâs Customer Care Center to report that her 2026MY Kia K4 was involved in a âhead on collisionâ where the vehicle âturned off out of nowhere, going like in a curb,â w…On April [XXX], 2026, the customer called Kiaâs Customer Care Center to report that her 2026MY Kia K4 was involved in a âhead on collisionâ where the vehicle âturned off out of nowhere, going like in a curb,â which resulted in a 2024MY Chevrolet vehicle hitting the K4 in the front. The customer indicated that the âauto cruiseâ was activated during the incident. The customer reported that she suffered a ânerve strikeâ to her lower back and lower knee damage, and she and two other passengers were transported to the hospital. The customer requested financial assistance. The subject Kia K4 is equipped with Lane Following Assist (âLFAâ) and Smart Cruise Control (âSCCâ). 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. According to vehicle data, the subject K4 had LFA and SCC activated. However, both LFA and SCC turned off about six (6) seconds pre-crash. The steering wheel was turned to the right a small amount, then sharply to the left at three (3) seconds pre-crash. At the same time, the driver pressed the accelerator fully. The driver did not press the brake pedal before the crash. There is no indication that the vehicle lost power. Kia is currently working to obtain additional information. |
| 753-14851 v2 | Level 2 | Kia America, Inc. | 2026-04 06:41 | King George, VA | 2025 KIA K4 | Verified Engaged | Passenger Car | Moderate W/ Hospitalization | 50 | Highway / Freeway | On April [XXX], 2026, the customer called KiaâÂÂs Customer Care Center to report that her 2025MY Kia K4 was involved in an incident, the airbags did not deploy, and the cruise control allegedly âÂÂfailed.â Spe…On April [XXX], 2026, the customer called KiaâÂÂs Customer Care Center to report that her 2025MY Kia K4 was involved in an incident, the airbags did not deploy, and the cruise control allegedly âÂÂfailed.â Specifically, the customer indicated that she was asleep and her husband was driving the vehicle when âÂÂthe cruise control was set for safe driving and it failed,â the vehicle in front of them abruptly stopped, and the brakes did not engage. The customer added that her husband âÂÂhad to fight the steering wheel to be able to jerk the wheelâ and the âÂÂsteering assist was the only thing that worked but it was working against us.â The customer reported that the police had told them they were not maintaining a safe distance. In addition, the customer noted that they were suing the âÂÂother peopleâ [i.e., the vehicle in front] because âÂÂthey slammed on their brakes.â The customer reported that she was transported to the hospital with âÂÂwhiplash,â injuries to her abdominals and chest, and a concussion. Her husband allegedly received whiplash and injuries from his âÂÂneck down to his anklesâ and went to the hospital later the same day. The customer requested a vehicle replacement. The subject Kia K4 is equipped with Lane Following Assist (âÂÂLFAâÂÂ) and Smart Cruise Control (âÂÂSCCâÂÂ). 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. According to vehicle data, the subject K4 had LFA and SCC activated. However, LFA was disengaged about one (1) second pre-crash because the driver sharply turned the steering wheel (112.9 degrees). Kia is currently working to obtain additional information. *** 6/15/2026 Monthly Update*** On May [XXX], 2026, Kia received a request via email from [XXX]. On June 11, 2026, Kia provided [XXX] the requested information via NHTSAâs SLFTS portal. Other than what was provided to [XXX], Kia has no further information. |
| 10039-15657 | Level 2 | BMW of North America, LLC | 2026-03 05:53 | Garner, NC | 2026 BMW X5 | Verified Engaged | Other Fixed Object | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1306-14367 v2 | Level 2 | Toyota Motor Engineering & Manufacturing | 2026-03 17:00 | LA | 2024 TOYOTA Sienna | Verified Engaged | Pole / Tree | Minor W/O Hospitalization | 78 | Highway / Freeway | Initial report: Entries in this report are based on unconfirmed allegations: On March [XXX], 2026, Toyota received an initial contact from the owner and driver of a vehicle involved in the crash. The owner described th…Initial report: Entries in this report are based on unconfirmed allegations: On March [XXX], 2026, Toyota received an initial contact from the owner and driver of a vehicle involved in the crash. The owner described that leading up to the crash event, the owner was operating the vehicle in cruise control and lane assist mode, and alleged that while driving on a highway in the first lane, the vehicle suddenly veered across multiple lanes into a ditch and struck a tree. The owner alleged failures in the cruise control, lane assist, brakes, steering, and pre-collision systems. As a result of the crash, the airbags deployed, and the vehicle was deemed a total loss. The owner was accompanied by his wife and two other family members. The owner alleged that due to the airbag deployment, the owner received bruises on both legs and swelling and left arm burned by air bags, and the wife has shoulder bruises and swelling and a bruise below her face. The owner stated their seat belt was used, the other three passengers seat belt usage is unknown. ------------------------------------------------------------------------------------------------------------------ On May 4, 2026, Toyota completed review of a vehicle inspection field report related to the crash event and obtained the Event Data Recorder (EDR) record and PCS Freeze Frame Data (PCS FFD) from the crash event. Additionally, a crash report from the [XXX] was provided. Based on the [XXX] Crash Report (26-060417), the weather conditions were rainy with dusk lighting conditions and the roadway was wet with some standing water. The speed limit of the roadway (I-10) for this location is 70 mph. A citation was given related to speeding (2865HCLA36:32:64 General Speed Law) and the speed related circumstances are coded "too fast for conditions." A review of the PCS FFD indicated the pre-crash speed as 77.6 mph and verified that dynamic radar cruise control (DRCC) and Lane Tracing Assist (LTA) were engaged in the recorded moments leading to the crash event. While traveling straight and approaching an overpass, the vehicle began to sway and LTA turned off. The driver made steering inputs and applied the brakes, but control of the vehicle was lost. The subject vehicle, originally positioned in lane 1, swerved and after the overpass slid off the road to the right into the grass and tree line before coming to a stop. As a result of the crash, the Driver Airbag and Driver Knee Airbag deployed, and the vehicle was declared a total loss with damage to the Front, Front Right, Front Left, Left, and Rear Left sides. All passengers, positioned in the second and third row seats were buckled. Based on the available information, it is suspected that the road speed traveled and road conditions led the vehicle to hydroplane and the driver's loss of control. The LTA and DRCC were operated in adverse environmental conditions contrary to owner's manual warnings. This will be the final update for this incident. |
| 13781-14254 | Level 2 | Tesla, Inc. | 2026-03 00:58 | Roseville, CA | 2024 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 74 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14255 | Level 2 | Tesla, Inc. | 2026-03 01:14 | Carson, CA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 12 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14256 | Level 2 | Tesla, Inc. | 2026-03 16:26 | Phoenix, AZ | 2024 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 27 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14257 | Level 2 | Tesla, Inc. | 2026-03 04:47 | Surprise, AZ | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14258 | Level 2 | Tesla, Inc. | 2026-03 11:14 | Port Saint Lucie, FL | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 112 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14259 | Level 2 | Tesla, Inc. | 2026-03 16:44 | Waynesboro, PA | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 48 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14260 | Level 2 | Tesla, Inc. | 2026-03 01:36 | Los Angeles, CA | 2019 TESLA Model 3 | Verified Engaged | SUV | Unknown | 1 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14261 | Level 2 | Tesla, Inc. | 2026-03 13:07 | Cumberland, RI | 2021 TESLA Model 3 | Verified Engaged | Heavy Truck | Unknown | 11 | Street | Redacted by NHTSA as confidential business information |
| 13781-14262 | Level 2 | Tesla, Inc. | 2026-03 23:49 | Clewiston, FL | 2022 TESLA Model Y | Verified Engaged | Pickup Truck | Unknown | 72 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14275 | Level 2 | Tesla, Inc. | 2026-03 03:09 | Fort Thomas, KY | 2023 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-14276 | Level 2 | Tesla, Inc. | 2026-03 18:08 | San Mateo, CA | 2026 TESLA Model Y | Verified Engaged | Other, see Narrative | Unknown | 49 | Street | Redacted by NHTSA as confidential business information |
| 13781-14277 | Level 2 | Tesla, Inc. | 2026-03 18:41 | Carson, CA | 2021 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 83 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14278 | Level 2 | Tesla, Inc. | 2026-03 20:17 | Lake Worth Beach, FL | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 71 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14279 | Level 2 | Tesla, Inc. | 2026-03 21:21 | San Diego, CA | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 65 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14280 | Level 2 | Tesla, Inc. | 2026-03 04:42 | Dallas, TX | 2024 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-14281 | Level 2 | Tesla, Inc. | 2026-03 07:27 | Loma Linda, CA | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 42 | Street | Redacted by NHTSA as confidential business information |
| 13781-14282 | Level 2 | Tesla, Inc. | 2026-03 14:27 | Redwood City, CA | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 68 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14283 | Level 2 | Tesla, Inc. | 2026-03 18:00 | Los Alamitos, CA | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 43 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14284 | Level 2 | Tesla, Inc. | 2026-03 20:32 | Sunbury, OH | 2023 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 49 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14306 | Level 2 | Tesla, Inc. | 2026-03 20:41 | NC | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 25 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14307 | Level 2 | Tesla, Inc. | 2026-03 23:14 | Richmond, CA | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 7 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14308 | Level 2 | Tesla, Inc. | 2026-03 23:22 | Miami, FL | 2025 TESLA Model X | Verified Engaged | Unknown | Unknown | 33 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14309 | Level 2 | Tesla, Inc. | 2026-03 00:01 | Garland, TX | 2024 TESLA Model Y | Verified Engaged | Pole / Tree | Unknown | 35 | Street | Redacted by NHTSA as confidential business information |
| 13781-14311 | Level 2 | Tesla, Inc. | 2026-03 04:34 | Carlyle, IL | 2016 TESLA Model X | Verified Engaged | Unknown | Unknown | 26 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14312 | Level 2 | Tesla, Inc. | 2026-03 06:27 | Sanford, NC | 2024 TESLA Cybertruck | Verified Engaged | Pole / Tree | Unknown | 33 | Street | Redacted by NHTSA as confidential business information |
| 13781-14314 | Level 2 | Tesla, Inc. | 2026-03 09:39 | Carlsbad, CA | 2023 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 67 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14315 | Level 2 | Tesla, Inc. | 2026-03 16:16 | CA | 2017 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 78 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14316 | Level 2 | Tesla, Inc. | 2026-03 00:57 | Fremont, CA | 2026 TESLA Model X | Verified Engaged | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14317 | Level 2 | Tesla, Inc. | 2026-03 08:13 | New Athens, IL | 2021 TESLA Model 3 | Verified Engaged | Other, see Narrative | Unknown | 40 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14318 | Level 2 | Tesla, Inc. | 2026-03 11:06 | Houston, TX | 2020 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-14319 | Level 2 | Tesla, Inc. | 2026-03 21:21 | Issaquah, WA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 12 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14320 | Level 2 | Tesla, Inc. | 2026-03 10:50 | New Hill, NC | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 78 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14321 | Level 2 | Tesla, Inc. | 2026-03 12:43 | Salt Lake City, UT | 2024 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 76 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14322 | Level 2 | Tesla, Inc. | 2026-03 12:55 | Kansas City, KS | 2020 TESLA Model 3 | Verified Engaged | Other, see Narrative | Unknown | 17 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14323 | Level 2 | Tesla, Inc. | 2026-03 20:10 | Fort Lauderdale, FL | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 40 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14324 | Level 2 | Tesla, Inc. | 2026-03 06:08 | Farmington, MI | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14325 | Level 2 | Tesla, Inc. | 2026-03 15:46 | Brunswick, GA | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14326 | Level 2 | Tesla, Inc. | 2026-03 15:40 | Long Beach, CA | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14327 | Level 2 | Tesla, Inc. | 2026-03 23:20 | Santa Fe Springs, CA | 2016 TESLA Model S | Verified Engaged | Unknown | Unknown | 57 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14356 | Level 2 | Tesla, Inc. | 2026-03 01:05 | Glendale, CA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 33 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14357 | Level 2 | Tesla, Inc. | 2026-03 07:43 | Saint Paul, MN | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 42 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14358 | Level 2 | Tesla, Inc. | 2026-03 11:36 | Jacksonville, FL | 2017 TESLA Model S | Verified Engaged | Passenger Car | Unknown | 34 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-14359 | Level 2 | Tesla, Inc. | 2026-03 19:00 | Washougal, WA | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 35 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-14360 | Level 2 | Tesla, Inc. | 2026-03 22:18 | Colorado Springs, CO | 2020 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 22 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-14362 | Level 2 | Tesla, Inc. | 2026-03 11:33 | Fountain Inn, SC | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 23 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14363 | Level 2 | Tesla, Inc. | 2026-03 14:37 | San Diego, CA | 2022 TESLA Model X | Verified Engaged | Unknown | Unknown | 43 | Street | Redacted by NHTSA as confidential business information |
| 13781-14364 | Level 2 | Tesla, Inc. | 2026-03 18:08 | San Jose, CA | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 6 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14365 | Level 2 | Tesla, Inc. | 2026-03 21:46 | OR | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 34 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-14392 | Level 2 | Tesla, Inc. | 2026-03 03:23 | Youngsville, LA | 2020 TESLA Model 3 | Verified Engaged | Pickup Truck | Unknown | 42 | Street | 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.