Crash of a Dassault Falcon 50EX in Moscow-Vnukovo: 4 killed

Date & Time: Oct 20, 2014 at 2357 LT
Type of aircraft:
Operator:
Registration:
F-GLSA
Flight Phase:
Survivors:
No
Schedule:
Moscow - Paris
MSN:
348
YOM:
2006
Flight number:
LEA074P
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
6624
Captain / Total hours on type:
1266.00
Copilot / Total flying hours:
1478
Copilot / Total hours on type:
246
Aircraft flight hours:
2197
Aircraft flight cycles:
1186
Circumstances:
During the takeoff run on runway 06 at Moscow-Vnukovo Airport, the three engine aircraft hit a snowplow with its left wing. The aircraft went out of control, rolled over and came to rest upside down in flames. All four occupants were killed, three crew members and Mr. Christophe de Margerie, CEO of the French Oil Group Total, who was returning to France following a meeting with the Russian Prime Minister Dmitry Medvedev. At the time of the accident, the RVR on runway 06 was estimated at 350 meters due to foggy conditions. The pilot of the snow-clearing vehicle was slightly injured.
Probable cause:
The accident occurred at nighttime under foggy conditions while it was taking off after cleared by the controller due to collision with the snowplow that executed runway incursion and stopped on the runway. Most probably, the accident was caused by the combination of the following contributing factors:
- lack of guidance on loss of control over an airdrome vehicle and/or situational awareness on the airfield in pertinent documents defining the duties of airdrome service personnel (airdrome shift supervisor and vehicle drivers);
- insufficient efficiency of risk mitigation measures to prevent runway incursions in terms of airdrome peculiarilies that is two intersecling runways;
- lack of proper supervision from the airdrome service shift supervisor, alcohol detected in his organism, over the airfield operations: no report to the ATM or request to the snowplow driver as he lost visual contact with the snowplow;
- violation by the airdrome service shift supervisor of the procedure for airdrome vehicles operations, their entering the runway (RWY 2) out of operation (closed for takeoff and landing operations) without requesting and receiving clearance from the ground controller;
- violations by the medical personnel of Vnukovo AP of vehicle driver medical check requirements by performing formally (only exterior assessment) the mandatory medical check of drivers after the duty, which significantly increased the risk of drivers consuning alcohol during the duty. The measures and controls applied at Vnukovo Airport to mitigate the risk of airdrome drivers doing their duties under the influence of alcohol were not effective enough;
- no possibility for the snowplow drivers engaged in airfield operations (due to lack of pertinent equipment on the airdrome vehicles) to continuously listen to the radio exchange at the Departure Control frequency, which does not comply with the Interaction Procedure of the Airdrome Service with Vnukovo ATC Center.
- loss of situational awareness by the snowplow driver, alcohol detected in his organism, while perfonning airfield operations that led to runway incursion and stop on the runway in use.
His failure to contact the airdrome service shift supervisor or ATC controllers after situational awareness was lost;
- ineffective procedures that resulted in insufficiently trained personnel using the airfield surveillance and control subsystem A3000 of A-SMGCS at the Vnukovo ATC Center, for air traffic management;
- no recommendation in the SOP of ATM personnel of Vnukovo ATC Center on how to set up the airfield surveillance and control subsystem A3000, including activation and deactivation of the Reserved Lines and alerts (as a result, all alerts were de-activated at the departure controller and ground controller's working positions) as well as how to operate the system including attention allocation techniques during aircraft takeoff and actions to deal with the subsystem messages and alerts;
- the porting of the screen second input of the A3000 A-SMGCS at the ATC shift supervisor WP for the display of the weather information that is not envisaged by the operational manual of the airfield surveillance and control subsystem. When weather information is selected to be displayed the radar data and the light alerts (which were present during the accident takeoff) become un available for the specialist that occupies the ATC shift supervisor's working position;
- the ATC shift supervisor's decision to join the sectors at working positions of Ground and Departure Control without considering the actual level of personnel training and possibilities for them to use the information of the airfield surveillance and control system (the criteria for joining of sectors are not defined in the Job Description of ATC shift supervisor, in particular it does not take into account the technical impossibility to change settings of the airfield surveillance and control system);
- failure by the ground controller to comply with the SOPs, by not taking actions to prevent the incursion of RWY 2 that was closed for takeoff and landing operations by the vehicles though having radar information and alert on the screen of the airfield surveillance and control system;
- failure by the out of staff instructor controller and trainee controller (providing ATM under the supervision of the instructor controller) to detect two runway incursions by the snowplow on the runway in use, including after the aircrew had been cleared to take off (as the clearance was given, the runway was clear), provided there was pertinent radar information on the screen of the airfield surveillance and control subsystem and as a result failure to inform the crew about the obstacle on the runway;
- lack of recommendations at the time of the accident in the Operator's (Unijet) FOM for flight crews on actions when external threats appear (e.g. foreign objects on the runway) during the takeoff;
- the crew failing to take measures to reject takeoff as soon as the Captain mentioned «the car crossing the road». No decision to abort takeoff might have been caused by probable nonoptimal psycho-emotional status of the crew (the long wait for the departure at an unfamiliar airport and their desire to fly home as soon as possible), which might have made it difficult for them to assess the actual threat level as they noticed the snowplow after they had started the takeoff run;
- the design peculiarity of the Falcon 50EX aircraft (the nose wheel steering can only be controlled from the LH seat) resulting in necessity to transfer aircraft control at a high workload phase of the takeoff roll when the FO (seated right) performs the takeoff.
Final Report:

Crash of a PZL-Mielec AN-2 in Shoyna

Date & Time: Sep 24, 2014 at 1225 LT
Type of aircraft:
Operator:
Registration:
RA-02322
Flight Phase:
Survivors:
Yes
Schedule:
Shoyna – Arkhangelsk
MSN:
1G239-26
YOM:
1990
Flight number:
OAO718
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft departed Shoyna Airport on a regular schedule service to Arkhangelsk-Vaskovo Airport, carrying eight passengers and two pilots. At liftoff, the aircraft banked right, causing the right lower wing to struck the ground. The right main gear was torn off upon impact. Out of control, the aircraft veered off runway and came to rest in a grassy area. All 10 occupants were rescued, among them three were slightly injured. The aircraft was damaged beyond repair. It is believed that the crew encountered strong cross winds upon takeoff.

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

Date & Time: Aug 6, 2014 at 0715 LT
Type of aircraft:
Operator:
Registration:
RA-17890
Flight Phase:
Survivors:
Yes
Schedule:
Prototskiye - Prototskiye
MSN:
1G205-31
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
7503
Aircraft flight cycles:
38974
Circumstances:
The crew was engaged in a crop spraying mission on rice paddy field located in Prototskiye (Krasnoarmeisk district of the Krasnodar region). Two minutes after takeoff, while flying at a height of about 50 metres, the engine lost power. The captain attempted an emergency landing when the aircraft nosed over and came to rest upside down, some 2 km east of Prototskiye. Those parts of the fuselage which were above the water were consumed by the erupting fire and both pilots escaped uninjured.
Probable cause:
The accident with An-2 RA-17890 aircraft was caused by its nosing-over during the emergency landing at the submerged rice bay. The emergency landing was due to the engine power loss in flight caused by the destruction of the can type combustor of the exhaust collector and burnout of the carburetor intake valve with the following high-temperature gases ingestion in the intake areas of the engine carburetor. The fatigue destruction of the can type combustor of the exhaust collector was caused along the main crack near the intake flex socket, it started from the surface of the damaged inlet port under the tube attachment pin towards the exhaust collector. By the moment of the main crack formation both inlet ports in left can type combustor under the tube attachment pin towards the exhaust collector had intolerable damage and size. During the last overhaul of the engine exhaust system of An-2 RA-17890 aircraft the left can type combustor had intolerable damage in its attaching lug to the exhaust collector which wasn't eliminated. The destruction of the inlet port valve was caused by the fusion of the boundaries of it material grains in conditions of acute temperature exposure induced by the destruction of the left can type combustor wall towards the main crack. Inadequate material (aluminum alloy D-16) of the valve specified by the drawing of aluminum allow AL-9T contributed to the valve destruction.

Crash of a BAe 125-800B in Moscow

Date & Time: Jul 7, 2014
Type of aircraft:
Operator:
Registration:
RA-02806
Flight Type:
Survivors:
Yes
Schedule:
Moscow – Makhatchkala
MSN:
258106
YOM:
1987
Flight number:
CIG9661
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Moscow-Vnukovo Airport on a positioning flight to Makhatchkala, carrying a crew of three. On approach to Makhatchkala Airport, the crew was unable to lower the gear that remained stuck in their wheel well. Despite several attempts, the crew was unable to lower the gear manually and eventually decided to return to Moscow-Vnukovo for an emergency landing. The aircraft belly landed on a foam covered runway and slid for few dozen metres before coming to rest. All three crew members escaped uninjured and the aircraft was damaged beyond repair.

Crash of an Antonov AN-2 in Starosel'ye: 2 killed

Date & Time: Jun 7, 2014 at 1440 LT
Type of aircraft:
Operator:
Registration:
RF-02883
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Starosel'ye - Starosel'ye
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after takeoff from Starosel'ye Airfield, while in initial climb, the aircraft impacted trees, stalled and crashed in a wooded area, bursting into flames. The aircraft was totally destroyed by a post crash fire and both occupants were killed. It was reported that the aircraft was not on the Russian Aviation Register and that the registration RF-02883 was unknown to the authority. Also, the pilot decided to takeoff from an airstrip that was closed to traffic and failed to announce his flight to ATC.

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 PZL-Mielec AN-2T in Gryazi

Date & Time: May 9, 2014 at 1630 LT
Type of aircraft:
Operator:
Registration:
RF-00446
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Terbuny – Gryazi
MSN:
1G236-07
YOM:
1989
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was returning to its base in Gryazi after taking part to a demonstration in Terbuny. After takeoff, while in initial climb, the engine lost power. The aircraft encountered difficulties to gain height, impacted power cables and crashed in an open field. All nine occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Loss of engine power for unknown reasons.

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 Antonov AN-24RV in Moscow

Date & Time: Jan 22, 2014 at 0819 LT
Type of aircraft:
Operator:
Registration:
RA-46473
Survivors:
Yes
Schedule:
Pskov - Moscow
MSN:
2 73 081 01
YOM:
1972
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
24
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Moscow-Domodedovo Airport, the crew encountered poor visibility due to marginal weather conditions. Rather than initiating a go-around procedure, the crew continued the descent when the aircraft crash landed to the right of runway 14R, in an area between the runway and the boundary fence. All 28 occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of an Antonov AN-12B in Irkutsk: 9 killed

Date & Time: Dec 26, 2013 at 2101 LT
Type of aircraft:
Operator:
Registration:
12162
Flight Type:
Survivors:
No
Schedule:
Novosibirsk - Irkutsk
MSN:
3 3 415 09
YOM:
1963
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
9
Circumstances:
The four engine aircraft departed Novosibirsk-Yeltsovka Airport on a cargo flight to Irkutsk, carrying three mechanics, six crew members and a load consisting of 1,5 tons of spare parts for the Irkut Group (Sukhoi, Beriev) based in Irkutsk. On approach to Irkust-2 Airport, the crew encountered marginal weather conditions with mist and limited visibility due to the night. On short final, the aircraft deviated to the right and descended too low until it impacted military vehicles and crashed onto several barracks of the 109th Arsenal of the Russian Army, coming to rest 770 metres short of runway 14 and about 90 metres to the right of its extended centerline. The aircraft was destroyed and all nine occupants were killed. There were no victims on the ground.
Probable cause:
The following findings were identified:
- The crew continued the descent below MDA without any visual contact with the ground, until the aircraft impacted obstacles and crashed,
- The flight manager was aware of the deterioration of the weather conditions at destination with a visibility that was below minimums, but failed to inform the crew accordingly,
- ATC at Irkutsk-2 Airport failed to inform the crew that he was deviating from the approach path on short final.