{"id":40045,"date":"2012-08-15T22:59:38","date_gmt":"2012-08-15T14:59:38","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/nasa-safety-panel-now-satisfied-with-spacex-anomaly-resolution-team\/"},"modified":"2012-08-15T22:59:38","modified_gmt":"2012-08-15T14:59:38","slug":"nasa-safety-panel-now-satisfied-with-spacex-anomaly-resolution-team","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/nasa-safety-panel-now-satisfied-with-spacex-anomaly-resolution-team\/","title":{"rendered":"NASA safety panel now satisfied with SpaceX anomaly resolution team"},"content":{"rendered":"<p>NASA\u2019s Aerospace Safety Advisory Panel (ASAP) have gone on record to say they are satisfied with SpaceX\u2019s explanations, relating to their \u201cfast\u201d scrub turnaround for Falcon 9\u2019s May launch. After claiming they were initially concerned with the pace of the turnaround, the ASAP members were reassured&nbsp;via&nbsp;overviews&nbsp;provided to them by NASA and SpaceX\u2019s Mission Assurance manager.<\/p>\n<p>ASAP and SpaceX:<\/p>\n<p>This latest meeting of the ASAP was once again chaired by Vice Admiral Joseph W. Dyer, USN (Ret.), and held at the Kennedy Space Center (KSC) near to the end of last month. Their findings and recommendations were passed on to NASA administrator Charlie Bolden \u2013 for his consideration \u2013 on August 8.<\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" class=\"alignleft size-full wp-image-25671\" title=\"A1213\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/08\/A1213.jpg\" alt=\"\" width=\"349\" height=\"232\" srcset=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/08\/A1213.jpg 349w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/08\/A1213-263x175.jpg 263w\" sizes=\"(max-width: 349px) 100vw, 349px\">The VADM opened the meeting with praise for KSC Center Director, Robert Cabana, thanking him for \u201cshepherding\u201d his organization through \u201ca very challenging time\u201d, before adding KSC\u2019s progress during its&nbsp;transition \u201cis better than the Panel could have hoped for,\u201d thanks to the institution\u2019s leadership.<\/p>\n<p>The ASAP were an active force in the drive to end the life of the Space Shuttle fleet, and were meeting at KSC just as Endeavour is being&nbsp;put through the final preparations to leave her home base for a retirement in California, an event that will leave the famous spaceport&nbsp;with just one remaining orbiter for the first time in close to 30 years.<\/p>\n<p>The Panel also spent some of their energy over recent years urging caution with respect to the commercial space program, most notably on the commercial crew future that is tasked with returning&nbsp;a domestic ability for the United States to launch its own astronauts \u2013 a capability lost via the retirement of the Space Shuttle fleet.<\/p>\n<h4 class=\"widget-title penci-border-arrow\">See Also<\/h4>\n<ul>\n<li>SpaceX Forum Section<\/li>\n<li>L2 SpaceX Section<\/li>\n<li>L2&nbsp;ISS Section<\/li>\n<li>Click here to Join L2<\/li>\n<\/ul>\n<p>However, the panel members have softened their stance towards NASA\u2019s commercial partners recently, opting to praise SpaceX on their recent \u2013 and highly successful \u2013 C2+ mission, albeit with the inclusion of a few side notes of caution, with the previous meeting at the Marshall Space Flight Center (MSFC) citing \u201ca few successes\u201d should not detract from pushing commercial companies through NASA\u2019s strict certification requirements for upcoming crewed missions.<\/p>\n<p>Notes from the latest meeting also included special attention for SpaceX, this time examining the short scrub turnaround between a pad abort for Falcon 9\u2019s opening attempt to launch Dragon on its debut mission to the International Space Station (ISS), and the successful launch that&nbsp;followed just a few days later.<\/p>\n<p>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 updates<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 educational resources<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><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-25666\" title=\"Z427\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/08\/Z427.jpg\" alt=\"\" width=\"348\" height=\"241\">The opening attempt was scrubbed \u2013 just seconds prior to launch \u2013 due to the breach of redline limits by Engine 5\u2019s chamber pressure readings on the Falcon 9, causing the flight computers to abort the launch. Due to the near-instant launch window for this mission, a scrub was called for the day.<\/p>\n<p>A similar, but not identical, issue was observed with the first flight of the Falcon 9 \u2013 an issue that was resolved ahead of launch due to an extended launch window for that opportunity.<\/p>\n<p>After the Falcon 9 was detanked, engineers arrived at the pad to inspect the engine \u2013 specifically the chamber hardware \u2013 and soon found an obvious problem with a check valve on the engine\u2019s turbopump.<\/p>\n<p>\u201cEngine pressure anomaly traced to turbopump valve,\u201d noted SpaceX CEO and Chief Designer Elon Musk at the time. \u201cReplacing on engine 5 and verifying no common mode.\u201d<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-25667\" title=\"Z631\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/08\/Z631.jpg\" alt=\"\" width=\"351\" height=\"267\">With the vehicle rolled back to the hanger for repairs, SpaceX engineers fixed the hardware on the Saturday night and reviewed the data the following day, allowing for the Falcon 9 to be rolled back out to the pad and returned to a launch stance by the Monday.<\/p>\n<p>The Falcon 9 was successfully launched at 3:44am Eastern on the Tuesday morning.<\/p>\n<p>While a large amount of data is restricted, the panel felt they could discuss the check valve issue, due to the root cause being released into the public domain by SpaceX. To that end, the panel heard from SpaceX\u2019s Director of Mission Assurance, Scott Henderson and were briefed by an internal&nbsp;NASA report on the scrub turnaround procedures.<\/p>\n<p>\u201cVADM Dyer noted that there were some constraints on what information could be disseminated at a public meeting, based on International Traffic in Arms Regulation (ITAR) restrictions as well as SpaceX proprietary data,\u201d stated the ASAP notes. \u201c(However,) the Hon. Mr. (Claude) Bolton stated that everyone is aware that there was an automatic shutdown on the SpaceX launch in May.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-25668\" title=\"Z4\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/08\/Z410.jpg\" alt=\"\" width=\"351\" height=\"268\">\u201cThe problem was found to be due to a check valve, (and) the process used to return to a launch position was described during the briefing, which was made by Mr. Scott Henderson, Director of Mission Assurance for SpaceX.\u201d<\/p>\n<p>The subject was discussed by the ASAP due to an apparent concern with the pace of the turnaround, with the notes adding \u201cVADM Dyer observed that the turnaround was so fast that there was initially some concern on the Panel\u2019s part that sufficient work may not have been done to identify root cause.\u201d<\/p>\n<p>However, after hearing from Mr Henderson \u2013 and verifying NASA\u2019s own report into the anomaly resolution by the SpaceX engineers \u2013 the ASAP saw no items of concern.<\/p>\n<p>\u201cThe ASAP understood from NASA\u2019s report that the process was effective and efficient, turning around for a second successful launch attempt in three days; it was thorough, robust, fast, and transparent to NASA,\u201d the meeting notes added.<\/p>\n<p>Click here for NSF\u2019s&nbsp;SpaceX News Articles (70): http:\/\/www.nasaspaceflight.com\/tag\/spacex\/<\/p>\n<p>Due to the proprietary nature of SpaceX\u2019s vehicle, no information has been released on how Engine 5 performed during ascent \u2013 as much as the vehicle clearly performed its required tasks. However, the ASAP went on record to say they are satisfied with the information they have to hand.<\/p>\n<p>\u201cAfter further review, the ASAP was satisfied with how this class D-equivalent mission was treated.\u201d<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-25670\" title=\"Z313\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/08\/Z313.jpg\" alt=\"\" width=\"349\" height=\"221\">Given the ASAP hold a large amount of influence&nbsp;at the Agency and political level, their recent positivity over SpaceX\u2019s practises is important, and timely \u2013 as NASA close in on providing final approval for SpaceX to transition from their Commercial Orbital Transportation Services (COTS) obligations \u2013 of which the C2+ mission passed the final objectives \u2013 to their Commercial Resupply Services (CRS) missions to the ISS.<\/p>\n<p>Pending that expected approval via NASA, L2 (LINK) information shows SpaceX have an opportunity to launch the first two CRS missions before the end of this year.<\/p>\n<p>Current information places the CRS-1 (SpX-1) mission with a NET (No Earlier Than) launch date of October 6, to be followed by the CRS-2 (SpX-2) mission, launching NET December 16. Manifested payloads up to at least CRS-3 (SpX-3) are also listed on documentation (L2 LINK).<\/p>\n<p>(Images: via SpaceX, NASA, and L2\u2019s SpaceX Dragon C2+ Mission Special Section \u2013 Containing presentations, videos, images (800mb of unreleased hi res images from the mission)&nbsp;and more).&nbsp;<\/p>\n<p>(Click here: http:\/\/www.nasaspaceflight.com\/l2\/&nbsp;\u2013 to view how you can support NSF and access the best space flight content on the entire internet).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>NASA\u2019s Aerospace Safety Advisory Panel (ASAP) have gone on record to say they are satisfied with SpaceX\u2019s explanations, relating to their \u201cfast\u201d scrub turnaround for Falcon 9\u2019s May launch. After claiming they were initially concerned with the pace of the turnaround, the ASAP members were reassured&nbsp;via&nbsp;overviews&nbsp;provided to them by NASA and SpaceX\u2019s Mission Assurance manager. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":29627,"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":[8862,2304,1395,479,316],"class_list":["post-40045","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-asap","tag-crs","tag-dragon","tag-falcon-9","tag-spacex"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40045"}],"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=40045"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40045\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/29627"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40045"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40045"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}