Incident: EasyJet IT Failure Causes Flight Cancellations and Stranded Passengers

Published Date: 2022-05-26

Postmortem Analysis
Timeline 1. The software failure incident happened on Thursday, as mentioned in the article [127735]. 2. Published on date: 2022-05-26 3. Estimated timeline: The incident occurred on Thursday, May 26, 2022.
System 1. IT systems [127735]
Responsible Organization 1. EasyJet (as the airline experiencing the software failure incident) [127735]
Impacted Organization 1. Customers of EasyJet flights, including holidaymakers stranded abroad and passengers at various airports across the UK [127735].
Software Causes 1. The software failure incident at EasyJet was caused by IT systems issues, resulting in flight cancellations and disruptions [127735].
Non-software Causes 1. Operational decision-making leading to flight cancellations [127735] 2. Communication issues with passengers regarding flight status [127735]
Impacts 1. Approximately 200 EasyJet flights were cancelled due to the software failure incident, affecting airports across the UK, including Gatwick, Edinburgh, Luton, Stansted, and Manchester [Article 127735]. 2. Holidaymakers were left stranded abroad as a result of the flight cancellations [Article 127735]. 3. Passengers experienced last-minute flight cancellations, with one woman mentioning that they were informed of the cancellation just 10 minutes before boarding the plane [Article 127735]. 4. Disruption in flight operations was expected to continue for some time even after the initial announcement of cancellations [Article 127735].
Preventions 1. Implementing thorough software testing procedures to identify and address any potential bugs or issues before deployment [127735]. 2. Regularly updating and maintaining the IT systems to ensure they are robust and up-to-date with the latest security patches and software upgrades [127735]. 3. Conducting regular system audits and risk assessments to proactively identify and mitigate any vulnerabilities in the software infrastructure [127735].
Fixes 1. Implementing robust software testing procedures to catch potential issues before they impact operations [127735]. 2. Conducting a thorough root cause analysis to identify the underlying reasons for the software failure and implementing measures to prevent similar incidents in the future [127735]. 3. Enhancing redundancy and failover mechanisms in the IT systems to ensure continuity of operations even in the event of software failures [127735].
References 1. EasyJet statement [127735]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident has happened again at one_organization: The article reports that EasyJet experienced a software failure that forced the airline to cancel some 200 flights. This incident caused disruption at airports across the UK, leaving holidaymakers stranded abroad. EasyJet apologized to customers for the inconvenience caused by the IT systems issues [Article 127735]. (b) The software failure incident has happened again at multiple_organization: There is no specific mention in the article about the software failure incident happening again at multiple organizations.
Phase (Design/Operation) design (a) The software failure incident in Article 127735 seems to be related to the design phase. The article mentions that EasyJet flights were cancelled after an IT failure, indicating that the failure was due to software issues introduced during system development or updates. The airline confirmed that the IT systems issues have been rectified, suggesting that the root cause was related to the design or development of the software system [127735].
Boundary (Internal/External) within_system (a) The software failure incident reported in Article 127735 was within_system. The article mentions that EasyJet flights were affected by an IT failure, indicating that the issue originated from within the airline's IT systems. The article states that the IT systems issues have been rectified by easyJet, further confirming that the failure was internal to their systems [127735].
Nature (Human/Non-human) non-human_actions (a) The software failure incident in the EasyJet case was primarily due to non-human actions, specifically an IT failure. The article mentions that EasyJet flights were cancelled after a software failure, and the airline confirmed that the IT systems issues were the cause of the disruption. This indicates that the failure was a result of contributing factors introduced without human participation [127735]. (b) The article does not provide specific information indicating that the software failure incident was due to contributing factors introduced by human actions.
Dimension (Hardware/Software) software (a) The software failure incident reported in Article 127735 was due to contributing factors originating in software. EasyJet flights were cancelled after an IT failure, indicating that the issue stemmed from the software systems used by the airline [127735].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident reported in Article 127735 does not indicate any malicious intent behind the failure. It appears to be a non-malicious failure caused by an IT failure that led to the cancellation of EasyJet flights, affecting numerous airports and leaving passengers stranded. The airline apologized to customers and mentioned that the IT systems issues have been rectified, with affected passengers advised to check Flight Tracker for flight status and apply for compensation [127735].
Intent (Poor/Accidental Decisions) unknown The software failure incident reported in Article 127735 does not provide specific details indicating whether the incident was caused by poor decisions or accidental decisions. The article mainly focuses on the impact of the failure, flight cancellations, stranded passengers, and the airline's response to the situation. Therefore, it is unknown whether the software failure was a result of poor decisions or accidental decisions.
Capability (Incompetence/Accidental) accidental (a) The software failure incident reported in Article 127735 does not explicitly mention development incompetence as a contributing factor. The article primarily focuses on the impact of the software failure on EasyJet flights and passengers, the cancellations, and the subsequent rectification of the IT systems issues. (b) The software failure incident in Article 127735 is described as an IT failure that forced EasyJet to cancel around 200 flights. The incident caused disruptions at airports across the UK, leaving holidaymakers stranded abroad. Passengers were informed of flight cancellations shortly before boarding, leading to inconvenience and chaos at various airports. The article does not indicate that the software failure was accidental; rather, it highlights the disruptions caused by the IT failure and the subsequent efforts to rectify the issues.
Duration temporary (a) The software failure incident in this case was temporary. EasyJet initially announced that the flights affected would be those departing between 13:00 and 15:00 BST on Thursday, but then mentioned that the disruption could last longer. The airline later confirmed that the IT systems issues had been rectified, indicating that the failure was not permanent [127735].
Behaviour omission, value, other (a) crash: The software failure incident in Article 127735 resulted in EasyJet having to cancel some 200 flights due to an IT failure, leaving holidaymakers stranded abroad. The disruption caused flights to be cancelled, impacting airports across the UK [127735]. (b) omission: The article mentions that passengers were told their flight had been cancelled just 10 minutes before they were due to board the plane, indicating a sudden omission of the intended function of providing flight services [127735]. (c) timing: The software failure incident caused disruptions to flights departing between 13:00 and 15:00 BST on Thursday, with the possibility of the disruption lasting longer. This delay in the system's performance aligns with a timing-related failure [127735]. (d) value: The software failure incident led to cancellations and disruptions in the flight schedule, indicating that the system was not performing its intended functions correctly, resulting in a value-related failure [127735]. (e) byzantine: The article does not provide information suggesting a byzantine behavior in the software failure incident. (f) other: The software failure incident also resulted in passengers being stuck at airports, including Gatwick and Stansted, and multiple flights being affected at various airports, showcasing a broader impact beyond just flight cancellations [127735].

IoT System Layer

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

Other Details

Category Option Rationale
Consequence property, delay (e) delay: People had to postpone an activity due to the software failure - The software failure incident led to the cancellation of some 200 flights by EasyJet, affecting airports across the UK and leaving holidaymakers stranded abroad [127735].
Domain transportation (a) The software failure incident reported in Article 127735 affected the airline industry, specifically EasyJet flights. The incident led to the cancellation of around 200 flights, causing disruption at airports across the UK and leaving holidaymakers stranded abroad [127735].

Sources

Back to List