Incident: Automatic Emergency Braking Glitch in Honda Vehicles Causes Sudden Braking

Published Date: 2022-02-24

Postmortem Analysis
Timeline 1. The software failure incident involving the glitch in Honda Accord sedans and CR-V SUVs happened when the National Highway Traffic Safety Administration started investigating the issue, which was reported in the article published on 2022-02-24 [124007]. Therefore, the software failure incident occurred before February 2022.
System 1. Automatic Emergency Braking systems in 2018 and 2019 Honda Accord sedans and 2017 to 2019 CR-V SUVs [Article 124007]
Responsible Organization 1. The software failure incident in the Honda Accord sedans and CR-V SUVs was caused by a possible glitch in the Automatic Emergency Braking system [Article 124007].
Impacted Organization 1. Drivers of Honda Accord sedans and CR-V SUVs [Article 124007] 2. National Highway Traffic Safety Administration (NHTSA) [Article 124007]
Software Causes 1. The software cause of the failure incident in the Honda Accord sedans and CR-V SUVs was a possible glitch in the Automatic Emergency Braking (AEB) systems, which sometimes caused the cars to randomly slam on the brakes without the driver touching the brake pedal [124007].
Non-software Causes 1. The failure incident in the Honda Accord sedans and CR-V SUVs was attributed to a possible glitch in the Automatic Emergency Braking system, causing the cars to randomly slam on the brakes without the driver touching the brake pedal [124007].
Impacts 1. The software failure incident in Honda Accord sedans and CR-V SUVs, where the cars randomly slammed on the brakes without driver input, led to 278 complaints received by NHTSA, with six of these complaints resulting in collisions and some minor injuries [124007].
Preventions 1. Implementing more rigorous testing procedures during the development phase to identify and address potential glitches in the Automatic Emergency Braking system [124007]. 2. Conducting thorough real-world simulations and scenario testing to ensure the system functions as intended in various driving conditions and scenarios [124007]. 3. Enhancing the system's fail-safe mechanisms to prevent unintended braking incidents, such as implementing redundant sensors or introducing additional layers of verification before engaging the automatic braking feature [124007].
Fixes 1. Conduct a thorough software code review to identify and rectify any bugs or glitches in the Automatic Emergency Braking system software [124007]. 2. Implement rigorous testing procedures, including real-world simulations and scenarios, to ensure the proper functioning of the emergency braking system without any false activations [124007]. 3. Provide a software update or patch to the affected vehicles to address the issue causing the random slamming on the brakes without driver input [124007].
References 1. National Highway Traffic Safety Administration (NHTSA) [Article 124007] 2. Honda [Article 124007] 3. Insurance Institute for Highway Safety [Article 124007]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident related to sudden braking without driver input has happened again within the same organization. The article mentions that NHTSA opened an investigation into Tesla cars for similar problems earlier this month, indicating that Honda is not the only automaker facing issues with their automatic braking systems [124007].
Phase (Design/Operation) design, operation (a) The software failure incident related to the design phase can be seen in the article where it mentions that the National Highway Traffic Safety Administration (NHTSA) is investigating popular Honda Accord sedans and CR-V SUVs for a possible glitch in the Automatic Emergency Braking systems. The glitch causes the cars to randomly slam on the brakes without the driver touching the brake pedal, indicating a failure introduced during the system development or updates [Article 124007]. (b) The software failure incident related to the operation phase is evident in the complaints received by NHTSA regarding sudden braking for no reason in Accords and CR-Vs. Some of these complaints involved collisions, with several people reporting that the problem occurred in their vehicles multiple times. This indicates a failure introduced by the operation or misuse of the system [Article 124007].
Boundary (Internal/External) within_system (a) within_system: The software failure incident related to the Honda Accord sedans and CR-V SUVs involves a glitch in the Automatic Emergency Braking systems installed in the vehicles. This glitch causes the cars to randomly slam on the brakes without the driver touching the brake pedal, leading to sudden braking for no reason. The system is designed to automatically apply the brakes if the driver fails to do so in certain situations, such as a vehicle stopping in front of them or a pedestrian in the vehicle’s path. The misfiring of these automatic braking systems can contribute to crashes that the technology was meant to prevent, potentially causing rear-end collisions [124007]. (b) outside_system: The article does not mention any contributing factors originating from outside the system that led to the software failure incident.
Nature (Human/Non-human) non-human_actions (a) The software failure incident related to non-human actions in the reported articles is the glitch in the Automatic Emergency Braking system in Honda Accord sedans and CR-V SUVs. This glitch causes the cars to randomly slam on the brakes without the driver touching the brake pedal, potentially leading to rear-end collisions [124007]. (b) The software failure incident related to human actions in the reported articles is the investigation by the National Highway Traffic Safety Administration (NHTSA) into the complaints of sudden braking for no reason in Accords and CR-Vs. The complaints, some of which involved collisions, were submitted by drivers who experienced the problem multiple times, indicating a potential flaw in the system's design or implementation [124007].
Dimension (Hardware/Software) hardware, software (a) The software failure incident related to hardware: - The article mentions that the National Highway Traffic Safety Administration (NHTSA) is investigating Honda Accord sedans and CR-V SUVs for a possible glitch in the Automatic Emergency Braking systems that causes the cars to randomly slam on the brakes without the driver touching the brake pedal [124007]. - The issue with the Automatic Emergency Braking system, which is a hardware component in the vehicles, is causing the sudden braking incidents reported by drivers. (b) The software failure incident related to software: - The article explains that when the automatic braking systems misfire, making vehicles stop or slow suddenly for no real reason, it can contribute to the very sort of crashes the technology was designed to prevent [124007]. - This indicates that the software controlling the Automatic Emergency Braking system is not functioning as intended, leading to the unexpected braking events reported by drivers.
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident described in the article is non-malicious. The failure is attributed to a possible glitch in the Automatic Emergency Braking systems of Honda Accord sedans and CR-V SUVs, causing the cars to randomly slam on the brakes without the driver touching the brake pedal. This glitch has led to numerous driver complaints and incidents of sudden braking for no reason, potentially resulting in collisions and minor injuries [124007].
Intent (Poor/Accidental Decisions) accidental_decisions The intent of the software failure incident related to the Honda Accord and CR-V vehicles investigated by the National Highway Traffic Safety Administration (NHTSA) appears to align more with the option of 'accidental_decisions' rather than 'poor_decisions'. The incident involves a possible glitch in the Automatic Emergency Braking systems of these vehicles, causing them to randomly slam on the brakes without driver input. This issue seems to stem from unintended behavior or mistakes in the software rather than poor decisions made intentionally by the developers or manufacturers. The article does not suggest deliberate poor decisions as the cause of the failure but rather highlights the unintended consequences of the software glitch [124007].
Capability (Incompetence/Accidental) development_incompetence, accidental (a) The software failure incident related to development incompetence is evident in the article as it mentions a possible glitch in the Automatic Emergency Braking systems of Honda Accord sedans and CR-V SUVs. The glitch causes the cars to randomly slam on the brakes without the driver touching the brake pedal, leading to complaints and even collisions [124007]. (b) The software failure incident related to accidental factors is also present in the article, where it describes how the automatic braking systems misfire, making vehicles stop or slow suddenly for no real reason. This unintended consequence can lead to crashes that the technology was designed to prevent, highlighting an accidental failure scenario [124007].
Duration temporary The software failure incident related to the Honda Accord sedans and CR-V SUVs involves a temporary failure. The incident is described as a glitch in the Automatic Emergency Braking system that causes the cars to randomly slam on the brakes without the driver touching the brake pedal. This glitch occurs under certain circumstances, such as when the system misfires and makes the vehicles stop or slow suddenly for no real reason, leading to potential collisions [124007].
Behaviour value, other (a) crash: The software failure incident described in the article is not related to a crash where the system loses state and does not perform any of its intended functions. Instead, the issue involves the Automatic Emergency Braking (AEB) systems in Honda vehicles randomly slamming on the brakes without driver input, indicating a malfunction in the braking system [124007]. (b) omission: The incident does not involve the system omitting to perform its intended functions at an instance(s). Instead, the problem lies in the system applying the brakes unexpectedly and without the driver touching the brake pedal [124007]. (c) timing: The failure is not related to the system performing its intended functions correctly but too late or too early. The issue is with the system applying the brakes inappropriately, leading to potential collisions [124007]. (d) value: The software failure incident is related to the system performing its intended functions incorrectly. The Automatic Emergency Braking system in Honda vehicles is malfunctioning by randomly applying the brakes without driver input, which can lead to accidents [124007]. (e) byzantine: The incident does not involve the system behaving erroneously with inconsistent responses and interactions. The issue is more straightforward, with the AEB system in Honda vehicles exhibiting a specific malfunction of randomly slamming on the brakes without driver intervention [124007]. (f) other: The behavior of the software failure incident can be described as a glitch in the Automatic Emergency Braking system of Honda vehicles, causing the cars to unexpectedly apply the brakes, potentially leading to collisions. This behavior is not consistent with the intended function of the AEB system, which is designed to prevent or reduce the severity of rear-end collisions by applying the brakes in specific situations [124007].

