Looking at this further, it appears that in order to ensure being able to do transit rides in STL, the only reason for going there (otherwise coming back ABQ-CHI we would just remain on the Southwest Chief), we would have to stay overnight in BOTH St. Louis and Chicago. If we intentionally book #314, and then get shunted to #316 if the KCY connection is missed, it means having to wait potentially 7 or more hours in Kansas City, a city without any rail transit. Maybe we could watch grass grow or paint dry there. If we book #316, forcing ourselves into the long wait, would they let us ride #314 if the connection is made? Odds are with such a large group the number of seats available could be limited.A suggestion for the Chief Rail Fest: Make St. Louis the homeward overnight rather than Chicago.
The connection at KCY between the Chief (ar 7:24am) and the MRR (dp 8:15am) is iffy, at best. If a late Chief misses the morning MRR, then the only option is to wait at KCY until 4pm for the evening trip to STL. Since there is a later train from KCY to STL, Amtrak likely will not hold the morning MRR more than a few minutes for a late Chief.
With the plan to move on to Chicago on the same day as departing KCY, the misconnect at KCY then compounds to a failed onward connection to CHI at STL requiring an unplanned overnight at STL and rebooking the onward leg to CHI for the next day. It also fouls any hotel reservations in Chigago which, depending on the terms of the reservation, could cause a loss of any deposit. In other words, if the Chief is late into KCY, the manure hits the fan blades for the rest of the plan.
If an overnight is planned STL, with the onward trip to Chicago the next morning and same day connections at CHI to east coast trains, then a misconnect at KCY between the Chief and the MRR only results in the loss of the transit rides in St. Louis. The planned hotel stay in St. Louis is still good. The next day onward reservations from STL to CHI are still good. Plus, since STL through CHI to eastern destinations is continuous, an AGR award reservation could handle the trip, maybe including a roomette and meal on the Texas Eagle to CHI.
Just a suggestion.
On the St. Louis end, taking #314 would pose no problem, as the light rail trips could easily be done in the afternoon and/or evening, we'd stay there, and then could depart next morning. #316 comes in way too late to see anything by daylight, even in the summer. But the big flaw with the Lincoln Service/Texas Eagle schedule is that 3 of the 5 trips leave STL before 8 AM, and then there is a 7+ hour gap until the next train at 3 PM. Said Train #304 would get into Chicago well after the Cardinal & Capitol Limited departures, and way too close to the Lake Shore Limited departure to be guaranteed.
So if one gets into STL at 9:40 PM, there's no time to ride Metrolink that evening, nor the following morning if we wanted to take the Texas Eagle. So it means a long day in STL, taking #304, plus an evening in a hotel in CHI, plus the next day doing things in Chicago before the eastward departures.
So the schedules do pose problems that would require more overnights to ensure we can accomplish our goals of riding certain transit. At the same time we'd have a longer stays in KCY and STL; at least at the latter there's more to do. In STL we have the newer Cross County Metrolink (Blue line) a definite goal, but there's no problem killing time riding the rest of the system in Missouri and Illinois again. I wouldn't do the Arch again, but there are other things to see and do along the light rail lines and downtown.
Another alternative is TWO nights in hotels in STL, which would allow us to arrive on #316 the first day, stay over, fulfill our transit obilgations over the next entire day, and then on the third day depart on the northbound Texas Eagle (#22/322/422) in order to easily make connections to the east.
Edited by KevinKorell, 29 April 2011 - 01:13 PM.