Emirates Flight 521

The aircraft involved was a Boeing 777-31H[note 1] with the registration A6-EMW, serial number 32700, and line number 434. It was equipped with two Rolls-Royce Trent 892 engines and was 13 years old, having made its first flight on 7 March 2003.[13] It was delivered new to Emirates on 28 March 2003, and had logged more than 58,000 flight hours in 13,000 cycles before the crash.[1]^: 14

The captain was a 34-year-old UAE national who had been with Emirates since March 2001 and had logged 7,457 flight hours, including 5,123 hours on the Boeing 777.[1] The first officer was 37-year-old Australian national who had been with Emirates since October 2014 and had 7,957 flight hours, with 1,292 of them on the Boeing 777.[1][14]

On 3 August 2016, Flight EK521 took off from Trivandrum International Airport (TRV) at 10:34 IST (05:04 UTC), 29 minutes after its scheduled departure time. It was scheduled to land at Dubai International Airport (DXB) at 12:24 GST (08:24 UTC).[15]

The approach and landing were normal from the air traffic control (ATC) point of view, with no emergency declared according to ATC recordings at the time.[16][17] The crew reported that they were going around, after which the tower instructed them to climb to 4,000 feet (1,200 m), which was acknowledged by the crew. Shortly after, the tower instructed the next flight to go around and alerted emergency services.[16] Wind shear and an ambient temperature of 48 °C (118 °F) were reported.[13]

The accident occurred at 12:37 GST (08:37 UTC). Significant wind shear affected the aircraft's airspeed through late final approach, and the aircraft touched down onto the 4,000-metre-long (13,000 ft) runway 12L at a point about 1,100 metres (3,600 ft) beyond the threshold, at a speed of 162 knots (300 km/h; 186 mph).[1] Two seconds later, the cockpit RAAS issued a "LONG LANDING" [note 2] warning and the crew initiated a go-around.[1] Six seconds after main-wheel touchdown, and with the nose-wheel still off the runway, the aircraft became airborne again after rotating to climb attitude. The flap setting was reduced to 20°, and the undercarriage was selected to retract, but the engine throttle remained unchanged because activation of go-around automation is inhibited after touchdown. The aircraft attained a maximum height above the runway of 85 feet (26 m) with its indicated airspeed decreasing, before commencing to settle back towards the ground. Twelve seconds after becoming airborne, the crew manually advanced the throttles to maximum, but the aircraft continued to sink, and it impacted the runway with its undercarriage in a partially retracted state 3 seconds later.[1]^: 81–86

The aircraft first impacted with the underside of its rear fuselage and skidded about 800 metres (2,600 ft; 870 yd) along runway 12L with its landing gear partly retracted as it turned to the right about 120°.[1] As the aircraft skidded down the runway, the number-2 (starboard or right) engine detached and slid along the wing's leading edge toward the wingtip.[1] Firefighting appliances were at the aircraft less than 90 seconds after it came to rest (which was 33 seconds after the initial impact) and started to fight fires at several locations, as all 300 passengers and crew were safely evacuated.[1][19] Videos from inside the aircraft, taken on passengers' cellphone cameras, showed the passengers failing to evacuate, instead giving priority to carry-on luggage, resulting in an overly long evacuation and heavy criticism.[20] Nine minutes after the aircraft came to a stop, with only the aircraft captain and the senior flight attendant still on board (checking for any remaining passengers), an explosion occurred as flames reached the aircraft's center fuel tank. The explosion resulted in the death of a firefighter,[1]^: 36–38 a Ras al-Khaimah resident named Jasim Issa Mohammed Hasan.[21] Thirty-two of the aircraft's occupants were injured, including the captain and the senior flight attendant, who evacuated after the explosion; the senior flight attendant was the only person among the passengers and crew seriously injured, suffering from smoke inhalation.[16][1]^: 7 In addition, seven firefighters were injured,[1]^: 7 several of the firefighters suffering from heat stroke.[1][22] The explosion spread the fire to the aircraft's cabin; firefighters needed 16 hours to bring the fire under control.[1] The airport was closed during and following the accident, which resulted in many diverted flights.[23]

The aircraft carried 282 passengers and 18 crew members.[24]

The General Civil Aviation Authority (GCAA) carried out an investigation into the accident,[26] assisted by Emirates; the aircraft's manufacturer Boeing; and Rolls-Royce, the manufacturer of the 777's engines.[27] In addition, the United States National Transportation Safety Board (NTSB) sent a five-person team to join the other investigators.[28] The flight data recorder and cockpit voice recorder were removed from the aircraft the day after the accident.[22][29] A preliminary report into the accident was published in September 2016,[8][30] and an interim statement in August 2017.[31] A preliminary report found that the pilot attempted to take off again after briefly touching down, and that the plane ultimately hit the runway as its landing gear was still retracting.[8]

The final report was released on 6 February 2020.[32][1] In the report, the following was noted in the causes section:

The flight crew did not effectively scan and monitor the primary flight instrumentation parameters during the landing and the attempted go-around. The flight crew were unaware that the autothrottle (A/T) had not responded to move the engine thrust levers to the takeoff/go-around switch (TO/GA) position after the commander pushed the TO/GA switch at the initiation of the FCOM ̶ go-around and missed approach procedure.[33]

The report concluded by saying:

The flight crew reliance on automation and lack of training in flying go-arounds from close to the runway significantly affected the flight crew performance in a critical flight situation which was different to that experienced by them during their simulated training flights.[33]

Following the accident, the airport was closed for 5+1⁄2 hours; many flights were diverted to nearby airports such as Abu Dhabi International Airport, Sharjah International Airport, and Al Maktoum International Airport.[34] The closure led Emirates and flydubai to cancel several of their flights,[35][36] and also affected 23,000 passengers at the airport.[37] Dubai International Airport resumed operations at 18:30 local time,[38][39] at restricted capacity, using only one runway and maximizing the use of the runways at Al Maktoum International Airport.[37] Arriving aircraft were prioritized over departure flights.[40] The damaged runway was repaired and reopened at 17:45 local time on 4 August,[40][41][42] and the airport resumed normal operations on 6 August 72 hours after the accident.[43][44]

On 11 August, eight days after the crash, Emirates provided US$7000 in compensation for each of the 282 passengers.[45]

Emirates changed the flight number of the Trivandrum to Dubai service to EK523.[46]

• China Airlines Flight 140 and Atlas Air Flight 3591 are other flights that crashed in a go around due to pilot errors.

• Incident statement by Emirates