DEPLOYDatabase

Incident · Collision

ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853)

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.

Occurred 2026-01-01 · May Mobility

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853)

Machine-readable surfaces

Sources (1)

  1. https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30413-13853

Common questions

What happened in ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853)?
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.
When did this incident occur?
The incident is recorded as occurring on January 1, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853)?
The incident is recorded as involving May Mobility on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853)?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 1 source (1 primary) · last reviewed 2026-07-14

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-07-14

Sources by quality tier

1
primary-regulatory-filing
Regulatory filing

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853).

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID 02a70373-8a89-48f1-84c3-052f77ff8f41