Search Forum
Blog Entry# 2301671
Posted: May 31 2017 (16:21)
41 Responses
Last Response: Jun 01 2017 (11:22)
41 Responses
Last Response: Jun 01 2017 (11:22)
May 31 2017 (16:21) 22120/Madgaon - Mumbai CSMT Tejas Express | KRMI/Karmali (2 PFs)
MAO_Jan_Shatabdi~
MAO_Jan_Shatabdi~ 15644 blog posts22120 KRMI-CSTM TEJAS EXPRESS KRMI CSTM LEFT KARMALI at 15:59, Running late by 1hrs 29 mins
Delayed due to technical reasons..
Let's see hw much it covers..
Delayed due to technical reasons..
Let's see hw much it covers..
36 Posts
Whooping slack of 60 mins 😆
Because of this Down traffic got badly trolled yesterday.. Single line hai yeh, xings k liye bhi slack dena padta hai trains ko.. Slack for this is just 20-30 mins..
Anyways 5hrs for 410.8 KMS @ 82.16 km/hr on single track is an excellent run..
Because of this Down traffic got badly trolled yesterday.. Single line hai yeh, xings k liye bhi slack dena padta hai trains ko.. Slack for this is just 20-30 mins..
Anyways 5hrs for 410.8 KMS @ 82.16 km/hr on single track is an excellent run..
Dont know what happened at KRMI as even updates were not matching with the usual time taken by any other train....but we calculated from Pernem crossing at 16:15 and the average was a mindblowing 90 kmph
Yday Tejas was delayed from KR and Tejas is a board /RM monitored train. Hence the special priority. That doesnt mean 60 mins slack is avbl.
...
more...
Yday Tejas was delayed from KR and Tejas is a board /RM monitored train. Hence the special priority. That doesnt mean 60 mins slack is avbl.
...
more...
I concluded 60 mins slack because in both the directions it did the same... easily covered up 60 mins... actual timetable is of 7.5 hrs n they always add necessary slack so that train in any case shud cover up n be on time. Madgaon terminal would have been a minus point here as my 22119 was 55 mins delayed still krmi arrival was just 8 mins late... They got enough time for sec maintenance of cleaning. Had this been mao terminal the delay cud be more. . So, the timetable is properly planned including krmi terminal over mao. I stick to my point it has slack of 60 mins overall which is a good thing
If its RB monitored train hence high priority. ..then its not really a good thing coz in future priority might not be given .. being positive about the timetable I concluded that there is enough slack which will assure the train will reach on time always*
KRMI mde the departure of train just 8 mins late its mentioned 4 pm departure which is fully wrong. Coz at 4 pm we crossed double decker at next station
KRMI mde the departure of train just 8 mins late its mentioned 4 pm departure which is fully wrong. Coz at 4 pm we crossed double decker at next station
If it was able to screw trains in down run, still got delayed then the reasons for kudal delay is just rainfall, the 120 mps was restricted to 110 kmph due to rains... still being 55 mins late at Kudal and arriving KRMI just 8 mins late, @110 mps confirms the 55-8=47 mins slack in KR and in CR too there is evident slack.