Recommended Posts

The current NASA shedule is DM-1 (uncrewed) in July 2017 and DM-2 (crewed) in Q4 2017.

 

Boeing's Starliner is at least 6 months behind and may slip again. They really screwed up.

 

NASA is not buying any Soyuz seats for 2019.

 

NASA is talking to Blue Origin about getting their SV vehicle ready for Commercial Crew. A cynic might think this is a hedge against Starliner dropping out.

NASA added requirements to both which slowed them down. Of course Boeing has other issues.

 

Crew Dragon is doing rather well, with the last milestone chart showing the propulsive landing milestone ticked. NASA wants that tested on cago first.

 

The major issue for SpaceX is when to load astronauts. .

 

NASA has always loaded astronauts after rocket fuelling. Downside: no one has protection if the rocket goes kaboomski.

 

SpaceX feels before fuelling is better; if anything goes wrong the astronauts are buttoned up, the SuperDracos primed for a bugout, and the ground crew isn't anywhere near a fueled or fuelling rocket

Edited by DocM
  • Like 1

Someone took the pad abort test video and edited it into the AMOS-6 video, timing Dragon 2's takeoff until the explosion had started.  Remember, Dragon 2 is covered in thermal protection materials which are good for re-entry from Mars/Moon velocities  - much hotter than the boomski.

 

Zzzoooommmmmm....

 

 

Edited by DocM
  • Like 2

Yes, they would have been fine. "Bugout Mode" would have gotten them away before anything nasty got to them, though they would feel the initial shock of the little boom that started all of the problems -- but it would be equivalent to what they'd feel at a surface landing. AKA stuff that Dragon 2 is designed to deal with anyway.

 

Dragon 2 could be set on fire with those combustibles of the kaboom seen above, and the crew inside would be fine. Those temperatures are far lower than those experienced at reentry. Obviously it's an undesirable situation, but that's what "Bugout Mode" is meant to prevent. Dragon 2 is the safest craft ever built, in any arena. Stick me in there and set it on fire with whatever ya want ... I'll sit back and dink around on Facebook. No worries. :yes: 

There's also the Deorbit Now button. For example;

 

Something happens which requires ISS to be evacuated and no pilots survive. Evacuees dive into Dragon, close the hatch, punch Deorbit Now, then Dragon does what comes naturally.

  • Like 1

Quoting Rupert Pearce of Inmarsat. 

 

Inmarsat 5 F4 is in the queue for Q1 2017

 

http://spacenews.com/inmarsat-juggling-two-launches-says-spacex-to-return-to-flight-in-december/

 

"SpaceX has obviously spent some time investigating the reasons behind their recent launch failure," Inmarsat Chief Executive Rupert Pearce said in a conference call with investors. "We believe they now have found a root cause that is fixable quite easily and quite quickly. So they should be able to return to flight in December."

  • Like 2

I'm sure there'll be a recording up of the interview shortly, but: 

 

Elon Musk on CNBC: "It looks like we'll be back launching by mid-December" & "[Amos 6 issue] has never been seen before in the history of rocketry" 

I can't really link exactly to it because it was live-tv, but he had the following to say:

We seem to have figured out what the issue was 

The problem had to do with liquid helium, advanced carbon composites, and solid oxygen.

This has never been seen before in rocketry, so that's why it was hard to figure out

But it looks like we'll be back launching by mid-december

He didn't reference if that would be at 39A or Vandenburg

 

https://www.reddit.com/r/spacex/comments/5b4do8/elon_musk_on_cnbc_it_looks_like_well_be_back/

Space News....

 

Quote

 

Musk predicts mid-December return to flight for Falcon 9

 

WASHINGTON  SpaceX Chief Executive Elon Musk said Nov. 4 he expects the Falcon 9 rocket to return to flight in the middle of December after overcoming a problem he claimed was unprecedented in the history of spaceflight.

 

Musk, briefly discussing the status of SpaceX during a half-hour interview on the cable news network CNBC Nov. 4, said that investigators had determined what caused the Sept. 1 pad explosion that destroyed a Falcon 9 and its satellite payload during fueling for a static-fire test.

 

"I think weve gotten to the bottom of the problem," he said. "It was a really surprising problem. It's never been encountered before in the history of rocketry."

 

Musk, confirming earlier discussion about the investigation, said the failure involved liquid helium being loaded into bottles made of carbon composite materials within the liquid oxygen tank in the rockets upper stage. This created solid oxygen, which Musk previously said could have ignited with the carbon composite materials. However, he did not go into that level of detail in his CNBC comments.

 

"Its never happened before in history, so thats why it took us a while to sort it out, Musk said, adding that SpaceX has been working with NASA, the U.S. Federal Aviation Administration and commercial customers on the accident investigation. This was the toughest puzzle to solve that weve ever had to solve."

 

Musk, though, suggested that the puzzle is now solved and that launches can resume in December. It looks like were going to be back to launching around mid-December, he said. He did not disclose what payload would fly on that return-to-flight mission, or from where the launch would take place.
>

 

 

Oh my. That's quite an interesting (not to mention unprecedented) failure ... wow. LOX turning solid. Then it makes the CC Bottles an incendiary material (as raw Oxygen is known to do to pretty much everything) ... and kaboom. Sounds like there was some moisture infiltration going on somewhere.

 

That's one of the perils of working with LOX, especially under pressure. Not sure what the solution is, as it's out of my realm of understanding at this point in my education. Really, really dangerous stuff and there's a lot of reasons that Engineers don't like working with it, or having to deal with it.

LOX infiltration is normal. 

 

The cold & empty He tank liner contracts slightly, opening a space between it and the carbon overwrap windings via differential expansion/contraction. LOX infiltrates the space and carbon overwrap windings, then is squeezed out when the tank liner pressurizes and expands again. Like wringing a sponge. No problem.

 

Solid O2 (sO2) doesn't squeeze out, and the pressure of the expanding tank liner into the carbon overwrap windings is all the added energy necessary to make the sO2 and carbon overwrap windings exchange atoms and go BOOM!

 

Definitely a stroll into an undiscovered country.

Edited by DocM
  • Like 2

The theory is that flow rates and timing that started the heat loss/engine which chilled the 66°K LOX below its 54.36°K melting point. Solid O2 was the unexpected result. Weird since He has a negative Joule-Thomson coefficient down to 53°K - it warms as it expands.

 

They were testing a new load sequence and, grossly simplifying, happened to hit a magic number where no one expected any numbers at all. Lesson learned, new book chapter.

2 DocM

 

rocketwatcher, in known for you forum, pinpointed issue damnly right -- indeed, why'd there held liquefied He??? my guess is simple: Musk & Co were running an experiment to load a little bit more fuel in the tank. Musk has pushed self in the cursed loop ==>> "reusability" makes dry mass up, then they plays w/ super chilled fuels, then they get into reliability troubles, then rocket falls in the very need to be reconstructed & yet again it runs dry mass mad.

 

P.S. super chilled propellant has been useful only for expendable rockets: because it makes dry mass & dimensions growing, it's useless for reusable schemes.

 

P.P.S. funny to see Musk's absurd about Methane rocket for journey to Mars: LM/LOX tanks need to have damn refrigerator ==>> dry mass & size of that space vehicle shall be bloated insanely.

Nothing absurd about using Methane. In fact, it's the only way we'll be going to Mars and coming back with people. They need to make their fuel on-site while they are there, and Methane is the easiest way to do that given the Martian environment.

 

No problem that the vehicles are big. More power/space to haul things they need to Mars. It's not a problem. :yes: 

3 hours ago, Unobscured Vision said:

No problem that the vehicles are big. More power/space to haul things they need to Mars. It's not a problem.

Mars is completely useless goal ==>> it's relatively far from Sun, has tricky environment & far from Earth as well. Lunar colony has been much more real to orchestrate it within upcoming 30 yrs. Loot at the ISS, it's so close to Earth, but project has plagued that bad.

Regarding Mars -- that is, of course, your opinion and you're free to express that opinion. Lunar Colonies, sure. Let's do a few of those ... why not?

 

Regarding the ISS, I'm not sure where you get the idea that it's been "plagued with problems". In fact, I'd venture to say it's been a resounding success; bridging the divide between, and sparking the evolution (and revolution) of monolithic Government Space Programs and Commercial Space ventures both, performing incredible science and research that could not be done anywhere else, and is serving as a test bed for new technologies. And it's not done yet. It has created tens of thousands of jobs worldwide, and led to the creation of hundreds of thousands of new jobs in other areas of the Aerospace Industry, inspired countless people to pursue careers in the Sciences and Technology sectors all over the world -- and has directly led to the current interest in Space Exploration. I wouldn't call that any kind of failure. It's one of Humanity's greatest achievements.

 

 

5 minutes ago, Unobscured Vision said:

Regarding the ISS, I'm not sure where you get the idea that it's been "plagued with problems"

just read what was supposed to be & compare it w/ what has been. For now, Cosmonautics cannot be just for curiosity's sake, it must chase only damn practical reasons. In our time, Water becomes too expensive to maintain state-of-the-art industry ==>> upcoming reality barely will meet capabilities even for cars.

2 minutes ago, SarK0Y said:

just read what was supposed to be & compare it w/ what has been. For now, Cosmonautics cannot be just for curiosity's sake, it must chase only damn practical reasons. In our time, Water becomes too expensive to maintain state-of-the-art industry ==>> upcoming reality barely will meet capabilities even for cars.

Then Water needs to be made not expensive. There are new discoveries in Science that will render that problem (and more) completely non-issues very shortly -- and the reason these discoveries were even made was thanks to Research and (now in-progress) Development at agencies like Roscosmos, NASA, ESA, CNSA, JAXA and all the Universities and Corporations around the world who are working on these new ideas.

 

You'll like this, @SarK0Y -- Russia's new Federation spacecraft will use some of these new technologies. So will the new Angara rockets. And all of us, around the world, will be cheering you folks in Russia on. It's all on the up-and-up. Budgets have been scaled back everywhere, and it's unfortunate that the ISS didn't get all of the things it was meant to. Perhaps Mir-2 will fulfill those aspirations.

7 hours ago, Unobscured Vision said:

Then Water needs to be made not expensive. There are new discoveries in Science that will render that problem (and more) completely non-issues very shortly -- and the reason these discoveries were even made was thanks to Research and (now in-progress) Development at agencies like Roscosmos, NASA, ESA, CNSA, JAXA and all the Universities and Corporations around the world who are working on these new ideas.

 

You'll like this, @SarK0Y -- Russia's new Federation spacecraft will use some of these new technologies. So will the new Angara rockets. And all of us, around the world, will be cheering you folks in Russia on. It's all on the up-and-up. Budgets have been scaled back everywhere, and it's unfortunate that the ISS didn't get all of the things it was meant to. Perhaps Mir-2 will fulfill those aspirations.

i'd like to share your optimism. But i always have lived the simple Principle ==>> be ready for the Worst & keep Hopes for the Best.

 

P.S.  my Cheers to you, Linux Comrade. windows & m$ as well must die :)))

FYI, Paragon SDC has won the NASA contract for a new water recovery system on ISS. They developed the Commercial Crew ECLSS used in Starliner and Dragon 2 and have a long history with NASA, Boeing, SpaceX and ISS. 

 

http://www.nasa.gov/press-release/nasa-awards-contract-to-increase-water-recovery-on-space-station

 

http://www.paragonsdc.com/paragon-iwp/

 

NASA has awarded Paragon with a Small Business Innovation Research (SBIR) Phase III contract for the patented Ionomer-membrane Water Processor (IWP) System. IWP will provide the platform for up to 98% water recovery in future deep space exploration missions with its initial application planned for installment on the International Space Station (ISS).

 

 

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

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!