Search NASA⌕ Search

SEARCH · Search NASA

Results for “terminal airspace”

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 109 records · Page 6

The Effectiveness of a Route Crossing Tool in a Simulated New York Airspace

Congested airspace is the cause of many delays in the terminal area and these delays can have a ripple effect on the rest of a nation's airspace. The New York terminal area is an example of where this happens in the U. S. An important goal, therefore, is to increase the efficiency of operations in congested terminal airspace where possible. Modeling studies of arrival and departure flows have shown that sharing of arrival and departure airspace increases efficiency in terminal operations. One source of inefficiency in terminal operations is that departure aircraft are frequently held level under arrival flows when it would be more efficient to climb the departure aircraft earlier. A Route Crossing Tool was developed to help controllers climb Newark (EWR) departures to the south earlier by temporarily sharing airspace with arrivals coming into LaGuardia (LGA) from the south. Instead of flying under the arrivals, a departure to the south could climb earlier by flying through the arrival airspace if there was a suitable gap between arrivals. A Human-in-the-Loop (HITL) simulation was conducted in this environment which compared three tool conditions: Baseline (no tool), a Single Route Crossing tool in which one route through the arrival flow was evaluated for crossing, and a Multi-Route Crossing tool in which five parallel routes were evaluated. In all conditions, the departures could be held level under the arrival flow. The results showed that controllers climbed a higher proportion of departures in the Multi-Route tool condition than in the other two conditions, with a higher proportion of departures climbed in smaller gaps and in front of trailing arrivals. The controllers indicated that the Multi-Route and Single Route tools helped them estimate distances more accurately and rated safety, workload, and coordination in the simulation as acceptable.

terminal airspace↗

ATD-3 Dynamic Routes for Arrivals in Weather (DRAW) Operational Concept, V2.0

NASA's Airspace Technology Demonstration-3 (ATD-3) is the applied traffic flow management activity, and third in the series of ATD projects. ATD-3 provides a suite of en route automation tools, both ground and flight-deck based, that focus on improving the efficiency of en route operation from initial cruise to arrival into the Terminal Radar Approach Control (TRACON). Dynamic Routes for Arrivals in Weather (DRAW) is a technology in the ATD-3 suite that is designed to provide Traffic Managers with a capability to efficiently manage arrival traffic flow and help sustain metering operations when weather is impacting arrivals into major airports. DRAW mitigates convective weather impact on arrival metering operations by providing tools to Traffic Managers that enable efficient reroutes free of convective weather conflicts, and integrated with the arrival metering schedule(s).

terminal airspace↗

Unmanned Aircraft Systems Traffic Management (UTM) Safely Enabling UAS Operations in Low-Altitude Airspace

Unmanned Aircraft System (UAS) Traffic Management (UTM) Enabling Civilian Low-Altitude Airspace and Unmanned Aircraft System Operations What is the problem? Many beneficial civilian applications of UAS have been proposed, from goods delivery and infrastructure surveillance, to search and rescue, and agricultural monitoring. Currently, there is no established infrastructure to enable and safely manage the widespread use of low-altitude airspace and UAS operations, regardless of the type of UAS. A UAS traffic management (UTM) system for low-altitude airspace may be needed, perhaps leveraging concepts from the system of roads, lanes, stop signs, rules and lights that govern vehicles on the ground today, whether the vehicles are driven by humans or are automated. What system technologies is NASA exploring? Building on its legacy of work in air traffic management for crewed aircraft, NASA is researching prototype technologies for a UAS Traffic Management (UTM) system that could develop airspace integration requirements for enabling safe, efficient low-altitude operations. While incorporating lessons learned from the today's well-established air traffic management system, which was a response that grew out of a mid-air collision over the Grand Canyon in the early days of commercial aviation, the UTM system would enable safe and efficient low-altitude airspace operations by providing services such as airspace design, corridors, dynamic geofencing, severe weather and wind avoidance, congestion management, terrain avoidance, route planning and re-routing, separation management, sequencing and spacing, and contingency management. One of the attributes of the UTM system is that it would not require human operators to monitor every vehicle continuously. The system could provide to human managers the data to make strategic decisions related to initiation, continuation, and termination of airspace operations. This approach would ensure that only authenticated UAS could operate in the airspace. In its most mature form, the UTM system could be developed using autonomicity characteristics that include self-configuration, self-optimization and self-protection. The self-configuration aspect could determine whether the operations should continue given the current andor predicted windweather conditions. NASA envisions concepts for two types of possible UTM systems. The first type would be a Portable UTM system, which would move from between geographical areas and support operations such as precision agriculture and disaster relief. The second type of system would be a Persistent UTM system, which would support low-altitude operations and provide continuous coverage for a geographical area. Either system would require persistent communication, navigation, and surveillance (CNS) coverage to track, ensure, and monitor conformance. What is NASA doing to test the technologies? NASA's near-term goal is the development and demonstration of a possible future UTM system that could safely enable low-altitude airspace and UAS operations. Working alongside many committed government, industry and academic partners, NASA is leading the research, development and testing that is taking place in a series of activities called Technology Capability Levels (TCL), each increasing in complexity. UTM TCL1 concluded field testing in August 2015 and is undergoing additional testing at an FAA site.

