Search NASA⌕ Search

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.

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

At least 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
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 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

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 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.↗
NASA NTRS2022

Trajectory Specification Applied to Terminal Airspace

Despite major efforts to automate air traffic control (ATC), it is still performed by humans today. The complexity and safety-criticality of ATC makes it very difficult to safely automate, but it must be automated to increase airspace capacity (the density of traffic that can be safely managed) and airport throughput (the number of arrivals and departures that an airport can safely handle in a given period of time) beyond what is possible with human controllers. This paper presents the Trajectory Specification (TS) concept, which can help to safely automate ATC. TS is a method of specifying aircraft trajectories such that the position at any given time in flight is restricted to a precisely defined bounding space, removing all ambiguity as to where the flight is allowed to be. The bounding space or volume is determined by tolerances relative to a reference trajectory (position as a function of time). The tolerances are dynamic and are based on the aircraft navigation capabilities and the traffic situation. The tolerances can be a piecewise linear function of time or distance along the route, allowing the tolerances to vary as needed, typically increasing with time for departures and decreasing for arrivals. A Trajectory Specification Language (TSL) is proposed for communicating trajectories from aircraft to ATC as requests and from ATC to aircraft as assignments. The TS concept requires a new generation of airborne Flight Management Systems (FMS) that understand the TSL and can fly the assigned trajectories, but this paper focuses on the ATC functions and the prototype ATC algorithms and software that were developed to test the TS concept. Assuming conformance, TS can guarantee safe separation for an arbitrary length of time even in the event of an ATC system or communication outage. It can help to achieve the high level of safety and reliability needed for ATC automation, and it can also reduce the reliance on ATC backup systems for tactical conflict detection and resolution during normal operation. TS can be applied to any controlled airspace, including enroute, terminal, and urban airspace, but this paper presents algorithms and software for arrival spacing and conflict detection and resolution in the terminal airspace serving a major airport. In a fast-time simulation of a full day of traffic in a major terminal airspace, all conflicts were resolved in near real time, demonstrating the computational feasibility and the preliminary operational feasibility of the TS concept. This paper is a compilation of previous papers, and it adds significant information that was omitted from those papers due to length limitations. It also updates some of the results of those earlier papers due to algorithm refinements and corrections of minor software errors.

air traffic control, trajectory↗
NASA NTRS2009

Collision Avoidance for Airport Traffic Concept Evaluation

An initial Collision Avoidance for Airport Traffic (CAAT) concept for the Terminal Maneuvering Area (TMA) was evaluated in a simulation study at the National Aeronautics and Space Administration (NASA) Langley Research Center. CAAT is being designed to enhance surface situation awareness and provide cockpit alerts of potential conflicts during runway, taxi, and low altitude air-to-air operations. The purpose of the study was to evaluate the initial concept for an aircraft-based method of conflict detection and resolution (CD&R) in the TMA focusing on conflict detection algorithms and alerting display concepts. This paper gives an overview of the CD&R concept, simulation study, and test results.

Jones, Denise R.↗
NASA NTRS2016

Conducting Safe and Efficient Airport Surface Operations in a NextGen Environment

The Next Generation Air Transportation System (NextGen) vision proposes many revolutionary operational concepts, such as surface trajectory-based operations (STBO) and technologies, including 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 of a flight crew to conduct safe and efficient airport surface operations while utilizing an AMM. Position accuracy of traffic was varied, and the effect of traffic position accuracy on airport conflict detection and resolution (CD&R) capability was measured. Another goal was to evaluate the crew's ability to safely conduct STBO by assessing the impact of providing traffic intent information, CD&R system capability, and the display of STBO guidance to the flight crew on both head-down and head-up displays (HUD). 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 incidents were averted. During the STBO testing, the flight crews met their required time-of-arrival at route end within 10 seconds on 98 percent of the trials, well within the acceptable performance bounds of 15 seconds. Traffic intent information was found to be useful in determining the intent of conflicting traffic, with graphical presentation preferred. The CD&R system was only minimally effective during STBO because the prevailing visibility was sufficient for visual detection of conflicting traffic. Overall, the pilots indicated STBO increased general situation awareness but also negatively impacted workload, reduced the ability to watch for other traffic, and increased head-down time.

Jones, Denise R.↗
NASA NTRS2018

Air Traffic Management-eXploration Testbed for Urban Air Mobility Research and Development

The presentation will describe the architecture, current capabilities and some future enhancements of the testbed that is being developed at the National Aeronautics and Space Administration (NASA) to enable benefit, impact, safety and cost assessments for accelerating the deployment of air traffic management concept and technologies in the national airspace system. The testbed will support analysis of operational feasibility of urban air mobility operations, a part of NASA's Air Traffic Management eXploration project, and provide the data needed by regulatory agencies charged with public safety. Introduction of concepts and technologies, especially new concepts and technologies, is difficult and often takes decades because of the inability to assess the operational impact of the interaction between the proposed concept and technology and operationally deployed systems in terms of system-wide safety, traffic flow efficiency, roles and workload of controllers and traffic managers, and impact on airlines and other operators. To overcome these limitations, the testbed is developing infrastructure to enable mathematical modeling, human-in-the-loop evaluations and testing with operational systems in a simulated environment. In addition to the difficulty of establishing communications between geographically distributed systems, downloading/installing software, and management of startup, error-handling and shutdown, a major impediment for conducting simulations and human-in-the-loop testing with operational systems is the tedious manual scenario generation process. Several of these difficulties have been addressed in the current state of the testbed. The testbed can be described in terms of the following elements (1) web-based frontend and backend, (2) Testbed Builder, (3) Data Distribution Service, (4) Component Library, (5) Simulation Management, and (6) Scenario Generation. The web-based frontend and backend enable the user to interact with the testbed for tasks such as composing a simulation, running a simulation and retrieving output data. The Testbed Builder application launched from the web frontend is a graphical user interface for the user to drag-and-drop and connect predefined blocks for composing a simulation/scenario generation task. The Builder writes a set of instructions for Simulation Management based on the links between the blocks and the block properties such as the component (executable) associated with a particular block. Management of the distributed simulation is accomplished by Execution and Component Managers. Execution Manager interprets the instructions provided by the Builder to instruct the Component Managers to download components from the Component Library to specified computers and to start them up. Once started, the components communicate with each other by publishing messages and subscribing to messages that are delivered by the Data Distribution Service. The Scenario Generation capability can be used for creating traffic scenarios for Multi-Aircraft Control System, which has been used extensively at NASA for human-in-the-loop-based concept evaluations. The presentation will provide a testbed enabled example scenario of Multi-Aircraft Control System based simulation in which the urban air mobility pilot using the conflict detection and resolution system would interact with the air traffic controllers for resolving conflicts with other aircraft during terminal area operations.

Testbed↗
NASA NTRS2018

Air Traffic Management-eXploration Testbed for Urban Air Mobility Research and Development

The presentation will describe the architecture, current capabilities and some future enhancements of the testbed that is being developed at the National Aeronautics and Space Administration (NASA) to enable benefit, impact, safety and cost assessments for accelerating the deployment of air traffic management concept and technologies in the national airspace system. The testbed will support analysis of operational feasibility of urban air mobility operations, a part of NASA's Air Traffic Management eXploration project, and provide the data needed by regulatory agencies charged with public safety. Introduction of concepts and technologies, especially new concepts and technologies, is difficult and often takes decades because of the inability to assess the operational impact of the interaction between the proposed concept and technology and operationally deployed systems in terms of system-wide safety, traffic flow efficiency, roles and workload of controllers and traffic managers, and impact on airlines and other operators. To overcome these limitations, the testbed is developing infrastructure to enable mathematical modeling, human-in-the-loop evaluations and testing with operational systems in a simulated environment. In addition to the difficulty of establishing communications between geographically distributed systems, downloading/installing software, and management of startup, error-handling and shutdown, a major impediment for conducting simulations and human-in-the-loop testing with operational systems is the tedious manual scenario generation process. Several of these difficulties have been addressed in the current state of the testbed. The testbed can be described in terms of the following elements- (1) web-based frontend and backend, (2) Testbed Builder, (3) Data Distribution Service, (4) Component Library, (5) Simulation Management, and (6) Scenario Generation. The web-based frontend and backend enable the user to interact with the testbed for tasks such as composing a simulation, running a simulation and retrieving output data. The Testbed Builder application launched from the web frontend is a graphical user interface for the user to drag-and-drop and connect predefined blocks for composing a simulation/scenario generation task. The Builder writes a set of instructions for Simulation Management based on the links between the blocks and the block properties such as the component (executable) associated with a particular block. Management of the distributed simulation is accomplished by Execution and Component Managers. Execution Manager interprets the instructions provided by the Builder to instruct the Component Managers to download components from the Component Library to specified computers and to start them up. Once started, the components communicate with each other by publishing messages and subscribing to messages that are delivered by the Data Distribution Service. The Scenario Generation capability can be used for creating traffic scenarios for Multi-Aircraft Control System, which has been used extensively at NASA for human-in-the-loop-based concept evaluations. The presentation will provide a testbed enabled example scenario of Multi-Aircraft Control System based simulation in which the urban air mobility pilot using the conflict detection and resolution system would interact with the air traffic controllers for resolving conflicts with other aircraft during terminal area operations.

Simulation↗
NASA NTRS2005

KB3D Reference Manual

This paper is a reference manual describing the implementation of the KB3D conflict detection and resolution algorithm. The algorithm has been implemented in the Java and C++ programming languages. The reference manual gives a short overview of the detection and resolution functions, the structural implementation of the program, inputs and outputs to the program, and describes how the program is used. Inputs to the program can be rectangular coordinates or geodesic coordinates. The reference manual also gives examples of conflict scenarios and the resolution outputs the program produces.

Munoz, Cesar↗
NASA NTRS1982

Power, thermal, and attitude control design interactions of the CCE/AMPTE spacecraft

The power, thermal and attitude control interactions of the CCE spacecraft and the design compromises resulting from these interactions are described. These compromises result from the conflict between the plane change maneuver requirements and the final on station requirements. The resolution of these conflicts to arrive at an acceptable final design, is given and the resulting power, thermal and attitude control systems are described in some detail.

Wingate, C. A., Jr.↗
NASA NTRS2003

Airborne Conflict Management within Confined Airspace in a Piloted Simulation of DAG-TM Autonomous Aircraft Operations

A human-in-the-loop experiment was performed at the NASA Langley Research Center to study the feasibility of Distributed Air/Ground Traffic Management (DAG-TM) autonomous aircraft operations in highly constrained airspace. The airspace was constrained by a pair of special use airspace (SUA) regions on either side of the pilot s planned route. The available airspace was further varied by changing the separation standard for lateral separation between 3 nm and 5 nm. The pilot had to maneuver through the corridor between the SUA s, avoid other traffic and meet flow management constraints. Traffic flow management (TFM) constraints were imposed as a required time of arrival and crossing altitude at an en route fix. This is a follow-up study to work presented at the 4th USA/Europe Air Traffic Management R&D Seminar in December 2001. Nearly all of the pilots were able to meet their TFM constraints while maintaining adequate separation from other traffic. In only 3 out of 59 runs were the pilots unable to meet their required time of arrival. Two loss of separation cases are studied and it is found that the pilots need conflict prevention information presented in a clearer manner. No degradation of performance or safety was seen between the wide and narrow corridors. Although this was not a thorough study of the consequences of reducing the en route lateral separation, nothing was found that would refute the feasibility of reducing the separation requirement from 5 nm to 3 nm. The creation of additional, second-generation conflicts is also investigated. Two resolution methods were offered to the pilots: strategic and tactical. The strategic method is a closed-loop alteration to the Flight Management System (FMS) active route that considers other traffic as well as TFM constraints. The tactical resolutions are short-term resolutions that leave avoiding other traffic conflicts and meeting the TFM constraints to the pilot. Those that made use of the strategic tools avoided additional conflicts, whereas, those making tactical maneuvers often caused additional conflicts. Many of these second-generation conflicts could be avoided by improved conflict prevention tools that clearly present to the pilot which maneuver choices will result in a conflict-free path. These results, together with previously reported studies, continue to support the feasibility of autonomous aircraft operations.

Barmore, Bryan↗
NASA NTRS2014

Safely Conducting Airport Surface Trajectory-Based Operations

A piloted simulation study was conducted at the National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) to evaluate the ability to safely conduct surface trajectory-based operations (STBO) by assessing the impact of providing traffic intent information, conflict detection and resolution (CD&R) system capability, and the display of STBO guidance to the flight crew on both head-down and head-up displays (HUD). Nominal and off-nominal conflict scenarios were conducted using 12 airline crews operating in a simulated Memphis International Airport terminal environment. The flight crews met their required time-of-arrival at route end within 10 seconds on 98 percent of the trials, well within the acceptable performance bounds of 15 seconds. Traffic intent information was found to be useful in determining the intent of conflict traffic, with graphical presentation preferred. The CD&R system was only minimally effective during STBO because the prevailing visibility was sufficient for visual detection of incurring traffic. Overall, the pilots indicated STBO increased general situation awareness but also negatively impacted workload, reduced the ability to watch for other traffic, and increased head-down time.

Jones, Denise R.↗