Search Forum
Blog Entry# 1579536
Posted: Sep 01 2015 (16:46)
25 Responses
Last Response: Sep 07 2015 (11:34)
25 Responses
Last Response: Sep 07 2015 (11:34)
Further slowed down :(
Starts 20 min early at COA and arrives 10 min late at GDR
Starts 20 min early at COA and arrives 10 min late at GDR
20 Posts
I firmly believe that this adjustment was done to avoid sandwich in between Annavaram and Rajamundry. 2717 - Amaravati group - 8463 and 7644 join the drama at Samarlakota. For record purpose, Ratnachal was experiencing back-to-back overtakes just to let Circar go ahead. The operation would be uniform from now on, at least on 90% of days. This is a brilliant step by SCR. :-)
I guess the batch of trains coming from Vizag will cause a problem if they are delayed. But they could have as well delayed Circar by 20-25 min at COA itself and run behind Prashanti/Anga from SLO itself. As it is Circar is taking more time ( 5h 52min ) to reach BZA than Seshadri in the same route ( 5h 15min). The schedule after BZA won't be affected, and some travel time can also be reduced.
You are right. But, there is always 17404 at Bhimavaram Town which can't be delayed. If Circar is rescheduled to depart late by another 25 minutes, then it would reach BVRT around 18:10 - add 15 - 20 minutes delay to that. Thus, it will clash with 17404. Besides, it will further delay BVRT-NDD passenger which is connecting train to 57231. Circar cannot follow 17404 because PF3 in GDV is blocked by 7402, PF1 by 7404 and PF2 will be blocked for 7480/7482. Hence, it is not a viable option to pospone the departure by 25 minutes at COA unless 7404's schedule is adjusted which I think is too tough to happen.