The Überlingen Mid-Air, the TCAS Resolution Advisory That One Crew Ignored, and the Rule That Has to Be Absolute

On July 1, 2002, two aircraft collided at flight level 360 over Lake Constance, Germany. Seventy-one people died - including 45 children - because one flight crew followed a human voice on the radio instead of a computed command from the collision avoidance system already working to keep them apart. The Überlingen accident is the definitive case study in why compliance with a TCAS Resolution Advisory is non-negotiable.

How TCAS Actually Works - And Why Both Aircraft Must Comply

Most pilots understand the Traffic Collision Avoidance System at a surface level: traffic alerts, colored diamonds on the display, climb and descent calls. The engineering underneath those prompts is what makes the compliance rule so important.

TCAS operates independently of air traffic control - not in coordination with it, not as a backup to it. Your aircraft’s TCAS unit interrogates the Mode C and Mode S transponders of nearby aircraft, listens to their altitude replies, and builds a three-dimensional picture of where every aircraft is heading. When it detects a collision threat within approximately 35 seconds to impact, it issues a Resolution Advisory (RA).

A Resolution Advisory is a command. Climb. Descend. Reduce Climb. Maintain Vertical Speed. The vertical speed indicator displays a red arc (the range to avoid) and a green arc (what to fly). The voice is unambiguous: “Climb, climb now.” “Descend, descend now.”

Here is the piece that pilots must fully internalize: before either crew hears anything, both aircraft’s TCAS units have already communicated with each other via Mode S datalink and coordinated their commands. If you receive a climb advisory, the other aircraft is receiving a descend advisory. The commands are complementary by design. The system has already solved the geometry.

That coordination only works if both crews execute their half. One aircraft following its RA and one aircraft not following its RA is worse than both crews ignoring TCAS entirely. If you follow your advisory and the other aircraft doesn’t, you may be flying toward each other rather than apart. The other crew has committed to a trajectory based on the assumption that you will do what your system told you to do.

The Conditions Over Lake Constance on the Night of the Collision

SKYGUIDE, the Swiss air traffic control agency, was managing traffic over Lake Constance through the Zurich Area Control Center. On the night of July 1, 2002, controller Peter Nielsen was working alone - a second controller was on break - while a maintenance crew performed work on the short-term conflict alert system, an automated tool that flags developing conflicts. That backup was not fully operational.

Nielsen was managing traffic from two sectors simultaneously, under conditions the post-accident investigation by the German Federal Bureau of Aircraft Accident Investigation found to represent a significant increase in workload with reduced safety margins.

Two aircraft were converging in his sector at FL360:

Bashkirian Airlines Flight 2937 - a Tupolev Tu-154M charter operating from Ufa, Russia to Barcelona, Spain. On board: 60 passengers and 9 crew. Forty-five of the passengers were children between 7 and 16 years old, traveling to a summer camp in Spain on a cultural exchange program.
DHL Flight 611 - a Boeing 757-200 freighter with a crew of two: Captain Paul Phillips and First Officer Brant Campioni.

What the TCAS System Did - And What the Crew Did Instead

Nielsen identified the conflict and radioed the Bashkirian crew with an instruction to descend to FL350, advising conflicting traffic to their right. What he did not know was that TCAS had already issued coordinated RAs to both aircraft.

The DHL crew received a climb advisory. They responded immediately and correctly - advanced thrust and began climbing.

The Bashkirian crew received a descend advisory. Almost simultaneously, they heard Nielsen’s voice instructing them to descend. In that moment, the RA and the controller instruction pointed in the same direction. The crew started descending.

Then TCAS recalculated.

The moment the DHL 757 began climbing, the geometry changed. With the DHL aircraft climbing and the Bashkirian aircraft descending, the two were now converging vertically from opposite directions. TCAS updated its advisory to the Bashkirian crew: climb. The green arc moved. The voice command reversed.

The Bashkirian crew did not follow the updated advisory.

The crew remained focused on Nielsen’s radio instruction. Nielsen, with no visibility into what TCAS had issued and unaware the DHL aircraft had begun climbing, continued transmitting vectors. He was solving the conflict the way controllers solve conflicts - with voice. The automated systems had already moved past that point.

At 21:35 UTC, the aircraft collided over the town of Owingen, near Überlingen in Baden-Württemberg, Germany. The vertical stabilizer of the DHL 757 cut through the fuselage of the Bashkirian Tu-154. Both aircraft broke apart. Debris came down over farmland and forest near the shore of Lake Constance.

Seventy-one people died. Forty-five of them were children.

Why the Bashkirian Crew Made That Choice

The investigation was careful not to assign simple blame. Several factors converged.

