Zoox robotaxi enters a smoke-obscured fire scene and reverses under remote guidance; software recall, June to July 2026

Changes to what this case says, with the reason. Every earlier version is kept.

• 2026-10-21: Inference: signed by. The interpretation's wording changed after the editor signed it (second, independent check of 21 october 2026); the signature is cleared so the editor signs the corrected wording.
  Show the change

  Before: Saurabh Bhatnagar

  After:
• 2026-10-21: Inference: source ids. Found in the editor's second, independent check of the interpretations, 21 october 2026: the interpretation now quotes the regulator's acknowledgment letter.
  Show the change

  Before: ["TC-ZOOX"]

  After: ["TC-ZOOX", "NHTSA-RCAK"]
• 2026-10-21: Inference: value. Found in the editor's second, independent check of the interpretations, 21 october 2026: the regulator's acknowledgment letter (nhtsa-rcak) does describe, in general terms, why such a vehicle could enter the scene; what the record lacks is a root cause for this event.
  Show the change

  Before: 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 does not show why the vehicle entered the scene (the cause field is blank), 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

  After: 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
• 2026-10-20: Sources: tc-zoox. Found in the editor's source re-check of 19-20 october 2026: the report is zoox's own submission ("manufacturer name: zoox, inc.", "submitted pursuant to 49 cfr § 573") published on nhtsa's site, so its type is company, not regulator (tier public_regulatory kept); the subtitle used the subject line of nhtsa's acknowledgment letter and now uses the report's own defect description, "the software may not detect and respond to heavy smoke".
  Show the change

  Before: {"title": "Zoox, Inc., Part 573 Safety Recall Report 26E044: ADS software May fail to detect and respond to heavy smoke (105 vehicles)", "type": "regulator", "checked": "2026-10-13"}

  After: {"title": "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)", "type": "company", "checked": "2026-10-20"}
• 2026-10-20: Inference: value. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) shows the vehicle itself braked and stopped before any remote guidance is mentioned, and that the reversal happened "under a teleguidance tactician's guidance" without saying the person drove; the software update "enhances existing capability of detecting and responding to heavy smoke" and nothing in it says the vehicle would now reverse itself out, so 'the control that worked was the remote human, not the driving software' and 'the recall brought the software up to what the human did' went beyond the record. the interpretation was not signed (signed_by null); the editor must sign the new wording.
  Show the change

  Before: The control that worked here was the remote human, not the driving software. The recall brought the software up to what the human did

  After: 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 does not show why the vehicle entered the scene (the cause field is blank), 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
• 2026-10-20: Controls: c-r3. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) says only that the vehicle reversed "under a teleguidance tactician's guidance"; no source gives the timing or says the remote person took over driving, so the mapping to human takeover with a time window is held at medium confidence pending the editor's classification.
  Show the change

  Before: {"note": "Teleoperation", "confidence": "high"}

  After: {"note": "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", "confidence": "medium"}
• 2026-10-20: Controls: c-i3. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) names the gap as detecting and responding to heavy smoke and says the software update "enhances existing capability"; it does not say scene recognition depends on cones or that smoke handling was absent.
  Show the change

  Before: {"note": "Scene recognition without cones; Smoke-specific perception handling (per the recall) (absent)", "confidence": "high"}

  After: {"note": "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", "confidence": "high"}
• 2026-10-20: Fields: recovery accountability: source ids. Found in the editor's source re-check of 19-20 october 2026: nhtsa's acknowledgment letter for recall 26e044 (nhtsa-rcak) is the record that carries the 8 july manufacturer's report date.
  Show the change

  Before: ["TC-ZOOX"]

  After: ["TC-ZOOX", "NHTSA-RCAK"]
• 2026-10-20: Fields: recovery accountability. Found in the editor's source re-check of 19-20 october 2026: the 8 july date is not in the cited recall report (tc-zoox), which shows "submission date: jul 16, 2026"; it is the "mfr's report date: july 08, 2026" in nhtsa's acknowledgment letter (nhtsa-rcak, now cited). tc-zoox also records the 25 june notification under the automated vehicle exemption program, the interim measures and the 15 july software release, which were missing.
  Show the change

  Before: Zoox investigated root cause and discussed severity, frequency and root causes with NHTSA; its Safety Committee decided on 7 July 2026 to file a voluntary software recall (defect report dated 8 July, covering 105 vehicles)

  After: 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
• 2026-10-20: Fields: recovery technical. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) says "the zoox vehicle, under a teleguidance tactician's guidance, reversed, after which the first responders placed traffic cones at the scene blocking two of the three through-lanes"; it does not say a teleoperator drove the vehicle.
  Show the change

  Before: A Zoox teleoperator reversed the vehicle away, letting first responders place traffic cones

  After: 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
• 2026-10-20: Fields: recovery automated fallback. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) says the vehicle "entered the scene" before braking and stopping; it does not describe how far it went, so 'did not drive through the scene' went beyond the record.
  Show the change

  Before: Hard braking and a stop: the vehicle did not drive through the scene

  After: 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
• 2026-10-20: Fields: action. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) says "the zoox vehicle entered the scene, then braked hard while attempting to steer away before coming to a stop"; the entry into the scene was missing from the action.
  Show the change

  Before: The vehicle braked hard while attempting to steer away, then stopped

  After: The vehicle entered the scene, then braked hard while attempting to steer away before coming to a stop
• 2026-10-20: Fields: envelope constraints. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) describes the defect as "the software may not detect and respond to heavy smoke, particularly in active emergency scenes" and leaves "description of the cause" blank; it does not say the vehicle's scene recognition keys on cones or that the scene lay outside its operating assumptions, so those readings were removed.
  Show the change

  Before: An uncordoned emergency scene lies outside normal operating assumptions; no cones meant the vehicle's scene-recognition had nothing to key on

  After: 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
• 2026-10-20: Outcome: affected parties. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) records that the vehicle entered the scene and that "no injuries were identified"; its "impede first responders" is the general safety-risk statement, and no source read reports an actual delay to responders in this event.
  Show the change

  Before: ["first responders (delay)"]

  After: ["first responders (the vehicle entered their scene; no injuries identified, no delay reported)"]
• 2026-10-20: Applicable rules. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) says "on june 25, 2026, zoox notified nhtsa of the event pursuant to its obligation under the automated vehicle exemption program"; neither cited source ties this event to the standing general order, and no crash was reported.
  Show the change

  Before: ["NHTSA Standing General Order (crash and incident reporting)", "Part 573 safety recall process"]

  After: ["NHTSA Automated Vehicle Exemption Program reporting obligation (Zoox notified NHTSA of the event on 25 June 2026)", "Part 573 safety recall process"]
• 2026-10-20: Context: actors: text. Found in the editor's source re-check of 19-20 october 2026: the recall report (tc-zoox) names the remote person as a "teleguidance tactician" who guided the vehicle, not a teleoperator driving it.
  Show the change

  Before: 1 (plus remote teleoperator)

  After: 1 (plus a remote teleguidance tactician)
• 2026-10-20: Title. Found in the editor's source re-check of 19-20 october 2026: zoox's part 573 recall report (tc-zoox) says the vehicle, "under a teleguidance tactician's guidance, reversed"; it does not say a remote human drove the vehicle, so 'teleoperator reverses it' overstated the record.
  Show the change

  Before: Zoox robotaxi enters a smoke-obscured fire scene; teleoperator reverses it; software recall, June to July 2026

  After: Zoox robotaxi enters a smoke-obscured fire scene and reverses under remote guidance; software recall, June to July 2026
• 2026-10-13: Fields and sources. Claims aligned to what each linked record says, found on review.
  Show the change

  Before: recall 'filed on 7 July 2026'; 'first responders delayed in placing cones'; NHTSA letter 'a week earlier'; both sources cited via TechCrunch

  After: recall decided 7 July, defect report dated 8 July, from the recall report linked directly; cones wording as the report states it; NHTSA letter linked and dated
• 2026-10-13: Context: jurisdiction. Jurisdiction text was split at a comma inside parentheses.
  Show the change

  Before: United States (federal NHTSA | location not disclosed)

  After: United States (federal NHTSA, location not disclosed)
• 2026-10-13: Controls: c-i3. A control has one state per case; entries in two states merged into the state the record supports.
  Show the change

  Before: failed: Scene recognition without cones; absent: Smoke-specific perception handling (per the recall)

  After: failed: Scene recognition without cones; Smoke-specific perception handling (per the recall) (absent)