The Aviation Herald Last Update: Saturday, Sep 19th 2020 10:27Z

26003 Articles available

Events from Jun 19th 1999 to Sep 19th 2020 www.avherald.com Incidents and News in Aviation List by: Filter: Crash: Flydubai B738 at Rostov on Don on Mar 19th 2016, lost height on go around after stabilizer moved nose down following holding for 2 hours

By Simon Hradecky, created Saturday, Mar 19th 2016 04:42Z, last updated Tuesday, Aug 21st 2018 15:22Z A Flydubai Boeing 737-800, registration A6-FDN performing flight FZ-981 from Dubai (United Arab Emirates) to Rostov on Don (Russia) with 55 passengers and 7 crew, had aborted the approach to Rostov's runway 22 at 01:41L (22:41Z) due to weather and entered a hold initially at 8000 feet, after 30 minutes at 8000 feet the aircraft climbed to FL150. After about 2 hours of holding the aircraft commenced another approach to Rostov's runway 22, winds from 240 degrees at 27 knots (14 m/s) gusting 42 knots (22 m/s), the crew announced a go around, the aircraft however impacted ground just off the runway at about 03:43L (00:43Z), broke up and burst into flames. There are no survivors.



The aircraft carried fuel for trip, contingency, alternate, final fuel reserve (30 minutes) and additional holding for about 2:30 hours, total fuel for an endurance of about 8.5 hours. The aircraft had been airborne until time of impact for 06:02 hours.



Russia's Ministry of Emergencies reported that more than 700 people and more than 100 vehicles have been deployed to the crash scene for search and recovery operations following the aircraft crash. The aircraft struck a wing onto the runway on touch down and began to disintegrate.



On Mar 20th 2016 the Ministry of Emergencies reported that search and recovery operations have been finished, there is still work in progress to support the investigation and subsequent removal of wreckage. All parts of the wreckage are still in place, none was moved.



On Mar 21st 2016 the Ministry of Emergencies reported, that the wreckage has been removed from the runway over night, the runway and infrastructure have been repaired, and first flights, in particular flights for the Ministry, landed on the runway without any anomalies in the morning of Mar 21st.



Russia's MAK (Interstate Aviation Committee, Accident Investigation Board) reported the aircraft broke up and burst into flames upon touching ground, debris is spread over a large area (several kilometers). An investigation has been opened. Both black boxes were recovered in good condition, work to read out the blackboxes has already started.



On Mar 20th 2016 the MAK reported both recorders received substantial mechanical damage, the memory modules are being removed from the recorders and are being prepared for read out, the preparatory work is expected to be finished by end of Mar 20th 2016. Late Mar 20th 2016 the MAK added, that the flight data recorder has been successfully read out and contains the data in good quality until impact of the aircraft, works to analyse the data have already started. The cockpit voice recorder memory module has received mechanical damage requiring repairs, checks of whether the non-volatile memory is still readable are going to commence after the repairs.



In the evening of Mar 21st 2016 the MAK reported that the repairs were successful and the cockpit voice recorder has been read out and contains good quality recordings until impact. The recording is now being transcribed and analysed.



On Mar 29th 2016 the MAK condemned all "leaked" information reported by Russian media as false and stated, that no information whatsoever has been leaked from the investigation. About one hour of CVR has been transcribed so far including the crew communication in the final stages of the flight. Mechanical reconstruction as well as preliminary analysis of the flight data recorder so far do not suggest any malfunction of the engines of the aircraft and no failures of aircraft systems or components, the aircraft had all necessary documentation and certificates of airworthiness, passed all required maintenance and was airworthy at the time of departure. The MAK is now undertaking mathematical modelling of the aircraft's flight trajectory in combination with the sounds available on the CVR. The identification of wreckage pieces and mechanical reconstruction of the aircraft continues.



On Apr 5th 2016 Russia's Ministry of Transport reported that on first approach to runway 22 the aircraft went around, the crew reported a wind shear on final approach, climbed to FL050 then FL080 and entered a hold to wait for improvement of weather. The crew subsequently requested and was cleared to FL150 in the hold. When air traffic control provided information that the visibility was 5000 meters, cloud ceiling at 630 meters/2000 feet, winds from 230 degrees at 13m/s gusting 18m/s (25 knots gusting 35 knots), no wind shear, the crew requested another approach clearance. On final approach at about 220 meters/720 feet the crew went around again and climbed, at 900 meters/3000 feet the stabilizer moved nose down causing the aircraft to stop climbing at about 1000 meters/3330 feet and entering a descent. The aircraft impacted ground about 120 meters from the runway threshold. Preliminary examination results of flight data and cockpit voice recorder do not reveal any evidence of a technical malfunction of engines or aircraft systems or any evidence of an explosion. The investigation is focussing on how the pitch control system works and crew actions during the go around. The captain (ATPL, 5,965 hours total, 2,597 hours on type) was certified for CATIIIa approaches.



On Apr 8th 2016 the MAK reported in Russian, that the actual weather conditions were as forecast and reported by the weather systems, all weather instruments were working normally. According to flight data recorder the first approach was performed in manual control in adverse weather conditions with winds from 230 degrees at 13m/s gusting 18m/s (25 knots gusting 35 knots), light rain, mist and light to moderate windshear. At an altitude of 340 meters/1100 feet the crew initated a go around due to a sudden change of direction and strength of wind and entered a hold to wait for improvement of weather conditions. The second approach was also flown in manual control, at a height of 220 meters/720 feet about 4km/2.2nm from the runway threshold the crew initiated a go around again selecting TOGA on the engines. At an altitude of 900 meters/2950 feet there were simultaneous actions, the crew returned the flight controls to neutral and the pitch trim moved 5 degrees nose down causing a rapid nose down movement of the aircraft resulting in -1G of vertical acceleration. The subsequent crew actions did not permit to pull the aircraft out of the resulting nose dive, the aircraft impacted ground at a speed of about 600kph/325 knots with the nose more than 50 degrees below the horizont. The MAK has completed on site work and selection of debris/units for examination of the performance of the longitudinal control system (pitch control). The MAK is further looking into the performance of the flight crew and training of the flight crew, according to documentation forwarded by UAE's GCAA the pilots were properly trained, had sufficient experience and were in possession of all needed certificates. The MAK is still in the process of analysing, transcribing and translating the onboard cockpit voice recorder. In the MAK's English version of the update of Apr 8th 2016 two differences are being noted: the simultaneous actions were a nose down input by the crew and a trim 5 degrees nose down, and the transcription of the voice recorder is said to be complete, clarification of content as well as translation and identification of speakers ongoing only.



The NTSB announced on Mar 19th 2016, that they are going to assist the MAK in the investigation.



On Mar 19th 2016 Boeing announced to assist the MAK's investigation as technical advisors.



The airline confirmed the aircraft crashed on landing in Rostov, there were no survivors. In a press conference the chairman added, that the captain had 5,900 hours of flying experience, the first officer 5,700 hours. Flydubai have dispatched an emergency response team to Rostov to assist families and to assist the investigation.



