2002 Überlingen mid-air collision
Fatal collision over Germany (July 2002) From Wikipedia, the free encyclopedia
Fatal collision over Germany (July 2002) From Wikipedia, the free encyclopedia
On 1 July 2002, BAL Bashkirian Airlines Flight 2937, a Tupolev Tu-154 passenger jet, and DHL International Aviation ME Flight 611, a Boeing 757 cargo jet, collided in mid-air over Überlingen, a southern German town on Lake Constance, near the Swiss border. All of the passengers and crew aboard both planes were killed, resulting in a total death toll of 71.[3]
Accident | |
---|---|
Date | 1 July 2002 |
Summary | Mid-air collision |
Site | Überlingen, Baden-Württemberg, Germany 47°46′42″N 9°10′26″E |
Total fatalities | 71 |
Total survivors | 0 |
First aircraft | |
RA-85816, the aircraft involved in the accident seen in March 2002 | |
Type | Tupolev-Tu-154M |
Operator | BAL Bashkirian Airlines |
IATA flight No. | V92937 |
ICAO flight No. | BTC2937 |
Call sign | BASHKIRIAN 2937[Note 1] |
Registration | RA-85816 |
Flight origin | Domodedovo International Airport, Moscow, Russia |
Destination | Barcelona El Prat Airport, Barcelona, Spain |
Occupants | 69 |
Passengers | 60 |
Crew | 9 |
Fatalities | 69 |
Survivors | 0 |
Second aircraft | |
A9C-DHL, the aircraft involved in the accident seen in June 2002, four weeks prior | |
Type | Boeing 757-23APF |
Operator | DHL International Aviation ME |
IATA flight No. | ES611 |
ICAO flight No. | DHX611 |
Call sign | DILMUN 611 |
Registration | A9C-DHL[Note 2] |
Flight origin | Bahrain International Airport, Manama, Bahrain[1][2] |
Stopover | Orio al Serio Airport, Bergamo, Italy |
Destination | Brussels Airport, Brussels, Belgium |
Occupants | 2 |
Crew | 2 |
Fatalities | 2 |
Survivors | 0 |
The official investigation by the German Federal Bureau of Aircraft Accident Investigation (German: Bundesstelle für Flugunfalluntersuchung -BFU) identified the main cause of the collision to be a number of shortcomings on the part of the Swiss air traffic control (ATC) service in charge of the sector involved, as well as ambiguities in the procedures regarding the use of the traffic collision avoidance system (TCAS) on board.[4]: 110 [BFU 1]
On 24 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 and architect whose wife and two children had been killed in the accident.[5][6][7]
Flight BTC2937 was a chartered flight from Moscow, Russia, to Barcelona, Spain, carrying 60 passengers and 9 crew.[8] Forty-six of the passengers were Russian schoolchildren from the city of Ufa, in Bashkortostan, on a school trip organised by the local UNESCO committee to the Costa Daurada beach area of Catalonia.[9][1][10][11] Most of the parents of the children were high-ranking officials in Bashkortostan.[12] One of the fathers was the head of the local UNESCO committee.[13] They travelled on an overnight train to Moscow and arrived on 29 June, then, as their driver accidentally took them to the wrong airport, they missed their original flight. They remained there until 1 July in order to find the arranged charter flight. Flight 2937 departed at Moscow Domodedovo Airport at 22:48 Moscow Time (18:48 UTC) bound for Barcelona International Airport (now Josep Tarradellas Barcelona–El Prat Airport).[14]
The aircraft, a 1995-built Tupolev Tu-154M registered as RA-85816, was first delivered to BAL Bashkirian Airlines before being sold to Transeuropean Airlines in 1998. The aircraft was once again sold to Shaheen Air in 1999 before being returned to BAL Bashkirian Airlines in January 2002.
The flight was piloted by an experienced Russian crew: 52-year-old Captain Alexander Mikhailovich Gross (Russian: Александр Михайлович Гросс) and 40-year-old First Officer Oleg Pavlovich Grigoriev (Russian: Олег Павлович Григорьев). The captain had more than 12,000 flight hours (including 4,918 hours on the Tu-154) to his credit. Grigoriev, the chief pilot of Bashkirian Airlines, had 8,500 hours of flying experience (with 4,317 hours on the Tu-154) and his task was to evaluate Captain Gross's performance throughout the flight.[15]
The 41-year-old seasoned pilot, Murat Akhatovich Itkulov (Russian: Мурат Ахатович Иткулов), with close to 7,900 flight hours (4,181 of them on the Tu-154), who was normally the first officer, did not officially serve on duty, because this was the captain's assessment flight; 50-year-old Sergei Gennadyevich Kharlov (Russian: Сергей Геннадьевич Харлов), a flight navigator with approximately 13,000 flight hours (including 6,421 hours on the Tu-154), and 37-year-old Flight Engineer Oleg Irikovich Valeev (Russian: Олег Ирикович Валеев), who had almost 4,200 flight hours (all of which were on the Tu-154), joined the three pilots in the cockpit.[15]
DHL International Aviation ME Flight 611, a Boeing 757-23APF cargo aircraft built in 1990 and first delivered to Zambia Airways as 9J-AFO before being sold to Gulf Air as VH-AWE[16] in late 1993. It was then sold to SNAS Aviation in 1996 under the same registration. The aircraft was then sold to European Air Transport as OO-DLK in 2000 until 2002 before being sold once again to DHL International as A9C-DHL. The flight was being flown by two Bahrain-based pilots,[17][18] 47-year-old British Captain Paul Phillips and 34-year-old Canadian First Officer Brant Campioni.[19] Both pilots were very experienced — Phillips had logged close to 12,000 flight hours (including 4,145 hours on the Boeing 757) and Campioni had accumulated more than 6,600 flight hours, with 176 of them on the Boeing 757. Campioni had also previously worked as an air cadet and corporal in the Canadian Military Engineers.[20] At the time of the accident, the aircraft was en route from Bahrain International Airport in Manama, Bahrain, to Brussels Airport in Brussels, Belgium, with a stop at Orio al Serio Airport in Bergamo, Italy, and departed Bergamo at 23:06 CEST (21:06 UTC).[1][2]
The airspace was controlled from Zürich, Switzerland, by the Swiss federal airspace control Skyguide. Air traffic controller Peter Nielsen, the only controller handling the airspace, was burdened with working two workstations at the same time.
At around 23:20 CEST (21:20 UTC), DHL Flight 611 reported to the area control center responsible for southern German airspace. Nielsen then instructed Flight 611 to climb from flight level 260 (26,000 ft (7,900 m)) to flight level 320 (32,000 ft (9,800 m)). Flight 611 requested permission to continue the climb to flight level 360 (36,000 feet (11,000 m)) to save fuel. Permission was granted by Nielsen, after which Flight 611 reached the desired altitude at 23:29:50. Meanwhile, Bashkirian Flight 2937 contacted Nielsen at 23:30, also at flight level 360. Nielsen acknowledged the flight, but did not assign a different altitude to either aircraft. This meant that both were now at the same altitude and on conflicting courses.
At 23:34:42 CEST (21:34:42 UTC), less than a minute before the crash, Nielsen realized the danger and contacted Flight 2937, instructing the pilot to descend to flight level 350 (1000 ft lower) to avoid collision with crossing traffic (Flight 611).[8] Seconds after the crew of Flight 2937 initiated this descent, their TCAS instructed them to climb, while at about the same time the TCAS on Flight 611 instructed the crew of that aircraft to descend.[4]: 111–113 [BFU 2] Had both aircraft followed those automated instructions, the collision would not have occurred.[4]: 34 [BFU 3]
Flight 611's pilots followed their TCAS instructions and initiated a descent, but could not immediately inform Nielsen because the controller was dealing with Flight 2937. The crew of Flight 2937, already descending as instructed by Nielsen,[4]: 104–106 [BFU 4] disregarded their TCAS instruction to climb. Thus, both planes were now descending.
Unaware of the TCAS-issued alerts, Nielsen repeated his instruction to Flight 2937 to descend, giving the crew incorrect information as to the position of the DHL plane (telling them that the plane was to the right when it was in fact to the left).[4]: 76 [BFU 5] About eight seconds before the collision, Flight 611's descent rate was about 12 m/s (2,400 ft/min), not quite as rapid as the 13 to 15 m/s (2,500 to 3,000 ft/min) range advised by the TCAS.
Flight 611, responding to the developing situation, increased its descent rate.[4]: 6–9 [BFU 6][BFU 7] Eight seconds before the collision, Flight 2937's crew became aware of the situation when they gained visual sight of Flight 611 incoming from the left, and, two seconds before the collision, obeyed their TCAS instruction and attempted to put the aircraft into a climb.
By then the collision was inevitable. The aircraft collided at 23:35:32 CEST (21:35:32 UTC), at almost a right angle, at an altitude of 10,630 m (34,890 ft), with Flight 611's vertical stabilizer slicing completely through Flight 2937's fuselage just ahead of the wings. Flight 2937 broke into several pieces, scattering wreckage into the Brachenreute neighborhood over a wide area.[8] The nose section of the aircraft fell vertically, while the tail section with the engines continued, stalled, and fell.
Flight 611, now with 80% of its vertical stabilizer lost, struggled for a further 7 kilometres (4.3 mi; 3.8 nmi) before crashing into a wooded area close to the village of Taisersdorf at a 70° downward angle. Each engine ended up several hundred meters away from the main wreckage, and the tail section was torn from the fuselage by trees just before impact.[4]: 19–33 [BFU 8] All 69 people onboard Flight 2937 and both crew members on board Flight 611 died.[4]: 9 [BFU 9][8]
Only one ATC, Peter Nielsen of ACC Zurich, was controlling the airspace through which the aircraft were flying.[8] The other controller on duty was resting in another room for the night. This was against Skyguide's regulations, but had been a common practice for years and was known and tolerated by management.[8] 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.[4]: 35–42 [BFU 10]
The ground-based optical collision warning system, which would have alerted the controller to the pending collision about 2+1⁄2 minutes before it happened,[4]: 88 [BFU 11] had been switched off for maintenance.[8] Nielsen was unaware of this.[4]: 89 An aural short-term conflict alert warning system released a warning addressed to workstation RE SUED at 23: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; however, whether or not this audible warning is functional is not something that is technically logged. Even if Nielsen had heard this warning, at that time finding a useful resolution order by the ATC was impossible.[4]: 89
All countries involved could add additional "deviating" statements to the official report. Bahrain, Switzerland, and Russia did submit positions that were published with the official report. The deviating statements were published verbatim as an appendix to the report by the BFU investigators.[21]
The statement by 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.[21]
Russia states that the Russian pilots were unable to obey the TCAS advisory to climb; the advisory was given when they were already at 10,800 m (35,500 ft), while the controller wrongly stated conflicting traffic was above them at 11,000 m (36,000 ft). Also, the ATC gave the wrong position of the DHL plane (2 o'clock instead of the actual 10 o'clock).[22] 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.[21]
Switzerland notes that the Tupolev was about 33 m (108 ft) below the flight level ordered by the Swiss controller, and still descending at 580 m/min (1,900 ft/min). 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.[21]
Nielsen needed medical attention due to traumatic stress caused by the accident.[23] At Skyguide, his former colleagues maintained a vase with a white rose over Nielsen's former workstation.[24] Skyguide, after initially having blamed the Russian pilot for the accident, accepted full responsibility and asked relatives of the victims for forgiveness.[25]
Skyguide paid compensation to the families of the dead children; the compensation amount was about CHF 30,000 ($34,087) to CHF 36,000. The Swiss Federal Court turned down appeals from some relatives for higher compensation in 2011.[26]
On 27 July 2006, a court in Konstanz decided that 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,[27] but in late 2013, Bashkirian Airlines and Germany reached a tacit agreement, ending the court case before a decision on the legal issues was reached.[28]
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.[27][needs update]
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 prosecutor called for prison terms up to 15 months if found guilty.[29] 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.[22] Another four Skyguide employees were cleared of any wrongdoing.[30]
Devastated by the death of his wife and two children aboard flight 2937, Vitaly Kaloyev, a Russian architect, held Peter Nielsen personally responsible for their deaths.[22] He tracked down and stabbed Nielsen to death, in the presence of Nielsen's wife and three children, at his home in Kloten, near Zürich, on 24 February 2004.[24][31] The Swiss police arrested Kaloyev at a local motel shortly afterward, and in 2005, he was sentenced to eight years for manslaughter. However, his sentence was later reduced after a Swiss judge ruled that he had acted with diminished responsibility.[32]
He was released in November 2007, having spent less than four years in prison, because his mental condition was not sufficiently considered in the initial sentence. In January 2008, he was appointed deputy construction minister of North Ossetia. Kaloyev was treated as a hero back home, and expressed no regret for his actions, instead blaming the murder victim for his own death.[32] In 2016, Kaloyev was awarded the highest state medal by the government, the medal "To the Glory of Ossetia".[22] The medal is awarded for the highest achievements, improving the living conditions of the inhabitants of the region, educating the younger generation, and maintaining law and order.[33]
The accident raised questions as to how pilots must react when they receive conflicting orders from TCAS and ATC. TCAS was a relatively new technology at the time of the accident, having been mandatory[Note 3] in Europe since 2000.[4]: 45 When TCAS issues a resolution advisory (RA), the pilot flying should respond immediately by directing attention to RA displays and maneuvering as indicated, unless doing so would jeopardise 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.[34]
In responding to a TCAS RA that directs a deviation from assigned altitude, the flight crew should 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.[34]
While 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.[4]: 103 [BFU 12] The manual described TCAS as "a backup to the ATC system", which could be wrongly interpreted to mean that ATC instructions have higher priority.[4]: 80 [BFU 13] This ambiguity was replicated in the Tu-154 Flight Operations Manual, which contained contradictory sections. On the one hand, chapter 8.18.3.4 emphasised the role of ATC and describes TCAS as an "additional aid",[4]: 53 [BFU 14] while chapter 8.18.3.2 forbade manoeuvers contrary to TCAS.[4]: 103 The BFU recommended that this ambiguity should be resolved in favor of obeying TCAS advisories even when these were in conflict with ATC instructions.[4]: 111 [BFU 15]
About a year before the Bashkirian Airlines-DHL collision, another incident had occurred involving confusion between conflicting TCAS and ATC commands. In 2001, two Japanese airliners nearly collided with each other in Japanese airspace. One of the aircraft had received conflicting orders from TCAS and ATC; one pilot followed the instructions of TCAS, while the other did not. A collision was only averted because one of the pilots made evasive maneuvers based on a visual judgment. The aircraft missed each other by about 135 m (443 ft), and the abrupt maneuver necessary to avert disaster left 100 occupants injured on one aircraft, some seriously.[35]: 2, 176, 134, 22 Japan published its report 11 days after the Überlingen accident, called in it on the International Civil Aviation Organization (ICAO) to make it clear that TCAS advisories should always take precedence over ATC instructions. ICAO accepted this recommendation and amended its regulations in November 2003.[36]
Before this accident, a change proposal (CP 112)[37] 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.[4]: 35 According to an analysis by Eurocontrol, this would have avoided the collision if the DHL crew had received and followed the new instructions and the Tupolev had continued to descend.[4]: 35 All TCAS II equipped aircraft have been upgraded to support RA reversal.[38]
Additionally, an automatic downlink for TCAS, which would have alerted the controller that a TCAS advisory had been issued to the aircraft under their control, and notified them of the nature of that advisory, had not been deployed worldwide at the time of the accident.[4]: 50
The investigation report contains a number of recommendations concerning TCAS, calling for upgrades, better training and clearer instructions to the pilots.[4]: 111–113 [BFU 16] The TCAS II system was redesigned, with its ambiguous "Adjust Vertical Speed" RA voice command changed to "Level-Off", to increase proper responses from pilots.[39][40]
In the U.S. off-Broadway play My Eyes Went Dark, which opened 7 June 2017 and closed 2 July, playwright and director Matthew Wilkinson tells Kaloyev's story, which featured, among other characters, Declan Conlon as Kaloyev and Thusitha Jayasundera as his wife. It played at 59E59 Theaters in New York City.[citation needed]
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.