As designed, the flight computer then recomputed a new ascent profile in real time to ensure Dragon’s entry into orbit for subsequent rendezvous and berthing with the ISS. This was achieved, and there was no effect on Dragon or the cargo resupply mission.
A bit defensive in tone but that's understandable.
Fort Lee, NJ, October 8, 2012 – ORBCOMM Inc. (Nasdaq: ORBC), a global satellite data communications company focused on two-way Machine-to-Machine (M2M) communications, today announced that the first prototype of its second generation of satellites (OG2) was launched on the Cargo Re-Supply Services (CRS-1) mission aboard the SpaceX Falcon 9 launch vehicle from Cape Canaveral, FL, on October 7, 2012 at 8:35 pm EST. The OG2 prototype satellite, flying as a secondary payload on this mission, was separated from the Falcon 9 launch vehicle at approximately 9:00 pm EST. However, due to an anomaly on one of the Falcon 9’s first stage engines, the rocket did not comply with a pre-planned International Space Station (ISS) safety gate to allow it to execute the second burn. For this reason, the OG2 prototype satellite was deployed into an orbit that was lower than intended. ORBCOMM and Sierra Nevada Corporation engineers have been in contact with the satellite and are working to determine if and the extent to which the orbit can be raised to an operational orbit using the satellite’s on-board propulsion system.
Only one question, why deploy if it was not in the " pre-planned International Space Station (ISS) safety gate".. why detach it from the stage.. ?
Approximately one minute and 19 seconds into last night's launch, the Falcon 9 rocket detected an anomaly on one first stage engine. Initial data suggests that one of the rocket's nine Merlin engines, Engine 1, lost pressure suddenly and an engine shutdown command was issued immediately. We know the engine did not explode, because we continued to receive data from it. Our review indicates that the fairing that protects the engine from aerodynamic loads ruptured due to the engine pressure release, and that none of Falcon 9's other eight engines were impacted by this event.
Approximately one minute and 19 seconds into last night's launch, the Falcon 9 rocket detected an anomaly on one first stage engine. Initial data suggests that one of the rocket's nine Merlin engines, Engine 1, lost pressure suddenly and an engine shutdown command was issued. We know the engine did not explode, because we continued to receive data from it. Panels designed to relieve pressure within the engine bay were ejected to protect the stage and other engines. Our review of flight data indicates that neither the rocket stage nor any of the other eight engines were negatively affected by this event.
...Pray that they do not alter it further.
It seems SpaceX has altered their statement from last night:Quote from: http://spaceref.com/news/viewpr.html?pid=38825Our review indicates that the fairing that protects the engine from aerodynamic loads ruptured due to the engine pressure releaseQuote from: http://www.spacex.com/press.php?page=20121008. Panels designed to relieve pressure within the engine bay were ejected to protect the stage and other engines.
Our review indicates that the fairing that protects the engine from aerodynamic loads ruptured due to the engine pressure release
. Panels designed to relieve pressure within the engine bay were ejected to protect the stage and other engines.
It seems SpaceX has altered their statement from last night:
Article on the latest. Held as long as I could to let things settle and get a better picture of status.http://www.nasaspaceflight.com/2012/10/dragon-iss-spacex-review-falcon-9-ascent-issues/
Arrival at the space station is scheduled for Flight Day 3, on October 11, via a Radial Bar Approach manuever.
I hear that the next Dragon burn is coming up soon - within the hour.
Perhaps it's time to change the title thread and lost the "ATTEMPT 1" ?
