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

Search
  Go  
Full Site Search
  Search  
 
Thu Jun 22, 2017 17:49:49 ISTHomeTrainsΣChainsAtlasPNRForumGalleryNewsFAQTripsLoginFeedback
Thu Jun 22, 2017 17:49:49 IST
PostPostPost Trn TipPost Trn TipPost Stn TipPost Stn TipAdvanced Search
Filters:

Blog Posts by mrssridevi.kilari
Page#    2 Blog Entries  
  
General Travel
0 Followers
1995 views
May 04 2014 (20:08)   12727/Godavari SF Express
 

mrssridevi.kilari   4 blog posts
Entry# 1083846            Tags   Past Edits
SCR making Godavari Express sucks. People are listing it as Queen of SCR, but it had already lost the sheen. Especially Section Controller making it trolling normal express. I am observing for 12727 / 12728 for last one month continuously.
12728
1. Never on dot from Sec ‘bad
2. Covers SC - Kazipet with good speed, even though some times TPT
...
more...
- NZM giving preference over this, last week section controller allowed 12707 , 5 min ahead of 12728 , it trailed until Kazipet where 12707 reached 13 min ahead of scheduled arrival and 12728 admitted with 8 min late.
3. From Kazipet to Warangal is another pathetic; either they will make it halted more than the scheduled halt of 2 min, generally from 5 to 15 min.
4. Reaching Warangal with general delay of 20 - 30 min.
5. From Warangal to Khamam, the run very fast like there is no another day, however with 1 halt introduced between WL - KMT, it is not able touch its earlier records.
6. Only thing we feel good about 12728 is, allowing it to over take 12616. But does it really require?
7. Once KMT is over, then stop, start and crawling oblivious observation. Every day un-officially it will be halted from Tondalagopavaram, Errupalem, Gangineni, Cheruvu Madhavaram, Kondapally, Rayanapadu and BZA NE Cabin. Hardly it touches 90 Kmph in this stretch.
8. Though it is able to reach Kondapally by 22:30, only admitting it to BZA with good delay from 10 - 40 min (never happened loco reversal within 20 min)
Even though there no other trains ahead of this in this section.
9. That is it, from BZA - VSKP, it is all depending on controller mood. Resulting 10 - 15 min daily delay to arrive VSKP.
The story of 12727 is too sad, Getting WAP-7 now a days regularly but making it run as WAG-5.
Regular over take by GHY weeklies bounded for South. Some times 17015 is also overtaking 12727 because of less stops between VSKP -RJY for 17015. We see the delay is happening on purpose as the same dealy at anaparti is being maintained at RJY.
Even though it reaches ahead of time to outer of BZA because of slack time, it would never admitted on time to BZA. And now a days the delay from BZA is increased to 1+ hour resulting 20 - 30 min delayed arrival to SC. Of course it never reached HYB on time any time.
I think it is good time to revert it back to its old avatar of 7/8 ( 7007/7008) avatar. It could save some money to public.

3 posts - Sun May 04, 2014

  
493 views
May 04 2014 (21:48)
Pavankumar2717~   5610 blog posts   401 correct pred (77% accurate)
Re# 1083846-4            Tags   Past Edits
VSKP RJY sector has habit to make SF's OT by normal express..

  
447 views
May 04 2014 (22:05)
mrssridevi.kilari   4 blog posts
Re# 1083846-5            Tags   Past Edits
I don't know the problem is with BZA division. They few favorite trains, by hook or crook they will make all possibilities to run on time for Tamilanadu, Padmavathi, Sathavahana .. also do lot favor to GHY based trains and to some extent Faluknuma

  
361 views
May 04 2014 (23:09)
Pavankumar2717~   5610 blog posts   401 correct pred (77% accurate)
Re# 1083846-6            Tags   Past Edits
BZA division is in deep love with Amaravathi SF,Prasanthi SF..

  
368 views
May 04 2014 (23:11)
Pavankumar2717~   5610 blog posts   401 correct pred (77% accurate)
Re# 1083846-7            Tags   Past Edits
Satavahana always gets screwed when going towords SC..

  
268 views
May 04 2014 (23:58)
sys tem~   8224 blog posts   75729 correct pred (76% accurate)
Re# 1083846-8            Tags   Past Edits
long distance trains should be given priority considering APSK runs on extremely tight schedule between SC and NGP ..it does this section in 8 hours flat ...and secondly if you thing godavari doesnt get priority think about the poor boy - kcg - sbc SF ..in its own terriroty SCR it runs late by alteast 1 hour to 2 hours daily without any fail towards SBC ..

5 posts are hidden.
  
General Travel
0 Followers
899 views
May 04 2014 (20:08)   12728/Godavari SF Express (PT)
 

mrssridevi.kilari   4 blog posts
Entry# 1083845            Tags   Past Edits
SCR making Godavari Express sucks. People are listing it as Queen of SCR, but it had already lost the sheen. Especially Section Controller making it trolling normal express. I am observing for 12727 / 12728 for last one month continuously.
12728
1. Never on dot from Sec ‘bad
2. Covers SC - Kazipet with good speed, even though some times TPT
...
more...
- NZM giving preference over this, last week section controller allowed 12707 , 5 min ahead of 12728 , it trailed until Kazipet where 12707 reached 13 min ahead of scheduled arrival and 12728 admitted with 8 min late.
3. From Kazipet to Warangal is another pathetic; either they will make it halted more than the scheduled halt of 2 min, generally from 5 to 15 min.
4. Reaching Warangal with general delay of 20 - 30 min.
5. From Warangal to Khamam, the run very fast like there is no another day, however with 1 halt introduced between WL - KMT, it is not able touch its earlier records.
6. Only thing we feel good about 12728 is, allowing it to over take 12616. But does it really require?
7. Once KMT is over, then stop, start and crawling oblivious observation. Every day un-officially it will be halted from Tondalagopavaram, Errupalem, Gangineni, Cheruvu Madhavaram, Kondapally, Rayanapadu and BZA NE Cabin. Hardly it touches 90 Kmph in this stretch.
8. Though it is able to reach Kondapally by 22:30, only admitting it to BZA with good delay from 10 - 40 min (never happened loco reversal within 20 min)
Even though there no other trains ahead of this in this section.
9. That is it, from BZA - VSKP, it is all depending on controller mood. Resulting 10 - 15 min daily delay to arrive VSKP.
The story of 12727 is too sad, Getting WAP-7 now a days regularly but making it run as WAG-5.
Regular over take by GHY weeklies bounded for South. Some times 17015 is also overtaking 12727 because of less stops between VSKP -RJY for 17015. We see the delay is happening on purpose as the same dealy at anaparti is being maintained at RJY.
Even though it reaches ahead of time to outer of BZA because of slack time, it would never admitted on time to BZA. And now a days the delay from BZA is increased to 1+ hour resulting 20 - 30 min delayed arrival to SC. Of course it never reached HYB on time any time.
I think it is good time to revert it back to its old avatar of 7/8 ( 7007/7008) avatar. It could save some money to public.
Page#    2 Blog Entries  

ARP (Advanced Reservation Period) Calculator

Reservations Open Today @ 8am for:
Trains with ARP 10 Dep on: Sun Jul 2
Trains with ARP 15 Dep on: Fri Jul 7
Trains with ARP 30 Dep on: Sat Jul 22
Trains with ARP 120 Dep on: Fri Oct 20

  
  

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.