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
62 records match
2020–20263 registriesClear
Narrow it down
What happened
Country
Year
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 ↗No injury reported2023-10-18Press recordseufy
The battery packs can overheat while charging or soon after charging, posing a fire hazard.
cause not establishedeufyRead the record ↗No injury reported2022-08-25Press recordsBear Robotics
Brinker International has paused a robotics test with Bear Robotics, which deployed server robots at 61 Chili's restaurants, CEO Kevin Hochman said Wednesday during Brinker's earnings call.
cause not establishedBear RoboticsRead the record ↗No injury reported2022-04-12Press recordsAethon
An unauthenticated attacker can connect to the TUG Home Base Server websocket to take control of TUG robots.
cause not establishedAethonRead the record ↗No injury reported2021-12-01Press recordsTiny Mile
Today, the Toronto City Council voted to ban sidewalk robots until the council has the opportunity to further study the effects they have on the community.
cause not establishedTiny MileRead the record ↗No injury reported2020-11-02Press recordsBossa Nova
Walmart Inc. has ended its contract with Bossa Nova Robotics Inc.
cause not establishedBossa NovaRead the record ↗