Other

Washington Post: space plan “stalled”

An article on the front page of the Washington Post discusses the lack of momentum the new space initiative has in Congress. The article is a good overview of the issues that have been discussed here and elsewhere in the last three-and-a-half months, although there’s not much in the way of new information. The writer, Guy Gugliotta, does engage in a bit of hyperbole when, about halfway through the article, he describes the “withering criticism” the plan has faced: other than a few “testy” exchanges (notably one in February he doesn’t explicitly mention between Rep. Bart Gordon (D-TN) and O’Keefe and John Marburger) the debate has been strong, but well-mannered. The article’s conclusion: the fate of the initiative is “at best, in doubt.”

12 comments to Washington Post: space plan “stalled”

  • Dwayne A. Day

    I agree that “whithering criticism” is overstated. The article implies that this criticism was expressed during congressional hearings. But I’ve been to most of O’Keefe’s appearances on the Hill and the overwhelming impression I came away with from them is admiration for the political process. The questions were generally good and always respectful. During a hearing before the Senate Appropriations Committee Senator Mikulski had some tough questions, primarily about the Hubble demise, but they were also fair questions and the tone was businesslike. I suspect that private meetings have been tougher. The exchange between congressman Gordon and O’Keefe was a little heated, but one also got the sense that Gordon was quite frustrated that nobody would give him a proper answer.

    On the one hand, O’Keefe has a good point that it is very difficult to provide a plan or a budget at such an early date. Until they have made a launch vehicle decision and selected a mission mode, those numbers are going to be unreliable.

    However, NASA has had an internal set of figures for several months now that they have not provided to Congress in public testimony. Those numbers were revealed in an Aviation Week article a week or so ago, but they have been floating around for quite a bit longer. I suspect that some congressional frustration is due to the view in Congress that NASA does indeed have some numbers and is withholding them from Congress, for whatever reason.

  • If they have numbers, they probably want to hold them close until they develop some level of comfort with them.

  • Dwayne A. Day

    It may be true that they are trying to get a level of comfort with them. But there are two problems. First, they have circulated the numbers to others. I actually heard about them months ago. So they are showing them to some people, just not the congressional committees. It is easy to see why the committees would be upset at this. Second, while seeking a level of comfort with their numbers, they must be getting mighty uncomfortable with the language coming from the Hill. So if this is what is actually going on, then NASA has decided to take the heat that the Post is referring to.

  • Who are “they”? Are you implying that NASA, unlike all other government agencies, is leakproof? The fact remains that O’Keefe probably wants to keep number close to the vest until he can justify them publicly.

  • Harold LaValley

    Also not knowing the out come of the MoontoMars commission hearings and of any mandates from the President. Those things may change what is done, how it is accomplished as well as when it will be done. Which to me anyways it makes no sense to speak of numbers that have very little tangibleness to them, when they can very so greatly from as little as 229billion to 1 trillion dollars. O’Keefe has given hard numbers with regards to all shuttle work and precieved cost to start any work on the CEV. Also depending on the direction of building from current rockets or from starting from scratch changes the totals as well. There is so much new hardware to design for both the Moon missions and for Mars of which a small amount of these items are common for use to both.

  • Harold: the 1 trillion dollar number is utterly bogus. So stop using it. Dwayne put that topic to bed quite efficienty a week or two ago.

    As for your posts: try putting them through a grammar checker – or have someone else read them – before you post them. They are rather hard to follow.

    “Tangibleness” is not a word.

  • Harold LaValley

    I agree that 1 Trillion is out of the question but NASA has and still has this nasty habit of dropping zero’s from many qoutes from the past. Shuttle build costs, Shuttle maintainance, Cost per shuttle launch, ISS project cost….
    I think when most people look at a huge number, we all would like to know what we will get for the cash. The senate is doing the same. They are asking Cev, is this a new rocket or shuttle derived, does this include any new lunar or Mars landers, what kind of base and size is to be used….
    They just simply want more details..
    So far we know the return to flight estimate, number of shuttle flights to finish the ISS and very little of anything else.

  • Harold: read Dwayne’s article. Nothing is going to cost a trillion dollars. And no, NASA does not drop zeroes from cost estimates. It is usually the first digits that change. Again, read Dwayne’s article.

  • Dwayne A. Day

    Mr. LaValley wrote:
    “…but NASA has and still has this nasty habit of dropping zero’s from many qoutes from the past. Shuttle build costs, Shuttle maintainance, Cost per shuttle launch…”

    NASA’s estimate for the cost of _developing_ the space shuttle was remarkably good. I would have to look this up again, but I believe that it was only off by about 20%. Now considering that this was a completely new vehicle with many new technologies, and it was built during a time of high inflation (the late 1970s) that was not bad.

    In addition, NASA actually _overestimated_ the cost of building the shuttle Endeavour and it turned out to be about 15% cheaper than they expected.

    NASA was, of course, completely wrong about the costs of _operating_ the shuttle and also the flight rate.

    There is lots of evidence that NASA is not really much worse than any other government agency at predicting the costs of high tech goods. Take a look at the SBIRS-High satellite, which was predicted to cost $2 billion and enter service in 2004 and is now predicted to cost $9 billion and enter service in 2007.

    It is worth noting, however, that government agencies are often bad at predicting costs even for mundane and low-tech things. A large road construction project in Northern Virginia actually cost significantly more than expected because of stupidity by the government accountants. For one thing, they forgot to include the cost of inflation over the seven-year lifetime of the project (something that anybody in Accounting 101 should know about). They also made a lot of dumb assumptions, like assuming that the state could simply “take” property belonging to a local school district. When they told a high school principal that they were going to take his football stadium and running track for an on-ramp, he told them that they would have to provide another one, which of course they had to build.

  • Paul Dietz

    According to McCurdy, NASA managed to get a good estimate for STS development costs by splitting the development into two phases. The first phase (which led to the vehicle flying) was close to budget, but Phase II (continuing development after the first flight) far exceeded projections.

  • Dwayne A. Day

    Mr. Dietz wrote:
    “but Phase II (continuing development after the first flight) far exceeded projections.”

    I know Howard and have worked with him, but never asked him about this. It is possible that “continuing development” was impossible to predict because the requirements kept changing. One could easily see how, once the thing is flying, officials are constantly redefining what they need to change.

    As I understand it, there are a number of things that traditionally go wrong in predicting the costs of advanced development projects. One of the big ones is that the decision makers keep revising the requirements. As a result, the vehicle that gets built is usually not the one that was defined in the initial cost estimate. Of course, there are legitimate excuses and illegitimate abuses of the requirements process. Supposedly, “spiral development” is a way of getting a handle on the requirements creep problem, although I have no idea how it affects cost estimating.

  • Paul Dietz

    This is just lazy speculation, but it’s also possible that continuing development ballooned because the stopping condition (a shuttle that satisfied the promises, or came close) was not attainable.