Continued Light Blogging

I’m in Columbia, MO, attending a wedding, and visiting family. Weather’s decent today (probably low nineties, but humidity’s not bad), but that’s because there seems to be a major drought here, with less than an inch of rain in the last few weeks. Corn crop is down by half.

Transterrestrial–your source for space policy, and farm reports!

One More Thought On Fleet Grounding

I earlier noted the irony that the one part of the Shuttle that has actually been reliable (the Orbiter) is the one that Mike Griffin wants to retire. Both Shuttle disasters were caused by the non-Orbiter parts (SRB in the case of Challenger, ET in the case of Columbia), and those are the pieces that he wants to build the new vehicles out of (SRB as a lower stage for the crew vehicle, and SRB and modified ET for the heavy lifter).

Of course, the response will be that the only reason those failures were a problem was because of the overall system configuration with the Orbiter. Since both the new concepts will have the payload on top, where blow torching from joint leaks, and falling foam won’t cause problems, that makes it OK (though that’s actually not true with the heavy lifter, since the ET was the first casualty from the SRB failure, before the Orbiter broke up).

Which brings up a question: how much side forces were detected during the Challenger launch from the SRB leak (presumably from attempts by the TVC to keep the vehicle straight)? Does anyone know (I assume that the data may be in the Rogers Commission Report)? Would it have caused a problem with “the stick”?

Complex Failure Bleg

One of the things that I’m working on is a series of case studies for failure of complex technological systems, particularly where a failure cascades (perhaps inevitably) into others. Columbia is a good example, in which the fragile leading-edge TPS was damaged during launch, which resulted in initial burnthrough during entry, which caused more internal damage, which resulted in a bigger hole in the wing, which resulted in increasing asymmetric forces on the vehicle, which resulted in eventual inability to keep the nose pointed forward, which resulted in the destructive breakup of the vehicle from aerodynamic forces.

Is anyone aware of similar cases (preferably non-space, e.g., the Bonefish fire)?

Grounded Fleet

Just a few random thoughts before crashing.

I haven’t had time to read much about the fleet grounding thing, but I’ve often said that when government occasionally does the right thing, it’s almost always for the wrong reason. If we end up retiring the Shuttle now, it won’t be because it costs too much for what it does, and soaks up a lot of money that could (at least in theory, though probably not in practice, given the way our space policy seems to work) be used for something more productive in terms of moving humanity into space. It will be because we got better cameras so that we could finally see the rain of debris that’s been falling from every ET every time we fly, and we’re nervous about killing astronauts (even though taking such risks is, at least in theory, part of their job description). Ignorance was bliss, at least if you make a healthy living off operating Space Shuttles.

I frankly think that it’s a dumb reason, but if it happens, I also think it’s a good outcome, so I won’t complain too much. But here’s the problem. There’s an old saying about some businesses being “too big to fail” (e.g., Lockheed, various banks in the eighties, perhaps GM)–that is, the political consequences of letting them go out of business are viewed as sufficiently dire that the government will continue to prop them up, a la Weekend at Bernies, even when the carcass begins to stink. Shuttle, I’m afraid, is like that.

What I suspect is going on is that the declaration of fleet grounding is to piously show NASA’s contrition over Columbia, and to demonstrate that they have a new “safety culture.” What it really means is that they’ll do some kind of kabuki dance to come up with another “solution” to the foam-falling-off problem, and then launch again. And when it falls off again, they’ll say, “time to ground the fleet again, back to the drawing board.” And then they’ll do another test flight. It could plod along in this manner for years, if JSC and Huntsville are lucky, and the rest of us (those who pay taxes and care about a serious space program, anyway)…less so.

Anyway, off to bed, and (oh, joy) another airplane ride at the crack of dawn.

As For The Light Posting

I’m just recovering from a harrowing travel nightmare. I was supposed to fly back down to Florida from DC last night, getting in after midnight, and then get up in the morning for a flight to LA.

That’s bad enough, and that was if things went according to plan. However, this trip was one of the least “going according to plan” types I’ve experienced in a long time. A front came through northern Virginia just as I was arriving at the airport, and I found out my flight to Atlanta was delayed. The first delay would have allowed me to still catch my connection to Fort Lauderdale, but the delays kept piling up (apparently the plane on which I was to depart was stuck at JFK, as a result of bad weather in New York). I talked the situation over with Delta, and they assured me that not only were they not going to be able to get me home that night, but they wouldn’t be able to do so (at least with any confidence) in the morning either, not in time to catch my flight to California, anyway.

So like Jim Lovell (not to make too grandiose a comparison to our respective situations), I gave up the moon, i.e., I resigned myself that I wasn’t going to get home that night, and determined instead to find an alternate route to California that wouldn’t cost an arm and a leg. I negotiated an exchange with American for a non-stop from Dulles to replace my non-stop from Fort Lauderdale in the morning, and got vouchers from Delta. The big problem at that point was that until my flight in the morning, I was stuck in DC with no room, or reservation. I schlepped my luggage up and down non-functional escalators at the Metro to get back to Crystal City, to discover that not only did I have no room, but there were no rooms to be had, due to all of the other people in the same boat who had been possessed of more sense than me, and got rooms as soon as they figured out the score instead of wasting time on the phone worrying about an unrelated flight the next day. Oh, and did I mention that my cell phone was almost dead, and that I’d forgotten to pack a charger, which was one of the things that I was going to retrieve on my brief visit home?

So anyway, I reschlepped luggage up and down non-functional escalators back to Reagan on the Metro, and looked for a rental car with which to hie myself out Dulles way and procure a room. The only one available was a full-size for seventy bucks a day, before tax, though she was kind enough to waive the drop fee for returning it to Dulles instead of Reagan. A taxi would have been cheaper, but not having a room, I didn’t know where to tell a taxi to go.

Anyway, long story short, I did find a room in Herndon, got a few hours sleep that (considering the cost of both car and room) cost me about forty bucks an hour, and I did manage to finally get to LA, though we sat on the tarmac for half an hour after arrival due to the fact that another aircraft was having minor maintenance problems at our designated gate.

I know I’m making this sound pretty bad. It was actually much worse–I’m just too beat right now to expound on the whole odyssey at length.

And why, you ask, was it so consarned important that I get to LA today?

Because I have a flight to St. Louis at 6:30 from here in the morning.

Don’t ask.

Rough Week

I’ve been at meetings at NASA HQ all day (sorry, nothing particularly exciting) and I’m about to fly back to Florida for about ten hours, after which I fly to California for the afternoon, then to St. Louis for a weekend family wedding, leaving on Friday morning. Blogging is unlikely for a while…

I will leave you with this irritating vignette from the White House Press Corps, offered by Jeff Foust:

Q And how is the Mars program going?

MR. McCLELLAN: NASA can probably update you on the effort. Again, this is a long-term program, and you can sit there and smirk about it, but the President felt it was important — (laughter) — the President felt it was important to outline a clearly defined mission for NASA. And we’re all excited about today’s launch and we wish the —

Q Will he be speaking about it —

MR. McCLELLAN: Hang on — we wish the crew all the best.

Q Will he be speaking about it —

MR. McCLELLAN: NASA is working on implementing it, John. Thanks for starting out the briefing on such — (laughter.)

Wasn’t that a knee slapper?

That dumb Bush and his fantasy mission to Mars. Yuk, yuk…

McClellan didn’t handle this well. The response to the first question should have been: “To which Mars program are you referring?” (Thus offering the reporter an opportunity to be more expansive on his profound ignorance about national space policy).

After he did so, saying something like, “You know, the president’s plan to send people to Mars decades from now,” the response would be: “Well, John, how much progress would you expect this year on something that’s not going to happen for decades? Do you imagine that that’s the sum total of American space policy? Or haven’t you been paying attention? Are you opposed to the nation having a long-term vision for space exploration?”

Yeah, I know that his job is to answer questions, not ask them, but still.

What’s really annoying about this is that on one of the few times the daily White House briefing leads off with space policy questions (due obviously to yesterday’s successful launch) there can’t be an intelligent discussion about it.

Biting Commentary about Infinity…and Beyond!