Radar data suggest the aircraft on final approach was to the left of the localizer and just to the left of the left runway edge and corrected to the right while over the runway bringing the aircraft just within the runway edges moments before ground contact.



Metars:

URRR 190430Z 26008G15MPS 230V300 4600 -SHRA BKN010 BKN033CB OVC100 05/04 Q0997 RESHRA R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE740/0987

URRR 190400Z 26008G13MPS 3300 -SHRA BKN012 BKN033CB OVC100 06/04 Q0997 RESHRA R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE740/0987

URRR 190330Z 25010G16MPS 230V290 3800 -SHRA BKN011 BKN030CB OVC100 06/04 Q0997 R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE740/0987

URRR 190300Z 25011G18MPS 3900 -SHRA BKN011 BKN030CB OVC100 06/04 Q0997 R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE740/0987

URRR 190230Z 25011G16MPS 4700 -SHRA BKN013 BKN031CB OVC100 06/04 Q0997 RESHRA R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE740/0987

URRR 190200Z 25011MPS 4600 1700SW SHRA BKN014 BKN032CB OVC100 06/04 Q0997 R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE740/0987

URRR 190130Z 24012G18MPS 4400 1700SW SHRA BKN013 BKN032CB OVC100 06/04 Q0997 R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE740/0987

URRR 190100Z 24014G22MPS 3800 -SHRA BKN014 BKN033CB OVC100 06/04 Q0997 R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE740/0987

URRR 190030Z 24012G19MPS 6000 -SHRA SCT018 BKN036CB OVC100 06/04 Q0998 R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE741/0988

URRR 190000Z 24010MPS 8000 -SHRA SCT017 BKN040CB OVC100 06/03 Q0998 WS R22 R22/290046 TEMPO 25015G20MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE741/0988

URRR 182330Z 24012MPS 3900 -SHRA SCT019 BKN036CB OVC100 06/03 Q0999 WS R22 R22/290046 TEMPO 25015G20MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE741/0989

URRR 182300Z 24009G15MPS 4500 -SHRA SCT017 BKN036CB OVC100 05/03 Q0999 WS R22 R22/290046 TEMPO 25015G20MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE742/0989

URRR 182230Z 25011G17MPS 4200 -SHRA SCT016 BKN033CB OVC100 06/03 Q1000 R22/290046 TEMPO 25015G20MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE742/0990

URRR 182200Z 25011MPS 5000 -SHRA SCT013 BKN033CB OVC100 06/04 Q1000 WS R22 R22/290046 TEMPO 25013G18MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE742/0990

URRR 182130Z 25009G15MPS 220V280 5000 -SHRA SCT013 BKN030CB OVC100 06/03 Q1000 R22/290046 TEMPO 25013G18MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE743/0990

URRR 182100Z 25008MPS 7000 -SHRA SCT011 BKN033CB OVC100 06/03 Q1000 R22/290057 TEMPO 25013G18MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE743/0990

URRR 182030Z 24008MPS 6000 -SHRA SCT016 SCT033CB OVC100 06/03 Q1001 R22/290057 TEMPO 25013G18MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE743/0991

URRR 182000Z 25007MPS 7000 -SHRA SCT017 SCT036CB OVC100 07/03 Q1001 R22/290057 TEMPO 25013G18MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE743/0991



ATC recording (Recording: Donday Rostov):

https://www.youtube.com/watch?v=-4m0FcsLnEg



Surveillance camera showing go around and descent (Video: Donday Rostov):

https://www.youtube.com/watch?v=7a2MJQbc5Zg



Surveillance camera, view from westsouthwest:

https://www.youtube.com/watch?v=rcDGu48F4PE



Surveillance camera at a car sale captured the event:

https://www.youtube.com/watch?v=_80M0aCcQyU



Reconstruction work in progress (Photo: MAK):





Aerial Overview of crash site (Photo: APA/Maxim Grigoryev/Tass):





Larger pieces of debris (Photos: APA):









Debris field near aiming markers runway 22, view towards right hand edge of runway (Photo: APA):





Debris field near aiming markers runway 22, view towards left hand edge of runway (Photo: APA):





Debris field near aiming markers runway 22, view towards point of first impact/left edge of runway (Photo: APA):





Scene in the following daybreak:









Map, arrow points to surveillance camera off the top of map (Graphics: AVH/Google Earth):







By Simon Hradecky, created Wednesday, Nov 27th 2019 10:25Z, last updated Wednesday, Nov 27th 2019 10:41Z



The fatal air accident to the Boeing 737-8KN A6-FDN aircraft occurred during the second go around, due to an incorrect aircraft configuration and crew piloting, the subsequent loss of PICs situational awareness in nighttime in IMC. This resulted in a loss of control of the aircraft and its impact with the ground. The accident is classified as Loss of Control In-Flight (LOC-I) occurrence.



Most probably, the contributing factors to the accident were:



- the presence of turbulence and gusty wind with the parameters, classified as a moderateto-strong windshear that resulted in the need to perform two go-arounds;



- the lack of psychological readiness (not go-around minded) of the PIC to perform the second go-around as he had the dominant mindset on the landing performance exactly at the destination aerodrome, having formed out of the emotional distress after the first unsuccessful approach (despite the RWY had been in sight and the aircraft stabilized on the glide path, the PIC had been forced to initiate go-around due to the windshear warning activation), concern on the potential exceedance of the duty time to perform the return flight and the recommendation of the airline on the priority of landing at the destination aerodrome;



- the loss of the PICs leadership in the crew after the initiation of go-around and his confusion that led to the impossibility of the on-time transition of the flight mental mode from approach with landing into go-around;



- the absence of the instructions of the maneuver type specification at the go-around callout in the aircraft manufacturer documentation and the airline OM;



- the crews uncoordinated actions during the second go-around: on the low weight aircraft the crew was performing the standard go-around procedure (with the retraction of landing gear and flaps), but with the maximum available thrust, consistent with the Windshear Escape Maneuver procedure that led to the generation of the substantial excessive nose-up moment and significant (up to 50 lb/23 kg) pushing forces on the control column to counteract it;



- the failure of the PIC within a long time to create the pitch, required to perform goaround and maintain the required climb profile while piloting aircraft unbalanced in forces;



- the PICs insufficient knowledge and skills on the stabilizer manual trim operation, which led to the long-time (for 12 sec) continuous stabilizer nose-down trim with the subsequent substantial imbalance of the aircraft and its upset encounter with the generation of the negative G, which the crew had not been prepared to. The potential impact of the somatogravic pitch-up illusion on the PIC might have contributed to the long keeping the stabilizer trim switches pressed;



- the psychological incapacitation of the PIC that resulted in his total spatial disorientation, did not allow him to respond to the correct prompts of the F/O;



- the absence of the criteria of the psychological incapacitation in the airline OM, which prevented the F/O from the in-time recognition of the situation and undertaking more decisive actions;



