SEARCH · Search NASA

Results for “Traffic Separation”

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 127 records · Page 7

All sources NASA NTRS DOE OSTI

NASA NTRS2011

Automated Air Traffic Control Operations with Weather and Time-Constraints: A First Look at (Simulated) Far-Term Control Room Operations

In this paper we discuss results from a recent high fidelity simulation of air traffic control operations with automated separation assurance in the presence of weather and time-constraints. We report findings from a human-in-the-loop study conducted in the Airspace Operations Laboratory (AOL) at the NASA Ames Research Center. During four afternoons in early 2010, fifteen active and recently retired air traffic controllers and supervisors controlled high levels of traffic in a highly automated environment during three-hour long scenarios, For each scenario, twelve air traffic controllers operated eight sector positions in two air traffic control areas and were supervised by three front line managers, Controllers worked one-hour shifts, were relieved by other controllers, took a 3D-minute break, and worked another one-hour shift. On average, twice today's traffic density was simulated with more than 2200 aircraft per traffic scenario. The scenarios were designed to create peaks and valleys in traffic density, growing and decaying convective weather areas, and expose controllers to heavy and light metering conditions. This design enabled an initial look at a broad spectrum of workload, challenge, boredom, and fatigue in an otherwise uncharted territory of future operations. In this paper we report human/system integration aspects, safety and efficiency results as well as airspace throughput, workload, and operational acceptability. We conclude that, with further refinements. air traffic control operations with ground-based automated separation assurance can be an effective and acceptable means to routinely provide very high traffic throughput in the en route airspace.

Prevot, Thomas↗

NASA NTRS2016

Air Traffic Controller Acceptability of Unmanned Aircraft System Detect-and-Avoid Thresholds

A human-in-the-loop experiment was conducted with 15 retired air traffic controllers to investigate two research questions: (a) what procedures are appropriate for the use of unmanned aircraft system (UAS) detect-and-avoid systems, and (b) how long in advance of a predicted close encounter should pilots request or execute a separation maneuver. The controller participants managed a busy Oakland air route traffic control sector with mixed commercial/general aviation and manned/UAS traffic, providing separation services, miles-in-trail restrictions and issuing traffic advisories. Controllers filled out post-scenario and post-simulation questionnaires, and metrics were collected on the acceptability of procedural options and temporal thresholds. The states of aircraft were also recorded when controllers issued traffic advisories. Subjective feedback indicated a strong preference for pilots to request maneuvers to remain well clear from intruder aircraft rather than deviate from their IFR clearance. Controllers also reported that maneuvering at 120 seconds until closest point of approach (CPA) was too early; maneuvers executed with less than 90 seconds until CPA were more acceptable. The magnitudes of the requested maneuvers were frequently judged to be too large, indicating a possible discrepancy between the quantitative UAS well clear standard and the one employed subjectively by manned pilots. The ranges between pairs of aircraft and the times to CPA at which traffic advisories were issued were used to construct empirical probability distributions of those metrics. Given these distributions, we propose that UAS pilots wait until an intruder aircraft is approximately 80 seconds to CPA or 6 nmi away before requesting a maneuver, and maneuver immediately if the intruder is within 60 seconds and 4 nmi. These thresholds should make the use of UAS detect and avoid systems compatible with current airspace procedures and controller expectations.

unmanned aircraft systems↗

NASA NTRS1972

Manual control theory applied to air traffic controller-pilot cooperation

Reduced runway separation standards are among the means which have been proposed for increasing airport capacity. The probability of a blunder will dominate the calculation of safe separation standards. Then the determinant of safe system performance will be the system reaction time comprised of the air traffic controller's detection, decision and communication delays, and the response times of the pilot and aircraft in executing a collision avoidance manuever. Estimates of these times, based on existing data, show that the delays ascribable to the human portions of the man-machine system are comparatively unimportant. New developments in radar, computers, and data links will be required to provide any substantial improvement of the existing system, and the goal of 2500 ft of separation may not be achievable.

Graham, D.↗

NASA NTRS2019

A Detect and Avoid System in the Context of Multiple-Unmanned Aircraft Systems Operations

