TCAS II, the Resolution Advisory, and the Automation That Tells Two Airliners How to Miss Each Other in the Dark

TCAS II (Traffic Collision Avoidance System, second generation) is airborne automation that detects converging aircraft and issues vertical escape commands - independent of air traffic control. When two TCAS-equipped aircraft are on a collision course, their units talk directly to each other, coordinate a solution in under a second, and order one to climb while ordering the other to descend. The core rule every pilot learns: when you get a Resolution Advisory, you follow it, even if the controller just told you something different.

What Is TCAS II and How Does It Work?

The Traffic Collision Avoidance System - spoken as “tee-cass” - is a last line of defense against midair collisions. The version flying on nearly every airliner and many business jets today is the second generation, TCAS II.

Its central idea is elegant: TCAS does not need radar, a controller, or any ground station. It communicates directly with the transponders in other aircraft. Your unit interrogates their transponder, their transponder replies, and from the timing and altitude in that reply, your system builds a three-dimensional picture of the traffic squawking around you.

This independence is the whole point. TCAS is designed to catch what every other layer drops. If a controller makes a mistake, if two clearances collide, or if a transponder code gets entered wrong, TCAS neither knows nor cares. It watches the actual airplanes, not the plan.

Traffic Advisory vs. Resolution Advisory: What’s the Difference?

TCAS II works in two escalating stages, and the difference between them matters enormously.

The Traffic Advisory (TA) is stage one. The system announces “Traffic, Traffic,” pointing the crew toward roughly where and at what altitude another aircraft is getting close. A TA is a heads-up. It does not tell you to do anything - it wants your eyes and your attention.

The Resolution Advisory (RA) is stage two, and it is a command, not a suggestion. The box has run the geometry, concluded a collision is genuinely developing, and issues a vertical order: “Climb, climb now” or “Descend, descend.”

Here is the elegant part. When two TCAS-equipped aircraft converge, their units coordinate first. One is told to climb; the other, at that same instant, is told to descend. Two independent computers - potentially built by different manufacturers - agree on a solution to a life-or-death problem in milliseconds, with no human in the loop and no ground station refereeing.

Why Do Pilots Always Follow the Resolution Advisory?

The rule that an RA overrides everything - including a controller’s instruction - was written after a tragedy.

In the summer of 2002, near Überlingen in southern Germany, at roughly 35,000 feet just before midnight, a passenger jet and a cargo jet were on quietly converging paths. A single controller, working alone with degraded systems that night, spotted the conflict late.

The controller told one aircraft to descend. But at almost exactly the same moment, both aircraft’s TCAS units had already coordinated their own solution: that same aircraft was told to climb, and the other to descend.

One crew received two contradictory orders - the controller said down, the box said up. They followed the controller. The other aircraft, following its box, was also descending. Both went down, into each other. 71 people died, many of them children.

The investigation reshaped procedures worldwide, and its conclusion is the single most important takeaway: when you get a Resolution Advisory, you follow the Resolution Advisory - even if a controller told you something different one second earlier. The box knows what the other aircraft’s box is doing. The controller, fundamentally, cannot.

What Did TCAS Version 7.1 Change?

The Überlingen crash exposed a real gap. In the original design, if a pilot did the wrong thing and maneuvered against their advisory, the system had no reliable way to recognize it and adapt.

The current standard, version 7.1, added reversal logic. If the box tells you to climb but you begin descending instead - whether following a controller or simply startled - version 7.1 watches the actual vertical distance between the aircraft. If it sees the gap closing when it should be opening, it reverses the command, flipping an aircraft from climb to descend (or vice versa) to force the miss back open. The system stopped trusting that humans would comply and started verifying.

Version 7.1 included a second, smaller fix rooted in human factors. The old spoken command “adjust vertical speed, adjust” was too often misread in the heat of the moment as an instruction to descend when the goal was to level off. The phraseology was simplified to a plain “level off, level off.” Sometimes the bug isn’t in the silicon - it’s in the sentence.

What Are the Limitations of TCAS?

TCAS is arguably the most successful safety automation in airline history. Midair collisions between transport aircraft, once a recurring nightmare, have become vanishingly rare in airspace where the equipment is required. But it has hard edges pilots must hold clearly.

It only sees aircraft with a working transponder. If the other aircraft is dark - no transponder, failed, or switched off - you are invisible to each other. In the light general aviation world, plenty of aircraft fit that description.

Resolution Advisories are vertical only. TCAS will tell you to climb or descend, never to turn. Adding horizontal maneuvering to the coordination problem was too complex and too risky for the original architecture, so the solution space is one axis: up or down.

Compliance can bust your assigned altitude. Climbing or descending hard to follow an RA is correct and expected - but it puts an aircraft off its clearance in busy airspace, and the controller has to absorb that. The automation solved one problem by handing a smaller one to the ground.

Nuisance alerts erode trust. Any system that cries wolf gets tuned out. Engineers work hard to keep false alerts down, because trust in automation is a finite resource - spend it carelessly and it runs out at the worst possible moment.

Who Builds TCAS, and What Comes Next?

The hardware comes from the major avionics houses. Honeywell has been in this space from the beginning, and a product line tracing through ACSS - tied to L3 and Thales - builds many of the units flying today. These are mature, deeply certified boxes, and that maturity is exactly why the standard evolves slowly. You do not casually push a software update to something allowed to override a human at 35,000 feet.

The successor is called ACAS X, and it represents a genuine philosophical shift. Today’s TCAS runs on decades of carefully handwritten rules - engineers coded the logic case by case. ACAS X replaces that with an optimized decision model: a large precomputed lookup table built by running millions of simulated encounters and calculating the mathematically best move for each situation, balancing collision risk against the cost of nagging the pilot over nothing.

The promise is fewer nuisance alerts and better performance. Because it is built on probabilities rather than rigid rules, ACAS X can also adapt to new kinds of traffic - drones, remotely piloted cargo aircraft, and closely spaced approaches - making it a collision-avoidance brain for a more crowded, more automated airspace.

The timeline is deliberately slow. Variants of ACAS X have been in development and testing for years, with military and unmanned versions moving first and the airline version phasing in gradually as fleets and standards catch up. This is a next-decade story, not a next-year one - and for a box with this much authority over human life, slow is the right speed.

Key Takeaways

• TCAS II works independently of air traffic control, communicating aircraft-to-aircraft via transponders to build its own picture of nearby traffic.
• A Traffic Advisory (“Traffic, Traffic”) is a heads-up; a Resolution Advisory (“Climb, climb now” / “Descend, descend”) is a coordinated command you must follow - even over a controller’s instruction.
• The 2002 Überlingen collision (~35,000 ft, 71 killed) established the absolute rule to always obey the RA.
• Version 7.1 added reversal logic to correct for non-compliance and simplified confusing phraseology to “level off, level off.”
• TCAS is vertical-only, blind to aircraft without a working transponder, and being succeeded by the probability-based ACAS X over the coming decade.