Comment swithched Imputs / Outputs (Score 1) 369
From my reading of the reports both engines didn't fail simultaneously, but rather one failed 8 seconds after the first, and while there was fuel onboard that doesn't necessarily rule out fuel starvation from another cause such as contamination or a fuel blockage. While a software or hardware failure is unlikely to be the sole contributer to the cause, reversed inputs / outputs to the FADEC system could have led to the system inadvertenly causing the incident.
Say for example the EEC on engine one indicates that it is experiencing fuel starvation from tank 1, and FADEC decides to switch engine one to tank 2, however because of reversed inputs / outputs it was infact engine 2 suffering the effects, now both engines are feeding from tank 2 where the fuel starvation is stemming from (be it cotaminated or blocked)! The time for the system to do the calculations and switch tanks is under 10 seconds, so in reality within 10 seconds the second engine would show similar characteristics. Not entirely different from the British midlands crash in the 1980's only it was the pilots who recieved the reversed information and reacted accordingly and shut down the engine appearing to be on fire, only they actually shut down their good engine.
As for the pilots, it is without doubt that their quick reaction saved many lives, immediately upon the problem arising the captain(pilot not flying) raised the flaps, while this raised the ultimate stall speed, it enabled the aircraft to at least make the right side of the fence.