Crash-aerien 18 MAY 2016 d'un Antonov An-12B 4K-AZ25 - Dwyer Airport (DWR)
ASN logo
Statuts:Accident investigation report completed and information captured
Date:mercredi 18 mai 2016
Type/Sous-type:Silhouette image of generic AN12 model; specific model in this crash may look slightly different
Antonov An-12B
Compagnie:Silk Way Airlines
Immatriculation: 4K-AZ25
Numéro de série: 3341209
Année de Fabrication: 1963
Heures de vol:19828
Moteurs: 4 Ivchenko AI-20M-6
Equipage:victimes: 7 / à bord: 9
Passagers:victimes: 0 / à bord: 0
Total:victimes: 7 / à bord: 9
Dégats de l'appareil: Détruit
Conséquences: Written off (damaged beyond repair)
Lieu de l'accident:Dwyer Airport (DWR) (   Afghanistan)
Phase de vol: Au décollage (TOF)
Aéroport de départ:Dwyer Airport (DWR/OADY), Afghanistan
Aéroport de destination:Mary Airport (MYP/UTAM), Turkménistan
An Antonov An-12B cargo plane, operated by Silk Way Airlines, overran the runway during takeoff from Dwyer Airport, Afghanistan, and burst into flames. Seven of the nine occupants suffered fatal injuries.

The crew planned to fly from Baku (Azerbaijan) to Bagram (Afghanistan), Dwyer (Afghanistan), Mary (Turkmenistan) and then back to Baku. The flight legs to Dwyer Airport were uneventful.
At 13:11 the crew started the engines on the apron at Dwyer Airport. Engine no.2 was the last to be started up at 13:47 hours.
Before the takeoff the captain distributed the duties within the crew, nominating the first officer as the Pilot Flying, and himself as Pilot Monitoring.
After the engine startup the crew initiated taxiing to perform takeoff on runway 23. The concrete runway at Dwyer measured 2439 m by 37 m.
In the course of the takeoff preparations, at 13:57:56 the flight mechanic reported an increase in MGT of engine no.3 above the acceptable level: "Engine 3, look, engine temperature over six hundred, over seven hundred", which was confirmed by the first officer: "Yes, it’s getting temperature" while the captain asked to be more attentive.
The takeoff was performed with Flaps 15. As the checklist was being read, the captain ordered to lock the propellers. After the captain's order to lock the propellers a slight increase in torque values was recorded on engine no.1 and 4, and in 17 seconds also engine no.2. There was no evidence that the propeller of engine no.3 was locked.
At 13:59:42 the crew initiated the takeoff. Before the takeoff the ATC advised the crew on the wind direction and speed on the runway: 280° 14 knots (7 m/sec) gusting 26 knots (13 m/sec). Thus it was quartering headwind and the headwind component might have been 5 to 9 m/sec.
While performing takeoff the crew first increased thrust on engines no.1 and no.4 and then on engine no.2 after 10 seconds. The thrust of the three engines was about 50 kg/ as per torque indicator (lower than takeoff mode). The third engine was still operating in the ground idle mode, though the CVR did not record any crew callouts concerning engine no.3 operation parameters.
Based on the CCTV system of Dwyer Airport the takeoff roll was initiated almost from the runway threshold and was conducted to the left of the runway centerline. No significant deviations from the takeoff course during the takeoff roll were recorded. During the takeoff roll the rudder was deflected left close to extreme. Probably the pilots were also applying differential control on engine no.2 to decrease the right torque moment.
At 14:00:14 at approximately 120 km/h IAS the "Engine no.3 negative thrust" signal started. At that time the aircraft was about 430 m away from the start of the takeoff roll.
At 14:00:42 engines no.1 and no.4 thrust was increased up to 63 kg/ as per torque indicator (consistent with takeoff mode for the actual flight conditions). At that time the IAS was about 150 km/h. Engine no.2 thrust was increased up to the same value only 23 seconds later at about 200 km/h IAS. At that time the aircraft was about 840 m away from the runway end. Engine no.3 was still operating in ground idle mode. Approximately 260 m before the runway end at a speed of 220 km/h IAS (maximum speed reached) nose up input on the control column was started. The aircraft did not lift off. After rolling all along the runway the aircraft overran the runway onto the ground at a speed of 220 km/h.
While moving on the ground the aircraft sustained significant damage, which led to a post-crash fire that destroyed most of the aircraft structures. Out of the nine persons on board seven were killed and two were seriously injured and taken to hospital.

Probable Cause:

The accident with the An-12B 4K-AZ25 aircraft was caused by the decision of the crew to take off with a failed engine No. 3, the propeller of which was not feathered. During the entire takeoff run, engine No. 3 remained at ground idle, as a result of which the engine propeller created a negative thrust that increased as the speed increased, preventing the crew from reaching the take-off speed of the aircraft from the runway.

The crew did not take measures to stop the takeoff, which led to the aircraft overrunning the runway at a speed of 220 km/h, its destruction, followed by fire.

Accident investigation:

Investigating agency: MAK Russia
Status: Investigation completed
Duration: 6 years and 5 months
Accident number: final report
Download report: Final report



photo of Antonov-An-12B-4K-AZ25
accident date: 18-05-2016
type: Antonov An-12B
registration: 4K-AZ25
photo of Antonov-An-12B-4K-AZ25
accident date: 18-05-2016
type: Antonov An-12B
registration: 4K-AZ25

Aircraft history
date registration operator remarks
19 July 1963 CCCP-11408 Soviet Air Force
25 Sept. 1986 CCCP-11408 Soviet Air Force Gear-up landing at Kabul, Afghanistan
15 Nov. 1991 CCCP-11408 MAP Omsk APO Aircraft Production Association (APO) of the Ministry of Aviation Industry (MAP)
12 Nov. 1993 RA-11408 Aviaobshchemash
1995 RA-11408 Sky Cabs Air Cargo leased
9 April 1998 RA-11408 Aerofreight Airlines
Nov. 2003 RA-11408 Avial NV leased
March 2004 RA-11408 Aerofreight Airlines returned
July 2004 4K-AZ56 Silk Way bought
2006 UR-CAF Shovkoviy Shlyah
Sept. 2015 4K-AZ25 Silk Way

Ce plan montre l'aéroport de départ ainsi que la supposée destination du vol. La ligne fixe reliant les deux aéroports n'est pas le plan de vol exact.
La distance entre Dwyer Airport et Mary Airport est de 748 km (467 miles).

Les informations ci-dessus ne représentent pas l'opinion de la 'Flight Safety Foundation' ou de 'Aviation Safety Network' sur les causes de l'accident. Ces informations prélimimaires sont basées sur les faits tel qu'ils sont connus à ce jour.
languages: languages


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

©2023 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314