Search NASA⌕ Search

SEARCH · Search NASA

Results for “Constellation program”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 253 records · Page 14

Rationale, Scenarios, and Profiles for the Application of the Internet Protocol Suite (IPS) in Space Operations

This greenbook captures some of the current, planned and possible future uses of the Internet Protocol (IP) as part of Space Operations. It attempts to describe how the Internet Protocol is used in specific scenarios. Of primary focus is low-earth-orbit space operations, which is referred to here as the design reference mission (DRM). This is because most of the program experience drawn upon derives from this type of mission. Application profiles are provided. This includes parameter settings programs have proposed for sending IP datagrams over CCSDS links, the minimal subsets and features of the IP protocol suite and applications expected for interoperability between projects, and the configuration, operations and maintenance of these IP functions. Of special interest is capturing the lessons learned from the Constellation Program in this area, since that program included a fairly ambitious use of the Internet Protocol.

Benbenek, Daniel B.↗

Altair Lander Life Support: Design Analysis Cycles 4 and 5

Life support systems are a critical part of human exploration beyond low earth orbit. NASA s Altair Lunar Lander team is pursuing efficient solutions to the technical challenges of human spaceflight. Life support design efforts up through Design Analysis Cycle (DAC) 4 focused on finding lightweight and reliable solutions for the Sortie and Outpost missions within the Constellation Program. In DAC-4 and later follow on work, changes were made to add functionality for new requirements accepted by the Altair project, and to update the design as knowledge about certain issues or hardware matured. In DAC-5, the Altair project began to consider mission architectures outside the Constellation baseline. Selecting the optimal life support system design is very sensitive to mission duration. When the mission goals and architecture change several trade studies must be conducted to determine the appropriate design. Finally, several areas of work developed through the Altair project may be applicable to other vehicle concepts for microgravity missions. Maturing the Altair life support system related analysis, design, and requirements can provide important information for developers of a wide range of other human vehicles.

Anderson, Molly↗

Altair Lander Life Support: Design Analysis Cycles 4 and 5

Life support systems are a critical part of human exploration beyond low earth orbit. NASA s Altair Lunar Lander team is pursuing efficient solutions to the technical challenges of human spaceflight. Life support design efforts up through Design Analysis Cycle (DAC) 4 focused on finding lightweight and reliable solutions for the Sortie and Outpost missions within the Constellation Program. In DAC-4 and later follow on work, changes were made to add functionality for new requirements accepted by the Altair project, and to update the design as knowledge about certain issues or hardware matured. In DAC-5, the Altair project began to consider mission architectures outside the Constellation baseline. Selecting the optimal life support system design is very sensitive to mission duration. When the mission goals and architecture change several trade studies must be conducted to determine the appropriate design. Finally, several areas of work developed through the Altair project may be applicable to other vehicle concepts for microgravity missions. Maturing the Altair life support system related analysis, design, and requirements can provide important information for developers of a wide range of other human vehicles.

Anderson, Molly↗

Habitability Insights from Selected NASA Habitat Mockup Testing Campaigns

In 2004, President Bush announced his Vision for Space Exploration, causing NASA to look beyond Low Earth Orbit. While the resulting Constellation Program was cancelled, a focus on expanding beyond LEO has continued to this day. Since 2005, multiple habitat concepts have been developed for the Moon, Mars, or deep space. Some of these concepts were mocked up in virtual or physical form and used in habitability testing campaigns. This paper provides an understanding of the value of two decades of habitability testing and highlights key insights obtainable only through human interaction with a vehicle concept design. The focus of this paper will be limited to primarily habitation work conducted primarily at or by the Johnson Space Center in support of active space habitat development programs or studies and is further limited to fixed habitats and will not discuss mobile habitats such as pressurized rovers.

Lunar Surface Habitation↗

Austere Human Missions to Mars

The Design Reference Architecture 5 (DRA 5) is the most recent concept developed by NASA to send humans to Mars in the 2030 time frame using Constellation Program elements. DRA 5 is optimized to meet a specific set of requirements that would provide for a robust exploration program to deliver a new six-person crew at each biennial Mars opportunity and provide for power and infrastructure to maintain a highly capable continuing human presence on Mars. This paper examines an alternate architecture that is scaled back from DRA 5 and might offer lower development cost, lower flight cost, and lower development risk. It is recognized that a mission set using this approach would not meet all the current Constellation Mars mission requirements; however, this 'austere' architecture may represent a minimum mission set that would be acceptable from a science and exploration standpoint. The austere approach is driven by a philosophy of minimizing high risk or high cost technology development and maximizing development and production commonality in order to achieve a program that could be sustained in a flat-funded budget environment. Key features that would enable a lower technology implementation are as follows: using a blunt-body entry vehicle having no deployable decelerators, utilizing aerobraking rather than aerocapture for placing the crewed element into low Mars orbit, avoiding the use of liquid hydrogen with its low temperature and large volume issues, using standard bipropellant propulsion for the landers and ascent vehicle, and using radioisotope surface power systems rather than a nuclear reactor or large area deployable solar arrays. Flat funding within the expected NASA budget for a sustained program could be facilitated by alternating cargo and crew launches for the biennial Mars opportunities. This would result in two assembled vehicles leaving Earth orbit for Mars per Mars opportunity. The first opportunity would send two cargo landers to the Mars surface to preposition a habitat, supplies, and exploration equipment. The next opportunity, two years later, would send to Mars orbit 1) a lander with a Mars Ascent Vehicle (MAV) and 2) a crewed Mars Transit Habitat with an Orion CEV for Earth return. The following opportunity, two years after the first crew, would go back to cargo-only launches. This alternation of cargo and crew opportunities results in a sustainable launch rate of six Ares V launches every two years. It is notable that four of the six launches per Mars opportunity are identical, build-to-print, Tran-Mars Injection stages. This type of production rate could lend itself well to a COTStype service provider, and would make it feasible to have a live spare in place in the event of a single launch failure.

landers↗

Investigation of Boundary Conditions for Flexible Multibody Spacecraft Dynamics

In support of both the Space Shuttle and International Space Station programs, a set of generic multibody dynamics algorithms integrated within the Trick simulation environment have addressed the variety of on-orbit manipulator simulation requirements for engineering analysis, procedures development and crew familiarization/training at the NASA Johnson Space Center (JSC). Enhancements to these dynamics algorithms are now being driven by a new set of Constellation program requirements for flexible multibody spacecraft simulation. One particular issue that has been discussed within the NASA community is the assumption of cantilever-type flexible body boundary conditions. This assumption has been commonly utilized within manipulator multibody dynamics formulations as it simplifies the computation of relative motion for articulated flexible topologies. Moreover, its use for modeling of space-based manipulators such as the Shuttle Remote Manipulator System (SRMS) and Space Station Remote Manipulator System (SSRMS) has been extensively validated against flight data. For more general flexible spacecraft applications, however, the assumption of cantilever-type boundary conditions may not be sufficient. This paper describes the boundary condition assumptions that were used in the original formulation, demonstrates that this formulation can be augmented to accommodate systems in which the assumption of cantilever boundary conditions no longer applies, and verifies the approach through comparison with an independent model previously validated against experimental hardware test data from a spacecraft flexible dynamics emulator.

Boundary-value problems↗

Integrating Engineering Data Systems for NASA Spaceflight Projects

NASA has a large range of custom-built and commercial data systems to support spaceflight programs. Some of the systems are re-used by many programs and projects over time. Management and systems engineering processes require integration of data across many of these systems, a difficult problem given the widely diverse nature of system interfaces and data models. This paper describes an ongoing project to use a central data model with a web services architecture to support the integration and access of linked data across engineering functions for multiple NASA programs. The work involves the implementation of a web service-based middleware system called Data Aggregator to bring together data from a variety of systems to support space exploration. Data Aggregator includes a central data model registry for storing and managing links between the data in disparate systems. Initially developed for NASA's Constellation Program needs, Data Aggregator is currently being repurposed to support the International Space Station Program and new NASA projects with processes that involve significant aggregating and linking of data. This change in user needs led to development of a more streamlined data model registry for Data Aggregator in order to simplify adding new project application data as well as standardization of the Data Aggregator query syntax to facilitate cross-application querying by client applications. This paper documents the approach from a set of stand-alone engineering systems from which data are manually retrieved and integrated, to a web of engineering data systems from which the latest data are automatically retrieved and more quickly and accurately integrated. This paper includes the lessons learned through these efforts, including the design and development of a service-oriented architecture and the evolution of the data model registry approaches as the effort continues to evolve and adapt to support multiple NASA programs and priorities.

Carvalho, Robert E.↗

A Case Study Using Modeling and Simulation to Predict Logistics Supply Chain Issues

Optimization of critical supply chains to deliver thousands of parts, materials, sub-assemblies, and vehicle structures as needed is vital to the success of the Constellation Program. Thorough analysis needs to be performed on the integrated supply chain processes to plan, source, make, deliver, and return critical items efficiently. Process modeling provides simulation technology-based, predictive solutions for supply chain problems which enable decision makers to reduce costs, accelerate cycle time and improve business performance. For example, United Space Alliance, LLC utilized this approach in late 2006 to build simulation models that recreated shuttle orbiter thruster failures and predicted the potential impact of thruster removals on logistics spare assets. The main objective was the early identification of possible problems in providing thruster spares for the remainder of the Shuttle Flight Manifest. After extensive analysis the model results were used to quantify potential problems and led to improvement actions in the supply chain. Similarly the proper modeling and analysis of Constellation parts, materials, operations, and information flows will help ensure the efficiency of the critical logistics supply chains and the overall success of the program.

Tucker, David A.↗

Exploration Life Support Technology Development for Lunar Missions

Exploration Life Support (ELS) is one of NASA's Exploration Technology Development Projects. ELS plans, coordinates and implements the development of new life support technologies for human exploration missions as outlined in NASA's Vision for Space Exploration. ELS technology development currently supports three major projects of the Constellation Program - the Orion Crew Exploration Vehicle (CEV), the Altair Lunar Lander and Lunar Surface Systems. ELS content includes Air Revitalization Systems (ARS), Water Recovery Systems (WRS), Waste Management Systems (WMS), Habitation Engineering, Systems Integration, Modeling and Analysis (SIMA), and Validation and Testing. The primary goal of the ELS project is to provide different technology options to Constellation which fill gaps or provide substantial improvements over the state-of-the-art in life support systems. Since the Constellation missions are so challenging, mass, power, and volume must be reduced from Space Shuttle and Space Station technologies. Systems engineering analysis also optimizes the overall architecture by considering all interfaces with the life support system and potential for reduction or reuse of resources. For long duration missions, technologies which aid in closure of air and water loops with increased reliability are essential as well as techniques to minimize or deal with waste. The ELS project utilizes in-house efforts at five NASA centers, aerospace industry contracts, Small Business Innovative Research contracts and other means to develop advanced life support technologies. Testing, analysis and reduced gravity flight experiments are also conducted at the NASA field centers. This paper gives a current status of technologies under development by ELS and relates them to the Constellation customers who will eventually use them.

Ewert, Michael K.↗

ATK Launch Vehicle (ALV-X1) Liftoff Acoustic Environments: Prediction vs. Measurement

The ATK Launch Vehicle (ALV-X1) provided an opportunity to measure liftoff acoustic noise data. NASA Marshall Space Flight Center (MSFC) engineers were interested in the ALV-X1 launch because the First Stage motor and launch pad conditions, including a relativity short deflector ducting, provide a potential analogue to future Ares I launches. This paper presents the measured liftoff acoustics on the vehicle and tower. Those measured results are compared to predictions based upon the method described in NASA SP-8072 "Acoustic Loads Generated by the Propulsion System" and the Vehicle Acoustic Environment Prediction Program (VAEPP) which was developed by MSFC acoustics engineers. One-third octave band sound pressure levels will be presented. This data is useful for the ALV-X1 in validating the pre-launch environments and loads predictions. Additionally, the ALV-X1 liftoff data can be scaled to define liftoff environments for the NASA Constellation program Ares vehicles. Vehicle liftoff noise is caused by the supersonic jet flow interaction with surrounding atmosphere or more simply, jet noise. As the vehicle's First Stage motor is ignited, an acoustic noise field is generated by the exhaust. This noise field persists due to the supersonic jet noise and reflections from the launch pad and tower, then changes as the vehicle begins to liftoff from the launch pad. Depending on launch pad and adjacent tower configurations, the liftoff noise is generally very high near the nozzle exit and decreases rapidly away from the nozzle. The liftoff acoustic time range of interest is typically 0 to 20 seconds after ignition. The exhaust plume thermo-fluid mechanics generates sound at approx.10 Hz to 20 kHz. Liftoff acoustic noise is usually the most severe dynamic environment for a launch vehicle or payload in the mid to high frequency range (approx.50 to 2000 Hz). This noise environment can induce high-level vibrations along the external surfaces of the vehicle and surrounding launch facility structures. The acoustic pressure fluctuations will induce severe vibrations in relatively large lightweight structures. Consequently, there is the potential for failure of the structure or attached electrical components. Due to these potential failures, the liftoff acoustic noise is one of the noise source inputs used to determine the vibro-acoustic qualification environment for a launch vehicle and its components.

Houston, Janice↗

The Lunar Mapping and Modeling Project

LMMP was initiated in 2007 to help in making the anticipated results of the LRO spacecraft useful and accessible to Constellation. The LMMP is managing and developing a suite of lunar mapping and modeling tools and products that support the Constellation Program (CxP) and other lunar exploration activities. In addition to the LRO Principal Investigators, relevant activities and expertise that had already been funded by NASA was identified at ARC, CRREL (Army Cold Regions Research & Engineering Laboratory), GSFC, JPL, & USGS. LMMP is a cost capped, design-to-cost project (Project budget was established prior to obtaining Constellation needs)

Noble, Sarah↗

Operational Lessons Learned from the Ares I-X Flight Test

The Ares I-X flight test, launched in 2009, is the first test of the Ares I crew launch vehicle. This development flight test evaluated the flight dynamics, roll control, and separation events, but also provided early insights into logistical, stacking, launch, and recovery operations for Ares I. Operational lessons will be especially important for NASA as the agency makes the transition from the Space Shuttle to the Constellation Program, which is designed to be less labor-intensive. The mission team itself comprised only 700 individuals over the life of the project compared to the thousands involved in Shuttle and Apollo missions; while missions to and beyond low-Earth orbit obviously will require additional personnel, this lean approach will serve as a model for future Constellation missions. To prepare for Ares I-X, vehicle stacking and launch infrastructure had to be modified at Kennedy Space Center's Vehicle Assembly Building (VAB) as well as Launch Complex (LC) 39B. In the VAB, several platforms and other structures designed for the Shuttle s configuration had to be removed to accommodate the in-line, much taller Ares I-X. Vehicle preparation activities resulted in delays, but also in lessons learned for ground operations personnel, including hardware deliveries, cable routing, transferred work and custodial paperwork. Ares I-X also proved to be a resource challenge, as individuals and ground service equipment (GSE) supporting the mission also were required for Shuttle or Atlas V operations at LC 40/41 at Cape Canaveral Air Force Station. At LC 39B, several Shuttle-specific access arms were removed and others were added to accommodate the in-line Ares vehicle. Ground command, control, and communication (GC3) hardware was incorporated into the Mobile Launcher Platform (MLP). The lightning protection system at LC 39B was replaced by a trio of 600-foot-tall towers connected by a catenary wire to account for the much greater height of the vehicle. Like Shuttle, Ares I-X will be stacked on a MLP and rolled out to the pad on a Saturn-era crawler-transporter. While Ares I-X was only held in place by the four hold-down posts on its aft skirt during rollout, a new vehicle stabilization system (VSS) attached to the vertical service structure kept the vehicle from undue swaying prior to launch at the pad, LC 39B. Following the launch, the flight test vehicle first stage was recovered with the aid of new parachutes resized to accommodate the five-segment-long first stage, which had a much greater length and mass than the Shuttle s reusable solid rocket boosters. After splashdown, recovery divers exercised extra care when handling the first stage to ensure that the flight data recorders in the fifth segment simulator were not damaged by exposure to sea water. The data recovered from the Ares I-X flight test will be very valuable in verifying the predicted environments and models used to design the vehicle. Lessons learned from Ares I-X will be shared with the Ares Projects through written and verbal reports and through integration of mission team members into the Project workforce.

Davis, Stephan R.↗

Development of Life Support System Technologies for Human Lunar Missions

