Josiah 🚀 Profile picture
Nov 19 10 tweets 3 min read Twitter logo Read on Twitter
I made and annotated a graph of Starship's ascent today, capturing the speed at every 1-second interval from the livestream telemetry, and it revealed some interesting things:
(1/10) A graph of the speed from Starship's initial liftoff through the explosion of the booster, segmented into parts that I found interesting. See thread for more details.
First, we see a constant acceleration of ~6m/s^2. The best reason for this that I can see would be limiting aerodynamic loads on the early ascent, which is necessary because the flaps move the CoP much higher than it is on other rockets, which do not do this on ascent.
(2/10) Image
(Falcon 9 pictured above)
The next piece is fairly straightforward, the throttle-down of the Raptors for Max-Q. This isn't as noticeable as it is on Falcon 9, most likely due to the previously mentioned aero limiting earlier in flight.
(3/10)
Then we finally see about a minute of exponential increase in speed, meaning the booster is not trying to limit aero loads or g-forces at this point, and is just pushing forward at a constant throttle.
(4/10)
Following this, we can see another period of constant acceleration as the rocket tries to limit g-forces before MECO. This can be seen on other rockets with a high TWR first stage, such as Antares:
(5/10) Image
After this, we see the speed start to decrease as the booster shuts off 30 of the 33 engines in a staggered sequence for hot-staging to begin:
(6/10)
After this is an interesting one, where SH gets pushed backwards by the force from SS's raptors, and experiences negative g-forces for a second, which (speculation) may have caused fuel slosh which ultimately killed it. Thanks to @DJSnM for originally pointing this out!
(7/10)
Then we can see a "lump" in the graph, as SH fires its engines briefly upwards as part of the flip maneuver, and the the speed starts to slow down as it starts to reverse its trajectory back toward the launch site.
(8/10)
The initial part of the boostback burn is performed at a constant acceleration of ~25m/s^2. Then, whatever caused the engines to go out kicks in, and we can see the acceleration slow as less and less engines are firing, before SH explodes in a spectacular cloud of vapor.
(9/10)
I hope you found this thread interesting, and here's the clean graph without the markups for further inspection. Thanks for reading this random idea that I found compelling and therefore spent many hours of my Saturday on!
(10/10) Image

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Josiah 🚀

Josiah 🚀 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @Space_Josiah

Nov 20
Following on from my graph of Super Heavy's ascent yesterday, I have a graph of Starship's ascent, from staging to FTS explosion:
(1/7) A graph of the speed from Starship's stage separation through the explosion of the second stage, segmented into parts that I found interesting. See thread for more details.
First, we can see that for most of the ship's burn, there is a long period of consistent increase in acceleration. This means that the Ship is firing all 6 engines at a constant throttle level, and is not trying to control for g-forces.
(2/7)
Notably, the vapor cloud appearing has seemingly little effect on the vehicle's acceleration, meaning that if it was a LOx leak as some have suspected, it was not large enough to cause a noticeable increase in acceleration as liquid oxygen was (potentially) lost.
(3/7)
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(