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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

An Evidence-based Approach to Developing a Management Strategy for Medical Contingencies on the Lunar Surface: The NASA/Haughton-Mars Project (HMP) 2006 Lunar Medical Contingency Simulation at Devon Island

The lunar architecture for future sortie and outpost missions will require humans to serve on the lunar surface considerably longer than the Apollo moon missions. Although the Apollo crewmembers sustained few injuries during their brief lunar surface activity, injuries did occur and are a concern for the longer lunar stays. Interestingly, lunar medical contingency plans were not developed during Apollo. In order to develop an evidence-base for handling a medical contingency on the lunar surface, a simulation using the moon-Mars analog environment at Devon Island, Nunavut, high Canadian Arctic was conducted. Objectives of this study included developing an effective management strategy for dealing with an incapacitated crewmember on the lunar surface, establishing audio/visual and biomedical data connectivity to multiple centers, testing rescue/extraction hardware and procedures, and evaluating in suit increased oxygen consumption. Methods: A review of the Apollo lunar surface activities and personal communications with Apollo lunar crewmembers provided the knowledge base of plausible scenarios that could potentially injure an astronaut during a lunar extravehicular activity (EVA). Objectives were established to demonstrate stabilization and transfer of an injured crewmember and communication with ground controllers at multiple mission control centers. Results: The project objectives were successfully achieved during the simulation. Among these objectives were extraction from a sloped terrain by a two-member crew in a 1 g analog environment, establishing real-time communication to multiple centers, providing biomedical data to flight controllers and crewmembers, and establishing a medical diagnosis and treatment plan from a remote site. Discussion: The simulation provided evidence for the types of equipment and methods for performing extraction of an injured crewmember from a sloped terrain. Additionally, the necessary communications infrastructure to connect multiple centers worldwide was established from a remote site. The surface crewmembers were confronted with a number of unexpected scenarios including environmental, communications, EVA suit, and navigation challenges during the course of the simulation which provided insight into the challenges of carrying out a medical contingency in an austere environment. The knowledge gained from completing the objectives will be incorporated into the exploration medical requirements involving an incapacitated astronaut on the lunar surface.

Scheuring, R. A.↗
NASA NTRS2005

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Contingency Management

This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗
NASA NTRS2010

Contingency Operations of Americas Next Moon Rocket, Ares V

America has begun the development of a new space vehicle system which will enable humans to return to the moon and reach even farther destinations. The system is called Constellation: it has 2 earth-launch vehicles, Ares I and Ares V; a crew module, Orion; and a lander, Altair with descent and ascent stages. Ares V will launch an Earth Departure Stage (EDS) and Altair into low earth orbit. Ares I will launch the Orion crew module into low earth orbit where it will rendezvous and dock with the Altair and EDS "stack". After rendezvous, the stack will contain four complete rocket systems, each capable of independent operations. Of course this multiplicity of vehicles provides a multiplicity of opportunities for off-nominal behavior and multiple mitigation options for each. Contingency operations are complicated by the issues of crew safety and the possibility of debris from the very large components impacting the ground. This paper examines contingency operations of the EDS in low earth orbit, during the boost to translunar orbit, and after the translunar boost. Contingency operations under these conditions have not been a consideration since the Apollo era and analysis of the possible contingencies and mitigations will take some time to evolve. Since the vehicle has not been designed, much less built, it is not possible to evaluate contingencies from a root-cause basis or from a probability basis; rather they are discussed at an effects level (such as the reaction control system is consuming propellant at a high rate). Mitigations for the contingencies are based on the severity of the off-nominal condition, the time of occurrence, recovery options, options for alternate missions, crew safety, evaluation of the condition (forensics) and future prevention. Some proposed mitigations reflect innovation in thinking and make use of the multiplicity of on-orbit resources including the crew; example: Orion could do a "fly around" to allow the crew to determine the condition and cause of a partially separated payload shroud. Other mitigations are really alternate missions; example, an engine out on during ascent resulted in insufficient propellant for the lunar mission, but the on-orbit vehicle stack is otherwise perfect and can pursue an alternate mission, such as a high ballistic trajectory to test the high-speed atmospheric reentry of Orion. Evaluation and presentation of contingency operations at this early stage of the development of the Ares V rocket will improve the design of the vehicle and lay the groundwork for the exhaustive contingency planning which must be done after the vehicle is built as preparations for operations.

Jaap, John↗
NASA NTRS2014

Mini-Membrane Evaporator for Contingency Spacesuit Cooling

The next-generation Advanced Extravehicular Mobility Unit (AEMU) Portable Life Support System (PLSS) is integrating a number of new technologies to improve reliability and functionality. One of these improvements is the development of the Auxiliary Cooling Loop (ACL) for contingency crewmember cooling. The ACL is a completely redundant, independent cooling system that consists of a small evaporative cooler--the Mini Membrane Evaporator (Mini-ME), independent pump, independent feedwater assembly and independent Liquid Cooling Garment (LCG). The Mini-ME utilizes the same hollow fiber technology featured in the full-sized AEMU PLSS cooling device, the Spacesuit Water Membrane Evaporator (SWME), but Mini-ME occupies only 25% of the volume of SWME, thereby providing only the necessary crewmember cooling in a contingency situation. The ACL provides a number of benefits when compared with the current EMU PLSS contingency cooling technology, which relies upon a Secondary Oxygen Vessel; contingency crewmember cooling can be provided for a longer period of time, more contingency situations can be accounted for, no reliance on a Secondary Oxygen Vessel (SOV) for contingency cooling--thereby allowing a reduction in SOV size and pressure, and the ACL can be recharged-allowing the AEMU PLSS to be reused, even after a contingency event. The first iteration of Mini-ME was developed and tested in-house. Mini-ME is currently packaged in AEMU PLSS 2.0, where it is being tested in environments and situations that are representative of potential future Extravehicular Activities (EVA's). The second iteration of Mini-ME, known as Mini- ME2, is currently being developed to offer more heat rejection capability. The development of this contingency evaporative cooling system will contribute to a more robust and comprehensive AEMU PLSS.

Makinen, Janice V.↗
NASA NTRS2015

Mini-Membrane Evaporator for Contingency Spacesuit Cooling

The next-generation Advanced Extravehicular Mobility Unit (AEMU) Portable Life Support System (PLSS) is integrating a number of new technologies to improve reliability and functionality. One of these improvements is the development of the Auxiliary Cooling Loop (ACL) for contingency crewmember cooling. The ACL is a completely redundant, independent cooling system that consists of a small evaporative cooler--the Mini Membrane Evaporator (Mini-ME), independent pump, independent feedwater assembly and independent Liquid Cooling Garment (LCG). The Mini-ME utilizes the same hollow fiber technology featured in the full-sized AEMU PLSS cooling device, the Spacesuit Water Membrane Evaporator (SWME), but Mini-ME occupies only approximately 25% of the volume of SWME, thereby providing only the necessary crewmember cooling in a contingency situation. The ACL provides a number of benefits when compared with the current EMU PLSS contingency cooling technology, which relies upon a Secondary Oxygen Vessel; contingency crewmember cooling can be provided for a longer period of time, more contingency situations can be accounted for, no reliance on a Secondary Oxygen Vessel (SOV) for contingency cooling--thereby allowing a reduction in SOV size and pressure, and the ACL can be recharged-allowing the AEMU PLSS to be reused, even after a contingency event. The first iteration of Mini-ME was developed and tested in-house. Mini-ME is currently packaged in AEMU PLSS 2.0, where it is being tested in environments and situations that are representative of potential future Extravehicular Activities (EVA's). The second iteration of Mini-ME, known as Mini-ME2, is currently being developed to offer more heat rejection capability. The development of this contingency evaporative cooling system will contribute to a more robust and comprehensive AEMU PLSS.

Makinen, Janice V.↗
NASA NTRS2013

NextGen Flight Deck Surface Trajectory-Based Operations (STBO): Contingency Holds

The purpose of this pilot-in-the-loop taxi simulation was to investigate a NextGen Surface Trajectory-Based Operations (STBO) concept called "contingency holds." The contingency-hold concept parses a taxi route into segments, allowing an air traffic control (ATC) surface traffic management (STM) system to hold an aircraft when necessary for safety. Under nominal conditions, if the intersection or active runway crossing is clear, the hold is removed, allowing the aircraft to continue taxiing without slowing, thus improving taxi efficiency, while minimizing the excessive brake use, fuel burn, and emissions associated with stop-and-go taxi. However, when a potential traffic conflict exists, the hold remains in place as a fail-safe mechanism. In this departure operations simulation, the taxi clearance included a required time of arrival (RTA) to a specified intersection. The flight deck was equipped with speed-guidance avionics to aid the pilot in safely meeting the RTA. On two trials, the contingency hold was not released, and pilots were required to stop. On two trials the contingency hold was released 15 sec prior to the RTA, and on two trials the contingency hold was released 30 sec prior to the RTA. When the hold remained in place, all pilots complied with the hold. Results also showed that when the hold was released at 15-sec or 30-sec prior to the RTA, the 30-sec release allowed pilots to maintain nominal taxi speed, thus supporting continuous traffic flow; whereas, the 15-sec release did not. The contingency-hold concept, with at least a 30-sec release, allows pilots to improve taxiing efficiency by reducing braking, slowing, and stopping, but still maintains safety in that no pilots "busted" the clearance holds. Overall, the evidence suggests that the contingency-hold concept is a viable concept for optimizing efficiency while maintaining safety.

NextGen↗
NASA NTRS1988

Contingency rescheduling of spacecraft operations

Spacecraft activity scheduling was a focus of attention in artificial intelligence recently. Several scheduling systems were devised which more-or-less successfully address various aspects of the activity scheduling problem, though most of these are not yet mature, with the notable expection of NASA's ESP. Few current scheduling systems, however, make any attempt to deal fully with the problem of modifying a schedule in near-real-time in the event of contingencies which may arise during schedule execution. These contingencies can include resources becoming unavailable unpredictably, a change in spacecraft conditions or environment, or the need to perform an activity not scheduled. In these cases it becomes necessary to repair an existing schedule, disrupting ongoing operations as little as possible. Normal scheduling is just a part of that which must be accomplished during contingency rescheduling. A prototype system named MAESTRO was developed for spacecraft activity scheduling. MAESTRO is briefly described with a focus on recent work in the area of real-time contingency handling. Included is a discussion of some of the complexities of the scheduling problem and how they affect contingency rescheduling, such as temporal constraints between activities, activities which may be interrupted and continued in any of several ways, and different ways to choose a resource complement which will allow continuation of an activity. Various heuristics used in MAESTRO for contingency rescheduling is discussed, as are operational concerns such as interaction of the scheduler with spacecraft subsystems controllers.

Britt, Daniel L.↗
NASA NTRS2005

The Earth Science Afternoon Constellation Contingency Procedures

The Earth Science Afternoon Constellation comprises NASA missions Aqua, Aura, CloudSat and the Orbiting Carbon Observatory (OCO), the joint NASA/CNES mission CALIPSO and the CNES mission PARASOL. Both NASA and CNES offices are responsible for ensuring that contingency plans or other arrangements exist to cope with contingencies within their respective jurisdictions until the conclusion of all Afternoon Constellation operations. The Mission Operations Working Group, comprised of members from each of the missions, has developed the high-level procedures for maintaining the safety of this constellation. Each contingency situation requires detailed analyses before any decisions are made. This paper describes these procedures, and includes defining what constitutes a contingency situation, the pertinent parameters involved in the contingency analysis and guidelines for the actions required, based on the results of the contingency analyses.

Case, Warren F.↗
NASA NTRS2019

Renewable Energy Contingencies in Power Systems: Concept and Case Study

This paper introduces the concept of renewable energy contingencies that represent long-term/extended variability of variable renewable energy (VRE) resources, namely, significant periods (e.g., days/weeks) of low wind/solar availability. These contingencies have not received much attention to date but are likely to emerge as a major issue in some countries such as India as the share of VRE increases. Using 38 years of climate model reanalysis data for wind over India, we demonstrate that low periods of wind contingency below long-term (Indian) national average of 5 m/s can extend for more than 100 days in several zones some of which are deploying large wind farms. Even in some of the best wind resource areas in India with long term average wind speed close to 7 m/s, low wind days (e.g., 5 m/s which is substantially below average) can extend up to 60 days. We propose a four-step methodology around a co-optimization based energy-ancillary services dispatch model to assess the impact of renewable contingency and implemented it for the state of Tamil Nadu, the most wind-rich state of India. We have estimated that annual renewable contingency cost impact of 5 GW additional wind in Tamil Nadu to be in the range of US$27-76 million pa. Planning analysis should embrace the concept of renewable contingency to recognize these costs and put in place necessary spinning reserve and back-up generation resources.

Mohar Chattopadhyay↗
NASA NTRS2005

Identifying Contingency Requirements using Obstacle Analysis on an Unpiloted Aerial Vehicle

This paper describes experience using Obstacle Analysis to identify contingency requirements on an unpiloted aerial vehicle. A contingency is an operational anomaly, and may or may not involve component failure. The challenges to this effort were: ( I ) rapid evolution of the system while operational, (2) incremental autonomy as capabilities were transferred from ground control to software control and (3) the eventual safety-criticality of such systems as they begin to fly over populated areas. The results reported here are preliminary but show that Obstacle Analysis helped (1) identify new contingencies that appeared as autonomy increased; (2) identify new alternatives for handling both previously known and new contingencies; and (3) investigate the continued validity of existing software requirements for contingency handling. Since many mobile, intelligent systems are built using a development process that poses the same challenges, the results appear to have applicability to other similar systems.

fault protection↗
NASA NTRS2005

Contingency Operations Support to NASA Johnson Space Center Medical Operations Division

The Wyle Laboratories Contingency Operations Group provides support to the NASA Johnson Space Center (JSC) Medical Operations Division in the event of a space flight vehicle accident or JSC mishap. Support includes development of Emergency Medical System (EMS) requirements, procedures, training briefings and real-time support of mishap investigations. The Contingency Operations Group is compliant with NASA documentation that provides guidance in these areas and maintains contact with the United States Department of Defense (DOD) to remain current on military plans to support NASA. The contingency group also participates in Space Operations Medical Support Training Courses (SOMSTC) and represents the NASA JSC Medical Operations Division at contingency exercises conducted worldwide by the DOD or NASA. The events of September 11, 2001 have changed how this country prepares and protects itself from possible terrorist attacks on high-profile targets. As a result, JSC is now considered a high-profile target and thus, must prepare for and develop a response to a Weapons of Mass Destruction (WMD) incident. The Wyle Laboratories Contingency Operations Group supports this plan, specifically the medical response, by providing expertise and manpower.

Stepaniak, Philip↗
NASA NTRS2005

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

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

Prabhu, Dinesh K.↗
NASA NTRS2006

Contingency Software in Autonomous Systems

This viewgraph presentation reviews the development of contingency software for autonomous systems. Autonomous vehicles currently have a limited capacity to diagnose and mitigate failures. There is a need to be able to handle a broader range of contingencies. The goals of the project are: 1. Speed up diagnosis and mitigation of anomalous situations.2.Automatically handle contingencies, not just failures.3.Enable projects to select a degree of autonomy consistent with their needs and to incrementally introduce more autonomy.4.Augment on-board fault protection with verified contingency scripts

autonomous systems↗
NASA NTRS2018

Contingency Management with Human Autonomy Teaming

Automation is playing an increasingly important role in many operations. It is often cheaper faster and more precise than human operators. However, automation is not perfect. There are many situations in which a human operator must step in. We refer to these instances as contingencies and the act of stepping in contingency management. Here we propose coupling Human Autonomy Teaming (HAT) with contingency management. We describe two aspects to HAT, bi-directional communication, and working agreements (or plays). Bi-directional communication like Crew Resource Management in traditional aviation, allows all parties to contribute to a decision. Working agreements specify roles and responsibilities. Importantly working agreements allow for the possibility of roles and responsibilities changing depending on environmental factors (e.g., situations the automation was not designed for, workload, risk, or trust). This allows for the automation to "automatically" become more autonomous as it becomes more trusted and/or it is updated to deal with a more complete set of possible situations. We present a concrete example using a prototype contingency management station one might find in a future airline operations center. Automation proposes reroutes for aircraft that encounter bad weather or are forced to divert for environmental or systems reasons. If specific conditions are met, these recommendations may be autonomously datalinked to the affected aircraft.

dispatch↗
NASA NTRS2002

Contingency Planning for Planetary Rovers

There has been considerable work in AI on planning under uncertainty. But this work generally assumes an extremely simple model of action that does not consider continuous time and resources. These assumptions are not reasonable for a Mars rover, which must cope with uncertainty about the duration of tasks, the power required, the data storage necessary, along with its position and orientation. In this paper, we outline an approach to generating contingency plans when the sources of uncertainty involve continuous quantities such as time and resources. The approach involves first constructing a "seed" plan, and then incrementally adding contingent branches to this plan in order to improve utility. The challenge is to figure out the best places to insert contingency branches. This requires an estimate of how much utility could be gained by building a contingent branch at any given place in the seed plan. Computing this utility exactly is intractable, but we outline an approximation method that back propagates utility distributions through a graph structure similar to that of a plan graph.

Dearden, Richard↗
NASA NTRS2002

Contingency Planning for the Microwave Anisotropy Probe Mission

The Microwave Anisotropy Probe (MAP) utilized a phasing loop/lunar encounter strategy to achieve a small amplitude Lissajous orbit about the Sun-Earth/Moon L2 libration point. The use of phasing loops was key in minimizing MAP's overall deltaV needs while also providing ample opportunities for contingency resolution. This paper will discuss the different contingencies and responses studied for MAP. These contingencies included accommodating excessive launch vehicle errors (beyond 3 sigma), splitting perigee maneuvers to achieve ground station coverage through the Deep Space Network (DSN), delaying the start of a perigee maneuver, aborting a perigee maneuver in the middle of execution, missing a perigee maneuver altogether, and missing the lunar encounter (crucial to achieving the final Lissajous orbit). It is determined that using a phasing loop approach permits many opportunities to correct for a majority of these contingencies.

Mesarch, Michael A.↗
NASA NTRS2003

Incremental Contingency Planning

There has been considerable work in AI on planning under uncertainty. However, this work generally assumes an extremely simple model of action that does not consider continuous time and resources. These assumptions are not reasonable for a Mars rover, which must cope with uncertainty about the duration of tasks, the energy required, the data storage necessary, and its current position and orientation. In this paper, we outline an approach to generating contingency plans when the sources of uncertainty involve continuous quantities such as time and resources. The approach involves first constructing a "seed" plan, and then incrementally adding contingent branches to this plan in order to improve utility. The challenge is to figure out the best places to insert contingency branches. This requires an estimate of how much utility could be gained by building a contingent branch at any given place in the seed plan. Computing this utility exactly is intractable, but we outline an approximation method that back propagates utility distributions through a graph structure similar to that of a plan graph.

Dearden, Richard↗
NASA NTRS2005

Orbiter Repair Maneuver Contingency Separation Methods and Analysis

Repairing damaged thermal protection system tile requires the Space Shuttle to be oriented such that repair platform access from the International Space Station (ISS) is possible. To do this, the Space Shuttle uses the Orbiter Repair Maneuver (ORM), which utilizes the Shuttle Remote Manipulator System (SRMS) to rotate the Space Shuttle in relation to the ISS, for extended periods of time. These positions cause difficulties and challenges to performing a safe separation (no collision or thruster plume damage to sensitive ISS structures) should an inadvertent release occur or a contingency procedure require it. To help protect for an SRMS failure or other failures, a method for separating without collision and the ability to redock to ISS from the ORM configuration was needed. The contingency ORM separation solution elegantly takes advantage of orbital mechanics between ISS and the separating Space Shuttle. By pitching the ISS down approximately 45 degrees, in a majority of the ORM repair positions, the altitude difference between the ISS and Space Shuttle center of gravity is maximized. This altitude difference results in different orbital energies (orbital periods) causing objects to separate from each other without requiring translational firings. Using this method, a safe contingency ORM separation is made possible in many odd positions even though some separation positions point high powered thrusters directly at fragile ISS and Soyuz solar arrays. Documented in this paper are the development simulations and procedures of the contingency ORM separation and the challenges encountered with large constraints to work around. Lastly, a method of returning to redock with the ISS to pick up the stranded crew members (or transfer the final crew members) is explained as well as the thruster and ISS loads analysis.

Machula, Michael↗