Crash of an Airbus A310-308 near Mezhdurechensk: 75 killed

Date & Time: Mar 23, 1994 at 0057 LT
Type of aircraft:
Operator:
Registration:
F-OGQS
Flight Phase:
Survivors:
No
Schedule:
Moscow - Hong Kong
MSN:
596
YOM:
1991
Flight number:
SU593
Country:
Region:
Crew on board:
12
Crew fatalities:
Pax on board:
63
Pax fatalities:
Other fatalities:
Total fatalities:
75
Captain / Total flying hours:
9675
Captain / Total hours on type:
38.00
Copilot / Total flying hours:
5855
Copilot / Total hours on type:
440
Aircraft flight hours:
5375
Aircraft flight cycles:
846
Circumstances:
While cruising by night at the assigned altitude of 10,100 metres, approaching the Novokuznetsk reporting point, the captain's daughter entered the cockpit. She was allowed to sit the left-hand seat while the captain demonstrated some autopilot features, using HDG/S and NAV submodes to alter the heading. The captain's son then took the left front seat. The captain intended to demonstrate the same manoeuvre when his son asked if he could turn the control wheel. He then turned the wheel slightly (applying a force of between 8-10 kg) and held it in that position for a few seconds before returning the wheel to the neutral position. The captain then demonstrated the same features as he did to his daughter and ended by using the NAV submode to bring the aircraft back on course. As the autopilot attempted to level the aircraft at its programmed heading, it came in conflict with the inputs from the control wheel which was blocked in a neutral position. Forces on the control wheel increased to 12-13 kg until the torque limiter activated by disconnecting the autopilot servo from the aileron control linkage. The autopilot remained engaged however. The aircraft then started to bank to the right at 2,5° per second, reaching 45° when the autopilot wasn't able to maintain altitude. The A310 started buffeting, which caught the attention of the captain who told the copilot to take control while he was trying to regain his seat. The seat of the copilot was fully aft, so it took him an additional 2-3 seconds to get to the control wheel. The bank continued to 90°, the aircraft pitched up steeply with +4,8g accelerations, stalled and entered a spin. Two minutes and six seconds later the aircraft struck the ground. The aircraft disintegrated on impact and all 75 occupants were killed, among them 25 foreigners.
Probable cause:
The accident was caused by a stall, spin and impact with the ground resulting from a combination of the following factors:
1. The decision by the PIC to allow an unqualified and unauthorized outsider (his son) to occupy his duty station and intervene in the flying of the aeroplane.
2. The execution of demonstration manoeuvres that were not anticipated in the flight plan or flight situation, with the PIC operating the autopilot while not at his duty station.
3. Application by the outsider and the co-pilot of control forces that interfered with the functioning of the roll channel of the autopilot (and are not recommended in the A310 flight manual), thus overriding the autopilot and disconnecting it from the aileron control linkage.
4. The copilot and PIC failed to detect the fact that the autopilot had become disconnected from the aileron control linkage, probably because:
- The A310 instrumentation has no declutch warning. The provision of signals in accordance with the requirements of Airworthiness Standard NLGS-3, para. 8.2.7.3., and international recommended practices, could have enabled the crew to detect the disengaged autopilot in a timely manner.
- The copilot and PIC may have been unaware of the peculiarities of the declutching function and the actions to be taken in such a situation because of a lack of appropriate information in the flight manual and crew training programme;
- It was difficult for the co-pilot to detect the disengagement of the autopilot by feel, either because of the small forces on his control column or because he took changing forces to be the result of Eldar's actions;
- The PIC was away from his position and distracted by the conversation with his daughter.
5. A slight, unintentional further turn of the control wheel(s) following disengagement of the autopilot caused a right roll to develop.
6. The PIC and copilot failed to detect the excessive right bank angle, which exceeded operating limits, and were late in re-entering the aircraft control loop because their attention was focussed on determining why the aircraft had banked to the right, a manoeuvre they interpreted as entry into a holding area with either no course line or with a new (false) course line generated on the navigational display.
A strong signal indicating that the aeroplane had exceeded the allowable operating bank angle, taking account of the delay in recognizing and assessing the situation and making a decision, could in this situation have attracted the crew's attention and enabled them to detect the bank at an earlier stage.
7. The aeroplane was subjected to buffeting and high angles of attack because the autopilot continued to perform its height-keeping function even after the actuator declutched and as the right roll developed, until the pilot disconnected it by overriding its longitudinal channel.
8. Inappropriate and ineffective action on the part of the copilot, who failed to disconnect the autopilot and to push the control column forward when the buffeting occurred and the aeroplane entered an unusual attitude (high angles of attack and pitch). These actions, which caused the aeroplane to stall and spin, could have resulted from:
- the presence of an outsider in the left-hand pilot's seat and the resulting delay before the PIC re-entered the aeroplane control loop;
- the less-than-optimum working posture of the copilot, whose seat was pushed back to its rearmost position;
- the occurrence, 2 seconds following the onset of buffeting, of an unintentional pitching up of the aeroplane, which sharply increased the angle of attack and reduced lateral controllability;
- unpreparedness of the crew to act in this situation because of lack of appropriate drills in the training programme;
- temporary loss of spatial orientation in night conditions.
Final Report:

Crash of an Antonov AN-12BP in Nalcik: 13 killed

Date & Time: Feb 24, 1994 at 1116 LT
Type of aircraft:
Operator:
Registration:
RA-11118
Flight Type:
Survivors:
No
Schedule:
Saint Petersburg - Volgograd - Nalcik
MSN:
01 348 002
YOM:
1971
Flight number:
FV9045
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
13
Circumstances:
The aircraft was completing a cargo flight from St Petersburg to Nalcik with an intermediate stop in Volgograd, carrying seven passengers, six crew members and a load of 12,5 tons of coins minted in St Petersburg. On final approach, at a distance of 8 km from the airport, at a speed of 260 km/h, flaps were selected down to an angle of 35°. Thirty seconds later, the aircraft started to pitch up and down then nosed up to an angle of 15°. It entered an uncontrolled descent and crashed at a speed of 414 km/h in a nose down angle of 55° in an open field located 4,5 km short of runway threshold. The aircraft disintegrated on impact and all 13 occupants were killed.
Probable cause:
It was determined that the loss of control was the consequence of an excessive accumulation of ice on stabilizers. Information transmitted to the crew regarding weather conditions at destination did not reflect the actual situation and did not mention any icing conditions.

Crash of an Antonov AN-12B in Anadyr

Date & Time: Feb 8, 1994 at 2336 LT
Type of aircraft:
Operator:
Registration:
CCCP-11340
Flight Type:
Survivors:
Yes
Schedule:
Khatanga - Anadyr
MSN:
00 347 504
YOM:
1970
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was performing a night cargo flight from Khatanga to Anadyr, carrying five passengers, six crew members and a load of vodka. The approach was completed in poor visibility due to heavy snow falls. Too high on the glide, the aircraft landed too far down the runway and was unable to stop within the remaining distance. It overran and came to rest in a ravine. All 11 occupants escaped with minor injuries and the aircraft was destroyed.
Probable cause:
Wrong approach configuration on part of the crew who should initiate a go-around as the aircraft was too high on the glide.

Crash of an Antonov AN-24B in Omsukchan

Date & Time: Feb 1, 1994 at 1616 LT
Type of aircraft:
Operator:
Registration:
RA-47718
Flight Phase:
Survivors:
Yes
Schedule:
Magadan - Omsukchan - Susuman - Magadan
MSN:
69900701
YOM:
1966
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
48
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
38294
Aircraft flight cycles:
29173
Circumstances:
During the takeoff roll, at a speed of 170 km/h, the aircraft deviated to the right and collided with a snow bank. It cartwheeled and came to rest. While all 53 occupants evacuated safely, the aircraft was damaged beyond repair.
Probable cause:
It was determined that the runway surface was contaminated with snow and has not been cleared prior to takeoff. It was also reported that the runway lights and edge markings were not clearly visible due to snow.

Crash of an Antonov AN-22 in Antonovo: 7 killed

Date & Time: Jan 19, 1994
Type of aircraft:
Operator:
Registration:
RA-09331
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Hahn - Tver - Voronezh
MSN:
02340408
YOM:
1972
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
After takeoff from Tver-Migalovo AFB, while climbing, the crew reported control problems. The aircraft rolled to the right and crashed near Antonovo, 16 km southwest of Tver AFB. Three occupants were seriously injured while seven others were killed.
Probable cause:
The accident was caused by the failure of an aileron control rod. Nevertheless, representatives from Antonov disagreed, stating icing caused the loss of control.

Crash of a Tupolev TU-154 in Irkoutsk: 125 killed

Date & Time: Jan 3, 1994 at 1207 LT
Type of aircraft:
Operator:
Registration:
RA-85656
Flight Phase:
Survivors:
No
Schedule:
Irkutsk - Moscow
MSN:
89A801
YOM:
1989
Flight number:
BKL130
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
115
Pax fatalities:
Other fatalities:
Total fatalities:
125
Circumstances:
While preparing the flight, the crew encountered technical problems with the engine n°2 and 17 minutes were necessary to start all three engines. A technical issue occurred with the starter of the engine n°2 and a warning light came on in the cockpit. The crew did not find any corrective actions in the operations manual and as he thought the warning was false, decided to take off. Four minutes after the aircraft departed Irkutsk Airport runway 12, while climbing, the starter located in the engine n°2 failed. Debris scattered around and hydraulic and fuel lines were cut. The crew declared an emergency and was cleared for an immediate return after the engine n°2 caught fire. Unfortunately, the crew was unable to extinguish the fire and the aircraft entered an uncontrolled descent and eventually crashed on farm buildings located about 11 km from the airport. The aircraft disintegrated on impact and all 124 occupants were killed as well as one farmer. Another farmer was seriously injured.
Probable cause:
The commission found that the air starter malfunction occurred when the engine was started due to a structural element of the air conditioning system, probably a fragment of the air-to-air radiator (VVR) splitter of engine n°2, hit under the constant pressure flap. This became possible due to the lack of protection against the ingress of foreign objects from the air lines and the low operational reliability of the VVR. A constant supply of air under pressure from the engines operating at a mode close to the nominal through an open damper led to the starter not switching off and the turbine rotor spinning up to off-design speed with the alarm "Dangerous starter speed" being triggered, which was detected by the flight engineer after starting all the engines. Pressing the starter shutdown button did not turn off the alarm. There were no other signs of failure other than the operation of the warning lamp. The crew, believing that the alarm was false, made the wrong decision to take off, which was a consequence of the unwillingness to act in such a situation due to shortcomings in the regulatory documentation, information support, as well as insufficient information content of the starter's technical condition monitoring system in the cockpit. Laying the mains of all three hydraulic systems through the fire-hazardous compartment of the engine n°2 is a constructive disadvantage of the Tu-154M aircraft.

Crash of a Tupolev TU-154B-2 in Grozny

Date & Time: Dec 25, 1993 at 1229 LT
Type of aircraft:
Operator:
Registration:
RA-85296
Survivors:
Yes
Schedule:
Moscow - Grozny
MSN:
78A296
YOM:
1978
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
165
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Moscow, the crew completed the approach to Grozny in poor weather conditions. The aircraft landed nose first, causing it to be torn off. The aircraft slid on the ground for few dozen metres before coming to rest. All 172 occupants evacuated safely while the aircraft was written off.

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

Date & Time: Dec 22, 1993
Type of aircraft:
Operator:
Registration:
CCCP-01410
Flight Phase:
Survivors:
Yes
MSN:
1G230-50
YOM:
1988
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The engine failed in flight, forcing the crew to attempt an emergency landing. The aircraft collided with trees and crashed in a wooded area located 190 km from Uray. All 10 occupants were slightly injured and the aircraft was destroyed.
Probable cause:
Engine failure for unknown reasons.

Crash of a PZL-Mielec AN-2 in Vorogovo

Date & Time: Dec 14, 1993
Type of aircraft:
Operator:
Registration:
RA-62599
Flight Phase:
Survivors:
Yes
MSN:
1G177-46
YOM:
1978
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Caught fire while taking off from Vorogovo. All 16 occupants escaped uninjured while the aircraft was destroyed.

Crash of a Beriev BE-12NKh off Yuzhno-Kurilsk

Date & Time: Oct 31, 1993
Type of aircraft:
Registration:
82 yellow
Survivors:
Yes
Schedule:
Yuzhno-Sakhalinsk - Yuzhno-Kurilsk
MSN:
9 6 017 02
YOM:
1969
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Yuzhno-Kurilsk, the crew realized that the sea was relatively rough with waves of 1,5 meter. Despite the situation, the crew decided to land in the bay. After touchdown, the right float was torn off and the aircraft rolled to the right and came to rest 120 metres offshore, partially submerged. All 20 occupants were rescued while a rescuer died from hypothermia. The aircraft partially sank as the fuselage was cut in several places after suffering chocks with water.