Search NASA⌕ Search

SEARCH · Search NASA

Results for “orion”

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 55 records · Page 3

Orion Optical Navigation Progress Toward Exploration: Mission 1

Optical navigation of human spacecraft was proposed on Gemini and implemented successfully on Apollo as a means of autonomously operating the vehicle in the event of lost communication with controllers on Earth. It shares a history with the "method of lunar distances" that was used in the 18th century and gained some notoriety after its use by Captain James Cook during his 1768 Pacific voyage of the HMS Endeavor. The Orion emergency return system utilizing optical navigation has matured in design over the last several years, and is currently undergoing the final implementation and test phase in preparation for Exploration Mission 1 (EM-1) in 2019. The software development is being worked as a Government Furnished Equipment (GFE) project delivered as an application within the Core Flight Software of the Orion camera controller module. The mathematical formulation behind the initial ellipse fit in the image processing is detailed in Christian. The non-linear least squares refinement then follows the technique of Mortari as an estimation process of the planetary limb using the sigmoid function. The Orion optical navigation system uses a body fixed camera, a decision that was driven by mass and mechanism constraints. The general concept of operations involves a 2-hour pass once every 24 hours, with passes specifically placed before all maneuvers to supply accurate navigation information to guidance and targeting. The pass lengths are limited by thermal constraints on the vehicle since the OpNav attitude generally deviates from the thermally stable tail-to-sun attitude maintained during the rest of the orbit coast phase. Calibration is scheduled prior to every pass due to the unknown nature of thermal effects on the lens distortion and the mounting platform deformations between the camera and star trackers. The calibration technique is described in detail by Christian, et al. and simultaneously estimates the Brown-Conrady coefficients and the Star Tracker/Camera interlock angles. Accurate attitude information is provided by the star trackers during each pass. Figure 1 shows the various phases of lunar return navigation when the vehicle is in autonomous operation with lost ground communication. The midcourse maneuvers are placed to control the entry interface conditions to the desired corridor for safe landing. The general form of optical navigation on Orion is where still images of the Moon or Earth are processed to find the apparent angular diameter and centroid in the camera focal plane. This raw data is transformed into range and bearing angle measurements using planetary data and precise star tracker inertial attitude. The measurements are then sent to the main flight computer's Kalman filter to update the onboard state vector. The images are, of course, collected over an arc to converge the state and estimate velocity. The same basic technique was used by Apollo to satisfy loss-of-comm, but Apollo used manual crew sightings with a vehicle-integral sextant instead of autonomously processing optical imagery. The software development is past its Critical Design Review, and is progressing through test and certification for human rating. In support of this, a hardware-in-the-loop test rig was developed in the Johnson Space Center Electro-Optics Lab to exercise the OpNav system prior to integrated testing on the Orion vehicle. Figure 2 shows the rig, which the test team has dubbed OCILOT (Orion Camera In the Loop Optical Testbed). Analysis performed to date shows a delivery that satisfies an allowable entry corridor as shown in Figure 3.

Holt, Greg N.↗

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↗

Design Optimisation and Mass Saving of the Structure of the Orion-MPCV European Service Module

This paper presents an overview of the design optimisation measures that have been proposed and analysed in order to reduce the mass of the structure, including the MMOD (Micro-Meteoroid and Orbital Debris) protection system, of the ESM (European Service Module) for the “Orion” MPCV (Multi-Purpose Crew Vehicle). Under an agreement between NASA and ESA, the NASA Orion MPCV for human space exploration missions will be powered by a European Service Module, based on the design and experience of the ATV (Automated Transfer Vehicle). The development and qualification of the European Service Module is managed and implemented by ESA. The ESM prime contractor and system design responsible is Airbus Defence and Space. Thales Alenia Space Italia is responsible for the design and integration of the ESM Structure and MMOD protection system in addition to the Thermal Control System and the Consumable Storage System. The Orion Multi-Purpose Crew Vehicle is a pressurized, crewed spacecraft that transports up to four crew members from the Earth’s surface to a nearby destination or staging point. Orion then brings the crew members safely back to the Earth’s surface at the end of the mission. Orion provides all services necessary to support the crew members while on-board for short duration missions (up to 21 days) or until they are transferred to another orbiting habitat. The ESM supports the crew module from launch through separation prior to re-entry by providing: in-space propulsion capability for orbital transfer, attitude control, and high altitude ascent aborts; water and oxygen/nitrogen needed for a habitable environment; and electrical power generation. In addition, it maintains the temperature of the vehicle's systems and components and offers space for unpressurized cargo and scientific payloads. The ESM has been designed for the first 2 Lunar orbit missions, EM-1 (Exploration mission 1) is an un-crewed flight planned around mid-2020, and EM-2, the first crewed flight, is planned in 2022. At the time where the first ESM is about to be weighted, the predicted mass lies slightly above the initial requirement. For future builds, mass reduction of the Service Module has been considered necessary. This is being investigated, together with other design improvements, in order to consolidate the ESM design and increase possible future missions beyond the first two Orion MPCV missions. The mass saving study has introduced new optimised structural concepts, optimisation of the MMOD protection shields, and optimised redesign of parts for manufacturing through AM (Additive Manufacturing).

Micro-Meteroids and Orbital Debris Protection Syst↗

Agile Approach to Assuring the Safety-Critical Embedded Software for NASA's Orion Spacecraft

Human-rated missions like NASA's Exploration Mission - 1 (EM-1) and the Orion Multi-Purpose Crew Vehicle are becoming exceedingly complex in terms of software's contribution to achieving mission objectives. The increasing complexity and inherent safety critical nature of the embedded flight software imposes a unique resource challenge to assurance providers responsible for affirming that the mission is going to fly safely. Another challenge NASA and other Government agencies are facing is that more and more software is being developed using an agile development methodology, which is divergent from the typical waterfall, iterative, and incremental development methodologies assurance providers generally observe in the development of safety-critical embedded software. Orion Independent Verification and Validation (IV&V) has addressed these challenges by providing focused assurance results of critical mission capabilities prioritized by a dynamic assessment of risk level. Prior to this approach, Orion IV&V evaluated areas of risk in much broader, and more static, terms. Due to the agile software development life cycle that Orion follows, IV&V findings were often reported months out of phase with the developer thereby imposing increased rework costs. As a result of evolving the approach to adding assurance on Orion, IV&V is able to incrementally deliver high-priority assurance conclusions and more impactful issues more in phase with the developer activities, thereby increasing the value of the findings to the project. The agile IV&V approach employed by the Orion IV&V team strives to achieve a cadence of delivery that matches the pace of development. This agile approach provides increased flexibility for the assurance provider to become more efficient in reporting assurance conclusions and issues. This paper and presentation will discuss the principles which drive the design of our approach, results to date, and stimulate thinking for groups looking to add assurance to software being developed using an agile methodology.

Justin Smith↗

Development of the Orion Life-Support Integration Facility (OLIF)

Testing the life support hardware of a vehicle that is going to take humans beyond low-Earth orbit (LEO) in conditions similar to space is crucial. The Orion Life-Support Integration Facility (OLIF) at NASA Johnson Space Center (JSC) was designed and built to test the Orion vehicle’s hardware and software as integrated systems to provide a complete Environmental Control and Life Support System (ECLSS) system-level qualification. The existing 11 Foot human rated vacuum chamber has been adapted to accommodate and integrate various qualification and flight like components of the Orion vehicle’s Air Revitalization System (ARS), Pressure Control System (PCS), Active Thermal Control System (ATCS) and the Orion Crew Survival System Suits (OCSS). The ultimate goal was to create an analog testbed that could safely support up to four test subjects in open “shirt-sleeve” or closed suit loop configurations and simulate Orion Cabin conditions. This integrated hardware/software ARS and PCS will help identify any technical issues that should be addressed prior to the Artemis-2 mission. This paper will discuss the history of Orion ECLSS hardware development testing in the 11 Foot Chamber, the challenge of integrating flight hardware and software control systems, and the capabilities that make it a unique, world class facility for NASA. It will provide an overview of past and future testing, and the lessons learned along the way.

Peter A Masi↗

Eleven Countries, an Integrated Spacecraft: the Story of International Collaboration that Built the Orion Spacecraft and Powered the Success of the Artemis I Mission

The quest to return humans to the Moon in the next step towards humanity's exploration of space is more alive than ever. After a great deal of achievements, failures, and lessons learned, the Artemis I mission set o to the Moon on November 16, 2022, with the goal of testing a new rocket, the Space Launch System, and a new spacecraft, Orion: designed, assembled, and tested across two continents, and 11 countries. Behind this mission, decades of experience with the International Space Station, Autonomous Transfer Vehicle operations, and many other program collaborations built the know-how on how to succeed together in the toughest environment | deep space. The Artemis I mission proved to be an incredible success, meeting 161 total mission objectives, including 21 developed during the flight based on outperforming spacecraft. It was also a case-study in international collaboration, given that ESA, NASA, and industry partners Airbus and Lockheed Martin for the first time had to design, build, test, and fly a fully integrated human-rated spacecraft, with most critical functions dependent and interconnected across U.S. and European systems. The U.S.-built Orion Crew Module and Crew Module Adapter and European-built European Service Module (ESM) shared critical interfaces and commodities, from propulsion, avionics, active/passive thermal, electrical power generation, storage and distribution to the software that managed it all. In this paper, we will describe relevant aspects of the integrated spacecraft design, providing context for the challenges that the team faced in all phases required to get Orion ready to fly, and provide a direct account of how the joint team formed, trained, and supported the operations of the successful Artemis I mission. We will also explore the evolution of the partnerships, given that these allow a multi-national e ort to sustain the program production, share costs, leverage a broader base of engineering expertise, and build more diverse capabilities over the long haul to support the Artemis goals and objectives. Lastly, we will cover critical lessons learned and how the Orion Program has implemented these in preparation of the next Artemis missions to repeat the success of Artemis I. The purpose of this paper is to document knowledge we gained and lessons we learned through the development of an integrated Orion spacecraft, since it is imperative we build on this now, at the dawn of the Artemis Program, an international endeavor to push human space exploration.

Deep Space Exploration↗

Symposium on the Orion Nebula to Honor Henry Draper, New York University, New York, NY, December 4, 5, 1981, Proceedings

The present conference on astronomical studies of the Orion Nebula covers molecular clouds in Orion, the use of the nebula's cloak as a model for gas super-shells around OB associations, optical and UV data concerning the nebula's physical conditions, the presence of atomic carbon in Orion, large scale distribution of far-IR and sub-mm line emission, star formation studies in the IR, gas dynamics in the circumstellar nebula of the Becklin-Neugebauer source, maser sources and far-IR CO line emission in Orion-KL, and synthesis maps of mm molecular lines. Also discussed are Orion's star distributions, core region nebular condensations, energetic molecular flows in star-forming cloud cores, IR observations of HH objects, compact continuum radio sources, the SiO maser, shock waves, and the chemical evolution of OB associations.

Glassgold, A. E.↗

The Einstein survey of the young stars in the Orion Nebula

The Orion Nebula is the best studied site of recent star formation in the Galaxy. The complete Einstein Observatory survey of the Orion Nebula covering a 2 deg x 2 deg region centered on the Trapezium is reported. An X-ray mosaic is presented for the Nebula along with a complete X-ray catalogue for this very young cluster. Approximately 150 distinct sources were found in this 4 sq deg region; spectral types and colors were obtained for about 1/2 of the optical counterparts of these sources. Comparison of the variability of the Orion X-ray sources with those found in the Rho Ophiuchi cloud leads to the conclusion that the Orion sources' variability is also likely to result from continual flaring activities. Eleven new late B stars associated with X-ray emission far exceeding that expected from early type stars were discovered. The X-rays may originate from pre-main sequence companions to these stars; a T-Tauri star of the same age would have the correct L sub x. Comparison of the solar type stars in Orion with those in the Pleiades, the Hyades, and the field suggests that the decay of activity with age is most appropriately described by an exponential, rather than a power law fit.

Zoonematkermani, S.↗

158 micron forbidden C II mapping of the Orion molecular cloud

A fully sampled, 1000-point, 1-arcmin-resolution map of the inner 6.5 x 10 arcmin (alpha x delta) regions of the Orion Nebula in the 157.7409-micron forbidden fine-structure line is constructed. Large-scale strip maps in forbidden C II across the face of the Orion molecular cloud, and CO(17-16), (14-13), and (7-6) spectra are obtained at selected positions in the Orion H II region/molecular cloud interface. Strong forbidden C II line emission is observed across the face of the Orion molecular. The total forbidden C II luminosity from the Orion molecular cloud is about 1500 solar luminosities, or 0.3 percent of the FIR luminosity. The extended forbidden C II emission probably arises in either the UV-exposed surface of the molecular cloud or from the surfaces of UV-exposed clumps within the molecular cloud.

Stacey, G. J.↗

The Star Formation History of Orion and its Environs

During this period of performance, we have obtained the following observations and carried out the analysis of the Orion associations itemized below. 1. Quest Optical Photometry: The photometric survey carries out with the Quest camera is finished. The strips at declinations +1 degree and -1 degree have already been processed. Photometry for a total of around 400,000 stars was obtained in these two strips with the Quest camera pipeline. Around 24,000 variables were picked out of this total by our variability software. Of these, around 2,500 stars fall above the main sequence and so were picked as candidates for spectroscopic follow-up. 2. Slit spectroscopy of bright candidates: Spectra for some 800 candidate PMS stars were obtained with the FAST spectrograph at the SAO 1.5m telescope in Mt. Hopkins. The spectra are being analyzed; 300 stars have been confirmed as young. 3. Multifiber spectroscopy: The first test of the multifiber spectrograph Hectoechelle were carried out in December 2003. One field of the Orion Nebula Cluster was observed with Hectochelle at three wavelength settings. A total of 157 spectra were obtained. Of these, 63 stars have been confirmed as Classical T Tauri stars, and 36 additional stars need further follow up. A paper is in preparation. 4. UBVRI photometry: We were granted time with the 4-shooter CCD Mosaic Camera at the SAO 1.2m telescope, to obtain UBVRI photometry of a subset of 53 newly identified T Tauri stars in the strips centered at DEC=-1 and +l. This sample is composed of strong Halpha emitting PMS stars (Classical T Tauri stars) located mostly in the Orion OB l b association, around the Orion Belt area. We have estimated mass accretion rates for 22 for these stars using the U photometry and the calibration of Gullbring et al. (1998), and found it to be similar to that of young stars in associations of similar age. 5. Near and mid-IR photometry: During the winter of 2003, we used the IR Camera on the SAO 1.2m telescope, to obtain L- band photometry of a set of the newly identified Orion OB l a and l b stars, in order to look for IR excess emission coming from the hotter inner parts of circumstellar disks. These data is being combined with the GEMINI/OSCIR 10 micron photometry obtained during 2002 and the mass accretion rates to determine the properties of disks in Ori lb. A paper is presently on preparation.

Calvet, Nuria↗

First Human Testing of the Orion Atmosphere Revitalization Technology

An amine-based carbon dioxide (CO2) and water vapor sorbent in pressure-swing regenerable beds has been developed by Hamilton Sundstrand and baselined for the Orion Atmosphere Revitalization System (ARS). In two previous years at this conference, reports were presented on extensive Johnson Space Center (JSC) testing of the technology in a representative environment with simulated human metabolic loads. The next step in developmental testing at JSC was to replace the simulated humans with real humans; this testing was conducted in the spring of 2008. This first instance of human testing of a new Orion ARS technology included several cases in a sealed Orione-quivalent free volume and three cases using emergency breathing masks connected directly to the ARS loop. Significant test results presented in this paper include comparisons between the standard metabolic rates for CO2 and water vapor production published in Orion requirements documents and real-world rate ranges observed with human test subjects. Also included are qualitative assessments of process flow rate and closed-loop pressure-cycling tolerability while using the emergency masks. Recommendations for modifications to the Orion ARS design and operation, based on the test results, conclude the paper.

Lin, Amy↗

First Human Testing of the Orion Atmosphere Revitalization Technology

An amine-based carbon dioxide (CO2) and water vapor sorbent in pressure-swing regenerable beds has been developed by Hamilton Sundstrand and baselined for the Orion Atmosphere Revitalization System (ARS). In two previous years at this conference, reports were presented on extensive Johnson Space Center (JSC) testing of the technology in a representative environment with simulated human metabolic loads. The next step in developmental testing at JSC was to replace the simulated humans with real humans; this testing was conducted in the spring of 2008. This first instance of human testing of a new Orion ARS technology included several cases in a sealed Orion-equivalent free volume and three cases using emergency breathing masks connected directly to the ARS loop. Significant test results presented in this paper include comparisons between the standard metabolic rates for CO2 and water vapor production published in Orion requirements documents and real-world rate ranges observed with human test subjects. Also included are qualitative assessments of process flow rate and closed-loop pressure-cycling tolerability while using the emergency masks. Recommendations for modifications to the Orion ARS design and operation, based on the test results, conclude the paper.

Lin, Amy↗

Assessment of Prone Positioning of Restrained, Seated Crewmembers in a Post Landing Stable 2 Orion Configuration

