<?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: SRB Holddown posts undergoing redesign evaluation ahead of STS-119</title>
	<atom:link href="http://www.nasaspaceflight.com/2008/12/srb-holddown-posts-undergoing-redesign-evaluation-ahead-of-sts-119/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nasaspaceflight.com/2008/12/srb-holddown-posts-undergoing-redesign-evaluation-ahead-of-sts-119/</link>
	<description>Giving space it's place on the web</description>
	<lastBuildDate>Sat, 13 Mar 2010 04:58:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: STS-125: Pad damaged during launch - Atlantis undergoing inspections &#124; NASASpaceFlight.com</title>
		<link>http://www.nasaspaceflight.com/2008/12/srb-holddown-posts-undergoing-redesign-evaluation-ahead-of-sts-119/comment-page-1/#comment-710</link>
		<dc:creator>STS-125: Pad damaged during launch - Atlantis undergoing inspections &#124; NASASpaceFlight.com</dc:creator>
		<pubDate>Tue, 12 May 2009 13:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=8365#comment-710</guid>
		<description>[...] powered off the launch pad without issue, despite what appears to be an indication that one of the studs, which hold down the Solid Rocket Boosters (SRBs) prior to T-0, suffered from a &#8220;hang-up&#8221; - which in itself is not uncommon, and would easily be [...]</description>
		<content:encoded><![CDATA[<p>[...] powered off the launch pad without issue, despite what appears to be an indication that one of the studs, which hold down the Solid Rocket Boosters (SRBs) prior to T-0, suffered from a &#8220;hang-up&#8221; &#8211; which in itself is not uncommon, and would easily be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NASASpaceFlight.com &#187; STS-119: Discovery mated to ET-127 as engineers focus on FCV issue</title>
		<link>http://www.nasaspaceflight.com/2008/12/srb-holddown-posts-undergoing-redesign-evaluation-ahead-of-sts-119/comment-page-1/#comment-245</link>
		<dc:creator>NASASpaceFlight.com &#187; STS-119: Discovery mated to ET-127 as engineers focus on FCV issue</dc:creator>
		<pubDate>Fri, 09 Jan 2009 04:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=8365#comment-245</guid>
		<description>[...] engineering meetings are taking place at the end of the week on the holddown post Debris Containment System (DCS), the main issue under evaluation relates to the requirement to replace all three of [...]</description>
		<content:encoded><![CDATA[<p>[...] engineering meetings are taking place at the end of the week on the holddown post Debris Containment System (DCS), the main issue under evaluation relates to the requirement to replace all three of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NASASpaceFlight.com &#187; Risk assessment notes holddown post debris threat to shuttle</title>
		<link>http://www.nasaspaceflight.com/2008/12/srb-holddown-posts-undergoing-redesign-evaluation-ahead-of-sts-119/comment-page-1/#comment-238</link>
		<dc:creator>NASASpaceFlight.com &#187; Risk assessment notes holddown post debris threat to shuttle</dc:creator>
		<pubDate>Mon, 05 Jan 2009 05:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=8365#comment-238</guid>
		<description>[...] The Holddown Post (HDP) #3 Debris Containment System (DCS) failure has already led to an agreed redesign of the system, as reported by this site last week. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Holddown Post (HDP) #3 Debris Containment System (DCS) failure has already led to an agreed redesign of the system, as reported by this site last week. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
