Incident: Galaxy Note 7 WiFi Hotspot Incident on Virgin America Flight

Published Date: 2016-12-23

Postmortem Analysis
Timeline 1. The software failure incident involving the Galaxy Note 7 WiFi hotspot on a Virgin America flight occurred in December 2016 as per the article published on December 23, 2016 [58206].
System The software failure incident involving the Galaxy Note 7 phones on the Virgin America flight was due to a specific system failure. The system that failed in this incident was: 1. WiFi network system on the Galaxy Note 7 phone [58206]
Responsible Organization 1. The individual who changed their device's WiFi network name to 'Galaxy Note 7_1097' on the Virgin America flight [58206].
Impacted Organization 1. Virgin America flight 358 crew members [58206]
Software Causes 1. The software cause of the failure incident was a passenger changing their device's WiFi network name to 'Galaxy Note 7_1097,' which prompted the crew to panic, thinking there was a Galaxy Note 7 device on board [58206].
Non-software Causes 1. The failure incident was primarily caused by the Samsung Galaxy Note 7 phones overheating and catching fire, leading to their ban on planes and eventual production halt [58206]. 2. The design flaw in the phone itself, specifically related to the battery pack being squeezed to dangerous pressure levels, was identified as a key factor in the fires [58206].
Impacts 1. The software failure incident involving a passenger changing their device's WiFi network name to 'Galaxy Note 7' almost caused a Virgin America flight to be diverted, leading to panic among the crew and passengers [58206]. 2. The incident resulted in an announcement on the flight instructing anyone with a Galaxy Note 7 to press the call button, causing disruption and potential safety concerns [58206]. 3. The situation escalated to the point where the plane was threatened with diversion and search if the device was not found, causing inconvenience and stress to passengers [58206]. 4. Ultimately, the impact of the software failure incident was the discovery that the device in question was not actually a Galaxy Note 7 but had its WiFi network name changed to create confusion and concern [58206].
Preventions 1. Implementing stricter security measures to prevent unauthorized access and tampering with device names on WiFi networks could have prevented the incident [58206].
Fixes 1. Implementing stricter controls on WiFi network naming to prevent misleading names like 'Galaxy Note 7_1097' that can cause panic on flights [58206].
References 1. Lucas Wojciechowski's Twitter feed ([58206])

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident related to Samsung's Galaxy Note 7 phones catching fire and causing panic on a Virgin America flight is an example of a failure happening again within the same organization. Samsung had been dealing with issues with the Galaxy Note 7 since its release in August, with reports of the handsets catching fire leading to bans on planes in the US and other countries [58206]. (b) The incident involving the Galaxy Note 7 phones catching fire and causing a flight to almost be diverted due to a false alarm about the device being on board is an example of a software failure incident that has occurred at multiple organizations. The incident led to bans on the Galaxy Note 7 on planes not only in the US but also in other countries across Europe and Asia, indicating a widespread impact beyond just one organization [58206].
Phase (Design/Operation) design, operation (a) The software failure incident in the article can be attributed to the design phase. The incident occurred because someone on board a Virgin America flight changed their device's WiFi network name to 'Galaxy Note 7_1097,' causing panic among the crew and passengers, leading to a potential diversion of the plane [58206]. (b) The software failure incident can also be linked to the operation phase. The crew members on the Virgin America flight reacted to the perceived threat of a Galaxy Note 7 being on board due to the changed WiFi network name, which disrupted the operation of the flight and led to potential consequences like diversion and search of passengers' bags [58206].
Boundary (Internal/External) within_system (a) The software failure incident reported in the articles is within_system. The incident occurred due to a passenger on a Virgin America flight changing their device's WiFi network name to 'Galaxy Note 7_1097,' causing panic among the crew and leading to a potential diversion of the plane [58206]. This incident was a result of an action taken within the system (changing the WiFi network name) that directly impacted the situation on the flight.
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in this case was due to non-human actions. The incident occurred because someone on board a Virgin America flight changed their device's WiFi network name to 'Galaxy Note 7_1097,' which led the crew to panic and almost caused the plane to be diverted. This non-human action of changing the WiFi network name created a false alarm related to the banned Samsung Galaxy Note 7 phones catching fire [58206]. (b) The software failure incident was also influenced by human actions. The passenger who changed the WiFi network name to 'Galaxy Note 7_1097' on their device inadvertently triggered the panic on the flight, leading to the crew searching for the supposed Galaxy Note 7 device. Additionally, the decision to stop production of the faulty Galaxy Note 7 phones was made by Samsung for consumer safety reasons after numerous incidents of the phones overheating and catching fire, indicating a failure related to human actions in the design and manufacturing process of the device [58206].
Dimension (Hardware/Software) software (a) The software failure incident in the article was not directly related to hardware issues. The incident occurred due to a passenger changing their device's WiFi network name to 'Galaxy Note 7_1097' on a Virgin America flight, causing panic among the crew and passengers [58206]. (b) The software failure incident in the article was directly related to software issues. The incident involved a passenger changing the WiFi network name of their device to 'Galaxy Note 7,' which led to confusion and concern on the flight, ultimately causing disruptions and potential diversion of the plane [58206].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident in this case was non-malicious. The incident occurred when a passenger on a Virgin America flight changed their device's WiFi network name to 'Galaxy Note 7_1097,' causing panic among the crew who thought there was a Galaxy Note 7 device on board. This incident led to a search of passengers' bags and the threat of diverting the plane [58206]. (b) There is no indication in the articles that the software failure incident was malicious.
Intent (Poor/Accidental Decisions) poor_decisions (a) The intent of the software failure incident related to poor_decisions: - The incident involving the Galaxy Note 7 WiFi hotspot on a Virgin America flight was a result of a passenger changing their device's WiFi network name to 'Galaxy Note 7_1097,' causing panic among the crew (Article 58206). (b) The intent of the software failure incident related to accidental_decisions: - The incident on the Virgin America flight where the crew thought a Galaxy Note 7 was on board was an unintended consequence of a passenger changing the WiFi network name, leading to a search of everyone's bags on the plane (Article 58206).
Capability (Incompetence/Accidental) development_incompetence, accidental (a) The software failure incident in the article can be attributed to development incompetence. The incident occurred when a passenger on a Virgin America flight changed their device's WiFi network name to 'Galaxy Note 7_1097,' causing panic among the crew and leading to a potential diversion of the plane [58206]. This incident highlights the lack of professional competence in ensuring proper device identification and handling procedures, ultimately causing unnecessary disruption and confusion. (b) The software failure incident can also be considered accidental. The passenger who changed the WiFi network name to 'Galaxy Note 7_1097' likely did so without the intention of causing a security scare on the flight. It was an accidental action that led to the crew mistaking it for a real Galaxy Note 7 device, triggering a series of events that could have resulted in the plane being diverted [58206]. This accidental action inadvertently created a situation that required intervention and investigation by the flight crew.
Duration temporary The software failure incident related to the Galaxy Note 7 WiFi hotspot incident on the Virgin America flight was temporary. The incident occurred when a passenger changed their device's WiFi network name to 'Galaxy Note 7_1097,' causing panic among the crew and passengers. The crew had to search for the device, and the situation was resolved when it was discovered that only the name of the device was changed to 'Galaxy Note 7,' and it was not an actual Galaxy Note 7 device [58206].
Behaviour crash, omission, other (a) crash: The software failure incident in the article can be categorized as a crash. The incident involved the crew of a Virgin America flight panicking and considering diverting the plane due to a passenger changing their device's WiFi network name to 'Galaxy Note 7,' which led to a disruptive situation on the flight [58206]. (b) omission: The software failure incident can also be categorized as an omission. The system failed to perform its intended function of identifying the actual presence of a Galaxy Note 7 device on board the flight, leading to confusion and a potential diversion of the plane [58206]. (c) timing: The timing of the software failure incident is not explicitly mentioned in the article. However, the incident involved the crew reacting to the situation with urgency, such as making announcements and searching passengers' bags, indicating a need for timely responses [58206]. (d) value: The software failure incident does not align with a failure due to the system performing its intended functions incorrectly [58206]. (e) byzantine: The software failure incident does not exhibit characteristics of a byzantine failure, where the system behaves erroneously with inconsistent responses and interactions [58206]. (f) other: The other behavior exhibited in this software failure incident is the disruptive and potentially alarming nature of the incident, which caused panic among the crew and passengers due to the false impression of a Galaxy Note 7 device being on board the flight [58206].

IoT System Layer

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

Other Details

Category Option Rationale
Consequence harm (a) unknown (b) unknown (c) unknown (d) unknown (e) unknown (f) unknown (g) no_consequence (h) harm: The software failure incident led to panic and disruption on a Virgin America flight, with crew members searching bags and potentially diverting the plane due to a passenger changing their device's WiFi network name to 'Galaxy Note 7' [58206]. (i) unknown
Domain information, transportation (a) The failed system in this incident was related to the information industry as it involved the use of a Galaxy Note 7 phone, which was banned from planes due to safety concerns related to catching fire [58206]. The incident also highlighted the potential risks associated with using this device, impacting the production and distribution of information. (b) The transportation industry was indirectly affected by the software failure incident as a Virgin America flight almost had to be diverted due to a passenger changing their device's WiFi network name to 'Galaxy Note 7,' causing panic among the crew [58206]. (m) The incident does not directly relate to any other specific industry mentioned in the options provided.

Sources

Back to List