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 1,495 records · Page 83

Artificial Gravity in Mars Orbit for Crew Acclimation

NASA’s current baseline plan for a crewed Mars mission anticipates a transit time of up to three hundred days in microgravity and 3-14 days on the Martian surface for gravity acclimation before the crew can safely perform their first Extra-Vehicular Activity (EVA). While there are multiple options for how initial surface operations will be performed, all current designs involve acclimation on the surface, and the impacts on the mission schedule, required supplies, and crew lander systems are significant. This paper proposes an alternative option utilizing artificial gravity, which offers benefits in terms of mission scope, mass savings, crew health, and long-term strategic vision. By moving the acclimation requirement to the orbiting habitat’s existing systems, rather than adding redundant systems to the lander, the Mars Descent Vehicle (MDV) can be a much smaller, simpler, and lighter design. Rather than the lander being designed to support crew for days, it would be mere hours. While ambitious, the concept of pre-acclimation in orbit can be not only safe and feasible, but done with fairly minimal changes to the planned architecture and overall mass requirements. The data used draws on decades of established research and demonstrates how this capability can be not only used for pre-acclimation, but also to support crew during early orbital-only missions, surface abort contingency scenarios, return-to-orbit abort scenarios, and as an early proof of capability into larger and more ambitious artificial gravity designs needed for extended exploration missions in the future.

Rowe, Justin↗

Testing Enabling Technologies for Safe UAS Urban Operations

A set of more than 100 flight operations were conducted at NASA Langley Research Center using small UAS (sUAS) to demonstrate, test, and evaluate a set of technologies and an overarching air-ground system concept aimed at enabling safety. The research vehicle was tracked continuously during nominal traversal of planned flight paths while autonomously operating over moderately populated land. For selected flights, off-nominal risks were introduced, including vehicle-to-vehicle (V2V) encounters. Three contingency maneuvers were demonstrated that provide safe responses. These maneuvers made use of an integrated air/ground platform and two on-board autonomous capabilities. Flight data was monitored and recorded with multiple ground systems and was forwarded in real time to a UAS traffic management (UTM) server for airspace coordination and supervision.

Moore, Andrew J.↗

Human Systems Integration Relationships Between Deep Space and Deepwater Exploration Challenges

NASA pursuit of human missions Beyond Earth Orbit (BEO) to the moon and eventually Mars will pose many new challenges. These missions are characterized by increased risks to human performance due to stress, fatigue, radiation exposure, and isolation. Fundamental changes in spaceflight operations will be required as well. A very critical part of future missions will be assisting the crew with problem-solving and contingency resolution using next-generation smart spacecraft systems. Human Systems Integration (HSI) must be included as part of the systems engineering process. Gateway1 will serve as part of the proving ground for maturing technology such as autonomous systems and space operations procedures to help meet moon mission goals and prepare humans for missions to Mars. For deep space missions, risk factors affecting humans such as mission duration, distance, and physiological/psychological effects, must be considered. A human is not a simple component but rather a system in a systems-of-systems application-a system influenced by cognitive and biological factors that are difficult to model/analyze. System complexity will demand an integrated approach that requires multiple viewpoints, including the understanding of the astronauts' capabilities and limitations to enhance safety, performance, and satisfaction on the interaction between all system users in a variety of environments to achieve acceptable mission goals and performance. HSI will play a vital role in the development of these future missions. This paper provides a discussion of HSI used at NASA and the critical role human factors engineering will play in the HSI process for future missions along with the challenges. Industries such as oil and gas (O&G) could benefit from the content of this paper to help improve the safety and operations of deepwater/oil and gas exploration activities. NASA engineering and human systems subject-matter expert personnel reviewed challenges reported in space-related environments for long space duration missions and identified similarities with the challenges encountered in deepwater exploration. The researchers noted the space industry's current solutions and proposed a system development view to solve future deepwater exploration challenges using HSI principles. This paper discusses the results of the review.

George Salazar↗

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

Demonstration of Two Extended Visual Line of Sight Methods for Urban UAV Operations

This report describes two extended visual line of sight (EVLOS) methods developed and utilized during two flight campaigns over the campus of NASA Langley Research Center (LaRC): a chase vehicle method and a radio controlled (RC) pilot handoff method. These campaigns were performed to (a) evaluate small unmanned aerial system (sUAS) flight beyond the visual line of sight (BVLOS) of the ground control station operator and (b) test technologies under development to enable a transition from EVLOS to BVLOS operations. While an autonomous waypoint-based operational approach enabled minimal pilot intervention in both methods, range containment was enforced (a) manually via continual pilot visual monitoring and (b) autonomously via on-board contingency landing autonomy triggerable at the boundary of stay-in geofences. In the thirty-nine flights which utilized the chase vehicle, the pilot followed the sUAS flying a 1.2 km path at 40m altitude over urban streets. In the fifteen flights which utilized pilot handoff, a pilot at one end of a 1.5 km path initiated the flight at 120m altitude over buildings and trees, and at the midway point of the path transferred radio control to a pilot at the other end. In comparison, the chase vehicle method requires less ground crew and simpler avionics, while the pilot handoff method avoids schedule risk arising from street traffic congestion but better replicates actual direct routing for BVLOS flights. Collision risk with another aircraft was introduced in both campaigns and mitigated with the same manual and autonomous methods. Results from these campaigns serve as a basis for planned BVLOS operations at NASA LaRC.

Nicholas Rymer↗

Risk Assessment of Obstacle Collision for UAVs under off-nominal conditions

Enabling operations of unmanned aerial vehicles (UAVs) in low-altitude airspace, demands the need of robust risk monitoring framework for assessing the safety of airspace, ground-structures and people. As widespread applications emerge, the need of risk assessment becomes increasingly important for UAV flights beyond visual line-of-sight, especially subjected to off-nominal conditions introduced by component failures, degraded controllability or environmental disturbances such as wind gusts in an urban canyon. From a safety perspective, collision with obstacles can be detrimental not only to the vehicle and payload, but also to the structure and people on ground. Although it is safe to assume that approved UAVs would be equipped with collision avoidance systems, risk of collision which can be predicted for a flight trajectory even before the UAV encounters any obstacle is beneficial to resolve contingencies in its decision-making under off-nominal conditions. In this paper, a framework is presented for computing the risk of collision with obstacle based on a UAV's predicted trajectory, proximity to static and dynamic obstacles, sub-system state-of-health and external wind conditions. The conditional probability of trajectory deviation is generated using a Bayesian Belief Network (BBN) based on on-board sensor measurements. Further, a kinematic 3-DOF model is implemented to compute deviation in UAV's trajectory subjected to one case study of off-nominal condition i.e. wind gusts. Finally, the integrated risk factor is demonstrated on real data from experimental flights of an octocopter at NASA Langley Research Center, in presence of simulated obstacles and wind conditions. The proposed approach would enable risk-informed decision making process for timely mitigation of current and future unsafe events.

Portia Banerjee↗

Flight Demonstration of Unmanned Aircraft System (UAS) Traffic Management (UTM) at Technical Capability Level 4

The NASA Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Project executed the fourth and final UTM Technical Capability Level demonstration between May and August 2019. Two Federal Aviation Administration (FAA)-designated UAS test sites managed the range, partners, and operations to meet the requirements set forth by the UTM Project. All stakeholders supported the execution of the flight testing through close collaboration. Results of the demonstration indicate the viability of the UTM concept to manage large scale operations and contingencies in an urban environment. The demonstration also provided insight into key technological gaps that must be addressed before such operations are routine, safe, and efficient. Standardization efforts related to UTM and the industry participants of those efforts can leverage the results and experiences of this flight activity to accelerate and more firmly ground forthcoming standards. The FAA and other regulators will be able to leverage results to inform future rule-making and identify additional gaps that require further analysis.

Unmanned Aircraft System Traffic Management↗

Lunar Transient Accelerations White Paper

Recently, the United States announced a plan to return astronauts to the moon by 2024 [8]. Lunar landing (and subsequent Mars landing) architecture was not considered when the current NASA standards and vehicle design requirements for crew injury risk were developed. Therefore a gap exists in protecting the crew in planetary landing scenarios. One of the interesting aspects of this design reference mission (DRM)is the consideration of having the crew stand during dynamic phases of flight. Although this approach was contemplated for the Apollo Lunar Module, current NASA standards do not address design solutions that allow the crew to stand. Currently, NASA uses several tools and associated limits to mitigate crew injury because of dynamic loads. Some of these tools are the Brinkley Dynamic Response Criterion (BDRC) model and Hybrid III Anthropomorphic Test Devices (ATDs) [10]; and these have several limitations for assessing spaceflight loading environments, as well as specific underlying assumptions that may not be applicable in planetary landing vehicles. The BDRC is a simple lumped mass parameter model developed by the U.S. military, and has been used primarily to evaluate injury risk associated with aircraft ejection systems. The model evaluates seat accelerations in each axis to determine injury risk. Because the model treats the human-seat-restraint system as a single system, it is contingent on a restraint system and seat with similar characteristics of the original test data underlying the model. In particular, the model requires a rigid seat with a minimum natural frequency of 15Hz, minimal seat pan padding, side supports, and multipoint harness. The BDRC model uses undamped natural frequency and damping coefficients based on these requirements and any deviations may render the model injury predictions void. In lunar landing, one expects that a minimal or even no seat with minimal restraints will be employed. In this case, the original model parameters are likely to not be applicable. For capsule-based spacecraft returning crew to Earth, the Hybrid III ATD in various sizes also is used to supplement the BDRC. This analytical tool was added to address limitations in the BDRC related to spacecraft landings while wearing a pressure garment and helmet. Although the Hybrid III ATD has additional measurement capability; head, neck,and lumbar spine responses were the only metrics included because of the limitations imposed by the model.Lunar landing acceleration limits must assume the crew is standing during landing, an orientation for which we have limited data.Although the Apollo missions did employ a standing orientation for the crew, much of the data is lost. Therefore data from othersources havebeen examined to inform lunar landing acceleration limits.

Jeffrey T Somers↗

TCL4 Corpus Christi Video with Narration

This is a video for use in presenting an overview of NASA's UAS Traffic Management (UTM) Project's Technical Capability Level 4 (TCL4) flight test that was conducted in the summer of 2019 in the urban flight areas of Corpus Christi, TX. The video presents a graphical view of the specific flight areas that were used and touches upon the main objectives that were demonstrated as part of the event. A number of examples with visual representations of Unmanned Aircraft Vehicles based on collected data are presented in various situations that were constructed to target certain concept elements of UTM. Examples of situations presented are: High density operations, operations in close proximity, off-nominal events, and contingency management situations.

UAS Traffic Management↗

Artemis I Trajectory Design and Optimization

This paper presents the overall trajectory design and optimization process for NASA’s Artemis I mission to send an uncrewed Orion vehicle to a lunar Distant Retrograde Orbit (DRO). The on-orbit trajectory begins at the Space Launch System (SLS) core separation and ends at the Orion service module Earth Entry Interface (EI) point. The details of the trajectory optimization process are presented, including design of nominal and extended mission options, launch windows, and abort options. Novel design techniques are also discussed to account for contingencies, such as using auxiliary thrusters to protect against main engine failure and applying trajectory shaping to mitigate or reduce eclipse durations.

Artemis I↗

Risk Assessment of Obstacle Collision for UAVs under Off-nominal Conditions

Enabling operations of unmanned aerial vehicles (UAVs) in low-altitude airspace demands the need of robust risk monitoring framework for assessing the safety of airspace, ground structures and people. As widespread applications emerge, the need of risk assessment becomes increasingly important for UAV flights beyond visual line-of-sight, especially subjected to off-nominal conditions introduced by component failures, degraded controllability or environmental disturbances such as wind gusts in an urban canyon. From a safety perspective, collision with obstacles can be detrimental not only to the vehicle and payload, but also to the structure and people on ground. Although it is safe to assume that approved UAVs would be equipped with collision avoidance systems, risk of collision which can be predicted for a flight trajectory even before the UAV encounters any obstacle is beneficial to resolve contingencies in its decision-making under off-nominal conditions. In this paper, a framework is presented for computing the risk of collision with obstacle based on a UAV’s predicted trajectory, proximity to static and dynamic obstacles, sub-system state-of-health and external wind conditions. The conditional probability of trajectory deviation is generated using a Bayesian Belief Network (BBN) based on on-board sensor measurements. Further, a kinematic 3-DOF model is implemented to compute deviation in UAV’s trajectory subjected to one case study of off-nominal condition i.e. wind gusts. Finally, the integrated risk factor is demonstrated on real data from experimental flights of an octocopter at NASA Langley Research Center, in presence of simulated obstacles and wind conditions. The proposed approach would enable risk-informed decision making process for timely mitigation of current and future unsafe events.

Bayesian network↗

Exploration EVA System Concept of Operations

The Exploration Extravehicular Activity (xEVA) System concept of operations (con ops) captures the National Aeronautics and Space Administration’s (NASA’s) current aims future missions to all potential Exploration destinations. This document captures the mission architectures, stakeholder expectations, and high level definitions of the capabilities and interfaces associated with the xEVA System. This includes missions to Gateway in cislunar space, the lunar surface, a redirected asteroid in cislunar space, Near Earth Asteroids (NEA), Mars’ orbit, the moons of Mars (Phobos and Deimos), and the surface of Mars. These missions, which include microgravity, milli-gravity, and partial-gravity surface EVAs, will involve a variety of engineering (maintenance, contingency, pioneering, construction) and science tasks. This document also captures information concerning vehicles and habitats with which the xEVA System will interface. The concepts of operations (con ops) detailed in this document are informed by the Artemis Program and a multitude of Exploration studies, and are also influenced by various integrated operational analog testing.

David Coan↗

Best Practices Identified Through the Completion of UAS Flight Demonstrations

After several years of research into Detect and Avoid (DAA) and Command and Control (C2) systems for Unmanned Aircraft Systems (UAS), the National Aeronautics and Space Administration’s (NASA) UAS Integration into the National Airspace System project initiated a focused two-year effort along with the Federal Aviation Administration (FAA) and three industry partners to investigate remaining issues in the specification, test, certification and airspace integration to allow UAS operations in non-segregated airspace. The approach taken had the industry partners propose a flight demonstration approximating a commercial operation, while NASA helped, as needed, the partners through design and test phases and NASA observed interactions with the FAA. During this effort NASA collected best practices intended to be of value to similar UAS endeavors. These best practices can be divided into different sets, including practices that describe the relationship between business considerations to UAS design or describe several UAS development challenges. Another set includes best practices focused on navigating the UAS design and type certification processes. A third set includes best practices that relate to the design of the DAA system. Deploying DAA systems in this timeframe posed unique challenges. Commercial off-the-shelf DAA systems do not exist, necessitating custom development and, for two of the partners, the use of low-size, -weight, and -power (SWaP) sensors not completely specified for DAA. A fourth set of best practices relates to lost-link contingency planning. The final set of best practices relates to the design and testing of C2 systems and obtaining spectrum licenses. The UAS demonstrations were piloted remotely, and for all aspects of flight safety, a C2 system was required to communicate DAA and other UAS subsystem data to the remote pilot and to allow the pilot to issue commands to the vehicle. Throughout the course of this effort, the partners integrated prototype DAA and C2 systems into unmanned aircraft, tested those systems, and laid the groundwork for type certification programs that are expected to continue.

NASA↗

Short Circuiting the Controller – Missteps in Maintenance and Inspection of Process and Wiring in STS-93

The primary objective of the Space Transportation System mission 93 (STS-93) was to deploy the Chandra X-Ray Observatory. Chandra, the world's most powerful X-Ray telescope, allowed scientists from around the world to study some of the most distant and dynamic objects in the universe. Stripped of nearly 7,000 pounds of its own gear to make room for the payload, the orbiter assigned to this mission was Space Shuttle Columbia. Prior to STS-93, Columbia had flown 25 flights and was NASA's oldest and heaviest orbiter. On July 23, 1999, after two prior launch scrubs, Eileen Collins and her crew of four launched from Kennedy Space Center. About five seconds after launch, Mission Control at Johnson Space Center detected a voltage drop on one of Columbia's electrical buses. As a result of this power fluctuation, a primary and back-up Main Engine controller dropped offline. Given design redundancy, the two remaining controllers supported all three engines. If there had been any other AC bus issues, one engine of the three on the Orbiter would have shut down. The redundant set of digital computer units in each engine controller saved Columbia and her crew from a very risky contingency abort. Post-flight inspection revealed soot on a screw head and a hole in an adjacent Kapton insulated wire. The single strand of polyimide wire was located nearly half-way down the payload bay. The Shuttle Independent Assessment Team (SIAT) reported that the wire had rubbed and chaffed against a burred screw head. The burr was later determined to be the result of overtightening of the screw by a technician during a maintenance refurbishment. Alone, the burr may not have been problematic, but later, during another ground processing event, possibly years after, someone inadvertently stepped on the wiring harness. With the pressure and motion of unintended contact, some of the Kapton insulation rubbed off against the burred screw head. The SIAT suspected the wire damage was pre-existing and was caused 4 or 5 years prior to the flight. Finally, the intense vibrations during the launch sequence allowed contact between the exposed conductor and exposed metal area on the burred screw head, resulting in the arcing and shorting of the wire. Due to the quick turnaround times of Space Shuttle Orbiters, wiring issues caused from multiple maintenance events were often overlooked. Additionally, failing to incorporate thorough and early inclusion of human systems integration (HSI) applications as a crucial part of the decision process can result in these types of misshaps. In order to reduce human error associated with integrated manufacturing, maintenance, refurbishment and flight preparations, wire inspection criteria should be refined and standardized, visual inspection processes should be quantified, and technicians should be certified by specially trained instructors. This case, among many others, unveils why human error management and development of safety metrics is a vital piece in the development of complex systems, and why it should be supported aggressively and implemented program wide.

Human Systems Integration↗

Initial Jupiter Orbit Insertion and Period Reduction Maneuver Plans for Juno

This paper describes the initial plans for the New Frontiers Juno mission at Jupiter. It includes the considerable contingency planning for mission recovery if the Jupiter Orbit Insertion (JOI) burn to place Juno into a large capture orbit were interrupted or terminated on a burn timer setting, and the options for the mission if the Period Reduction Maneuver (PRM) burn to achieve the final orbit period were terminated early. The analyses were based on the assumption that 14-day orbits were the desired operational orbit period.

Bordi, John J.↗

Cassini In-Flight Navigation Adaptations

In the nearly two decades of Cassini flight, adaptations to navigation processes were applied as characteristics unique to Cassini were identified and spacecraft configuration changes were implemented. Additionally, operational experience was leveraged into more efficient processes, better modeling, and more robust contingency strategies. Trajectory adjustments were implemented to allow further investigation of surprising science discoveries meriting more attention. Unique analyses were performed to determine how to best accomplish atypical science observations while maintaining acceptable risk levels. Descriptions of the most significant adaptations are organized according to the affected navigation subsystems: trajectory design, orbit determination, optical navigation, and maneuver design.

Wagner, Sean↗

Collaborative Communications Between a Human and a Resilient Safety Support System

Successful introductory UAM integration into the NAS will be contingent on resilient safety systems that support reduced-crew flight operations. In this paper, we present a system that performs three functions: 1) monitors an operator’s physiological state; 2) assesses when the operator is experiencing anomalous states; and 3) mitigates risks by a combination of dynamic, context-based unilateral or collaborative dynamic function allocation of operational tasks. The monitoring process receives high data-rate sensor values from eye-tracking and electrocardiogram sensors. The assessment process takes these values and performs a classification that was developed using machine learning algorithms. The mitigation process invokes a collaboration protocol called DFACC to which, based on context, performs vehicle operations that the operator would otherwise routinely execute. This system has been demonstrated in a UAM flight simulator for an operator incapacitation scenario. The methods and initial results as well as relevant UAM and AAM scenarios will be described.

Advanced Air Mobility,↗