LEVEL 3 Final report

Based on the investigation authority's final report.

Date
Show source
Occurrence
Landing accident during attempted go-around
Location
Runway 12L, Dubai International Airport
Show source
Operator
Emirates
Show source
Aircraft
Boeing 777-31H
Show source
Registration
A6-EMW
Show source
Route
Trivandrum, India, to Dubai, United Arab Emirates
Show source
People aboard
300: 282 passengers and 18 crew
Show source
Fatalities
1 firefighter; 0 aboard
Show source
Survivors
All 300 occupants
Show source
Topics
Insufficient go-around thrust, Thrust verification omitted, Automation and training gaps

This photograph is cropped for the banner. See the full photograph, credit, licence and what it shows.

Photographs and geographic context

Emirates Boeing 777 A6-EMW taxiing at Munich Airport.

A6-EMW taxiing at Munich Airport in March 2010.

Photo: Molch-Entertainment, CC0 1.0 Universal

Image info

The accident aircraft photographed on 23 March 2010, before the accident.

Image source

Original photograph used with no crop. Responsive WebP copies resized without cropping.

Geographic context

Geographical orientation for Emirates 521Trivandrum departure airport; Dubai runway 12L. Approximate airport locations for the scheduled Trivandrum to Dubai route.12NORTH UP / SCHEMATIC / NOT A RECORDED FLIGHT TRACK
  1. Trivandrum departure airport
  2. Dubai runway 12L
Approximate airport locations for the scheduled Trivandrum to Dubai route. Basemap: Natural Earth, public domain.
Read supporting evidence

What happened

After a prolonged flare and brief main-gear contact, the crew attempted a go-around. Touchdown had inhibited the TO/GA switches, and the crew missed the idle thrust state. The aircraft climbed to 85 ft radio altitude, lost speed and descended onto the runway.

Read the full incident Follow what happened, from the flight to the investigation findings.

What investigators concluded

The AAIS attributed the accident to idle thrust, ineffective instrument monitoring, failure to recognize the autothrottle response and omitted thrust verification. Training, procedures, alerts, wind information and controller workload contributed.

Evidence behind this explanation

The landing and attempted go-around

1,551 words / about 8 minutes to read. Based on the investigation records cited below.

A scheduled arrival in changing winds

Emirates flight 521 departed Trivandrum International Airport in India at 05:06 UTC on 3 August 2016, bound for Dubai. The Boeing 777-31H, registered A6-EMW, carried 282 passengers, two pilots and 16 cabin crewmembers. The commander flew from the left seat and the copilot monitored the flight. The pilots had received approximately 30 hours of rest before the flight. The aircraft's calculated landing weight was 229,682 kg, within its limits. Investigators found that the aircraft had been maintained under its approved program and that its systems and engines performed as designed.

About an hour before landing, the pilots briefed approaches to Dubai's runways 12L and 30L. Their missed approach briefing specified flaps 20 and a climb to 3,000 ft. A moderate windshear warning applied to every runway from 07:40 to 09:00 UTC. The pilots confirmed receiving the airport information broadcast that carried the warning. At 08:06, they discussed a windshear escape maneuver, including use of the takeoff/go-around switch and keeping the aircraft configuration unchanged. The commander later told investigators that similar warnings were familiar at Dubai and that he expected the landing to be manageable.

Air traffic control vectored the aircraft for the RNAV approach to runway 12L. Two earlier aircraft went around at 08:29 and 08:31, followed by two Emirates 777s that landed at 08:33 and 08:35. Flight 521's crew received no information about those go-arounds. With the landing gear down, speedbrakes armed and flaps 30 selected, they completed the landing checklist. The approach was stabilized before 1,000 ft radio altitude. The commander disconnected the autopilot at 930 ft and continued manually, with the autothrottle engaged and the flight directors on.

The copilot called a 16 kt tailwind at 190 ft radio altitude and then reported it reducing to 13 kt. The reference landing speed was 147 kt, with 152 kt selected for the approach. The aircraft crossed the runway threshold at approximately 54 ft radio altitude and 159 kt indicated airspeed. About 100 m beyond the threshold, the commander began the flare at approximately 40 ft. The investigation considered that initiation earlier than recommended and identified it as a contributor to the extended landing distance.

Sources for this section

The extended flare and brief touchdown

At 25 ft radio altitude, the autothrottle changed from SPEED to IDLE and brought the thrust levers back. Airspeed initially fell to 153 kt, then increased to 165 kt as the aircraft floated just above the runway. The recorded increase of 12 kt occurred over approximately four seconds. Investigators attributed it to horizontal windshear as the wind shifted from a tailwind to a headwind. The additional lift prolonged the float. Both pilots were looking outside and missed the increasing airspeed. The commander referred to thermals and made several control inputs while trying to bring the aircraft onto the runway.

At 08:37:16, a correction following a left roll produced a right bank of 7.4 degrees. The right main landing gear contacted the runway approximately 1,090 m beyond the threshold, at 161 kt indicated airspeed. During the next six seconds, the main gear cycled through air and ground indications. Both main gear were simultaneously in ground mode for less than two seconds. The nose gear remained airborne. The pilots did not recognize that the main gear had touched down, and the commander believed the aircraft was still flying above the runway.

Approximately two and a half seconds after the right main gear first contacted the runway, the commander called for a go-around and pushed the left TO/GA switch. A long-landing alert followed. Weight on the main gear had inhibited the switches, so the push left the autothrottle in IDLE and the thrust levers at idle. Neither pilot checked the flight mode annunciations. The commander pulled back on the control column and called for flaps 20. The copilot selected that setting as the aircraft became airborne again at approximately 153 kt.

Sources for this section

A climb with idle thrust

The aircraft initially gained height despite the idle engines. Its remaining speed, headwind and landing configuration supplied enough lift for this brief climb. The copilot announced positive climb at approximately 47 ft radio altitude. The commander called for gear up at 58 ft, with airspeed down to 145 kt. The go-around procedure required both pilots to verify that engine thrust was increasing after the flap selection, followed by the monitoring pilot verifying sufficient thrust and adjusting it as necessary. They omitted these checks. The procedure had no verbal announcement for either verification, leaving each pilot unaware that the other had missed it.

During gear retraction, the tower instructed flight 521 to continue straight ahead and climb to 4,000 ft. The copilot read back the instruction and changed the selected altitude from the briefed 3,000 ft. The investigation found that the transmission added workload and momentarily affected flying and monitoring. At 08:37:31, the aircraft reached its maximum radio altitude of 85 ft at 131 kt, then began descending. The pilots still had not identified the idle thrust state. Their expectation that the autothrottle would manage thrust continued through most of the attempted go-around.

Three seconds later, the commander called a windshear escape maneuver. At 08:37:35 he manually advanced both thrust levers fully forward. The cockpit issued a don't-sink warning, and the copilot called attention to speed. An airspeed-low caution followed as the aircraft descended at approximately 800 ft per minute. At 08:37:38, its aft fuselage struck the runway at 124 kt, above the stall speed. The engines had begun responding to the lever movement, but the remaining height allowed too little time to develop sufficient thrust. Impact occurred 18 seconds after the go-around began.

Sources for this section

Impact, smoke and evacuation

With its gear retracting, the aircraft struck near taxiway November 7. The right engine and pylon separated as the aircraft slid along the runway on its lower fuselage for approximately 32 seconds. It stopped near taxiway Mike 13, approximately 70 m right of the runway centerline, on a heading of about 250 degrees. Fire appeared at the detached right engine and beneath the left engine. Dense smoke emerged from the right side near the main landing gear bay. The first rescue vehicles and fire commander reached the site within 90 seconds of the aircraft stopping.

The commander transmitted a mayday at 08:39:04 and advised the tower that the aircraft was being evacuated. The flight crew completed the evacuation checklist and ordered evacuation. Smoke formed a barrier between the forward and aft cabin. Resting on the fuselage lowered the doors and reduced the slide slope to approximately 14 degrees. Winds of roughly 12 to 15 kt, gusting to 18 kt, disrupted several slides. Cabin crew blocked unusable doors and redirected passengers as conditions changed. The L1 slide detached, while the R1 slide became usable briefly before damage caused it to deflate.

The L2 and L4 slides were lifted against the fuselage by wind. The R4 slide bowed and evacuation there was interrupted for approximately 40 seconds. A crewmember went onto that slide to help passengers, then returned inside to continue the evacuation. The L5 slide served passengers before wind lifted it against the aircraft. A firefighter stabilized the twisted R5 slide, enabling evacuation through that exit. Crew instructed passengers to leave baggage, but several took belongings. Most occupants escaped through the usable slides in approximately 6 minutes 40 seconds.

The commander and senior cabin crewmember remained inside to search for passengers, including a child separated from her family. Dense smoke forced them back toward the forward cabin. Approximately 9 minutes 40 seconds after the aircraft stopped, the center wing tank exploded. A large section of upper right-wing skin struck and killed a firefighter. The two remaining crewmembers subsequently jumped from L1 onto the detached slide. All 300 occupants survived. Four cabin crewmembers suffered serious injuries; 28 occupants suffered minor injuries. The report also records seven minor injuries among rescue and firefighting personnel.

Sources for this section

Findings and safety measures

Investigators also examined the firefighting response. Video and witness evidence showed that the foam applied lacked a secure blanket. They attributed this to application methods: jets struck the aircraft at near right angles, breaking down foam bubbles, while water applied elsewhere washed foam away. Tests of samples from the same concentrate batches met the applicable performance standards. The report recommended training that would help crews identify confined heat sources, understand fire dynamics and choose appropriate tactics.

The AAIS identified four causes: idle thrust during almost the entire attempted go-around; ineffective scanning and monitoring of primary flight instruments; failure to recognize that the autothrottle had not advanced the levers; and omitted thrust verification that prevented timely corrective action. Its contributing factors included the early flare and wind shift, inaccurate awareness of touchdown, reliance on automation and inadequate training for low-level go-arounds with inhibited TO/GA switches. The aircraft provided no alert for inhibited switches or for the mismatch between go-around configuration and insufficient thrust. The procedures also lacked thrust-verification and flight-mode-change callouts.

The final report recorded Emirates introducing training for go-arounds after touchdown and with TO/GA switches inhibited. It added simulator exercises involving subtle instructor errors, revised briefings and training on switch logic, and promoted tactile feedback from moving thrust levers. The AAIS recommended further improvements to go-around training and cockpit monitoring. Recommendations to Boeing covered alerts for insufficient go-around thrust, clearer switch-inhibit information and verbal thrust checks. Other recommendations addressed controller communications, windshear information, firefighting tactics, passenger management and slide performance after landing-gear collapse. The final investigation report was issued on 20 January 2020.

Sources for this section
Runway Impact during Attempted Go-Around: Emirates Boeing 777-31H A6-EMW1.18.2.1 Application of fire extinguishing agent | Printed page 74 | PDF page 88Find this passage in evidence search
Runway Impact during Attempted Go-Around: Emirates Boeing 777-31H A6-EMW1.18.2.2 Testing of fire extinguishing agent samples | Printed page 75 | PDF page 89Find this passage in evidence search
Runway Impact during Attempted Go-Around: Emirates Boeing 777-31H A6-EMW4.2.2 Safety actions taken by Emirates | Printed page 137 | PDF page 151Find this passage in evidence search
Runway Impact during Attempted Go-Around: Emirates Boeing 777-31H A6-EMW4.3.4 Safety recommendations addressed to The Boeing Company | Printed page 141 | PDF page 155Find this passage in evidence search
Runway Impact during Attempted Go-Around: Emirates Boeing 777-31H A6-EMW4.3.6 Safety recommendations addressed to FAA | Printed page 144 | PDF page 158Find this passage in evidence search

Return to the short summary / Source status and limitations

How the sequence developed

Follow the main stages, then open the evidence beneath each step.

  1. Early flare and changing wind

    An early flare and a shift from tailwind to headwind prolonged the float.

    Read supporting evidence
  2. Touchdown inhibited TO/GA

    Main-gear contact inhibited the switches before the commander attempted the go-around.

    Read supporting evidence
  3. Thrust checks missed

    The crew selected flaps and gear but failed to verify increasing thrust.

    Read supporting evidence
  4. Energy lost

    The aircraft climbed briefly at idle thrust, then lost speed and height.

    Read supporting evidence
  5. Impact and fire

    Runway impact separated the right engine and led to fire and evacuation.

    Read supporting evidence

A simplified reading of the investigation findings. The sequence does not replace the full report or imply that every contributing factor is shown.

Sequence of events

Times are UTC. Dubai local time was UTC plus four hours; impact occurred at 12:37:38 local. Expand an event to see its evidence.

  1. 05:06Departure

    Flight 521 departed Trivandrum for Dubai.

  2. 08:37:05Threshold crossing

    The aircraft crossed at about 54 ft radio altitude and 159 kt indicated airspeed.

  3. 08:37:16Main-gear contact

    The right main gear touched approximately 1,090 m beyond the threshold.

  4. 08:37:31Maximum height

    The aircraft reached 85 ft radio altitude and began losing height.

  5. 08:37:35Manual thrust increase

    The commander advanced both levers to maximum.

  6. 08:37:38Runway impact

    The aft fuselage struck the runway with the gear retracting.

  7. 08:47:50Tank explosion

    The center wing tank exploded; a wing panel fatally injured a firefighter.

Search the report evidence

Search extracted report prose, with original page references. Short results link to the full document.

Questions readers ask

Why did the go-around lose height?

Both engines remained at idle until the final three seconds before impact. The crew omitted thrust verification and the aircraft had insufficient energy to sustain flight.

Why did the TO/GA switch fail to increase thrust?

Main-gear contact had inhibited the switches. The commander expected the autothrottle to advance the thrust levers, while its mode remained IDLE.

How did everyone aboard escape?

Passengers and most crew left through the usable slides in approximately 6 minutes 40 seconds. The commander and senior cabin crewmember left through L1 after the center wing tank exploded.

What the evidence can and cannot establish

Safety follow-up

Actions and recommendations are described at the dates of the cited records. A recommendation is not proof of implementation.

Evacuation and rescue recommendations

The AAIS recommended improved firefighting training and a review of slide performance with collapsed landing gear and wind.

Read supporting evidence
Runway Impact during Attempted Go-Around: Emirates Boeing 777-31H A6-EMW4.3.3 Safety recommendations addressed to Dubai Airports | Printed page 140 | PDF page 154Find this passage in evidence search
Runway Impact during Attempted Go-Around: Emirates Boeing 777-31H A6-EMW4.3.6 Safety recommendations addressed to FAA | Printed page 144 | PDF page 158Find this passage in evidence search

Classifications, with reasons

These labels organise the evidence. They are not a ranking of causes. A shared label means a shared research topic, not an identical mechanism.

CauseInsufficient go-around thrust

Both engines remained at idle until three seconds before impact, leaving insufficient energy to sustain flight.

CauseThrust verification omitted

The pilots missed the idle thrust state and omitted the procedure checks that could have prompted corrective action.

Contributing factorAutomation and training gaps

Training did not adequately cover go-arounds close to the runway with TO/GA switches inhibited.

Read alongside

These comparisons connect specific research topics. Shared circumstances do not establish identical causes. Evidence from both investigations is provided below.

Asiana Airlines Flight 214

Both Boeing 777 accidents involved idle thrust, missed automation cues and ineffective airspeed or thrust monitoring. At Dubai, main-gear contact inhibited the TO/GA switches, and the Emirates crew omitted thrust verification during the attempted go-around. During Asiana 214's visual approach at San Francisco, the pilot manually resisted advancing thrust levers, causing the autothrottle to enter HOLD and stop controlling thrust or airspeed. The NTSB identified unintended deactivation of automatic airspeed control, inadequate airspeed monitoring and delayed execution of a go-around among the probable causes. Both investigations identified weaknesses in automation training and operating information.

Read supporting evidence
NTSB AAR-14/01: Asiana Airlines 2142.2.2 Approach from 5 nm to the Runway | Printed page 81 | PDF page 99Find this passage in evidence search
NTSB AAR-14/01: Asiana Airlines 2143.2 Probable Cause | Printed page 129 | PDF page 147Find this passage in evidence search
NTSB AAR-14/01: Asiana Airlines 2143.2 Probable Cause | Printed page 129 | PDF page 147Find this passage in evidence search

Further investigation records

Explore the records below for additional context. They open on the publisher's site and are not all included in our report search. Source reuse terms apply.

Sources and transparency

GCAA AAIS final report issued 20 January 2020.

Source limitations

Fire destroyed the R3 door, preventing further examination of the slide-ramp deployment failure.

Runway Impact during Attempted Go-Around: Emirates Boeing 777-31H A6-EMW

UAE GCAA Air Accident Investigation Sector
Final report AIFN/0008/2016, issued 20 January 2020

Official report PDF, hosted by gcaa.gov.ae

Open source document

164 PDF pages.

GCAA report linked as the official investigation source. Original explanatory text and short supporting quotations. Source terms.

Read the extraction, classification and review methodology.

Suggest a correction to this dossier

Editorial record

Kevin Murphy writes the incident accounts on AirlineIncidents.com, out of a long interest in aviation safety and the lessons each investigation leaves behind.

Prepared by
AirlineIncidents editorial desk
Report citation check
Independent expert review
Not completed

Citation checks compare supporting text with the indexed report pages. They do not constitute independent expert review. How these pages are prepared.

Revision history

: Final investigation completed; GCAA AAIS report issued 20 January 2020.

Source-based corrections are reviewed before changes appear here. Suggest a correction to this dossier.