As I recall, that's how Gilligan and his crew were stranded on an island - a three-hour tour gone bad. Sometimes, travel is just like that.
I never like to fly the day of a game. Always nervous something will happen and I won't get there and the Seattle Mariners will make major news and everyone will have it but me, because I'll be listening to my i-pod on a runway somewhere.
So my flight to Kansas City? My itinerary had me out of Seattle yesterday at 1 p.m., connecting in Salt Lake City and arriving about 8 p.m. Inexpensive, get me in for tonight's game with almost a day to spare.
That was the plan.
Instead, there were problems with the plane in Seattle - something about the black box not recording. We sat on the plane for about 45 minutes, then were deplaned and told to make other plans. As I was speaking to a customer service rep, they announced they'd solved the problem and wanted us back aboard.
Off we went - more than 90 minutes late. Got to Salt Lake City, my connection was gone. And there were no flights to Kansas City the rest o the day or night. Back to customer service and - I am not making this up - their first plan was to fly me to Las Vegas, then to Detroit, then to Minneapolis and then, at 6 a.m., to KC.
I vetoed that. A four-hour trip from Seattle to Kansas City should not involve five cities.
A fine fellow behind the desk said they could fly me to Minneapolis direct from Salt Lake, put me up in a hotel and get me out this morning to KC. I took it. Flew to Minneapolis, landed at 11:30 p.m., and got to the West Bloomington Days Inn about 12:30 a.m.
Left a wakeup call for 4 a.m. for a 6 a.m. flight.
Once aboard my plane, we had - I am still not making this up - mechanical problems. We quickly fled the plane and were rebooked on at 8:30 a.m. flight. That one actually took off, got to KC about 10 a.m.
Not complaining here. Love the jo. Once, twice a year something like this happens and you laugh at yourself and the situation. How long does it take to get to Kansas City? How long you got?