Search NASA⌕ Search

SEARCH · Search NASA

Results for “contingency”

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 307 records · Page 17

Planning to Explore: Using a Coordinated Multisource Infrastructure to Overcome Present and Future Space Flight Planning Challenges

Few human endeavors present as much of a planning and scheduling challenge as space flight, particularly manned space flight. Just on the operational side of it, efforts of thousands of people across hundreds of organizations need to be coordinated. Numerous tasks of varying complexity and nature, from scientific to construction, need to be accomplished within limited mission time frames. Resources need to be carefully managed and contingencies worked out, often on a very short notice. From the beginning of the NASA space program, planning has been done by large teams of domain experts working months, sometimes years, to put together a single mission. This approach, while proven very reliable up to now, is becoming increasingly harder to sustain. Elevated levels of NASA space activities, from deployment of the new Crew Exploration Vehicle (CEV) and completion of the International Space Station (ISS), to the planned lunar missions and permanent lunar bases, will put an even greater strain on this largely manual process. While several attempts to automate it have been made in the past, none have fully succeeded. In this paper we describe the current NASA planning methods, outline their advantages and disadvantages, discuss the planning challenges of upcoming missions and propose a distributed planning/scheduling framework (CMMD) aimed at unifying and optimizing the planning effort. CMMD will not attempt to make the process completely automated, but rather serve in a decision support capacity for human managers and planners. It will help manage information gathering, creation of partial and consolidated schedules, inter-team negotiations, contingencies investigation, and rapid re-planning when the situation demands it. The fist area of CMMD application will be planning for Extravehicular Activities (EVA) and associated logistics. Other potential applications, not only in the space flight domain, and future research efforts will be discussed as well.

Balaban, Edward↗

International Space Station (ISS) Oxygen High Pressure Storage Management

High pressure oxygen onboard the ISS provides support for Extra Vehicular Activities (EVA) and contingency metabolic support for the crew. This high pressure 02 is brought to the ISS by the Space Shuttle and is transferred using the Oxygen Recharge Compressor Assembly (ORCA). There are several drivers that must be considered in managing the available high pressure 02 on the ISS. The amount of O2 the Shuttle can fly up is driven by manifest mass limitations, launch slips, and on orbit Shuttle power requirements. The amount of 02 that is used from the ISS high pressure gas tanks (HPGT) is driven by the number of Shuttle docked and undocked EVAs, the type of EVA prebreath protocol that is used and contingency use of O2 for metabolic support. Also, the use of the ORCA must be managed to optimize its life on orbit and assure that it will be available to transfer the planned amount of O2 from the Shuttle. Management of this resource has required long range planning and coordination between Shuttle manifest on orbit plans. To further optimize the situation hardware options have been pursued.

Lewis, John R.↗

A Comparison of Probabilistic and Deterministic Campaign Analysis for Human Space Exploration

Human space exploration is by its very nature an uncertain endeavor. Vehicle reliability, technology development risk, budgetary uncertainty, and launch uncertainty all contribute to stochasticity in an exploration scenario. However, traditional strategic analysis has been done in a deterministic manner, analyzing and optimizing the performance of a series of planned missions. History has shown that exploration scenarios rarely follow such a planned schedule. This paper describes a methodology to integrate deterministic and probabilistic analysis of scenarios in support of human space exploration. Probabilistic strategic analysis is used to simulate "possible" scenario outcomes, based upon the likelihood of occurrence of certain events and a set of pre-determined contingency rules. The results of the probabilistic analysis are compared to the nominal results from the deterministic analysis to evaluate the robustness of the scenario to adverse events and to test and optimize contingency planning.

Merrill, R. Gabe↗

Crew Exploration Vehicle (CEV) Potable Water System Verification Description

The Crew Exploration Vehicle (CEV), also known as Orion, will ferry a crew of up to six astronauts to the International Space Station (ISS), or a crew of up to four astronauts to the moon. The first launch of CEV is scheduled for approximately 2014. A stored water system on the CEV will supply the crew with potable water for various purposes: drinking and food rehydration, hygiene, medical needs, sublimation, and various contingency situations. The current baseline biocide for the stored water system is ionic silver, similar in composition to the biocide used to maintain quality of the water transferred from the Orbiter to the ISS and stored in Contingency Water Containers (CWCs). In the CEV water system, the ionic silver biocide is expected to be depleted from solution due to ionic silver plating onto the surfaces of the materials within the CEV water system, thus negating its effectiveness as a biocide. Since the biocide depletion is expected to occur within a short amount of time after loading the water into the CEV water tanks at the Kennedy Space Center (KSC), an additional microbial

Peterson, Laurie↗

Crew Exploration Vehicle (CEV) Potable Water System Verification Description

The Crew Exploration Vehicle (CEV), also known as Orion, will ferry a crew of up to six astronauts to the International Space Station (ISS), or a crew of up to four astronauts to the moon. The first launch of CEV is scheduled for approximately 2014. A stored water system on the CEV will supply the crew with potable water for various purposes: drinking and food rehydration, hygiene, medical needs, sublimation, and various contingency situations. The current baseline biocide for the stored water system is ionic silver, similar in composition to the biocide used to maintain quality of the water transferred from the Orbiter to the ISS and stored in Contingency Water Containers (CWCs). In the CEV water system, the ionic silver biocide is expected to be depleted from solution due to ionic silver plating onto the surfaces of the materials within the CEV water system, thus negating its effectiveness as a biocide. Since the biocide depletion is expected to occur within a short amount of time after loading the water into the CEV water tanks at the Kennedy Space Center (KSC), an additional microbial control is a 0.1 micron point of use filter that will be used at the outlet of the Potable Water Dispenser (PWD). Because this may be the first time NASA is considering a stored water system for longterm missions that does not maintain a residual biocide, a team of experts in materials compatibility, biofilms and point of use filters, surface treatment and coatings, and biocides has been created to pinpoint concerns and perform testing to help alleviate those concerns related to the CEV water system. Results from the test plans laid out in the paper presented to SAE last year (Crew Exploration Vehicle (CEV) Potable Water System Verification Coordination, 2008012083) will be detailed in this paper. Additionally, recommendations for the CEV verification will be described for risk mitigation in meeting the physicochemical and microbiological requirements on the CEV PWS.

Peterson, Laurie↗

Hubble Servicing Challenges Drive Innovation of Shuttle Rendezvous Techniques

Hubble Space Telescope (HST) servicing, performed by Space Shuttle crews, has contributed to what is arguably one of the most successful astronomy missions ever flown. Both nominal and contingency proximity operations techniques were developed to enable successful servicing, while lowering the risk of damage to HST systems, and improve crew safety. Influencing the development of these techniques were the challenges presented by plume impingement and HST performance anomalies. The design of both the HST and the Space Shuttle was completed before the potential of HST contamination and structural damage by shuttle RCS jet plume impingement was fully understood. Relative navigation during proximity operations has been challenging, as HST was not equipped with relative navigation aids. Since HST reached orbit in 1990, proximity operations design for servicing missions has evolved as insight into plume contamination and dynamic pressure has improved and new relative navigation tools have become available. Servicing missions have provided NASA with opportunities to gain insight into servicing mission design and development of nominal and contingency procedures. The HST servicing experiences and lessons learned are applicable to other programs that perform on-orbit servicing and rendezvous, both human and robotic.

Goodman, John L.↗

Design and Implementation of the Automated Rendezvous Targeting Algorithms for Orion

The Orion vehicle will be designed to perform several rendezvous missions: rendezvous with the ISS in Low Earth Orbit (LEO), rendezvous with the EDS/Altair in LEO, a contingency rendezvous with the ascent stage of the Altair in Low Lunar Orbit (LLO) and a contingency rendezvous in LLO with the ascent and descent stage in the case of an aborted lunar landing. Therefore, it is not difficult to realize that each of these scenarios imposes different operational, timing, and performance constraints on the GNC system. To this end, a suite of on-board guidance and targeting algorithms have been designed to meet the requirement to perform the rendezvous independent of communications with the ground. This capability is particularly relevant for the lunar missions, some of which may occur on the far side of the moon. This paper will describe these algorithms which are designed to be structured and arranged in such a way so as to be flexible and able to safely perform a wide variety of rendezvous trajectories. The goal of the algorithms is not to merely fly one specific type of canned rendezvous profile. Conversely, it was designed from the start to be general enough such that any type of trajectory profile can be flown.(i.e. a coelliptic profile, a stable orbit rendezvous profile, and a expedited LLO rendezvous profile, etc) all using the same rendezvous suite of algorithms. Each of these profiles makes use of maneuver types which have been designed with dual goals of robustness and performance. They are designed to converge quickly under dispersed conditions and they are designed to perform many of the functions performed on the ground today. The targeting algorithms consist of a phasing maneuver (NC), an altitude adjust maneuver (NH), and plane change maneuver (NPC), a coelliptic maneuver (NSR), a Lambert targeted maneuver, and several multiple-burn targeted maneuvers which combine one of more of these algorithms. The derivation and implementation of each of these algorithms will be discussed in detail, as well and the Rendezvous Targeting "wrapper" which will sequentially tie them all together into a single onboard targeting tool which can produce a final integrated rendezvous trajectory. In a similar fashion, the various guidance modes available for flying out each of these maneuvers will be discussed as well. This paradigm of having the onboard guidance & targeting capability described above is different than the way the Space Shuttle has operated thus far. As a result, a discussion of these differences in terms of operations and ground and crew intervention will also be discussed. However, the general framework of how the mission designers on the ground first perform all mission design and planning functions, and then uplink that burn plan to the vehicle ensures that the ground will be involved to ensure safety and reliability. The only real difference is which of these functions will be done onboard vs. on the ground as done currently. Finally, this paper will describe the performance of each of these algorithms individually as well as the entire suite of algorithms as applied to the Orion ISS and EDS/Altair rendezvous missions in LEO. These algorithms have been incorporated in both a Linear Covariance environment and a Monte Carlo environment and the results of these dispersion analyses will be presented in the paper as well.

DSouza, Christopher↗

Crew Exploration Vehicle Potable Water System Verification Description

A stored water system on the crew exploration vehicle (CEV) will supply the crew with potable water for: drinking and food rehydration, hygiene, medical needs, sublimation, and various contingency situations. The current baseline biocide for the stored water system is ionic silver, similar in composition to the biocide used to maintain the quality of the water, transferred from the orbiter to the International Space Station, stored in contingency water containers. In the CEV water system, a depletion of the ionic silver biocide is expected due to ionic silver-plating onto the surfaces of materials within the CEV water system, thus negating its effectiveness as a biocide. Because this may be the first time NASA is considering a stored water system for long-term missions that do not maintain a residual biocide, a team of experts in materials compatibility, biofilms and point-of-use filters, surface treatment and coatings, and biocides has been created to pinpoint concerns and perform the testing that will help alleviate concerns related to the CEV water system.

Tuan, George↗

Evaluation of Dual Pressurized Rover Operations During Simulated Planetary Surface Exploration

Introduction: A pair of small pressurized rovers (Space Exploration Vehicles, or SEVs) is at the center of the Global Point-of-Departure architecture for future human planetary exploration. Simultaneous operation of multiple crewed surface assets should maximize productive crew time, minimize overhead, and preserve contingency return paths. Methods: A 14-day mission simulation was conducted in the Arizona desert as part of NASA?s 2010 Desert Research and Technology Studies (DRATS). The simulation involved two SEV concept vehicles performing geological exploration under varied operational modes affecting both the extent to which the SEVs must maintain real-time communications with mission control ("Continuous" vs. "Twice-a-Day") and their proximity to each other ("Lead-and-Follow" vs. "Divide-and-Conquer"). As part of a minimalist lunar architecture, no communications relay satellites were assumed. Two-person crews consisting of an astronaut and a field geologist operated each SEV, day and night, throughout the entire 14-day mission, only leaving via the suit ports to perform simulated extravehicular activities. Standard metrics enabled quantification of the habitability and usability of all aspects of the SEV concept vehicles throughout the mission, as well as comparison of the extent to which the operating modes affected crew productivity and performance. Practically significant differences in the relevant metrics were prospectively defined for the testing of all hypotheses. Results and Discussion: Data showed a significant 14% increase in available science time (AST) during Lead-and-Follow mode compared with Divide-and-Conquer, primarily because of the minimal overhead required to maintain communications during Lead-and-Follow. In Lead-and-Follow mode, there was a non-significant 2% increase in AST during Twice-a-Day vs. Continuous communications. Situational awareness of the other vehicle?s location, activities, and contingency return constraints were enhanced during Lead-and-Follow and Twice-a-Day communications modes due to line-of-sight and direct SEV-to-SEV communication. Preliminary analysis of Scientific Data Quality and Observation Quality metrics showed no significant differences between modes.

Abercromby, Andrew F. J.↗

Flight Dynamics Operations: Methods and Lessons Learned from Space Shuttle Orbit Operations

The Flight Dynamics Officer is responsible for trajectory maintenance of the Space Shuttle. This paper will cover high level operational considerations, methodology, procedures, and lessons learned involved in performing the functions of orbit and rendezvous Flight Dynamics Officer and leading the team of flight dynamics specialists during different phases of flight. The primary functions that will be address are: onboard state vector maintenance, ground ephemeris maintenance, calculation of ground and spacecraft acquisitions, collision avoidance, burn targeting for the primary mission, rendezvous, deorbit and contingencies, separation sequences, emergency deorbit preparation, mass properties coordination, payload deployment planning, coordination with the International Space Station, and coordination with worldwide trajectory customers. Each of these tasks require the Flight Dynamics Officer to have cognizance of the current trajectory state as well as the impact of future events on the trajectory plan in order to properly analyze and react to real-time changes. Additionally, considerations are made to prepare flexible alternative trajectory plans in the case timeline changes or a systems failure impact the primary plan. The evolution of the methodology, procedures, and techniques used by the Flight Dynamics Officer to perform these tasks will be discussed. Particular attention will be given to how specific Space Shuttle mission and training simulation experiences, particularly off-nominal or unexpected events such as shortened mission durations, tank failures, contingency deorbit, navigation errors, conjunctions, and unexpected payload deployments, have influenced the operational procedures and training for performing Space Shuttle flight dynamics operations over the history of the program. These lessons learned can then be extended to future vehicle trajectory operations.

Cutri-Kohart, Rebecca M.↗

Hayabusa Recovery, Curation and Preliminary Sample Analysis: Lessons Learned from Recent Sample Return Mission

I describe lessons learned from my participation on the Hayabusa Mission, which returned regolith grains from asteroid Itokawa in 2010 [1], comparing this with the recently returned Stardust Spacecraft, which sampled the Jupiter Family comet Wild 2. Spacecraft Recovery Operations: The mission Science and Curation teams must actively participate in planning, testing and implementing spacecraft recovery operations. The crash of the Genesis spacecraft underscored the importance of thinking through multiple contingency scenarios and practicing field recovery for these potential circumstances. Having the contingency supplies on-hand was critical, and at least one full year of planning for Stardust and Hayabusa recovery operations was necessary. Care must be taken to coordinate recovery operations with local organizations and inform relevant government bodies well in advance. Recovery plans for both Stardust and Hayabusa had to be adjusted for unexpectedly wet landing site conditions. Documentation of every step of spacecraft recovery and deintegration was necessary, and collection and analysis of launch and landing site soils was critical. We found the operation of the Woomera Text Range (South Australia) to be excellent in the case of Hayabusa, and in many respects this site is superior to the Utah Test and Training Range (used for Stardust) in the USA. Recovery operations for all recovered spacecraft suffered from the lack of a hermetic seal for the samples. Mission engineers should be pushed to provide hermetic seals for returned samples. Sample Curation Issues: More than two full years were required to prepare curation facilities for Stardust and Hayabusa. Despite this seemingly adequate lead time, major changes to curation procedures were required once the actual state of the returned samples became apparent. Sample databases must be fully implemented before sample return for Stardust we did not adequately think through all of the possible sub sampling and analytical activities before settling on a database design - Hayabusa has done a better job of this. Also, analysis teams must not be permitted to devise their own sample naming schemes. The sample handling and storage facilities for Hayabusa are the finest that exist, and we are now modifying Stardust curation to take advantage of the Hayabusa facilities. Remote storage of a sample subset is desirable. Preliminary Examination (PE) of Samples: There must be some determination of the state and quantity of the returned samples, to provide a necessary guide to persons requesting samples and oversight committees tasked with sample curation oversight. Hayabusa s sample PE, which is called HASPET, was designed so that late additions to the analysis protocols were possible, as new analytical techniques became available. A small but representative number of recovered grains are being subjected to in-depth characterization. The bulk of the recovered samples are being left untouched, to limit contamination. The HASPET plan takes maximum advantage of the unique strengths of sample return missions

