Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operational 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.

304 records · Page 17
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Adaptive Stress Testing: Using Reinforcement Learning to Find Failures in Safety-Critical Systems

Emerging applications in artificial intelligence, such as driverless cars and autonomous aircraft promise to be more efficient, cheaper to operate, and always available. However, ensuring the safety of these systems remains a major challenge to their certification and adoption. These autonomous systems are expected to routinely make safety-critical decisions where failures can have serious consequences including loss of life and property. Testing and validation techniques aim to identify and diagnose potential failures before the system is deployed. However, finding failure scenarios in autonomous systems can be very challenging due to high-dimensional and continuous state spaces, interaction with large environments over many time steps, and the rarity of failures. This talk presents Adaptive Stress Testing (AST), a simulation-based testing framework for finding the most likely path to a failure event of a safety-critical system. The key idea of AST is that stress testing can be formulated as a Partially Observable Markov Decision Process (POMDP), which enables reinforcement learning techniques to be used for finding failure events. Reinforcement learning algorithms can efficiently explore the search space and have been shown to scale to very large systems. We present applications of AST to find failures in various safety-critical systems including the aircraft collision avoidance systems, autonomous cars, and small unmanned aerial vehicles.

autonomous vehicles↗
NASA NTRS2017

UAS Well Clear Recovery Against Non-Cooperative Intruders Using Vertical Maneuvers

This paper documents a study that drove the development of a mathematical expression in the minimum operational performance standards (MOPS) of detect-and-avoid (DAA) systems for unmanned aircraft systems (UAS). This equation describes the conditions under which vertical maneuver guidance could be provided during recovery of well clear separation with a non-cooperative VFR aircraft in addition to horizontal maneuver guidance. Although suppressing vertical maneuver guidance in these situations increased the minimum horizontal separation from 500 to 800 feet, the maximum severity of loss of well clear increased in about 35 of the encounters compared to when a vertical maneuver was preferred and allowed. Additionally, analysis of individual cases led to the identification of a class of encounter where vertical rate error had a large effect on horizontal maneuvers due to the difficulty of making the correct left-right turn decision: crossing conflict with intruder changing altitude. These results supported allowing vertical maneuvers when UAS vertical performance exceeds the relative vertical position and velocity accuracy of the DAA tracker given the current velocity of the UAS and the relative vertical position and velocity estimated by the DAA tracker. Looking ahead, these results indicate a need to improve guidance algorithms by utilizing maneuver stability and near mid-air collision risk when determining maneuver guidance to regain well clear separation.

detect and avoid↗
NASA NTRS2008

2007 Research and Engineering Annual Report

Selected research and technology activities at NASA Dryden Flight Research Center are summarized. These following activities exemplify the Center's varied and productive research efforts: Developing a Requirements Development Guide for an Automatic Ground Collision Avoidance System; Digital Terrain Data Compression and Rendering for Automatic Ground Collision Avoidance Systems; Nonlinear Flutter/Limit Cycle Oscillations Prediction Tool; Nonlinear System Identification Using Orthonormal Bases: Application to Aeroelastic/Aeroservoelastic Systems; Critical Aerodynamic Flow Feature Indicators: Towards Application with the Aerostructures Test Wing; Multidisciplinary Design, Analysis, and Optimization Tool Development Using a Genetic Algorithm; Structural Model Tuning Capability in an Object-Oriented Multidisciplinary Design, Analysis, and Optimization Tool; Extension of Ko Straight-Beam Displacement Theory to the Deformed Shape Predictions of Curved Structures; F-15B with Phoenix Missile and Pylon Assembly--Drag Force Estimation; Mass Property Testing of Phoenix Missile Hypersonic Testbed Hardware; ARMD Hypersonics Project Materials and Structures: Testing of Scramjet Thermal Protection System Concepts; High-Temperature Modal Survey of the Ruddervator Subcomponent Test Article; ARMD Hypersonics Project Materials and Structures: C/SiC Ruddervator Subcomponent Test and Analysis Task; Ground Vibration Testing and Model Correlation of the Phoenix Missile Hypersonic Testbed; Phoenix Missile Hypersonic Testbed: Performance Design and Analysis; Crew Exploration Vehicle Launch Abort System-Pad Abort-1 (PA-1) Flight Test; Testing the Orion (Crew Exploration Vehicle) Launch Abort System-Ascent Abort-1 (AA-1) Flight Test; SOFIA Flight-Test Flutter Prediction Methodology; SOFIA Closed-Door Aerodynamic Analyses; SOFIA Handling Qualities Evaluation for Closed-Door Operations; C-17 Support of IRAC Engine Model Development; Current Capabilities and Future Upgrade Plans of the C-17 Data Rack; Intelligent Data Mining Capabilities as Applied to Integrated Vehicle Health Management; STARS Flight Demonstration No. 2 IP Data Formatter; Space-Based Telemetry and Range Safety (STARS) Flight Demonstration No. 2 Range User Flight Test Results; Aerodynamic Effects of the Quiet Spike(tm) on an F-15B Aircraft; F-15 Intelligent Flight Controls-Increased Destabilization Failure; F-15 Integrated Resilient Aircraft Control (IRAC) Improved Adaptive Controller; Aeroelastic Analysis of the Ikhana/Fire Pod System; Ikhana: Western States Fire Missions Utilizing the Ames Research Center Fire Sensor; Ikhana: Fiber-Optic Wing Shape Sensors; Ikhana: ARTS III; SOFIA Closed-Door Flutter Envelope Flight Testing; F-15B Quiet Spike(TM) Aeroservoelastic Flight Test Data Analysis; and UAVSAR Platform Precision Autopilot Flight Results.

Stoliker, Patrick↗
NASA NTRS2003

Modeling, Analyzing, and Mitigating Dissonance Between Alerting Systems

Alerting systems are becoming pervasive in process operations, which may result in the potential for dissonance or conflict in information from different alerting systems that suggests different threat levels and/or actions to resolve hazards. Little is currently available to help in predicting or solving the dissonance problem. This thesis presents a methodology to model and analyze dissonance between alerting systems, providing both a theoretical foundation for understanding dissonance and a practical basis from which specific problems can be addressed. A state-space representation of multiple alerting system operation is generalized that can be tailored across a variety of applications. Based on the representation, two major causes of dissonance are identified: logic differences and sensor error. Additionally, several possible types of dissonance are identified. A mathematical analysis method is developed to identify the conditions for dissonance originating from logic differences. A probabilistic analysis methodology is developed to estimate the probability of dissonance originating from sensor error, and to compare the relative contribution to dissonance of sensor error against the contribution from logic differences. A hybrid model, which describes the dynamic behavior of the process with multiple alerting systems, is developed to identify dangerous dissonance space, from which the process can lead to disaster. Methodologies to avoid or mitigate dissonance are outlined. Two examples are used to demonstrate the application of the methodology. First, a conceptual In-Trail Spacing example is presented. The methodology is applied to identify the conditions for possible dissonance, to identify relative contribution of logic difference and sensor error, and to identify dangerous dissonance space. Several proposed mitigation methods are demonstrated in this example. In the second example, the methodology is applied to address the dissonance problem between two air traffic alert and avoidance systems: the existing Traffic Alert and Collision Avoidance System (TCAS) vs. the proposed Airborne Conflict Management system (ACM). Conditions on ACM resolution maneuvers are identified to avoid dynamic dissonance between TCAS and ACM. Also included in this report is an Appendix written by Lee Winder about recent and continuing work on alerting systems design. The application of Markov Decision Process (MDP) theory to complex alerting problems is discussed and illustrated with an abstract example system.

Song, Lixia↗
NASA NTRS2019

Detect-and-Avoid Alerting Performance for High-Speed UAS and Non-Cooperative Aircraft

This paper presents a set of experiments designed to assess the viability of using a smaller Detect and Avoid (DAA) volume for large Unmanned Aircraft Systems (UAS) when they are trying to remain well clear of non-cooperative visual flight rules (VFR) aircraft, in compliance with Federal regulations. The current DAA volume was defined for both cooperative and non-cooperative VFR traffic by the work of RTCA Special Committee 228 in 2017, in what is referred to in this paper as the Phase 1 standards. Subsequent work by the committee has been focused on enabling operations by smaller UAS that cannot carry the heavy radars required for the Phase 1 DAA Minimum Operational Performance Standards (MOPS). The work discussed in this paper will explore whether a Phase 1 UAS using a Phase 1 radar can use the reduced non-cooperative DAA alerting volume being studied for smaller, slower Phase 2 UAS without significantly degrading system safety. The study uses UAS models and background traffic from previous Phase 1 and Phase 2 research to run an unmitigated simulation that will examine alerting performance using different DAA well clear definitions. The primary metrics are also tied to the alerting performance of the DAA system, and include average alerting times, probabilities of missed and late alerts, and the probability of a near mid-air collision given a loss of "well clear," as defined by the DAA system. Results are expected to help RTCA make the determination whether or not the DAA well clear definition for Phase 1 UAS can be reduced for non-cooperative VFR aircraft.

Cone, Andrew C.↗
NASA NTRS2010

Stereoscopic Machine-Vision System Using Projected Circles

A machine-vision system capable of detecting obstacles large enough to damage or trap a robotic vehicle is undergoing development. The system includes (1) a pattern generator that projects concentric circles of laser light forward onto the terrain, (2) a stereoscopic pair of cameras that are aimed forward to acquire images of the circles, (3) a frame grabber and digitizer for acquiring image data from the cameras, and (4) a single-board computer that processes the data. The system is being developed as a prototype of machine- vision systems to enable robotic vehicles ( rovers ) on remote planets to avoid craters, large rocks, and other terrain features that could capture or damage the vehicles. Potential terrestrial applications of systems like this one could include terrain mapping, collision avoidance, navigation of robotic vehicles, mining, and robotic rescue. This system is based partly on the same principles as those of a prior stereoscopic machine-vision system in which the cameras acquire images of a single stripe of laser light that is swept forward across the terrain. However, this system is designed to afford improvements over some of the undesirable features of the prior system, including the need for a pan-and-tilt mechanism to aim the laser to generate the swept stripe, ambiguities in interpretation of the single-stripe image, the time needed to sweep the stripe across the terrain and process the data from many images acquired during that time, and difficulty of calibration because of the narrowness of the stripe. In this system, the pattern generator does not contain any moving parts and need not be mounted on a pan-and-tilt mechanism: the pattern of concentric circles is projected steadily in the forward direction. The system calibrates itself by use of data acquired during projection of the concentric-circle pattern onto a known target representing flat ground. The calibration- target image data are stored in the computer memory for use as a template in processing terrain images. During operation on terrain, the images acquired by the left and right cameras are analyzed. The analysis includes (1) computation of the horizontal and vertical dimensions and the aspect ratios of rectangles that bound the circle images and (2) comparison of these aspect ratios with those of the template. Coordinates of distortions of the circles are used to identify and locate objects. If the analysis leads to identification of an object of significant size, then stereoscopicvision algorithms are used to estimate the distance to the object. The time taken in performing this analysis on a single pair of images acquired by the left and right cameras in this system is a fraction of the time taken in processing the many pairs of images acquired in a sweep of the laser stripe across the field of view in the prior system. The results of the analysis include data on sizes and shapes of, and distances and directions to, objects. Coordinates of objects are updated as the vehicle moves so that intelligent decisions regarding speed and direction can be made. The results of the analysis are utilized in a computational decision-making process that generates obstacle-avoidance data and feeds those data to the control system of the robotic vehicle.

Mackey, Jeffrey R.↗
NASA NTRS2019

Detect-and-Avoid Alerting Performance for High-Speed UAS and Non-Cooperative Aircraft

This paper presents a set of experiments designed to assess the viability of using a smaller Detect and Avoid (DAA) volume for large Unmanned Aircraft Systems (UAS) when they are trying to remain well clear of non-cooperative visual flight rules (VFR) aircraft, in compliance with Federal regulations. The current DAA volume was defined for both cooperative and non-cooperative VFR traffic by the work of RTCA (Radio Technical Commission for Aeronautics) Special Committee 228 in 2017, in what is referred to in this paper as the Phase 1 standards. Subsequent work by the committee has been focused on enabling operations by smaller UAS that cannot carry the heavy radars required for the Phase 1 DAA Minimum Operational Performance Standards (MOPS). The work discussed in this paper will explore whether a Phase 1 UAS using a Phase 1 radar can use the reduced non-cooperative DAA alerting volume being studied for smaller, slower Phase 2 UAS without significantly degrading system safety. The study uses UAS models and background traffic from previous Phase 1 and Phase 2 research to run an unmitigated simulation that will examine alerting performance using different DAA well clear definitions. The primary metrics are also tied to the alerting performance of the DAA system, and include average alerting times, probabilities of missed and late alerts, and the probability of a near mid-air collision given a loss of "well clear," as defined by the DAA system. Results are expected to help RTCA make the determination whether or not the DAA well clear definition for Phase 1 UAS can be reduced for non-cooperative VFR aircraft.

UAS↗
NASA NTRS2019

Scenario Complexity for Unmanned Aircraft System Traffic

This work introduces an approach to estimate the complexity of a low-altitude air traffic scenario involving multiple UASs using mathematical programming. Given a set of multi-point UAS flight trajectories, vehicle dynamics, and a conflict resolution algorithm, an abstract model is developed such that it can be solved quickly using a mathematical programming optimization software without running high-fidelity simulations that can be computationally expensive and may not suit real-time apA quick and accurate assessment of complexity for a given traffic scenario can help plan and schedule flights to alleviate traffic bottleneck and mitigate operation risks, especially for unmanned aerial system traffic management where high traffic density or complexity is expected. This work introduces a traffic scenario complexity metric that was constructed based on the number of potential conflicts weighted by the conflict resolution cost associated. The cost associated with a conflict is calculated based on the corresponding conflict resolution maneuvers. To obtain the conflict resolution maneuvers, a MILP-based optimization was formulated with the vehicle model and conflict management parameters incorporated. To evaluate the complexity metrics, an approach of using measurements from high-fidelity simulations was proposed. The scenario complexity measurements for 920 random-generated scenarios were obtained through high-fidelity simulations and treated as the ground truth. Two statistics methods: Pearson and Alternative Conditional Expectations were applied for analysis. The results showed that the number of flights has low correlation with the scenario complexity according to the correlation coefficients calculated by both methods. The Alternative Conditional Expectations method shows that the proposed scenario complexity metric has better correlation with the ground truth than the number of potential conflicts.plications. In the abstract model, each vehicle is represented by a time-varied vector associated with position, speed, and heading information. The total extra distance that aircraft need to divert from their original routes to avoid collisions is computed and used to setup a quadratic programming formula. The metrics including the number of conflicts and extra distances travelled by all vehicles are then utilized to estimate the complexity of a given UAS flight scenario. Results and verification against high-fidelity simulations will be provided in the final draft.

traffic complexity↗
NASA NTRS2015

Java Architecture for Detect and Avoid Extensibility and Modeling

Unmanned aircraft will equip with a detect-and-avoid (DAA) system that enables them to comply with the requirement to "see and avoid" other aircraft, an important layer in the overall set of procedural, strategic and tactical separation methods designed to prevent mid-air collisions. This paper describes a capability called Java Architecture for Detect and Avoid Extensibility and Modeling (JADEM), developed to prototype and help evaluate various DAA technological requirements by providing a flexible and extensible software platform that models all major detect-and-avoid functions. Figure 1 illustrates JADEM's architecture. The surveillance module can be actual equipment on the unmanned aircraft or simulators that model the process by which sensors on-board detect other aircraft and provide track data to the traffic display. The track evaluation function evaluates each detected aircraft and decides whether to provide an alert to the pilot and its severity. Guidance is a combination of intruder track information, alerting, and avoidance/advisory algorithms behind the tools shown on the traffic display to aid the pilot in determining a maneuver to avoid a loss of well clear. All these functions are designed with a common interface and configurable implementation, which is critical in exploring DAA requirements. To date, JADEM has been utilized in three computer simulations of the National Airspace System, three pilot-in-the-loop experiments using a total of 37 professional UAS pilots, and two flight tests using NASA's Predator-B unmanned aircraft, named Ikhana. The data collected has directly informed the quantitative separation standard for "well clear", safety case, requirements development, and the operational environment for the DAA minimum operational performance standards. This work was performed by the Separation Assurance/Sense and Avoid Interoperability team under NASA's UAS Integration in the NAS project.

unmanned aircraft systems↗
NASA NTRS2019

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project

Phase 1 of the UAS-NAS (Unmanned Aircraft Systems-National Airspace System) project focused on MOPS (Minimum Operational Performance Standards) development for large UAS transitioning through Class D, E, and G airspace. Phase 2 activities are currently focused on extended UAS operations in Class D, E, and G airspace, as well as sensors and architectures that will enable DAA (Detect and Avoid) equipment to be installed on a wider range of UAS. Encounters with non-cooperative intruders in low altitude airspace under 10,000 feet will be explored for UAS with a low Size, Weight, and Power (SWaP) radar. New sensors for detecting non-cooperative intruder aircraft will have a more limited detection range and field of regard; therefore, the analysis of non-cooperative encounter geometries may help in developing the requirements for an onboard low SWaP radar (and electro-optical sensor). The current simulation, led by HSI (Human Systems Integration Division at NASA Ames Research Center) as part of the DAA subproject, will support efforts toward developing a modified DAA Well Clear (DWC) definition that would be more appropriate for UAS equipped with limited surveillance and aircraft performance capabilities compared to the Phase 1 DAA system. The findings will inform Phase 2 display requirements for alternative surveillance use cases.

Collision Avoidance↗
NASA NTRS2009

The International Space Station and the Space Debris Environment: 10 Years On

For just over a decade the International Space Station (ISS), the most heavily protected vehicle in Earth orbit, has weathered the space debris environment well. Numerous hypervelocity impact features on the surface of ISS caused by small orbital debris and meteoroids have been observed. In addition to typical impacts seen on the large solar arrays, craters have been discovered on windows, hand rails, thermal blankets, radiators, and even a visiting logistics module. None of these impacts have resulted in any degradation of the operation or mission of the ISS. Validating the rate of small particle impacts on the ISS as predicted by space debris environment models is extremely complex. First, the ISS has been an evolving structure, from its original 20 metric tons to nearly 300 metric tons (excluding logistics vehicles) ten years later. Hence, the anticipated space debris impact rate has grown with the increasing size of ISS. Secondly, a comprehensive visual or photographic examination of the complete exterior of ISS has never been accomplished. In fact, most impact features have been discovered serendipitously. Further complications include the estimation of the size of an impacting particle without knowing its mass, velocity, and angle of impact and the effect of shadowing by some ISS components. Inadvertently and deliberately, the ISS has also been the source of space debris. The U.S. Space Surveillance Network officially cataloged 65 debris from ISS from November 1998 to November 2008: from lost cameras, sockets, and tool bags to intentionally discarded equipment and an old space suit. Fortunately, the majority of these objects fall back to Earth quickly with an average orbital lifetime of less than two months and a maximum orbital lifetime of a little more than 15 months. The cumulative total number of debris object-years is almost exactly 10, the equivalent of one piece of debris remaining in orbit for 10 years. An unknown number of debris too small to be tracked and cataloged have also been generated, but normally with even shorter orbital lifetimes. Finally, eight collision avoidance maneuvers have been performed to avoid potential collisions between ISS and large, tracked space debris. The most recent such maneuver was accomplished by ESA's Automated Transfer Vehicle, the Jules Verne, just three months before the 10th anniversary of the launch of ISS's first element.

Johnson, Nicholas↗
NASA NTRS2018

A Concept for Civil Space Traffic Management

As technology has improved, operators have sought to use cubesats, as well as smallsats more generally, to perform increasingly more ambitious and sophisticated functions. Despite this, practical concerns associated with cubesat infant mortality, conjunctions, limited maneuverability, and debris generation have been relatively muted because most cubesats have been launched to lower orbits that limit both their orbital lifetime and consequences should a collision occur. NASA ARC has developed a concept for a highly-automated and distributed space traffic management (STM) architecture, drawing on similar work done to provide traffic management for small unmanned aerial systems (UAS) operating at low altitudes. The system proposes a strategy to accommodate growing space traffic volume safely, as well as pave the way for a transition of civil STM authority to a civilian governmental entity. The architecture envisions an open-access software platform architecture of data and service suppliers, consumers, and regulators, connected via a set of application programming interfaces (APIs). The platform would build on, rather than replicate existing integration and coordination efforts within the space situational awareness ecosystem, using existing standards for data message formats from organizations like the Consultative Committee for Space Data Systems and wrapping, rather than replacing existing integrations. We will present an initial STM architecture in this presentation, with a few examples showing how stakeholders can interact structurally, but flexibly, within this architecture.

Space Situational Awareness↗
NASA NTRS2016

Certification Strategies using Run-Time Safety Assurance for Part 23 Autopilot Systems

Part 23 aircraft operation, and in particular general aviation, is relatively unsafe when compared to other common forms of vehicle travel. Currently, there exists technologies that could increase safety statistics for these aircraft; however, the high burden and cost of performing the requisite safety critical certification processes for these systems limits their proliferation. For this reason, many entities, including the Federal Aviation Administration, NASA, and the US Air Force, are considering new options for certification for technologies that will improve aircraft safety. Of particular interest, are low cost autopilot systems for general aviation aircraft, as these systems have the potential to positively and significantly affect safety statistics. This paper proposes new systems and techniques, leveraging run-time verification, for the assurance of general aviation autopilot systems, which would be used to supplement the current certification process and provide a viable path for near-term low-cost implementation. In addition, discussions on preliminary experimentation and building the assurance case for a system, based on these principles, is provided.

automatic collision avoidance↗
NASA NTRSDate not supplied

Clutter Assessment for an Autonomous Multi-Agent Search Mission

This paper presents a method for evaluating the amount of clutter in a region where autonomous vehicles in a multi-agent system must operate based on LIDAR point cloud measurements. The point cloud is used to generate an occupancy grid which is then projected onto a 2D plane of vehicle motion, constituting an image. A series of Gaussian radial basis functions (GRBFs) is created, each centered at an occupied pixel in a 2D image, and summed together to form the clutter field. The clutter field is a representation of the density and permeability of the space at each coordinate. The clutter field is then approximated such that iso-clutter contours are simple geometric objects so that intelligent machine assets can easily query the distance between them and any given point in an environment. In this way, agents are able to determine whether to enter into or steer away from areas of interest. Each vehicle has a clutter threshold representing the clutter value of the space in which it can safely maneuver. The iso-clutter contour corresponding to a vehicle’s clutter threshold is treated as the boundary of an obstacle to be avoided. A simulation is presented where a multi-agent system is tasked with persistent observation of a cluttered area. Each vehicle in the simulation has a different clutter threshold. The vehicles use a potential field-based guidance algorithm, and an allocation of vehicles to specific regions of the space emerges.

multi-agent↗
NASA NTRS2004

Future of Fuel Savings

Using automation to free up controllers for more strategic management of air traffic is one approach being studied by NASA as it seeks to boost airspace system capacity and efficiency, thereby saving fuel. Heinz Erzberger, a NASA Ames Research Center senior scientist, says the Advanced Airspace Concept (AAC) has been studied for several years. It could increase efficiency 15% by providing optimal routes that cut airlines direct operating costs. A 25% increase in landings on existing runways could follow an important benefit. AAC is one of the efforts to be reviewed by the Joint Planning and Development Organization, an FAA-led initiative by six federal agencies to redesign the U.S. air transportation system by 2025. The main goal is to triple air traffic capacity within 20 years to avert the sort of gridlock that would make fuel consumption only one of many travel nightmares. The automated system approach would allow aircraft to fly optimal trajectories. A trajectory would be defined in the standard three dimensions and eventually include the fourth, time. The management of air traffic by the data-linked exchange of trajectories would start at high altitude and eventually move down to lower altitudes. The automated concept is an outgrowth of the type of tools developed by NASA for use by FAA controllers in managing traffic flows over the years, including ones that optimize routings for the best fuel burn. But AAC would push automation further to reduce workload so controllers can focus on "solving strategic control problems, managing traffic flow during changing weather and ... other unusal events." One key component, the automated trajectory server (ATS), is a ground systems that would rely on software to manage flight path requests from aircrews and controllers. But, Erzberger acknowledges, "The FAA's current plan for upgrades to air traffic services does not include [allowing] the future ground system to issue separation-critical clearances of trajectory changes autonomously to aircraft via data link without explicit approval of a controller," as the AAC proposes. The AAC enables pilots or controllers to data link requests for a trajectory change to the ATS for approval after they are deconflicted with the paths of other aircraft. To divert around storms, for example, pilots could data link their trajectory preference to the ATS. Since several aircraft might request similar routes, the computer would then have to suggest alternatives. This could be accomplished without pilot-controller radio calls, a big bottleneck now. The ATS would have a built-in conflict monitor to call for a resolution (turn, climb or descend), when loss of separation is likely in 1-20 min. The AAC system would reduce controller errors by 90%, according to NASA Ames estimates. The AAC would have a back-up program to assure separation-Tactical Separation Assurance (TSAFE). It s designed to detect short-term traffic conflicts within 3-4 min. of loss of separation. The last line of defense would still be provided by traffic alert & collision avoidance systems (TCAS).

Hughes, David↗
NASA NTRSDate not supplied

Decision Aid for Conjunction Risk Mitigation by Differential Drag

In the previous five years, the rate of conjunctions that the NASA Conjunction Assessment Risk Analysis (CARA) team processed and analyzed has more than tripled. (NASA CARA, 2024) New missions in the early development phases are now required to plan for dealing with conjunctions under the present space environment, and also projecting forward into a future likely with even further increased utilization of the space environment. Some missions are investigating the possibility of using differential drag to remediate conjunctions without expending limited fuel or for missions without propulsive capabilities. The NASA CARA team studied the historical record of conjunctions to evaluate the circumstances under which differential drag may be successfully applied and have developed a series of tables to use as a decision aid for missions considering differential drag. Currently, if a CARA-protected mission with maneuvering capabilities is predicted to have a conjunction with probability of collision (Pc) greater than 7E-5 (the default value of the ‘yellow threshold’, which may have some other value agreed by CARA and the mission during the Orbital Collison Avoidance Planning (OCAP) process), CARA will use its Maneuver Trade Space (MTS) tool to evaluate and recommend options for the timing and magnitude of a risk mitigation maneuver (RMM), based on the mission’s capabilities. If the conjunction’s Pc is greater than 1E-4, the ‘red threshold’, then an RMM must be executed per NASA Procedural Requirements (NPR) 8079.1 (NASA, 2023), although missions may execute an RMM even if the Pc is lower. The magnitude of the maneuver is typically a few cm/s, and CARA estimates how many will be required for the mission’s nominal lifetime – typically a few per year – during the OCAP process, to inform the mission’s delta-V requirement. For traditional satellites, this is usually smaller than other requirements for orbit insertion, maintenance, and disposal, but for CubeSats or other small satellite missions, a propulsion system may not provide much more than a few cm/s of delta-V or may not fit at all within the available budget of money, time, size, weight, and/or power (SWaP). Conversely, CubeSats often have deployable solar panels, which offer the capacity to have much higher areas facing some directions than others. Such a mission can instead use ‘differential drag’ to remediate a conjunction -- in other words, change its drag area (usually increasing) to deviate from the predicted collision course. This is how Planet’s Dove spacecraft maintain their formations and remediate conjunction risks without having on-board propulsion (Foster, et al., 2017) (Griffith, et al., 2021). CARA has been developing improvements to MTS to support differential-drag for NASA's missions -- where it is effective. CARA records all conjunctions of their protected payloads, with historical records starting in 2005 (with significant conjunction events starting to occur on or after 2013). From this record, approximately 7,300 had a Pc greater than 1E-4 at 3 days prior to the time of closest approach, the time analyzed for differential drag efficacy. Of those, approximately 4,300 had fully-defined covariance matrices stored for both the primary and secondary objects; this set of conjunctions is the basis for the analysis of this work. CARA’s MTS tool was used to propagate the primary satellite forward from that decision point with varying degrees of increase to ballistic coefficient (BC). Because these conjunctions came from multiple missions, the nondimensional ‘delta-BC’ factor was used to quantify and normalize the increase in ballistic coefficient, defined as follows: Delta-BC = BC_new / BC_old - 1 Positive delta-BC factors represent an increase in drag compared to the nominal attitude, while negative delta-BC factors (to a minimum of -1) represent a decrease in drag. At the conclusion of the differential-drag ‘maneuver’, the Pc was recalculated to evaluate whether or not the conjunction was mitigated (Pc < 3E-6). These results were then binned and sorted along several axes, including altitude, amount of delta-BC, and (pre-maneuver) rate of energy dissipation (EDR), to identify underlying patterns. The altitude plot is shown in Figure 1. To validate this analysis, we consulted the record of a NASA mission which uses differential drag to maintain its orbit and remediate conjunction risk. CARA’s empirical record of the mission’s orbit history suggests it achieves a delta-BC of 2.2. Of the twenty-one RMM plans that were submitted by this mission, eighteen were matched with conjunctions in the historical record; of those, twelve were successfully remediated (final measured Pc < 3E-6), and six were not. This is consistent with the expected efficacy for missions orbiting at that altitude. We are presently simulating this mission’s RMMs with MTS; this work is ongoing, but so far, the MTS results are qualitatively in agreement with the empirical results -- correctly predicting that a maneuver would or would not remediate a conjunction, if not exactly matching the final post-remediation Pc value. We found that differential drag was most successful for satellites with perigees below 560 km, and which could adopt an average delta-BC of 2 or greater (that is, increasing their ballistic coefficient by a factor of 3). However, this is a difficult threshold for a mission to clear; very few spacecraft are capable of adopting a high-drag configuration for 72 hours continuously. Planet’s Dove spacecraft use differential drag to remediate conjunctions (Griffith, et al., 2021), and they have a maximum delta-BC factor of 9, but in practice (with mission and charging constraints) they achieve a time-averaged delta-BC that is closer to 2 (Foster, et al., 2017). A mission’s differential drag utility strongly depends on the operational constraints that has the capacity to limit the time-averaged delta-BC. A mission with a high maximum delta-BC of 5 or more can have an effective delta-BC of less than 1 due to operational constraints such as instrument and solar panel pointing, especially if this constraint results in holding an intermediate drag value for most of its orbit. CARA has developed tables that can be used as decision aids to advise missions-in-development about the best way to utilize their differential drag capabilities. For missions below 560 km with the operational flexibility to devote multiple days to holding a high-drag configuration (or a sufficiently high drag ratio to compensate for limitations on that time), they are -- more likely than not -- able to successfully remediate high-risk conjunctions. Conversely, missions that do not meet these exacting criteria -- most missions -- can instead be advised to use on-board propulsion systems to perform RMMs, or to turn their minimum-area face towards the approach vector, thereby reducing Pc at the moment of conjunction due to the decreased Hard-Body Radius (HBR), that is a strongly correlated variable in the Pc calculations. (NASA, 2023)

conjunction assessment↗