TCAS, the Überlingen Collision, and the Resolution Advisory Rule Every Pilot Must Never Override

On July 1, 2002, two aircraft collided over Lake Constance in southern Germany, killing 71 people - including 45 children traveling to a UNESCO summer camp in Barcelona. The collision was not caused by a failure of technology. The Traffic Collision Avoidance System worked exactly as designed. Both aircraft received coordinated, complementary Resolution Advisories. One crew followed theirs. The other did not.

What TCAS Is and Why It Exists

TCAS was not built to solve a theoretical problem. It was built because airplanes kept running into each other and see-and-avoid was not sufficient to stop it.

The accident that drove congressional urgency was Pacific Southwest Airlines Flight 182 on September 25, 1978. A Boeing 727 on approach to San Diego’s Lindbergh Field collided with a Cessna 172 over the North Park neighborhood. 144 people died. The airline crew had been given traffic advisories and briefly had the Cessna in sight but lost visual contact before impact. The general aviation crew likely never knew the airliner was behind them.

That accident, and others like it, drove a decade-long push for a technological solution. By 1993, TCAS II was mandated on large U.S. transport aircraft. European adoption followed. By 2002, it was standard across most of commercial aviation.

TCAS I vs. TCAS II: What Each System Actually Does

TCAS I gives you Traffic Advisories - awareness alerts. “Traffic. Traffic.” It tells you something is nearby that deserves your attention. It does not tell you what to do about it. You use the advisory to acquire the traffic visually and maneuver as you judge best.

TCAS II goes further. When a conflict is serious enough, it escalates from a Traffic Advisory to a Resolution Advisory (RA). The RA is a commanded maneuver: “Climb. Climb Now.” or “Descend. Descend Now.” It is specific, calculated, and - critically - coordinated.

How TCAS II Coordination Works

Every TCAS II unit communicates with nearby TCAS II units via a Mode S datalink. When two aircraft are on a converging track, both systems detect the conflict and negotiate with each other in real time. They agree on who climbs and who descends. Both crews receive complementary instructions simultaneously.

The result, if both crews comply, is guaranteed separation.

This coordination is the entire basis for the RA compliance rule. The system’s geometry depends on both aircraft executing their assigned half of the solution. One aircraft deviating from its RA breaks the calculation - and the separation disappears.

The Night of the Überlingen Collision

Skyguide, the Swiss air traffic service provider, was responsible for upper airspace over Switzerland and significant portions of southern Germany. On the night of July 1, 2002, operations at the area control center near Zürich were severely degraded.

Peter Nielsen was the sector controller on duty. He was working alone - a second controller had stepped away on a break. Nielsen was managing two adjacent sectors by himself.

Two critical safety systems were offline simultaneously. The Short-Term Conflict Alert (STCA) - an automated system that flags converging traffic before a controller would spot the conflict manually - was out of service for scheduled maintenance. A separate phone coordination system used between sectors was also undergoing maintenance that same night. Nielsen was working with degraded tools and no backup.

The Sequence That Led to 71 Deaths

At 21:57 local time, the TCAS units on both aircraft detected the conflict.

DHL Flight 611, a Boeing 757 freighter flying from Bergamo, Italy to Brussels, received an RA: Descend. The crew acknowledged the advisory and pushed the nose down. They followed the system.

Bashkirian Airlines Flight 2937, a Tupolev Tu-154M carrying 60 passengers and 9 crew - including the 45 children from Ufa, Russia - received an RA at the same moment: Climb.

Eleven seconds after both RAs were issued, Nielsen spotted the converging tracks on radar. He called Bashkirian 2937 and instructed the crew to descend.

The Russian crew now held two contradictory instructions. Their TCAS commanded a climb. The controller - the voice of authority they had followed throughout their careers - commanded a descent. They chose the controller.

In Russian and Soviet-era aviation culture, controller authority was deeply embedded. That principle had governed every flight these pilots had ever made, and before TCAS existed, it was the correct response. It had been reinforced in every training environment they had passed through. The crew pushed forward on the controls. The Tu-154 began to descend.

The DHL 757, already descending on its own RA, continued down. Both aircraft were now descending on crossing tracks. The separation TCAS had calculated - which depended on the Tu-154 climbing away - was collapsing. TCAS sensed the deteriorating geometry and attempted to adjust, but the original solution required the Tu-154 going in the opposite direction. There was no longer enough time.

The right wing of the Tupolev struck the DHL Boeing 757 near its tail. The Boeing broke apart almost immediately. The Tu-154 lost structural integrity and began to break up. Wreckage fell across the German countryside near the town of Überlingen on the shore of Lake Constance.

Seventy-one people died: two crew on the DHL freighter, nine crew and sixty passengers on the Bashkirian flight - 45 of them children who had fallen asleep dreaming of Spain.

What the Investigation Found

The German Federal Bureau of Aircraft Accident Investigation (BFU) spent two years on the final report. The contributing factors were extensive: Skyguide’s staffing practices, the decision to take the STCA offline on the same night the coordination phone system was also under maintenance, a management culture that had allowed degraded operations to become routine, the absence of a second controller.

All of those factors created the conditions. But the primary cause - the finding the international aviation community could act on immediately - was unambiguous: the Bashkirian crew did not follow the Resolution Advisory.

Had both crews followed their respective RAs, the aircraft would have diverged. TCAS had already solved the problem. The solution required compliance from both crews. One crew did not comply.

What Changed After Überlingen

ICAO responded with an amendment to Annex 2 of the Convention on International Civil Aviation. The amendment made RA compliance a binding requirement - explicitly, without qualification. Crews must follow TCAS Resolution Advisories. If ATC issues a conflicting instruction, crews still follow the RA, advise the controller they are doing so, and return to their clearance only after the advisory resolves.

This is not guidance. It is a requirement.

Simulator training across international airlines was rebuilt specifically around the Überlingen scenario: TCAS commands one thing, a controller you trust commands another. The correct answer, drilled until it is automatic, is TCAS. Airlines that had not previously emphasized RA compliance as a training priority did so after Überlingen. The cultural shift - particularly in traditions where controller authority was deeply embedded - took years to fully solidify, but the regulatory framework was unambiguous from that point forward.

Skyguide underwent significant restructuring. Policies around simultaneous maintenance of critical safety systems were rewritten. Staffing standards were strengthened. Executives faced criminal charges in Swiss courts.

The Human Aftermath

Vitaly Kaloyev, a Russian architect, lost his wife and two children on the Bashkirian flight. In February 2004, he went to Peter Nielsen’s home in Kloten, Switzerland, and killed him.

Kaloyev was convicted of manslaughter and sentenced to eight years. He served approximately two and a half years before being released and returned to Russia, where he was later appointed to a regional government position.

Peter Nielsen, by every professional account, was doing his best in an operation that had been allowed to run with inadequate support. He made a consequential error. He was also not the architect of the staffing shortages or the maintenance decisions that left him working alone with degraded equipment that night. That context belongs in the record.

Why This Matters for Pilots Today

For transport category pilots: The RA rule is trained, practiced, and required. The discomfort of following TCAS when a trusted controller issues a conflicting instruction is exactly what simulator training prepares you for. Überlingen is why that scenario exists. If you have not flown it recently, fly it again.

For general aviation pilots: Most GA aircraft do not have TCAS II. Traffic Advisory systems and ADS-B traffic displays give you awareness - they do not coordinate a commanded maneuver with the other aircraft simultaneously. In that environment, the fundamental rule is see-and-avoid. Traffic advisories on any platform are designed to help you look in the right direction at the right time. If you see a conflict developing, notify ATC, maneuver as required, and keep your eyes outside.

Some advanced GA aircraft and light turbines are being equipped with TCAS I units. Understand what that system gives you: awareness advisories, not coordinated commanded maneuvers.

For any pilot in a TCAS II-equipped aircraft who receives a Resolution Advisory, the procedure is:

Execute the maneuver immediately
Advise ATC: "[Callsign] is following a TCAS RA"
When the advisory clears, advise ATC and return to your clearance

The system works when both crews follow it. Every time two aircraft separate cleanly because TCAS issued RAs and both crews complied, that is an accident that did not happen - no investigation, no report, no record. The system does what it was built to do and everyone lands.

Überlingen is the record of what happens when that chain breaks.

Key Takeaways

TCAS II Resolution Advisories are mandatory, not advisory - ICAO Annex 2, the FAA AIM, and all major airline SOPs require immediate compliance.
If ATC and TCAS conflict, follow TCAS. Advise the controller you are following an RA, then return to your clearance once the advisory resolves.
The Überlingen collision on July 1, 2002 killed 71 people - not because TCAS failed, but because one crew chose a controller’s conflicting instruction over their RA.
TCAS coordination depends on both aircraft. One crew deviating from its RA destroys the calculated separation for both.
GA pilots with traffic awareness tools should understand the difference: awareness for see-and-avoid, not coordinated commanded maneuvers.