Understanding TCAS and Resolution Advisories

The Traffic Collision Avoidance System (TCAS) is a cornerstone of modern aviation safety, mandated for aircraft operating in high-density airspace. Designed to function independently of ground-based air traffic control (ATC), TCAS provides pilots with an effective last‑line defense against mid‑air collisions. When the system detects a potential intruder aircraft, it progresses through two levels of alert: a Traffic Advisory (TA) that alerts the crew to nearby traffic, and a Resolution Advisory (RA) that commands an immediate vertical maneuver to prevent collision. The RA is the most urgent call—a timed, unambiguous instruction that pilots must execute without delay. The following sections provide a thorough operational guide to responding to these advisories safely and effectively.

TCAS Versions and Operational Principles

TCAS I, II, and III

TCAS equipment falls into three main categories. TCAS I provides Traffic Advisories only; it shows the position and altitude of intruders but does not issue resolution commands. TCAS II—the most common type in transport category aircraft—adds Resolution Advisories using Mode‑S transponder data. TCAS II has evolved through several versions (7.0, 7.1) with improvements such as enhanced RA logic and the “Reverse” and “Do Not Climb/Descend” advisories. TCAS III, which was tested but never widely deployed, was intended to provide horizontal resolution advisories. Today, TCAS II Version 7.1 is the standard for airliners in the United States, Europe, and most ICAO member states.

How TCAS Determines an RA

The system continuously interrogates neighboring transponders and calculates the time to closest approach (τ, tau) and the vertical separation. When τ falls below a pre‑set threshold (typically about 35 seconds for an RA), TCAS issues a vertical maneuver command designed to achieve safe separation. The logic considers the performance capabilities of both aircraft and, if both are TCAS‑equipped, coordinates the direction of the advisories (e.g., one aircraft climbs while the other descends) via a “coordination link.” This ensures that the two aircraft move away from each other rather than in the same direction.

Types of Resolution Advisories

Preventative vs. Corrective Advisories

TCAS RAs are classified as either preventative or corrective. A preventative RA, such as “Monitor Vertical Speed” (MVS), requires the crew to maintain the current vertical rate but not to deviate above or below a specified threshold. A corrective RA instructs the pilot to actively change vertical speed—typically “Climb” or “Descend”—at a target rate of at least 1500 ft/min. The most aggressive RAs may include “Increase Climb” or “Increase Descent” when the immediate separation is critically low.

Specific RA Categories

  • Climb/Descend: The pilot must pitch the aircraft to achieve and maintain a vertical speed of at least 1500 ft/min in the directed direction.
  • Do Not Climb/Do Not Descend: A “cross‑side” prohibition—the pilot must not increase the vertical rate toward the intruder; often used when the intruder is already at a conflicting altitude.
  • Clear of Conflict: The RA has ended; the pilot may return to the previously assigned altitude or flight path in coordination with ATC.
  • Level‑Off: The aircraft must stop climbing or descending immediately and hold altitude.
  • Climb (or Descend) ‑ Crossing: Appears when the intruder is passing through the same altitude range; the pilot must maintain the commanded vertical speed even if it means crossing the intruder’s altitude.

Understanding these distinctions is critical because responding incorrectly (e.g., climbing when the RA says “Do Not Climb”) can negate the protective coordination.

Proper Pilot Response to RAs

Immediate and Unambiguous Action

When an RA appears on the Primary Flight Display (PFD) or the dedicated TCAS display, the pilot flying (PF) must immediately press the “TCAS” button to ensure the autopilot or flight director will follow the RA (if the aircraft is equipped with an auto‑flight TCAS integration). The PF should announce “TCAS” and the type of RA (e.g., “Climb! Climb! Climb!”) while simultaneously applying the commanded pitch change. The pilot monitoring (PM) confirms the action and monitors the vertical speed and the intruder traffic on the display. Do not hesitate—even a few seconds of delay can reduce the safety margin below acceptable limits.

Autopilot and Flight Director Considerations

In many modern aircraft, the auto‑flight system can automatically follow the RA when the autopilot is engaged and the TCAS mode is active. Pilots must verify that the flight director has captured the RA command. However, if the autopilot does not respond (e.g., because of mode reversion or a malfunction), the PF must disconnect the autopilot and hand‑fly the maneuver. Never override an RA by re‑engaging the altitude hold or vertical speed select functions until the RA is explicitly canceled. RAs take precedence over all other altitude commands, including ATC instructions.

Communication with ATC

ICAO and FAA procedures require the pilot to immediately inform ATC of the RA action as soon as workload permits but after the initial maneuver. A standard call is: “TCAS RA, climbing to [or descending from] flight level X.” ATC will respond by acknowledging the RA and will not issue conflicting instructions while the RA is active. If ATC inadvertently gives an altitude change during an RA, the pilot must still follow the RA and inform ATC of the deviation. After the RA is cleared, the pilot should report “Clear of conflict, returning to [assigned altitude].”

Monitoring, Recovery, and Follow‑Up

After the RA is issued, the crew must monitor the vertical speed indicator (VSI) and the intruder’s motion on the TCAS screen. The moment the “Clear of Conflict” message appears, the pilot should level off and coordinate with ATC to return to the original flight path. ATC may issue a vector or altitude change to help resolve the traffic. It is essential to never return to the assigned altitude without ATC clearance if the RA occurred in controlled airspace; the aircraft may have deviated from the clearance and could conflict with other traffic.

Common Pitfalls and Errors

Delayed Response

One of the most frequent errors is a delayed reaction to the RA. Some pilots hesitate because they expect ATC to give a conflicting instruction or because they are unsure of the correct response. Training scenarios must emphasize that any RA—even a preventative one—requires an immediate crew response.

Incorrect Response

Another common mistake is piloting in the opposite direction of the RA (e.g., descending when the RA says “Climb”) due to misinterpretation or relying on the intruder’s position rather than the TCAS command. The RA is based on coordinated logic; disregarding it can nullify the protection. Pilots must resist the urge to “look outside” and instead trust the automated system during the short duration of the advisory.

Over‑reliance on Automation

Some crews assume the autopilot will always capture and follow the RA correctly. However, autopilot behavior can vary between aircraft types and versions. Recurrent training should include hand‑flown RA scenarios to ensure that pilots can manually execute a precise vertical speed change without the autopilot.

Crew Resource Management During RAs

Defined Roles and Callouts

Effective crew coordination is vital. Standard callouts include the PF saying “TCAS – Climb” while the PM looks at the intruder traffic and confirms “Climb, vertical speed positive.” The PM should also monitor the intruder’s trend vector and alert the PF if the separation does not appear to be increasing. After the RA clears, the PM should say “Clear of conflict – request return to assigned altitude.” Both pilots must avoid distractions—no non‑essential conversations, no programming of the FMC, and no unnecessary heads‑down time during the RA.

Workload Management

The few seconds of an RA can be a high‑stress event. Crews should practice briefings on “TCAS logic” before flight, and both pilots should mentally rehearse the immediate actions. The PM should handle all ATC communication without interrupting the PF’s focus on the aircraft attitude and vertical speed. After the event, a debrief (if time and workload permit) can help identify any procedural lapses.

Training and Proficiency Recommendations

Simulator Sessions

ICAO and national regulators require periodic TCAS training in full‑flight simulators. Effective sessions should include:

  • Late‑RA scenarios (tau less than 25 seconds) to practice immediate response.
  • Multiple RAs (e.g., a climb RA followed immediately by a descend RA) to test flexibility.
  • Scenarios with autopilot engaged and then disengaged to compare behaviors.
  • RA events that occur during non‑normal procedures (e.g., engine failure) to build cross‑check discipline.

Recurrent Knowledge Check

Online or classroom training should review RA types, the meaning of the “Red/Green” arcs on the VSI (or the modern symbolic cues), and the coordination logic between two TCAS‑equipped aircraft. Line‑oriented flight training (LOFT) can embed RAs into realistic traffic scenarios to reinforce proper decision‑making.

Case Studies and Lessons from Real Events

The Überlingen Collision (2002)

A tragic example of an RA being overridden by ATC instructions occurred near Überlingen, Germany. Two aircraft, one with a TCAS RA to descend and another with a complementary RA to climb, received conflicting ATC “descend” commands. The pilots of the aircraft with the climb RA followed ATC instead of the RA, resulting in a loss of separation and a fatal collision. Modern regulations now mandate that RA instructions take absolute priority over ATC voice commands. This incident underscores the importance of crew training to reject controller instructions during an RA and to make that decision known immediately on the radio.

Lessons from ASRS Reports

The NASA Aviation Safety Reporting System (ASRS) database contains numerous reports of TCAS‑related incidents. Common themes include:

  • Crews noticing the RA late because they were heads‑down programming the FMC.
  • RAs being nullified because one pilot followed the RA while the other inadvertently left the altitude‑alert system armed.
  • Misinterpretation of “Do Not Climb” vs. “Descend.”
These reports highlight the need for robust callout procedures and a sterile cockpit during periods of high traffic density.

Regulatory Guidance and Best Practices

FAA Advisory Circular 120‑55C

FAA AC 120‑55C (Air Carrier Operational Approval and Use of TCAS II) provides detailed guidance on pilot training, procedures, and operational approvals. It emphasizes that “the flight crew shall follow the RA unless doing so would jeopardize the safety of the aircraft” (e.g., flying into terrain) and requires that ATC be notified as soon as workload permits. The circular also discusses the use of the “TA Only” mode in low‑altitude or special operations.

EASA Guidelines

EASA Safety Information Bulletins (SIBs) and GM documents reinforce the priority of RAs over ATC instructions. They also specify that TCAS II Version 7.1 is mandatory for aircraft operating in European airspace. Operators must ensure that crew training includes the “Reverse” RA logic, where the sense of the RA may change if the intruder’s behavior changes unexpectedly.

ICAO Annex 2

ICAO Annex 2 (Rules of the Air) paragraph 3.9.2 states that “an aircraft equipped with an ACAS (Airborne Collision Avoidance System, synonymous with TCAS) shall comply with any resolution advisory issued by that system,” except when to do so would create an immediate collision with terrain or another aircraft. This international rule provides a legal basis for pilots to deviate from ATC instructions during an RA.

Conclusion

TCAS RAs are one of the most effective safety nets in aviation, but their success depends entirely on correct, immediate pilot response. By understanding the system logic, recognizing the different types of RAs, and practicing disciplined crew coordination—including unambiguous callouts, fast execution, and proper communication with ATC—pilots can turn a potential mid‑air collision into a harmless traffic event. Regular training and a healthy respect for the priority of RAs over all other commands are essential. Every flight crew should internalize the simple mantra: When in doubt, follow the RA.