DEPLOYDatabase

Incident · Recall

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

On June 20, 2026, an unoccupied Zoox robotaxi in Las Vegas encountered heavy smoke obscuring an active emergency fire scene that was not yet cordoned off with cones. The vehicle entered the scene, braked hard while attempting to steer away, and came to a stop; a Zoox teleguidance employee then instructed it to reverse.

No injuries were identified. Zoox notified NHTSA of a voluntary software recall on July 8 covering 105 vehicles and deployed a software update on July 15 adding heavy-smoke detection. The recall follows NHTSA Administrator Jonathan Morrison's July 2026 directive to AV developers to fix first-responder interference.

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 recalls 105 robotaxis after unoccupied vehicle drove into heavy smoke at 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. News 3 Las Vegas · https://news3lv.com/news/local/zoox-software-recall-robotaxi-drives-through-heavy-smoke-las-vegas-fire-emergency-autonomous-vehicles-amazon · 2026-07-20

Status history

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

Common questions

What happened in Zoox recalls 105 robotaxis after unoccupied vehicle drove into heavy smoke at active fire scene in Las Vegas?
On June 20, 2026, an unoccupied Zoox robotaxi in Las Vegas encountered heavy smoke obscuring an active emergency fire scene that was not yet cordoned off with cones. The vehicle entered the scene, braked hard while attempting to steer away, and came to a stop; a Zoox teleguidance employee then instructed it to reverse. No injuries were identified. Zoox notified NHTSA of a voluntary software recall on July 8 covering 105 vehicles and deployed a software update on July 15 adding heavy-smoke detection. The recall follows NHTSA Administrator Jonathan Morrison's July 2026 directive to AV developers to fix first-responder interference.
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 recalls 105 robotaxis after unoccupied vehicle drove into heavy smoke at 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 recalls 105 robotaxis after unoccupied vehicle drove into heavy smoke at 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 recalls 105 robotaxis after unoccupied vehicle drove into heavy smoke at 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 recalls 105 robotaxis after unoccupied vehicle drove into heavy smoke at 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 075c8500-b460-42ff-a21f-4fdaba0bb7ba