Reported What our labels mean

How we know: Zoox's Part 573 safety recall report (NHTSA recall 26E044) and NHTSA's July 16, 2026 acknowledgment letter; CNBC's July 17, 2026 report; FOX5 Las Vegas's Jan. 1, 2026 report.

Facts as known at: July 17, 2026 (NHTSA recall filing 26E044; CNBC)

TransportationCase study

Zoox recalls software on 105 robotaxis after one drove into a smoke-filled fire scene

The unoccupied robotaxi braked hard and stopped, then was reversed under remote guidance. Months earlier, a Zoox stalled in a busy Strip intersection.

Previously

In Part 1, Zoox let any adult with its app ride its steering-wheel-free robotaxis in Las Vegas, for free, under a federal exemption that allowed demonstrations only.

Zoox has recalled software on 105 robotaxis, all the vehicles its recall filing covers. Here's what changed since Part 1 (September 2025), what it cost, and what went wrong.

Cost and outcome (as of July 17, 2026)

  • Vehicles covered: 105, with an estimated 100% having the defect. (NHTSA filing)
  • Fix: updated software released on July 15, 2026 to all affected vehicles on public roads. (NHTSA filing)
  • Injuries: none identified, Zoox said. (NHTSA filing)
  • Cost of the recall: not disclosed.

What happened

On June 20, 2026, an unoccupied Zoox robotaxi met heavy smoke hiding an active fire scene that had not been coned off, according to Zoox's filing. The vehicle "entered the scene, then braked hard while attempting to steer away before coming to a stop." Under a remote "teleguidance tactician's" guidance, it reversed. First responders then placed cones blocking two of the three through-lanes. CNBC reported that the incident was in Las Vegas.

The filing says the software "may not detect and respond to heavy smoke, particularly in active emergency scenes." The risk: reduced visibility near an emergency scene "can increase the risk of a crash, or impede first responders." The recalled software was installed on Zoox robotaxis on public roads from April 23, 2026; the filing's production dates refer to that software, not to when vehicles were built.

What Zoox did

Zoox told NHTSA about the event on June 25. It investigated from June 22 to July 8 and concluded that "this is the only event of this kind that Zoox has experienced." Its safety committee decided on July 7 to file a recall, which NHTSA records as reported on July 8. Zoox first added operating measures to avoid active fire scenes, then pushed the software update on July 15. Because Zoox owns every affected vehicle and has never sold one, the filing says, there are no owners or dealers to notify.

At the time, CNBC reported, Zoox offered free rides in parts of Las Vegas and San Francisco, let select users hail robotaxis in small zones in Miami and Austin, and was testing in six other U.S. cities.

The recall followed a letter from NHTSA Administrator Jonathan Morrison, sent the week before, CNBC reported. Morrison said the agency had "identified a clear pattern of driverless AVs interfering with law enforcement and other first responders." He cited robotaxis driving into active emergency scenes and failing to respond to flashing lights, flares, smoke, fire and cones. He asked developers "to immediately focus their resources on fixing this issue" and to present solutions by the end of the month. The letter named no companies. The month before, CNBC noted, Waymo had recalled about 3,900 robotaxis after some drove into closed freeway construction zones.

The stall on the Strip

On Jan. 1, 2026, FOX5 Las Vegas reported a video of a Zoox robotaxi stopped in the intersection of Las Vegas Boulevard and Harmon. It moved forward and backward slightly but did not finish crossing as traffic moved again, then later resumed. The poster believed people were inside. "Safety is foundational at Zoox. We are aware of this incident and are looking into it," Zoox said.

What went wrong

  • A gap in perception. The software didn't reliably recognize heavy smoke at an emergency scene.
  • Recalls are adding up. Zoox recalled software on 332 vehicles in December 2025 over lane crossings near intersections, TechCrunch reported.
  • What we don't know yet: why the robotaxi stalled at Harmon, and how Zoox tested the smoke fix.

Our follow-up question for Zoox

What caused the January stall at Las Vegas Boulevard and Harmon, and how did Zoox test that the July 15 update detects heavy smoke?

Later developments (added Oct. 2026)

  • NHTSA granted Zoox a commercial exemption on July 31, 2026 (Federal Register), and paid rides began in Las Vegas on Aug. 10, 2026 (CNBC; Part 3).
  • On Sept. 23, 2026, TechCrunch reported that Zoox grounded its Atlanta test fleet after workers reported symptoms of possible toxic gas exposure. TechCrunch said the purpose-built robotaxis were not affected. (TechCrunch)

Sources

  1. Zoox, Inc., Part 573 Safety Recall Report, NHTSA recall 26E044. static.nhtsa.gov
  2. NHTSA, recall acknowledgment letter to Zoox, July 16, 2026. static.nhtsa.gov
  3. Annie Palmer, CNBC, “Amazon's Zoox issues software recall after robotaxi drove into heavy smoke,” July 17, 2026. cnbc.com
  4. FOX5 Las Vegas, “Zoox self-driving taxi stalls in middle of busy Las Vegas intersection,” Jan. 1, 2026. fox5vegas.com
  5. Kirsten Korosec, TechCrunch, “Zoox issues software recall over lane crossings,” Dec. 23, 2025. techcrunch.com
  6. Sean O'Kane, TechCrunch, “Exclusive: Zoox grounds Atlanta test fleet after workers report toxic gas exposure symptoms,” Sept. 23, 2026. techcrunch.com
  7. NHTSA, “Zoox—Grant of Temporary Exemption From Portions of Various Requirements of the Federal Motor Vehicle Safety Standards for an Automated Driving System,” Federal Register, FR Doc. 2026-15485, July 31, 2026. federalregister.gov
  8. Annie Palmer, CNBC, “Amazon's Zoox to launch paid robotaxi service in Las Vegas on Aug. 10,” Aug. 5, 2026. cnbc.com

Disclosure: [not in copy] Editor placeholder

© 2026 Real World Wire. Written October 25, 2026.