Russian civil aviation regulations at the time did not clearly establish the TCAS priority hierarchy that Western operators had trained for years to follow. The Bashkirian crew may not have understood that a TCAS RA supersedes a controller instruction - because their training environment had not made that unambiguous.

The controller was simultaneously an authority figure and a source of information the crew had no reason to distrust. They had been following his vectors correctly. When the RA and the controller instruction briefly aligned, following the controller felt consistent with proper procedure. When the advisory updated and reversed, the controller’s voice was still in their headsets.

The DHL crew - Captain Paul Phillips and First Officer Brant Campioni - did everything correctly. They followed their climb advisory without deviation, executed precisely what the system was designed to produce, and died in the collision having done their jobs exactly as trained.

Why This Matters for Every Pilot Flying TCAS-Equipped Aircraft

The Überlingen accident has direct bearing on anyone flying in airspace where TCAS is operating.

Controllers cannot see Resolution Advisories. They see your transponder return and a radar picture that updates every few seconds. TCAS updates its collision geometry approximately once per second, with full three-dimensional situational awareness of both aircraft’s actual flight paths. That calculation cannot be replicated by any human in any facility within the available time window. The controller is not inadequate - the controller is simply working with less information, updated less frequently, in a more complex cognitive environment.

When a TCAS RA fires, the other aircraft has already committed to its half of the maneuver. That crew is moving on the assumption that you will move as coordinated. Substituting a controller instruction for the computed advisory doesn’t just affect your aircraft - it invalidates the other aircraft’s maneuver.

The ICAO standard, the FAA standard, and every credible airline training program state the same rule: when a TCAS RA fires, you follow it. Immediately. Without waiting for controller clearance. Without asking permission.

The required phraseology is “TCAS RA” - key the mic, state it, and then fly the advisory. You do not hold for acknowledgment. You do not say standby. You fly it, and you tell the controller what you’re doing as you do it.

What Changed After Überlingen

Following the accident, ICAO revised its TCAS standards. TCAS II Version 7.1 introduced improvements including “Increase Climb” and “Increase Descent” commands, providing more explicit guidance when an initial advisory is not being followed adequately. Global training requirements were updated to mandate simulator scenarios involving RAs in recurrent training for air transport pilots.

These were meaningful changes. But aviation human factors professionals consistently note that the core lesson from Lake Constance was not a software gap. It was an authority problem. Pilots are trained from their first radio contact to treat the controller as the authority. Recalibrating that instinct to recognize when the panel outranks the frequency requires training that is deliberate, durable, and reinforced repeatedly.

The data on TCAS compliance is unambiguous: midair collision risk in TCAS-equipped airspace dropped dramatically after the mandate. The system works when both crews execute. Überlingen is the outlier that proves the rule by violating it.

The Aftermath

The investigation’s findings were critical of SKYGUIDE’s institutional practices: understaffing, inadequate procedures for single-controller overnight operations, and the decision to take the short-term conflict alert system offline without compensating safeguards. The German Federal Bureau of Aircraft Accident Investigation found systemic failures at multiple levels of the organization. The proximate cause was the Bashkirian crew’s failure to follow the updated RA - but the investigation documented the institutional conditions that created the environment in which that failure occurred.

Peter Nielsen returned to work while the investigation was underway. On February 24, 2004 - nineteen months after the collision - he was killed at his home in Zurich. Vitaly Kaloyev, a Russian architect who had lost his wife and two children aboard Bashkirian Flight 2937, had traveled to Switzerland seeking accountability for the deaths of his family. Kaloyev served a prison sentence and was subsequently released and returned to Russia.

Every person in this story was caught inside systems larger than any individual. A controller working under conditions he didn’t create. A crew flying under training standards that left them unprepared for the one moment requiring absolute clarity. Families who had no framework for any of it.

The technology performed exactly as designed. Both RAs fired correctly. The coordination was complete. One aircraft broke the system.

Key Takeaways

TCAS RAs are not advisories in the colloquial sense - they are coordinated commands, pre-solved between both aircraft’s systems before either crew hears anything. Compliance is mandatory.
A controller cannot see issued RAs and cannot know the other aircraft has already begun maneuvering. Following a controller’s conflicting instruction does not solve the conflict - it breaks the coordination already underway.
When an RA fires: respond immediately, call “TCAS RA” on frequency, fly the advisory, and inform the controller. Do not wait for clearance.
The Überlingen collision on July 1, 2002 killed 71 people - 45 of them children - because one crew prioritized a human voice over an updated climb advisory while the other aircraft was already climbing.
TCAS II Version 7.1 and updated recurrent training requirements followed the accident, but the primary lesson remains a human factors problem: authority hierarchy in the cockpit must be trained explicitly, repeatedly, and to the point of instinct.