Crash of a De Havilland DHC-6 Twin Otter 300 on Mt Bajaja: 10 killed

Date & Time: Oct 2, 2015 at 1451 LT
Operator:
Registration:
PK-BRM
Flight Phase:
Survivors:
No
Site:
Schedule:
Masamba – Makassar
MSN:
741
YOM:
1981
Flight number:
VIT7503
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
2911
Captain / Total hours on type:
2911.00
Copilot / Total flying hours:
4035
Copilot / Total hours on type:
4035
Aircraft flight hours:
45242
Aircraft flight cycles:
75241
Circumstances:
On 2 October 2015, a DHC-6 Twin Otter, registered PK-BRM, was being operated by PT. Aviastar Mandiri as a scheduled passenger flight with flight number MV 7503. The aircraft departed from Andi Jemma Airport, Masamba (WAFM)1 with the intended destination of Sultan Hasanuddin International Airport, Makassar (WAAA) South Sulawesi, Indonesia. On board the flight were 10 persons consisting of two pilots and eight passengers, including one company engineer. The previous flights were from Makassar – Tana Toraja – Makassar – Masamba – Seko - Masamba and the accident flight was from Masamba to Makassar which was the 6th sector of the day. The aircraft departed from Masamba at 1425 LT (0625 UTC2 ) with an estimated time of arrival at Makassar of 0739 UTC. The Pilot in Command (PIC) acted as Pilot Flying (PF) while the Second in Command (SIC) acted as Pilot Monitoring (PM). The flight was conducted under the Visual Flight Rules (VFR) and cruised at an altitude of 8,000 feet. At 0630 UTC, the pilot reported to Ujung Pandang Information officer that the aircraft passed an altitude of 4,500 feet and was climbing to 8,000 feet. The Ujung Pandang Information officer requested the pilot of the estimate time of aircraft position at 60 Nm out from MKS VOR/DME. At 0632 UTC, the pilot discussed about the calculation of estimate time to reach 60 Nm out from MKS and afterward the pilot informed Ujung Pandang Information officer that the estimate at 60 Nm was at 0715 UTC. At 0633 UTC, the Ujung Pandang Information officer informed the pilot to call when reaching 8,000 feet and was acknowledged by the pilot. At 0636 UTC, the pilot informed the Ujung Pandang Information officer that the aircraft had reached 8,000 feet and requested the squawk number (ATC transponder code). The Ujung Pandang Information officer acknowledged and gave the squawk number of A5616, which was acknowledged by the pilot. At 0637 UTC, the pilots discussed to fly direct to BARRU. BARRU is a town located at about 45 Nm north of Makassar. Both pilots agreed to fly direct and the SIC explained the experience of flying direct on the flight before. At 0651 UTC, the PIC told the SIC that he wanted to climb and one second later the CVR recorded the sound of impact.
Probable cause:
The following findings were identified:
1. The aircraft had valid Certificate of Airworthiness prior to the accident and was operated within the weight and balance envelope.
2. Both pilots had valid licenses and medical certificates.
3. The accident flight from Masamba (WAFM) to Makassar (WAAA) was the 6th sector for the aircraft and the crew that day. The PIC acted as Pilot Flying and the
SIC acted as Pilot Monitoring.
4. The satellite image published by BMKG at 0700 UTC showed that there were cloud formations at the accident area. The local villagers stated that the weather
on the accident area was cloudy at the time of the accident.
5. The aircraft departed Masamba at 0625 UTC (1425 LT), conducted under VFR with cruising altitude of 8,000 feet and estimated time of arrival Makassar at 0739 UTC.
6. After reached cruising altitude, at about 22 Nm from Masamba, the flight deviated from the operator visual route and directed to BARRU on heading 200° toward the area with high terrain and cloud formation based on the BMKG satellite image
7. The pilots decision making process did not show any evidence that they were concerned to the environment conditions ahead which had more risks and required correct flight judgment.
8. The CVR did not record EGPWS aural caution and warning prior to the impact. The investigation could not determine the reason of the absence of the EGPWS.
9. The CVR data and cut on the trees indicated that the aircraft was on straight and level flight and there was no indication of avoid action by climb or turn.
10. The SAR Agency did not receive any crashed signal from the aircraft ELT most likely due to the ELT antenna detached during the impact.
11. Regarding to the operation of the EGPWS for the flight crew, a special briefing was performed however there was no special training.
12. The operational test of TAWS system was not included in the pilot checklist.
13. The investigation could not determine the installation and the last revision of TAWS terrain database.
14. The investigation could not find the functional test result document after the installation of the TAWS.
15. Some of the DHC-6 pilots have not been briefed for the operation of the TAWS and EGPWS.

