alurail alurail
Home & Hub Live Journey Map Timetables Route Search Special Trains (KLB) Train Directory Fleet Database Station Directory Facilities & Depots Operating Areas Safety & Incidents Updates & News Photo Gallery alurail pass
User Suite
Map Home Timetables Fleet
alurail alurail
Hub / Home Directory & Insights
Live Journey Map Crowdsourced Live Journey
Timetables Train Schedules
Search Routes Direct & Transit Finder
Extraordinary Trains (EOT) Extraordinary Trains
Train Directory Master Train Fleet
Fleet Database Rolling Stock Info
Stations Facilities & Hubs
Facilities Depots & Workshops
Operating Areas Daop & Divre
Incidents & Safety (EOE) Historical Rail Incidents
Updates & News Railway Dispatches & Insights
Photo Gallery Curated Collection
alurail pass Supporter Perks
About alurail Platform Info & Vision
Sign In / Account
Back to Updates • Safety & Regulations
Live Radar alurail Pass Submit Photo
Live Journey / Updates / KNKT Comprehensive Investigation: KA 4B Argo Bromo Anggrek vs KRL Collision at East Bekasi & Systemic Failure Analysis
Safety & Regulations 29 September 2026

KNKT Comprehensive Investigation: KA 4B Argo Bromo Anggrek vs KRL Collision at East Bekasi & Systemic Failure Analysis

Comprehensive safety analysis and official accident investigation report on the collision between KA 4B Argo Bromo Anggrek and KA 5568A Commuter Line at Bekasi Timur Station (Final Report KNKT.26.04.03.02): interlocking block 104 logic, telemetry, human factors, Swiss Cheese Model, and safety recommendations.
Alurail Research & Investigation Team
Staff Writer & Rail Researcher • 514 views
KNKT Comprehensive Investigation: KA 4B Argo Bromo Anggrek vs KRL Collision at East Bekasi & Systemic Failure Analysis
OFFICIAL SAFETY INVESTIGATION KNKT Final Report No. KNKT.26.04.03.02

An in-depth investigation by the Komite Nasional Keselamatan Transportasi (KNKT) into the catastrophic collision between KA 4B Argo Bromo Anggrek and KA 5568A Commuter Line at Stasiun Bekasi Timur reveals that the accident was not caused by an isolated operational error, but rather by an accumulation of systemic failures. The breakdown of fail-safe safety principles within the block section signalling interlocking logic, emergency communication transmission bottlenecks in the control room, optical degradation of the locomotive cab's polycarbonate windshield, and the absence of tactical emergency braking regulations along high-speed curved alignments compounded each other, eliminating any margin for collision mitigation.

Total Casualties
123 Victims
16 Fatalities • 107 Injured
Impact Speed
40 km/h
Initial Speed 108 km/h
Stopping Distance Deficit
-29 Meters
Required 845 m vs Available 816 m
Total Delay
26,703 Minutes
92 Intercity Trains Affected
⏱ Incident Chronological Timeline — 27 April 2026
20.33.59
KA 5568A arrives at Track VI Stasiun Bekasi for passenger service.
20.45.32
KA 5568A departs Stasiun Bekasi — delayed by 8 minutes 32 seconds.
20.48.24 ⚠
Triggering Incident: KA 5181B strikes electric taxi B 2864 SBX at level crossing JPL 86 Jl. Ampera (Km 29+400). LAA de-energized. Crowds of residents begin approaching the up line.
20.48.55
KA 5568A comes to a stop at Track I Stasiun Bekasi Timur — track circuit 104BT occupied.
20.49.19 – 20.49.24
KA 5568A advances +1.69 m then makes an emergency stop — driver spots a crowd of people on the up track.
20.49.37 – 20.50.28 🔔
Communication Breakdown: Driver of KA 5568A contacts PPKP Selatan twice via Sepura Radio — unanswered as PPKP had stepped away from the control console to manage KA 5181B.
20.50.43 🔴
Interlocking Flaw: KA 4B passes Track III Stasiun Bekasi — Exit Signal J12 displays a GREEN aspect despite 104BT being occupied. KA 4B accelerates to 108 km/h.
20.52.12 — COLLISION
Locomotive CC 206 13 86 (KA 4B) collides into the rear of KA 5568A at Km 28+915 at a residual speed of ~40 km/h. 123 casualties: 16 fatalities, 107 injured.
📊 Operational Disruption Impact — Cumulative Delay (Minutes)
0 5,000 10,000 15,000 11,798 14,350 182 373 KAJJ Down (52 Trains) KAJJ Up (40 Trains) KRL Down (4 Trains) KRL Up (5 Trains) Intercity Trains (KAJJ) Commuter Line (KRL) Source: KNKT No. KNKT.26.04.03.02
🇯🇩 Swiss Cheese Model — 6 Layers of KNKT Systemic Failures
Layer 1
Interlocking Logic Flaw
Signal J12 remained green despite 104BT being occupied — fail-safe violation
Layer 2
Emergency Communication Degradation
PPKP left control console; Tait Radio reverberation — 4 unanswered calls
Layer 3
Cab Visibility Limitations
Aged polycarbonate windscreen — 946 m curve radius truncated driver sightline
Layer 4
Stopping Distance Deficit
Required 845 m — available 816 m: -29 m deficit at 108 km/h
Layer 5
Absence of SOP for Emergency Braking on Curves
No formal tactical emergency braking procedure for high-speed track curvature geometry
Layer 6
Master Time Desynchronization
Time offset disparities across telemetry systems, audio recorders, and cab CCTV hindered reconstruction
🔌 Braking Telemetry of CC 206 13 86 — Deceleration Phases
Braking phase reconstruction based on locomotive On Board Computer (OBC) data from the KNKT report
Initial Speed (passing J12 green) 108 km/h
Speed when driver initiated service brake ~95 km/h
Speed when emergency brake was applied ~68 km/h
Speed at impact (20.52.12 WIB) ~40 km/h
⚠ KNKT Note: The driver delayed emergency brake application while traversing curve IP.MC22D (R=946 m) to prevent the risk of jackknifing (folding derailment) at high speed — a decision compliant with standard operating practice but one that lengthened the stopping distance.

Executive Summary and Factual Incident Data

The train collision that occurred on Monday, 27 April 2026 at 20.52.12 WIB on Track I (up line) of Stasiun Bekasi Timur, Km 28+915, within the Stasiun Bekasi–Stasiun Cikarang block section, Daerah Operasi 1 Jakarta (Daop 1 Jakarta), was a catastrophic railway accident involving an executive-class intercity train and an urban commuter train. The accident involved KA 4B Argo Bromo Anggrek on the Gambir–Surabaya Pasarturi route, hauled by diesel-electric locomotive series CC 206 13 86 with a consist of 11 executive passenger cars, and KA 5568A Commuter Line on the Kampung Bandan–Cikarang route, comprising a 10-car Electric Multiple Unit (KRL) consist.

The collision occurred while KA 5568A was making an unscheduled stop at the platform of Stasiun Bekasi Timur due to an obstruction caused by crowds of residents spilling onto the up line. The KA 4B trainset, running at high speed from the west, slammed into the rear of KA 5568A. The Komite Nasional Keselamatan Transportasi (KNKT) investigation report No. KNKT.26.04.03.02 confirmed that this tragedy was not triggered by a single operational error (single point of failure), but rather by an accumulation of systemic failures. These failures stemmed from design flaws in the route interlocking logic, the degradation of the emergency communication system in the centralized control center, driver optical visibility limitations caused by aged cab window materials, and the absence of tactical guidelines governing emergency braking on high-speed track curves. The accident resulted in casualties, structural damage to rolling stock and track infrastructure, and the paralysis of rail operations across the main trunk line of western Java.

