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 181 records · Page 10

An Examination of Coarse Sun Sensor Contingencies in Attitude Determination and the Sun Vector Calculation

Satellite pointing is vital to the success of a mission. One element of that entails describing the position of the sun relative to the frame of the satellite. Coarse Sun Sensors (CSS) are typically used to provide the information to calculate the sun's position in Safe Modes or contingency operations. In the OCO-2 configuration there are 13 CSS total, which provide redundant 4 celestial coverage. Failures of the individual CSS elements can introduce holes in the celestial coverage resulting in potential loss of sun knowledge. These failures must be analyzed to determine if the contingency plan is sufficient to assure mission success. First the static case was looked at and determined that at a maximum, 3 CSS failures can be sustained on the body and 1 on the array without causing coverage holes. Also array sensors are more important to mission success. The Sun Vector calculation has been transcribed to MATLAB code and failure scenarios are being examined to determine the maximum error given a set of failure scenarios. This activity indicated that if there is a loss of the sun, the sun-searching algorithm could be modified to use XZ rotation as that is guaranteed to find it whereas the design using the YZ rotation misses the sun if it is at the + or - Y orientation.

celestial bodies↗

The Preparation for and Execution of Engineering Operations for the Mars Curiosity Rover Mission

The Mars Science Laboratory Curiosity Rover mission is the most complex and scientifically packed rover that has ever been operated on the surface of Mars. The preparation leading up to the surface mission involved various tests, contingency planning and integration of plans between various teams and scientists for determining how operation of the spacecraft (s/c) would be facilitated. In addition, a focused set of initial set of health checks needed to be defined and created in order to ensure successful operation of rover subsystems before embarking on a two year science journey. This paper will define the role and responsibilities of the Engineering Operations team, the process involved in preparing the team for rover surface operations, the predefined engineering activities performed during the early portion of the mission, and the evaluation process used for initial and day to day spacecraft operational assessment.

Mars↗

Mid-L/D Lifting Body Entry Demise Analysis

The mid-lift-to-drag ratio (mid-L/D) lifting body is a fully autonomous spacecraft under design at NASA for enabling a rapid return of scientific payloads from the International Space Station (ISS). For contingency planning and risk assessment for the Earth-return trajectory, an entry demise analysis was performed to examine three potential failure scenarios: (1) nominal entry interface conditions with loss of control, (2) controlled entry at maximum flight path angle, and (3) controlled entry at minimum flight path angle. The objectives of the analysis were to predict the spacecraft breakup sequence and timeline, determine debris survival, and calculate the debris dispersion footprint. Sensitivity analysis was also performed to determine the effect of the initial pitch rate on the spacecraft stability and breakup during the entry. This report describes the mid-L/D lifting body and presents the results of the entry demise and sensitivity analyses.

Ling, Lisa↗

Cassini Ring Plane Crossings: Hypervelocity Impact Risks to Sun Sensor Assemblies

For both F/G and D-ring crossings: Probability of a penetration damage of the SSH (Sun Sensor Head) window glass is very low; Optical attenuation due to craters on the surface of the window glass caused by direct HVI (Hyper-Velocity Impact) by dust particle is estimated to be less than 1 percent; Optical attenuation due to secondary debris cloud generated by the disintegrated ring dust particles is estimated to be less than 1 percent. To better manage the Sun sensor damage risk during selected proximal orbit crossings, it is highly desirable to follow the contingency procedures mentioned in Section VII of the paper: Details of this contingency procedure are given in the paper entitled "Cassini Operational Sun Sensor Risk Management During Proximal Orbit Saturn Ring Plane Crossings" authored by David M. Bates. Based on results of risk analyses documented in this work and contingency planning work described in the paper mentioned above, we judge that the proximal orbit campaign will be safe from the viewpoint of dust HVI hazard.

dust particles↗

Mid-Course Correction Contingency Analysis for the James Webb Space Telescope

This investigation details two analyses performed as part of an early orbit contingency operations study related to the James Webb Space Telescope’s limited ability to maneuver in a sunward direction. First, contingency planning developed by the Flight Dynamics Team and shared with the Science and Operations Center to quickly assess the available timeline in the event of a delayed mid-course correction maneuver is presented. Second, the methods for recovering from a maneuver over-burn using observatory geometry to exploit the solar radiation pressure perturbation contributions from the large sunshield as well as adjusting the maneuver campaign to recover the observatory are examined.

JWST↗

How Should Life Support Be Modeled and Simulated?

Why do most space life support research groups build and investigate large models for systems simulation? The need for them seems accepted, but are we asking the right questions and solving the real problems? The modeling results leave many questions unanswered. How then should space life support be modeled and simulated? Life support system research and development uses modeling and simulation to study dynamic behavior as part of systems engineering and analysis. It is used to size material flows and buffers and plan contingent operations. A DoD sponsored study used the systems engineering approach to define a set of best practices for modeling and simulation. These best practices describe a systems engineering process of developing and validating requirements, defining and analyzing the model concept, and designing and testing the model. Other general principles for modeling and simulation are presented. Some specific additional advice includes performing a static analysis before developing a dynamic simulation, applying the mass and energy conservation laws, modeling on the appropriate system level, using simplified subsystem representations, designing the model to solve a specific problem, and testing the model on several different problems. Modeling and simulation is necessary in life support design but many problems are outside its scope.

Jones, Harry W.↗

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↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service.Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations.The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-to-station handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an in-orbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

Sample Return Container Opening Process Concept for Potential Mars Sample Return

Proposed Mars Sample Return (MSR) missions would require a pristine and secure opening method to ensure sample Contamination Control and backward Planetary Protection. In order to reach the samples, a series of five containers would need to be opened inside of a Mars Returned Sample Handling (MRSH) facility. The process would include opening the Containment Assurance Module (CAM) aboard the Earth Entry Vehicle (EEV), the Secondary Containment Vessel (SCV), Primary Containment Vessel (PCV), and the Orbiting Sample (OS) container, and finally removing and opening the Returned Sample Tube Assemblies (RSTA). Some of these containers can be opened by reversing the mechanical assembly process while others would require destructive means. Several containers are still in a conceptual design phase while others are en route to Mars aboard the M2020 rover. In order to inform the design of the containers that are still in the conceptual stages, a study was performed at each level of the containment assembly. The studies were used to determine the least destructive and most robust methods to disassemble and open the containers while minimizing risk to the samples or the personnel. In addition to the envisioned disassembly and breaching method, contingency plans were made for completing the disassembly if damage to the vehicle and containment system occurred.

Liu, Yang↗

Mars Sample Return (MSR) Sample Receiving Facility (SRF) Assessment Study (MSAS)

NASA, in partnership with the European Space Agency (ESA), is seeking to return Martian geological and atmospheric samples to Earth for scientific study in the early 2030s. Due to the possibility that the samples could contain extraterrestrial life, Mars Sample Return (MSR) is classified as a Category V: Restricted Earth Return mission by the NASA Planetary Protection Office. As a result of this classification, a MSR Sample Receiving Facility (SRF) must not only provide a pristine environment to ensure samples are protected from terrestrial contamination for scientific investigations, it must also provide high-containment (biosafety level 4 [BSL-4]-equivalence) to isolate the samples from Earth’s biosphere until the samples are deemed safe for release and/or sterilized. The nominal utilization period for a SRF is anticipated to be 2-5 years and is intended to enable curation activities, biohazard assessment, select early science activities, and the rapid release of samples to the scientific community. However, to account for possible delays in schedule or the identification of extant life, this anticipated period of time must be flexible to accommodate schedule extensions and contingency plans. Due to requirements for high-level biological containment and cleanliness, a traditional receiving/curation facility cannot be utilized for MSR. Therefore, beginning in 2022, NASA Johnson Space Center is performing a MSR SRF Assessment Study (MSAS) to investigate the most optimal facility modality for a MSR SRF, as well as start to define programmatic early estimate of costs and schedules before the initial design phase begins. NASA is partnering with industry contractors (architectural and engineering firms with BSL-4 and cleanroom technology experience, as well as other contracted infrastructure and construction specialists) along with selected experts from NASA, ESA, existing U.S. BSL-4 facilities, and other U.S. government agencies, to carry out the assessment study. The MSAS should also aid in the future refinement of the science requirements (e.g., contamination control, equipment accommodations) before site-specific design would commence. As part of the MSAS, NASA is planning to assess an array of possibilities for a MSR SRF. One of the main considerations is the facility modality and whether an existing BSL-4 facility can be utilized (for some or all functions); or, if new constructure would be required, would a traditional fixed facility or a modular facility the best choice. MSAS will also investigate the ability of the modalities to accommodate two different facility capability endmembers: 1) a minimal facility focusing on biohazard assessment and curation tasks with a small footprint, and 2) an enhanced facility with additional capabilities to enable expedited processing and the completion of time-sensitive and (some) sterilization-sensitive science. The assessment is intended to generate information that will inform the selection of facility modalities for high-level conceptual design development. While the assessment study will focus on SRF requirements for accommodating curation, science, and sample safety assessment infrastructure, it will also consider an array of other factors, such as ease of access for international users, decommissioning, repurposing, future sale or lease following MSR’s use of the facility, and uncontained preparatory laboratory spaces. Upon completion of the study, the preferred modality and refined requirements would be utilized for site-specific design but will not be finalized until NASA’s completion of the National Environmental Policy Act (NEPA) process.

A.D. Harrington↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service. Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations. The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-tostation handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an inorbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

Communication Network Awareness Machine System Phase I Development: The Intelligent Party-Line Schema

As NextGen continues toward the full implementation of a Net-Centric Architecture (N-CA)it will inherently provide a continuous increase to the Three-Vs components (Volume, Velocity, and Variety) of big data . This will create an insurmountable environment for direct-action aviation personnel (DAAP)as the DAAP’s natural abilities to manage and process data into actionable information will be overmatched by the Three-Vs. Therefore, conducting operations within a N-CA requires that new tools and applications be researched and developed to aid the DAAP’s ability to understand and manage data, mitigate non-normals, create contingency plans and actions. This paper will describe a research area at NASA Langley Research Center known as the Intelligent Party-Line (IPL).

Intelligent Party-Line↗

Planning and Execution of the Three Mid-Course Correction Maneuvers for the James Webb Space Telescope

The James Webb Space Telescope (JWST) was successfully launched on December 25, 2021 12:20 UTC on an Ariane 5 rocket out of Kourou, French Guiana on a direct, lower energy manifold transfer out to the Sun Earth-Moon (SEM) L2 point. Three mid-course correction (MCC) maneuvers, designated MCC-1, MCC-1b, and MCC-2, were required to provide the energy necessary to reach L2 due to a purposeful biasing down of the launch vehicle. This paper will document the prelaunch preparation, nominal planning, contingency preparation, and successful execution of the three mid-course correction maneuvers.

Jeremy Peterson↗

Human Mars Mission Transit Abort Options for Ballistic High Thrust and Hybrid Transportation Systems

Throughout the entire history of human spaceflight, astronauts have never been more than a few day's journey from Earth. For missions to the International Space Station, or even to the Moon, aborting the mission and returning home is a relatively straightforward operation in the event of a life-threatening contingency. But on the journey to Mars, a mission abort is complicated by a single factor: the sheer distance to Mars that will take time to cover regardless of how powerful the propulsion system is. In a significant departure from the entire human spaceflight experience to date, a Mars mission abort will not mean an immediate return to Earth due to the heliocentric nature of the transit. After escaping Earth’s gravity and entering heliocentric space, aborting a mission to Mars will be measured in months not days even if the abort is initiated relatively early in the mission. This represents a fundamental shift in the way mission aborts are utilized to reduce mission risks and this change must be part of the narrative when discussing reliability, crew risk, contingency planning, and mission operations. Abort capability will vary between transportation propulsion systems depending on final design, operational implementation, and actual mission parameters such as departure date, but the difference is relatively insignificant given that ``mission abort'' in the heliocentric frame of reference is a wildly different paradigm than that historically used for Earth-centric missions which rely on abort as a risk mitigation strategy. The primary objective of this paper is to provide a clearer definition of human Mars mission aborts from a celestial physics and orbital mechanics perspective in the context of different propulsion systems.

Mars Architecture Team↗

Analysis of Mars 2020 Perseverance Entry, Descent, and Landing Attitude Initialization Performance

The Mars 2020 Perseverance rover successfully landed at Jezero Crater on February 18, 2021. To perform this feat, the entry, descent, and landing navigation filter must be initialized with an estimate of the spacecraft state, which includes attitude from the cruise attitude control subsystem. Accuracy of this initial attitude estimate has an impact on important metrics such as touchdown velocity. This paper presents a post-landing reconstruction of the attitude initialization error budget, showing that the requirement of 0.15 deg ($3\sigma$, per axis) was met. Each error source is described and analyzed, including flight telemetry where possible. Analysis of the error budget shows that it is driven by systematic sun sensor errors, star-scanner-to-sun-sensor alignment stability, and inertial-measurement-unit-to-sun-sensor alignment stability. Finally, a contingency plan to initialize the navigation filter in the event of a star scanner failure is presented. While this plan was not needed in flight, results indicate that the attitude initialization requirement could have still been met in this off-nominal scenario.

Lo, Kevin D.↗

Information and Best Practices Related to NASA Nuclear Flight Safety for Space Flights Involving Space Nuclear Systems

The purpose of this handbook is to facilitate a repeatable and robust process that promotes clear and effective interfaces between activities and stakeholders focused on meeting nuclear flight safety requirements for missions utilizing space nuclear systems (SNS), within the context of NASA’s broader nuclear-related activities and interfaces. NPR 8715.26, Nuclear Flight Safety, requires that the NASA project manager “incorporate nuclear flight safety considerations starting with program or project formulation through the point at which the SNS or other radioactive material no longer has the potential to affect Earth’s biosphere.” NASA’s use of SNS inherently involves partnering with other stakeholders to conduct a range of related activities that interface with nuclear flight safety. From a categorical perspective these include: (i) meeting the authorities and licensing requirements for possession and use of nuclear material, as governed by other Federal authorities; (ii) conducting National Environmental Policy Act (NEPA) activities for nuclear-enabled missions; (iii) meeting Federal nuclear launch authorization requirements; (iv) conducting radiological contingency planning activities, including those associated with international commitments; (v) performing risk communication and public outreach activities; and (vi) ensuring decommissioning and disposal strategies reflect National policies and interests. It is the intent of this handbook to promote an effective interface between nuclear flight safety and these interrelated categorical activities. In addition to activities undertaken with partnering agencies, there are individual nuclear-related activities and programs that have a nexus to nuclear flight safety, and these include: (i) applicable NASA Standing Review Boards; (ii) the US Department of Energy nuclear safety activities conducted in partnership with NASA under Memoranda of Understanding; (iii) the Department of Defense’s Range Safety activities; (iv) NASA’s general involvement in interagency and international dialogues regarding nuclear safety; (v) the NASA-administered Interagency Nuclear Safety Review Board; (vi) NASA’s program and project governance activities and nuclear-specific Technical Discipline Team activities under the Office of the Chief Engineer; and others. It is the intent of this handbook to promote effective leveraging of these additional interrelated organizational activities, as appropriate.

Donald Helton↗

Preliminary Development of Multi-Vehicle (m:N) Operations with NASA Langley’s Remote Vehicle Operations Center

To achieve the vision of Advanced Air Mobility (AAM), a transition from localized operations of aircraft to remote operations is being pursued across many use cases. This transition will allow fewer human operators to manage more increasingly autonomous aircraft (i.e., m operators managing N vehicles, or m:N). To study this operational concept, the National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) has developed a prototype remote vehicle operations center and ground control station (GCS) software to conduct research with simulated and real flight operations. To date, flight operations at LaRC have been limited to one vehicle per operator. However, the current paper describes initial development and considerations for enabling m:N flight operations at LaRC. Further, the research described in this paper provides the foundation for a concept of operations (ConOps) that will be developed to support remote operators managing multiple increasingly autonomous vehicles, with the goal of exploring human-autonomy teaming (HAT) concepts that enable more advanced m:N operations. Two key enablers have been identified to facilitate successful m:N operations: GCS software updates for multi-vehicle management and procedural updates for vehicle handoffs during off-nominal events. Additionally, specific modifications were identified across five key areas: technology and software, team structure, inter-team communication, contingency plans, and operator decision flows. Next steps in forming the LaRC m:N ConOps will include working with subject-matter experts to identify off-nominal scenarios, implementing the recommended GCS functionality for m:N operations, and performing integration testing of facility capabilities and new operational procedures. Although the future m:N ConOps will be tailored to the NASA LaRC remote operations facility and flight range, it is intended to be a transparent, accessible, and reality-based exemplar for external organizations seeking to create or evaluate their own m:N operational concepts.

m:N↗