Recommended Posts

I wonder what sort of procedure they have for removing the side booster nose cones from the interstage, they usually place that cap on it that locks itself to the stage after which they can lift it... but i suppose now they need some guys in a cherrypicker going up to unlock that nosecone first.

  • 2 weeks later...
2 minutes ago, DocM said:

That's not a booster, it's the new beefed up center core.

 

 It's rumored at least one FH booster will be a previouslycflown stage. 

I was going to say. Is it wider than a normal core?

  • Like 1

Thicker hull, massively beefed up Octaweb to take the loads, Octaweb mounts & longerons for the lower ends of the boosters, and a new beefed up "Sport" interstage with upper mounts for the boosters. 

  • Like 3

Nothing official, but gathered from tweets and recent articles...

 

1) Appears 39A was scheduled to be ready in November 2016, just not for FH, F9 could launch though.

 

2) FH requires new tracking systems for multicore landings, ordered from Orbital Systems, to be received on January 1, 2017 and will be installed then. This would conclude that FH would not have been able to launch in November 2016. Presently only have one tracking antenna at the cape, two more coming in so that all 3 stages can RTLS. (SpaceX payed for the gear)

 

3) Rumor of a "previously enjoyed" booster to be used on initial flight. No idea of the accuracy, but S1 has been proven to be the toughest stage ever built...unless someone has landed and tested one as much....(crickets)...

 

4) Have not heard anything on the construction at LZ-1 for the additional core landings.

 

5) Rumor has it that the damage at LC-40 is "moderate"...which I take as being a lot better than "nuked".

 

Anyone have anything else?

 

Thought this was a good article...will bring a reality smile

 

Why Exploding Rockets Are Not Always a Bad Thing

http://www.space.com/34051-exploding-rockets-arent-always-bad.html?utm_source=Twitter&utm_medium=Twitter&utm_campaign=socialtwitterspc&cmpid=social_spc_514648

 

:)

  • Like 2
  • 4 months later...

Going back to the cross feed system, or lack of it. I know it was talked about nearly a year ago. But I heard it mentioned somewhere fairly recently and was curious how they would manage the fuel in the centre booster. I presume they cant run all 3 at full power or all 3 will run out of propellant at the same time so will the centre booster be throttled back while the side boosters are in action then have it's power increased as those boosters prepare to and do detach?

With the cross feed system I think the idea was to run all three cores at full throttle but feed fuel from the outer cores to the inner core, so at the time the outer cores separate the inner core would still have lots of fuel.
With that plan dropped I'm not entirely sure how they will do it, I think it depends on the mission. They could drop the two boosters early with enough fuel to return and let the middle one burn for longer and land it on a barge. But like I said, that would probably depend on the mission, whenever it is possible to send the three boosters back that would probably be the cheapest solution.

I think they'll do it the "Delta-IV" way. Center Core will be in a partial-thrust mode until a bit after the two Side Cores separate, then it's a "Full Thrust" mode (see what I did there? :D) until it's spent and staging occurs. No reason to abandon what works. :p 

16 minutes ago, DocM said:

And we need to remember that 100% on that center core will be the Block 5 thrust of 1.9 million lbf.  Early FH's will likely use the Block 4 for a few launches for reuse testing.

Sweet, we'll get to see the performance of a Block-IV for a few launches. :yes: Even if it's on a FH, it'll fly. Works for me.

  • 2 weeks later...

HEADS UP!!

 

A Falcon Heavy side booster left Hawthorne last night!! Obvious because it had a nose cone in place of the interstage, and the front dolley wheels were repositioned.

 

 

I said a rude word as I was watching that video the first time haha

 

"Ok there's the engines....then the stage....still normal stage...NOSE CONE OMFG!"

Soon, Daniel-san ... soon.

 

Show me wash car. Hei. Show, wax-on, wax off ... hei. Show, paint the fence ... yosh'. Now show sand the floor ... hei. 

 

*Bow* You ready now. :D

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

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • 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. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? 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
  • 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!