ADS Software May Improperly Respond After a Crash

[RECALL]

Nov 7, 2023 · Cruise · Cruise AV (Chevrolet Bolt) · Miami

Failure Mode

RECALL

Event Date

Nov 7, 2023

Primary Entity

Cruise

Robotic Platform

Cruise AV (Chevrolet Bolt)

Jurisdiction / Location

Miami

Audit Standard

Physical State Verified

Incident Abstract & Audit Findings

Cruise LLC (Cruise) is recalling a subsystem within the Automated Driving Systems (ADS). The Collision Detection Subsystem may improperly cause the vehicle to attempt to move to the side of the road after a crash.

System & Fleet Architecture

Operating Manufacturer

Hardware Platform

Cruise AV (Chevrolet Bolt)

Operational Sectors

Physical AI / Robotics

Primary Sources & Evidentiary Filings

  • https://www.nhtsa.gov/recalls?nhtsaId=23E086000

    https://www.nhtsa.gov/recalls?nhtsaId=23E086000

Related Incidents & Failure Precedents

6 records on file

Incident Context & FAQ

What happened in ADS Software May Improperly Respond After a Crash?

Cruise LLC (Cruise) is recalling a subsystem within the Automated Driving Systems (ADS). The Collision Detection Subsystem may improperly cause the vehicle to attempt to move to the side of the road after a crash. [NHTSA campaign 23E086000] source: https://www.nhtsa.gov/recalls?nhtsaId=23E086000

When did this incident occur?

The incident is recorded as occurring on November 7, 2023 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

What robot was involved in ADS Software May Improperly Respond After a Crash?

Cruise AV (Chevrolet Bolt) by Cruise is the recorded robot involved in this incident at Miami.

Has anyone responded to ADS Software May Improperly Respond After a Crash?

No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.

What is the current status of ADS Software May Improperly Respond After a Crash?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.