Crash of an Embraer EMB-135BJ Legacy 600 in Kuzhenkino: 10 killed

Date & Time: Aug 23, 2023 at 1715 LT
Operator:
Registration:
RA-02795
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Moscow - Saint Petersburg
MSN:
145-1008
YOM:
2007
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
The Legacy departed Moscow-Sheremetyevo Airport shortly before 1645LT on a flight to St Petersburg-Pulkovo, carrying seven passengers and three crew members. According to the radar, while cruising at FL280, it entered an uncontrolled descent and spiraled into the ground until it crashed in an open field located near the village of Kuzhenkino, bursting into flames. The airplane was destroyed and all 10 occupants were killed. The airplane was the property of the Wagner Group owned by Evgueni Viktorovitch Prigozhine who was on board with Dmitry Utkin, n°2 of the group. It is showable on videos that the airplane was emanating white/grey smoke while spiraling to the ground.

Crash of a Sukhoi Superjet 100-95B in Moscow: 41 killed

Date & Time: May 5, 2019 at 1830 LT
Type of aircraft:
Operator:
Registration:
RA-89098
Survivors:
Yes
Schedule:
Moscow - Murmansk
MSN:
95135
YOM:
2017
Flight number:
SU1492
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
73
Pax fatalities:
Other fatalities:
Total fatalities:
41
Captain / Total flying hours:
6800
Captain / Total hours on type:
1570.00
Copilot / Total flying hours:
765
Copilot / Total hours on type:
615
Aircraft flight hours:
2710
Aircraft flight cycles:
1658
Circumstances:
The aircraft departed runway 24C at Moscow-Sheremetyevo Airport at 1803LT on a schedule service to Murmansk. Few minutes after takeoff, while climbing to an altitude of 10,000 feet, the crew encountered problems with the electrical system and informed ATC about an emergency situation via the transponder codes 7700 because communication systems were unserviceable. The crew initiated a circuit to return to the airport, continued the approach to runway 24L. On approach at an altitude between 900 and 1,100 feet, the windshear warning system sounded five times 'Go around. Windshear ahead'. From a height of 80 m (260 ft) above ground level, the aircraft descended below the glide path and at a height of 55 m (180 ft) the TAWS warning sounded: "Glide Slope." From that moment on the airspeed increased to 170 knots. At 18:30 the aircraft overflew the runway threshold and touched down at a distance of 900 m past the threshold at a speed of 158 knots. Touchdown occurred at a g-force of at least 2.55g with a subsequent bounce to a height of about 2 m. After two seconds the aircraft landed again on the nose landing gear with a vertical load 5.85g, and bounced to a height of 6 m. The third landing of the aircraft occurred at a speed of 140 knots with a vertical overload of at least 5g. This caused a rupture of the wing structure and fuel lines. The aircraft caught fire, went out of control, veered off runway to the right and came to rest in a grassy area, bursting into flames. The aircraft was destroyed by fire. 37 occupants were evacuated while 41 people, among them a crew member, were killed.

Crash of a Gulfstream G200 in Moscow

Date & Time: Feb 26, 2019 at 1244 LT
Type of aircraft:
Operator:
Registration:
4K-AZ88
Survivors:
Yes
Schedule:
Baku - Moscow
MSN:
189
YOM:
2008
Flight number:
EWS88
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7608
Captain / Total hours on type:
2356.00
Copilot / Total flying hours:
2554
Copilot / Total hours on type:
609
Aircraft flight hours:
4174
Aircraft flight cycles:
1787
Circumstances:
The airplane departed Baku-Bina Airport on a charter flight to Moscow, carrying three passengers and three crew members. Following an uneventful flight, the crew was cleared for an approach to Moscow-Sheremetyevo Airport runway 24C. The aircraft landed at a speed of 150 knots some 250 metres past the runway threshold. After touchdown, the crew started the braking procedure and activated the thrust reversers. After a course of several hundred metres, the aircraft deviated to the left, made an almost 180 turn and veered off runway to the left. While contacting soft ground, the right main gear was torn off and the aircraft came to rest in a snow covered area. All six occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The reason for the accident with the Gulfstream G200 4K-AZ88 was the stowing of the right-engine reverser by the pilot KVS from maximum thrust reversal while maintaining maximum thrust reversal on the left engine, which led to the appearance of a significant turning moment to the left. The aircraft turning to the left in the presence of a cross wind to the right, as well as turbulence of the airflow near the rudder due to the open thrust reversal mechanism of the left engine and possible ice deposition on the outer surfaces of the aircraft, which led to the development of a significant swing moment on the rudder. The development of a significant articulated moment on the rudder, in the absence of power steering in the rudder control system, led to its deviation to the leftmost position despite significant (up to 82 kg or 180 pounds) forces exerted by the crew on the pedals. The deviation of the rudder (pedals) to the left also led to the deviation of the nose wheel to the left. The total moment from the running reverse of the left engine, from the right engine in direct draft mode, and from the rudder and nose wheel deflection to the left, led to the aircraft rolling out of the runway and its damage. Separate braking applied by the crew could not prevent the aircraft from rolling out.

The following contributing factors were identified:
- The crew did not take into account the provisions of the AOM about the possible "destabilizing" effect of the thrust reverse when landing with a cross wind on the runway with a reduced braking coefficient;
- Increased psycho-emotional tension of the crew members due to long dissatisfaction and emotional discussion of instructions and actions of ATC controllers. At the same time, the instructions and actions of the ATC service controllers were in line with established procedures.
Final Report:

Ground fire of an Ilyushin II-96-300 in Moscow

Date & Time: Jun 3, 2014 at 1425 LT
Type of aircraft:
Operator:
Registration:
RA-96010
Flight Phase:
Survivors:
Yes
MSN:
74393201007
YOM:
1994
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
51427
Aircraft flight cycles:
7625
Circumstances:
The aircraft was parked on the apron at Moscow-Sheremetyevo Airport since two months as it was offered for sale and not in service anymore. In the afternoon, a fire erupted in the cockpit for unknown reasons. It took more than an hour to the fire brigade to extinguish the fire that destroyed all the cabin and the roof of the aircraft.
Probable cause:
Destroyed by fire of unknown origin. There were no investigations on this mishap.

Crash of a BAe 125-700B in Moscow

Date & Time: Feb 12, 2014 at 1850 LT
Type of aircraft:
Operator:
Registration:
RA-02801
Flight Type:
Survivors:
Yes
Schedule:
Moscow - Moscow
MSN:
257097
YOM:
1980
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew departed Moscow-Sheremetyevo Airport on a positioning flight to Moscow-Vnukovo Airport. On approach by night, the crew configured the aircraft for landed when he realized that the right main gear remained stuck in its wheel well. The crew following a holding pattern and after the runway was covered with foam, he completed an emergency landing. After touchdown, the right wing contacted ground and the aircraft slid for few dozen metres before coming to rest. Both pilots escaped uninjured and the aircraft was damaged beyond repair.

Crash of an Embraer ERJ-145EP in Moscow

Date & Time: Apr 28, 2011 at 1625 LT
Type of aircraft:
Operator:
Registration:
UR-DNK
Survivors:
Yes
Schedule:
Dniepropetrovsk – Moscow
MSN:
145-039
YOM:
1997
Flight number:
UDN505
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
30
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Dniepropetrovsk, the copilot started the approach to Moscow-Sheremetyevo Airport runway 25R with the flaps down at 22°. After touchdown, he started the braking procedure but the aircraft failed to decelerate as expected. The emergency braking systems were activated without any noticeable effect. Approaching the end of the runway at a speed of 70 knots, the copilot turn to the right in an attempt to veer off runway. The airplane ground looped then contacted a grassy area and lost its undercarriage before coming to rest. All 34 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the brakes is suspected.

Crash of a Boeing 737-505 in Perm: 88 killed

Date & Time: Sep 14, 2008 at 0510 LT
Type of aircraft:
Operator:
Registration:
VP-BKO
Survivors:
No
Schedule:
Moscow - Perm
MSN:
25792/2353
YOM:
1992
Flight number:
AUL821
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
82
Pax fatalities:
Other fatalities:
Total fatalities:
88
Captain / Total flying hours:
3900
Captain / Total hours on type:
1190.00
Copilot / Total flying hours:
8900
Copilot / Total hours on type:
236
Aircraft flight hours:
44533
Aircraft flight cycles:
35104
Circumstances:
On September 13, 2008 an Aeroflot –Nord flight crew (Captain and copilot), were conducting a scheduled domestic passenger flight n°AFL821 on a B737-505 aircraft, registration VP-BKO, from Moscow (Sheremetyevo, UUEE) to Perm (Bolshoye Savino, USPP). Apart from the two-member flight crew there were 4 flight attendants and 82 passengers on board, which makes a total of 88 people, including 66 citizens of the Russian Federation, 8 citizens of Azerbaijan, 1 citizen of Byelorussia, 1 of Germany, 1 of Italy, 1 of China, 1 of Latvia, 1 of Turkey, 1 of Uzbekistan, 5 citizens of Ukraine and 2 of France. According to the load sheet, the aircraft payload (cargo and passengers) was 8079 kg. The takeoff weight was ~54000 kg (with the max TOW of 60554 kg), the CG was at 20.61 % MAC, which was within the B-737-500 FCOM limitations. The calculated landing weight was 49700 kg (with the maximum of 49895 kg), and the CG was at 21.9 % MAC, which was also within the B737-500 FCOM limitations. The pre-flight briefing was conducted in due time and in compliance with the standard procedures. All the crew members passed medical check at the medical office of Aeroflot – Russian Airlines on September 13, 2008 at 1948 hrs and got permissions to fly. On the basis of the dispatch information (aircraft condition, aeronautical information, weather information, aircraft load data and operational flight plan) the PIC at 1955 hrs made a decision to fly. The takeoff was performed at 2113 without delay. The climb and level flight at FL290, 9,100 metres were conducted without any deviations. At 2245 hrs the crew started descent from the flight level to waypoint Mendeleyevo (940 MN). After passing over Mendeleyevo, in compliance with the Perm Approach Control instruction, the aircraft flew via the outer marker (705 PX) of Runway 21 which is the initial approach fix (IAF) for Runway 21 (heading 212° magnetic). After passing over the RWY with heading 110° M, the crew, following the Controller’s instruction, turned right for back course and started maneuvering for ILS approach to Runway 21. After the base turn, approaching the landing course at 600 m with both autopilot and autothrottle disengaged, the aircraft started climbing up to 1300 m, rolled 360° over the left wing and collided with the ground. The aircraft was totally destroyed and partly burnt in the ground fire. All passengers and crew members on board died due to the ground impact. The accident occurred at 2310 hrs 12.4 km from aerodrome reference point (ARP) of Perm Airport, azimuth 60° M. Accident site elevation is 153 m.
Probable cause:
The immediate cause of the accident was spatial disorientation of the crew, especially the Captain who was the pilot flying at the final stage of the flight, which led to the left flip-over, a steep descent and the crash of the aircraft. The spatial disorientation was experienced during the night time operation in clouds, with both autopilot and autothrottle disengaged. Contributing to the development of the spatial disorientation and failure to recover from it was a lack of proficiency in aircraft handling, crew resource management and of skills associated with upset recovery using "western"-type attitude indications that are found on foreign and modern Russian made aircraft. This type of indication differs from the one used on aircraft types previously flown by the crew (Tupolev 134, Antonov 2). The cause above was determined on the basis of flight recorders and ATC recorder data analysis, examination of the airframe and engine wreckage, results of the accident flight simulation, findings of the independent expertise conducted by test pilots from State Research Institute of Civil Aviation and Gromov Flight Research Institute as well as line pilots, and also on the basis of all the works conducted with participation of experts from Bermuda, France, Russia, UK and USA in the course of the investigation. The systemic cause of the accident was insufficient management by the airline of flight and maintenance operations of the Boeing 737 type of aircraft. These deficiencies in the aircraft maintenance also revealed through safety inspections conducted by the Russian Transport Oversight Authority and the Russian CAA after the accident. Deficiencies in the aircraft maintenance led to a situation when flights were performed for a long time with a throttle stagger that exceeded the limitations in the AMM and when the maintenance staff did not follow the AMM recommended troubleshooting procedures. The need to manage the throttle stagger during the approach increased crew workload. The forensic medical examination performed in the State Healthcare Center of Special Status “Perm Regional Forensic Expertise Bureau” confirmed the presence of ethyl alcohol in the Captain’s body before his death. The captain’s recent work schedule during the time period before the accident was conducive to fatigue and did not comply with national regulations.
Final Report:

Crash of a BAe 125-700A in Kharkiv: 3 killed

Date & Time: Jan 2, 2006 at 1116 LT
Type of aircraft:
Operator:
Registration:
P4-AOD
Flight Type:
Survivors:
No
Schedule:
Moscow - Kharkiv
MSN:
257153
YOM:
1981
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The crew departed Moscow-Sheremetyevo Airport on a positioning flight to Kharkiv where some passengers should be picked up for a charter flight to Lyon. On final approach to Kharkiv-Osnova Airport runway 07, at a distance of 4,600 metres from runway threshold, the crew selected flaps down. The right flap deployed to an angle of 20° (as requested by the crew) while the left flap deployed to an angle of 6°. This asymmetry caused the aircraft to roll to the left then to enter an uncontrolled descent before it crashed on the shore of lake Komsomolsk. The aircraft disintegrated on impact and debris were found 140 metres further while the main wreckage sank in the lake, some 4,300 metres from the runway threshold and 750 metres to the left of its extended centerline. All three crew members were killed.
Probable cause:
The crew lost control of the aircraft after they selected flaps down. Investigations showed that a technical failure occurred on the flap deployment synchronization system due to the failure of a drive pinion.

Crash of a Dassault Falcon 20C in Moscow

Date & Time: May 20, 2005
Type of aircraft:
Operator:
Registration:
RA-09007
Survivors:
Yes
MSN:
136
YOM:
1968
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Aircraft lost power on both engines while on approach to Moscow-Vnukovo airport. The crew decided to divert to Sheremetievo Airport when the undercarriage collapsed on landing. The aircraft veered off runway and slid in a grassy area before coming to rest. Nobody was injured but the aircraft was damaged beyond repair.
Probable cause:
It is believed that the engine lost power on approach because of the poor fuel quality.