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
32 records match
20253 registriesClear
Narrow it down
What happened
Country
Year
No injury reported2025-12NHTSAMay MobilityArlington30413-13468Passenger Car · struck on the rear · making right turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 2
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- East District Arlington 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.
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.
cause not established30413-13468May MobilitySource file ↗No injury reported2025-12NHTSAAvrideDallas31101-13620Pickup Truck · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Unknown
- SV Precrash Speed (MPH)
- 24
- CP Pre-Crash Movement
- Passing
- 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 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.
cause not established31101-13620AvrideSource file ↗No injury reported2025-12NHTSAMay MobilityArlington30413-13469Passenger Car · struck on the rear · making right turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear
- 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
- 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.
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.
cause not established30413-13469May MobilitySource file ↗No injury reported2025-12NHTSAWaymoInglewood30270-13484SUV · 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)
- 22
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Cloudy
- 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 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.
cause not established30270-13484WaymoSource file ↗No injury reported2025-12NHTSAMay MobilityAtlanta30413-13470SUV · struck on the right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Changing Lanes
- CP Contact Area
- Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- 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.
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.
cause not established30413-13470May MobilitySource file ↗No injury reported2025-12NHTSAAvrideDallas31101-13626Passenger Car · stopped
- Crash With
- Passenger Car
- 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
- Backing
- 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 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.
cause not established31101-13626AvrideSource file ↗No injury reported2025-11NHTSAAvrideAustin31101-13441Passenger 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
- 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.
Avride car was rear-ended at the intersection.
cause not established31101-13441AvrideSource file ↗No injury reported2025-11NHTSAAvrideAustin31101-13438Passenger Car · struck on the rear right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 15
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- 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.
Rear end collision, another vehicle hit Avride car from behind when traffic light became to be yellow.
cause not established31101-13438AvrideSource file ↗No injury reported2025-11NHTSAAvrideAustin31101-13439Passenger Car · struck on the front · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 30
- 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.
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.
cause not established31101-13439AvrideSource file ↗No injury reported2025-11NHTSATeslaAustin13781-13237struck on the rear left, rear right · stopped
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left, Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TESLA
- Model
- Model Y
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.
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.
cause not established13781-13237TeslaSource file ↗No injury reported2025-11NHTSAMay MobilityAtlanta30413-13249struck on the right, bottom · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Right, Bottom
- SV Precrash Speed (MPH)
- 5
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- Weather
- Cloudy, Rain
- 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.
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.
cause not established30413-13249May MobilitySource file ↗No injury reported2025-11NHTSAMay MobilityAtlanta30413-13248Passenger Car · struck on the front · stopped
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 1
- CP Pre-Crash Movement
- Backing
- CP Contact Area
- Rear Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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.
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.
cause not established30413-13248May MobilitySource file ↗No injury reported2025-11NHTSAAvrideAustin31101-13440Passenger Car · struck on the front right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 20
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Rain
- 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.
Civilian vehicle ran red light while the Avride car driver was entering the intersection on a green light.
cause not established31101-13440AvrideSource file ↗No injury reported2025-11NHTSAMay MobilityGrand Rapids30413-13083struck on the front left · parking maneuver
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Parking Maneuver
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 25
- 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.
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.
cause not established30413-13083May MobilitySource file ↗No injury reported2025-10NHTSAWaymoPhoenix30270-11889struck 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)
- 47
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Highway / Freeway
- Weather
- Partly Cloudy
- 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 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.
cause not established30270-11889WaymoSource file ↗No injury reported2025-10NHTSAWaymoPhoenix30270-11859SUV · struck on the rear left, right · proceeding straight
- Crash With
- SUV
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left, Right
- SV Precrash Speed (MPH)
- 31
- CP Pre-Crash Movement
- Making Left Turn
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- Phoenix 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 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.
cause not established30270-11859WaymoSource file ↗No injury reported2025-10NHTSAWaymoLos Angeles30270-11865Heavy Truck · struck on the rear · stopped
- Crash With
- Heavy 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
- Backing
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- Weather
- Cloudy
- 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 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.
cause not established30270-11865WaymoSource file ↗No injury reported2025-10NHTSAWaymoSan Francisco30270-12070Animal · struck on the rear left · proceeding straight
- Crash With
- Animal
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Other, see Narrative
- 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 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.
cause not established30270-12070WaymoSource file ↗No injury reported2025-09-20Press recordsUnitree Robotics
This vulnerability affects multiple Unitree robot models including Go2, G1, H1 and B2 series robots up to the latest firmware from today [20. September 2025].
cause not establishedUnitree RoboticsRead the record ↗No injury reported2025-09NHTSATeslaAustin13781-11787Animal · struck on the front left · stopped
- Crash With
- Animal
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 27
- CP Pre-Crash Movement
- NM Crossing Roadway
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Partly Cloudy
- Investigating Agency
- None
- Make
- TESLA
- Model
- Model Y
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.
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.
cause not established13781-11787TeslaSource file ↗No injury reported2025-08NHTSAMay MobilityEden Prairie30413-11669Pickup Truck · struck on the rear right · proceeding straight
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear Right
- SV Precrash Speed (MPH)
- 13
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Eden Prairie Police Dept
- 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.
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.
cause not established30413-11669May MobilitySource file ↗No injury reported2025-08NHTSAWaymoSan Francisco30270-11605SUV · struck on the rear · parked
- Crash With
- SUV
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Parked
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Right
- 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 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.
cause not established30270-11605WaymoSource file ↗No injury reported2025-07NHTSAZooxWinchester30610-11513Non-Motorist: Cyclist · struck on the rear left · making right turn
- Crash With
- Non-Motorist: Cyclist
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Rear Left
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Other, see Narrative
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 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.
cause not established30610-11513ZooxSource file ↗No injury reported2025-07NHTSAMay MobilityPeachtree Corners30413-11487Passenger Car · struck on the front · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 20
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Gwinnett County 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.
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.
cause not established30413-11487May MobilitySource file ↗No injury reported2025-07NHTSANuro, Inc.Mountain View30291-11458Passenger Car · struck on the rear · making left turn
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Left Turn
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 3
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Right
- Within ODD?
- [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 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.
cause not established30291-11458Nuro, Inc.Source file ↗No injury reported2025-07NHTSAMay MobilityAtlanta30413-11489struck on the right · making right turn
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Making Right Turn
- SV Contact Area
- Right
- SV Precrash Speed (MPH)
- 18
- 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.
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.
cause not established30413-11489May MobilitySource file ↗No injury reported2025-06NHTSAWaymoChandler30270-11174struck on the bottom · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Bottom
- SV Precrash Speed (MPH)
- 10
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- 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 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.
cause not established30270-11174WaymoSource file ↗No injury reported2025-06NHTSANuro, Inc.Santa Clara30291-11324struck 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)
- 13
- CP Pre-Crash Movement
- Stopped
- CP Contact Area
- Front Right
- 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 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.
cause not established30291-11324Nuro, Inc.Source file ↗No injury reported2025-06NHTSAWaymoPhoenix30270-11204Van · struck on the front · stopped
- Crash With
- Van
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Front
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Lane / Road Departure
- CP Contact Area
- Front Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- 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 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.
cause not established30270-11204WaymoSource file ↗No injury reported2025-06NHTSAZooxSan Francisco30610-11331Passenger Car · struck on the rear · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 9
- CP Pre-Crash Movement
- Crossing into Opposing Lane
- CP Contact Area
- Front
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Clear
- Investigating Agency
- None
- Make
- TOYOTA
- Model
- Highlander
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.
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.
cause not established30610-11331ZooxSource file ↗No injury reported2025-06NHTSAWaymoChandler30270-11209struck on the bottom · proceeding straight
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Bottom
- SV Precrash Speed (MPH)
- 10
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Parking Lot
- 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 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.
cause not established30270-11209WaymoSource file ↗No injury reported2025-04-09Health CanadaRA-77225Aiper Seagull Pro ZT6001 Cordless Robotic Swimming Pool Vacuum Cleaner
Aiper Seagull Pro ZT6001 Cordless Robotic Swimming Pool Vacuum Cleaner — Large current adapter can overheat, posing burn and fire hazards. One unit caught fire in Canada while charging (March 2025); no injuries and no property damage beyond the unit. ~2,606 units sold in Canada Jul 2023-Apr 2024 via Best Buy Canada, Tanguay, Amazon. Consumers told to stop use and contact Aiper for a free replacement Scuba S1 cleaner.
cause not establishedRA-77225Read the record ↗