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
Tue Jul 25, 2017 12:09:06 ISTHomeTrainsΣChainsAtlasPNRForumGalleryNewsFAQTripsLoginFeedback
Tue Jul 25, 2017 12:09:06 IST
PostPostPost Trn TipPost Trn TipPost Stn TipPost Stn TipAdvanced Search

Blog Posts by Upendra
Page#    11 Blog Entries  next>>
General Travel
Jul 25 2016 (20:31)   12124/Deccan Queen

Upendra   12 blog posts
Entry# 1941420            Tags   Past Edits
Her Highness Deccan Queen came back to her original look.......!!
General Travel
Jul 12 2016 (22:46)   12124/Deccan Queen

Upendra   12 blog posts
Entry# 1927725            Tags   Past Edits
Yesterday it was 12124 Deccan Queen who got delayed by more than 1 hour and her sister Pragati overtook her .........
Today it's 12128 Intercity who is running almost 2 hour late and same thing, her sister Indrayani overtook her......!!

Jul 12 2016 (22:59)
Success comes with love Thank you 12650*^~   15739 blog posts   4387 correct pred (85% accurate)
Re# 1927725-1            Tags   Past Edits
Why was DQ late?

Jul 13 2016 (09:41)
Upendra   12 blog posts
Re# 1927725-2            Tags   Past Edits
There was issue with overhead wire between Neral and Shelu
DQ was standing for 45 minutes before Neral......!!
General Travel
Jul 09 2016 (17:49)   12124/Deccan Queen

Upendra   12 blog posts
Entry# 1923863            Tags   Past Edits
07-July-2016 12123 Deccan Queen departed from Mumbai CST at 19:40 and reached Pune at 23:10........delayed by 3 hours almost......!!
★★★  Travelogue
May 26 2016 (20:03)   12124/Deccan Queen | PUNE/Pune Junction (6 PFs) | KYN/WCAM-2P/21862