With the Preliminary Design Review (PDR) for the Orion Crew Exploration Vehicle planned to be completed in 2009, Exploration Life Support (ELS), a technology development project under the National Aeronautics and Space Administration s (NASA) Exploration Technology Development Program, is focusing its efforts on needs for human lunar missions. The ELS Project s goal is to develop and mature a suite of Environmental Control and Life Support System (ECLSS) technologies for potential use on human spacecraft under development in support of U.S. Space Exploration Policy. ELS technology development is directed at three major vehicle projects within NASA s Constellation Program (CxP): the Orion Crew Exploration Vehicle (CEV), the Altair Lunar Lander and Lunar Surface Systems, including habitats and pressurized rovers. The ELS Project includes four technical elements: Atmosphere Revitalization Systems, Water Recovery Systems, Waste Management Systems and Habitation Engineering, and two cross cutting elements, Systems Integration, Modeling and Analysis, and Validation and Testing. This paper will provide an overview of the ELS Project, connectivity with its customers and an update to content within its technology development portfolio with focus on human lunar missions.

Barta, Daniel J.↗

Coded Modulation in C and MATLAB

This software, written separately in C and MATLAB as stand-alone packages with equivalent functionality, implements encoders and decoders for a set of nine error-correcting codes and modulators and demodulators for five modulation types. The software can be used as a single program to simulate the performance of such coded modulation. The error-correcting codes implemented are the nine accumulate repeat-4 jagged accumulate (AR4JA) low-density parity-check (LDPC) codes, which have been approved for international standardization by the Consultative Committee for Space Data Systems, and which are scheduled to fly on a series of NASA missions in the Constellation Program. The software implements the encoder and decoder functions, and contains compressed versions of generator and parity-check matrices used in these operations.

Hamkins, Jon↗

The Ares Launch Vehicles: Critical Capabilities for America's Continued Leadership in Space

The Constellation Program renews the nation's commitment to human space exploration a) Access to ISS. b) Human explorers to the Moon and beyond. c) Large telescopes and other hardware to LEO . Hardware is being built today. Development made easier by applying lessons learned from 50 years of spaceflight experience. Ares V heavy-lift capability will be a strategic asset for the nation. Constellation provides a means for world leadership through inspiration and strategic capability.

Cook, Stephen A.↗

Effects of the 8 psia / 32% O2 Atmosphere on the Human in the Spaceflight Environment

Extravehicular activity (EVA) is at the core of a manned space exploration program. There are elements of exploration that may be safely and effectively performed by robots, but there are critical elements of exploration that will require the trained, assertive, and reasoning mind of a human crewmember. To effectively use these skills, NASA needs a safe, effective, and efficient EVA component integrated into the human exploration program. The EVA preparation time should be minimized and the suit pressure should be low to accommodate EVA tasks without undue fatigue, physical discomfort, or suit-related trauma. Commissioned in 2005, the Exploration Atmospheres Working Group (EAWG) had the primary goal of recommending to NASA an internal environment that allowed efficient and repetitive EVAs for missions that were to be enabled by the former Constellation Program. At the conclusion of the EAWG meeting, the 8.0 psia and 32% oxygen (O2) environment were recommended for EVA intensive phases of missions. As a result of selecting this internal environment, NASA gains the capability for efficient EVA with low risk of decompression sickness (DCS), but not without incurring additional negative stimulus of hypobaric hypoxia to the already physiologically challenging spaceflight environment. This paper provides a literature review of the human health and performance risks associated with the 8 psia/32% O2 environment. Of most concern are the potential effects on the central nervous system including increased intracranial pressure, visual impairment, sensorimotor dysfunction, and oxidative damage. Other areas of focus include validation of the DCS mitigation strategy, incidence and treatment of acute mountain sickness (AMS), development of new exercise countermeasures protocols, effective food preparation at 8 psia, assurance of quality sleep, and prevention of suit-induced injury. As a first effort, the trade space originally considered in the EAWG was re-evaluated looking for ways to decrease the hypoxic dose by further enriching the O2% or increasing the pressure. After discussion with the NASA engineering and materials community, it was determined that the O2 could be enriched from 32% to 34% and the pressure increased from 8.0 to 8.2 psia without significant penalty. These two small changes increase alveolar O2 pressure by 11 mmHg, which is expected to significantly benefit crewmembers. The 8.2/34 environment (inspired O2 pressure = 128 mmHg) is also physiologically equivalent to the staged decompression atmosphere of 10.2 psia / 26.5% O2 (inspired O2 pressure = 127 mmHg) used on 34 different shuttle missions for approximately a week each flight. Once decided, the proposed internal environment, if different than current experience, should be evaluated through appropriately simulated research studies. In many cases, the human physiologic concerns can be investigated effectively through integrated multi-discipline ground-based studies. Although missions proposing to use an 8.2/34 environment are still years away, it is recommended that these studies begin early enough to ensure that the correct decisions pertaining to vehicle design, mission operational concepts, and human health countermeasures are appropriately informed.

Environmental control↗

Evidence Report: Risk of Hypobaric Hypoxia from the Exploration Atmosphere

Extravehicular activity (EVA) is at the core of a manned space exploration program. Some elements of exploration may be safely and effectively performed by robots, but certain critical elements will require the trained, assertive, and reasoning mind of a human crewmember. To effectively use these skills, NASA needs a safe, effective, and efficient EVA component integrated into the human exploration program. The EVA preparation time should be minimized and the suit pressure should be low to accommodate EVA tasks without causing undue fatigue, physical discomfort, or suit-related trauma. Commissioned in 2005, the Exploration Atmospheres Working Group (EAWG) had the primary goal of recommending to NASA an internal environment that allowed efficient and repetitive EVAs for missions that were to be enabled by the former Constellation Program. At the conclusion of the EAWG meeting, the 8.0 psia and 32% oxygen (O2) environment were recommended for EVA-intensive phases of missions. After re-evaluation in 2012, the 8/32 environment was altered to 8.2 psia and 34% O2 to reduce the hypoxic stress to a crewmember. These two small changes increase alveolar O2 pressure by 11 mmHg, which is expected to significantly benefit crewmembers. The 8.2/34 environment (inspired O2 pressure = 128 mmHg) is also physiologically equivalent to the staged decompression atmosphere of 10.2 psia / 26.5% O2 (inspired O2 pressure = 127 mmHg) used on 34 different shuttle missions for approximately a week each flight. As a result of selecting this internal environment, NASA gains the capability for efficient EVA with low risk of decompression sickness (DCS), but not without incurring the additional negative stimulus of hypobaric hypoxia to the already physiologically challenging spaceflight environment. This report provides a review of the human health and performance risks associated with the use of the 8.2 psia / 34% O2 environment during spaceflight. Of most concern are the potential effects on the central nervous system (CNS), including increased intracranial pressure, visual impairment, sensorimotor dysfunction, and oxidative damage. Other areas of focus include validation of the DCS mitigation strategy, incidence and treatment of transient acute mountain sickness (AMS), development of new exercise countermeasure protocols, effective food preparation at 8.2 psia, assurance of quality sleep, and prevention of suit-induced injury. Although missions proposing to use an 8.2/34 environment are still years away, it is recommended that these studies begin early enough to ensure that the correct decisions pertaining to vehicle design, mission operational concepts, and human health countermeasures are appropriately informed.

Norcross, Jason R.↗

Development of the J-2X Engine for the Ares I Crew Launch Vehicle and the Ares V Cargo Launch Vehicle: Building on the Apollo Program for Lunar Return Missions

The United States (U.S.) Vision for Space Exploration has directed NASA to develop two new launch vehicles for sending humans to the Moon, Mars, and beyond. In January 2006, NASA streamlined its hardware development approach for replacing the Space Shuttle after it is retired in 2010. Benefits of this approach include reduced programmatic and technical risks and the potential to return to the Moon by 2020, by developing the Ares I Crew Launch Vehicle (CLV) propulsion elements now, with full extensibility to future Ares V Cargo Launch Vehicle (CaLV) lunar systems. The Constellation Program selected the Pratt & Whitney Rocketdyne J-2X engine to power the Ares I Upper Stage Element and the Ares V Earth Departure Stage. This decision was reached during the Exploration Systems Architecture Study and confirmed after the Exploration Launch Projects Office performed a variety of risk analyses, commonality assessments, and trade studies. This paper narrates the evolution of that decision; describes the performance capabilities expected of the J-2X design, including potential commonality challenges and opportunities between the Ares I and Ares V launch vehicles; and provides a current status of J-2X design, development, and hardware testing activities. This paper also explains how the J-2X engine effort mitigates risk by testing existing engine hardware and designs; building on the Apollo Program (1961 to 1975), the Space Shuttle Program (1972 to 2010); and consulting with Apollo-era experts to derive other lessons lived to deliver a human-rated engine that is on an aggressive development schedule, with its first demonstration flight in 2012.

Greene, William D.↗