Forum Super Search
Posting Date From:
Posting Date To:
Train Type:
ONLY with Pic/Vid:
Sort by: Date:     Word Count:     Popularity:     
Public:    Pvt: Monitor:    RailFan Club:    

Full Site Search
Thu Jul 20, 2017 18:30:38 ISTHomeTrainsΣChainsAtlasPNRForumGalleryNewsFAQTripsLoginFeedback
Thu Jul 20, 2017 18:30:38 IST

Blog Entry# 2089076  
Posted: Dec 12 2016 (21:46)

No Responses Yet
General Travel
Dec 12 2016 (21:46)   16561/Yesvantpur - Kochuveli AC Express

8 Mail 8 Shatabdi   304 blog posts   49 correct pred (72% accurate)
Entry# 2089076            Tags   Past Edits
A Trip by the AC Express to CBE!
Entered YPR at around 1340 hrs, and PFs 1,2 and 6 were occupied by YPR-KCG, Kondaveedu Exp and 12629 KSK. KSK left at around 1415 hrs and Kondaveedu Exp left sharp at 1430. Also, TK passenger came and left from PF#3 close to time.
At around 1435 hrs, our train was allotted PF#2, and rake was shunted in by a KJM WDM-3D 5 min later. Meanwhile, the DEMU to HSRA occupied PF#3 now while Chikmagalur pass was allotted PF6. At 1520, we showed no
signs of dep. And at 1530, KCG exp started from PF1, which meant we were delayed. We finally started at 1540 hrs (with a nice heavy jerk) and made our way. We halted at BAND for HWH duronto crossing, while a Goods train was stationed at another PF, headed by twin UBL WDG4. After duronto crossed, we made our way to KJM to halt at 1637 hrs. We left a couple of mins later.
After KJM, we started blasting, crossing a MEMU on the way. Since we were late and Shtb was running on time, expected it to OT us at BWT. But, at Tyakal, we were looped and after 5 min, Shtb OT us at 110 kmph, headed by a WAP7 (We were headed by a WAP4 btw).
Left soon and stopped exactly for 40 seconds at BWT, before leaving and continuing to blast to make up lost time. At KPN, we crossed 12609 and we moved on.
By Mulanur, I felt we had made up 5 min of time, and after Somanayakanpatti, it was dark outside and nothing much could be seen. We just slowed down near by-pass, didnt stop as TPTY exp and 12679 were already ahead and 12695 was chasing us. We got ahead of it and after crossing Tirupattur, we picked up speed and started to blast. Crossed 12244 Shtb at around 7 PM, which meant, if given priority, we could still make it in time. At morappur, we crossed a terribly late running Kovai Exp and continued our progress. We slowed down only near Magnesite Jn and entered Salem at 2013 hrs and left after a 2 min halt.
After SA, TPTY IC started trollingn us. We slowed down 2 or 3 times and even stopped at Cauvery Station to maintain the gap with TPTY exp. Finally entered ED at 2115 hrs onto PF2. Hoped to leave soon, but didn't move even after 5 min. Meanwhile, Chalukya from TEN entered PF3 with UBL WDP4 and announcements went for 12695 to arrive on PF 1. At 2130 hrs we finally departed, having had a 15 min halt and simultaneously trolling 12695 too. After ED, the run was not that fast. Max speed might have been 90 that's all. Rchd TUP at 2215 hrs, where we met 12778 to UBL and left after a 2 min halt. Moved on, and after a halt at CBF for 2 min, rchd CBE at 2305 hrs on PF#1, delayed by 30 min with run time 7:25 , not really bad but if handled well, this train could do 7 hrs ypr-cbe and cbe-kcvl another 7-7:30 hrs.
I felt, arrival time of tpty exp must be changed to 2225 hrs at CBE, else this train gets trolled. Also, seems like 12008 overtakes this on most occasions. And this train doesn't need B10 and B11 for sure. This surely could be upgraded to SF category. And the current set of halts are enough, no more stops should be added.

ARP (Advanced Reservation Period) Calculator

Reservations Open Today @ 8am for:
Trains with ARP 10 Dep on: Sun Jul 30
Trains with ARP 15 Dep on: Fri Aug 4
Trains with ARP 30 Dep on: Sat Aug 19
Trains with ARP 120 Dep on: Fri Nov 17


Rail News

New Trains

Site Announcements

  • Entry# 2175399
    Feb 23 2017 (01:22PM)

    There has recently been a lot of frustration among RFs when their Station Pics, Loco Pics, Train Pics get rejected because the "number is not showing", "shed is not visible", the loco/train is at a distance, Train Board is too small, "better pic available", etc. . To address this issue, effective tomorrow, ALL...
  • Entry# 2165159
    Feb 15 2017 (09:53AM)

    A minor update, but may impact many members: Hereafter, FMs will be able to delete invalid Red Flags on Imaginary trains. Red Flags can be removed by FMs, only against specific complaints filed against the blog. This does not give all members the right to complain against EVERY single red flag they...
  • Entry# 2155798
    Feb 08 2017 (11:40AM)

    -@all members: As of recently, there has been a trend whereby minor name updates of Trains/Stations - whether such and such regional name should be there or not, whether the train should be called "Abc Express" or "Abc Superfast Express", etc. are threatening to take over the majority of Timeline entries. Also,...
  • Entry# 2147631
    Feb 01 2017 (11:05AM)

    A new experimental feature is being introduced called BotD - "Blog of the Day". The rules are: . 1. Replies are not eligible - only the Top Blog. 2. ONLY Blogs posted today (the day of the vote) are eligible. 3. Every member has ONE vote. In the course of the day, you may keep...
  • Entry# 2136570
    Jan 23 2017 (12:25AM)

    Several new features have been introduced recently to the Forum, and we are forever striving to make Member experience here more productive and satisfying. With the recent introduction and success of the new FM System, it has been observed that small groups of highly involved and enthusiastic members are far more...
  • Entry# 2134907
    Jan 21 2017 (02:46PM)

    It has been over 2 weeks since the appointment of the current batch of FMs and 750 Complaints have been handled so far. It gives me immense pleasure in congratulating them for running the team diligently, professionally, competently and above all, without a shred of controversy or bias. The FM position...
Scroll to Top
Scroll to Bottom

Go to Mobile site
Disclaimer: This website has NO affiliation with the Government-run site of Indian Railways. This site does NOT claim 100% accuracy of fast-changing Rail Information. YOU are responsible for independently confirming the validity of information through other sources.