FlightFollowerImpaired and Disoriented Pilot Crashes Boeing 737, Killing 88
Aeroflot-Nord 821's Final Descent Into Perm
On 13 September 2008, Aeroflot-Nord Flight SU821, a Boeing 737-500, tragically crashed on approach to Perm Bolshoye Savino Airport, Russia, killing all 88 occupants. The flight departed from Moscow Sheremetyevo Airport at 21:13 for a domestic route to Perm. Contact was lost at 3600 feet amid night-time cloud cover and difficult weather conditions.
The aircraft struck the outskirts of Perm, narrowly missing residential areas. Investigations revealed the primary cause was spatial disorientation of the crew, particularly the Captain flying the final approach. Night-time clouds, unfamiliar Western-style attitude indicators, and disengagement of autopilot and autothrottle contributed to the loss of control, steep left-bank descent, and crash.
Contributing factors included: Pilot fatigue and overwork Presence of ethyl alcohol in the Captain’s body Crew lack of proficiency in upset recovery and Western ADI systems Poor crew resource management (CRM) Maintenance deficiencies leading to persistent throttle asymmetry, increasing workload during approach This accident highlights the critical importance of crew training, automation management, and airline operational oversight in preventing spatial disorientation and fatal approach accidents. The accident occurred on 13 September 2008.
Aeroflot-Nord Flight SU821 crashed on approach to Perm on September 14, 2008, after the crew lost control in nighttime instrument conditions. The aircraft was a Boeing 737-500 and all 88 people aboard died. The investigation examined spatial disorientation, crew experience with the aircraft’s Western-style flight instruments, automation management and the asymmetry problem that increased cockpit workload.
More Than Alcohol: An Unfamiliar Instrument Panel
The accident sequence is particularly important because the aircraft was not simply ‘drunk and disoriented.’ The captain had ethyl alcohol in his system, but the investigation also identified inadequate familiarity with the aircraft’s attitude indications, disengagement of automation and the crew’s failure to recognize and recover from the developing upset. Those factors interacted.
How Spatial Disorientation Took Hold at Night
The final descent therefore represents a breakdown in the cockpit’s ability to maintain a reliable attitude reference. Once the aircraft entered a steep bank and descent at night, the crew’s perception of the aircraft diverged from its actual attitude. The case remains a powerful example of why upset-recovery training must account for the instrument systems a pilot will actually use in service.
A Captain Unfamiliar With the 737's Automation
The investigation of SU821 is especially important because the crew were operating a Boeing 737 with instrument displays and automation characteristics that were not fully familiar to the captain. The accident sequence developed during a night approach in cloud, when outside visual references were unavailable. Once the crew disengaged automation and began manually controlling the aircraft, the ability to maintain a reliable attitude reference became critical.
The throttle asymmetry issue also mattered because it added workload during an already demanding approach. Instead of a clean, stable descent, the crew were managing an airplane whose power levers were not behaving symmetrically while simultaneously interpreting attitude information. That does not make the mechanical issue the sole cause; it explains why the cockpit environment was more demanding when the loss of control began.
The presence of alcohol in the captain’s system is a documented investigative finding, but it should not be used as a sensational shortcut. The value of the case is the interaction between impairment, fatigue, unfamiliar instrumentation, automation changes, crew coordination and upset recovery. The accident became fatal when those factors converged during the final approach and the crew did not recover the aircraft from the steep bank and descent.
Research and reconstruction
Flight Follower Editorial Team
This reconstruction was researched from official investigation records where they exist, the original air traffic control recording, and contemporary reporting. The aircraft movement, timeline and written account were assembled independently by Flight Follower. Where an investigation is open or no probable cause has been published, the account says so rather than offering one.
About the Flight Follower team · Editorial policy · Corrections
Sources and investigation material
Accident Facts
- Incident date
- 13 Sep 2008
- Aircraft
- B737
- Flight
- SU821
- Category
- Crash, Unruly / Dispute
- Reconstruction
- 8:27