title: SKYbrary Accidents and Incidents link: https://skybrary.aero/accidents-and-incidents description: Latest accidents and incidents recorded by the SKYbrary project. generator: ITSB last-modified: 2024-03-28T13:42:38Z language: en errorsto: lucidiot@brainshit.fr title: MD11, en-route, Atlantic Ocean near Halifax Canada, 1998 link: https://skybrary.aero/accidents-and-incidents/md11-en-route-atlantic-ocean-near-halifax-canada-1998 description:

On 2 September 1998, an MD-11 aircraft belonging to Swissair, crashed into the sea off Nova Scotia following an in-flight electrical fire.

guid: https://skybrary.aero/accidents-and-incidents/md11-en-route-atlantic-ocean-near-halifax-canada-1998 uri: https://skybrary.aero/accidents-and-incidents/md11-en-route-atlantic-ocean-near-halifax-canada-1998 title: DC93, en-route, Cincinnati OH USA, 1983 link: https://skybrary.aero/accidents-and-incidents/dc93-en-route-cincinnati-oh-usa-1983 description:

On 2 June 1983, a DC9 aircraft operated by Air Canada was destroyed following an in-flight fire which began in one of the aircraft s toilets. 23 passengers died in the accident.

guid: https://skybrary.aero/accidents-and-incidents/dc93-en-route-cincinnati-oh-usa-1983 uri: https://skybrary.aero/accidents-and-incidents/dc93-en-route-cincinnati-oh-usa-1983 title: LJ35, Aberdeen SD USA, 1999 link: https://skybrary.aero/accidents-and-incidents/lj35-aberdeen-sd-usa-1999 description:

On 25 October 1999, a Learjet 35, being operated on a passenger charter flight by Sunjet Aviation, crashed in South Dakota following loss of control attributed to crew incapacitation.

guid: https://skybrary.aero/accidents-and-incidents/lj35-aberdeen-sd-usa-1999 uri: https://skybrary.aero/accidents-and-incidents/lj35-aberdeen-sd-usa-1999 title: AS50, en-route, Hawaii USA, 2005 link: https://skybrary.aero/accidents-and-incidents/as50-en-route-hawaii-usa-2005 description:

On 23 September 2005, an AS350 helicopter, operated by Heli USA Airways, crashed into the sea off Hawaii following loss of control associated with flight into adverse weather conditions.

guid: https://skybrary.aero/accidents-and-incidents/as50-en-route-hawaii-usa-2005 uri: https://skybrary.aero/accidents-and-incidents/as50-en-route-hawaii-usa-2005 title: CRJ1, Lexington KY USA, 2006 link: https://skybrary.aero/accidents-and-incidents/crj1-lexington-ky-usa-2006 description:

On 27 August 2006, a Bombardier CRJ100 cleared for a night take off from runway 22 instead began take off on unlit runway 26. It was too short and the aircraft ran off the end at speed and was destroyed by the subsequent impact and post-crash fire with the deaths of 49 of the 50 occupants - the First Officer surviving with serious injuries. The Investigation found that the actions of the flight crew had caused the accident but noted that insufficiently robust ATC procedures had been contributory and the effects of an ongoing runway extension project had been relevant.

guid: https://skybrary.aero/accidents-and-incidents/crj1-lexington-ky-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/crj1-lexington-ky-usa-2006 title: CL60, Montrose USA, 2004 link: https://skybrary.aero/accidents-and-incidents/cl60-montrose-usa-2004 description:

On 28 November 2004, the crew of a Bombardier Challenger 601 lost control of their aircraft soon after getting airborne from Montrose and it crashed and caught fire killing three occupants and seriously injuring the other three. The Investigation found that the loss of control had been the result of a stall caused by frozen deposits on the upper wing surfaces after the crew had failed to ensure that the wings were clean or utilise the available ground de/anti ice service. It was concluded that the pilots' lack of experience of winter weather operations had contributed to their actions/inactions.

guid: https://skybrary.aero/accidents-and-incidents/cl60-montrose-usa-2004 uri: https://skybrary.aero/accidents-and-incidents/cl60-montrose-usa-2004 title: CL60, Birmingham UK, 2002 link: https://skybrary.aero/accidents-and-incidents/cl60-birmingham-uk-2002 description:

On 4 January 2002, a Bombardier Challenger 604 became very quickly uncontrollable as the crew attempted to rotate for lift off at Birmingham and within a few seconds it had crashed inverted near the airport passenger terminal killing all on board. A rigorous Investigation found that an uncontrollable roll had occurred after an aerodynamic stall attributable to frost on the wings which had been noticed but apparently not considered indicative of a need for de-icing. The exclusively FAA promoted notion of polished frost may have played a part in the pilots decision making and was considered to be dangerously misleading.

guid: https://skybrary.aero/accidents-and-incidents/cl60-birmingham-uk-2002 uri: https://skybrary.aero/accidents-and-incidents/cl60-birmingham-uk-2002 title: DC87, Philadelphia USA, 2006 link: https://skybrary.aero/accidents-and-incidents/dc87-philadelphia-usa-2006 description:

On 7 February 2006, towards the end of a flight to Philadelphia, the crew of a DC8-71F detected possible signs of a fire and eventually a system warning confirming that a fire may be developing in part of the main deck cargo. During the subsequent landing, thick black smoke entered the flight deck and an emergency evacuation was performed immediately after the aircraft stopped. Despite the efforts of the emergency services, the aircraft was subsequently destroyed by fire which the Investigation traced to containers which it was suspected but not proved had been loaded with goods which included lithium batteries.

guid: https://skybrary.aero/accidents-and-incidents/dc87-philadelphia-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/dc87-philadelphia-usa-2006 title: CL60, Teterboro USA, 2005 link: https://skybrary.aero/accidents-and-incidents/cl60-teterboro-usa-2005 description:

On 2 February 2005, a Challenger, belonging to Platinum Jet Management, crashed after taking off from Teterboro, New Jersey, USA. The aircraft's center of gravity was well forward of the forward takeoff limit.

guid: https://skybrary.aero/accidents-and-incidents/cl60-teterboro-usa-2005 uri: https://skybrary.aero/accidents-and-incidents/cl60-teterboro-usa-2005 title: C212, en-route, Bamiyan Afghanistan, 2004 link: https://skybrary.aero/accidents-and-incidents/c212-en-route-bamiyan-afghanistan-2004 description:

On 27 November 2004, a CASA C212 operated by Presidential Airways, crashed in moutainous terrain near Bamiyan, Afghanistan. The aircraft stalled while trying to climb over a ridge.

guid: https://skybrary.aero/accidents-and-incidents/c212-en-route-bamiyan-afghanistan-2004 uri: https://skybrary.aero/accidents-and-incidents/c212-en-route-bamiyan-afghanistan-2004 title: MD82, Little Rock USA, 1999 link: https://skybrary.aero/accidents-and-incidents/md82-little-rock-usa-1999 description:

On 1 June 1999, an MD82 belonging to American Airlines, overran the end of the runway during landing. The captain and 10 passengers were killed.

guid: https://skybrary.aero/accidents-and-incidents/md82-little-rock-usa-1999 uri: https://skybrary.aero/accidents-and-incidents/md82-little-rock-usa-1999 title: DC93, vicinity Charlotte NC USA, 1994 link: https://skybrary.aero/accidents-and-incidents/dc93-vicinity-charlotte-nc-usa-1994 description:

On 2 July 1994, an DC-9 operated by US Air, collided with trees and a house shortly after attempting a missed approach at Charlotte Airport, USA, in heavy thunderstorms. 37 passengers were killed.

guid: https://skybrary.aero/accidents-and-incidents/dc93-vicinity-charlotte-nc-usa-1994 uri: https://skybrary.aero/accidents-and-incidents/dc93-vicinity-charlotte-nc-usa-1994 title: FA20, vicinity Narsarsuaq Greenland, 2001 link: https://skybrary.aero/accidents-and-incidents/fa20-vicinity-narsarsuaq-greenland-2001 description:

On 5 August 2001, a Dassault Falcon 20 with an inoperative GPWS making a night approach to Narsarsuaq by visual reference impacted terrain 4.5 nm from the aerodrome. The Investigation noted the original crew intention to fly a non-precision instrument approach and attributed the accident to the failure of the crew to follow applicable procedures or engage in meaningful CRM as well as to deficiencies in the Operator's required procedures which had combined to leave the crew vulnerable to a 'black hole' effect. The effects of fatigue were considered likely to have been contributory.

guid: https://skybrary.aero/accidents-and-incidents/fa20-vicinity-narsarsuaq-greenland-2001 uri: https://skybrary.aero/accidents-and-incidents/fa20-vicinity-narsarsuaq-greenland-2001 title: B752, Girona Spain, 1999 link: https://skybrary.aero/accidents-and-incidents/b752-girona-spain-1999 description:

On 14th September 1999, a Britannia Airways Boeing 757 crash landed and departed the runway after a continued unstabilised approach in bad weather to Girona airport, Spain.

guid: https://skybrary.aero/accidents-and-incidents/b752-girona-spain-1999 uri: https://skybrary.aero/accidents-and-incidents/b752-girona-spain-1999 title: B734, Brisbane Australia, 2001 link: https://skybrary.aero/accidents-and-incidents/b734-brisbane-australia-2001 description:

On 18th January 2001, a Qantas Boeing 737-400 encountered a Microburst while conducting a go-around at Brisbane Australia.

guid: https://skybrary.aero/accidents-and-incidents/b734-brisbane-australia-2001 uri: https://skybrary.aero/accidents-and-incidents/b734-brisbane-australia-2001 title: AS32, en-route, North Sea UK, 2002 link: https://skybrary.aero/accidents-and-incidents/as32-en-route-north-sea-uk-2002 description:

On 28th February 2002, an Aerospatiale AS332L Super Puma helicopter en route approximately 70 nm northeast of Scatsa, Shetland Islands was in the vicinity of a storm cell when a waterspout was observed about a mile abeam. Soon afterwards, violent pitch, roll and yaw with significant negative and positive g occurred. Recovery to normal flight was achieved after 15 seconds and after a control check, the flight was completed. After flight, all five tail rotor blades and tail pylon damage were discovered. It was established that this serious damage was the result of contact between the blades and the pylon.

guid: https://skybrary.aero/accidents-and-incidents/as32-en-route-north-sea-uk-2002 uri: https://skybrary.aero/accidents-and-incidents/as32-en-route-north-sea-uk-2002 title: B744, en-route, north of Anchorage AK USA, 1989 link: https://skybrary.aero/accidents-and-incidents/b744-en-route-north-anchorage-ak-usa-1989 description:

On 15 December 1989, a Boeing 747-400 positioning for a planned en-route stop at Anchorage with crew awareness of a significant volcanic eruption in progress some 150 nm upwind entered volcanic ash during descent north northeast of the airport. When an attempt to climb out of the ash using full thrust was made, all engines failed. After repeated and eventually successful engine restart attempts as a 13,000 feet loss of altitude occurred, the fight was completed. The Report of the comprehensive NTSB Investigation remains unpublished with only a brief factual report containing neither Safety Recommendations nor Safety Actions issued.

guid: https://skybrary.aero/accidents-and-incidents/b744-en-route-north-anchorage-ak-usa-1989 uri: https://skybrary.aero/accidents-and-incidents/b744-en-route-north-anchorage-ak-usa-1989 title: DHC2, Squaw Lake Quebec Canada, 2005 link: https://skybrary.aero/accidents-and-incidents/dhc2-squaw-lake-quebec-canada-2005 description:

On 1st September 2005, a DHC-2 Beaver, crashed near Squaw Lake, Quebec, Canada, following loss of control in poor weather and moderate to severe turbulence.

guid: https://skybrary.aero/accidents-and-incidents/dhc2-squaw-lake-quebec-canada-2005 uri: https://skybrary.aero/accidents-and-incidents/dhc2-squaw-lake-quebec-canada-2005 title: D228, vicinity Bodø Norway, 2003 link: https://skybrary.aero/accidents-and-incidents/d228-vicinity-bodo-norway-2003 description:

On 4 December 2003, the crew of a Dornier 228 approaching Bodø lost control of their aircraft after a lightning strike which temporarily blinded both pilots and damaged the aircraft such that the elevator was uncontrollable. After regaining partial pitch control using pitch trim, a second attempt at a landing resulted in a semi-controlled crash which seriously injured both pilots and damaged the aircraft beyond repair. The Investigation concluded that the energy in the lightning had probably exceeded certification resilience requirements and that up to 30% of the bonding wiring in the tail may have been defective before lightning struck.

guid: https://skybrary.aero/accidents-and-incidents/d228-vicinity-bodo-norway-2003 uri: https://skybrary.aero/accidents-and-incidents/d228-vicinity-bodo-norway-2003 title: C172, Toronto Canada, 2003 link: https://skybrary.aero/accidents-and-incidents/c172-toronto-canada-2003 description:

On 9th October 2003, a Cessna 172, suffered loss of power and made a forced landing after experiencing Carburettor Icing, over Toronto, Canada

guid: https://skybrary.aero/accidents-and-incidents/c172-toronto-canada-2003 uri: https://skybrary.aero/accidents-and-incidents/c172-toronto-canada-2003 title: DC10, Tahiti French Polynesia, 2000 link: https://skybrary.aero/accidents-and-incidents/dc10-tahiti-french-polynesia-2000 description:

On 24 December 2000, a Hawaiian Airlines DC10 overran the runway at Tahiti after landing long on a wet runway having encountered crosswinds and turbulence on approach in thunderstorms.

guid: https://skybrary.aero/accidents-and-incidents/dc10-tahiti-french-polynesia-2000 uri: https://skybrary.aero/accidents-and-incidents/dc10-tahiti-french-polynesia-2000 title: MD11, Dublin Ireland, 2002 link: https://skybrary.aero/accidents-and-incidents/md11-dublin-ireland-2002 description:

On 3 February 2002, a Delta Airlines MD-11 encountered a sudden exceptional wind gust (43 kts) during the landing roll at Dublin, Ireland. The pilot was unable to maintain the directional control of the aircraft and a runway excursion to the side subsequently occurred.

guid: https://skybrary.aero/accidents-and-incidents/md11-dublin-ireland-2002 uri: https://skybrary.aero/accidents-and-incidents/md11-dublin-ireland-2002 title: CONC, vicinity Paris Charles de Gaulle France, 2000 link: https://skybrary.aero/accidents-and-incidents/conc-vicinity-paris-charles-de-gaulle-france-2000 description:

On 25th July 2000, an Air France Concorde crashed shortly after take-off from Paris CDG following loss of control after debris from an explosive tyre failure between V1 and VR attributed to runway FOD ruptured a fuel tank and led to a fuel-fed fire which quickly resulted in loss of engine thrust and structural damage which made the aircraft impossible to fly. It was found that nothing the crew failed to do, including rejecting the take off after V1 could have prevented the loss of the aircraft and that they had been faced with entirely unforeseen circumstances.

guid: https://skybrary.aero/accidents-and-incidents/conc-vicinity-paris-charles-de-gaulle-france-2000 uri: https://skybrary.aero/accidents-and-incidents/conc-vicinity-paris-charles-de-gaulle-france-2000 title: B763, Manchester UK, 1998 link: https://skybrary.aero/accidents-and-incidents/b763-manchester-uk-1998 description:

On 25th November 1998, baggage containers on a B767, moved in flight causing damage to a cabin floor beam and damage to the standby system power supply cable causing electrical arcing. The aircraft landed safely at Manchester, UK, and the damage was only discovered during unloading.

guid: https://skybrary.aero/accidents-and-incidents/b763-manchester-uk-1998 uri: https://skybrary.aero/accidents-and-incidents/b763-manchester-uk-1998 title: DC10, Newburgh NY USA, 1996 link: https://skybrary.aero/accidents-and-incidents/dc10-newburgh-ny-usa-1996 description:

On 5 September 1996, a DC10 operated by Fedex, was destroyed by fire shortly after landing at Newburgh, USA, following a fire in the cargo compartment.

guid: https://skybrary.aero/accidents-and-incidents/dc10-newburgh-ny-usa-1996 uri: https://skybrary.aero/accidents-and-incidents/dc10-newburgh-ny-usa-1996 title: DC93, en-route, north west of Miami USA, 1996 link: https://skybrary.aero/accidents-and-incidents/dc93-en-route-north-west-miami-usa-1996 description:

On 11 May 1996, the crew of a ValuJet DC9-30 were unable to keep control of their aircraft after fire broke out. The origin of the fire was found to have been live chemical oxygen generators loaded contrary to regulations. The Investigation concluded that, whilst the root cause was poor practices at SabreTech (the maintenance contractor which handed over oxygen generators in an unsafe condition), the context for this was oversight failure at successive levels - Valujet over SabreTech and the FAA over Valujet. Failure of the FAA to require fire suppression in Class 'D' cargo holds was also cited.

guid: https://skybrary.aero/accidents-and-incidents/dc93-en-route-north-west-miami-usa-1996 uri: https://skybrary.aero/accidents-and-incidents/dc93-en-route-north-west-miami-usa-1996 title: SW4, Mirabel Montreal Canada, 1998 link: https://skybrary.aero/accidents-and-incidents/sw4-mirabel-montreal-canada-1998 description:

On 18 June 1998, the crew of a Swearingen SA226 did not associate directional control difficulty and an extended take off ground run at Montreal with a malfunctioning brake unit. Subsequent evidence of hydraulic problems prompted a decision to return but when evidence of control difficulties and fire in the left engine followed, a single engine diversion to Mirabel was flown where, just before touchdown, the left wing failed upwards. All occupants were killed when the aircraft crashed inverted. The Investigation found that overheated brakes had caused an engine nacelle fire which spread and eventually caused the wing failure.

guid: https://skybrary.aero/accidents-and-incidents/sw4-mirabel-montreal-canada-1998 uri: https://skybrary.aero/accidents-and-incidents/sw4-mirabel-montreal-canada-1998 title: S61, vicinity Bournemouth UK, 2002 link: https://skybrary.aero/accidents-and-incidents/s61-vicinity-bournemouth-uk-2002 description:

On 15 July 2002, a Sikorsky S-61 helicopter operated by Bristow suffered a catastrophic engine failure and fire. After an emergency landing and evacuation, the aircraft was destroyed by an intense fire.

guid: https://skybrary.aero/accidents-and-incidents/s61-vicinity-bournemouth-uk-2002 uri: https://skybrary.aero/accidents-and-incidents/s61-vicinity-bournemouth-uk-2002 title: C177, vicinity Calling Lake Alberta Canada, 2000 link: https://skybrary.aero/accidents-and-incidents/c177-vicinity-calling-lake-alberta-canada-2000 description:

On 30th May 2000, a Cessna 177 lost control shortly after take-off from Calling Lake, Alberta, Canada, crashed and suffered a post crash fire.

guid: https://skybrary.aero/accidents-and-incidents/c177-vicinity-calling-lake-alberta-canada-2000 uri: https://skybrary.aero/accidents-and-incidents/c177-vicinity-calling-lake-alberta-canada-2000 title: DC10, Sioux City USA, 1989 link: https://skybrary.aero/accidents-and-incidents/dc10-sioux-city-usa-1989 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/dc10-sioux-city-usa-1989 uri: https://skybrary.aero/accidents-and-incidents/dc10-sioux-city-usa-1989 title: C404, Glasgow UK, 1999 link: https://skybrary.aero/accidents-and-incidents/c404-glasgow-uk-1999 description:

On 3rd September 1999, shortly after take-off from Glasgow UK, a Cessna 404 experienced an engine failure which was mishandled, leading to loss of control, and the aircraft was destroyed by a post-crash fire.

guid: https://skybrary.aero/accidents-and-incidents/c404-glasgow-uk-1999 uri: https://skybrary.aero/accidents-and-incidents/c404-glasgow-uk-1999 title: T154 / B752, en-route, Uberlingen Germany, 2002 link: https://skybrary.aero/accidents-and-incidents/t154-b752-en-route-uberlingen-germany-2002 description:

On 1st July 2002, a Russian-operated Tu154 on a passenger flight collided at night with a cargo Boeing 757-200 over Überlingen, Germany with the consequent loss of control of both aircraft and the death of all occupants. The collision occurred after an ATC control lapse had led to a conflict which generated coordinated TCAS RAs which the B757 followed but the TU-154, in the presence of a conflicting ATC instruction, did not.

guid: https://skybrary.aero/accidents-and-incidents/t154-b752-en-route-uberlingen-germany-2002 uri: https://skybrary.aero/accidents-and-incidents/t154-b752-en-route-uberlingen-germany-2002 title: TOR / C152, en-route, Mattersey Nottinghamshire UK, 1999 link: https://skybrary.aero/accidents-and-incidents/tor-c152-en-route-mattersey-nottinghamshire-uk-1999 description:

On 21 January 1999, a UK Royal Air Force Tornado GR1 and a private Cessna 152 collided in mid air, at low level in day VMC with the resultant loss of both aircraft and the death of all occupants.

guid: https://skybrary.aero/accidents-and-incidents/tor-c152-en-route-mattersey-nottinghamshire-uk-1999 uri: https://skybrary.aero/accidents-and-incidents/tor-c152-en-route-mattersey-nottinghamshire-uk-1999 title: B744 / A321, vicinity London Heathrow UK, 2000 link: https://skybrary.aero/accidents-and-incidents/b744-a321-vicinity-london-heathrow-uk-2000 description:

On 28 April 2000, a British Airways Boeing 747-400 on go around at London Heathrow Airport, UK, had a loss of separation vertically from a British Midland A321 stationary on the runway waiting for take-off.

guid: https://skybrary.aero/accidents-and-incidents/b744-a321-vicinity-london-heathrow-uk-2000 uri: https://skybrary.aero/accidents-and-incidents/b744-a321-vicinity-london-heathrow-uk-2000 title: B744 / A306, vicinity London Heathrow UK, 1996 link: https://skybrary.aero/accidents-and-incidents/b744-a306-vicinity-london-heathrow-uk-1996 description:

On 15 April 1996 a significant loss of separation occurred when a B744, taking off from runway 27R at London Heathrow came into conflict to the west of Heathrow Airport with an A306 which had carried out a missed approach from the parallel runway 27L. Both aircraft were following ATC instructions. Both aircraft received and correctly followed TCAS RAs, the B744 to descend and the A306 to adjust vertical speed, which were received at the same time as corrective ATC clearances.

guid: https://skybrary.aero/accidents-and-incidents/b744-a306-vicinity-london-heathrow-uk-1996 uri: https://skybrary.aero/accidents-and-incidents/b744-a306-vicinity-london-heathrow-uk-1996 title: B737 / B737, vicinity Geneva Switzerland, 2006 link: https://skybrary.aero/accidents-and-incidents/b737-b737-vicinity-geneva-switzerland-2006 description:

On 11 May 2006, B737-700 taking off from Geneva came into close proximity with a Boeing Business Jet (BBJ) on a non revenue positioning flight which had commenced a go around from the same runway following an unstabilised approach. The Investigation attributed the conflict to the decision of ATC to give take off clearance to the departing aircraft when the approach of the inbound aircraft could have been seen as highly likely to result is a go around which would lead to proximity with the slower departing aircraft.

guid: https://skybrary.aero/accidents-and-incidents/b737-b737-vicinity-geneva-switzerland-2006 uri: https://skybrary.aero/accidents-and-incidents/b737-b737-vicinity-geneva-switzerland-2006 title: H500 / D150, en-route, North of London UK, 2007 link: https://skybrary.aero/accidents-and-incidents/h500-d150-en-route-north-london-uk-2007 description:

On 5 October 2007, a loss of separation occurred between a Hughes 369 helicopter and a Jodel D150. The incident occurred outside controlled airspace, in VMC, and the estimated vertical separation as the Jodel took avoiding action by descending, was assessed by both pilots to be less than 50 feet.

guid: https://skybrary.aero/accidents-and-incidents/h500-d150-en-route-north-london-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/h500-d150-en-route-north-london-uk-2007 title: D150 / H500, London UK, 2007 link: https://skybrary.aero/accidents-and-incidents/d150-h500-london-uk-2007 description:

On 5 October 2007, a loss of separation occurred between a Hughes 369 helicopter and a Jodel D150. The incident occurred outside controlled airspace, in VMC, and the estimated vertical separation as the Jodel took avoiding action by descending, was assessed by both pilots to be less than 50 feet.

guid: https://skybrary.aero/accidents-and-incidents/d150-h500-london-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/d150-h500-london-uk-2007 title: BE20, vicinity Gallatin Field MT USA, 2007 link: https://skybrary.aero/accidents-and-incidents/be20-vicinity-gallatin-field-mt-usa-2007 description:

On February 6, 2007, a Beech 200 King Air, being operated by Metro Aviation on an EMS positioning flight from Great Falls MT to Gallatin Field MT, collided at night in VMC with mountainous terrain approximately 13 nm north-northwest of the intended destination shortly after advising that the airport was in sight and requesting and obtaining permission for a visual approach.

guid: https://skybrary.aero/accidents-and-incidents/be20-vicinity-gallatin-field-mt-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/be20-vicinity-gallatin-field-mt-usa-2007 title: LJ35, vicinity Masset BC Canada, 1995 link: https://skybrary.aero/accidents-and-incidents/lj35-vicinity-masset-bc-canada-1995 description:

On 11 January 1995, a Learjet 35 on a medical positioning flight and carrying a medical team crashed into the sea while conducting an NDB approach to Masset, British Columbia, Canada. The most probable cause was considered to be a miss-set altimeter.

guid: https://skybrary.aero/accidents-and-incidents/lj35-vicinity-masset-bc-canada-1995 uri: https://skybrary.aero/accidents-and-incidents/lj35-vicinity-masset-bc-canada-1995 title: A320, vicinity Addis Ababa Ethiopia, 2003 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-addis-ababa-ethiopia-2003 description:

On 31 March 2003, an A320, operated by British Mediterranean AW, narrowly missed colliding with terrain during a non-precision approach to Addis Ababa, Ethiopia.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-addis-ababa-ethiopia-2003 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-addis-ababa-ethiopia-2003 title: C185, Smithers BC Canada, 2000 link: https://skybrary.aero/accidents-and-incidents/c185-smithers-bc-canada-2000 description:

On 27 September 2000, a Cessna 185, struck a snow covered hillside, probably while in controlled flight, en-route from Smithers BC, Canada.

guid: https://skybrary.aero/accidents-and-incidents/c185-smithers-bc-canada-2000 uri: https://skybrary.aero/accidents-and-incidents/c185-smithers-bc-canada-2000 title: D328, vicinity Manchester UK, 2006 link: https://skybrary.aero/accidents-and-incidents/d328-vicinity-manchester-uk-2006 description:

On 18 January 2006, a Dornier 328 on descent into Manchester UK, avoided CFIT only by response to EGPWS following failure to capture the ILS Glideslope and a high rate of descent in IMC.

guid: https://skybrary.aero/accidents-and-incidents/d328-vicinity-manchester-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/d328-vicinity-manchester-uk-2006 title: T154, vicinity Svalbard Norway, 1996 link: https://skybrary.aero/accidents-and-incidents/t154-vicinity-svalbard-norway-1996 description:

On 29 August 1996, a Tu-154, crashed after misflying an off-set LLZ non-precision approach to Svalbard Longyear airport, Norway, in IMC.

guid: https://skybrary.aero/accidents-and-incidents/t154-vicinity-svalbard-norway-1996 uri: https://skybrary.aero/accidents-and-incidents/t154-vicinity-svalbard-norway-1996 title: MD11, vicinity East Midlands UK, 2005 link: https://skybrary.aero/accidents-and-incidents/md11-vicinity-east-midlands-uk-2005 description:

On 3 December 2005, the crew of a MD-11 freighter failed to set the (very low) QNH for a night approach, due to distraction, and as a result descended well below the cleared altitude given by ATC for the intercept heading for the ILS at Nottingham East Midlands airport, UK.

guid: https://skybrary.aero/accidents-and-incidents/md11-vicinity-east-midlands-uk-2005 uri: https://skybrary.aero/accidents-and-incidents/md11-vicinity-east-midlands-uk-2005 title: A310, vicinity Birmingham UK, 2006 link: https://skybrary.aero/accidents-and-incidents/a310-vicinity-birmingham-uk-2006 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a310-vicinity-birmingham-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/a310-vicinity-birmingham-uk-2006 title: B734 / MD81, en-route, Romford UK, 1996 link: https://skybrary.aero/accidents-and-incidents/b734-md81-en-route-romford-uk-1996 description:

On 12 November 1996, a B737-400 descended below its assigned level in one of the holding patterns at London Heathrow in day IMC to within 100 feet vertically and between 680 and 820 metres horizontally of a MD-81 at its correct level, 1000 feet below. STCA prompted ATC to intervene and the 737 climbed back to its cleared level. Neither aircraft was fitted with TCAS 2 or saw the other visually.

guid: https://skybrary.aero/accidents-and-incidents/b734-md81-en-route-romford-uk-1996 uri: https://skybrary.aero/accidents-and-incidents/b734-md81-en-route-romford-uk-1996 title: B744, en-route, South China Sea, 2008 link: https://skybrary.aero/accidents-and-incidents/b744-en-route-south-china-sea-2008 description:

On 25 July 2008, a Boeing 747 suffered a rapid depressurisation of the cabin following the sudden failure of an oxygen cylinder, which had ruptured the aircraft's pressure hull. The incident occurred 475 km north-west of Manila, Philippines.

guid: https://skybrary.aero/accidents-and-incidents/b744-en-route-south-china-sea-2008 uri: https://skybrary.aero/accidents-and-incidents/b744-en-route-south-china-sea-2008 title: B772, London Heathrow UK, 2008 link: https://skybrary.aero/accidents-and-incidents/b772-london-heathrow-uk-2008 description:

On 17 January 2008, a British Airways Boeing 777 200ER crash-landed 330 metres short of the intended landing runway, 27L, at London Heathrow after a loss of engine thrust on short final. This un-commanded reduction of thrust was found to have been the result of ice causing a restriction in the fuel feed system. Prompt crew response minimized the extent of the inevitable undershoot so that it occurred within the airport perimeter.

guid: https://skybrary.aero/accidents-and-incidents/b772-london-heathrow-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/b772-london-heathrow-uk-2008 title: MD87 / C525, Milan Linate, 2001 link: https://skybrary.aero/accidents-and-incidents/md87-c525-milan-linate-2001 description:

On 8th October 2001, an SAS MD-87 taking off as cleared from Milan Linate in thick fog collided at high speed with a German-operated Cessna Citation which had failed to follow its taxi clearance and unknown to ATC had eventually crossed a lit red stop bar and entered the active runway just as the MD-87 was reaching the same point. After the collision, the MD-87 continued along the ground until it impacted, still at high speed, a ground handling building. Both aircraft caught fire and were destroyed. The 114 occupants of both aircraft and 4 ground personnel were killed.

guid: https://skybrary.aero/accidents-and-incidents/md87-c525-milan-linate-2001 uri: https://skybrary.aero/accidents-and-incidents/md87-c525-milan-linate-2001 title: B762 / A310, Toronto Canada, 2001 link: https://skybrary.aero/accidents-and-incidents/b762-a310-toronto-canada-2001 description:

On 23 October 2001, at Toronto Pearson Airport, a B767 cleared for take-off was forced to reject the take-off when a tractor towing an A310 crossed the runway ahead of it. The tractor had been cleared to cross the active runway by ATC.

guid: https://skybrary.aero/accidents-and-incidents/b762-a310-toronto-canada-2001 uri: https://skybrary.aero/accidents-and-incidents/b762-a310-toronto-canada-2001 title: SH33 / MD83, Paris CDG France, 2000 link: https://skybrary.aero/accidents-and-incidents/sh33-md83-paris-cdg-france-2000 description:

On the 25th of May, 2000 a UK-operated Shorts SD330 waiting for take-off at Paris CDG in normal visibility at night on a taxiway angled in the take-off direction due to its primary function as an exit for opposite direction landings was given a conditional line up clearance by a controller who had erroneously assumed without checking that it was at the runway threshold. After an aircraft which had just landed had passed, the SD330 began to line up unaware that an MD83 had just been cleared in French to take off from the full length and a collision occurred.

guid: https://skybrary.aero/accidents-and-incidents/sh33-md83-paris-cdg-france-2000 uri: https://skybrary.aero/accidents-and-incidents/sh33-md83-paris-cdg-france-2000 title: C340 / A332, Copenhagen Denmark, 2003 link: https://skybrary.aero/accidents-and-incidents/c340-a332-copenhagen-denmark-2003 description:

On 8 September 2003, a privately operated Cessna 340 departing the apron at Copenhagen failed to follow its correctly acknowledged taxi clearance and took a different route which led it to pass the holding point of a runway on which an Air Greenland Airbus 330 had just received take off clearance. ATC observed the error and the clearance was cancelled so that no actual risk of collision had existed. The Investigation considered that the taxi error had occurred at a position conducive to such errors and criticised what it considered were the inappropriate designations of the taxiways involved.

guid: https://skybrary.aero/accidents-and-incidents/c340-a332-copenhagen-denmark-2003 uri: https://skybrary.aero/accidents-and-incidents/c340-a332-copenhagen-denmark-2003 title: DHC6 / E145, Glasgow UK, 2006 link: https://skybrary.aero/accidents-and-incidents/dhc6-e145-glasgow-uk-2006 description:

On 29 August 2006, a Loganair DHC-6 began to taxi onto an intersecting active runway at Glasgow just an Embraer 145 was about to touch down on it but after a late sighting had reverse taxied clear so that there was no actual collision risk. It was found that the incursion had been contrary to the accepted ATC clearance and indirectly attributable to distraction. It was also noted that TWR controllers did not have an adequate understanding of the installed RIMCAS system with the result that the inappropriate mode set had not provided an alert at the point of incursion.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-e145-glasgow-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/dhc6-e145-glasgow-uk-2006 title: A310, Irkutsk Russia, 2006 link: https://skybrary.aero/accidents-and-incidents/a310-irkutsk-russia-2006 description:

On 8 July 2006, S7 Airlines A310 overran the runway on landing at Irkutsk at high speed and was destroyed after the Captain mismanaged the thrust levers whilst attempting to apply reverse only on one engine because the flight was being conducted with one reverser inoperative. The Investigation noted that the aircraft had been despatched on the accident flight with the left engine thrust reverser de-activated as permitted under the MEL but also that the previous two flights had been carried out with a deactivated right engine thrust reverser.

guid: https://skybrary.aero/accidents-and-incidents/a310-irkutsk-russia-2006 uri: https://skybrary.aero/accidents-and-incidents/a310-irkutsk-russia-2006 title: A332 / RJ1H, vicinity Zurich Switzerland, 2004 link: https://skybrary.aero/accidents-and-incidents/a332-rj1h-vicinity-zurich-switzerland-2004 description:

On 31 October 2004, a Loss of Separation occurred between an A330-200, on a low go-around from Rwy 14 at Zurich Switzerland, and an Avro RJ100 which had been cleared for take-off on Rwy 10 and was on a convergent flight path.

guid: https://skybrary.aero/accidents-and-incidents/a332-rj1h-vicinity-zurich-switzerland-2004 uri: https://skybrary.aero/accidents-and-incidents/a332-rj1h-vicinity-zurich-switzerland-2004 title: B763, en-route, New York NY USA, 2000 link: https://skybrary.aero/accidents-and-incidents/b763-en-route-new-york-ny-usa-2000 description:

On 30 March 2000, a Delta Airlines-operated Boeing 767-300 which was 15nm southeast of New York JFK after departure from there and was being flown visually at night by the First Officer with an 'international relief pilot' as extra crew on the flight deck, achieved 66 degrees of right bank before any of the the pilots noticed. A successful recovery was made with no consequences for the occupants and the aircraft then returned to JFK.

guid: https://skybrary.aero/accidents-and-incidents/b763-en-route-new-york-ny-usa-2000 uri: https://skybrary.aero/accidents-and-incidents/b763-en-route-new-york-ny-usa-2000 title: B763, en-route, Atlantic Ocean, 2008 link: https://skybrary.aero/accidents-and-incidents/b763-en-route-atlantic-ocean-2008 description:

On 28 January 2008, the first officer on a B767, flying from Toronto to London, became incapacitated and the captain elected to divert to the nearest airport, Shannon, Ireland.

guid: https://skybrary.aero/accidents-and-incidents/b763-en-route-atlantic-ocean-2008 uri: https://skybrary.aero/accidents-and-incidents/b763-en-route-atlantic-ocean-2008 title: A306, vicinity New York JFK, 2001 link: https://skybrary.aero/accidents-and-incidents/a306-vicinity-new-york-jfk-2001 description:

On 12 November 2001, an Airbus A300-600 encountered mild wake turbulence as it climbed after departing New York JFK to which the First Officer responded with a series of unnecessary and excessive control inputs involving cyclic full-deflection rudder pedal inputs. Within less than 7 seconds, these caused detachment of the vertical stabiliser from the aircraft resulting in loss of control and ground impact with a post crash fire. The Investigation concluded that elements of the company pilot training process and the design of the A300-600 rudder system had contributed to this excessive use of the rudder and its consequences.

guid: https://skybrary.aero/accidents-and-incidents/a306-vicinity-new-york-jfk-2001 uri: https://skybrary.aero/accidents-and-incidents/a306-vicinity-new-york-jfk-2001 title: MD83, vicinity Nantes France, 2004 link: https://skybrary.aero/accidents-and-incidents/md83-vicinity-nantes-france-2004 description:

On 21 March 2004, an MD-83 operated by Luxor Air, performed an unstabilised non-precision approach (NPA) to runway 21 at Nantes Atlantique airport, at night and under IMC conditions, which resulted in near-CFIT and a go around contrary to the standard missed approach procedure.

guid: https://skybrary.aero/accidents-and-incidents/md83-vicinity-nantes-france-2004 uri: https://skybrary.aero/accidents-and-incidents/md83-vicinity-nantes-france-2004 title: MD81, vicinity Stockholm Arlanda Sweden, 1991 link: https://skybrary.aero/accidents-and-incidents/md81-vicinity-stockholm-arlanda-sweden-1991 description:

On 27 December 1991, an MD-81 took off after airframe ground de/anti icing treatment but soon afterwards both engines began surging and both then failed. A successful crash landing with no fatalities was achieved four minutes after take off after the aircraft emerged from cloud approximately 900 feet above terrain. There was no post-crash fire. The Investigation found that undetected clear ice on the upper wing surfaces had been ingested into both engines during rotation and initiated engine surging. Without awareness of the aircraft's automated thrust increase system, the pilot response did not control the surging and both engines failed.

guid: https://skybrary.aero/accidents-and-incidents/md81-vicinity-stockholm-arlanda-sweden-1991 uri: https://skybrary.aero/accidents-and-incidents/md81-vicinity-stockholm-arlanda-sweden-1991 title: B752, vicinity Gardermoen Oslo Norway, 2002 link: https://skybrary.aero/accidents-and-incidents/b752-vicinity-gardermoen-oslo-norway-2002 description:

On 22 of January 2002, a Boeing 757-200 operated by Icelandair commenced an unstabilised approach to Oslo Gardermoen airport in instrument meteorological conditions (IMC) and in the presence of a strong tail wind. The result was a near loss of control and low altitude go-around with exceedance of speed limits and g-values exerted on the airframe.

guid: https://skybrary.aero/accidents-and-incidents/b752-vicinity-gardermoen-oslo-norway-2002 uri: https://skybrary.aero/accidents-and-incidents/b752-vicinity-gardermoen-oslo-norway-2002 title: C208, vicinity Pelee Island Canada, 2004 link: https://skybrary.aero/accidents-and-incidents/c208-vicinity-pelee-island-canada-2004 description:

On 17 January, 2004 a Cessna 208 Caravan operated by Georgian Express, took off from Pellee Island, Ontario, Canada, at a weight significantly greater than maximum permitted and with ice visible on the airframe. Shortly after take off, the pilot lost control of the aircraft and it crashed into a frozen lake.

guid: https://skybrary.aero/accidents-and-incidents/c208-vicinity-pelee-island-canada-2004 uri: https://skybrary.aero/accidents-and-incidents/c208-vicinity-pelee-island-canada-2004 title: P46T, vicinity Son Bonet Palma de Mallorca Spain, 2002 link: https://skybrary.aero/accidents-and-incidents/p46t-vicinity-son-bonet-palma-de-mallorca-spain-2002 description:

On 19 December 2002, a Piper PA-46 Malibu, after takeoff from Son Bonet Aerodrome, penetrated the control zone (CTR) of Palma de Mallorca tower. The pilot was instructed to leave the CTR and the aircraft headed towards mountainous terrain to the north of the island where the flight conditions were below the VFR minimum. In level flight the aircraft impacted terrain at an altitude of 2000 ft killing all three occupants.

guid: https://skybrary.aero/accidents-and-incidents/p46t-vicinity-son-bonet-palma-de-mallorca-spain-2002 uri: https://skybrary.aero/accidents-and-incidents/p46t-vicinity-son-bonet-palma-de-mallorca-spain-2002 title: DHC6, vicinity Saint Barthelemy French Antilles, 2001 link: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-saint-barthelemy-french-antilles-2001 description:

On 24 March 2001, a De Havilland DHC-6, operated by Caraïbes Air Transport, lost control during a VFR approach to Saint Barthelemy airport in the French Antilles. On short final the aircraft took a sharp left turn which resulted in impact with the terrain.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-saint-barthelemy-french-antilles-2001 uri: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-saint-barthelemy-french-antilles-2001 title: EC55, en-route, Hong Kong China, 2003 link: https://skybrary.aero/accidents-and-incidents/ec55-en-route-hong-kong-china-2003 description:

On 26 August 2003, at night, a Eurocopter EC155, operated by Hong Kong Government Flight Service (GFS), performing a casualty evacuation mission (casevac), impacted the elevated terrain in Tung Chung Gap near Hong Kong International airport.

guid: https://skybrary.aero/accidents-and-incidents/ec55-en-route-hong-kong-china-2003 uri: https://skybrary.aero/accidents-and-incidents/ec55-en-route-hong-kong-china-2003 title: SW4, en-route, Taranaki Province New Zealand, 2005 link: https://skybrary.aero/accidents-and-incidents/sw4-en-route-taranaki-province-new-zealand-2005 description:

On 3 May 2005, Fairchild-Swearingen SA227 (Metro III), operated by Airwork (NZ) Limited, was on a night air transport freight flight when it suffered a loss of control which developed into a spiral dive. The crew did not recover the control and the aircraft became overstressed which resulted in an in-flight break up and terrain impact, killing both crewmembers.

guid: https://skybrary.aero/accidents-and-incidents/sw4-en-route-taranaki-province-new-zealand-2005 uri: https://skybrary.aero/accidents-and-incidents/sw4-en-route-taranaki-province-new-zealand-2005 title: B703, Sydney Australia, 1969 link: https://skybrary.aero/accidents-and-incidents/b703-sydney-australia-1969 description:

On 1 December 1969, a Boeing 707-320 being operated by Pan Am and making a daylight take off from Sydney, Australia ran into a flock of gulls just after V1 and prior to rotation and after a compressor stall and observed partial loss of thrust on engine 2 (only), the aircraft commander elected to reject the take off. Despite rapid action to initiate maximum braking and the achievement of full reverse thrust on all engines including No 2, this resulted in an overrun of the end of the runway by 170m and substantial aircraft damage. A full emergency evacuation was carried out with no injuries to any of the occupants. There was no fire.

guid: https://skybrary.aero/accidents-and-incidents/b703-sydney-australia-1969 uri: https://skybrary.aero/accidents-and-incidents/b703-sydney-australia-1969 title: B763, vicinity Gatwick UK, 1999 link: https://skybrary.aero/accidents-and-incidents/b763-vicinity-gatwick-uk-1999 description:

On 18 October 1999, a Boeing 767-300 encountered a flock of wood pigeons, at 450 feet agl after take off from London Gatwick, and the ingestion of one caused sufficient distress to the left engine for it to be shut down and an air turn back made; it was subsequently concluded that the degree of damage caused was inconsistent with the applicable requirements of engine certification.

guid: https://skybrary.aero/accidents-and-incidents/b763-vicinity-gatwick-uk-1999 uri: https://skybrary.aero/accidents-and-incidents/b763-vicinity-gatwick-uk-1999 title: B763, vicinity London Heathrow UK, 1998 link: https://skybrary.aero/accidents-and-incidents/b763-vicinity-london-heathrow-uk-1998 description:

On 1 September 1998, a Boeing 767-300 had a bird strike with a large flock of geese moments before touchdown at London Heathrow airport, causing substantial damage.

guid: https://skybrary.aero/accidents-and-incidents/b763-vicinity-london-heathrow-uk-1998 uri: https://skybrary.aero/accidents-and-incidents/b763-vicinity-london-heathrow-uk-1998 title: B741, vicinity London Heathrow UK, 1997 link: https://skybrary.aero/accidents-and-incidents/b741-vicinity-london-heathrow-uk-1997 description:

On 6 December 1997, a British Airways Boeing 747-100, departing from London Heathrow airport, had an engine bird strike just after take off, causing substantial damage and falling debris.

guid: https://skybrary.aero/accidents-and-incidents/b741-vicinity-london-heathrow-uk-1997 uri: https://skybrary.aero/accidents-and-incidents/b741-vicinity-london-heathrow-uk-1997 title: DC91, vicinity Kansas City MO USA, 1999 link: https://skybrary.aero/accidents-and-incidents/dc91-vicinity-kansas-city-mo-usa-1999 description:

On March 4, 1999, a DC91 operated by USA Jet Airlines, at night and on final approach to land at Kansas City International Airport encountered a flock of large birds. The crew managed to regain sufficient thrust to continue the approach and land without further incident.

guid: https://skybrary.aero/accidents-and-incidents/dc91-vicinity-kansas-city-mo-usa-1999 uri: https://skybrary.aero/accidents-and-incidents/dc91-vicinity-kansas-city-mo-usa-1999 title: B763, vicinity Chicago IL USA, 2007 link: https://skybrary.aero/accidents-and-incidents/b763-vicinity-chicago-il-usa-2007 description:

On March 15, 2007, at night, a Boeing 767-300, operated by United Airlines, experienced a bird strike after take-off from Chicago O'Hare International Airport, Chicago, Illinois. The airplane ecountered a flock of ducks about 800 feet above ground level (AGL) resulting in the complete failure of the left engine. The crew was able to land the airplane safely.

guid: https://skybrary.aero/accidents-and-incidents/b763-vicinity-chicago-il-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/b763-vicinity-chicago-il-usa-2007 title: CRJ2, Washington Dulles VA USA, 2002 link: https://skybrary.aero/accidents-and-incidents/crj2-washington-dulles-va-usa-2002 description:

On March 9, 2002, a Bombardier CRJ 200 ER, operating by Atlantic Coast Airlines, encountered a flock of wild turkeys at a late stage in the take off roll Washington Dulles International Airport and a bird strike followed. The aircraft rejected take off and returned to gate.

guid: https://skybrary.aero/accidents-and-incidents/crj2-washington-dulles-va-usa-2002 uri: https://skybrary.aero/accidents-and-incidents/crj2-washington-dulles-va-usa-2002 title: C172, McKinney TX USA, 2003 link: https://skybrary.aero/accidents-and-incidents/c172-mckinney-tx-usa-2003 description:

On 8 July 2003, a Cessna 172S on an instructional flight hit a vulture which caused significant structural damage to the left wing. During the attempted forced landing which followed, control of the aircraft was lost and the aircraft crashed into terrain near McKinney TX USA.

guid: https://skybrary.aero/accidents-and-incidents/c172-mckinney-tx-usa-2003 uri: https://skybrary.aero/accidents-and-incidents/c172-mckinney-tx-usa-2003 title: C310, vicinity Wolf Point MT USA, 2000 link: https://skybrary.aero/accidents-and-incidents/c310-vicinity-wolf-point-mt-usa-2000 description:

On 25 May 2000, a commercially operated Cessna 310R on a positioning flight encountered a flock of geese in VMC at about 600 feet agl after a daylight take off from Wolf Point MT and one of the geese impacted and broke through the windscreen causing the pilot to loose control and the aircraft to crash.

guid: https://skybrary.aero/accidents-and-incidents/c310-vicinity-wolf-point-mt-usa-2000 uri: https://skybrary.aero/accidents-and-incidents/c310-vicinity-wolf-point-mt-usa-2000 title: F100, vicinity La Guardia NY USA, 2003 link: https://skybrary.aero/accidents-and-incidents/f100-vicinity-la-guardia-ny-usa-2003 description:

On 4 September 2003, an American Airlines Fokker F100 hit five Canada Geese, just after becoming airborne from New York La Guardia airport, with resultant failure of the No 2 engine and substantial airframe damage. The aircraft carried out an uneventful diversion to New York JFK.

guid: https://skybrary.aero/accidents-and-incidents/f100-vicinity-la-guardia-ny-usa-2003 uri: https://skybrary.aero/accidents-and-incidents/f100-vicinity-la-guardia-ny-usa-2003 title: B752, vicinity Cincinnati KY USA, 1999 link: https://skybrary.aero/accidents-and-incidents/b752-vicinity-cincinnati-ky-usa-1999 description:

On 22 February 1999, a Boeing 757-200 operated by Delta Air Lines, penetrated a large flock of Starlings during takeoff from Cincinnati/Northern Kentucky International Airport, Covington, Kentucky. The bird strike resulted in substantial damage to both engines but with no significant effect on the control of the airplane which made an uneventful return to land.

guid: https://skybrary.aero/accidents-and-incidents/b752-vicinity-cincinnati-ky-usa-1999 uri: https://skybrary.aero/accidents-and-incidents/b752-vicinity-cincinnati-ky-usa-1999 title: B762, vicinity Busan Korea, 2002 link: https://skybrary.aero/accidents-and-incidents/b762-vicinity-busan-korea-2002 description:

On 15 April 2002, a Boeing 767-200 attempting a circling approach at Busan in poor visibility crashed into terrain after failing to follow the prescribed procedure or go around when sight of the runway was lost. 129 of the 166 occupants were killed. The Investigation attributed the accident to actions and inactions of the pilots but noted that the aircraft operator bore considerable contextual responsibility for the poor crew performance. It was also concluded that ATC could have done more to manage the risk procedurally and tactically on the day and that ATM regulatory requirements did not adequately address risk.

guid: https://skybrary.aero/accidents-and-incidents/b762-vicinity-busan-korea-2002 uri: https://skybrary.aero/accidents-and-incidents/b762-vicinity-busan-korea-2002 title: SH36, vicinity East Midlands UK, 1986 link: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-east-midlands-uk-1986 description:

On 31 January 1986, at night during an instrument approach, a Shorts SD3-60 operated by Aer Lingus Commuter experienced a loss of control attributed to airframe ice accretion. When fully established on the Instrument Landing System (ILS), the aircraft began a series of divergent rolling oscillations which were accompanied by a very high rate of descent. The crew was able to regain control of the aircraft just before contact with power cables and subsequent impact with terrain near East Midlands Airport.

guid: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-east-midlands-uk-1986 uri: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-east-midlands-uk-1986 title: B742, Halifax Canada, 2004 link: https://skybrary.aero/accidents-and-incidents/b742-halifax-canada-2004 description:

On 14 October 2004, a B742 crashed on take off from Halifax International Airport, Canada, and was destroyed by impact forces and a post-crash fire. The crew had calculated incorrect V speeds and thrust setting using an EFB.

guid: https://skybrary.aero/accidents-and-incidents/b742-halifax-canada-2004 uri: https://skybrary.aero/accidents-and-incidents/b742-halifax-canada-2004 title: DH8D, en-route, South West of Glasgow UK, 2006 link: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-west-glasgow-uk-2006 description:

On 10 December 2006, a DHC-8-Q400, operated by Flybe, experienced multiple flight instrument failures whilst in icing conditions at night which were consistent with icing of the pitot/static system. After descending out of icing conditions all displays returned normal functionality and the pitot/static heaters were noted to have been off and were then correctly selected.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-west-glasgow-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-west-glasgow-uk-2006 title: A333, en-route, West of Learmonth Australia, 2008 link: https://skybrary.aero/accidents-and-incidents/a333-en-route-west-learmonth-australia-2008 description:

On 7 October 2008, an Airbus A330-300 aircraft experienced multiple system failure indications followed by uncommanded pitch-down events which resulted in serious injuries to passengers and cabin crew.

guid: https://skybrary.aero/accidents-and-incidents/a333-en-route-west-learmonth-australia-2008 uri: https://skybrary.aero/accidents-and-incidents/a333-en-route-west-learmonth-australia-2008 title: E195, en-route, Edinburgh UK, 2009 link: https://skybrary.aero/accidents-and-incidents/e195-en-route-edinburgh-uk-2009 description:

On 15 January 2009, an Embraer 195-200 being operated by UK Regional Airline Flybe was passing overhead Edinburgh UK at FL370 at night when communications problems between the flight deck and cabin crew occurred following the selection of emergency power as a precautionary measure after smoke, considered to possibly be of electrical origin, had been observed in the galley. An en route diversion with an uneventful outcome was accomplished.

guid: https://skybrary.aero/accidents-and-incidents/e195-en-route-edinburgh-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/e195-en-route-edinburgh-uk-2009 title: CVLT, en-route, Kapiti Coast New Zealand, 2003 link: https://skybrary.aero/accidents-and-incidents/cvlt-en-route-kapiti-coast-new-zealand-2003 description:

On 3 October 2003, a Convair 580 on a scheduled night freight flight from Christchurch to Palmerston North, was observed on radar to enter a tightening left turn and disappear while descending through an area of severe icing. The aircraft impacted the sea vertically and at high speed.

guid: https://skybrary.aero/accidents-and-incidents/cvlt-en-route-kapiti-coast-new-zealand-2003 uri: https://skybrary.aero/accidents-and-incidents/cvlt-en-route-kapiti-coast-new-zealand-2003 title: C404, Kulusuk Greenland, 2002 link: https://skybrary.aero/accidents-and-incidents/c404-kulusuk-greenland-2002 description:

On 1 August 2002, a Cessna 404, en-route at FL130 over Greenland, experienced sudden power loss on both engines, probably as a result of ice in the induction systems, leading to loss of control. The crew regained control at 3000 feet.

guid: https://skybrary.aero/accidents-and-incidents/c404-kulusuk-greenland-2002 uri: https://skybrary.aero/accidents-and-incidents/c404-kulusuk-greenland-2002 title: B744, Gardermoen Norway, 2004 link: https://skybrary.aero/accidents-and-incidents/b744-gardermoen-norway-2004 description:

On 21 September 2004, a Korean Air Boeing 747-400F experienced handling difficulties on take off due to the Centre of Gravity (CofG) being aft of the limit as a result of misloading.

guid: https://skybrary.aero/accidents-and-incidents/b744-gardermoen-norway-2004 uri: https://skybrary.aero/accidents-and-incidents/b744-gardermoen-norway-2004 title: C208, Helsinki Finland, 2005 link: https://skybrary.aero/accidents-and-incidents/c208-helsinki-finland-2005 description:

On 31 January 2005, the pilot of a Cessna 208 which had just taken off from Helsinki lost control of their aircraft as the flaps were retracted and the aircraft stalled, rolled to the right and crashed within the airport perimeter. The Investigation found that the take off had been made without prior airframe de/anti icing and that accumulated ice and snow on the upper wing surfaces had led to airflow separation and the stall, a condition which the pilot had failed to recognise or respond appropriately to for undetermined reasons.

guid: https://skybrary.aero/accidents-and-incidents/c208-helsinki-finland-2005 uri: https://skybrary.aero/accidents-and-incidents/c208-helsinki-finland-2005 title: AT45, Sienajoki Finland, 2006 link: https://skybrary.aero/accidents-and-incidents/at45-sienajoki-finland-2006 description:

On 11 December 2006, a Finnish Commuter Airlines ATR 42-500 veered off the runway on landing at Seinäjoki, Finland.

guid: https://skybrary.aero/accidents-and-incidents/at45-sienajoki-finland-2006 uri: https://skybrary.aero/accidents-and-incidents/at45-sienajoki-finland-2006 title: SH36, vicinity Marsa Brega Libya, 2000 link: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-marsa-brega-libya-2000 description:

On 13 January 2000, a Shorts SD3-60 suffered a double engine failure on approach to Marsa Brega, Libya, attributed to failure to use engine anti-icing during flight in icing conditions. The aircraft ditched into the sea and was destroyed by impact forces.

guid: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-marsa-brega-libya-2000 uri: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-marsa-brega-libya-2000 title: A320, vicinity Perpignan France, 2008 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-perpignan-france-2008 description:

On 27 November 2008, the crew of an XL Airways A320 on an airworthiness function flight following aircraft repainting lost control of the aircraft after fail to take the action necessary to recover from a full stall which had resulted from their continued airspeed reduction during a low speed handling test when Stall Protection System (SPS) activation did nor occur at the likely airspeed because two of the three angle of attack sensors were blocked by ice formed by water ingress during preparation for the repainting. This condition rendered angle of attack protection in normal law inoperative.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-perpignan-france-2008 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-perpignan-france-2008 title: B772, Denver CO USA, 2001 link: https://skybrary.aero/accidents-and-incidents/b772-denver-co-usa-2001 description:

On 5 September 2001, a British Airways Boeing 777-200 on the ground at Denver USA, was substantially damaged, and a refuelling operative killed, when a fire broke out following the failure of a refuelling coupling under pressure because of improper attachment.

guid: https://skybrary.aero/accidents-and-incidents/b772-denver-co-usa-2001 uri: https://skybrary.aero/accidents-and-incidents/b772-denver-co-usa-2001 title: BA11, en-route, Didcot UK, 1990 link: https://skybrary.aero/accidents-and-incidents/ba11-en-route-didcot-uk-1990 description:

On 10 June 1990, a BAC One-Eleven climbing through FL173 suddenly lost its left windscreen when the increasing cabin differential pressure overcame undersized securing bolts. The Captain was sucked almost completely out of the resulting aperture and was restrained by cabin crew whilst the First Officer declared a MAYDAY and diverted to Southampton. Only on the ground was it possible to recover the seriously injured Captain into the flight deck. The flight was the first since the windscreen had been replaced and the maintenance error involved was attributed to the presence of systemic failures in maintenance practices and their oversight.

guid: https://skybrary.aero/accidents-and-incidents/ba11-en-route-didcot-uk-1990 uri: https://skybrary.aero/accidents-and-incidents/ba11-en-route-didcot-uk-1990 title: Q9, vicinity Nogales USA, 2006 link: https://skybrary.aero/accidents-and-incidents/q9-vicinity-nogales-usa-2006 description:

On April 25, 2006 a Predator B an unmanned aerial vehicle (UAV), collided with the terrain following a loss of engine power approximately 10 nautical miles northwest of the Nogales International Airport, Nogales, Arizona.

guid: https://skybrary.aero/accidents-and-incidents/q9-vicinity-nogales-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/q9-vicinity-nogales-usa-2006 title: F27, vicinity Guernsey Channel Islands, 1999 link: https://skybrary.aero/accidents-and-incidents/f27-vicinity-guernsey-channel-islands-1999 description:

On 12 January 1999, control of a Fokker F27-600 was lost on approach to Guernsey Airport, Channel Islands, as a consequence of the aircraft being operated outside the load and balance limitations.

guid: https://skybrary.aero/accidents-and-incidents/f27-vicinity-guernsey-channel-islands-1999 uri: https://skybrary.aero/accidents-and-incidents/f27-vicinity-guernsey-channel-islands-1999 title: MD83, en-route, Pacific Ocean near Anacapa Island CA USA, 2000 link: https://skybrary.aero/accidents-and-incidents/md83-en-route-pacific-ocean-near-anacapa-island-ca-usa-2000 description:

On 31 January 2000, an Alaskan Airlines MD83, crashed into the sea off the coast of California, USA, following loss of control attributed to failure of the horizontal stabiliser trim system.

guid: https://skybrary.aero/accidents-and-incidents/md83-en-route-pacific-ocean-near-anacapa-island-ca-usa-2000 uri: https://skybrary.aero/accidents-and-incidents/md83-en-route-pacific-ocean-near-anacapa-island-ca-usa-2000 title: G73T, vicinity Miami Seaplane Base FL USA, 2005 link: https://skybrary.aero/accidents-and-incidents/g73t-vicinity-miami-seaplane-base-fl-usa-2005 description:

On 19 December 2005, a Grumman Turbo Mallard Sea Plane suffered a loss of control following the in-flight separation of the right hand wing, Miami Port, Florida, USA.

guid: https://skybrary.aero/accidents-and-incidents/g73t-vicinity-miami-seaplane-base-fl-usa-2005 uri: https://skybrary.aero/accidents-and-incidents/g73t-vicinity-miami-seaplane-base-fl-usa-2005 title: F50, vicinity Luxembourg, 2002 link: https://skybrary.aero/accidents-and-incidents/f50-vicinity-luxembourg-2002 description:

On 6 November 2002, a Fokker 50 operated by Luxair, crashed on approach to Luxembourg Airport following loss of control attributed to intentional operation of power levers in the ground range, contrary to SOPs.

guid: https://skybrary.aero/accidents-and-incidents/f50-vicinity-luxembourg-2002 uri: https://skybrary.aero/accidents-and-incidents/f50-vicinity-luxembourg-2002 title: F70, vicinity Munich Germany, 2004 link: https://skybrary.aero/accidents-and-incidents/f70-vicinity-munich-germany-2004 description:

On 5 January 2004, a Fokker 70, operated by Austrian Airlines, carried out a forced landing in a field 2.5 nm short of Munich Runway 26L following loss of thrust from both engines due to icing.

guid: https://skybrary.aero/accidents-and-incidents/f70-vicinity-munich-germany-2004 uri: https://skybrary.aero/accidents-and-incidents/f70-vicinity-munich-germany-2004 title: F27, vicinity Sharjah UAE, 2004 link: https://skybrary.aero/accidents-and-incidents/f27-vicinity-sharjah-uae-2004 description:

On 10 February 2004, a Fokker F27 operated by Kish Airlines, crashed on approach to Sharjah, UAE, as a result of loss of control caused by selection of both propellers to the ground range in flight.

guid: https://skybrary.aero/accidents-and-incidents/f27-vicinity-sharjah-uae-2004 uri: https://skybrary.aero/accidents-and-incidents/f27-vicinity-sharjah-uae-2004 title: DH8D, vicinity Kalmar Sweden, 2006 link: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-kalmar-sweden-2006 description:

On 6 April 2006, an incorrect response to a propeller malfunction, by the crew of an SAS Dash-8-Q400, resulted in an unstable single engine approach, and operation of the remaining engine outside limits. The aircraft landed safely at Kalmar, Sweden.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-kalmar-sweden-2006 uri: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-kalmar-sweden-2006 title: RJ1H, en-route, South West of Stockholm Sweden, 2007 link: https://skybrary.aero/accidents-and-incidents/rj1h-en-route-south-west-stockholm-sweden-2007 description:

On 22 March 2007, climbing out of Stockholm Sweden, the crew of a Malmö Aviation Avro RJ100 failed to notice that the aircraft was not pressurised until cabin crew advised them of automatic cabin oxygen mask deployment.

guid: https://skybrary.aero/accidents-and-incidents/rj1h-en-route-south-west-stockholm-sweden-2007 uri: https://skybrary.aero/accidents-and-incidents/rj1h-en-route-south-west-stockholm-sweden-2007 title: F900, en-route, South of Bucharest Romania, 1999 link: https://skybrary.aero/accidents-and-incidents/f900-en-route-south-bucharest-romania-1999 description:

On 14 September 1999, a F900 was subjected to rapid and violent vertical load oscillations, which killed most of the passengers, after incorrect crew response to a minor pitch control malfunction.

guid: https://skybrary.aero/accidents-and-incidents/f900-en-route-south-bucharest-romania-1999 uri: https://skybrary.aero/accidents-and-incidents/f900-en-route-south-bucharest-romania-1999 title: LJ35, Lyon France, 2000 link: https://skybrary.aero/accidents-and-incidents/lj35-lyon-france-2000 description:

On 2 May 2000, the crew of a LJ35 lost control of the aircraft, as a result of incorrect manual flying inputs, and crashed just before touchdown at Lyon, following an unstable single engine approach.

guid: https://skybrary.aero/accidents-and-incidents/lj35-lyon-france-2000 uri: https://skybrary.aero/accidents-and-incidents/lj35-lyon-france-2000 title: B412, vicinity Karlsborg Sweden, 2003 link: https://skybrary.aero/accidents-and-incidents/b412-vicinity-karlsborg-sweden-2003 description:

On 25 March 2003, the crew of a Bell 412 lost control of the aircraft as a result of pilot mishandling associated with the development of a Vortex Ring State.

guid: https://skybrary.aero/accidents-and-incidents/b412-vicinity-karlsborg-sweden-2003 uri: https://skybrary.aero/accidents-and-incidents/b412-vicinity-karlsborg-sweden-2003 title: L188, vicinity Stansted UK, 2007 link: https://skybrary.aero/accidents-and-incidents/l188-vicinity-stansted-uk-2007 description:

On 19 March 2007, shortly after take off from Stansted UK, the crew of a Lockheed Electra Freighter being operated by Atlantic Airways experienced control difficulties and power fluctuation on all engines, subsequently attributed to a malfunctioning propeller synchrophaser. The flight crew were unclear what was occurring and proceeded to shut down one engine and believed that the others were at risk of failure during a return to land.

guid: https://skybrary.aero/accidents-and-incidents/l188-vicinity-stansted-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/l188-vicinity-stansted-uk-2007 title: DH8D, vicinity Medford OR USA, 2003 link: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-medford-or-usa-2003 description:

On 8 January 2003, a DHC8-400 sustained multiple bird strikes during a night visual circuit at the Medford airport, OR, USA, resulting in loss of flight displays, multiple false system warnings and the shattering of the LH windscreen. The Captain sustained significant facial injuries and temporary incapacitation with a successful approach and landing being completed by the co-pilot.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-medford-or-usa-2003 uri: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-medford-or-usa-2003 title: GALX, en-route, North East of Newfoundland, Canada, 2007 link: https://skybrary.aero/accidents-and-incidents/galx-en-route-north-east-newfoundland-canada-2007 description:

On 8 February 2007, A Gulfstream G-200 on an eastbound transatlantic delivery flight being undertaken by its operator entered a high altitude stall resulting from crew flight planning errors after which flight at an altitude incompatible with the performance limits of the aircraft as loaded was attempted. The crew response to this situation was confused but eventually, recovery to controlled flight was achieved. The Investigation attributed the event to lack of flight crew understanding of the core principles of flight at high altitude.

guid: https://skybrary.aero/accidents-and-incidents/galx-en-route-north-east-newfoundland-canada-2007 uri: https://skybrary.aero/accidents-and-incidents/galx-en-route-north-east-newfoundland-canada-2007 title: DC93, vicinity Port Harcourt Nigeria, 2005 link: https://skybrary.aero/accidents-and-incidents/dc93-vicinity-port-harcourt-nigeria-2005 description:

On 10 December 2005, a Douglas DC9-32 operated by Sosoliso Airlines descended below the ILS Decision Altitude without visual reference, on approach to Port Harcourt Nigeria, and control was lost during the attempted initiation of a go around, followed by ground impact and post crash fire.

guid: https://skybrary.aero/accidents-and-incidents/dc93-vicinity-port-harcourt-nigeria-2005 uri: https://skybrary.aero/accidents-and-incidents/dc93-vicinity-port-harcourt-nigeria-2005 title: L101, vicinity Riyadh Saudi Arabia, 1980 link: https://skybrary.aero/accidents-and-incidents/l101-vicinity-riyadh-saudi-arabia-1980 description:

On 19 August 1980, a Lockheed L1011 operated by Saudi Arabian Airlines took off from Riyadh, Saudi Arabia - seven minutes later an aural warning indicated a smoke in the aft cargo compartment. Despite the successful landing all 301 persons on board perished due toxic fumes inhalation and uncontrolled fire.

guid: https://skybrary.aero/accidents-and-incidents/l101-vicinity-riyadh-saudi-arabia-1980 uri: https://skybrary.aero/accidents-and-incidents/l101-vicinity-riyadh-saudi-arabia-1980 title: DC10, en-route, Paris France, 1974 link: https://skybrary.aero/accidents-and-incidents/dc10-en-route-paris-france-1974 description:

On 3 March 1974, all 346 occupants were killed when a Turkish Airlines McDonnell Douglas DC 10 suffered an explosive decompression after an improperly secured hold door detached passing 12000ft in the climb shortly after departing Paris Orly. It was found that non-mandated corrective actions promulgated after the investigation into a similar DC10 explosive decompression in Canada nearly two years earlier had identified an identical fault in the door closure mechanism which had allowed it to indicate and appear secured when it was not had not been completed on the aircraft at the time of the accident.

guid: https://skybrary.aero/accidents-and-incidents/dc10-en-route-paris-france-1974 uri: https://skybrary.aero/accidents-and-incidents/dc10-en-route-paris-france-1974 title: B763 / B744, Amsterdam Netherlands, 1998 link: https://skybrary.aero/accidents-and-incidents/b763-b744-amsterdam-netherlands-1998 description:

A Boeing 767-300 departing from runway 24 at Amsterdam made a successful daylight rejected take off upon seeing a Boeing 747-400 under tow crossing the runway ahead. It was found that the crossing clearance had been given by the same trainee controller who had then cleared the 767 for take off after assuming that the towing traffic had cleared based on an unverified assumption based upon incorrect information which had been received earlier from an Assistant Controller. The conflict occurred with LVP in force and with visual surveillance of the runway from the TWR precluded by low cloud.

guid: https://skybrary.aero/accidents-and-incidents/b763-b744-amsterdam-netherlands-1998 uri: https://skybrary.aero/accidents-and-incidents/b763-b744-amsterdam-netherlands-1998 title: MD82, Madrid Barajas Spain, 2008 link: https://skybrary.aero/accidents-and-incidents/md82-madrid-barajas-spain-2008 description:

On 20 August 2008, an MD82 aircraft operated by Spanair took off from Madrid Barajas Airport with flaps and slats retracted; the incorrect configuration resulted in loss of control, collision with the ground, and the destruction of the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/md82-madrid-barajas-spain-2008 uri: https://skybrary.aero/accidents-and-incidents/md82-madrid-barajas-spain-2008 title: MD82, Detroit MI USA, 1987 link: https://skybrary.aero/accidents-and-incidents/md82-detroit-mi-usa-1987 description:

On 16 August 1987, an MD-82 being operated by Northwest Airlines on a scheduled passenger flight from Detroit MI to Phoenix AZ failed to get properly airborne in day VMC and, after damaging impact with obstacles within the airport perimeter after climbing to a maximum height of just under 40 ft, impacted the ground causing the destruction of the aircraft by impact forces and a subsequent fire. All but one of the 157 occupants were killed with the single survivor suffering serious injury. On the ground, 2 people were killed, 2 more seriously injured and 4 more suffered minor injury with several buildings vehicles and structures damaged or destroyed.

guid: https://skybrary.aero/accidents-and-incidents/md82-detroit-mi-usa-1987 uri: https://skybrary.aero/accidents-and-incidents/md82-detroit-mi-usa-1987 title: MD88, Groningen Netherlands, 2003 link: https://skybrary.aero/accidents-and-incidents/md88-groningen-netherlands-2003 description:

On 17 June 2003, a crew of a Boeing MD-88, belonging to Onur Air, executed a high speed rejected take-off at a late stage which resulted in overrun of the runway and serious damage to the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/md88-groningen-netherlands-2003 uri: https://skybrary.aero/accidents-and-incidents/md88-groningen-netherlands-2003 title: B772, London Heathrow UK, 2007 link: https://skybrary.aero/accidents-and-incidents/b772-london-heathrow-uk-2007 description:

On 26 February 2007, a Boeing 777-222 operated by United Airlines, after pushback from the stand at London Heathrow Airport, experienced internal failure of an electrical component which subsequently led to under-floor fire. The aircraft returned to a stand where was attended by the Airfield Fire Service and the passengers were evacuated.

guid: https://skybrary.aero/accidents-and-incidents/b772-london-heathrow-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/b772-london-heathrow-uk-2007 title: F15 / E145, en-route, Bedford UK, 2005 link: https://skybrary.aero/accidents-and-incidents/f15-e145-en-route-bedford-uk-2005 description:

On 27 January 2005, two USAF-operated McDonnell Douglas F15E fighter aircraft, both continued to climb and both passed through the level of an Embraer 145 being operated by British Airways Regional on a scheduled passenger flight from Birmingham to Hannover, one seen at an estimated range of 100 feet.

guid: https://skybrary.aero/accidents-and-incidents/f15-e145-en-route-bedford-uk-2005 uri: https://skybrary.aero/accidents-and-incidents/f15-e145-en-route-bedford-uk-2005 title: B744 / MD90, New Chitose Japan, 2008 link: https://skybrary.aero/accidents-and-incidents/b744-md90-new-chitose-japan-2008 description:

On 16 February 2008, during daylight and in poor visibility, a Boeing 747-400, operated by Japan Airlines, was holding on a taxiway next to runway 01R of New Chitose Airport, Japan. A Douglas MD-90-30 operated by the same airline landed on the same runway and was still on the runway when the B747 was cleared to line up and wait. Shortly after lineup the B747 began its takeoff roll without receiving such clearance and subsequently was instructed to abort the takeoff. The crew of the B747 successfully rejected the takeoff.

guid: https://skybrary.aero/accidents-and-incidents/b744-md90-new-chitose-japan-2008 uri: https://skybrary.aero/accidents-and-incidents/b744-md90-new-chitose-japan-2008 title: CRJ7 / CRJ2, Charlotte NC USA, 2008 link: https://skybrary.aero/accidents-and-incidents/crj7-crj2-charlotte-nc-usa-2008 description:

On 28 June 2008, a Bombardier CRJ 700 operated by PSA Airlines, during daytime pushback collided with a stationary CRJ 200 of the same company at Douglas International Airport Charlotte, North Carolina.

guid: https://skybrary.aero/accidents-and-incidents/crj7-crj2-charlotte-nc-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/crj7-crj2-charlotte-nc-usa-2008 title: F15 / B752, en-route, South East of Birmingham UK, 2000 link: https://skybrary.aero/accidents-and-incidents/f15-b752-en-route-south-east-birmingham-uk-2000 description:

On 22 November 2000, near Birmingham UK, a dangerous loss of vertical and lateral separation occurred between a Boeing B757-200 being operated by Britannia Airways on a passenger flight and a formation flight of two F-15Es being operated by the United States Air Force (USAF).

guid: https://skybrary.aero/accidents-and-incidents/f15-b752-en-route-south-east-birmingham-uk-2000 uri: https://skybrary.aero/accidents-and-incidents/f15-b752-en-route-south-east-birmingham-uk-2000 title: B763 / B763, Kansai Japan, 2007 link: https://skybrary.aero/accidents-and-incidents/b763-b763-kansai-japan-2007 description:

On 20 October 2007, at night, a Boeing 767-300 operated by Air Canada was taxiing for Runway 24L at Kansai International Airport for take-off. Meanwhile, another Boeing 767-300, operated by Japan Airlines, had been given landing clearance and was on approach to the same runway. After an incorrect readback, the Air Canada B767 entered the runway to line up. As a consequence of the runway incursion, the B767 on approach executed a go-around on the instructions of air traffic control.

guid: https://skybrary.aero/accidents-and-incidents/b763-b763-kansai-japan-2007 uri: https://skybrary.aero/accidents-and-incidents/b763-b763-kansai-japan-2007 title: B763 / B772, New Chitose Japan, 2007 link: https://skybrary.aero/accidents-and-incidents/b763-b772-new-chitose-japan-2007 description:

On 27 June 2007, a Skymark Boeing 767-300 rejected its night take off from the 3000 metre-long runway 19R at New Chitose from around 80 knots when an All Nippon Boeing 777-200 which had just landed on runway 19L was seen to be taxying across the runway near the far end. There was no actual risk of collision. Both aircraft were being operated in accordance with conflicting air traffic clearances issued by the same controller. None of the three controllers present in the TWR including the Supervisor noticed the error until alerted by the aircraft rejected take off call.

guid: https://skybrary.aero/accidents-and-incidents/b763-b772-new-chitose-japan-2007 uri: https://skybrary.aero/accidents-and-incidents/b763-b772-new-chitose-japan-2007 title: AT45 / B733, Munich Germany, 2004 link: https://skybrary.aero/accidents-and-incidents/at45-b733-munich-germany-2004 description:

During the hours of darkness at Munich on 3 May 2004, an ATR42-500 was given a conditional line up clearance for Runway 08R but contrary to this clearance then taxied onto that runway as a Boeing 737-300 was landing on it. The landing aircraft missed the right wingtip of the ATR-42, which continued taxing onto the runway as it approached, by a few metres .

guid: https://skybrary.aero/accidents-and-incidents/at45-b733-munich-germany-2004 uri: https://skybrary.aero/accidents-and-incidents/at45-b733-munich-germany-2004 title: B752, vicinity Cali Colombia, 1995 link: https://skybrary.aero/accidents-and-incidents/b752-vicinity-cali-colombia-1995 description:

On 20 December 1995, an American Airlines Boeing 757-200 inbound to Cali, Colombia made a rushed descent towards final approach at destination and the crew lost positional awareness whilst manoeuvring in night VMC. After the crew failed to stow the fully deployed speed brakes when responding to a GPWS PULL UP Warning, the aircraft impacted terrain and was destroyed with only four seriously injured survivors from the 163 occupants surviving the impact. The accident was attributed entirely to poor flight management on the part of the operating flight crew, although issues related to the FMS were found to have contributed to this.

guid: https://skybrary.aero/accidents-and-incidents/b752-vicinity-cali-colombia-1995 uri: https://skybrary.aero/accidents-and-incidents/b752-vicinity-cali-colombia-1995 title: B742 / B741, Tenerife Canary Islands Spain, 1977 link: https://skybrary.aero/accidents-and-incidents/b742-b741-tenerife-canary-islands-spain-1977 description:

On 27 March 1977, a KLM Boeing 747-200 began its low visibility take-off at Tenerife without requesting or receiving take-off clearance and a collision with a Boeing 747-100 backtracking the same runway subsequently occurred. Both aircraft were destroyed by the impact and consequential fire and 583 people died. The Investigation attributed the crash primarily to the actions and inactions of the KLM Captain, who was the Operator's Chief Flying Instructor. Safety Recommendations made emphasised the importance of standard phraseology in all normal radio communications and avoidance of the phrase take-off in ATC Departure Clearances.

guid: https://skybrary.aero/accidents-and-incidents/b742-b741-tenerife-canary-islands-spain-1977 uri: https://skybrary.aero/accidents-and-incidents/b742-b741-tenerife-canary-islands-spain-1977 title: A319, en-route, Free State Province South Africa, 2008 link: https://skybrary.aero/accidents-and-incidents/a319-en-route-free-state-province-south-africa-2008 description:

On 7 September 2008 a South African Airways Airbus A319 en route from Cape Town to Johannesburg at FL370 received an ECAM warning of the failure of the No 1 engine bleed system. The crew then closed the No. 1 engine bleed with the applicable press button on the overhead panel. The cabin altitude started to increase dramatically and the cockpit crew advised ATC of the pressurisation problem and requested an emergency descent to a lower level. During the emergency descent to 11000 ft amsl, the cabin altitude warning sounded at 33000ft and the flight crew activated the cabin oxygen masks. The APU was started and pressurisation was re-established at 15000ft amsl. The crew completed the flight to the planned destination without any further event. The crew and passengers sustained no injuries and no damage was caused to the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/a319-en-route-free-state-province-south-africa-2008 uri: https://skybrary.aero/accidents-and-incidents/a319-en-route-free-state-province-south-africa-2008 title: B733, Birmingham UK, 2009 link: https://skybrary.aero/accidents-and-incidents/b733-birmingham-uk-2009 description:

On 6 February 2009, the crew of a Boeing 737-300 departing Birmingham successfully rejected take off from well above V1 when it became clear to the First Officer as handling pilot, that it was impossible to rotate. The Investigation found that cause of the rotation difficulty was that the crew had failed to set the stabiliser trim to the appropriate position for take off after delaying this action beyond the normal point in pre flight preparations because ground de icing was in progress and not subsequently noticing.

guid: https://skybrary.aero/accidents-and-incidents/b733-birmingham-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/b733-birmingham-uk-2009 title: B737 / F100, vicinity Geneva Switzerland, 2006 link: https://skybrary.aero/accidents-and-incidents/b737-f100-vicinity-geneva-switzerland-2006 description:

On 29 December 2006, Geneva ATC saw the potential for runway 23 conflict between a departing 737 and an inbound F100 and instructed them to respectively reject take off and go around respectively. Although still at a relatively slow speed, the 737 continued its take off and subsequently lost separation in night IMC against the F100. The Investigation noted that take off clearance for the 737 had been delayed by a slow post-landing runway clearance by a business jet and that the 737 had not begun take off after clearance to do so until instructed to do so immediately.

guid: https://skybrary.aero/accidents-and-incidents/b737-f100-vicinity-geneva-switzerland-2006 uri: https://skybrary.aero/accidents-and-incidents/b737-f100-vicinity-geneva-switzerland-2006 title: B742, Brussels Belgium, 2008 link: https://skybrary.aero/accidents-and-incidents/b742-brussels-belgium-2008 description:

On 25 May 2008 a Kalitta Air B747-200F, which was departing Brussels on a cargo flight to Bahrain, overran Runway 20 at Brussels Airport, Belgium during a rejected take-off. The aircraft came to a stop 300m beyond the end of runway 20 and broke into three parts. The crew of four and one passenger safely evacuated from the aircraft and suffered only minor injuries.

guid: https://skybrary.aero/accidents-and-incidents/b742-brussels-belgium-2008 uri: https://skybrary.aero/accidents-and-incidents/b742-brussels-belgium-2008 title: CRJ2, en-route, Fort St. John BC Canada, 2006 link: https://skybrary.aero/accidents-and-incidents/crj2-en-route-fort-st-john-bc-canada-2006 description:

On 21 November 2006, an Air Canada Jazz CL-600-2B19 on a scheduled flight from Vancouver to Prince George was cleared for a non-precision approach at destination. During a missed approach because of worse than forecast weather conditions, the crew were unable to retract the flaps from their 45 degree landing setting. A diversion to the designated alternate was commenced but en route, ATC were requested to provide radar vectors to Fort St. John and an emergency was declared due to a low fuel prediction on arrival. The aircraft subsequently landed without further problem at Fort St. John with about 500 pounds of fuel remaining, equivalent to less than 10 minutes of flight time.

guid: https://skybrary.aero/accidents-and-incidents/crj2-en-route-fort-st-john-bc-canada-2006 uri: https://skybrary.aero/accidents-and-incidents/crj2-en-route-fort-st-john-bc-canada-2006 title: JS41, en-route, North West of Aberdeen UK, 2008 link: https://skybrary.aero/accidents-and-incidents/js41-en-route-north-west-aberdeen-uk-2008 description:

On 9 April 2008, a BAe Jetstream 41 departed Aberdeen in snow and freezing conditions after the Captain had elected not to have the airframe de/anti iced having noted had noted the delay this would incur. During the climb in IMC, pitch control became problematic and an emergency was declared. Full control was subsequently regained in warmer air. The Investigation concluded that it was highly likely that prior to take off, slush and/or ice had been present on the horizontal tail surfaces and that, as the aircraft entered colder air at altitude, this contamination had restricted the mechanical pitch control.

guid: https://skybrary.aero/accidents-and-incidents/js41-en-route-north-west-aberdeen-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/js41-en-route-north-west-aberdeen-uk-2008 title: JS31, Fort St. John BC Canada, 2007 link: https://skybrary.aero/accidents-and-incidents/js31-fort-st-john-bc-canada-2007 description:

On 9 January 2007, a Peace Air British Aerospace Jetstream 31 on a scheduled service flight from Grand Prairie, Alberta made an instrument approach to Runway 29 at Fort St. John, British Columbia and touched down 320 feet short of the runway striking approach and runway threshold lights.

guid: https://skybrary.aero/accidents-and-incidents/js31-fort-st-john-bc-canada-2007 uri: https://skybrary.aero/accidents-and-incidents/js31-fort-st-john-bc-canada-2007 title: MD83, Are/Ostersund Sweden, 2007 link: https://skybrary.aero/accidents-and-incidents/md83-areostersund-sweden-2007 description:

On 9 September 2007, an MD83 being operated by Austrian Company MAP Jet, which was over the permitted weight for the runway and conditions, made a night take off from Are/Ostersund airport, Sweden, very near the end of the runway and collided with the approach lights for the opposite runway before climbing away.

guid: https://skybrary.aero/accidents-and-incidents/md83-areostersund-sweden-2007 uri: https://skybrary.aero/accidents-and-incidents/md83-areostersund-sweden-2007 title: SF34, Izumo Japan, 2007 link: https://skybrary.aero/accidents-and-incidents/sf34-izumo-japan-2007 description:

On 10 December, 2007 a SAAB 340B being operated by Japan Air Commuter on a scheduled passenger flight left the runway at Izumo Airport during the daylight landing roll in normal visibility and continued further while veering to the right before coming to a stop on the airport apron.

guid: https://skybrary.aero/accidents-and-incidents/sf34-izumo-japan-2007 uri: https://skybrary.aero/accidents-and-incidents/sf34-izumo-japan-2007 title: NIM, vicinity Kandahar Afghanistan, 2006 link: https://skybrary.aero/accidents-and-incidents/nim-vicinity-kandahar-afghanistan-2006 description:

On 2 September 2006, a UK Royal Air Force (RAF) Nimrod, engaged in operations over Afghanistan experienced a fuel-fed bomb bay fire shortly after completing air-to-air refuelling. The fire spread and the aircraft exploded in flight before the crew were able to land at Kandahar. The Investigation concluded that the fuel leak had been the result of a series of systemic failures to ensure continued airworthiness of the aircraft type.

guid: https://skybrary.aero/accidents-and-incidents/nim-vicinity-kandahar-afghanistan-2006 uri: https://skybrary.aero/accidents-and-incidents/nim-vicinity-kandahar-afghanistan-2006 title: SW4, vicinity Lockhart River Queensland Australia, 2005 link: https://skybrary.aero/accidents-and-incidents/sw4-vicinity-lockhart-river-queensland-australia-2005 description:

On 7 May 2005, a Fairchild Aircraft Inc. SA227-DC Metro 23 aircraft, was being operated by Transair on an IFR flight from Bamaga to Cairns, with an intermediate stop at Lockhart River, Queensland. The aircraft impacted terrain approximately 11 km north-west of the Lockhart River aerodrome and was destroyed by the impact forces and an intense, fuel-fed, post-impact fire.

guid: https://skybrary.aero/accidents-and-incidents/sw4-vicinity-lockhart-river-queensland-australia-2005 uri: https://skybrary.aero/accidents-and-incidents/sw4-vicinity-lockhart-river-queensland-australia-2005 title: B763, Frankfurt Germany, 2007 link: https://skybrary.aero/accidents-and-incidents/b763-frankfurt-germany-2007 description:

On 20 August 2007, at Frankfurt, while a Boeing 767-300 was taxiing to its parking position, thick smoke developed in the passenger cabin. All passengers and the crew were able to leave the aircraft at the gate without further incident.

guid: https://skybrary.aero/accidents-and-incidents/b763-frankfurt-germany-2007 uri: https://skybrary.aero/accidents-and-incidents/b763-frankfurt-germany-2007 title: B773, Auckland Airport New Zealand, 2007 link: https://skybrary.aero/accidents-and-incidents/b773-auckland-airport-new-zealand-2007 description:

On 22 March 2007, an Emirates Boeing 777-300ER, started its take-off on runway 05 Right at Auckland International Airport bound for Sydney. The pilots misunderstood that the runway length had been reduced during a period of runway works and started their take-off with less engine thrust and flap than were required. During the take-off they saw work vehicles in the distance on the runway and, realising something was amiss, immediately applied full engine thrust and got airborne within the available runway length and cleared the work vehicles by about 28 metres.

guid: https://skybrary.aero/accidents-and-incidents/b773-auckland-airport-new-zealand-2007 uri: https://skybrary.aero/accidents-and-incidents/b773-auckland-airport-new-zealand-2007 title: C551 / B738, Oslo Gardermoen Norway, 2006 link: https://skybrary.aero/accidents-and-incidents/c551-b738-oslo-gardermoen-norway-2006 description:

On 7 September 2006, a Cessna 551 Citation, in normal visibility conditions entered the active runway at Oslo Gardermoen Airport, Norway without a valid ATC clearance. As result of the runway incursion, the ATC instructed a Boeing 737-800 to reject its take off thereby removing the risk of collision.

guid: https://skybrary.aero/accidents-and-incidents/c551-b738-oslo-gardermoen-norway-2006 uri: https://skybrary.aero/accidents-and-incidents/c551-b738-oslo-gardermoen-norway-2006 title: D328 / SB20, London City UK, 1999 link: https://skybrary.aero/accidents-and-incidents/d328-sb20-london-city-uk-1999 description:

On 15 April 1999, a Dornier 328 crossed the holding point while a Saab 2000 was decelerating after landing on the same runway and the separation between the two aircraft was reduced to 10 meters as the landing aircraft passed. The runway incursion was subsequently attributed to distraction.

guid: https://skybrary.aero/accidents-and-incidents/d328-sb20-london-city-uk-1999 uri: https://skybrary.aero/accidents-and-incidents/d328-sb20-london-city-uk-1999 title: JS31, Skien Norway, 2001 link: https://skybrary.aero/accidents-and-incidents/js31-skien-norway-2001 description:

On 30 November 2001, a BAe Jetsream 31 operated by European Executive Express ran off the side of runway 19 on landing at Skien Airport, Geiteryggen, Norway. The runway excursion was the consequence of an unstable non-precision approach, with airframe ice accretion, and a very heavy touchdown, which caused severe aircraft damage and loss of control.

guid: https://skybrary.aero/accidents-and-incidents/js31-skien-norway-2001 uri: https://skybrary.aero/accidents-and-incidents/js31-skien-norway-2001 title: E170, Cleveland OH USA, 2007 link: https://skybrary.aero/accidents-and-incidents/e170-cleveland-oh-usa-2007 description:

On 18 February 2007, while landing at Cleveland Hopkins International Airport, USA, an Embraer ERJ170 overran the snow contaminated runway. The crew failed to execute a go-around at the minimum decision altitude (MDA) of the localizer approach when adequate visual reference was not available.

guid: https://skybrary.aero/accidents-and-incidents/e170-cleveland-oh-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/e170-cleveland-oh-usa-2007 title: EUFI / A321, en-route, near Clacton UK, 2008 link: https://skybrary.aero/accidents-and-incidents/eufi-a321-en-route-near-clacton-uk-2008 description:

On 15 October 2008, following participation in a military exercise over East Anglia (UK), a formation of 2 foreign Eurofighters entered busy controlled airspace east north east of London without clearance while in the process of trying to establish the required initial contact with military ATC, resulting in loss of prescribed separation against several civil aircraft.

guid: https://skybrary.aero/accidents-and-incidents/eufi-a321-en-route-near-clacton-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/eufi-a321-en-route-near-clacton-uk-2008 title: GLF4, Berlin Tegel Germany, 2007 link: https://skybrary.aero/accidents-and-incidents/glf4-berlin-tegel-germany-2007 description:

A Gulfstream 4 departing from Berlin at night with good surface visibility prevailing was cleared to taxi onto the parallel runway beyond the one in use for landing because both the GND and TWR controllers had incorrectly assumed the original parking position of the aircraft. Upon approaching the runway crossing, the Gulfstream 4 crew recognised a stream of approaching aircraft and held clear whilst (with difficulty) alerting the TWR controller to their implied crossing clearance. At this point the controller recognised the ATC error.

guid: https://skybrary.aero/accidents-and-incidents/glf4-berlin-tegel-germany-2007 uri: https://skybrary.aero/accidents-and-incidents/glf4-berlin-tegel-germany-2007 title: B733, vicinity Belfast Aldergrove UK, 2006 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-belfast-aldergrove-uk-2006 description:

On 18 July 2006, a Boeing 737-300 being operated by a Spanish Airline commenced a daylight non precision approach with a 12 degree offset FAT towards Belfast Aldergrove but then made an unstable descent to 200 feet agl towards an unlicensed runway at a different airport before being told by ATC radar to go around. A further also unstable approach to the correct airport/runway followed. The Investigation noted that there were multiple cues indicating that an approach to the wrong airport was being made and was not able to establish any reason why two successive unstable approaches were not discontinued

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-belfast-aldergrove-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-belfast-aldergrove-uk-2006 title: B738, London Stansted UK, 2008 link: https://skybrary.aero/accidents-and-incidents/b738-london-stansted-uk-2008 description:

On 13 November 2008, a Boeing 737-800 with an unserviceable APU was being operated by Ryanair on a passenger flight at night was in collision with a tug after a cross-bleed engine start procedure was initiated prior to the completion of a complex aircraft pushback in rain. As the power was increased on the No 1 engine in preparation for the No 2 engine start, the resulting increase in thrust was greater than the counter-force provided by the tug and the aircraft started to move forwards. The towbar attachment failed and subsequently the aircraft s No 1 engine impacted the side of the tug, prior to the aircraft brakes being applied.

guid: https://skybrary.aero/accidents-and-incidents/b738-london-stansted-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/b738-london-stansted-uk-2008 title: B738 / CRJ1, New York La Guardia USA, 2007 link: https://skybrary.aero/accidents-and-incidents/b738-crj1-new-york-la-guardia-usa-2007 description:

On 5 July 2007, in daylight and good visibility, a Comair CRJ100 on an outbound scheduled service flight was cleared by a GND Controller to taxi across active runway 22 on which a Delta AL Boeing 737-800 also operating a scheduled service flight had already been cleared to land by the (TWR) local controller. The crossing to be made did not allow the CRJ100 crew to see up the runway towards the landing threshold until they had almost completed the crossing. When they did see the by then landed B738 coming towards them, they immediately increased thrust on the single operating engine to accelerate clear.

guid: https://skybrary.aero/accidents-and-incidents/b738-crj1-new-york-la-guardia-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/b738-crj1-new-york-la-guardia-usa-2007 title: B744, Sydney Australia, 2007 link: https://skybrary.aero/accidents-and-incidents/b744-sydney-australia-2007 description:

On 15 April 2007, a Qantas Boeing 747 flew through a microburst as it began to flare for a daylight touchdown at Sydney and a hard touchdown accompanied by activation of the onboard reactive windshear warning followed. A go-around was flown to an uneventful further approach and landing. The Investigation noted the absence of an LLWAS, that the dry microburst involved would not have triggered an onboard predictive windshear alert had such a system been fitted and the failure of ATC to fully communicate relevant wind velocity information. The hard landing was judged to have been inevitable.

guid: https://skybrary.aero/accidents-and-incidents/b744-sydney-australia-2007 uri: https://skybrary.aero/accidents-and-incidents/b744-sydney-australia-2007 title: B752, vicinity London Gatwick UK, 2008 link: https://skybrary.aero/accidents-and-incidents/b752-vicinity-london-gatwick-uk-2008 description:

On 13 December 2008, a rushed daylight radar to ILS approach into London Gatwick was made by a Monarch Airlines Boeing 757-200 inbound on a short haul passenger flight. During the approach, flown by the aircraft commander, the speedbrakes had been extended prior to joining the FAT to help slow down, and both flight crew then forgot that the speed brakes were still extended and also did not realise that the commander had disconnected the Autothrottle whilst manually positioning the aircraft onto the ILS LLZ after a late selection of the LLZ mode on the FD had caused an initial fly-through. A speed loss and eventual stick shaker activation at about 1000 ft aal followed after which a go around, initially somewhat unstable until control was passed to the co pilot, was flown with the speed brakes still remaining unintentionally extended until the aircraft was approaching 3000ft aal after which the remainder of the flight was uneventful.

guid: https://skybrary.aero/accidents-and-incidents/b752-vicinity-london-gatwick-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/b752-vicinity-london-gatwick-uk-2008 title: B752, en-route, Northern Ghana, 2009 link: https://skybrary.aero/accidents-and-incidents/b752-en-route-northern-ghana-2009 description:

On 28 January 2009 the crew of a Boeing 757-200 continued takeoff from Accra Ghana despite becoming aware of an airspeed discrepancy during the take off roll. An attempt to resolve the problem failed and the consequences led to confusion as to what was happening which prompted them to declare a MAYDAY and return - successfully - to Accra. The left hand pitot probe was found to be blocked by an insect. The Investigation concluded that a low speed rejected takeoff would have been more appropriate than the continued take off in the circumstances which had prevailed.

guid: https://skybrary.aero/accidents-and-incidents/b752-en-route-northern-ghana-2009 uri: https://skybrary.aero/accidents-and-incidents/b752-en-route-northern-ghana-2009 title: B763, Manchester UK, 2008 link: https://skybrary.aero/accidents-and-incidents/b763-manchester-uk-2008 description:

On 13 December 2008, a Thomsonfly Boeing 767-300 departing from Manchester for Montego Bay Jamaica was considered to be accelerating at an abnormally slow rate during the take off roll on Runway 23L. The aircraft commander, who was the pilot not flying, consequently delayed the V1 call by about 10 - 15 because he thought the aircraft might be heavier than had been calculated. During the rotation the TAILSKID message illuminated momentarily, indicating that the aircraft had suffered a tail strike during the takeoff. The commander applied full power and shortly afterwards the stick shaker activated briefly. The aircraft continued to climb away and accelerate before the flaps were retracted and the after-takeoff check list completed. The appropriate drills in the Quick Reference Handbook (QRH) were subsequently actioned, fuel was dumped and the aircraft returned to Manchester for an overweight landing without further incident.

guid: https://skybrary.aero/accidents-and-incidents/b763-manchester-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/b763-manchester-uk-2008 title: C185, Wellington New Zealand, 1997 link: https://skybrary.aero/accidents-and-incidents/c185-wellington-new-zealand-1997 description:

On Monday 3 March 1997 at 1014 hours, privately owned and operated Cessna 185 encountered wake turbulence from previous departing aircraft, the pilot lost control of the aircraft at a height from which recovery was not possible and the aircraft descended to the ground.

guid: https://skybrary.aero/accidents-and-incidents/c185-wellington-new-zealand-1997 uri: https://skybrary.aero/accidents-and-incidents/c185-wellington-new-zealand-1997 title: DH8C / GALX, Valencia Spain, 2008 link: https://skybrary.aero/accidents-and-incidents/dh8c-galx-valencia-spain-2008 description:

On 11 February 2008, the crew of a DHC8-300 misjudged the sufficient clearance during taxi and collided with a Gulfstream G200 at a taxiway intersection.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-galx-valencia-spain-2008 uri: https://skybrary.aero/accidents-and-incidents/dh8c-galx-valencia-spain-2008 title: F50 / T6, vicinity Maastricht Netherlands, 2007 link: https://skybrary.aero/accidents-and-incidents/f50-t6-vicinity-maastricht-netherlands-2007 description:

On 2 August 2007, a Fokker F50 on an ILS approach to Maastricht in IMC came into close proximity inside the CTZ with an unseen light aircraft which had failed to comply with its Special VFR transit clearance. The Investigation found that the transiting aircraft had come within 0.14nm / 260 metres of the opposite direction F50 at a similar altitude without either aircraft having sight of the other, and that the Harvard had been wrongly assumed by ATC to be a helicopter after an initial lack of call sign prefix clarity on first contact had not been positively resolved.

guid: https://skybrary.aero/accidents-and-incidents/f50-t6-vicinity-maastricht-netherlands-2007 uri: https://skybrary.aero/accidents-and-incidents/f50-t6-vicinity-maastricht-netherlands-2007 title: SF34, vicinity Sydney Australia, 2008 link: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-sydney-australia-2008 description:

On 3 November 2008, a Saab 340B being operated on a domestic passenger flight by Regional Express AL was tracking in daylight to join a 7nm final for Runway 34R at destination Sydney, when a passenger sustained minor injuries as the result of a transient encounter with turbulence that had led to a momentary loss of control of the aircraft and which was suspected as being of wake vortex origin.

guid: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-sydney-australia-2008 uri: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-sydney-australia-2008 title: A306, Paris CDG France, 1997 link: https://skybrary.aero/accidents-and-incidents/a306-paris-cdg-france-1997 description:

On 30 July 1997, an Airbus A300-600 being operated by Emirates Airline was departing on a scheduled passenger flight from Paris Charles de Gaulle in daylight when, as the aircraft was accelerating at 40 kts during the take off roll, it pitched up and its tail touched the ground violently. The crew abandoned the takeoff and returned to the parking area. The tail of the aircraft was damaged due to the impact with the runway when the plane pitched up.

guid: https://skybrary.aero/accidents-and-incidents/a306-paris-cdg-france-1997 uri: https://skybrary.aero/accidents-and-incidents/a306-paris-cdg-france-1997 title: A320, Ballykelly Northern Ireland UK, 2006 link: https://skybrary.aero/accidents-and-incidents/a320-ballykelly-northern-ireland-uk-2006 description:

On 29 March 2006, an Eirjet Airbus 320 was operating a scheduled passenger flight from Liverpool to Londonderry Airport in Northern Ireland for Ryanair in daylight. At 8nm from LDY, the operating crew reported that they were having problems with the ILS glideslope on approach to Runway 26. They judged that they were too high to carry out a safe landing from the ILS approach and requested permission from ATC to carry out a visual approach. The aircraft, with the commander as PF, then flew a right hand descending orbit followed by a visual circuit from which it landed. Upon landing, the crew were advised by Londonderry ATC, who had had the aircraft in sight when it called Finals and had then cleared it to land that they had, in fact, landed at Ballykelly airfield, a military helicopter base 5nm to the east-north-east of Londonderry.

guid: https://skybrary.aero/accidents-and-incidents/a320-ballykelly-northern-ireland-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/a320-ballykelly-northern-ireland-uk-2006 title: LJ24, vicinity Belleville Illinois USA, 2003 link: https://skybrary.aero/accidents-and-incidents/lj24-vicinity-belleville-illinois-usa-2003 description:

On November 12, 2003, a Bombardier Learjet 24D being operated on a non scheduled flight by Multi-Aero Inc. was destroyed during a forced landing and post crash fire following a loss of power in both engines after an encounter with a flock of birds just after take off from St. Louis Downtown Airport.

guid: https://skybrary.aero/accidents-and-incidents/lj24-vicinity-belleville-illinois-usa-2003 uri: https://skybrary.aero/accidents-and-incidents/lj24-vicinity-belleville-illinois-usa-2003 title: MD81, vicinity Chicago Midway, IL USA, 2008 link: https://skybrary.aero/accidents-and-incidents/md81-vicinity-chicago-midway-il-usa-2008 description:

On 7 July 2008, a Mc Donnell Douglas MD81 being operated by Midwest Airlines, Inc. had just taken off in day visual flight conditions when increasing pitch could initially not be controlled. Later, control was regained but with “higher than normal” pitch control pressure required to control the aircraft - after en-route diversion the aircraft landed uneventfully.

guid: https://skybrary.aero/accidents-and-incidents/md81-vicinity-chicago-midway-il-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/md81-vicinity-chicago-midway-il-usa-2008 title: B733 / B744, Chicago IL USA, 2006 link: https://skybrary.aero/accidents-and-incidents/b733-b744-chicago-il-usa-2006 description:

On 23 July 2006, a Boeing B737-300 operated by United Airlines executed an early rotation during a night take off when a Boeing 747 operated by Atlas Air was observed on a landing roll on an intersecting runway at Chicago O Hare Airport. The occurrence is attributed to ATC error.

guid: https://skybrary.aero/accidents-and-incidents/b733-b744-chicago-il-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/b733-b744-chicago-il-usa-2006 title: B737 / A332, Seatle-Tacoma WA USA, 2008 link: https://skybrary.aero/accidents-and-incidents/b737-a332-seatle-tacoma-wa-usa-2008 description:

On 2 July 2008, an Air Tran Airways B737-700 which had just landed at night on runway 34C at Sea-Tac failed to hold clear of runway 34R during taxi as instructed and passed almost directly underneath a North West Airlines A330-200 which had just become airborne from Runway 32R. The Investigation found that the 737 crew had been unaware of their incursion and that the alert provided by ASDE-X had not provided an opportunity for ATC to usefully intervene to stop prevent the potential conflict

guid: https://skybrary.aero/accidents-and-incidents/b737-a332-seatle-tacoma-wa-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/b737-a332-seatle-tacoma-wa-usa-2008 title: B738 / B744, Los Angeles USA, 2004 link: https://skybrary.aero/accidents-and-incidents/b738-b744-los-angeles-usa-2004 description:

On 19 August 2004, a Boeing 747-400 operated by Asiana Airlines, was given a landing clearance for runway 24L at Los Angeles (LAX). At the same time, a Boeing 737-800 operated by Southwest Airlines was given line up and wait instruction for the same runway. The B744 initiated a go-around as the crew spotted the B738 on the runway.

guid: https://skybrary.aero/accidents-and-incidents/b738-b744-los-angeles-usa-2004 uri: https://skybrary.aero/accidents-and-incidents/b738-b744-los-angeles-usa-2004 title: CRJ1 / A320, Baltimore MD USA, 2007 link: https://skybrary.aero/accidents-and-incidents/crj1-a320-baltimore-md-usa-2007 description:

On 2 December 2007, at Baltimore/Washington International Thurgood Marshall Airport, after controller error, a CRJ-100 operated by Comair with a valid take-off clearance missed by 400 ft vertically and 400 ft horizontally an Airbus A320, which just landed with also valid clearance on an intersecting runway.

guid: https://skybrary.aero/accidents-and-incidents/crj1-a320-baltimore-md-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/crj1-a320-baltimore-md-usa-2007 title: CRJ2, en-route, Jefferson City USA, 2004 link: https://skybrary.aero/accidents-and-incidents/crj2-en-route-jefferson-city-usa-2004 description:

On October 14, 2004, a Bombardier CRJ-200 being operated by Pinnacle Airlines on a non revenue positioning flight crashed into a residential area in the vicinity of Jefferson City Memorial Airport, Missouri after the flight crew attempted to fly the aircraft beyond its performance limits and a high altitude stall, to which their response was inappropriate, then followed.

guid: https://skybrary.aero/accidents-and-incidents/crj2-en-route-jefferson-city-usa-2004 uri: https://skybrary.aero/accidents-and-incidents/crj2-en-route-jefferson-city-usa-2004 title: CRJ7 / C172, Allentown PA USA, 2008 link: https://skybrary.aero/accidents-and-incidents/crj7-c172-allentown-pa-usa-2008 description:

On 19 September 2008, A Mesa Airlines CRJ-700 making a night take off from Allentown in accordance with its clearance saw an aircraft ahead on the runway whilst accelerating at in excess of 100 knots and responded with a high speed rejected take off, clearing the other aircraft by an estimated 3 metres at approximately 40 knots. It was found that the TWR controller failed to ensure that the just-landed light aircraft had vacated the runway before issuing the take off clearance. This controller was newly recruited and recently certified in-position after supervised experience gained almost exclusively during daylight hours.

guid: https://skybrary.aero/accidents-and-incidents/crj7-c172-allentown-pa-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/crj7-c172-allentown-pa-usa-2008 title: B742 / B744, Chicago O'Hare IL USA, 1999 link: https://skybrary.aero/accidents-and-incidents/b742-b744-chicago-ohare-il-usa-1999 description:

On 1 April 1999, an Air China Boeing 747-200F which had just landed on and cleared runway 14R at Chicago O Hare failed to follow its correctly read back taxi-in clearance and crossed the landing runway at night ahead of a Boeing 747 taking off. The latter rotated abruptly and banked away from the taxiing 747, missing it by an estimated 75 feet. It was found that the Air China aircraft had realised it was going the wrong way but had slowed rather than stopped taxiing with the nose of the aircraft past the runway centreline as it was overflown.

guid: https://skybrary.aero/accidents-and-incidents/b742-b744-chicago-ohare-il-usa-1999 uri: https://skybrary.aero/accidents-and-incidents/b742-b744-chicago-ohare-il-usa-1999 title: B738 / E135, en-route, Mato Grosso Brazil, 2006 link: https://skybrary.aero/accidents-and-incidents/b738-e135-en-route-mato-grosso-brazil-2006 description:

On 29 September 2006, a Boeing 737-800 level at FL370 collided with an opposite direction Embraer Legacy at the same level. Control of the 737 was lost and it crashed, killing all 154 occupants. The Legacy's crew kept control and successfully diverted to the nearest suitable airport. The Investigation found that ATC had not instructed the Legacy to descend to FL360 when the flight plan indicated this and soon afterwards, its crew had inadvertently switched off their transponder. After the consequent disappearance of altitude from all radar displays, ATC assumed but did not confirm the aircraft had descended.

guid: https://skybrary.aero/accidents-and-incidents/b738-e135-en-route-mato-grosso-brazil-2006 uri: https://skybrary.aero/accidents-and-incidents/b738-e135-en-route-mato-grosso-brazil-2006 title: SH36 / SH36, manoeuvring, Watertown WI USA, 2006 link: https://skybrary.aero/accidents-and-incidents/sh36-sh36-manoeuvring-watertown-wi-usa-2006 description:

On 5 February 2006, two Shorts SD-360-300 aircraft collided in mid air while in formation near Watertown, WI, USA; both aircraft suffered damage. One aircraft experienced loss of control and impacted terrain while the other made an emergency landing, overunning the runway, at a nearby airport.

guid: https://skybrary.aero/accidents-and-incidents/sh36-sh36-manoeuvring-watertown-wi-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/sh36-sh36-manoeuvring-watertown-wi-usa-2006 title: A306, vicinity Nagoya Japan, 1994 link: https://skybrary.aero/accidents-and-incidents/a306-vicinity-nagoya-japan-1994 description:

On 26 April 1994, the crew of an Airbus A300-600 lost control of their aircraft on final approach to Nagoya and the aircraft crashed within the airport perimeter. The Investigation found that an inadvertent mode selection error had triggered control difficulties which had been ultimately founded on an apparent lack understanding by both pilots of the full nature of the interaction between the systems controlling thrust and pitch on the aircraft type which were not typical of most other contemporary types. It was also concluded that the Captain's delay in taking control from the First Officer had exacerbated the situation.

guid: https://skybrary.aero/accidents-and-incidents/a306-vicinity-nagoya-japan-1994 uri: https://skybrary.aero/accidents-and-incidents/a306-vicinity-nagoya-japan-1994 title: A310 / B736, en-route, Southern Norway, 2001 link: https://skybrary.aero/accidents-and-incidents/a310-b736-en-route-southern-norway-2001 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a310-b736-en-route-southern-norway-2001 uri: https://skybrary.aero/accidents-and-incidents/a310-b736-en-route-southern-norway-2001 title: A310, vicinity Paris Orly France, 1994 link: https://skybrary.aero/accidents-and-incidents/a310-vicinity-paris-orly-france-1994 description:

On 24 September 1994, lack of understanding of automatic flight control modes, by the crew of an Airbus A-310, led to a full stall. The aircraft was recovered and subsequently landed without further event at Paris Orly.

guid: https://skybrary.aero/accidents-and-incidents/a310-vicinity-paris-orly-france-1994 uri: https://skybrary.aero/accidents-and-incidents/a310-vicinity-paris-orly-france-1994 title: GLF5 / A319, south-eastern France, 2004 link: https://skybrary.aero/accidents-and-incidents/glf5-a319-south-eastern-france-2004 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/glf5-a319-south-eastern-france-2004 uri: https://skybrary.aero/accidents-and-incidents/glf5-a319-south-eastern-france-2004 title: A319, Las Vegas NV USA, 2006 link: https://skybrary.aero/accidents-and-incidents/a319-las-vegas-nv-usa-2006 description:

On 30 January 2006 the Captain of an Airbus A319 inadvertently lined up and commenced a night rolling take off from Las Vegas on the runway shoulder instead of the runway centreline despite the existence of an illuminated lead on line to the centre of the runway from the taxiway access used. The aircraft was realigned at speed and the take off was completed. ATC were not advised and broken edge light debris presented a potential hazard to other aircraft until eventually found. The Investigation found that other similar events on the same runway had not been reported at all.

guid: https://skybrary.aero/accidents-and-incidents/a319-las-vegas-nv-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/a319-las-vegas-nv-usa-2006 title: A319, south of London UK, 2005 link: https://skybrary.aero/accidents-and-incidents/a319-south-london-uk-2005 description:

On 22 October 2005, a British Airways Airbus A319 climbing en route to destination over south east England at night in VMC experienced a major but temporary electrical failure. Most services were re-instated within a short time and the flight was continued. However, during the subsequent Investigation, which took over two years, a series of significant deficiencies were identified in the design of the A320 series electrical system and the manufacturer-recommended responses to failures in it and in response, Airbus developed solutions to most of them.

guid: https://skybrary.aero/accidents-and-incidents/a319-south-london-uk-2005 uri: https://skybrary.aero/accidents-and-incidents/a319-south-london-uk-2005 title: A319 / B737, Zurich Switzerland, 2002 link: https://skybrary.aero/accidents-and-incidents/a319-b737-zurich-switzerland-2002 description:

On 23 November 2002, an A319, landing on Rwy16 at Zurich Switzerland, narrowly missed collision with a B737-600 cleared for take off on an intersecting runway.

guid: https://skybrary.aero/accidents-and-incidents/a319-b737-zurich-switzerland-2002 uri: https://skybrary.aero/accidents-and-incidents/a319-b737-zurich-switzerland-2002 title: A319, en-route, Nantes France, 2006 link: https://skybrary.aero/accidents-and-incidents/a319-en-route-nantes-france-2006 description:

On 15 September 2006, an Easyjet Airbus A319, despatched under MEL provision with one engine generator inoperative and the corresponding electrical power supplied by the Auxiliary Power Unit generator, suffered a further en route electrical failure which included power loss to all COM radio equipment which could not then be re-instated. The flight was completed as flight planned using the remaining flight instruments with the one remaining transponder selected to the standard emergency code. The incident began near Nantes, France.

guid: https://skybrary.aero/accidents-and-incidents/a319-en-route-nantes-france-2006 uri: https://skybrary.aero/accidents-and-incidents/a319-en-route-nantes-france-2006 title: A320, Phoenix AZ USA, 2002 link: https://skybrary.aero/accidents-and-incidents/a320-phoenix-az-usa-2002 description:

On 28 August 2002, an America West Airbus A320 operating under an ADD for an inoperative left engine thrust reverser veered off the side of the runway during the landing roll at Phoenix AZ after the Captain mismanaged the thrust levers and lost directional control as a consequence of applying asymmetric thrust. Substantial damage occurred to the aircraft but most occupants were uninjured.

guid: https://skybrary.aero/accidents-and-incidents/a320-phoenix-az-usa-2002 uri: https://skybrary.aero/accidents-and-incidents/a320-phoenix-az-usa-2002 title: A320, London Heathrow UK, 2006 link: https://skybrary.aero/accidents-and-incidents/a320-london-heathrow-uk-2006 description:

On 26 June 2006, after an uneventful pre-flight pushback of a British Airways Airbus A320-200 at London Heathrow Airport, the aircraft started moving under its own power and, shortly afterwards, collided with the tractor that had just performed the pushback, damaging both the right engine and the tractor.

guid: https://skybrary.aero/accidents-and-incidents/a320-london-heathrow-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/a320-london-heathrow-uk-2006 title: A320, Khartoum Sudan, 2005 link: https://skybrary.aero/accidents-and-incidents/a320-khartoum-sudan-2005 description:

On 11 March 2005, an Airbus A321-200 operated by British Mediterranean Airways, executed two unstable approaches below applicable minima in a dust storm to land in Khartoum Airport, Sudan. The crew were attempting a third approach when they received information from ATC that visibility was below the minimum required for the approach and they decided to divert to Port Sudan where the A320 landed without further incident.

guid: https://skybrary.aero/accidents-and-incidents/a320-khartoum-sudan-2005 uri: https://skybrary.aero/accidents-and-incidents/a320-khartoum-sudan-2005 title: A320, vicinity Bahrain Airport, Kingdom of Bahrain, 2000 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-bahrain-airport-kingdom-bahrain-2000 description:

On 23 August 2000, a Gulf Air Airbus A320 flew at speed into the sea during an intended dark night go around at Bahrain and all 143 occupants were killed. It was subsequently concluded that, although a number of factors created the scenario in which the accident could occur, the most plausible explanation for both the descent and the failure to recover from it was the focus on the airspeed indication at the expense of the ADI and the effect of somatogravic illusion on the recently promoted Captain which went unchallenged by his low-experience First Officer.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-bahrain-airport-kingdom-bahrain-2000 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-bahrain-airport-kingdom-bahrain-2000 title: A320, en-route, Sydney Australia, 2007 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-sydney-australia-2007 description:

On 11 January 2007, an Air New Zealand Airbus A320 which had just departed Sydney Australia for Auckland, New Zealand was observed to have turned onto a heading contrary to the ATC-issued radar heading. When so advised by ATC, the crew checked the aircraft compasses and found that they were reading approximately 40 degrees off the correct heading.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-sydney-australia-2007 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-sydney-australia-2007 title: A320, Los Angeles USA, 2005 link: https://skybrary.aero/accidents-and-incidents/a320-los-angeles-usa-2005 description:

On 21 September 2005, an Airbus A320 operated by Jet Blue Airways made a successful emergency landing at Los Angeles Airport, California, with the nose wheels cocked 90 degrees to the fore-aft position after an earlier fault on gear retraction.

guid: https://skybrary.aero/accidents-and-incidents/a320-los-angeles-usa-2005 uri: https://skybrary.aero/accidents-and-incidents/a320-los-angeles-usa-2005 title: A320, vicinity Frankfurt Germany, 2001 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-frankfurt-germany-2001 description:

On 21 March 2001 an Airbus A320-200, operated by Lufthansa, experienced a flight controls malfunctions shortly after take-off which resulted in loss of control and subsequent near terrain impact. The uncontrolled roll, due to the malfunction of the pilot flying's sidestick, was recovered by the other pilot and the aircraft safely returned to land in Frankfurt without further incident.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-frankfurt-germany-2001 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-frankfurt-germany-2001 title: A320, Bilbao Spain, 2001 link: https://skybrary.aero/accidents-and-incidents/a320-bilbao-spain-2001 description:

On 7th February 2001, an Iberia A320 was about to make a night touch down at Bilbao in light winds when it experienced unexpected windshear. The attempt to counter the effect of this by initiation of a go around failed because the automatic activation of AOA protection in accordance with design criteria which opposed the crew pitch input. The aircraft then hit the runway so hard that a go around was no longer possible. Severe airframe structural damage and evacuation injuries to some of the occupants followed. A mandatory modification to the software involved was subsequently introduced.

guid: https://skybrary.aero/accidents-and-incidents/a320-bilbao-spain-2001 uri: https://skybrary.aero/accidents-and-incidents/a320-bilbao-spain-2001 title: A320 / CRJ2, Sofia Bulgaria, 2007 link: https://skybrary.aero/accidents-and-incidents/a320-crj2-sofia-bulgaria-2007 description:

On 13 April 2007 in day VMC, an Air France A320 departing Sofia lined up contrary to an ATC Instruction to remain at the holding point and be ready immediate. The controller did not immediately notice and after subsequently giving a landing clearance for the same runway, was obliged to cancel it send the approaching aircraft around. An Investigation attributed the incursion to both the incorrect terminology used by TWR and the failure to challenge the incomplete clearance read back by the A320 crew.

guid: https://skybrary.aero/accidents-and-incidents/a320-crj2-sofia-bulgaria-2007 uri: https://skybrary.aero/accidents-and-incidents/a320-crj2-sofia-bulgaria-2007 title: A320, Harstad/Narvik Norway 2004 link: https://skybrary.aero/accidents-and-incidents/a320-harstadnarvik-norway-2004 description:

On 25 November 2004, a MyTravel Airways Airbus A320 departed the side of the runway at Harstad, Norway at a low speed after loss of directional control when thrust was applied for a night take off on a runway with below normal surface friction characteristics. It was found that the crew had failed to follow an SOP designed to ensure that any accumulated fan ice was shed prior to take off and also failed to apply take off thrust as prescribed, thus delaying their appreciation of the uneven thrust produced.

guid: https://skybrary.aero/accidents-and-incidents/a320-harstadnarvik-norway-2004 uri: https://skybrary.aero/accidents-and-incidents/a320-harstadnarvik-norway-2004 title: A320, vicinity LaGuardia New York USA, 2009 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-laguardia-new-york-usa-2009 description:

On 15 January 2009, a United Airlines Airbus A320-200 approaching 3000 feet agl in day VMC following take-off from New York La Guardia experienced an almost complete loss of thrust in both engines after encountering a flock of Canada Geese . In the absence of viable alternatives, the aircraft was successfully ditched in the Hudson River about. Of the 150 occupants, one flight attendant and four passengers were seriously injured and the aircraft was substantially damaged. The subsequent investigation led to the issue of 35 Safety Recommendations mainly relating to ditching, bird strike and low level dual engine failure.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-laguardia-new-york-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-laguardia-new-york-usa-2009 title: A321, en-route, Gimpo South Korea, 2006 link: https://skybrary.aero/accidents-and-incidents/a321-en-route-gimpo-south-korea-2006 description:

On 9 June 2006, an Airbus 321-100, operated by Asiana Airlines, encountered a thunderstorm accompanied by Hail around 20 miles southeast of Anyang VOR at an altitude of 11,500 ft, while descending for an approach to Gimpo Airport. The radome was detached and the cockpit windshield was cracked due to impact with Hail.

guid: https://skybrary.aero/accidents-and-incidents/a321-en-route-gimpo-south-korea-2006 uri: https://skybrary.aero/accidents-and-incidents/a321-en-route-gimpo-south-korea-2006 title: A321, Manchester UK, 2008 (2) link: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2008-2 description:

On 28 July 2008, the crew flying an Airbus A321-200 departing Manchester UK were unable to raise the landing gear. The fault was caused by damage to the Nose Landing Gear sustained on the previous flight which experienced a heavy landing.

guid: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2008-2 uri: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2008-2 title: A321, Manchester UK, 2008 (1) link: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2008-1 description:

On 18 July 2008, an Airbus A321-200 operated by Thomas Cook Airlines experienced hard landing during night line training with significant aircraft damage not found until several days later. The hard landing was subsequently partially attributed to the inability to directly observe the trainee pitch control inputs on side stick of the A321.

guid: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2008-1 uri: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2008-1 title: A321, en-route, Vienna Austria, 2003 link: https://skybrary.aero/accidents-and-incidents/a321-en-route-vienna-austria-2003 description:

On 26th May 2003, a British Midland A321 suffered severe damage from hail en route near Vienna.

guid: https://skybrary.aero/accidents-and-incidents/a321-en-route-vienna-austria-2003 uri: https://skybrary.aero/accidents-and-incidents/a321-en-route-vienna-austria-2003 title: A332, en-route, North Atlantic Ocean, 2001 link: https://skybrary.aero/accidents-and-incidents/a332-en-route-north-atlantic-ocean-2001 description:

On 24 August 2001, an Air Transat Airbus A330-200 eastbound across the North Atlantic at night experienced a double-engine flameout after which Lajes on Terceira Island in the Azores was identified as the best diversion and a successful glide approach and landing there was subsequently achieved. The Investigation found that the flameouts had been the result of fuel exhaustion after a fuel leak from the right engine caused by a pre flight maintenance error. Fuel exhaustion was found to have occurred because the flight crew did not perform the QRH procedure applicable to an in-flight fuel leak.

guid: https://skybrary.aero/accidents-and-incidents/a332-en-route-north-atlantic-ocean-2001 uri: https://skybrary.aero/accidents-and-incidents/a332-en-route-north-atlantic-ocean-2001 title: A343 / B744, en-route, south of Newfoundland Canada, 1998 link: https://skybrary.aero/accidents-and-incidents/a343-b744-en-route-south-newfoundland-canada-1998 description:

On 20 July 1998, after an ATC error south of Newfoundland, an Air France A340 and an Air Canada 747-400 were on directly converging tracks and at the same level. Collision was avoided by the correct actioning of coordinated TCAS RAs by both aircraft.

guid: https://skybrary.aero/accidents-and-incidents/a343-b744-en-route-south-newfoundland-canada-1998 uri: https://skybrary.aero/accidents-and-incidents/a343-b744-en-route-south-newfoundland-canada-1998 title: A320, en-route, Denver CO USA, 2009 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-denver-co-usa-2009 description:

On 21 October 2009, an Airbus 320-200 being operated by Northwest Airlines on a scheduled passenger flight from San Diego to Minneapolis-St Paul, with the Captain as PF, overflew its destination at cruise level in VMC at night by more than 100 nm, after the two pilots had become distracted in conversation and lost situational awareness. They failed to maintain radio communications with a series of successive ATC units for well over an hour. After a routine inquiry from the cabin crew as to the expected arrival time, the flight crew realised what had happened and re-established ATC contact after which the flight was completed without further incident.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-denver-co-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-denver-co-usa-2009 title: A343, Toronto Canada, 2005 link: https://skybrary.aero/accidents-and-incidents/a343-toronto-canada-2005 description:

On 2 August 2005, an Airbus A340-300 attempted a daylight landing at Toronto on a rain-soaked runway during an active thunderstorm and overran for 300 metres ending up in a ravine from where, despite its destruction by an intense post crash fire, all 309 occupants escaped. The Investigation recommendations focused mainly on improving crew decision making in adverse weather conditions and issues related to the consequences of such an overrun on survivability, the latter including one for a 300 metre RESA requirement to be implemented.

guid: https://skybrary.aero/accidents-and-incidents/a343-toronto-canada-2005 uri: https://skybrary.aero/accidents-and-incidents/a343-toronto-canada-2005 title: A310, vicinity Abidjan Ivory Coast, 2000 link: https://skybrary.aero/accidents-and-incidents/a310-vicinity-abidjan-ivory-coast-2000 description:

On 30 January 2000, an Airbus 310 took off from Abidjan (Ivory Coast) at night bound for Lagos, Nigeria then Nairobi, Kenya. Thirty-three seconds after take-off, the airplane crashed into the Atlantic Ocean, 1.5 nautical miles south of the runway at Abidjan Airport. 169 persons died and 10 were injured in the accident.

guid: https://skybrary.aero/accidents-and-incidents/a310-vicinity-abidjan-ivory-coast-2000 uri: https://skybrary.aero/accidents-and-incidents/a310-vicinity-abidjan-ivory-coast-2000 title: A333, vicinity Wom Guam Airport, Guam, 2002 link: https://skybrary.aero/accidents-and-incidents/a333-vicinity-wom-guam-airport-guam-2002 description:

On 16 December 2002, approximately 1735 UTC, an Airbus A330-330, operating as Philippine Airlines flight 110, struck power lines while executing a localizer-only Instrument Landing System (ILS) approach to runway 6L at A.B. Pat Won Guam International Airport, Agana, Guam. Instrument meteorological conditions prevailed during the approach. Following a ground proximity warning system (GPWS) alert, the crew executed a missed approach and landed successfully after a second approach to the airport.

guid: https://skybrary.aero/accidents-and-incidents/a333-vicinity-wom-guam-airport-guam-2002 uri: https://skybrary.aero/accidents-and-incidents/a333-vicinity-wom-guam-airport-guam-2002 title: A388, Changi Singapore, 2008 link: https://skybrary.aero/accidents-and-incidents/a388-changi-singapore-2008 description:

On 10 January 2008, an Airbus A380 was damaged during push back at Singapore Changi International airport when the aircraft right wing undercarriage became stuck in soft ground adjacent to the taxiway.

guid: https://skybrary.aero/accidents-and-incidents/a388-changi-singapore-2008 uri: https://skybrary.aero/accidents-and-incidents/a388-changi-singapore-2008 title: B190, vicinity Lihue Hawaii, 2008 link: https://skybrary.aero/accidents-and-incidents/b190-vicinity-lihue-hawaii-2008 description:

On 14 January 2008, a single pilot Beech 1900C on a non scheduled mail flight which had departed from Honolulu disappeared during a visual dark night approach at its destination. The Investigation concluded that the pilot had become spatially disoriented and lost control of the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/b190-vicinity-lihue-hawaii-2008 uri: https://skybrary.aero/accidents-and-incidents/b190-vicinity-lihue-hawaii-2008 title: B463, en-route, South of Frankfurt Germany, 2005 link: https://skybrary.aero/accidents-and-incidents/b463-en-route-south-frankfurt-germany-2005 description:

On 12 March 2005, the crew of a BAe 146-300 climbing out of Frankfurt lost elevator control authority and an un-commanded descent at up to 4500 fpm in a nose high pitch attitude occurred before descent was arrested and control regained. After landing using elevator trim to control pitch, significant amounts of de/anti-icing fluid residues were found frozen in the elevator/stabilizer and aileron/rudder gaps. The Investigation confirmed that an accumulation of hygroscopic polymer residues from successive applications of thickened de/anti ice fluid had expanded by re-hydration and then expanded further by freezing thus obstructing the flight controls.

guid: https://skybrary.aero/accidents-and-incidents/b463-en-route-south-frankfurt-germany-2005 uri: https://skybrary.aero/accidents-and-incidents/b463-en-route-south-frankfurt-germany-2005 title: B735, en-route, SE of Kushimoto Wakayama Japan, 2006 link: https://skybrary.aero/accidents-and-incidents/b735-en-route-se-kushimoto-wakayama-japan-2006 description:

On 5 July 2006, during daytime, a Boeing 737-500, operated by Air Nippon Co., Ltd. took off from Fukuoka Airport as All Nippon Airways scheduled flight 2142. At about 08:10, while flying at 37,000 ft approximately 60 nm southeast of Kushimoto VORTAC, a cabin depressurization warning was displayed and the oxygen masks in the cabin were automatically deployed. The aircraft made an emergency descent and, at 09:09, landed on Chubu International Airport.

guid: https://skybrary.aero/accidents-and-incidents/b735-en-route-se-kushimoto-wakayama-japan-2006 uri: https://skybrary.aero/accidents-and-incidents/b735-en-route-se-kushimoto-wakayama-japan-2006 title: B743, vicinity Won Guam Airport, Guam, 1997 link: https://skybrary.aero/accidents-and-incidents/b743-vicinity-won-guam-airport-guam-1997 description:

On 6 August 1997, Korean Air flight 801, a Boeing 747-300, crashed at night at Nimitz Hill, 3 miles southwest of Won Guam International Airport, Agana, Guam while on final approach for runway 6 Left. Of the 254 persons on board, 228 were killed, and 23 passengers and 3 flight attendants survived the accident with serious injuries.

guid: https://skybrary.aero/accidents-and-incidents/b743-vicinity-won-guam-airport-guam-1997 uri: https://skybrary.aero/accidents-and-incidents/b743-vicinity-won-guam-airport-guam-1997 title: B74S, en-route, Anchorage AK USA, 2004 link: https://skybrary.aero/accidents-and-incidents/b74s-en-route-anchorage-ak-usa-2004 description:

On 5 December 2004 a Boeing 747-100SP experienced a rapid depressurisation and subsequent minor damage after reaching cruise level near Anchorage, Alaska. The crew elected to return to Ted Stevens International Airport, Anchorage where the aircraft landed without further incident.

guid: https://skybrary.aero/accidents-and-incidents/b74s-en-route-anchorage-ak-usa-2004 uri: https://skybrary.aero/accidents-and-incidents/b74s-en-route-anchorage-ak-usa-2004 title: B752, en-route, North Sea, 2006 link: https://skybrary.aero/accidents-and-incidents/b752-en-route-north-sea-2006 description:

On 22 October 2006 a blue haze was observed in the passenger cabin of a Boeing 757-200, operated by Thomsonfly, shortly after reaching cruise altitude on a scheduled passenger flight from Newcastle to Larnaca. A precautionary diversion was made to London Stansted, where an emergency evacuation was carried out successfully.

guid: https://skybrary.aero/accidents-and-incidents/b752-en-route-north-sea-2006 uri: https://skybrary.aero/accidents-and-incidents/b752-en-route-north-sea-2006 title: B752 / CRJ7, San Francisco CA USA, 2008 link: https://skybrary.aero/accidents-and-incidents/b752-crj7-san-francisco-ca-usa-2008 description:

On 13 January 2008, a Boeing 757-200 and a Bombardier CL-600 received pushback clearance from two adjacent terminal gates within 41 seconds. The ground controller believed there was room for both aircraft to pushback. During the procedure both aircraft were damaged as their tails collided. The pushback procedure of the Boeing was performed without wing-walkers or tail-walkers.

guid: https://skybrary.aero/accidents-and-incidents/b752-crj7-san-francisco-ca-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/b752-crj7-san-francisco-ca-usa-2008 title: B752/B722, Providence RI USA, 1999 link: https://skybrary.aero/accidents-and-incidents/b752b722-providence-ri-usa-1999 description:

On December 6, 1999, United Airlines Boeing 757 failed to follow its taxi-in clearance after landing at night in thick fog at Providence RI and ended up at the edge of the runway it had just the landed on as a departing FedEx Boeing 727 passed very close by. The TWR controller, without surface radar available, then made unjustified presumptions about the 757s position and twice cleared a 737 to take off whilst the runway was still obstructed. Fortunately, the crew of that aircraft declined until safety was positively assured by the eventual arrival of the 757 at the terminal.

guid: https://skybrary.aero/accidents-and-incidents/b752b722-providence-ri-usa-1999 uri: https://skybrary.aero/accidents-and-incidents/b752b722-providence-ri-usa-1999 title: B763, Luton UK, 2005 link: https://skybrary.aero/accidents-and-incidents/b763-luton-uk-2005 description:

On 16 February 2005, at Luton Airport, a Boeing B767-300 collided with the tug pulling it forward when the shear pin of the unserviceable tow bar being used to pull the aircraft broke. The aircraft ran onto the tug when the ground crew stopped the tug suddenly. As result of the collision with the tug the aircraft fuselage and landing gear was damaged.

guid: https://skybrary.aero/accidents-and-incidents/b763-luton-uk-2005 uri: https://skybrary.aero/accidents-and-incidents/b763-luton-uk-2005 title: B763, en-route, Northern France, 1998 link: https://skybrary.aero/accidents-and-incidents/b763-en-route-northern-france-1998 description:

On 9 January 1998, a Boeing 767-300 operated by United Airlines experienced an electrical systems malfunction subsequently attributed to arcing in a faulty electrical loom. The crew elected to divert to London Heathrow where emergency evacuation was carried out on a taxiway upon landing.

guid: https://skybrary.aero/accidents-and-incidents/b763-en-route-northern-france-1998 uri: https://skybrary.aero/accidents-and-incidents/b763-en-route-northern-france-1998 title: CRJ1, vicinity Brest France, 2003 link: https://skybrary.aero/accidents-and-incidents/crj1-vicinity-brest-france-2003 description:

On 22 June 2003, a Bombardier CRJ100 being operated by Brit Air flew an inaccurate night ILS approach and impacted terrain over a mile from the runway during an attempted unsuccessful go-around at Brest Guipavas Airport.

guid: https://skybrary.aero/accidents-and-incidents/crj1-vicinity-brest-france-2003 uri: https://skybrary.aero/accidents-and-incidents/crj1-vicinity-brest-france-2003 title: D328, Sumburgh UK, 2006 link: https://skybrary.aero/accidents-and-incidents/d328-sumburgh-uk-2006 description:

On 11 June 2006, a Dornier 328 operated by City Star Airlines whilst positioning in marginal visibility for a day approach at Sumburgh, Shetland Isles UK, and having incorrectly responded to TAWS Class A warnings/alerts by not gaining safe altitude, came to close proximity with terrain . The approach was continued and a safe landing was made at the airport.

guid: https://skybrary.aero/accidents-and-incidents/d328-sumburgh-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/d328-sumburgh-uk-2006 title: DC86, en-route, Narrows VA USA, 1996 link: https://skybrary.aero/accidents-and-incidents/dc86-en-route-narrows-va-usa-1996 description:

On 22 December 1996, during a post-maintenance airworthiness function flight at night in IMC, a Douglas DC8 operated by Airborne Express failed to recover from an intentional approach to the stall and loss of control without recovery followed leading to impact into mountainous terrain in the vicinity of Narrows, Virginia.

guid: https://skybrary.aero/accidents-and-incidents/dc86-en-route-narrows-va-usa-1996 uri: https://skybrary.aero/accidents-and-incidents/dc86-en-route-narrows-va-usa-1996 title: DH8A, vicinity Palmerston North New Zealand, 1995 link: https://skybrary.aero/accidents-and-incidents/dh8a-vicinity-palmerston-north-new-zealand-1995 description:

On 9 June 1995 a de Havilland DHC-8-100 collided with terrain some 16 km east of Palmerston North aerodrome while carrying out a daytime instrument approach. The airplane departed Auckland as scheduled Ansett New Zealand flight 703 to Palmerston North airport.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-vicinity-palmerston-north-new-zealand-1995 uri: https://skybrary.aero/accidents-and-incidents/dh8a-vicinity-palmerston-north-new-zealand-1995 title: JS41, Birmingham UK, 2007 link: https://skybrary.aero/accidents-and-incidents/js41-birmingham-uk-2007 description:

On 26 June 2007, at Birmingham Airport UK, a BAe Jetstream 41 started an engine running pushback without using intercom between ground crew and flight crew. The pushback could not be completed as the towbar could not be disconnected and confusion over a decision to return the aircraft to the gate resulted in an attempt to do so with the aircraft brakes selected which caused the aircraft nose landing gear to collapse.

guid: https://skybrary.aero/accidents-and-incidents/js41-birmingham-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/js41-birmingham-uk-2007 title: MD11, en-route, near Cape Ashizuri, Japan, 2007 link: https://skybrary.aero/accidents-and-incidents/md11-en-route-near-cape-ashizuri-japan-2007 description:

On 10 January 2007, a Transmile Air Services Boeing MD11F First Officer became suddenly incapacitated by seizure during a flight from Anchorage to Hong Kong. A diversion was made and the affected pilot hospitalised where the cause was identified as a previously non-symptomatic brain tumour.

guid: https://skybrary.aero/accidents-and-incidents/md11-en-route-near-cape-ashizuri-japan-2007 uri: https://skybrary.aero/accidents-and-incidents/md11-en-route-near-cape-ashizuri-japan-2007 title: RJ1H, vicinity Zurich Switzerland, 2001 link: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-zurich-switzerland-2001 description:

On 24 November 2001, a Crossair Avro RJ100 making a night non precision approach to Zurich violated approach minima and subsequently impacted terrain whilst making a delayed attempt to initiate a go around. The aircraft was destroyed by the impact and post crash fire and 24 of the 33 occupants were killed. The Investigation attributed the crash to the crew deliberately continuing descent below MDA without having acquired the prescribed visual reference. Both crew pairing and aspects of the crew as individuals were identified as the context.

guid: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-zurich-switzerland-2001 uri: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-zurich-switzerland-2001 title: MD82 / MD11, Anchorage AK USA, 2002 link: https://skybrary.aero/accidents-and-incidents/md82-md11-anchorage-ak-usa-2002 description:

On 17 March 2002, at Ted Stevens Anchorage Airport, a McDonnell Douglas MD82 operated by Alaska Airlines, on a night pushback in snow conditions collided with an inbound taxiing McDonnell Douglas MD-11. The MD82 suffered substantial rudder damage although the impacting MD11 winglet was undamaged.

guid: https://skybrary.aero/accidents-and-incidents/md82-md11-anchorage-ak-usa-2002 uri: https://skybrary.aero/accidents-and-incidents/md82-md11-anchorage-ak-usa-2002 title: MD83, vicinity Dublin Airport, Ireland, 2007 link: https://skybrary.aero/accidents-and-incidents/md83-vicinity-dublin-airport-ireland-2007 description:

On 16 August 2007, during a non-precision approach to RWY34 at Dublin airport, the flight crew of a MD83 misidentified the lights of a 16-storey hotel at Santry Cross as those of the runway approach lighting system. The aircraft deviated to the left of the approach course and descended below the Minimum Descent Altitude (MDA) without proper visual recognition of the runway in use. A go-around was initiated as soon as ATC corrective clearance was issued.

guid: https://skybrary.aero/accidents-and-incidents/md83-vicinity-dublin-airport-ireland-2007 uri: https://skybrary.aero/accidents-and-incidents/md83-vicinity-dublin-airport-ireland-2007 title: SF34, en-route, Santa Maria CA USA, 2006 link: https://skybrary.aero/accidents-and-incidents/sf34-en-route-santa-maria-ca-usa-2006 description:

On 2 January 2006, an American Eagle Saab 340 crew failed to notice a progressive loss of climb performance in icing conditions and control of the aircraft was lost when it stalled at 11,700 feet and was only recovered after a 5200 feet height loss. The Investigation noted that the aircraft had stalled prior to the activation of the Stall Protection System and that the climb had been conducted with the AP engaged and, contrary to SOP, with VS mode selected. It was concluded that SLD icing conditions had prevailed. Four Safety Recommendations were made and two previous ones reiterated.

guid: https://skybrary.aero/accidents-and-incidents/sf34-en-route-santa-maria-ca-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/sf34-en-route-santa-maria-ca-usa-2006 title: DH8D / TOR, en-route, North Sea UK, 2008 link: https://skybrary.aero/accidents-and-incidents/dh8d-tor-en-route-north-sea-uk-2008 description:

On 13 October 2008, a DHC-8 Q400 operating in uncontrolled airspace and in receipt of civil radar advisory service was given an avoiding action turn against military traffic but then received and actioned a TCAS RA whilst inside a notified Danger Area as a result of the avoiding action turn. No close proximity to other traffic resulted.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-tor-en-route-north-sea-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/dh8d-tor-en-route-north-sea-uk-2008 title: RJ85 / RJ1H, London City Airport, London UK, 2008 link: https://skybrary.aero/accidents-and-incidents/rj85-rj1h-london-city-airport-london-uk-2008 description:

On 21 April 2008, an Avro RJ85 aircraft was parked on Stand 10 at London City Airport, with an Avro RJ100 parked to its left, on the adjacent Stand 11. After being repositioned by a tug, the RJ85 taxied forward and to the right, its tail contacting the tail of the RJ100 and causing minor damage to the RJ100’s right elevator.

guid: https://skybrary.aero/accidents-and-incidents/rj85-rj1h-london-city-airport-london-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/rj85-rj1h-london-city-airport-london-uk-2008 title: NIM / AS32, vicinity RAF Kinloss UK, 2006 link: https://skybrary.aero/accidents-and-incidents/nim-as32-vicinity-raf-kinloss-uk-2006 description:

On 17 October 2006, at night, in low cloud and poor visibility conditions in the vicinity of Kinloss Airfield UK, a loss of separation event occurred between an RAF Nimrod MR2 aircraft and a civilian AS332L Puma helicopter.

guid: https://skybrary.aero/accidents-and-incidents/nim-as32-vicinity-raf-kinloss-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/nim-as32-vicinity-raf-kinloss-uk-2006 title: DH8D, vicinity Buffalo NY USA, 2009 link: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-buffalo-ny-usa-2009 description:

On 12 February 2009, a Bombardier DHC-8-400 on a night ILS approach to Buffalo-Niagara airport departed controlled flight and was completely destroyed by ground impact and subsequent fire. The Investigation found that the Captain had failed to effectively manage the flight and that his consequent response to a resulting stick shaker activation had been completely contrary to applicable procedures and his training, leading directly to the loss of the aircraft. The aircraft operator s normal approach procedures were also determined to be inadequate and it was noted that prior to the accident, sterile flight deck procedures had been comprehensively ignored.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-buffalo-ny-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-buffalo-ny-usa-2009 title: B742, en-route, south southeast of Jakarta Indonesia, 1982 link: https://skybrary.aero/accidents-and-incidents/b742-en-route-south-southeast-jakarta-indonesia-1982 description:

On 24 June 1982, a Boeing 747-200 had just passed Jakarta at FL370 in night VMC when it unknowingly entered an ash cloud from a recently begun new eruption of nearby volcano, Mount Galunggung, which the crew were unaware of. All engines failed in quick succession and a MAYDAY was declared. Involuntary descent began and a provisional diversion back to Jakarta, which would necessitate successful engine restarts to clear mountainous terrain en-route was commenced. Once clear of cloud with three successful engines restarts and level at FL120, the diversion plan was confirmed and completed with a visual approach from the overhead. 

guid: https://skybrary.aero/accidents-and-incidents/b742-en-route-south-southeast-jakarta-indonesia-1982 uri: https://skybrary.aero/accidents-and-incidents/b742-en-route-south-southeast-jakarta-indonesia-1982 title: A343, Anchorage AK USA, 2002 link: https://skybrary.aero/accidents-and-incidents/a343-anchorage-ak-usa-2002 description:

On 25 January 2002, in VMC at night, an Airbus A340-300 being operated by China Airlines successfully took-off from a parallel taxiway adjacent to the departure runway at Anchorage Alaska which was of less length than the calculated airplane take-off distance required.

guid: https://skybrary.aero/accidents-and-incidents/a343-anchorage-ak-usa-2002 uri: https://skybrary.aero/accidents-and-incidents/a343-anchorage-ak-usa-2002 title: A332, en-route, Atlantic Ocean, 2009 link: https://skybrary.aero/accidents-and-incidents/a332-en-route-atlantic-ocean-2009 description:

On 1 June 2009, an Airbus A330-200 being operated by Air France on a scheduled passenger flight from Rio de Janeiro to Paris CDG as AF447 exited controlled flight and crashed into the sea with the loss of the aircraft and all 228 occupants. It was found that the loss of control followed an inappropriate response by the flight crew to a transient loss of airspeed indications in the cruise which resulted from the vulnerability of the pitot heads to ice crystal icing.

guid: https://skybrary.aero/accidents-and-incidents/a332-en-route-atlantic-ocean-2009 uri: https://skybrary.aero/accidents-and-incidents/a332-en-route-atlantic-ocean-2009 title: A343, Changi Singapore, 2007 link: https://skybrary.aero/accidents-and-incidents/a343-changi-singapore-2007 description:

On 30 May 2007, at about 0555 hours local time, the crew of an Airbus A340-300 had to apply (Take-off Go Around) power and rotate abruptly at a high rate to become airborne while taking off from Runway 20C at Singapore Changi Airport, when they noticed the centreline lights were indicating the impending end of the available runway. The crew had calculated the take-off performance based on the full TORA (Take-off Run Available) of 4,000 m because they were unaware of the temporary shortening of Runway 20C to 2,500 m due to resurfacing works.

guid: https://skybrary.aero/accidents-and-incidents/a343-changi-singapore-2007 uri: https://skybrary.aero/accidents-and-incidents/a343-changi-singapore-2007 title: A343, London Heathrow UK, 1997 link: https://skybrary.aero/accidents-and-incidents/a343-london-heathrow-uk-1997 description:

On 5 November 1997, an Airbus A340-300 operated by Virgin Atlantic airlines experienced a landing gear malfunction. The crew executed a successful partial gear up landing at London Heathrow.

guid: https://skybrary.aero/accidents-and-incidents/a343-london-heathrow-uk-1997 uri: https://skybrary.aero/accidents-and-incidents/a343-london-heathrow-uk-1997 title: A343, Nairobi Kenya, 2008 link: https://skybrary.aero/accidents-and-incidents/a343-nairobi-kenya-2008 description:

On 27 April 2008 an Airbus A340-300 crew lost previously-acquired visual reference in fog on a night auto ILS into Nairobi but continued to a touchdown which occurred with the aircraft heading towards the edge of the runway following an inappropriate rudder input. The left main gear departed the paved surface and a go around was initiated and a diversion made. The event was attributed to a delay in commencing the go around. No measured RVR from any source was passed by ATC although it was subsequently found to have been recorded as I excess of Cat 1 limits throughout.

guid: https://skybrary.aero/accidents-and-incidents/a343-nairobi-kenya-2008 uri: https://skybrary.aero/accidents-and-incidents/a343-nairobi-kenya-2008 title: A345, Melbourne Australia, 2009 link: https://skybrary.aero/accidents-and-incidents/a345-melbourne-australia-2009 description:

On 20 March 2009 an Airbus A340-500, operated by Emirates, commenced a take-off roll for a normal reduced-thrust take-off on runway 16 at Melbourne Airport. The attempt to get the aircraft airborne resulted in a tail strike and an overrun because insufficient thrust had been set based upon an incorrect flight crew data entry.

guid: https://skybrary.aero/accidents-and-incidents/a345-melbourne-australia-2009 uri: https://skybrary.aero/accidents-and-incidents/a345-melbourne-australia-2009 title: A346, en-route, near Amsterdam Netherlands, 2005 link: https://skybrary.aero/accidents-and-incidents/a346-en-route-near-amsterdam-netherlands-2005 description:

On 8 February 2005 an Airbus A340-600 was 11 hours into its flight from Hong Kong to London Heathrow when the No 1 and No 4 engines ran down in quick succession. A fuel management problem rather than a fuel shortage was then diagnosed but a manual transfer was only partially successful and a diversion to Amsterdam was made on three engines. The Investigation found that the master Fuel Control and Monitoring Computer had failed, that timely warnings of automated fuel control system malfunctions were not provided and that alternate low fuel level warnings were inhibited by inappropriate system design.

guid: https://skybrary.aero/accidents-and-incidents/a346-en-route-near-amsterdam-netherlands-2005 uri: https://skybrary.aero/accidents-and-incidents/a346-en-route-near-amsterdam-netherlands-2005 title: AS32 / B734, Aberdeen UK, 2000 link: https://skybrary.aero/accidents-and-incidents/as32-b734-aberdeen-uk-2000 description:

For reasons that were not established, a Super Puma helicopter being air tested and in the hover at about 30 feet agl near the active runway at Aberdeen assumed that the departure clearance given by GND was a take off clearance and moved into the hover over the opposite end of the runway at the same time as a Boeing 737 was taking off. The 737 saw the helicopter ahead and made a high speed rejected take off, stopping approximately 100 metres before reaching the position of the helicopter which had by then moved off the runway still hovering.

guid: https://skybrary.aero/accidents-and-incidents/as32-b734-aberdeen-uk-2000 uri: https://skybrary.aero/accidents-and-incidents/as32-b734-aberdeen-uk-2000 title: AS32, en-route, North Sea Norway, 1998 link: https://skybrary.aero/accidents-and-incidents/as32-en-route-north-sea-norway-1998 description:

On 20 October 1998, in the North Sea, an Eurocopter AS332L Super Puma operated by Norsk HeliKopter AS, experienced engine failure with autorotation and subsequent lost of height. The crew misidentified the malfunctioning engine and reduced the power of the remaining serviceable engine. However, the mistake was realised quickly enough for the crew to recover control of the helicopter.

guid: https://skybrary.aero/accidents-and-incidents/as32-en-route-north-sea-norway-1998 uri: https://skybrary.aero/accidents-and-incidents/as32-en-route-north-sea-norway-1998 title: AS65, vicinity North Morecambe Platform Irish Sea UK, 2006 link: https://skybrary.aero/accidents-and-incidents/as65-vicinity-north-morecambe-platform-irish-sea-uk-2006 description:

On 27 December 2006, an AS365 Dauphin 2, operated by CHC Scotia, crashed into the sea adjacent to a gas platform in Morecambe Bay, UK, at night, following loss of control.

guid: https://skybrary.aero/accidents-and-incidents/as65-vicinity-north-morecambe-platform-irish-sea-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/as65-vicinity-north-morecambe-platform-irish-sea-uk-2006 title: AT43, vicinity Stansted UK, 2007 link: https://skybrary.aero/accidents-and-incidents/at43-vicinity-stansted-uk-2007 description:

On 18 January 2007 an ATR 42-300 freighter developed a control difficulty just after a night take off from Stansted UK, which led the flight crew to declare an emergency and undertake an immediate return to land. The landing was uneventful but the approach flown was unstable, with EGPWS warnings, and the origin of the handling difficulty was considered to be, in part, due to inappropriate control inputs by one of the pilots.

guid: https://skybrary.aero/accidents-and-incidents/at43-vicinity-stansted-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/at43-vicinity-stansted-uk-2007 title: AT43, en-route, Folgefonna Norway, 2005 link: https://skybrary.aero/accidents-and-incidents/at43-en-route-folgefonna-norway-2005 description:

On 14 September 2005, an ATR 42-320 operated by Coast Air AS experienced a continuous build up of ice in the climb, despite the activation of de-icing systems aircraft entered an uncontrolled roll and lost 1500ft in altitude. The crew initiated recovery actions, the aircraft was stabilised, and the flight continued without further event.

guid: https://skybrary.aero/accidents-and-incidents/at43-en-route-folgefonna-norway-2005 uri: https://skybrary.aero/accidents-and-incidents/at43-en-route-folgefonna-norway-2005 title: AT45, vicinity Sienajoki Finland, 2007 link: https://skybrary.aero/accidents-and-incidents/at45-vicinity-sienajoki-finland-2007 description:

On 1 January 2007, the crew of a ATR 42-500 carried out successive night approaches into Seinajoki Finland including three with EGPWS warnings, one near stall, and one near loss of control, all attributed to poor flight crew performance including use of the wrong barometric sub scale setting.

guid: https://skybrary.aero/accidents-and-incidents/at45-vicinity-sienajoki-finland-2007 uri: https://skybrary.aero/accidents-and-incidents/at45-vicinity-sienajoki-finland-2007 title: AT43, vicinity Geneva Switzerland, 2006 link: https://skybrary.aero/accidents-and-incidents/at43-vicinity-geneva-switzerland-2006 description:

On 29 March 2006 at about 1 mile from touchdown when in VMC on a night approach to destination Geneva, an ATR 42-300 being operated by Farnair on a cargo flight experienced a sudden electrical fire in the flight deck and an emergency was declared to ATC. Despite this situation the aircraft was able to land normally and vacate the runway via an RET after which it was forced to stop.

guid: https://skybrary.aero/accidents-and-incidents/at43-vicinity-geneva-switzerland-2006 uri: https://skybrary.aero/accidents-and-incidents/at43-vicinity-geneva-switzerland-2006 title: AT73, en-route, Roselawn IN USA, 1994 link: https://skybrary.aero/accidents-and-incidents/at73-en-route-roselawn-usa-1994 description:

On 31 October 1994, an ATR 72 exited controlled flight after a flap retraction when descending through 9000 feet was followed by autopilot disconnect and rapid and very large un-commanded roll inputs from which recovery, not within the scope of received crew training, was not achieved. The investigation found this roll upset had been due to a sudden and unexpected aileron hinge moment reversal after ice accretion on the upper wings aft of the leading edge pneumatic de-icing boots during earlier holding in icing conditions which had been - unknown to the crew - outside the icing certification envelope.

guid: https://skybrary.aero/accidents-and-incidents/at73-en-route-roselawn-usa-1994 uri: https://skybrary.aero/accidents-and-incidents/at73-en-route-roselawn-usa-1994 title: AT72, en-route, Mediterranean Sea near Palermo Italy, 2005 link: https://skybrary.aero/accidents-and-incidents/at72-en-route-mediterranean-sea-near-palermo-italy-2005 description:

On 6 August 2005, a Tuninter ATR 72-210 was ditched near Palermo after fuel was unexpectedly exhausted en route. The aircraft broke into three sections on impact and 16 of the 39 occupants died. The Investigation found that insufficient fuel had been loaded prior to flight because the flight crew relied exclusively upon the fuel quantity gauges which had been fitted incorrectly by maintenance personnel. It was also found that the pilots had not fully followed appropriate procedures after the engine run down and that if they had, it was at least possible that a ditching could have been avoided.

guid: https://skybrary.aero/accidents-and-incidents/at72-en-route-mediterranean-sea-near-palermo-italy-2005 uri: https://skybrary.aero/accidents-and-incidents/at72-en-route-mediterranean-sea-near-palermo-italy-2005 title: ATP, en-route, Oxford UK, 1991 link: https://skybrary.aero/accidents-and-incidents/atp-en-route-oxford-uk-1991 description:

On 11 August 1991, an British Aerospace ATP, during climb to flight level (FL) 160 in icing conditions, experienced a significant degradation of performance due to propeller icing accompanied by severe vibration that rendered the electronic flight instruments partially unreadable. As the aircraft descended below cloud, control was regained and the flight continued uneventfully.

guid: https://skybrary.aero/accidents-and-incidents/atp-en-route-oxford-uk-1991 uri: https://skybrary.aero/accidents-and-incidents/atp-en-route-oxford-uk-1991 title: B190, vicinity Charlotte NC USA, 2003 link: https://skybrary.aero/accidents-and-incidents/b190-vicinity-charlotte-nc-usa-2003 description:

On 8 January 2003, a B190, operated by Air Midwest, crashed shortly after take off from Charlotte, NC, USA, following loss of pitch control during takeoff. The accident was attributed to incorrect rigging of the elevator control system compounded by the airplane being outside load and balance limitations.

guid: https://skybrary.aero/accidents-and-incidents/b190-vicinity-charlotte-nc-usa-2003 uri: https://skybrary.aero/accidents-and-incidents/b190-vicinity-charlotte-nc-usa-2003 title: B190 / B190, Auckland NZ, 2007 link: https://skybrary.aero/accidents-and-incidents/b190-b190-auckland-nz-2007 description:

On 1 August 2007, the crew of a Beech 1900 aircraft holding on an angled taxiway at Auckland International Airport mistakenly accepted the take-off clearance for another Beech 1900 that was waiting on the runway and which had a somewhat similar call sign. The pilots of both aircraft read back the clearance. The aerodrome controller heard, but did not react to, the crossed transmissions. The holding aircraft entered the runway in front of the cleared aircraft, which had commenced its take-off. The pilots of both aircraft took avoiding action and stopped on the runway without any damage or injury.

guid: https://skybrary.aero/accidents-and-incidents/b190-b190-auckland-nz-2007 uri: https://skybrary.aero/accidents-and-incidents/b190-b190-auckland-nz-2007 title: SF34 / B190, Auckland NZ, 2007 link: https://skybrary.aero/accidents-and-incidents/sf34-b190-auckland-nz-2007 description:

On 29 May 2007, a Saab 340 aircraft that was holding on an angled taxiway at Auckland International Airport was inadvertently cleared to line up in front of a landing Raytheon 1900D. The aerodrome controller transmitted an amended clearance, but the transmission crossed with that of the Saab crew reading back the line-up clearance. The pilots of both aircraft took action to avoid a collision and stopped on the runway without any damage or injury.

guid: https://skybrary.aero/accidents-and-incidents/sf34-b190-auckland-nz-2007 uri: https://skybrary.aero/accidents-and-incidents/sf34-b190-auckland-nz-2007 title: B190 / BE9L, Quincy IL USA, 1996 link: https://skybrary.aero/accidents-and-incidents/b190-be9l-quincy-il-usa-1996 description:

On 19 November 1996, a Beech 1900C which had just landed and a Beech King Air A90 which was taking off collided at the intersection of two runways at the non-Towered Quincy Municipal Airport. Both aircraft were destroyed by impact forces and fire and all occupants of both aircraft were killed. The Investigation found that the King Air pilots had failed to monitor the CTAF or properly scan visually for traffic. The loss of life of the Beech 1900 occupants, who had probably survived the impact, was attributed largely to inability to open the main door of the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/b190-be9l-quincy-il-usa-1996 uri: https://skybrary.aero/accidents-and-incidents/b190-be9l-quincy-il-usa-1996 title: B722, Hamilton OT Canada 2008 link: https://skybrary.aero/accidents-and-incidents/b722-hamilton-ot-canada-2008 description:

On 22 July 2008, a Kelowna Flightcraft Air Charter Ltd. Boeing 727-200 was operating a cargo flight from Moncton NB, to Hamilton, OT. After radar vectoring for an approach to Runway 06 at Hamilton, the aircraft touched down hard and bounced before touching down hard a second time. Immediately after the second touchdown, a go-around was initiated. During rotation, the tailskid made contact with the runway. The thrust reverser actuator fairing and the number 2 engine tailpipe made contact with the ground off the departure end of the runway. The aircraft climbed away and then returned for a normal landing on Runway 12. There were no injuries; the aircraft sustained only minor damage.

guid: https://skybrary.aero/accidents-and-incidents/b722-hamilton-ot-canada-2008 uri: https://skybrary.aero/accidents-and-incidents/b722-hamilton-ot-canada-2008 title: B732, Seattle WA USA, 2006 link: https://skybrary.aero/accidents-and-incidents/b732-seattle-wa-usa-2006 description:

On 30 October 2006, at Seattle-Tacoma International Airport, Seattle, Washington a Boeing 737-200 operated by Alaska Airlines, took off in daylight from a runway parallel to that which had been cleared with no actual adverse consequences.

guid: https://skybrary.aero/accidents-and-incidents/b732-seattle-wa-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/b732-seattle-wa-usa-2006 title: B732, en-route, Maui Hawaii, 1988 link: https://skybrary.aero/accidents-and-incidents/b732-en-route-maui-hawaii-1988 description:

On 28 April 1988, a Boeing 737-200, operated by Aloha Airlines experienced an explosive depressurisation and structural failure at FL 240. Approximately 5.5 metres (or 18 feet) of cabin covering and structure was detached from the aircraft during flight. As result of the depressurisation, a member of the cabin crew was fatally injured. The flight crew performed an emergency descent, landing at Kahului Airport on the Island of Maui, Hawaii.

guid: https://skybrary.aero/accidents-and-incidents/b732-en-route-maui-hawaii-1988 uri: https://skybrary.aero/accidents-and-incidents/b732-en-route-maui-hawaii-1988 title: B732, Manchester UK, 1985 link: https://skybrary.aero/accidents-and-incidents/b732-manchester-uk-1985 description:

On 22nd August 1985, a B737-200 being operated by British Airtours, a wholly-owned subsidiary of British Airways, suffered an uncontained engine failure, with consequent damage from ejected debris enabling the initiation of a fuel-fed fire which spread to the fuselage during the rejected take off and continued to be fuel-fed after the aircraft stopped, leading to rapid destruction of the aircraft before many of the occupants had evacuated.

guid: https://skybrary.aero/accidents-and-incidents/b732-manchester-uk-1985 uri: https://skybrary.aero/accidents-and-incidents/b732-manchester-uk-1985 title: B732, Pekanbaru Indonesia, 2002 link: https://skybrary.aero/accidents-and-incidents/b732-pekanbaru-indonesia-2002 description:

On 14 January 2002, a Boeing 737-200, operated by Lion Air, attempted to complete a daylight take off from Pekanbaru, Indonesia without flaps set after a failure to complete the before take off checks. The rejected take off was not initiated promptly and the aircraft overran the runway. The take off configuration warning failed to sound because the associated circuit breaker was so worn that it had previously auto-tripped and this had not been noticed.

guid: https://skybrary.aero/accidents-and-incidents/b732-pekanbaru-indonesia-2002 uri: https://skybrary.aero/accidents-and-incidents/b732-pekanbaru-indonesia-2002 title: B732, vicinity Tamanrassat Algeria, 2003 link: https://skybrary.aero/accidents-and-incidents/b732-vicinity-tamanrassat-algeria-2003 description:

On 6 March 2003, a Boeing 737-200 being operated by Air Algerie had just become airborne during a daylight departure when the left hand engine suddenly failed just after the PF had called for gear up . Shortly afterwards, the aircraft commander, who had been PNF for the departure, took control but the normal pitch attitude was not reduced to ensure that a minimum airspeed of V2 was maintained and landing gear was not retracted. The aircraft lost airspeed, stalled and impacted the ground approximately 1nm from the point at which it had become airborne. A severe post crash fire occurred and the aircraft was destroyed and all on board except one passenger, were killed.

guid: https://skybrary.aero/accidents-and-incidents/b732-vicinity-tamanrassat-algeria-2003 uri: https://skybrary.aero/accidents-and-incidents/b732-vicinity-tamanrassat-algeria-2003 title: B733, vicinity Manchester UK, 1997 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-manchester-uk-1997 description:

On 1 August 1997, an Air Malta B737, descending for an approach into Manchester UK in poor weather, descended significantly below the cleared and correctly acknowledged altitude, below MSA.

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-manchester-uk-1997 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-manchester-uk-1997 title: B733, vicinity Sharm El-Sheikh Egypt, 2004 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-sharm-el-sheikh-egypt-2004 description:

On 3 January 3 2004, a Boeing 737-300 being operated by Flash Airlines on a passenger charter flight from Sharm el-Sheikh Egypt to Cairo for a refuelling stop en route to Paris CDG crashed into the sea 2½ minutes after a night take off into VMC and was destroyed and all 148 occupants killed. The Investigation was unable to establish a Probable Cause but found evidence of AP status confusion and the possibility of distraction leading to insufficient attention being paid to flight path control.

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-sharm-el-sheikh-egypt-2004 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-sharm-el-sheikh-egypt-2004 title: B733, en-route, northwest of Athens Greece, 2005 link: https://skybrary.aero/accidents-and-incidents/b733-en-route-northwest-athens-greece-2005 description:

On 14 August 2005, a Boeing 737-300 was released to service with the cabin pressurisation set to manual. This abnormal setting was not detected by the flight crew involved during standard checks. They took no corrective action after take-off when a cabin high altitude warning occurred. The crew lost consciousness as the aircraft climbed on autopilot and after eventual fuel exhaustion, the aircraft departed controlled flight and impacted terrain. The Investigation found that inadequate crew performance had occurred within a context of systemic organisational safety deficiencies at the Operator compounded by inadequate regulatory oversight.

guid: https://skybrary.aero/accidents-and-incidents/b733-en-route-northwest-athens-greece-2005 uri: https://skybrary.aero/accidents-and-incidents/b733-en-route-northwest-athens-greece-2005 title: B732 / A321, Manchester UK, 2004 link: https://skybrary.aero/accidents-and-incidents/b732-a321-manchester-uk-2004 description:

On 29 February 2004, a Boeing 737-200 crossed an active runway in normal daylight visibility ahead of a departing Airbus A321, the crew of which made a high speed rejected take off upon sighting the other aircraft after hearing its crossing clearance being confirmed. Both aircraft were found to have been operating in accordance with their acknowledged ATC clearances issued by the same controller. An alert was generated by the TWR conflict detection system but it was only visually annunciated and had not been noticed. Related ATC procedures were subsequently reviewed and improved.

guid: https://skybrary.aero/accidents-and-incidents/b732-a321-manchester-uk-2004 uri: https://skybrary.aero/accidents-and-incidents/b732-a321-manchester-uk-2004 title: B733, vicinity Bournemouth UK, 2007 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-bournemouth-uk-2007 description:

On 23 September 2007, the pilots of a Thomsonfly Boeing 737-300 almost lost control of their aircraft after initiating a go around from an unstable low airspeed and low thrust condition reached progressively but unnoticed during an approach to Bournemouth at night. Mismanagement of the aircraft during the go around was attributed to a lack of adequate understanding of the aircraft pitch control system and led to extreme pitch and an aerodynamic stall but the crew subsequently recovered control of the aircraft and an uneventful second approach and normal landing followed.

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-bournemouth-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-bournemouth-uk-2007 title: B733, vicinity Pittsburg PA USA, 1994 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-pittsburg-pa-usa-1994 description:

On 8 September 1994, a US Air Boeing 737-300 crashed near Pittsburg USA following loss of control attributed to a rudder malfunction.

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-pittsburg-pa-usa-1994 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-pittsburg-pa-usa-1994 title: B733, vicinity Helsinki Finland, 2008 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-helsinki-finland-2008 description:

On 26 March 2008, a Ukraine International Airlines Boeing 737-300 being vectored by ATC to the ILS at destination Helsinki in IMC descended below its cleared altitude and came close to a telecommunications mast. ATC noticed the deviation and instructed a climb. The investigation attributed the non-compliance with the accepted descent clearance to the failure of the flight crew to operate in accordance with SOPs. It was also noted that the way in which ATC safety systems were installed and configured at the time of the occurrence had precluded earlier ATC awareness of the hazard caused by the altitude deviation.

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-helsinki-finland-2008 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-helsinki-finland-2008 title: B734, Aberdeen UK, 2005 link: https://skybrary.aero/accidents-and-incidents/b734-aberdeen-uk-2005 description:

Significant damage was caused to the tailplane and elevator of a Boeing 737-400 after the pavement beneath them broke up when take off thrust was applied for a standing start from the full length of the runway at Aberdeen. Although in this case neither outcome applied, the Investigation noted that control difficulties consequent upon such damage could lead to an overrun following a high speed rejected takeoff or to compromised flight path control airborne. Safety Recommendations on appropriate regulatory guidance for marking and construction of blast pads and on aircraft performance, rolling take offs and lead-on line marking were made.

guid: https://skybrary.aero/accidents-and-incidents/b734-aberdeen-uk-2005 uri: https://skybrary.aero/accidents-and-incidents/b734-aberdeen-uk-2005 title: B734, en-route, Sulawesi Indonesia, 2007 link: https://skybrary.aero/accidents-and-incidents/b734-en-route-sulawesi-indonesia-2007 description:

On 1 January 2007, a B737-400 crashed into the sea off Sulawesi, Indonesia, after the crew lost control of the aircraft having become distracted by a minor technical problem.

guid: https://skybrary.aero/accidents-and-incidents/b734-en-route-sulawesi-indonesia-2007 uri: https://skybrary.aero/accidents-and-incidents/b734-en-route-sulawesi-indonesia-2007 title: SF34, vicinity Zurich Switzerland, 2000 link: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-zurich-switzerland-2000 description:

On 10 January 2000, two minutes and 17 seconds after departure from Zurich airport, at night in instrument meteorological conditions (IMC), a Saab 340 operated by Crossair, entered into right-hand dive and crashed.

guid: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-zurich-switzerland-2000 uri: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-zurich-switzerland-2000 title: B735, vicinity Perm Russian Federation, 2008 link: https://skybrary.aero/accidents-and-incidents/b735-vicinity-perm-russian-federation-2008 description:

On September 13 2008, at night and in good visual conditions*, a Boeing 737-500 operated by Aeroflot-Nord executed an unstabilised approach to Runway 21 at Bolshoye Savino Airport (Perm) which subsequently resulted in loss of control and terrain impact.

guid: https://skybrary.aero/accidents-and-incidents/b735-vicinity-perm-russian-federation-2008 uri: https://skybrary.aero/accidents-and-incidents/b735-vicinity-perm-russian-federation-2008 title: A320, vicinity Sochi Russia, 2006 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-sochi-russia-2006 description:

On 3 May 2006, an Airbus 320 crew failed to correctly fly a night IMC go around at Sochi and the aircraft crashed into the sea and was destroyed. The Investigation found that the crew failed to reconfigure the aircraft for the go around and, after having difficulties with the performance of an auto go-around, had disconnected the autopilot. Inappropriate control inputs, including simultaneous (summed) sidestick inputs by both pilots were followed by an EGPWS PULL UP Warning. There was no recovery and about a minute into the go around, a steep descent into the sea at 285 knots occurred.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-sochi-russia-2006 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-sochi-russia-2006 title: B738, vicinity Douala Cameroon, 2007 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-douala-cameroon-2007 description:

On 5 May 2007, a Kenya Airways Boeing 737-800 departing Douala at night crashed shortly after take-off following an unsuccessful attempt at recovery after late recognition of a progressive right roll which led to spiral dive. The Investigation was unable to positively establish the reason for the unintended roll, but noted that it ad not been possible to determine whether the pilots, and in particular the aircraft commander, had been aware of the fact that the AP was not engaged.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-douala-cameroon-2007 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-douala-cameroon-2007 title: B733, en-route, Santa Barbara CA USA, 1999 link: https://skybrary.aero/accidents-and-incidents/b733-en-route-santa-barbara-ca-usa-1999 description:

On 2 September 1999, a United Airlines Boeing Boeing 737-300 in the cruise at FL240, experienced severe turbulence due to an encounter with the wake vortex from a preceding MD11 on a similar track which had climbed through the level of the B737 with minimum lateral separation, 1.5 minutes earlier.

guid: https://skybrary.aero/accidents-and-incidents/b733-en-route-santa-barbara-ca-usa-1999 uri: https://skybrary.aero/accidents-and-incidents/b733-en-route-santa-barbara-ca-usa-1999 title: B734, Barcelona Spain, 2004 link: https://skybrary.aero/accidents-and-incidents/b734-barcelona-spain-2004 description:

On 28 November 2004, a KLM B737-400 departed laterally from the runway on landing at Barcelona due to the effects on the nosewheel steering of a bird strike which had occured as the aircraft took off from Amsterdam.

guid: https://skybrary.aero/accidents-and-incidents/b734-barcelona-spain-2004 uri: https://skybrary.aero/accidents-and-incidents/b734-barcelona-spain-2004 title: B734, en-route, Daventry UK, 1995 link: https://skybrary.aero/accidents-and-incidents/b734-en-route-daventry-uk-1995 description:

On 23 February 1995, a British Midland Boeing 737-400 made an emergency landing at Luton airport UK after losing most of the oil from both engines during initial climb out from East Midlands airport UK, attributed to failures in the quality of maintenance work and procedures during routine inspections of both engines prior to the flight.

guid: https://skybrary.aero/accidents-and-incidents/b734-en-route-daventry-uk-1995 uri: https://skybrary.aero/accidents-and-incidents/b734-en-route-daventry-uk-1995 title: B735, Newark NJ USA, 2006 link: https://skybrary.aero/accidents-and-incidents/b735-newark-nj-usa-2006 description:

On 21 August 2006, a Boeing 737-500 suffered a nose landing gear collapse during towing at the Newark Liberty International Airport. A technical crew was repositioning the aircraft in visual meteorological conditions during the occurrence. No persons were injured and minor aircraft damage occurred.

guid: https://skybrary.aero/accidents-and-incidents/b735-newark-nj-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/b735-newark-nj-usa-2006 title: B734, vicinity East Midlands UK, 1989 link: https://skybrary.aero/accidents-and-incidents/b734-vicinity-east-midlands-uk-1989 description:

On 8 January 1989, the crew of a British Midland Boeing 737-400 lost control of their aircraft due to lack of engine thrust shortly before reaching a planned en route diversion being made after an engine malfunction and it was destroyed by terrain impact with fatal or serious injuries sustained by almost all the occupants. The crew response to the malfunction had been followed by their shutdown of the serviceable rather the malfunctioning engine. The Investigation concluded that the accident was entirely the consequence of inappropriate crew response to a non-critical loss of powerplant airworthiness.

guid: https://skybrary.aero/accidents-and-incidents/b734-vicinity-east-midlands-uk-1989 uri: https://skybrary.aero/accidents-and-incidents/b734-vicinity-east-midlands-uk-1989 title: B734, en-route, New South Wales Australia, 2007 link: https://skybrary.aero/accidents-and-incidents/b734-en-route-new-south-wales-australia-2007 description:

On 11 August 2007, a Qantas Boeing 737-400 on a scheduled passenger service from Perth, WA to Sydney, NSW was about three quarters of the way there in day VMC when the master caution light illuminated associated with low output pressure of both main tank fuel pumps. The flight crew then observed that the centre tank fuel pump switches on the forward overhead panel were selected to the OFF position and he immediately selected them to the ON position. The flight was completed without further event.

guid: https://skybrary.aero/accidents-and-incidents/b734-en-route-new-south-wales-australia-2007 uri: https://skybrary.aero/accidents-and-incidents/b734-en-route-new-south-wales-australia-2007 title: B735, en-route, North East of London UK, 1996 link: https://skybrary.aero/accidents-and-incidents/b735-en-route-north-east-london-uk-1996 description:

On 5 September 1996, a Boeing 737-500 operated by British Midland, encountered severe wake turbulence whilst in the hold over London. The wake was attributed to a B767 some 6 nm ahead.

guid: https://skybrary.aero/accidents-and-incidents/b735-en-route-north-east-london-uk-1996 uri: https://skybrary.aero/accidents-and-incidents/b735-en-route-north-east-london-uk-1996 title: B735, vicinity London Heathrow UK, 2007 link: https://skybrary.aero/accidents-and-incidents/b735-vicinity-london-heathrow-uk-2007 description:

On 7 June 2007, a Boeing 737-500 operated by LOT Polish Airlines, after daylight takeoff from London Heathrow Airport lost most of the information displayed on Electronic Flight Instrument System (EFIS). The information in both Electronic Attitude Director Indicator (EADI) and Electronic Horizontal Situation Indicators (EHSI) disappeared because the flight crew inadvertently mismanaged the Flight Management System (FMS). Subsequently the crew had difficulties both in maintaining the aircraft control manually using the mechanical standby instruments and communicating adequately with ATC due to insufficient language proficiency. Although an emergency situation was not declared, the ATC realized the seriousness of the circumstances and provided discrete frequency and a safe return after 27 minutes of flight was achieved.

guid: https://skybrary.aero/accidents-and-incidents/b735-vicinity-london-heathrow-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/b735-vicinity-london-heathrow-uk-2007 title: B737, manoeuvring, west of Norwich UK 2009 link: https://skybrary.aero/accidents-and-incidents/b737-manoeuvring-west-norwich-uk-2009 description:

On 12 January 2009, the flight crew of an Easyjet Boeing 737-700 on an airworthiness function flight out of Southend lost control of the aircraft during a planned system test. Controlled flight was only regained after an altitude loss of over 9000 ft, during which various exceedences of the AFM Flight Envelope occurred. The subsequent investigation found that the Aircraft Operators procedures for such flights were systemically flawed.

guid: https://skybrary.aero/accidents-and-incidents/b737-manoeuvring-west-norwich-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/b737-manoeuvring-west-norwich-uk-2009 title: B735, vicinity Billund Denmark, 1999 link: https://skybrary.aero/accidents-and-incidents/b735-vicinity-billund-denmark-1999 description:

On 3rd December 1999, a Boeing 737-500 being operated by Maersk Air on a scheduled passenger flight from Birmingham to Copenhagen made a successful diversion to Billund in conditions of poor weather across the whole of the destination area after a go around at the intended destination but but landed with less than Final Reserve Fuel.

guid: https://skybrary.aero/accidents-and-incidents/b735-vicinity-billund-denmark-1999 uri: https://skybrary.aero/accidents-and-incidents/b735-vicinity-billund-denmark-1999 title: B738, Naha Japan, 2007 link: https://skybrary.aero/accidents-and-incidents/b738-naha-japan-2007 description:

On 20 August 2007, as a Boeing 737-800 being operated by China Airlines on a scheduled passenger flight arrived on the designated nose-in parking stand at destination Naha, Japan in daylight and normal visibility, fuel began to leak from the right wing near to the engine pod and ignited. An evacuation was quickly initiated and all 165 occupants including 8 crew members were able to leave the aircraft before it was engulfed by the fire, which spread rapidly and led to the destruction of the aircraft and major damage to the apron surface. As the stand was not adjacent to the terminal and not served by an air bridge, there was no damage to structures. All occupants had left the aircraft before the Airport RFFS arrived at the scene.

guid: https://skybrary.aero/accidents-and-incidents/b738-naha-japan-2007 uri: https://skybrary.aero/accidents-and-incidents/b738-naha-japan-2007 title: B738, Oslo Gardermoen Norway, 2005 link: https://skybrary.aero/accidents-and-incidents/b738-oslo-gardermoen-norway-2005 description:

On a 23 October, 2005 a Boeing 737-800 operated by Pegasus Airlines, during night time, commenced a take-off roll on a parallel taxiway at Oslo Airport Gardermoen. The aircraft was observed by ATC and stop instruction was issued resulting in moderate speed rejected take-off (RTO).

guid: https://skybrary.aero/accidents-and-incidents/b738-oslo-gardermoen-norway-2005 uri: https://skybrary.aero/accidents-and-incidents/b738-oslo-gardermoen-norway-2005 title: B738, vicinity Amsterdam Netherlands, 2009 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-amsterdam-netherlands-2009 description:

On 25 February 2009, a Boeing 737-800 crew making an automatic ILS approach to Amsterdam with the operating First Officer undergoing early stage line training and a Safety Pilot occupying the supernumerary crew seat lost control after a malfunction of one of the radio altimeters, which resulted in the autothrottle unexpectedly setting idle thrust. The resultant progressive pitch increase went unnoticed by any of the pilots until an EGPWS ‘PULL UP’ Warning occurred. A delayed response then prevented recovery and terrain impact followed with the aircraft wrecked but with no post crash fire and only nine fatalities amongst the 135 occupants.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-amsterdam-netherlands-2009 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-amsterdam-netherlands-2009 title: B738, Manchester UK, 2003 link: https://skybrary.aero/accidents-and-incidents/b738-manchester-uk-2003 description:

On 16 July 2003, a Boeing 737-800, being operated by Excel Airlines on a passenger flight from Manchester to Kos began take off on Runway 06L without the flight crew being aware of work in progress at far end of the runway. The take off calculations, based on the full runway length resulted in the aircraft passing within 56 ft of a 14 ft high vehicle just after take off.

guid: https://skybrary.aero/accidents-and-incidents/b738-manchester-uk-2003 uri: https://skybrary.aero/accidents-and-incidents/b738-manchester-uk-2003 title: B739, Akita Japan, 2007 link: https://skybrary.aero/accidents-and-incidents/b739-akita-japan-2007 description:

On 6 January 2007, a Boeing B737-900 operated by Korean Airlines landed at Akita Airport on a taxiway parallel to the in-use runway after a daylight non-precision approach (NPA) using a head-up display (HUD). The crew realised their error during the landing roll.

guid: https://skybrary.aero/accidents-and-incidents/b739-akita-japan-2007 uri: https://skybrary.aero/accidents-and-incidents/b739-akita-japan-2007 title: B741, en-route, Gunma Japan 1985 link: https://skybrary.aero/accidents-and-incidents/b741-en-route-gunma-japan-1985 description:

On August 12, 1985 a Boeing 747 SR-100 operated by Japan Air Lines experienced a loss of control attributed to loss of the vertical stabiliser. After the declaration of the emergency, the aircraft continued its flight for 30 minutes and subsequently impacted terrain in a mountainous area in Gunma Prefecture, Japan.

guid: https://skybrary.aero/accidents-and-incidents/b741-en-route-gunma-japan-1985 uri: https://skybrary.aero/accidents-and-incidents/b741-en-route-gunma-japan-1985 title: B741, en-route, East Moriches NY USA, 1996 link: https://skybrary.aero/accidents-and-incidents/b741-en-route-east-moriches-ny-usa-1996 description:

On 17 July 1996, a Boeing 747, operated by TWA, experienced an in-flight breakup and then crashed into the Atlantic Ocean near East Moriches, New York, USA.

guid: https://skybrary.aero/accidents-and-incidents/b741-en-route-east-moriches-ny-usa-1996 uri: https://skybrary.aero/accidents-and-incidents/b741-en-route-east-moriches-ny-usa-1996 title: B742, en-route, Penghu Island Taiwan, 2002 link: https://skybrary.aero/accidents-and-incidents/b742-en-route-penghu-island-taiwan-2002 description:

On 25 May 2002, a China Airlines Boeing 747-200 broke up in mid air, over Penghu Island Taiwan, following structural failure as a result of an improper repair in 1980, which had not been detected by subsequent inspections.

guid: https://skybrary.aero/accidents-and-incidents/b742-en-route-penghu-island-taiwan-2002 uri: https://skybrary.aero/accidents-and-incidents/b742-en-route-penghu-island-taiwan-2002 title: B742 / A320, Frankfurt Germany, 2006 link: https://skybrary.aero/accidents-and-incidents/b742-a320-frankfurt-germany-2006 description:

On 12 January 2006, an Air China Boeing 747-200 which had just landed at Frankfurt failed to correctly understand and read back its taxi in clearance and the incorrect readback was not detected by the controller. The 747 then crossed another runway at night and in normal visibility whilst an A320 was landing on it. The A320 responded by increased braking and there was consequently no actual risk of collision. The controller had not noticed the incursion and, in accordance with instructions, all stop bars were unlit and the RIMCAS had been officially disabled due to too many nuisance activations.

guid: https://skybrary.aero/accidents-and-incidents/b742-a320-frankfurt-germany-2006 uri: https://skybrary.aero/accidents-and-incidents/b742-a320-frankfurt-germany-2006 title: B742, vicinity Stansted UK, 1999 link: https://skybrary.aero/accidents-and-incidents/b742-vicinity-stansted-uk-1999 description:

On 22 December 1999, a KAL Boeing 747 freighter crashed shortly after take-off from Stansted UK, following an ADI malfunction.

guid: https://skybrary.aero/accidents-and-incidents/b742-vicinity-stansted-uk-1999 uri: https://skybrary.aero/accidents-and-incidents/b742-vicinity-stansted-uk-1999 title: A333, Hong Kong China, 2010 link: https://skybrary.aero/accidents-and-incidents/a333-hong-kong-china-2010 description:

On 13 April 2010, a Cathay Pacific Airbus A330-300 en route from Surabaya to Hong Kong experienced difficulty in controlling engine thrust. As these problems worsened, one engine became unusable and a PAN and then a MAYDAY were declared prior to a successful landing at destination with excessive speed after control of thrust from the remaining engine became impossible. Emergency evacuation followed after reports of a landing gear fire. Salt water contamination of the hydrant fuel system at Surabaya after alterations during airport construction work was found to have led to the appearance of a polymer contaminant in uplifted fuel.

guid: https://skybrary.aero/accidents-and-incidents/a333-hong-kong-china-2010 uri: https://skybrary.aero/accidents-and-incidents/a333-hong-kong-china-2010 title: B741, en-route, Pacific Ocean, 1997 link: https://skybrary.aero/accidents-and-incidents/b741-en-route-pacific-ocean-1997 description:

On 28th December 1997, a Boeing 747-100 being operated by United Airlines, which had departed from Tokyo for Hawaii, encountered severe turbulence thought to have been associated with a Jet Stream over the Pacific Ocean.

guid: https://skybrary.aero/accidents-and-incidents/b741-en-route-pacific-ocean-1997 uri: https://skybrary.aero/accidents-and-incidents/b741-en-route-pacific-ocean-1997 title: B744 / A321, London Heathrow UK, 2004 link: https://skybrary.aero/accidents-and-incidents/b744-a321-london-heathrow-uk-2004 description:

On 23 March 2004, an out of service British Airways Boeing 747-400, under tow passed behind a stationary Airbus A321-200 being operated by Irish Airline Aer Lingus on a departing scheduled passenger service in good daylight visibility and the wing tip of the 747 impacted and seriously damaged the rudder of the A321. The aircraft under tow was cleared for the towing movement and the A321 was holding position in accordance with clearance. The towing team were not aware of the collision and initially, there was some doubt in the A321 flight deck about the cause of a shudder felt when the impact occurred but the cabin crew of the A321 had felt the impact shudder and upon noticing the nose of the 747 appearing concluded that it had struck their aircraft. Then the First Officer saw the damaged wing tip of the 747 and informed ATC about the possible impact. Later another aircraft, positioned behind the A321, confirmed the rudder damage. At the time of the collision, the two aircraft involved were on different ATC frequencies.

guid: https://skybrary.aero/accidents-and-incidents/b744-a321-london-heathrow-uk-2004 uri: https://skybrary.aero/accidents-and-incidents/b744-a321-london-heathrow-uk-2004 title: B744 / B763, Melbourne Australia, 2006 link: https://skybrary.aero/accidents-and-incidents/b744-b763-melbourne-australia-2006 description:

On 2 February 2006, a Boeing 747-400 was taxiing for a departure at Melbourne Airport. At the same time, a Boeing 767-300 was stationary on taxiway Echo and waiting in line to depart from runway 16. The left wing tip of the Boeing 747 collided with the right horizontal stabiliser of the Boeing 767 as the first aircraft passed behind. Both aircraft were on scheduled passenger services from Melbourne to Sydney. No one was injured during the incident.

guid: https://skybrary.aero/accidents-and-incidents/b744-b763-melbourne-australia-2006 uri: https://skybrary.aero/accidents-and-incidents/b744-b763-melbourne-australia-2006 title: DH8A, Ottawa Canada, 2003 link: https://skybrary.aero/accidents-and-incidents/dh8a-ottawa-canada-2003 description:

On 04 November 2003, the crew of a de Havilland DHC-8-100 which had been de/anti iced detected a pitch control restriction as rotation was attempted during take off from Ottawa and successfully rejected the take off from above V1. The Investigation concluded that the restriction was likely to have been the result of a remnant of clear ice migrating into the gap between one of the elevators and its shroud when the elevator was moved trailing edge up during control checks and observed that detection of such clear ice remnants on a critical surface wet with de-icing fluid was difficult.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-ottawa-canada-2003 uri: https://skybrary.aero/accidents-and-incidents/dh8a-ottawa-canada-2003 title: B463 / PA38 Birmingham UK, 1999 link: https://skybrary.aero/accidents-and-incidents/b463-pa38-birmingham-uk-1999 description:

On 28 April 1999, a BAe 146-300 departing Birmingham began its daylight take off from Runway 33 without ATC clearance just prior to the touchdown of a PA38 on the intersecting runway 06. Collision was very narrowly avoided after the Controller intervened and the BAe 146 rejected its take off, just missing the PA38 which had stopped just off the runway 33 centreline. The Investigation noted the 146 pilots belief that a take off clearance had been issued but also that no attempt appeared to have been made to read it back or confirm it with the First Officer.

guid: https://skybrary.aero/accidents-and-incidents/b463-pa38-birmingham-uk-1999 uri: https://skybrary.aero/accidents-and-incidents/b463-pa38-birmingham-uk-1999 title: B737 en-route, Glen Innes NSW Australia, 2007 link: https://skybrary.aero/accidents-and-incidents/b737-en-route-glen-innes-nsw-australia-2007 description:

On 17 November 2007 a Boeing 737-700 made an emergency descent after the air conditioning and pressurisation system failed in the climb out of Coolangatta at FL318 due to loss of all bleed air. A diversion to Brisbane followed. The Investigation found that the first bleed supply had failed at low speed on take off but that continued take off had been continued contrary to SOP. It was also found that the actions taken by the crew in response to the fault after completing the take off had also been also contrary to those prescribed.

guid: https://skybrary.aero/accidents-and-incidents/b737-en-route-glen-innes-nsw-australia-2007 uri: https://skybrary.aero/accidents-and-incidents/b737-en-route-glen-innes-nsw-australia-2007 title: Vehicle / B752, Dublin Ireland, 2009 link: https://skybrary.aero/accidents-and-incidents/vehicle-b752-dublin-ireland-2009 description:

On 29 May 2009, a Boeing 757-200 being operated by UK Airline Thomson Airways on a passenger charter flight from Sharm-el-Sheikh, Egypt to Dublin and having just landed on runway 10 at destination at night in poor visibility overtook a small ride-on grass mower moving along the right hand side of the runway in approximate line with the aircraft’s right hand wing tip. The driver of the mower was unaware of the arriving aircraft until he heard it on the runway behind him. Prior to the landing, ATC had been informed that all grass-cutting equipment previously working on and around the runway had cleared it.

guid: https://skybrary.aero/accidents-and-incidents/vehicle-b752-dublin-ireland-2009 uri: https://skybrary.aero/accidents-and-incidents/vehicle-b752-dublin-ireland-2009 title: B762, San Francisco CA USA, 2008 link: https://skybrary.aero/accidents-and-incidents/b762-san-francisco-ca-usa-2008 description:

On 28 June 2008 a Boeing 767-200 being operated as a Public Transport cargo flight by ABX Air (DHL) experienced a ground fire after loading had been completed and all doors closed and just before engine startup at night. The fire was located in the supernumerary compartment of the airplane. This compartment, which is present on some cargo airplanes, is located directly aft of the cockpit and forward of the main deck cargo compartment which is where the toilet, galley, and three non-flight crew seats are located (see diagram below).The flight crew evacuated the aircraft through the flight deck windows and were not injured, but the aircraft was substantially fire damaged and later classified as a hull loss.

guid: https://skybrary.aero/accidents-and-incidents/b762-san-francisco-ca-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/b762-san-francisco-ca-usa-2008 title: B772, Tokyo Narita Japan, 2008 link: https://skybrary.aero/accidents-and-incidents/b772-tokyo-narita-japan-2008 description:

On July 30 2008, a Boeing 777-200 being operated by Vietnam Airlines on a scheduled passenger flight landed at Narita in daylight and normal visibility and shortly afterwards experienced a right engine fire warning with the appropriate crew response following. Subsequently, after the aircraft had arrived at the parking stand and all passengers and crewmembers had left the aircraft, the right engine caught fire again and this fire was extinguished by the Airport RFFS who were already in attendance. There were no injuries and the aircraft sustained only minor damage.

guid: https://skybrary.aero/accidents-and-incidents/b772-tokyo-narita-japan-2008 uri: https://skybrary.aero/accidents-and-incidents/b772-tokyo-narita-japan-2008 title: GL5T, Fox Harbour NS Canada, 2007 link: https://skybrary.aero/accidents-and-incidents/gl5t-fox-harbour-ns-canada-2007 description:

On 11 November 2007, a Bombardier BD-700 (Global 5000) operated by Canadian charter company Jetport touched down short of the runway at destination Fox Harbour in normal daylight visibility and then directional control was lost and the aircraft exited the side of the runway ending up having rotated 120° clockwise about its fore-aft axis and came to rest approximately 300metres from the threshold and approximately 50 meters from the runway edge. As a result, the co pilot and one of the passengers suffered serious injuries and the other eight occupants suffered minor injuries. The aircraft sustained major structural damage.

guid: https://skybrary.aero/accidents-and-incidents/gl5t-fox-harbour-ns-canada-2007 uri: https://skybrary.aero/accidents-and-incidents/gl5t-fox-harbour-ns-canada-2007 title: A343 / B744, London Heathrow UK, 2007 link: https://skybrary.aero/accidents-and-incidents/a343-b744-london-heathrow-uk-2007 description:

On 15 October 2007, an Airbus 340-300 being operated on a scheduled passenger flight by Air Lanka with a heavy crew in the flight deck was taxiing towards the departure runway at London Heathrow at night in normal visibility when the right wing tip hit and sheared off the left hand winglet of a stationary British Airways Boeing 747-400 which was in a queue on an adjacent taxiway. The Airbus 340 sustained only minor damage to the right winglet and navigation light.

guid: https://skybrary.aero/accidents-and-incidents/a343-b744-london-heathrow-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/a343-b744-london-heathrow-uk-2007 title: A320, vicinity Melbourne Australia, 2007 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-melbourne-australia-2007 description:

On 21 July 2007, an Airbus A320-232 being operated by Australian Operator Jetstar Airways and on final approach to Melbourne after a passenger flight from Christchurch, New Zealand intended to make a go around after the required visual reference at Decision Altitude was not available, but the intended action was mis-managed such that safe control of the aircraft was temporarily lost. Recovery was achieved and there were no further abnormalities of flight during a second missed approach at Melbourne or the subsequent diversion to Avalon.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-melbourne-australia-2007 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-melbourne-australia-2007 title: PC12 / CRJ2, Charlotte NC USA, 2009 link: https://skybrary.aero/accidents-and-incidents/pc12-crj2-charlotte-nc-usa-2009 description:

On 29 May 2009, the flight crew of a PSA Airlines Bombardier CRJ 200 taking off from Charlotte in accordance with an ATC clearance in normal day visibility observed a small aircraft enter the runway ahead of them whilst at high speed on their full length take off roll but were able to make an emergency stop on the centreline just clear of the other aircraft, a privately operated Pilatus PC12, which had moved to the side of the runway when its pilot, who had received and acknowledged ATC clearance to enter the runway, realised the conflict.

guid: https://skybrary.aero/accidents-and-incidents/pc12-crj2-charlotte-nc-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/pc12-crj2-charlotte-nc-usa-2009 title: A343, Helsinki Finland, 2009 link: https://skybrary.aero/accidents-and-incidents/a343-helsinki-finland-2009 description:

On 22 June 2009, an Airbus A340-300 being operated by Finnair suffered a single tyre failure during take off on a scheduled passenger flight to Helsinki and malfunction assessed as consequential by the flight crew occurred to the hydraulic system. The flight proceeded to destination and carried out a daylight landing there in normal visibility without any further aircraft damage. Because of a further deterioration in the status of the aircraft hydraulic systems during the landing roll, the aircraft was stopped on the runway and then towed into the gate. No persons were injured in this incident.

guid: https://skybrary.aero/accidents-and-incidents/a343-helsinki-finland-2009 uri: https://skybrary.aero/accidents-and-incidents/a343-helsinki-finland-2009 title: A332, Montego Bay Jamaica, 2008 link: https://skybrary.aero/accidents-and-incidents/a332-montego-bay-jamaica-2008 description:

On 28 October 2008, an Airbus A330-200 could not be rotated for liftoff whist making a night takeoff from Montego Bay until the Captain had increased the reduced thrust set to TOGA, after which the aircraft became airborne prior to the end of the runway and climbed away normally. The Investigation found that the takeoff performance data used had been calculated for the flight by Company Despatch and the fact that it had been based on a takeoff weight which was 90 tonnes below the actual take off weight had not been noticed by any of the flight crew.

guid: https://skybrary.aero/accidents-and-incidents/a332-montego-bay-jamaica-2008 uri: https://skybrary.aero/accidents-and-incidents/a332-montego-bay-jamaica-2008 title: A321, Sandefjord Norway, 2006 link: https://skybrary.aero/accidents-and-incidents/a321-sandefjord-norway-2006 description:

A321 experienced minimal braking action during the daylight landing roll in wet snow conditions and normal visibility and an overrun occurred. The aircraft came to a stop positioned sideways in relation to the runway centreline with the right hand main landing gear 2 metres beyond the limit of the paved surface.

guid: https://skybrary.aero/accidents-and-incidents/a321-sandefjord-norway-2006 uri: https://skybrary.aero/accidents-and-incidents/a321-sandefjord-norway-2006 title: A320, vicinity Glasgow UK, 2008 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-glasgow-uk-2008 description:

An Airbus A322 being operated by British Airways on a scheduled passenger flight from London Heathrow to Glasgow was being radar vectored in day IMC towards an ILS approach to runway 23 at destination when an EGPWS Mode 2 Hard Warning was received and the prescribed response promptly initiated by the flight crew with a climb to MSA.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-glasgow-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-glasgow-uk-2008 title: DH8D, vicinity Edinburgh UK, 2008 link: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-edinburgh-uk-2008 description:

On 23 December 2008, a DHC8-400 being operated by Flybe on a scheduled passenger flight from Southampton to Edinburgh continued descent below its cleared altitude of 2100ft in day VMC prior to and then whilst tracking the ILS LLZ for Runway 23 at destination. It remained below the ILS GS until the ATC GND Controller, who had no formal responsibility for this phase of flight but was positioned alongside the TWR Controller, observed that aircraft had descended to within 800 ft of local terrain approximately 5 nm from the runway threshold. The flight crew appeared unaware of this when making a Finals call to TWR at 5.5 nm and so the Controller queried the descent. The aircraft was then levelled to achieve 600ft agl at 4nm from the threshold and an uneventful landing subsequently followed.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-edinburgh-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-edinburgh-uk-2008 title: SW4, New Plymouth New Zealand, 2009 link: https://skybrary.aero/accidents-and-incidents/sw4-new-plymouth-new-zealand-2009 description:

A visual approach by a Swearingen SA227 at New Plymouth was rushed and unstable with the distraction of a minor propeller speed malfunction and with un-actioned GPWS warnings caused by excessive sink and terrain closure rates. After a hard touchdown close to the beginning of the runway, directional control was lost and the aircraft left the runway to the side before continuing parallel to it for the rest of the landing roll.

guid: https://skybrary.aero/accidents-and-incidents/sw4-new-plymouth-new-zealand-2009 uri: https://skybrary.aero/accidents-and-incidents/sw4-new-plymouth-new-zealand-2009 title: E145, Kemi-Tornio Finland 2008 link: https://skybrary.aero/accidents-and-incidents/e145-kemi-tornio-finland-2008 description:

On 11 December 2008 an EMB 145 being operated by Finnish Commuter Airlines on a scheduled passenger flight caught fire during the taxi in after a night landing after the APU failed to start and a major electrical power failure occurred simultaneously. The fire was not detected until after the aircraft arrived on stand when, with the passengers still on board, a member of the ground crew saw signs of fire at the back of the aircraft. The aircraft s own fire suppression system was successfully used to extinguish the fire, the passengers left the aircraft and there were no injuries and only minor damage to the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/e145-kemi-tornio-finland-2008 uri: https://skybrary.aero/accidents-and-incidents/e145-kemi-tornio-finland-2008 title: E135, George South Africa, 2009 link: https://skybrary.aero/accidents-and-incidents/e135-george-south-africa-2009 description:

On 7 December 2009, an South African Airlink Embraer 135 overran the recently refurbished wet landing runway at George after braking was ineffective and exited the aerodrome perimeter to end up on a public road. There was no fire and all occupants were able to evacuate the aircraft. The subsequent investigation attributed the overrun principally to inadequate wet runway friction following the surface maintenance activities and noted various significant non-compliances with ICAO Annex 14.

guid: https://skybrary.aero/accidents-and-incidents/e135-george-south-africa-2009 uri: https://skybrary.aero/accidents-and-incidents/e135-george-south-africa-2009 title: F50, Isle of Man, 2009 link: https://skybrary.aero/accidents-and-incidents/f50-isle-man-2009 description:

On 15 January 2009 a VLM Fokker 50 left the side of the runway at the Isle of Man during the daylight landing roll. It was concluded that directional control had been lost on the wet runway because the crew had attempted rudder steering whilst also applying reverse pitch, an action which was contrary to SOPSs.

guid: https://skybrary.aero/accidents-and-incidents/f50-isle-man-2009 uri: https://skybrary.aero/accidents-and-incidents/f50-isle-man-2009 title: A320, Hamburg Germany, 2008 link: https://skybrary.aero/accidents-and-incidents/a320-hamburg-germany-2008 description:

On 1 March 2008 an Airbus A320 being operated by Lufthansa on a scheduled passenger flight from Munich to Hamburg experienced high and variable wind velocity on short finals in good daylight visibility and during the attempt at landing on runway 23 with a strong crosswind component from the right, a bounced contact of the left main landing gear with the runway was followed by a left wing down attitude which resulted in the left wing tip touching the ground. A rejected landing was then flown and after radar vectoring, a second approach to runway 33 was made to a successful landing. No aircraft occupants were injured but the aircraft left wing tip was found to have been damaged by the runway contact. The track of the aircraft and spot wind velocities given by ATC at key points are shown on the illustration below.

guid: https://skybrary.aero/accidents-and-incidents/a320-hamburg-germany-2008 uri: https://skybrary.aero/accidents-and-incidents/a320-hamburg-germany-2008 title: MD82, vicinity Lambert St Louis MO USA, 2007 link: https://skybrary.aero/accidents-and-incidents/md82-vicinity-lambert-st-louis-mo-usa-2007 description:

On September 28, 2007 the left engine of a McDonnell Douglas MD82 caught fire during the departure climb from Lambert St. Louis and an air turn back was initiated. When the landing gear failed to fully extend, a go around was made to allow time for an emergency gear extension to be accomplished after which a successful landing and emergency evacuation from the fire-damaged aircraft followed. The Investigation concluded that the engine fire was directly consequential on an unapproved maintenance practice and that the fire was prolonged by flight crew interruption of an emergency checklist to perform non-essential tasks.

guid: https://skybrary.aero/accidents-and-incidents/md82-vicinity-lambert-st-louis-mo-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/md82-vicinity-lambert-st-louis-mo-usa-2007 title: LJ60, Columbia SC USA, 2008 link: https://skybrary.aero/accidents-and-incidents/lj60-columbia-sc-usa-2008 description:

On September 19 2008, a Learjet 60 departing Columbia SC USA on a non scheduled passenger overran after attempting a rejected take off from above V1 and then hit obstructions which led to its destruction by fire and the death or serious injury of all six occupants. The subsequent investigation found that the tyre failure which led to the rejected take off decision had been due to under inflation and had damaged a sensor which caused the thrust reversers to return to their stowed position after deployment with the unintended forward thrust contributing to the severity of the overrun.

guid: https://skybrary.aero/accidents-and-incidents/lj60-columbia-sc-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/lj60-columbia-sc-usa-2008 title: B733, Burbank CA USA, 2000 link: https://skybrary.aero/accidents-and-incidents/b733-burbank-ca-usa-2000 description:

On 5 March 2000, a Boeing 737-300 being operated by Southwest Airlines on a scheduled passenger flight from Las Vegas to Burbank overran the landing destination runway in normal day visibility after a steep visual approach had been flown at an abnormally high speed. The aircraft exited the airport perimeter and came to a stop on a city street near a gas station. An emergency evacuation of the 142 occupants led to 2 serious injuries and 42 minor injuries and the aircraft was extensively damaged.

guid: https://skybrary.aero/accidents-and-incidents/b733-burbank-ca-usa-2000 uri: https://skybrary.aero/accidents-and-incidents/b733-burbank-ca-usa-2000 title: B733, Nottingham East Midlands, UK 2006 link: https://skybrary.aero/accidents-and-incidents/b733-nottingham-east-midlands-uk-2006 description:

On 15 June 2006 a TNT Belgium-operated Boeing 737-300 on diversion to East Midlands because of poor destination weather made an unintended ground contact 90 metres to one side of the intended landing runway whilst attempting to initiate a go around after a mis-flown daylight Cat 3A ILS approach. The RH MLG assembly broke off before the aircraft left the ground again and climbed away after which it was then flown to nearby Birmingham for a successful emergency landing. The subsequent investigation attributed the poor aircraft management which led to the accident to pilot distraction.

guid: https://skybrary.aero/accidents-and-incidents/b733-nottingham-east-midlands-uk-2006 uri: https://skybrary.aero/accidents-and-incidents/b733-nottingham-east-midlands-uk-2006 title: B734, Yogyakarta Indonesia, 2007 link: https://skybrary.aero/accidents-and-incidents/b734-yogyakarta-indonesia-2007 description:

On 7 March 2007, a Boeing 737-400 being operated by Garuda landed on a scheduled passenger flight from Jakarta to Yogyakarta overran the end of the destination runway at speed in normal daylight visibility after a late and high speed landing attempt ending up 252 metres beyond the end of the runway surface in a rice paddy field. There was a severe and prolonged fire which destroyed the aircraft (see the illustration below taken from the Investigation Report) and 21 of the 140 occupants were killed, 12 seriously injured, 100 suffered minor injuries and 7 were uninjured.

guid: https://skybrary.aero/accidents-and-incidents/b734-yogyakarta-indonesia-2007 uri: https://skybrary.aero/accidents-and-incidents/b734-yogyakarta-indonesia-2007 title: B737, Chicago Midway USA, 2005 link: https://skybrary.aero/accidents-and-incidents/b737-chicago-midway-usa-2005 description:

On 8 December 2005, a delay in deploying the thrust reversers after a Boeing 737-700 touchdown at night on the slippery surface of the 1176 metre-long runway at Chicago Midway with a significant tailwind component led to it running off the end, subsequently departing the airport perimeter and hitting a car before coming to a stop. The Investigation concluded that pilots lack of familiarity with the autobrake system on the new 737 variant had distracted them from promptly deploying the reversers and that inadequate pilot training provision and the ATC failure to provide adequate braking action information had contributed.

guid: https://skybrary.aero/accidents-and-incidents/b737-chicago-midway-usa-2005 uri: https://skybrary.aero/accidents-and-incidents/b737-chicago-midway-usa-2005 title: B744, Bangkok Thailand, 1999 link: https://skybrary.aero/accidents-and-incidents/b744-bangkok-thailand-1999 description:

On 23 September 1999, a Boeing 747-400 being operated by Qantas on a scheduled passenger service from Sydney Australia to Bangkok overran Runway 21L during an attempted night landing in normal visibility and came to a halt substantially intact 320 metres beyond the runway end. There was no fire and a precautionary evacuation of the aircraft was not begun until 20 minutes after it came to rest. Only minor injuries were sustained by 38 of the 410 occupants, some during the initial runway excursion, others as a consequence of the evacuation. The aircraft remained substantially intact during the overrun although the nose landing gear and one main landing gear separated. The picture below, taken from the Official Accident Report, shows the aircraft in its final stopping position.

guid: https://skybrary.aero/accidents-and-incidents/b744-bangkok-thailand-1999 uri: https://skybrary.aero/accidents-and-incidents/b744-bangkok-thailand-1999 title: B744, Taipei Taiwan, 2000 link: https://skybrary.aero/accidents-and-incidents/b744-taipei-taiwan-2000 description:

On 31 October 2000, the crew of a Singapore Airlines Boeing 747-400 taxiing for a night departure at Taipei in reduced (but not 'low') visibility with an augmenting crew member present on the flight deck failed to follow their correctly-confirmed taxi instructions and commenced take off on a partially closed runway. The subsequent collision with construction equipment and resultant severe post crash fire destroyed the aircraft killing over half the 170 occupants and injured 71 others. All three flight crew survived.

guid: https://skybrary.aero/accidents-and-incidents/b744-taipei-taiwan-2000 uri: https://skybrary.aero/accidents-and-incidents/b744-taipei-taiwan-2000 title: B763, en-route, North West Thailand, 1991 link: https://skybrary.aero/accidents-and-incidents/b763-en-route-north-west-thailand-1991 description:

On 26 May 1991, a Lauda Air Boeing 767-300 experienced an un-commanded deployment of a thrust reverser climbing out of Bangkok which quickly led to a terminal loss of control and subsequent ground impact which destroyed the aircraft. The cause of the PW4000 thrust reverser fault was not established but it was noted that certification requirements included the ability to continue flight under any possible thrust reverser position and that there had been no pilot training requirement for, or awareness of, the essential response which would have required full aileron and rudder corrective action within 4 to 6 seconds.

guid: https://skybrary.aero/accidents-and-incidents/b763-en-route-north-west-thailand-1991 uri: https://skybrary.aero/accidents-and-incidents/b763-en-route-north-west-thailand-1991 title: B752, Puerto Plata Dominican Republic, 1998 link: https://skybrary.aero/accidents-and-incidents/b752-puerto-plata-dominican-republic-1998 description:

On 1 January 1998, a Boeing 757-200 being operated by Airtours International on a passenger charter flight from Bangor MA USA to Puerto Plata Dominican Republic struck the ground to the right of the intended landing runway shortly after the aircraft commander, flying manually as PF for a third approach, had initiated a late go around after failing to retain effective control of the aircraft. Despite sustaining substantial damage to the landing gear and airframe not appreciated by the flight crew, the aircraft was then successfully flown pressurised to the nominated diversion, Santo Domingo where an uneventful landing was accomplished. A fuel leak from the APU was observed once parked but the decision was taken to shut it down using the normal switch and not to expedite passenger disembarkation and no fire occurred. None of the occupants were injured during the landing attempt at Puerto Plata but the aircraft was found to have suffered extensive damage and had to be repaired before further flight by a team from the aircraft manufacturer.

guid: https://skybrary.aero/accidents-and-incidents/b752-puerto-plata-dominican-republic-1998 uri: https://skybrary.aero/accidents-and-incidents/b752-puerto-plata-dominican-republic-1998 title: MD11, Hong Kong China, 1999 link: https://skybrary.aero/accidents-and-incidents/md11-hong-kong-china-1999 description:

On 22 August 1999, a Boeing MD11 being operated by China Airlines on a scheduled passenger flight from Taipei to Hong Kong carried out a normal ILS approach to Runway 25 Left in a strong crosswind and some turbulence but the night landing on a wet runway surface in normal visibility was very hard after a high sink rate in the flare was not arrested. The right main landing gear collapsed, the right wing separated from the fuselage and the aircraft caught fire and became inverted and reversed ending up on the grass to the right of the runway. Rapid attendance by the RFFS facilitated the escape of most of the 315 occupants but there were 3 deaths and 50 serious injuries as well as 153 minor injuries. The aircraft was destroyed.

guid: https://skybrary.aero/accidents-and-incidents/md11-hong-kong-china-1999 uri: https://skybrary.aero/accidents-and-incidents/md11-hong-kong-china-1999 title: DH8D, en-route, South West Norway, 2004 link: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-west-norway-2004 description:

On 19 May 2004, a Bombardier DHC8-400 being operated on a scheduled passenger flight from Sandefjord to Bergen by Norwegian airline Wideroe was climbing through 13500 feet approximately 20nm west north west of Sandefjord in day VMC when there was a loud 'bang' from the left engine followed quickly by total power failure and a fire warning for that engine. The crew carried out the QRH drill, declared an emergency and made a return to Sandefjord. Although the left hand engine was shut down and both engine fire bottles had been discharged, the engine warning remained illuminated throughout the remainder of the flight. The aircraft was stopped on the runway after landing and a successful emergency evacuation of all 31 occupants was carried out with no injuries whilst the Airport Fire Service attended to the fire source.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-west-norway-2004 uri: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-west-norway-2004 title: A319, London Heathrow UK, 2007 link: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2007 description:

On 12 February 2007, an Airbus A319-100 being operated by British Airways on a scheduled passenger flight into London Heathrow made unintended contact in normal daylight visibility with the stationary airbridge at the arrival gate. This followed an emergency stop made after seeing hand signals from ground staff whilst following SEGS indications which appeared to suggest that there was a further 5 metres to run to the correct parking position. There was no damage to the aircraft, only minimal damage to the airbridge and there were no injuries to the aircraft occupants or any other person

guid: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2007 title: B737, Amsterdam Netherlands, 2003 link: https://skybrary.aero/accidents-and-incidents/b737-amsterdam-netherlands-2003 description:

n 22 December 2003, a Boeing 737-700 being operated by UK Operator Easyjet on a scheduled passenger flight from Amsterdam to London Gatwick was taxiing for departure at night in normal visibility and took a different route to that instructed by ATC. The alternative route was, unknown to the flight crew, covered with ice and as a consequence, an attempt to maintain directional control during a turn was unsuccessful and the aircraft left wing collided with a lamp-post. The collision seriously damaged the aircraft and the lamp post. One passenger sustained slight injuries because of the impact. The diagram below taken from the official investigation report shows the area where the collision occurred.

guid: https://skybrary.aero/accidents-and-incidents/b737-amsterdam-netherlands-2003 uri: https://skybrary.aero/accidents-and-incidents/b737-amsterdam-netherlands-2003 title: B738, Goteborg Sweden, 2003 link: https://skybrary.aero/accidents-and-incidents/b738-goteborg-sweden-2003 description:

On 7 December 2003, a Boeing 737-800 being operated by SAS on a passenger charter flight from Salzburg, Austria to Stockholm Arlanda with an intermediate stop at Goteborg made a high speed rejected take off during the departure from Goteborg because of an un-commanded premature rotation. There were no injuries to any occupants and no damage to the aircraft which taxied back to the gate.

guid: https://skybrary.aero/accidents-and-incidents/b738-goteborg-sweden-2003 uri: https://skybrary.aero/accidents-and-incidents/b738-goteborg-sweden-2003 title: B738, vicinity Skavsta Sweden, 2004 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-skavsta-sweden-2004 description:

On 2 July 2004, a Boeing 737-800 being operated by Irish operator Ryanair on a scheduled passenger flight from London Stansted to Skavsta Sweden, completed an extremely high speed and unstable approach in day VMC to destination during which relevant Operator SOPs were comprehensively ignored, EGPWS warnings were not actioned and AFM limits for trailing edge flap deployment were breached. Despite this, a landing at excessive speed was accommodated by just within the full length of the 2878 metre long dry runway.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-skavsta-sweden-2004 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-skavsta-sweden-2004 title: B742, Montreal Canada, 2000 link: https://skybrary.aero/accidents-and-incidents/b742-montreal-canada-2000 description:

On 23 July 2000, a Boeing 747-200 being operated by Royal Air Maroc on a scheduled passenger flight from New York to Montreal overran the temporarily restricted available landing runway length after the aircraft failed to decelerate sufficiently during a daylight landing with normal on-ground visibility. It struck barriers at the displaced runway end before stopping 215 metres further on. Shortly before it stopped, ATC observed flames coming out of the No. 2 engine and advised the flight crew and alerted the RFFS. However, no sustained fire developed and the aircraft was undamaged except for internal damage to the No 2 engine. No emergency evacuation was deemed necessary by the aircraft commander and there were no occupant or other injuries

guid: https://skybrary.aero/accidents-and-incidents/b742-montreal-canada-2000 uri: https://skybrary.aero/accidents-and-incidents/b742-montreal-canada-2000 title: B752, Newark NJ USA, 2006 link: https://skybrary.aero/accidents-and-incidents/b752-newark-nj-usa-2006 description:

On 28 October 2006, a Boeing 757-200 being flown by two experienced pilots but both with low hours on type was cleared to make a circling approach onto runway 29 at Newark in night VMC but lined up and landed without event on the parallel taxiway. They then did not report their error and ATC did not notice it after Airport Authority personnel who had observed it advised ATC accordingly, the pilots admitted their error.

guid: https://skybrary.aero/accidents-and-incidents/b752-newark-nj-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/b752-newark-nj-usa-2006 title: B763, Copenhagen Denmark, 1999 link: https://skybrary.aero/accidents-and-incidents/b763-copenhagen-denmark-1999 description:

On 24 August 1999, a Boeing 767-300 being operated by SAS on a scheduled passenger flight from Copenhagen to Tokyo was unable to get airborne from the take off roll on Runway 22R in normal daylight visibility and made a rejected take off from high speed. The aircraft was taxied clear of the runway and after a precautionary attendance of the RFFS because of overheated brakes, the passengers were disembarked and transported to the terminal. There was minor damage to the aircraft landing gear and rear fuselage.

guid: https://skybrary.aero/accidents-and-incidents/b763-copenhagen-denmark-1999 uri: https://skybrary.aero/accidents-and-incidents/b763-copenhagen-denmark-1999 title: D328, Isle of Man, 2005 link: https://skybrary.aero/accidents-and-incidents/d328-isle-man-2005 description:

On 28 November 2005, a Dornier 328 departing from Isle of Man was unable to rotate at the speed calculated as applicable but the crew were able to complete a successful rejected take off. The Investigation found that the crew had failed to use the increased take off speeds which were required for the aircraft type involved after the aircraft had been de/anti iced prior to departure.

guid: https://skybrary.aero/accidents-and-incidents/d328-isle-man-2005 uri: https://skybrary.aero/accidents-and-incidents/d328-isle-man-2005 title: MD81, Kiruna Sweden, 1997 link: https://skybrary.aero/accidents-and-incidents/md81-kiruna-sweden-1997 description:

A scheduled passenger flight from Stockholm Arlanda to Kiruna left the runway during the night landing at destination performed in a strong crosswind with normal visibility.

guid: https://skybrary.aero/accidents-and-incidents/md81-kiruna-sweden-1997 uri: https://skybrary.aero/accidents-and-incidents/md81-kiruna-sweden-1997 title: SF34 / E145, Stockholm Sweden, 2002 link: https://skybrary.aero/accidents-and-incidents/sf34-e145-stockholm-sweden-2002 description:

On 16 December 2002, a Saab 340 being operated by Swedish airline Skyways and arriving at Stockholm on a scheduled domestic passenger flight and an Embraer 145 being operated by Swiss on a scheduled passenger flight from Stockholm to Basel almost collided at the intersection between taxiways ‘Z’ and ‘A’ in normal night visibility. Upon seeing the Saab approaching on a conflicting track, the Embraer 145 was stopped very suddenly and the other aircraft passed within an estimated 3 metres. No persons were injured and neither aircraft was damaged. The diagram below taken from the official report shows the intersection involved.

guid: https://skybrary.aero/accidents-and-incidents/sf34-e145-stockholm-sweden-2002 uri: https://skybrary.aero/accidents-and-incidents/sf34-e145-stockholm-sweden-2002 title: A320, Toronto Canada, 2000 link: https://skybrary.aero/accidents-and-incidents/a320-toronto-canada-2000 description:

On 13 September 2000, an Airbus A320-200 being operated by Canadian airline Skyservice on a domestic passenger charter flight from Toronto to Edmonton was departing in day VMC when, after a “loud bang and shudder” during rotation, evidence of left engine malfunction occurred during initial climb and the flight crew declared an emergency and returned for an immediate overweight landing on the departure runway which necessitated navigation around several pieces of debris, later confirmed as the fan cowlings of the left engine. There were no injuries to the occupants.

guid: https://skybrary.aero/accidents-and-incidents/a320-toronto-canada-2000 uri: https://skybrary.aero/accidents-and-incidents/a320-toronto-canada-2000 title: A321, Daegu South Korea, 2006 link: https://skybrary.aero/accidents-and-incidents/a321-daegu-south-korea-2006 description:

On 21 February 2006, an Airbus A321-200 being operated by China Eastern on a scheduled passenger flight from Daegu to Shanghai Pudong failed to follow the marked taxiway centreline when taxiing for departure in normal daylight visibility and a wing tip impacted an adjacent building causing minor damage to both building and aircraft. None of the 166 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/a321-daegu-south-korea-2006 uri: https://skybrary.aero/accidents-and-incidents/a321-daegu-south-korea-2006 title: B722, Cotonou Benin, 2003 link: https://skybrary.aero/accidents-and-incidents/b722-cotonou-benin-2003 description:

On 25 December 2003, a Boeing 727-200 being operated by UTA (Guinea) on a scheduled passenger flight from Cotonou to Beirut with a planned stopover at Kufra, Libya, failed to get properly airborne in day VMC from the 2400 metre departure runway and hit a small building 2.45 metres high situated on the extended centreline 118 metres beyond the end of the runway. The right main landing gear broke off and ripped off a part of the trailing edge flaps on the right wing. The airplane then banked slightly to the right and crashed onto the beach where it broke into several pieces and ended up in the sea where the depth of water varied between three and ten metres. Of the estimated 163 occupants, 141 were killed and the remainder seriously injured.

guid: https://skybrary.aero/accidents-and-incidents/b722-cotonou-benin-2003 uri: https://skybrary.aero/accidents-and-incidents/b722-cotonou-benin-2003 title: B732, London Gatwick UK, 1993 link: https://skybrary.aero/accidents-and-incidents/b732-london-gatwick-uk-1993 description:

On 20 October 1993, a Boeing 737-200 being operated by Air Malta on a scheduled passenger flight from Malta to London Gatwick landed at destination on the taxiway parallel to the runway for which landing clearance had been given in good visibility at night after a Surveillance Radar Approach (SRA) terminating at 2 miles from touchdown had been conducted in VMC. There was no damage to the aircraft or injury to the occupants and the aircraft taxied to the allocated gate after the landing.

guid: https://skybrary.aero/accidents-and-incidents/b732-london-gatwick-uk-1993 uri: https://skybrary.aero/accidents-and-incidents/b732-london-gatwick-uk-1993 title: B738, Rotterdam Netherlands, 2003 link: https://skybrary.aero/accidents-and-incidents/b738-rotterdam-netherlands-2003 description:

On 12 January 2003, a Boeing 737-800 being operated by Dutch airline Transavia on a passenger charter flight initially going from Rotterdam to Maastrict-Aachen was obliged to reject its take off on Runway 24 at Rotterdam after it pitched nose-up just after take-off thrust had been selected. The pitch up movement only stopped when the aft fuselage and the tailskid assembly contacted the runway and only when the flight crew rejected the take-off did the aircraft nose gear regain ground contact. The aircraft was damaged and unfit for flight but able to taxi back to the terminal to allow the uninjured passengers to disembark.

guid: https://skybrary.aero/accidents-and-incidents/b738-rotterdam-netherlands-2003 uri: https://skybrary.aero/accidents-and-incidents/b738-rotterdam-netherlands-2003 title: B738, Sydney Australia, 2007 link: https://skybrary.aero/accidents-and-incidents/b738-sydney-australia-2007 description:

On 14 July 2007, a Boeing 737-800 being operated by New Zealand airline Polynesian Blue on a scheduled passenger service from Sydney to Christchurch New Zealand commenced take off on Runway 16R with asymmetric thrust set and veered off the side of the runway reaching the intersecting runway 07 before rejected take off action initiated by the flight crew took effect and the aircraft came to a stop.

guid: https://skybrary.aero/accidents-and-incidents/b738-sydney-australia-2007 uri: https://skybrary.aero/accidents-and-incidents/b738-sydney-australia-2007 title: ATP, Jersey Channel Islands, 1998 link: https://skybrary.aero/accidents-and-incidents/atp-jersey-channel-islands-1998 description:

On 9 May 1998, a British Regional Airlines ATP was being pushed back for departure at Jersey in daylight whilst the engines were being started when an excessive engine power setting applied by the flight crew led to the failure of the towbar connection and then to one of the aircraft's carbon fibre propellers striking the tug. A non standard emergency evacuation followed. All aircraft occupants and ground crew were uninjured.

guid: https://skybrary.aero/accidents-and-incidents/atp-jersey-channel-islands-1998 uri: https://skybrary.aero/accidents-and-incidents/atp-jersey-channel-islands-1998 title: BE9L, Zurich Switzerland, 2007 link: https://skybrary.aero/accidents-and-incidents/be9l-zurich-switzerland-2007 description:

On 27 September 2007, a Beech 90 King Air being operated single pilot by a small UK air taxi operator on a day cargo flight from Southend UK to Zurich left the runway after unintentionally touching down at destination without the landing gear extended following an approach in day VMC. The pilot, the only occupant, was uninjured but the aircraft was declared a hull loss because of substantial damage.

guid: https://skybrary.aero/accidents-and-incidents/be9l-zurich-switzerland-2007 uri: https://skybrary.aero/accidents-and-incidents/be9l-zurich-switzerland-2007 title: CRJ2, Providence RI USA, 2007 link: https://skybrary.aero/accidents-and-incidents/crj2-providence-ri-usa-2007 description:

On 16 December 2007, a Bombardier CRJ-200 being operated by Air Wisconsin on a scheduled passenger flight from Philadelphia, PA to Providence RI made an ILS approach to Runway 05 at destination in IMC which became unstable but was continued to an extremely hard night touchdown which broke the left hand main landing gear and was followed by exit of the aircraft from the left hand side of the runway and a slide through a snow-covered grassy area before it came to a stop without impacting any obstructions. There were no injuries to the occupants, who left the aircraft using the integral air stairs at the main door but the aircraft suffered substantial damage.

guid: https://skybrary.aero/accidents-and-incidents/crj2-providence-ri-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/crj2-providence-ri-usa-2007 title: MD11, New York JFK USA, 2003 link: https://skybrary.aero/accidents-and-incidents/md11-new-york-jfk-usa-2003 description:

A McDonnell Douglas MD11F failed to complete its touchdown on runway 04R at New York JFK until half way along the 2560 metre-long landing runway and then overran the paved surface by 73 metres having been stopped by the installed EMAS. The Investigation found no evidence that the aircraft was not serviceable and noted that the and that the landing had been attempted made with a tailwind component which meant that the runway was the minimum necessary for the prevailing aircraft landing weight.

guid: https://skybrary.aero/accidents-and-incidents/md11-new-york-jfk-usa-2003 uri: https://skybrary.aero/accidents-and-incidents/md11-new-york-jfk-usa-2003 title: SF34, New York JFK USA, 1999 link: https://skybrary.aero/accidents-and-incidents/sf34-new-york-jfk-usa-1999 description:

An SF34 overan New York JFK 04R after an unstabilised ILS approach in IMC was continued to a deep landing at excessive speed and the aircraft overan into the installed EMAS.

guid: https://skybrary.aero/accidents-and-incidents/sf34-new-york-jfk-usa-1999 uri: https://skybrary.aero/accidents-and-incidents/sf34-new-york-jfk-usa-1999 title: A320, vicinity New York JFK NY USA, 2007 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-new-york-jfk-ny-usa-2007 description:

On 10 February 2007, smoke was observed coming from an overhead locker on an Airbus A320 which had just departed from New York JFK. It was successfully dealt by cabin crew fire extinguisher use whilst an emergency was declared and a precautionary air turn back made with the aircraft back on the ground six minutes later. The subsequent investigation attributed the fire to a short circuit of unexplained origin in one of a number of spare lithium batteries contained in a passenger's camera case, some packaged an some loose which had led to three of then sustaining fire damage.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-new-york-jfk-ny-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-new-york-jfk-ny-usa-2007 title: B738, en-route, Colorado Springs CO USA, 2006 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-colorado-springs-co-usa-2006 description:

B738 diversion into KCOS following in-flight fire. The fire started after a passenger's air purifier device caught fire whilst in use during the flight. The user received minor burns and the aircraft cabin sustained minor damage.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-colorado-springs-co-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-colorado-springs-co-usa-2006 title: F27, vicinity Jersey Channel Islands, 2001 link: https://skybrary.aero/accidents-and-incidents/f27-vicinity-jersey-channel-islands-2001 description:

Shortly after take-off from Jersey Airport, Channel Islands, a F27 experienced an uncontained engine failure and a major fire external to the engine nacelle. The fire was extinguished and the aircraft landed uneventfully back at Jersey.

guid: https://skybrary.aero/accidents-and-incidents/f27-vicinity-jersey-channel-islands-2001 uri: https://skybrary.aero/accidents-and-incidents/f27-vicinity-jersey-channel-islands-2001 title: WW24, vicinity John Wayne Airport Santa Ana CA USA, 1993 link: https://skybrary.aero/accidents-and-incidents/ww24-vicinity-john-wayne-airport-santa-ana-ca-usa-1993 description:

On 15 December 1993, the crew of an IAI Westwind on a domestic passenger charter flight failed to leave sufficient separation between their aircraft and the Boeing 757 ahead on finals in night VMC and lost control or their aircraft which crashed killing all occupants and destroying the aircraft in the impact and post-crash fire.

guid: https://skybrary.aero/accidents-and-incidents/ww24-vicinity-john-wayne-airport-santa-ana-ca-usa-1993 uri: https://skybrary.aero/accidents-and-incidents/ww24-vicinity-john-wayne-airport-santa-ana-ca-usa-1993 title: E145, Hannover Germany, 2005 link: https://skybrary.aero/accidents-and-incidents/e145-hannover-germany-2005 description:

On 14 August 2005, a British Regional Airlines Embraer 145 overran Runway 27L at Hannover by 160 metes after flying a stable approach in daylight but then making a soft and late touchdown on a water covered runway. Dynamic aquaplaning began and this was followed by reverted rubber aquaplaning towards the end of the paved surface when the emergency brake was applied. The aircraft suffered only minor damage and only one of the 49 occupants was slightly injured.

guid: https://skybrary.aero/accidents-and-incidents/e145-hannover-germany-2005 uri: https://skybrary.aero/accidents-and-incidents/e145-hannover-germany-2005 title: E170, Frankfurt Germany, 2005 link: https://skybrary.aero/accidents-and-incidents/e170-frankfurt-germany-2005 description:

On 1 March 2005, an Embraer ERJ 170 inbound to Frankfurt was intentionally flown below the ILS Glideslope in good night visibility by the First Officer after disconnection of the Autopilot at approximately 340 feet agl in order to achieve an early turn off after touchdown as a means to catch up some of the delay to the flight. The result was impact with the approach lighting and touchdown before the beginning of the runway. Significant damage to the aircraft was found once it had reached the designated parking gate.

guid: https://skybrary.aero/accidents-and-incidents/e170-frankfurt-germany-2005 uri: https://skybrary.aero/accidents-and-incidents/e170-frankfurt-germany-2005 title: LJ25, Northolt London UK,1996 link: https://skybrary.aero/accidents-and-incidents/lj25-northolt-london-uk1996 description:

On 13 August 1996, a Bombardier Learjet 25B being operated by a Spanish Air Taxi Operator on a private charter flight from Palma de Mallorca Spain to Northolt made a high speed overrun of the end of the landing runway after an approach in day VMC and collided with traffic on a busy main road after exiting the airport perimeter. All three occupants - the two pilots and one passenger - suffered minor injuries as did the driver of a vehicle hit by the aircraft. The aircraft was destroyed by impact forces but there was no fire.

guid: https://skybrary.aero/accidents-and-incidents/lj25-northolt-london-uk1996 uri: https://skybrary.aero/accidents-and-incidents/lj25-northolt-london-uk1996 title: C550, Southampton UK, 1993 link: https://skybrary.aero/accidents-and-incidents/c550-southampton-uk-1993 description:

On 26 May 1993, a Cessna Citation II being operated by a UK Air Taxi Company on a positioning flight from Oxford to Southampton to collect passengers with just the flight crew on board overran the very wet landing runway at the destination in normal daylight visibility and ended up on an adjacent motorway where it collided with traffic, caught fire and was destroyed. The aircraft occupants and three people in cars received minor injuries.

guid: https://skybrary.aero/accidents-and-incidents/c550-southampton-uk-1993 uri: https://skybrary.aero/accidents-and-incidents/c550-southampton-uk-1993 title: MD83, vicinity Paris Orly France, 1997 link: https://skybrary.aero/accidents-and-incidents/md83-vicinity-paris-orly-france-1997 description:

On 23 November 1997, a McDonald Douglas MD 83 being operated by AOM French Airlines on a scheduled passenger flight from Marseille to Paris Orly made an unintended premature descent almost to terrain impact at 4nm from the destination runway in day IMC before a go around was commenced. A subsequent approach was uneventful and a normal landing ensued. There was no damage to the aircraft or injury to the occupants.

guid: https://skybrary.aero/accidents-and-incidents/md83-vicinity-paris-orly-france-1997 uri: https://skybrary.aero/accidents-and-incidents/md83-vicinity-paris-orly-france-1997 title: SF34, Kirkwall Orkney UK, 2003 link: https://skybrary.aero/accidents-and-incidents/sf34-kirkwall-orkney-uk-2003 description:

On 12 September 2003, a Saab 340B being operated by UK regional airline Loganair on a scheduled passenger flight from Aberdeen to Kirkwall experienced a loss of pitch control during landing at destination and the rear fuselage contacted the runway causing damage to the airframe. Once the aircraft had cleared the runway, some passengers and some of the hold baggage was removed before the aircraft was taxied to its parking position because of a suspicion that the aircraft might have been loaded contrary to the accepted load and trim sheet.

guid: https://skybrary.aero/accidents-and-incidents/sf34-kirkwall-orkney-uk-2003 uri: https://skybrary.aero/accidents-and-incidents/sf34-kirkwall-orkney-uk-2003 title: SF34, Lappeenranta Finland, 2008 link: https://skybrary.aero/accidents-and-incidents/sf34-lappeenranta-finland-2008 description:

On 31 January 2008 a Saab 340B being operated by Czech airline Job Air on a scheduled passenger service from Helsinki to Lappeenranta under a wet lease contract for a Company called ‘Fly Lappeenranta’ which was not an aircraft operator. During the night landing at Lappeenranta, it departed the left side of the runway after touch down in normal visibility with snow falling. Propeller damage was caused when an attempt was then made to return the aircraft to the runway after the excursion. None of the 16 occupants was injured.

guid: https://skybrary.aero/accidents-and-incidents/sf34-lappeenranta-finland-2008 uri: https://skybrary.aero/accidents-and-incidents/sf34-lappeenranta-finland-2008 title: A319 / B744, en-route near Oroville WA USA, 2008 link: https://skybrary.aero/accidents-and-incidents/a319-b744-en-route-near-oroville-wa-usa-2008 description:

On 10 January 2008, an Air Canada Airbus A319 en route over the north western USA encountered unexpected sudden wake vortex turbulence from an in trail Boeing 747-400 nearly 11nm ahead to which the pilots who then responded with potentially hazardous flight control inputs which led to reversion to Alternate Control Law and aggravated the external /disturbance to the aircraft trajectory with roll up to 55° and an unintended descent of 1400 feet which with cabin service in progress and sea belt signs off led to cabin service carts hitting the cabin ceiling and several passenger injuries, some serious.

guid: https://skybrary.aero/accidents-and-incidents/a319-b744-en-route-near-oroville-wa-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/a319-b744-en-route-near-oroville-wa-usa-2008 title: A320 / B738, vicinity Launceston Australia, 2008 link: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-launceston-australia-2008 description:

On 1 May 2008 an Airbus A320-200 being operated by JetStar on a scheduled passenger flight from Melbourne to Launceston, Tasmania was making a missed approach from runway 32L when it came into close proximity in night VMC with a Boeing 737-800 being operated by Virgin Blue and also inbound to Launceston from Melbourne which was manoeuvring about 5nm north west of the airport after carrying out a similar missed approach. Minimum separation was 3 nm at the same altitude and the situation was fully resolved by the A320 climbing to 4000 feet.

guid: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-launceston-australia-2008 uri: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-launceston-australia-2008 title: A320, en-route, Kalmar County Sweden, 2009 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-kalmar-county-sweden-2009 description:

On 2 March 2009, communication difficulties and inadequate operator procedures led to an Airbus A320-200 being de-iced inappropriately prior to departure from Vasteras and fumes entered the air conditioning system via the APU. Although steps were then taken before departure in an attempt to clear the contamination, it returned once airborne. The flight crew decided to don their oxygen masks and complete the flight to Poznan. Similar fumes in the passenger cabin led to only temporary effects which were alleviated by the use of therapeutic oxygen. The Investigation concluded that no health risks arose from exposure to the fumes involved.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-kalmar-county-sweden-2009 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-kalmar-county-sweden-2009 title: A333, en-route, Kota Kinabalu Malaysia, 2009 link: https://skybrary.aero/accidents-and-incidents/a333-en-route-kota-kinabalu-malaysia-2009 description:

On 22 June 2009, an Airbus A330-300 being operated by Qantas on a scheduled passenger flight from Hong Kong to Perth encountered an area of severe convective turbulence in night IMC in the cruise at FL380 and 10 of the 209 occupants sustained minor injuries and the aircraft suffered minor internal damage. The injuries were confined to passengers and crew who were not seated at the time of the incident. After consultations with ground medical experts, the aircraft commander determined that the best course of action was to complete the flight as planned, and this was uneventful.

guid: https://skybrary.aero/accidents-and-incidents/a333-en-route-kota-kinabalu-malaysia-2009 uri: https://skybrary.aero/accidents-and-incidents/a333-en-route-kota-kinabalu-malaysia-2009 title: A346, London Heathrow UK, 2009 link: https://skybrary.aero/accidents-and-incidents/a346-london-heathrow-uk-2009 description:

On 12 December 2009, an Airbus A340-600 being operated by Virgin Atlantic Airways on a scheduled passenger flight departing from London Heathrow in night VMC was slow to rotate and the aircraft settled at an initial climb speed below VLS - defined as the lowest selectable speed which provides an appropriate margin above the stall speed. This prompted the PF to reduce the aircraft pitch attitude in order to accelerate which resulted in a poor rate of climb of between 500 and 600 fpm. The flaps were retracted on schedule and the aircraft continued its climb. At no time was full takeoff thrust selected. Later in the climb, the crew looked again at the take off data calculation and realised that they had made the departure with insufficient thrust set and using Vr and V2 speeds which were too low for the actual aircraft weight. The flight to the planned destination was completed.

guid: https://skybrary.aero/accidents-and-incidents/a346-london-heathrow-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/a346-london-heathrow-uk-2009 title: B462, Cape Town South Africa, 2009 link: https://skybrary.aero/accidents-and-incidents/b462-cape-town-south-africa-2009 description:

On 19 March 2009 a BAe 146-200 being operated by South African Airlink on a scheduled passenger flight from George to Cape Town in day VMC experienced a flameout of all four engines during the landing roll at Cape Town. The aircraft had enough momentum to roll forward on the runway and vacate onto a taxiway and the APU continued to provide electrical power to the hydraulic system, which facilitated braking and directional control. It was then towed from the taxiway to the apron and the passengers disembarked normally.

guid: https://skybrary.aero/accidents-and-incidents/b462-cape-town-south-africa-2009 uri: https://skybrary.aero/accidents-and-incidents/b462-cape-town-south-africa-2009 title: B744, Montreal Canada, 2008 link: https://skybrary.aero/accidents-and-incidents/b744-montreal-canada-2008 description:

During the landing roll in normal the aircraft veered to the right and stopped with the nose landing gear off the side of the runway.

guid: https://skybrary.aero/accidents-and-incidents/b744-montreal-canada-2008 uri: https://skybrary.aero/accidents-and-incidents/b744-montreal-canada-2008 title: B744, Johannesburg South Africa, 2009 link: https://skybrary.aero/accidents-and-incidents/b744-johannesburg-south-africa-2009 description:

On 11 May 2009, a British Airways Boeing 747-400 departing Johannesburg came close to stalling following a stall protection system activation during night rotation which continued until landing gear retraction despite immediate appropriate crew response. Subsequent investigation found that loss of lift on rotation had resulted from the unanticipated effect of a design modification in respect of thrust reverser unlocked signals with the aircraft in ground status. The Investigation found that the potential effects of this on the transition from ground to air status including the lower stalling angle of attack in ground effect had not been foreseen.

guid: https://skybrary.aero/accidents-and-incidents/b744-johannesburg-south-africa-2009 uri: https://skybrary.aero/accidents-and-incidents/b744-johannesburg-south-africa-2009 title: B744, Phoenix USA, 2009 link: https://skybrary.aero/accidents-and-incidents/b744-phoenix-usa-2009 description:

On 10 January 2009, a Boeing 747-400 being operated by British Airways on a scheduled passenger flight from Phoenix USA to London had been pushed back from the gate in normal daylight visibility and the engines start was continuing when fumes and smoke were observed in the cabin and flight deck. The aircraft commander decided to return to the stand but there was some delay while the tug was reconnected and the movement accomplished. The intensity of the fumes increased and as the aircraft came to a halt on the stand an emergency evacuation was ordered.

guid: https://skybrary.aero/accidents-and-incidents/b744-phoenix-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/b744-phoenix-usa-2009 title: BE20, vicinity North Caicos British West Indies, 2007 link: https://skybrary.aero/accidents-and-incidents/be20-vicinity-north-caicos-british-west-indies-2007 description:

On 6 February 2007, a Beech King Air 200 on a scheduled passenger flight crashed into water soon after making a dark night VMC take off and initial climb from North Caicos. The Investigation noted that the regulatory requirement for a crew of two pilots had been ignored and that the pilot had probably consumed alcohol within the permitted limits prior to the take off. It was concluded that he had probably lost spatial awareness and been in the process of attempting recovery to the originally intended flight path when impact occurred.

guid: https://skybrary.aero/accidents-and-incidents/be20-vicinity-north-caicos-british-west-indies-2007 uri: https://skybrary.aero/accidents-and-incidents/be20-vicinity-north-caicos-british-west-indies-2007 title: C500, vicinity Biggin Hill UK, 2008 link: https://skybrary.aero/accidents-and-incidents/c500-vicinity-biggin-hill-uk-2008 description:

On 30 March 2008, a privately operated Cessna Citation 500 which had just taken off from Biggin Hill UK for Pau, France in day VMC reported engine vibration . Whilst positioning for a return to land, the aircraft descended and the pilots reported a major power problem just before it struck the side of a house killing all five occupants and destroying the house and adjacent property in the intense fire which followed.

guid: https://skybrary.aero/accidents-and-incidents/c500-vicinity-biggin-hill-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/c500-vicinity-biggin-hill-uk-2008 title: A346, Toulouse France, 2007 link: https://skybrary.aero/accidents-and-incidents/a346-toulouse-france-2007 description:

During ground running of engines, the aircraft impacted a concrete wall at a ground speed of 30 kts following unintended movement and the aircraft was wrecked.

guid: https://skybrary.aero/accidents-and-incidents/a346-toulouse-france-2007 uri: https://skybrary.aero/accidents-and-incidents/a346-toulouse-france-2007 title: B735, Denver USA, 2008 link: https://skybrary.aero/accidents-and-incidents/b735-denver-usa-2008 description:

Runway Side Excursion During Attempted Take-off in Strong and Gusty Crosswind Conditions.

guid: https://skybrary.aero/accidents-and-incidents/b735-denver-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/b735-denver-usa-2008 title: DH8D, London Gatwick UK, 2009 link: https://skybrary.aero/accidents-and-incidents/dh8d-london-gatwick-uk-2009 description:

On 1 November 2009, a Bombardier DHC8-400 by Flybe, made a hard landing at London Gatwick due abnormal high pitch angle and significant structural damage to the aft lower airframe resulted.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-london-gatwick-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/dh8d-london-gatwick-uk-2009 title: DH8D, vicinity Southampton UK, 2009 link: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-southampton-uk-2009 description:

On 3 March 2009, a DHC8-Q400 being operated by UK Regional airline Flybe on a scheduled passenger flight from Edinburgh to Southampton was making its approach at the planned destination in night IMC and moderate turbulence when the aircraft was allowed to loose airspeed to below its minimum manoeuvring speed and a momentary stick shaker activation occurred. The associated automatic disconnection of the autopilot was followed by extreme pitch up and excessive roll left before the flight crew regained full control of the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-southampton-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-southampton-uk-2009 title: DH8C, vicinity Sydney Australia, 2008 link: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-sydney-australia-2008 description:

On 26 December 2008, a DHC8-300 being operated by Eastern Australia Airlines from Moree to Sydney made an auto ILS approach in which became de-stabilised and was continued as such until a stick shaker activation occurred.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-sydney-australia-2008 uri: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-sydney-australia-2008 title: E195, en-route, Irish Sea UK, 2008 link: https://skybrary.aero/accidents-and-incidents/e195-en-route-irish-sea-uk-2008 description:

On 1 August 2008, an en-route Embraer 195 despatched with one air conditioning pack inoperative lost all air conditioning and pressurisation when the other pack’s Air Cycle Machine (ACM) failed, releasing smoke and fumes into the aircraft. A MAYDAY diversion was made to the Isle of Man without further event. The Investigation found that the ACM failed due to rotor seizure caused by turbine blade root fatigue, the same failure which had led the other air conditioning system to fail failure four days earlier. It was understood that a modified ACM turbine housing was being developed to address the problem.

guid: https://skybrary.aero/accidents-and-incidents/e195-en-route-irish-sea-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/e195-en-route-irish-sea-uk-2008 title: E145 / DH8B, Cleveland USA, 2009 link: https://skybrary.aero/accidents-and-incidents/e145-dh8b-cleveland-usa-2009 description:

On 26 June 2009 a Bombardier DHC8-200 being operated by Commutair on a scheduled Continental Express passenger flight from Cleveland to Port Columbus was cleared for take off when an Embraer 145 being operated by Jetlink on another scheduled Continental Express passenger flight from Cleveland to Kansas City was about to cross the same runway in accordance with its ATC clearance in normal daylight visibility. The conflicting clearances were resolved by flight crew awareness and action rather than ATC intervention and once satisfied that the 145 was holding position clear of the runway, the DHC8 took off as already cleared.

guid: https://skybrary.aero/accidents-and-incidents/e145-dh8b-cleveland-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/e145-dh8b-cleveland-usa-2009 title: MD82 / A319, vicinity Helsinki Finland, 2007 link: https://skybrary.aero/accidents-and-incidents/md82-a319-vicinity-helsinki-finland-2007 description:

On 5 September 2007 in day VMC, an MD82 being operated by SAS was obliged to carry out an own-initiative avoiding action orbit in day VMC against an Airbus A319 being operated by Finnair on a scheduled passenger after conflict when about to join final approach. Both aircraft were following ATC instructions which, in the case of the MD 82, had not included maintaining own separation so that the applicable separation minima were significantly breached.

guid: https://skybrary.aero/accidents-and-incidents/md82-a319-vicinity-helsinki-finland-2007 uri: https://skybrary.aero/accidents-and-incidents/md82-a319-vicinity-helsinki-finland-2007 title: B772, St Kitts West Indies, 2009 link: https://skybrary.aero/accidents-and-incidents/b772-st-kitts-west-indies-2009 description:

On 26 September 2009, the crew of a British Airways Boeing 777-200 unintentionally began and completed their take off in good daylight visibility from the wrong intermediate runway position with less than the required take off distance available. Due to the abnormally low weight of the aircraft compared to almost all other departures by this fleet, the aircraft nevertheless became airborne just before the end if the runway. The investigation attributed the error to a poorly marked taxiway and the failure of the crew to include the expected taxi routing in their pre flight briefing.

guid: https://skybrary.aero/accidents-and-incidents/b772-st-kitts-west-indies-2009 uri: https://skybrary.aero/accidents-and-incidents/b772-st-kitts-west-indies-2009 title: C525 / B773, vicinity London City UK, 2009 link: https://skybrary.aero/accidents-and-incidents/c525-b773-vicinity-london-city-uk-2009 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/c525-b773-vicinity-london-city-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/c525-b773-vicinity-london-city-uk-2009 title: AT43, vicinity Pristina Kosovo, 1999 link: https://skybrary.aero/accidents-and-incidents/at43-vicinity-pristina-kosovo-1999 description:

On 12 November 1999, a French-registered ATR 42-300 being operated by Italian airline Si Fly on a passenger charter flight from Rome to Pristina was positioning for approach at destination in day IMC when it hit terrain and was destroyed, killing all 24 occupants. A post crash fire broke out near the fuel tanks after the impact.

guid: https://skybrary.aero/accidents-and-incidents/at43-vicinity-pristina-kosovo-1999 uri: https://skybrary.aero/accidents-and-incidents/at43-vicinity-pristina-kosovo-1999 title: AT72 / B732, vicinity Queenstown New Zealand, 1999 link: https://skybrary.aero/accidents-and-incidents/at72-b732-vicinity-queenstown-new-zealand-1999 description:

On 26 July 1999, an ATR 72-200 being operated by Mount Cook Airlines on a scheduled passenger flight from Christchurch to Queenstown entered the destination CTR without the required ATC clearance after earlier cancelling IFR and in marginal day VMC due to snow showers, separation was then lost against a Boeing 737-200 being operated IFR by Air New Zealand on a scheduled passenger flight from Auckland to Queenstown which was manoeuvring visually (circling) after making an offset VOR/DME approach in accordance with a valid ATC clearance.

guid: https://skybrary.aero/accidents-and-incidents/at72-b732-vicinity-queenstown-new-zealand-1999 uri: https://skybrary.aero/accidents-and-incidents/at72-b732-vicinity-queenstown-new-zealand-1999 title: B738, vicinity Cork Ireland, 2006 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-cork-ireland-2006 description:

On 4 June 2006, a Boeing 737-800 being operated by Ryanair on a passenger flight from London Stansted to Cork became too high to land off a day visual approach and requested a right hand orbit to reposition. This positioning was flown too close to terrain with TAWS alert triggered prior to a second approach to a successful landing.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-cork-ireland-2006 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-cork-ireland-2006 title: B744, Paris CDG France, 2003 link: https://skybrary.aero/accidents-and-incidents/b744-paris-cdg-france-2003 description:

On 18 January 2003, a Boeing 747-400F being operated by Singapore Airlines Cargo on a scheduled cargo flight from Paris CDG to Dubai taxied for departure in darkness and fog with visibility less than 100 metres in places and the right wing was in collision with a stationary and unoccupied ground de/anti icing vehicle without the awareness of either the flight crew or anybody else at the time. Significant damage occurred to the de icing vehicle and the aircraft was slightly damaged. The vehicle damage was not discovered until almost two hours later and the aircraft involved was not identified until it arrived in Dubai where the damage was observed and the authorities at Paris CDG advised.

guid: https://skybrary.aero/accidents-and-incidents/b744-paris-cdg-france-2003 uri: https://skybrary.aero/accidents-and-incidents/b744-paris-cdg-france-2003 title: B772, Manchester UK, 2005 link: https://skybrary.aero/accidents-and-incidents/b772-manchester-uk-2005 description:

On 1 March 2005, a Boeing 777-200 being operated by Pakistan International Airlines on a scheduled passenger flight from Lahore to Manchester experienced a landing gear fire during taxi in at destination after an apparently routine landing in normal day visibility. There were no flight deck indications of a significant fire but an emergency evacuation was recommended by attending Fire Crew and carried out. Thirty one of the 344 occupants sustained minor injuries during this evacuation and the rest were uninjured. Five firefighters also sustained minor injuries as they assisted passengers from the slides. Damage to the aircraft was minor.

guid: https://skybrary.aero/accidents-and-incidents/b772-manchester-uk-2005 uri: https://skybrary.aero/accidents-and-incidents/b772-manchester-uk-2005 title: GLEX, Luton UK, 2008 link: https://skybrary.aero/accidents-and-incidents/glex-luton-uk-2008 description:

On 29 January 2008, a Bombardier BD700 Global Express on a private passenger flight from Van Nuys, California to Luton experienced a single tyre failure when landing at destination in normal day visibility which caused significant secondary damage to the flight control system and localised structural damage to the wing. The aircraft was stopped on the runway and there were no injuries to the four occupants.

guid: https://skybrary.aero/accidents-and-incidents/glex-luton-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/glex-luton-uk-2008 title: RJ1H, Zurich Switzerland, 2006 link: https://skybrary.aero/accidents-and-incidents/rj1h-zurich-switzerland-2006 description:

On 26 January 2006, when fixed ground electrical power was connected to an Avro RJ100 which had just reached its destination parking gate at Zurich, a flash fire occurred which was visible in the flight deck and an emergency evacuation was ordered. As the air bridge was by this time attached to door 1L,the cabin crew deplaned the passengers that way and no slides were deployed. The Investigation concluded that the fire had been caused by contamination of the ground power connector with ramp de icing fluid and found that there has been similar previous events.

guid: https://skybrary.aero/accidents-and-incidents/rj1h-zurich-switzerland-2006 uri: https://skybrary.aero/accidents-and-incidents/rj1h-zurich-switzerland-2006 title: SB20, Stockholm Arlanda, 2001 link: https://skybrary.aero/accidents-and-incidents/sb20-stockholm-arlanda-2001 description:

On 18 December 2001, a Saab 2000 being operated by Air Botnia on scheduled passenger flight from Stockholm to Oulu was taxiing out at night in normal visibility in accordance with its ATC clearance when a car appeared from the left on a roadway and drove at speed on a collision course with the aircraft. In order to avoid a collision, the aircraft had to brake sharply and the aircraft commander saw the car pass under the nose of the aircraft and judged the vehicle’s closest distance to the aircraft to be four to five metres. The car did not stop, could not subsequently be identified and no report was made by the driver or other witnesses. The diagram below taken from the official report shows the site of the conflict - the aircraft was emerging from Ramp ‘G’ to turn left on taxiway ‘Z’ and the broken line shows the roadway which is crossed just before the left turn is commenced.

guid: https://skybrary.aero/accidents-and-incidents/sb20-stockholm-arlanda-2001 uri: https://skybrary.aero/accidents-and-incidents/sb20-stockholm-arlanda-2001 title: SW4, vicinity Aberdeen UK, 2002 link: https://skybrary.aero/accidents-and-incidents/sw4-vicinity-aberdeen-uk-2002 description:

On 24 December 2002, a SA 227 Metroliner III being operated by Danish freight and passenger charter operator Benair on a positioning flight from Aberdeen to Aalborg with just the two pilots on board crashed just after take off in marginal VMC at night following a loss of control. It collided with a car which caught fire and both aircraft and car were destroyed although only one person, one of the flight crew, sustained any injury, which was minor.

guid: https://skybrary.aero/accidents-and-incidents/sw4-vicinity-aberdeen-uk-2002 uri: https://skybrary.aero/accidents-and-incidents/sw4-vicinity-aberdeen-uk-2002 title: A30B, en-route, Bristol UK, 2000 link: https://skybrary.aero/accidents-and-incidents/a30b-en-route-bristol-uk-2000 description:

On 27 June 2000 an Airbus A300-600 being operated by American Airlines on a scheduled passenger service from London Heathrow to New York JFK was being flown manually in the day VMC climb and approaching FL220 when a loud bang was heard and there was a simultaneous abrupt disturbance to the flight path. The event appeared to the flight crew to have been a disturbance in yaw with no obvious concurrent lateral motion. Although following the disturbance, the aircraft appeared to behave normally, the aircraft commander decided to return to London Heathrow rather than commence a transatlantic flight following what was suspected to have been an un-commanded flight control input. An uneventful return was made followed by an overweight landing 50 minutes after take off.

guid: https://skybrary.aero/accidents-and-incidents/a30b-en-route-bristol-uk-2000 uri: https://skybrary.aero/accidents-and-incidents/a30b-en-route-bristol-uk-2000 title: A310, en-route, Florida Keys USA, 2005 link: https://skybrary.aero/accidents-and-incidents/a310-en-route-florida-keys-usa-2005 description:

On 6 March 2005, an Airbus A310-300 being operated by Canadian airline Air Transat on a passenger charter flight from Varadero Cuba to Quebec City was in the cruise in daylight VMC at FL350 seventeen minutes after departure and overhead the Florida Keys when the flight crew heard a loud bang and felt some vibration. The aircraft entered a Dutch roll which was eventually controlled in manual flight after a height excursion. During descent for a possible en route diversion, the intensity of the Dutch Roll lessened and then stopped and the crew decided to return to Varadero. It was found during landing there that rudder control inputs were not effective and after taxi in and shutdown at the designated parking position, it was discovered that the aircraft rudder was missing. One of the cabin crew sustained a minor back injury during the event but no others from the 271 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/a310-en-route-florida-keys-usa-2005 uri: https://skybrary.aero/accidents-and-incidents/a310-en-route-florida-keys-usa-2005 title: A321, Hakodate Japan, 2002 link: https://skybrary.aero/accidents-and-incidents/a321-hakodate-japan-2002 description:

On 21 January 2002, an Airbus A321-100 being operated by All Nippon Airways on a scheduled passenger flight from Nagoya to Hakodate encountered sudden negative windshear just prior to planned touchdown and the pitch up which followed resulted in the aft fuselage being damaged prior to the initiation of a climb away to position for a further approach which led to a normal landing. Three of the cabin crew sustained minor injuries but the remaining 90 occupants were uninjured.

guid: https://skybrary.aero/accidents-and-incidents/a321-hakodate-japan-2002 uri: https://skybrary.aero/accidents-and-incidents/a321-hakodate-japan-2002 title: A343 / B752, London Heathrow UK, 1995 link: https://skybrary.aero/accidents-and-incidents/a343-b752-london-heathrow-uk-1995 description:

On 23 November 1995, in normal daylight visibility, an Airbus A340-300 being operated by Gulf Air on a scheduled international passenger flight from London Heathrow taxied past a Boeing 757-200 being operated by British Airways on a scheduled domestic passenger flight and also departing from London Heathrow which had stopped on a diverging taxiway within the departure holding area for Runway 27R such that the wing tip of the Airbus impacted the tail fin of other aircraft. Two of the 378 occupants of the two aircraft suffered minor injuries and both aircraft were damaged. Passengers were deplaned uneventfully from both aircraft.

guid: https://skybrary.aero/accidents-and-incidents/a343-b752-london-heathrow-uk-1995 uri: https://skybrary.aero/accidents-and-incidents/a343-b752-london-heathrow-uk-1995 title: AT43, Bergen Norway, 2005 link: https://skybrary.aero/accidents-and-incidents/at43-bergen-norway-2005 description:

On 31 January 2005, an ATR 42-300 being operated by Danish Air Transport on a scheduled passenger flight from Bergen to Florø in day VMC encountered pitch control difficulties during rotation and subsequent climb and after declaring an emergency made a successful return to land on the departure runway seven minutes later. None of the 25 occupants were injured and the only damage found was to the elevator and its leading edge fairings.

guid: https://skybrary.aero/accidents-and-incidents/at43-bergen-norway-2005 uri: https://skybrary.aero/accidents-and-incidents/at43-bergen-norway-2005 title: B74S, Stockholm Arlanda Sweden, 1996 link: https://skybrary.aero/accidents-and-incidents/b74s-stockholm-arlanda-sweden-1996 description:

On 14 June 1996, a Boeing 747SP being operated by Air China on a scheduled passenger flight from Beijing to Stockholm was arriving on the designated parking gate at destination in normal daylight visibility when it collided with the airbridge. None of the 130 occupants of the aircraft suffered any injury but the aircraft was substantially damaged and the airbridge was damaged .

guid: https://skybrary.aero/accidents-and-incidents/b74s-stockholm-arlanda-sweden-1996 uri: https://skybrary.aero/accidents-and-incidents/b74s-stockholm-arlanda-sweden-1996 title: B742, Stockholm Arlanda Sweden, 2007 link: https://skybrary.aero/accidents-and-incidents/b742-stockholm-arlanda-sweden-2007 description:

On 25 June 2007, a Boeing 747-200F being operated by Cathay Pacific on a scheduled cargo flight from Stockholm to Dubai had completed push back for departure in normal daylight visibility and the parking brakes had been set. The tow vehicle crew had disconnected the tow bar but before they and their vehicle had cleared the vicinity of the aircraft, it began to taxi and collided with the vehicle. The flight crew were unaware of this and continued taxiing for about 150 metres until the flight engineer noticed that the indications from one if the engines were abnormal and the aircraft was taxied back to the gate. The tow vehicle crew and the dispatcher had been able to run clear and were not injured physically injured although all three were identified as suffering minor injury (shock). The aircraft was substantially damaged and the tow vehicle was damaged .

guid: https://skybrary.aero/accidents-and-incidents/b742-stockholm-arlanda-sweden-2007 uri: https://skybrary.aero/accidents-and-incidents/b742-stockholm-arlanda-sweden-2007 title: B712, en-route, Union Star MO USA, 2005 link: https://skybrary.aero/accidents-and-incidents/b712-en-route-union-star-mo-usa-2005 description:

On 12 May 2005, a Boeing 717 crew climbed in night IMC without selecting the appropriate anti-icing systems on and as a result lost control. The non-standard crew response led to an eight minute period of pitch excursions which occurred over a 13,000 feet height band at recorded ground speeds between 290 and 552 knots prior to eventual recovery and included a split in control columns some two minutes into the upset. The Investigation concluded that the aircraft had been fully serviceable with all deviations from normal flight initiated or exacerbated by the control inputs of the flight crew.

guid: https://skybrary.aero/accidents-and-incidents/b712-en-route-union-star-mo-usa-2005 uri: https://skybrary.aero/accidents-and-incidents/b712-en-route-union-star-mo-usa-2005 title: B74S, Stockholm Arlanda Sweden, 2006 link: https://skybrary.aero/accidents-and-incidents/b74s-stockholm-arlanda-sweden-2006 description:

On 11 December 2006, a Boeing 747SP being operated by Syrian Air on a scheduled passenger flight from Damascus to Stockholm was arriving on the designated parking gate at destination in normal visibility at night when it collided with the airbridge. None of the 116 occupants of the aircraft suffered any injury but the aircraft was substantially damaged and the airbridge was damaged .

guid: https://skybrary.aero/accidents-and-incidents/b74s-stockholm-arlanda-sweden-2006 uri: https://skybrary.aero/accidents-and-incidents/b74s-stockholm-arlanda-sweden-2006 title: B762, Los Angeles USA, 2006 link: https://skybrary.aero/accidents-and-incidents/b762-los-angeles-usa-2006 description:

On June 2, 2006, an American Airlines Boeing 767-200ER fitted GE CF6-80A engines experienced an uncontained failure of the high pressure turbine (HPT) stage 1 disc in the No. 1 engine during a high-power ground run carried out in designated run up area at Los Angeles for maintenance purposes during daylight normal visibility conditions. The three maintenance personnel on board the aircraft as well as two observers on the ground were not injured but both engines and the aircraft sustained substantial damage from the fuel-fed fire which occurred as an indirect result of the failure.

guid: https://skybrary.aero/accidents-and-incidents/b762-los-angeles-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/b762-los-angeles-usa-2006 title: B763, en-route, near Ovalle Chile, 2005 link: https://skybrary.aero/accidents-and-incidents/b763-en-route-near-ovalle-chile-2005 description:

On 2 January 2005, a Boeing 767-300 being operated by Air Canada on a scheduled passenger flight in day VMC from Toronto to Santiago, Chile was approximately 180 nm north of the intended destination and in the cruise at FL370 when it suffered a run down of the left engine which flight deck indications suggested was due to fuel starvation. A MAYDAY was declared to ATC and during the subsequent drift down descent, with the cross feed valve open, the failed engine was successfully restarted and the flight was completed with both engines operating without further incident.

guid: https://skybrary.aero/accidents-and-incidents/b763-en-route-near-ovalle-chile-2005 uri: https://skybrary.aero/accidents-and-incidents/b763-en-route-near-ovalle-chile-2005 title: CRJ1, Southampton UK, 2007 link: https://skybrary.aero/accidents-and-incidents/crj1-southampton-uk-2007 description:

On 17 January 2007, a Bombardier CRJ 100 being operated by French airline Brit Air on a scheduled night passenger flight from Paris CDG to Southampton could not be directionally controlled after touchdown on a dry surface in normal visibility and almost calm winds and departed the side of the runway during the landing roll. There were no injuries to any of the 36 occupants and there was no damage to the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/crj1-southampton-uk-2007 uri: https://skybrary.aero/accidents-and-incidents/crj1-southampton-uk-2007 title: CRJ2, Traverse City MI USA, 2007 link: https://skybrary.aero/accidents-and-incidents/crj2-traverse-city-mi-usa-2007 description:

On 12 April 2007, a Bombardier CRJ-600 being operated by Pinnacle Airlines on a scheduled night passenger flight from Minneapolis-St. Paul to Traverse City overran the end of the slippery landing runway by 90 metres in normal visibility. There were no injuries to any of the 52 occupants but the aircraft sustained substantial, but repairable, damage, primarily at the forward lower fuselage.

guid: https://skybrary.aero/accidents-and-incidents/crj2-traverse-city-mi-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/crj2-traverse-city-mi-usa-2007 title: DC95 / C206, Toronto Canada, 2002 link: https://skybrary.aero/accidents-and-incidents/dc95-c206-toronto-canada-2002 description:

On 25 August 2002, a Douglas DC9-51 being operated by North West Airlines on a scheduled passenger flight from Toronto to Minneapolis had just taken off in day VMC when a Cessna 206 being operated on a passenger charter flight from Georgian Bay to Toronto unexpectedly carried out a missed approach from another runway. And despite last minute visual avoiding action came within close airborne proximity whilst still within the airport perimeter. There were no injuries to any of the 109 occupants of the DC9 or the 4 occupants of the Cessna.

guid: https://skybrary.aero/accidents-and-incidents/dc95-c206-toronto-canada-2002 uri: https://skybrary.aero/accidents-and-incidents/dc95-c206-toronto-canada-2002 title: F28, Saint John NB Canada, 2002 link: https://skybrary.aero/accidents-and-incidents/f28-saint-john-nb-canada-2002 description:

On 27 March 2002, a Fokker F28 being operated by Air Canada Regional Airlines (t/a Air Canada Jazz) on a scheduled night passenger flight from Toronto to Saint John, having made an uneventful procedural ILS approach to Runway 05 at destination, departed the slippery landing runway to the left shortly after touchdown in normal visibility conditions but regained it before coming to a stop. Aircraft damage was limited to minor cuts in the tyres of the right main and nose landing gear and damage to one runway edge light. There were no injuries to any of the occupants.

guid: https://skybrary.aero/accidents-and-incidents/f28-saint-john-nb-canada-2002 uri: https://skybrary.aero/accidents-and-incidents/f28-saint-john-nb-canada-2002 title: A319, en-route, east of Dublin Ireland, 2008 link: https://skybrary.aero/accidents-and-incidents/a319-en-route-east-dublin-ireland-2008 description:

On 27 May 2008 an Airbus A319-100 being operated by Germanwings on a scheduled passenger flight from Dublin to Cologne was 30nm east of Dublin and passing FL100 in the climb in unrecorded daylight flight conditions when the Purser advised the flight crew by intercom that “something was wrong”, that almost all the passengers had fallen asleep, and that at least one of the cabin crew seated nearby was “unresponsive”. Following a review of this information and a check of the ECAM pressurisation page which showed no warnings or failures, a decision was taken to don oxygen masks and the aircraft returned uneventfully to Dublin without any further adverse effects on the 125 occupants. A MAYDAY was declared during the diversion.

guid: https://skybrary.aero/accidents-and-incidents/a319-en-route-east-dublin-ireland-2008 uri: https://skybrary.aero/accidents-and-incidents/a319-en-route-east-dublin-ireland-2008 title: A319, London Heathrow UK, 2009 link: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2009 description:

On 15 March 2009, an Airbus A319-100 being operated by British Airways on a scheduled passenger flight from London Heathrow to Edinburgh experienced an electrical malfunction which blanked the EFIS displays following engine start with some electrical fumes but no smoke. The engines were shut down, a PAN was declared to ATC and the aircraft was towed back onto the gate where passengers disembarked normally via the airbridge.

guid: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2009 title: A343, Frankfurt Germany, 2008 link: https://skybrary.aero/accidents-and-incidents/a343-frankfurt-germany-2008 description:

On 21 August 2008, an Airbus A340-300 being operated by an undisclosed operator by a German-licensed flight crew on a scheduled passenger flight from Teheran to Frankfurt collided with a stationary bus with only the driver on board whilst approaching the allocated parking gate in normal daylight visibility. The No 4 engine impacted the bus roof as shown in the photograph below reproduced from the official report. None of the occupants of either the aircraft or the bus were injured.

guid: https://skybrary.aero/accidents-and-incidents/a343-frankfurt-germany-2008 uri: https://skybrary.aero/accidents-and-incidents/a343-frankfurt-germany-2008 title: AN26, Kassel Germany, 2007 link: https://skybrary.aero/accidents-and-incidents/an26-kassel-germany-2007 description:

On 4 October 2007, an Antonov An-26B cargo aircraft being operated for an unidentified Hungarian-registered carrier by a Ukrainian crew on an empty positioning flight from Stuttgart to Kassel overran the destination runway during a daylight landing in normal ground visibility. None of the six crew on board were injured. There was no damage to the aircraft but some damage to ground installations.

guid: https://skybrary.aero/accidents-and-incidents/an26-kassel-germany-2007 uri: https://skybrary.aero/accidents-and-incidents/an26-kassel-germany-2007 title: AS50 / PA32, en-route, Hudson River NJ USA, 2009 link: https://skybrary.aero/accidents-and-incidents/as50-pa32-en-route-hudson-river-nj-usa-2009 description:

On August 8, 2009 a privately operated PA32 and a Eurocopter AS350BA helicopter being operated by Liberty Helicopters on a public transport sightseeing flight collided in VMC over the Hudson River near Hoboken, New Jersey whilst both operating under VFR. The three occupants of the PA32, which was en route from Wings Field PA to Ocean City NJ, and the six occupants of the helicopter, which had just left the West 30th Street Heliport, were killed and both aircraft received substantially damaged.

guid: https://skybrary.aero/accidents-and-incidents/as50-pa32-en-route-hudson-river-nj-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/as50-pa32-en-route-hudson-river-nj-usa-2009 title: B738, en-route, southern Austria, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-southern-austria-2010 description:

On 9 May 2010, Boeing 737-800 being operated by Swedish operator Viking Airlines on a public transport charter flight from Sharm el Sheikh, Egypt to Manchester UK and which had earlier suffered a malfunction which affected the level of redundancy in the aircraft pressurisation system, experienced a failure of the single air conditioning pack in use when over southern Austria and an emergency descent and en route diversion to Vienna were made. There were no injuries to any of the 196 occupants.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-southern-austria-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-southern-austria-2010 title: B738, Limoges France, 2008 link: https://skybrary.aero/accidents-and-incidents/b738-limoges-france-2008 description:

On 21 March 2008, a Boeing 737-800 being operated by Ryanair on a scheduled passenger flight from Charleroi, Belgium to Limoges carried out a daylight approach at destination followed by a landing in normal ground visibility but during heavy rain and with a strong crosswind which ended with a 50 metre overrun into mud. None of the 181 occupants were injured but both engines were damaged by ingestion of debris.

guid: https://skybrary.aero/accidents-and-incidents/b738-limoges-france-2008 uri: https://skybrary.aero/accidents-and-incidents/b738-limoges-france-2008 title: B738, Prestwick UK, 2009 link: https://skybrary.aero/accidents-and-incidents/b738-prestwick-uk-2009 description:

On 23 December 2009, a Boeing 737-800 being operated by Irish airline Ryanair on a scheduled passenger flight from Dublin to Prestwick left the end of the destination runway in normal daylight visibility and the landing gear sunk into the adjacent wet grass after an attempt to brake on the icy surface prior to turning onto the designated exit taxiway was unsuccessful. The occupants left the aircraft via the forward airstairs onto the grass and then moved across to the paved surface of the taxiway and runway.

guid: https://skybrary.aero/accidents-and-incidents/b738-prestwick-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/b738-prestwick-uk-2009 title: DH8D, Chania Greece, 2010 link: https://skybrary.aero/accidents-and-incidents/dh8d-chania-greece-2010 description:

On 23 February 2010, a Bombardier DHC8-400 being operated by Flybe for Olympic Air on a scheduled passenger flight from Athens to Chania unintentionally made an approach at destination in day VMC towards a landing on a part of the runway which was closed and only corrected the profile shortly before touchdown to achieve an ultimately uneventful landing on the available part of the runway. None of the 55 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-chania-greece-2010 uri: https://skybrary.aero/accidents-and-incidents/dh8d-chania-greece-2010 title: E145, Nuremberg Germany, 2005 link: https://skybrary.aero/accidents-and-incidents/e145-nuremberg-germany-2005 description:

On 18 July 2005, an Embraer 145 being operated by Swiss Air Lines on a scheduled passenger flight from Zurich to Nuremberg left the 2700 metre runway during the landing roll at destination in normal daylight visibility by means of an intentional high speed attempt to turn to one side when it became apparent that the aircraft would not stop before the end of the runway. The aircraft departed the runway tail first during a ground loop of approximately 200 degrees to the left and eventually came to a stop 30 metres from the centreline with the main landing gear on the grass. None of the 19 occupants was injured and there was only slight damage to the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/e145-nuremberg-germany-2005 uri: https://skybrary.aero/accidents-and-incidents/e145-nuremberg-germany-2005 title: FA50, vicinity London City UK, 2010 link: https://skybrary.aero/accidents-and-incidents/fa50-vicinity-london-city-uk-2010 description:

On 21 January 2010, a Mystere Falcon 50 being operated by TAG Aviation on a positioning flight from Biggin Hill to London City in day VMC began a descent at a high rate below its cleared altitude of 2000 ft amsl because the aircraft commander believed, on the basis of external visual cues, that the aircraft was on a final approach track for Runway 27 at destination when in fact it was downwind for Runway 09. After an alert from ATC as the aircraft passed 900 ft agl at a rate of descent of approximately 2200 fpm, recovery to a normal landing on Runway 09 was achieved.

guid: https://skybrary.aero/accidents-and-incidents/fa50-vicinity-london-city-uk-2010 uri: https://skybrary.aero/accidents-and-incidents/fa50-vicinity-london-city-uk-2010 title: G115 / GLID, en-route Oxfordshire UK, 2009 link: https://skybrary.aero/accidents-and-incidents/g115-glid-en-route-oxfordshire-uk-2009 description:

On 14 June 2009, a Grob 115E Tutor being operated by the UK Royal Air Force (RAF) and based at RAF Benson was conducting aerobatics in uncontrolled airspace near Drayton, Oxfordshire in day VMC when it collided with a Standard Cirrus Glider on a cross country detail from Lasham. The glider was sufficiently damaged that it could no longer be controlled and the glider pilot parachuted to safety. The Tutor entered a spin or spiral manoeuvre which it exited in a steep dive from which it did not recover prior to a ground impact which killed both occupants.

guid: https://skybrary.aero/accidents-and-incidents/g115-glid-en-route-oxfordshire-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/g115-glid-en-route-oxfordshire-uk-2009 title: GLF4, vicinity Kerry Ireland, 2009 link: https://skybrary.aero/accidents-and-incidents/glf4-vicinity-kerry-ireland-2009 description:

On 13 July 2009, a Gulfstream IV being operated by Indian operator Asia Aviation on a private flight from Kerry to Luton with one passenger on board in day IMC suffered a left main windshield failure shortly after take off and elected to make a return to land. Having received an ATC clearance to do so, it then failed to follow it and began a steep descent approximately 6 nm to the south of the airport towards high ground. When ATC became aware of this, an urgent instruction to climb was given and eventually the return was completed.

guid: https://skybrary.aero/accidents-and-incidents/glf4-vicinity-kerry-ireland-2009 uri: https://skybrary.aero/accidents-and-incidents/glf4-vicinity-kerry-ireland-2009 title: DC10, en-route, Raymond PA USA, 2008 link: https://skybrary.aero/accidents-and-incidents/dc10-en-route-raymond-pa-usa-2008 description:

On 14 June 2008, a Boeing MD-10 being operated by Federal Express on a non-scheduled cargo flight from Memphis to New York JFK experienced a period of aerodynamic buffet during descent from FL320 to FL290 in an en route holding pattern near Raymond in day VMC. None of the three occupants were injured and the flight was completed without further event but a post flight inspection found that substantial damage had been caused to both elevators and to the right horizontal stabiliser.

guid: https://skybrary.aero/accidents-and-incidents/dc10-en-route-raymond-pa-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/dc10-en-route-raymond-pa-usa-2008 title: P28A / S76, Humberside UK 2009 link: https://skybrary.aero/accidents-and-incidents/p28a-s76-humberside-uk-2009 description:

On 26 September 2009, a Piper PA28-140 flown by an experienced pilot was about to touch down after a day VMC approach about a mile behind an S76 helicopter which was also categorised as 'Light' for Wake Vortex purposes rolled uncontrollably to the right in the flare and struck the ground inverted seriously injuring the pilot. The Investigation noted existing informal National Regulatory Authority guidance material already suggested that light aircraft pilots might treat 'Light' helicopters as one category higher when on approach and recommended that this advice be more widely promulgated.

guid: https://skybrary.aero/accidents-and-incidents/p28a-s76-humberside-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/p28a-s76-humberside-uk-2009 title: A388, en-route Batam Island Indonesia, 2010 link: https://skybrary.aero/accidents-and-incidents/a388-en-route-batam-island-indonesia-2010 description:

On 4 November 2010, a Qantas Airbus A380 climbing out of Singapore experienced a sudden and uncontained failure of one of its Rolls Royce Trent 900 engines which caused considerable collateral damage to the airframe and some of the aircraft systems. A PAN was declared and after appropriate crew responses including aircraft controllability checks, the aircraft returned to Singapore. The root cause of the failure was found to have been an undetected component manufacturing fault. The complex situation which resulted from the failure in flight was found to have exceeded the currently anticipated secondary damage from such an event.

guid: https://skybrary.aero/accidents-and-incidents/a388-en-route-batam-island-indonesia-2010 uri: https://skybrary.aero/accidents-and-incidents/a388-en-route-batam-island-indonesia-2010 title: B744, en-route NNW of Bangkok Thailand, 2008 link: https://skybrary.aero/accidents-and-incidents/b744-en-route-nnw-bangkok-thailand-2008 description:

On 7 January 2008, a Boeing 747-400 being operated by Qantas on a scheduled passenger flight from London Heathrow to Bangkok was descending through FL100 about 13.5 nm NNW of destination in day VMC when indications of progressive electrical systems failure began to be annunciated. As the aircraft neared the end of the radar downwind leg, only the AC4 bus bar was providing AC power and the aircraft main battery was indicating discharge. A manual approach to a normal landing was subsequently accomplished and the aircraft taxied to the designated gate where passenger disembarkation took place. None of the 365 occupants, who included two heavy crew members who were present in the flight deck throughout the incident, had sustained any injury and the aircraft was undamaged.

guid: https://skybrary.aero/accidents-and-incidents/b744-en-route-nnw-bangkok-thailand-2008 uri: https://skybrary.aero/accidents-and-incidents/b744-en-route-nnw-bangkok-thailand-2008 title: T154, vicinity Smolensk Russian Federation, 2010 link: https://skybrary.aero/accidents-and-incidents/t154-vicinity-smolensk-russian-federation-2010 description:

On 10 April 2010, a Polish Air Force Tupolev Tu-154M on a pre-arranged VIP flight into Smolensk Severny failed to adhere to landing minima during a non precision approach with thick fog reported and after ignoring a TAWS ‘PULL UP’ Warning in IMC continued descent off track and into the ground. All of the Contributory Factors to the pilot error cause found by the Investigation related to the operation of the aircraft in a range of respects including a failure by the crew to obtain adequate weather information for the intended destination prior to and during the flight.

guid: https://skybrary.aero/accidents-and-incidents/t154-vicinity-smolensk-russian-federation-2010 uri: https://skybrary.aero/accidents-and-incidents/t154-vicinity-smolensk-russian-federation-2010 title: B744, vicinity Dubai UAE, 2010 link: https://skybrary.aero/accidents-and-incidents/b744-vicinity-dubai-uae-2010 description:

On 3 September 2010, a UPS Boeing 747-400 freighter flight crew became aware of a main deck cargo fire 22 minutes after take off from Dubai. An emergency was declared and an air turn back commenced but a rapid build up of smoke on the flight deck made it increasingly difficult to see on the flight deck and to control the aircraft. An unsuccessful attempt to land at Dubai was followed by complete loss of flight control authority due to fire damage and terrain impact followed. The fire was attributed to auto-ignition of undeclared Dangerous Goods originally loaded in Hong Kong.

guid: https://skybrary.aero/accidents-and-incidents/b744-vicinity-dubai-uae-2010 uri: https://skybrary.aero/accidents-and-incidents/b744-vicinity-dubai-uae-2010 title: GLF4, Teterboro NJ USA, 2010 link: https://skybrary.aero/accidents-and-incidents/glf4-teterboro-nj-usa-2010 description:

On 1 October 2010, a Gulfstream G-IV being operated by General Aviation Flying Service as ‘Meridian Air Charter’ on a corporate flight from Toronto International to Teterboro made a deep landing on 1833m-long runway 06 at destination in normal day visibility and overran the end of the runway at a speed of 40 to 50 knots before coming to a stop 30m into a 122m long EMAS installation.

guid: https://skybrary.aero/accidents-and-incidents/glf4-teterboro-nj-usa-2010 uri: https://skybrary.aero/accidents-and-incidents/glf4-teterboro-nj-usa-2010 title: DH8D / B735, Exeter UK, 2009 link: https://skybrary.aero/accidents-and-incidents/dh8d-b735-exeter-uk-2009 description:

On 30 October 2009, a Bombardier DHC8-400 departing Exeter at night failed to stop as cleared at the runway 08 holding point and continued onto the runway on which a Boeing 737-500 had just touched down on in the opposite direction. The Investigation attributed the DHC8-400 crew error to distraction arising from failure to follows SOPs and poor monitoring of the Captain taxiing the aircraft by the First Officer. The failure of the DHC8 crew to immediately report the occurrence to Flybe, which had resulted in non-availability of relevant CVR data to the Investigation was also noted.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-b735-exeter-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/dh8d-b735-exeter-uk-2009 title: DHC6, vicinity Kokoda Papua New Guinea, 2009 link: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-kokoda-papua-new-guinea-2009 description:

On 11 August 2009, a De Havilland Canada DHC-6-300 being operated by Airlines PNG on a scheduled domestic passenger flight from Port Moresby to Kokoda impacted terrain in day IMC while transiting the Kokoda Gap, approximately 6nm south east of the intended destination. The aircraft was destroyed by impact forces and all 13 occupants were killed.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-kokoda-papua-new-guinea-2009 uri: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-kokoda-papua-new-guinea-2009 title: DHC6, vicinity Oksibil Indonesia, 2009 link: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-oksibil-indonesia-2009 description:

On 2 August 2009 a DHC-6 being operated by Merpati Nusantara Airlines on a scheduled domestic passenger flight from Sentani to Oksibil in West Papua in daylight and on a VFR Flight Plan was in collision with terrain 6nm from destination resulting in the destruction of the aircraft and the death of all 15 occupants.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-oksibil-indonesia-2009 uri: https://skybrary.aero/accidents-and-incidents/dhc6-vicinity-oksibil-indonesia-2009 title: E145, New York JFK USA, 2007 link: https://skybrary.aero/accidents-and-incidents/e145-new-york-jfk-usa-2007 description:

On 17 December 2007, an Embraer 145 being operated by Chautauqua Airlines on a Delta Connection passenger flight departing New York JFK runway 31L for an unrecorded destination carried out a high speed rejected take off in normal day visibility when the response to elevator control input at rotation was abnormal.

guid: https://skybrary.aero/accidents-and-incidents/e145-new-york-jfk-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/e145-new-york-jfk-usa-2007 title: G115 / G115, near Porthcawl South Wales UK, 2009 link: https://skybrary.aero/accidents-and-incidents/g115-g115-near-porthcawl-south-wales-uk-2009 description:

On 11 February 2009, the plots of two civil-registered Grob 115E Tutors being operated for the UK Royal Air Force (RAF) and both operating from RAF St Athan near Cardiff were conducting Air Experience Flights (AEF) for air cadet passengers whilst in the same uncontrolled airspace in day VMC and aware of the general presence of each other when they collided. The aircraft were destroyed and all occupants killed

guid: https://skybrary.aero/accidents-and-incidents/g115-g115-near-porthcawl-south-wales-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/g115-g115-near-porthcawl-south-wales-uk-2009 title: PC12 /A318, en-route north east of Toulouse France, 2010 link: https://skybrary.aero/accidents-and-incidents/pc12-a318-en-route-north-east-toulouse-france-2010 description:

On 2 June 2010, an A318 crew en route from over southern France as cleared at FL290 just managed to avoid collision with a Pilatus PC12 making a non revenue positioning flight on the same track and in the same direction after detection of slight and unexpected turbulence had prompted a visual scan ahead. Earlier, the PC12 pilot cleared at FL270 had observed a difference between his available two altimeters but after getting confirmation from ATC that the altimeter on the side which also had an invalid airspeed reading was correct had assumed that one was the correctly reading one.

guid: https://skybrary.aero/accidents-and-incidents/pc12-a318-en-route-north-east-toulouse-france-2010 uri: https://skybrary.aero/accidents-and-incidents/pc12-a318-en-route-north-east-toulouse-france-2010 title: S61, vicinity Bødo Norway, 2008 link: https://skybrary.aero/accidents-and-incidents/s61-vicinity-bodo-norway-2008 description:

On 24 February 2008, a Sikorsky S-61N being operated by British International Helicopters on a passenger flight from Værøy to Bødo attempted a visual approach at destination in day IMC and came close to unseen terrain before accepting an offer of assistance from ATC to achieve an ILS approach to runway 07 without further event. None of the 18 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/s61-vicinity-bodo-norway-2008 uri: https://skybrary.aero/accidents-and-incidents/s61-vicinity-bodo-norway-2008 title: A320, Varadero Cuba, 2010 link: https://skybrary.aero/accidents-and-incidents/a320-varadero-cuba-2010 description:

On 31 January 2010, an Airbus A320-200 being operated by the Canadian Airline Skyservice on a passenger flight from Toronto Canada to Varadero Cuba made a procedural night ILS approach to destination in heavy rain and, soon after touchdown on a flooded runway, drifted off the side and travelled parallel to it for a little over 500 metres before subsequently re-entering it at low speed. There were no injuries to the 186 occupants and the aircraft sustained only minor damage.

guid: https://skybrary.aero/accidents-and-incidents/a320-varadero-cuba-2010 uri: https://skybrary.aero/accidents-and-incidents/a320-varadero-cuba-2010 title: A332, Sydney Australia 2009 link: https://skybrary.aero/accidents-and-incidents/a332-sydney-australia-2009 description:

On 4 July 2009, an Airbus A332 being operated by Jetstar Airways on a scheduled passenger flight from Sydney to Melbourne carried a 750 kg ULD which had been expressly rejected by the aircraft commander during the loading operation without flight crew awareness. There was no reported effect on aircraft handling during the flight.

guid: https://skybrary.aero/accidents-and-incidents/a332-sydney-australia-2009 uri: https://skybrary.aero/accidents-and-incidents/a332-sydney-australia-2009 title: B738, Hobart Australia, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-hobart-australia-2010 description:

On 24 November 2010, a Boeing 737-800 being operated by Virgin Blue Airlines on a scheduled passenger flight from Melbourne, Victoria to Hobart, Tasmania marginally overran the destination runway after aquaplaning during the daylight landing roll in normal ground visibility.

guid: https://skybrary.aero/accidents-and-incidents/b738-hobart-australia-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-hobart-australia-2010 title: B744, Mumbai India, 2009 link: https://skybrary.aero/accidents-and-incidents/b744-mumbai-india-2009 description:

On 4 September 2009, a Boeing 744-400 being operated by Air India on a delayed scheduled passenger flight from Mumbai to Riyadh was awaiting take off in normal daylight when ATC advised that there was a fuel leak from the left side, that a fire had started and that the engines should be shut down. An emergency cabin evacuation was carried out using exits on the right hand side and there were 21 minor injuries to the 213 passengers with all 16 crew escaping without injury. The fire on the left hand side was quickly extinguished by the RFFS and aircraft damage was confined to that area.

guid: https://skybrary.aero/accidents-and-incidents/b744-mumbai-india-2009 uri: https://skybrary.aero/accidents-and-incidents/b744-mumbai-india-2009 title: B752, Las Vegas NV USA, 2008 link: https://skybrary.aero/accidents-and-incidents/b752-las-vegas-nv-usa-2008 description:

On 22 December 2008, a Boeing 757-200 on a scheduled passenger flight departing Las Vegas for New York JFK experienced sudden failure of the right engine as take off thrust was set and the aircraft was stopped on the runway for fire services inspection. Fire service personnel observed a hole in the bottom of the right engine nacelle and saw a glow inside so they discharged a fire bottle into the nacelle through the open pressure relief doors. In the absence of any contrary indications, this action was considered to have extinguished any fire and the aircraft was then taxied back to the gate on the remaining serviceable engine for passenger disembarkation. None of the 263 occupants were injured but the affected engine suffered significant damage.

guid: https://skybrary.aero/accidents-and-incidents/b752-las-vegas-nv-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/b752-las-vegas-nv-usa-2008 title: B752, Mumbai India, 2010 link: https://skybrary.aero/accidents-and-incidents/b752-mumbai-india-2010 description:

On 9 June 2010, a Boeing B757-200 being operated by Chennai-based Blue Dart Aviation on a scheduled cargo flight from Mumbai to Bangalore lined up and commenced a night take off in normal ground visibility aligned with the right hand runway edge lights of 45 metre wide runway 27. ATC were not advised of the error and corrective action and once airborne, the aircraft completed the intended flight without further event. A ground engineer at Bangalore then discovered damage to the right hand landing gear assembly including one of the brake units. After being alerted, the Mumbai Airport Authorities discovered a number of broken runway edge lights.

guid: https://skybrary.aero/accidents-and-incidents/b752-mumbai-india-2010 uri: https://skybrary.aero/accidents-and-incidents/b752-mumbai-india-2010 title: B763, en-route North Bay Canada, 2009 link: https://skybrary.aero/accidents-and-incidents/b763-en-route-north-bay-canada-2009 description:

On 19 June 2009 a Boeing 767-300 was level at FL330 in night IMC when the Captain s altimeter and air speed indicator readings suddenly increased, the latter by 44 knots. The altimeter increase triggered an overspeed warning and the Captain reduced thrust and commenced a climb. The resultant stall warning was followed by a recovery. The Investigation found that a circuitry fault had caused erroneous indications on only the Captain s instruments and that contrary to the applicable QRH procedure, no comparison with the First Officer s or Standby instruments had been made. A related Operator FCOM error was also identified.

guid: https://skybrary.aero/accidents-and-incidents/b763-en-route-north-bay-canada-2009 uri: https://skybrary.aero/accidents-and-incidents/b763-en-route-north-bay-canada-2009 title: B772, en-route Bozeman MT USA, 2008 link: https://skybrary.aero/accidents-and-incidents/b772-en-route-bozeman-mt-usa-2008 description:

On 26 November 2008, a Boeing 777-200 powered by RR RB211 Trent 800 series engines and being operated by Delta AL on a scheduled passenger flight from Shanghai Pudong to Atlanta was in the cruise at FL390 in day VMC in the vicinity of Bozeman MT when there was an uncommanded thrust reduction or rollback of the right engine.

guid: https://skybrary.aero/accidents-and-incidents/b772-en-route-bozeman-mt-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/b772-en-route-bozeman-mt-usa-2008 title: CL60, Almaty Kazakstan, 2007 link: https://skybrary.aero/accidents-and-incidents/cl60-almaty-kazakstan-2007 description:

On 26 December 2007, the crew of a Bombardier Challenger 604 which had received a 2-stage ground de/anti icing treatment lost roll control as the aircraft got airborne from a snow-covered runway at Almaty in freezing mist and light snow conditions and it crashed within the airport perimeter before continuing through the perimeter fence and catching fire. The Investigation concluded that the loss of control was probably caused by contamination of the wing leading edge with frozen deposits during the take off roll as a result of the crew's decision not to select wing anti-ice on contrary to applicable procedures.

guid: https://skybrary.aero/accidents-and-incidents/cl60-almaty-kazakstan-2007 uri: https://skybrary.aero/accidents-and-incidents/cl60-almaty-kazakstan-2007 title: B738, Mangalore India, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-mangalore-india-2010 description:

On 22 May 2010, an Air India Express Boeing 737-800 overran the landing runway at Mangalore when attempting a go around after thrust reverser deployment following a fast and late touchdown off an unstable approach. Almost all of the 166 occupants were killed when control was lost and the aircraft crashed into a ravine off the end of the runway. It was noted a relevant factor in respect of the approach, landing and failed go around attempt was probably the effect of sleep inertia on the Captain s performance and judgement after a prolonged sleep en-route

guid: https://skybrary.aero/accidents-and-incidents/b738-mangalore-india-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-mangalore-india-2010 title: DH8D, Bournemouth UK, 2010 link: https://skybrary.aero/accidents-and-incidents/dh8d-bournemouth-uk-2010 description:

On 30 November 2010, a Bombardier DHC8-400 being operated by Flybe on a scheduled passenger flight from an unrecorded origin to Southampton was unable to select any trailing edge flaps when preparing for the intended landing at destination. The night non precision approach in VMC was discontinued and a diversion was made to Bournemouth where a longer runway with an ILS procedure was available for the necessary flapless landing and during the subsequent touchdown, a tail strike occurred. None of the 73 occupants were injured and damage to the aircraft was minor.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-bournemouth-uk-2010 uri: https://skybrary.aero/accidents-and-incidents/dh8d-bournemouth-uk-2010 title: A321, en-route, Northern Sudan, 2010 link: https://skybrary.aero/accidents-and-incidents/a321-en-route-northern-sudan-2010 description:

On 24 August 2010, an Airbus A321-200 being operated by British Midland on a scheduled public transport service from Khartoum to Beirut experienced, during cruise at FL360 in night IMC, an electrical malfunction which was accompanied by intermittent loss of the display on both pilots’ EFIS and an uncommanded change to a left wing low attitude. De-selection of the No 1 generator and subsequent return of the rudder trim, which had not previously been intentionally moved, to neutral removed all abnormalities and the planned flight was completed without further event with no damage to the aircraft or injuries to the 49 occupants.

guid: https://skybrary.aero/accidents-and-incidents/a321-en-route-northern-sudan-2010 uri: https://skybrary.aero/accidents-and-incidents/a321-en-route-northern-sudan-2010 title: B738, Knock Ireland, 2009 link: https://skybrary.aero/accidents-and-incidents/b738-knock-ireland-2009 description:

On 19 October 2009, a Boeing 737-300 being operated by British Midland subsidiary bmibaby on a scheduled passenger flight from Knock (also more recently known as Ireland West ) to Manchester encountered a large flock of medium-sized birds during rotation for take off in normal day visibility and engine malfunction followed. Increasing engine vibration during the climb led to the decision to divert to Shannon, which was completed without further event. There were no injuries to the 133 occupants or anyone on the ground.

guid: https://skybrary.aero/accidents-and-incidents/b738-knock-ireland-2009 uri: https://skybrary.aero/accidents-and-incidents/b738-knock-ireland-2009 title: DH8A, en-route, near Bristol UK, 2010 link: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-near-bristol-uk-2010 description:

On 24 April 2010, a Bombardier DHC8-100 operated by Olympic Airways which had, some weeks earlier, been flown to the UK for heavy maintenance at Exeter was positioning from East Midlands to Exeter in day VMC with just the two flight crew on board when it experienced a significant oil loss from one engine en route and responded by shutting it down and declaring a PAN to ATC for radar vectors direct to destination. The remaining engine was then found to be losing oil, and the declared status was upgraded to a MAYDAY and a successful diversion to the nearest suitable airfield, Bristol, was made.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-near-bristol-uk-2010 uri: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-near-bristol-uk-2010 title: A346, Quito Ecuador, 2007 link: https://skybrary.aero/accidents-and-incidents/a346-quito-ecuador-2007 description:

On 31 August 2007 an Airbus A340-600 made a hard landing with drift /side slip present after a making a circling approach in good visibility with a relatively high cloudbase and was disabled on the runway after sustaining significant damage to the landing gear. It was found that the visual circling segment had been flown too close to the runway and the subsequent final approach had been unstabilised with touchdown being made at an excessive rate of descent. The destination risk assessment carried out by the airline involved was found to inadequate as was pilot training for the approach flown.

guid: https://skybrary.aero/accidents-and-incidents/a346-quito-ecuador-2007 uri: https://skybrary.aero/accidents-and-incidents/a346-quito-ecuador-2007 title: B752, Chicago O’Hare IL USA, 2008 link: https://skybrary.aero/accidents-and-incidents/b752-chicago-ohare-il-usa-2008 description:

On 22 September 2008, a Boeing 757-200 being operated by American Airlines on a scheduled passenger flight from Seattle/Tacoma WA to New York JFK lost significant electrical systems functionality en route. A diversion with an emergency declared was made to Chicago O Hare where after making a visual daylight approach, the aircraft was intentionally steered off the landing runway when the aircraft commander perceived that an overrun would occur. None of the 192 occupants were injured and there was only minor damage to the aircraft landing gear.

guid: https://skybrary.aero/accidents-and-incidents/b752-chicago-ohare-il-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/b752-chicago-ohare-il-usa-2008 title: B738/B738, Girona Spain, 2010 link: https://skybrary.aero/accidents-and-incidents/b738b738-girona-spain-2010 description:

On 14 January 2010, two Ryanair Boeing 737-800 aircraft were operating scheduled passenger flights from Girona to Las Palmas and Turin respectively and had taxied from adjacent gates at Girona in normal day visibility in quick succession. The Turin-bound aircraft taxied first but because it was early at the holding point for its CTOT, the other aircraft was designated first for take off and during the overtaking manoeuvre in the holding area, the wing tip of the moving Las Palmas aircraft hit the horizontal stabiliser of the Turin bound aircraft causing minor and substantial damage to the respective aircraft. None of the respective 81 and 77 occupants were injured and both aircraft taxied back to their gates.

guid: https://skybrary.aero/accidents-and-incidents/b738b738-girona-spain-2010 uri: https://skybrary.aero/accidents-and-incidents/b738b738-girona-spain-2010 title: CRJ2, Vigo Spain, 2010 link: https://skybrary.aero/accidents-and-incidents/crj2-vigo-spain-2010 description:

On 25 February 2010, a Bombardier CRJ200 being operated by Air Nostrum on a domestic passenger flight from Bilbao to Vigo carried out an ILS approach to runway 20 in day VMC which culminated in a non standard touchdown during which one wing touched the runway. The ground contact and consequential minor damage was not appreciated at the time and was found during a subsequent ground inspection. None of the 23 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/crj2-vigo-spain-2010 uri: https://skybrary.aero/accidents-and-incidents/crj2-vigo-spain-2010 title: B763, Atlanta GA, USA 2009 link: https://skybrary.aero/accidents-and-incidents/b763-atlanta-ga-usa-2009 description:

On 19 October 2009, a Boeing 767-300 being operated by Delta Airlines on a scheduled passenger flight from Rio de Janeiro to Atlanta inadvertently made a landing at destination in night VMC on parallel taxiway M instead of the intended and ATC-cleared landing runway 27R. None of the 194 occupants were injured and there was no damage to the aircraft or conflict with other traffic or vehicles. The third rostered crew member had become incapacitated en route with the consequence that neither of the other pilots had been able to take any in flight rest.

guid: https://skybrary.aero/accidents-and-incidents/b763-atlanta-ga-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/b763-atlanta-ga-usa-2009 title: B752, en-route, Central Mauritania, 2010 link: https://skybrary.aero/accidents-and-incidents/b752-en-route-central-mauritania-2010 description:

On 25 August 2010, a Boeing 757-200 being operated by UK airline Astraeus on a passenger flight from Freetown Sierra Leone to London Heathrow was in the cruise at night in IMC at FL370 when vibration levels on both engines increased. When the prescribed ice shedding drill was followed, one engine malfunctioned and vibration on the other remained abnormally high and so a MAYDAY was declared and a diversion to Nouakchott, Mauritania was made without further event. None of the 103 occupants were injured and there was no engine damage.

guid: https://skybrary.aero/accidents-and-incidents/b752-en-route-central-mauritania-2010 uri: https://skybrary.aero/accidents-and-incidents/b752-en-route-central-mauritania-2010 title: B733, vicinity Chambery France, 2010 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-chambery-france-2010 description:

On 7 February 2010, a Boeing 737-300 being operated by Jet2 on a scheduled passenger flight from Leeds/Bradford UK to Chambery France was making an ILS approach to runway 18 at destination in day IMC when a Mode 2 EGPWS Terrain, Pull Up Warning occurred. A climb was immediately initiated to VMC on top and a second ILS approach was then made uneventfully. Despite extreme pitch during the early stages of the pull up climb, none if the 109 occupants, all secured for landing, were injured.

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-chambery-france-2010 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-chambery-france-2010 title: A310, vicinity Quebec Canada, 2008 link: https://skybrary.aero/accidents-and-incidents/a310-vicinity-quebec-canada-2008 description:

On 5 March 2008, an Air Transat A310-300 was unintentionally mishandled by the flight crew during and shortly after departure from Quebec and effective control of the aircraft was temporarily lost. Whilst it was concluded that the origin of the initial difficulties in control were a result of confusion which began on the take off roll and led to a take off at excessive speed followed by subsequent mismanagement and overload, the inappropriate steep descent that followed was attributed to the effect of somatogravic illusion in respect of aircraft attitude control in conjunction with a singular focus on airspeed.

guid: https://skybrary.aero/accidents-and-incidents/a310-vicinity-quebec-canada-2008 uri: https://skybrary.aero/accidents-and-incidents/a310-vicinity-quebec-canada-2008 title: A318 / B738, en-route, Trasadingen Switzerland, 2009 link: https://skybrary.aero/accidents-and-incidents/a318-b738-en-route-trasadingen-switzerland-2009 description:

On 8 June 2009, an Airbus A318-100 being operated by Air France on a scheduled passenger flight from Belgrade, Serbia to Paris CDG in day VMC came into conflict with a Boeing 737-800 being operated by Ryanair on a scheduled passenger flight from Nottingham East Midlands UK to Bergamo Italy. The conflict was resolved mainly by TCAS RA response and there were no injuries to any occupants during the avoidance manoeuvres carried out by both aircraft.

guid: https://skybrary.aero/accidents-and-incidents/a318-b738-en-route-trasadingen-switzerland-2009 uri: https://skybrary.aero/accidents-and-incidents/a318-b738-en-route-trasadingen-switzerland-2009 title: A320, Oslo Norway, 2010 link: https://skybrary.aero/accidents-and-incidents/a320-oslo-norway-2010 description:

On 25 February 2010, an Aeroflot Airbus A320-200 unintentionally made a daylight take off from Oslo in good visibility from the taxiway parallel to the runway for which take off clearance had been given. Because of the available distance and the absence of obstructions, the take off was otherwise uneventful. The Investigation identified contributory factors attributable to the airline, the airport and the ANSP.

guid: https://skybrary.aero/accidents-and-incidents/a320-oslo-norway-2010 uri: https://skybrary.aero/accidents-and-incidents/a320-oslo-norway-2010 title: AT43, Lubbock TX USA, 2009 link: https://skybrary.aero/accidents-and-incidents/at43-lubbock-tx-usa-2009 description:

On 27 January 2009, an ATR 42-300 being operated by Empire Airlines on a scheduled cargo flight from Fort Worth Alliance to Lubbock was making a night ILS approach in IMC to runway 17R at destination when it stalled and crashed short of the runway. The aircraft caught fire and was in any case effectively already destroyed by the impact. Both crew members were injured, one seriously.

guid: https://skybrary.aero/accidents-and-incidents/at43-lubbock-tx-usa-2009 uri: https://skybrary.aero/accidents-and-incidents/at43-lubbock-tx-usa-2009 title: AT72, Mumbai India, 2009 link: https://skybrary.aero/accidents-and-incidents/at72-mumbai-india-2009 description:

On 10 November 2010, a Kingfisher Airlines ATR 72-200 made an excessively steep and unstabilised tailwind approach in light rain to runway 27 at Mumbai in visual daylight conditions. After touching down late, the aircraft was steered off the side of the runway when it became obvious that an overrun would otherwise occur. The Investigation found that ATC had failed to advise of water patches on the runway and aquaplaning had occurred. It also found that without aquaplaning, the available distance from the actual touchdown point would have been sufficient to stop the aircraft in.

guid: https://skybrary.aero/accidents-and-incidents/at72-mumbai-india-2009 uri: https://skybrary.aero/accidents-and-incidents/at72-mumbai-india-2009 title: B733, en-route, north of Antalya Turkey, 2009 link: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-antalya-turkey-2009 description:

On 2 May 2009, a Boeing 737-300 being operated by French airline Europe Airpost on a passenger charter flight from Marseille to Antalya, Turkey was descending in day VMC towards destination when a sudden and severe turbulence encounter led to a temporary loss of control and stall. Recovery was achieved and none of the 115 occupants was injured and the aircraft was undamaged.

guid: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-antalya-turkey-2009 uri: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-antalya-turkey-2009 title: B738, Eindhoven Netherlands, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-eindhoven-netherlands-2010 description:

On 4 June 2010, a Boeing 737-800 rejected take off from above V1 at Eindhoven when the First Officer, who was PF had the feeling that the aircraft was unsafe to fly after which the Captain selected the thrust reversers and the aircraft stopped 500m before the end of the 3000m runway. The Investigation found no evidence of an airworthiness fault or any relevant external atmospheric effects which would support the reported feeling . It was also noted that no prior call had preceded the reject and that any reject decision above 80 KIAS should be made by the aircraft commander.

guid: https://skybrary.aero/accidents-and-incidents/b738-eindhoven-netherlands-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-eindhoven-netherlands-2010 title: B738, en-route, Arabian Sea, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-arabian-sea-2010 description:

On 26 May 2010, a Boeing 737-800 being operated by Air India Express on a passenger flight from Dubai UAE to Pune, India was in the cruise at night at FL370 near PARAR when a sudden high speed descent occurred without ATC clearance during which nearly 7000 feet of altitude was lost in a little over 30 seconds before recovery was made. The remainder of the flight was uneventful. Despite the abnormal pitch, pitch change and g variation, none of the 113 occupants had been injured.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-arabian-sea-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-arabian-sea-2010 title: B738, Stuttgart Germany, 2005 link: https://skybrary.aero/accidents-and-incidents/b738-stuttgart-germany-2005 description:

On 23 April 2005, a Boeing 737-800 being operated by Turkish charter airline Sky Air on a passenger flight from Stuttgart to Dusseldorf tipped onto its tail when take off thrust was applied for the intended departure from Runway 25 in normal day visibility. The attempt to take off was immediately abandoned and the aircraft towed back to the gate for the 100 passengers to disembark. One of the cabin crew was slightly injured and the aircraft was severely damaged .

guid: https://skybrary.aero/accidents-and-incidents/b738-stuttgart-germany-2005 uri: https://skybrary.aero/accidents-and-incidents/b738-stuttgart-germany-2005 title: C501, Birmingham UK, 2010 link: https://skybrary.aero/accidents-and-incidents/c501-birmingham-uk-2010 description:

On 19 November 2010, a Cessna 501 being operated by The Frandley Aviation Partnership on a domestic cargo flight from Belfast Aldergrove to Birmingham continued descent on an initially visual day ILS approach to Runway 15 into IMC and until collision with the ILS GS aerial adjacent to the intended landing runway occurred. The aircraft caught fire and was destroyed. Both pilots were injured, one seriously.

guid: https://skybrary.aero/accidents-and-incidents/c501-birmingham-uk-2010 uri: https://skybrary.aero/accidents-and-incidents/c501-birmingham-uk-2010 title: F50, Groningen Netherlands, 2007 link: https://skybrary.aero/accidents-and-incidents/f50-groningen-netherlands-2007 description:

On 18 May 2007, a Fokker 50 being operated by Belgian airline VLM on a passenger flight from Amsterdam to Groningen landed long and at excessive speed after a visual day approach to runway 05 at destination and ran off the end of the runway onto grass. None of the 14 occupants were injured and the aircraft suffered only minor damage with two runway lights being damaged.

guid: https://skybrary.aero/accidents-and-incidents/f50-groningen-netherlands-2007 uri: https://skybrary.aero/accidents-and-incidents/f50-groningen-netherlands-2007 title: SB20, Werneuchen Germany, 2002 link: https://skybrary.aero/accidents-and-incidents/sb20-werneuchen-germany-2002 description:

On 10 July 2002, a Saab 2000 being operated by Swiss Air Lines on a scheduled public transport service from Basel to Hamburg encountered extensive thunderstorms affecting both the intended destination and the standard alternates and due to a shortage of fuel completed the flight with a landing in day VMC at an unmanned general aviation airstrip where the aircraft collided with an unseen obstruction. After the aircraft came to a stop with the landing gear torn off, the two cabin crew conducted the passenger evacuation on their own initiative. There was no fire and only one of the 20 occupants was injured. The aircraft was declared a hull loss due to the damage sustained relative to the location.

guid: https://skybrary.aero/accidents-and-incidents/sb20-werneuchen-germany-2002 uri: https://skybrary.aero/accidents-and-incidents/sb20-werneuchen-germany-2002 title: A310, Vienna Austria, 2000 link: https://skybrary.aero/accidents-and-incidents/a310-vienna-austria-2000 description:

On 12 July 2000, a Hapag Lloyd Airbus A310 was unable to retract the landing gear normally after take off from Chania for Hannover. The flight was continued towards the intended destination but the selection of an en route diversion due to higher fuel burn was misjudged and useable fuel was completely exhausted just prior to an intended landing at Vienna. The aeroplane sustained significant damage as it touched down unpowered inside the aerodrome perimeter but there were no injuries to the occupants and only minor injuries to a small number of them during the subsequent emergency evacuation.

guid: https://skybrary.aero/accidents-and-incidents/a310-vienna-austria-2000 uri: https://skybrary.aero/accidents-and-incidents/a310-vienna-austria-2000 title: B732, Medan Indonesia, 2005 link: https://skybrary.aero/accidents-and-incidents/b732-medan-indonesia-2005 description:

On 5 September 2005, a Boeing 737-200 being operated by Mandala Airlines on a scheduled domestic passenger flight from Medan, Indonesia to Jakarta failed to become properly airborne during the attempted take off from from runway 23 in day VMC and, after failing to remain airborne, overran the end of the runway at speed finally coming to a stop outside the airport perimeter. The aircraft was destroyed by impact forces and a subsequent fire and 100 of the 117 occupants were killed and 15 seriously injured. The aircraft collided with residential property, vehicles and various other obstructions and as a result a further 49 people on the ground were killed and a further 26 seriously injured.

guid: https://skybrary.aero/accidents-and-incidents/b732-medan-indonesia-2005 uri: https://skybrary.aero/accidents-and-incidents/b732-medan-indonesia-2005 title: MD83, Lanzarote Spain, 2007 link: https://skybrary.aero/accidents-and-incidents/md83-lanzarote-spain-2007 description:

On 5 June 2007, a McDonnell Douglas MD83 being flown by Austrian charter operator MAP on a flight from Lanzarote to Barcelona failed to follow a normal trajectory after take off in day VMC and developed violent roll oscillations. As speed increased, this stopped and a return to land was made without further event. Takeoff from Lanzarote had been unintentionally made without the flaps/slats being set to the required position.

guid: https://skybrary.aero/accidents-and-incidents/md83-lanzarote-spain-2007 uri: https://skybrary.aero/accidents-and-incidents/md83-lanzarote-spain-2007 title: B752, en-route, vicinity Chancay Peru, 1996 link: https://skybrary.aero/accidents-and-incidents/b752-en-route-vicinity-chancay-peru-1996 description:

On 2 October 1996, the crew of an Aero Peru Boeing 757 which had just made a night take off from Lima after maintenance found that all their altimeters, ASIs and VSIs were malfunctioning. A return was attempted but they did not respond to correctly functioning SPS or GPWS activations or use their RADALT indications and control was lost and sea impact followed. The instrument malfunctions were attributed to protective tape placed over the static ports which was not removed by maintenance before release to service or noticed by the crew during their pre flight checks.

guid: https://skybrary.aero/accidents-and-incidents/b752-en-route-vicinity-chancay-peru-1996 uri: https://skybrary.aero/accidents-and-incidents/b752-en-route-vicinity-chancay-peru-1996 title: CRJ2, en-route, east of Barcelona Spain, 2006 link: https://skybrary.aero/accidents-and-incidents/crj2-en-route-east-barcelona-spain-2006 description:

On 27 July 2006, a Bombardier CRJ200 being operated by Air Nostrum on a scheduled passenger flight from Barcelona to Basel, Switzerland in night VMC, suffered a sudden left hand engine failure and an associated engine fire when passing FL235 some 14 minutes after take off. An air turn back was made with indications of engine fire continuing until just three minutes before landing. An evacuation using the right hand exits was ordered by the Captain as soon as the aircraft had come to a stop and had been promptly actioned with the RFFS in attendance. There were no injuries to the 48 occupants during the evacuation and the only damage was to the affected engine.

guid: https://skybrary.aero/accidents-and-incidents/crj2-en-route-east-barcelona-spain-2006 uri: https://skybrary.aero/accidents-and-incidents/crj2-en-route-east-barcelona-spain-2006 title: B738, en-route, south west of Beirut Lebanon, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-west-beirut-lebanon-2010 description:

On 25 January 2010, a Boeing 737-800 being operated by Ethiopian Airlines on a scheduled passenger flight from Beirut to Addis Ababa in night IMC disappeared from ATC radar soon after departure from Runway 21 and was subsequently found to have impacted the sea in an unintentional out of control condition some five miles south west of the airport less than five minutes after getting airborne Impact resulted in the destruction of the aircraft and the death of all 90 occupants.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-west-beirut-lebanon-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-west-beirut-lebanon-2010 title: B712, en-route, Western Australia, 2006 link: https://skybrary.aero/accidents-and-incidents/b712-en-route-western-australia-2006 description:

On 28 February 2006, a Boeing 717-200 being operated by National Jet for Qantas Link on a domestic scheduled passenger flight from Paraburdoo to Perth, Western Australia in day IMC experienced an activation of the stall protection system just after the aircraft had levelled at a cruise altitude of FL340. The response of the flight crew was to initiate an immediate descent without either declaring an emergency or obtaining ATC clearance and, as a result, procedural separation against opposite direction traffic at FL320 was lost. The 72 occupants were uninjured and the aircraft was undamaged.

guid: https://skybrary.aero/accidents-and-incidents/b712-en-route-western-australia-2006 uri: https://skybrary.aero/accidents-and-incidents/b712-en-route-western-australia-2006 title: A321, Manchester UK, 2011 (1) link: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2011-1 description:

On 29 April 2011, an Airbus A321-200 being operated by Thomas Cook Airlines on a passenger service from Manchester UK to Iraklion, Greece took off in day VMC but failed to establish a climb at the expected speed until the aircraft pitch attitude was reduced below that prescribed for the aircraft weight which had been entered into the FMS. No abnormal manoeuvres occurred and none of the 231 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2011-1 uri: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2011-1 title: B734, Amsterdam Netherlands, 2010 (1) link: https://skybrary.aero/accidents-and-incidents/b734-amsterdam-netherlands-2010-1 description:

On 6 June 2010, a Boeing 737-400 being operated by Atlas Blue, a wholly owned subsidiary of Royal Air Maroc, on a passenger flight from Amsterdam to Nador, Morocco encountered a flock of geese just after becoming airborne from runway 18L in day VMC close to sunset and lost most of the thrust on the left engine following bird ingestion. A MAYDAY was declared and a minimal single engine climb out was followed by very low level visual manoeuvring not consistently in accordance with ATC radar headings before the aircraft landed back on runway 18R just over 9 minutes later.

guid: https://skybrary.aero/accidents-and-incidents/b734-amsterdam-netherlands-2010-1 uri: https://skybrary.aero/accidents-and-incidents/b734-amsterdam-netherlands-2010-1 title: AS32, en-route, near Peterhead Scotland UK, 2009 link: https://skybrary.aero/accidents-and-incidents/as32-en-route-near-peterhead-scotland-uk-2009 description:

On 1 April 2009, the flight crew of a Bond Helicopters Eurocopter AS332 L2 Super Puma en route from the Miller Offshore Platform to Aberdeen at an altitude of 2000 feet lost control of their helicopter when a sudden and catastrophic failure of the main rotor gearbox occurred and, within less than 20 seconds, the hub with the main rotor blades attached separated from the helicopter causing it to fall into the sea at a high vertical speed The impact destroyed the helicopter and all 16 occupants were killed. Seventeen Safety Recommendations were made as a result of the investigation.

guid: https://skybrary.aero/accidents-and-incidents/as32-en-route-near-peterhead-scotland-uk-2009 uri: https://skybrary.aero/accidents-and-incidents/as32-en-route-near-peterhead-scotland-uk-2009 title: AT72, Dresden Germany, 2002 link: https://skybrary.aero/accidents-and-incidents/at72-dresden-germany-2002 description:

On 5 March 2002, an ATR72-202 departed from runway 22 at Dresden in good visibility at night aligned with the edge lights of the runway without the crew apparently being aware of their error. Damage to both the edge lights and the aircraft was subsequently discovered. The Investigation attributed the error to the crew, concluding that a contributing factor had been that the correctly promulgated and lit runway width represented a reduction from a previously greater width with the surface now outside the runway being of a similar appearance to the actual runway surface.

guid: https://skybrary.aero/accidents-and-incidents/at72-dresden-germany-2002 uri: https://skybrary.aero/accidents-and-incidents/at72-dresden-germany-2002 title: AT43/A346, Zurich Switzerland, 2010 link: https://skybrary.aero/accidents-and-incidents/at43a346-zurich-switzerland-2010 description:

On 18 June 2010, an ATR 42 began a daylight take off on runway 28 at Zurich without ATC clearance at the same time as an A340 began take off from intersecting runway 16 with an ATC clearance. ATC were unaware of this until alerted to the situation by the crew of another aircraft which was waiting to take off from runway 28, after which the ATR 42 was immediately instructed to stop and did so prior to the runway intersection whilst the A340 continued departure on runway 16 .

guid: https://skybrary.aero/accidents-and-incidents/at43a346-zurich-switzerland-2010 uri: https://skybrary.aero/accidents-and-incidents/at43a346-zurich-switzerland-2010 title: ATP, Helsinki Finland, 2010 link: https://skybrary.aero/accidents-and-incidents/atp-helsinki-finland-2010 description:

On 11 January 2010, a British Aerospace ATP crew attempting to take off from Helsinki after a two-step airframe de/anti icing treatment (Type 2 and Type 4 fluids) were unable to rotate and the take off was successfully rejected from above V1. The Investigation found that thickened de/anti ice fluid residues had frozen in the gap between the leading edge of the elevator and the horizontal stabiliser and that there had been many other similarly-caused occurrences to aircraft without powered flying controls. There was concern that use of such thickened de/anti ice fluids was not directly covered by safety regulation.

guid: https://skybrary.aero/accidents-and-incidents/atp-helsinki-finland-2010 uri: https://skybrary.aero/accidents-and-incidents/atp-helsinki-finland-2010 title: B737, Southend UK, 2010 link: https://skybrary.aero/accidents-and-incidents/b737-southend-uk-2010 description:

On 21 Nov 2010, a Boeing 737-700 being operated by Arik Air on a non revenue positioning flight from Southend to Lagos with only the two pilots on board carried out a successful take off in daylight and normal ground visibility from runway 06 but became airborne only just before the end of the runway.

guid: https://skybrary.aero/accidents-and-incidents/b737-southend-uk-2010 uri: https://skybrary.aero/accidents-and-incidents/b737-southend-uk-2010 title: B738 / A319, Dublin Ireland, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-a319-dublin-ireland-2010 description:

On 16 October 2010, in day VMC, a Boeing 737-800 being operated by Turkish Airlines on a passenger flight from Dublin to Istanbul entered runway 28 at Dublin whilst an Airbus A319 being operated by Germanwings on a scheduled passenger flight from Koln to Dublin was about 0.5nm from touchdown on the same runway. The Airbus immediately initiated a missed approach from approximately 200 ft aal simultaneously with an ATC call to do so.

guid: https://skybrary.aero/accidents-and-incidents/b738-a319-dublin-ireland-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-a319-dublin-ireland-2010 title: B772, Singapore, 2010 link: https://skybrary.aero/accidents-and-incidents/b772-singapore-2010 description:

On 14 June 2010, a Boeing 777-200 being operated by British Airways on a scheduled passenger service from Singapore to London Heathrow with a relief crew present on the flight received indications of abnormal functioning of the right engine during a night take off in VMC. Subsequent and directly related developments en route, including greater than planned fuel consumption which put the intended destination out of reach, led to the declaration of a PAN to ATC and diversion to Amsterdam. Inspection after flight found that parts of the right engine were damaged or missing and the latter were matched to previously unidentified debris recovered from the runway at Singapore. None of the 214 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/b772-singapore-2010 uri: https://skybrary.aero/accidents-and-incidents/b772-singapore-2010 title: B773, Lagos Nigeria, 2010 link: https://skybrary.aero/accidents-and-incidents/b773-lagos-nigeria-2010 description:

On 11 Jan 2010, an Air France Boeing 777-300ER successfully rejected a night take off from Lagos from significantly above V1 when control column pressure at rotation was perceived as abnormal. The root and secondary causes of the incident were found to be the failure of the Captain to arm the A/T during flight deck preparation and his inappropriate response to this on the take off roll. It was considered that his performance may have being an indirect consequence of his decision to take a 40 minute period of in-seat rest during the 90 minute transit stop at Lagos.

guid: https://skybrary.aero/accidents-and-incidents/b773-lagos-nigeria-2010 uri: https://skybrary.aero/accidents-and-incidents/b773-lagos-nigeria-2010 title: TBM8, Birmingham UK, 2011 link: https://skybrary.aero/accidents-and-incidents/tbm8-birmingham-uk-2011 description:

On 12 January 2011, a privately operated Socata TBM850 light aircraft on a flight from Antwerp to Birmingham lost radio contact with ATC whilst in IMC on a non precision approach to runway 15 prior to the issue of a landing clearance and prior to checking in on the ATC TWR frequency. It continued the approach to obtain the required visual reference before landing over the top of a DHC8-400 aircraft which had lined up ready for take off in accordance with ATC instructions. No damage or personal injury resulted from the close proximity.

guid: https://skybrary.aero/accidents-and-incidents/tbm8-birmingham-uk-2011 uri: https://skybrary.aero/accidents-and-incidents/tbm8-birmingham-uk-2011 title: CRJ9 / Vehicles, Whitehorse YK Canada, 2009 link: https://skybrary.aero/accidents-and-incidents/crj9-vehicles-whitehorse-yk-canada-2009 description:

On 6 March 2009, a Bombardier CRJ 705 being operated by Air Canada Jazz on a daylight scheduled domestic passenger flight from Vancouver BC to Whitehorse landed on runway 31L without clearance and after overflying two snow sweepers operating on the same runway. There was no contact between the aircraft and the vehicles or any abrupt avoidance manoeuvre and none of the 58 aircraft occupants or those in the vehicles were injured.

guid: https://skybrary.aero/accidents-and-incidents/crj9-vehicles-whitehorse-yk-canada-2009 uri: https://skybrary.aero/accidents-and-incidents/crj9-vehicles-whitehorse-yk-canada-2009 title: E145, Dayton OH USA, 2011 link: https://skybrary.aero/accidents-and-incidents/e145-dayton-oh-usa-2011 description:

On 31 January 2011, an Embraer 145LR being operated by Expressjet Airlines on a scheduled passenger flight from Cleveland OH to Dayton left landing runway 06R during a night landing in normal ground visibility and light winds and ended up on intersecting active runway 36. None of the 32 occupants were injured and only minor damage was caused to ground installations and the aircraft. No conflict with other aircraft resulted from the incursion onto runway 36 and after establishing that there was no major damage to the aircraft and after the taxiway route had been sanded the aircraft was taxied in to the gate for passenger disembarkation.

guid: https://skybrary.aero/accidents-and-incidents/e145-dayton-oh-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/e145-dayton-oh-usa-2011 title: MD81, Grenoble France, 2010 link: https://skybrary.aero/accidents-and-incidents/md81-grenoble-france-2010 description:

On 5 February 2010, a McDonnell Douglas MD 81 being operated by SAS on a non scheduled passenger flight from Copenhagen to Grenoble carried out a normal ILS approach to runway 09 in dark night VMC conditions, but the touchdown was made with the aircraft at an excessive pitch angle and higher than normal rate of descent and a tail strike occurred. Serious damage was caused to the rear lower fuselage but none of the 131 occupants were injured and a normal taxi-in and disembarkation followed.

guid: https://skybrary.aero/accidents-and-incidents/md81-grenoble-france-2010 uri: https://skybrary.aero/accidents-and-incidents/md81-grenoble-france-2010 title: PC12, en-route, near Derby Western Australia, 2010 link: https://skybrary.aero/accidents-and-incidents/pc12-en-route-near-derby-western-australia-2010 description:

On 29 January 2010, a Pilatus PC-12/45 being operated on an aerial work basis on a Medevac flight from Derby to Kununurra Western Australia and climbing through FL180 in night VMC experienced signs of engine malfunction and initiated an air turnback during which the engine failed completely. The subsequent 6nm glide descent and approach culminated in a successful landing with the aircraft undamaged and all four occupants unhurt.

guid: https://skybrary.aero/accidents-and-incidents/pc12-en-route-near-derby-western-australia-2010 uri: https://skybrary.aero/accidents-and-incidents/pc12-en-route-near-derby-western-australia-2010 title: E190 / Vehicle, Denver CO, USA 2011 link: https://skybrary.aero/accidents-and-incidents/e190-vehicle-denver-co-usa-2011 description:

On 31 December 2010, an Embraer ERJ190 being operated by Air Canada on a scheduled passenger service from Denver to Chicago was about to begin the take off roll from the full length of runway 34R at Denver in normal day visibility in accordance with ATC clearance when the flight crew observed the headlights of a vehicle approaching along the runway towards their position. The aircraft held position and advised ATC who had previously been unaware of the presence of the vehicle.

guid: https://skybrary.aero/accidents-and-incidents/e190-vehicle-denver-co-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/e190-vehicle-denver-co-usa-2011 title: RJ1H/UNKN, vicinity Malmo Sweden, 2009 link: https://skybrary.aero/accidents-and-incidents/rj1hunkn-vicinity-malmo-sweden-2009 description:

On 13 October 2009, an Avro RJ100 being operated by Malmo Aviation on a scheduled passenger flight from Stockholm Bromma to Malmo in day VMC came into proximity with a unseen light aircraft crossing below which activated a TCAS RA which was followed. The flight crew were unaware that they were outside controlled airspace at the time. No abrupt manoeuvring occurred and none of the 85 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/rj1hunkn-vicinity-malmo-sweden-2009 uri: https://skybrary.aero/accidents-and-incidents/rj1hunkn-vicinity-malmo-sweden-2009 title: MD83, Barcelona Spain, 2006 link: https://skybrary.aero/accidents-and-incidents/md83-barcelona-spain-2006 description:

On 9 January 2006, a Mc Donnell Douglas MD83 being operated by Spanair on a scheduled passenger flight from Bilbao to Barcelona made an unstablised day VMC approach to a dry runway 07R at destination and landed long with apparently locked brakes before coming to a stop 140 metres from the end of the 2660 metre long runway. Following ATC reports of a fire in the area of the left main landing gear, an evacuation was ordered using the right side doors during which five of the 96 occupants received minor injuries. The RFFS arrived at the scene during the evacuation and extinguished the fire. Significant damage occurred to both main landing gear assembles and to both wings and the tail assembly but there was no damage to the primary structure.

guid: https://skybrary.aero/accidents-and-incidents/md83-barcelona-spain-2006 uri: https://skybrary.aero/accidents-and-incidents/md83-barcelona-spain-2006 title: JS41, vicinity Durban South Africa, 2009 link: https://skybrary.aero/accidents-and-incidents/js41-vicinity-durban-south-africa-2009 description:

On 24 September 2009 a BAe Jetstream 41 being operated by SA Airlink on a positioning flight from Durban to Pietermaritzburg with only three crew members on board experienced an engine fire during take off and after reaching a height of about 500 feet agl then entered a semi controlled descent to a high impact forced landing in a residential area about 1400 metres beyond the runway end. The three occupants were all seriously injured and the aircraft commander subsequently died as a result of his injuries. A fourth person on the ground was also injured.

guid: https://skybrary.aero/accidents-and-incidents/js41-vicinity-durban-south-africa-2009 uri: https://skybrary.aero/accidents-and-incidents/js41-vicinity-durban-south-africa-2009 title: A306, vicinity London Gatwick, 2011 link: https://skybrary.aero/accidents-and-incidents/a306-vicinity-london-gatwick-2011 description:

On 12 January 2011, an Airbus A300-600 being operated by Monarch Airlines on a passenger flight from London Gatwick to Chania, Greece experienced activations of the stall protection system after an unintended configuration change shortly after take off but following recovery, the flight continued as intended without further event. There were no abrupt manoeuvres and no injuries to the 347 occupants.

guid: https://skybrary.aero/accidents-and-incidents/a306-vicinity-london-gatwick-2011 uri: https://skybrary.aero/accidents-and-incidents/a306-vicinity-london-gatwick-2011 title: CRJ2, Dubai UAE, 2011 link: https://skybrary.aero/accidents-and-incidents/crj2-dubai-uae-2011 description:

On 9 May 2011, a Bombardier Challenger 850 began a positioning flight night take off from Dubai aligned with the right hand edge of runway 30 for which take off clearance had been given. The error was not detected until a collision with a lighting installation after which a high speed rejected take off was made. The Investigation noted that the Captain had lined up the aircraft on the runway edge in good visibility before passing control for the take off to the low-experience First Officer. It was concluded that the crew failed to sufficiently prioritise their external situational awareness.

guid: https://skybrary.aero/accidents-and-incidents/crj2-dubai-uae-2011 uri: https://skybrary.aero/accidents-and-incidents/crj2-dubai-uae-2011 title: A332/A345, Khartoum Sudan, 2010 link: https://skybrary.aero/accidents-and-incidents/a332a345-khartoum-sudan-2010 description:

On 30 September 2010, an A330-200 was about to take off from Khartoum at night in accordance with its clearance when signalling from a hand-held flashlight and a radio call from another aircraft led to this not taking place. The other (on-stand) aircraft crew had found that they had been hit by the A330 as it had taxied past en route to the runway. The Investigation found that although there was local awareness that taxiway use and the provision of surface markings at Khartoum did not ensure safe clearance between aircraft, this was not being communicated by NOTAM or ATIS.

guid: https://skybrary.aero/accidents-and-incidents/a332a345-khartoum-sudan-2010 uri: https://skybrary.aero/accidents-and-incidents/a332a345-khartoum-sudan-2010 title: RJ85, Helsinki Finland 2010 link: https://skybrary.aero/accidents-and-incidents/rj85-helsinki-finland-2010 description:

On 12 June 2010, a requested 22R runway inspection at Helsinki in normal daylight visibility carried out after a severe engine failure during the take off roll had led an Avro RJ85 being operated by Finnish Airline Blue1 on a scheduled passenger flight to Copenhagen to reject that take off at high speed. This inspection had not detected significant debris deposited on the runway during the sudden and severe engine failure. Two passenger aircraft, one being operated by Finnair to Dubrovnik, Croatia and the other being operated by Swedish airline TUIfly Nordic to Rhodes, Greece then departed the same runway before a re-inspection disclosed the debris and it was removed. Neither of the aircraft which used the runway prior to debris removal were subsequently found to have suffered any damage but both were advised of the situation en route.

guid: https://skybrary.aero/accidents-and-incidents/rj85-helsinki-finland-2010 uri: https://skybrary.aero/accidents-and-incidents/rj85-helsinki-finland-2010 title: B734, Amsterdam Netherlands, 2010 (2) link: https://skybrary.aero/accidents-and-incidents/b734-amsterdam-netherlands-2010-2 description:

On 2 October 2010 a Boeing 737-400 being operated by Turkish operator Corendon Airlines on a passenger flight from Dalaman to Amsterdam made a late touchdown on landing runway 22 at destination in normal daylight visibility conditions and failed to stop before the end of the runway. The overrun occurred at low speed and there were no injuries to the 173 occupants and only minor damage to the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/b734-amsterdam-netherlands-2010-2 uri: https://skybrary.aero/accidents-and-incidents/b734-amsterdam-netherlands-2010-2 title: A321, vicinity Singapore, 2010 link: https://skybrary.aero/accidents-and-incidents/a321-vicinity-singapore-2010 description:

On 27 May 2010 an Airbus A321-200 being operated by Australian operator JetStar on a passenger flight from Darwin to Singapore continued an initial approach at destination in day VMC with the aircraft inappropriately configured before a late go around was commenced which was also flown in a configuration contrary to prescribed SOPs. A subsequent second approach proceeded to an uneventful landing. There were no unusual or sudden manoeuvres during the event and no injuries to the occupants.

guid: https://skybrary.aero/accidents-and-incidents/a321-vicinity-singapore-2010 uri: https://skybrary.aero/accidents-and-incidents/a321-vicinity-singapore-2010 title: B763/B738, vicinity Melbourne Australia, 2010 link: https://skybrary.aero/accidents-and-incidents/b763b738-vicinity-melbourne-australia-2010 description:

On 5 December 2010 a Boeing 767-300 being operated by Qantas and departing Melbourne for Sydney in day VMC was following a Boeing 737-800 being operated by Virgin Australia which had also just departed Melbourne for Brisbane on the same SID and a loss of prescribed separation occurred. ATC became aware that the 767 was catching up with the 737 but were aware that it was in visual contact and therefore took no action to ensure separation was maintained. No TCAS activation occurred.

guid: https://skybrary.aero/accidents-and-incidents/b763b738-vicinity-melbourne-australia-2010 uri: https://skybrary.aero/accidents-and-incidents/b763b738-vicinity-melbourne-australia-2010 title: B733, Amsterdam Netherlands, 2010 link: https://skybrary.aero/accidents-and-incidents/b733-amsterdam-netherlands-2010 description:

On 10 February 2010 a KLM Boeing 737-300 unintentionally made a night take off from Amsterdam in good visibility from the taxiway parallel to the runway for which take off clearance had been given. Because of the available distance and the absence of obstructions, the take off was otherwise uneventful. The Investigation noted the familiarity of the crew with the airport and identified apparent complacency.

guid: https://skybrary.aero/accidents-and-incidents/b733-amsterdam-netherlands-2010 uri: https://skybrary.aero/accidents-and-incidents/b733-amsterdam-netherlands-2010 title: B763, en-route, mid North Atlantic, 2011 link: https://skybrary.aero/accidents-and-incidents/b763-en-route-mid-north-atlantic-2011 description:

On 14 January 2011 an Air Canada Boeing 767-300 was midway across the Atlantic Ocean eastbound at night when the First Officer, who had just woken from an exceptionally long period in-seat rest, suddenly but erroneously perceived a collision risk from oncoming traffic and without warning intervened to dive the aircraft before the Captain could stop him causing 16 occupant injuries. His behaviour was attributed to the effect of sleep inertia following a much longer period of sleep than permitted by Air Canada procedures. It was concluded that many Air Canada pilots did not understand the reasoning behind these procedures.

guid: https://skybrary.aero/accidents-and-incidents/b763-en-route-mid-north-atlantic-2011 uri: https://skybrary.aero/accidents-and-incidents/b763-en-route-mid-north-atlantic-2011 title: B462, Stord Norway, 2006 link: https://skybrary.aero/accidents-and-incidents/b462-stord-norway-2006 description:

On 10 October 2006, a BAE Systems 146-200 being operated by Danish airline Atlantic Airways on a passenger flight from Sola to Stord overran the end of runway 33 at destination at a slow speed in normal visibility at dawn (but just prior to the accepted definition of daylight) before plunging down a steep slope sustaining severe damage and catching fire immediately it had come to rest. The rapid spread of the fire and difficulties in evacuation resulted in the death of four of the 16 occupants and serious injury to six others. The aircraft was completely destroyed.

guid: https://skybrary.aero/accidents-and-incidents/b462-stord-norway-2006 uri: https://skybrary.aero/accidents-and-incidents/b462-stord-norway-2006 title: A318/B739, vicinity Amsterdam Netherlands, 2007 link: https://skybrary.aero/accidents-and-incidents/a318b739-vicinity-amsterdam-netherlands-2007 description:

On 6 December 2007 an Airbus A318 being operated by Air France on a scheduled passenger flight from Lyon to Amsterdam carried out missed approach from runway 18C at destination and lost separation in night VMC against a Boeing 737-900 being operated by KLM on a scheduled passenger flight from Amsterdam to London Heathrow which had just departed from runway 24. The conflict was resolved by correct responses to the respective coordinated TCAS RAs after which the A318 passed close behind the 737. There were no abrupt manoeuvres and none of the 104 and 195 occupants respectively on board were injured.

guid: https://skybrary.aero/accidents-and-incidents/a318b739-vicinity-amsterdam-netherlands-2007 uri: https://skybrary.aero/accidents-and-incidents/a318b739-vicinity-amsterdam-netherlands-2007 title: B712, vicinity Kalgoorlie Western Australia, 2010 link: https://skybrary.aero/accidents-and-incidents/b712-vicinity-kalgoorlie-western-australia-2010 description:

On 13 October 2010, a Boeing 717-200 being operated by Cobham Aviation Services Australia for QantasLink on a scheduled passenger flight from Perth to Kalgoorlie Western Australia carried out two consecutive approaches at destination in day VMC which resulted in stick shaker activations and subsequent go arounds. A third approach at a higher indicated airspeed was uneventful and continued to a landing. There were no abrupt manoeuvres and none of the 102 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/b712-vicinity-kalgoorlie-western-australia-2010 uri: https://skybrary.aero/accidents-and-incidents/b712-vicinity-kalgoorlie-western-australia-2010 title: B738, Newcastle UK, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-newcastle-uk-2010 description:

On 25 November 2010, a Boeing 737-800 being operated by Thompson Airways on a passenger fight from Arrecife, Lanzarote to Newcastle UK marginally overran Runway 07 at destination onto the paved stopway during a night landing in normal ground visibility. None of the 197 occupants were injured and the aircraft was undamaged. Passengers were disembarked to buses for transport to the terminal. An acceptable disposition of frozen deposits had been advised as present on the runway prior to the approach after a sweeping operation had been conducted following a discontinued approach ten minutes earlier because of advice from ATC that the runway was contaminated with wet snow.

guid: https://skybrary.aero/accidents-and-incidents/b738-newcastle-uk-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-newcastle-uk-2010 title: B738, vicinity Faro Portugal, 2011 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-faro-portugal-2011 description:

On 24 October 2011, the crew of a Ryanair Boeing 737-800 operating the first flight after an unexpectedly severe overnight storm found that after take off, an extremely large amount of rudder trim was required to fly ahead. Following an uneventful return to land, previously undetected damage to the rudder assembly was found which was attributed to the effects of the storm. It was found that pre flight checks required at the time could not have detected the damage and noted that the wind speeds which occurred were much higher than those anticipated by the applicable certification requirements.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-faro-portugal-2011 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-faro-portugal-2011 title: GLF4, Bedford MA USA, 2014 link: https://skybrary.aero/accidents-and-incidents/glf4-bedford-ma-usa-2014 description:

On 31 May 2014, a Gulfstream IV attempted to take off with the flight control gust locks engaged and, when unable to rotate, delayed initiating the inevitable rejected take off to a point where an overrun at high speed was inevitable. The aircraft was destroyed by a combination of impact forces and fire and all seven occupants died. The Investigation attributed the accident to the way the crew were found to have habitually operated but noted that type certification had been granted despite the aircraft not having met requirements which would have generated an earlier gust lock status warning.

guid: https://skybrary.aero/accidents-and-incidents/glf4-bedford-ma-usa-2014 uri: https://skybrary.aero/accidents-and-incidents/glf4-bedford-ma-usa-2014 title: DHC6, en-route, Arghakhanchi Western Nepal, 2014 link: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-arghakhanchi-western-nepal-2014 description:

On 16 February 2014 a Nepal Airlines DHC6 attempting a diversion on a VFR flight which had encountered adverse weather impacted terrain at an altitude of over 7000 feet in a mountainous area after intentionally entering cloud following a decision to divert due to weather incompatible with VFR. The aircraft was destroyed and all 18 occupants were killed. The Investigation attributed the accident to loss of situational awareness by the aircraft commander and inadequate crew co-operation in responding to the prevailing weather conditions.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-arghakhanchi-western-nepal-2014 uri: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-arghakhanchi-western-nepal-2014 title: GLEX/F2TH, vicinity Ibiza Spain, 2012 link: https://skybrary.aero/accidents-and-incidents/glexf2th-vicinity-ibiza-spain-2012 description:

On 21 September 2012, two aircraft came into conflict in Class 'A' airspace whilst under radar control at night and loss of separation was resolved by TCAS RA responses by both aircraft. Investigation found that one of the aircraft had passed a procedurally-documented clearance limit without ATC clearance or intervention and that situational awareness of its crew had been diminished by communications with the conflicting aircraft being conducted in Spanish rather than English. A Safety Recommendation on resolving the persistent problem of such language issues was made, noting that a similar recommendation had been made 11 years earlier.

guid: https://skybrary.aero/accidents-and-incidents/glexf2th-vicinity-ibiza-spain-2012 uri: https://skybrary.aero/accidents-and-incidents/glexf2th-vicinity-ibiza-spain-2012 title: B773, en-route, Bering Sea, 2013 link: https://skybrary.aero/accidents-and-incidents/b773-en-route-bering-sea-2013 description:

On 2 July 2013, a Korean Air Lines Boeing 777-300 experienced an uncommanded in-flight shutdown of one of its GE90-115B engines while crossing the Bering Sea. The crew made an uneventful diversion to Anadyr Russia. The Korean Aviation and Railway Accident Investigation Board (ARAIB) delegated investigative duties of this event to the National Transportation Safety Board (NTSB) which identified the cause of the failure as a manufacturing process deficiency which could affect nearly 200 similar engines.

guid: https://skybrary.aero/accidents-and-incidents/b773-en-route-bering-sea-2013 uri: https://skybrary.aero/accidents-and-incidents/b773-en-route-bering-sea-2013 title: A343 / GLID, en-route, north of Waldshut-Tiengen southwest Germany, 2012 link: https://skybrary.aero/accidents-and-incidents/a343-glid-en-route-north-waldshut-tiengen-southwest-germany-2012 description:

On 11 August 2012, the augmenting crew member in the flight deck of an Airbus A340 about to join final approach to Zurich in Class 'C' airspace as cleared suddenly saw a glider on a collision course with the aircraft. The operating crew were alerted and immediately executed a pronounced avoiding manoeuvre and the two aircraft passed at approximately the same level with approximately 260 metres separation. The Investigation attributed the conflict to airspace incursion by the glider and issue of a clearance to below MRVA to the A340 and noted the absence of relevant safety nets.

guid: https://skybrary.aero/accidents-and-incidents/a343-glid-en-route-north-waldshut-tiengen-southwest-germany-2012 uri: https://skybrary.aero/accidents-and-incidents/a343-glid-en-route-north-waldshut-tiengen-southwest-germany-2012 title: AT75, vicinity Magong Taiwan, 2014 link: https://skybrary.aero/accidents-and-incidents/at75-vicinity-magong-taiwan-2014 description:

On 23 July 2014, a TransAsia Airways ATR 72-500 crashed into terrain shortly after commencing a go around from a VOR approach at its destination in day IMC in which the aircraft had been flown significantly below the MDA without visual reference. The aircraft was destroyed and48 of the 58 occupants were killed. The Investigation found that the accident was entirely attributable to the actions of the crew and that it had occurred in a context of a systemic absence of effective risk management at the Operator which had not been adequately addressed by the Safety Regulator.

guid: https://skybrary.aero/accidents-and-incidents/at75-vicinity-magong-taiwan-2014 uri: https://skybrary.aero/accidents-and-incidents/at75-vicinity-magong-taiwan-2014 title: A306, vicinity Birmingham AL USA, 2013 link: https://skybrary.aero/accidents-and-incidents/a306-vicinity-birmingham-al-usa-2013 description:

On 14 August 2013, a UPS Airbus A300-600 crashed short of the runway at Birmingham Alabama on a night IMC non-precision approach after the crew failed to go around at 1000ft aal when unstabilised and then continued descent below MDA until terrain impact. The Investigation attributed the accident to the individually poor performance of both pilots, to performance deficiencies previously-exhibited in recurrent training by the Captain and to the First Officer's failure to call in fatigued and unfit to fly after mis-managing her off duty time. A Video was produced by NTSB to further highlight human factors aspects.

guid: https://skybrary.aero/accidents-and-incidents/a306-vicinity-birmingham-al-usa-2013 uri: https://skybrary.aero/accidents-and-incidents/a306-vicinity-birmingham-al-usa-2013 title: CRJ1, Kinshasa Democratic Republic of Congo, 2011 link: https://skybrary.aero/accidents-and-incidents/crj1-kinshasa-democratic-republic-congo-2011 description:

On 4 April 2011, the crew of a Georgian Airways Bombardier CRJ100 operating a domestic flight for the United Nations lost control of their aircraft as they commenced a go around from below the MDA for the non precision approach flown due to an absence of visual reference with the runway. They were aware from their weather radar of severe convective weather in the vicinity of the airport although the METAR passed by ATC did not indicate this. The aircraft crashed alongside the runway and was destroyed. All occupants except one who was seriously injured were killed.

guid: https://skybrary.aero/accidents-and-incidents/crj1-kinshasa-democratic-republic-congo-2011 uri: https://skybrary.aero/accidents-and-incidents/crj1-kinshasa-democratic-republic-congo-2011 title: D328 / R44, Bern Switzerland, 2012 link: https://skybrary.aero/accidents-and-incidents/d328-r44-bern-switzerland-2012 description:

On 2 June 2012, a Dornier 328 and a commercially-operated Robinson R44 helicopter came into close proximity within the airport perimeter whilst both were departing from Bern in VMC as cleared. The Investigation attributed the conflict to inappropriate issue of clearances by the controller in a context of an absence of both a defined final approach and take off area and fixed departure routes to the three designated departure points.

guid: https://skybrary.aero/accidents-and-incidents/d328-r44-bern-switzerland-2012 uri: https://skybrary.aero/accidents-and-incidents/d328-r44-bern-switzerland-2012 title: ULAC / A319 vicinity Southend UK, 2013 link: https://skybrary.aero/accidents-and-incidents/ulac-a319-vicinity-southend-uk-2013 description:

On 18 July 2013, an Airbus A319 level at 2000 feet QNH in Class G airspace and being radar vectored towards an ILS approach at Southend in day VMC had a sudden but brief base leg encounter with a paramotor which was not visible on radar and was seen too late for avoiding action to be practicable, before passing within an estimated 50 metres of the A319. The paramotor pilot could not subsequently be traced. The Investigation made a safety recommendation to the UK CAA to review the regulation and licensing of paramotor pilots.

guid: https://skybrary.aero/accidents-and-incidents/ulac-a319-vicinity-southend-uk-2013 uri: https://skybrary.aero/accidents-and-incidents/ulac-a319-vicinity-southend-uk-2013 title: Vehicle / E190, Toronto Canada, 2013 link: https://skybrary.aero/accidents-and-incidents/vehicle-e190-toronto-canada-2013 description:

On 11 March 2013, at night, a Sunwing Airlines' mechanic left their vehicle on the ramp with the engine running and in 'drive' and, unseen, it began moving towards the adjacent runway threshold, at which point ATC noticed a ground radar target and instructed an Air Canada Embraer 190 which was close to landing in accordance with a valid clearance to go around. The pilots did not hear these instructions and landed directly over the vehicle with approximately 35 feet clearance without seeing it.

guid: https://skybrary.aero/accidents-and-incidents/vehicle-e190-toronto-canada-2013 uri: https://skybrary.aero/accidents-and-incidents/vehicle-e190-toronto-canada-2013 title: B788, en-route Shikoku Island Japan, 2013 link: https://skybrary.aero/accidents-and-incidents/b788-en-route-shikoku-island-japan-2013 description:

On 16 January 2013, a main battery failure alert message accompanied by a burning smell in the flight deck was annunciated as an ANA Boeing 787-8 climbed through FL320 on a domestic flight. A diversion was immediately initiated and an emergency declared. A landing at Takamatsu was made 20 minutes later and an emergency evacuation completed. The Investigation found that the battery had been destroyed when thermal runway followed a suspected internal short circuit in one of the battery cells and concluded that certification had underestimated the potential consequences of such a single cell failure.

guid: https://skybrary.aero/accidents-and-incidents/b788-en-route-shikoku-island-japan-2013 uri: https://skybrary.aero/accidents-and-incidents/b788-en-route-shikoku-island-japan-2013 title: F100 / EC45, vicinity Bern Switzerland, 2012 link: https://skybrary.aero/accidents-and-incidents/f100-ec45-vicinity-bern-switzerland-2012 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/f100-ec45-vicinity-bern-switzerland-2012 uri: https://skybrary.aero/accidents-and-incidents/f100-ec45-vicinity-bern-switzerland-2012 title: LJ24, vicinity Bornholm Denmark, 2012 link: https://skybrary.aero/accidents-and-incidents/lj24-vicinity-bornholm-denmark-2012 description:

On 15 September 2012, a Learjet 24 experienced double engine failure in daylight VMC as it positioned visually on base leg at Bornholm and an emergency was declared. The subsequent handling of the aircraft then led to a stall from which recovery was not possible and terrain impact occurred in a standing crop at low forward speed shortly after crossing the coastline. The aircraft was destroyed and both occupants seriously injured. Investigation established that the engines had stopped due to fuel starvation resulting from mismanagement of the fuel system and had been preceded by a low fuel quantity warning.

guid: https://skybrary.aero/accidents-and-incidents/lj24-vicinity-bornholm-denmark-2012 uri: https://skybrary.aero/accidents-and-incidents/lj24-vicinity-bornholm-denmark-2012 title: DH8A, en-route SSE of Madang, Papua New Guinea, 2011 link: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-sse-madang-papua-new-guinea-2011 description:

On 13 October 2011, the Captain of a Bombardier DHC8-100 manually flying a low power, steep descent in an attempt to get below cloud to be able to see the destination aerodrome inadvertently allowed the speed to increase sufficiently to trigger an overspeed warning. In response, the power levers were rapidly retarded and both propellers entered the ground range and oversped. As a result, one engine was damaged beyond use and the other could not be unfeathered. A forced landing was made following which the aircraft caught fire. All three crew members but only one of the 29 passengers survived.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-sse-madang-papua-new-guinea-2011 uri: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-sse-madang-papua-new-guinea-2011 title: MA60, Kupang Indonesia, 2013 link: https://skybrary.aero/accidents-and-incidents/ma60-kupang-indonesia-2013 description:

On 10 June 2013, a Merpati Nusantara Xian MA60 flown by a First Officer undergoing supervised line training made an unstable visual approach at destination which culminated in a sudden further increase in the rate of descent. The aircraft initially touched down on the runway with a vertical acceleration of 6g and then, after a bounce of -3g, stopped in 200 metres. The impact resulted in the wing box separating from the fuselage. The Investigation found that the Power Levers had been unintentionally moved into the ground range shortly before touchdown without either pilot being aware.

guid: https://skybrary.aero/accidents-and-incidents/ma60-kupang-indonesia-2013 uri: https://skybrary.aero/accidents-and-incidents/ma60-kupang-indonesia-2013 title: A139, vicinity Sky Shuttle Heliport Hong Kong China, 2010 link: https://skybrary.aero/accidents-and-incidents/a139-vicinity-sky-shuttle-heliport-hong-kong-china-2010 description:

On 3 July 2010, an AW139 helicopter was climbing through 350 feet over Victoria Harbour Hong Kong just after takeoff when the tail rotor detached. A transition to autorotation was accomplished and a controlled ditching followed. All occupants were rescued but some sustained minor injuries. The failure was attributed entirely to manufacturing defects but no corrective manufacturer or regulatory action was taken until two similar accidents had occurred in Qatar (non-fatal) and Brazil (fatal) the following year and two interim Safety Recommendations were issued from this Investigation after which a comprehensive review of the manufacturing process led to numerous changes.

guid: https://skybrary.aero/accidents-and-incidents/a139-vicinity-sky-shuttle-heliport-hong-kong-china-2010 uri: https://skybrary.aero/accidents-and-incidents/a139-vicinity-sky-shuttle-heliport-hong-kong-china-2010 title: AT72, vicinity Pakse Laos, 2013 link: https://skybrary.aero/accidents-and-incidents/at72-vicinity-pakse-laos-2013 description:

On 16 October 2013, the crew of an ATR72-600 unintentionally flew their aircraft into the ground in IMC during a go around from an unsuccessful non precision approach at destination Pakse. The Investigation concluded that although the aircraft had followed the prescribed track, the crew had been confused by misleading FD indications resulting from their failure to reset the selected altitude to the prescribed stop altitude so that the decision altitude they had used for the approach remained as the selected altitude. Thereafter, erratic control of aircraft altitude had eventually resulted in controlled flight into terrain killing all on board.

guid: https://skybrary.aero/accidents-and-incidents/at72-vicinity-pakse-laos-2013 uri: https://skybrary.aero/accidents-and-incidents/at72-vicinity-pakse-laos-2013 title: BE20, Nadi Fiji, 2010 link: https://skybrary.aero/accidents-and-incidents/be20-nadi-fiji-2010 description:

On 25 April 2010, a Beech King Air touched down at Nadi with its landing gear in the transit position after flying a night approach during which a significant electrical system failure had occurred. The landing gear retracted and the aircraft left the runway to the side and came to a stop resting on its fuselage. The Investigation attributed the electrical failure, which directly affected the landing gear operating system and required two diodes to have both failed was likely to have meant that one would have failed on an earlier occasion with no apparent consequence.

guid: https://skybrary.aero/accidents-and-incidents/be20-nadi-fiji-2010 uri: https://skybrary.aero/accidents-and-incidents/be20-nadi-fiji-2010 title: B738, Alicante Spain, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-alicante-spain-2013 description:

On 27 March 2013, a Ryanair Boeing 737-800 was mis-handled during take off and a minor tailstrike occurred. The crew were slow to respond and continued an uninterrupted climb to FL220 before deciding to return to land and beginning the corresponding QRH drill. When the cabin pressurisation outflow valve was fully opened at FL130, the cabin depressurised almost instantly and the crew temporarily donned oxygen masks. The Investigation noted the absence of any caution on the altitude at which the QRH drill should be used but also noted clear guidance that the procedure should be actioned without delay.

guid: https://skybrary.aero/accidents-and-incidents/b738-alicante-spain-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-alicante-spain-2013 title: SB20, vicinity Sumburgh, UK 2014 link: https://skybrary.aero/accidents-and-incidents/sb20-vicinity-sumburgh-uk-2014 description:

On 15 December 2014, the Captain of a Saab 2000 lost control of his serviceable aircraft after a lightning strike when he attempted to control the aircraft manually without first disconnecting the autopilot and despite the annunciation of a series of related alerts. The aircraft descended from 4,000 feet to 1,100 feet at up to 9,500 fpm and 80 knots above Vmo. A fortuitous transient data transmission fault caused autopilot disconnection making it possible to respond to EGPWS 'SINK RATE' and 'PULL UP' Warnings. The Investigation concluded that limitations on autopilot disconnection by pilot override were contrary to the type certification of most other transport aircraft.

guid: https://skybrary.aero/accidents-and-incidents/sb20-vicinity-sumburgh-uk-2014 uri: https://skybrary.aero/accidents-and-incidents/sb20-vicinity-sumburgh-uk-2014 title: GLEX, Prestwick UK, 2014 link: https://skybrary.aero/accidents-and-incidents/glex-prestwick-uk-2014 description:

On 6 March 2014, a Bombardier Global 6000 being landed by a pilot using a HUD at night was mishandled to the extent that one wing was damaged by ground contact due to excessive pitch just before touchdown. During the Investigation, a Global 6000 operated by a different operator was similarly damaged during a night landing. The Investigation discovered that relevant operational documentation was inconsistent and pilot training had (in both cases) been inappropriate. These issues were resolved by a combination of aircraft manufacturer and aircraft operator action

guid: https://skybrary.aero/accidents-and-incidents/glex-prestwick-uk-2014 uri: https://skybrary.aero/accidents-and-incidents/glex-prestwick-uk-2014 title: DH8D, Aalborg Denmark, 2007 link: https://skybrary.aero/accidents-and-incidents/dh8d-aalborg-denmark-2007 description:

On 9 September 2007 the crew of an SAS Bombardier DHC8-400 approaching Aalborg were unable to lock the right MLG down and prepared accordingly. During the subsequent landing, the unlocked gear leg collapsed and the right engine propeller blades struck the runway. Two detached completely and penetrated the passenger cabin injuring one passenger. The Investigation found that the gear malfunction had been caused by severe corrosion of a critical connection and noted that no scheduled maintenance task included appropriate inspection. A Safety Recommendation to the EASA to review the design, certification and maintenance of the assembly involved was made.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-aalborg-denmark-2007 uri: https://skybrary.aero/accidents-and-incidents/dh8d-aalborg-denmark-2007 title: S76, Peasmarsh East Sussex UK, 2012 link: https://skybrary.aero/accidents-and-incidents/s76-peasmarsh-east-sussex-uk-2012 description:

On 3 May 2012, a Sikorsky S76C operating a passenger flight to a private landing site at night discontinued an initial approach because of lack of visual reference in an unlit environment and began to position for another. The commander became spatially disorientated and despite a number of EGPWS Warnings, continued manoeuvring until ground impact was only narrowly avoided - the minimum recorded height was 2 feet +/- 2 feet. An uneventful diversion followed. The Investigation recommended a review of the regulations that allowed descent below MSA for landing when flying in IMC but not on a published approach procedure.

guid: https://skybrary.aero/accidents-and-incidents/s76-peasmarsh-east-sussex-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/s76-peasmarsh-east-sussex-uk-2012 title: E55P, St Gallen-Altenrhein Switzerland, 2012 link: https://skybrary.aero/accidents-and-incidents/e55p-st-gallen-altenrhein-switzerland-2012 description:

On 6 August 2012 an Embraer Phenom 300 initiated a late go-around from an unstabilised ILS/DME approach at St. Gallen-Altenrhein. A second approach was immediately flown with a flap fault which had occurred during the first one and was also unstabilised with touchdown on a wet runway occurring at excessive speed. The aircraft could not be stopped before an overrun occurred during which a collision with a bus on the public road beyond the aerodrome perimeter was narrowly avoided. The aircraft was badly damaged but the occupants were uninjured. The outcome was attributed to the actions and inactions of the crew.

guid: https://skybrary.aero/accidents-and-incidents/e55p-st-gallen-altenrhein-switzerland-2012 uri: https://skybrary.aero/accidents-and-incidents/e55p-st-gallen-altenrhein-switzerland-2012 title: A320, Paris Orly France, 2013 link: https://skybrary.aero/accidents-and-incidents/a320-paris-orly-france-2013 description:

On 12 March 2013, a Tunis Air Airbus A320 landed on runway 08 at Paris Orly and, having slowed to just over 40 knots, were expecting, despite the covering of dry snow and some slush pre-notified and found on the runway, to vacate it without difficulty at the mid point. ATC then requested that the aircraft roll to the end of the runway before clearing. However, after a slight increase in speed, the crew were unable to subsequently slow the aircraft as the runway end approached and it overran at a low groundspeed before coming to a stop 4 seconds later.

guid: https://skybrary.aero/accidents-and-incidents/a320-paris-orly-france-2013 uri: https://skybrary.aero/accidents-and-incidents/a320-paris-orly-france-2013 title: B190, Blue River BC Canada, 2012 link: https://skybrary.aero/accidents-and-incidents/b190-blue-river-bc-canada-2012 description:

On 17 March 2012, the Captain of a Beech 1900C operating a revenue passenger flight lost control of the aircraft during landing on the 18metre wide runway at destination after an unstabilised day visual approach and the aircraft veered off it into deep snow. The Investigation found that the Operator had not specified any stable approach criteria and was not required to do so. It was also noted that VFR minima had been violated and, noting a fatal accident at the same aerodrome five months previously, concluded that the Operators risk assessment and risk management processes were systemically deficient.

guid: https://skybrary.aero/accidents-and-incidents/b190-blue-river-bc-canada-2012 uri: https://skybrary.aero/accidents-and-incidents/b190-blue-river-bc-canada-2012 title: AT72, Copenhagen Denmark, 2013 link: https://skybrary.aero/accidents-and-incidents/at72-copenhagen-denmark-2013 description:

On 14 January 2013, selection of the power levers to ground idle after an ATR 72-200 touchdown at Copenhagen produced only one of the two expected low pitch indications. As the First Officer called 'one low pitch' in accordance with SOP, the Captain selected both engines into reverse. He was unable to prevent the resultant veer off the runway. After travelling approximately 350 metres on grass alongside the runway as groundspeed reduced, the runway was regained. A propeller control fault which would have prevented low pitch transition on the right engine was recorded but could not subsequently be replicated.

guid: https://skybrary.aero/accidents-and-incidents/at72-copenhagen-denmark-2013 uri: https://skybrary.aero/accidents-and-incidents/at72-copenhagen-denmark-2013 title: A332 / A333, en-route, North West Australia, 2012 link: https://skybrary.aero/accidents-and-incidents/a332-a333-en-route-north-west-australia-2012 description:

On 31 March 2012, after the implementation of contingency ATC procedures for a period of 5 hours due to controller shortage, two Garuda A330 aircraft which had been transiting an associated Temporary Restricted Area (TRA) prior to re-entering controlled airspace were separately involved in losses of separation assurance, one when unexpectedly entering adjacent airspace from the TRA, the other when the TRA ceased and controlled airspace was restored. The Investigation did not find that any actual loss of separation had occurred but identified four Safety Issues in relation to the inadequate handling of the TRA activation by ANSP Airservices Australia.

guid: https://skybrary.aero/accidents-and-incidents/a332-a333-en-route-north-west-australia-2012 uri: https://skybrary.aero/accidents-and-incidents/a332-a333-en-route-north-west-australia-2012 title: B77L, Copenhagen Denmark, 2011 link: https://skybrary.aero/accidents-and-incidents/b77l-copenhagen-denmark-2011 description:

On 17 April 2011, a Boeing 777F bounced three times during an attempted landing at Copenhagen during which the underside of the aircraft was damaged by two tailstrikes. The second occurred during over-rotation for a go around commenced after thrust reverser deployment, with 760 metres of the 3300 metre-long runway remaining. The Investigation observed that a go around initiated after thrust reverser deployment was contrary to an express prohibition in the aircraft type FCOM. It was noted that the aircraft commander was an instructor pilot and that both pilots had less than 200 hours experience on the aircraft type.

guid: https://skybrary.aero/accidents-and-incidents/b77l-copenhagen-denmark-2011 uri: https://skybrary.aero/accidents-and-incidents/b77l-copenhagen-denmark-2011 title: C310, Hawarden UK, 2013 link: https://skybrary.aero/accidents-and-incidents/c310-hawarden-uk-2013 description:

On 15 November 2013, a privately operated Cessna 310 about to land at Hawarden crashed after power was lost from one engine and the experienced pilot appeared to have attempted to initiate a go around rather than land on the grass next to the runway. The Investigation found that both main fuel tanks were effectively empty after normal fuel use during the flight and since unused fuel remained in the auxiliary tanks, it was concluded that fuel starvation attributable to en route fuel system mismanagement had occurred. The other engine had been at full power but with fuel starvation imminent.

guid: https://skybrary.aero/accidents-and-incidents/c310-hawarden-uk-2013 uri: https://skybrary.aero/accidents-and-incidents/c310-hawarden-uk-2013 title: A320 / A139 vicinity Zurich Switzerland, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-a139-vicinity-zurich-switzerland-2012 description:

On 29 May 2012, a British Airways Airbus A320 departing Zürich and in accordance with its SID in a climbing turn received and promptly and correctly actioned a TCAS RA 'CLIMB'. The conflict which caused this was with an AW 139 also departing Zürich IFR in accordance with a SID but, as this aircraft was only equipped with a TAS to TCAS 1 standard, the crew independently determined from their TA that they should descend and did so. The conflict, in Class 'C' airspace, was attributed to inappropriate clearance issue by the TWR controller and their inappropriate separation monitoring thereafter.

guid: https://skybrary.aero/accidents-and-incidents/a320-a139-vicinity-zurich-switzerland-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-a139-vicinity-zurich-switzerland-2012 title: AT45, vicinity Prague Czech Republic, 2012 link: https://skybrary.aero/accidents-and-incidents/at45-vicinity-prague-czech-republic-2012 description:

On 31 October 2012, the crew of an ATR42 on a handover airworthiness function flight out of Prague briefly lost control in a full stall with significant wing drop after continuing a prescribed Stall Protection System (SPS) test below the appropriate speed and then failing to follow the correct stall recovery procedure. Failure of the attempted SPS test was subsequently attributed to both AOA vanes having become contaminated with water during earlier aircraft repainting at a specialist contractor and consequently being constrained in a constant position whilst the SPS test was being conducted at well above the prevailing freezing level.

guid: https://skybrary.aero/accidents-and-incidents/at45-vicinity-prague-czech-republic-2012 uri: https://skybrary.aero/accidents-and-incidents/at45-vicinity-prague-czech-republic-2012 title: Vehicle / B712, Perth Western Australia, 2014 link: https://skybrary.aero/accidents-and-incidents/vehicle-b712-perth-western-australia-2014 description:

On 26 July 2014, the crew of a Boeing 717 which had just touched down on the destination landing runway at Perth in normal day visibility as a heavy shower cleared the airport area after previously receiving and acknowledging a landing clearance saw the rear of a stationary vehicle on the runway centreline approximately 1180 metres from the landing threshold. An immediate go around was called and made and the aircraft cleared the vehicle by about 150 feet. The same experienced controller who had issued the landing clearance was found to have earlier given runway occupancy clearance to the vehicle.

guid: https://skybrary.aero/accidents-and-incidents/vehicle-b712-perth-western-australia-2014 uri: https://skybrary.aero/accidents-and-incidents/vehicle-b712-perth-western-australia-2014 title: B738/A319 en-route, south east of Zurich Switzerland, 2013 link: https://skybrary.aero/accidents-and-incidents/b738a319-en-route-south-east-zurich-switzerland-2013 description:

On 12 April 2013, a Ryanair Boeing 737-800 took a climb clearance intended for another Ryanair aircraft on the same frequency. The aircraft for which the clearance was intended did not respond and the controller did not notice that the clearance readback had come from a different aircraft. Once the wrong aircraft began to climb, from FL360 to FL380, a TCAS RA to descend occurred due to traffic just transferred to a different frequency and at FL370. That traffic received a TCAS RA to climb. STCA was activated at the ATS Unit controlling both Ryanair aircraft.

guid: https://skybrary.aero/accidents-and-incidents/b738a319-en-route-south-east-zurich-switzerland-2013 uri: https://skybrary.aero/accidents-and-incidents/b738a319-en-route-south-east-zurich-switzerland-2013 title: DH8D, Sault Ste. Marie ON Canada, 2013 link: https://skybrary.aero/accidents-and-incidents/dh8d-sault-ste-marie-canada-2013 description:

On 26 May 2013, a Porter Airlines DHC8-400 sustained substantial damage as a result of a mishandled night landing off a visual approach at Sault Ste. Marie which led to a 3g tail strike. The prior approach was stabilised at 500 feet but then unstabilised below that height. The handling pilot involved was a First Officer with 134 hours experience on the aircraft type, which was his first experience of multi crew transport aircraft after significant experience flying light aircraft. An absence of effective monitoring or intervention by the aircraft commander was identified during the Investigation.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-sault-ste-marie-canada-2013 uri: https://skybrary.aero/accidents-and-incidents/dh8d-sault-ste-marie-canada-2013 title: A332, vicinity Perth Australia, 2014 link: https://skybrary.aero/accidents-and-incidents/a332-vicinity-perth-australia-2014 description:

On 9 June 2014, a 'burning odour' of undetermined origin became evident in the rear galley of an Airbus A330 as soon as the aircraft powered up for take off. Initially, it was dismissed as not uncommon and likely to soon dissipate, but it continued and affected cabin crew were unable to continue their normal duties and received oxygen to assist recovery. En route diversion was considered but flight completion chosen. It was found that the rear pressure bulkhead insulation had not been correctly refitted following maintenance and had collapsed into and came into contact with APU bleed air duct.

guid: https://skybrary.aero/accidents-and-incidents/a332-vicinity-perth-australia-2014 uri: https://skybrary.aero/accidents-and-incidents/a332-vicinity-perth-australia-2014 title: PC6, Evora Portugal, 2012 link: https://skybrary.aero/accidents-and-incidents/pc6-evora-portugal-2012 description:

On 29 July 2012, the rudder of a Pilatus PC6 detached in flight and fell onto the stabiliser/elevator preventing its normal movement. Pitch control was gained using the electric stabiliser trim and a successful touchdown was achieved on the second attempt. However, directional control could not be maintained and a lateral runway excursion followed. Investigation attributed the rudder failure to maintenance error which went undetected. Unapproved dispensation by the maintenance organisation involved, which allowed some dual inspections for correct completion of safety critical tasks to be carried out by the same person, was considered to be a significant contributory factor.

guid: https://skybrary.aero/accidents-and-incidents/pc6-evora-portugal-2012 uri: https://skybrary.aero/accidents-and-incidents/pc6-evora-portugal-2012 title: SF34, vicinity Newcastle New South Wales Australia, 2012 link: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-newcastle-new-south-wales-australia-2012 description:

On 8 November 2012, the crew of a Saab 340 advised destination ATC at Newcastle in daylight hours that they were 'visual' and were so cleared. The aircraft was then observed to turn towards the lights of an industrial complex 6nm from the airport and descend and ATC intervened to provide guidance to final approach. Investigation found that the experienced Captain was guiding the First Officer, who had gained his professional licence 10 months earlier, towards what he had mistaken for the runway. Descent, perceived by the Captain as on 'finals', continued to 680 feet agl before a climb commenced.

guid: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-newcastle-new-south-wales-australia-2012 uri: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-newcastle-new-south-wales-australia-2012 title: A319 / B735, vicinity Prague Czech Republic, 2012 link: https://skybrary.aero/accidents-and-incidents/a319-b735-vicinity-prague-czech-republic-2012 description:

On 7 September 2012, the crew of an Air France Airbus A319 failed to follow their arrival clearance at destination and turned directly towards the ILS FAF and thereby into conflict with a Boeing 737-500 on an ILS approach. When instructed to turn left (and clear of the ILS) by the controller, the crew replied that they were following standard arrival which was not the case. As the separation between the two aircraft reduced, the controller repeated the instruction to the A319 to turn left and this was acknowledged. Minimum lateral separation was 1.7nm, sufficient to activate STCA.

guid: https://skybrary.aero/accidents-and-incidents/a319-b735-vicinity-prague-czech-republic-2012 uri: https://skybrary.aero/accidents-and-incidents/a319-b735-vicinity-prague-czech-republic-2012 title: IL76, St John's Newfoundland Canada, 2012 link: https://skybrary.aero/accidents-and-incidents/il76-st-johns-newfoundland-canada-2012 description:

On 13 August 2012, an Ilyushin IL76 freighter overran landing runway 11 at St John's at 40 knots. The Investigation established that although a stabilised approach had been flown, the aircraft had been allowed to float in the presence of a significant tail wind component and had not finally touched down until half way along the 2590 metre long runway. It was also found that reverse thrust had then not been fully utilised and that cross connection of the brake lines had meant that the anti skid pressure release system worked in reverse sense, thus reducing braking effectiveness.

guid: https://skybrary.aero/accidents-and-incidents/il76-st-johns-newfoundland-canada-2012 uri: https://skybrary.aero/accidents-and-incidents/il76-st-johns-newfoundland-canada-2012 title: A332 / A332, en-route, near Adelaide South Australia, 2013 link: https://skybrary.aero/accidents-and-incidents/a332-a332-en-route-near-adelaide-south-australia-2013 description:

On 20 September 2013, a loss of separation occurred between two en route Airbus A330s under radar surveillance in controlled airspace near Adelaide. The potential conflict was resolved with TCAS RA action by one of the aircraft involved but the TCAS equipment on board the other aircraft appeared to have malfunctioned and did not display any traffic information or generate an RA. The complex pattern of air routes in the vicinity of the event was identified by the Investigation as a Safety Issue requiring resolution by the ANSP and the response subsequently received was assessed as satisfactory.

guid: https://skybrary.aero/accidents-and-incidents/a332-a332-en-route-near-adelaide-south-australia-2013 uri: https://skybrary.aero/accidents-and-incidents/a332-a332-en-route-near-adelaide-south-australia-2013 title: A310, Ponta Delgada Azores Portugal, 2013 link: https://skybrary.aero/accidents-and-incidents/a310-ponta-delgada-azores-portugal-2013 description:

On 2 March 2013, the crew of an Airbus A310 mishandled a night tailwind touchdown at Ponta Delgada after a stabilised ILS approach had been flown and, after an initial bounce, the pitch was increased significantly and the main landing gear was fully compressed during the subsequent touchdown resulting in a tail strike and substantial related structural damage. The mishandling was attributed to deviation from the recommended 'light bounce' recovery technique. The absence of an instrument approach to the reciprocal (into wind) direction of the runway was noted and a recommendation that an RNAV procedure be made available was made.

guid: https://skybrary.aero/accidents-and-incidents/a310-ponta-delgada-azores-portugal-2013 uri: https://skybrary.aero/accidents-and-incidents/a310-ponta-delgada-azores-portugal-2013 title: Vehicles / B722, Hamilton ON Canada, 2013 link: https://skybrary.aero/accidents-and-incidents/vehicles-b722-hamilton-canada-2013 description:

On 19 March 2013 a Boeing 727 freighter was cleared to take off on a runway occupied by two snow clearance vehicles. The subsequent cancellation of the take off clearance was not received but a successful high speed rejected take off was accomplished on sight of the vehicles before their position was reached. The Investigation attributed the occurrence to the controller's failure to 'notice' the runway blocked indicator on his display and to his non-standard use of R/T communications. The late sighting of the vehicles by the aircraft crew was due to the elevated runway mid section.

guid: https://skybrary.aero/accidents-and-incidents/vehicles-b722-hamilton-canada-2013 uri: https://skybrary.aero/accidents-and-incidents/vehicles-b722-hamilton-canada-2013 title: CVLP, vicinity San Juan Puerto Rico, 2012 link: https://skybrary.aero/accidents-and-incidents/cvlp-vicinity-san-juan-puerto-rico-2012 description:

On 15 March 2012 the right hand engine exhaust of a Convair 440 freighter caught fire soon after take off and the fire was not contained within the exhaust duct or the zone covered by the fire protection system. After shutting this engine down, the subsequent Investigation concluded that the crew had lost control at low airspeed during an attempted turn back due to either an aerodynamic stall or a loss of directional control. It also found that the Operator involved was in serial violation of many regulatory requirements and that FAA oversight of the operation had been wholly ineffective.

guid: https://skybrary.aero/accidents-and-incidents/cvlp-vicinity-san-juan-puerto-rico-2012 uri: https://skybrary.aero/accidents-and-incidents/cvlp-vicinity-san-juan-puerto-rico-2012 title: B733, Yogyakarta Indonesia, 2011 link: https://skybrary.aero/accidents-and-incidents/b733-yogyakarta-indonesia-2011 description:

On 20 December 2011, the experienced Captain of a Sriwijaya Air Boeing 737-300 flew an unstabilised non-precision approach to a touchdown at Yogyakarta at excessive speed whilst accompanied by a very inexperienced First Officer. The aircraft overran the end of the 2200 metre-long wet runway by 75 metres . During the approach, the Captain 'noticed' several GPWS PULL UP Warnings but no action was taken. The Investigation attributed the accident entirely to the actions of the flight crew and found that there had been no alert calls from the First Officer in respect of the way the approach was flown.

guid: https://skybrary.aero/accidents-and-incidents/b733-yogyakarta-indonesia-2011 uri: https://skybrary.aero/accidents-and-incidents/b733-yogyakarta-indonesia-2011 title: A320, en-route Alpes-de-Haute-Provence France, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-alpes-de-haute-provence-france-2015 description:

On 24 March 2015, after waiting for the Captain to leave the flight deck and preventing his return, a Germanwings A320 First Officer put his aircraft into a continuous descent from FL380 into terrain killing all 150 occupants. Investigation concluded the motive was suicide, noted a history of mental illness dating from before qualification as a pilot and found that prior to the crash he had been experiencing mental disorder with psychotic symptoms which had not been detected through the applicable process for medical certification of pilots. Conflict between the principles of medical confidentiality and wider public interest was identified.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-alpes-de-haute-provence-france-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-alpes-de-haute-provence-france-2015 title: AT43, Madang Papua New Guinea, 2013 link: https://skybrary.aero/accidents-and-incidents/at43-madang-papua-new-guinea-2013 description:

On 19 October 2013, an ATR42 freighter departing Madang had to reject its takeoff when it was impossible to rotate and it ended up semi-submerged in a shallow creek beyond the airfield perimeter. The Investigation found that loading had been contrary to instructions and the aircraft had a centre of gravity outside the permitted range and was overweight. This was attributed to the aircraft operator s lack of adequate procedures for acceptance and loading of cargo. A lack of appreciation by all parties of the need to effectively mitigate runway overrun risk in the absence of a RESA was also highlighted.

guid: https://skybrary.aero/accidents-and-incidents/at43-madang-papua-new-guinea-2013 uri: https://skybrary.aero/accidents-and-incidents/at43-madang-papua-new-guinea-2013 title: AT76, vicinity Moranbah Queensland Australia, 2013 link: https://skybrary.aero/accidents-and-incidents/at76-vicinity-moranbah-queensland-australia-2013 description:

On 15 May 2013, an ATR 72-600 on a visual approach to Moranbah descended sufficiently low in order to avoid entering cloud that a number of TAWS Warnings were activated. All were a consequence of the descent to below 500 feet agl at a high rate of descent which appeared not to have been appreciated by the flight crew.

guid: https://skybrary.aero/accidents-and-incidents/at76-vicinity-moranbah-queensland-australia-2013 uri: https://skybrary.aero/accidents-and-incidents/at76-vicinity-moranbah-queensland-australia-2013 title: AT72, Shannon Ireland, 2014 link: https://skybrary.aero/accidents-and-incidents/at72-shannon-ireland-2014 description:

On 26 February 2014, an ATR 72-202 which had been substituted for the ATR42 which usually operated a series of night cargo flights was being marshalled out of its parking position with a new flight crew on board when the left wing was in collision with the structure of an adjacent hangar. The Investigation found that the aircraft type had not been changed on the applicable flight plan and ATC were consequently unaware that the aircraft had previously been parked in a position only approved for the use by the usual smaller aircraft type.

guid: https://skybrary.aero/accidents-and-incidents/at72-shannon-ireland-2014 uri: https://skybrary.aero/accidents-and-incidents/at72-shannon-ireland-2014 title: B744, Johannesburg South Africa, 2013 link: https://skybrary.aero/accidents-and-incidents/b744-johannesburg-south-africa-2013 description:

On 22 December 2013, a Boeing 747-400 taxiing for departure at Johannesburg at night with an augmented crew failed to follow its correctly-acknowledged taxi clearance and one wing hit a building resulting in substantial damage to both aircraft and building and a significant fuel leak. The aircraft occupants were all uninjured but four people in the building sustained minor injuries. The accident was attributed to crew error both in respect of an inadequate briefing and failure to monitor aircraft position using available charts and visual reference. Some minor contributory factors relating to the provision of airport lighting and signage were noted.

guid: https://skybrary.aero/accidents-and-incidents/b744-johannesburg-south-africa-2013 uri: https://skybrary.aero/accidents-and-incidents/b744-johannesburg-south-africa-2013 title: JS32, Torsby Sweden, 2014 link: https://skybrary.aero/accidents-and-incidents/js32-torsby-sweden-2014 description:

On 31 January 2014, an Estonian-operated BAE Jetstream 32 being used under wet lease to fulfil a government-funded Swedish domestic air service requirement landed long at night and overran the end of the runway. The Investigation concluded that an unstabilised approach had been followed by a late touchdown at excessive speed and that the systemic context for the occurrence had been a complete failure of the aircraft operator to address operational safety at anything like the level appropriate to a commercial operation. Failure of the responsible State Safety Regulator to detect and act on this situation was also noted.

guid: https://skybrary.aero/accidents-and-incidents/js32-torsby-sweden-2014 uri: https://skybrary.aero/accidents-and-incidents/js32-torsby-sweden-2014 title: B735, Jos Nigeria, 2010 link: https://skybrary.aero/accidents-and-incidents/b735-jos-nigeria-2010 description:

On 24 August 2010, a Boeing 737-500 made an uncontrolled touchdown on a wet runway at Jos in daylight after the approach was continued despite not being stabilised. A lateral runway excursion onto the grass occurred before the aircraft regained the runway centreline and stopped two-thirds of the way along the 3000 metre-long runway. Substantial damage was caused to the aircraft but none of the occupants were injured. The aircraft commander was the Operator's 737 Fleet Captain and the Investigation concluded that the length of time he had been on duty had led to fatigue which had impaired his performance.

guid: https://skybrary.aero/accidents-and-incidents/b735-jos-nigeria-2010 uri: https://skybrary.aero/accidents-and-incidents/b735-jos-nigeria-2010 title: C525 / P180, south west of Sion Switzerland, 2012 link: https://skybrary.aero/accidents-and-incidents/c525-p180-south-west-sion-switzerland-2012 description:

On 22 March 2013, a Cessna 525 inbound to Sion on a VFR clearance was flown into conflict with an IFR Piaggio P180 departing the same airport in compliance with its clearance and the prescribed separation between the two aircraft was lost in the vicinity of FL140. The Investigation concluded that an inappropriate ATC tactic had been employed in an attempt to achieve separation and recommended the development of a new procedure to better facilitate separation between IFR and VFR traffic in the airspace where the conflict occurred.

guid: https://skybrary.aero/accidents-and-incidents/c525-p180-south-west-sion-switzerland-2012 uri: https://skybrary.aero/accidents-and-incidents/c525-p180-south-west-sion-switzerland-2012 title: CRJ2 / A320, vicinity Port Elizabeth South Africa, 2014 link: https://skybrary.aero/accidents-and-incidents/crj2-a320-vicinity-port-elizabeth-south-africa-2014 description:

On 10 July 2014, Bombardier CRJ-200 instructed to go around at Port Elizabeth by ATC came into close proximity with an A320 which had just taken off from the same runway and initiated avoiding action to increase separation. The Investigation concluded that the TWR controller had failed to effectively monitor the progress of the aircraft on final approach before issuing a take off clearance to the A320.

guid: https://skybrary.aero/accidents-and-incidents/crj2-a320-vicinity-port-elizabeth-south-africa-2014 uri: https://skybrary.aero/accidents-and-incidents/crj2-a320-vicinity-port-elizabeth-south-africa-2014 title: AT75, vicinity Cork Ireland, 2014 link: https://skybrary.aero/accidents-and-incidents/at75-vicinity-cork-ireland-2014 description:

On 2 January 2014, the crew of an ATR 72-212A lost forward visibility due to the accumulation of a thick layer of salt deposits on the windshield whilst the aircraft was being radar positioned to an approach at Cork on a track which took it close to and at times over the sea in the presence of strong onshore winds. The Investigation concluded that the prevailing strong winds over and near to the sea in relatively dry air with little visible moisture present had been conducive to high concentrations of salt particles at low levels.

guid: https://skybrary.aero/accidents-and-incidents/at75-vicinity-cork-ireland-2014 uri: https://skybrary.aero/accidents-and-incidents/at75-vicinity-cork-ireland-2014 title: MD82, Copenhagen Denmark, 2013 link: https://skybrary.aero/accidents-and-incidents/md82-copenhagen-denmark-2013 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/md82-copenhagen-denmark-2013 uri: https://skybrary.aero/accidents-and-incidents/md82-copenhagen-denmark-2013 title: SS2, Manoeuvring West Mojave Desert CA USA, 2014 link: https://skybrary.aero/accidents-and-incidents/ss2-manoeuvring-west-mojave-desert-ca-usa-2014 description:

On 31 October 2014, the crew of a SpaceShip Two suborbital rocket, being operated by Scaled Composites on a routine test flight, broke up in flight after the co-pilot prematurely operated a release mechanism for an aerodynamic braking system which then deployed without further crew intervention. The NTSB Investigation concluded that whilst the co-pilot's error was the immediate cause of the accident, the context for it was the operator's failure to adequately understand and mitigate risk, and weakness in the FAA oversight process which led to inappropriate waivers from the normal requirements for issue of an experimental permit to fly.

guid: https://skybrary.aero/accidents-and-incidents/ss2-manoeuvring-west-mojave-desert-ca-usa-2014 uri: https://skybrary.aero/accidents-and-incidents/ss2-manoeuvring-west-mojave-desert-ca-usa-2014 title: B763, Montreal Quebec Canada, 2013 link: https://skybrary.aero/accidents-and-incidents/b763-montreal-quebec-canada-2013 description:

On 4 November 2013, smoke began to appear in the passenger cabin of a Boeing 767 which had just begun disembarking its 243 passengers via an airbridge after arriving at Montreal. The source was found to be a belt loader in position at the rear of the aircraft which had caught fire. Emergency evacuation using the airbridge only was ordered by the aircraft commander but cabin conditions led to other exits being used too. The fire was caused by a fuel leak and absence of an emergency stop button had prevented it being extinguished until the airport fire service arrived.

guid: https://skybrary.aero/accidents-and-incidents/b763-montreal-quebec-canada-2013 uri: https://skybrary.aero/accidents-and-incidents/b763-montreal-quebec-canada-2013 title: B738, en-route, near Lugano Switzerland, 2012 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-lugano-switzerland-2012 description:

On 4 April 2012, the cabin pressurisation controller (CPC) on a Boeing 737-800 failed during the climb passing FL305 and automatic transfer to the alternate CPC was followed by a loss of cabin pressure control and rapid depressurisation because it had been inadvertently installed with the shipping plug fitted. An emergency descent and diversion followed. The subsequent Investigation attributed the failure to remove the shipping plug to procedural human error and the poor visibility of the installed plug. It was also found that the pressurisation system ground test after CPC installation was not suitable to detect the error.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-lugano-switzerland-2012 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-lugano-switzerland-2012 title: A321, Incheon South Korea, 2013 link: https://skybrary.aero/accidents-and-incidents/a321-incheon-south-korea-2013 description:

On 16 April 2013, an A321 sustained significant damage during a tail strike during a bounced landing which followed loss of airspeed and an increase in sink rate shortly before touchdown after an otherwise stabilised approach. The Investigation attributed the tail strike to a failure to follow the recommended bounced landing response and noted the inadequate training provided by Asiana for bounced landing recovery.

guid: https://skybrary.aero/accidents-and-incidents/a321-incheon-south-korea-2013 uri: https://skybrary.aero/accidents-and-incidents/a321-incheon-south-korea-2013 title: E55P, Blackbushe UK, 2015 link: https://skybrary.aero/accidents-and-incidents/e55p-blackbushe-uk-2015 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/e55p-blackbushe-uk-2015 uri: https://skybrary.aero/accidents-and-incidents/e55p-blackbushe-uk-2015 title: A320, vicinity Auckland New Zealand, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-auckland-new-zealand-2012 description:

On 20 June 2012, the right V2500 engine compressor of an Airbus A320 suddenly stalled on final approach. The crew reduced the right engine thrust to flight idle and completed the planned landing uneventfully. Extensive engine damage was subsequently discovered and the investigation conducted attributed this to continued use of the engine in accordance with required maintenance procedures following bird ingestion during the previous sector. No changes to procedures for deferral of a post bird strike boroscope inspection for one further flight in normal service were proposed but it was noted that awareness of operations under temporary alleviations was important.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-auckland-new-zealand-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-auckland-new-zealand-2012 title: C56X, Port Harcourt Nigeria, 2013 link: https://skybrary.aero/accidents-and-incidents/c56x-port-harcourt-nigeria-2013 description:

On 14 July 2011, the crew of a Cessna Citation intentionally continued a night ILS approach at Port Harcourt below the applicable DA without having any visual reference with the runway and a crash landing and lateral runway excursion which severely damaged the aircraft followed. The Investigation did not establish any reason for the violation of minima but noted the complications which had arisen in respect of CRM because of two-Captain flight crew. Absence of two-way radio communications between the fire trucks and both ATC and the AFS Watch Room was noted to have delayed discovery of the crashed aircraft.

guid: https://skybrary.aero/accidents-and-incidents/c56x-port-harcourt-nigeria-2013 uri: https://skybrary.aero/accidents-and-incidents/c56x-port-harcourt-nigeria-2013 title: DC3, vicinity Yellowknife Canada, 2013 link: https://skybrary.aero/accidents-and-incidents/dc3-vicinity-yellowknife-canada-2013 description:

On 19 August 2013, a fire occurred in the right engine of a Douglas DC3-C on take off from Yellowknife. After engine shutdown, a right hand circuit was made in an attempt to land back on another runway but trees were struck and the aircraft crash-landed south of it. Emergency evacuation was successful. The Investigation found that a pre-existing cylinder fatigue crack had caused the engine failure/fire and that the propeller feathering pump had malfunctioned. It was found that an overweight take off had occurred and that various unsafe practices had persisted despite the regulatory approval of the Operator's SMS.

guid: https://skybrary.aero/accidents-and-incidents/dc3-vicinity-yellowknife-canada-2013 uri: https://skybrary.aero/accidents-and-incidents/dc3-vicinity-yellowknife-canada-2013 title: B738, en-route, south south west of Brisbane Australia, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-south-west-brisbane-australia-2013 description:

On 25 February 2013, a Boeing 737-800 about to commence descent from FL390 began to climb. By the time the crew recognised the cause and began to correct the deviation - their unintended selection of a inappropriate mode - the cleared level had been exceeded by 900 feet. During the recovery, a deviation from track occurred because the crew believed the autopilot had been re-engaged when it had not. The Investigation noted the failure to detect either error until flight path deviation occurred and attributed this to non-compliance with various operator procedures related to checking and confirmation of crew actions.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-south-west-brisbane-australia-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-south-west-brisbane-australia-2013 title: B734, Zurich Switzerland, 2013 link: https://skybrary.aero/accidents-and-incidents/b734-zurich-switzerland-2013 description:

On 11 October 2013, the commander of a Boeing 737-400 taxiing on wet taxiways at night after landing at Zurich became uncertain of his position in relation to the clearance received and when he attempted to manoeuvre the aircraft off the taxiway centreline onto what was believed to be adjacent paved surface, it became bogged down in soft ground. The Investigation considered the direct cause of the taxiway excursion was not following the green centreline lights but it recommended improvements in the provision of clear and consistent taxi instructions and in taxiway designations in the area of the event.

guid: https://skybrary.aero/accidents-and-incidents/b734-zurich-switzerland-2013 uri: https://skybrary.aero/accidents-and-incidents/b734-zurich-switzerland-2013 title: B190, vicinity Bebi south eastern Nigeria, 2008 link: https://skybrary.aero/accidents-and-incidents/b190-vicinity-bebi-south-eastern-nigeria-2008 description:

On 15 March 2008, a Beech 1900D on a non-revenue positioning flight to a private airstrip in mountainous terrain flown by an inadequately-briefed crew without sufficient guidance or previous relevant experience impacted terrain under power whilst trying to locate the destination visually after failing to respond to a series of GPWS Alerts and a final PULL UP Warning. Whilst attributing the accident to the crew, the Investigation also found a range of contributory deficiencies in respect of the Operator, official charting and ATS provision and additional deficiencies in the conduct of the unsuccessful SAR activity after the aircraft became overdue.

guid: https://skybrary.aero/accidents-and-incidents/b190-vicinity-bebi-south-eastern-nigeria-2008 uri: https://skybrary.aero/accidents-and-incidents/b190-vicinity-bebi-south-eastern-nigeria-2008 title: HUNT, manoeuvring, vicinity Shoreham UK, 2015 link: https://skybrary.aero/accidents-and-incidents/hunt-manoeuvring-vicinity-shoreham-uk-2015 description:

On 22 August 2015 the pilot of a civil-operated Hawker Hunter carrying out a flying display sequence at Shoreham failed to complete a loop and partial roll manoeuvre and the aircraft crashed into road traffic unrelated to the airshow and exploded causing multiple third party fatalities and injuries. The Investigation found that the pilot had failed to enter the manoeuvre correctly and then failed to abandon it when it should have been evident that it could not be completed. It was concluded that the wider context for the accident was inadequate regulatory oversight of UK civil air display flying risk management.

guid: https://skybrary.aero/accidents-and-incidents/hunt-manoeuvring-vicinity-shoreham-uk-2015 uri: https://skybrary.aero/accidents-and-incidents/hunt-manoeuvring-vicinity-shoreham-uk-2015 title: B772, Las Vegas NV USA, 2015 link: https://skybrary.aero/accidents-and-incidents/b772-las-vegas-nv-usa-2015 description:

On 8 September 2015, a catastrophic uncontained failure of a GE90-85B engine on a Boeing 777-200 taking off from Las Vegas was immediately followed by a rejected takeoff. A fuel-fed fire took hold and a successful emergency evacuation was completed. The Investigation traced the failure to a fatigue crack in the high pressure compressor well within the manufacturer s estimated crack initiation life and appropriate revisions to risk management have followed. The main operational risk concern of the Investigation was the absence of any procedural distinction in crew emergency responses for engine fires beginning in the air or on the ground.

guid: https://skybrary.aero/accidents-and-incidents/b772-las-vegas-nv-usa-2015 uri: https://skybrary.aero/accidents-and-incidents/b772-las-vegas-nv-usa-2015 title: A320 / B739, Yogyakarta Indonesia, 2013 link: https://skybrary.aero/accidents-and-incidents/a320-b739-yogyakarta-indonesia-2013 description:

On 20 November 2013, an A320 misunderstood its taxi out clearance at Yogyakarta and began to enter the same runway on which a Boeing 737, which had a valid landing clearance but was not on TWR frequency, was about to touch down from an approach in the other direction of use. On seeing the A320, which had stopped with the nose of the aircraft protruding onto the runway, the 737 applied maximum manual braking and stopped just before reaching the A320. The Investigation faulted ATC and airport procedures as well as the A320 crew for contributing to the risk created.

guid: https://skybrary.aero/accidents-and-incidents/a320-b739-yogyakarta-indonesia-2013 uri: https://skybrary.aero/accidents-and-incidents/a320-b739-yogyakarta-indonesia-2013 title: B190 / B737, Calgary Canada, 2014 link: https://skybrary.aero/accidents-and-incidents/b190-b737-calgary-canada-2014 description:

On 29 March 2014, a Beech 1900D being taxied by maintenance personnel at Calgary entered the active runway without clearance in good visibility at night as a Boeing 737-700 was taking off. The 737 passed safely overhead. The Investigation found that the taxiing aircraft had taken a route completely contrary to the accepted clearance and that the engineer on control of the aircraft had not received any relevant training. Although the airport had ASDE in operation, a transponder code was not issued to the taxiing aircraft as required and stop bar crossing detection was not enabled at the time.

guid: https://skybrary.aero/accidents-and-incidents/b190-b737-calgary-canada-2014 uri: https://skybrary.aero/accidents-and-incidents/b190-b737-calgary-canada-2014 title: A332, vicinity Melbourne Australia, 2013 link: https://skybrary.aero/accidents-and-incidents/a332-vicinity-melbourne-australia-2013 description:

On 8 March 2013, the crew of a Qantas A330 descended below controlled airspace and to 600 feet agl when still 9nm from the landing runway at Melbourne in day VMC after mismanaging a visual approach flown with the AP engaged. An EGWS Terrain Alert was followed by an EGPWS PULL UP Warning and a full recovery manoeuvre was flown. The Investigation found degraded situational awareness had followed inappropriate use of Flight Management System

guid: https://skybrary.aero/accidents-and-incidents/a332-vicinity-melbourne-australia-2013 uri: https://skybrary.aero/accidents-and-incidents/a332-vicinity-melbourne-australia-2013 title: A320, vicinity Lyons Saint-Exupéry France, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-lyons-saint-exupery-france-2012 description:

On 11 April 2012, a Hermes Airlines A320 commanded by a Training Captain who was also in charge of Air Operations for the airline was supervising a trainee Captain on a night passenger flight. The aircraft failed to establish on the Lyons ILS and, in IMC, descended sufficiently to activate both MSAW and EGPWS 'PULL UP' warnings which eventually prompted recovery. The Investigation concluded that application of both normal and emergency procedures had been inadequate and had led to highly degraded situational awareness for both pilots. The context for this was assessed as poor operational management at the airline.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-lyons-saint-exupery-france-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-lyons-saint-exupery-france-2012 title: A332 MRTT, en-route, south eastern Black Sea, 2014 link: https://skybrary.aero/accidents-and-incidents/a332-mrtt-en-route-south-eastern-black-sea-2014 description:

On 9 February 2014, the Captain of a military variant of the Airbus A330 suddenly lost control during the cruise on a passenger flight. A violent, initially negative 'g', pitch down occurred which reached 15800 fpm as the speed rose to Mach 0.9. In the absence of any effective crew intervention, recovery was achieved entirely by the aircraft Flight Envelope Protection System. The Investigation found that the upset had occurred when the Captain moved his seat forward causing its left arm rest to contact the personal camera he had placed behind the sidestick, forcing the latter fully forward.

guid: https://skybrary.aero/accidents-and-incidents/a332-mrtt-en-route-south-eastern-black-sea-2014 uri: https://skybrary.aero/accidents-and-incidents/a332-mrtt-en-route-south-eastern-black-sea-2014 title: A321, vicinity Islamabad Pakistan, 2010 link: https://skybrary.aero/accidents-and-incidents/a321-vicinity-islamabad-pakistan-2010 description:

On 28 July 2010, the crew of an Airbus A321 lost contact with the runway at Islamabad during a visual circling approach and continued in IMC outside the protected area and flying into terrain after repeatedly ignoring EGPWS Terrain Alerts and PULL UP Warnings. The Investigation concluded that the Captain had pre-planned a non-standard circuit which had been continued into IMC and had then failed to maintain situational awareness, control the aircraft through correct FMU inputs or respond to multiple EGPWS Warnings. The inexperienced First Officer appeared unwilling to take control in the absence of corrective action by the Captain.

guid: https://skybrary.aero/accidents-and-incidents/a321-vicinity-islamabad-pakistan-2010 uri: https://skybrary.aero/accidents-and-incidents/a321-vicinity-islamabad-pakistan-2010 title: A321, en-route, near Pamplona Spain, 2014 link: https://skybrary.aero/accidents-and-incidents/a321-en-route-near-pamplona-spain-2014 description:

On 5 November 2014, the crew of an Airbus A321 temporarily lost control of their aircraft in the cruise and were unable to regain it until 4000 feet of altitude had been lost. An investigation into the causes is continuing but it is already known that blockage of more than one AOA probe resulted in unwanted activation of high AOA protection which could not be stopped by normal sidestick inputs until two of the three ADRs had been intentionally deactivated in order to put the flight control system into Alternate Law.

guid: https://skybrary.aero/accidents-and-incidents/a321-en-route-near-pamplona-spain-2014 uri: https://skybrary.aero/accidents-and-incidents/a321-en-route-near-pamplona-spain-2014 title: B753, London Gatwick UK, 2014 link: https://skybrary.aero/accidents-and-incidents/b753-london-gatwick-uk-2014 description:

On 31 October 2014, indications of a malfunction of the right over wing emergency exit slide on take off were followed during the return to land by the complete detachment of the slide and un-commanded but controllable roll. The Investigation found that a series of technical issues with the slide panel and carrier locking devices caused the slide carrier to deploy and the slide to unravel. Although an SB existed to address some of these issues, it had not been actioned on the aircraft. Two operational matters encountered during the Investigation were the subject of Safety Recommendations.

guid: https://skybrary.aero/accidents-and-incidents/b753-london-gatwick-uk-2014 uri: https://skybrary.aero/accidents-and-incidents/b753-london-gatwick-uk-2014 title: B752, vicinity Keflavik Iceland, 2013 link: https://skybrary.aero/accidents-and-incidents/b752-vicinity-keflavik-iceland-2013 description:

On 26 February 2013, the crew of a Boeing 752 temporarily lost full control of their aircraft on a night auto-ILS approach at Keflavik when an un-commanded roll occurred during flap deployment after an earlier partial loss of normal hydraulic system pressure. The origin of the upset was found to have been a latent fatigue failure of a roll spoiler component, the effect of which had only become significant in the absence of normal hydraulic pressure and had been initially masked by autopilot authority until this was exceeded during flap deployment.

guid: https://skybrary.aero/accidents-and-incidents/b752-vicinity-keflavik-iceland-2013 uri: https://skybrary.aero/accidents-and-incidents/b752-vicinity-keflavik-iceland-2013 title: B732, vicinity Islamabad Pakistan, 2012 link: https://skybrary.aero/accidents-and-incidents/b732-vicinity-islamabad-pakistan-2012 description:

On 20 April 2012, the crew of a Boeing 737-200 encountered negative wind shear during an ILS final approach at night in lMC and failed to respond with the appropriate recovery actions. The aircraft impacted the ground approximately 4 nm from the threshold of the intended landing runway. The Investigation attributed the accident to the decision to continue to destination in the presence of adverse convective weather and generally ineffective flight deck management and noted that neither pilot had received training specific to the semi-automated variant of the 200 series 737 being flown and had no comparable prior experience.

guid: https://skybrary.aero/accidents-and-incidents/b732-vicinity-islamabad-pakistan-2012 uri: https://skybrary.aero/accidents-and-incidents/b732-vicinity-islamabad-pakistan-2012 title: B738, Djalaluddin Indonesia, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-djalaluddin-indonesia-2013 description:

On 6 August 2013, a Boeing 737-800 encountered cows ahead on the runway after landing normally in daylight following an uneventful approach and was unable to avoid colliding with them at high speed and as a result departed the runway to the left. Parts of the airport perimeter fencing were found to have been either missing or inadequately maintained for a significant period prior to the accident despite the existence of an airport bird and animal hazard management plan. Corrective action was taken following the accident.

guid: https://skybrary.aero/accidents-and-incidents/b738-djalaluddin-indonesia-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-djalaluddin-indonesia-2013 title: B773, Paris CDG France, 2013 link: https://skybrary.aero/accidents-and-incidents/b773-paris-cdg-france-2013 description:

On 28 July 2013, with passengers still boarding an Air France Boeing 777-300, an abnormal 'burnt' smell was detected by the crew and then thin smoke appeared in the cabin. A MAYDAY was declared and the Captain made a PA telling the cabin crew to evacuate the passengers via the doors, only via the doors. The resulting evacuation process was confused but eventually completed. The Investigation attributed the confused evacuation to the way it had been ordered and established that a fault in the APU had caused the smoke and fumes which had the potential to be toxic.

guid: https://skybrary.aero/accidents-and-incidents/b773-paris-cdg-france-2013 uri: https://skybrary.aero/accidents-and-incidents/b773-paris-cdg-france-2013 title: B737, New York La Guardia USA, 2013 link: https://skybrary.aero/accidents-and-incidents/b737-new-york-la-guardia-usa-2013 description:

On 22 July 2013 the Captain of a Boeing 737-700 failed to go around when the aircraft was not stabilised on final approach at La Guardia and then took control from the First Officer three seconds before touchdown and made a very hard nose first touchdown which substantially damaged the aircraft. The Investigation concluded that the accident had been a consequence of the continued approach and the attempt to recover with a very late transfer of control instead of a go around as prescribed by the Operator. The aircraft was substantially damaged.

guid: https://skybrary.aero/accidents-and-incidents/b737-new-york-la-guardia-usa-2013 uri: https://skybrary.aero/accidents-and-incidents/b737-new-york-la-guardia-usa-2013 title: DH8A, vicinity Svolvær Norway, 2010 link: https://skybrary.aero/accidents-and-incidents/dh8a-vicinity-svolvaer-norway-2010 description:

On 2 December 2010, a DHC8-100 crew briefly lost control of their aircraft after encountering a microburst and came very close to both the sea surface and a stall when turning onto night visual final at Svolvær during an otherwise uneventful circling approach. After recovery from 83 feet agl, involving an unplanned change of control, an uneventful diversion to an alternate followed. Commencement of an investigation was delayed by failure to report the event at all initially, or fully. It was found that during loss of control, airspeed had dropped to 72 knots and rate of descent had exceeded 2,200 fpm.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-vicinity-svolvaer-norway-2010 uri: https://skybrary.aero/accidents-and-incidents/dh8a-vicinity-svolvaer-norway-2010 title: A332, Jakarta Indonesia, 2013 link: https://skybrary.aero/accidents-and-incidents/a332-jakarta-indonesia-2013 description:

On 13 December 2013, an Airbus A330 encountered very heavy rain below 100 feet agl just after the autopilot had been disconnected for landing off an ILS approach at Jakarta. The aircraft Commander, as pilot flying, lost visual reference but the monitoring First Officer did not. A go around was neither called nor flown and after drifting in the flare, the aircraft touched down with the right main landing gear on the grass and continued like this for 500 metres before regaining the runway. The Investigation noted that prevailing SOPs clearly required that a go around should have been flown.

guid: https://skybrary.aero/accidents-and-incidents/a332-jakarta-indonesia-2013 uri: https://skybrary.aero/accidents-and-incidents/a332-jakarta-indonesia-2013 title: A320, en-route Karimata Strait Indonesia, 2014 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-karimata-strait-indonesia-2014 description:

On 28 December 2014, an A320 crew took unapproved action in response to a repeating system caution shortly after levelling at FL320. The unexpected consequences degraded the flight control system and obliged manual control. Gross mishandling followed which led to a stall, descent at a high rate and sea surface impact with a 20º pitch attitude and a 50º angle of attack four minutes later. The Investigation noted the accident origin as a repetitive minor system fault but demonstrated that the subsequent loss of control followed a combination of explicitly inappropriate pilot action and the absence of appropriate pilot action.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-karimata-strait-indonesia-2014 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-karimata-strait-indonesia-2014 title: BN2P, Antigua East Caribbean Sea, 2012 link: https://skybrary.aero/accidents-and-incidents/bn2p-antigua-east-caribbean-sea-2012 description:

On 7 October 2012, a Britten-Norman BN2 Islander pilot lost control of their aircraft shortly after take off from Antigua when the right engine stopped due to the presence of water in the corresponding fuel tank. The Investigation found that heavy rain whilst the aircraft had been parked prior to flight had resulted in water entering the tank because of anomalies in the fuel tank filler neck and cap. The reason why the pilot had been unable to keep control of the aircraft was not explained but evidence of his performance under training and test suggested weakness in aircraft control.

guid: https://skybrary.aero/accidents-and-incidents/bn2p-antigua-east-caribbean-sea-2012 uri: https://skybrary.aero/accidents-and-incidents/bn2p-antigua-east-caribbean-sea-2012 title: EC35, Sollihøgda Norway, 2014 link: https://skybrary.aero/accidents-and-incidents/ec35-sollihogda-norway-2014 description:

On 14 January 2014, the experienced pilot of an EC 135 HEMS aircraft lost control as a result of a collision with unseen and difficult to visually detect power lines as it neared the site of a road accident at Sollihøgda to which it was responding which damaged the main rotor and led to it falling rapidly from about 80 feet agl. The helicopter was destroyed by the impact which killed two of the three occupants and seriously injured the third. The Investigation identified opportunities to improve both obstacle documentation / pilot proactive obstacle awareness and on site emergency communications.

guid: https://skybrary.aero/accidents-and-incidents/ec35-sollihogda-norway-2014 uri: https://skybrary.aero/accidents-and-incidents/ec35-sollihogda-norway-2014 title: E145, vicinity Manchester UK, 2001 link: https://skybrary.aero/accidents-and-incidents/e145-vicinity-manchester-uk-2001 description:

On 25 September 2001, an Embraer 145 in descent to Manchester sustained a low power lightning strike which was followed, within a few seconds, by the left engine stopping without failure annunciation. A successful single engine landing followed. The Investigation concluded that the cause of failure of the FADEC-controlled AE3007 engine (which has no surge recovery logic) was the aero-thermal effects of the strike to which all aircraft with relatively small diameter fuselages and close mounted engines are vulnerable. It was considered that there was a risk of simultaneous double engine flameout in such circumstances which was impossible to quantify.

guid: https://skybrary.aero/accidents-and-incidents/e145-vicinity-manchester-uk-2001 uri: https://skybrary.aero/accidents-and-incidents/e145-vicinity-manchester-uk-2001 title: GLF4, Le Castellet France, 2012 link: https://skybrary.aero/accidents-and-incidents/glf4-le-castellet-france-2012 description:

On 13 July 2012, a Gulfstream G-IV left the side of the runway at high speed during the landing roll at Le Castellet following a positioning flight after ineffective deceleration after the flight crew had forgotten to arm the ground spoilers. The Investigation found that pilot response to this situation had been followed by a loss of directional control, collision with obstructions and rapid onset of an intense fire. Contributory factors identified included poor procedural compliance by the pilots, their lack of training on a relevant new QRH procedure which Gulfstream had ineffectively communicated and ineffective FAA oversight of the operation.

guid: https://skybrary.aero/accidents-and-incidents/glf4-le-castellet-france-2012 uri: https://skybrary.aero/accidents-and-incidents/glf4-le-castellet-france-2012 title: SF34, Stornoway UK, 2015 link: https://skybrary.aero/accidents-and-incidents/sf34-stornoway-uk-2015 description:

On 2 January 2015, the commander of a Saab 340 suddenly lost directional control during a within-limits crosswind take off and the aircraft left the runway onto grass at approximately 80 knots. No call to reject the take off was made and no action was taken to shut down the engines until the aircraft had come to a stop in the soft ground with a collapsed nose gear and substantial damage to the propellers and lower forward fuselage. The Investigation concluded that the most likely explanation for the excursion was the absence of any rudder input as the aircraft accelerated.

guid: https://skybrary.aero/accidents-and-incidents/sf34-stornoway-uk-2015 uri: https://skybrary.aero/accidents-and-incidents/sf34-stornoway-uk-2015 title: A333, Kathmandu Nepal, 2015 link: https://skybrary.aero/accidents-and-incidents/a333-kathmandu-nepal-2015 description:

On 4 March 2015, the crew of a Turkish Airlines A333 continued an automatic non precision RNAV approach below the prescribed minimum descent altitude without having obtained any element of visual reference and when this was acquired a few seconds before the attempted landing, the aircraft was not aligned with the runway centreline and during a 2.7g low-pitch landing, the left main gear touched down on the grass. The aircraft then left the runway completely before stopping with a collapsed nose gear and sufficient damage to be assessed a hull loss. None of 235 occupants sustained serious injury.

guid: https://skybrary.aero/accidents-and-incidents/a333-kathmandu-nepal-2015 uri: https://skybrary.aero/accidents-and-incidents/a333-kathmandu-nepal-2015 title: DH8A / Z42, vicinity Sault Ste. Marie ON Canada, 2014 link: https://skybrary.aero/accidents-and-incidents/dh8a-z42-vicinity-sault-ste-marie-canada-2014 description:

On 3 September 2014 in Class 'E' airspace, a light aircraft carrying out a spin recovery exercise in day VMC came very close to a DHC8 climbing out of Sault Ste. Marie. Although the DH8 crew had seen the light aircraft ahead and above and temporarily levelled off, the light aircraft then began a rapid descending turn and a TCAS RA 'Descend' followed. It was judged that a turn would also be necessary but even with this, the two aircraft subsequently passed within 350-450 feet at the same altitude in opposite directions. The Investigation made no Safety Recommendations.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-z42-vicinity-sault-ste-marie-canada-2014 uri: https://skybrary.aero/accidents-and-incidents/dh8a-z42-vicinity-sault-ste-marie-canada-2014 title: SF34, en-route, northern North Sea UK, 2014 link: https://skybrary.aero/accidents-and-incidents/sf34-en-route-northern-north-sea-uk-2014 description:

On 3 October 2014, the crew of a Saab 340 in the cruise at FL150 in day IMC did not recognise that severe icing conditions had been encountered early enough to make a fully-controlled exit from them and although recovery from the subsequent stall was successful, it was achieved in a non-standard manner. The Investigation concluded that although both mountain wave effects and severe icing had contributed to the incident, the latter had been the main cause. Both crew understanding of airframe icing risk and supporting Operator and Manufacturer documentation on the subject were considered deficient.

guid: https://skybrary.aero/accidents-and-incidents/sf34-en-route-northern-north-sea-uk-2014 uri: https://skybrary.aero/accidents-and-incidents/sf34-en-route-northern-north-sea-uk-2014 title: C500, vicinity Santiago Spain, 2012 link: https://skybrary.aero/accidents-and-incidents/c500-vicinity-santiago-spain-2012 description:

On 2 August 2012, a Cessna 500 positioning back to base after completing an emergency medical team transfer operation earlier in the night crashed one mile short of the runway at Santiago in landing configuration after being cleared to make an ILS approach. The Investigation concluded that the approach was unstabilised, had been flown without following the ILS GS and that the crew had used DME distance from the VOR near the crash position rather than the ILS DME. Fog was present in and around the airport.

guid: https://skybrary.aero/accidents-and-incidents/c500-vicinity-santiago-spain-2012 uri: https://skybrary.aero/accidents-and-incidents/c500-vicinity-santiago-spain-2012 title: B733 / DH8D, Fort McMurray Canada, 2014 link: https://skybrary.aero/accidents-and-incidents/b733-dh8d-fort-mcmurray-canada-2014 description:

On 4 August 2014, a Boeing 737-300 making a day visual approach at Fort McMurray after receiving an ILS/DME clearance lined up on a recently-constructed parallel taxiway and its crew were only alerted to their error shortly before touchdown by the crew of a DHC8-400 which was taxiing along the same taxiway in the opposite direction. This resulted in a go around being commenced from 46 feet agl. The Investigation noted that both pilots had been looking out during the final stages of the approach and had ignored important SOPs including that for a mandatory go around from an unstable approach.

guid: https://skybrary.aero/accidents-and-incidents/b733-dh8d-fort-mcmurray-canada-2014 uri: https://skybrary.aero/accidents-and-incidents/b733-dh8d-fort-mcmurray-canada-2014 title: SF34, en-route, near Caltrauna Argentina, 2011 link: https://skybrary.aero/accidents-and-incidents/sf34-en-route-near-caltrauna-argentina-2011 description:

On 18 May 2011, a Saab 340 crew attempted to continue a climb to their intended cruising level in significant airframe icing conditions at night before belatedly abandoning the attempt and descending to a lower level but one where their aircraft was nevertheless still rapidly accumulating ice. They were unable to recover control after it stalled and a crash into terrain below followed. The Investigation attributed the accident to lack of crew understanding of the importance of both the detection of and timely and appropriate response to both significant rates of airframe ice accumulation and indications of an impending aerodynamic stall.

guid: https://skybrary.aero/accidents-and-incidents/sf34-en-route-near-caltrauna-argentina-2011 uri: https://skybrary.aero/accidents-and-incidents/sf34-en-route-near-caltrauna-argentina-2011 title: B772, Singapore, 2013 link: https://skybrary.aero/accidents-and-incidents/b772-singapore-2013 description:

On 19 December 2013, the left engine of a Boeing 777-200 taxiing onto its assigned parking gate after arrival at Singapore ingested an empty cargo container resulting in damage to the engine which was serious enough to require its subsequent removal and replacement. The Investigation found that the aircraft docking guidance system had been in use despite the presence of the ingested container and other obstructions within the clearly marked 'equipment restraint area' of the gate involved. The corresponding ground handling procedures were found to be deficient as were those for ensuring general ramp awareness of a 'live' gate.

guid: https://skybrary.aero/accidents-and-incidents/b772-singapore-2013 uri: https://skybrary.aero/accidents-and-incidents/b772-singapore-2013 title: B773, en route, northern Turkey, 2014 link: https://skybrary.aero/accidents-and-incidents/b773-en-route-northern-turkey-2014 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/b773-en-route-northern-turkey-2014 uri: https://skybrary.aero/accidents-and-incidents/b773-en-route-northern-turkey-2014 title: MA60, en route, west of Bima Indonesia, 2011 link: https://skybrary.aero/accidents-and-incidents/ma60-en-route-west-bima-indonesia-2011 description:

On 12 December 2011, the crew of a Xian MA60 delayed their response to an engine fire warning until the existence of a fire had been confirmed by visual inspection and then failed to follow the memory engine shutdown drill properly so that fire continued for considerably longer than it should have. The Investigation found that an improperly tightened fuel line coupling which had been getting slowly but progressively worse during earlier flights had caused the fire. It was also concluded that the pilots' delay in responding to the fire had prolonged risk exposure and jeopardised the safety of the flight.

guid: https://skybrary.aero/accidents-and-incidents/ma60-en-route-west-bima-indonesia-2011 uri: https://skybrary.aero/accidents-and-incidents/ma60-en-route-west-bima-indonesia-2011 title: A139 / A30B, Ottawa Canada, 2014 link: https://skybrary.aero/accidents-and-incidents/a139-a30b-ottawa-canada-2014 description:

On 5 June 2014, an AW139 about to depart from its Ottawa home base on a positioning flight exceeded its clearance limit and began to hover taxi towards the main runway as an A300 was about to touch down on it. The TWR controller immediately instructed the helicopter to stop which it did, just clear of the runway. The A300 reached taxi speed just prior to the intersection. The Investigation attributed the error to a combination of distraction and expectancy and noted that the AW139 pilot had not checked actual or imminent runway occupancy prior to passing his clearance limit.

guid: https://skybrary.aero/accidents-and-incidents/a139-a30b-ottawa-canada-2014 uri: https://skybrary.aero/accidents-and-incidents/a139-a30b-ottawa-canada-2014 title: E170, Nuremberg Germany, 2013 link: https://skybrary.aero/accidents-and-incidents/e170-nuremberg-germany-2013 description:

On 13 March 2013, smoke and fumes were immediately evident when the cable of an external GPU was connected to an ERJ170 aircraft on arrival after flight with passengers still on board. A precautionary rapid disembarkation was conducted. The Investigation found that a short circuit had caused extensive heat damage to the internal part of the aircraft GPU receptacle and minor damage to the surrounding structure and that the short circuit had occurred due to metallic FOD lodged within the external connecting box of aircraft GPU receptacle.

guid: https://skybrary.aero/accidents-and-incidents/e170-nuremberg-germany-2013 uri: https://skybrary.aero/accidents-and-incidents/e170-nuremberg-germany-2013 title: DH8D / B737, Winnipeg Canada, 2014 link: https://skybrary.aero/accidents-and-incidents/dh8d-b737-winnipeg-canada-2014 description:

On 4 August 2014, the crew of a DHC8-400 departing Winnipeg continued beyond the holding point to which they had been cleared to taxi as a B737-700 was about to land. ATC observed the daylight incursion visually and instructed the approaching aircraft to go around as the DHC8 stopped within the runway protected area but clear of the actual runway. The Investigation found that the surface marking of the holding point which had been crossed was significantly degraded and noted the daily airport inspections had failed to identify this.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-b737-winnipeg-canada-2014 uri: https://skybrary.aero/accidents-and-incidents/dh8d-b737-winnipeg-canada-2014 title: A320, vicinity Abu Dhabi UAE, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-abu-dhabi-uae-2012 description:

On 16 November 2012, Captain of an A320 positioning for approach to Abu Dhabi at night became incapacitated due to a stroke. The First Officer took over control and declared a MAYDAY to ATC. The subsequent approach and landing were uneventful but since the First Officer was not authorised to taxi the aircraft, it was towed to the gate for passenger disembarkation. The investigation found that the Captain had an undiagnosed medical condition which predisposed him towards the formation of blood clots in arteries and veins.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-abu-dhabi-uae-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-abu-dhabi-uae-2012 title: B738, Mangalore India, 2012 link: https://skybrary.aero/accidents-and-incidents/b738-mangalore-india-2012 description:

On 14 August 2012, a Boeing 737-800 crew continued a previously stable ILS Cat 1 approach below the prescribed MDA without having acquired the prescribed visual reference. The aircraft was then damaged by a high rate of descent at the initial touchdown in the undershoot in fog. The occurrence was not reported by either the crew or the attending licensed engineer who discovered consequent damage to the aircraft. Dense fog had prevented ATC visual awareness. The Investigation attributed the undershoot to violation of minima and to both pilots looking out for visual reference leaving the flight instruments unmonitored.

guid: https://skybrary.aero/accidents-and-incidents/b738-mangalore-india-2012 uri: https://skybrary.aero/accidents-and-incidents/b738-mangalore-india-2012 title: A320, en route, north of Marseilles France, 2013 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-marseilles-france-2013 description:

On 12 September 2013, pressurisation control failed in an A320 after a bleed air fault occurred following dispatch with one of the two pneumatic systems deactivated under MEL provisions. The Investigation found that the cause of the in-flight failure was addressed by an optional SB not yet incorporated. Also, relevant crew response SOPs lacking clarity and a delay in provision of a revised MEL procedure meant that use of the single system had not been optimal and after a necessary progressive descent to FL100 was delayed by inadequate ATC response, and ATC failure to respond to a PAN call required it to be upgraded to MAYDAY.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-marseilles-france-2013 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-marseilles-france-2013 title: A346, en route, eastern Indian Ocean, 2013 link: https://skybrary.aero/accidents-and-incidents/a346-en-route-eastern-indian-ocean-2013 description:

On 3 February 2013, an Airbus A340 crew in the cruise in equatorial latitudes at FL350 in IMC failed to use their weather radar properly and entered an area of ice crystal icing outside the prevailing icing envelope. A short period of unreliable airspeed indications on displays dependent on the left side pitot probes followed with a brief excursion above FL350 and reversion to Alternate Law. Excessive vibration on the left engine then began and a diversion was made. The engine remained in use and was subsequently found undamaged with the fault attributed to ice/water ingress due to seal failure.

guid: https://skybrary.aero/accidents-and-incidents/a346-en-route-eastern-indian-ocean-2013 uri: https://skybrary.aero/accidents-and-incidents/a346-en-route-eastern-indian-ocean-2013 title: A320/B738, vicinity Delhi India, 2013 link: https://skybrary.aero/accidents-and-incidents/a320b738-vicinity-delhi-india-2013 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a320b738-vicinity-delhi-india-2013 uri: https://skybrary.aero/accidents-and-incidents/a320b738-vicinity-delhi-india-2013 title: B738 / C172, en route, near Falsterbo Sweden, 2014 link: https://skybrary.aero/accidents-and-incidents/b738-c172-en-route-near-falsterbo-sweden-2014 description:

On 20 July 2014, the pilot of a VFR Cessna 172 became distracted and entered the Class 'C' controlled airspace of two successive TMAs without clearance. In the second one he was overtaken by a Boeing 738 inbound to Copenhagen with less than 90 metres separation. The 738 crew reported a late sighting of the 172 and seemingly assessed that avoiding action was unnecessary. Although the 172 had a Mode C-capable transponder, it was not transmitting altitude prior to the incident and the Investigation noted that this had invalidated preventive ATC and TCAS safety barriers and compromised flight safety.

guid: https://skybrary.aero/accidents-and-incidents/b738-c172-en-route-near-falsterbo-sweden-2014 uri: https://skybrary.aero/accidents-and-incidents/b738-c172-en-route-near-falsterbo-sweden-2014 title: A388, en-route, northern Afghanistan, 2014 link: https://skybrary.aero/accidents-and-incidents/a388-en-route-northern-afghanistan-2014 description:

On 5 January 2014, an Airbus A380-800 en route to Singapore at night made an emergency descent and diversion to Baku after a loss of cabin pressure without further event. The Investigation attributed the pressure loss to a fatigue crack in a door skin which was initiated due to a design issue with door Cover Plates, which had not been detected when the Cover Plate was replaced with an improved one eighteen months earlier. Safety Issues related to cabin crew use of emergency oxygen and diversions to aerodromes with a fire category less than that normally required were also identified.

guid: https://skybrary.aero/accidents-and-incidents/a388-en-route-northern-afghanistan-2014 uri: https://skybrary.aero/accidents-and-incidents/a388-en-route-northern-afghanistan-2014 title: A320 / B738, vicinity Dubai UAE, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-dubai-uae-2012 description:

On 22 April 2012, an Airbus A320 and a Boeing 737 came into close proximity near Dubai whilst on the same ATC frequency and correctly following their ATC clearances shortly after they had departed at night from Sharjah and Dubai respectively. The Investigation found that correct response by both aircraft to coordinated TCAS RAs eliminated any risk of collision. The fact that the controller involved had only just taken over the radar position involved and was only working the two aircraft in conflict was noted, as was the absence of STCA at the unit due to set up difficulties.

guid: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-dubai-uae-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-dubai-uae-2012 title: A320, Basel-Mulhouse-Freiburg France, 2014 link: https://skybrary.aero/accidents-and-incidents/a320-basel-mulhouse-freiburg-france-2014 description:

On 6 October 2014, an A320 crew requested, accepted and commenced an intersection takeoff at Basel using reduced thrust performance data based on the originally anticipated full length takeoff which would have given 65% more TODA. Recognition of the error and application of TOGA allowed the aircraft to get airborne just before the runway end but the Investigation found that a rejected take off from high speed would have resulted in an overrun and noted that despite changes to crew procedures after a similar event involving the same operator a year earlier, the relevant procedures were still conducive to error.

guid: https://skybrary.aero/accidents-and-incidents/a320-basel-mulhouse-freiburg-france-2014 uri: https://skybrary.aero/accidents-and-incidents/a320-basel-mulhouse-freiburg-france-2014 title: DH8C, vicinity Abu Dhabi UAE, 2012 link: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-abu-dhabi-uae-2012 description:

On 9 September 2012, the crew of a DHC8-300 climbing out of Abu Dhabi declared a PAN and returned after visual evidence of the right engine overheating were seen from the passenger cabin. The Investigation found that the observed signs of engine distress were due to hot gas exiting through the cavity left by non-replacement of one of the two sets of igniters on the engine after a pressure wash carried out overnight prior to the flight and that the left engine was similarly affected. The context for the error was identified as a dysfunctional maintenance organisation at the Operator.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-abu-dhabi-uae-2012 uri: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-abu-dhabi-uae-2012 title: GLF3, Biggin Hill UK, 2014 link: https://skybrary.aero/accidents-and-incidents/glf3-biggin-hill-uk-2014 description:

On 24 November 2014, the crew of a privately-operated Gulfstream III carrying five passengers inadvertently commenced take off at night in poor visibility when aligned with the runway edge instead of the runway centreline. When the aircraft partially exited the paved surface, the take-off was rejected but not before the aircraft had sustained substantial damage which put it beyond economic repair. The Investigation found that chart and AIP information on the taxiway/runway transition made when lining up was conducive to error and that environmental cues, indicating the aircraft was in the wrong place to begin take-off, were weak.

guid: https://skybrary.aero/accidents-and-incidents/glf3-biggin-hill-uk-2014 uri: https://skybrary.aero/accidents-and-incidents/glf3-biggin-hill-uk-2014 title: E190, Oslo Norway, 2010 link: https://skybrary.aero/accidents-and-incidents/e190-oslo-norway-2010 description:

On 23 October 2010, an Embraer 190 commenced its night rolling takeoff from runway 01L at Oslo with the aircraft aligned with left runway edge lights instead of the lit centreline before correcting to the runway centreline and completing the takeoff and flight to destination. Engine damage caused by ingestion of broken edge light fittings, which was sufficient to require replacement of one engine before the next flight, was not discovered until after completion of an otherwise uneventful flight. Tyre damage requiring wheel replacement was also sustained. The Investigation concluded that inadequate CRM had been a Contributing Factor.

guid: https://skybrary.aero/accidents-and-incidents/e190-oslo-norway-2010 uri: https://skybrary.aero/accidents-and-incidents/e190-oslo-norway-2010 title: B738, vicinity Eindhoven Netherlands, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-eindhoven-netherlands-2013 description:

On 31 May 2013, a Boeing 737-800 (EI-ENL) being operated by Ryanair on a scheduled international passenger flight from Palma del Mallorca to Eindhoven as FR3531 was established on the ILS LOC in day IMC with the AP and A/T engaged and APP mode selected but above the GS, when the aircraft suddenly pitched up and stick shaker activation occurred. After a sudden loss of airspeed, the crew recovered control manually and the subsequent approach was completed without further event.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-eindhoven-netherlands-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-eindhoven-netherlands-2013 title: A320 / GLID, vicinity Memmingen Germany, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-glid-vicinity-memmingen-germany-2015 description:

On 6 April 2015, the crew of an A320 under radar control in Class E airspace and approaching 4000 feet made a very late sighting of a glider being flown by a student pilot which appeared ahead at a similar altitude. The glider pilot reported having seen a 'cone of light' coming towards him. Both aircraft took avoiding action as practicable and passed within a recorded 450 metres with the A320 passing an estimated 250 feet over the glider. The glider was not fitted with a transponder and was not required to be, and the controller had only secondary radar.

guid: https://skybrary.aero/accidents-and-incidents/a320-glid-vicinity-memmingen-germany-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-glid-vicinity-memmingen-germany-2015 title: SW4, Sanikiluaq Nunavut Canada, 2012 link: https://skybrary.aero/accidents-and-incidents/sw4-sanikiluaq-nunavut-canada-2012 description:

On 22 December 2012, the crew of a Swearingen SA227 attempting a landing, following an unstabilised non-precision approach at Sanikiluaq at night with questionable alternate availability in marginal weather conditions, ignored GPWS PULL UP Warnings, then failed in their attempt to transition into a low go around and the aircraft crashed into terrain beyond the runway. One occupant – an unrestrained infant – was killed and the aircraft was destroyed. The Investigation faulted crew performance, the operator and the regulator and reiterated that lap-held infants were vulnerable in crash impacts.

guid: https://skybrary.aero/accidents-and-incidents/sw4-sanikiluaq-nunavut-canada-2012 uri: https://skybrary.aero/accidents-and-incidents/sw4-sanikiluaq-nunavut-canada-2012 title: EC25, vicinity Bergen Norway, 2016 link: https://skybrary.aero/accidents-and-incidents/ec25-vicinity-bergen-norway-2016 description:

On 29 April 2016, an Airbus EC225 Super Puma main rotor detached without warning en-route to Bergen. Control was lost and it crashed and was destroyed. Rotor detachment was attributed to undetected development of metal fatigue in the same gearbox component which caused an identical 2009 accident to a variant of the same helicopter type. Despite this previous accident, the failure mode involved had not been properly understood or anticipated. The investigation identifies significant lessons to be learned related to gearbox design, risk assessment, fatigue evaluation, gearbox condition monitoring, type certification and continued airworthiness, which may also be valid for other helicopter types.

guid: https://skybrary.aero/accidents-and-incidents/ec25-vicinity-bergen-norway-2016 uri: https://skybrary.aero/accidents-and-incidents/ec25-vicinity-bergen-norway-2016 title: C500, vicinity Wiley Post Airport, Oklahoma City OK USA, 2008 link: https://skybrary.aero/accidents-and-incidents/c500-vicinity-wiley-post-airport-oklahoma-city-ok-usa-2008 description:

On 4 August 2008, a Cessna 500 on a business charter flight encountered a flock of very large birds shortly after take off from a small Oklahoma City airport. Wing damage from at least one bird collision with a force significantly greater than covered by the applicable certification requirements made it impossible for the pilot to retain control of the aircraft. Terrain impact followed. Both engines also ingested a bird. The Investigation noted that neither pilot nor aircraft operator were approved to operate commercial charter flights but concluded that this was not directly connected to the loss of the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/c500-vicinity-wiley-post-airport-oklahoma-city-ok-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/c500-vicinity-wiley-post-airport-oklahoma-city-ok-usa-2008 title: DH8D, Edmonton AB Canada, 2014 link: https://skybrary.aero/accidents-and-incidents/dh8d-edmonton-ab-canada-2014 description:

On 6 November 2014 a DHC8-400 sustained a burst right main gear tyre during take-off, probably after running over a hard object at high speed and diverted to Edmonton. Shortly after touching down at Edmonton with 'three greens' indicated, the right main gear leg collapsed causing wing and propeller damage and minor injuries to three occupants due to the later. The Investigation concluded that after a high rotational imbalance had been created by the tyre failure, gear collapse on touchdown had been initiated by a rotational speed of the failed tyre/wheel which was similar to one of the natural frequencies of the assembly.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-edmonton-ab-canada-2014 uri: https://skybrary.aero/accidents-and-incidents/dh8d-edmonton-ab-canada-2014 title: S76, vicinity Moosonee ON Canada, 2013 link: https://skybrary.aero/accidents-and-incidents/s76-vicinity-moosonee-canada-2013 description:

On 31 May 2013 the crew of an S76A helicopter positioning for a HEMS detail took off VFR into a dark night environment and lost control as a low level turn was initiated and did not recover. The helicopter was destroyed and the four occupants killed. The Investigation found that the crew had little relevant experience and were not operationally ready to conduct a night VFR take off into an area of total darkness. Significant deficiencies at the Operator and in respect of the effectiveness of its Regulatory oversight were identified as having been a significant context for the accident.

guid: https://skybrary.aero/accidents-and-incidents/s76-vicinity-moosonee-canada-2013 uri: https://skybrary.aero/accidents-and-incidents/s76-vicinity-moosonee-canada-2013 title: B738 / B738, Dublin Ireland, 2014 link: https://skybrary.aero/accidents-and-incidents/b738-b738-dublin-ireland-2014 description:

On 7 October 2014, a locally-based Boeing 737-800 taxiing for departure from runway 34 at Dublin as cleared in normal night visibility collided with another 737-800 stationary in a queue awaiting departure from runway 28. Whilst accepting that pilots have sole responsible for collision avoidance, the Investigation found that relevant restrictions on taxi clearances were being routinely ignored by ATC. It also noted that visual judgement of wingtip clearance beyond 10 metres was problematic and that a subsequent very similar event at Dublin involving two 737-800s of the same Operator was the subject of a separate investigation.

guid: https://skybrary.aero/accidents-and-incidents/b738-b738-dublin-ireland-2014 uri: https://skybrary.aero/accidents-and-incidents/b738-b738-dublin-ireland-2014 title: A321 / B734, Barcelona Spain, 2015 link: https://skybrary.aero/accidents-and-incidents/a321-b734-barcelona-spain-2015 description:

On 25 November 2015, an Airbus A321 taxiing for departure at Barcelona was cleared across an active runway in front of an approaching Boeing 737 with landing clearance on the same runway by a Ground Controller unaware that the runway was active. On reaching the lit stop bar protecting the runway, the crew queried their clearance and were told to hold position. Noting that the event had occurred at the time of a routine twice-daily runway configuration change and two previous very similar events in 2012 and 2014, further safety recommendations on risk management of runway configuration change were made.

guid: https://skybrary.aero/accidents-and-incidents/a321-b734-barcelona-spain-2015 uri: https://skybrary.aero/accidents-and-incidents/a321-b734-barcelona-spain-2015 title: A343 / B763, Barcelona Spain, 2014 link: https://skybrary.aero/accidents-and-incidents/a343-b763-barcelona-spain-2014 description:

On 5 July 2014, an Airbus A340-300 taxiing for departure at Barcelona was cleared across an active runway in front of an approaching Boeing 767 with landing clearance on the same runway by a Ground Controller unaware that the runway was active. Sighting by both aircraft resulted in an accelerated crossing and a very low go around. The Investigation noted the twice-daily runway configuration change made due to noise abatement reasons was imminent. It was also noted that airport procedure involved use of stop bars even on inactive runways and that their operation was then the responsibility of ground controllers.

guid: https://skybrary.aero/accidents-and-incidents/a343-b763-barcelona-spain-2014 uri: https://skybrary.aero/accidents-and-incidents/a343-b763-barcelona-spain-2014 title: A343, Auckland New Zealand, 2013 link: https://skybrary.aero/accidents-and-incidents/a343-auckland-new-zealand-2013 description:

On 18 May 2013 an Airbus A340 with the Captain acting as 'Pilot Flying' commenced its night take off from Auckland in good visibility on a fully lit runway without the crew recognising that it was lined up with the runway edge. After continuing ahead for approximately 1400 metres, the aircraft track was corrected and the take off completed. The incident was not reported to ATC and debris on the runway from broken edge lights was not discovered until a routine inspection almost three hours later. The Investigation concluded that following flights were put at risk by the failure to report.

guid: https://skybrary.aero/accidents-and-incidents/a343-auckland-new-zealand-2013 uri: https://skybrary.aero/accidents-and-incidents/a343-auckland-new-zealand-2013 title: A332, Dubai UAE, 2014 link: https://skybrary.aero/accidents-and-incidents/a332-dubai-uae-2014 description:

On 23 October 2014 an Airbus A330-200 made a sharp brake application to avoid overrunning the turn onto the parking gate at Dubai after flight. A cabin crew member who had left their seat prior to the call from the flight deck to prepare doors, fell and sustained serious neck and back injuries. The investigation found that the sudden braking had led to the fall but concluded that the risk had arisen because required cabin crew procedures had not been followed.

guid: https://skybrary.aero/accidents-and-incidents/a332-dubai-uae-2014 uri: https://skybrary.aero/accidents-and-incidents/a332-dubai-uae-2014 title: DH8B, en route, southwest of Windsor Locks CT USA, 2015 link: https://skybrary.aero/accidents-and-incidents/dh8b-en-route-southwest-windsor-locks-ct-usa-2015 description:

On 5 June 2015, a DHC8-200 descending towards Bradley experienced an in-flight fire which originated at a windshield terminal block. Attempts to extinguish the fire were unsuccessful with the electrical power still selected to the circuit. However, the fire eventually stopped and only smoke remained. An emergency evacuation was carried out after landing. The Investigation was unable to establish the way in which the malfunction that caused the fire arose but noted the continuing occurrence of similar events on the aircraft type and five Safety Recommendations were made to Bombardier to address the continuing risk.

guid: https://skybrary.aero/accidents-and-incidents/dh8b-en-route-southwest-windsor-locks-ct-usa-2015 uri: https://skybrary.aero/accidents-and-incidents/dh8b-en-route-southwest-windsor-locks-ct-usa-2015 title: A333, Manila Philippines, 2013 link: https://skybrary.aero/accidents-and-incidents/a333-manila-philippines-2013 description:

On 7 October 2013 a fire was discovered in the rear hold of an Airbus A330 shortly after it had arrived at its parking stand after an international passenger flight. The fire was eventually extinguished but only after substantial fire damage had been caused to the hold. The subsequent Investigation found that the actions of the flight crew, ground crew and airport fire service following the discovery of the fire had all been unsatisfactory. It also established that the source of the fire had been inadequately packed dangerous goods in passengers checked baggage on the just-completed flight.

guid: https://skybrary.aero/accidents-and-incidents/a333-manila-philippines-2013 uri: https://skybrary.aero/accidents-and-incidents/a333-manila-philippines-2013 title: A320, Porto Portugal, 2013 link: https://skybrary.aero/accidents-and-incidents/a320-porto-portugal-2013 description:

On 1 October 2013, an Airbus A320 took off from a runway intersection at Porto which provided 1900 metres TORA using take off thrust that had been calculated for the full runway length of 3480 metres TORA. It became airborne 350 metres prior to the end of the runway but the subsequent Investigation concluded that it would not have been able to safely reject the take-off or continue it, had an engine failed at high speed. The event was attributed to distraction and the inappropriate formulation of the operating airline's procedures for the pre take-off phase of flight.

guid: https://skybrary.aero/accidents-and-incidents/a320-porto-portugal-2013 uri: https://skybrary.aero/accidents-and-incidents/a320-porto-portugal-2013 title: C30J, Jalalabad Afghanistan, 2015 link: https://skybrary.aero/accidents-and-incidents/c30j-jalalabad-afghanistan-2015 description:

On 2 October 2015, a USAF C130J-30 Hercules crew attempted to depart Jalalabad without being aware that a hard shell NVG case which had been positioned in front of one of the control columns to keep the elevator in an up position during engines-running offloading of tall cargo at the rear was still in place. The resultant inability to control excessive pitch up was attributed to a pitch trim malfunction and crew response assumed this. A stall from which recovery was not made followed and the aircraft impacted terrain and exploded within the aerodrome perimeter 28 seconds after getting airborne.

guid: https://skybrary.aero/accidents-and-incidents/c30j-jalalabad-afghanistan-2015 uri: https://skybrary.aero/accidents-and-incidents/c30j-jalalabad-afghanistan-2015 title: DH8D, en route, west-northwest of Dublin Ireland, 2015 link: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-west-northwest-dublin-ireland-2015 description:

On 31 July 2015 a Bombardier DHC8-400 crew detected the presence of abnormal fumes on the flight deck and were then advised by the cabin crew that the forward toilet smoke alarm had been activated and that smoke was visible in the cabin. Smoke then appeared in the flight deck and a PAN was declared. A diversion to Dublin was subsequently made. The Investigation found that debris from a fractured bearing washer had compromised engine oil seals leading to fumes/smoke entering the aircraft through the air conditioning system. The manufacturer has since introduced a new infinite life bearing washer.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-west-northwest-dublin-ireland-2015 uri: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-west-northwest-dublin-ireland-2015 title: CRJ9, San Sebastian Spain, 2013 link: https://skybrary.aero/accidents-and-incidents/crj9-san-sebastian-spain-2013 description:

On 25 October 2013, the crew of a Bombardier CRJ 900 made an unstable visual daytime approach to San Sebastian which culminated in a hard landing of sufficient severity to trigger an inspection in accordance with the AMM. The inspection did not occur and the aircraft made a further revenue flight before the hard landing was reported and substantial landing gear damage was discovered. The unstable approach at a Category 'C' airport was found to have been flown by the First Officer contrary to applicable regulatory requirements.

guid: https://skybrary.aero/accidents-and-incidents/crj9-san-sebastian-spain-2013 uri: https://skybrary.aero/accidents-and-incidents/crj9-san-sebastian-spain-2013 title: E190, Amsterdam Netherlands, 2014 link: https://skybrary.aero/accidents-and-incidents/e190-amsterdam-netherlands-2014 description:

On 1 October 2014, an Embraer 190 made a very hard landing at Amsterdam after the flight crew failed to recognise that the aircraft had not been configured correctly for the intended automatic landing off the Cat 1 ILS approach being flown. They were slow to respond when no automatic flare occurred. The Investigation was unable to fully review why the configuration error had occurred or why it had not been subsequently detected but the recent type conversion of both the pilots involved was noted.

guid: https://skybrary.aero/accidents-and-incidents/e190-amsterdam-netherlands-2014 uri: https://skybrary.aero/accidents-and-incidents/e190-amsterdam-netherlands-2014 title: AT76, en route, west-southwest of Sydney Australia, 2014 link: https://skybrary.aero/accidents-and-incidents/at76-en-route-west-southwest-sydney-australia-2014 description:

On 20 February 2014, an ATR 72-600 crew mishandled their response to an intended airspeed adjustment whilst using VS mode during descent to Sydney and an upset involving opposite control inputs from the pilots caused an elevator disconnect. The senior cabin attendant sustained serious injury. After recovery of control, the flight was completed without further event. Post flight inspection did not discover damage to the aircraft which exceeded limit and ultimate loads on the stabilisers and the aircraft remained in service for a further five days until it was grounded for replacement of both horizontal and vertical stabilisers.

guid: https://skybrary.aero/accidents-and-incidents/at76-en-route-west-southwest-sydney-australia-2014 uri: https://skybrary.aero/accidents-and-incidents/at76-en-route-west-southwest-sydney-australia-2014 title: A332, vicinity Brisbane Australia, 2013 link: https://skybrary.aero/accidents-and-incidents/a332-vicinity-brisbane-australia-2013 description:

On 21 November 2013, an A330 rejected its take off from Brisbane after an airspeed indication failure. Following maintenance intervention, a similar airspeed indication fault on the subsequent departure was reported to have been detected after V1. Once airborne, reversion to Alternate Law occurred and slat retraction failed. After an air turnback, it was discovered that the cause of both events was blockage of the No. 1 Pitot Head by a mud-dauber wasp nest which was created during the initial two hour turnround at Brisbane. Investigation of a 2014 event to a Boeing 737 at Brisbane with exactly the same causation was noted.

guid: https://skybrary.aero/accidents-and-incidents/a332-vicinity-brisbane-australia-2013 uri: https://skybrary.aero/accidents-and-incidents/a332-vicinity-brisbane-australia-2013 title: H25B, vicinity Kerry Ireland, 2015 link: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-kerry-ireland-2015 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-kerry-ireland-2015 uri: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-kerry-ireland-2015 title: B752, en route, western Ireland, 2013 link: https://skybrary.aero/accidents-and-incidents/b752-en-route-western-ireland-2013 description:

On 20 October 2013, a Boeing 757-200 Co-Pilot believed his aircraft was at risk of stalling when he saw a sudden low airspeed indication on his display during a night descent and reacted by increasing thrust and making abrupt pitch-down inputs. Other airspeed indications remained unaffected. The Captain took control and recovery to normal flight followed. The excursion involved a significant Vmo exceedance, damage to and consequent failure of one of the hydraulic systems and passengers and cabin crew injuries. The false airspeed reading was attributed by the Investigation to transient Ice Crystal Icing affecting one of the pitot probes.

guid: https://skybrary.aero/accidents-and-incidents/b752-en-route-western-ireland-2013 uri: https://skybrary.aero/accidents-and-incidents/b752-en-route-western-ireland-2013 title: MD82, en route, west of Wichita KA USA, 2002 link: https://skybrary.aero/accidents-and-incidents/md82-en-route-west-wichita-ka-usa-2002 description:

On 4 June 2002, the crew of an MD82 in the cruise at FL330 with AP and A/T engaged failed to notice progressive loss of airspeed and concurrent increase in pitch attitude as both engines rolled back to thrust levels which could not sustain level flight. The aircraft stalled and a recovery was accomplished with significant altitude necessary before engine thrust was restored and a diversion made. The Investigation attributed the engine rollback to ice crystal icing obstructing the engine inlet pressure sensors following crew failure to use the engine anti-icing as prescribed. Two Safety Recommendations were made.

guid: https://skybrary.aero/accidents-and-incidents/md82-en-route-west-wichita-ka-usa-2002 uri: https://skybrary.aero/accidents-and-incidents/md82-en-route-west-wichita-ka-usa-2002 title: B738 / AT46, Jakarta Halim Indonesia, 2016 link: https://skybrary.aero/accidents-and-incidents/b738-at46-jakarta-halim-indonesia-2016 description:

On 4 April 2016, a Boeing 737-800 crew taking off in normal night visibility from Jakarta Halim were unable to avoid an ATR 42-600 under tow which had entered their runway after ambiguity in its clearance. Both aircraft sustained substantial damage and caught fire but all those involved escaped uninjured. The Investigation concluded that contributory to the accident had been failure to use a single runway occupancy frequency, towing of a poorly lit aircraft, the potential effect on pilot detection of an obstruction of embedded approach lighting ahead of the displaced landing threshold and issues affecting controller traffic monitoring effectiveness.

guid: https://skybrary.aero/accidents-and-incidents/b738-at46-jakarta-halim-indonesia-2016 uri: https://skybrary.aero/accidents-and-incidents/b738-at46-jakarta-halim-indonesia-2016 title: B733 / SW4, Los Angeles CA USA, 1991 link: https://skybrary.aero/accidents-and-incidents/b733-sw4-los-angeles-ca-usa-1991 description:

On 1 February 1991, a Boeing 737-300 had just made a normal visibility night touchdown on Los Angeles runway 24L in accordance with its clearance when its crew saw another aircraft stationary ahead of them on the same runway. Avoidance was impossible in the time available and a high speed collision and post-impact fire destroyed both aircraft and killed 34 of their 101 occupants and injured 30 others. The other aircraft was subsequently found to have been a Fairchild Metroliner cleared to line up and wait by the same controller who had then cleared the 737 to land.

guid: https://skybrary.aero/accidents-and-incidents/b733-sw4-los-angeles-ca-usa-1991 uri: https://skybrary.aero/accidents-and-incidents/b733-sw4-los-angeles-ca-usa-1991 title: B763, Chicago O'Hare IL USA, 2016 link: https://skybrary.aero/accidents-and-incidents/b763-chicago-ohare-il-usa-2016 description:

On 28 October 2016, an American Airlines Boeing 767-300 made a high speed rejected takeoff after an uncontained right engine failure. A successful emergency evacuation of the 170 occupants was completed as a major fuel-fed fire destroyed the failed engine and substantially damaged the aircraft structure. The failure was attributed to an undetected sub-surface manufacturing defect which was considered to have escaped detection because of systemically inadequate materials inspection requirements rather than any failure to apply existing practices. Safety issues in relation to an evacuation initiated by cabin crew following a rejected takeoff and fire were also examined.

guid: https://skybrary.aero/accidents-and-incidents/b763-chicago-ohare-il-usa-2016 uri: https://skybrary.aero/accidents-and-incidents/b763-chicago-ohare-il-usa-2016 title: B772, en-route, Northern Kanto Japan, 2014 link: https://skybrary.aero/accidents-and-incidents/b772-en-route-northern-kanto-japan-2014 description:

On 16 December 2014, a US-operated Boeing 777-200 encountered a significant period of severe clear air turbulence (CAT) which was unexpected by the flight crew when travelling eastbound over northern Japan at night between FL 270 and FL290. The decision to turn back to Tokyo to allow the nine seriously injured passengers and crew to be treated was made 90 minutes later. The Investigation concluded that the CAT encountered had been correctly forecasted but the Operator's dispatcher-based system for ensuring crew weather awareness was flawed in respect of international operations out of 'non hub' airports.

guid: https://skybrary.aero/accidents-and-incidents/b772-en-route-northern-kanto-japan-2014 uri: https://skybrary.aero/accidents-and-incidents/b772-en-route-northern-kanto-japan-2014 title: B738, Pardubice Czech Republic, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-pardubice-czech-republic-2013 description:

On 25 August 2013, the type-experienced crew of a Boeing 737-800 operating with one thrust reverser locked out made a late touchdown with a significant but allowable tail wind component present and overran the end of the runway at Pardubice onto grass at 51 knots. No damage was caused to the aircraft and no emergency evacuation was performed. The Investigation concluded that the aircraft had been configured so that even for a touchdown within the TDZ, there would have been insufficient landing distance available. The flight crew were found not to have followed a number of applicable operating procedures.

guid: https://skybrary.aero/accidents-and-incidents/b738-pardubice-czech-republic-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-pardubice-czech-republic-2013 title: DH8C / P180, Ottawa ON Canada, 2013 link: https://skybrary.aero/accidents-and-incidents/dh8c-p180-ottawa-canada-2013 description:

On 1 December 2013, a small aircraft taxing for departure at night was cleared to cross an active runway and did so as a DHC8 was taking off from the same runway. Separation was significant and there was no actual risk of collision. The Investigation found that the GND controller had issued clearance to the taxiing aircraft when he had responsibility for its whole taxi route but had neither updated the aircraft status system nor directly advised of the taxiing aircraft when passing responsibility for part of its cleared route to the TWR controller who therefore remained unaware of it.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-p180-ottawa-canada-2013 uri: https://skybrary.aero/accidents-and-incidents/dh8c-p180-ottawa-canada-2013 title: A319 / B738 / B738, en-route, near Lausanne Switzerland, 2013 link: https://skybrary.aero/accidents-and-incidents/a319-b738-b738-en-route-near-lausanne-switzerland-2013 description:

On 26 May 2013, an A319 in Swiss Class 'C' airspace received a TCAS 'Level Off' RA against a 737 above after being inadvertently given an incorrect climb clearance by ATC. The opposing higher-altitude 737 began a coordinated RA climb from level flight and this triggered a second conflict with another 737 also in the cruise 1000 feet above which resulted in coordinated TCAS RAs for both these aircraft. Correct response to all RAs resulted in resolution of both conflicts after prescribed minimum separations had been breached to as low as 1.5nm when 675 feet apart vertically.

guid: https://skybrary.aero/accidents-and-incidents/a319-b738-b738-en-route-near-lausanne-switzerland-2013 uri: https://skybrary.aero/accidents-and-incidents/a319-b738-b738-en-route-near-lausanne-switzerland-2013 title: A388, en-route, southeast of Mumbai India, 2014 link: https://skybrary.aero/accidents-and-incidents/a388-en-route-southeast-mumbai-india-2014 description:

On 18 October 2014, an Airbus A380 descending at night over north east India unexpectedly encountered what was subsequently concluded as likely to have been Clear Air Turbulence after diverting around convective weather. Although seat belt signs were already on, a flight deck instruction to cabin crew to be seated because of the onset of intermittent light to moderate turbulence was completed only seconds before the sudden occurrence of a short period of severe turbulence. Two unrestrained passengers and two of the cabin crew sustained serious injuries. There were other minor injuries and also some cabin trim impact damage.

guid: https://skybrary.aero/accidents-and-incidents/a388-en-route-southeast-mumbai-india-2014 uri: https://skybrary.aero/accidents-and-incidents/a388-en-route-southeast-mumbai-india-2014 title: B773, vicinity Houston TX USA, 2014 link: https://skybrary.aero/accidents-and-incidents/b773-vicinity-houston-tx-usa-2014 description:

On 3 July 2014, a Boeing 777-300 departing Houston came within 200 feet vertically and 0.61nm laterally of another aircraft after climbing significantly above the Standard Instrument Departure Procedure (SID) stop altitude of 4,000 feet believing clearance was to FL310. The crew responded to ATC avoiding action to descend and then disregarded TCAS 'CLIMB' and subsequently LEVEL OFF RAs which followed. The Investigation found that an inadequate departure brief, inadequate monitoring by the augmented crew and poor communication with ATC had preceded the SID non-compliance and that the crew should have followed the TCAS RAs issued.

guid: https://skybrary.aero/accidents-and-incidents/b773-vicinity-houston-tx-usa-2014 uri: https://skybrary.aero/accidents-and-incidents/b773-vicinity-houston-tx-usa-2014 title: B738, Auckland New Zealand, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-auckland-new-zealand-2013 description:

On 7 June 2013, stabiliser trim control cable, pulley and drum damage were discovered on a Boeing 737-800 undergoing scheduled maintenance at Auckland. The Investigation found the damage to have been due to a rag which was found trapped in the forward cable drum windings and concluded that the integrity of the system which provided for stabiliser trim system manual control by pilots had been compromised over an extended period. The rag was traced to a specific Australian maintenance facility which was run by the Operator's parent company and which was the only user of the particular type of rag.

guid: https://skybrary.aero/accidents-and-incidents/b738-auckland-new-zealand-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-auckland-new-zealand-2013 title: B773, Dubai UAE, 2016 link: https://skybrary.aero/accidents-and-incidents/b773-dubai-uae-2016 description:

On 3 August 2016 a Boeing 777-300 rejected a landing at Dubai from the runway following a late touchdown after floating in the flare. It then became airborne without either pilot noticing that the A/T had not responded to TO/GA switch selection and without thrust, control was soon lost and the aircraft hit the runway and slid to a stop. The Investigation found that the crew were unfamiliar with the initiation of a go around after touchdown and had failed to follow several required procedures which could have supported early recovery of control and completion of the intended go around.

guid: https://skybrary.aero/accidents-and-incidents/b773-dubai-uae-2016 uri: https://skybrary.aero/accidents-and-incidents/b773-dubai-uae-2016 title: B737, vicinity Branson MO USA, 2014 link: https://skybrary.aero/accidents-and-incidents/b737-vicinity-branson-mo-usa-2014 description:

On 12 January 2014, a Boeing 737-700 making a night visual approach to Branson advised 'field in sight' approximately 20 miles out and was transferred to TWR and given landing clearance at approximately 6,000 feet. However, the crew had misidentified the airport and subsequently landed on a similarly-orientated runway at a different airport. The Investigation found that required flight crew procedures for such an approach had not been followed and also that applicable ATC procedures for approval of visual approaches by IFR flights were conducive to pilot error in the event that airports were located in close proximity.

guid: https://skybrary.aero/accidents-and-incidents/b737-vicinity-branson-mo-usa-2014 uri: https://skybrary.aero/accidents-and-incidents/b737-vicinity-branson-mo-usa-2014 title: B752, London Gatwick, 2013 link: https://skybrary.aero/accidents-and-incidents/b752-london-gatwick-2013 description:

An announcement by the Captain of a fully-boarded Boeing 757-200 about to depart which was intended to initiate a Precautionary Rapid Disembarkation due to smoke from a hydraulic leak was confusing and a partial emergency evacuation followed. The Investigation found that Cabin Crew only knew of this via the announcement and noted subsequent replacement of the applicable procedures by an improved version, although this was still considered to lack resilience in one respect. The event was considered to have illustrated the importance of having cabin crew close to doors when passengers are on board aircraft on the ground.

guid: https://skybrary.aero/accidents-and-incidents/b752-london-gatwick-2013 uri: https://skybrary.aero/accidents-and-incidents/b752-london-gatwick-2013 title: A320 / CRJ2, Port Elizabeth South Africa, 2014 link: https://skybrary.aero/accidents-and-incidents/a320-crj2-port-elizabeth-south-africa-2014 description:

On 10 July 2014, the crew of a Bombardier CRJ200 on a visual go around from an approach to runway 26 at Port Elizabeth took visual avoiding action overhead of the aerodrome to ensure safe separation from an Airbus A320 which had just taken off. Both aircraft also received TCAS RAs. Minimum achieved separation from radar was 370 metres laterally and 263 feet vertically. The Investigation noted that the go around resulted from the TWR controller, who was supervising a student controller, clearing the A320 to enter the runway and take off when the CRJ200 was on short final to land.

guid: https://skybrary.aero/accidents-and-incidents/a320-crj2-port-elizabeth-south-africa-2014 uri: https://skybrary.aero/accidents-and-incidents/a320-crj2-port-elizabeth-south-africa-2014 title: B763, Singapore, 2015 link: https://skybrary.aero/accidents-and-incidents/b763-singapore-2015 description:

On 12 July 2015, a Japanese-operated Boeing 767-300 deviated from its acknowledged clearance and lit-centreline taxi routing and began take-off from a parallel taxiway in good night visibility, crossing a lit red stop bar in the process. When ATC observed this, the aircraft was instructed to stop which was achieved without further event. A subsequent take-off was uneventful. The crew did not report the event to their airline or their State authorities because the Captain determined that this case did not need to be reported and these organisations only became aware when subsequently contacted by the Investigating Agency.

guid: https://skybrary.aero/accidents-and-incidents/b763-singapore-2015 uri: https://skybrary.aero/accidents-and-incidents/b763-singapore-2015 title: E145, en-route, near London ON Canada, 2014 link: https://skybrary.aero/accidents-and-incidents/e145-en-route-near-london-canada-2014 description:

On 5 September 2014, the crew of an Embraer 145 encountered a more continuous area of convective activity en-route than expected. When it became impossible to see a way to continue through it, the aircraft commander requested, received and actioned flight path advice from the Company flight-following function. This led to the penetration of a mature thunderstorm and several minutes of severe turbulence with aircraft control lost and only regained upon exit from the storm. The Investigation found that the weather avoidance advice was based on an inappropriate source and that following it was an inappropriate command decision.

guid: https://skybrary.aero/accidents-and-incidents/e145-en-route-near-london-canada-2014 uri: https://skybrary.aero/accidents-and-incidents/e145-en-route-near-london-canada-2014 title: B738, vicinity Christchurch New Zealand, 2011 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-christchurch-new-zealand-2011 description:

On 29 October 2011, a Boeing 737-800 on approach to Christchurch during the 68 year-old aircraft commander's annual route check as 'Pilot Flying' continued significantly below the applicable ILS minima without any intervention by the other pilots present before the approach lights became visible and an uneventful touchdown occurred. The Investigation concluded that the commander had compromised the safety of the flight but found no evidence to suggest that age was a factor in his performance. A Safety Recommendation was made to the Regulator concerning the importance of effective management of pilot check flights.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-christchurch-new-zealand-2011 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-christchurch-new-zealand-2011 title: FA7X, en-route, north east of Kuala Lumpur Malaysia, 2011 link: https://skybrary.aero/accidents-and-incidents/fa7x-en-route-north-east-kuala-lumpur-malaysia-2011 description:

On 24 May 2011, a sudden uncommanded maximum upward deflection of the trimmable horizontal stabiliser occurred to a descending Dassault Falcon 7X. Automatic opposite elevator movement did not resolve the situation and an upset lasting just over 2½ minutes followed with a 9,500 feet climb at up to 41° pitch and a speed drop to 125KCAS. Only autonomous return of normal pitch response ended the control difficulty. The remainder of the flight was without further event. A single suddenly defective component with no effective crew response available and not anticipated during type certification was found to have caused the runaway.

guid: https://skybrary.aero/accidents-and-incidents/fa7x-en-route-north-east-kuala-lumpur-malaysia-2011 uri: https://skybrary.aero/accidents-and-incidents/fa7x-en-route-north-east-kuala-lumpur-malaysia-2011 title: A332, Karachi Pakistan, 2014 link: https://skybrary.aero/accidents-and-incidents/a332-karachi-pakistan-2014 description:

On 4 October 2014, the fracture of a hydraulic hose during an A330-200 pushback at night at Karachi was followed by dense fumes in the form of hydraulic fluid mist filling the aircraft cabin and flight deck. After some delay, during which a delay in isolating the APU air bleed exacerbated the ingress of fumes, the aircraft was towed back onto stand and an emergency evacuation completed. During the return to stand, a PBE unit malfunctioned and caught fire when one of the cabin crew attempted to use it which prevented use of the exit adjacent to it for evacuation.

guid: https://skybrary.aero/accidents-and-incidents/a332-karachi-pakistan-2014 uri: https://skybrary.aero/accidents-and-incidents/a332-karachi-pakistan-2014 title: AT76, vicinity Taipei Songshan Taiwan, 2015 link: https://skybrary.aero/accidents-and-incidents/at76-vicinity-taipei-songshan-taiwan-2015 description:

On 4 February 2015, a TransAsia Airways ATR 72-600 crashed into the Keelung River in central Taipei shortly after taking off from nearby Songshan Airport after the crew mishandled a fault on one engine by shutting down the other in error. They did not realise this until recovery from loss of control due to a stall was no longer possible. The Investigation found that the initial engine fault occurred before getting airborne and should have led to a low-speed rejected take-off. Failure to follow SOPs and deficiencies in those procedures were identified as causal.

guid: https://skybrary.aero/accidents-and-incidents/at76-vicinity-taipei-songshan-taiwan-2015 uri: https://skybrary.aero/accidents-and-incidents/at76-vicinity-taipei-songshan-taiwan-2015 title: S92, West Franklin Wellhead Platform North Sea, 2016 link: https://skybrary.aero/accidents-and-incidents/s92-west-franklin-wellhead-platform-north-sea-2016 description:

On 28 December 2016, yaw control was lost during touchdown of a Sikorsky S92A landing on a North Sea offshore platform and it almost fell into the sea. The Investigation found that the loss of control was attributable to the failure of the Tail Rotor Pitch Change Shaft bearing which precipitated damage to the associated control servo. It was also found that despite HUMS monitoring being in place, it had been ineffective in proactively alerting the operator to the earlier stages of progressive bearing deterioration which could have ensured the helicopter was grounded for rectification before the accident occurred.

guid: https://skybrary.aero/accidents-and-incidents/s92-west-franklin-wellhead-platform-north-sea-2016 uri: https://skybrary.aero/accidents-and-incidents/s92-west-franklin-wellhead-platform-north-sea-2016 title: MD88, New York La Guardia USA, 2015 link: https://skybrary.aero/accidents-and-incidents/md88-new-york-la-guardia-usa-2015 description:

On 5 March 2015 a Boeing MD88 veered off a snow-contaminated runway 13 at New York La Guardia soon after touchdown after the experienced flight crew applied excessive reverse thrust and thus compromised directional control due to rudder blanking, a known phenomenon affecting the aircraft type. The aircraft stopped partly outside the airport perimeter with the forward fuselage over water. In addition to identifying the main cause of the accident, the Investigation found that exposure to rudder blanking risks was still widespread. It also noted that the delayed evacuation was partly attributable to inadequate crew performance and related Company procedures.

guid: https://skybrary.aero/accidents-and-incidents/md88-new-york-la-guardia-usa-2015 uri: https://skybrary.aero/accidents-and-incidents/md88-new-york-la-guardia-usa-2015 title: A333, Chicago O'Hare IL USA, 2013 link: https://skybrary.aero/accidents-and-incidents/a333-chicago-ohare-il-usa-2013 description:

On 5 March 2013, the aft-stationed cabin crew of an Airbus A330-300 being operated by Lufthansa on a scheduled international passenger flight from Chicago O'Hare to Munich advised the flight crew after the night normal visibility take-off that they had heard an unusual noise during take-off. Noting that nothing unusual had been heard in the flight deck and that there were no indications of any abnormal system status, the Captain decided, after consulting Company maintenance, that the flight should be completed as planned. The flight proceeded uneventfully but on arrival in Munich, it became clear that the aircraft had sustained substantial damage due to a tail strike on take-off and was unfit for flight.

guid: https://skybrary.aero/accidents-and-incidents/a333-chicago-ohare-il-usa-2013 uri: https://skybrary.aero/accidents-and-incidents/a333-chicago-ohare-il-usa-2013 title: E190, Kupang Indonesia, 2015 link: https://skybrary.aero/accidents-and-incidents/e190-kupang-indonesia-2015 description:

On 21 December 2015, an Embraer 195 crew continued a significantly unstable approach which included prolonged repetition of 'High Speed' and a series of EGPWS Alerts which were both ignored and which culminated in a high speed late touchdown which ended in a 200 metre overrun. The Investigation attributed the event to poor flight management and noted the systemic lack of any effective oversight of pilot operating standards compounded in the investigated event by the effects of a steep flight deck authority gradient and the failure to detect anomalies in the normal operating behaviour of both the pilots involved.

guid: https://skybrary.aero/accidents-and-incidents/e190-kupang-indonesia-2015 uri: https://skybrary.aero/accidents-and-incidents/e190-kupang-indonesia-2015 title: A320, vicinity Naha Okinawa Japan, 2014 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-naha-okinawa-japan-2014 description:

On 28 April 2014, an Airbus A320 making a precision radar approach at Naha in IMC began descent from 1,000 feet QNH at 6nm from touchdown with the autopilot engaged and continued it until successive EGPWS 'PULL UP' Warnings occurred soon after the radar controller had advised four miles from touchdown. Minimum recorded radio height was 242 feet with neither the sea nor the runway in sight. The Investigation noted ineffective alerting by the First Officer, the radar controller's failure to notice the error until just before the EGPWS Warnings and the absence of MSAW annunciations at the controller's position.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-naha-okinawa-japan-2014 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-naha-okinawa-japan-2014 title: B737, Gran Canaria Spain, 2016 link: https://skybrary.aero/accidents-and-incidents/b737-gran-canaria-spain-2016 description:

On 7 January 2016, a Boeing 737-700 was inadvertently cleared by ATC to take off on a closed runway. The take-off was commenced with a vehicle visible ahead at the runway edge. When ATC realised the situation, a 'stop' instruction was issued and the aircraft did so after travelling approximately 740 metres. Investigation attributed the controller error to lost situational awareness. It also noted prior pilot and controller awareness that the runway used was closed and that the pilots had, on the basis of the take-off clearance crossed a lit red stop bar to enter the runway without explicit permission.

guid: https://skybrary.aero/accidents-and-incidents/b737-gran-canaria-spain-2016 uri: https://skybrary.aero/accidents-and-incidents/b737-gran-canaria-spain-2016 title: B738 / AS25, en-route, near Frankfurt Hahn Germany, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-as25-en-route-near-frankfurt-hahn-germany-2013 description:

On 25 April 2013, the experienced pilot of an en-route motor glider which was not under power at the time and therefore not transponding observed a potentially conflicting aircraft in Class 'E' airspace near Frankfurt Hahn and commenced avoiding action. Although the glider was within their field of view, neither of the pilots of the other aircraft, a Boeing 737 in a descent, was aware of the proximity of the glider until it passed them on an almost parallel opposite-direction track 161 feet below them at a range of 350 metres as their aircraft was passing approximately 6,500 feet QNH.

guid: https://skybrary.aero/accidents-and-incidents/b738-as25-en-route-near-frankfurt-hahn-germany-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-as25-en-route-near-frankfurt-hahn-germany-2013 title: E170, en-route, Ishioka Japan, 2014 link: https://skybrary.aero/accidents-and-incidents/e170-en-route-ishioka-japan-2014 description:

On 29 April 2014, an Embraer E170 being operated in accordance with ATC instructions in smooth air conditions suddenly encountered an unexpected short period of severe turbulence which led both members of the cabin crew to fall and sustain injury, one a serious injury. The Investigation concluded that the turbulence encountered, which had occurred soon after the aircraft began descent from FL110, was due to an encounter with the descending wake vortex of a preceding Airbus A340 which had been approximately 10 nm and 2 minutes ahead on the same track and had remained level at FL 110.

guid: https://skybrary.aero/accidents-and-incidents/e170-en-route-ishioka-japan-2014 uri: https://skybrary.aero/accidents-and-incidents/e170-en-route-ishioka-japan-2014 title: A319, vicinity Zurich Switzerland, 2014 link: https://skybrary.aero/accidents-and-incidents/a319-vicinity-zurich-switzerland-2014 description:

On 17 October 2014, two recently type-qualified Airbus A319 pilots responded in a disorganised way after a sudden malfunction soon after take-off from Zurich required one engine to be shutdown. The return to land was flown manually and visually at an excessive airspeed and rate of descent with idle thrust on the remaining engine all the way to a touchdown which occurred without a landing clearance. The Investigation concluded that the poor performance of the pilots had been founded on a lack of prior analysis of the situation, poor CRM and non-compliance with system management and operational requirements.

guid: https://skybrary.aero/accidents-and-incidents/a319-vicinity-zurich-switzerland-2014 uri: https://skybrary.aero/accidents-and-incidents/a319-vicinity-zurich-switzerland-2014 title: AT75, en-route, north of Visby Sweden, 2014 link: https://skybrary.aero/accidents-and-incidents/at75-en-route-north-visby-sweden-2014 description:

On 30 November 2014, an ATR 72-500 suddenly experienced severe propeller vibrations whilst descending through approximately 7,000 feet with the power levers at flight idle. The vibrations subsided after the crew feathered the right engine propeller and then shut the right engine down. The flight was completed without further event. Severe damage to the right propeller mechanism was found with significant consequential damage to the engine. Several other similar events were found to have occurred to other ATR72 aircraft and, since the Investigation could not determine the cause, the EASA was recommended to impose temporary operating limitations pending OEM resolution.

guid: https://skybrary.aero/accidents-and-incidents/at75-en-route-north-visby-sweden-2014 uri: https://skybrary.aero/accidents-and-incidents/at75-en-route-north-visby-sweden-2014 title: B739, Singapore, 2013 link: https://skybrary.aero/accidents-and-incidents/b739-singapore-2013 description:

On 26 May 2013, about 20 minutes after arrival at Singapore for a turn round expected to last about an hour and with crew members on board, a Boeing 737-900 was suddenly rotated approximately 30 degrees about its main gear by a relatively modest wind gust and damaged by consequent impacts. The Investigation concluded that the movement had been due to the failure to follow manufacturer's guidance on both adequate chocking of the aircraft wheels and the order of hold loading. It was found that the Operator had not ensured that its ground handling agent at Singapore was properly instructed.

guid: https://skybrary.aero/accidents-and-incidents/b739-singapore-2013 uri: https://skybrary.aero/accidents-and-incidents/b739-singapore-2013 title: B738, vicinity Porto Portugal, 2015 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-porto-portugal-2015 description:

On 5 September 2015, a Boeing 737-800 was about to commence descent on a non-precision final approach at Porto in VMC when a green laser was directed at the aircraft. The Pilot Flying responded rapidly by shielding his eyes and was unaffected but the other pilot looked up, sustained flash blindness and crew coordination was compromised. Subsequently, the approach became unstable and a go around to an uneventful approach to the reciprocal runway direction was completed. The subsequent Investigation noted the use of increasingly powerful green lasers in this way and that such use was not contrary to Portuguese law.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-porto-portugal-2015 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-porto-portugal-2015 title: B739, Yogyakarta Indonesia, 2015 link: https://skybrary.aero/accidents-and-incidents/b739-yogyakarta-indonesia-2015 description:

On 6 November 2015, a Boeing 737-900 overran the 2,200 metre-long landing runway at Yogyakarta after a tailwind approach with airspeed significantly above the applicable Vref followed by a long landing on a wet runway without optimum use of deceleration devices. The flight crew management of the situation once the aircraft had come to a stop was contrary to procedures in a number of important respects. The aircraft operator took extensive action to improve crew performance following the event. The Investigation found significant fault with the airport operator's awareness of runway surface condition and an absence of related significant risk management.

guid: https://skybrary.aero/accidents-and-incidents/b739-yogyakarta-indonesia-2015 uri: https://skybrary.aero/accidents-and-incidents/b739-yogyakarta-indonesia-2015 title: A320, Hiroshima Japan, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-hiroshima-japan-2015 description:

On 14 April 2015, a night RNAV(GNSS) approach to Hiroshima by an Airbus A320 was continued below minima without the prescribed visual reference and subsequently touched down 325 metres before the runway after failing to transition to a go around initiated from a very low height. The aircraft hit a permitted ground installation, then slid onto the runway before veering off it and stopping. The aircraft sustained extensive damage and an emergency evacuation followed with 28 of the 81 occupants sustaining minor injuries. The Investigation noted the unchallenged gross violation of minima by the Captain.

guid: https://skybrary.aero/accidents-and-incidents/a320-hiroshima-japan-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-hiroshima-japan-2015 title: H25B, vicinity Akron OH USA, 2015 link: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-akron-oh-usa-2015 description:

On 10 November 2015, the crew of an HS 125 lost control of their aircraft during an unstabilised non-precision approach to Akron when descent was continued below Minimum Descent Altitude without the prescribed visual reference. The airspeed decayed significantly below minimum safe so that a low level aerodynamic stall resulted from which recovery was not achieved. All nine occupants died when it hit an apartment block but nobody on the ground was injured. The Investigation faulted crew flight management and its context - a dysfunctional Operator and inadequate FAA oversight of both its pilot training programme and flight operations.

guid: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-akron-oh-usa-2015 uri: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-akron-oh-usa-2015 title: CRJ2, en-route, northern Sweden, 2016 link: https://skybrary.aero/accidents-and-incidents/crj2-en-route-northern-sweden-2016 description:

On 8 January 2016, a Bombardier CRJ200 crew were suddenly presented with a failure of one of the two main PFDs and a consequent uncommanded Autopilot disconnection during the cruise in dark night VMC conditions. No attempt was made to identify the failure as a single system fault and to maintain control using the second serviceable main PFD - which had the same indications as the Standby Horizon. Control of the aircraft was lost beyond possible recovery with terrain impact occurring 80 seconds after the initial appearance of erroneous PFD indications which were attributed to malfunction of the corresponding IRU.

guid: https://skybrary.aero/accidents-and-incidents/crj2-en-route-northern-sweden-2016 uri: https://skybrary.aero/accidents-and-incidents/crj2-en-route-northern-sweden-2016 title: A320 / F50, Adelaide Australia, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-f50-adelaide-australia-2016 description:

On 17 August 2016, a Fokker F50 crossed an active runway at Adelaide ahead of an A320 which was about to land after both its pilots and the controller involved had made assumptions about the content of radio transmissions they were aware they had not fully heard. The Investigation found that the A320 crew had responded promptly to the potential conflict by initiating a low go around over the other aircraft and noted that stop bars were not installed at Adelaide. In addition, aircraft taxiing across active runways were not required to obtain their crossing clearances on the runway control frequency.

guid: https://skybrary.aero/accidents-and-incidents/a320-f50-adelaide-australia-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-f50-adelaide-australia-2016 title: B738 / F100, Geneva Switzerland, 2014 link: https://skybrary.aero/accidents-and-incidents/b738-f100-geneva-switzerland-2014 description:

On 31 March 2014, a Geneva TWR controller believed it was possible to clear a light aircraft for an intersection take off ahead of a Fokker 100 already lining up on the same runway at full length and gave that clearance with a Boeing 737-800 6nm from touchdown on the same runway. Concluding that intervention was not necessary despite the activation of loss of separation alerts, the controller allowed the 737 to continue, issuing a landing clearance whilst the F100 was still on the runway. Sixteen seconds later, the 737 touched down three seconds after the F100 had become airborne.

guid: https://skybrary.aero/accidents-and-incidents/b738-f100-geneva-switzerland-2014 uri: https://skybrary.aero/accidents-and-incidents/b738-f100-geneva-switzerland-2014 title: B744, vicinity Bishkek Kyrgyzstan, 2017 link: https://skybrary.aero/accidents-and-incidents/b744-vicinity-bishkek-kyrgyzstan-2017 description:

On 16 January 2017, a Boeing 747-400F failed to successfully complete a night auto-ILS Cat 2 approach at Bishkek and the aircraft crashed and caught fire killing its occupants and 35 people on the ground and seriously injuring 36 others. The Investigation found that the flight crew had comprehensively failed to monitor the achieved approach flight path and, after capturing and flying down the false upper ILS GS lobe, had then failed to promptly initiate a go around at the applicable decision altitude. The fact that an automatic ILS approach could continue even on a false glideslope was noted.

guid: https://skybrary.aero/accidents-and-incidents/b744-vicinity-bishkek-kyrgyzstan-2017 uri: https://skybrary.aero/accidents-and-incidents/b744-vicinity-bishkek-kyrgyzstan-2017 title: E170 / F900, en-route, east of Varna Bulgaria, 2015 link: https://skybrary.aero/accidents-and-incidents/e170-f900-en-route-east-varna-bulgaria-2015 description:

On 30 June 2015 the crew of an en route Embraer 170 failed to notice that their transponder had reverted to Standby and the ATC response, which involved cross border coordination, was so slow that the aircraft was not informed of the loss of its transponder signal for over 30 minutes by which time it had already passed within 0.9nm of an unseen Dassault Falcon 900 at the same level. The Investigation found that the Embraer crew had failed to follow appropriate procedures and that the subsequent collision risk had been significantly worsened by a muddled and inappropriate ATC response.

guid: https://skybrary.aero/accidents-and-incidents/e170-f900-en-route-east-varna-bulgaria-2015 uri: https://skybrary.aero/accidents-and-incidents/e170-f900-en-route-east-varna-bulgaria-2015 title: DH8D, Saarbrucken Germany, 2015 link: https://skybrary.aero/accidents-and-incidents/dh8d-saarbrucken-germany-2015 description:

On 30 September 2015, the First Officer on an in-service airline-operated Bombardier DHC-8 400 selected the gear up without warning as the Captain was in the process of rotating the aircraft for take-off. The aircraft settled back on the runway wheels up and eventually stopped near the end of the 1,990 metre-long runway having sustained severe damage. The Investigation noted that a factor contributing to the First Officer's unintended action may have been her reduced concentration level but also highlighted the fact that the landing gear control design logic allowed retraction with the nose landing gear airborne.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-saarbrucken-germany-2015 uri: https://skybrary.aero/accidents-and-incidents/dh8d-saarbrucken-germany-2015 title: H25B / AS29, en-route / manoeuvring, near Smith NV USA, 2006 link: https://skybrary.aero/accidents-and-incidents/h25b-as29-en-route-manoeuvring-near-smith-nv-usa-2006 description:

On 28 August 2006, a Hawker 800 collided with a glider at 16,000 feet in Class 'E' airspace. The glider became uncontrollable and its pilot evacuated by parachute. The Hawker was structurally damaged and one engine stopped but it was recovered to a nearby airport. The Investigation noted that the collision had occurred in an area well known for glider activity in which transport aircraft frequently avoided glider collisions using ATC traffic information or by following TCAS RAs. The glider was being flown by a visitor to the area with its transponder intentionally switched off to conserve battery power.

guid: https://skybrary.aero/accidents-and-incidents/h25b-as29-en-route-manoeuvring-near-smith-nv-usa-2006 uri: https://skybrary.aero/accidents-and-incidents/h25b-as29-en-route-manoeuvring-near-smith-nv-usa-2006 title: FA50 / Vehicle, Moscow Vnukovo Russia, 2014 link: https://skybrary.aero/accidents-and-incidents/fa50-vehicle-moscow-vnukovo-russia-2014 description:

On 20 October 2014 a Dassault Falcon 50 taking off at night from Moscow Vnukovo collided with a snow plough which had entered the same runway without clearance shortly after rotation. Control was lost and all occupants died when it was destroyed by impact forces and post crash fire. The uninjured snow plough driver was subsequently discovered to be under the influence of alcohol. The Investigation found that the A-SMGCS effective for over a year prior to the collision had not been properly configured nor had controllers been adequately trained on its use, especially its conflict alerting functions.

guid: https://skybrary.aero/accidents-and-incidents/fa50-vehicle-moscow-vnukovo-russia-2014 uri: https://skybrary.aero/accidents-and-incidents/fa50-vehicle-moscow-vnukovo-russia-2014 title: F16 / C150, vicinity Berkeley County SC USA, 2015 link: https://skybrary.aero/accidents-and-incidents/f16-c150-vicinity-berkeley-county-sc-usa-2015 description:

On 7 July 2015, a mid-air collision occurred between an F16 and a Cessna 150 in VMC at 1,600 feet QNH in Class E airspace north of Charleston SC after neither pilot detected the conflict until it was too late to take avoiding action. Both aircraft subsequently crashed and the F16 pilot ejected. The parallel civil and military investigations conducted noted the limitations of see-and-avoid and attributed the accident to the failure of the radar controller working the F16 to provide appropriate timely resolution of the impending conflict.

guid: https://skybrary.aero/accidents-and-incidents/f16-c150-vicinity-berkeley-county-sc-usa-2015 uri: https://skybrary.aero/accidents-and-incidents/f16-c150-vicinity-berkeley-county-sc-usa-2015 title: JS31, Kärdla Estonia, 2013 link: https://skybrary.aero/accidents-and-incidents/js31-kardla-estonia-2013 description:

On 28 October 2013 a BAe Jetstream 31 crew failed to release one of the propellers from its starting latch prior to setting take off power and the aircraft immediately veered sharply off the side of the runway without directional control until the power levers were returned to idle. The aircraft was then steered on the grass towards the nearby apron and stopped. The Investigation found that the pilots had habitually used multiple unofficial procedures to determine propeller status prior to take off and also noted that no attempt had been made to stop the aircraft using the brakes.

guid: https://skybrary.aero/accidents-and-incidents/js31-kardla-estonia-2013 uri: https://skybrary.aero/accidents-and-incidents/js31-kardla-estonia-2013 title: A319 / A320, Naha Okinawa Japan, 2012 link: https://skybrary.aero/accidents-and-incidents/a319-a320-naha-okinawa-japan-2012 description:

On 5 July 2012, an Airbus A319 entered its departure runway at Naha without clearance ahead of an A320 already cleared to land on the same runway. The A320 was sent around. The Investigation concluded that the A319 crew - three pilots including one with sole responsibility for radio communications and a commander supervising a trainee Captain occupying the left seat - had misunderstood their clearance and their incorrect readback had not been detected by the TWR controller. It was concluded that the controller's non-use of a headset had contributed to failure to detect the incorrect readback.

guid: https://skybrary.aero/accidents-and-incidents/a319-a320-naha-okinawa-japan-2012 uri: https://skybrary.aero/accidents-and-incidents/a319-a320-naha-okinawa-japan-2012 title: A319, Montego Bay Jamaica, 2014 link: https://skybrary.aero/accidents-and-incidents/a319-montego-bay-jamaica-2014 description:

On 10 May 2014 the crew of an Airbus A319 failed to manage their daylight non-precision approach at destination effectively and it culminated in a very hard touchdown which exceeded landing gear design criteria. The Investigation concluded that the comprehensively poor performance of both pilots during the preparation for and execution of the approach could be attributed to both their repeated failure to follow SOPs and retain adequate situational awareness and to a failure of the aircraft operator to fully deliver effective training even though both this training and its SMS met relevant regulatory requirements and guidance.

guid: https://skybrary.aero/accidents-and-incidents/a319-montego-bay-jamaica-2014 uri: https://skybrary.aero/accidents-and-incidents/a319-montego-bay-jamaica-2014 title: B733, Nashville TN USA, 2015 link: https://skybrary.aero/accidents-and-incidents/b733-nashville-tn-usa-2015 description:

On 15 December 2015, a Boeing 737-300 crew inadvertently taxied their aircraft off the side of the taxiway into a ditch whilst en route to the gate after landing at Nashville in normal night visibility. Substantial damage was caused to the aircraft after collapse of the nose landing gear and some passengers sustained minor injuries during a subsequent cabin crew-initiated evacuation. The Investigation found that taxiing had continued when it became difficult to see the taxiway ahead in the presence of apron lighting glare after all centreline and edge lighting in that area had been inadvertently switched off by ATC.

guid: https://skybrary.aero/accidents-and-incidents/b733-nashville-tn-usa-2015 uri: https://skybrary.aero/accidents-and-incidents/b733-nashville-tn-usa-2015 title: F900 / B772, en-route, near Kihnu Island Estonia, 2013 link: https://skybrary.aero/accidents-and-incidents/f900-b772-en-route-near-kihnu-island-estonia-2013 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/f900-b772-en-route-near-kihnu-island-estonia-2013 uri: https://skybrary.aero/accidents-and-incidents/f900-b772-en-route-near-kihnu-island-estonia-2013 title: DC93 / B722, Madrid Spain, 1983 link: https://skybrary.aero/accidents-and-incidents/dc93-b722-madrid-spain-1983 description:

On 7 December 1983, a Boeing 727-200 taking off from Madrid in thick fog collided at high speed with a Douglas DC-9 which had not followed its departure taxi clearance to the beginning of the same runway. The DC-9 crew did not advise ATC of their uncertain location until asked for their position after non-receipt of an expected position report. The Investigation concluded that flight deck coordination on the DC-9 had been deficient and noted that gross error checks using the aircraft compasses had not been conducted. The airport was without any surface movement radar.

guid: https://skybrary.aero/accidents-and-incidents/dc93-b722-madrid-spain-1983 uri: https://skybrary.aero/accidents-and-incidents/dc93-b722-madrid-spain-1983 title: MD82 / C441, Lambert-St Louis MI USA, 1994 link: https://skybrary.aero/accidents-and-incidents/md82-c441-lambert-st-louis-mi-usa-1994 description:

On 22 November 1994 a McDonnell Douglas MD 82 flight crew taking off from Lambert- St. Louis at night in excellent visibility suddenly became aware of a stationary Cessna 441 on the runway ahead and was unable to avoid a high speed collision. The collision destroyed the Cessna but allowed the MD82 to be brought to a controlled stop without occupant injury. The Investigation found that the Cessna 441 pilot had mistakenly believed his departure would be from the runway he had recently landed on and had entered that runway without clearance whilst still on GND frequency.

guid: https://skybrary.aero/accidents-and-incidents/md82-c441-lambert-st-louis-mi-usa-1994 uri: https://skybrary.aero/accidents-and-incidents/md82-c441-lambert-st-louis-mi-usa-1994 title: B722 / BE10, Atlanta GA USA, 1990 link: https://skybrary.aero/accidents-and-incidents/b722-be10-atlanta-ga-usa-1990 description:

On 18 January 1990, a Boeing 727-200 landing at Atlanta at night and in good visibility in accordance with an unconditional clearance failed to see that a Beechcraft King Air, which had landed ahead of it, had yet to clear the runway. The 727 was unable to avoid a collision after a late sighting. The 727 sustained substantial damage and the King Air was destroyed. The Investigation attributed the collision to a combination of the failure of the runway controller to detect the lack of separation resulting from their issue of multiple landing clearances and the inadequacy of relevant ATC procedures.

guid: https://skybrary.aero/accidents-and-incidents/b722-be10-atlanta-ga-usa-1990 uri: https://skybrary.aero/accidents-and-incidents/b722-be10-atlanta-ga-usa-1990 title: DC91 / B722, Detroit MI USA, 1990 link: https://skybrary.aero/accidents-and-incidents/dc91-b722-detroit-mi-usa-1990 description:

On 3 December 1990 a Douglas DC9-10 flight crew taxiing for departure at Detroit in thick fog got lost and ended up stopped to one side of an active runway where, shortly after reporting their position, their aircraft was hit by a departing Boeing 727-200 and destroyed by the impact and subsequent fire. The Investigation concluded that the DC9 crew had failed to communicate positional uncertainty quickly enough but that their difficulties had been compounded by deficiencies in both the standard of air traffic service and airport surface markings, signage and lighting undetected by safety regulator oversight.

guid: https://skybrary.aero/accidents-and-incidents/dc91-b722-detroit-mi-usa-1990 uri: https://skybrary.aero/accidents-and-incidents/dc91-b722-detroit-mi-usa-1990 title: E190 / Vehicle, Paris CDG France, 2014 link: https://skybrary.aero/accidents-and-incidents/e190-vehicle-paris-cdg-france-2014 description:

On 19 April 2014, an Embraer 190 collided with the tug which was attempting to begin a pull forward after departure pushback which, exceptionally for the terminal concerned, was prohibited for the gate involved. As a result, severe damage was caused to the lower fuselage. The Investigation found that the relevant instructions were properly documented but ignored when apron services requested a 'push-pull' to minimise departure delay for an adjacent aircraft. Previous similar events had occurred on the same gate and it was suspected that a lack of appreciation of the reasons why the manoeuvre used was prohibited may have been relevant.

guid: https://skybrary.aero/accidents-and-incidents/e190-vehicle-paris-cdg-france-2014 uri: https://skybrary.aero/accidents-and-incidents/e190-vehicle-paris-cdg-france-2014 title: A320, vicinity Dublin Ireland, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-dublin-ireland-2015 description:

On 3 October 2015, an Airbus A320 which had just taken off from Dublin experienced fumes from the air conditioning system in both flight deck and cabin. A 'PAN' was declared and the aircraft returned with both pilots making precautionary use of their oxygen masks. The Investigation found that routine engine pressure washes carried out prior to departure have been incorrectly performed and a contaminant was introduced into the bleed air supply to the air conditioning system as a result. The context for the error was found to be the absence of any engine wash procedure training for the Operator's engineers.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-dublin-ireland-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-dublin-ireland-2015 title: B738, Delhi India, 2014 link: https://skybrary.aero/accidents-and-incidents/b738-delhi-india-2014 description:

On 5 January 2014, a Boeing 737-800 operating a domestic flight into Dehli diverted to Jaipur due to destination visibility being below approach minima but had to break off the approach there when the aircraft ahead was substantially damaged during landing, blocking the only runway. There was just enough fuel to return to Dehli as a MAYDAY flight and successfully land below applicable minima and with minimal fuel remaining. The Investigation found that a different alternate with better weather conditions would have been more appropriate and that the aircraft operator had failed to provide sufficient ground-based support to the flight.

guid: https://skybrary.aero/accidents-and-incidents/b738-delhi-india-2014 uri: https://skybrary.aero/accidents-and-incidents/b738-delhi-india-2014 title: A320, Jaipur India, 2014 link: https://skybrary.aero/accidents-and-incidents/a320-jaipur-india-2014 description:

On 5 January 2014, an Airbus A320 was unable to land at Delhi due to visibility below crew minima and during subsequent diversion to Jaipur, visibility there began to deteriorate rapidly. A Cat I ILS approach was continued below minima without any visual reference because there were no other alternates within the then-prevailing fuel endurance. The landing which followed was made in almost zero visibility and the aircraft sustained substantial damage after touching down to the left of the runway. The Investigation found that the other possible alternate on departure from Delhi had materially better weather but had been ignored.

guid: https://skybrary.aero/accidents-and-incidents/a320-jaipur-india-2014 uri: https://skybrary.aero/accidents-and-incidents/a320-jaipur-india-2014 title: SW4, en-route, near La Alianza Puerto Rico, 2013 link: https://skybrary.aero/accidents-and-incidents/sw4-en-route-near-la-alianza-puerto-rico-2013 description:

On 2 December 2013, an SA227 Freighter crew lost control of their aircraft after commencing descent from an 11,000 feet cruise in night VMC and it was destroyed by terrain impact which followed structural break-up at about 1,500 feet agl. The Investigation concluded that the break-up had followed an aggressive elevator input in a late attempt to recover from an earlier loss of control which the evidence suggested had been the consequence of unintended crew actions rather than mechanical anomalies. A number of previous SA227 loss of control events were identified, some of which had potentially similar features.

guid: https://skybrary.aero/accidents-and-incidents/sw4-en-route-near-la-alianza-puerto-rico-2013 uri: https://skybrary.aero/accidents-and-incidents/sw4-en-route-near-la-alianza-puerto-rico-2013 title: B738, Rostov-on-Don Russia, 2016 link: https://skybrary.aero/accidents-and-incidents/b738-rostov-don-russia-2016 description:

On 19 March 2016, a Boeing 737-800 making a second night ILS approach to Rostov-on-Don failed to complete a go around commenced after becoming unstable in turbulent conditions and crashed at high speed within the airport perimeter killing all 62 people on board. The Investigation concluded that the Captain had lost spatial awareness and then failed to configure the aircraft correctly or control its flightpath as intended and that although the First Officer had recognised this, he had tried to coach the Captain rather than take over. It was noted that the flight up to this point had been conducted normally.

guid: https://skybrary.aero/accidents-and-incidents/b738-rostov-don-russia-2016 uri: https://skybrary.aero/accidents-and-incidents/b738-rostov-don-russia-2016 title: B738, vicinity Trivandrum India, 2015 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-trivandrum-india-2015 description:

On 18 August 2015, a Boeing 737-800 made three unsuccessful ILS approaches at Cochin around dawn then diverted to Trivandrum where a day VOR approach was unsuccessful and a MAYDAY was declared due low fuel. Two further supposedly visual approaches were attempted there before a third such visual approach - which involved ignoring EGPWS PULL UP Warnings in IMC - was followed by a successful landing with 349kg fuel remaining. The Investigation found that aircraft safety had been jeopardised and that Cochin ATC had not communicated information on the deteriorating weather at Trivandrum. Relevant operator procedures were considered as inadequate.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-trivandrum-india-2015 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-trivandrum-india-2015 title: A320 / B738, en-route, near Córdoba Spain, 2014 link: https://skybrary.aero/accidents-and-incidents/a320-b738-en-route-near-cordoba-spain-2014 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a320-b738-en-route-near-cordoba-spain-2014 uri: https://skybrary.aero/accidents-and-incidents/a320-b738-en-route-near-cordoba-spain-2014 title: B736, Montréal QC Canada, 2015 link: https://skybrary.aero/accidents-and-incidents/b736-montreal-qc-canada-2015 description:

On 5 June 2015, a Boeing 737-600 landed long on a wet runway at Montréal and the crew then misjudged their intentionally-delayed deceleration because of an instruction to clear the relatively long runway at its far end and were then unable to avoid an overrun. The Investigation concluded that use of available deceleration devices had been inappropriate and that deceleration as quickly as possible to normal taxi speed before maintaining this to the intended runway exit was a universally preferable strategy. It was concluded that viscous hydroplaning had probably reduced the effectiveness of maximum braking as the runway end approached.

guid: https://skybrary.aero/accidents-and-incidents/b736-montreal-qc-canada-2015 uri: https://skybrary.aero/accidents-and-incidents/b736-montreal-qc-canada-2015 title: A333, Montréal QC Canada, 2014 link: https://skybrary.aero/accidents-and-incidents/a333-montreal-qc-canada-2014 description:

On 7 October 2014, an Airbus A330-300 failed to maintain the runway centreline as it touched down at Montréal in suddenly reduced forward visibility and part of the left main gear departed the runway edge, paralleling it briefly before returning to it and regaining the centreline as the landing roll was completed. The Investigation attributed the excursion to a delay in corrective action when a sudden change in wind velocity occurred at the same time as degraded visual reference. It was found that the runway should not have been in use in such poor visibility without serviceable lighting.

guid: https://skybrary.aero/accidents-and-incidents/a333-montreal-qc-canada-2014 uri: https://skybrary.aero/accidents-and-incidents/a333-montreal-qc-canada-2014 title: A320, Halifax NS Canada, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-halifax-ns-canada-2015 description:

On 29 March 2015, an Airbus A320 crew mismanaged the descent during a night non-precision approach at Halifax and continued below MDA without the mandatory autopilot disconnection until, with inadequate visual reference, the aircraft impacted terrain and obstructions 225 metres short of the runway. The aircraft was destroyed but there were no fatalities. The Investigation found that the crew did not monitor their descent against the required vertical profile, as there was no SOP requiring them to do so, and did not recognise in time that a go around was appropriate.

guid: https://skybrary.aero/accidents-and-incidents/a320-halifax-ns-canada-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-halifax-ns-canada-2015 title: B788, en-route, north of Darwin NT Australia, 2015 link: https://skybrary.aero/accidents-and-incidents/b788-en-route-north-darwin-nt-australia-2015 description:

On 21 December 2015, a Boeing 787-8 at FL400 in the vicinity of convective weather conducive to ice crystal icing penetrated an area which included maximum intensity weather radar returns. A very short period of erratic airspeed indications followed and the FCS reverted to Secondary Mode requiring manual flying. Since this Mode remained 'latched' and could therefore only be reset on the ground, it was decided that an en route diversion was appropriate and this was accomplished without further event. Boeing subsequently modified the FCS software to reduce the chances of reversion to Secondary Mode in short-duration unreliable airspeed events.

guid: https://skybrary.aero/accidents-and-incidents/b788-en-route-north-darwin-nt-australia-2015 uri: https://skybrary.aero/accidents-and-incidents/b788-en-route-north-darwin-nt-australia-2015 title: CL60 / A388, en-route, Arabian Sea, 2017 link: https://skybrary.aero/accidents-and-incidents/cl60-a388-en-route-arabian-sea-2017 description:

On 7 January 2017, the crew of a Bombardier Challenger en route at FL340 over international waters between India and the Arabian Peninsula temporarily lost control of their aircraft approximately one minute after an Airbus A380 had passed 1,000 feet above them tracking in the opposite direction. The Investigation is ongoing but has noted that both aircraft were in compliance with their air traffic clearances, that a major height loss occurred during loss of control with some occupants sustaining serious injuries and that after successfully diverting, the structure of the aircraft was found to have been damaged beyond economic repair.

guid: https://skybrary.aero/accidents-and-incidents/cl60-a388-en-route-arabian-sea-2017 uri: https://skybrary.aero/accidents-and-incidents/cl60-a388-en-route-arabian-sea-2017 title: MD83, vicinity Lagos Nigeria, 2012 link: https://skybrary.aero/accidents-and-incidents/md83-vicinity-lagos-nigeria-2012 description:

On 3 June 2012, the crew of a Boeing MD-83 experienced problems in controlling the thrust from first one engine and then also the other which dramatically reduced the amount of thrust available. Eventually, when a few miles from destination Lagos, it became apparent that it would be impossible to reach the runway and the aircraft crashed in a residential district killing all 153 occupants and 6 people on the ground. The Investigation was unable to conclusively identify the cause of the engine malfunctions but attributed the accident outcome to the crew's failure to make a timely diversion to an alternative airport.

guid: https://skybrary.aero/accidents-and-incidents/md83-vicinity-lagos-nigeria-2012 uri: https://skybrary.aero/accidents-and-incidents/md83-vicinity-lagos-nigeria-2012 title: DH8B, Kangerlussuaq Greenland, 2017 link: https://skybrary.aero/accidents-and-incidents/dh8b-kangerlussuaq-greenland-2017 description:

On 2 March 2017, a DHC8-200 took off from Kangerlussuaq in normal day visibility without clearance and almost immediately overflew three snow clearance vehicles on the runway. The Investigation identified a number of likely contributory factors including a one hour departure delay which the crew were keen to reduce in order to remain within their maximum allowable duty period and their inability to initially see the vehicles because of the runway down slope. No evidence of crew fatigue was found; it was noted that the vehicles involved had been in contact with TWR on a separate frequency using the local language.

guid: https://skybrary.aero/accidents-and-incidents/dh8b-kangerlussuaq-greenland-2017 uri: https://skybrary.aero/accidents-and-incidents/dh8b-kangerlussuaq-greenland-2017 title: A332, Perth WA Australia, 2014 link: https://skybrary.aero/accidents-and-incidents/a332-perth-wa-australia-2014 description:

On 26 November 2014, an Airbus A330-200 was struck by lightning just after arriving at its allocated stand following a one hour post-landing delay after suspension of ramp operations due to an overhead thunderstorm. Adjacent ground services operatives were subject to electrical discharge from the strike and one who was connected to the aircraft flight deck intercom was rendered unconscious. The Investigation found that the equipment and procedures for mitigation of risk from lightning strikes were not wholly effective and also that perceived operational pressure had contributed to a resumption of ground operations which hindsight indicated had been premature.

guid: https://skybrary.aero/accidents-and-incidents/a332-perth-wa-australia-2014 uri: https://skybrary.aero/accidents-and-incidents/a332-perth-wa-australia-2014 title: DH8A, Saulte Ste. Marie ON Canada, 2015 link: https://skybrary.aero/accidents-and-incidents/dh8a-saulte-ste-marie-canada-2015 description:

On 24 February 2015, the crew of a Bombardier DHC8-100 continued an already unstable approach towards a landing despite losing sight of the runway as visibility deteriorated in blowing snow. The aircraft touched down approximately 140 metres before the start of the paved surface. The continued unstable approach was attributed by the Investigation to plan continuation bias compounded by confirmation bias. It was also found that although the aircraft operator had had an approved SMS in place for almost six years, it had not detected that approaches made by the aircraft type involved were routinely unstable.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-saulte-ste-marie-canada-2015 uri: https://skybrary.aero/accidents-and-incidents/dh8a-saulte-ste-marie-canada-2015 title: ATP, Vilhelmina Sweden, 2016 link: https://skybrary.aero/accidents-and-incidents/atp-vilhelmina-sweden-2016 description:

On 6 April 2016, a BAe ATP partly left the side of the runway soon after touchdown, regaining it after 155 metres before completing its landing roll. It sustained damage rendering it unfit to continue flying but this was not noticed until five further flights had been made. Investigation attributed the excursion to lack of pilot response to unexpected beta range power and the continued flying to the aircraft Captain's failure to ensure proper event recording, accurate operator notification or a post-excursion engineering inspection of the aircraft. Systemic inadequacy in safety management and culture at the operator was identified.

guid: https://skybrary.aero/accidents-and-incidents/atp-vilhelmina-sweden-2016 uri: https://skybrary.aero/accidents-and-incidents/atp-vilhelmina-sweden-2016 title: IL76, vicinity Karachi Pakistan, 2010 link: https://skybrary.aero/accidents-and-incidents/il76-vicinity-karachi-pakistan-2010 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/il76-vicinity-karachi-pakistan-2010 uri: https://skybrary.aero/accidents-and-incidents/il76-vicinity-karachi-pakistan-2010 title: DH8B / BN2P, Horn Island QLD Australia, 2016 link: https://skybrary.aero/accidents-and-incidents/dh8b-bn2p-horn-island-qld-australia-2016 description:

On 12 October 2016, a BN2 Islander and a Bombardier DHC8-200 were involved in a near miss after the DHC8 took off from a runway which intersected with the runway on which the BN2 was about to land. The BN2 broke off its approach just before touchdown when the DHC8 was observed accelerating towards the runway intersection on its take-off roll. The Investigation noted that the uncontrolled aerodrome involved relied on visual separation and use of a CTAF and found that although both aircraft were aware of each other, the DHC8 crew failed to fully utilise visual lookout.

guid: https://skybrary.aero/accidents-and-incidents/dh8b-bn2p-horn-island-qld-australia-2016 uri: https://skybrary.aero/accidents-and-incidents/dh8b-bn2p-horn-island-qld-australia-2016 title: F28, Gällivare Sweden, 2016 link: https://skybrary.aero/accidents-and-incidents/f28-gallivare-sweden-2016 description:

On 6 April 2016, a Romanian-operated Fokker F28 overran the runway at Gällivare after a bounced night landing. There were no occupant injuries and only slight aircraft damage. The Investigation concluded that after a stabilised approach, the handling of the aircraft just prior and after touchdown, which included late and inappropriate deployment of the thrust reversers, was not compatible with a safe landing in the prevailing conditions, that the crew briefing for the landing had been inadequate and that the reported runway friction coefficients were probably unreliable. Safety Recommendations were made for a generic 'Safe Landing' concept to be developed.

guid: https://skybrary.aero/accidents-and-incidents/f28-gallivare-sweden-2016 uri: https://skybrary.aero/accidents-and-incidents/f28-gallivare-sweden-2016 title: DH8D / B772, vicinity Sydney Australia, 2016 link: https://skybrary.aero/accidents-and-incidents/dh8d-b772-vicinity-sydney-australia-2016 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-b772-vicinity-sydney-australia-2016 uri: https://skybrary.aero/accidents-and-incidents/dh8d-b772-vicinity-sydney-australia-2016 title: B734, Sharjah UAE, 2015 link: https://skybrary.aero/accidents-and-incidents/b734-sharjah-uae-2015 description:

On 24 September 2015, a Boeing 737-400 cleared for a night take-off from Sharjah took off from the parallel taxiway. The controller decided that since the taxiway was sterile and the aircraft speed was unknown, the safest option was to allow the take-off to continue. The Investigation noted that the taxiway used had until a year previously been the runway, becoming a parallel taxiway only when a new runway had been opened alongside it. It was noted that the controller had lost visual watch on the aircraft and regained it only once the aircraft was already at speed.

guid: https://skybrary.aero/accidents-and-incidents/b734-sharjah-uae-2015 uri: https://skybrary.aero/accidents-and-incidents/b734-sharjah-uae-2015 title: E195 / A320, Brussels Belgium, 2016 link: https://skybrary.aero/accidents-and-incidents/e195-a320-brussels-belgium-2016 description:

On 5 October 2016, an Embraer 195 took off at night without clearance as an Airbus A320 was about to touch down on an intersecting runway. The A320 responded promptly to the ATC go-around instruction and passed over the intersection after the E195 had accelerated through it during its take-off roll. The Investigation found that the E195 crew had correctly acknowledged a 'line up and wait' instruction but then commenced their take-off without stopping. Inadequate crew cross-checking procedures at the E195 operator and ATC use of intermediate runway access for intersecting runway take-offs were identified as contributory factors.

guid: https://skybrary.aero/accidents-and-incidents/e195-a320-brussels-belgium-2016 uri: https://skybrary.aero/accidents-and-incidents/e195-a320-brussels-belgium-2016 title: B773, Singapore, 2016 link: https://skybrary.aero/accidents-and-incidents/b773-singapore-2016 description:

On 27 June 2016, a Boeing 777-300ER powered by GE90-115B engines returned to Singapore when what was initially identified as a suspected right engine oil quantity indication problem evidenced other abnormal symptoms relating to the same engine. The engine caught fire on landing. The substantial fire was quickly contained and an emergency evacuation was not performed. The cause of the low oil quantity indication and the fire was a failure of the right engine Main Fuel Oil Heat Exchanger which had resulted in lubrication of the whole of the affected engine by a mix of jet fuel and oil.

guid: https://skybrary.aero/accidents-and-incidents/b773-singapore-2016 uri: https://skybrary.aero/accidents-and-incidents/b773-singapore-2016 title: E190 / A320, Toronto ON Canada, 2016 link: https://skybrary.aero/accidents-and-incidents/e190-a320-toronto-canada-2016 description:

On 30 January 2016, an Embraer 190-100 crew lined up on their assigned departure runway in good visibility at night without clearance to do so just as an Airbus A320 was about to land on it. The Investigation attributed the incursion to crew error arising from misinterpretation by both pilots of a non-standard Ground Controller instruction to position alongside another aircraft also awaiting departure at the hold when routinely transferring them to Tower as an instruction to line up on the runway. The failure to use the available stop bar system as a basis for controller incursion alerting was identified.

guid: https://skybrary.aero/accidents-and-incidents/e190-a320-toronto-canada-2016 uri: https://skybrary.aero/accidents-and-incidents/e190-a320-toronto-canada-2016 title: PC12, vicinity Meekatharra WA Australia, 2016 link: https://skybrary.aero/accidents-and-incidents/pc12-vicinity-meekatharra-wa-australia-2016 description:

On 18 June 2016, a PC12 crew experienced a sudden corruption of the SVS image on their PFDs soon after a night take-off and the Pilot Flying initially reacted by increasing pitch in response to the false image which had obscured the primary flight path symbology on the PFD. Recovery was achieved before the resulting airspeed drop had activated the Stall Protection System by the pilots transferring their attention to the Standby Instrument Display. The Investigation noted that the SVS was not certified for primary flight path control but that the failure had created temporary spatial disorientation.

guid: https://skybrary.aero/accidents-and-incidents/pc12-vicinity-meekatharra-wa-australia-2016 uri: https://skybrary.aero/accidents-and-incidents/pc12-vicinity-meekatharra-wa-australia-2016 title: A320, Brunei, 2014 link: https://skybrary.aero/accidents-and-incidents/a320-brunei-2014 description:

On 7 July 2014, an Airbus A320 landing at Brunei departed the side of the runway almost immediately after touchdown and continued to gradually diverge from the runway axis until stopping after a ground run of approximately 1,050 metres. The Investigation concluded that the aircraft commander, having taken over control from the First Officer when the latter lost their previously-acquired prescribed visual reference below Decision Altitude due to a sudden-onset intense rain shower ahead, had then continued the approach without recognising that the only lights still visible to him were those at the right hand edge of the runway.

guid: https://skybrary.aero/accidents-and-incidents/a320-brunei-2014 uri: https://skybrary.aero/accidents-and-incidents/a320-brunei-2014 title: B763, Addis Ababa Ethiopia, 2014 link: https://skybrary.aero/accidents-and-incidents/b763-addis-ababa-ethiopia-2014 description:

On 12 October 2014, a Boeing 767-300 commenced take-off at Addis Ababa in accordance with its clearance but rejected take-off at 135 knots when the crew saw an obstruction ahead in the centre of the runway and it stopped approximately 100 metres from a vehicle. The Investigation found that the GND controller had cleared the vehicle to enter the runway, the TWR controller had given take-off clearance without first checking that that the runway was clear. It could not be established whether the GND controller had obtained TWR controller permission to grant the vehicle runway access.

guid: https://skybrary.aero/accidents-and-incidents/b763-addis-ababa-ethiopia-2014 uri: https://skybrary.aero/accidents-and-incidents/b763-addis-ababa-ethiopia-2014 title: H25B / B738, en-route, south eastern Senegal, 2015 link: https://skybrary.aero/accidents-and-incidents/h25b-b738-en-route-south-eastern-senegal-2015 description:

On 5 September 2015, a Boeing 737-800 cruising as cleared at FL350 on an ATS route in daylight collided with an opposite direction HS 125-700 which had been assigned and acknowledged altitude of FL340. The 737 continued to destination with winglet damage apparently causing no control impediment but radio contact with the HS 125 was lost and it was subsequently radar-tracked maintaining FL350 and continuing westwards past its destination Dakar for almost an hour before making an uncontrolled descent into the sea. The Investigation found that the HS125 had a recent history of un-rectified altimetry problems which prevented TCAS activation.

guid: https://skybrary.aero/accidents-and-incidents/h25b-b738-en-route-south-eastern-senegal-2015 uri: https://skybrary.aero/accidents-and-incidents/h25b-b738-en-route-south-eastern-senegal-2015 title: A310, vicinity Moroni Comoros, 2009 link: https://skybrary.aero/accidents-and-incidents/a310-vicinity-moroni-comoros-2009 description:

On 29 June 2009, an Airbus A310-300 making a dark-night visual circling approach to Moroni crashed into the sea and was destroyed. The Investigation found that the final impact had occurred with the aircraft stalled and in the absence of appropriate prior recovery actions and that this had been immediately preceded by two separate GWPS 'PULL UP' events. It was concluded that the attempted circling procedure had been highly unstable with the crew's inappropriate actions and inactions probably attributable to their becoming progressively overwhelmed by successive warnings and alerts caused by their poor management of the aircraft's flight path.

guid: https://skybrary.aero/accidents-and-incidents/a310-vicinity-moroni-comoros-2009 uri: https://skybrary.aero/accidents-and-incidents/a310-vicinity-moroni-comoros-2009 title: UAV, manoeuvring, north of Reims France, 2006 link: https://skybrary.aero/accidents-and-incidents/uav-manoeuvring-north-reims-france-2006 description:

On 29 February 2016, control of a 50 kg, 3.8 metre wingspan UAV was lost during a flight test being conducted in a Temporary Segregated Area in northern Belgium. The UAV then climbed to 4,000 feet and took up a south south-westerly track across Belgium and into northern France where it crash-landed after the engine stopped. The Investigation found that control communications had been interrupted because of an incorrectly manufactured co-axial cable assembly and a separate autopilot software design flaw not previously identified. This then prevented the default recovery process from working. A loss of prescribed traffic separation was recorded.

guid: https://skybrary.aero/accidents-and-incidents/uav-manoeuvring-north-reims-france-2006 uri: https://skybrary.aero/accidents-and-incidents/uav-manoeuvring-north-reims-france-2006 title: A332 / Vehicle, Madrid Spain, 2014 link: https://skybrary.aero/accidents-and-incidents/a332-vehicle-madrid-spain-2014 description:

On 17 October 2014, an Airbus A330-200 crew taking off from Madrid at night detected non-runway lights ahead as they accelerated through approximately 90 knots. ATC were unaware what they might be and the lights subsequently disappeared, and the crew continued the takeoff. A reportedly unlit vehicle at the side of the runway was subsequently passed just before rotation. The Investigation found that the driver of an external contractor's vehicle had failed to correctly route to the parallel runway which was closed overnight for maintenance but had not realised this until he saw the lights of an approaching aircraft.

guid: https://skybrary.aero/accidents-and-incidents/a332-vehicle-madrid-spain-2014 uri: https://skybrary.aero/accidents-and-incidents/a332-vehicle-madrid-spain-2014 title: B738, Mildura VIC Australia, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-mildura-vic-australia-2013 description:

On 18 June 2013, a Boeing 737-800 crew en route to Adelaide encountered un-forecast below-minima weather conditions on arrival there and decided to divert to their designated alternate, Mildura, approximately 220nm away where both the weather report and forecast were much better. However, on arrival there, an un-forecast rapid deterioration to thick fog had occurred with insufficient fuel to go anywhere else. The only available approach was flown, but despite exceeding the minimum altitude by 260 feet, no visual reference was obtained. A further approach with the reported overcast 100 feet agl and visibility 200 metres was continued to a landing.

guid: https://skybrary.aero/accidents-and-incidents/b738-mildura-vic-australia-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-mildura-vic-australia-2013 title: B737, Mildura VIC Australia, 2013 link: https://skybrary.aero/accidents-and-incidents/b737-mildura-vic-australia-2013 description:

On 18 June 2013, a Boeing 737-800 crew en route to Adelaide learned that un-forecast below-minima weather had developed there and decided to divert to their designated alternate, Mildura, approximately 220nm away where both the weather report and forecast were much better. However, on arrival at Mildura, an un-forecast rapid deterioration to thick fog had occurred with insufficient fuel to divert elsewhere. The only available approach was flown to a successful landing achieved after exceeding the minimum altitude by 240 feet to gain sight of the runway. An observation immediately afterwards gave visibility 900 metres in fog with cloudbase 100 feet.

guid: https://skybrary.aero/accidents-and-incidents/b737-mildura-vic-australia-2013 uri: https://skybrary.aero/accidents-and-incidents/b737-mildura-vic-australia-2013 title: A320 / B789 / A343, San Francisco CA USA, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-b789-a343-san-francisco-ca-usa-2017 description:

On 7 July 2017 the crew of an Airbus A320, cleared for an approach and landing on runway 28R at San Francisco in night VMC, lined up for the visual approach for which it had been cleared on the occupied parallel taxiway instead of the runway extended centreline and only commenced a go-around at the very last minute, having descended to about 60 feet agl whilst flying over two of the four aircraft on the taxiway. The Investigation determined that the sole direct cause of the event was the poor performance of the A320 flight crew.

guid: https://skybrary.aero/accidents-and-incidents/a320-b789-a343-san-francisco-ca-usa-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-b789-a343-san-francisco-ca-usa-2017 title: DH8D, Manchester UK, 2016 link: https://skybrary.aero/accidents-and-incidents/dh8d-manchester-uk-2016 description:

On 14 December 2016, soon after a Bombardier DHC8-400 took off from Manchester, an unfastened engine access panel detached and struck and damaged the aircraft's vertical stabiliser before falling onto and alongside the departure runway. The Investigation found the panel had been left unsecured after routine overnight maintenance which required it to be opened and that this condition had not then been detected during the pilot-performed pre-flight external check. An identical event was found to have occurred to the same aircraft a month earlier. The Operator-provided pilot training on pre departure inspections was found to be inconsistent.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-manchester-uk-2016 uri: https://skybrary.aero/accidents-and-incidents/dh8d-manchester-uk-2016 title: SH36, vicinity Sint Maarten Eastern Caribbean, 2014 link: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-sint-maarten-eastern-caribbean-2014 description:

On 29 October 2014, a Shorts SD 3-60 ceased its climb out soon after take-off and was subsequently found to have descended into the sea at increasing speed with the impact destroying the aircraft. The Investigation found that the aircraft had been airworthy prior to the crash and, noting a dark night departure and a significant authority gradient on the fight deck, concluded that the pilot flying had probably experienced a somatogravic illusion as the aircraft accelerated during flap retraction and made a required left turn. The extent of any intervention by the other pilot could not be determined.

guid: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-sint-maarten-eastern-caribbean-2014 uri: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-sint-maarten-eastern-caribbean-2014 title: AT75 / B739, Medan Indonesia, 2017 link: https://skybrary.aero/accidents-and-incidents/at75-b739-medan-indonesia-2017 description:

On 3 August 2017, a Boeing 737-900ER landing at Medan was in wing-to-wing collision as it touched down with an ATR 72-500 which had entered the same runway to depart at an intermediate point. Substantial damage was caused but both aircraft could be taxied clear. The Investigation concluded that the ATR 72 had entered the runway at an opposite direction without clearance after its incomplete readback had gone unchallenged by ATC. Controllers appeared not to have realised that a collision had occurred despite warnings of runway debris and the runway was not closed until other aircraft also reported debris.

guid: https://skybrary.aero/accidents-and-incidents/at75-b739-medan-indonesia-2017 uri: https://skybrary.aero/accidents-and-incidents/at75-b739-medan-indonesia-2017 title: E190, en-route, southwest Vermont USA, 2016 link: https://skybrary.aero/accidents-and-incidents/e190-en-route-southwest-vermont-usa-2016 description:

On 25 May 2016, an Embraer ERJ 190 experienced a major electrical system failure soon after reaching its cruise altitude of FL 360. ATC were advised of problems and a descent to enable the APU to be started was made. This action restored most of the lost systems and the crew, not having declared an emergency, elected to complete their planned 400nm flight. The Investigation found that liquid contamination of an underfloor avionics bay had caused the electrical failure which had also involved fire and smoke without crew awareness because the smoke detection and air recirculation systems had been unpowered.

guid: https://skybrary.aero/accidents-and-incidents/e190-en-route-southwest-vermont-usa-2016 uri: https://skybrary.aero/accidents-and-incidents/e190-en-route-southwest-vermont-usa-2016 title: A320, vicinity Rapid City SD USA, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-rapid-city-sd-usa-2016 description:

On 7 July 2016, an Airbus A320 crew cleared for a dusk visual approach to Rapid City mis-identified runway 13 at Ellsworth AFB as runway 14 at their intended destination and landed on it after recognising their error just before touchdown. The Investigation concluded that the crew had failed to use the available instrument approach guidance to ensure their final approach was made on the correct extended centreline and noted that it had only been possible to complete the wrong approach by flying an abnormally steep unstabilised final approach. Neither pilot was familiar with Rapid City Airport.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-rapid-city-sd-usa-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-rapid-city-sd-usa-2016 title: C525 / C42, en-route / manoeuvring, near Eastbourne UK, 2017 link: https://skybrary.aero/accidents-and-incidents/c525-c42-en-route-manoeuvring-near-eastbourne-uk-2017 description:

On 7 March 2017, an en-route Cessna Citation and a manoeuvring Ikarus C42 light aircraft approaching almost head-on at speeds of 240 knots and 55 knots respectively almost collided at an altitude of 3,500 feet in VMC outside controlled airspace. The Investigation found that only the C42 pilot had seen a conflicting aircraft and that they had then taken avoiding action which had mitigated the high risk of collision. The closest point of approach was recorded on radar as less than 100 feet vertically and less than 185 metres laterally. The near miss was categorised as an ICAO 'A' event.

guid: https://skybrary.aero/accidents-and-incidents/c525-c42-en-route-manoeuvring-near-eastbourne-uk-2017 uri: https://skybrary.aero/accidents-and-incidents/c525-c42-en-route-manoeuvring-near-eastbourne-uk-2017 title: A333 / A319, en-route, east of Lashio Myanmar, 2017 link: https://skybrary.aero/accidents-and-incidents/a333-a319-en-route-east-lashio-myanmar-2017 description:

On 3 May 2017, an Airbus A330 and an Airbus A319 lost prescribed separation whilst tracking in opposite directions on a radar-controlled ATS route in eastern Myanmar close to the Chinese border. The Investigation found that the response of the A330 crew to a call for another aircraft went undetected and they descended to the same level as the A319 with the lost separation only being mitigated by intervention from the neighbouring Chinese ACC which was able to give the A319 an avoiding action turn. At the time of the conflict, the A330 had disappeared from the controlling ACCs radar.

guid: https://skybrary.aero/accidents-and-incidents/a333-a319-en-route-east-lashio-myanmar-2017 uri: https://skybrary.aero/accidents-and-incidents/a333-a319-en-route-east-lashio-myanmar-2017 title: CRJX, Madrid Spain, 2015 link: https://skybrary.aero/accidents-and-incidents/crjx-madrid-spain-2015 description:

On 1 February 2015, a Bombardier CRJ 1000 departed from Pamplona with slush likely to have been in excess of the regulatory maximum depth on the runway. On landing at Madrid, the normal operation of the brake units was compromised by ice and one tyre burst damaging surrounding components and leaving debris on the runway, and the other tyre was slow to spin up and sustained a serious flat spot. The Investigation concluded that the Pamplona apron, taxiway and runway had not been properly cleared of frozen deposits and that the flight crew had not followed procedures appropriate for the prevailing conditions.

guid: https://skybrary.aero/accidents-and-incidents/crjx-madrid-spain-2015 uri: https://skybrary.aero/accidents-and-incidents/crjx-madrid-spain-2015 title: BN2P / B763, vicinity Kagoshima Japan, 2015 link: https://skybrary.aero/accidents-and-incidents/bn2p-b763-vicinity-kagoshima-japan-2015 description:

On 10 October 2015, a Britten-Norman BN2 instructed to join final behind a Boeing 767 instead joined in front of it which obliged the 767 crew to make a go around. The Investigation was unable to establish why the BN2 pilot failed to follow their conditional clearance but noted that the 'follow' clearance given onto final approach had not been accompanied by a sequence number, and when giving the aircraft type to be followed so that its sighting could be reported, the controller had not challenged the incomplete readback or repeated the aircraft type when subsequently issuing the clearance.

guid: https://skybrary.aero/accidents-and-incidents/bn2p-b763-vicinity-kagoshima-japan-2015 uri: https://skybrary.aero/accidents-and-incidents/bn2p-b763-vicinity-kagoshima-japan-2015 title: DHC6, Tiree UK, 2017 link: https://skybrary.aero/accidents-and-incidents/dhc6-tiree-uk-2017 description:

On 7 March 2017, a DHC-6-300 left the side of the runway after touchdown in what the crew believed was a crosswind component within the Operator's crosswind limit. The Investigation concluded that the temporary loss of control of the aircraft was consistent with the occurrence with a sudden gust of wind above the applicable crosswind limits and noted the reliance of the crew on 'spot' winds provided by TWR during the final stages of the approach.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-tiree-uk-2017 uri: https://skybrary.aero/accidents-and-incidents/dhc6-tiree-uk-2017 title: A319, Mumbai India, 2013 link: https://skybrary.aero/accidents-and-incidents/a319-mumbai-india-2013 description:

On 12 April 2013, an Airbus A319 landed without clearance on a runway temporarily closed for routine inspection after failing to check in with TWR following acceptance of the corresponding frequency change. Two vehicles on the runway saw the aircraft approaching on short final and successfully vacated. The Investigation concluded that the communication failure was attributable entirely to the Check Captain who was in command of the flight involved and was acting as 'Pilot Monitoring'. It was considered that the error was probably attributable to the effects of operating through the early hours during which human alertness is usually reduced.

guid: https://skybrary.aero/accidents-and-incidents/a319-mumbai-india-2013 uri: https://skybrary.aero/accidents-and-incidents/a319-mumbai-india-2013 title: B738, Surat India, 2014 link: https://skybrary.aero/accidents-and-incidents/b738-surat-india-2014 description:

On 6 November 2014, a Boeing 737-800 taking off at night from Surat hit an object as it was approaching 80 knots and the take-off was immediately rejected. On return to the gate substantial damage was found to the left engine and a runway inspection found one dead buffalo and another live one. The runway was reopened after removal of the carcass but the live buffalo was not removed and was seen again by the runway the following day. The Investigation found a history of inadequate perimeter fencing and inadequate runway inspection practices at the airport.

guid: https://skybrary.aero/accidents-and-incidents/b738-surat-india-2014 uri: https://skybrary.aero/accidents-and-incidents/b738-surat-india-2014 title: AT43, vicinity Fond-du-Lac SK Canada, 2017 link: https://skybrary.aero/accidents-and-incidents/at43-vicinity-fond-du-lac-sk-canada-2017 description:

On 13 December 2017, control of an ATR 42-300 was lost just after it became airborne at night from Fond-du-Lac and it was destroyed by the subsequent terrain impact. Ten occupants sustained serious injuries from which one later died and all others sustained minor injuries. The Investigation found that the accident was primarily attributable to pre-takeoff ice contamination of the airframe with an inappropriate pilot response then preventing an achievable recovery. It was found that significant airframe ice accretion had gone undetected during an inadequate pre-flight inspection and that there was a more widespread failure to recognise airframe icing risk.

guid: https://skybrary.aero/accidents-and-incidents/at43-vicinity-fond-du-lac-sk-canada-2017 uri: https://skybrary.aero/accidents-and-incidents/at43-vicinity-fond-du-lac-sk-canada-2017 title: FA7X, London City UK, 2016 link: https://skybrary.aero/accidents-and-incidents/fa7x-london-city-uk-2016 description:

On 24 November 2016, a Dassault Falcon 7X being marshalled into an unmarked parking position after arriving at London City Airport was inadvertently directed into a collision with another crewed but stationary aircraft which sustained significant damage. The Investigation found that the apron involved had been congested and that the aircraft was being marshalled in accordance with airport procedures with wing walker assistance but a sharp corrective turn which created a 'wing growth' effect created a collision risk that was signalled at the last minute and incorrectly so by the wing walker involved and was also not seen by the marshaller.

guid: https://skybrary.aero/accidents-and-incidents/fa7x-london-city-uk-2016 uri: https://skybrary.aero/accidents-and-incidents/fa7x-london-city-uk-2016 title: B773, en-route, east northeast of Anchorage AK USA, 2015 link: https://skybrary.aero/accidents-and-incidents/b773-en-route-east-northeast-anchorage-ak-usa-2015 description:

On 30 December 2015, a Boeing 777-300 making an eastbound Pacific crossing en-route to Toronto encountered forecast moderate to severe clear air turbulence associated with a jet stream over mountainous terrain. Some passengers remained unsecured and were injured, one seriously and the flight diverted to Calgary. The Investigation found that crew action had mitigated the injury risk but that more could have been achieved. It was also found that the pilots had not been in possession of all relevant information and that failure of part of the air conditioning system during the turbulence was due to an improperly installed clamp.

guid: https://skybrary.aero/accidents-and-incidents/b773-en-route-east-northeast-anchorage-ak-usa-2015 uri: https://skybrary.aero/accidents-and-incidents/b773-en-route-east-northeast-anchorage-ak-usa-2015 title: A343, Tabriz Iran, 2013 link: https://skybrary.aero/accidents-and-incidents/a343-tabriz-iran-2013 description:

On 18 April 2013, an Airbus A340-300 was unintentionally taxied off the side of the runway during a 180° turn after backtracking the departure runway at Tabriz at night. The Investigation found that the prevailing wet runway conditions meant that the runway width alone was insufficient for the turn and full advantage had not been taken of a wide taxiway at the runway displaced threshold. It was also found that the technique used to turn had not been optimum and that the runway involved was for daylight use only and had a strength rating not compatible with A340 use.

guid: https://skybrary.aero/accidents-and-incidents/a343-tabriz-iran-2013 uri: https://skybrary.aero/accidents-and-incidents/a343-tabriz-iran-2013 title: B738, Barcelona Spain, 2015 link: https://skybrary.aero/accidents-and-incidents/b738-barcelona-spain-2015 description:

On 12 December 2015, whilst a Boeing 737-800 was beginning disembarkation of passengers via an air bridge which had just been attached on arrival at Barcelona, the bridge malfunctioned, raising the aircraft nose gear approximately 2 metres off the ground. The door attached to the bridge then failed and the aircraft dropped abruptly. Prompt cabin crew intervention prevented all but two minor injuries. The Investigation found that the occurrence had been made possible by the failure to recognise new functional risks created by a programme of partial renovation being carried out on the air bridges at the Terminal involved.

guid: https://skybrary.aero/accidents-and-incidents/b738-barcelona-spain-2015 uri: https://skybrary.aero/accidents-and-incidents/b738-barcelona-spain-2015 title: A306, Yerevan Armenia, 2015 link: https://skybrary.aero/accidents-and-incidents/a306-yerevan-armenia-2015 description:

On 17 May 2015, an Airbus A300-600 crew descended their aircraft below the correct vertical profile on a visual daytime approach at Yerevan and then landed on a closed section of the runway near the displaced runway threshold. The Investigation found that the crew had failed to review relevant AIS information prior to departing from Tehran and had not been expecting anything but a normal approach and landing. The performance of the Dispatcher in respect of briefing and the First Officer in respect of failure to adequately monitor the Captain's flawed conduct of the approach was highlighted.

guid: https://skybrary.aero/accidents-and-incidents/a306-yerevan-armenia-2015 uri: https://skybrary.aero/accidents-and-incidents/a306-yerevan-armenia-2015 title: B734 / C172, vicinity Girona Spain, 2016 link: https://skybrary.aero/accidents-and-incidents/b734-c172-vicinity-girona-spain-2016 description:

On 28 September 2016, a Boeing 737-400 and a Cessna 172 both on IFR Flight Plans came into close proximity when about to turn final on the same non-precision approach at Girona from different initial joining routes. The Investigation found that two ACC sector controllers had issued conflicting approach clearances after losing situational awareness following a routine sector split due to an area ATC flow configuration change. The detection of the consequences of their error had then been hindered by a temporary area low level radar outage but helped by timely visual acquisition by both aircraft and a TCAS RA.

guid: https://skybrary.aero/accidents-and-incidents/b734-c172-vicinity-girona-spain-2016 uri: https://skybrary.aero/accidents-and-incidents/b734-c172-vicinity-girona-spain-2016 title: AT72, Karup Denmark, 2016 link: https://skybrary.aero/accidents-and-incidents/at72-karup-denmark-2016 description:

On 25 January 2016, an ATR 72-200 crew departing from and very familiar with Karup aligned their aircraft with the runway edge lights instead of the lit runway centreline and began take-off, only realising their error when they collided with part of the arrester wire installation at the side of the runway after which the take-off was rejected. The Investigation attributed the error primarily to the failure of the pilots to give sufficient priority to ensuring adequate positional awareness and given the familiarity of both pilots with the aerodrome noted that complacency had probably been a contributor factor.

guid: https://skybrary.aero/accidents-and-incidents/at72-karup-denmark-2016 uri: https://skybrary.aero/accidents-and-incidents/at72-karup-denmark-2016 title: B738, Singapore, 2015 link: https://skybrary.aero/accidents-and-incidents/b738-singapore-2015 description:

On 6 December 2015, a Boeing 737-800 was being manoeuvred by tug from its departure gate at Singapore to the position where it was permitted to commence taxiing under its own power when the tug lost control of the aircraft, the tow bar broke and the two collided. The Investigation attributed the collision to the way the tug was used and concluded that the thrust during and following engine start was not a contributory factor. Some inconsistency was found between procedures for push back of loaded in-service aircraft promulgated by the airline, its ground handling contractor and the airport operator.

guid: https://skybrary.aero/accidents-and-incidents/b738-singapore-2015 uri: https://skybrary.aero/accidents-and-incidents/b738-singapore-2015 title: B743, vicinity Tehran Mehrabad Iran, 2015 link: https://skybrary.aero/accidents-and-incidents/b743-vicinity-tehran-mehrabad-iran-2015 description:

On 15 October 2015 a Boeing 747-300 experienced significant vibration from one of the engines almost immediately after take-off from Tehran Mehrabad. After the climb out was continued without reducing the affected engine thrust an uncontained failure followed 3 minutes later. The ejected debris caused the almost simultaneous failure of the No 4 engine, loss of multiple hydraulic systems and all the fuel from one wing tank. The Investigation attributed the vibration to the Operator's continued use of the engine without relevant Airworthiness Directive action and the subsequent failure to continued operation of the engine after its onset.

guid: https://skybrary.aero/accidents-and-incidents/b743-vicinity-tehran-mehrabad-iran-2015 uri: https://skybrary.aero/accidents-and-incidents/b743-vicinity-tehran-mehrabad-iran-2015 title: A320 / A321, vicinity Barcelona Spain, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-a321-vicinity-barcelona-spain-2016 description:

On 25 July 2016, an Airbus A320 and an Airbus A321 both departing Barcelona and following their ATC instructions came into conflict and the collision risk was removed by the TCAS RA CLIMB response of the A320. Minimum separation was 1.2 nm laterally and 200 feet vertically with visual acquisition of the other traffic by both aircraft. The Investigation found that the controller involved had become preoccupied with an inbound traffic de-confliction task elsewhere in their sector and, after overlooking the likely effect of the different rates of climb of the aircraft, had not regarded monitoring their separation as necessary.

guid: https://skybrary.aero/accidents-and-incidents/a320-a321-vicinity-barcelona-spain-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-a321-vicinity-barcelona-spain-2016 title: B463, Khark Island Iran, 2016 link: https://skybrary.aero/accidents-and-incidents/b463-khark-island-iran-2016 description:

On 19 June 2016, a BAe 146-300 landed long at Khark Island and overran the end of the runway at speed with the aircraft only stopping because the nose landing gear collapsed on encountering uneven ground. The Investigation attributed the accident - which caused enough structural damage for the aircraft to be declared a hull loss - entirely to the decisions and actions of the aircraft commander who failed to go around from an unstabilised approach, landed long and then did not ensure maximum deceleration was achieved. The monitoring role of the low experience First Officer was ineffective.

guid: https://skybrary.aero/accidents-and-incidents/b463-khark-island-iran-2016 uri: https://skybrary.aero/accidents-and-incidents/b463-khark-island-iran-2016 title: B737, New York La Guardia USA, 2016 link: https://skybrary.aero/accidents-and-incidents/b737-new-york-la-guardia-usa-2016 description:

On 27 October 2016, a Boeing 737-700 crew made a late touchdown on the runway at La Guardia and did not then stop before reaching the end of the runway and entered - and exited the side of - the EMAS before stopping. The Investigation concluded that the overrun was the consequence of a failure to go around when this was clearly necessary after a mishandled touchdown and that the Captain's lack of command authority and a lack of appropriate crew training provided by the Operator to support flight crew decision making had contributed to the failure to go around.

guid: https://skybrary.aero/accidents-and-incidents/b737-new-york-la-guardia-usa-2016 uri: https://skybrary.aero/accidents-and-incidents/b737-new-york-la-guardia-usa-2016 title: A333, London Heathrow UK, 2016 link: https://skybrary.aero/accidents-and-incidents/a333-london-heathrow-uk-2016 description:

On 26 June 2016, thick white smoke suddenly appeared in the cabin of a fully loaded Airbus A330-300 prior to engine start with the door used for boarding still connected to the air bridge. An emergency evacuation initiated by cabin crew was accomplished without injury although amidst some confusion due to a brief conflict between flight crew and cabin crew instructions. The Investigation found that the smoke had been caused when an APU seal failed and hot oil entered the bleed air supply and pyrolysed. Safety Recommendations in respect of both crew communication and procedures and APU auto-shutdown were made.

guid: https://skybrary.aero/accidents-and-incidents/a333-london-heathrow-uk-2016 uri: https://skybrary.aero/accidents-and-incidents/a333-london-heathrow-uk-2016 title: D328, Sumburgh Shetland Islands UK, 2017 link: https://skybrary.aero/accidents-and-incidents/d328-sumburgh-shetland-islands-uk-2017 description:

On 26 January 2017, an EASA Test Pilot carrying out certification test flying to extend the Dornier 328's maximum demonstrated crosswind was unable to retain control during an intended full stop landing on runway 09 at Sumburgh and it departed the side of the runway onto soft ground and stopped abruptly. The Investigation noted the Test Pilot's total type experience was the three circuits immediately prior to the excursion and attributed it to inappropriate flight control inputs and power lever movements. Intervention on the power levers by the aircraft commander had not been enough to prevent the excursion.

guid: https://skybrary.aero/accidents-and-incidents/d328-sumburgh-shetland-islands-uk-2017 uri: https://skybrary.aero/accidents-and-incidents/d328-sumburgh-shetland-islands-uk-2017 title: A343 / RJ1H, Copenhagen Denmark, 2016 link: https://skybrary.aero/accidents-and-incidents/a343-rj1h-copenhagen-denmark-2016 description:

On 26 December 2016, the wing of an Airbus A340-300 being repositioned by towing at Copenhagen as cleared hit an Avro RJ100 which had stopped short of its stand when taxiing due to the absence of the expected ground crew. The RJ100 had been there for twelve minutes at the time of the collision. The Investigation attributed the collision to differing expectations of the tug driver, the Apron controller and the RJ100 flight crew within an overall context of complacency on the part of the tug driver whilst carrying out what would have been regarded as a routine, non-stressful task.

guid: https://skybrary.aero/accidents-and-incidents/a343-rj1h-copenhagen-denmark-2016 uri: https://skybrary.aero/accidents-and-incidents/a343-rj1h-copenhagen-denmark-2016 title: FA20, vicinity Kish Island Iran, 2014 link: https://skybrary.aero/accidents-and-incidents/fa20-vicinity-kish-island-iran-2014 description:

On 3 March 2014, a Dassault Falcon 20 engaged in navigation aid calibration for the Regulator was flown into the sea near Kish Island in dark night conditions. The Investigation concluded that the available evidence indicated that the aircraft had been inadvertently flown into the sea as the consequence of the crew experiencing somatogravic illusion. It was also noted that the absence of a functioning radio altimeter and pilot fatigue attributable to the long duty period was likely to have exacerbated the pilots' vulnerability to this illusion.

guid: https://skybrary.aero/accidents-and-incidents/fa20-vicinity-kish-island-iran-2014 uri: https://skybrary.aero/accidents-and-incidents/fa20-vicinity-kish-island-iran-2014 title: B773, Lisbon Portugal, 2016 link: https://skybrary.aero/accidents-and-incidents/b773-lisbon-portugal-2016 description:

On 13 January 2016 ice was found on the upper and lower wing surfaces of a Boeing 777-300ER about to depart in the late morning from Lisbon in CAVOK conditions and 10°C. As Lisbon had no de-ice facilities, it was towed to a location where the sun would melt the ice more quickly but during poorly-planned manoeuvring, one of the wingtips was damaged by contact with an obstruction. The Investigation attributed the ice which led to the problematic re-positioning to the operator’s policy of tankering most of the return fuel on the overnight inbound flight where it had become cold-soaked.

guid: https://skybrary.aero/accidents-and-incidents/b773-lisbon-portugal-2016 uri: https://skybrary.aero/accidents-and-incidents/b773-lisbon-portugal-2016 title: B734, Lahore Pakistan, 2015 link: https://skybrary.aero/accidents-and-incidents/b734-lahore-pakistan-2015 description:

On 3 November 2015, a Boeing 737-400 continued an unstabilised day approach to Lahore. When only the First Officer could see the runway at MDA, he took over from the Captain but the Captain took it back when subsequently sighting it. Finally, the First Officer took over again and landed after recognising that the aircraft was inappropriately positioned. Both main gear assemblies collapsed as the aircraft veered off the runway. The Investigation attributed the first collapse to the likely effect of excessive shimmy damper play and the second collapse to the effects of the first aggravated by leaving the runway.

guid: https://skybrary.aero/accidents-and-incidents/b734-lahore-pakistan-2015 uri: https://skybrary.aero/accidents-and-incidents/b734-lahore-pakistan-2015 title: A320, Singapore, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-singapore-2015 description:

On 16 October 2015, the unlatched fan cowl doors of the left engine on an A320 fell from the aircraft during and soon after takeoff. The one which remained on the runway was not recovered for nearly an hour afterwards despite ATC awareness of engine panel loss during takeoff and as the runway remained in use, by the time it was recovered it had been reduced to small pieces. The Investigation attributed the failure to latch the cowls shut to line maintenance and the failure to detect the condition to inadequate inspection by both maintenance personnel and flight crew.

guid: https://skybrary.aero/accidents-and-incidents/a320-singapore-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-singapore-2015 title: A140, vicinity Tehran Mehrabad Iran, 2014 link: https://skybrary.aero/accidents-and-incidents/a140-vicinity-tehran-mehrabad-iran-2014 description:

On 10 August 2014, one of the engines of an Antonov 140-100 departing Tehran Mehrabad ran down after V1 and prior to rotation. The takeoff was continued but the crew were unable to keep control and the aircraft stalled and crashed into terrain near the airport. The Investigation found that a faulty engine control unit had temporarily malfunctioned and that having taken off with an inappropriate flap setting, the crew had attempted an initial climb with a heavy aircraft without the failed engine propeller initially being feathered, with the gear remaining down and with the airspeed below V2.

guid: https://skybrary.aero/accidents-and-incidents/a140-vicinity-tehran-mehrabad-iran-2014 uri: https://skybrary.aero/accidents-and-incidents/a140-vicinity-tehran-mehrabad-iran-2014 title: B738, Katowice Poland, 2007 link: https://skybrary.aero/accidents-and-incidents/b738-katowice-poland-2007 description:

On 28 October 2007, a Boeing 737-800 under the command of a Training Captain occupying the supernumerary crew seat touched down off an ILS Cat 1 approach 870 metres short of the runway at Katowice in fog at night with the AP still engaged. The somewhat protracted investigation did not lead to a Final Report until over 10 years later. This attributed the accident to crew failure to discontinue an obviously unstable approach and it being flown with RVR below the applicable minima. The fact that the commander was not seated at the controls was noted with concern.

guid: https://skybrary.aero/accidents-and-incidents/b738-katowice-poland-2007 uri: https://skybrary.aero/accidents-and-incidents/b738-katowice-poland-2007 title: AT76, Dublin Ireland, 2015 link: https://skybrary.aero/accidents-and-incidents/at76-dublin-ireland-2015 description:

On 23 July 2015, an ATR72-600 crew suspected their aircraft was unduly tail heavy in flight. After the flight they found that all passenger baggage had been loaded in the aft hold whereas the loadsheet indicated that it was all in the forward hold. The Investigation found that the person responsible for hold loading as specified had failed do so and that this failure had not been detected by the supervising Dispatcher who had certified the loadsheet presented to the aircraft Captain. Similar loading errors, albeit all corrected prior to flight, were found by the Operator to be not uncommon.

guid: https://skybrary.aero/accidents-and-incidents/at76-dublin-ireland-2015 uri: https://skybrary.aero/accidents-and-incidents/at76-dublin-ireland-2015 title: DH8D, Kathmandu Nepal, 2018 link: https://skybrary.aero/accidents-and-incidents/dh8d-kathmandu-nepal-2018 description:

On 12 March 2018, a Bombardier DHC8-400 departed the side of landing runway 20 at Kathmandu after erratic visual manoeuvring which followed a mis-flown non-precision approach to the opposite runway direction and was destroyed. The Investigation concluded that the accident was a consequence of disorientation and loss of situational awareness on the part of the Captain and attributed his poor performance to his unfitness to fly due to mental instability. A history of depression which had led to his release from service as a military pilot and a subsequent period of absence from any employment as a pilot was noted.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-kathmandu-nepal-2018 uri: https://skybrary.aero/accidents-and-incidents/dh8d-kathmandu-nepal-2018 title: A321 / B738, en-route, south eastern Bulgaria, 2016 link: https://skybrary.aero/accidents-and-incidents/a321-b738-en-route-south-eastern-bulgaria-2016 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a321-b738-en-route-south-eastern-bulgaria-2016 uri: https://skybrary.aero/accidents-and-incidents/a321-b738-en-route-south-eastern-bulgaria-2016 title: A321, Fuerteventura Spain, 2016 link: https://skybrary.aero/accidents-and-incidents/a321-fuerteventura-spain-2016 description:

On 16 July 2016, an Airbus A321’s unstabilised approach at Fuerteventura during pilot line training was not discontinued and takeover of control and commencement of a go-around had occurred just before a very hard runway contact. The subsequent landing was successful but serious damage to the main landing gear was not rectified before the next flight. The Investigation found that the hard touchdown had been recorded as in excess of 3.3g and that the return flight had been “risky and unsafe” after failure of the Captain and maintenance personnel at the Operator to recognise the seriousness of the hard landing.

guid: https://skybrary.aero/accidents-and-incidents/a321-fuerteventura-spain-2016 uri: https://skybrary.aero/accidents-and-incidents/a321-fuerteventura-spain-2016 title: DH8C, vicinity Adelaide Australia, 2015 link: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-adelaide-australia-2015 description:

On 24 April 2015, a Bombardier DHC8-300 making an RNAV approach at Adelaide in IMC with the AP engaged went below the procedure vertical profile. An EGPWS ‘PULL UP’ Warning was triggered at 5½nm out and the approach was discontinued reportedly due to “spurious instrument indications”. The Investigation found that the premature descent had occurred when mode re-selection after a Flight Director dropout had been incorrect with VS active instead of VNAV. It was found that both pilots had assessed the ‘PULL UP’ Warning as “spurious” and a missed approach rather than the mandated terrain avoidance procedure had been flown.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-adelaide-australia-2015 uri: https://skybrary.aero/accidents-and-incidents/dh8c-vicinity-adelaide-australia-2015 title: SB20, en-route, Muzzano Switzerland, 2013 link: https://skybrary.aero/accidents-and-incidents/sb20-en-route-muzzano-switzerland-2013 description:

On 28 November 2013, a Saab 2000 departing Lugano suffered an engine failure for no apparent reason and the crew determined that diversion to Milan was preferable to return to Lugano or continued climb over high terrain to reach intended destination Zurich. The Investigation found that the loss of engine power experienced was due to a double FADEC failure with a transient malfunction of one channel resulting in an automated transfer to the other channel which already had an undetected permanent fault attributable to maintenance error. It was noted that the airline involved had contracted out all continuing airworthiness responsibilities.

guid: https://skybrary.aero/accidents-and-incidents/sb20-en-route-muzzano-switzerland-2013 uri: https://skybrary.aero/accidents-and-incidents/sb20-en-route-muzzano-switzerland-2013 title: RJ1H, vicinity Gothenburg Sweden, 2016 link: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-gothenburg-sweden-2016 description:

On 7 November 2016, severe airframe vibrations occurred to an Avro RJ-100 which, following ground de icing, was accelerating in the climb a few minutes after departing from Gothenburg. The crew were able to stop the vibrations by reducing speed but they declared an emergency and returned to land where significant quantities of ice were found and considered to have been the cause of the vibrations. The Investigation concluded that the failure of the de icing operation in this case had multiple origins which were unlikely to be location specific and generic safety recommendations were therefore made.

guid: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-gothenburg-sweden-2016 uri: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-gothenburg-sweden-2016 title: A332, en-route, near Bangka Island Indonesia, 2016 link: https://skybrary.aero/accidents-and-incidents/a332-en-route-near-bangka-island-indonesia-2016 description:

On 4 May 2016, an Airbus A330-200 in the cruise in day VMC at FL390 in the vicinity of a highly active thunderstorm cell described by the crew afterwards as ‘cumulus cloud’ encountered a brief episode of severe clear air turbulence which injured 24 passengers and crew, seven of them seriously as well as causing some damage to cabin fittings and equipment. The Investigation was unable to determine how close to the cloud the aircraft had been but noted the absence of proactive risk management and that most of the injured occupants had not been secured in their seats.

guid: https://skybrary.aero/accidents-and-incidents/a332-en-route-near-bangka-island-indonesia-2016 uri: https://skybrary.aero/accidents-and-incidents/a332-en-route-near-bangka-island-indonesia-2016 title: AT43, vicinity Oksibil Papua Indonesia, 2015 link: https://skybrary.aero/accidents-and-incidents/at43-vicinity-oksibil-papua-indonesia-2015 description:

On 26 August 2015, contact was lost with an ATR 42-300 making a descent to Oksibil supposedly using detailed Company-provided visual approach guidance over mountainous terrain. Its burnt out wreckage was subsequently located 10 nm from the airport at 4,300 feet aal. The Investigation found that the prescribed guidance had not been followed and that the Captain had been in the habit of disabling the EGPWS to prelude nuisance activations. It was concluded that a number of safety issues identified collectively indicated that the organisational oversight of the aircraft operator by the regulator was ineffective.

guid: https://skybrary.aero/accidents-and-incidents/at43-vicinity-oksibil-papua-indonesia-2015 uri: https://skybrary.aero/accidents-and-incidents/at43-vicinity-oksibil-papua-indonesia-2015 title: A320 / SW4, Calgary AB Canada, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-sw4-calgary-ab-canada-2016 description:

On 2 December 2016, the crew of an Airbus A320 passing 100 knots on takeoff at Calgary saw another aircraft crossing an intersection ahead but continued because they considered that, as the other aircraft was already more than half way across, it would be clear before they reached that point. The Investigation found that the GND Controller had cleared the other aircraft to cross after forgetting that the runway was active and under TWR control. It was concluded that the response of the ANSP SMS process to a history of identical controller errors and related reports had been inadequate.

guid: https://skybrary.aero/accidents-and-incidents/a320-sw4-calgary-ab-canada-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-sw4-calgary-ab-canada-2016 title: A319, Santiago de Compostela Spain, 2016 link: https://skybrary.aero/accidents-and-incidents/a319-santiago-de-compostela-spain-2016 description:

On 10 October 2016, an Airbus 319 was cleared to divert to its first alternate after failing to land off its Cat II ILS approach at Porto and obliged to land at its second alternate with less than final reserve fuel after the first alternate declined acceptance due to lack of parking capacity. The Investigation concluded that adjacent ATC Unit coordination in respect of multiple diversions was inadequate and also found that the crew had failed to adequately appraise ATC of their fuel status. It also noted that the unsuccessful approach at the intended destination had violated approach ban visibility conditions.

guid: https://skybrary.aero/accidents-and-incidents/a319-santiago-de-compostela-spain-2016 uri: https://skybrary.aero/accidents-and-incidents/a319-santiago-de-compostela-spain-2016 title: B763, Warsaw Poland, 2011 link: https://skybrary.aero/accidents-and-incidents/b763-warsaw-poland-2011 description:

On 1 November 2011, a Boeing 767-300 landed at Warsaw with its landing gear retracted after declaring an emergency in anticipation of the possible consequences which in this event included an engine fire and a full but successful emergency evacuation. The Investigation attributed inability to achieve successful gear extension using either alternate system or free fall to crew failure to notice that the Battery Busbar CB which controlled power to the uplock release mechanism was tripped. Gear extension using the normal system had been precluded in advance by a partial hydraulic system failure soon after takeoff from New York.

guid: https://skybrary.aero/accidents-and-incidents/b763-warsaw-poland-2011 uri: https://skybrary.aero/accidents-and-incidents/b763-warsaw-poland-2011 title: C402, Virgin Gorda British Virgin Islands, 2017 link: https://skybrary.aero/accidents-and-incidents/c402-virgin-gorda-british-virgin-islands-2017 description:

On 11 February 2017, a Cessna 402 failed to stop on the runway when landing at Virgin Gorda and was extensively damaged. The Investigation noted that the landing distance required was very close to that available with no safety margin so that although touchdown was normal, when the brakes failed to function properly, there was no possibility of safely rejecting the landing or stopping normally on the runway. Debris in the brake fluid was identified as causing brake system failure. The context was considered as the Operator s inadequate maintenance practices and a likely similar deficiency in operational procedures and processes.

guid: https://skybrary.aero/accidents-and-incidents/c402-virgin-gorda-british-virgin-islands-2017 uri: https://skybrary.aero/accidents-and-incidents/c402-virgin-gorda-british-virgin-islands-2017 title: DH8D / DH8D, vicinity Sudbury ON Canada, 2016 link: https://skybrary.aero/accidents-and-incidents/dh8d-dh8d-vicinity-sudbury-canada-2016 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-dh8d-vicinity-sudbury-canada-2016 uri: https://skybrary.aero/accidents-and-incidents/dh8d-dh8d-vicinity-sudbury-canada-2016 title: SF34, Moruya NSW Australia, 2015 link: https://skybrary.aero/accidents-and-incidents/sf34-moruya-nsw-australia-2015 description:

On 9 January 2015, a Saab 340B encountered a flock of medium-sized birds soon after decelerating through 80 knots during its landing roll at Moruya. A subsequent flight crew inspection in accordance with the prevailing operator procedures concluded that the aircraft could continue in service but after completion of the next flight, a propeller blade tip was found to be missing. The Investigation concluded that the blade failure was a result of the earlier bird impact and found that airline procedures allowing pilots to determine continued airworthiness after a significant birdstrike had unknowingly been invalid.

guid: https://skybrary.aero/accidents-and-incidents/sf34-moruya-nsw-australia-2015 uri: https://skybrary.aero/accidents-and-incidents/sf34-moruya-nsw-australia-2015 title: SF34, Marsh Harbour Bahamas, 2013 link: https://skybrary.aero/accidents-and-incidents/sf34-marsh-harbour-bahamas-2013 description:

On 13 June 2013, a rushed and unstable visual approach to Marsh Harbour by a Saab 340B was followed by a mishandled landing and a runway excursion. The Investigation concluded that the way the aircraft had been operated had been contrary to expectations in almost every respect. This had set the scene for the continuation of a visual approach to an attempted landing in circumstances where there had been multiple indications that there was no option but to break off the approach, including a total loss of forward visibility in very heavy rain as the runway neared.

guid: https://skybrary.aero/accidents-and-incidents/sf34-marsh-harbour-bahamas-2013 uri: https://skybrary.aero/accidents-and-incidents/sf34-marsh-harbour-bahamas-2013 title: B737, en-route, northwest of Philadelphia PA USA, 2018 link: https://skybrary.aero/accidents-and-incidents/b737-en-route-northwest-philadelphia-pa-usa-2018 description:

On 17 April 2018, sudden uncontained left engine failure occurred to a CFM56-7B powered Boeing 737-700 when climbing through approximately FL320. Consequent damage included a broken cabin window causing rapid decompression and a passenger fatality. Diversion to Philadelphia without further significant event then followed. A single fan blade was found to have failed due to undetected fatigue. The Investigation noted that the full consequences of blade failure had not been identified during engine / airframe type certification nor fully recognised during investigation of an identical blade failure event in 2016 which had occurred to another of the same operator s 737-700s.

guid: https://skybrary.aero/accidents-and-incidents/b737-en-route-northwest-philadelphia-pa-usa-2018 uri: https://skybrary.aero/accidents-and-incidents/b737-en-route-northwest-philadelphia-pa-usa-2018 title: RJ85, vicinity Medellín International (Rionegro) Colombia, 2016 link: https://skybrary.aero/accidents-and-incidents/rj85-vicinity-medellin-international-rionegro-colombia-2016 description:

On 29 November 2016, a BAe Avro RJ85 failed to complete its night charter flight to Medellín (Rionegro) when all engines stopped due to fuel exhaustion and it crashed in mountainous terrain 10 nm from its intended destination killing almost all occupants. The Investigation noted the complete disregard by the aircraft commander of procedures essential for safe flight by knowingly departing with significantly less fuel onboard than required for the intended flight and with no apparent intention to refuel en route. It found that this situation arose in a context of a generally unsafe operation subject to inadequate regulatory oversight.

guid: https://skybrary.aero/accidents-and-incidents/rj85-vicinity-medellin-international-rionegro-colombia-2016 uri: https://skybrary.aero/accidents-and-incidents/rj85-vicinity-medellin-international-rionegro-colombia-2016 title: A320, Tehran Mehrabad Iran, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-tehran-mehrabad-iran-2016 description:

On 13 August 2016, an Airbus A320 departed the side of the runway at low speed during takeoff from Tehran Mehrabad and became immobilised in soft ground. The Investigation found that the Captain had not ensured that both engines were simultaneously stabilised before completing the setting of takeoff thrust and that his subsequent response to the resulting directional control difficulties had been inappropriate and decision to reject the takeoff too late to prevent the excursion. Poor CRM on the flight deck was identified as including but not limited to the First Officer’s early call to reject the takeoff being ignored.

guid: https://skybrary.aero/accidents-and-incidents/a320-tehran-mehrabad-iran-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-tehran-mehrabad-iran-2016 title: B734, en-route, east northeast of Tanegashima Japan, 2015 link: https://skybrary.aero/accidents-and-incidents/b734-en-route-east-northeast-tanegashima-japan-2015 description:

On 30 June 2015, both bleed air supplies on a Boeing 737-400 at FL370 failed in quick succession resulting in the loss of all pressurisation and, after making an emergency descent to 10,000 feet QNH, the flight was continued to the planned destination, Kansai. The Investigation found that both systems failed due to malfunctioning pre-cooler control valves and that these malfunctions were due to a previously identified risk of premature deterioration in service which had been addressed by an optional but recommended Service Bulletin which had not been taken up by the operator of the aircraft involved.

guid: https://skybrary.aero/accidents-and-incidents/b734-en-route-east-northeast-tanegashima-japan-2015 uri: https://skybrary.aero/accidents-and-incidents/b734-en-route-east-northeast-tanegashima-japan-2015 title: SF34, en-route, north of Edinburgh UK, 2017 link: https://skybrary.aero/accidents-and-incidents/sf34-en-route-north-edinburgh-uk-2017 description:

On 5 June 2017, a Saab 340B encountered an unexpected short period of severe in-cloud turbulence and icing soon after climbing through FL 100 on departure from Edinburgh and a temporary but constrained loss of pitch control occurred during which three successive Angle of Attack-triggered stick shaker activations occurred before the severity of the turbulence reduced and the intended climb could be resumed. The Investigation found that the crew had not responded to the problem in accordance with prescribed procedures and that at no time during the episode had they set Maximum Continuous Power to aid prompt and effective recovery.

guid: https://skybrary.aero/accidents-and-incidents/sf34-en-route-north-edinburgh-uk-2017 uri: https://skybrary.aero/accidents-and-incidents/sf34-en-route-north-edinburgh-uk-2017 title: GLF5, vicinity Hong Kong China, 2015 link: https://skybrary.aero/accidents-and-incidents/glf5-vicinity-hong-kong-china-2015 description:

On 13 January 2015, a Gulfstream G550 approaching Hong Kong on a positioning flight suddenly began rapidly descending without clearance and came within 500 feet of the sea surface before a recovery triggered by an EGPWS ‘PULL UP’ Warning had been accomplished. The Investigation found that the excursion resulted from an inadvertent and unrecognised elevator trim switch input which caused the autopilot to disconnect and that initiation of a recovery was delayed by the continued failure of all three pilots on the flight deck to determine the control status of the aircraft and was hindered by their ineffective CRM.

guid: https://skybrary.aero/accidents-and-incidents/glf5-vicinity-hong-kong-china-2015 uri: https://skybrary.aero/accidents-and-incidents/glf5-vicinity-hong-kong-china-2015 title: DH8B, en-route, west northwest of Port Moresby Papua New Guinea, 2017 link: https://skybrary.aero/accidents-and-incidents/dh8b-en-route-west-northwest-port-moresby-papua-new-guinea-2017 description:

On 4 August 2017, a de Havilland DHC8-200 was climbing through 20,000 feet after departing Port Moresby when a sudden loud bang occurred and the aircraft shuddered. Apart from a caution indicating an open main landing gear door, no other impediments to normal flight were detected. After a return to the point of departure, one of the main gear tyres was found to have exploded causing substantial damage to the associated engine structure and releasing debris. The Investigation concluded that tyre failure was attributable to FOD damage during an earlier landing on an inadequately maintained but approved compacted gravel runway.

guid: https://skybrary.aero/accidents-and-incidents/dh8b-en-route-west-northwest-port-moresby-papua-new-guinea-2017 uri: https://skybrary.aero/accidents-and-incidents/dh8b-en-route-west-northwest-port-moresby-papua-new-guinea-2017 title: A319, Ibiza Spain, 2016 link: https://skybrary.aero/accidents-and-incidents/a319-ibiza-spain-2016 description:

On 19 June 2016, an Airbus A320 failed to follow the clearly-specified and ground-marked self-positioning exit from a regularly used gate at Ibiza and its right wing tip collided with the airbridge, damaging both it and the aircraft. The Investigation found that the crew had attempted the necessary left turn using the Operator’s ‘One Engine Taxi Departure’ procedure using the left engine but then failed to follow the marked taxi guideline by a significant margin. It was noted that there had been no other such difficulties with the same departure in the previous four years it had been in use.

guid: https://skybrary.aero/accidents-and-incidents/a319-ibiza-spain-2016 uri: https://skybrary.aero/accidents-and-incidents/a319-ibiza-spain-2016 title: L410, Isle of Man, 2017 link: https://skybrary.aero/accidents-and-incidents/l410-isle-man-2017 description:

On 23 February 2017, a Czech-operated Let-410 departed from Isle of Man into deteriorating weather conditions and when unable to land at its destination returned and landed with a crosswind component approximately twice the certified limit. The local Regulatory Agency instructed ATC to order the aircraft to immediately stop rather than attempt to taxi and the carrier’s permit to operate between the Isle of Man and the UK was subsequently withdrawn. The Investigation concluded that the context for the event was a long history of inadequate operational safety standards associated with its remote provision of flights for a Ticket Seller.

guid: https://skybrary.aero/accidents-and-incidents/l410-isle-man-2017 uri: https://skybrary.aero/accidents-and-incidents/l410-isle-man-2017 title: A320, Lisbon Portugal, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-lisbon-portugal-2015 description:

On 19 May 2015, an Airbus A319 crew attempted to taxi into a nose-in parking position at Lisbon despite the fact that the APIS, although switched on, was clearly malfunctioning whilst not displaying an unequivocal ‘STOP’. The aircraft continued 6 metres past the applicable apron ground marking by which time it had hit the airbridge. The marshaller in attendance to oversee the arrival did not signal the aircraft or manually select the APIS ‘STOP’ instruction. The APIS had failed to detect the dark-liveried aircraft and the non-display of a steady ‘STOP’ indication was independently attributed to a pre-existing system fault.

guid: https://skybrary.aero/accidents-and-incidents/a320-lisbon-portugal-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-lisbon-portugal-2015 title: AT72, Zurich Switzerland, 2014 link: https://skybrary.aero/accidents-and-incidents/at72-zurich-switzerland-2014 description:

On 4 December 2014, directional control of an ATR 72-200 was compromised shortly after touchdown at Zurich after slightly misaligned nose wheels caused both tyres to be forced off their wheels leaving the wheel rims in direct contact with the runway surface. The Investigation found that the cause of the misalignment was the incorrect installation of a component several months earlier and the subsequent failure to identify the error. Previous examples of the same error were found and a Safety Recommendation was made that action to make the component involved less vulnerable to incorrect installation should be taken.

guid: https://skybrary.aero/accidents-and-incidents/at72-zurich-switzerland-2014 uri: https://skybrary.aero/accidents-and-incidents/at72-zurich-switzerland-2014 title: F100, Nuremburg Germany, 2015 link: https://skybrary.aero/accidents-and-incidents/f100-nuremburg-germany-2015 description:

On 20 January 2015, The APU of a Fokker 100 being routinely de-iced prior to departing Nuremburg oversped as a result of the ignition of ingested de-icing fluid in the APU. This led to its explosive uncontained failure as the result of which ejected debris entered the aft cabin and smoke occurred. No occupants were injured and all were promptly disembarked. The Investigation found that the de-icing contractor involved had not followed manufacturer-issued aircraft-specific de-icing procedures and in the continued absence of any applicable safety regulatory oversight of ground de-icing activity, corresponding Safety Recommendations were made.

guid: https://skybrary.aero/accidents-and-incidents/f100-nuremburg-germany-2015 uri: https://skybrary.aero/accidents-and-incidents/f100-nuremburg-germany-2015 title: SW4, en-route, North Vancouver BC Canada, 2015 link: https://skybrary.aero/accidents-and-incidents/sw4-en-route-north-vancouver-bc-canada-2015 description:

On 13 April 2015, a Swearingen SA226 Metro II which had recently departed on a cargo flight was climbing normally when it suddenly entered an unexplained and steep descent a few minutes after takeoff. There were no communications from the pilots. It was later found to have impacted terrain after a rate of descent exceeding 30,000 fpm had created aerodynamic forces which caused structural disintegration to begin before impact. The Investigation could not determine why but concluded that “alcohol intoxication almost certainly played a role” and noted that indications that the Captain was a chronic alcoholic had not prompted any intervention.

guid: https://skybrary.aero/accidents-and-incidents/sw4-en-route-north-vancouver-bc-canada-2015 uri: https://skybrary.aero/accidents-and-incidents/sw4-en-route-north-vancouver-bc-canada-2015 title: B738, Belfast International UK, 2017 link: https://skybrary.aero/accidents-and-incidents/b738-belfast-international-uk-2017 description:

On 21 July 2017, a Boeing 737-800 taking off from Belfast was only airborne near the runway end of the runway and then only climbed at a very shallow angle until additional thrust was eventually added. The Investigation found that the thrust set had been based on an incorrectly input surface temperature of -52°C, the expected top of climb temperature, instead of the actual surface temperature. Although inadequate acceleration had been detected before V1, the crew did not intervene. It was noted that neither the installed FMC software nor the EFBs in use were conducive to detection of the data input error.

guid: https://skybrary.aero/accidents-and-incidents/b738-belfast-international-uk-2017 uri: https://skybrary.aero/accidents-and-incidents/b738-belfast-international-uk-2017 title: B733, vicinity Kosrae Micronesia, 2015 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-kosrae-micronesia-2015 description:

On 12 June 2015, a Boeing 737-300 crew forgot to set QNH before commencing a night non-precision approach to Kosrae which was then flown using an over-reading altimeter. EGPWS Alerts occurred due to this mis-setting but were initially assessed as false. The third of these occurred when the eventual go-around was initially misflown and descent to within 200 feet of the sea occurred before climbing. The Investigation noted failure to action the approach checklist, the absence of ATC support and the step-down profile promulgated for the NDB/DME procedure flown as well as the potential effect of fatigue on the Captain.

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-kosrae-micronesia-2015 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-kosrae-micronesia-2015 title: B789 / A388, Singapore, 2017 link: https://skybrary.aero/accidents-and-incidents/b789-a388-singapore-2017 description:

On 30 March 2017, a Boeing 787 taxiing for departure at night at Singapore was involved in a minor collision with a stationary Airbus A380 which had just been pushed back from its gate and was also due to depart. The Investigation found that the conflict occurred because of poor GND controlling by a supervised trainee and had occurred because the 787 crew had exercised insufficient prudence when faced with a potential conflict with the A380. Safety Recommendations made were predominantly related to ATC procedures where it was considered that there was room for improvement in risk management.

guid: https://skybrary.aero/accidents-and-incidents/b789-a388-singapore-2017 uri: https://skybrary.aero/accidents-and-incidents/b789-a388-singapore-2017 title: A320, vicinity Tokyo Haneda Japan, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tokyo-haneda-japan-2016 description:

On 22 December 2016, an Airbus A320 cleared for a night approach to runway 16L at Haneda, which involved circling to the right from an initial VOR approach, instead turned left and began an approach to a closed but partially lit runway. ATC noticed and intervened to require a climb away for repositioning to the correct runway using radar vectors. The Investigation found that the context for the crew’s visual positioning error was their failure to adequately prepare for the approach before commencing it and that the new-on-type First Officer had not challenged the experienced Captain’s inappropriate actions and inactions.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tokyo-haneda-japan-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tokyo-haneda-japan-2016 title: A320, Toronto ON Canada, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-toronto-canada-2017 description:

On 25 February 2017, an Airbus A320 left the side of the landing runway at Toronto when, for undetermined reasons, the Captain, as Pilot Flying, set up a drift to the right just before touchdown. This was then followed by a lateral runway excursion into wet grass in rain-reduced visibility which continued for 1,650 metres before the aircraft regained the runway and stopped. The Investigation noted that both the absence of runway centreline lighting and the aircraft operator’s policy of not activating the aircraft rain repellent system or applying the alternative hydrophobic windshield coating may have increased the excursion risk.

guid: https://skybrary.aero/accidents-and-incidents/a320-toronto-canada-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-toronto-canada-2017 title: A320, Auckland New Zealand, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-auckland-new-zealand-2017 description:

On 27 October 2017, an Airbus A320 returned to Auckland after advice from ATC that the right engine may have been affected by ingestion of FOD during engine start - a clipboard and paper left just inside the right hand engine by an employee of the airline’s ground handling contractor acting as the aircraft loading supervisor. The subsequent inspection found paper throughout the engine and minor damage to an engine fan blade and the fan case attrition liner. The Dispatcher overseeing the departure said she had seen the clipboard inside the engine but assumed it would be retrieved before departure.

guid: https://skybrary.aero/accidents-and-incidents/a320-auckland-new-zealand-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-auckland-new-zealand-2017 title: L410, vicinity Lukla Nepal, 2017 link: https://skybrary.aero/accidents-and-incidents/l410-vicinity-lukla-nepal-2017 description:

On 27 May 2017, a Let 410 attempting to complete a visual approach to Lukla in rapidly deteriorating visibility descended below threshold altitude and impacted terrain close to the runway after stalling when attempting to climb in landing configuration. The aircraft was destroyed by the impact and two of the three occupants fatally injured. The Investigation concluded that the Captain had lost situational awareness at a critical time and had been slow to respond to the First Officer’s alert that the aircraft was too low. Safety Recommendations included the establishment of an independent and permanent Air Accident Investigation Agency.

guid: https://skybrary.aero/accidents-and-incidents/l410-vicinity-lukla-nepal-2017 uri: https://skybrary.aero/accidents-and-incidents/l410-vicinity-lukla-nepal-2017 title: A333 / A333, Narita International Japan, 2017 link: https://skybrary.aero/accidents-and-incidents/a333-a333-narita-international-japan-2017 description:

On 14 February 2017, an Airbus A330-300 preparing to depart Narita entered the active runway at night without clearance as another Airbus A330-300 was approaching the same runway with a landing clearance. ATC observed the conflict after an alert was activated on the surface display system and instructed the approaching aircraft, which was passing approximately 400 feet and had not observed the incursion, to go around. The Investigation attributed the departing aircraft crew’s failure to comply with their clearance to distraction and noted that the stop bar lighting system was not in use because procedures restricted its use to low visibility conditions.

guid: https://skybrary.aero/accidents-and-incidents/a333-a333-narita-international-japan-2017 uri: https://skybrary.aero/accidents-and-incidents/a333-a333-narita-international-japan-2017 title: E145, Sittwe Myanmar, 2017 link: https://skybrary.aero/accidents-and-incidents/e145-sittwe-myanmar-2017 description:

On 18 September 2017, an Embraer 145EP made a hard landing at Sittwe on the first of four flights that day. Clearly evident damage from what FDR data showed had been at least a 4.2g touchdown was not noticed during the pre-flight external inspection or during the two subsequent flights. Extensive structural damage was only identified during a routine overnight inspection. It was noted that one of the inspections which failed to detect damage had been carried out by a licensed engineer and that the aircraft Captain had at no stage reported or recorded a suspected hard landing.

guid: https://skybrary.aero/accidents-and-incidents/e145-sittwe-myanmar-2017 uri: https://skybrary.aero/accidents-and-incidents/e145-sittwe-myanmar-2017 title: JS41, Rhodes Greece, 2015 link: https://skybrary.aero/accidents-and-incidents/js41-rhodes-greece-2015 description:

On 2 February 2015, a Jetstream 41 made a hard and extremely fast touchdown at Rhodes and the left main gear leg collapsed almost immediately. The crew were able to prevent the consequent veer left from leading to a lateral runway excursion. The Investigation found that the approach had been significantly unstable throughout with touchdown at around 50 knots above what it should have been and that a whole range of relevant procedures had been violated by the management pilot who had flown the approach in wind shear conditions in which approaches to Rhodes were explicitly not recommended.

guid: https://skybrary.aero/accidents-and-incidents/js41-rhodes-greece-2015 uri: https://skybrary.aero/accidents-and-incidents/js41-rhodes-greece-2015 title: A320, Dublin Ireland, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-dublin-ireland-2017 description:

On 27 September 2017, an Airbus A320 being manoeuvred off the departure gate at Dublin by tug was being pulled forward when the tow bar shear pin broke and the tug driver lost control. The tug then collided with the right engine causing significant damage. The tug driver and assisting ground crew were not injured. The Investigation concluded that although the shear pin failure was not attributable to any particular cause, the relative severity of the outcome was probably increased by the wet surface, a forward slope on the ramp and fact that an engine start was in progress.

guid: https://skybrary.aero/accidents-and-incidents/a320-dublin-ireland-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-dublin-ireland-2017 title: C500, vicinity Kelowna BC Canada, 2016 link: https://skybrary.aero/accidents-and-incidents/c500-vicinity-kelowna-bc-canada-2016 description:

On 13 October 2016, a Cessna 500 crashed and was destroyed after an apparent loss of control shortly after taking off from Kelowna at night. In the absence of recorded flight data the Investigation was unable to explain the circumstances which led to loss of control but did identify significant safety concerns about both lack of progress in mandating the carriage of lightweight flight data recorders on small aircraft and a significant lack of effectiveness in the regulatory oversight of the business aviation sector in Canada.

guid: https://skybrary.aero/accidents-and-incidents/c500-vicinity-kelowna-bc-canada-2016 uri: https://skybrary.aero/accidents-and-incidents/c500-vicinity-kelowna-bc-canada-2016 title: B734, Timbuktu Mali, 2017 link: https://skybrary.aero/accidents-and-incidents/b734-timbuktu-mali-2017 description:

On 5 May 2017, a Boeing 737-400 made a visual approach to Timbuktu and slightly overran the end of the 2,170 metre-long runway into soft ground causing one of the engines to ingest significant quantities of damaging debris. The Investigation found that the landing had been made with a significantly greater than permitted tailwind component but that nevertheless had the maximum braking briefed been used, the unfactored landing distance required would have been well within that available. The preceding approach was found to have been comprehensively unstable throughout with no call for or intent to make a go around.

guid: https://skybrary.aero/accidents-and-incidents/b734-timbuktu-mali-2017 uri: https://skybrary.aero/accidents-and-incidents/b734-timbuktu-mali-2017 title: B772, en-route, northern Indian Ocean, 2014 link: https://skybrary.aero/accidents-and-incidents/b772-en-route-northern-indian-ocean-2014 description:

On 16 April 2014, a pre-flight concern about whether a Boeing 777-200ER about to depart Singapore had been overfuelled was resolved by a manual check but an en-route fuel system alert led to close monitoring of the fuel system. When a divergent discrepancy between the two independent fuel remaining sources became apparent, an uneventful precautionary air turnback was made and overfuelling subsequently confirmed. The Investigation found that a system fault had caused overfuelling and that the manual check carried out to confirm the actual fuel load had failed to detect it because it had been not been performed correctly.

guid: https://skybrary.aero/accidents-and-incidents/b772-en-route-northern-indian-ocean-2014 uri: https://skybrary.aero/accidents-and-incidents/b772-en-route-northern-indian-ocean-2014 title: B738, en-route, west of Canberra Australia, 2017 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-west-canberra-australia-2017 description:

On 13 March 2017, the crew of a Boeing 737-800 responded to an increase in indicated airspeed towards Vmo after changing the FMS mode during a high speed descent in a way that more abruptly disconnected the autopilot than they were anticipating which resulted in significant injuries to two of the cabin crew. The Investigation found that the operator s customary crew response to an overspeed risk at the airline concerned was undocumented in either airline or aircraft manufacturer procedures and had not been considered when an autopilot modification had been designed and implemented.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-west-canberra-australia-2017 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-west-canberra-australia-2017 title: B748, Prestwick UK, 2017 link: https://skybrary.aero/accidents-and-incidents/b748-prestwick-uk-2017 description:

On 30 March 2017, a significant amount of fuel was found to be escaping from a Boeing 747-8F as soon as it arrived on stand after landing at Prestwick and the fire service attended to contain the spill and manage the associated risk of fire and explosion. The Investigation found that the fuel had come from a Bell 412 helicopter that was part of the main deck cargo and that this had been certified as drained of fuel when it was not. The shipper s procedures, in particular in respect of their agents in the matter, were found to be deficient.

guid: https://skybrary.aero/accidents-and-incidents/b748-prestwick-uk-2017 uri: https://skybrary.aero/accidents-and-incidents/b748-prestwick-uk-2017 title: B773 / B738 / B738, Melbourne Australia, 2015 link: https://skybrary.aero/accidents-and-incidents/b773-b738-b738-melbourne-australia-2015 description:

On 5 July 2015, as a Boeing 777-300ER was departing Melbourne, two Boeing 737-800s which were initially on short final for intersecting runways with their ground separation dependent on one receiving a LAHSO clearance, went around. When both approaching aircraft did so, there was a loss of safe terrain clearance, safe separation and wake vortex separation between the three aircraft. The Investigation attributed the event to the actions of an inadequately supervised trainee controller and inappropriate intervention by a supervisory controller. It also identified a systemic safety issue generated by permitting LAHSO at night and a further flaw affecting the risk of all LAHSO at Melbourne.

guid: https://skybrary.aero/accidents-and-incidents/b773-b738-b738-melbourne-australia-2015 uri: https://skybrary.aero/accidents-and-incidents/b773-b738-b738-melbourne-australia-2015 title: A320 / AT76, Yangon Myanmar, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-at76-yangon-myanmar-2017 description:

On 18 September 2017, a departing Airbus A320 was instructed to line up and wait at Yangon but not given takeoff clearance until an ATR72 was less than a minute from touchdown and the prevailing runway traffic separation standard was consequently breached. The Investigation found that the TWR controller had been a temporarily unsupervised trainee who, despite good daylight visibility, had instructed the A320 to line up and wait and then forgotten about it. When the A320 crew, aware of the approaching ATR72, reminded her, she “did not know what to do” and the trainee APP controller had to intervene.

guid: https://skybrary.aero/accidents-and-incidents/a320-at76-yangon-myanmar-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-at76-yangon-myanmar-2017 title: B738, Sint Maarten Eastern Caribbean, 2017 link: https://skybrary.aero/accidents-and-incidents/b738-sint-maarten-eastern-caribbean-2017 description:

On 7 March 2017, a Boeing 737-800 crew making a daylight non-precision approach at Sint Maarten continued it without having established the required visual reference to continue beyond the missed approach point and then only realised that they had visually identified a building as the runway when visibility ahead suddenly improved. At this point the approach ground track was corrected but the premature descent which had inadvertently been allowed to occur was not noticed and only after the second of two EGPWS Alerts was a go-around initiated at 40 feet above the sea.

guid: https://skybrary.aero/accidents-and-incidents/b738-sint-maarten-eastern-caribbean-2017 uri: https://skybrary.aero/accidents-and-incidents/b738-sint-maarten-eastern-caribbean-2017 title: B738, Georgetown Guyana, 2011 link: https://skybrary.aero/accidents-and-incidents/b738-georgetown-guyana-2011 description:

On 30 July 2011, a Boeing 737-800 overran the wet landing runway at Georgetown after a night non-precision approach, exited the airport perimeter and descended down an earth embankment. There were no fatalities but the aircraft sustained substantial damage and was subsequently declared a hull loss. The Investigation attributed the overrun to a touchdown almost two thirds of the way down the runway and failure to utilise the aircraft s full deceleration capability. Loss of situational awareness and indecision as to the advisability of a go-around after a late touchdown became inevitable was also cited as contributory to the outcome.

guid: https://skybrary.aero/accidents-and-incidents/b738-georgetown-guyana-2011 uri: https://skybrary.aero/accidents-and-incidents/b738-georgetown-guyana-2011 title: B773, en-route, north northwest of Adelaide Australia, 2017 link: https://skybrary.aero/accidents-and-incidents/b773-en-route-north-northwest-adelaide-australia-2017 description:

On 14 October 2017, a Boeing 777-300ER en route to Sydney declared a MAYDAY and diverted to Adelaide after the annunciation of a lower deck hold fire warning and the concurrent detection of a burning smell in the flight deck. The remainder of the flight was completed without further event and after landing a precautionary rapid disembarkation was performed. The Investigation found that the fire risk had been removed by the prescribed crew response to the warning and that the burning which had occurred had been caused by chafing of a wiring loom misrouted at build.

guid: https://skybrary.aero/accidents-and-incidents/b773-en-route-north-northwest-adelaide-australia-2017 uri: https://skybrary.aero/accidents-and-incidents/b773-en-route-north-northwest-adelaide-australia-2017 title: B773, London Heathrow UK, 2016 link: https://skybrary.aero/accidents-and-incidents/b773-london-heathrow-uk-2016 description:

On 30 August 2016, a Boeing 777-300 crew began takeoff from London Heathrow at an intersection one third of the way along the runway using the reduced thrust calculated for a full-length take off instead of the rated thrust calculated for the intersection takeoff. As a result, the aircraft was only just airborne as it crossed the airport boundary and an adjacent public road. The Investigation attributed the data input error to crew failure to respond appropriately on finding that they had provisionally computed performance data based on different assumptions and concluded that the relevant Operator procedures were insufficiently robust.

guid: https://skybrary.aero/accidents-and-incidents/b773-london-heathrow-uk-2016 uri: https://skybrary.aero/accidents-and-incidents/b773-london-heathrow-uk-2016 title: B738 / B738, Toronto Canada, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-b738-toronto-canada-2018 description:

On 5 January 2018, an out of service Boeing 737-800 was pushed back at night into collision with an in-service Boeing 737-800 waiting on the taxiway for a marshaller to arrive and direct it onto the adjacent terminal gate. The first aircraft s tail collided with the second aircraft s right wing and a fire started. The evacuation of the second aircraft was delayed by non-availability of cabin emergency lighting. The Investigation attributed the collision to failure of the apron controller and pushback crew to follow documented procedures or take reasonable care to ensure that it was safe to begin the pushback.

guid: https://skybrary.aero/accidents-and-incidents/b738-b738-toronto-canada-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-b738-toronto-canada-2018 title: A333, en-route, southern Myanmar, 2013 link: https://skybrary.aero/accidents-and-incidents/a333-en-route-southern-myanmar-2013 description:

On 22 April 2013, a lower deck smoke warning occurred on an Airbus A330-300 almost 90 minutes into the cruise and over land. The warning remained on after the prescribed crew response and after an uneventful MAYDAY diversion was completed, the hold was found to be full of smoke and fire eventually broke out after all occupants had left the aircraft. The Investigation was unable to determine the fire origin but noted the success of the fire suppression system whilst the aircraft remained airborne and issues relating to the post landing response, especially communications with the fire service.

guid: https://skybrary.aero/accidents-and-incidents/a333-en-route-southern-myanmar-2013 uri: https://skybrary.aero/accidents-and-incidents/a333-en-route-southern-myanmar-2013 title: A333, vicinity Gold Coast Queensland Australia, 2017 link: https://skybrary.aero/accidents-and-incidents/a333-vicinity-gold-coast-queensland-australia-2017 description:

On 3 July 2017, an Airbus A330-300 was climbing through 2,300 feet after a night takeoff from Gold Coast when the number 2 engine began to malfunction. As a cabin report of fire in the same engine was received, it failed and a diversion to Brisbane was made. The Investigation found that the engine failure was entirely attributable to the ingestion of a single medium-sized bird well within engine certification requirements. It was concluded that the failure was the result of a sufficiently rare combination of circumstances that it would be extremely unlikely for multiple engines to be affected simultaneously.

guid: https://skybrary.aero/accidents-and-incidents/a333-vicinity-gold-coast-queensland-australia-2017 uri: https://skybrary.aero/accidents-and-incidents/a333-vicinity-gold-coast-queensland-australia-2017 title: B38M, en-route, northeast of Jakarta Indonesia, 2018 link: https://skybrary.aero/accidents-and-incidents/b38m-en-route-northeast-jakarta-indonesia-2018 description:

On 29 October 2018, a Lion Air Boeing 737-MAX 8 crew had difficulty controlling the pitch of their aircraft after takeoff from Jakarta and after eventually losing control, a high speed sea impact followed. The Investigation found that similar problems had also affected the aircraft s previous flight following installation of a faulty angle-of-attack sensor and after an incomplete post-flight defect entry, rectification had not occurred. Loss of control occurred because the faulty sensor was the only data feed to an undisclosed automatic pitch down system, MCAS, which had been installed on the 737-MAX variant without recognition of its potential implications.

guid: https://skybrary.aero/accidents-and-incidents/b38m-en-route-northeast-jakarta-indonesia-2018 uri: https://skybrary.aero/accidents-and-incidents/b38m-en-route-northeast-jakarta-indonesia-2018 title: B752, vicinity New York JFK USA, 2016 link: https://skybrary.aero/accidents-and-incidents/b752-vicinity-new-york-jfk-usa-2016 description:

On 7 July 2016, a right engine fire warning was annunciated as a Boeing 757-200 got airborne from New York JFK and after shutting the engine down in accordance with the corresponding checklist, an emergency declaration was followed by an immediate and uneventful return to land. After an external inspection confirmed there was no sign of an active fire, the aircraft was taxied to a terminal gate for normal disembarkation. The Investigation found that a fuel-fed fire had occurred because an O-ring had been incorrectly installed on a fuel tube during maintenance prior to the flight.

guid: https://skybrary.aero/accidents-and-incidents/b752-vicinity-new-york-jfk-usa-2016 uri: https://skybrary.aero/accidents-and-incidents/b752-vicinity-new-york-jfk-usa-2016 title: B734, Kabul Afghanistan, 2016 link: https://skybrary.aero/accidents-and-incidents/b734-kabul-afghanistan-2016 description:

On 10 December 2016, a Boeing 737-400 main gear leg collapsed on landing after an approach at excessive speed was followed by a prolonged float prior to touchdown on the high-altitude Kabul runway. The Investigation found that the collapse had followed a severe but very brief wheel shimmy episode in the presence of a number of factors conducive to this risk which the aircraft operator s pilots had not been trained to avoid. It was also found that although the aircraft operator regularly undertook wet lease contract flying, their pilot training policy did not include any route or aerodrome competency training.

guid: https://skybrary.aero/accidents-and-incidents/b734-kabul-afghanistan-2016 uri: https://skybrary.aero/accidents-and-incidents/b734-kabul-afghanistan-2016 title: B748, Amsterdam Netherlands, 2017 link: https://skybrary.aero/accidents-and-incidents/b748-amsterdam-netherlands-2017 description:

On 13 January 2017, a Boeing 747-8F arriving at Amsterdam at night in turbulent conditions initially touched down just short of landing runway 36R destroying runway threshold lights and causing minor damage to the aircraft which was subsequently observed after the aircraft had parked. The Investigation determined that a high rate of descent had developed towards the end of a previously stable approach and after this had led to EGPWS Glideslope and Sink Rate Alerts, a go-around was required under operator procedures but was not flown and an insufficient flare then led to a premature hard landing and bounce.

guid: https://skybrary.aero/accidents-and-incidents/b748-amsterdam-netherlands-2017 uri: https://skybrary.aero/accidents-and-incidents/b748-amsterdam-netherlands-2017 title: C130 / C27J, manoeuvring, near Mackall AAF NC USA, 2014 link: https://skybrary.aero/accidents-and-incidents/c130-c27j-manoeuvring-near-mackall-aaf-nc-usa-2014 description:

On 1 December 2014, a night mid-air collision occurred in uncontrolled airspace between a Lockheed C130H Hercules and an Alenia C27J Spartan conducting VFR training flights and on almost reciprocal tracks at the same indicated altitude after neither crew had detected the proximity risk. Substantial damage was caused but both aircraft were successfully recovered and there were no injuries. The Investigation attributed the collision to a lack of visual scan by both crews, over reliance on TCAS and complacency despite the inherent risk associated with night, low-level, VFR operations using the Night Vision Goggles worn by both crews.

guid: https://skybrary.aero/accidents-and-incidents/c130-c27j-manoeuvring-near-mackall-aaf-nc-usa-2014 uri: https://skybrary.aero/accidents-and-incidents/c130-c27j-manoeuvring-near-mackall-aaf-nc-usa-2014 title: DC10, Fort Lauderdale FL USA, 2017 link: https://skybrary.aero/accidents-and-incidents/dc10-fort-lauderdale-fl-usa-2017 description:

On 28 October 2017 the left main landing gear of an MD10-10F that had just touched down at Fort Lauderdale collapsed which led to the aircraft departing the side of the runway and catching fire. The Investigation found that the collapse had occurred because of metal fatigue which had developed in the absence of protective plating on part of the leg assembly. The reason for this could not be determined but it was noted that had the aircraft operator’s component overhaul interval not been longer than the corresponding manufacturer recommendation then the collapse would probably not have occurred.

guid: https://skybrary.aero/accidents-and-incidents/dc10-fort-lauderdale-fl-usa-2017 uri: https://skybrary.aero/accidents-and-incidents/dc10-fort-lauderdale-fl-usa-2017 title: B789, en-route, eastern Belgium, 2017 link: https://skybrary.aero/accidents-and-incidents/b789-en-route-eastern-belgium-2017 description:

On 29 April 2017, a Boeing 787-9 which had just reached cruise altitude after despatch with only one main ECS available began to lose cabin pressure. A precautionary descent and PAN was upgraded to a rapid descent and MAYDAY as cabin altitude rose above 10,000 feet. The Investigation found that aircraft release to service had not been preceded by a thorough enough validation of the likely reliability of the remaining ECS system. The inaudibility of the automated announcement accompanying the cabin oxygen mask drop and ongoing issues with the quality of CVR readout from 787 crash-protected recorders was also highlighted.

guid: https://skybrary.aero/accidents-and-incidents/b789-en-route-eastern-belgium-2017 uri: https://skybrary.aero/accidents-and-incidents/b789-en-route-eastern-belgium-2017 title: DC10, Macau SAR China, 2005 link: https://skybrary.aero/accidents-and-incidents/dc10-macau-sar-china-2005 description:

On 9 November 2005, a McDonnell Douglas DC10-30F almost failed to get airborne before the end of the runway on a night takeoff from Macau and its main landing gear then hit lighting and ILS equipment as it climbed at a very shallow angle. After flight, two wheel changes were required due to tyre damage. The Investigation was hindered by the failure of the State of the Operator to assist the Investigation but concluded that the aircraft had been correctly loaded and that the extended take off roll had been due to use of the wrong flap setting.

guid: https://skybrary.aero/accidents-and-incidents/dc10-macau-sar-china-2005 uri: https://skybrary.aero/accidents-and-incidents/dc10-macau-sar-china-2005 title: B773, Tokyo Haneda Japan, 2016 link: https://skybrary.aero/accidents-and-incidents/b773-tokyo-haneda-japan-2016 description:

On 27 May 2016, a Boeing 777-300 crew made a high speed rejected take off when departing from Tokyo after a number one engine failure warning was quickly followed by a fire warning for the same engine and ATC advice of fire visible. As the fire warning continued with the aircraft stopped, an emergency evacuation was ordered. The Investigation found that the engine failure and fire had occurred when the 1st stage disc of the High Pressure Turbine had suddenly failed as result of undetected fatigue cracking which had propagated from an undetected disc manufacturing fault.

guid: https://skybrary.aero/accidents-and-incidents/b773-tokyo-haneda-japan-2016 uri: https://skybrary.aero/accidents-and-incidents/b773-tokyo-haneda-japan-2016 title: B763 / A320, Delhi India, 2017 link: https://skybrary.aero/accidents-and-incidents/b763-a320-delhi-india-2017 description:

On 8 August 2017, a Boeing 767-300 departing Delhi was pushed back into a stationary and out of service Airbus A320 on the adjacent gate rendering both aircraft unfit for flight. The Investigation found that the A320 had been instructed to park on a stand that was supposed to be blocked, a procedural requirement if the adjacent stand is to be used by a wide body aircraft and although this error had been detected by the stand allocation system, the alert was not noticed, in part due to inappropriate configuration. It was also found that the pushback was commenced without wing walkers.

guid: https://skybrary.aero/accidents-and-incidents/b763-a320-delhi-india-2017 uri: https://skybrary.aero/accidents-and-incidents/b763-a320-delhi-india-2017 title: B772, en-route, southwest of Belfast UK, 2017 link: https://skybrary.aero/accidents-and-incidents/b772-en-route-southwest-belfast-uk-2017 description:

On 13 November 2017, fumes on a GE90-powered Boeing 777-200 sufficient to require flight crew oxygen mask use occurred as it descended towards London Heathrow. The flight was completed without further event. Subsequent engineering assessments twice led to release to service followed by recurrence and after the fourth such release, a left engine overheat was annunciated. After flight, a hole in the engine combustor case was found and the engine was removed for repair. The Investigation attributed the delayed identification of the causal fault to inappropriate guidance in the aircraft manufacturer s Fault Isolation Manual which was has since been amended.

guid: https://skybrary.aero/accidents-and-incidents/b772-en-route-southwest-belfast-uk-2017 uri: https://skybrary.aero/accidents-and-incidents/b772-en-route-southwest-belfast-uk-2017 title: B738, Christchurch New Zealand, 2015 link: https://skybrary.aero/accidents-and-incidents/b738-christchurch-new-zealand-2015 description:

On 11 May 2015, a Boeing 737-800 crew making a night landing at Christchurch had to react quickly when braking action deteriorated and only just succeeded in preventing an overrun. The Investigation found that a damp rather than wet runway had been assumed despite recent rain and that the aircraft operator had recently changed their procedures so that a damp runway should be considered as dry rather than wet for runway performance purposes. The questionable determination of the crew that the runway was likely to be damp, not wet, was attributed to a relatively high workload prior to final approach.

guid: https://skybrary.aero/accidents-and-incidents/b738-christchurch-new-zealand-2015 uri: https://skybrary.aero/accidents-and-incidents/b738-christchurch-new-zealand-2015 title: B738, vicinity Chuuk Micronesia, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-chuuk-micronesia-2018 description:

On 28 September 2018, a Boeing 737-800 was flown into the sea short of the intended landing runway at Chuuk during a non-precision approach which was continued below MDA without having obtained the required visual reference. The Investigation found that the Captain s approach had become unstable soon after autopilot disconnection and an excessive rate of descent had taken the aircraft below the indicated glideslope and below MDA despite multiple EGPWS Sink Rate aural Alerts and a visual-only PULL UP Warning with impact following 22 seconds after passing MDA. The absence of an aural PULL UP Warning was considered significant.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-chuuk-micronesia-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-chuuk-micronesia-2018 title: B738, Rome Ciampino Italy, 2008 link: https://skybrary.aero/accidents-and-incidents/b738-rome-ciampino-italy-2008 description:

On 10 November 2008, a Boeing 737-800 about to land at Rome Ciampino Airport flew through a large and dense flock of starlings, which appeared from below the aircraft. After the crew had made an unsuccessful attempt to go around, they lost control due to malfunction of both engines when full thrust was applied and a very hard impact half way along the runway caused substantial damage to the aircraft. The Investigation concluded that the Captain s decision to attempt a go around after the encounter was inappropriate and that bird risk management measures at the airport had been inadequate.

guid: https://skybrary.aero/accidents-and-incidents/b738-rome-ciampino-italy-2008 uri: https://skybrary.aero/accidents-and-incidents/b738-rome-ciampino-italy-2008 title: B789, Tel Aviv Israel, 2018 link: https://skybrary.aero/accidents-and-incidents/b789-tel-aviv-israel-2018 description:

On 29 March 2018, an augmented Boeing 787-9 crew completed an uneventful takeoff from Tel Aviv on a type conversion line check flight for one of the First Officers in the crew. After getting airborne, the crew found that all performance calculations including that for takeoff had been made on the basis of a Zero Fuel Weight which was 40 tonnes below the actual figure of 169 tonnes. The Investigation found that it was highly probable that automatic reduction in commanded pitch-up when rotation was attempted at too low a speed had prevented an accident during or soon after liftoff.

guid: https://skybrary.aero/accidents-and-incidents/b789-tel-aviv-israel-2018 uri: https://skybrary.aero/accidents-and-incidents/b789-tel-aviv-israel-2018 title: A343, Rio de Janeiro Galeão Brazil, 2011 link: https://skybrary.aero/accidents-and-incidents/a343-rio-de-janeiro-galeao-brazil-2011 description:

On 8 December 2011, an Airbus A340-300 did not become airborne until it had passed the end of the takeoff runway at Rio de Janeiro Galeão, which was reduced in length due to maintenance. The crew were unaware of this fact nor the consequent approach lighting, ILS antennae and aircraft damage, and completed their intercontinental flight. The Investigation found that the crew had failed to use the full available runway length despite relevant ATIS and NOTAM information and that even using rated thrust from where they began their takeoff, they would not have become airborne before the end of the runway.

guid: https://skybrary.aero/accidents-and-incidents/a343-rio-de-janeiro-galeao-brazil-2011 uri: https://skybrary.aero/accidents-and-incidents/a343-rio-de-janeiro-galeao-brazil-2011 title: B38M, en-route south east of Addis Ababa Ethiopia, 2019 link: https://skybrary.aero/accidents-and-incidents/b38m-en-route-south-east-addis-ababa-ethiopia-2019 description:

On 10 March 2019, a Boeing 738 MAX 8 left stick shaker activated immediately after takeoff from Addis Ababa for no apparent reason and remained on. A succession of four pitch down manoeuvres not initiated by the crew subsequently occurred and recovery from the final one was not achieved. Terrain impact followed a high speed dive six minutes after takeoff. The Investigation attributed the loss of control to an erroneous single source angle of attack input to the Manoeuvring Characteristics Augmentation System (MCAS) from which, in the absence of an applicable non-normal procedure or appropriate training, recovery was not achievable.

guid: https://skybrary.aero/accidents-and-incidents/b38m-en-route-south-east-addis-ababa-ethiopia-2019 uri: https://skybrary.aero/accidents-and-incidents/b38m-en-route-south-east-addis-ababa-ethiopia-2019 title: B77L, Paris CDG France, 2015 link: https://skybrary.aero/accidents-and-incidents/b77l-paris-cdg-france-2015 description:

On 22 May 2015, a Boeing 777F augmented crew attempted a reduced thrust daylight takeoff from Paris CDG using a thrust setting based on a weight 100 tonnes below the actual weight after an undetected crew error. The tailstrike protection system prevented fuselage runway contact after rotation attempts but only after a call from an augmenting crew member was full thrust set with the aircraft becoming airborne near the runway end. The Investigation noted poor crew performance but concluded that operator management of the risk involved and the corresponding regulatory oversight had been inadequate in a number of ways.

guid: https://skybrary.aero/accidents-and-incidents/b77l-paris-cdg-france-2015 uri: https://skybrary.aero/accidents-and-incidents/b77l-paris-cdg-france-2015 title: A320, vicinity Liverpool UK, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-liverpool-uk-2018 description:

On 24 June 2018, the Captain of an Airbus A320 which had just departed Liverpool inadvertently selected flaps/slats up when “gear up” was called. The error was quickly recognised and corrective action taken but the Investigation was unable to determine why the error occurred or identify circumstances directly conducive to it. It noted that they had previously investigated four similar events to the same operator’s A320s which had occurred over a period of less than 18 months with the operator introducing a requirement for a “pause” before gear or flap selection to allow time for positive checking before selector movement.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-liverpool-uk-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-liverpool-uk-2018 title: A319 / AS32, vicinity Marseille France, 2016 link: https://skybrary.aero/accidents-and-incidents/a319-as32-vicinity-marseille-france-2016 description:

On 27 June 2016, an Airbus A319 narrowly avoided a mid-air collision with an AS532 Cougar helicopter whose single transponder had failed earlier whilst conducting a local pre-delivery test flight whilst both were positioning visually as cleared to land at Marseille and after the helicopter had also temporarily disappeared from primary radar. Neither aircraft crew had detected the other prior to their tracks crossing at a similar altitude. The Investigation attributed the conflict to an inappropriate ATC response to the temporary loss of radar contact with the helicopter aggravated by inaccurate position reports and non-compliance with the aerodrome circuit altitude by the helicopter crew.

guid: https://skybrary.aero/accidents-and-incidents/a319-as32-vicinity-marseille-france-2016 uri: https://skybrary.aero/accidents-and-incidents/a319-as32-vicinity-marseille-france-2016 title: B744, en-route, southeast of Hong Kong SAR China, 2017 link: https://skybrary.aero/accidents-and-incidents/b744-en-route-southeast-hong-kong-sar-china-2017 description:

On 7 April 2017, a Boeing 747-400 crew did not adjust planned speed at an anticipated holding point when the level given was higher than expected. As a consequence of this and distraction, as the new holding level was approached and the turn began, stall buffet, several stick shaker activations and pilot-induced oscillations occurred when the crew failed to follow the applicable stall warning recovery procedure. Descent below the cleared level occurred and the upset caused injuries in the passenger cabin. Whilst attributing the event to poor crew performance, the Investigation also concluded that related operator pilot training was inadequate.

guid: https://skybrary.aero/accidents-and-incidents/b744-en-route-southeast-hong-kong-sar-china-2017 uri: https://skybrary.aero/accidents-and-incidents/b744-en-route-southeast-hong-kong-sar-china-2017 title: A320, vicinity Perth Australia, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-perth-australia-2015 description:

On 12 September 2015, an Airbus A320 autopilot and autothrust dropped out as it climbed out of Perth and multiple ECAM system messages were presented with intermittent differences in displayed airspeeds. During the subsequent turn back in Alternate Law, a stall warning was disregarded with no actual consequence. The Investigation attributed the problems to intermittently blocked pitot tubes but could not establish how this had occurred. It was also found that the priority for ECAM message display during the flight had been inappropriate and that the key procedure contained misleading information. These ECAM issues were subsequently addressed by the aircraft manufacturer.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-perth-australia-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-perth-australia-2015 title: DH8D, vicinity Belfast City UK, 2018 link: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-belfast-city-uk-2018 description:

On 11 January 2018, a Bombardier DHC8-400 departed Belfast City with incorrectly-set Flight Director (FD) modes and the Autopilot was then engaged without either pilot noticing that the aircraft was not being flown in accordance with the FD command bar or that the aircraft had then begun to descend. The rate of descent increased unnoticed and reached 4,300 fpm before recovery from a 928 feet minimum height after EGPWS 'DON'T SINK' and 'PULL UP' annunciations. The Investigation found that no target altitude had been entered and noted failure to follow normal operating procedures including on the use of checklists.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-belfast-city-uk-2018 uri: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-belfast-city-uk-2018 title: A332, en-route, mid Atlantic, 2013 link: https://skybrary.aero/accidents-and-incidents/a332-en-route-mid-atlantic-2013 description:

On 2 September 2013, an Airbus A330-200 crossing the ITCZ at FL400 at night encountered sudden severe turbulence unanticipated by the crew resulting in serious injuries to a few cabin crew / passengers and minor injuries to twelve others. An en route diversion to Fortaleza was made. The Investigation found that the origin of the turbulence was severe convective weather and failure to detect it in an area where it had been forecasted indicated that it was probably associated with sub-optimal use of the on-board weather radar with the severity of the encounter possibly aggravated by inappropriate contrary control inputs.

guid: https://skybrary.aero/accidents-and-incidents/a332-en-route-mid-atlantic-2013 uri: https://skybrary.aero/accidents-and-incidents/a332-en-route-mid-atlantic-2013 title: A320 / B738, vicinity Delhi India, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-delhi-india-2016 description:

On 30 January 2016, an Airbus A320 crew cleared for an ILS approach to runway 11 at Delhi reported established on the runway 11 LLZ but were actually on the runway 09 LLZ in error and continued on that ILS finally crossing in front of a Boeing 737-800 on the ILS for runway 10. The Investigation found that the A320 crew had not noticed they had the wrong ILS frequency set and that conflict with the 737 occurred because Approach transferred the A320 to TWR whilst a conflict alert was active and without confirming it was complying with its clearance.

guid: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-delhi-india-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-delhi-india-2016 title: E145, Bristol UK, 2017 link: https://skybrary.aero/accidents-and-incidents/e145-bristol-uk-2017 description:

On 22 December 2017, an Embraer 145 departed the side of the runway shortly after touching down at Bristol and finally stopped 120 metres from the runway edge. The Investigation found that the aircraft had landed after the emergency/parking brake had been inadvertently selected on during the approach when the intention had been to deploy the speed brakes. It was noted that the Captain designated as Pilot Flying had been new to both the aircraft type and the Operator and had been flying under supervision as part of the associated type conversion requirement for line training.

guid: https://skybrary.aero/accidents-and-incidents/e145-bristol-uk-2017 uri: https://skybrary.aero/accidents-and-incidents/e145-bristol-uk-2017 title: CRJ9, Turku Finland, 2017 link: https://skybrary.aero/accidents-and-incidents/crj9-turku-finland-2017 description:

On 25 October 2017, a Bombardier CRJ-900 crew lost directional control after touchdown at Turku in the presence of a tailwind component on a contaminated runway at night whilst heavy snow was falling. After entering a skid the aircraft completed a 180° turn before finally stopping 160 metres from the end of the 2500 metre-long runway. The Investigation found that skidding began immediately after touchdown with the aircraft significantly above the aquaplaning threshold and that the crew did not follow the thrust reverser reset procedure after premature deployment or use brake applications and aileron inputs appropriate to the challenging conditions.

guid: https://skybrary.aero/accidents-and-incidents/crj9-turku-finland-2017 uri: https://skybrary.aero/accidents-and-incidents/crj9-turku-finland-2017 title: B773, Abu Dhabi UAE, 2016 link: https://skybrary.aero/accidents-and-incidents/b773-abu-dhabi-uae-2016 description:

On 27 September 2016, the left engine of a Boeing 777-300 failed on takeoff from Abu Dhabi after it ingested debris resulting from tread separation from one of the nose landing gear tyres and a successful overweight return to land then followed. The Investigation found that FOD damage rather than any fault with the manufacture or re-treading of the tyre had initiated tread separation and also noted the absence of any assessment of the risk of engine damage and failure from such debris ingestion which it was noted had the potential to have affected both engines rather than just one.

guid: https://skybrary.aero/accidents-and-incidents/b773-abu-dhabi-uae-2016 uri: https://skybrary.aero/accidents-and-incidents/b773-abu-dhabi-uae-2016 title: SF34, vicinity Sydney Australia, 2017 link: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-sydney-australia-2017 description:

On 17 March 2017, uncommanded engine indications on a Saab 340B en route to Sydney were followed by vibration of the right engine after which, as the crew commenced right engine shutdown, its propeller assembly separated from the engine. A PAN was declared and the flight subsequently reached Sydney without further event. The Investigation found that the propeller gearbox shaft had fractured because of undetected internal fatigue cracking in the shaft. Applicable in-service shaft inspection procedures were found to be inadequate and mandatory enhancements to these procedures have since been introduced.

guid: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-sydney-australia-2017 uri: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-sydney-australia-2017 title: GLEX, Montréal St Hubert Canada, 2017 link: https://skybrary.aero/accidents-and-incidents/glex-montreal-st-hubert-canada-2017 description:

On 15 May 2017, a Bombardier Global Express crew failed to land on the restricted runway width available at Montréal St Hubert where there was a long-term construction project which had required reductions in both width and length of the main runway. The Investigation found that relevant NOTAM information including a requirement to pre-notify intended arrival had been ignored and that during arrival the crew had failed to respond to a range of cues that their landing would not be on the normally-available runway. Deficiencies in the arrangements made for continued use of part of the runway were also identified.

guid: https://skybrary.aero/accidents-and-incidents/glex-montreal-st-hubert-canada-2017 uri: https://skybrary.aero/accidents-and-incidents/glex-montreal-st-hubert-canada-2017 title: B773, Munich Germany, 2011 link: https://skybrary.aero/accidents-and-incidents/b773-munich-germany-2011 description:

On 3 November 2011, a Boeing 777-300ER crew lost directional control of their aircraft soon after touchdown and after veering off one side of runway 08R, it then crossed to the other side of it before stopping. The Investigation found that during the final stages of an intended autoland in CAT 1 conditions, an ILS LLZ signal disturbance caused by a departing aircraft had led a flight path deviation just before touchdown and, after delaying a pre-briefed automatic go-around until this was inhibited by main gear runway contact, the crew failed to either set thrust manually or disconnect the autopilot.

guid: https://skybrary.aero/accidents-and-incidents/b773-munich-germany-2011 uri: https://skybrary.aero/accidents-and-incidents/b773-munich-germany-2011 title: A320, Brasilia Brazil, 2015 link: https://skybrary.aero/accidents-and-incidents/a320-brasilia-brazil-2015 description:

On 8 April 2015, an Airbus A320 crew lost their previously-acquired and required visual reference for the intended landing runway at Brasilia but continued descent in heavy rain and delayed beginning a go around until the aircraft was only 40 feet above the runway threshold but had not reached it. A premature touchdown prior to the runway then occurred and the aircraft travelled over 30 metres on the ground before becoming airborne again. The Investigation was unable to establish any explanation for the failure to begin a go around once sufficient visual reference was no longer available.

guid: https://skybrary.aero/accidents-and-incidents/a320-brasilia-brazil-2015 uri: https://skybrary.aero/accidents-and-incidents/a320-brasilia-brazil-2015 title: A319, Rio de Janeiro Galeão Brazil, 2017 link: https://skybrary.aero/accidents-and-incidents/a319-rio-de-janeiro-galeao-brazil-2017 description:

On 19 July 2017, an Airbus A319 crew ignored the prescribed non-precision approach procedure for which they were cleared at Rio de Janeiro Galeão in favour of an unstabilised “dive and drive” technique in which descent was then continued for almost 200 feet below the applicable MDA and led to an EGPWS terrain proximity warning as a go around was finally commenced in IMC with a minimum recorded terrain clearance of 162 feet. The Investigation noted the comprehensive fight crew non-compliance with a series of applicable SOPs and an operational context which was conducive to this although not explicitly causal.

guid: https://skybrary.aero/accidents-and-incidents/a319-rio-de-janeiro-galeao-brazil-2017 uri: https://skybrary.aero/accidents-and-incidents/a319-rio-de-janeiro-galeao-brazil-2017 title: E190, en-route, southwest of Turku Finland, 2017 link: https://skybrary.aero/accidents-and-incidents/e190-en-route-southwest-turku-finland-2017 description:

On 3 December 2017, an Embraer E190 en-route at FL310 was already turning back to Helsinki because of a burning smell in the flight deck when smoke in the cabin was followed by smoke in the flight deck. A MAYDAY was declared to ATC reporting “fire on board” and their suggested diversion to Turku was accepted. The situation initially improved but worsened after landing prompting a precautionary emergency evacuation. The Investigation subsequently attributed the smoke to a malfunctioning air cycle machine. Issues with inaccessible cabin crew smoke hoods and with the conduct and aftermath of the evacuation were also identified.

guid: https://skybrary.aero/accidents-and-incidents/e190-en-route-southwest-turku-finland-2017 uri: https://skybrary.aero/accidents-and-incidents/e190-en-route-southwest-turku-finland-2017 title: E190 / D328, Basel Mulhouse France, 2016 link: https://skybrary.aero/accidents-and-incidents/e190-d328-basel-mulhouse-france-2016 description:

On 7 March 2016, an Embraer 190 entered the departure runway at an intersection contrary to an ATC instruction to remain clear after neither a trainee controller nor their supervisor noticed the completely incorrect readback. An aircraft taking off in the opposite direction was able to rotate and fly over it before either controller noticed the conflict. The Investigation was told that the crew of the incursion aircraft had only looked towards the left before lining up and concluded that the event had highlighted the weakness of safety barriers based solely on the communications and vigilance of pilots and controllers.

guid: https://skybrary.aero/accidents-and-incidents/e190-d328-basel-mulhouse-france-2016 uri: https://skybrary.aero/accidents-and-incidents/e190-d328-basel-mulhouse-france-2016 title: B789, London Gatwick UK, 2018 link: https://skybrary.aero/accidents-and-incidents/b789-london-gatwick-uk-2018 description:

On 28 March 2018, a Boeing 787-9 crew inadvertently commenced takeoff from the displaced threshold of the departure runway at Gatwick instead of the full length which was required for the rated thrust used. The Investigation found that the runway involved was a secondary one which the crew were unfamiliar with and to which access was gained by continuing along a taxiway which followed its extended centreline. It was noted that at least four other similar incidents had occurred during the previous six months and that various risk reduction actions had since been taken by the airport operator / ANSP.

guid: https://skybrary.aero/accidents-and-incidents/b789-london-gatwick-uk-2018 uri: https://skybrary.aero/accidents-and-incidents/b789-london-gatwick-uk-2018 title: A320, vicinity Delhi India, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-delhi-india-2017 description:

On 21 June 2017, an Airbus A320 number 2 engine began vibrating during the takeoff roll at Delhi after a bird strike. After continuing the takeoff, the Captain subsequently shut down the serviceable engine and set the malfunctioning one to TO/GA and it was several minutes before the error was recognised. After an attempted number 1 engine restart failed because an incorrect procedure was followed, a second attempt succeeded. By this time inattention to airspeed loss had led to ALPHA floor protection activation. Eventual recovery was followed by a return to land with the malfunctioning engine at flight idle.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-delhi-india-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-delhi-india-2017 title: C25A / Vehicle, Reykjavik Iceland, 2018 link: https://skybrary.aero/accidents-and-incidents/c25a-vehicle-reykjavik-iceland-2018 description:

On 11 January 2018, a privately-operated Cessna 525A Citation with a two-pilot English-speaking crew made a night takeoff from Reykjavik without clearance passing within less than a metre of a vehicle sanding the out-of-service and slippery intersecting runway as it rotated. The Investigation noted that the takeoff without clearance had been intentional and due to the aircraft slipping during the turn after backtracking. It also noted that the vehicle was operating as cleared by the TWR controller on a different frequency and that information about it given to an inbound aircraft on the TWR frequency had been in Icelandic.

guid: https://skybrary.aero/accidents-and-incidents/c25a-vehicle-reykjavik-iceland-2018 uri: https://skybrary.aero/accidents-and-incidents/c25a-vehicle-reykjavik-iceland-2018 title: AT76, Surabaya Indonesia, 2014 link: https://skybrary.aero/accidents-and-incidents/at76-surabaya-indonesia-2014 description:

On 11 June 2014, an ATR 72-600 sustained substantial damage after hitting an object after touchdown at Surabaya but was able to taxi to post-flight parking. The Investigation found that several sizeable items of equipment had been left on the runway after it had been closed for overnight maintenance work and that no runway inspection had been carried out once the work was complete. It was concluded that departing aircraft had probably become airborne before reaching the reported location and that ATC had reacted with insufficient urgency after beginning to receive FOD reports from previous landing aircraft once daylight prevailed.

guid: https://skybrary.aero/accidents-and-incidents/at76-surabaya-indonesia-2014 uri: https://skybrary.aero/accidents-and-incidents/at76-surabaya-indonesia-2014 title: MD83, Ypsilanti MI USA, 2017 link: https://skybrary.aero/accidents-and-incidents/md83-ypsilanti-mi-usa-2017 description:

On 8 March 2017, a Boeing MD83 departing Ypsilanti could not be rotated and the takeoff had to be rejected from above V1. The high speed overrun which followed substantially damaged the aircraft but evacuation was successful. The Investigation found that the right elevator had been locked in a trailing-edge-down position as a result of damage caused to the aircraft by high winds whilst it was parked unoccupied for two days prior to the takeoff. It was noted that on an aircraft with control tab initiated elevator movement, this condition was undetectable during prevailing pre flight system inspection or checks.

guid: https://skybrary.aero/accidents-and-incidents/md83-ypsilanti-mi-usa-2017 uri: https://skybrary.aero/accidents-and-incidents/md83-ypsilanti-mi-usa-2017 title: A321, vicinity Deauville France, 2013 link: https://skybrary.aero/accidents-and-incidents/a321-vicinity-deauville-france-2013 description:

On 26 September 2013, an Airbus A321 approaching Deauville in day VMC was advised that only a GNSS instrument approach - for which the crew were not approved - was available for the active runway. During the subsequent visual approach, the crew lost sight of the runway whilst over the sea and descended to almost the same height as the land ahead, eventually triggering an EGPWS ‘PULL UP’ Warning. The approach was subsequently abandoned after an EGPWS ‘SINK RATE’ Alert on short finals and non-standard positioning to the opposite runway direction, followed by a landing in the originally expected direction.

guid: https://skybrary.aero/accidents-and-incidents/a321-vicinity-deauville-france-2013 uri: https://skybrary.aero/accidents-and-incidents/a321-vicinity-deauville-france-2013 title: B764, en-route, Audincourt France, 2017 link: https://skybrary.aero/accidents-and-incidents/b764-en-route-audincourt-france-2017 description:

On 23 August 2017, a Boeing 767-400ER which had departed Zurich for a transatlantic crossing experienced a problem with cabin pressurisation as the aircraft approached FL 100 and levelled off to run the applicable checklist. However, despite being unable to confirm that the pressurisation system was functioning normally, the climb was then re-commenced resulting in a recurrence of the same problem and a MAYDAY emergency descent from FL 200. The Investigation found that an engineer had mixed up which pressurisation system valve was to be de-activated before departure and that the flight crew decision to continue the climb had been risky.

guid: https://skybrary.aero/accidents-and-incidents/b764-en-route-audincourt-france-2017 uri: https://skybrary.aero/accidents-and-incidents/b764-en-route-audincourt-france-2017 title: AT76, en-route, east of Cork Ireland, 2016 link: https://skybrary.aero/accidents-and-incidents/at76-en-route-east-cork-ireland-2016 description:

On 24 August 2016, an ATR 72-600 experienced a static inverter failure which resulted in smoke and fumes which were identifiably electrical. Oxygen masks were donned, a MAYDAY declared and after the appropriate procedures had been followed, the smoke / fumes ceased. The Investigation noted a long history of capacitor failures affecting this unit which continued to be addressed by successive non-mandatory upgrades including another after this event. However, it was also found that there was no guidance on the re-instatement of systems disabled during the initial response to such events, in particular the total loss of AC electrical power.

guid: https://skybrary.aero/accidents-and-incidents/at76-en-route-east-cork-ireland-2016 uri: https://skybrary.aero/accidents-and-incidents/at76-en-route-east-cork-ireland-2016 title: B772, en-route, Osaka Japan, 2017 link: https://skybrary.aero/accidents-and-incidents/b772-en-route-osaka-japan-2017 description:

On 23 September 2017, a large wing-to-body fairing panel confirmed to have dropped from a Boeing 777-200 passing over the centre of Osaka after takeoff off from Kansai hit and significantly damaged a moving vehicle. The Investigation found that the panel involved had a sufficient history of attachment bracket failures for Boeing to have developed an improved thicker bracket for new-build aircraft which had then been advised as available as a replacement for in-service 777-200 aircraft in a Service Letter which KLM had decided not to follow. Although some incorrect bracket attachment bolts were found, this was not considered contributory.

guid: https://skybrary.aero/accidents-and-incidents/b772-en-route-osaka-japan-2017 uri: https://skybrary.aero/accidents-and-incidents/b772-en-route-osaka-japan-2017 title: SB20, vicinity Billund Denmark, 2015 link: https://skybrary.aero/accidents-and-incidents/sb20-vicinity-billund-denmark-2015 description:

On 10 December 2015, a Saab 2000 descended below the prescribed vertical profile in IMC during a LLZ-only approach to Billund. An EGPWS ‘PULL UP’ warning was followed by a go around instead of the prescribed response to such a warning. A minor level bust and configuration exceedance followed after which the aircraft returned to its departure airport. Prior to the LLZ-only approach, an attempt to continue with an ILS approach to the same runway with only a LLZ signal available had also ended in a go around. In both cases, there was a complete failure to maintain vertical situational awareness.

guid: https://skybrary.aero/accidents-and-incidents/sb20-vicinity-billund-denmark-2015 uri: https://skybrary.aero/accidents-and-incidents/sb20-vicinity-billund-denmark-2015 title: E120, Amsterdam Netherlands, 2016 link: https://skybrary.aero/accidents-and-incidents/e120-amsterdam-netherlands-2016 description:

On 18 January 2016, an Embraer 120 crew made a night takeoff from Amsterdam Runway 24 unaware that the aircraft was aligned with the right side runway edge lights. After completion of an uneventful flight, holes in the right side fuselage and damage to the right side propeller blades, the latter including wire embedded in a blade leading edge, were found. The Investigation concluded that poor visual cues guiding aircraft onto the runway at the intersection concerned were conducive to pilot error and noted that despite ATS awareness of intersection takeoff risks, no corresponding risk mitigation had been undertaken.

guid: https://skybrary.aero/accidents-and-incidents/e120-amsterdam-netherlands-2016 uri: https://skybrary.aero/accidents-and-incidents/e120-amsterdam-netherlands-2016 title: A320 / B738, vicinity Barcelona, Spain 2018 link: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-barcelona-spain-2018 description:

On 6 July 2018, a Boeing 737-800 being positioned to join the intermediate approach sequence in the Barcelona CTR was obliged to take lateral avoiding action against an Airbus A320 ahead. The Investigation found that although both aircraft were in the same sector at the time, the controller had overlooked the presence of the A320 which had been transferred to the next sector before entering it prior to the controller involved routinely taking over the position. An on-screen alert to the developing conflict had not been seen by the controller. Minimum separation was 1.1nm laterally and 200 feet vertically.

guid: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-barcelona-spain-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-b738-vicinity-barcelona-spain-2018 title: B738, en-route, northeast of Lanzarote Canaries Spain, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-northeast-lanzarote-canaries-spain-2018 description:

On 10 February 2018, soon after a Boeing 737-800 en-route to Fuerteventura had begun its cleared descent from FL370 to FL130, the controller changed the clearance limit to FL360 after noticing a previously overlooked potential loss of separation with traffic below at FL350. The attempt to level off as instructed resulted in a mismanaged manual intervention which led to an upset lasting about a minute during which a passenger carrying a small child fell and sustained serious injury. The significant delay in getting the injured passenger to hospital after landing led to systemic deficiencies in airport medical assistance being identified.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-northeast-lanzarote-canaries-spain-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-northeast-lanzarote-canaries-spain-2018 title: B738 / A320, Edinburgh UK, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-a320-edinburgh-uk-2018 description:

On 13 August 2018, a Boeing 737-800 arriving at Edinburgh came to within 875 metres of an Airbus A320 departing from the same runway. Landing clearance was given one minute prior to touchdown which occurred when the departing aircraft was passing 60 feet aal and both aircraft were over the runway surface at the same time which constituted a runway incursion under local procedures. The Investigation found that the TWR position had been occupied by a trainee controller who had not received sufficient support from their supervisor after failing to act appropriately to ensure that the prescribed separation was maintained.

guid: https://skybrary.aero/accidents-and-incidents/b738-a320-edinburgh-uk-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-a320-edinburgh-uk-2018 title: A320, en-route, east of Cork Ireland, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-east-cork-ireland-2017 description:

On 2 November 2017, the flight crew of an Airbus A320 climbing out of Cork detected a “strong and persistent” burning smell and after declaring a MAYDAY returned to Cork where confusing instructions from the crew resulted in a combination of the intended precautionary rapid disembarkation and an emergency evacuation using escape slides. The Investigation highlighted the necessity of clear and unambiguous communications with passengers which distinguish these two options and in particular noted the limitations in currently mandated pre flight briefings for passengers seated at over wing emergency exits.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-east-cork-ireland-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-east-cork-ireland-2017 title: B738, Darwin Australia, 2016 link: https://skybrary.aero/accidents-and-incidents/b738-darwin-australia-2016 description:

On 6 December 2016, a Boeing 737-800 approaching Darwin at night in the vicinity of thunderstorm activity suddenly encountered very heavy rain just before landing which degraded previously good visual reference. After drifting right of centreline just before and after touchdown, the right main gear left the runway for 400 metres before regaining. The landing and taxi-in was subsequently completed. The Investigation attributed the excursion to difficulty in discerning lateral drift during the landing flare to an abnormally wide runway with no centreline lighting in poor night visibility and noted similar previous outcomes had been consistently associated with this context.

guid: https://skybrary.aero/accidents-and-incidents/b738-darwin-australia-2016 uri: https://skybrary.aero/accidents-and-incidents/b738-darwin-australia-2016 title: B77W, en-route, northeast of Los Angeles USA, 2016 link: https://skybrary.aero/accidents-and-incidents/b77w-en-route-northeast-los-angeles-usa-2016 description:

On 16 December 2016, a Boeing 777-300 which had just departed from runway 07R at Los Angeles was radar vectored in Class B airspace at up to 1600 feet below the applicable minimum radar vectoring altitude. The Investigation found that the area controller s initial vectoring had been contrary to applicable procedures and their communication confusing and that they had failed to recover the situation before it became dangerous. As a result, as the crew were responding in night IMC to a resulting EGPWS PULL UP Warning, the aircraft had passed within approximately 0.3 nm of obstructions at the same altitude.

guid: https://skybrary.aero/accidents-and-incidents/b77w-en-route-northeast-los-angeles-usa-2016 uri: https://skybrary.aero/accidents-and-incidents/b77w-en-route-northeast-los-angeles-usa-2016 title: SU95, Moscow Sheremetyevo Russia, 2019 link: https://skybrary.aero/accidents-and-incidents/su95-moscow-sheremetyevo-russia-2019 description:

On 5 May 2019, a Sukhoi RRJ-95B making a manually-flown return to Moscow Sheremetyevo after a lightning strike caused a major electrical systems failure soon after departure made a mismanaged landing which featured a sequence of three hard bounces of increasing severity. The third of these occurred with the landing gear already collapsed and structural damage and a consequential fuel-fed fire followed as the aircraft veered off the runway at speed. The subsequent evacuation was only partly successful and 41 of the 73 occupants died and 3 sustained serious injury. An Interim Report has been published.

guid: https://skybrary.aero/accidents-and-incidents/su95-moscow-sheremetyevo-russia-2019 uri: https://skybrary.aero/accidents-and-incidents/su95-moscow-sheremetyevo-russia-2019 title: B772, Dhaka Bangladesh, 2018 link: https://skybrary.aero/accidents-and-incidents/b772-dhaka-bangladesh-2018 description:

On 24 July 2018, a Boeing 777-200 making its second attempt to land at Dhaka in moderate to heavy rain partly left the runway during its landing roll and its right main landing gear sustained serious impact damage before the whole aircraft returned to the runway with its damaged gear assembly then causing runway damage. The Investigation attributed the excursion to the flight crew s inadequate coordination during manual handling of the aircraft and noted both the immediate further approach in unchanged weather conditions and the decision to continue to a landing despite poor visibility instead of going around again.

guid: https://skybrary.aero/accidents-and-incidents/b772-dhaka-bangladesh-2018 uri: https://skybrary.aero/accidents-and-incidents/b772-dhaka-bangladesh-2018 title: RJ85, en-route, near Musina South Africa, 2017 link: https://skybrary.aero/accidents-and-incidents/rj85-en-route-near-musina-south-africa-2017 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/rj85-en-route-near-musina-south-africa-2017 uri: https://skybrary.aero/accidents-and-incidents/rj85-en-route-near-musina-south-africa-2017 title: A333, St Lucia Eastern Caribbean, 2013 link: https://skybrary.aero/accidents-and-incidents/a333-st-lucia-eastern-caribbean-2013 description:

On 25 December 2013, an Airbus A330-300 conducted a stable night non-precision approach at St. Lucia but the crew found that after touchdown, atypical intervention was needed to ensure direction along the runway was maintained and also detected both ‘juddering’ and a more significant rate of deceleration than usual. Considerable impact damage to the lower fuselage and below-floor systems was subsequently discovered. The Investigation concluded that this damage had resulted from impact with water from a diverted river channel which had burst its banks and flooded the touchdown area of the runway to a depth of up to 60 cm.

guid: https://skybrary.aero/accidents-and-incidents/a333-st-lucia-eastern-caribbean-2013 uri: https://skybrary.aero/accidents-and-incidents/a333-st-lucia-eastern-caribbean-2013 title: AT72, vicinity Budapest Hungary, 2016 link: https://skybrary.aero/accidents-and-incidents/at72-vicinity-budapest-hungary-2016 description:

On 16 March 2016, an engine fire occurred to an ATR 72-200 departing Budapest and after declaring a MAYDAY, it was landed in the reciprocal direction on the departure runway without further event. The Investigation found that the failure had been initiated by the fatigue-induced failure of a single blade in the power turbine assembly but with insufficient evidence to ascribe a cause for this. A number of almost identical instances of engine failure initiated by failure of a single turbine blade were noted. Opportunities for both ATC procedures and flight crew response to mandatory emergency procedures were also identified.

guid: https://skybrary.aero/accidents-and-incidents/at72-vicinity-budapest-hungary-2016 uri: https://skybrary.aero/accidents-and-incidents/at72-vicinity-budapest-hungary-2016 title: F50 / P28T, vicinity Friedrichshafen Germany, 2016 link: https://skybrary.aero/accidents-and-incidents/f50-p28t-vicinity-friedrichshafen-germany-2016 description:

On 21 April 2016, a Fokker F50 under radar control in Class ‘E’ airspace was almost in collision with a VFR Piper PA28 after they closed on a constant relative bearing when inbound to Friedrichshafen in VMC. After only being able to locate the PA28 on their TCAS display, the F50 crew implemented a lateral avoidance manoeuvre which prevented generation of an RA. The Investigation concluded that special ATC procedures in place due to busy traffic because of an annually-held trade fair at Friedrichshafen had entailed “systemic risk” and also identified inadequate controller coordination as contributory to a near collision.

guid: https://skybrary.aero/accidents-and-incidents/f50-p28t-vicinity-friedrichshafen-germany-2016 uri: https://skybrary.aero/accidents-and-incidents/f50-p28t-vicinity-friedrichshafen-germany-2016 title: A319, Munich Germany, 2017 link: https://skybrary.aero/accidents-and-incidents/a319-munich-germany-2017 description:

On 3 July 2017, an Airbus A319 sustained significant landing gear damage during the First Officer’s manual landing at Munich which recorded a vertical acceleration exceeding the threshold for a mandatory airworthiness inspection. That inspection found damage to nose and one main landing gear legs and, following Airbus advice, all three were replaced before release to service. The Investigation was unable to explain why neither pilot detected the incorrect pitch attitude and excessive rate of descent in time to take corrective action and noted that a reversion to manual flight during intermediate approach had been due to a technical malfunction.

guid: https://skybrary.aero/accidents-and-incidents/a319-munich-germany-2017 uri: https://skybrary.aero/accidents-and-incidents/a319-munich-germany-2017 title: B789 / B773, Delhi India, 2017 link: https://skybrary.aero/accidents-and-incidents/b789-b773-delhi-india-2017 description:

On 7 October 2017, an arriving Boeing 787-9 and a departing Boeing 777-300 lost separation during intended use of runway 29 at Delhi when the 787-9 commenced a go around from overhead the runway because the departing 777-300 was still on the runway and came within 0.2 nm laterally and 200 feet vertically after ATC had failed to ensure that separation appropriate to mixed mode use was applied using speed control. The conflict was attributed to failure of the TWR controller to adhere to prevailing standard operating procedures.

guid: https://skybrary.aero/accidents-and-incidents/b789-b773-delhi-india-2017 uri: https://skybrary.aero/accidents-and-incidents/b789-b773-delhi-india-2017 title: B773, Dhaka Bangladesh, 2016 link: https://skybrary.aero/accidents-and-incidents/b773-dhaka-bangladesh-2016 description:

On 7 June 2016, a GE90-115B engined Boeing 777-300 made a high speed rejected takeoff on 3200 metre-long runway 14 at Dhaka after right engine failure was annunciated at 149KCAS - just below V1. Neither crew nor ATC requested a runway inspection and 12 further aircraft movements occurred before it was closed for inspection and recovery of 14 kg of debris. The Investigation found that engine failure had followed Super Absorbent Polymer (SAP) contamination of some of the fuel nozzle valves which caused them to malfunction leading to Low Pressure Turbine (LPT) mechanical damage. The contaminant origin was not identified.

guid: https://skybrary.aero/accidents-and-incidents/b773-dhaka-bangladesh-2016 uri: https://skybrary.aero/accidents-and-incidents/b773-dhaka-bangladesh-2016 title: C550, en-route, north of Savannah GA USA, 2019 link: https://skybrary.aero/accidents-and-incidents/c550-en-route-north-savannah-ga-usa-2019 description:

On 9 May 2019, a Cessna 550 level at FL 350 experienced an unexplained left engine rundown to idle and the crew began descent and a diversion to Savannah. When the right engine also began to run down passing 8000 feet, an emergency was declared and the already-planned straight-in approach was successfully accomplished without any engine thrust. The ongoing Investigation has already established that the likely cause was fuel contamination resulting from the inadvertent mixing of a required fuel additive with an unapproved substance known to form deposits which impede fuel flow when they accumulate on critical fuel system components.

guid: https://skybrary.aero/accidents-and-incidents/c550-en-route-north-savannah-ga-usa-2019 uri: https://skybrary.aero/accidents-and-incidents/c550-en-route-north-savannah-ga-usa-2019 title: SW4, Thompson MB Canada, 2017 link: https://skybrary.aero/accidents-and-incidents/sw4-thompson-mb-canada-2017 description:

On 2 November 2017, a Fairchild SA 227-AC Metro III landing at Thompson after a ferry-permit flight issued to facilitate a hydraulic fluid leak rectification left the runway when reverse pitch was selected and sustained substantial damage. The Investigation found that the flight had been continued without shutting down the left engine when its oil pressure dropped below the level requiring this in the QRH. The oil loss was found to be attributable to the same cause as a similar loss identified two days previously for which rectification had supposedly been achieved. The hydraulic leak did not affect the flight.

guid: https://skybrary.aero/accidents-and-incidents/sw4-thompson-mb-canada-2017 uri: https://skybrary.aero/accidents-and-incidents/sw4-thompson-mb-canada-2017 title: B737, Singapore Seletar, 2017 link: https://skybrary.aero/accidents-and-incidents/b737-singapore-seletar-2017 description:

On 16 November 2017, a Boeing 737-700 departing Singapore Seletar was observed by ATC to only become airborne very near the end of the runway and to then climb only very slowly. Ten approach lights were subsequently found to have been impact-damaged by contact with the aircraft. The Investigation found that after the crew had failed to follow procedures requiring them to validate the FMC recalculation of modified takeoff performance data against independent calculations made on their EFBs, takeoff was made with reduced thrust instead of the full thrust required. The modification made was also found not to have been required.

guid: https://skybrary.aero/accidents-and-incidents/b737-singapore-seletar-2017 uri: https://skybrary.aero/accidents-and-incidents/b737-singapore-seletar-2017 title: CRJ9, Entebbe Uganda, 2018 link: https://skybrary.aero/accidents-and-incidents/crj9-entebbe-uganda-2018 description:

On 4 February 2018, a Bombardier CRJ900 which had just arrived at Kigali after a flight from Entebbe was found to have identical damage to all left engine fan blade trailing edges and a small bolt was subsequently found trapped in the intake acoustic lining. The Investigation concluded that the recovered bolt had probably been picked up by the outboard left main gear tyre at slow speed and then ejected into the engine as wheel speed increased during takeoff thus causing the observed damage. FOD mitigation measures at Entebbe, where a major airside construction project was in progress, were faulted.

guid: https://skybrary.aero/accidents-and-incidents/crj9-entebbe-uganda-2018 uri: https://skybrary.aero/accidents-and-incidents/crj9-entebbe-uganda-2018 title: S92, northeast of Aberdeen UK, 2018 link: https://skybrary.aero/accidents-and-incidents/s92-northeast-aberdeen-uk-2018 description:

On 23 August 2018, a low experience Sikorsky S92 First Officer undergoing line training made a visual transit between two North Sea offshore platforms but completed an approach to the wrong one. The platform radio operator alerted the crew to their error and the helicopter then flew to the correct platform. The Investigation attributed the error primarily to the inadequate performance of both pilots on what should have been a straightforward short visual flight but particularly highlighted the apparent failure of the Training Captain to fully recognise the challenges of the flight involved when training and acting as Pilot Monitoring.

guid: https://skybrary.aero/accidents-and-incidents/s92-northeast-aberdeen-uk-2018 uri: https://skybrary.aero/accidents-and-incidents/s92-northeast-aberdeen-uk-2018 title: B789 / C172, en-route, northwest of Madrid Spain, 2017 link: https://skybrary.aero/accidents-and-incidents/b789-c172-en-route-northwest-madrid-spain-2017 description:

On 8 August 2017, a Boeing 787-9 climbing through FL109 after departing Madrid received and promptly followed a TCAS RA DESCEND against crossing traffic at FL110 and this action quickly resolved the conflict. The Investigation found that both aircraft involved were following their IFR clearances and attributed the conflict to the controller involved who forgot to resolve a previously-identified potential conflict whilst resolving another potential conflict elsewhere in the sector. It was also found that the corresponding STCA activation had not been noticed and in any event had occurred too late to be of use.

guid: https://skybrary.aero/accidents-and-incidents/b789-c172-en-route-northwest-madrid-spain-2017 uri: https://skybrary.aero/accidents-and-incidents/b789-c172-en-route-northwest-madrid-spain-2017 title: A320, en-route, east of Miyazaki Japan, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-east-miyazaki-japan-2018 description:

On 27 August 2018, an Airbus A320 level at FL 300 encountered unanticipated turbulence which caused one of the cabin crew to fall and sustain what was belatedly diagnosed as spinal fracture. The Investigation found that the aircraft had flown through the decaying wake vortex from an almost opposite direction Boeing 747-400F at FL310 which had been observed to cross what was subsequently found to be 13.8 nm ahead of the A320 prior to the latter crossing its track 1 minute 40 seconds later that coincided with a very brief period in which vertical acceleration varied between +0.19g and +1.39g.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-east-miyazaki-japan-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-east-miyazaki-japan-2018 title: A319 / A320, Paris CDG France, 2014 link: https://skybrary.aero/accidents-and-incidents/a319-a320-paris-cdg-france-2014 description:

On 25 November 2014, the crew of an Airbus A320 taking off from Paris CDG and in the vicinity of V1 saw an A319 crossing the runway ahead of them and determined that the safest conflict resolution was to continue the takeoff. The A320 subsequently overflew the A319 as it passed an estimated 100 feet agl. The Investigation concluded that use of inappropriate phraseology by the TWR controller when issuing an instruction to the A319 crew had led to a breach of the intended clearance limit. It was also noted that an automated conflict alert had activated too late to intervene.

guid: https://skybrary.aero/accidents-and-incidents/a319-a320-paris-cdg-france-2014 uri: https://skybrary.aero/accidents-and-incidents/a319-a320-paris-cdg-france-2014 title: A343, Bogota Colombia, 2017 link: https://skybrary.aero/accidents-and-incidents/a343-bogota-colombia-2017 description:

On 11 March 2017, contrary to crew expectations based on their pre-flight takeoff performance calculation, an Airbus 340-300 taking off from the 3,800 metre-long at Bogata only became airborne just before the end of the runway. The Investigation found that the immediate reason for this was the inadequate rate of rotation achieved by the Training Captain performing the takeoff. However, it was also found that the operator’s average A340-300 rotation rate was less than would be achieved using handling recommendations which themselves would not achieve the expected performance produced by the Airbus takeoff performance software that reflected type certification findings.

guid: https://skybrary.aero/accidents-and-incidents/a343-bogota-colombia-2017 uri: https://skybrary.aero/accidents-and-incidents/a343-bogota-colombia-2017 title: B734, en-route, eastern England UK, 2018 link: https://skybrary.aero/accidents-and-incidents/b734-en-route-eastern-england-uk-2018 description:

On 12 October 2018, the crew of a Boeing 737-400 already released to service under MEL conditions with an inoperative No 1 engine generator encountered a loss of services from the No 2 electrical system en-route to East Midlands which created a situation not addressed by QRH procedures. The flight was completed and both the new and existing defects were subsequently rectified relatively easily. The Investigation concluded that the operator involved appeared to be prioritising operational requirements over aircraft serviceability issues and made a range of Safety Recommendations aimed at improving company safety culture and the effectiveness of regulatory oversight.

guid: https://skybrary.aero/accidents-and-incidents/b734-en-route-eastern-england-uk-2018 uri: https://skybrary.aero/accidents-and-incidents/b734-en-route-eastern-england-uk-2018 title: A320, en-route, west southwest of Karachi Pakistan, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-west-southwest-karachi-pakistan-2018 description:

On 5 March 2018, the crew of an Airbus A320 in descent towards Karachi observed a slow but continuous drop in cabin pressure which eventually triggered an excessive cabin altitude warning which led them to don oxygen masks, commence an emergency descent and declare a PAN to ATC until the situation had been normalised. The Investigation found that the cause was the processing of internally corrupted data in the active cabin pressure controller which had used a landing field elevation of over 10,000 feet. It noted that Airbus is developing a modified controller that will prevent erroneous data calculations occurring.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-west-southwest-karachi-pakistan-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-west-southwest-karachi-pakistan-2018 title: E50P, Berlin Schönefeld Germany, 2013 link: https://skybrary.aero/accidents-and-incidents/e50p-berlin-schonefeld-germany-2013 description:

On 15 February 2013, an Embraer EMB-500 Phenom 100 crew lost control of their aircraft shortly before touchdown at Berlin Schönefeld when it stalled and crash-landed. The Investigation was not completed for almost six years but concluded that the stall was a result of ice accretion during an approach in icing conditions without activation of the airframe de icing system. It found poor crew awareness of both the ice and stall protection systems and, suspecting that this may be true of other type-rated pilots, accordingly made Safety Recommendations to key regulatory authorities concerning the type rating syllabus.

guid: https://skybrary.aero/accidents-and-incidents/e50p-berlin-schonefeld-germany-2013 uri: https://skybrary.aero/accidents-and-incidents/e50p-berlin-schonefeld-germany-2013 title: AT45, vicinity Esbjerg Denmark, 2016 link: https://skybrary.aero/accidents-and-incidents/at45-vicinity-esbjerg-denmark-2016 description:

On 27 March 2016 an ATR 42-500 had just departed Esbjerg when the right engine flamed out. It was decided to complete the planned short flight to Billund but on the night IMC approach there, the remaining engine malfunctioned and lost power. The approach was completed and the aircraft evacuated after landing. The Investigation found the left engine failed due to fuel starvation resulting from a faulty fuel quantity indication probably present since recent heavy maintenance and that the right engine had emitted flames during multiple compressor stalls to which it was vulnerable due to in-service deterioration and hot section damage.

guid: https://skybrary.aero/accidents-and-incidents/at45-vicinity-esbjerg-denmark-2016 uri: https://skybrary.aero/accidents-and-incidents/at45-vicinity-esbjerg-denmark-2016 title: AT75, vicinity Yasouj Iran, 2018 link: https://skybrary.aero/accidents-and-incidents/at75-vicinity-yasouj-iran-2018 description:

On 18 February 2018, contact was lost with an ATR72-500 approaching Yasouj and two days later the wreckage of the aircraft was located in mountainous terrain with no sign of survivors. The flight recorders were eventually recovered and their data helped attribute the accident to descent below the designated minimum safe altitude followed by an encounter with severe mountain wave conditions which led to the crew losing control and a terrain impact which destroyed the aircraft and killed all its occupants. An apparently widespread failure to recognise the potential risk of severe mountain wave encounters was also found.

guid: https://skybrary.aero/accidents-and-incidents/at75-vicinity-yasouj-iran-2018 uri: https://skybrary.aero/accidents-and-incidents/at75-vicinity-yasouj-iran-2018 title: A320 / Vehicle, London Gatwick UK, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-vehicle-london-gatwick-uk-2018 description:

On 3 February 2018, a runway inspection vehicle was cleared onto the active runway at London Gatwick ahead of an aircraft which had just touched down and driven towards it having been cleared to do so because the aircraft crew’s confirmation that they would clear the runway before reaching the vehicle was considered by the controller as a clearance limit. The Investigation found that the associated runway inspection procedure had not been adequately risk-assessed and noted that many issues raised by it had still not been addressed by the time it was completed eighteen months later.

guid: https://skybrary.aero/accidents-and-incidents/a320-vehicle-london-gatwick-uk-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-vehicle-london-gatwick-uk-2018 title: A320, Gold Coast QLD Australia, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-gold-coast-qld-australia-2017 description:

On 18 December 2017, an A320 crew found that only one thrust reverser deployed when the reversers were selected shortly after touchdown but were able to retain directional control. The Investigation found that the aircraft had been released to service in Adelaide with the affected engine reverser lockout pin in place. This error was found to have occurred in a context of multiple failures to follow required procedures during the line maintenance intervention involved for which no mitigating factors of any significance could be identified. A corrective action after a previous similar event at the same maintenance facility was also found not to have been fully implemented.

guid: https://skybrary.aero/accidents-and-incidents/a320-gold-coast-qld-australia-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-gold-coast-qld-australia-2017 title: A320, Malé Maldives, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-male-maldives-2018 description:

On 7 September 2018, an Airbus A320 was inadvertently landed on an under- construction runway at Malé in daylight VMC but met no significant obstructions and sustained only minor damage. The Investigation attributed the error to confusion generated by a combination of pilot inattention to clearly relevant notification, controller distraction, the failure of the airport operator to follow required procedures and the failure of the safety regulator to ensure that sufficient arrangements to ensure safety were in place and complied with.

guid: https://skybrary.aero/accidents-and-incidents/a320-male-maldives-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-male-maldives-2018 title: A320, en-route, northeast of Granada Spain, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-northeast-granada-spain-2017 description:

On 21 February 2017, an Airbus A320 despatched with the APU inoperative experienced successive failures of both air conditioning and pressurisation systems, the second of which occurred at FL300 and prompted the declaration of a MAYDAY and an emergency descent followed by an uneventful diversion to Alicante. The Investigation found that the cause of the dual failure was likely to have been the undetectable and undetected degradation of the aircraft bleed air regulation system and whilst noting a possibly contributory maintenance error recommended that a new scheduled maintenance task to check components in the aircraft type bleed system be established.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-northeast-granada-spain-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-northeast-granada-spain-2017 title: B738, Manila Philippines, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-manila-philippines-2018 description:

On 16 August 2018, a Boeing 737-800 made a stabilised approach to Manila during a thunderstorm with intermittent heavy rain but the crew lost adequate visual reference as they arrived over the runway. After a drift sideways across the 60 metre-wide landing runway, a veer off occurred and was immediately followed by a damaging collision with obstructions not compliant with prevailing airport safety standards. The Investigation found that the Captain had ignored go around calls from the First Officer and determined that the corresponding aircraft operator procedures were inadequate as well as faulting significant omissions in the Captain s approach brief.

guid: https://skybrary.aero/accidents-and-incidents/b738-manila-philippines-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-manila-philippines-2018 title: AN72, Sao Tome, Sao Tome & Principe, 2017 link: https://skybrary.aero/accidents-and-incidents/an72-sao-tome-sao-tome-principe-2017 description:

On 29 July 2017, an Antonov AN-74 crew sighted several previously unseen large eagles rising from the long grass next to the runway as they accelerated for takeoff at Sao Tome and, concerned about the risk of ingestion, made a high speed rejected takeoff but were unable to stop on the runway and entered a deep ravine just beyond it which destroyed the aircraft. The Investigation found that the reject had been unnecessarily delayed until above V1, that the crew forgot to deploy the spoilers which would have significantly increased the stopping distance and that relevant crew training was inadequate.

guid: https://skybrary.aero/accidents-and-incidents/an72-sao-tome-sao-tome-principe-2017 uri: https://skybrary.aero/accidents-and-incidents/an72-sao-tome-sao-tome-principe-2017 title: S76, vicinity Lagos Nigeria, 2015 link: https://skybrary.aero/accidents-and-incidents/s76-vicinity-lagos-nigeria-2015 description:

On 12 August 2015, a Sikorsky S76C crew on a flight from an offshore platform to Lagos lost control of their aircraft after a sudden uncommanded pitch up, yaw and roll began and 12 seconds later it crashed into water in a suburb of Lagos killing both pilots and four of the 10 passengers. The Investigation concluded that the upset had been caused by a critical separation within the main rotor cyclic control system resulting from undetected wear at a point where there was no secondary mechanical locking system such as a locking pin or a wire lock to maintain system integrity.

guid: https://skybrary.aero/accidents-and-incidents/s76-vicinity-lagos-nigeria-2015 uri: https://skybrary.aero/accidents-and-incidents/s76-vicinity-lagos-nigeria-2015 title: AT76, Lisbon Portugal, 2016 link: https://skybrary.aero/accidents-and-incidents/at76-lisbon-portugal-2016 description:

On 22 October 2016, an ATR 72-600 Captain failed to complete a normal night landing in relatively benign weather conditions and after the aircraft had floated beyond the touchdown zone, it bounced three times before finally settling on the runway in a substantially damaged condition. The Investigation noted that touchdown followed an unstabilised approach and that there had been little intervention by the First Officer. However, it tentatively attributed the Captain s poor performance to a combination of fatigue at the end of a repetitive six-sector day and failure of the operator to provide adequate bounced landing recognition and recovery training.

guid: https://skybrary.aero/accidents-and-incidents/at76-lisbon-portugal-2016 uri: https://skybrary.aero/accidents-and-incidents/at76-lisbon-portugal-2016 title: MD83, Port Harcourt Nigeria, 2018 link: https://skybrary.aero/accidents-and-incidents/md83-port-harcourt-nigeria-2018 description:

On 20 February 2018, a Boeing MD-83 attempting a night landing at Port Harcourt during a thunderstorm and heavy rain touched down well beyond the touchdown zone and departed the side of the runway near its end before continuing 300 metres beyond it. The Investigation found that a soft touchdown had occurred with 80% of the runway behind the aircraft and a communications failure on short final meant a wind velocity change just before landing leading to a tailwind component of almost 20 knots was unknown to the crew who had not recognised the need for a go around.

guid: https://skybrary.aero/accidents-and-incidents/md83-port-harcourt-nigeria-2018 uri: https://skybrary.aero/accidents-and-incidents/md83-port-harcourt-nigeria-2018 title: AT72, Trollhättan Sweden, 2018 link: https://skybrary.aero/accidents-and-incidents/at72-trollhattan-sweden-2018 description:

On 9 October 2018, an ATR 72-200 left the runway during a night landing at Trollhättan before regaining it undamaged and taxiing in normally. The excursion was not reported or observed except by the flight crew. The subsequent discovery of tyre mark evidence led to an Investigation which concluded that the cause of the excursion had been failure of the left seat pilot to adequately deflect the ailerons into wind on routinely taking over control from the other pilot after landing because there was no steering tiller on the right. The non-reporting was considered indicative of the operator’s dysfunctional SMS.

guid: https://skybrary.aero/accidents-and-incidents/at72-trollhattan-sweden-2018 uri: https://skybrary.aero/accidents-and-incidents/at72-trollhattan-sweden-2018 title: A332, en-route, North Atlantic, 2019 link: https://skybrary.aero/accidents-and-incidents/a332-en-route-north-atlantic-2019 description:

On 6 February 2019, an Airbus A330-200 Captain’s Audio Control Panel (ACP) malfunctioned and began to emit smoke and electrical fumes after coffee was spilt on it. Subsequently, the right side ACP also failed, becoming hot enough to begin melting its plastic. Given the consequent significant communications difficulties, a turnback to Shannon was with both pilots taking turns to go on oxygen. The Investigation found that flight deck drinks were routinely served in unlidded cups with the cup size in use incompatible with the available cup holders. Pending provision of suitably-sized cups, the operator decided to begin providing cup lids.

guid: https://skybrary.aero/accidents-and-incidents/a332-en-route-north-atlantic-2019 uri: https://skybrary.aero/accidents-and-incidents/a332-en-route-north-atlantic-2019 title: E75S, vicinity Atlanta GA USA, 2016 link: https://skybrary.aero/accidents-and-incidents/e75s-vicinity-atlanta-ga-usa-2016 description:

On 6 November 2019, the crew of an Embraer E175LR which had just taken off from Atlanta experienced difficulty in maintaining pitch control after an apparent pitch trim runaway and an emergency was declared. Control was subsequently regained and a return to land was made without further problems. The Investigation is continuing but has identified the root cause as wiring damage arising from incorrect installation, noted that potentially related corrective action was not mandated and determined that the operator’s QRH drill for the situation encountered had significantly contained only one memory action rather the two in the aircraft manufacturer’s version.

guid: https://skybrary.aero/accidents-and-incidents/e75s-vicinity-atlanta-ga-usa-2016 uri: https://skybrary.aero/accidents-and-incidents/e75s-vicinity-atlanta-ga-usa-2016 title: A319, vicinity Glasgow UK, 2018 link: https://skybrary.aero/accidents-and-incidents/a319-vicinity-glasgow-uk-2018 description:

On 30 September 2018, an Airbus A319 Captain had to complete a flight into Glasgow on his own when the First Officer left the flight deck after suffering a flying-related anxiety attack. After declaring a ‘PAN’ to ATC advising that the aircraft was being operated by only one pilot, the flight was completed without further event. The Investigation found that the First Officer had been “frightened” after the same Captain had been obliged to take control during his attempted landing the previous day and had “felt increasingly nervous” during his first ‘Pilot Flying’ task since the event the previous day.

guid: https://skybrary.aero/accidents-and-incidents/a319-vicinity-glasgow-uk-2018 uri: https://skybrary.aero/accidents-and-incidents/a319-vicinity-glasgow-uk-2018 title: B752, Alicante Spain, 2017 link: https://skybrary.aero/accidents-and-incidents/b752-alicante-spain-2017 description:

On 10 April 2017, a Boeing 757-200 landing at Alicante in benign weather conditions was mishandled by an inexperienced First Officer on his third and final Line Check attempt and significant damage resulted from rear fuselage runway contact. The Investigation found that after an uneventful flight thus far, the Check Captain intervened to tell the First Officer to lower the nose after touchdown but on receiving a response indicating that he believed a go around was required, the Captain took control to complete the landing. The Investigation considered that the supervising Captain could have prevented the accident by intervening earlier.

guid: https://skybrary.aero/accidents-and-incidents/b752-alicante-spain-2017 uri: https://skybrary.aero/accidents-and-incidents/b752-alicante-spain-2017 title: A320, vicinity Tallinn Estonia, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tallinn-estonia-2018 description:

On 28 February 2018, an Airbus A320 would not rotate for a touch-and-go takeoff and flightpath control remained temporarily problematic and the aircraft briefly settled back onto the runway with the gear in transit damaging both engines. A very steep climb was then followed by an equally steep descent to 600 feet agl with an EGPWS ‘PULL UP’ activation before recovery. Pitch control was regained using manual stabiliser trim but after both engines stopped during a MAYDAY turnback, an undershoot touchdown followed. The root cause of loss of primary pitch control was determined as unapproved oil in the stabiliser actuator.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tallinn-estonia-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tallinn-estonia-2018 title: A320, Macau SAR China, 2018 (1) link: https://skybrary.aero/accidents-and-incidents/a320-macau-sar-china-2018-1 description:

On 28 August 2018, an Airbus A320 bounced touchdown in apparently benign conditions resulted in nose gear damage and debris ingestion into both engines, in one case sufficient to significantly reduce thrust. The gear could not be raised at go around and height loss with EGPWS and STALL warnings occurred when the malfunctioning engine was briefly set to idle. Recovery was followed by a MAYDAY diversion to Shenzen and an emergency evacuation. The Investigation attributed the initial hard touchdown to un-forecast severe very low level wind shear and most of the damage to the negative pitch attitude during the second post-bounce touchdown.

guid: https://skybrary.aero/accidents-and-incidents/a320-macau-sar-china-2018-1 uri: https://skybrary.aero/accidents-and-incidents/a320-macau-sar-china-2018-1 title: B763, Halifax NS Canada, 2019 link: https://skybrary.aero/accidents-and-incidents/b763-halifax-ns-canada-2019 description:

On 4 March 2019, a Boeing 767-300 crew lost directional control of their aircraft as speed reduced following their touchdown at Halifax and were unable to prevent it being rotated 180° on the icy surface before coming to a stop facing the runway landing threshold. The Investigation found that the management of the runway safety risk by the airport authority had been systemically inadequate and that the communication of what was known by ATC about the runway surface condition had been incomplete. A number of subsequent corrective actions taken by the airport authority were noted.

guid: https://skybrary.aero/accidents-and-incidents/b763-halifax-ns-canada-2019 uri: https://skybrary.aero/accidents-and-incidents/b763-halifax-ns-canada-2019 title: E195, vicinity Salzburg Austria, 2017 link: https://skybrary.aero/accidents-and-incidents/e195-vicinity-salzburg-austria-2017 description:

On 27 October 2017, an Embraer E195-200 missed approach was attempted in response to a predictive windshear alert on short final at Salzburg without ensuring sufficient engine thrust was set and when a stall warning followed, the correct recovery procedure was not initiated until over a minute had elapsed. Thereafter, following two holds, an approach and landing was completed without further event. The operator did not report the event in a timely or complete manner and it was therefore not possible to identify it as a Serious Incident requiring an independent investigation until almost three months after it had occurred.

guid: https://skybrary.aero/accidents-and-incidents/e195-vicinity-salzburg-austria-2017 uri: https://skybrary.aero/accidents-and-incidents/e195-vicinity-salzburg-austria-2017 title: A333, en-route, southeast of Alice Springs Australia, 2016 link: https://skybrary.aero/accidents-and-incidents/a333-en-route-southeast-alice-springs-australia-2016 description:

On 16 August 2016, an Airbus A330-300 right engine failed just over two hours into a flight from Sydney to Kuala Lumpur. It was eventually shut down after two compressor stalls and increased vibration had followed ‘exploratory’ selection of increased thrust. A ‘PAN’ declaration was followed by diversion to Melbourne, during which two relight attempts were made, in preference to other nearer alternates without further event. The Investigation found that delayed shutdown and the relight attempts were contrary to applicable procedures and the failure to divert to the nearest suitable airport had extended the time in an elevated risk environment.

guid: https://skybrary.aero/accidents-and-incidents/a333-en-route-southeast-alice-springs-australia-2016 uri: https://skybrary.aero/accidents-and-incidents/a333-en-route-southeast-alice-springs-australia-2016 title: C25A, Bern Switzerland, 2018 link: https://skybrary.aero/accidents-and-incidents/c25a-bern-switzerland-2018 description:

On 2 March 2018, a Cessna 525A touched down at Bern aligned with the left hand edge of the runway and then left it completely before re-entering it after a little over 300 metres and completing the landing roll without further event. Damage to the aircraft and six runway edge and taxi lights was subsequently found. The Investigation noted that the crew stated that they had retained full visual contact with the runway during final approach and that the recorded braking action was good. It was not possible to establish why neither pilot had been aware of the misalignment.

guid: https://skybrary.aero/accidents-and-incidents/c25a-bern-switzerland-2018 uri: https://skybrary.aero/accidents-and-incidents/c25a-bern-switzerland-2018 title: SF34 / PA27, Nassau Bahamas, 2018 link: https://skybrary.aero/accidents-and-incidents/sf34-pa27-nassau-bahamas-2018 description:

On 22 September 2018, a Saab 340B taking off in accordance with its clearance at Nassau came close to a midair collision over the main runway after a light aircraft began an almost simultaneous takeoff in the opposite direction of the same runway contrary to its received and correctly acknowledged non-conflicting takeoff clearance for a different runway without the TWR controller noticing. The light aircraft passed over the Saab 340 without either aircraft crew seeing the other aircraft. The Investigation noted that the light aircraft pilot had “forgotten” his clearance and unconsciously substituted an alternative.

guid: https://skybrary.aero/accidents-and-incidents/sf34-pa27-nassau-bahamas-2018 uri: https://skybrary.aero/accidents-and-incidents/sf34-pa27-nassau-bahamas-2018 title: B773, en-route, near Kurihara Japan, 2018 link: https://skybrary.aero/accidents-and-incidents/b773-en-route-near-kurihara-japan-2018 description:

On 24 June 2018, a Boeing 777-300 was briefly subjected to unexpected and severe Clear Air Turbulence (CAT) whilst level at FL300 which resulted in a serious injury to one of the cabin crew as they cleared up after in-flight service. The Investigation concluded that the turbulence had occurred because of the proximity of the aircraft to a strong jet stream and that the forecast available at pre-flight briefing had underestimated the strength of the associated vertical wind shear.

guid: https://skybrary.aero/accidents-and-incidents/b773-en-route-near-kurihara-japan-2018 uri: https://skybrary.aero/accidents-and-incidents/b773-en-route-near-kurihara-japan-2018 title: DH8B, Nuuk Greenland, 2019 link: https://skybrary.aero/accidents-and-incidents/dh8b-nuuk-greenland-2019 description:

On 30 May 2019, a DHC8-200 departing from Nuuk could not be rotated at the calculated speed even using full aft back pressure and the takeoff was rejected with the aircraft coming to a stop with 50 metres of the 950 metre long dry runway remaining. The initial Investigation focus was on a potential airworthiness cause associated with the flight control system but it was eventually found that the actual weights of both passengers and cabin baggage exceeded standard weight assumptions with the excess also resulting in the aircraft centre of gravity being outside the range certified for safe flight.

guid: https://skybrary.aero/accidents-and-incidents/dh8b-nuuk-greenland-2019 uri: https://skybrary.aero/accidents-and-incidents/dh8b-nuuk-greenland-2019 title: F2TH / GLID, vicinity St Gallen-Altenrhein Switzerland, 2017 link: https://skybrary.aero/accidents-and-incidents/f2th-glid-vicinity-st-gallen-altenrhein-switzerland-2017 description:

On 15 October 2017, a Falcon 2000EX on base leg for an easterly ILS approach at St Gallen-Altenrhein came into close proximity with a reciprocal track glider at 5000 feet QNH in Class ‘E’ airspace in day VMC with neither aircraft seeing the other until just before their minimum separation - 0.35 nm horizontally and 131 feet vertically - occurred. The Investigation attributed the conflict to the lack of relevant traffic separation requirements in Class E airspace and to the glider not having its transponder switched on and not listening out with the relevant ATC Unit.

guid: https://skybrary.aero/accidents-and-incidents/f2th-glid-vicinity-st-gallen-altenrhein-switzerland-2017 uri: https://skybrary.aero/accidents-and-incidents/f2th-glid-vicinity-st-gallen-altenrhein-switzerland-2017 title: B788, vicinity Amritsar India, 2018 link: https://skybrary.aero/accidents-and-incidents/b788-vicinity-amritsar-india-2018 description:

On 19 April 2018, a Boeing 787-8 suddenly encountered a short period of severe turbulence as it climbed from FL160 towards clearance limit FL 190 during a weather avoidance manoeuvre which had taken it close to the Amritsar overhead and resulted in a level bust of 600 feet, passenger injuries and minor damage to cabin fittings. The Investigation found that the flight had departed during a period of adverse convective weather after the crew had failed to download a pre flight met briefing or obtain and review available weather updates.

guid: https://skybrary.aero/accidents-and-incidents/b788-vicinity-amritsar-india-2018 uri: https://skybrary.aero/accidents-and-incidents/b788-vicinity-amritsar-india-2018 title: A320 / SF34, vicinity London Stansted UK, 2019 link: https://skybrary.aero/accidents-and-incidents/a320-sf34-vicinity-london-stansted-uk-2019 description:

On 12 February 2019, an Airbus A320 under the command of a Captain reportedly undergoing line training supervised by a Training Captain occupying the supernumerary crew seat was slow to follow ATC instructions after breaking off from an unstabilised approach at London Stansted caused by the First Officer’s mismanagement of the approach and lost separation at night as it crossed approximately 600 feet above a Saab 340B climbing after takeoff. The Investigation found that flight crew workload had been exacerbated after the Captain under supervision unnecessarily delayed taking over control and had then not done so in the prescribed way.

guid: https://skybrary.aero/accidents-and-incidents/a320-sf34-vicinity-london-stansted-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/a320-sf34-vicinity-london-stansted-uk-2019 title: A320, Perth Australia, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-perth-australia-2018 description:

On 14 August 2018, an Airbus A320 departed Perth without full removal of its main landing gear ground locks and the unsecured components fell unseen from the aircraft during taxi and takeoff, only being recovered after runway FOD reports. The Investigation identified multiple contributory factors including an inadequately-overseen recent transfer of despatch responsibilities, the absence of adequate ground lock use procedures, the absence of required metal lanyards linking the locking components not attached directly to each gear leg flag (as also found on other company aircraft) and pilot failure to confirm that all components were in the flight deck stowage.

guid: https://skybrary.aero/accidents-and-incidents/a320-perth-australia-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-perth-australia-2018 title: A320, Bristol UK, 2019 link: https://skybrary.aero/accidents-and-incidents/a320-bristol-uk-2019 description:

On 23 March 2019, the crew of a fully-loaded Airbus A320 about to depart Bristol detected an abnormal noise from the nose landing gear as a towbarless tug was being attached. Inspection found that the aircraft nose gear had been impact-damaged rendering the aircraft no longer airworthy and the passengers were disembarked. The Investigation noted that tug driver training had been in progress and that the tug had not been correctly aligned with the nose wheels, possibly due to a momentary lapse in concentration causing the tug being aligned with the nose leg rather than the nose wheels.

guid: https://skybrary.aero/accidents-and-incidents/a320-bristol-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/a320-bristol-uk-2019 title: B738, Mumbai India, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-mumbai-india-2018 description:

On 10 July 2018, a Boeing 737-800 marginally overran the wet landing runway at Mumbai after the no 1 engine thrust reverser failed to deploy when full reverse was selected after a late touchdown following a stabilised ILS approach. The Investigation found that the overrun was the result of touchdown with almost 40% of the runway behind the aircraft followed by the failure of normal thrust reverser deployment when attempted due to a failed actuator in one of the reversers. The prevailing moderate rain and the likelihood that dynamic aquaplaning had occurred were identified as contributory.

guid: https://skybrary.aero/accidents-and-incidents/b738-mumbai-india-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-mumbai-india-2018 title: B738, Alicante Spain, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-alicante-spain-2018 description:

On 7 June 2018, a Boeing 737-800 operated by a non-Spanish speaking crew was given takeoff clearance at Alicante after the same supervised student controller had previously cleared two vehicles to begin a full-length opposite-direction runway inspection in Spanish. The controller error was only recognised when the vehicles were able to transmit that they were still on the runway, the aircraft crew being unaware of the conflict until then told to reject the takeoff. The maximum speed reached by the aircraft was 88 knots and minimum separation between the aircraft and the closest vehicle was never less than 1000 metres.

guid: https://skybrary.aero/accidents-and-incidents/b738-alicante-spain-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-alicante-spain-2018 title: B738, en-route, near Sydney Australia 2018 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-sydney-australia-2018 description:

On 12 July 2018, a Boeing 737-800 was climbing through FL135 soon after takeoff from Sydney with First Officer line training in progress when the cabin altitude warning horn sounded because both air conditioning packs had not been switched on. The Captain took control and descended the aircraft to FL100 until the situation had been normalised and the intended flight was completed. The Investigation noted that although both pilots were experienced in command on other aircraft types, both had limited time on the 737 and concluded that incorrect system configuration was consequent on procedures and checklists not being managed appropriately.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-sydney-australia-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-sydney-australia-2018 title: A310 / C421, en-route, northeast of Montréal Canada, 2018 link: https://skybrary.aero/accidents-and-incidents/a310-c421-en-route-northeast-montreal-canada-2018 description:

On 16 May 2018, an Airbus A310 and a Cessna 421 being positioned for ILS approaches to adjacent parallel runways at Montréal by different controllers lost separation. One controller incorrectly believed that he had transferred control of the Cessna to the other when the shift supervisor re-opened a sector which had been temporarily combined with his. The Investigation attributed the conflict to multiple deviations from standard procedures, memory lapses relating to controller information exchange of information and a loss of full situational awareness compounded by the shift supervisor also acting as an instructor whilst being distracted by his other duties.

guid: https://skybrary.aero/accidents-and-incidents/a310-c421-en-route-northeast-montreal-canada-2018 uri: https://skybrary.aero/accidents-and-incidents/a310-c421-en-route-northeast-montreal-canada-2018 title: A320, Macau SAR China, 2018 (2) link: https://skybrary.aero/accidents-and-incidents/a320-macau-sar-china-2018-2 description:

On 12 November 2018, an Airbus A320 took off from Macau in good daylight visibility whilst a same-direction runway inspection was in progress but became airborne well before reaching it. The conflict was not recognised until an aural conflict alert was activated, at which point the ATC Assistant took the microphone and instructed the vehicle to clear the runway. The Investigation found that the TWR Controller had forgotten that the vehicle was still on the runway until alerted by the audible alarm and had not checked either the flight progress board or the surface radar before issuing the takeoff clearance.

guid: https://skybrary.aero/accidents-and-incidents/a320-macau-sar-china-2018-2 uri: https://skybrary.aero/accidents-and-incidents/a320-macau-sar-china-2018-2 title: E190, manoeuvring, northeast of Lisbon Portugal 2018 link: https://skybrary.aero/accidents-and-incidents/e190-manoeuvring-northeast-lisbon-portugal-2018 description:

On 11 November 2018, an Embraer 190-100LR just airborne on a post maintenance non revenue positioning flight became extremely difficult to control as it entered cloud despite the complete absence of any flight control warnings. After reversion to Direct Law, partial normal control was regained and, once visual, the flight was guided to an eventually successful landing. The Investigation found that the aircraft had been released from heavy maintenance with the aileron system incorrectly configured and attributed this primarily to the comprehensively dysfunctional working processes at the maintenance facility involved. Extensive airframe deformation meant the aircraft was a hull loss.

guid: https://skybrary.aero/accidents-and-incidents/e190-manoeuvring-northeast-lisbon-portugal-2018 uri: https://skybrary.aero/accidents-and-incidents/e190-manoeuvring-northeast-lisbon-portugal-2018 title: AT76, Fez Morocco, 2018 link: https://skybrary.aero/accidents-and-incidents/at76-fez-morocco-2018 description:

On 6 July 2018, an ATR 72-600 followed an unstable approach at Fez with a multiple-bounce landing including a tail strike which caused rear fuselage deformation. The aircraft then continued in operation and the damage was not discovered until first flight preparations the following day. The Investigation found that the Captain supervising a trainee First Officer as handling pilot failed to intervene appropriately during the approach and thereafter had failed to act responsibly. The context for poor performance was assessed as systemic weakness in both the way the ATR fleet was being run and in regulatory oversight of the Operator.

guid: https://skybrary.aero/accidents-and-incidents/at76-fez-morocco-2018 uri: https://skybrary.aero/accidents-and-incidents/at76-fez-morocco-2018 title: AT75, en-route, near Almansa Spain, 2017 link: https://skybrary.aero/accidents-and-incidents/at75-en-route-near-almansa-spain-2017 description:

On 9 September 2017, an ATR 72-500 crew temporarily lost control of their aircraft when it stalled whilst climbing in forecast moderate icing conditions after violation of applicable guidance. Recovery was then delayed because the correct stall recovery procedure was not followed. A MAYDAY declaration due to a perception of continuing control problems was followed by a comprehensively unstabilised ILS approach to Madrid. The Investigation concluded that the stall and its sequel were attributable to deficient flight management and inappropriate use of automation. The operator involved was recommended to implement corrective actions to improve the competence of its crews.

guid: https://skybrary.aero/accidents-and-incidents/at75-en-route-near-almansa-spain-2017 uri: https://skybrary.aero/accidents-and-incidents/at75-en-route-near-almansa-spain-2017 title: A346, en-route, northern Turkey, 2019 link: https://skybrary.aero/accidents-and-incidents/a346-en-route-northern-turkey-2019 description:

On 21 August 2019, an Airbus A340-600 encountered sudden-onset moderate to severe clear air turbulence whilst in the cruise at FL 360 over northern Turkey which resulted in a serious passenger injury. The Investigation found that the flight was above and in the vicinity of convective clouds exhibiting considerable vertical development but noted that neither the en-route forecast nor current alerting had given any indication that significant turbulence was likely to be encountered. It was noted the operator s flight crew had not been permitted to upload weather data in flight but since this event, that restriction had been removed.

guid: https://skybrary.aero/accidents-and-incidents/a346-en-route-northern-turkey-2019 uri: https://skybrary.aero/accidents-and-incidents/a346-en-route-northern-turkey-2019 title: SF34, Savonlinna Finland, 2019 link: https://skybrary.aero/accidents-and-incidents/sf34-savonlinna-finland-2019 description:

On 7 January 2019, a Saab 340B made a late touchdown during light snowfall at night close to the edge of the runway at Savonlinna before veering off and eventually stopping. The Investigation attributed the excursion to flight crew misjudgements when landing but also noted the aircraft operator had a long history of similar investigated events in Scandinavia and had failed to follow its own documented Safety Management System. The Investigation also concluded that there was a significant risk that EU competition rules could indirectly compromise publicly-funded air service contract tendering by discounting the operational safety assessment of tendering organisations.

guid: https://skybrary.aero/accidents-and-incidents/sf34-savonlinna-finland-2019 uri: https://skybrary.aero/accidents-and-incidents/sf34-savonlinna-finland-2019 title: C560, vicinity Oslo Norway, 2017 link: https://skybrary.aero/accidents-and-incidents/c560-vicinity-oslo-norway-2017 description:

On 11 January 2017, control of a Cessna Citation 560 departing Oslo on a short positioning flight was lost control during flap retraction when a violent nose-down manoeuvre occurred. The First Officer took control when the Captain did not react and recovered with a 6 g pullout which left only 170 feet of ground clearance. A MAYDAY - subsequently cancelled when control was regained - was declared and the intended flight was then completed without further event. The Investigation concluded that tailplane stall after the aircraft was not de-iced prior to departure was the probable cause of the upset.

guid: https://skybrary.aero/accidents-and-incidents/c560-vicinity-oslo-norway-2017 uri: https://skybrary.aero/accidents-and-incidents/c560-vicinity-oslo-norway-2017 title: DH8A, Rouyn-Noranda QC Canada, 2019 link: https://skybrary.aero/accidents-and-incidents/dh8a-rouyn-noranda-qc-canada-2019 description:

On 23 January 2019, a Bombardier DHC8-100 failed to complete its intended night takeoff from Rouyn-Noranda after it had not been commenced on or correctly aligned parallel to the (obscured) centreline and the steadily increasing deviation had not been recognised until a runway excursion was imminent. The Investigation attributed this to the failure of the crew to pay sufficient attention to the external perspective provided by the clearly-visible runway edge lighting whilst also noting the Captain s likely underestimation of the consequences of a significant flight deck authority gradient and a failure to fully follow relevant applicable operating procedures.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-rouyn-noranda-qc-canada-2019 uri: https://skybrary.aero/accidents-and-incidents/dh8a-rouyn-noranda-qc-canada-2019 title: BCS3, Porto Portugal, 2018 link: https://skybrary.aero/accidents-and-incidents/bcs3-porto-portugal-2018 description:

On 15 July 2018, an Airbus 220-300 crew were slow to recognise that the maximum de-rate thrust required for their takeoff from Porto had not been reached but after increasing it were able to get safely airborne prior to the end of the runway. The Investigation found that applicable SOPs had not been followed and that the function of both the spoiler and autothrottle systems was inadequately documented and understood and in the case of the former an arguably flawed design had been certified. Five similar events had been recorded by the aircraft operator involved in less than six months.

guid: https://skybrary.aero/accidents-and-incidents/bcs3-porto-portugal-2018 uri: https://skybrary.aero/accidents-and-incidents/bcs3-porto-portugal-2018 title: B744, Maastricht-Aachen Netherlands, 2017 link: https://skybrary.aero/accidents-and-incidents/b744-maastricht-aachen-netherlands-2017 description:

On 11 November 2017, a type-experienced Boeing 747-400ERF crew making a night rolling takeoff at Maastricht-Aachen lost aircraft directional control after an outer engine suddenly failed at low speed and a veer-off onto soft ground adjacent to the runway followed. The Investigation found that rather than immediately reject the takeoff when the engine failed, the crew had attempted to maintain directional control without thrust reduction to the point where an excursion became unavoidable. The effect of startle , the Captain s use of a noise cancelling headset and poor alerting to the engine failure by the First Officer were considered contributory.

guid: https://skybrary.aero/accidents-and-incidents/b744-maastricht-aachen-netherlands-2017 uri: https://skybrary.aero/accidents-and-incidents/b744-maastricht-aachen-netherlands-2017 title: A320, vicinity Karachi Pakistan, 2020 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-karachi-pakistan-2020 description:

On 22 May 2020, an Airbus A320 made an extremely high speed unstabilised ILS approach to runway 25L at Karachi and did not extend the landing gear for touchdown. It continued along the runway resting on both engines before getting airborne again with the crew announcing their intention to make another approach. Unfortunately, both engines failed due to the damage sustained and the aircraft crashed in a residential area near the airport and was destroyed by impact forces and a post-crash fire. 97 of the 99 occupants died and four persons on the ground were injured with one subsequently dying.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-karachi-pakistan-2020 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-karachi-pakistan-2020 title: B738, en-route, near Toyama Japan, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-toyama-japan-2018 description:

On 8 July 2018, a Boeing 737-800 discontinued three consecutive approaches at its intended destination Toyama because, despite unexceptional weather conditions, it was in each case, impossible to achieve or continue a stabilised approach within the operator s applicable criteria. Diversion to the designated alternate was then commenced with just sufficient fuel to reach it without using final reserve fuel. However, en-route the crew became concerned at their fuel status and ATC initially had difficulty receiving their emergency communications resulting in a MAYDAY declaration. An expedited routing then followed with a landing which just avoided the use of final reserve fuel.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-toyama-japan-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-near-toyama-japan-2018 title: B738, Sochi Russia, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-sochi-russia-2018 description:

On 1 September 2018, a Boeing 737-800, making its second night approach to Sochi beneath a large convective storm with low level windshear reported, floated almost halfway along the wet runway before overrunning it by approximately 400 metres and breaching the perimeter fence before stopping. A small fire did not prevent all occupants from safely evacuating. The Investigation attributed the accident to crew disregard of a number of windshear warnings and a subsequent encounter with horizontal windshear resulting in a late touchdown and noted that the first approach had meant that the crew had been poorly prepared for the second.

guid: https://skybrary.aero/accidents-and-incidents/b738-sochi-russia-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-sochi-russia-2018 title: DH8D, Yangon Myanmar, 2019 link: https://skybrary.aero/accidents-and-incidents/dh8d-yangon-myanmar-2019 description:

On 8 May 2019, a Bombardier DHC8-400 making its second approach to Yangon during a thunderstorm touched down over halfway along the runway after an unstabilised approach but then briefly became airborne again before descending very rapidly and sustaining extreme structural damage on impact before sliding off the end of the runway. The Investigation found that prior to the final rapid descent and impact, the Captain had placed the power levers into the beta range, an explicitly prohibited action unless an aircraft is on the ground. No cause for the accident other than the actions of the crew was identified.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-yangon-myanmar-2019 uri: https://skybrary.aero/accidents-and-incidents/dh8d-yangon-myanmar-2019 title: F50, vicinity Nairobi Kenya, 2014 link: https://skybrary.aero/accidents-and-incidents/f50-vicinity-nairobi-kenya-2014 description:

On 2 July 2014, a Fokker 50 fully loaded - and probably overloaded - with a cargo of qat crashed into a building and was destroyed soon after its night departure from Nairobi after failing to climb due to a left engine malfunction which was evident well before V1. The Investigation attributed the accident to the failure of the crew to reject the takeoff after obvious malfunction of the left engine soon after they had set takeoff power which triggered a repeated level 3 Master Warning that required an automatic initiation of a rejected takeoff.

guid: https://skybrary.aero/accidents-and-incidents/f50-vicinity-nairobi-kenya-2014 uri: https://skybrary.aero/accidents-and-incidents/f50-vicinity-nairobi-kenya-2014 title: AT76, Canberra Australia, 2017 link: https://skybrary.aero/accidents-and-incidents/at76-canberra-australia-2017 description:

On 19 November 2017, an ATR 72-600 being operated by a flight crew who were simultaneously undertaking a routine Line Check during revenue flying made a hard landing at Canberra which caused significant damage to the aircraft. The Investigation noted that the low experience First Officer had mismanaged the final stages of the approach so that it was no longer stabilised and that although the opportunity was there, the Captain had failed to intervene promptly enough to prevent the resulting hard landing. The Check Captain had assessed the imminent landing as likely to be untidy rather than unsafe.

guid: https://skybrary.aero/accidents-and-incidents/at76-canberra-australia-2017 uri: https://skybrary.aero/accidents-and-incidents/at76-canberra-australia-2017 title: AT75, vicinity Nelson New Zealand, 2017 link: https://skybrary.aero/accidents-and-incidents/at75-vicinity-nelson-new-zealand-2017 description:

On 9 April 2017, an ATR 72-500 crew were unable to obtain a right main landing gear locked down indication during their approach to Nelson and diverted to Palmerston North where the gear did not collapse on landing. The Investigation found the indication had been consequent on failure of both right main gear locking springs due to corrosion and that existing preventative maintenance procedures would not have detected this. It was also noted that contrary to the applicable procedures, the crew had cycled the gear several times which might, but in the event did not, have had significant effects.

guid: https://skybrary.aero/accidents-and-incidents/at75-vicinity-nelson-new-zealand-2017 uri: https://skybrary.aero/accidents-and-incidents/at75-vicinity-nelson-new-zealand-2017 title: SB20, Unalaska AK USA, 2019 link: https://skybrary.aero/accidents-and-incidents/sb20-unalaska-ak-usa-2019 description:

On 17 October 2019, a Saab 2000 overran the Unalaska runway after touchdown following difficulty braking and exited the airport perimeter before finally coming to rest on shoreline rocks. The Investigation attributed the poor braking to incorrect brake system wiring originating during maintenance some 2½ years earlier but noted the touchdown occurred with crew awareness that the prevailing tailwind component was well in excess of the permitted limits with no reason not to use the into-wind runway and attributed this to plan continuation bias. The aircraft operator’s failure to apply their specifically-applicable airport qualification requirements to the Captain was noted.

guid: https://skybrary.aero/accidents-and-incidents/sb20-unalaska-ak-usa-2019 uri: https://skybrary.aero/accidents-and-incidents/sb20-unalaska-ak-usa-2019 title: B38M, Helsinki Finland, 2019 link: https://skybrary.aero/accidents-and-incidents/b38m-helsinki-finland-2019 description:

On 18 January 2019, two aircraft taxiing for departure at Helsinki were cleared to cross the landing runway between two landing aircraft. Landing clearance for the second was given once the crossing traffic had cleared as it passed 400 feet in expectation that the previous landing aircraft would also shortly be clear. However, the first landing aircraft was slower than expected clearing the runway and so the second was instructed to go-around but did not then do so because this instruction was lost in the radar height countdown below 50 feet and the runway was seen clear before touchdown.

guid: https://skybrary.aero/accidents-and-incidents/b38m-helsinki-finland-2019 uri: https://skybrary.aero/accidents-and-incidents/b38m-helsinki-finland-2019 title: B748, Tokyo Narita Japan, 2017 link: https://skybrary.aero/accidents-and-incidents/b748-tokyo-narita-japan-2017 description:

On 15 July 2017, a Boeing 747-8F close to its maximum takeoff weight only became airborne just before the end of the 2,500 metre-long north runway at Narita after the reduced thrust applicable to the much longer south runway was used for the takeoff and the aircraft cleared the upwind runway threshold by only 16 feet. The Investigation found that the very experienced Captain and the very inexperienced First Officer had both failed to follow elements of the applicable takeoff performance change procedures after the departure runway anticipated during pre-start flight preparations prior to ATC clearance delivery had changed.

guid: https://skybrary.aero/accidents-and-incidents/b748-tokyo-narita-japan-2017 uri: https://skybrary.aero/accidents-and-incidents/b748-tokyo-narita-japan-2017 title: S76, en-route, southeast of Lagos Nigeria, 2016 link: https://skybrary.aero/accidents-and-incidents/s76-en-route-southeast-lagos-nigeria-2016 description:

On 3 February 2016, a Sikorsky S76C on a flight from an offshore platform to Lagos was ditched when the crew believed that it was no longer possible to complete their intended flight to Lagos. After recovering the helicopter from the seabed, the Investigation concluded that the crew had failed to perform a routine standard procedure after takeoff - resetting the compass to ‘slave rather than ‘free’ mode - and had then failed to recognise that this was the cause of the flight path control issues which they were experiencing or disconnect the autopilot and fly the aircraft manually.

guid: https://skybrary.aero/accidents-and-incidents/s76-en-route-southeast-lagos-nigeria-2016 uri: https://skybrary.aero/accidents-and-incidents/s76-en-route-southeast-lagos-nigeria-2016 title: B738, vicinity Tehran Iran, 2020 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-tehran-iran-2020 description:

On 8 January 2020, a Boeing 737-800 was destroyed by a ground to air missile when climbing through approximately 4800 feet aal three minutes after takeoff from Tehran for Kiev and its 176 occupants were killed. The Investigation is continuing but it has been confirmed that severe damage and an airborne fire followed the detonation of a proximity missile after a military targeting error, with subsequent ground impact. It is also confirmed that the flight was following its ATC clearance and that a sequence of four separate errors led to two missiles being fired at the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-tehran-iran-2020 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-tehran-iran-2020 title: A320 (2) / CRJX (2) / B738 (3) / A332, vicinity Madrid Barajas Spain, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-2-crjx-2-b738-3-a332-vicinity-madrid-barajas-spain-2018 description:

On 27 May 2018, four losses of separation on final approach during use of dependent parallel landing runways occurred within 30 minutes at Madrid following a non-scheduled weather-induced runway configuration change. This continuing situation was then resolved by reverting to a single landing runway. The Investigation attributed these events to “the complex operational situation” which had prevailed following a delayed decision to change runway configuration after seven consecutive go-arounds in 10 minutes using the previous standard runway configuration. The absence of sufficient present weather information for the wider Madrid area to adequately inform ATC tactical strategy was assessed as contributory.

guid: https://skybrary.aero/accidents-and-incidents/a320-2-crjx-2-b738-3-a332-vicinity-madrid-barajas-spain-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-2-crjx-2-b738-3-a332-vicinity-madrid-barajas-spain-2018 title: DH8D, vicinity Exeter UK, 2010 link: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-exeter-uk-2010 description:

On 11 September 2010, a DHC8-400 being operated by Flybe on a scheduled passenger flight from Bergerac France to Exeter failed to level as cleared during the approach at destination in day VMC and continued a premature descent without the awareness of either pilot due to distraction following a minor system malfunction until an EGPWS PULL UP Hard Warning occurred following which a recovery climb was initiated. There were no abrupt manoeuvres and no injuries to any of the 53 occupants.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-exeter-uk-2010 uri: https://skybrary.aero/accidents-and-incidents/dh8d-vicinity-exeter-uk-2010 title: A306, East Midlands UK, 2011 link: https://skybrary.aero/accidents-and-incidents/a306-east-midlands-uk-2011 description:

On 10 January 2011, an Air Atlanta Icelandic Airbus A300-600 on a scheduled cargo flight made a bounced touchdown at East Midlands and then attempted a go around involving retraction of the thrust reversers after selection out and before they had fully deployed. This prevented one engine from spooling up and, after a tail strike during rotation, the single engine go around was conducted with considerable difficulty at a climb rate only acceptable because of a lack of terrain challenges along the climb out track.

guid: https://skybrary.aero/accidents-and-incidents/a306-east-midlands-uk-2011 uri: https://skybrary.aero/accidents-and-incidents/a306-east-midlands-uk-2011 title: B733, vicinity Montpelier, France 2011 link: https://skybrary.aero/accidents-and-incidents/b733-vicinity-montpelier-france-2011 description:

On 10 January 2011, a Europe Airpost Boeing 737-300 taking off from Montpelier after repainting had just rotated for take off when the leading edge slats extended from the Intermediate position to the Fully Extended position and the left stick shaker was activated as a consequence of the reduced stalling angle of attack. Initial climb was sustained and soon afterwards, the slats returned to their previous position and the stick shaker activation stopped. The unexpected configuration change was attributed to paint contamination of the left angle of attack sensor, the context for which was inadequate task guidance.

guid: https://skybrary.aero/accidents-and-incidents/b733-vicinity-montpelier-france-2011 uri: https://skybrary.aero/accidents-and-incidents/b733-vicinity-montpelier-france-2011 title: B733, Paris CDG France, 2011 link: https://skybrary.aero/accidents-and-incidents/b733-paris-cdg-france-2011 description:

On 23 July 2011, a Boeing 737-300 being operated by Jet2.com on a passenger flight from Leeds/Bradford to Paris CDG experienced violent vibration from the main landing gear at touch down in normal day visibility on runway 27R at a normal speed off a stabilised approach. This vibration was accompanied by lateral acceleration that made directional control difficult but the aircraft was kept on the runway and at a speed of 75 knots, the vibrations abruptly stopped. Once clear of the runway, the aircraft was stopped and the engines shutdown prior to a tow to the gate. None of the 133 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/b733-paris-cdg-france-2011 uri: https://skybrary.aero/accidents-and-incidents/b733-paris-cdg-france-2011 title: MD82, en-route, near Machiques Venezuela, 2005 link: https://skybrary.aero/accidents-and-incidents/md82-en-route-near-machiques-venezuela-2005 description:

On 16 August 2005, the flight crew of a West Caribbean MD82 on a passenger flight from Tocumen Airport in Panama to Martinique attempted to cruise at a level which was incompatible with aircraft performance. They then failed to recognise the results of this action and when the lack of sufficient engine thrust led to an aerodynamic stall and confusion precluded a recovery before the aircraft impacted terrain at high speed out of control killing all 152 occupants.

guid: https://skybrary.aero/accidents-and-incidents/md82-en-route-near-machiques-venezuela-2005 uri: https://skybrary.aero/accidents-and-incidents/md82-en-route-near-machiques-venezuela-2005 title: A319 / UNKN, Stockholm Arlanda Sweden, 2011 link: https://skybrary.aero/accidents-and-incidents/a319-unkn-stockholm-arlanda-sweden-2011 description:

On 5 February 2011, an Airbus A319-100 being operated by Air Berlin on a passenger flight departing Stockholm inadvertently proceeded beyond the given clearance limit for runway 19R and although it subsequently stopped before runway entry had occurred, it was by then closer to high speed departing traffic than it should have been. There was no abrupt stop and none of the 103 occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/a319-unkn-stockholm-arlanda-sweden-2011 uri: https://skybrary.aero/accidents-and-incidents/a319-unkn-stockholm-arlanda-sweden-2011 title: DH8A, en-route near Sørkjosen Norway link: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-near-sorkjosen-norway description:

On 21 February 2006, a Bombardier DHC8-100 being operated by Widereo Flyveselskap on a passenger flight from Tromsø to Sørkjosen experienced a temporary loss of control during descent in night IMC when the power levers were inadvertently selected to a position aft of the Flight Idle gate and propeller overspeed and engine malfunction followed. After recovery and shut down of the right engine, a return to Tromsø was made using the remaining engine without further event.

guid: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-near-sorkjosen-norway uri: https://skybrary.aero/accidents-and-incidents/dh8a-en-route-near-sorkjosen-norway title: B722, Moncton Canada, 2010 link: https://skybrary.aero/accidents-and-incidents/b722-moncton-canada-2010 description:

On 24 March 2010, a Boeing 727-200 being operated by Canadian company Cargojet AW on a scheduled cargo flight from Hamilton Ontario to Moncton New Brunswick failed to stop after a night landing on 1875 metre long runway 06 at destination in normal ground visibility and eventually stopped in deep mud approximately 100 metres beyond the runway end and approximately 40 metres past the end of the paved runway end strip. The three operating flight crew, who were the only occupants, were uninjured and the aircraft received only minor damage.

guid: https://skybrary.aero/accidents-and-incidents/b722-moncton-canada-2010 uri: https://skybrary.aero/accidents-and-incidents/b722-moncton-canada-2010 title: B752, Jackson Hole WY USA, 2010 link: https://skybrary.aero/accidents-and-incidents/b752-jackson-hole-wy-usa-2010 description:

On 29 December 2010 an American Airlines Boeing 757-200 overran the landing runway at Jackson Hole WY after a bounced touchdown following which neither the speed brakes nor the thrust reversers functioned as expected. The subsequent investigation found that although the speed brakes had been armed and the deployed call had been made, this had not occurred and that the thrust reversers had locked on transit after premature selection during the bounce. It was noted that had the spoilers been manually selected, the thrust reverser problem would not have prevented the aircraft stopping on the runway.

guid: https://skybrary.aero/accidents-and-incidents/b752-jackson-hole-wy-usa-2010 uri: https://skybrary.aero/accidents-and-incidents/b752-jackson-hole-wy-usa-2010 title: A319, Belfast Aldergrove UK, 2011 link: https://skybrary.aero/accidents-and-incidents/a319-belfast-aldergrove-uk-2011 description:

On 6 January 2011 an Easyjet Airbus A319 experienced the sudden onset of thick smoke in the cabin as the aircraft cleared the runway after landing. The aircraft was stopped and an evacuation was carried out during which one of the 52 occupants received a minor injury. The subsequent investigation attributed the occurrence to the continued use of reverse idle thrust after clearing the runway onto a little used taxiway where the quantity of de-ice fluid residue was much greater than on the runway.

guid: https://skybrary.aero/accidents-and-incidents/a319-belfast-aldergrove-uk-2011 uri: https://skybrary.aero/accidents-and-incidents/a319-belfast-aldergrove-uk-2011 title: B752, Denver CO USA, 2011 link: https://skybrary.aero/accidents-and-incidents/b752-denver-co-usa-2011 description:

On 26 September 2011, a Boeing 757-200 being operated by United Airlines on a scheduled passenger flight from Chicago to Denver experienced a left engine bird strike during deceleration after landing on runway 35R at destination in normal day visibility. The affected engine ran down as the aircraft cleared the runway and was shut down after a report of smoke being emitted from it. The aircraft was stopped and the remaining engine also shut down prior to a tow to the assigned terminal gate for passenger disembarkation. None of the 185 occupants were injured but the affected engine was severely damaged and there was visible evidence that some debris from it had impacted the aircraft fuselage.

guid: https://skybrary.aero/accidents-and-incidents/b752-denver-co-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/b752-denver-co-usa-2011 title: E145/C172, Gulfport MS USA, 2011 link: https://skybrary.aero/accidents-and-incidents/e145c172-gulfport-ms-usa-2011 description:

On 19 June 2011, an Embraer ERJ145 being operated by Expressjet AL on a scheduled passenger flight departing Gulfport in day VMC came into close proximity with a privately operated Cessna 172 which had just departed another runway at the same airport which had an extended centreline which passed through the centreline of the runway used by the 145. There was no manoeuvring by either aircraft and no injuries to any occupants.

guid: https://skybrary.aero/accidents-and-incidents/e145c172-gulfport-ms-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/e145c172-gulfport-ms-usa-2011 title: MD11, Riyadh Saudi Arabia, 2010 link: https://skybrary.aero/accidents-and-incidents/md11-riyadh-saudi-arabia-2010 description:

On 27 July 2010, a Boeing MD11F being operated by Lufthansa Cargo on a scheduled flight from Frankfurt to Riyadh bounced twice prior to a third hard touchdown whilst attempting to land on 4205 metre-long Runway 33L at destination in normal day visibility. The fuselage was ruptured and, as the aircraft left the side of the runway, the nose landing gear collapsed and a fire began to take hold. A ‘MAYDAY’ call was made as the aircraft slid following the final touchdown. Once the aircraft had come to a stop, the two pilots evacuated before it was largely destroyed by fire. One pilot received minor injuries, the other injuries described as major.

guid: https://skybrary.aero/accidents-and-incidents/md11-riyadh-saudi-arabia-2010 uri: https://skybrary.aero/accidents-and-incidents/md11-riyadh-saudi-arabia-2010 title: DH8D/DH8D, vicinity Toronto City Airport Canada, 2010 link: https://skybrary.aero/accidents-and-incidents/dh8ddh8d-vicinity-toronto-city-airport-canada-2010 description:

On 11 May 2010, a Bombardier DHC8-400 aircraft being operated by Porter AL on a scheduled passenger flight Toronto City to Ottawa and another aircraft of the same type and operator on a scheduled passenger flight from Montreal to Toronto City came into close proximity south east of the airport and received and actioned co-ordinated TCAS RAs. Minimum separation was 300 feet vertically at the same altitude. There were no abrupt manoeuvres and none of the occupants were injured.

guid: https://skybrary.aero/accidents-and-incidents/dh8ddh8d-vicinity-toronto-city-airport-canada-2010 uri: https://skybrary.aero/accidents-and-incidents/dh8ddh8d-vicinity-toronto-city-airport-canada-2010 title: B737, Chicago Midway IL, USA 2011 link: https://skybrary.aero/accidents-and-incidents/b737-chicago-midway-il-usa-2011 description:

On 26 April 2011 a Southwest Boeing 737-700 was assessed as likely not to stop before the end of landing runway 13C at alternate Chicago Midway in daylight and was intentionally steered to the grass to the left of the runway near the end, despite the presence of a EMAS. The subsequent investigation determined that the poor deceleration was a direct consequence of a delay in the deployment of both speed brakes and thrust reverser. It was noted that the crew had failed to execute the Before Landing Checklist which includes verification of speed brake arming.

guid: https://skybrary.aero/accidents-and-incidents/b737-chicago-midway-il-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/b737-chicago-midway-il-usa-2011 title: AT72, en-route, southern Scotland UK, 2011 link: https://skybrary.aero/accidents-and-incidents/at72-en-route-southern-scotland-uk-2011 description:

On 15 March 2011, an ATR 72-200 on a non revenue positioning flight from Edinburgh to Paris CDG in night VMC with just the two pilots on board began to experience roll and directional control difficulties as the aircraft accelerated upon reaching the planned cruise altitude of FL230. A PAN call was made to ATC and a return to Edinburgh was made with successful containment of the malfunctioning flying controls.

guid: https://skybrary.aero/accidents-and-incidents/at72-en-route-southern-scotland-uk-2011 uri: https://skybrary.aero/accidents-and-incidents/at72-en-route-southern-scotland-uk-2011 title: MA60, vicinity Kaimana West Papua Indonesia, 2011 link: https://skybrary.aero/accidents-and-incidents/ma60-vicinity-kaimana-west-papua-indonesia-2011 description:

On 7 May 2011, the crew of a Xian MA60 lost control of their aircraft during an attempted go around at Kaimana after failing to obtain sufficient visual reference to complete the approach despite a significant violation of the minima for the required visual-only approach. The aircraft was destroyed by the high speed impact and all occupants were killed. The Investigation found that the crew had comprehensively failed to conduct the go around procedure as prescribed and it was suspected that the new-to-type Captain may have reverted to procedures for his previous jet aircraft type after ineffective type conversion training.

guid: https://skybrary.aero/accidents-and-incidents/ma60-vicinity-kaimana-west-papua-indonesia-2011 uri: https://skybrary.aero/accidents-and-incidents/ma60-vicinity-kaimana-west-papua-indonesia-2011 title: B738/B738, vicinity Queenstown New Zealand, 2010 link: https://skybrary.aero/accidents-and-incidents/b738b738-vicinity-queenstown-new-zealand-2010 description:

On 20 June 2010, a Boeing 737-800 being operated by New Zealand company Pacific Blue AL on a scheduled passenger flight from Auckland to Queenstown lost IFR separation assurance against a Boeing 737-800 being operated by Qantas on a scheduled passenger flight from Sydney to Queenstown whilst both aircraft were flying a go around following successive but different instrument approaches at their shared intended destination. There were no abrupt manoeuvres and none of the respectively 88 and 162 occupants of the two aircraft were injured.

guid: https://skybrary.aero/accidents-and-incidents/b738b738-vicinity-queenstown-new-zealand-2010 uri: https://skybrary.aero/accidents-and-incidents/b738b738-vicinity-queenstown-new-zealand-2010 title: BN2P, Montserrat (British Overseas Territory), 2011 link: https://skybrary.aero/accidents-and-incidents/bn2p-montserrat-british-overseas-territory-2011 description:

On 22 May 2011 a Britten-Norman BN2A Islander being operated by Bermudian domiciled carrier Montserrat AW on a scheduled passenger flight from Antigua to Montserrat was considered at risk of an overrun after visual positioning to a day landing on runway 28 at destination in normal ground visibility. The pilot intentionally steered the aircraft off one side of the runway to decrease the degree of potential hazard and the aircraft came to a stop beside the runway and 46 metres from its end without injuries to any of the 8 occupants or damage to the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/bn2p-montserrat-british-overseas-territory-2011 uri: https://skybrary.aero/accidents-and-incidents/bn2p-montserrat-british-overseas-territory-2011 title: A333, en-route, south of Moscow Russia, 2010 link: https://skybrary.aero/accidents-and-incidents/a333-en-route-south-moscow-russia-2010 description:

On 22 December 2010, a Finnair Airbus A330-300 inbound to Helsinki and cruising in very cold air at an altitude of 11,600 metres lost cabin pressurisation in cruise flight and completed an emergency descent before continuing the originally intended flight at a lower level. The subsequent Investigation was carried out together with that into a similar occurrence to another Finnair A330 which had occurred 11 days earlier. It was found that in both incidents, both engine bleed air systems had failed to function normally because of a design fault which had allowed water within their pressure transducers to freeze.

guid: https://skybrary.aero/accidents-and-incidents/a333-en-route-south-moscow-russia-2010 uri: https://skybrary.aero/accidents-and-incidents/a333-en-route-south-moscow-russia-2010 title: CRJ2, en-route, south of Santander Spain, 2009 link: https://skybrary.aero/accidents-and-incidents/crj2-en-route-south-santander-spain-2009 description:

On 24 February 2009, the Captain of a CRJ 200 being operated by Air Nostrum on a passenger flight from Madrid to Santander inadvertently shut down both engines simultaneously during the descent but a successful restart was rapidly achieved and the remainder of the flight was uneventful. The subsequent investigation concluded that the shutdown was the consequence of both violation of procedure and lack of knowledge of the Captain involved.

guid: https://skybrary.aero/accidents-and-incidents/crj2-en-route-south-santander-spain-2009 uri: https://skybrary.aero/accidents-and-incidents/crj2-en-route-south-santander-spain-2009 title: B738/B763, Barcelona Spain, 2011 link: https://skybrary.aero/accidents-and-incidents/b738b763-barcelona-spain-2011 description:

On 14 April 2011, a Ryanair Boeing 737-800 failed to leave sufficient clearance when taxiing behind a stationary Boeing 767-300 at Barcelona and the 737 wingtip was in collision with the horizontal stabiliser of the 767, damaging both. The 767 crew were completely unaware of any impact but the 737 crew realised the close proximity but dismissed a cabin crew report that a passenger had observed a collision. Both aircraft completed their intended flights without incident after which the damage was discovered, that to the 767 requiring that the aircraft be repaired before further flight.

guid: https://skybrary.aero/accidents-and-incidents/b738b763-barcelona-spain-2011 uri: https://skybrary.aero/accidents-and-incidents/b738b763-barcelona-spain-2011 title: B752, vicinity Atlanta GA USA, 2011 link: https://skybrary.aero/accidents-and-incidents/b752-vicinity-atlanta-ga-usa-2011 description:

On 11 March 2011, a Delta AL Boeing 757 departed Atlanta GA with no secondary radar indication visible to ATC and also failed to make contact with departure radar after accepting the frequency transfer instruction. During the eight minutes out of radio contact, it successively lost separation against two light aircraft and another passenger aircraft as it followed the cleared RNAV departure routing for eight minutes until the crew queried further climb on the TWR frequency and were invited to select their transponder on and contact the correct frequency.

guid: https://skybrary.aero/accidents-and-incidents/b752-vicinity-atlanta-ga-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/b752-vicinity-atlanta-ga-usa-2011 title: DH8A/DH8C, en-route, northern Canada, 2011 link: https://skybrary.aero/accidents-and-incidents/dh8adh8c-en-route-northern-canada-2011 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/dh8adh8c-en-route-northern-canada-2011 uri: https://skybrary.aero/accidents-and-incidents/dh8adh8c-en-route-northern-canada-2011 title: B738/B734, Johannesburg South Africa, 2010 link: https://skybrary.aero/accidents-and-incidents/b738b734-johannesburg-south-africa-2010 description:

On 27 July 2010, a South African Airways Boeing 737-800 on take from Runway 21R was instructed to reject that take off when already at high speed because a Boeing 737-400 was crossing the same runway ahead. The rejected take off was successful. The Investigation found that both aircraft had been operated in accordance with clearances issued by the responsible position in TWR ATC where OJT was in progress.

guid: https://skybrary.aero/accidents-and-incidents/b738b734-johannesburg-south-africa-2010 uri: https://skybrary.aero/accidents-and-incidents/b738b734-johannesburg-south-africa-2010 title: CRJ2/ATP, Stockholm Sweden, 2011 link: https://skybrary.aero/accidents-and-incidents/crj2atp-stockholm-sweden-2011 description:

On 21 January 2011, a Belarusian Bombardier CRJ200 failed to fly the prescribed missed approach procedure at night in IMC and when ATC observed a developing conflict with another aircraft which had just departed another runway with a conflicting clearance, both aircraft were given heading instructions to mitigate the proximity risk. The resulting CPA was 1.8nm at an altitude of 1600 feet. The subsequent investigation attributed the pilot error to a change of aircraft control in the flare when it became apparent that a safe landing was not assured.

guid: https://skybrary.aero/accidents-and-incidents/crj2atp-stockholm-sweden-2011 uri: https://skybrary.aero/accidents-and-incidents/crj2atp-stockholm-sweden-2011 title: WW24, vicinity Norfolk Island South Pacific, 2009 link: https://skybrary.aero/accidents-and-incidents/ww24-vicinity-norfolk-island-south-pacific-2009 description:

On 18 November 2009, an IAI Westwind on a medevac mission failed to make a planned night landing at Norfolk Island in unanticipated adverse weather and was intentionally ditched offshore because of insufficient fuel to reach the nearest alternate. The fuselage broke in two on water contact but all six occupants escaped from the rapidly sinking wreckage and were eventually rescued. The Investigation initially completed in 2012 was reopened after concerns about its conduct and a new Final Report in 2017 confirmed that the direct cause was flawed crew decision-making but also highlighted ineffective regulatory oversight and inadequate Operator procedures.

guid: https://skybrary.aero/accidents-and-incidents/ww24-vicinity-norfolk-island-south-pacific-2009 uri: https://skybrary.aero/accidents-and-incidents/ww24-vicinity-norfolk-island-south-pacific-2009 title: DH8C, Kimberley South Africa, 2010 link: https://skybrary.aero/accidents-and-incidents/dh8c-kimberley-south-africa-2010 description:

On 16 July 2010, a South African Express Airways Bombardier DHC 8-300 hit an animal during a night landing at Kimberley after a passenger flight from Johannesburg. The nose landing gear took a direct hit and collapsed but after a temporary loss of directional control, the runway centreline was regained and the aircraft brought to a stop. The Investigation found wildlife access to the aerodrome was commonplace and the attempts at control inadequate.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-kimberley-south-africa-2010 uri: https://skybrary.aero/accidents-and-incidents/dh8c-kimberley-south-africa-2010 title: E145, Stuttgart Germany, 2009 link: https://skybrary.aero/accidents-and-incidents/e145-stuttgart-germany-2009 description:

On 5 January 2009, a Flybe Embraer 145 made a late touchdown with slight snow falling on a runway pre-notified as affected by slush deposits and failed to stop until it had overrun into the RESA where it finally stopped on a heading 25º off the runway alignment. The Investigation concluded that although the airport operator process for determining braking action was flawed and two Safety Recommendations were made in that respect, the overrun of the 3045metres LDA was attributable to flight crew action and that operator guidance was deficient.

guid: https://skybrary.aero/accidents-and-incidents/e145-stuttgart-germany-2009 uri: https://skybrary.aero/accidents-and-incidents/e145-stuttgart-germany-2009 title: B738, en-route, east of Asahikawa Japan, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-east-asahikawa-japan-2010 description:

On 26 October 2010, an All Nippon Boeing 737-800 was radar vectored towards mountainous terrain and simultaneously given descent clearance to an altitude which was 5000 feet below the applicable MVA whilst in IMC without full flight crew awareness. Two TAWS PULL UP hard warnings occurred in quick succession as a result. The flight crew responses were as prescribed and the subsequent investigation found that the closest recorded proximity to terrain had been 655 feet. It was established that the controller had forgotten about MVA.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-east-asahikawa-japan-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-east-asahikawa-japan-2010 title: MD82, Phuket Thailand, 2007 link: https://skybrary.aero/accidents-and-incidents/md82-phuket-thailand-2007 description:

On 16 September 2007, an MD-82 being operated by One Two Go Airlines attempted a missed approach from close to the runway at Phuket but after the flight crew failed to ensure that the necessary engine thrust was applied, the aircraft failed to establish a climb and after control was lost, the aircraft impacted the ground within the airport perimeter and was destroyed by the impact and a subsequent fire. Ninety of the 130 occupants were killed, 26 suffered serious injuries and 14 suffered minor injuries.

guid: https://skybrary.aero/accidents-and-incidents/md82-phuket-thailand-2007 uri: https://skybrary.aero/accidents-and-incidents/md82-phuket-thailand-2007 title: RJ85 / Vehicle, Gothenburg Sweden, 2011 link: https://skybrary.aero/accidents-and-incidents/rj85-vehicle-gothenburg-sweden-2011 description:

On 8 September 2011, a Brussels Airlines Avro RJ85 on the take off roll at Gothenburg came close to collision with a vehicle which the subsequent investigation found had been issued with clearance to enter the same runway as a result of controller error in the context of non-essential conversation. The vehicle saw the approaching aircraft just before entering the runway and stopped just clear of the runway approximately 40 metres ahead of the point at which it became airborne.

guid: https://skybrary.aero/accidents-and-incidents/rj85-vehicle-gothenburg-sweden-2011 uri: https://skybrary.aero/accidents-and-incidents/rj85-vehicle-gothenburg-sweden-2011 title: F100, Southampton UK, 1998 link: https://skybrary.aero/accidents-and-incidents/f100-southampton-uk-1998 description:

On 24 November 1998, a KLM uk Fokker 100 overran runway 20 at Southampton after a late and fast daylight touchdown in rain was followed by poor braking. The Investigation found that the assessment of the runway as ‘wet’ passed by ATC prior the incident was correct but that sudden heavy rain shortly before the aircraft landed had caused a rapid deterioration to somewhere between ‘Wet’ and ‘Flooded’. Slow drainage of water from the runway was subsequently identified and the runway was grooved.

guid: https://skybrary.aero/accidents-and-incidents/f100-southampton-uk-1998 uri: https://skybrary.aero/accidents-and-incidents/f100-southampton-uk-1998 title: B744 / Vehicle, Luxembourg Airport, Luxembourg 2010 link: https://skybrary.aero/accidents-and-incidents/b744-vehicle-luxembourg-airport-luxembourg-2010 description:

On 21 January 2010, a Cargolux Boeing 747-400F was in collision with an unoccupied van whilst about to touch down on runway 24 at Luxembourg airport in thick fog following a Cat 3b ILS approach. It was subsequently established that a maintenance crew and their vehicle had earlier been cleared to enter the active runway but their presence had then been overlooked. Comprehensive safety recommendations to rectify deficiencies in both ATC procedures and prevailing ATC practices were made by the Investigation.

guid: https://skybrary.aero/accidents-and-incidents/b744-vehicle-luxembourg-airport-luxembourg-2010 uri: https://skybrary.aero/accidents-and-incidents/b744-vehicle-luxembourg-airport-luxembourg-2010 title: A109, vicinity London Heliport London UK, 2013 link: https://skybrary.aero/accidents-and-incidents/a109-vicinity-london-heliport-london-uk-2013 description:

On 16 January 2013, an Augusta 109E helicopter positioning by day on an implied (due to adverse weather conditions) SVFR clearance collided with a crane attached to a tall building under construction. It and associated debris fell to street level and the pilot and a pedestrian were killed and several others on the ground injured. It was concluded that the pilot had not seen the crane or seen it too late to avoid whilst flying by visual reference in conditions which had become increasingly challenging. The Investigation recommended improvements in the regulatory context in which the accident had occurred.

guid: https://skybrary.aero/accidents-and-incidents/a109-vicinity-london-heliport-london-uk-2013 uri: https://skybrary.aero/accidents-and-incidents/a109-vicinity-london-heliport-london-uk-2013 title: A321, Manchester UK, 2011 (2) link: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2011-2 description:

On 23 December 2011, an Austrian Airlines Airbus A321 sustained a tail strike at Manchester as the main landing gear contacted the runway during a night go around initiated at a very low height after handling difficulties in the prevailing wind shear. The remainder of the go around and subsequent approach in similar conditions was uneventful and the earlier tail strike was considered to have been the inevitable consequence of initiating a go around so close to the ground after first reducing thrust to idle. Damage to the aircraft rendered it unfit for further flight until repaired but was relatively minor.

guid: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2011-2 uri: https://skybrary.aero/accidents-and-incidents/a321-manchester-uk-2011-2 title: AS50, Dalamot Norway, 2011 link: https://skybrary.aero/accidents-and-incidents/as50-dalamot-norway-2011 description:

On 4 July 2011, a Eurocopter AS 350 making a passenger charter flight to a mountain cabin in day VMC appeared to suddenly depart controlled flight whilst making a tight right turn during positioning to land at the destination landing site and impacted terrain soon afterwards. The helicopter was destroyed by the impact and ensuing fire and all five occupants were fatally injured. The subsequent investigation came to the conclusion that the apparently abrupt manoeuvring may have led to an encounter with servo transparency at a height from which the pilot was unable to recover before impact occurred.

guid: https://skybrary.aero/accidents-and-incidents/as50-dalamot-norway-2011 uri: https://skybrary.aero/accidents-and-incidents/as50-dalamot-norway-2011 title: A320, en-route, North East Spain 2006 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-east-spain-2006 description:

On 28 May 2006, a Vueling Airbus A320 encountered sudden significant turbulence at FL325 and, during a temporary loss of control, was forced down to FL310 before recovery was achieved. Seven occupants sustained minor injuries and there was some internal damage caused by an unrestrained cabin service cart. The origin of the disturbance was found to have been wake vortices from an Airbus A340-300 which was 10nm ahead and 500 feet above on the same airway but the Investigation found that the crew response had been inappropriate and could have served to exacerbate the effects of the external disturbance.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-east-spain-2006 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-east-spain-2006 title: B738, Perth Western Australia, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-perth-western-australia-2010 description:

On 24 February 2010, a Garuda Boeing 737-800 misunderstood the runway exit instruction issued during their landing roll at Perth and turned onto an intersecting active runway. An expeditious exit from this runway followed and no actual conflict resulted. The phraseology used by air traffic control was open to incorrect interpretation by the flight crew and led to their premature turn off the landing runway despite a prior briefing on exit options.

guid: https://skybrary.aero/accidents-and-incidents/b738-perth-western-australia-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-perth-western-australia-2010 title: B744, en-route, East China Sea, 2011 link: https://skybrary.aero/accidents-and-incidents/b744-en-route-east-china-sea-2011 description:

On 28 July 2011, 50 minutes after take off from Incheon, the crew of an Asiana Boeing 747-400F declared an emergency advising a main deck fire and an intention to divert to Jeju. The effects of the rapidly escalating fire eventually made it impossible to retain control and the aircraft crashed into the sea. The Investigation concluded that the origin of the fire was two adjacent pallets towards the rear of the main deck which contained Dangerous Goods shipments including Lithium ion batteries and flammable substances and that the aircraft had broken apart in mid-air following the loss of control.

guid: https://skybrary.aero/accidents-and-incidents/b744-en-route-east-china-sea-2011 uri: https://skybrary.aero/accidents-and-incidents/b744-en-route-east-china-sea-2011 title: SU95, manoeuvring near Jakarta Indonesia, 2012 link: https://skybrary.aero/accidents-and-incidents/su95-manoeuvring-near-jakarta-indonesia-2012 description:

On 9 May 2012, a Sukhoi RRJ-95 on a manufacturer-operated demonstration flight out of Jakarta Halim descended below the promulgated safe altitude and, after TAWS alerts and warnings had been ignored, impacted terrain in level flight which resulted in the destruction of the aeroplane and death of all 45 occupants. The Investigation concluded that that the operating crew were unaware that their descent would take them below some of the terrain in the area until the alerts started and then assumed they had been triggered by an incorrect database and switched the equipment off.

guid: https://skybrary.aero/accidents-and-incidents/su95-manoeuvring-near-jakarta-indonesia-2012 uri: https://skybrary.aero/accidents-and-incidents/su95-manoeuvring-near-jakarta-indonesia-2012 title: A388/A320, vicinity Frankfurt Germany, 2011 link: https://skybrary.aero/accidents-and-incidents/a388a320-vicinity-frankfurt-germany-2011 description:

On 13 December 2011, an Airbus 320 was allowed to depart from runway 25C at Frankfurt on a left turning SID just prior to the touchdown of an A380 on runway 25L. The A380 had then initiated a low go around which put it above, ahead of and parallel to the A320 with a closest proximity of 1nm / 200 ft, in breach of the applicable wake vortex separation minima of 7nm / 1000ft. The Investigation found that there had been no actual encounter with the A380 wake vortices but that systemic ATC operational risk management was inadequate.

guid: https://skybrary.aero/accidents-and-incidents/a388a320-vicinity-frankfurt-germany-2011 uri: https://skybrary.aero/accidents-and-incidents/a388a320-vicinity-frankfurt-germany-2011 title: B738, en-route, south east of Marseilles France, 2011 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-east-marseilles-france-2011 description:

On 6 July 2011 the First Officer of a Ryanair Boeing 737-800 was suddenly incapacitated during a passenger flight from Pisa to Las Palmas. The Captain declared a medical emergency and identified the First Officer as the affected person before diverting uneventfully to Girona. The subsequent investigation focused particularly on the way the event was perceived as a specifically medical emergency rather than also being an operational emergency as well as on the operator procedures for the situation encountered.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-east-marseilles-france-2011 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-east-marseilles-france-2011 title: B773, en-route, Bay of Bengal, 2011 link: https://skybrary.aero/accidents-and-incidents/b773-en-route-bay-bengal-2011 description:

On 18 October 2011, an Etihad Boeing 777-300 encountered severe turbulence westbound over the Bay of Bengal because of a late track deviation whilst the aircraft commander was briefly absent from the flight deck. Two occupants, one a member of the cabin crew and the other a passenger, sustained severe injuries and 12 other occupants sustained minor injuries. The subsequent Investigation noted that the severe weather encountered was evident well in advance and could have been avoided. The low level of experience in role and on aircraft type of the operating crew was noted.

guid: https://skybrary.aero/accidents-and-incidents/b773-en-route-bay-bengal-2011 uri: https://skybrary.aero/accidents-and-incidents/b773-en-route-bay-bengal-2011 title: B763, Melbourne Australia, 2006 link: https://skybrary.aero/accidents-and-incidents/b763-melbourne-australia-2006 description:

On 3 August 2006, a Qantas Boeing 767-300 encountered a large flock of birds during rotation and sustained multiple strikes on many parts of the aircraft. Left engine vibration immediately increased but as reducing thrust also reduced the vibration, it was decided following consultation with maintenance to continue to the planned destination, Sydney.

guid: https://skybrary.aero/accidents-and-incidents/b763-melbourne-australia-2006 uri: https://skybrary.aero/accidents-and-incidents/b763-melbourne-australia-2006 title: B738/A321, Prague Czech Republic, 2010 link: https://skybrary.aero/accidents-and-incidents/b738a321-prague-czech-republic-2010 description:

On 18 June 2010 a Sun Express Boeing 737-800 taxiing for a full length daylight departure from runway 06 at Prague was in collision with an Airbus 321 which was waiting on a link taxiway leading to an intermediate take off position on the same runway. The aircraft sustained damage to their right winglet and left horizontal stabiliser respectively and both needed subsequent repair before being released to service.

guid: https://skybrary.aero/accidents-and-incidents/b738a321-prague-czech-republic-2010 uri: https://skybrary.aero/accidents-and-incidents/b738a321-prague-czech-republic-2010 title: B737/LJ45, Chicago Midway, USA 2011 link: https://skybrary.aero/accidents-and-incidents/b737lj45-chicago-midway-usa-2011 description:

On 1 December 2011 a Southwest Boeing 737-700 was cleared to taxi in after landing on a route which included crossing another active runway before contacting GND and the controller who had issued that clearance then inadvertently issued a take off clearance to a Gama Charters Learjet 45 for the runway to be crossed. One of the 737 pilots saw the approaching Learjet and warned the PF to stop as the runway crossing was about to begin. The departing aircraft then overflew the stationary 737 by 62 feet after rotating shortly before the crossing point without seeing it.

guid: https://skybrary.aero/accidents-and-incidents/b737lj45-chicago-midway-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/b737lj45-chicago-midway-usa-2011 title: SW4 / Vehicle, Dunedin New Zealand, 2010 link: https://skybrary.aero/accidents-and-incidents/sw4-vehicle-dunedin-new-zealand-2010 description:

On 25 May 2010 an Airwork SA227 Metroliner operating a cargo flight narrowly missed colliding with a vehicle on the runway during its night landing at Dunedin in normal visibility. The vehicle was subsequently found to have been on the runway without the appropriate authority in order to carry out a security inspection and the vehicle only co-incidentally at the side of the runway as its driver was unaware of the aircraft. It was noted such access had become a matter of custom and practice for which the context was inadequate procedures for control of airside vehicular access.

guid: https://skybrary.aero/accidents-and-incidents/sw4-vehicle-dunedin-new-zealand-2010 uri: https://skybrary.aero/accidents-and-incidents/sw4-vehicle-dunedin-new-zealand-2010 title: A332, Abu Dhabi UAE, 2012 link: https://skybrary.aero/accidents-and-incidents/a332-abu-dhabi-uae-2012 description:

On 30 January 2012, an Airbus A330 departing Abu Dhabi at night lined up on the runway edge lights in the prevailing low visibility and attempted to take off. The take off was eventually rejected and the aircraft towed away from the runway. Damage was limited to that resulting from the impact of the aircraft landing gear with runway edge lights and the resultant debris. An Investigation is continuing into the circumstances and causation of the incident.

guid: https://skybrary.aero/accidents-and-incidents/a332-abu-dhabi-uae-2012 uri: https://skybrary.aero/accidents-and-incidents/a332-abu-dhabi-uae-2012 title: CRJ7, Kanpur India, 2011 link: https://skybrary.aero/accidents-and-incidents/crj7-kanpur-india-2011 description:

On 20 July 2011, an Alliance Air CRJ 700 touched down over half way along the 9000 ft long runway at Kanpur after a stable ILS approach but with an unexpected limiting tailwind component and failed to stop before the end of the paved surface. Although an emergency evacuation was not necessary and there were no injuries, the aircraft was slightly damaged by impact with an obstruction. The subsequent investigation attributed the event to the commanders continued attempt at a landing when a late touchdown became increasingly likely.

guid: https://skybrary.aero/accidents-and-incidents/crj7-kanpur-india-2011 uri: https://skybrary.aero/accidents-and-incidents/crj7-kanpur-india-2011 title: A320/B773, Dubai UAE, 2012 link: https://skybrary.aero/accidents-and-incidents/a320b773-dubai-uae-2012 description:

On March 20 2012 an Airbus A320 failed to taxi as instructed after vacating the landing runway 12L at Dubai and crossed the lit stop bar of an intersection access to runway 12R before stopping just in time to prevent a collision with a Boeing 777-300ER about to pass the intersection at very high speed on take off. Taxi clearance had been correctly given and acknowledged. The aircraft commander had extensive aircraft type experience but the inexperienced First Officer appeared to be undergoing early stage line training with a Safety Pilot present. No Final Report of the Investigation has been released and its status is unclear.

guid: https://skybrary.aero/accidents-and-incidents/a320b773-dubai-uae-2012 uri: https://skybrary.aero/accidents-and-incidents/a320b773-dubai-uae-2012 title: A320, Cochin India, 2011 link: https://skybrary.aero/accidents-and-incidents/a320-cochin-india-2011 description:

On 29 August 2011, an Airbus A320 which had up to that point made a stabilised auto ILS approach at destination deviated from the runway centreline below 200 feet aal but continued to a night touchdown which occurred on the edge of the 3400 metre runway and was followed by exit from the side onto soft ground before eventually coming to a stop adjacent to the runway about a third of the way along it. The subsequent investigation attributed the event to poor crew performance in reduced visibility

guid: https://skybrary.aero/accidents-and-incidents/a320-cochin-india-2011 uri: https://skybrary.aero/accidents-and-incidents/a320-cochin-india-2011 title: A343, London Heathrow, UK 2012 link: https://skybrary.aero/accidents-and-incidents/a343-london-heathrow-uk-2012 description:

On 5 February 2012, an Airbus A340-300 started its takeoff from an intermediate point on the runway for which no regulated takeoff weight information was available and had only become airborne very close to the end of the runway and then climbed only very slowly. The Investigation found that as the full length of the planned departure runway was not temporarily unavailable, ATC had offered either the intersection subsequently used or the full length of the available parallel runway and that despite the absence of valid performance data for the intersection, the intersection had been used.

guid: https://skybrary.aero/accidents-and-incidents/a343-london-heathrow-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/a343-london-heathrow-uk-2012 title: B732, vicinity Washington National DC USA, 1982 link: https://skybrary.aero/accidents-and-incidents/b732-vicinity-washington-national-dc-usa-1982 description:

On 13 January 1982, an Air Florida Boeing 737-200 took off in daylight from runway 36 at Washington National in moderate snow but then stalled before hitting a bridge and vehicles and continuing into the river below after just one minute of flight killing most of the occupants and some people on the ground. The accident was attributed entirely to a combination of the actions and inactions of the crew in relation to the prevailing adverse weather conditions and, crucially, to the failure to select engine anti ice on which led to over reading of actual engine thrust.

guid: https://skybrary.aero/accidents-and-incidents/b732-vicinity-washington-national-dc-usa-1982 uri: https://skybrary.aero/accidents-and-incidents/b732-vicinity-washington-national-dc-usa-1982 title: SH36, vicinity Edinburgh UK, 2001 link: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-edinburgh-uk-2001 description:

On 27 February 2001, a Loganair SD3-60 lost all power on both engines soon after take off from Edinburgh. An attempt to ditch in the Firth or Forth in rough seas resulted in the break up and sinking of the aircraft and neither pilot survived. The loss of power was attributed to the release of previously accumulated frozen deposits into the engine core when the engine anti icing systems were selected on whilst climbing through 2200 feet. These frozen deposits were considered to have accumulated whilst the aircraft had been parked prior to flight without engine intake blanks fitted.

guid: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-edinburgh-uk-2001 uri: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-edinburgh-uk-2001 title: RJ1H, vicinity Zurich Switzerland, 2011 link: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-zurich-switzerland-2011 description:

On 20 July 2011, the flight crew of a Swiss European Avro RJ-100 on a positioning flight from Nuremburg to Zurich responded inappropriately to an unexpected ‘bank angle’ alert in IMC. Near loss of control followed during which a PAN was eventually declared. The situation was resolved by a belated actioning of the QRH checklist applicable to the failure symptoms experienced. The subsequent investigation attributed the event to inappropriate crew response to a failure of a single IRU and poor manual flying skill whilst the situation was resolved.

guid: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-zurich-switzerland-2011 uri: https://skybrary.aero/accidents-and-incidents/rj1h-vicinity-zurich-switzerland-2011 title: D328, Norwich UK, 2012 link: https://skybrary.aero/accidents-and-incidents/d328-norwich-uk-2012 description:

On 22 March 2012, a Scot Airways Dornier 328 left the side of the runway shortly after touchdown following an unstable visual sequel to a non precision approach at Norwich and then carried out a go around without further event. The aircraft was undamaged by the excursion but a runway edge light was broken. The subsequent Investigation noted the gross violation of Operator SOPs in respect of the way the initial approach had been conducted, the absence of necessary crew procedures following a serious incident and the absence of any OFDM programme.

guid: https://skybrary.aero/accidents-and-incidents/d328-norwich-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/d328-norwich-uk-2012 title: CRJ2, Menorca Spain, 2011 link: https://skybrary.aero/accidents-and-incidents/crj2-menorca-spain-2011 description:

On 9 April 2011, an Air Nostrum Bombardier CRJ 200 landed at Menorca in daylight and good visibility on closed runway 01L which was parallel to 01R, the one for which landing clearance had been given. The explanation given by the pilot was that the wrong runway had been programmed into the FMS. The subsequent investigation found that all aspects of the notification and implementation of the runway closure had been in order and that crew error was the only cause.

guid: https://skybrary.aero/accidents-and-incidents/crj2-menorca-spain-2011 uri: https://skybrary.aero/accidents-and-incidents/crj2-menorca-spain-2011 title: A124, Zaragoza Spain, 2010 link: https://skybrary.aero/accidents-and-incidents/a124-zaragoza-spain-2010 description:

On 20 April 2010, the left wing of an Antonov Design Bureau An124-100 which was taxiing in to park after a night landing at Zaragoza under marshalling guidance was in collision with two successive lighting towers on the apron. Both towers and the left wingtip of the aircraft were damaged. The subsequent investigation attributed the collision to allocation of an unsuitable stand and lack of appropriate guidance markings.

guid: https://skybrary.aero/accidents-and-incidents/a124-zaragoza-spain-2010 uri: https://skybrary.aero/accidents-and-incidents/a124-zaragoza-spain-2010 title: GLF6, Roswell NM USA, 2011 link: https://skybrary.aero/accidents-and-incidents/glf6-roswell-nm-usa-2011 description:

On 2 April 2011, the crew of a Gulfstream G650 undertaking a pre-type certification experimental test flight take off with one engine intentionally inoperative were unable to recover controlled flight after a wing drop occurred during take off. The aeroplane impacted the ground without becoming properly airborne and was destroyed by a combination of the impact and a post crash fire with fatal injuries to all four occupants. The subsequent Investigation found that preparation for the flight had been inadequate and had failed to incorporate effective response to previous similar incidents where recovery had been successful.

guid: https://skybrary.aero/accidents-and-incidents/glf6-roswell-nm-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/glf6-roswell-nm-usa-2011 title: SH36, vicinity Oshawa ON Canada, 2004 link: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-oshawa-canada-2004 description:

On 16 December 2004, an Air Cargo Carriers Shorts SD3-60 attempted to land at Oshawa at night on a runway covered with 12.5mm of wet snow which did not offer the required landing distance. After unexpectedly poor deceleration despite selection of reverse propeller pitch, full power was applied and actions for a go around were taken. Although the aircraft then became airborne in ground effect, it subsequently failed to achieve sufficient airspeed to sustain a climb and an aerodynamic stall was followed by impact with terrain and trees beyond the end of the runway. The aircraft was substantially damaged and both pilots sustained serious injuries but there was no post-crash fire

guid: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-oshawa-canada-2004 uri: https://skybrary.aero/accidents-and-incidents/sh36-vicinity-oshawa-canada-2004 title: DH8C / Vehicle, Tamworth SE Australia, 2008 link: https://skybrary.aero/accidents-and-incidents/dh8c-vehicle-tamworth-se-australia-2008 description:

On 7 February 2008, an ATC TWR at Tamworth cleared an Eastern Australia Bombardier DHC8-300 for take off having already cleared a bird scaring vehicle onto the same runway. The vehicle was still on the runway at the time of the take off clearance and as the flight crew could see the vehicle, they did not commence take off. The vehicle driver reported having been monitoring the TWR frequency and vacated the runway. The subsequent Investigation noted a record of good competency assessments for the controller involved and found no specific explanation for his lapse.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-vehicle-tamworth-se-australia-2008 uri: https://skybrary.aero/accidents-and-incidents/dh8c-vehicle-tamworth-se-australia-2008 title: B734, Palembang Indonesia, 2008 link: https://skybrary.aero/accidents-and-incidents/b734-palembang-indonesia-2008 description:

On 2 October 2008, a Boeing 737-400 being used for flight crew command upgrade line training unintentionally landed off a non precision approach at Palembang in daylight on a taxiway parallel to the landing runway. Neither pilot realised their error until the aircraft was already on the ground when they saw a barrier ahead and were able to brake hard to stop only 700 metres from touchdown. It was found that the taxiway involved had served as a temporary runway five years earlier and that previously obliterated markings from that use had become visible.

guid: https://skybrary.aero/accidents-and-incidents/b734-palembang-indonesia-2008 uri: https://skybrary.aero/accidents-and-incidents/b734-palembang-indonesia-2008 title: B763/DH8D, Fukuoka Japan, 2010 link: https://skybrary.aero/accidents-and-incidents/b763dh8d-fukuoka-japan-2010 description:

On 10 May 2010, the TWR controller at Fukuoka cleared a Bombardier DHC8-400 to land on runway 16 and then a minute later whilst it was still on approach cleared a Boeing 767-300 to line up and take off on the same runway. Only a query from approaching aircraft which had been cleared to land prompted by hearing a take off clearance being given for the same runway alerted ATC to the simultaneous runway use clearances. As it was too late to stop the departing aircraft at the holding point, its clearance was changed to line up and wait and the approaching aircraft was instructed to go around.

guid: https://skybrary.aero/accidents-and-incidents/b763dh8d-fukuoka-japan-2010 uri: https://skybrary.aero/accidents-and-incidents/b763dh8d-fukuoka-japan-2010 title: Vehicle / PAY4, Perth Western Australia, 2012 link: https://skybrary.aero/accidents-and-incidents/vehicle-pay4-perth-western-australia-2012 description:

Whilst a light aircraft was lined up for departure, a vehicle made an incorrect assumption about the nature of an ambiguously-phrased ATC TWR instruction and proceeded to enter the same runway. There was no actual risk of conflict since, although LVP were still in force after earlier fog, the TWR controller was able to see the vehicle incursion and therefore withhold the imminent take off clearance. The subsequent Investigation noted that it was imperative that clearance read backs about which there is doubt are not made speculatively in the expectation that they will elicit confirmation or correction.

guid: https://skybrary.aero/accidents-and-incidents/vehicle-pay4-perth-western-australia-2012 uri: https://skybrary.aero/accidents-and-incidents/vehicle-pay4-perth-western-australia-2012 title: B788, Boston MA USA, 2013 link: https://skybrary.aero/accidents-and-incidents/b788-boston-ma-usa-2013 description:

On 7 January 2013, a battery fire on a Japan Air Lines Boeing 787-8 began almost immediately after passengers and crew had left the aircraft after its arrival at Boston on a scheduled passenger flight from Tokyo Narita. The primary structure of the aircraft was undamaged. Investigation found that an internal short circuit within a cell of the APU lithium-ion battery had led to uncontained thermal runaway in the battery leading to the release of smoke and fire. The origin of the malfunction was attributed to system design deficiency and the failure of the type certification process to detect this.

guid: https://skybrary.aero/accidents-and-incidents/b788-boston-ma-usa-2013 uri: https://skybrary.aero/accidents-and-incidents/b788-boston-ma-usa-2013 title: D328, Mannheim Germany, 2008 link: https://skybrary.aero/accidents-and-incidents/d328-mannheim-germany-2008 description:

On 19 March 2008, a Cirrus AL Dornier 328 overran runway 27 at Mannheim after a late touchdown, change of controlling pilot in the flare and continued failure to control the aircraft so as to safely complete a landing. The Investigation attributed the late touchdown and subsequent overrun to an initial failure to reject the landing when the TDZ was overflown and the subsequent failure to control the engines properly. The extent of damage to the aircraft was attributed to the inadequate RESA and extensive contextual safety deficiencies were identified in respect of both the aircraft and airport operators.

guid: https://skybrary.aero/accidents-and-incidents/d328-mannheim-germany-2008 uri: https://skybrary.aero/accidents-and-incidents/d328-mannheim-germany-2008 title: Vehicle / PA31, Mackay SE Australia, 2008 link: https://skybrary.aero/accidents-and-incidents/vehicle-pa31-mackay-se-australia-2008 description:

On 29 June 2012, a Piper PA31 taking off from runway 05 on a passenger charter flight just missed hitting an inspection vehicle which had entered the take off runway from an intersecting one contrary to ATC clearance. The overflying aircraft was estimated to have cleared the vehicle by approximately 20 feet and the pilot was unaware it had entered the active runway. The driver had been taking a mobile telephone call at the time and attributed the incursion to distraction. The breached clearance had been given and correctly read back approximately two minutes prior to the conflict occurring.

guid: https://skybrary.aero/accidents-and-incidents/vehicle-pa31-mackay-se-australia-2008 uri: https://skybrary.aero/accidents-and-incidents/vehicle-pa31-mackay-se-australia-2008 title: B738, Nuremburg Germany, 2010 link: https://skybrary.aero/accidents-and-incidents/b738-nuremburg-germany-2010 description:

On 8 January 2010, an Air Berlin Boeing 737-800 attempted to commence a rolling take off at Nuremburg on a runway pre-advised as having only medium braking action. Whilst attempting to position the aircraft on the runway centreline, directional control was lost and the aircraft exited the paved surface onto soft ground at low speed before the flight crew were able to stop it. The event was attributed to the inappropriately high taxi speed onto the runway and subsequent attempt to conduct a rolling take off. Relevant Company standard operating procedures were found to be deficient.

guid: https://skybrary.aero/accidents-and-incidents/b738-nuremburg-germany-2010 uri: https://skybrary.aero/accidents-and-incidents/b738-nuremburg-germany-2010 title: A319, Luton UK, 2012 link: https://skybrary.aero/accidents-and-incidents/a319-luton-uk-2012 description:

On 14 February 2011, an Easyjet Airbus A319 being flown by a trainee Captain under supervision initiated a go around from below 50 feet agl after a previously stabilised approach at Luton and a very hard three point landing followed before the go around climb could be established. The investigation found that the Training Captain involved, although experienced, had only limited aircraft type experience and that, had he taken control before making a corrective sidestick input opposite to that of the trainee, it would have had the full instead of a summed effect and may have prevented hard runway contact.

guid: https://skybrary.aero/accidents-and-incidents/a319-luton-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/a319-luton-uk-2012 title: RJ85, en-route, north of Tampere Finland 2009 link: https://skybrary.aero/accidents-and-incidents/rj85-en-route-north-tampere-finland-2009 description:

On 17 December 2009, a Blue 1 Avro RJ85 experienced progressive fuel starvation during continued flight after the crew had failed to carry out the QRH drill for an abnormal fuel system indication caused by fuel icing. Although hindsight was able to confirm that complete fuel starvation had not been likely, a failure to recognise the risk to fuel system function arising from routine operations in very cold conditions was identified by the subsequent investigation.

guid: https://skybrary.aero/accidents-and-incidents/rj85-en-route-north-tampere-finland-2009 uri: https://skybrary.aero/accidents-and-incidents/rj85-en-route-north-tampere-finland-2009 title: B738, vicinity Memmingen Germany, 2012 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-memmingen-germany-2012 description:

On 23 September 2012 a Ryanair Boeing 737-800 made a premature descent to 450 feet agl in day VMC whilst turning right onto visual finals for runway 24 at Memmingen after the FMS selected altitude had been set to a figure only 44 feet above runway threshold elevation of 2052 feet amsl. EGPWS Alerts of Sink Rate and Caution Terrain prompted initiation of a go around which, as it was initiated, was accompanied by a an EGPWS TERRAIN PULL UP warning. The go around and a second successful approach to runway 24 were uneventful. The Investigation is not yet complete.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-memmingen-germany-2012 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-memmingen-germany-2012 title: PRM1, vicinity Samedan Switzerland, 2010 link: https://skybrary.aero/accidents-and-incidents/prm1-vicinity-samedan-switzerland-2010 description:

On 19 December 2010, a Raytheon 390 inbound to Samedan from Zagreb made a daylight approach to runway 21 at destination in marginal VMC which involved a steep and unstable descent from which a landing was not possible. The subsequent go around was followed by entry to a visual right hand circuit which was contrary to local procedures due to terrain constraints. Overbanking in the turn towards final approach was followed by a stall and loss of control which led to ground impact which, with the post crash fire, destroyed the aeroplane and fatally injured both occupants.

guid: https://skybrary.aero/accidents-and-incidents/prm1-vicinity-samedan-switzerland-2010 uri: https://skybrary.aero/accidents-and-incidents/prm1-vicinity-samedan-switzerland-2010 title: A332, vicinity Tripoli Libya, 2010 link: https://skybrary.aero/accidents-and-incidents/a332-vicinity-tripoli-libya-2010 description:

On 12 May 2010, an Afriqiyah Airways Airbus A330 making a daylight go around from a non precision approach at Tripoli which had been discontinued after visual reference was not obtained at MDA did not sustain the initially established IMC climb and, following flight crew control inputs attributed to the effects of somatogravic illusion and poor CRM, descended rapidly into the ground with a high vertical and forward speed, The aircraft was destroyed by impact forces and the consequent fire and all but one of the 104 occupants were killed.

guid: https://skybrary.aero/accidents-and-incidents/a332-vicinity-tripoli-libya-2010 uri: https://skybrary.aero/accidents-and-incidents/a332-vicinity-tripoli-libya-2010 title: B737 / A320, Los Angeles CA USA, 2007 link: https://skybrary.aero/accidents-and-incidents/b737-a320-los-angeles-ca-usa-2007 description:

On 16 August 2007, a Westjet Boeing 737-700 which had just landed began to cross a runway in normal daylight visibility from which an Airbus A320 was taking off because the crew had received a clearance to do so after an ambiguous position report given following a non-instructed frequency change. When the other aircraft was seen, the 737 was stopped partly on the runway and the A320 passed close by at high speed with an 11 metre clearance. The AMASS activated, but not until it was too late to inform a useful controller response.

guid: https://skybrary.aero/accidents-and-incidents/b737-a320-los-angeles-ca-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/b737-a320-los-angeles-ca-usa-2007 title: B735/B733, Dallas-Fort Worth TX USA, 2001 link: https://skybrary.aero/accidents-and-incidents/b735b733-dallas-fort-worth-tx-usa-2001 description:

On 16 August 2001, a Continental Boeing 737-500 which had just landed on runway 18R at Dallas-Fort-Worth crossed runway 18L in daylight in front of a Delta Boeing 737-300 which had originally been believed to be holding position but was then seen to be taking off from the same runway. The Delta aircraft rotated early and sharply to overfly the crossing aircraft and suffered a tail strike in doing so. Clearance was estimated to have been about 100 feet. Both aircraft were being operated in accordance with valid ATC clearances issued by the same controller.

guid: https://skybrary.aero/accidents-and-incidents/b735b733-dallas-fort-worth-tx-usa-2001 uri: https://skybrary.aero/accidents-and-incidents/b735b733-dallas-fort-worth-tx-usa-2001 title: A320/B734, vicinity London Gatwick UK, 2012 link: https://skybrary.aero/accidents-and-incidents/a320b734-vicinity-london-gatwick-uk-2012 description:

On 4 August 2012 an Easyjet Airbus A320 on approach to London Gatwick was given landing clearance in IMC for a runway occupied by a Boeing 737-400 waiting for take off which heard this transmission. Despite normal ground visibility and an unrestricted view of the runway, ATC failed to recognise their error and, after two unsuccessful attempts to advise them of it, the commander of the 737 instructed the A320 to go around which it did. Only upon hearing this did the controller realise what had happened.

guid: https://skybrary.aero/accidents-and-incidents/a320b734-vicinity-london-gatwick-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/a320b734-vicinity-london-gatwick-uk-2012 title: SF34/SF34, vicinity Stornoway UK, 2011 link: https://skybrary.aero/accidents-and-incidents/sf34sf34-vicinity-stornoway-uk-2011 description:

On 15 October 2011, a Loganair Saab 340 in uncontrolled airspace and inbound and level at 2000 feet QNH on a procedural non precision approach in day IMC to runway 18 at Stornoway received a TCAS RA ‘DESCEND’ when a second Loganair Saab 340 outbound on the same procedure descended prematurely to the same altitude contrary to ATC clearance. The subsequent investigation concluded that the failure of the controller to re-iterate the requirement to remain at 3000 feet outbound until advised had contributed the crew error. Minimum separation after the TCAS RA was less than 0.1nm horizontally when 500 feet vertically.

guid: https://skybrary.aero/accidents-and-incidents/sf34sf34-vicinity-stornoway-uk-2011 uri: https://skybrary.aero/accidents-and-incidents/sf34sf34-vicinity-stornoway-uk-2011 title: A319/B733, en-route, near Moutiers France, 2010 link: https://skybrary.aero/accidents-and-incidents/a319b733-en-route-near-moutiers-france-2010 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a319b733-en-route-near-moutiers-france-2010 uri: https://skybrary.aero/accidents-and-incidents/a319b733-en-route-near-moutiers-france-2010 title: A320 / A320, Zurich Switzerland, 2011 link: https://skybrary.aero/accidents-and-incidents/a320-a320-zurich-switzerland-2011 description:

On 15 March 2011 two Swiss International Airlines’ Airbus A320 aircraft were cleared for simultaneous take off on intersecting runways at Zurich by the same controller. As both approached the intersection at high speed, the Captain of one saw the other and immediately rejected take off from 130 knots, stopping just at the edge of the intersection shortly after the other aircraft had flown low overhead unaware of the conflict. The Investigation noted a long history of similar incidents at Zurich and concluded that systemic failure of risk management had not been addressed by the air traffic control agency involved.

guid: https://skybrary.aero/accidents-and-incidents/a320-a320-zurich-switzerland-2011 uri: https://skybrary.aero/accidents-and-incidents/a320-a320-zurich-switzerland-2011 title: AT72, vicinity Stockholm Bromma Sweden, 2010 link: https://skybrary.aero/accidents-and-incidents/at72-vicinity-stockholm-bromma-sweden-2010 description:

On 21 August 2010 a Golden Air Flyg ATR 72 under ATC control in Class C airspace was vectored close to three parachutists who had been dropped from a helicopter as part of an air show because of confusion between the ATC unit with responsibility for the incident airspace and the adjacent unit to which that responsibility had been delegated because it was nearest to the air show site. Additional confusion was caused by poor R/T practice by both ATC units and by different portrayal of a holding pattern on charts held by ATC and he flight crew.

guid: https://skybrary.aero/accidents-and-incidents/at72-vicinity-stockholm-bromma-sweden-2010 uri: https://skybrary.aero/accidents-and-incidents/at72-vicinity-stockholm-bromma-sweden-2010 title: B743, vicinity Jeddah Saudia Arabia, 2008 link: https://skybrary.aero/accidents-and-incidents/b743-vicinity-jeddah-saudia-arabia-2008 description:

On 5 May 2008, a Saudi Arabian Boeing 747-300 being positioned for maintenance to include investigation of degraded power output from the no 1 GE CF6-50 engine experienced an uncontained failure of the same engine shortly after take off from Jeddah followed by an uneventful air turn back. The failure was attributed to the vulnerability of the engine design to high pressure turbine blade loss.

guid: https://skybrary.aero/accidents-and-incidents/b743-vicinity-jeddah-saudia-arabia-2008 uri: https://skybrary.aero/accidents-and-incidents/b743-vicinity-jeddah-saudia-arabia-2008 title: B722, Lagos Nigeria, 2006 link: https://skybrary.aero/accidents-and-incidents/b722-lagos-nigeria-2006 description:

On 7 September 2006, a DHL Boeing 727-200 overran the runway at Lagos by 400 metres after the First Officer was permitted to attempt a landing in challenging weather conditions on a wet runway off an unstable ILS approach. Following a long and fast touchdown at maximum landing weight, a go around was then called after prior selection of thrust reversers but was not actioned and a 400 metre overrun onto soft wet ground followed. The accident was attributed to poor tactical decision making by the aircraft commander.

guid: https://skybrary.aero/accidents-and-incidents/b722-lagos-nigeria-2006 uri: https://skybrary.aero/accidents-and-incidents/b722-lagos-nigeria-2006 title: E145/E135, Chicago O’Hare USA, 2011 link: https://skybrary.aero/accidents-and-incidents/e145e135-chicago-ohare-usa-2011 description:

On 8 August 2011, an Embraer 145 was given take off clearance from runway 32L at O Hare in day VMC without the controller making the required check for potentially conflicting arrivals to runway 09R which pass over the runway. When the controller realised that the departing aircraft would conflict with an Embraer 135 approaching 09R, he told his aircraft to stay low and the runway 09R controller to send his aircraft around. Radar data indicated that the 135 on go around had crossed runway 32L about 125 feet above and just over 100 metres in front of the departing 145.

guid: https://skybrary.aero/accidents-and-incidents/e145e135-chicago-ohare-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/e145e135-chicago-ohare-usa-2011 title: BE20/SF34, vicinity Stornoway UK, 2011 link: https://skybrary.aero/accidents-and-incidents/be20sf34-vicinity-stornoway-uk-2011 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/be20sf34-vicinity-stornoway-uk-2011 uri: https://skybrary.aero/accidents-and-incidents/be20sf34-vicinity-stornoway-uk-2011 title: B752/GLID, vicinity Glasgow UK, 2011 link: https://skybrary.aero/accidents-and-incidents/b752glid-vicinity-glasgow-uk-2011 description:

On 23 July 2011 a Boeing 757 in Class E airspace east of Glasgow in VMC encountered a glider ahead at the same altitude and deviated right to avoid a collision. The glider, climbing in a thermal, had not seen the 757 until it passed during avoiding action. The closest proximity was estimated as 100 metres at the same level as the glider passed to the left of the 757 in the opposite direction. Since the circumstances were considered to have demonstrated a safety critical risk by the UK CAA, an interim airspace reclassification Class D was implemented

guid: https://skybrary.aero/accidents-and-incidents/b752glid-vicinity-glasgow-uk-2011 uri: https://skybrary.aero/accidents-and-incidents/b752glid-vicinity-glasgow-uk-2011 title: B744, Bagram Afghanistan, 2013 link: https://skybrary.aero/accidents-and-incidents/b744-bagram-afghanistan-2013 description:

On 29 April 2013, a Boeing 747-400 freighter departed controlled flight and impacted terrain shortly after taking off from Bagram and was destroyed by the impact and post crash fire and all occupants were killed. The Investigation found that a sudden and significant load shift had occurred soon after take off which damaged hydraulic systems Nos. 1 and 2 and the horizontal stabilizer drive mechanism components as well as moving the centre of gravity aft and out of the allowable flight envelope. The Load shift was attributed to the ineffective securing techniques employed.

guid: https://skybrary.aero/accidents-and-incidents/b744-bagram-afghanistan-2013 uri: https://skybrary.aero/accidents-and-incidents/b744-bagram-afghanistan-2013 title: B738, vicinity Denpasar Bali Indonesia, 2013 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-denpasar-bali-indonesia-2013 description:

On 13 April 2013, a Lion Air Boeing 737-800 flew a day non precision approach to runway 09 at Bali (Denpasar) and continued when the required visual reference was lost below MDA. Despite continued absence of visual reference, the approach was continued until the EGPWS annunciation 'TWENTY', when the aircraft commander called a go around. Almost immediately, the aircraft hit the sea surface to the right of the undershoot area and broke up. All 108 occupants were rescued with only four sustaining serious injury. The Investigation attributed the accident entirely to the actions and inactions of the two pilots.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-denpasar-bali-indonesia-2013 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-denpasar-bali-indonesia-2013 title: A319, London Heathrow UK, 2013 link: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2013 description:

On 24 May 2013 the fan cowl doors on both engines of an Airbus A319 detached as it took off from London Heathrow. Their un-latched status after a routine maintenance input had gone undetected. Extensive structural and system damage resulted and a fire which could not be extinguished until the aircraft was back on the ground began in one engine. Many previously-recorded cases of fan cowl door loss were noted but none involving such significant collateral damage. Safety Recommendations were made on aircraft type certification in general, A320-family aircraft modification, maintenance fatigue risk management and aircrew procedures and training.

guid: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2013 uri: https://skybrary.aero/accidents-and-incidents/a319-london-heathrow-uk-2013 title: A310, Khartoum Sudan, 2008 link: https://skybrary.aero/accidents-and-incidents/a310-khartoum-sudan-2008 description:

On 10 June 2008, a Sudan Airways Airbus A310 made a late night touchdown at Khartoum and the actions of the experienced crew were subsequently unable to stop the aircraft, which was in service with one thrust reverser inoperative and locked out, on the wet runway. The aircraft stopped essentially intact some 215 metres beyond the runway end after overrunning on smooth ground but a fuel-fed fire then took hold which impeded evacuation and eventually destroyed the aircraft.

guid: https://skybrary.aero/accidents-and-incidents/a310-khartoum-sudan-2008 uri: https://skybrary.aero/accidents-and-incidents/a310-khartoum-sudan-2008 title: A306, Stockholm Sweden, 2010 link: https://skybrary.aero/accidents-and-incidents/a306-stockholm-sweden-2010 description:

On 16 January 2010, an Iran Air Airbus A300-600 veered off the left side of the runway after a left engine failure at low speed whilst taking off at Stockholm. The directional control difficulty was attributed partly to the lack of differential braking but also disclosed wider issues about directional control following sudden asymmetry at low speeds. The Investigation concluded that deficiencies in the type certification process had contributed to the loss of directional control. It was concluded that the engine malfunction was due to the initiation of an engine stall by damage caused by debris from a deficient repair.

guid: https://skybrary.aero/accidents-and-incidents/a306-stockholm-sweden-2010 uri: https://skybrary.aero/accidents-and-incidents/a306-stockholm-sweden-2010 title: B734, vicinity Lyon France, 2010 link: https://skybrary.aero/accidents-and-incidents/b734-vicinity-lyon-france-2010 description:

On 7 September 2010, a Turkish operated Boeing 737-400 flew a non precision approach at Lyon Saint-Exupéry in IMC significantly below the procedure vertical profile throughout and only made a go around when instructed to do so by ATC following an MSAW activation. The minimum recorded radio height was 250 feet at 1.4nm from the runway threshold.

guid: https://skybrary.aero/accidents-and-incidents/b734-vicinity-lyon-france-2010 uri: https://skybrary.aero/accidents-and-incidents/b734-vicinity-lyon-france-2010 title: AT72, Shannon Ireland, 2011 link: https://skybrary.aero/accidents-and-incidents/at72-shannon-ireland-2011 description:

On 17 July 2011, an Aer Arann ATR 72-200 made a bounced daylight landing at Shannon in gusty crosswind conditions aggravated by the known effects of a nearby large building. The nose landing gear struck the runway at 2.3g and collapsed with subsequent loss of directional control and departure from the runway. The aircraft was rendered a hull loss but there was no injury to the 25 occupants. The accident was attributed to an excessive approach speed and inadequate control of aircraft pitch during landing. Crew inexperience and incorrect power handling technique whilst landing were also found to have contributed.

guid: https://skybrary.aero/accidents-and-incidents/at72-shannon-ireland-2011 uri: https://skybrary.aero/accidents-and-incidents/at72-shannon-ireland-2011 title: A320, en-route, north of Öland Sweden, 2011 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-oland-sweden-2011 description:

On 5 March 2011, a Finnair Airbus A320 was westbound in the cruise in southern Swedish airspace after despatch with Engine 1 bleed air system inoperative when the Engine 2 bleed air system failed and an emergency descent was necessary. The Investigation found that the Engine 2 system had shut down due to overheating and that access to proactive and reactive procedures related to operations with only a single bleed air system available were deficient. The crew failure to make use of APU air to help sustain cabin pressurisation during flight completion was noted.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-oland-sweden-2011 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-oland-sweden-2011 title: B732, vicinity Abuja Nigeria, 2006 link: https://skybrary.aero/accidents-and-incidents/b732-vicinity-abuja-nigeria-2006 description:

On 29 October 2006, an ADC Airlines Boeing 737-200 encountered wind shear almost immediately taking off from Abuja into adverse weather associated with a very rapidly developing convective storm. Unseen from the apron or ATC TWR it stalled, crashed and burned after just over one minute airborne killing 96 of the 105 occupants. The Investigation concluded that loss of control during the wind shear encounter was not inevitable but was a consequence of inappropriate crew response. Concerns about the quality of crew training and competency validation were also raised.

guid: https://skybrary.aero/accidents-and-incidents/b732-vicinity-abuja-nigeria-2006 uri: https://skybrary.aero/accidents-and-incidents/b732-vicinity-abuja-nigeria-2006 title: E145, en-route, north east of Madrid Spain, 2011 link: https://skybrary.aero/accidents-and-incidents/e145-en-route-north-east-madrid-spain-2011 description:

On 4 August 2011, a Luxair Embraer 145 flying a STAR into Madrid incorrectly read back a descent clearance to altitude 10,000 feet as being to 5,000 feet and the error was not detected by the controller. The aircraft was transferred to the next sector where the controller failed to notice that the incorrect clearance had been repeated. Shortly afterwards, the aircraft received a Hard EGPWS Pull Up Warning and responded to it with no injury to the 47 occupants during the manoeuvre. The Investigation noted that an MSAW system was installed in the ACC concerned but was not active.

guid: https://skybrary.aero/accidents-and-incidents/e145-en-route-north-east-madrid-spain-2011 uri: https://skybrary.aero/accidents-and-incidents/e145-en-route-north-east-madrid-spain-2011 title: B752 / B752, en-route, north of Tenerife Spain 2011 link: https://skybrary.aero/accidents-and-incidents/b752-b752-en-route-north-tenerife-spain-2011 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/b752-b752-en-route-north-tenerife-spain-2011 uri: https://skybrary.aero/accidents-and-incidents/b752-b752-en-route-north-tenerife-spain-2011 title: A319/A332, vicinity Barcelona Spain, 2012 link: https://skybrary.aero/accidents-and-incidents/a319a332-vicinity-barcelona-spain-2012 description:

On 8 February 2012, a TCAS RA occurred between an Airbus A330 and an Airbus A319 both under ATC control for landing on runway 25R at Barcelona as a result of an inappropriate plan to change the sequence. The opposite direction aircraft both followed their respective RAs and minimum separation was 1.4 nm horizontally and 400 feet vertically. The Investigation noted that the use of Spanish to communicate with one aircraft and English to communicate with the other had compromised situational awareness of the crew of the latter who had also not had visual contact with the other aircraft.

guid: https://skybrary.aero/accidents-and-incidents/a319a332-vicinity-barcelona-spain-2012 uri: https://skybrary.aero/accidents-and-incidents/a319a332-vicinity-barcelona-spain-2012 title: B733, Chambery France, 2012 link: https://skybrary.aero/accidents-and-incidents/b733-chambery-france-2012 description:

On 14 April 2012, a Titan Airways Boeing 737-300 attempted to take off from Chambery with incorrect reference speeds taken from the EFB used for performance calculations. As a consequence, the pressure hull was damaged by a tail strike during take off, although not sufficiently to affect cabin pressure during the subsequent flight. The Investigation concluded that the accident raised regulatory issues in respect of the general design and use of EFB computers to calculate performance data.

guid: https://skybrary.aero/accidents-and-incidents/b733-chambery-france-2012 uri: https://skybrary.aero/accidents-and-incidents/b733-chambery-france-2012 title: A388, en-route, north east of Singapore, 2011 link: https://skybrary.aero/accidents-and-incidents/a388-en-route-north-east-singapore-2011 description:

On 31 January 2011, a Singapore Airlines Airbus A380-800 was in the cruise when there was sudden loud noise and signs of associated electrical smoke and potential burning in a toilet compartment with a corresponding ECAM smoke alert. After a fire extinguisher had been discharged into the apparent source, there were no further signs of fire or smoke. Subsequent investigation found signs of burning below the toilet floor and it was concluded that excessive current caused by a short circuit which had resulted from a degraded cable had been the likely cause, with over current protection limiting the damage caused by overheating.

guid: https://skybrary.aero/accidents-and-incidents/a388-en-route-north-east-singapore-2011 uri: https://skybrary.aero/accidents-and-incidents/a388-en-route-north-east-singapore-2011 title: B773, vicinity Melbourne Australia, 2011 link: https://skybrary.aero/accidents-and-incidents/b773-vicinity-melbourne-australia-2011 description:

On 24 July 2011, a Thai Airways International Boeing 777-300 descended below the safe altitude on a night non-precision approach being flown at Melbourne and then failed to commence the go around instructed by ATC because of this until the instruction had been repeated. The Investigation concluded that the aircraft commander monitoring the automatic approach flown by the First Officer had probably experienced automation surprise in respect of the effects of an unexpected FMS mode change and had thereafter failed to monitor the descent of the aircraft with a selected FMS mode which was not normally used for approach.

guid: https://skybrary.aero/accidents-and-incidents/b773-vicinity-melbourne-australia-2011 uri: https://skybrary.aero/accidents-and-incidents/b773-vicinity-melbourne-australia-2011 title: A320, vicinity Oslo Norway, 2008 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-oslo-norway-2008 description:

On 19 December 2008, an Aeroflot Airbus A320 descended significantly below its cleared and acknowledged altitude after the crew lost situational awareness at night whilst attempting to establish on the ILS at Oslo from an extreme intercept track after a late runway change and an unchallenged incorrect readback. The Investigation concluded that the response to the EGPWS warning which resulted had been “late and slow” but that the risk of CFIT was “present but not imminent”. The context for the event was considered to have been poor communications between ATC and the aircraft in respect of changes of landing runway.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-oslo-norway-2008 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-oslo-norway-2008 title: FA20, Durham Tees Valley UK, 2012 link: https://skybrary.aero/accidents-and-incidents/fa20-durham-tees-valley-uk-2012 description:

On 9 August 2012, a serviceable Cobham Leasing Fan Jet Falcon overran the 2291 metre long runway at Durham Tees Valley after beginning rejecting take off from above V1 because of a suspected bird strike. The crew believed there was a possibility of airframe damage from a single medium sized bird sighted ahead which might have been hit by the main landing gear. It was found that the overrun distance had been increased by low friction on the stopway and noted that the regulatory exemption issued for operation without FDR and CVR was no longer appropriate.

guid: https://skybrary.aero/accidents-and-incidents/fa20-durham-tees-valley-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/fa20-durham-tees-valley-uk-2012 title: SF34/AT72, Helsinki Finland, 2011 link: https://skybrary.aero/accidents-and-incidents/sf34at72-helsinki-finland-2011 description:

On 29 December 2011 a Golden Air ATR 72 making a daylight approach to runway 22R at Helsinki and cleared to land observed a Saab 340 entering the runway and initiated a low go around shortly before ATC, who had observed the incursion, issued a go around instruction. The Investigation attributed the breach of clearance by the Latvian-operated Saab 340 primarily to poor CRM, a poor standard of R/T and inadequate English Language proficiency despite valid certification of the latter.

guid: https://skybrary.aero/accidents-and-incidents/sf34at72-helsinki-finland-2011 uri: https://skybrary.aero/accidents-and-incidents/sf34at72-helsinki-finland-2011 title: BE20, vicinity Glasgow UK, 2012 link: https://skybrary.aero/accidents-and-incidents/be20-vicinity-glasgow-uk-2012 description:

On 15 September 2012, the crew of a Beech Super King Air on a medevac flight making an ILS approach to runway 23 at Glasgow became temporarily distracted by the consequences of a mis-selection made in an unfamiliar variant of their aircraft type and a rapid descent of more than 1000 feet below the 3500 feet cleared altitude towards terrain in IMC at night followed. An EGPWS PULL UP Warning and ATC MSAW activation resulted before the aircraft was recovered back to 3500 feet and the remainder of the flight was uneventful.

guid: https://skybrary.aero/accidents-and-incidents/be20-vicinity-glasgow-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/be20-vicinity-glasgow-uk-2012 title: E170/E120, San Francisco CA, USA 2007 link: https://skybrary.aero/accidents-and-incidents/e170e120-san-francisco-ca-usa-2007 description:

On 26 May 2007, a Republic Airlines Embraer 170 taking off from runway 01L at San Francisco nearly collided with an aircraft which had just landed on intersecting runway 28R and come to a stop at the intersection. Both aircraft were operating in accordance with instructions to take off and land respectively issued by the same TWR controller. After an AMASS conflict alert issued 15 seconds in advance of the subsequent conflict, the controller involved instructed the aircraft on landing roll to hold ,

guid: https://skybrary.aero/accidents-and-incidents/e170e120-san-francisco-ca-usa-2007 uri: https://skybrary.aero/accidents-and-incidents/e170e120-san-francisco-ca-usa-2007 title: A332/B738, vicinity Amsterdam Netherlands, 2012 link: https://skybrary.aero/accidents-and-incidents/a332b738-vicinity-amsterdam-netherlands-2012 description:

On 13 November 2012, a Garuda Airbus A330 and a KLM Boeing 737 lost separation against each other whilst correctly following radar vectors to parallel approaches at Amsterdam but there was no actual risk of collision as each aircraft had the other in sight and no TCAS RA occurred. The Investigation found that one of the controllers involved had used permitted discretion to override normal procedures during a short period of quiet traffic but had failed to restore normal procedures when it became necessary to do so, thus creating the conflict and the ANSP was recommended to review their procedures.

guid: https://skybrary.aero/accidents-and-incidents/a332b738-vicinity-amsterdam-netherlands-2012 uri: https://skybrary.aero/accidents-and-incidents/a332b738-vicinity-amsterdam-netherlands-2012 title: CL30, en-route, north west of Moscow Russia, 2010 link: https://skybrary.aero/accidents-and-incidents/cl30-en-route-north-west-moscow-russia-2010 description:

On 23 December 2010 an aircraft climbing out of Moscow in night IMC experienced a sudden in-flight pitch upset in which the three unrestrained passengers were injured, one seriously, as a result of an inappropriate pilot response to an annunciation of autopilot stabiliser trim malfunction. Despite extensive inspection, no root cause of this malfunction, which had been transitory, could be found. Crew QRH guidance in respect of the fault experienced was found to be unhelpful and crew knowledge of pitch trim - which could have eliminated any pitch disturbance - was deficient.

guid: https://skybrary.aero/accidents-and-incidents/cl30-en-route-north-west-moscow-russia-2010 uri: https://skybrary.aero/accidents-and-incidents/cl30-en-route-north-west-moscow-russia-2010 title: B733, Birmingham UK, 2012 link: https://skybrary.aero/accidents-and-incidents/b733-birmingham-uk-2012 description:

On 21 September 2012, an Aurela Boeing 737-300 lost directional control and left the paved surface when attempting to turn off the landing runway at Birmingham expeditiously to avoid the following aircraft having to go around. The Investigation noted that the range of the approaching aircraft - still 2.5nm as the incident aircraft began to clear the runway - had not been communicated and concluded that the speed of the aircraft had been inappropriate for the prevailing wet surface conditions as well as unnecessary to prevent a go around by the following aircraft.

guid: https://skybrary.aero/accidents-and-incidents/b733-birmingham-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/b733-birmingham-uk-2012 title: MD83, Juba Sudan, 2006 link: https://skybrary.aero/accidents-and-incidents/md83-juba-sudan-2006 description:

On 23 June 2006, an AMC Airlines MD83 significantly overran the landing runway at Juba after a late touchdown followed by unexpected and un-commanded asymmetry in ground spoiler deployment and thrust reverser control caused by an unappreciated loss at some point en-route of all fluid from one of the two hydraulic systems. The Investigation concluded that the abnormal hydraulic system status should have been detectable prior to attempting a landing but also that one of the consequences of hydraulic system design should be modified.

guid: https://skybrary.aero/accidents-and-incidents/md83-juba-sudan-2006 uri: https://skybrary.aero/accidents-and-incidents/md83-juba-sudan-2006 title: B772, Cairo Egypt, 2011 link: https://skybrary.aero/accidents-and-incidents/b772-cairo-egypt-2011 description:

On 29 July 2011 an oxygen-fed fire started in the flight deck of an Egypt Air Boeing 777-200 about to depart from Cairo with most passengers boarded. The fire rapidly took hold despite attempts at extinguishing it but all passengers were safely evacuated via the still-attached air bridge access to doors 1L and 2L. The flight deck and adjacent structure was severely damaged. The Investigation could not conclusively determine the cause of the fire but suspected that wiring damage attributable to inadequately secured cabling may have provided a source of ignition for an oxygen leak from the crew emergency supply

guid: https://skybrary.aero/accidents-and-incidents/b772-cairo-egypt-2011 uri: https://skybrary.aero/accidents-and-incidents/b772-cairo-egypt-2011 title: BN2A, vicinity Bonaire Netherlands Antilles, 2009 link: https://skybrary.aero/accidents-and-incidents/bn2a-vicinity-bonaire-netherlands-antilles-2009 description:

On 22 October 2009, a BN2 Islander suspected to have been overloaded experienced an engine failure shortly after departure from Curaçao. Rather than return, the Pilot chose to continue the flight to the intended destination but had to carry out a ditching when it proved impossible to maintain height. All passengers survived but the Pilot died. The cause of the engine failure could not be established but the Investigation found a context for the accident which had constituted systemic failure by the Operator to deliver operational safety which had been ignored by an inadequate regulatory oversight regime.

guid: https://skybrary.aero/accidents-and-incidents/bn2a-vicinity-bonaire-netherlands-antilles-2009 uri: https://skybrary.aero/accidents-and-incidents/bn2a-vicinity-bonaire-netherlands-antilles-2009 title: B737, Fort Nelson BC Canada, 2012 link: https://skybrary.aero/accidents-and-incidents/b737-fort-nelson-bc-canada-2012 description:

On 9 January 2012, an Enerjet Boeing 737-700 overran the landing runway 03 at Fort Nelson by approximately 70 metres after the newly promoted Captain continued an unstabilised approach to a mis-managed late-touchdown landing. The subsequent Investigation attributed the accident to poor crew performance in the presence of a fatigued aircraft commander.

guid: https://skybrary.aero/accidents-and-incidents/b737-fort-nelson-bc-canada-2012 uri: https://skybrary.aero/accidents-and-incidents/b737-fort-nelson-bc-canada-2012 title: AS3B, vicinity Sumburgh Airport Shetland Islands UK, 2013 link: https://skybrary.aero/accidents-and-incidents/as3b-vicinity-sumburgh-airport-shetland-islands-uk-2013 description:

On 23 August 2013, the crew of a Eurocopter AS332 L2 Super Puma helicopter making a non-precision approach to runway 09 at Sumburgh with the AP engaged in 3-axes mode descended below MDA without visual reference and after exposing the helicopter to vortex ring conditions were unable to prevent a sudden onset high rate of descent followed by sea surface impact and rapid inversion of the floating helicopter. Four of the 18 occupants died and three were seriously injured. The Investigation found no evidence of contributory technical failure and attributed the accident to inappropriate flight path control by the crew.

guid: https://skybrary.aero/accidents-and-incidents/as3b-vicinity-sumburgh-airport-shetland-islands-uk-2013 uri: https://skybrary.aero/accidents-and-incidents/as3b-vicinity-sumburgh-airport-shetland-islands-uk-2013 title: A320 / B738 Barcelona Spain, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-b738-barcelona-spain-2012 description:

On 27 May 2012, an Airbus A320 departing Barcelona was cleared by GND to taxi across an active runway on which a Boeing 737-800 was about to land. Whilst still moving but before entering the runway, the A320 crew, aware of the aircraft on approach, queried their crossing clearance but the instruction to stop was given too late to stop before crossing the unlit stop bar. The 737 was instructed to go around and there was no actual risk of collision. The Investigation attributed the controller error to lack of familiarisation with the routine runway configuration change in progress.

guid: https://skybrary.aero/accidents-and-incidents/a320-b738-barcelona-spain-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-b738-barcelona-spain-2012 title: D228, vicinity Kathmandu Nepal, 2012 link: https://skybrary.aero/accidents-and-incidents/d228-vicinity-kathmandu-nepal-2012 description:

On 28 September 2012, control of a Sita Air Dornier 228 being flown by an experienced pilot was lost at approximately 100 feet aal after take off from Kathmandu in benign daylight weather conditions and the aircraft stalled without obvious attempt at recovery before impacting the ground where a fire broke out. All occupants were killed and the aircraft was destroyed. The comprehensive investigation found that insufficient engine thrust was being delivered to sustain flight but, having eliminated engine bird ingestion and aircraft loading issues, was unable to establish any environmental, airworthiness or loading issue which might have caused this.

guid: https://skybrary.aero/accidents-and-incidents/d228-vicinity-kathmandu-nepal-2012 uri: https://skybrary.aero/accidents-and-incidents/d228-vicinity-kathmandu-nepal-2012 title: B738, Eindhoven Netherlands, 2012 link: https://skybrary.aero/accidents-and-incidents/b738-eindhoven-netherlands-2012 description:

On 11 October 2012, the crew of a Ryanair Boeing 737-800 did not change frequency to TWR when instructed to do so by GND whilst already backtracking the departure runway and then made a 180° turn and took off without clearance still on GND frequency. Whilst no actual loss of ground or airborne safety resulted, the Investigation found that when the Captain had queried the receipt of a take off clearance with the First Officer, he had received and accepted a hesitant confirmation. Crew non-compliance with related AIP ground manoeuvring restrictions replicated in their airport briefing was also noted.

guid: https://skybrary.aero/accidents-and-incidents/b738-eindhoven-netherlands-2012 uri: https://skybrary.aero/accidents-and-incidents/b738-eindhoven-netherlands-2012 title: B733 / vehicle, Amsterdam Netherlands, 2010 link: https://skybrary.aero/accidents-and-incidents/b733-vehicle-amsterdam-netherlands-2010 description:

On 18 December 2010, the ATC Runway Controller responsible for runway 24 at Amsterdam gave a daylight take off clearance in normal visibility to a Norwegian Boeing 737-300 whilst a bird control vehicle which they had earlier given clearance to enter the runway was still on it. The departing aircraft overflew the vehicle without noticing it. The subsequent investigation highlighted significant differences between the procedures for active runway access at Amsterdam and corresponding international practice as well as finding that integrated safety investigation and overall safety management at the airport were systemically ineffective.

guid: https://skybrary.aero/accidents-and-incidents/b733-vehicle-amsterdam-netherlands-2010 uri: https://skybrary.aero/accidents-and-incidents/b733-vehicle-amsterdam-netherlands-2010 title: A321 / B738, Dublin Ireland, 2011 link: https://skybrary.aero/accidents-and-incidents/a321-b738-dublin-ireland-2011 description:

On 21 May 2011, a Monarch Airlines A321 taxiing for departure at Dublin inadvertently taxied onto an active runway after failing to follow its taxi clearance. The incursion was not noticed by ATC but the crew of a Boeing 737 taking off from the same runway did see the other aircraft and initiated a very high speed rejected take off stopping 360 metres from it. The incursion occurred in a complex manoeuvring area to a crew unfamiliar with the airport at a location which was not a designated hot spot. Various mitigations against incursions at this position have since been implemented.

guid: https://skybrary.aero/accidents-and-incidents/a321-b738-dublin-ireland-2011 uri: https://skybrary.aero/accidents-and-incidents/a321-b738-dublin-ireland-2011 title: AT43, vicinity Glasgow, UK 2012 link: https://skybrary.aero/accidents-and-incidents/at43-vicinity-glasgow-uk-2012 description:

On 22 February 2012, the crew of an ATR 42 making a radar-vectored ILS approach to runway 23 at Glasgow at night allowed the airspeed of the aircraft to reduce and a stall warning followed. Corrective action then led to an overspeed and further corrective action almost led to a second stall warning. The Investigation concluded that SOPs were not followed, monitoring was ineffective and crew cooperation during recovery was poor. It was considered that crew performance may have been affected by inadequate rest prior to a night flying duty period.

guid: https://skybrary.aero/accidents-and-incidents/at43-vicinity-glasgow-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/at43-vicinity-glasgow-uk-2012 title: Vehicle / E190 / E121, Jersey Channel Islands, 2010 link: https://skybrary.aero/accidents-and-incidents/vehicle-e190-e121-jersey-channel-islands-2010 description:

On 1 June 2010, an Airport RFFS bird scaring vehicle entered the active runway at Jersey in LVP without clearance and remained there for approximately three minutes until ATC became aware. The subsequent Investigation found that the incursion had fortuitously occurred just after an ERJ 190 had landed and had been terminated just as another aircraft had commenced a go around after failure to acquire the prescribed visual reference required to continue to a landing. The context for the failure of the vehicle driver to follow existing procedures was found to be their inadequacy and appropriate changes were implemented.

guid: https://skybrary.aero/accidents-and-incidents/vehicle-e190-e121-jersey-channel-islands-2010 uri: https://skybrary.aero/accidents-and-incidents/vehicle-e190-e121-jersey-channel-islands-2010 title: A343, vicinity Paris CDG France, 2012 link: https://skybrary.aero/accidents-and-incidents/a343-vicinity-paris-cdg-france-2012 description:

On 13 March 2012, an A340-300 crew cleared for a Cat 3 ILS approach at Paris CDG with LVP in force failed to descend at a rate which would allow the aircraft to capture the ILS GS and at 2nm from the runway, when still 2500 feet above runway height, the ILS GS mode engaged on a false upper lobe of about 10° and as a result of the consequent rapid pitch up and speed reduction, aircraft control was almost lost. After a period of further confusion, a go around was initiated and the subsequent approach was uneventful.

guid: https://skybrary.aero/accidents-and-incidents/a343-vicinity-paris-cdg-france-2012 uri: https://skybrary.aero/accidents-and-incidents/a343-vicinity-paris-cdg-france-2012 title: A319, Copenhagen Denmark, 2012 link: https://skybrary.aero/accidents-and-incidents/a319-copenhagen-denmark-2012 description:

On 21 September 2012, an SAS A319 which had just landed normally under the control of an experienced pilot left the paved surface when attempting to make a turn off the RET at a taxi speed greater than appropriate. The pilot was familiar with the airport layout and the misjudgement was attributed in part to the fact that the pilot involved had recently converted to their first Airbus type after a long period operating the DC9/MD80/90 series which had a different pilot eye height and was fitted with steel rather than the more modern carbon brakes.

guid: https://skybrary.aero/accidents-and-incidents/a319-copenhagen-denmark-2012 uri: https://skybrary.aero/accidents-and-incidents/a319-copenhagen-denmark-2012 title: AT72 / JS32, en-route, north east of Jonkoping Sweden, 2012 link: https://skybrary.aero/accidents-and-incidents/at72-js32-en-route-north-east-jonkoping-sweden-2012 description:

On 20 June 2012, an ATR72-200 level at FL140 and a climbing opposite direction Jetstream 32 received and correctly responded to co-ordinated TCAS RAs after ATC error. The controller had not noticed visual MTCD and STCA alerts and had attempted to continue active controlling after a TCAS RA declaration. The Investigation observed that the ineffectiveness of visual conflict alerts had previously featured in a similar event at the same ACC and that the ANSP had advised then that its addition was planned. TCAS RA response controller training was considered to be in need of improvement to make it more effective.

guid: https://skybrary.aero/accidents-and-incidents/at72-js32-en-route-north-east-jonkoping-sweden-2012 uri: https://skybrary.aero/accidents-and-incidents/at72-js32-en-route-north-east-jonkoping-sweden-2012 title: B739, Pekanbaru Indonesia, 2011 link: https://skybrary.aero/accidents-and-incidents/b739-pekanbaru-indonesia-2011 description:

On 14 February 2011, a Lion Air Boeing 737-900 making a night landing at Pekanbaru overran the end of the 2240 metre long runway onto the stopway after initially normal deceleration largely attributable to the thrust reversers was followed by a poor response to applied maximum braking in the final 300 metres. Whilst performance calculations showed that a stop on the runway should have been possible, it was concluded that a combination of water patches with heavy rubber contamination had reduced the friction properties of the surface towards the end of the runway and hence the effectiveness of brake application.

guid: https://skybrary.aero/accidents-and-incidents/b739-pekanbaru-indonesia-2011 uri: https://skybrary.aero/accidents-and-incidents/b739-pekanbaru-indonesia-2011 title: A333, vicinity Orlando FL USA, 2013 link: https://skybrary.aero/accidents-and-incidents/a333-vicinity-orlando-fl-usa-2013 description:

On 19 January 2013, a Rolls Royce Trent 700-powered Virgin Atlantic Airbus A330-300 hit some medium sized birds shortly after take off from Orlando, sustaining airframe impact damage and ingesting one bird into each engine. Damage was subsequently found to both engines although only one indicated sufficient malfunction - a complete loss of oil pressure - for an in-flight shutdown to be required. After declaration of a MAYDAY, the return to land overweight was completed uneventfully. The investigation identified an issue with the response of the oil pressure detection and display system to high engine vibration events and recommended modification.

guid: https://skybrary.aero/accidents-and-incidents/a333-vicinity-orlando-fl-usa-2013 uri: https://skybrary.aero/accidents-and-incidents/a333-vicinity-orlando-fl-usa-2013 title: B733, en-route, north of Yuma AZ USA, 2011 link: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-yuma-az-usa-2011 description:

On 1 April 2011, a Southwest Boeing 737-300 climbing through FL340 experienced a sudden loss of pressurisation as a section of fuselage crown skin ruptured. A successful emergency descent was made with a diversion to Yuma, where the aircraft landed half an hour later. Investigation found that the cause of the failure was an undetected manufacturing fault in the 15 year-old aircraft. One member of the cabin crew and an off duty staff member who tried to assist him became temporarily unconscious after disregarding training predicated on the time of useful consciousness after sudden depressurisation.

guid: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-yuma-az-usa-2011 uri: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-yuma-az-usa-2011 title: B738, Glasgow UK, 2012 link: https://skybrary.aero/accidents-and-incidents/b738-glasgow-uk-2012 description:

On 19 October 2012, a Jet2-operated Boeing 737-800 departing Glasgow made a high speed rejected take off when a strange smell became apparent in the flight deck and the senior cabin crew reported what appeared to be smoke in the cabin. The subsequent emergency evacuation resulted in one serious passenger injury. The Investigation was unable to conclusively identify a cause of the smoke and the also- detected burning smells but excess moisture in the air conditioning system was considered likely to have been a factor and the Operator subsequently made changes to its maintenance procedures.

guid: https://skybrary.aero/accidents-and-incidents/b738-glasgow-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/b738-glasgow-uk-2012 title: AT43, Jersey Channel Islands, 2012 link: https://skybrary.aero/accidents-and-incidents/at43-jersey-channel-islands-2012 description:

On 16 July 2012, the left main landing gear of a Blue Islands ATR 42-300 collapsed during landing at Jersey. The aircraft stopped quickly on the runway as the left wing and propeller made ground contact. Although the crew saw no imminent danger once the aircraft had stopped, the passengers thought otherwise and perceived the need for an emergency evacuation which the sole cabin crew facilitated. The Investigation found that the fatigue failure of a side brace had initiated the gear collapse and that the origin of this was a casting discontinuity in a billet of aluminium produced to specification.

guid: https://skybrary.aero/accidents-and-incidents/at43-jersey-channel-islands-2012 uri: https://skybrary.aero/accidents-and-incidents/at43-jersey-channel-islands-2012 title: B773, en-route, South China Sea Vietnam 2011 link: https://skybrary.aero/accidents-and-incidents/b773-en-route-south-china-sea-vietnam-2011 description:

On 17 October 2011, a Singapore Airlines Boeing 777-300 in the cruise at night with a Training Captain in command made what turned out to be an insufficient deviation around a potential source of turbulence and, with the seat belt signs remaining off, a number of cabin crew and passenger injuries were sustained during sudden brief but severe turbulence encounter. The Operator subsequently introduced enhanced pilot training to support more effective weather avoidance and better use of the various types of weather radar fitted to aircraft in their 777 fleet.

guid: https://skybrary.aero/accidents-and-incidents/b773-en-route-south-china-sea-vietnam-2011 uri: https://skybrary.aero/accidents-and-incidents/b773-en-route-south-china-sea-vietnam-2011 title: SF34, vicinity Mariehamn Finland, 2012 link: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-mariehamn-finland-2012 description:

On 14 February 2012 a Latvian-operated Saab 340 acknowledged an ATC clearance to make a procedural ILS approach to Mariehamn and then completely disregarded the clearance by setting course direct to the aerodrome. Subsequently, having lost situational awareness, repeated GPWS PULL UP warnings at night in VMC were ignored as control of the aircraft was lost with a recovery only achieved an estimated 2 seconds before ground impact would have occurred and then followed by more ignored PULL UP Warnings due to continued proximity to terrain before the runway was sighted and a landing achieved.

guid: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-mariehamn-finland-2012 uri: https://skybrary.aero/accidents-and-incidents/sf34-vicinity-mariehamn-finland-2012 title: A319 / PRM1, en-route, near Fribourg Switzerland, 2011 link: https://skybrary.aero/accidents-and-incidents/a319-prm1-en-route-near-fribourg-switzerland-2011 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a319-prm1-en-route-near-fribourg-switzerland-2011 uri: https://skybrary.aero/accidents-and-incidents/a319-prm1-en-route-near-fribourg-switzerland-2011 title: B738 / B738, Seville Spain, 2012 link: https://skybrary.aero/accidents-and-incidents/b738-b738-seville-spain-2012 description:

On 13 April 2012 a Boeing 737-800 being taxied off its parking stand for a night departure by the aircraft commander failed to follow the clearly and correctly marked taxi centrelines on the well-lit apron and instead took a short cut towards the taxiway centreline which resulted in the left winglet striking the left horizontal stabiliser and elevator of another Ryanair aircraft correctly parked on the adjacent stand causing damage which rendered both aircraft unfit for flight. The pilot involved was familiar with the airport and had gained almost all his flying experience on the accident aircraft type.

guid: https://skybrary.aero/accidents-and-incidents/b738-b738-seville-spain-2012 uri: https://skybrary.aero/accidents-and-incidents/b738-b738-seville-spain-2012 title: MD83, Kandahar Afghanistan, 2012 link: https://skybrary.aero/accidents-and-incidents/md83-kandahar-afghanistan-2012 description:

On 24 January 2012, a Swiftair Boeing MD83 about to touch down on runway 05 at Kandahar lost alignment with the extended runway centreline when initiating the daylight landing flare for a landing and a corrective roll resulted in the right wing tip striking the ground 20 metres prior to the runway threshold before completing the landing. The Investigation found that the prior approach had been unstable both at the prescribed ‘gate’ and thereafter and should have led to a go around. It was also found that neither the operator nor the crew were authorised to make the GPS approach used.

guid: https://skybrary.aero/accidents-and-incidents/md83-kandahar-afghanistan-2012 uri: https://skybrary.aero/accidents-and-incidents/md83-kandahar-afghanistan-2012 title: DHC6, Dabra Indonesia, 2011 link: https://skybrary.aero/accidents-and-incidents/dhc6-dabra-indonesia-2011 description:

On 17 October 2011, the pilot of a Merpati DHC6 attempting to land at Dabra on a scheduled passenger flight lost control of the aircraft when several bounces were followed by the aircraft leaving the runway and hitting some banana trees before re entering the runway whereupon a ground loop was made near the end of the runway to prevent an overrun onto unfavourable terrain. The aircraft was damaged but none of the occupants were injured. The mis-managed landing was attributed to an unstabilised approach.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-dabra-indonesia-2011 uri: https://skybrary.aero/accidents-and-incidents/dhc6-dabra-indonesia-2011 title: C30J, en-route, northern Sweden 2012 link: https://skybrary.aero/accidents-and-incidents/c30j-en-route-northern-sweden-2012 description:

On 15 March 2012, a Royal Norwegian Air Force C130J-30 Hercules en route on a positioning transport flight from northern Norway to northern Sweden crossed the border, descended into uncontrolled airspace below MSA and entered IMC. Shortly after levelling at FL 070, it flew into the side of a 6608 foot high mountain. The Investigation concluded that although the direct cause was the actions of the crew, Air Force procedures supporting the operation were deficient. It also found that the ATC service provided had been contrary to regulations and attributed this to inadequate controller training.

guid: https://skybrary.aero/accidents-and-incidents/c30j-en-route-northern-sweden-2012 uri: https://skybrary.aero/accidents-and-incidents/c30j-en-route-northern-sweden-2012 title: A320 / A346, en-route, Eastern Indian Ocean, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-a346-en-route-eastern-indian-ocean-2012 description:

On 18 January 2012, ATC error resulted in two aircraft on procedural clearances in oceanic airspace crossing the same waypoint within an estimated 2 minutes of each other without the prescribed 1000 feet vertical separation when the prescribed minimum separation was 15 minutes unless that vertical separation existed. By the time ATC identified the loss of separation and sent a CPDLC message to the A340 to descend in order to restore separation, the crew advised that such action was already being taken. The Investigation identified various organisational deficiencies relating to the provision of procedural service by the ANSP concerned.

guid: https://skybrary.aero/accidents-and-incidents/a320-a346-en-route-eastern-indian-ocean-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-a346-en-route-eastern-indian-ocean-2012 title: SB20 / C510, vicinity Lugano Switzerland, 2011 link: https://skybrary.aero/accidents-and-incidents/sb20-c510-vicinity-lugano-switzerland-2011 description:

On 16 December 2011, a Saab 2000 in the hold and an opposite direction Cessna VLJ joining it lost procedural separation in IMC near Lugano due to conflicting ATC clearances issued by the same controller who had used the wrong Transition Level. Any risk of collision was removed by a TCAS RA activated on the Saab 2000 but the Investigation found that the DFTI radar display available to the controller to help resolve unexpected emergency situations was configured to systematically convert SSR standard pressure altitudes to QNH for altitude display using a distant and inappropriate value of QNH.

guid: https://skybrary.aero/accidents-and-incidents/sb20-c510-vicinity-lugano-switzerland-2011 uri: https://skybrary.aero/accidents-and-incidents/sb20-c510-vicinity-lugano-switzerland-2011 title: C550, vicinity Cagliari Sardinia Italy, 2004 link: https://skybrary.aero/accidents-and-incidents/c550-vicinity-cagliari-sardinia-italy-2004 description:

On 24 February 2004, a Cessna 550 inbound to Cagliari at night requested and was approved for a visual approach without crew awareness of the surrounding terrain. It was subsequently destroyed by terrain impact and a resultant fire during descent and all occupants were killed. The Investigation concluded that the accident was the consequence of the way the crew conducted the flight in the absence of adequate visual references and with the possibility of a black hole effect. It was also noted that the aircraft was not fitted, nor required to be fitted, with TAWS.

guid: https://skybrary.aero/accidents-and-incidents/c550-vicinity-cagliari-sardinia-italy-2004 uri: https://skybrary.aero/accidents-and-incidents/c550-vicinity-cagliari-sardinia-italy-2004 title: B737/C212 en-route/manoeuvring, near Richmond NSW Australia, 2011 link: https://skybrary.aero/accidents-and-incidents/b737c212-en-routemanoeuvring-near-richmond-nsw-australia-2011 description:

On 5 November 2011, ATC cleared a Virgin Australia Boeing 737-700 to climb without speed restriction through an active parachute Drop Zone contrary to prevailing ATC procedures. As a result, prescribed separation from the drop zone was not maintained, but an avoiding action turn initiated by the 737 crew in VMC upon recognising the conflict eliminated any actual risk of collision with either the drop aircraft or its already-departed free-fall parachutists. The incident was attributed to a combination of inadequate controller training and inadequate ATC operational procedures.

guid: https://skybrary.aero/accidents-and-incidents/b737c212-en-routemanoeuvring-near-richmond-nsw-australia-2011 uri: https://skybrary.aero/accidents-and-incidents/b737c212-en-routemanoeuvring-near-richmond-nsw-australia-2011 title: A319 / A321, en-route, west north west of Geneva, Switzerland 2011 link: https://skybrary.aero/accidents-and-incidents/a319-a321-en-route-west-north-west-geneva-switzerland-2011 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a319-a321-en-route-west-north-west-geneva-switzerland-2011 uri: https://skybrary.aero/accidents-and-incidents/a319-a321-en-route-west-north-west-geneva-switzerland-2011 title: AT72, vicinity Tyumen Russian Federation, 2012 link: https://skybrary.aero/accidents-and-incidents/at72-vicinity-tyumen-russian-federation-2012 description:

On 2 April 2012, the crew of an ATR72-200 which had just taken off from Tyumen lost control of their aircraft when it stalled after the flaps were retracted and did not recover before it crashed and caught fire killing or seriously injuring all occupants. The Investigation found that the Captain knew that frozen deposits had accumulated on the airframe but appeared to have been unaware of the danger of not having the airframe de-iced. It was also found that the crew had not recognised the stall when it occurred and had overpowered the stick pusher and pitched up.

guid: https://skybrary.aero/accidents-and-incidents/at72-vicinity-tyumen-russian-federation-2012 uri: https://skybrary.aero/accidents-and-incidents/at72-vicinity-tyumen-russian-federation-2012 title: CRJ2, Barcelona Spain, 2011 link: https://skybrary.aero/accidents-and-incidents/crj2-barcelona-spain-2011 description:

On 30 July 2011, an Air Nostrum CRJ200 continued a significantly unstable visual approach to Barcelona in the vicinity of a convective storm to a point where the aircraft commander considered that a go around would be less safe than continuing the approach. In an attempt to regain a viable vertical profile from above, sustained and very high rates of descent were flown triggering a continuous 16 seconds of EGPWS Mode 1 PULL UP Warnings which were completely ignored. The resultant very hard landing caused structural damage to the aircraft and the sole cabin crew sustained a minor injury.

guid: https://skybrary.aero/accidents-and-incidents/crj2-barcelona-spain-2011 uri: https://skybrary.aero/accidents-and-incidents/crj2-barcelona-spain-2011 title: B738, vicinity Kittilä, Finland 2012 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-kittila-finland-2012 description:

On 26 December 2012, a Boeing 737-800 experienced an uncommanded pitch up in IMC when intercepting the ILS GS at Kittilä. Initial crew response could not prevent a rapid transition to a very high nose up attitude and stick shaker activation occurred. Recovery from this upset was eventually achieved. The Investigation found that frozen de icing fluid had prevented three of the four input cranks for both elevator PCUs from functioning normally. It also concluded that, notwithstanding new de-icing procedures introduced by Boeing since the occurrence, the current aircraft type certification for all 737 variants may be unsound.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-kittila-finland-2012 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-kittila-finland-2012 title: B773, vicinity Toronto Canada, 2012 link: https://skybrary.aero/accidents-and-incidents/b773-vicinity-toronto-canada-2012 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/b773-vicinity-toronto-canada-2012 uri: https://skybrary.aero/accidents-and-incidents/b773-vicinity-toronto-canada-2012 title: A319, vicinity Wuxi China, 2010 link: https://skybrary.aero/accidents-and-incidents/a319-vicinity-wuxi-china-2010 description:

On 14 September 2010, the crew of a Sichuan Airlines Airbus A319 continued an ILS approach into Wuxi despite awareness of adverse convective weather conditions at the airport. Their inattention to automation management then led to a low energy warning and the inappropriate response to this led to the activation of flight envelope protection quickly followed by a stall warning. Inappropriate response to this was followed by loss of control and a full stall and high rate of descent from which recovery was finally achieved less than 900 feet agl.

guid: https://skybrary.aero/accidents-and-incidents/a319-vicinity-wuxi-china-2010 uri: https://skybrary.aero/accidents-and-incidents/a319-vicinity-wuxi-china-2010 title: A320 / C56X, vicinity Geneva Switzerland, 2011 link: https://skybrary.aero/accidents-and-incidents/a320-c56x-vicinity-geneva-switzerland-2011 description:

On 17 August 2012, a Swiss A320 being positioned under radar vectors for arrival at Geneva was inadvertently vectored into conflict with a Cessna Citation already established on the ILS LOC for runway 23 at Geneva. Controller training was in progress and the Instructor had just taken control because of concerns at the actions of the Trainee. An error by the Instructor was recognised and de-confliction instructions were given but a co-ordinated TCAS RA still subsequently occurred. STCA was activated but constraints on access to both visual and aural modes of the system served to diminish its value.

guid: https://skybrary.aero/accidents-and-incidents/a320-c56x-vicinity-geneva-switzerland-2011 uri: https://skybrary.aero/accidents-and-incidents/a320-c56x-vicinity-geneva-switzerland-2011 title: SW4, Cork Ireland, 2011 link: https://skybrary.aero/accidents-and-incidents/sw4-cork-ireland-2011 description:

On 10 February 2011, control of a Spanish-operated Fairchild SA227 operating a scheduled passenger flight from Belfast UK to Cork, Ireland was lost during an attempt to commence a third go around due to fog from 100 feet below the approach minimum height. The Investigation identified contributory causes including serial non-compliance with many operational procedures and inadequate regulatory oversight of the Operator. Complex relationships were found to prevail between the Operator and other parties, including “Manx2”, an Isle of Man-based Ticket Seller under whose visible identity the aircraft operated. Most resultant Safety Recommendations concerned systemic improvement in regulatory oversight effectiveness.

guid: https://skybrary.aero/accidents-and-incidents/sw4-cork-ireland-2011 uri: https://skybrary.aero/accidents-and-incidents/sw4-cork-ireland-2011 title: EC35, vicinity Glasgow City Heliport UK, 2013 link: https://skybrary.aero/accidents-and-incidents/ec35-vicinity-glasgow-city-heliport-uk-2013 description:

On 29 November 2013, control of an Airbus Helicopters EC135 undertaking a night VMC night for policing purposes was lost after both engines flamed out following fuel starvation. The subsequent crash killed the three occupants and seven on the ground, seriously injuring eleven others. The Investigation found that although the pilot had acknowledged low fuel warnings after both fuel transfer pumps had been switched off, the helicopter had not then been landed within 10 minutes as required. No evidence of any relevant airworthiness defects was found and without FDR/CVR data, a full explanation of the accident circumstances was not possible.

guid: https://skybrary.aero/accidents-and-incidents/ec35-vicinity-glasgow-city-heliport-uk-2013 uri: https://skybrary.aero/accidents-and-incidents/ec35-vicinity-glasgow-city-heliport-uk-2013 title: AS3B, en-route, northern North Sea UK, 2008 link: https://skybrary.aero/accidents-and-incidents/as3b-en-route-northern-north-sea-uk-2008 description:

On 22 February 2008, a Eurocopter AS332 L2 Super Puma flying from an offshore oil platform to Aberdeen was struck by lightning. There was no apparent consequence and so, although this event required a landing as soon as possible, the commander decided to continue the remaining 165nm to the planned destination which was achieved uneventfully. Main rotor blade damage including some beyond repairable limits was subsequently discovered. The Investigation noted evidence indicating that this helicopter type had a relatively high propensity to sustain lightning strikes but noted that, despite the risk of damage, there was currently no adverse safety trend.

guid: https://skybrary.aero/accidents-and-incidents/as3b-en-route-northern-north-sea-uk-2008 uri: https://skybrary.aero/accidents-and-incidents/as3b-en-route-northern-north-sea-uk-2008 title: EC25, en-route, 20nm east of Aberdeen UK, 2012 link: https://skybrary.aero/accidents-and-incidents/ec25-en-route-20nm-east-aberdeen-uk-2012 description:

On 10 May 2012, the crew of a Eurocopter EC225 LP on a flight from Aberdeen to an offshore platform received an indication that the main gearbox (MGB) lubrication system had failed. Shortly after selecting the emergency lubrication system, that also indicated failure and the crew responded in accordance with the QRH drill to “land immediately” by carrying out a successful controlled ditching. The ongoing investigation has found that there had been a mechanical failure of the MGB but that the emergency lubrication system had, contrary to indications, been functioning normally.

guid: https://skybrary.aero/accidents-and-incidents/ec25-en-route-20nm-east-aberdeen-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/ec25-en-route-20nm-east-aberdeen-uk-2012 title: EC25, en-route, 32nm southwest of Sumburgh UK, 2012 link: https://skybrary.aero/accidents-and-incidents/ec25-en-route-32nm-southwest-sumburgh-uk-2012 description:

On 22 October 2012, the crew of a Eurocopter EC225 LP on a flight from Aberdeen to an offshore platform received an indication that the main gearbox (MGB) lubrication system had failed. Shortly after selecting the emergency lubrication system, that system also indicated failure and the crew responded in accordance with the QRH drill to “land immediately” by carrying out a successful controlled ditching. The ongoing investigation has found that there had been a mechanical failure within the MGB but that the emergency lubrication system had, contrary to indications, been functioning normally.

guid: https://skybrary.aero/accidents-and-incidents/ec25-en-route-32nm-southwest-sumburgh-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/ec25-en-route-32nm-southwest-sumburgh-uk-2012 title: AS3B, vicinity Den Helder Netherlands, 2006 link: https://skybrary.aero/accidents-and-incidents/as3b-vicinity-den-helder-netherlands-2006 description:

On 21 November 2006, the crew of a Bristow Eurocopter AS332 L2 making an unscheduled passenger flight from an offshore platform to Den Helder in night VMC decided to ditch their aircraft after apparent malfunction of an engine and the flight controls were perceived as rendering it unable to safely complete the flight. All 17 occupants survived but the evacuation was disorganised and both oversight of the operation by and the actions of the crew were considered to have been inappropriate in various respects. Despite extensive investigation, no technical fault which would have rendered it unflyable could be confirmed.

guid: https://skybrary.aero/accidents-and-incidents/as3b-vicinity-den-helder-netherlands-2006 uri: https://skybrary.aero/accidents-and-incidents/as3b-vicinity-den-helder-netherlands-2006 title: EC25, vicinity ETAP Central offshore platform, North Sea UK link: https://skybrary.aero/accidents-and-incidents/ec25-vicinity-etap-central-offshore-platform-north-sea-uk description:

On 18 February 2009, the crew of Eurocopter EC225 LP Super Puma attempting to make an approach to a North Sea offshore platform in poor visibility at night lost meaningful visual reference and a sea impact followed. All occupants escaped from the helicopter and were subsequently rescued. The investigation concluded that the accident probably occurred because of the effects of oculogravic and somatogravic illusions combined with both pilots being focused on the platform and not monitoring the flight instruments.

guid: https://skybrary.aero/accidents-and-incidents/ec25-vicinity-etap-central-offshore-platform-north-sea-uk uri: https://skybrary.aero/accidents-and-incidents/ec25-vicinity-etap-central-offshore-platform-north-sea-uk title: E145, Ljubljana Slovenia, 2010 link: https://skybrary.aero/accidents-and-incidents/e145-ljubljana-slovenia-2010 description:

On 24 May 2010 the crew of a Regional Embraer 145 operating for Air France continued an unstable visual approach at Ljubljana despite breaching mandatory go-around SOPs and ignoring a continuous EGPWS PULL UP Warning. The subsequent touchdown was bounced and involved ground contact estimated to have been at 1300fpm with a resultant vertical acceleration of 4g. Substantial damage was caused to the landing gear and adjacent fuselage. It was concluded that the type-experienced crew had mis-judged a visual approach and then continued an unstabilised approach to a touchdown with the aircraft not properly under control.

guid: https://skybrary.aero/accidents-and-incidents/e145-ljubljana-slovenia-2010 uri: https://skybrary.aero/accidents-and-incidents/e145-ljubljana-slovenia-2010 title: B738/B738, vicinity Oslo Norway, 2012 link: https://skybrary.aero/accidents-and-incidents/b738b738-vicinity-oslo-norway-2012 description:

On 31 October 2012, a Boeing 737-800 on go around after delaying the breaking off of a fast and high unstable ILS approach at Oslo lost separation in IMC against another aircraft of the same type and Operator which had just taken off from the same runway as the landing was intended to be made on. The situation was aggravated by both aircraft responding to a de-confliction turn given to the aircraft on go around. Minimum separation was 0.2nm horizontally when 500 feet apart vertically, both climbing. Standard missed approach and departure tracks were the same.

guid: https://skybrary.aero/accidents-and-incidents/b738b738-vicinity-oslo-norway-2012 uri: https://skybrary.aero/accidents-and-incidents/b738b738-vicinity-oslo-norway-2012 title: PRM1/CRJ2, Nice France, 2012 link: https://skybrary.aero/accidents-and-incidents/prm1crj2-nice-france-2012 description:

On 29 March 2010, a Raytheon 390 operating a passenger charter flight failed to follow acknowledged taxi instructions in normal visibility at night and entered the departure runway at an intermediate intersection and turned to backtrack against an opposite direction CRJ200 which had just started its take off roll. There was no ATC intervention but the CRJ crew saw the aircraft ahead and were able to stop before reaching it. The Raytheon flight crew stated that they had “encountered considerable difficulties finding out where they were while taxiing” and ended up on the departure runway “without realising it”.

guid: https://skybrary.aero/accidents-and-incidents/prm1crj2-nice-france-2012 uri: https://skybrary.aero/accidents-and-incidents/prm1crj2-nice-france-2012 title: MD83, en-route, near Nancy France, 2009 link: https://skybrary.aero/accidents-and-incidents/md83-en-route-near-nancy-france-2009 description:

On 20 December 2009 a Blue Line McDonnell Douglas MD-83 almost stalled at high altitude after the crew attempted to continue climbing beyond the maximum available altitude at the prevailing aircraft weight. The Investigation found that failure to cross check data input to the Performance Management System prior to take off had allowed a gross data entry error made prior to departure - use of the Zero Fuel Weight in place of Gross Weight - to go undetected.

guid: https://skybrary.aero/accidents-and-incidents/md83-en-route-near-nancy-france-2009 uri: https://skybrary.aero/accidents-and-incidents/md83-en-route-near-nancy-france-2009 title: B732, vicinity Resolute Bay Canada, 2011 link: https://skybrary.aero/accidents-and-incidents/b732-vicinity-resolute-bay-canada-2011 description:

On 20 August 2011, a First Air Boeing 737-200 making an ILS approach to Resolute Bay struck a hill east of the designated landing runway in IMC and was destroyed. An off-track approach was attributed to the aircraft commander s failure to recognise the effects of his inadvertent interference with the AP ILS capture mode and the subsequent loss of shared situational awareness on the flight deck. The approach was also continued when unstabilised and the Investigation concluded that the poor CRM and SOP compliance demonstrated on the accident flight were representative of a wider problem at the operator.

guid: https://skybrary.aero/accidents-and-incidents/b732-vicinity-resolute-bay-canada-2011 uri: https://skybrary.aero/accidents-and-incidents/b732-vicinity-resolute-bay-canada-2011 title: A333, en-route, near Bournemouth UK, 2012 link: https://skybrary.aero/accidents-and-incidents/a333-en-route-near-bournemouth-uk-2012 description:

On 16 April 2012, a Virgin Atlantic A330-300 made an air turnback to London Gatwick after repetitive hold smoke detector warnings began to occur during the climb. Continuing uncertainty about whether the warnings, which continued after landing, were false led to the decision to order an emergency evacuation on the runway. Subsequent investigation found that the smoke warnings had all been false and had mainly come from one faulty detector. It also found that aspects of the way the evacuation had taken place had indicated where there were opportunities to try and improve passenger behaviour.

guid: https://skybrary.aero/accidents-and-incidents/a333-en-route-near-bournemouth-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/a333-en-route-near-bournemouth-uk-2012 title: B742, Düsseldorf Germany, 2005 link: https://skybrary.aero/accidents-and-incidents/b742-dusseldorf-germany-2005 description:

On 24 January 2005, an Atlas Air Boeing 747-200F overran the end of the landing runway at Düsseldorf after runway braking action notified just prior to landing as medium due to snowfall unexpectedly deteriorated after the snowfall intensified. The overrun led to collision with ground obstacles and engines 2 and 3 caught fire. Escape slide malfunction at the forward left hand door led to an alternative non standard crew evacuation route being used. Significant damage to the aircraft resulted in it being declared a hull loss. The Investigation took almost 8 years to complete and publish.

guid: https://skybrary.aero/accidents-and-incidents/b742-dusseldorf-germany-2005 uri: https://skybrary.aero/accidents-and-incidents/b742-dusseldorf-germany-2005 title: A320/E190/B712, vicinity Helsinki Finland, 2013 link: https://skybrary.aero/accidents-and-incidents/a320e190b712-vicinity-helsinki-finland-2013 description:

On 6 February 2013, ATC mismanagement of an Airbus A320 instructed to go around resulted in loss of separation in IMC against the Embraer 190 ahead which was obliged to initiate a go around when no landing clearance had been issued due to a Boeing 737-800 still on the runway after landing. Further ATC mismanagement then resulted in a second IMC loss of separation between the Embraer 190 and a Boeing 717 which had just take off from the parallel runway. Controller response to the STCA Alerts generated was found to be inadequate and ANSP procedures in need of improvement.

guid: https://skybrary.aero/accidents-and-incidents/a320e190b712-vicinity-helsinki-finland-2013 uri: https://skybrary.aero/accidents-and-incidents/a320e190b712-vicinity-helsinki-finland-2013 title: A332, Caracas Venezuela, 2013 link: https://skybrary.aero/accidents-and-incidents/a332-caracas-venezuela-2013 description:

On 13 April 2013, an Air France Airbus A330-200 was damaged during a hard (2.74 G) landing at Caracas after the aircraft commander continued despite the aircraft becoming unstabilised below 500 feet agl with an EGPWS ‘SINK RATE’ activation beginning in the flare. Following a superficial inspection, maintenance personnel determined that no action was required and released the aircraft to service. After take off, it was impossible to retract the landing gear and the aircraft returned. Considerable damage from the earlier landing was then found to both fuselage and landing gear which had rendered the aircraft unfit to fly.

guid: https://skybrary.aero/accidents-and-incidents/a332-caracas-venezuela-2013 uri: https://skybrary.aero/accidents-and-incidents/a332-caracas-venezuela-2013 title: Vehicle / UNKN, Singapore Changi, 2013 link: https://skybrary.aero/accidents-and-incidents/vehicle-unkn-singapore-changi-2013 description:

On 4 April 2013, during a brief daytime runway closure for inspection purposes, a vehicle entered the runway without ATC awareness and was still there when the runway was re-opened and the first landing clearance was issued. TWR control subsequently observed the vehicle on the runway visually but, when they were unable to make contact with it, instructed the aircraft on final approach to go around when it was just under 1nm from touchdown. It was discovered that the vehicle involved had been in broken contact with another nearby aerodrome because the wrong radio frequency had been selected.

guid: https://skybrary.aero/accidents-and-incidents/vehicle-unkn-singapore-changi-2013 uri: https://skybrary.aero/accidents-and-incidents/vehicle-unkn-singapore-changi-2013 title: AT72, Helsinki Finland, 2012 link: https://skybrary.aero/accidents-and-incidents/at72-helsinki-finland-2012 description:

On 19 August 2012, the crew of a Flybe Finland ATR 72-200 approaching Helsinki failed to respond appropriately to a fault which limited rudder travel and were then unable to maintain directional control after touchdown with a veer off the runway then following. It was concluded that as well as prioritising a continued approach over properly dealing with the annunciated caution, crew technical knowledge in respect of the fault encountered had been poor and related training inadequate. Deficiencies found in relevant aircraft manufacturer operating documentation were considered to have been a significant factor and Safety Recommendations were made accordingly.

guid: https://skybrary.aero/accidents-and-incidents/at72-helsinki-finland-2012 uri: https://skybrary.aero/accidents-and-incidents/at72-helsinki-finland-2012 title: HAWK, vicinity Bournemouth, UK 2011 link: https://skybrary.aero/accidents-and-incidents/hawk-vicinity-bournemouth-uk-2011 description:

On 20 August 2011, a RAF Aerobatic Team Hawk failed to complete a formation break to land near Bournemouth and the aircraft flew into the ground, destroying the aircraft and killing the pilot. The subsequent Inquiry concluded that the pilot had become semi conscious as the result of the sudden onset of G-induced impairment characterised as A-LOC. It was found that the manoeuvre as flown was not radically different to usual and that the context for the accident was to be found in a range of organisational failures in risk management.

guid: https://skybrary.aero/accidents-and-incidents/hawk-vicinity-bournemouth-uk-2011 uri: https://skybrary.aero/accidents-and-incidents/hawk-vicinity-bournemouth-uk-2011 title: B788, London Heathrow UK, 2013 link: https://skybrary.aero/accidents-and-incidents/b788-london-heathrow-uk-2013 description:

On 12 July 2013 an unoccupied and unpowered Boeing 787-8, remotely parked at London Heathrow after an arrival earlier the same day caught fire. An investigation found that the source of the fire was an uncontained thermal runaway in the lithium-metal battery within an Emergency Locator Transmitter (ELT). Fifteen Safety Recommendations, all but one to the FAA, were made as a result of the Investigation.

guid: https://skybrary.aero/accidents-and-incidents/b788-london-heathrow-uk-2013 uri: https://skybrary.aero/accidents-and-incidents/b788-london-heathrow-uk-2013 title: B738, Lyon France, 2009 link: https://skybrary.aero/accidents-and-incidents/b738-lyon-france-2009 description:

On 29 August 2009, an Air Algérie Boeing B737-800 departed the side of the runway during take off but then regained the paved surface after sustaining damage from obstructions, completed the take off without further event and continued to destination. Damage to one of the engines, to tyres and to two lights was discovered at the destination. ATC remained unaware of the excursion until the Operator asked its representative at Lyon to ask the airport to carry out a runway inspection.

guid: https://skybrary.aero/accidents-and-incidents/b738-lyon-france-2009 uri: https://skybrary.aero/accidents-and-incidents/b738-lyon-france-2009 title: A319, vicinity Tunis Tunisia, 2012 link: https://skybrary.aero/accidents-and-incidents/a319-vicinity-tunis-tunisia-2012 description:

On 24 March 2012, an Air France Airbus A319 Captain continued descent towards destination Tunis at high speed with the landing runway in sight well beyond the point where a stabilised approach was possible. With 5nm to go, airspeed was over 100 KIAS above the applicable VApp and the aircraft was descending at over 4000fpm with flaps zero. EGPWS activations for Sink Rate, PULL UP and Too Low Terrain apparently went unnoticed but at 400 feet agl, ATC granted a crew request for a 360° turn. The subsequent approach/landing was without further event. Investigation attributed the event to “sloppy CRM”.

guid: https://skybrary.aero/accidents-and-incidents/a319-vicinity-tunis-tunisia-2012 uri: https://skybrary.aero/accidents-and-incidents/a319-vicinity-tunis-tunisia-2012 title: Vehicle / B738, Brisbane Australia, 2006 link: https://skybrary.aero/accidents-and-incidents/vehicle-b738-brisbane-australia-2006 description:

On 21 April 2006, a Boeing 737-800 cleared to take off from Brisbane began to do so whilst a vehicle was crossing the same runway in accordance with an ATC clearance issued on a different frequency. The aircraft crew saw the vehicle as they accelerated but decided that it would be clear by the time they reached its position. The vehicle driver reported that he was still within the runway strip when the aircraft passed. Since the occurrence, the adoption at Brisbane of the ICAO recommended procedure of using one frequency for all runway occupancy is being “actively considered”.

guid: https://skybrary.aero/accidents-and-incidents/vehicle-b738-brisbane-australia-2006 uri: https://skybrary.aero/accidents-and-incidents/vehicle-b738-brisbane-australia-2006 title: B738, Kingston Jamaica, 2009 link: https://skybrary.aero/accidents-and-incidents/b738-kingston-jamaica-2009 description:

On 22 December 2009, the flight crew of an American Airlines Boeing 737-800 made a long landing at Kingston at night in heavy rain and with a significant tailwind component and their aircraft overran the end of the runway at speed and was destroyed beyond repair. There was no post-crash fire and no fatalities, but serious injuries were sustained by 14 of the 154 occupants. The accident was attributed almost entirely to various actions and inactions of the crew. Damage to the aircraft after the overrun was exacerbated by the absence of a RESA.

guid: https://skybrary.aero/accidents-and-incidents/b738-kingston-jamaica-2009 uri: https://skybrary.aero/accidents-and-incidents/b738-kingston-jamaica-2009 title: B738, Perth Australia, 2008 link: https://skybrary.aero/accidents-and-incidents/b738-perth-australia-2008 description:

On 9 May 2008, a Boeing 737-800 made a low go around at Perth in good daylight visibility after not approaching with regard to the temporarily displaced runway threshold. A second approach was similarly flown and, having observed a likely landing on the closed runway section, ATC instructed a go around. However, instead, the aircraft flew level at a low height over the closed runway section before eventually touching down just beyond the displaced threshold. The Investigation found that runway closure markings required in Australia were contrary to ICAO Recommendations and not conducive to easy recognition when on final approach.

guid: https://skybrary.aero/accidents-and-incidents/b738-perth-australia-2008 uri: https://skybrary.aero/accidents-and-incidents/b738-perth-australia-2008 title: Vehicles / B737, Toronto Canada, 2008 link: https://skybrary.aero/accidents-and-incidents/vehicles-b737-toronto-canada-2008 description:

On 29 July 2008, a Boeing 737-700 taking off from Toronto in accordance with its TWR clearance was about a third of the way down the runway when three vehicles, which had previously been cleared to enter the same runway by a GND controller were seen. The aircraft became airborne approximately 760 metres from the vehicles.

guid: https://skybrary.aero/accidents-and-incidents/vehicles-b737-toronto-canada-2008 uri: https://skybrary.aero/accidents-and-incidents/vehicles-b737-toronto-canada-2008 title: A342, Perth Australia, 2005 link: https://skybrary.aero/accidents-and-incidents/a342-perth-australia-2005 description:

On 24 April 2005, an Airbus A340-200 landed short of the temporarily displaced runway threshold at Perth in good daylight visibility despite their prior awareness that there was such a displacement. The Investigation concluded that the crew had failed to correctly identify the applicable threshold markings because the markings provided were insufficiently clear to them and probably also because of the inappropriately low intensity setting of the temporary PAPI. No other Serious Incidents were reported during the same period of runway works.

guid: https://skybrary.aero/accidents-and-incidents/a342-perth-australia-2005 uri: https://skybrary.aero/accidents-and-incidents/a342-perth-australia-2005 title: B738, Paris CDG France, 2008 link: https://skybrary.aero/accidents-and-incidents/b738-paris-cdg-france-2008 description:

On 16 August 2008, an AMC Airlines Boeing 737-800 inadvertently began a night take off from an intersection on runway 27L at Paris CDG which left insufficient take off distance available before the end of the temporarily restricted runway length. It collided with and damaged obstructions related to construction works in progress on the closed section of the runway but sustained only minor damage and completed the intended flight to Luxor. The context for the flight crew error was identified as inadequate support from the Operator and inadequate airport risk assessment for operations with a reduced runway length.

guid: https://skybrary.aero/accidents-and-incidents/b738-paris-cdg-france-2008 uri: https://skybrary.aero/accidents-and-incidents/b738-paris-cdg-france-2008 title: A30B, Bratislava Slovakia, 2012 link: https://skybrary.aero/accidents-and-incidents/a30b-bratislava-slovakia-2012 description:

On 16 November 2012, an Air Contractors Airbus A300 departed the left the side of the landing runway at Bratislava after an abnormal response to directional control inputs. Investigation found that incorrect and undetected re-assembly of the nose gear torque links had led to the excursion and that absence of clear instructions in maintenance manuals, since rectified, had facilitated this. It was also considered that the absence of any regulation requiring equipment in the vicinity of the runway to be designed to minimise potential damage to aircraft departing the paved surface had contributed to the damage caused by the accident.

guid: https://skybrary.aero/accidents-and-incidents/a30b-bratislava-slovakia-2012 uri: https://skybrary.aero/accidents-and-incidents/a30b-bratislava-slovakia-2012 title: A320, vicinity Tel Aviv Israel, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tel-aviv-israel-2012 description:

On 3 April 2012, the crew of an Air France Airbus A320 came close to loosing control of their aircraft after accepting, inadequately preparing for and comprehensively mismanaging it during an RNAV VISUAL approach at Tel Aviv and during the subsequent attempt at a missed approach. The Investigation identified significant issues with crew understanding of automation - especially in respect of both the use of FMS modes and operations with the AP off but the A/T on - and highlighted the inadequate provision by the aircraft operator of both procedures and pilot training for this type of approach.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tel-aviv-israel-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-tel-aviv-israel-2012 title: A318/B738, Nantes France, 2010 link: https://skybrary.aero/accidents-and-incidents/a318b738-nantes-france-2010 description:

On 25 May 2010 an Air France Airbus A318 making an automatic landing off an ILS Cat 2 approach at Nantes experienced interference with the ILS LOC signal caused by a Boeing 737-800 which was departing from the same runway but early disconnection of the AP removed any risk of un-correctable directional control problems during the landing roll. Both aircraft were operating in accordance with their ATC clearances. Investigation attributed the conflict to the decision of TWR not to instruct the A318 to go around and because of diminished situational awareness.

guid: https://skybrary.aero/accidents-and-incidents/a318b738-nantes-france-2010 uri: https://skybrary.aero/accidents-and-incidents/a318b738-nantes-france-2010 title: A319/A319, en-route, South west of Basle-Mulhouse France, 2010 link: https://skybrary.aero/accidents-and-incidents/a319a319-en-route-south-west-basle-mulhouse-france-2010 description:

On 29 June 2010, an Easyjet Switzerland Airbus A319 inbound to Basle-Mulhouse and an Air France Airbus A319 outbound from Basle-Mulhouse lost separation after an error made by a trainee APP controller under OJTI supervision during procedural service. The outcome was made worse by the excessive rate of climb of the Air France aircraft approaching its cleared level and both an inappropriate response to an initial preventive TCAS RA and a change of track during the ensuing short sequence of RAs by the Training Captain in command of and flying the Easyjet aircraft attributed by him to his situational ‘anxiety’.

guid: https://skybrary.aero/accidents-and-incidents/a319a319-en-route-south-west-basle-mulhouse-france-2010 uri: https://skybrary.aero/accidents-and-incidents/a319a319-en-route-south-west-basle-mulhouse-france-2010 title: A319, Casablanca Morocco, 2011 link: https://skybrary.aero/accidents-and-incidents/a319-casablanca-morocco-2011 description:

On 8 August 2011 an Air France Airbus A319 crew failed to correctly identify the runway on which they were cleared to land off a visual approach at Casablanca and instead landed on the parallel runway. ATC, who had already cleared another aircraft to cross the same runway, did not notice until this other aircraft crew, who had noticed the apparently abnormal position of the approaching aircraft and remained clear of the runway as a precaution, advised what had happened. Investigation was hindered by the stated perception of the Air France PIC that the occurrence was not a Serious Incident.

guid: https://skybrary.aero/accidents-and-incidents/a319-casablanca-morocco-2011 uri: https://skybrary.aero/accidents-and-incidents/a319-casablanca-morocco-2011 title: MD83, en route, near Gossi Mali, 2014 link: https://skybrary.aero/accidents-and-incidents/md83-en-route-near-gossi-mali-2014 description:

In the early hours of 24 July 2014, a Boeing MD 83 being operated for Air Algérie by Spanish ACMI operator Swiftair crashed in northern Mali whilst en route from Ouagadougou, Burkina Faso to Algiers and in the vicinity of severe convective actvity associated with the ICTZ. Initial findings of the continuing Investigation include that after indications of brief but concurrent instability in the function of both engines, the thrust to both simultaneously reduced to near idle and control of the aircraft was lost. High speed terrain impact followed and the aircraft was destroyed and all 116 occupants killed.

guid: https://skybrary.aero/accidents-and-incidents/md83-en-route-near-gossi-mali-2014 uri: https://skybrary.aero/accidents-and-incidents/md83-en-route-near-gossi-mali-2014 title: PRM1, vicinity Annemasse France, 2013 link: https://skybrary.aero/accidents-and-incidents/prm1-vicinity-annemasse-france-2013 description:

On 4 March 2013, a Beechcraft Premier 1A stalled and crashed soon after take off from Annemasse. The Investigation concluded that the loss of control was attributable to taking off with frozen deposits on the wings which the professional pilot flying the privately-operated aircraft had either not been aware of or had considered insignificant. It was found that the aircraft had been parked outside overnight and that overnight conditions, particularly the presence of a substantial quantity of cold-soaked fuel, had been conducive to the formation of frost and that no airframe de/anti icing facilities had been available at Annemasse.

guid: https://skybrary.aero/accidents-and-incidents/prm1-vicinity-annemasse-france-2013 uri: https://skybrary.aero/accidents-and-incidents/prm1-vicinity-annemasse-france-2013 title: A320, en-route, north of Swansea UK, 2012 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-swansea-uk-2012 description:

On 7 September 2012, the crew of an Aer Lingus Airbus A320-200 mis-set their descent clearance. When discovering this as the actual cleared level was being approached, the AP was disconnected and the unduly abrupt control input made led to an injury to one of the cabin crew. The original error was attributed to ineffective flight deck monitoring and the inappropriate corrective control input to insufficient appreciation of the aerodynamic handling aspects of flight at high altitude. A Safety Recommendation to the Operator to review relevant aspects of its flight crew training was made.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-swansea-uk-2012 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-swansea-uk-2012 title: CRJ7, Lorient France, 2012 link: https://skybrary.aero/accidents-and-incidents/crj7-lorient-france-2012 description:

On 16 October 2012, a Brit Air Bombardier CRJ 700 landed long on a wet runway at Lorient and overran the runway. The aircraft sustained significant damage but none of the occupants were injured. The Investigation attributed the accident to poor decision making by the crew whilst showing signs of complacency and fatigue and failing to maintain a sterile flight deck or go around when the approach became unstable. A context of deficiencies at the airport and at the Operator was also detailed and it was concluded that aquaplaning had occurred.

guid: https://skybrary.aero/accidents-and-incidents/crj7-lorient-france-2012 uri: https://skybrary.aero/accidents-and-incidents/crj7-lorient-france-2012 title: A320, São Paulo Congonhas Brazil, 2007 link: https://skybrary.aero/accidents-and-incidents/a320-sao-paulo-congonhas-brazil-2007 description:

On 17 July 2007, the commander of a TAM Airlines Airbus A320 being operated with one thrust reverser locked out was unable to stop the aircraft leaving the landing runway at Congonhas at speed and it hit buildings and was destroyed by the impact and fire which followed killing all on board and others on the ground. The investigation attributed the accident to pilot failure to realise that the thrust lever of the engine with the locked out reverser was above idle, which by design then prevented both the deployment of ground spoilers and the activation of the pre-selected autobrake.

guid: https://skybrary.aero/accidents-and-incidents/a320-sao-paulo-congonhas-brazil-2007 uri: https://skybrary.aero/accidents-and-incidents/a320-sao-paulo-congonhas-brazil-2007 title: S92, en-route, east of St John’s Newfoundland Canada, 2009 link: https://skybrary.aero/accidents-and-incidents/s92-en-route-east-st-johns-newfoundland-canada-2009 description:

On 12 March 2009, a Sikorsky S-92A crew heading offshore from St. John's, Newfoundland declared an emergency and began a return after total loss of main gear box oil pressure but lost control during an attempted ditching. The Investigation found that all oil had been lost after two main gear box securing bolts had sheared. It was noted that ambiguity had contributed to crew misdiagnosis the cause and that the ditching had been mishandled. Sea States beyond the capability of Emergency Flotation Systems and the limited usefulness of personal Supplemental Breathing Systems in cold water were identified as Safety Issues.

guid: https://skybrary.aero/accidents-and-incidents/s92-en-route-east-st-johns-newfoundland-canada-2009 uri: https://skybrary.aero/accidents-and-incidents/s92-en-route-east-st-johns-newfoundland-canada-2009 title: B772, en-route, near Hrabove Eastern Ukraine, 2014 link: https://skybrary.aero/accidents-and-incidents/b772-en-route-near-hrabove-eastern-ukraine-2014 description:

On 17 July 2014, ATC lost contact with a Malaysian Airlines Boeing 777-200 en route at FL330 and wreckage of the aircraft was subsequently found. An Investigation by the Dutch Transport Safety Board concluded that the aircraft had been brought down by an anti-aircraft missile fired from an area where an armed insurgency was in progress. It was also concluded that Ukraine already had sufficient reason to close the airspace involved as a precaution before the investigated event occurred and that none of the parties involved had recognised the risk posed to overflying civil aircraft by the armed conflict.

guid: https://skybrary.aero/accidents-and-incidents/b772-en-route-near-hrabove-eastern-ukraine-2014 uri: https://skybrary.aero/accidents-and-incidents/b772-en-route-near-hrabove-eastern-ukraine-2014 title: B739, en-route, east of Denver CO USA, 2012 link: https://skybrary.aero/accidents-and-incidents/b739-en-route-east-denver-co-usa-2012 description:

On 31 July 2012, a Boeing 737-900 struck a single large bird whilst descending to land at Denver in day VMC and passing approximately 6000 feet aal, sustaining damage to the radome, one pitot head and the vertical stabiliser. The flight crew declared an emergency and continued the approach with ATC assistance to an uneventful landing. The bird involved was subsequently identified as a White Faced Ibis, a species which normally has a weight around 500 gm but can exceptionally reach a weight of 700 gm. The hole made in the radome was 60 cm x 30 cm.

guid: https://skybrary.aero/accidents-and-incidents/b739-en-route-east-denver-co-usa-2012 uri: https://skybrary.aero/accidents-and-incidents/b739-en-route-east-denver-co-usa-2012 title: H25B, vicinity Owatonna MN USA, 2008 link: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-owatonna-mn-usa-2008 description:

On 31 July 2008, the crew of an HS125-800 attempted to reject a landing at Owatonna MN after a prior deployment of the lift dumping system but their aircraft overran the runway then briefly became airborne before crashing. The aircraft was destroyed and all 8 occupants were killed. The Investigation attributed the accident to poor crew judgement and general cockpit indiscipline in the presence of some fatigue and also considered that it was partly consequent upon the absence of any regulatory requirement for either pilot CRM training or operator SOP specification for the type of small aircraft operation being undertaken.

guid: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-owatonna-mn-usa-2008 uri: https://skybrary.aero/accidents-and-incidents/h25b-vicinity-owatonna-mn-usa-2008 title: A332, en-route, near Dar es Salaam Tanzania, 2012 link: https://skybrary.aero/accidents-and-incidents/a332-en-route-near-dar-es-salaam-tanzania-2012 description:

On 27 February 2012, the crew of an Airbus A330 en route at night and crossing the East African coast at FL360 encountered sudden violent turbulence as they flew into a convective cell not seen on their weather radar and briefly lost control as their aircraft climbed 2000 feet with resultant minor injuries to two occupants. The Investigation concluded that the isolated and rapidly developing cell had not been detected because of crew failure to make proper use of their weather radar, but noted that activation of flight envelope protection and subsequent crew action to recover control had been appropriate.

guid: https://skybrary.aero/accidents-and-incidents/a332-en-route-near-dar-es-salaam-tanzania-2012 uri: https://skybrary.aero/accidents-and-incidents/a332-en-route-near-dar-es-salaam-tanzania-2012 title: DHC6, en-route, Mount Elizabeth Antarctica, 2013 link: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-mount-elizabeth-antarctica-2013 description:

On 23 January 2013, a Canadian-operated DHC6 on day VFR positioning flight in Antarctica was found to have impacted terrain under power and whilst climbing at around the maximum rate possible. The evidence assembled by the Investigation indicated that this probably occurred following entry into IMC at an altitude below that of terrain in the vicinity having earlier set course en route direct to the intended destination. The aircraft was destroyed and there were no survivors.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-mount-elizabeth-antarctica-2013 uri: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-mount-elizabeth-antarctica-2013 title: E190, en route, Bwabwata National Park Namibia, 2013 link: https://skybrary.aero/accidents-and-incidents/e190-en-route-bwabwata-national-park-namibia-2013 description:

On 29 November 2013, an Embraer 190 Captain intentionally initiated a high speed descent from the previously-established FL380 cruise altitude after the First Officer left the flight deck and thereafter prevented him from re-entering. The descent was maintained to ground impact with the AP engaged using a final selected altitude below ground level. The Investigation noted that the Captain had been through some life experiences capable of having an effect on his state of mind but in the absence of any other evidence was unable establish any motive for suicide.|Day|VMC|1209|||Aircraft Operation||Locked Flight Deck Door|Procedural non compliance, Malicious Interference|Independent|Yes|Hull loss|No|||Most or all occupants|33||No|No|Aircraft Operation, Aircraft Airworthiness|FQMA|FNLU|||||||||Into terrain|Post Crash Fire||||||||||||No|Available but ineffective|Available but ineffective||||||||||||||||19457

guid: https://skybrary.aero/accidents-and-incidents/e190-en-route-bwabwata-national-park-namibia-2013 uri: https://skybrary.aero/accidents-and-incidents/e190-en-route-bwabwata-national-park-namibia-2013 title: A343, en-route, mid North Atlantic Ocean, 2011 link: https://skybrary.aero/accidents-and-incidents/a343-en-route-mid-north-atlantic-ocean-2011 description:

On 22 July 2011 an Air France A340-300 en route over the North Atlantic at FL350 in night IMC encountered moderate turbulence following "inappropriate use of the weather radar" which led to an overspeed annunciation followed by the aircraft abruptly pitching up and gaining over 3000 feet in less than a minute before control was regained and it was returned to the cleared level. The Investigation concluded that "the incident was due to inadequate monitoring of the flight parameters, which led to the failure to notice AP disengagement and the level bust, following a reflex action on the controls.”

guid: https://skybrary.aero/accidents-and-incidents/a343-en-route-mid-north-atlantic-ocean-2011 uri: https://skybrary.aero/accidents-and-incidents/a343-en-route-mid-north-atlantic-ocean-2011 title: JU52, en-route, west of Chur Switzerland, 2018 link: https://skybrary.aero/accidents-and-incidents/ju52-en-route-west-chur-switzerland-2018 description:

On 4 August 2018, a Junkers Ju-52 making a low level sightseeing flight through the Swiss Alps crashed killing all 20 occupants after control was lost when it stalled after encountering unexceptional windshear. The Investigation found that the pilots had created the conditions which led to the stall and then been unable to recover from it and concluded that the accident was a direct consequence of their risky behaviour. It found that such behaviour was common at the operator, that the operator was being managed without any regard to operational risk and that safety regulatory oversight had been systemically deficient.

guid: https://skybrary.aero/accidents-and-incidents/ju52-en-route-west-chur-switzerland-2018 uri: https://skybrary.aero/accidents-and-incidents/ju52-en-route-west-chur-switzerland-2018 title: A333, Sydney Australia, 2017 link: https://skybrary.aero/accidents-and-incidents/a333-sydney-australia-2017 description:

On 17 December 2017, it was discovered after completion of an Airbus A330-300 passenger flight from Sydney to Bejing that freight loading had not been correctly documented on the load and trim sheet presented to and accepted by the Captain and as a result, the aircraft had exceeded its certified MTOW on departure. The Investigation found that the overload finding had not been promptly reported or its safety significance appreciated, that the error had its origin in related verbal communications during loading and noted that the aircraft operator had since made a series of improvements to its freight loading procedures.

guid: https://skybrary.aero/accidents-and-incidents/a333-sydney-australia-2017 uri: https://skybrary.aero/accidents-and-incidents/a333-sydney-australia-2017 title: AT75, vicinity Manchester UK, 2016 link: https://skybrary.aero/accidents-and-incidents/at75-vicinity-manchester-uk-2016 description:

On 4 March 2016, the flight crew of an ATR72-500 decided to depart from Manchester without prior ground de/anti icing treatment judging it unnecessary despite the presence of frozen deposits on the airframe and from rotation onwards found that manual forward control column input beyond trim capability was necessary to maintain controlled flight. The aircraft was subsequently diverted. The Investigation found that the problem had been attributable to ice contamination on the upper surface of the horizontal tailplane. It was considered that the awareness of both pilots of the risk of airframe icing had been inadequate.

guid: https://skybrary.aero/accidents-and-incidents/at75-vicinity-manchester-uk-2016 uri: https://skybrary.aero/accidents-and-incidents/at75-vicinity-manchester-uk-2016 title: AT76, en-route, near Førde Airport Norway, 2016 link: https://skybrary.aero/accidents-and-incidents/at76-en-route-near-forde-airport-norway-2016 description:

On 14 November 2016, an ATR72-600 crew lost control at FL150 in severe icing conditions. Uncontrolled rolls and a 1,500 feet height loss followed during an apparent stall. After recovery, the Captain announced to the alarmed passengers that he had regained control and the flight was completed without further event. The Investigation found that the crew had been aware that they had encountered severe icing rather than the forecast moderate icing but had attempted to continue to climb which took the aircraft outside its performance limitations. The recovery from the stall was non-optimal and two key memory actions were overlooked.

guid: https://skybrary.aero/accidents-and-incidents/at76-en-route-near-forde-airport-norway-2016 uri: https://skybrary.aero/accidents-and-incidents/at76-en-route-near-forde-airport-norway-2016 title: CRJ2, Charleston WV USA, 2010 link: https://skybrary.aero/accidents-and-incidents/crj2-charleston-wv-usa-2010 description:

On 19 January 2010, PSA Airlines CRJ 200 began take off from Charleston with an incorrect flap setting. After late crew recognition, a rejected take off was commenced at V1+13KIAS and an overrun into the EMAS bed at approximately 50knots followed. It was noted that had the overrun occurred prior to installation of the EMAS bed, the aircraft would probably have run down the steep slope immediately after the then-available RESA. The flap setting error was attributed non-adherence to a sterile flight deck. The late reject decision to an  initial attempt to correct the flap error during the take off.

guid: https://skybrary.aero/accidents-and-incidents/crj2-charleston-wv-usa-2010 uri: https://skybrary.aero/accidents-and-incidents/crj2-charleston-wv-usa-2010 title: DH8C, Toronto Canada, 2019 link: https://skybrary.aero/accidents-and-incidents/dh8c-toronto-canada-2019 description:

On 10 May 2019, a Bombardier DHC8-300 taxiing in at Toronto at night was hit by a fuel tanker travelling at “approximately 25 mph” which failed to give way where a designated roadway crossed a taxiway causing direct crew and indirect passenger injuries and substantial damage. The Investigation attributed the collision to the vehicle driver’s limited field of vision in the direction of the aircraft coming and lack of action to compensate for this, noting the need for more effective driver vigilance with respect to aircraft right of way rules when crossing taxiways. The aircraft was declared beyond economic repair.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-toronto-canada-2019 uri: https://skybrary.aero/accidents-and-incidents/dh8c-toronto-canada-2019 title: CRJ2 / Vehicles, Montréal Canada, 2019 link: https://skybrary.aero/accidents-and-incidents/crj2-vehicles-montreal-canada-2019 description:

On 2 February 2019, a Bombardier CRJ200 narrowly avoided collision with part of a convoy of snowplough vehicles which entered the landing runway at Montreal without clearance less than 10 seconds before touchdown and begun to position on the centreline. The Investigation found that despite the prompt initiation of a go-around on sighting the vehicles, the aircraft was likely to have cleared them by less than 100 feet. A number of opportunities for improved ground vehicle movement procedures were identified and the incursion was seen as indicative of a general need to more effectively address this risk at Canadian airports.

guid: https://skybrary.aero/accidents-and-incidents/crj2-vehicles-montreal-canada-2019 uri: https://skybrary.aero/accidents-and-incidents/crj2-vehicles-montreal-canada-2019 title: A319 / WT9, vicinity Stuttgart Germany, 2017 link: https://skybrary.aero/accidents-and-incidents/a319-wt9-vicinity-stuttgart-germany-2017 description:

On 26 June 2017, an Airbus A319 which had just taken off from Stuttgart came into conflict in Class ‘D’ airspace with a VFR light aircraft crossing its track and when, at 1,200 feet agl, the TCAS RA to descend which resulted was followed, an EGPWS Mode 3 Alert was generated. Clear of Conflict was annunciated after 10 seconds and climb resumed. The Investigation concluded that the light aircraft pilot had failed to follow the clearance which had been accepted and had caused the flight path conflict which was resolved by the response of the A319 to the TCAS RA.

guid: https://skybrary.aero/accidents-and-incidents/a319-wt9-vicinity-stuttgart-germany-2017 uri: https://skybrary.aero/accidents-and-incidents/a319-wt9-vicinity-stuttgart-germany-2017 title: A321, Charlotte NC USA, 2015 link: https://skybrary.aero/accidents-and-incidents/a321-charlotte-nc-usa-2015 description:

On 15 August 2015, an Airbus A321 on approach to Charlotte commenced a go around but following a temporary loss of control as it did so then struck approach and runway lighting and the undershoot area sustaining a tail strike before climbing away. The Investigation noted that the 2.1g impact caused substantial structural damage to the aircraft and attributed the loss of control to a small microburst and the crew’s failure to follow appropriate and recommended risk mitigations despite clear evidence of risk given by the aircraft when it went around and available visually.

guid: https://skybrary.aero/accidents-and-incidents/a321-charlotte-nc-usa-2015 uri: https://skybrary.aero/accidents-and-incidents/a321-charlotte-nc-usa-2015 title: B738 / DV20, vicinity Reus Spain, 2019 link: https://skybrary.aero/accidents-and-incidents/b738-dv20-vicinity-reus-spain-2019 description:

On 12 May 2019, a Boeing 737-800 making its second procedural ILS approach to runway 25 at Reus came into conflict with an opposite direction light aircraft as the latter approached one of the designated VFR entry points having been instructed to remain well above the altitude which normally ensures separation of IFR and VFR traffic. The collision risk was resolved by TCAS RA promptly followed by the 737. The Investigation concluded that limiting the TWR radar display to the ATZ for controller training purposes had resulted in neither the trainee controller nor their supervisor being aware of the risk.

guid: https://skybrary.aero/accidents-and-incidents/b738-dv20-vicinity-reus-spain-2019 uri: https://skybrary.aero/accidents-and-incidents/b738-dv20-vicinity-reus-spain-2019 title: CL60, en-route, southwest of Shahr-e-Kord Iran, 2018 link: https://skybrary.aero/accidents-and-incidents/cl60-en-route-southwest-shahr-e-kord-iran-2018 description:

On 11 March 2018 an Unreliable Speed Alert occurred on a Bombardier Challenger, the Captain’s airspeed increasing whilst the First Officer’s decreased. The First Officer attempted to commence the corresponding drill but the Captain’s interruptions prevented this and a (false) overspeed warning followed. The Captain’s response to both alerts was to reduce thrust which led to a Stall Warning followed, after no response, by stick pusher activation which was repeatedly opposed by the Captain despite calls to stop from the First Officer. The stalled condition continued for almost five minutes until a 30,000 feet descent was terminated by terrain impact.

guid: https://skybrary.aero/accidents-and-incidents/cl60-en-route-southwest-shahr-e-kord-iran-2018 uri: https://skybrary.aero/accidents-and-incidents/cl60-en-route-southwest-shahr-e-kord-iran-2018 title: A319, Nice France, 2019 link: https://skybrary.aero/accidents-and-incidents/a319-nice-france-2019 description:

On 29 August 2019, an Airbus A319 crew used more runway than expected during a reduced thrust takeoff from Nice, although not enough to justify increasing thrust. It was subsequently found that an identical error made by both pilots when independently calculating takeoff performance data for the most limiting runway intersection had resulted in use of data for a less limiting intersection than the one eventually used. The Investigation concluded that the only guaranteed way to avoid such an error would be an automatic cross check, a system upgrade which was not possible on the particular aircraft involved.

guid: https://skybrary.aero/accidents-and-incidents/a319-nice-france-2019 uri: https://skybrary.aero/accidents-and-incidents/a319-nice-france-2019 title: B738, vicinity Bristol UK, 2019 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-bristol-uk-2019 description:

On 1 June 2019, a Boeing 737-800 was instructed to go around after it was observed to be significantly below the vertical profile for its RNAV approach as it reached the procedure minimum descent altitude. Having then climbed less than 300 feet, the aircraft began to descend, reaching 457 feet agl before resuming its climb. The Investigation found that the terrain proximity on approach followed a failure to discontinue a comprehensively unstable approach and the terrain proximity episode during the go around was due to continued following of the Flight Director which was providing guidance based on incorrect mode selections.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-bristol-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-bristol-uk-2019 title: B739, Kathmandu Nepal, 2018 link: https://skybrary.aero/accidents-and-incidents/b739-kathmandu-nepal-2018 description:

On 19 April 2018, a Boeing 737-900 made a high speed rejected takeoff at Kathmandu in response to a configuration warning and overran the runway without serious consequences. The Investigation found that when a false Takeoff Configuration Warning caused by an out of adjustment switch had been annunciated just after V1, the Captain had decided to reject the takeoff because of concerns about the local terrain and locally adverse weather. It was noted that the aircraft operator did not provide criteria for rejecting takeoff up to or above the 80 knot crosscheck but that the Boeing reference QRH did so.

guid: https://skybrary.aero/accidents-and-incidents/b739-kathmandu-nepal-2018 uri: https://skybrary.aero/accidents-and-incidents/b739-kathmandu-nepal-2018 title: A321, vicinity London Gatwick, UK 2020 link: https://skybrary.aero/accidents-and-incidents/a321-vicinity-london-gatwick-uk-2020 description:

On 26 February 2020, after a difficult Airbus A321 left engine first flight of the day start, the same happened on the third sector with en-route engine abnormalities then affecting both engines. With no fault found during post flight maintenance inspections and despite similar engine starting problems, both engines then malfunctioned after takeoff from Gatwick. A MAYDAY return followed. Investigation found that the cause was fuel system contamination by addition of approximately 38 times the correct quantity of biocide during earlier scheduled maintenance and that the release of the aircraft to service for the flight had followed inadequate troubleshooting action.

guid: https://skybrary.aero/accidents-and-incidents/a321-vicinity-london-gatwick-uk-2020 uri: https://skybrary.aero/accidents-and-incidents/a321-vicinity-london-gatwick-uk-2020 title: A320 / B738, en-route, north northwest of Sofia Bulgaria, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-b738-en-route-north-northwest-sofia-bulgaria-2016 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a320-b738-en-route-north-northwest-sofia-bulgaria-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-b738-en-route-north-northwest-sofia-bulgaria-2016 title: L410, Dubrovnik Croatia, 2018 link: https://skybrary.aero/accidents-and-incidents/l410-dubrovnik-croatia-2018 description:

On 29 November 2018, a Let 410 landed on a temporarily closed section of the runway at Dubrovnik after a visual approach in benign weather conditions. The Investigation found that the flight crew had not carried out a sufficient pre-flight review of current and available information about a major multi-phase runway reconstruction there which they were familiar with. The opportunity for better advance and real time communication with aircraft operators and their flight crew and the benefit of the recommended ‘X’ marking at the beginning of any temporarily closed part of a runway, omitted in this case, was noted.

guid: https://skybrary.aero/accidents-and-incidents/l410-dubrovnik-croatia-2018 uri: https://skybrary.aero/accidents-and-incidents/l410-dubrovnik-croatia-2018 title: IL76, Yerevan Armenia, 2019 link: https://skybrary.aero/accidents-and-incidents/il76-yerevan-armenia-2019 description:

On 16 May 2019, an Ilyushin Il-76 overran the end of the landing runway at Yerevan after completing an ILS approach because the crew hadn’t realised until it was too late to stop that the available landing distance was reduced at the far end of the runway. The Investigation noted that it would have been possible to stop the aircraft in the distance available and attributed the lack of flight crew awareness to a combination of their own lack of professionalism and that exhibited by the Dispatcher and to the inadequacy and lack of clarity in the NOTAM communications advising the change.

guid: https://skybrary.aero/accidents-and-incidents/il76-yerevan-armenia-2019 uri: https://skybrary.aero/accidents-and-incidents/il76-yerevan-armenia-2019 title: A320, Pristina Kosovo, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-pristina-kosovo-2017 description:

On 1 December 2017, an Airbus A320 made an unintentional - and unrecognised - hard landing at Pristina. As the automated system for alerting outside-limits hard landings was only partially configured and output from the sole available channel was not available, the aircraft continued in service for a further eight sectors before an exceedance was confirmed and the aircraft grounded. The Investigation noted that whilst the aircraft Captain is responsible for recording potential hard landings, the aircraft operator involved should ensure that at least one of the available automated alerting channels is always functional in support of crew subjective judgement.

guid: https://skybrary.aero/accidents-and-incidents/a320-pristina-kosovo-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-pristina-kosovo-2017 title: A320, Raipur India, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-raipur-india-2016 description:

On 14 December 2016, an Airbus A320 made a 2.5g initial runway contact when landing at Raipur after the trainee First Officer failed to flare the aircraft adequately and the Training Captain took over too late to prevent a bounce followed by a 3.2g final touchdown. The Investigation found that despite the Training Captain’s diligent coaching, the First Officer had failed to respond during the final stages of the approach and that the takeover of control should have occurred earlier so that the mishandled final stage of the approach could have been discontinued and go around flown.

guid: https://skybrary.aero/accidents-and-incidents/a320-raipur-india-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-raipur-india-2016 title: A388, vicinity Moscow Domodedovo Russia, 2017 link: https://skybrary.aero/accidents-and-incidents/a388-vicinity-moscow-domodedovo-russia-2017 description:

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.

guid: https://skybrary.aero/accidents-and-incidents/a388-vicinity-moscow-domodedovo-russia-2017 uri: https://skybrary.aero/accidents-and-incidents/a388-vicinity-moscow-domodedovo-russia-2017 title: A320, vicinity Jaipur India, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-jaipur-india-2016 description:

On 27 February 2016, an Airbus A320 making an into-sun visual approach to Jaipur in hazy conditions lined up on a road parallel to the intended landing runway and continued descent until an EGPWS ‘TOO LOW TERRAIN’ Alert occurred at 200 feet agl upon which a go-around was initiated. The Investigation found that although the First Officer had gained visual reference with both road and runway at 500 feet agl, the Captain had seen only the road and continued asking the First Officer to continue descent towards it despite the First Officer’s attempts to alert him to his error.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-jaipur-india-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-jaipur-india-2016 title: CVLP, en-route, east of Miami Opa Locka USA, 2019 link: https://skybrary.aero/accidents-and-incidents/cvlp-en-route-east-miami-opa-locka-usa-2019 description:

On 8 February 2019, a Convair C131 climbing out of Nassau experienced a right engine propeller control malfunction. The Captain was able to stabilise power and continued the flight to Miami. As descent began, the same engine malfunctioned and was shut down but the left engine then also malfunctioned and, after an emergency declaration, a mishandled ditching followed. This wrecked the aircraft and only the First Officer survived, seriously injured. The Investigation noted that related engine malfunction on the outbound flight had not been recorded or investigated. No wreckage recovery was attempted so engine failure causes were not determined.

guid: https://skybrary.aero/accidents-and-incidents/cvlp-en-route-east-miami-opa-locka-usa-2019 uri: https://skybrary.aero/accidents-and-incidents/cvlp-en-route-east-miami-opa-locka-usa-2019 title: MD83 / AT76, Isfahan Iran, 2018 link: https://skybrary.aero/accidents-and-incidents/md83-at76-isfahan-iran-2018 description:

On 21 January 2018, a McDonnell Douglas MD-83 which had just landed on one of the two parallel runways at Isfahan, entered the roll out end of the other one and began taxiing on it in the opposite direction to an ATR72-600 which was about to touch down at the other end of the same runway. The Investigation found that the MD83 had failed to follow its taxi clearance but also that the TWR controller involved had failed to instruct the conflicting ATR-72 to go around, a requirement that was not optional despite the 4397 metre runway length.

guid: https://skybrary.aero/accidents-and-incidents/md83-at76-isfahan-iran-2018 uri: https://skybrary.aero/accidents-and-incidents/md83-at76-isfahan-iran-2018 title: B737, en-route, west southwest of Pensacola FL USA, 2016 link: https://skybrary.aero/accidents-and-incidents/b737-en-route-west-southwest-pensacola-fl-usa-2016 description:

On 27 August 2016, debris from sudden uncontained failure of the left CFM56-7B engine of a Boeing 737-700 climbing through approximately FL 310 west southwest of Pensacola in day VMC penetrated the fuselage barrel and caused a rapid depressurisation. An emergency descent and a diversion to Pensacola followed without further event. The Investigation found that collateral damage had followed low-cycle fatigue cracking of a single fan blade due to a previously unrecognised weakness in the design of this on-condition component which, because it had not been detected during the engine certification process, meant its consequences “could not have been predicted”.

guid: https://skybrary.aero/accidents-and-incidents/b737-en-route-west-southwest-pensacola-fl-usa-2016 uri: https://skybrary.aero/accidents-and-incidents/b737-en-route-west-southwest-pensacola-fl-usa-2016 title: A321, Glasgow UK, 2019 link: https://skybrary.aero/accidents-and-incidents/a321-glasgow-uk-2019 description:

On 24 November 2019, as an Airbus A321 taking off from the 2665 metre-long runway 05 at Glasgow approached the calculated V1 with the flex thrust they had set, the aircraft was not accelerating as expected and they applied TOGA thrust. This resulted in the aircraft becoming airborne with less than 400 metres of runway remaining. The Investigation confirmed what the crew had subsequently discovered for themselves - that they had both made an identical error in their independent EFB performance calculations which the subsequent standard procedures and checks had not detected. The operator is reviewing its related checking procedures.

guid: https://skybrary.aero/accidents-and-incidents/a321-glasgow-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/a321-glasgow-uk-2019 title: MD82, Tarbes France, 2018 link: https://skybrary.aero/accidents-and-incidents/md82-tarbes-france-2018 description:

On 16 January 2018, a McDonnell Douglas MD-82 attempting to land at Tarbes was subject to gross mishandling by the crew and the approach became unstable. A subsequent low level go-around attempt was then made without setting sufficient thrust which resulted in sustained and close proximity to terrain at an airspeed close to stall entry before the required thrust was eventually applied. The Investigation was hindered by non-reporting of the event but was able to conclude that multiple pilot errors in a context of poor crew coordination during the approach had caused confusion when the go around was initiated.

guid: https://skybrary.aero/accidents-and-incidents/md82-tarbes-france-2018 uri: https://skybrary.aero/accidents-and-incidents/md82-tarbes-france-2018 title: B773, Hong Kong China, 2017 link: https://skybrary.aero/accidents-and-incidents/b773-hong-kong-china-2017 description:

On 28 April 2017, a Boeing 777-300 made a 3.2g manual landing at Hong Kong, which was not assessed as such by the crew and only discovered during routine flight data analysis, during a Final Line Check flight for a trainee Captain. The Investigation noted that the landing technique used was one of the reasons the Check was failed. The trainee had been an experienced 737 Captain with the operator who had returned from 777 type conversion training with another airline and was required to undertake line training to validate his command status in accordance with local requirements.

guid: https://skybrary.aero/accidents-and-incidents/b773-hong-kong-china-2017 uri: https://skybrary.aero/accidents-and-incidents/b773-hong-kong-china-2017 title: B788, en-route, southwest of Kansai Japan, 2019 link: https://skybrary.aero/accidents-and-incidents/b788-en-route-southwest-kansai-japan-2019 description:

On 29 March 2019, both engines of a Boeing 787-8 on descent to Kansai malfunctioned in quick succession causing auto ignition to be triggered by sub-idle engine rpm but thereafter, sufficient thrust was available to safely complete the flight just under half an hour after the dual malfunction. The Investigation found that the cause of these malfunctions had been contamination of the fuel system with abnormally large concentrations of residue which could be reliably traced to a routinely applied biocide and which had solidified and intermittently impeded the transfer of fuel from the tanks to the engines.

guid: https://skybrary.aero/accidents-and-incidents/b788-en-route-southwest-kansai-japan-2019 uri: https://skybrary.aero/accidents-and-incidents/b788-en-route-southwest-kansai-japan-2019 title: B763, en-route, east southeast of Houston TX USA, 2019 link: https://skybrary.aero/accidents-and-incidents/b763-en-route-east-southeast-houston-tx-usa-2019 description:

On 23 February 2019, a Boeing 767-300 transitioned suddenly from a normal descent towards Houston into a steep dive and high speed terrain impact followed. The Investigation found that after neither pilot had noticed the First Officer’s inadvertent selection of go around mode during automated flight, the First Officer had then very quickly responded with an increasingly severe manual pitch-down, possibly influenced by a somatogravic illusion. He was found to have had a series of short air carrier employments terminating after failure to complete training, had deliberately and repeatedly sought to conceal this history and lacked sufficient aptitude and competency.

guid: https://skybrary.aero/accidents-and-incidents/b763-en-route-east-southeast-houston-tx-usa-2019 uri: https://skybrary.aero/accidents-and-incidents/b763-en-route-east-southeast-houston-tx-usa-2019 title: AT76, vicinity Al Hoceima Morocco, 2018 link: https://skybrary.aero/accidents-and-incidents/at76-vicinity-al-hoceima-morocco-2018 description:

On 9 July 2018, an ATR 72-600 continued a non-precision approach to Al Hoceima below the procedure MDA without obtaining visual reference and subsequently struck the sea surface twice, both times with a vertical acceleration exceeding structural limits before successfully climbing away and diverting to Nador having reported a bird strike. The Investigation attributed the accident to the Captain’s repeated violation of operating procedures which included another descent below MDA without visual reference the same day and the intentional deactivation of the EGPWS without valid cause. There was significant fuselage structure and landing gear damage but no occupant injuries.

guid: https://skybrary.aero/accidents-and-incidents/at76-vicinity-al-hoceima-morocco-2018 uri: https://skybrary.aero/accidents-and-incidents/at76-vicinity-al-hoceima-morocco-2018 title: BE20, vicinity Gillam Canada, 2019 link: https://skybrary.aero/accidents-and-incidents/be20-vicinity-gillam-canada-2019 description:

On 24 April 2019, the engine of a Beech B200 en-route from Winnipeg to Churchill at FL 250 failed due to fuel exhaustion and the crew realised that they had forgotten to refuel before departure. An emergency was declared and a diversion to the nearest available airport was commenced but the right engine later failed for the same reason leaving them with no option but to land on a frozen lake surface. The Investigation concluded that confusion as to relative responsibility between the trainee Captain and the supervising pilot-in-command were central to the failure to refuel prior to departure as intended.

guid: https://skybrary.aero/accidents-and-incidents/be20-vicinity-gillam-canada-2019 uri: https://skybrary.aero/accidents-and-incidents/be20-vicinity-gillam-canada-2019 title: B773, Mauritius, 2018 link: https://skybrary.aero/accidents-and-incidents/b773-mauritius-2018 description:

On 16 September 2018, a Boeing 777-300 was beginning its takeoff from Mauritius when an inadvertently unsecured cabin service cart left its stowage in the forward galley area and travelled at increasing speed towards the rear of the cabin injuring several passengers before it stopped after meeting an empty seat towards the rear of the cabin. The Investigation noted that cabin crew late awareness of an abnormal aircraft configuration and its consequences had led to them generally prioritising service delivery over safety procedures prior to takeoff with this then leading to an overlooked safety task not being detected.

guid: https://skybrary.aero/accidents-and-incidents/b773-mauritius-2018 uri: https://skybrary.aero/accidents-and-incidents/b773-mauritius-2018 title: A319, vicinity Paris CDG, France 2014 link: https://skybrary.aero/accidents-and-incidents/a319-vicinity-paris-cdg-france-2014 description:

On 12 March 2014, an Airbus A319 left engine stopped without any apparent cause on approach to Paris CDG. The crew then started the APU which also stopped. The Investigation found that the cause was engine and APU fuel starvation caused by non-identification of a recurring intermittent malfunction in the fuel quantity indicating system because of a combination of factors including crew failure to record fuel status in line with clear instructions and an inadequate maintenance troubleshooting manual. An inadequately-written abnormal crew drill and the crew’s inadequate fuel system knowledge then resulted in the fuel crossfeed valve not being opened.

guid: https://skybrary.aero/accidents-and-incidents/a319-vicinity-paris-cdg-france-2014 uri: https://skybrary.aero/accidents-and-incidents/a319-vicinity-paris-cdg-france-2014 title: A320, London Stansted UK, 2019 link: https://skybrary.aero/accidents-and-incidents/a320-london-stansted-uk-2019 description:

On 1 March 2019, an Airbus A320 left engine suffered a contained failure soon after takeoff thrust was set for a night departure from London Stansted but despite the absence of an instruction to cabin crew to begin an evacuation, they did so anyway just before the aircraft was going to be taxied clear of the runway with the Captain only aware when passengers were seen outside the aircraft. The Investigation found that an evacuation had been ordered by the senior member of the cabin crew after she was “overwhelmed” by the situation and believed her team members were “scared”.

guid: https://skybrary.aero/accidents-and-incidents/a320-london-stansted-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/a320-london-stansted-uk-2019 title: A320, vicinity Birmingham UK, 2019 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-birmingham-uk-2019 description:

On 26 August 2019, an Airbus A320 attempted two autopilot-engaged non-precision approaches at Birmingham in good weather before a third one was successful. Both were commenced late and continued when unstable prior to eventual go-arounds, for one of which the aircraft was mis-configured causing an ‘Alpha Floor’ protection activation. A third non-precision approach was then completed without further event. The Investigation noted an almost identical event involving the same operator four months later, observing that all three discontinued approaches appeared to have originated in confusion arising from a slight difference between the procedures of the aircraft operator and AIP plates.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-birmingham-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-birmingham-uk-2019 title: A320, vicinity London Heathrow UK, 2019 link: https://skybrary.aero/accidents-and-incidents/a320-vicinity-london-heathrow-uk-2019 description:

On 23 September 2019, the flight crew of an Airbus A320 on approach to London Heathrow detected strong acrid fumes on the flight deck and after donning oxygen masks completed the approach and landing, exited the runway and shut down on a taxiway. After removing their masks, one pilot became incapacitated and the other unwell and both were taken to hospital. The other occupants, all unaffected, were disembarked to buses. The very comprehensive investigation was unable to establish the origin of the fumes but did identify a number of circumstantial factors which corresponded to those identified in previous similar events.

guid: https://skybrary.aero/accidents-and-incidents/a320-vicinity-london-heathrow-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/a320-vicinity-london-heathrow-uk-2019 title: E190 / B738, Amsterdam Netherlands, 2018 link: https://skybrary.aero/accidents-and-incidents/e190-b738-amsterdam-netherlands-2018 description:

On 27 July 2018, Amsterdam ATC cleared a Boeing 737-800 to line up for departure from an intermediate taxiway but the 737 crew then heard the controller issue a takeoff clearance to an Embraer ERJ190 from the full length of the same runway. Having stopped past the holding point but clear of the actual runway and reported on the runway, they were then given a takeoff clearance, too, but held position. The 190 crew heard the 737 takeoff clearance and rejected their own takeoff, passing clear of the 737 at high speed. The Investigation suggested a review of intersection takeoffs.

guid: https://skybrary.aero/accidents-and-incidents/e190-b738-amsterdam-netherlands-2018 uri: https://skybrary.aero/accidents-and-incidents/e190-b738-amsterdam-netherlands-2018 title: B738, London Gatwick UK, 2020 link: https://skybrary.aero/accidents-and-incidents/b738-london-gatwick-uk-2020 description:

On 28 February 2020, a Boeing 737-800 taking off from the full length of the London Gatwick main runway, which is in excess of 3000 metres long, was observed to get airborne only 120 metres before the end of the paved surface. The Investigation found that the crew response when the automatic V1 and VR calls did not occur was unduly delayed with rotation only occurring at a much higher than normal speed. No system fault was subsequently found and it was concluded that the crew had most likely omitted to input these speeds to the FMC after calculation.

guid: https://skybrary.aero/accidents-and-incidents/b738-london-gatwick-uk-2020 uri: https://skybrary.aero/accidents-and-incidents/b738-london-gatwick-uk-2020 title: B789, Oslo Norway, 2018 link: https://skybrary.aero/accidents-and-incidents/b789-oslo-norway-2018 description:

On 18 December 2018, a Boeing 787-9 was instructed to taxi to a specified remote de-icing platform for de-icing prior to takeoff from Oslo. The aircraft collided with a lighting mast on the de-icing platform causing significant damage to both aircraft and mast. The Investigation found that in the absence of any published information about restricted aircraft use of particular de-icing platforms and any markings, lights, signage or other technical barriers to indicate to the crew that they had been assigned an incorrect platform, they had visually assessed the clearance as adequate. Relevant Safety Recommendations were made.

guid: https://skybrary.aero/accidents-and-incidents/b789-oslo-norway-2018 uri: https://skybrary.aero/accidents-and-incidents/b789-oslo-norway-2018 title: E195, Exeter UK, 2019 link: https://skybrary.aero/accidents-and-incidents/e195-exeter-uk-2019 description:

On 28 February 2019, an Embraer E195 abandoned takeoff from Exeter when fight deck fumes/smoke accompanied thrust applied against the brakes. When informed of similar conditions in the cabin, the Captain ordered an emergency evacuation. Some passengers using the overwing exits re-entered the cabin after becoming confused as to how to leave the wing. The Investigation attributed the fumes to an incorrectly-performed engine compressor wash arising in a context of poorly-managed maintenance and concluded that guidance on overwing exit use had been inadequate and that the 1.8 metre certification height limit for exits without evacuation slides should be reduced.

guid: https://skybrary.aero/accidents-and-incidents/e195-exeter-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/e195-exeter-uk-2019 title: A343, Bogotá Colombia, 2017 (2) link: https://skybrary.aero/accidents-and-incidents/a343-bogota-colombia-2017-2 description:

On 19 August 2017, an Airbus A340-300 encountered significant unforecast windshear on rotation for a maximum weight rated-thrust night takeoff from Bogotá and was unable to begin its climb for a further 800 metres during which angle of attack flight envelope protection was briefly activated. The Investigation noted the absence of a windshear detection system and any data on the prevalence of windshear at the airport as well as the failure of ATC to relay in English reports of conditions from departing aircraft received in Spanish. The aircraft operator subsequently elected to restrict maximum permitted takeoff weights from the airport.

guid: https://skybrary.aero/accidents-and-incidents/a343-bogota-colombia-2017-2 uri: https://skybrary.aero/accidents-and-incidents/a343-bogota-colombia-2017-2 title: B738, en-route, west of Bar Montenegro, 2019 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-west-bar-montenegro-2019 description:

On 13 February 2019, a Boeing 737-800 en-route over the southern Adriatic Sea unexpectedly encountered severe clear air turbulence and two unsecured cabin crew and some unsecured passengers were thrown against the cabin structure and sustained minor injuries. The Investigation found that the Captain had conducted the crew pre-flight briefing prior to issue of the significant weather chart applicable to their flight by which time severe turbulence due to mountain waves at right angles to an established jetstream not shown on the earlier chart used for the briefing was expected at a particular point on their route.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-west-bar-montenegro-2019 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-west-bar-montenegro-2019 title: CRJ7 / A319, Lyon Saint-Exupéry France, 2017 link: https://skybrary.aero/accidents-and-incidents/crj7-a319-lyon-saint-exupery-france-2017 description:

On 17 March 2017, a Bombardier CRJ 700 which had just landed on runway 35R at Lyon Saint-Exupéry was about to cross runway 35L as cleared when its crew saw the departing Airbus A319 on runway 35L accelerating towards their intended crossing position and braked to a stop before entering the runway. The Investigation found that both aircraft had complied with all instructions issued by the TWR controller and concluded that safety management processes at the airport were not commensurate with the incursion risk involved and had been unchanged since an almost identical incident a year previously.

guid: https://skybrary.aero/accidents-and-incidents/crj7-a319-lyon-saint-exupery-france-2017 uri: https://skybrary.aero/accidents-and-incidents/crj7-a319-lyon-saint-exupery-france-2017 title: E550, Paris Le Bourget France, 2017 link: https://skybrary.aero/accidents-and-incidents/e550-paris-le-bourget-france-2017 description:

On 27 November 2017, an Embraer EMB 550 crew ignored a pre-takeoff indication of an inoperative airframe ice protection system despite taxiing out and taking off in icing conditions. The flight proceeded normally until approach to Paris Le Bourget when the Captain was unable to flare for touchdown at the normal speed and a 4g runway impact which caused a main gear leg to pierce the wing followed. The Investigation found that the crew had failed to follow relevant normal and abnormal operating procedures and did not understand how flight envelope protection worked or why it had activated on approach.

guid: https://skybrary.aero/accidents-and-incidents/e550-paris-le-bourget-france-2017 uri: https://skybrary.aero/accidents-and-incidents/e550-paris-le-bourget-france-2017 title: E190, Nice France, 2017 link: https://skybrary.aero/accidents-and-incidents/e190-nice-france-2017 description:

On 6 November 2017, an Embraer E190 cleared for a normal visibility night takeoff at Nice began it on a parallel taxiway without ATC awareness until it had exceeded 80 knots when ATC noticed and a rejected takeoff was instructed and accomplished without any consequences. The Investigation found that although both pilots were familiar with Nice, their position monitoring relative to taxi clearance was inadequate and both had demonstrated a crucial lack of awareness of the colour difference between taxiway and runway lighting. Use of non-standard communications phraseology by both controllers and flight crew was also found to be contributory.

guid: https://skybrary.aero/accidents-and-incidents/e190-nice-france-2017 uri: https://skybrary.aero/accidents-and-incidents/e190-nice-france-2017 title: B735, vicinity Madrid Barajas Spain, 2019 link: https://skybrary.aero/accidents-and-incidents/b735-vicinity-madrid-barajas-spain-2019 description:

On 5 April 2019, a Boeing 737-500 crew declared an emergency shortly after departing Madrid Barajas after problems maintaining normal lateral, vertical or airspeed control of their aircraft in IMC. After two failed attempts at ILS approaches in unexceptional weather conditions, the flight was successfully landed at a nearby military airbase. The Investigation found that a malfunction which probably prevented use of the Captain’s autopilot found before departure was not documented until after the flight but could not find a technical explanation for inability to control the aircraft manually given that dispatch without either autopilot working is permitted.

guid: https://skybrary.aero/accidents-and-incidents/b735-vicinity-madrid-barajas-spain-2019 uri: https://skybrary.aero/accidents-and-incidents/b735-vicinity-madrid-barajas-spain-2019 title: A320, Calicut India, 2019 link: https://skybrary.aero/accidents-and-incidents/a320-calicut-india-2019 description:

On 20 June 2019, an Airbus A320 about to touchdown at night at Calicut drifted to the right once over the runway when the rain intensity suddenly increased and briefly left the runway before regaining it and completing the landing and taxi in. Runway edge lighting and the two main gear tyres were damaged. The Investigation attributed the excursion to loss of enough visual reference to maintain the centreline until touchdown followed by late recognition of the deviation and delayed response to it. The visibility reduction was considered to have created circumstances in which a go-around would have been advisable.

guid: https://skybrary.aero/accidents-and-incidents/a320-calicut-india-2019 uri: https://skybrary.aero/accidents-and-incidents/a320-calicut-india-2019 title: B737 / B738, vicinity Amsterdam Netherlands, 2018 link: https://skybrary.aero/accidents-and-incidents/b737-b738-vicinity-amsterdam-netherlands-2018 description:

On 29 March 2018, a Boeing 737-700 commenced a late go-around from landing at Amsterdam on a runway with an extended centreline which passed over another runway from which a Boeing 737-800 had already been cleared for takeoff. An attempt by the controller responsible for both aircraft to stop the departing aircraft failed because the wrong callsign was used, so low level divergent turns were given to both aircraft and 0.5nm lateral and 300 feet vertical separation was achieved. The Investigation concluded that the ATC procedure involved was potentially hazardous and made a safety recommendation that it should be withdrawn.

guid: https://skybrary.aero/accidents-and-incidents/b737-b738-vicinity-amsterdam-netherlands-2018 uri: https://skybrary.aero/accidents-and-incidents/b737-b738-vicinity-amsterdam-netherlands-2018 title: B735, en-route, north northwest of Jakarta Indonesia, 2021 link: https://skybrary.aero/accidents-and-incidents/b735-en-route-north-northwest-jakarta-indonesia-2021 description:

On 9 January 2021, a Boeing 737-500 was climbing though 10,700 feet less than five minutes after departing Jakarta in daylight when it began to descend at an increasing rate from which no recovery occurred and 23 seconds later was destroyed by sea surface impact killing all 62 occupants. The Investigation concluded that the departure from controlled flight was unintentional and the result of the pilots’ inattention to their primary flight instruments when, during a turn with the autopilot engaged, an autothrottle malfunction created apparently unrecognised thrust asymmetry which culminated in a wing drop and a consequent  loss of control.

guid: https://skybrary.aero/accidents-and-incidents/b735-en-route-north-northwest-jakarta-indonesia-2021 uri: https://skybrary.aero/accidents-and-incidents/b735-en-route-north-northwest-jakarta-indonesia-2021 title: A320, Lisbon Portugal, 2019 link: https://skybrary.aero/accidents-and-incidents/a320-lisbon-portugal-2019 description:

On 16 September 2019, an Airbus A320 departing Lisbon only became airborne 110 metres before the end of runway 21 and had a high speed rejected takeoff been required, it was likely to have overrun the runway. The Investigation found that both pilots had inadvertently calculated reduced thrust takeoff performance using the full 3705 metre runway length and then failed to identify their error before FMS entry. They also did not increase the thrust to TOGA on realising that the runway end was fast approaching. This was the operator’s third almost identical event at Lisbon in less than five months.

guid: https://skybrary.aero/accidents-and-incidents/a320-lisbon-portugal-2019 uri: https://skybrary.aero/accidents-and-incidents/a320-lisbon-portugal-2019 title: A388, en-route, southwest Greenland, 2017 link: https://skybrary.aero/accidents-and-incidents/a388-en-route-southwest-greenland-2017 description:

On 30 September 2017, an Airbus A380-800 en-route over Greenland suffered a sudden explosive uncontained failure of the number 4 engine shortly after thrust was increased to adjust the cruise level to FL 370. Following recovery of a crucial piece of ejected debris, the Investigation was able to determine that the failure was attributable to a specific type of fatigue failure within a titanium alloy used in the manufacture of the engine fan hub. This risk had not been identifiable during manufacture or in-service and had not been recognised by the engine manufacturer or during the engine certification process.

guid: https://skybrary.aero/accidents-and-incidents/a388-en-route-southwest-greenland-2017 uri: https://skybrary.aero/accidents-and-incidents/a388-en-route-southwest-greenland-2017 title: B738 / B738, Perth Australia, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-b738-perth-australia-2018 description:

On 28 April 2018, a Boeing 737-800 exited the landing runway at Perth and without clearance crossed a lit red stop bar protecting the other active runway as another 737 was accelerating for takeoff. This aircraft was instructed to stop due to a runway incursion ahead and passed 15 metres clear of the incursion aircraft which by then had also stopped. The Investigation concluded that, after failing to refer to the aerodrome chart, the Captain had mixed up two landing runway exits of which only one involved subsequently crossing the other active runway and decided the stop bar was inapplicable.

guid: https://skybrary.aero/accidents-and-incidents/b738-b738-perth-australia-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-b738-perth-australia-2018 title: A388, en-route, Wyoming USA, 2020 link: https://skybrary.aero/accidents-and-incidents/a388-en-route-wyoming-usa-2020 description:

On 2 February 2020, an Airbus A380 in the cruise at night at FL 330 encountered unforecast clear air turbulence with the seatbelt signs off and one unsecured passenger in a standard toilet compartment sustained a serious injury as a result. The Investigation noted that relevant airline policies and crew training had been in place but also observed a marked difference in the availability of handholds in toilet compartments provided for passengers with disabilities or other special needs and those in all other such compartments and made a corresponding safety recommendation to standardise and placard handhold provision in all toilet compartments.

guid: https://skybrary.aero/accidents-and-incidents/a388-en-route-wyoming-usa-2020 uri: https://skybrary.aero/accidents-and-incidents/a388-en-route-wyoming-usa-2020 title: B739, Paris CDG France, 2019 link: https://skybrary.aero/accidents-and-incidents/b739-paris-cdg-france-2019 description:

On 27 October 2019, an under-floor hold fire warning was annunciated in the flight deck of a Boeing 737-900 which had been pushed back at Paris CDG and was about to begin taxiing. Since there were no signs of fire in the passenger cabin or during an emergency services external inspection, a non-emergency disembarkation of all occupants was made. The hold concerned was then opened and fire damage sourced to the overheated lithium battery in a passenger wheelchair was discovered. The Investigation identified a number of weaknesses in both the applicable loading procedures and compliance with the ones in place.

guid: https://skybrary.aero/accidents-and-incidents/b739-paris-cdg-france-2019 uri: https://skybrary.aero/accidents-and-incidents/b739-paris-cdg-france-2019 title: A319, Helsinki Finland, 2018 link: https://skybrary.aero/accidents-and-incidents/a319-helsinki-finland-2018 description:

On 3 August 2018, smoke appeared and began to intensify in the passenger cabin but not the flight deck of an Airbus A319 taxiing for departure at Helsinki. Cabin crew notified the Captain who stopped the aircraft and sanctioned an emergency evacuation. This then commenced whilst the engines were still running and inadequate instructions to passengers resulted in a completely disorderly evacuation. The Investigation attributed this to inadequate crew procedures which only envisaged an evacuation ordered by the Captain for reasons they were directly aware of and not a situation where the evacuation need was only obvious in the cabin.

guid: https://skybrary.aero/accidents-and-incidents/a319-helsinki-finland-2018 uri: https://skybrary.aero/accidents-and-incidents/a319-helsinki-finland-2018 title: B744 / B773 / B773, en-route, Delhi India, 2018 link: https://skybrary.aero/accidents-and-incidents/b744-b773-b773-en-route-delhi-india-2018 description:

On 22 December 2018, a Boeing 747-400 crew began to climb from FL310 without clearance and prescribed separation was lost against both an opposite direction Boeing 777-300 at FL 320 and another same direction Boeing 777-300 cleared to fly at FL330. The Investigation found that the 747 crew had requested FL 390 and then misunderstood the controller’s response of “level available 350” as a clearance to climb and gave a non-standard response and began to climb when the controller responded instructing the flight to standby for higher. Controller attempts to resolve the resultant ‘current conflict warnings’ were only partially successful.

guid: https://skybrary.aero/accidents-and-incidents/b744-b773-b773-en-route-delhi-india-2018 uri: https://skybrary.aero/accidents-and-incidents/b744-b773-b773-en-route-delhi-india-2018 title: A320 / E145, vicinity Barcelona Spain, 2019 link: https://skybrary.aero/accidents-and-incidents/a320-e145-vicinity-barcelona-spain-2019 description:

On 27 September 2019, an Airbus A320 and an Embraer 145 both inbound to Barcelona and being positioned for the same Transition for runway 25R lost separation and received and followed coordinated TCAS RAs after which the closest point of approach was 0.8nm laterally when 200 feet vertically apart. The Investigation found that the experienced controller involved had initially created the conflict whilst seeking to resolve another potential conflict between one of the aircraft and a third aircraft inbound for the same Transition and having identified it had then implemented a faulty recovery plan and executed it improperly.

guid: https://skybrary.aero/accidents-and-incidents/a320-e145-vicinity-barcelona-spain-2019 uri: https://skybrary.aero/accidents-and-incidents/a320-e145-vicinity-barcelona-spain-2019 title: B733, Wamena Papua Indonesia, 2016 link: https://skybrary.aero/accidents-and-incidents/b733-wamena-papua-indonesia-2016 description:

On 13 September 2016, a Boeing 737-300 made an unstabilised approach to Wamena and shortly after an EGPWS ‘PULL UP’ warning due to the high rate of descent, a very hard landing resulted in collapse of the main landing gear, loss of directional control and a lateral runway excursion. The Investigation found that the approach had been carried out with both the cloudbase and visibility below the operator-specified minima and noted that the Captain had ignored a delayed go around suggestion from the First Officer because he was confident he could land safely as the two aircraft ahead had done.

guid: https://skybrary.aero/accidents-and-incidents/b733-wamena-papua-indonesia-2016 uri: https://skybrary.aero/accidents-and-incidents/b733-wamena-papua-indonesia-2016 title: B738, en-route, east southeast of Adelaide Australia, 2017 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-east-southeast-adelaide-australia-2017 description:

On 13 September 2017, the airspeed of a Boeing 737-800 unexpectedly increased during an intentionally high speed descent and the Captain’s overspeed prevention response, which followed his taking over control without following the applicable procedure, was inappropriate and led directly to cabin crew injuries, one of which was serious. The Investigation found that the speed increase had been the result of a sudden decrease in tailwind component associated with windshear and noted that despite moderate clear air turbulence being forecast for the area, this had not resulted in the seat belt signs being on or any consequent cabin crew briefing.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-east-southeast-adelaide-australia-2017 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-east-southeast-adelaide-australia-2017 title: A320, Sylt Germany, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-sylt-germany-2017 description:

On 30 September 2017, an Airbus A320 touched down late after an ILS approach to runway 32 at Sylt with a significant tailwind component being reported and failed to stop before overrunning the end of the runway and subsequently stopped on grass 80 metres beyond it. The Investigation noted that the calculated required landing distance was close to the landing distance available, the actual approach speed was 20 knots above the calculated one and that the aircraft had floated in the flare above a wet runway. It was concluded that the runway excursion was attributable to non-performance of a go-around.

guid: https://skybrary.aero/accidents-and-incidents/a320-sylt-germany-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-sylt-germany-2017 title: A333, Medan Indonesia, 2020 link: https://skybrary.aero/accidents-and-incidents/a333-medan-indonesia-2020 description:

On 15 September 2020, an Airbus A330-300 touched down at Medan partially off the runway as a result of misjudgement by the right seat handling pilot before regaining it and completing the landing roll. The aircraft and some runway lights were damaged. The handling pilot was an A320/A330 dual-rated Instructor Pilot conducting standardisation training on a new Captain who had not flown for 7½ months having himself not flown from the right seat for six months. The continuing Investigation has recommended that the State Safety Regulator issues guidance in support of its temporary alleviations to pilot recency requirements.

guid: https://skybrary.aero/accidents-and-incidents/a333-medan-indonesia-2020 uri: https://skybrary.aero/accidents-and-incidents/a333-medan-indonesia-2020 title: A320, Surat India, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-surat-india-2017 description:

On 4 October 2017, an Airbus A320 slightly overran the end of runway 22 at Surat during an early morning daylight landing. A temporarily displaced landing threshold meant the runway length was only 1,905 metres rather than the 2,905 metre full length. The aircraft remained on a paved surface and was undamaged. Its crew did not report the excursion which was only discovered when broken runway lighting was subsequently discovered. The Investigation found that the non-precision approach made was unstable and that a prolonged float in the subsequent flare meant that only 600 metres of runway remained ahead at touchdown.

guid: https://skybrary.aero/accidents-and-incidents/a320-surat-india-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-surat-india-2017 title: GLF4, Abuja Nigeria, 2018 link: https://skybrary.aero/accidents-and-incidents/glf4-abuja-nigeria-2018 description:

On 12 September 2018, a Gulfstream G-IV overran the runway at Abuja after the air/ground status system failed to transition to ground on touchdown and the crew were slow to recognise that as a result neither spoilers nor thrust reversers had deployed. In the absence of recorded flight data, it was not possible to establish why the air/ground sensing system did not transition normally but no fault was found. The aircraft operator’s procedures in the event of such circumstances were found to be inadequate and regulatory oversight of the operator to have been comprehensively deficient over an extended period.

guid: https://skybrary.aero/accidents-and-incidents/glf4-abuja-nigeria-2018 uri: https://skybrary.aero/accidents-and-incidents/glf4-abuja-nigeria-2018 title: B738, vicinity Bergerac France, 2015 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-bergerac-france-2015 description:

On 29 January 2015, a Boeing 737-800 crew attempting to fly an NDB approach to Bergerac, with prior awareness that it would be necessary because of pre-notified ILS and DME unavailability, descended below 800 feet agl in IMC until an almost 1000 feet per minute descent when still over 8 nm from the runway threshold triggered an EGPWS ‘TERRAIN PULL UP’ warning and the simultaneous initiation of a go-around. The Investigation found that the PF First Officer was unfamiliar with NDB approaches but had not advised the Captain which resulted in confusion and loss of situational awareness by both pilots.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-bergerac-france-2015 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-bergerac-france-2015 title: B738, en-route, Aegean Sea, 2019 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-aegean-sea-2019 description:

On 22 August 2019, the left engine of a Boeing 737-800 failed for unknown reasons soon after reaching planned cruise level of FL360 twenty minutes after departing Samos, Greece and two attempted relights during and after descent to FL240 were unsuccessful. Instead of diverting to the nearest suitable airport as required by applicable procedures, the management pilot in command did not declare single engine operation and completed the planned flight to Prague, declaring a PAN to ATC only on entering Czech airspace. The Investigation noted that engine failure was due to fuel starvation after failure of the engine fuel pump.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-aegean-sea-2019 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-aegean-sea-2019 title: B788, en-route, central Romania, 2017 link: https://skybrary.aero/accidents-and-incidents/b788-en-route-central-romania-2017 description:

On 10 March 2017, a Boeing 787-8 lost contact with ATC over central Romania whilst the Captain was taking his second in-seat controlled rest and flight continued through Romanian and then, in daylight and without clearance, into Hungarian airspace. After well over an hour out of contact, military fighter interception prompted the re-establishment of normal communication. It was found that whilst the Captain was asleep, both speakers had been off and the First Officer had not been wearing her headset although she claimed that normal ATC communications had occurred whilst admitting that they had not been written down as required.

guid: https://skybrary.aero/accidents-and-incidents/b788-en-route-central-romania-2017 uri: https://skybrary.aero/accidents-and-incidents/b788-en-route-central-romania-2017 title: B738, Goa India, 2016 link: https://skybrary.aero/accidents-and-incidents/b738-goa-india-2016 description:

On 27 December 2016, the crew of a Boeing 737-800 taking off from Goa at night lost control shortly after setting takeoff thrust following which the aircraft almost immediately began to drift right and off the runway. It then continued at speed over rough ground for almost 300 metres before eventually stopping after which a MAYDAY call was followed by an emergency evacuation. The Investigation found that the Captain had increased thrust to takeoff without first ensuring that both engines were stabilised and then attempted to correct the drift by left rudder and brake rather than rejecting the takeoff.

guid: https://skybrary.aero/accidents-and-incidents/b738-goa-india-2016 uri: https://skybrary.aero/accidents-and-incidents/b738-goa-india-2016 title: A388, en-route, Bay of Bengal India, 2019 link: https://skybrary.aero/accidents-and-incidents/a388-en-route-bay-bengal-india-2019 description:

On 10 July 2019 an Airbus A380 in the cruise at night at FL 400 encountered unexpectedly severe turbulence approximately 13 hours into the 17 hour flight and 27 occupants were injured as a result, one seriously. The detailed Investigation concluded that the turbulence had occurred in clear air in the vicinity of a significant area of convective turbulence and a jet stream. A series of findings were related to both better detection of turbulence risks and ways to minimise injuries if unexpectedly encountered with particular reference to the aircraft type and operator but with wider relevance.

guid: https://skybrary.aero/accidents-and-incidents/a388-en-route-bay-bengal-india-2019 uri: https://skybrary.aero/accidents-and-incidents/a388-en-route-bay-bengal-india-2019 title: GLEX, Liverpool UK, 2019 link: https://skybrary.aero/accidents-and-incidents/glex-liverpool-uk-2019 description:

On 11 December 2019, a Bombardier BD700 Global 6000 making a night landing at Liverpool suffered a nose wheel steering failure shortly after touchdown. The crew were unable to prevent the aircraft departing the side of the runway into a grassed area where it stopped, undamaged, in mud. The Investigation found that the crew response was contrary to that needed for continued directional control but also that no pilot training or QRH procedure covered such a failure occurring at high speed nor was adequate guidance available on mitigating the risk of inadvertent opposite brake application during significant rudder deflection.

guid: https://skybrary.aero/accidents-and-incidents/glex-liverpool-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/glex-liverpool-uk-2019 title: B742, Sokoto Nigeria, 2013 link: https://skybrary.aero/accidents-and-incidents/b742-sokoto-nigeria-2013 description:

On 4 October 2013, a Boeing 747-200 touched down short of the intended landing runway at Sokoto after the Captain opted to reduce track miles by making a direct visual contact approach in dark night calm wind conditions rather than continuing as initially cleared towards an ILS approach in the reciprocal runway direction. The Investigation was hampered by an inoperative FDR and failure to preserve relevant CVR data on the grounded aircraft and concluded that the decision to make a visual approach rather than an ILS approach when the VASI was out of service for both runways was inappropriate.

guid: https://skybrary.aero/accidents-and-incidents/b742-sokoto-nigeria-2013 uri: https://skybrary.aero/accidents-and-incidents/b742-sokoto-nigeria-2013 title: A320 / E195, vicinity Brussels Belgium, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-e195-vicinity-brussels-belgium-2018 description:

On 23 February 2018, an Embraer 195LR and an Airbus A320 on SIDs departing Brussels lost separation after the 195 was given a radar heading to resolve a perceived third aircraft conflict which led to loss of separation between the two departing aircraft. STCA and coordinated TCAS RA activations followed but only one TCAS RA was followed and the estimated minimum separation was 400 feet vertically when 1.36 nm apart. The Investigation found that conflict followed an error by an OJTI-supervised trainee controller receiving extended revalidation training despite gaining his licence and having almost 10 years similar experience in Latvia.

guid: https://skybrary.aero/accidents-and-incidents/a320-e195-vicinity-brussels-belgium-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-e195-vicinity-brussels-belgium-2018 title: B738, East Midlands UK, 2020 link: https://skybrary.aero/accidents-and-incidents/b738-east-midlands-uk-2020 description:

On 9 February 2020, a Boeing 737-800 rejected its takeoff from East Midlands from a speed above V1 after encountering windshear in limiting weather conditions and was brought to a stop with 600 metres of runway remaining. The Investigation found that the Captain had assigned the takeoff to his First Officer but had taken control after deciding that a rejected takeoff was appropriate even though unequivocal QRH guidance that high speed rejected takeoffs should not be made due to windshear existed. Boeing analysis found that successful outcomes during takeoff windshear events have historically been more likely when takeoff is continued.

guid: https://skybrary.aero/accidents-and-incidents/b738-east-midlands-uk-2020 uri: https://skybrary.aero/accidents-and-incidents/b738-east-midlands-uk-2020 title: C525, vicinity Bournemouth UK, 2019 link: https://skybrary.aero/accidents-and-incidents/c525-vicinity-bournemouth-uk-2019 description:

On 13 April 2019, an experienced Cessna 525 pilot almost lost control shortly after takeoff from Bournemouth when a recently installed performance enhancement system malfunctioned. After a six minute flight involving a potentially hazardous upset and recovery of compromised control, the turn back was successful. The Investigation found that although the pilot was unaware of the supplementary procedures supporting the modification, these did not adequately address possible failure cases. Also, certification flight tests prior to modification approval did not identify the severity of some possible failure outcomes and corresponding Safety Recommendations were made to the system manufacturer and safety regulators.

guid: https://skybrary.aero/accidents-and-incidents/c525-vicinity-bournemouth-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/c525-vicinity-bournemouth-uk-2019 title: AT45, en-route, north of Islamabad Pakistan, 2016 link: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-islamabad-pakistan-2016 description:

On 7 December 2016, the crew of an ATR 42-500 lost control after airworthiness-related complications followed shutdown of the left engine whilst in the cruise and high speed terrain impact followed. The Investigation concluded that three pre-existing faults with the left engine and its propeller control mechanism had led to a loss of power which had necessitated its shutdown but that these faults had then caused much higher left side drag than would normally result from an engine shutdown and made it progressively more difficult to maintain control. Recovery from a first loss of control was followed by another without recovery.

guid: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-islamabad-pakistan-2016 uri: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-islamabad-pakistan-2016 title: E170 / Vehicles, Toronto Canada, 2019 link: https://skybrary.aero/accidents-and-incidents/e170-vehicles-toronto-canada-2019 description:

On 28 January 2019, a departing Embraer 170-200 narrowly avoided collision with part of a convoy of four snow clearance vehicles which failed to follow their clearance to enter a parallel taxiway and instead entered a Rapid Exit Taxiway and continued across the runway holding point before stopping just clear of the actual runway after multiple calls to do so. A high speed rejected takeoff led to the aircraft stopping just before the intersection where the incursion had occurred. The Investigation noted the prevailing adverse weather without attributing any specific cause to the vehicle convoy’s failure to proceed as cleared.

guid: https://skybrary.aero/accidents-and-incidents/e170-vehicles-toronto-canada-2019 uri: https://skybrary.aero/accidents-and-incidents/e170-vehicles-toronto-canada-2019 title: C56X, Aarhus Denmark, 2019 link: https://skybrary.aero/accidents-and-incidents/c56x-aarhus-denmark-2019 description:

On 5 August 2019, a Cessa 560XLS touched down in runway undershot at Aarhus whilst making a night ILS approach there and damage sustained when it collided with parts of the ILS LOC antenna caused a fuel leak which after injury-free evacuation of the occupants then ignited destroying most of the aircraft. The Investigation attributed the accident to the Captain’s decision to intentionally fly below the ILS glideslope in order to touch down at the threshold and to the disabling of the EGWPS alerting function in the presence of a steep authority gradient, procedural non-compliance and poor CRM.

guid: https://skybrary.aero/accidents-and-incidents/c56x-aarhus-denmark-2019 uri: https://skybrary.aero/accidents-and-incidents/c56x-aarhus-denmark-2019 title: AT76, Canberra Australia, 2019 link: https://skybrary.aero/accidents-and-incidents/at76-canberra-australia-2019 description:

On 25 September 2019, an ATR 72-600 about to depart from Canberra at night but in good visibility failed to follow its clearance to line up and take off on runway 35 and instead began its takeoff on runway 30. ATC quickly noticed the error and instructed the aircraft to stop which was accomplished from a low speed. The Investigation concluded that the 1030 metre takeoff distance available on runway 30 was significantly less than that required and attributed the crew error to attempting an unduly rushed departure for potentially personal reasons in the presence of insufficiently robust company operating procedures.

guid: https://skybrary.aero/accidents-and-incidents/at76-canberra-australia-2019 uri: https://skybrary.aero/accidents-and-incidents/at76-canberra-australia-2019 title: A320, en-route, north of Marseilles France, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-marseilles-france-2017 description:

On 17 November 2017, an Airbus A320 flight crew were both partially incapacitated by the effect of fumes described as acrid and stinging which they detected when following another smaller aircraft to the holding point at Geneva and then waiting in line behind it before taking off, the effect of which rapidly worsened en-route and necessitated a precautionary diversion to Marseilles. The very thorough subsequent Investigation was unable to determine the origin or nature of the fumes encountered but circumstantial evidence pointed tentatively towards ingestion of engine exhaust from the aircraft ahead in one or both A320 engines.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-marseilles-france-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-north-marseilles-france-2017 title: AT76, vicinity Dublin Ireland, 2016 link: https://skybrary.aero/accidents-and-incidents/at76-vicinity-dublin-ireland-2016 description:

On 2 September 2016, an ATR72-600 cleared to join the ILS for runway 28 at Dublin continued 800 feet below cleared altitude triggering an ATC safe altitude alert which then led to a go around from around 1000 feet when still over 5nm from the landing runway threshold. The Investigation attributed the event broadly to the Captain’s inadequate familiarity with this EFIS-equipped variant of the type after considerable experience on other older analogue-instrumented variants, noting that although the operator had provided simulator differences training, the -600 was not classified by the certification authority as a type variant.

guid: https://skybrary.aero/accidents-and-incidents/at76-vicinity-dublin-ireland-2016 uri: https://skybrary.aero/accidents-and-incidents/at76-vicinity-dublin-ireland-2016 title: CRJX / AT75, Tambolaka Indonesia, 2018 link: https://skybrary.aero/accidents-and-incidents/crjx-at75-tambolaka-indonesia-2018 description:

On 11 May 2018, a Bombardier CRJ1000 climbing on departure from Tambolaka and an ATR72-500 descending inbound there lost safe separation when during opposite turns in visual flight in uncontrolled airspace. Prompt response to both coordinated TCAS RAs resolved the conflict. The Investigation found the departing flight Captain mixed up left and right downwind circuit joining by the ATR 72 and that his inexperienced First Officer had not picked this up. It also noted that this Captain may not have been fit for duty and that all parties may have failed to fully recognise the limitations of ANSP ‘information’ service.

guid: https://skybrary.aero/accidents-and-incidents/crjx-at75-tambolaka-indonesia-2018 uri: https://skybrary.aero/accidents-and-incidents/crjx-at75-tambolaka-indonesia-2018 title: B738 / E110, Brasilia Brazil, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-e110-brasilia-brazil-2018 description:

On 10 April 2018, a Boeing 737-800 crew making a night takeoff from Brasilia did not see a smaller aircraft which had just landed on the same runway and was ahead until it appeared in the landing lights with rotation imminent. After immediately setting maximum thrust and rotating abruptly, the 737 just cleared the other aircraft, an Embraer 110 whose occupants were aware of a large aircraft passing very low overhead whilst their aircraft was still on the runway. The Investigation attributed the conflict primarily to controller use of non-standard phraseology and the absence of unobstructed runway visibility from the TWR.

guid: https://skybrary.aero/accidents-and-incidents/b738-e110-brasilia-brazil-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-e110-brasilia-brazil-2018 title: B738 / B738 / B752, Birmingham UK, 2020 link: https://skybrary.aero/accidents-and-incidents/b738-b738-b752-birmingham-uk-2020 description:

On 8 September 2020, an airport maintenance team driving at night on the centreline of the active runway at Birmingham were unaware that an inadequately secured 2 metre-long ladder had fallen from their pickup truck. Three aircraft then landed in the following half hour narrowly missing the ladder before it was discovered and the runway closed. The Investigation found that a more suitable alternative vehicle was available and that the completely inadequate method used to secure the ladder in their vehicle had failed to restrain it when the vehicle accelerated after passing the aiming point markings in the touchdown zone.

guid: https://skybrary.aero/accidents-and-incidents/b738-b738-b752-birmingham-uk-2020 uri: https://skybrary.aero/accidents-and-incidents/b738-b738-b752-birmingham-uk-2020 title: B738, vicinity Lanzarote Spain, 2019 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-lanzarote-spain-2019 description:

On 25 March 2019, a Boeing 737-800 making a non-precision daylight approach to Lanzarote with line training in progress began descending below the correct approach profile shortly after visual acquisition of the runway at 10nm when a much lower altitude than specified was maintained, EGPWS ‘CAUTION TERRAIN’ and ‘TERRAIN PULL UP’ activations eventually followed. With the terrain below clearly visible, the autopilot and autothrottle were disconnected and the aircraft flown level until the correct profile was regained after which the flight was then completed without further event. The Investigation made no findings which would fully explain the procedural non-compliance involved.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-lanzarote-spain-2019 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-lanzarote-spain-2019 title: B738, vicinity Paris Orly France, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-vicinity-paris-orly-france-2018 description:

On 7 February 2018, a Boeing 737-800 experienced an airspeed mismatch during takeoff on a post maintenance positioning flight but having identified the faulty system by reference to the standby instrumentation, the intended flight was completed without further event. After the recorded defect was then signed off as “no fault found” after a failure to follow the applicable fault-finding procedure, the same happened on the next (revenue) flight but with an air turnback made. The Investigation found that the faulty sensor had been fitted at build three years earlier with a contaminated component which had slowly caused sensor malfunction to develop.

guid: https://skybrary.aero/accidents-and-incidents/b738-vicinity-paris-orly-france-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-vicinity-paris-orly-france-2018 title: DH8C, Darwin NT Australia, 2019 link: https://skybrary.aero/accidents-and-incidents/dh8c-darwin-nt-australia-2019 description:

On 11 November 2019, one of the two PW100 series engines of a Bombardier DHC8-300 failed catastrophically when takeoff power was set prior to brake release. The Investigation found that the power turbine shaft had fractured in two places and all first and second stage power turbine blades had separated from their disks. The shaft failure was found to have been caused by fatigue cracking initiated by corrosion pitting which was assessed as probably the result of prolonged marine low-altitude operations by the aircraft. It was found that this fatigue cracking could increase undetected during service between scheduled inspections.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-darwin-nt-australia-2019 uri: https://skybrary.aero/accidents-and-incidents/dh8c-darwin-nt-australia-2019 title: ATP, Birmingham UK, 2020 link: https://skybrary.aero/accidents-and-incidents/atp-birmingham-uk-2020 description:

On 22 May 2020, a BAe ATP made a go around after the First Officer mishandled the landing flare at Birmingham and when the Captain took over for a second approach, his own mishandling of the touchdown led to a lateral runway excursion. The Investigation found that although the prevailing surface wind was well within the limiting crosswind component, that component was still beyond both their handling skill levels. It also found that they were both generally inexperienced on type, had not previously encountered more than modest crosswind landings and that their type training in this respect had been inadequate.

guid: https://skybrary.aero/accidents-and-incidents/atp-birmingham-uk-2020 uri: https://skybrary.aero/accidents-and-incidents/atp-birmingham-uk-2020 title: CRJ2 / B773, Toronto Canada, 2019 link: https://skybrary.aero/accidents-and-incidents/crj2-b773-toronto-canada-2019 description:

On 9 August 2019, a Bombardier CRJ-200LR about to depart Toronto which had read back and actioned a clearance to line up on the departure runway then began its takeoff without clearance and only commenced a high speed rejected takeoff when a Boeing 777-300 came into view crossing the runway ahead. A high speed rejected takeoff was completed from a maximum speed of around 100 knots. The Investigation concluded that an increased crew workload, an expectation that a takeoff clearance would be received without delay and misinterpretation of the line up instructions led to the premature initiation of a takeoff.

guid: https://skybrary.aero/accidents-and-incidents/crj2-b773-toronto-canada-2019 uri: https://skybrary.aero/accidents-and-incidents/crj2-b773-toronto-canada-2019 title: S76, en-route, northwest of Los Angeles USA, 2020 link: https://skybrary.aero/accidents-and-incidents/s76-en-route-northwest-los-angeles-usa-2020 description:

On 26 January 2020, a Sikorsky S76B on a night VFR passenger flight was observed to emerge from low cloud shortly after ATC had lost contact with it following a report that it was climbing to 4000 feet. It had then almost immediately crashed into terrain, destroying the aircraft and killing all its occupants. The Investigation found that the helicopter had been serviceable and that the pilot had lost control after intentionally continuing into IMC and then attempting to climb which resulted in spatial disorientation. The aircraft operator’s inadequate risk management was found to have contributed to the accident outcome.

guid: https://skybrary.aero/accidents-and-incidents/s76-en-route-northwest-los-angeles-usa-2020 uri: https://skybrary.aero/accidents-and-incidents/s76-en-route-northwest-los-angeles-usa-2020 title: DH8C, Stephenville NL Canada, 2018 link: https://skybrary.aero/accidents-and-incidents/dh8c-stephenville-nl-canada-2018 description:

On 15 November 2018, a Bombardier DHC8-300 made a main gear only touchdown at Stephenville with only minor damage after diverting there when the nose landing gear only partially extended when routinely selected on approach at the originally intended destination. The Investigation found that the cause was incorrect nose gear assembly which had allowed hydraulic fluid to leak and eventually led to it jamming. There was some concern at the way the flight was conducted following the problem which involved continuous smartphone communications with the operator and an overspeed which it was considered constituted an avoidable risk to safety.

guid: https://skybrary.aero/accidents-and-incidents/dh8c-stephenville-nl-canada-2018 uri: https://skybrary.aero/accidents-and-incidents/dh8c-stephenville-nl-canada-2018 title: B712 / CRJ7, vicinity Strasbourg France, 2019 link: https://skybrary.aero/accidents-and-incidents/b712-crj7-vicinity-strasbourg-france-2019 description:

On 12 April 2019, a Boeing 717-200 commenced a go around at Strasbourg because the runway ahead was occupied by a departing Bombardier CRJ700 which subsequently, despite co-ordinated TCAS RAs, then came to within 50 feet vertically when only 740 metres apart laterally as the CRJ, whose crew did not see the 717, passed right to left in front of it. The Investigation attributed the conflict primarily to a series of flawed judgements by the TWR controller involved whilst also noting one absent and one inappropriate ATC procedure which respectively may have provided a context for the resultant risk.

guid: https://skybrary.aero/accidents-and-incidents/b712-crj7-vicinity-strasbourg-france-2019 uri: https://skybrary.aero/accidents-and-incidents/b712-crj7-vicinity-strasbourg-france-2019 title: B788, en-route, Chengde China, 2019 link: https://skybrary.aero/accidents-and-incidents/b788-en-route-chengde-china-2019 description:

On 15 August 2019, a Boeing 787 descending towards destination Beijing received ATC approval for convective weather avoidance but this was then modified with both a new track requirement and a request to descend which diminished its effectiveness. A very brief encounter with violent turbulence followed but as the seat belt signs had not been proactively switched on, the cabin was not secured and two passengers sustained serious injuries and two cabin crew sustained minor injuries. The Investigation noted that weather deviation requests could usefully be accompanied by an indication of how long they were required for.

guid: https://skybrary.aero/accidents-and-incidents/b788-en-route-chengde-china-2019 uri: https://skybrary.aero/accidents-and-incidents/b788-en-route-chengde-china-2019 title: AT72, Cologne-Bonn Germany, 2020 link: https://skybrary.aero/accidents-and-incidents/at72-cologne-bonn-germany-2020 description:

On 27 April 2020, an ATR 72-200 freighter crew attempted a night takeoff in good visibility aligned with the edge of runway 06 and did not begin rejecting it until within 20 knots of the applicable V1 despite hearing persistent regular noises which they did not recognise as edge light impacts and so completed the rejection on the same alignment. The Investigation noted both pilots’ familiarity with the airport and their regular work together and attributed their error to their low attention level and a minor distraction during the turnround after backtracking.

guid: https://skybrary.aero/accidents-and-incidents/at72-cologne-bonn-germany-2020 uri: https://skybrary.aero/accidents-and-incidents/at72-cologne-bonn-germany-2020 title: JS32, Münster/Osnabrück Germany, 2019 link: https://skybrary.aero/accidents-and-incidents/js32-munsterosnabruck-germany-2019 description:

On 8 October 2019, a BAe Jetstream 32 departing Münster/Osnabrück couldn’t be rotated and after beginning rejected takeoff from well above V1, the aircraft departed the side of the runway passing close to another aircraft at high speed before regaining the runway for the remainder of its deceleration. The Investigation noted that the flight was the first supervised line training sector for the very inexperienced First Officer but attributed the whole event to the Training Captain’s poor performance which had, apart many from other matters, led indirectly to the inability to rotate and to the subsequent directional control problem.

guid: https://skybrary.aero/accidents-and-incidents/js32-munsterosnabruck-germany-2019 uri: https://skybrary.aero/accidents-and-incidents/js32-munsterosnabruck-germany-2019 title: IL76 / B741, en-route, west of Delhi India, 1996 link: https://skybrary.aero/accidents-and-incidents/il76-b741-en-route-west-delhi-india-1996 description:

On 12 November 1996, an Ilyushin IL76TD and an opposite direction Boeing 747-100 collided head on at the same level in controlled airspace resulting in the destruction of both aircraft and the loss of 349 lives. The Investigation concluded that the IL76 had descended one thousand feet below its cleared level after its crew had interpreted ATC advice of opposite direction traffic one thousand feet below as the reason to remain at FL150 as re-clearance to descend to this lower level. Fifteen Safety Recommendations relating to English language proficiency, crew resource management, collision avoidance systems and ATC procedures were made.

guid: https://skybrary.aero/accidents-and-incidents/il76-b741-en-route-west-delhi-india-1996 uri: https://skybrary.aero/accidents-and-incidents/il76-b741-en-route-west-delhi-india-1996 title: A320, en-route, northwest Greece, 2017 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-northwest-greece-2017 description:

On 29 September 2017, the crew of an Airbus A320 detected a smell of burning plastic and simultaneously observed black smoke entering the flight deck near the right side rudder pedals. Completion of appropriate response procedures reduced the smoke and a diversion to Athens with a MAYDAY declared was without further event. The origin of the smoke and fumes was traced to the failure of the static inverter which was part of a batch which had been previously notified as faulty but not identified as such by the aircraft operator’s maintenance organisation which has since modified its relevant procedures.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-northwest-greece-2017 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-northwest-greece-2017 title: B789, en-route, west of Swansea UK, 2020 link: https://skybrary.aero/accidents-and-incidents/b789-en-route-west-swansea-uk-2020 description:

On 1 October 2020, a Boeing 787-9 was approaching the top of descent when the cabin crew discovered a mobile phone crushed in a flat bed seat which had just been changed to the seated position for landing. A fire which had started was extinguished and the Captain declared a ‘PAN’ to ensure the fire service attended the arrival. The Investigation noted that there are currently no seat design requirements to prevent electronic devices from becoming trapped in seats and that it is proving challenging to find a workable solution. A Safety Recommendation to improve seat design regulations was made.

guid: https://skybrary.aero/accidents-and-incidents/b789-en-route-west-swansea-uk-2020 uri: https://skybrary.aero/accidents-and-incidents/b789-en-route-west-swansea-uk-2020 title: A388, en-route, north northeast of Beira Mozambique, 2020 link: https://skybrary.aero/accidents-and-incidents/a388-en-route-north-northeast-beira-mozambique-2020 description:

On 16 January 2020 an Airbus A380 in the cruise at FL 400 in an area of correctly forecast convective turbulence encountered severe turbulence not anticipated by the crew who had not put on the seatbelt signs or alerted the cabin crew in time for the cabin to be secured. An unsecured passenger was seriously injured and several other passengers and an unsecured member of cabin crew were lifted off their feet but managed to avoid injury. The Investigation concluded that the flight crew had not made full use of the capabilities of the available on board weather radar equipment.

guid: https://skybrary.aero/accidents-and-incidents/a388-en-route-north-northeast-beira-mozambique-2020 uri: https://skybrary.aero/accidents-and-incidents/a388-en-route-north-northeast-beira-mozambique-2020 title: C441, en-route, east southeast of Broome Australia, 2018 link: https://skybrary.aero/accidents-and-incidents/c441-en-route-east-southeast-broome-australia-2018 description:

On 2 March 2018, a Cessna 441 conducting a single-pilot scheduled passenger flight to Broome suffered successive failures of both engines due to fuel exhaustion and a MAYDAY was declared. Unable to reach the destination or any other aerodrome by the time this occurred, an uneventful landing was made on the area’s main highway. The Investigation found that the fuel quantity was over-reading due to water in the fuel tanks, that cross-checking of fuel used versus indicated fuel in tanks was not done and that when the possibility of fuel exhaustion was first indicated, an available diversion was not made.

guid: https://skybrary.aero/accidents-and-incidents/c441-en-route-east-southeast-broome-australia-2018 uri: https://skybrary.aero/accidents-and-incidents/c441-en-route-east-southeast-broome-australia-2018 title: S92, manoeuvring, near Shipston-on-Stour UK, 2019 link: https://skybrary.aero/accidents-and-incidents/s92-manoeuvring-near-shipston-stour-uk-2019 description:

On 14 October 2019, a Sikorsky S92A manoeuvring below low cloud in poor daylight visibility in an unsuccessful attempt to locate the intended private landing site flew north towards rising ground approximately ¾ mile east of it, coming within a recorded 28 feet above terrain near to occupied houses before making an emergency climb and over-torqing the engines followed by an unstable but successful second approach. The Investigation found relevant operator procedures absent or ineffective, an intention by the management pilot in command to reach the landing site despite conditions and uncertainty about the applicable regulatory context for the flight. 

guid: https://skybrary.aero/accidents-and-incidents/s92-manoeuvring-near-shipston-stour-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/s92-manoeuvring-near-shipston-stour-uk-2019 title: B788, en-route, Northwest Pacific Ocean, 2019 link: https://skybrary.aero/accidents-and-incidents/b788-en-route-northwest-pacific-ocean-2019 description:

On 1 June 2019, a Boeing 787-8 lost all cabin air conditioning after both packs failed less than an hour from its destination, Narita. When the Cabin Altitude reached 10,000 feet, the descent already commenced was completed as an emergency descent and the flight thereafter was without further event. The Investigation found that although an amended non normal procedure restricting pack resets to a maximum altitude of 35000 feet had been issued almost two months earlier, it was still “under review” at the operator which has since amended their procedures for assessing manufacturer communications which have operational safety implications.

guid: https://skybrary.aero/accidents-and-incidents/b788-en-route-northwest-pacific-ocean-2019 uri: https://skybrary.aero/accidents-and-incidents/b788-en-route-northwest-pacific-ocean-2019 title: B733, en-route, north of Narrandera NSW Australia, 2018 link: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-narrandera-nsw-australia-2018 description:

On 15 August 2018, a Boeing 737-300SF crew concerned about a small residual pressure in a bleed air system isolated after a fault occurred en-route then sought and were given non-standard further troubleshooting guidance by company maintenance which, when followed, led directly and indirectly to additional problems including successive incapacitation of both pilots and a MAYDAY diversion. The Investigation found that the aircraft concerned was carrying a number of relevant individually minor undetected defects which meant the initial crew response was not completely effective and prompted a request for in-flight assistance which was unnecessary and led to the further outcomes.

guid: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-narrandera-nsw-australia-2018 uri: https://skybrary.aero/accidents-and-incidents/b733-en-route-north-narrandera-nsw-australia-2018 title: DH8D, en-route, east northeast of Accra Ghana, 2018 link: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-east-northeast-accra-ghana-2018 description:

On 6 March 2018, smoke was detected coming from flight deck and passenger cabin air conditioning vents of an en-route Bombardier DHC8-400. A MAYDAY was declared to ATC but the prescribed response effectively cleared the smoke and no emergency evacuation on landing was deemed necessary. The Investigation found that the smoke was caused by oil leaking into the air conditioning system due to a failed right hand engine seal. The operator subsequently began to implement a recommended engine modification and adopt a system provided by the engine manufacturer to proactively detect such oil leaks before air conditioning systems are contaminated. 

guid: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-east-northeast-accra-ghana-2018 uri: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-east-northeast-accra-ghana-2018 title: UAV, Barcarès near Perpignan France, 2019 link: https://skybrary.aero/accidents-and-incidents/uav-barcares-near-perpignan-france-2019 description:

On 14 July 2019, after control of a DJI-Inspire 2 UA was lost, it descended into people on the ground under power causing multiple minor injuries. The Investigation found that “professional drone pilots” were operating the UA in gross breach of the approval obtained, had deleted all recorded controller evidence of the accident flight and that their account of the loss of control was not compatible with the evidence recovered from the UA. It also noted that the risk of injury to third parties was increased by the absence of protection around the propellers which was not a regulatory requirement.

guid: https://skybrary.aero/accidents-and-incidents/uav-barcares-near-perpignan-france-2019 uri: https://skybrary.aero/accidents-and-incidents/uav-barcares-near-perpignan-france-2019 title: B773, en-route, west of Haifa Israel, 2021 link: https://skybrary.aero/accidents-and-incidents/b773-en-route-west-haifa-israel-2021 description:

On 17 January 2021, a Boeing 777-300 which had just begun descent into Beirut encountered unexpected moderate to severe clear air turbulence which resulted in one major and several minor injuries to unsecured occupants including cabin crew. The Investigation found that the flight crew had acted in accordance with all applicable procedures on the basis of information available to them but noted that the operator’s flight watch system had failed to generate and communicate a message about a relevant SIGMET until after the severe turbulence episode due to a data processing issue not identified as representing an operational safety risk.

guid: https://skybrary.aero/accidents-and-incidents/b773-en-route-west-haifa-israel-2021 uri: https://skybrary.aero/accidents-and-incidents/b773-en-route-west-haifa-israel-2021 title: A320, en-route, northern Italy, 2016 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-northern-italy-2016 description:

On 15 August 2016, the cognitive condition of an Airbus A320 Captain deteriorated en-route to Riga and he assigned all flight tasks to the First Officer. When his condition deteriorated further, an off duty company First Officer travelling as a passenger was invited to occupy the flight deck supernumerary crew seat to assist. Once descent had commenced, the Captain and assisting First Officer swapped seats and the flight was thereafter completed without any further significant event. The Investigation concluded that the Captain’s serious physical and mental exhaustion had been the result of the combined effect of chronic fatigue and stress.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-northern-italy-2016 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-northern-italy-2016 title: AT45, en-route, north northwest of Tanegashima Japan, 2019 link: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-northwest-tanegashima-japan-2019 description:

On 12 October 2019, an ATR 42-500 on which Captain upgrade line training was being conducted encountered mild clear air turbulence soon after descent began and despite setting flight idle power, a concurrent speed increase led to concern at a possible VMO exceedence. An abrupt and ultimately simultaneous manual increase in pitch attitude followed leading to serious injury to the unsecured cabin crew which rendered them unfit to work. The Investigation found that the upset - a change in pitch from -2.3° to +6.3°in one second - was almost entirely due to pitch input from both pilots rather than turbulence.

guid: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-northwest-tanegashima-japan-2019 uri: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-northwest-tanegashima-japan-2019 title: B738 / B738, en-route, south of Écija Spain, 2019 link: https://skybrary.aero/accidents-and-incidents/b738-b738-en-route-south-ecija-spain-2019 description:

On 16 July 2019, a Boeing 737-800 inbound to Malaga and another Boeing 738-800 inbound to Seville and under area radar control lost separation after the Malaga-bound aircraft was unexpectedly given radar headings to extend its destination track miles after early handover to a control  sector which it had not yet entered. With no time to achieve resolution, the two aircraft, both descending, came within 1.3 nm of each other at the same level. The Investigation attributed the conflict to an overly-permissive Letter of Agreement between Seville Centre and Malaga Approach and recommended that it be revised to improve risk management.

guid: https://skybrary.aero/accidents-and-incidents/b738-b738-en-route-south-ecija-spain-2019 uri: https://skybrary.aero/accidents-and-incidents/b738-b738-en-route-south-ecija-spain-2019 title: AT45, en-route, north of Aurillac France, 2018 link: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-aurillac-france-2018 description:

On 25 March 2018, an ATR 42-500 main landing gear bay door weighing 15 kg detached shortly after a night descent had begun but this was unknown until the flight arrived at Aurillac. The Investigation found that the root cause of the detachment was a loose securing nut which had triggered a sequence of secondary failures within a single flight which culminated in the release of the door. It was concluded that the event highlighted specific and systemic weakness in relevant airworthiness documentation and practice in relation to the lost door and the use of fasteners on this aircraft type generally.

guid: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-aurillac-france-2018 uri: https://skybrary.aero/accidents-and-incidents/at45-en-route-north-aurillac-france-2018 title: B788, en-route, near Huesca northeast Spain, 2019 link: https://skybrary.aero/accidents-and-incidents/b788-en-route-near-huesca-northeast-spain-2019 description:

On 3 November 2019, a Boeing 787-8 descending towards Barcelona experienced an unanticipated airspeed increase and the unduly abrupt manual pitch response which resulted in a large and rapid oscillation in vertical acceleration during an otherwise smooth descent resulted in two serious injuries, one to a passenger and the other to one of the cabin crew. It appeared that the cause of the airspeed increase was an unexplained vertical mode reversion from VNAV SPD to VNAV PTH about 20 seconds prior to the upset caused by the response to it. 

guid: https://skybrary.aero/accidents-and-incidents/b788-en-route-near-huesca-northeast-spain-2019 uri: https://skybrary.aero/accidents-and-incidents/b788-en-route-near-huesca-northeast-spain-2019 title: PA46, en-route, north northwest of Guernsey Channel Islands, 2019 link: https://skybrary.aero/accidents-and-incidents/pa46-en-route-north-northwest-guernsey-channel-islands-2019 description:

On 21 January 2019, a Piper PA46-310P en-route north northwest of Guernsey was reported missing and subsequently confirmed to have broken up in flight during an uncontrolled descent. The Investigation found that neither the pilot nor the aircraft involved were able to be used for commercial passenger flight operations but also found that although the direct cause of loss of control was unproven, it was most likely the consequence of carbon monoxide poisoning originating from an exhaust system leak. The safety implications arising from operation of private flights for commercial passenger transport purposes contrary to regulatory requirements were also highlighted.

guid: https://skybrary.aero/accidents-and-incidents/pa46-en-route-north-northwest-guernsey-channel-islands-2019 uri: https://skybrary.aero/accidents-and-incidents/pa46-en-route-north-northwest-guernsey-channel-islands-2019 title: DHC6, Jomsom Nepal, 2013 link: https://skybrary.aero/accidents-and-incidents/dhc6-jomsom-nepal-2013 description:

On 16 May 2013, a DHC6-300 on a domestic passenger flight made a tailwind touchdown at excessive speed in the opposite direction of the of 740 metre-long runway to the notified direction in use and, after departing the runway to one side during deceleration, re-entered the runway and attempted to take off. This failed and the aircraft breached the perimeter fence and fell into a river. The Investigation identified inappropriate actions of the aircraft commander in respect of both the initial landing and his response to the subsequent runway excursion and also cited the absence of effective CRM.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-jomsom-nepal-2013 uri: https://skybrary.aero/accidents-and-incidents/dhc6-jomsom-nepal-2013 title: DH8D / P180, en-route, near Kelowna BC Canada, 2019 link: https://skybrary.aero/accidents-and-incidents/dh8d-p180-en-route-near-kelowna-bc-canada-2019 description:

On 3 January 2019, prescribed vertical separation was lost between a Bombardier DHC8-400 and a Piaggio P180 on converging cruise tracks at FL 220 and only restored after a resulting TCAS RA was followed. The Investigation found both aircraft were being flown in accordance with their clearances and that the controller involved had not been aware of corresponding traffic and conflict alerting system activations. A specific traffic display fault which arose from failure to follow a routine software upgrade procedure correctly and the shift supervisor failing to recognise the need to act as controller when workload increased were assessed contributory.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-p180-en-route-near-kelowna-bc-canada-2019 uri: https://skybrary.aero/accidents-and-incidents/dh8d-p180-en-route-near-kelowna-bc-canada-2019 title: B772, en-route, north of Bahrain, 2017 link: https://skybrary.aero/accidents-and-incidents/b772-en-route-north-bahrain-2017 description:

On 27 September 2017, a Boeing 777-200LRF Captain left the flight deck to retrieve their crew meal about 40 minutes after departing Abu Dhabi but whilst doing so he collapsed unconscious in the galley and despite assistance subsequently died. A MAYDAY was declared and a diversion to Kuwait successfully completed by the remaining pilot. The Investigation determined that the cause of death was cardiopulmonary system collapse due to a stenosis in the coronary artery. It was noted that the Captain’s medical condition had been partially concealed from detection because of his unapproved use of potentially significant self-medication.

guid: https://skybrary.aero/accidents-and-incidents/b772-en-route-north-bahrain-2017 uri: https://skybrary.aero/accidents-and-incidents/b772-en-route-north-bahrain-2017 title: DH8D, en-route, north of Plymouth UK, 2019 link: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-north-plymouth-uk-2019 description:

On 14 November 2019, a Bombardier DHC8-400 experienced roll control difficulties after takeoff. These were manageable but it was decided a precautionary diversion should be made and this was accomplished without any significant roll control difficulty. The Investigation found that the right wing aileron control cable had failed due to undetected wear and that an option to fit an upgraded cable had not been taken. It also found the aircraft had a history of an intermittently unresponsive right aileron and discovered that signal noise filters which smoothed recorded data for all three primary flight control channels compromised FDR data value.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-north-plymouth-uk-2019 uri: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-north-plymouth-uk-2019 title: A321, en-route, north of Kaohsiung Taiwan, 2019 link: https://skybrary.aero/accidents-and-incidents/a321-en-route-north-kaohsiung-taiwan-2019 description:

On 29 October 2019, an Airbus A321 was descending towards its destination, Kaohsiung, when the First Officer suddenly lost consciousness without warning. The Captain declared a MAYDAY and with cabin crew assistance, he was secured clear of the flight controls and given oxygen which appeared beneficial. He was then removed to the passenger cabin where a doctor recommended continuing oxygen treatment. On arrival, he had fully regained consciousness. Medical examination and tests both on arrival and subsequently were unable to identify a cause although a context of cumulative fatigue was considered likely after three consecutive nights of inadequate sleep.

guid: https://skybrary.aero/accidents-and-incidents/a321-en-route-north-kaohsiung-taiwan-2019 uri: https://skybrary.aero/accidents-and-incidents/a321-en-route-north-kaohsiung-taiwan-2019 title: UAV, manoeuvring, Poole Dorset UK, 2020 link: https://skybrary.aero/accidents-and-incidents/uav-manoeuvring-poole-dorset-uk-2020 description:

On 19 November 2020, the police operator of a DJI Matrice M210 UA lost control of it over Poole when it drifted beyond Visual Line Of Sight (VLOS) and communication ceased. It was subsequently damaged when colliding with a house in autoland mode. The Investigation found that a partial power failure had followed battery disconnection with its consequences not adequately communicated to the pilot. It faulted both the applicable UA User Manual content and the absence of sufficient UA status and detected wind information to the pilot. A failure to properly define VLOS was identified but not considered directly causal.

guid: https://skybrary.aero/accidents-and-incidents/uav-manoeuvring-poole-dorset-uk-2020 uri: https://skybrary.aero/accidents-and-incidents/uav-manoeuvring-poole-dorset-uk-2020 title: A333, en-route, west northwest of Sydney Australia, 2019 link: https://skybrary.aero/accidents-and-incidents/a333-en-route-west-northwest-sydney-australia-2019 description:

On 15 December 2019, an Airbus A330-200 turned back to Sydney shortly after departure when a major hydraulic system leak was annunciated. The return was uneventful until engine shutdown after clearing the runway following which APU use for air conditioning was followed by a gradual build up of hydraulic haze and fumes which eventually prompted an emergency evacuation. The Investigation found that fluid leaking from ruptured rudder servo hose had entered the APU air intake. The resulting evacuation was found to have been somewhat disorganised with this being attributed mainly to a combination of inadequate cabin crew procedures and training.

guid: https://skybrary.aero/accidents-and-incidents/a333-en-route-west-northwest-sydney-australia-2019 uri: https://skybrary.aero/accidents-and-incidents/a333-en-route-west-northwest-sydney-australia-2019 title: DHC6, en-route, south southwest of Jomsom Nepal, 2016 link: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-south-southwest-jomsom-nepal-2016 description:

On 24 February 2016 a DHC6 (9N-AHH) on a VFR flight to Jomsom which had continued towards destination after encountering adverse weather impacted remote rocky terrain at an altitude of almost 11,000 feet approximately 15 minutes after takeoff after intentionally and repeatedly entering cloud in order to reach the destination. The aircraft was destroyed and all on board were killed. The Investigation attributed this to the crew’s repeated decision to fly in cloud and their deviation from the intended route after losing situational awareness. Spatial disorientation followed and they then failed to respond to repeated EGPWS cautions and warnings.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-south-southwest-jomsom-nepal-2016 uri: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-south-southwest-jomsom-nepal-2016 title: A320 / B739, en-route, northwest of Surabaya Indonesia, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-b739-en-route-northwest-surabaya-indonesia-2018 description:

On 6 January 2018, a Boeing 737-900 and an Airbus A320 both inbound to Surabaya with similar estimated arrival times were cleared to hold at the same waypoint at FL100 and FL110 respectively but separation was lost when the A320 continued below FL110. Proximity was limited to 1.9nm laterally and 600 feet vertically following correct responses to coordinated TCAS RAs. The Investigation found that all clearances / readbacks had been correct but that the A320 crew had set FL100 instead of their FL110 clearance and attributed this to diminished performance due to the passive distraction of one of the pilots.

guid: https://skybrary.aero/accidents-and-incidents/a320-b739-en-route-northwest-surabaya-indonesia-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-b739-en-route-northwest-surabaya-indonesia-2018 title: F100, en-route, northwest of Goroka Papua New Guinea, 2020 link: https://skybrary.aero/accidents-and-incidents/f100-en-route-northwest-goroka-papua-new-guinea-2020 description:

On 18 March 2020, a Fokker 100 en-route to Port Moresby experienced a failure of the cabin pressurisation and air conditioning system due to a complete failure of the bleed air system. An emergency descent and a PAN were declared and a diversion to Madang completed. The Investigation noted unscheduled work on the bleed air system had occurred prior to the departure of the flight and that long running problems with this system had not been satisfactorily resolved until after the investigated occurrence when four malfunctioning components had finally been systematically identified and replaced.

guid: https://skybrary.aero/accidents-and-incidents/f100-en-route-northwest-goroka-papua-new-guinea-2020 uri: https://skybrary.aero/accidents-and-incidents/f100-en-route-northwest-goroka-papua-new-guinea-2020 title: A319, en-route, southwest of Carlisle UK, 2021 link: https://skybrary.aero/accidents-and-incidents/a319-en-route-southwest-carlisle-uk-2021 description:

On 6 August 2021, an Airbus A319 experienced uncommanded loss of both Flight Directors and the Flight Mode Annunciator and disconnection of both autopilot and autothrust in the climb. After levelling at FL350, significant inertial reference position inconsistencies were observed. A precautionary PAN was declared and the flight was completed. Investigation found that the cause was a momentary abnormal vertical shock load transferred to Inertial Reference System equipment through an overextended nose gear shock absorber by a sharp jolt during takeoff caused by a runway patch repair. Sensitivity of the particular inertial reference system installed on the aircraft was noted.

guid: https://skybrary.aero/accidents-and-incidents/a319-en-route-southwest-carlisle-uk-2021 uri: https://skybrary.aero/accidents-and-incidents/a319-en-route-southwest-carlisle-uk-2021 title: DH8D, en-route, south of Port Moresby Papua New Guinea, 2020 link: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-port-moresby-papua-new-guinea-2020 description:

On 16 March 2020, a PW150A-powered Bombardier DHC8-400 crew declared a PAN and turned back to Port Moresby after abnormal fumes and (much later) some visible ‘smoke’ which had become apparent after takeoff began to intensify causing some passengers breathing difficulties. Once clear of the landing runway, a precautionary rapid disembarkation was completed. The Investigation found that the source of the smoke/fumes was oil leaking from a failed right engine bearing seal. The failure was found to have occurred ahead of the recommended inspection interval for the seal concerned, a risk which engine manufacturer Pratt & Whitney Canada was aware of.

guid: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-port-moresby-papua-new-guinea-2020 uri: https://skybrary.aero/accidents-and-incidents/dh8d-en-route-south-port-moresby-papua-new-guinea-2020 title: A320 / A320, en-route, northeast of Surabaya Indonesia, 2018 link: https://skybrary.aero/accidents-and-incidents/a320-a320-en-route-northeast-surabaya-indonesia-2018 description:

On 17 January 2018, two Airbus A320s both inbound to Surabaya at night were vectored to the same waypoint to hold, one at FL210 and the other at FL200 but the one initially given FL210 was then re-cleared to also descend to FL200. The two aircraft subsequently received and followed coordinated TCAS RAs which restored prescribed separation. The Investigation found that before the conflict, the experienced controller involved had made several transmissions to aircraft other than the intended ones and noted that the usually-available ATC conflict alerting system had been temporarily out of service without any consequent mitigations in place.

guid: https://skybrary.aero/accidents-and-incidents/a320-a320-en-route-northeast-surabaya-indonesia-2018 uri: https://skybrary.aero/accidents-and-incidents/a320-a320-en-route-northeast-surabaya-indonesia-2018 title: A332, en-route, Central African Republic, 2020 link: https://skybrary.aero/accidents-and-incidents/a332-en-route-central-african-republic-2020 description:

On 31 December 2020, an Airbus A330-200 identified a fuel leak during a routine top-of-climb check but instead of following the prescribed engine shutdown and leak isolation procedure and then landing as soon as possible, the crew had continued on track until diverting to N’Djaména over 90 minutes later by which time nearly six tonnes of fuel was missing. The leak was caused by an incorrectly assembled connection at the pylon/engine interface. The flight crew’s procedural non-compliance was identified as having introduced an avoidable fire risk and been indicative of a systemically weak safety culture at the airline concerned.

guid: https://skybrary.aero/accidents-and-incidents/a332-en-route-central-african-republic-2020 uri: https://skybrary.aero/accidents-and-incidents/a332-en-route-central-african-republic-2020 title: B738, en-route, southwest of Metz France, 2018 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-southwest-metz-france-2018 description:

On 13 July 2018, a Boeing 737-800 cruising at FL370 at night experienced a sudden rapid depressurisation. An emergency descent to FL 090 followed but the cabin altitude was not manually controlled and after the cabin pressure had risen to that equivalent to 7000 feet below sea level, immediate equalisation of cabin and actual altitudes resulted in a second sudden depressurisation. Diversion to Frankfurt Hahn was completed without further event. The first depressurisation had resulted from a transient and rare pressure controller malfunction but passenger injuries were considered attributable to a complete absence of pressurisation control during the emergency descent.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-southwest-metz-france-2018 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-southwest-metz-france-2018 title: BE20, en-route, near Lausanne Switzerland, 2019 link: https://skybrary.aero/accidents-and-incidents/be20-en-route-near-lausanne-switzerland-2019 description:

On 23 February 2019, a Raytheon B200 King Air which had recently departed Saanen was passing FL155 for cleared altitude FL240 when a total electrical failure occurred. On subsequently making contact with ATC on a hand-held personal radio, the pilot advised his intention to exit controlled airspace and complete an already commenced visual diversion to Lausanne which was then done. It was found that failure to use the prescribed normal checklists had resulted in an undetected electrical system selection error which had led to the successive discharge of both main batteries when corresponding alerts and warnings also went unnoticed.

guid: https://skybrary.aero/accidents-and-incidents/be20-en-route-near-lausanne-switzerland-2019 uri: https://skybrary.aero/accidents-and-incidents/be20-en-route-near-lausanne-switzerland-2019 title: DHC6, en-route, northwest of Fort Providence NWT Canada, 2021 link: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-northwest-fort-providence-nwt-canada-2021 description:

On 1 November 2021, a deHavilland DHC6-300 crew en-route to Fort Simpson realised that they had insufficient fuel on board to reach their intended destination and therefore decided to attempt a diversion to the nearest available airport at Fort Providence. As fuel available dwindled, one engine was shut down but after an inadvertent fuel tank selection, the initially intended diversion was no longer possible and a forced landing in a bog was successfully accomplished. The Training Captain involved had developed a habit of performing checklists silently and from memory after gaining all his professional pilot experience at the same operator.

guid: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-northwest-fort-providence-nwt-canada-2021 uri: https://skybrary.aero/accidents-and-incidents/dhc6-en-route-northwest-fort-providence-nwt-canada-2021 title: E170, en-route, southwest of Birmingham UK, 2021 link: https://skybrary.aero/accidents-and-incidents/e170-en-route-southwest-birmingham-uk-2021 description:

On 7 June 2021 an Embraer ERJ170 had just commenced its descent towards destination when both primary and secondary pitch trim systems failed resulting in excessive nose-down pitch control forces and an inoperative autopilot. The flight was completed without further event with the Pilot Flying using both hands on the control yoke to control pitch attitude manually. During the landing roll the nosewhweel steering system also failed. The pitch trim failure was attributed to probable jamming of the trim actuator due to water, possibly condensation, freezing within it. The steering system fault was attributed to a completely unrelated sensor failure.

guid: https://skybrary.aero/accidents-and-incidents/e170-en-route-southwest-birmingham-uk-2021 uri: https://skybrary.aero/accidents-and-incidents/e170-en-route-southwest-birmingham-uk-2021 title: B738, west southwest of Barcelona Spain, 2021 link: https://skybrary.aero/accidents-and-incidents/b738-west-southwest-barcelona-spain-2021 description:

On 31 July 2021, a Boeing 737-800 descending through an area of convective activity which was subject to a current SIGMET encountered some anticipated moderate turbulence whilst visually deviating around storm cells without reducing speed. When it appeared possible that the maximum speed may be exceeded because of turbulence, the autopilot was disconnected and a severe pitch up and then down immediately followed resulting in serious injuries to two of the four cabin crew and a passenger. This disconnection was contrary to the aircraft operator’s procedures and to the explicit training received by the pilot involved who was in command.

guid: https://skybrary.aero/accidents-and-incidents/b738-west-southwest-barcelona-spain-2021 uri: https://skybrary.aero/accidents-and-incidents/b738-west-southwest-barcelona-spain-2021 title: A20N / AC11, en-route, northwest of Zurich [German airspace], 2019 link: https://skybrary.aero/accidents-and-incidents/a20n-ac11-en-route-northwest-zurich-german-airspace-2019 description:

On 13 October 2019, an Airbus A320neo inbound to Zurich had been cleared to the lowest available Class ‘C’ airspace level when a light aircraft crossing its intended track below in uncontrolled airspace began to climb into the same Class C airspace without clearance. An ATC Conflict Alert was activated and the controller put the A320 on an avoidance radar heading and safe separation was thereby achieved. The reason for the incursion was not determined but the event was considered yet another example of yet-to-be-addressed airspace infringement risk and a corresponding safety recommendation was made to the State Safety Regulator.

guid: https://skybrary.aero/accidents-and-incidents/a20n-ac11-en-route-northwest-zurich-german-airspace-2019 uri: https://skybrary.aero/accidents-and-incidents/a20n-ac11-en-route-northwest-zurich-german-airspace-2019 title: SF34, manoeuvring, southwest Scotland UK, 2021 link: https://skybrary.aero/accidents-and-incidents/sf34-manoeuvring-southwest-scotland-uk-2021 description:

On 14 September 2021 the crew of a Saab S340B being used for type conversion training purposes were unable to cross start the left engine after it had been temporarily shut down to demonstrate single engine handling performance because the right starter-generator failed. A MAYDAY was declared and after prompt electrical load shedding, sufficient battery power remained to complete a successful diversion. The starter-generator failure was suspected to be attributable to its use whilst in service with a previous operator to support multiple starts at intervals which were insufficient to allow the unit to cool.

guid: https://skybrary.aero/accidents-and-incidents/sf34-manoeuvring-southwest-scotland-uk-2021 uri: https://skybrary.aero/accidents-and-incidents/sf34-manoeuvring-southwest-scotland-uk-2021 title: BK17, vicinity Auckland Islands New Zealand, 2019 link: https://skybrary.aero/accidents-and-incidents/bk17-vicinity-auckland-islands-new-zealand-2019 description:

On 22 April 2019, a Eurocopter-Kawasaki BK-117C-1 helicopter was being positioned for an aeromedical evacuation the following day when it was unintentionally flown into the sea at night. The three crew members were able to evacuate from the partially submerged aircraft before it sank. The accident was attributed to the single pilot’s loss of situational awareness due to loss of visual depth perception when using night vision goggles. The relevant aircraft operator procedures and the applicable regulatory requirements were both found be inadequate relative to the operational risk which the flight involved.

guid: https://skybrary.aero/accidents-and-incidents/bk17-vicinity-auckland-islands-new-zealand-2019 uri: https://skybrary.aero/accidents-and-incidents/bk17-vicinity-auckland-islands-new-zealand-2019 title: UAV, near Imsil-gun South Korea, 2009 link: https://skybrary.aero/accidents-and-incidents/uav-near-imsil-gun-south-korea-2009 description:

On 3 August 2009, control of a rotary UAV being operated by an agricultural cooperative for routine crop spraying in the south western part of South Korea was lost and the remote pilot was fatally injured when it then collided with him. The Investigation found that an inappropriately set pitch trim switch went unnoticed and the consequentially unexpected trajectory was not recognised and corrected. The context was assessed as inadequacies in the operator’s safety management arrangements and the content of the applicable UAV Operations Manual as well as lack of recurrent training for the operators’ qualified UAV remote pilots.

guid: https://skybrary.aero/accidents-and-incidents/uav-near-imsil-gun-south-korea-2009 uri: https://skybrary.aero/accidents-and-incidents/uav-near-imsil-gun-south-korea-2009 title: B734, en-route, west of Meekatharra Australia, 2022 link: https://skybrary.aero/accidents-and-incidents/b734-en-route-west-meekatharra-australia-2022 description:

On 10 June 2022, on reaching the planned FL330 cruise altitude abeam Meekatharra, a Boeing 737-400 crew observed a 340 feet difference between the two primary altimeter readings. The crew did not advise ATC of the breach of RVSM separation minima but after identifying which instrument was in error, they returned uneventfully to their departure point, Perth, where an engineering inspection found residue on all four electrically-heated pitot/static probes. It was found that a few days earlier, an engine ground run without first removing non-standard plastic probe covers had contaminated the probes with cleaning performed prior to release to service.

guid: https://skybrary.aero/accidents-and-incidents/b734-en-route-west-meekatharra-australia-2022 uri: https://skybrary.aero/accidents-and-incidents/b734-en-route-west-meekatharra-australia-2022 title: A346, en-route, Clariden Switzerland, 2018 link: https://skybrary.aero/accidents-and-incidents/a346-en-route-clariden-switzerland-2018 description:

On 6 November 2018, an Airbus A340-600 in the cruise northbound over the Swiss Alps received an overspeed warning after encountering an unexpected wind velocity change but the crew failed to follow the prescribed response procedure. This led initially to a climb above their cleared level and further inappropriate actions were then followed by PAN and MAYDAY declarations as control of the aircraft was briefly lost in a high speed descent to below their cleared level. The operator subsequently enhanced pilot training realism by providing it in a simulator configured for the aircraft variant operated and introduced ‘upset recovery training’.

guid: https://skybrary.aero/accidents-and-incidents/a346-en-route-clariden-switzerland-2018 uri: https://skybrary.aero/accidents-and-incidents/a346-en-route-clariden-switzerland-2018 title: B738, en-route, southeast of Varanasi India, 2021 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-southeast-varanasi-india-2021 description:

On 17 November 2021, shortly after a Boeing 737-800 commenced initial descent into Patna from FL350, a cautionary alert indicating automatic pressurisation system failure was annunciated. When the initial actions of the prescribed non-normal procedure did not resolve the problem, the system outflow valve was fully opened and a rapid depressurisation followed. After this incorrect action, the relevant crew emergency procedures were then comprehensively not properly followed and it was further concluded that the Captain had temporarily lost consciousness after a delay in donning his oxygen mask. The context for the mismanaged response was identified as outflow valve in-service failure.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-southeast-varanasi-india-2021 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-southeast-varanasi-india-2021 title: B77W, en-route, east of Oman, 2021 link: https://skybrary.aero/accidents-and-incidents/b77w-en-route-east-oman-2021 description:

On 12 September 2021, a Boeing 777-300 in the cruise at FL 380 and approaching Oman from the east at night experienced a sudden left engine failure. It was shut down, a PAN call was made and diversion to Muscat made in preference to completing the intended flight to Abu Dhabi. An off-wing examination of the GE90 engine which failed found that the hydro-mechanical unit of the accessory gearbox had malfunctioned in a way which allowed fuel to mix with the engine oil. This failure had not been anticipated in the applicable Fault Identification Manual which was amended accordingly.

guid: https://skybrary.aero/accidents-and-incidents/b77w-en-route-east-oman-2021 uri: https://skybrary.aero/accidents-and-incidents/b77w-en-route-east-oman-2021 title: A320, en-route, near Okayama Japan, 2022 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-near-okayama-japan-2022 description:

On 16 January 2022, an Airbus A320 in the cruise unexpectedly and very briefly encountered light clear air turbulence. Despite being secured in their seat, one passenger sustained a serious injury not assessed by the passenger concerned or the cabin crew as such at the time but which subsequently resulted in hospitalisation with a broken rib. The minor turbulence encountered had included a lateral movement which caused firm impact with the seat armrest. The operators’ comprehensive response included amending the safety briefing and related procedures and introducing a new video on turbulence awareness to be shown immediately after the briefing.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-near-okayama-japan-2022 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-near-okayama-japan-2022 title: E170 / C525, en-route, south of Auxerre France, 2022 link: https://skybrary.aero/accidents-and-incidents/e170-c525-en-route-south-auxerre-france-2022 description:

On 12 January 2022, an Embraer 170 and a Cessna 525 crossed tracks without the prescribed minimum separation with neither ATC nor the Embraer crew being aware. Although ATC had issued acknowledged clearances to keep the Embraer 1,000 feet above the Cessna, it actually passed beneath it violating minimum lateral separation. The underlying cause of the event was found to be an un-rectified recurrent intermittent fault in one of the Cessna’s air data systems. Poor Cessna crew/controller communication during the event, systemically poor safety culture at its operator and shortcomings in the Textron Aircraft Maintenance Manual were considered contributory.

guid: https://skybrary.aero/accidents-and-incidents/e170-c525-en-route-south-auxerre-france-2022 uri: https://skybrary.aero/accidents-and-incidents/e170-c525-en-route-south-auxerre-france-2022 title: B39M, en-route, Beaverton OR USA, 2024 link: https://skybrary.aero/accidents-and-incidents/b39m-en-route-beaverton-or-usa-2024 description:

On 5 January 2024, a Boeing 737-9 which had just departed Portland was climbing through 14,800 feet when there was a loud bang followed by a rapid decompression. The cause - the loss of a fuselage plug fitted at an unused door location - was immediately obvious. An emergency was declared and a landing back at Portland was made after a total of twenty minutes airborne. The Investigation is continuing but has found that the fuselage plug involved was installed without being properly secured and noted that the aircraft had only recently been delivered new to the operator.

guid: https://skybrary.aero/accidents-and-incidents/b39m-en-route-beaverton-or-usa-2024 uri: https://skybrary.aero/accidents-and-incidents/b39m-en-route-beaverton-or-usa-2024 title: A321, north of Mogadishu Somalia, 2016 link: https://skybrary.aero/accidents-and-incidents/a321-north-mogadishu-somalia-2016 description:

On 2 February 2016, an Airbus A321 Boeing 757-200F in the climb after departing from Mogadishu had just passed FL100 when an explosion occurred inside the passenger cabin and led to significant structural damage to a small area of the fuselage which caused cabin depressurisation, the ejection of one passenger and led to three others being seriously injured. The damaged aircraft was recovered to Mogadishu without any further consequences and the explosion was found to have been intentionally caused by the ejected male passenger. A series of Safety Recommendations were issued aimed at improving security checking of passengers boarding flights from Mogadishu.

guid: https://skybrary.aero/accidents-and-incidents/a321-north-mogadishu-somalia-2016 uri: https://skybrary.aero/accidents-and-incidents/a321-north-mogadishu-somalia-2016 title: A320, en-route, southeast of Omaha USA, 2022 link: https://skybrary.aero/accidents-and-incidents/a320-en-route-southeast-omaha-usa-2022 description:

On 19 November 2022 an Airbus A320 was descending below 13,000 feet towards its destination Omaha clear of cloud at night and at 290 knots when an explosive decompression occurred as a result of bird strike damage. An emergency was declared and once on the ground, three locations where the fuselage skin had been broken open were discovered. The structural damage was assessed as substantial and the aircraft was withdrawn from service for major repairs. The birds involved were identified by DNA analysis as migrating Snow or Ross’s Geese, the former of which can weigh up to 2.6kg.

guid: https://skybrary.aero/accidents-and-incidents/a320-en-route-southeast-omaha-usa-2022 uri: https://skybrary.aero/accidents-and-incidents/a320-en-route-southeast-omaha-usa-2022 title: A320 / A320, en-route, east of Nashik India, 2022 link: https://skybrary.aero/accidents-and-incidents/a320-a320-en-route-east-nashik-india-2022 description:

On 21 March 2022, an Airbus A320 level at FL 360 lost separation with another Airbus A320 which continued its descent beyond its cleared level. A predictive conflict alert prompted the controller to issue multiple calls confirming the clearance limit but with no response so when both aircraft tracks crossed at FL 360, lateral separation was reduced to 3.8 nm. It was concluded that the immediate cause of the conflict was the failure of the descending aircraft to respond to ATC alerting calls but that its origin was an undetected incorrect readback of the descent clearance.

guid: https://skybrary.aero/accidents-and-incidents/a320-a320-en-route-east-nashik-india-2022 uri: https://skybrary.aero/accidents-and-incidents/a320-a320-en-route-east-nashik-india-2022 title: B738, en-route, south southwest of Toulouse France, 2015 link: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-southwest-toulouse-france-2015 description:

On 25 February 2015, a Boeing 737-800 encountered severe clear air turbulence as it crossed the Pyrenees northbound at FL 380. Two of the four cabin crew sustained serious injuries and it was decided to divert to Bordeaux where the flight arrived 35 minutes later. The turbulence and its consequences were attributed to the flight’s lateral and vertical closeness to a correctly forecast opposite-direction jet stream core and specifically to allowing cabin service to commence despite being near the boundary associated with severe turbulence following a negative ATC response when asked whether other flights had reported severe turbulence.

guid: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-southwest-toulouse-france-2015 uri: https://skybrary.aero/accidents-and-incidents/b738-en-route-south-southwest-toulouse-france-2015 title: A359, en-route, west southwest of Manila Philippines, 2019 link: https://skybrary.aero/accidents-and-incidents/a359-en-route-west-southwest-manila-philippines-2019 description:

On 21 February 2019, the Captain of an Airbus A350-900 in the cruise en-route to Hong Kong became and remained incapacitated. The First Officer took over control and completed the flight as planned without further event. The Cabin Crew Manager was called to the flight deck and advised and a doctor on board provided medical assistance to the Captain who remained conscious but with slurred speech and was hospitalised on arrival. It was concluded that the response to the situation had been effectively handled and the remainder of the flight was completed in accordance with all applicable procedures and training.

guid: https://skybrary.aero/accidents-and-incidents/a359-en-route-west-southwest-manila-philippines-2019 uri: https://skybrary.aero/accidents-and-incidents/a359-en-route-west-southwest-manila-philippines-2019 title: B748, en-route, Persian Gulf, 2021 link: https://skybrary.aero/accidents-and-incidents/b748-en-route-persian-gulf-2021 description:

On 22 March 2021, the pilots of a Boeing 747-8F which had just reached its initial cruise level after departing Dubai observed smoke and sparks coming from the window heating system and declared a PAN advising their intention to dump fuel and return to Dubai. With the faulty system switched off, this was accomplished without further event. It was found that the cause of the system malfunction was a design-related vulnerability with a history of recurrence which had not been adequately addressed by the aircraft manufacturer and the FAA as safety regulator following relevant NTSB Safety Recommendations made in 2007.

guid: https://skybrary.aero/accidents-and-incidents/b748-en-route-persian-gulf-2021 uri: https://skybrary.aero/accidents-and-incidents/b748-en-route-persian-gulf-2021 title: B772, en-route, near Denver USA, 2021 link: https://skybrary.aero/accidents-and-incidents/b772-en-route-near-denver-usa-2021 description:

On 20 February 2021, a Boeing 777-200 climbing through 12,500 feet experienced a sudden right engine failure and fire shortly after thrust had been increased before entering airspace where moderate turbulence was expected. Despite actioning the corresponding drills, the fire did not go out until shortly before landing back at Denver. Engine debris fell to the ground over a wide area, fortuitously with only damage and no injuries. The failure was found to have been initiated by the fatigue failure of a single fan blade after required routine inspections had failed to find early-stage evidence of such a risk.

guid: https://skybrary.aero/accidents-and-incidents/b772-en-route-near-denver-usa-2021 uri: https://skybrary.aero/accidents-and-incidents/b772-en-route-near-denver-usa-2021