Live data from Hacker News

A SpaceX Falcon 9 rocket has exploded at Cape Canaveral

techcrunch.com

81–90 of 560 posts

Re: A SpaceX Falcon 9 rocket has exploded at Cape Canaveral

#81
post #5

Wild-ass speculation in the absence of more information than a tweet and a photo of a pad fire: SpaceX test-fire the first stage motors before each launch. If this was a test firing that went spectacularly wrong, it's embarrassing -- but there won't have been any human beings within blast range and it's better to fail in test than to fail in flight with a payload on top. (If it was a catastrophic failure during fueli…

It looks like it was during fueling, and the payload is lost.

[deleted]

Re: A SpaceX Falcon 9 rocket has exploded at Cape Canaveral

#82
post #70

Earlier quoted context omitted.

I know nothing about space - why are they doing tests, where the rocket could possibly explode or fail, with the payload on board?

That was my first reaction. I thought they could create a dummy payload with the same dimensions and weight. But, then... unless the weight distribution of the payload is important.

Loading the payload isn't a quick thing, it takes time and a lot of careful work to do. So doing it before the tests can save a lot of time and I'm guessing money.

Re: A SpaceX Falcon 9 rocket has exploded at Cape Canaveral

#83

My mind goes to the debugging stage after the dust has settled... how would a rocket scientist determine the cause of a RUD like this?

Not a rocket scientist; just an electrical engineer with plenty of failure analysis experience. Here is generally how I would translate my process to this case.

As a sibling mentioned, there will be lots of telemetry about what was going on with various systems during the incident. That data may indicate a few specific points to start, but it will mostly be useful for putting other facts into context. In parallel would be an effort to comb over the pad, recover as much as possible of what remains of the rocket, and try to identify what parts are what. There may be some obvious forensic evidence of parts to concentrate on, but in all likelihood the analysis will be guided by a combination of analyzing the telemetry and the damage patterns on the remaining pieces. Hopefully the combination will narrow the probable causes down enough to concentrate analysis on a couple-three theories.

Once plausible and probable theories are identified, teams will start to drill down into what event chains could cause them and look for evidence to confirm or reject those. Some of that will involve destructive analysis of the wreckage; you can glean a surprising amount of information from high-magnification images, x-rays, and sections of what otherwise looks like a twisted hunk of scrap metal. Some will involve modeling; no doubt the engineers who designed the engines have some sort of model they used to test it, and the parameters on that model can be varied to create various out-of-spec conditions. Some will be design analysis, to see if some previously-unseen corner case could have caused an otherwise-conformant system to fail catastrophically. Test data on the involved systems will be analyzed to look for any anomalies that might have been passed off at the time but that might be significant on hindsight.

Assuming possibilities still exist and are not sufficiently firm, or even just to be extra thorough, a few possibilities may be tested in practical (and possibly destructive) tests. In other words, try to blow up (or simulate blowing up) another engine in a controlled manner. That may or may not be possible, depending on what the root cause is; a parts tolerance issue, for example, would be practically impossible to recreate unless it were possible to manually change affected parts to match the suspected tolerances that caused the failure.

I'm sure an actual rocket scientist will come along and provide more detail. My work was limited to exploding caps and FETs.

Re: A SpaceX Falcon 9 rocket has exploded at Cape Canaveral

#85

For all developers of anything. Repeat this mantra. This is why we test, this is why we test, this is why we test. It is especially important to repeat this mantra around management types who want last minute builds before going in front of important customers, because the light blue button looks SO much better then the dark blue button...

I mean, it's not like SpaceX doesn't test. They missed something, and unfortunately this time it caused a total loss that they're going to have to answer to. But yes, you're right; we recently implemented a two-week demo lockout policy at my office. No changes are allowed being committed closer than two weeks from a demo date, and two or three guys are dedicated to just testing and shaking down the system. They're the only ones allowed to call for a bug fix, and they're only allowed to call for a bug fix. It seems as though management has finally realized that missing one requirement during a demo is much, much better than having the whole enchilada crash spectacularly.

Re: A SpaceX Falcon 9 rocket has exploded at Cape Canaveral

#87
post #58
post #31

Earlier quoted context omitted.

The reused rocket will be used to launch SES-10 later this year, not AMOS-6. Source: http://spacenews.com/spacex-to-launch-ses-10-satellite-on-re...

Question is whether they will have a launch pad at that time and how long investigations will last and until a fix is deployed. May well be that there are no more launches this year.

Yeah the last time they lost something it was a 6 month freeze on launches.
Post reply on HN