FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

2016 Silk Way Airlines Antonov An-12 crash

18 May 2016 · Dwyer Airport, Lashkargah, Afghanistan

Antonov An-12 · Runway overrun due to engine failure and pilot error

From Dwyer Airport (DWR) to Mary International Airport (MYP)

Report a problem

Event

Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
Event fatalities
7 · all aircraft and ground
Ground fatalities
Unknown
Occupants
9
Survivors
2
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
2
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline

Antonov An-12

Flight
ZP 4K-AZ25
Aircraft type
Antonov AN-12
Category
Airplane · from aircraft type
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
4K-AZ25
Onboard fatalities
7
Route
From Dwyer Airport (DWR)To Mary International Airport (MYP)

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Task performance
  • Aircraft › Aircraft oper/perf/capability

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

On 18 May 2016, a Silk Way Airlines Antonov An-12 cargo plane crashed after an engine failure during the take off run at Dwyer Airport in southern Afghanistan, en route to Mary International Airport in Turkmenistan. Seven of the nine crew members on board were killed in the crash, which was the second crash for Silk Way in Afghanistan after a 2011 Il-76 crash. The two survivors were Ukrainian nationals, who worked as technicians and were not in the flights cockpit; they were taken to hospital and treated for their injuries.

Arif Mammadov, head of Azerbaijan's State Civil Aviation Administration, said that the aircraft crashed after hitting an obstruction.

Azerbaijan's Accident Investigation Commission dispatched a team to Camp Dwyer to investigate the crash.

Investigation and cause

Investigation

On 8 June 2016 the Interstate Aviation Committee (MAK) announced, that Afghanistan have delegated the accident investigation to the MAK, the MAK is now leading the investigation into the accident, Azerbaijan's Accident Investigation Commissions as well as specialists from Ukrainian aircraft manufacturer are participating in this investigation.

On 16 November 2016 Russia's MAK released their preliminary report reporting that First Officer Abdullayev was pilot flying, and Captain Shaydanov was pilot monitoring. While taxiing out for departure the flight engineer reported the #3 engine (inboard right hand) was showing an of above the captain requested to be more attentive. The flaps were set to 15 degrees, CG as well as gross weight was within limits. While reading the takeoff checklist the propellers were locked, #1 and #4 propellers moved into their locked position, the #2 propeller reached the position about 17 seconds after the others, there was no evidence the #3 propeller ever locked. ATC reported the winds from 280 degrees at 14 knots gusting 26 knots and cleared the flight for takeoff.

The final report was released by the Russian Interstate Aviation Committee in October 2022, stated that the probable cause was the crew decision to conduct the takeoff with engine #3 inoperative, the propeller of which was not feathered. In course of the takeoff run, engine #3 was kept in the Ground Idle mode, therefore the propeller was producing a negative thrust which was increasing as the speed was increasing, preventing the aircraft from reaching the liftoff speed. During the takeoff run, the crew took no measures to abort the takeoff, and this resulted in the aircraft runway overrun at a speed of 220 km/h, as well as in the aircraft destruction in the post-crash fire and in the deaths of people.

As stated above, the crew made a decision to conduct a takeoff with inoperative engine #3. Most probably, this decision had been made considering that at the Dwyer AD there were no conditions necessary for the engine overhaul or change. During the takeoff run no crew reports related to the abnormal engine #3 operation were recorded. Thus, the aircraft takeoff run was conducted with the unfeathered propeller of the inoperative engine #3 which caused a significant negative thrust development and inhibited the speed increase. This conclusion is also proved by the mathematical model made by Antonov State Company. According to Antonov State Company conclusion, the model results that more accurately meet the recorded aircraft trajectory parameters are the results of the scenario when there is no autofeathering of the engine #3 propeller as an answer to the reverse thrust alert. The engine #3 propeller turns into with the negative thrust development which increases as the speed increases. The situation was caused by not setting the engine #3 throttle control lever to 40±2 degrees temperature mode. Moreover, according to Antonov State Company conclusion, it should be assumed that the propeller of engine #3 (inoperative engine) was not latched to the flight stop.

During the takeoff run, the unfeathered propeller created the maximum negative thrust which made the takeoff impossible. The available data do not provide the opportunity to precisely determine the reason why during the takeoff run, the crew did not increase the engine #3 rpm up to the values more than the ground idle. The most probable reason may be the increase of the turbine outlet temperature of engine #3 above the maximum allowable taxiing limit. Probably, the crew was afraid that the increase of the inoperative engine rpm may cause the recurrent increase of the turbine outlet temperature above the allowable limit.

The recorded information and the CCTV data of Dwyer AD evidence that with the elevator nose-up deflection to -14°, the aircraft did not lift off. On running along all the runway length (2439 m), and the concrete area of 90 m at a speed of 220 km/h, at 10:00:57, the aircraft ran over the runway and reached the ground. The total run before the aircraft overran the runway concrete surface lasted 70 s. During the takeoff run the crew took no measures to abort the takeoff.

Text from the Wikipedia article “2016 Silk Way Airlines Antonov An-12 crash” (revision 1359601701, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

Sources

Wikipedia article: 2016 Silk Way Airlines Antonov An-12 crash
Article
2016 Silk Way Airlines Antonov An-12 crash
Revision
1359601701 · 2026-06-16 · retrieved 2026-09-18
Wikidata
Q24147327
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
Where each value comes from
Record
Wikipedia article "2016 Silk Way Airlines Antonov An-12 crash" (page 50581588, revision 1359601701)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site
Map position
Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
airline flight number in the infobox
Fatalities
Wikipedia infobox: aircraft fatalities
Ground fatalities
not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (1)
  • Wikipedia · Facts from the Wikipedia article's infobox and coordinates, not checked against an investigation report. Independent review pending.