{"id":39995,"date":"2012-10-20T00:54:51","date_gmt":"2012-10-19T16:54:51","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/dragon-enjoying-iss-stay-despite-minor-issues-falcon-9-investigation-begins\/"},"modified":"2012-10-20T00:54:51","modified_gmt":"2012-10-19T16:54:51","slug":"dragon-enjoying-iss-stay-despite-minor-issues-falcon-9-investigation-begins","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/dragon-enjoying-iss-stay-despite-minor-issues-falcon-9-investigation-begins\/","title":{"rendered":"Dragon enjoying ISS stay, despite minor issues \u2013 Falcon 9 investigation begins"},"content":{"rendered":"<p>SpaceX\u2019s Dragon spacecraft is behaving well \u2013 bar a couple of minor issues \u2013 during its berthed phase of the CRS-1 (SpX-1) mission, as it closes in on its departure at the end of the month. The unberthing will be conducted by the Space Station Remote Manipulator System (SSRMS), which translated away from the Dragon to allow for an inspection this week.<\/p>\n<p>Dragon CRS-1\/SpX-1:<\/p>\n<p>The first Commercial Resupply Services (CRS) mission to the International Space Station (ISS) is achieving its primary objectives, despite Dragon\u2019s eventful ride uphill.<\/p>\n<p>Its noisy partner, the Falcon 9 launch vehicle, lost an engine during first stage ascent, while the second stage failed a propellant mass check at SECO-1, resulting in its secondary payload passenger \u2013 an Orbcomm satellite \u2013 being left in an unworkable orbit, prior to deorbiting.<\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" class=\"alignleft size-full wp-image-26502\" title=\"Z3\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/10\/Z37.jpg\" alt=\"\" width=\"349\" height=\"267\">The first stage issue related to Engine 1, one of nine Merlin 1Cs, after \u2013 it is understood \u2013 the fuel dome above the nozzle ruptured. The engine did not explode, but did cause the fairing that protects the engine from aerodynamic loads to rupture and fall away from the vehicle due to the engine pressure release.<\/p>\n<p>It is not clear if any specific details into the root cause of the failure will ever be revealed to the public, due to the proprietary nature of SpaceX\u2019s hardware. However, NASA and SpaceX are currently reviewing the incident via a joint CRS-1 Post-Flight Investigation Board.<\/p>\n<p>It has been noted the board are carrying out a comprehensive examination and analysis of all launch data, with the goal of understanding what happened and how to correct it prior to future flights.<\/p>\n<p>According to L2 sources, the board has dispositioned systems and components that data show were not part of the anomaly, typical for the early steps in a failure analysis. The next step will be to review the build records of the remaining components that could be suspect.<\/p>\n<h4 class=\"widget-title penci-border-arrow\">See Also<\/h4>\n<ul>\n<li>LIVE SpaceX Mission Section<\/li>\n<li>     (adsbygoogle = window.adsbygoogle <\/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>Meanwhile, parallel efforts are reviewing past test data of engines and stages at the McGregor Rocket Development Facility in Texas to look for similar data signatures to that observed during Falcon 9\u2019s ascent. The extensive test history of Merlin engines, even where there was a problem during testing, lends an empirical base to the investigation.<\/p>\n<p>The next flight, CRS-2 (SpX-2) is currently scheduled to launch in January, 2013 \u2013 although that date will be dependant on the outcome of the board\u2019s findings, not least any potential corrective actions required on the next Falcon 9 vehicle.<\/p>\n<p>CRS-2 will debut the use of Dragon\u2019s Trunk section, capable of delivering unpressurized cargo, prior to the payload being removed by the ISS\u2019 robotic assets after berthing.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-26503\" title=\"Z10\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/10\/Z107.jpg\" alt=\"\" width=\"347\" height=\"245\">Per L2 manifest documentation, this mission will carry two Heat Rejection Subsystem Grapple Fixture (HRSGF) \u2013 Grapple Bars in Dragon\u2019s Trunk, for installation on the Mobile Base System (MBS) Payload and Orbit Replaceable Unit Accommodation (POA).<\/p>\n<p>No downmass has yet been allocated for Dragon\u2019s Trunk for CRS-2 or CRS-3, the latter set to carry three sets of science payloads alongside its compliment of primary upmass that will ride \u2013 as per usual \u2013 in the Dragon\u2019s pressurized section.<\/p>\n<p>In preparation for the use of Dragon\u2019s Trunk, the COTS 2+ mission saw the Canadian robot Dextre (SPDM) ride on the SSRMS to meet with Dragon\u2019s Trunk section, allowing for an inspection and the evaluation of clearances ahead of robotic operations proper during CRS-2.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-26508\" title=\"Z563\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/10\/Z563.jpg\" alt=\"\" width=\"350\" height=\"248\">For CRS-1, ISS managers decided not to repeat the operation with Dextre, instead allowing for the SSRMS to reposition for an inspection of its LEE (Latching End Effector) that grabbed hold of Dragon during its arrival at the orbital outpost. This inspection was completed this week.<\/p>\n<p>\u201cMobile Transporter (MT) Translation and Space Station Remote Manipulator System (SSRMS) Latching End Effector (LEE) Inspection: \u201cThe MT moved from worksite 2 to worksite 5, which is one of the home positions of the MT,\u201d per notes on L2\u2019s rolling ISS update section.<\/p>\n<p>\u201cFollowing the MT translate, the SSRMS (based on the Node 2 PDGF) positioned to support a LEE inspection. LEE inspection completed, and photos are under review.\u201d<\/p>\n<p>The MT will reposition to worksite 2 ahead of grappling the CRS-1 Dragon for its unberthing at the end of the month, marking the end of the private spacecraft\u2019s time at the ISS.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-26505\" title=\"Z5\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/10\/Z56.jpg\" alt=\"\" width=\"349\" height=\"217\">As with the COTS 2+ Dragon, the period of joint operations have progressed very smoothly, beginning with the opening of the Dragon hatch, prior to the removal of Dragon\u2019s payloads.<\/p>\n<p>\u201cSpaceX (SpX)-1 Dragon Cargo Operations: ISS Commander (CDR) Williams and Flight Engineer (FE)-6 Hoshide worked ahead of the timeline and executed all ingress operations originally planned,\u201d noted L2\u2019s CRS-1 Dragon Update Section.<\/p>\n<p>\u201cWilliams and Hoshide began Dragon cargo transfer operations, which included unpacking of double cold bags containing critical science such as NanoRacks and Resist Tubule. After unpack, the double cold bags and ice bricks were temporarily stowed on the ISS to allow condensation to evaporate.<\/p>\n<p>Click here for other Dragon News Articles:&nbsp;http:\/\/www.nasaspaceflight.com\/tag\/dragon\/<\/p>\n<p>\u201cWilliams then performed health checks and removed Dragon Glacier samples and transferred the samples to Microgravity Experiment Research Locker Incubator II (MERLIN) on ISS. The crew performed 100 percent of SpX-1 Dragon cargo unpacking and approximately 77 percent of packing for return (within the first day).\u201d<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-26504\" title=\"Z4\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/10\/Z410.jpg\" alt=\"\" width=\"350\" height=\"236\">During the initial berthed operations, Dragon sat patiently on Node 2, providing no real headaches for SpaceX and ISS controllers on the ground, bar one minor issue that was soon cleared.<\/p>\n<p>\u201cSpX-1 Vehicle Status: Onboard Dragon all systems are functioning nominally. The batteries are at a proper state of charge and the prop system is configured properly for ISS safety. Thermal Control System (TCS) is also functioning properly,\u201d added the L2 Status Notes.<\/p>\n<p>\u201cOverall, the SpX-1 Dragon is healthy. (However,) Dragon experienced a Single Event Effect (SEE) on the Trunk Remote Input\/Output (RIO) Unit String B as ISS passed over the South Atlantic Anomaly. The team power cycled and re-synched the RIO string and recovered the unit.\u201d<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-26509\" title=\"Z8\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2012\/10\/Z87.jpg\" alt=\"\" width=\"350\" height=\"228\">During this week, SpaceX carried out an evaluation into Dragon\u2019s capabilities related to the impact of removing ISS power from the spacecraft for up to a 12 hour period \u2013 an assessment based on Dragon being at the Station during an Stage EVA at the Station.<\/p>\n<p>After the evaluation, ground teams in Hawthorne, California (MCC-X) worked on troubleshooting the \u201cSpX Network Switch B\u201d which went down during the week.<\/p>\n<p>\u201cThere are two fully redundant Network Switches which are up and running nominally,\u201d added the notes. \u201cTeams will attempt a reboot of the switch and if that doesn\u2019t work, will reflash the switch from the flight computer.\u201d<\/p>\n<p>SpX ground specialists successfully executed a reboot of the Network Switch B, which recovered the Network Switch B without issue.<\/p>\n<p>The next operation will be for the SSRMS to regrapple Dragon ahead of its departure, currently expected on October 28.<\/p>\n<p>(Images: via L2\u2019s SpaceX Dragon Mission Special Section \u2013 Containing presentations, videos, images (Over 2,500MB in size), space industry member discussion and more. Now includes CRS-1 Image Dump, every single hi res photo taken from the ISS \u2013 several hundred images).<\/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>SpaceX\u2019s Dragon spacecraft is behaving well \u2013 bar a couple of minor issues \u2013 during its berthed phase of the CRS-1 (SpX-1) mission, as it closes in on its departure at the end of the month. The unberthing will be conducted by the Space Station Remote Manipulator System (SSRMS), which translated away from the Dragon [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":30332,"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":[2304,1395,479,233,316],"class_list":["post-39995","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-crs","tag-dragon","tag-falcon-9","tag-iss","tag-spacex"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/39995"}],"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=39995"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/39995\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/30332"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=39995"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=39995"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=39995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}