Recommended Posts

Here we go. What they're getting awards for - (spacecraft images bottom)

Boeing: CST-100 crew capsule

SpaceX: Dragon capsule launch escape/landing system

Sierra Nevada: Dream Chaser spaceplane

Blue Origin: New Shepard capsule

RELEASE: 11-102

NASA AWARDS NEXT SET OF COMMERCIAL CREW DEVELOPMENT AGREEMENTS

WASHINGTON -- NASA has awarded four Space Act Agreements in the second

round of the agency's Commercial Crew Development (CCDev2) effort.

Each company will receive between $22 million and $92.3 million to

advance commercial crew space transportation system concepts and

mature the design and development of elements of their systems, such

as launch vehicles and spacecraft.

The selectees for CCDev2 awards are:

-- Blue Origin, Kent, Wash., $22 million

-- Sierra Nevada Corporation, Louisville, Colo., $80 million

-- Space Exploration Technologies (SpaceX), Hawthorne, Calif., $75

million

-- The Boeing Company, Houston, $92.3 million

"We're committed to safely transporting U.S. astronauts on

American-made spacecraft and ending the outsourcing of this work to

foreign governments," NASA Administrator Charles Bolden said. "These

agreements are significant milestones in NASA's plans to take

advantage of American ingenuity to get to low-Earth orbit, so we can

concentrate our resources on deep space exploration."

The goal of CCDev2 is to accelerate the availability of U.S.

commercial crew transportation capabilities and reduce the gap in

American human spaceflight capability. Through this activity, NASA

also may be able to spur economic growth as potential new space

markets are created.

Once developed, crew transportation capabilities could become

available to commercial and government customers.

"The next American-flagged vehicle to carry our astronauts into space

is going to be a U.S. commercial provider," said Ed Mango, NASA's

Commercial Crew Program manager. "The partnerships NASA is forming

with industry will support the development of multiple American

systems capable of providing future access to low-Earth orbit."

These awards are a continuation of NASA's CCDev initiatives, which

began in 2009 to stimulate efforts within U.S. industry to develop

and demonstrate human spaceflight capabilities. For more information

about NASA's Commercial Crew Program, visit:

Boeing CST-100 (partnered with Bigelow Aerospace)

CST-100.jpg

SpaceX Dragon (already flying)

fancy-dragon3_640x480.jpg

Sierra Nevada Dream Chaser (partnered with Northrop Grumman & Virgin Galactic)

Sierra+Nevada+Dream_Chaser.jpg

Blue Origin New Shepard (somewhat black project)

A513.jpg

Details -

Sierra Nevada:

system requirements review

canted airfoil fin selection

cockpit based flight simulator

vehicle avionics integration laboratory

system defniition review

flight control integration laboratory

ETA structure delivery

separation system test

preliminary design review for Dream Chaser

optional milestones: materials testing captive carry and ETA landing gear drop tests, ETA captive carry flight test, wind tunnel testing, dream chaser handling qualities evaluation, main RCS test, two hybrid rocket motor test firing, thrust vector control test, ETA captive carry flight test readiness review, ETA free flight test

Blue Origin:

* Space Vehicle Design: space vehicle system requirements review

* Pusher escape Risk Reduction: pusher escape ground firing, pusher escape pad escape test (optional milestones: pusher escape max-Q sled test calibration run, pusher escape mas-Q sled test egress run)

* RBS (reusable booster system) engine risk reduction: engine thrust chamber assembly test at Stennis (optional: engine pump cold gas drive test, engine pump hot gas drive test) [as an aside, apparently the RBF is a 100klbf restartable hydrolox engine)

Boeing:

launch abort engine fabrication & hot fire test demonstration

landing air bag drop demonstration #1

phase I wind tunnel tests

interim design review - 4

parachute drop tests demonstration

SM propellant tank development test

LV EDS/ASIF interface simulation test

Preliminary design review

SpaceX:

launch abort system propulsion conceptual design review

design status review 1 (for Falcon 9/Dragon crew transportation system)

LAS propulsion components PDR

crew accommodation concept prototype and in situ trial (internally-funded by SpaceX, NASA astronauts invited to try crew accomodations and give feedback)

DSR 2

crew accommodation concept delta-prototype and in-situ trial 2

LAS propulsion component test articles complete

LAS propulsion component initial test cycle

concept baseline review

Sierra Nevada hasn't provided a timeline graphic for Dream Chaser's timeline, but drop tests of the full size test bird, analogous to the Shuttle Enterprise, will perform drop-test flights in 2012 - likely using the Virgin Galactic White Knight Two serving as its mothership. A launch is possible atop an Atlas V in 2014.

Blue Origin is, as usual, cryptic other than the test flight will be on an Atlas V and later flights on their own reusable booster.

  • 2 months later...

CCDev is now starting level 2 (CCDev-2) and is issuing bi-monthly reports. The most recent is here -

http://www.nasa.gov/pdf/563409main_201106_Commercial_60day_Report_508.pdf

Highlights:

Boeing CST-100: Delta Systems Design Review completed, Full-scale landing airbag test this summer.

SpaceX Dragon: abort system design and supporting paper gets sent to NASA this month (July 2011). Cabin hardware (seats, controls, and enhanced life support) development in parallel.

SNC Dream Chaser: system requirements review, preliminary design review, airfoil selection

Blue Origin SV: vehicle design, pusher launch escape, and reusable booster.

No, it's TSTO - two stages.

The only SSTO spacecraft that's been proposed was the Lockheed Martin VentureStar spaceplane and it's X-33 testbed, both of which used the revolutionary Linear Aerospike engine. They were cancelled by NASA & Congress in 2001 during X-33's construction; it was too big a threat to the Space Shuttle establishment.

VentureStar was shown in the opening credits for Star Trek: Enterprise and was also referenced in Avatar.

Left to right: X-33, VentureStar and Space Shuttle

x33_venturestar_shuttle.jpg

oh come on Doc, you know i love the VentureStar, it's basically my Valkyrie shuttle, and yes the name was used in the Avatar ISV...that was a nice touch i thought. is there a chance the VS will be resurrected now the shuttle is retired? will the aeospike engine magically work to spec now? please?

When who is scheduled to do what - subject to change, of course

2011:

Dragon C2 cargo - ISS approach (optional C3 - ISS docking)

2012:

Dragon C3 cargo - ISS docking (if blended C2/C3 isn't done)

Dream Chaser drop tests (from WhiteKnightTwo)

Cygnus C1 cargo first test flight - ISS approach

Falcon Heavy delivered to Vandenberg AFB SLC-4E

Dragon cargo to ISS goes operational - 12 flights

Cygnus cargo to ISS goes operational - 8 flights

2013:

Falcon Heavy first flight

Dream Chaser unmanned flight

2014:

CST100 unmanned flight

Dragon manned flight

Dream Chaser manned flight

2016:

NASA MPCV* unmaned flight (if NASA's SLS** booster is ready)

* Multi-Purpose Crew Vehicle

** Space Launch System ultra-heavy lift rocket

MPCV is what's supposed to take us to the moon and Mars, right? So why not just launch it to the moon 2016?

EDIT: i liked your Buck Rogers joke, but i intentionally avoided it...the Venture Star cancellation really saddens me...such a beautiful ship!

Orion/MPCV is what's left of the Constellation lunar program, an exercise in how NOT to do things.

Constellation was finally killed last year but its supporters keep trying to resurrect it, and MPCV is part of that in spite of Dragon being designed to be just as capable for beyond Earth orbit missions. Its launcher, SLS, is late and getting later as Constellation advocates try to resurrect Ares V as the design goal in spite of good reasons not to ($$$$$$)

Stupidity & greed.

The correct way to do heavy lift is to have a competition like COTS for cargo and CCDev for crew; let SpaceX's Falcon X/XX concept etc. take on all comers. The problem is that this puts the old-paradigm high-cost systems like shuttle-derived (SLS/Ares V, Direct etc) at a cost disadvantage, which doesn't sit well with congressmen & senators who have shuttle-based NASA centers and suppliers in their states/districts.

NASA and United Launch Associates (ULA - a Lockheed/Boeing joint venture) have signed a Space Act Agreement for the human-rating of the Atlas V booster. This agreement is unfunded, but it will allow ULA to use NASA's labs to develop, simulate and test towards this end. ULA's dime.

Atlas V is to be the front line launcher for the SNC Dream Chaser, Blue Origin's Space Vehicle, and Boeing's CST-100.

The big question is if the $120M+ cost of Atlas V will be lowered enough to compete with Falcon 9's $59M - $69M price point. The current price is the same as a cross-fed Falcon Heavy, a much more powerful system set to start flying in 2013. Massive overkill for this purpose, but still....

Atlas V and CST-100

atlas402.jpg

Atlas V and Dream Chaser

atlas_dreamchaser.jpg

every time you feel hostile towards spaceplanes, just sing the theme song from Star Blazers to yourself, and picture the Argo/Yamato flying through space with that huge citadel on top. you'll get in the spirit and won't hate spaceplanes any more.

"we're off to outer space, we're leaving mother Earth, to save the human race..."

As I'v said, they have their uses including emergency medical and delicate experiment/materials return, but for now not the routine up/down stuff.

That said, I'm prepping a post that may make you happier. It's not near term but it is commercial and very real.

  • 4 weeks later...

CCDev 60 day update #2

http://www.nasa.gov/pdf/580957main_August%202011_CSD%2060%20Day%20Report_508.pdf

Notables:

The main potential delay for SpaceX's COTS-2/3 flight actually docking at ISS is not them but delays in software updates at ISS itself.

SpaceX will be testing at White Sands, presumably the Super Draco thrusters.

Blue Origin will be testing engines at Stennis.

SNC at Langley, KSC and JSC.

Boeing at Langley.

Aside-

SpaceX is testing the Super Draco's at White Sands because that center is set up to handle engine testing with toxic hypergolic fuels; nitrogen tetroxide and hydrazine - the same as most other spacecraft. The plan is to eventually transition to the NOBFx monopropellant if its ignition speed is fast enough for use in launch abort systems.

NOBFx = Nitrous Oxide Fuel Blend x, a FireStar Technologies propitiatory mix of nitrous oxide with a fuel and blending agents in various proportions (the "x") according to the mission. By storing both oxidizer and fuel in a stabilized mix it simplifies the plumbing considerably and it's not anywhere near as toxic as hypergolics. It gets tested at ISS in 2012,

http://www.firestar-engineering.com/index.html

NOFBx advantages -

  • constituents are widely available from chemical suppliers, inexpensive and safe to handle.
    can be transported and handled without undue precautions or hazards.
    effluents are non-toxic and produces no accumulated deposits or contamination.
    propulsion system has high Isp (320-340 s) ? similar to the most common bi-propellant.
    has far better lift capability than the current workhorse monopropellant, hydrazine.
    is tolerant to a wide thermal range; storable at room temperature on the ground and is Space-storable.
    [is projected to] lower cost compared to existing propulsion systems of comparable performance.
    is monopropellant, which significantly reduces the need for auxiliary hardware, saving cost, volume, and mass for launch systems.
    utilizes cool running thrusters that dramatically reduce thermal design challenges.
    burns in liquid, gas, and two-phase flow.
    does not have the materials compatibility constraints of traditional hypergolic systems.

  • 2 months later...

Boeing will be using one of the old Shuttle processing facilities to prep & refurbish their CST-100 CCDev entry -

Link....

Boeing signs lease for NASA's space shuttle hangar

CAPE CANAVERAL, Fla. ? The Boeing Co. plans to build space taxis at a mothballed space shuttle processing hangar at NASA's Kennedy Space Center in central Florida.

On Monday, NASA officials and company executives confirmed that Boeing has reached an agreement with Space Florida, a state-backed agency working to expand space-related businesses in Florida, to lease Orbiter Processing Facility 3 at the center.

Boeing will also place the headquarters of its commercial crew operation in Florida, said John Mulholland, vice president and program manager for the company's effort.

"We will launch from right here, on Florida's Space Coast," Mullholland said.

The agreement was hailed by state and federal officials during a news conference inside the Orbiter Processing Facility. "Ladies and gentlemen, the dream is alive," said Sen. Bill Nelson, D-Fla.

NASA Deputy Administrator Lori Garver said the agreement would give a "major boost" to the space agency's commercialization efforts. She noted that Boeing and Space Florida were already sprucing up the shuttle's old hangar.

"I love what you've done to the place so far," she joked.

Kennedy Space Center is drafting a master plan for a revamped spaceport that, in addition to supporting future NASA spacecraft, will host commercial, military and international customers.

Boeing is one of four companies NASA is sponsoring to develop spaceships that can ferry astronauts to the International Space Station, a $100 billion project of 16 nations orbiting 240 miles (385 kilometers) above Earth.

With the retirement of NASA's space shuttles this summer, the United States is currently dependent on Russia to fly crews to the orbital outpost, at a cost of about $350 million per year.

NASA hopes to be able to buy rides from U.S. firms before the end of 2016.

Boeing's proposed space taxi is a seven-seat capsule called the CST-100, which would launch on an Atlas 5 rocket.

The company also has an agreement to provide rides for clients of Bigelow Aerospace, which is developing privately-owned inflatable space habitats for commercial and government lease.

NASA has spent $388 million to bolster the development of passenger spaceships. Boeing won $18 million in the program's first round of financing and $92.3 million in the second phase, which is currently under way.

The U.S. space agency this year added $20.6 million in options to Boeing's agreement if the company can complete additional milestones in the CST-100 development.

The Obama administration is requesting $850 million for the program for the fiscal year that began Oct. 1. Bills pending in the U.S. House of Representatives and Senate would cut that to $312 million and $500 million, respectively.

OPF-3

5936079070_d2590e369e.jpg

  • 1 month later...

Q1 2012 Commercial Crew Development milestones -

Sierra Nevada Corp. (SNC) Dream Chaser

- Engineering Test Article (ETA) Structure Delivery

- Captive Carry Interface & ETA Landing Gear Drop Tests (read: attachment for the Virgin WhiteKnightTwo mothership)

- Separation System Test

- ETA Captive Carry Flight Test Readiness Review

Boeing CST-100

- Launch Vehicle Emergency Detection System/Avionics System Integration Facility Interface Simulation Test Phase 2

- Launch Abort Engine (LAE) Fabrication and Hot Fire Test Demo

SpaceX Dragon

- Crew Accommodation Concept Prototype and In-Situ Trial 1 (read: seats, control panel layouts & controls)

- Crew Accommodation Concept Delta-Prototype and In-Situ Trial 2

(launch abort/DragonRider test fire in Q2)

Blue Origin SV

- Pusher Escape Ground Firing (read: launch abort system)

- Pusher Escape Test Vehicle #1 Shipment

United Launch Alliance (ULA) human-rated Atlas V launcher

- No milestone in Q1

Alliant Techsystems Inc. (ATK) Liberty launcher (unfunded)

- Launch System Initial System Design (ISD)

- Technical Interchange Meeting 2

- Program Status Review (PSR)

Excalibur Almaz Incorporated (EAI) (unfunded)

- System Requirements Review

- Launch Vehicle Compatibility Review

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

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