Recommended Posts

Inconel is an iron-nickel-cobalt-titanium superalloy which is incredibly tough. It's used for printing SuperDraco engines.

The Dragon spacecraft would have survived if it had been programmed to deploy its parachutes after the vehicle broke up (even without SuperDraco abort engines !!), and from now on the software will support this safety mode.

Article released.....

 

 

In a teleconference with reporters, Elon Musk said the preliminary conclusion of the three-week investigation was that a steel strut, designed to hold a bottle of helium in place within the upper stage

Interesting....

http://www.spacex.com/news/2015/07/20/crs-7-investigation-update

>

As noted above, these conclusions are preliminary. Our investigation is ongoing until we exonerate all other aspects of the vehicle, but at this time, we expect to return to flight this fall and fly all the customers we intended to fly in 2015 by end of year.

>

Overpressure, just not the way we would think it could happen. Wow. And a strut failing like that is sure to put the supplier out of business just from the lawsuit(s) alone.

 

Not sure if the information is publicly available on who made the strut, or the Engineering Data for that piece. Probably not, though I'd love to take a look at it. It has to be a company in the United States in order to clear Mil/Gov Certification requirements. I doubt that information is just going to be accessible to anyone who'd want it.  :laugh:

 

So, we'll just go on what we've been told in the release. A strut rated at 10k failed at 20% load, most likely from material defect. The rest of the assembly, not designed to compensate for a failure (since it shouldn't happen) simply did its' job but the COPV tank mounted inside the LOX tank broke loose, ruptured, and then overpressurized the LOX tank.

 

Even if that happened 20 minutes later, after the S2 had been fired and most of the LOX had been used up, that stage would have hosed and unusable. That Merlin-D would never have fired up again; or if it had, it would have exploded. Likely there are safety checks to prevent an explosion event if the LOX supply were "tainted" by the COPV supply, but at least the overpressure event wouldn't occur. It would still mean the Dragon and its' cargo wouldn't make it to the ISS, forcing an abort and return to Earth.

 

Yeah, bad stuff. At least it was a "sure thing" that the Dragon survived intact and the ground received data from it for as long as they had Line of Sight. I wonder what ultimately happened to it.

This Dragon 1 hit the water at terminal velocity. In the future they'll be programmed to deploy the chutes if F9 breaks up. Cargo Dragon 2 will also fly, with SuperDracos and parachutes.

....but the COPV tank mounted inside the LOX tank broke loose, ruptured, and then overpressurized the LOX tank.

>

No sign that the COPV ruptured.

http://www.aviationweek.com/space/musk-outlines-suspected-root-cause-falcon-9-failure

>

In a teleconference with reporters, Musk said the upper stage exploded while the first stage was still firing after a high-pressure helium bottle broke loose in the upper stage

Oh, excuse me. I thought the COPV tank itself ruptured once it broke loose. I forgot how buoyant Helium actually is, even at 5,500 psi. Liquid in a liquid will still obey density differences, no matter what pressure it's at.

 

So yeah, it probably floated to the top of the LOX tank, and from there all hell broke loose (literally) because it still hit the top of the LOX tank with the mass of 5,500 psi of Helium plus the mass of the COPV tank .. yeah, overpressure time for the LOX tank. Sometimes all it takes is a light tap with those kinds of forces and that kind of cold, as DD will be familiar with. If that COPV tank was moving around the LOX tank, and impacted the sides or the top with enough force, it could cause a defect and a rupture point too.

  • Like 1

I bet Elon was pretty steamed at that supplier...

I'm not sure "steamed" is enough to describe how truly p***ed off Elon, the rest of SpaceX, NASA, Boeing, and the Aerospace Industry in general is at that supplier right now.

 

Sepeiku with rusty steak knives, toothpicks and horribly inefficient spoons are probably being planned for tomorrow at the supplier's headquarters as we speak.  :shiftyninja:

I'm not sure "steamed" is enough to describe how truly p***ed off Elon, the rest of SpaceX, NASA, Boeing, and the Aerospace Industry in general is at that supplier right now.

 

Sepeiku with rusty steak knives, toothpicks and horribly inefficient spoons are probably being planned for tomorrow at the supplier's headquarters as we speak.  :shiftyninja:

 

I'm English, understating things comes with the territory. ;)

  • Like 1

The "counter intuitive" is what really bothered me...still does a bit until Elon clarifies the "readings" which ultimately lead to this statement. With out further info, and going on the articles data, imho, I have to lean on the idea that the strut broke due to metallurgical issues, tank rattle and eventual displacement which caused contents to dump before contact reseal of lines and the increased pressure in the LOX tank was now above rating and blew. This may have shown as COPV pressure decrease (during prechill sequence) and abrupt sealing, as LOX tank pressure increase (in stage 2)....while stage 1 was still in it's phase...giving the headshake in instrumentation for .9 seconds. SpaceX has to get back launching, and an increased launch schedule as mentioned can be done with this time punching out cores and assembly till then.....Hope for the best...These guys are GOOD....

 

Sad to hear about the "heavy" delay

 

Watch everyone else learn from this and have chute capability on launch.....Cheers

  • Like 1

I am going to orlando for my honeymoon around April time next year. Could I get lucky and it coincide with the first falcon heavy launch  :cool:

 

I tried that on my honeymoon 16 years ago. I was even lucky that were was going to be a launch whilst I was there, but when it came down to it, I just couldn't go to the launch...

 

Last time I went to one, the Challenger exploded. Guess it's still bothering me! :(

I tried that on my honeymoon 16 years ago. I was even lucky that were was going to be a launch whilst I was there, but when it came down to it, I just couldn't go to the launch...

 

Last time I went to one, the Challenger exploded. Guess it's still bothering me! :(

 

I've wanted to see one for years but the last time we were there I was under 25 so the extra insurance on a hire car made it far too expensive so I couldn't get there. My other half isn't all that bothered by it thought so I doubt she'd want to drive all the way there for a scrubbed launch.

A candid reminder on complacency.....

 

 

 

The explosion of a SpaceX rocket during a space station resupply mission last month jolted the company awake in some ways, CEO and founder Elon Musk said.

Prior to the June 28 Falcon 9 rocket explosion

  • Like 1

If only NASA would have sent out an email asking if there is any reason at all to delay the launch of Challenger.

Got to give props to SpaceX for having such a candid open floor policy. It isn't as common as it should be in the aviation/aerospace industry.

  • Like 2

Interesting stuff going on.

NSFers report

http://forum.nasaspaceflight.com/index.php?topic=36326.5150

a west coast crew appears to be training recovery ops with a used Dragon

two east coast support ships appear to be sailing a search pattern that indicates the use of side-scan sonar. Together with Musk's statements about using an ROV to search for CRS-7 debris, it appears the hunt is still on to find S2 and perhaps the Dragon.

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

    • No registered users viewing this page.
  • 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!