SEARCH · Search NASA
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.
A general overview of the Orion abort flight test is presented. The contents include: 1) Abort Flight Test Project Overview; 2) DFRC Exploration Mission Directorate; 3) Abort Flight Test; 4) Flight Test Configurations; 5) Flight Test Vehicle Engineering Office; 6) DFRC FTA Scope; 7) Flight Test Operations; 8) DFRC Ops Support; 9) Launch Facilities; and 10) Scope of Launch Abort Flight Test
The Ares I Crew Launch Vehicle (CLV) is being developed by the U.S. National Aeronautics and Space Administration (NASA) to provide crew access to the International Space Station (ISS) and, together with the Ares V Cargo Launch Vehicle (CaLV), serves as one component of a future launch capability for human exploration of the Moon. During the system requirements definition process and early design cycles, NASA defined and began implementing plans for integrated ground and flight testing necessary to achieve the first human launch of Ares I. The individual Ares I flight hardware elements: the first stage five segment booster (FSB), upper stage, and J-2X upper stage engine, will undergo extensive development, qualification, and certification testing prior to flight. Key integrated system tests include the Main Propulsion Test Article (MPTA), acceptance tests of the integrated upper stage and upper stage engine assembly, a full-scale integrated vehicle dynamic test (IVDT), aerodynamic testing to characterize vehicle performance, and integrated testing of the avionics and software components. The Ares I-X development flight test will provide flight data to validate engineering models for aerodynamic performance, stage separation, structural dynamic performance, and control system functionality. The Ares I-Y flight test will validate ascent performance of the first stage, stage separation functionality, and a highaltitude actuation of the launch abort system (LAS) following separation. The Orion-1 flight test will be conducted as a full, un-crewed, operational flight test through the entire ascent flight profile prior to the first crewed launch.
The Ares I crew launch vehicle is being developed by the U.S. National Aeronautics and Space Administration (NASA) to provide crew and cargo access to the International Space Station (ISS) and, together with the Ares V cargo launch vehicle, serves as a critical component of NASA's future human exploration of the Moon. During the preliminary design phase, NASA defined and began implementing plans for integrated ground and flight testing necessary to achieve the first human launch of Ares I. The individual Ares I flight hardware elements - including the first stage five segment booster (FSB), upper stage, and J-2X upper stage engine - will undergo extensive development, qualification, and certification testing prior to flight. Key integrated system tests include the upper stage Main Propulsion Test Article (MPTA), acceptance tests of the integrated upper stage and upper stage engine assembly, a full-scale integrated vehicle ground vibration test (IVGVT), aerodynamic testing to characterize vehicle performance, and integrated testing of the avionics and software components. The Ares I-X development flight test will provide flight data to validate engineering models for aerodynamic performance, stage separation, structural dynamic performance, and control system functionality. The Ares I-Y flight test will validate ascent performance of the first stage, stage separation functionality, validate the ability of the upper stage to manage cryogenic propellants to achieve upper stage engine start conditions, and a high-altitude demonstration of the launch abort system (LAS) following stage separation. The Orion 1 flight test will be conducted as a full, un-crewed, operational flight test through the entire ascent flight profile prior to the first crewed launch.
I. Best Estimated Trajectory (BET) objective: a) Produce reconstructed trajectory of the PA-1 flight to understand vehicle dynamics and aid other post flight analyses. b) Leverage all measurement sources taken of vehicle during flight to produce the most accurate estimate of vehicle trajectory. c) Generate trajectory reconstructions of the Crew Module (CM), Launch Abort System (LAS), and Forward Bay Cover (FBC). II. BET analysis was started immediately following the PA-1 mission and was completed in September, 2010 a) Quick look version of BET released 5/25/2010: initial repackaging of SIGI data. b) Preliminary version of BET released 7/6/2010: first blended solution using available sources of external measurements. c) Final version of BET released 9/1/2010: final blended solution using all available sources of data.
Marine weather and related parameters such as wind, ocean wave height and period, air temperature, sea surface temperature, visibility, and potential for icing are critical to the design, operation, and safety of crewed space vehicles. The National Aeronautics and Space Administration's (NASA's) Constellation Program requires detailed assessment of marine weather related parameters that may be encountered during launch, abort, landing, and crew rescue operations for the crewed Axes/Orion space vehicles. This information is required for both space vehicle design and operational purposes. The space vehicles must be designed such that they cam withstand the environment they are likely to encounter. The crewed Axes/Orion space vehicles will launch from NASA's Kennedy Space Center (KSC), Florida for both International Space Station (ISS) missions with 51.6deg inclination orbits and lunar missions with approximately 280 inclination orbits. Since both missions will fly ever the Atlantic Ocean on ascent to orbit and will fly over the Pacific Ocean on descent from orbit, an unlikely but possible emergency abort could require parachuting the Orion capsule and crew into the ocean. This situation could potentially put the crew in an isolated and hazardous environment for severn hours while they await rescue. Therefore, abort, landing, and crew rescue elements of the Constellation Program must address weather related parameters on a global scale. This paper describes buoy measurement data, sea surface temperature satellite data, and sea state computer model data that are being utilized by the Constellation Program to address these design and operational issues.
Marine weather and related parameters such as wind, ocean wave height and period, air temperature, sea surface temperature, visibility, and potential for icing are critical to the design, operation, and safety of crewed space vehicles. The National Aeronautics and Space Administration's (NASA's) Constellation Program requires detailed assessment of marine weather related parameters that may be encountered during launch, abort, landing, and crew rescue operations for the crewed Ares/Orion space vehicles. This information is required for both space vehicle design and operational purposes. The space vehicles must be designed such that they can withstand the environment they are likely to encounter. The crewed Ares/Orion space vehicles will launch from NASA's Kennedy Space Center (KSC), Florida for both International Space Station (ISS) missions with 51.6 o inclination orbits and lunar missions with approximately 28 inclination orbits. Since both missions will fly over the Atlantic Ocean on ascent to orbit and will fly over the Pacific Ocean on descent from orbit, an unlikely but possible emergency abort could require parachuting the Orion capsule and crew into the ocean. This situation could potentially put the crew in an isolated and hazardous environment for several hours while they await rescue. Therefore, abort, landing, and crew rescue elements of the Constellation Program must address weather related parameters on a global scale. This paper describes buoy measurement data, sea surface temperature satellite data, and sea state computer model data that are being utilized by the Constellation Program to address these design and operational issues.
This paper presents information regarding the nosecap Flush Airdata Sensing (FADS) system on Orion’s Pad Abort 1 (PA-1) vehicle. The purpose of the nosecap FADS system was to test whether or not useful data could be obtained from a FADS system if it was placed in close proximity to firing rocket nozzles like the Attitude Control Motor (ACM) nozzles on the PA-1 Launch Abort System. The nosecap FADS system used pressure measurements from a series of pressure ports which were arranged in a cruciform pattern and flush with the surface of the vehicle to estimate values of angle of attack, angle of sideslip, Mach number, impact pressure, and freestream static pressure. This paper will present the algorithms employed by the FADS system along with the development of the calibration datasets and a comparison of the final results to the Best Estimated Trajectory (BET) data for PA-1. Also presented in this paper is a Computational Fluid Dynamics (CFD) study to explore the impact of the ACM on the nosecap FADS system. The comparison of the nosecap FADS system results to the BET and the CFD study showed that more investigation is needed to quantify the impact of the firing rocket motors on the FADS system.
This presentation presents information regarding the nose-cap flush airdata sensing (FADS) system on Orion's Pad Abort 1 (PA-1) vehicle. The purpose of the nose-cap FADS system was to test whether or not useful data could be obtained from a FADS system if it was placed in close proximity to firing rockets nozzles like the attitude control motor (ACM) nozzles on the PA-1 launch abort system (LAS). The nose-cap FADS systems use pressure measurements from a series of pressure ports which are arranged in a cruciform pattern and flush with the surface of the vehicle to estimate values of angle of attack, angle of side-slip, Mach number, impact pressure and free-stream static pressure.
The need for robust and reliable access from space is clearly demonstrated by the recent loss of the Space Shuttle Columbia; as well as the NASA s goals to get the Shuttle re-flying and extend its life, build new vehicles for space access, produce successful robotic landers and s a q k ret~rr? ~llisrions, and maximize the science content of ambitious outer planets missions that contain nuclear reactors which must be safe for re-entry after possible launch aborts. The technology lynch pin of access from space is hypersonic entry systems such the thermal protection system, along with navigation, guidance and control (NG&C). But it also extends to descent and landing systems such as parachutes, airbags and their control systems. Current space access technology maturation programs such as NASA s Next Generation Launch Technology (NGLT) program or the In-Space Propulsion (ISP) program focus on maturing laboratory demonstrated technologies for potential adoption by specific mission applications. A key requirement for these programs success is a suitable queue of innovative technologies and advanced concepts to mature, including mission concepts enabled by innovative, cross cutting technology advancements. When considering space access, propulsion often dominates the capability requirements, as well as the attention and resources. From the perspective of access from space some new cross cutting technology drivers come into view, along with some new capability opportunities. These include new miniature vehicles (micro, nano, and picosats), advanced automated systems (providing autonomous on-orbit inspection or landing site selection), and transformable aeroshells (to maximize capabilities and minimize weight). This paper provides an assessment of the technology drivers needed to meet future access from space mission requirements, along with the mission capabilities that can be envisioned from innovative, cross cutting access from space technology developments.
We will discuss the feasibility of using a minimally-modified variant of a SpaceX Dragon capsule as a low-cost, large-capacity, near-term, Mars lander for scientific and human-precursor missions. We have been evaluating such a Red Dragon platform as an option for a Discovery Program mission concept. A Red Dragon lander has the potential to be low cost primarily because it would be derived from a routinely-flying spacecraft. Dragon is being developed to ferry cargo and crew to and from the International Space Station (ISS). The cargo variant is currently undergoing test flights, which will be followed by standard ISS cargo missions and, eventually, crewed flights. The human variant, unlike other Earth-return vehicles, appears to also have most of the capabilities necessary to land on Mars. In particular, it has a set of high-thrust, throttleable, storable bi-propellant Super- Draco engines integrated directly into the capsule which are intended for launch abort and powered landings on Earth. These thrusters suggest the possibility of a parachute-free, fully-propulsive deceleration at Mars from supersonic speeds to the surface. Concepts for large, human-relevant landers (see, e.g., [1]) also often employ supersonic retro-propulsion; Red Dragon's entry, descent, and landing approach would scale to those landers. Further, SpaceX's Falcon Heavy launch vehicle, currently under development and expected to have its first flight in 2013, will be capable of sending Dragon on a trajectory to Mars. We will discuss our motivation for exploring a Red Dragon lander, the primary technical questions which determine its feasibility, and the current results of our analysis. In particular, we will examine entry, descent, and landing (EDL) in detail. We will describe the modifications to Dragon necessary for interplanetary cruise, EDL, and operations on the Martian surface.
The NASA Constellation Program's Ares I-X rocket launched successfully on October 28, 2009 collecting valuable data and providing risk reduction for the Ares I project. The Ares I-X mission was formulated and implemented in less than four years commencing with the Exploration Systems Architecture Study in 2005. The test configuration was founded upon assets and processes from other rocket programs including Space Shuttle, Atlas, and Peacekeeper. For example, the test vehicle's propulsion element was a Shuttle Solid Rocket Motor. The Ares I-X rocket comprised a motor assembly, mass and outer mold line simulators of the Ares I Upper Stage, Orion Spacecraft and Launch Abort System, a roll control system, avionics, and other miscellaneous components. The vehicle was 327 feet tall and weighed approximately 1,800,000 pounds. During flight the rocket reached a maximum speed of Mach 4.8 and an altitude of 150,000 feet. The vehicle demonstrated staging at 130,000 feet, tested parachutes for recovery of the motor, and utilized approximately 900 sensors for data collection. Developing a new launch system and preparing for a safe flight presented many challenges. Specific challenges included designing a system to withstand the environments, manufacturing large structures, and re-qualifying heritage hardware. These and other challenges, if not mitigated, may have resulted in test cancellation. Ares I-X succeeded because the mission was founded on carefully derived objectives, led by decisive and flexible management, implemented by an exceptionally talented and dedicated workforce, and supported by a thorough independent review team. Other major success factors include the use of proven heritage hardware, a robust System Integration Laboratory, multi-NASA center and contractor team, concurrent operations, efficient vehicle assembly, effective risk management, and decentralized element development with a centralized control board. Ares I-X was a technically complex test that required creative thinking, risk taking, and a passion to succeed.
On October 28, 2009, NASA launched Ares I-X, the first flight test of the Constellation Program that will send human beings to the Moon and beyond. This successful test is the culmination of a three-and-a-half-year, multi-center effort to design, build, and fly the first demonstration vehicle of the Ares I crew launch vehicle, the successor vehicle to the Space Shuttle. The suborbital mission was designed to evaluate the atmospheric flight characteristics of a vehicle dynamically similar to Ares I; perform a first stage separation and evaluate its effects; characterize and control roll torque; stack, fly, and recover a solid-motor first stage testing the Ares I parachutes; characterize ground, flight, and reentry environments; and develop and execute new ground hardware and procedures. Built from existing flight and new simulator hardware, Ares I-X integrated a Shuttle-heritage four-segment solid rocket booster for first stage propulsion, a spacer segment to simulate a five-segment booster, Peacekeeper axial engines for roll control, and Atlas V avionics, as well as simulators for the upper stage, crew module, and launch abort system. The mission leveraged existing logistical and ground support equipment while also developing new ones to accommodate the first in-line rocket for flying astronauts since the Saturn IB last flew from Kennedy Space Center (KSC) in 1975. This paper will describe the development and integration of the various vehicle and ground elements, from conception to stacking in KSC s Vehicle Assembly Building; hardware performance prior to, during, and after the launch; and preliminary lessons and data gathered from the flight. While the Constellation Program is currently under review, Ares I-X has and will continue to provide vital lessons for NASA personnel in taking a vehicle concept from design to flight.
Integrated vehicle testing will be critical to ensuring proper vehicle integration of the Ares I crew launch vehicle and Ares V cargo launch vehicle. The Ares Projects, based at Marshall Space Flight Center in Alabama, created the Flight and Integrated Test Office (FITO) as a separate team to ensure that testing is an integral part of the vehicle development process. As its name indicates, FITO is responsible for managing flight testing for the Ares vehicles. FITO personnel are well on the way toward assembling and flying the first flight test vehicle of Ares I, th Ares I-X. This suborbital development flight will evaluate the performance of Ares I from liftoff to first stage separation, testing flight control algorithms, vehicle roll control, separation and recovery systems, and ground operations. Ares I-X is now scheduled to fly in summer 2009. The follow-on flight, Ares I-Y, will test a full five-segment first stage booster and will include cryogenic propellants in the upper stage, an upper stage engine simulator, and an active launch abort system. The following flight, Orion 1, will be the first flight of an active upper stage and upper stage engine, as well as the first uncrewed flight of an Orion spacecraft into orbit. The Ares Projects are using an incremental buildup of flight capabilities prior to the first operational crewed flight of Ares I and the Orion crew exploration vehicle in 2015. In addition to flight testing, the FITO team will be responsible for conducting hardware, software, and ground vibration tests of the integrated launch vehicle. These efforts will include verifying hardware, software, and grou handling interfaces. Through flight and integrated testing, the Ares Projects will identify and mitigate risks early the United States prepares to take its next giant leaps to the Moon and beyond.
Integrated vehicle testing will be critical to ensuring proper vehicle integration of the Ares I crew launch vehicle and Ares V cargo launch vehicle. The Ares Projects, based at Marshall Space Flight Center in Alabama, created the Flight and Integrated Test Office (FITO) as a separate team to ensure that testing is an integral part of the vehicle development process. As its name indicates, FITO is responsible for managing flight testing for the Ares vehicles. FITO personnel are well on the way toward assembling and flying the first flight test vehicle of Ares I, the Ares I-X. This suborbital development flight will evaluate the performance of Ares I from liftoff to first stage separation, testing flight control algorithms, vehicle roll control, separation and recovery systems, and ground operations. Ares I-X is now scheduled to fly in summer 2009. The follow-on flight, Ares I-Y, will test a full five-segment first stage booster and will include cryogenic propellants in the upper stage, an upper stage engine simulator, and an active launch abort system. The following flight, Orion 1, will be the first flight of an active upper stage and upper stage engine, as well as the first uncrewed flight of an Orion spacecraft into orbit. The Ares Projects are using an incremental buildup of flight capabilities prior to the first operational crewed flight of Ares I and the Orion crew exploration vehicle in 2015. In addition to flight testing, the FITO team will be responsible for conducting hardware, software, and ground vibration tests of the integrated launch vehicle. These efforts will include verifying hardware, software, and ground handling interfaces. Through flight and integrated testing, the Ares Projects will identify and mitigate risks early as the United States prepares to take its next giant leaps to the Moon and beyond.
The Ares I-X flight test, scheduled for 2009, is the first opportunity for the Constellation Program and Ares Projects to obtain important data on the in-flight loads, first stage recovery, and ground-handling characteristics of the Ares I crew launch vehicle. The flight test vehicle will incorporate a mix of flight and mockup hardware, reflecting an acceptable representation of the mass and outer mold line characteristics of the operational Ares I vehicle. It will be powered by a four-segment solid rocket motor from the Space Shuttle inventory and will include a fifth, inert spacer segment and new forward structures to make it the same shape as the Ares I first stage. The vehicle also includes mass simulators for the upper stage, Orion crew module, and launch abort system to match the outer mold line of Ares I; an active roll control system; and avionics derived from Shuttle and Atlas hardware. This suborbital mission will take the flight test vehicle from stacking in the Vehicle Assembly Building (VAB) at Kennedy Space Center (KSC) through liftoff, maximum dynamic pressure, first stage separation, and recovery. Ares I-X presented NASA with unique project management challenges. This presentation will address those unique challenges, including managing a virtual nationwide team under a constrained timeline; designing and building the launch vehicle and ground systems; working concurrently with Space Shuttle activities; and integrating technical and management functions. It also will identify key data collected and lessons learned from the flight that will be applied to future exploration missions.
Ares I-X will be NASA's first test flight for a new human-rated launch vehicle since 1981, and the team is well on its way toward completing the vehicle's design and hardware fabrication for an April 2009 launch. This uncrewed suborbital development test flight gives NASA its first opportunities to: gather critical data about the flight dynamics of the integrated launch vehicle; understand how to control its roll during flight; better characterize the stage separation environments during future flight; and demonstrate the first stage recovery system. The Ares I-X Flight Test Vehicle (FTV) incorporates a mix of flight and mockup hardware. It is powered by a four-segment solid rocket booster, and will be modified to include a fifth, spacer segment; the upper stage, Orion crew exploration vehicle, and launch abort system are simulator hardware to make the FTV aerodynamically similar to the same size, shape, and weight of Ares I. The Ares IX first stage includes an existing Shuttle solid rocket motor and thrust vector control system controlled by an Ascent Thrust Vector Controller (ATVC) designed and built by Honeywell International. The avionics system will be tested in a dedicated System Integration Laboratory located at Lockheed Martin Space Systems (LMSS) in Denver, Colorado. The Upper Stage Simulator (USS) is made up of cylindrical segments that will be stacked and integrated at Kennedy Space Center (KSC) for launch. Glenn Research Center is already building these segments, along with their internal access structures. The active Roll Control System (RoCS) includes two thruster units harvested from Peacekeeper missiles. Duty cycle testing for RoCS was conducted, and fuel tanking and detanking tests will occur at KSC in early 2008. This important flight will provide valuable experience for the ground operations team in integrating, stacking, and launching Ares I. Data from Ares I-X will ensure the safety and reliability of America's newest launch vehicle.
Ascent vehicles in the developmental stages of the program are instrumented with Developmental Flight Instrumentation (DFI) sensors. These sensors establish a link between a vehicle and engineers on the ground to communicate conditions experienced during the ascent. These data are then compared to pre-flight predictions used in the design process. The aerodynamic, acoustic, thermal, and structural data are either telemetered to ground stations during the ascent or stored on the vehicle for post-flight recovery and archived at the Huntsville Operations Support Center (HOSC). Following NASA's Artemis I Space Launch System (SLS) launch on November 16, 2020, data from three separate programs are available at the HOSC: Space Shuttle Program (Space Transport System (STS)), Constellation Program (Ares I-X), and Artemis Program (SLS). Availability of these data presents a unique opportunity to examine DFI data from three distinct vehicles and analyze the broad impact of the DFI data on the understanding of transonic aerodynamics. Classical spectrogram and Empirical Mode Decomposition techniques were used to present data in aerodynamically analogous regions on each vehicle. On the SLS and Ares I-X, a region downstream of the Launch Abort System motors was chosen. Comparing SLS and the STS, a region downstream of booster Froward Attach Hardware was selected as analogous flow region. Some other regions of interest were also identified. Although similarities in flow features on three vehicles were identified, some challenges in the comparison were also encountered, especially due to poor temporal and spatial resolution of Shuttle measurements.
Ascent vehicles in the developmental stages of the program are instrumented with Developmental Flight Instrumentation (DFI) sensors. These sensors establish a link between a vehicle and engineers on the ground to communicate conditions experienced during the ascent. These data are then compared to pre-flight predictions used in the design process. The aerodynamic, acoustic, thermal, and structural data are either telemetered to ground stations during the ascent or stored on the vehicle for post-flight recovery and archived at the Huntsville Operations Support Center (HOSC). Following NASA's Artemis I Space Launch System (SLS) launch on November 16, 2020, data from three separate programs are available at the HOSC: Space Shuttle Program (Space Transport System (STS)), Constellation Program (Ares I-X), and Artemis Program (SLS). Availability of these data presents a unique opportunity to examine DFI data from three distinct vehicles and analyze the broad impact of the DFI data on the understanding of transonic aerodynamics. Classical spectrogram and Empirical Mode Decomposition techniques were used to present data in aerodynamically analogous regions on each vehicle. On the SLS and Ares I-X, a region downstream of the Launch Abort System motors was chosen. Comparing SLS and the STS, a region downstream of booster Froward Attach Hardware was selected as analogous flow region. Some other regions of interest were also identified. Although similarities in flow features on three vehicles were identified, some challenges in the comparison were also encountered, especially due to poor temporal and spatial resolution of Shuttle measurements.