Search NASA⌕ Search

SEARCH · Search NASA

Results for “Collision avoidance”

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 307 records · Page 17

Prototyping Operational Autonomy for Space Traffic Management

Current state of the art in Space Traffic Management (STM) relies on a handful of providers for surveillance and collision prediction, and manual coordination between operators. Neither is scalable to support the expected 10x increase in spacecraft population in less than 10 years, nor does it support automated manuever planning. We present a software prototype of an STM architecture based on open Application Programming Interfaces (APIs), drawing on previous work by NASA to develop an architecture for low-altitude Unmanned Aerial System Traffic Management. The STM architecture is designed to provide structure to the interactions between spacecraft operators, various regulatory bodies, and service suppliers, while maintaining flexibility of these interactions and the ability for new market participants to enter easily. Autonomy is an indispensable part of the proposed architecture in enabling efficient data sharing, coordination between STM participants and safe flight operations. Examples of autonomy within STM include syncing multiple non-authoritative catalogs of resident space objects, or determining which spacecraft maneuvers when preventing impending conjunctions between multiple spacecraft. The STM prototype is based on modern micro-service architecture adhering to OpenAPI standards and deployed in industry standard Docker containers, facilitating easy communication between different participants or services. The system architecture is designed to facilitate adding and replacing services with minimal disruption. We have implemented some example participant services (e.g. a space situational awareness provider/SSA, a conjunction assessment supplier/CAS, an automated maneuver advisor/AMA) within the prototype. Different services, with creative algorithms folded into then, can fulfil similar functional roles within the STM architecture by flexibly connecting to it using pre-defined APIs and data models, thereby lowering the barrier to entry of new players in the STM marketplace. We demonstrate the STM prototype on a multiple conjunction scenario with multiple maneuverable spacecraft, where an example CAS and AMA can recommend optimal maneuvers to the spacecraft operators, based on a predefined reward function. Such tools can intelligently search the space of potential collision avoidance maneuvers with varying parameters like lead time and propellant usage, optimize a customized reward function, and be implemented as a scheduling service within the STM architecture. The case study shows an example of autonomous maneuver planning is possible using the API-based framework. As satellite populations and predicted conjunctions increase, an STM architecture can facilitate seamless information exchange related to collision prediction and mitigation among various service applications on different platforms and servers. The availability of such an STM network also opens up new research topics on satellite maneuver planning, scheduling and negotiation across disjoint entities.

space traffic management↗

ACAS Xr Part Task Sim, Preliminary Experiment Design

In early 2022, the Human Autonomy Teaming Lab (NASA Ames Research Center) will conduct a manned, human-in-the-loop (HITL) simulation. This part task HITL will begin the lab’s Hazard Perception and Avoidance (HPA) technical work under NASA’s Advanced Air Mobility (AAM), Automated Flight and Contingency Management (AFCM) Sub-Project. The goals will be to assess levels of automation for manned, electric vertical takeoff and landing (eVTOL) aircraft. This simulation will test manual and automated Resolution Advisory (RA) responses and return-to-course (RTC) maneuvers for the first version of the Airborne Collision Avoidance System’s (ACAS) rotary-wing (Xr) variant. This will be conducted on a fixed-based simulator designed to fly eVTOL aircraft while maneuvering for intruding traffic. Variables for this study include levels of autonomy (i.e., manual and automated) as well as the types of alerts at the onset of conflicts (i.e., Corrective and RA). The data collected will include response times, losses of well clear, and maneuver sizes and durations as well as subjective ratings like acceptability, perceived workload, and meaningful human control. Additional details and future anticipations are also discussed.

air taxis↗

Microrover Operates With Minimal Computation

Small, light, highly mobile robotic vehicles called "microrovers" use sensors and artificial intelligence to perform complicated tasks autonomously. Vehicle navigates, avoids obstacles, and picks up objects using reactive control scheme selected from among few preprogrammed behaviors to respond to environment while executing assigned task. Under development for exploration and mining of other planets. Also useful in firefighting, cleaning up chemical spills, and delivering materials in factories. Reactive control scheme and principle of behavior-description language useful in reducing computational loads in prosthetic limbs and automotive collision-avoidance systems.

Miller, David P.↗

Effects of CubeSat Deployments in Low-Earth Orbit

Long-term models, such as NASA's LEGEND (LEO (Low-Earth Orbit)-to-GEO (Geosynchrous Earth Orbit) Environment Debris) model, are used to make predictions about how space activities will affect the long-term evolution of the debris environment. Part of this process is to predict how spacecraft and rocket bodies will be launched and left in the environment in the future. This has usually been accomplished by repeating past launch history to simulate future launches. It was partially upon the basis of the results of such models that both national and international orbital debris mitigation guidelines - especially the "25-year rule" for post-mission disposal - were determined. The proliferation of Cubesat launches in recent years, however, has raised concerns that we are seeing a fundamental shift in how humans launch satellites into space that may alter the assumptions upon which our current mitigation guidelines are based. The large number of Cubesats, and their short lifetime and general inability to perform collision avoidance, potentially makes them an important new source of debris. The NASA Orbital Debris Program Office (ODPO) has conducted a series of LEGEND computations to investigate the long-term effects of adding Cubesats to the environment. Several possible future scenarios were simulated to investigate the effects of the size of future Cubesat launches and the efficiency of post-mission disposal on the proliferation of catastrophic collisions over the next 200 years. These results are compared to a baseline "business-as-usual" scenario where launches are assumed to continue as in the past without major Cubesat deployments. Using these results, we make observations about the continued use of the 25-year rule and the importance of the universal application of post-mission disposal. We also discuss how the proliferation of Cubesats may affect satellite traffic at lower altitudes.

Matney, M. J.↗

Concepts of Integration for UAS Operations in the NAS

One of the major challenges facing the integration of Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) is the lack of an onboard pilot that can comply with the legal requirement identified in the US Code of Federal Regulations (CFR) that pilots see and avoid other aircraft. UAS will be expected to demonstrate the means to perform the function of see and avoid while preserving the safety level of the airspace and the efficiency of the air traffic system. This paper introduces a Sense and Avoid (SAA) concept for integration of UAS into the NAS that is currently being developed by the National Aeronautics and Space Administration (NASA) and identifies areas that require additional experimental evaluation to further inform various elements of the concept. The concept design rests on interoperability principles that take into account both the Air Traffic Control (ATC) environment as well as existing systems such as the Traffic Alert and Collision Avoidance System (TCAS). Specifically, the concept addresses the determination of well clear values that are large enough to avoid issuance of TCAS corrective Resolution Advisories, undue concern by pilots of proximate aircraft and issuance of controller traffic alerts. The concept also addresses appropriate declaration times for projected losses of well clear conditions and maneuvers to regain well clear separation.

Consiglio, Maria C.↗

Strategic Deconfliction Performance: Results and Analysis from the NASA UTM Technical Capability Level 4 Demonstration

Unmanned Aircraft System (UAS) Traffic Management (UTM) refers to the service-based, cooperative approach to the management of small UAS in the National Airspace System that is safe, scalable, and fair. UTM provides the means to manage the airspace in a complementary manner that does not burden the current air traffic control workforce or infrastructure but allows the Air Navigation Service Provider to maintain its regulatory and operational authority of the airspace. A key feature of UTM is the ability to provide operators the means to strategically deconflict operations from others in the airspace through the digital exchange of information via supporting services. Through this approach, the four-dimensional operation volumes that encompass the intent of operators in a given area are discoverable and can be used for airspace awareness as well as planning conflict free operations that account for and avoid other operations. In certain cases, it is also possible to negotiate volume intersections for shared airspace use without the need to re-plan. In the NASA UTM concept, strategic deconfliction is the first layer of three in the overall conflict management model. The three layers of the conflict management model, which follow the International Civil Aviation Organization’s scheme [ICAO 2005] are: strategic conflict management, separate provision, and collision avoidance. In UTM, the strategic layer mostly occurs prior to departure, but is applicable to en route operations with sufficient planning horizon. The initial requirements for a strategic deconfliction capability within UTM are defined in a NASA publication [Rios 2018]. Within the concept and implementation of service-provided strategic deconfliction is the notion of priority. It is understood that there are instances in which an operation requires a priority designation within the UTM system and special handling accordingly to provide situation awareness and facilitate appropriate responses from other airspace users. Examples of situations requiring priority designation include: when an operator declares an emergency due to problems with the vehicle or its immediate surroundings; operations that are in support of certain organizations (e.g., public safety and first responders); or special missions that also require priority use of airspace (e.g., emergency medical deliveries). UAS Volume Reservations (UVRs) also relate to the topic of priority in the sense that the airspace that the volume encompasses has a different status or classification in which unassociated operations must vacate if inside, or avoid if outside, through strategic deconfliction with the volume. Operations that are specially permitted to access the UVR area are typically assigned priority status given the nature of their mission and their associated credentials. The ability to perform strategic deconfliction, handle certain operations with a priority distinction, and establish UVRs that are communicated throughout the UTM system, is predicated on an architecture that has been established through an evolutionary process in response to close collaboration with stakeholders from government and industry. Another important and influential aspect of these capabilities and architecture is the live, distributed flight tests that have been conducted across the Technical Capability Levels (TCLs) that culminated with a set of complex tests performed as part of TCL4 [Rios 2020]. The TCL4 flight test involved two FAA-designated UAS test sites building teams to collaborate with NASA’s UTM Project on the execution of several detailed, small UAS scenarios in urban environments.

conflict management↗

Target Trailing With Safe Navigation for Maritime Autonomous Surface Vehicles

This software implements a motion-planning module for a maritime autonomous surface vehicle (ASV). The module trails a given target while also avoiding static and dynamic surface hazards. When surface hazards are other moving boats, the motion planner must apply International Regulations for Avoiding Collisions at Sea (COLREGS). A key subset of these rules has been implemented in the software. In case contact with the target is lost, the software can receive and follow a "reacquisition route," provided by a complementary system, until the target is reacquired. The programmatic intention is that the trailed target is a submarine, although any mobile naval platform could serve as the target. The algorithmic approach to combining motion with a (possibly moving) goal location, while avoiding local hazards, may be applicable to robotic rovers, automated landing systems, and autonomous airships. The software operates in JPL s CARACaS (Control Architecture for Robotic Agent Command and Sensing) software architecture and relies on other modules for environmental perception data and information on the predicted detectability of the target, as well as the low-level interface to the boat controls.

Wolf, Michael↗

Distance estimation and collision prediction for on-line robotic motion planning

An efficient method for computing the minimum distance and predicting collisions between moving objects is presented. This problem is incorporated into the framework of an in-line motion-planning algorithm to satisfy collision avoidance between a robot and moving objects modeled as convex polyhedra. In the beginning, the deterministic problem where the information about the objects is assumed to be certain is examined. L(1) or L(infinity) norms are used to represent distance and the problem becomes a linear programming problem. The stochastic problem is formulated where the uncertainty is induced by sensing and the unknown dynamics of the moving obstacles. Two problems are considered: First, filtering of the distance between the robot and the moving object at the present time. Second, prediction of the minimum distance in the future in order to predict the collision time.

Kyriakopoulos, K. J.↗

JSC Orbital Debris Website Description

Purpose: The website provides information about the NASA Orbital Debris Program Office at JSC, which is the lead NASA center for orbital debris research. It is recognized world-wide for its leadership in addressing orbital debris issues. The NASA Orbital Debris Program Office has taken the international lead in conducting measurements of the environment and in developing the technical consensus for adopting mitigation measures to protect users of the orbital environment. Work at the center continues with developing an improved understanding of the orbital debris environment and measures that can be taken to control its growth. Major Contents: Orbital Debris research is divided into the following five broad efforts. Each area of research contains specific information as follows: 1) Modeling - NASA scientists continue to develop and upgrade orbital debris models to describe and characterize the current and future debris environment. Evolutionary and engineering models are described in detail. Downloadable items include a document in PDF format and executable software. 2) Measurements - Measurements of near-Earth orbital debris are accomplished by conducting ground-based and space-based observations of the orbital debris environment. The data from these sources provide validation of the environment models and identify the presence of new sources. Radar, optical and surface examinations are described. External links to related topics are provided. 3) Protection - Orbital debris protection involves conducting hypervelocity impact measurements to assess the risk presented by orbital debris to operating spacecraft and developing new materials and new designs to provide better protection from the environment with less weight penalty. The data from this work provides the link between the environment defined by the models and the risk presented by that environment to operating spacecraft and provides recommendations on design and operations procedures to reduce the risk as required. These data also help in the analysis and interpretation of impact features on returned spacecraft surfaces. 4) Mitigation - Controlling the growth of the orbital debris population is a high priority for NASA, the United States, and the major space-faring nations of the world to preserve near-Earth space for future generations. Mitigation measures can take the form of curtailing or preventing the creation of new debris, designing satellites to withstand impacts by small debris, and implementing operational procedures ranging from utilizing orbital regimes with less debris, adopting specific spacecraft attitudes, and even maneuvering to avoid collisions with debris. Downloadable items include several documents in PDF format and executable software.and 5) Reentry - Because of the increasing number of objects in space, NASA has adopted guidelines and assessment procedures to reduce the number of non-operational spacecraft and spent rocket upper stages orbiting the Earth. One method of postmission disposal is to allow reentry of these spacecraft, either from orbital decay (uncontrolled entry) or with a controlled entry. Orbital decay may be achieved by firing engines to lower the perigee altitude so that atmospheric drag will eventually cause the spacecraft to enter. However, the surviving debris impact footprint cannot be guaranteed to avoid inhabited landmasses. Controlled entry normally occurs by using a larger amount of propellant with a larger propulsion system to drive the spacecraft to enter the atmosphere at a steeper flight path angle. It will then enter at a more precise latitude, longitude, and footprint in a nearly uninhabited impact region, generally located in the ocean.

