This HTML5 document contains 11 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n12http://dbkwik.webdatacommons.org/resource/1zJZra_qVDCr4gj8aQqW1Q==
n13http://dbkwik.webdatacommons.org/ontology/
dctermshttp://purl.org/dc/terms/
rdfshttp://www.w3.org/2000/01/rdf-schema#
n6http://dbkwik.webdatacommons.org/resource/vrzUGUFxWkjvW9sx4fZZ6Q==
n2http://dbkwik.webdatacommons.org/resource/v04O9MTQ2P_5_idRHyXt_A==
n9http://dbkwik.webdatacommons.org/resource/D8dw8TKL0M1ucVFzGFRqxQ==
n5http://dbkwik.webdatacommons.org/nasa/property/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n11http://dbkwik.webdatacommons.org/resource/zuwqhh-Q3rqryxLVp1lCUA==
n8http://dbkwik.webdatacommons.org/resource/IdsyqGr_qdg8ju-G7Gv5gQ==
xsdhhttp://www.w3.org/2001/XMLSchema#
dbrhttp://dbpedia.org/resource/
n7http://dbkwik.webdatacommons.org/resource/6I6FLi29OyciUet5wlYCrQ==
n4http://dbkwik.webdatacommons.org/resource/imBBJSaPcCDu3z0Wf0FWVQ==
Subject Item
n2:
rdfs:label
Shuttle-C
rdfs:comment
The Shuttle-C concept would theoretically cut development costs for a heavy launch vehicle by re-using technology developed for the shuttle program. The proposal involved using, at various times, existing spaceframes, Space Shuttle Main Engines that had reached maintenance lifetime limits, and spare navigation computers. One proposal even involved converting the Columbia or Enterprise into a single-use cargo launcher. Before the loss of Space Shuttle Challenger, NASA had expected about 14 shuttle flights a year. In the aftermath of the Challenger incident, it became clear that this launch rate was not feasible for a variety of reasons. With the Shuttle-C, it was thought that the lower maintenance and safety requirements for the unmanned vehicle would allow a higher flight rate.
owl:sameAs
dbr:Shuttle-C
dcterms:subject
n4: n8: n9: n12:
n5:wikiPageUsesTemplate
n6: n7: n11:
n13:abstract
The Shuttle-C concept would theoretically cut development costs for a heavy launch vehicle by re-using technology developed for the shuttle program. The proposal involved using, at various times, existing spaceframes, Space Shuttle Main Engines that had reached maintenance lifetime limits, and spare navigation computers. One proposal even involved converting the Columbia or Enterprise into a single-use cargo launcher. Before the loss of Space Shuttle Challenger, NASA had expected about 14 shuttle flights a year. In the aftermath of the Challenger incident, it became clear that this launch rate was not feasible for a variety of reasons. With the Shuttle-C, it was thought that the lower maintenance and safety requirements for the unmanned vehicle would allow a higher flight rate. There were two development phases planned. The first consisted of deciding the shape and size of the cargo carrier. NASA studies showed that a small but functional carrier would be most efficient for launches. In the early 1990s, NASA engineers planning a manned mission to Mars included a Shuttle-C design to launch six non reusable 80 ton segments to create two Mars ships in Earth orbit. After President George W. Bush called for the end of the Space Shuttle by 2010, these proposed configurations were put aside. NASA resurrected the idea of the Shuttle-C concept in the form of the Shuttle-Derived Launch Vehicle. The proposal was for a 120 metric tonne payload with an in-line design, now known as Ares V. This design would have been significantly different in layout from Shuttle-C. Shuttle-C comes in various configurations: one variant has three Orbiter main engines, while the other has two. Only one known mock-up of Shuttle-C exists, created by Boeing for engineering development tests in 1989. Shuttle-Derived Heavy Lift Launch Vehicle is another similar proposal based on the Shuttle-C concept which uses existing Space Shuttle systems with a new cargo vehicle, however the system would not be reusable.