Soumitra Chawathe*^~   30227 blog posts   98200 correct pred (72% accurate)
Entry# 1865583            Tags   Past Edits
Its my pleasure to share with you my maiden journey on-board 12124 ( /pnr/post/1857982 ) since my joining the IRI. The
trip was special in many ways – Though I’ve travelled umpteen number of times since childhood, I was just a traveller and not a railfan. Since my joining of IRI in 2012, train journeys are not just journeys but a process of learning, observations and recalling rail-knowledge which I have gathered, courtesy this wonderful website. My long cherished dream ultimately realised with me and my better half taking this train from PUNE-DR. This journey was special in many ways and boy, I was thrilled!!
22nd May 2016 dawned like no other, but I was all agog with excitement to be on-board the most prestigious train of my home zone. We reached station at 06.45 and entered through the booking office entrance, leading to the fag end of Mumbai end of PF-1. We were cheerfully welcomed by the Queen herself who was being shunted. We walked to our coach C2 which was CR 99153 was placed in the middle of the rake. Our seats were 74 and 75, the last seats on the 3-seat side. The exteriors, now wrapped in Maharashtra Tourism livery were gleaming. We climbed onboard and were left delighted. The interiors were simply pristine. The gangway had a red coloured carpet, some vintage CR posters hung on the sideways while eye-catching scenery posters hung on the either ends. The washrooms were spotless and dry with everything perfectly in place. Train TT too was affixed on one side. DQ truly lives up to its name and the lofty ISO benchmark.
The clock struck 07.15 and our loco KYN WCAM-2P 21862 honked. Drifting past the pitlines and yard, the LP notched up aggressively as were cruised past Sangam Bridge and scurried past SVJR at 85-90 kmph, completing the daily ritual overtake of 11024 Sahyadri Express. The catering guys (CR’s Departmental Catering Service) soon appeared on the scene and took orders, the wide selection of menu being Veg. Cutlet, Omelette, Baked Beans on Toast, Cheese Sandwich, Cheese Toast, Chicken Cutlets, etc. We had to visit a temple later, hence we took Veg Cutlets and Cheese Sandwiches. TTE came and checked the tickets religiously, checking ID cards as well. Usually some TTEs here just tick off the chart and ticket and orally ask whether ID card is in possession or not. Nevertheless with formalities done, we tightened the seatbelts for the wonderful journey that lay ahead. We were running at MPS wherever permitted, blazing everything that came in our way. In the meanwhile, we crossed 99803 LNL-PUNE EMU and 12940 JP-PUNE SF Express all along. The MPS feast continued till MVL after which we slowed down. Thanks to full sectional clearance and great priority, we arrived on PF-2 of LNL at 08.10. On PF-1 was 22105 Indrayani “Indu” Express. The two sisters meet each other here daily in perfect coordination. We got the starter at 08.13 and exited. By now, the breakfast was served which was really delectable. We relished on the same and washed it down with hot coffee. We arrived at KAD at 08.17 for mandatory brake testing, a tradition since ages.
After the go-ahead, the mighty and enchanting Bor Ghats beckoned us to ride downhill. Everything was pretty smooth and we already begun our descent, striding through numerous tunnels en-route. We had a touch and go halt at Monkey Hill at 08.27 and Go-ahead at Thakurwadi Cabin at 08.35. Everything was perfect when at around 08.50, we were stopped in middle of nowhere, at KM post 109/05. We were on the middle line and two lines surrounded us on either sides. The line on the left was the line towards KJT, via Nagnath Cabin, while the line towards our right was the line bound to PUNE. No-one bothered much for initial 15 minutes, thinking it to be an unscheduled halt. But as the clock ticked, the question mark on the faces became more intense and restlessness grew. It was 45 minutes and no chances of movement. Many passengers had got down for a stroll, while a few were peeping out from the door. The rumours had reached a peak, some saying brake failure, some saying track fracture/damage while some saying landslide. In the meanwhile, 11007 Deccan Express crossed us, followed by 11031 Udyan Express. Our younger sister, 12126 Pragati Express overtook us, their passengers shocked to see us standing there, followed by 17222 COA-LTT with our passengers powerlessly watching and resigning to the fate. 2 triplets of WAG-7 bankers too returned light to KJT. The TTE came and informed the passengers that a boulder had rolled off to the tracks, hit the loco and damaged the brake pipe. He then requested for mobile phone. Being surrounded deep in mountainous area, there were issues with mobile networks and nearly 90% of passengers did not have access to mobile. One passenger fortunately had a working mobile and the TTE alerted the CR control room. The TTE informed that the controllers had asked Sahyadri Expess to halt beside our train and those who wished to proceed ahead may board Sahyadri and proceed. He also informed that that a rescue loco was already on its way. Minutes later, Sahyadri came and stopped beside our train. Many people jumped from ours and boarded Sahyadri. In about 5 minutes, Sahyadri departed. What a sight it was!! The train which gets overtaken by ours daily, now had a rare chance to overtake us!! The delay had now mounted to over 1 hour and it was past 10 already. Realising the hunger and thirst, the pantry guys made hay while the sun shone, with many passengers including us opting for another round of tea and snacks. At around 10.15, we got a backward jerk that sent cheers amongst the crowd. The rescue loco, a weird and wacky #offlink CNB WAG-7 had arrived and had attached itself to take charge of the train. The loco seemed fit and raring to go and why not, not even in its wildest dreams it could have thought that it would get to haul DQ one day!!
At 10.25, amidst cries of “Ganpati Bappa Morya”, we had finally departed, after a 1 hr 40 min ordeal cum adventure. The descent was ongoing at a slow and steady pace and the LPs seemed extra careful now. We skipped RF heaven PDI at 10.45 and slowed down further. We crawled all the way to KJT where we were received on PF-2, with the local passengers, vendors awe-struck to see DQ stopping by and running so late. 11029 CSTM-KOP Koyna Express was on PF-1 for banker attachment. Within 5-10 minutes, CSTM-KJT Fast local arrived on PF-2A. We were closely followed by 17032 HYB-CSTM Express which arrived on PF-3 shortly. The wait at KJT seemed endless, the passengers got down for breather. The starter was still red and no one had an idea when it would turn amber. The 95120 KJT-CSTM Fast Local departed at 11.19. At 11.25, 17032 was given starter, with us still waiting for our turn. At 11.30, controllers showed us some mercy and gave us the starter after which we departed. The situation post KJT improved and we got good clearance. There were not much slowdowns, except for TSR/PSR along the way. We had a good run till KYN, where we halted on PF-6 for 2 minutes for signal at 12.20.
Post KYN, the run to TNA again was good by “that day’s standards”, though not MPS, speed was decent. The run from KYN-TNA was completed in about 25 minutes and we skipped TNA at moderate speed at 12.55, finally something to cheer to see an important station being skipped. Some passengers already stood near the door to ready themselves to alight at DR, causing discomfort to those sitting and wanting to go to washrooms. I informed a couple of them that it was still half an hour atleast for DR, but they did not pay any heed to me. The Waggie literally unleashed itself for the penultimate run post TNA-KYN and tried best to cover delay, hitting MPS. The run from TNA-DR was covered in 20 minutes. Finally at 13.15, we had a breezing entry on PF-6 at DR, late by over 3 hours, having overtaken by 5 trains!! What a voyage it was, this avatar of DQ will be remembered and cherished for a lifetime!! Thanks for reading!! :-)
Pic-1: Train Board
Pic-2: Interiors
Pic-3: TT affixed inside coaches
Pic-4: The rail poster
Pic-5: The beginning of the long wait
Pic-6: Sahyadri Express to our rescue
Pic-7 & 8: Another endless wait at KJT
Pic-9: Departing KYN

