Recommended Posts

That was immense. Looked like it lost a raptor going up then another near the landing. The green at the end was probably it trying to relight that lost one. Looked slow enough to land so maybe a legs issue too?

5 minutes ago, warwagon said:

What looks slow, is not so slow when it's something that big and heavy.

True, it’s hard to tell it’s speed and how far it was from the ground when the videos are from miles away.

 

17 minutes ago, anthdci said:

That was immense. Looked like it lost a raptor going up then another near the landing. The green at the end was probably it trying to relight that lost one. Looked slow enough to land so maybe a legs issue too?

 

17 minutes ago, IsItPluggedIn said:

Looks like they lost one at the end it was trying to relight but failed.

T-0 about 1745 Eastern

 

The ascent engine cutoffs were planned, otherwise it's go too high as fuel burns made it lighter. The RUD landing was because of low header (landing) tank pressures. 

 

OTOH, the skydiver maneuver and flip worked like a charm.

 

Screenshot_2020-12-09-17-51-51-350.thumb.jpeg.cb2a6a87b72981792aeb170fb794cadf.jpeg

 

 

 

  • Like 2

Wow, that was an unbelievable first attempt.  I can't believe how stable it was during the belly flop, and how close it was to landing.  Seems like SN9 needs only a slight adjustment.  Exciting progress!

  • Like 2

So anyone care to speculate on the low pressure? Are we talking something they can adjust for next time or perhaps a redesign so we're not likely to see SN9 rolling out any time soon?

I assume the header tanks were probably full so it's not going to be as simple as just putting more propellant in there? Maybe a chilling issue where it's boiling off too quickly? Maybe just a simple plumbing issue due to the forces generated on the flip.

 

I'd love SpaceX to include telemetry on the next one.

 

Aside from all of that, honestly it blew my mind watching that, I was just waiting at every step for something to go wrong. When the first engine went and there was a little jerk I thought for sure that was an engine loss so was waiting for them to trigger an abort. Then the second one went and the rocket just seemed to hover and I thought ok now this is defiantly an abort, they may have attempted with 2 raptors to land (that was always the plan anyway right?) providing they still had the two raptors they needed but when it just sort of hovered on one for quite some time I was just waiting for the boom.

 

Then comes the flip, OK maybe they'll abort part way down or let it crash into the sea and my god did it seem to fall slowly. There were times where I thought the video had frozen it looked so still and stable.

It wasn't until it started to drop below the cloud cover and you could see it looked to be over the pad did I start to believe it might actually make it. 

I don't know if this is right but I'm not sure the landing legs deployed but that could have just been due to the higher velocity and it not having enough time but that thing came unbelievably close.

  • Like 1
9 hours ago, spacelordmaster said:

The crash seems to have been caused by the landing rockets failure to slow the ship down. It was coming down too fast it seems.

The landing is fed by two header tanks, not the mains.

 

The methane header is between the two mains, and the oxygen header is in the top of the nose for balance reasons. Each tank is pressurized to help push the liquid methane or oxygen into the lines & engines before the engine pumps start.

 

Apparently what happened was the methane tank pressure wasn't high enough, causing low power & a hot oxygen rich burn. Hot oxygen eats metal, so the engines cooked.

 

Here's a video showing the header tanks,

 

 

  • Like 2

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
  • Posts

    • Thank god they got rid of the disgusting looking sidebars, and the corner radius looks much better, too. Two things I hated on day one, and never got used to.
    • JetBrains launches Rider 2026.2 EAP 5, bringing several AI improvements by David Uzondu JetBrains has released the fifth EAP version of Rider 2026.2, bringing a faster startup flow with the new non-modal startup screen and quality-check hooks for Claude Code and Codex. In the latest EAP release, Rider now has newly bundled "quality-check" hooks that run background tests on code edits before the external agent proceeds. For example, after Claude Code rewrites a class, Rider immediately triggers a PostToolUse hook that analyzes the code for syntax errors and formatting warnings. It then passes those findings back to the model as feedback, allowing the agent to fix its own output before finalizing the task. If Rider detects compilation errors, the IDE prevents the agent from treating the task as complete, while minor formatting warnings simply help guide the model toward better output. The "Explain with AI" feature can now tackle tricky build errors directly from the console, helping .NET developers who frequently wrestle with multi-targeting failures and MSBuild errors. JetBrains introduced Explain with AI back in the 2024.1 release cycle. With this feature, instead of forcing developers to copy long diagnostics into a separate chat window, Rider now lets you trigger these explanations directly from the error source. In similar EAP news, JetBrains recently opened the first EAP for IntelliJ IDEA 2026.2, with features that appeal to both those who are into AI-assisted coding and those who prefer "classic" manual development. For manual developers, the release adds revamped dependency completion for Maven and Gradle build scripts, which pulls data directly from the local cache to suggest relevant versions. It also brings the Spring Debugger update, displaying security indicators next to endpoints to visualize secured routes during runtime. In addition to database migration tools for Flyway and Liquibase, this build introduces a Hibernate debugger that shows the exact SQL or HQL queries that the framework plans to execute, letting developers jump directly to the Java code that triggered them.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      502
    2. 2
      PsYcHoKiLLa
      222
    3. 3
      ATLien_0
      87
    4. 4
      Steven P.
      80
    5. 5
      +Edouard
      80
  • Tell a friend

    Love Neowin? Tell a friend!