During the Orion landing and recovery subsystem design review, June 2009, it was noted that the human system and various vehicle systems, the environmental control and life support (ECLSS) and guidance, navigation and control (GN&C) systems for example, are negatively affected by Orion assuming a stable 2 (upside down; Figure A) configuration post landing. The stable 2 configuration is predicted to occur about 50% of the time based on Apollo landing data and modeling of the current capsule. The stable 2 configuration will be countered by an active up-righting system (crew module up-righting system; CMUS). Post landing balloons will deploy and inflate causing the vehicle to assume or maintain the stable 1 (up-right; Figure B) configuration. During the design review it was proposed that the up-righting system could be capable of righting the vehicle within 60 seconds. However, this time limit posed a series of constraints on the design which made it less robust than desired. The landing and recovery subsystem team requested an analysis of Orion vehicle systems as well as the human system with regard to the effect of stable 2 in order to determine if an up-righting response time greater than 60 seconds could be tolerated. The following report focuses on the assessment of the human system in the posture assumed when Orion is in the stable 2 configuration. Stable 2 will place suited, seated, and restrained crewmembers in a prone (facedown), head-up position for a period of time dependent on the functionality of the up-righting systems, ability of the crew to release themselves from the seat and restraints, and/or time to arrival of rescue forces. Given that the Orion seat and restraint system design is not complete and therefore, not available for evaluation, Space Medicine assessed how long a healthy but deconditioned crewmember could stay in this prone, restrained position and the physiological consequences of this posture by researching terrestrial analogs and considered the known physiological alterations and deconditioning experienced by long duration crewmembers.

Barr, Yael↗

Orion Entry Performance-Based Center-of-Gravity Box

The Orion capsule is designed both for Low Earth Orbit missions to the ISS and for missions to the moon. For ISS class missions, the capsule will use an Apollo-style direct entry. For lunar return missions, depending on the timing of the mission, the capsule could perform a direct entry or a skip entry of up to 4800 n.mi. in order to land in the coastal waters of California. The physics of atmospheric re-entry determine the capability of the Orion vehicle. For a given vehicle mass and shape, physics tells us that the driving parameters for an entry vehicle are the hypersonic lift-to-drag ratio (L/D) and the flight path angle at entry interface (gamma(sub EI)). The design of the Orion atmospheric re-entry must meet constraints during both nominal and dispersed flight conditions on landing accuracy, heating rate, total heat load, sensed acceleration, and proper disposal of the Service Module. These constraints define an entry corridor in the space of L/D-gamma(sub EI); if the vehicle falls within this corridor, then all constraints are met. The gamma(sub EI) dimension of the corridor can be further constrained by the gloads experienced during emergency entries. Thus, the entry performance for the Orion vehicle can be described completely by the L/D. Bounds on the hypersonic L/D necessary to achieve all the mission requirements can be defined for the given entry corridor. Landing accuracy performance drives the lower limit on L/D. In order to achieve the desired landing accuracy, a minimum L/D must be ensured. The design of the Thermal Protection System (TPS) drives the upper limit on L/D. A higher L/D can drive mass into the design of the TPS. Conversely, once the TPS is designed, the L/D must be ensured to stay below a certain limit in order for the TPS to stay within its design envelop. The L/D must stay within its upper and lower bounds during dispersed flight conditions. L/D is a function of both the aerodynamics and the center-of-gravity (CG) of the vehicle. The aerodynamics of the vehicle are determined by Computational Fluid Mechanics (CFD) and wind tunnel tests. However, the aerodynamics are not known precisely. Instead, an aerodynamic database has been developed where the aerodynamic coefficients are known to fall within a probabilistic band defined by upper and lower bounds. It is expected that the probabilistic band will shrink after the first missions are flown and real-world data is collected. Until that time, the Orion must be designed to the current aerodynamic database. Thus, for a given aerodynamic database with given uncertainties, the allowable range in L/D can be mapped to an allowable box for the CG location. The CG box is used to set requirements on the dispersions allowed for vehicle packaging and cargo storage. As the aerodynamic uncertainties decrease, the size of the CG box can increase. This paper discusses the technique used to map the minimum and maximum L/D bounds set by the entry performance requirements to the allowable dispersions in CG while accounting for aerodynamic uncertainties. The L/D is defined as the ratio of the lift force to the drag force. It is equivalent to the ratio of lift coefficient (C(sub L)) over drag coefficient (C(sub D)). C(sub L) and C(sub D) are functions of Mach number (M) and angle of attack (alpha). A Mach number of 25 is used as a measuring point of the hypersonic L/D. Variations in C(sub L), C(sub D) and alpha cause variations in L/D. Equation (1) shows the three contributions to the variation in L/D.

Rea, Jeremy R.↗

ENRE 655 Class Project. Development of the Initial Main Parachute Failure Probability for the Constellation Program (CxP) Orion Crew Exploration Vehicle (CEV) Parachute Assembly System (CPAS)

Loss of Crew (LOC) and Loss of Mission (LOM) are two key requirements the Constellation Program (CxP) measure against. To date, one of the top risk drivers for both LOC and LOM has been Orion's Crew Exploration Vehicle (CEV) Parachute Assembly System (CPAS). Even though the Orion CPAS is one of the top risk drivers of CxP, it has been very difficult to obtain any relevant data to accurately quantify the risk. At first glance, it would seem that a parachute system would be very reliable given the track record of Apollo and Soyuz. Given the success of those two programs, the amount of data is considered to be statistically insignificant. However, due to CxP having LOC/LOM as key design requirements, it was necessary for Orion to generate a valid prior to begin the Risk Informed Design process. To do so, the Safety & Mission Assurance (S&MA) Space Shuttle & Exploration Analysis Section generated an initial failure probability for Orion to use in preparation for the Orion Systems Requirements Review (SRR).

Fuqua, Bryan C.↗

Orion FSW V and V and Kedalion Engineering Lab Insight

NASA, along with its prime Orion contractor and its subcontractor s are adapting an avionics system paradigm borrowed from the manned commercial aircraft industry for use in manned space flight systems. Integrated Modular Avionics (IMA) techniques have been proven as a robust avionics solution for manned commercial aircraft (B737/777/787, MD 10/90). This presentation will outline current approaches to adapt IMA, along with its heritage FSW V&V paradigms, into NASA's manned space flight program for Orion. NASA's Kedalion engineering analysis lab is on the forefront of validating many of these contemporary IMA based techniques. Kedalion has already validated many of the proposed Orion FSW V&V paradigms using Orion's precursory Flight Test Article (FTA) Pad Abort 1 (PA-1) program. The Kedalion lab will evolve its architectures, tools, and techniques in parallel with the evolving Orion program.

Mangieri, Mark L.↗

Orion Relative Navigation Flight Software Analysis and Design

The Orion relative Navigation System has sought to take advantage of the latest developments in sensor and algorithm technology while living under the constraints of mass, power, volume, and throughput. In particular, the only sensor specifically designed for relative navigation is the Vision Navigation System (VNS), a lidar-based sensor. But it uses the Star Trackers, GPS (when available) and IMUs, which are part of the overall Orion navigation sensor suite, to produce a relative state accurate enough to dock with the ISS. The Orion Relative Navigation System has significantly matured as the program has evolved from the design phase to the flight software implementation phase. With the development of the VNS system and the STORRM flight test of the Orion Relative Navigation hardware, much of the performance of the system will be characterized before the first flight. However challenges abound, not the least of which is the elimination of the RF range and range-rate system, along with the development of the FSW in the Matlab/Simulink/Stateflow environment. This paper will address the features and the rationale for the Orion Relative Navigation design as well as the performance of the FSW in a 6-DOF environment as well as the initial results of the hardware performance from the STORRM flight.

D'Souza, Chris↗

The Orion Pad Abort 1 Flight Test A Highly Successful Test

The Orion Pad Abort 1 (PA-1) flight test was designed as an early demonstration of the Launch Abort System (LAS) for the Orion capsule. The LAS was designed developed and manufactured by the Lockheed Martin/Orbital Sciences team. At inception it was realized that recovery of the Orion Capsule simulator would be useful from an engineering analysis and data recovery point of view. Additionally this test represented a flight opportunity for the Orion parachute system, which in a real abort would provide final landing deceleration. The Orion parachute program is named CPAS (CEV Parachute Assembly System). Thus CPAS became a part of the PA-1 flight, as a secondary test objective. At program kick off, the CPAS system was in the design state described below. Airbag land landing of the spacecraft was the program baseline. This affected the rigging of the parachutes. The system entry deployment conditions and vehicle mass have both evolved since that original design. It was decided to use the baseline CPAS Generation 1 (Gen 1) parachute system for the recovery of the PA-1 flight. As CPAS was a secondary test objective, the system would be delivered in its developmental state. As the PA-1 program evolved, the parachute recovery system (CPAS) moved from a secondary objective to a more important portion of the program. Tests were added, weights and deployment conditions changed and some hardware portions of the CPAS configuration were not up to the new challenges. Additional tests were added to provide confidence in the developmental system. This paper will review a few of these aspects with the goal of showing some preliminary and qualitative results from what we believe was a highly successful test.

Sinclair, Robert↗