Country
Operator Image

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.

Crash of a PZL-Mielec AN-2PF near Kalga

Date & Time: Sep 21, 1992
Type of aircraft:
Operator:
Registration:
CCCP-32596
Flight Phase:
Survivors:
Yes
MSN:
1G105-10
YOM:
1969
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
13879
Aircraft flight cycles:
12825
Circumstances:
Crashed in unknown circumstances 11 km from Kalga Airstrip. There were no casualties.

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

Date & Time: Aug 29, 1992
Type of aircraft:
Operator:
Registration:
CCCP-65810
Survivors:
Yes
MSN:
3 35 22 01
YOM:
1973
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
51
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
26173
Aircraft flight cycles:
18701
Circumstances:
For unknown reasons, the aircraft landed too far down the runway at Kharkiv-Osnova Airport. Unable to stop within the remaining distance, it overran and came to rest. All 58 occupants escaped uninjured while the aircraft was considered as damaged beyond repair.

Crash of a Tupolev TU-134A in Ivanovo: 84 killed

Date & Time: Aug 27, 1992 at 2244 LT
Type of aircraft:
Operator:
Registration:
CCCP-65058
Survivors:
No
Schedule:
Mineralnye Vody - Donetsk - Ivanovo
MSN:
49868
YOM:
1977
Flight number:
SU2808
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
77
Pax fatalities:
Other fatalities:
Total fatalities:
84
Aircraft flight hours:
26307
Aircraft flight cycles:
16388
Circumstances:
The aircraft departed Mineralnye Vody on a schedule service to Ivanovo with an intermediate stop in Donetsk. Following an uneventful flight, the crew initiated the descent to Ivanovo-Yuzhny Airport. The visibility was limited due to the night and poor weather conditions. On final approach, the aircraft was not properly aligned on the glide and the copilot and the navigator attempted to inform the captain about the deviation but without success. The captain continued the approach in a wrong configuration when, at a speed of 370 km/h and a rate of descent of 6 metres per second, the left wing struck a residential building. The aircraft entered a nose-down attitude and crashed 512 metres further, some 2,450 metres short of runway 29, bursting into flames. The aircraft was totally destroyed and all 84 occupants were killed.
Probable cause:
The accident was the consequence of a wrong approach configuration on part of the crew. The captain ignored several alerts from the copilot and the navigator and failed to initiate a go-around procedure despite the GPWS alarm sounded for about 10 seconds. The following contributing factors were reported:
- Loss of altitude control in adverse weather conditions following a premature descent,
- The crew failed to follow the published approach procedures, which resulted in the aircraft approaching the airport at an insufficient altitude and at an excessive speed,
- The 4th turn was completed too late at a distance less than calculated, which caused the aircraft to deviate from the approach path with a separation (deviation) of 1,900 metres to the right of the approach path at a distance of 8,600 metres from the runway threshold at an altitude of 500 metres,
- The captain decided to continue the approach while a landing was obviously impossible,
- A total interruption of interactions within the crew during the approach procedure, which brang the captain in a delicate situation without any assistance from the other members of the crew and causing a regular loss of the altitude control,
- The crew let the aircraft passing the admissible vertical speed during the final approach,
- Failure of the crew to initiate a go-around procedure while the Ground Proximity Warning System alarm sounded for about 10 seconds,
- Excessive corrective maneuvers on part of the captain which caused the aircraft to enter a roll angle greater than the permissible limits,
- The violation by the crew of the approach pattern was facilitated by the lack of assistance from ATC at Ivanovo Airport.