RailForum.com
TrainWeb.com

RAILforum Post A Reply
my profile | directory login | register | search | faq | forum home

» RAILforum » Passenger Trains » Amtrak » what is going on with the capitol ltd » Post A Reply

Post A Reply
Login Name:
Password:
Message Icon: Icon 1     Icon 2     Icon 3     Icon 4     Icon 5     Icon 6     Icon 7    
Icon 8     Icon 9     Icon 10     Icon 11     Icon 12     Icon 13     Icon 14    
Message:

HTML is not enabled.
UBB Code™ is enabled.

 

Instant Graemlins Instant UBB Code™
Smile   Frown   Embarrassed   Big Grin   Wink   Razz  
Cool   Roll Eyes   Mad   Eek!   Confused    
Insert URL Hyperlink - UBB Code™   Insert Email Address - UBB Code™
Bold - UBB Code™   Italics - UBB Code™
Quote - UBB Code™   Code Tag - UBB Code™
List Start - UBB Code™   List Item - UBB Code™
List End - UBB Code™   Image - UBB Code™

What is UBB Code™?
Options


Disable Graemlins in this post.


 


T O P I C     R E V I E W
sojourner
Member # 3134
 - posted
The Amtrak website says train #29 will be over 13 hours late to Chicago. Does anyone know what the problem is and whether I should be worried about connections later this spring?
 
notelvis
Member # 3071
 - posted
I'll be on number 29 April 11 making a same day connection in Chicago to number 3.

I didn't think I had anything to worry about until now.
 
cdnfan32
Member # 4674
 - posted
In June our family is taking a long trip from Grand Forks to Chicago and then the Capitol Limited to Washington and a final short connection to Wilmington, Delaware for my wife's parents' 50th wedding anniversary celebration. I've been monitoring the Capitol Limited's performance since I got worried about making the connection in Washington and I can tell you that in the last 30 days, arrival in Washington has been an average of about 4 and half hours late (although the one time it was 18 hours late kind of skews the average).

I posted a question here about this some weeks ago and most folks figured it was weather related; now I'm worried it's more of a chronic problem. If we wander into my in-laws' anniversary party just as it's wrapping up, my name will be "Mud" and it'll be the last time I get to design the family trip itinerary!
 
MDRR
Member # 2992
 - posted
I'm not totally sure, but do know #30 (31) is running 5-6 hours late due to NS derailment, so am guessing #29 (30) was probably majorly impacted due to same?
 
cdnfan32
Member # 4674
 - posted
Do you know where the NS derailment was and when?
Thx
 
MDRR
Member # 2992
 - posted
No not really, just received info from amtrak this AM regarding what I posted and was estimated to be in Pgh approx 5-6 hours late.
So, between Cle and Pgh maybe?
 
Liberty Limited
Member # 4300
 - posted
CSX derailed 40 miles East of Pittsburgh, apparently at a switch. I was aboard 30(30) which had encountered its own misfortunes before and after we boarded (engine HEP issues, an apparent crossing accident), then slowed to creep through the derailment site, whose evidence was just a disconnected switch, and a 300' section of newly laid track that had yet to be tamped.

Riding 30(30) from PGH to WAS, we passed both 29(30) (very very late) near PGH and 29(31)(about on time) near Martinsburg.
 
sojourner
Member # 3134
 - posted
Thank you for the info. It sounds like it won't be an ongoing problem, thank goodness!

Hope you enjoyed your travels regardless, Liberty Limited
 
sojourner
Member # 3134
 - posted
As I mentioned in another strand, I just spoke with an Amtrak person who had phoned me about a slight schedule change (unrelated to LSL/Capitol Ltd). She checked and told me that these (continuing) horrendous delays on the Capitol Ltd in the past few weeks are due to track work due to end April 12. So . . . I hope she is right!
 



Contact Us | Home Page

Powered by Infopop Corporation
UBB.classic™ 6.7.2




Copyright © 2007-2016 TrainWeb, Inc. Top of Page|TrainWeb|About Us|Advertise With Us|Contact Us