Zone

Crash of a Boeing 737-524 off Jakarta: 62 killed

Date & Time: Jan 9, 2021 at 1440 LT
Type of aircraft:
Operator:
Registration:
PK-CLC
Flight Phase:
Survivors:
No
Schedule:
Jakarta - Pontianak
MSN:
27323/2616
YOM:
1994
Flight number:
SJY182
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
56
Pax fatalities:
Other fatalities:
Total fatalities:
62
Captain / Total flying hours:
17904
Captain / Total hours on type:
9023.00
Copilot / Total flying hours:
5107
Copilot / Total hours on type:
4957
Aircraft flight hours:
62983
Aircraft flight cycles:
40383
Circumstances:
On 9 January 2021, a Boeing 737-500 aircraft, registration PK-CLC, was being operated by PT. Sriwijaya Air on a scheduled passenger flight from Soekarno-Hatta International Airport (WIII), Jakarta to Supadio International Airport (WIOO), Pontianak . The flight number was SJY182. According to the flight plan filed, the fuel endurance was 3 hours 50 minutes. At 0736 UTC (1436 LT) in daylight conditions, Flight SJY182 departed from Runway 25R of Jakarta. There were two pilots, four flight attendants, and 56 passengers onboard the aircraft. At 14:36:46 LT, the SJY182 pilot contacted the Terminal East (TE) controller and was instructed “SJY182 identified on departure, via SID (Standard Instrument Departure) unrestricted climb level 290”. The instruction was read back by the pilot. At 14:36:51 LT, the Flight Data Recorder (FDR) data recorded that the Autopilot (AP) system engaged at altitude of 1,980 feet. At 14:38:42 LT, the FDR data recorded that as the aircraft climbed past 8,150 feet, the thrust lever of the left engine started reducing, while the thrust lever position of the right engine remained. The FDR data also recorded the left engine N1 was decreasing whereas the right engine N1 remained. At 14:38:51 LT, the SJY182 pilot requested to the TE controller for a heading change to 075° to avoid weather conditions and the TE controller approved the request. At 14:39:01 LT, the TE controller instructed SJY182 pilot to stop their climb at 11,000 feet to avoid conflict with another aircraft with the same destination that was departing from Runway 25L. The instruction was read back by the SJY182 pilot. At 14:39:47 LT, the FDR data recorded the aircraft’s altitude was about 10,600 feet with a heading of 046° and continuously decreasing (i.e., the aircraft was turning to the left). The thrust lever of the left engine continued decreasing. The thrust lever of the right engine remained. At 14:39:54 LT, the TE controller instructed SJY182 to climb to an altitude of 13,000 feet, and the instruction was read back by an SJY182 pilot at 14:39:59 LT. This was the last known recorded radio transmission by the flight. At 14:40:05 LT, the FDR data recorded the aircraft altitude was about 10,900 feet, which was the highest altitude recorded in the FDR before the aircraft started its descent. The AP system then disengaged at that point with a heading of 016°, the pitch angle was about 4.5° nose up, and the aircraft rolled to the left to more than 45°. The thrust lever position of the left engine continued decreasing while the right engine thrust lever remained. At 14:40:10 LT, the FDR data recorded the autothrottle (A/T) system disengaged and the pitch angle was more than 10° nose down. About 20 seconds later the FDR stopped recording. The last aircraft coordinate recorded was 5°57'56.21" S 106°34'24.86" E. At 14:40:37 LT, the TE controller called SJY182 to request for the aircraft heading but did not receive any response from the pilot. At 14:40:48 LT, the radar target of the aircraft disappeared from the TE controller radar screen. At 14:40:46 LT, the TE controller again called SJY182 but did not receive any response from the pilot. The TE controller then put a measurement vector on the last known position of SJY182 and advised the supervisor of the disappearance of SJY182. The supervisor then reported the occurrence to the operation manager. The TE controller repeatedly called SJY182 several times and also asked other aircraft that flew near the last known location of SJY182 to call the SJY182. The TE controller then activated the emergency frequency of 121.5 MHz and called SJY182 on that frequency. All efforts were unsuccessful to get any responses from the SJY182 pilot. About 1455 LT, the operation manager reported the occurrence to the Indonesian Search and Rescue Agency (Badan Nasional Pencarian dan Pertolongan/BNPP). At 1542 LT, the Air Traffic Services (ATS) provider declared the uncertainty phase (INCERFA) of the SJY182. The distress phase of SJY182 (DETRESFA) was subsequently declared at 1643 LT.
Probable cause:
The following contributing factors were identified:
• The corrective maintenance processes of the A/T problem were unable to identify the friction or binding within the mechanical system of the thrust lever and resulted in the prolonged and unresolved of the A/T problem.
• The right thrust lever did not reduce when required by the A/P to obtain selected rate of climb and aircraft speed due to the friction or binding within the mechanical system, as a result, the left thrust lever compensated by moving further backward which resulted in thrust asymmetry.
• The delayed CTSM activation to disengage the A/T system during the thrust asymmetry event due to the undervalued spoiler angle position input resulted in greater power asymmetry.
• The automation complacency and confirmation bias might have led to a decrease in active monitoring which resulted in the thrust lever asymmetry and deviation of the flight path were not being monitored.
• The aircraft rolled to the left instead of to the right as intended while the control wheel deflected to the right and inadequate monitoring of the EADI might have created assumption that the aircraft was rolling excessively to the right which resulted in an action that was contrary in restoring the aircraft to safe flight parameters.
• The absence of the guidance of the national standard for the UPRT, may have contributed to the training program not being adequately implemented to ensure that pilots have enough knowledge to prevent and recover of an upset condition effectively and timely.
Final Report:

Crash of a Boeing 737 MAX 8 off Jakarta: 189 killed

Date & Time: Oct 29, 2018 at 0631 LT
Type of aircraft:
Operator:
Registration:
PK-LQP
Flight Phase:
Survivors:
No
Schedule:
Jakarta - Pangkal Pinang
MSN:
43000
YOM:
2018
Flight number:
JT610
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
181
Pax fatalities:
Other fatalities:
Total fatalities:
189
Captain / Total flying hours:
6028
Captain / Total hours on type:
5176.00
Copilot / Total flying hours:
5174
Copilot / Total hours on type:
4286
Aircraft flight hours:
895
Aircraft flight cycles:
443
Circumstances:
The aircraft departed runway 25L at Jakarta-Soekarno-Hatta Airport at 0621LT bound for Pangkal Pinang, carrying 181 passengers and 8 crew members. The crew was cleared to climb but apparently encountered technical problems and was unable to reach a higher altitude than 5,375 feet. At this time, the flight shows erratic speed and altitude values. The pilot declared an emergency and elected to return to Jakarta when control was lost while at an altitude of 3,650 feet and at a speed of 345 knots. The airplane entered a dive and crashed 12 minutes after takeoff into the Kerawang Sea, about 63 km northeast from its departure point. The airplane disintegrated on impact and few debris were already recovered but unfortunately no survivors. It has been reported that the aircraft suffered various technical issues during the previous flight on Sunday night but was released for service on Monday morning. Brand new, the airplane was delivered to Lion Air last August 18. At the time of the accident, weather conditions were considered as good. The Cockpit Voice Recorder (CVR) was found on 14 January 2019. In the initial stages of the investigation, it was found that there is a potential for repeated automatic nose down trim commands of the horizontal stabilizer when the flight control system on a Boeing 737 MAX aircraft receives an erroneously high single AOA sensor input. Such a specific condition could among others potentially result in the stick shaker activating on the affected side and IAS, ALT and/or AOA DISAGREE alerts. The logic behind the automatic nose down trim lies in the aircraft's MCAS (Maneuvering Characteristics Augmentation System) that was introduced by Boeing on the MAX series aircraft. This feature was added to prevent the aircraft from entering a stall under specific conditions. On November 6, 2018, Boeing issued an Operations Manual Bulletin (OMB) directing operators to existing flight crew procedures to address circumstances where there is erroneous input from an AOA sensor. On November 7, the FAA issued an emergency Airworthiness Directive requiring "revising certificate limitations and operating procedures of the airplane flight manual (AFM) to provide the flight crew with runaway horizontal stabilizer trim procedures to follow under certain conditions.
Probable cause:
Contributing factors defines as actions, omissions, events, conditions, or a combination thereof, which, if eliminated, avoided or absent, would have reduced the probability of the accident or incident occurring, or mitigated the severity of the
consequences of the accident or incident. The presentation is based on chronological order and not to show the degree of contribution.
1. During the design and certification of the Boeing 737-8 (MAX), assumptions were made about flight crew response to malfunctions which, even though consistent with current industry guidelines, turned out to be incorrect.
2. Based on the incorrect assumptions about flight crew response and an incomplete review of associated multiple flight deck effects, MCAS’s reliance on a single sensor was deemed appropriate and met all certification requirements.
3. MCAS was designed to rely on a single AOA sensor, making it vulnerable to erroneous input from that sensor.
4. The absence of guidance on MCAS or more detailed use of trim in the flight manuals and in flight crew training, made it more difficult for flight crews to properly respond to uncommanded MCAS.
5. The AOA DISAGREE alert was not correctly enabled during Boeing 737-8 (MAX) development. As a result, it did not appear during flight with the mis-calibrated AOA sensor, could not be documented by the flight crew and was therefore not available to help maintenance identify the mis-calibrated AOA sensor.
6. The replacement AOA sensor that was installed on the accident aircraft had been mis-calibrated during an earlier repair. This mis-calibration was not detected during the repair.
7. The investigation could not determine that the installation test of the AOA sensor was performed properly. The mis-calibration was not detected.
8. Lack of documentation in the aircraft flight and maintenance log about the continuous stick shaker and use of the Runaway Stabilizer NNC meant that information was not available to the maintenance crew in Jakarta nor was it available to the accident crew, making it more difficult for each to take the appropriate actions.
9. The multiple alerts, repetitive MCAS activations, and distractions related to numerous ATC communications were not able to be effectively managed. This was caused by the difficulty of the situation and performance in manual handling, NNC execution, and flight crew communication, leading to ineffective CRM application and workload management. These performances had previously been identified during training and reappeared during the accident flight.
Final Report:

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 Boeing 737-36M in Yogyakarta

Date & Time: Dec 20, 2011 at 1713 LT
Type of aircraft:
Operator:
Registration:
PK-CKM
Survivors:
Yes
Schedule:
Jakarta - Yogyakarta
MSN:
28333/2810
YOM:
1996
Flight number:
SJY230
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
131
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
29801
Copilot / Total flying hours:
562
Aircraft flight hours:
31281
Aircraft flight cycles:
21591
Circumstances:
On 20 December 2011, a Boeing 737-300 aircraft, registered PK-CKM, was being operated by PT. Sriwijaya Air on a schedule passenger flight SJ230 from Soekarno Hatta International Airport (WIII) Jakarta to Adisutjipto International Airport (WARJ), Yogyakarta. There were 141 persons on board; two pilots, four cabin crews and 135 passengers consisted124 adult, 7 children and 4 infant. The aircraft departed from Jakarta at 14.00 LT (07.00 UTC), the pilot in command was the pilot flying and the co-pilot was the pilot monitoring. At 08.10 UTC the aircraft made holding at 8 NM from JOG VOR due to bad weather. After the second holding and the weather was deteriorated, the airport authority closed the airport for takeoff and landing. The pilot requested divert to Juanda Airport (WARR), Surabaya and landed at 08.40 UTC. After refuelling and received the information about weather improvement in Yogyakarta then the aircraft departed, at 09.20 UTC, in this sequence of flight the PIC acted as PF, with 137 persons on board consisted of two pilots, four cabin crews and 131 passengers consisted 120 adult, 7 children and 4 infant. The aircraft was on the fifth sequence from seven aircraft approaching Adisucipto airport Yogyakarta. Passing JOG VOR it was seen on radar screen that the aircraft speed was read 203 Kts at 2700 ft. Approach Controller instructed to reduce the speed. At about 1200 ft, the pilot had the runway insight and disengaged the autopilot and auto throttle. The pilot made correction to the approach profile by roll up to 25 degrees and rate of descend up to 2040 ft per minute. The GPWS warning of ‘pull up’ and sink ‘rate were’ activated. Aircraft touched down at speed 156 Kts of 138 Kts target landing speed. During landing roll, the auto-brake and spoiler activated automatically. The thrust reverse were deployed and the N1 were recorded on the FDR increase and decrease to idle before increased to 80% prior to aircraft stop. The PIC noticed that the aircraft would not be able to stop in the runway and decided to turn the aircraft to the left. The aircraft stopped at 75 meter from the end of runway 09 and 54 meter on the left side of the centre line. Most of the passenger evacuated through left and right forward escape slides. All passengers were evacuated safely. The passenger on the stretcher case was evacuated by the airport rescue. 6 passengers reported minor injured while all crew and the remaining passengers were not injured. The aircraft suffered major damage on the right main and nose wheel.
Probable cause:
Findings:
1. The aircraft was airworthy prior the accident. There was no evidence that the aircraft had malfunction during the flight.
2. The crew had valid license and medical certificate. There was no evidence of crew incapacitation.
3. In this flight Pilot in Command acted as Pilot Flying and Second In command acted as Pilot Monitoring.
4. The flight crew did not conduct approach crew briefing.
5. There was no checklist reading.
6. The PIC as Pilot Flying did not have the instrument approach procedure immediately available to review during approach.
7. During the approach, the PIC course indicator was set at 091 and the SIC was at 084.
8. The rate of descend recorded vary and up to 1920 ft per minute and below 500 ft AGL the rate of descend recorded up to 2040 ft per minute.
9. The approach did not meet the stabilize approach criteria as stated in the FCOM.
10. There were several GPWS warning of ‘sink rate’ and ‘pull up’ activated during approach.
11. The aircraft touched down at speed 156 Kt before bounced, instead of 138 Kt target landing speed.
12. The flap extended to 40 after the aircraft touch down.
13. The FDR recorded reduction in N1 during thrust reverser activation after landing.
14. The CRM was not well implemented.
Factors:
Unsuccessful to recognize the two critical elements, namely fixation and complacency affected pilot decision to land the aircraft while the approach was not meet the criteria of stabilized approach.
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 McDonnell Douglas MD-90-30 in Jakarta

