Passenger Trains > Today's Crescent delays

#20 lost 58" Meridian-Tuscaloosa and #19 35" Birmingham-Tuscaloosa. #19 was actually OT out of B'ham. I could just barely hear the DS talking on a distant tower about a meet towards Bessemer that must have held him up. Not sure what happened to #20 Meridian-Crabtree, but can tell you there was an awkward 3-way meet at Crabtree. NS #314 pulled into the siding there first and #19 pulled in facing him; then #20 proceed north on the main. then #19 back out and proceeded south. I think #20 lost about 15 min. and #19 about 20 min.
Andy

20 was nearly 4 hours late this morning going into Charlottesvlle. N/S us on it's way to being a 'worst performer' with major railroads. This used to be our best on-time performance route.

There is nothing rare or unusual about any of these delays-just because they are starting to get attention doesn't make them unusual. 20 Almost ALWAYS loses an hour on this same sector account a meet with 19 anyway. Its VERY common to have backup meets between 19/20 like you describe and has been for over 15 years. Google "Crescent Meets in Tuscaloosa" on Youtube and find years of videos of the same reverse move meets between 19/20.

The only thing unusual about the route are the actual delays being caused by heavy traffic and freights. The hour lost between MEI and TCL has been that way for a long time, its just that typical padding is usually enough to fix the train..not anymore with the heavier traffic and delays caused EAST of BHM.

20 lost time right out side Meridian due to NS train going on the law on the mainline. Apparently they were trying to get it into the yard at Meridian and didn't make it. The type meet you mention is a normal move right now. Yes, it has been going on for many years. At one time, when the trains were running closer on time, they would meet at Bryant, which is the yard lead RR north of the station. One of the trains would have a back up move. Apparently, Autorouter doesn't like of know of this move. Actually, 19 did not loose time at the meet yesterday, it lost time later.

NS is slowly getting like CN.



Edited 1 time(s). Last edit at 11/23/17 11:06 by joemvcnj.

Amtrak-P42 Wrote:
-------------------------------------------------------
> There is nothing rare or unusual about any of
> these delays-just because they are starting to get
> attention doesn't make them unusual. 20 Almost
> ALWAYS loses an hour on this same sector account a
> meet with 19 anyway. Its VERY common to have
> backup meets between 19/20 like you describe and
> has been for over 15 years. Google "Crescent Meets
> in Tuscaloosa" on Youtube and find years of videos
> of the same reverse move meets between 19/20.
>
> The only thing unusual about the route are the
> actual delays being caused by heavy traffic and
> freights. The hour lost between MEI and TCL has
> been that way for a long time, its just that
> typical padding is usually enough to fix the
> train..not anymore with the heavier traffic and
> delays caused EAST of BHM.

Whatever the reason, padding or not(every ld route has padding built in)NS always treated 19/20 well, especially 20. Within the last year and a half the on time performance of 20 has gone from something like 85% to a staggering 10%! Don't tell me freight interference has gone up that much where now the norm is for 20 to be 3 - 4 hours late on an almost daily basis?

chess Wrote:
-------------------------------------------------------
> Amtrak-P42 Wrote:
> --------------------------------------------------
> -----
> > There is nothing rare or unusual about any of
> > these delays-just because they are starting to
> get
> > attention doesn't make them unusual. 20 Almost
> > ALWAYS loses an hour on this same sector account
> a
> > meet with 19 anyway. Its VERY common to have
> > backup meets between 19/20 like you describe
> and
> > has been for over 15 years. Google "Crescent
> Meets
> > in Tuscaloosa" on Youtube and find years of
> videos
> > of the same reverse move meets between 19/20.
> >
> > The only thing unusual about the route are the
> > actual delays being caused by heavy traffic and
> > freights. The hour lost between MEI and TCL has
> > been that way for a long time, its just that
> > typical padding is usually enough to fix the
> > train..not anymore with the heavier traffic and
> > delays caused EAST of BHM.
>
> Whatever the reason, padding or not(every ld route
> has padding built in)NS always treated 19/20 well,
> especially 20. Within the last year and a half the
> on time performance of 20 has gone from something
> like 85% to a staggering 10%! Don't tell me
> freight interference has gone up that much where
> now the norm is for 20 to be 3 - 4 hours late on
> an almost daily basis?

Yes. It has. If you notice 19-20 are much more ontime during weekends and holidays. And it's more like 1-2.5 regularly.