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 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-301 in Ujung Pandang

Date & Time: Dec 21, 2009 at 0151 LT
Type of aircraft:
Operator:
Registration:
PK-MDH
Survivors:
Yes
Schedule:
Surabaya – Ujung Pandang
MSN:
23932/1554
YOM:
1988
Flight number:
MZ766
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
102
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Surabaya-Juanda Airport, the crew started a night approach to Ujung Pandang-Sultan Hasanuddin Airport (Makassar). On short final, at a height of 50 feet, the aircraft descended fast and landed nose first. A tyre burst on impact and the aircraft was stopped following a normal landing course. All 108 occupants evacuated safely and the aircraft was damaged beyond repair due to fuselage damages.

Crash of a Fokker 100 in Kupang

Date & Time: Dec 2, 2009 at 2215 LT
Type of aircraft:
Operator:
Registration:
PK-MJD
Survivors:
Yes
Schedule:
Ujung Pandang - Kupang
MSN:
11474
YOM:
1993
Flight number:
MZ5840
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
88
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18776
Copilot / Total flying hours:
7074
Aircraft flight hours:
29637
Aircraft flight cycles:
29450
Circumstances:
PK-MJD was on passenger schedule flight from Sultan Hasanuddin Airport, Makassar with destination El Tari Airport, Kupang, East Nusa Tenggara. The flight number was Merpati 5840 and carried 94 person on board consist of 88 passengers including four children and four infants, two pilot and four flight attendant. A maintenance engineer was on-board in this flight. Acting as pilot flying was the Second in Command (SIC) while the Pilot in Command acted as Pilot Monitoring. On approach, the pilot selected landing gear to down position. The left main landing gear indicator light was showed red, its means that the left main landing gear was not in down position and unsafe for landing. The pilot reported to the Air Traffic Controller (ATC) for a go-around and requested an area for holding to solve the problem. The ATC gave a clearance to hold over Kupang bay. The pilot tried to solve the problem by conducting the procedure according to the emergency checklist, including selected the landing gear by alternate selector. The pilot then requested to the ATC to fly at low altitude over the airport and asked to the ATC to observe the landing gear condition. The pilot also asked through the company radio for an engineer on-ground to observe visually the landing gear condition. The pilot then returned to the holding area, repeated the procedure but unsuccessful. Both pilots and engineer had a discussion and decided to attempt un-procedural method to make the landing gear down. Prior making these efforts the pilot announced to the passengers about the problem and their attempts that might be unpleasant to the passengers. After all attempts to lower the landing gear had failed, the pilot decided to land with the left main landing gear in up position. The pilot also asked the flight attendant to prepare for an abnormal landing. The ATC were prepared the airport fire fighting and ambulance, and also contacted the local police, armed forces, and hospitals and asking for additional ambulances. The ATC then informed the pilot that the ground support was ready. On short final the pilot instructed ‘brace for impact’ and the FA repeated that instruction to all passengers. The aircraft touched down at the touch down zone on runway 07. The pilot flying held the left wing as long as possible and kept the aircraft on the centre line, and the pilot monitoring shut down both engines. The aircraft stopped at about 1,200 meters from the beginning of runway 07, on the left shoulder of the runway and the FA instructed to the passengers to keep calm and to evacuate the aircraft. The pilot continued the procedures for emergency. The evacuation was performed through all door and window exits. No one was injured on this serious incident.
Probable cause:
The debris trapped in the chamber between the orifice and the stopper of the restrictor check valve, it caused the orifice closed. This condition was resulted the hydraulic flow from the actuator blocked and caused the left main landing gear jammed at up position.
Final Report:

Crash of a PZL-Mielec M-28-05PI in Mulia: 4 killed

Date & Time: Nov 2, 2009 at 1200 LT
Type of aircraft:
Operator:
Registration:
P-4202
Flight Type:
Survivors:
No
Site:
Schedule:
Jayapura – Mulia
MSN:
AJE003-04
YOM:
2004
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The twin engine aircraft departed Jayapura-Sentani Airport on a flight to Mulia, carrying four crew members and a load of logistics support dedicated to the Puncak Jaya Police Department. While approaching Mulia in marginal weather conditions, the aircraft struck the slope of a mountain located 33 km northwest of Mulia. The wreckage was found two days later and all four occupants were killed.
Probable cause:
Controlled flight into terrain.

Crash of a GAF Nomad N.24A in Long Apung: 5 killed

Date & Time: Sep 7, 2009 at 1428 LT
Type of aircraft:
Operator:
Registration:
P-837
Flight Phase:
Survivors:
Yes
Schedule:
Long Bawan - Tarakan
MSN:
135
YOM:
1982
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
While performing a maritime patrol flight, the aircraft crashed in unknown circumstances in the region of Long Apung. Five occupants were killed while four others were seriously injured.

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

