12710 has started 25 mins late at SC i.e. at 23:20 and reached Kondapalli by 4:20 am.. very impressive run.. but stopped after kondapalli for nearly an hour outside BZA. I do not understand this logic of BZA division. Sometimes I feel BZA and SC divisions are bad at traffic management.
well some one feel that BZA also worst zone
This happens regularly I guess. I have rarely seen this reach BZA before 5 am
I do not say it is bad..... just words out of frustration.. Impressive revenues from freight is not possible without good traffic management
Frustration because of long waiting in the outer of BZA..
BZA is not a zone but just a Division...
Will GNWL 38 gets cnf in simhapuri exp on may 10th from NLR-SC....pls reply
Ys will confirm,in worst case goes to RAC
Reason for change in Schedule and delay in Train Running status
After change of depature time of Simhapuri express 12709 from 21.00 to 22.10 hrs the train was handed over to SC division on most of the occasions in the RT or 15 to 20mins late as per statistics taken for month of Dec 2014. Only 9 times the train was handed over beyond 30minutes late to SC division.This is also due to late running of the express trains taken over from MAS and GTL divisions.
The change in depature time was effected due to change in arrival and depature timings of 17209 SBC-CCT express whch arrive earlier ar 21.45 hrs and advanced to 20.05hrs to gudur station as a arrangement with the
Blog Entry Unlocked.
On request by blog author.
We would like to inform that on analysis of the punctuality of 12709 Simhapuri, it has been found that whenever it is received late from other division i.e BZA this train misses its charted path and loses its punctuality due to non-availability of path/clash of timings with the other trains and other operational constraints and platform congestion at Secunderabad station.
Few times precedence has been given to sensitive short distance commuter trains.
BZA is handling simhapuri late to SC div
Nothing in brief.....BZA is balming other train are causing simhapuri delay by min 20mins atleast.....SC is saying BZA div is handing over late to SC div that is causig more delay antunadu....
No Solution for now
Can admins unlock the above post
Got reply from SC operating staff.
Train arrived today at 8am,
Avg train arrives late by 1 hr , new TT just ruined this train also daily pax lost ogl-nlr fast mrng connection
Great SCR BZA divn, this train has been OT by a SF spl at NLR today :). 02854 ERS - SRC SF Spl has OT 12709 Simhapuri. The obsession with other zone trains continues even with spls :).
ERS-SRC Spl should reach BZA at 02:10 and Simhapuri at 02:35. So I think this OT is justified
02854 spl has non stop run from GDR to BZA....and there is no issue if being OT at NLR as NLR being a halt for Simhapuri and has nearly 8 halts from NLR to BZA
True, but a special train OT regular train is something rare and i didn't witnessed till date :). Generally spls will get less preference in other zones.
By the way, there is no stop at GDR as per TE. After RU, it will run non-stop till BZA.
The main reason for OT is....to clear the main line block
If 02854 was not given OT...then when simhapuri halts at NLR then this spl has to halt outer which causes main line block making other trains also delayed..especially it effects a lot in goods flow
I just shared the info what i has seen in IRI,i correct my self
VM - KGP has given the starter at BZA as HYB - VSKP godavari is delayed. Now i guess, it can't reach VSKP till 6:30 am. Also, MAS - JP has given the starter at BZA as VSKP - HYB godavari is also delayed :).
Tell me is this always right time at bza because i am having train 22 morning at bza 12666 at 5.30 am
Can i catch 12666 cape -howarh express at bza at 5.30 am
post ur pnr in pnr section. delete it from here
This has a delay of Normally 20-30 mins arr at BZA. I think you can take the train because cape-hwh will be trailing this train
Should be a safe bet for you,should make it...