DEPLOYDatabase

Incident · Collision

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

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.

Occurred 2026-04-01 · May Mobility

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-15019)?
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.
When did this incident occur?
The incident is recorded as occurring on April 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-15019)?
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-15019)?
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-15019)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (1 primary) · last reviewed 2026-07-12

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-07-12

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-15019).

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 3026e58b-1b3f-4d8d-9a0e-f263ef77acb7