- the possible «operational» tiredness of the crew: by the time of the accident the crew had been proceeding the flight for 6 hours, of which 2 hours under intense workload that implied the need to make non-standard decisions; in this context the fatal accident occurred at the worst possible time in terms of the circadian rhythms, when the human performance is severely degraded and is at its lower level along with the increase of the risk of errors.



The lack of the objective information on the HUD operation (there were no flight tests of the unit carried out into the entire range of the operational G, including the negative ones; the impossibility to reproduce the real HUD readings in the progress of the accident flight, that is the image the pilot was watching with the consideration of his posture in the seat trough the stream video or at the FFS) did not allow making conclusion on its possible impact on the flight outcome. At the same time the investigation team is of the opinion that the specific features of the HUD indication and display in conditions existed during final phase of the accident flight (severe turbulence, the aircraft upset encounter with the resulting negative G, the significant difference between the actual and the target flight path) that generally do not occur under conditions of the standard simulator sessions, could have affected the situational awareness of the PIC, having been in the highly stressed state.



The MAK provided lenghty analysis spanning 66 pages (starting page 104, ending page 169).



The investigation analysed that the crew was well rested The MAK wrote:



The analysis of compliance of the work and rest schedule within a record period (28 consecutive days) did not identify any violations. The crew had a sufficient amount of the preflight rest. As per the submitted data, the Fatigue Management System is implemented in the airline. The system encourages the fatigue-related confidential reports by the crewmembers for any stage of the flight operations (the preflight, in-flight, post-flight one). For a number of quantitative indicators the system goes beyond the national aviation legislation (that is it ensures the improved conditions for the crewmembers). Since 2009, the airline has accumulated 450 000 flights with a total flight time of more than 1 million hours. Within the period, 70 fatigue-related confidential reports were submitted. The majority of them were proactive by nature  as the crewmembers reported the fatigue presence and were removed from duty until they felt fit for flight operations.



The weather was no factor into the accident. The MAK wrote: "The forecast and actual weather en route, for the Rostov-on-Don destination aerodrome and the alternative aerodromes of Trabzon (LTCG) and Volgograd (URWW) did not impede the performance of the flight mission and met the IFR."



The MAK analysed that the first approach to Rostov was aborted and a go around initiated after the crew received an automatic call "Go-Around, Windshear ahead" warning at about 1100 feet, which had been generated by the Predictive Windshear warning system located in the weather radar (the reactive windshear warning system resides in the EGPWS and activates when the aircraft is in an actual windshear situation). The MAK wrote: "It was an almost instant response by the crew, about 1 s from the aural message trigger! This is the evidence of the crew having been prepared for such kind of events and well trained on the simulator as for the practice of actions in windshear. Most likely, the HUD had a positive effect at that, too, as the windshear warning is very vividly noticeable." with reference to the initiation of the go-around.



The MAK analysed that the captain initiated the go around as a windshear escape maneouver by applying maximum thrust but leaving the aircraft configuration unchanged (gear remaining down, flap setting remaining unchanged). The MAK wrote: "Initially in 10 sec, the PIC reached the pitch of 14 15º, following the HUD commands and the FCOM and QRH guidance. To counteract the excessive pitch-up moment, generated at the engine thrust increase to maximum, the PIC was forced to move the control column significantly forward."



The aircraft was to climb 1200 feet for the go around only, 1000 feet below the target altitude the ALT ACQUIRE mode activated for the flight director. The MAK wrote:



After the activation of the ALT ACQUIRE mode, without being cleared for further climb, the PIC started to reduce pitch with the additional deflection of the control column to nose-down (up to 8.5° with the maximum deflection available of 13.75) and, consequently, with the associated application of additional pushing forces. The actions in question with the engines on maximum thrust resulted in the increase of airspeed. The F/O drew the PICs attention to the need of monitoring the speed.



At the moment the Flight Path Symbol on HUD was higher than Guidance Cue, that is to maintain the target flight path the additional control inputs to nose-down were required. With the control column position unchanged the PIC, in addition, pressed the trim switches on the control wheel for about 4 s to nose-down (the angle of deflection of the stabilizer was changed for 1.8º) that resulted in the pitch reduction up to 3-4º and additional acceleration.



As the result the IAS exceeded the limit value (with flaps, extended on 30°, Vfe is 175 kt) and TE Flap Load Relief was activated. The flaps automatically retracted to 25 (the flap handle remained at the 30 detent). It should be noted that at the initiation of go-around IAS was equal to 160 kt that is the margin to the limit (with no flap load relief) at the performance of Windshear Escape Maneuver amounted to 15 kt.



At 22:42:34, the aircraft reached the target altitude of 2300 ft and, despite all the actions by the crew, continued to climb. The PIC, without being cleared for further climb, reduced the thrust (down to 83 % N1), although the windshear warning was still displayed. The reduction of the engines thrust led to the reduction of the pitch-up moment. The control column was returned to an almost neutral position.



The IAS had continued to increase for a while (the maximum reached value was 182 kt), what the F/O drew the PICs attention to again.



Subsequently the pilots discussed the overspeed condition, it remained unclear however, whether any of them had recognized the flaps relief.



While the aircraft entered a hold to wait for improvement of weather a number of other aircraft attempted the approach to Rostov and went around reporting windshear too.



The captain decided to attempt another approach following following considerations:



1) The improvement of weather conditions that had been monitored by the crew as far back as the point of go-around allowed hoping for a successful approach after a certain time.



2) The sufficient quantity of fuel allowed to proceed the holding pattern not less than 2 hours and did not constitute the time pressure.



3) The actual weather and the forecast weather at the alternate aerodromes (Volgograd and Mineralnye Vody) were favorable, which did not involve hasty actions either.



4) The aircraft was in immediate proximity to the Rostov-on-Don destination aerodrome, with radio and navigation aids set and ready for approach.



Taking the decision to perform another approach the PIC, most probably, took into account that in case of landing at the Rostov-on-Don airport the loss of time in the holding area (about 2 hrs) would not be crucial. The passengers will be delivered to destination; it will still be possible to perform the return flight, as the duty time will not exceed the allowed value. The potential diversion to the alternate aerodrome would entail many problems: the overnight stop and the associated significant delay of the flight, the passengers accommodation, the breach of the operational schedule of the aircraft, the other expenses both for the airline and for the crew. These circumstances could have enhanced the motivation of the PIC to perform landing right at the destination airport (Rostov-on-Don). The PIC undertook every possible step to complete the main task, that is to deliver passengers to destination.



The captain discussed the decision with dispatch via Satcom for a considerable time, the company supported the decision by the captain. Following the second approach the airline recommended to divert to Mineralnye Vody and transmitted a flight plan for the 270nm trip taking 44 minutes and requiring 1728 kg of fuel. The crew briefed the diversion to Mineralnye Vody in case of another go around and again briefed the windshear escape maneouver.



The MAK analysed:



In this context, the PICs decision to proceed a holding pattern for another approach under the actual circumstances had been the best possible and reasoned decision. This very decision was coordinated with the airline. Taking into consideration the sufficient quantity of fuel to hold and divert to an alternate aerodrome, actual weather and favorable forecast as for the alternate aerodrome, this solution did not pose risks and did not threaten the successful outcome of the flight. The crew undertook all the necessary steps both for the successful landing at the destination aerodrome and the diversion to an alternate aerodrome.



1:40 hours after the first go around and 21 minutes prior to impact ATC advised the crew that the weather office had not advised about any windshear on the runway (previous weather reports had forecasted moderate windshear). The captain decided to attempt the approach, coordinated the diversion to Mineralnye Vody in case of a go-around with the controller, the aircraft left the hold and positioned for the approach, Vref had been determined at 133 KIAS, the captain applied a 20 knots wind correct and thus set Vapp to 153 KIAS. The MAK analysed that the crew had "appropriately identified the approach

speed." and added: "At the same time the crew, having in mind the difficulties during the first go-around, coordinated with the controller that in case of go-around they would immediately climb FL080."



The HUD was switched to an IMC mode. The MAK analysed based on engineering simulations that the aircraft performance had not been impaired by icing. The crew configured the aircraft for landing and performed the ILS approach to runway 22. The aircraft intercepted the glideslope while maintaining 2250 feet MSL, wind information from tower indicated winds from 230 degrees at 12m/s (23 knots) gusting 18m/s (35 knots). Descending through 2165 feet the captain disengaged the autopilot, descending through 1960 feet the autothrust was disengaged. The landing checklist was performed.



Descending through 1000 feet the aircraft was nearly stabilized with all parameters within limits, the captain announced "stabilizing now", the MAK analysed probably referring to the IAS of 163 KIAS 10 knots above Vapp.



The MAK analysed:



The aircraft was flown a little bit higher of glideslope (0.3 0.2 dots), and the PIC was applying the corrective pushing movements on the control column to maintain the glide path descent more precisely, along with that the thrust (N1) was increased from 65% to 70%. Over the same moment the aircraft encountered wind gust. The combination of these three factors resulted in the IAS, after decreasing to the target value of 153 kt, increase within a second for 15 kt (from 153 to 168 kt), in 2 next seconds it additionally increased up to 176 kt. In such a way the actual speed exceeded the target one (153 kt) for more than 20 kt. This overspeed was responded by the F/O at 00:40:49: «Check the speed». It is the overspeed for a considerable value that, most probably, was the reason for the PIC to make decision on go-around. The PIC took the decision right away, called it out to the F/O and similarly was responded immediately.



At 00:40:50 the TO/GA mode was activated with the power levers advanced to full thrust.



With the thrust levers advanced to full thrust rather than remaining at TOGA setting the captain probably again initiated the "windshear escape maneouver", however, no windshear warning had occured (unlike the first approach). The first officer therefore queried whether to reduce flaps and retract gear, which the captain agreed. As such, a standard missed approach was carried out though with maximum thrust.



The MAK analysed:



Before the second go-around there was no windshear warning activation, as well as there was no explicit callout by the PIC on the type of maneuver (the airline OM did not stipulate such a specification of commands), that is why the F/O could have perceived the maneuver to come as the standard go-around  particularly given that he had just drawn the PICs attention to the deviation (on speed) of the stabilized approach criteria. It is the F/O who offered to PIC to retract flaps to 15, as it is prescribed at the standard go-around. The PIC immediately agreed with the F/O, although according to SOP (item 12.1.1), the decision-making and the respective callout to retract flaps should come from the PIC himself with a simultaneous GO-AROUND callout.



Thus, with the consideration of the subsequent landing gear retraction following the F/Os report on positive rate of climb, actually the crew was performing a standard go-around procedure at the low weight aircraft with the maximum thrust of the engines (N1=101%), as it is prescribed by the Windshear Escape Maneuver. Taking into account that in preparation for the second approach it is this procedure that had been talked over by the crew, the indicated factor may have played a certain role, as later the whole range of the erroneous and inappropriate actions by the PIC resulted in a loss of control of the aircraft. This very moment, most probably, had been a turning point in the chain of the events.



At 00:40:54, the F/O reported go-around to the Rostov Tower controller and was instructed to contact the Rostov Radar controller. The crew did not contact the Radar controller.



The increase of the engines thrust combined with the retraction of flaps and landing gear led to the significant increase of pitch-up moment (more than at the first go-around); to counteract it the substantial push of the control column was required with the application of pushing forces on the control column of up to 50 lb (23 kg), that had been preserved for quite a long time (more than 40 sec). The piloting - especially the precise piloting - of an out of trim aircraft (unbalanced on forces), is always complicated and implies the increase of the pilots workload, including the psychoemotional component. Indeed, the nature of the control wheel motion on pitch after the initiation of go-around is loose (the longer movements) and abrupt (reactive) with the noticeable delay. This very nature of the piloting is always the evidence of the flight mental mode disruption and the absence of forecast on the further behavior of the aircraft (the pilot is behind the aircraft, the aircraft flies ahead of the pilot).



The MAK annotated:



1. It should also be taken into account that the stated forces on the control column PIC, most probably, had maintained by one (left) hand. The other hand was on power levers (the confirmation to this is stated here below).

2. Hereinafter the integral flight mental mode means not only the pilots reflection of the flight process, that is matching of real aircraft attitude and mode to the perceived ones, but also the ability of the pilot to fly ahead of the aircraft, including to predict the aircraft behavior in response to the control inputs.

3. As per the information, submitted by the airline, the PIC was well experienced in performing go-arounds in real flights (6 go-arounds not counting the first goaround at the day of the accident, of which 3 as a PF and 3 as a PM). The airline could not provide the information on the reasons for go-arounds.



The captain was supposed to establish 15 degrees nose up pitch, however, did not acquire that pitch, changing the pitch in steps, as such the aircraft did not maintain the climb path (unlike the first go around). The MAK wrote:



The average pitch in climb was equal to about 10º, which was obviously insufficient for the given conditions, taking into account that:



- the thrust-to-weight ratio of the aircraft was high (the aircraft was of a relatively low weight of 54 t. and the engines were delivering the maximum possible thrust);

- the drag of the aircraft was significantly less against the first go-around (landing gear up, flaps 15º).



The PIC, apparently, failed to consider all these factors. At the same time the F/O, observing the PIC, having difficulties in piloting the aircraft drew his attention to the necessity to maintain the required pitch.



The PIC briefly (for a second) increased pitch up to 18.5º, then reduced it again to 4º...5º, having applied the disproportionately significant pushing movements on the control column (more than ½ of travel from the neutral position to fully forward) and generated the vertical G of 0.43 g.



In reaction to such actions by the PIC, the F/O prompted once again:



00:41:18,0 00:41:19,4 F/O Now keep it, keep it to fifteen, keep it



