Jump to content

Khabarovsk United Air Group Flight 3949

From Alfawiki
Adapted from the English Wikipedia article Khabarovsk United Air Group Flight 3949, available under CC BY-SA 4.0Updated 29 November 202520 sources
Khabarovsk United Air Group
IndustryAviation
FateRenamed Dalavia; ceased operations in 2008
Headquarters
Khabarovsk
,
Russia

Khabarovsk United Air Group Flight 3949 Accident

Khabarovsk United Air Group Flight 3949 was a domestic Russian passenger service traveling from Yuzhno-Sakhalinsk to Khabarovsk. On 7 December 1995 local time (6 December UTC), the aircraft crashed, resulting in the loss of all ninety-eight individuals on board. The incident occurred when the plane entered a steep descending spiral while flying under automated control at an altitude of approximately 10,600 metres (34,800 ft).

The inquiry conducted by the Russian Interstate Aviation Committee (IAC) determined that the accident stemmed from a combination of mechanical malfunction, pilot error, and a design defect. Shortly after departure, the aircraft abruptly banked sharply to the left. In response, the flight crew executed an unconventional procedure by transferring fuel from the left tank to the right, which caused a shift in balance toward the right side. The pilots did not realize that the aircraft had rolled to the right. Due to inadequate monitoring, the plane entered a severe right turn, spiraling downward uncontrollably and ultimately crashing at high velocity.

This tragedy marked the second accident involving a Tupolev Tu-154 within a span of nearly two years, following the January 1994 crash of Baikal Airlines Flight 130. It was also Russia’s second major jet airliner disaster within twelve months, after the Vanavara air disaster. The airline operating the flight, Khabarovsk United Air Group, was later renamed Dalavia before ceasing operations in 2008.

Aircraft

The airplane involved in the incident was a Tupolev Tu-154B-1 model, constructed on 30 July 1976 with the serial number 76А164. Initially registered as USSR-85164, it was operated by the Soviet Union's national airline, Aeroflot. After the collapse of the Soviet Union in 1991, the aircraft received a new registration, RA-85164, and was assigned to the Khabarovsk United Air Group, although its exterior paint scheme remained unchanged from its previous operator.

Before the crash, this Tupolev Tu-154 had logged 30,001 flight hours and undergone four maintenance overhauls, the most recent of which took place on 23 September 1991. During that last service, two engines were replaced. Post-maintenance, the plane exhibited an uncommanded leftward roll tendency that pilots had noted but remained unresolved. Despite this unresolved issue, flight crews continued operating the aircraft.

Passengers and crew

Onboard were 90 passengers along with 8 crew members, including five children and one infant. The specific nationalities of those aboard were not publicly released.

The cockpit team at the time comprised:

  • Captain Viktor Konstantinovich Sumarokov, aged 46, serving as pilot-in-command. A graduate of Buguruslan Flying School, he accumulated over 12,000 total flight hours, with 5,054 hours specifically on the Tupolev Tu-154. His record showed no prior accidents or incidents.
  • First Officer Stanislav Aleksandrovich Revedovich, aged 43. He graduated from Omsk Aviation Academy and had approximately 10,000 flight hours overall, including 1,620 hours on the Tupolev Tu-154. He had been involved in a landing incident in Irkutsk in 1994.

Other flight crew members included Navigator Alexander Alekseevich Martynov, age 32, with 5,008 flight hours (1,990 on Tu-154), and Flight Engineer Grigory Alekseevich Moroz, age 30, who had flown a total of 1,816 hours exclusively on the Tupolev Tu-154.

Crash

This flight represented the second segment of a round trip originating from Khabarovsk to Yuzhno-Sakhalinsk, returning to Khabarovsk, and then continuing onward to Novosibirsk with a scheduled stopover in Ulan-Ude. Initially planned to depart for Yuzhno-Sakhalinsk at 16:45 local time, the flight experienced a delay of several hours caused by worsening weather conditions. The aircraft ultimately departed around 23:00 local time without any passengers on board. During this leg, the plane exhibited a gradual left bank, prompting the crew to continuously apply right aileron input to maintain level flight. After successfully stabilizing the wings, the journey proceeded without further complications.[1]

Touching down at Yuzhno-Sakhalinsk Airport at 00:34 local time, the aircraft remained stationary for roughly two hours. For the next leg, First Officer Revidovich assumed control as the pilot flying, while Captain Sumarokov managed radio communications. The aircraft departed at 02:43 a.m. carrying 90 passengers. The takeoff weight was compliant with operational limits, recorded at 82,600 kilograms (182,100 lb), and fuel load was 15,100 kilograms (33,300 lb).[1]

Start of failure

Shortly after beginning the climb, the aircraft suddenly started to bank leftward in a progressive manner. The crew, familiar with this behavior from previous flights, responded by pushing the control column rightward to level the wings. Despite their efforts, the left bank persisted, necessitating increasingly greater right control inputs to prevent excessive rolling. At one point, the bank angle reached approximately 30 degrees—beyond what the crew typically managed.[1]

Observing this pronounced asymmetry, Captain Sumarokov suggested addressing it by transferring fuel from the left wing tank to the right wing tank to counterbalance the tilt. This approach was unanimously agreed upon by all crew members. Having encountered similar scenarios before, they had previously implemented this exact procedure successfully to restore balance. After executing the fuel transfer, they continued with the flight.[1]

The autopilot system, engaged earlier during climb-out, detected an opposite turn developing toward the right and responded by deflecting the control column leftward. However, despite these corrections, the bank angle intensified progressively up to 15 degrees. Once exceeding the autopilot’s maximum corrective capacity, it failed to maintain control as the aircraft veered further right. Meanwhile, the crew was occupied with completing pre-landing checklists and remained unaware that the aircraft had deviated right instead of continuing its expected left turn.[1][2]

Plunge

While the pilots shifted their focus to the pre-landing checklist, the aircraft's bank angle continued to increase steadily. It eventually surpassed 30 degrees, triggering the aircraft’s alert system to warn the crew by activating warning lights. Neither pilot responded immediately to these signals; however, Captain Sumarokov perceived that something was amiss due to the pronounced banking sensation. Recognizing the excessive tilt, he instructed First Officer Revidovich to "slow down".[1][2]

03:07:35 Captain What are you doing? Slow down!
03:07:36 Captain Hold on! Disengage the autopilot!
03:07:39 First Officer I see! We’re off course!
03:07:45 Captain What now? What’s happening?
03:07:46 First Officer Bank angle!
03:07:47 Captain What the…? Where are we headed?!
03:07:48 First Officer Banking! Banking! Large bank angle!

Captain Sumarokov eventually commanded the autopilot to be switched off, yet the aircraft continued its banking motion. The turn accelerated further to the right at a rate of approximately 2 degrees per second. Even after moving the control column leftward upon reaching a 45-degree bank, the tilt intensified. Confused by these developments, Captain Sumarokov questioned his colleague about the situation. First Officer Revidovich confirmed that the plane was turning right at an unusually steep angle.[1][2]

As the turn persisted, airspeed increased beyond safe operational limits, activating the overspeed warning alarm. Recognizing the imminent risk of loss of control, the crew attempted to counteract the excessive bank by applying a leftward input of roughly 45 degrees on the control column. However, this effort failed to stabilize the aircraft, which continued to lean further right.[1]

03:07:49 Commentary Overspeed alarm sounds
03:07:50 First Officer Bank angle is too steep!
03:07:51 Captain Decrease the bank angle!
03:07:52 First Officer Speed is excessive!
03:07:53 Captain Y... mother. Where exactly are we? System one status!
03:07:55 First Officer Bank! Can’t you see it?!
03:07:57 Captain Which direction is this banking?!
03:08:58 First Officer Can’t you see how much it’s banking?
03:08:01 Flight Engineer Speed! Speed alert!
03:08:02 First Officer What’s the current speed?
03:08:03 Captain Correct the bank angle! Take your time! Slowly now!


Crash

Template:External media The aircraft descended rapidly toward the terrain at a velocity exceeding 100 meters per second. In a frantic effort to regain control, the flight crew manipulated the control column vigorously in all directions to counteract the escalating right bank. Disoriented and unable to establish spatial awareness, their efforts to stabilize the plane were unsuccessful. The aircraft spiraled downward, accelerating further as the pilots lost command of the controls.[1]

03:08:06 Commentary Bank angle warning alarm sounds
03:08:12 Captain We're falling! We're falling!
03:08:14 First Officer Altitude! E-e-e-e!
03:08:16 Captain That's it, fuck! That's it, fuck!
03:08:19 First Officer Well...
03:08:20 Commentary Impact noise
03:08:21 End of recording

The airplane collided with Bo-Dzhausa Mountain at an estimated vertical velocity near 300 m/s and a pitch angle close to 70 degrees. The impact caused the aircraft to fragment extensively. All 98 occupants on board perished instantly upon impact.[1]

Response

According to the investigation, the aircraft was cruising at approximately 10,600 metres (34,800 ft) (with some sources indicating 9,600 metres (31,500 ft)) when it vanished from radar shortly after delivering a routine ATC communication.[3][4] The last ATC contact occurred at 03:00 a.m. local Vladivostok time (17:00 UTC), with Flight 3949 located roughly 160 km from Khabarovsk. It failed to arrive by its scheduled time of 03:45 local time.[5] Approximately one hour later, search and rescue operations began. An Antonov An-12 and a Russian Air Force Antonov An-26 were dispatched to locate the missing plane but were forced to cease efforts by midnight due to poor visibility and heavy snowfall.[6][7]

Initial reports from Radio Moscow claimed that burning wreckage had been sighted about 120 km from Khabarovsk; however, this was refuted by the Russian Ministry of Emergency Situations.[8]

Residents in Koppi reported hearing low-flying aircraft nearby, while in Grossevichi some claimed the plane had crashed within village limits. Despite deploying multiple personnel to these locations, no evidence of the aircraft was found. Consequently, search efforts expanded toward the Tatar Strait, with numerous vessels dispatched to comb the waters for debris.[9][6]

On December 9, Deputy Prime Minister Oleg Soskovets arrived in Khabarovsk to oversee search operations. Authorities deployed a fleet of 22 ships in the Tatar Strait region and announced plans to involve a Tupolev Tu-134 equipped with metal detection technology. The Ministry of Defense also committed satellite resources in hopes of locating wreckage.[6][10]

Paratroopers from the Russian Armed Forces were deployed in support of recovery efforts. Although some debris was discovered initially, it was later identified as remnants from previous aviation accidents predating Flight 3949’s crash. A total search area covering roughly 14,000 square meters was examined without locating any wreckage. Satellite images suggested possible debris near Berezovaya; however, this was subsequently disproven. Additional reports about oil slicks north of the Sea of Japan and smoke sightings near Sukpai were also dismissed by officials.[11][12]

After days without success, authorities sought help from renowned Russian psychic Juna, who recommended enlarging the search perimeter. She indicated that the crash site might be located near the Samarga River, within an area twice as large as that already covered by rescuers. Despite thorough investigation in this suggested zone, no wreckage was found.[11][6]

The crash location was ultimately discovered on December 18, 1995, by chance on Bo-Dzhausa Mountain’s Sikhote-Alin Ridge by a pilot from Vostok Aviation Company flying a Mil Mi-8. He was not part of official search teams but noticed unusual soil coloration on a nearby mountain and observed part of an aircraft fuselage protruding from the ground during an emergency landing in the taiga.[13][14] He reported this discovery to authorities and was awarded the Medal of Nesterov for his contribution.[2]

