Accident and Serious Incident Reports: WX
Accident and Serious Incident Reports: WX
Definition
Reports relating to accidents and serious incidents which involved weather or related atmospheric conditions as a significant causal factor.
The reports are grouped together below in subcategories. Weather related events are mostly related to the occurrence or risk of a loss of control because of the effects of significant in flight icing or in flight turbulence. The turbulence case can involve en route or low level flight, the latter especially in respect of approach and landing. Many adverse weather events are associated with Cumulonimbus (Cb) cloud or phenomena associated with them such as the occurrence of Hail, Microbursts or Tornados.
In-Flight Airframe Icing
On 9 August 2024, an ATR 72-500 at FL170 encountered weather conditions which led to airframe icing. Indicated airspeed decreased quickly without corrective action despite corresponding alerts and almost immediately after an ‘INCREASE SPEED’ alert during a turn, the aircraft stalled eventually entering a flat spin until impacting terrain in a residential area. Impact and a post-crash fire destroyed the aircraft and all occupants were killed. The Investigation is continuing.
On 20 January 2020, a DHC8-300 encountered severe icing conditions, and both engines successively failed during its approach to Bergen. The automatic ignition system restarted the engines but for a short time the aircraft was completely without power. It was concluded that ice had accreted on and then detached from the engine air inlets and either entered the combustion chamber partly melted and caused a flameout or disrupted the airflow into the engine sufficiently to stall it. Shortcomings were identified in the operator’s documentation for operation in icing conditions and further review of weather radar use by ATC was recommended.
On 8 February 2021, an Embraer 500 Phenom 100 (9H-FAM) crew lost control of their aircraft shortly before the intended touchdown when it stalled due to airframe ice contamination. The resulting runway impact collapsed the nose and main gear, the latter causing fuel leak and resultant fire as the aircraft slid along the runway before veering off it. The Investigation found that flight in icing conditions during the approach had not been accompanied by the prescribed use of the airframe de-icing system and that such non compliance appeared to be routine and its dangers unappreciated.
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.
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.
In-Flight Icing - Piston Engine
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.
On 9th October 2003, a Cessna 172, suffered loss of power and made a forced landing after experiencing Carburettor Icing, over Toronto, Canada
In-Flight Icing - Turbine Engine
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.
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.
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.
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.
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.
En Route In-Cloud Air Turbulence
On 28 May 2021, a Boeing 767-300 climbing over central South Korea with extensive cloud including embedded cumulonimbus present and near an active transverse Jetstream axis below the intended cruise altitude suddenly encountered severe turbulence as it re-entered cloud on a resumed climb. A serious injury occurred to one of the cabin crew who was unable to return to her crew seat and secure herself because of the flight crew’s short notice that turbulence risk would increase from moderate to severe. Opportunities for further improvement in both aircrew turbulence risk prevention procedures and pilots’ turbulence risk response training were identified.
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.
On 25 July 2021, a Boeing 737-800 which had previously been manoeuvring visually around storm cells over the Alps during the initial descent into Nice turned back on track believing the avoidance action was complete but was then unable to avoid penetrating a further cell during which severe turbulence caused a serious injury to one of the cabin crew and a lesser injury to another. Multiple aircraft in the area had been simultaneously requesting track deviations at the time with ATC displays not showing weather returns. In the absence of plans to introduce this, a corresponding safety recommendation was made.
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.
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.
Hail Damage
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.
On 26th May 2003, a British Midland A321 suffered severe damage from hail en route near Vienna.
Volcanic Ash Effects
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.
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.
Sand/Dust Storm
none on SKYbrary
Fog
On 4 February 2023, a Boeing 767-300 which had initiated a night go-around in freezing fog passed within 115 feet of a Boeing 737-700 taking off from the same runway. The aircraft had been respectively cleared to land and takeoff by the same controller but on sighting the 737 on the runway ahead, the 767 crew deemed a go around was necessary to avoid a ground collision. The experienced controller’s poor judgement was attributed to a combination of expectation bias, lack of awareness of a predictable delay to the 737’s departure and absence of any training in low visibility operations.
On 23 January 2020, a Bombardier CRJ700 making a HUD-supported manual Cat 3a ILS approach to Lyon Saint-Exupéry in freezing fog conditions deviated from the required flight path localiser and reached a minimum of 265 feet agl before a go around was initiated without initially being flown in accordance with standard procedures. The Captain involved was relatively new to type and had not previously flown such an approach in actual low visibility conditions. The Investigation was not able to determine exactly what contributed to the approach and initial go around being misflown but identified a number of possible contributors.
On 18 March 2016 at night and with visibility just above the minimum permitted for landing with thick fog patches present, an Airbus A319 entered the runway at Cheongju contrary to its clearance as a Boeing 737-800 was landing on it as cleared. Only when the 737 crew saw the other aircraft ahead when still at high speed were they able to initiate an immediate lateral deviation and avoid a collision by creating a 3 metre separation between the two aircraft. The Investigation found that the A319 had exceeded its clearance and remained on the Ground frequency but noted poor controller phraseology.
On 29 November 2017, a Boeing 737-900 on an ILS approach at Atlanta became unstable after the autothrottle and autopilot were both disconnected and was erroneously aligned with an occupied taxiway parallel to the intended landing runway. A go-around was not commenced until the aircraft was 50 feet above the ground after which it passed low over another aircraft on the taxiway. The Investigation found that the Captain had not called for a go around until well below the Decision Altitude and had then failed to promptly take control when the First Officer was slow to begin climbing the aircraft.
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.
Clear Air Turbulence
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.
On 5 December 2021, an Airbus A359-900 crew encountered a very brief episode of unexpected clear air turbulence associated with visible signs of convective weather in the vicinity. Not having had prior warning, the senior cabin crew member fell and was seriously injured. The investigation concluded that the risk of turbulence prevailing for the location and season as the end of daylight approached was greater than perceived by the pilots, despite their familiarity with the local area and its weather. The investigation further concluded that releasing the cabin crew from their previously secured positions had been inappropriate.
On 16 January 2022, an Airbus A320 in cruise unexpectedly and very briefly encountered light clear air turbulence. Despite being secured in a seat, one passenger sustained a serious injury not assessed as such by the passenger or the cabin crew 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’ response included amending the safety briefing and related procedures and introducing a new video on turbulence awareness to be shown immediately after the briefing.
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.
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.
Precipitation-limited In Flight Vision
On 24 February 2020, a Sikorsky S92 crew departing at night from an oil rig platform in the Norwegian sector of the North Sea in adverse weather conditions temporarily lost pitch control of their helicopter after both pilots became spatially disorientated prior to reaching the minimum speed for autopilot engagement. Recovery was successful and the remainder of the flight was uneventful but the Investigation concluded that operator procedures were insufficiently robust and that helicopters engaged in offshore operations could usefully be equipped with low speed flight modes to mitigate the consequences of pilot spatial disorientation during low level manoeuvring.
On 11 February 2022 an Airbus A320 making a visual approach to Guadeloupe at night was advised by ATC of a descent below the minimum safe altitude after continuing the approach after visual reference was temporarily lost. A repeat of this warning by ATC prompted crew recognition that the aircraft was not on the required approach track or profile and a go around was initiated from 460 feet agl. The decision to attempt a visual approach in unsuitable circumstances and a delay in recognising the need for a go-around were found to have been symptomatic of poor tactical decision making.
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.
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.
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.
Strong Surface Winds
On 24 February 2020, a Sikorsky S92 crew departing at night from an oil rig platform in the Norwegian sector of the North Sea in adverse weather conditions temporarily lost pitch control of their helicopter after both pilots became spatially disorientated prior to reaching the minimum speed for autopilot engagement. Recovery was successful and the remainder of the flight was uneventful but the Investigation concluded that operator procedures were insufficiently robust and that helicopters engaged in offshore operations could usefully be equipped with low speed flight modes to mitigate the consequences of pilot spatial disorientation during low level manoeuvring.
On 25 October 2022, a Boeing 777-300ER encountered deteriorating weather conditions after initiating a delayed arrival diversion from Singapore Changi to nearby Batam where four approaches were flown and a ‘MAYDAY Fuel’ declared before a landing was achieved. By this time, the fuel remaining was “significantly below final reserve” although the actual figure was not published in the Investigation Report. It was concluded that the delay in commencing the diversion and the inappropriate attempt to perform an autoland on RWY04 at Batam airport by the flight crew contributed to the potentially hazardous circumstances.
On 7 August 2020, a Boeing 737-800 making its second attempt to land at Calicut off a night ILS approach with a significant tailwind component became unstabilised and touched down approximately half way down the 2,700 metre-long wet table top runway and departed the end of it at 85 knots before continuing through the RESA and a fence and then dropping sharply onto a road. This caused the fuselage to separate into three pieces with 97 of the 190 occupants including both pilots being fatally or seriously injured and 34 others sustaining minor injuries. Significant fuel spillage occurred but there was no fire.
On 9 January 2020, a Fokker 100 overran the landing runway at Newman. The Investigation found that a stabilised approach had preceded a correctly-positioned touchdown and attributed the overrun to a combination of the approach speed required by the prevailing crosswind and runway surface conditions. It was noted that whilst the aircraft operator did not permit contaminated runway operations, they had not provided their pilots with any guidance as to when contamination might exist and also that advisory material published by the safety regulator did not cover the risk of reduced braking performance during landings in moderate or heavy rainfall.
On 17 September 2020, a Bombardier Global 6000 which had completed a circling approach to land at Biggin Hill in day VMC touched down with an inappropriate pitch and roll attitude which caused the right wingtip to contact the runway surface. The Investigation found that the landing technique just before touchdown was not in accordance with the manufacturer’s crosswind landing technique although the roll rate achieved could not be accounted for by the roll control input alone and was probably increased by localised wind velocity variations despite the absence of any such variations being reported by ATC.
Lightning Damage
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.
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.
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.
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.
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.
Low Level Windshear
On 21 October 2020, an Embraer ERJ170 on short final at Paris CDG responded to a windshear warning by breaking off the approach and climbing. The warning soon stopped but the aircraft drifted sideways in the strong crosswind towards the adjacent parallel runway from which an Airbus A320 had just taken off. A Short-Term Conflict Alert on the controller's display was accompanied by a TCAS RA event triggered for both aircraft. The Investigation was concerned about the implications of failure to climb straight ahead from parallel runways during unexpected go-arounds. Safety Recommendations were made on risk management of parallel runway operations by both pilots and safety regulators.
On 6 December 2018, a Boeing 737-700 overran the 1,770 metre-long landing runway at destination by 45 metres after entering the EMAS. Normal visibility prevailed but heavy rain was falling and a 10 knot tailwind component existed. The event was attributed to the pilots’ continuation bias in the face of deteriorating conditions and a late touchdown on the relatively short runway. A lack of guidance from the operator on the need for pilots to re-assess the validity of landing data routinely obtained at the top of descent was identified.
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.
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.
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.
In Flight Icing - Turboprop Engine
none on SKYbrary
In Flight Icing - Jet Engine
none on SKYbrary
Mountain Wave/Rotor Conditions
On 23 February 2016, a Boeing 737-800 departing New Chitose encountered sudden-onset and unforecast heavy snowfall whilst taxiing out. When the right engine ran down and cabin crew reports of unusual smells in the cabin and flames coming from the right engine were received, it was decided that an emergency evacuation was required. During this evacuation three passengers were injured, one seriously. The engine fire was found to have been in the tailpipe and caused by an oil leak due to engine fan blade and compressor icing which had also led to vapourised engine oil contaminating the air conditioning system.
Triggered Lightning Strike
none on SKYbrary
Layer Cloud Airframe Icing
On 21 October 2020, an Embraer ERJ170 on short final at Paris CDG responded to a windshear warning by breaking off the approach and climbing. The warning soon stopped but the aircraft drifted sideways in the strong crosswind towards the adjacent parallel runway from which an Airbus A320 had just taken off. A Short-Term Conflict Alert on the controller's display was accompanied by a TCAS RA event triggered for both aircraft. The Investigation was concerned about the implications of failure to climb straight ahead from parallel runways during unexpected go-arounds. Safety Recommendations were made on risk management of parallel runway operations by both pilots and safety regulators.
On 6 December 2018, a Boeing 737-700 overran the 1,770 metre-long landing runway at destination by 45 metres after entering the EMAS. Normal visibility prevailed but heavy rain was falling and a 10 knot tailwind component existed. The event was attributed to the pilots’ continuation bias in the face of deteriorating conditions and a late touchdown on the relatively short runway. A lack of guidance from the operator on the need for pilots to re-assess the validity of landing data routinely obtained at the top of descent was identified.
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.
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.
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.
Related Articles
For all accident reports held on SKYbrary, see the main section on Category:Accidents and Incidents.
Categories
