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 271 records · Page 15

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 (EDS). 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 learned to deliver a human-rated engine that is on an aggressive development schedule, with its first demonstration flight in 2012.

Greene, WIlliam↗

Crew Exploration Vehicle Launch Abort System Flight Test Overview

The Constellation program is an organization within NASA whose mission is to create the new generation of spacecraft that will replace the Space Shuttle after its planned retirement in 2010. In the event of a catastrophic failure on the launch pad or launch vehicle during ascent, the successful use of the launch abort system will allow crew members to escape harm. The Flight Test Office is the organization within the Constellation project that will flight-test the launch abort system on the Orion crew exploration vehicle. The Flight Test Office has proposed six tests that will demonstrate the use of the launch abort system. These flight tests will be performed at the White Sands Missile Range in New Mexico and are similar in nature to the Apollo Little Joe II tests performed in the 1960s. An overview of the launch abort system flight tests for the Orion crew exploration vehicle is given. Details on the configuration of the first pad abort flight test are discussed. Sample flight trajectories for two of the six flight tests are shown.

Williams-Hayes, Peggy S.↗

Ares V Overview and Status

As part of NASA s Constellation Program to resume exploration beyond low Earth orbit (LEO), the Ares V heavy-lift cargo launch vehicle as currently conceived will be able to send more crew and cargo to more places on the Moon than the Apollo Program Saturn V. (Figure 1) It also has unprecedented cargo mass and volume capabilities that will be a national asset for science, commerce, and national defense applications. Compared to current systems, it will offer approximately five times the mass and volume to most orbits and locations. The Columbia space shuttle accident, the resulting investigation, the Vision for Space Exploration, and the Exploration Systems Architecture Study (ESAS) broadly shaped the Constellation architecture. Out of those events and initiatives emerged an architecture intended to replace the space shuttle, complete the International Space Station (ISS), resume a much more ambitious plan to explore the moon as a stepping stone to other destinations in the solar system. The Ares I was NASA s main priority because of the goal to retire the Shuttle. Ares V remains in a concept development phase, evolving through hundreds of configurations. The current reference design was approved during the Lunar Capabilities Concept Review/Ares V Mission Concept Review (LCCR/MCR) in June 2008. This reference concept serves as a starting point for a renewed set of design trades and detailed analysis into its interaction with the other components of the Constellation architecture and existing launch infrastructure. In 2009, the Ares V team was heavily involved in supporting the Review of U.S. Human Space Flight Plans Committee. Several alternative designs for Ares V have been supplied to the committee. This paper will discuss the origins of the Ares V design, the evolution to the current reference configuration, and the options provided to the review committee.

Creech, Steve↗

Humidity Testing for Human Rated Spacecraft

Determination that equipment can operate in and survive exposure to the humidity environments unique to human rated spacecraft presents widely varying challenges. Equipment may need to operate in habitable volumes where the atmosphere contains perspiration, exhalation, and residual moisture. Equipment located outside the pressurized volumes may be exposed to repetitive diurnal cycles that may result in moisture absorption and/or condensation. Equipment may be thermally affected by conduction to coldplate or structure, by forced or ambient air convection (hot/cold or wet/dry), or by radiation to space through windows or hatches. The equipment s on/off state also contributes to the equipment s susceptibility to humidity. Like-equipment is sometimes used in more than one location and under varying operational modes. Due to these challenges, developing a test scenario that bounds all physical, environmental and operational modes for both pressurized and unpressurized volumes requires an integrated assessment to determine the "worst-case combined conditions." Such an assessment was performed for the Constellation program, considering all of the aforementioned variables; and a test profile was developed based on approximately 300 variable combinations. The test profile has been vetted by several subject matter experts and partially validated by testing. Final testing to determine the efficacy of the test profile on actual space hardware is in the planning stages. When validation is completed, the test profile will be formally incorporated into NASA document CxP 30036, "Constellation Environmental Qualification and Acceptance Testing Requirements (CEQATR)."

Johnson, Gary B.↗

Short Duration Bioastronautics Investigation 1904: Human Factors Assessment of Vibration Effects on Visual Performance during Launch

The primary objective of the Short Duration Bioastronautics Investigation (SDBI) 1904 was to determine visual performance limits during Shuttle operational vibration and g-loads, specifically through the determination of minimal usable font sizes using Orion-type display formats. Currently there is little to no data available to quantify human visual performance under the extreme g- and vibration conditions of launch. Existing data on shuttle vibration magnitude and frequency is incomplete and does not address human visual performance. There have been anecdotal reports of performance decrements from shuttle crews, but no structured data have been collected. Previous work by NASA on the effects of vibration and linear g-loads on human performance was conducted during the Gemini era, but these experiments were performed using displays and controls that are dramatically different than current concepts being considered by the Constellation Program. Recently, three investigations of visual performance under vibration have been completed at NASA Ames Research Center: the first examining whole-body vibration, the second employing whole-body vibration coupled with a sustained g-load, and a third examining the effects of peak versus extended duration vibration. However, all of these studies were conducted using only a single x-axis direction (eyeballs in/out). Estimates of thrust oscillations from the Constellation Ares-I first stage are driving the need for realistic human performance requirements. SDBI 1904 was an opportunity to address the need for requirements by conducting a highly focused and applied evaluation in a relevant spaceflight environment. The SDBI was a companion effort to Detailed Test Objective (DTO) 695, which measured shuttle seat accelerations (vibration) during ascent. Data from the SDBI will serve an important role in interpreting the DTO vibration data. Both SDBI 1904 and DTO 695 were low impact with respect to flight resources, and combined, they represent an efficient and focused problem solving approach. This project provided (a) immediate data for developing preliminary human performance vibration requirements; (b) flight validated inputs for ongoing and future ground-based research; and (c) preliminary information related to Orion display format design.

Thompson, Shelby↗

Development of Methodology to Gather Seated Anthropometry Data in a Microgravity Environment

The Constellation Program is designing a new vehicle based off of new anthropometric requirements. These requirements specify the need to account for a spinal elongation factor for anthropometric measurements involving the spine, such as eye height and seated height. However, to date there is no data relating spinal elongation to a seated posture. Only data relating spinal elongation to stature has been collected in microgravity. Therefore, it was proposed to collect seated height in microgravity to provide the Constellation designers appropriate data for their analyses. This document will describe the process in which the best method to collect seated height in microgravity was developed.

Rajulu, Sudhakar↗

Human-rating Automated and Robotic Systems - (How HAL Can Work Safely with Astronauts)

Long duration human space missions, as planned in the Vision for Space Exploration, will not be possible without applying unprecedented levels of automation to support the human endeavors. The automated and robotic systems must carry the load of routine housekeeping for the new generation of explorers, as well as assist their exploration science and engineering work with new precision. Fortunately, the state of automated and robotic systems is sophisticated and sturdy enough to do this work - but the systems themselves have never been human-rated as all other NASA physical systems used in human space flight have. Our intent in this paper is to provide perspective on requirements and architecture for the interfaces and interactions between human beings and the astonishing array of automated systems; and the approach we believe necessary to create human-rated systems and implement them in the space program. We will explain our proposed standard structure for automation and robotic systems, and the process by which we will develop and implement that standard as an addition to NASA s Human Rating requirements. Our work here is based on real experience with both human system and robotic system designs; for surface operations as well as for in-flight monitoring and control; and on the necessities we have discovered for human-systems integration in NASA's Constellation program. We hope this will be an invitation to dialog and to consideration of a new issue facing new generations of explorers and their outfitters.

Baroff, Lynn↗

Evaluation of Advanced Composite Structures Technologies for Application to NASA's Vision for Space Exploration

