Tupolev · Single-aisle jet
Tupolev Tu-134
Is the Tupolev Tu-134 safe? It ranks #0 of 53 airliner families we rate, with 25 fatal accidents counted in about 18 million passenger flights.
How the score is built
- Fatal passenger accidents
- 25 in 18.1 million flights
1.4 fatal passenger accidents per million flights. Counted: passenger flights, accidents and unexplained losses; not counted: sabotage, hijackings, shoot-downs and deliberate crew acts.
- Full-loss equivalents
- 17.7
Each counted accident adds the share of people on board who died (1 = no survivors). This is what the score is based on.
- Flights flown
- 18.1 million
Estimated passenger departures. Passenger departures 1967 to 7 October 2026 from a fleet model: deliveries with a median passenger service life of about 22 years and about 1,599 departures per aircraft per year (average of similar types in OpenSky). OpenSky sees too few of these aircraft because they were retired before 2019. After 1991 capped by departures reported by the former Soviet republics (World Bank). Uncertainty roughly ±50%.
- Technology generation
- Gen 2 jet (integrated autoflight, analogue cockpit)
Small fleets are pulled toward the record of their generation: 0.88 full-loss equivalents per million flights over 236 million flights. Weight of this family's own record: 86%.
- Last fatal passenger accident
- 20 June 2011
RusLine, lsf RusAir, 1 km S of Petrozavodsk Airport (PES), Russia: 47 of 52 people on board died.
- Hull losses
- 71
Civil aircraft destroyed or written off from all causes, including non-fatal accidents, cargo flights and attacks; airframes flown by air forces on military operations are left out (context only, not in the score).
Compared with everyday risks
One flight on the Tupolev Tu-134 carries about the same risk of death as the activities near it below.
- An hour's walk1 in 14 million
- Driving 100 miles (160 km)1 in 5.9 million
- A day of skiing1 in 1.3 million
- One flight on the Tupolev Tu-134This aircraft1 in 1 million
- An ordinary day: accidents and violence1 in 1 million
- A scuba dive1 in 500,000
- Cycling 100 miles (160 km)1 in 430,000
- Running a marathon1 in 290,000
- A skydive1 in 250,000
- A general anaesthetic1 in 100,000
- Riding a motorbike 100 miles (160 km)1 in 83,000
Accident history
25 fatal accidents count toward the score, with 1,303 people on board killed.
| Date | Flight | Killed | What happened |
|---|---|---|---|
| RusLine, lsf RusAirTu-134A-3 · 1 km S of Petrozavodsk Airport (PES), Russia | 47 / 52 on board | On approach to Petrozavodsk in fog worse than the minimums, the crew descended below the safe altitude without seeing the lights, struck trees and came down on a highway. The navigator was found to be mildly drunk and crew coordination was poor.Type: Flight into terrainASN record | |
| UTair AviationTu-134A-3 · Samara Airport (KUF), Russia | 6 / 57 on board | Approaching Samara in fog far below minimums, which weather staff failed to relay, the crew went below decision height without seeing the lights. The aircraft touched down hard 300 m short and right of the runway, lost its left wing and overturned.Type: Landed short or longASN record | |
| Vietnam Airlines VN815Tu-134B-3 · Phnom Penh-Pochentong Airport (PNH), Cambodia | 65 / 66 on board | In a sudden heavy downpour the captain pressed on below a safe height despite warnings from his crew; the jet hit palm trees, a late go-around failed and it crashed into rice fields about 300 m short of the runway. A one-year-old boy survived.Type: Landed short or longASN record | |
| Azerbaijan AirlinesTu-134B-3 · 3,8 km from Nakhichevan Airport (NAJ), Azerbaijan | 52 / 82 on board | Soon after takeoff the left engine failed and the crew shut down the good right engine by mistake. Without power, the aircraft crashed in a field while turning to avoid apartment blocks. The failed engine had run 30 hours with an unrepaired defect.Type: Engine failureASN record | |
| Harka Air Services, lsf Komi AviaTu-134A · Lagos-Murtala Muhammed Airport (LOS), Nigeria | 16 / 80 on board | Landing at Lagos in heavy rain and low cloud, the aircraft touched down long, overran the runway and hit a concrete culvert 500 m beyond the end.Type: Runway excursionASN record | |
| Aeroflot, Central Region Civil Aviation DirectorateTu-134A · 3 km SE of Ivanovo Airport (IWA), Russia | 84 / 84 on board | On an unstable approach in drizzle and low cloud, the captain disregarded his navigator's advice and a GPWS warning, then made a steep corrective turn that raised the sink rate; the jet hit trees nearly 3 km short of the runway.Type: Flight into terrainASN record | |
| Aeroflot, North Kavkaz Civil Aviation DirectorateTu-134A · 3 km E of Pervouralsk, Russia | 27 / 71 on board | In cruise a fire broke out under the rear cargo hold floor, probably from a wiring short. As the crew descended, electrics and instruments failed, and they force-landed in a snowy field, striking irrigation equipment.Type: FireASN record | |
| Hâng Không ViêtnamTu-134A · 6 km N of Bangkok-Don Muang International Airport (BKK), Thailand | 76 / 90 on board | Approaching in thunderstorms, the aircraft was below the minimum altitude over the outer marker and struck the ground, breaking up over 500 m.Type: Flight into terrainASN record | |
| Aeroflot / BelarusTu-134AK · Surgut Airport (SGC), Russia | 20 / 51 on board | Flying a non-standard approach in cloud, the crew flew the opposite course to their clearance, lost sight of the runway and went below decision height; the aircraft hit the ground beside the runway, broke up and burned.Type: Flight into terrainASN record | |
| Aeroflot / BelarusTu-134A · 3 km NE of Berlin-Schönefeld Airport (SXF), Germany | 72 / 82 on board | The radio operator misheard a notice that runway 25R was closed as a landing clearance for it. Swinging between the parallel runways with power unchanged, the Tu-134 sank well below the glide slope and hit trees 3 km short.Type: Flight into terrainASN record | |
| Aeroflot, North Kavkaz Civil Aviation DirectorateTu-134A · Kuybyshev Airport (KUF), Russia | 70 / 94 on board | The captain flew the approach with his window blinds closed as unauthorised training, and the crew did not stop him. The blinds opened a second before touchdown; the jet hit the runway at about 4.8 g, a wing failed, it rolled over and burned.Type: Hard landing or abnormal runway contactASN record | |
| Aeroflot, Komi Civil Aviation DirectorateTu-134AK · Kopsa, Russia | 54 / 94 on board | Smoke was reported from the rear cargo hold soon after take-off. As it filled the cabin the crew descended and attempted a forced landing in low cloud and rain, striking trees in a forest. Hazardous items in a passenger's luggage were suspected.Type: FireASN record | |
| Aeroflot, Privolzhsk Civil Aviation DirectorateTu-134A · Penza Airport (PEZ), Russia | 1 / 59 on board | The crew abandoned the take-off at 246 km/h, citing low thrust and a false engine vibration warning, but began braking late. The Tu-134 ran off the end and down into a ravine. The one fatality was a passenger who suffered a heart attack.Type: Runway excursionASN record | |
| Aeroflot / EstoniaTu-134A · near Zolochiv, Ukraine | 79 / 79 on board | Descending towards Lviv at about FL130, the Tu-134 collided head-on with a military An-26 that had just taken off. Civil and military controllers had misjudged where both aircraft were.Type: Mid-air collisionASN record | |
| Aeroflot / BelarusTu-134AK · 10 km E of Minsk-2 International Airport (MSQ), Belarus | 58 / 80 on board | Ice that had formed on the wings broke away on take-off and was swallowed by the rear-mounted engines. Both flamed out within about a minute; the Tu-134 came down in woodland and caught fire.Type: IcingASN record | |
| Balkan Bulgarian AirlinesTu-134A · 4 km from Sofia-Vrazhdebna Airport (SOF), Bulgaria | 50 / 50 on board | In heavy snow, the crew went below decision altitude trying to spot the runway. They began a go-around at 80-100 m, but the Tu-134 struck a power line and came down in woods 4 km from the runway.Type: Flight into terrainASN record | |
| Aeroflot, Privolzhsk Civil Aviation DirectorateTu-134A · 36 km SW of Alma-Ata Airport (ALA), Kazakhstan | 90 / 90 on board | The Tu-134 began its descent towards Alma-Ata too early over mountains. The terrain warning went on for 23 seconds with no reaction; the crew then started a climbing turn, and moments later it hit Dolan Mountain.Type: Flight into terrainASN record | |
| Aeroflot / BelarusTu-134A · 2 km NE of Kurilovka, Ukraine | 84 / 84 on board | A controller put two Tu-134s on crossing airways at the same level, misjudging their separation; a late climb instruction was misheard. They collided in cloud at 8,400 m. This aircraft carried the Pakhtakor football team; 178 died in all.Type: Mid-air collisionASN record | |
| Aeroflot / MoldovaTu-134A · 3,5 km SE of Kurilovka, Ukraine | 94 / 94 on board | A controller put two Tu-134s on crossing airways at the same level after denying this flight a climb, and a late correction was misheard. They collided in cloud at 8,400 m and both broke up; 178 people died in all.Type: Mid-air collisionASN record | |
| Balkan Bulgarian AirlinesTu-134 · near Gabare, Bulgaria | 73 / 73 on board | After climbing to about 4,900 m, the Tu-134 went into an unexplained descent and hit the ground near Gabare. No cause is recorded.Type: Unknown causeASN record | |
| Malev Hungarian AirlinesTu-134 · 6,3 km SW of Urziceni, Romania | 29 / 53 on board | Cleared down to 600 m for a direct approach to Bucharest's main airport, the crew flew on reduced power and did not notice the Tu-134 gradually losing height until it hit flat ground.Type: Flight into terrainASN record | |
| InterflugTu-134 · Leipzig Airport (LEJ), Germany | 27 / 34 on board | On a precision radar approach to Leipzig, the controller stopped watching the final 3.2 km and the crew ignored their decision height. The Tu-134 sank below the glide path, hit the middle marker mast and rolled into the ground. Crew and controller were jailed.Type: Flight into terrainASN record | |
| Aeroflot / Armenia SU512Tu-134A · Amman-Marka International Airport (ADJ), Jordan | 2 / 85 on board | The captain wrongly believed an engine had failed and abandoned the takeoff above V1. The jet overran, went down a ravine and hit a concrete building; two crew and seven people inside the building died.Type: Runway excursionASN record | |
| Malev Hungarian AirlinesTu-134 · near Kiev-Borispol Airport (KBP), Ukraine | 49 / 49 on board | Nearing Kiev, a generator failure left the Tu-134 on battery power, and fog forced two missed approaches. The jet then crashed and broke up.Type: System failureASN record | |
| AviogenexTu-134A · Rijeka Airport (RJK), Croatia | 78 / 83 on board | Approaching Rijeka in heavy storms and turbulence, the Tu-134 was lifted above the glide path; the crew cut power and steepened the descent, then hit the runway hard on the right gear. The wing broke off and the jet flipped, slid and burned.Type: Hard landing or abnormal runway contactASN record |
Listed but not counted
These events did not happen on regular passenger flights or were caused by a crime or a deliberate act, which says little about the aircraft design.
| Date | Flight | Killed | Why not counted |
|---|---|---|---|
| Volga-AviaexpressTu-134A-3 · near Buchalki, Russia | 44 / 44 on board | Unlawful interference (sabotage, hijacking or shoot-down). Bombing. A suicide bomber detonated explosives in the cabin at about 8,100 m on the flight to Volgograd, causing decompression and break-up. A second airliner from Domodedovo was destroyed by another bomber almost simultaneously.Type: SecurityASN record | |
| MAP Zhukovski LIITu-134AK · Samoyliha, Shatura district, Russia | 8 / 8 on board | Not a scheduled passenger flight. Flight-test photo chase flight that collided at about 3,000 m with the Tu-22M3 research aircraft it was filming. The Tu-134 lost part of its tail and crashed into swampy forest; the Tu-22 landed safely.Type: Mid-air collisionASN record | |
| Transair GeorgiaTu-134A · Sukhumi-Babusheri Airport (SUI), Georgia | 1 / 30 on board | Unlawful interference (sabotage, hijacking or shoot-down). Attack on the ground during the Abkhazia war. While passengers were boarding at Sukhumi, separatists fired Grad rockets at the aircraft, which caught fire and burned out.Type: SecurityASN record | |
| Transair GeorgiaTu-134A · Sukhumi-Babusheri Airport (SUI), Georgia | 27 / 27 on board | Unlawful interference (sabotage, hijacking or shoot-down). Shoot-down. Abkhaz separatists fired a shoulder-launched heat-seeking missile from a patrol boat at the aircraft approaching Sukhumi; it went out of control and fell into the sea from about 300 m.Type: SecurityASN record | |
| República de MoçambiqueTu-134A-3 · near Komatipoort, South Africa | 34 / 44 on board | Not a scheduled passenger flight. Bringing President Samora Machel home from Zambia, the crew followed a wrong beacon, turned early and kept descending at night without seeing the ground, ignoring a long terrain warning. The Tu-134 hit hills inside South Africa; Machel was among the dead.Type: Flight into terrainASN record | |
| AeroflotTu-134 · Ufa Airport (UFA), Russia | 4 / 78 on board | Unlawful interference (sabotage, hijacking or shoot-down). During a stop at Ufa, two armed men on the run from police tried to take over the Tu-134 and shot two passengers dead before security forces killed them both. They had reportedly killed two policemen on the way to the airport.Type: SecurityASN record | |
| Soviet Air ForceTu-134Sh2 · near Donetsk, Ukraine | 7 / 7 on board | Military operation. The navigator school's Tu-134 hit strong turbulence in cruise; a backup yaw damper, cross-wired during military repairs, then cut in and sent false commands to the controls. Violent pitch and roll followed and the jet broke up in the air.Type: System failureASN record | |
| Aeroflot / GeorgiaTu-134A · Tbilisi Airport (TBS), Georgia | 7 / 66 on board | Unlawful interference (sabotage, hijacking or shoot-down). Nine hijackers stormed the cockpit and opened fire; the co-pilot threw the jet around to spoil their aim, overstressing it. They were driven out of the flight deck, the plane returned to Tbilisi and troops stormed it. Seven people died, including two hijackers.Type: SecurityASN record | |
| AeroflotTu-134 · Leningrad-Pulkovo Airport (LED), Russia | 1 / 57 on board | Unlawful interference (sabotage, hijacking or shoot-down). A man said his companion would set off a bomb unless the domestic flight went to London or Oslo. The crew pretended to stop in Finland but landed at Leningrad; when the ruse was spotted, guards stormed in, killing one hijacker and arresting the other.Type: SecurityASN record | |
| CSA Ceskoslovenské AerolinieTu-134A · Praha-Ruzyne International Airport (PRG), Czechia | 1 / 57 on board | Unlawful interference (sabotage, hijacking or shoot-down). A passenger attacked a flight attendant and tried to force the cockpit door, threatening to blow up the plane. He would not give up and was shot by onboard security, dying later.Type: SecurityASN record | |
| Ministry of Radio Equipment ProductionTu-134IK · near Severomorsk-1 Naval Air Station, Russia | 15 / 16 on board | Ferry flight without passengers. The Tu-134 testbed for anti-submarine equipment was positioning to a naval air station. On the ILS it sank below the glideslope and drifted left while the pilot ignored terrain alarms and warnings, then a wing hit a mast's guy wire on a hill.Type: Flight into terrainASN record | |
| Aeroflot / LatviaTu-134A · 1,5 km NE of Liepaya Airport (LPX), Latvia | 4 / 5 on board | Cargo flight. On a night cargo flight in snow and rain below minimums, the overloaded Tu-134 flew an unstable approach, sank under the glide slope and drifted right. Power came too late; it clipped trees and hit a railway embankment. The controller had cleared it despite the weather.Type: Flight into terrainASN record | |
| AviogenexTu-134A · Libreville Airport (LBV), Gabon | 8 / 8 on board | Cargo flight. The Tu-134 crashed while landing at Libreville on a cargo flight, killing all eight on board. No cause is recorded.Type: Unknown causeASN record | |
| Tupolev Design BureauTu-134 · near Chkalovsky, Russia | 8 / 8 on board | Test flight. During military trials of the second Tu-134 prototype, the pilot applied about 25 degrees of rudder without slowing down. The jet yawed hard, dived and crashed.Type: Loss of control in flightASN record |
The Tu-134 is close to extinct, and most of its record comes from Soviet-era flying. Up to 7 October 2026 it has 39 fatal events in our data. 25 count, in about 18 million passenger flights; 19 of those were before 1992, and the last was in 2011. Crews descending below safe heights, poor discipline in the cockpit and air traffic control errors explain most of them. Its record is weaker than that of the DC-9, its nearest Western counterpart, and Soviet-era flight counts are estimates.
What the Tu-134 is and where it still flies
The Tu-134 is a short-haul twinjet with two engines at the tail, a T-tail and, on most versions, a glazed nose for the navigator. Its main gear folds into pods behind the wing, like the Tu-154. It first flew in 1963 and entered service in 1967. Tupolev built 852, typically with about 76 seats.
Aeroflot flew most of them, alongside Interflug, Balkan, Malév, ČSA and Aviogenex in Eastern Europe and Hàng Không Việt Nam, now Vietnam Airlines. After 1991 they passed to airlines such as UTair, RusLine and Azerbaijan Airlines. About 5 remain, with Russian state and military operators. Regular passenger flights have ended.
Descending below safe heights
Nine counted accidents were flights into terrain, and several more were approaches flown too low in bad weather. On 30 August 1983 a Tu-134 began its descent towards Alma-Ata too early over the mountains; the terrain warning sounded for 23 seconds before the crew reacted, and all 90 died. On 12 December 1986, near Berlin-Schönefeld, the radio operator took a notice that a runway was closed for a landing clearance, and the jet sank into trees (72 of 82).
Vietnam Airlines 815 pressed on below a safe height in a downpour at Phnom Penh in 1997; 65 of 66 died, and a one-year-old boy survived. The last counted accident followed the same pattern. On 20 June 2011 a RusLine crew descended below the safe altitude in fog at Petrozavodsk and came down on a highway; 47 of 52 died, and the navigator was found to be mildly drunk.
Discipline and control
- 20 October 1986, Kuybyshev: the captain flew the approach with his window blinds closed as unauthorised practice. The jet hit the runway hard, a wing failed and it burned; 70 of 94 died.
- 5 December 1995, Azerbaijan Airlines, Nakhchivan: after one engine failed, the crew shut down the good one by mistake. 52 of 82 died.
- 11 August 1979, Kurilovka: a controller put two Aeroflot Tu-134s at the same level on crossing airways, and they collided in cloud. 178 died on the two aircraft, among them the Pakhtakor football team.
In 1985 a Tu-134 collided near Lviv with a military An-26 that civil and military controllers had both misplaced (79 dead).
Accidents the aircraft played a part in
On 1 February 1985 ice broke away from the wings on take-off from Minsk and was swallowed by both rear-mounted engines, which flamed out within a minute; 58 of 80 died. Fires in or under the rear cargo hold brought down Tu-134s in 1986, in the Komi republic (54 of 94), and in 1990, near Pervouralsk (27 of 71).
What is left out
Seven acts of violence are listed but not counted, including the Volga-Aviaexpress jet destroyed by a suicide bomber in 2004 (44 dead) and a Transair Georgia Tu-134 shot down approaching Sukhumi in 1993 (27). Seven cargo, test, military, ferry and other crashes are also left out, among them the Mozambique government flight that killed President Samora Machel in 1986. Our methodology explains why.
How to tell if you are on one
Flight trackers show T134. Two engines at the tail, a T-tail, gear pods behind the wings and, on most, a glazed nose give it away.
Questions people ask
Is the Tu-134 still in service?
Barely. About 5 of the 852 built remain, with Russian state and military operators. Russia moved the type off scheduled routes after the Petrozavodsk crash in 2011, and the last regular passenger flights ended in the late 2010s.
Why did two Tu-134s collide over Ukraine in 1979?
On 11 August 1979 a controller put two Aeroflot Tu-134s on crossing airways at the same level near Dniprodzerzhynsk and misjudged their separation. A late instruction to climb was misheard, and they collided in cloud at 8,400 metres. All 178 people on both aircraft died, among them the Pakhtakor Tashkent football team.
What happened to Samora Machel's plane?
On 19 October 1986 the Tu-134 bringing Mozambique's president home from Zambia followed a wrong beacon, turned early and kept descending at night despite a long terrain warning. It hit hills just inside South Africa; Machel and 33 others died. As a government flight it is listed but not counted.
What was the 'blind landing' crash at Kuybyshev?
On 20 October 1986 the captain of an Aeroflot Tu-134 flew the approach to Kuybyshev, now Samara, with his window blinds closed as unauthorised practice, and the rest of the crew did not stop him. The jet hit the runway at about 4.8 g, a wing failed and it rolled over and burned. 70 of 94 died.
Sources
- 1.ASN record: Aeroflot Tu-134A, Kurilovka, 11 August 1979 (opens in a new tab) · Aviation Safety Network
- 2.ASN record: Aeroflot Tu-134A, Kuybyshev, 20 October 1986 (opens in a new tab) · Aviation Safety Network
- 3.ASN record: Aeroflot Tu-134AK, near Minsk, 1 February 1985 (opens in a new tab) · Aviation Safety Network
- 4.ASN record: Vietnam Airlines flight VN815, Phnom Penh, 3 September 1997 (opens in a new tab) · Aviation Safety Network
- 5.ASN record: RusLine Tu-134A-3, Petrozavodsk, 20 June 2011 (opens in a new tab) · Aviation Safety Network
- 6.ASN record: República de Moçambique Tu-134A-3, near Komatipoort, 19 October 1986 (opens in a new tab) · Aviation Safety Network
- 7.SafetyScorer fleet model (World Bank departures, OpenSky averages) (opens in a new tab)Passenger departures 1967 to 7 October 2026 from a fleet model: deliveries with a median passenger service life of about 22 years and about 1,599 departures per aircraft per year (average of similar types in OpenSky). OpenSky sees too few of these aircraft because they were retired before 2019. After 1991 capped by departures reported by the former Soviet republics (World Bank). Uncertainty roughly ±50%.