Recommended Posts

22 hours ago, DocM said:

This is going to put serious heat on ULA/Boeing/LockMart as regards Vulcan "reuse" by way of parachuting the engine bay & engines, catching it with a chopper. This design still needs solid boosters.

I see 3 possible outcomes for such a stupid idea.

 

1.  No pilot will agree to attempting something so monstrously stupid, nor will the FAA or other similar organisations

2.  A clean miss

3.  A dead chopper crew

 

Such retrievals were done of US Corona spysat film return capsules, and the Ryan Firebee recon drones over SE Asia from 1964-1975. Thousands of missions.

 

The Vulcan engine bay would be larger, but the principle is proven. Just a bit costly and a logistical nightmare vs. doing as God and Robert A. Heinlein intended ;)

 

140114-F-DW547-008.JPG

 

Ryan Firebee

140114-F-DW547-004.JPG

 

Go to 3:45 of this video to see a chopper snatch a parachuting drone

 

 

Edited by DocM
4 hours ago, PaulRocket said:

Is it correct that a Dragon costs about $50-60M? 

Under the CRS Round 1 contract SpaceX was allocated 12 missions at a cost of $1.6 billion, or about $133.3 million a mission. Musk has said about half of this was the cost of Dragon 1, so about $67.7 million.

 

This contract was extended twice, first adding 3 missions then another 5 for a total of 20 CRS missions and at each an inflation factor was applied.  These missions now cost about $140 million each.

 

SpaceX, OrbitalATK and Sierra Nevada were each awarded 6 initial CRS Round 2 missions with SpaceX getting the highest evaluation score and per mission award, but that amount isn't accurately known yet.  The total CRS Round 2 contract for all 3 providers maxes out at $14 billion, counting 6 missions each and the likely additional missions past those, and as stated SpaceX will get the largest chunk.

 

All SpaceX CRS Round 2 missions will fly using Dragon 2, and the baseline mission includes propulsive landings at LZ-1.

 

What's interesting about CRS Round 2 is that both Boeing's CST-100 Starliner and Lockheed's entry were eliminated early. Starliner couldn't hold enough pressurized cargo/mission, and Lockheed was eliminated for high costs and mission complexity - it required 2 vehicles.

 

 

Edited by DocM
  • Like 2
20 minutes ago, DocM said:

Under the CRS Round 1 contract SpaceX was allocated 12 missions at a cost of $1.6 billion, or about $133.3 million a mission. Musk has said about half of this was the cost of Dragon 1, so about $67.7 million.

 

This contract was extended twice, first adding 3 missions then another 5 for a total of 20 CRS missions and at each an inflation factor was applied.  These missions now cost about $140 million each.

 

SpaceX, OrbitalATK and Sierra Nevada were each awarded 6 initial CRS Round 2 missions with SpaceX getting the highest evaluation score and per mission award, but that amount isn't accurately known yet.  The total CRS Round 2 contract for all 3 providers maxes out at $14 billion, counting 6 missions each and the likely additional missions past those, and as stated SpaceX will get the largest chunk.

 

All SpaceX CRS Round 2 missions will fly using Dragon 2, and the baseline mission includes propulsive landings at LZ-1.

 

What's interesting about CRS Round 2 is that both Boeing's CST-100 Starliner and Lockheed's entry were eliminated early. Starliner couldn't hold enough pressurized cargo/mission, and Lockheed was eliminated for high costs and mission complexity - it required 2 vehicles.

 

 

Thanks for the answer! Looks like SpaceX will have a lot of Dragons sitting around waiting for being reused on some commercial missions. 

Regarding 24h refurbishment time, do we know if SpaceX is still planning on getting Brownsville up and running by 2018? I imagine this is quite important since they will probably be limited to one launch per 2 weeks at the Cape...

2018 still appears to be "the plan," and things are moving there with road improvements, lots of surveying, and the STARGATE tracking/R&D building having gone up. One 10 meter tracking dish is up, and anothers base has been poured. More land acquisitions too. We'll likely see major cement work soon.

 

And keep in mind: this is a $100 million project, and a lot of it has been soil preparation - as in drying it out. This takes installing thousands of deep "wick drains," a lot of dirt piled on top for weight, and time.

Edited by DocM
  • Like 2

This video seems so prescient 6 years later....and the music choice of Uprising (Muse) was absolutely perfect.

 

CC: Richard Shelby

 

 

 

>

They will not force us
They will stop degrading us
They will not control us
We will be victorious
(So come on)

  • Like 2

They've already lost. There's so much coming down the pipe in the next two years that it would take OldSpace probably twenty years to get to this point IF they could be bothered to try. Let alone have any kind of forward-thinking or risk-taking in the underlying technologies that have gotten SpaceX this far already.

 

Nope. I keep saying this, but it's really the only thing that can sum it up. OldSpace are really just here for the Participation trophies at this point. The best they can do is to latch onto one of the NewSpace companies like leeches (and they have, in fact -- Blue Origin) and try to survive. OldSpace is at the mercy of NewSpace, make no mistake. They had their chance to do things their way, develop their own engine and completely pish-poshed the funding. Now they've missed the train. And the plane. And the boat. And finally the rocket.

 

The AR-1 engine, while halfway decent, is really, really out of step and out of touch with current technology -- and still three years from being ready for anything. It should have been ready TEN years ago when it was REALLY needed.

 

And they'd better thank their lucky stars that Elon and Bezos aren't absolute sharks ... because if the tables were turned, NewSpace would have already been plowed under without a second glance.

  • Like 2

I completely agree with your assessment, I was actually thinking about the other new space companies, Blue Origin seems to have something to show, but stuff like Orbital, I'm not so sure about, and Virgin Galactic seems to be postponing indefinitely, while their product slowly becomes less and less impressive in comparison to the competitors tech and prices. What about the Dream chaser will there still be a market for that one when the Dragon 2 is flying?
We don't need a new monopoly situation, even if it is SpaceX sitting on the monopoly.

  • Like 1
1 hour ago, SALSN said:

>

Whatabout the Dream chaser will there still be a market for that one when the Dragon 2 is flying?
>

Dream Chaser has a CRS Round 2 ISS cargo contract, joining SpaceX and OrbitalATK, and is ramping to another glide/landing test.  Part of this development is a big cargo Trunk to meet the CRS Round 2 volume requirements. 

 

Fun fact: Dream Chaser beat out both Boeing and Lockheed Martin in the competition.

 

They're also working with Germany and a few others on DC4E, Dream Chaser for Europe, to fly on Ariane. This should let them fly to either the ISS or Chinese station. Part of this work is that Dream Chaser would use a European built version of the International Docking Adapter. 

 

CRS R2 unmanned Dream Chaser

maxresdefault.jpg

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'.
  • 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
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!