ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14815)
[COLLISION]Apr 1, 2026 · Avride · Avride delivery robot · Bowling Green, Ohio, USA
Failure Mode
COLLISION
Event Date
Apr 1, 2026
Primary Entity
Avride
Robotic Platform
Avride delivery robot
Jurisdiction / Location
Bowling Green, Ohio, USA
Audit Standard
Physical State Verified
Incident Abstract & Audit Findings
On April [XXX], 2026 at 11:47 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was stopped at a red light facing westbound on [XXX] in autonomous mode behind an SUV. While stopped at the red light, a passenger car approached the AVRIDE AV from behind at high speeds without slowing down or breaking as it approached the red light.
System & Fleet Architecture
Operating Manufacturer
Hardware Platform
Operational Sectors
Primary Sources & Evidentiary Filings
- Inspect Filing
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-31101-14815
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-31101-14815
Related Incidents & Failure Precedents
6 records on file- Amazon Prime Air MK30 drone crashes into residential garden in Darlington, UK, prompting AAIB investigation[COLLISION]
Jul 29, 2026 · Amazon · Amazon Astro · Seattle
Details - Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured[COLLISION]
Jul 26, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Waymo robotaxi involved in two-vehicle collision in Los Angeles, multiple people hospitalized[COLLISION]
Jul 26, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Waymo robotaxi involved in two-vehicle crash in LA's Pico-Union, one person critically injured[COLLISION]
Jul 25, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Tesla remote operator crashed a Robotaxi into a tree stump in Houston, NHTSA data shows[COLLISION]
Jul 20, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA
Details - Tesla robotaxi remote operator crashed vehicle into metal fence in Houston[COLLISION]
Jul 20, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA
Details
Incident Context & FAQ
What happened in ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14815)?
On April [XXX], 2026 at 11:47 PM, an AVRIDE autonomous vehicle(the "AVRIDE AV") was in a collision in Dallas, TX on [XXX] near [XXX]. The AVRIDE AV was stopped at a red light facing westbound on [XXX] in autonomous mode behind an SUV. While stopped at the red light, a passenger car approached the AVRIDE AV from behind at high speeds without slowing down or breaking as it approached the red light. This maneuver from the passenger car resulted in the front of the passenger car making contact with the rear of the AVRIDE AV. The force from the collision caused the AVRIDE AV to move forward which resulted in the front of the AVRIDE AV also making contact with the rear of the SUV stopped in front of it at the red light. All 3 vehicles sustained damage. No injuries were reported.
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.
What robot was involved in ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14815)?
Avride delivery robot by Avride is the recorded robot involved in this incident at Bowling Green, Ohio, USA.
Has anyone responded to ADS crash report in Dallas, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-14815)?
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-14815)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.