Crash of a Beechcraft MC-12W Liberty in Afghanistan: 3 killed

Date & Time: Jan 9, 2014
Type of aircraft:
Operator:
Registration:
N195AE
Flight Phase:
Survivors:
No
Site:
MSN:
FA-195
YOM:
1989
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The twin engine aircraft was performing a special mission with a crew of two and a member of the ISAF on board. The accident occurred in unknown circumstances somewhere in the east part of Afghanistan. The aircraft was destroyed and all three occupants were killed. There are no indications that the aircraft was brought down by enemy fire, said a Defense official. It was later reported that the airplane involved was completing an Air Medium-Altitude Reconnaissance and Surveillance System (MARSS) mission.

Crash of a Lockheed C-130J-30 Super Hercules at Shank AFB

Date & Time: May 19, 2013 at 1420 LT
Type of aircraft:
Operator:
Registration:
04-3144
Flight Type:
Survivors:
Yes
Schedule:
Kandahar – Shank AFB
MSN:
5560
YOM:
2004
Location:
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
904.00
Copilot / Total hours on type:
252
Circumstances:
On 19 May 2013, at approximately 0950 Zulu (1420 local), a C-130J, tail number (T/N) 04-3144, assigned to the 41st Airlift Squadron, 19th Airlift Wing, Little Rock Air Force Base (AFB), Arkansas, ran off the end of a runway at Forward Operating Base (FOB) Shank, Northeast, Afghanistan, struck a ditch which collapsed the nose gear and eventually ripped the right main landing gear from the fuselage. The right outboard engine struck the ground, pressurized fuel and oil lines were broken, fluid was sprayed over the cracked engine casing, and the right wing caught fire. The mishap aircraft (MA) came to a full stop at approximately 544 feet (ft) off the end of the paved runway surface. The mishap crew (MC), Aeromedical Evacuation (AE) crew and two ambulatory patients safely evacuated the aircraft through the top flight-deck emergency escape hatch meeting 600 ft off the nose of the aircraft. There were no fatalities, significant injuries or damage to civilian property. The total estimated loss is $73,990,265. The MA was on an AE mission and included five active duty C-130J crewmembers from the 772nd Expeditionary Airlift Squadron (19th Airlift Wing deployed), Kandahar Air Base (AB), Afghanistan. Additionally, the MA had aboard six reserve AE crewmembers from the 651st Expeditionary Aeromedical Evacuation Squadron (349th Air Mobility Wing and 433rd Airlift Wing deployed), Kandahar AB, Afghanistan. The mishap sortie happened on the third of five planned legs that day to an airfield that was at 6,809 ft Mean Sea Level (MSL) and experiencing winds varying from 200 to 250 degrees gusting from 6 to 28 knots. On the second attempted landing, the MA touched down approximately 1,500 ft down the runway but was 27 knots indicated airspeed (KIAS) faster than computed touchdown landing speed leading to the aircraft going off the end of the runway at approximately 49 KIAS.
Probable cause:
On the second landing attempt at a high altitude airfield (6,809 ft MSL), poor CRM coupled with a late power reduction by MP1 caused the MA to touchdown 27 KIAS faster than computed touchdown landing speed leading to the aircraft going off the end of the runway at approximately 49 KIAS. Because of unique aircraft performance characteristics when operating into and out of high altitude airfields, there was no way that the MA could perform a 50% flap landing (in accordance with T.O. 1C-130(C)J-1-1 landing assumptions, nose wheel landing gear speed restrictions and power level transition speed restrictions) at FOB Shank and land 27 KIAS fast. The MA’s actual landing speed simply overtasked the aircrafts capability to stop within the runway available.
Several factors substantially contributed to this mishap, including:
- Channelized attention,
- Risk assessment during operation,
- Delayed necessary action,
- Response set,
- Procedural error.
Final Report:

Crash of a Boeing 747-428BCF at Bagram AFB: 7 killed

Date & Time: Apr 29, 2013 at 1527 LT
Type of aircraft:
Operator:
Registration:
N949CA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Camp Bastion - Bagram AFB - Dubaï
MSN:
25630/960
YOM:
1993
Flight number:
NCR102
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
6000
Captain / Total hours on type:
440.00
Copilot / Total flying hours:
1100
Copilot / Total hours on type:
209
Circumstances:
The aircraft crashed shortly after takeoff from Bagram Air Base, Bagram, Afghanistan. All seven crewmembers—the captain, first officer, loadmaster, augmented captain and first officer, and two mechanics—died, and the airplane was destroyed from impact forces and postcrash fire. The 14 Code of Federal Regulations Part 121 supplemental cargo flight, which was operated under a multimodal contract with the US Transportation Command, was destined for Dubai World Central - Al Maktoum International Airport, Dubai, United Arab Emirates. The airplane’s cargo included five mine-resistant ambush-protected (MRAP) vehicles secured onto pallets and shoring. Two vehicles were 12-ton MRAP all-terrain vehicles (M-ATVs) and three were 18-ton Cougars. The cargo represented the first time that National Airlines had attempted to transport five MRAP vehicles. These vehicles were considered a special cargo load because they could not be placed in unit load devices (ULDs) and restrained in the airplane using the locking capabilities of the airplane’s main deck cargo handling system. Instead, the vehicles were secured to centerline-loaded floating pallets and restrained to the airplane’s main deck using tie-down straps. During takeoff, the airplane immediately climbed steeply then descended in a manner consistent with an aerodynamic stall. The National Transportation Safety Board’s (NTSB) investigation found strong evidence that at least one of the MRAP vehicles (the rear M-ATV) moved aft into the tail section of the airplane, damaging hydraulic systems and horizontal stabilizer components such that it was impossible for the flight crew to regain pitch control of the airplane. The likely reason for the aft movement of the cargo was that it was not properly restrained. National Airlines’ procedures in its cargo operations manual not only omitted required, safety-critical restraint information from the airplane manufacturer (Boeing) and the manufacturer of the main deck cargo handling system (Telair, which held a supplemental type certificate [STC] for the system) but also contained incorrect and unsafe methods for restraining cargo that cannot be contained in ULDs. The procedures did not correctly specify which components in the cargo system (such as available seat tracks) were available for use as tie-down attach points, did not define individual tie-down allowable loads, and did not describe the effect of measured strap angle on the capability of the attach fittings.
Probable cause:
The NTSB determines that the probable cause of this accident was National Airlines’ inadequate procedures for restraining special cargo loads, which resulted in the loadmaster’s
improper restraint of the cargo, which moved aft and damaged hydraulic systems No . 1 and 2 and horizontal stabilizer drive mechanism components, rendering the airplane uncontrollable. Contributing to the accident was the FAA’s inadequate oversight of National Airlines’ handling of special cargo loads.
Final Report:

Crash of a Beechcraft MC-12W 204 km NE of Kandahar: 4 killed

Date & Time: Apr 27, 2013 at 1243 LT
Type of aircraft:
Operator:
Registration:
09-0676
Flight Phase:
Survivors:
No
Site:
Schedule:
Kandahar - Kandahar
MSN:
FL-676
YOM:
2008
Flight number:
Independence 08
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1749
Captain / Total hours on type:
242.00
Copilot / Total flying hours:
2434
Copilot / Total hours on type:
38
Circumstances:
On 27 April 2013, at approximately 1243 local time (L) in Afghanistan, an MC-12W, tail number 09-0676 impacted terrain 110 nautical miles northeast of Kandahar Airfield (KAF) while on a combat intelligence, surveillance, and reconnaissance (ISR) mission. The four crewmembers on board were the Mishap Mission Commander (MMC), Mishap Pilot (MP), Mishap Sensor Operator (MSO), and Mishap Tactical Systems Operator (MTSO). The four airmen were killed instantly on impact and the Mishap Aircraft (MA), valued at $19.8 million, was destroyed. The crew and MA were deployed to the 361st expeditionary Reconnaissance Squadron, 451st Air Expeditionary Wing, KAF, Afghanistan. The MA, callsign Independence 08, departed KAF at 1157L and entered orbit at 1229L. The MA encountered deteriorating weather in the orbit and was climbing from 20,000 to 23,000 feet mean sea level (MSL) at 1241L to fly above the weather when the mishap occurred. In addition, the crew had found an enemy combatant and was in the process of adjusting their orbit to enhance mission success.
Probable cause:
Accident Investigation Board was conducted by USAF Brigadier General Donald J. BACON. His conclusion were as follow:
I find by clear and convincing evidence the cause of the mishap was a stall due to insufficient airspeed, while in a climbing left turn, which developed into a left spin followed quickly by a high-speed spiral, from which the crew was unable to recover. Additionally, I find, by a preponderance of evidence, each of the following three factors substantially contributed to the mishap:
orbit weather that impeded visibility and masked the horizon;
pilot inexperience in the MC-12W;
known MC-12W program risks associated with sustaining required combat capability in theater.
Final Report:

Crash of an Antonov AN-12TB in Shindand

Date & Time: Oct 19, 2012 at 1800 LT
Type of aircraft:
Operator:
Registration:
EK-12112
Flight Type:
Survivors:
Yes
MSN:
01 347 907
YOM:
1971
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine aircraft was completing a cargo flight to the Shindand AFB, carrying a load of 4'700 pounds of voting documents intended to the US soldiers based at Shindand AFB. For unknown reasons, the aircraft landed hard and bounced. On the second touchdown, the left main gear was torn off. The aircraft slid for about 1,750 metres then veered off runway to the left and came to rest in a drainage ditch. While all six occupants escaped uninjured, the aircraft was destroyed by impact and a post impact fire. US Federal Voting Assistance Program published a notice on 24OCT2012, informing that mail consisted of voting documents for US soldiers covering the US Presidential Election of 06NOV2012.

Crash of a McDonnell Douglas MD-83 in Kandahar

Date & Time: Jan 24, 2012 at 0828 LT
Type of aircraft:
Operator:
Registration:
EC-JJS
Survivors:
Yes
Schedule:
Dubai - Kandahar
MSN:
49793/1656
YOM:
1989
Flight number:
SWT094
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
86
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4946
Captain / Total hours on type:
3228.00
Copilot / Total flying hours:
2881
Copilot / Total hours on type:
2222
Circumstances:
On Tuesday, 24 January 2012, a McDonnell Douglas MD-83, registration EC-JJS and operated by Swiftair, took off from the Dubai Airport (United Arab Emirates) at 02:08 UTC on a scheduled flight to the Kandahar Airport (Afghanistan). Its callsign was SWT094 and there were 86 passengers (one of them a company mechanic), three flight attendants and two cockpit crew onboard. Swiftair, S.A. was operating this regularly scheduled passenger flight under an ACMI arrangement with the South African company Gryphon Airlines. The crew was picked up at its usual hotel in the emirate of Ras al-Khaimah (United Arab Emirates) at 21:00. The airplane was parked in the Ras al-Khaimah airport and had to be flown empty to the Dubai Airport. This flight departed at 00:20 UTC en route to Dubai. Once there, an agent for Gryphon Airlines gave the crew the documentation for the flight to Kandahar. They went through customs at the Dubai Airport, boarded the passengers and the cargo and refueled the airplane with enough fuel to make the return the flight, a typical practice so as to avoid refueling in Kandahar. The airplane took off from runway 30R at the Dubai Airport at 02:08 on standard instrument departure RIKET2D and climbed to flight level FL290. The first officer was the pilot flying. At 03:42, while over SERKA, they were transferred to Kabul control, which instructed them to descend to FL280. The crew reported its ISAF callsign (ISF39RT) to this ATS station, which allowed the aircraft to fly over Afghan airspace, and entered the new stipulated squawk code. Kabul Control instructed the crew to follow some radar vectors that took them to point SODAS, where they were transferred to Kandahar Control at 03:46. The crew reduced the airspeed to 250 kt above this point. Kandahar Control cleared them for an RNAV (GPS) approach to runway 05, providing a direct vector to point FALOD (the IAF), and to descend to 6,000 ft. The weather information provided on the ATIS “F” broadcast was runway in use 05, wind from 060º at 17 kt gusting to 24 kt, visibility 1,200 m, scattered clouds at 2,700 ft and broken clouds at 3,000 ft, temperature 1 ºC, dewpoint -7 ºC and QNH 30.06 in Hg (1,018 mbar). This information was practically the same as that radioed to the crew by the Kandahar control tower a few minutes before landing: wind from 060 at 15 kt gusting to 21 kt. They reached point FALOD (IAF) under cloud cover (and thus in IMC conditions). They did not exit the clouds until 1,500 ft before minimums which, for this approach, according to the associated chart, was an altitude of 3,700 ft, or 394 ft AGL. They established visual contact with the runway 500 ft above minimums and noted that they were a little right of the runway centerline. Since the captain had more operational experience at the destination airfield, he decided to take over the controls and fly the last phase of the approach maneuver. The PAPI was out of service, meaning that in final approach they only had visual references to the runway and over the ground. During short final they corrected the deviation from the runway centerline by adjusting their path from right to left. They landed at 03:58. During the flare, the crew noticed the airplane was shifting to the left, threatening to take them off the runway, as a result of which the captain applied a right roll angle. This caused the right wing tip to strike the ground before the wheels made contact with the ground. The captain regarded the maneuver as a hard landing, although the first officer thought they might have struck the runway. The autopilot was engaged until visual contact was established with the runway and the auto-throttle until the landing. On exiting the runway, the airport control tower personnel (who had witnessed the contact with the ground) ordered the crew to stop and informed them of the damage they had seen during the landing. They dispatched the emergency services (firefighters), which forced them to turn off their engines. Once it was confirmed that there was no fuel leak or damage to the wheels or brakes, they allowed the crew to restart the engines and proceed to the stand. The wing made contact with the ground some 20 m prior to the threshold, resulting in five threshold lights being destroyed by the aircraft and in damage to the aircraft’s right wing. According to the crew’s statement, the passengers were not really aware of the contact between the wing and the ground and they were subsequently disembarked normally.
Probable cause:
The accident was likely caused by the failure to observe the company's operating procedures and not executing a go-around when the approach was clearly not stabilized. Moreover, the operator lacked the authorization (and the crew the training) to carry out the RNAV (GPS) approach maneuver that was conducted at RWY 05 of the Kandahar Airport.
Contributing to the accident was:
The inoperable status of the PAPI at runway 05 of the Kandahar Airport, which was thus unable to aid the crew to establish the aircraft on the correct descent slope.
Final Report:

Crash of a PZL-Mielec C-145A Skytruck in Walan Rabat

Date & Time: Dec 18, 2011 at 1502 LT
Type of aircraft:
Operator:
Registration:
08-0319
Flight Type:
Survivors:
Yes
Schedule:
Kandahar - Qalat - Walan Rabat - Qalat - Kandahar
MSN:
AJE003-19
YOM:
2009
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3546
Captain / Total hours on type:
434.00
Copilot / Total flying hours:
982
Copilot / Total hours on type:
677
Aircraft flight hours:
1164
Aircraft flight cycles:
1273
Circumstances:
At 0939 hours Zulu time on 18 December 2011, an M-28, Tail Number 08-0319, departed Kandahar Air Base, Afghanistan on a mission to pick up four passengers at Qalat, Afghanistan, transport them to Walan Rabat short takeoff and landing zone, transport two additional personnel from Walan Rabat back to Qalat, then return to Kandahar Air Base. The mishap aircraft and crew were assigned or attached to the 318th Special Operations Squadron, 27th Special Operations Wing at Cannon Air Force Base, New Mexico, and were deployed to the 318th Expeditionary Special Operations Squadron at Kandahar Air Base, Afghanistan. After an uneventful stop at Qalat to onload four passengers and their bags, the mishap crew flew a 20-minute leg to Walan Rabat. Surface winds at Walan Rabat were 190 degrees at 14 knots gusting to 17 knots, 30 degrees off a direct tailwind for runway 34. Because the landing zone has a three percent upslope for runway 34, and a 1,500-foot mountain exists 1½ miles to the north, the pilot elected to land with a tailwind on runway 34, the preferred landing direction. Walan Rabat Landing Zone is a 1,756-foot long, 31-foot wide, semi-prepared dirt strip with poorly defined boundaries. The landing zone was marked with AMP-3 markings, commonly called a “box-and-one” with colored panels. The mishap pilot consulted a wind component chart and incorrectly calculated the tailwind component, mistakenly believing it was within the allowable limit for landing the M-28. The pilot flew a shallow 2½-3 degree approach due to the upsloping landing zone. At approximately 1,000 feet short of the landing zone, the mishap pilot visually acquired the AMP-3 markings and landed the mishap aircraft at 1032 zulu. After a firmer than normal landing, the aircraft veered to the right and departed the prepared surface. The nose gear encountered uneven terrain and collapsed, causing the mishap aircraft to flip tail-over-nose. The mishap crew and passengers then egressed the aircraft through the copilot’s window. There were no serious injuries to crew or passengers. The mishap aircraft, which was valued at approximately $12,300,000 was destroyed. There were no civilian casualties.
Probable cause:
The AIB president found no clear and convincing evidence of the primary cause of the accident. He determined by a preponderance of evidence that the Landing Zone Condition, Cross-Monitoring Performance, Task/Mission-in-Progress Re-planning, Landing with an Excessive Tailwind, and Aircraft Engine Anomalies substantially contributed to the mishap, ultimately causing the mishap aircraft to veer off the prepared surface into rough terrain, resulting in the collapse of the nose landing gear and destruction of the aircraft.
Final Report:

Crash of an Ilyushin II-76TD near Bagram AFB: 9 killed

Date & Time: Jul 6, 2011 at 0010 LT
Type of aircraft:
Operator:
Registration:
4K-AZ55
Flight Type:
Survivors:
No
Site:
Schedule:
Baku - Bagram AFB
MSN:
20534 20680
YOM:
2005
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
9
Circumstances:
The four engine aircraft departed Baku-Bina Airport at 2126LT on a cargo flight to Bagram AFB, carrying 9 crew members and a load of 18 tons of various goods destined to the NATO forces deployed in Afghanistan. While approaching Bagram AFB by night, at an altitude of 12,500 feet, the aircraft impacted the slope of a mountain located 25 km from the airport. The wreckage was found at the first light of day. The aircraft was destroyed and all 9 occupants were killed.

Crash of a Lockheed L-382E-20C Hercules near Kabul: 8 killed

Date & Time: Oct 12, 2010 at 1950 LT
Type of aircraft:
Operator:
Registration:
5X-TUC
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Bagram - Kabul
MSN:
4362
YOM:
1969
Flight number:
NCR662
Location:
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The four engine aircraft departed Bagram AFB on a short flight to Kabul, carrying 8 crew members and a load of various equipment on behalf of the NATO forces based in Pakistan. En route, while cruising by night, the aircraft impacted a rocky face located 30 km east of Kabul. The aircraft disintegrated on impact and all 8 occupants were killed.
Probable cause:
Controlled flight into terrain.

Crash of an Antonov AN-12BP at Camp Dwyer AFB

Date & Time: Jul 28, 2010
Type of aircraft:
Operator:
Registration:
3X-GEQ
Flight Type:
Survivors:
Yes
MSN:
4 3 422 10
YOM:
1964
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Camp Dwyer AFB (Forward Operating Base Dwyer) located in the Helmand Province, the aircraft went out of control, veered off runway, collided with a fence and came to rest into a ravine, broken in two. All six occupants were uninjured while the aircraft was damaged beyond repair. It was later dismantled by the US Air Force. The aircraft was carrying a load of fresh fruits and dairy products.