Jump to content

Aeroflot Flight Sh-88

From Alfawiki
Adapted from the English Wikipedia article Aeroflot Flight Sh-88, available under CC BY-SA 4.0Updated 29 November 2025
Aeroflot Flight Sh-88
Company typeScheduled domestic passenger flight
IndustryAviation
Headquarters
Leninabad (present-day Khujand), Tajik SSR
,
Soviet Union
ProductsPassenger air transport


Template:Infobox aircraft occurrence

Aeroflot Flight Sh-88 was a scheduled domestic route connecting Leninabad (present-day Khujand) to Dushanbe. On June 12, 1980, the flight ended in tragedy near Dushanbe when it crashed, resulting in the loss of all 29 individuals aboard. The accident was attributed to errors by both the flight crew and air traffic control personnel.

Aircraft

The aircraft involved was a Yakovlev Yak-40 bearing the registration CCCP-87689 (factory number 9910403, serial number 03-04). Manufactured at the Saratov Aviation Plant on February 28, 1969, it was subsequently delivered to the Ministry of Civil Aviation. By March 12, it had been assigned to the Dushanbe Aviation Unit under the Tajik Civil Aviation Administration. The cabin configuration accommodated 24 seats.

Accident

Flight Sh-88 departed from Leninabad Airport at 13:04 under the command of Captain E. M. Lander. The Yak-40 ascended to an altitude of 7,200 meters carrying a total of 29 occupants—four crew members and twenty-five passengers, including two children.

Weather conditions en route from the Anzob pass to Dushanbe featured scattered clouds with bases between 2,500 and 2,800 meters and cloud tops reaching six to seven kilometers. Moderate turbulence prevailed alongside fresh westerly winds and isolated thunderstorms. These conditions were within acceptable meteorological limits for the captain and did not impede planned flight or landing operations.

Approximately 73 kilometers from Dushanbe Airport at 13:32, the crew deviated nine kilometers westward from their flight path to circumvent thunderstorm activity. However, this deviation was only communicated to air traffic control a minute later when it expanded to ten kilometers. Permission was granted by the controller for thunderstorm avoidance and descent to 6,000 meters near the Pugus non-directional beacon (NDB). Despite this, the regional center controller failed to track the flight’s position or notice its lateral displacement until the aircraft was roughly 67 kilometers from its destination.

At 13:36, the crew reported passing the Pugus NDB at an altitude of 6,000 meters; in truth, they remained about 37 kilometers away due to errors in wind speed estimation compounded by radio compass malfunctions caused by electrical interference amid dusty haze and nearby thunderstorms. The regional center controller neglected to monitor Flight Sh-88’s progress or provide positional updates. Instead, he only relayed a bearing of 340° relative to the airfield control point and instructed the crew to switch communications to the approach controller.

Although the Yak-40 was located approximately 43 kilometers northwest of Pugus, the approach controller did not ascertain its exact location before authorizing descent to 4,800 meters at the Dushanbe outer marker with an intended magnetic course of 86°. At 13:38, the aircraft altered course toward 160° heading for the outer marker and began descending. During this phase, air traffic control issued a direct bearing of 330° and instructed an expedited descent to 4,800 meters. Since this placed the aircraft beyond its assigned limit bearing of 340°, it had veered westward without detection by controllers who failed to initiate monitoring or verify actual position. Meanwhile, severe turbulence and icing conditions impaired radio compass functionality on board, preventing accurate navigation by the crew within cloud cover.

At approximately 13:40, pilots incorrectly reported having passed the outer marker at an altitude of 4,800 meters despite still being some 43 kilometers distant. The approach controller did not utilize available radio navigation aids to confirm this claim and approved further descent down to circuit altitude at 3,600 meters. Navigating mountainous terrain with peaks reaching up to 4,018 meters, the crew commenced a right turn while descending on a heading of roughly 266°, opposite to final landing direction. Without confirming precise location, they were then instructed by approach control to contact circuit control.

Cloud cover intensified fully as contact shifted to circuit control. Consistent with previous controllers’ oversights, this controller also failed to determine Flight Sh-88’s position accurately but authorized descent down to 2,100 meters during a third turn based on airfield pressure settings. This clearance overlooked that the aircraft was off established approach paths and significantly right of its designated limit bearing of 275°. Upon descending below 3,000 meters, pilots reported adjusting altimeters using local pressure at 694 mm Hg. Recognizing their position far north of intended approach routes, they leveled off near 2,840 meters and ceased descent before turning southward aiming to reestablish proper alignment.

When queried about their heading by air traffic control, crew responded that they were maintaining a course of 180°, although they were still in a turning maneuver actually oriented around heading 217°. Pilots requested bearings due to unreliable radio compass readings; however, circuit control provided an azimuth of only 300°, disregarding that this exceeded prescribed limits. Furthermore, when asked for positional data by pilots, controller admitted inability to provide it because radar systems were offline for equipment replacement despite availability of an ARP-75 direction finder.

At approximately 13:44:00 while flying through clouds at an altitude near 2,840 meters and traveling at about 380 km/h on a heading around 208°, Flight Sh-88 collided with a mountainside slope resulting in complete destruction of the aircraft and fatality for all onboard occupants.

Investigation

Investigation findings:

  1. During the final segment of the flight, as the crew maneuvered to avoid thunderstorm cells, unreliable radio compass readings combined with inconsistent wind speed data prevented precise identification of the Pugus NDB passage and the Dushanbe outer marker. This hindered effective navigation and position tracking.
  2. The aircraft's deviation from the planned route and approach pattern while circumventing thunderstorms was not supervised by air traffic controllers at Dushanbe airport. Despite operating under special conditions and outside prescribed bearings, the aircraft’s location was never established or relayed to the flight crew. Additionally, the flight operations manager failed to implement necessary measures to curb ATC violations and did not ensure proper shift organization.

The controllers and flight crew committed multiple breaches against NPP GA-78 regulations:

  1. The regional center controller neglected flight monitoring duties and did not update the crew on the aircraft’s whereabouts during thunderstorm avoidance maneuvers;
  2. The approach controller failed to ascertain and communicate the aircraft’s position, omitted clarifying its location when transferring control to the circuit controller, and authorized descent to 3,600 meters—below the elevation of nearby mountainous terrain;
  3. The circuit controller did not confirm aircraft identification, neglected oversight of crew adherence to descent and landing procedures, and permitted descent to 2,100 meters while the plane was off course and beyond limiting bearings;
  4. The flight crew did not consider distortions in radio compass signals caused by thunderstorms and mountainous terrain effects during thunderstorm avoidance, reported inaccurate NDB passage timing, and failed to apply effective navigation techniques for reaching the NDB.

These infractions resulted in a 32-kilometer deviation toward mountains rising up to 4,764 meters. Subsequent descent to 2,100 meters culminated in controlled flight into terrain as the aircraft collided with a mountainside.

The accident's root cause was attributed to shortcomings in air traffic control at Dushanbe airport, including non-compliance with NPP GA-78 standards in flight management, coupled with crew errors in position determination while navigating through thunderstorms in mountainous regions.

Notes

Template:Aviation accidents and incidents in 1980 Template:Aviation accidents and incidents in the Soviet Union in the 1980s and 1990s Template:Aviation accidents and incidents in Tajikistan