Date & Time: Mar 9, 2009 at 1535 LT
Type of aircraft:
Operator:
Registration:
PK-LIL
Survivors:
Yes
Schedule:
Ujung Pandang - Jakarta
MSN:
53573/2182
YOM:
1997
Flight number:
LNI793
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
166
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25000
Captain / Total hours on type:
5000.00
Copilot / Total flying hours:
5000
Copilot / Total hours on type:
800
Aircraft flight hours:
18695
Aircraft flight cycles:
14507
Circumstances:
Lion Mentari Airline (Lion Air) as flight number LNI-793, departed from Sultan Hasanuddin Airport (WAAA), Makassar, Ujung Pandang, Sulawesi at 0636 UTC for Soekarno-Hatta International Airport (WIII), Jakarta. The estimated flight hour from Makassar to Jakarta was 2 hours. The crew consisted of two pilots and four flight attendants. There were 166 adult passengers. The copilot was the pilot flying for the sector, and the pilot in command (PIC) was the support/monitoring pilot. During the approach to runway 25L at Jakarta, the weather at the airport was reported as wind direction 200 degrees, wind speed 20 knots, visibility 1,000 meters, and rain. The PIC reported that he decided to take over control from the copilot. The PIC later reported that he had the runway in sight passing through 1,000 feet on descent, and he disengaged the autopilot at 400 feet. At about 50 feet the aircraft drifted to the right and the PIC initiated corrective action to regain the centreline. The aircraft touched down to the left of the runway 25L centerline and then commenced to drift to the right. The PIC reported that he immediately commenced corrective action by using thrust reverser, but the aircraft increasingly crabbed along the runway with the tail to the right of runway heading. The investigation subsequently found that the right thrust reverser was deployed, but left thrust reverser was not deployed. The aircraft stopped at 0835 on the right side of the runway 25L, 1,095 meters from the departure end of the runway on a heading of 152 degrees; 90 degrees to the runway 25L track. The main landing gear wheels collapsed, and still attached to the aircraft, were on the shoulder of the runway and the nose wheel was on the runway. The passengers and crew disembarked via the front right escape slide and right emergency exit windows. None of the occupants were injured
Probable cause:
The aircraft was not stabilized approach at 100 feet above the runway.
Final Report:

Crash of a Boeing 737-2H6 in Jambi: 1 killed

Date & Time: Aug 27, 2008 at 1634 LT
Type of aircraft:
Operator:
Registration:
PK-CJG
Survivors:
Yes
Schedule:
Jakarta - Jambi
MSN:
23320/1120
YOM:
1985
Flight number:
SJY062
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
124
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
7794
Captain / Total hours on type:
6238.00
Copilot / Total flying hours:
5254
Copilot / Total hours on type:
4143
Aircraft flight hours:
49996
Aircraft flight cycles:
54687
Circumstances:
On 27 August 2008, a Boeing 737-200 aircraft, registered PK-CJG, was being operated on a scheduled passenger service from Soekarno-Hatta International Airport, Jakarta to Sultan Thaha Airport, Jambi with flight number SJY062. On board the flight were two pilots, four flight attendants, and 124 passengers. The Pilot in Command (PIC) acted as Pilot Flying (PF) while the Second in Command (SIC) acted as Pilot Monitoring (PM). The flight time from Jakarta to Jambi was estimated to be about one hour and the aircraft was dispatched with approximately 4 hours of fuel endurance. The number one electrical engine driven generator was unserviceable, as such the Auxiliary Power Unit (APU) generator was used during the flight to maintain two generators operation. Prior to descent into Jambi, the PIC conducted the crew briefing and stated a plan for Makinga straight-in approach to runway 31 with flap 40°, reviewed the go-around procedures and stated that Palembang was the alternate airport.There was no abnormality recorded nor reported until the PIC commenced the approach to Jambi. At 09:18 UTC, the SIC contacted Thaha Tower controller and reported that the aircraft was descending and passing FL160 and had been cleared by Palembang Approach control to descend to 12,000 feet. The Thaha Tower controller issued a clearance to descend to 2500 feet and advised that runway 31 was in use. The SIC asked about the weather conditions and was informed that the wind was calm, rain over the field and low cloud on final approach to runway 31. The PIC flew the aircraft direct to intercept the final approach to runway 31. While descending through 2500 feet, and about 8 miles from the VOR, the flap one degree and flap 5° were selected. Subsequently the landing gear was extended and flap 15° was selected. 13 seconds after flap 15 selection, the pilots noticed that the hydraulic system A low pressure warning light illuminated, and also the hydraulic system A quantity indicator showed zero. The PIC commanded the SIC to check the threshold speed for the existing configuration of landing, weight and with flap 15°. The SIC called out that the threshold speed was 134 kts and the PIC decided to continue with the landing. The PIC continued the approach and advised the SIC that he aimed to fly the aircraft slightly below the normal glide path in order to get more distance available for the landing roll. The aircraft touched down at 0930 UTC and during the landing roll, the PIC had difficulty selecting the thrust reversers. The PIC the applied manual braking. During the subsequent interview, the crew reported that initially they felt a deceleration then afterward a gradual loss of deceleration. The PIC reapplied the brakes and exclaimed to the SIC about the braking condition, then the SIC also applied the brakes to maximum in responding to the situation. The aircraft drifted to the right of the runway centre line about 200 meters prior to departing off the end of the runway, and stopped about 120 meters from the end of the runway 31 in a field about 6 meters below the runway level. Three farmers who were working in that area were hit by the aircraft. One was fatally injured and the other two were seriously injured. The pilots reported that, after the aircraft came to a stop, they executed the Emergency on Ground Procedure. The PIC could not put both start levers to the cut-off position, and also could not pull the engines and APU fire warning levers. The PIC also noticed that the speed brake lever did not extend. The radio communications and the interphone were also not working. The flight attendants noticed a significant impact before the aircraft stopped. They waited for any emergency command from the PIC before ordering the evacuation. However, the passengers started to evacuate the aircraft through the right over-wing exit window before commanded by the flight attendants. The flight attendants subsequently executed the evacuation procedure without command from the PIC. The left aft cabin door was blocked by the left main landing gear that had detached from the aircraft and the flight attendants were unable to open the door. The right main landing gear and both engines were also detached from the aircraft. The Airport Rescue and Fire Fighting (ARFF) come to the crash site and activated the extinguishing agent while the passengers were evacuating the aircraft. The PIC, SIC and FA1 were the last persons to evacuate the aircraft. The APU was still running after all passengers and crew evacuation completed, afterward one company engineer went to the cockpit and switched off the APU. All crew and passengers safely evacuated the aircraft. No significant property damage was reported.
Probable cause:
Contributing Factors:
- When the aircraft approach for runway 31, the Loss of Hydraulic System A occurred at approximately at 1,600 feet. At this stage, there was sufficient time for pilots to conduct a missed approach and review the procedures and determine all the consequences prior to landing the aircraft.
- The smooth touchdown with a speed 27 kts greater than Vref and the absence of speed brake selection, led to the aircraft not decelerating as expected.
Final Report:

Crash of a Boeing 737-408 in Batam

Date & Time: Mar 10, 2008 at 1020 LT
Type of aircraft:
Operator:
Registration:
PK-KKT
Survivors:
Yes
Schedule:
Jakarta - Batam
MSN:
24353/1721
YOM:
1989
Flight number:
DHI292
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
171
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 10 March 2008, a Boeing Company 737-400 aircraft, registered PK-KKT, was being operated by Adam SkyConnection Airlines (Adam Air) as scheduled passenger flight with flight number DHI292. The flight departed Soekarno – Hatta Airport, Jakarta at 01:30 UTC with destination Hang Nadim Airport, Batam and the estimated time of arrival was 03:05 UTC. On board in this flight were 177 people consisted of two pilots, four flight attendants, and 171 passengers. The Pilot in Command (PIC) acted as pilot flying (PF) and the Second in Command (SIC) acted as pilot monitoring (PM). The flight until commencing descend was uneventful. Prior to descend, the flight crew received weather information indicating that the weather was fine. At 0302 UTC the flight crew contacted Hang Nadim tower controller and informed them that the visibility was 1,000 meters and they were sequence number three for landing runway 04. The flight crew of the aircraft on sequence number two informed to Hang Nadim tower controller that the runway was insight at an altitude of about 500 feet. The Hang Nadim tower controller forwarded the information to the flight crew of DHI 292, and followed this by issuing landing clearance, and additional information that the wind velocity was 360 degrees at 8 knots and heavy rain. The DHI 292 flight crew acknowledged the information. The landing configuration used flaps 40 degrees with landing speed of 136 knots. The flight crew were able to see the runway prior to the Decision Altitude (DA), however the PIC was convinced that continuing the approach to landing was unsafe and elected to go around. The Hang Nadim tower controller instructed the flight crew to climb to 3000 feet, maintain runway heading, and contact Singapore Approach. At 0319 UTC, DHI 292 was established on the localizer runway 04, and the Hang Nadim tower controller informed them that the visibility improved to 2,000 meters. While on final approach, the flight crew DHI 292 reported that the runway was in sight and the Hang Nadim tower controller issued a landing clearance. On touchdown, the crew felt that the main wheels barely touch the runway first. During the landing roll, as the ground speed decreased below 30 knots, the aircraft yawed to the right. The flight crew attempted to steer the aircraft back to centerline by applying full left rudder. The aircraft continued yaw to the right and came to stop on the runway shoulder at approximately 40 meters from the right side of the runway edge, and 2,760 meters from the runway 04 threshold. No one was injured in this accident. The aircraft was seriously damaged with the right main landing gear assembly detached and collapsing backward and damaging the right wing and flaps. The right engine was displaced from its attachment point.
Probable cause:
The Flight Data Recorder (FDR) and the Cockpit Voice Recorder (CVR) data were downloaded. The CVR data showed that the aircraft was flying below the correct glide path indicated by a glide slope aural warning, and the crew had difficulty in recovering the condition. The CVR also recorded landing gear warning after touchdown which indicated the landing gear had collapsed. The FDR data showed that the vertical acceleration during landing was 2.97 g, however this amount of vertical acceleration should not damage the landing gear. The FDR data showed that just after touchdown, the right main landing gear collapsed. The FDR also recorded that the aircraft experienced hard landing and had bounced on a previous flight, and the value of the vertical acceleration recorded was 1.78 g. It was most likely that the hard landing and bounce had affected the strength of the landing gear. The examination of the failed landing gear also found corrosion on the fracture surface of the right main landing gear strut.
Final Report:

