Crash of a Boeing 737-53A in Kazan: 50 killed

Date & Time: Nov 17, 2013 at 1924 LT
Type of aircraft:
Operator:
Registration:
VQ-BBN
Survivors:
No
Schedule:
Moscow - Kazan
MSN:
24785/1882
YOM:
1990
Flight number:
TAK363
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
44
Pax fatalities:
Other fatalities:
Total fatalities:
50
Captain / Total flying hours:
2783
Captain / Total hours on type:
2509.00
Copilot / Total flying hours:
2093
Copilot / Total hours on type:
1943
Aircraft flight hours:
51547
Aircraft flight cycles:
36596
Circumstances:
On final approach to Kazan from Domodedovo in marginal weather conditions, crew was forced to make a go around as the aircraft was not correctly aligned with the runway centerline. While climbing to a height of 700 meters, the aircraft went out of control, nosed down and hit the ground. The aircraft disintegrated on impact and all 50 occupants were killed. MAK reported in a first statement that the crew did not follow the standard approach profile and the approach was unstable. TOGA mode was selected, autopilot deactivated and flaps raised from 30 to 15 degrees. As gear were retracted, the aircraft pitched up to about 25 degrees nose up and the indicated airspeed decreased from 150 to 125 knots. Crew countered the nose up by control inputs and the climb was stopped. Aircraft reached a maximum height of 2,300 feet and began to rapidly descend until it impacted the ground with a near vertical angle of 75 degrees at a speed of 242 knots, some 20 seconds after reaching the height of 2,300 feet. The crash was no survivable.
Probable cause:
Systemic weaknesses in identifying and controlling the levels of risk, non-functional safety management system in the airline and lack of control over the level of crew training by aviation authorities at all levels (Tatarstan Civil Aviation Authority, Russian Civil Aviation Authority), that resulted in an unqualified crew being assigned to the flight.
During the go-around the crew did not recognize that the autopilot had disconnected resulting in the aircraft impacting ground in a complex spatial position (nose up upset). The captain, pilot flying, lacked the skills to recover the aircraft from the complex spatial upset (lack of Upset Recovery), that led to significant negative G-forces, loss of spatial orientation sending the aircraft into a steep drive (75 degrees nose down) until impact with ground.
The go around was required because the aircraft on its final approach arrived in a position from which landing was impossible as result of a map shift by about 4000 meters (aircraft systems determining the position of the aircraft in error), the inability of the crew in those circumstances to combine aircraft control and navigation with needed precision, and the lack of active support by air traffic control during prolonged observation of significant deviation from the approach procedure.
The following factors were considered as contributory:
The captain not having had primary flight training,
The flight crew members being allowed to upgrade to Boeing 737 without satisfying the required qualifications including the English language,
Methodical shortcomings in retraining as well as verification of results and quality of training,
Insufficient level of organisation of flight operations at the airline, which resulted in failure to detect and correct shortcomings in working with the navigation equipment, pilot technique and crew interaction, including missed approaches,
Systematic violation of crew work and rest hours, a large debt of holidays, which could have resulted in accumulation of fatigue adversely affecting crew performance, Simulator training that lacked a missed approach with intermediate height and all engines operating,
Increased emotional stress to the flight crew before deciding to go around because they could not establish the position of their aircraft with the necessary precision to accomplish a successful landing,
Violation of the principle "Aviate, Navigate, Communicate" by both flight crew and air traffic control, which resulted in the flight crew not following standard operating procedures at the time of initiating the go around because the pilot monitoring was diverted from his duties for a prolonged period and did not monitor the flight parameters,
The fact that the crew did not recognize the autopilot had disconnected and delayed intervention by the crew, that resulted in the aircraft entering a complex spatial position (nose up upset),
Imperfection of simulator training programs for Upset Recovery Procedures as well as lack of criteria for assessing the quality of training, which resulted in the crew being unable to recover the aircraft from the upset,
The possible impact of somatogravic illusions,
The non-addressing of prior accident investigation recommendations, geared towards elimination of risks and establishing risk level management, had prevented the prevention of this accident,
Lack of proper supervision of issuance of pilot certificates in accordance with achieving specified requirements and qualifications,
Failure of safety management system (SMS) in the airline, lack of guidelines for SMS development and approval, lack of a formal approach to approve/agree on SMS and pilot training by the related authorities,
Deficiencies in aviation training centers' performance and absence of verification of training quality,
Lack of requirements for flight crew to be proficient in English Language for retraining on foreign aircraft types and lack of formal approach to verify language proficiency,
lack of formal approach to conduct periodic verification of flight crew qualification,
systematic violation of crew work and rest times,
lack of training of flight crew on go around from intermediate heights in manual control potentially leading to complex spatial position (e.g. nose high upset),
The map shifts in aircraft without GPS without training of crew to operate in such conditions,
Lack of active assistance by air traffic control when the approach procedure was deviated from over a prolonged period of time,
Breach of principle "Aviate, Navigate, Communicate".
Translation via www.avherald.com
Final Report:

Crash of a Antonov AN-2 in Tayozhny: 2 killed

Date & Time: Oct 26, 2013 at 2015 LT
Type of aircraft:
Operator:
Flight Type:
Survivors:
Yes
Schedule:
Yerbogachon - Tayozhny
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Following an illegal flight from Yerbogachon (Irkutsk region), the crew started a night approach to Tayozhny (Boguchany district of the Krasnoyarsk region) Airfield. In poor visibility due to the night, the crew was unable to establish a visual contact with the abandoned airstrip. Two approaches were abandoned. During a third attempt, the single engine airplane impacted trees and crashed in a wooded area located 35 metres short of runway, bursting into flames. Both pilots were killed and both passengers were seriously injured.
Probable cause:
According to investigations, the aircraft did not have any CofA or registration certification, and it was unknown to the Russian registry. It is believed that the flight was illegal as the crew was attempting to land on an abandoned airfield and therefore not equipped for night operations.

Crash of an Antonov AN-2 in Sevryukovo

Date & Time: Oct 6, 2013 at 1425 LT
Type of aircraft:
Operator:
Registration:
RA-31505
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Sevryukovo - Sevryukovo
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Bought in 2000 and stored since, the airplane was under restoration since August 2013. The crew (one pilot and one engineer), decided to perform a test flight in the region of Sevryukovo (Korocha District of the Belgorod region). En route, the engine failed, forcing the crew to attempt an emergency landing. The aircraft impacted ground and crashed, coming to rest upside down and bursting into flames. Both occupants escaped uninjured while the aircraft was partially destroyed by fire.
Probable cause:
An investigation by the Interstate Aviation Committee revealed that the airplane carried a false registration and was flown without a certificate of airworthiness. Since the airplane was not officially registered, the IAC terminated their investigation.

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

Date & Time: Sep 18, 2013 at 1337 LT
Type of aircraft:
Operator:
Registration:
RA-33017
Flight Phase:
Survivors:
Yes
Schedule:
Surgut – Saranpaul – Arbyn – Surgut
MSN:
1G218-04
YOM:
1986
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
5277
Aircraft flight cycles:
24822
Circumstances:
The aircraft departed Surgut on September 12 on a special flight to Saranpaul and Arbyn, carrying two pilots and five employees of the Sosvapromgeologya Company. On September 18, the crew was supposed to fly back to Surgut but due to poor weather conditions, decided to fly to Nefteyugansk. About an hour and 10 minutes into the flight, while cruising at an altitude of 700 metres, the engine temperature increased to 305° C. and the oil temperature to 90° C. In the same time, the engine lost power. The crew decided to reduce his altitude and to attempt an emergency landing when the aircraft crash landed in a field located 48 km west of Nyagan. There was no fire. All seven occupants were injured and the aircraft was damaged beyond repair.
Probable cause:
Most probably the accident with An-2 RA-33017 aircraft was caused by usage of uncoordinated automative fuel not specified by valid aircraft maintenance engineering documentation with low octane grade, mechanical admixture (rusting) that resulted in cylinder-heads temperature increase beyond operating limits, engine power loss, unintentional flight altitude decrease and the need of an emergency landing on saturated terrain.
The contributing factors could be:
- Unsatisfactory management of storage, refiling procedures and fuel quality inspection at Arbyn Airfield,
- Incorrect PIC's decision to perform a flight after detection of deviation from standards in fuel quick drain (color, consistency, mechanical mixtures).

Crash of a Canadair RegionalJet CRJ-200ER in Moscow

Date & Time: Sep 7, 2013 at 2115 LT
Operator:
Registration:
TC-EJA
Survivors:
Yes
Schedule:
Naples - Moscow
MSN:
7763
YOM:
2003
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Naples-Capodichino Airport, the crew started the descent to Moscow. On approach to Vnukovo Airport Runway 09, while completing the approach checklist and configuring the aircraft for landing, the crew noticed that both main landing gears remained stuck in their wheel well while the nose gear was lock down properly. The crew abandoned the approach and initiated a go-around. During a holding circuit, the crew attempted to troubleshoot the system and to deploy both main gears manually without success. The crew eventually decided to complete the landing in such configuration. The aircraft landed on runway 01 with both main gears retracted and the nose gear down, slid for few dozen metres and came to a halt. All 11 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a PZL-Mielec AN-2TP near Vilyuisk

Date & Time: Aug 16, 2013 at 1345 LT
Type of aircraft:
Operator:
Registration:
RA-01419
Flight Phase:
Survivors:
Yes
Schedule:
Vilyuisk - Kyubeinde-Ugulet
MSN:
1G230-59
YOM:
1988
Flight number:
PI9977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3973
Captain / Total hours on type:
480.00
Copilot / Total flying hours:
374
Copilot / Total hours on type:
52
Aircraft flight hours:
7587
Aircraft flight cycles:
10148
Circumstances:
Few minutes after takeoff from Vilyuisk Airport, on a schedule service (flight n° PI9977) to Kyubeinde-Ugulet, while cruising at an altitude of about 400 metres, the engine overheated and lost power while the oil pressure dropped. The crew decided to return to Vilyuisk when the engine failed shortly later. The captain attempted an emergency landing in a swampy area located 26 km northwest of Vilyuisk (at N63°54.584" E121°18.048"). The main wheels got stuck in soft ground, the engine was ripped off, and the aircraft came to rest, bursting into flames. Both pilots and all 9 passengers escaped uninjured and the aircraft was totally destroyed by fire.
Probable cause:
The accident with An-2Т RA-01419 aircraft was caused by emergency landing at the landing place in marsh area selected from air that resulted in main landing gear dipping in soft ground, dynamic pitch-down moment followed by engine ground impact and fuselage separation along engine mounting fitting, airframe structure and gear damage. Gasoline pipeline destruction during engine separation from aircraft frame and gasoline ingestion on the hot parts of power unit caused fire which almost completely destroyed the aircraft. Wrong PIC's actions who didn't turn off ignition and shut off fuel before aircraft landing could contribute to the fire. The emergency landing at the landing place selected from air was caused by oil temperature increase and pressure drop below specified by the aircraft FOM values in flight. It wasn't possible to determine the cause of temperature increase and oil pressure drop due to engine component substantial damage during fire.
Final Report:

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 a PZL-Mielec AN-2 near Nekrasovka

Date & Time: Jun 28, 2013 at 1100 LT
Type of aircraft:
Operator:
Registration:
RF-00408
Flight Phase:
Survivors:
Yes
Schedule:
Khabarovsk - Samarga
MSN:
1G98-04
YOM:
1968
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft departed Khabarovsk on a charter flight to Samarga, carrying two pilots and seven fishermen flying to a fish camp. En route, the crew encountered engine problems and elected to return to Khabarovsk. Unable to maintain a safe altitude, the crew attempted to carry out an emergency landing when the airplane impacted trees and crashed in a wooded area, coming to rest in a small river. All nine occupants were injured, five of them seriously. The aircraft was damaged beyond repair.

Crash of a PZL-Mielec AN-2R near Chernolesskoye: 1 killed

Date & Time: May 15, 2013 at 1034 LT
Type of aircraft:
Registration:
RA-31403
Flight Phase:
Survivors:
No
Schedule:
Chernolesskoye - Chernolesskoye
MSN:
1G197-26
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5437
Captain / Total hours on type:
2527.00
Aircraft flight hours:
8523
Aircraft flight cycles:
34391
Circumstances:
The pilot, sole on board, was performing a crop spraying flight on behalf of the 'Svoboda' Agricultural Cooperation in the region of Chernolesskoye. While flying at a height of about 9 metres, trying to get altitude, the single engine aircraft successively collided with power cables and a concrete pylon, continued for about 99 metres then crashed in an open field, bursting into flames. The aircraft was destroyed by impact forces and a post impact fire and the pilot was killed.
Probable cause:
The accident occurred during crop-dusting flight due to late aircraft entry into climb for flying over PTL resulted in aircraft collision with power transmission line tower on a field under cultivation, followed by ground impact and fire. Probably late aircraft entry into climb was caused by PIC performance impairment (final crop dusting in final flight was performed after which PIC had to rest during 1,5 hours and short recreation cycle was disordered during flight operation), and also low-observability of PTL wires without day marking.
Final Report:

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

Date & Time: Mar 23, 2013 at 1503 LT
Type of aircraft:
Operator:
Registration:
RA-02203
Flight Phase:
Survivors:
Yes
Schedule:
Vostochnaya - Vostochnaya
MSN:
1G234-34
YOM:
1989
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5536
Captain / Total hours on type:
2710.00
Copilot / Total flying hours:
61
Copilot / Total hours on type:
61
Aircraft flight hours:
3612
Aircraft flight cycles:
16267
Circumstances:
The crew was engaged in a crop spraying flight on agricultural field in Vostochnaya, about 70 km northeast of Krasnodar. The day prior to the accident, the engine failed in flight and the crew made a forced landing in a field. As the carburetor was broken, it was replaced and an engine test run was performed. On 23 March, one minute after takeoff, while climbing to a height of 30 metres, the engine failed again. The crew attempted an emergency landing when the aircraft stalled and crashed in the Bakhotinski Lake, coming to rest upside down. The copilot escaped with minor injuries while the captain was killed. The wreckage was recovered three days later.
Probable cause:
The accident was caused by its nosing during the emergency landing on water surface. The emergency landing was caused by the engine power loss and flameout in the air due to the destruction of the exhaust collector can type combustor and burn through of the carburetor intake valve followed by high temperature burnt gases ingestion into the engine carburetor intake. The destruction of the exhaust collector can type combustor most probably occurred on the corrosion mechanism energized in conditions of the material heat during the engine operation using motor petrol. Power factor resulted in initial crack formation most probably was caused by residual tenses in the material of manufacture origine caused during can type combustor manufacture. In accordance with the passport the latest can type combustor overhaul was performed on January 27, 2009 in "Shakhtinsky ARZ DOSSAAF" CJSC. The commission didn't find the actual confirmation of the can type combustor overhaul as the marking at the single remained label indicates that the specified section had overhaul at the plant n° 420GA in October 1983.
Final Report: