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

 Actions

Special

Semantic search

  • B773, vicinity Toronto Canada, 2012 (Synopsis: On 28 May 2012 a GE90-powered Air Canada Boeing 777-300ER experienced sudden failure of the right engine during the initial climb after take off. There were no indications of associated engine fire and the failed engine was secured, fuel jettisoned and a return to land made. The Investigation found that the failure was related to a known manufacturing defect which was being controlled by repetitive boroscope inspections, the most recent of which was suspected not to have identified deterioration in the affected part of the engine.)
  • DC10, Sioux City USA, 1989 (Synopsis: On 19 July 1989, a GE CF6-6D-powered Douglas DC-10-10 at FL370 suffered a sudden explosive failure of the tail-mounted number 2 engine and a complete loss of hydraulics so that the aircraft could only be controlled by varying thrust on the remaining two engines. With only limited flightpath control, the subsequent Sioux City emergency landing led to the destruction of the aircraft by impact and fire. The Investigation attributed the engine failure to non-identification of a fan disc fatigue crack arising from a manufacturing defect and the loss of hydraulics to debris dispersal which had exceeded the system’s certification protection.)
  • IL76, vicinity Karachi Pakistan, 2010 (Synopsis: On 27 November 2010, collateral damage to the wing of an IL-76 in the vicinity of an uncontained engine failure, which occurred soon after take-off from Karachi, led to fuel in that wing igniting. Descent from a maximum height of 600 feet occurred accompanied by a steadily increasing right bank. Just under a minute after take-off ground impact occurred and impact forces and fire destroyed the aircraft. The Investigation concluded that the engine failure was attributable to component fatigue in the LP compressor and that it would have been impossible for the crew to retain control.)
  • MD82, Copenhagen Denmark, 2013 (Synopsis: On 30 January 2013, the crew of a Boeing MD82 successfully rejected its take off at Copenhagen after sudden explosive failure of the left hand JT8D engine occurred during the final stage of setting take off thrust. Full directional control of the aircraft was retained and the failure was contained, but considerable engine debris was deposited on the runway. The subsequent Investigation concluded that a massive failure within the low pressure turbine had been initiated by the fatigue failure of one blade, the reason for which could not be established.)
  • RJ85, en-route, near Musina South Africa, 2017 (Synopsis: On 8 November 2017, an Avro RJ85 in cruise after just crossing into South African airspace from Zimbabwe suddenly experienced the apparently simultaneous failure of both left hand engines. After reviewing their situation, it was decided to continue to Johannesburg and this was achieved without further event. The Investigation found that the initiating failure was that of the number 2 (inner) engine which failed mechanically as a consequence of maintenance error but that this failure was uncontained and turbine debris from the number 2 hit the number 1 engine FADEC box and caused that engine to shut down too.)