Recurring |
one_organization |
(a) The software failure incident of the iPad app crashing for American Airlines pilots is an example of a similar incident happening again within the same organization. This incident affected multiple flights in American Airlines' fleet, causing delays and inconvenience to passengers [35193].
(b) The articles do not provide information about a similar incident happening again at other organizations or with their products and services. |
Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase can be seen in the article where American Airlines experienced a significant issue with the iPad app used by pilots as part of their electronic flight bags. The app crashed, affecting multiple planes scattered throughout the entire fleet. This incident was attributed to a software application issue on pilot iPads, indicating a failure introduced during the development or design phase of the system [35193].
(b) The software failure incident related to the operation phase is evident in the same article where American Airlines had to delay multiple flights due to the iPad app crash. The pilots were unable to take off because their iPads powered down unexpectedly, leading to flight disruptions. This failure was a result of the operation or use of the system, as the pilots were directly impacted by the software glitch during their flight operations [35193]. |
Boundary (Internal/External) |
within_system |
(a) The software failure incident involving the American Airlines pilot iPads crashing can be categorized as within_system. The incident was caused by a glitch in the electronic flight bag app used by pilots, which led to multiple flights being delayed [35193]. The issue originated from within the system itself, affecting the functionality of the iPads and disrupting flight operations. |
Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident related to non-human actions occurred when the iPad app used by pilots crashed, affecting multiple flights in the American Airlines fleet [35193].
(b) The software failure incident related to human actions involved a security researcher who was barred from a United Airlines flight after tweeting about attempting to hack the passenger oxygen controls on his flight [35193]. |
Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident related to hardware:
- The incident with American Airlines' iPad app crashing affected multiple flights due to the iPads powering down unexpectedly, which can be attributed to hardware issues with the devices themselves [35193].
(b) The software failure incident related to software:
- The main software failure incident in this case was the crash of the iPad app used by pilots, which disrupted multiple flights and required some planes to return to the gate for a Wi-Fi connection to fix the issue. This points to a software problem within the application itself [35193]. |
Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the American Airlines iPad app crash can be categorized as non-malicious. The incident was caused by a glitch in the software application used by pilots, leading to the iPads powering down unexpectedly, affecting multiple flights across the airline's fleet [35193]. The issue was not a result of malicious intent but rather a technical failure within the software system. |
Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The software failure incident involving American Airlines' iPad app crash can be attributed to poor decisions. The incident was a result of the app crashing, affecting multiple flights and leaving pilots unable to take off. The decision to rely solely on the iPad app as an "electronic flight bag" without a backup plan in case of such failures can be considered a poor decision. This incident highlights the risks associated with depending entirely on technology without adequate contingency measures in place [35193]. |
Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident related to development incompetence is not explicitly mentioned in the provided articles.
(b) The software failure incident related to accidental factors is evident in the article. The incident where the iPad app used by pilots crashed, leading to flight delays and affecting multiple planes in the American Airlines fleet, was an accidental failure. The crash of the app was unexpected and unfamiliar to the pilots, indicating that it was not intentional but rather a result of an accidental software glitch [35193]. |
Duration |
temporary |
(a) The software failure incident related to the American Airlines pilot iPads crashing was temporary. The incident caused delays in multiple flights, with some flights having to return to the gate to access a Wi-Fi connection to fix the issue. An American Airlines spokesperson confirmed the issue with the software application on pilot iPads and mentioned that they were working to have the flights on the way to their destination as soon as possible [35193]. |
Behaviour |
crash |
(a) crash: The software failure incident in Article 35193 involved a crash of the iPad app used by pilots, which led to delays in multiple flights as the pilots were unable to take off due to the app crashing [35193].
(b) omission: There is no specific mention of the software failure incident being related to the system omitting to perform its intended functions at an instance(s) in the provided article.
(c) timing: The software failure incident did not involve the system performing its intended functions correctly, but too late or too early.
(d) value: The software failure incident did not involve the system performing its intended functions incorrectly.
(e) byzantine: The software failure incident did not involve the system behaving erroneously with inconsistent responses and interactions.
(f) other: The behavior of the software failure incident in Article 35193 can be categorized as a crash, where the system lost state and did not perform its intended functions, leading to flight delays and inconvenience for passengers [35193]. |