Search NASA⌕ Search

SEARCH · Search NASA

Results for “Launch Abort System”

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 73 records · Page 4

Constellation Training Facility Support

The National Aeronautics and Space Administration is developing the next set of vehicles that will take men back to the moon under the Constellation Program. The Constellation Training Facility (CxTF) is a project in development that will be used to train astronauts, instructors, and flight controllers on the operation of Constellation Program vehicles. It will also be used for procedure verification and validation of flight software and console tools. The CxTF will have simulations for the Crew Exploration Vehicle (CEV), Crew Module (CM), CEV Service Module (SM), Launch Abort System (LAS), Spacecraft Adapter (SA), Crew Launch Vehicle (CLV), Pressurized Cargo Variant CM, Pressurized Cargo Variant SM, Cargo Launch Vehicle, Earth Departure Stage (EDS), and the Lunar Surface Access Module (LSAM). The Facility will consist of part-task and full-task trainers, each with a specific set of mission training capabilities. Part task trainers will be used for focused training on a single vehicle system or set of related systems. Full task trainers will be used for training on complete vehicles and all of its subsystems. Support was provided in both software development and project planning areas of the CxTF project. Simulation software was developed for the hydraulic system of the Thrust Vector Control (TVC) of the ARES I launch vehicle. The TVC system is in charge of the actuation of the nozzle gimbals for navigation control of the upper stage of the ARES I rocket. Also, software was developed using C standards to send and receive data to and from hand controllers to be used in CxTF cockpit simulations. The hand controllers provided movement in all six rotational and translational axes. Under Project Planning & Control, support was provided to the development and maintenance of integrated schedules for both the Constellation Training Facility and Missions Operations Facilities Division. These schedules maintain communication between projects in different levels. The CxTF support provided is one that requires continuous maintenance since the project is still on initial development phases.

Flores, Jose M.↗

PIV Measurements of the CEV Hot Abort Motor Plume for CFD Validation

NASA s next manned launch platform for missions to the moon and Mars are the Orion and Ares systems. Many critical aspects of the launch system performance are being verified using computational fluid dynamics (CFD) predictions. The Orion Launch Abort Vehicle (LAV) consists of a tower mounted tractor rocket tasked with carrying the Crew Module (CM) safely away from the launch vehicle in the event of a catastrophic failure during the vehicle s ascent. Some of the predictions involving the launch abort system flow fields produced conflicting results, which required further investigation through ground test experiments. Ground tests were performed to acquire data from a hot supersonic jet in cross-flow for the purpose of validating CFD turbulence modeling relevant to the Orion Launch Abort Vehicle (LAV). Both 2-component axial plane Particle Image Velocimetry (PIV) and 3-component cross-stream Stereo Particle Image Velocimetry (SPIV) measurements were obtained on a model of an Abort Motor (AM). Actual flight conditions could not be simulated on the ground, so the highest temperature and pressure conditions that could be safely used in the test facility (nozzle pressure ratio 28.5 and a nozzle temperature ratio of 3) were used for the validation tests. These conditions are significantly different from those of the flight vehicle, but were sufficiently high enough to begin addressing turbulence modeling issues that predicated the need for the validation tests.

Wernet, Mark↗

Orion Pad Abort 1 GN and C Design and Development

The first flight test of the Orion Abort Flight Test project is scheduled to launch in Spring 2010. This flight test is known as Pad Abort 1 (PA-1) and it is intended to accomplish a series of flight test objectives, including demonstrating the capability of the Launch Abort System (LAS) to propel the Crew Module (CM) to a safe distance from a launch vehicle during a pad abort. The PA-1 Flight Test Article (FTA) is actively controlled by a guidance, navigation, and control (GN&C) system for much of its flight. The purpose of this paper is to describe the design, development, and analysis of the PA-1 GN&C system. A description of the technical solutions that were developed to meet the challenge of satisfying many competing requirements is presented. A historical perspective of how the Orion LAV compares to the Apollo Launch Escape Vehicle (LEV) design will also be included.

Medina, Edgar A.↗

Mode Selection Techniques in Variable Mass Flexible Body Modeling

In developing a flexible body spacecraft simulation for the Launch Abort System of the Orion vehicle, when a rapid mass depletion takes place, the dynamics problem with time varying eigenmodes had to be addressed. Three different techniques were implemented, with different trade-offs made between performance and fidelity. A number of technical issues had to be solved in the process. This paper covers the background of the variable mass flexibility problem, the three approaches to simulating it, and the technical issues that were solved in formulating and implementing them.

Launch Abort System↗

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↗

The NASA MLAS Flight Demonstration - A Review of a Highly Successful Test

NASA has tested the Max Launch Abort System (MLAS) as a risk-mitigation design should problems arise with the baseline Orion spacecraft launch abort design. The Max in MLAS is not Maximum, but rather dedicated to Max Faget, The renowned NASA Spacecraft designer. In the fall of 2009, the mission was flown, with great success, from the NASA Wallops Flight Facility. The MLAS flight test vehicle prototype consists of a boost ring, coast ring, and the MLAS fairing itself, which houses an Orion Command Module (CM) boilerplate. The objective of the MLAS flight test is to reorient the fairing with the CM, weighing approximately 29,000 lbs and traveling 290 fps, 180 degrees to an orientation suitable for the release of the CM during a pad abort and low altitude abort. Although multiple parachute deployments are used in the MLAS flight test vehicle to complete its objective, there are only two parachute types employed in the flight test. Five of the nine parachutes used for MLAS are 27.6 ft DO ribbon parachutes, and the remaining four are standard G-12 cargo parachutes. This paper presents an overview of the 27.6 ft DO ribbon parachute system employed on the MLAS flight test vehicle for coast ring separation, fairing reorientation, and as drogue parachutes for the CM after separation from the fairing. Discussion will include: the process used to select this design, previously proven as a spin/stall recovery parachute; descriptions of all components of the parachute system; the minor modifications necessary to adapt the parachute to the MLAS program; the techniques used to analyze the parachute for the multiple roles it performs; a discussion of the rigging techniques used to interface the parachute system to the vehicle; a brief description of how the evolution of the program affected parachute usage and analysis; and a summary of the results of the flight test, including video of the flight test and subsequent summary analysis. . A discussion of the flight test which was highly successful as well as the flight test observations will be a significant portion of the review.

Taylor, Anthony P.↗

A Review of the NASA MLAS Flight Demonstration

The NASA Engineering and Safety Center (NESC) has tested the Max Launch Abort System (MLAS) as a risk-mitigation design should problems arise with the baseline Orion spacecraft launch abort design. The Max in MLAS is not Maximum, but rather dedicated to Max Faget, the renowned NASA Spacecraft designer. In July 2009, the mission was flown, with great success, from the NASA Wallops Flight Facility. The MLAS flight test vehicle prototype consists of a boost skirt, coast skirt, and the MLAS fairing itself, which houses an Orion Command Module (CM) boilerplate. The objective of the MLAS flight test is to reorient the fairing with the CM, weighing approximately 29,000 lbs and traveling 290 fps, 180 degrees to an orientation suitable for the release of the CM during a pad abort or low altitude abort. The boost and coast skirts provide the necessary thrust and stability to establish the flight test conditions and are released prior to the reorientation of the fairing. A secondary test objective after successful release of the CM from the fairing is to demonstrate the removal of the CM forward bay cover (FBC) with the CM drogue parachutes, and subsequent deployment of the CM main parachutes attached to the FBC. Although multiple parachute deployments are used in the MLAS flight test vehicle to complete its objective, there are only two parachute types employed in the flight test. Five of the nine parachutes used for MLAS are 27.6 ft DO ribbon parachutes already proven as a spin/stall parachute for military aircraft, and the remaining four are G-12 cargo parachutes modified for increased strength and reefing. This paper presents an overview of the 27.6 ft DO ribbon parachute system employed on the MLAS flight test vehicle for coast skirt separation, fairing reorientation, and as CM drogue parachutes. Discussion will include: the process used to select this design; descriptions of all components of the parachute system; the minor modifications necessary to adapt the parachute to the MLAS program; the techniques used to analyze the parachute for the multiple roles it performs including discussions of how the evolution of the program affected parachute usage and analysis; a summary of the results of the highly successful flight test, including video of the flight test; and an overview of the subsequent post-test analysis.

Taylor, Anthony P.↗

TPSAS-NF1676L-11132-DND

The Orion Pad Abort 1 Flight Test occurred on May 6th, 2010 at White Sands Missile Range in New Mexico. The test was the first for the Orion vehicle and was primarily a test of the Orion Launch Abort System’s ability to execute an abort from the launch pad. The test was successful, and, in most cases, results were well within predicted outcomes. For this test, the thermal control subsystem was an inherent part of the flight operations team. The thermal team provided pre-launch predictions of component temperatures, set component temperature limits, and monitored those limits during the flight operations process as part of the primary flight operations team. The thermal team was also responsible for day-of-flight predictions of the main abort motor’s propellant mean bulk temperature, a key launch constraint for the test. After the test, thermal data was collected, reviewed, and compared against pre-launch predictions showing very good agreement in most areas. Based on the pre-test and flight operations experience, a detailed list of lessons learned has been developed and will be reviewed prior to potential future Orion or other such flight tests.

Joseph F Gasbarre↗

TPSAS-NF1676L-11021-DND

The Orion Pad Abort 1 Flight Test occurred on May 6th, 2010 at White Sands Missile Range in New Mexico. The test was the first for the Orion vehicle and was primarily a test of the Orion Launch Abort System’s ability to execute an abort from the launch pad. The test was successful and in most cases results were well within predicted outcomes. For this test, the thermal control subsystem was an inherent part of the flight operations team. The thermal team provided pre-launch predictions of component temperatures, set component temperature limits, and monitored those limits during the flight operations process as part of the primary flight operations team. The thermal team was also responsible for day-of-flight predictions of the main abort motor’s propellant mean bulk temperature, a key launch constraint for the test. After the test, thermal data was collected, reviewed, and compared against pre-launch predictions showing very good agreement in most areas. Based on the pre-test and flight operations experience, a detailed list of lessons learned has been developed and will be reviewed prior to potential future Orion or other such flight tests.

Joseph F Gasbarre↗

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↗

Launch Pad Escape System Design (Human Spaceflight)

A launch pad escape system for human spaceflight is one of those things that everyone hopes they will never need but is critical for every manned space program. Since men were first put into space in the early 1960s, the need for such an Emergency Escape System (EES) has become apparent. The National Aeronautics and Space Administration (NASA) has made use of various types of these EESs over the past 50 years. Early programs, like Mercury and Gemini, did not have an official launch pad escape system. Rather, they relied on a Launch Escape System (LES) of a separate solid rocket motor attached to the manned capsule that could pull the astronauts to safety in the event of an emergency. This could only occur after hatch closure at the launch pad or during the first stage of flight. A version of a LES, now called a Launch Abort System (LAS) is still used today for all manned capsule type launch vehicles. However, this system is very limited in that it can only be used after hatch closure and it is for flight crew only. In addition, the forces necessary for the LES/LAS to get the capsule away from a rocket during the first stage of flight are quite high and can cause injury to the crew. These shortcomings led to the development of a ground based EES for the flight crew and ground support personnel as well. This way, a much less dangerous mode of egress is available for any flight or ground personnel up to a few seconds before launch. The early EESs were fairly simple, gravity-powered systems to use when thing's go bad. And things can go bad very quickly and catastrophically when dealing with a flight vehicle fueled with millions of pounds of hazardous propellant. With this in mind, early EES designers saw such a passive/unpowered system as a must for last minute escapes. This and other design requirements had to be derived for an EES, and this section will take a look at the safety design requirements had to be derived for an EES, and this section will take a look at the safety design aspects for a launch pad escape system.

Maloney, Kelli↗

Development and Qualification of the Primary Structure of the Orion European Service Module

This paper presents an overview of the development and qualification test campaign for the primary structure of the European Service Module of ORION, the NASA spacecraft which will serve the future human exploration missions to the Moon, Mars and beyond. Under an agreement between NASA and ESA, the ORION will be powered by a European Service Module (ESM), providing also water and oxygen for astronauts' life sustainability. The development and qualification of the European Service Module (ESM) is under ESA responsibility with Airbus Defense and Space as the prime contractor. Thales Alenia Space Italia is responsible for design development, manufacturing, assembly and qualification of the Structure subsystem. The European Service Module, installed onto the launch adapter, shall support the crew module with its adapter and a launch abort system. It shall sustain: - A combination of global and local launch loads during lift off and ascent phases, - On orbit loads induced by engine firing for orbital transfers and attitude control. The ESM structure is based on a core made of Composite Fiber Reinforced Polymer (CFRP) sandwich panels complemented by aluminum alloy platforms, longerons and secondary structures. A development campaign has been implemented in order to define and validate composite parts' strength allowable values for design: coupon tests at material level, test at component level up to breadboards tests performed on main structural components (composite to metallic joints, and at panels' discontinuities). An incremental approach as defined in [1] has been followed. A qualification static test campaign at primary structure assembly level has been implemented in order to validate the design against static stiffness and ultimate strength as well as to correlate the structural Finite Element Model (FEM) used for sizing and confirm the margins of safety. The tests have been performed successfully by Thales Alenia Space Italia (TAS-I) on two flight representative structural models (STA1, STA2), in Turin facilities (Italy) between August 2015 and March 2017, with engineering support of technical representatives from Airbus, ESA, NASA and LMCO. The main development and qualification test activities and associated results are presented and discussed in the paper

Structural Testing↗

Real-Time Simulation of Ares I Launch Vehicle

The Ares Real-Time Environment for Modeling, Integration, and Simulation (ARTEMIS) has been developed for use by the Ares I launch vehicle System Integration Laboratory (SIL) at the Marshall Space Flight Center (MSFC). The primary purpose of the Ares SIL is to test the vehicle avionics hardware and software in a hardware-in-the-loop (HWIL) environment to certify that the integrated system is prepared for flight. ARTEMIS has been designed to be the real-time software backbone to stimulate all required Ares components through high-fidelity simulation. ARTEMIS has been designed to take full advantage of the advances in underlying computational power now available to support HWIL testing. A modular real-time design relying on a fully distributed computing architecture has been achieved. Two fundamental requirements drove ARTEMIS to pursue the use of high-fidelity simulation models in a real-time environment. First, ARTEMIS must be used to test a man-rated integrated avionics hardware and software system, thus requiring a wide variety of nominal and off-nominal simulation capabilities to certify system robustness. The second driving requirement - derived from a nationwide review of current state-of-the-art HWIL facilities - was that preserving digital model fidelity significantly reduced overall vehicle lifecycle cost by reducing testing time for certification runs and increasing flight tempo through an expanded operational envelope. These two driving requirements necessitated the use of high-fidelity models throughout the ARTEMIS simulation. The nature of the Ares mission profile imposed a variety of additional requirements on the ARTEMIS simulation. The Ares I vehicle is composed of multiple elements, including the First Stage Solid Rocket Booster (SRB), the Upper Stage powered by the J- 2X engine, the Orion Crew Exploration Vehicle (CEV) which houses the crew, the Launch Abort System (LAS), and various secondary elements that separate from the vehicle. At launch, the integrated vehicle stack is composed of these stages, and throughout the mission, various elements separate from the integrated stack and tumble back towards the earth. ARTEMIS must be capable of simulating the integrated stack through the flight as well as propagating each individual element after separation. In addition, abort sequences can lead to other unique configurations of the integrated stack as the timing and sequence of the stage separations are altered.

Tobbe, Patrick↗

Orion Exploration Flight Test Post-Flight Inspection and Analysis

The multipurpose crew vehicle, Orion, is being designed and built for NASA to handle the rigors of crew launch, sustainment and return from scientific missions beyond Earth orbit. In this role, the Orion vehicle is meant to operate in the space environments like the naturally occurring meteoroid and the artificial orbital debris environments (MMOD) with successful atmospheric reentry at the conclusion of the flight. As a result, Orion's reentry module uses durable porous, ceramic tiles on almost thirty square meters of exposed surfaces to accomplish both of these functions. These durable, non-ablative surfaces maintain their surface profile through atmospheric reentry; thus, they preserve any surface imperfections that occur prior to atmospheric reentry. Furthermore, Orion's launch abort system includes a shroud that protects the thermal protection system while awaiting launch and during ascent. The combination of these design features and a careful pre-flight inspection to identify any manufacturing imperfections results in a high confidence that damage to the thermal protection system identified post-flight is due to the in-flight solid particle environments. These favorable design features of Orion along with the unique flight profile of the first exploration flight test of Orion (EFT-1) have yielded solid particle environment measurements that have never been obtained before this flight.

Miller, J. E.↗

2011 Ground Testing Highlights Article

Two tests supporting development of the launch abort system for the Orion MultiPurpose Crew Vehicle were run in the NASA Ames Unitary Plan wind tunnel last year. The first test used a fully metric model to examine the stability and controllability of the Launch Abort Vehicle during potential abort scenarios for Mach numbers ranging from 0.3 to 2.5. The aerodynamic effects of the Abort Motor and Attitude Control Motor plumes were simulated using high-pressure air flowing through independent paths. The aerodynamic effects of the proximity to the launch vehicle during the early moments of an abort were simulated with a remotely actuated Service Module that allowed the position relative to the Crew Module to be varied appropriately. The second test simulated the acoustic environment around the Launch Abort Vehicle caused by the plumes from the 400,000-pound thrust, solid-fueled Abort Motor. To obtain the proper acoustic characteristics of the hot rocket plumes for the flight vehicle, heated Helium was used. A custom Helium supply system was developed for the test consisting of 2 jumbo high-pressure Helium trailers, a twelve-tube accumulator, and a 13MW gas-fired heater borrowed from the Propulsion Simulation Laboratory at NASA Glenn Research Center. The test provided fluctuating surface pressure measurements at over 200 points on the vehicle surface that have now been used to define the ground-testing requirements for the Orion Launch Abort Vehicle.

Ross, James C.↗

Orion Guidance and Control Ascent Abort Algorithm Design and Performance Results

During the ascent flight phase of NASA s Constellation Program, the Ares launch vehicle propels the Orion crew vehicle to an agreed to insertion target. If a failure occurs at any point in time during ascent then a system must be in place to abort the mission and return the crew to a safe landing with a high probability of success. To achieve continuous abort coverage one of two sets of effectors is used. Either the Launch Abort System (LAS), consisting of the Attitude Control Motor (ACM) and the Abort Motor (AM), or the Service Module (SM), consisting of SM Orion Main Engine (OME), Auxiliary (Aux) Jets, and Reaction Control System (RCS) jets, is used. The LAS effectors are used for aborts from liftoff through the first 30 seconds of second stage flight. The SM effectors are used from that point through Main Engine Cutoff (MECO). There are two distinct sets of Guidance and Control (G&C) algorithms that are designed to maximize the performance of these abort effectors. This paper will outline the necessary inputs to the G&C subsystem, the preliminary design of the G&C algorithms, the ability of the algorithms to predict what abort modes are achievable, and the resulting success of the abort system. Abort success will be measured against the Preliminary Design Review (PDR) abort performance metrics and overall performance will be reported. Finally, potential improvements to the G&C design will be discussed.

Proud, Ryan W.↗

The International Orion Spacecraft Is off Towards the Stars

Following a very successful year of manufacturing, assembly and testing in factories located around the globe, NASA and ESA are preparing to deliver the major Exploration Mission-1 (EM-1) Orion flight elements, including the Crew Module, ESA Service Module and Launch Abort System. This international effort to design and develop a deep space exploration capable human spacecraft is rapidly transitioning from the design, development and test phase to the early test flight and production phase. Two major flight tests, an Ascent Abort test and EM-1, Orion's first flight onboard NASA's new heavy lift Space Launch System, are planned for the near future. Further, Orion will play a crucial role in the ambitious new Deep Space Gateway human exploration Program. This paper gives a short overview of the system and subsystem configuration of the Orion spacecraft, including NASA and ESA contributions, a status of EM-1, AA-2 and EM-2 spacecraft production, and a look at Orion's role in the construction and operation of the Deep Space Gateway. The paper will also address the innovative international cooperation methods being employed to conduct Orion and Service Module integration.

Kirasich, Mark↗

Integrated System Test Approaches for the NASA Ares I Crew Launch Vehicle

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.

Cockrell, Charles E., Jr.↗