8 posts are hidden.

Jul 02 2016 (16:01)
Upendra   12 blog posts
Re# 1865583-9            Tags   Past Edits
A incidence with 11010 Sinhagad Express:
13-July-2014 an early morning 11010 Sinhagad Express started it's journey towards Mumbai, sharp at 06:05 AM, after taking all scheduled halts 11010 reached MPS after CCH with 2-3 slowdowns till Kamshet around 07:15 AM just after MVL suddenly a hard breaking sound heard with 11010 stopping all of sudden, we were having no idea what happened, hoping train will start moving in 5-10 minutes but after 15 minutes a breaking news came that track is damaged ahead with one small piece separated from it (it was really breaking news :-) ).
were very fortunate, as one of the worker seen the broken railway track and immediately reported to MVL & LNL and controllers took a prompt action to aware Loco Pilot on time and a mishap was averted
Now the restoration activities came in to force and Pune/Mumbai division of CR started emergency repair of track which took almost 1 hour to complete. It was 08:25 when our train started moving and crawled to Lonavala. It was 08:40 when our train departed from LNL and after completing all halt formalities of Bhor Ghat it reached KJT around 09:25 and departed at 09:30 after one local train reached EMU platform.
It was 10:15 when Sinhagad Express reached KYN and kept on hold (guess why?). Her Highness Deccan Queen was closely following Sinhagad Express and finally overtook us at Kalyan, soon after DQ crossed KYN, Sinhagad Express got clearance and started heading towards Mumbai CST and finally reached Dadar at 11:10. We alighted at Dadar happily giving blessings to to that worker of CR who saved us from mishap.

2 posts are hidden.
General Travel
Jun 18 2016 (22:44)   12125/Pragati Express

Upendra   12 blog posts
Entry# 1899965            Tags   Past Edits
Pragati Express and Indrayani Express were introduced in 1989.
click here
Page#    11 Blog Entries  next>>

ARP (Advanced Reservation Period) Calculator

Reservations Open Today @ 8am for:
Trains with ARP 10 Dep on: Fri Aug 4
Trains with ARP 15 Dep on: Wed Aug 9
Trains with ARP 30 Dep on: Thu Aug 24
Trains with ARP 120 Dep on: Wed Nov 22


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.