#51 (5/23) late due to bridge fire?

Amtrak Unlimited Discussion Forum

Help Support Amtrak Unlimited Discussion Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Status
Not open for further replies.
Why not bring the Cardinal south from DC on NS to Lynchburg, then do a reversing move

on the wye and go West on CSX to CliftonForge and eliminate the BBRR mess. OR as been previously mentioned, NS thru Roanoke and then back to the western edge of West VA.?
 
Last edited by a moderator:
I saw the cardinal 50 Sunday morning at 4:45 PM make its regular stop in Maysville Kentucky. Buckingham branch Railroad who services the tracks through Staunton, Virginia confirmed there was a fire but could not give out details as it is still under criminal investigation. They said that Amtrak had the option to wait until 11:30 PM that Friday night for it to be repaired (and we could've got through) but Amtrak made the .decision that they didn't want to wait. I was surprised to find out that Amtrak is actually owned by the US government
 
Amtrak did not have the equipment to send out #50 on Saturday night for an overnight run to NYP.
#50 did indeed go out. It was listed as "disruption" almost immediately (if not sooner). As I said earlier it showed up on "Track a Train" as having passed Dyer and I might have seen it past Lafayette. Linda T quoted a news article saying that it was turned in IND. But I'm still curious, did it go back from IND on Sunday as the Hoosier State, sleeper included?
Actually, I was reporting what Amtrak's 1-800-USA-RAIL said when I called on Saturday. They said Saturday's Cardinal #50 was going to terminate at IND. Since I'm riding on Wednesday I called today to see the status and they said 50 would run its full run starting Wednesday, and I reconfirmed that Saturday's train #50 turned at IND, and they said yes it did. I don't know why it would show up at MAY based on my conversation with reservations. Go figure.
 
I saw the cardinal 50 Sunday morning at 4:45 PM make its regular stop in Maysville Kentucky. Buckingham branch Railroad who services the tracks through Staunton, Virginia confirmed there was a fire but could not give out details as it is still under criminal investigation. They said that Amtrak had the option to wait until 11:30 PM that Friday night for it to be repaired (and we could've got through) but Amtrak made the .decision that they didn't want to wait. I was surprised to find out that Amtrak is actually owned by the US government
Not sure what you saw go through MAY on Sunday morning, but the Huntington crew yesterday confirmed that the Sat-Sun 50 was terminated in IND (as USA-RAIL said). According to the crew the fire was at Craigsville, and they've heard anything from one to three ties were on fire, not the great conflagration that many of us (at least I) imagined when USA-RAIL said "a major fire." The 50 got across on Friday, the 51 was stopped, 51 backed all the way from STA to CVS. I didn't think about things like no headlight going through tunnels, backing across roads, around bends that you can't see around... that was a major operation in itself to back the train 30 some miles. And yeah, I talked to the guy who did it. I'm easily amazed, but I think the HUN crew did a great job getting the train back to CVS.
 
Last edited by a moderator:
... I certainly wouldn't recommend the Cardinal, which is one of Amtrak's most frustrating routes (I also wouldn't recommend the Sunset Limited or the Empire Builder).
How so for the Cardinal?

Thanks
And the SL?? Considering it's usually early into LAX. Just the early hour is a drawback for me.
Again, 3 a week, though it does usually run early. Also, the freaking early hour, as you say.

I have found scheduling around a 3-a-week a nightmare. If anything goes wrong, the next train isn't for 2 days... maybe 3.
 
Status
Not open for further replies.
Back
Top