<?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: SpaceX&#8217;s loses launch contract due to scheduling delays	</title>
	<atom:link href="https://behindtheblack.com/behind-the-black/points-of-information/spacexs-loses-launch-contract-due-to-scheduling-delays/feed/" rel="self" type="application/rss+xml" />
	<link>https://behindtheblack.com/behind-the-black/points-of-information/spacexs-loses-launch-contract-due-to-scheduling-delays/</link>
	<description></description>
	<lastBuildDate>Fri, 09 Dec 2016 04:36:16 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Edward		</title>
		<link>https://behindtheblack.com/behind-the-black/points-of-information/spacexs-loses-launch-contract-due-to-scheduling-delays/#comment-950930</link>

		<dc:creator><![CDATA[Edward]]></dc:creator>
		<pubDate>Fri, 09 Dec 2016 04:36:16 +0000</pubDate>
		<guid isPermaLink="false">http://behindtheblack.com/?p=43109#comment-950930</guid>

					<description><![CDATA[ken anthony, 
It would be a good take, except that it assumes that SpaceX could have been flying for a couple of months.  

So far, I have seen no evidence that SpaceX yet has confidence in the new procedures that they have said should solve the problem, and with this latest delay, I see evidence that they still do not have enough confidence to fly and may even be considering tweaking or testing the procedure some more.  

Having been on the problem solving side of faulty or misbehaving spaceflight hardware, I know that these things are not rushed.  Rushing is how other problems are missed and how accidents happen.  

A company or team that does not fully understand the process can end up with a rocket exploding on the pad due to unexpected reactions, and oh!, that&#039;s just what happened to SpaceX.  I think it is likely that they are being especially cautious, this time.  

Since their site is announced as &quot;&lt;i&gt;Random Musings from the Warped Minds of ...,&lt;/i&gt;&quot; I suspect that Selenian Boondocks does not want us to take their musings too seriously.]]></description>
			<content:encoded><![CDATA[<p>ken anthony,<br />
It would be a good take, except that it assumes that SpaceX could have been flying for a couple of months.  </p>
<p>So far, I have seen no evidence that SpaceX yet has confidence in the new procedures that they have said should solve the problem, and with this latest delay, I see evidence that they still do not have enough confidence to fly and may even be considering tweaking or testing the procedure some more.  </p>
<p>Having been on the problem solving side of faulty or misbehaving spaceflight hardware, I know that these things are not rushed.  Rushing is how other problems are missed and how accidents happen.  </p>
<p>A company or team that does not fully understand the process can end up with a rocket exploding on the pad due to unexpected reactions, and oh!, that&#8217;s just what happened to SpaceX.  I think it is likely that they are being especially cautious, this time.  </p>
<p>Since their site is announced as &#8220;<i>Random Musings from the Warped Minds of &#8230;,</i>&#8221; I suspect that Selenian Boondocks does not want us to take their musings too seriously.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ken anthony		</title>
		<link>https://behindtheblack.com/behind-the-black/points-of-information/spacexs-loses-launch-contract-due-to-scheduling-delays/#comment-950908</link>

		<dc:creator><![CDATA[ken anthony]]></dc:creator>
		<pubDate>Fri, 09 Dec 2016 02:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://behindtheblack.com/?p=43109#comment-950908</guid>

					<description><![CDATA[Selenium boondocks has a good take on this.]]></description>
			<content:encoded><![CDATA[<p>Selenium boondocks has a good take on this.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Edward		</title>
		<link>https://behindtheblack.com/behind-the-black/points-of-information/spacexs-loses-launch-contract-due-to-scheduling-delays/#comment-950907</link>

		<dc:creator><![CDATA[Edward]]></dc:creator>
		<pubDate>Fri, 09 Dec 2016 02:09:28 +0000</pubDate>
		<guid isPermaLink="false">http://behindtheblack.com/?p=43109#comment-950907</guid>

					<description><![CDATA[The good news is that SpaceX is demonstrating seriousness about reliability.  They seem to be willing to lose a payload in order to assure that they have fixed their problem and will consistently launch safely.  This may be a short-term setback, but if the next many launches go well, it is likely a long-term victory.  

True or not (I think &quot;not&quot;), many people blamed pressure to launch for the Challenger disaster.  SpaceX seems to be telling the world that they would rather lose a payload to a competitor than fold from such pressure.  

Although this is not the one that went to Arianespace, EchoStar 23 has some pressure to get on orbit and be operational by the middle of next year, otherwise the Brazilian license may expire for some of the frequencies the satellite is built to use.  This may merely be an additional financial cost to EchoStar, as I am guessing that they could maintain these frequencies by paying a fine to Brazil, should they end up missing the deadline.]]></description>
			<content:encoded><![CDATA[<p>The good news is that SpaceX is demonstrating seriousness about reliability.  They seem to be willing to lose a payload in order to assure that they have fixed their problem and will consistently launch safely.  This may be a short-term setback, but if the next many launches go well, it is likely a long-term victory.  </p>
<p>True or not (I think &#8220;not&#8221;), many people blamed pressure to launch for the Challenger disaster.  SpaceX seems to be telling the world that they would rather lose a payload to a competitor than fold from such pressure.  </p>
<p>Although this is not the one that went to Arianespace, EchoStar 23 has some pressure to get on orbit and be operational by the middle of next year, otherwise the Brazilian license may expire for some of the frequencies the satellite is built to use.  This may merely be an additional financial cost to EchoStar, as I am guessing that they could maintain these frequencies by paying a fine to Brazil, should they end up missing the deadline.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ChrisL		</title>
		<link>https://behindtheblack.com/behind-the-black/points-of-information/spacexs-loses-launch-contract-due-to-scheduling-delays/#comment-950823</link>

		<dc:creator><![CDATA[ChrisL]]></dc:creator>
		<pubDate>Thu, 08 Dec 2016 18:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://behindtheblack.com/?p=43109#comment-950823</guid>

					<description><![CDATA[That&#039;s what competition is about.  If you can&#039;t meet the buyer&#039;s needs, he goes elsewhere. In the private sector, failure has consequences.]]></description>
			<content:encoded><![CDATA[<p>That&#8217;s what competition is about.  If you can&#8217;t meet the buyer&#8217;s needs, he goes elsewhere. In the private sector, failure has consequences.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
