TCAS II, the Uberlingen Midair Collision of Two Thousand Two, and the Resolution Advisory Rule Every Pilot Needs to Know Before They Ever Hear Traffic Traffic in the Headset

On July 1, 2002, 71 people died above southern Germany when the crew of Bashkirian Airlines Flight 2937 followed an air traffic controller’s instruction instead of a TCAS Resolution Advisory. Both collision avoidance computers had functioned correctly - the architecture that should have separated the two aircraft was broken by a single human decision made in the final seconds before impact. Understanding why TCAS Resolution Advisory compliance is absolute is the most critical thing any pilot flying in controlled airspace can know.

The Uberlingen Midair Collision: What Happened

At 36,000 feet above southern Germany, a Bashkirian Airlines Tupolev 154 and a DHL Boeing 757 were converging at a combined closure speed approaching 600 knots. Each aircraft carried a TCAS II unit. Each unit generated a Resolution Advisory. The Tupolev’s system commanded a climb. The Boeing’s system commanded a descent. The geometry was solved.

At nearly the same moment, Swiss air traffic controller Peter Nielsen radioed Bashkirian Flight 2937 and instructed the crew to descend. The crew descended. The DHL crew, meanwhile, had already initiated their own descent in compliance with their Resolution Advisory.

Both aircraft were now descending. The paired solution the computers had calculated no longer held. The aircraft collided. Seventy-one people were killed.

The History Behind TCAS: Why Automated Collision Avoidance Became Mandatory

The push for automated airborne collision avoidance began in 1978 after Pacific Southwest Airlines Flight 182. A Boeing 727 collided with a Cessna 172 over San Diego in clear daylight, killing 144 people. Both aircraft had valid clearances. Radar separation failed at the critical moment.

When two aircraft can occupy the same piece of sky simultaneously while both operating legally, radar and radio alone cannot solve the problem. The FAA spent the 1980s developing a system with industry - one that did not depend on ground controllers, did not depend on radio communication, and could function autonomously in the final seconds before a collision.

The result was TCAS II, which became mandatory for commercial air carrier operations in United States airspace in 1993. Europe followed. By the late 1990s it was essentially universal on large aircraft worldwide.

How TCAS II Works: From Traffic Advisory to Resolution Advisory

TCAS II interrogates the Mode C and Mode S transponders of nearby aircraft on radio frequencies around 1,000 MHz. Every aircraft with a transponder is continuously broadcasting its identity and altitude. TCAS reads those broadcasts, builds a three-dimensional picture of surrounding traffic, calculates closing speeds, and projects where those flight paths go.

The system produces two distinct types of output - and they are not the same thing.

A Traffic Advisory is awareness. When TCAS detects traffic within roughly 20 to 48 seconds of a projected close approach, the crew hears “traffic, traffic” and an amber symbol appears on the display. This is information. The system is saying: look around, be ready.

A Resolution Advisory is a command. When TCAS calculates that the conflict is critical - typically within 15 to 35 seconds of a projected collision - it directs a specific vertical maneuver: climb, climb, descend, descend, increase climb, reduce descent. The aural alert is unmistakable. The display upgrades to red. The system is not providing information to evaluate. It is issuing a directive.

Why TCAS Pairs Advisories Between Aircraft

When two TCAS-equipped aircraft are converging, their systems are not operating independently. They communicate through the Mode S data link, exchanging coordination messages in milliseconds. One aircraft receives a climb advisory; the other receives a descent advisory. The two commanded maneuvers are paired. The conflict geometry is solved assuming both crews execute their individual commands.

If one aircraft climbs and the other descends, separation increases. If both descend - or both do anything other than their assigned maneuver - the geometry the computer solved no longer holds. There is no fallback.

The integrity of the solution depends entirely on both crews complying. That is why the rule is absolute.

The Three-Step Rule for Resolution Advisory Response

Current guidance from ICAO, the FAA, and EASA is consistent. When a Resolution Advisory activates:

Immediately initiate the commanded maneuver.
Advise air traffic control that you are following a TCAS Resolution Advisory.
Maintain the maneuver until the advisory clears or is replaced by a new advisory.

That is the complete procedure. A controller issuing a conflicting clearance does not change it. Surprise at the advisory does not change it.

The Narrow Exception: When You May Deviate

Compliance with a Resolution Advisory may be set aside if following it would create an immediate hazard. The standard training example is terrain: a climb advisory that would fly the aircraft into a mountain is not one to follow. The word immediate is load-bearing here. The bar is not uncertainty about the advisory. The bar is not a conflicting ATC clearance. The bar is immediate physical danger created by the maneuver itself.

A controller’s instruction to do something different does not meet that bar.

What the German Investigation Found

The German Federal Bureau of Aircraft Accident Investigation identified two interacting causes at Uberlingen.

First, Nielsen issued a descent clearance that directly contradicted Bashkirian 2937’s active climb Resolution Advisory. He was working alone that night, covering responsibilities that required two controllers - his colleague had gone on break. A direct telephone line between the two sectors was not functioning. The backup short-term conflict alert system at the Skyguide center in Zurich had been taken offline for maintenance without adequate mitigation in place. Nielsen was simultaneously managing a separate complex traffic situation on another sector.

Second, the Bashkirian flight crew responded to the controller rather than to the TCAS. The investigation found that crew training on Resolution Advisory response was inadequate. The rule existed in documentation, but it had not been trained to the level of automatic behavior. When two conflicting commands arrived simultaneously - one from a machine and one from a trusted human voice - the crew chose the human voice.

That instinct is understandable. In that specific scenario, it is wrong. And at Uberlingen, it was fatal.

The Post-Uberlingen Industry Response

The consensus across the industry after Uberlingen was that the Resolution Advisory rule needed to be trained to reflex, not memorized for a written exam. Airlines worldwide revised simulator curricula to include explicit scenarios where a TCAS Resolution Advisory conflicts with an ATC instruction. The correct response has to be automatic, because the available window is too small for deliberation.

The technical response was TCAS II Version 7.1, which became the worldwide standard and was mandated for all commercial operations in Europe by 2015. The key changes addressed reversal scenarios - situations where the system issues an initial advisory and then modifies or reverses it as the geometry evolves. Version 7.1 refined the logic for those cases, improved inhibit criteria for weakening advisories, and strengthened the sense-reversal delay, giving crews a clearer signal when the system changed its guidance and reducing the potential for confusion during a rapidly evolving threat.

Where Collision Avoidance Technology Is Going: ACAS X

The FAA, working with MIT Lincoln Laboratory, has been developing the next generation of the system: ACAS X (Airborne Collision Avoidance System X). Where TCAS II follows a deterministic decision tree, ACAS X uses a probabilistic encounter model. The system maintains a probability distribution over possible aircraft states and uses dynamic programming to generate advisories that optimize performance across the realistic range of what might happen next, rather than assuming a single projected trajectory.

ACAS X is expected to produce fewer nuisance advisories in benign situations while maintaining equivalent protection in genuine threat scenarios. The program also addresses new categories of airspace users: ACAS Xa targets large commercial aircraft, while ACAS Xu is designed for unmanned aircraft systems, which have operational envelopes and collision avoidance challenges that TCAS was not built to handle.

Deployment timelines are not yet firm. TCAS II Version 7.1 remains the mandated standard for the foreseeable future.

What This Means for General Aviation Pilots

General aviation pilots operating in Class A airspace or at high altitudes are visible to the TCAS systems aboard nearby commercial aircraft. Your transponder is being interrogated. You may not receive Resolution Advisories yourself - your equipment may not support Mode S coordination logic - but commercial TCAS units see you and will maneuver around you if the geometry requires it.

If a commercial aircraft near you makes a deviation that appears inconsistent with a clearance, consider that the crew may be following a TCAS advisory. Give them room. Do not make calls or queries that add to their workload in those moments.

If you fly a turbine aircraft or high-performance piston with an installed TCAS unit, the training philosophy applies regardless of certificate level. Know the phraseology. Know the rule. Fly the Resolution Advisory scenario in a simulator before you encounter it in the airplane. The correct response needs to be established before the amber symbol upgrades to red.

Both TCAS units at Uberlingen worked correctly. The DHL crew executed perfectly. What failed was the human side of the interface - a training program that had not built the right reflex, an operational organization with systemic vulnerabilities, and a controller in an impossible position making a call that was not his to make.

The rule is three words: fly the advisory.

Key Takeaways

TCAS II Resolution Advisories are commands, not suggestions. When the advisory fires, immediately execute the directed maneuver and advise ATC you are doing so.
Paired advisories depend on both crews complying. TCAS II coordinates between aircraft via Mode S data link; if one crew deviates, the computed separation solution fails.
The Uberlingen collision on July 1, 2002, killed 71 people because a flight crew followed an ATC instruction that contradicted an active Resolution Advisory - both TCAS units had worked correctly.
The only valid exception to following a Resolution Advisory is an immediate physical hazard created by the maneuver itself, not a conflicting clearance and not surprise.
TCAS II Version 7.1 is the current mandated worldwide standard; ACAS X, developed by the FAA and MIT Lincoln Laboratory, is the probabilistic successor currently under development.