TCAS (Traffic Collision Avoidance System)

The Traffic Collision Avoidance System is standardized under ICAO Annex 10, Volume IV, Chapter 4 (Airborne Collision Avoidance Systems) and in the United States mandated under 14 CFR §121.356 (air carriers), §125.224 (large transport aircraft), and §135.180 (commuter and on-demand operations). EASA mandates ACAS II (the ICAO designation for TCAS II) under Commission Regulation (EU) No 1332/2011 and AMC1 ACAS.A.001, applicable to turbine-powered aeroplanes with a maximum certificated take-off mass exceeding 5,700 kg or authorized to carry more than 19 passengers. The system operates on the 1090 MHz Mode S transponder frequency, actively interrogating surrounding aircraft transponders and computing closure rates and collision geometry entirely onboard, without ATC involvement.

TCAS I provides Traffic Advisories (TAs) only — a visual and aural alert identifying the intruding aircraft's relative bearing, altitude, and closure rate ('TRAFFIC, TRAFFIC'), alerting the crew to look for conflicting traffic. TCAS I does not provide guidance on which manoeuvre to execute and is used primarily in smaller turboprop and regional aircraft. TCAS II provides both TAs and Resolution Advisories (RAs). An RA is a specific flight path deviation instruction ('CLIMB, CLIMB', 'DESCEND, DESCEND', 'MONITOR VERTICAL SPEED', 'LEVEL OFF, LEVEL OFF') generated when the system's collision avoidance logic determines separation has degraded to a threat level based on time-to-collision geometry, typically a Tau (time threshold) of 35 seconds or less at cruise altitudes. When two TCAS II-equipped aircraft are involved, their systems communicate via 1090 MHz data link to coordinate complementary manoeuvres — if one is commanded to climb, the other is commanded to descend — ensuring the advisories do not conflict.

TCAS II Version 7.1, mandated by ICAO Standards and Recommended Practices since March 2012 and by FAA Order 8400.10 for US operations effective March 2017, incorporates critical logic improvements developed following the Überlingen mid-air collision on 1 July 2002. In that accident, a DHL Boeing 757-200 and a Bashkirian Airlines Tupolev Tu-154M collided over southern Germany at FL360, killing all 71 occupants. The investigation (BFU Germany, 2004) found that the Bashkirian crew followed an ATC descent instruction that contradicted their TCAS RA to climb, while the DHL crew correctly followed their TCAS RA. The fundamental lesson — that following TCAS RA takes precedence over ATC instructions in all cases — is now embedded in ICAO Annex 2, §3.2, and all major states' AIP/regulatory guidance. TCAS II Version 7.1 further improved the 'reversal' RA logic, which issues a new 'INCREASE DESCENT' or 'INCREASE CLIMB' command when the initial RA proves insufficient, and refined the 'level off' advisory to reduce unnecessary altitude deviations.

The next-generation system, ACAS X, is under ICAO and FAA development. ACAS Xa is designed for transport aircraft with improved logic using a probabilistic encounter model rather than the deterministic Tau model. ACAS Xu addresses unmanned aircraft systems (UAS) integration. ACAS Xo addresses low-altitude helicopter operations and general aviation. ACAS X is expected to reduce nuisance RA rates (a significant operational complaint with TCAS II in high-density airspace) while maintaining or improving safety performance. Service entry for ACAS Xa in commercial aviation is anticipated post-2027.

Pilot compliance with TCAS RAs is a firm regulatory requirement: the correct crew response is to immediately — within 5 seconds — manoeuvre to comply with the RA, then notify ATC ('UNABLE, TCAS RA'). Pilots must not disregard an RA based on visual acquisition of the traffic, weather avoidance priorities, or ATC instructions, except in cases where following the RA would cause a more immediate danger such as terrain impact.

TCAS II is mandatory equipment on aircraft used in airline, charter, and many regional operations. For flight schools operating multi-engine turbine aircraft or conducting type-rating training in full-flight simulators, TCAS familiarity is a mandatory pre-training requirement under most airline type-rating syllabi. Students transitioning from light GA aircraft to turbine-powered aircraft encounter TCAS for the first time during type-rating ground school, and the TCAS response procedure — 'respond immediately, coordinate with ATC only after' — is a non-standard abnormal procedure tested in simulator sessions and type-rating oral exams.

In the simulator environment, TCAS RA events are a standard Crew Resource Management (CRM) training scenario. The flight standards associated with RA response (EASA CS-FSTD(A) and FAA AC 120-40C) require that full-flight simulators accurately replicate TCAS aurals, visual symbology on TCAS display, and traffic advisory logic. Schools responsible for initial type-rating qualification must ensure their simulator qualification documents include TCAS scenarios in the scenario library, and that instructors are qualified to inject TCAS traffic from the instructor operating station.

Aviatize tracks TCAS training completion as a specific curriculum element within the training management module, allowing type-rating programs to record whether a candidate has completed the required TCAS ground training, simulator RA response scenarios, and any associated written assessments. The system can flag trainees who have completed simulator TCAS sessions but not the regulatory ground school component, ensuring both elements are signed off before solo or line training commences.

For combined ATO/AOC operations where the same aircraft are used for both training and commercial flights, Aviatize's maintenance control module tracks TCAS equipment serviceability. A TCAS failure squawk is categorized against the aircraft's MEL — typically MMEL Chapter 34, with a Category B or C deferral period — and the system automatically restricts the aircraft from flight assignments requiring operational TCAS (such as Class A airspace operations or flights above FL180 where TCAS II is operationally mandatory) until the squawk is cleared and the maintenance release recorded.