<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>NASASpaceFlight.com &#187; STS-119</title>
	<atom:link href="http://www.nasaspaceflight.com/tag/sts-119/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nasaspaceflight.com</link>
	<description>Giving space it's place on the web</description>
	<lastBuildDate>Thu, 09 Feb 2012 20:25:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
		<item>
		<title>STS-119 BLT test a success, gains a greater understanding of reentry</title>
		<link>http://www.nasaspaceflight.com/2009/05/sts-119-blt-test-success-gains-greater-understanding-reentry/</link>
		<comments>http://www.nasaspaceflight.com/2009/05/sts-119-blt-test-success-gains-greater-understanding-reentry/#comments</comments>
		<pubDate>Fri, 08 May 2009 04:18:49 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[STS-119]]></category>
		<category><![CDATA[TPS]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9785</guid>
		<description><![CDATA[STS-119&#8242;s Boundary Layer Transition (BLT) Detailed Test Objective (DTO) has been deemed a huge success, following the presentation of the test results. The tests will continue on at least two more flights, as engineers gain vital data on the conditions a spacecraft endures during reentry. The goal of the experiment was to measure the effects [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p>STS-119&#8242;s Boundary Layer Transition (BLT) Detailed Test Objective (DTO) has been deemed a huge success, following the presentation of the test results. The tests will continue on at least two more flights, as engineers gain vital data on the conditions a spacecraft endures during reentry.</p>
<p><span id="more-9785"></span></p>
<p>The goal of the experiment was to measure the effects of increased heating from an early boundary layer transition as the orbiter returns to Earth. <a href="http://www.nasaspaceflight.com/2007/12/sts-126-set-to-carry-out-special-reentry-experiment/" target="_blank">The DTO was set to debut on STS-126</a>, before being deferred to STS-119.</p>
<p>During a normal reentry, the orbiter compresses the air as it is entering the atmosphere, which creates a protective region (similar to insulation) with temperatures in the 2000-3000F degree range.</p>
<div><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=3.0">LIVE STS-125 UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=35.0">L2 STS-125/400 Special Section</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?topic=16457.0">Stunning STS-119 Review Video</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?action=tags&amp;tags=STS-119">L2 STS-119 Special (3200mb)</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></div>
<p>Those values are ably handled by the tiles and other protective systems on the shuttle, however,  just inches away &#8211; outside of the boundary layer &#8211; the readings can rise to 10,000 degrees</p>
<p>If there is any sort of interruption in that flow &#8211; such as a protruding gap filler, or damaged tile, or other rough surface &#8211; the boundary layer will be tripped sooner than expected, and the extreme heat could cause damage to the tiles, or the orbiter itself in severe cases.</p>
<p>Gap fillers started to become a concern on STS-28, when they were the likely cause of an early BLT (around Mach 18). Several of the gap fillers were found protruding after landing, and more than the usual amount fell on the runway after touchdown.</p>
<p>However a 1989 report from NASA stated that protruding gap fillers were not a flight safety concern, only an issue for turn-around for the next flight.</p>
<p><img class="alignleft size-full wp-image-9787" title="a25" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/05/a25.jpg" alt="a25" width="302" height="182" />The STS-119 test was proposed as a means of accurately measuring the actual conditions of an early BLT by installing a specially designed tile with a 0.25&#8221; bump to Discovery&#8217;s belly. Located near the port main landing gear door, the protrusion was expected to cause a transition around Mach 15.</p>
<p>Specially installed tiles with Modular Auxiliary Data System (MADS) instrumentation were installed in several spots across the orbiter&#8217;s belly with the ability to measure precise temperatures.</p>
<p>A Navy P3 Orion was also used, flying over the Gulf of Mexico underneath the shuttle&#8217;s path to take infrared pictures known as Hypersonic AeroTHermodynamic InfraRed Measurements (HYTHIRM).</p>
<p>The initial review of the data &#8211; via Program Requirements Control Board (PRCB) presentations, available on L2 &#8211; indicates that if anything, the models used to determine BLT temperatures were too conservative.</p>
<p>Predictions of the speed at which the 0.25&#8221; protuberance would trip the boundary layer were estimated to be around Mach 15.4. However, the initial BLT occurred at Mach 15.6, 969 seconds after the start of Entry Interface (EI).</p>
<p><img class="alignleft size-full wp-image-9789" title="a41" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/05/a41.jpg" alt="a41" width="325" height="204" />Surface temperatures in the smooth flow region &#8211; protected by the boundary layer &#8211; were measured at around 1,600 degrees F which was consistent with flight history.</p>
<p>The temperatures in the turbulent wedge of the nose cone area were approximately 1,900 degrees F &#8211; which was a little lower than predictions, but consistent with observations from STS-28.</p>
<p>The main area of concern was heating after the trip region became established. The lack of any Reaction Cured Glass (tile coating) &#8220;melt or flow&#8221; leads to the conclusion that most temperatures were less than 2,500 degrees F &#8211; with predictions of around 2,700-2,800 degrees F.</p>
<p>Documentation claims the peak temperature measured was approximately 2,000 degrees F, while pre-flight predictions were nearly 3,000 degrees F.</p>
<p>Post flight scans of the OML (Outer Mold Line) shape of the tiles in the protuberance area show no discernible change in the surface of the tiles.</p>
<p><img class="alignleft size-full wp-image-9788" title="a35" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/05/a35.jpg" alt="a35" width="315" height="179" />One unexpected benefit of the multiple observation methods was the measurement of what&#8217;s called an Asymmetric Boundary Layer Transition (ABLT).</p>
<p>This occurred on the opposite side from the protuberance at Mach 10.5 &#8211; within limits for a normal BLT at Mach 11 &#8211; from some sort of &#8220;roughness&#8221; on the vehicle.</p>
<p>Post-flight GN&amp;C assessments, along with data from the additional thermocouples and imagery from the HYTHIRM project, isolated the source of that ABLT to a region near the starboard side of the nose gear door.</p>
<p>Such high resolution data might be able to pin down the source of airflow tripping. However, given the lower speeds that such a situation can occur, ABLT is not considered a significant issue.</p>
<p>Next up for BLT is to increase the size of the protuberance to 0.35&#8221; &#8211; to be installed on Discovery for her STS-128 flight. The larger wedge is expected to trip the boundary layer at around Mach 18, provided information on higher levels of heat.</p>
<p>HYTHIRM is now preparing for the STS-125 entry, but has indicated readiness for being involved with the STS-128 experiment.</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which most of the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9785&amp;ts=1328834908" style="display:none;" alt="pixelstats trackingpixel"/>

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/05/sts-119-blt-test-success-gains-greater-understanding-reentry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NASA reviews SRB upgrades at STS-125 FRR &#8211; Outlines STS-119 event</title>
		<link>http://www.nasaspaceflight.com/2009/05/nasa-srb-upgrades-sts-125-frr-outlines-119-event/</link>
		<comments>http://www.nasaspaceflight.com/2009/05/nasa-srb-upgrades-sts-125-frr-outlines-119-event/#comments</comments>
		<pubDate>Mon, 04 May 2009 23:35:22 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[SRB]]></category>
		<category><![CDATA[STS-119]]></category>
		<category><![CDATA[STS-125]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9752</guid>
		<description><![CDATA[With launch of STS-125 now less than a week away, NASA managers have thoroughly reviewed the performance of the Solid Rocket Boosters (SRBs) from the previous missions, approving several safety and performance upgrades to aid Shuttles Atlantis and Endeavour on their STS-125 and STS-400 missions respectively. Thrust Tail-Off Imbalance: The first issue relating to the [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p>With launch of STS-125 now less than a week away, NASA managers have thoroughly reviewed the performance of the Solid Rocket Boosters (SRBs) from the previous missions, approving several safety and performance upgrades to aid Shuttles Atlantis and Endeavour on their STS-125 and STS-400 missions respectively.</p>
<p><span id="more-9752"></span><br />
<strong>Thrust Tail-Off Imbalance:</strong></p>
<p>The first issue relating to the SRBs discussed at the SSP FRR (Space Shuttle Program Flight Readiness Review) pertained to <a href="http://www.nasaspaceflight.com/2009/04/sts-119-ifa-review-focus-on-discoverys-boosters/" target="_blank">the thrust tail-off imbalance noted during the STS-119 mission in March</a>.</p>
<p>&#8220;STS-119 GN&amp;C (Guidance Navigation and Control) Quick-look showed departures from PE flight history for roll and yaw attitude error&#8230;&#8221; notes the Reusable Solid Rocket Motor (RSRM) FRR presentation, available for download on L2.</p>
<p>While SRB thrust tail-off imbalance occurs on every mission, strict guidelines are used during the casting/pouring of the SRB segments&#8217; propellant at the ATK factory in Utah to minimize all aspects of thrust imbalance during SRB flight.</p>
<p><img class="alignleft size-full wp-image-9754" title="a22" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/05/a22.jpg" alt="a22" width="256" height="248" />However, the STS-119 event followed the STS-124 thrust tail-off imbalance in May 2008 and the less severe event on STS-126 last November.</p>
<p>As a result, the SSP has provided the GN&amp;C community with all RSRM reconstruction data to support their analysis of the various flight control systems responsible for detecting this type of imbalance and taking the necessary action to correct the vehicle&#8217;s attitude/pitch/yaw accordingly.</p>
<p>For this, the GN&amp;C community has been tasked with identifying any &#8220;design, process, and material factors&#8221; that could have/could be contributing to the thrust tail-off phenomenon.</p>
<p>In addition to the GN&amp;C investigation, the SSP has developed a working theory, which pertains to a burn rate variation.</p>
<p>&#8220;Primary contributor to trace shape variation observed on STS-119, STS-124, and STS-126 is a burn rate variation and location of added mixes in the segments,&#8221; notes the presentation.</p>
<p>In addition to this theory, several upgrades have been added to the engineering, manufacturing, and analytical controls to &#8220;keep thrust imbalance on future flights well within CEI requirements.&#8221;</p>
<p>As such, an extensive review of the propellant casting process for STS-125 and subsequent flights that will use already poured SRB segments has been conducted, resulting in clearance for flight for all of those segments.</p>
<p><strong>O-Ring Modification and LCC Contingency Temperatures for Heater Failure Scenario:<br />
</strong><br />
<img class="alignleft size-full wp-image-9755" title="a51" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/05/a51.jpg" alt="a51" width="248" height="202" />An additional change to the SRBs on STS-125 relates to the replacement of the fluorocarbon O-rings with a newly developed V1288 O-ring in the field joints of the SRBs.</p>
<p>The V1288 O-rings are new low-temperature fluorocarbon O-rings that were developed to &#8220;improve resiliency at lower temperatures with no degradation to other performance characteristics,&#8221; notes the RSRM presentation.</p>
<p>These new O-rings will allow the Space Shuttle to fly with higher safety margins and/or at lower temperatures.</p>
<p>The basis for verifying these new O-rings for flight included, but was not limited to, Anchors modeling (with showed compliance with all CEI tracking requirements), high temperature sealing capability that was equivalent to the O-rings used on STS-119 and several previous missions, splice strength that showed &#8220;no degradation with age,&#8221; and an ablation and erosion of less than half that of the previous O-ring flight model.</p>
<p>Additionally, five static firings were conducted to test the new O-rings. &#8220;V1288 forward field joint fired at 58 degrees F on TEM-13 (joint heaters not activated &#8211; no hot gas into J-leg),&#8221; notes the FRR presentation.</p>
<p>These O-rings flew successfully on ATK BSMs on STS-122, STS-123, STS-124, STS-126, and STS-119 &#8211; which added confidence to the application of these O-rings in the RSRM segment field joints on STS-125 and subsequent flights.</p>
<p>Furthermore, the RSRM presentation to the SSP FRR also notes changes to the minimum allowable temperatures for the SRB field joints.</p>
<p><img class="alignleft size-full wp-image-9756" title="a34" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/05/a34.jpg" alt="a34" width="320" height="222" />Should the SRB heaters fail during the countdown, the SSP FRR presentation notes that the minimum allowable sensor temperature for the field joints will 44 degrees F, with the minimum sensor temperatures for the Igniter-to-case Joint and the Nozzle-to-case Joint at 70 degrees F and 62 degrees F respectively.</p>
<p>These minimum allowable temperatures will be &#8220;Automatically applied after valid (measurements violate) 86 degrees F Launch Commit Criteria (LCC) redline,&#8221; notes the RSRM presentation.</p>
<p>However, the J-leg has the potential to experience &#8220;low temperature performance degradation&#8221; because the J-leg becomes stiffer and shrinks in colder temperatures.</p>
<p>&#8220;RSRM designed to maintain J-leg axial engagement at ignition for temperatures from 90 degrees F down to 40 degrees F,&#8221; notes the SSP FRR presentation.</p>
<p>However, a full up test of the field joint thermal protection system has not occurred at the lower 44 degrees F limit.</p>
<p>In fact, the lowest tested temperature is 56 degrees F with no humidity conditioning. During those tests, there was no hot gas penetration past the J-leg tip.</p>
<p>This means that during a launch scenario with a 44 degrees F temperature reading, there is an increased potential for gas penetration into the J-leg because of &#8220;rubber shrinkage at colder temperatures.&#8221;</p>
<p>Nevertheless, while a full up test of the field joint thermal protection system at the 44 degrees F limit has not been conducted, multiple tests with intentionally flawed components have been undertaken.</p>
<div><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=3.0">LIVE STS-125 UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=35.0">L2 STS-125/400 Special Section</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></div>
<p>Through all these tests, the RSRM presentation notes that &#8220;no capture feature O-ring failure or primary O-ring erosion&#8221; occurred; in fact, &#8220;hot gas to primary O-ring required intentional flaw alignment of every redundant feature.&#8221;</p>
<p>Furthermore, &#8220;Potential opening of the J-joint, caused by cold temperatures, creates a less severe environment or less severe gas impingement than a flaw focused on the capture feature O-ring,&#8221; notes the RSRM presentation.</p>
<p>In all, the thermal protection system for the RSRM segments is certified for flight. Intentional flaw testing and analysis shows compliance with both upper and lower temperature extremes as well as flaw size extremes that may be present as a result of the segment-mating process.</p>
<p>In summary, all O-ring seals and joint thermal protection systems meet all the necessary flight requirements at 44 degrees F. Therefore, STS-125 and subsequent flights are safe to fly with the new O-ring configuration under the failed heater field joint contingency temperature of 44 degrees F.</p>
<p><strong>Engineer Camera Repositioning:<br />
</strong><br />
In addition to the internal modifications, NASA engineers have repositioned the Right Hand Forward Skirt Aft Pointing (FSAP) camera on the exterior of the SRB.</p>
<p>The change, which Shuttle Program Manager John Shannon noted during the FRR Briefing last Thursday, was done at the request of the Debris Integration Group.</p>
<p>The precise reason for the modification is to gain further engineering data on the inter-tank region of the External Tank &#8211; an area of the tank that has experience minor, yet consistent, foam loss over the last several flights.</p>
<p>This camera re-configuration has flown once before, on the STS-120 mission in October 2007. That repositioning was performed to gain a wider view of the newly designed Ice Frost Ramps.</p>
<p>Nevertheless, subsequent flights from STS-120 all utilized the previous SRB camera configuration &#8211; a configuration which debuted on STS-121 in July 2006.</p>
<p>For STS-125, only the RH FSAP camera will be repositioned. Both FSAP cameras will be repositioned for STS-127 and subsequent flights.</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which most of the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9752&amp;ts=1328834908" style="display:none;" alt="pixelstats trackingpixel"/>

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/05/nasa-srb-upgrades-sts-125-frr-outlines-119-event/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Endeavour rolls out for STS-400 role at Pad 39B &#8211; GUCP anomaly status</title>
		<link>http://www.nasaspaceflight.com/2009/04/endeavour-rolls-out-for-sts-400-role-gucp-anomaly-status/</link>
		<comments>http://www.nasaspaceflight.com/2009/04/endeavour-rolls-out-for-sts-400-role-gucp-anomaly-status/#comments</comments>
		<pubDate>Fri, 17 Apr 2009 11:27:47 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[ET]]></category>
		<category><![CDATA[GUCP]]></category>
		<category><![CDATA[STS-119]]></category>
		<category><![CDATA[STS-125]]></category>
		<category><![CDATA[STS-400]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9560</guid>
		<description><![CDATA[Shuttle Endeavour has completed her rollout to 39B, where she will be put through a part flow as the STS-400 LON (Launch On Need) support for Atlantis&#8217; STS-125 mission. During this flow, engineers will test the alignment procedures with the Ground Umbilical Carrier Plate (GUCP) &#8211; following the leak during STS-119&#8242;s opening launch attempt. STS-400/127 [...]


Related posts:<ol><li><a href='http://www.nasaspaceflight.com/2008/09/sts-400-rolls-out-of-vab-sts-125-payload-delay-to-saturday/' rel='bookmark' title='Permanent Link: STS-400 rolls out of VAB &#8211; STS-125 payload delay to Saturday'>STS-400 rolls out of VAB &#8211; STS-125 payload delay to Saturday</a> <small>A problem during the preparation of Atlantis&#8217; Hubble Servicing payload...</small></li>
<li><a href='http://www.nasaspaceflight.com/2008/11/sts-126-endeavour-easing-through-countdown/' rel='bookmark' title='Permanent Link: STS-126: Super smooth Endeavour easing through the countdown to L-1'>STS-126: Super smooth Endeavour easing through the countdown to L-1</a> <small>A loose washer on a ground support carrier plate is...</small></li>
<li><a href='http://www.nasaspaceflight.com/2008/10/dual-flow-de-stack-debate/' rel='bookmark' title='Permanent Link: Dual flow ballet for Endeavour and Atlantis &#8211; De-stack debate'>Dual flow ballet for Endeavour and Atlantis &#8211; De-stack debate</a> <small>Preliminary milestone schedules have been created for the complex dual...</small></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>Shuttle Endeavour has completed her rollout to 39B, where she will be put through a part flow as the STS-400 LON (Launch On Need) support for Atlantis&#8217; STS-125 mission. During this flow, engineers will test the alignment procedures with the Ground Umbilical Carrier Plate (GUCP) &#8211; following the leak during STS-119&#8242;s opening launch attempt.</p>
<p><span id="more-9560"></span></p>
<p><strong>STS-400/127 Flow:<br />
</strong><br />
Endeavour spent a week inside the Vehicle Assembly Building (VAB), prior to rolling out of High Bay 1 shortly before midnight local time.</p>
<p>Engineers were called to stations two hours ahead of first motion, after completing the retraction of platforms that had surrounded the vehicle during ET mate and Shuttle Interface testing (S0008).</p>
<p>&#8220;A5214 Shuttle Transfer and Mate to Pad B: &#8220;E&#8221;, &#8220;D&#8221; and &#8220;B&#8221; platform retracts are complete. S0008 Shuttle Interface Testing is complete. SRB HPU checks are complete,&#8221; noted pre-rollout processing information on L2. &#8220;The SSV has been powered down in preparation for rollout. SRB Hold-down Post Firing Line Checks are complete.&#8221;</p>
<p>Only three minor issues of note were worked during Endeavour&#8217;s VAB flow, two relating to orbiter camera systems, and one relating to Endeavour turning herself off during an unexpected power loss inside the famous building.</p>
<div><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=4.0">LIVE STS-127/400 UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?action=tags&amp;tags=STS-127">L2 STS-127  Special Section</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=35.0">L2 STS-125/400 Special Section</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></div>
<p>&#8220;During S0008, an unexpected power loss occurred resulting in Orbiter/SRB power down (resolved),&#8221; added processing information. &#8220;During ET Sep Camera testing, the flash module did not flash during testing,&#8221; which has also been resolved, although engineering evaluations will continue, due to <a href="http://www.nasaspaceflight.com/2009/03/sts-119-complex-robotics-s6-tps-to-be-cleared/" target="_blank">similar issues with Discovery&#8217;s ET camera during STS-119</a>.</p>
<p>&#8220;While attempting to download images from ET/TPS DCS Camera to A31P laptop, the following error message was received: &#8216;An error was detected with reading images from card, retry&#8217;,&#8221; was noted as the only other problem during the VAB flow. Further troubleshooting resolved the issue.</p>
<p>The Rotating Service Structure (RSS) is not due to be retracted around Endeavour until Monday, which &#8211; thanks to Atlantis&#8217; RSS on Pad 39A being retracted on Friday &#8211; will allow for the <a href="http://www.nasaspaceflight.com/2008/09/endeavoursts-400-arrives-at-pad-39b-both-sisters-visible/" target="_blank">stunning photography of both shuttles being visible on the pads, as was last seen prior to the on orbit issues with Hubble</a>, which ultimately delayed STS-125 last year.</p>
<p>See more: <a href="http://www.nasaspaceflight.com/tag/sts-400/" target="_blank">Click here for recent STS-400 related articles</a><br />
See more: <a href="http://www.nasaspaceflight.com/tag/sts-127/" target="_blank">Click here for recent STS-127 related articles<br />
</a><br />
<strong>GUCP Testing and Status:</strong></p>
<p>Once Endeavour is put through her STS-400 flow on 39B, engineers will keep a close eye on the mating and installation process of the GUCP, in order to try and gain more data on a potential root cause to the <a href="http://www.nasaspaceflight.com/2009/03/sts-119-in-prep-for-tanking-following-engineering-overview-for-crew/" target="_blank">leak observed during STS-119&#8242;s opening launch attempt &#8211; which caused the launch to be scrubbed</a>.</p>
<p><img class="alignleft size-full wp-image-9563" title="a312" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a312.jpg" alt="a312" width="295" height="191" />&#8220;STS-119 / ET-127 Performance Summary: Pre-launch: 1st loading resulted in scrub/LCC (Launch Commit Criteria) violation due to GH2 leakage at GUCA (&gt;40,000 ppm. Flight seal/QD (Quick Disconnect) replaced,&#8221; noted a post mission IFA (In Flight Anomaly) review presentation on L2, written by the MAF (Michoud Assembly Facility).</p>
<p>&#8220;Leakage occurred during transition from fast fill to topping. Vent valve opened when 98 percent level sensor indicated wet. Detected by leak detectors (LD 23 &amp; 25) located in ground umbilical shroud. Isolates leak to either ground side quick disconnect (QD) or interface with flight seal.</p>
<p>&#8220;Contingency plans (vent valve cycling) unsuccessful in controlling leakage within acceptable limits. Launch scrubbed, <a href="http://www.nasaspaceflight.com/2009/03/sts-119-nasa-managers-press-ahead-with-sunday-launch-attempt/" target="_blank">flight seal/disconnect replaced</a>. No GH2 leakage observed during subsequent loading. <a href="http://www.nasaspaceflight.com/2009/03/sts-119-live-second-attempt-tsm-t0/" target="_blank">No other anomalous performance observed during loading</a>.&#8221;</p>
<p>No root cause has yet been found, although the leading candidate has been noted on the latest documentation relating to the incident.</p>
<p>&#8220;No first-time hardware changes implemented for STS-119/ET-127 GH2 vent system. 31 previous loadings with only 1 leak observed (13,500 ppm). Previous leaks also observed during fast fill to topping transition,&#8221; added the MAF presentation.</p>
<p><img class="alignleft size-full wp-image-9564" title="a47" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a47.jpg" alt="a47" width="335" height="188" />&#8220;Most probable cause identified as momentary breach in flexible flight-seal to bellows probe due to ‘thermal shock’ of GH2/LH2 with vent valve in open position.</p>
<p>&#8220;Significant Disassembly Observations: Lower left pad was hard against skin. Other locations were not touching (0.014 &#8211; 0.030 gap / 0.001 requirement) indicating a pull downward and to the left. Peripheral seal compressed more on left side and toward bottom of GUCP.</p>
<p>&#8220;Left side pivot assembly in hard contact with pivot pin (pin would not rotate). Stain observed on external surface of bellows guard and peripheral seal at 6 o’clock position. Flight-side seal asymmetrically compressed at 3, 7 and 8 o&#8217;clock positions.&#8221;</p>
<p>However, as per usual, engineers will ensure the problem isn&#8217;t related to another factor, such as a problem with the alignment of the hardware on the tank. In order to check their procedures, STS-400&#8242;s flow included the addition of tape markers on the alignment pins, to allow the monitoring of the hardware for any movement during the process.</p>
<p>&#8220;GUCP Checkout: Engineering added a dev to apply tape to GUCP alignment pins,&#8221; noted Endeavour processing information. &#8220;The tape application is complete. The procedure on the GUCP Alignment will be worked at the Pad.&#8221;</p>
<p>The MAF document also included a full run down on what is required when mating the umbilical and plate to the tank, which is more complex than may be assumed.</p>
<p><img class="alignleft size-full wp-image-9562" title="a211" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a211.jpg" alt="a211" width="321" height="194" />&#8220;Installation Process: GUCP installed using three (3) guide pins to align. Install / torque pyro bolt to verify distance from tank (7.0 &#8211; 7.06&#8221;) and ensure proper bellows preload. Adjust pivot assembly feet to contact the umbilical hinge bracket pins and remove guide pins (recent change from hard-down preload requirement, last year).</p>
<p>&#8220;Adjust pads between GUCP periphery and tank skin to lightly touch (4 places). Install QD with use of 4 guide pins. Adjust pads (4 places) to verify parallelism and take measurements (Checkout cell and integration cell). Helium leak check at around 6 psig.</p>
<p>&#8220;Post vent line installation. Adjust pads (4 places) to ensure around 0.001 clearance and ensure feet contact hinge pins. Helium leak check at around 6 psig.&#8221;</p>
<p>Engineers don&#8217;t expect the same issue to cause a problem for STS-125&#8242;s countdown in less than a month&#8217;s time, but have taken precautions on both <a href="http://www.nasaspaceflight.com/2008/12/sts-125s-tank-manifest-meeting-ares-i-x-iss-food-shortage-2/" target="_blank">Atlantis&#8217; ET-130</a> and Endeavour&#8217;s ET-131.</p>
<p>&#8220;ET-130 vent disconnect hardware removed, inspected/re-built and replaced in VAB. Micro-fibers observed on flight seal emanating from corners of seal (around 1&#8221; length, 0.0003&#8221; dia., max). Fibers inherent to manufacturing process and accepted use-as-is,&#8221; added the presentation.</p>
<p>&#8220;Seal compression (&gt;10x max fiber dia.) due to probe loading sufficient to either liberate or cold flow fibers into seal parent material. Similar fibers observed on seal installed and successfully flown on ET-127. No significant observations noted during disassembly and rebuilding of QD.&#8221;</p>
<p>&#8220;ET-131 flight seal re-inspected and replaced due to small, isolated indention on sealing surface. Indention not observed / documented during multiple visual / tactile inspections at MAF and initial inspection at KSC (cause indeterminate). Condition not consistent with observations noted on ET-127 seal.&#8221;</p>
<p>These precautions have already avoided the STS-119 issue from becoming a topic of concern at next week&#8217;s SSP (Space Shuttle Program) Flight Readiness Review (FRR), with managerial approval to fly as-is with the next two tanks.</p>
<p>&#8220;Root Cause Fault Tree Investigation and Tests In Progress .STS-125 (ET-130) and LON (ET-131) Hardware and Installation Re-Verified,&#8221; confirmed the document. &#8220;No Constraints to Flight Identified.&#8221;</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9560&amp;ts=1328834908" style="display:none;" alt="pixelstats trackingpixel"/>

<p>Related posts:<ol><li><a href='http://www.nasaspaceflight.com/2008/09/sts-400-rolls-out-of-vab-sts-125-payload-delay-to-saturday/' rel='bookmark' title='Permanent Link: STS-400 rolls out of VAB &#8211; STS-125 payload delay to Saturday'>STS-400 rolls out of VAB &#8211; STS-125 payload delay to Saturday</a> <small>A problem during the preparation of Atlantis&#8217; Hubble Servicing payload...</small></li>
<li><a href='http://www.nasaspaceflight.com/2008/11/sts-126-endeavour-easing-through-countdown/' rel='bookmark' title='Permanent Link: STS-126: Super smooth Endeavour easing through the countdown to L-1'>STS-126: Super smooth Endeavour easing through the countdown to L-1</a> <small>A loose washer on a ground support carrier plate is...</small></li>
<li><a href='http://www.nasaspaceflight.com/2008/10/dual-flow-de-stack-debate/' rel='bookmark' title='Permanent Link: Dual flow ballet for Endeavour and Atlantis &#8211; De-stack debate'>Dual flow ballet for Endeavour and Atlantis &#8211; De-stack debate</a> <small>Preliminary milestone schedules have been created for the complex dual...</small></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/04/endeavour-rolls-out-for-sts-400-role-gucp-anomaly-status/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>STS-119 IFA Review: Focus on Discovery&#8217;s Boosters</title>
		<link>http://www.nasaspaceflight.com/2009/04/sts-119-ifa-review-focus-on-discoverys-boosters/</link>
		<comments>http://www.nasaspaceflight.com/2009/04/sts-119-ifa-review-focus-on-discoverys-boosters/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 03:21:30 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[IFA]]></category>
		<category><![CDATA[SRB]]></category>
		<category><![CDATA[STS-119]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9520</guid>
		<description><![CDATA[The usual ballet of reviews to ensure safe flight has moved through another key stage, following the full review of STS-119&#8242;s IFAs (In Flight Anomalies). With the next two missions heading to different orbital destinations, part of the IFA review will go towards STS-125&#8242;s upcoming Flight Readiness Review (FRR), and the ISS related section forwarded [...]


Related posts:<ol><li><a href='http://www.nasaspaceflight.com/2008/12/srb-holddown-posts-undergoing-redesign-evaluation-ahead-of-sts-119/' rel='bookmark' title='Permanent Link: SRB Holddown posts undergoing redesign evaluation ahead of STS-119'>SRB Holddown posts undergoing redesign evaluation ahead of STS-119</a> <small>Engineers will meet in the middle of January to push...</small></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>The usual ballet of reviews to ensure safe flight has moved through another key stage, following the full review of STS-119&#8242;s IFAs (In Flight Anomalies). With the next two missions heading to different orbital destinations, part of the IFA review will go towards STS-125&#8242;s upcoming Flight Readiness Review (FRR), and the ISS related section forwarded to Endeavour&#8217;s STS-127 mission.</p>
<p><span id="more-9520"></span></p>
<p>Most of the issues reviewed were known about as and when they occurred during Discovery&#8217;s mission, and only a handful of elements requiring further evaluation &#8211; such as the issue with the ET Umbilical Well Camera, which failed to flash more than once, along with issues downloading any usable imagery of the External Tank post separation.</p>
<p>&#8220;IFAs: There were no significant issues with any of the IFAs but the flight rationale for the partial Tyvek cover release and more information on the Umbilical Well Camera Flash/Download problem will be discussed at the PRCB (Program Requirements Control Board) meeting,&#8221; noted an L2 acquired 8th Floor (MOD) summary on Monday.</p>
<div><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=3.0">LIVE STS-125 UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=35.0">L2 STS-125/400 Special Section</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?topic=16457.0">Stunning STS-119 Review Video</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=33.0">L2 STS-119 Special (3000mb)</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></div>
<p>&#8220;MOD (Mission Operations Directorate) presented one IFA for the Abort Light command being inadvertently sent prelaunch. There is one other potential MOD IFA for WFCR2 (GNC console) sluggish performance.</p>
<p>&#8220;The Loss of ISS to Ground Voice during the RPM (Rbar Pitch Maneuver) was briefed as an item of interest. MOD is tracking this item with an ISS anomaly to ensure adequate closure prior to STS-127.&#8221;</p>
<p>The full STS-119 IFA review consisted of 15 presentations &#8211; all available on L2 &#8211; ranging from the state of the launch pad, propulsion systems, and flight software. Below is the review of STS-119&#8242;s boosters.</p>
<p><strong>RSRM IFA Review:</strong></p>
<p>STS-119&#8242;s boosters performed as expected, bar a slight issue with a <a href="http://www.nasaspaceflight.com/2008/07/discovery-ascent-trajectory-anomaly-noted-on-sts-124-ifa-review/" target="_blank">tail-off thrust imbalance &#8211; last seen during STS-124&#8242;s ascent last May.</a></p>
<p>The imbalance is caused when one booster loses pressure during burnout slightly faster than its opposite number, causing the stack to yaw slightly &#8211; which usually results in the SSMEs (Space Shuttle Main Engines) and/or the SRB TVC (Thrust Vector Control) system countering to keep the shuttle on the correct trajectory.</p>
<p>&#8220;All RSRM countdown parameters were within limits and within family. Overall performance of both RSRM motors and all ATK BSMs (Booster Separation Motors) excellent and well within requirements,&#8221; noted the ATK IFA presentation on the Reusable Solid Rocket Motors.</p>
<p>&#8220;RSRM tail-off thrust imbalance slightly outside of historical family (but within statistical expectation) at discreet time intervals. Overall performance of both STS-119 (RSRM-103) motors and ATK BSMs were excellent.&#8221;</p>
<p>The lack of dedicated section on the tail-off thrust imbalance, with only passing mentions on some of the other IFA review presentations, points to the issue requiring no further action. During STS-124&#8242;s post flight IFA review, several follow-up presentations were required for further understanding.</p>
<p><img class="alignleft size-full wp-image-9522" title="a28" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a28.jpg" alt="a28" width="303" height="213" />Elsewhere on the boosters, seven &#8220;squawks&#8221; &#8211; booster speak for an issue &#8211; were noted on STS-119&#8242;s RSRMs, which is usual and slightly lower than some recent flights.</p>
<p>&#8220;4 inch circumferential crack or unbond detected on the RH (Right Hand) center field joint aft RT455 ramp at approximately 250 degrees,&#8221; noted one of the squawks found on the boosters during post-retrieval inspections.</p>
<p>&#8220;Crack was probed and appeared to extend the full width of the ramp. Cracked area exhibited evidence of cohesive failure in the RT455 material with no evidence of a void or unbond, indicating impact rather than processing problems</p>
<p>&#8220;As the impact was on the aft ramp and showed an aft, moving forward orientation, this could not be an ascent concern.&#8221;</p>
<p>Such damage can be caused when the boosters impact the water, following their parachuted return to the ocean after the two minute assist of the shuttle during first stage flight.</p>
<p>However, every inch of the returned boosters are examined for any &#8220;out of family&#8221; area of interest, even if it had no detrimental effect during powered flight.</p>
<p><img class="alignleft size-full wp-image-9523" title="a37" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a37.jpg" alt="a37" width="213" height="260" />An example of which related to foreign object material found inside a safety and arming device, following it strip down after flight.</p>
<p>&#8220;Foreign material (fiber) was found in Arming Monitor Serial Number 0000021R12; part was refurbished in Nov 2006, prior to any recent corrective actions,&#8221; noted the presentation. &#8220;Fiber was located on switch deck insulator. Foreign Material had no effect on A-M operation.&#8221;</p>
<p>This device was also noted on another squawk, relating to a cracked switch (see left).</p>
<p>&#8220;Cracked switch upper deck was found after disassembly in Arming Monitor Serial Number 0000021R12. Recent corrective action has re-inspected all parts in inventory; however, this S&amp;A was refurbished prior to recent corrective actions (November 2006),&#8221; the presentation added.</p>
<p>&#8220;Crack had no effect on Switch Deck, A-M, or S&amp;A Operation. Cracking mechanism is understood. Brittle molding material may crack thru mold tool pinholes when removed and go unnoticed through several refurbishments.&#8221;</p>
<p>The other squawks related to excessive grease on a vent port plug, more foreign objects, and another crack &#8211; this time on the ignitor chamber insulation, which was not deemed to be a problem.</p>
<p><strong>RSRB IFA Review:</strong></p>
<p>Separate from the RSRM review are the Solid Rocket Boosters (RSRB), which were reviewed by the United Space Alliance (USA). A total of 14 squawks were found on STS-119&#8242;s SRBs.</p>
<p><img class="alignleft size-full wp-image-9524" title="a44" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a44.jpg" alt="a44" width="296" height="260" />A problem with the SWAR (Sea Water Activated Release) ‘failures to release’ was again noted, this time with three of the devices on the RH Booster &#8211; <a href="http://www.nasaspaceflight.com/2008/02/sts-122-reviewing-atlantis-ifas-parachute-failure-tops-list/" target="_blank">which is a known condition that has occurred on a number of flights in succession now</a>.</p>
<p>The SWAR provides a method of disconnecting main parachute from SRB after splashdown, with the immersion in seawater closing an electrical circuit to release a shear pin from the riser about two seconds after immersion.</p>
<p>The SWAR was fully implemented in 1998 on STS-95, in order to increase diver safety by eliminating need to cut parachute lines. Since STS-122, the problem has been heavily documented on both post flight and pre-flight Flight Readiness Review (FRR) presentations.</p>
<p>The problem is believed to be associated with a known failure mechanism with the pyrotechnic train, when the primer fails to breach the stainless steel booster closure cup with enough energy to ignite charge in booster.</p>
<p>Other issues noted included: &#8220;10 sec Reefing Line Cutter (RLC) fired earlier than Lot average. A retention pin not retained in clevis hole. Booster Trowellable Ablative (BTA) delamination on Booster Separation Motor (BSM) triple mount. Several pieces of green and red tape found on various elements of the booster (making up for four squawks).</p>
<p>&#8220;Slice on aft Integrated Electronic Assembly (IEA) forward face center cover Thermal Protection System (TPS). Possible impact on External Tank Attachment (ETA) ring forward face. Aft Integrated Electronic Assembly (IEA) J7 code plug not safety wired.&#8221;</p>
<p>One highlight of the RSRB IFA presentation was the performance of the modified Hold Down Posts (HDPs), which suffered an anomaly during STS-126&#8242;s launch, spreading debris across the launch pad, including a large metal spring &#8211; which would obviously be a major debris impact hazard for the shuttle, as noted in several presentations on the incident, the modifications, and the risks.</p>
<p><a href="http://www.nasaspaceflight.com/?s=HDP" target="_blank">Click Here for NASASpaceFlight.com&#8217;s articles on the HDP issue and resolution.</a></p>
<p>Interestingly, there appears to have been another failure on one of the posts, which would have resulted in an identical debris hazard as seen on STS-126, had it of not been for the newly modified Debris Containment System (DCS) on the HDPs &#8211; as was called for during the redesign post STS-126.</p>
<p>&#8220;Debris Containment System (DCS) on HDP 5 engaged stop blocks. Excellent support from team enabled new design implementation on STS-119/BI135. STS-126/BI136 IFA would have reoccurred without stop blocks. Stop block modification performed as designed. All debris contained.&#8221;</p>
<p><img class="alignleft size-full wp-image-9526" title="a63" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a63.jpg" alt="a63" width="300" height="118" />That secondary retention feature, which saw the addition of two tapered stop blocks, replaced the previous anti-rotation device.</p>
<p>The physical threat to the vehicle relates to either large pieces of debris &#8211; such as the large metal spring found in the north trench after STS-126 &#8211; or small sharp fragments of metal &#8211; such as tube lock clips &#8211; potentially impacting an OMS Pod, a SSME (Space Shuttle Main Engine), an aft Reaction Control System (RSC) “venier” thruster, or part of the vehicle’s TPS (Thermal Protection System).</p>
<p>Given STS-119&#8242;s lift-off saw an issue with one of the HDPs, the first live test of the modified system has &#8211; in effect &#8211; been carried out, and was found to be a huge success.</p>
<p>Further IFA review articles will follow.</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9520&amp;ts=1328834909" style="display:none;" alt="pixelstats trackingpixel"/>

<p>Related posts:<ol><li><a href='http://www.nasaspaceflight.com/2008/12/srb-holddown-posts-undergoing-redesign-evaluation-ahead-of-sts-119/' rel='bookmark' title='Permanent Link: SRB Holddown posts undergoing redesign evaluation ahead of STS-119'>SRB Holddown posts undergoing redesign evaluation ahead of STS-119</a> <small>Engineers will meet in the middle of January to push...</small></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/04/sts-119-ifa-review-focus-on-discoverys-boosters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>STS-119 FCV performance boosts flight rationale for STS-125</title>
		<link>http://www.nasaspaceflight.com/2009/04/sts-119-fcv-performance-boosts-flight-rationale-sts-125/</link>
		<comments>http://www.nasaspaceflight.com/2009/04/sts-119-fcv-performance-boosts-flight-rationale-sts-125/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 03:28:41 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[FCV]]></category>
		<category><![CDATA[STS-119]]></category>
		<category><![CDATA[STS-125]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9455</guid>
		<description><![CDATA[Aiding the requirement of flight rationale for STS-125, engineers have found that the three replacement Flow Control Valves (FCVs) that flew on STS-119 suffered from no cracking, following inspections on the valves after they had been removed from Discovery. The news comes as managers prepare to conduct both the post flight review of STS-119 and [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p>Aiding the requirement of flight rationale for STS-125, engineers have found that the three replacement Flow Control Valves (FCVs) that flew on STS-119 suffered from no cracking, following inspections on the valves after they had been removed from Discovery. The news comes as managers prepare to conduct both the post flight review of STS-119 and the opening pre-briefs for STS-125 later this week.</p>
<p><span id="more-9455"></span></p>
<p><strong>STS-125 Processing Flow Latest:</strong></p>
<p>Atlantis &#8211; preparing for her May 12 launch date to the Hubble Space Telescope &#8211; is enjoying a smooth pad flow out at 39A, as she moves into hyper servicing and payload arrival preparations.</p>
<p>&#8220;Will continue with S0024 preps. That will lead to a Call-to-Stations Tuesday night, and hyper servicing on Wednesday and Thursday of this week,&#8221; noted the latest Shuttle Stand-Up/Integration report on L2. &#8220;Next week preparing for the payload delivery on April 18.</p>
<p>&#8220;Range Safety System validation (first motion checks) are complete. Helium signature test and Ball Seal Leak Checks are complete and good; GO2 blank off plates removed.&#8221;</p>
<div><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=3.0">LIVE STS-125 UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=35.0">L2 STS-125/400 Special Section</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></div>
<p>This week will also kick off the Flight Readiness Reviews (FRRs) for STS-125, opening with the second MOD FRR review &#8211; following the previous FRRs last September, before the mission was delayed &#8211; outlining the upcoming mission in detail.</p>
<p>This will also coincide with the Mission Management Team (MMT) undergoing a pre-brief, which will be headed by Leroy Cain.</p>
<p>&#8220;Folks have a lot of other things to do between now and STS-125, and have a lot of other meetings on the schedule. We won&#8217;t do it if it does not look necessary,&#8221; noted Mr Cain on the Stand-Up.</p>
<p>&#8220;On STS-125, there will be a MMT pre-brief. It will be scheduled this week. It will be a challenge to find a place to put it on the calendar with the meetings we have in place.&#8221;</p>
<p><strong>Flow Control Valves:</strong></p>
<p><img class="alignleft size-full wp-image-9457" title="a24" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a24.jpg" alt="a24" width="310" height="250" />As with STS-119, more discussion will take place on the Flow Control Valves (FCVs), following the incident observed during STS-126&#8242;s ride to orbit late last year. This in turn led to a major part of the FRR process being dedicated towards the gaining of Flight Rationale ahead of STS-119.</p>
<p>Click <a href="http://www.nasaspaceflight.com/tag/fcv/" target="_blank"><span><span><span><span><span><span><span style="color: #b85b5a;">here for NASASpaceflight.com articles on the FCV issue</span></span></span></span></span></span></span></a> since STS-126.</p>
<p>Including two Special PRCBs (Program Requirement Control Board) meetings, the launch date was delayed until managers and engineers were certain they had the right amount of confidence in flying the three FCVs on Discovery &#8211; without the requirement to standdown for a redesign, which some engineers had been calling for.</p>
<p>As per usual, the decision to fly with three &#8220;cherry picked&#8221; valves that had previously flown without issue has been proven to be the correct decision, with no anatomies noted during Discovery&#8217;s ascent.</p>
<p>That confidence has been boosted via flight inspections, proving the valves didn&#8217;t suffer from cracks &#8211; which is the driver for an eventual liberation, as found with one of Endeavour&#8217;s valves.</p>
<p>&#8220;On OV-103 (Discovery&#8217;s) FCVs, did get them out last week and to Vacco over the weekend and inspected,&#8221; noted the Orbiter Project at the Johnson Space Center. &#8220;Two of the three looked really good, no cracks. The other one picked up a little scratch.</p>
<p>&#8220;We will have to figure out where that came from, and how to get it turned around. Right now the first blush is that we might have to do some flow-balance testing on it. Will work through that. It looks like the FCVs came through pretty well.&#8221;</p>
<p>Due to the nominal performance of the valves, the sets of FCVs that are set to fly with Atlantis on STS-125, and Endeavour on STS-127 (and STS-400 if required), will be likely to gain the required flight rationale without the need for a major discussion at the FRRs.</p>
<p><img class="alignleft size-full wp-image-9458" title="a311" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a311.jpg" alt="a311" width="287" height="192" />A proposed metal plate that would &#8220;beef up&#8221; the most &#8216;at risk&#8217; area of the downstream plumbing in the Main Propulsion System (MPS) &#8211; known as the 90 degree elbow bend &#8211; is now unlikely to have a place in future plans, due to the reduced threat of a liberation, which would have to be on a greater magnitude than that observed during STS-126 to cause damage in this area of the MPS.</p>
<p>In fact, the encouraging post flight inspections of the valves, from which no cracks have been found, will aid flight rationale for at least STS-125.</p>
<p>&#8220;The FCV data is very important, and getting those three valves off of STS-119 is the first time we&#8217;ve had a chance to look at just one flight&#8217;s performance in terms of crack growth,&#8221; added the Orbiter Project.</p>
<p>&#8220;It is good to see that we had no cracks on the valves within our detectability limits pre-flight, and then after flight we don&#8217;t see any as well. It is good news for our flight rationale.&#8221;</p>
<p>No major issues are expected to be discussed when managers close out STS-119 via what is called the post-flight IFA (In Flight Anomaly) review, to be conducted during Thursday&#8217;s PRCB meeting &#8211; thanks in part to Discovery&#8217;s clean mission.</p>
<p>&#8220;On STS-119 MMT debrief, do not have much to talk about. For most of the folks solicited, we really don&#8217;t have much to debrief from a MMT standpoint,&#8221; noted Mr Cain on the Stand-Up report.</p>
<p>Items likely to be discussed are the usual &#8220;squawks&#8221; that are noted on most Solid Rocket Booster (SRBs) IFA presentations, along with the problem with the ET Umbilical Well Camera, which failed to properly execute its flash &#8211; or download imagery &#8211; during post ET-sep.</p>
<p>&#8220;Still working on the ET camera off of STS-119. Got it back to JSC. Did some troubleshooting, and had the same indications as on flight with the camera,&#8221; added engineering notes. &#8220;Sent the camera on command and nothing happened; the laptop couldn&#8217;t find the camera. They opened of up the box and couldn&#8217;t find anything.&#8221;</p>
<p>Any items of interest found during the STS-119 post-flight IFA review will be added to the STS-125 SSP (Space Shuttle Program) FRR documentation.</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9455&amp;ts=1328834909" style="display:none;" alt="pixelstats trackingpixel"/>

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/04/sts-119-fcv-performance-boosts-flight-rationale-sts-125/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ISS concern over S1 Radiator &#8211; may require replacement via shuttle mission</title>
		<link>http://www.nasaspaceflight.com/2009/04/iss-concern-s1-radiator-may-require-replacement-shuttle-mission/</link>
		<comments>http://www.nasaspaceflight.com/2009/04/iss-concern-s1-radiator-may-require-replacement-shuttle-mission/#comments</comments>
		<pubDate>Thu, 02 Apr 2009 03:34:47 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[ISS]]></category>
		<category><![CDATA[STS-119]]></category>
		<category><![CDATA[STS-128]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9399</guid>
		<description><![CDATA[Imagery taken of the delaminated panel on the International Space Station&#8217;s S1 Radiator has revealed a &#8220;structural risk&#8221; on the array, which has the potential to create an ammonia leak in the External Thermal Control System (ETCS). NASA managers are considering options that include flying a replacement radiator array on a downstream shuttle mission, along [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p>Imagery taken of the delaminated panel on the International Space Station&#8217;s S1 Radiator has revealed a &#8220;structural risk&#8221; on the array, which has the potential to create an ammonia leak in the External Thermal Control System (ETCS). NASA managers are considering options that include flying a replacement radiator array on a downstream shuttle mission, along with bringing the damaged S1 Radiator back to Earth. </p>
<p><span id="more-9399"></span></p>
<p>The <a href="http://www.nasaspaceflight.com/2008/09/radiator-damaged-on-iss-off-nominal-soyuz-investigation-update/" target="_blank">damage was first spotted late last summer during a routine imagery survey</a>, in order to check for any damage &#8211; usually caused by MMOD (Micrometeoroid Orbital Debris) strikes &#8211; to the outside of the Station </p>
<p>Imagery found that one of the eight radiator panels on the S1 array &#8211; which each have two thermal face sheets, one on each side, epoxy-glued and autoclaved to the honeycomb structure of the radiator &#8211; was observed as peeled back. These face sheets have a thermal surface coating designed to maximize heat reflection and absorption transfer to space.</p>
<div><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php#2">Downstream Mission UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?action=tags&amp;tags=ISS">L2 ISS Section</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></div>
<p>The radiators are used to remove heat from the Station, via a loop filled with ammonia, supplied by the ETCS accumulator, and backed up by the Ammonia Tank Assembly (ATA).</p>
<p>Though the cause of the damage has not been confirmed, the survey was called after Russian spacewalkers reported one of the Service Module thruster covers had impacted the S1 radiator, after it was jettisoned during a spacewalk last year, making it the leading candidate &#8211; especially since all the other panels remain in good shape.</p>
<p>Initially it was thought the radiator would continue to work without issue, with the opening report last year noting: &#8220;The thermal team reported there is no significant change to the heat rejection capability so currently there are no changes to operations planned.&#8221;</p>
<p>However, Station managers decided to utlize STS-119&#8242;s EVA time to take a closer look. This task remained, despite Discovery&#8217;s mission content being reduced by one EVA.</p>
<p><a href="http://www.nasaspaceflight.com/2009/03/packed-eva-2-on-fd7-of-sts-119/" target="_blank">During STS-119&#8242;s EVA-2</a>, the spacewalkers took photography &#8211; including thermal imagery &#8211; of the panels to check for hot spots and allow for a closer inspection of the damage on the ground. Those evaluations have taken place and have revealed the issue as potentially serious.</p>
<p><img class="alignleft size-full wp-image-9402" title="a3" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a3.jpg" alt="a3" width="250" height="180" />&#8220;S1-3-2 Radiator Peeled Back Panel Status: Engineering and Boeing brought in a status of this situation,&#8221; noted an expansive ISS update in this week&#8217;s Space Station Program Control Board (SSPCB) meeting notes, available on L2 &#8211; before outlining some of the basics of the radiator system.</p>
<p>&#8220;The board was reminded that the Ammonia Tank Assembly (ATA) acts as an accumulator for the ETCS system. The built in ETCS accumulator does not have sufficient volume to be able to react to the orbital thermal environmental variation with the ATA supply valves closed.</p>
<p>&#8220;At this point, the structures folks indicated that with a single panel peeled back from the S1-3-2 radiator, general on orbit load cycles are now reacted at ammonia flow tube weld joints vs the skin of the panel.</p>
<p>&#8220;The honeycomb substructure will not react loads without the adhered panel skin. Because of this phenomenon, the engineering team believes that we are at risk for the weld to fatigue and fail and subsequently create a leak in the system.&#8221;</p>
<p>The report went on to outline the impacts of a leak in the loop, noting the ISS crew would be alerted by their Failure Detection, Isolation and Recovery (FDIR) system during such an event, in turn allowing for either the crew or controllers on the ground to isolate the leak.</p>
<p>&#8220;(However,) the board was reminded that the current FDIR only alerts the crew or ground to a potential ammonia leak when the accumulator pressure drops to 170 psia to protect the pump.</p>
<p>&#8220;Since there is an accumulator at the pump assembly, the entire ATA tank would be emptied prior to auto FDIR annunciating the problem and shutting down the loop. Once notified of a leak, it takes the crew around 30 minutes to manually isolate a radiator panel or the MCC around 15 minutes.</p>
<p>&#8220;However, current hazard constraints and flight rules inhibit isolating radiator panels under insolation to ensure that you do not over pressurize an isolated flow path.&#8221;</p>
<p><img class="alignleft size-full wp-image-9401" title="a2" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/04/a2.jpg" alt="a2" width="334" height="207" />Should such an event take place, the Station would not be without a full supply of ammonia for long, with <a href="http://www.nasaspaceflight.com/2009/01/128-discovery-prcb-updates-mission-baseline/" target="_blank">STS-128/17A due to carry a new ATA to the ISS this summer</a> &#8211; a regular changeout, <a href="http://www.nasaspaceflight.com/2009/02/sts-131-logistics-flight-baselined-by-prcb/" target="_blank">with another ATA set to fly on STS-131</a>.</p>
<p>However, managers are required to work options for at least the interim, which includes flying a spare radiator &#8211; likely to be a full S1 replacement &#8211; on a future shuttle mission.</p>
<p>That option includes bringing back the current S1 radiator system for evaluation of root cause on the ground &#8211; allowing for important lessons learned as the ISS heads into the next decade.</p>
<p>&#8220;The board gave several actions. First was to see what it would take to fly a spare to orbit and perform an R&amp;R (Removal and Replacement) and to bring back the failed system to determine the root cause,&#8221; added the report.</p>
<p>&#8220;Second, was to determine what it would take to ensure that the community was OK with venting this particular panel in the near future to protect for a loop leak.</p>
<p>&#8220;Third, was to investigate potential software changes, hazard waivers, etc to help MOD and the crew detect and isolate failures to individual panels with minimal loss of ammonia.</p>
<p>&#8220;This may require changes to the software to use ATA tank quantity/pressure vs accum pressure for detection, possible waiver of the radiator over pressurization constraint, etc.&#8221;</p>
<p>Such issues once again highlight how <a href="http://www.nasaspaceflight.com/2009/03/aresorion-slipping-18-months-shuttle-extension-upper-hand/" target="_blank">the proposed shuttle extension</a> may provide a major benefit to the ISS, with not only the ability to carry major replacement hardware to orbit, but also the down mass capability that may be called upon, as seen with the potential option to bring the S1 Radiator back to Earth.</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9399&amp;ts=1328834909" style="display:none;" alt="pixelstats trackingpixel"/>

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/04/iss-concern-s1-radiator-may-require-replacement-shuttle-mission/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Discovery deservicing in OPF-3 &#8211; TPS assessment positive</title>
		<link>http://www.nasaspaceflight.com/2009/03/discovery-deservicing-in-opf-3-tps-assessment-positive/</link>
		<comments>http://www.nasaspaceflight.com/2009/03/discovery-deservicing-in-opf-3-tps-assessment-positive/#comments</comments>
		<pubDate>Mon, 30 Mar 2009 14:04:06 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[STS-119]]></category>
		<category><![CDATA[STS-128]]></category>
		<category><![CDATA[TPS]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9363</guid>
		<description><![CDATA[Following her 13 day mission in space on STS-119, Discovery is being deserviced inside her Orbiter Processing Facility (OPF-3), ahead of her next mission, STS-128. Close inspections of her Thermal Protection System (TPS) created a list of work that will be carried during her 101 day processing flow. Discovery touched down on KSC runway 15 [...]


Related posts:<ol><li><a href='http://www.nasaspaceflight.com/2008/12/endeavour-departs-edwards-sca-piggyback-ride-texas/' rel='bookmark' title='Permanent Link: Endeavour and her SCA piggyback ride arrive in Louisiana, via JSC flyover'>Endeavour and her SCA piggyback ride arrive in Louisiana, via JSC flyover</a> <small>The Shuttle Carrier Aircraft (SCA) and Endeavour departed from Edwards...</small></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>Following her 13 day mission in space on STS-119, Discovery is being deserviced inside her Orbiter Processing Facility (OPF-3), ahead of her next mission, STS-128. Close inspections of her Thermal Protection System (TPS) created a list of work that will be carried during her 101 day processing flow.</p>
<p><span id="more-9363"></span></p>
<p>Discovery touched down on KSC runway 15 at 15:14:45 local time on Saturday, completing a successful mission installing the final solar array truss to bring the ISS to full power.</p>
<p><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=2.0">STS-119/STS-128 UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=33.0">L2 STS-119 (MMT Level)</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></span></p>
<p>De-orbit burn, re-entry, and landing performance were all nominal, with entry controllers reporting the flagship orbiter enjoyed a faultless return home.</p>
<p>Once safed at the Shuttle Landing Facility (SLF), S0069 Integrated Roll-In operations picked up. Orbiter tow first motion from the SLF to OPF3 was at 18:46 local, before she was spotted in OPF-3 at 20:55. Fuel cell shutdown/ground power transfer was completed at 00:30 on Sunday.</p>
<p>TPS assessment began at 15:40 on Saturday, with engineers documenting most areas of Discovery&#8217;s heatshield, prior to being towed back to the OPF.</p>
<p>&#8220;Overall vehicle looked good. There was one protruding Ames gap filler, it was the gap filler seen on orbit,&#8221; noted the TPS assessment report on L2. &#8220;There were three instances of missing putty repairs.&#8221;</p>
<p><img class="alignleft size-full wp-image-9365" title="a226" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a226.jpg" alt="a226" width="260" height="180" />A special Boundary Layer Transition (BLT) Detailed Test Objective (DTO), which involved one tile on Discovery&#8217;s belly protruding slightly, was also inspected, with no damage reported in the local area.</p>
<p>&#8220;BLT protuberance did not exhibit significant slumping or erosion,&#8221; added the report. &#8220;Structural integrity was maintained. BLT protuberance tile did not appear slumped, although minor glazing was noted along the trailing edge of the fin. Streaking was noted along 3 tiles downstream of the protuberance. &#8221;</p>
<p>Also reported were the thermal barriers on the Nose Landing Gear Door (NLGD), which provided close up views of an item of interest found during Flight Day 3&#8242;s RPM photography.</p>
<p>&#8220;On orbit &#8216;fray&#8217; on Forward NLGD thermal barrier was actually frayed edge of patch, no damage to weave of fabric noted,&#8221; added the report, before listing other areas of interest on the forward section of Discovery.</p>
<p>&#8220;Right portion of Arrowhead Blanket was protruding .05&#8221; around attach point. Chin panel -441 gap filler had one tear on the right side approximately 1&#8221; long. Right hand side gap measurement was .180, left hand side gap measurement was .170, and the center measurement was .210.&#8221;</p>
<p>&#8220;Unknown marking on the V070-391035-313 tile was an orange marking approximately 2&#8221; long, no protrusion noted. Large amount of degradation seen on FRCS (Forward Reaction Control System) thermal barrier R4R. Damage was noted in previous repair location.&#8221;</p>
<p><img class="alignleft size-full wp-image-9366" title="a316" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a316.jpg" alt="a316" width="244" height="182" />For Discovery&#8217;s Main Landing Gear Doors (MLGS), the thermal barriers also appeared nominal, while a gap filler &#8211; noticed in the RPM photography, actually survived re-entry, as opposed to coming lose during Flight Control Surface checkouts on Flight Day 12, or during re-entry.</p>
<p>&#8220;Gap filler on the left hand inboard elevon was still present. The protrusion appeared to be the same as on orbit with no obvious effects of overtemp. The gap filler was confirmed to be 3 plies of Ames.&#8221;</p>
<p>&#8220;Left hand inboard elevon damage appeared to be the same as on orbit, with and estimated depth of .3-.4”. Rounding of damage edges indicates evidence of possible heating.*</p>
<p>Other items of interest included missing putty repairs on three tiles &#8211; which can be expected, a broken &#8220;piano key&#8221; tile on the body flap, and a protruding gap filler on one of Discovery&#8217;s OMS Pods &#8211; which have performed well since the couple of incidents with torn stitching between the tiles and the blankets.</p>
<p>&#8220;Discolorations noted on orbit aft of the LH ETD were not noted as abnormal on the runway,&#8221; the report added. &#8220;Piano key tile above the body flap had a large portion of the cantilever broken off.</p>
<p><img class="alignleft size-full wp-image-9369" title="a414" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a414.jpg" alt="a414" width="247" height="165" />&#8220;Tile between engines 2 and 3 had an edge broken off. Piece of material debris identified on top of the RH (Right Hand) side of the body flap. Source unknown (see left image).</p>
<p>&#8220;OMS protruding gap filler noted on orbit as 500-001 was visibly frayed. It is notable that this portion of the gap filler was not noted as protruding on orbit.&#8221;</p>
<p>Further inspections on Discovery&#8217;s TPS are being conducted in the OPF, ahead of final deservicing tasks and preparations to enter her into the STS-128 processing flow, which has technically started with post STS-119 work.</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size. STS-119 L2 Section includes same collections of all MMT presentations, images and video, now over 3,000 mb in total.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9363&amp;ts=1328834909" style="display:none;" alt="pixelstats trackingpixel"/>

<p>Related posts:<ol><li><a href='http://www.nasaspaceflight.com/2008/12/endeavour-departs-edwards-sca-piggyback-ride-texas/' rel='bookmark' title='Permanent Link: Endeavour and her SCA piggyback ride arrive in Louisiana, via JSC flyover'>Endeavour and her SCA piggyback ride arrive in Louisiana, via JSC flyover</a> <small>The Shuttle Carrier Aircraft (SCA) and Endeavour departed from Edwards...</small></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/03/discovery-deservicing-in-opf-3-tps-assessment-positive/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>STS-119: Discovery returns home to Florida &#8211; Soyuz TMA-14 docks</title>
		<link>http://www.nasaspaceflight.com/2009/03/sts-119-live-discovery-for-florida-return/</link>
		<comments>http://www.nasaspaceflight.com/2009/03/sts-119-live-discovery-for-florida-return/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 15:55:39 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[STS-119]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9380</guid>
		<description><![CDATA[Discovery has completed her highly successful mission to the International Space Station (ISS) with a return to the Kennedy Space Center (KSC) on Saturday. The crew of STS-119 had two opportunities to land in Florida &#8211; with the first waved off due to unpredictable weather. A GO for the deorbit burn on Orbit 202 was given, [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p>Discovery has completed her highly successful mission to the International Space Station (ISS) with a return to the Kennedy Space Center (KSC) on Saturday. The crew of STS-119 had two opportunities to land in Florida &#8211; with the first waved off due to unpredictable weather. A GO for the deorbit burn on Orbit 202 was given, before a nominal landing time of 7:14pm GMT on runway 15. Meanwhile, the Russian Soyuz TMA-14 has docked with the ISS.</p>
<p><span id="more-9380"></span></p>
<p>Discovery has marked yet another issue-free mission on orbit &#8211; highlighted by the successful installation and deployment of the S6 integrated truss segment and solar array wings &#8211; with only a handful of minor items of interest for the MER (Mission Evaluation Room), with shuttle manager John Shannon previewing the weekend landing as an amazing feat.</p>
<p><img class="alignleft size-full wp-image-9350" title="a225" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a225.jpg" alt="a225" width="248" height="159" />&#8220;These are great days in space,&#8221; Mr Shannon said, opening the latest Shuttle Stand-Up/Integration report on L2. &#8220;OV-103 (Discovery) undocked from Station, giving us a chance to see the fully completed truss assembly.</p>
<p>&#8220;The 18 Soyuz safely lifted off, headed for Station. At this time, there are 13 human beings in low-earth orbit &#8211; an amazing feat. This flight has been unbelievably smooth. Everyone worked extremely hard getting to this launch, with many weekends worked and many hours of overtime.&#8221;</p>
<p>&#8220;STS-119/15A had2 a very successful docked mission,&#8221; added MMT chairman Leroy Cain, who noted he &#8220;is very proud of the whole team.&#8221;</p>
<p><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=2.0">STS-119 LIVE UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?topic=15996.0">Soyuz TMA-14  LIVE Updates</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=33.0">L2 STS-119 LIVE (MMT Level)</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></span></p>
<p>The Soyuz TMA-14 launched on Thursday, carrying the next ISS commander Gennady Padalka, flight engineer Michael Barratt and space tourist, Charles Simonyi.</p>
<p>Docking at just after 1pm GMT was successful, although Padlaka had to complete the approach manually, following what appears to have been an anomoly with the KURS automated docking system.</p>
<p>Confirmation Discovery is safe to return came via the DAT (Damage Assessment Team) report to the MMT (Mission Management Team) on Friday, following an overview of the Late Inspections that were carried out on Flight Day 12.</p>
<p>No items of concern were found on Discovery&#8217;s TPS (Thermal Protection System), which has once again proved the major advancements by the Michoud Assembly Facility (MAF) and the SSP (Space Shuttle Program) in reducing foam and ice liberation from the External Tanks during ascent.</p>
<p>Had a major problem been found with the heatshield, Discovery was still &#8211; as pre-planned &#8211; close enough to the ISS to return to the Station and wait for rescue by the LON (Launch On Need) vehicle &#8211; which would have been Endeavour.</p>
<p>That LON requirement has been stood down by the successful TPS review by DAT, and Discovery&#8217;s opening task on Flight Day 14 was to perform burn to finalize the orbiter&#8217;s separation from the ISS.</p>
<p><img class="alignleft size-full wp-image-9352" title="a53" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a53.jpg" alt="a53" width="240" height="191" />The crew awoke on Flight Day 14 to a song from ABBA, before heading into deorbit preparations, which resulted in this afternoon&#8217;s SIMPLEX burn (a two-OMS retrograde burn), slowing Discovery orbital velocity and taking her out of orbit for landing just over one hour later.</p>
<p><em>L2 Members can download several high quality re-entry videos, via a handheld camcorder on the flight deck, from deorbit burn to post landing, with crew audio. <a href="http://forum.nasaspaceflight.com/index.php?topic=8873.0" target="_blank">*Click Here*</a>  for free trailers.</em></p>
<p>Powering the hydraulic systems that control Discovery&#8217;s Flight Control Surfaces (FCS) &#8211; which were checked out on Flight Day 13 &#8211; were three APUs (Auxiliary Power Units), although this is based on redundancy, as only one is required for re-entry and landing.</p>
<p>An issue with APU 2 was noted late in the mission, although this didn&#8217;t hold any impact for Discovery&#8217;s final hours prior to her wheels stopping on the Shuttle Landing Facility (SLF)</p>
<p>&#8220;APU 2 heater thermostat dithering. This is a problem seen numerous times before and is characterized as a &#8220;set point&#8221; change,&#8221; noted the MER report on L2. &#8220;No impact to flight or to APU operation. May require replacement post flight.&#8221;</p>
<p>Discovery&#8217;s re-entry also mark a shuttle first, with data being gathered by a special Boundary Layer Transition (BLT) Detailed Test Objective (DTO) that is installed on her TPS.</p>
<p>The DTO will attempt to gather data during entry regarding the aerothermal effects caused by the boundary layer transitioning from laminar flow to turbulent flow at a high Mach number. <a href="http://www.nasaspaceflight.com/2007/12/sts-126-set-to-carry-out-special-reentry-experiment/" target="_blank">The test was originally set to debut with Endeavour on STS-126</a>.</p>
<p><img class="alignleft size-full wp-image-9349" title="a315" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a315.jpg" alt="a315" width="300" height="175" />&#8220;Boundary Layer trip induced by a protuberance placed on a lower surface tile on the port wing,&#8221; noted associated documentation on L2. &#8220;Protuberance height of 0.25 inches is expected to trip boundary layer at Mach 15. Thermocouples installed on protuberance tile and downstream tiles will capture data.&#8221;</p>
<p>Before this DTO was approved by shuttle managers, an extensive review was conducted to ensure that the changes would not affect the performance of the Orbiter during re-entry, and that the protuberance tile was placed in an area that would minimize the occurrence of damage to the protuberance tile by ascent debris.</p>
<p>Images taken from Flight Day 3&#8242;s RPM &#8211; used to take hi-res photography of Discovery&#8217;s belly &#8211; showed the tile area in question was clean and ready for Saturday&#8217;s re-entry test.</p>
<p>Now Discovery has landing, she will head into S0069 (roll-in) operations, ahead of being spotted in her Orbiter Processing Facility (OPF). Post flight processing will begin on Monday, starting with opening TPS inspections and the safing of her power systems.</p>
<p>She will then begin flight processing for <a href="http://www.nasaspaceflight.com/2009/01/128-discovery-prcb-updates-mission-baseline/" target="_blank">her next mission, STS-128, which was originally set to fly with Atlantis, ahead of realignment of the shuttle manifest</a>.</p>
<p><img class="alignleft size-full wp-image-9351" title="a413" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a413.jpg" alt="a413" width="250" height="147" />Targeting launch for No Earlier Than (NET) August 6, 2009, Discovery will be prepared for a 13 day, 3 EVA, mission to the ISS that will include the flight of the TriDAR AR&amp;D Sensor Detailed Test Objective (DTO), the next Boundary Layer Transition (BLT) DTO, and the first flight of the OI-34 flight software.</p>
<p>Also riding uphill with Discovery will be a new crew member for the ISS &#8211; Nicole Stott &#8211; as well as MISSE (Materials on International Space Station Experiments) 6A and 6B, SIMPLEX, MAUI, and SEITI.</p>
<p>However, the primary payload for Space Shuttle Discovery will be the MPLM (Multi-Purpose Logistics Module) Leonardo &#8211; returned from the highly successful STS-126 mission in November &#8211; and the Lightweight Experiment Support Structure Carrier with an Ammonia Tank Assembly.</p>
<p>Interestingly, assessments on how to accelerate STS-128/17A are in progress, according to the latest Stand-Up report, which will be discussed after the landing of STS-119.</p>
<p>Two more missions are planned for Discovery, <a href="http://www.nasaspaceflight.com/2009/02/sts-131-logistics-flight-baselined-by-prcb/" target="_blank">STS-131</a> and <a href="http://www.nasaspaceflight.com/2009/02/shuttle-planning-clfs-ams-noted-maf-extra-ets/" target="_blank">STS-134 &#8211; the latter awaiting final approval</a>, with the possibility of additional flights via shuttle extension.</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size. STS-119 L2 Section includes same collections of all MMT presentations, images and video, now over 3,000 mb in total.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9380&amp;ts=1328834909" style="display:none;" alt="pixelstats trackingpixel"/>

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/03/sts-119-live-discovery-for-florida-return/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>STS-119: Amazing Discovery undocks from ISS, heads to Late Inspection</title>
		<link>http://www.nasaspaceflight.com/2009/03/sts-119-live-amazing-discovery-set-for-undocking-and-flyaround/</link>
		<comments>http://www.nasaspaceflight.com/2009/03/sts-119-live-amazing-discovery-set-for-undocking-and-flyaround/#comments</comments>
		<pubDate>Wed, 25 Mar 2009 13:10:05 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[ISS]]></category>
		<category><![CDATA[STS-119]]></category>
		<category><![CDATA[TPS]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9298</guid>
		<description><![CDATA[Shuttle manager John Shannon has described Discovery&#8217;s performance as &#8220;amazing&#8221;, ahead of Wednesday&#8217;s undocking from the International Space Station (ISS). Discovery is now heading to Late Inspections of her Thermal Protection System (TPS) on Flight Day 12 of STS-119. Final Shuttle/Station transfers took place prior to undocking, mainly relating to human samples stored in cold [...]


Related posts:<ol><li><a href='http://www.nasaspaceflight.com/2009/02/progress-m-66-launches-heads-for-the-international-space-station/' rel='bookmark' title='Permanent Link: Progress M-66 launches, heads for the International Space Station'>Progress M-66 launches, heads for the International Space Station</a> <small>The Russian cargo ship Progress M-66/32P has launched from the...</small></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>Shuttle manager John Shannon has described Discovery&#8217;s performance as &#8220;amazing&#8221;, ahead of Wednesday&#8217;s undocking from the International Space Station (ISS). Discovery is now heading to Late Inspections of her Thermal Protection System (TPS) on Flight Day 12 of STS-119.</p>
<p><span id="more-9298"></span></p>
<p>Final Shuttle/Station transfers took place prior to undocking, mainly relating to human samples stored in cold bags, which was the cause of the change to the plan relating to the departure timeline.</p>
<p><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=2.0">STS-119 LIVE UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=33.0">L2 STS-119 LIVE (MMT Level)</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></span></p>
<p>Normally the hatches would be closed the day before undocking, but to ensure the samples remained within their &#8220;thermal clock&#8221; ahead of being handed over to scientists on the ground, hatch closure was delayed to as late as was viable.</p>
<p>Rendezvous tools checkouts also took place ahead of the farewell between the crews of Discovery and the International Space Station, before hatch closure and leak checks.</p>
<p><img class="alignleft size-full wp-image-9313" title="a09" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a09.gif" alt="a09" width="269" height="185" />Following undocking, Discovery performed a full, one lap, flyaround of the Station, which provided the first images of the ISS with all four of its solar arrays deployed - thanks to the successful delivery and installation of the final integrated truss segment, S6.</p>
<p>ISS Commander Mike Finke was asking for video of the flyaround, eager to see his newly grown Station.</p>
<p>Once the flyaround was completed, Discovery performed separation burns to increase the distance between herself and the ISS. </p>
<p>Refer to the live update pages for up to the second events, images and video.</p>
<p><strong>Final checks of Discovery&#8217;s TPS:</strong></p>
<p>Late Inspections will be completed before the distance between Discovery and the ISS are too great, allowing for the orbiter to return to the ISS in the event of serious damage being found during the final check of the Thermal Protection System (TPS).</p>
<p><img class="alignleft size-full wp-image-9303" title="a222" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a222.jpg" alt="a222" width="270" height="198" />This procedure, utilizing the Laser Dynamic Range Imager (LDRI) and sensor suite package on the end of the Orbiter Boom Sensor System (OBSS), will take place on Flight Day 12.</p>
<p>Given the lack of damage observed during Flight Day 2&#8242;s opening inspections and <a href="http://www.nasaspaceflight.com/2009/03/sts-119-complex-robotics-s6-tps-to-be-cleared/" target="_blank">Flight Day 3&#8242;s RPM (Rbar Pitch Maneuver) &#8211; which only found a handful of items that required clearance by the DAT (Damage Assessment Team) on the ground</a> &#8211; the procedure will <a href="http://www.nasaspaceflight.com/2009/03/sts-119-opening-tps-inspections-several-issues-worked/" target="_blank">provide a &#8220;before and after&#8221; overview of Discovery&#8217;s heatshield</a>, in order to check for any damage during her docked phase of the mission.</p>
<p>This is required in case Discovery suffered a MMOD (Micro-Meteoroid Orbital Debris) hit whilst docked. While serious damage is highly unlikely, due to the protection provided by the ISS when docked, orbiters can still be susceptible to hits, <a href="http://www.nasaspaceflight.com/2008/12/endeavour-deservicing-window-damage-failed-to-spread/" target="_blank">especially on their windows</a> and <a href="http://www.nasaspaceflight.com/2006/11/mmod-hit-on-atlantis-was-from-another-vehicle/" target="_blank">radiators &#8211; as seen on previous missions</a>.</p>
<p>The critical area of the RCC (Reinforced Carbon Carbon) Wing Leading Edges (WLE) also have the ability to &#8220;feel&#8221; impacts on their panels, via the WLE Impact Detection System (IDS). Daily presentations on the WLE IDS have noted no &#8220;triggers&#8221; of concern during the docked phase.</p>
<p>The importance of ensuring the TPS is in good condition for re-entry is obvious, with the teams on the ground literally inspecting ever inch of the heatshield.</p>
<p><img class="alignleft size-full wp-image-9304" title="a313" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a313.jpg" alt="a313" width="321" height="260" />Due to the methodical nature of the inspections, even the slightest anomaly with the scans is raised to the Mission Management Team (MMT), <a href="http://www.nasaspaceflight.com/2009/03/sts-119-opening-tps-inspections-several-issues-worked/" target="_blank">as was one issue during Flight Day 2</a>.</p>
<p>&#8220;Picture matching at the start of Stbd (Starboard) scan 2 while at pause pt 13 to image FD2 LDRI missed coverage of lower T-Seal (R7),&#8221; opened a technical presentation to the MMT on L2, which also relates to Flight Day 12&#8242;s Late Inspections.</p>
<p>The missing area of coverage, caused by a slight oscillation on the sensor package, is only a matter of inches across. However,<a href="http://www.nasaspaceflight.com/2009/03/clean-discovery-sights-on-rpm-and-iss-docking/" target="_blank"> thanks to the arsenal of data gained via the RPM and the WLE IDS </a>- and flight history since Return To Flight &#8211; engineers on the ground already know the area in question has not suffered any damage of note.</p>
<p>&#8220;STS-119 FD2 &#8211; Missing LDRI Coverage of Lower Tee 7R: Missing coverage likely due to LDRI Flight Unit 3’s masking, oscillations and system stack up error,&#8221; added the presentation. &#8220;No need for additional imagery in this location.</p>
<p>&#8220;800 mm RPM imagery showed no damage (Detection Resolution 0.3”). No ascent WLE IDS triggers at the 7/8R interface. Coating damage in this region is acceptable due to increased lock side RCC thickness and redundant RCC on the Tee. Minor corrections to late inspection will adequately cover this area.</p>
<p>&#8220;To reduce the risk of this reoccurring for late inspection, we will make real-time adjustments to point the LDRI more like what was <a href="http://www.nasaspaceflight.com/2007/06/tps-inspections-for-atlantis-port-oms-pod-blanket-issue/" target="_blank">flown on STS-117</a> and <a href="http://www.nasaspaceflight.com/2008/03/sts-123-houston-checking-into-strange-ascent-debris-incident/" target="_blank">STS-123 FD2</a>.</p>
<p>&#8220;Half a cross hair adjustment falls within the alignment process that we have with Crew and the Flight Control Team (use this during training sims and flights). On FD4 spoke with PDRS (Payload Deployment and Retrieval System) about our half a cross hair adjustment plans and they are okay with it.&#8221;</p>
<p><img class="alignleft size-full wp-image-9305" title="a412" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a412.jpg" alt="a412" width="180" height="246" />One of the last items to be cleared was a gap filler on the left elevon area of Discovery, which was observed to be protruding.</p>
<p>The concern with protruding gap fillers relates to their potential to disrupt &#8211; or &#8220;trip&#8221; &#8211; the flow of the super hot gases the orbiter will race through during entry interface. Such an event is not a crew/orbiter safety issue, instead it relates to the possibility of increased TPS re-works once she returns to her Orbiter Processing Facility (OPF).</p>
<p>This final item was cleared over the weekend, following a peer review to ensure the gap filler presented no concern to the orbiter.</p>
<p>&#8220;On the mission, the TPS was cleared on Saturday. The team did a great job of working through the gap filler,&#8221; added the Orbiter Project at the Johnson Space Center (JSC) . &#8220;Looking forward to late inspection on Thursday.&#8221;</p>
<p>Such has been the &#8220;clean&#8221; performance of Discovery during STS-119, Mr Shannon once again praised the teams, before rallying them to one final push to return the orbiter and crew home safely.</p>
<p>&#8220;We couldn&#8217;t have a better vehicle on orbit. It&#8217;s just amazing,&#8221; Mr Shannon noted. &#8220;Great mission. Let&#8217;s keep our focus. We&#8217;re going to be flying this entire week. It&#8217;s been going extremely well, and we just want to finish it up the right way. Thanks for everything you&#8217;ve done.&#8221;</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size. STS-119 L2 Section includes same collections of all MMT presentations, images and video, now over 3,000 mb in total.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9298&amp;ts=1328834909" style="display:none;" alt="pixelstats trackingpixel"/>

<p>Related posts:<ol><li><a href='http://www.nasaspaceflight.com/2009/02/progress-m-66-launches-heads-for-the-international-space-station/' rel='bookmark' title='Permanent Link: Progress M-66 launches, heads for the International Space Station'>Progress M-66 launches, heads for the International Space Station</a> <small>The Russian cargo ship Progress M-66/32P has launched from the...</small></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/03/sts-119-live-amazing-discovery-set-for-undocking-and-flyaround/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>STS-119: NASA troubleshoots during problematic final EVA</title>
		<link>http://www.nasaspaceflight.com/2009/03/sts-119-problematic-troubleshooting-during-final-eva/</link>
		<comments>http://www.nasaspaceflight.com/2009/03/sts-119-problematic-troubleshooting-during-final-eva/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 21:30:39 +0000</pubDate>
		<dc:creator>Chris Bergin</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Shuttle]]></category>
		<category><![CDATA[EVA]]></category>
		<category><![CDATA[ISS]]></category>
		<category><![CDATA[STS-119]]></category>

		<guid isPermaLink="false">http://www.nasaspaceflight.com/?p=9273</guid>
		<description><![CDATA[Spacewalkers Richard Arnold and Joseph Acaba have completed the final EVA of STS-119, tasked with several replanned elements, including troubleshooting on the Unpressurized Cargo Carrier Attach System (UCCAS), which proved to be problematic. Meanwhile, no issues of note are being worked on Discovery, although engineers are monitoring the amount of propellant Discovery has been using [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p>Spacewalkers Richard Arnold and Joseph Acaba have completed the final EVA of STS-119, tasked with several replanned elements, including troubleshooting on the Unpressurized Cargo Carrier Attach System (UCCAS), which proved to be problematic. Meanwhile, no issues of note are being worked on Discovery, although engineers are monitoring the amount of propellant Discovery has been using during the docked phase of the mission.</p>
<p><span id="more-9273"></span> <strong>EVA-3:</strong></p>
<p>With STS-119 reduced from four to three EVAs, due to the need to undock prior to the Soyuz cut out, EVA-2 was also replanned.</p>
<p>Conducted Swanson and Acaba, EVA-2 worked on P6 Battery replacement preps, deployment of the P3 and S3 Truss Payload Attachment Systems, P1/P3 Fluid Jumper connections/Radiator Beam Valve Module Thermal Cover removal, and P6 Power and Data Grapple Fixture retrieval.</p>
<p>However, issues were noted when attempts were made to unstow a cargo carrier attachment system (P3 NADIR UCCAS), caused by an incorrect installation of a locking pin.</p>
<p>&#8220;A hardware issue during EVA 2 prevented the deployment of the P3 nadir UCCAS,&#8221; noted on of the MMT department presentations on L2. &#8220;Real time troubleshooting was unsuccessful and the associated timeline impact caused several tasks to be dropped from EVA 2.&#8221;</p>
<p><img class="alignleft size-full wp-image-9275" title="a219" src="http://www.nasaspaceflight.com/wp-content/uploads/2009/03/a219.jpg" alt="a219" width="349" height="225" />Work on the locking pin was unsuccessful, leading to photography being taken for further evaluation on the ground, while the hardware was tied down until an EVA in the future can look into solving the issue at a later date.</p>
<p>EVA-3 tasks also included the relocation of a CETA (Crew and Equipment Transfer Assembly) Cart. Currently both CETA carts are on the port side of the MT (Mobile Transporter), one will be moved to the starboard side for STS-127 activities.</p>
<p>&#8220;S3 Outboard/Zenith PAS deploy: deferred from EVA-2 due to issues with the P3 UCCAS,&#8221; are among other tasks, along with the get aheads of: &#8220;LEE (Latching End Effector) B Lube: Lubricate the snares or SSRMS (Space Station Remote Manipulator System) LEE B side.&#8221;</p>
<p>Other get-aheads include: &#8220;S1/S3 Segment-Segment Attach System BBC Panel Reconfig and the installation of the CETA Coupler.</p>
<p>&#8220;S1/S3 Fluid Jumper install: same for the starboard side. P1 FHRC P-Clamp release: needed if/when it becomes necessary to replace the P1 FHRC. S1 FHRC P-Clamp release: same for the starboard side,&#8221; noted some of the other get-aheads, although not all of the items could be completed due to time available in the EVA.</p>
<p><strong>Discovery Latest:</strong></p>
<p>The Mission Management Team (MMT) met on Monday with no new issues in work with Discovery, with only a couple of new additions on the Mission Evaluation Room (MER) list over the weekend.</p>
<p><span style="MS Shell Dlg;"><span style="Arial;"><div class="L2Info right"><h4>See Also</h4><ul><li><a href="http://forum.nasaspaceflight.com/index.php?board=2.0">STS-119 LIVE UPDATES</a></li><li><a href="http://forum.nasaspaceflight.com/index.php?board=33.0">L2 STS-119 LIVE (MMT Level)</a></li><li><a href="http://www.nasaspaceflight.com/l2/">Click here to Join L2</a></li></ul></div></span></span></span></p>
<p>One note references an increased use of propellant by Discovery for this stage of the mission based on predictions, although that could be expected, following the use of her thrusters during the S6 Solar Array deploy, where she took control of the shuttle/station complex&#8217;s attitude in tandem with the Russian thrusters on the Station.</p>
<p>In addition, Flight Day 8 saw the precautionary DAM (Debris Avoidance Manoeuvre) being conducted by Discovery&#8217;s Digital Autopilot (DAP), which raised the Station away from a potential conjunction threat.</p>
<p>&#8220;A potential conjunction with orbital debris (Object 26264- CZ-4 Debris) was identified and required that a Debris Avoidance Manoeuvre (DAM) be performed to clear the ISS/Shuttle stack,&#8221; noted one MMT presentation.</p>
<p>&#8220;A retrograde delta V of ~0.9 feet per second (out of a targeted 1.0 fps) was generated by holding attitude in the undock attitude (ISS 0, 0, 0 roll, pitch, yaw) for 3 hours. The stack was then maneuvered back to the nominal Torque Equilibrium Attitude (TEA) before crew sleep.&#8221;</p>
<p>The other issue raised over the weekend related to a pressure anomaly on a GN2 regulator located in the midbody (midfuselage).</p>
<p>&#8220;After GN2 Repress on FD 6 the pressure downstream of the system 2 GN2 200 psig regulator gradually climbed to 267 psig over 20 hours,&#8221; noted an associated presentation to the MMT. &#8220;Rise in pressure attributed to an in specification leakage in a closed volume.</p>
<p>&#8220;The crew opened the system 2 water tank regulator to increase system volume and upon a subsequent waste water dump the pressure returned to a nominal 204 psig. The pressure has been monitored since the opening of the water tank regulator and the pressure has remained at around 204 psig.&#8221;</p>
<p>As of Monday&#8217;s MMT, no IFAs (In Flight Anomalies) or MER level &#8220;funnies&#8221; were in need of discussion, highlighting Discovery&#8217;s superb performance on this mission.</p>
<p><a href="http://www.nasaspaceflight.com/l2/"><em><span><span><span><em><span><span lang="EN-GB"><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style="color: #0066cc;">L2 members</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></em></span></span></span></em></a><em><span><span><em><span><span lang="EN-GB">: Documentation &#8211; from which the above article has quoted snippets &#8211; is available in full in the related L2 sections, now over 4000 gbs in size. STS-119 L2 Section includes same collections of all MMT presentations, images and video, now over 3,000 mb in total.</span></span></em></span></span></em></p>
<img src="http://www.nasaspaceflight.com/wp-content/plugins/pixelstats/trackingpixel.php?post_id=9273&amp;ts=1328834909" style="display:none;" alt="pixelstats trackingpixel"/>

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.nasaspaceflight.com/2009/03/sts-119-problematic-troubleshooting-during-final-eva/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

