Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “air traffic control, trajectory”

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 19 records

Trajectory Specification Language for Air Traffic Control

Trajectory Specification is a method of specifying aircraft trajectories with tolerances such that the position at any instant in time is constrained to a precisely defined bounding space. The bounding space at any instant in time is defined by tolerances relative to a reference trajectory that specifies position as a function of time. The tolerances are dynamic and are based on the aircraft navigation capabilities and the traffic situation. This paper proposes a standard Trajectory Specification Language (TSL) based on the Extensible Markup Language (XML) to represent these specifications and to communicate them by datalink. The language can be used to downlink trajectory requests from air to ground and to uplink trajectory assignments from ground to air. The XML format can be converted to binary for operational use, if necessary, using Efficient XML Interchange (EXI) or Abstract Syntax Notation (ASN.1).

XM↗

Trajectory Specification for Automation of Terminal Air Traffic Control

"Trajectory specification" is the explicit bounding and control of aircraft tra- jectories such that the position at each point in time is constrained to a precisely defined volume of space. The bounding space is defined by cross-track, along-track, and vertical tolerances relative to a reference trajectory that specifies position as a function of time. The tolerances are dynamic and will be based on the aircraft nav- igation capabilities and the current traffic situation. A standard language will be developed to represent these specifications and to communicate them by datalink. Assuming conformance, trajectory specification can guarantee safe separation for an arbitrary period of time even in the event of an air traffic control (ATC) sys- tem or datalink failure, hence it can help to achieve the high level of safety and reliability needed for ATC automation. As a more proactive form of ATC, it can also maximize airspace capacity and reduce the reliance on tactical backup systems during normal operation. It applies to both enroute airspace and the terminal area around airports, but this paper focuses on arrival spacing in the terminal area and presents ATC algorithms and software for achieving a specified delay of runway arrival time.

air traffic control↗

Effects of modeling errors on trajectory predictions in air traffic control automation

Air traffic control automation synthesizes aircraft trajectories for the generation of advisories. Trajectory computation employs models of aircraft performances and weather conditions. In contrast, actual trajectories are flown in real aircraft under actual conditions. Since synthetic trajectories are used in landing scheduling and conflict probing, it is very important to understand the differences between computed trajectories and actual trajectories. This paper examines the effects of aircraft modeling errors on the accuracy of trajectory predictions in air traffic control automation. Three-dimensional point-mass aircraft equations of motion are assumed to be able to generate actual aircraft flight paths. Modeling errors are described as uncertain parameters or uncertain input functions. Pilot or autopilot feedback actions are expressed as equality constraints to satisfy control objectives. A typical trajectory is defined by a series of flight segments with different control objectives for each flight segment and conditions that define segment transitions. A constrained linearization approach is used to analyze trajectory differences caused by various modeling errors by developing a linear time varying system that describes the trajectory errors, with expressions to transfer the trajectory errors across moving segment transitions. A numerical example is presented for a complete commercial aircraft descent trajectory consisting of several flight segments.

Jackson, Michael R. C.↗

The Impact of Trajectory Prediction Uncertainty on Air Traffic Controller Performance and Acceptability

A Human-In-The-Loop air traffic control simulation investigated the impact of uncertainties in trajectory predictions on NextGen Trajectory-Based Operations concepts, seeking to understand when the automation would become unacceptable to controllers or when performance targets could no longer be met. Retired air traffic controllers staffed two en route transition sectors, delivering arrival traffic to the northwest corner-post of Atlanta approach control under time-based metering operations. Using trajectory-based decision-support tools, the participants worked the traffic under varying levels of wind forecast error and aircraft performance model error, impacting the ground automations ability to make accurate predictions. Results suggest that the controllers were able to maintain high levels of performance, despite even the highest levels of trajectory prediction errors.

trajectory prediction uncertainty↗

Conflict-free trajectory planning for air traffic control automation

As the traffic demand continues to grow within the National Airspace System (NAS), the need for long-range planning (30 minutes plus) of arrival traffic increases greatly. Research into air traffic control (ATC) automation at ARC has led to the development of the Center-TRACON Automation System (CTAS). CTAS determines optimum landing schedules for arrival traffic and assists controllers in meeting those schedules safely and efficiently. One crucial element in the development of CTAS is the capability to perform long-range (20 minutes) and short-range (5 minutes) conflict prediction and resolution once landing schedules are determined. The determination of conflict-free trajectories within the Center airspace is particularly difficult because of large variations in speed and altitude. The paper describes the current design and implementation of the conflict prediction and resolution tools used to generate CTAS advisories in Center airspace. Conflict criteria (separation requirements) are defined and the process of separation prediction is described. The major portion of the paper will describe the current implementation of CTAS conflict resolution algorithms in terms of the degrees of freedom for resolutions as well as resolution search techniques. The tools described in this paper have been implemented in a research system designed to rapidly develop and evaluate prototype concepts and will form the basis for an operational ATC automation system.

Slattery, Rhonda↗

Differing Air Traffic Controller Responses to Similar Trajectory Prediction Errors: An Interrupted Time-Series Analysis of Controller Behavior

A Human-In-The-Loop simulation was conducted in January of 2013 in the Airspace Operations Laboratory at NASAs Ames Research Center. The simulation airspace included two en route sectors feeding the northwest corner of Atlantas Terminal Radar Approach Control. The focus of this paper is on how uncertainties in the studys trajectory predictions impacted the controllers ability to perform their duties. Of particular interest is how the controllers interacted with the delay information displayed in the meter list and data block while managing the arrival flows. Due to wind forecasts with 20-knot over-predictions and 20-knot under-predictions, delay value computations included errors of similar magnitude, albeit in opposite directions. However, when performing their duties in the presence of these errors, did the controllers issue clearances of similar magnitude, albeit in opposite directions?

human-automation interaction↗

Differing Air Traffic Controller Responses to Similar Trajectory Prediction Errors

A Human-In-The-Loop simulation was conducted in January of 2013 in the Airspace Operations Laboratory at NASA's Ames Research Center. The simulation airspace included two en route sectors feeding the northwest corner of Atlanta's Terminal Radar Approach Control. The focus of this paper is on how uncertainties in the study's trajectory predictions impacted the controllers ability to perform their duties. Of particular interest is how the controllers interacted with the delay information displayed in the meter list and data block while managing the arrival flows. Due to wind forecasts with 30-knot over-predictions and 30-knot under-predictions, delay value computations included errors of similar magnitude, albeit in opposite directions. However, when performing their duties in the presence of these errors, did the controllers issue clearances of similar magnitude, albeit in opposite directions?

trajectory prediction uncertainty↗

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↗

Design Analysis of Corridors-in-the-Sky

Corridors-in-the-sky or tubes is one of new concepts in dynamic airspace configuration. It accommodates high density traffic, which has similar trajectories. Less air traffic controllers workload is expected than classic airspaces, thus, corridors-in-the-sky may increase national airspace capacity and reduce flight delays. To design corridors-in-the-sky, besides identifying their locations, their utilization, altitudes, and impacts on remaining system need to be analyzed. This paper chooses one tube candidate and presents analyses of spatial and temporal utilization of the tube, the impact on the remaining traffic, and the potential benefit caused by off-loading the traffic from underlying sectors. Fundamental issues regarding to the benefits have been also clarified. Methods developed to assist the analysis are described. Analysis results suggest dynamic tubes in terms of varied utilizations during different time periods. And it is found that combined lane options would be a good choice to lower the impact on non-tube users. Finally, it shows significant reduction of peak aircraft count in underlying sectors with only one tube enabled.

Xue, Min↗

Trajectory specification for high capacity air traffic control

Method and system for analyzing and processing information on one or more aircraft flight paths, using a four-dimensional coordinate system including three Cartesian or equivalent coordinates (x, y, z) and a fourth coordinate .delta. that corresponds to a distance estimated along a reference flight path to a nearest reference path location corresponding to a present location of the aircraft. Use of the coordinate .delta., rather than elapsed time t, avoids coupling of along-track error into aircraft altitude and reduces effects of errors on an aircraft landing site. Along-track, cross-track and/or altitude errors are estimated and compared with a permitted error bounding space surrounding the reference flight path.

Paielli, Russell A.↗

Capture Conditions for Merging Trajectory Segments to Model Realistic Aircraft Descents

A typical commercial aircraft trajectory consists of a series of flight segments. An aircraft switches from one segment to another when certain specified variables reach their desired values. Trajectory synthesis for air traffic control automation must be consistent with practical pilot procedures. We examine capture conditions for merging trajectory segments to model commercial aircraft descent in trajectory synthesis. These conditions translate into bounds on measurements of atmospheric wind, pressure, and temperature. They also define ranges of thrust and drag feasible for a descent trajectory. Capture conditions are derived for the Center-TRACON Automation System developed at NASA Ames Research Center for automated air traffic control. Various uses of capture conditions are discussed. A Boeing 727-200 aircraft is used to provide numerical examples of capture conditions.

Zhao, Yiyuan↗

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

Concept of Operations for Management by Trajectory

This document describes Management by Trajectory (MBT), a concept for future air traffic management (ATM) in which every flight operates in accordance with a four-dimensional trajectory (4DT) that is negotiated between the airspace user and the Federal Aviation Administration (FAA) to respect the airspace user's goals while complying with National Airspace System (NAS) constraints. In the present-day NAS, the ATM system attempts to predict the trajectory for each flight based on the approved flight plan and scheduled or controlled departure time. However, once the aircraft starts to move, controllers tactically manage the aircraft to implement traffic management restrictions, separate otherwise conflicting aircraft, and address arising NAS constraints. Tactical controller actions are not directly communicated to the automation systems or other stakeholders. Furthermore, the initial trajectory prediction does not anticipate these disruptions or how they will impact the flight. Consequently, and compounded by gaps in required data and models, trajectory predictions are less accurate than possible, which affects Traffic Flow Management (TFM) performance. A cornerstone of the MBT concept is that all air vehicles have, at all times, an assigned 4DT from their current state to their destination. These assigned trajectories consist of trajectory constraints and descriptions. Pilots and air traffic controllers, with the aid of automation, operate the aircraft to comply with the assigned trajectory, unless first negotiating a revision. Equipped aircraft have substantial responsibility for complying with the assigned trajectory without controller intervention. To maximize the operational flexibility available to the airspace user, the assigned trajectory only imposes trajectory constraints as required to achieve the ATM goals of NAS constraint compliance and aircraft separation. Trajectory descriptions are added to the assigned trajectory to ensure sufficient predictability. To further improve trajectory prediction accuracy, airspace users supplement the assigned trajectory by broadcasting intent information and updating it as necessary. Air vehicle intent is a more detailed description of the airspace user's plan for how the flight will fly the assigned trajectory. Air vehicle intent can change freely, without negotiation, as long as it remains in compliance with the assigned trajectory. Aircraft assigned trajectories, air vehicle intent, and predicted trajectories are shared, creating a common view among stakeholders. A NAS Constraint Service gathers and publishes information about all known NAS constraints, enabling airspace users to be informed participants in trajectory negotiation. Trajectory constraints in the assigned trajectory are mapped to NAS constraints to facilitate identifying which aircraft are affected when NAS constraints change. To support efficient trajectory negotiation, all aircraft provide current information about air vehicle capabilities. Assigned trajectories are constructed to satisfy all known NAS constraints, improving trajectory stability and predictability. Uncertainty and disruptions are handled by modifying the assigned trajectory as far in advance as possible. By proactively negotiating changes to the assigned trajectory, rather than relying on controller-selected tactical actions such as vectors to resolve traffic conflicts or implement miles-in-trail restrictions, MBT keeps aircraft on closed trajectories that are fully known to all stakeholders. Since reactive air traffic control actions cannot be predicted in advance, the downstream trajectory cannot be accurately predicted until they happen. Reliable trajectory predictions allow the system to identify needed modifications to trajectories further in advance, where they can be negotiated and communicated as amendments (i.e., additional or altered trajectory constraints) to the assigned trajectory. Decision Support Tools (DSTs) aid controllers in rapidly defining and communicating closed trajectories to the aircraft and support all stakeholders in trajectory negotiation. Anticipated MBT benefit mechanisms include more accurate trajectory predictions, improved ATM performance and robustness to off-nominal conditions, increased flexibility and operational efficiency, reduced impediments to emerging classes of airspace users accessing NAS resources, reduced environmental impacts, and enhanced safety.

ConOps↗

Modeling Uncertainty in Time and Fuel Benefit Estimation for TASAR Operational Evaluation

The Traffic Aware Strategic Aircrew Requests concept aims to reduce weather-induced delays, improve route efficiency, and efficiently share route modification options by combining onboard avionics data, Automatic Dependent Surveillance-Broadcast data, and broadband internet data to generate optimal, traffic-compatible trajectory changes based on real-time traffic and weather data. Time and fuel benefits due to use of the Traffic Aware Planner (TAP) software can be estimated by taking the difference in predicted flight time and fuel usage before and after a TAP-inspired trajectory change is completed. Although TAP’s optimization algorithm predicts flight and fuel usage based on the current flight route and weather data, it does not account for possible air traffic controller-initiated trajectory changes, reroutes due to sudden weather changes, or other pilot/controller actions that may occur during flight. This paper introduces an approach for quantifying the uncertainty in estimated time and fuel benefits.

Burris, Joseph↗

Traffic Aware Strategic Aircrew Requests (TASAR) Concept of Operations

Aircrews submit trajectory change requests to air traffic control (ATC) to better achieve the operator's preferred business trajectory. Requests are currently made with limited information and are often denied because the change is not compatible with traffic. Also, request opportunities can be overlooked due to lack of automation that advises aircrews of trajectory changes that improve flight time, fuel burn, and other objectives. The Traffic Aware Strategic Aircrew Requests (TASAR) concept leverages Automatic Dependent Surveillance-Broadcast (ADS-B) surveillance information to advise the aircrew of beneficial trajectory changes that are probed for traffic compatibility prior to issuing the request to ATC. This document describes the features, benefits, and limitations of TASAR automation hosted on an Electronic Flight Bag. TASAR has two modes: (1) auto mode that continuously assesses opportunities for improving the performance of the flight and (2) manual mode that probes trajectory changes entered by aircrews for conflicts and performance objectives. The roles and procedures of the aircrew and ATC remain unchanged under TASAR.

Henderson, Jeffrey↗

Trajectory-Based Takeoff Time Predictions Applied to Tactical Departure Scheduling: Concept Description, System Design, and Initial Observations

Current aircraft departure release times are based on manual estimates of aircraft takeoff times. Uncertainty in takeoff time estimates may result in missed opportunities to merge into constrained en route streams and lead to lost throughput. However, technology exists to improve takeoff time estimates by using the aircraft surface trajectory predictions that enable air traffic control tower (ATCT) decision support tools. NASA s Precision Departure Release Capability (PDRC) is designed to use automated surface trajectory-based takeoff time estimates to improve en route tactical departure scheduling. This is accomplished by integrating an ATCT decision support tool with an en route tactical departure scheduling decision support tool. The PDRC concept and prototype software have been developed, and an initial test was completed at air traffic control facilities in Dallas/Fort Worth. This paper describes the PDRC operational concept, system design, and initial observations.

Engelland, Shawn A.↗

Pilot in Command: An Illustration of Autonomous Flight Management

Several years of NASA research have produced the concept for air traffic management called "Distributed Air/Ground Traffic Management," a major operational advancement that should significantly increase the capacity of the National Airspace System. A key component, "Autonomous Flight Management," introduces a new class of aircraft operations in which pilots are authorized to freely maneuver and execute optimal trajectories independent from air traffic controllers. These aircraft operators would benefit from significant increases in flexibility to optimize all flight operations and from avoiding most of the delays associated with ground-controlled operations. Responsibilities for aircraft separation and arrival flow conformance are transferred to the flight deck, and the pilots use computerized decision-support tools to accomplish these tasks. A research prototype of these tools called the "Autonomous Operations Planner" is being developed at the NASA Langley Research Center. This 14-minute video illustrates Autonomous Flight Management from the airline pilot's perspective.

Wing, David J.↗

A Cockpit-Based Application for Traffic Aware Trajectory Optimization

The Traffic Aware Planner (TAP) is a cockpit-based advisory tool designed to be hosted on a Class 2 Electronic Flight Bag and developed to enable the concept of Traffic Aware Strategic Aircrew Requests (TASAR). This near-term concept provides pilots with optimized route changes that reduce fuel burn or flight time, avoids interactions with known traffic, weather and restricted airspace, and may be used by the pilots to request a trajectory change from air traffic control. TAP's internal architecture and algorithms are derived from the Autonomous Operations Planner, a flight-deck automation system developed by NASA to support research into aircraft self-separation. This paper reviews the architecture, functionality and operation of TAP.

TASAR↗