Country
Operator Image

Crash of an Antonov AN-124-100 in Torino: 4 killed

Date & Time: Oct 8, 1996 at 1050 LT
Type of aircraft:
Operator:
Registration:
RA-82069
Flight Type:
Survivors:
Yes
Site:
Schedule:
Moscow - Torino - Abu Dhabi - Bandar Seri Begawan
MSN:
977305591
YOM:
1993
Flight number:
SU9981
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total hours on type:
431.00
Circumstances:
The aircraft departed Moscow-Chkalovsky Airport bound for Torino, carrying 19 passengers and four crew members. The aircraft should be loaded with Ferrari cars to be delivered in Bandar Seri Begawan, Brunei, following a fuel stop at Abu Dhabi Airport. While descending to Torino-Caselle Airport, the crew was informed about the weather conditions at destination: wind variable at 3 knots, visibility 2,000 metres, RVR runway 36 more than 1,500 metres, light rain, scattered at 1,500 feet, scattered at 3,500 feet, broken at 7,000 feet, OAT and dew point 13°C, QNH 1012. On final approach to runway 36, the crew was unable to establish a visual contact with the runway and the captain decided to initiate a go-around procedure. Unfortunately, this decision was taken too late. While climbing, the aircraft struck trees and crashed onto houses located in the village of San Francesco al Campo, about one km from the runway end. The aircraft, a house and a barn were destroyed. Both pilots, two people on the ground and 20 cows in the barn were killed.
Probable cause:
The following findings were reported:
- Weather conditions were marginal,
- At the time of the accident, the runway length was 2,350 metres instead of 3,300 metres due to work in progress,
- The ILS CAT III system was inoperative during work in progress,
- The pilots were warned that the crew of an aircraft that landed on the same runway 36 about 11 minutes earlier established a visual contact with the runway at an altitude of 200 feet only,
- The crew continued the approach below MDA without establishing visual contact with the runway,
- Poor crew coordination,
- Poor approach planning,
- The crew failed to follow the approach checklist,
- The crew did not divide up the tasks in a correct manner,
- The crew did not prepare for a possible go-around procedure,
- The decision of the captain to initiate a go-around procedure was taken too late,
- The crew encountered engine trouble after the power levers were suddenly moved,
- The relative low experience of the captain on this type of aircraft.

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

Date & Time: Jun 25, 1994
Type of aircraft:
Operator:
Registration:
CCCP-70263
Flight Phase:
Survivors:
Yes
MSN:
1G139-22
YOM:
1972
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During initial climb, the engine failed. The aircraft stalled and crashed, bursting into flames. All eight occupants escaped uninjured (or with minor injuries) while the aircraft was destroyed.
Probable cause:
Engine failure during climb out for unknown reasons.

Crash of a Let L-410UVP in Blagoveshchensk

Date & Time: Jun 14, 1994
Type of aircraft:
Operator:
Registration:
RA-67470
Flight Phase:
Survivors:
Yes
MSN:
84 12 35
YOM:
1984
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While taxiing at Blagoveshchensk-Ignatyevo Airport, the pilot was forced to make an evasive maneuver to avoid a collision with a bus. Doing so, the nose gear collided with a drainage ditch (25 cm deep) located on the left side of the taxiway. On impact, the nose gear collapsed and the aircraft came to rest. All 14 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a Tupolev TU-134A-3 in Arkhangelsk

Date & Time: May 7, 1994 at 1242 LT
Type of aircraft:
Operator:
Registration:
RA-65976
Survivors:
Yes
Schedule:
Moscow - Arkhangelsk
MSN:
3 35 20 07
YOM:
1973
Flight number:
SU2315
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
56
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
33606
Aircraft flight cycles:
21071
Circumstances:
On approach to Arkhangelsk-Talagi, the crew encountered technical problems with the landing gear that could not be lowered. Several manual attempts were made and finally, only the right main gear remained stuck in its wheel well. The captain decided to land in such configuration. After touchdown, the aircraft slid on the ground then veered off runway and came to rest in a grassy area. All 62 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The right main gear could not be lowered because of a breakage of the filling connection of the hydraulic tank due to metal fatigue while the aircraft was taxiing at Moscow-Sheremetyevo Airport. The fitting was blown out under pressure and damaged hydraulic lines, causing a hydraulic fluid leak and the oil pressure to drop.

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 Ilyushin II-86 in New Delhi: 4 killed

Date & Time: Mar 8, 1994 at 1200 LT
Type of aircraft:
Operator:
Registration:
RA-86119
Flight Phase:
Survivors:
Yes
Schedule:
New Delhi - Tashkent - Moscow
MSN:
51483209087
YOM:
1985
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
An Air Sahara (Sahara Airlines) boeing 737-2R4C registered VT-SIA was engaged in a local training flight at New Delhi-Indira Gandhi Airport, carrying one instructor and three trainee pilots. Five circuits and landings were completed uneventfully and during the sixth touch-and-go exercice, after take off from runway 28, the aircraft took a left turn and crashed on the international apron. The aircraft collided with an Aeroflot Ilyushin II-86 registered RA-86119 that was parked on the apron, bay n°45. Both aircraft were destroyed by fire. All four crew members on board the Boeing 737 were killed as well as four people on board the II-86 and one on the ground.
Probable cause:
Loss of control after rotation due to application of wrong rudder by trainee pilot during engine failure exercice. The instructor did not guard/block the rudder control and give clear commands as instructor so as to obviate the application of wrong rudder control by the trainee pilot.

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 Tupolev TU-154B in Yerevan

Date & Time: Dec 5, 1992
Type of aircraft:
Operator:
Registration:
CCCP-85105
Survivors:
Yes
MSN:
75A105
YOM:
1975
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
146
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach and landing to Yerevan-Zvartnots Airport was completed in poor weather conditions. Upon landing, the aircraft was not properly aligned with the centerline and landed too far to the right of the runway. Out of control, it veered off runway and eventually collided with a concrete wall. All 154 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
It was determined that the aircraft was not properly aligned with the runway centerline upon landing after the crew mistook the runway edge lights with the runway centerline lights.

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

Date & Time: Oct 14, 1992
Type of aircraft:
Operator:
Registration:
CCCP-07840
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
1G169-55
YOM:
1976
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances near Kostanay while completing a flight on behalf of the Kazakh government. All three occupants were injured and the aircraft was destroyed.