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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

Integrated Network Architecture for NASA's Orion Missions

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. The series of missions will begin with a new crew exploration vehicle (called Orion) that will initially provide crew exchange and cargo supply support to the International Space Station (ISS) and then become a human conveyance for travel to the Moon. The Orion vehicle will be mounted atop the Ares I launch vehicle for a series of pre-launch tests and then launched and inserted into low Earth orbit (LEO) for crew exchange missions to the ISS. The Orion and Ares I comprise the initial vehicles in the Constellation system of systems that later includes Ares V, Earth departure stage, lunar lander, and other lunar surface systems for the lunar exploration missions. These key systems will enable the lunar surface exploration missions to be initiated in 2018. The complexity of the Constellation system of systems and missions will require a communication and navigation infrastructure to provide low and high rate forward and return communication services, tracking services, and ground network services. The infrastructure must provide robust, reliable, safe, sustainable, and autonomous operations at minimum cost while maximizing the exploration capabilities and science return. The infrastructure will be based on a network of networks architecture that will integrate NASA legacy communication, modified elements, and navigation systems. New networks will be added to extend communication, navigation, and timing services for the Moon missions. Internet protocol (IP) and network management systems within the networks will enable interoperability throughout the Constellation system of systems. An integrated network architecture has developed based on the emerging Constellation requirements for Orion missions. The architecture, as presented in this paper, addresses the early Orion missions to the ISS with communication, navigation, and network services over five phases of a mission: pre-launch, launch from T0 to T+6.5 min, launch from T+6.5 min to 12 min, in LEO for rendezvous and docking with ISS, and return to Earth. The network of networks that supports the mission during each of these phases and the concepts of operations during those phases are developed as a high level operational concepts graphic called OV-1, an architecture diagram type described in the Department of Defense Architecture Framework (DoDAF). Additional operational views on organizational relationships (OV-4), operational activities (OV-5), and operational node connectivity (OV-2) are also discussed. The system interfaces view (SV-1) that provides the communication and navigation services to Orion is also included and described. The challenges of architecting integrated network architecture for the NASA Orion missions are highlighted.

Bhasin, Kul B.↗
NASA NTRSDate not supplied

Artemis I Orion ESM Propulsion System Engine Performance

NASA's Orion spacecraft transports humans and cargo into cislunar space for the Artemis program. The European Service Module (ESM), supplied by ESA and its European industry partners, provides Orion with power and in-space propulsion. The Orion-ESM propulsion system is a bipropellant hypergolic propulsion system using monomethyl hydrazine (MMH) and nitrogen tetroxide (MON-3). Primary translational propulsion is provided by the Orbital Maneuvering System Engine(OMS-E), with backup translational propulsion provided by eight Auxiliary thrusters (AUX). Attitude control and small translational maneuvers are provided by twenty four Reaction Control System (RCS) engines. The 2022 Artemis I mission was the first integrated flight test of the Orion-ESM spacecraft and its propulsion system. The OMS-E used on Artemis I was a refurbished Space Shuttle OMS-E that previously flew on nineteen missions ranging f rom STS-41G in 1984 to STS-112 in 2002. The Auxiliary engines are modified Aerojet Rocketdyne R4D-11 engines produced specifically for the Orion program. The RCS engines are Ariane Group engines originally used for the Automated Transfer Vehicle (ATV) program. This paper will discuss the unique operational requirements for each engine on Orion and the development and qualification effort sat both the engine and system-level that were completed to enable a successful Artemis I mission. Next the paper will evaluate the in-f light performance of the engines during the Artemis I mission showing nominal performance as expected. Additionally, comparisons to models will be presented showing very good correlation. Finally, the paper will address the plan for the engines on future Orion missions and the evolution of the system operation.

liquid propulsion systems↗
NASA NTRSDate not supplied

Artemis I Orion ESM Propulsion System Engine Performance

NASA's Orion spacecraft transports humans and cargo into cislunar space for the Artemis program. The European Service Module (ESM), supplied by ESA and its European industry partners, provides Orion with power and in-space propulsion. The Orion-ESM propulsion system is a bipropellant hypergolic propulsion system using monomethyl hydrazine (MMH) and nitrogen tetroxide (MON-3). Primary translational propulsion is provided by the Orbital Maneuvering System Engine (OMS-E), with backup translational propulsion provided by eight Auxiliary thrusters (AUX). Attitude control and small translational maneuvers are provided by twenty-four Reaction Control System (RCS) engines. The 2022 Artemis I mission was the first integrated flight test of the Orion-ESM spacecraft and its propulsion system. The OMS-E used on Artemis I was a refurbished Space Shuttle OMS-E that previously flew on nineteen missions ranging from STS-41G in 1984 to STS-112 in 2002. The Auxiliary engines are modified Aerojet Rocketdyne R4D-11 engines produced specifically for the Orion program. The RCS engines are Ariane Group engines originally used for the Automated Transfer Vehicle (ATV) program. This paper will discuss the unique operational requirements for each engine on Orion and the development and qualification effort sat both the engine and system-level that were completed to enable a successful Artemis I mission. Next the paper will evaluate the in-f light performance of the engines during the Artemis I mission showing nominal performance as expected. Additionally, comparisons to models will be presented showing very good correlation. Finally, the paper will address the plan for the engines on future Orion missions and the evolution of the system operation.

liquid propulsion systems↗
NASA NTRS2018

Agile Approach to Adding Assurance and Mitigating Overall Mission Risk for Orion Software on EM-1

Human-rated missions like Orion are becoming exceedingly complex in terms of software contribution to achieving mission objectives, and this creates a resource challenge for everyone whose job is to add assurance that the mission is going to fly safely. Orion IV&V has addressed this challenge by providing focused assurance results of critical mission capabilities prioritized by a dynamic assessment of risk level. Prior to this approach, Orion IV&V was evaluating areas of risk in much broader, and more static, terms. Due to the Agile software development cycle that Orion follows, IV&V findings were often reported months out of phase with the developer. As a result of evolving the approach to providing assurance on Orion, IV&V is able to incrementally deliver high-priority assurance data 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 presentation will discuss the principles which drive the design of our approach, results to date, and aspirations for long-term performance.

Assurance↗
NASA NTRS1992

158 micrometers (CII) mapping of the Orion molecular cloud

Data from the inner regions of the Orion nebula in the 157.7409 micrometers (CII) fine structure line is investigated. Large scale strip maps in (CII) across the face of the Orion molecular cloud, and CO spectra at selected positions in the Orion HII region/molecular cloud interface were obtained. The total (CII) luminosity from the Orion molecular cloud is estimated to be approximately 1500 of the solar luminosity or 0.3 of the far infrared luminosity. The overall properties of the Orion molecular cloud deduced are: the photodissociated gas to molecular gas mass fraction, the (CII) line to far infrared continuum intensity ratio and the (CII)/CO(12) (1 to 0) line intensity ratio are the same for the Orion molecular cloud and the nuclei of non-starburst galaxies. The observations provide an important link between (CII) emission from galactic molecular clouds and the nuclei of external galaxies.

Stacey, G. J.↗
NASA NTRS1995

PAHs as Probes of Photodissociation Regions in M17 and the Orion Bar

We have obtained narrow-band images of M17 SW and the Orion Bar in the PAH emission bands and pedestal (3.29, 3. 36, 3. 42 microns) The emission bands at 3.3 and 3.4 microns arise from the photodissociation regions (PDRs) between ionized gas and molecular clouds. In both M17 SW and the Orion Bar, the PDRs are nearly edge-on, providing excellent opportunities for comparing models of PDRs with observations. We observe an exponential drop in the strength of the 3.3 micron emission with a 1/e distance of 9 arcsec in Orion and 5 arcsec in M17 SW, in good agreement with previous observations. These results show that the two regions are very similar, and they imply that the mean density is 2.4 times higher in the Orion Bar than in the M17 SW PDR. However, we also find that in the Orion Bar, the ratio of the 3.4 micron emission to the 3.3 micron emission is consistent with the 1/e distance of 3 arcsec determined from PDR models fit to the molecular H and CO in the Orion Bar. We are presently investigating how the main band can imply that the UV field is dropping with a 1/e distance of 9 arcsec while the model PDR predicts a 1/e distance of 3 arcsec.

