AirAsia Flight 8501 crash
An Airbus A320 crashed into the Java Sea, killing all 162 people aboard.
The damage was public. The root cause was preventable.
An Airbus A320 crashed into the Java Sea, killing all 162 people aboard.
What the software actually got wrong
A cracked solder joint in the rudder travel limiter unit had caused repeated fault warnings on earlier flights; the crew responded by pulling circuit breakers to reset the system, which unexpectedly disengaged the autopilot and dropped the aircraft into a reduced flight-envelope-protection mode that the crew was not trained to recognize, and manual inputs then sent the aircraft into an unrecoverable stall.
A cracked solder joint in the rudder travel limiter...
A cracked solder joint in the rudder travel limiter unit had caused repeated fault warnings on earlier flights
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 crew responded by pulling circuit breakers to reset...
the crew responded by pulling circuit breakers to reset the system, which unexpectedly disengaged the autopilot and dropped the aircraft into a reduced flight-envelope-protection mode that the crew was not trained to recognize
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.
Manual inputs then sent the aircraft into an unrecoverable...
manual inputs then sent the aircraft into an unrecoverable stall
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.