Crash of a Tupolev TU-134A in Sofia: 50 killed

Date & Time: Jan 10, 1984 at 1938 LT
Type of aircraft:
Operator:
Registration:
LZ-TUR
Survivors:
No
Schedule:
Berlin - Sofia
MSN:
4 35 23 08
YOM:
1974
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
45
Pax fatalities:
Other fatalities:
Total fatalities:
50
Circumstances:
The approach to Sofia-Vrazhdebna Airport was initiated by night and limited visibility due to snow falls. On short final, the crew descended below the glide when the aircraft struck successively power cables and tree tops and crashed in a wooded area located 4 km short of runway threshold, bursting into flames. The aircraft was destroyed and all 50 occupants were killed.
Probable cause:
The decision of the crew to continue the approach below the glide without any visual contact with the runway until impact with obstacles.

Crash of a Tupolev TU-134A in Tbilisi: 8 killed

Date & Time: Nov 18, 1983
Type of aircraft:
Operator:
Registration:
CCCP-65807
Survivors:
Yes
Schedule:
Tbilisi - Batumi - Kiev - Leningrad
MSN:
3352108
YOM:
1973
Flight number:
SU6833
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
59
Pax fatalities:
Other fatalities:
Total fatalities:
7
Aircraft flight hours:
13273
Aircraft flight cycles:
10506
Circumstances:
En route from Tbilisi to Batumi, while in cruising altitude, seven hijackers (young Georgian people) elected to divert the aircraft to Turkey. Hijackers opened fire in the cabin and cockpit but the copilot was able to make sharp maneuvers, forcing the hijacker to leave the cockpit. The crew was able to return to Tbilisi Airport where security forces stormed the aircraft. Seven occupants, three crew members and four passengers (among them three hijackers) were killed. At least 63 bullets holes were found in the fuselage and the aircraft was considered as damaged beyond repair due to serious deformation of the structure caused by excessive g loads during an emergency descent.
Probable cause:
Structural damages caused by excessives g loads and bullets holes due to hijacking situation.

Crash of a Tupolev TU-134A near Almaty: 90 killed

Date & Time: Aug 30, 1983 at 2017 LT
Type of aircraft:
Operator:
Registration:
CCCP-65129
Survivors:
No
Site:
Schedule:
Kazan - Chelyabinsk - Alma-Ata
MSN:
60630
YOM:
1978
Flight number:
SU5463
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
84
Pax fatalities:
Other fatalities:
Total fatalities:
90
Aircraft flight hours:
9976
Aircraft flight cycles:
6515
Circumstances:
Following an uneventful flight from Chelyabinsk at an altitude of 10,200 meters, the crew was cleared to initiate the approach to Alma-Ata Airport in view of a landing on runway 05. By night, the crew was instructed to initiate a left turn and to descend to an altitude of 600 meters after being informed of an II-62 approaching eight km right of their position. As the aircraft was too low, the GPWS warning sounded in the cockpit. For unknown reasons, the crew failed to react promptly and initiated a corrective maneuver 23 seconds later. The aircraft nosed up to an angle of 14° then turned left to an angle of 11-12° when it struck two seconds later the slope of Mt Dolan (690 meters high) located about 36 km west of Almaty Airport. The aircraft disintegrated on impact and all 90 occupants were killed. The wreckage was found 24 meters below the summit.
Probable cause:
It was determined that the crew failed to prepare the approach maneuver according to published procedures. ATC failed to assist the crew properly and transmitted wrong instructions, causing the airplane to descent prematurely to the unsafe altitude of 600 meters and outside the approach diagram. The crew failed to be proactive when the GPWS alarm sounded and a corrective action was taken too late. It was also reported that the phraseology used by the pilots was non standard.

Crash of a Tupolev TU-134A in Yerevan

Date & Time: Jun 17, 1983
Type of aircraft:
Operator:
Registration:
CCCP-65657
Survivors:
Yes
Schedule:
Simferopol - Yerevan
MSN:
0 35 11 03
YOM:
1970
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
62
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
17870
Aircraft flight cycles:
11029
Circumstances:
En route from Simferopol to Yerevan, while cruising at an altitude of 10,200 meters over the city of Gali in Abkhazia, the crew spotted CB's at high altitude but failed to modify his route. The aircraft went into the CB's and encountered severe turbulences. The crew was able to continue the flight within further incident and to land at Yerevan Airport. After being parked on apron, the aircraft was inspected and it was later confirmed that it sustained severe structural damages after it recorded excessive G loads (+3.05/-0.65). There were no casualties but the aircraft was considered as damaged beyond repair.
Probable cause:
In-flight structural damages caused by severe atmospheric turbulences.

