Recommended Posts

3 hours ago, jjkusaf said:

Missing a couple of Merlin engines on the back of that food truck .... otherwise .... looks great!

 

If Spaceballs could do it ... so can SpaceX

626b80dd797753892d9d080c34b3758b.jpg

This is so full of win, I don't know where to even begin ... only thing that's missing is "Raise Your Hands", the side pan camera, and the SpaceX paintjob. :yes: :woot:

extra data...

 

reference the above newest Dragon v1...

 

This one is D1-11 which is flying on CRS-9.
D1-12 will fly on CRS-10.
CRS-11 will be the first Dragon capsule to be reused using pressure hull of Dragon D1-6.
D1-6 was CRS-4
CRS-11 will be DR1-? (Dragon v1 reusable - #)

NASA has stated new launchers. NASA has not said that cargo craft can't be refurbished.
Various avionics and thrusters have already been reused in Dragon, Elon statement approx 2 years ago...

reference-EchoLogic/reddit

will require verification, but source usually accurate.

 

pressure vessel (hull)

DragonPressureHull.jpg

 

----------------------------

Remember the launch delay due to the barge.....

 

 Waivers of Ship Protection Probability of Impact Requirement

A Notice by the Federal Aviation Administration on 05/10/2016

 

summary

Quote

This notice concerns two petitions for waiver submitted to the FAA by Space Exploration Technologies Corp. (SpaceX): A petition to waive the requirement that a waiver request be submitted at least 60 days before the effective date of the waiver unless good cause for later submission is shown in the petition; and a petition to waive the requirements that exclude persons in waterborne vessels from the collective risk criteria and limit the probability of impact on waterborne vessels to 1 × 10 −5.

full submission at...

https://www.federalregister.gov/articles/2016/05/10/2016-09685/waivers-of-ship-protection-probability-of-impact-requirement

  • Like 1

ooops          forgot this...

 

another image of the FH booster test article

7L9Q6VL.jpg

 

image source

 

resembles wind tunnel mock-up model

 

ZJfbZzz.jpg

link

 

 

 

wzy8ooH.jpg

link

 

:D

  • Like 2
2 minutes ago, Draggendrop said:

ooops          forgot this...

 

another image of the FH booster test article

7L9Q6VL.jpg

 

image source

 

resembles wind tunnel mock-up model

 

ZJfbZzz.jpg

link

 

 

 

wzy8ooH.jpg

link

 

:D

That's pretty.  Would like to purchase one and sit it up in my living room.

  • Like 2

In reference to pressure hull reuse, McGregor storage

 

RzH0x36.jpg

SpaceX

 

--------------------------

 

Found some eye candy for Falcon "hold down", thought it was neat and dropped it here....

 

Link has images of moving mechanism

Falcon holddown mechanism test, 2015, Vandenburg

 

 

eDXIH93.png

Closed               

 

 

qYrCP1n.png

Open

 

 

JCSAT14-4.jpg

Pin between landing legs is the hold down points, also used for jack/chain stabilizing on ASDS

 

21048044876_d43001a370_o.jpg

FH will have 4 additional actuators for hold down.

 

:D

  • Like 2

Carbon scoring marks due to reentry. If that had been metal tears, I promise those would have been a lot longer and we'd see more of them, there would have been buckling/folding nearby as well as blowouts and breaches. In other words, we'd see a lot more damage, and SpaceX would have been forthcoming about it. :yes: 

Dunno if it is cracks, some sort of structural damage or just scoring marks (hard to tell really) ... but ... if it is damaged ....

 

DATA!!!

 

Gotta remember ... SpaceX didn't have high hopes for this thing returning in one piece ... so even if there is some sort of structural damage ... they have the whole thing to study versus bits and pieces. :)

 

  • Like 1

My guess would be an octaweb shielding degradation/burn through, of which caused increased pressure to push out those lower access panels. Probably a bit for expensive, than wanted, for a reusable...but this is what they need for data and improvements...still a massive win on the landing, particularly with the damage.

 

:D 

  • Like 2

Well, DD, you called it. Octaweb looked like it was on fire, you said ... you may have been right. There's no visible damage on the rest of the rocket, so a high-v entry could have messed with it. Could explain the "leaking and burning".

 

Would make a slightly stronger case for a Chem or Carbon Snuff system to put out any fires at landing; but it's not gonna help anything during a high-v boostback or entry. Problem is any chem or carbon is gonna clog up the Merlins ... :no: ... and that's a no-go.

  • Like 1

They will have a good jump, with the data, to button her up to better withstand the heat/pressure. She landed fine with an admirable control system. This will only get better. After all, this is stuff that is hard to simulate, one needs to do it and see what to improve.

 

This is a total win either way....she landed, under control and presented a book rack of data for the hot and fast returns.....next.....

:D

  • Like 1

Full size image

 

26428478544_2bff22971f_o.jpg

 

image link

 

This and 3 more on SpaceX flickr...

https://www.flickr.com/photos/spacex/

 

Three cores together will give an idea of FH's size......:D

  • Like 1

Yep, it landed with damage -- no idea how bad, but it's damage and it held up all the way to landing. That speaks to the robustness of the platform. :yes: 

 

1.3 Upgrades are in-progress, so this'll be one more thing to look at and improve where needed. I'm sure they're looking at the telemetry very carefully to see what happened, when and where it happened at. Among the things that are special about Falcon-9 Rockets ... they're smart. Nothing, nothing happens to them that SpaceX can't account for later on.

 

Take the failed strut last year. Think ULA could have figured that one out? Nope. Not a chance. And since then SpaceX has added more sensors, just to make sure it doesn't take that long to figure it out if it happens again.

  • Like 2
Just now, flyingskippy said:

Which lower access panels were blown out? I wasn't able to see anything on their flicker account. 

Down by the legs, two panels were off prior to landing on ASDS. The area can be seen on landing video. Apparently they were designed to come off when a pressurization occurs above the octaweb....referenced in a reddit thread...need to confirm still

:)

I just checked the vid and didn't see anything. I could be looking in the wrong area too though.  I did see a green flash after engine shutdown characteristic of the TEA-TEB ignition system. Maybe the ignition system took some damage as well. 

  • Like 1

Talking about this area right @Draggendrop?

 

Capture.JPG

 

Whereas the other barge landing looks like it had a black panel across.

 

Untitled-1.jpg

 

 

Still...phenomenal ... data ... plus they'll be able to reuse something from it. :)

 

  • Like 3
This topic is now closed to further replies.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!