Search Forum
Blog Entry# 1545189
Posted: Jul 19 2015 (17:01)
17 Responses
Last Response: Aug 02 2015 (23:08)
17 Responses
Last Response: Aug 02 2015 (23:08)
this was the bullshit answer that I received from CR for asking stoppages at thane and kalyan -_-
12 Posts
Most of the times, i have seen 17318 halting at TNA, pf.7 for two obvious reasons. UP fast line is occupied by fast EMU or EMU expected, hence unable to get clear to cross over to 3rd line.
11029 Koyna Express which has halt at TNA, gets clear to go ahead...forcing 17318 to take unscheduled halt.
11029 Koyna Express which has halt at TNA, gets clear to go ahead...forcing 17318 to take unscheduled halt.
17318 stopping unusually has no use at all... as the reserved pax will obviously be boarding from ltt itself, but if it stops in the up direction ie 17317 then that would be greatly useful for the people... I hv travelled 3 times till now in 17317 but it sadly didn't stop in the pf but yes in the outers
What i meant to say is, if 17318 is stopping unscheduled most of the times (obviously for more than 2 mins) , then there is nothing wrong in giving it a scheduled stoppage. It will be beneficial for pax, no doubt, as pax need not have to rush to LTT early morning
Traveled in the down train yesterday.
Stopped at Thane for 13 minutes and at Kalyan for 8 minutes.
Only four reserved people in S6 including me. :D Will post the pic of chart later.
Stopped at Thane for 13 minutes and at Kalyan for 8 minutes.
Only four reserved people in S6 including me. :D Will post the pic of chart later.
Unnecessarily, this train follows Koyna. Koyna has so many halts and by following this, UBL exp is not gaining anything.
Either it should overtake and reach UBL by night 2200 or it should start by 1300 from LTT and reach UBL in the early morning.
Completely screwedup TT now.
Either it should overtake and reach UBL by night 2200 or it should start by 1300 from LTT and reach UBL in the early morning.
Completely screwedup TT now.