Posted on 06/27/2009 5:07:40 AM PDT by Erik Latranyi
A Northwest Airlines jet traveling from Hong Kong to Tokyo last Tuesday suffered a series of equipment and computer malfunctions strikingly similar to those encountered by Air France Flight 447 just before it crashed into the Atlantic Ocean on May 31.
The Northwest plane and its passengers, however, emerged unscathed. Details of the harrowing incident described in a memo by one of the Northwest pilots and confirmed Friday by others familiar with the matter highlight how cockpit crews can safely cope with something that is almost never supposed to happen: a system breakdown that prevented the crew from knowing how fast the plane was flying.
During the brief but dramatic event, the Northwest Airbus A330's crew was left without reliable speed measurements for three minutes. In addition, the computer safeguards designed to keep the aircraft from flying dangerously too fast or too slow were also impaired. Like the Air France A330 jetliner, the Northwest plane entered a storm and quickly started showing erroneous and unreliable airspeed readings.
(Excerpt) Read more at online.wsj.com ...
Think of it this way: If your ground speed is 200 mph, but you have a 100 mph tail wind, then your actual air speed is only 100 mph (200 mph - 100mph). If you have a 100 mph head wind, then your air speed is 300 mph with a 200 mph ground speed. The aircraft doesn't care what the ground speed is, only the speed of the airflow past the aircraft.
I wouldn't define a possible failure of multiple pitot-static and/or air data systems as "still working properly". It is like saying a car without brakes or a steering wheel still operates normally because it can propel itself.
Fortunately, the airplane's engine control systems continued to work, allowing the pilot to control the speed of the airplane using power settings.
The pilot said the airspeed indicators returned to normal, but the flight-control computers never did.
The question is, was this caused by some kind of pitot-static system issue (i.e., icing), or an air data computer issue, or some combination of both.
I am guessing it is a pitot-static icing problem which introduces out of norm data into the air data system, which given the flight conditions (high-altitude, high speed cruise) causes the air data computer to go haywire.
So the airplane makes its own throttle adjustment to the airspeed data ? Sounds like the DC metro train unfortunately.
Every ststem on this aircraft is fail safe fail safe fail safe.Fly by wire die by wire.
My friend is a pilot, not a structural guy. The report was attributed to George Larson, Editor emeritus of Smithsonian Air & Space Magazine.
so airspeed is a quantity relative to the surrounding atmosphere rather than to GPS coordinates; thank you.
GPS will tell you your ground speed, it will not tell you your airspeed.
Having had no experience with such gear, we bought one in early May for our recent month toodling around the lower third of the entire country....amazing what these little gadgets can do.
Air moves. Your GPS indicated speed will enable you to crash very accurately.
Airspeed is the primary factor in causing lift. If flight were not totally dependent upon lift, then air speed would be unimportant.
NTSB should ground all A330’s until this problem has been fixed.
ours got stolen; consequently spent 45 minutes looking for a pizza shop last night rather than 10 minutes.
"Tuesday 23rd June, 2009 10am enroute HKG to NRT. Entering Narita Japan airspace.
"FL390 mostly clear with occasional isolated areas of rain, clouds tops about FL410. "Outside air temperature was -50C TAT -21C (you're not supposed to get liquid water at these temps). We did.
"As we were following other aircraft along our route. We approached a large area of rain below us. Tilting the weather radar down we could see the heavy rain below, displayed in red. At our altitude the radar indicated green or light precipitation, most likely ice crystals we thought.
"Entering the cloud tops we experienced just light to moderate turbulence. (The winds were around 30kts at altitude.) After about 15 seconds we encountered moderate rain. We thought it odd to have rain streaming up the windshield at this altitude and the sound of the plane getting pelted like an aluminum garage door. It got very warm and humid in the cockpit all of a sudden. Five seconds later the Captain's, First Officer's, and standby airspeed indicators rolled back to 60kts. The auto pilot and auto throttles disengaged. The Master Warning and Master Caution flashed, and the sounds of chirps and clicks letting us know these things were happening.
"Jerry Staab, the Capt. hand flew the plane on the shortest vector out of the rain. The airspeed indicators briefly came back but failed again. The failure lasted for THREE minutes. We flew the recommended 83%N1 power setting. When the airspeed indicators came back we were within 5 knots of our desired speed. Everything returned to normal except for the computer logic controlling the plane. (We were in alternate law for the rest of the flight.)
"We had good conditions for the failure; daylight, we were rested, relatively small area, and light turbulence. I think it could have been much worse. Jerry did a great job flying and staying cool. We did our procedures called dispatch and maintenance on the SAT COM and landed in Narita. That's it."
Warm rain at FL390. I bet there was a hailstorm down on the ocean below.
Geez I hate to post this but here goes. It’s like NASCAR drivers establishing their pit road speed by the rpms shown on the tachometer in a specific gear.
I’ve driven a car with a broken speedometer but a functioning tachometer. I determined speed by rpm readings and the gear I was in from prior experience in the car.
I think this is why I was never much good at flying a kite; my only solution ever to be was “run faster.”
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.