Subsequent accounts indicated that rescue teams had flown over the crash site multiple times but failed to detect it due to adverse weather conditions and rugged terrain.[15]

The impact created a crater approximately six feet deep and seventy feet across, evidencing an extremely high-speed collision with minimal intact wreckage remaining. Scattered throughout were fragmented human remains and personal effects destroyed by the force of impact. Over fifty personnel were assigned to recover victims’ bodies.[15]

Officials announced that family members wishing to visit the crash site would be accommodated via special flights.[15][16]

This tragedy intensified scrutiny on Russia’s aviation sector, marking it as the fifth air disaster within one week and second major catastrophe in under two years. The incident further strained an industry already facing challenges, especially with an impending indefinite strike planned by the Federation of Air Traffic Controllers’ Trade Union within days. Russian media outlet Kommersant criticized existing air traffic control systems as inadequate and inefficient for managing rapid post-Soviet aviation growth.[6]

Approximately two months after this event, Russian authorities mandated grounding all Tupolev Tu-154B aircraft nationwide following indications that an unidentified mechanical malfunction may have caused uncommanded right banking prior to the crash. These aircraft remained grounded pending completion of investigations.[17]

Initial inquiry

Analysis of the crash scene indicated that the aircraft likely struck the ground at a high velocity, as evidenced by the large crater and scattered debris, suggesting a nose-first impact. While officials initially considered possibilities such as an in-flight explosion or sudden cabin depressurization, they ultimately pointed to mechanical malfunction as the most probable cause. Notably, the crew did not send out a distress signal, and the final radio communication showed no signs of emergency from the pilots.[16][18]

On the day the wreckage was discovered, both flight recorders were recovered; however, they had sustained significant damage from the crash. The protective casings were distorted, and the tapes inside exhibited tears and breaks. Consequently, only partial data retrieval was achievable during decoding.[19]

Crash causation

During ascent, an abrupt left bank occurred without any pilot input, caused by a malfunction within one of the flight control systems. To counteract this, the crew continuously applied right bank control. Captain Sumarokov suggested employing a previously successful technique to correct such left banking by transferring fuel between tanks—a method not outlined in the aircraft’s manual and thus considered non-standard. Despite this, the crew consented to proceed with this approach.[1]

Fuel transfer from the left and center tanks generated rightward rolling forces. Asymmetric fuel transfer was permissible provided it remained within established limits. Instrumentation indicated only a slight fuel imbalance; however, due to inaccurate gauge readings, the crew failed to recognize that they had transferred an excessive amount of fuel—over 3,600 kilograms—into the right tank. Meanwhile, the left tank contained less than 1,000 kilograms.[1]

Initially, the autopilot managed to correct the unintended left bank; however, with additional fuel added to the right tank, rolling forces surpassed what the system could compensate for, causing the aircraft to bank right instead. The crew did not detect this shift because they assumed normal autopilot function and were preoccupied with completing pre-landing procedures.[1]

Once the bank angle became sufficiently steep to warrant concern, the pilots were unable to determine its direction. Coupled with complete darkness outside, this led to disorientation regarding their spatial positioning. Rather than collaborating effectively, panic ensued among the crew as their altitude rapidly decreased. A lack of training in spatial orientation contributed to a breakdown in Cockpit Resource Management (CRM), ultimately preventing resolution of the situation.[1]

Additional shortcomings

The sudden banking to the left was traced back to an incorrectly installed aileron component within the Tupolev Tu-154's control mechanism. This part had been replaced with one taken from another aircraft of the same model as a cost-saving measure. The maintenance outcome was not verified, and the aircraft underwent only a limited number of test flights. Maintenance personnel failed to identify the defect. When the pilots eventually detected the malfunction and reported it, their concerns were dismissed by the company, which chose to disregard these warnings.[1]

