ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14263)
[COLLISION]Mar 1, 2026 · Zoox · Zoox Robotaxi · Miami
Failure Mode
COLLISION
Event Date
Mar 1, 2026
Primary Entity
Zoox
Robotic Platform
Zoox Robotaxi
Jurisdiction / Location
Miami
Audit Standard
Physical State Verified
Incident Abstract & Audit Findings
An occupied Zoox autonomous vehicle traveling southeast on [XXX] stopped behind traffic in the outer left turn lane (lane #2) for a red traffic signal at [XXX] in Las Vegas. A dumpster-hauling truck (Vehicle 2) was stopped in the adjacent through-lane (lane #3). Shortly after the light turned green and the Zoox vehicle began its left turn, the Vehicle 2 operator abruptly steered left, accelerated, and cut into the Zoox vehicle's path, violating its right of way.
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-30610-14263
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-14263
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 Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14263)?
An occupied Zoox autonomous vehicle traveling southeast on [XXX] stopped behind traffic in the outer left turn lane (lane #2) for a red traffic signal at [XXX] in Las Vegas. A dumpster-hauling truck (Vehicle 2) was stopped in the adjacent through-lane (lane #3). Shortly after the light turned green and the Zoox vehicle began its left turn, the Vehicle 2 operator abruptly steered left, accelerated, and cut into the Zoox vehicle's path, violating its right of way. The Zoox vehicle braked hard; however, Vehicle 2 struck the Zoox vehicle's right-side front wheel, fender, roof-mounted sensor unit, and body panel. The Zoox vehicle was towed from the scene and sustained moderate damage. No injuries were reported, and police were not called.
When did this incident occur?
The incident is recorded as occurring on March 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 Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14263)?
Zoox Robotaxi by Zoox is the recorded robot involved in this incident at Miami.
Has anyone responded to ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14263)?
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 ZOOX Zoox (NHTSA SGO 30610-14263)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.