• Noticed/Questioned Major Delays, Annulments, Reroutes

  • Discussion related to Amtrak also known as the National Railroad Passenger Corp.
Discussion related to Amtrak also known as the National Railroad Passenger Corp.

Moderators: GirlOnTheTrain, mtuandrew, Tadman

  by ThirdRail7
 
MBTA F40PH-2C 1050 wrote:
electricron wrote:
MBTA F40PH-2C 1050 wrote:
electricron wrote: I would simply state a 13 to 14 hour delay is one huge major delay....
How difficult would it had been for Amtrak to accommodate these passengers at the Richmond train station just two miles away?
And how would they accommodate these passengers to Richmond? I'm going to assume, you mean bring them to the nearest station? Walk them back 2 miles to the station on the trap rock and track structure??? When situations like this arise, Conductors and A.C.'s can not just empty a train, and walk psgr's back a mile to a station, it is unsafe and could be very dangerous, especially at dusk. I'm sure the crew didn't think it would be that long to get back underway, but communication sometimes takes a while to get a plan in place in the RR, TM's got to take to Chief TD's and then talk to the next person.......a wise, fatherly figure engineer taught me the greatest piece of knowledge since I have been on the RR..."take it slow, because when you rush, that is when sh*t happens and everything hits the fan"
They could have uncoupled the car with the brake problems from the front half of the train and taken those passengers in those cars to the station and come back using track 2 and coupled onto the cars in the last half of the train and taken them to the station, leaving the problem car at the scene. I'm not suggesting that's the only thing they could do, but it is one they could have done without placing passengers at risk. Per the news article I linked, deputy sheriffs had no problems reaching the train, so passengers shouldn't have had more problems reaching the same road or street where they parked their patrol cars, and could have risen a bus to the station. I'll admit that alternate may have placed passengers at risk, but not more so than the deputy sheriffs.

What the news article failed at was describing what Amtrak did to fix the damaged brakes and wheels for the problem car? Did Amtrak repair it where it was, replace the brakes, replace the car, etc?
But that is the job of local law enforcement and rescue crews, check up/rescue on situations in any kind of terrain. Got to remember that there are passengers of all ages on this train. MBTA has had to save/transfer Amtrak psgr's to our equipment and visa versa up here in MA/RI, and those kind of transfers can take almost 2 hours to complete depending on what the exact situation is, and is a last resort if rescue power can't be readied quickly enough. I don't know the territory down there, 1 or 2 main trks, but sounds like there was no rescue engine, or possibly no rescue crew available to man the rescue unit. I agree with your idea to uncouple and drag back the good half of the train, but obviously there was a variable that forced Amtrak not able to do that move. I'm assuming as well that this is CSX dispatched territory?? A rescue train can not just be summoned, and travel over CSX without proper paperwork and release forms, that takes time. Railroading is tough sometimes, it is easy to say "well why didn't they do this??" Most of the time, the easiest solution can't be done :wink:

I missed this. The variable is if you uncoupled the portion of the train south of the diner and ran away with it, what happens to the passengers that are in the cars north of the crippled diner? They are now stuck and without HEP since you took the engines. That's not a big issue if you could come up behind them with another engine, grab them and shove to RVR...which was the original plan. However, when you're holding a main on one of the busiest corridors in the east which is causing single track conditions, and the host railroad has a quite a few trains to run and can't commit to running a light engine and then shoving passengers on the only track left, that is a serious variable.

So, they made temporary repairs at the scene.
  by srock1028
 
David Benton wrote:Not suggesting they should have done this ,but could a locomotive drag a car with locked brakes ? .
Sure it could, expect bad flat spots and possible damage to the rail. Like you said, not a good idea to do so.
  by srock1028
 
David Benton wrote:Not suggesting they should have done this ,but could a locomotive drag a car with locked brakes ? .
Sure it could, expect bad flat spots and possible damage to the rail. Like you said, not a good idea to do so.
  by shlustig
 
Does anybody know why:

#'s 304, 305, 307 of the 12th all lost 3'00" to 4'45" between Dwight & Joliet?

and

#19 (11th) lost 9'00" between WAS & NOL??
  by ThirdRail7
 
shlustig wrote:Does anybody know why:

#'s 304, 305, 307 of the 12th all lost 3'00" to 4'45" between Dwight & Joliet?
Yet another grade crossing collision which shuts the tracks.
shlustig wrote: and

#19 (11th) lost 9'00" between WAS & NOL??
It was held in DC for disposition due to storms in the area. When it was released, NS instituted flash flood restrictions. It turned out to be a good thing since the storms brought down trees and debris. 19 was able to stop short of any trouble. However, once the tracks were clear, more flash flood restrictions were instituted.
  by JoeBas
 
Actually after havimg to do an engine change to diesel in Philly, 19 was held in WAS for folks being bustituted in from 30's problems, and had we left WAS on or close to on time we likely would gotten through VA before the skies opened. We then lost a couple more hours between ATL and ATN due to a freight going into emergency.
  by ThirdRail7
 
JoeBas wrote:Actually after havimg to do an engine change to diesel in Philly, 19 was held in WAS for folks being bustituted in from 30's problems, and had we left WAS on or close to on time we likely would gotten through VA before the skies opened. We then lost a couple more hours between ATL and ATN due to a freight going into emergency.

This is not really correct. They were contemplating letting 19 run away but NS already had problems below which is why the train was held. Additionally, the freight didn't have as much of an impact as the calendar day inspection that was performed on the engines at ATL which wouldn't have been needed if the train wasn't so late.
  by Dick H
 
Downeasters #683, #684, #685 and #686 all took
a hit of between one and two hours late today with
the PAR 40MPH speed restriction from Portland to
the NH/MA State Line. With the weather forecast
calling for low to mid-90's through Friday along the
Downeaster route, there could be several repeats
of todays' circumstances as the week progresses.
  by JoeBas
 
ThirdRail7 wrote:This is not really correct. They were contemplating letting 19 run away but NS already had problems below which is why the train was held.
Well seeing as how they held 97 as well, and we both left as SOON as the bus got there...
ThirdRail7 wrote:Additionally, the freight didn't have as much of an impact as the calendar day inspection that was performed on the engines at ATL which wouldn't have been needed if the train wasn't so late.
At least to me it sure didn't seem like we sat at ATL too too much longer than normal (scheduled stop 25 minutes, actual stop 52 minutes), though I may have been a little "late numb" at that point. But we sure did spend a whole lotta time sitting in the woods between ATL and ATN, and went from leaving ATL 7'11" down to 8'55" down at ATN, so you make the call... ;)
  by shlustig
 
Does anybody know why #50 (16th) eastbound Cardinal and #51 (17th) westbound Cardinal lost 5'00" and 4'00" respectively between CVS and Hinton?
  • 1
  • 92
  • 93
  • 94
  • 95
  • 96
  • 176