Launch News [Sep.1, 2016] Falcon 9 explodes on the Launch Pad

IronRain

The One and Only (AFAIK)
Administrator
Moderator
Orbiter Contributor
News Reporter
Donator
Joined
Oct 11, 2009
Messages
3,488
Reaction score
407
Points
123
Location
Utrecht
Website
www.spaceflightnewsapi.net
This Falcon 9, F9-029, was meant to launch Israel's Amos-6 communications satellite. It is not sure if payload was aboard at the time of explosion

CrRWg16WgAEs6d3.jpg:large


No reported injuries, but it happened a couple of minutes ago, so this is still developing.
 
Last edited:
Just saw it on facebook, dude out in the water snapped a picture.
 
Was it during the static fire test? So I guess there was no payload on it?
 
"The satellite was supposed to be attached to the rocket for the test fire."

"The satellite was attached to the rocket for the test fire."​
Spaceflight Now: Explosion at Falcon 9 launch pad
 
Just smoke rising
[ame="http://www.youtube.com/watch?v=gy5-X-shRRE"]Incident At Kennedy Space Center SpaceX Test Site - YouTube[/ame]
 
I'm sure some of it is that gray smoke...
Yes, that video was grabbed after the explosion, not before. It's a record segment from this feed: http://kscwmserv1.ksc.nasa.gov/channel4 which currently shows LC39 OTV camera 080 which is on the SE corner of the roof of the VAB.

---------- Post added at 04:24 PM ---------- Previous post was at 04:17 PM ----------

This is per Eric Berger:

[ame="http://twitter.com/SciGuySpace/status/771352111657385984"]Eric Berger on Twitter: "Official statement from @SpaceX: https://t.co/GxvH2E8401"[/ame]
 
Last edited:
They take three steps forward, then one back.

I see the service structure is still standing....
 
Last edited:
Well, at least we learned from the previous mistakes and there were no people around the pad this time...

What could have happened there?
They say it was 3 minutes before the test, so a rocket was just standing there and decided to blow up all of a sudden?

Such a bad timing, too - no one was expecting anything interesting to happen yet, so all the cameras were off.
 
Well, at least we learned from the previous mistakes and there were no people around the pad this time...

What could have happened there?
They say it was 3 minutes before the test, so a rocket was just standing there and decided to blow up all of a sudden?

Such a bad timing, too - no one was expecting anything interesting to happen yet, so all the cameras were off.
Based on the position of the Transporter/Erector (T/E), it was not T-3 minutes as it is retracted by then.
 
Quite dismaying considering the first NASA crewed flight by SpaceX is planned to be in 2017:

SECOND SPACEX CREW FLIGHT ORDERED BY NASA.
DEREK RICHARDSON JULY 30TH, 2016
http://www.spaceflightinsider.com/o...ogies/second-spacex-crew-flight-ordered-nasa/

I'm thinking NASA will now want multiple successful flights by SpaceX before ok'ing a crewed flight by SpaceX. This will likely push back the first SpaceX crewed flight to 2018.

The first reuse of a F9 booster planned for later this year becomes also more problematical now. Though for the crew flights SpaceX would use new boosters, having two failed boosters in a row would still look bad for SpaceX if the reuse booster did fail, especially for SpaceX trying to build a reputation of reliability for crewed flights.

Bob Clark
 
Last edited:
it was not T-3 minutes
What was scheduled time for the static fire test's ignition, as I can't find it anywhere (everyone writes only about explosion)? According to 45th Space Wing the explosion occurred at 9:07 a.m. EDT.
 
What was scheduled time for the static fire test's ignition, as I can't find it anywhere (everyone writes only about explosion)? According to 45th Space Wing the explosion occurred at 9:07 a.m. EDT.
That no-one except SpaceX knows. They never publish the T0 for the static fires.
 
Perhaps someone flew their Delta Glider into the pad while checking out the beautiful new scenery... :uhh:
 
Perhaps someone flew their Delta Glider into the pad while checking out the beautiful new scenery... :uhh:

Or the booster flight controller was too busy testing Orbiter 2016 on his second screen.
 
Back
Top