Crash of an Antonov AN-32B in Tarapacá

Date & Time: Jun 11, 2017 at 1712 LT
Type of aircraft:
Operator:
Registration:
HK-4833
Survivors:
Yes
Schedule:
La Pedrera – Tarapacá
MSN:
34 04
YOM:
1993
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
40
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8400
Captain / Total hours on type:
1475.00
Copilot / Total flying hours:
1560
Copilot / Total hours on type:
426
Aircraft flight hours:
3409
Aircraft flight cycles:
3182
Circumstances:
Following an unventful charter flight from La Pedrera, the crew initiated the approach to Tarapacá Airfield. Just after touchdown on runway 25, the aircraft went out of control and veered off runway to the right. While contacting soft ground, the airplane rolled for few dozen metres and became stuck in mud. All 45 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The following findings were identified:
- Inappropriate decision by the aircraft operator to rush the aircraft's initial route to an aerodrome unknown to the company, not appropriate to the type of aircraft and not authorised in its Operating Specifications, without at least a proper risk assessment.
- Inadequate crew decision to accept and decide to proceed to an unknown aerodrome, without due knowledge of its characteristics, without prior experience or training in aerodrome operation and without at least a risk assessment.
- A side runway excursion, from 24 metres from the threshold of runway 25, as a result of a probable unstabilised approach resulting in an off-axis landing.
Contributing factors:
- Inefficient planning and supervision of operations by the aircraft operator, by scheduling the operation to an unknown airfield.
- Failure of the company to comply with the contents of the Dispatch Manual and General Operations Manual, in relation to the procedures that must be complied with before operating new routes, new airports or special airports, in aspects such as route analysis, runway analysis, risk management and crew requirements.
- Ignorance of the Tarapacá runway by the crew.
Final Report:

Crash of a Fokker F27 Friendship 600 in Garbaharey

Date & Time: Jun 3, 2017 at 1120 LT
Type of aircraft:
Registration:
5Y-FMM
Flight Type:
Survivors:
Yes
Schedule:
Mogadishu - Garbaharey
MSN:
10318
YOM:
1967
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3600
Circumstances:
On 3rd June 2016 at 1120 hours, a Fokker 27/Mk600 registration 5Y-FMM operated by Safari Express Cargo Ltd, courtesy of the WFP was ferrying relief supplies from Mogadishu to Garbaharrey Airport was involved in an accident on landing at the destination airport. On touch down, the right hand main landing gear collapsed resulting from a collision with an obstacle of approximately 2 meter high on short final approach. The aircraft subsequently had a runway excursion to the starboard side. A segment of the right hand wing contacted the ground and was severed off from the rest of the wing with ensuing fuel spillage and fire. All the four propeller blades of the starboard engine contacted the ground surface and suffered rearwards bends. The fire was however contained before spreading further. All four crew members were able to evacuate safely while the aircraft was damaged beyond repair.
Final Report:

Crash of a Swearingen SA227AC Metro III in Tampico

Date & Time: Jun 2, 2017 at 2245 LT
Type of aircraft:
Operator:
Registration:
XA-UAJ
Flight Type:
Survivors:
Yes
Schedule:
Saltillo – Puebla
MSN:
AC-586
YOM:
1984
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3280
Copilot / Total flying hours:
1144
Aircraft flight hours:
35318
Aircraft flight cycles:
43028
Circumstances:
The twin engine aircraft departed Saltillo Airport on a night cargo flight to Puebla, carrying two pilots and a load of 550 kilos of various goods. En route, the crew declared an emergency and reported a low fuel condition before being cleared to divert to Tampico-General Francisco Javier Mina Airport. On final approach, both engines stopped and the aircraft descended into trees and crashed in a wooded area located 850 metres short of runway 31. Both pilots were slightly injured and the aircraft was damaged beyond repair.
Probable cause:
Emergency landing due to an inadequate pre-flight of the aircraft which resulted in the loss of power of both engines during the cruise flight due to exhaustion of fuel on board.
Contributing factors:
- Lack of adherence to flight planning procedures.
- Lack of coordination between captain and operations officer during pre-flight preparation.
- Lack of supervision of dispatcher activities.
Final Report:

Crash of a Boeing 737-33A in Manokwari

Date & Time: May 31, 2017 at 0851 LT
Type of aircraft:
Operator:
Registration:
PK-CJC
Survivors:
Yes
Schedule:
Ujung Pandang – Sorong – Manokwari
MSN:
24025/1556
YOM:
1988
Flight number:
SJY570
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
146
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13371
Captain / Total hours on type:
3110.00
Copilot / Total flying hours:
5570
Copilot / Total hours on type:
2523
Aircraft flight hours:
60996
Circumstances:
On 31 May 2017, a Boeing 737-300 aircraft registration PK-CJC was being operated by PT. Sriwijaya Air as a scheduled passenger flight from Hasanuddin Airport (WAHH), Makassar, South Sulawesi to Rendani Airport (WAUU), Manokwari, West Papua, with one transit stop at Domine Eduard Osok Airport (WASS) Sorong, West Papua. The flight was uneventful since the first departure from Makassar until commencing the approach at Manokwari. At 0815 LT (2315 UTC), the aircraft departed Sorong to Manokwari. On board in the flight were two pilots, four flight attendants and 146 passengers. On this flight, the Second in Command (SIC) acted as Pilot Flying (PF) and the Pilot in Command (PIC) acted as Pilot Monitoring (PM). At 2331 UTC, the pilot made first contact to Rendani Tower controller and informed that the aircraft was descending from FL 230 (altitude 23,000 feet) and requested the weather information. The Rendani Tower controller informed to the pilot that the wind was calm, ground visibility 6 km, cloud FEW CB 1,400 feet, temperature and dew point 26/25°C. At 2336 UTC, Rendani Tower controller instructed to the pilot to descend to 11,000 feet and to report when on Visual Meteorological Condition (VMC). At 2338 UTC, the pilot informed that they were on VMC condition and passed altitude 13,000 feet while position was 32 Nm from ZQ NDB (Non-Directional Beacon). Rendani Tower controller instructed to fly maintain on visual condition, fly via overhead, descend to circuit altitude, join right downwind runway 35, and to report when overhead Manokwari. At 2344 UTC, the pilot reported that the aircraft was over Manokwari and Rendani Tower controller informed to the pilot that the visibility changed to 5 km. Two minutes later Rendani Tower controller instructed to the pilot to continue approach and to report on right base runway 35. At 2349 UTC, at approximately 600 feet, the PIC as PM took over control by called “I have control” and the SIC replied “You have control”. A few seconds later the pilot reported that the aircraft was on final runway 35, and Rendani Tower controller instructed to the pilot to report when the runway 35 insight. The pilot immediately replied that the runway was in sight and acknowledged by Rendani Tower controller who then issued landing clearance with additional information that the wind was calm and the runway condition wet. At approximately 550 feet, the PIC instructed the SIC turn on the wiper and reconfirmed to SIC that the runway was in sight. Between altitude 500 feet to 200 feet, the EGPWS aural warnings “Sink Rate” and “Pull Up” sounded. At 2350 UTC, the aircraft touched down and rolled on runway 35. The spoiler deployed and the pilot activated the thrust reversers. The crew did not feel significant deceleration. The aircraft stopped at approximate 20 meters from the end of runway pavement. After the aircraft stopped, the PIC commanded “Evacuate” through the Passenger Address (PA) system. The Rendani Tower Controller saw that the aircraft was overrun and activated the crash bell then informed the Airport Rescue and Fire Fighting (ARFF) that there was an aircraft overrun after landing on runway 35. All the flight crew and passengers evacuated the aircraft and transported to the terminal building safely.
Probable cause:
According to factual information during the investigation, the Komite Nasional Keselamatan Transportasi identified initial findings as follows:
1. The aircraft was airworthy prior to the accident, there was no report or record of aircraft system abnormality during the flight. The aircraft had a valid Certificate of Airworthiness (C of A) and Certificate of Registration (C of R).
2. The aircraft operator had a valid Air Operator Certificate (AOC) to conduct a scheduled passenger transport.
3. The crew held valid licenses and medical certificates.
4. The weather conditions during aircraft approach and landing was slight rain with cumulonimbus viewed nearby the airport, wind was calm and runway was wet.
5. In this flight Second in Command (SIC) acted as Pilot Flying (PF) and the Pilot in Command (PIC) acted as Pilot Monitoring (PM). The PIC took over control from the SIC during approach at altitude approximately 600 feet.
6. At approximate 550 feet, the PIC instructed the SIC to turn on the wiper and reconfirmed to SIC that the runway was in sight.
7. Between altitude 500 feet to 200 feet, the EGPWS aural warnings “Sink Rate” and “Pull Up” sounded.
8. The CCTV recorded water splash when aircraft on landing roll.
9. Several area of the runway warp in approximate 2 - 5 meters square meters with standing waters on the runway of Rendani Airport.
10. Several runway lights covered by grass with the height approximately of 30-40 cm.
11. Rendani Aerodrome Manual (AM) as general guidelines in the airport operation had not been approved by the DGCA at the time of accident.
12. Rendani Airport (WAUU), Fire fighting category III refer to AIP amended on April 2015.
Final Report:

Crash of a PZL-Mielec M28-05 Skytruck in Bajura: 1 killed

Date & Time: May 30, 2017 at 1210 LT
Type of aircraft:
Operator:
Registration:
NA-048
Flight Type:
Survivors:
Yes
Schedule:
Surkhet - Simikot
MSN:
AJE003-02
YOM:
2004
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew departed Surkhet on a flight to Simikot but was unable to land at Simikot due to high winds and diverted to Bajura Airfield. Upon arrival, the twin engine aircraft crashed and came to rest upside down. The captain was killed and both other crew members were seriously injured.

Crash of a Dornier DO328Jet-310 in Mogadishu

Date & Time: May 30, 2017 at 1030 LT
Type of aircraft:
Operator:
Registration:
N330BG
Flight Type:
Survivors:
Yes
Schedule:
Entebbe – Mogadishu
MSN:
3184
YOM:
2001
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an unventful flight from Entebbe, the twin engine airplane made a belly landing at Mogadishu-Aden Abdulle Airport. After touchdown, it slid for few hundre metres before coming to rest. All four crew members evacuated safely and the aircraft was damaged beyond repair.

Crash of an Antonov AN-26 in Balashov: 1 killed

Date & Time: May 30, 2017 at 0640 LT
Type of aircraft:
Operator:
Registration:
RF-36160
Flight Type:
Survivors:
Yes
Schedule:
Balashov - Balashov
MSN:
80 01
YOM:
1979
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was performing a local training mission at Balashov Airport, in the region of Saratov. Following several touch-and-go manoeuvres, the crew initiated a new approach. On final, the airplane descended below the MDA and, at a speed of 240 km/h, rolled to the right to an angle of 24°, stalled and crashed in a field located 1,100 metres from the airfield, bursting into flames. Five occupants were injures while a pilot under supervision was killed. The airplane had the dual registration RF-36160 and 79 red.
Crew:
Cpt Y. Tereshin,
Maj S. Rodionov,
Ens Frolov,
P. Halaimov,
I. Makhmoudov,
M. Artemiev. †
Probable cause:
It was determined that during the approach, the instructor led the aircraft descending below MDA when he simulated an engine failure and positioned both power levers to idle. As a result of the failure of the propeller feathering system, the right engine stopped. After 14 seconds, the instructor mistakenly shut down the left engine that was running properly, causing the aircraft to lose speed, to stall and to crash.

Crash of a Let L-410UVP-E20 in Lukla: 2 killed

Date & Time: May 27, 2017 at 1404 LT
Type of aircraft:
Operator:
Registration:
9N-AKY
Flight Type:
Survivors:
Yes
Schedule:
Kathmandu – Lukla
MSN:
14 29 17
YOM:
2014
Flight number:
GO409
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
9687
Captain / Total hours on type:
1897.00
Copilot / Total flying hours:
1311
Copilot / Total hours on type:
1028
Aircraft flight hours:
2550
Aircraft flight cycles:
5467
Circumstances:
On May 27, 2017 9N-AKY, LET 410 UVP-E20 of Goma Air (now Summit Air), a domestic carrier of Nepal had a published program to operate 5 flights to Lukla from Kathmandu. The first flight departed Kathmandu at 0026 UTC. By the time 0647 UTC they had completed 4 flights. The fifth and the last flight departed Kathmandu at 0744 UTC for Lukla as call sign Goma Air 409. Goma Air 409 was the cargo flight carrying 1680 kg cargo for Lukla. There were two cockpit crews, one cabin crew and no passengers on board the flight. It was pre-monsoon period. Lukla weather on that particular day was cloudy since morning. But ceiling and visibility were reported OK. However, CCTV footage shows rapidly deteriorating weather condition before and after the crash. Automatic VHF recorder of Lukla Tower and CVR recording showed Tower was regularly updating pilots of deteriorating weather. All the pre-and post-departure procedure of the flight was completed in normal manner. Before departure from Kathmandu Pilots were found to have obtained latest weather of Lukla, Phaplu and Rumjatar. PIC decided to remain south of track to avoid the terrain and cloud. When Goma 409 was about 11 miles East from Kathmandu they were informed that Lukla was having heavy rain and airport closed. By that time air traffic congestion in TIA was slowly developing. Traffics were holding in the air and in the ground as well. So Goma 409 continued for Lukla. However, after crossing 26 miles from Kathmandu, they were again informed that the rain had ceased and airport was open. An AS350 helicopter, 9N AGU which departed Lukla at 0803 UTC for Kathmandu had reported unstable wind on final Runway 06. Enroute weather reported by 9N AGU upon request of Lukla Tower was good beyond the Lukla valley. However, it was apprehended that for fixed wing, weather might be difficult to enter valley. Lukla Tower relayed all available information when Goma Air 409 had first established contact at time 0810 UTC. Later, Goma Air and 9N AGY, two reciprocal traffics were also in contact each other. 9N AGY relayed the actual weather status to GOMA AIR. Lukla valley's ceiling and visibility was OK for VFR until 0812UTC ( 6 minutes before crash). Weather started to deteriorate very fast. Mountain Ridges were visible through thin layer of foggy cloud until 0814 UTC. After one minute (approx.) Right Base for Runway 06, was covered up and cloud from left base was moving towards final. Duty ATS Officer of Lukla Tower was regularly up dating pilots about deteriorating weather condition. However, Tower was found to be failed to close the runway as per SOP in spite of rapidly deterioratingweather. Pilots ventured to continue though the weather was marginal. Aircraft reported entering valley at 0816. CVR record showed that First Officer sighted the runway at 0817 (64 seconds before the impact). Instantly PIC acknowledged he had also the runway in sight. Aircraft was at 9100 ft (approx.) when the cockpit crews sighted the runway. It maintained 9000 feet (approx.) for further 21 seconds. At time 0817:12i.e. 48 seconds before the impact Tower gave the latest wind as Westerly 04 knots and runway was clear. PIC was still in doubt and asked whether there was rain. Upon confirmation of having no rain from the Tower the aircraft started to descend further. The PIC, who was also the PF, found to have lost situational awareness deviated to the right with continued descend. At 0817:35 (25 seconds before impact) when the flight was descending through 8650 ft First Officer warned PIC that they were too low. PIC did not respond the F/O's call-out and continued descend. On reaching 8500 ft. F/O again warned PIC in panic. Then PIC asked in panic where the runway was. F/O directed towards the runway. But it was already too low and too late. There was initially two short stall warning sound. Then a continuous stall warning sounded till the impact, which lasted for 13 seconds. The last words in CVR records was "w]/ gtfg " (Do not pull too much). Abrupt change in aircraft attitude in an attempt to climb and reach threshold height at 8900 ft. (on Kathmandu QNH) in a landing configuration, with landing gears down and on full flaps, created excessive drag resulting the aircraft to stall. Subsequently, its left wing first hit a small tree branch 180 ft. short of the threshold. Then impacted the sloppy terrain 100ft. short of the runway. After the crash aircraft engine was reported to be running for about a minute. But there was no postcrash fire. Aircraft was totally damaged by the impact.
Crew:
Paras Kumar Rai, pilot, †
Srijan Manandhar, copilot, †
Pragya Maharjan, cabin crew.
Probable cause:
The Commission concludes that the probable cause of this accident was aircraft stall as a result of excessive drag created by sudden increase in angle of attack of the aircraft supplemented by low speed (below Vref) in an attempt to initiate immediate climb on a landing configuration (full flap and landing gear down) warranted by the critical situation of the final phase of flight.
Contributing factors:
- Critical terrain and rapidly deteriorating weather condition.
- Pilot's loss of situational awareness.
- Improper pilot response to stall warning including failure to advance power lever to maximum at appropriate time.
- Violation of SOP by the ATS and Pilot as well.
Final Report:

Crash of a Swearingen SA226T Merlin IIIB in Arnprior

Date & Time: May 26, 2017
Operator:
Registration:
C-GFPX
Flight Type:
Survivors:
Yes
Schedule:
North Bay - Arnprior
MSN:
T-310
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine airplane departed North Bay on an ambulance flight to Arnprior, carrying two pilots and a doctor. Following an uneventful flight, the crew was cleared for a VOR/DME approach to runway 28 under VFR conditions. On short final, the aircraft descended too low and impacted ground 50 metres short of runway. Upon impact, the nose gear collapsed and the airplane slid for about 600 metres before coming to rest. All three occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a De Havilland DHC-6 Twin Otter 300 at Perris Valley

Date & Time: May 24, 2017 at 1515 LT
Operator:
Registration:
N708PV
Survivors:
Yes
Schedule:
Perris Valley - Perris Valley
MSN:
489
YOM:
1976
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3358
Captain / Total hours on type:
2131.00
Copilot / Total flying hours:
1893
Copilot / Total hours on type:
12
Aircraft flight hours:
37885
Circumstances:
The pilot of the twin-engine, turbine-powered airplane reported that, while providing flights for skydivers throughout the day, he had a potential new hire pilot flying with him in the right seat. He added that, on the eighth flight of the day, the new pilot was flying during the approach and "approximately 200 feet south from the threshold of [runway] 15 at approximately 15 feet AGL [above ground level] the bottom violently and unexpectedly dropped out. [He] believe[d] some kind of wind shear caused the aircraft [to] slam onto [the] runway and bounce into the air at a 45 to 60-degree bank angle to the right." The prospective pilot then said, "you got it." The pilot took control of the airplane and initiated a go-around by increasing power, which aggravated the "off runway heading." The right wing contacted the ground, the airplane exited the runway to the right and impacted a fuel truck, and the right wing separated from the airplane. The impact caused the pilot to unintentionally add max power, and the airplane, with only the left engine functioning, ground looped to the right, coming to rest nose down.
Probable cause:
The prospective pilot's improper landing flare and the pilot's delayed remedial action to initiate a go-around, which resulted in a runway excursion.
Final Report: