ALBERT

Description: This document serves as a user manual for the STBO Client in Charlotte Douglas International Airport Air Traffic Control Tower. It describes the elements of the full interface and provides explanations for how to interact with the interface. The document also provides instructions for entering Traffic Management Initiatives, scheduling runway utilization changes, and closing runways. There are also detailed instructions for how to negotiate Approval Request (APREQ) release times using the STBO Client.

Description: Urban Air Mobility (UAM) - defined as safe and efficient air traffic operations in a metropolitan area for manned aircraft and unmanned aircraft systems - is being researched and developed by industry, academia, and government. Significant resources have been invested toward cultivating an ecosystem for Urban Air Mobility that includes manufacturers of electric vertical takeoff and landing aircraft, builders of takeoff and landing areas, and researchers of the airspace integration concepts, technologies, and procedures needed to conduct Urban Air Mobility operations safely and efficiently alongside other airspace users. This paper provides high-level descriptions of both emergent and early expanded operational concepts for Urban Air Mobility that NASA is developing. The scope of this work is defined in terms of missions, aircraft, airspace, and hazards. Past and current Urban Air Mobility operations are also reviewed, and the considerations for the data exchange architecture and communication, navigation, and surveillance requirements are also discussed. This paper will serve as a starting point to develop a framework for NASA's Urban Air Mobility airspace integration research and development efforts with partners and stakeholders that could include fast-time simulations, human-in-the-loop (HITL) simulations, and flight demonstrations.

Description: NASA has been collaborating with the Federal Aviation Administration (FAA) and aviation industry partners to develop and demonstrate new concepts and technologies for the Integrated Arrival, Departure, and Surface (IADS) traffic management capabilities under the Airspace Technology Demonstration 2 (ATD-2) project. The primary goal of the ATD-2 project is to improve the predictability and the operational efficiency of the air traffic system in metroplex environments while maintaining or improving throughput by enhancing and integrating arrival, departure and surface prediction, scheduling, and management systems. In the Phase 1 Baseline IADS Demonstration, the tactical surface scheduling capability and the user interfaces for ramp controllers and ramp traffic managers were implemented for ramp operations. The purpose of the tactical surface scheduling capability is to provide the airline ramp controller with aircraft pushback advisories that prevent surface congestion and to respond to surface and airspace constraints that become known over relatively short time horizons. For this purpose, the tactical surface metering tool first estimates the capacity of current and near-future runway resources from flight schedule and surveillance data. With demand forecasts and predicted taxi trajectories, this tool computes an efficient runway schedule of aircraft in the planning horizon based on their readiness, Earliest Off-Block Times (EOBTs), and a ration by schedule (RBS) rule. Details on the implementation of the Tactical Surface Metering tool will be provided in the full paper. Both pushback and recommended hold times advisories provided by this surface metering tool are shown on the user interfaces for the ramp controller and the ramp traffic manager, called Ramp Traffic Console (RTC) and Ramp Manager Traffic Console (RMTC), respectively. There is excess queue time in the system due to demand capacity imbalance, this time can be taken as a hold on the runway queue or at the gate and was referred to as the Metering Value. This metering value can be adjusted by the Ramp Manager in collaboration with Air Traffic Controller-Tower Traffic Management Coordinator (TMC). They selected a set of metering values as default values for the tool during human-in-the-loop simulation. As the metering value increases, there is a decrease in the gate hold and increase in the queue time at the runway. Procedures and Information needs related to managing the surface metering procedures were researched in the simulated environment. These procedures will be compared to the procedures adopted at Charlotte Douglas International Airport when the tools were deployed and adopted in November 2017 for one departure push bank per day. Feedback regarding initial issues, information needs such as the need to see EOBTs on the flight data tags and how they compare to scheduled times will also be discussed in the full paper. Initial results will be provided regarding the choice of the metering value and how it was adjusted on a daily basis and what procedures evolved will also be presented in the paper.

Description: The introduction of Performance-Based Navigation (PBN) specifications to air traffic management has resulted in many benefits during nominal operations, including shorter flight paths, reduced fuel costs, and improved terminal area arrival rates. However, these benefits become less noticeable during off-nominal operations where aircraft are routinely interrupted from staying on PBN procedures due to disturbances such as missed approaches. This human-in-the-loop (HITL) study used multiple types of disturbance events to perturb the arrival schedule. Perturbed schedules were managed with different types of schedule adjustments, including a condition with no adjustments. The study collected data on a host of dependent variables, including human factors measures on controller workload and system performance measures such as schedule nonconformance (nc). Initial analyses showed strong correlations between aggregated controller workload and aggregated nc, as well as benefits of both automatic and manual schedule adjustments for increasing system performance, such as reduced PBN procedure interruptions. The goal of this paper is to further test these initial findings. The results indicated that an increase in schedule nonconformance correlated with an increase in controller workload at specific time intervals, and automated schedule adjustments consistently reduced controller workload associated with nonconformance.

Description: This paper assesses the resilience of scheduled Performance-Based Navigation (PBN) arrival operations. Resilience is defined as an ability to return to nominal operations following a schedule perturbation. Results from a Human-in-the- Loop (HITL) experiment that included off-nominal events to perturb the schedule are described. The schedule comes from a precision trajectory-based arrival manager. The experiment collected data regarding the response to perturbed schedules in three conditions, where: 1) a disturbance rejection algorithm made schedule adjustments automatically, 2) a Traffic Management Coordinator (TMC) participant made schedule adjustments manually, or 3) no schedule adjustments were made. Analyses showed that the simulations scheduled PBN operations have inherent resilience, recovering from more than half of the perturbed schedules even with no schedule adjustments. Resilience to the same off-nominal events improved with schedule adjustments; an increased proportion of perturbed schedules recovered within the length of operation run, and the average duration of the schedules perturbed state decreased. Compared to the manual schedule adjustments condition, a greater number of schedule adjustments occurred for the same off-nominal events in the automated condition. However, perturbed schedules were recovered more frequently and perturbations were less severe in the automated condition. Subjective and objective workload in the manual and the automated schedule adjustment conditions were similar to the no schedule adjustment condition.

Description: This paper investigates routes and procedures for Urban Air Mobility (UAM), which aims to reduce congestion on the roads and highways by offering air taxi as an alternative to driving. The routes and procedures being explored are current-day helicopter routes along with different communication procedures that are available as tools in the near-term. Three different levels of UAM traffic were evaluated in the Dallas Fort Worth (DFW) area. The current-day helicopter routes were modified to separate them from traditional traffic, and a Letter of Agreement (LOA) was introduced in some of the conditions to reduce verbal communications. We found that modifications to the routes and introduction of LOA helped increase the number of UAM flights that the controllers reported they could manage and reduce their communications, which made controller self-reported workload more operationally acceptable. However, the self-reported workload experienced by busy airport towers cannot be effectively managed via the usage of LOA and modified helicopter routes, suggesting there is an opportunity to re-think roles and responsibilities of the UAM system participants.

Description: The present research explored whether the implementation of a letter of agreement (LOA), or pre-established written terms of engagement, would reduce controller communication associated workload in a HITL study simulating a near-term UAM infrastructure with varying traffic levels. Current helicopter routes, including modified versions, and communication procedures were outlined in the LOA. Time spent communicating was reduced under both conditions featuring a LOA, for current and modified routes, compared to present day procedures without a LOA. Results suggest that utilizing current-day helicopter routes and implementing a LOA may prove beneficial for near-term low-density and low-tempo UAM operations.

Description: This document serves as a user manual for the Ramp Traffic Console (RTC) in the Ramp Control Tower. It describes the elements of the RTC interface and provides explanations for how to utilize the RTC to manage ramp traffic. The RTC provides live data for all flights including Earliest Off-Block Times (EOBT) and Traffic Management Initiatives (TMI). The RTC augments management of ramp traffic by providing notifications of runway configurations, and lists flight arrivals, near arrivals and departures as additional sources of information. If applicable, this document also provides instructions for use of the Ramp Manager Traffic Console (RMTC) for ramp manager functions of adjusting the priority flight list, and setting ramp status. The RTC/RMTC ramp tool are components of Airspace Technology Demonstration-2.

Description: The What-If System is meant to be a "sandbox" to be able to view the potential impact of system wide changes on the tower side and metering decisions on the ramp side without actually making changes to the system. The What-If System is a tool within which with STBO, RMTC and DASH may be used such that proposed changes and updates can be made to determine their impact in isolation. The What-If System is a prototype tool, we welcome suggestions for improving the What-If utility. Improvements will be incorporated in later builds beyond phase-1 of ATD-2.

Description: Implementation of Urban Air Mobility (UAM) operations, or air passenger transportation systems within densely populated metropolitan areas, seeks to mitigate increasing traffic congestion. However, the development and integration of UAM operations into the national airspace system comes with its own unique challenges, such as vehicle requirements, flight planning and scheduling, and coordination between UAM flights and air traffic controllers. In particular, verbal coordination will play an integral part in the determined success of UAM operations and its ability to meet projected high consumer demands. In order to meet demands and higher traffic volumes on UAM routes, verbal communication between the UAM pilot and controller must be streamlined to reduce the controller's workload while helping to maintain safety within a given airspace. One method of reducing verbal workload are Letters Of Agreement (LOAs) that outline responsibilities and procedures for operations in an airspace. These LOAs will specify the operations, procedures, and routes for UAM flights. The proposed study will examine the usability of two route formatting styles for LOAs; (i) Verbal route descriptions and (ii) Tower En Route Control (TECs) routes. Verbal route descriptions will include the route name and associated visual cues on the route. The TEC route versions will include relevant waypoints and charts outlining the route with waypoints marked. The study will be part of a UAM X1 human in the loop (HITL) simulation. Controller participants will handle traditional air traffic including moderate levels of UAM traffic on current and modified helicopter routes within the Dallas Fort-Worth area. Scenarios will be counterbalanced and repeated to test both route formatting versions. After each trial, participants will rate the usability of the LOA used in the previous trial via a subjective questionnaire. We expect that controllers will prefer the LOA with TEC routes due to simplicity and visual elements available.