_Incident · Collision_

# ADS crash report in Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-14092)

Canonical ID: `0a9422e0-ee61-46d9-b054-1a5ea5b4ca35`

- **Occurred:** 2026-02-01
- **Kind:** `collision`
- **Status (derived):** active
- **Company:** [Motional](/companies/motional.md) (id: `c785150a-ee0b-4a51-bab8-384a0d5cd50e`)

On February [XXX], 2026, at approximately 9:55 AM PT, a Motional Ioniq 5 AV (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the driver’s seat. The AV was stopped southbound on [XXX] in the left-turn lane at the intersection with [XXX], positioned behind two other stopped vehicles.

At that time, a sedan traveling eastbound on [XXX] was being actively pursued by a law enforcement vehicle which had its  flashing lights and siren activated.  Both vehicles turned left and proceeded northbound on [XXX] but using  the southbound lanes.   As the sedan traveled in the wrong lanes on [XXX], it struck the passenger-side front end and right wheel well of the Motional vehicle which remained stopped in the left turn lane the entire time. The sedan did not stop after striking the Motional vehicle and continued traveling in the wrong (southbound) lanes and counter to the flow of traffic while it continued fleeing from police.

No occupants of the Motional vehicle were injured. The Motional vehicle sustained damage to the front end and was towed from the scene. The Las Vegas Metropolitan Police Department is investigating the incident, but a police report is not yet available

## Sources (1)

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

## Common questions

### What happened in ADS crash report in Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-14092)?

On February [XXX], 2026, at approximately 9:55 AM PT, a Motional Ioniq 5 AV (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the driver’s seat. The AV was stopped southbound on [XXX] in the left-turn lane at the intersection with [XXX], positioned behind two other stopped vehicles.

At that time, a sedan traveling eastbound on [XXX] was being actively pursued by a law enforcement vehicle which had its  flashing lights and siren activated.  Both vehicles turned left and proceeded northbound on [XXX] but using  the southbound lanes.   As the sedan traveled in the wrong lanes on [XXX], it struck the passenger-side front end and right wheel well of the Motional vehicle which remained stopped in the left turn lane the entire time. The sedan did not stop after striking the Motional vehicle and continued traveling in the wrong (southbound) lanes and counter to the flow of traffic while it continued fleeing from police.

No occupants of the Motional vehicle were injured. The Motional vehicle sustained damage to the front end and was towed from the scene. The Las Vegas Metropolitan Police Department is investigating the incident, but a police report is not yet available

### When did this incident occur?

The incident is recorded as occurring on February 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 Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-14092)?

The incident is recorded as involving Motional on the DEPLOY registry. No specific robot model is linked to this incident in the registry.

### Has anyone responded to ADS crash report in Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-14092)?

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 Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-14092)?

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


_API: GET /v1/incidents/0a9422e0-ee61-46d9-b054-1a5ea5b4ca35 · sources: /v1/incidents/0a9422e0-ee61-46d9-b054-1a5ea5b4ca35/sources · responses: /v1/incidents/0a9422e0-ee61-46d9-b054-1a5ea5b4ca35/responses · status: /v1/incidents/0a9422e0-ee61-46d9-b054-1a5ea5b4ca35/status · canonical URL: /incidents/nhtsa-sgo-30410-14092_