Impact Parameter Quantitative Breakdown and Factual Damage Details
Casualties and Injuries 123 casualties, comprising 16 fatalities and 107 injured victims.
Rolling Stock Damage: KA 4B Locomotive CC 206 13 86 sustained severe deformation to the Leading Cab (Cab 1), fuel tank rupture on the lower underbody, compressed and bent Brake Cylinder (BC) piping on Bogie 1, catastrophic damage to the cowcatcher, severed driver cab exterior steps, and bent main deck frame caused by collision inertia.
Rolling Stock Damage: KA 5568A Passenger coach K1 181 73 suffered structural body destruction due to direct impact forces, while the rear driving trailer car K1 181 74 derailed completely with all 4 axles (wheelsets) off the rails.
Permanent Way Track Infrastructure Damage A total of 15 concrete sleepers were shattered and 10 E-Clip elastic rail fasteners were fractured or dislodged at the Km 28+915 point of impact.
Operational Disruption: Intercity Trains (KAJJ) Cancellation of 36 train trips, route curtailment on 3 trains, down-line delays affecting 52 trains totaling 11,798 minutes, and up-line delays affecting 40 trains totaling 14,350 minutes.
Operational Disruption: Commuter Line (KRL) Cancellation of 8 commuter train trips, route curtailment on 20 trains, down-line delays affecting 4 commuter trains (182 minutes), and up-line delays affecting 5 commuter trains (373 minutes).

Sequence of Events

The accident at Stasiun Bekasi Timur was triggered by an antecedent incident that initiated a cascading chain reaction (domino effect) across the shared corridor. Time synchronization throughout the investigation was established by KNKT by utilizing the verified network time (Network Time Protocol / NTP UTC+7) from the electric taxi's On Board Unit (OBU) recorder and the CCTV cameras of KA 5568A as the master time reference to reconcile time offsets across all telemetry instruments and voice recorders.

The initial chain of events began at 20.48.24 WIB, when KA 5181B Commuter Line on the Cikarang–Angke route, running on the down line, struck a battery electric passenger vehicle (taxi) with license plate B 2864 SBX at level crossing JPL 86 Jl. Ampera (Km 29+400). The taxi was dragged and wedged underneath the leading cab of KA 5181B, causing the train to come to a halt and tripping the overhead catenary power supply (LAA). The violent impact at JPL 86 drew nearby residents out in droves toward the scene, gradually spilling over and occupying the adjacent up track directly alongside it.

At 20.48.55 WIB, KA 5568A arrived at Track I of Stasiun Bekasi Timur for scheduled passenger boarding and alighting. Upon completing platform duties, KA 5568A departed at 20.49.19 WIB. However, after advancing approximately 1.69 meters, the driver spotted crowds of people swarming the up line toward Tambun following the collision at JPL 86, prompting the driver to immediately execute a stop at 20.49.24 WIB to prevent striking pedestrians. With KA 5568A halted at the platform, track circuit section 104BT remained occupied.

Meanwhile, KA 4B, running under operational schedule adjustments, passed through Track III of Stasiun Bekasi without stopping at 20.50.43 WIB, encountering Exit Signal J12 displaying a green aspect. The driver of KA 4B accelerated toward the track speed limit of 114 km/h under the expectation that the block section ahead was clear and unobstructed. The driver of KA 4B only sighted a signal displaying red ahead after negotiating the track curvature and promptly initiated stepped service braking leading into emergency braking. However, the deficit in available stopping distance rendered the collision unavoidable at 20.52.12 WIB.

Corrected Master Time (WIB) Physical Event Sequence and Rolling Stock Movement Radio Communication Transcription and Control System Indications
20.33.59 KA 5568A arrives and comes to a complete stop on Track VI of Stasiun Bekasi. Train arrival verified per station signalling monitoring.
20.34.45 – 20.38.32 KA 116B Sawunggalih arrives on Track III of Stasiun Bekasi, boards passengers, and departs ahead of KA 5568A. Train dispatching adjusted by the Stasiun Bekasi Train Dispatcher (PPKA Bekasi).
20.45.32 KA 5568A is dispatched from Track VI of Stasiun Bekasi bound for Stasiun Bekasi Timur. KA 5568A departs with an 8-minute 32-second delay against the working timetable (Gapeka).
20.48.24 Antecedent Incident: KA 5181B strikes an electric taxi at level crossing JPL 86 Jl. Ampera on the down line. Recorded on electric taxi OBU; vehicle pinned under the front cab of KA 5181B.
20.48.44 – 20.48.58 Driver of KA 5181B initiates radio contact with Centralized Train Controller South (PPKP Selatan). Driver transmits via Tait Radio Rig Section 27 via individual call (PTT); audio is muffled and exhibits severe reverberation.
20.48.55 KA 5568A comes to a complete halt on Track I of Stasiun Bekasi Timur for passenger service. The KRL consist occupies track circuit section 104BT.
20.49.19 – 20.49.24 KA 5568A moves forward ±1.69 meters, then stops once again. Driver of KA 5568A spots a crowd of residents on the up line and brings the train to a stop.
20.49.37 – 20.50.28 Driver of KA 5568A calls PPKP Selatan twice via Sepura Radio Section 27. Calls go unanswered as PPKP Selatan is occupied managing KA 5181B and has stepped away from the console.
20.50.23 – 20.50.27 PPKP Selatan instructs KA 6075B following behind KA 5181B to hold at Stasiun Tambun. PPKP Selatan stands up and walks toward the Train Operations Controller (OPKA) desk.
20.50.43 KA 4B runs through Track III of Stasiun Bekasi without stopping. KA 4B departs 3 minutes 17 seconds ahead of Gapeka timetable provisions.
20.50.59 – 20.51.25 PPKP Timur contacts KA 4B via Locomotive Radio Section 11. PPKP Timur instructs: "frequently sound Semboyan 35 (horn)" and "brake a little bit" due to an obstruction on the down line.
20.51.18 Driver of KA 4B moves automatic brake handle to minimum reduction service brake. KA 4B speed recorded at 108 km/h at Km 27+600; locomotive independent brake is bailed off.
20.51.33 Assistant Driver of KA 4B sights Signal B104 displaying a red aspect and reports to PPKP Timur. KA 4B position at Km 28+049 (having passed Co-acting Signal UB104 at Km 28+030).
20.51.34 Driver of KA 4B moves automatic brake handle to full service brake position. Brake Pipe pressure drops progressively toward 49 psi.
20.51.56 Driver of KA 4B applies emergency brake at Km 28+588 (275 meters prior to collision). Brake handle moved to emergency upon visually sighting the KRL consist; speed at that instant was 78 km/h.
20.52.12 Collision: KA 4B impacts the rear of KA 5568A at 40 km/h at Km 28+915. Locomotive accelerometer records out-of-range status (---); train consist comes to a complete rest at Km 28+941.

Technical Evaluation of Signalling Systems on the Stasiun Bekasi–Stasiun Bekasi Timur Block Section

