NER dwell times at NYP

[daybeers]

I'm looking at planning a trip down to DC in early November, and looking at the return trips, I'm trying to return to leave WAS as late as possible and still be able to connect with a train to get me back to HFD, so that would be NER #132.

The only thing that confuses me is the dwell time in NYP is 44 minutes, when it's usually around 15. I see that #140 does this also. Is this just for slot timing? #96 waits 37 minutes, but that makes sense to me, since it's coming from VA, so it could have gotten delayed.

 

[Acela150]

Padding. That’s all that is.

 

[daybeers]

Padding. That’s all that is.

It's just a hell of a lot of padding. Why do a few of them have a lot more than the rest?

 

[CCC1007]

Padding. That’s all that is.

It's just a hell of a lot of padding. Why do a few of them have a lot more than the rest?

If these are northbound trains, I would guess that Metro North May be the culprit, as lining them up for the slots across their territory may need a longer dwell time.

 

[Anderson]

Without looking at the timetables, there are a few trains that get held for "sweet spot" departures (e.g. there's one SB Regional I recall having about an hour at WAS so it can tap into rush hour traffic).

 

[railiner]

I am guessing that some of these dwell intervals, besides rail traffic related 'slots', may be an effort to have certain routes depart NYP on a "memory" schedule--the same time on the clock as others throughout the day...

 

[bratkinson]

I'm looking at planning a trip down to DC in early November, and looking at the return trips, I'm trying to return to leave WAS as late as possible and still be able to connect with a train to get me back to HFD, so that would be NER #132.

The only thing that confuses me is the dwell time in NYP is 44 minutes, when it's usually around 15. I see that #140 does this also. Is this just for slot timing? #96 waits 37 minutes, but that makes sense to me, since it's coming from VA, so it could have gotten delayed.

Train #148. Since June 9, it departs WAS at 4:55P and arrives HFD 11:46P. It's a single seat ride all the way...no shuttle NHV-HFD. I've ridden it multiple times two stops further, to WNL (Windsor Locks) where there's free parking (I live in MA). In fact, I'll be on that very train NYP-WNL next Tuesday after a day joyriding the LIRR getting new-to-me mileage.

 

[Acela150]

Padding. That’s all that is.

It's just a hell of a lot of padding. Why do a few of them have a lot more than the rest?

If these are northbound trains, I would guess that Metro North May be the culprit, as lining them up for the slots across their territory may need a longer dwell time.

That's another reason that I totally forgot about.

 

[daybeers]

I'm looking at planning a trip down to DC in early November, and looking at the return trips, I'm trying to return to leave WAS as late as possible and still be able to connect with a train to get me back to HFD, so that would be NER #132.

The only thing that confuses me is the dwell time in NYP is 44 minutes, when it's usually around 15. I see that #140 does this also. Is this just for slot timing? #96 waits 37 minutes, but that makes sense to me, since it's coming from VA, so it could have gotten delayed.

Train #148. Since June 9, it departs WAS at 4:55P and arrives HFD 11:46P. It's a single seat ride all the way...no shuttle NHV-HFD. I've ridden it multiple times two stops further, to WNL (Windsor Locks) where there's free parking (I live in MA). In fact, I'll be on that very train NYP-WNL next Tuesday after a day joyriding the LIRR getting new-to-me mileage.

I'd love to take 148, but it only runs Monday-Friday. I've actually taken that train numerous times, but that was before the time change back in June.

 

[bratkinson]

I'm looking at planning a trip down to DC in early November, and looking at the return trips, I'm trying to return to leave WAS as late as possible and still be able to connect with a train to get me back to HFD, so that would be NER #132.

The only thing that confuses me is the dwell time in NYP is 44 minutes, when it's usually around 15. I see that #140 does this also. Is this just for slot timing? #96 waits 37 minutes, but that makes sense to me, since it's coming from VA, so it could have gotten delayed.

Train #148. Since June 9, it departs WAS at 4:55P and arrives HFD 11:46P. It's a single seat ride all the way...no shuttle NHV-HFD. I've ridden it multiple times two stops further, to WNL (Windsor Locks) where there's free parking (I live in MA). In fact, I'll be on that very train NYP-WNL next Tuesday after a day joyriding the LIRR getting new-to-me mileage.

I'd love to take 148, but it only runs Monday-Friday. I've actually taken that train numerous times, but that was before the time change back in June.

I hadn't realized you were looking to ride on a Sunday. In looking at the current NEC timetable, you could leave WAS 30 minutes later on Acela 2258 which arrives NHV about 30 minutes before 132 does. You'd have to wait there to grab the same shuttle #432 to HFD.

I was thinking perhaps the new CTRail operation had a later train from NHV, unfortunately, they don't.

 

[daybeers]

I'm looking at planning a trip down to DC in early November, and looking at the return trips, I'm trying to return to leave WAS as late as possible and still be able to connect with a train to get me back to HFD, so that would be NER #132.

The only thing that confuses me is the dwell time in NYP is 44 minutes, when it's usually around 15. I see that #140 does this also. Is this just for slot timing? #96 waits 37 minutes, but that makes sense to me, since it's coming from VA, so it could have gotten delayed.

Train #148. Since June 9, it departs WAS at 4:55P and arrives HFD 11:46P. It's a single seat ride all the way...no shuttle NHV-HFD. I've ridden it multiple times two stops further, to WNL (Windsor Locks) where there's free parking (I live in MA). In fact, I'll be on that very train NYP-WNL next Tuesday after a day joyriding the LIRR getting new-to-me mileage.

I'd love to take 148, but it only runs Monday-Friday. I've actually taken that train numerous times, but that was before the time change back in June.

I hadn't realized you were looking to ride on a Sunday. In looking at the current NEC timetable, you could leave WAS 30 minutes later on Acela 2258 which arrives NHV about 30 minutes before 132 does. You'd have to wait there to grab the same shuttle #432 to HFD.

I was thinking perhaps the new CTRail operation had a later train from NHV, unfortunately, they don't.

You're right, I never specified what day, oops! Sorry about that! Yeah, there isn't much point to taking 2258 if I have to wait for 432 anyway. I would just like as much time in DC as possible, but I need to be back early Monday morning (and no, I can't take #190. I need to be somewhere mid-morning. I have taken that before though: an interesting experience!) I would take NER #166, which leaves WAS at 5:17P and arrives NHV 10:41P, but there aren't any train or bus connections, and Uber or Lyft would be ~$30/person, since I'm going with a friend, so that might be an option, but probably not.

 

[bratkinson]

PLAN C:

If you're OK riding coach or business class overnight, take #66 WAS-NHV (10:10PM - 4:40AM) then catch the first CTRail #6400 at 8:10 AM. 3.5 hrs in what will likely be a deserted NHV station is not appealing, in my mind. The benches are uncomfortable to sit on. PLAN D would be to ride #66 a couple stops longer, double back to NHV in time to catch CTRail. That would keep you safe and comfortable for those 3.5 hours.

I finally had to give up on #66. I'd take it WAS-BOS then kill time in BOS before catching #449 to SPG. I've concluded I'm just too old to sit up all night which is strange, my last job before retiring was 3rd shift at CSX Intermodal.

CORRECTION!!!

It just dawned on me that 10:10PM Sunday night goes into Monday morning, so the first CTRail to HFD you can make is #4452 at 6:35 AM. Not so bad a layover after all. In my experience, #66 is rarely late north (east) of NYP due to the long layover there...it's a good time for sleeping while not moving!