{"id":3491074,"date":"2026-07-17T14:12:02","date_gmt":"2026-07-17T14:12:02","guid":{"rendered":"https:\/\/techingeek.com\/index.php\/2026\/07\/17\/zoox-announces-software-recall-following-a-robotaxis-confusion-caused-by-dense-smoke\/"},"modified":"2026-07-17T14:12:02","modified_gmt":"2026-07-17T14:12:02","slug":"zoox-announces-software-recall-following-a-robotaxis-confusion-caused-by-dense-smoke","status":"publish","type":"post","link":"https:\/\/techingeek.com\/index.php\/2026\/07\/17\/zoox-announces-software-recall-following-a-robotaxis-confusion-caused-by-dense-smoke\/","title":{"rendered":"Zoox announces software recall following a robotaxi’s confusion caused by dense smoke"},"content":{"rendered":"
<\/div>\n
\n

Zoox has initiated a software recall following a scenario in June where one of its robotaxis had difficulty navigating an emergency fire scene filled with smoke.<\/p>\n

The Amazon-owned entity announced on Friday that it has dispatched a software update to its fleet of 105 vehicles aimed at correcting the issue. Zoox informed TechCrunch via a statement that the update \u201cimproves the current ability to identify active [emergency] situations by incorporating the capability to detect and respond to significant smoke in certain conditions.\u201d<\/p>\n

At the time of the incident in June, there were no occupants in the vehicle, and Zoox reported to the National Highway Traffic Safety Administration (NHTSA) that it is unaware of any injuries linked to the issue. The NHTSA\u2019s report does not specify the location of the June occurrence, and Zoox chose not to disclose it.<\/p>\n

The recall from Zoox comes just days after NHTSA administrator Jonathan Morrison cautioned self-driving vehicle firms against obstructing emergency responders in a letter.<\/p>\n

\u201cTo be clear: the failure to recognize and effectively respond to such scenarios signifies a functional shortcoming,\u201d he stated. \u201cEmergency situations are not infrequent or exceptional \u2018edge cases.\u2019 Therefore, NHTSA is currently issuing a call to action for AV developers and operators to urgently allocate their efforts towards rectifying this issue.\u201d<\/p>\n

TechCrunch previously highlighted how Waymo has faced ongoing conflicts with first responders as it ventures into new locations. As of March this year, the company had recorded at least six instances where first responders needed to physically relocate robotaxis from emergency sites.<\/p>\n

According to the report by NHTSA regarding the recall, on June 20, a Zoox robotaxi \u201cencountered dense smoke that obscured an active emergency fire scene which was not marked off with cones.\u201d The Zoox vehicle \u201cbraked abruptly while attempting to avoid the situation before ultimately stopping.\u201d A Zoox teleoperator was able to maneuver the vehicle away from the scene, enabling first responders to set up traffic cones.<\/p>\n

Zoox informed NHTSA that it performed an investigation to determine the underlying cause and recognize any similar occurrences. The company stated \u201cthis is the sole occurrence of this nature that Zoox has faced,\u201d and that during late June and early July, it engaged in numerous discussions with the safety authority about the \u201cgravity, recurrence, and fundamental causes.\u201d Zoox made the decision to recall on July 7, a day prior to Morrison\u2019s correspondence.<\/p>\n

This is not the inaugural recall for Zoox. The business voluntarily recalled vehicle software in March 2025 to rectify a hard-braking concern that NHTSA had been examining since 2024. It executed two additional recalls in May 2025 following a collision with a passenger vehicle and an incident involving a Zoox vehicle that was hit by an e-scooter rider.<\/p>\n

Zoox has been progressively broadening its testing to additional cities and is providing complimentary rides in Las Vegas and San Francisco, in preparation for a forthcoming commercial rollout. This launch is contingent on the NHTSA granting the company an exemption from certain Federal Motor Vehicle Safety Standards, due to the fact that Zoox\u2019s robotaxis do not feature a steering wheel or pedals. The NHTSA has also recently suggested eliminating the brake-pedal requirement for vehicles designed for full autonomy.<\/p>\n

This piece has been revised with a statement from Zoox.<\/em><\/p>\n<\/div>\n

Purchasing through links in our articles may yield a small commission for us. This does not influence our editorial autonomy.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/div>\n
\n

Zoox has initiated a software recall following a scenario in June where one of its robotaxis had difficulty navigating an emergency fire scene filled with smoke.<\/p>\n

The Amazon-owned entity announced on Friday that it has dispatched a software update to its fleet of 105 vehicles aimed at correcting the issue. Zoox informed TechCrunch via a statement that the update \u201cimproves the current ability to identify active [emergency] situations by incorporating the capability to detect and respond to significant smoke in certain conditions.\u201d<\/p>\n

At the time of the incident in June, there were no occupants in the vehicle, and Zoox reported to the National Highway Traffic Safety Administration (NHTSA) that it is unaware of any injuries linked to the issue. The NHTSA\u2019s report does not specify the location of the June occurrence, and Zoox chose not to disclose it.<\/p>\n

The recall from Zoox comes just days after NHTSA administrator Jonathan Morrison cautioned self-driving vehicle firms against obstructing emergency responders in a letter.<\/p>\n

\u201cTo be clear: the failure to recognize and effectively respond to such scenarios signifies a functional shortcoming,\u201d he stated. \u201cEmergency situations are not infrequent or exceptional \u2018edge cases.\u2019 Therefore, NHTSA is currently issuing a call to action for AV developers and operators to urgently allocate their efforts towards rectifying this issue.\u201d<\/p>\n

TechCrunch previously highlighted how Waymo has faced ongoing conflicts with first responders as it ventures into new locations. As of March this year, the company had recorded at least six instances where first responders needed to physically relocate robotaxis from emergency sites.<\/p>\n

According to the report by NHTSA regarding the recall, on June 20, a Zoox robotaxi \u201cencountered dense smoke that obscured an active emergency fire scene which was not marked off with cones.\u201d The Zoox vehicle \u201cbraked abruptly while attempting to avoid the situation before ultimately stopping.\u201d A Zoox teleoperator was able to maneuver the vehicle away from the scene, enabling first responders to set up traffic cones.<\/p>\n

Zoox informed NHTSA that it performed an investigation to determine the underlying cause and recognize any similar occurrences. The company stated \u201cthis is the sole occurrence of this nature that Zoox has faced,\u201d and that during late June and early July, it engaged in numerous discussions with the safety authority about the \u201cgravity, recurrence, and fundamental causes.\u201d Zoox made the decision to recall on July 7, a day prior to Morrison\u2019s correspondence.<\/p>\n

This is not the inaugural recall for Zoox. The business voluntarily recalled vehicle software in March 2025 to rectify a hard-braking concern that NHTSA had been examining since 2024. It executed two additional recalls in May 2025 following a collision with a passenger vehicle and an incident involving a Zoox vehicle that was hit by an e-scooter rider.<\/p>\n

Zoox has been progressively broadening its testing to additional cities and is providing complimentary rides in Las Vegas and San Francisco, in preparation for a forthcoming commercial rollout. This launch is contingent on the NHTSA granting the company an exemption from certain Federal Motor Vehicle Safety Standards, due to the fact that Zoox\u2019s robotaxis do not feature a steering wheel or pedals. The NHTSA has also recently suggested eliminating the brake-pedal requirement for vehicles designed for full autonomy.<\/p>\n

This piece has been revised with a statement from Zoox.<\/em><\/p>\n<\/div>\n

Purchasing through links in our articles may yield a small commission for us. This does not influence our editorial autonomy.<\/em><\/p>\n","protected":false},"author":2,"featured_media":3491075,"comment_status":"open","ping_status":"closed","sticky":false,"template":"Default","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3491074","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/posts\/3491074"}],"collection":[{"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/comments?post=3491074"}],"version-history":[{"count":0,"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/posts\/3491074\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/media\/3491075"}],"wp:attachment":[{"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/media?parent=3491074"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/categories?post=3491074"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/techingeek.com\/index.php\/wp-json\/wp\/v2\/tags?post=3491074"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}