Ground accident of a Boeing KC-135R Stratotanker in Bishkek

Date & Time: Sep 26, 2006 at 2010 LT
Type of aircraft:
Operator:
Registration:
63-8886
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bishkek - Bishkek
MSN:
18734
YOM:
1964
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On Sept. 26, at approximately 8:03 p.m. local time, a KC-135R landed at Manas International Airport 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. The KC-135R was struck by a host nation TU-154 that was taking off. 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 with no additional damage to the aircraft. The three aircrew members on board the KC-135R, as well as the nine aircrew members and 52 passengers aboard the TU-154, survived the accident. None of the aircrew or passengers on board the TU-154 sustained any injuries. One KC-135 crew member sustained minor abrasions while evacuating the aircraft.
Probable cause:
The collision between the TU-154 and KC-135R aircraft was clearly an accident and not the result of any intentional conduct. The Accident Investigation Board, convened by AMC, determined that the accident was caused by the Kyrgyzaeronavigation air traffic controller who cleared a civilian airliner for takeoff without verifying that the KC-135R was clear of the runway. In addition to the air traffic controller, the AIB found evidence of several contributing factors involving the KC-135R aircrew, conflicting published airport notices, and a tower liaison employed by the U.S. Government to facilitate communication between the tower and U.S. aircrews. Although the AIB found the air traffic controller primarily at fault, the U.S. KC-135R crew and tower liaison shared responsibility for ensuring the KC-135R cleared the runway to a safe location following landing. The accident might have been avoided had any of them exercised better awareness of their situation.
In conclusion, 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.
The KC-135R is assigned to the 92nd Air Refueling Wing, Fairchild Air Force Base, Wash. While deployed at Manas AB, the KC-135R and its aircrew were assigned to U.S. Central Command's 376th Air Expeditionary Wing, flying missions supporting coalition aircraft over Afghanistan.
Final Report:

Crash of an Ilyushin II-62M in Bishkek

Date & Time: Oct 23, 2002 at 0457 LT
Type of aircraft:
Registration:
RA-86452
Flight Type:
Survivors:
Yes
Schedule:
Moscow - Bishkek
MSN:
16 22 2 1 2
YOM:
1976
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
34662
Aircraft flight cycles:
6060
Circumstances:
The aircraft departed Moscow-Domodedovo Airport on a positioning flight Bishkek-Manas Airport where cargo should be loaded. The water ballast tanks were not filled, causing the centre of gravity to be outside the allowed limits. After passing the outer marker on approach to runway 26, a 15-second period of oscillations started with changes in bank angle and heading (between 245° and 255°). The plane passed over the runway threshold at a height of 30 metres and at a speed of 293 km/h. At this point the altitude should have been 15 metres. At a height of 20 metres, at a speed of 297 km/h, the thrust reversers of the n°1 and 4 engines were deployed. This was contrary to regulations, which stipulate that thrust reversers may only be deployed at the leveling-off altitude of 5-8 metres. The nose then rose to a 7° pitch angle. This was caused by the activation of the thrust reversers and the centre of gravity which was too far aft. The pitch-up could not be countered by a 13° nose down elevator application. The plane finally touched down on the maingear wheels 1395 metres down the 4,200 metres long runway. The flight engineer, without telling the pilot in command, shut down the n°2 and 3 engines. With an elevator-down deflection of 10-11° and the stabilizer at -3,3° the crew were still not able to get the nose gear on the ground. After retracting the thrust reversers and with the elevator deflected in a 21° nose-down attitude, the nose pitched down from +7° to -2,5° in 2-3 seconds. The stabilizer was then trimmed from -3,3° to +9° which caused the pitch angle to increase again. The Ilyushin ran off the left side of the runway 3,001 metres past the runway threshold. The plane continued until colliding with a concrete obstruction. The aircraft caught fire and burned out almost completely.
Probable cause:
Wrong approach configuration on part of the flying crew, which caused the airplane to land too far down the runway. The following contributing factors were identified:
- Poor crew coordination,
- The pilot-in-command who was also the General Manager of the company, did not had sufficient training and qualifications to act in such position,
- Poor crew resources management,
- Poor flight and approach planning.

Crash of a Yakovlev Yak-40 in Osh

Date & Time: Oct 21, 2001
Type of aircraft:
Operator:
Registration:
EX-87470
Flight Phase:
Survivors:
Yes
Schedule:
Osh – Bishkek
MSN:
9441537
YOM:
1974
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
32
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll at Osh Airport, the captain decided to abort for unknown reasons. Unable to stop within the remaining distance, the aircraft verran and came to rest in a ravine. All 36 occupants evacuated safely while the aircraft was damaged beyond repair.

Crash of a Yakovlev Yak-40 in Jalal-Abad

Date & Time: Aug 14, 1998
Type of aircraft:
Operator:
Registration:
EX-87529
Survivors:
Yes
MSN:
9 52 11 41
YOM:
1975
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Jalal-Abad Airport, the aircraft was unable to stop within the remaining distance. It overran, lost its undercarriage and came to rest. There were no casualties but the aircraft was damaged beyond repair.

Crash of a Yakovlev Yak-40 in Jalal-Abad

Date & Time: Sep 15, 1989
Type of aircraft:
Operator:
Registration:
CCCP-87391
Survivors:
Yes
Schedule:
Bishkek - Jalal-Abad
MSN:
9 41 03 33
YOM:
1974
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following a wrong approach configuration, the crew completed the landing at an excessive speed in a nose-down attitude. Upon touchdown, the aircraft bounced three times then veered off runway and came to rest. All 30 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the flying crew.

Crash of a Yakovlev Yak-40 in Bishkek

Date & Time: Sep 2, 1989
Type of aircraft:
Operator:
Registration:
CCCP-87509
Survivors:
Yes
Schedule:
Jalal-Abad - Bishkek
MSN:
9 52 11 40
YOM:
1975
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
40
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While descending to Bishkek, the hydraulic systems failed at an altitude of 5,700 meters. The crew continued the approach when the captain informed ATC that he was unable to lower the gear. The crew completed a belly landing on a grassy area parallel to the main runway at Bishkek Airport. The aircraft slid on a certain distance before coming to rest. While all 43 occupants were uninjured, the aircraft was considered as damaged beyond repair.
Probable cause:
Failure of the main hydraulic system due to the loss of the cap of the hydraulic tank caused by the destruction of the nut due to fatigue caused by structural and manufacturing faults.

Crash of a PZL-Mielec AN-2 near Frunze

Date & Time: Apr 8, 1986
Type of aircraft:
Operator:
Registration:
CCCP-56375
Flight Phase:
MSN:
1G180-54
YOM:
1978
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances near Frunze after the crew failed to follow the minimum safe altitude. Occupant fate unknown.

Crash of a Yakovlev Yak-40 in Osh

Date & Time: Jun 29, 1983
Type of aircraft:
Operator:
Registration:
CCCP-87808
Survivors:
Yes
Schedule:
Bishkek - OSh
MSN:
9 23 18 23
YOM:
1972
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While cruising at an altitude of 7,200 meters over the city of Kazarman on a flight from Bishkek to Osh, the aircraft encountered severe downdrafts and entered an uncontrolled descent during which it lost 2,200 meters and recorded excessive loads of +5.5 g. The crew finally took over control of the airplane and landed safely at Osh Airport. Nevertheless, the aircraft became unserviceable following irreparable structural damages. All nine occupants were injured.
Probable cause:
In-flight structural damages caused by severe downdrafts in altitude.

Crash of a PZL-Mielec AN-2R near Jalal-Abad: 2 killed

Date & Time: Feb 18, 1979 at 1231 LT
Type of aircraft:
Operator:
Registration:
CCCP-07837
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Jalal-Abad – Komsomol
MSN:
1G169-52
YOM:
1976
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Aircraft flight hours:
2002
Aircraft flight cycles:
6845
Circumstances:
The crew was completing a positioning flight from Jalal-Abad to the "Komsomol" Airstrip in the Bazar-Kurgan district of the Osh region. nine minutes after takeoff, he encountered below-minima weather conditions (low clouds and fog) over the Kara-Kiyakyr Mountain Range. The decision to return was taken too late so the aircraft entered a layer of fog and crashed at a height of 970 metres into the slope of a mountain (1,163 metres high) located west of Suzak (at N40°53' E72°51', some 10.5 km southwest of Jalal-Abad Airport). One of the two pilots and the sole passenger (an aircraft mechanic) were killed and the sole survivor was injured.
Probable cause:
Decision of the captain to continue the flight in below-minima weather conditions and his decision to return was too late. It was also reported that ATC failed to inform the crew about the minimum safe altitude in the area and the fact that weather conditions deteriorated en route. Finally, weather bulletin published by meteorologist were incomplete.

Crash of an Antonov AN-2 near Talas

Date & Time: Jul 2, 1978
Type of aircraft:
Operator:
Registration:
CCCP-02190
Flight Phase:
Survivors:
Yes
Schedule:
Talas - Frunze
MSN:
112247314
YOM:
1959
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route, the engine malfunctioned then failed. The crew reduced his altitude and attempted an emergency landing in a field. There were no injuries while the aircraft was written off.
Probable cause:
Engine failure in flight for undetermined reasons.