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

[COLLISION]

Nov 1, 2025 · Avride · Avride delivery robot · Bowling Green, Ohio, USA

Failure Mode

COLLISION

Event Date

Nov 1, 2025

Primary Entity

Avride

Robotic Platform

Avride delivery robot

Jurisdiction / Location

Bowling Green, Ohio, USA

Audit Standard

Physical State Verified

Incident Abstract & Audit Findings

Rear end collision, another vehicle hit Avride car from behind when traffic light became to be yellow.

System & Fleet Architecture

Operating Manufacturer

Hardware Platform

Avride delivery robotView Spec

Operational Sectors

Physical AI / Robotics

Primary Sources & Evidentiary Filings

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

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

Related Incidents & Failure Precedents

6 records on file

Incident Context & FAQ

What happened in ADS crash report in Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13438)?

Rear end collision, another vehicle hit Avride car from behind when traffic light became to be yellow.

When did this incident occur?

The incident is recorded as occurring on November 1, 2025 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 Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13438)?

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 Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13438)?

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 Austin, TX involving a HYUNDAI Ioniq 5 (NHTSA SGO 31101-13438)?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.