Contributing Factors:
Deviation from the company visual route without properly considering the elevated risks of cruising altitude lower than the highest terrain and instrument meteorological condition in addition with the absence of the EGPWS warning resulted in the omission of avoidance actions.
Final Report:

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

Date & Time: Oct 2, 2015 at 1203 LT
Type of aircraft:
Operator:
Registration:
C-GCMD
Flight Phase:
Survivors:
No
MSN:
31-7912101
YOM:
1979
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot, sole on board, departed Managua-Augusto C. Sandino Airport at 0934LT on a flight for the Australian Company CSA Global, taking part to a geological mission dedicated to the construction of a canal. In unknown circumstances, the twin engine aircraft went out of control and crashed in a field located in Los Camastros, about one km north of Veracruz. The pilot was killed and maybe tried to use a parachute before the crash as one was found in the wreckage.

Crash of a Cessna 421B Golden Eagle II in Ozren: 1 killed

Date & Time: Sep 24, 2015 at 1230 LT
Operator:
Registration:
YU-BSW
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Banja Luka – Tuzla
MSN:
421B-0248
YOM:
1972
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The twin engine aircraft, operated by STS Avijacija (STS Aviation), departed Banja Luka on a charter flight to Tuzla, carrying two passengers and one pilot taking part to a foxes vaccination program. While cruising at low altitude, the airplane entered an area of clouds when it impacted trees and crashed on the slope of a mountain located near the Monastery of Ozren, southeast part of the Serbian Republic of Bosnia, bursting into flames. Both passengers were seriously injured and the pilot was killed.
Probable cause:
The root cause of the accident is the entry of the aircraft into the cloud at a low altitude, in conditions of increased cloudiness, which led to the impact of the aircraft in the ground. The accident is caused by inadequate preparation of the crew for the flight, deviation of the crew from the planned and approved route by location (diversion from the given route) and flight height (flight at a lower altitude than the approved one), as well as not taking timely procedures to return to the given route and flight height, as well as incorrect actions in case of encountering a deteriorated weather situation on the route under VFR flight conditions.
The accident was affected by:
a) The decision of the manager on the manner of execution of the flight,
b) Ignoring information about the meteorological situation and weather forecast,
c) Inadequate preparation of the crew for the execution of the flight at a low altitude and in conditions of fire of the meteorological situation,
d) Non-compliance with VFR rules for minimum flight height and meteorological minimum for airspace class “F” and “G”,
e) Loss of visual contact with the ground.

Crash of a PZL-Mielec AN-2R near Bratsk

Date & Time: Sep 16, 2015 at 1115 LT
Type of aircraft:
Registration:
RA-35141
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Zhelenogorsk-Ilimsky – Taseyovo – Achinsk
MSN:
1G112-23
YOM:
1969
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5116
Captain / Total hours on type:
4683.00
Copilot / Total flying hours:
1283
Copilot / Total hours on type:
1283
Aircraft flight hours:
14512
Aircraft flight cycles:
19970
Circumstances:
The single engine airplane departed Zhelenogorsk-Ilimsky Airport on a flight to Achinsk with an intermediate stop in Taseyovo, carrying one passenger and two pilots. After 43 minutes into the flight, while cruising at an altitude of about 1,200 metres, the engine lost power and the oil temperature increased from 70° to 150° C. The aircraft lost height, forcing the crew to attempt an emergency landing. The aircraft hit tree tops and eventually crash landed in a wooded area located 60 km northeast of Bratsk. The aircraft was damaged beyond repair and all three occupants escaped unarmed.
Probable cause:
The crash of An-2 RA-35141 aircraft occurred during the emergency landing on a forest firebreak. The landing was urged due to in-flight engine power loss as a result of the destruction of the 62.06.02 bronze hub pouring of the master rod big end of the crank mechanism. Most probably the destruction of the bronze hub pouring was caused by a manufacturing flaw consisting in a lack of bronze friction with the steel base on a part of its surface.
Final Report:

Crash of a Piper PA-60 Aerostar in San Pedro de los Milagros: 2 killed

Date & Time: Sep 11, 2015 at 1740 LT
Operator:
Registration:
N164HH
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Santa Fe de Antioquia - Medellín
MSN:
60-0012
YOM:
1969
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
8800
Copilot / Total flying hours:
7000
Circumstances:
The twin engine aircraft departed Santa Fe de Antioquia on a flight to Medellín, carrying one passenger and two pilots who were taking part to the production of the Tom Cruise movie 'Barry Seal - American Traffic'. While flying over mountainous terrain in IMC conditions, the airplane struck the slope of a hill with its right wing then crashed at the bottom of trees. A pilot was seriously injured and both other occupants were killed. The aircraft was destroyed.
Probable cause:
The accident was the consequence of a controlled flight into terrain after the crew decided to continue the flight at low height in IMC conditions.
The following contributing factors were identified:
- The foreign crew was not familiarized with the area of flight,
- Poor flight planning,
- CFIT.
Final Report:

Crash of a BAe 125-700B off Dakar: 7 killed

Date & Time: Sep 5, 2015 at 1812 LT
Type of aircraft:
Operator:
Registration:
6V-AIM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Ouagadougou - Dakar
MSN:
257062
YOM:
1979
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
7658
Captain / Total hours on type:
2158.00
Copilot / Total flying hours:
3339
Aircraft flight hours:
13279
Aircraft flight cycles:
11877
Circumstances:
The airplane departed Ouagadougou Airport at the end of the afternoon on an ambulance flight to Dakar-Léopold Sédar Senghor Airport with one patient, one doctor, two nurses and three crew members on board. After entering in contact with Dakar Control, the crew was cleared to FL340, an altitude that was confirmed by the crew at 1801LT. But the airplane continued and climbed to FL350. At 1812LT, the aircraft collided with a Boeing 737-8FB operated by Ceiba Intercontinental. Registered 3C-LLY, the B737 was operating the flight CEL071 Dakar - Cotonou - Malabo with 104 passengers and 8 crew members on board. Immediately after the collision, the BAe 125 entered an uncontrolled descent and crashed in the Atlantic Ocean about 111 km off Dakar. The pilot of the Boeing 737 informed ATC about a possible collision and continued to Malabo without further problem. Nevertheless, the top of the right winglet of the Boeing 737 was missing. SAR operations were suspended after a week and no trace of the BAe 125 nor the 7 occupants was ever found.
Probable cause:
The collision was the consequence of an error on part of the crew of the BAe 125 who failed to follow his assigned altitude at FL340 and continued to FL350 which was the assigned altitude for the Boeing 737. The captain of the B737 confirmed that he have seen the aircraft descending to him. Only the flight recorders could have helped to determine how such a situation could have occurred; Unfortunately they disappeared with the plane. There was a difference of 1,000 feet in the indications of both captain/copilot altimeters.
Final Report:

Crash of a De Havilland DHC-2 Beaver near Les Bergeronnes: 6 killed

Date & Time: Aug 23, 2015 at 1127 LT
Type of aircraft:
Operator:
Registration:
C-FKRJ
Flight Phase:
Survivors:
No
Schedule:
Lac Long - Lac Long
MSN:
1210
YOM:
1958
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
5989
Captain / Total hours on type:
4230.00
Aircraft flight hours:
25223
Circumstances:
The float-equipped de Havilland DHC-2 Mk. 1 Beaver (registration C-FKRJ, serial number 1210), operated by Air Saguenay (1980) inc., was on a visual flight rules sightseeing flight in the region of Tadoussac, Quebec. At 1104 Eastern Daylight Time, the aircraft took off from its base on Lac Long, Quebec, for a 20-minute flight, with 1 pilot and 5 passengers on board. At 1127, on the return trip, approximately 2.5 nautical miles north-northwest of its destination (7 nautical miles north of Tadoussac), the aircraft stalled in a steep turn. The aircraft descended vertically and struck a rocky outcrop. The aircraft was substantially damaged in the collision with the terrain and was destroyed by the post-impact fire. The 6 occupants received fatal injuries. No emergency locator transmitter signal was captured.
Probable cause:
Findings as to causes and contributing factors:
1. The pilot performed manoeuvres with a reduced safety margin at low altitudes. As a result, these flights involved a level of risk that was unnecessary to attain the objectives of sightseeing flights.
2. With no restrictions on manoeuvres and no minimum altitude prescribed by the company prior to flight, the pilot flew according to his own limits and made a steep turn at approximately 110 feet above ground level.
3. When the pilot made a steep left turn, aerodynamic stalling ensued, causing an incipient spin at an altitude insufficient to allow control of the aircraft to be regained prior to vertical collision with the terrain.
4. The absence of an angle-of-attack indicator system and an impending stall warning device deprived the pilot of the last line of defence against loss of control of the aircraft.

Findings as to risk:
1. If lightweight flight data recording systems are not used to closely monitor flight operations, there is a risk that pilots will deviate from established procedures and limits, thereby reducing safety margins.
2. If Transport Canada does not take concrete measures to facilitate the use of lightweight flight data recording systems and flight data monitoring, operators may not be able to proactively identify safety deficiencies before they cause an accident.
3. If pilots do not obtain at least the regulatory rest periods, there is a risk that flights will be conducted when pilots are fatigued.
4. Unless all flights made are recorded in the pilot’s logbook and monitored by the company, it is possible that the pilot will not receive the required rest periods, which increases the risk of flights being conducted when the pilot is fatigued.
5. If flights made are not recorded in the aircraft’s journey logbook, it is possible that inspection and maintenance schedules and component lifetimes will be exceeded, increasing the risk of failure.
6. Unless safety management systems are required, assessed, and monitored by Transport Canada in order to ensure continual improvement, there is an increased risk that companies will not be able to identify and effectively mitigate the hazards involved in their operations.
7. If pilots do not receive stall training that demonstrates the aircraft’s actual behaviour in a steep turn under power, there is a high risk of loss of control.

Other findings:
1. The replacement of the ventral fin with Seafins on C-FKRJ was in compliance with the requirements of Kenmore Air Harbor Inc.’s supplemental type certificate.
2. The control wheel was in the left-hand position (pilot side) at the moment of impact.
3. Angle-of-attack indicator systems have been recognized as contributing to flight safety by improving pilot awareness of the stall margin at all times, thereby allowing pilots to react in order to prevent loss of control of the aircraft.
4. Stall warning systems have been recognized as a means of improving flight safety by providing a clear, unambiguous warning of an impending stall.
Final Report:

Crash of a Let L-410UVP in Červený Kameň: 4 killed

Date & Time: Aug 20, 2015 at 0921 LT
Type of aircraft:
Operator:
Registration:
OM-ODQ
Flight Phase:
Survivors:
Yes
Schedule:
Dubnica - Dubnica
MSN:
84 13 20
YOM:
1984
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
10625
Aircraft flight hours:
8021
Circumstances:
The twin engine aircraft was carrying 17 skydivers and two pilots and was performing a skydiving mission with another Let L-410 owned by the same operator. Registered OM-SAB, the second aircraft was carrying 17 skydivers and 2 pilots as well. Both crew were preparing a program for an airshow scheduled next Sunday August 23. While climbing to an altitude of about 1,400 - 1,500 metres, the pilot of OM-ODQ was trying to get closer to OM-SAB when both aircraft collided. All but three skydivers were able to bail out prior both aircraft crashed in a wooded area located north of the airfield. All four crew members were killed and three skydivers as well, one in OM-SAB and two in OM-ODQ.
Probable cause:
The main cause of the in-flight collision was a poor flight management on part of the OM-ODQ captain.
Contributing factors:
- The captain of OM-ODQ was using a mobile phone at the time of the collision,
- The total weight of OM-ODQ at the time of the accident was above MTOW.
Final Report:

Crash of a Let L-410MA in Červený Kameň: 3 killed

Date & Time: Aug 20, 2015 at 0921 LT
Type of aircraft:
Operator:
Registration:
OM-SAB
Flight Phase:
Survivors:
Yes
Schedule:
Dubnica - Dubnica
MSN:
75 04 05
YOM:
1975
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
8404
Copilot / Total flying hours:
235
Aircraft flight hours:
5618
Circumstances:
The twin engine aircraft was carrying 17 skydivers and two pilots and was performing a skydiving mission with another Let L-410 owned by the same operator. Registered OM-ODQ, the second aircraft was carrying 17 skydivers and 2 pilots as well. Both crew were preparing a program for an airshow scheduled next Sunday August 23. While climbing to an altitude of about 1,400 - 1,500 metres, the pilot of OM-ODQ was trying to get closer to OM-SAB when both aircraft collided. All but three skydivers were able to bail out prior both aircraft crashed in a wooded area located north of the airfield. All four crew members were killed and three skydivers as well, one in OM-SAB and two in OM-ODQ.
Probable cause:
The main cause of the in-flight collision was a poor flight management on part of the OM-ODQ captain.
Contributing factors:
- The captain of OM-ODQ was using a mobile phone at the time of the collision,
- The total weight of OM-ODQ at the time of the accident was above MTOW.
Final Report:

Crash of an ATR42-300 near Oksibil: 54 killed

