I’ve had the idea of covering the first launch of SpaceX’s Falcon Heavy rocket in the back of my mind for the last few years, but I didn’t book my travel for Tuesday’s launch until Saturday afternoon.
I was waiting for a confirmation of the schedule from the company that would be more solid than a notional “No Earlier Than” date, and which would then let me know if I could still attend a Yahoo Finance cryptocurrency conference in New York on Wednesday. Besides, I knew that D.C. and Orlando often represent a cheap city pair.
Having to reach the Kennedy Space Center by 1:15 p.m. to visit Launch Complex 39A ruled out some decent mid-day fares. But Southwest’s site showed a 6 a.m. nonstop out of National for only $50. Sold!
Then I canceled the D.C.-NYC Amtrak reservation I’d had for Tuesday night (I appreciate that the railroad still lets you do that for free until 24 hours before departure) and booked a Tuesday-night flight from Orlando to New York to replace it.
I went with United for that leg, spending a little extra (a still-reasonable $155) to fly on an airline where my frequent-flyer status would allow a free same-day-change to a Wednesday flight to Newark if a launch scrub required that. A few more clicks to book a rental car and one night’s lodging, and I had launch travel solved… or so I thought until an hour after a liftoff that got pushed back to 3:45 p.m. by upper-atmosphere winds.
At that point, the “OMG! OMG!” shaking had stopped, I’d filed my copy, and Google Maps indicated that the usual 45-minute drive from KSC to Orlando would run an hour and 15 minutes. Nope! As horrendous post-launch traffic dragged Google’s arrival estimates past my flight’s boarding time, I called United to see if they had space on the morning’s first MCO-EWR nonstop, a 5:36 a.m. departure. They did.
After dropping off my rental car and getting through a mercifully quick security checkpoint (is there a better exhibit for TSA Pre or Clear than MCO?), I ran to my original flight’s gate and saw for myself that the plane was gone. I called United back, the rep bailed me out of the consequences of my overly-optimistic travel tactics by putting me on that 5:36 a.m. flight for free, and then I opened my laptop–tethering off my phone because the airport WiFi didn’t let me connect–to book a hotel barely two miles away for $90.
By then, it had been some 10 hours since I’d last eaten, so I treated myself to a nice dinner at the airport. (If you, too, get stuck at MCO and want something more original than the terminal’s fast-casual brands, head upstairs to McCoy’s in the Hyatt Regency). After a prolonged wait for the hotel van, thanks to no visible signage indicating that these shuttles could pick up at either of two spaces on the B side that sit maybe 800 feet apart, I was in bed by around midnight.
I somehow woke up one minute before the 4:15 alarm I’d set on my phone and was through security 40 minutes later. You can image my relief at seeing my upgrade clear, then having a quick NJ Transit ride from EWR to Manhattan help wrap up this prolonged commute by 9:10 a.m.
A long and informative day ensued with Yahoo colleagues, most of whom I hadn’t seen in months, and various cryptocurrency experts. But then my travel luck ran out again when my train to D.C. left more than an hour and a half late. Twitter, not Amtrak, informed me that this was the result of a tragedy–a northbound Acela striking and killing a person walking along the tracks in the Bronx, which led police to close the railroad for two hours.
That meant I didn’t get home until nearly 1 a.m, almost 21 hours after my day had begun. But I did get to sleep in my own bed, and I came home with two posts filed from KSC that more than covered my travel costs as well as dozens of photos (since edited into a Flickr album) and one unusual recording that you can hear after the jump.