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 559 records · Page 31

Recent Ground Hold and Rapid Depressurization Testing of Multilayer Systems

In the development of flight insulation systems for large cryogenic orbital storage (spray on foam and multilayer insulation), testing need include all environments that are experienced during flight. While large efforts have been expended on studying, bounding, and modeling the orbital performance of the insulation systems, little effort has been expended on the ground hold and ascent phases of a mission. Historical cryogenic in-space systems that have flown have been able to ignore these phases of flight due to the insulation system being within a vacuum jacket. In the development phase of the Nuclear Mars Vehicle and the Shuttle Nuclear Vehicle, several insulation systems were evaluated for the full mission cycle. Since that time there had been minimal work on these phases of flight until the Constellation program began investigating cryogenic service modules and long duration upper stages. With the inception of the Cryogenic Propellant Storage and Transfer Technology Demonstration Mission, a specific need was seen for the data and as such, several tests were added to the Cryogenic Boil-off Reduction System liquid hydrogen test matrix to provide more data on a insulation system. Testing was attempted with both gaseous nitrogen (GN2) and gaseous helium (GHe) backfills. The initial tests with nitrogen backfill were not successfully completed due to nitrogen liquefaction and solidification preventing the rapid pumpdown of the vacuum chamber. Subsequent helium backfill tests were successful and showed minimal degradation. The results are compared to the historical data.

Space Environment Simulation↗

Exploring Life Support Architectures for Evolution of Deep Space Human Exploration

Life support system architectures for long duration space missions are often explored analytically in the human spaceflight community to find optimum solutions for mass, performance, and reliability. But in reality, many other constraints can guide the design when the life support system is examined within the context of an overall vehicle, as well as specific programmatic goals and needs. Between the end of the Constellation program and the development of the "Evolvable Mars Campaign", NASA explored a broad range of mission possibilities. Most of these missions will never be implemented but the lessons learned during these concept development phases may color and guide future analytical studies and eventual life support system architectures. This paper discusses several iterations of design studies from the life support system perspective to examine which requirements and assumptions, programmatic needs, or interfaces drive design. When doing early concept studies, many assumptions have to be made about technology and operations. Data can be pulled from a variety of sources depending on the study needs, including parametric models, historical data, new technologies, and even predictive analysis. In the end, assumptions must be made in the face of uncertainty. Some of these may introduce more risk as to whether the solution for the conceptual design study will still work when designs mature and data becomes available.

Anderson, Molly↗

Influence of Combined Whole-Body Vibration Plus G-Loading on Visual Performance

Recent engineering analyses of the integrated Ares-Orion stack show that vibration levels for Orion crews have the potential to be much higher than those experienced in Gemini, Apollo, and Shuttle vehicles. Of particular concern to the Constellation Program (CxP) is the 12 Hz thrust oscillation (TO) that the Ares-I rocket develops during the final ~20 seconds preceding first-stage separation, at maximum G-loading. While the structural-dynamic mitigations being considered can assure that vibration due to TO is reduced to below the CxP crew health limit, it remains to be determined how far below this limit vibration must be reduced to enable effective crew performance during launch. Moreover, this "performance" vibration limit will inform the operations concepts (and crew-system interface designs) for this critical phase of flight. While Gemini and Apollo studies provide preliminary guidance, the data supporting the historical limits were obtained using less advanced interface technologies and very different operations concepts. In this study, supported by the Exploration Systems Mission Directorate (ESMD) Human Research Program, we investigated display readability-a fundamental prerequisite for any interaction with electronic crew-vehicle interfaces-while observers were subjected to 12 Hz vibration superimposed on the 3.8 G loading expected for the TO period of ascent. Two age-matched groups of participants (16 general population and 13 Crew Office) performed a numerical display reading task while undergoing sustained 3.8 G loading and whole-body vibration at 0, 0.15, 0.3, 0.5, and 0.7 g in the eyeballs in/out (x-axis) direction. The time-constrained reading task used an Orion-like display with 10- and 14-pt non-proportional sans-serif fonts, and was designed to emulate the visual acquisition and processing essential for crew system monitoring. Compared to the no-vibration baseline, we found no significant effect of vibration at 0.15 and 0.3 g on task error rates (ER) or response times (RT). Significant degradations in both ER and RT, however, were observed at 0.5 and 0.7 g for 10-pt, and at 0.7 g for 14-pt font displays. These objective performance measures were mirrored by participants' subjective ratings. Interestingly, we found that the impact of vibration on ER increased with distance from the center of the display, but only for vertical displacements. Furthermore, no significant ER or RT aftereffects were detected immediately following vibration, regardless of amplitude. Lastly, given that our reading task required no specialized spaceflight expertise, our finding that effects were not statistically distinct between our two groups is not surprising. The results from this empirical study provide initial guidance for evaluating the display readability trade-space between text-font size and vibration amplitude. However, the outcome of this work should be considered preliminary in nature for a number of reasons: 1. The single 12 Hz x-axis vibration employed was based on earlier load-cycle models of the induced TO environment at the end of Ares-I first stage flight. Recent analyses of TO mitigation designs suggest that significant concurrent off-axis vibration may also occur. 2. The shirtsleeve environment in which we tested fails to capture the full kinematic and dynamic complexity of the physical interface between crewmember and the still-to-bematured helmet-suit-seat designs, and the impact these will have for vibration transmission and consequent performance. 3. By examining performance in this reading and number processing task, we are only assessing readability, a first and necessary step that in itself does not directly address the performance of more sophisticated operational tasks such as vehicle-health monitoring or manual control of the vehicle.

readability↗

Reliability and Probabilistic Risk Assessment - How They Play Together

PRA methodology is one of the probabilistic analysis methods that NASA brought from the nuclear industry to assess the risk of LOM, LOV and LOC for launch vehicles. PRA is a system scenario based risk assessment that uses a combination of fault trees, event trees, event sequence diagrams, and probability and statistical data to analyze the risk of a system, a process, or an activity. It is a process designed to answer three basic questions: What can go wrong? How likely is it? What is the severity of the degradation? Since 1986, NASA, along with industry partners, has conducted a number of PRA studies to predict the overall launch vehicles risks. Planning Research Corporation conducted the first of these studies in 1988. In 1995, Science Applications International Corporation (SAIC) conducted a comprehensive PRA study. In July 1996, NASA conducted a two-year study (October 1996 - September 1998) to develop a model that provided the overall Space Shuttle risk and estimates of risk changes due to proposed Space Shuttle upgrades. After the Columbia accident, NASA conducted a PRA on the Shuttle External Tank (ET) foam. This study was the most focused and extensive risk assessment that NASA has conducted in recent years. It used a dynamic, physics-based, integrated system analysis approach to understand the integrated system risk due to ET foam loss in flight. Most recently, a PRA for Ares I launch vehicle has been performed in support of the Constellation program. Reliability, on the other hand, addresses the loss of functions. In a broader sense, reliability engineering is a discipline that involves the application of engineering principles to the design and processing of products, both hardware and software, for meeting product reliability requirements or goals. It is a very broad design-support discipline. It has important interfaces with many other engineering disciplines. Reliability as a figure of merit (i.e. the metric) is the probability that an item will perform its intended function(s) for a specified mission profile. In general, the reliability metric can be calculated through the analyses using reliability demonstration and reliability prediction methodologies. Reliability analysis is very critical for understanding component failure mechanisms and in identifying reliability critical design and process drivers. The following sections discuss the PRA process and reliability engineering in detail and provide an application where reliability analysis and PRA were jointly used in a complementary manner to support a Space Shuttle flight risk assessment.

Safie, Fayssal M.↗

Exploring Life Support Architectures for Evolution of Deep Space Human Exploration

Life support system architectures for long duration space missions are often explored analytically in the human spaceflight community to find optimum solutions for mass, performance, and reliability. But in reality, many other constraints can guide the design when the life support system is examined within the context of an overall vehicle, as well as specific programmatic goals and needs. Between the end of the Constellation program and the development of the "Evolvable Mars Campaign", NASA explored a broad range of mission possibilities. Most of these missions will never be implemented but the lessons learned during these concept development phases may color and guide future analytical studies and eventual life support system architectures. This paper discusses several iterations of design studies from the life support system perspective to examine which requirements and assumptions, programmatic needs, or interfaces drive design. When doing early concept studies, many assumptions have to be made about technology and operations. Data can be pulled from a variety of sources depending on the study needs, including parametric models, historical data, new technologies, and even predictive analysis. In the end, assumptions must be made in the face of uncertainty. Some of these may introduce more risk as to whether the solution for the conceptual design study will still work when designs mature and data becomes available.

Anderson, Molly S.↗

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

Prior to the redirection of the Constellation Program, the Wallops 11.3-meter ground station was tasked to support the Orion's Dissimilar Voice (DV) link and the Ares's Development Flight Instrument (DFI) link. Detailed analysis of the launch trajectories indicates that during the launch and ascent operation, the critical events of Orion-Ares main engine cut off (MECO) and Separation occur at low elevation angle. We worked with engineers from both Wallops Flight Facility (WFF) and Johnson Space Center (JSC) to perform an intensive measurement and link analysis campaign on the DV and DFI links. The main results were as follows: (1) The DV links have more than 3 dB margin at MECO and Separation. (2) The DFI links have 0 dB margin at Separation during certain weather condition in summer season. (3) Tropospheric scintillation loss is the major impairment at low elevation angle. (4) The current scintillation models in the Recommendation ITU-R P.618 (Propagation data and prediction methods required for the design of Earth-space telecommunication systems), which are based on limited experimental and theoretical work, exhibit idiosyncratic behaviors. We developed an improved model based on the measurements of recent Shuttle mission launch and ascent links and the ITU propagation data. (5) Due to the attitude uncertainty of the Orion-Ares stack, the high dynamics of the launch and ascent trajectory, and the irregularity of the Orion and Ares antenna patterns, we employed new link analysis approach to model the spacecraft antenna gain. In this paper we discuss the details of the aforementioned results.

Cheung, Kar-Ming↗

Use of IPsec by Manned Space Missions

NASA's Constellation Program is developing its next generation manned space systems for missions to the International Space Station (ISS) and the Moon. The Program is embarking on a path towards standards based Internet Protocol (IP) networking for space systems communication. The IP based communications will be paired with industry standard security mechanisms such as Internet Protocol Security (IPsec) to ensure the integrity of information exchanges and prevent unauthorized release of sensitive information in-transit. IPsec has been tested in simulations on the ground and on at least one Earth orbiting satellite, but the technology is still unproven in manned space mission situations and significant obstacles remain.

Pajevski, Michael J.↗

Preliminary Characterization of the Altair Lunar Lander Slosh Dynamics and Some Implications for the Thrust Vector Control Design

This paper describes a conceptual design of the Thrust Vector Control (TVC) system and preliminary modeling of propellant slosh, for the Altair Lunar Lander. Altair is a vehicle element of the NASA Constellation Program aimed at returning humans to the moon. Guidance, Navigation, and Control (GN&C) is the measurement and control of spacecraft position, velocity, and attitude in support of mission objectives. One key GN&C function is the commanding of effectors that control attitude and impart delta V on the vehicle, utilizing both reaction control system (RCS) thrusters and throttling and TVC gimbaling of the vehicle main engine. Both the Altair descent and ascent modules carry fuel tanks. During thrusting maneuvers, the sloshing of liquid fuels in partially filled tanks can interact with the controlled system in such a way as to cause the overall system to be unstable. These fuel tanks must be properly placed, relative to the spacecraft's c.m., to avoid any unstable interactions. Following this will be a discussion of propellant slosh modeling work performed for the present vehicle configuration, including slosh frequency and participatory fluid mass predictions. Knowing the range of slosh mode frequencies over mission phases, the TVC bandwidth must be carefully selected so as not to excite the slosh modes at those frequencies. The likely need to increase the damping factor of slosh modes via baffles will also be discussed. To conclude, a discussion of operations procedures aimed at minimizing TVC-slosh interactions will be given.

Lee, Allan Y.↗

Interfacing Space Communications and Navigation Network Simulation with Distributed System Integration Laboratories (DSIL)

NASA's planned Lunar missions will involve multiple NASA centers where each participating center has a specific role and specialization. In this vision, the Constellation program (CxP)'s Distributed System Integration Laboratories (DSIL) architecture consist of multiple System Integration Labs (SILs), with simulators, emulators, testlabs and control centers interacting with each other over a broadband network to perform test and verification for mission scenarios. To support the end-to-end simulation and emulation effort of NASA' exploration initiatives, different NASA centers are interconnected to participate in distributed simulations. Currently, DSIL has interconnections among the following NASA centers: Johnson Space Center (JSC), Kennedy Space Center (KSC), Marshall Space Flight Center (MSFC) and Jet Propulsion Laboratory (JPL). Through interconnections and interactions among different NASA centers, critical resources and data can be shared, while independent simulations can be performed simultaneously at different NASA locations, to effectively utilize the simulation and emulation capabilities at each center. Furthermore, the development of DSIL can maximally leverage the existing project simulation and testing plans. In this work, we describe the specific role and development activities at JPL for Space Communications and Navigation Network (SCaN) simulator using the Multi-mission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE) tool to simulate communications effects among mission assets. Using MACHETE, different space network configurations among spacecrafts and ground systems of various parameter sets can be simulated. Data that is necessary for tracking, navigation, and guidance of spacecrafts such as Crew Exploration Vehicle (CEV), Crew Launch Vehicle (CLV), and Lunar Relay Satellite (LRS) and orbit calculation data are disseminated to different NASA centers and updated periodically using the High Level Architecture (HLA). In addition, the performance of DSIL under different traffic loads with different mix of data and priorities are evaluated.

Traffic Measuring and Monitoring↗

Constellation Architecture and System Margins Strategy

NASA's Constellation Program (CxP) is responsible for the definition, design, development, and operations of the flight, ground, and mission operations elements being developed by the United States for the human exploration of the Moon, Mars, and beyond. This paper provides an overview of the latest CxP technical architecture baseline, driving requirements, and reference missions for initial capability to fly to the International Space Station (ISS) and to the Moon. The results of the most recent design decisions and analyses supporting the architecture, including the Ares I, Ares V, Orion crew exploration vehicle, and the Altair lunar lander will be presented.

Muirhead, Brian↗

SSME to RS-25: Challenges of Adapting a Heritage Engine to a New Vehicle Architecture

Following the cancellation of the Constellation program and retirement of the Space Shuttle, NASA initiated the Space Launch System (SLS) program to provide next-generation heavy lift cargo and crew access to space. A key constituent of the SLS architecture is the RS-25 engine, also known as the Space Shuttle Main Engine (SSME). The RS-25 was selected to serve as the main propulsion system for the SLS core stage in conjunction with the solid rocket boosters. This selection was largely based on the maturity and extensive experience gained through 135 missions, 3000+ ground tests, and over a million seconds total accumulated hot-fire time. In addition, there were also over a dozen functional flight assets remaining from the Space Shuttle program that could be leveraged to support the first four flights. However, while the RS-25 is a highly mature system, simply unbolting it from the Space Shuttle boat-tail and installing it on the new SLS vehicle is not a "plug-and-play" operation. In addition to numerous technical integration details involving changes to significant areas such as the environments, interface conditions, technical performance requirements, operational constraints and so on, there were other challenges to be overcome in the area of replacing the obsolete engine control system (ECS). While the magnitude of accomplishing this effort was less than that needed to develop and field a new clean-sheet engine system, the path to the first flight of SLS has not been without unexpected challenges.

Ballard, Richard O.↗

Evolution of Orion Mission Design for Exploration Mission 1 and 2

The evolving mission design and concepts of NASA's next steps have shaped Orion into the spacecraft that it is today. Since the initial inception of Orion, through the Constellation Program, and now in the Exploration Mission frame-work with the Space Launch System (SLS), each mission design concept and program goal have left Orion with a set of capabilities that can be utilized in many different mission types. Exploration Missions 1 and 2 (EM-1 and EM-2) have now been at the forefront of the mission design focus for the last several years. During that time, different Design Reference Missions (DRMs) were built, analyzed, and modified to solve or mitigate enterprise level design trades to ensure a viable mission from launch to landing. The resulting DRMs for EM-1 and EM-2 were then expanded into multi-year trajectory scans to characterize vehicle performance and Earth-Moon geometry trends. This provides Orion's subsystems with stressing reference trajectories to help design their system. Now that Orion has progressed through the Preliminary and Critical Design Re-views (PDR and CDR) there is a general shift in the focus of mission design from aiding the vehicle design to providing mission specific products needed for pre-flight and real time operations. Some of the mission specific products need-ed include analysis of steering law performance, inputs into navigational accura-cy assessments, abort options at any point in the mission for each valid trajecto-ry in the launch window, recontact avoidance between the upper stage and Orion post nominal separation, etc.

Gutkowski, Jeffrey P.↗

Evolution of Orion Mission Design for Exploration Mission 1 and 2

The evolving mission design and concepts of NASA’s next steps have shaped Orion into the spacecraft that it is today. Since the initial inception of Orion, through the Constellation Program, and now in the Exploration Mission frame-work with the Space Launch System (SLS), each mission design concept and pro-gram goal have left Orion with a set of capabilities that can be utilized in many different mission types. Exploration Missions 1 and 2 (EM-1 and EM-2) have now been at the forefront of the mission design focus for the last several years. During that time, different Design Reference Missions (DRMs) were built, analyzed, and modified to solve or mitigate enterprise level design trades to ensure a viable mission from launch to landing. The resulting DRMs for EM-1 and EM-2 were then expanded into multi-year trajectory scans to characterize vehicle performance as affected by variations in Earth-Moon geometry. This provides Orion’s subsystems with stressing reference trajectories to help design their system. Now that Orion has progressed through the Preliminary and Critical Design Reviews (PDR and CDR), there is a general shift in the focus of mission design from aiding the vehicle design to providing mission specific products needed for pre-flight and real time operations. Some of the mission specific products needed include, large quantities of nominal trajectories for multiple monthly launch periods and abort options at any point in the mission for each valid trajectory in the launch window.

Gutkowski, Jeffrey P.↗

Introduction to the Portable Life Support Schematic and Technology Development Components

Conger presented the operations and functions of the baseline Constellation Program (CxP) Portable Life Support System (PLSS) schematic and key development technologies. He explained the functional descriptions of the schematic components in the fluid systems of the PLSS for multiple operational scenarios. PLSS subsystems include the oxygen subsystem, the ventilation subsystem, and the thermal subsystem. He also presented the operational PLSS modes: Nominal EVA mode, Umbilical - no recharge mode, Umbilical - with recharge mode, BENDS mode, BUDDY mode, Secondary oxygen mode, and the PLSS-removed umbilical mode.

Conger, Bruce↗

Large Payload Ground Transportation and Test Considerations

Many spacecraft concepts under consideration by the National Aeronautics and Space Administration’s (NASA’s) Evolvable Mars Campaign take advantage of a Space Launch System payload shroud that may be 8 to 10 meters in diameter. Large payloads can theoretically save cost by reducing the number of launches needed--but only if it is possible to build, test, and transport a large payload to the launch site in the first place. Analysis performed previously for the Altair project identified several transportation and test issues with an 8.973 meters diameter payload. Although the entire Constellation Program—including Altair—has since been canceled, these issues serve as important lessons learned for spacecraft designers and program managers considering large payloads for future programs. A transportation feasibility study found that, even broken up into an Ascent and Descent Module, the Altair spacecraft would not fit inside available aircraft. Ground transportation of such large payloads over extended distances is not generally permitted, so overland transportation alone would not be an option. Limited ground transportation to the nearest waterway may be possible, but water transportation could take as long as 67 days per production unit, depending on point of origin and acceptance test facility; transportation from the western United States would require transit through the Panama Canal to access the Kennedy Space Center launch site. Large payloads also pose acceptance test and ground processing challenges. Although propulsion, mechanical vibration, and reverberant acoustic test facilities at NASA’s Plum Brook Station have been designed to accommodate large spacecraft, special handling and test work-arounds may be necessary, which could increase cost, schedule, and technical risk. Once at the launch site, there are no facilities currently capable of accommodating the combination of large payload size and hazardous processing such as hypergolic fuels, pyrotechnic devices, and high pressure gasses. Ironically, the limiting factor to a national heavy lift strategy may not be the rocket technology needed to throw a heavy payload, but rather the terrestrial infrastructure—roads, bridges, airframes, and buildings—necessary to transport, acceptance test, and process large spacecraft. Failure to carefully consider where and how large spacecraft are manufactured, tested, and launched could result in unforeseen cost to modify existing (or develop new) infrastructure, or incur additional risk due to increased handling operations or eliminating key verifications. Although this paper focuses on the canceled Altair spacecraft as a case study, the issues identified here have wide applicability to other large payloads, including concepts under consideration for NASA’s Evolvable Mars Campaign.

Rucker, Michelle A.↗

Progress on Ares First Stage Propulsion

The mission of the National Aeronautics and Space Administration (NASA) is not simply to maintain its current position with the International Space Station and other space exploration endeavors, but to build a permanent outpost on the Moon and then travel on to explore ever more distant terrains. The Constellation Program will oversee the development of the crew capsule, launch vehicles, and other systems needed to achieve this mission. From this initiative will come two new launch vehicles: the Ares I and Ares V. The Ares I will be a human-rated vehicle, which will be used for crew transport; the Ares V, a cargo transport vehicle, will be the largest launch vehicle ever built. The Ares Projects team at Marshall Space Flight Center (MSFC) in Huntsville, Alabama is assigned with developing these two new vehicles. The Ares I vehicle will have an in-line, two-stage rocket configuration. The first stage will provide the thrust or propulsion component for the Ares rocket systems through the first two minutes of the mission. The First Stage Team is tasked with developing the propulsion system necessary to liftoff from the Earth and loft the entire Ares vehicle stack toward low-Earth orbit. Building on the legacy of the Space Shuttle and other NASA space exploration initiatives, the propulsion for the Ares I First Stage will be a Shuttle-derived reusable solid rocket motor. Progress to date by the First Stage Team has been robust and on schedule. This paper provides an update on the design and development of the Ares First Stage Propulsion system.

Priskos, Alex S.↗

Progress on Ares First Stage Propulsion

The mission of the National Aeronautics and Space Administration (NASA) is not simply to maintain its current position with the International Space Station and other space exploration endeavors, but to build a permanent outpost on the Moon and then travel on to explore ever more distant terrains. The Constellation Program will oversee the development of the crew capsule, launch vehicles, and other systems needed to achieve this mission. From this initiative will come two new launch vehicles: the Ares I and Ares V. The Ares I will be a human-rated vehicle, which will be used for crew transport; the Ares V, a cargo transport vehicle, will be the largest launch vehicle ever built. The Ares Projects team at Marshall Space Flight Center (MSFC) in Huntsville, Alabama is assigned with developing these two new vehicles. The Ares I vehicle will have an inline, two-stage rocket configuration. The first stage will provide the thrust or propulsion component for the Ares rocket systems through the first two minutes of the mission. The First Stage Team is tasked with developing the propulsion system necessary to liftoff from the Earth and loft the entire Ares vehicle stack toward low-Earth orbit. Building on the legacy of the Space Shuttle and other NASA space exploration initiatives, the propulsion for the Ares I First Stage will be a Shuttle-derived reusable solid rocket motor. Progress to date by the First Stage Team has been robust and on schedule. This paper provides an update on the design and development of the Ares First Stage Propulsion system. The presentation provides an overview of the information presented in the paper.

Priskos, Alex S.↗

Crew Exploration Vehicle (CEV) (Orion) Occupant Protection: Appendices - Part 1

Dr. Nancy J. Currie, of the NASA Engineering and Safety Center (NESC), Chief Engineer at Johnson Space Center (JSC), requested an assessment of the Crew Exploration Vehicle (CEV) occupant protection as a result of issues identified by the Constellation Program and Orion Project. The NESC, in collaboration with the Human Research Program (HRP), investigated new methods associated with occupant protection for the Crew Exploration Vehicle (CEV), known as Orion. The primary objective of this assessment was to investigate new methods associated with occupant protection for the CEV, known as Orion, that would ensure the design provided minimal risk to the crew during nominal and contingency landings in an acceptable set of environmental and spacecraft failure conditions. This documents contains the appendices to the NESC assessment report. NASA/TM-2013-217380, Application of the Brinkley Dynamic Response Criterion to Spacecraft Transient Dynamic Events supersedes this document.

Currie-Gregg, Nancy J.↗