Crash of a Boeing 737-230 in Malang

Date & Time: Nov 1, 2007 at 1324 LT
Type of aircraft:
Operator:
Registration:
PK-RIL
Survivors:
Yes
Schedule:
Jakarta – Malang
MSN:
22137/788
YOM:
1981
Flight number:
RI260
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
89
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
19357
Captain / Total hours on type:
10667.00
Copilot / Total flying hours:
2300
Copilot / Total hours on type:
1528
Aircraft flight hours:
57823
Circumstances:
On 1 November 2007, a Boeing Company B737-200 aircraft, registered PK-RIL, operated by PT. Mandala Airlines as flight number MDL 260, was on a scheduled passenger flight from Jakarta Soekarno-Hatta International Airport, Jakarta, to Abdurrachman Saleh Airport, Malang, East Java. The pilot in command (PIC) was the handling pilot, and the copilot was the support/monitoring pilot. There were 94 persons on board the aircraft, consisting of two pilots, three cabin crew, and 89 passengers. The aircraft landed at Malang at 1324 Western Indonesian Standard Time (06:24 Coordinated Universal Time (UTC). It was reported to have been raining heavily when the aircraft landed on runway 35 at Malang. The aircraft bounced twice after the initial severe hard landing, and the lower drag strut of the nose landing gear fractured, resulting in the rearwards collapse of the nose landing gear and separation of the lower nose landing gear shock strut and wheel assembly. The aircraft’s nose then contacted the runway, and the aircraft came to rest 290 metres before the departure end of runway 17. The crew subsequently reported that during the visual segment of the landing approach, they realized that the aircraft was too high with reference to the precision approach path indicator (PAPI) for runway 35. The PIC increased the aircraft’s rate of descent (ROD) to capture the PAPI. The high ROD was not arrested, and as a consequence, the severe hard landing occurred which substantially damaged the aircraft. No one of the passengers or crew was injured.
Probable cause:
The flight crew did not appear to have an awareness that the aircraft was above the desired approach path to runway 35 at Malang until they sighted the visual approach slope indication lighting system. The pilot in command continued the approach in reduced visibility and heavy rain; marginal visual meteorological conditions. Non-adherence by the flight crew to stabilized approach procedures, which resulted in the initial severe hard landing at Malang, together with the omission of a high bounced landing recovery, resulted in substantial damage to the aircraft. The following findings were identified:
- The PIC allowed the approach at Malang to become unstabilized and did not correct that condition.
- The PIC continued the approach in reduced visibility and heavy rain; marginal visual meteorological conditions.
- Neither pilot responded appropriately to the ground proximity warning system voice aural ‘SINK RATE’ or ‘PULL UP’ warnings that sounded during the final approach to Malang.
- The PIC did not initiate action to recover from the high bounced landing following the initial severe hard landing impact.
- The PIC did not ensure that effective crew coordination was maintained during the landing approach.
Final Report:

Crash of a Boeing 737-497 in Yogyakarta: 21 killed

Date & Time: Mar 7, 2007 at 0758 LT
Type of aircraft:
Operator:
Registration:
PK-GZC
Survivors:
Yes
Schedule:
Jakarta - Yogyakarta
MSN:
25664
YOM:
1992
Flight number:
GIA200
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
133
Pax fatalities:
Other fatalities:
Total fatalities:
21
Captain / Total flying hours:
13421
Captain / Total hours on type:
3703.00
Copilot / Total flying hours:
1528
Copilot / Total hours on type:
1353
Aircraft flight hours:
35207
Aircraft flight cycles:
37360
Circumstances:
On 7 March 2007, a Boeing Company 737-497 aircraft, registered PK-GZC, was being operated by Garuda Indonesia on an instrument flight rules (IFR), scheduled passenger service, as flight number GA200 from Soekarno-Hatta Airport, Jakarta to Adisutjipto Airport, Yogyakarta. There were two pilots, five flight attendants, and 133 passengers on board. The pilot in command (PIC) and copilot commenced duty in Jakarta at about 21:30 Coordinated Universal Time (UTC), or 04:30 local time, for the flight to Yogyakarta. Prior to departing Jakarta, during the push back, the PIC contacted the ground engineers and informed them that the number-1 (left) engine thrust reverser fault light on the cockpit instruments had illuminated. The engineers reset the thrust reverser in the engine accessories unit and the fault light extinguished. The scheduled departure time was 23:00. The aircraft took off from Jakarta at 23:17, and the PIC was the pilot flying for the sector to Yogyakarta. The copilot was the monitoring/support pilot. During the cruise, just before top of descent, the crew was instructed by Jakarta Control to ‘maintain level 270 and contact Yogya Approach 123.4’. The copilot acknowledged; ‘contact Yogya 123.4, Indonesia 200’. The PIC started to give a crew briefing at 23:43 stating: ‘in case of holding, heading of 096’. The briefing was interrupted by a radio transmission from Yogya Approach, giving GA200 a clearance to Yogyakarta via airway W 17 for runway 09, and a requirement to report when leaving flight level 270. When radio communication was completed, the PIC continued with the crew briefing for an ILS approach, stating:
When clear approach ILS runway 09, course 088. (C) Frequency 1091, aerodrome elevation three hundred fifty, (C) leaving two thousand five hundred by 6 point 6 DME ILS, (C) to check four DME one thousand six hundred seventy, (C) crossing two DME one thousand thirty seven. Decision Altitude ILS Cat I, five eight seven, two three seven both set, approach flap forty, auto brake two. Speed one three six, one five one, two twenty. Timing from final approach-fix to VOR 6 DME. (C) With airspeed approximately one four one, two minutes thirty six. (C) In case localizer, MDA seven hundred, localizer, miss approach, at point six. (C) DME ILS India Juliet oscar golf. (C) On landing, to the left standby parking stand. Go-around missed approach climb one thousand five hundred turn left. To holding fix via Yogya VOR, continue climb four thousand feet, to cross Yogya at or above two thousand five hundred DME eight. (C).
Twelve minutes and 17 seconds later, Yogya Approach cleared GA200 ‘for visual approach runway zero nine, proceed to long final, report runway in sight’. The copilot acknowledged the clearance and asked for confirmation that they were cleared to descend to circuit altitude, Yogya Approach replied ‘descend to two thousand five hundred initially’. The crew informed the investigation that they were conducting an Instrument Landing System (ILS) approach to runway 09, in visual meteorological conditions (VMC). However they did not inform Yogya Approach or Yogyakarta Tower that they were flying the 09 ILS approach. At 23:58:10, the aircraft overran the departure end of runway 09 at Yogyakarta Airport. The PIC reported that as the aircraft was about to leave the runway, he shut down both engines. The aircraft crossed a road, and impacted an embankment before stopping in a rice paddy field 252 meters from the threshold of runway 27 (departure end of runway 09). The aircraft was destroyed by the impact forces and an intense, fuel-fed, post impact fire. There were 119 survivors. One flight attendant and 20 passengers were fatally injured. One flight attendant and 11 passengers were seriously injured.
Probable cause:
Causes:
1) Flight crew communication and coordination was less than effective after the aircraft passed 2,336 feet on descent after flap 1 was selected. Therefore the safety of the flight was compromised.
2) The PIC flew the aircraft at an excessively high airspeed and steep descent during the approach. The crew did not abort the approach when stabilized approach criteria were not met.
3) The pilot in command did not act on the 15 GPWS alerts and warnings, and the two calls from the copilot to go around.
4) The copilot did not follow company instructions and take control of the aircraft from the pilot in command when he saw that the pilot in command repeatedly ignored warnings to go around.
5) Garuda did not provide simulator training for its Boeing 737 flight crews covering vital actions and required responses to GPWS and EGPWS alerts and warnings such as ‘TOO LOW TERRAIN’ and ‘WHOOP, WHOOP PULL UP’.
Other Factors:
1) The airport did not meet the ICAO Standard with respect to runway end safety areas.
2) The airport did not meet the ICAO Standard with respect to rescue and fire fighting equipment and services for operation outside the airport perimeter and in swampy terrain.
Final Report: