20 February,2025 02:19 PM IST | Mumbai | Rajendra B. Aklekar
File Pic
A suburban fast train skipped Mulund station by a few coaches on Tuesday evening, causing inconvenience to several commuters. Sources reported that while the train briefly halted, it did not reverse to adjust its position, forcing passengers who missed their stop to disembark at the next station, Thane, approximately 2 km away.
"I think the motorman misjudged the stop and overshot the platform by a few coaches. There was a lot of confusion, and the train remained halted for about seven to eight minutes. Eventually, an announcement was made by the train staff, requesting affected commuters to alight at Thane station instead. After the announcement, the train resumed its journey," said Vedant Mhatre, a commuter onboard.
Sources confirmed that the train in question was a Kasara-fast local that had departed from Mumbai CSMT at 8:44 PM, with a scheduled halt at Mulund at 9:22 PM.
ALSO READ
Suburban services on WR affected after train skips halt at Charni Road station
Motormen call off plan to protest after assurance on their demands
WR cancels jumbo block between Mumbai Central and Mahim, services to run normal
Motormen’s protest may hit Central Railway services on Monday, here's why
Work to build bullet train's origin station progressing fast: Vaishnaw
The suburban services on Western Railway were badly affected owing to a technical issue with the train management system (TMS), leading to detention of Mumbai local trains.
The movement of several trains was disrupted owing to the glitch, leading to severe delays in the timings of the afternoon trains.
"One train halted on platform number 5 for a long time as constant repeated announcements were made that its a Churchgate Fast local. When I reached there, the motorman was calling up the control room insisting its a Virar Fast. After five to 10 minutes, an announcement was made on the platform stating that it was in fact a Virar Fast," said a commuter, Vedant Mhatre.
"There was a problem at TMS, which occurred at 2.30 pm for 25 minutes. There was a cascading effect and trains got delayed by 10-15 minutes. The issue has been rectified," a Western Railway spokesperson said, adding, "There was no major glitch and the problem was rectified within a half an hour."
