<?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 policy challenges and strategies to be discussed this week</title>
	<atom:link href="http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=space-policy-challenges-and-strategies-to-be-discussed-this-week</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: SarK0Y</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-402375</link>
		<dc:creator><![CDATA[SarK0Y]]></dc:creator>
		<pubDate>Fri, 08 Mar 2013 20:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-402375</guid>
		<description><![CDATA[&lt;b&gt;Dark&lt;/b&gt;, keep in mind, missions have carried too light payloads, thereby it gives room for additional reliability.]]></description>
		<content:encoded><![CDATA[<p><b>Dark</b>, keep in mind, missions have carried too light payloads, thereby it gives room for additional reliability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-387404</link>
		<dc:creator><![CDATA[joe]]></dc:creator>
		<pubDate>Thu, 06 Dec 2012 22:11:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-387404</guid>
		<description><![CDATA[Nowhere in this discussion did I call CRS-1 a success.  So I am forgeting nothing.

You seriously need to get some kind of a grip.]]></description>
		<content:encoded><![CDATA[<p>Nowhere in this discussion did I call CRS-1 a success.  So I am forgeting nothing.</p>
<p>You seriously need to get some kind of a grip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coastal Ron</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-387393</link>
		<dc:creator><![CDATA[Coastal Ron]]></dc:creator>
		<pubDate>Thu, 06 Dec 2012 21:32:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-387393</guid>
		<description><![CDATA[joe said:

&quot;&lt;i&gt;I guess this better sum up this â€œdebateâ€.&lt;/i&gt;&quot;

Except it seems you&#039;re changing, yet again, what you&#039;re talking about.  Previously you said &quot;Get back to me when SpaceX can make the one rocket they actually have work.&quot;, and I pointed out that the Falcon 9 did work for it&#039;s primary mission.  The Falcon 9 also had a flawless previous flight on the COTS-2/3 flight, so they actually do have a history of rockets that actually work.

Now you&#039;re slicing and dicing to pick out something that shows the Falcon 9 isn&#039;t perfect.  Well OK, it&#039;s not perfect.  There, I said it.  We good?

&quot;&lt;i&gt;I try very hard to avoid the kind of personal insults you (and others around here) deal in routinely, but if anyone has â€œa medical issueâ€ that needs addressing it is not me.&lt;/i&gt;&quot;

Well that&#039;s good to know, but how do you explain your forgetfulness?

No need to answer, as I&#039;m off to new conversations...]]></description>
		<content:encoded><![CDATA[<p>joe said:</p>
<p>&#8220;<i>I guess this better sum up this â€œdebateâ€.</i>&#8221;</p>
<p>Except it seems you&#8217;re changing, yet again, what you&#8217;re talking about.  Previously you said &#8220;Get back to me when SpaceX can make the one rocket they actually have work.&#8221;, and I pointed out that the Falcon 9 did work for it&#8217;s primary mission.  The Falcon 9 also had a flawless previous flight on the COTS-2/3 flight, so they actually do have a history of rockets that actually work.</p>
<p>Now you&#8217;re slicing and dicing to pick out something that shows the Falcon 9 isn&#8217;t perfect.  Well OK, it&#8217;s not perfect.  There, I said it.  We good?</p>
<p>&#8220;<i>I try very hard to avoid the kind of personal insults you (and others around here) deal in routinely, but if anyone has â€œa medical issueâ€ that needs addressing it is not me.</i>&#8221;</p>
<p>Well that&#8217;s good to know, but how do you explain your forgetfulness?</p>
<p>No need to answer, as I&#8217;m off to new conversations&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-387378</link>
		<dc:creator><![CDATA[joe]]></dc:creator>
		<pubDate>Thu, 06 Dec 2012 20:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-387378</guid>
		<description><![CDATA[Ron,

I guess this better sum up this &quot;debate&quot;.

- They lost another payload that was flying on CRS-1.  
- The Falcon 9 literally blew chunks off itself during ascent.
- There is currently an investigation underway to determine the cause of the incident.
- The Falcon 9 next flight has been delayed to no earlier than March 2013 (and will likely be delayed beyond that)

And you wish to characterize that as a success.  

I try very hard to avoid the kind of personal insults you (and others around here) deal in routinely, but if anyone has â€œa medical issueâ€ that needs addressing it is not me.

Have a nice day,

Joe]]></description>
		<content:encoded><![CDATA[<p>Ron,</p>
<p>I guess this better sum up this &#8220;debate&#8221;.</p>
<p>&#8211; They lost another payload that was flying on CRS-1.<br />
&#8211; The Falcon 9 literally blew chunks off itself during ascent.<br />
&#8211; There is currently an investigation underway to determine the cause of the incident.<br />
&#8211; The Falcon 9 next flight has been delayed to no earlier than March 2013 (and will likely be delayed beyond that)</p>
<p>And you wish to characterize that as a success.  </p>
<p>I try very hard to avoid the kind of personal insults you (and others around here) deal in routinely, but if anyone has â€œa medical issueâ€ that needs addressing it is not me.</p>
<p>Have a nice day,</p>
<p>Joe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coastal Ron</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-387374</link>
		<dc:creator><![CDATA[Coastal Ron]]></dc:creator>
		<pubDate>Thu, 06 Dec 2012 20:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-387374</guid>
		<description><![CDATA[joe mumbled:

&quot;&lt;i&gt;Get back to me when SpaceX can make the one rocket they actually have work.&lt;/i&gt;&quot;

What&#039;s to get back to your about?  The CRS-1 mission was a success - Dragon was put in it&#039;s proper orbit, and it even docked at the ISS ahead of schedule.

You even admitted that it was a success, so are forgetting what you said?  Sounds like a medical issue you need to address Joe...]]></description>
		<content:encoded><![CDATA[<p>joe mumbled:</p>
<p>&#8220;<i>Get back to me when SpaceX can make the one rocket they actually have work.</i>&#8221;</p>
<p>What&#8217;s to get back to your about?  The CRS-1 mission was a success &#8211; Dragon was put in it&#8217;s proper orbit, and it even docked at the ISS ahead of schedule.</p>
<p>You even admitted that it was a success, so are forgetting what you said?  Sounds like a medical issue you need to address Joe&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-387352</link>
		<dc:creator><![CDATA[joe]]></dc:creator>
		<pubDate>Thu, 06 Dec 2012 19:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-387352</guid>
		<description><![CDATA[You guys sure do like crowing about things that have not been done.

Get back to me when SpaceX can make the one rocket they actually have work.]]></description>
		<content:encoded><![CDATA[<p>You guys sure do like crowing about things that have not been done.</p>
<p>Get back to me when SpaceX can make the one rocket they actually have work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Shipley</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-387057</link>
		<dc:creator><![CDATA[Neil Shipley]]></dc:creator>
		<pubDate>Thu, 06 Dec 2012 01:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-387057</guid>
		<description><![CDATA[Hey Joe.  
Seeing that you&#039;re a concerned citizen regarding the performance of SpaceX, would you like to comment on the fact that SpaceX has just been awarded a couple of satellite launches for the DoD?  This after their recent performance to the ISS and they are also for 2 &#039;new&#039; vehicles - F9v1.1 upgraded F9 (you know, 10 engines all up) and their new FH (28 engines all up).

Breaking the mould methinks.  ULA&#039;s going to have to do something about their cost structure else their business is &#039;gone&#039;.]]></description>
		<content:encoded><![CDATA[<p>Hey Joe.<br />
Seeing that you&#8217;re a concerned citizen regarding the performance of SpaceX, would you like to comment on the fact that SpaceX has just been awarded a couple of satellite launches for the DoD?  This after their recent performance to the ISS and they are also for 2 &#8216;new&#8217; vehicles &#8211; F9v1.1 upgraded F9 (you know, 10 engines all up) and their new FH (28 engines all up).</p>
<p>Breaking the mould methinks.  ULA&#8217;s going to have to do something about their cost structure else their business is &#8216;gone&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coastal Ron</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-387019</link>
		<dc:creator><![CDATA[Coastal Ron]]></dc:creator>
		<pubDate>Wed, 05 Dec 2012 21:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-387019</guid>
		<description><![CDATA[joe said:

&quot;&lt;i&gt;Not next to them, but around the area, that is why they will not take chances on flying a rocket that has had repeated potentially dangerous malfunctions until those issues are resolved. There is always additional risk when flying any rocket, but (at least if you are the Range Safety Office) you are not going to exacerbate that risk by allowing a rocket to fly that has an unresolved known flaw.&lt;/i&gt;&quot;

I would disagree with your definition of range safety.  They are not rocket inspectors, so they are not validating the design of the rockets that use the range.  Their job is to mitigate damage when things go wrong.

For instance, they have control over the self destruct mechanisms on each rocket, which they can activate if they feel the rocket is not following it&#039;s intended route and could endanger people and property.  They already know what the planned debris pattern is supposed to be everywhere along the route the rocket will take prior to self-destruct, so I think they would tell you that &quot;residents&quot; and &quot;residents who work at CCAFS&quot; are not in any danger.  And they have blown up a lot of rockets (and watched quite a few blow up on their own), so I think they have their processes and procedures pretty well worked out.

This is a non-issue.

As to your &quot;unresolved known flaw&quot; comment, calling it a &quot;known flaw&quot; is unsubstantiated.  It was a failure, and not one that had been seen previously.  It might not have even been an engine issue, but one involving a tank or plumbing upstream of the engine.

And it may turn out that no root cause is ever found for this issue, especially if it is not a design issue but a manufacturing or assembly defect.  That&#039;s the problem with single use vehicles, is that it&#039;s difficult to get absolute resolution of problems when you can&#039;t examine the actual item.

SpaceX is also at an interesting inflection point, in that they only have one more launch of this design of the Falcon 9 before changing over to a pretty much completely new design (v1.1).  If they can&#039;t find any obvious root cause for the shutdown, then it will be up to SpaceX and NASA to determine if they will go ahead with the next flight as planned (i.e. Falcon 9 v1.0) or push out the flight to when they can use the new (and currently unproven) v1.1 of the Falcon 9.

This is not a business for the faint hearted, as Musk has explained many times.  We&#039;ll see.]]></description>
		<content:encoded><![CDATA[<p>joe said:</p>
<p>&#8220;<i>Not next to them, but around the area, that is why they will not take chances on flying a rocket that has had repeated potentially dangerous malfunctions until those issues are resolved. There is always additional risk when flying any rocket, but (at least if you are the Range Safety Office) you are not going to exacerbate that risk by allowing a rocket to fly that has an unresolved known flaw.</i>&#8221;</p>
<p>I would disagree with your definition of range safety.  They are not rocket inspectors, so they are not validating the design of the rockets that use the range.  Their job is to mitigate damage when things go wrong.</p>
<p>For instance, they have control over the self destruct mechanisms on each rocket, which they can activate if they feel the rocket is not following it&#8217;s intended route and could endanger people and property.  They already know what the planned debris pattern is supposed to be everywhere along the route the rocket will take prior to self-destruct, so I think they would tell you that &#8220;residents&#8221; and &#8220;residents who work at CCAFS&#8221; are not in any danger.  And they have blown up a lot of rockets (and watched quite a few blow up on their own), so I think they have their processes and procedures pretty well worked out.</p>
<p>This is a non-issue.</p>
<p>As to your &#8220;unresolved known flaw&#8221; comment, calling it a &#8220;known flaw&#8221; is unsubstantiated.  It was a failure, and not one that had been seen previously.  It might not have even been an engine issue, but one involving a tank or plumbing upstream of the engine.</p>
<p>And it may turn out that no root cause is ever found for this issue, especially if it is not a design issue but a manufacturing or assembly defect.  That&#8217;s the problem with single use vehicles, is that it&#8217;s difficult to get absolute resolution of problems when you can&#8217;t examine the actual item.</p>
<p>SpaceX is also at an interesting inflection point, in that they only have one more launch of this design of the Falcon 9 before changing over to a pretty much completely new design (v1.1).  If they can&#8217;t find any obvious root cause for the shutdown, then it will be up to SpaceX and NASA to determine if they will go ahead with the next flight as planned (i.e. Falcon 9 v1.0) or push out the flight to when they can use the new (and currently unproven) v1.1 of the Falcon 9.</p>
<p>This is not a business for the faint hearted, as Musk has explained many times.  We&#8217;ll see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-386985</link>
		<dc:creator><![CDATA[joe]]></dc:creator>
		<pubDate>Wed, 05 Dec 2012 19:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-386985</guid>
		<description><![CDATA[Sorry, I did not realize you had a patent on the phrase.]]></description>
		<content:encoded><![CDATA[<p>Sorry, I did not realize you had a patent on the phrase.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: common sense</title>
		<link>http://www.spacepolitics.com/2012/12/03/space-policy-challenges-and-strategies-to-be-discussed-this-week/#comment-386976</link>
		<dc:creator><![CDATA[common sense]]></dc:creator>
		<pubDate>Wed, 05 Dec 2012 18:34:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/?p=6060#comment-386976</guid>
		<description><![CDATA[&quot;In fact I find most of the general populace to have a reassuring amount of (you should excuse the expression) common sense.&quot;

Okay this time but you should not use my name in vain.]]></description>
		<content:encoded><![CDATA[<p>&#8220;In fact I find most of the general populace to have a reassuring amount of (you should excuse the expression) common sense.&#8221;</p>
<p>Okay this time but you should not use my name in vain.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
