![\"Z587\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/05\/Z587.jpg\")
The location of the leak would have likely been in or around one of the helium tanks known as Composite Overwrap Pressure Vessels (COPV) \u2013 a vital element for the pressurization needs of the vehicle.<\/p>\nSpaceX\u2019s Falcon 9 v1.1 launch of six ORBCOMM OG-2 satellites has seen its launch date tweaked to No Earlier Than (NET) launch date to June 15, pending its Static Fire test on Friday. The slight delay is understood to be related to a re-test requirement on the satellites. Meanwhile, Orbital\u2019s launch of the Antares rocket with the CRS-2\/ORB-2 Cygnus \u2013 set to ride to the International Space Station (ISS) \u2013 was pushed back to a NET July 1 target.<\/p>\n
SpaceX Falcon 9 v1.1 Launch:<\/p>\n
The next launch of SpaceX\u2019s Falcon 9 v1.1 was recently delayed after a problem occurred during the required Static Fire test early in May.<\/p>\n
While the specifics of the problem haven\u2019t been released, SpaceX did note the issue related to a helium leak inside the first stage of the rocket.<\/p>\n
The location of the leak would have likely been in or around one of the helium tanks known as Composite Overwrap Pressure Vessels (COPV) \u2013 a vital element for the pressurization needs of the vehicle.<\/p>\n
With the problem noted during the fuelling of the rocket, controllers acted quickly to safe the vehicle via a scrub of the Static Fire, ahead of detanking operations.<\/p>\n
Lowered off her Space Launch Complex -40 (SLC-40) launch pad at Cape Canaveral, the Falcon 9 was rolled back to her hanger for borescope inspections and unspecified repairs.<\/p>\n
It is understood those repairs have since been completed, with the majority of the recent effort relating to reviewing the root cause of the leak, in order to avoid a repeat situation during the next Static Fire or indeed the launch itself.<\/p>\n
(adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
The launch date was reset several times, mainly to find an optimum new target for the mission, with SpaceX and the Eastern Range settling on June 12.<\/p>\n
In order to meet that date, the plan revolved around a Static Fire test on Monday. However, that was postponed a few days ago when source information noted the six spacecraft \u2013 that are set to enjoy a ride to space on the Falcon 9 \u2013 require an unspecified re-test procedure.<\/p>\n
![\"Z7\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/03\/Z7.jpg\")
While SpaceX could opt to conduct the Static Fire with or without the payload atop of the vehicle, the realigned plan calls for the Static Fire to take place on Thursday, likely as an integrated stack.<\/p>\n
UPDATE: Static Fire moved to Friday afternoon local time due to weather requirements \u2013 likely impacting rollout operations.<\/p>\n
A large window is usually available for these tests \u2013 which are also called \u201cHot Fires\u201d \u2013 given the test culminates in the firing of the nine Merlin 1D engines for a few seconds while the rocket is held down at the pad.<\/p>\n
The latest Static Fire date remains preliminary, as does the launch date target, which has now moved to June 15, with a window ranging from 20:00 to 20:53 local time. A back-up date of June 16 is also noted, with a window that stretches from 19:38 to 20:31 local.<\/p>\n
*Click here for more SpaceX News Articles*<\/p>\n
SpaceX is yet to respond to questions confirming these latest launch targets, although they are now published in KSC\/Cape Status information (L2). It is likely the company and customer will release a firm schedule closer to the time of launch, as is usually prudent based on many factors.<\/p>\n
![\"Z9\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/05\/Z91.jpg\")
Those factors include negotiations with the Eastern Range, who have to approve the realigned launch schedule before SpaceX can set the actual launch date. The Eastern Range is currently working a near-term maintenance period, which could further impact the launch date.<\/p>\n
UPDATE: ORBCOMM confirmed the issue was with their satellites via a release on their website late on Tuesday.<\/p>\n
\u201cDuring final integration on one of the OG2 spacecraft, we encountered a minor issue resulting in a few extra days of delay to perform precautionary steps to ensure there are no operational concerns with the satellite,\u201d noted the company.<\/p>\n
\u201cWe intend to re-encapsulate the satellites this evening (Tuesday).<\/p>\n
Orbital Antares\/Cygnus ORB-2\/CRS-2:<\/p>\n
Orbital\u2019s next launch of their Antares rocket is tasked with lofting the next Cygnus spacecraft on a resupply run to the International Space Station (ISS).<\/p>\n<\/p>\n
The Commercial Resupply Services (CRS) mission, also known as ORB-2, was enjoying a smooth flow until a failure occurred thousands of miles from the Wallops launch sites.<\/p>\n
The issue related to one of the AJ-26 engines \u2013 set to launch with a future Antares rocket failing \u2013 failing during a test at the Stennis Space Center.<\/p>\n
The Antares launch vehicle utilizes the Aerojet Rocketdyne produced AJ-26 \u2013 a rebuilt version of Soviet NK-33 \u2013 for first stage ascent, an engine that has been very reliable during Antares early career.<\/p>\n
![\"Z7\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/06\/Z72.jpg\")
Testing of the engines at Stennis is a major requirement to ensure the units are in full working order prior to being integrated with the launch vehicle. The AJ-26\u2019s are tested at the E-1 Test Stand, in one its three cells.<\/p>\n
On May 22, L2 information noted a large failure \u2013 cited as an explosion \u2013 of the AJ-26 engine undergoing a test fire \u2013 mid-way through its burn. Orbital and Aerojet confirmed the failure, without providing specifics, although source information notes the engine and the test stage were heavily damaged.<\/p>\n
No further information has been provided by either NASA Stennis, Orbital or Aeroject Rocketdyne, with the latter confirming to NASASpaceFlight.com on Monday that they will only provide an update at a later date, due to an ongoing investigation into the failure.<\/p>\n
![\"Z38-350x225\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2013\/09\/Z38-350x225.jpg\")
What is known is the failure has resulted in a delay to the next Antares mission, due to the commonality of the engines both set for flight and undergoing testing.<\/p>\n
It was hoped a new launch date would place Antares with a ride uphill on June 20. However, this was soon shown to be optimistic, as Orbital released a new NET date of July 1 \u2013 which is also very preliminary at this time.<\/p>\n
\u201cOrbital has updated its Antares launch schedule for the Orb-2 mission to a date no earlier than (NET) July 1, 2014. The new launch schedule reflects the timing of the investigation into the cause of an AJ26 engine failure that occurred in late May at NASA\u2019s Stennis Space Center during customary acceptance testing,\u201d noted Orbital this week.<\/p>\n
![\"Z3A\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/02\/Z3A.jpg\")
\u201cAll other elements of the Orb-2 mission are prepared to move forward, including the Cygnus spacecraft, which is fueled and, except for late-load cargo, is packed with its manifest of ISS cargo.\u201d<\/p>\n
The engine that failed during testing wasn\u2019t set to fly until next year, on a future CRS mission. Orbital\u2019s release confirmed the investigation into the failure is ongoing.<\/p>\n
\u201cThe investigation into the failure is being led by the Antares main stage propulsion supplier, Aerojet Rocketdyne, with Orbital and NASA engineers also supporting the effort,\u201d added the statement.<\/p>\n
\u201cOnce the investigation team reaches the point in their process that they can clear Antares to launch the Orb-2 mission, a targeted launch date will be established. For now, NET July 1 is simply a planning date.\u201d<\/p>\n
(Images: via L2\u2032s Cygnus Section, containing presentations, videos, a vast set of unreleased hi-res images from Cygnus\u2019 missions, interactive high level updates and more. Other images via Jacques van Oene\/Spacepatches.nl, SpaceX Orbital and NASA).<\/p>\n
(Click here: http:\/\/www.nasaspaceflight.com\/l2\/ \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":"
SpaceX\u2019s Falcon 9 v1.1 launch of six ORBCOMM OG-2 satellites has seen its launch date tweaked to No Earlier Than (NET) launch date to June 15, pending its Static Fire test on Friday. The slight delay is understood to be related to a re-test requirement on the satellites. Meanwhile, Orbital\u2019s launch of the Antares rocket […]<\/p>\n","protected":false},"author":1,"featured_media":29992,"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":[9066,1871,1695,639,479,233,3842,7577,316,4255],"class_list":["post-39568","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-aj-26","tag-antares","tag-cape-canaveral","tag-cygnus","tag-falcon-9","tag-iss","tag-orbcomm","tag-orbital","tag-spacex","tag-wallops"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/39568"}],"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=39568"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/39568\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/29992"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=39568"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=39568"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=39568"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}