The Überlingen Midair, the TCAS Resolution Advisory One Crew Ignored, and the Rule Rewritten in the Sky Over Lake Constance

The 2002 Überlingen midair collision killed 71 people when a crew ignored a TCAS Resolution Advisory, rewriting international standards for cockpit compliance.

Aviation Technology Analyst

On July 1, 2002, two aircraft collided over Lake Constance in southern Germany, killing all 71 people aboard both flights. Both aircraft had functioning TCAS systems. Both received coordinated Resolution Advisories. One crew followed the advisory. One crew did not. The result reshaped global standards for how pilots respond when the machine and the controller disagree.

What Happened Over Lake Constance

At 23:35 Central European Time, Bashkirian Airlines Flight 29 - a Tupolev 154 carrying 69 passengers and crew, most of them Russian schoolchildren traveling to Barcelona - was cruising at Flight Level 360. DHL Flight 611, a Boeing 757 cargo jet with a crew of two, had been cleared to climb through the same level on a crossing track.

The vectors had been assigned in a way that created a collision geometry.

TCAS activated and issued coordinated Resolution Advisories simultaneously: climb to the DHL 757, descend to the Bashkirian Tu-154. The two systems had already coordinated with each other automatically before either pilot reacted. If both crews complied, they would miss each other by approximately 1,000 feet.

Captain Paul Phillips and First Officer Brant Campioni aboard the DHL flight disconnected the autopilot and climbed immediately. They followed the advisory exactly as trained.

The Bashkirian crew did not.

How TCAS Works

TCAS (Traffic Collision Avoidance System) - called ACAS by ICAO - was developed after a midair collision over San Diego in September 1978, when Pacific Southwest Airlines Flight 182, a Boeing 727, collided with a Cessna 172 on approach to Lindbergh Field, killing 144 people. The crew had been given traffic information about the Cessna but lost visual contact in the pattern. They collided on short final.

The safety community asked whether aircraft could be given the ability to detect each other directly, without depending on radar, radio, or a controller’s awareness.

TCAS II became mandatory on U.S. air carriers with more than 30 seats in 1993. ICAO adopted the standard internationally; it is now required on commercial aircraft over 5,500 kilograms in most of the world.

The system interrogates nearby transponders on 1090 MHz - the same frequency secondary surveillance radar uses. Any aircraft with a Mode C or Mode S transponder responds. The TCAS computer tracks those replies, calculates range, bearing, altitude, and rate of closure, and builds a continuously updated picture of everything within roughly 14 nautical miles laterally and 6,000 feet vertically.

Aircraft pass through three threat classifications:

  • Proximate traffic - targets in your airspace, no immediate threat
  • Traffic Advisory (TA) - yellow symbol; watch this target, build situational awareness, no maneuver required yet
  • Resolution Advisory (RA) - the red. Action required. Issued when a collision threat is calculated within approximately 40 seconds

A Resolution Advisory is a command to maneuver - not a suggestion. It directs a specific vertical response and displays a green arc on your vertical speed indicator. The required response time is two to three seconds.

The feature most pilots underestimate: when your aircraft generates an RA, it simultaneously broadcasts a coordination message to other TCAS-equipped aircraft in the area. The two systems negotiate a solution before either pilot has begun to react. One aircraft gets up. The other gets down. The separation is mathematically guaranteed - provided both pilots comply.

That last clause is everything.

What Went Wrong on the Night of July 1, 2002

The Swiss air navigation service provider Skyguide was operating under degraded conditions. The ground-based short-term conflict alert system - which warns controllers of converging traffic - had been disabled for maintenance. A phone connection between two control sectors was also out of service.

The sector responsible for both aircraft had only one controller on duty. Standard staffing was two. Peter Nielsen was working alone.

Nielsen was handling a Lufthansa flight on a different radio frequency when the conflict developed. When he saw it, he transmitted to the Bashkirian crew and told them to descend to Flight Level 350 - the same direction as the RA the Tu-154 had already received.

Then the geometry changed.

Because the DHL crew had already begun climbing, TCAS recalculated. The coordinated solution updated. The Bashkirian Tu-154’s advisory reversed. It now said climb.

Why the Tupolev Crew Descended

Captain Alexander Gross now held two simultaneous, contradictory instructions: TCAS said climb, the controller said descend. He chose the controller.

His first officer had already begun responding to the TCAS climb advisory and had pulled back slightly on the controls. The captain overrode him and pushed the nose down.

Both aircraft descended.

They collided at approximately 34,900 feet, 3 minutes and 42 seconds after TCAS first activated. The debris field fell into the village of Überlingen and into Lake Constance. All 69 people aboard the Tu-154 died. Both DHL crew members died.

The German Federal Bureau of Aircraft Accident Investigation (BFU) led the official inquiry. Its final report identified the failure to follow the TCAS Resolution Advisory as the primary cause of the accident. Contributing factors included inadequate Skyguide staffing, the disabled conflict alert system, and deficiencies in TCAS training across the aviation system.

Why This Wasn’t Simply Pilot Error

The BFU was careful on this point. The report wasn’t simply assigning blame to the Tupolev crew. It identified that the aviation training system had not prepared pilots for the specific scenario where following TCAS meant ignoring a controller.

Existing training materials contained ambiguous language. Some guidance suggested pilots should use judgment when TCAS and ATC conflicted. But the entire purpose of the TCAS coordination logic is that the judgment has already been done - by the computers, before the advisory appears on the display. The systems had already negotiated a solution. There was nothing left to decide.

Captain Gross had spent his career in an aviation culture that placed heavy emphasis on controller authority. That instinct was correct in every situation except this one.

What ICAO Changed After Überlingen

ICAO reviewed and strengthened its guidance following the accident. The standard that emerged left no room for interpretation:

When you receive a Resolution Advisory, comply immediately. Notify ATC that you are maneuvering in accordance with TCAS. Return to your clearance after the conflict resolves. The RA takes precedence over the controller. No exceptions.

That language is now embedded in training programs worldwide. TCAS compliance became a standard simulator recurrency drill. The reflex to follow the RA immediately - without hesitation, without checking with ATC first - has to be as automatic as V1 callouts or memory items for an engine failure.

TCAS II Version 7.1, which became the ICAO standard following subsequent accident analyses, improved system performance near terrain, reduced nuisance advisories, and introduced better logic for handling sense reversals - situations where the system changes the direction of an advisory mid-maneuver because the geometry has shifted, exactly as happened to the Tu-154 over Lake Constance.

Earlier versions of TCAS had generated enough nuisance advisories that some crews developed a habit of hesitating before complying. Version 7.1 brought the false alert rate down substantially. That engineering work mattered: a system that cried wolf would have undermined the entire compliance framework the post-Überlingen rules depended on.

The Next Generation: ACAS X

The FAA and Eurocontrol have been developing ACAS X for approximately 15 years. Where TCAS II uses deterministic threat logic - a fixed set of rules for defined geometric scenarios - ACAS X uses a probabilistic model. It evaluates thousands of possible trajectories for conflicting aircraft and calculates the maneuver that minimizes risk across all of them.

TCAS II was designed for a specific airspace model: transport category aircraft with defined performance envelopes and structured altitude separation. ACAS X is built for a wider range of scenarios, including unmanned aircraft, closely spaced parallel approaches, and airspace structures that didn’t exist when TCAS II was engineered.

Three variants are in development:

  • ACAS Xa - manned commercial and large business aircraft
  • ACAS Xu - unmanned systems, where collision avoidance logic interfaces directly with the flight control system (there is no pilot to process a voice advisory)
  • ACAS Xo - special operations environments

Certifying and deploying a new global standard across tens of thousands of aircraft is a process measured in years at minimum. The transition is underway.

What This Means for GA Pilots

If you’re flying general aviation aircraft without TCAS, you are still a factor in this system.

Any TCAS-equipped aircraft near you is building a picture of your position based on your transponder reply. Squawking Mode C with altitude puts you in that picture with reasonable accuracy. When a nearby airliner climbs or descends without an obvious clearance change, they may be following a TCAS RA - not experiencing a mechanical problem. If you are that traffic, hold your altitude and heading. Be predictable.

ADS-B Out makes you a sharper target. GPS-derived position broadcast gives the TCAS picture of your geometry more precision - a practical argument for equipage beyond the regulatory mandate.

Traffic advisory systems on your EFB are not TCAS. They provide situational awareness. They do not coordinate with other aircraft. They do not generate Resolution Advisories. They cannot guarantee separation the way a coordinated RA can. Know what your equipment does and what it doesn’t.

The Human Dimension

Peter Nielsen, the controller working alone that night, was killed in February 2004. Vitaly Kaloyev, a Russian architect whose wife and two children were among the 71 killed over Lake Constance, found Nielsen in Zurich and stabbed him to death. Kaloyev had attended meetings with Skyguide following the accident and believed the company had not taken genuine responsibility for what happened. He served approximately three and a half years before his release.

60 of the 71 who died were children.

The official reports document the system failures accurately: inadequate staffing, degraded equipment, insufficient training, compounding failures across multiple layers. A controller working alone in a broken system made instructions that contributed to 71 deaths.

Überlingen is not an argument against cockpit automation. It is an argument that automation only works when the humans in the loop understand their role, trust the system when it deserves trust, and have been trained to act without hesitation when acting matters most.

The engineering case is straightforward: TCAS has the full geometry in real time. No radar lag. No radio delay. No competing cognitive load across multiple frequencies. It has already coordinated with the other aircraft. In the specific window of a collision threat, the machine has better information and faster response time than any controller. The rule doesn’t diminish ATC authority. It says there is one scenario where a system already has the whole picture and has already solved the problem. Use it.


Key Takeaways

  • On July 1, 2002, the collision of Bashkirian Airlines Flight 29 and DHL Flight 611 over Lake Constance killed 71 people - 69 aboard the Tu-154 and both DHL crew members - when the Bashkirian captain followed an ATC descent instruction instead of a TCAS climb advisory
  • TCAS coordinates automatically between aircraft before either pilot reacts; both crews must comply for the separation guarantee to function
  • Post-Überlingen ICAO standard: TCAS Resolution Advisories take absolute precedence over ATC instructions - maneuver immediately, notify ATC, return to clearance after the RA clears
  • TCAS II Version 7.1 improved sense reversal handling and reduced nuisance advisories; ACAS X, built on a probabilistic threat model, is in development for both manned and unmanned aircraft
  • GA pilots without TCAS should squawk Mode C, consider ADS-B Out, and maintain predictable flight paths near TCAS-equipped aircraft; EFB traffic tools provide awareness only - they are not collision avoidance systems

Radio Hangar. Aviation talk, built by pilots. Listen live | More articles