UTM Low-altitude↗

The ASLOTS concept: An interactive, adaptive decision support concept for Final Approach Spacing of Aircraft (FASA). FAA-NASA Joint University Program

This presentation outlines a concept for an adaptive, interactive decision support system to assist controllers at a busy airport in achieving efficient use of multiple runways. The concept is being implemented as a computer code called FASA (Final Approach Spacing for Aircraft), and will be tested and demonstrated in ATCSIM, a high fidelity simulation of terminal area airspace and airport surface operations. Objectives are: (1) to provide automated cues to assist controllers in the sequencing and spacing of landing and takeoff aircraft; (2) to provide the controller with a limited ability to modify the sequence and spacings between aircraft, and to insert takeoffs and missed approach aircraft in the landing flows; (3) to increase spacing accuracy using more complex and precise separation criteria while reducing controller workload; and (4) achieve higher operational takeoff and landing rates on multiple runways in poor visibility.

Simpson, Robert W.↗

Models of Human Information Requirements: "When Reasonable Aiding Systems Disagree"

Aircraft flight management and Air Traffic Control (ATC) automation are under development to maximize the economy of flight and to increase the capacity of the terminal area airspace while maintaining levels of flight safety equal to or better than current system performance. These goals are being realized by the introduction of flight management automation aiding and operations support systems on the flight deck and by new developments of ATC aiding systems that seek to optimize scheduling of aircraft while potentially reducing required separation and accounting for weather and wake vortex turbulence. Aiding systems on both the flight deck and the ground operate through algorithmic functions on models of the aircraft and of the airspace. These models may differ from each other as a result of variations in their models of the immediate environment. The resultant flight operations or ATC commands may differ in their response requirements (e.g. different preferred descent speeds or descent initiation points). The human operators in the system must then interact with the automation to reconcile differences and resolve conflicts. We have developed a model of human performance including cognitive functions (decision-making, rule-based reasoning, procedural interruption recovery and forgetting) that supports analysis of the information requirements for resolution of flight aiding and ATC conflicts. The model represents multiple individuals in the flight crew and in ATC. The model is supported in simulation on a Silicon Graphics' workstation using Allegro Lisp. Design guidelines for aviation automation aiding systems have been developed using the model's specification of information and team procedural requirements. Empirical data on flight deck operations from full-mission flight simulation are provided to support the model's predictions. The paper describes the model, its development and implementation, the simulation test of the model predictions, and the empirical validation process. The model and its supporting data provide a generalizable tool that is being expanded to include air/ground compatibility and ATC crew interactions in air traffic management.

Corker, Kevin↗

Scheduling and Delivering Aircraft to Departure Fixes in the NY Metroplex with Controller-Managed Spacing Tools

In this paper, successful Time-Based Flow Management (TBFM) scheduling systems for arrivals are considered and adapted to apply to departures. We present a concept of operations that integrates Controller-Managed Spacing tools for departures (CMS-D) with existing tactical departure scheduling tools to coordinate demand at departure fixes in a metroplex environment. We tested our concept in a Human-in-the-Loop simulation and compared the effect of two scheduling conditions: 1) "Departure Scheduling" consisting of an emulation of the Integrated Departure and Arrival Capability (IDAC) where Towers and a Planner (Traffic Management Coordinator at the appropriate facility) coordinate aircraft scheduled takeoff times to departure fixes; and 2) "Arrival Sensitive Departure Scheduling" where, in addition, the Tower and Planner also consider arrival Scheduled Time of Arrivals (STAs) at the airport's dependent runway. Results indicate little difference between the two scheduling conditions, but a large difference between the No Tools and the two scheduling conditions with CMS-D tools. The scheduling/CMS-D tools conditions markedly reduced heading, speed clearances, and workload for controllers who were merging flows at the departure fixes. In the tool conditions, departure controllers conditioned departures earlier rather than later when aircraft were tied near the departure fixes. In the scheduling/CMS-D tools conditions, departures crossed the departure fixes 50 seconds earlier and with an 8% error rate (consisting of time ahead or behind desired time of arrival) compared to a 19% error rate in the No Tool condition. Two exploratory runs showed that similar beneficial effects can be obtained only with the CMS-D tools without scheduling takeoff times, but at the cost of a somewhat higher workload for controllers, indicating the benefits of pre-departure scheduling of aircraft with minimal delays. Hence, we found that CMS-D tools were very beneficial in the metroplex environment we tested but that further research is needed to clarify the benefits of the various scheduling approaches.

terminal airspace↗

En Route Detect and Avoid Well Clear in Terminal Area Landing Pattern

A fast time simulation was conducted to test the detect and avoid Well Clear definition designed for en route use when an unmanned aircraft (UA) is approaching the landing pattern of the terminal area. Measures focused on were loss of well clear and alerts intended to help the pilot avoid loss of well clear. Data indicated warning-level alerts will occur outside the typical Class D airspace which may prevent the UA from normal operations in the terminal airspace. Other aircraft on 45o entry could result in “nuisance” alerts which may also prevent the UA from normal operations in the terminal airspace. However, eliminating horizontal proximity (τmod) has the potential to increase “nuisance” alerts on the 45o entry and downwind legs. Overall, this suggests that a more stringent definition of Well Clear may be advisable in the landing pattern of the terminal area.

Trujillo, Anna C.↗

A Comparison of Two Terminal Area Detect and Avoid Well Clear Definitions

Technical requirements are currently under development for a detect and avoid system (DAA) that would support the operation of Unmanned Aircraft Systems (UAS) within the National Airspace System (NAS). Such a system would aid UAS operators in maintaining sufficient separation, or "well clear", from other aircraft in their vicinity. The first set of technical standards for a UAS DAA system (referred to as "Phase 1" requirements) was limited to UAS operations transiting through Class D, E, and G airspace to, or from, Class A (or special-use) airspace. Explicitly out of scope of the Phase 1 requirements was the operation of UAS within terminal airspace in the NAS. Fern, Rorie, Roberts and Monk (2018) explored the application of a Phase 1 DAA system within Class D terminal airspace in a human-in-the-loop simulation. The results of the study demonstrated a poor fit of the Phase 1 DAA well clear (DWC) definition to these terminal operations. The original DWC definition was designed for the en-route environment and could not account for the complex, tightly-choreographed nature of traffic typically found near an airport. The interaction of the en-route DWC definition and the terminal area traffic led to excessive DAA alerting against safely-separated traffic. The frequent alerting quickly degraded pilots' ability to discriminate between encounters where a maneuver was or was not necessary. This resulted in slower response times, higher rates of losses of DAA well clear, and more severe losses of DAA well clear than had been observed in previous DAA research (e.g., Rorie et al., 2017). The current paper reports on a follow-on study to Fern et al. (2018) that tested two DWC definitions designed to accommodate standard terminal area operating procedures, such as traffic in the downwind leg of a VFR traffic pattern while the UAS is on final. The two definitions utilized identical horizontal and vertical thresholds but differed in whether or not Tau (a function that takes into account the closure rate of two aircraft) was included as a part of the DWC hazard zone. The "Tau" DWC candidate definition nominally extended the DWC hazard zone by 15 seconds in the direction of the intruder aircraft, while the "No Tau" DWC candidate definition did not extend the DWC hazard zone. The results of this follow-on study indicated that both candidate definitions improved pilot and DAA system performance relative to Fern et al (2018). Pilot response times and rates of losses of DWC returned to levels comparable to earlier research in the en-route environment. Several important differences between the two DWC candidate definitions, however, are also discussed.

