Turkish Airlines Flight 1951

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Turkish Airlines Flight 1951
File:Crash Turkish Airlines TK 1951 cockpit 2.jpg
The Turkish Airlines Boeing 737-8F2, registration TC-JGE, just after the crash near Schiphol Airport.
Accident summary
Date 25 February 2009 (2009-02-25)
Summary Main reason: Faulty radio altimeter. Minor reasons: pilot error, stall[1][2][3][4][5]
Site North of the Polderbaan runway (18R/36L), near Amsterdam Airport Schiphol
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 128
Crew 7
Injuries (non-fatal) 117 (including 11 serious)
Fatalities 9
Survivors 126
Aircraft type Boeing 737-8F2
Aircraft name Tekirdağ
Operator Turkish Airlines
Registration TC-JGE
Flight origin Istanbul Atatürk Airport, Istanbul, Turkey
Destination Amsterdam Airport Schiphol, Amsterdam, Netherlands

Turkish Airlines Flight 1951 (also known as the Poldercrash) was a passenger flight that crashed during landing at the Amsterdam Schiphol Airport, Netherlands, on 25 February 2009, resulting in the death of nine passengers and crew including all three pilots.

The aircraft, a Turkish Airlines Boeing 737-800, crashed into a field approximately 1.5 kilometres (0.93 mi) north of the Polderbaan runway, (18R), prior to crossing the A9 motorway inbound, at 9:31 UTC (10:31 CET), having flown from Istanbul, Turkey. The aircraft broke into three pieces on impact. The wreckage did not catch fire.[6][7][8]

The crash was caused primarily by the aircraft's automated reaction which was triggered by a faulty radio altimeter. This caused the autothrottle to decrease the engine power to idle during approach. The crew noticed this too late to take appropriate action to increase the thrust and recover the aircraft before it stalled and crashed.[9] Boeing has since issued a bulletin to remind pilots of all 737 series and BBJ aircraft of the importance of monitoring airspeed and altitude, advising against the use of autopilot or autothrottle while landing in cases of radio altimeter discrepancies.[10]

Background

Aircraft

Boeing 737-8F2 TC-JGE, the plane that was involved, landing at Kiev-Boryspil Airport in January 2009

The aircraft, built in 2002, was a Next Generation Boeing 737-800 series model 8F2[11] with registration TC-JGE, named "Tekirdağ".[12][13] The model −8F2 denotes the configuration of the 737-800 built for use by Turkish Airlines. They had 51 aircraft of this model in service at the time of the crash.[14]

Flight

There were 128 passengers and seven crew members on board.[12][15][16] The plane was under the command of Instructor Captain Hasan Tahsin Arısan,[17] one of the airline's most experienced senior pilots.[not in citation given] A former Turkish Air Force fleet commander, Captain Arısan had been working for Turkish Airlines since 1996. He had over 5,000 hours of flight time on the F-4E Phantom II.[18] The other flight deck crew members were Olgay Özgür, was the safety pilot of the flight, and he was graduated from a flight school in Ankara, and flew the MD 80 for World Focus Airlines before joining Turkish Airlines and passing the 737 type rating, he was sitting in the cockpit's center jump seat, and Murat Sezer, co-pilot under line training, flying as co-pilot. The cabin crew consisted of Figen Eren, Perihan Özden, Ulvi Murat Eskin, and Yasemin Vural.[17]

Landing and damage

The plane was cleared for an approach on runway 18R (also known as the Polderbaan runway) but came down short of the runway threshold, sliding through the wet clay of a plowed field.

The aircraft suffered significant damage. Although the fuselage broke into three pieces, it did not catch fire. Both engines separated and came to rest 100 metres (300 ft) from the fuselage.[18]

Aftermath

File:Location crash Turkish Airlines TK 1951.svg
Runway diagram of Schiphol Airport with the Polderbaan runway depicted in black and the location of the crash marked with a red star
File:Crash Turkish Airlines TK 1951 plane engine.jpg
Both jet engines separated, coming to rest 100 metres (330 ft) from the fuselage

While several survivors and witnesses indicated that it took rescuers 20 to 30 minutes to arrive at the site after the crash,[19][20] others have stated that the rescuers arrived quickly at the scene.[19][21][22] About 60 ambulances arrived along with at least three LifeLiner helicopters (air ambulances, Eurocopter EC135), and a fleet of fire engines.[citation needed][23] An unconfirmed report by De Telegraaf states that the firefighters were at first given the wrong location for the crash site, delaying their arrival.[24] Lanes of the A4 and A9 motorways were closed to all traffic to allow emergency services to quickly reach the site of the crash.

The bodies of three cockpit crew members were the last to be removed from the plane, at around 20:00 that evening, because the cockpit had to be examined before it could be cut open to get to these crew members.[25] Also, some of the survivors say that at least one of the pilots was alive after the crash.[26] The relatives of the passengers on the flight were sent to Amsterdam by Turkish Airlines shortly after.[27]

The full crash site of Turkish 1951

All flights in and out of Schiphol Airport were suspended, according to an airport spokeswoman. Several planes were diverted to Rotterdam The Hague Airport as well as to Brussels Airport. At about 11:15 UTC, it was reported that the Kaagbaan runway (06/24) had been re-opened to air traffic, followed by the Buitenveldertbaan runway (09/27).[28]

Turkish Airlines continues to use Flight 1951 on its Istanbul (Atatürk) to Amsterdam route.[29]

Investigation

The investigation was led by the Dutch Safety Board (DSB, Dutch: Onderzoeksraad voor Veiligheid or OVV), and assisted by an expert team from Turkish Airlines and a representative team of the American NTSB, accompanied by advisors from Boeing and the FAA,[30][31] Turkish Directorate General of Civil Aviation (SHGM), the operator, the UK Air Accidents Investigation Branch, and the French Bureau d'Enquêtes et d'Analyses pour la sécurité de l'Aviation Civile (BEA).[10][32] The cockpit voice recorder and the flight data recorder were recovered quickly after the crash, after which they were transported to Paris to read out the data.[33] The Dutch public prosecution initially asked the DSB to hand over the black boxes, but the DSB refused to do so. It stated that there was no indication of homicide, manslaughter, hijacking or terrorism, which would warrant an investigation by the prosecution.[34][35]

While on final approach for landing, the aircraft was about 2,000 ft (610 m) above ground, when the left-hand (captain's) radio altimeter suddenly changed from 1,950 feet (590 m) to read −8 feet (−2.4 m) altitude, although the right-hand (co-pilot's) radio altimeter functioned correctly.[9] The voice recording showed that the crew was given an audible warning signal ("TOO LOW!, GEAR!") that indicated that the aircraft's landing gear should be down, as the aircraft was, according to the radio altimeter, flying too low.[9] Later, the safety board's preliminary report modified this analysis, indicating that the flight data recorder history of the captain's radio altimeter showed 8191 feet (the maximum possible recorded) until the aircraft descended through 1950, then suddenly showed negative 8 feet.[36]

The throttles were pulled back to idle thrust to slow the aircraft to descend and acquire the glideslope, but the autothrottle unexpectedly reverted to "retard" mode, which is designed to automatically decrease thrust shortly before touching down on the runway at 27 feet (8.2 m) above runway height.[37] At 144 kt, the pilots manually increased thrust to sustain that speed,[36] but the autothrottle immediately returned the thrust lever to idle power because the first officer did not hold the throttle lever in position. The throttles remained at idle for about 100 seconds while the aircraft slowed to 83 knots (154 km/h), 40 knots (74 km/h) below reference speed as the aircraft descended below the required height to stay on the glideslope.[38] The stick-shaker activated at about 150 metres (490 ft) above the ground, indicating an imminent stall, the autothrottle advanced, and the captain attempted to apply full power.[38] The engines responded, but there was not enough altitude or forward airspeed to recover, and the aircraft hit the ground tail-first at 95 knots (176 km/h).[38]

The data from the flight recorder also showed that the same altimeter problem had happened twice during the previous eight landings but that on both occasions the crew had taken the correct action by disengaging the autothrottle and manually increasing the thrust. Investigations are under way to determine why more action had not been taken after the altimeter problem was detected.[39] In response to the preliminary conclusions, Boeing issued a bulletin, Multi-Operator Message (MOM) 09-0063-01B, to remind pilots of all 737 series and Boeing Business Jet (BBJ) aircraft of the importance of monitoring airspeed and altitude (the "primary flight instruments"), advising against the use of autopilot or autothrottle while landing in cases of radio altimeter discrepancies.[10] Following the release of the preliminary report, Dutch and international press concluded that pilot inattention caused the accident,[40][41][42][43] though several Turkish news publications still emphasized other possible causes.[44][45]

On 9 March 2009, the recovery of the wreckage started. All parts of the plane were moved to an East Schiphol hangar[46][47] for reconstruction.[not in citation given]

It was reported that the first officer survived the accident but rescuers were unable to reach him via the cockpit door due to security measures introduced in the wake of the September 11, 2001 attacks. The rescuers eventually cut their way into the cockpit through the roof, by which time the first officer had died.[48]

On 6 May 2010 the final report was released.[49] Turkish Airlines disputes crash inquiry findings on stall recovery.[50]

Passengers

File:Memorial Area TK1951.jpg
Memorial area near the crash site.
File:Turkish Air 1951 Seating Chart EN 01.svg
Seat map showing injuries and deaths

There were nine fatalities and a total of 117 injuries, 11 of them serious.[49](p29,178-180) Five of the deceased victims were Turkish citizens, including the pilot, the co-pilot, a trainee pilot and one member of the cabin crew.[51][52][53][54] Four were Americans, of whom three have been identified as Boeing employees stationed in Ankara and working on an Airborne Early Warning and Control (AEW&C) program for the Turkish military.[15][55][56][6][47]

The plane carried 53 passengers from the Netherlands, 51 from Turkey, seven from the United States, three from the United Kingdom, one each from Germany, Bulgaria, and Italy, and one from either Thailand[57][58] or Taiwan.[55][56][59]

Among the passengers were the sisters Jihad and Hajar Alariachi, presenters of the Dutch television programme De Meiden van Halal. Jihad and Hajar were taken to hospital with minor injuries.[60]

Dramatization

The story of the disaster was featured on the tenth season of Canadian TV series Mayday, the episode is entitled "Who's in Control?".[61]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found., official translation from Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. Final report, section 2.4 "History of the flight", p.25
  17. 17.0 17.1 Turkish Airlines names four dead crew members in Amsterdam crash
  18. 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  23. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. http://www.flightradar24.com/data/flights/tk1951/
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  36. 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found. Section 4.20.14
  38. 38.0 38.1 38.2 Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. 47.0 47.1 Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. 55.0 55.1 Lua error in package.lua at line 80: module 'strict' not found.
  56. 56.0 56.1 Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.

External links

External images
image icon Photos of TC-JGE at airliners.net
image icon Photos of TC-JGE from AirDisaster.com