The MachineRecord
Reported to NHTSA

Peachtree Corners, GA

Operators running driving automation here have filed 2 crash reports with the federal regulator. None of them record an injury reaching hospitalisation.

Reading the numbers

May Mobility filed 2 of the 2 reports (100%). The most common outcome recorded is "Minor W/O Hospitalization" (1). No report records an injury reaching hospitalisation, so none of them is a case in the register. The other party is most often passenger car (2).

By operator

  • May Mobility2

By outcome

  • Minor W/O Hospitalization1
  • No Injured Reported1

Crash with

  • Passenger Car2
Filings

The reports themselves

Narratives are written by the operator. Personal detail is removed by NHTSA before publication, which is why names appear as [XXX].

30413-11593May Mobility2025-08Minor W/O Hospitalizationwith passenger car
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…

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].

30413-11487May Mobility2025-07No Injured Reportedwith passenger car
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…

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.

A filing records that a crash happened and who was involved. It does not establish fault. Reports are amended as an operator learns more, and the register keeps the latest version. How this is verified.

Weekly digest

New cases, once a week, by email

Every case added to the register in the last seven days, with its sources. Free, no account, and the register is the only sender.

One email a week, Monday morning. Unsubscribe in one click.