A general warning becomes a named defect
Zoox filed U.S. recall 26E044 for 105 public-road automated-driving-system installations because its software may not detect and respond to heavy smoke, particularly near active emergency scenes. The Part 573 report estimates that all 105 potentially involved units contain the defect. That narrows NHTSA's broader July warning about driverless vehicles interfering with first responders into a smoke-specific software boundary for one operating fleet.[1,2,3]
The filing traces the recall to June 20, when an unoccupied Zoox vehicle entered a smoke-obscured fire scene that had not been cordoned off with cones. It braked hard while steering away, stopped, then reversed under a teleguidance tactician's guidance. Zoox said its review found no injuries and no other event of this kind.[1,2,3]
The remedy still needs operating evidence
The mechanism matters beyond the incident count: reduced visibility can raise crash risk or impede first responders, while the exit sequence depended on teleguidance after the vehicle stopped. Zoox said the update enhances its existing ability to detect and respond to heavy smoke. Fleet operations, road users, emergency crews, city agencies and autonomous-vehicle developers are exposed to whether that response works before a vehicle enters an active scene.[1,2,3]
The limit is one company-reported, no-injury event. The opened record publishes no independent remedy test, smoke-scenario coverage, detection range, false-response rate or post-update field performance, and it does not identify the incident location. The next measurable catalysts are Zoox's promised recall-filing update after remedy deployment, NHTSA's planned end-July meetings with vehicle developers, and any disclosed validation or recurrence data.[1,2,3]