Crash of a Tupolev TU-134A in Sukhumi

Date & Time: Aug 14, 1982 at 1809 LT
Type of aircraft:
Operator:
Registration:
CCCP-65836
Flight Phase:
Survivors:
Yes
Schedule:
Sukhumi - Moscow-Vnukovo
MSN:
17113
YOM:
1974
Flight number:
SU974
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
76
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
17003
Aircraft flight cycles:
10406
Circumstances:
At 1808LT, the crew was cleared for takeoff from Sukhumi-Babushara runway 02. During the takeoff run, 26 seconds after it started to roll, at a speed of 195 km/h, the crew sighted a Let L-410M entering the runway. Registered CCCP-67191, the Let L-410 was engaged in a scheduled service (flight SU73G) to Kutaisi with two pilots and nine passengers on board. The captain of the Tupolev decided to abandon the takeoff maneuver and initiated an emergency braking procedure. Spoilers were deployed and revers systems were activated. He elected to turn to the left to reach an exit taxiway. In the same time, the crew of the Let saw the Tupolev coming from their right and increased engine power to move forward. Seven seconds after the crew of the Tupolev rejected takeoff, at a speed of 216 km/h, the right wing of the Tupolev struck the Let that was destroyed upon impact. The Tupolev rolled for about 514 meters then veered off runway to the left and came to rest 48 meters to the left of its centerline. All 82 people on board the TU-134 escaped uninjured while all 11 people on board the Let were killed.
Probable cause:
It was determined that the collision was the consequence of a series of errors made by the crew of the Let L-410 who failed to follow ATC and ground controllers instructions regarding taxiing procedures prior to takeoff, which led them to enter the runway when he was not authorized to do so. A poor management in flights organization at Sukhumi Airport remains a contributing factor as well as few procedures violation on the part of ATC and ground controllers, among others concerning the use of a non-standard phraseology which may create confusion to the crew.

Crash of a Tupolev TU-134IK at Severomorsk-Safonovo NAS: 15 killed

Date & Time: Jun 17, 1982
Type of aircraft:
Registration:
CCCP-65687
Flight Type:
Survivors:
Yes
Schedule:
Moscow - Severomorsk
MSN:
62400
YOM:
1979
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
15
Circumstances:
The aircraft departed Moscow-Zhukovsky Airport on a flight to Severomorsk-Safonovo NAS, carrying 16 people. On approach, the crew encountered bad weather conditions and the visibility was poor. On final, the Ground Proximity Warning System (GPWS) alarm sounded in the cockpit, informing the pilot his altitude was too low. The navigator also informed the captain that the aircraft deviated from the approach path to the left by one km but the captain ignored these messages as well as ATC instructions. At an altitude of 206 meters, the left wing struck an electric pole. The aircraft lost height and crashed, bursting into flames. The captain survived and was slightly injured while 15 other occupants were killed.
Probable cause:
The captain failed to follow the approach procedures and ignored ATC instructions as well as GPWS and other crew member warnings. In such conditions, he led the aircraft deviating from the approach path and descending below the minimum safe altitude until impact.

Crash of a Tupolev TU-134A in Simferopol

Date & Time: Jun 28, 1981
Type of aircraft:
Operator:
Registration:
CCCP-65871
Survivors:
Yes
Schedule:
Kiev - Simferopol
MSN:
28311
YOM:
1975
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
59
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
11492
Aircraft flight cycles:
8206
Circumstances:
Brakes and tires overheated during a pre-takeoff inappropriate taxiing manoeuvre at Kiev-Borispol Airport. During the takeoff roll at Borispol Airport, at a speed of 135 km/h, the crew was instructed to abandon the takeoff as he did not receive any clearance. The crew interrupted the procedure and was later cleared for a second departure. During this manoeuvre, brakes and tires overheated again. Upon touchdown at Simferopol Airport, a tire located on the right main gear exploded. Debris struck the lower part of the right wing and punctured a fuel tank. Fuel spilled and a fire erupted. The crew was able to stop the plane on the runway and all 65 occupants were evacuated, among them 29 passengers were injured. The aircraft was partially destroyed by fire.
Probable cause:
A tire burst on landing after overheating during an abandoned takeoff and taxi procedure at Kiev-Borispol Airport. A poor flight preparation and a lack of crew training were considered as contributing factors.