Date & Time: Aug 2, 2009 at 1100 LT
Operator:
Registration:
PK-NVC
Flight Phase:
Survivors:
No
Site:
Schedule:
Jayapura - Oksibil
MSN:
626
YOM:
1979
Flight number:
MZ9760D
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
15
Captain / Total flying hours:
8387
Captain / Total hours on type:
8387.00
Copilot / Total flying hours:
1207
Copilot / Total hours on type:
1207
Aircraft flight hours:
27336
Circumstances:
On the morning of Sunday, 2 August 2009, a de Havilland DHC-6 Twin Otter aircraft, registered PK-NVC, operated by PT. Merpati Nusantara Airlines as flight number MZ-7960D, departed from Sentani Airport, Jayapura for Oksibil Airport. The flight was planned in accordance with the visual flight rules (VFR). There were 15 persons on board; two pilots, one engineer, 10 adult passengers and two infants. The estimated flight time was 50 minutes. The fuel on board was sufficient for 2 hours and 50 minutes flight time. About 15 minutes prior to the estimated time of arrival at Oksibil the crew of another aircraft informed the Twin Otter crew that the weather in the Oksibil area was partly cloudy. There were no further reports of radio transmissions from the Twin Otter, and it did not arrive at Oksibil. A search was initiated at the time the aircraft would have run out of fuel. On the morning of 4 August 2009, searchers located the wreckage of the Twin Otter at an elevation of about 9,300 feet about 6 Nm from Oksibil. The aircraft was destroyed by impact forces, and all of the occupants were fatally injured.
Probable cause:
The pilots did not maintain visual flight procedures when flying below lowest safe altitude, and the aircraft was flown into cloud in the vicinity of gap north west of Oksibil. In conclusion, the accident was consistent with controlled flight into terrain.
Final Report:

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

Date & Time: Jun 29, 2009 at 1601 LT
Operator:
Registration:
PK-BRO
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Dekai - Wamena
MSN:
756
YOM:
1981
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The twin engine aircraft departed Dekai Airport at 1530LT on a cargo flight to Wamena, carrying three crew members and a load of 1,600 kilos of various goods. Between 1554LT and 1600LT, the crew was in contact with Wamena. At 1601LT, while cruising at an altitude of 9,600 feet in limited visibility, the aircraft collided with a mountain slope. The wreckage was found a day later about 19 km southeast from Wamena. The aircraft disintegrated on impact and all three occupants were killed.
Probable cause:
Controlled flight into terrain after the crew was flying under VFR mode in IMC conditions. IFR approach to Wamena are not possible, VFR only.

Crash of a Lockheed C-130H Hercules in Madiun: 100 killed

Date & Time: May 20, 2009 at 0630 LT
Type of aircraft:
Operator:
Registration:
A-1325
Flight Type:
Survivors:
Yes
Schedule:
Jakarta – Madiun
MSN:
4917
YOM:
1982
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
98
Pax fatalities:
Other fatalities:
Total fatalities:
100
Circumstances:
The four engine aircraft departed Jakarta-Halim Perdana Kusuma Airport on a flight to Madiun, carrying Indonesian soldiers/officers and family members. On final approach to Madiun-Iswahyudi Airport, the crew failed to realize his altitude was too low when the aircraft collided with four houses and eventually crashed in a rice paddy field. 98 occupants as well as two people on the ground were killed while 14 other occupants were seriously injured.

Crash of a Pilatus PC-6/B2-H4 Turbo Porter near Mulia: 11 killed

Date & Time: Apr 17, 2009 at 1015 LT
Operator:
Registration:
PK-LTJ
Flight Phase:
Survivors:
No
Site:
Schedule:
Ilaga - Mulia
MSN:
959
YOM:
2008
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
2664
Captain / Total hours on type:
1412.00
Aircraft flight hours:
542
Circumstances:
On the morning of 17 April 2009, a Pilatus PC-6/B2-H4 Turbo Porter aircraft, registered PK-LTJ, operated by PT. Mimika Air, charter flight from Ilaga to Mulia in the Puncak Jaya District of Papua. The Mimika Local Government owned the aircraft. There were 11 people on board; one pilot, one observer, and nine passengers comprised of eight adults and one infant. The aircraft was also carrying National Government election boxes. The flight in accordance with the visual flight rules was estimated to take 18 minutes. There was no record of communication with the aircraft during the flight. Two minutes after the estimated time of arrival, when the Porter had not arrived, a search was commenced. On 18 April, search aircraft located the wreckage of the Porter at an elevation of about 12,000 feet on Mt Gergaji. The location was on the direct track between Ilaga and Mulia. The aircraft impacted the ground in an inverted attitude, and was destroyed by the impact forces and the post-impact fire. All occupants were fatally injured. The weather in the valleys along the route was mostly clear, with cloud on the mountains. The route flown by the pilot was the direct track, which passed over a mountain range, with a high peak adjacent to, and west of the track at about the midway point, at 13,700 feet. The investigation determined that it was likely that the pilot had flown the aircraft into cloud and lost control of the aircraft in instrument meteorological conditions. The impact signature was consistent with uncontrolled flight at the time of impact. This probably resulted from the pilot becoming spatially disoriented after entering cloud.
Probable cause:
The pilot may not have had adequate knowledge of the route and weather conditions, and may have been relying on Global Positioning System navigation, and was attempting to climb on the direct track over Mt Gergaji. It was likely that the pilot became spatially disoriented after entering cloud while operating under visual flight procedures, leading to a loss of control and uncontrolled impact with terrain.
Final Report: