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

    • 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!