The technical investigation of the signalling system revealed fundamental flaws in the design of the route interlocking logic following modern railway facility upgrades. Stasiun Bekasi Timur holds the status of an intermediate block station governed by an Automatic Blocking System (ABS). Track I of Stasiun Bekasi Timur is situated between Block Signal B104 (Km 28+440) and Block Signal B103 (Km 29+195). To accommodate advance train arrival warnings for the semi-automatic level crossing JPL 85 at Jl. Moh. Yamin (Km 28+725), this block section is split into two track circuits: section 104AT and section 104BT. The entire passenger platform span of Stasiun Bekasi Timur lies within track circuit section 104BT.

The evolution of the signalling design demonstrates a progressive degradation of fail-safe safety principles. Under the 2014 Design Document (Signal Aspect Drawing Step-1 Railway Electrification and Double-Double Tracking Package B1), the signalling configuration was governed by a signal-to-track dependency philosophy. In that initial design, the provision of Block Signal B105 between the Bekasi Exit Signal and Block Signal B104 guaranteed that if either section 104AT or section 104BT were occupied by rolling stock, Exit Signal J32 would display green, Block Signal B105 would display yellow, and Block Signal B104 would display red. Through this sequence, the three-aspect signalling principle was maintained in proper progression.

However, the implementation of Switch Over Phase II at Stasiun Bekasi on 20 November 2021 decommissioned Block Signal B105 and Co-acting Signal UB105 to accommodate station yard expansion, leaving the up line section with only Co-acting Signal UB104 (Km 28+030) and Block Signal B104 (Km 28+440) following the station exit signal. The 2022 Design Review Document (Signal Aspect Plan DL-23) reformulated the new signalling sequence under a signal-to-signal paradigm without mapping the granular impact of track circuit occupancy states. Consequently, the route locking logic for J12–14T at Stasiun Bekasi only verified the occupancy state of track circuit section 104AT while completely disregarding the occupancy state of section 104BT.

Block Section 104 Track Occupancy Scenario Bekasi Exit Signal J12 Aspect Status Co-acting Signal UB104 Aspect Status Bekasi Timur Block Signal B104 Aspect Status Three-Aspect Safety Principle Evaluation
Condition 1: Section 104AT Occupied, Section 104BT Clear Yellow Aspect (Caution / Proceed with Caution) Horizontal White Light (Red Signal Indication) Red Aspect (Semboyan 7 / Stop) Standard Compliant: A yellow aspect precedes the red aspect, providing the driver with advance warning.
Condition 2: Section 104AT Occupied, Section 104BT Occupied Yellow Aspect (Caution / Proceed with Caution) Horizontal White Light (Red Signal Indication) Red Aspect (Semboyan 7 / Stop) Standard Compliant: Warning aspect progression forms normally.
Condition 3 (Factual Accident Scenario): Section 104AT Clear, Section 104BT Occupied Green Aspect (Semboyan 5 / Clear / Proceed) Horizontal White Light (Red Signal Indication) Red Aspect (Semboyan 7 / Stop) Systemic Flaw (Fatal Hazard): Direct aspect skip occurs from Green to Red without prior Yellow cautionary warning.

Signalling simulation tests conducted by KNKT on 28–29 April 2026 empirically demonstrated that whenever section 104BT was occupied by rolling stock (as when KA 5568A was held at the platform), route setting from Track III of Stasiun Bekasi resulted in Exit Signal J12 continuing to show a green aspect. At the same time, the interlocking control display (Visual Display Unit / VDU) at the Stasiun Bekasi PPKA control desk was not equipped with monitoring indicators for block signal or co-acting signal aspects on open track sections, leaving the PPKA operator without any means of visual confirmation for such anomalies. Further sample testing conducted on 12–13 May 2026 at Stasiun Manggarai uncovered an identical logic defect on the Manggarai–Sudirman route (Signals JL22A, JL42A, and JL152A remained green while section 206BT was occupied and signal B206 was red), indicating systemic methodological deficiencies in factory and site acceptance testing for electronic interlocking systems across the national railway network.

Train KA 4B Locomotive Data Logger Analysis and Braking Dynamics

Locomotive CC 206 13 86 is equipped with an integrated GE-C20EMP Electronic Brake Valve (EBV) braking system, comprising an Automatic Brake Handle (controlling brake pipe air pressure throughout the trainset) and an Independent Brake Handle (controlling the locomotive brake cylinder braking independently). Telemetry analysis from the locomotive data logger reconstructed the braking control responses executed by the driver:

Locomotive Telemetry Parameter Minimum Service Braking Phase (Min. Reduction) Full Service Braking Phase (Full Service) Emergency Braking Phase (Emergency Brake)
Actual Time Range 20.51.18 – 20.51.27 WIB 20.51.34 – 20.51.55 WIB 20.51.56 – 20.52.12 WIB
Rolling Stock Kilometrage Position Km 27+600 (1,315 m from point of collision) Km 28+078 to Km 28+619 Km 28+588 to Km 28+915 (point of impact)
Train Speed (v) 108 km/h → 105 km/h 105 km/h → 79 km/h 78 km/h → 40 km/h at collision
Brake Pipe Pressure 71 psi decreasing to 65 psi 62 psi decreasing steadily to 49 psi 43 psi rapidly dropping to 0 psi
Brake Cylinder Pressure 0 psi (locomotive bailed off) Briefly rose to 8 psi, then bailed off to 0 psi Surged rapidly reaching saturation limit of 70 psi
Throttle Status & Traction Motor Current Throttle position T7, current load 168 A Throttle T6 reduced to T4, current decreased to 144 A Pneumatic Control Switch (PCS) "Open", current 0 A
Independent Brake Handle Status Released position Released position Moved to applied position at Km 28+752

The driver's action of exhausting the locomotive brake cylinder pressure (bail-off) down to 0 psi during full service braking was a train-handling technique intended to attenuate the differential deceleration rate between the locomotive and the passenger coaches behind it. The driver sought to minimize inter-car compressive coupler buff forces that could trigger severe in-train jerks.

When the driver of train KA 4B detected the red aspect on Block Signal B104 at an effective sighting distance of ±410 meters, the train was traversing horizontal curved track number IP.MC22D (curve radius R = 946 meters, situated between Km 27+398 and Km 27+685). The driver consciously chose not to initiate an immediate emergency brake application. Under the driver's technical understanding acquired through years of operating service, applying emergency braking at speeds exceeding 100 km/h while the train is negotiating curved geometry poses severe risks of train jackknifing derailment or vehicle overturn resulting from the unmanaged discharge of longitudinal inertial forces pushing against the outer rail.

The driver decided to apply full service braking first and delay emergency brake application until the locomotive had cleared the curved track approaching grade crossing JPL 85. However, the investigation revealed that the driver had never received formal simulator-based training regarding emergency braking scenarios on curved track. Service Regulation (Peraturan Dinas) Number 16A of 2023 Article 40 contains only qualitative mandates devoid of operational technical criteria, leaving emergency braking decisions entirely reliant upon the driver's subjective judgment amidst a critical emergency.

Kinematic Equation Derivation of Deceleration and Stopping Distance

Locomotive deceleration evaluation based on data logger records is derived through the kinematic equations of uniformly accelerated rectilinear motion:

1) Full Service Phase (Δt = 21 s, v0 = 105 km/h = 29.2 m/s, vt = 79 km/h = 21.94 m/s, sfs = 541 m):
afs = (vt - v0) / Δt = (21.94 - 29.2) / 21 = -0.35 m/s²

2) Emergency Brake Phase (Δt = 16 s, v0 = 78 km/h = 21.7 m/s, vt = 40 km/h = 11.11 m/s, seb = 275 m):
aeb = (vt - v0) / Δt = (11.11 - 21.7) / 16 = -0.66 m/s²

