Incident: Airbag Sensor Failure in Subaru Forester Occupant Detection System

Published Date: 2019-08-13

Postmortem Analysis
Timeline 1. The software failure incident involving the Subaru Forester's airbag sensor was reported on August 6, 2019, in Article 88241. Therefore, the software failure incident happened in August 2019.
System 1. Occupant detection system in the Subaru Forester vehicles from the 2016 to 2018 model years [88241]
Responsible Organization 1. The software failure incident in the Subaru Forester involving the airbag sensor was caused by a fault in the occupant detection system, leading to the failure to turn on the front-passenger airbag when the seat is occupied [88241].
Impacted Organization 1. Owners of Subaru Forester vehicles from the 2016 to 2018 model years [88241] 2. National Highway Traffic Safety Administration (NHTSA) [88241]
Software Causes 1. Software bug in the occupant detection system causing the front-passenger airbag not to deploy when the seat is occupied [88241].
Non-software Causes 1. Occupant detection system failing to turn on the front-passenger airbag when the seat is occupied. 2. Reports of the SRS light illuminating in the dashboard. 3. Risk of injury due to potential airbag failure to deploy in the event of a crash. 4. Lack of response from Subaru regarding the investigation. 5. Lack of reports of crashes, fires, injuries, or deaths related to the alleged problem (as per NHTSA document) [88241].
Impacts 1. Increased risk of injury to occupants due to the airbag sensor failure to deploy in the event of a crash [88241].
Preventions 1. Implementing thorough testing procedures during the development phase to detect any issues with the occupant detection system and SRS light functionality before the vehicles are released to the market [88241]. 2. Conducting regular software updates and maintenance checks to ensure the proper functioning of the airbag sensor system throughout the lifespan of the vehicle [88241].
Fixes 1. Software update or patch to address the issue with the occupant detection system failing to turn on the front-passenger airbag when the seat is occupied [88241].
References 1. NHTSA document dated Aug. 6 [88241]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident related to the Subaru Forester's airbag sensor has happened again within the same organization. The NHTSA opened a preliminary evaluation into the Subaru Forester after receiving multiple complaints about the vehicle's airbag sensor, indicating a recurring issue with the software system in the vehicle [88241]. (b) There is no information in the provided article to suggest that a similar incident has happened at other organizations or with their products and services.
Phase (Design/Operation) design (a) The software failure incident related to the design phase can be inferred from the article as the NHTSA opened an investigation into the Subaru Forester after receiving complaints about the vehicle's airbag sensor. Owners reported issues with the occupant detection system failing to turn on the front-passenger airbag when the seat is occupied, indicating a potential design flaw in the system [88241]. (b) The software failure incident related to the operation phase is not explicitly mentioned in the article.
Boundary (Internal/External) within_system (a) The software failure incident related to the Subaru Forester's airbag sensor issue seems to be within the system. The failure is described as the occupant detection system failing to turn on the front-passenger airbag when the seat is occupied, and reports of the SRS light illuminating in the dashboard [88241]. These issues indicate a failure within the system's software or sensors that are responsible for detecting occupants and deploying airbags correctly.
Nature (Human/Non-human) non-human_actions (a) The software failure incident related to the Subaru Forester's airbag sensor issue seems to be a case of non-human_actions. The NHTSA investigation was initiated based on multiple complaints from owners about the occupant detection system failing to turn on the front-passenger airbag when the seat is occupied. This indicates a potential fault or bug in the software system controlling the airbag sensor, which is a non-human factor contributing to the failure [88241].
Dimension (Hardware/Software) hardware (a) The software failure incident related to hardware: The article mentions complaints about the vehicle's airbag sensor system, specifically the occupant detection system failing to turn on the front-passenger airbag when the seat is occupied. This issue is related to hardware components such as the sensor system in the vehicle [88241]. (b) The software failure incident related to software: The article does not provide specific information indicating that the failure originated in the software. It primarily focuses on complaints related to the airbag sensor system and the occupant detection system, which are hardware components [88241].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident related to the Subaru Forester's airbag sensor does not appear to be malicious. The article does not mention any intentional actions by humans to harm the system. Instead, it describes complaints from owners about the occupant detection system failing to turn on the front-passenger airbag when the seat is occupied, and reports of the SRS light illuminating in the dashboard. The National Highway Traffic Safety Administration (NHTSA) has opened an investigation into the issue, and Subaru has not responded to requests for comment yet. There have been no reports of crashes, fires, injuries, or deaths related to this problem [88241].
Intent (Poor/Accidental Decisions) unknown The articles do not provide specific information about whether the software failure incident related to the Subaru Forester's airbag sensor was due to poor decisions or accidental decisions. Therefore, the intent behind the software failure incident remains unknown.
Capability (Incompetence/Accidental) accidental (a) The article does not provide specific information indicating the software failure incident occurred due to development incompetence. Therefore, it is unknown. (b) The article mentions complaints about the occupant detection system failing to turn on the front-passenger airbag when the seat is occupied, and reports of the SRS light illuminating in the dashboard. These issues could be considered as software failures introduced accidentally, leading to potential safety risks related to airbag deployment [88241].
Duration unknown The articles do not provide specific information about whether the software failure incident related to the Subaru Forester's airbag sensor issue is permanent or temporary.
Behaviour omission, value, other (a) crash: The software failure incident in the article is not described as a crash where the system loses state and does not perform any of its intended functions [88241]. (b) omission: The software failure incident involves the occupant detection system failing to turn on the front-passenger airbag when the seat is occupied, indicating an omission of performing its intended function [88241]. (c) timing: The article does not mention the software failure incident being related to the system performing its intended functions too late or too early [88241]. (d) value: The software failure incident involves the system performing its intended function incorrectly, as the front-passenger airbag is not activated when needed, leading to a potential safety risk [88241]. (e) byzantine: The software failure incident is not described as the system behaving erroneously with inconsistent responses and interactions [88241]. (f) other: The software failure incident involves the SRS light illuminating in the dashboard, which could be considered as an additional behavior not covered by the options provided [88241].

IoT System Layer

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

Other Details

Category Option Rationale
Consequence theoretical_consequence (a) death: People lost their lives due to the software failure (b) harm: People were physically harmed due to the software failure (c) basic: People's access to food or shelter was impacted because of the software failure (d) property: People's material goods, money, or data was impacted due to the software failure (e) delay: People had to postpone an activity due to the software failure (f) non-human: Non-human entities were impacted due to the software failure (g) no_consequence: There were no real observed consequences of the software failure (h) theoretical_consequence: There were potential consequences discussed of the software failure that did not occur (i) other: Was there consequence(s) of the software failure not described in the (a to h) options? What is the other consequence(s)? The articles do not mention any consequences related to death, harm, basic needs, property damage, or non-human entities resulting from the software failure incident. There were no reports of crashes, fires, injuries, or deaths involving the alleged problem [88241]. The potential consequences discussed were related to the increased risk of injury if the airbag fails to deploy in the event of a crash [88241].
Domain transportation (a) The failed system in the incident was related to the transportation industry as it involved the Subaru Forester's airbag sensor malfunction, which is crucial for passenger safety in vehicles [88241].

Sources

Back to List