Analysis of Traffic Conflicts in a Mixed-Airspace Evaluation of Airborne Separation Assurance

A pair of human-in-the-loop simulation evaluations of a distributed air/ground separation assurance system have been conducted to investigate the function allocation between humans and automation systems as well as ground-based and airborne agents in the Next Generation Air Transportation System and beyond. This paper focuses on an analysis of certain critical conflicts observed between self-separating aircraft and ground-managed traffic in the same airspace. The principal cause of each conflict is identified and potential mitigations are discussed, such as: the sharing of trajectory intent information between the ground and the air; more cautious trajectory planning by the self-separating aircraft; and more equitable rules-of-the-road between the self-separating aircraft and ground-managed aircraft. This analysis will inform the ongoing design of an airborne separation assurance automation tool

A Turn-Projected State-Based Conflict Resolution Algorithm

State-based conflict detection and resolution (CD&R) algorithms detect conflicts and resolve them on the basis on current state information without the use of additional intent information from aircraft flight plans. Therefore, the prediction of the trajectory of aircraft is based solely upon the position and velocity vectors of the traffic aircraft. Most CD&R algorithms project the traffic state using only the current state vectors. However, the past state vectors can be used to make a better prediction of the future trajectory of the traffic aircraft. This paper explores the idea of using past state vectors to detect traffic turns and resolve conflicts caused by these turns using a non-linear projection of the traffic state. A new algorithm based on this idea is presented and validated using a fast-time simulator developed for this study

The Effects of Limited Intent Information Availability on Self-Separation in Mixed Operations

This paper presents the results of a computer simulation of the NASA Autonomous Flight Rules (AFR) concept for airborne self-separation in airspace shared with conventional Instrument Flight Rules (IFR) traffic. This study was designed to determine the impact of varying levels of intent information from IFR aircraft on the performance of AFR conflict detection and resolution. The study used Automatic Dependent Surveillance-Broadcast (ADS-B) to supply IFR intent, but other methods such as an uplink from a ground-based System Wide Information Management (SWIM) network could alternatively supply this information. The independent variables of the study consist of the number of ADS-B trajectory change reports broadcast by IFR aircraft and the time interval between those reports. The conflict detection and resolution metrics include: the number of conflicts and losses of separation, the average conflict warning time, and the amount of time spent in strategic vs. tactical flight modes (i.e., whether the autoflight system was decoupled from the planned route in the Flight Management System in order to respond to a short-notice traffic conflict). The results show a measurable benefit of broadcasting IFR intent vs. relying on state-only broadcasts. The results of this study will inform ongoing separation assurance research and FAA NextGen design decisions for the sharing of trajectory intent information in the National Airspace System

Function Allocation between Automation and Human Pilot for Airborne Separation Assurance

Maintaining safe separation between aircraft is a key determinant of the airspace capacity to handle air transportation. With the advent of satellite-based surveillance, aircraft equipped with the needed technologies are now capable of maintaining awareness of their location in the airspace and sharing it with their surrounding traffic. As a result, concepts and cockpit automation are emerging to enable delegating the responsibility of maintaining safe separation from traffic to the pilot; thus increasing the airspace capacity by alleviating the limitation of the current non-scalable centralized ground-based system. In this paper, an analysis of allocating separation assurance functions to the human pilot and cockpit automation is presented to support the design of these concepts and technologies. A task analysis was conducted with the help of Petri nets to identify the main separation assurance functions and their interactions. Each function was characterized by three behavior levels that may be needed to perform the task: skill, rule and knowledge based levels. Then recommendations are made for allocating each function to an automation scale based on their behavior level characterization and with the help of Subject matter experts

The Complexity of Pebbling in Diameter Two Graphs*

Given a simple, connected graph, a pebbling configuration is a function from its vertex set to the nonnegative integers. A pebbling move between adjacent vertices removes two pebbles from one vertex and adds one pebble to the other. A vertex r is said to be reachable from a configuration if there exists a sequence of pebbling moves that places one pebble on r. A configuration is solvable if every vertex is reachable. We prove tight bounds on the number of vertices with two and three pebbles that an unsolvable configuration on a diameter two graph can have in terms of the size of the graph. We also prove that determining reachability of a vertex is NP-complete, even in graphs of diameter two

Pilot Subjective Assessments During an Investigation of Separation Function Allocation Using a Human-In-The-Loop Simulation

Two human-in-the-loop simulation experiments were conducted to investigate allocation of separation assurance functions between ground and air and between humans and automation. The experiments modeled a mixed-operations concept in which aircraft receiving ground-based separation services shared the airspace with aircraft providing their own separation service (i.e., self-separation). The two experiments, one pilot-focused and the other controller-focused, addressed selected key issues of mixed operations and modeling an emergence of NextGen technologies and procedures. This paper focuses on the results of the subjective assessments of pilots collected during the pilot-focused human-in-the-loop simulation, specifically workload and situation awareness. Generally the results revealed that across all conditions, pilots' perceived workload was low to medium, with the highest reported levels of workload occurring when the pilots experienced a loss of separation during the scenario. Furthermore, the results from the workload data and situation awareness data were complimentary such that when pilots reported lower levels of workload they also experienced higher levels of situation awareness

In-Flight Evaluation of the Traffic Aware Planner on the NASA HU-25A Guardian Aircraft