3) Combined Average Deceleration:
aavg = (afs + aeb) / 2 = (-0.35 - 0.66) / 2 = -0.505 m/s²

4) Theoretical Stopping Distance Requirement from v0 = 105 km/h (29.2 m/s):
s = (v0²) / (2 × |aavg|) = (29.2)² / (2 × 0.505) = 844.19 m ≈ 845 meters

Because the physical distance available from the full service braking initiation point (Km 28+078) to the point of collision (Km 28+915) was only 816 meters, a stopping distance deficit of approximately 29 meters caused the impact to occur at a residual speed of 40 km/h.

Referencing ISO 2631 standards on railway passenger comfort (av ≤ 0.315 m/s²), the comfortable stopping distance at a cruising speed of 108 km/h is 1,429 meters, and at the authorized track speed of 115 km/h is 1,620 meters. Because the actual distance between Exit Signal J12 at Bekasi Station and Block Signal B104 at Bekasi Timur Station spans 1,781 meters, had the signaling system functioned correctly by displaying a yellow aspect on Exit Signal J12, the 1,781-meter spatial margin would have provided more than ample safety margin for the driver to achieve a complete stop before Block Signal B104.

Driver Cab Visibility Factors and Sensory Ergonomics

Limitations in the driver's visual detection of track conditions were influenced by an interplay between rolling stock physical materials and ambient light pollution. Based on PT KAI Rolling Stock Management Director Official Note Number 001/KR.203/R/XII/2015, the entire CC 206 locomotive fleet utilizes cab windshields made of specialized thickness polycarbonate to protect drivers from trackside projectile throwing hazards. However, polycarbonate material possesses significantly lower surface abrasion resistance compared to conventional laminated safety glass.

Physical examination of the locomotive hauling train KA 4B revealed deep wiper sweep scratches and swirl marks on the cab windshield exterior surface. At night, these micro-scratches refract external light into extensive diffuse glare (light scattering). A comparative observation conducted by the KNKT on 16 May 2026 demonstrated that visibility from the cab of a Series TM6000 EMU equipped with laminated safety glass yielded sharp, dispersion-free signal light contrast. Conversely, from the CC 206 locomotive cab, trackside light sources distorted into diffuse glare that obscured the driver's visual edge acuity.

Driver Cab Observation Position Spatial Distance to Signal Nighttime Field Optical Visibility Analysis
Km 27+750 280 m from UB104 (690 m from B104) The horizontal white LED beam of Repeater Signal UB104 was completely masked by ambient light pollution from streetlights and residential housing lining the right-hand side of the track. Block Signal B104 was obstructed by track curvature and overhead catenary system (LAA) mast alignments.
Km 27+900 130 m from UB104 (540 m from B104) The signal beam of UB104 remained blended into surrounding residential illumination. Inside the CC 206 cab, a fused glare effect occurred, while Block Signal B104 became faintly visible behind the left-hand LAA masts.
Km 28+000 30 m from UB104 (440 m from B104) The mast structure and aspect of Repeater Signal UB104 could only now be unequivocally discerned by the driver's eyes. Block Signal B104 became distinctly visible displaying a red aspect.

Repeater Signal UB104 was installed at Km 28+030 utilizing a configuration of five white LED lamps to repeat the aspect of Block Signal B104 at Km 28+440, which was obscured by track curve geometry IP.MC22D, given that the direct line-of-sight sighting distance of Signal B104 was only 410 meters (failing to meet the minimum 600-meter sighting distance mandated by Minister of Transportation Regulation Number 44 of 2018). However, Repeater Signal UB104 was not equipped with a black background shield. At night, the white LED luminous emissions from this signal exhibited intensity and wavelength characteristics virtually identical to street and house lighting in the densely populated settlement along the right side of the up track (jalur hulu).

This degraded optical environment interacted with the train crew's cognitive workload and confirmation bias. Because the driver of train KA 4B had passed Exit Signal J12 at Bekasi Station displaying a green aspect, the driver's mental model was established upon the certainty that the block section ahead was clear and the subsequent signal would display at least a caution (yellow) aspect. With no scheduled intermediate stops until Cirebon Station, the driver's visual focus was directed toward high-speed cruising and did not anticipate a hazard indication from Repeater Signal UB104, which was masked amidst light pollution. The driver only realized the presence of a track obstruction hazard when the illuminated red aspect of Block Signal B104 came into direct line of sight immediately upon exiting the curve.

Operational Communication Constraints and Control Center Ergonomics

Emergency response coordination at the Daop 1 Jakarta Train Operation Control Center (Pusdal Manggarai) experienced severe bottlenecks resulting from telecommunication facility fragmentation and excessive operator workload. Operational control over physical train movements across the Eastern Region (Manggarai–Cikarang–Cikampek corridor) fell under the jurisdiction of the Eastern Train Dispatcher (PPKP Timur) desk. However, digital communication radio consoles serving KRL Commuter Line drivers (Tait Section 27 and Sepura Section 27 consoles) were physically positioned at the Southern Train Dispatcher (PPKP Selatan) desk. The PPKP Timur desk was equipped solely with a conventional analog radio console to communicate with long-distance passenger train locomotives (Section 1). This physical separation severed direct information flow between PPKP Timur and the commuter fleet operating within its territorial control.

The handling of the accident at grade crossing JPL 86 revealed a cascade of communication failures that critically delayed emergency response:

  • Following the collision between train KA 5181B and an electric taxi at JPL 86, the driver of KA 5181B attempted to unclip the Tait radio microphone from its mounting bracket. This attempt failed because the microphone clip jammed, forcing the driver to transmit while hunched over in a standing posture with a mouth-to-microphone distance exceeding 5 centimeters. This exceeded the manufacturer's technical guidelines (Tait Operational Instruction TM9000), which stipulate a maximum speaking distance of ≤ 5 cm. Consequently, the transmitted audio signal suffered from poor modulation, sounding faint, reverberant, and distorted (warbling), severely impeding PPKP Selatan's ability to comprehend the message.
  • The report from the driver of KA 5181B lacked standardized structure and failed to adhere to standard railway safety phraseology. The driver repeatedly uttered colloquial phrases: "hit a car, Sir" ("nemper mobil Pak"), "the car is trapped, Sir" ("mobilnya nyangkut Pak"), without promptly specifying the train number identity, kilometrage position, or structure gauge clearance status on the adjacent up track. This ambiguity forced PPKP Selatan to conduct protracted verification inquiries consuming 3 minutes and 20 seconds (20:48:44 to 20:52:04 WIB) merely to ascertain the train's location and track fouling status.
  • PPKP Timur, overhearing fragmented reports from the adjacent PPKP Selatan desk, immediately contacted KA 4B via analog radio. However, the instruction given to the driver relied on ambiguous, informal terminology: "Bang, be careful around East Bekasi JPL... try braking a bit, tap the brakes lightly, bang..." ("Bang hati-hati di JPL Bekasi Timur... coba direm-rem dulu direm-rem dikit ya bang..."). The phrase "brake a bit lightly" possesses no operational definition in railway regulations and completely failed to convey the acute severity of a track obstruction, leading the driver of KA 4B to respond with only a moderate minimum service brake application.
  • The driver of KA 5568A, held at the platform of Bekasi Timur Station by civilian crowds surging onto the track, attempted to contact PPKP Selatan twice, at 20:49:37 and 20:50:28 WIB via the Sepura Section 27 console. Both calls went unanswered because PPKP Selatan had physically stepped away from the workstation to the operations manager (OPKA) desk to deliver a manual verbal report of the KA 5181B accident in accordance with SOP Board of Directors Regulation Number PER.U/KT.204/VI/1/KA-2024. Because the driver of KA 5568A initiated routine individual calls rather than pressing the Emergency Call Button, the incoming calls failed to trigger an emergency barge-in override alarm on the dispatcher console.
  • The Daop 1 Jakarta Operation Control Center utilized open external speakers to broadcast incoming radio calls without providing individual headsets for dispatchers. Simultaneous audio transmissions from multiple active radio sections created severe acoustic clutter (noise pollution) and perceptual confusion among dispatching staff. This environment was further compounded by the graphic display on the PPKP Timur monitor, which failed to arrange the corridor track diagram in geographic continuity and omitted the station name label "Bekasi Timur Station," displaying only an unbroken chain of track circuit alphanumeric codes that impeded rapid identification of train positions.

