Crash of a Tupolev TU-154B-2 off Sochi: 92 killed

Date & Time: Dec 25, 2016 at 0525 LT
Type of aircraft:
Operator:
Registration:
RA-85572
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Moscow - Sochi - Hmeimim
MSN:
83A-572
YOM:
1983
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
84
Pax fatalities:
Other fatalities:
Total fatalities:
92
Aircraft flight hours:
6689
Circumstances:
The airplane departed Moscow-Chkhalovksy AFB at 0138LT on a flight to Hmeimin AFB located near Latakia, Syria, carrying 84 passengers and 8 crew members. At 0343LT, the aircraft landed at Sochi-Adler Airport to refuel. At 0525LT, the takeoff was initiated from runway 24. After a course of 34 seconds, the pilot-in-command initiated the rotation at a speed of 300 km/h. Shortly after liftoff, the undercarriage were raised and the pilot continued to climb with a nose-up angle of 15°. About 53 seconds after takeoff, at an altitude of 157 metres, the captain asked the flaps to be retracted while the aircraft was climbing to a height of 231 metres with a speed of 360 km/h. Following erroneous movements on the control column, the aircraft nosed down and its speed increased to 373 km/h when the GPWS alarm sounded in the cockpit. With a rate of descent of 30 metres per second, the aircraft reached the speed of 540 km/h, rolled to the left to an angle of 50° and eventually crashed in the sea some 1,270 metres offshore, at 05:25 and 49 seconds. The flight took 73 seconds between liftoff and impact with water. The wreckage was found 2,760 metres from the end of runway 24 and 340 metres to the left of its extended centerline, at a depth of 30 metres. The aircraft disintegrated on impact and all 92 occupants were killed, among them 64 members of the Alexandrov Choir of the Red Army, their Artistic Director, nine journalists, seven officers from the Ministry of Defence, two senior officials and one representative of a public Company who were traveling to Hmeimim Air Base to commemorate the New Year's Eve celebrations with Russian soldiers based in Syria.
Probable cause:
The accident was the consequence of a loss of control that occurred during initial climb by night over the sea after the pilot-in-command suffered a spatial disorientation due to an excessive neuropsychic stress combined with fatigue.

Crash of an Ilyushin II-18V near Tiksi

Date & Time: Dec 19, 2016 at 0445 LT
Type of aircraft:
Operator:
Registration:
RF-91821
Flight Type:
Survivors:
Yes
Schedule:
Yekaterinburg - Kansk - Tiksi
MSN:
185 0080 03
YOM:
1965
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
31
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine airplane departed Yekaterinburg on a flight to Tiksi with an intermediate stop in Kansk, carrying 32 passengers and seven crew members. During a polar night approach, the aircraft deviated from the approach pattern and dropped below the glide path relying on a flawed approach scheme. This caused the belly to touch the summit of a snow-covered hill (392 metres high) located 31 km northwest of Tiksi Airport. The aircraft bounced and touched the ground again on the rear slope of the hill some 1,250 metres further on. The fuselage broke into three parts. There was no fire. All 7 crew and 31 passengers were injured, 16 seriously.

Crash of an Antonov AN-26-100 in Belaya Gora

Date & Time: Oct 11, 2016 at 1638 LT
Type of aircraft:
Operator:
Registration:
RA-26660
Survivors:
Yes
Schedule:
Yakutsk - Belaya Gora
MSN:
8008
YOM:
1979
Flight number:
PI203
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11439
Captain / Total hours on type:
2697.00
Copilot / Total flying hours:
11142
Copilot / Total hours on type:
122
Aircraft flight hours:
34490
Aircraft flight cycles:
16367
Circumstances:
On final approach to Belaya Gora Airport, the aircraft was too low and hit the ground. On impact, the right main gear and the nose gear collapsed. The aircraft slid for several yards before coming to rest in a snow covered field about 400 meters short of runway threshold and 300 meters to the left of the approach path. The propeller on the right engine was torn off and it appears that the fuselage was bent as well. All 33 occupants were evacuated safely. At the time of the accident, weather conditions were marginal with limited visibility caused by snow falls. It was reported the visibility was about 2,5 km at the time of the accident while the crew needed at least 4 km on an NDB approach.
Probable cause:
The accident was caused by the combination of the following factors:
- Absence of standard operating procedures issued by the operator of how to conduct NDB approaches,
- Violation of procedures by tower who only transmitted information about snow fall and recommended to perform a low pass over the runway but did not transmit the actual visibility was 1900 meters below required minimum
- Absence of information that the visibility was below required minimum, the last transmission indicated minimum visibility was present,
- Presence of numerous landmarks (abandoned ships, ship cranes, fuel transshipment complex, ...) covered by snow within 700-1000 meters from the unpaved runway which could be taken as runway markers by flight crew,
- Presence of a number of "bald spots" due to the transitional period of year where the underlying surface became visible making it difficult to visualize and recognize the unpaved runway covered with snow (it was the first flight into Belaya Gora for the crew in the winter season, they had operated into the aerodrome only in summer so far),
- Insufficient use of the available nav aid on final approach which led to lack of proper control of the aircraft position relative to the glide path,
- Lack of possibility for tower to watch the aircraft performing the NDB approach from his work place.
Final Report:

Crash of a PZL-Mielec AN-2R near Krapivninsky: 3 killed

Date & Time: Jul 31, 2016 at 1335 LT
Type of aircraft:
Operator:
Registration:
RA-54790
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Berdsk – Mansky
MSN:
1G183-54
YOM:
1979
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
5787
Captain / Total hours on type:
1342.00
Aircraft flight hours:
8853
Circumstances:
The single engine airplane was completing a positioning flight from Berdsk to Mansky where insecticides should be pulverized on wooded area. On board were a pilot, a mechanic and a passenger. Following a night in Berdsk, the airplane took off at 1201LT for the last leg to Mansky. En route, weather conditions deteriorated and the visibility was poor. Too low, the aircraft impacted trees and crashed in a wooded area located on the slope of Mt Abatova (747 metres high) located 40 km east of Krapivninsky. The airplane was destroyed by impact forces and a post crash fire. The wreckage was found the following day at an altitude of 541 metres. All three occupants were killed.
Crew:
R. Rodzhapov, pilot,
I. Valiullin, mechanic.
Passenger:
Yuri Pakhomov, maybe acting as a copilot on this flight, despite he was not licensed anymore.
Probable cause:
Controlled flight into terrain following the decision of the pilot to fly under VFR mode in IMC conditions in an uncontrolled area. Poor flight planning and flying without a copilot were considered as contributing factors.
Final Report:

Crash of an Ilyushin II-76TD near Uyan: 10 killed

Date & Time: Jul 1, 2016 at 1113 LT
Type of aircraft:
Operator:
Registration:
RA-76840
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Irkutsk - Irkutsk
MSN:
1033417553
YOM:
1994
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
11209
Captain / Total hours on type:
8711.00
Copilot / Total flying hours:
5584
Copilot / Total hours on type:
5124
Aircraft flight hours:
13000
Aircraft flight cycles:
4500
Circumstances:
The aircraft departed Irkutsk Airport at 1019LT on a fire fighting mission in the region of Bayanday. As the crew was approaching the area to be treated, the aircraft impacted trees and crashed in a wooded area, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire. The wreckage was found two days later and all 10 crew members were killed.
Crew:
L.S. Owl, pilot,
A. A. Lebedev, copilot,
G. L. Petrov, navigator,
V. N. Kuznetsov, flight engineer,
I. E. Murahin, radio operator,
S. A. Makarov, flight operator,
S. A. Souslov, flight operator,
M. M. Khadayev, flight operator,
V. G. Jdanov, operator,
A. M. Mashnin, operator.

Crash of a PZL-Mielec AN-2R in Novopokrovskoye: 2 killed

Date & Time: Jun 30, 2016 at 0604 LT
Type of aircraft:
Operator:
Registration:
RA-33462
Flight Phase:
Survivors:
No
Schedule:
Novopokrovskoye - Novopokrovskoye
MSN:
1G228-12
YOM:
1988
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4398
Captain / Total hours on type:
2140.00
Aircraft flight hours:
3370
Circumstances:
The airplane was engaged in a crop spraying mission, carrying a load of herbicides, one passenger and one pilot. In the early morning, while completing a seventh low pass, at a height of about 20-40 metres, the pilot initiated a left turn when the aircraft descended to the ground and crashed at a speed of 140 km/h in an open field, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire and both occupants were killed.
Probable cause:
Fatal accident with Аn-2 RA-33462 agricultural aircraft occurred during aerial works on crop-dusting and was caused most probably by the piloting error consisting in unintentional descent when performing a turn for the next crop-dusting round which resulted in the aircraft controlled flight into terrain.
Most probably, the following factors contributed to the accident:
- The PIC not trained for crop-dusting flight without first officer,
- The PIC conducting the flight with a passenger on first-officer’s seat,
- The presence of alcohol in PIC's and the passenger's bodies,
- A possible transfer of the aircraft control from PIC to the passenger (former An-2 pilot) made by PIC,
- Violations of An-2 AFM and FAR-128 requirements on maintaining heights, bank angles during turns and flight speed while crop-dusting,
- Krasny Kut Civil Aviation Flight School management not controlling crop-dusting operations at the fields.
Final Report:

Crash of a PZL-Mielec AN-2 in Maryevka: 1 killed

Date & Time: Apr 14, 2016 at 1420 LT
Type of aircraft:
Operator:
Flight Phase:
Survivors:
No
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Crashed in unknown circumstances in a field located in Maryevka while completing a crop spraying mission. The pilot, sole on board, was killed.

Crash of a PZL-Mielec AN-2R in Aksarino

Date & Time: Apr 3, 2016 at 0732 LT
Type of aircraft:
Operator:
Registration:
RA-54828
Flight Phase:
Survivors:
Yes
Schedule:
Aksarino - Aksarino
MSN:
1G184-35
YOM:
16
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6095
Aircraft flight hours:
6782
Circumstances:
The pilot, sole on board, was engaged in a crop spraying mission over plantation located near Aksarino, Republic of Tatarstan, and the aircraft was carrying a load of 1,200 kilos of fertilizers. Shortly after takeoff, while climbing, the engine encountered technical problems. The pilot elected to make an emergency landing when the aircraft crash landed in a field and came to rest. The aircraft was damaged beyond repair and the pilot was uninjured.
Probable cause:
Most probably the accident with An-2 RA-54828 aircraft after its takeoff in order to perform crop dusting was caused by inadvertent engine cut-off due to water ingestion into fuel flow system. Most probably water ingestion into engine fuel flow system was due to violation of refueling procedure by the crew. The aircraft sustained significant damage during the emergency landing on slush soft surface.
Final Report:

Ground fire of an Antonov AN-26RT in Rostov-on-Don

Date & Time: Mar 29, 2016
Type of aircraft:
Operator:
Registration:
09 blue
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
122 02
YOM:
1982
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, the right engine caught fire. The crew aborted the takeoff procedure and was able to stop the aircraft on the runway. Unfortunately, he was unable to extinguish the fire that destroyed the right engine. All occupants evacuated safely and the aircraft was partially destroyed by fire.
Probable cause:
The right engine caught fire during takeoff for unknown reasons.

Crash of a Boeing 737-8KN in Rostov-on-Don: 62 killed

Date & Time: Mar 19, 2016 at 0342 LT
Type of aircraft:
Operator:
Registration:
A6-FDN
Survivors:
No
Schedule:
Dubai - Rostov-on-Don
MSN:
40241/3517
YOM:
2010
Flight number:
FZ981
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
55
Pax fatalities:
Other fatalities:
Total fatalities:
62
Captain / Total flying hours:
5961
Captain / Total hours on type:
4682.00
Copilot / Total flying hours:
5767
Copilot / Total hours on type:
1100
Aircraft flight hours:
21257
Aircraft flight cycles:
9421
Circumstances:
At the overnight into 19.03.2016 the Flydubai airline flight crew, consisting of the PIC and F/O, was performing the round-trip international scheduled passenger flight FDB 981/982 on route
Dubai (OMDB) – Rostov-on-Don (URRR) – Dubai (OMDB) on the B737-8KN A6-FDN aircraft. At 18:37 on 18.03.2016 the aircraft took off from the Dubai airport. The flight had been performed in IFR. At 18:59:30 FL360 was reached. The further flight has been performed on this very FL. The descent from FL has been initiated at 22:17. Before starting the descent, the crew contacted the ATC on the Rostov-on-Don airport actual weather and the active RWY data. In progress of the glide path descent to perform landing with magnetic heading 218° (RWY22) the crew relayed the presence of “windshear” on final to the ATC (as per the aboard windshear warning system activation). At 22:42:05 from the altitude of 1080 ft (330 m) above runway level performed go-around. Further on the flight was proceeded at the holding area, first on FL080, then on FL150. At 00:23 on 19.03.2016, the crew requested descent for another approach. It was an ILS approach. The A/P was disengaged by the crew at the altitude of 2165 ft QNH (575 m QFE), and the A/T at the altitude of 1960 ft QNH (510 m QFE). . In the progress of another approach the crew made the decision to initiate go-around and at 00:40:50, from the altitude of 830 ft (253 m) above the runway level, started the maneuver. After the reach of the altitude of 3350 ft (1020 m) above the runway level the aircraft transitioned to a steep descent and at 00:41:49 impacted the ground (it collided the surface of the artificial runway at the distance of about 120 m off the RWY22 threshold) with the nose-down pitch of about 50⁰ and IAS about 340 kt (630 km/h). The aircraft disintegrated on impact and all 62 occupants were killed.
Probable cause:
The fatal air accident to the Boeing 737-8KN A6-FDN aircraft occurred during the second go around, due to an incorrect aircraft configuration and crew piloting, the subsequent loss of PIC’s situational awareness in nighttime in IMC. This resulted in a loss of control of the aircraft and its impact with the ground. The accident is classified as Loss of Control In-Flight (LOC-I) occurrence.
Most probably, the contributing factors to the accident were:
- The presence of turbulence and gusty wind with the parameters, classified as a moderate to-strong "windshear" that resulted in the need to perform two go-arounds;
- The lack of psychological readiness (not go-around minded) of the PIC to perform the second go-around as he had the dominant mindset on the landing performance exactly at the destination aerodrome, having formed out of the "emotional distress" after the first unsuccessful approach (despite the RWY had been in sight and the aircraft stabilized on the glide path, the PIC had been forced to initiate go-around due to the windshear warning activation), concern on the potential exceedance of the duty time to perform the return flight and the recommendation of the airline on the priority of landing at the destination aerodrome;
- The loss of the PIC’s leadership in the crew after the initiation of go-around and his "confusion" that led to the impossibility of the on-time transition of the flight mental mode from "approach with landing" into "go-around";
- The absence of the instructions of the maneuver type specification at the go-around callout in the aircraft manufacturer documentation and the airline OM;
- The crew’s uncoordinated actions during the second go-around: on the low weight aircraft the crew was performing the standard go-around procedure (with the retraction of landing gear and flaps), but with the maximum available thrust, consistent with the Windshear Escape Maneuver procedure that led to the generation of the substantial excessive nose-up moment and significant (up to 50 lb/23 kg) "pushing" forces on the control column to counteract it;
- The failure of the PIC within a long time to create the pitch, required to perform go around and maintain the required climb profile while piloting aircraft unbalanced in forces;
- The PIC’s insufficient knowledge and skills on the stabilizer manual trim operation, which led to the long-time (for 12 sec) continuous stabilizer nose-down trim with the subsequent substantial imbalance of the aircraft and its upset encounter with the generation of the negative G, which the crew had not been prepared to. The potential impact of the somatogravic "pitch-up illusion" on the PIC might have contributed to the long keeping the stabilizer trim switches pressed;
- The psychological incapacitation of the PIC that resulted in his total spatial disorientation, did not allow him to respond to the correct prompts of the F/O;
- The absence of the criteria of the psychological incapacitation in the airline OM, which prevented the F/O from the in-time recognition of the situation and undertaking more decisive actions;
- The possible operational tiredness of the crew: by the time of the accident the crew had been proceeding the flight for 6 hours, of which 2 hours under intense workload that implied the need to make non-standard decisions; in this context the fatal accident occurred at the worst possible time in terms of the circadian rhythms, when the human performance is severely degraded and is at its lower level along with the increase of the risk of errors.
The lack of the objective information on the HUD operation (there were no flight tests of the unit carried out into the entire range of the operational G, including the negative ones; the impossibility to reproduce the real HUD readings in the progress of the accident flight, that is the image the pilot was watching with the consideration of his posture in the seat trough the stream video or at the FFS) did not allow making conclusion on its possible impact on the flight outcome. At the same time the investigation team is of the opinion that the specific features of the HUD indication and display in conditions existed during final phase of the accident flight (severe turbulence, the aircraft upset encounter with the resulting negative G, the significant difference between the actual and the target flight path) that generally do not occur under conditions of the standard simulator sessions, could have affected the situational awareness of the PIC, having been in the highly stressed state.
Final Report: