Search

A tool to give the public a window into Unmanned Aerial Systems (UAS) Traffic Management (UTM) operations was created from an existing data collection tool. The interface included a map and a table showing details about UAS operations that could be queried in a number of ways. Eleven participants attended the study, successfully completing a 19-item task set in about 30 minutes. They correctly found information for 87% of the non-subjective tasks at a rate of around a minute per task, and rated the usability of the tool at the end of the session above the industry benchmark. Participants gave favorable reviews of the "public portal tool", even reporting that they would be satisfied with less information that it presented. There were one or two elements of the display that users found distracting and some navigation functions that need improvement, but on balance, the public representatives liked the features they saw in, and had few criticisms of, the public portal tool. One important issue for the small Unmanned Aerial System community to resolve will be how much or how little information should be available about UTM operations to members of the public.

A tool to give the public a window into Unmanned Aerial Systems (UAS) Traffic Management (UTM) operations was created from an existing data collection tool. The interface included a map and a table showing details about UAS operations that could be queried in a number of ways. Eleven participants attended the study, successfully completing a 19-item task set in about 30 minutes. They correctly found information for 87% of the non-subjective tasks at a rate of around a minute per task, and rated the usability of the tool at the end of the session above the industry benchmark. Participants gave favorable reviews of the "public portal tool", even reporting that they would be satisfied with less information that it presented. There were one or two elements of the display that users found distracting and some navigation functions that need improvement, but on balance, the public representatives liked the features they saw in, and had few criticisms of, the public portal tool. One important issue for the small Unmanned Aerial System community to resolve will be how much or how little information should be available about UTM operations to members of the public.

The Technology Capability Level-3 (TCL3) flight tests were conducted at six different test sites located across the USA from March to May of 2018. The campaign resulted in over 830 data collection flights using 28 different aircraft and involving 20 flight crews. Flights not only varied in duration, but also in the environments and terrains over which they flew. The TCL3 tests highlighted four different types of tests: three tests focused on Communication, Navigation and Surveillance (CNS); six tests focused on Sense and Avoid (SAA) technologies; six tests focused on USS Data and Information Exchange (DAT); and five tests focused on exploring fundamental Concepts of the project (CON). This document presents data collected during the TCL3 tests that informed the operator’s experiences—the quality of the unmanned aerial system (UAS) Service Supplier (USS) information that the operator was provided with, the usefulness of this information, and the usability of the automation, both while airborne and on the ground. It is intended to complement the reports written by the test sites and the quantitative reports and presentations of the UAS Traffic Management (UTM) project. With the goal of instructing what the minimum information requirements and/or best practices might be in TCL3 operations, the driving enquiry was: How do you get the information you need, when you need it, to successfully fly a UAS in UTM airspace? This enquiry touches on two requirements for displays, which are to provide adequate situation awareness (SA) and to share information through a USS. The six test sites participating in the TCL3 tests flew a subset of the 20 tests (outlined above), with most sites working on a subset of each of the four types: Communications, Navigation and Surveillance (CNS); DAT; CON; and Sense and Avoid (SAA). The, mainly qualitative, data addressed in this report was collected by the AOL (Airspace Operations Laboratory) both on-site and remotely for each test. The data consists of the contents of end-of-day debriefs, end-of-day surveys, observer notes, and flight test information, all submitted as part of the Data Management Plan (DMP).

The purpose of this paper is to describe a research platform for the Urban Air Mobility (UAM) concept. UAM was conceived to enable short-range, low-altitiude service to commuters in metropolitan areas. At the NASA Ames Airspace Operations Laboratory (AOL) user interfaces have been developed to support small UAS operations for the UAS Traffic Management (UTM) project. Due to operational similarities between UAM and UTM, the UTM architecture offers a convenient starting point for research and development of UAM operations. Herein, we begin with an overview of the primary need and expectations characterizing concepts for modern air transportation systems, followed by a brief description of the UTM and UAM concepts. We then describe the UTM architecture, as well as the AOL's research platform and capabilities. The potential applications for UAM research and development are then discussed, providing some direction for future research efforts.

