FlyDubai flight FZ981

fz981

Update April 7, 2016 –

Source: REX

The data obtained from flight recorders of the FlyDubai Boeing 737 that crashed in Russia during landing on March 19 unveiled a clear picture of what was happening on board the plane.

According to the black boxes, when coming in to land at an angle of 218 degrees, the pilot at first decided to go round again. The pilot informed a flight control officer of wind shear and proceeded to gain altitude, flying from 1,500 meters to the waiting area of 2,500 meters. However, light icing on the fuselage made the pilot-in-commander climb to 4,550 meters.

Twenty-two minutes before the tragedy, the pilot reported weather conditions to flight control officers: “… visibility 5 kilometers, cloud base 630 meters, wind 230 degrees, 13 m/s with gusts of 18 m/s, light pouring rain, mist, strong turbulence, moderate wind shear. ”

Two minutes later, the dispatcher informed the commander of the plane that there was no data on wind shear.

At 03:23 a.m. the crew requested descending but admitted that this attempt to land the aircraft may not be the last one. The dispatcher gave permission to rise again to level 80.

The next minute, the Boeing started descending. At an altitude of 220 meters, the commander took the aircraft for another attempt as his apprehensions were confirmed.

At this point, a fatal mistake was made, but the reason for it remains still unknown. At an altitude of 900 meters, the stabilizer suddenly switched to the dive mode. While the pilot was pulling the wheel to lift the nose and gain altitude, the aircraft was nosediving.

At an altitude of about 1,000 meters, the aircraft tilted to the left side and crashed into the ground.

The clock was showing 3:42.

According to data recorders, the systems of the aircraft were working normally. Thus, only two reasons are left on the list of possible causes of the crash: the work of the longitudinal control system of the Boeing and actions of the crew when coming for a second approach.

The Boeing 737 of FlyDubai airline with 55 passengers and seven crew members aboard crashed on March 19 at the airport of Rostov-on-Don, leaving no survivors.

Pravda.Ru

All Russian planes to be equipped with anti-missile systems

06.04.2016All the state and maybe civil planes will be equipped with defence against man-portable air-defence systems, which are used by terrorists, the Russian Deputy Defence Minister Yuriy Borisov claimed.

According to him, the enterprise will just undertake the creation of defence system against MANPADS. About 100 complexes of such equipment are planned to be produced a year.

Borisov noted that development of the Samara research institute Ekran gave a good account of oneself, and now almost all of the Russian Armed Forces’ helicopters, not only combat but also transport ones, are being equipped with complexes named Vitebsk.

“The complex will be modernized, will operate in a wider frequency range, and at long distances, and secure defence of all the flying vehicles. At the same time, the whole air squad, that transports top officials, has already been equipped with these complexes, the President-S system,” Borisov said.

The Deputy Minister also added that the complex is in great demand abroad. Spanish companies, in particular, wished to purchase the development.

Pravda.Ru

Update March 29, 2016 – Interstate Aviation Committee (IAC) of Russia released a statement that the flight data recorders showed that the aircraft was fully operational when it took off from the airport in Dubai. The data obtained from the cockpit voice recorder (CVR) will not be disclosed to the public. “According to the preliminary analysis of the information obtained from flight recorders to date, no onboard system malfunctions, aircraft components’ defects or power system failures have been found.”  “In accordance with Russian and International rules of aviation accident investigation, the information obtained from the cockpit voice recorder (CVR) is not to be made public. IAC did not and does not intend to disclose this information.” source

A representative of the Interstate Aviation Committee said the preliminary findings of the investigation would be released by 19 April 2016.

28 March, 2016 – 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 . source

Flight FZ981, (FZ981/FDB981) Boeing 737-800 from Dubai crashed in Rostov-on-Do on March 19 2016, 3.50am local time.  Pilots: Captain Aristos Sokratous, 37, from Cyprus, and first officer Alejandro Alava, 37, from Spain.  There were 62 people on board, including 55 passengers and 7 crew members.

FlyDubai was founded 19. March 2008 and suffered its first loss on 8th anniversary.

fr3

source  link no longer active

Cd4XtpFXIAQviiU Cd5ZIziW8AAKrx5

source: Flightradar24

Government of Dubai Media Office youtube.com/watch?v=h_IIC3mb0Wo – 43min  bit.ly/1RaHtJf
Saturday, March 19, 2016 – flydubai Chief Executive Officer Ghaith Al Ghaith held a press conference today at the Government of Dubai Media Office Dubai to brief the media on the crash of its flight from Dubai to Rostov-on-Don in southwestern Russia early Saturday morning.

A6-FDN Boeing 737-8KN(WL)

Config: C12Y162

Engines: 2x CFMICFM56-7B27

Delivered: 19. Jan 2011

Remarks: configured “Y189, leased from GECAS, Ferried PAEGLADXB 24. – 25. Jan 2011 on delivery, re-configured “C12Y162” Sep 2013

Airline founded 19. Mar 2008, started operations 01. Jun 2009.

planespotters.net/airframe/Boeing/737/40241/A6-FDN-flydubai

flightradar24.com/data/flights/fz981/#922b3bd

The aircraft had passed a C-grade maintenance check on 21 January 2016.

Interstate Aviation Committee

MAK /IAC/ is an executive body coordinating the use and management of airspace and the sphere of civil aviation of member states.

The Interstate Aviation Committee (IAC / MAK), a civil aviation body for ex-Soviet states, was formed on the basis of the intergovernmental Agreement on Civil Aviation and Air Space Use (the Agreement), signed on 30.12.91. As of 2008 the participants of the Agreement are republics Azerbaijan, Armenia, Belarus, Georgia, Kazakhstan, Kyrgyzstan, Moldova, Russian Federation, Tadjikistan, Turkmenistan, Uzbekistan and Ukraine.

aviation-safety.net/database/record.php?id=20160319-0

The ASN database involving aircraft fitted with the CFMI CFM56 engine includes AirAsia and Germanwings.

198 occurrences in the ASN safety database

19-MAR-2016 Boeing 737-8KN A6-FDN flydubai 62 Rostov Airpo…
24-MAR-2015 Airbus A320-211 D-AIPX Germanwings 150 Prads-Haute-…
28-DEC-2014 Airbus A320-216 PK-AXC Indonesia AirAsia 162 Java Sea

CFM56-5C
CFM56-5A

CFM56-3

CFM56-2

Accident description
Last updated: 20 March 2016
Developing story –
the information presented here is preliminary and may change rapidly.
Status: Preliminary
Date: Saturday 19 March 2016
Time: 03:41
Type: Silhouette image of generic B738 model; specific model in this crash may look slightly different
Boeing 737-8KN (WL)
Operator: flydubai
Registration: A6-FDN
C/n / msn: 40241/3517
First flight: 2010-12-21 (5 years 3 months)
Engines: 2 CFMI CFM56-7B27
Crew: Fatalities: 7 / Occupants: 7
Passengers: Fatalities: 55 / Occupants: 55
Total: Fatalities: 62 / Occupants: 62
Airplane damage: Destroyed
Airplane fate: Written off (damaged beyond repair)
Location: Rostov Airport (ROV) (Russia)
Phase: Approach (APR)
Nature: International Scheduled Passenger
Departure airport: Dubai Airport (DXB/OMDB), United Arab Emirates
Destination airport: Rostov Airport (ROV/URRR), Russia
Flightnumber: FZ981

Narrative:
A Boeing 737-800 aircraft, operated by FlyDubai as Flight FZ981 from Dubai, impacted airport terrain during a second approach attempt in bad weather to Rostov-On-Don Airport in Southern Russia. The airplane was destroyed and the 55 passengers and 7 crew fatally injured.
Flight 981 departed Dubai at 18:37 hours UTC on March 18. At 22:43 UTC (01:43 local time) the aircraft aborted the approach to runway 22 at Rostov Airport and began circling the area until it entered a holding pattern at 23:25 UTC.
The flight left the holding pattern at 00:28 UTC (03:28 LT) and descended towards Rostov for another attempted approach to runway 22. The aircraft crashed on airport terrain during this attempt. ADS-B data recorded by Flightradar24 show the aircraft descending to an altitude of 1550 feet when it began to climb again at 3 NM (5,6 km) short of the runway. It reached about 3975 feet until the airplane entered a steep descent before impacting airport terrain.

Timeline of events (times in UTC):
17:45 FZ981 scheduled time of departure
18:22 FZ981 pushed back from Stand E18 at Dubai Airport
18:37 FZ981 commences takeoff from runway 30R at Dubai Airport
19:14 FZ981 reaches cruising altitude of FL360
22:16 FZ981 commences descent from FL360
22:20 FZ981 scheduled time of arrival
22:23 S71159 (an Airbus A319 from Moscow-Domodedovo) lands after it’s first approach to runway 22
22:28 U62758 (an Airbus A320 from Khudzhand) lands after it’s first approach to runway 22
22:39 FZ981 commences final approach to runway 22 at Rostov Airport
22:42 FZ981 aborts first approach at 1725 ft, 6.7 km short of the runway
22:49 FZ981 reaches 8000 feet and heads towards the northeast of the airport
22:54 SU1166 (a Sukhoi Superjet 100-95B from Moscow-Sheremetyevo) aborts the first approach to runway 22
23:07 SU1166 aborts the second approach to runway 22
23:17 SU1166 aborts the third approach to runway 22
23:20 SU1166 diverts towards Krasnodar
23:20 FZ982 scheduled time of return flight back to Dubai
23:27 FZ981 enters holding pattern at 15000 feet to the southeast of the airport
00:28 FZ981 leaves the holding pattern and descends for a second approach
00:36 FZ981 intercepts the runway 22 localizer at 10 NM from the runway
00:40 FZ981 aborts second approach at 1550 ft, 5.6 km short of the runway
00:41 FZ981 impacts airport terrain after a steep descent from 3975 feet

Sources:

» MAK

METAR Weather report:

00:00 UTC / 03:00 local time:
URRR 190000Z 24010MPS 8000 -SHRA SCT017 BKN040CB OVC100 06/03 Q0998 WS R22 R22/290046 TEMPO 25015G20MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE741/0988
00:30 UTC / 03:30 local time:
URRR 190030Z 24012G19MPS 6000 -SHRA SCT018 BKN036CB OVC100 06/04 Q0998 R22/290046 TEMPO 25017G25MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE741/0988
Wind 240 degrees, 12 m/s gusting to 19 m/s; Visibility 6000m; light rain showers; Scattered couds at 1800 feet, broken Cumulonimbus clouds at 3600 feet, overcast at 10000 feet; Temperature 6°C; Dew point 4°C

22:30 UTC / 01:30 local time:
URRR 182230Z 25011G17MPS 4200 -SHRA SCT016 BKN033CB OVC100 06/03 Q1000 R22/290046 TEMPO 25015G20MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE742/0990
Wind 250 degrees, 11 m/s gusting to 17 m/s; Visibility 4200m; light rain showers; Scattered couds at 1600 feet, broken Cumulonimbus clouds at 3300 feet, overcast at 10000 feet; Temperature 6°C; Dew point 3°C

23:00 UTC / 02:00 local time:
URRR 182300Z 24009G15MPS 4500 -SHRA SCT017 BKN036CB OVC100 05/03 Q0999 WS R22 R22/290046 TEMPO 25015G20MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE742/0989

23:30 UTC / 02:30 local time:
URRR 182330Z 24012MPS 3900 -SHRA SCT019 BKN036CB OVC100 06/03 Q0999 WS R22 R22/290046 TEMPO 25015G20MPS 1000 SHRA BR SCT003 BKN020CB RMK QFE741/0989

source: aviation-safety.net/database/engine/CF-CFM56
CFMI CFM56
Last updated: 16 January 2014
General details:
Model: CFMI CFM56
Country: France
United States of America
Developed in: 1974
Type: Turbofan

List of aircraft accidents in the ASN database involving aircraft fitted with the CFMI CFM56 engine.

Aircraft types in the ASN database fitted with the CFMI CFM56 engine:
  • Airbus A319
  • Airbus A320
  • Airbus A321
  • Airbus A340
  • Boeing 707
  • Boeing 737-300
  • Boeing 737-400
  • Boeing 737-500
  • Boeing 737-600
  • Boeing 737-700
  • Boeing 737-800
  • Boeing 737-900
  • Boeing C-135
  • McDonnell Douglas DC-8
Specific engine models within the CFMI CFM56 series in the ASN database:
  • CFMI CFM56-2A-2
  • CFMI CFM56-2C
  • CFMI CFM56-2C1
  • CFMI CFM56-3B1
  • CFMI CFM56-3B2
  • CFMI CFM56-3C1
  • CFMI CFM56-5A1
  • CFMI CFM56-5A1/F
  • CFMI CFM56-5A3
  • CFMI CFM56-5A5
  • CFMI CFM56-5B3/P
  • CFMI CFM56-5B4
  • CFMI CFM56-5B4/3
  • CFMI CFM56-5B4/P
  • CFMI CFM56-5B5/3
  • CFMI CFM56-5B5/P
  • CFMI CFM56-5B6/3
  • CFMI CFM56-5B6/P
  • CFMI CFM56-5C2
  • CFMI CFM56-5C3
  • CFMI CFM56-5C4
  • CFMI CFM56-7B20
  • CFMI CFM56-7B22
  • CFMI CFM56-7B24
  • CFMI CFM56-7B24E
  • CFMI CFM56-7B26
  • CFMI CFM56-7B26/3
  • CFMI CFM56-7B26E
  • CFMI CFM56-7B27
  • CFMI CFM56-7B27/3
  • CFMI CFM56-7B27E
  • CFMI F108-CF-100

aviation-safety.net/database/record.php?id=20160319-0 featured the following YouTube videos:

RT  youtube.com/watch?v=nlqlRZmz5QU&feature=youtu.be 1,753,191 subscribers 1,678,275,211 views Joined Mar 28, 2007

MrOutofcontrolvideos  youtu.be/57v4_U-N15c 2,279 subscribers 4,832,437 views Joined Dec 18, 2012 – plus.google.com/+MrOutofcontrolvideos/posts 9 followers|82,495 views

Related Mar 29th 2016, flaps problem: A Flydubai Boeing 737-800, registration A6-FDZ (up until today, this aircraft has been seen in zero other incidents while Flydubai is listed in totally 7 incidents, accidents or reports so far) performing flight FZ-251 from Dubai (United Arab Emirates) to Mashhad (Iran), was on approach to Mashhad when the flaps could not be extended beyond 5 degrees. The crew entered a hold to work the related checklists, extended the flaps further using the alternate flaps extension and performed a safe landing on Mashhad’s runway 31R at a higher than normal speed (about 160 knots over ground). source

shrt lnk: http://wp.me/p5eLCS-gQ

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s