NEC clogged somewhere around Baltimore

[MARC Rider]

My evening ride home on MARC has been stalled just north of West Baltimore for about 30 minutes. Conductor says it's a signal problem. The train behind us stopedal next to us an then got to move ahead of us. We're now on the move again, but slowly.

Wonder what happened (in detail)?

 

[Ryan]

We are moving on time out of WAS, hopefully we make it to Odenton without delay.

Betty mentioned some delays up near WIL as well.

 

[Slayer Essence]

I'm on train 85 and between Aberdeen and Baltimore we've come to a halt. Have been crawling / stopped for what seems like 30 minutes. Conductor said there is catenary power issues going into Baltimore.

 

[MARC Rider]

Just a follow-up. When I finally got into Baltimore, here's what the departure board looked like. You don't usually see that sort of thing in Baltimore too often.

 

[Thirdrail7]

My evening ride home on MARC has been stalled just north of West Baltimore for about 30 minutes. Conductor says it's a signal problem. The train behind us stopedal next to us an then got to move ahead of us. We're now on the move again, but slowly.

Wonder what happened (in detail)?

You had a 1-2-3 punch on this. CETC basically shut down in rush hour and had to be rebooted. While this occurs, trains can basically make it as far as the nearest interlocking until it runs out of railroad.

So, most traffic halted. This, of course causes congestion, late turns, etc.

If that isn't enough, there is a track project north between Gunpow and Edgewood, resulting in single tracking. As such, you have a bunch of late trains converging on single track territory at once.

The additional insult was single track operation in another section between Perryville and Wilmington.

 

[Acela150]

My evening ride home on MARC has been stalled just north of West Baltimore for about 30 minutes. Conductor says it's a signal problem. The train behind us stopedal next to us an then got to move ahead of us. We're now on the move again, but slowly.

Wonder what happened (in detail)?

You had a 1-2-3 punch on this. CETC basically shut down in rush hour and had to be rebooted. While this occurs, trains can basically make it as far as the nearest interlocking until it runs out of railroad.

So, most traffic halted. This, of course causes congestion, late turns, etc.

If that isn't enough, there is a track project north between Gunpow and Edgewood, resulting in single tracking. As such, you have a bunch of late trains converging on single track territory at once.

The additional insult was single track operation in another section between Perryville and Wilmington.

That's a nasty 1-2-3 punch.. Real nasty.

 

[Thirdrail7]

My evening ride home on MARC has been stalled just north of West Baltimore for about 30 minutes. Conductor says it's a signal problem. The train behind us stopedal next to us an then got to move ahead of us. We're now on the move again, but slowly.

Wonder what happened (in detail)?

You had a 1-2-3 punch on this. CETC basically shut down in rush hour and had to be rebooted. While this occurs, trains can basically make it as far as the nearest interlocking until it runs out of railroad.

So, most traffic halted. This, of course causes congestion, late turns, etc.

If that isn't enough, there is a track project north between Gunpow and Edgewood, resulting in single tracking. As such, you have a bunch of late trains converging on single track territory at once.

The additional insult was single track operation in another section between Perryville and Wilmington.

That's a nasty 1-2-3 punch.. Real nasty.

Look at the bright side Acela150: At least the automatics still worked! :giggle: