Barciur
OBS Chief
THanks. Will definitely post oneBarciur,
Would be interested in a connection report from you when you travel. Save travels!
THanks. Will definitely post oneBarciur,
Would be interested in a connection report from you when you travel. Save travels!
Odds are in your favor for making the connection, I think. The last time #49 missed #7 in CHI was on October 13th.Currently on #49 about 30 miles east of Elk Heart, IN. We were running about 2 hours behind schedule due to the track work issues in NYS. Now we are stopped in the Indiana "dead zone" and the conductor just announced we need to wait for a series of east bound freights to go by before we can resume our journey. My guess is based on the last week's track record of delays in this area that we will pull into CHI well over 3 hours late once again and maybe even later, as he said there is very heavy "congestion" up ahead. Arrgh. I hope I make my connection to today's #7
Good luck. The pattern in recent days appears to be random on which east or westbound CL/LSL gets through CHI-EKH ok and which do not.Now stopped again, just east of SOB, and again waiting for more freight traffic to pass by. No additional time given, but likely another 30-45 minutes. My window of opportunity is shrinking here.
Must have gotten around the slow freight train. He made it to CHI in time to take a leisurely stroll around Union Station before going to the waiting room for EB #7. #49(10/30) arrived at CHI at 1:09 PM, a mere 3 hours and 24 minutes late. Only lost 3 minutes between SOB to CHI, which is much better than #48(10/30) which took almost an additional 3 hours last night from CHI (dep 21 minutes late) to SOB (dep 3 hours and 5 minutes late).I hope I don't see another 2 hours worth of delays AFTER SOB, I won't make it at that rate. We finally are moving again--at 15 mph. A guy in a bicycle just went by us on a side road!!! The conductor says still much "congestion" up ahead, so not looking good.
:-((
Note: apparently NS decided to let us stay behind an extremely slow freight instead of let us go around as we had requested--thus the very slow pace!
Yup--A four hour delay while they hooked up three private cars and replaced an engine-now in MN, just 6 hours behind, with NO toilets operating in the forward sleepers--what an adventure!!!Last October runs. Does it get better in November? Destination results for the Thursday, October 30 departure CL and LSLs.. All departed on-time unless otherwise noted.
CL #29(10/30): arrived CHI 1 hour and 13 minutes late [dep TOL on-time]
LSL #49(10/30): arrived CHI 3 hours and 24 minutes late [dep ALB 5 minutes late, BUF 2 hours and 10 minutes late]
CL #30(10/30): dep CHI 34 minutes late, arrived WAS 1 hour and 57 minutes late [dep TOL 2 hours and 31 minutes late]
LSL #48(10/30): dep CHI 21 minutes late, arrived NYP 2 hours and 48 minutes late [dep SOB 3 hours and 5 minutes late]
While Montana Mike was worried about #49 reaching CHI in time for EB #7, no problem. #7(10/31) departed CHI 4 hours and 10 minutes late at 6:25 PM. Oh well.
The reports have some CLs with a diner and sightseer lounge car and others with just the cross country cafe car. With 4 consists, they may be running 1 or 2 with the diner/SSL configuration and the rest without. So far in November has #29 has arrived at Chicago more than 3 hours late twice with the latest being 3 hours and 38 minutes allowing >6 hours to turn the equipment around. It is possible that Amtrak will shift back to 3 consists and the full diner & SSL setup before November 18.I have read conflicting information about the temporary change in the consist of the Cap Limited (30) that was done to create another trainset. Amtrak's web site indicates that through 11/18/14, there will be no full diner or sightseer lounge on 30. I found another post elsewhere which indicated that Amtrak backtracked on the change and replaced the SSL. I'll be on 30 on 11/16.
Enter your email address to join: