Cases › operational mistake › LR-2026-0632
Zoox robotaxis recalled after failing to recognize heavy smoke and an active fire scene
Confirmed Why: 2 independent outlets · 2 independent reports
Status: no action reported
No source states: loss or records, agent tool, could do, deployer, industry.
Zoox, an Amazon-owned company, operates driverless robotaxis that carry free passengers in Las Vegas and San Francisco. On June 20, an unoccupied Zoox robotaxi approached an active emergency fire scene obscured by heavy smoke that was not cordoned off with cones. The vehicle entered the scene, braked hard while attempting to steer away, and came to a stop. A remote operator reversed it away from the scene, allowing first responders to place traffic cones. Zoox investigated the incident, notified the National Highway Traffic Safety Administration, and recalled software across its 105 robotaxis. The update adds the ability to detect and respond to heavy smoke in certain situations. No injuries were identified, and Zoox said this was the only event of its kind.
What happened
No source tells the story step by step yet.
What was done
No source states an action or fix.
Risks
Primary43 incidents
Also63 incidents
Rising: 5 vs 2.2 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
Harness ApplicationPhysical safety interlocks · Human approval for high-impact actions · Live behaviour monitoring · Adversarial testing before deployment
Similar incidents
Evidence
No source states: a step-by-step account, 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
Notes on gaps
The incident location comes from Zoox's report via CNBC; NHTSA's report does not state it per TechCrunch. Zoox's own date for the recall decision (July 7, per TechCrunch) and notification to NHTSA (July 8, per CNBC) are both given as stated.
LR-2026-0632 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON