KSC FOMO is real

This weekend is treating me to the first-world problem of having travel booked to a place I haven’t visited in three years–at the cost of not being able to visit another place I haven’t visited in four years.

The Kennedy Space Center's Vehicle Assembly Building, Shuttle Landing Facility Runway, and launch complexes 39A and 39B as seen from an American Airlines jet on the way to Miami.

While I will be packing Sunday to fly to Berlin for the IFA electronics show for the first time since 2019 (disclosure: the organizers are covering most of the travel costs for an invited group of U.S. journalists and analysts, myself included), NASA’s massive Space Launch System rocket will be enjoying what I trust is its last night of slumber on Pad 39B at the Kennedy Space Center before starting a journey to the Moon Monday morning.

Before everybody gets on my case for the subpar judgment I’ve just confessed, I booked the IFA travel in early July, weeks before NASA set tentative launch dates for this uncrewed Artemis I mission. At least I’ve got Monday morning mostly free to glue myself to a screen and see if SLS lifts off in the two-hour window that opens at 8:33 a.m.

Meanwhile, journalists I know are arriving at Cape Canaveral and tweeting photos from KSC’s press site, something I last got to do in 2018. The Artemis 1 countdown began Saturday morning. And if no technical glitches surface and all the other launch-commit criteria line up green Monday, everybody close enough will get to see NASA’s largest rocket since the Saturn V take to the skies–then hear and feel the crackling thunder of its engines, which apparently will be a lot louder than the shuttle’s.

I’ll only get to watch the proceedings from my living room. The closest I’ve gotten to the Cape since that February 2018 trip to cover Falcon Heavy’s debut is seeing KSC from a plane–which, don’t get me wrong, is a real window-seat treat.

But while I may have to wait two more years for a chance to see the next SLS launch, the launch calendar is now so busy at the Space Coast that even a randomly scheduled trip to central Florida allows decent odds of seeing a liftoff. So, yes, I will return to KSC even if it’s just for fun–and in that case, I’m bringing my family so they can see firsthand why I’m so crazy about this.

Weekly output: Falcon Heavy (x2), family-plan wireless math, Strava privacy, Web-site defacements, Tech Night Owl

This week was more exciting than most: I returned to the Kennedy Space Center for the first time since 2011 to see the liftoff of the most powerful rocket to leave American soil since 1973. I still can’t quite believe that I pulled that off… but I have the photos I took around Launch Complex 39A and the audio of the launch I recorded from the KSC press site to remind me that I did.

2/6/2018: SpaceX successfully launches the world’s most powerful rocket, Yahoo Finance

Two posts about the Falcon Heavy appeared at this Web address. The first was a curtain-raiser I filed late Monday explaining the significance of the Falcon Heavy. The second was a launch story–written in advance so I only had to add descriptions of the liftoff and the subsequent landing of the outer first-stage boosters–that my editors subbed in Tuesday afternoon. I also had a third post mostly ready that you didn’t read: a just-in-case piece about an unsuccessful launch that became irrelevant minutes after 3:45 p.m. Tuesday.

If you didn’t get a chance to see the pre-launch story at Yahoo, you can still read it at the Internet Archive, as shown in the screengrab above.

2/7/2018: The family cell-phone bill: How to find savings on shared wireless plans, USA Today

A reader complained that last week’s USAT column on cheaper alternatives to unlimited data for a smartphone didn’t offer any insight about saving money on shared-use family plans. Dear reader: story assignment accepted.

2/7/2018: The Strava social exercise app can reveal your home address, Yahoo Finance

I was grateful for this chance to redeem my prior Strava coverage: a study by a mobile-security firm that revealed how that exercise-tracking app’s geofenced privacy options can pinpoint a Strava user’s home address instead of obscuring it.

2/10/2018: Kuwait interior-ministry site hacked, Al-Jazeera

The Arabic-language news channel had me on to talk (overdubbed live into Arabic) about a recent episode of a hacker in Saudi Arabia defacing the site of Kuwait’s Interior Ministry. There’s a long history of this kind of digital vandalism, and fortunately the host mainly asked me about that instead of Gulf politics.

2/10/2018: February 10, 2018 — Kirk McElhearn and Rob Pegoraro, Tech Night Owl

I talked with host Gene Steinberg about the Falcon Heavy launch, Strava’s privacy issues and Apple’s new HomePod speaker. Gene’s other guest was Kirk McElhearn, who’s long been among my favorite Apple reporters.

Launch logistics: Booking a trip to see Falcon Heavy fly on three days’ notice

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.

The schedule details I needed from SpaceX arrived shortly after noon Saturday, so I got to work–one travel component at a time.

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.

Continue reading