NASA's Unmanned Aircraft Systems Integration into the National Airspace System (UAS in the NAS) project examines the technical barriers associated with the operation of UAS in civil airspace. For UAS, the removal of the pilot from onboard the aircraft has eliminated the ability of the ground-based pilot in command (PIC) to use out-the-window visual information to make judgements about a potential threat of a loss of well clear with another aircraft. NASA's Phase 1 research supported the development of a Detect and Avoid (DAA) system that supports the ground-based pilot's ability to detect potential traffic conflicts and determine a resolution maneuver, but existing display/alerting requirements did not account for multiple UAS control (1:N). Demands for increased scalability of UAS in the NAS operations are expected to create a need for simultaneous control of UAs, and thus, a new DAA HMI design will likely be necessary. Previous research, however, has found performance degradations as the number of vehicles under operator control has increased. The purpose of the current human-in-the-loop (HITL) simulation was to examine the viability of 1:N operations with the Phase 1 DAA alerting and guidance. Sixteen UAS pilots flew three scenarios with varying number of UAs under their control (1:1, 1:3, 1:5). In addition to their supervisory and sensor mission responsibilities, pilots were to utilize the DAA system to remain DAA well clear (DWC) during scripted conflicts of mixed severity. Measured response times, separation performance, mission task data, and subjective feedback were collected to assess how the multi-UAS control configuration impacted pilots' ability to maintain DAA well clear and perform the mission tasks. Overall, the DAA system proved surprisingly adaptive to multi-UAS control for preventing losses of DAA well clear (LoDWC). The findings suggest that, while multi-UAS operators are able to maintain safe separation (DWC) from other traffic, their ability to efficiently perform missions drastically decreases with their number of controlled vehicles. Pilot feedback indicated that, for this context, the use of automation support tools for completing and managing mission tasks would be appropriate and desired, especially for ensuring efficient use of assets. Finally, human-machine interface (HMI) design considerations for multi-UAS operations are discussed.

Monk, Kevin J.↗

NASA NTRS2003

Improved Conflict Detection for Reducing Operational Errors in Air Traffic Control

An operational error is an incident in which an air traffic controller allows the separation between two aircraft to fall below the minimum separation standard. The rates of such errors in the US have increased significantly over the past few years. This paper proposes new detection methods that can help correct this trend by improving on the performance of Conflict Alert, the existing software in the Host Computer System that is intended to detect and warn controllers of imminent conflicts. In addition to the usual trajectory based on the flight plan, a "dead-reckoning" trajectory (current velocity projection) is also generated for each aircraft and checked for conflicts. Filters for reducing common types of false alerts were implemented. The new detection methods were tested in three different ways. First, a simple flightpath command language was developed t o generate precisely controlled encounters for the purpose of testing the detection software. Second, written reports and tracking data were obtained for actual operational errors that occurred in the field, and these were "replayed" to test the new detection algorithms. Finally, the detection methods were used to shadow live traffic, and performance was analysed, particularly with regard to the false-alert rate. The results indicate that the new detection methods can provide timely warnings of imminent conflicts more consistently than Conflict Alert.

Paielli, Russell A.↗

NASA NTRS2010

Time of Closest Approach in Three-Dimensional Airspace

In air traffic management, the aircraft separation requirement is defined by a minimum horizontal distance and a minimum vertical distance that the aircraft have to maintain. Since this requirement defines a cylinder around each aircraft rather than a sphere, the three-dimensional Euclidean distance does not provide an appropriate basis for the definition of time of closest approach. For instance, conflicting aircraft are not necessarily in loss of separation at the time of closest three-dimensional Euclidean distance. This paper proposes a definition of time of closest approach that characterizes conflicts in a three-dimensional airspace. The proposed time is defined as the time that minimizes a distance metric called cylindrical norm. An algorithm that computes the time of closest approach between two aircraft is provided and the formal verification of its main properties is reported.

Munoz, Cesar A.↗

NASA NTRS2022

PAAV Concept Document

The Pathfinding for Airspace with Autonomous Vehicles (PAAV) Concept Document, version 1.0, lays out the key challenges and potential solutions for the use of uncrewed aircraft (UA) technology for future regional air cargo operations. The challenges and solutions described in this document were informed by communications with the UA industry community (e.g., RTCA, the Federal Aviation Administration, and regional air cargo business operators), as well as the PAAV team’s research activities during the last two years including four tabletop exercises, a human-in-the-loop simulation study, a numerical simulation study, a functional allocation study, and flight data analysis (Appendix A). This document first describes the expected operational context of PAAV (Section 2), such as the flight mission, baseline UAS components, nominal operations, m:N operations (i.e., "m" remote pilots per "N" aircraft), and off-nominal operations. This context sets the scope for the PAAV concept development work. PAAV concept development assumes that UA operations will be increasingly autonomous. Thus, near- and far-term assumptions are defined (Section 3). PAAV identified seven key challenges for UA operations (Section 4): - Flight route planning - Separation and flow management - Traffic pattern integration - Contingency management - Taxi, takeoff, and landing - m:N operations - Communications operations The following 13 potential solutions to these challenges are then described (Section 5): - Scalable communications architecture - Data link - Designated UAS corridors - Crew planning for m:N operations - Flight route optimization - Traffic load-level control - Trajectory solutions with data link - Automated hazard avoidance for m:N operations - Traffic pattern integration (TPI) tool - Standard lost command and control (C2) link (LC2L) procedures - Automated hazard avoidance under LC2L - Auto-taxi, auto-takeoff, and auto-land - Ground control station (GCS) user interface for m:N operations The document attempts to link each of these solutions to one or more of the challenge areas. Novel solutions involving numerous automation technologies are needed to mitigate traffic and airspace management challenges, especially for realizing m:N operations and ensuring safety under LC2L conditions. The purpose of this document is to help understand alternatives and tradeoffs among potential solutions and provide a foundation for a cohesive PAAV concept that will be described and refined in subsequent concept versions.

