Recommended Posts

2 hours ago, SALSN said:

All these impressive numbers are before any Raptor implementation, correct? Whit a Raptor second stage, this is going to be even crazier! (Perhaps that is what all the static is Unobscured Vision's posts are about? but as far as I know that is not really a secret?)

Everybody's already known about a likely implementation of Raptor on the second stage for a while now. The stuff in [static] and [elsewhere] are ... spoilers. :) Stuff that can't be disclosed yet, but can be teased. Elon will drop the mic when he's ready to, Soon (TM). :yes: 

1 hour ago, Unobscured Vision said:

Everybody's already known about a likely implementation of Raptor on the second stage for a while now. The stuff in [static] and [elsewhere] are ... spoilers. :) Stuff that can't be disclosed yet, but can be teased. Elon will drop the mic when he's ready to, Soon (TM). :yes: 

That is what I thought. But now I'm even more curious to find out what the next reveal is about, I thought they had pretty much dialled the F9 system in by now, and thus also the F9 which is of course largely based on the F9.

The center core is already massively overbuilt; a whole different core version. Also a new Interstage, S2 upgrades include reinforcements, mods for a much longer coast (direct geostationary insertions for DoD) etc. This bird will be a bad ass mo-fo without a Raptor S2. 

 

Don't be surprised if the new, larger, forged titanium grid fins look a bit like those on ITS.

  • Like 2

And the boosters will be reflown cores, so reusability pays off often and early.

 

A successful Falcon Heavy maiden flight with 3 recoverd cores, 2 reused, would be a flipping earthquake in the launch industry.

  • Like 2

Chris Bergin at NSF just posted an image of a soon to be re-flown Falcon Heavy booster core on the test stand at McGregor. Sounding like it's Core 1023 - Thaicom-8.  Now 1023-2.

 

http://forum.nasaspaceflight.com/index.php?topic=42705.msg1665165#new

 

ConeHeads Rule!!l

  • Like 2
  • 2 weeks later...
  • 3 weeks later...
  • 3 weeks later...

They've already tested all 3 cores separately. 

 

They have a few items to add to the launch mount, including 4 more hold-downs and plumbing, before they can mount Falcon Heavy.  They also have to mount the Commercial Crew crew arm & white room. Can't do those until LC-40 is back in operation, which should be August-ish. Should take about 6 weeks.

 

The first integrated burn with 27 engines will be a wet dress rehearsal and static fire on LC-39A this fall.

Edited by DocM
  • Like 1
10 hours ago, DocM said:

SpaceX says a mass simulator of some kind, but pulling a rabbit out their hat at the last minute wouldn't be a surprise. 

or a wheel of cheese ;)

  • Like 2
  • 2 weeks later...
  • 3 weeks later...

BIG BIRD INCOMING!!

 

FH booster core 1023.2 (Thaicom-8) heading to KSC to meet up with 1033, the FH #1 center core. FH booster core 1025.2 (CRS-9) mods are being finished up before heading to McGregor for firing.

 

The FH #1 S2 "Frankenstage" is next. The Frankenstage is modded for the S2 recovery experiment on FH #1.

 

All photos taken at Imgur....

 

59559df9e521c_FH1_booster_core-B1023.thumb.jpg.7fd8a5937757d01ea06d16e56676293f.jpg

  • Like 2
  • 3 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!