Crash of a Lockheed C-130H Hercules in Baghdad

Date & Time: Jun 27, 2008 at 1235 LT
Type of aircraft:
Operator:
Registration:
86-0412
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
5098
YOM:
1987
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
34
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine aircraft departed Baghdad Airport on a support mission, carrying 32 passengers and a crew of six. Sixty seconds after takeoff, while climbing to a height of 313 feet and at a speed of 163 knots, the airplane's defensive system activated. The pilot reacted in accordance with applicable directives and after reacting to the defensive alert, the crew realized that all three engines n°1, 3 and 4 lost 60% of power. The crew attempted an emergency landing in an open field located 7,5 km north of the airport. The aircraft was damaged beyond repair and all 38 occupants escaped uninjured. U.S. Air Force Maintenance and Explosive Ordnance Disposal personnel from the 447th Air Expeditionary Group were called in. They placed explosive charges on the plane and blew up the Hercules on July 7.
Probable cause:
The Board President could not find clear and convincing evidence to determine the exact cause of the engine power loss. He did find evidence to conclude that several factors combined to significantly contribute to the Mishap Airplane (MA) landing partially gear down. Specifically, a defensive system alert, the aircraft's low altitude and airspeed at the time of the malfunction, and the decision to respond to the alert at low altitude and airspeed combined to result in the MA landing partially gear down. All MA systems and performance were normal prior to the defensive system alert. An undetermined malfunction occurred during the defensive reaction that caused three of the MA's four engines to stabilize at an RPM (60%) which was not sufficient to maintain flight and the low altitude and airspeed at the time of the malfunction limited the time available for situation analysis and recovery. The Mishap Crew (MC) had never been exposed to a loss of three or four engines on takeoff in the C-130H2 simulator which resulted in an emergency situation the MC had not seen before at a low altitude and airspeed. Checklist actions taken by the MC did not recover the engines and the Mishap Pilot (MP) appropriately performed a limited power, controlled descent, and forced landing resulting in only minor injuries.

Crash of Beechcraft T-1A Jayhawk in Lubbock

Date & Time: May 21, 2008 at 2144 LT
Type of aircraft:
Operator:
Registration:
93-0633
Flight Type:
Survivors:
Yes
Schedule:
Lubbock - Lubbock
MSN:
TT-90
YOM:
1993
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a night training flight on behalf of the U.S. Air Force 86th Flying Training Squadron, 47th Flying Training Wing, Laughlin Air Force Base, Texas. After several manoeuvres in the vicinity of the Lubbock-Preston Smith Airport, the crew started an non precision approach to runway 17R. At that time, weather conditions were not so good with rain showers and winds up to 40 knots. On final approach, the aircraft seems to sink and pitched down. The captain increased both engines power but the aircraft hit the ground 1,1 mile short of runway 17R threshold. On impact, the nose gear was sheared off and the aircraft came to rest in a field. Both pilots were slightly injured while the aircraft was damaged beyond repair.
Probable cause:
Conjunction of poor weather conditions and crew errors. The aircraft encountered windshear with downburst on descent and the crew ignored warnings. The combination of the following human factors placed the aircraft in a dangerous weather environment: poor mission planning, inattention, complacency, lack of procedural knowledge and restricted vision.

Crash of a Learjet C-21A in Decatur

Date & Time: Oct 2, 2006 at 1215 LT
Type of aircraft:
Operator:
Registration:
84-0066
Flight Type:
Survivors:
Yes
Schedule:
Decatur - Decatur
MSN:
35-512
YOM:
1984
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing a local training flight at Decatur Airport, consisting of touch-and-go maneuvers. On final approach to runway 24, the instructor elected to simulate a failure of the right engine. Anticipating the touch-and-go procedure, the instructor deactivated the yaw damper system while the aircraft was about 10-20 feet above the runway. As the speed increased, the instructor called out 'speed' twice when the copilot reduced the power on the left engine. The aircraft rolled to the right, causing the right wingtip to struck the ground. The aircraft went out of control, veered off runway and came to rest, bursting into flames. Both pilots escaped with minor injuries while the aircraft was destroyed.
Probable cause:
The crew’s failure to take appropriate action after allowing the aircraft to get 15 knots [17 mph] slow over the runway threshold. Had either pilot taken proper action to go around upon seeing the airspeed bleeding away by advancing power on both engines, this mishap could have been avoided.

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 a Lockheed C-5B Galaxy at Dover AFB

Date & Time: Apr 3, 2006 at 0642 LT
Type of aircraft:
Operator:
Registration:
84-0059
Flight Type:
Survivors:
Yes
Schedule:
Dover – Ramstein – Koweït City
MSN:
500-0083
YOM:
1986
Crew on board:
14
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine aircraft departed Dover AFB at 0621LT on a flight to Kuwait City with an intermediate stop at Ramstein Airbase, Germany, carrying 17 people, three passengers and 14 crew members. Ten minutes into the flight, the copilot informed ATC about technical problems and was cleared for an immediate return. On final approach to runway 32, the aircraft descended below the glide and impacted ground few hundred metres short of runway. It came to rest in a prairie, broken in three. All 17 occupants were injured.
Probable cause:
Based on clear and convincing evidence, the Board President determined the primary cause of the mishap was the pilots' and flight engineers' failure to use the number three, fully operational, engine; the instructor's and primary flight engineer's failure to brief, and the pilots' failure to consider or utilize a 62.5 or 40% flap setting (instead of a 100% flap setting); and the pilots' attempt at a visual approach to runway 32, descending well below a normal glidepath for an instrument-aided approach or the normal VFR pattern altitude of 1,800 ft. There is substantial evidence that a contributing factor to this mishap was MP1's failure to give a complete approach briefing, in that, nonstandard factors, configuration, landing distance, and missed approach intentions were not addressed.

Crash of a Lockheed MC-130H Hercules near Gramsh: 9 killed

Date & Time: Mar 31, 2005 at 2000 LT
Type of aircraft:
Operator:
Registration:
87-0127
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Tirana - Tirana
MSN:
5118
YOM:
1987
Location:
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
9
Circumstances:
Assigned to the 352nd Special Operations Group based at RAF Mildenhall, the four engine aircraft departed Tirana-Rinas Airport in the evening for a night training mission with the Albanian Army. While flying at low height, about 300 feet above the ground by night and using night-vision goggles, the crew elected to gain height while approaching a ridge. Unable to climb, the aircraft stalled and crashed in hilly and snow covered terrain. The aircraft was destroyed and all nine occupants were killed.
Probable cause:
The accident investigation board determined that the crew's loss of situational awareness placed the aircraft in too low a climb with respect to the surrounding mountainous terrain. Responding to the situation, the crew did not use all available power and stalled the aircraft during a turning climb. This resulted in a loss of aircraft control and almost immediate crash.