Überlingen mid-air collision

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Bashkirian Airlines Flight 2937
DHL Flight 611
Accident summary
Date 1 July 2002 (2002-07)
Summary Mid-air collision aggravated by communication technology deficiencies
Site Überlingen, Germany
Lua error in package.lua at line 80: module 'strict' not found.
Total fatalities 71
Total survivors 0
First aircraft
180px
RA-85816, the aircraft involved in the accident, seen here at Stuttgart Airport in August 1997.
Type Tupolev Tu-154M
Operator Bashkirian Airlines
Registration RA-85816
Flight origin Domodedovo Int'l Airport[BFU 1][2]
Moscow, Russia
Destination Barcelona Int'l Airport
Barcelona, Spain
Passengers 60 (including 45 children)
Crew 9
Fatalities 69 (all)
Survivors 0
Second aircraft
180px
The DHL Boeing 757 involved in the accident
Type Boeing 757-23APF[1]
Operator DHL
Registration A9C-DHL
Flight origin Bahrain Int'l Airport[3][4]
Stopover Orio al Serio Airport
Bergamo, Italy
Destination Brussels Airport
Brussels, Belgium
Passengers 0
Crew 2
Fatalities 2 (all)
Survivors 0
Site of the crash is located in Germany
Site of the crash
Site of the crash
The crash occurred at approximately 47° 46′ 42″ N, 9° 10′ 26″ E.
File:Gedenkstätte Flugzeugabsturz Überlingen Perlenkette.jpg
Memorial tablet "Die zerrissene Perlenkette"

On 1 July 2002, Bashkirian Airlines Flight 2937, a Tupolev Tu-154 passenger jet with 69 people on board – mostly children – and DHL Flight 611, a Boeing 757 cargo jet with a crew of two, collided over the towns of Überlingen and Owingen, in southern Germany. All 71 people on board both aircraft were killed.[5]

The official investigation by the German BFU identified as the main cause of the collision a number of shortcomings on the part of the Swiss air traffic control service in charge of the sector involved, and also ambiguities in the procedures regarding the use of TCAS, the on-board aircraft collision avoidance system.[BFU 2]

Less than two years after the crash, on 26 February 2004, Peter Nielsen, the air traffic controller on duty at the time of the collision, was murdered in an apparent act of revenge by Vitaly Kaloyev, a Russian citizen who had lost his wife and two children in the accident.[6][7][8]

Flights involved

Bashkirian Airlines Flight 2937 was a chartered flight from Moscow, Russia, to Barcelona, Spain, carrying sixty passengers and nine crew. Forty-five of the passengers were Russian schoolchildren from the city of Ufa in Bashkortostan on a school trip organized by the local UNESCO committee to the Costa Dorada area of Spain.[2][3][9][10] Most of the parents of the children were high-ranking officials in Bashkortostan.[11] One of the fathers was the head of the local UNESCO committee.[12]

The aircraft, a Tupolev Tu-154M registered as RA-85816, was piloted by an experienced Russian crew: 52-year-old Captain Alexander Mihailovich Gross (Александр Михайлович Гросс) and 40-year-old First Officer Oleg Pavlovich Grigoriev (Олег Павлович Григорьев). The captain had more than 12,000 flight hours to his credit. Grigoriev, the chief pilot of Bashkirian Airlines, had 8,500 hours of flying experience and his task was to evaluate Captain Gross's performance throughout the flight. 41-year-old Murat Ahatovich Itkulov (Мурат Ахатович Иткулов), a seasoned pilot with close to 7,900 flight hours who was normally the first officer, did not officially serve on duty due to the captain's assessment. 50-year-old Sergei Kharlov, a flight navigator with approximately 13,000 flight hours, and 37-year-old Flight Engineer Oleg Valeev, who had almost 4,200 flight hours, joined the three pilots in the cockpit.[13]

DHL Flight 611, a Boeing 757-23APF cargo aircraft registered as A9C-DHL, had originated in Bahrain and was being flown by two Bahrain-based[3][14] pilots, 47-year-old British Captain Paul Phillips and 34-year-old Canadian First Officer Brant Campioni.[10] Both pilots were very experienced – the captain had logged close to 12,000 flight hours and the first officer had accumulated more than 6,600 flight hours. At the time of the accident, the aircraft was en route from Bergamo, Italy, to Brussels, Belgium.

Accident

The two aircraft were flying at flight level 360 (36,000 feet, 10,973 m) on a collision course. Despite being just inside the German border, the airspace was controlled from Zürich, Switzerland, by the private Swiss airspace control company Skyguide. The only air traffic controller handling the airspace, Peter Nielsen, was working two workstations at the same time. He did not realize the problem in time and thus failed to keep the aircraft at a safe distance from each other. Only less than a minute before the accident did he realize the danger and contacted Flight 2937, instructing the pilot to descend by a thousand feet to avoid collision with crossing traffic (Flight 611). Seconds after the Russian crew initiated the descent, however, their traffic collision avoidance system (TCAS) instructed them to climb, while at about the same time the TCAS on Flight 611 instructed the pilots of that aircraft to descend.[BFU 3] Had both aircraft followed those automated instructions, the collision would not have occurred.[BFU 4]

Flight 611's pilots on the Boeing jet followed the TCAS instructions and initiated a descent, but could not immediately inform Nielsen because the controller was dealing with Flight 2937. About eight seconds before the collision, Flight 611's descent rate was about 2,400 feet per minute (12 m/s), not as rapid as the 2,500 to 3,000 ft/min (13 to 15 m/s) range advised by TCAS. Having already commenced his descent, as instructed by the controller, the pilot on the Tupolev disregarded the TCAS instruction to climb,[BFU 5] thus both planes were now descending.

Unaware of the TCAS-issued alerts, Nielsen repeated his instruction to Flight 2937 to descend, giving the Tupolev crew incorrect information as to the position of the DHL plane (telling them that the Boeing was to the right of the Tupolev when it was in fact to the left).[BFU 6]

The aircraft collided at almost a right angle at an altitude of 34,890 feet (10,630 m), with the Boeing's vertical stabilizer slicing completely through Flight 2937's fuselage just ahead of the Tupolev's wings. The Tupolev exploded and broke into several pieces, scattering wreckage over a wide area. The nose section of the aircraft fell vertically, while the tail section with the engines continued, stalled, and fell. The crippled Boeing, now with 80% of its vertical stabilizer lost, struggled for a further seven kilometres (four miles) before crashing into a wooded area close to the village of Taisersdorf at a 70-degree downward angle. Each engine ended up several hundred metres away from the main wreckage, and the tail section was torn from the fuselage by trees just before impact. All 69 people on the Tupolev, and the two on board the Boeing, died.[BFU 7]

Other factors in the crash

Only one air traffic controller, Peter Nielsen of ACC Zurich, was controlling the airspace through which the aircraft were flying. The other controller on duty was resting in another room for the night. This was against the regulations, but had been a common practice for years and was known and tolerated by management. Maintenance work was being carried out on the main radar image processing system, which meant that the controllers were forced to use a fallback system.[BFU 8] The ground-based optical collision warning system, which would have alerted the controller to the pending collision approximately 2½ minutes before it happened,[BFU 9] had been switched off for maintenance; Nielsen was unaware of this.[BFU 10] There still was an aural STCA warning system, which released a warning addressed to workstation RE SUED at 21:35:00 (32 seconds before the collision); this warning was not heard by anyone present at that time, although no error in this system could be found in a subsequent technical audit; whether this audible warning is turned on or not, is not logged technically. Even if Nielsen had heard this warning, at that time finding a useful resolution order by the air traffic controller is impossible.[BFU 11]

Deviating statements in the official report

Temporary memorial at Uberlingen's Sosa Fountain.

All countries involved could add additional "deviating" statements to the official report. The Kingdom of Bahrain, Switzerland, and the Russian Federation did submit positions that were published with the official report. The USA did not submit deviating positions. The deviating statements were published verbatim as an appendix to the report by the German federal investigators.[15]

The statement by the Kingdom of Bahrain, the home country of the DHL plane, mostly agrees with the findings of the report. It says that the report should have put less emphasis on the actions of individuals and more on the faults within Skyguide's organisation and management. Bahrain's statement also mentions the lack of crew resource management in the Tupolev's cockpit as a factor in the crash.[15]

The Russian Federation states that the Russian pilots were unable to obey the TCAS advisory to climb; the advisory was given when they were already at 35500 feet while the controller wrongly stated there was conflicting traffic above them at 36000 feet. Also, the controller gave the wrong position of the DHL plane (2 o'clock instead of the actual 10 o'clock). Russia asserts that the DHL crew had a "real possibility" to avoid a collision since they were able to hear the conversation between the Russian crew and the controller.[15]

Switzerland notes that the Tupolev was about 33 metres below the flight level ordered by the Swiss controller, and still descending at 1900 feet per minute. The Swiss say that this was also a cause of the accident. Switzerland also requested that the BFU make a formal finding that the TCAS advisories would have been useful if obeyed immediately; the BFU declined to do so.[15]

Aftermath

File:Skyguide Memorial.jpg
Skyguide memorial to the aviation accident and murder of Peter Nielsen.

