Emirates’ (Probably) Terrifying Boeing 777 Flight To Washington

Aviation is incredibly safe, and for every disaster there are many catastrophes that are narrowly avoided. It would appear that an Emirates Boeing 777 departing Dubai about a week ago nearly had a major incident after takeoff. Let me share what I’ve been able to piece together so far.

What happened to this Emirates plane on takeoff?

The flight in question is Emirates EK231 from Dubai (DXB) to Washington Dulles (IAD), which was scheduled to depart at 2:25AM on Monday, December 20, 2021. The flight was operated by one of Emirates’ newest Boeing 777-300ERs, with the registration code A6-EQI.

Here’s what I’ve been able to piece together, and I’m trying to explain this as simply as possible, so the average person can understand it (and if I get anything wrong pilots are more than welcome to correct me, but please do so in language everyone can understand):

  • The crew operating the previous flight with the aircraft had set the altitude to zero in the flight director system (which controls the autopilot); the crew on this flight was supposed to (but didn’t) set the altitude to 4,000 feet, which is a standard altitude to first climb to after departure
  • During the departure, the pilot flying the aircraft decided to “follow” what the flight director was showing, which was an altitude of zero feet
  • While the plane would typically rotate at a much lower speed, the plane was still on the ground at 216 knots, and even overran the standard runway area, and only took off in the runway safety area
  • The plane was already flying over houses at an altitude of 75 feet, going a minimum of 234 knots
  • The plane barely gained altitude, and was at an altitude of just 175 feet when it was flying at a speed of 262 knots
  • As a point of comparison, ordinarily the plane would be at well under 200 knots at that altitude, and would be climbing much faster
  • While it would be standard to return to the airport to assess damage when something like this happens (given the potential for overspeed with the flaps, plus the potential damage if the aircraft did unknowingly hit something), the pilots made the decision to continue to Washington
  • It’s my understanding that the US Federal Aviation Administration (FAA) is now investigating this incident, and that at least the two pilots at the controls have been suspended, or possibly even fired

The thing that stands out here the most is the complete lack of control that the crew had over the plane. The crew was managing the computers rather than flying the aircraft. What would posses a crew to overrun the standard portion of a runway while going over 200 knots, when there was nothing wrong with the plane? And on top of that there were four pilots, so how did none of them catch on to this error?

For those curious, below is some data from Flightradar24 for the flight in question vs. a more “standard” flight on the same route. Note that while the data on Flightradar24 isn’t always accurate, it’s my understanding that these numbers match what’s believed to have happened, and what’s being investigated. You’ll want to look at the right two columns, with the left column being the altitude, and the right column being the speed.

Here’s the data for the flight in question:

Then here’s the data for the same flight several days earlier:

As you can tell, that data is vastly different. This sounds concerning — a Boeing 777 (presumably) full of passengers and fuel was barely climbing after takeoff, but rather just kept gaining speed, to the point that it was lower than many high rises in Dubai.

This incident happened on an Emirates Boeing 777

Emirates has sent a memo to pilots

While Emirates hasn’t yet officially commented on this incident, the airline did send out the following alert to pilots on Monday, essentially referencing the incident:

CREWS ARE REMINDED THAT THERE ARE NO FCOM NORMAL PROCEDURE REQUIREMENTS TO CHANGE THE MCP AFTER LANDING OR SHUTDOWN. THERE HAVE BEEN TIMES WHEN THE MCP “ALTITUDE WINDOW” HAS BEEN SET TO THE AIRPORT ELEVATION WHICH MAY CAUSE ISSUES ON THE SUBSEQUENT DEPARTURE. CREWS SHALL NOT SET AIRPORT ELEVATION ON THE MCP AFTER LANDING OR SHUT DOWN.

In other words, Emirates is telling pilots not to set the altitude to zero on approach, for fear of the next crew not changing that.

I wonder what it was like on the plane

I’d be curious to hear from a passenger onboard, because I wonder if passengers had any clue what was going on:

  • On the one hand, perhaps passengers didn’t really know what was going on, since it was dark outside, and most people aren’t really avgeeks and paying attention to every aircraft movement
  • On the other hand, perhaps passengers totally knew what was going on, given that the plane was going at a very high speed while still on the runway, and then barely climbed after takeoff

While I feel safe flying with Emirates, in general I’m not surprised to see things like this happen once in a while:

  • Emirates pilots deal with a lot of fatigue, given that they often operate ultra long haul flights departing in the middle of the night; no matter how hard you try, this has to take a toll on you
  • In general Emirates hires 777 pilots with less experience than you’d find at some other airlines; that’s largely because it’s Emirates’ smallest plane, and Emirates isn’t going to consistently have a couple of people with 10,000+ flights hours at the controls (as you’d find on American and United, for example)
  • Then there’s coronavirus, which in general has caused a lot of pilots to become a bit rusty, since many have only recently been brought to work after being furloughed
I wonder what this incident was like for passengers

Bottom line

While I’m sure more information will emerge soon, it’s my understanding that an Emirates Boeing 777 had a pretty frightening departure out of Dubai about a week ago. Specifically, the altitude for after takeoff was set to ground level rather than 4,000 feet, and as a result the plane didn’t climb very high, but rather just sped up.

As a result, the plane overran the standard portion of the runway, and then flew at a very low altitude while going very fast. I imagine this must have been frightening for everyone onboard, and those on the ground who were awake (or who were woken up by the noise of such a low aircraft).

Since the FAA is allegedly investigating the incident, hopefully we end up learning more. If anyone has more details on the incident, please chime in!

(Tip of the hat to God Save The Points)

Conversations (227)
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.

Katrina M. Guest

I was on that flight (happy to share my plane ticket as proof). I remember a sunken feeling in my stomach shortly after takeoff (similar to what you feel on a roller coaster when it drops). I remember clenching the armrest, and a couple of passengers near me looking around. We all knew it was a feeling that wasn't normal, but it lasted for a few seconds before feeling "normal" again. I honestly forgot about that moment once we landed 13 hours later. I think most passengers forgot and dismissed that feeling because it was so quick compared to the full flight time. If it had made the news, I'm sure many would have commented on that shared feeling of going way too fast but not reaching altitude. It felt like a roller coaster ride. Reading this article makes me so grateful to be alive. It's eerie to know what it feels like when something is wrong with a flight you're on. For reference, I lived in the UAE for 8 years and took many Emirates flights. The journey from Dubai to Washington, D.C. was a familiar trip so this flight in particular really stands out to me.

0
‼ 0
TacoPete82 Guest

When you operate off clock, you adjust your rest schedule to accommodate these changes. To say this was due to fatigue is ridiculous.

0
‼ 0
MandR Guest

Wow, it's 2025, and I just saw this. I was on this flight with my daughter—she was recording the takeoff at the time and wondering why it was taking longer than usual. We are frequent flyers on this route, so it felt unusual. It's scary to hear about this now. Thank God nothing bad happened.

0
‼ 0
Pradipta Shome Guest

Thanks for letting us know of this incident and appropriate corrective measures being instituted.

0
‼ 0
John Voxx Guest

I have been only flying Emirates for two factors. A) rich airline, unlimited free fuel, brand new aircrafts B) White western pilots - meaning well trained qualified and safe. This flight in question was flying with point B totally compromised meaning they need to have Arab pilots who performed this kind of dangerous stunt. Why is no one mentioning the names of those pilots in question?

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