|
Airbus have been looking at all the data [of the QF flight] for months now, and where are we hey? Cosmic rays! Give me a break.
I can see four major conclusions;
1. It's a bug in the flight computer and they've not been able to replicate it, thus it still exists.
2. They've found something and won't make it public until they have a recitification action tested and ready to roll-out.
3. There's an unknown incompatibility between the input devices and the flight computer, which may take years to determine and rectify.
4. FBW is technologically premature and may carry something from #1-3 (my belief).
In cases 1-3, intermittent issues can occur. I have just seen the end on a data messaging corruption (lock-up) for Australian Fire and Emergency Services and that was a single occurance every 6-9 months of continuous operation. That's once in over 2 million transmissions/receptions of identical messages. So even though the message is exactly the same, and the firmware remains the same, the system didn't lock-up for millions of cycles...hugely frustrating! But when it finally did, it was as dumb as a post, and came without any warning. The system could not be rebooted, it required re-flashing of the firmware first, then a hard start. There was nothing in the data to suggest what was going on, it was determined through searching tens of thousands of lines of script.
This is a similar scenario to what we are seeing with the Qantas flight as well as some other recorded cases. The systems seem fine both before and after, but it was real and the flight data would support that.
I still stand behind FBW being way too premature.
|