Schedule Deviations from Gapeka and Latent Hazards of Mixed-Traffic Operations

The KNKT investigation identified substantial operational timetable deviations from the Master Train Working Diagram (Gapeka) on the night of the occurrence. Train KA 5568A departed Bekasi Station running 8 minutes and 32 seconds behind schedule after being held for an overtaking maneuver by train KA 116B Sawunggalih. The delay of KA 116B had itself been initiated by route-setting queues behind train KA 49 in the Jatinegara Station interlocking area. Conversely, train KA 4B passed Bekasi Station non-stop 3 minutes and 17 seconds ahead of its Gapeka schedule. This advance was facilitated by an operational speed increase for KA 4B from 109 km/h to 114 km/h pursuant to an extra-Gapeka operating authorization issued via Directorate General of Railways (DJKA) Letter Number KA.407/1/5/DJKA/2025.

KNKT simulation calculations demonstrated that in the absence of a line blockage at the Bekasi Timur station yard, the net schedule deviations between the two trains would theoretically have still maintained a safe headway margin of 2 minutes and 48 seconds. Under an unhindered normal operating scenario, KA 5568A would have advanced into the subsequent block section and KA 4B would merely have encountered a stop aspect at Home Signal J10 of Tambun Station. However, the compound schedule deviations severely eroded the temporal and spatial safety buffers between the trains. When KA 5568A was brought to a standstill at the platform due to external factors, the protective separation distance between the two trains evaporated rapidly.

This catastrophe underscored the latent hazards inherent in mixed-traffic operations on shared tracks along the Bekasi–Cikarang corridor. This double-track trunk line is shared concurrently by high-speed intercity trains (114–120 km/h) characterized by extended braking distances, and high-density urban commuter trains operating under stop-and-go profiles. Operating two diametrically opposed rolling stock operating profiles on common track infrastructure without the protective safety net of cab-signaling Automatic Train Protection (ATP) introduces extreme systemic vulnerability to human error and single-point signaling failures.

Causal Analysis and Six Primary Contributing Factors (Swiss Cheese Model)

The catastrophic collision at Bekasi Timur Station was a manifestation of the Swiss Cheese Model of cumulative failure, in which multiple layers of safety defenses collapsed simultaneously. Trackside signalling system deficiencies, human-machine interface weaknesses, the failure to transmit safety-critical information, and procedural limitations interconnected and compounded, eliminating any remaining opportunity to mitigate or prevent the collision.

Structure of Primary Contributing Factors to the Bekasi Timur Station Collision (KNKT)
Factor 1: Unidentified Hazard Condition in Block 104 Interlocking Logic

Bekasi Station Starter Signal J12 was designed to respond exclusively to the occupancy status of track circuit section 104AT, ignoring the status of section 104BT. When KA 5568A occupied section 104BT along the Bekasi Timur platform, the signalling system continued to display a clear (green) aspect on Signal J12, while Block Signal B104 ahead displayed a stop (red) aspect. This sequence violated the safety principles of three-aspect signalling by eliminating the cautionary (yellow) aspect required to advise proceed with caution.

Factor 2: Emergency Communication Failures Following the JPL 86 Accident

The driver of KA 5181B contacted the South PPKP (Train Dispatcher) using a standard individual call rather than initiating a priority Emergency Call. A mechanical failure in the radio handset cradle inside the KRL cab forced the driver to speak from an unergonomic distance, resulting in faint and distorted audio quality. The absence of standardized emergency safety phraseology prolonged the verbal clarification process to 3 minutes and 20 seconds.

Factor 3: Failure to Transmit Operational Reports of KA 5568A Being Held

Critical information that KA 5568A was detained on Track I at Bekasi Timur Station due to a civilian crowd on the tracks failed to reach train dispatchers. The driver of KA 5568A placed only routine calls over the Sepura radio system, while the South PPKP dispatcher had stepped away from the console to brief the shift supervisor.

Factor 4: Absence of Formal Inter-Desk Communication Mechanisms Between South & East PPKP

Train movement control along the Bekasi–Cikarang corridor was overseen by the East PPKP, whereas radio communication with the KRL commuter fleet was handled separately by the South PPKP. Lacking standard operating procedures for cross-desk coordination, the East PPKP received no factual intelligence regarding the situation at Bekasi Timur Station; consequently, guidance relayed to the driver of KA 4B remained speculative and failed to issue an immediate emergency stop order.

Factor 5: Driver's Failure to Identify Repeater Signal UB104 Aspect

The mental model established by the crew of KA 4B—presuming an unobstructed track after passing Bekasi Starter Signal J12 at clear (green)—induced cognitive expectancy bias. This was exacerbated by diminished nocturnal visibility of Repeater Signal UB104 against background urban light pollution, along with severe optical glare and light scattering caused by wiper abrasions across the locomotive cab's polycarbonate windshield.

Factor 6: Absence of Procedures & Training for Emergency Braking on Curved Track

The driver of KA 4B chose to delay applying the emergency brake upon sighting the red aspect of Block Signal B104, fearing derailment or rollover caused by jackknifing forces within the IP.MC22D curve. Sinking into subjective judgment without objective technical guidance, the driver favored a full service brake before transitioning to emergency braking only after clearing the curve, resulting in a stopping distance deficit that directly precipitated the physical collision.

Comprehensive Synthesis of KNKT Investigation Findings

The exhaustive KNKT investigation formulated 12 comprehensive findings mapping the systemic interrelationships across railway operations during this accident:

  1. Railway operations on the Bekasi Station–Cikarang Station section operated under a shared-track regime blending higher-speed intercity passenger trains with suburban commuter trains without adequate physical infrastructure separation.
  2. Significant schedule deviations relative to GAPEKA timetable specifications occurred: KA 5568A departed 8 minutes 32 seconds late due to intercity train overtakes at Bekasi Station, whereas KA 4B passed through 3 minutes 17 seconds ahead of schedule under permissible track speed adjustments.
  3. An inconsistency in master reference time existed across digital recording instruments throughout the operating environment, including clock discrepancies between the signalling system, dispatch voice recorders, rolling stock CCTV logs, and locomotive telemetry units.
  4. A breakdown of fail-safe functionality occurred in the electrical signalling system, wherein the subdivision of track circuit sections 104AT and 104BT within Block 104 was improperly integrated into the Bekasi Station interlocking logic table. The occupied state of section 104BT failed to enforce a caution (yellow) aspect on Starter Signal J12 when setting the route, creating a hazardous sequence where a clear (green) signal was directly succeeded by a stop (red) signal.
  5. The signalling control console (VDU) in the Bekasi Station PPKA office provided no visual display of signal aspect statuses for automatic block signals and repeater signals in the open line section, depriving local train dispatchers of aspect verification capabilities.
  6. Telecommunications facilities at the Daop 1 Jakarta Operation Control Center were operationally fragmented: East PPKP, controlling the physical line, lacked digital KRL communication radios, while KRL traffic was monitored separately by South PPKP without formal inter-desk emergency information-sharing protocols.
  7. The failure by train crews encountering a track obstruction to initiate a dedicated Emergency Call, combined with the lack of safety-critical communication phraseology protocols and mechanical handset cradle defects in the KRL cab, prolonged reporting of the JPL 86 level crossing collision to 3 minutes and 20 seconds.
  8. The control center operating environment suffered from excessive ambient noise due to open loudspeakers without personal headsets, alongside an East PPKP graphical display interface that failed to explicitly label Bekasi Timur Station.
  9. The locomotive cab's polycarbonate windshield suffered degraded optical clarity caused by micro-swirls and wiper blade abrasions, inducing severe nighttime optical glare and scattering that impaired visual contrast when reading wayside signal aspects.
  10. The white LED array of Repeater Signal UB104 was visually masked by background illumination from surrounding residential settlements due to the absence of a high-contrast black background shield.
  11. The driver of KA 4B performed staged brake applications progressing from minimum reduction to full service and finally emergency braking. The application of the locomotive independent brake release (bail-off) technique and the hesitation to apply emergency brakes within the curved alignment stemmed from a complete absence of standard operating procedures and specialized training for high-speed curve emergency handling.
  12. Automatic train protection along the operational line remained non-functional due to the absence of an integrated Automatic Train Protection (ATP) / SKKO system, as mandated by Minister of Transportation Regulation Number 52 of 2014.

Safety Actions Implemented and Comprehensive Safety Recommendations

In response to interim investigative findings during the inquiry, railway industry stakeholders implemented a series of immediate safety actions:

  • Directorate General of Railways (DJKA): Issued an instruction letter mandating a comprehensive review of maximum operating speed limits along mixed-traffic corridors (Gambir–Manggarai and Bekasi–Cikarang), instituted periodic infrastructure certification audits, established a Joint ATP/SKKO Technology Development Taskforce via Director General Decree No. KP-DJKA 93 of 2026, and installed a high-contrast black background shield on Repeater Signal UB104 through the Jakarta Class 1 Railway Engineering Center.
  • PT Kereta Api Indonesia (Persero): Issued Emergency Operating Instruction O/426 dated 29 April 2026 mandating that all non-stopping through trains make an unscheduled stop (Berhenti Luar Biasa / BLB) at Bekasi Station and strictly prohibiting departure until block section 104BT is positively confirmed clear. Imposed temporary speed restrictions capped at 60 km/h between Km 27+730 and Km 28+030 and 80 km/h across the Bekasi–Cikarang section, conducted a comprehensive Kyosan signalling evaluation, synchronized all operational recording device clocks to the BMKG NTP server, closed 172 unauthorized level crossings via Official Memorandum No. 7/KS.103/V/KA/2026, and promulgated Operating Communication SOP No. SOP.OMP/KL.104/VIII/1/KA-2026 along with Work Instruction IK-01/Pusdal1/VIII/2026.

To realize an exhaustive national railway safety transformation and prevent the recurrence of similar catastrophes, the KNKT issued definitive safety recommendations:

To the Directorate General of Railways (DJKA):
  • Audit and rectify the design of the signalling interlocking logic between Bekasi Station and Bekasi Timur Station to ensure starter signals reflect the occupancy status of all subsequent track circuit sections in a fail-safe manner.
  • Review the national signalling aspect progression sequence standard, harmonizing progressive warning aspects with actual stopping distances, line running speeds, and diverse rolling stock braking characteristics.
  • Evaluate all repeater signal placements in urban corridors to ensure optical readability through the installation of contrast shields against ambient light pollution.
  • Promulgate safety regulations mandating standardized phraseology and structured safety-critical emergency communication protocols for all infrastructure managers and train operating companies.
  • Secure an allocated, dedicated, and protected wireless radio frequency spectrum for national railway operations.
  • Tighten safety oversight concerning control room interface design, ergonomics, and cognitive workload thresholds for train dispatch personnel.
  • Accelerate the implementation of integrated trackside and onboard Automatic Train Protection (ATP) / SKKO systems as mandated by Minister of Transportation Regulation Number 52 of 2014.
  • Mandate independent verification and validation testing by an Independent Safety Assessor (ISA) compliant with the Reliability, Availability, Maintainability, and Safety (RAMS) lifecycle for all future signalling modifications and new installations.
To PT Kereta Api Indonesia (Persero):
  • Evaluate the mechanical placement and operational ergonomics of cab radio communication equipment to satisfy manufacturer ergonomic and usability standards.
  • Conduct recurring simulation training for train crews and PPKP dispatchers on emergency safety-critical communication procedures and the mandatory initiation of priority emergency call functions.
  • Establish optical clarity thresholds and maintenance standards for locomotive cab windscreens, including buffing cycles, periodic polycarbonate replacement schedules, and evaluating high-performance laminated safety glass.
  • Develop rigorous standard operating procedures and simulator curricula for high-speed emergency braking along curved track alignments, taking into account vehicle dynamic stability calculations.
  • Restructure the ergonomic layout of the Daop 1 Jakarta Operation Control Center, including integrating KRL radio consoles directly into corresponding sector dispatch desks, adopting personal headsets, and upgrading graphical track displays.
  • Institute proactive operational competency programs empowering personnel to identify, log, and mitigate latent signalling and track operation hazards before incidents materialize.
To PT Kereta Commuter Indonesia (KAI Commuter / PT KCI):
  • Implement uniform master time synchronization across all KRL fleet telemetry subsystems, cab audio recorders, and onboard CCTV surveillance via a single centralized network protocol.
  • Standardize and enforce emergency communication training modules, strictly requiring train drivers to depress the dedicated Emergency Call button whenever encountering track obstructions or line hazards.
  • Upgrade recurring refresher training curricula for KRL train crews, focusing heavily on managing emergencies within open block sections, inter-crew coordination, and rapid reporting of gauge clearances and track obstructions.
References & Official Documentation:
• Komite Nasional Keselamatan Transportasi (KNKT), Railway Accident Investigation Report No. KNKT.26.04.03.02.
• Republic of Indonesia Minister of Transportation Regulation No. PM 44 of 2018 on Technical Requirements for Special Railway Facilities.
• Republic of Indonesia Minister of Transportation Regulation No. PM 52 of 2014 on Technical Standards for Automatic Train Protection Systems.
• PT Kereta Api Indonesia (Persero), Service Regulation (Peraturan Dinas) No. 16A of 2023 Article 40 on Locomotive Brake Operation.

Related Dispatches

Officially Cancelled: PT KAI Halts 23 Used EMU Imports, Mandates 23 New Trainsets via PT INKA Flexible Production
Policy & Regulations

Officially Cancelled: PT KAI Halts 23 Used EMU Imports, Mandates 23 New Trainsets via PT INKA Flexible Production

Policy Rollback Analysis: Why PT KAI Canceled the Gapeka 2026 Train Consolidation and Renaming Plan
Policy & Analysis

Policy Rollback Analysis: Why PT KAI Canceled the Gapeka 2026 Train Consolidation and Renaming Plan

