SpaceX has had a dramatic end to the week, with a successful Static Fire test of their Falcon 9 v1.1 rocket at Cape Canaveral, concluded just hours after the F-9R Dev-1 test rocket failed during testing in Texas. The test failure holds no impact to next week’s ASIASAT-6 mission, currently targeting Wednesday.
Falcon 9 Static Fire:
SpaceX is preparing to follow up the ASIASAT-8 success with the lofting of the sister satellite, ASIASAT-6.
A key processing milestone for the launch vehicle was the Static Fire test, a requirement that is used to ensure the pad’s fueling systems – and the rocket – function properly in a fully operational environment.
Numerous requirements have to be successfully proven via such a test, such as the engine ignition and shut down commands, which have to operate as designed, and that the Merlin 1D engines perform properly during start-up.
The flow towards the ignition of the nine engines appears to have proceeded without issue, with a short burst of the nine engines confirmed at 7:41pm Eastern, slightly ahead of the the predicted opening of what was a four hour long test window.
With the required engine and vehicle data collected, detanking operations followed, before the rocket will be lowered on to the Transporter Erector (TE) and rolled back to the hanger.
Once inside the barn, she will be mated with the satellite and fairing, both of which did not ride out to the pad for this test.
ASIASAT has confirmed the satellite is now encapsulated inside the Falcon 9 v1.1 fairing in the hanger.
Next up is a data review, which will be fed into the Launch Readiness Review (LRR) – a key meeting that will confirm the launch date.
The current projected launch date has held relatively firm on the schedule during this flow, only moving slightly to the right to what is now the August 27 target, within a launch window ranging from 00:50 to 04:05 Eastern.
ASIASAT-6 – like her sister satellite – 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.
Sporting 28 high-powered C-band transponders, with a design life of 15 years.
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.
F-9R Dev-1 Failure:
The successful Static Fire of the Falcon 9 v1.1 in Florida occurred just hours after the loss of the F-9R Dev-1 test vehicle in Texas.
The successor to the Grasshopper test vehicle, the F-9R Dev-1 vehicle was employed to demonstrate a more aggressive set of objectives, feeding directly into the ongoing efforts that will hopefully result in Falcon 9 first stages returning back to terra firma.
The F-9R Dev-1 resided with the Grasshopper at SpaceX’s McGregor Test Facility, and was a close match to the Falcon 9 v1.1 first stage dimensions.
The first sightings of this test vehicle were shown via photos taken by several local people from a public road in the vicinity of the test site – some of which were provided to L2 (along with videos) – at the time providing the first glimpse of the landing leg structures.
The legs were closely based on the hardware that SpaceX is now employing on their latest Falcon 9 missions – bar the two ASIASAT missions, due to performance requirements.
The F9-R Dev-1 vehicle enjoyed several hops into the Texas air, providing impressive controllability, while refining the use of fins for stability and the pinpoint soft landing on her four legs.
On Friday, the vehicle was lost.
“Three engine F9R Dev1 vehicle auto-terminated during test flight. No injuries or near injuries. Rockets are tricky…,” noted SpaceX CEO Elon Musk on Twitter.
The loss should not come as a major surprise, given SpaceX had already admitted they intended to push their test vehicles to the limits.
“So we’re 5-for-5 testing on this Grasshopper. But, but that means we’re not pushing hard enough. We’ve got to tunnel one of those vehicle into the ground by trying something really hard,” noted SpaceX President Gwynne Shotwell just over a year ago.
“So now our challenge to our test team is you’ve got to push hard enough that we’re going to see something happen. A spectacular video.”
On Friday, that became a reality, as amateur footage acquired by CBS showed the F-9R Dev-1 rising under the power of her three engines, before appearing to suffer from a loss of control, prior to the Flight Termination System (FTS) carrying out a controlled explosion, as it is designed to do.
“During the flight, an anomaly was detected in the vehicle and the flight termination system automatically terminated the mission,” noted SpaceX in a statement.
“With research and development projects, detecting vehicle anomalies during the testing is the purpose of the program. Today’s test was particularly complex, pushing the limits of the vehicle further than any previous test.
As is our practice, the company will be reviewing the flight record details to learn more about the performance of the vehicle prior to our next test. SpaceX will provide another update when the flight data has been fully analyzed.”
Sources have confirmed the reason for the failure was specific to the test vehicle only. No impacts to flight vehicles are expected.
Notably, limitations at the Texas site result in an AGL (Altitude above Ground Level) ceiling that is somewhat restrictive.
As a result, another test vehicle – the Falcon 9-R Dev -2 – will take up residency at Spaceport America in New Mexico, where the vehicle will be able to fly at much higher altitudes.
According to L2 sources, the Dev-2 has not yet been seen in residence at Spaceport America, although SpaceX workers were observed on site and working in an area that is expected to be utilized by the test rocket.
(Images: SpaceX, Twitter (links to accounts in the main coverage thread) – and L2)
(Click here: http://www.nasaspaceflight.com/l2/ – to view how you can access the best space flight content on the entire internet and directly support NASASpaceflight.com’s running costs)