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 3601 to 3700.
| Report ID | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 30270-11571 | ADS | Waymo LLC | 2025-08 22:48 | Phoenix, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 9 | Street | On August [XXX], 2025 at 10:48 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona traveled through standing water on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] when it app…On August [XXX], 2025 at 10:48 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona traveled through standing water on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] when it approached standing water in the Waymo AV's lane of travel. As the Waymo AV traveled through the standing water, the front, rear, and bottom of the Waymo AV made contact with the standing water. 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-11573 | ADS | Waymo LLC | 2025-08 19:02 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Minor W/O Hospitalization | 0 | Street | On August [XXX], 2025 at 7:02 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 parked at the curb facing sou…On August [XXX], 2025 at 7:02 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 parked at the curb facing south on [XXX] with hazard lights activated for a passenger drop-off. While the Waymo AV was parked and the passengers were exiting, an SUV that was parked facing east reversed out of a parking stall on the east side of [XXX] and the rear of the SUV made contact with the rear left 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 preparing to exit the Waymo AV. Two of the Waymo AV passengers alleged minor injuries. 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-11588 | ADS | Waymo LLC | 2025-08 10:54 | Palo Alto, CA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Intersection | On August [XXX], 2025 at 10:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Palo Alto, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] when …On August [XXX], 2025 at 10:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Palo Alto, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling eastbound on [XXX] when it came to a stop for the stop sign at the intersection with [XXX]. An SUV that was traveling behind the Waymo AV approached the Waymo AV from behind and the front right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 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-11589 | ADS | Waymo LLC | 2025-08 02:29 | Daly City, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Intersection | On August [XXX], 2025 at 2:29 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Daly City, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing south on [X…On August [XXX], 2025 at 2:29 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Daly City, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] in the left lane for a red light at the intersection with [XXX]. While the Waymo AV remained stopped for the red light, a passenger car 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. 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 and because of airbag deployment. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-11590 | ADS | Waymo LLC | 2025-08 12:18 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Street | On August [XXX], 2025 at 12:18 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 traveling southbound on [XXX…On August [XXX], 2025 at 12:18 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 traveling southbound on [XXX] when it came to a stop to park in-lane for a passenger drop-off with its hazard lights activated. An SUV that was traveling behind the Waymo AV came to a stop behind the parked Waymo AV. While the Waymo AV remained stationary, the SUV proceeded to maneuver around the left side of the Waymo AV by crossing the double yellow center line and entering the opposing lane of travel. As the SUV passed the stationary Waymo AV the right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. |
| 30270-11591 | ADS | Waymo LLC | 2025-08 11:43 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | Other, see Narrative | Property Damage. No Injured Reported | 22 | Street | On August [XXX], 2025 at 11:43 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California had its rear left wheel separate from the vehicle on [XXX] near [XXX]. The Waymo AV was traveling northe…On August [XXX], 2025 at 11:43 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California had its rear left wheel separate from the vehicle on [XXX] near [XXX]. The Waymo AV was traveling northeastbound in the second to right lane on [XXX] when its left rear wheel separated from the vehicle. The wheel rolled northbound across the southwestbound lanes of [XXX] and entered [XXX], where it made contact with the curb. At the time the wheel separated from the vehicle, 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-11594 | ADS | Waymo LLC | 2025-08 13:32 | Paradise Valley, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 2 | Street | On August [XXX], 2025 at 1:32 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Paradise Valley, Arizona was in a collision involving an automated flagger assistance device on [XXX] near [XXX]. The Waymo AV wa…On August [XXX], 2025 at 1:32 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Paradise Valley, Arizona was in a collision involving an automated flagger assistance device on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] when it came to a stop to yield to an automated flagger assistance device that was positioned near the east curb of [XXX]. The arm of the automated flagger assistance device lowered onto the front of the Waymo AV and then the Waymo AV proceeded forward, making further contact with the arm of the automated flagger assistance device. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The automated flagger assistance device 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-11596 | ADS | Waymo LLC | 2025-08 20:36 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On August [XXX], 2025 at 8:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on…On August [XXX], 2025 at 8:36 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it came to a stop for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, a passenger car 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. 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-11605 | ADS | Waymo LLC | 2025-08 17:25 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | No Injured Reported | 0 | Street | On August [XXX], 2025 at 5:25 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 parked at the curb facing nor…On August [XXX], 2025 at 5:25 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 parked at the curb facing north on [XXX] for a passenger drop-off with hazard lights activated. An SUV was traveling northbound on [XXX]. As the SUV approached the parked Waymo AV, a Waymo AV passenger opened the rear left door and the right side of the SUV made contact with the open left rear door of the stopped 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 preparing to exit the Waymo AV. 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-11607 | ADS | Waymo LLC | 2025-08 19:34 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 8 | Street | On August [XXX], 2025 at 7:34 PM 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 stopped facing west …On August [XXX], 2025 at 7:34 PM 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 stopped facing west at the curb on the north side of [XXX] after a passenger drop-off. At the same time, a passenger car was traveling westbound within a queue of traffic in the adjacent lane. The Waymo AV then proceeded to maneuver forward and to the left to exit the parking spot and merge into a gap in the traffic queue ahead of the passenger car. The passenger car continued to proceed forward, and the front right side of the passenger car 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-11611 | ADS | Waymo LLC | 2025-08 12:15 | Phoenix, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 2 | Street | On August [XXX], 2025 at 12:15 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX]…On August [XXX], 2025 at 12:15 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the second from the right lane when it began to change lanes to the rightmost lane. As the Waymo AV was completing the lane change maneuver, a pickup truck that was stopped in the rightmost lane facing north behind and to the right of the Waymo AV proceeded forward, and the front of the pickup truck 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-11621 | ADS | Waymo LLC | 2025-08 21:21 | Phoenix, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 32 | Intersection | On August [XXX], 2025 at 9:21 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] i…On August [XXX], 2025 at 9:21 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the leftmost lane. As the Waymo AV continued to proceed straight as it approached a green light at the intersection at [XXX], a passenger car traveling southbound in the adjacent, second to the leftmost lane, attempted to turn left and entered into the Waymo AV's lane of travel. The front left side 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-11622 | ADS | Waymo LLC | 2025-08 21:37 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Intersection | On August [XXX], 2025 at 9: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 [XXX]. The Waymo AV was stopped facing east in…On August [XXX], 2025 at 9: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 [XXX]. The Waymo AV was stopped facing east in the right turn lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped for the red light, a passenger car traveling eastbound on [XXX] 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 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-11671 | ADS | Waymo LLC | 2025-08 22:57 | Culver City, CA | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 3 | Street | On August [XXX], 2025 at 10:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Culver City, California was in a collision involving a pickup truck with a flatbed trailer on [XXX] near [XXX]. The Waymo AV was…On August [XXX], 2025 at 10:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Culver City, California was in a collision involving a pickup truck with a flatbed trailer on [XXX] near [XXX]. The Waymo AV was parked at the curb facing west on [XXX] and a pickup truck with an attached flatbed trailer was parked in front of the Waymo AV. The Waymo AV proceeded forward and to the left to exit the parking spot, and the front right side of the Waymo AV made contact with the left rear side of the flatbed. 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-11673 | ADS | Waymo LLC | 2025-08 15:05 | Scottsdale, AZ | 2024 JAGUAR I-PACE | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Street | On August [XXX], 2025 at 3:05 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] in the …On August [XXX], 2025 at 3:05 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] in the right turn lane behind a passenger car waiting to turn right at a stop sign at the intersection with [XXX]. An SUV initially stopped behind the Waymo AV began to proceed 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-11765 | ADS | Waymo LLC | 2025-08 23:03 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Street | On August [XXX], 2025 at 11:03 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west on…On August [XXX], 2025 at 11:03 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing west on [XXX] for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, a passenger car 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. Waymo became aware of damage to the Waymo AV exceeding $1,000 on September 17, 2025. 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-11595 | ADS | Nuro | 2025-08 10:45 | Houston, TX | 2022 TOYOTA Prius | Verified Not Engaged | Passenger Car | Property Damage. No Injured Reported | 0 | Intersection | On August [XXX], 2025, one of Nuro's Prius vehicles operating in manual mode in the Houston area was struck from behind while yielding to cross-traffic at an intersection. The vehicle had been operating in autonomous mo…On August [XXX], 2025, one of Nuro's Prius vehicles operating in manual mode in the Houston area was struck from behind while yielding to cross-traffic at an intersection. The vehicle had been operating in autonomous mode within 30 seconds prior to the incident, but the operator had disengaged autonomy several seconds prior to reaching the intersection. No injuries resulted from this incident, although there was minor property damage to both vehicles. |
| 30413-11593 v2 | ADS | May Mobility | 2025-08 11:35 | Peachtree Corners, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | Minor W/O Hospitalization | 13 | Intersection | The May vehicle was travelling in an autonomous vehicle (AV) only lane approaching an intersection. A vehicle travelling to the left of the May shuttle (ego) in the non-AV lane performed a right hand turn across the May…The May vehicle was travelling in an autonomous vehicle (AV) only lane approaching an intersection. A vehicle travelling to the left of the May shuttle (ego) in the non-AV lane performed a right hand turn across the May vehicle¢ÃÂÃÂs path. Given the full stopping power and the limited space with which the ego had to stop, the ego was physically unable to stop in time before impact. The primary factor that led to this collision was human error on the part of the other vehicle that was required to yield to through traffic in the AV lane but did not. Right turns across a straight lane are uncommon, and drivers are typically not used to them, however there are several signs that instruct other traffic to yield to the vehicles in the AV lane. There were no autonomy faults or errors which led to this incident. Update: There was no indication of injury or request for medical attention at the scene. The police report states "Driver 1 complained of neck pain." For this reason, we are updating the highest severity injury alleged field to reflect the âminor w/o hospitalizationâ injury level. The remaining content of this report is unchanged from the initial report submitted on September [XXX], 2025, Report ID #[XXX]. |
| 30413-11669 | ADS | May Mobility | 2025-08 18:08 | Eden Prairie, MN | 2023 TOYOTA Sienna | Verified Engaged | Pickup Truck | No Injured Reported | 13 | Intersection | A May autonomous shuttle (Ego) is passing through an intersection. A vehicle sensor detects a false positive as a pedestrian moving toward the May vehicles path in a region closely behind another vehicle. This causes…A May autonomous shuttle (Ego) is passing through an intersection. A vehicle sensor detects a false positive as a pedestrian moving toward the May vehicles path in a region closely behind another vehicle. This causes the May vehicle to stop to allow it to safely pass. A following agent (still accelerating at the time of the impact) collides with the May vehicle one second after we come to a stop. Re-simulation on newer software shows that routine software improvements resolved this issue and the commercial May software has been updated to this release. |
| 30490-11693 | ADS | Beep, Inc. | 2025-08 12:10 | Jacksonville, FL | 2022 FORD Transit | Verified Not Engaged | Pole / Tree | Property Damage. No Injured Reported | 25 | Street | On August [XXX], 2025, a Beep-operated Ford E-Transit (002B) equipped with an automated driving system developed by Oxa Autonomy Ltd. was involved in a collision with a stationary object in Jacksonville, FL. While navig…On August [XXX], 2025, a Beep-operated Ford E-Transit (002B) equipped with an automated driving system developed by Oxa Autonomy Ltd. was involved in a collision with a stationary object in Jacksonville, FL. While navigating westbound on [XXX] along a predefined route, vehicle 002B began to slowly veer towards the right curb. The vehicle eventually climbed the curb with the right front and rear wheels and the passenger-side mirror contacted a stationary light pole. There was one passenger onboard at the time of the incident, an employee of the Jacksonville Transportation Authority. There were no reported injuries, and the vehicle was driven from the scene. Review of the automated driving system logs as well as onboard video footage determined that the operator disengaged the automated driving system 7.5 seconds prior to the vehicle mounting the curb. Further examination of the onboard video footage noted that the operator appeared to be drowsy and inattentive prior to the incident. Beep confirmed that the operators shift was in compliance with anti-fatigue policies for this operation. The operator was referred for a post-accident drug and alcohol testing following the incident and tested negative for any impairment. Following the conclusion of the investigation into this incident, the operator was separated from employment. |
| 30530-11597 | ADS | Aurora Operations, Inc. | 2025-08 10:55 | Strawn, TX | 2024 PETERBILT 579 | Verified Not Engaged | Heavy Truck | Property Damage. No Injured Reported | 7 | Highway / Freeway | At approximately 10:55 AM CST on August [XXX], 2025, an Aurora truck was traveling westbound on [XXX] in autonomy during a development mission with an Aurora vehicle operator near Stephenville, Texas. The Aurora truck …At approximately 10:55 AM CST on August [XXX], 2025, an Aurora truck was traveling westbound on [XXX] in autonomy during a development mission with an Aurora vehicle operator near Stephenville, Texas. The Aurora truck was in the right lane and approaching an unmarked right-lane closure with no advance warning signs. The Aurora vehicle operator decided to disengage autonomy and attempted to manually merge the Aurora truck into the left lane. During the vehicle operators manual lane change, a passing tractor trailer sped up on the left and made contact with the Aurora truck. The Aurora vehicle operator attempted to alert the other tractor trailer of the impact to the Aurora truck by honking the horn and flashing lights. However, the passing tractor trailer proceeded without stopping, and after being unable to gain the other drivers attention, the Aurora vehicle operator pulled over to the shoulder of the highway to assess damage to the Aurora truck. The Aurora vehicle operator reported damage to the trucks left side mirror and sensor equipment to Auroras dispatch before returning to Auroras terminal in Aledo, Texas. No injuries were reported. |
| 30610-11497 | ADS | Zoox, Inc. | 2025-08 18:16 | San Francisco, CA | 2026 ZOOX Zoox | Verified Engaged | SUV | Property Damage. No Injured Reported | 0 | Street | An unoccupied Zoox vehicle in autonomy was traveling north on [XXX] toward [XXX] in San Francisco and slowing for an SUV (Vehicle 2) ahead, also heading north on [XXX]. As the Zoox vehicle approached the nearly stopped V…An unoccupied Zoox vehicle in autonomy was traveling north on [XXX] toward [XXX] in San Francisco and slowing for an SUV (Vehicle 2) ahead, also heading north on [XXX]. As the Zoox vehicle approached the nearly stopped Vehicle 2, it steered left to pass. The driver of Vehicle 2 then, without using a turn signal, abruptly began reversing in an apparent attempt to parallel park on the right side of [XXX]. The Zoox vehicle then braked to a near stop when it was struck on the right rear wheel by Vehicle 2 as it swung into a parking space. Shortly afterward, the Zoox vehicle was towed from the scene for inspection. The Zoox vehicle did not sustain damage, but the left front bumper of the SUV appeared to have minor damage. There were no reported injuries, and the police were not called. |
| 30610-11563 | ADS | Zoox, Inc. | 2025-08 15:11 | San Francisco, CA | 2026 ZOOX Zoox | Verified Engaged | Pickup Truck | Property Damage. No Injured Reported | 0 | Street | An unoccupied Zoox autonomous vehicle was stopped at a green traffic light on eastbound [XXX], waiting for traffic ahead to clear to turn left onto [XXX] in San Francisco. A pickup truck (Vehicle 2) was also stopped for …An unoccupied Zoox autonomous vehicle was stopped at a green traffic light on eastbound [XXX], waiting for traffic ahead to clear to turn left onto [XXX] in San Francisco. A pickup truck (Vehicle 2) was also stopped for the same traffic light, directly behind the Zoox vehicle. After the light turned yellow, the Vehicle 2 driver passed the stopped Zoox vehicle on the left side, striking the left rear fender, and proceeded through the red light. The Vehicle 2 driver did not stop to exchange information. Shortly afterward, the Zoox vehicle turned left onto [XXX] to clear the scene, briefly stopped again, and then pulled over. The Zoox vehicle was then towed for inspection. It sustained minor damage. There were no reported injuries and the police were not called. |
| 30610-11587 | ADS | Zoox, Inc. | 2025-08 16:47 | Spring Valley, NV | 2024 ZOOX Zoox | Verified Engaged | Heavy Truck | Property Damage. No Injured Reported | 11 | Street | An unoccupied Zoox autonomous vehicle was traveling west along [XXX] toward [XXX] in Las Vegas when a tractor-trailer (Vehicle 2) operator failed to yield the right-of-way, failed to stop at a stop sign, and quickly pull…An unoccupied Zoox autonomous vehicle was traveling west along [XXX] toward [XXX] in Las Vegas when a tractor-trailer (Vehicle 2) operator failed to yield the right-of-way, failed to stop at a stop sign, and quickly pulled out of a driveway crossing the centerline and entering the Zoox vehicle's travel lane in an apparent attempt to make a left turn onto westbound [XXX]. The Zoox vehicle braked hard and steered right within its travel lane, but contact was unavoidable. The right corner of the front bumper and grille of the tractor-trailer made contact with the left front side of the Zoox vehicle. The Zoox vehicle then came to a complete stop. The operator of Vehicle 2 reversed off the roadway and stayed on-site to exchange information with the Zoox operations team. The Zoox vehicle was towed from the scene for inspection and was found to have sustained moderate damage. The front bumper, hood, and grille on Vehicle 2 appeared to be damaged. There were no reported injuries, and the police were not called. |
| 30610-11696 | ADS | Zoox, Inc. | 2025-08 09:11 | Santa Monica, CA | 2019 TOYOTA Highlander | Verified Engaged | SUV | Property Damage. No Injured Reported | 10 | Street | A Zoox vehicle (Vehicle 1) in autonomous mode was traveling southwest on [XXX] towards [XXX] in Santa Monica when it was struck on the passenger side by an SUV (Vehicle 2), traveling southeast on [XXX], which failed to y…A Zoox vehicle (Vehicle 1) in autonomous mode was traveling southwest on [XXX] towards [XXX] in Santa Monica when it was struck on the passenger side by an SUV (Vehicle 2), traveling southeast on [XXX], which failed to yield the right-of-way and entered the Zoox vehicle's travel path. The Zoox vehicle braked, the vehicle operator disengaged, continued to brake, and steered left, but contact was unavoidable. The Zoox vehicle sustained moderate damage, and Vehicle 2 also sustained damage. There were no reported injuries, and the police were not notified. |
| 33257-11549 | OTHER | VinFast Auto, LLC | 2025-08 10:05 | Suyu District, Suqian, Jiangsu, China, PW | 2023 VINFAST VF 8 | Unknown - see Narrative | SUV | Minor W/O Hospitalization | 50 | Highway / Freeway | This occurred while the Subject Vehicle (SV) was accelerating off [XXX] ([XXX]) onto [XXX] during lane change and rear-ended another vehicle. SV was damaged and required towing from the scene, incident vehicle was able …This occurred while the Subject Vehicle (SV) was accelerating off [XXX] ([XXX]) onto [XXX] during lane change and rear-ended another vehicle. SV was damaged and required towing from the scene, incident vehicle was able to leave the scene under its own power. SV driver sustained minor injuries to the hands and underwent X-Ray examination. Driver alleged VF8 brakes may not have functioned properly at the time of the accident. VinFast internal investigation identified the SV Service Brake was not pressed prior to contact with incident vehicle. |
| 34970-11835 | ADS | Ohmio, Inc. | 2025-08 12:41 | Riverside, CA | 2024 Ohmio LIFT | Unknown - see Narrative | SUV | Minor W/O Hospitalization | 15 | Street | The [XXX] was driving on [XXX] towards [XXX] in Riverside California. A minivan reversed out of a parking position (perpendicular parking to road lane) from the right side of the road into the shuttle¢ÂÂs path and stru…The [XXX] was driving on [XXX] towards [XXX] in Riverside California. A minivan reversed out of a parking position (perpendicular parking to road lane) from the right side of the road into the shuttle¢ÂÂs path and struck the shuttle from the side. After the incident a supervisor from the Riverside Transport Agency RTA (operator or the vehicle) was called to the side. The RTA supervisor recorded the incident according to RTAs protocols. In addition to the [XXX] trainer/supervisor being on the vehicle additional [XXX] personal was called to the side as well. Summary of Events: -Upon detecting the minivan in the side envelope, the system issued a brake command within 5ms. -Brake pressure began rising 58ms after the command and exceeded 90% of the requested pressure 164ms after the initial command. -The minivan reversed out of a parking space perpendicular to the [XXX] âÂÂs direction of travel and struck the Lift on the side. -The minivan continued reversing until contact occurred. -The elapsed time from first detection of the minivan in the side envelope to impact was approximately 358ms. -The vehicle came to a complete stop in 1.178 seconds. In Summary: The other car pushing out from the parking position did not give way as would have been required. The [XXX] detected the other car getting into the right side of its safety envelope just 358ms before the impact. The reaction time of the [XXX] was as expected in terms of reacting to the signal and initiating a brake maneuver. However, the short time and distance between the other car entering the [XXX] safety envelope (and consequently its track) was too short to avoid the collision. Even if the [XXX] had come to a complete stop before the actual impact the collision would most likely have happened but potentially at a slightly different position. |
| 540-11429 | Level 2 | General Motors, LLC | 2025-08 02:14 | Thoreau, NM | 2025 GMC Yukon XL | Verified Engaged | Animal | Unknown | 78 | Highway / Freeway | On August [XXX], 2025, a 2025 GMC Yukon XL was traveling west on [XXX] in Thoreau, New Mexico with Super Cruise engaged and active. Crash data indicates a frontal impact resulting in deployment of the front airbags and …On August [XXX], 2025, a 2025 GMC Yukon XL was traveling west on [XXX] in Thoreau, New Mexico with Super Cruise engaged and active. Crash data indicates a frontal impact resulting in deployment of the front airbags and seat belt pretensioners. Crash data also indicates that the driver seat belt was buckled prior to the crash. According to OnStar recordings, the driver reported his vehicle struck an elk that crossed in front of the vehicle. Telematics data also shows that approximately 1 second prior to the crash, Super Cruise entered a "Disabled/Not Ready" state due to a brake pedal press. |
| 540-11453 | Level 2 | General Motors, LLC | 2025-08 13:30 | Glastonbury, CT | 2025 BUICK Enclave | Verified Engaged | Unknown | Unknown | 63 | Highway / Freeway | On August [XXX], 2025, a 2025 Buick Enclave was traveling west in the right lane on [XXX] in Glastonbury, Connecticut with Super Cruise engaged and active. Crash data indicates a low-level impact that did not deploy air…On August [XXX], 2025, a 2025 Buick Enclave was traveling west in the right lane on [XXX] in Glastonbury, Connecticut with Super Cruise engaged and active. Crash data indicates a low-level impact that did not deploy airbags or seat belt pretensioners. According to OnStar recordings, the driver reported her vehicle was rear-ended by another vehicle whose airbag deployed. Telematics data also shows that approximately 1 second prior to the crash, Super Cruise entered a "Disabled/Not Ready" state due to a brake pedal press. |
| 540-11494 | Level 2 | General Motors, LLC | 2025-08 21:57 | Houston, TX | 2022 CHEVROLET Bolt EUV | Verified Engaged | Unknown | Unknown | 62 | Highway / Freeway | On August [XXX], 2025, a Chevrolet Bolt EUV was traveling eastbound on [XXX] ([XXX]) in Houston, Texas, with Super Cruise engaged and active. After exiting the highway, crash data indicated that the vehicle experienced …On August [XXX], 2025, a Chevrolet Bolt EUV was traveling eastbound on [XXX] ([XXX]) in Houston, Texas, with Super Cruise engaged and active. After exiting the highway, crash data indicated that the vehicle experienced two frontal impacts, which resulted in the deployment of the front seat belt pretensioners and airbags. Both the driver and front passenger were wearing their seatbelts at the time of the crash. The specific object(s) impacted by the vehicle are unknown. Telematics data shows that Super Cruise entered a "Disabled/Not Ready" state 23 seconds prior to the crash due to a driver takeover. |
| 540-11510 | Level 2 | General Motors, LLC | 2025-08 16:53 | Ventura, CA | 2024 CADILLAC Lyriq | Verified Engaged | Unknown | Unknown | 66 | Highway / Freeway | On August [XXX], 2025, a Cadillac Lyriq was traveling northbound on highway CA-33 in Ventura, California, with Super Cruise engaged and active. Crash data indicates a frontal impact occurred that deployed the front seat…On August [XXX], 2025, a Cadillac Lyriq was traveling northbound on highway CA-33 in Ventura, California, with Super Cruise engaged and active. Crash data indicates 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. The specific object(s) impacted by the vehicle are unknown. Telematics data shows that Super Cruise entered a "Disabled/Not Ready" state 2 seconds prior to the crash due to a driver takeover. |
| 540-11551 | Level 2 | General Motors, LLC | 2025-08 23:51 | Laughlin, NV | 2025 GMC Sierra | Verified Engaged | Passenger Car | Unknown | 48 | Highway / Freeway | On August [XXX], 2025, a 2025 Sierra was traveling eastbound on [XXX] in Laughlin, Nevada, with Super Cruise engaged and active. Crash data indicates there was a left-side impact and rollover that deployed the front sea…On August [XXX], 2025, a 2025 Sierra was traveling eastbound on [XXX] in Laughlin, Nevada, with Super Cruise engaged and active. Crash data indicates there was a left-side impact and rollover that deployed the front seat belt pretensioners and airbags. The driver and passenger were wearing seat belts at the time of the crash. According to OnStar audio recordings, the driver reported that another vehicle was traveling the wrong way on the highway and hit them. Telematics data shows that Super Cruise entered an "Override" state at 2.7 seconds prior to the crash due to detection of hands on the wheel and steering wheel torque, followed by a "Disabled/Not Ready" state at 2.2 sec prior to the crash due to a brake pedal press. |
| 540-11552 | Level 2 | General Motors, LLC | 2025-08 19:59 | Petersburg, VA | 2025 CHEVROLET Traverse | Verified Engaged | Other Fixed Object | Unknown | 70 | Highway / Freeway | On August [XXX], 2025, a 2025 Traverse was traveling southbound on [XXX] in Petersburg, VA, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pretens…On August [XXX], 2025, a 2025 Traverse was traveling southbound on [XXX] in Petersburg, VA, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pretensioners and airbags. The passenger was wearing their seat belt at the time of the crash. The driver was not. According to OnStar audio recordings, the driver reported that they lost control of the vehicle and swerved off the highway and hit a guardrail. Telematics data shows that Super Cruise entered an "Override" state at 1 second prior to the crash due to detection of hands on the wheel and steering wheel torque, followed shortly by a "Degraded Escalation" due to the driver seat belt being unbuckled. This was immediately followed by a "Disabled/Not Ready" state due to a driver takeover. |
| 540-11566 | Level 2 | General Motors, LLC | 2025-08 13:32 | Thornton, CO | 2025 GMC Hummer EV Pickup | Verified Engaged | Unknown | Unknown | 36 | Highway / Freeway | On August [XXX], 2025, a 2025 Hummer EV was traveling northbound on [XXX] in Broomfield, Colorado, with Super Cruise engaged and active. According to OnStar audio recordings, the driver reported being rear-ended by anot…On August [XXX], 2025, a 2025 Hummer EV was traveling northbound on [XXX] in Broomfield, Colorado, with Super Cruise engaged and active. According to OnStar audio recordings, the driver reported being rear-ended by another vehicle, and that the airbags deployed in the other vehicle. Telematics data indicates that Super Cruise entered a "Degraded Escalation" state 14 seconds prior to the crash due to a forward collision alert, which was immediately followed by a "Disabled/Not Ready" state as a result of a driver takeover. |
| 540-11570 | Level 2 | General Motors, LLC | 2025-08 07:17 | Port Orchard, WA | 2025 CHEVROLET Blazer | Verified Engaged | Other, see Narrative | No Injured Reported | 20 | Highway / Freeway | On August [XXX], 2025, a 2025 Chevrolet Blazer EV was travelling southwest on [XXX] in Port Orchard, Washington, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the fr…On August [XXX], 2025, a 2025 Chevrolet Blazer EV was travelling southwest on [XXX] in Port Orchard, Washington, with Super Cruise engaged and active. Crash data indicates there was a frontal impact that deployed the front seat belt pretensioners and driver airbag. The driver was wearing their seat belt at the time of crash. According to OnStar audio recordings, the vehicle hit a stationary construction truck trailer. Telematics data indicates Super Cruise was engaged and active at the time of the crash. |
| 540-11606 | Level 2 | General Motors, LLC | 2025-08 16:32 | Niceville, FL | 2023 CADILLAC CT5 | Verified Engaged | Unknown | Unknown | 64 | Highway / Freeway | On August [XXX], 2025, a Cadillac CT5-V was traveling southbound on [XXX] in Eglin Air Force Base, Florida, with Super Cruise engaged and active. Crash data indicates rear and side impacts occurred that deployed airbags…On August [XXX], 2025, a Cadillac CT5-V was traveling southbound on [XXX] in Eglin Air Force Base, Florida, with Super Cruise engaged and active. Crash data indicates rear and side impacts occurred that deployed airbags and front seat belt pretensioners. The driver was wearing a seat belt at the time of the crash. The cause of the impacts remains undetermined. Telematics data shows that Super Cruise entered a "Disabled/Not Ready" state 7 seconds prior to the crash due to a brake press, hands detected on the steering wheel and an applied steering wheel torque. |
| 753-11524 | Level 2 | Kia America, Inc. | 2025-08 10:40 | Rancho Santa Fe, CA | 2024 KIA Niro | Verified Engaged | Pole / Tree | Moderate W/ Hospitalization | 45 | Highway / Freeway | On [XXX], the customer called Kias Customer Care Center regarding her 2024MY Kia Niro, indicating that her daughter had a malfunction with the drivers lane assist on the vehicle. The customer reported that her daughter …On [XXX], the customer called Kias Customer Care Center regarding her 2024MY Kia Niro, indicating that her daughter had a malfunction with the drivers lane assist on the vehicle. The customer reported that her daughter got off the highway and forgot to turn off HDA and picked up cyclists as veh[REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. The vehicle started following [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] to the right with lane detection, but when [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] went to turn off, she was unable to and it forced my veh[REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION] to hit a tree in a ditch. She reported that her daughter was transported to the hospital after the incident and had sustained bruises, limited mobility, and stitches to the back of her head. She requested the black box for the vehicle. In addition, the customer suggested that before the accident, her daughter had taken the vehicle to a Kia dealership with a concern about the HDA and the dealership identified no concerns. The subject Kia Niro is equipped with Highway Drive Assist (HDA), LFA, and 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. The functionality of LFA is contingent upon several outside factors and it is always the responsibility of the driver to safely steer the vehicle and to maintain the vehicle in its lane. Kia confirmed that Smart Cruise Control (SCC) and Lane Following Assist (LFA) were active from approximately 19 seconds to 7 seconds prior to the collision. At 7 seconds pre-collision, LFA was disengaged. Kia is currently working to obtain additional information to evaluate this incident. |
| 855-11626 v2 | Level 2 | Mercedes-Benz USA, LLC | 2025-08 01:21 | Dallas, TX | 2024 MERCEDES-BENZ EQE-Class Sedan | Alleged Engaged | Other Fixed Object | No Injured Reported | 63 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 945-11574 v2 | Level 2 | Nissan North America, Inc. | 2025-08 13:30 | 2021 INFINITI QX50 | Alleged Engaged | SUV | Minor W/O Hospitalization | 78 | Street | The information contained in this report is based on Nissan's understanding of the allegations received during Claimant's discussions with Nissan's Consumer Affairs representatives and Nissan's preliminary vehicle inspec…The information contained in this report is based on Nissan's understanding of the allegations received during Claimant's discussions with Nissan's Consumer Affairs representatives and Nissan's preliminary vehicle inspection. On 8/21/25 claimant notified Nissan Consumer Affairs of an accident which reportedly occurred on 8/[XXX]/25. The Claimant stated that the Claimant's son was driving the vehicle with "cruise assist" on with both hands on the wheel. Claimant stated the vehicle steered to the left on its own, colliding with oncoming traffic. Claimant was not hospitalized immediately after the incident but visited a physician on 8/20/25. Claimant states that the son sustained injuries to both hands and was concussed. On 8/27/25, Nissan received the allegation that a curtain air bag had deployed during the incident and that claimant's son was hospitalized. On 9/4/25, Nissan inspected the vehicle. Primary vehicle damage was observed in the left front corner and proceeding down the left side of the vehicle. The left curtain, the driver, and the passenger knee airbags were deployed as a result of the impact. EDR data gathered from the vehicle did not support the claimant's allegations of the vehicle steering to the left proir to the incident. On 9/10/25, Nissan requested a copy of the police report from the claimant. The claimant informed Nissan that they had already settled with the insurance company and that the investigation "would no longer be applicable." | |
| 1243-11470 v2 | Level 2 | Subaru of America, Inc. | 2025-07 15:23 | Falmouth, ME | 2023 SUBARU Outback | Alleged Engaged | Other, see Narrative | Minor W/ Hospitalization | 65 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 1306-11380 v3 | Level 2 | Toyota Motor Engineering & Manufacturing | 2025-07 00:15 | CA | 2024 TOYOTA RAV4 | Verified Not Engaged | Other Fixed Object | Serious W/ Hospitalization | 71 | Highway / Freeway | From original report (July 25, 2025): Entries in this report are based on unconfirmed allegations: On July [XXX], 2025, Toyota received an initial contact from the driver of a rental vehicle involved in the crash. The d…From original report (July 25, 2025): Entries in this report are based on unconfirmed allegations: On July [XXX], 2025, Toyota received an initial contact from the driver of a rental vehicle involved in the crash. The driver described that cruise control was engaged with lane trace assist/lane departure assist and pre-collision system turned on leading up to the crash event. The driver alleged that while driving on a highway, the lane trace assist/lane departure assist failed to engage and keep vehicle within lanes, and the PCS failed to detect the median of the freeway and slow down the vehicle before impact. The driver stated he noticed twice before the incident the lane trace assist/lane departure would keep the vehicle in the lane. The driver stated the third time, the vehicle drifted out of the lane, and the driver side of the vehicle impacted the freeway median. The driver alleged the driver assistance features did not function properly and failed to prevent the accident. As a result of the crash, the driver alleged that: the airbags deployed; there was significant damage to the front driver's side of the vehicle, including the wheel, tire, bumper, and fender; one of the five occupants seated in the left rear position sustained injuries to her left rib cage that required emergency room treatment (seat belt use unknown); and the vehicle was towed from the scene and deemed a total loss. The driver stated the California Highway Patrol responded to the crash and provided report numbers "NCIC - 9650". From Update Report (September 15, 2025): On August 28, 2025, Toyota completed vehicle inspection field report related to the crash event and obtained the Event Data Recorder (EDR) record. The record indicated that the vehicle's Dynamic Radar Cruise Control (DRCC) was engaged in the recorded moments leading up to the crash event. Toyota is investigating the Lane Tracing Assist (LTA) engagement status, and the timing of driver inputs related to steering, acceleration, and braking. This information will be provided in a future update. Minor revisions to information in the report fields above were made based on factual information obtained from the field report and EDR record. From Update Report (May 15, 2026): On May 12, 2026, following review of the available vehicle data, Toyota determined the LTA function was not active in the recorded moments (8 seconds) leading up to the crash, therefore the vehicle was not in an ADAS L2 state. This will be the final update for this incident. |
| 13781-11289 | Level 2 | Tesla, Inc. | 2025-07 12:45 | Austin, TX | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 7 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11290 | Level 2 | Tesla, Inc. | 2025-07 22:09 | Edison, NJ | 2024 TESLA Model X | Verified Engaged | Unknown | Unknown | 4 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11293 | Level 2 | Tesla, Inc. | 2025-07 01:24 | Flowery Branch, GA | 2026 TESLA Model Y | Verified Engaged | Other Fixed Object | Property Damage. No Injured Reported | 46 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-11304 | Level 2 | Tesla, Inc. | 2025-07 21:06 | Charlotte, NC | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 74 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11305 | Level 2 | Tesla, Inc. | 2025-07 01:37 | Miami, FL | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 15 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-11306 | Level 2 | Tesla, Inc. | 2025-07 02:50 | Tallahassee, FL | 2025 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 27 | Street | Redacted by NHTSA as confidential business information |
| 13781-11307 | Level 2 | Tesla, Inc. | 2025-07 09:19 | Harrison, OH | 2023 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 19 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-11308 | Level 2 | Tesla, Inc. | 2025-07 04:25 | Charlotte, NC | 2025 TESLA Model 3 | Verified Engaged | Pole / Tree | Unknown | 43 | Street | Redacted by NHTSA as confidential business information |
| 13781-11309 | Level 2 | Tesla, Inc. | 2025-07 01:07 | San Francisco, CA | 2022 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 22 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11310 | Level 2 | Tesla, Inc. | 2025-07 20:12 | Bethlehem,, PA | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 9 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11311 | Level 2 | Tesla, Inc. | 2025-07 11:42 | Santa Clarita, CA | 2020 TESLA Model 3 | Verified Engaged | SUV | Unknown | 105 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11312 | Level 2 | Tesla, Inc. | 2025-07 18:44 | Hialeah, FL | 2024 TESLA Model 3 | Verified Engaged | Unknown | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-11313 | Level 2 | Tesla, Inc. | 2025-07 23:00 | Carrollton, TX | 2023 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-11314 | Level 2 | Tesla, Inc. | 2025-07 21:30 | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 21 | Street | Redacted by NHTSA as confidential business information | |
| 13781-11315 | Level 2 | Tesla, Inc. | 2025-07 06:56 | Los Angeles, CA | 2023 TESLA Model Y | Verified Engaged | Passenger Car | Unknown | 72 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11316 | Level 2 | Tesla, Inc. | 2025-07 02:29 | Hacienda Heights, CA | 2023 TESLA Model X | Verified Engaged | Unknown | Unknown | 56 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11317 | Level 2 | Tesla, Inc. | 2025-07 02:04 | Westminster, CA | 2024 TESLA Model Y | Verified Engaged | Other, see Narrative | Unknown | 75 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11318 | Level 2 | Tesla, Inc. | 2025-07 22:54 | Buena Vista Township, NJ | 2019 TESLA Model 3 | Verified Engaged | Unknown | Fatality | 4 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11319 v2 | Level 2 | Tesla, Inc. | 2025-07 04:44 | Sayreville, NJ | 2018 TESLA Model 3 | Verified Engaged | Unknown | Fatality | 102 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11320 v2 | Level 2 | Tesla, Inc. | 2025-07 11:32 | Chaney Ranch, CA | 2021 TESLA Model Y | Verified Engaged | Other Fixed Object | Minor W/O Hospitalization | 69 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11339 | Level 2 | Tesla, Inc. | 2025-07 17:56 | League City, TX | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11340 | Level 2 | Tesla, Inc. | 2025-07 09:41 | New Franklin, OH | 2019 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 43 | Street | Redacted by NHTSA as confidential business information |
| 13781-11341 | Level 2 | Tesla, Inc. | 2025-07 16:54 | Yonkers, NY | 2026 TESLA Model Y | Verified Engaged | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11342 | Level 2 | Tesla, Inc. | 2025-07 19:44 | West Alton, MO | 2022 TESLA Model Y | Verified Engaged | Unknown | Unknown | Unknown | Redacted by NHTSA as confidential business information | |
| 13781-11347 | Level 2 | Tesla, Inc. | 2025-07 21:46 | Mansfield, PA | 2023 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-11348 | Level 2 | Tesla, Inc. | 2025-07 11:15 | Mountain View, CA | 2021 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 39 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11349 | Level 2 | Tesla, Inc. | 2025-07 05:47 | Reno, NV | 2021 TESLA Model X | Verified Engaged | Other Fixed Object | Unknown | 24 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-11350 | Level 2 | Tesla, Inc. | 2025-07 21:43 | Mequon, WI | 2023 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 67 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11351 | Level 2 | Tesla, Inc. | 2025-07 21:50 | Carnot-Moon, PA | 2021 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 23 | Street | Redacted by NHTSA as confidential business information |
| 13781-11352 | Level 2 | Tesla, Inc. | 2025-07 16:53 | Round Rock, TX | 2023 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 26 | Street | Redacted by NHTSA as confidential business information |
| 13781-11353 | Level 2 | Tesla, Inc. | 2025-07 22:22 | Murrieta, CA | 2019 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 9 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11354 | Level 2 | Tesla, Inc. | 2025-07 20:38 | Las Vegas, NV | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 15 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11355 | Level 2 | Tesla, Inc. | 2025-07 19:40 | Springfield, NJ | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 33 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11356 | Level 2 | Tesla, Inc. | 2025-07 00:14 | Alhambra, CA | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 27 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11357 | Level 2 | Tesla, Inc. | 2025-07 22:08 | Manchester Township, NJ | 2022 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 45 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11368 | Level 2 | Tesla, Inc. | 2025-07 11:15 | Hartford, CT | 2025 TESLA Model 3 | Verified Engaged | Other, see Narrative | Unknown | 46 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11369 | Level 2 | Tesla, Inc. | 2025-07 00:53 | Sunnyvale, CA | 2019 TESLA Model 3 | Verified Engaged | Van | Unknown | 52 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11375 v4 | ADS | Tesla, Inc. | 2025-07 15:15 | Austin, TX | 2026 TESLA Model Y | Verified Engaged | SUV | Minor W/ Hospitalization | 2 | Intersection | Summary: This updated report does not report a new incident or make any material changes to the factual record. It only removes confidential or personally identifying information to make the incident narrative publicly a…Summary: This updated report does not report a new incident or make any material changes to the factual record. It only removes confidential or personally identifying information to make the incident narrative publicly available. The Tesla ADS was in the right turn only slip lane with a yield sign yielding for cross traffic from the left. The ADS was stopped then creeped forward up to 2MPH while continuing to yield for cross traffic and was rear-ended by an SUV behind the ADS. The ADS had a safety monitor present with no passengers in the vehicle. On 07/29 Tesla received notice that the safety monitor reported a minor complaint of pain and later sought medical evaluation. |
| 13781-11386 | Level 2 | Tesla, Inc. | 2025-07 04:29 | Mountain View, CA | 2019 TESLA Model X | Verified Engaged | Unknown | Unknown | 69 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11387 | Level 2 | Tesla, Inc. | 2025-07 17:40 | New Springfield, OH | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 42 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11388 | Level 2 | Tesla, Inc. | 2025-07 21:29 | Orem, UT | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 13 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11389 | Level 2 | Tesla, Inc. | 2025-07 21:00 | Mason, OH | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 35 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11390 | Level 2 | Tesla, Inc. | 2025-07 15:54 | Fremont, CA | 2025 TESLA Model Y | Verified Engaged | Unknown | Unknown | 15 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11391 | Level 2 | Tesla, Inc. | 2025-07 20:41 | Houston, TX | 2016 TESLA Model X | Verified Engaged | Unknown | Unknown | 58 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11392 | Level 2 | Tesla, Inc. | 2025-07 21:32 | Tuxedo, NY | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 53 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11393 v2 | Level 2 | Tesla, Inc. | 2025-07 23:31 | Yonkers, NY | 2025 TESLA Model 3 | Verified Engaged | Other, see Narrative | Unknown | 20 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-11394 | Level 2 | Tesla, Inc. | 2025-07 16:25 | Asheville, NC | 2019 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 43 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11396 | Level 2 | Tesla, Inc. | 2025-07 00:26 | Georgetown, KY | 2023 TESLA Model X | Verified Engaged | Other Fixed Object | Unknown | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 13781-11397 | Level 2 | Tesla, Inc. | 2025-07 22:55 | Ashby Gap Estates, VA | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 16 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11398 | Level 2 | Tesla, Inc. | 2025-07 07:00 | Chesterfield, MO | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 74 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11399 | Level 2 | Tesla, Inc. | 2025-07 05:50 | Hazel Park, MI | 2025 TESLA Model 3 | Verified Engaged | Other Fixed Object | Unknown | 34 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-11406 | Level 2 | Tesla, Inc. | 2025-07 00:26 | Austin, TX | 2023 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 35 | Street | Redacted by NHTSA as confidential business information |
| 13781-11407 | Level 2 | Tesla, Inc. | 2025-07 17:13 | Fremont, CA | 2020 TESLA Model 3 | Verified Engaged | Passenger Car | Unknown | 13 | Highway / Freeway | Redacted by NHTSA as confidential business information |
| 13781-11408 | Level 2 | Tesla, Inc. | 2025-07 13:26 | Olde Oaks, TX | 2022 TESLA Model X | Verified Engaged | SUV | Unknown | 32 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-11409 | Level 2 | Tesla, Inc. | 2025-07 15:44 | Oxnard, CA | 2024 TESLA Model Y | Verified Engaged | Unknown | Unknown | 53 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-11410 | Level 2 | Tesla, Inc. | 2025-07 03:05 | North Richland Hills, TX | 2023 TESLA Model Y | Verified Engaged | Unknown | Unknown | 30 | Intersection | Redacted by NHTSA as confidential business information |
| 13781-11411 | Level 2 | Tesla, Inc. | 2025-07 00:09 | Moraine, OH | 2024 TESLA Model X | Verified Engaged | Motorcycle | Fatality | 49 | Rural Road | Redacted by NHTSA as confidential business information |
| 13781-11434 | Level 2 | Tesla, Inc. | 2025-07 01:59 | Pink, OK | 2025 TESLA Model 3 | Verified Engaged | Unknown | Unknown | 63 | Unknown | Redacted by NHTSA as confidential business information |
| 13781-11435 | Level 2 | Tesla, Inc. | 2025-07 02:04 | North Bethesda, DC | 2022 TESLA Model Y | Verified Engaged | Other Fixed Object | Unknown | 64 | Highway / Freeway | Redacted by NHTSA as confidential business information |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. The themed reading of the driverless narratives is on the reports page.