Terminal Area↗

Pathfinding for Airspace with Autonomous Vehicles (PAAV) ACAS Xr Terminal Area Simulation Overview

This presentation provides an overview of an upcoming human-in-the-loop simulation planned by the Pathfinding for Airspace with Autonomous Vehicles (PAAV) subproject, as part of the Air Traffic Management eXploration project. The study will investigate Detect and Avoid (DAA) concepts in and around the DAA terminal area (DTA). The DTA has received little investigation in real-time, pilot-in-the-loop simulation. This study proposes to use current remotely piloted aircraft system (RPAS) pilots to investigate the effectiveness of current DTA requirements using the FAA's Airborne Collision Avoidance System X for Rotorcraft (ACAS Xr) as the DAA system under test. The findings of this stufy will be used to inform DTA and ACAS Xr standards development. This presentation will be provided to RTCA Special Committee 228 as an overview and as an opportunity to collect feedback from the larger RPAS/DAA community on the study design and key scenarios and metrics. The presentation provides a brief overview of open areas of research with ACAS Xr, the experimental design, the simulation environment and the simulation schedule.

advanced air mobility↗

A System Concept for Facilitating User Preferences in En Route Airspace

The Federal Aviation Administration is trying to make its air traffic management system more responsive to the needs of the aviation community by exploring the concept of 'free flight' for aircraft flying under instrument flight rules. A logical first step toward free flight could be made without significantly altering current air traffic control (ATC) procedures or requiring new airborne equipment by designing a ground-based system to be highly responsive to 'user preference' in en route airspace while providing for an orderly transition to the terminal area. To facilitate user preference in all en route environments, a system based on an extension of the Center/TRACON Automation System (CTAS) is proposed in this document. The new system would consist of two integrated components. An airspace tool (AT) focuses on unconstrained en route aircraft (e.g., not transitioning to the terminal airspace), taking advantage of the relatively unconstrained nature of their flights and using long-range trajectory prediction to provide cost-effective conflict resolution advisories to sector controllers. A sector tool (ST) generates efficient advisories for all aircraft, with a focus on supporting controllers in analyzing and resolving complex, highly constrained traffic situations. When combined, the integrated AT/ST system supports user preference in any air route traffic control center sector. The system should also be useful in evaluating advanced free-flight concepts by serving as a test bed for future research. This document provides an overview of the design concept, explains its anticipated benefits, and recommends a development strategy that leads to a deployable system.

Vivona, R. A.↗

An Exploratory Evaluation of UAS Detect and Avoid Operations in the Terminal Environment

