After Weeks of Delay, SpaceX Falcon Launches Communications Satellite Payload

After several weeks of delay, SpaceX has successfully launched from Cape Canaveral AsiaSat's communications satellite, AsiaSat 6. This launch was originally intended to occur on August 27. However, due to a failure of an experimental SpaceX rocket during a test flight, the launch was delayed. The experimental rocket apparently malfunctioned because of a sensor error. The company stated that the same error wasn’t likely to occur in its regular Falcon 9 rocket, but wanted to "triple-check" its systems to be certain. SpaceFlightInsider has a play-by-play on the launch process and more details on the communications satellites aboard. They note: [This] marked the fifth flight of the Falcon 9 in 2014. Since the company began using the booster, it had only been able to carry out about two launches annually of the rocket – until now. With the United States Air Force considering the rocket for use under the lucrative Evolved Expendable Launch Vehicle (EELV) program and NASA already utilizing it to deliver cargo (and potentially crew) to the International Space Station, the rocket has become a popular player in terms of launch services. The next mission that SpaceX should use the propulsive descent landing system on, is the launch of one of the firm’s Dragon spacecraft carrying out NASA’s Commercial Resupply Services 4 (SpX-4) mission – currently scheduled to take place on Sept. 19.

Comments

Re:Updating gman003's post

[Granular]

Apollo 13 should count, but not for what most people know about.

The second stage center engine shut down early due to a thrust chamber sensor reading low pressure. While this did not impact the orbital insertion (the remaining 4 engines fired for an additional 4 minutes to make up for it), the sensor reading that shutdown the engine may have been in error, and is still not understood. However, if this shutdown had not occurred, the vehicle would likely have been lost in just moments after when the shutdown occurred. The center engine was experiencing severe pogo osculations, resulting in the engine flexing the thrust frame up and down by 3 inches, 16 times each second—this motion would have resulted in disintegration of the rocket in short order. The thrust chamber sensor should have been unaffected by the pogo, so that is unlikely to be the cause of the reading that led to the shutdown. So it is possible that while one failure during launch almost destroyed Apollo 13, a second failure actually (temporarily at least) saved the mission.

See this article for more information.