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 469 records · Page 26
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Pre-Flight Tests with Astronauts, Flight and Ground Hardware, to Assure On-Orbit Success

On-Orbit Constraints Test (OOCT's) refers to mating flight hardware together on the ground before they will be mated on-orbit or on the Lunar surface. The concept seems simple but it can be difficult to perform operations like this on the ground when the flight hardware is being designed to be mated on-orbit in a zero-g/vacuum environment of space or low-g/vacuum environment on the Lunar/Mars Surface. Also some of the items are manufactured years apart so how are mating tasks performed on these components if one piece is on-orbit/on Lunar/Mars surface before its mating piece is planned to be built. Both the Internal Vehicular Activity (IVA) and Extra-Vehicular Activity (EVA) OOCT's performed at Kennedy Space Center will be presented in this paper. Details include how OOCT's should mimic on-orbit/Lunar/Mars surface operational scenarios, a series of photographs will be shown that were taken during OOCT's performed on International Space Station (ISS) flight elements, lessons learned as a result of the OOCT's will be presented and the paper will conclude with possible applications to Moon and Mars Surface operations planned for the Constellation Program.

Haddad Michael E.↗
NASA NTRS2011

Human Factors Analysis to Improve the Processing of Ares-1 Launch Vehicle

The Constellation Program (CxP) is composed of an array of vehicles used to go to the Moon and Mars. The Ares vehicle one of the components of CxP, goes through several stages of processing before it is launched at the Kennedy Space Center. In order to have efficient and effective ground processing inside and outside the vehicle, all of the ground processing activities should be analyzed. The analysis for this program was performed, by engineers, technicians, and human factors experts with spacecraft processing experience. The procedure used to gather data was accomplished by observing human activities within physical mockups. The paper will focus on the procedures, analysis and results from these observations.

Dippolito, Gregory M.↗
NASA NTRS2010

Human-Rating Implementation for Commercial Space

This slide presentation reviews the appropriate NASA standards and Health and Medical Technical Authority (HMTA) standards for human rated spacecraft developed by commercial vendors. Included are the HMTA requirements for the Constellation Program (CxP)

Whitmore, Mihriban↗
NASA NTRS2010

1-G Human Factors for Optimal Processing and Operability of Ground Systems up to CxP GOP PDR

During the mid stages of design development, up to Constellation Program (CxP) Preliminary Design Review (PDR), the requirements for leveraging I-G human factors for optimizing ground processing of Flight Hardware were mature for levels - 2, 3, 4, and 5. This paper gives an overview of the accomplishments achieved during that time. The main focus of this paper will be on the CxP Ground Operations Project human factors engineering analysis process using a Human Factors Engineering Analysis Tool (HFEAT) for developing the level- 5 requirements effecting the design development of the subsystems for Ground Support System (GSS), and Ground Support Equipment (GSE).

Stambolian, Damon B.↗
NASA NTRS2010

Human Factors Operability Timeline Analysis to Improve the Processing Flow of the Orion Spacecraft

The Constellation Program (CxP) Orion vehicle goes through several areas and stages of processing before its launched at the Kennedy Space Center. In order to have efficient and effective processing, all of the activities need to be analyzed. This was accomplished by first developing a timeline of events that included each activity, and then each activity was analyzed by operability experts and human factors experts with spacecraft processing experience. This papers focus is to explain the results and the process for developing this human factors operability timeline analysis to improve the processing flow of Orion.

Schlierf, Roland↗
NASA NTRS2010

Ares I-X: Lessons for a New Era of Spaceflight

Since 2005, the Ares Projects at Marshall Space Flight Center (MSFC) have been developing the Ares I crew launch vehicle and Ares V cargo launch vehicle. On October 28, 2009, the first development flight test of the Ares I crew launch vehicle, Ares I-X, lifted off from a launch pad at Kennedy Space Center (KSC) on successful suborbital flight. Despite the President s intention to cancel the Constellation Program of which Ares is a part, this historic flight has produced a great amount of data and numerous lessons learned for any future launch vehicles. This paper will describe the accomplishments of Ares I-X and the lessons that other programs can glean from this successful mission. Ares I was designed to carry up to four astronauts to the International Space Station (ISS). It also was designed to be used with the Ares V cargo launch vehicle for a variety of missions beyond low-Earth orbit (LEO). The Ares I-X development flight test was conceived in 2006 to acquire early engineering and environment data during liftoff, ascent, and first stage recovery. The test achieved the following primary objectives: Demonstrated control of a dynamically similar, integrated Ares I/Orion, using Ares I relevant ascent control algorithms. Performed an in-flight separation/staging event between a Ares I-similar First Stage and a representative Upper Stage. Demonstrated assembly and recovery of a new Ares I-like First Stage element at KSC. Demonstrated First Stage separation sequencing, and quantify First Stage atmospheric entry dynamics, and parachute performance. Characterized the magnitude of integrated vehicle roll torque throughout First Stage flight.

Davis, Stephan R.↗
NASA NTRS2010

Maximizing Launch Vehicle and Payload Design Via Early Communications

The United States? current fleet of launch vehicles is largely derived from decades-old designs originally made for payloads that no longer exist. They were built primarily for national security or human exploration missions. Today that fleet can be divided roughly into small-, medium-, and large-payload classes based on mass and volume capability. But no vehicle in the U.S. fleet is designed to accommodate modern payloads. It is usually the payloads that must accommodate the capabilities of the launch vehicles. This is perhaps most true of science payloads. It was this paradigm that the organizers of two weekend workshops in 2008 at NASA's Ames Research Center sought to alter. The workshops brought together designers of NASA's Ares V cargo launch vehicle (CLV) with scientists and payload designers in the astronomy and planetary sciences communities. Ares V was still in a pre-concept development phase as part of NASA?s Constellation Program for exploration beyond low Earth orbit (LEO). The space science community was early in a Decadal Survey that would determine future priorities for research areas, observations, and notional missions to make those observations. The primary purpose of the meetings in April and August of 2008, including the novel format, was to bring vehicle designers together with space scientists to discuss the feasibility of using a heavy lift capability to launch large observatories and explore the Solar System. A key question put to the science community was whether this heavy lift capability enabled or enhanced breakthrough science. The meetings also raised the question of whether some trade-off between mass/volume and technical complexity existed that could reduce technical and programmatic risk. By engaging the scientific community early in the vehicle design process, vehicle engineers sought to better understand potential limitations and requirements that could be added to the Ares V from the mission planning community. From the vehicle standpoint, while the human exploration mission could not be compromised to accommodate other payloads, the design might otherwise be tailored to not exclude other payload requirements. This paper summarizes the findings of the workshops and discusses the benefits of bringing together the vehicle design and science communities early in their concept phases

Morris, Bruce↗
NASA NTRS2010

The Lunar Mapping and Modeling Project

The Lunar Mapping and Modeling Project (LMMP) is managing a suite of lunar mapping and modeling tools and data products that support lunar exploration activities, including the planning, de-sign, development, test, and operations associated with crewed and/or robotic operations on the lunar surface. Although the project was initiated primarily to serve the needs of the Constellation program, it is equally suited for supporting landing site selection and planning for a variety of robotic missions, including NASA science and/or human precursor missions and commercial missions such as those planned by the Google Lunar X-Prize participants. In addition, LMMP should prove to be a convenient and useful tool for scientific analysis and for education and public out-reach (E/PO) activities.

Nall, M.↗
NASA NTRS2010

Overview of the Altair Lunar Lander Thermal Control System Design and the Impacts of Global Access

NASA s Constellation Program (CxP) was developed to successfully return humans to the Lunar surface prior to 2020. The CxP included several different project offices including Altair, which was planned to be the next generation Lunar Lander. The Altair missions were architected to be quite different than the Lunar missions accomplished during the Apollo era. These differences resulted in a significantly dissimilar Thermal Control System (TCS) design. The current paper will summarize the Altair mission architecture and the various operational phases associated with the planned mission. In addition, the derived thermal requirements and the TCS designed to meet these unique and challenging thermal requirements will be presented. During the past year, the design team has focused on developing a vehicle architecture capable of accessing the entire Lunar surface. Due to the widely varying Lunar thermal environment, this global access requirement resulted in major changes to the thermal control system architecture. These changes, and the rationale behind the changes, will be detailed throughout the current paper.

Stephan, Ryan A.↗
NASA NTRS2010

Reference Avionics Architecture for Lunar Surface Systems

Developing and delivering infrastructure capable of supporting long-term manned operations to the lunar surface has been a primary objective of the Constellation Program in the Exploration Systems Mission Directorate. Several concepts have been developed related to development and deployment lunar exploration vehicles and assets that provide critical functionality such as transportation, habitation, and communication, to name a few. Together, these systems perform complex safety-critical functions, largely dependent on avionics for control and behavior of system functions. These functions are implemented using interchangeable, modular avionics designed for lunar transit and lunar surface deployment. Systems are optimized towards reuse and commonality of form and interface and can be configured via software or component integration for special purpose applications. There are two core concepts in the reference avionics architecture described in this report. The first concept uses distributed, smart systems to manage complexity, simplify integration, and facilitate commonality. The second core concept is to employ extensive commonality between elements and subsystems. These two concepts are used in the context of developing reference designs for many lunar surface exploration vehicles and elements. These concepts are repeated constantly as architectural patterns in a conceptual architectural framework. This report describes the use of these architectural patterns in a reference avionics architecture for Lunar surface systems elements.

Somervill, Kevin M.↗
NASA NTRS2007

Photonic Bandgap (PBG) Shielding Technology

Photonic Bandgap (PBG) shielding technology is a new approach to designing electromagnetic shielding materials for mitigating Electromagnetic Interference (EM!) with small, light-weight shielding materials. It focuses on ground planes of printed wiring boards (PWBs), rather than on components. Modem PSG materials also are emerging based on planar materials, in place of earlier, bulkier, 3-dimensional PBG structures. Planar PBG designs especially show great promise in mitigating and suppressing EMI and crosstalk for aerospace designs, such as needed for NASA's Constellation Program, for returning humans to the moon and for use by our first human visitors traveling to and from Mars. Photonic Bandgap (PBG) materials are also known as artificial dielectrics, meta-materials, and photonic crystals. General PBG materials are fundamentally periodic slow-wave structures in I, 2, or 3 dimensions. By adjusting the choice of structure periodicities in terms of size and recurring structure spacings, multiple scatterings of surface waves can be created that act as a forbidden energy gap (i.e., a range of frequencies) over which nominally-conductive metallic conductors cease to be a conductor and become dielectrics. Equivalently, PBG materials can be regarded as giving rise to forbidden energy gaps in metals without chemical doping, analogous to electron bandgap properties that previously gave rise to the modem semiconductor industry 60 years ago. Electromagnetic waves cannot propagate over bandgap regions that are created with PBG materials, that is, over frequencies for which a bandgap is artificially created through introducing periodic defects

Bastin, Gary L.↗
NASA NTRS2011

Achieving the Proper Balance Between Crew and Public Safety

A paramount objective of all human-rated launch and reentry vehicle developers is to ensure that the risks to both the crew onboard and the public are minimized within reasonable cost, schedule, and technical constraints. Past experience has shown that proper attention to range safety requirements necessary to ensure public safety must be given early in the design phase to avoid additional operational complexities or threats to the safety of people onboard. This paper will outline the policy considerations, technical issues, and operational impacts regarding launch and reentry vehicle failure scenarios where crew and public safety are intertwined and thus addressed optimally in an integrated manner. Historical examples and lessons learned from both the Space Shuttle and Constellation Programs will be presented. Using these examples as context, the paper will discuss some operational, design, and analysis approaches to mitigate and balance the risks to people onboard and in the public. Manned vehicle perspectives from the FAA and Air Force organizations that oversee public safety will also be summarized. Finally, the paper will emphasize the need to factor policy, operational, and analysis considerations into the early design trades of new vehicles to help ensure that both crew and public safety are maximized to the greatest extent possible.

Gowan, John↗
NASA NTRS2010

Metabolic Costs and Biomechanics of Inclined Ambulation and Exploration Tasks in a Planetary Suit

Observations from Apollo lunar surface extravehicular activities (EVAs) and a few studies conducted in partial-gravity simulation environments have helped us understand suited human performance in reduced-gravity environments. The Constellation Program EVA Systems Project Office initiated a series of tests aimed at increasing our understanding of human performance and suit kinematics under various simulated lunar EVA conditions, including matched unsuited controls, to identify the specific metabolic costs and biomechanics of the prototype Mark III Advanced Spacesuit Technology Demonstrator. A primary goal of the series is to provide evidence-based recommendations for suit mass, center of gravity, pressure, and suit kinematic constraints that optimize human performance in partial-gravity environments. Results will be combined with studies in other lunar analogs to evaluate the effectiveness and limitations of these environments. As our understanding of suited human performance matures, different combinations of variables can be evaluated to determine whether significant interactions exist between parameters. This report provides an overview of key findings of Integrated Suit Test (IST)-2. As future tests are completed, focusing on other suit factors, analog environments, or different suits, study results will be combined and reevaluated. The series of tests comprising IST-2 was conducted from June 13, 2007 through October 24, 2007.

Aerospace environments↗
NASA NTRS2011

USM3D Simulations of Saturn V Plume Induced Flow Separation

The NASA Constellation Program included the Ares V heavy lift cargo vehicle. During the design stage, engineers questioned if the Plume Induced Flow Separation (PIFS) that occurred along Saturn V rocket during moon missions at some flight conditions, would also plague the newly proposed rocket. Computational fluid dynamics (CFD) was offered as a tool for initiating the investigation of PIFS along the Ares V rocket. However, CFD best practice guidelines were not available for such an investigation. In an effort to establish a CFD process and define guidelines for Ares V powered simulations, the Saturn V vehicle was used because PIFS flight data existed. The ideal gas, computational flow solver USM3D was evaluated for its viability in computing PIFS along the Saturn V vehicle with F-1 engines firing. Solutions were computed at supersonic freestream conditions, zero degree angle of attack, zero degree sideslip, and at flight Reynolds numbers. The effects of solution sensitivity to grid refinement, turbulence models, and the engine boundary conditions on the predicted PIFS distance along the Saturn V were discussed and compared to flight data from the Apollo 11 mission AS-506.

Deere, Karen↗
NASA NTRS2011

Ares I Aerodynamic Testing at the Boeing Polysonic Wind Tunnel

Throughout three full design analysis cycles, the Ares I project within the Constellation program has consistently relied on the Boeing Polysonic Wind Tunnel (PSWT) for aerodynamic testing of the subsonic, transonic and supersonic portions of the atmospheric flight envelope (Mach=0.5 to 4.5). Each design cycle required the development of aerodynamic databases for the 6 degree-of-freedom (DOF) forces and moments, as well as distributed line-loads databases covering the full range of Mach number, total angle-of-attack, and aerodynamic roll angle. The high fidelity data collected in this facility has been consistent with the data collected in NASA Langley s Unitary Plan Wind Tunnel (UPWT) at the overlapping condition ofMach=1.6. Much insight into the aerodynamic behavior of the launch vehicle during all phases of flight was gained through wind tunnel testing. Important knowledge pertaining to slender launch vehicle aerodynamics in particular was accumulated. In conducting these wind tunnel tests and developing experimental aerodynamic databases, some challenges were encountered and are reported as lessons learned in this paper for the benefit of future crew launch vehicle aerodynamic developments.

Pinier, Jeremy T.↗
NASA NTRS2008

Evolution of Safety Analysis to Support New Exploration Missions

NASA is currently developing the Ares I launch vehicle as a key component of the Constellation program which will provide safe and reliable transportation to the International Space Station, back to the moon, and later to Mars. The risks and costs of the Ares I must be significantly lowered, as compared to other manned launch vehicles, to enable the continuation of space exploration. It is essential that safety be significantly improved, and cost-effectively incorporated into the design process. This paper justifies early and effective safety analysis of complex space systems. Interactions and dependences between design, logistics, modeling, reliability, and safety engineers will be discussed to illustrate methods to lower cost, reduce design cycles and lessen the likelihood of catastrophic events.

Thrasher, Chard W.↗
NASA NTRS2011

Project Management Using Modern Guidance, Navigation and Control Theory

Implementing guidance, navigation, and control (GN&C) theory principles and applying them to the human element of project management and control is not a new concept. As both the literature on the subject and the real-world applications are neither readily available nor comprehensive with regard to how such principles might be applied, this paper has been written to educate the project manager on the "laws of physics" of his or her project (not to teach a GN&C engineer how to become a project manager) and to provide an intuitive, mathematical explanation as to the control and behavior of projects. This paper will also address how the fundamental principles of modern GN&C were applied to the National Aeronautics and Space Administration's (NASA) Constellation Program (CxP) space suit project, ensuring the project was managed within cost, schedule, and budget. A project that is akin to a physical system can be modeled and managed using the same over arching principles of GN&C that would be used if that project were a complex vehicle, a complex system(s), or complex software with time-varying processes (at times nonlinear) containing multiple data inputs of varying accuracy and a range of operating points. The classic GN&C theory approach could thus be applied to small, well-defined projects; yet when working with larger, multiyear projects necessitating multiple organizational structures, numerous external influences, and a multitude of diverse resources, modern GN&C principles are required to model and manage the project. The fundamental principles of a GN&C system incorporate these basic concepts: State, Behavior, Feedback Control, Navigation, Guidance and Planning Logic systems. The State of a system defines the aspects of the system that can change over time; e.g., position, velocity, acceleration, coordinate-based attitude, and temperature, etc. The Behavior of the system focuses more on what changes are possible within the system; this is denoted in the state of the system. The behavior of a system, as captured in the system modeling, when properly done will aid in accurately predicting future system performance. The Feedback Control system understands the state and behavior of the system and uses feedback to adjust control inputs into the system. The feedback, which is the right arm of the Control system, allows change to be affected in the overall system; it therefore is important to not only correctly identify the system feedback inputs, but also the system response to the feedback inputs. The Navigation system takes multiple data inputs and based on a priori knowledge of the inputs, develops a statistically based weighting of the inputs and measurements to determine the system's state. Guidance and Planning Logic of the system, complete with an understanding of where the system is (provided by the Navigation system), will in turn determine where the system needs to be and how to get it there. With any system/project, it is critical that the objective of the system/project be clearly defined -- not only to plan but to measure performance and to aid in guiding the system or the project. The system principles discussed above, which can be and have been applied to the current CxP space suit development project, can also be mapped to real-world constituents, thus allowing project managers to apply systems theories that are well defined in engineering and mathematics to a discipline (i.e., Project Management) that historically has been based in personal experience and intuition. This mapping of GN&C theory to Project Management will, in turn, permit a direct, methodical approach to Project Management, planning and control providing a tool to help predict (and guide) performance and an understanding of the project constraints, how the project can be controlled, and the impacts to external influences and inputs. This approach, to a project manager, flows down to the three bottom-line variables of cost, schedule, and scope ando the needed control of these three variables to successfully perform and complete a project.

Hill, Terry R.↗
NASA NTRS2011

Component-Level Electronic-Assembly Repair (CLEAR) Operational Concept

This Component-Level Electronic-Assembly Repair (CLEAR) Operational Concept document was developed as a first step in developing the Component-Level Electronic-Assembly Repair (CLEAR) System Architecture (NASA/TM-2011-216956). The CLEAR operational concept defines how the system will be used by the Constellation Program and what needs it meets. The document creates scenarios for major elements of the CLEAR architecture. These scenarios are generic enough to apply to near-Earth, Moon, and Mars missions. The CLEAR operational concept involves basic assumptions about the overall program architecture and interactions with the CLEAR system architecture. The assumptions include spacecraft and operational constraints for near-Earth orbit, Moon, and Mars missions. This document addresses an incremental development strategy where capabilities evolve over time, but it is structured to prevent obsolescence. The approach minimizes flight hardware by exploiting Internet-like telecommunications that enables CLEAR capabilities to remain on Earth and to be uplinked as needed. To minimize crew time and operational cost, CLEAR exploits offline development and validation to support online teleoperations. Operational concept scenarios are developed for diagnostics, repair, and functional test operations. Many of the supporting functions defined in these operational scenarios are further defined as technologies in NASA/TM-2011-216956.

Oeftering, Richard C.↗