To: Tzfat
You are correct. The computer did exactly what it was designed to do. In the event the computer doesn’t like what the pilot is doing the computer decides for him and locks out the pilot and flies how it wants to fly. It’s called fly-by-wire. The flight computer makes the final decision on any pilot input and can override any commands.
It’s pretty obvious the AF447 flight computer was having a bad silicon day and wouldn’t let the pilots even put the freaking nose down to get out of the stall. As far as I know Boeing airplanes don’t have this problem.
44 posted on
05/27/2011 8:28:23 AM PDT by
Jack Hydrazine
(It's the end of the world as we know it and I feel fine!)
To: Jack Hydrazine
53 posted on
05/27/2011 9:35:58 AM PDT by
raygun
To: Jack Hydrazine
In the event the computer doesnt like what the pilot is doing the computer decides for him and locks out the pilot and flies how it wants to fly. Its called fly-by-wire. The flight computer makes the final decision on any pilot input and can override any commands.
No, you are wrong. Have you ever flown an Airbus (or anything for that matter). Your so-called "lock out" is not a function of any fly-by-wire aircraft within normal flight regimes. Period. Did you stay at a Holiday Express last night?
Its pretty obvious the AF447 flight computer was having a bad silicon day and wouldnt let the pilots even put the freaking nose down to get out of the stall. As far as I know Boeing airplanes dont have this problem.
Wrong again. The cause is most likely not a software failure, but a hardware failure. A320 and A330/340 aircraft were under an Airworthiness Directive at the time to replace faulty pitot tubes. It just so happens that numerous Boeing aircraft had crashes (with loss of life) because of just such failures. A Northwest B727 crashed in 1974 with a loss of all souls for that very reason.
58 posted on
05/27/2011 12:46:04 PM PDT by
Tzfat
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson