DEPLOYDatabase

Incident · Collision

ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14924)

On April [XXX], 2026 at 2:54 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling southeastbound on [XXX] in autonomous mode when it stopped at a stop sign at the intersection with [XXX]. The AVRIDE AV was being trailed by an SUV. It was raining at the time. After stopping at the stop sign, the AVRIDE AV began to initiate a right hand turn onto [XXX]. As the AVRIDE AV began to turn right, a cyclist approached the AVRIDE AV from behind. The cyclist disobeyed traffic rules and passed the SUV which was behind the AVRIDE AV while also driving through the stop sign without stopping. While attempting to pass the AVRIDE AV, the cyclist lost control due to the slick roads from the rain as the cyclist approached the intersection. This maneuver resulted in the front of the cyclist making contact with the rear of the AVRIDE AV. The cyclist left the scene following the incident. No injuries were reported. The AVRIDE AV sustained damage.

Occurred 2026-04-01 · Avride

Track ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14924)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14924)?
On April [XXX], 2026 at 2:54 PM, an AVRIDE autonomous vehicle (the "AVRIDE AV") was in a collision in Dallas, Texas at the intersection of [XXX] and [XXX]. The AVRIDE AV was traveling southeastbound on [XXX] in autonomous mode when it stopped at a stop sign at the intersection with [XXX]. The AVRIDE AV was being trailed by an SUV. It was raining at the time. After stopping at the stop sign, the AVRIDE AV began to initiate a right hand turn onto [XXX]. As the AVRIDE AV began to turn right, a cyclist approached the AVRIDE AV from behind. The cyclist disobeyed traffic rules and passed the SUV which was behind the AVRIDE AV while also driving through the stop sign without stopping. While attempting to pass the AVRIDE AV, the cyclist lost control due to the slick roads from the rain as the cyclist approached the intersection. This maneuver resulted in the front of the cyclist making contact with the rear of the AVRIDE AV. The cyclist left the scene following the incident. No injuries were reported. The AVRIDE AV sustained damage.
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 Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14924)?
The incident is recorded as involving Avride on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14924)?
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 Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14924)?
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 Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14924).

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 bc2c14b2-abeb-4c92-b772-710d1616f749