NASAs Traffic Aware Planner (TAP) software is a research-prototype decision support tool that provides pilots with time- and fuel-saving route recommendations that optimize their current trajectory. The software runs on a first-of-a-kind system architecture onboard three aircraft in revenue service conducting operational evaluations with a major domestic airline. Therefore, significant NASA-internal testing is required prior to releasing the software to the partner airline. This paper describes a flight test plan that exercises the functionality of the TAP software in a representative operational environment, describes the system architecture developed and implemented for the NASA Langley HU-25A Guardian aircraft to support the test objectives, presents outcomes of the flight test campaign, and discusses use cases that demonstrate the value of flight testing for this activity.Research into flight path optimization of transport aircraft conducted by the National Aeronautics and SpaceAdministration (NASA) has produced an operational concept known as Traffic Aware Strategic Aircrew Requests(TASAR) [1, 2]. This near-term concept [3] provides the aircrew with a flight deck decision support tool known asthe Traffic Aware Planner (TAP). The TAP software leverages a growing number of information sources on the flightdeck to make time- and fuel-saving route optimization recommendations to the aircrew while en route. The aircrewcan then use the suggestions provided by the tool to make route change requests with a greater likelihood of acceptanceby air traffic control (ATC). Since TASAR is a concept intended for the current operational environment, it isintentionally designed to have no safety-critical impact or require any changes to current Federal AviationAdministration (FAA) rules and procedures [4, 5].The research prototype TAP system [68], explained further in Section III.C, continually incorporates up-to-dateaircraft state data from onboard avionics, as well as the latest position of surrounding traffic, the most recent windforecast, and the most recent convective weather forecast, in order to calculate candidate trajectory modifications thatimprove upon the current active route. These trajectories account for user-selectable objective functions [3] of reducedfuel burn, reduced flight time, or an airline-derived combination of factors known as trip cost. Previous analyses andsimulations have estimated substantial savings for airlines employing this technique within the U.S. National AirspaceSystem (NAS) [911]. Operational evaluations with Alaska Airlines seek to validate these projected benefits usingmeasured data while simultaneously providing benefits to the airline [12, 13].The TAP software has undergone a number of human-in-the-loop simulations [14] and flight test activities[1517] in order to validate the operational concept, evaluate human factors considerations (e.g., workload, usability,distraction, etc.), and to assess the ability of the software to function in a representative operational environment (e.g.,connected to live avionics data, using in-flight internet connectivity, etc.). However, these simulations and flight testcampaigns did not account for the hardware architecture implemented on the three aircraft for Alaska Airlinesoperational evaluations of the TAP software. Therefore, a need was identified to thoroughly test the functionality ofthe software in a similar hardware architecture to that of the partner airlines aircraft. Information regarding testapparatus and environments used to evaluate TAP prior to testing on the HU-25A can be found in reference [18].A campaign of flight trials on a NASA aircraft, the HU-25A Guardian, was conducted to ensure that the researchprototype TAP system functions well in a configuration similar to the Alaska Airlines aircraft prior to deployment.This airborne, networked environment enables an assessment of the operational factors unique to the flight environment. Additionally, this activity evaluated the effectiveness and benefit of new TAP functionality andoperation in a relevant flight environment while allowing the rapid prototyping of new concepts and features.This paper is organized as follows: Section II discusses the details of the flight test plan, flight profiles, and theduties of personnel involved with conducting flight operations. Section III describes the test platform, avionicsequipage, and system architecture. Section IV presents a discussion of results, and Section V contains concludingremarks

Radiation Test Challenges for Scaled Commerical Memories

As sub-100nm CMOS technologies gather interest, the radiation effects performance of these technologies provide a significant challenge. In this talk, we shall discuss the radiation testing challenges as related to commercial memory devices. The focus will be on complex test and failure modes emerging in state-of-the-art Flash non-volatile memories (NVMs) and synchronous dynamic random access memories (SDRAMs), which are volatile. Due to their very high bit density, these device types are highly desirable for use in the natural space environment. In this presentation, we shall discuss these devices with emphasis on considerations for test and qualification methods required

On the Substitution of Identicals in Counterfactual Reasoning

It is widely held that counterfactuals, unlike attitude ascriptions, preserve the referential transparency of their constituents, i.e., that counterfactuals validate the substitution of identicals when their constituents do. The only putative counterexamples in the literature come from counterpossibles, i.e., counterfactuals with impossible antecedents. Advocates of counterpossibilism, i.e., the view that counterpossibles are not all vacuous, argue that counterpossibles can generate referential opacity. But in order to explain why most substitution inferences into counterfactuals seem valid, counterpossibilists also often maintain that counterfactuals with possible antecedents are transparency‐preserving. I argue that if counterpossibles can generate opacity, then so can ordinary counterfactuals with possible antecedents. Utilizing an analogy between counterfactuals and attitude ascriptions, I provide a counterpossibilist‐friendly explanation for the apparent validity of substitution inferences into counterfactuals. I conclude by suggesting that the debate over counterpossibles is closely tied to questions concerning the extent to which counterfactuals are more like attitude ascriptions and epistemic operators than previously recognized

Weather Design Considerations for the TASAR Traffic Aware Planner

The Traffic Aware Planner (TAP) is a decision support automation tool for trajectory planning and optimization intended for use on todays flight deck. Drawing from a variety of on- and off-board data sources, TAP employs a sophisticated trajectory optimization algorithm that provides the aircrew with fuel- and time-saving reroute recommendations that are free of known conflicts with traffic, special use airspace, and severe convective weather. As this kind of weather is a significant part of the pilots decision-making process while planning trajectory changes en route, a series of investigations has been conducted into the integration of weather data and associated functionality into the TAP software. This paper reviews the weather data sources and functionality that have been incorporated into TAP to date, along with experience gathered in the course of the design process