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
3 records match for May Mobility
2025–20261 registryClear
Narrow it down
What happened
Country
Year
Minor injury2026-04NHTSAAtlanta30413-14938struck on the rear, front · proceeding straight
- Crash With
- Other, see Narrative
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Rear, Front
- SV Precrash Speed (MPH)
- 21
- CP Pre-Crash Movement
- Proceeding Straight
- CP Contact Area
- Rear Left, Front Left
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Intersection
- Weather
- Clear
- Investigating Agency
- Atlanta Police Department Zone 5
- 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 1:59 pm EST, a third-party vehicle, John Deere UTV Crossover Gator Utility Vehicle, collided with a May Mobility Autonomous Vehicle (AV) in Atlanta, Georgia, at the intersection of [XXX] and [XXX]. The May Mobility AV was traveling south on [XXX] in Atlanta, Georgia approaching the intersection of [XXX] on a green traffic light, with its automated driving system engaged in autonomous mode. The third- party vehicle was traveling west on [XXX] approaching a red light at [XXX] when it ran the red light and proceeded into the intersection without slowing, making contact with the May Mobility AV. The May Mobility AV began to apply the brakes as the third- party vehicle started to run the red light. During the May Mobility AVâs braking, the telematics confirm that the Autonomous Vehicle Operator also started to intervene, moving the steering wheel to the right and braking more forcefully. The collision was unavoidable with the third-party vehicle making contact with the front left bumper and the driver side rear passenger door of the May Mobility AV. The May Mobility AV was towed from the scene. May Mobility is reporting this crash under Request No. 1 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available.
cause not established30413-14938May MobilitySource file ↗Minor injury2026-01NHTSAAtlanta30413-13853struck on the front left · lane / road departure
- Crash With
- Other Fixed Object
- Highest Injury Severity Alleged
- Minor W/ Hospitalization
- SV Pre-Crash Movement
- Lane / Road Departure
- SV Contact Area
- Front Left
- SV Precrash Speed (MPH)
- 29
- Within ODD?
- Yes
- Automation System Engaged?
- ADS
- Roadway Type
- Street
- Weather
- Cloudy
- Investigating Agency
- Atlanta Police Dept. Zone 5
- 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 January [XXX], 2026 at 7:48 AM, a May Mobility Autonomous Vehicle (AV) was in a collision with a fire hydrant in Atlanta, Georgia on [XXX]near[XXX]. The May Mobility AV was traveling westbound on [XXX]in Atlanta, Georgia with its automated driving system engaged in autonomy mode when the Autonomous Vehicle Operator (AVO) fell asleep while his right hand rested on the right side of the steering wheel. In-cabin video and telematics confirms that the AVO's hand restricted the motion of the steering wheel, preventing the autonomous system from keeping the vehicle in its lane. Though the AV braked after perceiving the exit from its travel lane, collision with the fire hydrant could not be avoided. The air bags deployed during the collision and the AV was towed from the scene. The AVO was transported by ambulance to the hospital with minor injuries.
cause not established30413-13853May MobilitySource file ↗Minor injury2025-08NHTSAPeachtree Corners30413-11593Passenger Car · struck on the front right · proceeding straight
- Crash With
- Passenger Car
- Highest Injury Severity Alleged
- Minor W/O Hospitalization
- SV Pre-Crash Movement
- Proceeding Straight
- SV Contact Area
- Front Right
- SV Precrash Speed (MPH)
- 13
- CP Pre-Crash Movement
- Making Right Turn
- CP Contact Area
- Rear 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 vehicle was travelling in an autonomous vehicle (AV) only lane approaching an intersection. A vehicle travelling to the left of the May shuttle (ego) in the non-AV lane performed a right hand turn across the May vehicle¢ÃÂÃÂs path. Given the full stopping power and the limited space with which the ego had to stop, the ego was physically unable to stop in time before impact. 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 are several signs that instruct other traffic to yield to the vehicles in the AV lane. There were no autonomy faults or errors which led to this incident. Update: There was no indication of injury or request for medical attention at the scene. The police report states "Driver 1 complained of neck pain." For this reason, we are updating the highest severity injury alleged field to reflect the âminor w/o hospitalizationâ injury level. The remaining content of this report is unchanged from the initial report submitted on September [XXX], 2025, Report ID #[XXX].
cause not established30413-11593May MobilitySource file ↗