![\"2014-08-26](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/08\/2014-08-26-22_57_02-chan9large.jpg-704%C3%97480-350x255.jpg\")
Following the removal and replacement of two valves on Tuesday morning, engineers confirmed the problem had been fixed, as they reported back to a Delta LRR during Tuesday.<\/p>\nSpaceX has delayed the launch of its latest Falcon 9 v1.1 rocket \u2013 tasked with lofting the ASIASAT-6 satellite into orbit \u2013 for one to two weeks. The call was made by CEO Elon Musk shortly after the rocket had been erected at her Space Launch Complex -40 (SLC-40) pad, with the rationale based on giving the team more time to evaluate any potential commonality with an incident involving a test vehicle.\n<\/p>\n
Falcon 9 Delay:<\/p>\n
Initially, no specific reasons was provided as to why the call was made, although engineers had been working on a helium leak throughout the past 24 hours or so, as noted during Monday\u2019s Launch Readiness Review (LRR) that classed this as an open item, per L2.<\/p>\n
Following the removal and replacement of two valves on Tuesday morning, engineers confirmed the problem had been fixed, as they reported back to a Delta LRR during Tuesday.<\/p>\n
This resulted in a go to proceed with the launch attempt \u2013 thus making the problem an unlikely reason for the delay.<\/p>\n
While the launch vehicle was being rolled out and erected at the pad, Mr. Musk is understood to have e-mailed the SpaceX team to postpone the launch, in order to \u201cgive the team more time to check everything\u201d ahead of the mission.<\/p>\n
\u201cFalcon 9 \/ AsiaSat-6 launch that was planned for 8\/27, 0050L-0405L, has been scrubbed per SpaceX,\u201d added KSC\/Cape Status. \u201cThere is no new launch date at this time and no reason given at this time.\u201d<\/p>\n
Several hours later, Mr. Musk noted the delay was due to potential commonality between the hardware on the Falcon 9 v1.1 and the F-9R Dev-1 test rocket that failed during her \u201chop\u201d at SpaceX\u2019s test facility in McGregor, Texas.<\/p>\n
While the evaluations into the test failure were also classed as the official reason behind the one day delay of the ASIASAT-6 mission \u2013 when the mission moved to Wednesday morning \u2013 sources suggest there was little to be concerned about between the test failure and the upcoming launch. It was also mooted that the launch date was expected to slip by a day, even before the F-9R Dev-1 had her issue.<\/p>\n
In explaining the details behind the problem that occurred with the F-9R Dev-1 (L2), sources stressed that any similar issue with the Falcon 9 v1.1 tasked with the ASIASAT-6 launch would not have resulted in the failure observed in Texas.<\/p>\n
![\"2014-08-26](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/08\/2014-08-26-22_56_18-Launch-of-SpaceX-Falcon-9s-10th-Flight-with-ORBCOMM-OG2-YouTube-350x246.jpg\")
In fact, the same issue would have resulted in the Falcon 9 v1.1 aborting and safing in-situ on the launch pad \u2013 or an avoidance of the engine issue via the sensor voting system, outvoting the bad sensor.<\/p>\n
The reason the former did not happen for the F-9R Dev-1 is because she does not lift off from a regular launch pad and thus does not have the hold down posts to stop the rocket from lifting off in an off-nominal condition.<\/p>\n
Yet despite reviewing the test vehicle incident, ahead of Friday\u2019s Static Fire \u2013 resulting a go to proceed, and again ahead of the Wednesday morning attempt, this was the reason for the delay being called.<\/p>\n
\u201cSpaceX has decided to postpone the flight of AsiaSat 6. We are not aware of any issue with Falcon 9, nor the interfaces with the Spacecraft, but have decided to review all potential failure modes and contingencies again. We expect to complete this process in one to two weeks,\u201d noted Mr. Musk.<\/p>\n
![\"2014-08-23](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/08\/2014-08-23-03_16_24-f9r-dev1-Google-Search-350x247.jpg\")
\u201cThe natural question is whether this is related to the test vehicle malfunction at our development facility in Texas last week. After a thorough review, we are confident that there is no direct link. Had the same blocked sensor port problem occurred with an operational Falcon 9, it would have been outvoted by several other sensors. That voting system was not present on the test vehicle.<\/p>\n
\u201cWhat we do want to triple-check is whether even highly improbable corner case scenarios have the optimal fault detection and recovery logic. This has already been reviewed by SpaceX and multiple outside agencies, so the most likely outcome is no change. If any changes are made, we will provide as much detail as is allowed under US law.\u201d<\/p>\n
While the loss of the F-9R Dev-1 was obviously regrettable, it was not unexpected.<\/p>\n
SpaceX made it clear, over a year ago, that the test vehicle at the heart of the company\u2019s fully reusable launch system aspirations was going to be pushed to her limits. As such, a failure was always going to be a distinct possibility.<\/p>\n
![\"2014-08-26](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/08\/2014-08-26-22_51_36-F9R-Dev1-moment-of-explosion-YouTube-350x254.jpg\")
Also, in typical SpaceX fashion, the demise of the F-9R Dev-1 still provided what is understood to be a first, specifically the first U.S. autonomous Range Safety event by a rocket, as the test vehicle capably ended her own life \u2013 despite not using the more extensive version of the Flight Termination System (FTS) that Falcon 9 v1.1\u2019s can utilize during launches out of Cape Canaveral and Vandenberg Air Force Base.<\/p>\n
Once clearance is provided to conduct the launch, the Falcon 9 v1.1 will aim to loft the ASIASAT-6 satellite into a Geostationary Transfer Orbit (GTO), utilizing the power of the upgraded Falcon 9 v1.1, with the first stage requiring all of its propellant to get the job done.<\/p>\n
As such, there won\u2019t be a propulsive landing attempt of the core on this mission, with the next first stage return attempt currently the CRS-4\/SpX-4 Dragon mission, potentially aiming for a landing on a barge in the Atlantic.<\/p>\n
![\"2014-07-28](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/07\/2014-07-28-11_06_02-asiasat-6-Google-Search-350x254.jpg\")
ASIASAT-6 \u2013 like her sister satellite \u2013 is based on the Space Systems\/Loral 1300 platform. The bird is designed to provide C-band coverage over Asia, Australasia, Central Asia and the Pacific islands.<\/p>\n
The bird also sports 28 high-powered C-band transponders, with a design life of 15 years.<\/p>\n
After being lofted into a Geostationary Transfer Orbit (GTO), she will be positioned at the 120 degrees East orbital slot, with a global beam and a regional beam to offer enhanced power and look angles for video distribution and broadband network services in the region.<\/p>\n
The launch follows on from last month\u2019s successful mission to loft the ASIASAT-8 satellite into orbit.<\/p>\n
(Images via SpaceX, NASA KSC and ASIASAT).<\/p>\n","protected":false},"excerpt":{"rendered":"
SpaceX has delayed the launch of its latest Falcon 9 v1.1 rocket \u2013 tasked with lofting the ASIASAT-6 satellite into orbit \u2013 for one to two weeks. The call was made by CEO Elon Musk shortly after the rocket had been erected at her Space Launch Complex -40 (SLC-40) pad, with the rationale based on […]<\/p>\n","protected":false},"author":1,"featured_media":30001,"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":[3172,479,316],"class_list":["post-39518","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-asiasat","tag-falcon-9","tag-spacex"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/39518"}],"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=39518"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/39518\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/30001"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=39518"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=39518"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=39518"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}