Crash of a Tupolev TU-134B in Sochi

Date & Time: Jan 6, 1981
Type of aircraft:
Operator:
Registration:
CCCP-65698
Flight Type:
Survivors:
Yes
Schedule:
Sukhumi - Sochi
MSN:
63325
YOM:
1980
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
1416
Aircraft flight cycles:
901
Circumstances:
The day prior to the accident, the aircraft was supposed to fly from Riga to Sochi but the flight was diverted to Sukhumi due to poor weather at destination. On the morning of January 6, the crew completed a positioning flight from Sukhumi to Sochi-Adler without any passengers on board. Following a wrong approach configuration, the aircraft landed at an excessive speed and after touchdown, the crew failed to use the brakes properly. Unable to stop within the remaining distance, the airplane overran and came to a halt. All six crew members escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the flying crew who failed to follow the approach checklist. The following contributing factors were reported:
- Flaps and undercarriage were deployed too late during the approach procedure,
- Excessive speed on approach and touchdown,
- After landing, the crew failed to use brakes according to published procedures,
- Poor crew coordination.

Crash of a Tupolev TU-134 in Warsaw

Date & Time: Jan 23, 1980
Type of aircraft:
Operator:
Registration:
SP-LGB
Survivors:
Yes
Schedule:
Brussels - Berlin - Warsaw
MSN:
8 35 06 03
YOM:
1968
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown on runway 11 at Warsaw-Okecie Airport, the airplane was unable to stop within the remaining distance. It overran and struck a four meters high embankment. Upon impact, the right wing was torn off and the airplane came to rest in flames. There were no casualties while the aircraft was written off. The aircraft was christened 'Władysław Reymont'.

Crash of a Tupolev TU-134A near Kurilovka: 94 killed

Date & Time: Aug 11, 1979 at 1335 LT
Type of aircraft:
Operator:
Registration:
CCCP-65816
Flight Phase:
Survivors:
No
Schedule:
Chelyabinsk - Voronezh - Kichinev
MSN:
4 35 22 10
YOM:
1974
Flight number:
SU7628
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
88
Pax fatalities:
Other fatalities:
Total fatalities:
94
Aircraft flight hours:
12739
Aircraft flight cycles:
7683
Circumstances:
The airplane departed Voronezh Airport at 1254LT on the last leg of a flight from Chelyabinsk to Kishinev, Moldavia, carrying 88 passengers and a crew of six. At 1317LT, the airplane entered the Kharkiv ARTCC at an altitude of 8,400 meters. The crew requested several times the permission to climb to 9,600 meters but this was denied due to heavy traffic. Eight minutes later, a second Aeroflot Tupolev TU-134AK entered the same ARTCC at an altitude of 5,700 meters. Registered CCCP-65735, it was completing flight SU7880 from Tashkent to Minsk with an intermediate stop in Donetsk. On board were 77 passengers and a crew of seven, among them all staff from the Pakhtakor Tashkent Football Team who should play against the Dynamo Minsk Team in two days. The crew of the second TU-134 was first cleared to climb to 7,200 meters and later to 8,400 meters. The air traffic controller miscalculated the distance and timing between both aircraft. About 90 seconds later, at an altitude at 8,400 meters but on crossing airways, both airplanes collided at an angle of 95° from each other. The right wing of CCCP-65735 struck the cockpit of CCCP-65816. Both aircraft spiralled to the ground, partially disintegrated in the air and eventually crashed in fields located around the villages of Kurilovka, Nikolaevka and Elizavetovka, about 35 km northwest of Dnipropetrovsk. Debris were found on a large area and none of the 178 occupants survived the accident.
Probable cause:
The in-flight collision was the consequence of multiple errors on part of the Air Traffic Controller and his instructor in charge of the Kharkiv Southwest Sector. The following factors were reported:
- Violations of the published procedures,
- Poor assistance and negligence on part of ATC in level assignment,
- Non compliance with requirements and regulations in force on part of ATC,
- Non compliance with standard radio phraseology,
- Lack of coordination,
- Intense traffic,
- Stress situation.