DEPLOYDatabase

Incident · Recall

Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las Vegas

On June 20, 2026, an unoccupied Zoox robotaxi entered an active emergency fire scene obscured by heavy smoke in Las Vegas that had not yet been cordoned off with cones. The vehicle braked hard while attempting to steer away before stopping. Zoox notified NHTSA of a voluntary software recall on July 8, 2026, affecting 105 robotaxis.

A software update enhancing heavy-smoke detection was released to all affected vehicles on July 15. No injuries were identified. The recall follows NHTSA Administrator Morrison's July 8 letter calling AV interference with first responders a functional insufficiency.

Occurred 2026-06-20 · Zoox · Investigated by NHTSA

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las Vegas

Machine-readable surfaces

Sources (2)

  1. CNBC · https://www.cnbc.com/2026/07/17/amazon-zoox-recalls-robotaxi-smoke.html · 2026-07-17
  2. FOX5 Las Vegas · https://www.fox5vegas.com/2026/07/20/zoox-issues-software-recall-after-robotaxi-drives-into-heavy-smoke-las-vegas/ · 2026-07-20

Status history

  • Active · 2026-07-25 · agent:recon

Common questions

What happened in Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las Vegas?
On June 20, 2026, an unoccupied Zoox robotaxi entered an active emergency fire scene obscured by heavy smoke in Las Vegas that had not yet been cordoned off with cones. The vehicle braked hard while attempting to steer away before stopping. Zoox notified NHTSA of a voluntary software recall on July 8, 2026, affecting 105 robotaxis. A software update enhancing heavy-smoke detection was released to all affected vehicles on July 15. No injuries were identified. The recall follows NHTSA Administrator Morrison's July 8 letter calling AV interference with first responders a functional insufficiency.
When did this incident occur?
The incident is recorded as occurring on June 20, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las Vegas?
The incident is recorded as involving Zoox on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las Vegas?
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 Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las Vegas?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-08-09

Verification posture

Verified

Medium confidence

Review state

Stable

Last reviewed 2026-08-09

Sources by quality tier

1
secondary-established-publication
Established publication
1
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las Vegas.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID 1ab43db6-30a3-451d-82ee-975fbbd61b07