TCAS Two, the Collision Over Lake Constance, and the Rule That Says the Box Beats ATC Every Time

TCAS II (Traffic Collision Avoidance System) is an independent onboard system that tracks nearby aircraft and, when necessary, issues coordinated Resolution Advisories commanding specific vertical maneuvers to resolve traffic conflicts. The governing rule is absolute: when TCAS issues an RA, pilots must follow it immediately - even if it contradicts an ATC instruction. The 2002 mid-air collision over Überlingen, Germany, which killed 71 people, is the defining example of what happens when that rule is not followed.

Why Was TCAS Developed?

Before TCAS, mid-air collisions happened with grim regularity. Faster aircraft were filling increasingly crowded airspace while radar coverage remained patchy at lower altitudes, and controllers managed enormous traffic volumes with tools that offered no automatic conflict alerting.

June 30, 1956 - a United Airlines Douglas DC-7 and a TWA Lockheed Constellation collided over the Grand Canyon, killing 128 people. That disaster drove the creation of the Federal Aviation Agency, the forerunner to the FAA.

August 31, 1986 - Aeromexico Flight 498, a Douglas DC-9, was on approach to Los Angeles International when it entered the Terminal Control Area without a functioning transponder. A Piper Cherokee with two adults and a child was flying below in uncontrolled airspace. The two aircraft collided at approximately 6,500 feet, killing 82 people, including 15 on the ground when debris fell into a residential neighborhood.

Cerritos changed the political calculus. The FAA had been developing collision avoidance technology since the 1970s, but years of technical disputes and regulatory delays had stalled the effort. After Cerritos, Congress acted. By 1993, TCAS II was required on virtually every turbine-powered aircraft with more than 30 seats operating in American airspace.

How Does TCAS Actually Work?

TCAS is fully independent of ground-based radar and air traffic control. It works by interrogating the transponders of nearby aircraft - essentially asking: where are you, and what altitude are you at? It receives those replies and builds a complete picture of the surrounding traffic environment on its own.

This independence is deliberate. ATC radar is time-delayed, may have coverage gaps, and requires a controller to interpret and act on it. TCAS communicates directly with the other aircraft’s avionics, in real time, without that chain of intermediaries.

What Is the Difference Between a Traffic Advisory and a Resolution Advisory?

TCAS issues two levels of alerts.

A Traffic Advisory (TA) - “Traffic. Traffic.” - places the conflicting aircraft on the cockpit display and alerts the crew to be aware. A TA does not instruct a maneuver. It tells you to look.

A Resolution Advisory (RA) is a command. “Climb.” “Descend.” “Climb now.” “Maintain vertical speed.” The RA specifies the vertical rate required to resolve the conflict, and a green arc on the vertical speed indicator marks the target zone. When you receive an RA, you fly to that arc.

Why Do Both Aircraft Need to Follow the RA?

This is the detail that makes TCAS work - and the detail that makes non-compliance catastrophic.

When two TCAS-equipped aircraft are converging, the two systems communicate directly with each other. They coordinate their advisories so that one aircraft climbs while the other descends - complementary commands, not contradictory ones. The geometry is solved for both aircraft acting simultaneously.

If only one crew follows their RA, the system’s solution breaks down. The box calculated separation based on both aircraft responding. If one aircraft maneuvers and the other does not, the maneuvering aircraft is now moving toward a position where the other aircraft is no longer where the system expected it to be. The margin for error collapses.

When you receive an RA, you are not just protecting your own aircraft. You are half of a coordinated two-aircraft maneuver. Your response - or your failure to respond - directly affects the other crew and everyone aboard their aircraft.

What Happened Over Lake Constance on July 1, 2002?

Just after midnight on July 1, 2002, two aircraft were converging at Flight Level 360 over southern Germany. Bashkirian Airlines Flight 2937, a Tupolev 154 carrying 60 passengers and 9 crew from Moscow to Barcelona, was inbound from the northeast. A DHL Boeing 757 cargo jet with 2 pilots was climbing through the same altitude on a crossing track from the west.

The Zurich area control center had one controller on duty that night: Peter Nielsen. He was working two frequencies. The primary radar was down for scheduled maintenance. He was operating on backup systems, alone.

Nielsen recognized the conflict late and instructed the Bashkirian crew to descend - expedite.

At nearly the same moment, both TCAS systems issued coordinated RAs. The DHL 757 received a climb RA. The Bashkirian Tu-154 received a descend RA. On the surface, this appeared to align with what Nielsen had just said. The Bashkirian crew, trained in a Soviet-era culture where ATC was the unquestioned authority, treated the controller instruction and the TCAS RA as consistent guidance.

What the crew did not fully account for was that the TCAS descend command was half of a coordinated pair. The DHL aircraft was climbing away from them because its system told it to climb. Both aircraft following TCAS would have separated. But Nielsen, working degraded radar, could not clearly see the full geometry, and he continued issuing instructions.

The Bashkirian crew’s response became inconsistent. The TCAS continued commanding descent. Evidence suggests the crew leveled off or began to climb. The two aircraft collided at approximately 34,800 feet. The Tupolev’s vertical stabilizer sliced through the DHL 757’s fuselage. Both aircraft broke apart over the town of Überlingen, Germany. All 71 people on both aircraft were killed.

What Did the Investigation Conclude?

The German Federal Bureau of Aircraft Accident Investigation (BFU) issued a thorough final report identifying multiple contributing factors: the degraded radar, a single controller managing excessive workload, and the late recognition of the conflict.

The central finding was unambiguous. The Bashkirian crew received the correct TCAS RA, coordinated with the DHL aircraft’s climb advisory. Had both crews followed the system, both aircraft would have separated. One crew followed their RA consistently. One crew did not.

What Is the ICAO Rule on TCAS RAs vs. ATC Instructions?

Überlingen produced a clear regulatory response. ICAO (the International Civil Aviation Organization) mandated that crews must follow TCAS RAs even when they contradict ATC instructions. No exceptions.

The reasoning is embedded in how the system works. The controller is not aboard the aircraft. The controller does not know the precise geometry the TCAS has calculated. The controller may be working with delayed or degraded radar data, as Nielsen was that night. TCAS interrogates the conflicting aircraft directly and resolves the geometry in real time.

ATC is the authority in controlled airspace - but TCAS RA is the override. The system was specifically designed and certified to supersede ATC instructions in a conflict scenario for exactly this reason.

What Should Pilots Do When They Receive an RA?

The procedure is straightforward and must become instinct:

1. Immediately execute the RA maneuver - fly to the green arc on the vertical speed indicator.
2. Notify ATC - “Traffic, TCAS RA” - so the controller knows you are maneuvering.
3. Stay with the RA - do not revert to your cleared altitude until the system announces “Clear of conflict.”
4. Advise ATC when clear of conflict and return to your cleared altitude.

Do not wait for controller confirmation. Do not debate the advisory. The system is updating in real time. You fly it.

What Are TCAS Version 7.1 Reversal Advisories?

TCAS II Version 7.1 - the current standard - added reversal advisories to handle scenarios where the threat geometry changes rapidly enough that the original RA no longer resolves the conflict.

If the system first tells you to maintain a climb and then issues “Increase climb” or reverses to “Descend,” respond to the new instruction immediately. The system has updated its geometry calculation. Your job is to stay with it, not to hold to the first advisory.

What About General Aviation Aircraft?

Most general aviation aircraft carry TCAS I, which provides Traffic Advisories only - no resolution commands. Others have ADS-B In with a traffic display and audio alerts.

For GA pilots, the primary tools remain ATC, see-and-avoid, and whatever situational awareness the cockpit provides. That is a separate but important conversation about layered protection in uncontrolled and Class E airspace.

If you are flying a transport-category aircraft with TCAS II installed, the contract is clear. When the box gives you a Resolution Advisory, you execute it.

Key Takeaways

• TCAS II is an independent system that interrogates nearby aircraft directly and does not rely on ground radar or ATC to function.
• A Traffic Advisory (TA) means be aware; a Resolution Advisory (RA) means act now - fly to the green arc on your VSI immediately.
• When two TCAS-equipped aircraft converge, both systems coordinate complementary maneuvers. If one crew does not follow their RA, the coordinated solution fails.
• The Überlingen collision (July 1, 2002) killed 71 people because one crew received the correct TCAS descend RA but did not follow it consistently.
• ICAO mandates that crews follow TCAS RAs over ATC instructions, without exception - notify ATC, fly the maneuver, return to cleared altitude when conflict is resolved.