m
General fixes, removed erroneous space
>HolyT (→Flight: ce simpler, less awkward syntax) |
imported>SdkbBot m (General fixes, removed erroneous space) |
||
| Line 9: | Line 9: | ||
| occurrence_type = Accident | | occurrence_type = Accident | ||
| date = {{Start date|2016|08|03|df=yes}} | | date = {{Start date|2016|08|03|df=yes}} | ||
| summary = Crashed during [[go-around]] due to [[pilot error]] in failure to monitor thrust<ref name=Final/>{{rp|134}} | | summary = Crashed during [[go-around]] due to [[pilot error]] in failure to monitor [[thrust]]<ref name=Final/>{{rp|134}} | ||
| site = [[Dubai International Airport]], [[Dubai]], [[United Arab Emirates]] | | site = [[Dubai International Airport]], [[Dubai]], [[United Arab Emirates]] | ||
| coordinates = {{coord|25|14|51|N|55|22|46|E|type:event|display=inline,title}} | | coordinates = {{coord|25|14|51|N|55|22|46|E|type:event|display=inline,title}} | ||
| Line 51: | Line 51: | ||
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.<ref name="AH49c12302"/><ref>{{cite web|url=http://archive-server.liveatc.net/omdb/OMDB-Twr-Both-Aug-03-2016-0830Z.mp3|title=OMDB Towers, 3 Aug 2016 0830-0900Z|publisher=LiveATC.net|access-date=3 August 2016}}{{Dead link|date=September 2018 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> The crew reported that they were [[Go-around|going around]], after which the tower instructed them to climb to 4,000 feet, which was acknowledged by the crew. Shortly after, the tower instructed the next flight to go around and alerted emergency services.<ref name=AH49c12302>{{cite web|url=http://avherald.com/h?article=49c12302|title=Accident: Emirates B773 at Dubai on Aug 3rd 2016, touched down during go-around without gear, aircraft on fire |work=Aviation Herald |access-date=3 August 2016}}</ref> Wind shear and an ambient temperature of {{convert|48|C}} were reported.<ref name="ASN030816">{{cite web|url=https://aviation-safety.net/database/record.php?id=20160803-0|title=A6-EMW Accident description|last=Ranter|first=Harro|website=aviation-safety.net|publisher=[[Flight Safety Foundation]] which owns the [[Aviation Safety Network]]|access-date=3 August 2016}}</ref> | 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.<ref name="AH49c12302"/><ref>{{cite web|url=http://archive-server.liveatc.net/omdb/OMDB-Twr-Both-Aug-03-2016-0830Z.mp3|title=OMDB Towers, 3 Aug 2016 0830-0900Z|publisher=LiveATC.net|access-date=3 August 2016}}{{Dead link|date=September 2018 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> The crew reported that they were [[Go-around|going around]], after which the tower instructed them to climb to 4,000 feet, which was acknowledged by the crew. Shortly after, the tower instructed the next flight to go around and alerted emergency services.<ref name=AH49c12302>{{cite web|url=http://avherald.com/h?article=49c12302|title=Accident: Emirates B773 at Dubai on Aug 3rd 2016, touched down during go-around without gear, aircraft on fire |work=Aviation Herald |access-date=3 August 2016}}</ref> Wind shear and an ambient temperature of {{convert|48|C}} were reported.<ref name="ASN030816">{{cite web|url=https://aviation-safety.net/database/record.php?id=20160803-0|title=A6-EMW Accident description|last=Ranter|first=Harro|website=aviation-safety.net|publisher=[[Flight Safety Foundation]] which owns the [[Aviation Safety Network]]|access-date=3 August 2016}}</ref> | ||
The accident occurred at 12:37 GST (08:37 UTC). Significant [[wind shear]] affected the aircraft's airspeed through late [[Final approach (aeronautics)|final approach]], and the aircraft touched down onto the {{convert|4000|m}} long runway 12L at a point approximately {{convert|1100|m}} beyond the [[Runway|threshold]], at a speed of {{convert|162|kn|km/h mph|abbr=}}.<ref name="Final" /> Two seconds later, the cockpit [[Runway Awareness and Advisory System|RAAS]] issued a "LONG LANDING" {{#tag:ref|The Runway Awareness Advisory System's "LONG LANDING" monitor warning indicates when an aircraft has not touched down within a pre-configured distance from the runway threshold, which may result in the remaining runway length being insufficient to bring the aircraft to a complete stop.<ref name="RAAS">{{cite web|last1=Honeywell International Inc|title=Product Description - SmartRunway/SmartLanding|url=https://www51.honeywell.com/aero/common/documents/egpws-documents/raas-documents/SmartRunway_SmartLanding_description.pdf|website=www51.honeywell.com|publisher=Honeywell|access-date=8 September 2016|page=9}}</ref>|group="note"}} warning and the crew initiated a [[go-around]].<ref name="Final" /> 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 (aeronautics)|flap]] setting was reduced to 20°, and the [[Undercarriage (aeronautics)|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 {{ convert | 85 | ft | 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 three seconds later.<ref name=Final />{{rp|pages= | The accident occurred at 12:37 GST (08:37 UTC). Significant [[wind shear]] affected the aircraft's airspeed through late [[Final approach (aeronautics)|final approach]], and the aircraft touched down onto the {{convert|4000|m}} long runway 12L at a point approximately {{convert|1100|m}} beyond the [[Runway|threshold]], at a speed of {{convert|162|kn|km/h mph|abbr=}}.<ref name="Final" /> Two seconds later, the cockpit [[Runway Awareness and Advisory System|RAAS]] issued a "LONG LANDING" {{#tag:ref|The Runway Awareness Advisory System's "LONG LANDING" monitor warning indicates when an aircraft has not touched down within a pre-configured distance from the runway threshold, which may result in the remaining runway length being insufficient to bring the aircraft to a complete stop.<ref name="RAAS">{{cite web|last1=Honeywell International Inc|title=Product Description - SmartRunway/SmartLanding|url=https://www51.honeywell.com/aero/common/documents/egpws-documents/raas-documents/SmartRunway_SmartLanding_description.pdf|website=www51.honeywell.com|publisher=Honeywell|access-date=8 September 2016|page=9}}</ref>|group="note"}} warning and the crew initiated a [[go-around]].<ref name="Final" /> 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 (aeronautics)|flap]] setting was reduced to 20°, and the [[Undercarriage (aeronautics)|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 {{ convert | 85 | ft | 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 three seconds later.<ref name=Final />{{rp|pages=81–86}} | ||
The aircraft first impacted with the underside of its rear fuselage and skidded about {{convert|800|m}} along runway 12L with its [[landing gear]] partly retracted as it turned to the right about 120 degrees.<ref name="Final" /> As the aircraft skidded down the runway, the [[Aircraft engine position number|number 2]] (starboard) engine detached and slid along the wing's leading edge toward the wingtip.<ref name="Final" /> 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.<ref name="Final" /><ref>{{cite tweet|user=DXBMediaOffice|number=760770176329641984|title=All reported safe|date=3 August 2016}}</ref> 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.<ref>{{cite web|title=Scenes from inside flight Emirates EK 521|url=https://www.youtube.com/watch?v=c6aKMTlBKVo}}</ref> 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), there was an explosion as flames reached the aircraft's center fuel tank. The explosion resulted in the death of a firefighter,<ref name="Final" />{{rp|page=36–38|}} a [[Ras al-Khaimah]] resident named Jasim Issa Mohammed Hasan.<ref>{{Cite web|last1=Bond|first1=Anthony|last2=Evans|first2=Sophie|date=2016-08-03|title=Hero firefighter dies saving 282 passengers in Emirates plane crash|url=http://www.mirror.co.uk/news/world-news/emirates-plane-crash-hero-firefighter-8553934|access-date=2020-09-25|website=mirror}}</ref> 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.<ref name=AH49c12302/><ref name=Final />{{rp|page=7}} In addition, seven firefighters were injured,<ref name=Final />{{rp|page=7}} several of the firefighters suffering from [[heat stroke]].<ref name="Final" /><ref name=Cromwell /> The explosion spread the fire to the aircraft's cabin; it took firefighters 16 hours to bring the fire under control.<ref name="Final" /> The airport was closed during and following the accident, which resulted in many diverted flights.<ref>{{cite tweet|number=760780236665544704|user=FlightRadar24|title=Dubai International Airport remains closed for takeoffs & landings after earlier #EK521 accident.|date=3 August 2016}}</ref> | The aircraft first impacted with the underside of its rear fuselage and skidded about {{convert|800|m}} along runway 12L with its [[landing gear]] partly retracted as it turned to the right about 120 degrees.<ref name="Final" /> As the aircraft skidded down the runway, the [[Aircraft engine position number|number 2]] (starboard) engine detached and slid along the wing's leading edge toward the wingtip.<ref name="Final" /> 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.<ref name="Final" /><ref>{{cite tweet|user=DXBMediaOffice|number=760770176329641984|title=All reported safe|date=3 August 2016}}</ref> 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.<ref>{{cite web|title=Scenes from inside flight Emirates EK 521|url=https://www.youtube.com/watch?v=c6aKMTlBKVo}}</ref> 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), there was an explosion as flames reached the aircraft's center fuel tank. The explosion resulted in the death of a firefighter,<ref name="Final" />{{rp|page=36–38|}} a [[Ras al-Khaimah]] resident named Jasim Issa Mohammed Hasan.<ref>{{Cite web|last1=Bond|first1=Anthony|last2=Evans|first2=Sophie|date=2016-08-03|title=Hero firefighter dies saving 282 passengers in Emirates plane crash|url=http://www.mirror.co.uk/news/world-news/emirates-plane-crash-hero-firefighter-8553934|access-date=2020-09-25|website=mirror}}</ref> 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.<ref name=AH49c12302/><ref name=Final />{{rp|page=7}} In addition, seven firefighters were injured,<ref name=Final />{{rp|page=7}} several of the firefighters suffering from [[heat stroke]].<ref name="Final" /><ref name=Cromwell /> The explosion spread the fire to the aircraft's cabin; it took firefighters 16 hours to bring the fire under control.<ref name="Final" /> The airport was closed during and following the accident, which resulted in many diverted flights.<ref>{{cite tweet|number=760780236665544704|user=FlightRadar24|title=Dubai International Airport remains closed for takeoffs & landings after earlier #EK521 accident.|date=3 August 2016}}</ref> | ||
| Line 115: | Line 115: | ||
The [[General Civil Aviation Authority]] (GCAA) carried out an investigation into the accident,<ref name=Opened>{{cite tweet |user=gcaa_uae |number=760798690470658049 |author=General Civil Aviation Authority |author-link=General Civil Aviation Authority |date=3 August 2016 |title=(untitled) }}</ref> assisted by Emirates; the aircraft's manufacturer Boeing; and Rolls-Royce, the manufacturer of the 777's engines.<ref>{{cite web|author1=Cornwell|first=Alexander|date=4 August 2016|title=Exclusive: Emirates EK521 investigation to take 3 to 5 months|url=http://gulfnews.com/business/aviation/exclusive-emirates-ek521-investigation-to-take-3-to-5-months-1.1873555|access-date=4 August 2016|website=Gulf News|publisher=Al Nasir Publishing}}</ref> In addition, the United States [[National Transportation Safety Board]] (NTSB) sent a five-person team to join the other investigators.<ref>{{cite web|title=Emirates jet tried to abort landing shortly before Dubai crash (VIDEO)|url=http://www.themalaymailonline.com/world/article/emirates-jet-tried-to-abort-landing-shortly-before-dubai-crash|website=Malay Mail Online|access-date=7 August 2016|location=Dubai|date=6 August 2016}}</ref> The [[flight data recorder]] and [[cockpit voice recorder]] were removed from the aircraft the day after the accident.<ref name="Cromwell">{{cite web|url=http://gulfnews.com/news/uae/emergencies/investigators-recover-ek521-recorders-1.1873897|title=Investigators recover EK521 recorders|author1=Cornwell|first=Alexander|date=4 August 2016|website=Gulf News|publisher=Al Nasir Publishing|access-date=4 August 2016}}</ref><ref name="KJTimes1">{{cite web|url=http://khaleejtimes.com/20160804/8024/no-title|title=DXB facilities now 'fully operational', black box recovered|author1=Clarke|first=Kelly|date=4 August 2016|website=Khaleej Times|access-date=4 August 2016}}</ref> A preliminary report into the accident was published in September 2016,<ref name=Prelim/><ref>{{Cite news|title=Investigation into Emirates crash landing 'could take up to three years'|work=The National|url=http://www.thenational.ae/uae/investigation-into-emirates-crash-landing-could-take-up-to-three-years|access-date=2016-11-21}}</ref> and an interim statement in August 2017.<ref name=Interim>{{cite web |url=https://www.gcaa.gov.ae/en/ePublication/admin/iradmin/Lists/Incidents%20Investigation%20Reports/Attachments/108/2016-AIFN-0008-0016%20First%20Interim%20Statement.pdf |title=First Interim Statement: AAIS Case №. AIFN/0008/2016 |publisher=General Civil Aviation Authority |location=Abu Dhabi |access-date=6 August 2017}}</ref> 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.<ref name="Prelim" /> | The [[General Civil Aviation Authority]] (GCAA) carried out an investigation into the accident,<ref name=Opened>{{cite tweet |user=gcaa_uae |number=760798690470658049 |author=General Civil Aviation Authority |author-link=General Civil Aviation Authority |date=3 August 2016 |title=(untitled) }}</ref> assisted by Emirates; the aircraft's manufacturer Boeing; and Rolls-Royce, the manufacturer of the 777's engines.<ref>{{cite web|author1=Cornwell|first=Alexander|date=4 August 2016|title=Exclusive: Emirates EK521 investigation to take 3 to 5 months|url=http://gulfnews.com/business/aviation/exclusive-emirates-ek521-investigation-to-take-3-to-5-months-1.1873555|access-date=4 August 2016|website=Gulf News|publisher=Al Nasir Publishing}}</ref> In addition, the United States [[National Transportation Safety Board]] (NTSB) sent a five-person team to join the other investigators.<ref>{{cite web|title=Emirates jet tried to abort landing shortly before Dubai crash (VIDEO)|url=http://www.themalaymailonline.com/world/article/emirates-jet-tried-to-abort-landing-shortly-before-dubai-crash|website=Malay Mail Online|access-date=7 August 2016|location=Dubai|date=6 August 2016}}</ref> The [[flight data recorder]] and [[cockpit voice recorder]] were removed from the aircraft the day after the accident.<ref name="Cromwell">{{cite web|url=http://gulfnews.com/news/uae/emergencies/investigators-recover-ek521-recorders-1.1873897|title=Investigators recover EK521 recorders|author1=Cornwell|first=Alexander|date=4 August 2016|website=Gulf News|publisher=Al Nasir Publishing|access-date=4 August 2016}}</ref><ref name="KJTimes1">{{cite web|url=http://khaleejtimes.com/20160804/8024/no-title|title=DXB facilities now 'fully operational', black box recovered|author1=Clarke|first=Kelly|date=4 August 2016|website=Khaleej Times|access-date=4 August 2016}}</ref> A preliminary report into the accident was published in September 2016,<ref name=Prelim/><ref>{{Cite news|title=Investigation into Emirates crash landing 'could take up to three years'|work=The National|url=http://www.thenational.ae/uae/investigation-into-emirates-crash-landing-could-take-up-to-three-years|access-date=2016-11-21}}</ref> and an interim statement in August 2017.<ref name=Interim>{{cite web |url=https://www.gcaa.gov.ae/en/ePublication/admin/iradmin/Lists/Incidents%20Investigation%20Reports/Attachments/108/2016-AIFN-0008-0016%20First%20Interim%20Statement.pdf |title=First Interim Statement: AAIS Case №. AIFN/0008/2016 |publisher=General Civil Aviation Authority |location=Abu Dhabi |access-date=6 August 2017}}</ref> 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.<ref name="Prelim" /> | ||
The final report was released on February 6, 2020.<ref>{{Cite web|url=https://www.gcaa.gov.ae/en/Pages/NewsDetails.aspx?NewsID=490|title=Final report news notice on gcaa.gov.ae|publisher=General Civil Aviation Authority|access-date=7 February 2020}}</ref><ref name="Final">{{cite web|url=https://www.gcaa.gov.ae/en/ePublication/admin/iradmin/Lists/Incidents%20Investigation%20Reports/Attachments/125/2016-Published%20Final%20Report%20AIFN-0008-2016-UAE521%20on%206-Feb-2020.pdf|title=Final Report: AAIS Case No: AIFN/0008/2016 Runway Impact during Attempted Go-Around|date=20 January 2020<!--This was the date it was issued-->|publisher=General Civil Aviation Authority|access-date=7 February 2020}}</ref> In the report, the following was noted in the causes section:<blockquote> | |||
The final report was released on February | |||
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 TO/GA position after the Commander pushed the TO/GA switch at the initiation of the FCOM ̶ Go-around and Missed Approach Procedure.<ref>{{Cite web|title=Emirates Flight 521 Crash Report|url=https://travelradar.aero/pilot-error-emirates-flight-521-crash-report-released/14050/|last=Deo|first=Ankur|date=22 February 2020|website=Travel Radar|access-date=6 May 2020}}</ref></blockquote> | 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 TO/GA position after the Commander pushed the TO/GA switch at the initiation of the FCOM ̶ Go-around and Missed Approach Procedure.<ref>{{Cite web|title=Emirates Flight 521 Crash Report|url=https://travelradar.aero/pilot-error-emirates-flight-521-crash-report-released/14050/|last=Deo|first=Ankur|date=22 February 2020|website=Travel Radar|access-date=6 May 2020}}</ref></blockquote> | ||
| Line 123: | Line 121: | ||
==Aftermath== | ==Aftermath== | ||
Following the accident, the airport was closed for {{frac|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]].<ref>{{cite web|title=Flight EK521: Landing gear issues not confirmed|url=http://gulfnews.com/news/uae/emergencies/flight-ek521-landing-gear-issues-not-confirmed-1.1872893|website=Gulf News|publisher=Al Nasir Publishing|access-date=4 August 2016|date=4 August 2016}}</ref> The closure led Emirates and [[flydubai]] to cancel several of their flights,<ref>{{cite web|author1=Francis|first=Sneha May|date=3 August 2016|title=Flydubai cancels all flights|url=http://www.emirates247.com/flydubai-cancels-all-flights-2016-08-03-1.637841|access-date=4 August 2016|website=Emirates 247|publisher=Dubai Media Incorporated.}}</ref><ref>{{cite web|title=Flight operations resume at Dubai airport|url=http://www.khaleejtimes.com/nation/dubai/emirates-cancels-flights-after-ek521-incident|website=Khaleej Times|access-date=4 August 2016|date=3 August 2016}}</ref> and also affected 23,000 passengers at the airport.<ref name=Gulfnews1 /> Dubai International Airport resumed operations at 18:30 local time,<ref>{{cite web|author=Clarke|first=Kelly|last2=Butalia|first2=Nivriti|date=4 August 2016|title=Emirates incident: Guess what costs $1 million a minute?|url=http://khaleejtimes.com/20160803/8770/no-title|access-date=4 August 2016|website=Khaleej Times}}</ref><ref>{{cite web|author1=Francis|first=Sneha May|last2=Rai|first2=Bindu|date=3 August 2016|title=DXB departures, arrivals resume|url=http://www.emirates247.com/dxb-departures-arrivals-resume-2016-08-03-1.637832|access-date=4 August 2016|website=Emirates 247|publisher=Dubai Media Incorporated}}</ref> at restricted capacity, utilizing only one runway and maximizing the use of the runways at Al Maktoum International Airport.<ref name=Gulfnews1>{{cite web|title=Dubai airport day 2: Flight cancellation and warning of delays|url=http://gulfnews.com/news/uae/emergencies/dubai-airport-day-2-flight-cancellation-and-warning-of-delays-1.1873423|website=Gulf News|publisher=Al Nasir Publishing|access-date=4 August 2016|date=4 August 2016}}</ref> Arriving aircraft were prioritized over departure flights.<ref name= thenational1 /> The damaged runway was repaired and reopened at 17:45 local time on 4 August,<ref name="thenational1">{{cite web|author1=Hanif|first=Nadeem|date=4 August 2016|title=Flight disruptions expected at Dubai airport for 48 hours following crash landing|url=http://www.thenational.ae/uae/transport/flight-disruptions-expected-at-dubai-airport-for-48-hours-following-crash-landing|url-status=dead|archive-url=https://archive. | Following the accident, the airport was closed for {{frac|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]].<ref>{{cite web|title=Flight EK521: Landing gear issues not confirmed|url=http://gulfnews.com/news/uae/emergencies/flight-ek521-landing-gear-issues-not-confirmed-1.1872893|website=Gulf News|publisher=Al Nasir Publishing|access-date=4 August 2016|date=4 August 2016}}</ref> The closure led Emirates and [[flydubai]] to cancel several of their flights,<ref>{{cite web|author1=Francis|first=Sneha May|date=3 August 2016|title=Flydubai cancels all flights|url=http://www.emirates247.com/flydubai-cancels-all-flights-2016-08-03-1.637841|access-date=4 August 2016|website=Emirates 247|publisher=Dubai Media Incorporated.}}</ref><ref>{{cite web|title=Flight operations resume at Dubai airport|url=http://www.khaleejtimes.com/nation/dubai/emirates-cancels-flights-after-ek521-incident|website=Khaleej Times|access-date=4 August 2016|date=3 August 2016}}</ref> and also affected 23,000 passengers at the airport.<ref name=Gulfnews1 /> Dubai International Airport resumed operations at 18:30 local time,<ref>{{cite web|author=Clarke|first=Kelly|last2=Butalia|first2=Nivriti|date=4 August 2016|title=Emirates incident: Guess what costs $1 million a minute?|url=http://khaleejtimes.com/20160803/8770/no-title|access-date=4 August 2016|website=Khaleej Times}}</ref><ref>{{cite web|author1=Francis|first=Sneha May|last2=Rai|first2=Bindu|date=3 August 2016|title=DXB departures, arrivals resume|url=http://www.emirates247.com/dxb-departures-arrivals-resume-2016-08-03-1.637832|access-date=4 August 2016|website=Emirates 247|publisher=Dubai Media Incorporated}}</ref> at restricted capacity, utilizing only one runway and maximizing the use of the runways at Al Maktoum International Airport.<ref name=Gulfnews1>{{cite web|title=Dubai airport day 2: Flight cancellation and warning of delays|url=http://gulfnews.com/news/uae/emergencies/dubai-airport-day-2-flight-cancellation-and-warning-of-delays-1.1873423|website=Gulf News|publisher=Al Nasir Publishing|access-date=4 August 2016|date=4 August 2016}}</ref> Arriving aircraft were prioritized over departure flights.<ref name= thenational1 /> The damaged runway was repaired and reopened at 17:45 local time on 4 August,<ref name="thenational1">{{cite web|author1=Hanif|first=Nadeem|date=4 August 2016|title=Flight disruptions expected at Dubai airport for 48 hours following crash landing|url=http://www.thenational.ae/uae/transport/flight-disruptions-expected-at-dubai-airport-for-48-hours-following-crash-landing|url-status=dead|archive-url=https://archive.today/20160804151532/http://www.thenational.ae/uae/transport/flight-disruptions-expected-at-dubai-airport-for-48-hours-following-crash-landing|archive-date=4 August 2016|access-date=4 August 2016|website=The National|publisher=Abu Dhabi Media}}</ref><ref>{{cite web|author1=Kedem|first=Shoshana|date=4 August 2016|title=Dubai International Airport reopens runway after fire on Emirates flight|url=http://7days.ae/dubai-international-airport-reopens-runway-fire-emirates-flight/90476|url-status=dead|archive-url=https://web.archive.org/web/20160806231558/http://7days.ae/dubai-international-airport-reopens-runway-fire-emirates-flight/90476|archive-date=6 August 2016|access-date=4 August 2016|website=7Days|publisher=Catchpole Communications FZ-LLC}}</ref><ref>{{cite web|author1=Nagraj|first=Aarti|date=4 August 2016|title=Dubai airport on 'recovery mode' for next 48 hours|url=http://gulfbusiness.com/dubai-airport-on-recovery-mode-for-next-48-hours/|access-date=4 August 2016|website=Gulf Business|publisher=Motivate Publishing}}</ref> and the airport resumed normal operations on 6 August, 72 hours after the accident.<ref>{{cite web|author1=Cornwell|first=Alexander|title=Dubai International returns to full capacity after Emirates fire|url=http://gulfnews.com/business/aviation/dubai-international-returns-to-full-capacity-after-emirates-fire-1.1874552|access-date=6 August 2016|website=Gulf News|publisher=AL Nasir Publishing}}</ref><ref>{{cite web|author1=Sebugwaawo|first=Ismail|date=6 August 2016|title=Dubai airport flights 'back to normal' after Emirates accident|url=http://7days.ae/dubai-airport-flights-back-normal-emirates-accident/90503|url-status=dead|archive-url=https://web.archive.org/web/20160806231605/http://7days.ae/dubai-airport-flights-back-normal-emirates-accident/90503|archive-date=6 August 2016|access-date=6 August 2016|website=7Days|publisher=Catchpole Communications FZ-LLC}}</ref> | ||
On 11 August, eight days after the crash, Emirates provided US$7000 in compensation for each of the 282 passengers.<ref>{{cite news|last=Saseendran |first=Sajila |url=http://gulfnews.com/news/uae/emergencies/ek521-passengers-touched-by-emirates-compensation-announcement-1.1877723 |title=EK521 passengers 'touched' by Emirates compensation announcement |website=Gulf News |publisher=Al Nisr Publishing |date=11 August 2016 |access-date=12 August 2016}}</ref> | On 11 August, eight days after the crash, Emirates provided US$7000 in compensation for each of the 282 passengers.<ref>{{cite news|last=Saseendran |first=Sajila |url=http://gulfnews.com/news/uae/emergencies/ek521-passengers-touched-by-emirates-compensation-announcement-1.1877723 |title=EK521 passengers 'touched' by Emirates compensation announcement |website=Gulf News |publisher=Al Nisr Publishing |date=11 August 2016 |access-date=12 August 2016}}</ref> | ||
| Line 132: | Line 130: | ||
{{reflist|group=note}} | {{reflist|group=note}} | ||
==See | ==See also== | ||
*[[China Airlines Flight 140]] and [[Atlas Air Flight 3591]], other flights that crashed in a go around due to pilot errors. | *[[China Airlines Flight 140]] and [[Atlas Air Flight 3591]], other flights that crashed in a go around due to pilot errors. | ||