New technical standards for Unmanned Aircraft Systems (UAS) detect and avoid (DAA) systems mark recent progress toward realizing the goal of full integration of UAS into the National Airspace System (NAS). The DAA system is intended to provide a means of compliance with operating regulations that required pilots on board manned aircraft to remain "well clear" of other aircraft which is accomplished through out-the-window visual acquisition of other aircraft and application of a subjective judgment of safe separation. The requirements for the DAA system, including the specification of a DAA well clear threshold as well as functional requirements for detecting, tracking, alerting and guidance processing, and displays, are specified in DO-365, Minimum Operational Performance Standards (MOPS) for DAA Systems developed within RTCA (Radio Technical Commission for Aeronautics) Special Committee 228 (SC-228). Intended as the first in a series of phased versions, these requirements are frequently referred to as the "Phase 1" DAA system. The Phase 1 DAA system is limited for use by aircraft transitioning to and from Class A or special use airspace, through Class D, E, and G airspace. In particular, the Phase 1 DAA MOPS are not intended for terminal airspace operations, a critical gap for enabling a full range of UAS operations. The application of the Phase 1 DAA system and DAA well clear threshold within the terminal area is predicted to result in a high number of unnecessary alerts when the UAS is safely separated from other traffic. The goal of the present study was to examine pilot performance and operational issues related to the operation of the Phase 1 DAA system in a terminal area. This experiment was intended as an exploratory study that would be used to inform the development of a new terminal area-specific DAA well clear definition, and associated alerting and guidance requirements. The two main objectives of this study were to: 1) characterize pilot behavior in the terminal environment with the Phase 1 DAA system, and 2) investigate the effect of modifications to the Phase 1 DAA alerting and guidance structure. In particular, the authors were interested in determining whether the removal of specific alerting and guidance levels, without changing the DAA well clear definition or alerting thresholds, would impact pilot performance while conducting terminal operations. The results indicate that the Phase 1 well clear definition and alerting and guidance resulted in frequent alerting that degraded pilots' ability to discriminate between encounters where another aircraft was safely separated versus when a maneuver was necessary. The resulting impact on pilot performance was slower response times and higher frequency and severity of losses of DAA well clear compared to those observed for experiments examining pilot performance in the en route environment. There was no significant effect of alerting and guidance display configuration on pilot performance.

terminal area↗

An Exploratory Evaluation of UAS Detect and Avoid Operations in the Terminal Environment

New technical standards for Unmanned Aircraft Systems (UAS) detect and avoid (DAA) systems mark recent progress toward realizing the goal of full integration of UAS into the National Airspace System (NAS). The DAA system is intended to provide a means of compliance with operating regulations that required pilots on board manned aircraft to remain "well clear" of other aircraft which is accomplished through out-the-window visual acquisition of other aircraft and application of a subjective judgment of safe separation. The requirements for the DAA system, including the specification of a DAA well clear threshold as well as functional requirements for detecting, tracking, alerting and guidance processing, and displays, are specified in DO-365, Minimum Operational Performance Standards (MOPS) for DAA Systems developed within RTCA Special Committee 228 (SC-228). Intended as the first in a series of phased versions, these requirements are frequently referred to as the "Phase 1" DAA system. The Phase 1 DAA system is limited for use by aircraft transitioning to and from Class A or special use airspace, through Class D, E, and G airspace. In particular, the Phase 1 DAA MOPS are not intended for terminal airspace operations, a critical gap for enabling a full range of UAS operations. The application of the Phase 1 DAA system and DAA well clear threshold within the terminal area is predicted to result in a high number of unnecessary alerts when the UAS is safely separated from other traffic. The goal of the present study was to examine pilot performance and operational issues related to the operation of the Phase 1 DAA system in a terminal area. This experiment was intended as an exploratory study that would be used to inform the development of a new terminal area-specific DAA well clear definition, and associated alerting and guidance requirements. The two main objectives of this study were to: 1) characterize pilot behavior in the terminal environment with the Phase 1 DAA system, and 2) investigate the effect of modifications to the Phase 1 DAA alerting and guidance structure. In particular, the authors were interested in determining whether the removal of specific alerting and guidance levels, without changing the DAA well clear definition or alerting thresholds, would impact pilot performance while conducting terminal operations. The results indicate that the Phase 1 well clear definition and alerting and guidance resulted in frequent alerting that degraded pilots' ability to discriminate between encounters where another aircraft was safely separated versus when a maneuver was necessary. The resulting impact on pilot performance was slower response times and higher frequency and severity of losses of DAA well clear compared to those observed for experiments examining pilot performance in the en route environment. There was no significant effect of alerting and guidance display configuration on pilot performance.

Rorie, Conrad↗

Monitoring Airspace Complexity and Determining Contributing Factors

The national airspace has evolved over many years to accommodate increased traffic demand [1] while simultaneously maintaining one of the safest forms of transportation [2], [3]. One of the reasons for this success is the ability of the system and the operators to adapt and accommodate to situations that routinely disrupt optimal operations. These situations may include: adverse weather, delays, early arrivals, equipment outages, and other factors that are outside the operators ability to control. These factors can lead to states where automation is unable to properly handle these issues and therefore air traffic controllers and pilots have to intervene, ultimately increasing communication between operators resulting in higher workload. As controller workload increases to handle sub-optimal operating conditions this can be viewed as an increase in complexity. The reasoning for this is because humans are now required to make tactical decisions in response to external factors, resulting in a departure from the strategic plan where operations would be more efficiently managed. Human operators control airspace complexity under rigid regulations that are constantly changing. The airspace is divided into sectors and the number of aircraft assigned to each controller is limited for safe handling. There has been past work that devised airspace complexity metrics in commercial aviation and related these metrics to controller workload (e.g., [4],[5]). The upper bounds on the system load are pre-determined. Such bounds on complexity make for a safe system, but the system cannot scale and adapt to autonomous, dense, and heterogeneous traffic, including the many types of Unmanned Aerial Vehicles (UAVs) envisioned to be added to the operations. We hypothesize that, as traffic density and heterogeneity grow, and other key metrics change, there will be phase transitions at which the way traffic should be managed changes significantly [6]. We offer a method for in-time detection of contributing factors that lead to phase transitions, characterized by increased complexity. To the best of our knowledge, there is no tool similar to our proposed effort that identifies such contributing factors or precursor patterns. To define the scope we are proposing to measure complexity from the viewpoint of the Terminal Radar Approach Control Facilities (TRACON) controller’s perspective. In particular we are analyzing arrivals into KSFO. With safety as the top concern for airspace operators, it is important to recognize that as density and heterogeneity grow, the focus of the system will change. Times of the day when the airspace has low density and heterogeneity, the flights will follow more efficient paths where the aircraft move on established routes that are more or less directly to the destination. However, when density and heterogeneity increases, the system will begin changing focus to avoiding conflicts and collisions and route the flights in a more flexible way. Higher flexibility requires more communication and coordination between controllers and pilots which the current automation is unable to handle. This paper proposes a novel approach that monitors airspace complexity at multiple scales, uses a Machine Learning-based tool that predicts when operations will transition to a regime of greater complexity, and identifies actions that can reduce the complexity while still maintaining efficient and safe operations. We demonstrate our proposed approach using data from multiple complementary sources. This includes, but is not limited to: historical aircraft surveillance data from NASA’s Sherlock Data Warehouse [7], METAR weather data, and airport configuration data from Aviation System Performance Metrics (ASPM). The surveillance data flight paths are sampled at a variable sample rate — increasing as the aircraft approaches the airport. This is due to how Sherlock manages flight track stitching between different radar facilities which have different sampling rates. The weather and performance data are logged at defined intervals throughout the day at a courser refresh rate. In addition to the logged data and metrics, we leverage pre-defined Standard Terminal Arrival Routes (STARs) procedures to characterize the path of each flight. Each flight files for one of these routes in the flight plan well before entering the terminal airspace, and approximately follows the route until it leaves the STAR, typically on the final fix of a runway transition. However, most flights do not always fly the full STAR procedure to completion [8], but the majority do adhere to the fixes within the common route of the procedure. Our approach leverages fixes in the common route of each of the STARs to build a reference path to the airport. This allows us to characterize the flight paths in what we are defining as the “maneuvering area” (the airspace between the STAR and before the flight is lined up on the runway’s final approach) to determine how off nominal the flights are to calculate its complexity score. Determining airspace complexity is a concept that does not have a concrete answer. In designing this metric, we consider what increases the workload for the air traffic controllers. Consequently more specialized vectoring maneuvers results in higher workload. Accordingly, we start with a theory: each flight has a direct path it takes from the STAR’s common route to the final approach’s outer marker fix for the flight’s landing runway. It is important to note that the direct path is only used as a reference. If the majority of the flights have a large consistent offset as compared to other routes it does not necessarily mean that those flights have higher complexity. We are merely building a distribution based on this direct path for that particular STAR and runway pair to determine the normal mode of operations for that route. Flights that are in the upper tail of these distributions will result in higher complexity scores and flights that fly in the median will represent the normal mode of operations and therefore will have lower complexity scores. Since flights following each STAR route take different paths to the airport, we have a different distribution for each STAR route and therefore can model these distributions to compute a complexity score from their respective normalized distributions. To evaluate the effectiveness of our proposed airspace complexity metric we will compare against an established approach based on trajectory clustering [9]. This unsupervised learning technique consists of the following steps: (1) identify the general maneuvering areas (waypoints) by performing $\kappa$-means or DBSCAN clustering on locations where aircraft frequently turn based on the surveillance radar track data, (2) map flight trajectories onto sequences of waypoints, and (3) cluster the sequences based on their common subsequences. From a high-level perspective, this baseline model learns nominal operations in the airspace through the sequence of waypoints that are representative of where aircraft change direction and defines deviations from the nominal operations as “complex.” Therefore, more deviations from the nominal operations correspond to higher complexity values. For our validation, we re-implemented this technique and tune model hyper-parameters to correctly detect waypoints for the arrival traffic into the San Francisco bay area. We will compute the complexity measure over a one-year period using our proposed technique as well as the baseline. Our validation will be based on each technique’s ability to detect a set of undesirable outcomes (e.g., go-arounds, holding patterns, average time in the airspace, etc.). Since our current complexity metric is derived from the offset from the direct reference path, it’s important to understand what causes these offsets. In many of the flights with high offset distance, flights performing holding patterns and S turns can be observed. These maneuvering tactics are utilized to add distance between the aircraft and the destination runway to prevent multiple flights from having conflicting arrival times. In order to predict a rise in complexity (or the precursor to complexity), it’s necessary to be able to identify these potential conflicts (which in turn, result in higher offsets). To do this, we define a “representative flight” for each STAR route and runway pair. This flight is approximately the path the flight would take if there was a clear path with no other flights in the airspace — including the time remaining to the airport. We first identify the flights for a given STAR runway pair using the offset to the reference path distributions that fall between the 44-55 percentiles. This yields the flights that conform to the most normal mode of operation. Each of these flights is partitioned based on the percent complete from the entry point into the maneuvering areas from 0\% – 100\% complete. Then for each percent “bin”, we take the median value of the flight’s latitude/longitude coordinates, airspeed, and (non causal) time remaining to the airport to construct a lookup table for each percent complete bin on a given route. As a flight enters the maneuvering area, we can find the estimated arrival time of a flight to the airport by finding the closest point to the representative path’s percent complete bin (relative to the flight’s current position at any snapshot in the airspace) and therefore retrieve the corresponding remaining time left on the “representative path”. We assume that the flight will follow the representative path to completion when deriving these estimates. We can then compare these estimated arrival times against other flights for the same snapshot in time to identify potential conflicts. If more flights are estimated to arrive within a tolerance window than there are runways available, then we have a potential conflict. We can use this derived measure along with other factors expected to add disruption to the operation such as weather and runway configuration changes as an input to machine learning tools to detect precursors that increases in our complexity measure. This novel method will assist in uncovering insights into the contributing factors that lead to increased complexity that may allow for in-time responses to avoid reaching a high complexity state in the airspace.

complexity↗

Human-in-the-Loop Flight Simulation Experiment on Unmanned Aircraft Terminal Operations

A Detect and Avoid (DAA) System is a suite of sensors, tracker, and alerting and guidance algorithms that assist a remote pilot of an Unmanned Aircraft System in maintaining separation from airborne traffic by complying with current ‘see and avoid’ requirements. To date, work has focused on operations transiting to and from Class A or special use airspace. Current efforts are defining DAA system requirements for operations in and around terminal airspace. As a contribution to the current efforts, this paper presents results from a Human-in-the-Loop experiment comparing methods of changing from the transit-specific alerting and guidance criteria to the reduced terminal-specific alerting and guidance criteria.

Devin Patrick Jack↗

Terminal Area Considerations for UAS Detect and Avoid

Unmanned Aircraft Systems need to be able to comply with manned aviation ‘see and avoid’ separation requirements. A Detect and Avoid (DAA) System includes sensors, a tracker, and alerting and guidance algorithms that assist a remote pilot in maintaining separation from airborne traffic. To date, DAA system requirements development has focused on operations transiting to and from Class A or special use airspace. Current efforts are defining DAA system requirements for operations in and around terminal airspace. As a contribution to the current efforts, this paper highlights results from a Human in the Loop (HiTL) experiment comparing methods of changing from the transit-specific alerting and guidance criteria to proposed terminal-specific alerting and guidance criteria. It discusses operational considerations that are beyond the HiTL.

Unmanned Aircraft Systems↗

Cruise-Efficient Short Takeoff and Landing (CESTOL): Potential Impact on Air Traffic Operations

The National Aeronautics and Space Administration (NASA) is investigating technological and operational concepts for introducing Cruise-Efficient Short Takeoff and Landing (CESTOL) aircraft into a future US National Airspace System (NAS) civil aviation environment. CESTOL is an aircraft design concept for future use to increase capacity and reduce emissions. CESTOL provides very flexible takeoff, climb, descent and landing performance capabilities and a high-speed cruise capability. In support of NASA, this study is a preliminary examination of the potential operational impact of CESTOL on airport and airspace capacity and delay. The study examines operational impacts at a subject site, Newark Liberty Intemational Airport (KEWR), New Jersey. The study extends these KEWR results to estimate potential impacts on NAS-wide network traffic operations due to the introduction of CESTOL at selected major airports. These are the 34 domestic airports identified in the Federal Aviation Administration's Operational Evolution Plan (OEP). The analysis process uses two fast-time simulation tools to separately model local and NAS-wide air traffic operations using predicted flight schedules for a 24-hour study period in 2016. These tools are the Sen sis AvTerminal model and NASA's Airspace Concept Evaluation System (ACES). We use both to simulate conventional-aircraft-only and CESTOL-mixed-with-conventional-aircraft operations. Both tools apply 4-dimension trajectory modeling to simulate individual flight movement. The study applies AvTerminal to model traffic operations and procedures for en route and terminal arrival and departures to and from KEWR. These AvTerminal applications model existing arrival and departure routes and profiles and runway use configurations, with the assumption jet-powered, large-sized civil CESTOL aircraft use a short runway and standard turboprop arrival and departure procedures. With these rules, the conventional jet and CESTOL aircraft are procedurally separated from each other geographically and in altitude during tenninal airspace approach and departure operations, and each use a different arrival runway. AvTeminal implements its unique Focal-point Scheduling Process to sequence, space and delay aircraft to resolve spacing and overtake conflicts among flights in the airspace and airport system serving KEWR. This Process effectively models integrated arrival and departure operations. AvTerminal assesses acceptance rates and delay magnitude and causality at selected locations, including en route outer boundary fixes, tenninal airspace arrival and departure boundary fixes, terminal airspace arrival merge and departure diverge fixes, and runway landing and takeoff runways. The analysis compares the resulting capacity impacts, flight delays and delay sources between CESTOL and conventional KEWR operations. AvTerminal quantitative results showed that CESTOL has significant capability to increase airport arrival acceptance rates (35-40% at KEWR) by taking advantage of otherwise underused airspace and runways where available. The study extrapolates the AvTerminal-derived KEWR peak arrival and departure acceptance rates to estimate capacity parameter values for each of the OEP airports in the ACES modeling of traffic through the entire NAS network. The extrapolations of acceptance rates allow full, partial or no achievement of CESTOL capacity gains at an OEP airport as determined by assessments of the degree to which local procedures allow leveraging of CESTOL capabilities. These assessments consider each OEP airport's runway geometries, runway system configurations, airport and airspace operations, and potential CESTOL traffic loadings. The ACES modeling, simulates airport and airspace spacing constraints imposed by airport runway system, terminal and en route air traffic control and traffic flow management operations using airport acceptance rates representing conventional-aircraft-only and CESTOL-mixed operations. CEOL aircraft are assumed to have Mach 0.8, and alternatively Mach 0.7, cruise speeds to examine compatibility with conventional aircraft operations in common airspace. The ACES results provides estimates of CESTOL delay impact NAS-wide and at OEP airports due to changes in OEP airport acceptance rates and changes in en route airspace potential conflict rates. Preliminary results show meaningful nationwide delay reductions (20%) due to CESTOL operations at 34 major domestic airports.

Couluris, G. J.↗