Incident Overview

Date: Monday 20 June 2011
Aircraft Type: Tupolev Tu-134A-3
Owner/operator: RusLine, lsf RusAir
Registration Number: RA-65691
Location: 1 km S of Petrozavodsk Airport (PES) – ÿ Russia
Phase of Flight: Approach
Status: Destroyed, written off
Casualties: Fatalities: 47 / Occupants: 52
Component Affected: Aircraft ? Specifically, the Tu-134A Tupolev aircraft.Aircraft ? Specifically, the Tu-134A Tupolev aircraft.
Investigating Agency: MAKMAK
Category: Accident
A RusLine Tu-134A, operated by RusAir, crashed while on approach to Petrozavodsk Airport, Russia, resulting in the loss of 47 lives and the survival of 5. The flight departed Moscow-Domodedovo (DME) at 22:24 on a domestic service to Petrozavodsk. Due to insufficient seating capacity for the route, RusAir was chartered to operate the flight using a Tu-134. The aircraft struck trees and crashed on a highway while on final approach to runway 01, breaking up and coming to rest approximately 390 meters to the right of the runway’s extended centerline and 570 meters short of the runway threshold. The crew failed to decide to go-around, instead descending below the minimum safe altitude due to poor visual contact and lack of navigational awareness.A RusLine Tu-134A, operated by RusAir, crashed while on approach to Petrozavodsk Airport, Russia, resulting in the loss of 47 lives and the survival of 5. The flight departed Moscow-Domodedovo (DME) at 22:24 on a domestic service to Petrozavodsk. Due to insufficient seating capacity for the route, RusAir was chartered to operate the flight using a Tu-134. The aircraft struck trees and crashed on a highway while on final approach to runway 01, breaking up and coming to rest approximately 390 meters to the right of the runway’s extended centerline and 570 meters short of the runway threshold. The crew failed to decide to go-around, instead descending below the minimum safe altitude due to poor visual contact and lack of navigational awareness.

Description

RusLine flight 9605, a Tupolev Tu-134A, crashed while on approach to Petrozavodsk Airport, Russia, killing 47 occupants; 5 survived the accident. Flight 9605 had departed Moscow-Domodedovo (DME) at 22:24 on a domestic service to Petrozavodsk. The flight was operated by RusAir on behalf of RusLine. Flight RLU-243 could not be operated by RusLine’s Canadair Regional Jets because it lacked the seating capacity needed for the service between Domodedovo and Petrozavodsk.Therefor RusAir was chartered to operate the flight using a Tu-134. The Tupolev struck trees and crash-landed on a highway while on final approach to runway 01. It broke up and came to rest about 390 metres to the right of the runway’s extended centreline and 570 m short of the runway threshold. CONCLUSION: The airplane flew an approach in conditions worse than weather minimums for the airfield and the crew failed decide to go-around. Instead the airplane descended below the minimum safe altitude in the absence of visual contact with approaching lighting and landmarks, which led to contact with trees and the ground in controlled flight. Contributing factors were: – Poor interaction of the crew and poor crew resource management (CRM) from the commander of the flight during the approach. The pilot subordinated himself to the navigator causing the co-pilot to be effectively excluded from decisions. – The use during the flight of a navigator in a light level of alcoholic intoxication – Incorrect weather forecast with regards to height of the cloud base, visibility and severe weather – fog. – The use of navigation equipment that used satellite navigation to determine the aircrafts position, which was in violation of the Flight Manual Supplement for the Tu-134.

Primary Cause

Insufficient seating capacity on the flight, leading to a decision to operate with a less capable aircraft (Tu-134) instead of a Canadair Regional Jet.Insufficient seating capacity on the flight, leading to a decision to operate with a less capable aircraft (Tu-134) instead of a Canadair Regional Jet.

Share on:

Leave a Reply

Your email address will not be published. Required fields are marked *