TCAS RA Not Followed
From SKYbrary Wiki
This article is intended to give an overview of the occurrences where a TCAS RA has not been followed (correctly) by the flight crew. It describes the possible scenarios and the safety barriers used to prevent or mitigate the safety effects of such occurrences.
TCAS is one of the last safety barriers to protect from an accident, the ones after it being pilot visual response (with limited applicability in Instrument Meteorological Conditions (IMC)) and providence (i.e. luck). Therefore, ICAO documents state that all RAs should be followed unless the safety of the aircraft is at risk.
One of the most common reasons for not following a TCAS RA is the visual acquisition of (what is perceived to be) the conflicting traffic. It is worth noting, however, that the flight crew might not be fully aware of the overall picture in complex traffic situations and therefore visual acquisition is not a valid excuse for procedural non-compliance.
A dedicated study was performed in 2017 by the EUROCONTROL Safety Improvement Sub-Group (SISG) after identifying "TCAS RA Not Followed" as one of the Top 5 ATM Operational Safety Priorities. The SISG's analysis examines the operational context (factors that can affect the situation) and establishes a set of generic scenarios that account for different situational developments. While the scenarios are not equally probable (and data collected from both A&I events and a dedicated survey confirm they are not) they do constitute a useful, concise representative subset that substitutes effectively for trying to imagine all possible scenarios. The scenarios are grouped in the following categories and subcategories:
- Lack of pilot detection/awareness of the TCAS RA due to:
- Human-machine interface (Human-Machine Interface (HMI)) issues (i.e., factors concerning the perception and interpretation of the TCAS HMI and alert annunciations);
- Presence of other flight deck signals and alerts, or external distractions, occurring simultaneously with the TCAS RA; and/or
- Flight deck mindset (i.e., any factor concerning the mind-set or expectations of the crew immediately beforehand).
- Misinterpretation of TCAS RA due to:
- Decision not to follow RA due to:
- Other signals and alerts;
- Contradictory ATC instructions (this situation also includes prior ATC instructions being actioned when the RA occurs);
- TCAS credibility issues (e.g. if the RA is perceived as false/unreliable or due to rapid succession of different RAs);
- Aircraft performance issues/concerns (actual or perceived aircraft performance limitations);
- Flight deck mind-set;
- Significant flight conditions (e.g. cockpit warnings, severe weather, terrain, etc.); and/or
- Inadequate TCAS training.
- TCAS RA response not executed correctly due to:
- HMI Issues;
- Late or inadequate pilot response;
- Unintentional pilot response;
- Aircraft performance issues/concerns;
- Flight deck CRM;
- Inadequate TCAS training;
- Flight deck mind-set;
- Duration of RA less than the pilot's reaction time; and/or
- Flight deck control inputs and handling (e.g. inappropriate vertical speed when approaching the selected flight level).
Two major sets of barriers can reduce the risk associated with TCAS RA not followed events:
- Prevention barriers: When deployed and employed correctly, these defences are capable of preventing a TCAS RA not being followed. Three prevention barriers have been identified:
- Following a TCAS TA: TCAS RA Prevention Functionality by Auto Pilot reducing rates of climb/descent approaching selected level.
- Enhanced TCAS training including experience with multiple tracks, conflict-aircraft crossing and reversal RAs; and,
- Training and enforcement of standard operating procedures (SOPs) requiring TCAS RAs to be followed unless the safety of the aircraft would be compromised
- Mitigation barriers: When deployed and employed correctly, these are capable of alerting pilots to a potential conflict during the initial stages of an event involving not following the commands of an activated TCAS RA, in sufficient time to act in order to prevent a collision. One mitigation barrier has been identified:
These barriers are identified in the TCAS-dedicated SISG study and are based on a wide literature search and consultation.
Analysis of the effectiveness of the safety barriers against the generic scenarios has shown that the three prevention barriers cited above achieve limited effectiveness (i.e. they are effective in a small number of situation types). However, the "Training and enforcement of SOPs requiring TCAS RAs to be followed" barrier could prevent the events where pilots detect and interpret the RA but decide not to follow it. Experience has shown that the decision not to follow a TCAS RA is the most common cause for such events. Therefore, this barrier could be beneficial from a practical point of view.
In contrast, the mitigation barrier cited above achieves high effectiveness (i.e. is effective for most of the generic scenarios). However, this capability currently is only available on new models from one manufacturer, with a retrofit being available for older fleet aircraft. For the time being, it is unlikely that this capability will become available from any other manufacturer due to patenting issues.
TCAS RA Not Followed A&I Examples
- A310 / B736, en-route, Southern Norway, 2001 (On 21 February 2001, a level bust 10 nm north of Oslo Airport by a climbing PIA A310 led to loss of separation with an SAS B736 in which response to a TCAS RA by the A310 not being in accordance with its likely activation (descend). The B736 received and correctly actioned a Climb RA.)
- A319 / PRM1, en-route, near Fribourg Switzerland, 2011 (On 10 June 2011 an ATC error put a German Wings A319 and a Hahn Air Raytheon 390 on conflicting tracks over Switzerland and a co-ordinated TCAS RA followed. The aircraft subsequently passed in very close proximity without either sighting the other after the Hahn Air crew, contrary to Company procedures, followed an ATC descent clearance issued during their TCAS ‘Climb’ RA rather than continuing to fly the RA. The Investigation could find no explanation for this action by the experienced crew - both Hahn Air management pilots. The recorded CPA was 0.6 nm horizontally at 50 feet vertically.)
- A320 / B738, en-route, near Córdoba Spain, 2014 (On 30 October 2014, a descending Airbus A320 came close to a Boeing 737-800 at around FL 220 after the A320 crew significantly exceeded a previously-instructed 2,000 fpm maximum rate of descent assuming it no longer applied when not reiterated during re-clearance to a lower altitude. Their response to a TCAS RA requiring descent at not above 1,000 fpm was to further increase it from 3,200 fpm. Lack of notification delayed the start of an independent Investigation but it eventually found that although the A320 TCAS equipment had been serviceable, its crew denied failing to correctly follow their initial RA.)
- A320 / B738, en-route, north northwest of Sofia Bulgaria, 2016 (On 4 June 2016, a Boeing 737-800 instructed to climb from FL340 to FL380 by the controller of one sector in Bulgarian upper airspace came into sufficiently close proximity to an Airbus A320 under the control of a different sector controller to trigger co-ordinated TCAS RAs. Separation was eventually restored after the 737 followed its RA despite the A320, which had already deviated from its clearance on the basis of a prior TCAS TA without informing ATC, ignoring their RA. The Investigation found that the root cause of the conflict had been inadequate coordination between two vertically separated ATC sectors.)
- A320/B738, vicinity Delhi India, 2013 (On 2 September 2013, a B737 crew were not instructed to go around from their approach by ATC as it became increasingly obvious that an A320 departing the same runway would not be airborne in time for a landing clearance to be issued. They initiated a go around over the threshold and then twice came into conflict with the A320 as both climbed on similar tracks without ATC de-confliction, initially below the height where TCAS RAs are functional. Investigation attributed the conflict to ATC but the failure to effectively deal with the consequences jointly to ATC and both aircraft crews.)
- B752 / B752, en-route, north of Tenerife Spain 2011 (On 20 November 2011, a problem in reading the altitude labels on the ATC radar control display led to a Finnair Boeing 757 being cleared to make a descent which brought it into proximity with a Thomas Cook Boeing 757 in day VMC. Co-ordinated TCAS RAs were generated onboard both aircraft but when the Finnair aircraft failed to respond to its Climb RA and continued descent, the other aircraft, which had responded correctly to its initial RA, received a further RA to reverse their descent to a climb. The Finnair aircraft reported retaining visual contact with the other aircraft throughout.)
- C525 / B773, vicinity London City UK, 2009 (On 27 July 2009, a Cessna 525 departing from London City failed to comply with the initial 3000 feet QNH SID Stop altitude and at 4000 feet QNH in day VMC came into close proximity on an almost reciprocal heading with a Boeing 777-300ER. The 777, on which line training was being conducted, failed to follow any of the three TCAS RAs generated. Actual minimum separation was approximately 0.5nm laterally and estimated at between 100 feet and 200 feet vertically. It was noted that the Cessna had been given a stepped climb SID.)
- DH8A/DH8C, en-route, northern Canada, 2011 (On 7 February 2011 two Air Inuit DHC8s came into head-to-head conflict en route over the eastern shoreline of Hudson Bay in non radar Class ‘A airspace when one of them deviated from its cleared level towards the other which had been assigned the level 1000 feet below. The subsequent investigation found that an inappropriate FD mode had been used to maintain the assigned level of the deviating aircraft and noted deficiencies at the Operator in both TCAS pilot training and aircraft defect reporting as well as a variation in altitude alerting systems fitted to aircraft in the DHC8 fleet.)
- DH8D / DH8D, vicinity Sudbury ON Canada, 2016 (On 14 October 2016, two Bombardier DHC8-400s received coordinated TCAS RAs as they came into opposite direction conflict near Sudbury, an uncontrolled airport, as one was descending inbound and emerging from an overcast layer and the other was level just below that layer after departing. Both aircraft crews ignored their RAs and their respective visual manoeuvring brought them to within 0.4nm at the same altitude. The Investigation noted that the conflict had occurred in Class ‘E’ airspace after the departing aircraft had cancelled IFR to avoid a departure delay attributable to the inbound IFR aircraft.)
- E55P, Blackbushe UK, 2015 (On 31 July 2015 a Saudi-operated Embraer Phenom on a private flight continued an unstabilised day visual approach to Blackbushe in benign weather conditions. The aircraft touched down with excess speed with almost 70% of the available landing distance behind the aircraft. It overran and was destroyed by impact damage and fire and all occupants died. The Investigation concluded that the combination of factors which created a very high workload for the pilot "may have saturated his mental capacity, impeding his ability to handle new information and adapt his mental model" leading to his continuation of a highly unstable approach.)
- F100 / EC45, vicinity Bern Switzerland, 2012 (On 24 May 2012, a Fokker 100 descending visual downwind to land at Berne and an EC145 helicopter transiting the Bern CTR (Class 'D' airspace) VFR came within 0.7 nm horizontally and 75 ft vertically despite early traffic advice having been given to both aircraft. The Investigation attributed the conflict to the failure of the F100 crew to follow either their initial TCAS RA or a subsequent revised one and noted that although STCA was installed at Berne it had been disabled "many years before".)
- F900 / B772, en-route, near Kihnu Island Estonia, 2013 (On 17 October 2013, a Falcon 900 climbing as cleared to FL 340 and being operated as a State Aircraft equipped with TCAS II v7.0 initially responded to a TCAS RA against crossing traffic at FL 350 in day VMC in the opposite direction to the one directed and prescribed separation was lost as a result. The Investigation concluded that the F900 crew had commenced a climb on receipt of a TCAS RA 'ADJUST VERTICAL SPEED' when a reduction in the 800 fpm rate of climb was required. Safety Recommendations were made in respect of TCAS RA requirements for State Aircraft.)
- Airborne Collision Avoidance System (ACAS)
- ACAS Regulation and Procedures
- ACAS Resolution and Traffic Advisories
- Assessment of Pilot Compliance with TCAS RA Using Radar Data
- ATC Avoiding Instructions Opposite to TCAS RA
- TCAS II version 7.1
- ‘Climb’ RAs and Performance Limitations
- TCAS - Always follow the RA (SKYclip)
- The Assessment of Pilot Compliance with TCAS RAs, TCAS Mode Selection and Serviceability Using ATC Radar Data, EUROCONTROL, 1 Oct 2020
- TCAS pilot compliance assessment based on radar data - Presentation, EUROCONTROL, 21 Sept 2020
- ACAS RA Not Followed, a study by the EUROCONTROL SISG, 2017