An assessment was performed to identify the applicability of composite material technologies to major structural elements of the NASA Constellation program. A qualitative technology assessment methodology was developed to document the relative benefit of 24 structural systems with respect to 33 major structural elements of Ares I, Orion, Ares V, and Altair. Technology maturity assessments and development plans were obtained from more than 30 Boeing subject matter experts for more than 100 technologies. These assessment results and technology plans were combined to generate a four-level hierarchy of recommendations. An overarching strategy is suggested, followed by a Constellation-wide development plan, three integrated technology demonstrations, and three focused projects for a task order follow-on.

Messinger, Ross↗

Numerical Modeling of Propellant Boil-Off in a Cryogenic Storage Tank

A numerical model to predict boil-off of stored propellant in large spherical cryogenic tanks has been developed. Accurate prediction of tank boil-off rates for different thermal insulation systems was the goal of this collaboration effort. The Generalized Fluid System Simulation Program, integrating flow analysis and conjugate heat transfer for solving complex fluid system problems, was used to create the model. Calculation of tank boil-off rate requires simultaneous simulation of heat transfer processes among liquid propellant, vapor ullage space, and tank structure. The reference tank for the boil-off model was the 850,000 gallon liquid hydrogen tank at Launch Complex 39B (LC- 39B) at Kennedy Space Center, which is under study for future infrastructure improvements to support the Constellation program. The methodology employed in the numerical model was validated using a sub-scale model and tank. Experimental test data from a 1/15th scale version of the LC-39B tank using both liquid hydrogen and liquid nitrogen were used to anchor the analytical predictions of the sub-scale model. Favorable correlations between sub-scale model and experimental test data have provided confidence in full-scale tank boil-off predictions. These methods are now being used in the preliminary design for other cases including future launch vehicles

Majumdar, A. K.↗

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 directs 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. This decision was reached after the Exploration Launch Projects Office performed a variety of risk analyses, commonality assessments, and trade studies. 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 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 building on the Apollo Program and other lessons lived to deliver a human-rated engine that is on an aggressive development schedule, with its first demonstration flight in 2012.

Snoddy, Jim↗

Lunar Mapping and Modeling Project

The Lunar Mapping and Modeling Project (LMMP) has been created to manage the development of a suite of lunar mapping and modeling products that support the Constellation Program (CxP) and other lunar exploration activities, including the planning, design, development, test and operations associated with lunar sortie missions, crewed and robotic operations on the surface, and the establishment of a lunar outpost. The project draws on expertise from several NASA and non-NASA organizations (MSFC, ARC, GSFC, JPL, CRREL and USGS). LMMP will utilize data predominately from the Lunar Reconnaissance Orbiter, but also historical and international lunar mission data (e.g. Apollo, Lunar Orbiter, Kaguya, Chandrayaan-1), as available and appropriate, to meet Constellation s data needs. LMMP will provide access to this data through a single, common, intuitive and easy to use NASA portal that transparently accesses appropriately sanctioned portions of the widely dispersed and distributed collections of lunar data, products and tools. LMMP will provide such products as DEMs, hazard assessment maps, lighting maps and models, gravity models, and resource maps. We are working closely with the LRO team to prevent duplication of efforts and ensure the highest quality data products. While Constellation is our primary customer, LMMP is striving to be as useful as possible to the lunar science community, the lunar education and public outreach (E/PO) community, and anyone else interested in accessing or utilizing lunar data.

Noble, Sarah K.↗

Enabling IP Header Compression in COTS Routers via Frame Relay on a Simplex Link

NASA is moving toward a networkcentric communications architecture and, in particular, is building toward use of Internet Protocol (IP) in space. The use of IP is motivated by its ubiquitous application in many communications networks and in available commercial off-the-shelf (COTS) technology. The Constellation Program intends to fit two or more voice (over IP) channels on both the forward link to, and the return link from, the Orion Crew Exploration Vehicle (CEV) during all mission phases. Efficient bandwidth utilization of the links is key for voice applications. In Voice over IP (VoIP), the IP packets are limited to small sizes to keep voice latency at a minimum. The common voice codec used in VoIP is G.729. This new algorithm produces voice audio at 8 kbps and in packets of 10-milliseconds duration. Constellation has designed the VoIP communications stack to use the combination of IP/UDP/RTP protocols where IP carries a 20-byte header, UDP (User Datagram Protocol) carries an 8-byte header, and RTP (Real Time Transport Protocol) carries a 12-byte header. The protocol headers total 40 bytes and are equal in length to a 40-byte G.729 payload, doubling the VoIP latency. Since much of the IP/UDP/RTP header information does not change from IP packet to IP packet, IP/UDP/RTP header compression can avoid transmission of much redundant data as well as reduce VoIP latency. The benefits of IP header compression are more pronounced at low data rate links such as the forward and return links during CEV launch. IP/UDP/RTP header compression codecs are well supported by many COTS routers. A common interface to the COTS routers is through frame relay. However, enabling IP header compression over frame relay, according to industry standard (Frame Relay IP Header Compression Agreement FRF.20), requires a duplex link and negotiations between the compressor router and the decompressor router. In Constellation, each forward to and return link from the CEV in space is treated independently as a simplex link. Without negotiation, the COTS routers are prevented from entering into the IP header compression mode, and no IP header compression would be performed. An algorithm is proposed to enable IP header compression in COTS routers on a simplex link with no negotiation or with a one-way messaging. In doing so, COTS routers can enter IP header compression mode without the need to handshake through a bidirectional link as required by FRF.20. This technique would spoof the routers locally and thereby allow the routers to enter into IP header compression mode without having the negotiations between routers actually occur. The spoofing function is conducted by a frame relay adapter (also COTS) with the capability to generate control messages according to the FRF.20 descriptions. Therefore, negotiation is actually performed between the FRF.20 adapter and the connecting COTS router locally and never occurs over the space link. Through understanding of the handshaking protocol described by FRF.20, the necessary FRF.20 negotiations messages can be generated to control the connecting router, not only to turn on IP header compression but also to adjust the compression parameters. The FRF.20 negotiation (or control) message is composed in the FRF.20 adapter by interpreting the incoming router request message. Many of the fields are simply transcribed from request to response while the control field indicating response and type are modified.

Nguyen, Sam P.↗

Pressure Effects on Oxygen Concentration Flammability Thresholds of Materials for Aerospace Applications

Spacecraft materials selection is based on an upward flammability test conducted in a quiescent environment in the highest-expected oxygen-concentration environment. However, NASA s advanced space exploration program is anticipating using various habitable environments. Because limited data is available to support current program requirements, a different test logic is suggested to address these expanded atmospheric environments through the determination of materials self-extinguishment limits. This paper provides additional pressure effects data on oxygen concentration and partial pressure self-extinguishment limits under quiescent conditions. For the range of total pressures tested, the oxygen concentration and oxygen partial pressure flammability thresholds show a near linear function of total pressure. The oxygen concentration/oxygen partial pressure flammability thresholds depend on the total pressure and appear to increase with increasing oxygen concentration (and oxygen partial pressure). For the Constellation Program, the flammability threshold information will allow NASA to identify materials with increased flammability risk because of oxygen concentration and total pressure changes, minimize potential impacts, and allow for development of sound requirements for new spacecraft and extraterrestrial landers and habitats.

Hirsch, David↗

A Return to Innovative Engineering Design, Critical Thinking and Systems Engineering

I believe we are facing a critical time where innovative engineering design is of paramount importance to the success of our aerospace industry. However, the very qualities and attributes necessary for enhancing, educating, and mentoring a creative spirit are in decline in important areas. The importance of creativity and innovation in this country was emphasized by a special edition of the Harvard Business Review OnPoint entitled: "The Creative Company" which compiled a series of past and present articles on the subject of creativity and innovation and stressed its importance to our national economy. There is also a recognition of a lack of engineering, critical thinking and problem-solving skills in our education systems and a trend toward trying to enhance those skills by developing K-12 educational programs such as Project Lead the Way, "Science for All Americans", Benchmarks 2061 , etc. In addition, with respect to spacecraft development, we have a growing need for young to mid-level engineers with appropriate experience and skills in spacecraft design, development, analysis, testing, and systems engineering. As the Director of Engineering at NASA's Johnson Space Center, I realized that sustaining engineering support of an operational human spacecraft such as the Space Shuttle is decidedly different than engineering design and development skills necessary for designing a new spacecraft such as the Crew Exploration Vehicle of the Constellation Program. We learned a very important lesson post Columbia in that the Space Shuttle is truly an experimental and not an operational vehicle and the strict adherence to developed rules and processes and chains of command of an inherently bureaucratic organizational structure will not protect us from a host of known unknowns let alone unknown unknowns. There are no strict rules, processes, or procedures for understanding anomalous results of an experiment, anomalies with an experimental spacecraft like Shuttle, or in the conceptual design of a spacecraft. Engineering design is as much an art as it is a science. The critical thinking skills necessary to uncover lurking problems in an experimental design and creatively develop solutions are some of the same skills necessary to design a new spacecraft. Thus, I believe engineers unfamiliar with or removed from design and development need time to transition and develop the required skill set to be effective spacecraft designers. I believe the creative process necessary in design can be enhanced and even taught as early as grades K-12 and should continue to be nurtured and developed at the university level and beyond. I am going to present a strategy for developing learning teams to address complex multidisciplinary problems and to creatively develop solutions to those problems rapidly at minimal cost. I will frame a real problem, the development of on-orbit thermal protection system repair of the Space Shuttle, and step through the series of skills necessary to enhance the creative process. The case study I will illustrate is based on a real project, the R&D Reinforced Carbon-Carbon (RCC) Repair Team's development of on-orbit repair concepts for damaged Space Shuttle RCC nose cap and/or leading edges.

Camarda, Charles J.↗

Kennedy Space Center: Apollo to Multi-User Spaceport

NASA Kennedy Space Center (KSC) was established as the gateway to exploring beyond earth. Since the establishment of KSC in December 1963, the Center has been critical in the execution of the United States of Americas bold mission to send astronauts beyond the grasp of the terra firma. On May 25, 1961, a few weeks after a Soviet cosmonaut became the first person to fly in space, President John F. Kennedy laid out the ambitious goal of landing a man on the moon and returning him safely to the Earth by the end of the decade. The resultant Apollo program was massive endeavor, driven by the Cold War Space Race, and supported with a robust budget. The Apollo program consisted of 18 launches from newly developed infrastructure, including 12 manned missions and six lunar landings, ending with Apollo 17 that launched on December 7, 1972. Continuing to use this infrastructure, the Skylab program launched four missions. During the Skylab program, KSC infrastructure was redesigned to meet the needs of the Space Shuttle program, which launched its first vehicle (STS-1) on April 12, 1981. The Space Shuttle required significant modifications to the Apollo launch pads and assembly facilities, as well as new infrastructure, such as Orbiter and Payload Processing Facilities, as well as the Shuttle Landing Facility. The Space Shuttle was a workhorse that supported many satellite deployments, but was key for the construction and maintenance of the International Space Station, which required additional facilities at KSC to support processing of the flight hardware. After reaching the new Millennium, United States policymakers searched for new ways to reduce the cost of space exploration. The Constellation Program was initiated in 2005 with a goal of providing a crewed lunar landing with a much smaller budget. The very successful Space Shuttle made its last launch on July 8, 2011, after 135 missions. In the subsequent years, KSC continues to evolve, and this paper will address past and future efforts of the transformation of the KSC Apollo and Space Shuttle heritage infrastructure into a more versatile, multi-user spaceport. The paper will also discuss the US Congressional and NASA initiatives for developing and supporting multiple commercial partners, while simultaneously supporting NASAs human exploration initiative, consisting of Space Launch System (SLS), Orion spacecraft and associated ground launch systems. In addition, the paper explains the approach with examples for NASA KSC to leverage new technologies and innovative capabilities developed to reduce the cost to individual users.

launchpad↗

Performance Analysis of Apollo Navigational Starter Routine

The focus of this project is to recreate and analyze the effectiveness of the original Apollo Starter Routine (ASR) which was used to generate the state vector of the Apollo spacecraft based on a series of radiometric observations. The original Apollo navigation software is unavailable in a modern programming language and the original coding has not been preserved. This necessitates its recreation using the original software documentation. Space Shuttle navigation software does not typically use the ASR or an algorithm like it since the Shuttle s state vector is easily deduced from GPS information or other sources. However, this tactic will be ineffective when trying to determine the state vector of a craft approaching, departing or in orbit around the Moon since the GPS network faces the surface of the Earth, not outer space. The recreation of the ASR from the original documentation is therefore vital as a simulation baseline for the navigation software under development for the Constellation program. The algorithms that make up the ASR will be extracted from the original documentation and adapted for and then implemented in a modern programming language; the majority of it will be coded in Matlab. The ASR s effectiveness will then be tested using simulated tracking data. The ability of the ASR to handle realistically noisy data and the accuracy with which it generates state vectors were analyzed. The ASR proved to be robust enough to process data with range and angle noise as large as 10,000 meters and 10(exp -6) radians together and 300,000 meters and 5x10(exp -4) radians separately at Lunar distances. The ASR was able to handle marginally more noise at distances closer to the Earth where the angle noise was less significant. The ASR is capable of effectively processing 40-80 data points gathered at a rate of one per 20 seconds at close Earth orbit and up to 28-40 data points gathered at a rate of one per minute at distant Earth orbit and Lunar orbit.

Ivanov, Stoyan I.↗

The First Development of Human Factors Engineering Requirements for Application to Ground Task Design for a NASA Flight Program

The National Aeronautics and Space Administration has long applied standards-derived human engineering requirements to the development of hardware and software for use by astronauts while in flight. The most important source of these requirements has been NASA-STD-3000. While there have been several ground systems human engineering requirements documents, none has been applicable to the flight system as handled at NASA's launch facility at Kennedy Space Center. At the time of the development of previous human launch systems, there were other considerations that were deemed more important than developing worksites for ground crews; e.g., hardware development schedule and vehicle performance. However, experience with these systems has shown that failure to design for ground tasks has resulted in launch schedule delays, ground operations that are more costly than they might be, and threats to flight safety. As the Agency begins the development of new systems to return humans to the moon, the new Constellation Program is addressing this issue with a new set of human engineering requirements. Among these requirements is a subset that will apply to the design of the flight components and that is intended to assure ground crew success in vehicle assembly and maintenance tasks. These requirements address worksite design for usability and for ground crew safety.

Dischinger, H. Charles, Jr.↗

Apollo: Learning From the Past, For the Future

This paper shares an interesting and unique case study of knowledge capture by the National Aeronautics and Space Administration (NASA), an ongoing project to recapture and make available the lessons learned from the Apollo lunar landing project so that those working on future projects do not have to "reinvent the wheel". NASA's new Constellation program, the successor to the Space Shuttle program, proposes a return to the Moon using a new generation of vehicles. The Orion Crew Vehicle and the Altair Lunar Lander will use hardware, practices, and techniques descended and derived from Apollo, Shuttle and the International Space Station. However, the new generation of engineers and managers who will be working with Orion and Altair are largely from the decades following Apollo, and are likely not well aware of what was developed in the 1960s. In 2006 a project at NASA's Johnson Space Center was begun to find pertinent Apollo-era documentation and gather it, format it, and present it using modern tools for today's engineers and managers. This "Apollo Mission Familiarization for Constellation Personnel" project is accessible via the web from any NASA center for those interested in learning "how did we do this during Apollo?"

Grabois, Michael R.↗