Commuter train interference by Utica, NY?

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.

Cal

Engineer
Joined
Jan 23, 2021
Messages
4,547
Location
Socal
From Amtrak Alerts Twitter:
"Empire Service Train 283 is currently operating approx. 30min late due to earlier commuter train interference east of Utica (UCA)."

I'm sorry, but am I right in thinking that there is no commuter rail service east of Utica (or even anywhere north of Poughekeepsie)?
 
When I drive on the Cross Bronx Expwy I will travel East or West on a road which is most definitely a North-South route (I-95) People often just look at a segment or a part of a route without seeing it in totality. My Southbound train out of NYP to WAS better go West for a bit and get to NJ
 
When I drive on the Cross Bronx Expwy I will travel East or West on a road which is most definitely a North-South route (I-95) People often just look at a segment or a part of a route without seeing it in totality. My Southbound train out of NYP to WAS better go West for a bit and get to NJ
Except in a few sections on the NEC, your southbound train is really heading west, per RR jargon. ;) Since I'm not sure where the sections are that are referred to as north/south (around Philly, I believe), I usually will say south/west or north/east when reporting the direction of a train.
 
Utica is railroad direction west of MNRR territory. Geographically it is more like northwest.

Trains from New York to Albany, even though they travel north, are numbered as if they are traveling west, because Albany is railroad direction west from New York, being part of the Water Level Route to Chicago, which is an east-west route.
 
Yes. The time was lost on MNRR territory due to interference by MNRR commuter trains. Since that is east of Utica, there is nothing wrong with that statement.
May not be wrong, but it is confusing, as Utica is 164 miles from the start of MNRR serivce and territory in Poughkeepsie!
 
Sure, clearly Boston is pretty far to the East as well as North, and along the Ct shore is more East West than North South, but like the example JIS gave is along a N/S rr route and it would probably be confusing as heck to include more than the four cardinal directions on a schedule or official use. Talking to someone about what a train is doing is different, often, if someone calls me when I'm going to a hockey meeting in Syracuse or Buffalo, I'll say something like "heading West from Albany, see you in a few hours."
 
May not be wrong, but it is confusing, as Utica is 164 miles from the start of MNRR serivce and territory in Poughkeepsie!
People who know that much ought not to get confused, ;) and most people neither know that, nor really worry about the detail of why their train got delayed. They just are upset.
 
People who know that much ought not to get confused, ;) and most people neither know that, nor really worry about the detail of why their train got delayed. They just are upset.
Might as well be correct in who's to blame for the delay, though, ex. due to earlier Metro-North commuter train interferance south of Poughkeepsie. Maybe when the tweet when out, the train was in Utica, but it could've also mentioned that, ex. is currently operating approx. 30 min late leaving Utica due to earlier Metro-North commuter train interferance south of Poughkeepsie.

But you're right, most would just think 'oh, just another Amtrak delay. Why'd we give them money again?'
 
Might as well be correct in who's to blame for the delay, though, ex. due to earlier Metro-North commuter train interferance south of Poughkeepsie. Maybe when the tweet when out, the train was in Utica, but it could've also mentioned that, ex. is currently operating approx. 30 min late leaving Utica due to earlier Metro-North commuter train interferance south of Poughkeepsie.

But you're right, most would just think 'oh, just another Amtrak delay. Why'd we give them money again?'
It seems to me that Amtrak intentionally tries to be non-specific in attributing delays. It's probably to avoid finger-pointing fights and maintain reasonably good relationships with host RRs.
 
It seems to me that Amtrak intentionally tries to be non-specific in attributing delays. It's probably to avoid finger-pointing fights and maintain reasonably good relationships with host RRs.
When Amtrak says it was due to commuter interference, one can rest assured that the delay was charged to MNRR and will show up in the host performance statistics report which Amtrak publishes each month and reports back to FRA and Congress periodically..
 
It seems to me that Amtrak intentionally tries to be non-specific in attributing delays. It's probably to avoid finger-pointing fights and maintain reasonably good relationships with host RRs.
Oh yes, because Amtrak's relationships with host RRs are so strong, definitely two-way streets 🥴😉
 
Oh yes, because Amtrak's relationships with host RRs are so strong, definitely two-way streets 🥴😉
Well I believe NS (or was it CSX) had a hissy-fit when Amtrak called them out by name on Twitter before, so they no longer use railroad names to avoid that.

Nice to know that railroads really are toddlers.
 
We are looking at a Twitter alert meant to give a quick message to people with an interest about what is going on with a train. It is not a press release or a formal report, nor should it try to be. Just a few lines that tell passengers or others who actually need to know what's up with a train. They have no reason to cater to curiosity seekers.
 
We are looking at a Twitter alert meant to give a quick message to people with an interest about what is going on with a train. It is not a press release or a formal report, nor should it try to be. Just a few lines that tell passengers or others who actually need to know what's up with a train. They have no reason to cater to curiosity seekers.
But giving more accurate information is always helpful either way.
 
But giving more accurate information is always helpful either way.

Not necessarily. To the person who is boarding at Utica, what “more accurate” information would be helpful to them?

Putting a ton of detail won’t fit in a tweet, and even if it did, most folks wouldn’t read it anyway.

“Train 123 is running 33 minutes late because of a meet at milepost 567.4 of the Spoonerville Subdivision with freight train ABX-PHT43 which was running 35 mph due to a speed restriction related to special equipment in its consist, which cost the train 26 minutes; and then further delayed running on approach signals near CP Junction just outside the Albany station.”

Or, they could say “Train 123 is running approximately 30 minutes late due to earlier freight train interference east of Utica.”

How is the first one more helpful to the average person?
 
Back
Top