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
1,112 records match
2017–20266 registriesClear
Narrow it down
What happened
Country
Year
Property damage only2025-06NHTSAWaymoPhoenix30270-11177SUV · struck on the rear right · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. 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
- 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 12:45 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing south in the second from the right lane on [XXX] for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, an SUV that was initially stopped directly behind the Waymo AV approached the Waymo AV and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. 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-11177WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11194SUV · struck on the rear · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. 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
- Right
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 4:18 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing southwest on [XXX] for a red light at the intersection at [XXX]. While the Waymo AV remained stopped, an SUV that was initially stopped directly behind the Waymo AV proceeded to maneuver around the Waymo on the left, and the passenger side of the SUV made contact with the rear driver side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11194WaymoSource file ↗Property damage only2025-06NHTSAWaymoSan Francisco30270-11162SUV · struck on the rear · stopped
- Crash With
- SUV
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- 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 June [XXX], 2025 at 4:47 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and making a slight right onto [XXX] when it came to a stop on the right side of its lane to yield to an SUV traveling southwestbound on [XXX]. The SUV attempted to pass the stationary Waymo AV, stopped momentarily, and then began to reverse. The SUV then continued its attempt to pass, and the front driver side of the SUV made contact with the rear driver side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11162WaymoSource file ↗Property damage only2025-06NHTSAWaymoPhoenix30270-11206struck on the front right · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 21
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- 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 11:04 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a tire on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] in the second from the right lane when several tires fell from a trailer pulled by a recreation vehicle traveling westbound on [XXX] in front of the Waymo AV. The tires rolled into the roadway and the front of the Waymo AV made contact with one of the tires, which then went under 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. The passenger in the Waymo AV was not belted at the time of the collision. 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-11206WaymoSource file ↗Property damage only2025-06NHTSAZooxParadise30610-11166Pickup Truck · struck on the rear left, rear, rear right · stopped
- Crash With
- Pickup Truck
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Stopped
- SV Contact Area
- Rear Left, Rear, Rear Right
- SV Precrash Speed (MPH)
- 0
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Front Left, Front, Front Right
- 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 autonomous mode was traveling in the left through lane (lane #2) on westbound [XXX], approaching [XXX] in Las Vegas. The Zoox vehicle operator disengaged from autonomy after the traffic light at [XXX] transitioned from green to yellow and braked, bringing the Zoox vehicle to a stop, at which point it was rear-ended by a pickup truck (Vehicle 2) traveling behind. Both vehicles sustained minor damage however, the Zoox vehicle was towed from the scene as its operator was not comfortable driving it back. There were no reported injuries, and the police were not notified.
cause not established30610-11166ZooxSource file ↗Property damage only2025-04NHTSAWaymoPhoenix30270-11297struck on the front right, bottom · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Property Damage. No Injured Reported
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right, Bottom
- SV Precrash Speed (MPH)
- 5
- CP Pre-Crash Movement
- Other, see Narrative
- CP Contact Area
- Unknown
- 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 April [XXX], 2025 at 7:21 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a chain at a parking lot entrance at [XXX]. The Waymo AV was traveling westbound on [XXX] when it made a left turn into a parking lot at [XXX]. As the Waymo AV proceeded to enter the parking lot, the front of the Waymo AV made contact with a chain hanging across the entrance to the parking lot. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The chain sustained damage. Waymo became aware of damage to the chain on June 26th, 2025. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
cause not established30270-11297WaymoSource file ↗Property damage only2022-07-04UK OPSS2111-0087Husqvarna Automower 435X AWD and 535 AWD robotic lawnmower
Husqvarna Automower 435X AWD and 535 AWD robotic lawnmower — OPSS product recall 2111-0087: Husqvarna Automower 435X AWD and 535 AWD robotic lawnmowers recalled due to fire risk from a charging pattern stressing batteries to unusual levels of degradation. 5 reported incidents of lawnmowers catching fire while charging. Manufacturer arranged battery replacement via dealers plus two mandatory software updates.
cause not established2111-0087Read the record ↗Property damage only2021-12-09Health CanadaRA-63684Husqvarna Automower 435X AWD and Automower 535 AWD robotic lawnmowers
Husqvarna Automower 435X AWD and Automower 535 AWD robotic lawnmowers — Battery may degrade after roughly 1,450 charging cycles and overheat, creating a fire risk. No injuries in Canada or the US; 5 international incidents where the malfunction damaged equipment. Husqvarna offered free battery replacement to units with 1,200+ cycles and two free software updates via the Automower Connect App to prevent degradation.
cause not establishedRA-63684Read the record ↗Property damage only2021-09-19Japan NITEA202200442Electric vacuum cleaner (self-propelled/robot type), model SY-111
Electric vacuum cleaner (self-propelled/robot type), model SY-111 — A self-propelled (robot) vacuum cleaner caught fire while connected to its charging stand at a residence in Chiba Prefecture, burning the unit and the surrounding area. NITE's investigation found a lithium-ion battery cell had likely overheated and ignited, but due to the severity of the burn damage it could not conclusively determine whether the product itself was the cause. No injuries were reported.
cause not establishedA202200442Read the record ↗Property damage only2021-07-16Press recordsOcado Group
the collision of three bots on the grid resulting in a fire.
cause not establishedOcado GroupRead the record ↗Property damage only2019-01-01Press recordsOcado Group
an electrical fault at one of the first generation battery charging units at the edge of the ambient storage grid at the Andover plant caused the plastic lid on the top of a grocery-carrying robot to catch light.
cause not establishedOcado GroupRead the record ↗Property damage only2017-07-17Press recordsKnightscope
Around 2 p.m., the robot veered off its predetermined path and plunged into the fountain in the center of Washington Harbour.
cause not establishedKnightscopeRead the record ↗