DEPLOYDatabase

Incident · Collision

ADS crash report in Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593)

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.

Occurred 2025-08-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 Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593)?
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.
When did this incident occur?
The incident is recorded as occurring on August 1, 2025 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 Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593)?
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 Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593)?
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 Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593)?
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 Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593).

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 a8cdf5a2-3d18-4e63-936a-f88beeea9230