The Rocket Still Waiting

As September 2016 closes, the distinction matters more than any comeback narrative. In a September 23 update reported by Stephen Clark at Spaceflight Now, SpaceX said preliminary examination pointed to a “large breach” in the second stage's cryogenic helium system. Investigators were still pursuing its cause. The company anticipated returning to flight as early as November, explicitly pending the investigation's results.

That is a conditional plan, not a completed recovery. The condition is the important part of the sentence.

Finding the break is not finding the cause

The September 1 explosion occurred during fueling for a preflight engine test at Cape Canaveral's Complex 40. It destroyed the rocket and the Amos 6 communications satellite mounted above it. According to Clark's report, the engines were not scheduled to ignite for another eight minutes.

The helium system is not incidental plumbing. Clark describes pressurized helium vessels inside the upper stage's liquid-oxygen tank. During flight, helium is warmed through the engine and routed into propellant tanks to maintain pressure as fuel is consumed. A system that helps keep the stage structurally sound is therefore part of the failure investigation—not a detail safely outside the story of how a rocket works.

But locating a breach does not explain what produced it. Clark explicitly cautioned that the breach might be a symptom rather than the root cause. SpaceX said it was tracking all plausible causes through an extensive fault tree: a structured investigation of the different paths that could lead to the observed failure.

Credit is due for keeping that uncertainty visible. Declaring the mystery solved would make a tidier announcement. It would not make a safer vehicle.

The evidence has to travel further than the debris

SpaceX said only 93 milliseconds separated the first signs of trouble from the loss of data. Its account described approximately 3,000 engineering-data channels under analysis, alongside imagery, audio and video. Most debris had been recovered, catalogued and moved for inspection. The investigation included representatives from the FAA, NASA and the Air Force as well as SpaceX and industry experts.

Those are reported investigative activities, not independent proof that the eventual explanation will be complete. They nevertheless describe something more substantial than confidence: records that can constrain competing accounts of what happened.

The useful public standard follows from that distinction. A credible return should connect the evidence to an explanation, the explanation to a correction, and the correction to testing. Those are standards for judging resumption, not claims that each step has already occurred—or that SpaceX has refused them.

This is also where the people beyond the launch company belong in the account. Amos 6's owner lost a spacecraft. Other customers need to plan around launch availability; NASA depends on Falcon 9 for station cargo missions. Their need is not simply for a reassuring date. It is for a basis on which to judge what that date means.

A coherent recovery does not require publishing every engineering file. It requires enough explanation that those carrying the consequences are not asked to substitute the manufacturer's confidence for their own judgment.

In the September 23 statement, SpaceX promised to resume its manifest “as quickly as responsible” once the investigation identified the cause. That ordering deserves to survive the countdown: explanation first, schedule second.

November can be a target. It cannot be an answer to what broke.