If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user



Semantic search

  • C525 / B773, vicinity London City UK, 2009 (Synopsis: 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.)
  • GLF5 / A319, south-eastern France, 2004 (Synopsis: On 16 September 2004, a loss of separation occurred over Geneva between Air France A319 and a Gulfstream 5 which commenced descent without clearance by ATC and with coordinated TCAS RAs not followed by either aircraft.)
  • H25B, vicinity Kerry Ireland, 2015 (Synopsis: On 16 June 2015, the crew of a US-operated HS125 on a commercial air transport flight failed to continue climbing as cleared to FL200 after take off from Kerry for a transatlantic flight and instead levelled at 2000 feet on track towards higher terrain. Prompt ATC recognition of the situation and intervention to direct an immediate climb resolved the imminent CFIT risk. The Investigation found that the two pilots involved had, despite correct readback, interpreted their clearance to flight level two hundred as being to two thousand feet and then failed to seek clarification from ATC when they became confused.)
  • A310, vicinity Birmingham UK, 2006 (Synopsis: On 24 November 2006, an A310 descended significantly below cleared altitude during a radar vectored approach positioning, as a result of the flight crew's failure to set the QNH, which was unusually low.)
  • A310 / B736, en-route, Southern Norway, 2001 (Synopsis: 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.)
  • BE20/SF34, vicinity Stornoway UK, 2011 (Synopsis: On 31 December 2011 a USAF C12 Beech King Air descended 700 feet below the cleared outbound altitude on a procedural non precision approach to Stornoway in uncontrolled airspace in IMC and also failed to fly the procedure correctly. As a result it came into conflict with a Saab 340 inbound on the same procedure. The Investigation found that the C12 crew had interpreted the QNH given by ATC as 990 hPa as 29.90 inches, the subscale setting units used in the USA. The Saab 340 pilot saw the opposite direction traffic on TCAS and descended early to increase separation.)
  • A388, vicinity Moscow Domodedovo Russia, 2017 (Synopsis: On 10 September 2017, an Airbus A380-800 cleared for an ILS approach at Moscow Domodedovo in visual daylight conditions descended below its cleared altitude and reached 395 feet agl whilst still 7nm from the landing runway threshold with a resultant EGPWS ‘PULL UP’ warning. Recovery was followed by an inadequately prepared second approach which was discontinued and then a third approach to a landing. The Investigation attributed the crew’s difficulties primarily to failure to follow various routine operating procedures relating to use of automation but noted that there had been scope for better presentation of some of these procedures.)
  • A319/B733, en-route, near Moutiers France, 2010 (Synopsis: On 8 July 2010 an Easyjet Airbus A319 on which line training was being conducted mis-set a descent level despite correctly reading it back and, after subsequently failing to notice an ATC re-iteration of the same cleared level, continued descent to 1000 feet below it in day VMC and into conflict with crossing traffic at that level, a Boeing 737. The 737 received and actioned a TCAS RA ‘CLIMB’ and the A319, which received only a TCAS TA, was given an emergency turn by ATC. The recorded CPA was 2.2 nm and 125 feet.)
  • A319 / A321, en-route, west north west of Geneva, Switzerland 2011 (Synopsis: On 6 August 2011 an Easyjet Airbus A319 on which First Officer Line Training was in progress exceeded its cleared level during the climb after a different level to that correctly read back was set on the FMS. As a result, it came into conflict with an Alitalia A321 and this was resolved by responses to coordinated TCAS RAs. STCA alerts did not enable ATC resolution of the conflict and it was concluded that a lack of ATC capability to receive Mode S EHS DAPs - since rectified - was a contributory factor to the outcome.)
  • A321 / B738, en-route, south eastern Bulgaria, 2016 (Synopsis: On 8 September 2016, an Airbus A321 en route in Bulgarian airspace at FL 350 was given and acknowledged a descent but then climbed and came within 1.2nm of a descending Boeing 737. The Investigation found that the inexperienced A321 First Officer had been temporarily alone when the instruction was given and had insufficient understanding of how to control the aircraft. It was also found that despite an STCA activation of the collision risk, the controller, influenced by a Mode ‘S’ downlink of the correctly-set A321 cleared altitude, had then added to the risk by instructing the 737 to descend.)
  • B773, en route, northern Turkey, 2014 (Synopsis: On 8 August 2014, the First Officer of a Boeing 777 in the cruise at night at FL340 inadvertently input a change of desired track into the MCP selected altitude window whilst acting as both PF and PM during controlled rest by the aircraft commander. The aircraft then descended for nearly 2 minutes without her awareness until ATC queried the descent and it was arrested at FL317.)
  • DH8D / B772, vicinity Sydney Australia, 2016 (Synopsis: On 9 December 2016, a Bombardier DHC8-400 departing Sydney lost prescribed separation against an inbound Boeing 777-200 after its crew failed to ensure that the aircraft levelled as cleared at 5,000 feet and this was exceeded by 600 feet. The Investigation found that the First Officer, as Pilot Flying, had disconnected the autopilot prior to routinely changing the selected airspeed because it tended to disconnect when this was done with altitude capture mode active but had then failed to re-engage it. The Captain's lack of effective monitoring was attributed to distraction as he sought to visually acquire the conflicting traffic.)