ASN logo
Date:Wednesday 23 March 1994
Type:Silhouette image of generic A310 model; specific model in this crash may look slightly different
Airbus A310-304
Operator:Aeroflot Russian International Airlines
Registration: F-OGQS
MSN: 596
First flight: 1991-09-11 (2 years 6 months)
Total airframe hrs:5375
Engines: 2 General Electric CF6-80C2A8
Crew:Fatalities: 12 / Occupants: 12
Passengers:Fatalities: 63 / Occupants: 63
Total:Fatalities: 75 / Occupants: 75
Aircraft damage: Destroyed
Aircraft fate: Written off (damaged beyond repair)
Location:near Mezhduretshensk (   Russia)
Phase: En route (ENR)
Nature:International Scheduled Passenger
Departure airport:Moskva-Sheremetyevo Airport (SVO/UUEE), Russia
Destination airport:Hong Kong-Kai Tak International Airport (HKG/VHHH), Hong Kong
Flightnumber: 593
The aircraft was en route from Moscow to Hong Kong at 10100 m when, approaching the Novokuznetsk reporting point, the captain's daughter entered the cockpit. She was allowed to sit the left-hand seat while the captain demonstrated some autopilot features, using HDG/S and NAV submodes to alter the heading. The captain's son then took the left front seat. The captain intended to demonstrate the same manoeuvre when his son asked if he could turn the control wheel. He then turned the wheel slightly (applying a force of between 8-10 kg) and held it in that position for a few seconds before returning the wheel to the neutral position. The captain then demonstrated the same features as he did to his daughter and ended by using the NAV submode to bring the aircraft back on course. As the autopilot attempted to level the aircraft at its programmed heading, it came in conflict with the inputs from the control wheel which was blocked in a neutral position. Forces on the control wheel increased to 12-13 kg until the torque limiter activated by disconnecting the autopilot servo from the aileron control linkage. The autopilot remained engaged however. The aircraft then started to bank to the right at 2,5deg/sec, reaching 45deg. when the autopilot wasn't able to maintain altitude. The A310 started buffeting, which caught the attention of the captain who told the co-pilot to take control while he was trying to regain his seat. The seat of the co-pilot was fully aft, so it took him an additional 2-3 seconds to get to the control wheel. The bank continued to 90 degrees, the aircraft pitched up steeply with +4,8g accelerations, stalled and entered a spin. Two minutes and six seconds later the aircraft struck the ground.

Probable Cause:

The A310 disaster was caused by a stall, spin and impact with the ground resulting from a combination of the following factors:
1. The decision by the PIC to allow an unqualified and unauthorized outsider (his son) to occupy his duty station and intervene in the flying of the aeroplane.
2. The execution of demonstration manoeuvres that were not anticipated in the flight plan or flight situation, with the PIC operating the autopilot while not at his duty station.
3. Application by the outsider and the co-pilot of control forces that interfered with the functioning of the roll channel of the autopilot (and are not recommended in the A310 flight manual), thus overriding the autopilot and disconnecting it from the aileron control linkage.
4. The co-pilot and PIC failed to detect the fact that the autopilot had become disconnected from the aileron control linkage, probably because:
- The A310 instrumentation has no declutch warning. The provision of signals in accordance with the requirements of Airworthiness Standard NLGS-3, para., and international recommended practices, could have enabled the crew to detect the disengaged autopilot in a timely manner.
- The co-pilot and PIC may have been unaware of the peculiarities of the declutching function and the actions to be taken in such a situation because of a lack of appropriate information in the flight manual and crew training programme;
- It was difficult for the co-pilot to detect the disengagement of the autopilot by feel, either because of the small forces on his control column or because he took changing forces to be the result of Eldar's actions;
- The PIC was away from his position and distracted by the conversation with his daughter.
5. A slight, unintentional further turn of the control wheel(s) following disengagement of the autopilot caused a right roll to develop.
6. The PIC and co-pilot failed to detect the excessive right bank angle, which exceeded operating limits, and were late in re-entering the aircraft control loop because their attention was focussed on determining why the aircraft had banked to the right, a manoeuvre they interpreted as entry into a holding area with either no course line or with a new (false) course line generated on the navigational display.
A strong signal indicating that the aeroplane had exceeded the allowable operating bank angle, taking account of the delay in recognizing and assessing the situation and making a decision, could in this situation have attracted the crew's attention and enabled them to detect the bank at an earlier stage.
7. The aeroplane was subjected to buffeting and high angles of attack because the autopilot continued to perform its height-keeping function even after the actuator declutched and as the right roll developed, until the pilot disconnected it by overriding its longitudinal channel.
8. Inappropriate and ineffective action on the part of the co-pilot, who failed to disconnect the autopilot and to push the control column forward when the buffeting occurred and the aeroplane entered an unusual attitude (high angles of attack and pitch). These actions, which caused the aeroplane to stall and spin, could have resulted from:
- the presence of an outsider in the left-hand pilot's seat and the resulting delay before the PIC re-entered the aeroplane control loop;
- the less-than-optimum working posture of the co-pilot, whose seat was pushed back to its rearmost position;
- the occurrence, 2 seconds following the onset of buffeting, of an unintentional pitching up of the aeroplane, which sharply increased the angle of attack and reduced lateral controllability;
- unpreparedness of the crew to act in this situation because of lack of appropriate drills in the training programme;
- temporary loss of spatial orientation in night conditions.

Accident investigation:
Investigating agency: MAK
Status: Investigation completed
Accident number: Final report
Download report: Final report

Distraction in cockpit
Loss of control

» Flight International 29.3-4 April 1995 (13)
» Flight International 6-12 April 1994 (8)
» Air Safety Week 28 March 1994 (p. 4)
» Edwin van Rij
» Flight International 30 March - 5 April 94
» ICAO Adrep Summary 2/94 (#4)
» On the crash of the aircraft of A310-308 F-OGQS of airline "Russian International Airlines" / Ministry of Transport letter 28.04.95 No. 44

Follow-up / safety actions

issued 6 Safety Recommendations

Show all...


photo of Airbus-A310-304-F-OGQS
accident date: 23-03-1994
type: Airbus A310-304
registration: F-OGQS
photo of Airbus-A310-304-F-OGQS
accident date: 23-03-1994
type: Airbus A310-304
registration: F-OGQS
photo of Airbus-A310-304-F-OGQS
accident date: 23-03-1994
type: Airbus A310-304
registration: F-OGQS

This map shows the airport of departure and the intended destination of the flight. The line between the airports does not display the exact flight path.
Distance from Moskva-Sheremetyevo Airport to Hong Kong-Kai Tak International Airport as the crow flies is 7099 km (4437 miles).
Accident location: Exact; deduced from official accident report.

This information is not presented as the Flight Safety Foundation or the Aviation Safety Network’s opinion as to the cause of the accident. It is preliminary and is based on the facts as they are known at this time.
languages: languages


Airbus A310

  • 255 built
  • 2nd loss
  • 2nd fatal accident
  • 2nd worst accident (at the time)
  • 6th worst accident (currently)
» safety profile

  • 24th worst accident (at the time)
  • 31st worst accident (currently)
» safety profile

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2022 Flight Safety Foundation

701 N. Fairfax St., Ste. 250
Alexandria, Virginia 22314