you all notice a few of the raptor motors weren't firing? crazy cool step though to get to the finish line eventually
Enjoy the benefits of a premium membership!
Upgrade Account
-
TalkBass has been independent since 1998. Add your voice.
Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
Join free Log in
Want zero display ads or expanded classifieds tools? Compare plans.
SpaceX and other space stuff
- Thread starter bholder
- Start date
Yeah, that was interesting. The detail of the data they put into their graphics is another thing I like about SpaceX webcasts.
Also, you get crowd noise that tells you when something isn't quite right.
Invalid Link Removed
Last edited:
Did you read SpaceX's tweet afterwards?
"As if the flight test was not exciting enough, Starship experienced a rapid unscheduled disassembly before stage separation."
I love these guys.
"As if the flight test was not exciting enough, Starship experienced a rapid unscheduled disassembly before stage separation."
I love these guys.
Rapid unscheduled disassembly! That’s a hilarious comment.
Riiiight! How manny Daffys to power that torch? Maybe they should make the Daffy a standard unit at The Register!
That launch was pretty dang exciting, for all the right reasons!
I wonder how many design advances the next stack already has.... And how soon before we see it? 48 hours?
That launch was pretty dang exciting, for all the right reasons!
I wonder how many design advances the next stack already has.... And how soon before we see it? 48 hours?
More surprising than losing some engines was that they seemed to re-light some of them mid-flight. Didn't realize they could do that.
Things seemed to be going sideways from pretty early on in the flight. Max-Q was called while the vehicle was significantly sub-sonic, and much later than the planned T+0:55. Without any actual payload it seems like the whole ship should have been going much faster much sooner.
Will be interesting to hear more about what went wrong.
Things seemed to be going sideways from pretty early on in the flight. Max-Q was called while the vehicle was significantly sub-sonic, and much later than the planned T+0:55. Without any actual payload it seems like the whole ship should have been going much faster much sooner.
Will be interesting to hear more about what went wrong.
Watching the LabPadre replays, there was damage to the QD (quick disconnect) housing on the gantry. And you can see engines going out and relighting. Lokt.s like 6 or 7 were out at one point.
I did notice the debris being blown upward at the launch, and wondered what that might have been. I'll be interested to see what SpaceX says about that, if anything.
After the launch, prior to the RUD, there's different colored flame coming off the first stage. Looks like something else blew out too.
Yeah, I'm watching the replay you posted, and at ~2:48:00, there begins a discussion about the possibility of some hydraulic damage, and one of the outer-ring Raptor engines blowing out.
On the small screen I was watching, it looked like there were 3 separate stages, all failing to seperate, with the engines trying to ignite...
As far as I was aware there were only 2 stages (the main engine, and the Starship), and we had a live camera view of the Starship engines waiting for separation, and ignition...
So I'm guessing that the fuel tank had developed a couple of cracks, and the fuel was starting to ignite.
Anyway, I hope somebody at SpaSex grabs that footage of it going into its death spiral, and uses it to replace the traditional buffering pinwheel on all their computer systems.
As far as I was aware there were only 2 stages (the main engine, and the Starship), and we had a live camera view of the Starship engines waiting for separation, and ignition...
So I'm guessing that the fuel tank had developed a couple of cracks, and the fuel was starting to ignite.
Anyway, I hope somebody at SpaSex grabs that footage of it going into its death spiral, and uses it to replace the traditional buffering pinwheel on all their computer systems.
Interesting. More discussion among the LabPadre guys that - just a theory here - with the reduced thrust from the un-lit engines, the vehicle wasn't high enough for the programming to trigger the separation. I wonder if part of the hiccup could be two competing subroutines, as it were.
Stage 1: "Time to flip!"
Stage 2: "Wait, I'm still attached."
Stage 1: "Sucks to be you! WHEEEEEE!!!"
Stage 2:
ETA: Upon further thought, it could have also been a safety lockout that prevented separation. If stage 1 realized it wasn't high enough, or was starting to do something it shouldn't, the program might keep the stages together so you don't end up with two out-of-control objects instead of just one. That way, a safety-destruct can obliterate them both.
In any case... Space is hard.
Stage 1: "Time to flip!"
Stage 2: "Wait, I'm still attached."
Stage 1: "Sucks to be you! WHEEEEEE!!!"
Stage 2:
ETA: Upon further thought, it could have also been a safety lockout that prevented separation. If stage 1 realized it wasn't high enough, or was starting to do something it shouldn't, the program might keep the stages together so you don't end up with two out-of-control objects instead of just one. That way, a safety-destruct can obliterate them both.
In any case... Space is hard.
Last edited:
Oh, man! LabPadre tweeted a clip of their remote feed showing the camera farm and the minivan taking all that damage:
Possible, but I think the higher the rocket goes…the flames change color…
Possibly, IMO, it started to tumble due to not enough rocket power due to engines not working.
But, I’m no rocket Dr…