Nielsen needed medical attention due to traumatic stress caused by the accident.[16] At Skyguide, his former colleagues maintained a vase with a white rose over Nielsen's former workstation.[17] Skyguide, after initially having blamed the Russian pilot for the accident, accepted full responsibility and asked relatives of the victims for forgiveness.[18] On 19 May 2004, the official investigators found that managerial incompetence and systems failures were the main cause of the accident.[citation needed]

On 27 July 2006, a court in Konstanz decided that the Federal Republic of Germany should pay compensation to Bashkirian Airlines. The court found that Germany was legally responsible for the actions of Skyguide. The government appealed the ruling;[19] however, in the autumn of 2013 Bashkirian Airlines and the Federal Republic of Germany reached a silent agreement, ending the court case before a decision on the legal issues was reached.[20]

In another case before the court in Konstanz, Skyguide's liability insurance is suing Bashkirian Airlines for 2.5 million euro in damages. The case was opened in March 2008; the legal questions are expected to be difficult, as the airline has filed for bankruptcy under Russian law.[19]

A criminal investigation of Skyguide began in May 2004. On 7 August 2006, a Swiss prosecutor filed manslaughter charges against eight employees of Skyguide. The Winterthur[not in citation given] prosecutor called for prison terms of 6 to 15 months, alleging "homicide by negligence".[21] The verdict was announced in September 2007. Three of the four managers convicted were given suspended prison terms and the fourth was ordered to pay a fine. Another four employees of the Skyguide firm were cleared of any wrongdoing.[22]

Murder of Peter Nielsen

Devastated by the loss of his wife and two children aboard flight 2937, Vitaly Kaloyev, a Russian architect, held Peter Nielsen responsible for their deaths. He tracked down and stabbed Nielsen to death at his home in Kloten, near Zürich, on 24 February 2004.[17][23] The Swiss police arrested Kaloyev at a local motel shortly after, and he was sentenced to prison for the murder in 2005. He was released in November 2007 because his mental condition was not sufficiently considered in the initial sentence. After his release, Kaloyev was dubbed a "hero" in North Ossetia. In January 2008, he was appointed deputy construction minister of North Ossetia.[24]

TCAS and conflicting orders

The accident raised questions on how pilots must react when they receive conflicting orders from the TCAS and from air traffic control (ATC). TCAS was a relatively new technology at the time of the accident, having been mandatory[Note 1] in Europe since 2000.[BFU 12] Whilst the TCAS is programmed to assume that both crews will promptly follow the system's instructions, the operations manual did not clearly state that TCAS should always take precedence over any ATC commands.[BFU 13]

When a resolution advisory (RA) occurs, the pilot flying should respond immediately by direct attention to RA displays and maneuver as indicated, unless doing so would jeopardize the safe operation of the flight, or unless the flight crew can assure separation with the help of definitive visual acquisition of the aircraft causing the RA.[25] In responding to a TCAS RA that directs a deviation from assigned altitude, communicate with ATC as soon as practicable after responding to the RA. When the RA is removed, the flight crew should advise ATC that they are returning to their previously assigned clearance or should acknowledge any amended clearance issued.[25]

The TCAS Pilot's Guide was ambiguous as to whether or not TCAS advisories should take precedence over ATC instructions.[BFU 14] This ambiguity was replicated in the Tu-154 Flight Operations Manual, which contained contradictory sections. On the one hand, chapter 8.18.3.4 emphasized the role of the ATC and describes the TCAS as an "additional aid",[BFU 15] whilst chapter 8.18.3.2 forbids manoeuvers contrary to the TCAS.[BFU 16] The BFU recommended that this ambiguity should be resolved in favor of obeying TCAS advisories even when these were in conflict with ATC instructions.[BFU 17]

Prior incidents

Seventeen months before the Bashkirian Airlines-DHL collision there had already been another incident involving confusion between conflicting TCAS and ATC commands. In 2001 two Japanese airliners nearly collided with each other in Japanese skies. One of the aircraft had received conflicting orders from the TCAS and ATC; one pilot followed the instructions of the TCAS while the other did not. A collision was only averted because one of the pilots made evasive maneuvers based on a visual judgement. The aircraft missed each other by about 135 metres (443 ft), and the abrupt maneuver necessary to avert disaster left 100 occupants injured on one aircraft, some seriously.[26](pp2,176,134,22) As a consequence Japan called for measures to prevent similar incidents. However, the International Civil Aviation Organization (ICAO) did not take action until after the crash over Germany in 2002.[27][not in citation given] In addition four near misses in Europe occurred before the German disaster, because one set of pilots obeyed the air traffic controllers while the other obeyed TCAS.[citation needed] The ICAO decided to fulfill Japan's request 18 months after the Japan Airlines incident.[citation needed]

Technical solutions

Before this accident a change proposal (CP 112)[28] for the TCAS II system had been issued. This proposal would have created a "reversal" of the original warning – asking the DHL plane to climb and the Tupolev crew to descend.[BFU 18] According to an analysis by Eurocontrol this would have avoided the collision if the DHL crew had followed the new instructions and the Tupolev had continued to descend.[BFU 18] All new aircraft since March 2012 are fitted with TCAS II version 7.1 which includes this reversal logic, and existing aircraft must be upgraded before December 2015.[29]

Additionally, an automatic downlink for the TCAS – which would have alerted the controller that a TCAS advisory had been issued to the aircraft under his control, and notified him of the nature of that advisory – had not been deployed worldwide at the time of the accident.[BFU 19][not in citation given]

Recommendations after the accident

The investigation report contains a number of recommendations concerning TCAS, calling for upgrades and for better training and clearer instructions to the pilots.[BFU 20]

Notable passengers on Flight 2937

Fourteen-year-old Kirill Degtyarev created paintings from age 4 to his death and had held two public exhibitions. After his death, Ufa hosted one exhibition and Überlingen hosted another.[13]

Dramatization

The Discovery Channel Canada documentary series Mayday featured this accident in the episode titled Deadly Crossroads, which was released in 2004.[30]

The National Geographic Channel documentary series Seconds From Disaster featured this mid-air collision in the episode entitled Collision at 35,000 feet release in 26 September 2011.

"Flug in die Nacht – Das Unglück von Überlingen" (2009), ("Flight into the night – the accident at Überlingen") produced by German and Swiss TV stations SWR and SF, is a motion picture based on the crash and the subsequent killing of the air traffic controller.[31]

The Smithsonian Channel's "Air Disasters" documentary series, featured this accident in the second season's third episode titled "System Breakdown", released in 2011. Available on Netflix as of Oct. 2015.

See also

Notes

  1. TCAS was mandatory for aircraft with a maximum certified take-off weight of over 30 tonnes or a seating capacity of over thirty passengers. Both aircraft involved in this accident met the criteria for mandatory TCAS installation.

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
  4. "Mid-air collision of 1 July 2002: sequence of events" (Skyguide). Archived September 27, 2011 at the Wayback Machine
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 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. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. "Children's holiday party on doomed plane." CNN. 4 July 2002. Retrieved on 28 April 2010. Archived May 12, 2010 at the Wayback Machine
  12. http://www.newsru.com/world/02jul2002/aviacrash.html
  13. 13.0 13.1 "Deadly Crossroads," Mayday
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 15.3 Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. 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.
  23. "Swiss air crash controller killed." CNN. Wednesday 25 February 2004. Retrieved on 29 January 2010.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 http://www.faa.gov/documentLibrary/media/Advisory_Circular/TCAS%20II%20V7.1%20Intro%20booklet.pdf
  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. Change proposal CP112E
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. IMDb
  31. Lua error in Module:WikidataCheck at line 28: attempt to index field 'wikibase' (a nil value). Flug in die Nacht – Das Unglück von Überlingen at IMDb

Official report

Lua error in package.lua at line 80: module 'strict' not found.

  1. Section 1.1 "History of the flights", page 6
  2. Section 3.2 "Causes", page 110
  3. Section 4 "Safety Recommendations", pages 111-113
  4. Section 1.16.2 "ACAS/TCAS II analysis", page 34
  5. Section 2.7 "Analysis summary", pages 104-106
  6. Section 2.4.1 "ATC Zurich", page 76
  7. Section 1.2 "Injuries to persons", page 9
  8. Section 1.17.1 "ATC Zurich", pages 35-42
  9. Section 2.6.1.4 "Warning systems", page 88
  10. page 89
  11. page 89
  12. page 45
  13. page 103: "Paragraph 6.1 of the TCAS Pilot's Guide states "TCAS 2000 is intended as a back-up to visual collision avoidance, application of 'right-of-way' rules, and ATC separation services", and leaves a degree of ambiguity over the interpretation of the term 'back-up'."
  14. page 80 "The wording "TCAS is a backup to the ATC system..." could be interpreted that ATC takes priority to TCAS"
  15. page 53 "For the avoidance of in-flight collisions is the visual control of the situation in the airspace by the crew and the correct execution of all instructions issued by the Air Traffic Controller to be viewed as the most important tool. TCAS is an additional instrument which ensures the timely determination of oncoming traffic, the classification of the risk and, if necessary, planning of an advice for a vertical avoidance manoeuvre." - TU154M Flight Operations Manual
  16. page 103
  17. page 111 "Safety Recommendation 18/2003"
  18. 18.0 18.1 page 35
  19. page 50
  20. Section 4 "Safety Recommendations", pages 111-113

External links


On conflicting orders