Leaked Flydubai recorder data reveals argument, panic in cockpit before ‘fatal nosedive’

© Guillermo Granja
The Flydubai FZ981 crash in Rostov-on-Don, Russia, could have followed the pilots’ failure to manage the landing after taking control of the system, media reveal citing flight data. The final minutes are said to have been full of arguments and screams of terror.

#FlydubaiGate: Pilots speak out to RT after Rostov-on-Don crash

Now that decoding of the flight data recorders of the crashed Boeing is complete, an unnamed source told Russian daily Kommersant that pilot error is now dominating the investigation as the probable cause.

It appears that while trying to gain altitude after an unsuccessful landing attempt in bad weather, one of the pilots pulled the control stick up too much, causing a stall break and an uncontrollable nosedive.

The Interstate Aviation Committee believes that the official results of the decoding will be made public within a week or two.

Meanwhile, according to Kommersant’s sources, the recorder revealed that flight FZ981 had made two attempts to land in automatic mode, and since a veering squall wind hampered the second attempt, the pilot decided to make a third approach for landing in manual mode.

One of the pilots pressed the TOGA (Take off. Go around) button and turned off the autopilot, writes the daily.

Anonymous experts Kommersant talked to believe the pilot did not manage the diving rudder and horizontal stabilizer, which steer the plane in opposite directions – down and up, respectively.

When the pilot pulled up, he put both the rudder and stabilizer in a sharp climb mode, somewhat fighter-jet style, plus enacted the TOGA regime’s retracted flaps, decreasing ascending force. As a result, the aircraft lost speed and got into the beyond-stall angle of approach. All this led to an uncontrollable dive, the experts believe.

At that moment, the voice recorder is said to have registered a conflict between pilots. The pilot that tried to force the aircraft to gain altitude apparently turned the engines to powerful take-off mode, forcing the aircraft to continue its climb.

The other pilot believed the situation was dangerous and apparently did the opposite: he pushed his own control over to bring the Boeing’s nose down and prevent the sweeping up, while yelling at his colleague to stop doing it that way.

“Wait! Where are you flying? Stop! Stop!” a voice on the recorder reportedly yelled.

The pilots’ contrary actions caused the controls of the aircraft to ‘split’: the Boeing 737’s onboard computer was receiving mutually-exclusive commands from the two controls, which are usually operated synchronously. This rendered the plane out of control.

When they felt the plummeting sensation, the crew coordinated their actions, but it was already too late. The Boeing 737-800 was roaring at 325kph downwards at an angle of about 45 degrees. It burst into flames upon collision with the ground, killing all 62 people on board.

During the last seconds before the collision both pilots were screaming with terror, Kommersant reports.

On March 20, Russia’s Investigative Committee named pilot error or technical failure as the prime theories as to the cause of the Flydubai’s Boeing 737-800 crash in Rostov-on-Don on March 19.

It is unclear from the recording which pilot was doing what, Kommersant notes. At first the investigators even believed that only one man was speaking the whole time. Now, to identify the voices of the deceased pilots, the expertise of their former colleagues and even relatives may be needed.

Comments (185)
DrDre 1 hour ago

What’s interesting is today an Egypt airliner is hijacked and forced to land in Cyprus by a man claiming to be wearing a suicide vest.

What’s also interesting is the 2-hour “hold pattern” for the FlyDubai plane, which is an extremely long time not to divert, particularly since the weather was not improving.

Probably like MH370 we will never know what happened.

TWA Flight 800 was shot down over Long Island, by mistake, by the US navy. The government claimed the fuel tank exploded. The handling of the flight data recorder and air traffic control records in the MH crash over Ukraine, and the “investigation” into it, also do not exude confidence.

Governments cannot be trusted. It would not surprise me if the Russian government wanted to cover up that, say, an ISIS supporter had blown up an airplane over Russian skies. Not saying that’s what happened, but not saying pilot fatigue caused it either.

Rob Freemantle 2 hours ago
The jew main scream media missed an opportunity…. wasn’t it shot down by Russia with a Buk missile?

 

DrDre> Sebastien Lamoureux 3 hours ago
Sebastien Lamoureux
In my pilot opinion, the pilot in command elected to do a manual go around rather than following the miss more…

Landing lights are beams, pointing in one direction, not a ball that engulfs the entire aircraft. This isn’t ET. Yes it is possible to construct some scenario where it was pilot error – if you ignore the huge ball of flame which consumed the plane.

A good comparison video, useful to dispel this misinformation, is one on YouTube entitled “SX-VIP Boeing 737 – Night Landing HD“, video ID is “NsSpLgdl-YA “. Those are landing lights. The FlyDubai plane: ball of flame.

One thing to notice is, with landing lights, as they are a directional beam, the brightness of the light varies with distance and angle, whereas the FlyDubai “ball of fire” retained the same intensity and shape during the entire plunge, which is particularly observable in the third video I have listed, on YoutTube, video ID is “7xfJvE8I0RM“.

Unfortunately the video quality is not good enough to make any definitive conclusion; the ball of fire could be an optical illusion due to low resolution combined with wide aperture due to nighttime conditions.

Sebastien Lamoureux 4 hours ago
In my pilot opinion, the pilot in command elected to do a manual go around rather than following the miss approach procedure which is all done on auto pilot. They were obviously tired and exhausted which did not help the PIC decision making. I believe the PIC patience was running thin and he just went ahead with a manual Go Around , applied full power and attempted to raise the altitude quickly so he could try another approach manually. But as he did so, the flaps were still in landing config and did not have enough time to retract which caused a lot of drag and decreased the air speed so badly that the 737 stalled. The other pilot realized what was going on and asked his colleague to stop doing that. He also tried to take over the controls in order to lower the nose so they could gain some much needed airspeed. However the power was set on full which would force the nose up, and when both pilots have their hands on the controls, it cancel the orders. In a matter of seconds the plane stalled and was way to low to recover. Game over. To explain better what happened, first you have to understand that the Boeing philosophy is very different than Airbus. On an Airbus under normal law, the computer would have not allowed the plane to stall, auto pilot on or not. It would have gone on alpha max at worst but will not have crashed. This is a different story with Boeing, The 737 is a very delicate machine to fly manually with almost no room for error. In this instance the only thing thing to do was to close the throttle, lower the nose, gain some speed, clean up the flaps and gear then increase power as you raise the nose to gain altitude once you have the correct air speed. Please note you have only 2 or 3 s max to do so before stalling. This is all basic flying skills. Sadly due to a combination of events which in my opinion involves severe fatigue they messed up and sealed their faith, Sad story. RIP.
Let’s hope the Fly Dubai management will be taking action and allow ASAP proper rest for their pilots so this does not happen again, if not it will definitely take place again. We are only human.

 

Facebooktwitterredditpinterestlinkedinmail

Leave a Reply

You must be logged in to post a comment.