Find a safety record
Every incident, injury and recall on file, from the national registries that publish them. Search a maker, a model, a town or a reference number — or narrow by what happened. Each record is the registry's own text, reproduced without rewriting, with the reference that locates it at the source. Registries count different things, so a total is a count of FILINGS and never a measure of how dangerous something is. How the record was collected.
Or jump to a maker
21 records match
20261 registryClear
Narrow it down
What happened
Country
Year
No injury reported2026-06NHTSAAvrideDallas31101-15587SUV · struck on the front · making left turn
- Crash With
- SUV
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 4
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-15587AvrideSource file ↗No injury reported2026-06NHTSAAvrideDallas31101-15477Passenger Car · struck on the left · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 4
- CP Pre-Crash Movement
- Stopped
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Partly Cloudy
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-15477AvrideSource file ↗No injury reported2026-05NHTSAAvrideDallas31101-15093struck on the top · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Top
- SV Precrash Speed (MPH)
- 10
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-15093AvrideSource file ↗No injury reported2026-05NHTSAMay MobilityArlington30413-15463struck on the front left · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 33
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Sienna
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30413-15463May MobilitySource file ↗No injury reported2026-05NHTSAMay MobilityArlington30413-15464struck on the front left · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 32
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Sienna
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30413-15464May MobilitySource file ↗No injury reported2026-04NHTSAWaymoVenice30270-14578Pickup Truck · struck on the rear · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30270-14578WaymoSource file ↗No injury reported2026-04NHTSANuro, Inc.Santa Clara30291-14538Motorcycle · struck on the left · proceeding straight
- Crash With
- Motorcycle
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Left
- SV Precrash Speed (MPH)
- 19
- CP Pre-Crash Movement
- Passing
- CP Contact Area
- Unknown
- Within ODD?
- [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- TOYOTA
- Model
- Prius
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30291-14538Nuro, Inc.Source file ↗No injury reported2026-04NHTSAMay MobilityAtlanta30413-15019Passenger Car · struck on the rear right · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Atlanta Police Department
- Make
- TOYOTA
- Model
- Sienna
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30413-15019May MobilitySource file ↗No injury reported2026-04NHTSAWaymoLos Angeles30270-14707Passenger Car · struck on the front left · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 12
- CP Pre-Crash Movement
- Parked
- CP Contact Area
- Rear
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- ZEEKR
- Model
- RT
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30270-14707WaymoSource file ↗No injury reported2026-03NHTSAMay MobilityArlington30413-14624SUV · struck on the rear right · making right turn
- Crash With
- SUV
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 6
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Cloudy
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Sienna
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30413-14624May MobilitySource file ↗No injury reported2026-03NHTSAAvrideAustin31101-14649Van · stopped
- Crash With
- Van
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Unknown
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-14649AvrideSource file ↗No injury reported2026-03NHTSAAvrideDallas31101-14650struck on the front right · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 23
- CP Pre-Crash Movement
- Stopped
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-14650AvrideSource file ↗No injury reported2026-03NHTSAWaymoRedwood City30270-14289Passenger Car · struck on the rear left · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 14
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Investigating Agency
- Redwood Police Department
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30270-14289WaymoSource file ↗No injury reported2026-03NHTSAWaymoLos Angeles30270-14220SUV · struck on the rear left · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 31
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- JAGUAR
- Model
- I-PACE
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30270-14220WaymoSource file ↗No injury reported2026-03NHTSAAvrideDallas31101-14647struck on the front right · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 29
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-14647AvrideSource file ↗No injury reported2026-03NHTSAAvrideDallas31101-14652making left turn
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Unknown
- SV Precrash Speed (MPH)
- 13
- CP Pre-Crash Movement
- Stopped
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-14652AvrideSource file ↗No injury reported2026-03NHTSAWeRideSan Jose30792-14655Pickup Truck · struck on the rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- NISSAN
- Model
- Ariya Hatchback
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30792-14655WeRideSource file ↗No injury reported2026-02NHTSAZooxLas Vegas30610-14340Pickup Truck · struck on the rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- ZOOX
- Model
- Zoox
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30610-14340ZooxSource file ↗No injury reported2026-01NHTSAAurora InnovationEl Paso30530-14071struck on the front left · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 55
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Highway / Freeway
- Weather
- Cloudy
- Make
- PETERBILT
- Model
- 579
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established30530-14071Aurora InnovationSource file ↗No injury reported2026-01NHTSAAvrideDallas31101-13761Pickup Truck · struck on the right · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 30
- CP Pre-Crash Movement
- Entering Traffic
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Dallas Police Department
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-13761AvrideSource file ↗No injury reported2026-01NHTSAAvrideDallas31101-14068struck on the front · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 27
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Make
- HYUNDAI
- Model
- Ioniq 5
SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.
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.
cause not established31101-14068AvrideSource file ↗