{"id":42111,"date":"2006-03-26T19:15:10","date_gmt":"2006-03-26T11:15:10","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/spacex-come-hell-or-high-water\/"},"modified":"2006-03-26T19:15:10","modified_gmt":"2006-03-26T11:15:10","slug":"spacex-come-hell-or-high-water","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/spacex-come-hell-or-high-water\/","title":{"rendered":"SpaceX: Come Hell or High Water"},"content":{"rendered":"<p>The loss of the maiden Falcon 1 launch on Friday may complicate both the legal and logistical picture, but CEO Elon Musk still proclaims \u201cCome hell or high water, we are going to make this work\u201d.<\/p>\n<p>A formal US Government-led anomaly investigation will be conducted in partnership with SpaceX, while the failure of Falcon 1 is likely to have an impact on SpaceX\u2019s anti-trust suit against Lockheed Martin and Boeing.<\/p>\n<p>The loss of the Falcon I maiden launch on Friday was apparently due to a fuel leak fire around the top of the main engine that cut into the first stage helium pneumatic system.<\/p>\n<p>THE FAILURE<\/p>\n<p>SpaceX\u2019s initial analysis indicates that there was a fuel leak just above the main engine, which caused a highly visible fire.  The fire cut into the first stage helium pneumatic system, causing a decrease of pneumatic pressure at T+25s. <\/p>\n<p>\u2018Once the pneumatic pressure decreased below a critical value, the spring return safety function of the pre-valves forced them to close, shutting down the the main engine at T+29s,\u2019 Elon Musk stated in a statement about the incident.<\/p>\n<p>\u2018The good news is that all vehicle systems, including the main engine, thrust vector control, structures, avionics, software, guidance algorithm, etc. were picture perfect.  Falcon\u2019s trajectory was within 0.2 degrees of nominal during powered flight,\u2019 wrote Musk.  \u2018Falcon was executing perfectly on all fronts until fire impaired the first stage pneumatic system.<\/p>\n<p>\u2018I am very encouraged and grateful that our launch customers took the time to call and express their support of SpaceX when their reaction could easily have been the opposite.  We will stand by them as they have stood by us.\u2019<\/p>\n<p>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>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>SpaceX launch tickets<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>Thousands watched and listened to the launch attempt live via online web-cast, with thousands more downloading the recorded flight footage that NASASpaceFlight.com obtained [see our FTP section, free membership required].  Hundreds followed and discussed live coverage in the NASASpaceFlight.com forums as it happened [link], generating over 16,000 views to a single thread within a few hours.<\/p>\n<p>(Frame taken from the video \u2013 showing the engine let go)<\/p>\n<p>This was the first Falcon launch attempt which used a thermal blanket on the first stage tank in an attempt to mitigate LOX boil-off.  The thin cryogenic blanket was attached to the tank with velcro, and was to be ripped off on liftoff by a lanyard attached to the launch platform.  There was much speculation among the webcast audience that the blanket, which in the video clearly failed to fully detach upon liftoff, may have contributed to the failure.<\/p>\n<p>Elon Musk yesterday dismissed concerns that the blanket had interfered with the rockets operation, stating that from the initial analysis it did not appear that the insulation played a negative role.<\/p>\n<p>\u2018Our plan at this point is to analyze data and debris to be certain that the above preliminary analysis is correct and then isolate and address all possible causes for the fuel leak,\u2019 stated Musk, \u2018In addition, we will do another ground up systems review of the entire vehicle to flush out any other potential issues.\u2019 <\/p>\n<p>He also stated that there would be a formal US Government-led investigation performs in cooperating with SpaceX to establish an official explanation.<\/p>\n<p>THE NEXT ATTEMPT<\/p>\n<p>\u2018I cannot predict exactly when the next flight will take place, as that depends on the findings of this investigation and ensuring that our next customer is comfortable that all reasonable steps have been taken to ensure reliability,\u2019 stated Musk, \u2018However, I would hope that the next launch occurs in less than six months.\u2019<\/p>\n<p>A return to flight within six months is an ambitious goal.  Even before the accident, the second launch of the Falcon 1 had been expected no sooner than three to six months, and the failure will undoubtedly complicate already delicate matters at the Vandenberg launch site.<\/p>\n<p>SpaceX had intended to make their maiden launch from the Complex 3 West launch site at Vandenberg last summer, with the Navy\/Air Force TacSat-1 payload. <\/p>\n<p>However, a long-delayed Titan 4 launch on the same range, combined with concerns from Lockheed Martin as they resumed use of the neighboring Complex 3 East launch site, led to frustrations and delays.  Eventually SpaceX made the decision to make the maiden launch from Kwajalein with the Air Force Academy\u2019s FalconSat-2 payload.<\/p>\n<p>SpaceX had hopes that a successful Kwajalein launch would clear the air of any remaining friction at Vandenberg.  \u2018I think the concerns that the 30th Space Wing have about us launching from 3 West will be resolved after we have a successful launch from Kwajalein,\u2019 said SpaceX VP of Business Development Gwynne Shotwell just hours before the Falcon 1 failure.  How the failure will impact operations at Vandenberg now remains to be seen.<\/p>\n<p>Regardless of launch site and vehicle reliability issues, the second launch attempt will have an unavoidable delay from the payload customers themselves.  When the TacSat-1 launch was re-ordered last fall behind FalconSat-2, the payload was put in storage and the TacSat-1 team dispersed to other projects.  SpaceX anticipated that re-assembling the customer\u2019s team would take a few months even before the Falcon 1 failure.<\/p>\n<p>EYES FORWARD<\/p>\n<p>SpaceX\u2019s third customer is the Malaysian government for their 2.5 meter resolution imaging satellite, RazakSat.  The launch is planned for February of 2007 from Kwajalein, pushed back from the original schedule by the Malaysians themselves, who decided to make use of the excess capacity on their flight by developing a secondary payload adapter for the Falcon 1.<\/p>\n<p>So, in addition to their primary RazakSat payload, they are going to fly some university cube sats, and other small academic payloads as well.  As explained by SpaceX\u2019s Gwynne Shotwell on Friday, \u2018The Malaysians have done a really nice thing for the tiny satellite community, and that is they have built a secondary payload adapter which fits on a Falcon.\u2019<\/p>\n<p>The larger question is how the Falcon 1 setback will effect the first launch of the more ambitious Falcon 9, expected in mid-2007.  On the press call before the launch Friday, the Falcon 9 was described as currently being in active development with \u2018hardware on the floor\u2019. The first Falcon 9 main tank was anticipated to be friction-stir welded together in the next several weeks.<\/p>\n<p>SpaceX provided NASA Space Flight with some new details on the Falcon 9 and a new 1C variant of the Merlin engine currently under development.  The Falcon 9 will be using a new regeneratively cooled version of the Merlin engine.  Both the Merlin 1B engine, and a successor regenerative 1C engine are now in development.  The set of 1B engines currently being built will only be used for stage firing tests of the Falcon 9.  The 1C engine, also now under development, will eventually power the first production Falcon 9 vehicles.<\/p>\n<p>The regenerative versions of the Merlin engines have been under development since last year in response to reliability concerns about the ablative nozzle of the existing Merlin 1A engine.  It does not appear that the ablative nozzle was a factor in Friday\u2019s launch.<\/p>\n<p>LAWSUIT TAKES A HIT<br \/>\nThe failure to launch will very likely have a direct impact on SpaceX\u2019s anti-trust suit against Lockheed Martin and Boeing.<\/p>\n<p>Two weeks ago, the Space Exploration Company\u2019s anti-trust legal case against Lockheed Martin and Boeing was reopened with the filing of a renewed set of claims by SpaceX.  A timeline has now been released that anticipates a new hearing in mid-May.<\/p>\n<p>All claims in the case were initially dismissed in February, when Justice Florence-Marie Cooper concluded that SpaceX \u2018is not yet ready to compete with the Defendants in the EELV market. Because it lacks such readiness, its speculative claims regarding future harm are not ripe.\u2019  It seems certain that the unsuccessful launch will do nothing to dispel this impression.<\/p>\n<p>The dismissal ruling in February permitted SpaceX 20 days to file an amended complaint to reopen the case.  The new claims filing occurred two weeks ago.  However, at the time of the dismissal, Justice Cooper stated that she felt an amended complaint would be unlikely to \u2018overcome the constitutional deficiencies that plague its claims\u2019.<\/p>\n<p>Last week Justice Cooper outlined a timeline for the case to proceed:<\/p>\n<p>April 6 \u2013 Lockheed and Boeing deadline to file a response to SpaceX\u2019s second amended complaint (almost certainly with a renewed motion to dismiss)<\/p>\n<p>April 27 \u2013 SpaceX deadline to file a response to the Defendant\u2019s response.<\/p>\n<p>May 8th \u2013 Lockheed and Boeing final filing deadline for response before hearing<\/p>\n<p>May 15th, 10am \u2013 in-person oral arguments hearing, assuming Lockheed\/Boeing move to dismiss.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The loss of the maiden Falcon 1 launch on Friday may complicate both the legal and logistical picture, but CEO Elon Musk still proclaims \u201cCome hell or high water, we are going to make this work\u201d. A formal US Government-led anomaly investigation will be conducted in partnership with SpaceX, while the failure of Falcon 1 [&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":[316],"class_list":["post-42111","post","type-post","status-publish","format-standard","hentry","category-news","tag-spacex"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/42111"}],"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=42111"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/42111\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=42111"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=42111"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=42111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}