
British Airways chief executive described the incident as “catastrophic” as 800 flights were canceled and 75,000 travelers were affected.
Flight compensation website flightright.com estimated that British Airways would have to pay around €61m to passengers for refunds alone under EU legislation. Add to this the cost of reimbursing angry passengers for unexpected hotel stays and other inconveniences, and the total financial damage to British Airways has been estimated at £100m.
Why? Someone turned their data center off and on again.
The entire airline was down for almost 2 days. This wasn’t a natural disaster, it was a process failure.
In this article, we’ll explore how to spot process failures before they occur using a system called Failure Mode and Effects Analysis (FMEA). We’ll assess an overview and then delve in deeper to ground our understanding and include a premade Process Street FMEA template to help you run your own assessments in future.
In this article we’ll cover:
- Your free FMEA (Failure Modes and Effects Analysis) template
- FMEA? What is Failure Mode and Effects Analysis?
- When do we use FMEA?
- Conducting and documenting Failure Mode and Effect Analysis: A user’s guide
- What happened to British Airways?
- Why did it happen?
- How can FMEA help us prevent this happening again?








