Country
code

City District of Jakarta

Crash of a Boeing 737-4Y0 in Jakarta

Date & Time: Mar 20, 2021 at 1126 LT
Type of aircraft:
Operator:
Registration:
PK-YSF
Flight Type:
Survivors:
Yes
Schedule:
Jakarta - Makassar
MSN:
23869/1639
YOM:
1988
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Few minutes after takeoff from Jakarta-Halim Perdanakusuma Airport, the crew informed ATC about technical problems and was cleared to return. Shortly after touchdown on runway 24, the right main gear collapsed. The aircraft slid for few hundred metres then veered off runway to the right and came to rest in a grassy area. There were no injuries among the occupant and the aircraft is damaged beyond repair.

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 Learjet 31A in Jakarta

Date & Time: Sep 25, 2016 at 1946 LT
Type of aircraft:
Operator:
Registration:
PK-JKI
Flight Type:
Survivors:
Yes
Schedule:
Yogyakarta – Jakarta
MSN:
31-213
YOM:
2001
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing an ambulance flight from Yogyakarta-Adisujipto Airport to Jakarta-Halim Perdanakusuma Airport on behalf of the Indonesian Red Cross (Palang Merah Indonesia), carrying one patient, two doctors, two accompanists and three crew members. The approach was completed by night and marginal weather conditions. After touchdown on runway 24, the aircraft skidded on a wet runway. After a course of 1,300 metres, it veered to the right and departed the runway surface. While contacting soft ground, the right main gear was torn off while the left main gear partially collapsed. Then the aircraft bounced and impacted the ground several times, causing the left wing to be bent. Eventually, the right engine partially detached from the pylon. All eight occupants were rescued and the aircraft was damaged beyond repair. There was no fire.

Ground collision with an ATR42-600 in Jakarta

Date & Time: Apr 4, 2016 at 1957 LT
Type of aircraft:
Operator:
Registration:
PK-TNJ
Flight Phase:
Survivors:
Yes
MSN:
1015
YOM:
2014
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
2073
Aircraft flight cycles:
1038
Circumstances:
On 4 April 2016, Boeing 737-800 registration PK-LBS was being operated by Batik Air as scheduled passenger flight with flight number ID 7703 from Halim Perdanakusuma Airport with intended destination Sultan Hasanuddin International Airport, Makassar. An ATR 42-600 aircraft, registration PK-TNJ operated by TransNusa Aviation Mandiri was being repositioned from north to south apron of Halim Perdanakusuma Airport by a ground handling agent PT. Jasa Angkasa Semesta (PT. JAS). The aircraft was towed without aircraft electrical power fed to the system including the radio communication and aircraft lighting system. At the time of occurrence, the ID7703 pilot communicated to Halim Tower controller on frequency 118.6 MHz while the towing car driver communicated using handheld radio on frequency 152.73 KHz and was handled by assistant controller. At 1948 LT (1248 UTC), ID7703 pilot received taxi clearance from Halim Tower controller and after the ID7703 taxi, the towing car driver received clearance for towing and to report when on taxiway C. Afterward the towing car driver was instructed to expedite and to follow ID7703. While the ID7703 backtracking runway 24, the towed aircraft entered the runway intended to cross and to enter taxiway G. At 1256 UTC, ID7703 pilot received takeoff clearance and initiated the takeoff while the towed aircraft was still on the runway. The towing car driver and the pilots took action to avoid the collision. The decision of the pilot and the towing car driver to move away from the centerline runway had made the aircraft collision on the centerline runway (head to head) avoided, however the wings collision was unavoidable. At 1257 UTC, the ID7703 collided with the towed aircraft. The ID7703 pilot rejected the takeoff and stopped approximately 400 meters from the collision point while the towed aircraft stopped on the right of the centerline runway 24. No one injured at this occurrence and both aircraft severely damaged.
Probable cause:
The collision was the result of a poor coordination by ATC staff at Jakarta Airport. The following factors were reported:
- Handling of two movements in the same area with different controllers on separate frequencies without proper coordination resulted in the lack of awareness to the controllers, pilots and towing car driver,
- The communication misunderstanding of the instruction to follow ID 7703 most likely contributed the towed aircraft enter the runway,
- The lighting environments in the tower cab and turning pad area of runway 24 might have diminished the capability to the controllers and pilots to recognize the towed aircraft that was installed with insufficient lightings.
Final Report:

Crash of a Fokker F27 Friendship 400M in Jakarta: 11 killed

Date & Time: Jun 21, 2012 at 1450 LT
Type of aircraft:
Operator:
Registration:
A-2708
Flight Type:
Survivors:
No
Schedule:
Jakarta - Jakarta
MSN:
10546
YOM:
1976
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
The crew (one instructor and six pilot under training) were engaged in a training flight and departed Jakarta-Halim Perdanakusuma Airport at 1310LT for a local flight consisting of touch-and-go manoeuvres. After a circuit, the pilot-in-command completed a last turn to the left to join the glide for runway 18 when the aircraft stalled and crashed onto several houses located less than one km from the runway threshold. The aircraft was destroyed as well as several houses. Six occupants in the aircraft and four people on the ground were killed while the copilot was critically injured. Unfortunately, he did not survive to his severe injuries and died few hours later at hospital.
Probable cause:
It was reported that the approach speed was too low during the last turn, causing the aircraft to stall. The distance between the aircraft and the ground was insufficient to expect recovery.

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 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 F27 Friendship 600 in Jakarta: 3 killed

Date & Time: Sep 26, 1972
Type of aircraft:
Operator:
Registration:
PK-GFP
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Jakarta - Jakarta
MSN:
10462
YOM:
1971
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Aircraft flight hours:
2095
Aircraft flight cycles:
1478
Circumstances:
The crew was engaged in a local training flight from Jakarta-Kemayoran Airport. Shortly after takeoff from runway 35, while in initial climb, the airplane banked right and crashed 90 meters to the right of the runway. The aircraft was destroyed and all three pilots were killed.

Crash of a NAMC YS-11-102 in Jakarta

Date & Time: Apr 1, 1971
Type of aircraft:
Operator:
Registration:
PK-MYN
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Jakarta - Jakarta
MSN:
2011
YOM:
1965
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was engaged in a local training mission at Jakarta-Kemayoran Airport. After completing several touch-and-go manoeuvres with one engine voluntarily inoperative, the pilot-in-command made a new landing successfully. After rotation, during initial climb, the airplane stalled and crashed in a gear-up and flaps-down configuration onto the runway before coming to rest. All three crew members were injured and the aircraft was damaged beyond repair.

Ground accident of a Douglas C-47A-25-DK in Jakarta: 3 killed

Date & Time: Apr 5, 1962
Operator:
Registration:
PK-GDM
Survivors:
Yes
MSN:
13731
YOM:
1944
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Suffered a ground accident at Kemayoran Airport in Jakarta. The exact circumstances of the occurrence remains unknown and three people were killed.