During the NASA Unmanned Aircraft System (UAS) Traffic Management (UTM) Project’s Technical Capability Level 3 (TCL3) demonstration, a service for stakeholders to share weather and aircraft observations was tested. The overall goal was to increase awareness of airspace and weather activity to increase a pilot’s ability to fly safely. To achieve this goal, a mechanism to share data was created, called “UAS Reports” or UREPs, which were generated by client systems and sent to a central data service. The data service provided subscriptions and allowed for data requests to share the reports that had been sent in by stakeholders. To execute this functionality, four FAA (Federal Aviation Administration)-designated UAS test sites performed UREP testing as part of TCL3. NASA provided the centralized service and test site partners flew missions and simulated activity at the test sites to generate data to send to the service. The loop was closed by having other clients (usually other small UAS operators) request those data from the service or subscribe to feeds from the service. Overall, the tests demonstrated the utility of such a service. In this report, the testing setup, data collection, and analysis of results are presented. The concept of UREPs has since been incorporated as a service within NASA’s Conflict Mitigation Model for UTM. The concept will continue to be tested in NASA’s TCL4 activities.

NASA is currently engaged in research to safely enable large-scale commercial applications of small Unmanned Aerial Systems (UAS) in low altitude airspace. This research effort, referred to as UAS Traffic Management (UTM), encompasses the concepts and technologies needed to accommodate the projected demand of UAS operating in the national airspace. One aspect related to the successful implementation of UTM in the future is public acceptance. Transparency will heavily influence this acceptance, and a public portal will provide much of that transparency through ease of access to information about the operations - mainly who, why, and where such operations are taking place. Related concerns to the public are individual privacy, security, and accountability of the operators. Providing the aforementioned information about operations can mitigate these concerns, but a balance will have to be achieved between the need for transparency from the public and the privacy of the operators. The proper balance and the needs of the various UTM stakeholders with regard to information access will be explored through the development and testing of a public portal as part of NASA's Technical Capability 3 (TCL 3) demonstration. Additionally, various approaches to the display of information and user interfaces will be surveyed through the development of a public portal by multiple UTM industry partners across different test sites.

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.

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.

In this paper we discuss how team configuration may influence how infor-mation is shared among team members for low-altitude Unmanned Aircraft Systems (UAS) operations. NASA collected and analyzed observation data gathered during a series of field tests for the UAS Traffic Management (UTM) project. The field tests were part of a larger effort aimed at advancing the UTM concept, conducted at six test-sites spread across the USA. Ground control station (GCS) concepts, flight-crew composition, and crew-size var-ied within and across test-sites. Flight crews took two strategic approaches to organizing their teams. The first of the two approaches was implemented by one third of the flight crews. These crews integrated the role of UTM opera-tor into the duties of existing crew members, merging the current roles with this new one, keeping the UTM Operator collocated with the flight crew. The remaining two thirds implemented a distributed team configuration, where a single UTM operator distributed support across multiple crews. Results from our data collection efforts revealed that UTM Operator location influenced whether flight crews used verbal communication versus displays to acquire UTM information.

These slides form the first talking points for the CON3 focus groups. They are designed to give an overview of the UTM project to people with no prior knowledge so they can help us with ideas for a public portal USS.

The Technology Capability Level-2 National Campaign (TCL2nc) was conducted at six different test-sites located across the USA, during May and June of 2017. The campaign resulted in over 240 data collection flights using 24 different aircraft and involving 23 flight crews. Flights not only varied in duration, but also in the environments and terrains over which they flew. The TCL2nc highlighted beyond visual line of sight (BVLOS) and altitude-stratified operations, and saw five partners bring their own, independently built, UAS Service Supplier (USS) for use during the flight tests. This document presents data collected during the TCL2nc that informs the 'Operator' section of the 'Requirements/Best Practices' from the UTM Technical Capability Matrix and Guidelines to Operate (Rios, version as of March 2017). A review of the data collected indicated that although teams were well qualified on paper (in terms of both completing training and having experience with flying UAS vehicles), greater consideration should be given to the unique perspectives and backgrounds of future UAS operators. Overall, teams looked at a variety of sources for information, including USS client-displays, and participants became more mindful of the need to be aware of other vehicles, highlighting the value of reporting information. Observations found that flight crews' time to respond to a UTM issue depended heavily on the team structure, communication efficiency, and crew procedures. These points are discussed in more detail below.

The Technology Capability Level-2 National Campaign (TCL2nc) was conducted at six different test sites located across the USA, during May and June of 2017. The campaign resulted in over 250 data collection flights using 26 different aircraft and involving 23 flight crews. Flights not only varied in duration, but also in the environments and terrains over which they flew. The TCL2nc highlighted beyond visual line of sight (BVLOS) and altitude-stratified operations, and saw five partners bring their own, independently built, UTM Service Supplier (USS) for use during the flight tests. This document presents data collected during the TCL2nc that informs the 'Operator' section of the 'Requirements/Best Practices' from the UTM Technical Capability Matrix and Guidelines to Operate (Rios, version as of March 2017). A review of the data collected indicated that although teams were well qualified on paper (in terms of both completing training and having experience with flying UAS vehicles), greater consideration should be given to the unique perspectives and backgrounds of future UAS operators. Overall, teams looked at a variety of sources for information, including USS client-displays, and participants became more aware of the need to be aware of other vehicles, highlighting the value of reporting information. Observations found that flight crews' time to respond to a UTM issue depended heavily on the team structure, communication efficiency, and crew procedures.

NASA is collaborating with the Federal Aviation Administration (FAA) and aviation industry partners to develop and demonstrate new concepts and technologies for Integrated Arrival, Departure, and Surface (IADS) traffic management capabilities under the Airspace Technology Demonstration 2 (ATD-2) project. One of the goals of the IADS capabilities in the ATD-2 project is to increase predictability and throughput of airspace operations by improving Traffic Management Initiative (TMI) compliance. This paper focuses on the Approval Request (APREQ) procedures developed for the ATD-2 project between the Air Traffic Control (ATC) Tower at Charlotte Douglas International Airport and Washington Center. In March 2017, NASA conducted a Human-in-the-Loop (HITL) simulation to evaluate the operational procedures and information requirements for the APREQ procedures in the ATD-2 IADS system between ATC Tower and Center. The findings from the HITL are used to compare ATD-2 APREQ procedures with information about current day APREQ procedures.

NASA is collaborating with the Federal Aviation Administration (FAA) and aviation industry partners to develop and demonstrate new concepts and technologies for Integrated Arrival, Departure, and Surface (IADS) traffic management capabilities under the Airspace Technology Demonstration 2 (ATD-2) project. One of the goals of the IADS capabilities in the ATD-2 project is to increase predictability and throughput of airspace operations by improving Traffic Management Initiative (TMI) compliance. This paper focuses on the Approval Request (APREQ) procedures developed for the ATD-2 project between the Air Traffic Control (ATC) Tower at Charlotte Douglas International Airport and Washington Center. In March 2017, NASA conducted a Human-in-the-Loop (HITL) simulation to evaluate the operational procedures and information requirements for the APREQ procedures in the ATD-2 IADS system between ATC Tower and Center. The findings from the HITL are used to compare ATD-2 APREQ procedures with information about current day APREQ procedures.

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. One of the goal of The IADS capabilities in the ATD-2 project is to increase predictability and increase throughput via improving TMI compliance. The IADS capabilities that will impact TMI compliance are built upon previous NASA research, the Precision Departure Release Capability (PDRC). The proposed paper will evaluate the APREQCFR process between ATC Tower and Center and information sharing between ATC Tower and the airline Ramp tower. Subjective measures collected from the HITL surveys (e.g., workload, situational awareness, acceptability, usability) and performance metrics such as TMI, TMAT, and pushback advisory compliance from APREQCFR flights and will be reported.

NASA has been working with the FAA and aviation industry partners to develop and demonstrate new concepts and technologies that integrate arrival, departure, and surface traffic management capabilities. In March 2017, NASA conducted a human-in-the-loop (HITL) simulation for integrated surface and airspace operations, modeling Charlotte Douglas International Airport, to evaluate the operational procedures and information requirements for the tactical surface metering tool, and data exchange elements between the airline controlled ramp and ATC Tower. In this paper, we focus on the calibration of the tactical surface metering tool using various metrics measured from the HITL simulation results. Key performance metrics include gate hold times from pushback advisories, taxi-in/out times, runway throughput, and departure queue size. Subjective metrics presented in this paper include workload, situational awareness, and acceptability of the metering tool and its calibration

NASA's UAS Traffic Management (UTM) project concluded its second flight demonstration activity in late October 2016. This activity demonstrated the capabilities and functionality incorporated into its Technical Capability Level 2 (TCL2) concept, which envisions future operations that are low density, capable of being performed over sparsely populated areas, and allow for a concurrent mix of longer duration, beyond visual-line-of-sight flights and shorter flights within visual-line-of-sight (VLOS). To incorporate these features into a flight demonstration, a scenario-based approach was taken to address different aspects of the TCL2 environment and to meet defined objectives. This paper will describe elements of how the flight activity was conducted and present analyses regarding UTM operations, system messages, and alerting as they pertained to meeting the demonstration objectives and shedding light on research questions and lessons learned.NASA was able to successfully demonstrate complex UTMoperations in a TCL 2 environment in collaboration withindustry partners and the Reno-Stead Airport UAS test range.A scenario-based approach to the demonstration provided arelevant means through which the key elements and objectivesof the test could be captured. Although issues were identifiedthrough the testing and feedback of test participants, theoverall results were in line with the overall UTM objective ofsafely enabling large-scale UAS operations in low altitudeairspace.

The purpose of this paper is to report on a human factors evaluation of ground control station design concepts for interacting with an unmanned traffic management system. The data collected for this paper comes from recent field tests for NASA's Unmanned Traffic Management (UTM) project, and covers the following topics; workload, situation awareness, as well as flight crew communication, coordination, and procedures. The goal of this evaluation was to determine if the various software implementations for interacting with the UTM system can be described and classified into design concepts to provide guidance for the development of future UTM interfaces. We begin with a brief description of NASA's UTM project, followed by a description of the test range configuration related to a second development phase. We identified (post hoc) two classes in which the ground control stations could be grouped. This grouping was based on level of display integration. The analysis was exploratory and informal. It was conducted to compare ground stations across those two classes and against the aforementioned topics. Herein, we discuss the results.

In air traffic control, task demand and workload have important implications for the safety and efficiency of air traffic. Task demand is dynamic, however, research on demand transitions and associated controller perception and performance is limited. In addition, there is a comparatively restricted understanding of the influence of task demand transitions on workload and performance, in association with automation. This study used an air traffic control simulation to investigate the influence of task demand transitions and two conditions of varying automation, on workload and efficiency-related performance. Findings showed that a both the direction of the task demand variation, and the amount of automation, influenced the relationship between workload and performance. Further research is needed to enhance understanding of demand transition and workload history effects on operator experience and performance, in both air traffic control and other safety-critical domains.

A human-in-the-loop simulation study addressed terminal-area controller-workstation interface variations for interoperability between three new capabilities being introduced by the FAA. The capabilities are Terminal Sequencing and Spacing (TSAS), Automated Terminal Proximity Alert (ATPA), and wake-separation recategorization, or 'RECAT.' TSAS provides controllers with Controller-Managed Spacing (CMS) tools, including slot markers, speed advisories, and early/late indications, together with runway assignments and sequence numbers. ATPA provides automatic monitor, warning, and alert cones to inform controllers about spacing between aircraft on approach. ATPA cones are sized according to RECAT, an improved method of specifying wake-separation standards. The objective of the study was to identify potential issues and provide recommendations for integrating TSAS with ATPA and RECAT. Participants controlled arrival traffic under seven different display configurations, then tested an 'exploratory' configuration developed with participant input. All the display conditions were workable and acceptable, but controllers strongly preferred having the CMS tools available on Feeder positions, and both CMS tools and ATPA available on Final positions. Controllers found the integrated systems favorable and liked being able to tailor configurations to individual preferences.