Zoox recalls its whole fleet's software after a robotaxi drove into a fire scene — and NHTSA sets a deadline

Zoox recalled the software on its entire 105-vehicle robotaxi fleet after an empty vehicle in Las Vegas failed to detect heavy smoke on June 20 and drove toward an active fire scene that hadn't yet been coned off. The vehicle braked hard and stopped; a teleoperator backed it out. No one was hurt, and Zoox says the event is the only one of its kind in its history — the update adds explicit detection of and response to heavy smoke. The regulator's framing is the sharper edge: NHTSA called the failure a "functional insufficiency," said driverless AVs now show a clear pattern of interfering with law enforcement and first responders, and demanded operators bring remedies to the agency before the end of the month.

Why it matters

The first-responder problem has graduated from anecdotes to a regulatory program with a deadline. The same week brought Texas operators reporting 21 new crashes to federal regulators and San Francisco's mayor seeking robotaxi reforms after Waymo stalls gridlocked streets — the pattern federal scrutiny of Tesla's FSD foreshadowed is now sector-wide. For Zoox, mid-expansion push, a voluntary same-day software fix is the cheap version of compliance; the month-end NHTSA bar is the one that could actually slow deployment schedules across every operator, including Waymo's four-city expansion.

What to watch

What operators file with NHTSA by the deadline and whether it hardens into a rule; any follow-on incidents while remedies roll out; whether emergency-scene performance becomes a certification gate in Texas and California.