ASN Aircraft accident Boeing KC-135R Stratotanker 63-8886 Bishkek Airport (FRU)
ASN logo
 

Status:Information is only available from news, social media or unofficial sources
Date:Tuesday 26 September 2006
Time:20:10
Type:Silhouette image of generic K35R model; specific model in this crash may look slightly different
Boeing KC-135R Stratotanker
Operator:United States Air Force - USAF
Registration: 63-8886
MSN: 18734/717
First flight: 1964-09-09 (42 years )
Engines: 4 CFMI F108-CF-100
Crew:Fatalities: 0 / Occupants: 3
Passengers:Fatalities: 0 / Occupants: 0
Total:Fatalities: 0 / Occupants: 3
Aircraft damage: Substantial
Aircraft fate: Written off (damaged beyond repair)
Location:Bishkek Airport (FRU) (   Kyrgyzstan)
Phase: Landing (LDG)
Nature:Military
Departure airport:?
Destination airport:Bishkek-Manas International Airport (FRU/UAFM), Kyrgyzstan
Narrative:
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.

Probable Cause:

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.

Classification:
Language/communication problems
Runway incursion
Runway mishap

Sources:
» KC-135 Accident Investigation Board complete (Air Mobility Command Public Affairs, 20-12-2006)
» Kyrgyz aircraft collision: No injuries
» Kyrgyz presidential jet damaged in collision with U.S. tanker - 1 (RIA Novosti 27-9-2006)
» ruffled feathers (Air Force Times 28-09-2006)


Photos

photo of Boeing-KC-135R-Stratotanker-63-8886
 
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

Share

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

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org