Terminal Area Test Vector Development

Calhoun, Sean; Rorie, Conrad; Lewis, Todd; Jack, Devin; Hoffler, Keith

NASA NTRS · 20190027686

Terminal Area Test Vector Development

Calhoun, Sean·Rorie, Conrad·Lewis, Todd·Jack, Devin·Hoffler, Keith

Abstract

This presentation provides an overview of work being done to develop test vectors for the terminal area, in coordination with RTCA Special Committee 228, an organization developing the Minimum Operational Performance Standards (MOPS) for Unmanned Aircraft Systems (UAS) Detect and Avoid (DAA) systems. The work leverages existing encounter data to develop a set of encounters to be used to define and refine both performance-based and functionally-based terminal area MOPS requirements. The encounter set would be used across various organizations supporting MOPS terminal area requirements development to provide some level of consistency in terms of terminal area assumptions. The work will investigate other potentially applicable data sets and make any similarly needed adjustments to arrive at a consolidated set of terminal area encounters.

Explore related subjects

terminal area test vector

Keep this discovery

Explore connections, maps & timelines

BibTeX RIS

Calhoun, Sean, Rorie, Conrad, Lewis, Todd, Jack, Devin, Hoffler, Keith. 2019-06-12. Terminal Area Test Vector Development. https://ntrs.nasa.gov/citations/20190027686

Cite the original work for its findings. Save a collection to share your selection of sources.

NASA NTRS2018

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↗

NASA NTRS2017

Trajectory Specification for Terminal Air Traffic: Pairwise Conflict Detection and Resolution

Trajectory Specification is the explicit bounding and control of aircraft trajectories such that the position at any 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 navigation capabilities and the current traffic situation. Assuming conformance, Trajectory Specification can guarantee safe separation for an arbitrary period of time even in the event of an air traffic control (ATC) system or datalink failure; hence it can help to achieve the high level of safety and reliability needed for ATC automation. It can also reduce the reliance on tactical backup systems during normal operation. This paper applies it to the terminal area around a major airport and presents algorithms and software for detecting and resolving conflicts. A representative set of pairwise conflicts was generated, and a fast-time simulation was run on them. All conflicts were successfully resolved in real time, demonstrating the computational feasibility of the concept.