Zolensky, Michael E.↗

First Results from NASA's Lunar Atmosphere and Dust Environment Explorer (LADEE)

As of early August, 2013, the Lunar Atmosphere and Dust Environment Explorer (LADEE) mission is scheduled for launch on a Minotaur V rocket from Wallops Flight Facility during a five-day launch period that opens on Sept. 6, 2013 (early Sept. 7 UTC). LADEE will address 40 year-old mysteries of the lunar atmosphere and the question of levitated lunar dust. It will also pioneer the next generation of optical space communications. LADEE will assess the composition of the lunar atmosphere and investigate the processes that control its distribution and variability, including sources, sinks, and surface interactions. LADEE will also determine whether dust is present in the lunar exosphere, and reveal its sources and variability. These investigations are relevant to our understanding of surface boundary exospheres and dust processes occurring at many objects throughout the solar system, address questions regarding the origin and evolution of lunar volatiles, and have potential implications for future exploration activities. Following a successful launch, LADEE will enter a series of phasing orbits, which allows the spacecraft to arrive at the Moon at the proper time and phase. This approach accommodates any dispersion in the Minotaur V launch injection. LADEE's arrival at the moon in early October. The spacecraft will approach the moon from its leading edge, travel behind the Moon out of sight of the Earth, and then re-emerge and execute a three-minute Lunar Orbit Insertion maneuver. This will place LADEE in an elliptical retrograde equatorial orbit with an orbital period of approximately 24 hours. A series of maneuvers is then performed to reduce the orbit to become nearly circular with a 156-mile (250- kilometer) altitude. Spacecraft checkout and science instrument commissioning will commence in early-October and will nominally span 30 days but can be extended for an additional 30 days in the event of contingencies. Following commissioning, the 100-day Science Phase is performed at an orbit with periapsis between 20-60 km. This orbit must be constantly managed due to the Moon's highly inhomogeneous gravity field. During the Science Phase, the moon will rotate more than three times underneath the LADEE orbit. LADEE employs a high heritage instrument payload: a Neutral Mass Spectrometer (NMS) from Goddard Space Flight Center, an Ultraviolet/Visible Spectrometer (UVS) from Ames Research Center, and a dust detection experiment (LDEX) from the University of Colorado/LASP. It will also carry the Lunar Laser Communications Demonstration (LLCD) as a technology demonstration. The LLCD is funded by the Human Exploration Operations Mission Directorate (HEOMD), managed by GSFC, and built by the MIT Lincoln Lab. Contingent upon LADEE's successful lunar orbit insertion and checkout, we will report the early results from the science investigations.

Moon↗

Earth Return Navigation Analysis for Manned Spacecraft Using Optical and Radiometric Measurements

Future manned space missions will travel beyond low Earth orbit with more stringent navigation requirements and fewer navigation resources than used for the Apollo Program of the 1960s. A study has been performed to assess radiometric and optical tracking capabilities necessary to meet nominal and contingency Earth entry flight path angle requirements. Results indicate that 3 tracking stations will be insufficient for meeting nominal entry requirements, while the performance of a 6 station architecture is dependent on the entry geometry. Optical tracking results indicate that a narrow-angle camera is required for satisfying contingency Earth return requirements.

GN&C↗

Capturing Safety Requirements to Enable Effective Task Allocation Between Humans and Automaton in Increasingly Autonomous Systems

There is a current drive towards enabling the deployment of increasingly autonomous systems in the National Airspace System (NAS). However, shifting the traditional roles and responsibilities between humans and automation for safety critical tasks must be managed carefully, otherwise the current emergent safety properties of the NAS may be disrupted. In this paper, a verification activity to assess the emergent safety properties of a clearly defined, safety critical, operational scenario that possesses tasks that can be fluidly allocated between human and automated agents is conducted. Task allocation role sets were proposed for a human-automation team performing a contingency maneuver in a reduced crew context. A safety critical contingency procedure (engine out on takeoff) was modeled in the Soar cognitive architecture, then translated into the Hybrid Input Output formalism. Verification activities were then performed to determine whether or not the safety properties held over the increasingly autonomous system. The verification activities lead to the development of several key insights regarding the implicit assumptions on agent capability. It subsequently illustrated the usefulness of task annotations associated with specialized requirements (e.g., communication, timing etc.), and demonstrated the feasibility of this approach.

Neogi, Natasha A.↗

Monitoring of the Atmosphere on the International Space Station with the Air Quality Monitor

During the early years of human spaceflight, short duration missions allowed for monitoring of the spacecraft environment to be performed via archival sampling, in which samples were returned to Earth for analysis. With the construction of the International Space Station (ISS) and the accompanying extended mission durations, the need for enhanced, real-time monitors became apparent. The Volatile Organic Analyzer (VOA) operated on ISS for 7 years, where it assessed trace volatile organic compounds in the cabin air. The large and fixed-position VOA was eventually replaced with the smaller Air Quality Monitor (AQM). Since March 2013, the atmosphere of the U.S. Operating Segment (USOS) has been monitored in near real-time by a pair of AQMs. These devices consist of a gas chromatograph (GC) coupled with a differential mobility spectrometer (DMS) and currently target detection list of 22 compounds. These targets are of importance to both crew health and the Environmental Control and Life Support Systems (ECLSS) on ISS. Data is collected autonomously every 73 hours, though the units can be controlled remotely from mission control to collect data more frequently during contingency or troubleshooting operations. Due to a nominal three-year lifetime on-orbit, the initial units were replaced in February 2016. This paper will focus on the preparation and use of the AQMs over the past several years. A description of the technical aspects of the AQM will be followed by lessons learned from the deployment and operation of the first set of AQMs. These lessons were used to improve the already-excellent performance of the instruments prior to deployment of the replacement units. Data trending over the past several years of operation on ISS will also be discussed, including data obtained during a survey of the USOS modules. Finally, a description of AQM use for contingency and investigative studies will be presented.

Wallace William T.↗

Towards a Universal Biology: Is the Origin and Evolution of Life Predictable?

The origin and evolution of life seems an unpredictable oddity, based on the quirks of contingency. Celebrated by the late Stephen Jay Gould in several books, "evolution by contingency" has all the adventure of a thriller, but lacks the predictive power of the physical sciences. Not necessarily so, replied Simon Conway Morris, for convergence reassures us that certain evolutionary responses are replicable. The outcome of this debate is critical to Astrobiology. How can we understand where we came from on Earth without prophesy? Further, we cannot design a rational strategy for the search for life elsewhere - or to understand what the future will hold for life on Earth and beyond - without extrapolating from pre-biotic chemistry and evolution. There are several indirect approaches to understanding, and thus describing, what life must be. These include philosophical approaches to defining life (is there even a satisfactory definition of life?), using what we know of physics, chemistry and life to imagine alternate scenarios, using different approaches that life takes as pseudoreplicates (e.g., ribosomal vs non-ribosomal protein synthesis), and experimental approaches to understand the art of the possible. Given that: (1) Life is a process based on physical components rather than simply an object; (2). Life is likely based on organic carbon and needs a solvent for chemistry, most likely water, and (3) Looking for convergence in terrestrial evolution we can predict certain tendencies, if not quite "laws", that provide predictive power. Biological history must obey the laws of physics and chemistry, the principles of natural selection, the constraints of an evolutionary past, genetics, and developmental biology. This amalgam creates a surprising amount of predictive power in the broad outline. Critical is the apparent prevalence of organic chemistry, and uniformity in the universe of the laws of chemistry and physics. Instructive is the widespread occurrence of convergent or parallel evolution, which suggests that under certain conditions similar solutions are arrived at independently.

Universal biology; life everywhere↗

Trajectory Design Considerations for Exploration Mission 1

Exploration Mission 1 (EM-1) will be the first mission to send an uncrewed Orion Multi-Purpose Crew Vehicle (MPCV) to cislunar space in the fall of 2019. EM-1 was originally conceived as a lunar free-return mission, but was later changed to a Distant Retrograde Orbit (DRO) mission as a precursor to the Asteroid Redirect Mission. To understand the required mission performance (i.e., propellant requirement), a series of trajectory optimization runs was conducted using JSC's Copernicus spacecraft trajectory optimization tool. In order for the runs to be done in a timely manner, it was necessary to employ a parallelization approach on a computing cluster using a new trajectory scan tool written in Python. Details of the scan tool are provided and how it is used to perform the scans and post-process the results. Initially, a scan of daily due east launched EM-1 DRO missions in 2018 was made. Valid mission opportunities are ones that do not exceed the useable propellant available to perform the required burns. The initial scan data showed the propellant and delta-V performance patterns for each launch period. As questions were raised from different subsystems (e.g., power, thermal, communications, flight operations, etc.), the mission parameters or data that were of interest to them were added to the scan output data file. The additional data includes: (1) local launch and landing times in relation to sunrise and sunset, (2) length of eclipse periods during the in-space portion of the mission, (3) Earth line of sight from cislunar space, (4) Deep Space Network field of view looking towards cislunar space, and (5) variation of the downrange distance from Earth entry interface to splashdown. Mission design trades can also be performed based on the information that the additional data shows. For example, if the landing is in darkness, but the recovery operations team desires a landing in daylight, then an analysis is performed to determine how to change the mission design to meet this request. Also, subsystems request feasibility of alternate or contingency mission designs, such as adding an Orion main engine checkout burn or Orion completing all of its burns using only its auxiliary thrusters. This paper examines and presents the evolving trade studies that incorporate subsystem feedback and demonstrate the feasibility of these constrained mission trajectory designs and contingencies.

Dawn, Timothy F.↗

Safe2Ditch Autonomous Crash Management System for Small Unmanned Aerial Systems: Concept Definition and Flight Test Results

Small unmanned aerial systems (sUAS) have the potential for a large array of highly-beneficial applications. These applications are too numerous to comprehensively list, but include search and rescue, fire spotting, precision agriculture, etc. to name a few. Typically sUAS vehicles weigh less than 55 lbs and will be performing flight operations in the National Air Space (NAS). Certain sUAS applications, such as package delivery, will include operations in the close proximity of the general public. The full benefit from sUAS is contingent upon the resolution of several technological areas in order to provide an acceptable level of risk for widespread sUAS operations. Operations of sUAS vehicles pose risks to people and property on the ground as well as manned aviation. Several of the more significant sUAS technological areas include, but are not limited to: autonomous sense and avoid and deconfliction of sUAS from other sUAS and manned aircraft, communications and interfaces between the vehicle and human operators, and the overall reliability of the sUAS and constituent subsystems. While all of the technological areas listed contribute significantly to the safe execution of the sUAS flight operations, contingency or emergency systems can greatly contribute to sUAS risk mitigations to manage situations where the vehicle is in distress. The Safe2Ditch (S2D) system is an autonomous crash management system for sUAS. Its function is to enable sUAS to execute emergency landings and avoid injuring people on the ground, damaging property, and lastly preserving the sUAS and payload. A sUAS flight test effort was performed to test the integration of sub-elements of the S2D system with a representative sUAS multi-rotor.

Glaab, Louis J.↗