Note: At this moment, there was a minor (down to 97 % N1) decrease in engines power with the subsequent restoration of the maximum thrust. The investigation team is of the opinion that this very decrease was incidental and is associated with the PICs hand on power levers at the above-indicated significant change of the vertical G.



Having focused the attention on maintaining pitch, both pilots had completely lost the awareness of on the airspeed, that was gradually increasing and at 00:41:10 reached the limit Vfe (200 kt) for flaps 15º, after which the T.E. FLAP LOAD RELIEF was activated. The flaps were set to 10º. In such a way, it was a repetition of the situation that occurred during first go-around.



With that, the F/O, as opposed to the first go-around, did not draw the PICs attention on the speed exceedance. The engines kept on running at the maximum thrust up to the impact with ground; the flaps handle remained at the 15º detent.



The situation when the attention of the crew was excessively concentrated on the pitch control of the aircraft led to the substantial narrowing of perception of the other information (the tunnel effect). The number of parameters, having been monitored and analyzed at a time, had decreased sharply, down to about one or two.



The onset of the critical situation started at 00:41:30.5. In proceeding the piloting of the out of trim aircraft (unbalanced on forces), and obviously enduring inconvenience; at the present parameters of flight: Н ≈ 3350 ft QNH (935 m QFE), IAS  210 kt, pitch  10º to nose-up, the stabilizer setting  2.7º to nose-up, flaps 10º, the power mode of the engines  the maximum thrust, the PIC pressed the stabilizer trim switches to nose-down.



The HUD indicated a pitch up was needed at that point. The MAK analysed:



In other words, most probably the PIC, having acted in such a manner, tried to relieve the pushing forces on the control column, rather than to transition the aircraft to nose down. However, along the stabilizer trim, the pilot did not return the control column to neutral position, with that the stabilizer trim switch remained pressed for an abnormally long time (12 s!!!).



Note: 1. The investigation team did not identify any signs of failure or the uncommanded movement of the stabilizer. The direction and duration of the stabilizer trim are consistent with the respective discrete signals registration (the FDR records the discrete signals, associated with the commands to the nosedown and nose-up stabilizer trim in a manual or automatic mode). The short time pull of the control column (at 00:41:39) beyond neutral resulted in the stabilizer trim stop that is consistent with the inherent logic of the control system function.



2. Most likely, by this moment of time the flight mental mode at the PIC had been completely disrupted, whereas his emotional condition may be characterized as distress/a very strong stress. It is confirmed by the fact that from 00:41:33 and up to the end of the flight the quite dynamic pedal inputs are recorded, with that they had not been anyhow justified by the flight situation. It is known from the practice of the air accident investigation that when the pilots encounter complete spatial disorientation and lose the ability to appropriately evaluate the situation, often they start to do the involuntary (reflex) control inputs. In this sense, as for the modern transport aircraft, the deflection of pedals that, usually, are not used in flight, is the most indicative symptom. After the forward deflection of the left pedal within a time of 00:41:33  00:41:39, the aircraft bank was changing with a constant angular rate from 5 to the right to 12 to the left with the practically neutral position of the control wheel that again demonstrates the crew failure to monitor all the necessary parameters.



