R
Richard McCormick
Guest
Looking at the Cardinal route map it appears that it's more southerly route seems to spare it from the freight traffic nightmare that seems to exist in the CLE-SOB corridor and which plagues both the 29 CL and 49 LSL on a daily basis.That route which takes it up through Cincinnati/Indianapolis to CHI has certainly had a much better OTP than either 29/CL or 49/LSL. For period from 8/5-9/1 the 51 Cardinal has averaged 82 minutes delays compared to 29/CL with 152 minutes and 49/LSL with a whopping 221 minutes.The largest delay for 29 was 383 minutes on 8/27 and for 49 it was a whopping 529 minutes on 8/22;both trains missed connection with both TE and SWC on those days leaving passengers bound for West coast stranded in CHI with no alternatives until the next day's trains. As you said, things may improve by late October but I need to make reservation now. The 51/ Cardinal works for my schedule as it leaves NYP on Friday 6:45 A.M. arriving CHI 10 A.M on Saturday.With 59/CONO not departing CHI until 8:05 P.M. it gives me some time for a quick tour around CHI before heading down to NOL. 59/CONO arrives NOL 3:32 P.M. giving me time to settle into my overnight hotel.Haven't been to NOL since the summer just before Katrina so it should be interesting to see how much has been done to rebuild NOL in the last decade or so. Looking forward to some chicory coffee and beignets at Cafe Du Monde and a dinner of crawfish with red beans and rice and maybe some good Jazz before hitting the sack for the night. Finally, head over to Union Station to catch 1/SL departing 9:00 A.M. Monday morning for my final destination Tucson/AZ arriving 6:45 P.M. Tuesday night. With 10 hour daytime layover in CHI and overnight stay in NOL this trip may seem a bit long but now being retired I have all the time that I need.Things should be better by October between WAS, NYP and CHI! The plan to ride the Crescent to NOL is a good one as you say, but of course you have to stay on your dime in NOL!I may have to modify my original plans and avoid both the CL and LSL routes entirely. Seems like the 19 Crescent to NOL has much better on time record. This would require an overnight stay in NOL(never a bad thing!) and then catch 1 SL leaving 9:00 A.M. next morning to TUS. This route would also prevent me from being on sleeper that would have to be cut away from TE and coupled onto the SL consist at SAS in the wee hours of the morning.. Anybody with any better suggestions or ideas I am open to any and all of them.
The LSL and Cap Connections in CHI are guaranteed so Amtrak would be responsible for getting you to TUS, if you missed the 421 they may even put you on the SWC to LAX, then #2 to TUS if it was on a day #2 was scheduled to operate!
You may want to look @ the Cardinal #51 ( 3days a week also) if it gets to CHI on a #421 day, its OTP had been much better into CHI than #29 or #49/#449!
I have only one concern with this route that I am considering.The 51/ Cardinal is sold out of all sleeping accommodations,including roomettes,most likely due to it's limited service 3 day/week schedule.That means the entire 28 hour trip has to be done in coach class. I am not sure how well I will be able to handle sleeping in a reclining seat as opposed to a roomette.Since 51/Cardinal departs NYP it can't use Superliner coaches which I understand to be much more comfortable than the older Amfleet II coaches used on 51/Cardinal as well as 49/LSL.Also, many other forum posts have discussed poor restroom conditions on Amfleet coaches (I believe 2/coach car for approx 60 people) vs. Superliner coaches( 4-5/coach car for about 74 people).It would seem to me that the Superliner coaches,with a much better ratio of restrooms to total people and slightly roomier seats would have an advantage over the older Amfleet coaches.Of course,wanting to travel on a Superliner coach would mean having to forgo both the 51/Cardinal and/or 49 LSL in favor of 29 CL. Would appreciate any insight or feedback on either of these concerns before I finalize travel plans.Also, thanks for reading my rather lengthy post.