Cases › operational mistake › LR-2026-0282
Zoox robotaxi rear-ended by SUV after stopping for ambulance
Preliminary Why: Publisher not yet named · subject to change
Severity minor: A single robotaxi was shunted and neither vehicle could drive away, with no third party or wider scope stated.
Earliest source we hold 2026-10-30 · Captured by AI Risk Wire 2026-10-31 01:31 UTC
A Zoox robotaxi in Las Vegas driverless service slowed and stopped at traffic lights, apparently to yield to an ambulance with flashing lights.
Risks this incident falls under
| Risk | Role | NIST AI 600-1 | Incidents | Last 6 quarters |
|---|---|---|---|---|
| Agent takes destructive or unapproved actions | Primary | Human-AI Configuration | 20 |
Sorted by rule from the case's fields; not yet read from the sources.
Control failure chain
L1 · ModelProvider not namedModel provider
Sources not yet read for controls.
Model version not linked to a model card.
L2 · HarnessHarness not namedAgent framework vendor
Sources not yet read for controls.
3 more for this risk at this layer
L3 · ApplicationDeployer not namedDeployer
Sources not yet read for controls.
6 more for this risk at this layer
L4 · Infrastructure / targetOrganisation hitOrganisation hit
Sources not yet read for controls.
1 more for this risk at this layer
HeldFailedGot aroundMissingNot mentionedNot read yetAttacker's ownOrder: model · harness · application · target
The same controls in other incidents of this risk
| Control | Layer | Here | Held elsewhere | Did not hold elsewhere |
|---|---|---|---|---|
| Tool allow-list | L2 Harness | Not read yet | – | – |
| Stop control | L2 Harness | Not read yet | – | – |
| Fail-closed defaults | L2 Harness | Not read yet | – | – |
| Least-privilege access for the agent | L3 Application | Not read yet | – | – |
| Production kept apart from test | L3 Application | Not read yet | – | 1 |
| Human approval for high-impact actions | L3 Application | Not read yet | – | 3 |
| Change review and separation of duties | L3 Application | Not read yet | – | – |
| Activity logs | L3 Application | Not read yet | – | – |
| Adversarial testing before deployment | L3 Application | Not read yet | – | – |
| Backups and recovery | L4 Infrastructure / target | Not read yet | – | – |
Risk grouping: Not yet classified
No source we hold states: who caused it, intended or not, before or after release, the ai's part.
The story
No source states: when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.
Show every field, with its source and grade
The AI system
What happened
Impact
Context
LR-2026-0282 · version 2 · published 2026-10-31 after automatic checks; not yet checked field by field by a person · changes to this case · JSON