TCAS Two, the Uberlingen Mid-Air Collision, and the Resolution Advisory That Overrides ATC
The 2002 Uberlingen mid-air collision killed 71 people after a crew followed ATC instead of their TCAS Resolution Advisory - here's what every pilot needs to know.
On July 1, 2002, a Bashkirian Airlines Tupolev 154 and a DHL Boeing 757 collided at approximately 35,000 feet above Lake Constance on the German-Swiss border, killing 71 people. The Tupolev’s TCAS had issued the correct Resolution Advisory. The crew did not follow it. Understanding what went wrong - and why the rules changed afterward - is essential knowledge for any pilot who flies with TCAS equipment.
How Does TCAS Work?
Traffic Collision Avoidance System (TCAS) works by actively interrogating the transponders of nearby aircraft and building a real-time geometric picture of surrounding traffic. Your TCAS unit transmits interrogation signals on 1090 MHz - the same frequency used when ground radar queries your transponder. Aircraft equipped with Mode C or Mode S transponders reply automatically, and your system collects those replies to calculate range, altitude, and closure rate for each target.
The FAA requires TCAS II on most commercial transport and large turbine aircraft operating in U.S. airspace. Smaller general aviation aircraft often carry TCAS I, which provides traffic awareness but does not generate maneuver commands. The full collision avoidance capability - the part that tells you how to move the airplane - lives in TCAS II.
What Is the Difference Between a TA and an RA?
TCAS generates two distinct alert types, and confusing them is a training failure.
A Traffic Advisory (TA) activates the cockpit display, triggers the “Traffic, traffic” audio alert, and gives you a visual reference for the intruder. The system is cueing your attention. It is not commanding a maneuver yet.
A Resolution Advisory (RA) is a commanded vertical maneuver. “Climb, climb.” “Descend, descend.” “Maintain vertical speed.” “Don’t descend.” The vertical speed indicator shows the band to target or avoid. You have approximately five seconds to begin complying. An RA is not advisory in the colloquial sense - it is a specific instruction generated from a conflict geometry calculation you cannot replicate in the time available.
How Do Two TCAS Systems Coordinate With Each Other?
This is the engineering detail that makes TCAS II fundamentally different from any ground-based traffic tool. When two TCAS-equipped aircraft generate a mutual conflict, the two systems communicate directly with each other over the transponder datalink - aircraft to aircraft, no human in the loop.
The coordination happens in approximately one-tenth of a second. One system issues a climb advisory while simultaneously instructing the other aircraft’s TCAS to issue a descent advisory. The advisories are always complementary. You will never see two aircraft both commanded into the same vertical maneuver on a converging track.
Ground radar sweeps update every four to twelve seconds depending on the facility. TCAS is running a continuous real-time calculation and coordinating between aircraft faster than a controller can form a sentence. The two systems are not comparable tools operating in the same problem space - they are operating at different time scales entirely.
What Happened at Uberlingen?
Shortly before midnight local time on July 1, 2002, Bashkirian Airlines flight BTC 2937 - a Tupolev 154 on a charter from Moscow to Barcelona - was cruising eastbound at flight level 360 over Lake Constance. Sixty-nine people were aboard, including 45 children traveling to a summer camp in Spain. DHL flight DHX 611, a Boeing 757 cargo jet, was crossing its path on a climbing track. The closure rate between the two aircraft was approaching 900 miles per hour.
Zurich Area Control Center was managing both flights. That night, the sector was operating short-staffed, with a single controller working alone while a colleague dealt with equipment in another room. The facility’s ground-based conflict alert system had been generating nuisance alarms and was not being monitored closely. The conflict was flagged late.
The controller called BTC 2937 and instructed the crew to descend to flight level 350. At nearly the same moment, the Tupolev’s TCAS issued its Resolution Advisory: climb. The DHL 757 had already received the complementary advisory from its own TCAS: descend. That crew pushed the nose over immediately.
The Bashkirian crew followed the controller. They pushed the nose over too.
Two aircraft. The same vertical maneuver. On a converging track. Eight seconds later, they collided at approximately 35,000 feet. All 69 people aboard the Tupolev died, along with both crew members on the DHL aircraft. 71 fatalities total.
Why Did the Crew Follow ATC Instead of TCAS?
The German accident investigation board concluded that a primary cause of the collision was the crew’s decision to follow the ATC descent instruction rather than the TCAS climb RA. The controller’s error was a contributing cause, and there were systemic failures in the ATC environment that night. But the investigation’s central finding was unambiguous: the TCAS RA had given the correct answer. If the Tupolev had climbed while the DHL aircraft descended, both would have survived. The system worked. The crew did not follow it.
The human factors analysis identified several converging problems.
Authority conditioning. Pilots are trained from the beginning to follow ATC. The voice on the radio represents the controlling authority over the airspace. Overriding a human instruction based on a machine command requires an explicitly trained, deeply embedded habit. In 2002, that training was inconsistent - particularly in Russian-flagged operations, where controller authority doctrine was strongly embedded.
Simultaneous inputs. The ATC call and the TCAS RA arrived nearly simultaneously. The crew was already processing the controller’s instruction when the RA was issued. The human input had a cognitive head start.
No visual reference. It was nighttime. The crew could not see the DHL aircraft. The TCAS display was the only available geometric picture of where the conflict was developing.
What Are the Rules After Uberlingen?
Post-Uberlingen guidance from the International Civil Aviation Organization (ICAO) is now non-negotiable across commercial aviation globally.
When you receive a Resolution Advisory from TCAS II:
- Comply immediately. Do not weigh the RA against any ATC instruction.
- Do not seek confirmation. There is no time, and the other aircraft is already maneuvering based on the coordination your TCAS has executed.
- Advise ATC after you are established in the maneuver and the conflict is resolving. The standard phrasing most operators use: “Unable, TCAS RA.”
- Fly the advisory to resolution. Do not return to your assigned altitude or heading without ATC coordination.
The phrase simulator instructors use today is direct: “TCAS wins.” Not because the box is infallible, but because by the time you have an RA, you are in a collision geometry where the system is executing a coordinated solution - with the other aircraft - that no human can replicate in the time available.
How Effective Has TCAS II Been?
The data is compelling. From the mid-1990s, as TCAS II was phased into widespread commercial aviation use, mid-air collisions between large aircraft in controlled airspace essentially disappeared in regions with high equipage rates. The FAA and ICAO have both credited TCAS II as one of the most impactful safety interventions in aviation history.
The critical insight from the engineering side: the RA is not simply advice. It is one side of a coordinated solution. When your TCAS issues an RA, it has simultaneously communicated to the other aircraft’s TCAS what your airplane is going to do. If you deviate from the commanded maneuver, you break that coordination. You have introduced uncertainty into a system that was converging toward a solution that kept both aircraft safe. Compliance is not optional, and it is not only about your own safety.
What Is ACAS X and When Will It Replace TCAS?
TCAS II is mature technology built on standards from the 1980s. The next generation system is called ACAS X (Airborne Collision Avoidance System X), developed by the FAA in collaboration with MIT Lincoln Laboratory over more than a decade.
The fundamental difference is computational. TCAS II uses deterministic logic tables - engineers pre-calculated the correct maneuver for a defined set of encounter geometries and built a lookup table. If the geometry looks like this, issue this RA. The problem: lookup tables do not handle novel encounter types gracefully, and airspace is growing significantly more complex.
ACAS X uses a probabilistic optimization algorithm instead. It builds a real-time probabilistic model of the encounter, accounts for uncertainty in sensing and aircraft performance, and optimizes the commanded maneuver across a distribution of possible futures. This approach is better suited to the airspace environment taking shape with unmanned aircraft, electric vertical takeoff and landing (eVTOL) operations, and increasing traffic density in congested corridors.
There are four variants currently in development:
- ACAS Xa - the replacement for TCAS II on large commercial aircraft
- ACAS Xo - designed for oceanic operations with reduced separation standards
- ACAS Xu - the unmanned aircraft variant, for drones and UAS entering the national airspace
- ACAS Xp - a passive system for general aviation using ADS-B Out broadcasts
ACAS Xp is potentially the most significant development for the GA community. It does not require an active interrogator. It listens to ADS-B broadcasts, builds a traffic picture from that data, and generates advisories with a smaller hardware footprint and meaningfully lower cost than a full TCAS installation. The FAA has been clear that ACAS Xp is not yet certified or mandated, and the rulemaking process will take time. But it represents the first architecture capable of bringing coordinated conflict resolution guidance to light aircraft that currently have traffic displays with no maneuver coordination capability at all.
Key Takeaways
- When TCAS II issues a Resolution Advisory, comply immediately - the RA takes priority over any ATC instruction, without exception.
- The two TCAS systems coordinate aircraft-to-aircraft in approximately one-tenth of a second; deviating from the RA breaks that coordination and endangers both aircraft.
- The 2002 Uberlingen collision killed 71 people after a crew followed an ATC descent instruction instead of a TCAS climb RA - the system had the correct answer.
- Post-Uberlingen ICAO guidance is now universal: fly the RA, then advise ATC with “Unable, TCAS RA.”
- ACAS X, built on probabilistic optimization rather than lookup tables, is the next generation system - with a general aviation variant (ACAS Xp) that could extend coordinated conflict alerting to light aircraft for the first time.
Radio Hangar. Aviation talk, built by pilots. Listen live | More articles