Search NASA⌕ Search

SEARCH · Search NASA

Results for “Launch Abort Scenario”

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 37 records · Page 2

Passive Thrust Oscillation Mitigation for the CEV Crew Pallet System

The Crew Exploration Vehicle (CEV) was intended to be the next-generation human spacecraft for the Constellation Program. The CEV Isolator Strut mechanism was designed to mitigate loads imparted to the CEV crew caused by the Thrust Oscillation (TO) phenomenon of the proposed Ares I Launch Vehicle (LV). The Isolator Strut was also designed to be compatible with Launch Abort (LA) contingencies and landing scenarios. Prototype struts were designed, built, and tested in component, sub-system, and system-level testing. The design of the strut, the results of the tests, and the conclusions and lessons learned from the program will be explored in this paper.

Sammons, Matthew↗

Open-Loop Pitch Table Optimization for the Maximum Dynamic Pressure Orion Abort Flight Test

NASA has scheduled the retirement of the space shuttle orbiter fleet at the end of 2010. The Constellation program was created to develop the next generation of human spaceflight vehicles and launch vehicles, known as Orion and Ares respectively. The Orion vehicle is a return to the capsule configuration that was used in the Mercury, Gemini, and Apollo programs. This configuration allows for the inclusion of an abort system that safely removes the capsule from the booster in the event of a failure on launch. The Flight Test Office at NASA's Dryden Flight Research Center has been tasked with the flight testing of the abort system to ensure proper functionality and safety. The abort system will be tested in various scenarios to approximate the conditions encountered during an actual Orion launch. Every abort will have a closed-loop controller with an open-loop backup that will direct the vehicle during the abort. In order to provide the best fit for the desired total angle of attack profile with the open-loop pitch table, the table is tuned using simulated abort trajectories. A pitch table optimization program was created to tune the trajectories in an automated fashion. The program development was divided into three phases. Phase 1 used only the simulated nominal run to tune the open-loop pitch table. Phase 2 used the simulated nominal and three simulated off nominal runs to tune the open-loop pitch table. Phase 3 used the simulated nominal and sixteen simulated off nominal runs to tune the open-loop pitch table. The optimization program allowed for a quicker and more accurate fit to the desired profile as well as allowing for expanded resolution of the pitch table.

Stillwater, Ryan A.↗

PEG Enhancement for EM1 and EM2+ Missions

NASA is currently building the Space Launch System (SLS) Block-1 launch vehicle for the Exploration Mission 1 (EM-1) test flight. The next evolution of SLS, the Block-1B Exploration Mission 2 (EM-2), is currently being designed. The Block-1 and Block-1B vehicles will use the Powered Explicit Guidance (PEG) algorithm. Due to the relatively low thrust-to-weight ratio of the Exploration Upper Stage (EUS), certain enhancements to the Block-1 PEG algorithm are needed to perform Block-1B missions. In order to accommodate mission design for EM-2 and beyond, PEG has been significantly improved since its use on the Space Shuttle program. The current version of PEG has the ability to switch to different targets during Core Stage (CS) or EUS flight, and can automatically reconfigure for a single Engine Out (EO) scenario, loss of communication with the Launch Abort System (LAS), and Inertial Navigation System (INS) failure. The Thrust Factor (TF) algorithm uses measured state information in addition to a priori parameters, providing PEG with an improved estimate of propulsion information. This provides robustness against unknown or undetected engine failures. A loft parameter input allows LAS jettison while maximizing payload mass. The current PEG algorithm is now able to handle various classes of missions with burn arcs much longer than were seen in the shuttle program. These missions include targeting a circular LEO orbit with a low-thrust, long-burn-duration upper stage, targeting a highly eccentric Trans-Lunar Injection (TLI) orbit, targeting a disposal orbit using the low-thrust Reaction Control System (RCS), and targeting a hyperbolic orbit. This paper will describe the design and implementation of the TF algorithm, the strategy to handle EO in various flight regimes, algorithms to cover off-nominal conditions, and other enhancements to the Block-1 PEG algorithm. This paper illustrates challenges posed by the Block-1B vehicle, and results show that the improved PEG algorithm is capable for use on the SLS Block 1-B vehicle as part of the Guidance, Navigation, and Control System.

Von der Porten, Paul↗

Potential Improvements to the Nuclear Safety and Launch Approval Process for Nuclear Reactors Utilized for Space Power and Propulsion Applications

This study examines potential improvements that could be made to the nuclear safety and launch approval process for fission reactors to reduce the associated uncertainties in cost and schedule while continuing to ensure public safety and environmental protection. It concentrates on the launch approval and mission safety of fission power and propulsion applications of nuclear energy. Improvements to the launch approval process for radioisotope power systems (RPSs) are being considered elsewhere but are acknowledged throughout the report. The study considered technical, process, and organizational improvements to the launch approval processes. The study exclusively evaluated reactors that would not be started up prior to achieving a “sufficiently high orbit,” per United Nations (UN) Resolution 47/68.Potential criticality accidents were considered that could occur during a launch failure or abort or during reentry. Numerous scenarios were examined that might involve one or more Earth flybys as well as potential transportation missions that could intentionally return an active, or previously active fission reactor to Earth orbit. The Study Group was guided in its deliberations according to a number of fundamental principles. These included the paramount importance of adequate and appropriate levels of public safety and environmental protection as well as the importance of the inclusion of independent scientific, engineering, and safety reviews of the applications and proposals as a critical part of the process. Also considered was the need for the development of launch approval processes that might be different, depending upon the source of the application for launch approval, whether it be derived as a governmental launch, a commercial launch, or a hybrid/combination of the two. It is clear that all launches of nuclear reactors into space should have similar safety requirements; however, the safety review effort and the details of the analysis that are required should be commensurate with the potential hazards and the actual risk, which may differ based on the reactor design and its intended purpose. Finally, the study aimed at ensuring that whatever processes and procedures are developed should maximize the sufficiency, simplicity, and transparency of the processes. The Study Group reached five Conclusions and makes thirteen Recommendations. The Conclusions and Recommendations presented here are extensions of those presented previously in other studies. This report attempts to add specificity to the actions that need to be taken in order to move forward with successful space fission reactor programs. Without action to address the perceived and real problems in the launch approval process, designers and mission managers will be reluctant to commit the resources necessary to make space fission reactors a reality.

Camp, Allen↗

The Ejectable Data Recorder: A Lean, Risk-Informed Approach for Hardware Development

NASA is developing the Orion spacecraft to transport crew from the Earth to the Moon as part of the Artemis series of missions. To provide a crew escape capability from pre-launch through ascent, the Orion vehicle is equipped with a Launch Abort System (LAS), built by Lockheed Martin, which pulls the capsule away from the launch vehicle in the event of an abort scenario. The Ascent Abort 2 (AA-2) test flight occurred on July 2, 2019,and tested a production version of the LAS to ensure that it can operate as intended, and to collect a large data set from hundreds of sensors on the vehicle to support Orion flight certification. In the original AA-2 architecture, a single-string set of communications antennas on the LAS would downlink all of the in-flight test data to ground stations. However, that communications architecture was predicted to have data dropouts during abort and jettison of the LAS, and would not support data transmission at all after LAS jettison. As a result, a comprehensive trade study was completed, yielding the addition of antennas on the crew module (CM), a buffer/rebroadcast capability for key portions of the flight, and an ejectable data recorder (EDR) subsystem. This EDR subsystem would serve as a backup to the radio frequency (RF) communications system, and would be non-flight critical, providing a unique capability that enabled management to take a different approach with the hardware and software development. The Crew Module and Separation Ring were developed as “Class 1”Flight Hardware, albeit with some tailoring approaches to enable efficiencies. The Class 1 designation requires full rigor for flight hardware and software, documenting everything that happens to a piece of hardware from procurement through disposal, requiring a full spectrum of acceptance tests, and the highest rigor of quality assurance processes. At the other end of the spectrum, Class 3hardware is controlled, but not intended for flight, and leaves the level of rigor up to the project manager. This classification is often used for research and development projects. Similarly,Class-1E has been recently defined at NASA for ISS payloads and technology development projects that are not flight critical and do not need the full rigor of Class 1 to be successful. The EDR subsystem was challenged at commencement to adopt a skunkworks and agile-like approach to hardware development, allowing for a different risk posture than the rest of the AA-2 hardware. After initially pursuing Class 1 processes, the EDR subsystem design evolved to incorporating numerous commercial components, leading to re-designation as a Class-1E subsystem. The resulting EDR subsystem was fully successful in meeting all flight system requirements, and achieved 100% retrieval of flight test data. This paper will discuss the risk posture of the EDR subsystem and the subsequent tailoring that was enacted as part of its Class-1E status.

EDR↗

Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios

Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis. This approach becomes difficult when failure propagation paths change as a function of the system operation. Additionally, if the propagation paths represent interactions among even a modest number of components, the scenario count becomes combinatorially intractable. This paper presents an alternate approach for quantifying the probability of failure propagation in such a case. Rather than explicitly defining scenario sequences, simple physical models are created for each of the components. In this way, only the physical states and rules of component interactions must be defined, rather than event sequences for each individual scenario. Initiating failures are introduced into the system, either randomly or as defined by relative likelihood, and the failures cascade through the system via the interaction rules. This process is repeated using Monte Carlo methods and, as a result, the most probable scenarios “self-evolve” in terms of both sequence path and frequency. This approach was applied to failures occurring in the engine compartment of a space launch vehicle with four liquid rocket engines and four high-pressure helium tanks. Each engine was modeled with key components, such as turbomachinery, combustion chamber, propellant lines, and additional support systems. Three test cases were conducted with different high-energy engine failures. End results of interest included an additional engine-out failure and tank burst, which represent the loss-of-mission (LOM) and loss-of-crew (LOC) failure environments, respectively. Observations show that almost every scenario outcome is unique and that many scenarios involve complex chain reactions that are difficult to predict. This validates the usefulness of the modeling approach in assessing the overall risks to the crew during a launch vehicle abort.

Rocket Engine↗

On-Board Entry Trajectory Planning Expanded to Sub-orbital Flight

A methodology for on-board planning of sub-orbital entry trajectories is developed. The algorithm is able to generate in a time frame consistent with on-board environment a three-degree-of-freedom (3DOF) feasible entry trajectory, given the boundary conditions and vehicle modeling. This trajectory is then tracked by feedback guidance laws which issue guidance commands. The current trajectory planning algorithm complements the recently developed method for on-board 3DOF entry trajectory generation for orbital missions, and provides full-envelope autonomous adaptive entry guidance capability. The algorithm is validated and verified by extensive high fidelity simulations using a sub-orbital reusable launch vehicle model and difficult mission scenarios including failures and aborts.

Lu, Ping↗

Shuttle Abort Flight Management (SAFM) - Application Overview

One of the most demanding tasks that must be performed by the Space Shuttle flight crew is the process of determining whether, when and where to abort the vehicle should engine or system failures occur during ascent or entry. Current Shuttle abort procedures involve paging through complicated paper checklists to decide on the type of abort and where to abort. Additional checklists then lead the crew through a series of actions to execute the desired abort. This process is even more difficult and time consuming in the absence of ground communications since the ground flight controllers have the analysis tools and information that is currently not available in the Shuttle cockpit. Crew workload specifically abort procedures will be greatly simplified with the implementation of the Space Shuttle Cockpit Avionics Upgrade (CAU) project. The intent of CAU is to maximize crew situational awareness and reduce flight workload thru enhanced controls and displays, and onboard abort assessment and determination capability. SAFM was developed to help satisfy the CAU objectives by providing the crew with dynamic information about the capability of the vehicle to perform a variety of abort options during ascent and entry. This paper- presents an overview of the SAFM application. As shown in Figure 1, SAFM processes the vehicle navigation state and other guidance information to provide the CAU displays with evaluations of abort options, as well as landing site recommendations. This is accomplished by three main SAFM components: the Sequencer Executive, the Powered Flight Function, and the Glided Flight Function, The Sequencer Executive dispatches the Powered and Glided Flight Functions to evaluate the vehicle's capability to execute the current mission (or current abort), as well as more than IS hypothetical abort options or scenarios. Scenarios are sequenced and evaluated throughout powered and glided flight. Abort scenarios evaluated include Abort to Orbit (ATO), Transatlantic Abort Landing (TAL), East Coast Abort Landing (ECAL) and Return to Launch Site (RTLS). Sequential and simultaneous engine failures are assessed and landing footprint information is provided during actual entry scenarios as well as hypothetical "loss of thrust now" scenarios during ascent.

Hu, Howard↗

Analyzing the Impacts of Natural Environments on Launch and Landing Availability for NASA's Exploration Systems Development Programs

The National Aeronautics and Space Administration (NASA) is developing new capabilities for human and scientific exploration beyond Earth orbit. Natural environments information is an important asset for NASA's development of the next generation space transportation system as part of the Exploration Systems Development (ESD) Programs, which includes the Space Launch System (SLS) and Multi-Purpose Crew Vehicle (MPCV) Programs. Natural terrestrial environment conditions - such as wind, lightning and sea states - can affect vehicle safety and performance during multiple mission phases ranging from pre-launch ground processing to landing and recovery operations, including all potential abort scenarios. Space vehicles are particularly sensitive to these environments during the launch/ascent and the entry/landing phases of mission operations. The Marshall Space Flight Center (MSFC) Natural Environments Branch provides engineering design support for NASA space vehicle projects and programs by providing design engineers and mission planners with natural environments definitions as well as performing custom analyses to help characterize the impacts the natural environment may have on vehicle performance. One such analysis involves assessing the impact of natural environments to operational availability. Climatological time series of operational surface weather observations are used to calculate probabilities of meeting/exceeding various sets of hypothetical vehicle-specific parametric constraint thresholds. Outputs are tabulated by month and hour of day to show both seasonal and diurnal variation. This paper will discuss how climate analyses are performed by the MSFC Natural Environments Branch to support the ESD Launch Availability (LA) Technical Performance Measure (TPM), the SLS Launch Availability due to Natural Environments TPM, and several MPCV (Orion) launch and landing availability analyses - including the 2014 Orion Exploration Flight Test 1 (EFT-1) mission.

Altino, Karen M.↗

CFD 2030 Grand Challenge: CFD-in-the-Loop Monte Carlo Flight Simulation for Space Vehicle Design

Flight qualification of space vehicles is markedly different from those typically employed for aircraft. The concept of an extensive flight test campaign for a space vehicle does not exist, and vehicle designers must look to alternative techniques for demonstrating robust and reliable performance of their vehicles prior to operational flight. A space vehicle may undergo only a handful of flight tests in its development cycle, with each flight representing a drastically different flight phase or flight configuration. For instance, NASA’s Space Launch System (SLS) launch vehicle and Orion spacecraft will only see a total of four flight demonstrations before flying a crew on its first operational mission, and each flight demonstrates a unique vehicle configuration and/or set of flight conditions. The SLS will be flown only one time before it becomes operational (Artemis 1). The Orion spacecraft Crew Module (CM) will have been tested twice, once on a Delta IV launch vehicle (Exploration Flight Test 1) and once as a fully integrated system with the SLS launch vehicle (Artemis 1). The Orion Launch abort system will have been tested twice, once in a pad abort scenario (Pad Abort 1) and once in an inflight abort scenario (Ascent Abort 2) on a modified Peacekeeper booster. Both of these latter tests involve only a boiler plate CM, not a functional Orion spacecraft. Thus, unlike aircraft, there is very little opportunity for engineers to assess and evaluate their preflight predictions. Instead, space vehicle designers rely on Monte Carlo flight simulations with detailed dispersions of predicted nominal flight behavior to determine how robust their design is to errors and uncertainties in the flight conditions their vehicle may encounter. These Monte Carlo analyses entail thousands of trajectory simulations to demonstrate that the vehicle can meet design requirements at a specified level of reliability. From an aerodynamics and aerothermodynamics perspective, these trajectory simulations are fueled by an extensive aerodynamic database that covers the complete range of expected flight conditions, vehicle configurations, and flight attitudes expected in a given mission. Today, these databases amount to a table of engineering parameters that can be quickly interrogated by the trajectory simulator. The aerodynamic and aerothermodynamic databases are assembled via a series of ground tests, empirical and analytical analysis, physics-based computational analysis, applicable past flight performance data, and in some cases, engineering judgment. These databases generally take years to assemble for a new space vehicle system and in the case of SLS/Orion, over a decade of test and analysis have been expended to develop the extensive databases required to cover the myriad of configurations and potential flight conditions required for the system. Recently, it has been proposed that Computational Fluid Dynamic (CFD) and computing capability may be reaching a point where it is foreseeable that CFD could be integrated directly into the production trajectory simulation tools used to design NASA’s space vehicles. To demonstrate this, NASA has embarked on two demonstrations of this type of capability, one where six degree of freedom flight trajectory simulation equations are embedded in an existing CFD solver and another where a production CFD solver is loosely coupled with a production trajectory simulation tool. These efforts represent an initial demonstration of a future approach to flight trajectory simulation, but they are a far cry from the capability required to perform a full-up CFD-in-the-loop Monte Carlo trajectory simulation. Therefore, this represents a viable grand challenge for computational methods addressing space vehicle design and development. The final paper/presentation will discuss the many hurdles, beyond simply raw computational power, to realizing this grand challenge and how they map directly to the CFD Vision 2030 ojectives. Among these are the wide range of flight conditions, including accelerating/decelerating flight, encountered by a space vehicle during launch and/or entry. The vehicle can also encounter numerous configuration changes, some of which can be quite drastic, during the course of its flight, so robust, automated geometry modeling, grid generation, and adaptation will play a huge role in reaching this goal. Multiply this by 1000’s of trajectory simulations occurring simultaneously in a given Monte Carlo analysis, and the problem readily scales to absorb virtually any size of supercomputer envisioned today. The concept of CFD-in-the-loop Monte Carlo trajectory simulation poses a formidable challenge for emerging and future computing systems, and it has the potential to shave years off the development cycle for aerodynamic and aerothermodynamic performance predictions as compared to today’s space vehicle design approach.

CFD 2030↗

Surface Landing Site Weather Analysis for Constellation Program

Weather information is an important asset for NASA's Constellation Program in developing the next generation space transportation system to fly to the International Space Station, the Moon and, eventually, to Mars. Weather conditions can affect vehicle safety and performance during multiple mission phases ranging from pre-launch ground processing to landing and recovery operations, including all potential abort scenarios. Meteorological analysis is an important contributor, not only to the development and verification of system design requirements but also to mission planning and active ground operations. Of particular interest are the surface atmospheric conditions at both nominal and abort landing sites for the manned Orion capsule. Weather parameters such as wind, rain, and fog all play critical roles in the safe landing of the vehicle and subsequent crew and vehicle recovery. The Marshall Space Flight Center Natural Environments Branch has been tasked by the Constellation Program with defining the natural environments at potential landing zones. Climatological time series of operational surface weather observations are used to calculate probabilities of occurrence of various sets of hypothetical vehicle constraint thresholds, Data are available for numerous geographical locations such that statistical analysis can be performed for single sites as well as multiple-site network configurations. Results provide statistical descriptions of how often certain weather conditions are observed at the site(s) and the percentage that specified criteria thresholds are matched or exceeded. Outputs are tabulated by month and hour of day to show both seasonal and diurnal variation. This paper will describe the methodology used for data collection and quality control, detail the types of analyses performed, and provide a sample of the results that can be obtained,

Altino, Karen M.↗

Optimizing interplanetary trajectories with deep space maneuvers

Analysis of interplanetary trajectories is a crucial area for both manned and unmanned missions of the Space Exploration Initiative. A deep space maneuver (DSM) can improve a trajectory in much the same way as a planetary swingby. However, instead of using a gravitational field to alter the trajectory, the on-board propulsion system of the spacecraft is used when the vehicle is not near a planet. The purpose is to develop an algorithm to determine where and when to use deep space maneuvers to reduce the cost of a trajectory. The approach taken to solve this problem uses primer vector theory in combination with a non-linear optimizing program to minimize Delta(V). A set of necessary conditions on the primer vector is shown to indicate whether a deep space maneuver will be beneficial. Deep space maneuvers are applied to a round trip mission to Mars to determine their effect on the launch opportunities. Other studies which were performed include cycler trajectories and Mars mission abort scenarios. It was found that the software developed was able to locate quickly DSM's which lower the total Delta(V) on these trajectories.

Navagh, John↗

Predicting Orion Launch Abort Acoustics

Computational fluid dynamics (CFD) scale-resolving simulations were performed to help assess the Orion launch abort system’s vibro-acoustic environment in collaboration with the Orion Loads and Dynamics team at the Johnson Space Center (JSC). The primary objectives are to establish best practices and to validate CFD predictions for surface fluctuating pressure spectra with ground, wind tunnel, and flight test data. Excellent agreement is obtained between CFD predictions by the Cartesian adaptive mesh refinement (AMR) module of the Launch, Ascent, and Vehicle Aerodynamics (LAVA) solver and measurements from a ground test representative of the start of a pad abort scenario, and with measurements from a wind tunnel test case corresponding to a transonic, high total angle of attack ascent abort scenario. A simplified (static and at rest) simulation of a pad abort flight test shows good agreement with the flight data, whereas a more costly simulation where the vehicle is accelerating relative to the ground from rest to Mach 0.4 shows consistent over-prediction of the spectra. Simulation results for a supersonic ascent abort flight test are in reasonable agreement with the measurements, but show larger excursions in regions where non-linear interactions between the plume turbulence, shocks, and turbulent boundary layer are strongest – likely due to CFD modeling assumptions, the effect of which are discussed. Overall, the CFD results demonstrate that scale-resolving simulation methodologies like the one presented can help characterize full-scale launch abort vehicle near-field noise and can complement wind tunnel, ground and flight tests by providing trends and reducing uncertainty for scenarios that cannot or are not planned to be tested.

Orion↗

Optimal control theory determination of feasible return-to-launch-site aborts for the HL-20 Personnel Launch System vehicle

The personnel launch system (PLS) being studied by NASA is a system to complement the space shuttle and provide alternative access to space. The PLS consists of a manned spacecraft launched by an expendable launch vehicle (ELV). A candidate for the manned spacecraft is the HL-20 lifting body. In the event of an ELV malfunction during the initial portion of the ascent trajectory, the HL-20 will separate from the rocket and perform an unpowered return to launch site (RTLS) abort. This work details an investigation, using optimal control theory, of the RTLS abort scenario. The objective of the optimization was to maximize final altitude. With final altitude as the cost function, the feasibility of an RTLS abort at different times during the ascent was determined. The method of differential inclusions was used to determine the optimal state trajectories, and the optimal controls were then calculated from the optimal states and state rates.

Dutton, Kevin E.↗

Surface Landing Site Weather Analysis for NASA's Constellation Program

Weather information is an important asset for NASA's Constellation Program in developing the next generation space transportation system to fly to the International Space Station, the Moon and, eventually, to Mars. Weather conditions can affect vehicle safety and performance during multiple mission phases ranging from pre-launch ground processing of the Ares vehicles to landing and recovery operations, including all potential abort scenarios. Meteorological analysis is art important contributor, not only to the development and verification of system design requirements but also to mission planning and active ground operations. Of particular interest are the surface weather conditions at both nominal and abort landing sites for the manned Orion capsule. Weather parameters such as wind, rain, and fog all play critical roles in the safe landing of the vehicle and subsequent crew and vehicle recovery. The Marshall Space Flight Center (MSFC) Natural Environments Branch has been tasked by the Constellation Program with defining the natural environments at potential landing zones. This paper wiI1 describe the methodology used for data collection and quality control, detail the types of analyses performed, and provide a sample of the results that cab be obtained.

Altino, Karen M.↗

Shuttle Orbiter Contingency Abort Aerodynamics: Real-Gas Effects and High Angles of Attack

An important element of the Space Shuttle Orbiter safety improvement plan is the improved understanding of its aerodynamic performance so as to minimize the "black zones" in the contingency abort trajectories [1]. These zones are regions in the launch trajectory where it is predicted that, due to vehicle limitations, the Orbiter will be unable to return to the launch site in a two or three engine-out scenario. Reduction of these zones requires accurate knowledge of the aerodynamic forces and moments to better assess the structural capability of the vehicle. An interesting aspect of the contingency abort trajectories is that the Orbiter would need to achieve angles of attack as high as 60deg. Such steep attitudes are much higher than those for a nominal flight trajectory. The Orbiter is currently flight certified only up to an angle of attack of 44deg at high Mach numbers and has never flown at angles of attack larger than this limit. Contingency abort trajectories are generated using the data in the Space Shuttle Operational Aerodynamic Data Book (OADB) [2]. The OADB, a detailed document of the aerodynamic environment of the current Orbiter, is primarily based on wind-tunnel measurements (over a wide Mach number and angle-of-attack range) extrapolated to flight conditions using available theories and correlations, and updated with flight data where available. For nominal flight conditions, i.e., angles of attack of less than 45deg, the fidelity of the OADB is excellent due to the availability of flight data. However, at the off-nominal conditions, such as would be encountered on contingency abort trajectories, the fidelity of the OADB is less certain. The primary aims of a recent collaborative effort (completed in the year 2001) between NASA and Boeing were to determine: 1) accurate distributions of pressure and shear loads on the Orbiter at select points in the contingency abort trajectory space; and 2) integrated aerodynamic forces and moments for the entire vehicle and the control surfaces (body flap, speed brake, and elevons). The latter served the useful purpose of verification of the aerodynamic characteristics that went into the generation of the abort trajectories.

Prabhu, Dinesh K.↗

Space Shuttle Main Engine (SSME) Options for the Future Shuttle

The main engines for the Future Shuttle will focus on improved safety and operability. Performance enhancements may also be required for vehicle safety purposes to achieve more desirable abort scenarios. This paper discusses the potential improvements that will be considered for implementation into the Future Shuttle. Integrated engine and vehicle health management systems will achieve additional system-level reliability improvements over those currently in development. Advanced instrumentation for detecting leaks, analyzing component wear and degradation, and providing sophisticated operational data will be used for reliable engine control and scheduling maintenance operations. A new nozzle and main combustion chamber (MCC) will reduce failure probability by 50% and allow for higher thrust capability without requiring the entire engine to be redesigned. Turbopump improvements may range from minor component improvements to using 3rd-generation pumps built on the advanced concepts demonstrated by the Integrated Powerhead Development (IPD) program and the Space Launch Initiative (SLI) prototype engines.The main engines for the Future Shuttle will focus on improved safety and operability. Performance enhancements may also be required for vehicle safety purposes to achieve more desirable abort scenarios. This paper discusses the potential improvements that will be considered for implementation into the Future Shuttle. Integrated engine and vehicle health management systems will achieve additional system-level reliability improvements over those currently in development. Advanced instrumentation for detecting leaks, analyzing component wear and degradation, and providing sophisticated operational data will be used for reliable engine control and scheduling maintenance operations. A new nozzle and main combustion chamber (MCC) will reduce failure probability by 50% and allow for higher thrust capability without requiring the entire engine to be redesigned. Turbopump improvements may range from minor component improvements to using 3rd-generation pumps built on the advanced concepts demonstrated by the Integrated Powerhead Development (IPD) program and the Space Launch Initiative (SLI) prototype engines.

Jue, Fred↗

Human exploration of Mars

A systems study is underway of astronaut missions to Mars that could be accomplished over the next four decades. In addition to an emphasis on the transportation and facility infrastructure required for such missions, other relevant technologies and mission constraints are also being considered. These induce on-orbit assembly, trajectory type, launch opportunities, propellant storage, crew size, cabin pressure, artificial gravity, life-support systems, radiation hazards, power/energy storage, thermal control, human factors, communications, abort scenarios, landing techniques, exploration strategies, and science activities. A major objective of the study is to identify enabling and significantly enhancing technologies for accomplishing the goal of the human exploration of Mars.

Clark, Benton C.↗