Country
Operator Image

Crash of an ATR42-512 in Serui

Date & Time: Sep 9, 2024 at 1035 LT
Type of aircraft:
Operator:
Registration:
PK-YSP
Flight Phase:
Survivors:
Yes
Schedule:
Biak - Serui - Jayapura
MSN:
559
YOM:
1998
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
42
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll from Serui-Stevanus Rumbewas Airport Runway 28, the crew decided to abort for unknown reasons. The airplane veered off runway to the left. While contacting soft ground, it lost its undercarriage and slid for few dozen metres before coming to rest nearby a wooded area. All 48 occupants evacuated safely. The airplane landed at 1019LT from Biak and was taking off for its last leg to Jayapura when the accident occurred.

Crash of a Boeing 737-4Y0 in Jakarta

Date & Time: Mar 20, 2021 at 1126 LT
Type of aircraft:
Operator:
Registration:
PK-YSF
Flight Type:
Survivors:
Yes
Schedule:
Jakarta - Makassar
MSN:
23869/1639
YOM:
1988
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6228
Captain / Total hours on type:
5208.00
Copilot / Total flying hours:
1255
Copilot / Total hours on type:
1084
Aircraft flight hours:
55982
Aircraft flight cycles:
65005
Circumstances:
On 20 March 2021, a Boeing 737-400F, registered PK-YSF, was being operated by Trigana Air Service on a non-schedule cargo flight from Halim Perdanakusuma International Airport (WIHH), Jakarta, Indonesia with intended destination of Sultan Hasanuddin International Airport (WAAA), South Sulawesi, Indonesia. On board in this flight was two pilots, one engineer and one Flight Operation Officer (FOO). According to the weight and balance sheet, the flight carried 16,672 kgs of general cargo, takeoff fuel of 11,100 kg and the takeoff weight was 60,695 kg (133,835 lbs). The Pilot in Command (PIC) acted as Pilot Flying (PF) and the Second in Command (SIC) acted as Pilot Monitoring (PM). At 0328 UTC (1028 LT), the PM requested clearance to Halim Tower controller (the controller) to pushback and start the engines. At 1031 LT, the PM requested to the controller for taxi clearance. There was no report of aircraft system abnormality prior to the aircraft departure. At 1047 LT, the controller issued clearance to the PK-YSF pilot to enter and to backtrack Runway 24. At 1051 LT, the PM reported ready for departure to the controller. The controller issued takeoff clearance with additional departure clearance that after takeoff, turn left to heading 180° and initially climb to altitude of 3,000 feet. The PM acknowledged the clearance. The takeoff was conducted with reduced takeoff thrust by assumed temperature of 40°C and the aircraft became airborne at 10:52:57 LT. At 1055 LT, the controller advised the pilot to report when established on heading 180°. The PM reported that they were experiencing right engine failure and requested to fly to AL NDB . The controller advised the PM to turn left heading 060° and to climb to 2,500 feet. Furthermore, the controller asked the pilot intention whether to hold over AL NDB or direct for landing approach. The PM replied that they would hold over AL NDB and added the information that no fire was detected. The controller issued clearance to fly to AL NDB at altitude of 2,500 feet. The controller assumed that PK-YSF would return to Halim and advised the Airport Rescue and Fire-Fighting (ARFF) personnel that PK-YSF experienced right engine failure and would return to Halim. At 1058 LT, the controller requested the information of time required for holding over AL NDB and was replied by the PM that holding would require about 15 minutes. Furthermore, the controller requested whether the pilot able to hold at a point about 15 to 20 Nm from AL NDB and was replied by the PM that they did not objection to the proposal. The controller instructed the pilot to maintain outbound heading up to 15 Nm, at altitude of 2,500 feet. This was intended by the controller to manage the departure and arrival aircraft to and from Halim. At 1116 LT, the PM reported that they were ready to turn left for approach. The controller advised the pilot to turn left and to intercept localizer of the Instrument Landing System (ILS) Runway 24. At 1125 LT, the PM reported to the controller that the Runway was in sight. The controller advised that the wind was from 060° at velocity of 6 knots, QNH 1,007 mbs and issued landing clearance. The aircraft touched down on the touchdown zone and shortly after, both wheels of the right main landing gear detached. The controller noticed spark appeared from the aircraft and pressed the crash bell. At 1127 LT, the controller informed pilots of the other aircraft that the runway blocked by the landing aircraft and identified fire on one of the engines. Few seconds later, the PM called the controller whether any fire and was replied by the controller that fire was visible on the left side of the aircraft.

Crash of a Boeing 737-347 in Wamena

Date & Time: Sep 13, 2016 at 0733 LT
Type of aircraft:
Operator:
Registration:
PK-YSY
Flight Type:
Survivors:
Yes
Schedule:
Jayapura – Wamena
MSN:
23597/1287
YOM:
1986
Flight number:
TGN7321
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
23823
Captain / Total hours on type:
9627.00
Copilot / Total flying hours:
650
Copilot / Total hours on type:
480
Aircraft flight hours:
59420
Aircraft flight cycles:
48637
Circumstances:
On 13 September 2016, a Boeing 737-300 Freighter, registered PK-YSY was being operated by PT. Trigana Air Service on a scheduled cargo flight from Sentani Airport, Jayapura (WAJJ) to Wamena Airport, Wamena (WAVV), Papua, Indonesia. Approximately 2130 UTC, during the flight preparation, the pilot received weather information which stated that on the right base runway 15 of Wamena Airport, on the area of Mount Pikei, low cloud was observed with the cloud base was increasing from 200 to 1000 feet and the visibility was 3 km. At 2145 UTC, the aircraft departed Sentani Airport with flight number IL 7321 and cruised at altitude 18,000 feet. On board the aircraft was two pilots and one Flight Operation Officer (FOO) acted as loadmaster. The aircraft carried 14,913 kg of cargo. The Pilot in Command (PIC) acted as Pilot Flying (PF) while the Second in Command (SIC) acted as Pilot Monitoring (PM). There was no reported or recorded aircraft system abnormality during the flight until the time of occurrence. After passing point MALIO, the aircraft started to descend. The pilot observed the weather met the criteria of Visual Meteorological Condition (VMC). The pilots able to identify another Trigana flight from Sentani to Wamena in front of them. While passing altitude 13,500 feet, approximately over PASS VALLEY, the Wamena Tower controller instructed the pilot to report position over JIWIKA. When the aircraft position was over point JIWIKA, the Wamena Tower controller informed to the pilot that the flight was on sequence number three for landing and instructed the pilot to make orbit over point X, which located at 8 Nm from runway 15. The pilot made two orbits over Point X to make adequate separation with the aircraft ahead prior to received approach clearance. About 7,000 feet (about 2,000 feet above airport elevation), the pilot could not identify visual checkpoint mount PIKEI and attempted to identify a church which was a check point of right base runway 15. The pilot felt that the aircraft position was on right side of runway centerline. About 6,200 feet (about 1,000 feet above airport elevation), the PF reduced the rate of descend and continued the approach. The PM informed to the PF that runway was not in sight and advised to go around. The PF was confident that the aircraft could be landed safely as the aircraft ahead had landed. Approximately 5,600 feet altitude (about 500 feet above airport elevation) and about 2 Nm from runway threshold the PF was able to see the runway and increased the rate of descend. The pilot noticed that the Enhanced Ground Proximity Warning System (EGPWS) aural warning “SINK RATE” active and the PF reduced the rate of descend. While the aircraft passing threshold, the pilot felt the aircraft sunk and touched down at approximately 125 meters from the beginning runway 15. The Flight Data Recorder recorded the vertical acceleration was 3.25 g on touchdown at 2230 UTC. Both of main landings gear collapsed. The left main landing gear detached and found on runway. The engine and lower fuselage contacted to the runway surface. The aircraft veer to the right and stopped approximately 1,890 meters from the beginning of the runway 15. No one was injured on this occurrence and the aircraft had substantially damage. Both pilots and the load master evacuated the aircraft via the forward left main cargo door used a rope.
Probable cause:
Refer to the previous aircraft that was landed safely, the pilot confidence that a safe landing could be made and disregarding several conditions required for go around.
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:

Crash of an ATR42-300 near Balikpapan

Date & Time: Feb 11, 2010 at 1150 LT
Type of aircraft:
Operator:
Registration:
PK-YRP
Flight Phase:
Survivors:
Yes
Schedule:
Tanjung Redep - Samarinda
MSN:
50
YOM:
1987
Flight number:
TGN162
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
46
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12000
Copilot / Total flying hours:
2000
Aircraft flight hours:
34414
Aircraft flight cycles:
42107
Circumstances:
On 11 February 2010, an Avions de Transport Regional ATR 42-300 aircraft, registered PK-YRP, was being operated by Trigana Air Service on a scheduled passenger service between Kalimarau Airport Berau (BEJ) and Samarinda (SRI) as flight TGN162. There were 52 persons on board; two pilots, one engineer, two flight attendants, one flight dispatcher and 46 passengers (43 adults, one child, and two infants). The aircraft departed from Berau at 0230 UTC1 and climbed to Flight Level 140. Balikpapan approach cleared the crew to track from en-route Way Point LOLOT direct to Samarinda. After transferring to Temindung Tower, Samarinda, the crew was cleared to track direct to left downwind for runway 04. The controller informed them that the wind was 060/12 knots. The crew did not report any abnormalities and the aircraft operation appeared to be normal. During the final approach for runway 04, the left ECU light illuminated followed by low oil pressure and torque indications. The Pilot in Command decided to go around, divert to Balikpapan, and carry out the QRH engine shut-down procedure. They commenced the climb to 4000 ft with the left engine inoperative. Approximately 16 Nm from Balikpapan Airport, while climbing through 3,800 feet, the right ECU light illuminated, immediately followed by low oil pressure and low torque indications. The right engine then failed. The crew broadcast a MAYDAY to Balikpapan Approach and decided to conduct a forced landing into a clear field in the Samboja area, about 16 Nm from the Balikpapan Airport. The PIC gave instructions to the Flight Attendant to prepare the passengers for an emergency landing. After the aircraft came to a stop the PIC initiated an evacuation.
Probable cause:
The both engine were lack of fuel before flame out, it was indicated the fuel management was out of control during flight that might be a misleading of fuel quantity indication. The proper analysis could not be carried out due to both FDR and CVR were un-operated.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 300 on Mt Puncak Jaya: 12 killed

Date & Time: Nov 17, 2006 at 0800 LT
Operator:
Registration:
PK-YPY
Flight Phase:
Survivors:
No
Site:
Schedule:
Mulia – Ilaga
MSN:
535
YOM:
1977
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
12
Circumstances:
The twin engine aircraft departed Mulia on a special flight to Ilaga, carrying a delegation of nine people flying to Ilaga to visit several districts of the Irian Jaya province on behalf of a talks between several administrations. While cruising at an altitude of 10,500 feet in marginal weather conditions, the aircraft struck Mt Puncak Jaya. The wreckage was found the following day. All 12 occupants were killed.
Probable cause:
Controlled flight into terrain.

Crash of a De Havilland DHC-4 Caribou in Mamit

Date & Time: Oct 10, 2006 at 1400 LT
Type of aircraft:
Operator:
Registration:
PK-YRO
Flight Type:
Survivors:
Yes
Schedule:
Mulia – Mamit – Wamena
MSN:
24
YOM:
1960
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on wet gravel runway 11/29, the aircraft veered off runway and came to rest in a wooded area, broken in two. All five occupants escaped uninjured.

Crash of a De Havilland DHC-6 Twin Otter 300 in Silimo

Date & Time: Sep 3, 2002
Operator:
Registration:
PK-YPQ
Flight Type:
Survivors:
Yes
Schedule:
Wamena – Silimo
MSN:
498
YOM:
1976
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Silimo Airstrip, during the last segment, the aircraft lost height and struck the ground few metres short of runway 05 threshold. Out of control, the airplane veered to the left and came to rest in a ditch. All three occupants escaped uninjured while the aircraft was damaged beyond repair. The Silimo's runway is 560 metres long and 20 metres wide. Its surface is in gravel and it has a gradient of 9°. Due to the environmental topography, a go-around procedure is not possible on short final and the area is subject to strong currents that can change rapidly and brutally.
Probable cause:
It is believed that the loss of height on short final was the consequence of sudden change in the wind direction and speed.

Crash of a De Havilland DHC-6 Twin Otter 300 near Nabire: 6 killed

Date & Time: May 25, 2002 at 0700 LT
Operator:
Registration:
PK-YPZ
Flight Phase:
Survivors:
No
Site:
Schedule:
Nabire – Enarotali
MSN:
458
YOM:
1975
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
While cruising in poor weather conditions at an altitude of 7,800 feet, the twin engine aircraft struck the slope of a mountain located about 50 km from Nabire. The aircraft was destroyed and all six occupants were killed. At the time of the accident, the visibility was poor due to heavy rain falls and the mountain struck by the aircraft was shrouded in mist.
Probable cause:
Controlled flight into terrain.

Crash of a Pilatus PC-6/B2-H4 Turbo Porter in Bugalaga

Date & Time: Jan 18, 2002 at 1000 LT
Operator:
Registration:
PK-YPC
Flight Type:
Survivors:
Yes
Schedule:
Nabire - Bugalaga
MSN:
726
YOM:
1971
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
8500
Circumstances:
Upon landing on runway 06, the single engine aircraft bounced twice then veered off runway and came to rest in bushes. Both pilots escaped unhurt while the aircraft was damaged beyond repair.
Probable cause:
The crew completed the landing roll with a tailwind component and the runway was in poor conditions at the time of the accident, which remained a contributing factor.