Country
code

Rostov oblast

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:

Crash of a PZL-Mielec AN-2R near Rostov

Date & Time: Jun 15, 2015 at 0754 LT
Type of aircraft:
Operator:
Registration:
RA-84553
Flight Phase:
Survivors:
Yes
MSN:
1G189-20
YOM:
1980
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10541
Aircraft flight hours:
9645
Circumstances:
The single engine aircraft was engaged in a crop spraying mission on behalf of the Mikhail Farm located in the Tatsinsky District of the Rostov Region. The aircraft was carrying 400 kilos of fuel, 1,200 liters of pesticides, one pilot and one boy aged 13, the son of the farmer. Few minutes after takeoff, while approaching the area to be treated at a height of about 20-25 metres and at a speed of 130 km/h, the engine failed. The aircraft lost height, collided with power cables and crashed in a field, bursting into flames. The wreckage was found 2 km from the Mikhail farmhouse. The pilot escaped unhurt while the boy was injured. The aircraft was totally destroyed by a post crash fire.
Probable cause:
The reason for the accident with An-2 RA-84553 was performing a flight in a known defective aircraft, leading to engine failure and the need for in-flight forced landing, during which there was a collision with power lines, followed by a rough landing that led to the structural failure and fire. Investigation to determine the cause of the engine failure was not possible due to the failure to ensure the safety of the aircraft after the accident and the absence of operational and technical documentation. The adoption of the decision by the pilot to reject takeoff after detecting a loss engine power on the takeoff could have prevented the accident. The aircraft did not have a valid Certificate of Airworthiness and the time between overhauls had been exceeded on 10 April 2015.
Final Report:

Crash of a PZL-Mielec AN-2T in Azov

Date & Time: May 10, 2015 at 1433 LT
Type of aircraft:
Operator:
Registration:
RF-01159
Flight Phase:
Survivors:
Yes
Schedule:
Azov - Azov
MSN:
1G108-24
YOM:
1969
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Azov-Almaz Airfield on a skydiving mission, carrying 12 skydivers and one pilot on behalf of the Azov Flying Club. Shortly after takeoff, while climbing, the engine lost power. The pilot attempted to return for an emergency landing when the aircraft lost height and crashed in an open field located near the airport, bursting into flames. All 13 occupants were rescued, among them one passenger suffered minor injuries. The aircraft was totally destroyed by fire.
Probable cause:
Loss of engine power for unknown reasons.

Crash of a PZL-Mielec AN-2P in Shakhty

Date & Time: Jul 28, 2013
Type of aircraft:
Operator:
Registration:
FLA-3618K
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Shakhty - Shakhty
MSN:
1G151-37
YOM:
1973
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Shakhty Airport, Rostov oblast, the pilot encountered engine problem. He elected to make an emergency landing in an open field located 500 metres from the airport. On touchdown, the aircraft lost its undercarriage, wings and tail before coming to rest in bushes. The pilot, uninjured, fled the scene but was arrested by police few hours later. Technician by a Plant at the Shakhty Airport, he was the owner of this aircraft since seven months and was performing a local test flight despite he was not in possession of any valid pilot licence according to Russian authorities.

Crash of an Antonov AN-2 near Byelaya Kalitva

Date & Time: Mar 22, 2012
Type of aircraft:
Operator:
Registration:
FLA-1041K
Flight Phase:
Flight Type:
Survivors:
Yes
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane crashed in unknown circumstances in a forest located 50 km north of Byelaya Kalitva, Rostov oblast. There were no casualties but the aircraft was damaged beyond repair. The circumstances of the accident remains unknown. The flight was considered as illegal as this registration was not officially recorded in the Russian Civil Aviation register.

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

Date & Time: Aug 25, 2006
Type of aircraft:
Registration:
RA-32706
Flight Phase:
Survivors:
Yes
Schedule:
Voronovo - Voronovo
MSN:
1G212-11
YOM:
1985
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Few minutes after takeoff from Voronovo, the crew encountered engine problems. He elected to maintain altitude but the aircraft descended, collided with trees and crashed in a wooded area located 7,5 km from the departure point, bursting into flames. Both pilots escaped uninjured while the aircraft was totally destroyed by a post crash fire.
Probable cause:
Engine failure for unknown reasons.

Crash of a Tupolev TU-154B-2 near Gluboki: 46 killed

Date & Time: Aug 24, 2004 at 2253 LT
Type of aircraft:
Operator:
Registration:
RA-85556
Flight Phase:
Survivors:
No
Schedule:
Moscow - Sochi
MSN:
82A556
YOM:
1982
Flight number:
SBI1047
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
38
Pax fatalities:
Other fatalities:
Total fatalities:
46
Aircraft flight hours:
30751
Circumstances:
The aircraft departed Moscow-Domodedovo Airport at 2140LT on a schedule service to Sochi-Adler Airport. At 2253LT, while cruising at an altitude of 12,100 metres, the aircraft suffered an in-flight explosion, entered an uncontrolled descent and crashed in a field located near Gluboki. First rescuers arrived on the scene about 8 hours later. The aircraft was totally destroyed and all 46 occupants were killed.
Probable cause:
The Federal Safety Board (FSB) reported 3 days later that the accident was the consequence of the explosion of a bomb. Two women flying from Makhatshala landed in Moscow at 1945LT and were able to embark with the explosive device following security deficiencies. Traces of hexogene were found on debris.

Crash of a Yakovlev Yak-40 in Rostov-on-Don

Date & Time: Jan 25, 1995 at 1506 LT
Type of aircraft:
Registration:
RA-87464
Survivors:
Yes
Schedule:
Volgograd - Rostov-on-Don
MSN:
9 43 03 37
YOM:
1974
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Rostov-on-Don Airport, the three engine aircraft encountered difficulties to stop within the remaining distance. It overran, lost its undercarriage, struck a concrete wall and came to rest 870 past the runway end. All 10 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Following a wrong manipulation, the flight engineer activated the thrust reversers on engine n°1 and n°3 but not on the engine n°2 that was providing full power. Such configuration reduced the braking action and the crew was unable to stop the aircraft within the landing distance available.

Crash of a Beriev BE-12P near Veshenskaya

Date & Time: Jul 14, 1992
Type of aircraft:
Registration:
40 yellow
Flight Type:
Survivors:
Yes
MSN:
9 6 014 04
YOM:
1969
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was engaged in a fire fighting mission and its crew just landed on the Don River to perform a scooping mission when it collided with a flock of birds that struck the right engine. The aircraft veered to the right and came to rest on the shore. All four crew members escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Birdstrike.