{"id":40588,"date":"2010-11-29T21:21:39","date_gmt":"2010-11-29T13:21:39","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/sts-133-the-battle-continues-for-et-137-flight-rationale\/"},"modified":"2010-11-29T21:21:39","modified_gmt":"2010-11-29T13:21:39","slug":"sts-133-the-battle-continues-for-et-137-flight-rationale","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/sts-133-the-battle-continues-for-et-137-flight-rationale\/","title":{"rendered":"STS-133: The battle continues for ET-137 flight rationale"},"content":{"rendered":"<p>Despite the large amount of progress made towards flight rationale \u2013 called for in relation to Discovery\u2019s External Tank (ET-137) stringer cracks \u2013 teams are heading into another week of deliberations, with a large amount of work ahead of them. Although STS-133 is threatening to move into next year, NASA managers will continue to evaluate the opportunity to make a late December window.<\/p>\n<p>STS-133 ET-137 Latest:<\/p>\n<p>Last week\u2019s Program Requirements Control Board (PRCB) meeting was \u2013 at least in the eyes of some sources close to the situation \u2013 set to show \u201ca path through the trees\u201d on enabling NASA managers to be satisfied the repaired ET-137 would be safe to fly.<\/p>\n<p>However, in a sign of just how seriously the Agency and its contractors take safety, the cautious approach of reaching deeper into the root cause findings, along with further evaluations into the potential ascent hazards, was opted for early into Thursday\u2019s meeting.<\/p>\n<h4 class=\"widget-title penci-border-arrow\">See Also<\/h4>\n<ul>\n<li>STS-133 LIVE UPDATES<\/li>\n<li>L2 STS-133 Special Section<\/li>\n<li>Click here to Join L2<\/li>\n<\/ul>\n<p>With ET-137 now in a repaired state at the pad, managers were hoping to take a launch window opportunity which ranged from December 3 to December 7. With the decision to delay, the realigned target was pushed to the next window, ranging from December 17 through to December 20 \u2013 although this window is simply for planning purposes at this stage.<\/p>\n<p>\u201cThere is still significant open work to understand root cause and risk associated with stringer cracks. The schedule of open work reflected an ECD (Estimated Completion Date) of 12\/15. Therefore, the Dec 3rd-7th launch window is not feasible. For planning purposes, launch is assumed to be NET (No Earlier Than) 12\/17,\u201d noted the PRCB summary (via L2).<\/p>\n<p>STS-133 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-133\/<\/p>\n<p>As noted by Space Shuttle Program (SSP) manager John Shannon, an internal status update will be conducted at the next scheduled PRCB meeting this coming Thursday, prior to updating NASA management on the Friday. At present, the procedure towards the Launch Status meeting \u2013 a mini Agency Flight Readiness Review (FRR) to confirm a new launch date \u2013 will remain on hold for at least a week.<\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" class=\"alignleft size-full wp-image-17037\" title=\"A321\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/11\/A3211.jpg\" alt=\"\" width=\"340\" height=\"270\">As noted in presentations to the November 18 PRCB, progress was being made on flight rationale, although a lot was riding on finding issues specific to the two cracked stringers on ET-137, namely S6 and S7. This proved to be unsuccessful by the time managers met prior to Thanksgiving.<br \/>\n&nbsp;<br \/>\n\u201cProximate root cause for the stringer cracks has not been identified. Initial evaluation of the crack locations and surfaces indicate that there was not a pre-existing flaw. However, additional work is planned to determine whether the crack could have initiated during installation and then propagated under cryo loading,\u201d added the November 25 PRCB notes.<\/p>\n<p>Space tourism guides<path d=\"M7.59009 18.59L9.00009 20L17.0001 12L9.00009 4L7.59009 5.41L14.1701 12\" style=\"animation: initial !important; background: initial !important; border: 0px !important; box-shadow: none !important; color: inherit !important; cursor: inherit !important; direction: inherit !important; display: inline !important; fill: currentcolor !important; filter: initial !important; float: none !important; margin: 0px !important; opacity: initial !important; outline: 0px !important; overflow: initial !important; padding: 0px !important; stroke: initial !important; transform: initial !important; vertical-align: initial !important; visibility: inherit !important;\"><\/path>NASA mission patches<path d=\"M7.59009 18.59L9.00009 20L17.0001 12L9.00009 4L7.59009 5.41L14.1701 12\" style=\"animation: initial !important; background: initial !important; border: 0px !important; box-shadow: none !important; color: inherit !important; cursor: inherit !important; direction: inherit !important; display: inline !important; fill: currentcolor !important; filter: initial !important; float: none !important; margin: 0px !important; opacity: initial !important; outline: 0px !important; overflow: initial !important; padding: 0px !important; stroke: initial !important; transform: initial !important; vertical-align: initial !important; visibility: inherit !important;\"><\/path>Spaceflight news subscription<path d=\"M7.59009 18.59L9.00009 20L17.0001 12L9.00009 4L7.59009 5.41L14.1701 12\" style=\"animation: initial !important; background: initial !important; border: 0px !important; box-shadow: none !important; color: inherit !important; cursor: inherit !important; direction: inherit !important; display: inline !important; fill: currentcolor !important; filter: initial !important; float: none !important; margin: 0px !important; opacity: initial !important; outline: 0px !important; overflow: initial !important; padding: 0px !important; stroke: initial !important; transform: initial !important; vertical-align: initial !important; visibility: inherit !important;\"><\/path>\n<p>     (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n<p>\u201cNo issues were identified during disassembly\/re-assembly of S6 and S7 (e.g. shims not installed originally and were not required, smooth flat skin with no defects noted). There are 91 items identified in the fishbone analysis, 21 of which are considered high interest items.&nbsp;<\/p>\n<p>\u201cSince the stress models show that a \u201cgood\u201d stringer would not fail in the manner observed, manufacturing\/installation induced defects\/stresses are considered primary contributors. However, additional work is planned to ensure the models are sufficiently accurate to conclude a \u201cgood\u201d stringer would not crack if properly installed.\u201d<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-17036\" title=\"A4521\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/11\/A45211.jpg\" alt=\"\" width=\"335\" height=\"270\">The cracked stringers were first noticed via a crack in the tank\u2019s Thermal Protection System (TPS) foam, when cameras spotted the foam defect localized on an area of the LOX\/Intertank flange.<\/p>\n<p>While the foam crack was noticed during the draining of ET-137 \u2013 following the scrub relating to the leak on the Ground Umbilical Carrier Plate (GUCP) \u2013 it was only after the foam was removed that the four cracks were found in the two stringers.<\/p>\n<p>A question being worked relates to if the cryo process of tanking provides the highest amount of stress on the stringers \u2013 thus allowing engineers to be confident with status of the stringers prior to launch if no defects are detected, or if higher stresses during ascent (such as MaxQ) could result in stringer defects propagating and ultimately leading to foam liberations \u2013 that in turn may impact on to the orbiter.<\/p>\n<p>\u201cTo determine whether tanking is a good screen for this failure mode, thermally induced stresses during cryo loading were compared to in-flight loads: Initial analysis results show the stress during cryo loading is higher than in-flight for the region of about the first 4 fasteners but flight loads are predicted to be higher than cryo loads for the region of the 5th through 8th fasteners,\u201d continued the PRCB notes.<\/p>\n<p>\u201cSince certain simplifying assumptions were made, a higher fidelity assessment will be performed.<\/p>\n<p>\u201cAnalysis to demonstrate structural fault tolerance is in work. Preliminary debris analysis indicates that stringer debris is not expected but TPS liberation is possible. However, this analysis assumed the TPS was not bonded. A higher fidelity assessment will be performed.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-17038\" title=\"A412\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/11\/A4123.jpg\" alt=\"\" width=\"339\" height=\"239\">Large sections of the flange also underwent Non Destructive Evaluations (NDE) at the pad, via in-situ scanning techniques \u2013 with results showing no other defects have been noted in other stringers on ET-137, although the PRCB did note that the critical flaw size and probability of detection have not been determined.<\/p>\n<p>Some areas of the flange also remain outstanding due to the limitations of pad access, while engineers had already begun scans on the lower flange areas, located between the intertank and the LH2 tank.<\/p>\n<p>With the teams now back after the Thanksgiving break, a list of \u201csignificant open work\u201d has been created, ranging from \u201cmining\u201d for historical crack data on the root cause drive, to rechecking ascent imagery in an attempt to catch for any cracks that may have formed in the flange area during the ride uphill \u2013 although it has been previously noted that no notable foam liberations have originated from the LOX\/Intertank flange region.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-17039\" title=\"A69\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/11\/A692.jpg\" alt=\"\" width=\"335\" height=\"235\">\u201cPrevious crack data mining and how assembly\/installation may contribute. Higher fidelity test fixture (utilizing complete stringer sections instead of just coupon testing), testing with flaws. The objective is to induce cracks to better understand the failure mechanism,\u201d listed the PRCB notes.<\/p>\n<p>\u201cHigher fidelity stress analysis for prelaunch cryo loading and in-flight stresses to understand ability to screen with tanking. Fishbone work to drive out areas that require additional investigation. Structural fail safe analysis (e.g. how many stringers can be lost).Higher fidelity debris analysis for structure and for TPS (e.g. with foam adhered).<\/p>\n<p>\u201cKSC (Kennedy Space Center) evaluation of access for making modifications if deemed necessary. SE&amp;I (Systems Engineering and Integration) relook at imagery to look for U shaped type cracks.\u201d<\/p>\n<p>(Further updates and articles will follow. Refer to live coverage threads linked above. L2 members refer to STS-133 live coverage sections for internal coverage, presentations, images and and updates from engineers and managers. Images used, Lead: NASA.gov. Within the article: via L2 acquired PRCB presentations).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Despite the large amount of progress made towards flight rationale \u2013 called for in relation to Discovery\u2019s External Tank (ET-137) stringer cracks \u2013 teams are heading into another week of deliberations, with a large amount of work ahead of them. Although STS-133 is threatening to move into next year, NASA managers will continue to evaluate [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":29632,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[9021,9051],"class_list":["post-40588","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-et","tag-sts-133"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40588"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=40588"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40588\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/29632"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40588"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40588"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}