Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Turkish Airlines Crash Explained : inattentive pilots

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web

erikgigem

Well-known member
Joined
Mar 4, 2006
Posts
101
Initial findings to this tragic accident. See article for the whole story. -Erik

SOURCE: Wall Street Journal
http://online.wsj.com/article/SB123621483296035363.html

Dutch investigators indicated a malfunctioning altitude indicator combined with inattentive pilots resulted in last week's fatal crash of a Turkish Airlines jet approaching Amsterdam's Schiphol Airport, sparking new concerns about the issue of cockpit complacency...

..John Goglia, a former member of the U.S. National Transportation Safety Board, said the preliminary findings highlight that pilots "are supposed to monitor aircraft systems," but "automation tends to make some complacent" and extra training may be necessary to counter that trend.

The details disclosed so far in the Amsterdam crash indicate that the crew seemingly failed to notice -- or simply disregarded -- a number of warnings that ought to have alerted them about an impending stall...
 
On a Boeing memo we got from our company today regarding the crash, the FDR/CVR revealed that at 2,000' the left hand RA read -8 feet and triggered the auto throttles to retard.

For 100 seconds, the crew allowed their airspeed to decay to 40 knots below Vref before the stick shaker activated.

Why didn't the pilot flying disconnect the auto throttles to get back on speed?

Why didn't the pilot monitoring mention anything about the decaying airspeed?

I think Sully would be dissapointed...
 
Are autothrottles really worth the increased mishap rate with them? Anyone with experience care to elaborate? Nothing keeps you in the loop like managing power to control airspeed.
 
Are autothrottles really worth the increased mishap rate with them? Anyone with experience care to elaborate? Nothing keeps you in the loop like managing power to control airspeed.

Thats why i like the crj 200, but you have to remember "never compromise savings" auto throttles save a lot of $
 
Are autothrottles really worth the increased mishap rate with them? Anyone with experience care to elaborate? Nothing keeps you in the loop like managing power to control airspeed.
The opposite may be listed as a probable cause in the Colgan crash. If the autopilot levels off after a flight-idle descent and you forget or get side tracked, the airspeed will decay quickly. I just flew a q400 with the autopilot deferred and I must say that i was more aware of my situational awareness then with the autopilot.
 
The opposite may be listed as a probable cause in the Colgan crash. If the autopilot levels off after a flight-idle descent and you forget or get side tracked, the airspeed will decay quickly. I just flew a q400 with the autopilot deferred and I must say that i was more aware of my situational awareness then with the autopilot.

I like being aware of my situational awareness.
 
When I was at Eagle on the SAAB, they taught that the "ALTS" on the EFIS meant "Add a little torque, stupid."

I remember that saying!!
Today as I have the opportunity to fly heavier and more advanced aircraft, I still back up the autothrottles by keeping my hand on them when they are engaged...especially during the approach. I have never had to disconnect them beacuse of a problem, but I have come pretty close a few times.
 
Anyone knows how long were they on duty? Fatigue a suspect? That one always get overlooked. 16 hour duty day, 8 hours of flying? Weather delayed? ...

Third country of not, those guys had been safe pilots and made it all the way up a 737 by being safe and methodical until that day. What really happened?...
 
The latest from the Aviation Herald:
http://avherald.com/h?article=41595ec3/0052&opt=0
Accident: Turkish Airlines B738 at Amsterdam on Feb 25th 2009, landed on a field
By Simon Hradecky, created Wednesday, Mar 4th 2009 13:59Z, last updated Wednesday, Mar 4th 2009 15:15Z

The Dutch Accident Investigators have revealed first results in a press conference in Den Haag today. With the exception of the left radio altimeter the Dutch Safety Board has not found any irregularities with the aircraft. The airplane was carrying 127 passengers and 7 crew. 9 occupants were killed in the accident, thereof 4 crew and 5 passengers. 28 of the injured are still in hospital care. The captain was occupying the left hand seat, a fully qualified first officer occupied the right hand seat. For this first officer this was a training flight. Another first officer occupied the observer's seat.

The airplane was performing an ILS approach to runway 18R on autopilot in fairly bad visibility according to standard operating procedures by Turkish Airlines. Mist and low cloud prevailed suggesting, that the crew most likely did not see Polderbaan (runway 18R) while commencing the final descent. While the airplane was at 1950 feet MSL with the autoflight systems coupled to the ILS already, the left hand radar altimeter produced a wrong height reading of -8 feet. This resulted in the autothrottles to pull the thrust to idle. The landing gear warning horn sounded as a result of the erroneous reading, but was not considered to be a problem according to the cockpit voice recorder. However, this warning should have alerted the crew of a radar altimeter problem. The stick shaker activated at a height of about 500 feet AGL, at which point full power was applied. This however was already too late to recover the flight and the airplane subsequently impacted ground. The airplane hit ground with the tail first at a speed of 92 knots (normal landing speed would have been 140 knots) and slid for about 150 meters until coming to a stop. The airplane's tail broke off and the fuselage ruptured at the business class, the landing gear separated according to its design. The engines separated and continued for an additional about 250 meters due to the thrust they developed and the sudden deceleration of the airframe.

The fatalities were mainly along the line of rupture through the business class. The cockpit crew was fatally injured mainly because of the enormeous deceleration forces and the nose wheel, that got partially embedded into the cockpit.

The flight data recorder stores 25 hours of flight data, which covered the last 8 flights of the airplane. During those flights another two failures of the left hand radar altimeter had been recorded. A Boeing Alert sent to all operators of 737s (all types) said, that no evidence of bird strike, engine or airframe icing, wake turbulence or windshear has been found so far. There was adequate fuel on board throughout the entire flights. Both engines responded normally to throttle inputs, the airplane responded normally to flight control inputs all the time. The digital flight data recorder indicated, that the autopilot B and autothrottle was being used for an ILS approach to runway 18R. The right hand radar altimeter was providing proper data, while the left hand radar altimeter provided faulty readings of -7 and -8 feet. The autothrottles, using the left hand radar altimeter, transitioned to the flare mode and retarded the throttles to idle thrust. The throttles remained at the idle stop for about 100 seconds, while the airspeed dropped to 40 knots below selected approach speed.

According to Boeing, if one of the radar altimeters provides erroneous height readings (regardless of whether the radar altimeter indicates itsself failed or not - failure flag or not), typical flight deck effects requiring crew intervention would be erratic radar altimeter readings on the instrument displays with differences between the two readings, inability to engage both autopilots in dual mode for the approach mode, unexpected removal of flight director bars, unexpected configuration warnings and a premature autothrottle RETARD announciation on the pilots' primary flight displays.
 
Probably be smart enough not to fly on Turkish Airways. Or any other POS 3rd world carrier

Right, because American pilots have never screwed up? Taking off on the wrong runway, slamming one into a Columbian mountainside after losing SA due to FMS programming, etc. etc.

Nothing wrong with TK. This was just one said unfortunate accident.
 
This unfortunate accident like the others was because of crew inattention to basic flying skills. Letting a plane do something you don't want it to do isn't automations fault. The pilots should be letting automation help them not let it take you places you do not want to go. Disconnecting the AP and AT makes you in charge again so blaming the RA because of a glitch is no reason to crash an airplane.
 
Difete thanks,

I am having impure thoughts about your avatar. Stop! Stop! go away impure thoughts from my brain.
 

Latest resources

Back
Top Bottom