Incident: Airbag Control Module Software Failure in Volkswagen Vehicles, 2015-2016

Published Date: 2019-07-31

Postmortem Analysis
Timeline 1. The software failure incident happened in late 2017 based on the information provided in the article [86997]. 2. Published on 2019-07-31. 3. The software failure incident occurred in late 2017.
System 1. Airbag control module in the 2015-2016 Tiguan and 2015-2016 CC models [86997]
Responsible Organization 1. Supplier ZF/TRW [86997]
Impacted Organization 1. Owners of the 2015-2016 Tiguan and CC vehicles manufactured by Volkswagen were impacted by the software failure incident [86997].
Software Causes 1. The software cause of the failure incident was a faulty capacitor in the airbag control module, which could cause the airbag system to act incorrectly, leading to issues such as deactivating the airbags or deploying them at an improper time [86997].
Non-software Causes 1. Faulty capacitor in the airbag control module [86997]
Impacts 1. The software failure incident in Volkswagen's airbag control module could cause the airbags to deactivate or deploy at an improper time, increasing the risk of injury to occupants [86997].
Preventions 1. Implementing more rigorous testing procedures during the development phase to detect faulty components in the airbag control module before mass production [86997]. 2. Conducting regular quality control checks on the airbag control module components to ensure they meet the required standards and specifications [86997]. 3. Enhancing the monitoring system in the vehicles to detect any anomalies or malfunctions in the airbag system in real-time, thus enabling proactive maintenance and repairs [86997].
Fixes 1. Technicians will flash the cars with a software update that is able to detect an increase in resistance within the module, which is what happens when the faulty capacitor in the module fails. If that increased resistance is found, technicians will replace the airbag control module [86997].
References 1. Field cases reported to Volkswagen [86997] 2. Supplier ZF/TRW [86997]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident related to the faulty airbag control module in Volkswagen vehicles has happened again within the same organization. Volkswagen first received information about the issue from a single field case in late 2017. Subsequently, in 2018, the automaker received a second case from the field, and a third case was reported later in 2018. After working with the supplier ZF/TRW, Volkswagen decided that the defect was significant enough to warrant a recall [86997]. (b) There is no information in the provided article indicating that a similar software failure incident related to the faulty airbag control module has happened at other organizations or with their products and services.
Phase (Design/Operation) design (a) The software failure incident in the Volkswagen airbag system recall can be attributed to the design phase. The faulty capacitor in the airbag control module, which is a component of the software system, was identified as the root cause of the issue. This faulty capacitor introduced a defect in the system, causing the airbag system to potentially malfunction by either deactivating the airbags or deploying them at an incorrect time [86997]. (b) The software failure incident is not directly linked to the operation phase or misuse of the system. The article primarily focuses on the design flaw in the airbag control module and the subsequent recall and software update process to address the issue.
Boundary (Internal/External) within_system (a) The software failure incident related to the airbag control module in Volkswagen's recall is within_system. The faulty capacitor within the airbag control module is causing the airbag system to act incorrectly, leading to potential risks of deactivation or improper deployment of airbags and seatbelt pretensioners [86997]. The remedy for this issue involves flashing the cars with a software update that can detect an increase in resistance within the module, indicating a failure of the faulty capacitor, and then replacing the airbag control module [86997].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in the Volkswagen recall was due to a faulty capacitor in the airbag control module, which is a non-human factor introduced during the manufacturing process. This faulty component caused the airbag system to potentially deactivate or deploy at an incorrect time, increasing the risk of injury [86997]. (b) Human actions were involved in the detection and response to the software failure incident. Volkswagen first received information about the issue from field cases in late 2017 and 2018. After working with the supplier ZF/TRW and identifying the defect, Volkswagen decided to issue a recall to address the software failure [86997].
Dimension (Hardware/Software) hardware, software (a) The software failure incident in the Volkswagen recall was due to a faulty capacitor in the airbag control module, which is a hardware component. The faulty capacitor caused the airbag system to act incorrectly, potentially leading to the deactivation or improper deployment of airbags and seatbelt pretensioners [86997]. (b) The remedy for the software failure incident involved flashing the cars with a software update that can detect an increase in resistance within the module, indicating a failure of the faulty capacitor. If the increased resistance is found, technicians will replace the airbag control module, showing that the software update was addressing the hardware-related issue [86997].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident related to the airbag control module in Volkswagen vehicles is categorized as non-malicious. The issue stemmed from a faulty capacitor in the module, causing the airbag system to act incorrectly by potentially deactivating the airbags or deploying them at an improper time. Volkswagen identified the problem through field cases and collaboration with the supplier, leading to a recall to address the defect. The remedy involved flashing the cars with a software update to detect the faulty capacitor and replacing the airbag control module if needed [86997].
Intent (Poor/Accidental Decisions) unknown (a) The software failure incident related to the airbag control module in Volkswagen vehicles was not due to poor decisions but rather a faulty capacitor within the module. The issue was identified after multiple field cases were reported, leading to the decision for a recall and a software update to detect the fault [86997].
Capability (Incompetence/Accidental) accidental (a) The software failure incident in the Volkswagen recall was not attributed to development incompetence. The issue stemmed from a faulty capacitor in the airbag control module, causing the airbag system to malfunction [86997]. (b) The software failure incident in the Volkswagen recall was accidental, as it was caused by a faulty capacitor in the airbag control module, leading to incorrect airbag deployment or deactivation [86997].
Duration temporary The software failure incident related to the airbag control module in Volkswagen's recall is temporary. The faulty capacitor in the module can cause the airbag system to act incorrectly, leading to issues such as airbags deactivating or deploying at an improper time. The remedy involves flashing the cars with a software update that can detect an increase in resistance within the module caused by the faulty capacitor. If the increased resistance is found, technicians will replace the airbag control module, indicating that the failure is due to specific circumstances related to the faulty component [86997].
Behaviour omission, timing, value, other (a) crash: The software failure incident in the Volkswagen recall article is not described as a crash where the system loses state and does not perform any of its intended functions. (b) omission: The faulty capacitor in the airbag control module can cause the airbag system to omit performing its intended functions correctly. It might cause the airbags to deactivate or deploy at an improper time, leading to the omission of correct airbag deployment [86997]. (c) timing: The software failure incident is related to timing issues as the faulty capacitor in the airbag control module can cause the airbags to deploy at an improper time, which can greatly increase the risk of injury [86997]. (d) value: The software failure incident is related to value issues as the faulty capacitor in the airbag control module can cause the airbag system to perform its intended functions incorrectly, such as deactivating the airbags or deploying them at an improper time [86997]. (e) byzantine: The software failure incident is not described as a byzantine failure where the system behaves erroneously with inconsistent responses and interactions. (f) other: The other behavior of the software failure incident is the illumination of the airbag warning light, which serves as an indicator that something is amiss with the airbag system [86997].

IoT System Layer

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

Other Details

Category Option Rationale
Consequence harm, theoretical_consequence The consequence of the software failure incident described in the article is related to harm. The faulty capacitor in the airbag control module can cause the airbag system to act incorrectly, potentially leading to the deactivation or improper deployment of airbags and seatbelt pretensioners. This incorrect behavior of the airbag system can greatly increase the risk of injury to individuals, whether a crash is involved or not [86997].
Domain transportation (a) The failed system in the article is related to the transportation industry. The software failure incident involved the airbag control module in Volkswagen vehicles, specifically the 2015-2016 Tiguan and CC models, which are components of the transportation industry as they are vehicles designed for moving people [86997].

Sources

Back to List