Planned Train Service Renaming and Fleet Consolidation in Gapeka 2026: Operational Implications & Headway Dynamics
Operations

Planned Train Service Renaming and Fleet Consolidation in Gapeka 2026: Operational Implications & Headway Dynamics

alurail alurail
Built upon GAPEKA 2025, visualized open-sourcedly with OpenRailwayMap and Leaflet.js. Powered by PostgreSQL (PostGIS, pgRouting), Dijkstra/A* Algorithms dan Viterbi Algorithm
Copyright ©️ 2024-2026 alurail by alula Made with 💗 from Pejaten, ID
Copyright ©️ 2024-2026 alurail by alula
Made with 💗 from Pejaten, ID

Community & Photographers

  • alurail Pass PRO
  • Submit Photo
  • User Suite
  • Curated Feed
  • Community Feed

Platform & Legal

  • About Platform
  • Terms & Conditions
  • Privacy Policy
  • Open Source Notices
  • FAQ / Help Center
Pass PRO PRO Upload Photo Suite Gallery
About
Terms
Privacy
License
FAQ
© 2026 alurail. All rights reserved.
alurail

alurail Legal & Info

About alurail

<h2>About AluRail</h2>

<p class="lead">
AluRail (Aluline TGV) is a free web-based platform that visualizes railway operations and train travel schedules across Indonesia. The service is available through <a href="https://aluline.id" target="_blank">aluline.id</a> and <a href="https://aluline.my.id" target="_blank">aluline.my.id</a>, developed independently by <strong>Alula</strong>
(<a href="https://alula.web.id" target="_blank">alula.web.id</a>) for railway enthusiasts (railfans) and passengers seeking a more intuitive understanding of train movements and timetable operations.
</p>

<h3>How It Works</h3>

<p>
AluRail transforms official <strong>GAPEKA 2025</strong> (Indonesia Railway Timetable Graph) data into an interactive geospatial visualization. Every train journey is reconstructed from scheduled departure and arrival times, station sequences, railway topology, and routing calculations to estimate how trains would move across the network.
</p>

<p>
Unlike conventional timetable viewers, AluRail continuously simulates train movement using a custom railway physics engine. The simulation considers various operational parameters including route geometry, train acceleration, braking, cruising speed, station dwell times, operational constraints, and other physical assumptions to estimate each train's position throughout its journey.
</p>

<p>
Whenever available, the platform also supports <strong>Crowdsourced Live Tracking</strong>. Passengers currently travelling on board may voluntarily share their GPS location. These telemetry reports are validated using map-matching algorithms and compared against the predicted GAPEKA route before being displayed to other users.
</p>

<h3>The Technology Behind AluRail</h3>

<ul>
<li><strong>PostgreSQL (PostGIS):</strong> Serves as the core geospatial database storing railway infrastructure, stations, and spatial relationships.</li>

<li><strong>Custom Railway Routing Engine:</strong> Implements graph-based routing algorithms including Dijkstra and A* to calculate railway paths, station connectivity, and operational routes.</li>

<li><strong>Railway Physics Engine:</strong> Simulates train movement by modelling acceleration, deceleration, cruising behaviour, station stops, speed restrictions, and travel progression based on timetable data.</li>

<li><strong>Viterbi Map-Matching:</strong> Validates crowdsourced GPS telemetry by matching noisy GPS observations onto the most probable railway track, improving live tracking reliability.</li>

<li><strong>Leaflet.js & OpenRailwayMap:</strong> Provide interactive map rendering and railway visualization layers.</li>
</ul>

<h3>Supported Railway Services</h3>

<p>
AluRail supports visualization for various railway services operating across Indonesia, including passenger, commuter, urban transit, heritage, and freight operations. Depending on data availability, the platform currently supports:
</p>

<ul>
<li>Intercity Passenger Trains (KA Antar Kota)</li>
<li>Whoosh High-Speed Railway</li>
<li>Commuter Line</li>
<li>Feeder Train Services</li>
<li>Local Passenger Trains</li>
<li>Freight Operations (Container, Cargo, Tanker, Coal, Cement and other freight services)</li>
<li>LRT Jakarta</li>
<li>LRT Jabodebek</li>
<li>LRT South Sumatra (Palembang)</li>
<li>Jakarta MRT</li>
<li>Ambarawa Heritage Railway</li>
</ul>

<p>
Additional railway operators and future services may be introduced as more infrastructure and timetable data become available.
</p>

<h3>Platform Features</h3>

<p>
AluRail combines timetable simulation, geospatial analysis, and live community participation into a single railway visualization platform. Key features include:
</p>

<ul>

<li>
<strong>Follow Mode</strong><br>
Automatically follows a selected train throughout its journey while continuously updating its estimated or live position.
</li>

<li>
<strong>Live GPS Cast</strong><br>
Passengers may voluntarily broadcast GPS telemetry while travelling onboard, allowing supported trains to display verified live positions instead of purely simulated movement.
</li>

<li>
<strong>Spotting Mode</strong><br>
Allows railfans to discover trains approaching nearby stations or railway crossings, making it easier to plan photography and train spotting activities.
</li>

<li>
<strong>Enhanced Railway Physics</strong><br>
Movement simulation considers railway gradient, elevation profile, track curvature, acceleration, braking, traction performance, speed restrictions, and operational constraints to produce more realistic train behaviour.
</li>

<li>
<strong>Detailed Route Analytics</strong><br>
Provides interactive charts including route elevation, curvature, gradient between stations, speed profile, and operational characteristics throughout the journey.
</li>

<li>
<strong>Train Information</strong><br>
Displays operational information about each service including operator, train category, route, schedule, formation details, and other service information.
</li>

<li>
<strong>Rolling Stock Database</strong><br>
Provides information about locomotives, EMUs, DMUs, coaches, wagons, and other railway vehicles used by supported services.
</li>

<li>
<strong>Coach & Class Information</strong><br>
Displays available passenger classes together with reference illustrations where available to help passengers identify onboard accommodation.
</li>
<li>
<strong>Adaptive Train Rendering</strong><br>
Train visualization automatically adjusts according to the current map zoom level. Different rendering modes are used to maintain smooth performance while displaying thousands of simultaneously simulated trains.
</li>

<li>
<strong>Train Filtering</strong><br>
Filter trains by service category such as Intercity, Commuter, High-Speed, Metro, LRT, Freight, Heritage, and other supported railway services.
</li>

<li>
<strong>Regional Filtering</strong><br>
Display trains operating within selected operational regions (Daerah Operasi / DAOP and other railway operational divisions) for easier monitoring.
</li>

<li>
<strong>Points of Interest (POI)</strong><br>
Explore railway-related locations including train spotting locations, photography viewpoints, railway landmarks, bridges, tunnels, stations, and other notable locations along the railway network.
</li>

<li>
<strong>Depots & Maintenance Facilities</strong><br>
View railway maintenance facilities including rolling stock depots, locomotive depots, maintenance workshops (Balai Yasa), stabling yards, and other operational infrastructure.
</li>

</ul>

<div class="disclaimer-box">
<h4>Disclaimer</h4>

<p>
<strong>AluRail is primarily a timetable simulation platform.</strong>
Unless a train is actively sharing verified Live Tracking data, all train positions displayed on the map are computational estimations generated from published schedules and the platform's railway physics engine.
</p>

<p>
Although the simulation attempts to realistically reproduce railway operations, actual train movements may differ significantly due to dispatching decisions, signal aspects, operational priorities, temporary speed restrictions, maintenance work, weather conditions, delays, early departures, extraordinary operations, GPS inaccuracies, or many other real-world factors that cannot always be observed by the platform.
</p>

