TAM Airlines Flight 3054 runway overrun
An Airbus A320 overran the runway at Sao Paulo-Congonhas Airport and crashed into a building, killing all 187 people aboard and 12 on the ground.
The damage was public. The root cause was preventable.
An Airbus A320 overran the runway at Sao Paulo-Congonhas Airport and crashed into a building, killing all 187 people aboard and 12 on the ground.
What the software actually got wrong
One throttle lever was left in the climb-power detent while the other was set to idle for landing, and the aircraft's thrust-control logic did not clearly alert the crew that asymmetric power settings would prevent the spoilers and thrust reversers from deploying, causing the plane to accelerate down the wet runway instead of stopping.
One throttle lever was left in the climb-power detent...
One throttle lever was left in the climb-power detent while the other was set to idle for landing
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 aircraft's thrust-control logic did not clearly alert the...
the aircraft's thrust-control logic did not clearly alert the crew that asymmetric power settings would prevent the spoilers and thrust reversers from deploying, causing the plane to accelerate down the wet runway instead of stopping
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.