Crash of a Piper PA-31-310 Navajo in Caernarfon: 1 killed

Date & Time: Sep 6, 2017 at 1723 LT
Type of aircraft:
Registration:
N250AC
Flight Type:
Survivors:
No
MSN:
31-7612040
YOM:
1976
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4000
Aircraft flight hours:
9243
Circumstances:
Approximately 20 minutes after takeoff from a private airstrip in Cheshire the pilot reported pitch control problems and stated his intention to divert to Caernarfon Airport. Approximately 5 minutes later, the aircraft struck Runway 25 at Caernarfon Airport, with landing gear and flaps retracted, at high speed, and with no noticeable flare manoeuvre. The aircraft was destroyed. The elevator trim was found in a significantly nose-down position, and whilst the reason for this could not be determined, it is likely it would have caused the pilot considerable difficulty in maintaining control of the aircraft. The extensive fire damage to the wreckage and the limited recorded information made it difficult to determine the cause of this accident with a high level of confidence. A possible scenario is a trim runaway, and both the CAA and the EASA are taking safety action to promote awareness for trim runaways as a result of this accident.
Probable cause:
After reporting pitch control problems, N250AC made a direct diversion with a significantly unstable approach, in a clean configuration, to Runway 25 at Caernarfon Airport. The elevator trim was found in a nose-down position and, whilst the reason for this could not be determined, it is likely that it caused the pilot considerable difficulty in controlling the aircraft. The aircraft struck Runway 25 at Caernarfon Airport, with landing gear and flaps retracted, at high speed, and with no noticeable flare manoeuvre. The extensive fire damage to the wreckage and the limited recorded information made it difficult to determine the cause of this accident with a high level of confidence. It is possible there was a nose-down trim runaway that the pilot was unable to stop.
Final Report:

Crash of an Antonov AN-26B in Maban

Date & Time: Aug 28, 2017 at 1130 LT
Type of aircraft:
Operator:
Registration:
EK-26006
Flight Type:
Survivors:
Yes
MSN:
121 02
YOM:
1982
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown on runway 33 at Maban Airport, South Sudan, the airplane was unable to stop within the remaining distance and overran. It lost its undercarriage and came to rest, bursting into flames. All crew members evacuated safely and the aircraft was totally destroyed by a post crash fire. The crew was completing a cargo flight on behalf of the United Nations High Commissioner for Refugees (UNHCR).

Crash of a Britten Norman BN-2A-26 Islander in Eteringbang: 1 killed

Date & Time: Jul 25, 2017 at 1755 LT
Type of aircraft:
Operator:
Registration:
8R-GRA
Flight Type:
Survivors:
No
Schedule:
Ekereku – Eteringbang
MSN:
3006
YOM:
1982
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4760
Aircraft flight hours:
24716
Circumstances:
The twin engine airplane departed Ekereku on a cargo flight to Eteringbang, carrying fuel drums for local miners. On final approach to Eteringbang Airfield Runway 03, the aircraft was very low and the pilot initiated a right turn when control was lost. The aircraft crashed in a dense wooded area some 200 metres from the runway. The aircraft was destroyed and the pilot, sole on board, was killed. The pilot Collin Martin was the Chief Pilot of Roraima Airways since 2015.
Probable cause:
The pilot flew a non-standard traffic pattern very low and very close to the runway. The excessive and extreme fight manoeuvres to position the aircraft for the landing resulted in a loss of aircraft control.
Contributory Factors:
The pilot’s failure to operate in accordance with established standard operating procedures when approaching the runway to land.
Final Report:

Crash of a Boeing 737-301F in Wamena

Date & Time: Jul 18, 2017 at 1239 LT
Type of aircraft:
Operator:
Registration:
PK-YGG
Flight Type:
Survivors:
Yes
Schedule:
Timika – Wamena
MSN:
23743/1510
YOM:
1988
Flight number:
TMG103
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was performing a cargo flight from Timika, carrying five crew members and a load of various goods including constructioin materials. Upon landing on runway 15, the airplane bounced twice. It went out of control and veered off runway to the left. While contacting soft ground, both main landing gear were torn off and the aircraft slid for few dozen metres before coming to rest. All five crew members evacuated safely while the aircraft was damaged beyond repair.

Crash of a Cessna 207 Stationair in Vinalhaven

Date & Time: Jun 26, 2017 at 0741 LT
Operator:
Registration:
N207GM
Flight Type:
Survivors:
Yes
Schedule:
Rockland - Vinalhaven
MSN:
207-0217
YOM:
1972
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15436
Captain / Total hours on type:
356.00
Aircraft flight hours:
12458
Circumstances:
The pilot reported that the approach appeared normal, but during the landing on the 1,500 feet long gravel strip, the airplane firmly struck the runway and bounced. He added that the bounce was high and that the remaining runway was too short to correct the landing with power. The pilot chose to go around, applying full power and 20° of flaps for the balked landing procedure. During the climb, the airplane drifted left toward 50-ft-tall trees about 150 ft from the departure end of the runway. Unable to climb over the trees, the airplane struck the tree canopy, the nose dropped, and the pilot instinctively reduced power as the airplane descended through the trees and impacted terrain. The wings and fuselage were substantially damaged. The pilot reported no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause:
The pilot's failure to maintain a stabilized approach, which resulted in a bounced landing and subsequent go-around with insufficient distance to clear trees during the climb.
Final Report:

Crash of a Beechcraft 200 Super King Air in Bamako

Date & Time: Jun 14, 2017 at 1405 LT
Operator:
Registration:
TZ-DDG
Survivors:
Yes
Schedule:
Bamako - Bamako
MSN:
BB-589
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful cloud seeding mission over the region of Mopti, the pilot was returning to Bamako-Senou Airport. For unknown reasons, the aircraft made a belly landing and slid for few dozen metres before coming to rest on the right side of runway 06/24. The pilot escaped uninjured and the aircraft was damaged beyond repair.

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: