Search NASA⌕ Search

SEARCH · Search NASA

Results for “Contingency planning”

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 325 records · Page 18

Descent guidance and mission planning for space shuttle

The Space Shuttle descent mission planning, mission design, deorbit targeting, and entry guidance have necessarily become interrelated because of the nature of the Orbiter's design and mission requirements. The desired descent trajectory has been formulated in a drag acceleration/relative velocity state space since nearly all of the vehicle's highly constraining flight limitations can be uniquely represented in this plane. Constraints and flight requirements that affect the descent are described. The guidance logic which allows the Orbiter to follow the designed trajectory, the impacts of contingency aborts and flightcrew interaction are discussed. The mission planning and guidance techniques remain essentially unchanged through the Shuttle flight test program and subsequent operational flights.

Joosten, B. K.↗

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

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

Dynamic Contingency Analysis Tool 2.0 User Manual with Test System Examples

This document introduces Version 2 of the Dynamic Contingency Analysis Tool (DCAT) software package developed by Pacific Northwest National Laboratory and serves as a guide for using this package to conduct cascading failure simulations for the electric power system. The DCAT is an open-platform and publicly available software; it is intended to help develop applications that aim to improve the capabilities of power system planning engineers to assess the impact and likelihood of extreme contingencies and potential cascading events across their systems and interconnections. Outputs from the DCAT will support finding mitigating actions to reduce the risk of cascading outages in technically sound and effective ways. This manual provides detailed instructions on how to use this tool on multicore Windows workstations or servers. In the public version of DCAT, several improvements have been made over the previous version: (1) it was modularized; (2) a graphical user interface (GUI) was developed; (3) a new version of the MPjobs parallel processing module was incorporated; and (4) a batch-processing function was added. The features of the DCAT GUI are described, including some examples of how to use the GUI to perform simulations. A full explanation of the DCAT methodology is available in the Phase 1 report.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Study of space shuttle EVA/IVA support requirements. Volume 2: EVA/IVA tasks, guidelines, and constraints definition

The guidelines for EVA and IVA tasks to be performed on the space shuttle are defined. In deriving tasks, guidelines, and constraints, payloads were first identified from the mission model. Payload requirements, together with man and manipulator capabilities, vehicle characteristics and operation, and safety considerations led to a definition of candidate tasks. Guidelines and constraints were also established from these considerations. Scenarios were established, and screening criteria, such as commonality of EVA and IVA activities, were applied to derive representative planned and unplanned tasks. The whole spectrum of credible contingency situations with a potential requirement for EVA/IVA was analyzed.

Webbon, B. W.↗

Emergency medical operations at Kennedy Space Center in support of space shuttle

The unique environment of the Kennedy Space Center includes a wide variety of industrial processes culminating in launch and spaceflight. Many are potentially hazardous to the work force and the astronauts. Technology, planning, training, and quality control are utilized to prevent contingencies and expedite response should a contingency occur.

Myers, K. J.↗

STS-63 Space Shuttle report

The STS-63 Space Shuttle Program Mission Report summarizes the Payload activities and provides detailed data on the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Reusable Solid Rocket Motor (RSRM), and the Space Shuttle Main Engine (SSME) systems performance during this sixty-seventh flight of the Space Shuttle Program, the forty-second since the return to flight, and twentieth flight of the Orbiter vehicle Discovery (OV-103). In addition to the OV-103 Orbiter vehicle, the flight vehicle consisted of an ET that was designated ET-68; three SSME's that were designated 2035, 2109, and 2029 in positions 1, 2, and 3, respectively; and two SRB's that were designated BI-070. The RSRM's that were an integral part of the SRB's were designated 360Q042A for the left SRB and 360L042B for the right SRB. The STS-63 mission was planned as an 8-day duration mission with two contingency days available for weather avoidance or Orbiter contingency operations. The primary objectives of the STS-63 mission were to perform the Mir rendezvous operations, accomplish the Spacehab-3 experiments, and deploy and retrieve the Shuttle Pointed Autonomous Research Tool for Astronomy-204 (SPARTAN-204) payload. The secondary objectives were to perform the Cryogenic Systems Experiment (CSE)/Shuttle Glo-2 Experiment (GLO-2) Payload (CGP)/Orbital Debris Radar Calibration Spheres (ODERACS-2) (CGP/ODERACS-2) payload objectives, the Solid Surface Combustion Experiment (SSCE), and the Air Force Maui Optical Site Calibration Tests (AMOS). The objectives of the Mir rendezvous/flyby were to verify flight techniques, communication and navigation-aid sensor interfaces, and engineering analyses associated with Shuttle/Mir proximity operations in preparation for the STS-71 docking mission.

Fricke, Robert W., Jr.↗

Emergency Medical Operations at Kennedy Space Center in Support of Space Shuttle

The unique environment of the Kennedy Space Center includes a wide variety of industrial processes culminating in launch and spaceflight. Many are potentially hazardous to the work force and the astronauts. Technology, planning, training, and quality control are utilized to prevent contingencies and expedite response should a contingency occur.

Myers, K. Jeffrey↗

Results of the International Space Station Interim Resistance Exercise Device Man-in-the-Loop Test

The Interim Resistance Exercise Device (iRED), developed for the International Space Station (ISS), was evaluated using human subjects for a Man-In-The-Loop Test (MILT). Thirty-two human subjects exercised using the iRED in a test that was conducted over a 63-working-day period. The subjects performed the same exercises will be used on board ISS, and the iRED operating constraints that are to be used on ISS were followed. In addition, eight of the subjects were astronauts who volunteered to be in the evaluation in order to become familiar with the iRED and provide a critique of the device. The MILT was scheduled to last for 57,000 exercise repetitions on the iRED. This number of repetitions was agreed to as a number typical of that expected during a 3-person, 17-week ISS Increment. One of the canisters of the iRED failed at the 49,683- repetition mark (87.1% of targeted goal). The remaining canister was operated using the plan for operations if one canister fails during flight (contingency operations). This canister remained functional past the 57,000-repetition mark. This report details the results of the iRED MILT, and lists specific recommendations regarding both operation of the iRED and future resistance exercise device development.

Moore, A. D., Jr.↗

Unmanned Aerial Systems Traffic Management (UTM): Safely Enabling UAS Operations in Low-Altitude Airspace

Currently, there is no established infrastructure to enable and safely manage the widespread use of low-altitude airspace and UAS flight operations. Given this, and understanding that the FAA faces a mandate to modernize the present air traffic management system through computer automation and significantly reduce the number of air traffic controllers by FY 2020, the FAA maintains that a comprehensive, yet fully automated UAS traffic management (UTM) system for low-altitude airspace is needed. The concept of UTM is to begin by leveraging concepts from the system of roads, lanes, stop signs, rules and lights that govern vehicles on the ground today. Building on its legacy of work in air traffic management (ATM), NASA is working with industry to develop prototype technologies for a UAS Traffic Management (UTM) system that would evolve airspace integration procedures for enabling safe, efficient low-altitude flight operations that autonomously manage UAS operating in an approved low-altitude airspace environment. UTM is a cloud-based system that will autonomously manage all traffic at low altitudes to include UASs being operated beyond visual line of sight of an operator. UTM would thus enable safe and efficient flight operations by providing fully integrated traffic management services such as airspace design, corridors, dynamic geofencing, severe weather and wind avoidance, congestion management, terrain avoidance, route planning re-routing, separation management, sequencing spacing, and contingency management. UTM removes the need for human operators to continuously monitor aircraft operating in approved areas. NASA envisions concepts for two types of UTM systems. The first would be a small portable system, which could be moved between geographical areas in support of operations such as precision agriculture and public safety. The second would be a Persistent system, which would support low-altitude operations in an approved area by providing continuous automated coverage. Both would require persistent communication, navigation, and surveillance (CNS) coverage to track, ensure, and monitor conformance. UTM is creating an airspace management tool that allows the ATM system to accommodate the number of UAS that will operate in the low altitude airspace. The analogy is just because we have a car, whether its autonomous or someone is driving, does not diminish the need for a road or road signs or rules of the road.

traffic management↗

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

Tenets of Lunar EVAs for Artemis III

The purpose of these top level EVA tenets for Artemis III is to capture and promote EVA planning principles which drive decisions before and during the mission that are related to mission timeline, contingencies, and how risks are balanced. The tenets listed below are not shown in a priority order. (Reference Artemis III Mission Planning Summit, Action 27, 3/9/2023).

EVA↗

Integration of On-board EOS Schedule Revision with Space Communication Emulation System

The need for on-board decision-making for planning science observations on Earth Observing Satellites is based on the fact that the desirability of acquiring an image can change dynamically, because of changes in meteorological conditions (e.g. cloud cover), unforeseen events such as fires, floods, or volcanic eruptions, or unexpected changes in satellite or ground station capability. In such cases, satellite resources, such as power and SSR capacity can potentially be better utilized taking another image that is of higher quality. Currently, typical Earth observing satellites cannot communicate directly with each other, and can only communicate with ground stations about 5% to 10% of the time. Because of the limited communication windows, as well as the cost and effort that would need to be expended in revising a mission schedule, a ground-based scheduler would have little or no opportunity to revise the schedule in response to the contingencies that may arise. For this reason, a distributed science planning system combining a ground-based scheduler with on-board schedule revision capabilities is warranted. This paper will describe algorithms for on-board decision-making for science planning and their integration with the advanced satellite control and communications technology developed at the Space Communication Emulation Facility (SCEF) at NASA Glenn Research Center. Our objective of demonstrating how advanced communications and scheduling technology can be combined to improve the scientific utility of images acquired by Earth observing systems will be discussed via a description of a number of realistic flight scenarios.

Khatib, Lina↗

Collective Intelligence and Three Aspects of Planning in Organizations: A NASA Example

For many complex sociotechnical systems, planning seems to require explicit coordination; certainly, in executing a plan the activities of different actors must be tightly coupled. However, distributing the needed planning information can be very burdensome and error prone, because different groups need different collections of information, updated or kept current on different time cycles. Further, the information needed to form successful plans is often highly distributed, and while feedback about the success of prior plans may exist, it may not be available to those in a position of using this to improve plans or to detect and resolve other problems in the system (Weick, 1995). Tools to support various aspects of planning have been developed, and can provide a huge benefit to the individuals working on that aspect. To be tractable, most solutions address a quite bounded slice of work, isolating it from the larger context. Prospective planning takes place over multiple, nested cycles of decision making. This builds a plan that specifies activities of different granularity. "Subplans" may specify multiple parallel activities by different groups and individuals, as well as sequential, nested actions by a single actor. Planning produces valuable, sharable, external, representations: in addition to prospective use, plans support retrospective assessment and also action in the present. Viewing planning in a larger context - both temporal and organizational -- enables noticing what one does not know and generating more systemic and effective solutions. Viewing a problem as one of collective intelligence invites thinking about the larger organizational context. Many approaches to supporting collective intelligence do not support execution of highly contingent actions, distributed across many players, and hence provide incomplete support for planning. However, CI technology maybe helpful in managing the processes of gathering information for decision making in planning and of distributing plan information to various actors, needed on various time cycles.

Billman, Dorrit↗

Space Shuttle/Orbiter EVA and EVA provisions

EVA objectives, procedures, and equipment for the Shuttle are reviewed. The EVA will occur as a planned excursion, to complete a mission objective, or on a contingency basis as support for the mission or to effect repairs to the Orbiter or its payload. Configurations for the placement of the airlock for EVA with and without Spacelab payloads are discussed, along with the various EVA tasks which could be expected as necessary for mission completion. Handholds have been placed in strategic positions on the RMS and along the payload doors, and a safety tether has been incorporated with line extension out to 25 ft. Off-the-shelf tools such as needlenose pliers, forceps, diagonal cutters, etc. are carried as standard equipment for the repair of malfunctioning equipment and doorlatches. Finally, attention is given to EVA lighting, communication, life-support, and work station restraint systems.

Goodman, J. R.↗

An Approach to Reasoning Service Migration in Data and Reasoning Fabric (DRF) Implementation

In this paper we consider service placement problem for Data and Reasoning Fabric (DRF) enabled airspace operations assuming a fixed cloud/edge infrastructure with allocated computing, storage and power resources, where cloud/edge servers, and communication stations are in a wired connected network, while vehicles use a wireless network for communication. The objective is to automatically select the best location for the requested service execution, which achieves minimum cost while satisfying the user quality of service (QoS) and available resources constraints. To this end, we estimate for each potential location the response time, consumed energy and total cost; formulate an optimization problem for cost minimization given the users QoS constraints and network infrastructure limitations; and solve it using nonlinear programming tools. The approach is applied to trajectory re-planning use case to handle a no-fly zone contingency in real time.

Vahram Stepanyan↗

Rapid Contingency Simulation Modeling of the NASA Crew Launch Vehicle

The NASA Crew Launch Vehicle is a two-stage orbital launcher designed to meet NASA's current as well as future needs for human space flight. In order to free the designers to explore more possibilities during the design phase, a need exists for the ability to quickly perform simulation on both the baseline vehicle as well as the vehicle after proposed changes due to mission planning, vehicle configuration and avionics changes, proposed new guidance and control algorithms, and any other contingencies the designers may wish to consider. Further, after the vehicle is designed and built, the need will remain for such analysis in the event of future mission planning. An easily reconfigurable, modular, nonlinear six-degree-of-freedom simulation matching NASA Marshall's in-house high-fidelity simulator is created with the ability to quickly perform simulation and analysis of the Crew Launch Vehicle throughout the entire launch profile. Simulation results are presented and discussed, and an example comparison fly-off between two candidate controllers is presented.

Betts, Kevin M.↗

Simulating Impacts of Extreme Events on Grids with High Penetrations of Wind Power Resources

As extreme weather events become more frequent and intense, the demand for connecting grid operation and infrastructure planning with extreme event models will increase as well. We present a methodology for creating damage contingencies and scenarios for electric transmission grids during a hurricane strike. Using WIND Toolkit meteorological data in conjunction with fragility curves for various electric grid elements, we generate stochastic damage scenarios that can be used for short- and long-term planning problems, e.g., emergency asset management. Included is an example case study: Hurricane Dolly damaging a synthetic 2000-bus test system during its landing in Southern Texas. We perform statistical analysis of damages and discuss topological effects on the example synthetic grid. Also, we include a cursory evaluation of impacts using simplified operational models. Finally, we discuss how our method can be extended to use even higher-fidelity meteorological data sets and suggest directions for future work.

contingencies↗