F9: Starlink v1.0 Launch 5


Recommended Posts

60 more Starlink commsats

 

Pad: LC-39A

Date: March14

Time: 0935 Eastern

 

And on April 8 the US Air Force will use Starlink in a nation-wide live-fire Air Battle Management System exercise, connecting air and land based assets. 

 

Sites will include Eglin AFB, Florida, Nellis AFB, Nevada, Yuma Proving Ground, Arizona, and the White Sands Missile Range, New Mexico.

Link to comment
Share on other sites

  • 2 weeks later...

StarLink v1.0 Launch 5

 

Static fire good

5th flight of core 1048 (1048.5)

Re-flight of the StarLink v0.9 fairings 

Date: Sunday, March 15,

Time: 0922 Eastern (1322 UT)

  • Like 2
Link to comment
Share on other sites

Well ... she tried to go.  Aborted right after engine(s) fired.

 

"Ignition

Liftoff

Disregard

We have an abort"

 

 

14:50

 

 

 

Link to comment
Share on other sites

Good launch & insertion, but the first stage recovery failed.  Musk said one engine shut down early creating an Engine-Out (the other 8 throttle up), so no recovery.

 

Speculation: it looked a bit wobbly during the entry burn, and the plume looked small. Perhaps one of the 3 landing engines failed? 

Link to comment
Share on other sites

23 hours ago, DocM said:

Good launch & insertion, but the first stage recovery failed.  Musk said one engine shut down early creating an Engine-Out (the other 8 throttle up), so no recovery.

 

Speculation: it looked a bit wobbly during the entry burn, and the plume looked small. Perhaps one of the 3 landing engines failed? 

That’s only the second engine to fail during a mission if I remember rightly?

Link to comment
Share on other sites

2 hours ago, anthdci said:

That’s only the second engine to fail during a mission if I remember rightly?

 

Yup, and the first Merlin 1D out of several hundred flown. The other was a Merlin 1C, a far different engine.

 

More proof their multi-engine with armored engine cells &  Engine-Out capability is the correct approach.

Link to comment
Share on other sites

  • 1 month later...

Which caused a high temp fault, triggering the Engine Out system. 

 

It was a landing engine, and a high energy launch which requires a 3 engine high-G deceleration segment during the landing burn. Not being able to do this, the booster sacrificed itself to save the droneship.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.