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
74 reports, showing 1 to 74.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30410-16407 | ADS | Motional | 2026-08 12:40 | Las Vegas, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Pole / Tree | No Injured Reported | 4 | Street | On August [XXX], 2026, at approximately 12:40 PM PT, a Motional Ioniq 5 Robotaxi (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a Vehicle Operator in the driverâs seat. The Motional vehicle w…On August [XXX], 2026, at approximately 12:40 PM PT, a Motional Ioniq 5 Robotaxi (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a Vehicle Operator in the driverâs seat. The Motional vehicle was traveling within the[XXX] shopping mall complex. While executing a left-turn maneuver onto [XXX], the Motional vehicle encountered a [XXX] delivery truck parked with its liftgate in the lowered position. The [XXX] truck was blocking the vehicleâs intended path through the intersection, and the Motional vehicle initiated an S-curve maneuver to route around the parallel parked truck.. While completing the S-curve maneuver, the Motional vehicle contacted the curb and made physical contact with a small palm tree approximately three feet tall located near the curb. The Vehicle Operator disengaged the autonomous system at the time of impact and assumed manual control to maneuver the vehicle to a safe location. No injuries were reported, and no airbags deployed. The Motional vehicle was not towed from the scene and remained drivable. | |
| 30413-16664 | ADS | May Mobility | 2026-08 14:17 | Arlington, TX | 2024 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 0 | Intersection | On August [XXX], 2026, at 2:17 p.m. CT, a May Mobility autonomous vehicle (AV) operating northbound in autonomous mode stopped at a stop sign on [XXX] in Arlington, Texas. The May Mobility AV began to make a right turn i…On August [XXX], 2026, at 2:17 p.m. CT, a May Mobility autonomous vehicle (AV) operating northbound in autonomous mode stopped at a stop sign on [XXX] in Arlington, Texas. The May Mobility AV began to make a right turn into the curb lane of eastbound [XXX], but stopped mid-turn to yield to a crossing vehicle. A passenger vehicle trailing the May Mobility AV advanced into the crosswalk at three mph, making contact with the May Mobility AV's rear left corner, causing moderate damage to the May Mobility AVâs rear left-side bumper and quarter panel, and damaging the passenger vehicleâs front right tire. No injuries were reported, no towing was needed, and no airbags were deployed. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30634-16662 | ADS | PlusAI Inc | 2026-08 13:06 | Buda, TX | 2025 INTERNATIONAL LT62F | Verified Engaged | Other, see Narrative | No Injured Reported | 55 | Highway / Freeway | The subject vehicle (V1) was traveling southbound on the [XXX] connector ramp approaching Interstate [XXX] South. V1 was traveling at approximately 55 mph and proceeding within its lane as the roadway narrowed from two l…The subject vehicle (V1) was traveling southbound on the [XXX] connector ramp approaching Interstate [XXX] South. V1 was traveling at approximately 55 mph and proceeding within its lane as the roadway narrowed from two lanes to one. A white tractor-trailer (V2) traveling on the driver's side of V1 moved across the lane boundary, attempting to merge into the lane V1 was occupying before fully clearing the subject vehicle. During this movement, V2 made minor contact with V1's driver-side exterior mirror. V1's safety driver took control of the subject vehicle and maneuvered it to the shoulder, where it came to a complete stop. V2 did not stop and continued driving southbound on Interstate [XXX]. | |
| 30270-15934 | ADS | Waymo LLC | 2026-07 16:23 | Orlando, FL | 2024 JAGUAR I-PACE | Verified Engaged | Pole / Tree | No Injured Reported | 4 | Parking Lot | On July [XXX], 2026 at 4:23 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a pole in a parking lot at [XXX]. The Waymo AV was traveling northbound in a parking l…On July [XXX], 2026 at 4:23 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Orlando, Florida was in a collision involving a pole in a parking lot at [XXX]. The Waymo AV was traveling northbound in a parking lot at [XXX] and approaching a parking area. The Waymo AV initiated a left turn with its left turn signal activated, and the front right side of the Waymo AV made contact with a pole. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damages. Waymo determined that this collision met the criteria for 5-day reporting on July 22th, 2026 after an additional review of available information. 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-16084 | ADS | Waymo LLC | 2026-07 12:41 | Los Angeles, CA | 2026 ZEEKR RT | Verified Engaged | Passenger Car | No Injured Reported | 0 | Street | On July [XXX], 2026 at 12:41 PM PDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing south on…On July [XXX], 2026 at 12:41 PM PDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was stopped facing south on a narrow portion of [XXX], with vehicles parked at the curb in both directions. The Waymo AV was positioned partially in-lane near the west curb, with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, a passenger car behind the Waymo AV traveling southbound on [XXX] initiated a left turn into a driveway on the east side of the [XXX], to the left of the Waymo AV. The passenger car then reversed out of the driveway and into the roadway, and the rear of the passenger car made contact with the left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30270-16085 | ADS | Waymo LLC | 2026-07 16:11 | Atlanta, GA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | No Injured Reported | 16 | Street | On July [XXX], 2026 at 4:11 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] and approac…On July [XXX], 2026 at 4:11 PM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] and approaching a work zone along westbound [XXX] where the westbound half of the roadway was sectioned off by construction panel barricades. The Waymo AV slowed and maneuvered to the right and began to approach an SUV traveling eastbound on [XXX] along the south curb at a low rate of speed. The Waymo AV proceeded forward to pass the SUV to the left, and at the same time, the SUV maneuvered to the left and entered the Waymo AV's path of travel, and the front left side of the SUV made contact with the front 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 SUV 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-16167 | ADS | Waymo LLC | 2026-07 19:12 | Dallas, TX | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | No Injured Reported | 15 | Street | On July [XXX] 2026 at 7:12 PM CDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Dallas, Texas was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southeastbound in the righ…On July [XXX] 2026 at 7:12 PM CDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Dallas, Texas was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was traveling southeastbound in the rightmost lane on [XXX] and slowing as it approached a red light at the intersection with [XXX]. While the Waymo AV was slowing, it approached a pickup truck stopped facing southeastbound in the second lane from the right, and partially in the rightmost lane, in a queue of traffic stopped for the red light ahead. The Waymo AV continued forward and began to pass the pickup truck on the right, and while the Waymo AV was passing the pickup truck, the pickup truck began to change lanes to the rightmost lane, entering the Waymo AV's lane of travel, and the front right side of the pickup 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. 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-16168 | ADS | Waymo LLC | 2026-07 09:27 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | Van | No Injured Reported | 0 | Street | On July [XXX], 2026 at 9:27 AM PDT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling southbound in the seco…On July [XXX], 2026 at 9:27 AM PDT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was traveling southbound in the second lane from the right on [XXX] when it slowed to a stop for a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a van traveling southbound on [XXX] in the second lane from the right 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. 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. | |
| 30410-15730 | ADS | Motional | 2026-07 19:32 | Las Vegas, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Heavy Truck | No Injured Reported | 1 | Street | On July [XXX], 2026, at approximately 7:32 PM PT, a Motional Ioniq 5 Robotaxi with VIN [XXX] was operating in autonomous mode in Las Vegas, Nevada, with a Safety Driver in the driverâs seat. The Motional vehicle was tr…On July [XXX], 2026, at approximately 7:32 PM PT, a Motional Ioniq 5 Robotaxi with VIN [XXX] was operating in autonomous mode in Las Vegas, Nevada, with a Safety Driver in the driverâs seat. The Motional vehicle was traveling in the roadway area near the [XXX] shopping mall and proceeding south on a parking lot street. The Motional vehicle encountered a parked semi-truck and trailer that was fully blocking its lane of travel. The Motional vehicle initiated a maneuver to safely navigate around the parked semi-truck by momentarily entering the opposite lane of travel before intending to return to the south bound lane. The Motional Vehicle initiated the maneuver and when reaching the point at which it was parallel with the parked semi-truck trailer,the Vehicle Operator disengaged the autonomous system and assumed manual control to complete the maneuver. The Motional Vehicle returned to the Motional facility at the end of operation as planned. Upon a routine inspection of the vehicle, it was discovered by facilities staff that the vehicle had sustained minor cosmetic damage which does not require repair. No injuries were reported, and no airbags deployed. The Motional vehicle was not towed from the scene. Law enforcement was not contacted, and no police report was filed. | |
| 30413-16218 | ADS | May Mobility | 2026-07 14:33 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Van | No Injured Reported | 0 | Street | On July [XXX], 2026, at 2:33 p.m. ET, the May Mobility autonomous vehicle (AV) was facing west on [XXX] at a red light, preparing for a right turn onto northbound [XXX] in Atlanta, GA. The Autonomous Vehicle Operator (AV…On July [XXX], 2026, at 2:33 p.m. ET, the May Mobility autonomous vehicle (AV) was facing west on [XXX] at a red light, preparing for a right turn onto northbound [XXX] in Atlanta, GA. The Autonomous Vehicle Operator (AVO) disengaged autonomy during the right turn and assumed manual operation of the AV. Twenty-eight seconds after the disengagement, the manually operated AV, which had queued behind a van at a red light, rolled forward at 0.45 mph. The front of the May Mobility AV made contact with the rear of the van. No damage was evident to the AV or the van. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-16238 | ADS | May Mobility | 2026-07 13:04 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 0 | Street | On July [XXX], 2026, at 1:04 p.m. CT, the May Mobility autonomous vehicle (AV), operating in autonomous mode, was traveling west on [XXX] in Arlington, Texas, when it came to a complete stop for a moving mail delivery va…On July [XXX], 2026, at 1:04 p.m. CT, the May Mobility autonomous vehicle (AV), operating in autonomous mode, was traveling west on [XXX] in Arlington, Texas, when it came to a complete stop for a moving mail delivery van attempting to pull away from the curb. The AV remained stationary, in the lane, and in autonomous operation, as an SUV approached traveling east on [XXX]. As the SUV passed on the passenger side, the right side of the SUV made contact with the stationary AV's right-side mirror and right-side sensor pod, causing minor damage to the sensor pod and minor scuff marks to the mirror. The SUV continued traveling east without stopping. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30410-15591 | ADS | Motional | 2026-06 14:27 | Las Vegas, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 0 | Street | On June [XXX], 2026, at approximately 2:27 PM PT, a Motional Ioniq 5 Robotaxi (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a Vehicle Operator in the driverâs seat. The Motional vehicle was t…On June [XXX], 2026, at approximately 2:27 PM PT, a Motional Ioniq 5 Robotaxi (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a Vehicle Operator in the driverâs seat. The Motional vehicle was traveling southbound on [XXX], south of [XXX], in the rightmost of two lanes. A bus was stopped in the Motional vehicle's lane of travel directly ahead. During the lane-change maneuver to move around the bus, the AV signaled and began positioning for a left-lane change but stopped due to traffic. In order to complete the lane change, the Vehicle Operator disengaged the AV system and manually moved the Motional vehicle toward the left lane, where a rapidly approaching vehicle clipped the Motional vehicle's front left quarter panel while passing. The other vehicle did not stop following the collision and fled the scene. Following the impact, the Vehicle Operator pulled over to the side of the roadway. No injuries were reported, and no airbags deployed. The Motional vehicle sustained damage to its front left quarter panel but remained drivable. The Motional vehicle had been in manual control for less than 30 seconds before impact. Law enforcement was contacted, and a police report was filed. | |
| 31101-15477 | ADS | Avride Inc. | 2026-06 14:54 | Dallas, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 4 | Street | On June [XXX], 2026 at 2:54 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound on [XXX] in autonomous mode when it approached a …On June [XXX], 2026 at 2:54 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling eastbound on [XXX] in autonomous mode when it approached a passenger car parked on the left side of the roadway. As the AVRIDE AV approached the parked vehicle, the driver-side door of the passenger car was opened into the roadway. There was insufficient room to open the door safely without interfering with traffic. The AVRIDE AV continued traveling straight ahead, resulting in light contact between its left side mirror and the driver-side door of the passenger car. Neither vehicle sustained damage. No injuries were reported. | |
| 31101-15587 | ADS | Avride Inc. | 2026-06 07:49 | Dallas, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | SUV | No Injured Reported | 4 | Intersection | On June [XXX], 2026 at 7:49 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound in autonomous mode in the…On June [XXX], 2026 at 7:49 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, TX at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound in autonomous mode in the middle lane on [XXX], a one-way street, as it approached the intersection with [XXX]. An SUV was traveling alongside the AVRIDE AV in the lane immediately to its left. As both vehicles approached the intersection the traffic signal was green and transitioned to yellow as the AVRIDE AV entered the intersection. The AVRIDE AV initiated a left turn onto [XXX] from a non-turning lane. The front left of the AVRIDE AV made light contact with the front right of the SUV. Neither vehicle sustained damage. No injuries were reported. | |
| 30410-15247 | ADS | Motional | 2026-05 15:05 | Las Vegas, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 2 | Street | On May [XXX], 2026, at approximately 8:05 AM PT, a Motional Ioniq 5 Robotaxi (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a Vehicle Operator in the driver's seat. The Motional vehicle was trav…On May [XXX], 2026, at approximately 8:05 AM PT, a Motional Ioniq 5 Robotaxi (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a Vehicle Operator in the driver's seat. The Motional vehicle was traveling eastbound on [XXX] near the intersection with [XXX] and came to a stop at a red traffic signal. While stopped, the Vehicle Operator disengaged autonomous mode and assumed manual control to perform a lane change to travel southbound on[XXX]. As the Vehicle Operator maneuvered the Motional vehicle into the right-turn lane in manual mode at approximately 2 mph, the passenger-side front bumper and fender of the Motional vehicle struck another vehicle that was occupying the lane. The autonomous system had been disengaged less than 30 seconds before the impact. | |
| 30413-15463 | ADS | May Mobility | 2026-05 16:11 | Arlington, TX | 2024 TOYOTA Sienna | Verified Engaged | Other, see Narrative | No Injured Reported | 33 | Street | On May [XXX], 2026 at 4:11 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX] The May Mobility AV was traveling Eastbound on [XXX…On May [XXX], 2026 at 4:11 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX] The May Mobility AV was traveling Eastbound on [XXX]. As the May Mobility AV passes [XXX] a loop of an unsecured, low-hanging utility cable that was dangling above the right lane of travel made contact with the front right A-pillar near the windshield of the May Mobility AV. At the time of impact, the May Mobility AV was in autonomous mode, traveling at 33 MPH. The impact left scuffs on the May Mobility AV that were buffed out, not requiring repair. Damage to the utility cable beyond the original state of disrepair is unknown. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-15464 | ADS | May Mobility | 2026-05 16:38 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | Other, see Narrative | No Injured Reported | 32 | Street | On May [XXX], 2026 at 4:38 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX]. The May Mobility AV was traveling Eastbound on [XX…On May [XXX], 2026 at 4:38 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX]. The May Mobility AV was traveling Eastbound on [XXX]. As the May Mobility AV passes [XXX] a loop of an unsecured, low-hanging utility cable that was dangling above the right lane of travel struck the windshield and roof of the May Mobility AV. At the time of impact, the May Mobility AV was in autonomous mode, traveling at 32 MPH. The May Mobility AV sustained damage on the top, front, and right side of the vehicle that is estimated to be more than $1,000. Damage to the utility cable beyond the original state of disrepair is unknown. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 31101-15093 | ADS | Avride Inc. | 2026-05 14:10 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other Fixed Object | No Injured Reported | 10 | Intersection | On May [XXX], 2026 at 2:10 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling northwestbound in autonomous mode on [XXX] when it approached…On May [XXX], 2026 at 2:10 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was traveling northwestbound in autonomous mode on [XXX] when it approached a red light at a railroad crossing. After stopping at the red light and waiting for the railroad crossing gate to raise, the AVRIDE AV began to drive forward. As the AVRIDE AV drove forward, the railroad crossing gate began to lower again. As the railroad crossing gate lowered, the AVRIDE AV continued to drive forward. This maneuver resulted in the top of the AVRIDE AV making contact with the railroad crossing gate. Neither the AVRIDE AV nor railroad crossing gate sustained damage. No injuries were reported. | |
| 30270-14578 | ADS | Waymo LLC | 2026-04 12:20 | Venice, CA | 2024 JAGUAR I-PACE | Verified Engaged | Pickup Truck | No Injured Reported | 0 | Street | On April [XXX], 2026 at 12:20 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Venice, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped facing west on a narr…On April [XXX], 2026 at 12:20 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Venice, California was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped facing west on a narrow portion of [XXX], with vehicles parked at the curb in both directions, to yield to a pickup truck traveling eastbound on [XXX]. While the Waymo AV was stopped, the pickup truck proceeded to pass the Waymo AV to the left, and the left side of the pickup truck made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-14707 | ADS | Waymo LLC | 2026-04 21:44 | Los Angeles, CA | 2025 ZEEKR RT | Verified Not Engaged | Passenger Car | No Injured Reported | 12 | Street | On April [XXX], 2026 at 9:44 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southeastboun…On April [XXX], 2026 at 9:44 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southeastbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions, in autonomous mode. The Waymo AV transitioned to manual mode and the test driver continued proceeding forward on a curve of [XXX] where the roadway continued to the left, and the front right side of the Waymo AV made contact with the rear left side of a passenger car parked facing southeast at the curb. As a result of this collision, the passenger car was pushed forward, and the front of the passenger car made contact with the rear of a second passenger car parked directly in front of the first passenger car. 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. All three 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. | |
| 30291-14538 | ADS | Nuro | 2026-04 11:50 | Santa Clara, CA | 2022 TOYOTA Prius | Verified Engaged | Motorcycle | No Injured Reported | 19 | Street | On April [XXX], 2026, Nuro was operating a Prius test vehicle in auto mode on [XXX], a street in Santa Clara, CA with a single travel lane in the direction of travel, when a motorcycle attempted to overtake the Nuro vehi…On April [XXX], 2026, Nuro was operating a Prius test vehicle in auto mode on [XXX], a street in Santa Clara, CA with a single travel lane in the direction of travel, when a motorcycle attempted to overtake the Nuro vehicle from behind. In so doing, the motorcyclist clipped the side of the Nuro vehicle, causing some minor property damage to the Nuro vehicle. The motorcyclist then pulled over to the side of the road, and both parties exchanged information. Neither the motorcyclist nor the occupants of the Nuro vehicle were injured, and law enforcement was not called to the scene. | |
| 30410-14562 | ADS | Motional | 2026-04 16:42 | Las Vegas, NV | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other Fixed Object | No Injured Reported | 23 | Street | On April [XXX], 2026, at approximately 4:42 PM local time, a Motional autonomous vehicle [XXX] was traveling southbound on [XXX] approaching [XXX] in Las Vegas, Nevada. While proceeding within its lane of travel, the ve…On April [XXX], 2026, at approximately 4:42 PM local time, a Motional autonomous vehicle [XXX] was traveling southbound on [XXX] approaching [XXX] in Las Vegas, Nevada. While proceeding within its lane of travel, the vehicle encountered a piece of concrete debris located in the roadway. The vehicle subsequently struck the debris, resulting in a punctured front tire and damage to the vehicle's undercarriage. Following the impact, the safety driver brought the vehicle to a controlled stop and pulled over to the side of the roadway. Due to the damage to the tire, the vehicle was not drivable. A tow truck was requested and the vehicle was subsequently removed from the scene. | |
| 30413-15019 | ADS | May Mobility | 2026-04 18:28 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 0 | Street | On April [XXX], 2026, at 6:28 PM ET, a passenger car collided with a May Mobility Autonomous Vehicle (AV) operating in Atlanta, Georgia on [XXX] near [XXX]. The May Mobility AV was traveling east on [XXX] in the left lan…On April [XXX], 2026, at 6:28 PM ET, a passenger car collided with a May Mobility Autonomous Vehicle (AV) operating in Atlanta, Georgia on [XXX] near [XXX]. The May Mobility AV was traveling east on [XXX] in the left lane. A passenger car traveling east on [XXX] in the right lane proceeded to change lanes from the right lane to the left lane. The May Mobility AV Operator began braking before a pedestrian crosswalk, which had an activated Rectangular Rapid Flashing Beacon and the presence of a pedestrian waiting to cross. After changing lanes, the passenger car failed to brake and the front of the passenger car made contact with the rear of the May Mobility AV. At the time of impact, the May Mobility AV was in manual mode. The May Mobility AV sustained a significant puncture in the rear, lower bumper with scratches, the passenger car sustained scratches on the front bumper. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it may become available. | |
| 34952-14990 | ADS | Stack AV | 2026-04 14:46 | Edgewood, NM | 2025 PETERBILT 579 | Verified Not Engaged | Heavy Truck | No Injured Reported | 60 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 30270-14220 | ADS | Waymo LLC | 2026-03 19:19 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | No Injured Reported | 31 | Street | On March [XXX], 2026 at 7:19 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 northwestbound on [XXX]…On March [XXX], 2026 at 7:19 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 northwestbound on [XXX] in the second from the right lane when an SUV traveling southwestbound in a parking lot at [XXX] exited the parking lot without stopping and began to make a right turn onto [XXX]. The SUV partially entered the Waymo AV's lane of travel as it completed turning right, and the front left side 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-14289 | ADS | Waymo LLC | 2026-03 06:51 | Redwood City, CA | 2024 JAGUAR I-PACE | Verified Engaged | Passenger Car | No Injured Reported | 14 | Street | On March [XXX], 2026 at 6:51 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Redwood City, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northeastboun…On March [XXX], 2026 at 6:51 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Redwood City, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northeastbound in the right lane on [XXX] when a passenger car traveling northwestbound in a parking lot adjacent to [XXX] exited the parking lot without stopping and began to turn left onto southwestbound [XXX]. The passenger car entered the Waymo AV's lane of travel, and the Waymo AV maneuvered to the left as the passenger car continued turning left, and the front right 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. | |
| 30413-14624 | ADS | May Mobility | 2026-03 10:18 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 6 | Intersection | On March [XXX], 2026, at 10:18 am, a third-party vehicle collided with a May Mobility Autonomous Vehicle (Ego) in Arlington, Texas, at the intersection of [XXX] and [XXX]. The May Ego was traveling north on [XXX], making…On March [XXX], 2026, at 10:18 am, a third-party vehicle collided with a May Mobility Autonomous Vehicle (Ego) in Arlington, Texas, at the intersection of [XXX] and [XXX]. The May Ego was traveling north on [XXX], making a right turn at a yield sign onto eastbound [XXX]. with its automated driving system engaged in autonomy mode. The May Ego stopped at the yield sign then held its position in order to confirm its prediction that an oncoming vehicle was not making a left turn across the ego's path. The third-party vehicle, traveling north on [XXX] behind the Ego, failed to stop at the yield sign and rear-ended the Ego. Vehicle telematics confirm the Autonomous Vehicle Operator intervened using the accelerator to avoid the collision; however, the collision was unavoidable. | |
| 30792-14655 | ADS | WeRide Corp | 2026-03 11:46 | San Jose, CA | 2024 NISSAN Ariya Hatchback | Verified Engaged | Pickup Truck | No Injured Reported | 0 | Street | On the morning of March [XXX], 2026, at approximately 11:46 a.m., a WeRide autonomous vehicle (Vehicle 1) was traveling along [XXX] in San Jose, California, proceeding straight in the second lane from the left as it appr…On the morning of March [XXX], 2026, at approximately 11:46 a.m., a WeRide autonomous vehicle (Vehicle 1) was traveling along [XXX] in San Jose, California, proceeding straight in the second lane from the left as it approached the intersection with [XXX]. Operating in autonomous mode, the vehicle came to a complete stop at a red traffic signal. While stopped, Vehicle 1 was struck from behind by a white 2012 Chevrolet Colorado pickup truck (Vehicle 2), whose driver failed to stop in time. Immediately following the collision, the In-vehicle safety operator of Vehicle 1 disengaged autonomous mode and assessed the situation. Both drivers then relocated their vehicles to a safe area nearby, where they exchanged information and performed a visual inspection of the damage. The damage to both vehicles was minor in nature. Vehicle 1 sustained a small scratch to its rear bumper, while Vehicle 2 sustained a corresponding minor scratch to its front bumper. No injuries were reported by either party, and emergency services were not requested. | |
| 31101-14647 v2 | ADS | Avride Inc. | 2026-03 15:54 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other, see Narrative | No Injured Reported | 29 | Street | On March [XXX], 2026 at 3:54 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was driving northeastbound in the right lane on [XXX] in autonomous m…On March [XXX], 2026 at 3:54 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was driving northeastbound in the right lane on [XXX] in autonomous mode when it approached a traffic sign laying down in the right lane. Upon noticing the sign, the AVRIDE AV moved into the left lane. While moving into the left lane, the right front of the AVRIDE AV made contact with the road sign. The AVRIDE AV sustained minor damage. No injuries were reported. | |
| 31101-14649 | ADS | Avride Inc. | 2026-03 13:26 | Austin, TX | 2026 HYUNDAI Ioniq 5 | Verified Engaged | Van | No Injured Reported | 0 | Street | On March [XXX], 2026 at 1:26 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was facing northeast in autonomous mode while stopped at the red ligh…On March [XXX], 2026 at 1:26 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Austin, Texas on [XXX] near [XXX]. The AVRIDE AV was facing northeast in autonomous mode while stopped at the red light on [XXX] at the intersection with [XXX]. While stopped at the red light, a van slowly approached the AVRIDE AV from behind. The front of the van then made light contact with the rear of the AVRIDE AV. Neither vehicle sustained damage. No injuries were reported. | |
| 31101-14650 | ADS | Avride Inc. | 2026-03 15:41 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other, see Narrative | No Injured Reported | 23 | Street | On March [XXX], 2026 at 3:41 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in autonomous mode on [XXX] in the right lan…On March [XXX], 2026 at 3:41 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in autonomous mode on [XXX] in the right lane when it approached a road sign lying down in the middle of the right lane. As the AVRIDE AV proceeded straight ahead, the front of the AVRIDE AV made contact with the road sign which was already lying down on the road. The AVRIDE AV sustained minor damage. The road sign did not sustain damage. No injuries were reported. | |
| 31101-14652 | ADS | Avride Inc. | 2026-03 10:23 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other, see Narrative | No Injured Reported | 13 | Intersection | On March [XXX], 2026, at 10:23 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound on [XXX] in autonom…On March [XXX], 2026, at 10:23 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling northwestbound on [XXX] in autonomous mode approaching the intersection with [XXX] with a safety driver behind the wheel. As the AVRIDE AV approached the green light at the intersection, the AVRIDE AV planned to continue driving straightforward through the intersection. While entering the intersection, the safety driver took over the vehicle in manual mode and took a left turn onto the left lane on [XXX]. The right lane on [XXX] was blocked off by a temporary traffic control sign. As the safety driver made the left hand turn, the right front of the AVRIDE AV made contact with the traffic sign. The AVRIDE AV sustained minor damage. The traffic sign sustained zero damage. No injuries were reported. | |
| 30410-14092 | ADS | Motional | 2026-02 09:55 | Las Vegas, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 0 | Intersection | On February [XXX], 2026, at approximately 9:55 AM PT, a Motional Ioniq 5 AV (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the driverâs seat. The AV was stopped southbound on…On February [XXX], 2026, at approximately 9:55 AM PT, a Motional Ioniq 5 AV (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the driverâs seat. The AV was stopped southbound on [XXX] in the left-turn lane at the intersection with [XXX], positioned behind two other stopped vehicles. At that time, a sedan traveling eastbound on [XXX] was being actively pursued by a law enforcement vehicle which had its flashing lights and siren activated. Both vehicles turned left and proceeded northbound on [XXX] but using the southbound lanes. As the sedan traveled in the wrong lanes on [XXX], it struck the passenger-side front end and right wheel well of the Motional vehicle which remained stopped in the left turn lane the entire time. The sedan did not stop after striking the Motional vehicle and continued traveling in the wrong (southbound) lanes and counter to the flow of traffic while it continued fleeing from police. No occupants of the Motional vehicle were injured. The Motional vehicle sustained damage to the front end and was towed from the scene. The Las Vegas Metropolitan Police Department is investigating the incident, but a police report is not yet available | |
| 30410-14170 | ADS | Motional | 2026-02 3:16 | Las Vegas, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Other, see Narrative | No Injured Reported | 25 | Street | On Feb [XXX], at approximately 3:16 AM local time, a Motional IONIQ 5 automated vehicle was operating in autonomous mode southbound on Las Vegas Boulevard, traveling at approximately 25 mph. While proceeding in its lane…On Feb [XXX], at approximately 3:16 AM local time, a Motional IONIQ 5 automated vehicle was operating in autonomous mode southbound on Las Vegas Boulevard, traveling at approximately 25 mph. While proceeding in its lane of travel, an individual located near the roadway threw an object toward the front of the vehicle. The object made contact with the lower front bumper area. The vehicle remained under autonomous control and came to a controlled stop following the impact. There were no reported injuries to any occupants or members of the public. No airbags deployed. The vehicle sustained minor cosmetic damage to the lower front bumper and front license plate area. The vehicle was not towed from the scene. | |
| 30410-14238 | ADS | Motional | 2026-02 23:55 | Las Vegas, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 25 | Street | On Wednesday, February [XXX], a vehicle struck the front passenger side of a Motional Ioniq 5 AV in Las Vegas, Nevada. The Motional vehicle was operating in autonomous mode near the intersection of [XXX] and [XXX] when i…On Wednesday, February [XXX], a vehicle struck the front passenger side of a Motional Ioniq 5 AV in Las Vegas, Nevada. The Motional vehicle was operating in autonomous mode near the intersection of [XXX] and [XXX] when it encountered another vehicle that had stopped in the AV's lane of travel. The AV maneuvered around the stopped vehicle and continued forward. Shortly thereafter, the other vehicle accelerated and attempted to change lanes into the AV's lane from an adjacent lane. The Vehicle Operator disengaged autonomous mode and attempted to avoid the vehicle, but the other vehicle struck the AV's front passenger side. No injuries were reported and the Motional vehicle remained moveable following the collision. The other vehicle did not stop and fled the scene. | |
| 30610-14340 | ADS | Zoox, Inc. | 2026-02 23:01 | Las Vegas, NV | 2026 ZOOX Zoox | Verified Engaged | Pickup Truck | No Injured Reported | 0 | Street | An occupied Zoox autonomous vehicle traveling south on [XXX] was stopped for a red signal at [XXX] in Las Vegas. After the light turned green, and before the Zoox vehicle started to move, a Pickup (Vehicle 2) traveling d…An occupied Zoox autonomous vehicle traveling south on [XXX] was stopped for a red signal at [XXX] in Las Vegas. After the light turned green, and before the Zoox vehicle started to move, a Pickup (Vehicle 2) traveling directly behind it rear-ended it. Shortly thereafter, both vehicles traveled a few feet ahead and pulled over. The passengers exited the Zoox vehicle onto the sidewalk. After exchanging information, the Zoox vehicle returned to base for inspection, where it was found to have sustained moderate damage. No injuries were reported, and police were not notified. | |
| 30530-14071 | ADS | Aurora Operations, Inc. | 2026-01 17:30 | El Paso, TX | 2024 PETERBILT 579 | Verified Engaged | Other, see Narrative | No Injured Reported | 55 | Highway / Freeway | At 5:03 PM CDT on January [XXX], 2026 in El Paso, Texas, an Aurora vehicle was traveling east on [XXX] at approximately 55 MPH during a development mission. The Aurora vehicle was in autonomy. The Aurora vehicle was tr…At 5:03 PM CDT on January [XXX], 2026 in El Paso, Texas, an Aurora vehicle was traveling east on [XXX] at approximately 55 MPH during a development mission. The Aurora vehicle was in autonomy. The Aurora vehicle was traveling straight in its lane. A pickup truck was present ahead. A loose object from the pickup truck struck the Aurora vehicle. After impact, the vehicle operator elected to disengage autonomy and returned to the Aurora terminal. The Aurora vehicle was driveable from the location. No injuries were reported. The Aurora vehicle sustained damage. Aurora will supplement or modify its reporting should additional relevant information become available. | |
| 31101-13761 | ADS | Avride Inc. | 2026-01 14:15 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Pickup Truck | No Injured Reported | 30 | Street | On January [XXX] at approximately 2:15 p.m., an AVRIDE autonomous vehicle (the AVRIDE AVâ) was involved in a collision in Dallas, Texas, on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in the right lane w…On January [XXX] at approximately 2:15 p.m., an AVRIDE autonomous vehicle (the AVRIDE AVâ) was involved in a collision in Dallas, Texas, on [XXX] near [XXX]. The AVRIDE AV was traveling southbound in the right lane with autonomous mode engaged when it approached a pickup truck exiting a parking lot on the right side of the roadway. The pickup truck entered the roadway without stopping or yielding, cutting off the AVRIDE AV and contacting the right side of the AVRIDE AV with the pickup truckâs front-left area. The AVRIDE AVâs airbags deployed and the vehicle required towing. Both vehicles sustained damage. No injuries were reported. | |
| 31101-14068 | ADS | Avride Inc. | 2026-01 11:34 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Other Fixed Object | No Injured Reported | 27 | Street | On January [XXX], 2026 at 11:34 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on Victory Avenue near [XXX]. The AVRIDE AV was traveling southbound on [XXX] engaged in autonomous m…On January [XXX], 2026 at 11:34 AM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas on Victory Avenue near [XXX]. The AVRIDE AV was traveling southbound on [XXX] engaged in autonomous mode when it aproached a grounded yield sign on the road centerline. Upon approaching the yield sign, the sign began to tilt into the AVRIDE AV lane of travel. This resulted in the left front of the AVRIDE AV making contact with the yield sign. The sign sustained no damage. The AVRIDE AV sustained no damage. No injuries were reported. | |
| 30270-13484 | ADS | Waymo LLC | 2025-12 17:22 | Inglewood, CA | 2024 JAGUAR I-PACE | Verified Engaged | SUV | No Injured Reported | 22 | Intersection | 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…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. | |
| 30413-13468 | ADS | May Mobility | 2025-12 11:29 | Arlington, TX | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 2 | Intersection | 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-13469 | ADS | May Mobility | 2025-12 19:37 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 4 | Intersection | 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-13470 | ADS | May Mobility | 2025-12 11:01 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 5 | Street | 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 AVOs. Upon review of this AVOâs actions it was decided to remove this person from their role as an AVO. | |
| 31101-13620 v2 | ADS | Avride Inc. | 2025-12 19:35 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Pickup Truck | No Injured Reported | 24 | Street | 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-13626 | ADS | Avride Inc. | 2025-12 10:04 | Dallas, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 0 | Street | 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. | |
| 13781-13237 v2 | ADS | Tesla, Inc. | 2025-11 22:24 | Austin, TX | 2026 TESLA Model Y | Verified Engaged | Other, see Narrative | No Injured Reported | 0 | Street | 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 stopped behind traffic at an intersection with a red light. A person on a motor scooter (VRU) approached the ADS from behind and moved into a gap directly behind the ADS. As the VRU was directly behind the stopped ADS, the VRU steered right and made contact with the ADS's rear end. Afterwards the VRU hopped the right curb and continued to proceed straight on the sidewalk. Safety monitor and passenger were present in the vehicle. | |
| 30410-13069 | ADS | Motional | 2025-11 14:30 | Pittsburgh, PA | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 12 | Intersection | Redacted by NHTSA as confidential business information | |
| 30413-13083 | ADS | May Mobility | 2025-11 11:40 | Grand Rapids, MN | 2023 TOYOTA Sienna | Verified Engaged | Other Fixed Object | No Injured Reported | 25 | Street | A May autonomous shuttle (Ego) is approaching a passenger stop location in autonomy. The vehicle operator (AVO) presses on the accelerator, taking control of the Ego, then accelerates into the curb at the stop. The Ego m…A May autonomous shuttle (Ego) is approaching a passenger stop location in autonomy. The vehicle operator (AVO) presses on the accelerator, taking control of the Ego, then accelerates into the curb at the stop. The Ego made contact with the curb 3 seconds after switching into manual, causing severe damage to the front-right tire. Resimulation of this event shows that there were no autonomy errors that led to this event, and had the Ego stayed in autonomy, this event would not have happened. This AVO had just completed our training course with only a few hours of service time before this incident. Upon further review of the AVO performance, on their own, it was decided to remove her from the AVO role. | |
| 30413-13248 | ADS | May Mobility | 2025-11 15:06 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 1 | Intersection | The May autonomous shuttle (Ego) stopped in Autonomous mode safely behind a lead vehicle at a traffic light, which then, the lead vehicle, reversed into the stationary Ego. The Autonomous vehicle operator took over contr…The May autonomous shuttle (Ego) stopped in Autonomous mode safely behind a lead vehicle at a traffic light, which then, the lead vehicle, reversed into the stationary Ego. The Autonomous vehicle operator took over control of the vehicle and attempted to reverse, but was unable to get out of the way of the reversing vehicle. The planner did roll out the agent with a reversing policy and predicted the collision, but the system currently is not able to honk or reverse or do anything else that could have avoided this. The primary factor was fault by the lead vehicle. There was no fault in our software that led to this event. | |
| 30413-13249 | ADS | May Mobility | 2025-11 11:38 | Atlanta, GA | 2023 TOYOTA Sienna | Verified Engaged | Other Fixed Object | No Injured Reported | 5 | Parking Lot | During normal autonomous operation, the May autonomous shuttle (Ego) was traveling through a narrow section of roadway in a parking lot bordered by parked vehicles on the left and a retaining wall on the right on experim…During normal autonomous operation, the May autonomous shuttle (Ego) was traveling through a narrow section of roadway in a parking lot bordered by parked vehicles on the left and a retaining wall on the right on experimental software version v29.0.20. As the Ego proceeded, the system initially recognized the static retaining wall as a large, non-rectangular object. As the Ego approaches the wall, the resulting density of lidar returns on the object (wall) exceeds the detectors maximum limitation. The newer lidar points, toward the forward edge of the elongated object, exceeding the limit were filtered out, causing the track to disappear when the ego approached 5m from the track (i.e. the wall). The situation was exacerbated by the fact that the road edge was incorrectly marked in that section. The road edge was drawn through the retaining wall and thus the vehicle did not have any prior knowledge about the edge of the road. As a result, the Ego drove too close to the wall, scraping it at a speed of 2 meters per second while driving straight (i.e. in lane-nominal policy) with no nudge or veer corrections. There was no damage to the wall. The limitation leading to the lost track affects Software versions v26.0 (when the Open World Tracklet v2 feature was introduced) through v31.0. This is the only known instance of this failure mode, and in v32.0 an optimization was made to remove the LIDAR threshold entirely and mitigate the vulnerability. Furthermore, the incorrect road edge annotation was corrected shortly after this incident and the map updated for the deployed vehicles. | |
| 31101-13438 | ADS | Avride Inc. | 2025-11 21:21 | Austin, TX | 2023 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 15 | Street | Rear end collision, another vehicle hit Avride car from behind when traffic light became to be yellow. | |
| 31101-13439 | ADS | Avride Inc. | 2025-11 21:57 | Austin, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 30 | Street | Avride car was traveling on the side road next to an off ramp with a vehicle attempting to lane change into our lane. The other driver had the blinker ON indicating to lane change. Avride car drove past it leading the ot…Avride car was traveling on the side road next to an off ramp with a vehicle attempting to lane change into our lane. The other driver had the blinker ON indicating to lane change. Avride car drove past it leading the other vehicle to have to wait to lane change. As Avride car approaches the intersection at a red light, the other vehicle then comes out from behind the rover to the left lane again, cuts the rover off and then drives off. | |
| 31101-13440 | ADS | Avride Inc. | 2025-11 18:11 | Austin, TX | 2025 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 20 | Intersection | Civilian vehicle ran red light while the Avride car driver was entering the intersection on a green light. | |
| 31101-13441 | ADS | Avride Inc. | 2025-11 15:07 | Austin, TX | 2022 HYUNDAI Ioniq 5 | Verified Engaged | Passenger Car | No Injured Reported | 0 | Intersection | Avride car was rear-ended at the intersection. | |
| 30270-11859 | ADS | Waymo LLC | 2025-10 02:20 | Phoenix, AZ | 2024 JAGUAR I-PACE | Verified Engaged | SUV | No Injured Reported | 31 | Street | On October [XXX], 2025 at 2:20 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the l…On October [XXX], 2025 at 2:20 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] in the leftmost lane. An SUV was traveling southbound, ahead of and to the right of the Waymo AV in the center lane on [XXX]. As the Waymo AV continued to proceed straight and approached the SUV, the SUV initiated a left turn from the center lane, crossing the dashed white lane line and entering the Waymo AV's lane of travel. The Waymo AV began braking and maneuvered to the left, and the front left side of the SUV 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. 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-11865 | ADS | Waymo LLC | 2025-10 15:57 | Los Angeles, CA | 2024 JAGUAR I-PACE | Verified Engaged | Heavy Truck | No Injured Reported | 0 | Parking Lot | On October [XXX], 2025 at 3:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling westboun…On October [XXX], 2025 at 3:57 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a heavy truck in a parking lot at [XXX]. The Waymo AV was traveling westbound in a parking lot at [XXX] when it slowed to a stop to yield to a heavy truck that was facing west and executing a reversing turn into a loading dock parking stall at the south side of the parking lot. The heavy truck came to a stop, proceeded forward a short distance, and then came to a stop again. While the heavy truck was stopped, the Waymo AV proceeded forward to pass to the right of the heavy truck. As the Waymo AV was passing the heavy truck, the heavy truck once again initiated a reversing turn towards the parking stall and the Waymo AV came to a stop to yield to the heavy truck. The heavy truck continued to reverse and the front right corner of the heavy truck's trailer 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. 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-11889 | ADS | Waymo LLC | 2025-10 09:15 | Phoenix, AZ | 2024 JAGUAR I-PACE | Verified Not Engaged | Other, see Narrative | No Injured Reported | 47 | Highway / Freeway | On October [XXX], 2025 at 9:15 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a trash can on [XXX] near Exit [XXX]. The Waymo AV was traveling northbound on [XXX…On October [XXX], 2025 at 9:15 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a trash can on [XXX] near Exit [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane. A pickup truck that was traveling northbound on [XXX] in the third from the right lane made contact with a trash can that was in the roadway. The trash can deflected off the pickup truck and rolled across the roadway. As the trash can was entering the Waymo AV's lane of travel, the test driver transitioned the Waymo AV to manual mode and began to maneuver to the right and the trash can 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-12070 | ADS | Waymo LLC | 2025-10 23:40 | San Francisco, CA | 2024 JAGUAR I-PACE | Verified Engaged | Animal | No Injured Reported | 5 | Street | On October [XXX], 2025 at 11:40 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California made contact with a cat on [XXX] at [XXX]. The Waymo AV was stopped next to the curb for a passenger p…On October [XXX], 2025 at 11:40 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California made contact with a cat on [XXX] at [XXX]. The Waymo AV was stopped next to the curb for a passenger pickup facing east on [XXX]. As the passengers were boarding the Waymo AV, a cat approached the Waymo AV from the southern sidewalk of [XXX] and sat in the roadway partially under the front right corner of the Waymo AV. A pedestrian approached the Waymo AV from the east on the southern sidewalk of [XXX] and began crouching near the front of the Waymo AV, stepping partially into the roadway, appearing to reach for the cat. As they did so, the cat moved farther from the sidewalk under the Waymo AV and the pedestrian stepped back onto the sidewalk. The Waymo AV then departed the pickup location and the rear right tire made contact with the cat. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Waymo later received notice that the cat did not survive. The passengers in the Waymo AV did not have seatbelts fastened at the time, having just boarded the Waymo AV. Waymo is reporting this crash under Request 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available. | |
| 30410-12017 | ADS | Motional | 2025-10 14:30 | Las Vegas, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | Other, see Narrative | No Injured Reported | 0 | Intersection | On October [XXX], 2025, at approximately 2:30 PM PT, a Motional AV with VIN [XXX] was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the drivers seat. The vehicle was traveling northbound on […On October [XXX], 2025, at approximately 2:30 PM PT, a Motional AV with VIN [XXX] was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the drivers seat. The vehicle was traveling northbound on [XXX] in the second of four lanes from the left, approaching the intersection with [XXX]. While stopped at a red traffic signal, an adult male pedestrian began crossing [XXX] from the west side of the street, several hundred feet away from a designated crosswalk. The pedestrian proceeded southbound across multiple lanes and paused on a median located ahead and to the left of the AV. The AV detected and classified the pedestrian the entire time. When the traffic signal turned green, the pedestrian remained stopped on the median. Given that the pedestrian remained stopped in place, the AV began to move forward slowly at approximately 2.5 mph and continued to correctly detect and classify the pedestrian. The pedestrian, holding what appears to be an item in a plastic bag, suddenly stepped into the far-left turn lane ahead of the AV, the AV immediately came to a complete stop still in the second lane. The pedestrian continued crossing, making a light physical contact with the rear driverâs side of the vehicle before continuing across the remaining three lanes of traffic still outside of the crosswalk. The vehicle operator then disengaged the autonomous system and pulled over to complete an incident report. No police were notified. There were no injuries, no damage, and no airbag deployments. The pedestrian did not stop at the scene and the identity of the pedestrian is unknown. | |
| 13781-11787 v2 | ADS | Tesla, Inc. | 2025-09 13:08 | Austin, TX | 2026 TESLA Model Y | Verified Engaged | Animal | No Injured Reported | 27 | 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 proceeding straight in the center lane of the three lane street. As the Tesla ADS was approaching a green light at an intersection, a dog perpendicular to the Tesla vehicle is seen running into the intersection from the right. The Tesla ADS reduced vehicle speed and steered to the left. The dog proceeded to run onto the main road and toward the Tesla ADS's lane and path. The Tesla ADS continued to reduce vehicle speed and biased left in lane. The dog ran toward the Tesla and made contact with the bottom of the Tesla ADS's front right bumper which caused the dog to be pushed to the right, into the lane and path of an approaching van. As the Tesla ADS continued to proceed forward, the dog appeared behind the van and was seen running away from the street, only to turn around and run back toward the street. Safety monitor was present and no passengers were inside the vehicle. | |
| 34952-11803 | ADS | Stack AV | 2025-09 7:47 | Mount Pleasant, PA | 2025 PETERBILT 579 | Verified Engaged | Heavy Truck | No Injured Reported | 28 | Highway / Freeway | Redacted by NHTSA as confidential business information | |
| 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. | |
| 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. | |
| 30291-11458 | ADS | Nuro | 2025-07 18:00 | Mountain View, CA | 2022 TOYOTA Prius | Verified Engaged | Passenger Car | No Injured Reported | 3 | Intersection | On Wednesday, July [XXX], a Nuro vehicle operating in autonomous mode stopped at sign-controlled intersection, then began to cautiously proceed through the intersection to make a left turn. Just after the Nuro vehicle b…On Wednesday, July [XXX], a Nuro vehicle operating in autonomous mode stopped at sign-controlled intersection, then began to cautiously proceed through the intersection to make a left turn. Just after the Nuro vehicle began to move into the intersection, it was struck from behind by another vehicle. | |
| 30413-11487 | ADS | May Mobility | 2025-07 14:30 | Peachtree Corners, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 20 | Intersection | The May autonomous vehicle was travelling in an autonomous vehicle (AV) only lane, on [XXX], approaching the intersection at [XXX] A vehicle travelling to the left of the May shuttle in the non-AV lane attempted to perf…The May autonomous vehicle was travelling in an autonomous vehicle (AV) only lane, on [XXX], approaching the intersection at [XXX] A vehicle travelling to the left of the May shuttle in the non-AV lane attempted to perform a right hand turn across the May vehicles path and collided with the May AV. 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 is a metal street sign that instructs other traffic to yield to the vehicles in the AV lane. There were no autonomy faults or errors which led to this incident. Additionally, there is a second traffic light at this intersection that warns public drivers to yield to the AV shuttle. This light was not operating as it should during this incident. We are working with our partner to maintain the operation of this light and have implemented a mitigation policy of daily inspections of this light and implementing an AVO in service if this light is not functioning. | |
| 30413-11489 | ADS | May Mobility | 2025-07 09:02 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Other Fixed Object | No Injured Reported | 18 | Street | While traveling north on [XXX], the Autonomous Vehicle Operator (AVO) engages autonomy 3.0 m before the planned right turn and 7.7 m before the break in the curb while traveling at 8.0 m/s. The May Autonomous Vehicle (e…While traveling north on [XXX], the Autonomous Vehicle Operator (AVO) engages autonomy 3.0 m before the planned right turn and 7.7 m before the break in the curb while traveling at 8.0 m/s. The May Autonomous Vehicle (ego) was planning to make a tight right turn into a parking lot, which the AVO was unaware of when engaging autonomy. The ego jerked to the right upon entering autonomy, hitting a curb and damaging both passenger-side front and rear tires and the right rear tire rim. The AV attempted the right turn despite not having time to slow sufficiently and mounted the curb. The AVO intervened by accelerating and steering back to the left upon striking the curb, manually maneuvering back to the street while striking a second curb on the opposite side of the parking lot driveway. Resimulations without the manual intervention show the ego slowing appropriately and making the right turn into the parking lot. The AVO should have been attentive to the planned route before engaging autonomy. As a result of this incident, planned improvements to the AVOs instructive dash and audio alerts for upcoming turns have begun to be implemented. | |
| 30610-11513 | ADS | Zoox, Inc. | 2025-07 15:32 | Winchester, NV | 2024 ZOOX Zoox | Verified Engaged | Non-Motorist: Cyclist | No Injured Reported | 0 | Intersection | An unoccupied Zoox vehicle in autonomous mode was traveling in the right turn lane on southbound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. At that time, an e-cyclist was tra…An unoccupied Zoox vehicle in autonomous mode was traveling in the right turn lane on southbound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. At that time, an e-cyclist was traveling south on the sidewalk adjacent to southbound [XXX]. As the Zoox vehicle slowed to execute its turn, the e-cyclist rapidly approached the crosswalk in the path ahead of the Zoox vehicle. The Zoox vehicle braked to yield to the approaching e-cyclist. The e-cyclist then veered left and accelerated into the roadway, making contact with the right rear side of the nearly stopped Zoox vehicle. The e-cyclist fell to the ground behind the Zoox vehicle. The Zoox vehicle then started to move and completed the right turn onto [XXX] and completed its mission. The cyclist appears to have ridden away from the scene. A bystander reported the event to Zoox. There was minor damage to the Zoox vehicle, and information was not exchanged with the e-cyclist. The police were later notified. | |
| 30270-11174 | ADS | Waymo LLC | 2025-06 08:16 | Chandler, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Other Fixed Object | No Injured Reported | 10 | Parking Lot | On June [XXX], 2025 at 8:16 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an elevated gate track in a parking lot at [XXX]. The Waymo AV was traveling eastbou…On June [XXX], 2025 at 8:16 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an elevated gate track in a parking lot at [XXX]. The Waymo AV was traveling eastbound in a parking lot at [XXX] through a gate opening when the bottom of the Waymo AV made contact with the elevated gate track. 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-11204 | ADS | Waymo LLC | 2025-06 05:58 | Phoenix, AZ | 2021 JAGUAR I-PACE | Verified Engaged | Van | No Injured Reported | 0 | Parking Lot | On June [XXX], 2025 at 5:58 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a van at the entrance of a parking lot at [XXX]. The Waymo AV was stopped facing sout…On June [XXX], 2025 at 5:58 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a van at the entrance of a parking lot at [XXX]. The Waymo AV was stopped facing south at the entrance of a parking lot at [XXX] while yielding to traffic and preparing to make a left turn at the intersection at [XXX]. As the Waymo AV remained stopped, a van traveling westbound in the rightmost lane on [XXX] traveled onto the north sidewalk of [XXX]. It then entered the parking lot entrance from the sidewalk, traveling perpendicular to the standard direction of travel. The front of the van made contact with the front driver side of the Waymo AV, which was still stationary at intersection, causing the Waymo AV to spin and the front of the Waymo AV to then make contact with a sign pole. 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-11209 | ADS | Waymo LLC | 2025-06 09:05 | Chandler, AZ | 2024 JAGUAR I-PACE | Verified Engaged | Other Fixed Object | No Injured Reported | 10 | Parking Lot | On June [XXX], 2025 at 9:05 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an elevated gate track in a parking lot at [XXX]. The Waymo AV was traveling eastbou…On June [XXX], 2025 at 9:05 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Chandler, Arizona was in a collision involving an elevated gate track in a parking lot at [XXX]. The Waymo AV was traveling eastbound in a parking lot at [XXX] through a gate opening when the bottom of the Waymo AV made contact with the elevated gate track. 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. | |
| 30291-11324 | ADS | Nuro | 2025-06 12:38 | Santa Clara, CA | 2022 TOYOTA Prius | Verified Engaged | Other, see Narrative | No Injured Reported | 13 | Street | On Tuesday, June [XXX], 2025 a Nuro vehicle operating in autonomous mode encountered a trash bin that had been placed away from the curb, sticking out into the travel lane, and due to operator error, the side mirror tapp…On Tuesday, June [XXX], 2025 a Nuro vehicle operating in autonomous mode encountered a trash bin that had been placed away from the curb, sticking out into the travel lane, and due to operator error, the side mirror tapped it. The bin was not damaged or moved, but a plastic attachment to the Nuro vehicle sustained negligible damage. Law enforcement was not involved and there were no injuries reported or VRUs present. | |
| 30410-11101 | ADS | Motional | 2025-06 17:06 | 2024 HYUNDAI Ioniq 5 | Verified Engaged | SUV | No Injured Reported | 0 | Intersection | Redacted by NHTSA as confidential business information | ||
| 30610-11331 | ADS | Zoox, Inc. | 2025-06 23:17 | San Francisco, CA | 2019 TOYOTA Highlander | Verified Engaged | Passenger Car | No Injured Reported | 9 | Street | A Zoox vehicle (Vehicle 1), operating in manual mode, was heading south on [XXX], in the southbound lane, approaching [XXX] in San Francisco, when it encountered a passenger car (Vehicle 2) traveling north and occupying …A Zoox vehicle (Vehicle 1), operating in manual mode, was heading south on [XXX], in the southbound lane, approaching [XXX] in San Francisco, when it encountered a passenger car (Vehicle 2) traveling north and occupying both the northbound and southbound lanes on [XXX]. The Zoox vehicle slowed and moved to the right for the oncoming Vehicle 2 however, as Vehicle 2 passed, its driver's side mirror made contact with the driver's side rear of the Zoox vehicle. The driver of Vehicle 2 failed to stop and exchange information. The Zoox vehicle did not sustain any damage, but Vehicle 2 appeared to have sustained minor damage to its driver's side mirror. There were no reported injuries, and the police were not notified. | |
| 669-11335 v2 | ADS | Hyundai Motor America | 2025-06 17:06 | Paradise, NV | 2024 HYUNDAI Ioniq 5 | Verified Engaged | SUV | No Injured Reported | 0 | Intersection | 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. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. 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. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.