Qantas Flight 32 uncontained engine failure
An Airbus A380's engine disintegrated in flight over Indonesia, sending debris through the wing and fuselage; the crew safely landed the severely damaged aircraft with no fatalities.
The damage was public. The root cause was preventable.
An Airbus A380's engine disintegrated in flight over Indonesia, sending debris through the wing and fuselage; the crew safely landed the severely damaged aircraft with no fatalities.
What the software actually got wrong
While the initiating failure was a manufacturing defect in an oil pipe, the engine explosion triggered over 100 individual ECAM warning and caution messages in quick succession, and the flight-warning software's design provided no way to prioritize or filter them, overwhelming the crew during the most critical phase of the emergency.
While the initiating failure was a manufacturing defect in...
While the initiating failure was a manufacturing defect in an oil pipe, the engine explosion triggered over 100 individual ECAM warning and caution messages in quick succession
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-warning software's design provided no way to prioritize...
the flight-warning software's design provided no way to prioritize or filter them, overwhelming the crew during the most critical phase of the emergency
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.
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.