Sloan, G. C.↗
NASA NTRS2003

The Star Formation History of Orion and its Environs

During the period of performance, we have obtained the following observations and carried out the analysis of the Orion associations itemized below. Optical Photometry: The Quest camera that had been damaged by lightning on Sept. 2001 was reconfigured to use 10 chips and only 3 filters instead of the original 4 but retaining its spatial coverage of 2.3deg wide in declination. During the Winter and Fall 2002 observing campaigns, we obtained multifilter photometry using the Quest camera on the 1mt Schmidt of the Venezuelan National Observatory, to continue the survey of the Orion clouds. In the Winter 2002 season, we obtained photometry for 10 scans at DEC=+5, 7 scans at DEC=-5. Several additional scans at DEC=-3 were obtained during the Fall 2002 observing campaign. Slit spectroscopy of bright candidates: During 2002 spectra for some 235 candidate PMS stars were obtained with the FAST spectrograph at the SAO 1.5m telescope in Mt. Hopkins. These objects, all brighter than V=16, are located in two strips centered at DEC=+l and -5, and spanning from RA=5h-6h. The spectra are being analyzed. Multifiber spectroscopy: Spectroscopy for our fainter (V less than or equal to 16) candidates has not kept pace with our spectroscopy of brighter candidates, because of the delay in the commissioning of the Hectospec and Hectoechelle multi-object spectrographs at the new 6.5m MMT. We obtained some data with the Hydra spectrograph on the WIYN telescope: Feb 1-4, 2002. Time granted to the project: "A Large Scale Survey of the Low-Mass Young Population in the Orion OB1 Association" (P.I.: C. Briceno). Three half-nights (we used the first half of the night, the second half of the night was used with the Mini-Mosaic imager by another team). Only the first half night was clear. We observed 3 fields centered in a 2.3 deg wide strip centered at DEC=-1 and spanning RA=Sh to 6h. A total of 250 spectra were obtained for the same number of candidate PMS stars. Nov. 13-15, 2002. Time granted to the project "Cluster survey of protoplanetary disk evolution", (P.I.: A. Sicilia-Aguilar). Clear weather throughout. We obtained spectra for some 200 candidate PMS stars in 3 fields located in a 2.3 deg wide strip centered at DEC=+l and spanning from RA=5h20m to 5h35m. Data for both observing runs is partially reduced and is being analyzed. U photometry: During Nov.29-Dec.4, 2002 we were granted time with the 4-shooter CCD Mosaic Camera at the SAO 1.2m telescope, to obtain U-band photometry of a subset of the newly identified T Tauri stars in the strip centered at DEC=-1. This sample is composed of strong H(alpha) emitting PMS stars (Classical T Tauri stars) located mostly in the Orion OB lb association, around the Orion Belt area. Our data will be combined with our calibration of the U-band excess (Gullbring et al. 1998) to derive mass accretion rates. Because of bad weather we observed only 20 stars during 1.5 clear nights. Near IR photometry: During Dec. 14-19, 2002 we used the IR Camera on the SAO 1.2m telescope, to obtain L-band photometry of a set of 17 the newly identified Orion OB 1a and 1b stars, in order to look for IR excess emission coming from the hotter inner parts of circumstellar disks. Again, mediocre weather prevented a larger set to be observed. These stars were also observed with the OSCIR mid-IR camera on Gemini North during later 2001. Our goal is to construct SEDs from the visual out to the mid-IR (by combining our optical/IR data with 2MASS JHK magnitudes) in order to explore disk dissipation at the critical ages of 5-10 Myr spanned by these stars.

Calvet, Nuria↗
NASA NTRS2003

Baby Stars in Orion Solve Solar System Mystery

What do X-rays, meteoroids, infant stars in the Orion Nebula, and our solar system have in common? Perhaps much more than anyone thought. Eric Feigelson of Penn State University stumbled onto a connection one day while his thoughts were far from the solar system, turned toward the vibrant neighborhood of young stars, hot gas, and caliginous dust of the Orion Nebula. This nebula, 1500 light-years away, is visible to the naked eye in the constellation Orion, a gem to behold with a good pair of binoculars or a telescope under dark skies. In Orion, Feigelson inadvertently found a possible solution to a long-standing mystery about our own solar system: the presence of exotic isotopes locked away in meteoroids. Scientists have assumed that these short-lived isotopes - special forms of atomic nuclei, such as aluminum-26 and calcium-41 - were transported here by a nearby supernova. Only tenuous evidence for such an explosion exists, but what else could have made the isotopes? The isotopes are about as old as the solar system, and the Sun couldn t possibly have been powerful enough to create them. Well, maybe we need to give the Sun a little more credit. Feigelson found that very young, midsized stars in the Orion Nebula - in the same stellar class as our Sun except they are only a million years old - produce powerful flares visible in X-rays. His team spotted these X-ray flares with the Chandra X-Ray Observatory. These baby-tantrum flares are indeed energetic enough to forge heavy isotopes, Feigelson says. If the infant stars in Orion can do it now, then our Sun could have done the same when the solar system was forming about 4.5 billion years ago, when the Sun itself was only a few million years old.

Wanjek, Christopher↗
NASA NTRS2009

Avionics System Architecture for the NASA Orion Vehicle

It has been 30 years since the National Aeronautics and Space Administration (NASA) last developed a crewed spacecraft capable of launch, on-orbit operations, and landing. During that time, aerospace avionics technologies have greatly advanced in capability, and these technologies have enabled integrated avionics architectures for aerospace applications. The inception of NASA s Orion Crew Exploration Vehicle (CEV) spacecraft offers the opportunity to leverage the latest integrated avionics technologies into crewed space vehicle architecture. The outstanding question is to what extent to implement these advances in avionics while still meeting the unique crewed spaceflight requirements for safety, reliability and maintainability. Historically, aircraft and spacecraft have very similar avionics requirements. Both aircraft and spacecraft must have high reliability. They also must have as much computing power as possible and provide low latency between user control and effecter response while minimizing weight, volume, and power. However, there are several key differences between aircraft and spacecraft avionics. Typically, the overall spacecraft operational time is much shorter than aircraft operation time, but the typical mission time (and hence, the time between preventive maintenance) is longer for a spacecraft than an aircraft. Also, the radiation environment is typically more severe for spacecraft than aircraft. A "loss of mission" scenario (i.e. - the mission is not a success, but there are no casualties) arguably has a greater impact on a multi-million dollar spaceflight mission than a typical commercial flight. Such differences need to be weighted when determining if an aircraft-like integrated modular avionics (IMA) system is suitable for a crewed spacecraft. This paper will explore the preliminary design process of the Orion vehicle avionics system by first identifying the Orion driving requirements and the difference between Orion requirements and those of other previous crewed spacecraft avionics systems. Common systems engineering methods will be used to evaluate the value propositions, or the factors that weight most heavily in design consideration, of Orion and other aerospace systems. Then, the current Orion avionics architecture will be presented and evaluated.

Baggerman, Clint↗
NASA NTRS2010

A Comparison Between Orion Automated and Space Shuttle Rendezvous Techniques

