Preliminary Accident Report Released For EK521

In early August, an Emirates 777 crash landed in Dubai. While there has been a lot of speculation as to what happened, up until now we haven’t received much official information.

Well, the General Civil Aviation Authority of the UAE has released a preliminary report of what happened to EK521 as it came in to land at Dubai International Airport. This is a preliminary report, meaning it doesn’t draw any conclusions as to the cause of the crash, but rather reports on all the facts we know as of now.

As usual, the preliminary report is highly technical and 28 pages long, so the average person won’t understand much of what’s explained in the report. However, it’s a very interesting read nonetheless.

Big picture, what happened was that the plane landed “long,” about 1,100 meters down the runway, partly caused by a change in the winds as the plane approached.

The plane had full flaps and idle power as it touched down, though due to the warning system saying that the plane landed long, the pilots decided to execute a go around. That’s where things got messed up.

The plane climbed to an altitude of 85 feet and the pilots had already retracted the plane’s gear and raised the flaps, though the plane didn’t have a positive rate of climb. At that point the plane began to sink.

We don’t know whether the pilots tried to activate the “take off/go around” switch or not, though regardless it apparently doesn’t work on a Boeing once the gear makes contact with the ground (which matches a past theory we’ve heard about what happened).

While the evacuation was successful (all passengers got out safely, though unfortunately one of the firefighters died during the rescue efforts), it’s amazing that this was done in spite of major problems with the evacuation. The 777-300 has 10 emergency exits. Only five of the 10 emergency exits were ever used, and of the five used, some of them had problems beyond that, as you can see in the below chart:

EK-Evacuation

On top of that, passengers stupidly took their personal belongings with them, which slowed down the evacuation process further, putting peoples’ lives at risk.

While totally random, it’s interesting to note that the captain was younger and had fewer hours than the first officer (which isn’t unusual at Emirates, as the captain was a “local,” while the first officer was Australian):

EK521-Captain

I’m not suggesting that had anything to do with the accident, as both pilots were pretty experienced. Rather I was just impressed that the 777 captain was just 34 — that’s impressive!

Bottom line

What we know for sure is that EK521 crashed due to a go around gone wrong. The winds changed during the landing, which caused the pilots to make a “long” landing and then decide to go around. Unfortunately the plane stalled as it tried to climb out, though it remains to be seen how exactly that mistake occurred.

Conversations (15)
The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.
Comment as a member

Membership is free and takes no more information than commenting as a guest. Earn status points for good contributions, and see fewer ads as your status grows.

Type your response here.

If you'd like to participate in the discussion, please adhere to our commenting guidelines. Anyone can comment, and your email address will not be published. Register to save your unique username and earn special OMAAT reputation perks!

  1. Loading comments…
Recent Comments
The latest from the OMAAT community.

The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.

Kent Miller Guest

Stick to premium travel related perspectives. It's fairly obvious that an "average person won’t understand much of what’s explained in the report" based on your interpretation of the evidence. There are alternative approaches to TO/GA and while some insist that the TO/GA is deactivated upon sensors on the landing gear strain gauges, it is common for pilots to reacquire control and perform TO/GA by themselves. This is a fairly complex event and the preliminary report, which I read, only reveals more questions than answers.

0
‼ 0
AAExPlat Guest

Not sure what there is to say about this other than the incident was caused by ABSOLUTELY POOR airmanship. No change in wind should cause a 3,000+ foot long landing and monitoring speed is essentially the most important part of any GA procedure. No speed = no lift. The utter incompetence shown by those two pilots is enough to have me question the safety culture of the entire airline. I won't fly OZ and AF for the same reason...sounds like EK may need to be added. If pilots cannot execute a common occurrence procedure like "GA" and "pitch and power", I am not going to sit myself or my family on one of their flights. Because it is only a matter of time until you'll be on one of their flights where this will need to be executed. I'd rather endure 10 hours of flying on a substandard product airline like AA or UA.

0
‼ 0
Falco Peregrinus Guest

Hello Lucky, You may want to red these blog posts from a pilot (I'm sure you know of him) about differences between Pilot and Co-Pilot/First Officer : www.askthepilot.com/questionanswers/seniority/ www.askthepilot.com/pilots-and-copilots/

0
‼ 0
George Guest

It has been reported that the recertification instructors keep stressing that all "auto pilot" commands are disabled once the wheel sensors detect touchdown. Therefore, it isn't enough to just press the TO/GA switch, the PF/PNF has to manually shift the throttle to full thrust. Maybe the pilot flying wasn't paying attention, or he forgot the operating manual. Once they heard the "Long Landing" call and decided on a GA at such low altitude, the PF should have taken over manual controls. This seems to be a combination of three compounded errors by the PF and PNF. 1. Even with a long landing, there was enough runway left to land the plane safely. There was no need to go around. 2. Once the PF decided to go around after touchdown, he just pressed the TO/GA switch expecting the Flight Director to take over the thrust management. Neither the PF or the PNF seems to have had a hand on the throttle to manually over ride if necessary. 3. It took them a full 12 seconds after the TO/GA switch press to realize the Flight Director hadn't increased the thrust, by which time it was too late.

0
‼ 0
Phi Lot Phac Up Guest

At 0837:35, three seconds before impact with the runway, both thrust levers were moved from the idle position to full forward. Pilot error. All the rest is BS.

0
‼ 0

Save posts to read later

Saving posts is a member feature. Become an OMAAT member to build a reading list you can come back to from any device.

Become a member
Meet Ben Schlappig, OMAAT Founder
5,883,136 Miles Traveled

43,914,800 Words Written

47,187 Posts Published