Tupolev Tu-154M – EX-85718

Incident Overview

Date: Tuesday 26 September 2006

Aircraft Type: Tupolev Tu-154M

Owner/operator: Altyn Air

Registration Number: EX-85718

Location: Bishkek Airport (FRU) – ÿ Kyrgyzstan

Phase of Flight: Take off

Status: Substantial, repaired

Casualties: Fatalities: 0 / Occupants: 61

Component Affected: KC-135R’s left wing, KC-135R’s engine, and the KC-135R’s fairing.KC-135R’s left wing, KC-135R’s engine, and the KC-135R’s fairing.

Category: Accident

A USAF Boeing KC-135R Stratotanker incident occurred at Bishkek (FRU) on 20:03 following a combat mission over Afghanistan. A Tupolev 154M of Altyn Air (EX-85718) was cleared for takeoff on runway 08. During the landing, a collision between the KC-135R and the Tupolev 154M resulted in significant damage to the KC-135R. The collision damaged the KC-135R’s left wing and nearly severed its engine. The TU-154 lost approximately six feet of its right wingtip, but remained airborne and returned to the airport for an emergency landing. The KC-135R sustained extensive damage, including fire and extensive damage to its left wing. The incident was attributed to a conflict between the Kyrgyz air traffic controller’s instructions regarding runway usage, a discrepancy between a NOTAM and the KC-135R’s clearance, and a lack of situational awareness among the Kyrgyz controller and LNO. The LNO failed to adequately address the conflicting instructions and failed to properly read back the KC-135R’s response.A USAF Boeing KC-135R Stratotanker incident occurred at Bishkek (FRU) on 20:03 following a combat mission over Afghanistan. A Tupolev 154M of Altyn Air (EX-85718) was cleared for takeoff on runway 08. During the landing, a collision between the KC-135R and the Tupolev 154M resulted in significant damage to the KC-135R. The collision damaged the KC-135R’s left wing and nearly severed its engine. The TU-154 lost approximately six feet of its right wingtip, but remained airborne and returned to the airport for an emergency landing. The KC-135R sustained extensive damage, including fire and extensive damage to its left wing. The incident was attributed to a conflict between the Kyrgyz air traffic controller’s instructions regarding runway usage, a discrepancy between a NOTAM and the KC-135R’s clearance, and a lack of situational awareness among the Kyrgyz controller and LNO. The LNO failed to adequately address the conflicting instructions and failed to properly read back the KC-135R’s response.

Description

A USAF Boeing KC-135R Stratotanker had landed at Bishkek (FRU) at 20:03 following a combat mission over Afghanistan. After landing, the KC-135R was parked at the intersection of the active runway and a taxiway while the crew awaited clarification on instructions from the air traffic control tower. Meanwhile, a Tupolev 154M of Altyn Air (EX-85718) had been cleared for takeoff on runway 08. The TU-154’s right wing struck the fairing of the KC-135R’s No. 1 engine. The force of the impact nearly severed the No. 1 engine from KC-135R and destroyed a portion of the aircraft’s left wing. The TU-154 lost approximately six feet of its right wingtip, but was able to get airborne and return to the airport for an emergency landing. The KC-135 caught fire and sustained extensive damage. Although the AIB determined the principal cause of the mishap was the Kyrgyzaeronavigation controller clearing the TU-154 for takeoff without verifying that KC-135R was clear of the runway, there was evidence the following factors also contributed to the mishap: – The Kyrgyz air traffic controller’s instruction to vacate at taxiway Golf after dark conflicted with a published Notice to Airmen (NOTAM) that limited that taxiway’s use to daylight hours. The contractor safety liaison (LNO) employed by the U.S. Air Force to facilitate communication between its aircrews and Kyrgyz controllers did not clarify the apparent discrepancy. – After questioning the Kyrgyz controller’s instruction to vacate the runway at taxiway Golf, the LNO instructed the KC-135R crew to hold short of Alpha. The mishap KC-135R crew misperceived the LNO’s instructions and responded “holding short of Golf.” The LNO failed to catch the read-back error. – The Kyrgyz controller failed to maintain awareness of the KC-135R’s location. – The LNO failed to maintain situational awareness and intervene when the controller’s actions endangered the KC-135R and aircrew.

Primary Cause

Conflict between Kyrgyz air traffic controller instructions regarding runway usage, a discrepancy between a NOTAM and the KC-135R’s clearance, and a lack of situational awareness among the Kyrgyz controller and LNO.Conflict between Kyrgyz air traffic controller instructions regarding runway usage, a discrepancy between a NOTAM and the KC-135R’s clearance, and a lack of situational awareness among the Kyrgyz controller and LNO.

Share on: