XL Airways Germany Flight 888T crash
An Airbus A320 on a customer-acceptance test flight crashed into the Mediterranean Sea off Perpignan, France, killing all 7 people aboard.
The damage was public. The root cause was preventable.
An Airbus A320 on a customer-acceptance test flight crashed into the Mediterranean Sea off Perpignan, France, killing all 7 people aboard.
What the software actually got wrong
Angle-of-attack sensors had been washed, then obstructed by water that froze at altitude; the flight-control computers, unable to get valid angle-of-attack data, could not provide the low-speed stall protection the crew was relying on during a low-speed test maneuver, and the aircraft stalled and crashed before the crew could recover.
Angle-of-attack sensors had been washed, then obstructed by water...
Angle-of-attack sensors had been washed, then obstructed by water that froze at altitude
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
The flight-control computers, unable to get valid angle-of-attack data,...
the flight-control computers, unable to get valid angle-of-attack data, could not provide the low-speed stall protection the crew was relying on during a low-speed test maneuver
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
The aircraft stalled and crashed before the crew could...
the aircraft stalled and crashed before the crew could recover
Requs AI Edge Case and Software FMEA together treat this as a known, catalogued defect pattern — not a novel surprise — so it gets tested for deliberately rather than discovered after deployment.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.