Country
Operator Image

Crash of an Airbus A300B4-600 in Medan: 234 killed

Date & Time: Sep 26, 1997 at 1334 LT
Type of aircraft:
Operator:
Registration:
PK-GAI
Survivors:
No
Site:
Schedule:
Jakarta - Medan
MSN:
214
YOM:
1982
Flight number:
GA152
Country:
Region:
Crew on board:
12
Crew fatalities:
Pax on board:
222
Pax fatalities:
Other fatalities:
Total fatalities:
234
Captain / Total flying hours:
11978
Captain / Total hours on type:
782.00
Copilot / Total flying hours:
709
Copilot / Total hours on type:
709
Aircraft flight hours:
27095
Aircraft flight cycles:
16593
Circumstances:
On 26 September 1997 the Garuda Indonesia Flight GA 152, PK-GAI Airbus A300-B4 departed from the Jakarta Soekarno-Hatta International Airport at 04:41 UTC. The aircraft was on a regular scheduled passengers flight to Polonia International Airport of Medan, North Sumatera with estimated time of arrival 06:41 UTC. Flight GA 152 was flying under Instrument Flight Rules during daylight. Before the flight, the flight crew reported to Garuda Indonesia Flight Operations office to receive flight briefings, including Notice to Airmen (NOTAM), weather conditions and forecast en-route, at destination and alternate airports, as well as the flight plan. The NOTAM stated that the MDN VOR was overdue for maintenance and advised to use the facility ‘with caution', although the Medan VOR has been calibrated with both ground and flight calibration on 14 June 1997 and valid until 14 December 1997, the use of Medan VOR was classified as “restricted due to radial course alignment at 270 degrees radial”. At the time of flight-planning, the visibility from Medan TAFOR (26 September 1997, 00.00 UTC – 24.00 UTC) was 1000 meters in smoke. The dispatcher stated that he received information through company channel that the actual visibility at Medan was 400 meters in smoke, which was below the minimum required visibility for runway 05 ILS of 800 meters. At 06:12:51 GA 152 requested a descend clearance to Medan Control. Medan Control cleared the aircraft to descend to FL 150. On passing FL 150, GA 152 was informed that the aircraft was in radar contact, at a distance of 43 nautical miles from MDN VOR/DME. The crew was then instructed to descend to 3000 ft for a landing on Runway 05 and to reduce the speed to 220 knots to allow Bouraq flight BO 683 to takeoff from Runway 23 at 06:20:47. GA152 requested a speed of 250 knots below 10000 feet which was approved. At 6:27:12, Medan Approach instructed GA 152 to maintain altitude on heading to Medan VOR/DME. GA 152 confirmed this instruction at 6:27:21. At 06:27:50 Medan Approach transmitted an instruction “Merpati one five two you er .. turn left heading two four zero vectoring for intercept ILS runway zero five from the right side traffic now er.. rolling”. There was no response by any aircraft to this transmission. At 06:28:06 Medan Approach enquired “Indonesia one five two do you read”. GA 152 asked the ATC to repeat the message. At 06:28:13 Medan Approach instructed GA 152 to “Turn left heading er.. two four zero two three five now vectoring for intercept ILS runway zero five”. This instruction was acknowledged by GA 152. At 06:28:52 the PIC asked the Medan Approach whether the aircraft was clear from the mountainous area northwest from Medan. This was confirmed by Medan Approach, and GA 152 was instructed to continue turning left on heading 215°M. At 06:29:41, GA 152 was instructed to descend to 2000 ft and the crew acknowledged it. Recorded FDR information indicates the aircraft is essentially wings level, heading approx 225M° and passing through 3000 feet on descent. Then at 06:30:04 GA 152 was instructed to turn right heading 046 degrees, and to report when established on the localizer. This was acknowledged by GA 152, but misread the heading “Turn right heading zero four zero Indonesia one five two check established”. Meanwhile recorded FDR information indicates the aircraft commences a roll to the left, heading reducing indicating a left turn and passing through 2600 feet on descent. At 6:30:33, while turning left, First Officer reminded the Captain to turn right. Two seconds later GA 152 queried Medan Approach whether the turn is to the left or to the right onto heading 046 degrees. At 6:30:39 Medan Approach replied “Turning right Sir”, which was acknowledged by GA 152. FDR data shows that the aircraft began to roll to wings level. At 06:30:51 Medan Approach asked whether GA 152 was making a left turn or a right turn. Recorded FDR information indicates the aircraft was wings level and rolling to the right, heading approximately 135°M and increasing, at 2035 feet pressure altitude on descent. GA 152 responded “We are turning right now”. At 06:31:05 Medan Approach instructed GA 152 to continue turning left. Recorded FDR information showed that at this point the aircraft had passed the assigned 2000 ft altitude and continued descending. GA 152 replied “Err...confirm turning left we are starting to turn right now”. During the interview, the controller stated that it was around this time that he recognized that the aircraft went below the required altitude (1800 ft and descending). Recorded FDR information indicates the aircraft reduced right roll from approx 24.3º to 10.2° and then rolled right again to approx 25°, while heading was increasing indicated a right turn was being maintained and the aircraft continued descending. At 06:31:32 the sound of tree impact is recorded. The elevation of the initial impact with the trees was at about 1550 ft above sea level. The final impact on the bottom of a ravine approximately 600 meters from the first tree impact destroyed the aircraft, and 234 people on board of the aircraft perished. There were no ground casualties.
Probable cause:
There was confusion regarding turning direction of left turn instead of right turn at critical position during radar vectoring that reduced the flight crew’s vertical awareness while they were concentrating on the aircraft’s lateral changes. These caused the aircraft to continue descending below the assigned altitude of 2,000 feet and hit treetops at 1,550 feet above mean sea level.
Final Report:

Crash of a Douglas DC-10-30 in Fukuoka: 3 killed

Date & Time: Jun 13, 1996 at 1208 LT
Type of aircraft:
Operator:
Registration:
PK-GIE
Flight Phase:
Survivors:
Yes
Schedule:
Fukuoka – Denpasar – Jakarta
MSN:
46685
YOM:
1979
Flight number:
GA865
Country:
Region:
Crew on board:
15
Crew fatalities:
Pax on board:
260
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
10263
Captain / Total hours on type:
2641.00
Copilot / Total flying hours:
3910
Copilot / Total hours on type:
1437
Aircraft flight hours:
46325
Circumstances:
During the takeoff roll at Fukuoka-Itazuke Airport runway 16, at a speed of 158 knots, the captain started the rotation. During initial climb, at a height of about 3 metres, the right engine suffered a loss of power after a fan blade located on the 1st stage of the high pressure compressor disk separated. The N1 dropped to 23,7% and five seconds later, the flight engineer informed the crew about the failure of the engine n°1. The captain decided to abort the takeoff and landed back on runway. The aircraft contacted ground with a vertical acceleration of 2,1 g then thrust reversers were deployed and ground spoilers were extended. Unable to stop within the remaining distance, the aircraft overran, crossed a road, skidded for about 620 metres before coming to rest in an open field, bursting into flames. Three passengers were killed.
Probable cause:
Although the CAS was well in excess of V1 and the aircraft had already lifted off from the runway, the takeoff was aborted. Consequently the aircraft departed the end of the runway, came to rest and caught fire. It is estimated that contributing to the rejection of the takeoff under this circumstance was the fact that the CAP's judgement in the event of the engine failure was inadequate. Investigation revealed that the turbine blade that failed, had operated for 30913 hours and 6182 cycles. General Electric had advised customers to discard blades after about 6000 cycles.
Final Report:

Crash of a Douglas DC-9-32 in Denpasar

Date & Time: Jun 21, 1993 at 1125 LT
Type of aircraft:
Operator:
Registration:
PK-GNT
Survivors:
Yes
Schedule:
Yogyakarta - Denpasar
MSN:
47790/907
YOM:
1979
Flight number:
GA630
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
72
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Denpasar-I Gusti Ngurah Rai Airport, Bali, the aircraft was too high on the glide. The captain made an overcorrection, causing the aircraft to approach the runway with a high rate of descent. In a nose-up attitude, the aircraft struck the runway surface with a positive acceleration of 5 g. After landing, the crew completed the deceleration and braking procedure, vacated the runway and rolled to the gate where all occupants disembarked safely. A complete inspection of the aircraft by technicians revealed that it suffered major fuselage damages and was later declared as damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the flying crew.

Crash of a Douglas DC-9-32 in Medan: 23 killed

Date & Time: Apr 4, 1987 at 1440 LT
Type of aircraft:
Operator:
Registration:
PK-GNQ
Survivors:
Yes
Schedule:
Banda Aceh - Medan
MSN:
47741
YOM:
1976
Flight number:
GA035
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
37
Pax fatalities:
Other fatalities:
Total fatalities:
23
Circumstances:
On final approach to Medan-Polonia Airport, pilots encountered poor weather conditions with thunderstorm activity, turbulences and heavy rain falls. On final, the aircraft became unstable and lost height. The pilot increased engine power when the aircraft struck a television antenna, stalled and crashed in a field, bursting into flames. 23 occupants were killed while 22 others were injured.
Probable cause:
Loss of control on final approach probably caused by windshear and microburst.

Crash of a Douglas DC-9-32 in Denpasar

Date & Time: Dec 30, 1984
Type of aircraft:
Operator:
Registration:
PK-GNI
Survivors:
Yes
Schedule:
Jakarta - Denpasar
MSN:
47636
YOM:
1974
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
69
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following several errors during the final approach, the aircraft altitude over the runway 09 threshold was too high. The pilot-in-command decided to continue the landing and the touchdown was completed 1,800 meters past the runway threshold. Unable to stop within the remaining distance, the aircraft overran, lost its undercarriage and came to rest in a mangrove, broken in three. All 75 occupants were evacuated, some of them were injured. The aircraft was destroyed.
Probable cause:
Wrong approach configuration on part of the flying crew.

Crash of a Douglas DC-9-32 in Jakarta

Date & Time: Jun 11, 1984
Type of aircraft:
Operator:
Registration:
PK-GNE
Flight Type:
Survivors:
Yes
MSN:
47561/674
YOM:
1972
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
For unknown reasons, the aircraft landed hard and bounced three times. On the third impact, the aircraft recorded a positive aerodynamic force of 5,8 g that caused the fuselage to break in two between sections 737 and 756. All five crew members escaped uninjured while the aircraft was written off.

Crash of a Fokker F28 Fellowship 3000 in Bandar Lampung: 3 killed

Date & Time: Jun 2, 1983 at 0850 LT
Type of aircraft:
Operator:
Registration:
PK-GFV
Flight Phase:
Survivors:
Yes
Schedule:
Bandar Lampung - Jakarta
MSN:
11132
YOM:
1978
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
57
Pax fatalities:
Other fatalities:
Total fatalities:
3
Aircraft flight hours:
9334
Aircraft flight cycles:
9227
Circumstances:
At liftoff from Bandar Lampung-Branti Airport runway 14, the captain realized that one of the engine failed. He abandoned the takeoff procedure and landed back onto runway. Unable to stop within the remaining distance, the airplane overran, struck a concrete wall and crashed on a small hill located 138 meters past the runway end. Both pilot and a passenger were killed while 12 occupants were injured and 46 others escaped uninjured. The aircraft was destroyed.
Probable cause:
It was determined that none of the engine failed at takeoff. Following a poor flight preparation, the crew failed to follow the pre-takeoff checklist and adopted a wrong takeoff configuration.