The MachineRecord
NHTSA Standing General Order 2021-01

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 2801 to 2900.

Report IDProgramEntityIncidentPlaceVehicleEngagedCrash withSeveritySpeed, mphRoadwayNarrative
30270-13484ADSWaymo LLC2025-12 17:22Inglewood, CA2024 JAGUAR I-PACEVerified EngagedSUVNo Injured Reported22Intersection
On December [XXX], 2025 at 5:22 PM PT a Waymo Autonomous Vehicle (¢Â€ÂœWaymo AV”) operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwestboun…On December [XXX], 2025 at 5:22 PM PT a Waymo Autonomous Vehicle (¢Â€ÂœWaymo AV”) operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southwestbound on [XXX] and proceeding straight at the intersection with [XXX]. While the Waymo AV was proceeding through the intersection, an SUV that was travelling southeastbound on [XXX] proceeded to make a right turn onto southwestbound [XXX] without stopping while facing a stop sign. The front of the SUV made contact with the rear right 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13485ADSWaymo LLC2025-12 14:50Austin, TX2024 JAGUAR I-PACEVerified EngagedOther Fixed ObjectProperty Damage. No Injured Reported10Parking Lot
On December [XXX], 2025 at 2:50 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas made contact with the pavement in a parking lot driveway entrance on [XXX] near [XXX]. The Waymo AV was traveling s…On December [XXX], 2025 at 2:50 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas made contact with the pavement in a parking lot driveway entrance on [XXX] near [XXX]. The Waymo AV was traveling southeastbound on [XXX] in the left lane, and began to turn left into a parking lot driveway entrance when the underside of the Waymo AV made contact with the pavement. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13486ADSWaymo LLC2025-12 14:37San Francisco, CA2024 JAGUAR I-PACEVerified EngagedPassenger CarProperty Damage. No Injured Reported0Intersection
On December [XXX], 2025 at 2:37 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX] and the off-ramp f…On December [XXX], 2025 at 2:37 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at the intersection with [XXX] and the off-ramp freeway exit [XXX] of [XXX]. The Waymo AV was traveling southbound on [XXX] and proceeding straight at the intersection with [XXX] and the off-ramp freeway exit [XXX] of [XXX]. The ADV slowed down to a stop while entering the intersection after detecting a collision with a bird in flight. As the Waymo AV remained stationary, a passenger car traveling directly behind the Waymo AV approached the Waymo AV from behind 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. The Waymo AV and the passenger car sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13487ADSWaymo LLC2025-12 15:02Austin, TX2024 JAGUAR I-PACEVerified EngagedOther Fixed ObjectProperty Damage. No Injured Reported10Parking Lot
On December [XXX], 2025 at 3:02 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas made contact with the pavement in a parking lot driveway entrance on [XXX] near [XXX]. The Waymo AV was traveling s…On December [XXX], 2025 at 3:02 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas made contact with the pavement in a parking lot driveway entrance on [XXX] near [XXX]. The Waymo AV was traveling southeastbound on [XXX] in the left lane, and began to turn left into a parking lot driveway entrance when the underside of the Waymo AV made contact with the pavement. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13488ADSWaymo LLC2025-12 22:24Atlanta, GA2024 JAGUAR I-PACEVerified EngagedPassenger CarMinor W/ Hospitalization22Street
On December [XXX], 2025 at 10:24 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the rig…On December [XXX], 2025 at 10:24 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the right lane on [XXX] when a passenger car that was initially stopped facing north on [XXX], to the right and in front of the Waymo AV, proceeded forward into the intersection at [XXX]. As the passenger car entered the intersection the front 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. The passengers of the Waymo AV were transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13489ADSWaymo LLC2025-12 13:54Scottsdale, AZ2024 JAGUAR I-PACEVerified EngagedHeavy TruckProperty Damage. No Injured Reported1Parking Lot
On December [XXX], 2025 at 1:54 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling southbound o…On December [XXX], 2025 at 1:54 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling southbound on a driveway at a parking lot at [XXX] and a heavy truck was traveling southbound on the driveway ahead of the Waymo AV. The heavy truck came to a stop and the Waymo AV slowed to a stop to yield to the stopped heavy truck. The heavy truck reversed and the Waymo AV reversed momentarily before coming to a stop. The heavy truck continued to reverse, and the Waymo AV began to reverse again, and the rear of the heavy truck made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV' Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13490ADSWaymo LLC2025-12 22:17Los Angeles, CA2024 JAGUAR I-PACEVerified EngagedSUVMinor W/O Hospitalization9Street
On December [XXX], 2025 at 10:17 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 southwestbound in th…On December [XXX], 2025 at 10:17 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 southwestbound in the right lane on [XXX] when it began to slow for a flashing red light at the intersection with [XXX]. While the Waymo AV was slowing, an SUV traveling southwestbound in the right lane on [XXX] began accelerating as it 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. Both vehicles sustained damage. The passengers in the Waymo AV were not belted at the time of the collisions. The passengers in the Waymo AV alleged minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13491ADSWaymo LLC2025-12 21:48Los Angeles, CA2024 JAGUAR I-PACEVerified EngagedVanMinor W/ Hospitalization0Street
On December [XXX], 2025 at 9:48 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 stopped at the curb facing south…On December [XXX], 2025 at 9:48 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 stopped at the curb facing southeast on [XXX] with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, a van traveling southeastbound on [XXX] maneuvered to the right and approached the Waymo AV from behind, and the front of the van 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. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13495ADSWaymo LLC2025-12 01:41San Francisco, CA2024 JAGUAR I-PACEVerified EngagedSUVMinor W/ Hospitalization0Street
On December [XXX], 2025 at 1:41 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing northeast on […On December [XXX], 2025 at 1:41 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing northeast on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling northeastbound on [XXX] 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. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13506ADSWaymo LLC2025-12 04:09Atlanta, GA2024 JAGUAR I-PACEVerified EngagedOther, see NarrativeProperty Damage. No Injured Reported25Intersection
On December [XXX], 2025 at 4:09 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving debris on [XXX] at [XXX]. The Waymo AV was traveling northwestbound on [XXX] in the…On December [XXX], 2025 at 4:09 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving debris on [XXX] at [XXX]. The Waymo AV was traveling northwestbound on [XXX] in the the left lane proceeding through the intersection with [XXX] when the front left side tire of the Waymo AV made contact with a piece of 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13507ADSWaymo LLC2025-12 05:54Brisbane, CA2021 JAGUAR I-PACEVerified EngagedHeavy TruckProperty Damage. No Injured Reported0Street
On December [XXX], 2025 at 5:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Brisbane, California was in a collision involving a heavy truck on [XXX] at a parking lot entrance at [XXX]. The Waymo AV was tra…On December [XXX], 2025 at 5:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Brisbane, California was in a collision involving a heavy truck on [XXX] at a parking lot entrance at [XXX]. The Waymo AV was traveling eastbound in the right lane on [XXX] when it began to slow for a heavy truck traveling eastbound in the right lane on [XXX] in front of the Waymo AV. The heavy truck changed lanes to the left and the Waymo AV proceeded forward in the right lane, adjacent to the heavy truck. The heavy truck then proceeded to turn right from the left lane into the parking lot at [XXX], entering the Waymo AV's lane of travel. The Waymo AV slowed to a stop as the heavy truck continued to turn, and the right 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13508ADSWaymo LLC2025-12 02:08Orlando, FL2024 JAGUAR I-PACEVerified Not EngagedHeavy TruckProperty Damage. No Injured Reported0Street
On December [XXX], 2025 at 2:08 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling northbound in autono…On December [XXX], 2025 at 2:08 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling northbound in autonomous mode on [XXX] in the third from the right lane when it came to a stop behind a heavy truck in a queue of traffic at the intersection with [XXX]. The heavy truck began to reverse and the Waymo AV activated its horn. As the heavy truck continued to reverse, the test driver transitioned the Waymo AV to manual mode and the rear of the heavy truck made contact with the front of the Waymo AV. 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-13509ADSWaymo LLC2025-12 04:08San Francisco, CA2024 JAGUAR I-PACEVerified EngagedOther Fixed ObjectProperty Damage. No Injured Reported18Street
On December [XXX], 2025 at 4:08 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling east…On December [XXX], 2025 at 4:08 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] when the front of the Waymo AV made contact with a fallen utility line hanging in the travel lane. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The utility line sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13510ADSWaymo LLC2025-12 07:20San Francisco, CA2021 JAGUAR I-PACEVerified EngagedPassenger CarProperty Damage. No Injured Reported15Street
On December [XXX], 2025 at 7:20 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southeastb…On December [XXX], 2025 at 7:20 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southeastbound on [XXX] in the third from the right lane and exiting the intersection with [XXX], when it began to change lanes to the right with its right signal activated. As the Waymo AV was completing the lane change maneuver, a passenger car that was initially stopped in a queue of traffic in the rightmost lane proceeded to change lanes to the left, entering the Waymo AV's lane of travel, and the front left side of the passenger car made contact with the rear 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-13511ADSWaymo LLC2025-12 13:17Los Angeles, CA2024 JAGUAR I-PACEVerified EngagedVanProperty Damage. No Injured Reported0Intersection
On December [XXX], 2025 at 1:17 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 stopped facing west on [XXX] for…On December [XXX], 2025 at 1:17 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 stopped facing west on [XXX] for a red light at the intersection with [XXX] with its right turn signal activated. After remaining stopped for approximately six minutes a short distance in advance of the stop line at the red light, the Waymo AV passenger opened the rear left side door and exited the vehicle, and a van that was initially stopped directly behind the Waymo AV maneuvered to the left before slowing to a stop behind the Waymo AV. The Waymo AV passenger briefly interacted with the van operator through the van window, and then re-entered the Waymo AV. The van then proceeded to pass the Waymo AV on the left and the right side of the van 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. The passenger in the Waymo AV was not belted at the time of the collision. 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-13512ADSWaymo LLC2025-12 12:07Los Angeles, CA2024 JAGUAR I-PACEVerified EngagedHeavy TruckProperty Damage. No Injured Reported0Street
On December [XXX], 2025 at 12:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound on…On December [XXX], 2025 at 12:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was traveling eastbound on a narrow portion of [XXX] when it slowed to a stop to yield to a heavy truck that was stopped facing west on [XXX]. While the Waymo AV was stopped, the heavy truck proceeded to pass to the left of the Waymo AV and the left side of the heavy 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. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13513ADSWaymo LLC2025-12 10:02Phoenix, AZ2024 JAGUAR I-PACEVerified EngagedHeavy TruckProperty Damage. No Injured Reported0Parking Lot
On December [XXX], 2025 at 10:02 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling southbound in…On December [XXX], 2025 at 10:02 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling southbound in the parking lot at [XXX] when it slowed to a stop to yield to a heavy truck that was facing southwest and executing a reversing turn into a loading dock parking stall at the east side of the parking lot. The heavy truck came to a stop, then began to proceed forward in the southbound direction, and the Waymo AV proceeded forward again, following the heavy truck. The heavy truck then came to a stop and began to reverse. The Waymo AV then momentarily reversed before coming to a stop and the heavy truck continued to reverse, 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13514ADSWaymo LLC2025-12 08:20San Francisco, CA2021 JAGUAR I-PACEVerified EngagedOther Fixed ObjectProperty Damage. No Injured Reported25Street
On December [XXX], 2025 at 8:20 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling sout…On December [XXX], 2025 at 8:20 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fallen utility line on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on [XXX] when the front of the Waymo AV made contact with a fallen utility line hanging in the travel lane. 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13515ADSWaymo LLC2025-12 00:04Austin, TX2024 JAGUAR I-PACEVerified EngagedPassenger CarProperty Damage. No Injured Reported0Street
On December [XXX], 2025 at 12:04 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 northbound on [XXX] …On December [XXX], 2025 at 12:04 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 northbound on [XXX] in the leftmost lane when it slowed to a stop in a queue of traffic for a red light at the intersection with [XXX]. A passenger car that was initially stopped directly in front of the Waymo AV began to reverse and the Waymo AV activated its horn and hazard lights. The passenger car continued to reverse and the rear of the passenger car 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. 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-13538ADSWaymo LLC2025-12 00:34West Hollywood, CA2024 JAGUAR I-PACEVerified EngagedPassenger CarProperty Damage. No Injured Reported0Street
On December [XXX], 2025 at 12:34 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling westboun…On December [XXX], 2025 at 12:34 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in West Hollywood, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] when it slowed to a stop to yield to a passenger car that was stopped partially in-lane facing west on [XXX]. While the Waymo AV was stopped, a passenger in the Waymo AV opened the rear left side door to exit. A second passenger car that was initially traveling directly behind the Waymo AV maneuvered around to the left of the stationary Waymo AV, entering the opposing lane of travel, and the right side of the passenger car made contact with the open rear left door 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. The passengers in the Waymo AV were not belted at the time of the collision as they were exiting the vehicle. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13539ADSWaymo LLC2025-12 13:21San Francisco, CA2024 JAGUAR I-PACEVerified EngagedFirst Responder VehicleProperty Damage. No Injured Reported0Intersection
On December [XXX], 2025 at 1:21 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] at [XXX]. The Waymo AV was stopped fac…On December [XXX], 2025 at 1:21 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] at [XXX]. The Waymo AV was stopped facing east in the left lane on [XXX] for a red light at the intersection with [XXX]. A fire engine with lights and siren activated traveling northbound in the leftmost lane on [XXX] proceeded straight through the intersection with [XXX] before stopping, then reversing into the intersection. The fire engine then proceeded to turn left onto [XXX]. The Waymo AV moved slightly to the right within its lane, then came to a stop to yield to the oncoming fire engine. While the Waymo AV was stopped, the fire engine continued to complete the left turn and the left side of the fire engine 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 Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13540ADSWaymo LLC2025-12 13:23Los Angeles, CA2024 JAGUAR I-PACEVerified EngagedPickup TruckProperty Damage. No Injured Reported0Parking Lot
On December [XXX], 2025 at 1:23 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pick-up truck in a parking lot at [XXX]. The Waymo AV came to a stop facin…On December [XXX], 2025 at 1:23 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pick-up truck in a parking lot at [XXX]. The Waymo AV came to a stop facing northwestbound after completing a multipoint turn in a parking lot at [XXX]. A pickup truck traveling southeastbound in the parking lot approached the Waymo AV and came to a stop to the right of the Waymo AV. The pickup truck then proceeded forward to pass the Waymo AV and the rear right side of the pickup truck made contact with the rear right side of the stationary Waymo AV. At the time of the impact, the Waymo AV' Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13541ADSWaymo LLC2025-12 18:35San Francisco, CA2024 JAGUAR I-PACEVerified EngagedPickup TruckProperty Damage. No Injured Reported0Street
On December [XXX], 2025 at 6:35 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southbound …On December [XXX], 2025 at 6:35 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southbound in the second from the right lane on [XXX] with its left turn signal activated when it initiated a lane change to the leftmost lane. As the Waymo AV crossed the dashed white lane line, the Waymo AV slowed to a stop, partially in the leftmost lane and partially in the second from the right lane, to yield to a passenger car stopped in a queue of traffic in front of the Waymo AV. A pickup truck that was initially stopped in the leftmost lane facing south on [XXX] behind and to the left of the Waymo AV proceeded forward and the front right 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. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13542ADSWaymo LLC2025-12 03:45Phoenix, AZ2024 JAGUAR I-PACEVerified EngagedHeavy TruckProperty Damage. No Injured Reported0Parking Lot
On December [XXX], 2025 at 3:45 AM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling southbound in a p…On December [XXX], 2025 at 3:45 AM MT a Waymo Autonomous Vehicle (Waymo AV) operating in Phoenix, Arizona was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling southbound in a parking lot at [XXX] when it slowed to a stop with its hazard lights activated to yield to a heavy truck that was facing south and executing a reversing turn into a loading dock parking stall at the east side of the parking lot. The heavy truck continued to reverse, and the rear left side of the heavy truck trailer made contact with the right side of the stationary Waymo AV. At the time of the impact, the Waymo AV' Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
30270-13548ADSWaymo LLC2025-12 10:49Phoenix, AZ2024 JAGUAR I-PACEVerified EngagedHeavy TruckProperty Damage. No Injured Reported12Intersection
On December [XXX], 2025 at 10:49 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] in…On December [XXX], 2025 at 10:49 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] in the designated right turn lane and began to slow in preparation for a right turn at a green light at the intersection with [XXX]. As the Waymo AV initiated the right turn, a box truck traveling northbound in the left adjacent lane on [XXX], initiated a right turn onto [XXX], crossing the solid white line and entering the Waymo AV's lane of travel, and the front right side of the box truck 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-13549ADSWaymo LLC2025-12 17:09Los Angeles, CA2024 JAGUAR I-PACEVerified EngagedSUVProperty Damage. No Injured Reported0Intersection
On December [XXX], 2025 at 5:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northeastbound on [XXX]…On December [XXX], 2025 at 5:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northeastbound on [XXX] in the designated left turn lane with its left turn signal activated when it began to slow to a stop for a yellow light at the intersection with [XXX]. As the traffic light turned red the Waymo AV remained stopped. An SUV traveling northeastbound on [XXX] approached the Waymo AV from behind 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. 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-13554ADSWaymo LLC2025-12 11:13South San Francisco, CA2024 JAGUAR I-PACEVerified EngagedHeavy TruckProperty Damage. No Injured Reported0Street
On December [XXX], 2025 at 11:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in South San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped southb…On December [XXX], 2025 at 11:13 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in South San Francisco, California was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped southbound on [XXX] in the right lane in a queue of traffic for the red light at the intersection with [XXX]. While the Waymo AV was stopped, a heavy truck that was initially stopped immediately behind the Waymo AV proceeded forward and the front of the heavy truck 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-13557ADSWaymo LLC2025-12 16:54Atlanta, GA2024 JAGUAR I-PACEVerified EngagedHeavy TruckProperty Damage. No Injured Reported0Street
On December [XXX], 2025 at 4:54 PM 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 northwestbound on [X…On December [XXX], 2025 at 4:54 PM 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 northwestbound on [XXX] when it slowed to a stop to yield to a stopped heavy truck facing northwest in-lane. The heavy truck began to reverse and the Waymo AV momentarily reversed before coming to a stop. The heavy truck continued to reverse and the Waymo AV momentarily reversed before coming to a stop and the rear of the heavy truck 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. 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-13564ADSWaymo LLC2025-12 14:30San Francisco, CA2024 JAGUAR I-PACEVerified EngagedNon-Motorist: Scooter - SkateboardProperty Damage. No Injured Reported0Intersection
On December [XXX], 2025 at 2:30 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a scooterist on [XXX] at [XXX]. The Waymo AV was traveling southbound on […On December [XXX], 2025 at 2:30 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a scooterist on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] with its right turn signal activated when it began to slow for a right turn at the green traffic light at the intersection with [XXX]. After initiating the right turn, the Waymo AV slowed to a stop to yield to pedestrians in the crosswalk crossing [XXX]. While the Waymo AV was stopped, a scooterist traveling southbound in the bike lane on [XXX] approached the Waymo AV from behind, and the front of the scooter made contact with the rear right 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.
30413-13468ADSMay Mobility2025-12 11:29Arlington, TX2024 TOYOTA SiennaVerified EngagedPassenger CarNo Injured Reported2Intersection
The May Mobility vehicle (Ego) is stopped at a red light, then the Ego begins to accelerate and turn right when the traffic light changes to green. As the Ego accelerates, a pedestrian begins moving and enters the crossw…The May Mobility vehicle (Ego) is stopped at a red light, then the Ego begins to accelerate and turn right when the traffic light changes to green. As the Ego accelerates, a pedestrian begins moving and enters the crosswalk from the other side of the intersection. This activates the rule-based crosswalk logic. Ego determines that it is able to stop before the crosswalk without exceeding our max deceleration threshold, which triggers an in-policy stopping reaction for the crosswalk. The Ego brakes to yield for the pedestrian. The vehicle trailing the Ego accelerates, making contact with the rear-end of the Ego. In the 2.5 seconds between the start of the Ego braking and the collision, the rear vehicle accelerated from 0.2 to 6.1 m/s (0.4 to 13.6 mph) without slowing until after the collision occurred. In response to this incident, immediate mitigations were made, in that the vehicle operators (AVOs) operate all intersections in manual mode. This remained in place until January 12, when we received a solution which instituted a reduction of the 3.5 m/s2 parameter, in order to prevent the Ego from yielding to pedestrians in crosswalks that are still far from the Ego’s lane if such yielding would induce braking.
30413-13469ADSMay Mobility2025-12 19:37Arlington, TX2023 TOYOTA SiennaVerified EngagedPassenger CarNo Injured Reported4Intersection
The May Mobility vehicle (Ego) approaches a turn with a trailing vehicle following closely behind. The May planner initially selects a trajectory it believes will safely complete the turn. However, as the Ego begins the …The May Mobility vehicle (Ego) approaches a turn with a trailing vehicle following closely behind. The May planner initially selects a trajectory it believes will safely complete the turn. However, as the Ego begins the turn, it re-evaluates the situation and detects a significant risk of striking the curb. At that point, the planner shifts focus from avoiding the curb entirely to minimizing the severity of a potential curb strike. To reduce speed before the expected contact, the Ego brakes at €“3.5 m/s²). Because the trailing vehicle is following so closely, this deceleration makes a rear-end collision likely. The Ego predicts a potential rear-end collision and elects to reduce brake force to lessen the impact severity. Moments later, the trailing vehicle strikes the rear driver-side bumper of the Ego and then drives away. Future improvements are underway to give the planner a policy option to steer away from curbs. This new capability will help the vehicle avoid situations where braking becomes the only remaining way to manage close curb proximity.
30413-13470ADSMay Mobility2025-12 11:01Atlanta, GA2024 TOYOTA SiennaVerified EngagedSUVNo Injured Reported5Street
The May Mobility vehicle (Ego) was operating in autonomy while waiting in slow traffic in the leftmost of two parallel lanes. Ahead, both lanes were obstructed by stopped vehicles, prompting traffic to move to the center…The May Mobility vehicle (Ego) was operating in autonomy while waiting in slow traffic in the leftmost of two parallel lanes. Ahead, both lanes were obstructed by stopped vehicles, prompting traffic to move to the center turn lane to proceed. The Autonomous Vehicle Operator (AVO) intervened to move closer to the lead vehicle as another vehicle in the right lane attempted to merge left, preventing it. After the merging car stopped, the AVO pulled closer to the lead vehicle, removing any space to merge. As the lead vehicle began to move, both the AVO and the vehicle to the right immediately accelerated, while the merging vehicle moved left into the side of the May AV. Had the Ego remained in Autonomous mode, it would have maintained a safe distance allowing the merging vehicle to proceed safely. No software defects led to this event. This behavior goes against the training of May AVO€™s. Upon review of this AVO’s actions it was decided to remove this person from their role as an AVO.
30610-13660ADSZoox, Inc.2025-12 16:08San Francisco, CA2026 ZOOX ZooxVerified EngagedPassenger CarProperty Damage. No Injured Reported1Intersection
An unoccupied Zoox vehicle (Vehicle 1) was stationary in the right lane on northeast-bound [XXX] at [XXX] in San Francisco, stopped behind traffic at a red light. After the light turned green, the Zoox vehicle initially …An unoccupied Zoox vehicle (Vehicle 1) was stationary in the right lane on northeast-bound [XXX] at [XXX] in San Francisco, stopped behind traffic at a red light. After the light turned green, the Zoox vehicle initially remained stopped to yield to an active police vehicle making a right turn onto [XXX] from the adjacent lane. During the subsequent green light cycle, as the Zoox vehicle began to proceed straight along [XXX], two passenger cars, including Vehicle 2, cut across its path from behind, attempting an illegal right turn onto [XXX] from a through lane. The Zoox vehicle braked hard, but contact was unavoidable, and Vehicle 2 clipped the Zoox vehicle's left front fender. The front-seat passenger of Vehicle 2 exited to inspect the Zoox vehicle before returning to their car and leaving the scene without exchanging information. The Zoox vehicle then cleared the scene and returned to base. Upon inspection, the Zoox vehicle was found to have sustained minor damage. Police were notified, and no injuries were reported.
30610-13661ADSZoox, Inc.2025-12 17:56San Francisco, CA2026 ZOOX ZooxVerified EngagedPickup TruckProperty Damage. No Injured Reported1Street
An occupied Zoox autonomous vehicle (Vehicle 1) was traveling west on [XXX] past [XXX] when it encountered debris in the lane. The Zoox vehicle braked hard for the debris and was then rear ended by a close-following Pick…An occupied Zoox autonomous vehicle (Vehicle 1) was traveling west on [XXX] past [XXX] when it encountered debris in the lane. The Zoox vehicle braked hard for the debris and was then rear ended by a close-following Pickup (Vehicle 2) that was abruptly merging into the lane directly behind the Zoox vehicle. The Vehicle 2 driver then reversed and left the scene without attempting to exchange information. Shortly after, the Zoox vehicle cleared the scene, turned right onto [XXX], and pulled over to allow the riders to exit the vehicle. The Zoox vehicle then returned to base for inspection and was found to have sustained moderate damage. There were no reported injuries, and the police were notified.
31101-13612 v5ADSAvride Inc.2025-12 17:11Dallas, TX2025 HYUNDAI Ioniq 5Verified EngagedPickup TruckProperty Damage. No Injured Reported14Street
On December [XXX], 2025 at 5:11 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] engaged in autonomous mode w…On December [XXX], 2025 at 5:11 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] engaged in autonomous mode when it approached a pickup truck parked on the right curb with both doors open. As the AVRIDE AV proceeded to pass the parked pickup truck, the right side of the AVRIDE AV made contact with the open front left side door of the parked pickup truck. Following the collision, the AVRIDE AV pulled over to the side of the road. Both vehicles sustained minor damage. There were no reported injuries. There was no indication of injury or request for medical attention at the scene. Avride received notification of injury from the other party's insurance company on January 16, 2026. Because of this, Avride made an update in the report changing the highest severity injury alleged as "Minor W/O Hospitalization". After following up with the other party's insurance claim, no information or documentation for the alleged injury was provided. Communication from the other party and their representation has stopped as of May 8, 2026. Because of this, we are updating the report again and changing the highest injury severity alleged to "Property Damage. No Injury Reported."
31101-13615 v2ADSAvride Inc.2025-12 19:23Austin, TX2025 HYUNDAI Ioniq 5Verified EngagedPassenger CarProperty Damage. No Injured Reported16Street
On December [XXX], 2025 at 7:23 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas. The AVRIDE AV was traveling eastbound on [XXX] in autonomous mode engaged, preparing to turn left on…On December [XXX], 2025 at 7:23 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas. The AVRIDE AV was traveling eastbound on [XXX] in autonomous mode engaged, preparing to turn left onto [XXX]. As the AVRIDE AV began to enter the turn lane on [XXX], a passenger car traveling in front of the AVRIDE AV moved into the AVRIDE AV¢Â€Â™s lane of travel and the rear left side of the passenger car made contact with the front right fender of the AVRIDE AV. Both vehicles sustained damage. There were no reported injuries.
31101-13616ADSAvride Inc.2025-12 11:27Dallas, TX2025 HYUNDAI Ioniq 5Verified EngagedVanProperty Damage. No Injured Reported20Street
On December [XXX], 2025 at 11:27 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the right lane on [XXX] engaged in aut…On December [XXX], 2025 at 11:27 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the right lane on [XXX] engaged in autonomous mode when it approached a pickup truck parked in the AVRIDE AV's lane of travel. A van was traveling eastbound in the left lane on [XXX]. As the AVRIDE AV began to change lanes to the left lane the left side of the AVRIDE AV made contact with the right side of the van. Both vehicles stopped and pulled over following the collision. Both vehicles sustained damage. No injuries were reported.
31101-13619ADSAvride Inc.2025-12 07:35Austin, TX2023 HYUNDAI Ioniq 5Verified EngagedSUVProperty Damage. No Injured Reported12Street
On December [XXX], 2025 at 7:35 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the middle lane on [XXX] engaged in aut…On December [XXX], 2025 at 7:35 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound in the middle lane on [XXX] engaged in autonomous mode. [XXX] is a three-lane street. The AVRIDE AV approached a school bus located in the right lane that was stopping with its stop sign signals displayed. The AVRIDE AV and a passenger car in the right lane next to the AVRIDE AV began to slow in order to stop in compliance with applicable traffic rules. As the AVRIDE AV was in the process of slowing to a stop, an SUV traveling in the right lane directly behind the AVRIDE AV and passenger car attempted to pass the passenger car on the left side and AVRIDE AV on the right side in one maneuver. This caused the left front side of the SUV to make contact with the rear right side of the AVRIDE AV. Both vehicles stopped and pulled over after the incident. Both vehicles sustained damage. No injuries were reported.
31101-13620 v2ADSAvride Inc.2025-12 19:35Dallas, TX2025 HYUNDAI Ioniq 5Verified EngagedPickup TruckNo Injured Reported24Street
On December [XXX], 2025 at 7:35 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 in the rightmost lane on [XXX] engage…On December [XXX], 2025 at 7:35 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 in the rightmost lane on [XXX] engaged in autonomous mode. A pickup truck traveling in eastbound in the left lane began to change lanes into the AVRIDE AV's lane of travel and the right side of the truck made contact with the left side of the AVRIDE AV. No damage was observed to either vehicle and no injuries were reported.
31101-13621ADSAvride Inc.2025-12 11:47Dallas, TX2025 HYUNDAI Ioniq 5Verified EngagedOther Fixed ObjectProperty Damage. No Injured Reported17Street
On December [XXX], 2025 at 11:47 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound on [XXX] engaged in autonomous mode when…On December [XXX], 2025 at 11:47 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound on [XXX] engaged in autonomous mode when it made contact with a stationary dumpster located on the right side of the road and the right side of the AVRIDE AV made contact with the left side of the stationary dumpster. The collision resulted in damage to the AVRIDE AV. No injuries were reported.
31101-13624ADSAvride Inc.2025-12 11:11Dallas, TX2025 HYUNDAI Ioniq 5Verified EngagedHeavy TruckProperty Damage. No Injured Reported7Street
On December [XXX], 2025 at 11:11 AM, 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 the left lane on [XXX] engaged in aut…On December [XXX], 2025 at 11:11 AM, 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 the left lane on [XXX] engaged in autonomous mode when it began to change lanes to the right lane. A heavy truck traveling southbound in the right lane on [XXX] proceeded straight as the AVRIDE AV attempted to change lanes, and the front right side of the AVRIDE made contact with the rear left side of the heavy truck. The collision resulted in damage to the AVRIDE AV. No damage was reported to the dairy truck. No injuries were reported.
31101-13625ADSAvride Inc.2025-12 07:54Austin, TX2023 HYUNDAI Ioniq 5Verified EngagedHeavy TruckProperty Damage. No Injured Reported4Street
On December [XXX], 2025 at 7:54 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southeastbound in autonomous mode in the center lane…On December [XXX], 2025 at 7:54 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southeastbound in autonomous mode in the center lane on [XXX] when it came to a stop at a red light at the intersection with [XXX]. While the AVRIDE AV was stopped, a tow truck traveling in the right lane began to enter the AVRIDE AV€™s lane of travel. There was sufficient space for the tow truck to move into the lane while the AVRIDE AV remained stopped. When the traffic signal turned green, both vehicles began to proceed slowly into the intersection. The tow truck then came to an abrupt stop while the light remained green. The safety driver of the AVRIDE AV applied the brakes, but due to the sudden stop by the tow truck, the front of the AVRIDE AV made contact with the rear of the tow truck. Both vehicles sustained damage. No injuries were reported.
31101-13626ADSAvride Inc.2025-12 10:04Dallas, TX2025 HYUNDAI Ioniq 5Verified EngagedPassenger CarNo Injured Reported0Street
On December [XXX], 2025 at 10:05 AM, an AVRIDE AV autonomous vehicle (the €œAVRIDE AV”) was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling forward at a low speed on [XXX] in autonomous…On December [XXX], 2025 at 10:05 AM, an AVRIDE AV autonomous vehicle (the €œAVRIDE AV”) was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling forward at a low speed on [XXX] in autonomous mode when the passenger car ahead of it began to reverse. The AVRIDE AV came to a stop, and the safety driver sounded the horn. The passenger car in front of the AVRIDE AV continued to reverse and the rear of the passenger car made contact with the front of the AVRIDE AV. The vehicles barely made contact. No damage to either vehicle and no injuries were reported.
31101-13627ADSAvride Inc.2025-12 06:41Austin, TX2023 HYUNDAI Ioniq 5Verified EngagedSUVProperty Damage. No Injured Reported0Highway / Freeway
On December [XXX], 2025 at 6:41 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX]. The AVRIDE AV was traveling eastbound in autonomous mode in the right lane on [XXX] East. T…On December [XXX], 2025 at 6:41 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX]. The AVRIDE AV was traveling eastbound in autonomous mode in the right lane on [XXX] East. The AVRIDE AV was stopped at a yield sign, attempting to merge into traffic onto [XXX] East, when an SUV approached from the AVRIDE AV from behind and the front of the SUV made contact with the rear of the AVRIDE AV. Following the collision, both vehicles came to a safe stop, and the drivers exchanged information. Both vehicles sustained minor damage. No injuries were reported.
502-13360 v2Level 2Ford Motor Company2025-12 14:24Southfield, MI2025 FORD F-150Verified EngagedPassenger CarMinor W/ Hospitalization0Highway / Freeway
Update to Report [XXX]: Ford has obtained the police report regarding this incident, which documents a four-vehicle collision. According to the report, a Kia Sorento struck the rear of the Ford F-150, causing the F-150 t…Update to Report [XXX]: Ford has obtained the police report regarding this incident, which documents a four-vehicle collision. According to the report, a Kia Sorento struck the rear of the Ford F-150, causing the F-150 to collide with the rear of a Subaru Impreza. Subsequently, a Ford Fusion struck the rear of the Kia Sorento. The report noted that emergency medical services were requested only for the occupant of the Kia Sorento, with no other injuries reported. Additionally, the report indicates that roadway conditions were dry at the time of the incident. No additional information has been received that materially differs from the details preciously reported about this incident.
540-13273 v2Level 2General Motors, LLC2025-12 18:24Albany, NY2025 CADILLAC EscaladeVerified EngagedSUVFatality85Highway / Freeway
On December [XXX], 2025, a 2025 Cadillac Escalade was travelling northwest on [XXX] in Albany, New York, with Super Cruise engaged and active. Crash data indicated a frontal impact occurred that deployed the front seat b…On December [XXX], 2025, a 2025 Cadillac Escalade was travelling northwest on [XXX] in Albany, New York, with Super Cruise engaged and active. Crash data indicated a frontal impact occurred that deployed the front seat belt pretensioners and airbags. The driver and front passenger were wearing their seat belts at the time of the crash. According to OnStar recordings, the driver stated he struck a vehicle that pulled in front of him. The driver complained of chest pain. At 2 seconds prior to the crash, Super Cruise changed to a Disabled/Not Ready state due to the driver braking. Update: On December 5, 2025, GM learned according to news reports a 2018 Chevrolet Traverse entered the highway and crossed all four lanes of traffic, blocking the path of the Escalade, which struck the Traverse from behind in the far-left lane. The driver of the Traverse was later pronounced dead at Albany Medical Center. The other passengers in the Traverse (one adult and three children) and the four adults traveling in the Escalade were also taken to the Albany Medical Center. According to news reports and a NY State Police update published on December 2, the other eight people involved in the crash had non-life-threatening injuries.
540-13304Level 2General Motors, LLC2025-12 11:58Sacramento, CA2022 CADILLAC EscaladeVerified EngagedOther, see NarrativeUnknown19Highway / Freeway
On December [XXX], 2025, a 2022 Cadillac Escalade was travelling northbound on [XXX] in Sacramento, California, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed airbags …On December [XXX], 2025, a 2022 Cadillac Escalade was travelling northbound on [XXX] in Sacramento, California, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed airbags and the front seat belt pretensioners. The driver and front passenger were wearing their seat belt at the time of crash. Telematics data indicates Super Cruise changed to "Disabled/Not Ready" 2.3 seconds prior to the crash due to driver take over with a brake apply. According to OnStar audio recordings, the driver claimed a vehicle abruptly changed into the Escalade's lane of travel.
540-13305Level 2General Motors, LLC2025-12 8:00Ridgefield, WA2025 GMC YukonVerified EngagedOther, see NarrativeUnknown79Highway / Freeway
On December [XXX], 2025, a 2025 GMC Yukon was travelling southbound on [XXX] in Ridgefield, Washington, with Super Cruise engaged and active. Crash data indicates there were two frontal impacts that deployed airbags and …On December [XXX], 2025, a 2025 GMC Yukon was travelling southbound on [XXX] in Ridgefield, Washington, with Super Cruise engaged and active. Crash data indicates there were two frontal impacts that deployed airbags and the front seat belt pretensioners. The driver was wearing their seat belt at the time of crash. Telematics data indicates Super Cruise changed to "Disabled/Not Ready" at the time of the crash due to driver take over with a brake apply. According to OnStar audio recordings, the driver claimed to have impacted a stationary vehicle that was turned sideways in the road with no lights on.
540-13414 v3Level 2General Motors, LLC2025-12 09:43Macon, GA2025 GMC SierraVerified EngagedOther Fixed ObjectUnknown62Highway / Freeway
On December [XXX], 2025, a 2025 GMC Sierra was travelling northbound on [XXX] in Macon, Georgia with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pret…On December [XXX], 2025, a 2025 GMC Sierra was travelling northbound on [XXX] in Macon, Georgia with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pretensioners and airbags. The driver and front passenger were wearing their seat belt at the time of crash. A review of the OnStar audio recordings indicated no response from the occupants. Update: On December 31, 2025, GM received the police report along with updated vehicle crash and telemetry data. The police report indicates that the vehicle was traveling eastbound on [XXX] in an active construction zone. The driver reported that while traveling on the interstate and attempting to make a lane change, the vehicle intervened to correct the maneuver, resulting in contact with the barrier for the right-lane closure. Vehicle telemetry data indicates that Super Cruise transitioned to "Disabled/Not Ready" 3 seconds prior to the crash due to a driver brake application. Update: On March 2, 2026, GM received remote event data from the vehicle. The data indicates that the vehicle was traveling at 62mph prior to the time of the crash and that Super Cruise entered a Degraded Escalation state 1.4 seconds prior to the crash due to lost lane line detection.
540-13446 v2Level 2General Motors, LLC2025-12 14:50Farmersville, TX2025 CADILLAC CT5Verified EngagedHeavy TruckMinor W/O Hospitalization43Intersection
On December [XXX], 2025, a 2025 Cadillac CT5 was travelling eastbound in the left lane on [XXX] in Farmersville, Texas, with Super Cruise engaged and active. Crash data indicated a frontal impact occurred that deployed t…On December [XXX], 2025, a 2025 Cadillac CT5 was travelling eastbound in the left lane on [XXX] in Farmersville, Texas, with Super Cruise engaged and active. Crash data indicated a frontal impact occurred that deployed the front seat belt pretensioners and airbags. The driver was wearing a seat belt at the time of the crash. According to OnStar recordings, the driver stated they struck an 18-wheeler and another unknown vehicle. Telematics data indicates Super Cruise changed to "Disabled/Not Ready" 2 seconds prior to the crash due to driver brake apply. Update: On December 30, 2025 GM received the police report which indicates that the CT5 driver did not control speed and impacted the left rear of the front tractor unit and the side of the tractor trailer stopped at a traffic signal. The report further notes that the subject vehicle then struck the rear right of a stationary Ford F-350 pickup truck positioned adjacent to the semi-truck. Only a minor injury was reported by the CT5 driver.
540-13562 v2Level 2General Motors, LLC2025-12 13:17Clio, MI2026 CADILLAC LyriqVerified EngagedSUVNo Injured Reported81Highway / Freeway
On December [XXX], 2025, a 2026 Cadillac Lyriq was travelling southbound on [XXX] in Clio, Michigan, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt…On December [XXX], 2025, a 2026 Cadillac Lyriq was travelling southbound on [XXX] in Clio, Michigan, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pretensioners and airbags. The driver and front passenger were wearing their seat belt at the time of crash. A review of the OnStar audio recordings indicated that their vehicle hit another vehicle. Telematics data indicates that Super Cruise entered an "Enabled" state 6 seconds prior to the crash. Update: On March 25, 2026, GM received the police report, which indicates that the Cadillac Lyriq driver lost control of the vehicle, sideswiped the driver side of a GMC Acadia, and then struck the center median. The GMC Acadia subsequently left the roadway, entered a wooded area, and struck a tree. The police report notes that there was sleet/hail at the time of the incident and that both vehicles were towed from the scene; no injuries were reported.
540-13572 v2Level 2General Motors, LLC2025-12 19:41Ellsworth, KS2024 CHEVROLET TraverseVerified EngagedOther Fixed ObjectMinor W/O Hospitalization72Highway / Freeway
On December [XXX], 2025, a 2024 Chevrolet Traverse was travelling west on [XXX] in Ellsworth, Kansas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact and rollover that deployed airba…On December [XXX], 2025, a 2024 Chevrolet Traverse was travelling west on [XXX] in Ellsworth, Kansas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact and rollover that deployed airbags and the front seat belt pretensioners. The driver and front passenger were wearing their seat belts at the time of crash. A review of the OnStar audio recordings indicated that the vehicle rolled over, and vehicle occupants claimed minor injuries. Telematics data indicates that Super Cruise was "engaged and active" at the time of the crash. Update: On March 3, 2026, GM received the police report, which states the vehicle was traveling west bound on [XXX] when it crossed the center line into a construction zone and contacted a series of orange traffic cones. The vehicle continued forward and struck yellow sand-filled impact attenuator barrels positioned in front of fixed concrete barriers, then impacted the concrete barriers and rolled approximately one time. In addition to the driver and front passenger, there were two other occupants in the vehicle; their seat belt usage at the time of the crash is unknown. Only minor injuries were reported, and all vehicle occupants declined medical transport from the scene. The vehicle was towed from the crash location.
540-13574Level 2General Motors, LLC2025-12 19:31Amarillo, TX2024 CHEVROLET TraverseVerified EngagedOther, see NarrativeUnknown65Highway / Freeway
On December [XXX], 2025, a 2024 Chevrolet Traverse was travelling west on [XXX] in Amarillo, Texas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt …On December [XXX], 2025, a 2024 Chevrolet Traverse was travelling west on [XXX] in Amarillo, Texas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pretensioners and airbags. The driver and front passenger were wearing their seat belt at the time of crash. A review of the OnStar audio recordings indicated the driver reported that another vehicle pulled out in front of them and they could not stop. Telematics data indicates that Super Cruise entered an "Disabled/Not Ready" state at the time of the crash due to a driver brake apply.
540-13577 v2Level 2General Motors, LLC2025-12 9:02Trumann, AR2024 CHEVROLET TraverseVerified EngagedOther Fixed ObjectNo Injured Reported49Highway / Freeway
On December [XXX], 2025, a 2024 Chevrolet Traverse was travelling southbound on [XXX] in Trumann, Arkansas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front se…On December [XXX], 2025, a 2024 Chevrolet Traverse was travelling southbound on [XXX] in Trumann, Arkansas, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pretensioners and airbags. The driver and front passenger were wearing their seat belts at the time of crash. A review of the OnStar audio recordings indicated a two-vehicle crash. Telematics data indicates that Super Cruise entered a "Disabled/Not Ready" state 2.7 seconds prior to the crash due to a driver brake apply. According to the police report, the subject vehicle was passing another vehicle on the left when the other vehicle swerved into the subject vehicle's lane. The subject vehicle driver steered left to avoid contact and lost control, striking the center median concrete barrier. The subject vehicle did not make contact with the other vehicle.
753-13580 v2Level 2Kia America, Inc.2025-12 02:31Chandler, AZ2025 KIA K4Alleged EngagedPassenger CarModerate W/ Hospitalization55Highway / Freeway
On January 2, 2026, the customer called Kia's Customer Care Center regarding his 2025MY Kia K4, indicating that, on December [XXX], 2025, he was in "an accident because cruise control would not disengage." The customer a…On January 2, 2026, the customer called Kia's Customer Care Center regarding his 2025MY Kia K4, indicating that, on December [XXX], 2025, he was in "an accident because cruise control would not disengage." The customer also indicated that Lane Following Assist was also on. He alleged that while driving, he saw a "red light ahead and I had cruise control on." He attempted to "press on the brakes," but "it didn't take off cruise control even after turning it off." The subject K4 came into contact with a white Ford SUV and the customer reported both drivers sustained injuries. Kia subsequently requested and received from the customer photos and the Arizona Traffic Ticket and Complaint given to the customer. 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. Kia is working with the customer to arrange an inspection of the vehicle. Kia has no further information at this time. **Monthly Update 3/16/2026** After attempting to arrange an inspection of the vehicle, KA learned that the vehicle had been sold and would not be available for inspection. KA has no further information.
945-13455Level 2Nissan North America, Inc.2025-12 21:46Denver, CO2025 NISSAN Ariya MPVVerified EngagedUnknownUnknown21Highway / 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-13203 v4Level 2BMW of North America, LLC2025-11 09:48UNK2025 BMW X3Verified EngagedPole / TreeNo Injured Reported65Highway / FreewayRedacted by NHTSA as confidential business information
1243-13355Level 2Subaru of America, Inc.2025-11 15:43Green Valley, AZ2025 SUBARU AscentAlleged EngagedPassenger CarNo Injured ReportedIntersectionRedacted by NHTSA as confidential business information
1306-13609Level 2Toyota Motor Engineering & Manufacturing2025-11 10:45Valdosta, GA2024 TOYOTA CorollaVerified EngagedOther Fixed ObjectMinor W/O Hospitalization50Intersection
Entries in this report are based on unconfirmed allegations: On November [XXX], 2025, Toyota received initial contact from the mother, calling on behalf of her daughter. She alleged her daughter was involved in an accide…Entries in this report are based on unconfirmed allegations: On November [XXX], 2025, Toyota received initial contact from the mother, calling on behalf of her daughter. She alleged her daughter was involved in an accident where the cruise control on her 2024 Toyota Corolla got stuck and caused her to crash into a ditch. The caller believes there may have been a malfunction with the cruise control. As a result of the crash, the caller alleged that: the airbag deployed there were no serious injuries; and the vehicle was deemed a total loss by the insurance company. On January 9, 2026, Toyota completed a field report based on inspection of the subject vehicle. The field report contained EDR and PCS Freeze Frame Data (PCS FFD) from the crash event. The PCS FFD showed that dynamic radar cruise control (DRCC) and lane trace assist (LTA) were engaged in the recorded moments leading to the crash event. Based on the engagement status of level 2 ADAS in moments leading up to the crash, this report is now being made. The EDR data and PCS FFD confirmed the driver did not apply the brakes until 1.5sec before the airbag deployment. After the brake switch became ON, cruise control and lane centering turned off appropriately, and deceleration was observed consistent with the brake application. The loss of control experienced by the driver and subsequent damage are likely caused by the road speed traveled (50mph in a 35mph speed zone approaching a T-intersection controlled by a stop sign at the intersection) and timing of brake application (1.5 sec before airbag deployment) prior to going through the intersection and off the road. Therefore, this will be the final update for this incident. The customer provided a number for a case with the [XXX]: [XXX].
13781-13050Level 2Tesla, Inc.2025-11 20:13Wills Point, TX2024 TESLA Model YVerified EngagedOther Fixed ObjectUnknown80Highway / FreewayRedacted by NHTSA as confidential business information
13781-13051Level 2Tesla, Inc.2025-11 06:09East Hampton, NY2025 TESLA Model 3Verified EngagedUnknownUnknownUnknownRedacted by NHTSA as confidential business information
13781-13073Level 2Tesla, Inc.2025-11 23:19Newbury Park, CA2023 TESLA Model YVerified EngagedUnknownUnknown19UnknownRedacted by NHTSA as confidential business information
13781-13074Level 2Tesla, Inc.2025-11 16:54Solana Beach, CA2022 TESLA Model XVerified EngagedUnknownUnknown66UnknownRedacted by NHTSA as confidential business information
13781-13075Level 2Tesla, Inc.2025-11 06:21Irvine, CA2025 TESLA Model 3Verified EngagedUnknownUnknown40UnknownRedacted by NHTSA as confidential business information
13781-13076Level 2Tesla, Inc.2025-11 16:39San Rafael, CA2023 TESLA Model YVerified EngagedOther, see NarrativeUnknown14Highway / FreewayRedacted by NHTSA as confidential business information
13781-13077Level 2Tesla, Inc.2025-11 21:43San Ramon, CA2024 TESLA Model YVerified EngagedUnknownUnknown78UnknownRedacted by NHTSA as confidential business information
13781-13078Level 2Tesla, Inc.2025-11 21:59Baldwin Park, CA2023 TESLA Model XVerified EngagedSUVUnknown22Highway / FreewayRedacted by NHTSA as confidential business information
13781-13103Level 2Tesla, Inc.2025-11 00:12San Francisco, CA2026 TESLA Model YVerified EngagedOther, see NarrativeNo Injured Reported3StreetRedacted by NHTSA as confidential business information
13781-13104Level 2Tesla, Inc.2025-11 14:59Redwood City, CA2018 TESLA Model 3Verified EngagedUnknownUnknown58UnknownRedacted by NHTSA as confidential business information
13781-13105Level 2Tesla, Inc.2025-11 14:30Fayetteville, NC2025 TESLA Model YVerified EngagedSUVUnknown8StreetRedacted by NHTSA as confidential business information
13781-13106Level 2Tesla, Inc.2025-11 12:47McLean, VA2026 TESLA Model YVerified EngagedUnknownUnknown23UnknownRedacted by NHTSA as confidential business information
13781-13108Level 2Tesla, Inc.2025-11 22:08Lake Forest, CA2026 TESLA Model YVerified EngagedUnknownUnknown39UnknownRedacted by NHTSA as confidential business information
13781-13109Level 2Tesla, Inc.2025-11 08:59Portland, OR2018 TESLA Model 3Verified EngagedUnknownUnknown55UnknownRedacted by NHTSA as confidential business information
13781-13110Level 2Tesla, Inc.2025-11 16:29Westfield, IN2018 TESLA Model XVerified EngagedUnknownUnknown31UnknownRedacted by NHTSA as confidential business information
13781-13111Level 2Tesla, Inc.2025-11 00:04Powder Springs, GA2023 TESLA Model 3Verified EngagedSUVUnknown47IntersectionRedacted by NHTSA as confidential business information
13781-13112Level 2Tesla, Inc.2025-11 11:53Westminster, CA2025 TESLA Model 3Verified EngagedUnknownUnknown89UnknownRedacted by NHTSA as confidential business information
13781-13113Level 2Tesla, Inc.2025-11 00:07West Harrison, NY2026 TESLA Model YVerified EngagedUnknownUnknown77UnknownRedacted by NHTSA as confidential business information
13781-13114Level 2Tesla, Inc.2025-11 17:30Vale, NC2025 TESLA Model 3Verified EngagedPickup TruckUnknownHighway / FreewayRedacted by NHTSA as confidential business information
13781-13115Level 2Tesla, Inc.2025-11 18:19Miami, FL2026 TESLA Model YVerified EngagedUnknownUnknownUnknownRedacted by NHTSA as confidential business information
13781-13116Level 2Tesla, Inc.2025-11 15:28Nashville, TN2024 TESLA Model 3Verified EngagedUnknownUnknown19UnknownRedacted by NHTSA as confidential business information
13781-13117Level 2Tesla, Inc.2025-11 00:04Richardson, TX2026 TESLA Model YVerified EngagedUnknownUnknown12IntersectionRedacted by NHTSA as confidential business information
13781-13118Level 2Tesla, Inc.2025-11 10:48Brookline, MA2025 TESLA Model XVerified EngagedUnknownUnknown34StreetRedacted by NHTSA as confidential business information
13781-13141Level 2Tesla, Inc.2025-11 23:47Nuevo, CA2024 TESLA CybertruckVerified EngagedUnknownUnknown37Highway / FreewayRedacted by NHTSA as confidential business information
13781-13142Level 2Tesla, Inc.2025-11 22:15Mira Loma, CA2026 TESLA Model YVerified EngagedUnknownUnknown66UnknownRedacted by NHTSA as confidential business information
13781-13143Level 2Tesla, Inc.2025-11 13:54Kansas City, MO2023 TESLA Model 3Verified EngagedUnknownUnknown2StreetRedacted by NHTSA as confidential business information
13781-13145Level 2Tesla, Inc.2025-11 05:40Hopkinton, MA2023 TESLA Model YVerified EngagedUnknownUnknown53Highway / FreewayRedacted by NHTSA as confidential business information
13781-13146Level 2Tesla, Inc.2025-11 22:33Princeton, NJ2026 TESLA Model YVerified EngagedPickup TruckUnknown11IntersectionRedacted by NHTSA as confidential business information
13781-13147Level 2Tesla, Inc.2025-11 16:17Pompano Beach, FL2024 TESLA Model YVerified EngagedUnknownUnknownStreetRedacted by NHTSA as confidential business information
13781-13149Level 2Tesla, Inc.2025-11 01:44San Francisco, CA2026 TESLA Model YVerified EngagedOther, see NarrativeNo Injured Reported0StreetRedacted by NHTSA as confidential business information
13781-13172Level 2Tesla, Inc.2025-11 02:35Grand Prairie, TX2025 TESLA Model 3Verified EngagedSUVUnknown21IntersectionRedacted by NHTSA as confidential business information
13781-13173Level 2Tesla, Inc.2025-11 07:29Escondido, CA2025 TESLA Model YVerified EngagedPassenger CarUnknown74Highway / FreewayRedacted by NHTSA as confidential business information
13781-13174Level 2Tesla, Inc.2025-11 19:56Spring City, PA2026 TESLA Model YVerified EngagedSUVUnknown42Highway / FreewayRedacted by NHTSA as confidential business information
13781-13175Level 2Tesla, Inc.2025-11 15:42Erie, CO2026 TESLA Model YVerified EngagedUnknownUnknown76UnknownRedacted by NHTSA as confidential business information
13781-13176Level 2Tesla, Inc.2025-11 22:13Sunnyvale, CA2025 TESLA Model 3Verified EngagedOther Fixed ObjectUnknown38Highway / FreewayRedacted by NHTSA as confidential business information
13781-13177Level 2Tesla, Inc.2025-11 02:05Fort Scott, KS2018 TESLA Model 3Verified EngagedAnimalUnknown81Highway / FreewayRedacted by NHTSA as confidential business information
13781-13178Level 2Tesla, Inc.2025-11 12:05Riverside, CA2022 TESLA Model SVerified EngagedOther Fixed ObjectUnknown16StreetRedacted by NHTSA as confidential business information
13781-13179Level 2Tesla, Inc.2025-11 13:13Houston, TX2026 TESLA Model YVerified EngagedUnknownUnknown37UnknownRedacted by NHTSA as confidential business information
13781-13180Level 2Tesla, Inc.2025-11 04:33Reno, NV2024 TESLA Model YVerified EngagedUnknownUnknownUnknownRedacted by NHTSA as confidential business information
13781-13181Level 2Tesla, Inc.2025-11 04:20Orlando, FL2022 TESLA Model 3Verified EngagedPassenger CarUnknown58Highway / FreewayRedacted by NHTSA as confidential business information
13781-13182Level 2Tesla, Inc.2025-11 04:11Orange, CA2025 TESLA Model 3Verified EngagedOther Fixed ObjectUnknownHighway / FreewayRedacted 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.