<p>
Even when Live Tracking is available, GPS accuracy depends on user participation, mobile device quality, satellite reception, and local environmental conditions. Therefore, displayed positions should always be considered informational rather than authoritative.
</p>

<p>
<strong>This service must not be used as an official operational reference</strong> for travel planning, ticketing decisions, passenger information, or railway operations. Always refer to official PT Kereta Api Indonesia (Persero) information channels for accurate operational updates.
</p>

<p>
AluRail / Aluline TGV is an independent community project and is not affiliated with, endorsed by, partnered with, or officially associated with PT Kereta Api Indonesia (Persero), OpenStreetMap, OpenRailwayMap, or any other referenced organizations.
</p>
</div>

<p class="footer-note">
Made with ❣️ from Pejaten, Indonesia.
</p>

Terms of Use

<section id="terms-en" class="lang-content">
<h2>Terms of Service</h2>
<p class="effective-date"><strong>Effective Date:</strong> January 1, 2025 (Updated for GAPEKA 2025)</p>

<h3>1. Acceptance of Terms</h3>
<p>By accessing AluRail through aluline.id, aluline.my.id, and related subdomains (collectively, the "Service"), you acknowledge that you have read, understood, and agreed to these Terms of Service. If you do not agree, you must discontinue use of the Service.</p>

<h3>2. Independent Service</h3>
<p>AluRail is an independent community project developed by Alula. It is not affiliated with, endorsed by, or operated by any railway operator, government agency, or transportation authority unless explicitly stated.</p>

<h3>3. Nature of the Service</h3>
<p>The Service provides train schedule visualization, estimated train positions, operational simulations, and crowdsourced location validation based on publicly available information, GAPEKA data, and algorithmic processing. Displayed information may differ from actual railway operations.</p>

<h3>4. No Operational Guarantee</h3>
<p>Train movements, schedules, platform assignments, delays, cancellations, dispatching decisions, and operational conditions may change without notice. The Service must not be considered an official operational information source.</p>

<h3>5. Crowdsourced Contributions</h3>
<p>Users may voluntarily contribute GPS telemetry while onboard trains. Submission of fake GPS data, manipulated locations, automated submissions, spam, or attempts to interfere with system accuracy is strictly prohibited.</p>

<h3>6. Acceptable Use</h3>
<p>You agree not to misuse the Service, interfere with its infrastructure, reverse engineer protected components, exploit security vulnerabilities, scrape excessive data, or use automated systems that negatively impact platform availability.</p>

<h3>7. Intellectual Property</h3>
<p>Unless otherwise stated, the Service, its software, interface, branding, and original content remain the intellectual property of their respective owners. Open-source components remain governed by their own licenses.</p>

<h3>8. Availability</h3>
<p>The Service may be modified, suspended, restricted, or discontinued at any time without prior notice.</p>

<h3>9. Disclaimer ("AS IS")</h3>
<p>THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ACCURACY, OR CONTINUOUS AVAILABILITY.</p>

<h3>10. Limitation of Liability</h3>
<p>To the fullest extent permitted by law, Alula shall not be liable for direct, indirect, incidental, consequential, special, or punitive damages arising from the use of or inability to use the Service, including travel decisions, delays, missed connections, financial loss, personal injury, or data loss.</p>

<h3>11. Changes to these Terms</h3>
<p>These Terms may be updated periodically. Continued use of the Service constitutes acceptance of the revised Terms.</p>

<h3>12. Contact</h3>
<p>Questions regarding these Terms may be directed through the official AluRail contact channels.</p>
</section>

<h3>Independent Service Disclaimer</h3>

<p>AluRail is an independent community-developed platform created by Alula for railway visualization, research, educational, and enthusiast purposes.</p>

<p>AluRail is <strong>not affiliated with, associated with, authorized by, endorsed by, sponsored by, supported by, maintained by, operated by, or officially connected with</strong> PT Kereta Api Indonesia (Persero), PT Kereta Commuter Indonesia, PT Kereta Api Logistik, PT Kereta Api Pariwisata, PT Kereta Cepat Indonesia China (Whoosh), MRT Jakarta, LRT Jabodebek, LRT Jakarta, LRT Sumatera Selatan (Palembang), their subsidiaries, affiliates, successors, government agencies, transportation authorities, or any other railway operators unless explicitly stated.</p>

<p>All company names, railway service names, station names, train names, logos, trademarks, service marks, brands, route names, and other intellectual property displayed within the Service remain the property of their respective owners and are used solely for identification, informational, interoperability, historical, mapping, educational, or descriptive purposes.</p>

<p>The visualization presented by the Service represents publicly available operational information, algorithmic estimations, historical references, and voluntary community contributions. It must not be interpreted as an official operational system, railway dispatching platform, passenger information system, or real-time control center operated by any railway company.</p>

Privacy Policy

<section id="privacy-en" class="lang-content">
<h2>Privacy Policy</h2>
<p class="effective-date"><strong>Last Updated:</strong> June 2026</p>

<h3>1. Privacy Commitment</h3>
<p>Your privacy is important to us. We collect only the information reasonably necessary to operate and improve the Service.</p>

<h3>2. GPS Collection</h3>
<p>Your GPS location is accessed only after you intentionally enable Live Tracking. Background location is never collected without your explicit action.</p>

<h3>3. Processing</h3>
<p>Submitted GPS telemetry is processed using routing algorithms including Viterbi matching against the railway network to validate train positions. Telemetry is not associated with your personal identity.</p>

<h3>4. Server Logs</h3>
<p>Standard server logs such as IP address, browser type, timestamps, and technical diagnostics may be collected for security, abuse prevention, troubleshooting, and performance monitoring.</p>

<h3>5. Data Retention</h3>
<p>Live telemetry is temporary and automatically expires after the associated trip ends unless longer retention is required for security investigations.</p>

<h3>6. Third Parties</h3>
<p>We do not sell or rent your GPS telemetry. Limited technical processing by infrastructure providers may occur solely for operating the Service.</p>

<h3>7. Security</h3>
<p>Reasonable technical and organizational safeguards are implemented, although no online system can guarantee absolute security.</p>

<h3>8. User Safety</h3>
<p>We discourage publicly sharing real-time GPS positions. Anonymous mode or pseudonyms are strongly recommended.</p>

<h3>9. Your Responsibility</h3>
<p>Use of Live GPS or spotting features is entirely voluntary and at your own risk.</p>
</section>

Open Source Notices

<section id="opensource-en" class="lang-content">
<h2>Open Source Notice</h2>
<p>AluRail is built upon numerous open-source technologies and open data projects. We sincerely thank the communities maintaining them.</p>
<ul>
<li><strong>PostgreSQL, PostGIS & pgRouting</strong> — Spatial database, GIS extension, and routing engine.</li>
<li><strong>OpenStreetMap & OpenRailwayMap</strong> — Railway infrastructure and mapping data under their respective licenses.</li>
<li><strong>Leaflet.js</strong> — Interactive mapping library.</li>
</ul>
<p>All trademarks, copyrights, and licenses belong to their respective owners. Use within AluRail does not imply endorsement by those projects.</p>
</section>

alurail for Android

Versi 1.3.0 • APK (110 MB)

Download the official alurail app package for Android.

Download APK
Requires Android 8.0 (Oreo) or later
alurail Pass Prime GRATIS!
early access

alurail Pass Prime GRATIS!