Johnson, Nicholas L.↗

Distance estimation and collision prediction for on-line robotic motion planning

An efficient method for computing the minimum distance and predicting collisions between moving objects is presented. This problem has been incorporated in the framework of an in-line motion planning algorithm to satisfy collision avoidance between a robot and moving objects modeled as convex polyhedra. In the beginning the deterministic problem, where the information about the objects is assumed to be certain is examined. If instead of the Euclidean norm, L(sub 1) or L(sub infinity) norms are used to represent distance, the problem becomes a linear programming problem. The stochastic problem is formulated, where the uncertainty is induced by sensing and the unknown dynamics of the moving obstacles. Two problems are considered: (1) filtering of the minimum distance between the robot and the moving object, at the present time; and (2) prediction of the minimum distance in the future, in order to predict possible collisions with the moving obstacles and estimate the collision time.

Kyriakopoulos, K. J.↗

SC-228 Inclusion of DAA Warning Alert for TCAS Interoperability

This white paper summarizes NASA research results that have informed Special Committee 228 (SC-228) discussions and decisions regarding the inclusion of a warning-level alert within the detect and avoid (DAA) alerting structure for unmanned aircraft systems (UAS). For UAS, the removal of the pilot from onboard the aircraft has eliminated the ability of the ground-based pilot in command (PIC) to use out-the-window visual information to make judgments about a potential threat of a loss of well clear with another aircraft. As a result, the DAA traffic display will be the primary source of information that the PIC can use to execute the three primary well clear functions: 1) detect a potential loss of well clear, 2) determine a resolution maneuver, and 3) upload that maneuver to the aircraft via the ground control station (GCS). In addition, pilots are required to coordinate with air traffic control (ATC) prior to maneuvering off of their approved flight plan. In determining an appropriate resolution maneuver to avoid a loss of well clear, the PIC must decide both when and how to maneuver, and both the timeliness and the accuracy (i.e., correctness) of the maneuver are critical to reducing the likelihood and/or severity of a loss of well clear. Alerting information is one of three critical components of the DAA display, along with traffic information elements (e.g., relative heading, speed and altitude) and maneuver guidance. Alerting information and maneuver guidance, in particular, have been found to have a significant impact, both statistically and practically, on pilots' ability to avoid and minimize the severity of losses of well clear While all three display components are key to pilots performing the traffic avoidance task of remaining well clear, in general, alerting information provides crucial information about when a resolution maneuver is required while maneuver guidance assists the pilot in determining how best to maneuver. A fundamental task of the DAA alerting system is to provide critical timing information to the pilot about the potential for a loss of well clear with another aircraft. This is done by employing both temporal and spatial thresholds that indicate to the pilot the likelihood and imminence of a loss of well clear. The design of the DAA alerting thresholds is a balancing act between eliciting the desired pilot response in real loss of well clear threat events and reducing excessive, unnecessary, and/or uncoordinated UAS maneuvering within the air traffic environment; larger thresholds, both spatially and temporally, may increase the likelihood of a pilot avoiding a loss of well clear, but it can also increase the frequency of maneuvering - especially in cases where a maneuver is not actually needed to maintain well clear. A series of human in the loop (HITL) simulations have been conducted as part of NASA's Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) project. The purpose of these HITLs has been to provide empirical results in order to inform development of the minimum human-machine interface requirements for the DAA system. This white paper will present those results which provide evidence of a human performance benefit (in terms of response times and ability to remain well clear of other aircraft) of the DAA warning alert both with and without a collision avoidance system on board the aircraft.

TCAS interoperability↗

Functional Allocation Approach for Separation Assurance for Remotely Piloted Aircraft

A functional analysis framework is employed with the objective of exploring the separation assurance function for the remotely piloted aircraft system. The architecture of the remotely piloted aircraft system—highlighting several of the component systems and the functions resident onboard the remotely piloted aircraft and in the ground control station—is described to provide the context for understanding the complexity of the said system for a detailed functional analysis. The interactions between the agents of the separation assurance function belonging to the air traffic service provider, remotely piloted aircraft system operator and remotely piloted aircraft are described. Separation assurance by air traffic control, remain well clear by the remotely piloted aircraft system and collision avoidance onboard the remotely piloted aircraft are briefly discussed. The functional analysis framework is illustrated by relating the agents to the actions of (a) acquiring the surveillance information, (b) checking for conflicts, (c) creating the solutions for resolving conflicts and (d) implementing the conflict resolution solutions. This example is offered as a template by which a more detailed functional analysis of this and other functions could be developed. The architecture of the remotely piloted aircraft system is described to aid this process.

Functional analysis↗

Controlling telerobots with video data and compensating for time-delayed video using Omniview

Remote viewing is critical for teleoperations, but the inherent limitations of standard video reduce the operator's effectiveness. These limitations have been compensated for in many ways, from using the operator's adaptability, to augmenting his capability with feedback from a variety of sensors and simulations. Omniview can overcome some of these limitations and improve the operator's efficiency without adding additional sensors or computational burden. It can minimize the potential collisions with facility equipment, provide peripheral vision, and display multiple images simultaneously from a single input device. The Omniview technology provides electronic pan, tilt, magnify, and rotational orientation within a hemispherical field-of-view without any moving parts. Image sizes, viewing directions, scale, offset, etc., may be adjusted to fit operator needs. This paper discusses the derivation of the image transformation, the design of the electronics, and two applications to telepresence that are under development. These are Video Emulated Tweening (VET), and Manipulator Guidance and Positioning (ManGAP). The VET effort uses Omniview to compensate for time-delayed video in teleoperation of remote vehicles. In ManGAP two Omniview systems are used to provide two sets of orientation vectors to points in the field-of-view (FOV). These vectors then provide absolute position information to both control the position of the telerobot, and to avoid collisions with the work sight equipment.

Kuban, Dan↗

Functional Allocation Approach for Separation Assurance for Remotely Piloted Aircraft

A functional analysis framework is employed with the objective of exploring the separation assurance function for the remotely piloted aircraft system. The architecture of the remotely piloted aircraft system—highlighting several of the component systems and the functions resident onboard the remotely piloted aircraft and in the ground control station—is described to provide the context for understanding the complexity of the said system for a detailed functional analysis. The interactions between the agents of the separation assurance function belonging to the air traffic service provider, remotely piloted aircraft system operator and remotely piloted aircraft are described. Separation assurance by air traffic control, remain well clear by the remotely piloted aircraft system and collision avoidance onboard the remotely piloted aircraft are briefly discussed. The functional analysis framework is illustrated by relating the agents to the actions of (a) acquiring the surveillance information, (b) checking for conflicts, (c) creating the solutions for resolving conflicts and (d) implementing the conflict resolution solutions. This example is offered as a template by which a more detailed functional analysis of this and other functions could be developed. The architecture of the remotely piloted aircraft system is described to aid this process.

functional analysis↗

ACES M and S: Unmitigated Factorial Encounter Study on DAA/TCAS Interoperability

Realization of the expected proliferation of Unmanned Aircraft System (UAS) operations in the National Airspace System (NAS) depends on the development and validation of standards for UAS Detect and Avoid (DAA) Systems. The RTCA Special Committee 228 is charged with leading the development of draft Minimum Operational Performance Standards (MOPS) for UAS DAA Systems. NASA, as a participating member of RTCA SC-228 is committed to supporting the development and validation of draft requirements for DAA alerting and guidance systems. This presentation contains the results of two combinatorial encounter analysis studies using NASA's SAA Control fast-time simulation capability for this purpose. In these studies, encounters between two aircraft were simulated one at a time for the full factorial combination of encounter geometries (e.g., encounter angle, CPA offset) and aircraft performance (e.g., ownership and intruder ground speeds and vertical rates). The first study analyzes the relationships (e.g., timeline) between the different alerting-safety regions in the SC-228 MOPS (in order of increasing severity): 1) DAA warning alert, 2) well clear recovery (WCR) guidance, 3) DAA-Collision Avoidance (CA), and 4) TCAS RA. This study will focus primarily on encounter situations in which TCAS RA occurs prior to any of the other alerting-safety boundaries. In particular, this study will investigate whether using vertical distance or vertical distance at closest point of approach (i.e., vertical miss distance or VMD) is more appropriate for the definition of the DAA-CA region. In addition, cases where transitions between different regions skip an intermediate region will be analyzed. The second study in this presentation explores a proposal to use an altitude rate error threshold to determine if vertical maneuvers are acceptable for DAA WCR guidance against non-cooperative intruders. This study incorporates the radar from the Honeywell sensor model and examines a series of pairwise encounters between a non-cooperative intruder and a UAS ownship, with different combinations of intruder states and ownship performance levels. The study uses SAA Control as a simulation platform and pilot model, and Omnibands to provide DWC recovery guidance. Two simulation sets, one that allows vertical DWC recovery guidance and one that does not, are compared to determine if encounters with altitude rate errors above 250 feet-per-minute are more likely to have more severe losses of well clear, as determined by the Loss of Well-Clear Severity metric.

SaaControl↗

Avoiding a maneuvering aircraft with TCAS

The present investigation was carried out in NASA's Man-Vehicle Systems Research Facility B 727 simulator because of the need for veridical aircraft response. Pilot performance was measured in testing TCAS II after an avoidance maneuver has been initiated. A proposed change to the system will cause the TCAS II to issue a subsequent maneuver. This maneuver may be an increase in climb or descent rate from 1500 to 2500 ft/min, or a change from a climb to a descent or a descent to a climb. Three questions were addressed: (1) can the pilot detect the change in the maneuver advisory, (2) can the pilot respond promptly and accurately to the new advisory, and (3) can the maneuver be performed in the normal operating envelope of the aircraft. The reaction times found in the study suggest that pilots are able to respond within the two seconds targeted by the TCAS logic. The pilot performance data were used to modify the TCAS II logic to reflect actual pilot performance. This will result in a safe and appropriate maneuver selection in the rare instance when the conflicting aircraft maneuvers, and by doing so invalidates the initial maneuver issued by the collision avoidance system.

Chappell, Sheryl L.↗

Computing Proximity to Threat Along Uncertain Trajectory to Support Urban Air Mobility

Many airspace threats affect the selection of a flight route, such as terrain, physical obstacles, adverse weather, and special-use airspace, among others. Threat avoidance during Urban Air Mobility (UAM) and Low Altitude Mobility (LAM) flights is especially challenging due to their lower cruising altitudes. These operations may be exposed to buildings, towers, trees, terrain undulations, etc., along much of their flight route. Moreover, these low-altitude flights in urban environments are expected to encounter very busy airspace, increasing the workload associated with threat avoidance. The Proximity to Threat (PtT) function aims to support onboard or remote pilots by computing the risk from geospatial threats in the airspace along an aircraft’s flight path. The threats are both static entities and dynamic airspace restrictions that have been modeled and stored in geo-referenced mapping databases. The flight path may be specified by waypoints, airways, or similar discrete route elements or by a time series of closely spaced position and altitude points. Flight path uncertainty can also be taken into account by assuming both the position and altitude to be sampled from two normal distributions, each being specified by a mean and variance. PtT uses this additional information to verify that the flight path remains clear of threats along a wider path or if a position is reached earlier or later than anticipated, assuring the pilot or operator that there will be an available safety margin even if the aircraft deviates due to one or more occurrences of unexpected wind gusts, mechanical failures, airspeed changes, collision avoidance maneuvers, etc. The client can specify an uncertainty confidence level to bound the set of trajectories evaluated for threats so that the confidence level corresponds to the client’s risk tolerance under the expected conditions. PtT can be used as a pre-flight planning tool to determine a safe route through known threats and in-flight to avoid emerging or changing threats. In this report, we present the PtT function, discuss how the trajectory uncertainty is incorporated into the PtT function, and describe the use of this PtT function in a representative scenario.

urban air mobility↗

Appendix N. Pc Calculation Approaches – UPDATE 3/20/24

This document represents a technical content update to Appendix N of the NASA Spacecraft Conjunction Assessment and Collision Avoidance Best Practices Handbook (OCE-51, available on NODIS) requested by the Consultative Committee for Space Data Standards (CCSDS) to document the background on why NASA populates certain fields of the Conjunction Data Message (CDM) in certain ways. This update was requested to be used as reference material for the CCSDS CDM documentation update and so is being published as a white paper out of cycle from Handbook updates. When the full Handbook is next updated, these Appendix redlines may be incorporated into the official document. Two versions are attached - the redlines to the published Handbook for use in understanding what has changed and a clean copy.

conjunction assessment↗