Date & Time: Aug 16, 2015 at 1455 LT
Type of aircraft:
Operator:
Registration:
PK-YRN
Flight Phase:
Survivors:
No
Site:
Schedule:
Jayapura - Oksibil
MSN:
102
YOM:
1988
Flight number:
TGN267
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
54
Captain / Total flying hours:
25287
Captain / Total hours on type:
7340.00
Copilot / Total flying hours:
3818
Copilot / Total hours on type:
2640
Aircraft flight hours:
50133
Aircraft flight cycles:
55663
Circumstances:
An ATR 42-300 aircraft registered PK-YRN was being operated by PT Trigana Air Service on 16 August 2015 as scheduled passenger flight with flight number IL267 from Sentani to Oksibil. On board of this flight were 54 persons. This flight was the fifth flight of the day and the second flight from Sentani to Oksibil. The aircraft departed Sentani at 0522 UTC and estimated time of arrival Oksibil was at 0604 UTC. The Second in Command (SIC) acted as Pilot Flying while the Pilot in Command (PIC) acted as Pilot Monitoring. The weather at Oksibil reported that the cloud was broken (more than half area of the sky covered by cloud) and the cloud base was 8,000 feet (4,000 feet above airport elevation) and the visibility was 4 up to 5 km. The area of final approach path was covered by clouds. The flight cruising at 11,500 feet and at 0555 UTC, the pilot made first contact with Oksibil Aerodrome Flight Information Services (AFIS) officer, reported on descent at position Abmisibil and intended to direct left base leg runway 11. At 0600 UTC, Oksibil AFIS officer expected the aircraft would have been on final but the pilot had not reported, the AFIS officer contacted the pilot but did not reply. The AFIS officer informed Trigana in Sentani that they had lost contact with IL267. The aircraft wreckage was found on a ridge of Tanggo Mountain, Okbape District, Oksibil at approximately 8,300 feet AMSL at coordinates of 04°49’17.34” S, 140°29’51.18” E, approximately 10 NM from Oksibil Aerodrome on bearing of 306°. All occupants were fatally injured and the aircraft was destroyed by impact force and post impact fire. The Flight Data Recorder (FDR) and Cockpit Voice Recorder were recovered and transported to KNKT recorder facility. The recovery of FDR data was unsuccessful while the recovery of CVR data successfully retrieved accident flight data. The CVR did not record any crew briefing, checklist reading not EGPWS warning prior to impact. The CVR also did not record EGPWS altitude call out on two previous flights. The investigation concluded that the EGPWS was probably not functioning.
Probable cause:
The following findings were identified:
1. The aircraft had valid Certificate of Airworthiness and was operated within the weight and balance envelope.
2. All crew had valid licenses and medical certificates.
3. The flight plan form was filed with intention to fly under Instrument Flight Rule (IFR), at flight level 155, with route from Sentani to MELAM via airways W66 then to Oksibil. The MORA of W66 between Sentani to MELAM was 18,500 feet.
4. The flight was the 5th flight of the day for the crew with the same aircraft and the second flight on the same route of Sentani to Oksibil.
5. The CVR data revealed that the previous flight from Sentani to Oksibil the flight cruised at altitude of 11,500 feet and the approach was conducted by direct to left base runway 11.
6. The CVR data also revealed that on the accident flight, the flight cruised at altitude 11,500 feet and intended to direct left base leg runway 11 which was deviate from the operator visual guidance approach that described the procedure to fly overhead the airport prior to approach to runway 11.
7. The witness stated that most of the time, the flight crew deviated from the operator visual approach guidance. The deviation did not identify by the aircraft operator.
8. The downloading process to retrieve data from the FDR was unsuccessful due to the damage of the FDR unit that most likely did not record data during the accident flight. The repetition problems of the FDR unit showed that the aircraft operator surveillance to the repair station was not effective.
9. The CVR did not record any crew briefing, checklist reading and EGPWS altitude callout prior to land on two previous flights nor the EGPWS caution and warning prior to impact.
10. The spectrum analysis of the CVR determined that both engines were operating prior to the impact.
11. Several pilots, had behavior of pulling the EGPWS CB to eliminate the nuisance of EGPWS warning. The pilots stated that the reason for pulling the EGPWS CB was due to the pilots considered this warning activation was not appropriate for the flight conditions. The correction to this behavior was not performed prior to the accident.
12. The investigation could not determine the actual EGPWS CB position during the accident flight.
13. The installation of EGPWS by the aircraft operator was not conducted according to the Service Bulletin issued by the aircraft manufacturer.
14. The terrain data base installed in the EGPWS of PK-YRN was the version MK_VIII_Worldwide_Ver_471 that was released in 2014. The Oksibil Airport was not included in the high-resolution update in this version of terrain database.
15. The information for Oksibil published in AIP volume IV (Aerodrome for Light Aircraft/ALA) did not include approach guidance. The operator issued visual guidance of circling approach runway 11 for internal use.
16. The visual approach guidance chart stated that the minimum safe altitude was 8,000 feet while the aircraft impacted with terrain at approximately 8,300 feet. This indicated an incorrect information in the chart. The investigation considered that the pattern on the approach guidance chart was not easy to fly, as many altitudes and heading changes.
17. Several maintenance records such as component status installed on the aircraft and installation of EGPWS was not well documented. This indicated that the maintenance management was not well performed.
18. The investigation could not find any regulation that describes the pilot training requirement for any addition or modification of aircraft system which affect to the aircraft operation.
19. There was no information related to the status of ZX NDB published on NOTAM prior to the accident.
20. Several safety issues indicated that the organization oversight of the aircraft operator by the regulator was not well implemented.
Contributing Factors:
1. The deviation from the visual approach guidance in visual flight rules without considering the weather and terrain condition, with no or limited visual reference to the terrain resulted in the aircraft flew to terrain.
2. The absence of EGPWS warning to alert the crew of the immediate hazardous situation led to the crew did not aware of the situation.
Final Report: