<?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: Space issues in the House DOD appropriations report</title>
	<atom:link href="http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=space-issues-in-the-house-dod-appropriations-report</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: Royce Jones</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-267342</link>
		<dc:creator><![CDATA[Royce Jones]]></dc:creator>
		<pubDate>Wed, 02 Sep 2009 08:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-267342</guid>
		<description><![CDATA[Actually, it was the Air Force that messed things up. First, winged shuttle to meet their imaginary cross range requirements, then with the help of Congress raping the Shuttles of commercial and DoD payloads - to protect the ELV and later EELVs from competition. The net effect was the loss of 100% of the commerical satellite market in the US. Now the Air Force pays 100% of the cost of the EELVs and over $200 million a year just to maintain the ground operations. 

Fred is right - the EELV are a Air Force program - because they have no other customers other than the Air Force and the Air Force pays for all of the costs of the program. Also, the EELV companies where allowed to write off their investments on their taxes - so really they paid nothing.

NASA looked at man rating the EELVs many times (Orbital Spaceplane for example) and always came to the same conclusion - too expensive. Now the EELVs are being low balled priced - again - as an option to Ares 1. Fact is both are bad choices.

The COTS vehicles are not low cost vehicles either. Because of the low lift capability they are actually very expensive, expecially the OSC vehicle.

Maybe its time for the Air Force, NASA and others to sit down and come up with a plan - not a political plan - but a financial plan that works. Good luck with that.]]></description>
		<content:encoded><![CDATA[<p>Actually, it was the Air Force that messed things up. First, winged shuttle to meet their imaginary cross range requirements, then with the help of Congress raping the Shuttles of commercial and DoD payloads &#8211; to protect the ELV and later EELVs from competition. The net effect was the loss of 100% of the commerical satellite market in the US. Now the Air Force pays 100% of the cost of the EELVs and over $200 million a year just to maintain the ground operations. </p>
<p>Fred is right &#8211; the EELV are a Air Force program &#8211; because they have no other customers other than the Air Force and the Air Force pays for all of the costs of the program. Also, the EELV companies where allowed to write off their investments on their taxes &#8211; so really they paid nothing.</p>
<p>NASA looked at man rating the EELVs many times (Orbital Spaceplane for example) and always came to the same conclusion &#8211; too expensive. Now the EELVs are being low balled priced &#8211; again &#8211; as an option to Ares 1. Fact is both are bad choices.</p>
<p>The COTS vehicles are not low cost vehicles either. Because of the low lift capability they are actually very expensive, expecially the OSC vehicle.</p>
<p>Maybe its time for the Air Force, NASA and others to sit down and come up with a plan &#8211; not a political plan &#8211; but a financial plan that works. Good luck with that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Revloc</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265910</link>
		<dc:creator><![CDATA[Revloc]]></dc:creator>
		<pubDate>Tue, 18 Aug 2009 03:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265910</guid>
		<description><![CDATA[Fred is wrong. The EELV rockets were developed and are owned by ULA (Boeing and Lockheed-Martin) The Air Force is just buying launch services. During EELV development the Air Force provided just $500 million each to both companies to acquire 1st in-line launch service availability. The designs, facilities, and tooling for both Atlas V and Delta IV are owned by ULA. ULA can man-rate their vehicles if NASA asks them to. The Air Force can&#039;t dictate to ULA a no man-rate condition.]]></description>
		<content:encoded><![CDATA[<p>Fred is wrong. The EELV rockets were developed and are owned by ULA (Boeing and Lockheed-Martin) The Air Force is just buying launch services. During EELV development the Air Force provided just $500 million each to both companies to acquire 1st in-line launch service availability. The designs, facilities, and tooling for both Atlas V and Delta IV are owned by ULA. ULA can man-rate their vehicles if NASA asks them to. The Air Force can&#8217;t dictate to ULA a no man-rate condition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rand Simberg</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265532</link>
		<dc:creator><![CDATA[Rand Simberg]]></dc:creator>
		<pubDate>Thu, 13 Aug 2009 21:44:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265532</guid>
		<description><![CDATA[&lt;em&gt;And of course there is the requirement for a design load factor increase from 1.25 to 1.4, a safety factor from the days before computers, even though actual flight loads can be validated in unmanned flight.&lt;/em&gt;

A truly stupid requirement.  If it added reliability, the launch insurance industry would insist on it for satellite launches.]]></description>
		<content:encoded><![CDATA[<p><em>And of course there is the requirement for a design load factor increase from 1.25 to 1.4, a safety factor from the days before computers, even though actual flight loads can be validated in unmanned flight.</em></p>
<p>A truly stupid requirement.  If it added reliability, the launch insurance industry would insist on it for satellite launches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DD</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265529</link>
		<dc:creator><![CDATA[DD]]></dc:creator>
		<pubDate>Thu, 13 Aug 2009 20:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265529</guid>
		<description><![CDATA[I agree completely with Jon on this. NASA man-rating adds a lot of cost for little safety, but unfortunately NASA will not accept the EELV unless they can make whatever changes they want. Nobody is going to hand-fly a rocket into orbit, yet that is always a requirement. And of course there is the requirement for a design load factor increase from 1.25 to 1.4, a safety factor from the days before computers, even though actual flight loads can be validated in unmanned flight. Although ULA has some pretty good designs, they essentially sell only to the government, a cost-insensitive customer, and so their costs are not as tightly controlled as they could be. But even DOD will not pay for man-rating when they have no requirement for it. Only hope would be if ULA is willing to dedicate the Delta (or at least a new variant of it) to NASA.]]></description>
		<content:encoded><![CDATA[<p>I agree completely with Jon on this. NASA man-rating adds a lot of cost for little safety, but unfortunately NASA will not accept the EELV unless they can make whatever changes they want. Nobody is going to hand-fly a rocket into orbit, yet that is always a requirement. And of course there is the requirement for a design load factor increase from 1.25 to 1.4, a safety factor from the days before computers, even though actual flight loads can be validated in unmanned flight. Although ULA has some pretty good designs, they essentially sell only to the government, a cost-insensitive customer, and so their costs are not as tightly controlled as they could be. But even DOD will not pay for man-rating when they have no requirement for it. Only hope would be if ULA is willing to dedicate the Delta (or at least a new variant of it) to NASA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Major Tom</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265346</link>
		<dc:creator><![CDATA[Major Tom]]></dc:creator>
		<pubDate>Tue, 11 Aug 2009 20:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265346</guid>
		<description><![CDATA[&quot;There are rumours the Air Force has vetoed changes to EELVs.&quot;  [Mr. Meijering]

I won&#039;t try to confirm or dispute the rumors, but it&#039;s important to point out that human-rating changes don&#039;t have to (and probably shouldn&#039;t) be incorporated in every Delta IV or Atlas V that leaves Decatur.  ULA can develop and produce a modified, variant EELV for NASA crew launches, while still using the same workforce and facilities to produce unmodified EELVs for USAF, NRO, NASA unmanned, and commercial customers.  It would largely be the same assembly sequence, but for crewed variants, the sequence would fork at a couple points for redundant avionics and engine diagnostics.  Unmodified EELVs should remain at the same price (or lower -- see below), while NASA pays some modest premium for its modified EELV variants for crew launch.

And in terms of costs, there&#039;s no reason for the USAF to pay for those modifications or for an extra EELV pad at the Cape for NASA crewed launch needs.  And even if national security users did share in some of those costs (say, because greater engine reliability will benefit high-value NRO payloads), they&#039;d quickly recoup their investment by spreading the costs of the EELV industrial base over a substantially larger customer base.  If anything, unmodified EELVs should go down in price somewhat if NASA crew launches are added to the EELV customer base.

As an aside, the cost of unmodified EELVs will go way down if NASA goes the in-space propellant provisioning route and uses EELV to supply propellant on orbit.  See how much EELV demand grows on page 4 of this presentation if such moves were made:

http://www.ulalaunch.com/docs/publications/PropellantDepotJPC2009.pdf

&quot;And if MSFC gets the job of approving the Delta and itâ€™s man rating - that will be REALLY EXPENSIVE!... They have to justify their workforce and will find LOTS of problems that should or could be fixed.&quot;  [Charles]

The key is to give the bulk of NASA human space flight workforce something else to do.  This was one of the major flaws of ESAS -- instead of redirecting NASA&#039;s human space flight workforce to exploration activities per the VSE, it got them wrapped around the axle of another mid-range LEO launcher.  NASA should do what industry isn&#039;t doing, can&#039;t do, or won&#039;t do, and mid-range launch to LEO is something that industry has been doing well for years.  Between heavy lift, in-space propellant provisioning, in-space transit, landers, etc., there&#039;s plenty other things for the NASA human space flight workforce to do.

FWIW...]]></description>
		<content:encoded><![CDATA[<p>&#8220;There are rumours the Air Force has vetoed changes to EELVs.&#8221;  [Mr. Meijering]</p>
<p>I won&#8217;t try to confirm or dispute the rumors, but it&#8217;s important to point out that human-rating changes don&#8217;t have to (and probably shouldn&#8217;t) be incorporated in every Delta IV or Atlas V that leaves Decatur.  ULA can develop and produce a modified, variant EELV for NASA crew launches, while still using the same workforce and facilities to produce unmodified EELVs for USAF, NRO, NASA unmanned, and commercial customers.  It would largely be the same assembly sequence, but for crewed variants, the sequence would fork at a couple points for redundant avionics and engine diagnostics.  Unmodified EELVs should remain at the same price (or lower &#8212; see below), while NASA pays some modest premium for its modified EELV variants for crew launch.</p>
<p>And in terms of costs, there&#8217;s no reason for the USAF to pay for those modifications or for an extra EELV pad at the Cape for NASA crewed launch needs.  And even if national security users did share in some of those costs (say, because greater engine reliability will benefit high-value NRO payloads), they&#8217;d quickly recoup their investment by spreading the costs of the EELV industrial base over a substantially larger customer base.  If anything, unmodified EELVs should go down in price somewhat if NASA crew launches are added to the EELV customer base.</p>
<p>As an aside, the cost of unmodified EELVs will go way down if NASA goes the in-space propellant provisioning route and uses EELV to supply propellant on orbit.  See how much EELV demand grows on page 4 of this presentation if such moves were made:</p>
<p><a href="http://www.ulalaunch.com/docs/publications/PropellantDepotJPC2009.pdf" rel="nofollow">http://www.ulalaunch.com/docs/publications/PropellantDepotJPC2009.pdf</a></p>
<p>&#8220;And if MSFC gets the job of approving the Delta and itâ€™s man rating &#8211; that will be REALLY EXPENSIVE!&#8230; They have to justify their workforce and will find LOTS of problems that should or could be fixed.&#8221;  [Charles]</p>
<p>The key is to give the bulk of NASA human space flight workforce something else to do.  This was one of the major flaws of ESAS &#8212; instead of redirecting NASA&#8217;s human space flight workforce to exploration activities per the VSE, it got them wrapped around the axle of another mid-range LEO launcher.  NASA should do what industry isn&#8217;t doing, can&#8217;t do, or won&#8217;t do, and mid-range launch to LEO is something that industry has been doing well for years.  Between heavy lift, in-space propellant provisioning, in-space transit, landers, etc., there&#8217;s plenty other things for the NASA human space flight workforce to do.</p>
<p>FWIW&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martijn Meijering</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265338</link>
		<dc:creator><![CDATA[Martijn Meijering]]></dc:creator>
		<pubDate>Tue, 11 Aug 2009 19:16:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265338</guid>
		<description><![CDATA[I would love to know the details of what happened.

I agree national security trumps the needs of the civil space program, but that doesn&#039;t mean the issue cannot be discussed openly. I don&#039;t see why national security would be harmed if the DoD were to say &quot;we don&#039;t want those clowns from MSFC messing around with our launchers&quot;. Also, this only applies to the CLV, there is no reason to rule out EELVs as propellant launchers or for launching Altair. This would actually help with establishing reliability, and the same thing could be done with Falcon.

Keeping these considerations secret also undermines the whole FACA process. I imagine this would actually be illegal, unless the president signs some kind of finding and this is somehow communicated to the appropriate oversight bodies in Congress. And legal considerations aside, I cannot believe the White House would tolerate any of this happening without their consent. I wonder how the order was passed down the chain of command and whether General Jones&#039; review of launch systems had anything to do with it.]]></description>
		<content:encoded><![CDATA[<p>I would love to know the details of what happened.</p>
<p>I agree national security trumps the needs of the civil space program, but that doesn&#8217;t mean the issue cannot be discussed openly. I don&#8217;t see why national security would be harmed if the DoD were to say &#8220;we don&#8217;t want those clowns from MSFC messing around with our launchers&#8221;. Also, this only applies to the CLV, there is no reason to rule out EELVs as propellant launchers or for launching Altair. This would actually help with establishing reliability, and the same thing could be done with Falcon.</p>
<p>Keeping these considerations secret also undermines the whole FACA process. I imagine this would actually be illegal, unless the president signs some kind of finding and this is somehow communicated to the appropriate oversight bodies in Congress. And legal considerations aside, I cannot believe the White House would tolerate any of this happening without their consent. I wonder how the order was passed down the chain of command and whether General Jones&#8217; review of launch systems had anything to do with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CharlesTheSpaceGuy</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265335</link>
		<dc:creator><![CDATA[CharlesTheSpaceGuy]]></dc:creator>
		<pubDate>Tue, 11 Aug 2009 18:38:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265335</guid>
		<description><![CDATA[For the EELV (almost certainly the Delta) to be man-rated, NASA would have to pony up the money for it. The AF would not allow it&#039;s launcher price to be increased due to requirements for man rating. 

And if MSFC gets the job of approving the Delta and it&#039;s man rating - that will be REALLY EXPENSIVE! Mainly since MSFC will have great motivation to prove that they are needed to sign off on every nit. They have to justify their workforce and will find LOTS of problems that should or could be fixed. 

The AF will not want to allow NASA to determine if their launcher is safe to fly, from painful experience.]]></description>
		<content:encoded><![CDATA[<p>For the EELV (almost certainly the Delta) to be man-rated, NASA would have to pony up the money for it. The AF would not allow it&#8217;s launcher price to be increased due to requirements for man rating. </p>
<p>And if MSFC gets the job of approving the Delta and it&#8217;s man rating &#8211; that will be REALLY EXPENSIVE! Mainly since MSFC will have great motivation to prove that they are needed to sign off on every nit. They have to justify their workforce and will find LOTS of problems that should or could be fixed. </p>
<p>The AF will not want to allow NASA to determine if their launcher is safe to fly, from painful experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Norm Hartnett</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265331</link>
		<dc:creator><![CDATA[Norm Hartnett]]></dc:creator>
		<pubDate>Tue, 11 Aug 2009 18:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265331</guid>
		<description><![CDATA[This decision was made several pay grades above the Augustine Committee level. National security trumps human space flight. The decision is based on the past history of the interaction between national security space access and NASA space access. Basically NASA made promises they couldn&#039;t keep and those promises lead to disassembly of the nation&#039;s launch vehicle capabilities. This directly lead to the EELV program once it became clear that NASA couldn&#039;t meet it&#039;s obligations.

To be fair there was, as usual, much political interference which lead to this mess.

They made their bed, now they and the human space program have to sleep in it.]]></description>
		<content:encoded><![CDATA[<p>This decision was made several pay grades above the Augustine Committee level. National security trumps human space flight. The decision is based on the past history of the interaction between national security space access and NASA space access. Basically NASA made promises they couldn&#8217;t keep and those promises lead to disassembly of the nation&#8217;s launch vehicle capabilities. This directly lead to the EELV program once it became clear that NASA couldn&#8217;t meet it&#8217;s obligations.</p>
<p>To be fair there was, as usual, much political interference which lead to this mess.</p>
<p>They made their bed, now they and the human space program have to sleep in it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martijn Meijering</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265311</link>
		<dc:creator><![CDATA[Martijn Meijering]]></dc:creator>
		<pubDate>Tue, 11 Aug 2009 11:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265311</guid>
		<description><![CDATA[It&#039;s disappointing that this is not said openly and even more disappointing the Augustine panel goes along with this.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s disappointing that this is not said openly and even more disappointing the Augustine panel goes along with this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.spacepolitics.com/2009/08/09/space-issues-in-the-house-dod-appropriations-report/#comment-265304</link>
		<dc:creator><![CDATA[Fred]]></dc:creator>
		<pubDate>Tue, 11 Aug 2009 08:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=2524#comment-265304</guid>
		<description><![CDATA[It&#039;s not a rumour, and it&#039;s not particularly sinister. Both EELV&#039;s are paid for by the Air Force. They are AF LV&#039;s.  The AF are quite happy for NASA to use &#039;em for sat launches. Indeed they encourage this. They just don&#039;t want NASA to start trying to man rate them as they&#039;re afraid this would add to the cost of the EELV&#039;s. Given the history of NASA&#039;s development efforts who can blame them.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s not a rumour, and it&#8217;s not particularly sinister. Both EELV&#8217;s are paid for by the Air Force. They are AF LV&#8217;s.  The AF are quite happy for NASA to use &#8216;em for sat launches. Indeed they encourage this. They just don&#8217;t want NASA to start trying to man rate them as they&#8217;re afraid this would add to the cost of the EELV&#8217;s. Given the history of NASA&#8217;s development efforts who can blame them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
