Continuing…
An obvious one: an upper stage to fit in the Shuttle payload bay to move payloads into higher orbits… 12-hour GPS, GEO or escape. The illustration seems to show a single stage equipped with drop-tanks in a somewhat unusual arrangement.
Continuing…
In 1985, the Space Shuttle program was already about a decade and a half old, the shuttles themselves were already starting to show themselves as “old tech.” It was clear that they would need replacing with a next generation of vehicle, and of course Rockwell wanted to build whatever “Shuttle II” came along… if for no other reason, a Shuttle II would make the Shuttle instantly obsolete and wipe out Rockwell’s Shuttle-based income. It was obvious that such a system would enter service sometime after the year 2000. Not, of course, very long after 2000. That would be nuts.
Interestingly, the illustration Rockwell used for the Next Generation Shuttle was not a Rockwell design, but a NASA-Langley concept for a small “Orbit-on-Demand” vehicle. If you’d like more information on this exact design, boy, have I got a deal for you: it was described and illustrated in US Launch Vehicles Projects #03.
Continuing…
In 1985 Rockwell pondered the business case for a brand-new Saturn V-class expendable booster specifically for the Strategic Defense Initiative (“Star Wars”) program. The heavy payload capability coupled with large diameter payloads would allow the launch of sizable space-based lasers and similar systems. In order for the booster to warrant the high development cost, there would have had to have been a need for the capability, and obviously the USAF hasn’t filed the sky with orbital laser systems.
The launcher illustrated is not one I’ve seen elsewhere. It has three Shuttle boosters, a core seemingly larger in diameter than the Shuttle ET, and a propulsion module (presumably recoverable) with five or six engines, presumably SSMEs.
Continuing…
Rockwell in 1985 considered the business case of small unmanned launchers of 15,000 pounds payload capability. The goal would be low cost ($100/lb of payload delivered to orbit). It’s not clear, at least from this report, if Rockwell had a design of their own under consideration; the illustration included shows only non-Rockwell commercial designs… the “Dolphin” and “Conestoga II” from Space Services, Inc; the “Phoenix” SSTO from Pacific American Launch Systems; the “Space Van” from Transpace Inc. (though what’s shown is just the standard orbiter atop the 747 SCA); the “Constellation” from Star Struck Inc.; the Delta from Transpace Carriers Inc (which appears to be a standard Delta II); the Atlas from Convair; and the “Excalibur” from Truax Engineering, a reduced-scale version of the Aerojet Sea Dragon of two decades earlier.
Continuing…
Moving away from the Space Shuttle, Rockwell looked towards the next generation of manned space vehicle. In this case, a small vehicle with about 10% the payload of the Space Shuttle. The general configuration was used by Rockwell for several small space launch vehicles at about this time, mostly military vehicles. While the payload was nowhere near the STS’s, it would- if it worked as advertised – potentially wreck the business model for the STS program by providing a far cheaper means of getting crew into space.
Continuing…
The OMV survived for a number of years as a number of generally similar concepts: an unmanned vehicle designed to shove satellites around Earth orbit. Several companies proposed vehicles such as this with varying degrees of capability. Some were designed to stay in space and be refueled; others were designed to go up with the Shuttle and then come back down with it for refurb and refueling. I believe the OMV shown here was of that kind.
Continuing…
In 1985 Rockwell considered the business case for a small unmanned research vehicle to be released from the Orbiter payload bay. It would be *something* akin to the X-37, though of an utterly different lifting body configuration.
Also note: this vehicle re-appears later in the report, including a nice three-view of an “operational” version.
As time goes by, I find more and more unhappy customers… not because I’m turning out a crappy product or not filling orders, but because the emails i send out are directed into spam buckets. I *assume* that this is because the emails have one or more, sometimes many, HTML links in them, and the spam filters read them as, well, spam. But an email exchange usually fixes that right up.
One problem that I can’t seem to fix, however, is orders from the “free.fr” email system. Multiple machines, multiple email systems, all messages sent to “free.fr” addresses bounce back as undeliverable because the system has, through presumably the same process as he spam filters, decided that these messages are spam, and has successfully blocked me out. So if you have a free.fr email address and don;t get a reply from me, *ever,* contact me via a *different* email.