Dagestan Airlines Flight 372

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Dagestan Airlines Flight 372
File:Dagestan Airlines Flight 372 crash site (from MAK report)-11.jpg
The tailfin of the aircraft at the crash site
Accident summary
Date December 4, 2010 (2010-12-04)
Summary Crew error, fuel starvation
Site Domodedovo International Airport, Domodedovsky District, Moscow Oblast, Russia
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 160
Crew 8
Injuries (non-fatal) 92
Fatalities 2
Survivors 166
Aircraft type Tupolev Tu-154M
Operator Dagestan Airlines
Registration RA-85744
Flight origin Vnukovo International Airport, Moscow
Destination Uytash Airport, Makhachkala

Dagestan Airlines Flight 372 was a scheduled commercial flight between Vnukovo International Airport, Moscow and Uytash Airport, Makhachkala. On December 4, 2010 a Tupolev Tu-154M operating the flight, with registration RA-85744,[1] skidded off the runway following an emergency landing at Domodedovo International Airport, 45 km south-east of Vnukovo. Two people on board were killed.[2]

Aircraft

File:South East Airlines Tupolev Tu-154.jpg
Dagestan Airlines RA-85744 Tu-154M, the aircraft involved. The airline had been renamed South East Airlines when this photo was taken.

The aircraft operating the flight was a Tupolev Tu-154M, registered RA-85744,cn: 92A-927.[3] It had been built in 1992, and was equipped with three Soloviev D-30KU jet engines for propulsion.[3] The aircraft had been completely overhauled in 2009, and met all relevant European safety standards, as it had been used for the transport of the Belgium national football (soccer) team in November 2010, a flight which required it to meet European regulations.[4]

Accident

The plane was flying a scheduled trip from Vnukovo International Airport in Moscow to Uytash Airport in Makhachkala, Republic of Dagestan.[5] Two of the aircraft's three engines failed shortly after take off from Vnukovo Airport at 14:07 local time (11:07 UTC); the pilots reported the loss of engines when the aircraft was at a height of around 9,100 metres (29,900 ft).[1] An emergency landing at Domodedovo International Airport was requested, and as the aircraft was in the process of landing, the third engine failed.[1][5] The aircraft approached runway 32R from the right at almost right angles, overflying the threshold before turning right at 500 metres (1,600 ft) to the left of the runway and crossing over the runway, flying parallel with but to the right of the runway.[6] The aircraft touched down 88 metres (289 ft) to the right of the runway centerline, and only 350 metres (1,150 ft) short of the end, about a half-hour after its departure, landing in conditions of freezing rain.[1][6]

The landing caused the plane to sustain major damage,[7] and it was written off shortly after the incident.[8] A passenger on board the plane said that the aircraft broke into three parts after landing.[9] Later reports said that both the cockpit and vertical stabilizer had separated from the aircraft, and that the wings and undercarriage had both been damaged.[3]

Casualties

The emergency landing resulted in 92 injuries (of which 39 were serious) and two fatalities.[10][11][12][13]

One of the two dead was Gadzhimurad Magomedov, the brother of Magomedsalam Magomedov, the president of Dagestan.[14] The other (died of a heart attack) was the mother of a judge of the Constitutional Court of Russia.

The number of people on board the plane was unclear; early reports said that between 163 and 172 people were on board,[5][15] but a number of 168, eight of which were crew members, was later settled on.[5][8]

Aftermath

Russian authorities dispatched investigators to the site of the emergency landing,[7] classifying the investigation as a "criminal probe", according to the Russian Investigative Committee.[15] Prosecutor General Yury Chaika was said to be "keeping a watchful eye" over the proceedings.[15] Several hours after the incident occurred, the lead prosecutor in the investigation said that the preliminary results suggested a bird strike was responsible for the loss of engines.[1]

By the day after the incident, investigators had recovered the flight data recorder and a second data-storing device.[16][clarification needed] The Interstate Aviation Committee (MAK) said that it had begun analysis of both recovered devices, which were said to be in "satisfactory condition".[16] The cockpit voice recorder was recovered on 10 December.[17] Analysis of the flight data recorder showed that eight minutes after the aircraft took off, at an altitude of 6,500 metres (21,300 ft), the fuel supply to the engines fluctuated, and as the aircraft passed 9,000 metres (30,000 ft), the outer two engines shut down.[18] The crew at this point began a descent towards Domodedovo Airport.[18] The central engine had a "period of instability", but its normal status was "restored and maintained" until the aircraft's landing.[18]

The fuel supply at Vnukovo Airport was confirmed to meet standards.[18] On 1 April 2011, investigators announced that poor fuel quality had been ruled out as a cause of the crash, despite instrument readings that indicated issues with the fuel supply before the aircraft crashed.[19]

On 26 September 2011, the MAK released its report into the incident, concluding that the cause was the flight engineer accidentally shutting off a fuel pump while transferring fuel.[6] As a result, fuel consumption fluctuated, leading to unusual altitude and engine readings before the outer two engines shut down.[6] At this point, the crew chose to bring the plane to Domodedovo Airport.[6] The report said that the crew had not used all available options to deal with the loss of engine power and had not followed procedures for landing with two nonfunctional engines.[6] The report also noted that the crew had not been sufficiently trained to deal with the situation.[6]

On 22 January 2015, the airplane's pilot Zakarzha Zakarzhayev was found guilty in court under article 263.3 of the Criminal Code of Russia (violating safety rules of transportation and air travel, which led by neglect to death of two or more people).[20] He was given a suspended sentence of 3 years and then immediately amnestied.[21]

References

  1. 1.0 1.1 1.2 1.3 1.4 Lua error in package.lua at line 80: module 'strict' not found.
  2. http://lenta.ru/news/2010/12/04/noengines
  3. 3.0 3.1 3.2 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. 5.0 5.1 5.2 5.3 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 6.4 6.5 6.6 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Final report, section 1.2
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 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 15.2 Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 18.3 Lua error in package.lua at line 80: module 'strict' not found.
  19. 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.

External links