Aeroflot Flight E-46
| Industry | Airline |
|---|---|
| Founded | 1923 |
| Headquarters | Moscow , Soviet Union |
| Products | Passenger air transport |
Template:Infobox aircraft occurrence
Aeroflot Flight E-46 was a domestic passenger service that tragically ended in a crash on Tuesday, April 19, 1983, near the city of Leninakan (present-day Gyumri), in Armenia. The plane, a Yakovlev Yak-40 under the operation of Aeroflot, collided with terrain, resulting in the loss of all 21 individuals aboard.
Aircraft
The aircraft involved, a Yak-40 bearing tail number 87291 (factory serial 9320628, production number 28-06), was manufactured in 1973 at the Saratov Aviation Plant. It was assigned to the Leninakan division of the Armenian Civil Aviation Directorate on May 10 by the USSR's Ministry of Civil Aviation.[1][2]
Accident
Flight E-46 was conducted along the route from Volgograd to Leninakan with an intermediate stop at Nalchik, piloted by Captain R.G. Bagdasaryan. The aircraft departed from Nalchik Airport at 17:07 and ascended to a cruising altitude of 6,600 meters. Onboard were four crew members and seventeen passengers.[1]
After passing over Kislovodsk, the plane deviated rightward, prompting a warning from the dispatcher at the regional center in Mineralnye Vody (Minvody). The crew's response to return to the prescribed flight path (PFP) was delayed, causing the aircraft to fly approximately 10 kilometers parallel but off-course. Upon reaching Gori, it was realigned with the PFP and at 17:53 contacted the Tbilisi regional center's dispatcher, reporting passage over Gori at 6,600 meters altitude. The dispatcher acknowledged this and instructed descent to 5,700 meters. During the subsequent leg toward Leninakan, multiple course adjustments reduced the heading from 185° to 130°, yet without precise navigation efforts. This led to a leftward drift of roughly 28 kilometers off-route. At 18:02, pilots informed Tbilisi ATC of exiting the zone at an altitude of 5,700 meters; however, their actual location was about 57 kilometers from Tbilisi—far short of the planned exit point—and displaced leftward by 28 kilometers, still with nearly 39 kilometers before reaching ATC handover.[1]
At 18:03, contact was made with Leninakan Airport’s approach controller who was informed that the aircraft had entered their airspace zone, though it remained approximately 87 kilometers distant and displaced left by about 29 kilometers. A minute and a half later, when requesting position confirmation, the controller reported an azimuth of 30° but noted that the plane was not visible on radar—an indication of significant deviation. Despite this, no corrective measures were taken by ATC. Unaware of their true position, pilots soon reported crossing the control boundary at a distance of 21 kilometers and indicated favorable conditions for visual flight. The controller then authorized descent to 3,300 meters at the Radio Navigation Point (RNP). During this descent phase, neither ground-based nor onboard radio navigation systems were utilized properly to guide toward the airport beacon.[1]
Meteorological conditions included cumulus clouds between altitudes of 600 to 1,000 meters with tops reaching seven to eight kilometers; visibility exceeded ten kilometers though mountain summits were partially obscured by cloud cover. While descending through approximately 3,600 meters altitude, pilots were instructed to contact the circle controller—a role fulfilled by the approach controller himself. Despite lacking radar contact with the aircraft, clearance was given for further descent to 900 meters in preparation for a third turn. At this point, although actually located some 40 kilometers from Leninakan Airport and unaware of this fact, at around 18:08 pilots reported passing over the airport’s RNP and commenced landing maneuvers despite being off-course.[1]
At approximately 18:09, while executing a right turn with a bank angle of about 13° on heading 178°, the Yak-40 collided with Mount Shishtepe’s slope at an elevation near 2,523 meters. The crash site lies roughly 41 kilometers northeast of Leninakan Airport between Spitak and Stepanavan in Lori Province. The impact completely destroyed the aircraft and resulted in fatalities for all twenty-one occupants—four crew members and seventeen passengers.[1]
Causes
The commission's investigation identified the following factors as contributing to the accident:[1]
- The flight crew failed to actively navigate the aircraft along the Gori to Leninakan segment, underutilized the RNS, and consequently strayed from the designated route without awareness of their precise position. During the final portion of the flight, lacking knowledge of their location and not having reached the Required Navigation Performance (RNP), the crew initiated descent and landing procedures outside the established aerodrome pattern, significantly breaching the standards set by NPP GA-78 and the Flight Operation Manual at Leninakan Airport.
- The RC Tbilisi dispatcher’s management of the flight was inadequate: radar monitoring was not maintained, deviation from the route was neither prevented nor corrected, and no efforts were made to redirect the aircraft back on course. Furthermore, when transferring control to the Leninakan Airport approach sector, in contravention of NPP GA-78, NSD GA-81, and dispatcher operational protocols, the dispatcher failed to verify the aircraft’s actual position or communicate this information to the crew.
- Upon receiving notification from the crew about entering its zone, the Leninakan Airport approach controller did not identify the aircraft or relay its position back to them. The controller neglected to evaluate the reported 30° azimuth, issue instructions for route reestablishment, or ensure navigation toward the RNP utilizing a direction finder. Lacking continuous radar supervision and unaware of the aircraft’s true location after it passed the 21-kilometer control boundary, he authorized descent from a secure altitude of 4,200 meters down to 3,300 meters. While simultaneously performing circle control duties without ongoing radar tracking in both approach and circle zones, he failed to guide the aircraft toward RNP compliance, omitted requiring a safe altitude holding pattern for identification purposes, withheld critical landing approach information, and permitted descent to 900 meters with an approach outside aerodrome parameters. This series of actions violated NPP GA-78, NSD GA-81, Leninakan Airport’s Flight Operation Manual, and established procedures for approach and circle controllers. Moreover, despite lacking radar data, he did not request assistance from Air Defense nor utilize their resources for position determination.
- The senior controller neglected to oversee or direct the Yak-40 flight operations effectively, demonstrated complete passivity in supervising both approach and circle controllers’ performance, and failed to implement necessary interventions that could have averted the accident.
Conclusion
The tragedy involving the Yak-40 resulted from severe breaches by both Air Traffic Control personnel and flight crew of regulations outlined in NPP GA-78 and Leninakan Airport’s Flight Operation Manual. These violations caused an untimely descent outside prescribed aerodrome procedures culminating in collision with mountainous terrain.[1]
References
Template:Aviation accidents and incidents in 1983 Template:Aviation accidents and incidents in the Soviet Union during the 1980s and 1990s
- Aeroflot accidents and incidents
- April 1983 events
- 1983 occurrences in Armenia
- Lori Province
- Accidents involving the Yakovlev Yak-40
- Aviation accidents caused by controlled flight into terrain
- Aviation incidents attributed to air traffic controller error
- Aviation accidents and incidents in 1983
- Aviation accidents and incidents within the Soviet Union
- Aviation accidents and incidents in Armenia
- Accidents and incidents involving the Yakovlev Yak-40