DEPLOYDatabase

Incident · Collision

ADS crash report in Arlington, TX involving a TOYOTA Sienna (NHTSA SGO 30413-16664)

On August [XXX], 2026, at 2:17 p.m. CT, a May Mobility autonomous vehicle (AV) operating northbound in autonomous mode stopped at a stop sign on [XXX] in Arlington, Texas. The May Mobility AV began to make a right turn into the curb lane of eastbound [XXX], but stopped mid-turn to yield to a crossing vehicle.

A passenger vehicle trailing the May Mobility AV advanced into the crosswalk at three mph, making contact with the May Mobility AV's rear left corner, causing moderate damage to the May Mobility AV’s rear left-side bumper and quarter panel, and damaging the passenger vehicle’s front right tire. No injuries were reported, no towing was needed, and no airbags were deployed.

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 becomes available.

Occurred 2026-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.

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Arlington, TX involving a TOYOTA Sienna (NHTSA SGO 30413-16664)?
On August [XXX], 2026, at 2:17 p.m. CT, a May Mobility autonomous vehicle (AV) operating northbound in autonomous mode stopped at a stop sign on [XXX] in Arlington, Texas. The May Mobility AV began to make a right turn into the curb lane of eastbound [XXX], but stopped mid-turn to yield to a crossing vehicle. A passenger vehicle trailing the May Mobility AV advanced into the crosswalk at three mph, making contact with the May Mobility AV's rear left corner, causing moderate damage to the May Mobility AV’s rear left-side bumper and quarter panel, and damaging the passenger vehicle’s front right tire. No injuries were reported, no towing was needed, and no airbags were deployed. 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 becomes available.
When did this incident occur?
The incident is recorded as occurring on August 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 Arlington, TX involving a TOYOTA Sienna (NHTSA SGO 30413-16664)?
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 Arlington, TX involving a TOYOTA Sienna (NHTSA SGO 30413-16664)?
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 Arlington, TX involving a TOYOTA Sienna (NHTSA SGO 30413-16664)?
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-10-18

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-10-18

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 Arlington, TX involving a TOYOTA Sienna (NHTSA SGO 30413-16664).

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 9ca00f6a-4d0e-44a7-aed5-aa8a6669b275