The Orion spacecraft will replace the space shuttle and will be the first human spacecraft since the Apollo program to leave low earth orbit. This vehicle will serve as the cornerstone of a complete space transportation system with a myriad of mission requirements necessitating rendezvous to multiple vehicles in earth orbit, around the moon and eventually beyond . These goals will require a complex and robust vehicle that is, significantly different from both the space shuttle and the command module of the Apollo program. Historically, orbit operations have been accomplished with heavy reliance on ground support and manual crew reconfiguration and monitoring. One major difference with Orion is that automation will be incorporated as a key element of the man-vehicle system. The automated system will consist of software devoted to transitioning between events based on a master timeline. This effectively adds a layer of high level sequencing that moves control of the vehicle from one phase to the next. This type of automated control is not entirely new to spacecraft since the shuttle uses a version of this during ascent and entry operations. During shuttle orbit operations however many of the software modes and hardware switches must be manually configured through the use of printed procedures and instructions voiced from the ground. The goal of the automation scheme on Orion is to extend high level automation to all flight phases. The move towards automation represents a large shift from current space shuttle operations, and so these new systems will be adopted gradually via various safeguards. These include features such as authority-to-proceed, manual down modes, and functional inhibits. This paper describes the contrast between the manual and ground approach of the space shuttle and the proposed automation of the Orion vehicle. I will introduce typical orbit operations that are common to all rendezvous missions and go on to describe the current Orion automation architecture and contrast it with shuttle rendezvous techniques and circumstances. The shuttle rendezvous profile is timed to take approximately 3 days from orbit insertion to docking at the International Space Station (ISS). This process can be divided into 3 phases: far-field, mid-field and proximity operations. The far-field stage is characterized as the most quiescent phase. The spacecraft is usually too far to navigate using relative sensors and uses the Inertial Measurement Units (IMU s) to numerically solve for its position. The maneuvers are infrequent, roughly twice per day, and are larger than other burns in the profile. The shuttle uses this opportunity to take extensive ground based radar updates and keep high fidelity orbit states on the ground. This state is then periodically uplinked to the shuttle computers. The targeting solutions for burn maneuvers are also computed on the ground and uplinked. During the burn the crew is responsible for setting the shuttle attitude and configuring the propulsion system for ignition. Again this entire process is manually driven by both crew and ground activity. The only automatic processes that occur are associated with the real-time execution of the burn. The Orion automated functionality will seek to relieve the workload of both the crew and ground during this phase

Ruiz, Jose O,↗
NASA NTRS2011

Orion Flight Test-1 Thermal Protection System Instrumentation

The Orion Crew Exploration Vehicle (CEV) was originally under development to provide crew transport to the International Space Station after the retirement of the Space Shuttle, and to provide a means for the eventual return of astronauts to the Moon. With the current changes in the future direction of the United States human exploration programs, the focus of the Orion project has shifted to the project s first orbital flight test, designated Orion Flight Test 1 (OFT-1). The OFT-1 is currently planned for launch in July 2013 and will demonstrate the Orion vehicle s capability for performing missions in low Earth orbit (LEO), as well as extensibility beyond LEO for select, critical areas. Among the key flight test objectives are those related to validation of the re-entry aerodynamic and aerothermal environments, and the performance of the thermal protection system (TPS) when exposed to these environments. A specific flight test trajectory has been selected to provide a high energy entry beyond that which would be experienced during a typical low Earth orbit return, given the constraints imposed by the possible launch vehicles. This trajectory resulted from a trade study that considered the relative benefit of conflicting objectives from multiple subsystems, and sought to provide the maximum integrated benefit to the re-entry state-of-the-art. In particular, the trajectory was designed to provide: a significant, measureable radiative heat flux to the windward surface; data on boundary transition from laminar to turbulent flow; and data on catalytic heating overshoot on non-ablating TPS. In order to obtain the necessary flight test data during OFT-1, the vehicle will need to have an adequate quantity of instrumentation. A collection of instrumentation is being developed for integration in the OFT-1 TPS. In part, this instrumentation builds upon the work performed for the Mars Science Laboratory Entry, Descent and Landing Instrument (MEDLI) suite to instrument the OFT-1 ablative heat shield. The MEDLI integrated sensor plugs and pressure sensors will be adapted for compatibility with the Orion TPS design. The sensor plugs will provide in-depth temperature data to support aerothermal and TPS model correlation, and the pressure sensors will provide a flush air data system for validation of the entry and descent aerodynamic environments. In addition, a radiometer design will be matured to measure the radiative component of the reentry heating at two locations on the heat shield. For the back shell, surface thermocouple and pressure port designs will be developed and applied which build upon the heritage of the Space Shuttle Program for instrumentation of reusable surface insulation (RSI) tiles. The quantity and location of the sensors has been determined to balance the needs of the reentry disciplines with the demands of the hardware development, manufacturing and integration. Measurements which provided low relative value and presented significant engineering development effort were, unfortunately, eliminated. The final TPS instrumentation has been optimized to target priority test objectives. The data obtained will serve to provide a better understanding of reentry environments for the Orion capsule design, reduce margins, and potentially reduce TPS mass or provide TPS extensibility for alternative missions.

Kowal, T. John↗
NASA NTRS2012

The Space Operations Simulation Center (SOSC) and Closed-Loop Hardware Testing for Orion Rendezvous System Design

The exploration goals of Orion / MPCV Project will require a mature Rendezvous, Proximity Operations and Docking (RPOD) capability. Ground testing autonomous docking with a next-generation sensor such as the Vision Navigation Sensor (VNS) is a critical step along the path of ensuring successful execution of autonomous RPOD for Orion. This paper will discuss the testing rationale, the test configuration, the test limitations and the results obtained from tests that have been performed at the Lockheed Martin Space Operations Simulation Center (SOSC) to evaluate and mature the Orion RPOD system. We will show that these tests have greatly increased the confidence in the maturity of the Orion RPOD design, reduced some of the latent risks and in doing so validated the design philosophy of the Orion RPOD system. This paper is organized as follows: first, the objectives of the test are given. Descriptions of the SOSC facility, and the Orion RPOD system and associated components follow. The details of the test configuration of the components in question are presented prior to discussing preliminary results of the tests. The paper concludes with closing comments.

Milenkovic, Zoran↗
NASA NTRS2013

Tuning and Robustness Analysis for the Orion Absolute Navigation System

The Orion Multi-Purpose Crew Vehicle (MPCV) is currently under development as NASA's next-generation spacecraft for exploration missions beyond Low Earth Orbit. The MPCV is set to perform an orbital test flight, termed Exploration Flight Test 1 (EFT-1), some time in late 2014. The navigation system for the Orion spacecraft is being designed in a Multi-Organizational Design Environment (MODE) team including contractor and NASA personnel. The system uses an Extended Kalman Filter to process measurements and determine the state. The design of the navigation system has undergone several iterations and modifications since its inception, and continues as a work-in-progress. This paper seeks to show the efforts made to-date in tuning the filter for the EFT-1 mission and instilling appropriate robustness into the system to meet the requirements of manned space ight. Filter performance is affected by many factors: data rates, sensor measurement errors, tuning, and others. This paper focuses mainly on the error characterization and tuning portion. Traditional efforts at tuning a navigation filter have centered around the observation/measurement noise and Gaussian process noise of the Extended Kalman Filter. While the Orion MODE team must certainly address those factors, the team is also looking at residual edit thresholds and measurement underweighting as tuning tools. Tuning analysis is presented with open loop Monte-Carlo simulation results showing statistical errors bounded by the 3-sigma filter uncertainty covariance. The Orion filter design uses 24 Exponentially Correlated Random Variable (ECRV) parameters to estimate the accel/gyro misalignment and nonorthogonality. By design, the time constant and noise terms of these ECRV parameters were set to manufacturer specifications and not used as tuning parameters. They are included in the filter as a more analytically correct method of modeling uncertainties than ad-hoc tuning of the process noise. Tuning is explored for the powered-flight ascent phase, where measurements are scarce and unmodelled vehicle accelerations dominate. On orbit, there are important trade-off cases between process and measurement noise. On entry, there are considerations about trading performance accuracy for robustness. Process Noise is divided into powered flight and coasting ight and can be adjusted for each phase and mode of the Orion EFT-1 mission. Measurement noise is used for the integrated velocity measurements during pad alignment. It is also used for Global Positioning System (GPS) pseudorange and delta- range measurements during the rest of the flight. The robustness effort has been focused on maintaining filter convergence and performance in the presence of unmodeled error sources. These include unmodeled forces on the vehicle and uncorrected errors on the sensor measurements. Orion uses a single-frequency, non-keyed GPS receiver, so the effects due to signal distortion in Earth's ionosphere and troposphere are present in the raw measurements. Results are presented showing the efforts to compensate for these errors as well as characterize the residual effect for measurement noise tuning. Another robustness tool in use is tuning the residual edit thresholds. The trade-off between noise tuning and edit thresholds is explored in the context of robustness to errors in dynamics models and sensor measurements. Measurement underweighting is also presented as a method of additional robustness when processing highly accurate measurements in the presence of large filter uncertainties.

Holt, Greg N.↗
NASA NTRS2013

Orion Scripted Interface Generator (OrionSIG)

The Orion spacecraft undergoing development at NASA and Lockheed Martin aims to launch the first humans to set foot on asteroids and Mars.' Sensors onboard Orion must transmit back to Earth astronomical amounts of data recording almost everything in 50,231 lb. (22,784 kg)2 of spacecraft, down to the temperatures, voltages, or torsions of even the most minor components. This report introduces the new Orion Scripted Interface Generator (OrionSIG) software created by summer 2013 NASA interns Robert Dooling and Samuel Harris. OrionSIG receives a list of Orion variables and produces a script to graph these measurements regardless of their size or type. The program also accepts many other input options to manipulate displays, such as limits on the graph's range or commands to graph different values in a reverse sawtooth wave. OrionSIG paves the way for monitoring stations on Earth to process, display, and test Orion data much more efficiently, a helpful asset in preparation for Orion's first test mission in 2014. Figure I.

Dooling, Robert J.↗
NASA NTRS2015

Orion Launch Abort System Jettison Motor Performance During Exploration Flight Test 1

This paper presents an overview of the flight test objectives and performance of the Orion Launch Abort System during Exploration Flight Test-1. Exploration Flight Test-1, the first flight test of the Orion spacecraft, was managed and led by the Orion prime contractor, Lockheed Martin, and launched atop a United Launch Alliance Delta IV Heavy rocket. This flight test was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety. This test included the first flight test of the Launch Abort System performing Orion nominal flight mission critical objectives. Although the Orion Program has tested a number of the critical systems of the Orion spacecraft on the ground, the launch environment cannot be replicated completely on Earth. Data from this flight will be used to verify the function of the jettison motor to separate the Launch Abort System from the crew module so it can continue on with the mission. Selected Launch Abort System flight test data is presented and discussed in the paper. Through flight test data, Launch Abort System performance trends have been derived that will prove valuable to future flights as well as the manned space program.

McCauley, Rachel J.↗
NASA NTRS2016

Evolution of Orion Mission Design for Exploration Mission 1 and 2

The evolving mission design and concepts of NASA's next steps have shaped Orion into the spacecraft that it is today. Since the initial inception of Orion, through the Constellation Program, and now in the Exploration Mission frame-work with the Space Launch System (SLS), each mission design concept and program goal have left Orion with a set of capabilities that can be utilized in many different mission types. Exploration Missions 1 and 2 (EM-1 and EM-2) have now been at the forefront of the mission design focus for the last several years. During that time, different Design Reference Missions (DRMs) were built, analyzed, and modified to solve or mitigate enterprise level design trades to ensure a viable mission from launch to landing. The resulting DRMs for EM-1 and EM-2 were then expanded into multi-year trajectory scans to characterize vehicle performance and Earth-Moon geometry trends. This provides Orion's subsystems with stressing reference trajectories to help design their system. Now that Orion has progressed through the Preliminary and Critical Design Re-views (PDR and CDR) there is a general shift in the focus of mission design from aiding the vehicle design to providing mission specific products needed for pre-flight and real time operations. Some of the mission specific products need-ed include analysis of steering law performance, inputs into navigational accura-cy assessments, abort options at any point in the mission for each valid trajecto-ry in the launch window, recontact avoidance between the upper stage and Orion post nominal separation, etc.

Gutkowski, Jeffrey P.↗
NASA NTRS2016

Orion Exploration Flight Test 1 (EFT-1) Best Estimated Trajectory Development

The Orion Exploration Flight Test 1 (EFT-1) mission successfully flew on Dec 5, 2014 atop a Delta IV Heavy launch vehicle. The goal of Orions maiden flight was to stress the system by placing an uncrewed vehicle on a high-energy trajectory replicating conditions similar to those that would be experienced when returning from an asteroid or a lunar mission. The Orion navigation team combined all trajectory data from the mission into a Best Estimated Trajectory (BET) product. There were significant challenges in data reconstruction and many lessons were learned for future missions. The team used an estimation filter incorporating radar tracking, onboard sensors (Global Positioning System and Inertial Measurement Unit), and day-of-flight weather balloons to evaluate the true trajectory flown by Orion. Data was published for the entire Orion EFT-1 flight, plus objects jettisoned during entry such as the Forward Bay Cover. The BET customers include approximately 20 disciplines within Orion who will use the information for evaluating vehicle performance and influencing future design decisions.

Holt, Greg N.↗
NASA NTRS2017

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.↗