Zone

Crash of an ATR72-600 in Semarang

Date & Time: Dec 25, 2016 at 1824 LT
Type of aircraft:
Operator:
Registration:
PK-WGW
Survivors:
Yes
Schedule:
Bandung – Semarang
MSN:
1234
YOM:
2015
Flight number:
IW1896
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
68
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4065
Captain / Total hours on type:
3805.00
Copilot / Total flying hours:
3300
Copilot / Total hours on type:
3200
Aircraft flight hours:
3485
Aircraft flight cycles:
4104
Circumstances:
On 25 December 2016, an ATR 72-600 aircraft registered PK-WGW was being operated by PT. Wings Abadi Airlines (Wings Air) as a scheduled passenger flight from Husein Sastranegara International Airport (WICC), Bandung to Ahmad Yani International Airport (WAHS), Semarang with flight number WON 1896. On board the aircraft were two pilots, two flight attendants and 68 passengers. There was no report or record of aircraft system malfunction prior to the departure. The aircraft departed from Bandung at 1734 LT (1034 UTC). The Pilot in Command (PIC) acted as Pilot Flying (PF) and the Second in Command (SIC) acted as Pilot Monitoring (PM). The flight from departure until commenced for landing approach was uneventful. At 1112 UTC, at night condition, the air traffic controller of Semarang Approach unit (approach controller) informed to all traffic that the rain was falling over the airport and the pilot confirmed whether the rain was heavy and was replied that it was slight rain. At 1115 UTC, the flight held over waypoint KENDA for separation with another aircraft and maintained altitude of 4,000 feet. Two minutes later, the flight was approved to descend to altitude of 3,000 feet. At 1118 UTC, the approach controller issued clearance for RNAV approach to runway 13 and advised the pilot to report when leaving waypoint KENDA. One minute later, the pilot reported leaving waypoint KENDA and the approach controller instructed to continue approach and to contact to the air traffic controller of Semarang Tower unit (tower controller). At 1120 UTC, the pilot advised to the tower controller that the aircraft was on final and the runway was in sight. The tower controller instructed to continue the landing approach and advised that the surface wind direction was 190° with velocity of 15 knots, altimeter setting 1,008 mbs and the runway was wet. At 1121 UTC, the tower controller had visual contact to the aircraft and issued landing clearance, the pilot read back the clearance and requested to reduce the approach light intensity. The tower controller reduced the light intensity and confirmed whether the intensity was appropriate then the pilot affirmed. At 1124 UTC, the aircraft touched down and bounced. After the third bounce, the pilot attempted to go around and the aircraft touched the runway. The tower controller noticed that the red light on the right wing was lower than the green light on the left wing. The aircraft moved to the right from the runway centerline and stopped near taxiway D. The tower controller realized that the aircraft was not in normal condition and pressed the crass bell then informed the Airport Rescue and Fire Fighting (ARFF) personnel by phone that there was aircraft accident near the taxiway D. At 1126 UTC, the pilot advised the tower controller that the aircraft stopped on the runway and requested assistance. The tower controller acknowledged the message and advised the pilot to wait for the assistance. While waiting the assistance, the pilot kept the engines run to provide lighting in the cabin. At 1129 UTC, the tower controller advised the pilot to shut down the engines since the ARFF personnel had arrived near the aircraft to assist the evacuation. Passenger evacuation completed at approximately 10 minutes after the aircraft stopped.
Probable cause:
Contributing Factors:
- The visual illusion of aircraft higher than the real altitude resulted in late flare out which made the aircraft bounced.
- The unrecovered bounce resulted in abnormal landing attitude with vertical acceleration up to 6 g and collapsed the right main landing gear.
Final Report:

Crash of a Boeing 737-8GP off Denpasar

