Flydubai Flight 981: Difference between revisions

Coordinates: 47°15′30″N 039°49′6″E / 47.25833°N 39.81833°E / 47.25833; 39.81833
From Wikipedia, the free encyclopedia
Content deleted Content added
Agastya (talk | contribs)
Original research: no mention of similarity between these two crashes and Flight 981 in the cited sources
Line 206: Line 206:


Five days after the crash, on 24 March, the [[Crown Prince]] of Abu Dhabi [[Mohammed bin Zayed Al Nahyan]] went to Moscow to discuss the course of the crash investigation with Russian President [[Vladimir Putin]].<ref>{{cite news |title=Putin, Abu Dhabi prince to discuss investigation of FlyDubai aircraft in south Russia |url=http://tass.ru/en/politics/864893 |agency=[[Russian News Agency TASS|TASS]] |date=24 March 2016 |accessdate=25 March 2016}}</ref>
Five days after the crash, on 24 March, the [[Crown Prince]] of Abu Dhabi [[Mohammed bin Zayed Al Nahyan]] went to Moscow to discuss the course of the crash investigation with Russian President [[Vladimir Putin]].<ref>{{cite news |title=Putin, Abu Dhabi prince to discuss investigation of FlyDubai aircraft in south Russia |url=http://tass.ru/en/politics/864893 |agency=[[Russian News Agency TASS|TASS]] |date=24 March 2016 |accessdate=25 March 2016}}</ref>

Aviation experts in Russia pointed out multiple similarities between Flight 981 and [[Tatarstan Airlines Flight 363]].<ref>{{cite news |first=Olga |last=Bozhieva |date=22 March 2016 |title=Катастрофа Boeing: эксперты оценили версию заклинивания руля высоты |url=http://www.mk.ru/incident/2016/03/22/katastrofa-boeing-eksperty-ocenili-versiyu-zaklinivaniya-rulya-vysoty.html |newspaper=[[Moskovskij Komsomolets]] |access-date=28 March 2016 |language=ru}}</ref> In both cases, a [[Boeing 737]] impacted the airfield at a high vertical speed while attempting a go-around. The Flight 363 investigation, conducted by the [[Interstate Aviation Committee]], ruled that the 2013 accident was the result of pilot error; one dissenting commission member, a [[Federal Air Transport Agency|Rosaviatsiya]] representative, filed an alternative opinion report, claiming the commission ignored a possible mechanical malfunction of the Boeing 737's [[Elevator (aeronautics)|elevator]] controls.<ref>{{cite web |first=Nikolay |last=Studenikin |url=http://mak-iac.org/upload/iblock/6e0/Особое%20мнение.PDF |title=Особое мнение представителя Росавиации |trans-title=Alternative opinion of the Rosaviatsiya representative |accessdate=27 March 2016 |publisher=[[Interstate Aviation Committee]] |language=ru |format=pdf}}</ref>


On 28 March, Artyom Kiryanov, a [[Civic Chamber of the Russian Federation|Russian Civic Chamber]] member, called for Russia's [[Federal Air Transport Agency]] and the [[Interstate Aviation Committee|IAC]] to suspend the flying certificates of all Russian-owned and -operated Boeing 737 [[Boeing 737 Classic|Classics]] and [[Boeing 737 Next Generation|Next Generation]] series, until the end of the Flight 981 investigation – citing concerns about the elevator controls in all 737s.<ref>{{cite news |first=Elena |last=Loria |url=http://izvestia.ru/news/607561 |title=Для Boeing 737 могут закрыть российское небо |trans-title=Russian sky could be closed for Boeing 737 |work=[[Izvestia]] |date=28 March 2016 |accessdate=31 March 2016 |language=ru}}</ref> After this news reached the U.S., the [[Boeing]] company's stock went down 0.81% on the [[New York Stock Exchange]].<ref>{{cite news |first=Robin |last=Reyes |url=http://sonoranweeklyreview.com/russian-government-official-seeking-to-suspend-operations-of-boeing-737s-in-wake-of-flydubai-crash-nyseba/ |title=Russian Government Official Seeking To Suspend Operations of Boeing 737s in Wake of Flydubai Crash (NYSE:BA) |work=Sonoran Weekly Review |location=[[Belize]] |date=29 March 2016 |accessdate=31 March 2016}}</ref>
On 28 March, Artyom Kiryanov, a [[Civic Chamber of the Russian Federation|Russian Civic Chamber]] member, called for Russia's [[Federal Air Transport Agency]] and the [[Interstate Aviation Committee|IAC]] to suspend the flying certificates of all Russian-owned and -operated Boeing 737 [[Boeing 737 Classic|Classics]] and [[Boeing 737 Next Generation|Next Generation]] series, until the end of the Flight 981 investigation – citing concerns about the elevator controls in all 737s.<ref>{{cite news |first=Elena |last=Loria |url=http://izvestia.ru/news/607561 |title=Для Boeing 737 могут закрыть российское небо |trans-title=Russian sky could be closed for Boeing 737 |work=[[Izvestia]] |date=28 March 2016 |accessdate=31 March 2016 |language=ru}}</ref> After this news reached the U.S., the [[Boeing]] company's stock went down 0.81% on the [[New York Stock Exchange]].<ref>{{cite news |first=Robin |last=Reyes |url=http://sonoranweeklyreview.com/russian-government-official-seeking-to-suspend-operations-of-boeing-737s-in-wake-of-flydubai-crash-nyseba/ |title=Russian Government Official Seeking To Suspend Operations of Boeing 737s in Wake of Flydubai Crash (NYSE:BA) |work=Sonoran Weekly Review |location=[[Belize]] |date=29 March 2016 |accessdate=31 March 2016}}</ref>

==Similar incidents==
There have been many similar incidents to this crash, since the intoduction of high thrust to weight ratio jet powered aircraft, military and civilian. An instance from 1983 saw an apparently fully serviceable [[English Electric Canberra T.17]] fly into the ocean, shortly after take-off into low cloud, at [[RAF Gibraltar]] on 03 August 1983. The pilot was disorientated due to [[Sensory illusions in aviation|somotogravic effects]] on his balance system, causing the pilot to perceive the aircraft climbing hard, when the aircraft accelerated rapidly in only a very gentle climb. The Canberra pilot pushed hard, exacerbating the somotogravic effect, until the aircraft flew into the ocean in a steep dive.<ref name="asncan">{{cite web|title=ASN Wikibase Occurrence # 58798|url=http://aviation-safety.net/wikibase/wiki.php?id=58798|website=viation-safety.net|accessdate=31 March 2016}}</ref><ref name="canaccrep">{{cite book|title=Aircraft Accident Involving Royal Air Force Canberra T17 WJ625|date=13 May 1985|publisher=Ministry of Defence|location=London|url=http://www.ukserials.com/pdflosses/maas_19830803_wj625.pdf|accessdate=31 March 2016}}</ref>

Aviation experts in Russia pointed out multiple similarities between Flight 981 and [[Tatarstan Airlines Flight 363]].<ref>{{cite news |first=Olga |last=Bozhieva |date=22 March 2016 |title=Катастрофа Boeing: эксперты оценили версию заклинивания руля высоты |url=http://www.mk.ru/incident/2016/03/22/katastrofa-boeing-eksperty-ocenili-versiyu-zaklinivaniya-rulya-vysoty.html |newspaper=[[Moskovskij Komsomolets]] |access-date=28 March 2016 |language=ru}}</ref> In both cases, a [[Boeing 737]] impacted the airfield at a high vertical speed while attempting a go-around. The Flight 363 investigation, conducted by the [[Interstate Aviation Committee]], ruled that the 2013 accident was the result of pilot error; one dissenting commission member, a [[Federal Air Transport Agency|Rosaviatsiya]] representative, filed an alternative opinion report, claiming the commission ignored a possible mechanical malfunction of the Boeing 737's [[Elevator (aeronautics)|elevator]] controls.<ref>{{cite web |first=Nikolay |last=Studenikin |url=http://mak-iac.org/upload/iblock/6e0/Особое%20мнение.PDF |title=Особое мнение представителя Росавиации |trans-title=Alternative opinion of the Rosaviatsiya representative |accessdate=27 March 2016 |publisher=[[Interstate Aviation Committee]] |language=ru |format=pdf}}</ref>


==Notes==
==Notes==

Revision as of 19:46, 31 March 2016

Flydubai Flight 981
A6-FDN, the aircraft involved in the crash, seen departing from Dubai International Airport in 2011
Accident
Date19 March 2016 (2016-03-19)
SummaryCrashed during aborted landing attempt; under investigation
SiteRostov-on-Don Airport
Rostov-on-Don, Rostov Oblast, Russia
47°15′30″N 039°49′6″E / 47.25833°N 39.81833°E / 47.25833; 39.81833
Aircraft
Aircraft typeBoeing 737-800
OperatorFlydubai
RegistrationA6-FDN
Flight originDubai International Airport
Dubai, United Arab Emirates
DestinationRostov-on-Don Airport
Rostov-on-Don, Russia
Passengers55
Crew7
Fatalities62 (all)
Survivors0
Flydubai Flight 981 is located in Middle East
Dubai International Airport
Dubai International Airport
Rostov-on-Don Airport
Rostov-on-Don Airport
Origin and destination airports

Flydubai Flight 981 (FZ981/FDB981)[a] was a scheduled international passenger flight that crashed during an aborted landing at Rostov-on-Don Airport in Rostov-on-Don, Russia, in the early morning hours of 19 March 2016, resulting in the death of all 55 passengers and seven crew.

The flight, operated by a Boeing 737-800 aircraft, originated from Dubai International Airport in Dubai, the United Arab Emirates. Rostov Airport was experiencing inclement weather at the time Flight 981 approached. Flight 981 aborted its first landing attempt and went into a holding pattern nearby for nearly two hours before making a second landing attempt. After aborting the second landing attempt, the aircraft climbed to 4,000 feet (1,200 m), then descended rapidly and crashed near the threshold of Runway 22.[3][4]

Background

Airline

Flydubai is an Emirati state-owned low-cost carrier, with its hub in Dubai. Its chairman, Sheikh Ahmed bin Saeed Al Maktoum, is also the chairman of Dubai-based Emirates.[5] Flydubai commenced operations in 2009 and rapidly expanded; by late 2015, it flew to 95 destinations, including 11 in Russia. Its entire fleet consists of Boeing 737s. Flydubai launched its Rostov-on-Don service in September 2013 with two scheduled flights per week.[6]

The airline had no previous fatal accidents and had an "excellent safety record".[7] In 2015, Flydubai passed the safety audit of the IATA, and several days before the crash had become an official member of the organisation.[8] In the aftermath of the crash, Flydubai pilots raised concerns about rostering-related fatigue. A pilot told the BBC on a condition of anonymity that staff had insufficient time to rest between shifts. The pilot shared their concern with a senior member of the staff, who replied, "we don't have a fatigue issue at Flydubai". Another employee said it was their belief that, of the 25 of 600 active pilots who resigned from the airline in 2016, most had done so because of "fatigue, rosters and quality of life", and that in the pilots' opinion an accident was inevitable. In response to the allegations, Flydubai told the BBC, "we are unable to disclose confidential information relating to our employees."[9]

Aircraft

The aircraft involved was a five-year-old Boeing 737-8KN,[b] registered as A6-FDN,[10] MSN 40241, powered by two CFM International CFM56 engines.[11] Its first flight was on 21 December 2010, and it was delivered to Flydubai on 24 January 2011.[11] The aircraft had passed a C-grade maintenance check on 21 January 2016.[12]

Flight 981 carried enough fuel for 8.5 hours of flight; it had been flying for six hours prior to the crash.[13]

Flight crew

The captain was 38-year-old Aristos Sokratous, from Cyprus.[14] He had 5,965 hours of total flying time.[15] Sokratous was promoted to captain a year and a half before the crash.[14] At the time of the crash, he had intended to quit the airline after accepting a job from Ryanair, which would allow him to be based with his family in Cyprus.[16] His wife is due to give birth to their first child a few weeks after the crash.[14] According to several Flydubai staff members, Sokratous decided to leave the airline mainly because of fatigue and lifestyle issues.[9]

The first officer, 37-year-old Alejandro Cruz Álava, was Spanish.[17] He had 5,769 hours of flying time.[15] He started flying with Flydubai two years before the crash, having flown for two regional airlines in the Spanish Canary IslandsBinter and Naysa – earlier in his career.[18]

Both pilots had experience in landing at Rostov-on-Don.[19]

Weather

At the time of the crash, visibility at the airport was normal, though it was reduced from 5,000 m (16,000 ft) at 3:22, when the crew decided to attempt a second approach, to 3,500 m (11,500 ft) at 3:39, when they aborted it.[20][21] There were light rain showers, scattered clouds at 1,800 ft (550 m) and broken cumulonimbus clouds at 3,600 ft (1,100 m).[22] The temperature was 6 °C (43 °F).[22]

The crew was warned by ATC about "severe turbulence and moderate wind shear" on final approach.[20][21] The wind speed was 14 m/s (31 mph; 27 kn)*, gusting to 18 m/s (40 mph; 35 kn)*, with the wind direction at 230 degrees, according to the ATC–crew communications published online.[20][21]

Flight

Flight 981 was scheduled to depart from Dubai International Airport at 21:45 Gulf Standard Time (UTC+4) on 18 March 2016 and arrive at Rostov-on-Don Airport at 01:20 Moscow Standard Time (UTC+3) the next day.[23] It departed from Dubai after a 35-minute delay, at 22:20 GST.[24] The return flight from Rostov-on-Don was scheduled to depart at 02:20 MST.[22]

First approach and hold

File:FZ981.png
Flight 981 holding and approach path

After a four-hour flight, at 01:39 MST, Flight 981 began its approach to Rostov-on-Don. The flight crew aborted the approach at 01:42, at an altitude of 1,725 feet (526 m)*, 6.7 kilometres (4.2 mi)* from the runway, because of poor weather conditions.[22] In the previous twenty minutes, two other flights had landed successfully at Rostov-on-Don on their first attempt: S7 Airlines Flight 1159 (at 01:23) and Ural Airlines Flight 2758 (at 01:28).[22][25]

Flight 981 went into a holding pattern near the airport for the next two hours, waiting for the weather to improve.[13][4] It maintained 8,000 feet (2,400 m)* for the first 30 minutes of the hold and then climbed to 15,000 feet (4,600 m)* feet.[13] Soon after Flight 981's first aborted landing, Aeroflot Flight 1166 made three unsuccessful attempts to land at Rostov-on-Don (at 01:54, 02:07 and 02:17), and at 02:20 diverted to nearby Krasnodar Airport, where it landed at 02:59.[22][26]

Second approach and crash

At 03:28, the crew of Flydubai Flight 981 started the second attempt to land on runway 22.[22] According to ATC communications published online, pilots reported to ATC that in case they would need to make another go-around, they would climb to flight level 80 – approximately 8,000 feet (2,400 m).[c][22][21] At 03:36 the aircraft intercepted the runway 22 localizer at 10 nautical miles (19 km)* from the runway.[22] The crew confirmed it to ATC and continued the descent.[20][21]

At 03:40, when the aircraft descended to 480 meters (1,570 ft)* with a speed of 243 km/h[27][4] and was about 5.5 kilometres (3.4 mi) from the runway threshold, the crew decided to abort the landing, due to bad weather conditions.[28] They reported their intention to ATC with "Going around, Sky Dubai[d] 981".[20][21] ATC advised Flight 981 to switch to another air traffic controller ("Sky Dubai 981, contact Rostov Radar on 121.2").[20][21] Flight 981 acknowledged this with "121.2, bye-bye" which was their final transmission.[20][21] The aircraft increased its speed and within 40 seconds climbed to 1,200 meters (3,900 ft)* with a speed of about 343 km/h.[27][4] Starting at 03:40:40 the aircraft's altitude rapidly decreased and in 20 seconds it hit the ground.[28][4]

At 03:42, the ATC of the airport alerted the local emergency services about the crash.[29] The aircraft struck the ground immediately east of the approach end of Runway 22. A CCTV video, uploaded online after the crash, shows an aircraft plunge into the ground in a steep nose-down attitude, followed by an explosion.[30] According to a source from the rescue team, the small radius of the expansion of debris and the small size of the debris parts, points out that the speed of the fall was more than 400 km/h; as even the aircraft's magnesium alloy wheel hubs were shattered.[31] This speed assessment matches the Flightradar24 data.[27] According to the same source, the aircraft struck the ground with a nose-down pitch of about 60 degrees.[31]

Victims

People on board by nationality[17][32]
Nationality Passengers Crew
 Russia 44 1
 Ukraine 8 0
 India 2 0
 Uzbekistan 1 0
 Spain 0 2
 Colombia 0 1
 Cyprus 0 1
 Kyrgyzstan 0 1
 Seychelles 0 1
Total 55 7

All 62 people on board, 55 passengers and 7 crew members, died in the crash.[24] 44 passengers, including four children, were Russian citizens.[33][17] Eight other passengers came from Ukraine, two from India and one from Uzbekistan. 30 of the passengers were tourists on a package tour from Natalie Tours, one of the largest Russian tour operators.[25] Among the passengers were Igor Pakus, chief physician of the Rostov Oblast regional clinic hospital and a member of the Regional Legislative Assembly, and Elvira Belyakova, head of Rostvertol's pension fund.[25]

Investigation

On the day of the crash, an investigative commission was established by the Interstate Aviation Committee to determine the circumstances and causes of the crash.[10] The investigation is led by Russian air accident investigators, and includes representatives of the aviation authorities of the United Arab Emirates (the state of the aircraft's registration and operator), the United States (where the aircraft's designer and manufacturer is headquartered) and France (where the aircraft's engines were designed).[10] The U.S. team consists of air accident investigators from the National Transportation Safety Board (NTSB), experts from Boeing and representatives of the Federal Aviation Administration (FAA).[34]

The Russian Investigative Committee opened a criminal investigation into any possible safety violations leading to the crash,[35] and allocated more than 50 investigators to work on the case.[36] In a statement, it listed "crew error, technical failure, adverse weather conditions and other factors" as possible reasons for the crash.[36] Terrorism was ruled out as a possibility[12] and no traces of explosives were found.[37]

Progress

On 20 March, air crash investigators completed a survey of the wreckage.[38] Russian and Emirati experts started an analysis of the radar data, flight crew–ATC communications and meteorological information.[38] Both flight recorders were recovered from the crash site and delivered to the Interstate Aviation Committee in Moscow.[10]

On 20 and 21 March, Russian investigators, together with their colleagues from the United Arab Emirates (UAE) and France, extracted the memory modules from their protective casings and downloaded the data from both the flight data recorder (FDR) and the cockpit voice recorder (CVR).[38] Both flight recorders functioned normally during the flight and kept recording data until the time of impact.[38] The CVR casing sustained more severe damage than the FDR, but the quality of both recordings was good.[38] The investigators began to analyse the data and to prepare a transcript of the communication between the crew.[38] They also started synchronising information from the flight recorders, ATC data and meteorological information.[38]

On 21 March investigators in Rostov-on-Don finished collecting debris from the crash site and started reconstructing the fuselage layout in a hangar.[38] Another group of investigators, based in Moscow, together with Emirati investigators, airline representatives and experts from Cyprus and Spain, started to collect and analyse materials on the aircraft's airworthiness, Flight 981's preparation before departure, and the training of its flight crew.[38]

On 23 March, Russian and foreign investigators began to test the Rostov Airport's radio communication equipment, examine ATC communications with other flight crews before the crash and evaluate the actions of the ATC and the airport's meteorological services.[38] Using data retrieved from the flight recorders, as well as information from the aircraft maintenance log and flight documentation, the investigators began to analyse the operation of all Flight 981's aircraft systems, including the flight control system and engines, and also analyse the actions and state of the flight crew during the entire flight.[38]

On 24 March, a representative of the Interstate Aviation Committee said the preliminary findings of the investigation, using flight recorder data, could be released in about two weeks.[39]

On 29 March, investigators began the analysis of the preserved units and elements of the aircraft’s flight control system.[38] The IAC laboratory began the preparation of the data for mathematical modelling of the flight and a audiovisual computer-generated simulation of the plane’s flight path at the time of the accident.[38] The IAC requested that Boeing provide to the investigation some technical documentation for an assessment of the aircraft's system operations and also to provide information about all similar previous incidents with Boeing airframes.[38]

Preliminary findings

On 29 March the IAC announced, that based on the preliminary analysis of information from the flight recorders, no failures of any aircraft systems and components, or engines, have been discovered so far.[38] The aircraft had a valid airworthiness certificate, it underwent all the necessary technical maintenance and was in good order at the time of departure.[38] The IAC informed that Russian, Emirati, U.S. and French experts, using the CVR data, were able to prepare a transcript of more than an hour of crew communications, including those at the final stages of the flight.[38] But the IAC said it does not plan to publish the transcript, citing international and Russian rules of air crash investigation.[38]

Russian TV leak

A trimmable horizontal stabiliser (tailplane) on a Boeing 737-800.
File:Yoke.png
The captain's yoke, with the trim and autopilot disengage switches on the left

On 25 March, Russia-1 reported that the flight recorders revealed the following sequence of events, citing an undisclosed source in the investigation commission.[28][40][41] At 03:40:00, the captain decided to abort the approach due to adverse weather conditions and to climb to flight level 50 (approx. 5,000 feet, 1,500 m).[28] For the next 40 seconds, the aircraft climbed with the autopilot on and a 15-degree nose angle.[28] Before the aircraft could reach the designated flight level, the autopilot was manually disengaged and, shortly after, the aircraft began to descend rapidly.[28]

According to this unverified leak, the instant the autopilot was disconnected, the tailplane moved to the full nose-down position.[28][40][41] The report posited a scenario in which the pilot flying, meaning to take manual control during an encounter with severe turbulence, and intending to turn off the autopilot, inadvertently operated the trim switch instead.[e] The pilots were unaware of the trim condition as they struggled to arrest the descent by pulling the yoke, thus actuating the elevators, which proved ineffective. A pilot is heard on the CVR saying, "don't worry", "don't do that" and "pull up", repeating each phrase three times. Another possible explanation for the loss of control, the report suggested, is an "unprecedented" mechanical failure of the Boeing 737. At 03:41:00, the aircraft crashed.[28]

Reaction

Memorial at the airport

In light of the disaster, the Governor of Rostov Oblast, Vasily Golubev, announced that the government would pay 1 million rubles (about US$ 15,000) to the families of the victims.[12] The day after the crash, 20 March, was designated as a day of mourning in the region.[12]

On 21 March Flydubai opened a Family Assistance Centre for the families of the victims in Rostov-on-Don.[42] It announced a payment of US$ 20,000 per passenger for the "immediate financial needs" of their families.[43] The airline resumed regular flights to Rostov as soon as the airport reopened after the crash, but assigned a different flight number for it.[5][44]

In a press conference, the airline's CEO, Ghaith Al Ghaith, informed Emirati journalists that specialists from the engineering, safety, and security departments of Flydubai are working closely on the ground with the Russian investigators.[45] He asked the media to refrain from speculation and "give the investigators time to do their job and come out with results".[45]

Five days after the crash, on 24 March, the Crown Prince of Abu Dhabi Mohammed bin Zayed Al Nahyan went to Moscow to discuss the course of the crash investigation with Russian President Vladimir Putin.[46]

Aviation experts in Russia pointed out multiple similarities between Flight 981 and Tatarstan Airlines Flight 363.[47] In both cases, a Boeing 737 impacted the airfield at a high vertical speed while attempting a go-around. The Flight 363 investigation, conducted by the Interstate Aviation Committee, ruled that the 2013 accident was the result of pilot error; one dissenting commission member, a Rosaviatsiya representative, filed an alternative opinion report, claiming the commission ignored a possible mechanical malfunction of the Boeing 737's elevator controls.[48]

On 28 March, Artyom Kiryanov, a Russian Civic Chamber member, called for Russia's Federal Air Transport Agency and the IAC to suspend the flying certificates of all Russian-owned and -operated Boeing 737 Classics and Next Generation series, until the end of the Flight 981 investigation – citing concerns about the elevator controls in all 737s.[49] After this news reached the U.S., the Boeing company's stock went down 0.81% on the New York Stock Exchange.[50]

Notes

  1. ^ FZ is the IATA designator and FDB is the ICAO airline designator. These designators may be included in the flight number,[1] eg. FlyDubai Flight FZ981.[2]
  2. ^ The aircraft was a Boeing 737-800 model; Boeing assigns a unique customer code for each company that buys one of its aircraft, which is applied as an infix in the model number at the time the aircraft is built. The code for Flydubai is "KN", hence "737-8KN".
  3. ^ Aircraft altitude is measured by air pressure according to calculated sea level taking into account the actual pressure, which declines as altitude above sea level increases. A flight level is the pressure altitude in hundreds of feet related to standard pressure of 1013,25 hPa at sea level.
  4. ^ Sky Dubai is the airline's assigned call sign.
  5. ^ The stabiliser trim switch is a pair of three-stage spring-loaded switches located on the outer arm of the yoke. Dual operation disconnects the autopilot and moves the tailplane in the desired direction. On release, the switches return to the neutral position (inactive). The autopilot disengage switch is a push button underneath the trim switch. (FCOM)

References

  1. ^ "Airline Codes – IATA Designators". Dauntless Jaunter. Pardeaplex Media. Retrieved 31 March 2016.
  2. ^ Tomkiw, Lydia (20 March 2016). "Flydubai Flight FZ981 Crash Update: Flight Recorders 'Badly Damaged,' Russian Officials Say Could Delay Investigation". International Business Times. Retrieved 31 March 2016.
  3. ^ "Rostov-On-Don Airport in Russia". Sputnik News. 19 March 2016. Retrieved 19 March 2016.
  4. ^ a b c d e "Playback of FlyDubai flight FZ981". Flightradar24. Retrieved 29 March 2016.
  5. ^ a b Cornwell, Alexander (21 March 2016). "Flydubai to resume flights to Rostov-on-Don on Tuesday". Gulf News. Dubai. Retrieved 22 March 2016.
  6. ^ Jain, Shweta (21 March 2016). "Flydubai Russia expansion plans may be affected by crash of flight FZ981". Gulf News. Dubai. Retrieved 23 March 2016.
  7. ^ Baldwin, Derek (19 March 2016). "Flydubai crash surprising as airline has excellent safety record, Dubai-based analyst says". Gulf News. Dubai. Retrieved 19 March 2016.
  8. ^ "Flydubai becomes latest IATA member from MENA". Arab News. Jeddah. 12 March 2016. Retrieved 25 March 2016.
  9. ^ a b Fottrell, Stephen (24 March 2016). "FlyDubai crash pilot 'was due to leave job over fatigue'". BBC World Service. Retrieved 24 March 2016.
  10. ^ a b c d "Boeing 737-800 А6-FDN 19.03.2016". Interstate Aviation Committee. 19 March 2016. Retrieved 19 March 2016.
  11. ^ a b "Boeing 737 Next Gen MSN 40241". Airfleets.net. Retrieved 19 March 2016.
  12. ^ a b c d Chance, Matthew; Cullinane, Susannah; Meilhan, Pierre (19 March 2016). "Flydubai plane crashes in Russia; 62 aboard reported dead". CNN. Retrieved 19 March 2016.
  13. ^ a b c Hradecky, Simon (19 March 2015). "Crash: Flydubai B738 at Rostov on Don on Mar 19th 2016, struck wing onto runway after holding for 2 hours". Aviation Herald. Retrieved 19 March 2016.
  14. ^ a b c "Cyprus Pilot of Crashed FlyDubai Jet Had a New Job Elsewhere". The New York Times. Associated Press. 19 March 2016. Retrieved 19 March 2016.
  15. ^ a b "Flydubai plane crash: airline to give victims' families $20,000 each". Gulf News. Dubai. 19 March 2016. Retrieved 19 March 2016.
  16. ^ Long, Natalie (19 March 2016). "Flydubai plane crash pilot, co-pilot leave behind pregnant wives". Gulf News. Dubai. Retrieved 19 March 2016.
  17. ^ a b c "Updated list of passengers and crew members of flight 981 – Dubai – Rostov-on-Don". Ministry of Emergency Situations. 19 March 2016. Retrieved 19 March 2016.
  18. ^ Long, Natalie (19 March 2016). "Flydubai plane crash: Two Spaniards were from Canary Islands". Gulf News. Dubai. Retrieved 19 March 2016.
  19. ^ Cornwell, Alexander (20 March 2016). "Flydubai chief executive: 'Airport was good enough to land'". Gulf News. Dubai. Retrieved 20 March 2016.
  20. ^ a b c d e f g "Последние переговоры пилотов упавшего «Боинга» с диспетчерами аэропорта Ростова: аудио" [The last communications between the pilots of the crashed Boeing with Rostov ATC: Audio]. DonDay. 19 March 2016. Retrieved 19 March 2016.
  21. ^ a b c d e f g h "Крушение самолета в Ростове-на-Дону" [Aircraft crash in Rostov-on-Don]. Aviation Safety. 19 March 2016. Retrieved 19 March 2016.
  22. ^ a b c d e f g h i "ASN Aircraft accident Boeing 737-8KN A6-FDN Rostov Airport (ROV)". Aviation Safety Network. Retrieved 19 March 2016.
  23. ^ "Flydubai flight FZ 981: Dubai – Rostov". FlightMapper. Retrieved 19 March 2016.
  24. ^ a b "Statement relating to Flydubai FZ981". Flydubai. 19 March 2016. Retrieved 19 March 2016.
  25. ^ a b c "Струйное течение, полупустой самолет. Основные версии причин авиакатастрофы в Ростове-на-Дону" [Jet stream, half-empty aircraft. Main versions of the plane crash in Rostov-on-Don]. Meduza (in Russian). 19 March 2016. Retrieved 19 March 2016.
  26. ^ "Aeroflot flight SU1166". Flightradar24. Retrieved 19 March 2016.
  27. ^ a b c "Крушение «Боинга» Flydubai. Что до сих пор неизвестно" [Crash of Flydubai's Boeing. What is still unknown]. Meduza (in Russian). 20 March 2016. Retrieved 20 March 2016.
  28. ^ a b c d e f g h Kondrashov, Andrey (25 March 2016). "Не волнуйся, тяни: о чем думали пилоты "Боинга" за секунды до крушения" [Don't worry, pull up: what where the thoughts of the Boeing pilots seconds before the crash]. Russia-1 (in Russian). Retrieved 26 March 2016.
  29. ^ "Происшествие с самолетом Боинг в г.Ростове-н/Д" [Incident with Boeing aircraft in Rostov-on-Don] (in Russian). Rostov-on-Don branch of the Ministry of Emergency Situations. 19 March 2016. Retrieved 19 March 2016.
  30. ^ "Plane Crashes in Russia". The New York Times. Reuters. 19 March 2016. Retrieved 19 March 2016.
  31. ^ a b "Источник: Boeing потерпел крушение, пытаясь уйти на третий круг" [Source: Boeing crashed, trying to go around for a third attempt] (in Russian). TASS. 19 March 2016. Retrieved 20 March 2016.
  32. ^ "FZ981 Flight Manifest" (pdf). Flydubai. 22 March 2016. Retrieved 23 March 2016.
  33. ^ "Statement relating to Flydubai flight FZ981". Flydubai. 19 March 2016. Retrieved 19 March 2016.
  34. ^ "US Transport Agency Sending Team to Russia to Assist in Boeing Crash Probe". Sputnik. 19 March 2016. Retrieved 20 March 2016.
  35. ^ Roth, Andrew (19 March 2016). "Dubai passenger jet crashes in Russia, killing 62". The Washington Post. Retrieved 19 March 2016.
  36. ^ a b Nechepurenko, Ivan (19 March 2016). "Wind Given as Possible Cause of Fatal Plane Crash in Russia". The New York Times. Retrieved 19 March 2016.
  37. ^ "Вероятность теракта на борту разбившегося в Ростове самолета практически исключена" (in Russian). Interfax. 19 March 2016. Retrieved 24 March 2016.
  38. ^ a b c d e f g h i j k l m n o p q r "Боинг 737-800 А6-FDN 19.03.2016" [Boeing 737-800 А6-FDN 19.03.2016] (in Russian). Interstate Aviation Committee. 20 March 2016. Retrieved 20 March 2016.
  39. ^ "Данные с самописцев разбившегося в Ростове "Боинга" озвучат в течение двух недель" [The data from the flight recorders of Boeing crashed in Rostov to be revealed in two weeks] (in Russian). Interfax. 24 March 2016. Retrieved 25 March 2016.
  40. ^ a b "'Pull up!': Russian TV airs final words of flydubai jet crash pilots". Agence France-Presse. 26 March 2016. Retrieved 26 March 2016.
  41. ^ a b Nechepurenko, Ivan (26 March 2016). "Possible Pilot Error Is Cited in FlyDubai Crash in Russia". The New York Times. Retrieved 26 March 2016.
  42. ^ "Confirmation of opening of Family Assistance Centre". Flydubai. 21 March 2016. Retrieved 22 March 2016.
  43. ^ "Statement relating to flydubai flight FZ981". Flydubai. 20 March 2016. Retrieved 20 March 2016.
  44. ^ Westall, Sylvia (20 March 2016). "Flydubai Says No Change to Flights After Russia Crash". The New York Times. Reuters. Retrieved 25 March 2016.
  45. ^ a b Rahman, Mujeeb (21 March 2016). "Flydubai rejects rumours, says flight operations normal". AMEinfo. Abu Dhabi. Retrieved 23 March 2016.
  46. ^ "Putin, Abu Dhabi prince to discuss investigation of FlyDubai aircraft in south Russia". TASS. 24 March 2016. Retrieved 25 March 2016.
  47. ^ Bozhieva, Olga (22 March 2016). "Катастрофа Boeing: эксперты оценили версию заклинивания руля высоты". Moskovskij Komsomolets (in Russian). Retrieved 28 March 2016.
  48. ^ Studenikin, Nikolay. "Особое мнение представителя Росавиации" [Alternative opinion of the Rosaviatsiya representative] (pdf) (in Russian). Interstate Aviation Committee. Retrieved 27 March 2016.
  49. ^ Loria, Elena (28 March 2016). "Для Boeing 737 могут закрыть российское небо" [Russian sky could be closed for Boeing 737]. Izvestia (in Russian). Retrieved 31 March 2016.
  50. ^ Reyes, Robin (29 March 2016). "Russian Government Official Seeking To Suspend Operations of Boeing 737s in Wake of Flydubai Crash (NYSE:BA)". Sonoran Weekly Review. Belize. Retrieved 31 March 2016.

External links