Incident: Chevy Volt Battery Packs Safety Investigation After Collision Tests

Published Date: 2011-11-28

Postmortem Analysis
Timeline 1. The software failure incident involving the Chevy Volt's battery packs occurred in May, as mentioned in Article 9247. 2. Article 9247 was published on 2011-11-28. 3. Estimation: The incident occurred in May 2011.
System 1. Chevy Volt battery packs [9247]
Responsible Organization unknown
Impacted Organization 1. Chevy Volt owners were impacted by the software failure incident as the NHTSA found that damage to the Volt's battery in crash tests resulted in fires [9247].
Software Causes 1. Unknown
Non-software Causes 1. Damage to the Volt's battery resulting from a side collision and a rotation of 180 degrees during crash tests conducted by the NHTSA [Article 9247]. 2. Rupture of the line carrying coolant to the batteries during the crash tests [Article 9247].
Impacts 1. The software failure incident involving the Chevy Volt's battery packs resulted in fires after specific collision tests conducted by the NHTSA [Article 9247]. 2. The incident raised concerns about the safety of the Chevy Volt's batteries following crashes, leading to a formal safety defect investigation by the NHTSA [Article 9247]. 3. General Motors responded by creating an engineering team to address safety concerns and offering a vehicle loan program to Volt owners worried about safety until the issue is resolved [Article 9247].
Preventions 1. Implementing robust software testing procedures that include thorough crash and safety testing [9247]. 2. Conducting more extensive real-world crash simulations during the software development phase to identify potential vulnerabilities [9247]. 3. Regularly updating and improving the software to address any identified safety concerns or vulnerabilities [9247].
Fixes 1. Implement software updates or modifications to the battery management system to prevent potential thermal runaway or fire incidents following a crash [9247].
References 1. National Highway Traffic Safety Administration (NHTSA) [Article 9247] 2. General Motors (GM) [Article 9247]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident related to the Chevy Volt's battery packs resulting in fires after collision tests is specific to General Motors (GM) as the manufacturer of the Chevy Volt. The National Highway Traffic Safety Administration (NHTSA) opened a formal investigation into the safety of the battery packs in the Chevy Volt following a series of collision tests [9247]. GM responded by creating an engineering team to develop potential changes to address safety concerns and offering a vehicle loan program to Volt owners concerned about safety [9247]. (b) The articles do not mention any similar incidents of software failure related to battery packs resulting in fires after collision tests at other organizations or with their products and services.
Phase (Design/Operation) design, unknown (a) The software failure incident related to the design phase is evident in the article. The National Highway Traffic Safety Administration (NHTSA) opened a formal investigation into the safety of the battery packs in the Chevy Volt following a series of collision tests. The tests conducted by the NHTSA found that damage to the Volt's battery resulted in a fire after a side collision and a rotation of 180 degrees, which simulated impact with a pole or tree followed by a rollover. The article mentions that the line carrying coolant to the batteries was ruptured in each case, indicating a design flaw that led to the battery-related fire incidents [9247]. (b) The software failure incident related to the operation phase is not explicitly mentioned in the article. Therefore, it is unknown if the failure was due to contributing factors introduced by the operation or misuse of the system.
Boundary (Internal/External) within_system (a) The software failure incident related to the Chevy Volt battery packs was within the system. The failure was attributed to damage to the battery packs during crash tests, specifically the rupture of the line carrying coolant to the batteries, leading to elevated battery temperatures and an electrical fire [9247]. The incident was a result of internal factors within the Chevy Volt system, highlighting a potential flaw in the design or construction of the battery packs.
Nature (Human/Non-human) non-human_actions (a) The software failure incident in this case was not directly related to non-human actions but rather to the physical damage caused by the crash tests on the Chevy Volt's battery packs. The NHTSA found that damage to the battery packs during the collision tests resulted in a fire due to the rupture of the coolant line, leading to elevated battery temperatures and an electrical fire weeks later [9247]. (b) The software failure incident was not attributed to human actions but rather to the design vulnerability of the Chevy Volt's battery packs when subjected to specific crash scenarios. General Motors responded by creating an engineering team to address the safety concerns and offering a vehicle loan program to owners worried about safety until the issue is resolved [9247].
Dimension (Hardware/Software) hardware (a) The software failure incident in the Chevy Volt battery packs was primarily due to hardware issues. The National Highway Traffic Safety Administration (NHTSA) found that damage to the Volt's battery packs, specifically the rupture of the line carrying coolant to the batteries, resulted in fires after collision tests [9247]. (b) The software failure incident in the Chevy Volt was not directly attributed to software issues. The concerns and investigations were focused on the safety of the battery packs and the potential for fires following crashes, indicating that the root cause was related to hardware failures rather than software defects [9247].
Objective (Malicious/Non-malicious) unknown <Article 9247> does not mention any software failure incident related to the Chevy Volt battery safety investigation. Therefore, the information about the objective of the software failure incident is unknown in this context.
Intent (Poor/Accidental Decisions) unknown The software failure incident related to the Chevy Volt battery packs did not involve a software-related issue. The failure was attributed to damage to the battery packs during crash tests, leading to a fire risk due to coolant line ruptures. The incident was not caused by poor decisions or accidental decisions related to software but rather by physical damage to the battery packs during simulated crash scenarios [9247].
Capability (Incompetence/Accidental) unknown The articles do not mention any software failure incident related to development incompetence or accidental factors.
Duration unknown The software failure incident related to the Chevy Volt battery packs resulting in fires after collision tests does not directly involve a software failure. The issue primarily revolves around the battery packs and their safety in crash scenarios. Therefore, the duration of the incident is not applicable in terms of being permanent or temporary in the context of software failure.
Behaviour crash, other (a) The software failure incident in this case can be categorized as a crash. The incident involved a safety issue with the battery packs in the Chevy Volt following collision tests conducted by the National Highway Traffic Safety Administration (NHTSA). The tests resulted in damage to the Volt's battery, leading to a fire after a side collision and a rotation of 180 degrees, simulating impact with a pole or tree followed by a rollover. The battery temperatures rose following the simulated crash and rollover, and an electrical fire started more than three weeks later, indicating a failure of the system losing its state and not performing its intended functions [9247]. (f) In addition to the crash behavior, the incident can also be categorized as an "other" behavior. This is because the software failure incident involved a specific scenario where damage to the Volt's batteries during crash tests designed to replicate real-world scenarios resulted in fires. This behavior is not explicitly described in the options provided but falls under a unique circumstance related to the safety of the battery packs in the Chevy Volt [9247].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence non-human, theoretical_consequence The articles do not mention any consequences related to death, harm, basic needs, property loss, or delays caused by the software failure incident involving the Chevy Volt's battery packs [9247]. The main consequence discussed in the articles is the potential for a battery-related fire following a crash due to damage to the Volt's batteries in specific crash scenarios. General Motors responded by taking steps to address safety concerns, such as creating an engineering team to develop potential changes and offering a vehicle loan program to concerned Volt owners [9247].
Domain transportation, manufacturing The software failure incident reported in Article 9247 is related to the transportation industry. The incident involves the safety concerns regarding the battery packs in the Chevy Volt, an electric vehicle manufactured by General Motors. The National Highway Traffic Safety Administration (NHTSA) conducted tests simulating real-world crash scenarios, which led to battery damage and subsequent fires in the vehicle after collisions and rollovers [9247]. This incident falls under the transportation industry category as it directly impacts the safety and functionality of electric vehicles like the Chevy Volt, which are designed for moving people and things. The safety defect investigation and engineering efforts initiated by General Motors in response to the incident further emphasize the transportation industry's connection to this software failure incident.

Sources

Back to List