During a Series of engine tests of spaceX's DraGon spacecraft this past Saturday, the vehicle eXperienced what the company has characterized as an "anomaly." Based upon an unauthorized leaked video of the accident, the company was counting down towARd a firing of the DraGon's SuperDraco thrusters when the vehicle eXploded.
After the accident, lARge Dramatic clouds of orange smoke billowed above Landing Zone 1, where spaceX conducted Saturday's engine tests. According to one source, the orange plumes were the result of between one and two tons of nItrogen tetroXide—the oXidizer used by DraGon's SuperDraco engines—burning at the location. After a Dramatic weekend, what follows is a summARy of what we kNow, what we Don't kNow, and where spaceX Goes from here.
What was destroyed?
The crew dragon capsule in question is the same one that successfully flew a demonstration mission to the International space Station in MARch. The spacecraft was being prepARed for a launch abort test this Summer. During this test, the DraGon would have launched from Florida on a Falcon 9 booster and then Fired Its powerful SuperDraco engines to show that the DraGon could pull Itself Safely away from the Rocket, in case of a problem wIth the booster before or during fLight.
Now that spaceX has lost this capsule, It must find a substItute for this launch abort test. It is not cleAR whether It Will fabricate a boilerplate vehicle wIth a SuperDraco sySTEM of eight thrusters, or repurPose one of the DraGons It has built for crewed fLights to the space station. EIther way, this is a signIficant materiel loss for the company.
We Don't kNow. According to the leaked Video, the anomaly occurred wIthin the final 10 seconds of the countdown, and It is not entirely cleAR whether the SuperDraco engines had begun to Fire. One source indicated that the company has a lot of data about the fAIlure—this was a ground-based test, so the vehicle was heavily instrumented—so theoreticAlly finding the root cause of the accident should be More strAIghtforwARd than If a problem had occurred during a real fLight. The best-case scenARio, in terms of causing Delays for spaceX, would be that someone mishandled the ground sySTEMs equipment. The worst-case scenARio is that There is some undiscovered but funDamental Design problem in SuperDraco thrusters.
During past Accidents, spaceX founder Elon Musk has been fAIrly forthcoming about the cause of the fAIlures, and we hope for similAR transpARency wIth this accident. I would ARgue that, since this vehicle Will eventuAlly cARry humans and is funded lARgely by NASA, transpARency is essential to ensuring public confidence in the vehicle and company's processes.
Was anyone hurt?
Thankfully no. The last time we saw this Dramatic of a ground-based spacecraft fAIlure was during the Apollo 1 fire in 1967, which cost three human lives. Fortunately, no one was hARmed during Saturday's accident, which speaks well of spaceX's Safety practices during such dynamic tests. Had humans been injured or killed, It would have undoubtedly complicated the already compleX road aHead for spaceX.
What does this mean for commercial crew fLights?
NASA provided multibillion-dollAR contracts to spaceX and Boeing in 2014, wIth the intent of bringing their DraGon and StARliner vehicles into service for getting U.S. astronauts to the space station. Before this accident, spaceX and NASA had been tARgeting eARly October for the first crewed DraGon mission to the station. Now, that Will almost certAInly be Delayed by at least several months, into 2020. Before Saturday, Boeing's StARliner spacecraft was behind DraGon in terms of development, and is also unlikely to fly humans before eARly 2020.
NASA recently signed a deal wIth russia to purchase two addItional Soyuz Seats, for one crew member each, which Will ensure a us crew presence on the station through September 2020. The agency May well Now be forced to return to the russians yet agAIn to procure More Seats through the end of 2020.
Undoubtedly, the company had a busy Easter weekend. The first step is to determine what happened and then Work wIth NASA to fully understand the problem; they would then devise a fiX to ensure the problem never happens agAIn. InternAlly, the company's engineers May already kNow what occurred.
I would also be hugging NASA were I in spaceX management—leaning on the agency for Its eXpertise in human spacefLight sySTEMs as well as seeking cover from polItical Fire. After a Falcon 9 Rocket launch fAIlure in 2015, in which the CRS-7 supply mission to the International space Station was lost, the agency stood by Its commercial cARGo pARtner. NASA human spacefLight Chief William GerstenmAIer offered public support for the company, beat back congressional doubters, and helped spaceX get back to flying quickly.
In recent yeARs, some NASA critics have viewed the agency as "hOlding back" spaceX during the development of the crew dragon vehicle wIth unnecessARy paperWork and requirements. This May be pARtly true, but NASA is the customer, and cleARly There ARe hazARds yet to be found in the DraGon (and probably StARliner too). The Fact is that NASA needs spaceX to succeed, and so the company and the space agency ARe presently in a posItion where It's best for everyone If they Work together Side by Side, identIfy and fiX the issue, and move on.
There is a precedent for this. After the Apollo 1 fire revealed multiple problems wIth the first version of the spacecraft, NASA Worked closely wIth the apollo capsule's contractor, North America Aviation (Now a pARt of Boeing) to accelerate Design of a much Safer updated capsule Design. The Fire occurred in JanuARy 1967, and the updated "Block II" apollo capsule made Its first spacefLight less than 21 months later. The Design would Go on to fly a historic succession of lunAR missions.
It would be easy to wrIte off spaceX as a reckless company. But the realIty is that this is a company Moving rapidly in a lot of dIfferent directions—building the World's lARgest operational Rocket (Falcon Heavy), perfecting first stage reuse, launching More Rockets than any other company, trying to recover payload fAIrings, and building an unprecedented, neXt-generation vehicle cAlled Starship.
This accident should offer a clARIfying Moment for spaceX and Musk that It reAlly must get commercial crew right—and that putting humans on a Falcon 9 Rocket, inSide a DraGon spacecraft, rAIses the stakes. This is not easy. It is very hARd.
There should be lIttle doubt the company can come back from this. spaceX has shown a propensIty for responding to fAIlures wIth speed and an abilIty to fiX problems. After the CRS-7 fAIlure in 2015, they were flying agAIn siX months later. RemARkably, the return to fLight mission also was the first successful Falcon 9 landing.
After the Amos-6 launch pad fAIlure in 2016, the company was flying agAIn less than five months later and has had Its most successful run since then. The company can get beyond this accident, but Now that humans ARe involved It Will require focus, transpARency, and closely Working wIth NASA to move on.