Unmanned aircraft, uncrewed aircraft, regional air↗

NASA NTRSDate not supplied

Traffic Prediction for Uncommunicative Aircraft in Terminal Airspace: Development Framework and Performance Evaluations

This paper presents an air traffic prediction algorithm that takes observations of an aircraft and classifies aircraft type, estimates the aircraft's intent to and method of joining an airport traffic pattern, and predicts the aircaft's future trajectory. To develop algorithms that enable autonomous aircraft to safely insert into un-towered traffic patterns, several challenges need to be addressed. These challenges range from traffic detection to sensor fusion to own-ship trajectory replanning. Critical to a trajectory replanning algorithm is information regarding the future behavior of all traffic aircraft in the operational environment. The presented traffic prediction algorithm generates this information using regular measurements of traffic aircraft position and velocity to classify the aircraft by speed-class, estimate how the aircraft will approach the runway, and construct a predicted trajectory to the runway including future positions and velocities at specific times. The predictions of the presented algorithm are the necessary inputs for any downstream traffic pattern sequencing and own-ship trajectory planning routines. The presented algorithm is benchmarked using approximately 300 randomized traffic trajectories, spanning four vehicle weight classes and eight traffic entry types. While the algorithm can process multiple traffic vehicles in the terminal area, there is no prediction of traffic-on-traffic interaction. Each traffic vehicle is processed separately.

John D McMinn↗

NASA NTRS2017

Management by Trajectory Trade Study of Roles and Responsibilities Between Participants and Automation Report

This report describes a trade study of roles and responsibilities associated with the Management by Trajectory (MBT) concept. The MBT concept describes roles, responsibilities, and information and automation requirements for providing air traffic controllers and managers the ability to quickly generate, evaluate and implement changes to an aircraft's trajectory. In addition, the MBT concept describes mechanisms for imposing constraints on flight operator preferred trajectories only to the extent necessary to maintain safe and efficient traffic flows, and the concept provides a method for the exchange of trajectory information between ground automation systems and the aircraft that allows for trajectory synchronization and trajectory negotiation. The participant roles considered in this trade study include: airline dispatcher, flight crew, radar controller, traffic manager, and Air Traffic Control System Command Center (ATCSCC) traffic management specialists. The proposed allocation of roles and responsibilities was based on analysis of several use cases that were developed for this purpose as well as for walking through concept elements. The resulting allocation of roles and responsibilities reflects both increased automation capability to support many aviation functions, as well as increased flexibility to assign responsibilities to different participants - in many cases afforded by the increased automation capabilities. Note that the selection of participants to consider for allocation of each function is necessarily rooted in the current environment, in that MBT is envisioned as an evolution of the National Airspace System (NAS), and not a revolution. A key feature of the MBT allocations is a vision for the traffic management specialist to take on a greater role. This is facilitated by the vision that separation management functions, in addition to traffic management functions, will be carried out as trajectory management functions. This creates an opportunity for flexibility, allowing the traffic management specialist to carry out tasks that today can only be carried out by the controller currently in contact with the aircraft. This additional tasking for the traffic management specialist comes with requirements for workload management. An increased role for the Data-side (D-side) controller relative to the Radar-side (R-side) controller is a potential approach to mitigating workload for the traffic management specialist, as the D-side controller would have similar ability to perform separation management functions in what today might be considered the "trajectory management" timeframe. This analysis did not distinguish between the D-side and R-side controllers since in many cases the R-side controller works unassisted.

Fernandes, Alicia D.↗

NASA NTRS1983

Simulation study of traffic-sensor noise effects on utilization of traffic situation display for self-spacing task

The effect of traffic sensor noise on the ability of a pilot to perform an intrail spacing task was determined. The tests were conducted in a fixed base cockpit simulator configured as a current generation transport aircraft, with an electronic traffic display provided in the weather radarscope location. The true positions of the traffic were perturbed in both relative range and azimuth by random errors to simulate traffic sensor noise associated with an onboard sensor. The evaluation task involved simulated instrument approaches into a terminal area while maintaining self separation on a lead aircraft. Separation performance data and pilot subjective ratings and comments were obtained. The results of the separation data indicate that displayed traffic position errors, having standard deviation values up to 0.3-n.mi. range and 8 deg azimuth, had negligible effect on the spacing performance achieved by the pilots. Speed profiles of the lead aircraft, display of the lead aircraft groundspeed, and individual pilot techniques were found to significantly affect the mean spacing performance.

Williams, D. H.↗

NASA NTRS2004

Trajectory Specification for High-Capacity Air Traffic Control

In the current air traffic management system, the fundamental limitation on airspace capacity is the cognitive ability of human air traffic controllers to maintain safe separation with high reliability. The doubling or tripling of airspace capacity that will be needed over the next couple of decades will require that tactical separation be at least partially automated. Standardized conflict-free four-dimensional trajectory assignment will be needed to accomplish that objective. A trajectory specification format based on the Extensible Markup Language is proposed for that purpose. This format can be used to downlink a trajectory request, which can then be checked on the ground for conflicts and approved or modified, if necessary, then uplinked as the assigned trajectory. The horizontal path is specified as a series of geodetic waypoints connected by great circles, and the great-circle segments are connected by turns of specified radius. Vertical profiles for climb and descent are specified as low-order polynomial functions of along-track position, which is itself specified as a function of time. Flight technical error tolerances in the along-track, cross-track, and vertical axes define a bounding space around the reference trajectory, and conformance will guarantee the required separation for a period of time known as the conflict time horizon. An important safety benefit of this regimen is that the traffic will be able to fly free of conflicts for at least several minutes even if all ground systems and the entire communication infrastructure fail. Periodic updates in the along-track axis will adjust for errors in the predicted along-track winds.

Paielli, Russell A.↗

NASA NTRS2015

PTM Along Track Algorithm to Maintain Spacing During Same Direction Pair-Wise Trajectory Management Operations

Pair-wise Trajectory Management (PTM) is a cockpit based delegated responsibility separation standard. When an air traffic service provider gives a PTM clearance to an aircraft and the flight crew accepts the clearance, the flight crew will maintain spacing and separation from a designated aircraft. A PTM along track algorithm will receive state information from the designated aircraft and from the own ship to produce speed guidance for the flight crew to maintain spacing and separation

Carreno, Victor A.↗

NASA NTRS1999

Pilot Performance on New ATM Operations: Maintaining In-Trail Separation and Arrival Sequencing

Cockpit Display of Traffic Information (CDTI) may enable new Air Traffic Management (ATM) operations. However, CDTI is not the only source of traffic information in the cockpit; ATM procedures may provide information, implicitly and explicitly, about other aircraft. An experiment investigated pilot ability to perform two new ATM operations - maintaining in-trail separation from another aircraft and sequencing into an arrival stream. In the experiment, pilots were provided different amounts of information from displays and procedures. The results are described.

Pritchett, Amy R.↗

NASA NTRS2015

National Air Space (NAS) Data Exchange Environment Through 2060

NASA's NextGen Concepts and Technology Development (CTD) Project focuses on capabilities to improve safety, capacity and efficiency of the National Air Space (NAS). In order to achieve those objectives, NASA sought industry-Government partnerships to research and identify solutions for traffic flow management, dynamic airspace configuration, separation assurance, super density operations, airport surface operations and similar forward-looking air-traffic modernization (ATM) concepts. Data exchanges over NAS being the key enabler for most of these ATM concepts, the Sub-Topic area 3 of the CTD project sought to identify technology candidates that can satisfy air-to-air and air/ground communications needs of the NAS in the year 2060 timeframe. Honeywell, under a two-year contract with NASA, is working on this communications technology research initiative. This report summarizes Honeywell's research conducted during the second year of the study task.

National Air Space↗

NASA NTRS1980

Evaluation of the potential format and content of a cockpit display of traffic information

The types and formats of information most suitable to be displayed in a cockpit display of traffic information (CDTI) are investigated. Twenty three airline pilots and 13 instrumentated general aviation pilots were asked to select from sets of symbols of various complexities incorporating various levels of information that would contain all information necessary for monitoring the traffic situation, detecting errors, maintaining separation and merging. Display features selected by a significant number of pilots were then evaluated for their capabilities in helping pilots to assess the lateral or vertical separation between their own and another aircraft in a dynamic simulation. It is found that while some of the features initially chosen by the pilots, such as flightpath predictors, aided the pilots in perceiving the traffic situation correctly, others, such as ground speed and climb/descend arrows and relative altitude encoding of symbols for other aircraft, did not contribute to improved performance speed or accuracy.

Hart, S. G.↗

NASA NTRS1980

Perception of aircraft separation with pilot-preferred symbology on a cockpit display of traffic information

The concept of a cockpit display of traffic information (CDTI) was developed for use in later full mission simulator evaluations of the CDTI concept. Pilots chose their preferred method of displaying air traffic information for several variables. Variables included: type of background, update rate, update type, predictor type, and history type. Each pilot designed a display he felt would be most useful in flight operations. After a series of test trials, each pilot was given the opportunity to modify the display for the experimental task. For a second day of testing, they repeated the experimental task using their display as well as displays chosen by other pilots. Results indicated a variety of individual preferences in symbology and differences in the accuracy of judgments. Pilots indicated concern for clutter of the display, relationship of the displayed symbology to physical reality, and a need to perceive the relative motion of the intruder aircraft. Analysis of data indicated that pilots were able to improve their performance with practice.

Oconnor, S.↗

NASA NTRS2011

Design and Evaluation of the Terminal Area Precision Scheduling and Spacing System

This paper describes the design, development and results from a high fidelity human-in-the-loop simulation of an integrated set of trajectory-based automation tools providing precision scheduling, sequencing and controller merging and spacing functions. These integrated functions are combined into a system called the Terminal Area Precision Scheduling and Spacing (TAPSS) system. It is a strategic and tactical planning tool that provides Traffic Management Coordinators, En Route and Terminal Radar Approach Control air traffic controllers the ability to efficiently optimize the arrival capacity of a demand-impacted airport while simultaneously enabling fuel-efficient descent procedures. The TAPSS system consists of four-dimensional trajectory prediction, arrival runway balancing, aircraft separation constraint-based scheduling, traffic flow visualization and trajectory-based advisories to assist controllers in efficient metering, sequencing and spacing. The TAPSS system was evaluated and compared to today's ATC operation through extensive series of human-in-the-loop simulations for arrival flows into the Los Angeles International Airport. The test conditions included the variation of aircraft demand from a baseline of today's capacity constrained periods through 5%, 10% and 20% increases. Performance data were collected for engineering and human factor analysis and compared with similar operations both with and without the TAPSS system. The engineering data indicate operations with the TAPSS show up to a 10% increase in airport throughput during capacity constrained periods while maintaining fuel-efficient aircraft descent profiles from cruise to landing.

Swenson, Harry N.↗

NASA NTRS2002

Examining the Pilot and Controller Performance Data When in a Free Flight with Weather Phenomenon

The present study investigated effects of weather related factors on the performance of pilots under free flight. A weather scenario was defined by a combination of precipitation factors (light rain, moderate rain, and heavy rain or snow), visibility (1,4,8 miles), wind conditions (light, medium, or heavy), cloud ceiling (800ft. below, 1800ft above, and 4000ft horizontal). The performance of the aircraft self-separation was evaluated in terms of detection accuracy and detection times for student- and commercial (expert) pilots. Overall, the results obtained from a behavioral analysis showed that in general, the ability to recognize intruder aircraft conflict incidents, followed by the ability to acquire the spatial location of the intruder aircraft relative to ownership aircraft were judged to be the major cognitive tasks as perceived by the participants during self-separation. Further, the participants rarely used cockpit display of traffic information (CDTI) during conflict management related to aircraft separation, but used CDTI highly during decision-making tasks. In all weather scenarios, there were remarkable differences between expert and student pilots in detection times. In summary, weather scenarios were observed to affect intruder aircraft detection performance accuracies. There was interaction effects between weather Scenario-1 and Scenario-2 for climbing task data generated by both expert- and student- pilots at high traffic density. Scenario-3 weather condition provided an opportunity for poor detection accuracy as well as detection time increase. This may be attributed to low visibility. The intruder aircraft detection times were not affected by the weather conditions during climbing and descending tasks. The decision of pilots to fly into certain weather condition was dependent in part on the warning distance to the location of the weather. When pilots were warned of the weather conditions, they were more likely to fly their aircraft into it, but mostly when the warning was not close to the weather location.

Nituen, Celestine A.↗