Country
code

West Kalimantan

Crash of a Boeing 737-4Y0 in Pontianak

Date & Time: Jun 1, 2012 at 1235 LT
Type of aircraft:
Operator:
Registration:
PK-CJV
Survivors:
Yes
Schedule:
Jakarta - Pontianak
MSN:
24689/1883
YOM:
1990
Flight number:
SJY188
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
155
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25000
Circumstances:
The approach to Pontianak was unstable and really difficult due to turbulence and poor weather conditions (heavy rain falls). The aircraft landed on wet runway 15 and skidded. It eventually veered off runway to the left and went through a muddy field. The nose gear was torn off while both main gears sank, leaving both engines on the ground. While all 163 occupants were evacuated safely, the aircraft was damaged beyond repair. At the time of the accident, weather conditions were as follow: wind from 230 at 22 knots, visibility 600 metres, few clouds at 900 feet, broken at 700 feet, CB's above the terrain and turbulences.

Crash of a Pilatus PC-6/B2-H4 Turbo Porter in Muaritan: 2 killed

Date & Time: Apr 25, 2012 at 1730 LT
Operator:
Registration:
PK-VVQ
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Balikpapan - Balikpapan
MSN:
965
YOM:
2009
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1912
Captain / Total hours on type:
81.00
Aircraft flight hours:
2397
Aircraft flight cycles:
3466
Circumstances:
The Pilatus Porter PC-6 aircraft operated by PT. Puji Astuti Aviation (Susi Air) registered PK-VVQ on Areal Survey Flight, departed from Sepinggan-Balikpapan to Melak Area on 25 April 2012 at 0440 UTC (Universal Time Coordinate) or 1240 LT. There were one pilot and one pasenger on board, the estimate flight endurance was seven hours. At 0505 the aircraft reported leaving Balikpapan Approach. At 0910 the aircraft was reported to Melak Radio on radial 060 at the altitude of 3,500 feet, and that it would be leaving Survey after a further twenty minutes. Melak Radio reported that the aircraft lost contact at 0930. At 0922 a text message was sent by the passenger to his employer stating “Run out of fuel, landing on road”. The Search and Rescue Bureau informed that a distress signal was tetected on 1025 at the position of 00 25’.02” N 116.02’.48”E. On 26 April 2012 at 1730 UTC the aircraft was found in Muaritan – Kecamatan Tabang, Kutai Karta Negara at the position 00 25’.03” N 116.01’.55”E. The aircraft was substantially damaged, the pilot and the passenger were fatally injured.
Probable cause:
The engine flamed out caused by lack of fuel supply from main fuel tank to the engine. The pilot likely fixated on the survey flight execution and lost awareness of his fuel situation. The transferring of fuel from the auxiliary tank was not performed during the flight as required. The combination of inexperience of the pilot related to survey flying, fatigue and the highly demanding survey operator contributed to this sequence of events.
Final Report:

Crash of a Boeing 737-4Y0 in Pontianak

Date & Time: Nov 2, 2010 at 1118 LT
Type of aircraft:
Operator:
Registration:
PK-LIQ
Survivors:
Yes
Schedule:
Jakarta – Pontianak
MSN:
24911/2033
YOM:
1991
Flight number:
JT712
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
169
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8190
Copilot / Total flying hours:
656
Aircraft flight hours:
49107
Aircraft flight cycles:
28889
Circumstances:
On 2 November 2010, a Boeing Company B737-400 aircraft, registered PK-LIQ, was being operated by Lion Mentari Airlines on a passenger schedule flight with flight number JT 712. This flight was the first flight for the crew and was scheduled for departure at 09.30 LT (02.30 UTC). On board the flight was 175 person included 2 pilots and 4 flight attendants and 169 passengers consisted 2 infants and one engineer. The pilots stated that the aircraft had history problem on the difficulty of selection the thrust reversers and automatic of the speed brake deployment. This problem was repetitive since the past three months. The aircraft pushed back at 0950 LT (0250 UTC). During taxi out, the yaw damper light illuminated for two times. The pilot referred to the Quick Reference Handbook (QRH) which guided the pilot to turn off the yaw dumper switch then back to turn on. Considered to these problems, the pilot asked the engineer to come to cockpit and asked to witness the problem. The aircraft departed Soekarno Hatta International Airport, Jakarta at 1012 LT (0312 UTC) with destination of Supadio Airport, Pontianak. The Pilot in Command acted as pilot flying (PF) and the Second in Command acted as pilot monitoring (PM). The flight to Pontianak until commenced for descent was uneventful. Prior to descend, the PF performed approach crew briefing with additional briefing included review of the past experiences on the repetitive problems of thrust reversers which sometimes hard to operate and the speed brake failed to auto deploy. Considering these problems, the PF asked to the PM to check and to remind him to the auto deployment of the speed brake after the aircraft touch down. During descend, the pilot was instructed by Pontianak Approach controller to conduct Instrument Landing System (ILS) approach for runway 15 and was informed that the weather was slight rain. On the initial approach, the auto pilot engaged, flaps 5° and aircraft speed 180 knots. After the aircraft captured the localizer at 1300 feet, the PF asked to the PM to select the landing gear down, flaps 15° and the speed decreased to 160 knots. The PF aimed to set the flaps landing configuration when the glide slope captured. When the glide slope captured, the auto pilot did not automatically follow the glide path and the aircraft altitude maintained at 1300 feet, resulted in the aircraft slightly above the normal glide path. The PF realized the condition then disengaged the auto pilot and the auto throttle simultaneously, and fly manually to correct the glide path by pushing the aircraft pitch down. While trying to regain the correct the glide path, the PF commanded for flaps 40° and to complete the landing checklist. The flap lever has been selected to 40°, but the indicator indicated at 30°. Realized to the flaps indication, the PF asked the landing speed for flaps 30° configuration in case the flaps could not move further to 40°. When aircraft altitude was 600 feet and the pilots completing the landing checklist, the PM reselected the flap from 30° to 40° and was successful. The pilots realized that the aircraft touched down was beyond the touchdown zone and during the landing roll the PF tried to select the thrust reverser but the levers were hard to select and followed by the speed brake failed to automatic-deploy. The pilots did not feel the deceleration, and then the PF applied maximum manual braking and selected the speed brake handle manually. Afterward, the thrust reversers successfully operated and a loud sound was heard prior to the aircraft stop. The Supadio tower controller on duty noticed that the aircraft was about to overrun the runway and immediately pressed the crash bell. The aircraft stopped at approximately 70 meters from the runway or 10 meters from the end of stop-way. The PIC then commanded to the flight attendants to evacuate the passengers through the exits. No one injured in this accident.
Probable cause:
The following factors were identified:
- Inconsistency to the Aircraft Maintenance Manual (AMM) for the rectifications performed during the period of the reversers and auto speed brake deployment problem was might probably result of the unsolved symptom problems.
- The decision to land during the un-stabilized approach which occurred from 1000 feet to 50 feet above threshold influenced by lack of crew ability in assessing to accurately perceive what was going on in the flight deck and outside the airplane.
- The effect of delayed of the speed brake and thrust reverser deployment effected to the aircraft deceleration which required landing distance greater than the available landing distance.
Final Report:

Crash of a Fletcher FU-24-950 in Ketapang: 2 killed

Date & Time: Dec 31, 2009 at 0826 LT
Type of aircraft:
Operator:
Registration:
PK-PNX
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Ujung Tanjung - Jambi - Pangkal Pinang - Ketapang - Tangar
MSN:
187
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2892
Captain / Total hours on type:
641.00
Circumstances:
The aircraft was completing a ferry flight from Ujung Tanjung/Pekanbaru home base to Tangar airstrip, Center of Kalimantan, with reference flight approval number D09-038960 and Security Clearance number AU05-033328, person on board was one pilot and one engineer. On 29 December 2009, the aircraft departed from Ujung Tanjung, transit at Jambi and stop overnight at Pangkal Pinang Airport, Bangka with total flight time was 3 hours. On the next day 30 December 2009, the aircraft continuing flight from Pangkal Pinang to Rahadi Oesman Airport, Ketapang, West Kalimantan and overnight at Ketapang with total flight time is 1:40 hours. On the next day 31 December 2009, the aircraft plan to continued flight to Tangar Airstrip. The aircraft was airworthy prior departure and dispatched from Ketapang with the following sequence:
a. The pilot requested for start the engine at 01:17 UTC4 (08:17 Local Time);
b. At 01:24 the pilot requested for taxi, and the ATC gave clearance via taxiway “A”. The pilot requested intersection runway 17 and approved by ATC
c. The ATC requested for reported when ready for departure, and the pilot reported ready for departure, then the ATC gave the departure clearance.
d. At 01:25, the aircraft was departed and crashed at 01:26 striking the roof of the hospital and broken down into pieces at the parking area in which have had approximate 1.5 Kilometer to the left side from the flight path centreline. The aircraft was substantially damage and the crew on board consist of one pilot in command and one aircraft maintenance engineer; both of them were fatally injured.
Probable cause:
The investigation concluded that the aircraft engine was not in power during impact with the hospital roof. There was a corroded fuel pump, that indicated of contaminated fuel.
Findings:
• The aircraft was airworthy prior departure.
• The pilot was fit for flight.
• The booster pump was found of an evident of surface corrosion on the spring, plate and van pump indicated that contaminated fuel.
• Referred to the Fletcher Flight Manual and Pilot Operating Handbook chapter 3.10. Fuel System Failure, the booster pump must have been operated prior to flight.
• The propeller blades were on fine pitch and no sign of rotating impact. The engine was not in powered when hit the ground.
• No evidence damage related to the engine prior to the occurrence.
Final Report:

Crash of a Boeing 737-2T4 in Tarakan

Date & Time: Oct 3, 2006 at 1120 LT
Type of aircraft:
Operator:
Registration:
PK-RIE
Survivors:
Yes
Schedule:
Balikpapan – Tarakan
MSN:
22804
YOM:
1983
Flight number:
RI394
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
104
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Tarakan-Juwata Airport, the crew was informed of the poor visibility due smoke emanating from forest fire. After touchdown on runway 06/24 which is 1,845 metres long, the aircraft went out of control, veered off runway, lost its undercarriage and one engine and came to rest. All 110 occupants escaped uninjured while the aircraft was damaged beyond repair. At the time of the accident, the visibility was reported to be about 400 metres, below minimums.

Crash of a Britten-Norman BN-2A-21 Islander in Tarakan: 7 killed

Date & Time: Nov 7, 2002 at 1027 LT
Type of aircraft:
Operator:
Registration:
PK-VIZ
Survivors:
Yes
Schedule:
Tarakan - Long Bawan
MSN:
697
YOM:
1973
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
Shortly after takeoff from Tarakan Airport, en route to Long Bawan, the pilot encountered engine problems and decided to return. On approach, the aircraft stalled and crashed on the top of a hill located 1,500 metres short of runway. Three passengers were injured while seven other occupants were killed.
Probable cause:
Engine failure for unknown reasons.

Crash of a Britten-Norman BN-2A-21 Islander on Mt Saran: 11 killed

Date & Time: Apr 25, 1994
Type of aircraft:
Operator:
Registration:
PK-ZAA
Flight Phase:
Survivors:
No
Site:
Schedule:
Pontianak - Nanga Pinoh
MSN:
730
YOM:
1974
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
En route from Pontianak to Nanga Pinoh, the pilot encountered poor weather conditions. While descending in IMC conditions, the twin engine aircraft struck the slope of Mt Saran located 48 km west of Nanga Pinoh. All 11 occupants were killed.
Probable cause:
Controlled flight into terrain.

Crash of a Cessna 402A in Ketapang: 1 killed

Date & Time: Oct 8, 1991
Type of aircraft:
Operator:
Registration:
PK-WWE
Survivors:
Yes
MSN:
402A-0002
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On final approach to Ketapang Airport, the twin engine aircraft crashed in unknown circumstances few hundred metres short of runway threshold. A passenger was killed while eight other occupants were injured.

Crash of a Douglas C-47B-20-DK in Pontianak

Date & Time: Jan 19, 1973
Operator:
Registration:
PK-EHC
Flight Type:
Survivors:
Yes
MSN:
15684/27129
YOM:
1945
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a cargo flight on behalf of the Pertamina Company. During the last segment, the airplane struck the runway 15 surface with its left wing. It went out of control, veered off runway and came to rest. While all four crew members escaped uninjured, the aircraft was damaged beyond repair.

Crash of a Douglas C-47A-20-DL in Tarakan

Date & Time: Aug 17, 1945
Operator:
Registration:
A65-7
Flight Type:
Survivors:
Yes
MSN:
9288
YOM:
1943
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
3605
Circumstances:
The crew was performing a cargo flight to Tarakan Airfield. The landing was completed with a strong tail wind and after touchdown, the aircraft was unable to stop within the remaining distance, veered off runway and came to rest in the bush. All three crew members were unhurt but the aircraft was damaged beyond repair.
Probable cause:
Landing with strong tail wind.