Zoox robotaxi enters a smoke-obscured fire scene and reverses under remote guidance; software recall, June to July 2026
The typed evidence object. This is the working store; the case page is the reader's form.
| Layer / facet | Value | Type | Sources | Conf. |
|---|---|---|---|---|
| Mandate: principal | Zoox, operating a driverless service | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | high |
| Mandate: objective | Navigate public roads without an occupant | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | high |
| Actor | A Zoox robotaxi with no one on board | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | high |
| Inputs | On 20 June 2026 the vehicle encountered heavy smoke obscuring an active emergency fire scene that had not been cordoned off with cones | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | high |
| Decision | Not disclosed; the filing describes behavior, not the planner's state | assertion | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | low |
| Envelope: constraints | An active fire scene, obscured by heavy smoke and not yet cordoned off with cones; the filing names the gap as the software's detection of and response to heavy smoke, leaves its cause field blank, and does not say whether the missing cones played a part | interpretation | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | medium |
| Action | The vehicle entered the scene, then braked hard while attempting to steer away before coming to a stop | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | high |
| Outcome | State: averted. Zoox identified no injuries. First responders placed cones after the vehicle reversed. As of July 2026. | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | high |
| Evidence: event | Zoox's own account in the recall report; Zoox told NHTSA this was the only event of its kind | assertion | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | medium |
| Recovery: automated fallback | After entering the scene, the vehicle braked hard while attempting to steer away and came to a stop; the filing does not say how far into the scene it went | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | high |
| Recovery: technical | Under a remote teleguidance tactician's guidance, the vehicle reversed, after which first responders placed traffic cones blocking two of the three through-lanes; the filing does not say whether the remote person drove the vehicle or guided its software | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | high |
| Recovery: accountability | Zoox notified NHTSA of the event on 25 June 2026 under its Automated Vehicle Exemption Program obligation, investigated root cause between 22 June and 8 July, and discussed severity, frequency and root causes with NHTSA; its Safety Committee decided on 7 July 2026 to file a voluntary software recall covering 105 vehicles (manufacturer's report date 8 July in NHTSA's acknowledgment letter; Part 573 report submitted 16 July). As an interim remedy Zoox bolstered its existing operational measures to avoid driving near active fire emergency scenes and released updated software to the affected vehicles on 15 July 2026 | fact | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles); NHTSA Office of Defects Investigation, Recall Management Division, recall acknowledgment letter to Zoox, Inc., 26E044: ADS [automated driving system] Software May Fail to Detect and Respond to Heavy Smoke | high |
| Inputs: world_state | NHTSA's administrator wrote to driverless developers on 8 July 2026 warning them about driving into emergency scenes and failing to respond to smoke, fire and cones | fact | NHTSA Administrator Jonathan Morrison, letter to developers of driverless automated driving systems on interactions with first responders, 8 Jul 2026 | high |
Controls
| Status | Control | Canonical |
|---|---|---|
| failed | Heavy-smoke detection and response: per the recall, the software may not detect and respond to heavy smoke in certain situations, particularly in active emergency scenes; the scene had not been cordoned off with cones | C-I3 Degraded-input detection |
| succeeded | Safe stop | C-R2 Automated fail-safe |
| succeeded | Remote teleguidance: the vehicle reversed under a teleguidance tactician's guidance; no timing is disclosed, and the filing does not say whether the person took over driving | C-R3 Human takeover with a time window |
| succeeded | Voluntary recall process | C-R4 Organizational recovery process |
Inference
inference Two responses appear in the recall filing, one after the other: after entering the smoke-obscured scene, the vehicle braked hard while trying to steer away and stopped; it then reversed under a remote teleguidance tactician's guidance, after which first responders placed cones. The filing ties the event to software that in certain situations may not detect and respond to heavy smoke, and the update enhances that detection and response. The record gives no root cause for this event (the filing's cause field is blank, and the National Highway Traffic Safety Administration's acknowledgment describes the defect only in general terms, as software that 'may fail to detect heavy smoke, allowing the vehicle to enter an area of low visibility'), and does not show whether the remote person drove the vehicle or guided its software, or whether the update changes what the vehicle does once inside such a scene.
Sources
| ID | Record | Type | Link |
|---|---|---|---|
| NHTSA-LTR | NHTSA Administrator Jonathan Morrison, letter to developers of driverless automated driving systems on interactions with first responders, 8 Jul 2026 | regulator primary record | nhtsa.gov ↗ checked 2026-10-13 |
| TC-ZOOX | Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles) | company primary record | static.nhtsa.gov ↗ checked 2026-10-20 |
| NHTSA-RCAK | NHTSA Office of Defects Investigation, Recall Management Division, recall acknowledgment letter to Zoox, Inc., 26E044: ADS [automated driving system] Software May Fail to Detect and Respond to Heavy Smoke | regulator primary record | static.nhtsa.gov ↗ checked 2026-10-20 |