Safety failure
Realized harm
An unoccupied Zoox robotaxi stopped abruptly in the Decatur/Russell intersection in Las Vegas to yield to an emergency vehicle and was rear-ended by a Ford 4Runner
AIR-2026-0222 AIR record · 2026-08-zoox-las-vegas-decatur-russell-rear-end
A real party was affected. This incident caused actual consequences, not a demonstrated capability.
From the supporting source
A driverless Zoox vehicle was struck from behind by a Ford 4Runner at the intersection of Decatur Boulevard and Russell Road around 11 a.m. on August 25, with no riders aboard the robotaxi at the time of the crash, according to Zoox.hoodline.com
The record
Disclosed
2026-09-07
Occurred
2026-08-25
Vendor
Zoox (Amazon)
Product
Zoox robotaxi
Risk domain
Agent behaviour › Unsafe actuation
System type
Classical autonomy (no generative model)
Who acted
Agent acted (contested) — the robotaxi's abrupt stop set up the collision; the striking driver also failed to stop
Attack surface
Autonomous operations
Autonomy level
Fully autonomous
Initial vector
None autonomous action
Impact type
Property damage, Traffic collision
Confidence
Medium
Submitted by
EAI Internal
Crosswalk
- OWASP Agentic Top 10 (2026)
- ASI01 – Agent Goal Hijack
- MITRE ATLAS
- AML.T0048 – External Harms
- NIST AI RMF
- MEASURE 2.6; MANAGE 1.3
- EU AI Act
- Annex III §1(c)
- ISO/IEC
- TR 24028; 24029-1; 23894
- AIUC-1
- C. Safety
- Scope
- agent misuse
- Mitigation
- Require confirmation for destructive actions; Implement dry-run modes; Use layered safety controls.
- Taxonomy
- Enkrypt AI agent risk taxonomy · Black-Box Red Teaming of Agentic AI: A Taxonomy-Driven Framework for Automated Risk Discovery
Blast radius
one robotaxi and one human-driven Ford 4Runner in a Las Vegas intersection; no riders aboard; no injuries reported
Capability abused
Defense & remediation
Recorded defense
emergency-vehicle yielding behaviour (mandated by NHTSA's July 2026 first-responder directive)
Guardrail kinds
Physical safety system
Guardrail outcome
Silent
Fix shipped
none; Zoox attributes fault to the following driver; collision under investigation
Taxonomy & references
Curator notes
Boundary call, included deliberately: on Zoox's account the robot did what the regulator ordered (stopped for an oncoming emergency vehicle) and the human driver behind it was at fault, so defense_bypassed is false. It is retained because the recurring failure shape is the abrupt stop in mixed traffic that human followers do not anticipate - Zoox's March 2025 recall of 258 vehicles was for unexpected hard braking after two rear-end motorcycle collisions, and a witness (Kourtney Wagner, via KLAS 8 News Now) said drivers will need to adjust to robotaxi driving habits. The collision came to rest in the middle of the intersection. Property damage is the realized impact; no injuries reported. Context: the crash occurred 15 days after Zoox began paid service (10 Aug) under NHTSA's 30 Jul 2026 exemption (up to 2,500 steering-wheel-free vehicles), and days before airport service began (3 Sep). Hoodline cites Facebook-shared federal filings of at least 52 reportable Zoox crashes in Nevada - unverified here. Las Vegas Review-Journal coverage not cited. Secondary press only, hence medium.
Supporting sources
Cite as
Enkrypt AI. "An unoccupied Zoox robotaxi stopped abruptly in the Decatur/Russell intersection in Las Vegas to yield to an emergency vehicle and was rear-ended by a Ford 4Runner". AIR, AIR-2026-0222. https://agentincident.vercel.app/i/AIR-2026-0222/ (accessed 2026-10-19).