SEARCH · Search NASA
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.
The presentation provides an overview of the UTM Research Transition Team (RTT) and the role of the Concepts and Use Cases Working Group (CWG) as part of the joint NASA-FAA effort. The deliverables, role in tests/demonstrations, future work, and summary impact of the CWG are the main areas covered.
NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.
NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.
The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.
The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.
Explore the source record for details and available documents.
NASA's Moon to Mars Objectives outline a strategic vision for human spaceflight culminating in crewed missions to Mars. A critical component of this objective is the development of systems that are capable of being Earth-Independent Operated (EIO). A key aspect of EIO is the ability to rapidly detect, diagnose, and respond to anomalies in crew-supporting habitat and connected systems. To address this, the Dynamic Anomaly Response and Integrated Analysis (DARIA) architecture has been developed. DARIA incorporates a network of compact, wireless sensing devices called the System for Telemetry Amalgamation of Multimodal PrognosticS (STAMPS) for increased state awareness of EIO habitats. Able to perform on-the-fly data acquisition, STAMPS are connected to integrated anomaly data dashboards for crew visualization. DARIA is designed to seamlessly integrate into various off-world environments, including the International Space Station, Lunar Gateway, Artemis Base Camp, and future Mars habitats. By leveraging Commercial Off-The-Shelf (COTS) hardware, the NASA Internet of Things (NASA IoT) framework, and EIO fault detection methods, DARIA provides a cost-effective and adaptable solution for anomaly detection and response in EIO habitats.
The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.