On 1 July 2002, a Bashkirian Airlines Tupolev Tu-154M and a DHL Boeing 757-200 collided near Überlingen, Germany, while both were under the control of Zurich ACC. As of 6 November 2026, the investigation is long closed: the German BFU published its final report in May 2004, identifying an ATC instruction given too late, the Tu-154 crew's response against their TCAS resolution advisory, and systemic failures in night staffing, procedures, and technical availability.
Key facts
| Date and local time | 1 July 2002, 23:35:32 local time, 21:35:32 UTC |
| Aircraft type | Tupolev Tu-154M and Boeing 757-200 |
| Registration | RA-85816 and A9C-DHL |
| Operator and type of operation | Bashkirian Airlines passenger flight 2937 and DHL cargo flight 611 |
| Route or purpose of the flight | Moscow-Domodedovo to Barcelona, and Bergamo to Brussels |
| Phase of flight | Cruise |
| People on board | 71 in total |
| Outcome | Mid-air collision, both aircraft destroyed, 71 fatalities |
| Investigating authority and case number | German BFU, AX001-1-2/02 |
| Report status | Final report published, May 2004 |
What happened
Shortly before the collision, both aircraft were level at FL 360 and converging in Zurich ACC airspace. The BFU reconstructed the sequence from FDR, CVR, stored TCAS data, recorded RT, and radar data.
- Traffic becomes relevant: Between about 21:33 and 21:34:41 UTC, the Tu-154 crew discussed the traffic shown on the TCAS display and tried to work out where it was. At 21:34:42, TCAS generated a traffic advisory, TA, and the crew called out the traffic.
- ATC gives a late descent: At 21:34:49, seven seconds after the TA, Zurich ACC instructed the Tu-154 to expedite descent to FL 350 because of crossing traffic. The Tu-154 crew started to act on that instruction immediately.
- TCAS gives opposite commands: At 21:34:56, TCAS generated coordinated resolution advisories in both aircraft. The Tu-154 received a climb RA, while the Boeing 757 received a descend RA.
- The two crews diverge: The DHL crew followed the RA and descended. In the Tu-154, the copilot called out that TCAS said climb, but the pilot-in-command, an instructor in the right seat, replied that ATC was guiding them down. The Tu-154 continued descending.
- ATC reinforces the wrong path: At 21:35:03, while the Tu-154 crew were still discussing the conflict, the controller repeated the instruction to descend. According to the BFU, that repeated instruction confirmed the crew in their decision to keep descending.
- Collision: At 21:35:32 UTC, the aircraft collided near Überlingen. Both crashed to the ground north of the town.
What the investigators found
The BFU identified two immediate causes. First, the controller did not notice the imminent loss of separation in time, and the instruction for the Tu-154 to descend came so late that the required separation from the 757 could no longer be ensured. Second, the Tu-154 crew followed the ATC descent instruction and continued to do so after TCAS advised them to climb, which was contrary to the generated RA.
The report also identified systemic causes. The BFU found that the integration of ACAS/TCAS II into the aviation system was insufficient, and that ICAO, national, manufacturer and operator procedures were not standardized and were partly incomplete or contradictory. In simple terms, the technical logic of TCAS said one thing, but the rule set and training material did not always say it clearly enough in the same place and in the same words.
At Zurich ACC that night, the situation was degraded. Planned maintenance work affected several systems. The visual STCA, short term conflict alert on the screen, was unavailable, and after 21:23 the direct telephone lines to neighboring ATC units were no longer available. The BFU also found that nearby control units had not been informed about the planned sectorization work.
Staffing was another major part of the finding. During the night shift, one controller was handling all traffic control tasks while the other controller was resting. The BFU concluded that management and quality assurance had not ensured continuous staffing of all open workstations at night, and had tolerated for years a practice in which one controller worked alone during low traffic periods.
The chain of events
This accident was not one single mistake. It was a chain in which degraded ATC support, late conflict recognition, ambiguous procedural doctrine, and a crew decision under time pressure all lined up at the same moment.
- Late conflict picture: The controller did not detect the separation problem early enough. Once the late descent instruction was issued, there was almost no time margin left for a safe ATC solution.
- Reduced safety net: The visual STCA was unavailable, direct coordination phone lines to neighboring units were out, and maintenance work was underway in the control room. Those barriers were supposed to help a controller see and solve a conflict sooner.
- Single-person operation: One controller was working while the other rested. That meant one person had to scan, coordinate, communicate, and manage degraded systems at the same time.
- Conflicting cues: The Tu-154 crew received an ATC descent instruction, then a contrary TCAS climb RA. In a high-authority environment, the controller’s instruction carried strong weight, especially because it arrived first.
- Repeated ATC instruction: The second descent instruction from ATC reinforced the crew’s choice to continue descending. The BFU treated that as part of why the crew did not switch to the TCAS command.
- Unclear RA doctrine: The BFU found the international and operator procedures of the time were not clear enough about immediate, unreserved RA compliance and prompt radio reporting. That matters because TCAS is designed as the last line of defence, not one cue among many.
What to learn from it
A student pilot is unlikely to face this exact high-altitude airline scenario, but the training value is very direct. It sits at the junction of Communications, Human Performance, Air Law, and operational discipline: know which instruction has priority, act promptly, and tell ATC clearly what you are doing.
- Follow the RA: The BFU’s safety recommendation after the accident was that pilots should obey a TCAS RA regardless of contrary ATC instruction, unless compliance would be more dangerous. The practical lesson is simple: if TCAS gives a resolution advisory, it is no longer a discussion about preference. It is an immediate maneuver.
- Report it on the radio: The BFU stressed that ATC can only stop issuing conflicting vertical instructions if the pilot reports the RA in time. In training terms, this is where standard phraseology matters: a short, clear call such as reporting a TCAS RA tells the controller why you are not complying with the last clearance.
- Expect authority pressure: The Tu-154 crew had a human-factors problem as well as a technical one. ATC had spotted the conflict, repeated the descent, and appeared to offer a solution. Pilots need procedures strong enough to override that pressure when the collision-avoidance system commands the opposite.
- Know the last safety net: TCAS is designed as the last line of defence when separation has already broken down or is about to. That means it must be treated differently from a traffic call or a suggestion. You are not weighing it against normal vertical control, you are executing the escape plan built into the system.
Train what would have broken the chain
These learning goals from the PPL syllabus cover the points above. Train each one with lessons, radio scenarios and practice questions.
- 1Air Law 2.b.ii.4
The student should be able to explain the difference between instructions and information from the FIS and those from the ATC (e.g., traffic information vs. avoidance recommendation vs. avoidance instruction).
- 2Air Law 2.b.i.2
The student should be able to state their rights and obligations regarding ATC communication, particularly read-backs, compliance, and if necessary, refusal to follow instructions.
- 3Human Performance and Limitations 2.b.ii.6
The student should be able to indicate that in situations of high workload or emergencies, the error rate increases.
- 4Air Law 2.b.i.3
The student should be able to describe the role and tasks of ATC regarding separation.
Train it before you need it
Create a free account to work through these learning goals with lessons, radio scenarios and practice questions.
