Recommended Posts

30 minutes ago, DocM said:

On I-10, one hour east of Tuscon.

 

https://imgur.com/a/Vbxrx#zPdInH5

 

zPdInH5.jpg

It's *actually* happening

puss-in-boots-oooh-cat-gif-557.gif

  • Like 3

Well it's out of the bag now, so it can be discussed. :D 

 

Falcon Heavy Demo Mission -- May 2017 !!

 

-- Final approval for the two new pads at LC-13 (aka LZ-1) has been issued (citation), so expect some rapid construction to take place there quite soon to allow FH to RTLS all three cores if necessary. The "North Pad" has already begun ground clearing. OCISLY will likely catch the center core on the first flight, and it'll be quite a bit farther out to sea than the usual Falcon-9 positioning (in all likelihood).

 

-- Also of interest is a Red Dragon flight using FH that will test out the technology in circumlunar space sometime next year; but the RD Mars Missions scheduled for the 2018 synod are "off the table" as of now and most likely will happen during the 2020 synod. There's still talk that nothing has changed, however, and that 2018 is still the target date. I'm personally inclined to believe the 2020 date has more credibility, myself.

 

More information as it's made available. :) 

  • Like 3

Yep. :D And it's already on its' way to (likely) Texas for Static Fire Testing. That's my best guess. If Processing holds true, +2~3 months or so to test it out then on to the Cape for Integration. And we can bet that the Core Stage is gonna get worked during those SFT's. I'm sure they'll do a half-dozen or more by the time they're done. :yes: 

And TWO completed Core stages exist, iirc. Red (which rolled out with the latest two boosters) and Aqua which we saw last summer. Don't know if Aqua was actually meant to be used for flight or if it's a Test Article for reference. We never really got where it ended up at, did we @DocM? All we saw was the single image, but it was most certainly a Heavy Core's business end. Ugh. Too much Algebra now. And talking to Insiders. Sshhhh. :shifty:

Edited by Unobscured Vision
Rephrasing ...

Just doing a bit a reading. When the Falcon Heavy launches, in reusable configuration, it will be the highest capacity rocket currently flying (LEO: 32,640 kg) surpassing the delta IV heavy (LEO: 28,790 kg). In fully expendable configuration it will be classified as a super heavy lift vehicle, (LEO: 54,400 kg).

This will make it the 2-5th highest capacity rocket every depending on how you look at it. (Depending if you include the shuttle/Braun as payload and N1 as successful).

Which is pretty impressive for a private company that has only existed for 14 years.

  • Like 1
  • 1 month later...

Oh, Good Lord.....

 

First Musk tweets that the Falcon Heavy expendable payload to GTO, currently listed at 22,800 kg, can be boosted by 20% if the customer wants it 

 


@elonmusk
Looks like it could do 20% more with some structural upgrades to handle higher loads. But that's in fully expendable mode.


which calcs to 27,760 kg. That should have been a clue....

 

Now we discover that the disposable mass to LEO of 54.4 tonnes to LEO isn't up to date - it's now 64,000 kg :woot:

 

http://www.spacex.com/about/capabilities

 

 

F9-FH_full_performance.jpg

It also impacts mass to GEO, which was 22,200 kg

 

Elon Musk ✔ @elonmusk
@jasonlamb Looks like it could do 20% more with some structural upgrades to handle higher loads. But that's in fully expendable mode.

 

22,200 * 1.2 = 26,640 kg :woot:

47 minutes ago, IsItPluggedIn said:

So Falcon heavy is burgeoning on SLS block 1 territory to LEO. 

Just wait until ... ;) .... [REDACTED] ... :D ... :yes: ... *that*. Falcon Heavy is likely to have several upgrades over its' lifetime.

 

[EDIT] And the structural upgrades are only the beginning. 

Grossly overpowered for its' size is a word I'd use to characterize what Falcon Heavy will be capable of in its' final iteration ... just about equivalent to SLS. Think Defiant Class and you'll have a good idea. Punching way above it's weight, and knocking 'em out too. :yes: 

Interesting how Falcon Heavy will actually need to restrain itself in LEO/GTO missions causes such spirited ... erm ... "discussion" ... amongst the learned. Especially since they're trying to make arguments using really, really old numbers. :laugh:

They tweaked it again

 

http://www.spacex.com/falcon-heavy

 

LEO: 63.8 tonnes (-200 kg for Musk's GTO structural upgrades?)
GTO: 26.7 tonnes
Mars: 16.8 tonnes
Pluto: 3.5 tonnes

Edited by DocM
  • Like 1

As predicted, @DocM ... good call. "4+ tonnes to friggin' Pluto" (I assume in fully expendable mode). :yes: 

 

And it's juuuust able to get a B-2200 uphill, as I predicted. No need to strip the 2200 down, now

 

Now all we gotta do is wait for [static] and [static][incomprehensible][more static], then the [static][solar flare interference] and then we'll see who's getting what *where* ... :D 

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?)

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!