The actions in question (the substantial stabilizer trim to nose-down along with the keeping and even some increase of the average deflection of the control column to nose-down) led to the rapid decrease of pitch (the average pitch rate about 6 /sec) and the aircraft transition from the climb to descent with the significant negative G (initially minus 0.3 minus 0.4 g, then  up to minus 1.07 g), at that the near-zero and negative G (

Note: FCT 737 NG (TM), page 7.22: It may be difficult to know how much stabilizer trim to use, and care must be taken to avoid using too much trim. Pilots should not fly the airplane using stabilizer trim, and should stop trimming nose down when they feel the g force on the airplane lessen or the required elevator force lessen.



The F/O, operating as PM, realized that the hazardous situation was emerging. Desperately, with the increasing anxiety in voice, he tried to return the PIC to a control loop and rectify the situation. From the point of time of 00:41:34 the F/O prompted the appropriate actions to the PF (the control column pull) to prevent the situation transition to the accident. Nevertheless, most likely, the PIC had no longer heard the F/O and had not reacted to his words  he had fully lost the control of the situation, as well as the capability to control the aircraft.



The inappropriate actions by the PIC within 12 sec, when the stabilizer trim switches were kept pressed, the aircraft entered into nose-down upset (negative pitch of about 40º, IAS  280 kt with the flaps 10º, the altitude of 2800 ft QNH (770 m QFE), the engines power at maximum thrust, the stabilizer setting of 2.4º to nose-down).



Within the time interval of 00:41:42-43 it had been a momentary aft control column deflection by ≈11 (more than 2/3 travel off neutral) with the subsequent return beyond neutral in the forward direction. The calculations were the evidence (see Section 1.16.7), that if at that point of time the control column were repositioned to a full pull and was kept at that position, the aircraft could have been recovered from descent with a sufficient margin of height. Only aircraft aerodynamic performance and capabilities are analyzed here. The crew members state and actions are analyzed below and have not been taken into consideration in the engineering simulation.



Similar results were obtained as a result of the experiment at the B737-800 aircraft simulator. The appropriate actions by the crew (the pull of the control column creating vertical G of 2.2 2.4 with the simultaneous reduction of the thrust to idle) allowed recovering the aircraft safely.



From the point of time of 00:41:44, the F/O attempted to pull the control column (see also Section 1.16.8).



The last seconds of the FDR record explicitly confirms the complete spatial disorientation of the PIC and indicate the critical disruption of the flight mental mode integrity. Apart the lack of appropriate actions on the aircraft recovery from descent (even after the EGPWS PULL UP warning activation) the control wheel was repositioned to practically full left in roll that led to the intensive development of the left roll. The aircraft impacted ground with the significant speed (≈ 340 kt), high negative pitch (≈ 50º) and the left bank ≈ 60º.



Note: The analysis showed that, most probably, even with the appropriate actions by the pilot at the EGPWS PULL UP warning activation at that point it had not been possible to prevent the catastrophic situation (to recover the aircraft out of descent).



Honeywell, being the EGPWS manufacturer, upon the investigation team request commented that the accident flight actual parameters (rate of descent 18000 ft/min (91 m/s)) had been far beyond than the maximum values (7000 ft/min (36 m/s)), determined by the TSO C151b and DO-161A documents, in accordance to which the system had been designed.



At the same time at that phase of flight the pilots could not have known that it had been already impossible to recover the aircraft out of descent, for this reason no appropriate actions in response to this warning demonstrates indeed the critical disruption of the flight mental mode.



In the progress of the analysis of the crew proficiency and their in-flight actions the question arises  quite naturally  how the experienced and disciplined crew, having been in a normal working condition and monitored the flight, all of a sudden had lost control and let the situation occur that resulted in the fatal accident?



All the actions and taken decisions (besides the setting of QFE instead of QNH during first approach) up to the moment of initiation of the second go-around testify to a high level of training and proficiency of the crew, and the PIC had been an indisputable leader. The point of initiation of go-around during the second approach can be considered as the onset of the abnormal situation. From that moment, the PIC started to make errors, take inappropriate actions and was no longer a leader.



The MAK analysed whether the first officer should have detected the incapacitatio of the captain and taken control stating that according to the FCOM detection of incapacitation and take over of control should occur if there was no verbal reply by the pilot flying to two communications by the pilot momitoring addressing the pilot flying, or no verbal reply to the pilot monitoring pointing a significant deviation from the intended flight path, or no reaction to a system malfunction. The captain did react to the communication by the first officer, though in one word only. The MAK wrote:



The events of the psychological incapacitation, when the PF verbally responds to the communication and physically exercises the control inputs, but these are obviously inconsistent with the current flight environment, as a rule, are not incorporated into the airlines OM. The Flydubai airline OM did not state such occurrences either. Consequently, the PM for more than 30 s had been prompting the correct actions to PF and at a certain point even tried to intervene in the control with prompting the correct direction of the control column deflection by the action. Still, because of the continued inappropriate actions by the PIC and the specific features of the pitch control system (Sections 1.16.7 and 1.16.8), the actions by the F/O had been unsuccessful.



With respect to the trim relief the MAK analysed:



As for the accident flight, both in progress of the first and the second go-around the PIC, when pressing the trim switches, did not return the control column to neutral, thereby increasing the pitch-down moment. In the course of the meetings with the representatives of the command, flight crew and instructor personnel of the airline the view has been expressed by them that the PIC could not have possessed the sufficient level of knowledge on the peculiarities of the forces trim on the aircraft of the Boeing 737 type.



The investigation team also notes that in case of long-time press on the stabilizer trim switches there is a danger of loss of the feedback on forces. Due to the small amount of forces the pilots finger gets used to them quickly, which may lead to the prolongation of the earlier started action, that is to the holding of the trim switches. The non-optimal working condition of the pilot or the situation, when the pilot does not achieve the required goal (the forces relief on the control column) with the mentioned action, can be contributive in the case.



...



The PM has the opportunity to stop the stabilizer trim by pressing the trim switches in the opposite direction (as for the situation of the accident flight with the control column, for a long time had been kept by the PF at the nose-down deflection, for the PM to use his own stabilizer trim switches it had been necessary to use the stabilizer override switch (see also Section 1.18.2).



In the factual section 1.18. the MAK laid out how the electrical trim and the cut out switches inside the ontrol column worked stating, that with a deflection of the control column of more than 4 degrees nose down any electrical trim up command would be blocked (or with the control column more than 4 degrees nose up any electrical trim down command would be blocked), whereas with the control column within -4 and +4 dgerees of deflection in case both trim up and trim down commands would be registered causing the stabilizer to stop (with both commands present at the same time). Only the override switch would permit to have the trim up command pass through in case of the control column being deflecte more than 4 degrees nose down.



The MAK analysed with respect to the head up display (HUD):



One more specific feature of the use of HUD is that the pilot only at his certain relative head posture against HUD can observe the complete picture. At the considerable change of the pilots head posture against HUD, for example, at the extreme maneuvers, severe turbulence, upset encounter (notably with the reach of near-zero and negative Gs) the portion of the HUD picture may be lost out of the pilots vision field. Following the investigation team request the HUD manufacturer responded that at its certification there were no flight assessment of the unit carried out into the entire range of the operational G (up to -1 g) for the Boeing 737 aircraft (since it is not stipulated by the certification requirements) and the respective test pilot evaluation does not exist either.



...



Fig. 71 and Fig. 72 represent the HUD reconstructed images at the points of time, coherent with the maximum reached negative G (-1.07) and the moment of the F/Os interference into the control. It is apparent that HUD switched to the display mode, corresponding to upset. The HUD is switched to this mode, when the nose-down pitch exceeds 20 degrees.



According to the HGS Pilot Guide, this mode enhances interpretation of an unusual attitude by the pilot. All the redundant information is retracted out from the HUD screen. These are only altitude and IAS scales, pitch and roll together with the slip indicator that are displayed. In the progress of the investigation team activities team some pilots noted that in the stress environment the applied indication (two nonparallel lines) might be misinterpreted by the pilot, as the indication, similar in appearance, is used to display RWY at the HUD operation in the AIII mode.



Thus, taking into account the lack of the objective information on the HUD operation (there were no flight tests of the unit carried out in the entire range of the operational G; the impossibility to reproduce the real HUD readings in the progress of the accident flight, that is the image, the pilot was really watching with the consideration of his posture in the seat, through the stream video (see Section 1.16.9) or at the FFS) did not allow making unambiguous conclusion on its possible impact on the flight outcome.



At the same time the investigation team believes that the further elaboration of the methodological issues of the practicability and the use of the HUD at different segments of flight, as well as the carry out of the additional flight tests into the entire operational range and the works on the improvement of the data presentation (with the consideration of the opinion of the experts in ergonomics and aviation psychology) may mitigate the risks of the erroneous interpretation of readings in the stress situation.



FDR graphics (Graphics: MAK):





Head Up Display Figure 70 (Graphics: MAK):





Head Up Display Figure 71 (Graphics: MAK):



On Nov 26th 2019 the Interstate Aviation Committee (MAK, also known as IAC) released their final report concluding the probable causes of the crash were:The MAK provided lenghty analysis spanning 66 pages (starting page 104, ending page 169).The investigation analysed that the crew was well rested The MAK wrote:The weather was no factor into the accident. The MAK wrote: "The forecast and actual weather en route, for the Rostov-on-Don destination aerodrome and the alternative aerodromes of Trabzon (LTCG) and Volgograd (URWW) did not impede the performance of the flight mission and met the IFR."The MAK analysed that the first approach to Rostov was aborted and a go around initiated after the crew received an automatic call "Go-Around, Windshear ahead" warning at about 1100 feet, which had been generated by the Predictive Windshear warning system located in the weather radar (the reactive windshear warning system resides in the EGPWS and activates when the aircraft is in an actual windshear situation). The MAK wrote: "It was an almost instant response by the crew, about 1 s from the aural message trigger! This is the evidence of the crew having been prepared for such kind of events and well trained on the simulator as for the practice of actions in windshear. Most likely, the HUD had a positive effect at that, too, as the windshear warning is very vividly noticeable." with reference to the initiation of the go-around.The MAK analysed that the captain initiated the go around as a windshear escape maneouver by applying maximum thrust but leaving the aircraft configuration unchanged (gear remaining down, flap setting remaining unchanged). The MAK wrote: "Initially in 10 sec, the PIC reached the pitch of 14 15º, following the HUD commands and the FCOM and QRH guidance. To counteract the excessive pitch-up moment, generated at the engine thrust increase to maximum, the PIC was forced to move the control column significantly forward."The aircraft was to climb 1200 feet for the go around only, 1000 feet below the target altitude the ALT ACQUIRE mode activated for the flight director. The MAK wrote:Subsequently the pilots discussed the overspeed condition, it remained unclear however, whether any of them had recognized the flaps relief.While the aircraft entered a hold to wait for improvement of weather a number of other aircraft attempted the approach to Rostov and went around reporting windshear too.The captain decided to attempt another approach following following considerations:The captain discussed the decision with dispatch via Satcom for a considerable time, the company supported the decision by the captain. Following the second approach the airline recommended to divert to Mineralnye Vody and transmitted a flight plan for the 270nm trip taking 44 minutes and requiring 1728 kg of fuel. The crew briefed the diversion to Mineralnye Vody in case of another go around and again briefed the windshear escape maneouver.The MAK analysed:1:40 hours after the first go around and 21 minutes prior to impact ATC advised the crew that the weather office had not advised about any windshear on the runway (previous weather reports had forecasted moderate windshear). The captain decided to attempt the approach, coordinated the diversion to Mineralnye Vody in case of a go-around with the controller, the aircraft left the hold and positioned for the approach, Vref had been determined at 133 KIAS, the captain applied a 20 knots wind correct and thus set Vapp to 153 KIAS. The MAK analysed that the crew had "appropriately identified the approachspeed." and added: "At the same time the crew, having in mind the difficulties during the first go-around, coordinated with the controller that in case of go-around they would immediately climb FL080."The HUD was switched to an IMC mode. The MAK analysed based on engineering simulations that the aircraft performance had not been impaired by icing. The crew configured the aircraft for landing and performed the ILS approach to runway 22. The aircraft intercepted the glideslope while maintaining 2250 feet MSL, wind information from tower indicated winds from 230 degrees at 12m/s (23 knots) gusting 18m/s (35 knots). Descending through 2165 feet the captain disengaged the autopilot, descending through 1960 feet the autothrust was disengaged. The landing checklist was performed.Descending through 1000 feet the aircraft was nearly stabilized with all parameters within limits, the captain announced "stabilizing now", the MAK analysed probably referring to the IAS of 163 KIAS 10 knots above Vapp.The MAK analysed:With the thrust levers advanced to full thrust rather than remaining at TOGA setting the captain probably again initiated the "windshear escape maneouver", however, no windshear warning had occured (unlike the first approach). The first officer therefore queried whether to reduce flaps and retract gear, which the captain agreed. As such, a standard missed approach was carried out though with maximum thrust.The MAK analysed:The MAK annotated:The captain was supposed to establish 15 degrees nose up pitch, however, did not acquire that pitch, changing the pitch in steps, as such the aircraft did not maintain the climb path (unlike the first go around). The MAK wrote:The HUD indicated a pitch up was needed at that point. The MAK analysed:The MAK analysed whether the first officer should have detected the incapacitatio of the captain and taken control stating that according to the FCOM detection of incapacitation and take over of control should occur if there was no verbal reply by the pilot flying to two communications by the pilot momitoring addressing the pilot flying, or no verbal reply to the pilot monitoring pointing a significant deviation from the intended flight path, or no reaction to a system malfunction. The captain did react to the communication by the first officer, though in one word only. The MAK wrote:With respect to the trim relief the MAK analysed:In the factual section 1.18. the MAK laid out how the electrical trim and the cut out switches inside the ontrol column worked stating, that with a deflection of the control column of more than 4 degrees nose down any electrical trim up command would be blocked (or with the control column more than 4 degrees nose up any electrical trim down command would be blocked), whereas with the control column within -4 and +4 dgerees of deflection in case both trim up and trim down commands would be registered causing the stabilizer to stop (with both commands present at the same time). Only the override switch would permit to have the trim up command pass through in case of the control column being deflecte more than 4 degrees nose down.The MAK analysed with respect to the head up display (HUD):FDR graphics (Graphics: MAK):Head Up Display Figure 70 (Graphics: MAK):Head Up Display Figure 71 (Graphics: MAK): By Simon Hradecky, created Tuesday, Aug 21st 2018 15:18Z, last updated Tuesday, Aug 21st 2018 15:23Z On Aug 21st 2018 the Interstate Aviation Committee (MAK) reported that the draft final report is in the final stage. Basically all data collection and analysis has been completed, only the Head Up Display (HUD) indications have been restored from the FDR data by the device manufacturer in Feburary 2018 and are currently being put together in form of a streaming video. The HUD indications may be important to establish the causes of the accident and to introduce safety recommendations. Based on the results the commission may decide to conduct a simulator experiment to reproduce the HUD indications which were displayed during the accident flight.

By Simon Hradecky, created Wednesday, Apr 20th 2016 21:27Z, last updated Monday, Mar 20th 2017 17:34Z



The second approach was flown manually in flight director mode (like the first approach), at 220 meters/720 feet of height and 4.5km/2.42nm before the runway threshold the crew decided to go around, one of the likely reasons being an air speed increase of 20 knots to 176 knots within 3 seconds. The engines were accelerated to 101/102% N1, maximum takeoff/go-around thrust. During the go around the crew retracted the landing gear and reduced the flaps to 15 degrees.



Climbing through 1900 feet AGL at nose up attitude of 18 degrees the pilot flying pushed the control column forward resulting in a nose down movement and reduction of vertical acceleration to +0.5G and an increase in airspeed causing the automatic retraction of flaps from 15 to 10 degrees at a speed of above 200 KIAS.



The engine thrust was reduced for a brief period resulting in a speed decrease, the flaps returned to 15 degrees, then engine thrust was increased again to TOGA, the flaps retracted automatically again to 10 degrees, the flaps remained in that position until impact.



The pilot flying applied nose up inputs resulting in a vertical climb rate of 16 meters/s (3150 fpm).



At a height of 900 meters/2950 feet a simultaneous nose down control input and a stabilizer nose down deflection from -2.5 degrees (6.5 units) to +2.5 degrees (1.5 units) occurred resulting in the aircraft, after having reached 1000 meters/3300 feet, to begin to descend and experience a vertical acceleration of -1.0G.



According to FDR the nose down trim input came from the stabilizer trim switch at the control column and lasted for 12 seconds while the cockpit voice recorder recorded specific noise of the trim wheels rotating.



The MAK wrote: "The following crew recovery actions did not allow to avoid an impact with the ground". The aircraft impacted the runway about 120 meters past the runway threshold with a speed of more than 600kph/324 knots and more than 50 degrees pitch nose down killing all occupants and destroying the aircraft.



The captain (ATPL) had accumulated 5,961 hours total and 4,905 hours on type, the first officer (ATPL) 5,767 hours total and 1,100 hours on type. The aircraft had accumulated 21,252 hours flying time in 9,420 flight cycles.



At the time of the accident ATIS (identification letter) E was active and read: "... surface wind 230 degrees, 12 mps gust 19 mps, visibility 3800 m, light shower rain, clouds scattered at 540 meters, broken cumulonimbus at 1080 m, moderate turbulence from surface to 1000 m; moderate icing in clouds at 900-1500 m, tempo wind 250 degrees 17 mps gust 25 mps, visibility 1000 m, shower rain, mist, clouds scattered cloudbase 90 m, broken cumulonimbus cludbase 600 m..."



Aerodrome ILS, outer and inner marker, runway lighting system and PAPIs were operating normally as per design.



The cockpit voice recorder is still being analysed and transcribed at the time of the release of the preliminary report.



On May 16th 2016 the MAK announced, that the transcription of the cockpit voice recorder has been completed.



Late Mar 19th 2017 the MAK reported that the investigation is still ongoing, the investigation including the accredited representatives from the NTSB and the United Arab Emirates is currently completing the analysis of the information collected so far, the final report will be drafted afterwards.



Aerial Detail of impact area (Photo: MAK):





Wreckage distribution on the crash site, watch objects 116 and 117 prior to the runway threshold (Graphics: MAK):





Flight trajectory (Graphics: MAK):



In the late evening of Apr 20th 2016 The Interstate Aviation Committee (MAK) released their interim report in English stating, that following the first go around the crew entered a hold and subsequently requested to climb to FL150 after encountering moderate icing in the hold.The second approach was flown manually in flight director mode (like the first approach), at 220 meters/720 feet of height and 4.5km/2.42nm before the runway threshold the crew decided to go around, one of the likely reasons being an air speed increase of 20 knots to 176 knots within 3 seconds. The engines were accelerated to 101/102% N1, maximum takeoff/go-around thrust. During the go around the crew retracted the landing gear and reduced the flaps to 15 degrees.Climbing through 1900 feet AGL at nose up attitude of 18 degrees the pilot flying pushed the control column forward resulting in a nose down movement and reduction of vertical acceleration to +0.5G and an increase in airspeed causing the automatic retraction of flaps from 15 to 10 degrees at a speed of above 200 KIAS.The engine thrust was reduced for a brief period resulting in a speed decrease, the flaps returned to 15 degrees, then engine thrust was increased again to TOGA, the flaps retracted automatically again to 10 degrees, the flaps remained in that position until impact.The pilot flying applied nose up inputs resulting in a vertical climb rate of 16 meters/s (3150 fpm).At a height of 900 meters/2950 feet a simultaneous nose down control input and a stabilizer nose down deflection from -2.5 degrees (6.5 units) to +2.5 degrees (1.5 units) occurred resulting in the aircraft, after having reached 1000 meters/3300 feet, to begin to descend and experience a vertical acceleration of -1.0G.According to FDR the nose down trim input came from the stabilizer trim switch at the control column and lasted for 12 seconds while the cockpit voice recorder recorded specific noise of the trim wheels rotating.The MAK wrote: "The following crew recovery actions did not allow to avoid an impact with the ground". The aircraft impacted the runway about 120 meters past the runway threshold with a speed of more than 600kph/324 knots and more than 50 degrees pitch nose down killing all occupants and destroying the aircraft.The captain (ATPL) had accumulated 5,961 hours total and 4,905 hours on type, the first officer (ATPL) 5,767 hours total and 1,100 hours on type. The aircraft had accumulated 21,252 hours flying time in 9,420 flight cycles.At the time of the accident ATIS (identification letter) E was active and read: "... surface wind 230 degrees, 12 mps gust 19 mps, visibility 3800 m, light shower rain, clouds scattered at 540 meters, broken cumulonimbus at 1080 m, moderate turbulence from surface to 1000 m; moderate icing in clouds at 900-1500 m, tempo wind 250 degrees 17 mps gust 25 mps, visibility 1000 m, shower rain, mist, clouds scattered cloudbase 90 m, broken cumulonimbus cludbase 600 m..."Aerodrome ILS, outer and inner marker, runway lighting system and PAPIs were operating normally as per design.The cockpit voice recorder is still being analysed and transcribed at the time of the release of the preliminary report.On May 16th 2016 the MAK announced, that the transcription of the cockpit voice recorder has been completed.Late Mar 19th 2017 the MAK reported that the investigation is still ongoing, the investigation including the accredited representatives from the NTSB and the United Arab Emirates is currently completing the analysis of the information collected so far, the final report will be drafted afterwards.Aerial Detail of impact area (Photo: MAK):Wreckage distribution on the crash site, watch objects 116 and 117 prior to the runway threshold (Graphics: MAK):Flight trajectory (Graphics: MAK):

By (anonymous) on Thursday, Dec 5th 2019 08:44Z





By The Legacy on Thursday, Dec 5th 2019 05:32Z





By Captain Crunch on Wednesday, Dec 4th 2019 23:04Z





By BluexMax on Wednesday, Dec 4th 2019 16:21Z





By Captain Crunch on Wednesday, Dec 4th 2019 07:37Z





By Captain Crunch on Wednesday, Dec 4th 2019 07:12Z





By BlueMax on Monday, Dec 2nd 2019 10:02Z





By Captain Crunch on Monday, Dec 2nd 2019 00:01Z





By Captain Crunch on Sunday, Dec 1st 2019 23:07Z





By Bluemax on Friday, Nov 29th 2019 09:23Z





By Hans W. on Friday, Nov 29th 2019 08:34Z





By (anonymous) on Friday, Nov 29th 2019 08:07Z





By Hans W. on Friday, Nov 29th 2019 08:04Z





By Ray_Y on Thursday, Nov 28th 2019 17:53Z





By Ray_Y on Thursday, Nov 28th 2019 17:49Z





By Human on Thursday, Nov 28th 2019 16:44Z





By Human on Thursday, Nov 28th 2019 16:38Z





By Human on Thursday, Nov 28th 2019 16:38Z





By Drone Pilot on Thursday, Nov 28th 2019 12:04Z





By BusDriver on Thursday, Nov 28th 2019 10:18Z





By Cumulative on Thursday, Nov 28th 2019 08:27Z





By John R Sunara on Thursday, Nov 28th 2019 04:36Z





By Skment on Thursday, Nov 28th 2019 02:23Z





By Sarah on Thursday, Nov 28th 2019 00:23Z





By hfjkads on Wednesday, Nov 27th 2019 22:50Z





By busdriver on Wednesday, Nov 27th 2019 22:45Z





By busdriver on Wednesday, Nov 27th 2019 22:42Z





By Jason H on Wednesday, Nov 27th 2019 22:42Z





By Brian Johnson on Wednesday, Nov 27th 2019 22:36Z





By John on Wednesday, Nov 27th 2019 16:30Z





Add your comment: (max 1024 characters) Your Name: Your Email: Subject: Your comment: The Aviation Herald Apps

Android and iOS

Support The Aviation Herald

one time

Monthly support 1 €/month

Interview: The human factor named "Simon Hradecky" and the team of man and machine Get the news right onto your desktop when they happen © 2008-2020 by The Aviation Herald, all rights reserved, reprint and republishing prohibited. We use cookies to ensure you get the best experience on our site, learn more