IoT System Layer

Layer Option Rationale
Perception sensor (a) The failure in the reported incident seems to be related to the sensor layer of the cyber physical system. The article mentions that Honda's emergency braking system uses radar to track vehicles ahead. If the radar sensor misfires or provides incorrect information about the proximity of the vehicle ahead, it can lead to the automatic application of brakes without a real reason, contributing to crashes that the technology was designed to prevent [124007].
Communication connectivity_level The software failure incident reported in the article [124007] is related to the connectivity level of the cyber physical system. The issue described involves the Automatic Emergency Braking (AEB) systems in Honda Accord sedans and CR-V SUVs randomly slamming on the brakes without driver input. This problem is attributed to a glitch in the AEB technology, which is designed to automatically apply the brakes in certain situations. The malfunction of this system at the connectivity level, possibly involving the network or transport layer, leads to sudden braking incidents that can result in collisions [124007].
Application TRUE The software failure incident described in the article [124007] is related to the application layer of the cyber physical system. The article mentions that the National Highway Traffic Safety Administration is investigating Honda Accord sedans and CR-V SUVs for a possible glitch in the Automatic Emergency Braking systems. This glitch causes the cars to randomly slam on the brakes without the driver touching the brake pedal, indicating a failure introduced by bugs or errors in the application layer of the system.

Other Details

Category Option Rationale
Consequence harm (b) harm: People were physically harmed due to the software failure The software failure incident involving the Honda Accord sedans and CR-V SUVs led to several collisions, with some resulting in minor injuries to individuals. The National Highway Traffic Safety Administration (NHTSA) received 278 complaints of sudden braking for no reason in these vehicles, and six of these complaints allegedly involved collisions, causing physical harm to individuals [124007].
Domain transportation (a) The failed system in the article is related to the transportation industry. The National Highway Traffic Safety Administration (NHTSA) is investigating Honda Accord sedans and CR-V SUVs for a possible glitch in their Automatic Emergency Braking systems, which are designed to prevent rear-end collisions [Article 124007].

Sources

Back to List