Date & Time: Apr 13, 2013 at 1510 LT
Type of aircraft:
Operator:
Registration:
PK-LKS
Survivors:
Yes
Schedule:
Bandung - Denpasar
MSN:
38728/4350
YOM:
2013
Flight number:
LNI904
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
101
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15000
Captain / Total hours on type:
6173.00
Copilot / Total flying hours:
1200
Copilot / Total hours on type:
923
Aircraft flight hours:
142
Aircraft flight cycles:
104
Circumstances:
On 13 April 2013, a Boeing 737-800 aircraft, registered PK-LKS, was being operated by PT. Lion Mentari Airlines (Lion Air) on a scheduled passenger flight as LNI 904. The aircraft departed from Husein Sastranegara International Airport (WICC) Bandung at 0545 UTC to Ngurah Rai International Airport (WADD), Bali, Indonesia. The flight was the last sector of four legs scheduled for the crew on that day which were Palu (WAML) - Balikpapan (WALL) - Banjarmasin (WAOO) - Bandung (WICC) - Bali (WADD). The aircraft flew at FL 390, while the Second in Command (SIC) was the Pilot Flying (PF) and the Pilot in Command (PIC) was the Pilot Monitoring (PM). There were 2 pilots, 5 flight attendants and 101 passengers comprising 95 adults, 5 children and 1 infant making a total of 108 persons on board. The flight from the departure until start of the approach into Bali was uneventful. At 0648 UTC, the pilot made first communications with the Bali Approach controller (Bali Director) when the aircraft was located 80 Nm from BLI VOR. The pilot received clearance to proceed direct to the TALOT IFR waypoint and descend to 17,000 feet. At 0652 UTC, the Bali Director issued a further clearance for the pilot direct to KUTA point and descent to 8,000 feet. At 0659 UTC, the aircraft was vectored for a VOR DME approach for runway 09 and descent to 3,000 feet. At 0703 UTC, while the aircraft was over KUTA point, the Bali Director transferred communications with the aircraft to Bali Control Tower (Ngurah Tower). At 0704 UTC, the pilot contacted Ngurah Tower controller and advised that the aircraft was leaving KUTA point. The Ngurah Tower controller instructed the pilot to continue the approach and to reduce the aircraft speed to provide sufficient separation distance with another aircraft. At 0707 UTC, the Ngurah Tower issued take-off clearance for a departing aircraft on runway 09. At 0708 UTC, with LKS at approximately 1,600 feet AGL, the Ngurah Tower controller saw the aircraft on final approach and gave a landing clearance with additional information that the wind was from 120° at 05 knots. At 0708:47 UTC, the aircraft Enhance Ground Proximity Warning System (EGPWS) aural alert called “ONE THOUSAND”, the SIC said one thousand, stabilized, continue, prepare for go-around missed approach three thousand. The FDR showed that the pilot flown using LNAV (Lateral Navigation) and VNAV (Vertical Navigation) during the approach until disengagement of the Auto Pilot. The sequence of events during the final approach is based on the recorded CVR and FDR data, and information from crew interviews as follows: At 0708:56 UTC, while the aircraft altitude was approximately 900 feet AGL, the SIC commented that the runway was not in sight, whereas the PIC commented “OK. Approach light in sight, continue”. At 0709:33 UTC, after the EGPWS aural alert “MINIMUM” sounded at an aircraft altitude of approximately 550 feet AGL, the SIC disengaged the autopilot and the auto-throttle and then continued the approach. At 0709:43 UTC, the EGPWS called “THREE HUNDRED”. At 0709:47 UTC, the CVR recorded a sound similar to rain hitting the windshield. At 0709:49 UTC, the EGPWS called “TWO HUNDRED”. At 0709:53 UTC, while the aircraft altitude was approximately 150 feet AGL, the PIC took over control of the aircraft. The SIC handed control to the PIC and stated that he could not see the runway. At 0710:01 UTC, after the EGPWS called “TWENTY”, the PIC commanded for go-around. At 0710:02 UTC, the aircraft impacted the water, short of the runway. The aircraft stopped facing to the north at about 20 meters from the shore or approximately 300 meters south-west of the beginning of runway 09. Between 0724 UTC to 0745 UTC, three other aircraft took-off and six aircraft landed using runway 09. At 0750 UTC, the airport was closed until 0850 UTC. At 0755 UTC, all occupants were completely evacuated, the injured passengers were taken to the nearest hospitals and uninjured occupants to the airport crisis centre.
Probable cause:
The National Transportation Safety Committee initial findings on the accident flight are as follows:
- The aircraft was airworthy prior to impact and has an item on the DMI (deferred maintenance item) category C (right engine oil filter).
- All crew has valid licenses and medical certificates.
- The Second in Command (SIC) acted as Pilot Flying (PF).
- The flight performed a VOR DME approach runway 09, and the published Minimum Descent Altitude (MDA) was 465 ft AGL.
- The approach configuration used was flap 40.
- At 900 ft AGL the PF did not have the runway in sight.
- Upon reaching the MDA the flight profile indicated a constant path.
- The PIC took over control of the aircraft at about 150 ft radio altitude.
- The SIC handed over control to the PIC at about 150 ft and stated that he could not see the runway.
- The final approach phase of the flight profile was outside the envelope of the EGPWS warning, therefore no EGPWS warning was recorded on the CVR.
The NTSC concluded in its final report that the accident was caused by the following factors:
- The aircraft flight path became unstable below minimum descends altitude (MDA) with the rate of descend exceeding 1000 feet per minute and this situation was recognized by both pilots.
- The flight crew loss of situational awareness in regards of visual references once the aircraft entered a rain cloud during the final approach below minimum descends altitude (MDA).
- The PIC decision and execution to go-around was conducted at an altitude which was insufficient for the go-around to be executed successfully.
- The pilots of accident aircraft was not provided with timely and accurate weather condition despite the weather around the airport and particularly on final approach to the airport was changing rapidly.
Final Report:

Crash of a Fokker F27 Friendship 400M in Bandung: 24 killed

Date & Time: Apr 6, 2009 at 1230 LT
Type of aircraft:
Operator:
Registration:
A-2703
Survivors:
No
Schedule:
Bandung - Bandung
MSN:
10538
YOM:
1976
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
24
Circumstances:
The aircraft was performing a paratroopers/skydiving mission in the region of Bandung, taking part to a military program with members of the Special Forces on board. While approaching runway 29 with 20 knots crosswind, the aircraft went out of control and crashed onto a hangar, bursting into flames. All 24 occupants were killed, among them 17 paratroopers, one instructor and 6 crew members.

Crash of a Fokker F27 Friendship in Bandung: 28 killed

Date & Time: Jul 17, 1997 at 1155 LT
Type of aircraft:
Operator:
Registration:
PK-YPM
Survivors:
Yes
Site:
Schedule:
Bandung - Jakarta
MSN:
10415
YOM:
1969
Flight number:
TGN304
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
45
Pax fatalities:
Other fatalities:
Total fatalities:
28
Circumstances:
The aircraft departed Bandung-Husein Sastranegara Airport on a regular schedule flight to Jakarta, carrying 45 passengers and 5 crew members. Shortly after takeoff, the captain informed ATC that the left engine lost power and elected to diver to the Bandung-Sulaiman AFB for an emergency landing. On final approach to runway 13, the crew was unable to maintain a safe altitude when the aircraft struck roofs and crashed. Twenty occupants were rescued while 28 others were killed, including all five crew members. All occupants were Indonesian citizens except for one passenger from Singapore.
Probable cause:
Failure of the left engine for unknown reasons.

Crash of a Casa-Nurtanio CN235-100 on Mt Puntang: 31 killed

Date & Time: Oct 18, 1992 at 1330 LT
Operator:
Registration:
PK-MNN
Flight Phase:
Survivors:
No
Site:
Schedule:
Semarang - Bandung
MSN:
N013
YOM:
1990
Flight number:
MZ5601
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
31
Circumstances:
The crew initiated the descent to Bandung-Husein Sastranegara Airport and encountered poor weather conditions with heavy rain falls. Too low, the aircraft struck the slope of Mt Puntang located about 25 km south of Bandung Airport. The aircraft disintegrated on impact and all 31 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew initiated the descent prematurely for unknown reasons.

Crash of a Lockheed C-130H-30 Hercules in Jakarta: 135 killed

Date & Time: Oct 5, 1991 at 1500 LT
Type of aircraft:
Operator:
Registration:
A-1324
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Jakarta - Bandung
MSN:
4927
YOM:
1982
Country:
Region:
Crew on board:
12
Crew fatalities:
Pax on board:
122
Pax fatalities:
Other fatalities:
Total fatalities:
135
Circumstances:
The four engine aircraft was returning to Bandung, carrying 122 airmen who had just took part to the annual Armed Forces Day ceremony at Jakarta-Halim Perdanakusuma Airport. One minute after takeoff, while in initial climb, the crew declared an emergency and reported engine problems. After being cleared to return for an emergency landing, the crew lost control of the airplane that stalled and crashed on a building housing the Department of Labour. A passenger survived while 133 other occupants were killed as well as two security guards working in the building.
Probable cause:
Loss of control after the engine n°3 caught fire during initial climb for unknown reasons.

Crash of a De Havilland DH.60M Moth in Lembang: 1 killed

Date & Time: Apr 26, 1936
Type of aircraft:
Registration:
PK-SAI
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bandung - Bandung
MSN:
1485
YOM:
1931
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
An instructor and one female student pilot departed Bandung on a local training flight. En route, the airplane collided with high tension wires and crashed in Lembang, about 10 km northeast of the airfield. The instructor H. C. Keim was slightly injured while the student pilot, Mrs. Van Lierop, was killed.

Crash of an Avro 504K in Cisarua

Date & Time: Mar 14, 1934
Type of aircraft:
Operator:
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bandung - Bandung
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot departed Bandung on a solo training flight. The engine failed in flight and the pilot bailed out and abandoned the aircraft that dove into the ground and crashed in a ravine. The airplane was destroyed and the pilot Lt Van Velthoven was uninjured.
Probable cause:
Engine failure in flight.