Firstly, we need to go back in time. Several mid-air collisions occurred in the US in 1956, 1986, and 1987, followed by another in Überlingen, Germany, in 2002. These incidents accelerated the development of the system we know as ACAS. The term ACAS refers to the technical standard or concept. TCAS, on the other hand, refers to a current implementation.
Generally speaking, ACAS is designed to serve as a last-resort safety net to prevent mid-air collisions. It generates two types of alerts: Traffic Advisories (TAs) and Resolution Advisories (RAs). TAs aim to help pilots spot other aircraft and to alert them to be ready for a potential resolution advisory. In contrast, RAs recommend avoidance manoeuvres to the pilot, such as 'level-off', 'climb', or 'descend'.
One of the common challenges of ACAS is the unnecessary issuing of RAs, often caused by high vertical rates of climb or descent. While high rates can save fuel and time, they can become a problem when aircraft continue to climb/descend with a high vertical rate close to their cleared level. ACAS will issue an RA when it calculates a collision risk based on the two aircraft's closing speed. A high vertical rate before levelling off may cause ACAS to predict a conflict with another aircraft, even when each crew is following the appropriate ATC instructions. This is just one example of system issues that have led to the development and validation of new generations of ACAS.
The ACAS X version of the system appears in different variants: ACAS Xa for general purpose, ACAS Xo for specific operations like parallel approaches, ACAS Xu for unmanned aircraft, and ACAS sXu for small, unmanned aircraft.
This topic is complex. But if you want to know more,
Eurocontrol's page on ACAS is a great starting point. In the meantime, check out this week's news selection below.
Kasia