SEARCH · Search NASA

Results for “conflict resolution”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 163 records · Page 9

All sources NASA NTRS DOE OSTI

NASA NTRS2021

Strategic and Tactical Functions in an Autonomous Air Traffic Management System

This paper evaluates, by means of fast-time simulation, performance of a candidate system for autonomous air traffic management. Advancing towards autonomy in air traffic management may be necessary in order for new air vehicle types such as electric Vertical Take Off and Landing (eVTOL) to operate safely and efficiently in airspace shared with conventional traffic. To account for uncertain prediction, autonomous air traffic management was divided into two integrated and coordinated subsystems: strategic scheduling, performed at predeparture, and tactical conflict detection and resolution, performed throughout the flight. The conflict detection and resolution subsystem contained a second tactical scheduling function that applied to flights operating in the airspace near the destination airport. This paper compares and contrasts the two subsystems and uses fast-time simulation to demonstrate the comparisons. A scenario of 54 flights inbound to Newark Liberty International Airport was simulated multiple times with different parameters. The scenario was created using flight plans recorded from the National Airspace System on a low weather, average traffic day in April 2018. Whereas the routes were not changed, the departure times of the flights were modified to increase arrival rates at the Newark runway and arrival meter fixes. Results of the simulations showed that the autonomous air traffic management system was able to safely manage the traffic, even with prediction uncertainty. In addition, they showed the importance of including flight holding maneuvers, in addition to path stretching, in conflict detection and resolution and of coordinating strategic and tactical scheduling. Finally, a tradeoff between absorbing the delay calculated by strategic scheduling on the ground versus in the air showed that taking most of the delay on the ground is cost effective for a simple idealized cost function. However, taking a little of the delay in the air prevented throughput on the runway from dropping for short periods due to trajectory prediction uncertainty.

air traffic control↗

NASA NTRS1997

Investigation of Alert Zone and Display Concepts for Free Flight

To better understand the potential benefits and drawbacks of utilizing a probability-based method, a number of alternative approaches to the collision avoidance problem were examined and summarized in the paper "Survey of Conflict Detection and Resolution Modeling Methods" which was presented in August 1997 at the AIAA Guidance, Navigation, and Control Conference. The paper provides a summary and comparative evaluation of the many different approaches that have been used in the past to perform conflict analysis. Each method is categorized in its dynamic modeling approach and method of handling conflict detection and conflict resolution. For example, one category included the extrapolation method used to predict future trajectories of which 3 were defined: nominal, probabilistic, and worst-case. Another category listed the metrics and parameters used by each method to make conflict decisions (i.e. estimated time to closest point of approach, miss distance, current separation, expected maneuvering cost, probability of conflict). Other useful information such as the ability to handle multi-aircraft conflicts and cooperative and non-cooperative maneuvering is also included.

Yang, Lee C.↗

NASA NTRS1999

En route Spacing Tool: Efficient Conflict-free Spacing to Flow-Restricted Airspace

This paper describes the Air Traffic Management (ATM) problem within the U.S. of flow-restricted en route airspace, an assessment of its impact on airspace users, and a set of near-term tools and procedures to resolve the problem. The FAA is committed, over the next few years, to deploy the first generation of modem ATM decision support tool (DST) technology under the Free-Flight Phase-1 (FFp1) program. The associated en route tools include the User Request Evaluation Tool (URET) and the Traffic Management Advisor (TMA). URET is an initial conflict probe (ICP) capability that assists controllers with the detection and resolution of conflicts in en route airspace. TMA orchestrates arrivals transitioning into high-density terminal airspace by providing controllers with scheduled times of arrival (STA) and delay feedback advisories to assist with STA conformance. However, these FFPl capabilities do not mitigate the en route Miles-In-Trail (MIT) restrictions that are dynamically applied to mitigate airspace congestion. National statistics indicate that en route facilities (Centers) apply Miles-In-Trail (MIT) restrictions for approximately 5000 hours per month. Based on results from this study, an estimated 45,000 flights are impacted by these restrictions each month. Current-day practices for implementing these restrictions result in additional controller workload and an economic impact of which the fuel penalty alone may approach several hundred dollars per flight. To mitigate much of the impact of these restrictions on users and controller workload, a DST and procedures are presented. The DST is based on a simple derivative of FFP1 technology that is designed to introduce a set of simple tools for flow-rate (spacing) conformance and integrate them with conflict-probe capabilities. The tool and associated algorithms are described based on a concept prototype implemented within the CTAS baseline in 1995. A traffic scenario is used to illustrate the controller's use of the tool, and potential display options are presented for future controller evaluation.

Green, S.↗

NASA NTRS1993

OMP-26 - An interactive scheduling tool for the 26 meter subnetwork

Operations Mission Planner for the 26 Meter (26M) Antenna Subnetwork (OMP-26) is an interactive scheduling tool developed by the Jet Propulsion Laboratory (JPL) to assist in allocating the Deep Space Network (DSN) 26M antennas to support Earth-orbiting Spacecraft (SC). Prior to integrating OMP-26 into the 26M scheduling arena, the text-based, labor-intensive task lacked the sufficient means to support the 1992 mission support increase. Therefore, JPL developed the OMP-26 interactive scheduling tool to automate the time consuming tasks of the existing, manual scheduling process. OMP-26 has addressed the scheduling dilemma by assisting schedulers to identify and resolve conflicts more quickly through its graphical display features and constraint-checking editing capability. Although OMP-26 has reduced the scheduler's existing workload by easing the identification and resolution of conflicts, it will not meet the needs of another mission support increase to occur by 1995. Therefore, future plans for OMP-26 involve transitioning from a solely interactive scheduling tool to one that is highly automated and more powerful.

Rosas, Jody L.↗

NASA NTRS2017

Efficient Planning of Wind-Optimal Routes in North Atlantic Oceanic Airspace

The North Atlantic oceanic airspace (NAT) is crossed daily by more than a thousand flights, which are greatly affected by strong jet stream air currents. Several studies devoted to generating wind-optimal (WO) aircraft trajectories in the NAT demonstrated great efficiency of such an approach for individual flights. However, because of the large separation norms imposed in the NAT, previously proposed WO trajectories induce a large number of potential conflicts. Much work has been done on strategic conflict detection and resolution (CDR) in the NAT. The work presented here extends previous methods and attempts to take advantage of the NAT traffic structure to simplify the problem and improve the results of CDR. Four approaches are studied in this work: 1) subdividing the existing CDR problem into sub-problems of smaller sizes, which are easier to handle; 2) more efficient data reorganization within the considered time period; 3) problem localization, i.e. concentrating the resolution effort in the most conflicted regions; 4) applying CDR to the pre-tactical decision horizon (a couple of hours in advance). Obtained results show that these methods efficiently resolve potential conflicts at the strategic and pre-tactical levels by keeping the resulting trajectories close to the initial WO ones.

Rodionova, Olga↗

NASA NTRS2012

Air traffic management evaluation tool

Methods for evaluating and implementing air traffic management tools and approaches for managing and avoiding an air traffic incident before the incident occurs. A first system receives parameters for flight plan configurations (e.g., initial fuel carried, flight route, flight route segments followed, flight altitude for a given flight route segment, aircraft velocity for each flight route segment, flight route ascent rate, flight route descent route, flight departure site, flight departure time, flight arrival time, flight destination site and/or alternate flight destination site), flight plan schedule, expected weather along each flight route segment, aircraft specifics, airspace (altitude) bounds for each flight route segment, navigational aids available. The invention provides flight plan routing and direct routing or wind optimal routing, using great circle navigation and spherical Earth geometry. The invention provides for aircraft dynamics effects, such as wind effects at each altitude, altitude changes, airspeed changes and aircraft turns to provide predictions of aircraft trajectory (and, optionally, aircraft fuel use). A second system provides several aviation applications using the first system. Several classes of potential incidents are analyzed and averted, by appropriate change en route of one or more parameters in the flight plan configuration, as provided by a conflict detection and resolution module and/or traffic flow management modules. These applications include conflict detection and resolution, miles-in trail or minutes-in-trail aircraft separation, flight arrival management, flight re-routing, weather prediction and analysis and interpolation of weather variables based upon sparse measurements. The invention combines these features to provide an aircraft monitoring system and an aircraft user system that interact and negotiate changes with each other.

Sridhar, Banavar↗

NASA NTRS2014

Effect of Traffic Position Accuracy for Conducting Safe Airport Surface Operations

The Next Generation Air Transportation System (NextGen) concept proposes many revolutionary operational concepts and technologies, such as display of traffic information and movements, airport moving maps (AMM), and proactive alerts of runway incursions and surface traffic conflicts, to deliver an overall increase in system capacity and safety. A piloted simulation study was conducted at the National Aeronautics and Space Administration (NASA) Langley Research Center to evaluate the ability to conduct safe and efficient airport surface operations while utilizing an AMM displaying traffic of various position accuracies as well as the effect of traffic position accuracy on airport conflict detection and resolution (CD&R) capability. Nominal scenarios and off-nominal conflict scenarios were conducted using 12 airline crews operating in a simulated Memphis International Airport terminal environment. The data suggest that all traffic should be shown on the airport moving map, whether qualified or unqualified, and conflict detection and resolution technologies provide significant safety benefits. Despite the presence of traffic information on the map, collisions or near collisions still occurred; when indications or alerts were generated in these same scenarios, the incidences were averted.

Jones, Denise R.↗

NASA NTRS2016

Defining the Collision Avoidance Region for DAA Systems

Unmanned aircraft systems (UAS) will be required to equip with a detect-‐and-‐avoid (DAA) system in order to satisfy the federal aviation regulations to maintain well clear of other aircraft, some of which may be equipped with a Traffic Collision Avoidance System (TCAS) to mitigate the possibility of mid-‐air collisions. As such, the minimum operational performance standards (MOPS) for UAS DAA systems are being designed with TCAS interoperability in mind by a group of industry, government, and academic institutions named RTCA Special Committee-228 (SC-228). This document will discuss the development of the spatial-‐temporal volume known as the collision avoidance region in which the DAA system is not allowed to provide vertical guidance to maintain or regain DAA well clear that could conflict with resolution advisories (RAs) issued by the intruder aircraft's TCAS system. Three collision avoidance region definition candidates were developed based on the existing TCAS RA and DAA alerting definitions. They were evaluated against each other in terms of their interoperability with TCAS RAs and DAA alerts in an unmitigated factorial encounter analysis of 1.3 million simulated pairs.

collision avoidance region↗

NASA NTRS1991

Distributed scheduling with COMPASS

COMPASS (COMPuter Aided Scheduling System) is a sophisticated, interactive scheduling tool used within NASA. Like most existing tools, however, COMPASS is a single-user application. There is a large class of scheduling problems which may be better solved by allowing several people at various locations to build separate schedules with shared resources. DISCORS (DIStributed COmputer Resource Scheduling) is a set of services which support a distributed version of COMPASS. This architecture naturally accommodates the integration of user-defined resource models without modifying COMPASS. DISCORS services include the ability to establish and manage communications, to code messages in efficient formats, to provide fault detection and recovery, and to configure schedulers across a network. In its present form, DISCORS effectively supports distributed COMPASS, but fails to run fast and to guarantee efficient schedules. Further enhancements may allow several users to simultaneously and interactively work together to create complex schedules while COMPASS detects and coordinates the resolution of conflicting requests.

Rufat-Latre, Jorge↗

NASA NTRS2006

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and Their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative a requirement to standardize and control the naming conventions of very disparate systems and technologies are emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation Initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation Initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and birds of a feather activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another

Bradford, Robert N.↗

NASA NTRS2006

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative, a requirement to standardize and control the naming conventions of very disparate systems and technologies is emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and Birds of a Feather (BoF) activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another standards body or technologies that are currently not standardized. For activities one through three, we will provide the analysis by either discipline or technology with rationale, identification and brief description of requirements and precedence. For activity four, we will provide a list of current standards bodies e.g. IETF and a list of potential candidates.

Bradford, Robert N.↗

NASA NTRS1994

The Corps Battle Simulaton: Remodeling the Model for New Missions

During the mid 1980's the U. S. Army established the Corps Battle Simulation (CBS) as a standard tool for training commanders and their staffs.

Low Intensity Conflict Resolution Detailing multi-↗

NASA NTRS2006

NASA Tech Briefs, September 2006

Topics covered include: Improving Thermomechanical Properties of SiC/SiC Composites; Aerogel/Particle Composites for Thermoelectric Devices; Patches for Repairing Ceramics and Ceramic- Matrix Composites; Lower-Conductivity Ceramic Materials for Thermal-Barrier Coatings; An Alternative for Emergency Preemption of Traffic Lights; Vehicle Transponder for Preemption of Traffic Lights; Automated Announcements of Approaching Emergency Vehicles; Intersection Monitor for Traffic-Light-Preemption System; Full-Duplex Digital Communication on a Single Laser Beam; Stabilizing Microwave Frequency of a Photonic Oscillator; Microwave Oscillators Based on Nonlinear WGM Resonators; Pointing Reference Scheme for Free-Space Optical Communications Systems; High-Level Performance Modeling of SAR Systems; Spectral Analysis Tool 6.2 for Windows; Multi-Platform Avionics Simulator; Silicon-Based Optical Modulator with Ferroelectric Layer; Multiplexing Transducers Based on Tunnel-Diode Oscillators; Scheduling with Automated Resolution of Conflicts; Symbolic Constraint Maintenance Grid; Discerning Trends in Performance Across Multiple Events; Magnetic Field Solver; Computing for Aiming a Spaceborne Bistatic- Radar Transmitter; 4-Vinyl-1,3-Dioxolane-2-One as an Additive for Li-Ion Cells; Probabilistic Prediction of Lifetimes of Ceramic Parts; STRANAL-PMC Version 2.0; Micromechanics and Piezo Enhancements of HyperSizer; Single-Phase Rare-Earth Oxide/Aluminum Oxide Glasses; Tilt/Tip/Piston Manipulator with Base-Mounted Actuators; Measurement of Model Noise in a Hard-Wall Wind Tunnel; Loci-STREAM Version 0.9; The Synergistic Engineering Environment; Reconfigurable Software for Controlling Formation Flying; More About the Tetrahedral Unstructured Software System; Computing Flows Using Chimera and Unstructured Grids; Avoiding Obstructions in Aiming a High-Gain Antenna; Analyzing Aeroelastic Stability of a Tilt-Rotor Aircraft; Tracking Positions and Attitudes of Mars Rovers; Stochastic Evolutionary Algorithms for Planning Robot Paths; Compressible Flow Toolbox; Rapid Aeroelastic Analysis of Blade Flutter in Turbomachines; General Flow-Solver Code for Turbomachinery Applications; Code for Multiblock CFD and Heat-Transfer Computations; Rotating-Pump Design Code; Covering a Crucible with Metal Containing Channels; Repairing Fractured Bones by Use of Bioabsorbable Composites; Kalman Filter for Calibrating a Telescope Focal Plane; Electronic Absolute Cartesian Autocollimator; Fiber-Optic Gratings for Lidar Measurements of Water Vapor; Simulating Responses of Gravitational-Wave Instrumentation; SOFTC: A Software Correlator for VLBI; Progress in Computational Simulation of Earthquakes; Database of Properties of Meteors; Computing Spacecraft Solar-Cell Damage by Charged Particles; Thermal Model of a Current-Carrying Wire in a Vacuum; Program for Analyzing Flows in a Complex Network; Program Predicts Performance of Optical Parametric Oscillators; Processing TES Level-1B Data; Automated Camera Calibration; Tracking the Martian CO2 Polar Ice Caps in Infrared Images; Processing TES Level-2 Data; SmaggIce Version 1.8; Solving the Swath Segment Selection Problem; The Spatial Standard Observer; Less-Complex Method of Classifying MPSK; Improvement in Recursive Hierarchical Segmentation of Data; Using Heaps in Recursive Hierarchical Segmentation of Data; Tool for Statistical Analysis and Display of Landing Sites; Automated Assignment of Proposals to Reviewers; Array-Pattern-Match Compiler for Opportunistic Data Analysis; Pre-Processor for Compression of Multispectral Image Data; Compressing Image Data While Limiting the Effects of Data Losses; Flight Operations Analysis Tool; Improvement in Visual Target Tracking for a Mobile Robot; Software for Simulating Air Traffic; Automated Vectorization of Decision-Based Algorithms; Grayscale Optical Correlator Workbench; "One-Stop Shopping" for Ocean Remote-Sensing and Model Data; State Analysis Database Tool; Generating CAHV and CAHVOmages with Shadows in ROAMS; Improving UDP/IP Transmission Without Increasing Congestion; FORTRAN Versions of Reformulated HFGMC Codes; Program for Editing Spacecraft Command Sequences; Flight-Tested Prototype of BEAM Software; Mission Scenario Development Workbench; Marsviewer; Tool for Analysis and Reduction of Scientific Data; ASPEN Version 3.0; Secure Display of Space-Exploration Images; Digital Front End for Wide-Band VLBI Science Receiver; Multifunctional Tanks for Spacecraft; Lightweight, Segmented, Mostly Silicon Telescope Mirror; Assistant for Analyzing Tropical-Rain-Mapping Radar Data; and Anion-Intercalating Cathodes for High-Energy- Density Cells.

Source record↗

NASA NTRS2018

Airborne Trajectory Management for Urban Air Mobility

Urban Air Mobility (UAM) has captured the imagination of the public and the aviation industry for someday soon moving people and goods through and around metropolitan areas using Unmanned Aircraft Systems (UAS) that are electrically powered, environmentally friendly, and autonomously operated. Significant investment and rapid development of vehicles for this activity is taking place, with package delivery services already beginning in some areas. However, the ability to manage thousands of these vehicles safely in a congested urban area presents a challenge unprecedented in air traffic management. Initial studies of this problem led by NASA under the UAS Traffic Management (UTM) initiative have primarily focused on geo-fencing and centralized reservation of airspace for individual flights. This paper proposes an extension of UTM using a de-centralized approach employing airborne surveillance, self-separation, and a minimized “design separation” approach to permit the optimization and safety of each flight in very high traffic densities and close proximities. The concept employs Airborne Trajectory Management (ABTM) principles and a novel new concept for variable separation criteria to manage the angular velocity of a passing vehicle, thus eliminating the "startle factor" and perceived hazard of very close operations. ABTM also accomplishes most of the services required for safe planning and execution of normal flights and recovery from abnormal or emergency operations while accommodating conventional piloted flights using the current air traffic control paradigm. The environment for UAM operations is described along with the proposed means for autonomous, tactical separation of the vehicles. Sample geometries of traffic conflicts and resolutions are shown and the airspace definitions, rules for flight within them, and additions and exemptions to the rules for these flights are listed and explained.

Cotton, William↗

NASA NTRSDate not supplied

Detect-and-Avoid Maneuver Planning: Benefits of Including Route Recapture

Development of Detect-and-avoid (DAA) systems’ maneuver guidance requirements at RTCA has centered on tactical maneuvers away from the intruder. Recapturing the flight-plan route the initial maneuver is not directly taken into account by most DAA maneuver guidance algorithms. This work demonstrates potential challenges and inefficiencies that can arise in recapturing the route after resolving a conflict. Horizontal resolution trajectories for a test matrix of encounters with varying aircraft speeds and geometries are computed by minimizing either flight time or deviation to serve as a baseline. Turn directions computed from a reference DAA algorithm coupled with a pilot selection model and a second algorithm called Autoresolver (AR) are compared to these baseline resolution trajectories. Baseline results show that turning into the intruder yields favorable cost for most encounters. Additional analysis of pilot response data shows that only three-fourths of pilots’ horizontal maneuvers turn into intruders, a percentage much lower than the baseline results. Improvement to a DAA guidance algorithm based on findings in this work is discussed.

Route Recapture↗

NASA NTRSDate not supplied

Detect-and-Avoid Maneuver Planning: Benefits of Including Route Recapture

Route Recapture↗

NASA NTRS2014

A Closer Look at Automation Behavior During a Human-in-the-Loop Simulation

A 2012 Human-In-The-Loop air traffic control simulation investigated a gradual paradigm-shift in the allocation of functions between operators and automation. Air traffic controllers staffed five adjacent high-altitude en route sectors, and during the course of a two-week experiment, worked traffic under four different function allocation concepts aligned with increasingly mature NextGen operational environments. These NextGen time-frames ranged from near current-day operations to nearly fully-automated control, in which the ground systems automation was responsible for detecting conflicts, issuing strategic and tactical resolutions, and alerting controllers to exceptional circumstances. This paper continues the investigations reported in previous publications. Analyses of data surrounding the conflict-resolution task serve as the context in which we investigate the interactions between controllers and the automation.

Human-Automation Interaction↗

NASA NTRS2012

The Effects of Limited Intent Information Availability on Self-Separation in Mixed Operations

This paper presents the results of a computer simulation of the NASA Autonomous Flight Rules (AFR) concept for airborne self-separation in airspace shared with conventional Instrument Flight Rules (IFR) traffic. This study was designed to determine the impact of varying levels of intent information from IFR aircraft on the performance of AFR conflict detection and resolution. The study used Automatic Dependent Surveillance-Broadcast (ADS-B) to supply IFR intent, but other methods such as an uplink from a ground-based System Wide Information Management (SWIM) network could alternatively supply this information. The independent variables of the study consist of the number of ADS-B trajectory change reports broadcast by IFR aircraft and the time interval between those reports. The conflict detection and resolution metrics include: the number of conflicts and losses of separation, the average conflict warning time, and the amount of time spent in strategic vs. tactical flight modes (i.e., whether the autoflight system was decoupled from the planned route in the Flight Management System in order to respond to a short-notice traffic conflict). The results show a measurable benefit of broadcasting IFR intent vs. relying on state-only broadcasts. The results of this study will inform ongoing separation assurance research and FAA NextGen design decisions for the sharing of trajectory intent information in the National Airspace System.

Lewis, Timothy A.↗