<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: House appropriators cut deeper at NASA</title>
	<atom:link href="http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=house-appropriators-cut-deeper-at-nasa</link>
	<description>Because sometimes the most important orbit is the Beltway...</description>
	<lastBuildDate>Wed, 17 Sep 2014 13:35:41 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>By: Major Tom</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-340345</link>
		<dc:creator><![CDATA[Major Tom]]></dc:creator>
		<pubDate>Sun, 20 Feb 2011 03:55:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-340345</guid>
		<description><![CDATA[&quot;I am not familiar with &#039;the Air Force Analysis&#039; you refer to&quot;

Here&#039;s a summary and link to the presentation.

http://www.spaceref.com/news/viewsr.html?pid=31792

&quot;but if it was done for the Ares I that is a very different stack than either an In Line or Side Mount SDHLV and would not be applicable to this discussion&quot;

Those are all different stacks, but the fundamental problem -- that solid rocket propellant continues to burn after deflagration and poses a radiant heating danger to capsule parachutes -- is the same as long as those stacks use SRBs.

&quot;... the Apollo/Saturn hardware would have been &#039;incrementally evolved&#039; to support space operations.&quot;

I&#039;m all for incremental evolution when the technical base is affordable, sustainable, and reliable.  The Apollo systems didn&#039;t meet the first two criteria once the Soviet N-1 effort collapsed, and probably wouldn&#039;t have met the third criterion given a handful more flights.

&quot;Now that the SD hardware is available to be similarly &#039;incrementally evolved&#039;&quot;

The Shuttle technical base doesn&#039;t meet these criteria, either.  

Shuttle has wasted NASA&#039;s human space flight budget on ETO transport for decades now, leaving practically nothing for BEO activities and limiting the LEO destination (ISS) to a budget that&#039;s half that its transportation (STS).  It&#039;s like spending double your mortgage or rent each year on gas for your commute.

Ares I/Orion was going to be a $35-40 billion development effort, vice the two EELV families, which the taxpayer got for $1 billion development investment, or Falcon 9/Dragon (unmanned), which the taxpayer received for $278 million.

Now we&#039;re being sold a congressionally designed SDHLV that NASA prices somewhere north of $16 billion, when we could put fault detection and gantries on Delta IVs to loft Orion for hundreds of millions of dollars.

When is this insanity going to end?  We&#039;re spending billions more on transportation vice destination and tens of billions more than what other space sectors spend for equivalent capabilities.  And for what?  A system crippled by safety concerns because it has no LES (STS) or will kill crews regardless of the LES (see USAF analysis above)?

&quot;That is according to NASA Headquarters.&quot;

Not to be snide, but what higher technical authority do you want to appeal to?

God?

&quot;I really wish that fight did not have to happen because I fear the outcome is going to very damaging for everyone (except those who want there to be no American based Space Program at all).&quot;

We can have an &quot;American-based&quot;, even a &quot;NASA-based&quot;, human space flight program without Shuttle or Constellation vehicles.

&quot;Per the above I simply so not accept your assertion that &#039;crews will be safer on those existing vehicles&#039;. For one thing a crew rated EELV is not an &#039;existing vehicle&#039;.&quot;

You&#039;re right that there is no crew-rated EELV today.  But adding a fault detection system, some pad gantries, and an LES to an existing ELV/capsule is a much simpler and much less expensive development than creating an entirely new LV stack (Ares I, sidemount, inline, etc.) out of Shuttle components that were not originally designed to fly in such a configuration.  That&#039;s even more true when the ELVs will have (or already do have) dozens of flights behind them before the first flight of that new Shuttle-derived LV stack.

FWIW...]]></description>
		<content:encoded><![CDATA[<p>&#8220;I am not familiar with &#8216;the Air Force Analysis&#8217; you refer to&#8221;</p>
<p>Here&#8217;s a summary and link to the presentation.</p>
<p><a href="http://www.spaceref.com/news/viewsr.html?pid=31792" rel="nofollow">http://www.spaceref.com/news/viewsr.html?pid=31792</a></p>
<p>&#8220;but if it was done for the Ares I that is a very different stack than either an In Line or Side Mount SDHLV and would not be applicable to this discussion&#8221;</p>
<p>Those are all different stacks, but the fundamental problem &#8212; that solid rocket propellant continues to burn after deflagration and poses a radiant heating danger to capsule parachutes &#8212; is the same as long as those stacks use SRBs.</p>
<p>&#8220;&#8230; the Apollo/Saturn hardware would have been &#8216;incrementally evolved&#8217; to support space operations.&#8221;</p>
<p>I&#8217;m all for incremental evolution when the technical base is affordable, sustainable, and reliable.  The Apollo systems didn&#8217;t meet the first two criteria once the Soviet N-1 effort collapsed, and probably wouldn&#8217;t have met the third criterion given a handful more flights.</p>
<p>&#8220;Now that the SD hardware is available to be similarly &#8216;incrementally evolved'&#8221;</p>
<p>The Shuttle technical base doesn&#8217;t meet these criteria, either.  </p>
<p>Shuttle has wasted NASA&#8217;s human space flight budget on ETO transport for decades now, leaving practically nothing for BEO activities and limiting the LEO destination (ISS) to a budget that&#8217;s half that its transportation (STS).  It&#8217;s like spending double your mortgage or rent each year on gas for your commute.</p>
<p>Ares I/Orion was going to be a $35-40 billion development effort, vice the two EELV families, which the taxpayer got for $1 billion development investment, or Falcon 9/Dragon (unmanned), which the taxpayer received for $278 million.</p>
<p>Now we&#8217;re being sold a congressionally designed SDHLV that NASA prices somewhere north of $16 billion, when we could put fault detection and gantries on Delta IVs to loft Orion for hundreds of millions of dollars.</p>
<p>When is this insanity going to end?  We&#8217;re spending billions more on transportation vice destination and tens of billions more than what other space sectors spend for equivalent capabilities.  And for what?  A system crippled by safety concerns because it has no LES (STS) or will kill crews regardless of the LES (see USAF analysis above)?</p>
<p>&#8220;That is according to NASA Headquarters.&#8221;</p>
<p>Not to be snide, but what higher technical authority do you want to appeal to?</p>
<p>God?</p>
<p>&#8220;I really wish that fight did not have to happen because I fear the outcome is going to very damaging for everyone (except those who want there to be no American based Space Program at all).&#8221;</p>
<p>We can have an &#8220;American-based&#8221;, even a &#8220;NASA-based&#8221;, human space flight program without Shuttle or Constellation vehicles.</p>
<p>&#8220;Per the above I simply so not accept your assertion that &#8216;crews will be safer on those existing vehicles&#8217;. For one thing a crew rated EELV is not an &#8216;existing vehicle&#8217;.&#8221;</p>
<p>You&#8217;re right that there is no crew-rated EELV today.  But adding a fault detection system, some pad gantries, and an LES to an existing ELV/capsule is a much simpler and much less expensive development than creating an entirely new LV stack (Ares I, sidemount, inline, etc.) out of Shuttle components that were not originally designed to fly in such a configuration.  That&#8217;s even more true when the ELVs will have (or already do have) dozens of flights behind them before the first flight of that new Shuttle-derived LV stack.</p>
<p>FWIW&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: common sense</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-340048</link>
		<dc:creator><![CDATA[common sense]]></dc:creator>
		<pubDate>Wed, 16 Feb 2011 18:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-340048</guid>
		<description><![CDATA[@  Joe wrote @ February 16th, 2011 at 1:36 pm

&quot;I am not familiar with â€œthe Air Force Analysisâ€ you refer to, but if it was done for the Ares I that is a very different stack than either an In Line or Side Mount SDHLV and would not be applicable to this discussion&quot;

Oh well, you are not familiar with the AF analysis yet you know for sure it is not applicable? 

I wonder what it is you actually do in this business.]]></description>
		<content:encoded><![CDATA[<p>@  Joe wrote @ February 16th, 2011 at 1:36 pm</p>
<p>&#8220;I am not familiar with â€œthe Air Force Analysisâ€ you refer to, but if it was done for the Ares I that is a very different stack than either an In Line or Side Mount SDHLV and would not be applicable to this discussion&#8221;</p>
<p>Oh well, you are not familiar with the AF analysis yet you know for sure it is not applicable? </p>
<p>I wonder what it is you actually do in this business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: common sense</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-340046</link>
		<dc:creator><![CDATA[common sense]]></dc:creator>
		<pubDate>Wed, 16 Feb 2011 18:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-340046</guid>
		<description><![CDATA[@  Major Tom wrote @ February 16th, 2011 at 11:16 am

&quot;er the Air Force analysis, there are whole minutes during the ascent when there is practically zero chance of a survivable abort.&quot;

You would also have to consider a pad abort as really non trivial. You have several mode of failures with SRBs AND LH2-LOX. A burning SRB might detonate the main tank which in turn might - I don&#039;t know for sure - detonate the other SRB. A detonation would most likely annihilate the capsule. Unless you know ahead of time it is going to happen there is no way to escape it. In any case it does indeed beg the question for the necessity of an actual LAS for such vehicle. I strongly believe that a LAS actually increases risk in that case for several reasons that I said above and those you state as well. 

An SDLV with a LAS inline (a la Ares V) would be very difficult to make work properly with even greater difficulty than an Ares I vehicle. 

A sidemount SDLV with a LAS might be even worse on the whole range of flight from pad to LAS jettison if the purpose is to recover the crew well... alive. 

We do not need a SD anything. We will not get a SD anything. Because on top of the technical difficulty they are well... too expensive!]]></description>
		<content:encoded><![CDATA[<p>@  Major Tom wrote @ February 16th, 2011 at 11:16 am</p>
<p>&#8220;er the Air Force analysis, there are whole minutes during the ascent when there is practically zero chance of a survivable abort.&#8221;</p>
<p>You would also have to consider a pad abort as really non trivial. You have several mode of failures with SRBs AND LH2-LOX. A burning SRB might detonate the main tank which in turn might &#8211; I don&#8217;t know for sure &#8211; detonate the other SRB. A detonation would most likely annihilate the capsule. Unless you know ahead of time it is going to happen there is no way to escape it. In any case it does indeed beg the question for the necessity of an actual LAS for such vehicle. I strongly believe that a LAS actually increases risk in that case for several reasons that I said above and those you state as well. </p>
<p>An SDLV with a LAS inline (a la Ares V) would be very difficult to make work properly with even greater difficulty than an Ares I vehicle. </p>
<p>A sidemount SDLV with a LAS might be even worse on the whole range of flight from pad to LAS jettison if the purpose is to recover the crew well&#8230; alive. </p>
<p>We do not need a SD anything. We will not get a SD anything. Because on top of the technical difficulty they are well&#8230; too expensive!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-340043</link>
		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Wed, 16 Feb 2011 18:36:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-340043</guid>
		<description><![CDATA[â€œMajor Tom wrote @ February 16th, 2011 at 11:16 am 
â€œI was not trying to compare Shuttle to an EELV with a capsule. The subject (at least I thought it was) was SDHLV to EELV.â€
Regardless, itâ€™s manned space flight and astronaut risks that weâ€™re talking about, not satellites. That means we have to include aborts in our consideration. 
â€œMicrometeorite or orbital debris strikes orbiter, leading to loss of vehicle in orbit or on re-entryâ€¦ Crew error during re-entry.â€
These are risks on any manned mission. Theyâ€™re not unique to Shuttle.
â€œWithout knowing all of the factors driving the Shuttle number, you cannot say how much higher it would be for an SDHLV (without the Orbiter reentry/landing components)â€
Itâ€™s not going to be much different from Shuttle, since whatever capsule the SDHLV is throwing is still subject to those debris and crew error risks.â€

The point I think you are missing is that the same is true for any crew vehicle design whether it is launched on an SDHLV or an EELV.  The Shuttle (1 in 90) number already covers that for the Orbiter (which is bigger and more fragile than any capsule design will be â€“ and thus is a â€œbigger targetâ€); the EELV (1 in 50) number does not cover such exposure at all (it covers only payload delivery to orbit).  Therefore to have an â€œapples to applesâ€ comparison you would have to set the end point of the risk analysis at the same point.  If that endpoint is delivery of payload to orbit, then I still say a (1 in 100) number is extremely conservative for an SDHLV.

â€œNevertheless, letâ€™s assume (again hypothetically) that abort from any SDHLV is more difficult than for an EELV. The generally used reliability number for an abort system is 90% (1 in 10). Letâ€™s grant that figure to EELV and only give SDHLV half that 80% (1 in 5).â€
â€œItâ€™s much worse than that for SDHLV. Even assuming an inline design (and setting aside the engineering nightmare of trying to get off a sidemount stack safely), per the Air Force analysis, there are whole minutes during the ascent when there is practically zero chance of a survivable abort. On top of that, to have a shot at getting away from the SRBs during the rest of the ascent profile, the LES on an SDHLV has to be much bigger and more complex â€” and thus less reliable â€” than the LES for an all-liquid stack.
As a result of the above, the Ares I/Orion LES was looking at about 50% (1-in-2). At that point, it begs the question of why even have an LES. If itâ€™s a coin toss as to whether the LES is going to save or kill the crew, then youâ€™re better off without it.â€

I am not familiar with â€œthe Air Force Analysisâ€ you refer to, but if it was done for the Ares I that is a very different stack than either an In Line or Side Mount SDHLV and would not be applicable to this discussion

â€œâ€œThose are â€˜sunk costsâ€™ as is the money already spent developing the EELVs.
Fair enough. We canâ€™t revisit history, but I sure wish we could in the case of Shuttle.â€

So do I, give me a time machine and the ability to run the circa 1970 United States and the Apollo/Saturn hardware would have been â€œincrementally evolvedâ€ to support space operations.  Instead we â€œthrew it awayâ€ and went chasing the â€œbold, innovative, game hanging, paradigm shiftingâ€ technology of its day (the Space Shuttle).  Now that the SD hardware is available to be similarly â€œincrementally evolvedâ€ we are in the process of making the same mistake again

â€œâ€œThe cost estimates for SDHLV are well lower than â€˜tens of billions of dollarsâ€™â€
Not so far according to NASA:
â€œThe authorization act gives NASA until 2016 to field the heavy-lift rocket and crew vehicle, and authorizes Congress to spend more than $10 billion on the two projects over the next three yearsâ€ but â€œNASAâ€™s Jan. 10 interim report states that â€˜neither Reference Vehicle Design currently fits the projected budget profiles nor schedule goals outlinedâ€™ in the lawâ€.â€

That is according to NASA Headquarters.  One of the discussions, likely to be â€œinterestingâ€ in the coming congressional hearings is why NASA HQ failed to provide the â€œsupporting dataâ€ (the field center technical work that was input to the NASA HQ generated report) Congress had requested.  I really wish that fight did not have to happen because I fear the outcome is going to very damaging for everyone (except those who want there to be no American based Space Program at all).

â€œEven if SDHLV cost the same as EELVs or Falcon 9, why spend taxpayer money duplicating a capability? Especially when crews will be safer on those existing vehicles?â€

Per the above I simply so not accept your assertion that â€œcrews will be safer on those existing vehiclesâ€.  For one thing a crew rated EELV is not an â€œexisting vehicleâ€.

At any rate, as you say: â€œFWIWâ€¦â€]]></description>
		<content:encoded><![CDATA[<p>â€œMajor Tom wrote @ February 16th, 2011 at 11:16 am<br />
â€œI was not trying to compare Shuttle to an EELV with a capsule. The subject (at least I thought it was) was SDHLV to EELV.â€<br />
Regardless, itâ€™s manned space flight and astronaut risks that weâ€™re talking about, not satellites. That means we have to include aborts in our consideration.<br />
â€œMicrometeorite or orbital debris strikes orbiter, leading to loss of vehicle in orbit or on re-entryâ€¦ Crew error during re-entry.â€<br />
These are risks on any manned mission. Theyâ€™re not unique to Shuttle.<br />
â€œWithout knowing all of the factors driving the Shuttle number, you cannot say how much higher it would be for an SDHLV (without the Orbiter reentry/landing components)â€<br />
Itâ€™s not going to be much different from Shuttle, since whatever capsule the SDHLV is throwing is still subject to those debris and crew error risks.â€</p>
<p>The point I think you are missing is that the same is true for any crew vehicle design whether it is launched on an SDHLV or an EELV.  The Shuttle (1 in 90) number already covers that for the Orbiter (which is bigger and more fragile than any capsule design will be â€“ and thus is a â€œbigger targetâ€); the EELV (1 in 50) number does not cover such exposure at all (it covers only payload delivery to orbit).  Therefore to have an â€œapples to applesâ€ comparison you would have to set the end point of the risk analysis at the same point.  If that endpoint is delivery of payload to orbit, then I still say a (1 in 100) number is extremely conservative for an SDHLV.</p>
<p>â€œNevertheless, letâ€™s assume (again hypothetically) that abort from any SDHLV is more difficult than for an EELV. The generally used reliability number for an abort system is 90% (1 in 10). Letâ€™s grant that figure to EELV and only give SDHLV half that 80% (1 in 5).â€<br />
â€œItâ€™s much worse than that for SDHLV. Even assuming an inline design (and setting aside the engineering nightmare of trying to get off a sidemount stack safely), per the Air Force analysis, there are whole minutes during the ascent when there is practically zero chance of a survivable abort. On top of that, to have a shot at getting away from the SRBs during the rest of the ascent profile, the LES on an SDHLV has to be much bigger and more complex â€” and thus less reliable â€” than the LES for an all-liquid stack.<br />
As a result of the above, the Ares I/Orion LES was looking at about 50% (1-in-2). At that point, it begs the question of why even have an LES. If itâ€™s a coin toss as to whether the LES is going to save or kill the crew, then youâ€™re better off without it.â€</p>
<p>I am not familiar with â€œthe Air Force Analysisâ€ you refer to, but if it was done for the Ares I that is a very different stack than either an In Line or Side Mount SDHLV and would not be applicable to this discussion</p>
<p>â€œâ€œThose are â€˜sunk costsâ€™ as is the money already spent developing the EELVs.<br />
Fair enough. We canâ€™t revisit history, but I sure wish we could in the case of Shuttle.â€</p>
<p>So do I, give me a time machine and the ability to run the circa 1970 United States and the Apollo/Saturn hardware would have been â€œincrementally evolvedâ€ to support space operations.  Instead we â€œthrew it awayâ€ and went chasing the â€œbold, innovative, game hanging, paradigm shiftingâ€ technology of its day (the Space Shuttle).  Now that the SD hardware is available to be similarly â€œincrementally evolvedâ€ we are in the process of making the same mistake again</p>
<p>â€œâ€œThe cost estimates for SDHLV are well lower than â€˜tens of billions of dollarsâ€™â€<br />
Not so far according to NASA:<br />
â€œThe authorization act gives NASA until 2016 to field the heavy-lift rocket and crew vehicle, and authorizes Congress to spend more than $10 billion on the two projects over the next three yearsâ€ but â€œNASAâ€™s Jan. 10 interim report states that â€˜neither Reference Vehicle Design currently fits the projected budget profiles nor schedule goals outlinedâ€™ in the lawâ€.â€</p>
<p>That is according to NASA Headquarters.  One of the discussions, likely to be â€œinterestingâ€ in the coming congressional hearings is why NASA HQ failed to provide the â€œsupporting dataâ€ (the field center technical work that was input to the NASA HQ generated report) Congress had requested.  I really wish that fight did not have to happen because I fear the outcome is going to very damaging for everyone (except those who want there to be no American based Space Program at all).</p>
<p>â€œEven if SDHLV cost the same as EELVs or Falcon 9, why spend taxpayer money duplicating a capability? Especially when crews will be safer on those existing vehicles?â€</p>
<p>Per the above I simply so not accept your assertion that â€œcrews will be safer on those existing vehiclesâ€.  For one thing a crew rated EELV is not an â€œexisting vehicleâ€.</p>
<p>At any rate, as you say: â€œFWIWâ€¦â€</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Major Tom</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-340034</link>
		<dc:creator><![CDATA[Major Tom]]></dc:creator>
		<pubDate>Wed, 16 Feb 2011 16:16:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-340034</guid>
		<description><![CDATA[&quot;I was not trying to compare Shuttle to an EELV with a capsule. The subject (at least I thought it was) was SDHLV to EELV.&quot;

Regardless, it&#039;s manned space flight and astronaut risks that we&#039;re talking about, not satellites.  That means we have to include aborts in our consideration. 
 
&quot;Micrometeorite or orbital debris strikes orbiter, leading to loss of vehicle in orbit or on re-entry... Crew error during re-entry.&quot;

These are risks on any manned mission.  They&#039;re not unique to Shuttle.

&quot;Without knowing all of the factors driving the Shuttle number, you cannot say how much higher it would be for an SDHLV (without the Orbiter reentry/landing components)&quot;

It&#039;s not going to be much different from Shuttle, since whatever capsule the SDHLV is throwing is still subject to those debris and crew error risks.

&quot;Nevertheless, letâ€™s assume (again hypothetically) that abort from any SDHLV is more difficult than for an EELV. The generally used reliability number for an abort system is 90% (1 in 10). Letâ€™s grant that figure to EELV and only give SDHLV half that 80% (1 in 5).&quot;

It&#039;s much worse than that for SDHLV.  Even assuming an inline design (and setting aside the engineering nightmare of trying to get off a sidemount stack safely), per the Air Force analysis, there are whole minutes during the ascent when there is practically zero chance of a survivable abort.  On top of that, to have a shot at getting away from the SRBs during the rest of the ascent profile, the LES on an SDHLV has to be much bigger and more complex -- and thus less reliable -- than the LES for an all-liquid stack.

As a result of the above, the Ares I/Orion LES was looking at about 50% (1-in-2).  At that point, it begs the question of why even have an LES.  If it&#039;s a coin toss as to whether the LES is going to save or kill the crew, then you&#039;re better off without it.

&quot;Those are &#039;sunk costs&#039; as is the money already spent developing the EELVs.

Fair enough.  We can&#039;t revisit history, but I sure wish we could in the case of Shuttle.

&quot;The cost estimates for SDHLV are well lower than &#039;tens of billions of dollars&#039;&quot;

Not so far according to NASA:

&quot;The authorization act gives NASA until 2016 to field the heavy-lift rocket and crew vehicle, and authorizes Congress to spend more than $10 billion on the two projects over the next three years&quot; but &quot;NASAâ€™s Jan. 10 interim report states that &#039;neither Reference Vehicle Design currently fits the projected budget profiles nor schedule goals outlined&#039; in the law&quot;.

http://spacenews.com/civil/110111-nasa-heavy-lift-proposal.html

And Ares I/Orion alone was pushing $35-40 billion before termination.

Even if SDHLV cost the same as EELVs or Falcon 9, why spend taxpayer money duplicating a capability?  Especially when crews will be safer on those existing vehicles?

&quot;and the cost for fielding crew rated EELVs would not be zero.

No, but they&#039;re measured in the hundreds of millions to low billions of dollars, not $10-20 billion plus.

FWIW...]]></description>
		<content:encoded><![CDATA[<p>&#8220;I was not trying to compare Shuttle to an EELV with a capsule. The subject (at least I thought it was) was SDHLV to EELV.&#8221;</p>
<p>Regardless, it&#8217;s manned space flight and astronaut risks that we&#8217;re talking about, not satellites.  That means we have to include aborts in our consideration. </p>
<p>&#8220;Micrometeorite or orbital debris strikes orbiter, leading to loss of vehicle in orbit or on re-entry&#8230; Crew error during re-entry.&#8221;</p>
<p>These are risks on any manned mission.  They&#8217;re not unique to Shuttle.</p>
<p>&#8220;Without knowing all of the factors driving the Shuttle number, you cannot say how much higher it would be for an SDHLV (without the Orbiter reentry/landing components)&#8221;</p>
<p>It&#8217;s not going to be much different from Shuttle, since whatever capsule the SDHLV is throwing is still subject to those debris and crew error risks.</p>
<p>&#8220;Nevertheless, letâ€™s assume (again hypothetically) that abort from any SDHLV is more difficult than for an EELV. The generally used reliability number for an abort system is 90% (1 in 10). Letâ€™s grant that figure to EELV and only give SDHLV half that 80% (1 in 5).&#8221;</p>
<p>It&#8217;s much worse than that for SDHLV.  Even assuming an inline design (and setting aside the engineering nightmare of trying to get off a sidemount stack safely), per the Air Force analysis, there are whole minutes during the ascent when there is practically zero chance of a survivable abort.  On top of that, to have a shot at getting away from the SRBs during the rest of the ascent profile, the LES on an SDHLV has to be much bigger and more complex &#8212; and thus less reliable &#8212; than the LES for an all-liquid stack.</p>
<p>As a result of the above, the Ares I/Orion LES was looking at about 50% (1-in-2).  At that point, it begs the question of why even have an LES.  If it&#8217;s a coin toss as to whether the LES is going to save or kill the crew, then you&#8217;re better off without it.</p>
<p>&#8220;Those are &#8216;sunk costs&#8217; as is the money already spent developing the EELVs.</p>
<p>Fair enough.  We can&#8217;t revisit history, but I sure wish we could in the case of Shuttle.</p>
<p>&#8220;The cost estimates for SDHLV are well lower than &#8216;tens of billions of dollars'&#8221;</p>
<p>Not so far according to NASA:</p>
<p>&#8220;The authorization act gives NASA until 2016 to field the heavy-lift rocket and crew vehicle, and authorizes Congress to spend more than $10 billion on the two projects over the next three years&#8221; but &#8220;NASAâ€™s Jan. 10 interim report states that &#8216;neither Reference Vehicle Design currently fits the projected budget profiles nor schedule goals outlined&#8217; in the law&#8221;.</p>
<p><a href="http://spacenews.com/civil/110111-nasa-heavy-lift-proposal.html" rel="nofollow">http://spacenews.com/civil/110111-nasa-heavy-lift-proposal.html</a></p>
<p>And Ares I/Orion alone was pushing $35-40 billion before termination.</p>
<p>Even if SDHLV cost the same as EELVs or Falcon 9, why spend taxpayer money duplicating a capability?  Especially when crews will be safer on those existing vehicles?</p>
<p>&#8220;and the cost for fielding crew rated EELVs would not be zero.</p>
<p>No, but they&#8217;re measured in the hundreds of millions to low billions of dollars, not $10-20 billion plus.</p>
<p>FWIW&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Boozer</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-339972</link>
		<dc:creator><![CDATA[Rick Boozer]]></dc:creator>
		<pubDate>Tue, 15 Feb 2011 20:17:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-339972</guid>
		<description><![CDATA[&lt;i&gt;&quot;Falcon was lucky twice but I expect that cluster to blow up on the pad next time. I will keep my fingers crossed.&quot;&lt;/i&gt;

Based on their past tendency to be a money sponge, I&#039;m no big ATK fan.  But if they had a viable economically competitive rocket sitting on the pad ready to launch right now, I would be glued to the video coverage and rooting for their success because it would be to the advantage of the USA&#039;s future in space.  Whether you like them or not, if your priorities weren&#039;t so screwed up, you would have that same attitude about SpaceX&#039;s next launch instead of keeping your fingers crossed for their failure.  What is in the best interests of your country should come before petty puerile fanboism.  You are truly warped.]]></description>
		<content:encoded><![CDATA[<p><i>&#8220;Falcon was lucky twice but I expect that cluster to blow up on the pad next time. I will keep my fingers crossed.&#8221;</i></p>
<p>Based on their past tendency to be a money sponge, I&#8217;m no big ATK fan.  But if they had a viable economically competitive rocket sitting on the pad ready to launch right now, I would be glued to the video coverage and rooting for their success because it would be to the advantage of the USA&#8217;s future in space.  Whether you like them or not, if your priorities weren&#8217;t so screwed up, you would have that same attitude about SpaceX&#8217;s next launch instead of keeping your fingers crossed for their failure.  What is in the best interests of your country should come before petty puerile fanboism.  You are truly warped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: common sense</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-339937</link>
		<dc:creator><![CDATA[common sense]]></dc:creator>
		<pubDate>Tue, 15 Feb 2011 05:16:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-339937</guid>
		<description><![CDATA[@ Joe wrote @ February 14th, 2011 at 11:17 am

&quot;Actually that is incorrect. I can (and do) live without you very well.&quot;

It does not look like it since you keep coming at me. And beside my unfathomable charm I wonder what makes you think of me so much. Could I be right?

Now as your usual self, you state things without reference: Such as I said it was &quot;impossible&quot; to abort from side-mount or that there is some analysis showing you can actually safely abort... Anyway. 

You know what might work is to find someone, an expert, - not me of course - that could actually explain to you what needs to be done for a rigorous abort analysis. An analysis that would include proximity aero and 6-DOF at various point on ascent at different angles of attack that include on-pad, max-Q, max-alpha-Q, max-alpha, max-Mach, max-heating to name a few. With such a configuration you may need max side slip as well since the vehicle is not symmetric. LAS release analysis and re-contact. Re-contact with burning solids. Etc etc. Aerothermal analysis of plume impingement would have to be done with the actual vehicle with all systems and TPS. The LAS would have to be sized for the associated ascent trajectory. I&#039;ll grant you that it may have been done already and that I am just ignorant. But until I see the analysis and that it shows it can be done I&#039;ll say that there is a high risk of killing the crew... on abort from side-mount. 

And the preliminary analysis you linked to just does not cut it. 

Oh well...]]></description>
		<content:encoded><![CDATA[<p>@ Joe wrote @ February 14th, 2011 at 11:17 am</p>
<p>&#8220;Actually that is incorrect. I can (and do) live without you very well.&#8221;</p>
<p>It does not look like it since you keep coming at me. And beside my unfathomable charm I wonder what makes you think of me so much. Could I be right?</p>
<p>Now as your usual self, you state things without reference: Such as I said it was &#8220;impossible&#8221; to abort from side-mount or that there is some analysis showing you can actually safely abort&#8230; Anyway. </p>
<p>You know what might work is to find someone, an expert, &#8211; not me of course &#8211; that could actually explain to you what needs to be done for a rigorous abort analysis. An analysis that would include proximity aero and 6-DOF at various point on ascent at different angles of attack that include on-pad, max-Q, max-alpha-Q, max-alpha, max-Mach, max-heating to name a few. With such a configuration you may need max side slip as well since the vehicle is not symmetric. LAS release analysis and re-contact. Re-contact with burning solids. Etc etc. Aerothermal analysis of plume impingement would have to be done with the actual vehicle with all systems and TPS. The LAS would have to be sized for the associated ascent trajectory. I&#8217;ll grant you that it may have been done already and that I am just ignorant. But until I see the analysis and that it shows it can be done I&#8217;ll say that there is a high risk of killing the crew&#8230; on abort from side-mount. </p>
<p>And the preliminary analysis you linked to just does not cut it. </p>
<p>Oh well&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Das Boese</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-339899</link>
		<dc:creator><![CDATA[Das Boese]]></dc:creator>
		<pubDate>Mon, 14 Feb 2011 22:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-339899</guid>
		<description><![CDATA[VirgilSamms wrote @ February 14th, 2011 at 3:21 pm

&lt;cite&gt;Nothing on earth except soyuz has a longer flight heritage than the ATK and Astrium hardware.&lt;/cite&gt;

None of the components have ever flown in the proposed configuration, so I&#039;m not sure where you see &quot;flight heritage&quot;.

&lt;cite&gt;That is why it is going to be the next soyuz and the launcher of choice for the next half century.&lt;/cite&gt;

I find that hard to believe as it has none of the economic advantages or versatility that Soyuz offers.
The &quot;next Soyuz&quot; will be Soyuz with some upgrades, competing in a diversified market.

&lt;cite&gt;Falcon was lucky twice but I expect that cluster to blow up on the pad next time. I will keep my fingers crossed.&lt;/cite&gt;

I think you will find your expectation unfounded.
Engineers don&#039;t believe in luck, at SpaceX or anywhere.
Well okay, maybe at NASA and whoever builds the external tank for them (Lockheed, was it?).]]></description>
		<content:encoded><![CDATA[<p>VirgilSamms wrote @ February 14th, 2011 at 3:21 pm</p>
<p><cite>Nothing on earth except soyuz has a longer flight heritage than the ATK and Astrium hardware.</cite></p>
<p>None of the components have ever flown in the proposed configuration, so I&#8217;m not sure where you see &#8220;flight heritage&#8221;.</p>
<p><cite>That is why it is going to be the next soyuz and the launcher of choice for the next half century.</cite></p>
<p>I find that hard to believe as it has none of the economic advantages or versatility that Soyuz offers.<br />
The &#8220;next Soyuz&#8221; will be Soyuz with some upgrades, competing in a diversified market.</p>
<p><cite>Falcon was lucky twice but I expect that cluster to blow up on the pad next time. I will keep my fingers crossed.</cite></p>
<p>I think you will find your expectation unfounded.<br />
Engineers don&#8217;t believe in luck, at SpaceX or anywhere.<br />
Well okay, maybe at NASA and whoever builds the external tank for them (Lockheed, was it?).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aremis Asling</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-339898</link>
		<dc:creator><![CDATA[Aremis Asling]]></dc:creator>
		<pubDate>Mon, 14 Feb 2011 22:16:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-339898</guid>
		<description><![CDATA[&quot;But then, if youâ€™ve been following the threads, crew survivability isnâ€™t a priority so much as hardware with some of the shills for SpaceX.&quot;

Yes, I&#039;m a SpaceX fan.  But considering what they&#039;ve accomplished thus far and the track record of every company before it that has tried it, I&#039;d say there&#039;s good reason to be one.  That said, I&#039;m really more of a commercial space fan, andI&#039;m excited to see the other players in the field.  But for one, no one else has yet launched anything, so it&#039;s just hard to get enthused about them.  Also discouraging for those of us that are commercial fans, the rest of the players in the field are far more tight-lipped about progress.  It&#039;s business prudence, I understand, and I don&#039;t blame them.  But it&#039;s hard to get excited about news you never get.

My issue is not that I feel SpaceX is the one-and-only option, I don&#039;t.  Heck, they may not even be the best option.  My issue is that people pan them as an inevitable failure (why?  I don&#039;t know, perhaps because it&#039;s a day that ends in &#039;y&#039;), or tout another system as a shoe-in over some perceived inferiority SpaceX has that I&#039;ve never seen anyone actually prove.  That annoys me.  So I respond to it.]]></description>
		<content:encoded><![CDATA[<p>&#8220;But then, if youâ€™ve been following the threads, crew survivability isnâ€™t a priority so much as hardware with some of the shills for SpaceX.&#8221;</p>
<p>Yes, I&#8217;m a SpaceX fan.  But considering what they&#8217;ve accomplished thus far and the track record of every company before it that has tried it, I&#8217;d say there&#8217;s good reason to be one.  That said, I&#8217;m really more of a commercial space fan, andI&#8217;m excited to see the other players in the field.  But for one, no one else has yet launched anything, so it&#8217;s just hard to get enthused about them.  Also discouraging for those of us that are commercial fans, the rest of the players in the field are far more tight-lipped about progress.  It&#8217;s business prudence, I understand, and I don&#8217;t blame them.  But it&#8217;s hard to get excited about news you never get.</p>
<p>My issue is not that I feel SpaceX is the one-and-only option, I don&#8217;t.  Heck, they may not even be the best option.  My issue is that people pan them as an inevitable failure (why?  I don&#8217;t know, perhaps because it&#8217;s a day that ends in &#8216;y&#8217;), or tout another system as a shoe-in over some perceived inferiority SpaceX has that I&#8217;ve never seen anyone actually prove.  That annoys me.  So I respond to it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aremis Asling</title>
		<link>http://www.spacepolitics.com/2011/02/12/house-appropriators-cut-deeper-at-nasa/#comment-339896</link>
		<dc:creator><![CDATA[Aremis Asling]]></dc:creator>
		<pubDate>Mon, 14 Feb 2011 22:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=4420#comment-339896</guid>
		<description><![CDATA[&quot;Nothing on earth except soyuz has a longer flight heritage than the ATK and Astrium hardware&quot;

Than ATK and Astrium hardware?  Sure.  But not in the configuration they plan.  A 5 segment SRB has never flown, and the Astrium hardware has never played the role it&#039;s playing in this new design.  I&#039;m sure it will fly.  At least I very much hope it does.  But to say this brand new rocket can ride in on the flight heritage of its components is simply incorrect.  It certainly helps, but a lot of reliable components do not constitute a reliable rocket.

F9/Dragon will have been flying successfully in substantially the same configuration, save for improvements from lessons learned, for that entire period.]]></description>
		<content:encoded><![CDATA[<p>&#8220;Nothing on earth except soyuz has a longer flight heritage than the ATK and Astrium hardware&#8221;</p>
<p>Than ATK and Astrium hardware?  Sure.  But not in the configuration they plan.  A 5 segment SRB has never flown, and the Astrium hardware has never played the role it&#8217;s playing in this new design.  I&#8217;m sure it will fly.  At least I very much hope it does.  But to say this brand new rocket can ride in on the flight heritage of its components is simply incorrect.  It certainly helps, but a lot of reliable components do not constitute a reliable rocket.</p>
<p>F9/Dragon will have been flying successfully in substantially the same configuration, save for improvements from lessons learned, for that entire period.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