The flight manual lacked instructions for the crew on handling such an event; consequently, the crew relied on a previously successful procedure. Although the fuel transfer technique used was unconventional, it was not forbidden. However, the accident aircraft suffered from inaccurate fuel gauge readings, preventing pilots from precisely determining how much fuel had been shifted between tanks. Despite performing asymmetric fuel transfer, this practice was considered normal in Tupolev Tu-154 operations, provided that the aircraft's balance stayed within acceptable limits.[1]

Once the plane entered a steep right bank, the crew quickly lost spatial awareness. Years prior to the accident, an audible alert system designed to warn crews of excessive bank angles had been installed on the Tupolev Tu-154. Nevertheless, in 1986, authorities decided to remove this alarm entirely from the fleet. The absence of this warning may have contributed to the crew’s delayed response to the sudden banking change.[20][1]

Summary

The investigation identified five potential factors which, when combined, likely caused the crash. It is believed that fuel feed was drawn exclusively from the left wing tanks to compensate for a tendency for the aircraft’s left wing to fly low.[3] This fuel imbalance probably caused the plane to bank rightward, with the autopilot managing to correct this for approximately 35 minutes after departure.[3]

Further critique was directed at regional navigation operations, which were found severely inadequate. Radar equipment serving the Khabarovsk area had been damaged by a recent storm but remained unrepaired and unused by personnel. Additionally, communication between pilots and air traffic control (ATC) was not recorded due to tape failure. The aircraft was not actively monitored by on-duty staff, and following its disappearance, there was minimal communication from ATC or Air Defence personnel.[1]

Following this incident, it was decided that an audible bank angle warning system would be reintroduced on Tupolev Tu-154 aircraft.[20]

See also

References

  1. ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 Cite error: Invalid <ref> tag; no text was provided for refs named report_2
  2. ↑ 2.0 2.1 2.2 2.3 Cite error: Invalid <ref> tag; no text was provided for refs named Komsomolskaya_Pravda
  3. ↑ 3.0 3.1 3.2 Cite error: Invalid <ref> tag; no text was provided for refs named asn
  4. ↑ "Plane Crashes for Airlines of Russia and the Former Soviet Union".
  5. ↑ "Rescuers search for lost Russian jet". 7 December 1995. Retrieved 10 February 2025.
  6. ↑ 6.0 6.1 6.2 6.3 6.4 Cite error: Invalid <ref> tag; no text was provided for refs named Kommersant
  7. ↑ "SNOW HINDERS SEARCH FOR RUSSIAN PLANE". 7 December 1995. Retrieved 28 January 2025.
  8. ↑ "World IN BRIEF : RUSSIA : Plane Feared to Have Crashed; 97 Aboard". 7 December 1995. Retrieved 27 January 2025.
  9. ↑ "Russian jet carrying 97 still missing". 8 December 1995. Retrieved 27 January 2025.
  10. ↑ "SATELLITE SPOTS APPARENT REMAINS OF LOST PLANE". 13 December 1995. Retrieved 10 February 2025.
  11. ↑ 11.0 11.1 Cite error: Invalid <ref> tag; no text was provided for refs named LATimes
  12. ↑ Gould, Paul (9 December 1995). "Traces of lost Russian jet dismissed". Retrieved 27 January 2025.
  13. ↑ "Russian Crash Site Found". 19 December 1995. Retrieved 28 January 2025.
  14. ↑ Gould, Paul (18 December 1995). "Missing Russian airliner found by chance". Retrieved 27 January 2025.
  15. ↑ 15.0 15.1 15.2 Cite error: Invalid <ref> tag; no text was provided for refs named Deseret
  16. ↑ 16.0 16.1 Cite error: Invalid <ref> tag; no text was provided for refs named Independent
  17. ↑ "Crash leads to Tu-154B groundings". 7 February 1996. Retrieved 6 February 2025.
  18. ↑ Los Angeles Times, 20 December 1995
  19. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named report_1
  20. ↑ 20.0 20.1 Cite error: Invalid <ref> tag; no text was provided for refs named Technical

Template:Aviation accidents and incidents in 1995 Template:Aviation accidents and incidents in Russia during the 1990s