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
6 records match for May Mobility
20261 registryClear
Narrow it down
What happened
Country
Year
No injury reported2026-05NHTSAArlington30413-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-05NHTSAArlington30413-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-04NHTSAAtlanta30413-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 ↗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 ↗No injury reported2026-03NHTSAArlington30413-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 ↗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 ↗