Recurring |
one_organization |
(a) The software failure incident related to easyJet using incorrect take-off data due to a glitch in the electronic flight bag happened within the same organization. An investigation revealed that the likely reason for the incident was an anomaly on the electronic flight bag, and neither easyJet nor Airbus was aware of the glitch in Airbus’ FlySmart software. Airbus corrected the glitch in a software update after the incident [44383].
(b) There is no information in the provided article about the software failure incident happening again at multiple organizations or with their products and services. |
Phase (Design/Operation) |
design, operation |
(a) The software failure incident in the article was related to the design phase. The incident occurred due to a glitch in the electronic flight bag (a touchscreen tablet computer) that produced incorrect data for take-off calculations when the crew changed the condition from wet to dry runway. This glitch led to the pilots unknowingly using the wrong runway data, putting the aircraft at risk of overshooting the runway during take-off [44383].
(b) Additionally, the operation phase also played a role in the incident as the crew, specifically the captain and co-pilot, were operating the system and relying on the data provided by the electronic flight bag during the take-off process. The crew members were not aware that they were using incorrect figures for the runway, highlighting an operational aspect of the failure incident [44383]. |
Boundary (Internal/External) |
within_system |
The software failure incident involving easyJet pilots using incorrect take-off data for the wrong runway can be analyzed as follows:
(a) within_system: The software glitch that led to the incorrect take-off data being provided to the pilots was identified as originating from within the system. The glitch occurred in the electronic flight bag (EFB), a touchscreen tablet computer used by the crew to access critical flight information. This glitch resulted in the EFB producing data for a longer runway when the crew changed the condition from wet to dry, leading to the miscalculation of take-off performance figures [44383].
(b) outside_system: There is no explicit mention in the article of contributing factors originating from outside the system that led to the software failure incident. The primary cause of the incident was attributed to the software glitch within the electronic flight bag system, which provided incorrect data to the pilots during the pre-flight preparations and take-off process. |
Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident in the easyJet incident was attributed to a glitch in the electronic flight bag (EFB), a touchscreen tablet computer used by the crew to calculate take-off data. This glitch led to the EFB producing data for a longer runway when the crew changed the condition from wet to dry, resulting in the pilots unknowingly using incorrect figures for the actual runway length [44383].
(b) Human actions also played a role in the incident as the captain initially calculated take-off data for a shorter runway with wet conditions, anticipating rain showers nearby. When the runway was actually dry, the crew changed the condition for a reduced thrust setting. However, they were not aware that the software glitch in the EFB had produced data for a longer runway, leading to the use of incorrect figures during take-off [44383]. |
Dimension (Hardware/Software) |
software |
(a) The software failure incident in the article was not attributed to hardware issues but rather to a software glitch. The incident occurred due to a glitch in the electronic flight bag (a touchscreen tablet computer) that produced incorrect data for take-off calculations, leading to the pilots using the wrong runway data [44383].
(b) The software failure incident was specifically attributed to a software glitch. The glitch in the electronic flight bag software provided the pilots with erroneous information for take-off calculations, ultimately leading to the potential risk of overshooting the runway during take-off [44383]. |
Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident in the article was non-malicious. The incident was attributed to a software glitch in the electronic flight bag, which produced incorrect data for the take-off calculations on a different runway than the one the plane was actually using. This glitch led to the pilots unknowingly using the wrong take-off data, putting the aircraft at risk of overshooting the runway. The glitch was not intentional but rather a technical issue that resulted in incorrect information being provided to the flight crew [Article 44383]. |
Intent (Poor/Accidental Decisions) |
accidental_decisions |
The software failure incident involving easyJet pilots using incorrect take-off data for the wrong runway was primarily attributed to accidental_decisions. The incident occurred because of a glitch in the electronic flight bag (EFB) that produced data for a longer runway when the crew changed the condition from wet to dry. This unintentional error led to the pilots unknowingly using incorrect figures for take-off, putting the aircraft at risk of overshooting the runway [Article 44383]. |
Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in the article was not attributed to development incompetence. The incident was primarily caused by a glitch in the electronic flight bag (EFB) that produced incorrect take-off data for the pilots, leading to the use of wrong runway performance figures [44383].
(b) The software failure incident was categorized as accidental. The glitch in the electronic flight bag (EFB) that provided incorrect take-off data for the pilots was not intentional but rather an anomaly that occurred during the operation of the software. This accidental glitch led to the pilots using erroneous information for take-off, putting the aircraft at risk of overshooting the runway [44383]. |
Duration |
temporary |
(a) The software failure incident in the reported case was temporary. It was a temporary failure caused by a glitch in the electronic flight bag (EFB) that produced incorrect data for the take-off calculations. This glitch led to the pilots using the wrong runway data, putting the aircraft at risk during take-off [44383]. The incident was not a permanent failure as it was rectified through a software update by Airbus to correct the glitch in the FlySmart software used by the airline. |
Behaviour |
omission, value, other |
(a) crash: The software failure incident in the article did not involve a crash where the system lost state and did not perform any of its intended functions [Article 44383].
(b) omission: The software failure incident can be categorized as an omission where the system omitted to perform its intended functions at an instance(s). In this case, the software glitch led to the incorrect calculation of take-off data for the runway, putting the aircraft at risk of overshooting it [Article 44383].
(c) timing: The software failure incident was not related to timing issues where the system performed its intended functions correctly but too late or too early [Article 44383].
(d) value: The software failure incident falls under the category of value, where the system performed its intended functions incorrectly. The glitch in the electronic flight bag produced data for a longer runway when the crew changed the condition from wet to dry, leading to the miscalculation of take-off data [Article 44383].
(e) byzantine: The software failure incident did not exhibit behavior characteristic of a byzantine failure, where the system behaves erroneously with inconsistent responses and interactions [Article 44383].
(f) other: The software failure incident can be described as a case of incorrect behavior due to a software glitch in the electronic flight bag, resulting in the crew using incorrect figures for take-off calculations, ultimately putting the aircraft at risk [Article 44383]. |