Jakarta, CNBC Indonesia - The National Transportation Safety\nCommittee (KNKT) has disclosed an initial investigative report into the\ncollision between the Argo Bromo Anggrek train and a KRL Commuter Line\non the Kampung Bandan-Cikarang route at Bekasi Timur station on 27\nApril. The incident involved Argo Bromo Anggrek train number KA 4B on\nthe Gambir-Surabaya Pasar Turi route and the KRL train number 5568A on\nthe Kampung Bandan-Cikarang route.<\/p>\n
Chairman Soerjanto Tjahjono said in the initial report there were\nthree causes of the collision between the two trains. Firstly, a\nsignalling anomaly between Bekasi and Bekasi Timur stations. \u2018Based on\nthe results of a Train Stepping service simulation conducted in the\nBekasi Station Equipment Room and field simulations after the incident,\nwith the route running directly from Track 3 at Bekasi Station and the\ntrack condition 104BT in the Bekasi Timur area being occupied, the\nsignal at the exit J12 (Bekasi) could display a green aspect (symbol 5)\nor a safe aspect. The repeater signal UB104 shows a horizontally lit\nwhite light (symbol 9C3) indicating a red block indication. Then, the\nblock signal B104 shows a red aspect (symbol 7). The simulation results\nare consistent with the signalling aspects.\u2019<\/p>\n
From the simulation, this indicates the signal at Bekasi Station\ncould not detect the 5568A train at Bekasi Timur, which would indicate\nthat the exit signal should show a safe or green light. The repeater\nsignal showed an unsafe aspect or a horizontal white light when the\npreceding signal was red, and the block signal showed a red aspect. The\nexit signal, in fact, should have shown a caution (yellow) if the\npreceding signal still indicated an unsafe or red status.<\/p>\n
Not only that, based on preliminary simulations, the driver of Argo\nBromo Anggrek also had difficulty seeing the repeater signal in the\nBekasi-Bekasi Timur block due to illumination from nearby homes and\nmarket lights.<\/p>\n
\u2018In the cab of the locomotive, and in the KRL cab, we observed at\nnight that the driver struggled to see the repeater signal because of\nlighting from markets and houses around the track. There were lights\nfrom residents and street lamps with intensity and colour resembling the\nrepeater signal,\u2019 he said.<\/p>\n
In addition to signalling, there was miscommunication between the\nrailway\u2019s Train Operation Control (PK). Moreover, the communication\nsystem was considered overly convoluted. \u2018The Radio communications used\nby the PK South (S.27) and PK East (S.1) areas were not integrated well,\ncausing delays as PK South had to inform the Chief who then passed the\ninformation to PK East. This needs addressing,\u2019 he explained.<\/p>\n
He said PK did not know the real-time conditions around Bekasi, as\ncommunications were carried out via voice radio. \u2018We received reports\nfrom the Argo Bromo Anggrek driver that he had to brake from 1.3 km\nafter receiving information of a temperamental approach of the KRL\nahead. The driver attempted braking, but PK did not know the actual\nconditions around Bekasi Timur since communication was only by radio in\nthe cab.\u2019<\/p>\n
There was also miscommunication between PK Bekasi Timur and the Argo\nBromo Anggrek driver, where PK instructed only progressive braking\nrather than full braking, making the collision unavoidable. \u2018PK East\ninformed the driver to perform gradual braking and to use the horn 35\ntimes, but information about the line clearance ahead was not obtained\nfrom the relevant crossing,\u2019 he said.<\/p>\n
Soerjanto explained that KA 4B Argo Bromo Anggrek had actually\nalready performed emergency braking when passing the block signal before\nBekasi Timur. However, because PK only instructed gradual braking, the\ncollision could not be avoided. \u2018From the data logger, KA 4B Argo Bromo\nAnggrek performed emergency braking and independent braking at 300\nmetres from the block signal before Bekasi Timur. The collision occurred\nat a speed of 40-60 km\/h,\u2019 he concluded.<\/p>", "url": "https:\/\/jawawa.id\/newsitem\/key-causes-of-the-argo-bromo-anggrek-collision-with-the-krl-signalling-and-communications-1779542244", "image": "" }, "sponsor": "Okusi Associates", "sponsor_url": "https:\/\/okusiassociates.com" }