Re:No, not the Avionics... (Score 1)

But both FADECs would consist of identical hardware and be running identical software correct? So despite the safety precautions, it is still theoretically possible that some command sent to them triggered the exact same bug in both, assuming an actual software or specification problem. (In systems like these a specification can be buggy) That would be one of my suspicions.

I'm not familiar with the B777 or the Trent engines, but on other aircraft the FADEC typically only receive quite simple commands. Those commands are pretty much universally independent between the two FADECs (i.e. if one command was screwy, it should only affect one FADEC. But even then, commands coming into the FADEC would normally be checked for validity. Thrust commands typically come from LVDT attached to the thrust levers in the cockpit. Other things like engine anti-ice commands typically are simply discrete inputs from cockpit switches, or commands via a data bus.

I'll bet you a case of beer that the AAIB report will state that something other than a FADEC software bug caused this accident.

My bet is on some other common cause, such as a fuel issue (water in fuel, or out of spec fuel freezing or gelling in the fuel system and restricting the fuel flow, etc).