Thread: $1.4 Billion lost due in part to lack of ... communication

Originally Posted by AvWeb

The crash on takeoff of a 509th Air Wing, Air Force B-2 Spirit bomber, February 23 operating at Andersen Air Force Base, Guam, was caused by water in the aircraft's sensors, according to an Air Combat report issued Thursday. Specifically, moisture in three port transducer units "distorted data introduced by a B-2 Spirit's air data system" which led to flawed information entering the bomber's flight control computers. The aircraft was reacting to inaccurate airspeed and a "perceived" negative angle of attack. This resulted in an "uncommanded 30 degree nose-high pitch-up on takeoff," according to the Air Force.

Major Ryan ]ineffective communication of critical information [/color] about a technique used to remove moisture from the sensors also contributed.
It's possible that all the pilots had to do to avert the accident was turn on the pitot heat prior to performing air data calibrations. But the suggested technique was not part of checklist procedures.

http://www.youtube.com/watch?v=8ZB-iziY2Bw

Pilot error killed this aircraft.

The takeoff should have been aborted when the flight computer threw a fit. At that point, they were well below V1 speed. Instead, they continued, well beyond V1, before the errors "corrected themselves", and subsequently crashed.

In an aircraft which must almost entirely be controlled by flight computer systems, I think it was foolish to continue the flight after such an error ocurred. The pilots should have been well aware of how essential and what command authority the computer has, and should have respected any malfunction thereof.

See Aeroperu Flight 603 for another example where 70 people died because maintenance didn't remove a single piece of tape.

Draco

At least the money spent on the ejection seats was well spent...

Originally Posted by draco7891

Pilot error killed this aircraft.

The takeoff should have been aborted when the flight computer threw a fit. At that point, they were well below V1 speed. Instead, they continued, well beyond V1, before the errors "corrected themselves", and subsequently crashed.

In an aircraft which must almost entirely be controlled by flight computer systems, I think it was foolish to continue the flight after such an error ocurred. The pilots should have been well aware of how essential and what command authority the computer has, and should have respected any malfunction thereof.

See Aeroperu Flight 603 for another example where 70 people died because maintenance didn't remove a single piece of tape.

Draco

Of course...whoever was flying wasn't qualified to make the proper decisions that you just listed...too bad you weren't flying it.


Marm

Originally Posted by draco7891

Pilot error killed this aircraft.

The takeoff should have been aborted when the flight computer threw a fit. At that point, they were well below V1 speed. Instead, they continued, well beyond V1, before the errors "corrected themselves", and subsequently crashed.

In an aircraft which must almost entirely be controlled by flight computer systems, I think it was foolish to continue the flight after such an error ocurred. The pilots should have been well aware of how essential and what command authority the computer has, and should have respected any malfunction thereof.

See Aeroperu Flight 603 for another example where 70 people died because maintenance didn't remove a single piece of tape.

Draco

From what I understand, the computer just said "Screw You" and started doing what it wanted. I took it to mean that the pilots were trying to regain control of the plane and put it back down, but I guess that's open to interpretation.

ALERT!

Someone has tried to register using the IP Address 124.134.52.127 which is MATCHED IN THE RBL DATABASE of the proxies.dnsbl.sorbs.net RBL.

This registration attempt has been allowed and the account has been permanently banned.

Registration Details: seolin887 ( qiulian@lovesoftware.net )