T-CAS II, the Resolution Advisory, and the Night Over Uberlingen That Taught Every Crew to Trust the Box Over the Controller

The Traffic Collision Avoidance System (TCAS) is an onboard computer that watches the sky independently of air traffic control and, if it detects a converging aircraft, issues a direct command to climb or descend. After the July 1, 2002 midair collision over Überlingen, Germany, aviation adopted a firm worldwide rule: when TCAS issues a Resolution Advisory (RA), the crew follows the RA - even if it contradicts air traffic control. This is one of the few situations in aviation where automation, not the human, holds final authority.

What Is TCAS and What Does It Do?

TCAS is a computer that lives in the aircraft and performs one job: it monitors surrounding traffic and, if it determines a collision is likely, tells the crew what to do about it. It operates independently of ground-based radar and air traffic control.

The system works by talking directly to the transponders of nearby aircraft - the same box that squawks a four-digit code and reports altitude to controllers. TCAS interrogates those transponders and listens to the replies.

How Does TCAS Work Without Radar?

TCAS calculates threats from the transponder replies it receives. From the timing of a reply, it derives range. From the altitude data in the reply, it determines whether the intruder is level, above, or below. From the rate of change of all of that, it calculates time to collision.

The key engineering insight is that the system cares about time, not distance. It does not really care how many miles separate the two aircraft. It cares how many seconds until both occupy the same piece of air.

Traffic Advisory vs. Resolution Advisory: The Two Stages

TCAS escalates in two distinct stages, and the difference between them is critical.

The first stage is the Traffic Advisory (TA). At roughly 40 seconds from a potential collision, the system announces “Traffic, traffic.” This is a heads-up only - it tells the crew to look outside and find the aircraft on the display. It does not command any action.

The second stage is the Resolution Advisory (RA). At roughly 25 seconds from collision, TCAS stops advising and starts commanding. It calls “Climb, climb” or “Descend, descend,” with a target vertical rate displayed on the vertical speed indicator as a green band to fly into and a red band to avoid.

How Does TCAS Coordinate Between Two Aircraft?

When two TCAS-equipped aircraft are converging, their computers communicate before issuing orders. They negotiate and deconflict the vertical automatically: one aircraft is told to climb, the other is told to descend, at the same instant.

This happens in a fraction of a second, with no ground involvement and no radio call. Two independent boxes - potentially on aircraft from two different airlines in two different countries - agree on a plan and split the altitude, guaranteeing the two aircraft are commanded in opposite directions.

The Überlingen Midair Collision: What Happened?

Just before midnight on July 1, 2002, two aircraft converged near Lake Constance in southern Germany. A Bashkirian Airlines Tupolev Tu-154, a Russian jetliner carrying schoolchildren, was cruising at 36,000 feet. A DHL Boeing 757 cargo flight with two pilots aboard was approaching from the opposite direction at the same 36,000 feet.

Both aircraft had TCAS, and both systems worked perfectly. They coordinated: the DHL 757’s computer commanded descend, and the Tupolev’s computer commanded climb. The boxes had solved the problem.

At almost the same moment the Tupolev’s TCAS ordered a climb, the air traffic controller instructed the Tupolev to descend. Faced with a human authority contradicting the computer and roughly 20 seconds to decide, the crew followed the controller and descended. The DHL 757, obeying its own RA, was also descending.

Both aircraft went down, the coordinated solution was broken, and they collided. 71 people died, most of them children. There were no survivors.

This was not the failure of one person. The controller was working alone, covering two positions at a facility where critical equipment was down for maintenance and a backup phone system was not working. The German accident investigators, the BFU, documented these system failures in detail. It was an organizational accident, not a villain.

Why Do Pilots Now Follow the Box Over the Controller?

Überlingen forced the industry to answer an uncomfortable question: when the machine and the human disagree, who wins?

For decades, aviation culture had a clear answer - the controller is the authority. That instinct is baked into pilot training, and it is correct most of the time. But TCAS exposed a narrow case where it is exactly wrong. The controller cannot see the coordinated solution and may not even know the intruder is there the way the box does. In the final 25 seconds, the box genuinely knows better.

So the rule changed worldwide. Today it is drilled into every crew: if you receive a Resolution Advisory, you follow the RA - even if it contradicts ATC. You announce “TCAS RA” to the controller, fly the green needle, and sort out the paperwork later, on the ground, alive.

That is a profound admission for a profession built on human command authority. In this one narrow, time-critical slice of flying, the automation is the final authority, and pilots are told in advance to obey it.

What Are the Pros and Cons of TCAS?

The upside is enormous and proven. Since TCAS II became mandatory on airliners, the midair collision - once one of the great terrors of commercial aviation - has become vanishingly rare. By any measure, it is one of the most successful safety systems ever fielded.

The limitations are real:

• It only sees transponders. If an aircraft is not squawking or has its transponder switched off, TCAS is blind to it. The system is only as good as the cooperation of everyone in the sky.
• It resolves in the vertical only. TCAS commands climbs and descents - never turns. Engineers chose this deliberately because altitude changes are faster, more predictable, and easier to coordinate between two computers. But down low, near the ground, options get thin, which is why certain RAs are inhibited below altitude floors so the box never commands a descent into terrain.
• The human factor. An RA is loud, sudden, often at night, and may command something that feels wrong and contradicts a clearance. Following it takes training, discipline, and trust.
• Nuisance alerts. Too aggressive, and the system cries wolf, firing RAs that disrupt safe traffic and eroding crew trust. The tension between the false alarm and the missed detection is the central engineering challenge of collision avoidance.

What Is ACAS X, the Next Generation?

Today’s system, TCAS II, is essentially a giant hand-crafted rulebook - thousands of explicit if-this-then-that rules written by engineers. It is brilliant but rigid, and tuning it to reduce false alarms without missing real threats is brutally hard.

Its replacement, the Airborne Collision Avoidance System X (ACAS X), thinks differently. Instead of a fixed rulebook, it uses a probabilistic model that simulates possible futures, weighs their likelihood, and selects the maneuver with the best outcome across all of them while firing the fewest unnecessary alerts. It is an optimization engine rather than a lookup table. The FAA, working with MIT’s Lincoln Laboratory, drove much of the development, aiming for fewer nuisance RAs, better protection, and flexibility for new kinds of traffic.

That flexibility matters because the airspace is getting more crowded and more varied. A variant called ACAS Xu targets unmanned aircraft (drones), where there is no pilot in the seat to pull the yoke - the avoidance logic must couple directly to the flight controls or feed a remote operator across a laggy link. Another variant, ACAS Xr, targets rotorcraft and their low, slow, tight-quarters flying.

On timeline: the core ACAS X standards are complete and published, and adoption has begun - but adoption in aviation is measured in years and sometimes decades, because every fleet and regulator must move together. The TCAS in your next airline flight will not suddenly become the new system. This is a deliberate handoff, done carefully, with proof at every step.

Key Takeaways

• TCAS works by timing transponder replies to calculate seconds-to-collision, then commands vertical maneuvers - independent of radar and ATC.
• A Traffic Advisory (TA) fires around 40 seconds out as a heads-up; a Resolution Advisory (RA) fires around 25 seconds out as a hard command to climb or descend.
• The July 1, 2002 Überlingen collision killed 71 people when a crew followed ATC instead of their RA, breaking the coordinated solution between two aircraft at 36,000 feet.
• The worldwide rule since then: always follow the RA, even when it contradicts air traffic control.
• The next-generation ACAS X replaces the fixed rulebook with a probabilistic model, with ACAS Xu for drones and ACAS Xr for rotorcraft - standards published, adoption underway but slow.