Recommended Posts

3 hours ago, DocM said:

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/

 

 

 

 

 

I went to the "Mars Live Experience" last night and Jason Crusan was talking about this being tested on the ISS for future deployment on Mars. 

SpaceX timeline.

 

FH and F9 development end in about 16 months with Block 5. ITS spaceship testing starts in Q3-Q4 2018.  Booster testing in mid-2019, orbital tests in 2020.

 

From the final ITS presentation pdf.

 

ITS-Timeline-1280.jpg

 

 

  • Like 3

Well, there we have it folks! Red Dragon can start in Feb. 2018, ITS can start flying in August-September 2022. :D That's what I'm lining up the beginning of the lines with. Matches up with launch windows nicely.

probability of next explosion is very high -- Musk et Co must stop gambling on deeply cryogenic propellants ==>> DCP needs the brand new EXPENDABLE rocket. DCP is extremely tricky Beast:

 

1. fuel easily goes 3-stated at once  (it's partially solid, partially liquid & partially gaseous) + fluctuates through that states.

2. material becomes fragile.

3. very limited time to keep fuel stable.

4. chemical surprise (like cool fire) can takeover at any Place, at any Time. 

=====================

Don't gamble with that Beast ==>> There never has mercy. :)

Better tell that to Russia since sub-chilled LOX is required on the Russian engined Antares and Soyuz 2-1v.

 

Sub-chilled LOX at 66°K is liquid, not partially solid (54.6°K) and certainly not partially gas because it's well below its 90.188°K boiling point.

 

Something abnormal in the prop and He loads chilled the LOX enough to solidify it (likely γ-phase) inside the COPV overwrap winding, nowhere else. This has been reproduced, with a loud bang, so preventing it from happening again shouldn't be an issue. 

Edited by DocM
17 hours ago, DocM said:

Better tell that to Russia since sub-chilled LOX is required on the Russian engined Antares and Soyuz 2-1v.

 

Sub-chilled LOX at 66°K is liquid, not partially solid (54.6°K) and certainly not partially gas because it's well below its 90.188°K boiling point.

i think they have followed only well-proven process -- if No, Musk-like stories (Boom, baby, Boom) shall become their fate too.

17 hours ago, DocM said:

certainly not partially gas because it's well below its 90.188°K boiling point.

gaseous state may instantly appear in some locations. solid state in a classical form doesn't exist within the over-chilled medium -- super electrical conductivity + other quantum odds make a material transparent for super cooled Atoms/Molecules.

Quote

SpaceX chief Elon Musk called the problem surprising and said it had never been encountered in the history of rocketry.

But it's not completely unexpected. A panel of highly respected aerospace experts told NASA eight months before the accident that the lack of a re-circulation pump aboard the Falcon rocket could be a safety problem.

RELATED: Dramatic Video Shows Moment of SpaceX Explosion

"We are concerned that there may be insufficient pre-cooling of the tank and plumbing with (SpaceX's) current planned oxidizer fill scenario," former astronaut Thomas Stafford and members of the International Space Station Advisory Committee wrote in a December 2015 letter to NASA.

The letter was released on Friday.

"Without re-circulation there may be stratification of oxidizer temperature that will cause a variation in the input conditions to the oxidizer pump," the letter said.

NASA's space shuttles, for example, used a re-circulation system and pressure lines to help keep liquid oxygen temperatures consistent, Mike Leinbach, former shuttle launch director, told Seeker.

"That's key," said Leinbach.

NASA also has a bit of history with liquid oxygen behaving badly with a composite fuel tank, which was developed as part of the experimental X-33 spaceship in the 1990s.

RELATED: SpaceX Rocket, Israeli Satellite Destroyed

"The composite tank experienced cracks when fueled in development tests. Composite was used to save weight. Never could overcome it technically, and contributed a lot to the program demise," Leinbach wrote in an email.

http://www.seeker.com/spacex-elon-musk-falcon-rocket-explosion-launch-pad-accident-2083614822.html

 

In all fairness we'll call this lesson learned. SpaceX will adapt, and the data gathered on this mishap can be used to prevent occurrences like this one in the future; be it Russia or anyone else. Better that it happen before these rockets have Crews on top of them -- in any Space Program. Don't want any loss of life, injury, or setbacks over something that could have been prevented. (Y) 

 

This is another example of how difficult Space is. 

And LOX stratification in a full tank over time wasn't the issue. The tank was only part full. 

 

As to prop and crew loading...

 

1) you load crew first. The rocket is empty so both the flight crew and ground crew are safe. During fueling the flight crew is buttoned up in a capsule surrounded by thermal protection materials, which is also equipped with a powerful launch escape system looking for an excuse to bug out.

 

It would have easily outrun the AMOS-6 event, as fast an event as one can imagime.

 

2) you fuel first, and expose both the flight crew and ground crew to a rocket filled with 500t of propellants looking for an excuse to go boom. If anything goes wrong both crews are SOL; the launch escape system can't fire and the NASA required zip lines are a joke. Puh-lease. Call the coroner.

 

I'll take door #1.

 

How the NAC avoids common sense sometimes amazes me.

 

 

Edited by DocM
  • Like 1
38 minutes ago, DocM said:

As to prop and crew loading...

much better to use Soyuz-like scheme w/ no DCP as well. other schemes could be adopted to crew vehicle, if they have showed due success rate in cargo flights.

 

46 minutes ago, DocM said:

1) you load crew first. The rocket is empty so both the flight crew and ground crew are safe. During fueling the flight crew is buttoned up in a capsule surrounded by thermal protection materials, which is also equipped with a powerful launch escape system looking for an excuse to bug out.

i've had some doubts about escape system of Dragon ==>> engines of capsule must be as far from 2nd stage as possible, otherwise rocket explosion could affect them.

5 minutes ago, SarK0Y said:

second moment, solid boosters work faster, it's better for escape tower.

Why, when the Dragon 2's propulsion system, at full power, can do the same job at the same response time and speed with less weight? No need for an escape tower that potentially can strike the spacecraft (not to mention add additional weight)?

 

Nah, we like the SuperDraco engines. A lot. :yes: 

  • Like 2
43 minutes ago, Unobscured Vision said:

Why, when the Dragon 2's propulsion system, at full power

perhaps theoretically, practically Musk's "optimizations" have proven self unsafe. i remember how Musk's supporters were blackmailing Shuttle. But in practice Shuttle was more reliable/safe & even more cheap as well.

1 hour ago, SarK0Y said:

much better to use Soyuz-like scheme w/ no DCP as well. other schemes could be adopted to crew vehicle, if they have showed due success rate in cargo flights.

Guess you missed the part about other launchers using chilled LOX. If Shuttle had continued it's quite likely it too would have used sub-chilled propellants, NASA was exploring it and saw no deal breakers, and the required pumps are commercially available. In short, quit the FUD.

 

Quote

 

i've had some doubts about escape system of Dragon ==>> engines of capsule must be as far from 2nd stage as possible, otherwise rocket explosion could affect them.

Dragon 2 pad abort test overlaid on AMOS-6 explosion, timed so the SuperDraco ignition happens after the event started. FYI, the SuperDracos reach 100% throttle in 90-100 milliseconds.

 

 

5 minutes ago, DocM said:

Guess you missed the part about other launchers using chilled LOX. If Shuttle had continued it's quite likely it too would have used sub-chilled propellants, NASA was exploring it and saw no deal breakers, and the required pumps are commercially available. In short, quit the FUD.

Yes, it'd be used WELL-PROVEN PROCESS & RD180-like engines for its boosters :rolleyes:

 

10 minutes ago, DocM said:

the SuperDracos reach 100% throttle in 90-100 milliseconds

your pic just shows how engines of Dragon could be affected by such explosion -- normal escape tower stays safe at any scenario.

Guess you missed the part about RD-180 not being used for govt launches after Vulcan flies. Atlas V then needs to be commercially viable, which it will have a problem doing - too many NON-Russian engined options. 

 

The SuperDraco nozzles are covered by pop-off panels before they fire, and so are protected. After they fire their exhaust velocity is fast and voluminous enough to handle thrusting during a hypersonic re-entry for landing on Mars, so a piddling subsonic fireball is nothing. Try harder.

Just a heads up guys, we can't use the "troll" word without getting a warning.

 

We must agree to disagree and move on with our usual thorough science.

 

You guys are smart and know what to do.

 

Thanks much.    :s

14 minutes ago, DocM said:

I could get very creative quoting that first line DD, but I'll restrain myself.

I'm having one of those days where I feel like a bag of hammers, shouldn't be near a keyboard.....:s

5 hours ago, DocM said:

Guess you missed the part about RD-180 not being used for govt launches after Vulcan flies. Atlas V then needs to be commercially viable, which it will have a problem doing - too many NON-Russian engined options. 

vulcan.png

planned:rofl: i'd like to share you some inside -- this rocket will go nowhere or will have RD yet again :) well, mid-12.16?:)

This topic is now closed to further replies.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • 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
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!