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.

SourceResearch connectionFrom yearThrough year

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

At least 289 records · Page 16

All sources NASA NTRS DOE OSTI

NASA NTRS2010

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.↗

NASA NTRS2009

Altair Lunar Lander Development Status: Enabling Human Lunar Exploration

As a critical part of the NASA Constellation Program lunar transportation architecture, the Altair lunar lander will return humans to the moon and enable a sustained program of lunar exploration. The Altair is to deliver up to four crew to the surface of the moon and return them to low lunar orbit at the completion of their mission. Altair will also be used to deliver large cargo elements to the lunar surface, enabling the buildup of an outpost. The Altair Project initialized its design using a minimum functionality approach that identified critical functionality required to meet a minimum set of Altair requirements. The Altair team then performed several analysis cycles using risk-informed design to selectively add back components and functionality to increase the vehicles safety and reliability. The analysis cycle results were captured in a reference Altair design. This design was reviewed at the Constellation Lunar Capabilities Concept Review, a Mission Concept Review, where key driving requirements were confirmed and the Altair Project was given authorization to begin Phase A project formulation. A key objective of Phase A is to revisit the Altair vehicle configuration, to better optimize it to complete its broad range of crew and cargo delivery missions. Industry was invited to partner with NASA early in the design to provide their insights regarding Altair configuration and key engineering challenges. A blended NASA-industry team will continue to refine the lander configuration and mature the vehicle design over the next few years. This paper will update the international community on the status of the Altair Project as it addresses the challenges of project formulation, including optimizing a vehicle configuration based on the work of the NASA Altair Project team, industry inputs and the plans going forward in designing the Altair lunar lander.

Laurini, Kathleen C.↗

NASA NTRS2009

Altair Lunar Lander Development Status: Enabling Lunar Exploration

As a critical part of the NASA Constellation Program lunar transportation architecture, the Altair lunar lander will return humans to the moon and enable a sustained program of lunar exploration. The Altair is to deliver up to four crew to the surface of the moon and return them to low lunar orbit at the completion of their mission. Altair will also be used to deliver large cargo elements to the lunar surface, enabling the buildup of an outpost. The Altair Project initialized its design using a "minimum functionality" approach that identified critical functionality required to meet a minimum set of Altair requirements. The Altair team then performed several analysis cycles using risk-informed design to selectively add back components and functionality to increase the vehicle's safety and reliability. The analysis cycle results were captured in a reference Altair design. This design was reviewed at the Constellation Lunar Capabilities Concept Review, a Mission Concept Review, where key driving requirements were confirmed and the Altair Project was given authorization to began Phase A project formulation. A key objective of Phase A is to revisit the Altair vehicle configuration, to better optimize it to complete its broad range of crew and cargo delivery missions. Industry was invited to partner with NASA early in the design to provide their insights regarding Altair configuration and key engineering challenges. NASA intends to continue to seek industry involvement in project formulation activities. This paper will update the international coimmunity on the status of the Altair Project as it addresses the challenges of project formulation, including optinuzing a vehicle configuration based on the work of the NASA Altair Project team, industry inputs and the plans going forward in designing the Altair lunar lander.

Laurini, Kathleen C.↗

NASA NTRS2011

The Effects of Microgravity on Seated Height (Spinal Elongation)

ABSTRACT Many physiological factors, such as spinal elongation, fluid shifts, bone atrophy, and muscle loss, occur during an exposure to a microgravity environment. Spinal elongation is just one of the factors that can also affect the safety and performance of a crewmember while in space. Spinal elongation occurs due to the lack of gravity/compression on the spinal column. This allows for the straightening of the natural spinal curve. There is a possible fluid shift in the inter-vertebral disks that may also result in changes in height. This study aims at collecting the overall change in seated height for crewmembers exposed to a microgravity environment. During previous Programs, Apollo-Soyuz Test Project (ASTP) and Skylab, spinal elongation data was collected from a small number of subjects in a standing posture but were limited in scope. Data from these studies indicated a quick increase in stature during the first few days of weightlessness, after which stature growth reached a plateau resulting in up to a 3% increase of the original measurement [1-5]. However, this data was collected only for crewmembers in standing posture and not in a seated posture. Seated height may have a different effect than standing height due to a change in posture as well as due to a compounded effect of wearing restraints and a potential compression of the gluteal area. Seated height was deemed as a critical measurement in the design of the Constellation Program s (CxP) Crew Exploration Vehicle (CEV), called Orion which is now the point-of-departure vehicle for the Multi-Purpose Crew Vehicle (MPCV) Program; therefore a better understanding of the effects of microgravity on seated height is necessary. Potential changes in seated height that may not have impacted crew accommodation in previous Programs will have significant effects on crew accommodation due to the layout of seats in the Orion.. The current and existing configuration is such that the four crewmembers are stacked two by two with the commander and pilot seats on the top and the two remaining seats underneath, thereby limiting the amount of clearance for the crewmembers seated in the bottom seat. The inner mold line of these types of vehicles are fixed due to other design constraints; therefore, it is essential that all seats incorporate additional clearance to account for adequate spinal growth thereby ensuring that the crew can safely ingress the seat and be strapped in prior to its return to earth. If there is not enough clearance to account for spinal growth deltas between seats then there is the potential that crewmembers will not be able to comfortably and safely fit into their seats. The crewmember in the bottom stacked seat may even have negative clearance with the seat above him or her which could lead to potential ingress/egress issues or potentially injury of the crewmember during landing. These impacts are specific to these types of vehicles with stacked seat configuration. Without proper knowledge of the amount of spinal elongation, or growth, which occurs due to microgravity and space flight, the design of future vehicle(s) or suits may cause injury, discomfort, and limit crew accommodation and crew complements. The experiment primarily aimed to collect seated height data for subjects exposed to microgravity environments, and feed new information regarding the effect of elongation of the spine forward into the design of the Orion. The data collected during the experiment included, two seated height measurement and two digital pictures of seated height pre-, in-, and post-flight. In addition to seated height, crewmembers had an optional task of collecting stature , standing height. Seated height data was obtained from 29 crewmembers that included 8 ISS increment crew (2 females and 6 males) and 21 Shuttle crew (1 female, 20 males), and whose mean age was 48 years ( 4 years). This study utilized the last six Shuttle flights, STS-128 to STS-134. The results show that partipating crewmembers experienced growth up to 6% in seated height and up to 3% in stature. Based on the worst case statistical analysis of the subject data, the recommended seated height growth of 6% will be provided to the designers as the necessary seated height adjustment.

Young, K. S.↗

NASA NTRS2006

Systems Integration Processes for NASA's Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable low earth orbit. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific processes for requirements development and verification, integrated design and analysis, integrated simulation and testing and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The CLV Project is broken logically into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.

Reuter, James L.↗

NASA NTRS2010

Heavy Lift for Exploration: Options and Utilization

Every study of exploration capabilities since the Apollo Program has recommended the renewal of a heavy lift launch capability for the United States. NASA is aggressively pursuing that capability. This paper will discuss several aspects of that effort and the potential uses for that heavy lift capability. The need for heavy lift was cited most recent in the findings of the Review of U.S. Human Space Flight Plans Committee. Combined with considerations of launch availability and on-orbit operations, the Committee finds that exploration will benefit from the availability of a heavy-lift vehicle, the report said. In addition, heavy lift would enable the launching of large scientific observatories and more capable deep-space missions. It may also provide benefit in national security applications. The most recent focus of NASA s heavy lift effort is the Ares V cargo launch vehicle, which is part of the Constellation Program architecture for human exploration beyond low Earth orbit (LEO). The most recent point-of-departure configuration of the Ares V was approved during the Lunar Capabilities concept Review (LCCR) in 2008. The Ares V first stage propulsion system consists of a core stage powered by six commercial liquid hydrogen/liquid oxygen (LH2/LOX) RS-68 engines, flanked by two 5.5-segment solid rocket boosters (SRBs) based on the 5-segment Ares I first stage. The boosters use the same Polybutadiene Acrylonitrile (PBAN) propellant as the Space Shuttle. Atop the core stage is the Earth departure stage (EDS), powered by a single J-2X upper stage engine based on the Ares I upper stage engine. The 33-foot-diameter payload shroud can enclose a lunar lander, scientific instruments, or other payloads. Since LCCR, NASA has continued to refine the design through several successive internal design cycles. In addition, NASA has worked to quantify the broad national consensus for heavy lift in ways that, to the extent possible, meet the needs of the user community.

Creech, Steve↗

NASA NTRS2006

Systems Integration Processes for NASA Ares I Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable Low Earth Orbit (LEO). This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and nonpropulsion elements within NASA's Crew Launch Vehicle (CLV), now known as the Ares I. The objective of the Ares I is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to LEO in support of the lunar and Mars missions. The Ares I must successfully provide this capability within cost and schedule, and with an acceptable risk approach. This paper will describe the systems engineering management processes that will be applied to assure Ares I Project success through complete and efficient technical integration. Discussion of technical review and management processes for requirements development and verification, integrated design and analysis, integrated simulation and testing, and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The Ares I Project is logically divided into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these Ares I elements and among the other Constellation projects. Also discussed is launch vehicle stack integration (Ares I to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage. The processes for decomposing requirements to the elements and ensuring that requirements have been correctly validated, decomposed, and allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements, will be discussed.

Taylor, James L.↗

NASA NTRS2009

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 information provided through LMMP will assist CxP in: planning tasks in the areas of landing site evaluation and selection, design and placement of landers and other stationary assets, design of rovers and other mobile assets, developing terrain-relative navigation (TRN) capabilities, and assessment and planning of science traverses. The project draws on expertise from several NASA and non-NASA organizations (MSFC, ARC, GSFC, JPL, CRREL US Army Cold Regions Research and Engineering Laboratory, and the 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 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. Two visualization systems are being developed, a web-based system called Lunar Mapper, and a desktop client, ILIADS, which will be downloadable from the LMMP portal. LMMP will provide such products as local and regional imagery and DEMs, hazard assessment maps, lighting and gravity models, and resource maps. We are working closely with the LRO team to prevent duplication of efforts and to 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 commercial community, the lunar education and public outreach (E/PO) community, and anyone else interested in accessing or utilizing lunar data. A beta version of the portal and visualization systems is expected to be released in late 2009, with a version 1 release planned for early 2011.

Noble, Sarah K.↗

NASA NTRS2010

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, in a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation; testing results, and other information. Where appropriate, actual performance history was used for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to verify compliance with requirements and to highlight design or performance shortcomings for further decision-making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability and maintainability analysis, and present findings and observation based on analysis leading to the Ground Systems Preliminary Design Review milestone.

Gernand, Jeffrey L.↗

NASA NTRS2010

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, within a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability, and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation, testing results, and other information. Where appropriate, actual performance history was used to calculate failure rates for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to assess compliance with requirements and to highlight design or performance shortcomings for further decision making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability, and maintainability analysis, and present findings and observation based on analysis leading to the Ground Operations Project Preliminary Design Review milestone.

Gernand, Jeffrey L.↗

NASA NTRS2012

NASA's Space Launch System Progress Report

Exploration beyond Earth orbit will be an enduring legacy for future generations, as it provides a platform for science and exploration that will define new knowledge and redefine known boundaries. NASA s Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is responsible for designing and developing the first exploration-class rocket since the Apollo Program s Saturn V that sent Americans to the Moon in the 1960s and 1970s. The SLS offers a flexible design that may be configured for the Orion Multi-Purpose Crew Vehicle with associated life-support equipment and provisions for long journeys or may be outfitted with a payload fairing that will accommodate flagship science instruments and a variety of high-priority experiments. Building on legacy systems, facilities, and expertise, the SLS will have an initial lift capability of 70 tonnes (t) in 2017 and will be evolvable to 130 t after 2021. While commercial launch vehicle providers service the International Space Station market, this capability will surpass all vehicles, past and present, providing the means to do entirely new missions, such as human exploration of Mars. Building on the foundation laid by over 50 years of human and scientific space flight and on the lessons learned from the Apollo, Space Shuttle, and Constellation Programs the SLS team is delivering both technical trade studies and business case analyses to ensure that the SLS architecture will be safe, affordable, reliable, and sustainable. This panel will address the planning and progress being made by NASA s SLS Program.

May, Todd A.↗

NASA NTRS2008

Semi-Automated Diagnosis, Repair, and Rework of Spacecraft Electronics

NASA's Constellation Program for Exploration of the Moon and Mars places human crews in extreme isolation in resource scarce environments. Near Earth, the discontinuation of Space Shuttle flights after 2010 will alter the up- and down-mass capacity for the International Space Station (ISS). NASA is considering new options for logistics support strategies for future missions. Aerospace systems are often composed of replaceable modular blocks that minimize the need for complex service operations in the field. Such a strategy however, implies a robust and responsive logistics infrastructure with relatively low transportation costs. The modular Orbital Replacement Units (ORU) used for ISS requires relatively large blocks of replacement hardware even though the actual failed component may really be three orders of magnitude smaller. The ability to perform in-situ repair of electronics circuits at the component level can dramatically reduce the scale of spares and related logistics cost. This ability also reduces mission risk, increases crew independence and improves the overall supportability of the program. The Component-Level Electronics Assembly Repair (CLEAR) task under the NASA Supportability program was established to demonstrate the practicality of repair by first investigating widely used soldering materials and processes (M&P) performed by modest manual means. The work will result in program guidelines for performing manual repairs along with design guidance for circuit reparability. The next phase of CLEAR recognizes that manual repair has its limitations and some highly integrated devices are extremely difficult to handle and demand semi-automated equipment. Further, electronics repairs require a broad range of diagnostic capability to isolate the faulty components. Finally repairs must pass functional tests to determine that the repairs are successful and the circuit can be returned to service. To prevent equipment demands from exceeding spacecraft volume capacity and skill demands from exceeding crew time and training limits, the CLEAR project is examining options provided by non-real time tele-operations, robotics, and a new generation of diagnostic equipment. This paper outlines a strategy to create an effective repair environment where, with the support of ground based engineers, crewmembers can diagnose, repair and test flight electronics in-situ. This paper also discusses the implications of successful tele-robotic repairs when expanded to rework and reconfiguration of used flight assets for building Constellation infrastructure elements.

Struk, Peter M.↗

NASA NTRS2015

An Approach for Performance Based Glove Mobility Requirements

The Space Suit Assembly (SSA) Development Team at NASA Johnson Space Center has invested heavily in the advancement of rear‐entry planetary exploration suit design but largely deferred development of extravehicular activity (EVA) glove designs, and accepted the risk of using the current flight gloves, Phase VI, for exploration missions. However, as design reference missions mature, the risks of using heritage hardware have highlighted the need for developing robust new glove technologies. To address the technology gap, the NASA Space Technology Mission Directorate's Game‐Changing Development Program provided start‐up funding for the High Performance EVA Glove (HPEG) Element as part of the Next Generation Life Support (NGLS) Project in the fall of 2013. The overarching goal of the HPEG Element is to develop a robust glove design that increases human performance during EVA and creates pathway for implementation of emergent technologies, with specific aims of increasing pressurized mobility to 60% of barehanded capability, increasing the durability in on‐pristine environments, and decreasing the potential of gloves to cause injury during use. The HPEG Element focused initial efforts on developing quantifiable and repeatable methodologies for assessing glove performance with respect to mobility, injury potential, thermal conductivity, and abrasion resistance. The team used these methodologies to establish requirements against which emerging technologies and glove designs can be assessed at both the component and assembly levels. The mobility performance testing methodology was an early focus for the HPEG team as it stems from collaborations between the SSA Development team and the JSC Anthropometry and Biomechanics Facility (ABF) that began investigating new methods for suited mobility and fit early in the Constellation Program. The combined HPEG and ABF team used lessons learned from the previous efforts as well as additional reviews of methodologies in physical and occupational therapy arenas to develop a protocol that assesses gloved range of motion, strength, dexterity, tactility, and fit in comparative quantitative terms and also provides qualitative insight to direct hardware design iterations. The protocol was evaluated using five experienced test subjects wearing the EMU pressurized to 4.3psid with three different glove configurations. The results of the testing are presented to illustrate where the protocol is and is not valid for benchmark comparisons. The process for requirements development based upon the results is also presented along with suggested performance values for the High Performance EVA Gloves to be procured in fiscal year 2015.

Aitchison, Lindsay↗

NASA NTRS2016

An Approach for Performance Based Glove Mobility Requirements

The Space Suit Assembly (SSA) Development Team at NASA Johnson Space Center has invested heavily in the advancement of rear-entry planetary exploration suit design but largely deferred development of extravehicular activity (EVA) glove designs, and accepted the risk of using the current flight gloves, Phase VI, for exploration missions. However, as design reference missions mature, the risks of using heritage hardware have highlighted the need for developing robust new glove technologies. To address the technology gap, the NASA Space Technology Mission Directorate's Game-Changing Development Program provided start-up funding for the High Performance EVA Glove (HPEG) Element as part of the Next Generation Life Support (NGLS) Project in the fall of 2013. The overarching goal of the HPEG Element is to develop a robust glove design that increases human performance during EVA and creates pathway for implementation of emergent technologies, with specific aims of increasing pressurized mobility to 60% of barehanded capability, increasing the durability in on-pristine environments, and decreasing the potential of gloves to cause injury during use. The HPEG Element focused initial efforts on developing quantifiable and repeatable methodologies for assessing glove performance with respect to mobility, injury potential, thermal conductivity, and abrasion resistance. The team used these methodologies to establish requirements against which emerging technologies and glove designs can be assessed at both the component and assembly levels. The mobility performance testing methodology was an early focus for the HPEG team as it stems from collaborations between the SSA Development team and the JSC Anthropometry and Biomechanics Facility (ABF) that began investigating new methods for suited mobility and fit early in the Constellation Program. The combined HPEG and ABF team used lessons learned from the previous efforts as well as additional reviews of methodologies in physical and occupational therapy arenas to develop a protocol that assesses gloved range of motion, strength, dexterity, tactility, and fit in comparative quantitative terms and also provides qualitative insight to direct hardware design iterations. The protocol was evaluated using five experienced test subjects wearing the EMU pressurized to 4.3psid with three different glove configurations. The results of the testing are presented to illustrate where the protocol is and is not valid for benchmark comparisons. The process for requirements development based upon the results is also presented along with suggested performance values for the High Performance EVA Gloves currently in development.

Aitchison, Lindsay↗

NASA NTRS2007

Orion GN and C Overview and Architecture

The Crew Exploration Vehicle, named Orion, is a critical element in the Constellation Program to develop the transportation system needed to send humans back to the moon and then beyond. Lockheed Martin is the prime contractor for the Orion spacecraft, which is managed by the Johnson Space Center. The Orion GN&C sub-system is being jointly developed by NASA and Lockheed Martin through a mode team approach. The GN&C is a critical element of the Orion mission to carry astronauts to low earth orbit to service the International Space Station and then on later flights to transfer and return a crew of four to the moon. The Orion GN&C system must perform monitoring and abort functions during ascent, rendezvous and docking in both low earth and lunar orbits, perform uncrewed lunar loiter operations, perform trans earth injection and atmospheric entry and landing. The Orion also must be integrated with the Ares I Crew Launch Vehicle, the Earth Departure Stage of the Ares V and the Lunar Surface Access Module. This paper provides an overview of the Orion GN&C system. The functional capabilities of the Orion GN&C will be provided in the context of Constellation architecture, the key GN&C requirements will be summarized, the GN&C architecture will be presented, the development schedule and plans will summarized and finally conclusions will be presented.

Hu, Howard↗

NASA NTRS2024

Lunar Regolith Simulant User's Guide: Revision A

This guide is titled Lunar Regolith Simulant User's Guide, Rev A, and two points need to be made about the title. First, is the use of the term "regolith". During the Apollo Program, the term "soil" was used for taking a sample of the loose material on the surface, and then cataloging that sample in the lunar curation database as a "soil sample". By the 1980s, the term "regolith" gained favor by lunar scientists. In the Lunar Sourcebook (Heiken et al., 1991), regolith is defined as "a general term for the layer or mantle of fragmental and unconsolidated rock material, whether residual or transported and of highly varied character, that nearly everywhere forms the surface of the land and overlies or covers bedrock". Regolith is a terrestrial term that seems to go back to 1897, according to a recent paper by Huggett (2023). Huggett summed up his paper by writing, "soil and regolith are one in the same". "Regolith" will mostly be used throughout this guide, as it tends to separate in one's mind the unique nature of the Moon's surface when compared to the inherent bias humans have in their mind when they hear and use the word "soil". When referring to Apollo samples, "soil" is used for historical context and in some places the simple term "lunar simulant" is also used. Secondly, Rev A is used in the title because NASA released its first Lunar Regolith Simulant User's Guide in 2010, near the end of NASA's Constellation Program (Schrader et al., 2010). This guide follows in the pattern of that first guide and will be updated on a periodic basis as new simulants are created, characterized and used, and as new information emerges about the Moon's regolith due to new lunar exploration missions, both robotic and human.

Simulant↗

NASA NTRS2011

Wallops Low Elevation Link Analysis for the Constellation Launch/Ascent Links

To execute the President's Vision for Space Exploration, the Constellation Program (CxP) was formed to build the next generation spacecraft Orion and launch vehicles Ares, to transport human and cargo to International Space Station (ISS), moon, and Mars. This paper focuses on the detailed link analysis for Orion/Ares s launch and ascent links with Wallops 11.3m antenna (1) Orion's Dissimilar Voice link: 10.24 Kbps, 2-way (2) Ares Developmental Flight Instrument link, 20 Mbps, downlink. Three launch trajectories are considered: TD7-E, F (Feb), and G (Aug). In certain launch scenarios, the critical events of main engine cutoff (MECO) and Separation occur during the low elevation regime of WFF s downrange -- less than 5 degree elevation angle. The goal of the study is to access if there is enough link margins for WFF to track the DV and DFI links.

Constellation↗

NASA NTRS2014

Application of Fault Management Theory to the Quantitative Selection of a Launch Vehicle Abort Trigger Suite

The theory of System Health Management (SHM) and of its operational subset Fault Management (FM) states that FM is implemented as a "meta" control loop, known as an FM Control Loop (FMCL). The FMCL detects that all or part of a system is now failed, or in the future will fail (that is, cannot be controlled within acceptable limits to achieve its objectives), and takes a control action (a response) to return the system to a controllable state. In terms of control theory, the effectiveness of each FMCL is estimated based on its ability to correctly estimate the system state, and on the speed of its response to the current or impending failure effects. This paper describes how this theory has been successfully applied on the National Aeronautics and Space Administration's (NASA) Space Launch System (SLS) Program to quantitatively estimate the effectiveness of proposed abort triggers so as to select the most effective suite to protect the astronauts from catastrophic failure of the SLS. The premise behind this process is to be able to quantitatively provide the value versus risk trade‐off for any given abort trigger, allowing decision makers to make more informed decisions. All current and planned crewed launch vehicles have some form of vehicle health management system integrated with an emergency launch abort system to ensure crew safety. While the design can vary, the underlying principle is the same: detect imminent catastrophic vehicle failure, initiate launch abort, and extract the crew to safety. Abort triggers are the detection mechanisms that identify that a catastrophic launch vehicle failure is occurring or is imminent and cause the initiation of a notification to the crew vehicle that the escape system must be activated. While ensuring that the abort triggers provide this function, designers must also ensure that the abort triggers do not signal that a catastrophic failure is imminent when in fact the launch vehicle can successfully achieve orbit. That is, the abort triggers must have low false negative rates to be sure that real crew‐threatening failures are detected, and also low false positive rates to ensure that the crew does not abort from non‐crew‐threatening launch vehicle behaviors. The analysis process described in this paper is a compilation of over six years of lessons learned and refinements from experiences developing abort triggers for NASA's Constellation Program (Ares I Project) and the SLS Program, as well as the simultaneous development of SHM/FM theory. The paper will describe the abort analysis concepts and process, developed in conjunction with SLS Safety and Mission Assurance (S&MA) to define a common set of mission phase, failure scenario, and Loss of Mission Environment (LOME) combinations upon which the SLS Loss of Mission (LOM) Probabilistic Risk Assessment (PRA) models are built. This abort analysis also requires strong coordination with the Multi‐Purpose Crew Vehicle (MPCV) and SLS Structures and Environments (STE) to formulate a series of abortability tables that encapsulate explosion dynamics over the ascent mission phase. The design and assessment of abort conditions and triggers to estimate their Loss of Crew (LOC) Benefits also requires in‐depth integration with other groups, including Avionics, Guidance, Navigation and Control(GN&C), the Crew Office, Mission Operations, and Ground Systems. The outputs of this analysis are a critical input to SLS S&MA's LOC PRA models. The process described here may well be the first full quantitative application of SHM/FM theory to the selection of a sensor suite for any aerospace system.

Lo, Yunnhon↗