SpaceX reporting tiny explosion in Dragon ISS launch [UPDATED with statement]
This morning we’re hearing official word from SpaceX that their Dragon capsule launch to the International Space Station didn’t go as perfect because it seemed inside the live feed. What you’re about to work out is a little bit an explosion, some debris flying from the craft, and a burst of fireside. For sure because the fire is surrounded by loads of fire from the rockets surrounding it, it will become just a little difficult to detect – great thing the video is in slow motion and you may see all of it in all of its glorious detail.
The situation we’re seeing here’s what SpaceX calls an “anomaly”, assuring us that the ship is indeed in orbit across the Earth now and that the explosion wasn’t something they were alarmed about because it happened nor now. What you will see that looks a load more serious than SpaceX is making it out to be, that being a burst of flame and a suite of debris falling from the rocket because it continues on its course.
UPDATE: SpaceX has released the next statement at the situation, assuring the general public that the mission will continue as planned, and that there wasn’t actually an explosion in any respect – all is easily!
The Dragon spacecraft is on its solution to the International Space Station this morning and is performing nominally following the launch of the SpaceX CRS-1 official cargo resupply mission from Cape Canaveral, Florida at 8:35PM ET Sunday, October 7, 2012.
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 means that one of the crucial rocket’s nine Merlin engines, Engine 1, lost pressure suddenly and an engine shutdown command was issued immediately. We all know the engine didn’t explode, because we continued to receive data from it. Our review indicates that the fairing that protects the engine from aerodynamic loads ruptured as a result engine pressure release, and that none of Falcon 9′s other eight engines were impacted by this event.
As designed, the flight computer then recomputed a brand new ascent profile in real time to make certain Dragon’s entry into orbit for subsequent rendezvous and berthing with the ISS. This was achieved, and there has been no effect on Dragon or the cargo resupply mission.
Falcon 9 did exactly what it was designed to do. Just like the Saturn V, which experienced engine loss on two flights, Falcon 9 is designed to deal with an engine out situation and still complete its mission.
We will continue to study all flight data with a view to understand the reason for the ambiguity, and may devote the resources essential to identify the difficulty and apply those lessons to future flights. We’ll provide additional info because it becomes available.
Dragon is anticipated to start its method of the station on October 10, where it will become grappled and berthed by Akihiko Hoshide of the Japan Aerospace Exploration Agency and Expedition 33 Commander Sunita Williams of NASA. Over the ensuing weeks, the crew will unload Dragon’s payload and reload it with cargo to be returned to Earth. Splashdown is concentrated for October 28
This craft also works with the Falcon 9, projecting the Dragon capsule into space with nine engines. It’s designed in order that if anyone of its nine engines should fail, the on-board computers will instantly detect it and act. When a failure occurs, the fuel supply should be cut and the unused propellant may be distributed to the remainder engines, this letting them burn longer.
Because these engines were also designed to play down damage to each other should considered one of them fail, it seems that one one of the most nine was knocked out within the anomaly. SpaceX has assured that they’d be providing additional info at the exact situation because it unfolds through the day [SEE ABOVE]. We must assume at this point that the mission will continue instantly as SpaceX doesn’t seem to have their feathers ruffled an excessive amount of – stay tuned!