Rabu, 30 September 2026

KNKT Reveals Chain of Failures Behind Deadly Train Collision in Bekasi

BEKASI, Indonesia — Indonesia's National Transportation Safety Committee (KNKT) has released its final investigation into the deadly collision between the Argo Bromo Anggrek intercity train and Commuter Line 5568A at Bekasi Timur Station, revealing a chain of problems involving railway signaling, emergency communication and braking procedures.

The collision occurred on April 27, 2026, at approximately 8:52 p.m. local time, killing 16 people and injuring 107 others. KNKT's investigation identified 60 findings and six contributing factors. Importantly, KNKT said these contributing factors were identified for transportation-safety purposes and were not intended to determine administrative, civil or criminal liability. 

The chain of events began minutes earlier

The disaster did not begin with the collision between the two trains.

At approximately 8:48:24 p.m., Commuter Line KA 5181B, traveling from Tambun toward Bekasi Timur, collided with a battery-powered electric taxi at JPL 86 on Jalan Ampera.

The accident created a crowd around the railway line and triggered a sequence of events that ultimately contributed to the much larger collision. 

At 8:48:55 p.m., another commuter train, KA 5568A, stopped on Track I at Bekasi Timur Station to allow passengers to board and leave the train.

Approximately 24 seconds later, at 8:49:19 p.m., KA 5568A moved about 1.69 meters toward Tambun before stopping again at 8:49:24 p.m.

According to the KNKT timeline, the driver stopped after seeing a crowd of people on the track ahead.

The problem was that information about why KA 5568A remained stopped was not successfully communicated to the relevant railway traffic controller. 

Meanwhile, the Argo Bromo Anggrek was approaching

At 8:50:43 p.m., KA 4B Argo Bromo Anggrek departed from Bekasi Station and proceeded directly through Track III.

The train was approaching Bekasi Timur while KA 5568A remained ahead on Track I.

Approximately two minutes later, at 8:52:12 p.m., the two trains collided on Track I at Bekasi Timur Station.

The impact severely damaged the front portion of the trains and caused dozens of casualties. KNKT recorded 123 victims in total: 16 fatalities and 107 people injured. 

What happened with the braking?

One of the most closely examined parts of the investigation was the braking of the Argo Bromo Anggrek.

According to KNKT's reconstruction, the train initially entered a service-braking phase at approximately 8:51:16 p.m., when it was still more than one kilometer from the collision point.

The driver maintained full-service braking as the train approached the stationary KRL.

The emergency brake was activated at approximately 8:51:56 p.m., when the train was about 275 meters from the collision point and traveling at approximately 78 km/h.

The train continued moving after the impact and eventually stopped about 26 meters beyond the collision point. 

KNKT noted that the emergency braking was performed after the driver recognized the rear section of KA 5568A.

Six contributing factors identified by KNKT

Rather than identifying a single cause, KNKT identified six contributing factors:

  • A hazard in the signaling relationship between Bekasi and Bekasi Timur stations was not identified.
  • Problems occurred in communication during the emergency situation.
  • Communication from KA 5568A failed to reach the necessary parties.
  • There was no effective mechanism for transferring information between the southern and eastern railway traffic controllers.
  • The auxiliary signal UB104 was not properly identified.
  • There was no emergency-braking procedure specifically addressing high-speed trains operating on curved track. 

The findings indicate that the disaster involved multiple layers of railway operations, rather than being explained by a single action at the moment of impact.

A signaling problem at the center of the investigation

One of the most significant issues involved the signaling relationship between Bekasi and Bekasi Timur.

The Argo Bromo Anggrek received permission to proceed from Bekasi, while the commuter train was still occupying the track ahead.

KNKT's investigation found that the hazardous condition created by the interaction of the signaling system was not properly identified. 

The investigation also found a discrepancy between the actual train movements and the scheduled railway timetable.

KA 5568A departed Bekasi 8 minutes and 32 seconds later than scheduled, while KA 4B departed 3 minutes and 17 seconds earlier than its scheduled departure time. 

Communication failures added another layer of risk

The earlier collision between KA 5181B and the electric taxi created an emergency situation at Bekasi Timur.

However, information that KA 5568A was being held because of the crowd on the track was not successfully passed to the southern railway traffic controller.

KNKT said the relevant controller was simultaneously dealing with the earlier collision.

There was also no mechanism for transferring information between the southern and eastern traffic-control personnel, leaving a critical gap in the flow of information. 

The driver's view was also examined

KNKT found that the windshield of the Argo Bromo Anggrek's locomotive had scratches that affected visibility.

Investigators said the condition of the glass affected the driver's ability to interpret the auxiliary signal. 

This became another element in the chain of circumstances examined by investigators.

The driver later became a suspect

Following the KNKT investigation, police separately named the Argo Bromo Anggrek driver as a suspect in the criminal investigation.

Police cited evidence including data from the train's data logger and argued that emergency braking occurred approximately 263 meters before the collision.

Police also consulted experts in railway operations, signaling, telecommunications, rolling stock, infrastructure and criminal law. 

However, this should not be confused with KNKT's safety investigation.

KNKT's six contributing factors are not a declaration that one individual was legally responsible. The committee explicitly stated that its findings were intended to identify conditions that could be eliminated or improved to reduce the possibility of another accident. 

A warning beyond one driver

The Bekasi Timur collision therefore raises a broader question for Indonesia's railway system: what happens when several safety barriers fail at the same time?

A previous train collision, a crowd on the track, incomplete emergency communication, signaling issues, difficulties identifying an auxiliary signal, visibility concerns and the absence of a specific emergency-braking procedure all formed part of the sequence reconstructed by investigators.

The lesson from the KNKT report is not simply about what happened in the final seconds before the trains collided.

It is about the chain of failures that allowed the two trains to reach that point in the first place.

And for the families of the 16 people who died, that chain of events represents more than an investigation. It is the search for an answer to one fundamental question:

Could the collision have been prevented if even one of those safety barriers had worked as intended?

Tidak ada komentar:

Posting Komentar