{"id":41246,"date":"2008-12-02T22:58:40","date_gmt":"2008-12-02T14:58:40","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/pristine-endeavour-deservicing-at-edwards-window-6-damage-failed-to-spread\/"},"modified":"2008-12-02T22:58:40","modified_gmt":"2008-12-02T14:58:40","slug":"pristine-endeavour-deservicing-at-edwards-window-6-damage-failed-to-spread","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/pristine-endeavour-deservicing-at-edwards-window-6-damage-failed-to-spread\/","title":{"rendered":"Pristine Endeavour deservicing at Edwards \u2013 Window 6 damage failed to spread"},"content":{"rendered":"<p>Engineers are working through post flight deservicing tasks on Endeavour at Dryden Flight Research Facility (DFRC)\/Edwards Air Force Base, with opening engineering images and notes pointing towards an extremely clean vehicle, following Sunday\u2019s landing in California. Images of Endeavour\u2019s Window 6 \u201cthermal pane\u201d \u2013 which suffered from a MMOD strike on orbit \u2013 show the damage did not spread during re-entry.<\/p>\n<\/p>\n<p>Endeavour was towed to the Mate\/Demate facility \u2013 which is used for deservicing the orbiter, and for lifting orbiters on to the back of the SCA (Shuttle Carrier Aircraft) \u2013 late on Sunday local time.<\/p>\n<p>\u201cEndeavour successfully landed at DFRC at 1626 EST yesterday. The orbiter was spotted at the Mate\/Demate at 0106 EST Monday morning,\u201d noted post flight processing. \u201cPost landing operations continue.\u201d<\/p>\n<p>A couple of issues were noted with the opening procedures. notably with the process of transferring power from Endeavour\u2019s Fuel Cells to ground power at the Mate\/Demate facility. However, that was expected to be resolved without a timeline hit to S5022 operations.<\/p>\n<p>The opening report on the condition of Endeavour has already been created, which backs up Mission Management Team (MMT) chair Leroy Cain\u2019s praise for what he believes could may be the \u201ccleanest\u201d orbiter ever, due to the lack of any notable TPS (Thermal Protection System) damage.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-8115\" style=\"black 5px solid;\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2008\/12\/a2.jpg\" alt=\"\" width=\"248\" height=\"187\">Opening evaluations into the landing gear point to good performance during landing \u2013 despite the shorter runway Endeavour touched down on. 800 feet of runway still remained when the orbiter\u2019s wheels stopped.<\/p>\n<p>The runway report is the fourth milestone check of the orbiter\u2019s TPS, following Flight Day 2 inspections via the OBSS (Orbiter Boom Sensor System), Flight Day 3\u2019s RPM (Rbar Pitch Maneuver) images taken from the International Space Station (ISS), and Flight Day 15\u2019s Late Inspections, which finally clear the orbiter for re-entry. The lack of damage is mainly thanks to the performance of Endeavour\u2019s External Tank (ET-129). which suffered hardly any foam loss during ascent.<\/p>\n<p>Rocket building kits<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>SpaceX<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>\n<p>     (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n<p>\u201cOverall the vehicle looked very clean. No further degradation to the damages noted in RPM photos was observed,\u201d noted the runway report on L2. \u201cApproximately 5 tiles had damages greater than 1.0 inch<\/p>\n<p>\u201cOne location of protruding Ames gap filler (as noted on orbit RPM images) was found. Ames was protruding approximately 0.5\u201d. No noticeable local overtemp or change from the on-orbit photo.<\/p>\n<p>In total, only about 10 areas \u2013 all matching the RPM photography \u2013 were listed in the runway report on TPS damage, which is extremely low compared to most flights. Only a handful of areas received some notes of interest, notable on the OMS (Orbital Manuvering System) Pods.<\/p>\n<h4 class=\"widget-title penci-border-arrow\">See Also<\/h4>\n<ul>\n<li>STS-126 POST FLIGHT UPDATES<\/li>\n<li>L2 STS-126 Special (3,500mb)<\/li>\n<li>Click here to Join L2<\/li>\n<\/ul>\n<p>\u201cTwo body flap lower surface tiles have minor damages that appear to have sintered during reentry. Base heat shield tile damage appeared unchanged from the on-orbit photo. Dome heat shield blanket had no tears,\u201d added the report.<\/p>\n<p>\u201cLH (Left Hand) OMS pod gap fillers were protruding similar to on-orbit photos, and were slightly more frayed. Large tile damage on RH (Right Hand) OMS engine base, adjacent to stinger, part number unknown. Dimensions approximately 2\u201d x 3\u201d\u201d<\/p>\n<p>The main area of interest related to how Endeavour\u2019s Window 6 (Pilot side) performed during the return, following the MMOD hit on orbit. While the damage was only to the first of the there panes each window has, thus was safe to re-enter with, extensive analysis was performed by engineers on the ground.<\/p>\n<p>The worst case scenario related to the damage spreading, resulting in small fragments liberating from the window and potentially impacting the aft of the orbiter.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-8116\" style=\"black 5px solid;\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2008\/12\/a3.jpg\" alt=\"\" width=\"192\" height=\"197\">\u201cImpacts are possible along upper surface from window to vertical tail. Maximum impact velocity on tail approximately 1100 ft\/sec,\u201d noted the Window 6 MMOD Debris Transport presentation on L2, published on FD13. \u201cAt higher Mach numbers and angles of attack impacts are limited to tail.\u201d<\/p>\n<p>This process of working to the worst case scenario is a regular feature of NASA\u2019s safety regime, ensuring every possibility is understood, and that such situations have a factor of safety margin inbuilt.<\/p>\n<p>This was still deemed as no threat to safety, due to the time on re-entry (late in the landing phase) this could have potentially occurred, and the small probability of the thermal pane cracking via the high pressures of re-entry.<\/p>\n<p>As observed in several post landing photographs of the MMOD damage, the window did not crack, with only a small amount of thermal expansion of the damage around the hole caused by the MMOD.<\/p>\n<p>\u201cMMOD damage on Window 6 did not appear to propagate during reentry,\u201d confirmed associated notes. The window will be replaced \u2013 as is normal \u2013 during post flight processing, when Endeavour returns to her Orbiter Processing Facility (OPF-2).<\/p>\n<p>Endeavour will spend around five more days in California, before heading back to Florida on top of the SCA. A timeline and a flight path \u2013 which will involve several stopovers en route \u2013 is yet to be finalized, though the SCA\/Endeavour pairing is expected to depart for the cross country trip on Sunday.<\/p>\n<p>Click HERE to watch MaxQ\u2019s amazing STS-126 Review Video.<\/p>\n<p><em><em>L2 members<\/em><\/em><em><em>: All documentation \u2013 from which the above article has quoted snippets \u2013 is available in full in the related L2 sections, now over 4000 gbs in size.<\/em><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Engineers are working through post flight deservicing tasks on Endeavour at Dryden Flight Research Facility (DFRC)\/Edwards Air Force Base, with opening engineering images and notes pointing towards an extremely clean vehicle, following Sunday\u2019s landing in California. Images of Endeavour\u2019s Window 6 \u201cthermal pane\u201d \u2013 which suffered from a MMOD strike on orbit \u2013 show the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"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":[9240,7935],"class_list":["post-41246","post","type-post","status-publish","format-standard","hentry","category-news","tag-sts-126-mmod","tag-tps"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/41246"}],"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=41246"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/41246\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=41246"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=41246"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=41246"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}