May Mobility Unexpected or inappropriate behaviour — Indianapolis, IN, US — August 2021
What is observable from the evidence
No individually observed facts are recorded for this record; see its structured details and sources instead.
Automation status
Unknown
Whether the driving-automation feature was engaged is a separate question from whether it caused the event.
System / software version
Not identified in the available sources.
Causal attribution
Undetermined
The available evidence does not establish a cause. Involvement of a driving-automation system is not the same as its being a cause.
No other party was involved, but automation was not confirmed engaged at the moment of contact (or a human/teleoperator is described as having taken control first) and no evidence links a prior automated maneuver to the event. Asserting automation contribution from bare subject-vehicle involvement alone would not be supported — see the rulebook's automation-engagement-vs-contribution distinction.
What remains unknown
The available evidence does not leave anything specific unestablished for this event.
Interpretation
No interpretation is offered for this event.
Sources & evidence
The sources below are the evidence. The summary and any interpretation on this page are written by White Box Autonomy and are not themselves evidence.
Regulatory record · Toyota Motor Engineering & Manufacturing
NHTSA SGO report 1306-1247 (v1)
Published September 2021 · Retrieved 6 September 2026
Regulatory record · May Mobility
NHTSA SGO report 30413-1206 (v1)
Published September 2021 · Retrieved 6 September 2026
About this record
Origin: Source-derived. What this means.
Record last reviewed or updated: 6 September 2026.
To report an error or raise a concern about this record, contact zuduo.zheng@uq.edu.au.