Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “NAS Integration”

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 217 records · Page 12

Appendix A: NAS-Wide Encounter Rate Evaluation Using Historical Radar Data and the Airspace Concept Evaluation System (ACES)

Regulations that establish operational and performance requirements for unmanned aircraft systems (UAS) are being developed by a consortium of government, industry and academic institutions. Those requirements will apply to detect-and-avoid (DAA) systems and other equipment necessary to integrate UAS with the National Airspace System (NAS) and are determined according to their contribution to the overall level of safety required to operate in the airspace. Several key gaps must be addressed in order to link equipment requirements to an airspace level of safety. Foremost among these is the calculation of the relative effectiveness of a particular system to mitigate violations of a separation standard with other aircraft, which is known as the systems risk ratio. The risk ratio is calculated as the probability of mid-air collision with a DAA system divided by the probability of mid-air collision without a DAA system. The risk ratio of a DAA system, in combination with the risk ratios of other collision avoidance mitigations, will determine the overall safety of the airspace measured in terms of the number of mid-air collisions per flight hour. Defining the required risk ratio that the DAA system needs to ensure the safety of the airspace requires an evaluation of the current airspace and a simulated evaluation that incorporates UAS aerodynamic performance and the mission characteristics of future UAS operations that are projected to be conducted in areas that interact with current operations. These evaluations will produce the frequency of encounters that currently exist in the airspace and those that could be generated with the introduction of UAS. Together, the frequency of encounters, an evaluation of unmitigated risk of collision, and a desired level of safety of the airspace will yield a required risk ratio of the DAA system. This study will focus on evaluating the encounter rates between aircraft based on historical radar data and encounter rates that could occur based on simulated UAS missions.

Unmanned Aircraft Systems↗

Identifying Common Coordination Procedures across Extensible Traffic Management (xTM) to Integrate xTM Operations into the National Airspace System

New categories of missions and vehicle types, such as drone delivery services, on-demand air taxi, and high-altitude long-endurance (HALE) vehicles are being proposed to operate using a novel, highly automated information exchange infrastructure and a community-based, cooperative traffic management concept. Collectively, these new operations are called Extensible Traffic Management (xTM). As these xTM vehicles become more prevalent, their operations will increasingly overlap with existing conventional aircraft and with each other. In order to seamlessly co-exist with current conventional aircraft operations, new coordination procedures, tools and services will be needed to integrate xTM into the future National Airspace System (NAS). In our prior work, we have identified a set of use cases for xTM interactions with air traffic control (ATC), categorized across different xTM operations based on trigger events. Events consisted of ones such as nominal xTM vehicle transition into the ATC environment or an off-nominal emergency landing situation. In this paper, we have extended the prior work to identify commonalities in the coordination procedures across xTM, as well as differences that are specific to the individual xTM operations. The overall results showed that two types of xTM-ATC interactions were prevalent: 1) xTM vehicles transitioning between xTM and ATC operational environments; 2) xTM vehicles being allowed to continue xTM operations in areas that are normally controlled by ATC. The results also suggested that emergency and rare off-nominal events may need specialized procedures for each vehicle type. The overall results suggest that there is a pathway to define a common method of handling and integrating diverse xTM operations in the future NAS, but there need to be procedures for individualized handling of xTM vehicles in infrequent, safety-critical events.

Extensible Traffic Management (xTM)↗

Considerations in the Integration of Small Aircraft Transportation System Higher Volume Operations (SATSHVO) in the National Airspace System (NAS)

The Small Aircraft Transportation System Higher Volume Operations (SATS HVO) concept holds the promise for increased efficiency and throughput at many of the nations under-used airports. This concept allows for concurrent operations at uncontrolled airports that under today s procedures are restricted to one arrival or one departure operation at a time, when current-day IFR separation standards are applied. To allow for concurrent operations, SATS HVO proposes several fundamental changes to today's system. These changes include: creation of dedicated airspace, development of new procedures and communications (phraseologies), and assignment of roles and responsibilities for pilots and controllers, among others. These changes would affect operations on the airborne side (pilot) as well as the groundside (controller and air traffic flow process). The focus of this paper is to discuss some of the issues and potential problems that have been considered in the development of the SATS HVO concept, in particular from the ground side perspective. Reasonable solutions to the issues raised here have been proposed by the SATS HVO team, and are discussed in this paper.

Lohr, Gary W.↗

Aircraft Loss of Control: Problem Analysis for the Development and Validation of Technology Solutions

Aircraft loss of control (LOC) is a leading cause of fatal accidents across all transport airplane and operational classes. LOC can result from a wide spectrum of precursors (or hazards), often occurring in combination. Technologies developed for LOC prevention and recovery must therefore be effective under a wide variety of conditions and uncertainties, including multiple hazards, and the validation process must provide a means of assessing system effectiveness and coverage of these hazards. This paper provides a detailed description of a methodology for analyzing LOC as a dynamics and control problem for the purpose of developing effective technology solutions. The paper includes a definition of LOC based on several recent publications, a detailed description of a refined LOC accident analysis process that is illustrated via selected example cases, and a description of planned follow-on activities for identifying future potential LOC risks and the development of LOC test scenarios. Some preliminary considerations for LOC of Unmanned Aircraft Systems (UAS) and for their safe integration into the National Airspace System (NAS) are also discussed.

Belcastro, Christine M.↗

The Generic Resolution Advisor and Conflict Evaluator (GRACE) for Detect-And-Avoid Systems

Java Architecture for Detect-And-Avoid (DAA) Extensibility and Modeling (JADEM) was developed at NASA Ames Research Center as a research and modeling tool for Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS). UAS will be required to have DAA systems in order to fulfill the regulatory requirement to remain well clear'' of other traffic. JADEM supports research on technological requirements and Minimum Operational Performance Standards (MOPS) for UAS DAA systems by providing a flexible and extensible software platform that includes models and algorithms for all major DAA functions. This paper describes one of these algorithms, the Generic Resolution Advisor and Conflict Evaluator (GRACE). GRACE supports two core DAA functions: threat evaluation and guidance. GRACE is generic in the sense that it is designed to work with any aircraft or sensor type (both cooperative and non-cooperative), and to be used in various applications and DAA guidance concepts, thus supporting evolving MOPS requirements and research. GRACE combines flexibility, robustness, and computational efficiency. It has modest memory requirements and can handle multiple cooperative and noncooperative intruders. GRACE has been used as a core JADEM component in several real-time and fast-time experiments, including human-in-the-loop simulations and live flight tests.

detect and avoid↗

The Generic Resolution Advisor and Conflict Evaluator (GRACE) for Unmanned Aircraft Detect-And-Avoid Systems

The paper describes the Generic Resolution Advisor and Conflict Evaluator (GRACE), a novel alerting and guidance algorithm that combines flexibility, robustness, and computational efficiency. GRACE is generic since it was designed without any assumptions regarding temporal or spatial scales, aircraft performance, or its sensor and communication systems. Therefore, GRACE was adopted as a core component of the Java Architecture for Detect-And-Avoid (DAA) Extensibility and Modeling, developed by NASA as a research and modeling tool for Unmanned Aerial Systems Integration in the National Airspace System (NAS). GRACE has been used in a number of real-time and fast-time experiments supporting evolving requirements of DAA research, including parametric studies, NAS-wide simulations, human-in-the-loop experiments, and live flight tests.

Unmanned Aircraft↗

Automatic Execution of Collision Avoidance and Return to Course Analysis (D.6.20) Experiment Review

This presentation details the experimental design for an upcoming engineering analysis of a mock version of the Airborne Collision Avoidance System (ACAS), specifically the 'Xu' variant, which is designed for unmanned aircraft platforms. As a component of the Unmanned Aircraft System (UAS) Integration into the National Airspace System (NAS) project, this engineering analysis intends to study aspects of ACAS Xu in two parts. In the first phase of the study, the display and alerting guidance for collision avoidance (CA) resolution advisories (RA) shown to pilots at a ground control station will be manipulated, varying in level of RA transparency and presentation of safe maneuver parameters. The second phase of the engineering analysis will examine pilots' response to increasing levels of automation in the tasks of collision avoidance and return-to-course (RTC).

Sadler, Garrett↗

Low Size, Weight, and Power (SWaP) Experiments 1 & 2 Flight Test Series 6 VIP Day

This presentation provides an overview of two recently completed human-in-the-loop simulations, conducted as part of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. These studies investigated the effects of shorter RADAR surveillance ranges on DAA system performance. They were designed to serve as a validation of the fast-time simulation work performed by other groups working on the UAS-NAS project. They were also intended to establish a baseline for the Flight Test 6 Full Mission configuration flights. Low SWaP HITL 1 examined system performance with two candidate non-cooperative DAA well clear (DWC) definitions with a RADAR declaration range of 3.5nm. Low SWaP HITL 2 looked at DAA system performance with four different RADAR declaration ranges (1.5, 2.0, 2.5, & 3.0nm) with a non-cooperative DWC definition of 450ft vertical separation and 2200ft horizontal separation. The results of each study and the implications for FT6 are discussed.

Rorie, Conrad↗

Flight Test 6 VIP Day: A Little Bit of How We Got Here

This presentation provides an overview of the Detect and Avoid subproject of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. It discusses efforts and contributions for Phase 1 and on-going work for Phase 2.

Shively, Jay↗

UAS Concept of Operations and Vehicle Technologies Demonstration

In 2017 and 2018, under National Aeronautics and Space Administration (NASA) sponsorship, the New York Unmanned Aircraft Systems (UAS) Test Site and Northeast UAS Airspace Integration Research (NUAIR) Alliance conducted a year-long research project that culminated in a UAS technology flight demonstration. The research project included the creation of a concept of operations, and development and demonstration of UAS technologies. The concept of operations was focused on an unmanned aircraft transiting from cruise through Class E airspace into a high-density urban terminal environment. The terminal environment in which the test was conducted was Griffiss International Airport, under Syracuse Air Traffic Control (ATC) approach control and Griffiss control tower. Employing an Aurora Centaur optionally piloted aircraft (OPA), this project explored six scenarios aimed at advancing UAS integration into the National Airspace System (NAS) under both nominal and off-nominal conditions. Off-nominal conditions were defined to include complete loss of the communications link between the remote pilot’s control station on the ground and the aircraft. The off-nominal scenarios that were investigated included lost-link conditions with and without link recovery, an automated ATC initiated go-around, autonomous rerouting around a dynamic airspace obstruction (in this case simulated weather), and autonomous taxi operations to clear the runway.

Swieringa, Kurt↗

Display and Automation Considerations for the Airborne Collision Avoidance System Xu

In this paper we examine several display and automation considerations of a collision avoidance system that is currently under development: the Airborne Collision Avoidance System (ACAS) Xu. This study builds on previous work conducted as part of NASA’s Unmanned Aircraft Systems (UAS) Integration into the National Airspace System (NAS) project. ACAS Xu represents the next-generation successor to the Traffic Alert and Collision Avoidance System (TCAS II), wherein the Xu variant is intended for UAS applications. Whereas TCAS II exclusively issues RAs in the vertical dimension, a major distinction between ACAS Xu and previous collision avoidance (CA) systems is the introduction of horizontal and “blended” RAs (i.e., RAs with both horizontal and vertical components). This present work was conducted as an engineering analysis involving two parts. In Part 1, a two-by-two, within-subjects study was performed that manipulated how RAs were presented to a pilot situated at a UAS ground control station. Five participants experienced four experimental trials in which text and aural alerting characteristics were manipulated. In Part 2, another five participants experienced four trials in which the levels of automation were manipulated with regard to the CA and return-to-course (RTC) tasks. The results for Part 1 found no effect of display or alerting configuration on pilot performance. However, it was discovered that pilot response time to RAs greatly depended on the RA type. In particular, pilots were quicker to respond to vertical RAs (M = 4.52 seconds) than horizontal (M = 7.42 seconds) and blended (M = 9.68 seconds) RAs in which both dimensions were issued simultaneously. For Part 2 of the study, pilots found both auto-CA and auto-RTC functions equally useful. Most pilots were comfortable with the automation, however responses were mixed. Three of five participants indicated high levels of comfort with the auto-CA function, while two rated their comfort as low. Pilots’ comfort for the auto-RTC functionality was slightly higher: four out of five pilots gave high ratings, while one pilot gave a low rating. Overall, pilots ordinally ranked their preference for automated functions as auto-CA together with auto-RTC (when an aural alert announces a change between CA and RTC states), auto-CA, and auto-CA and RTC (without the aural state-change announcement). Recommendations for improving the display of automation are also discussed.

collision avoidance↗

Display and Automation Considerations for the Airborne Collision Avoidance System Xu

In this presentation we examine several display and automation considerations of a collision avoidance system that is currently under development: the Airborne Collision Avoidance System (ACAS) Xu. This study builds on previous work conducted as part of NASA’s Unmanned Aircraft Systems (UAS) Integration into the National Airspace System (NAS) project. ACAS Xu represents the next-generation successor to the Traffic Alert and Collision Avoidance System (TCAS II), wherein the Xu variant is intended for UAS applications. Whereas TCAS II exclusively issues RAs in the vertical dimension, a major distinction between ACAS Xu and previous collision avoidance (CA) systems is the introduction of horizontal and “blended” RAs (i.e., RAs with both horizontal and vertical components). This present work was conducted as an engineering analysis involving two parts. In Part 1, a two-by-two, within-subjects study was performed that manipulated how RAs were presented to a pilot situated at a UAS ground control station. Five participants experienced four experimental trials in which text and aural alerting characteristics were manipulated. In Part 2, another five participants experienced four trials in which the levels of automation were manipulated with regard to the CA and return-to-course (RTC) tasks. The results for Part 1 found no effect of display or alerting configuration on pilot performance. However, it was discovered that pilot response time to RAs greatly depended on the RA type. In particular, pilots were quicker to respond to vertical RAs (M = 4.52 seconds) than horizontal (M = 7.42 seconds) and blended (M = 9.68 seconds) RAs in which both dimensions were issued simultaneously. For Part 2 of the study, pilots found both auto-CA and auto-RTC functions equally useful. Most pilots were comfortable with the automation, however responses were mixed. Three of five participants indicated high levels of comfort with the auto-CA function, while two rated their comfort as low. Pilots’ comfort for the auto-RTC functionality was slightly higher: four out of five pilots gave high ratings, while one pilot gave a low rating. Overall, pilots ordinally ranked their preference for automated functions as auto-CA together with auto-RTC (when an aural alert announces a change between CA and RTC states), auto-CA, and auto-CA and RTC (without the aural state-change announcement). Recommendations for improving the display of automation are also discussed.

collision avoidance↗

Overview of NASA's Air Traffic Management - eXploration (ATM-X) Project

Projected increases in new vehicle types, new missions, and the continual growth in traditional (e.g., airlines, general aviation) aviation will require changes to the current air traffic system, particularly to accommodate the desire of operators to be more involved in air traffic decisions. To address these challenges, the National Airspace System needs to undergo a transformation to a more scalable, flexible, user-focused system that addresses safety and security requirements and resiliency for current and new users. A system designed to integrate modular software services, provided by users, third parties and government for air traffic management functions, will be scalable and more easily allow modernization and for collaboration between users and service providers. ATM-X is responding to NASA's pivot towards integrating projected new, diverse entrants into the NAS, while also leveraging NASA's prior ATM achievements that continue to improve traditional airspace operations. This project is a two-phased approach to conduct research and focused evaluations to assess the feasibility of a service-based approach and to identify critical design considerations to enable airspace access for new entrants, integrated with current traditional operations. Phase 1 research will be conducted to determine what is needed to reach the ATM-X goals based on specific use-cases to enable large-scale, passenger-carrying Urban Air Mobility operations in a metroplex environment, and also to improve traditional operations in the Northeast Region leveraging mature NASA technologies. Some of these evaluations will be conducted in simulations and field activities. Phase 2 will build upon Phase 1 towards more defined, focused research and field demonstrations in real-world environments to integrate multiple elements of a scalable, service-based ATM-X concept.

air traffic management↗

Requirements for an Integrated UAS CNS Architecture

Communications, Navigation and Surveillance (CNS) requirements must be developed in order to establish a CNS architecture supporting Unmanned Air Systems integration in the National Air Space (UAS in the NAS). These requirements must address cybersecurity, future communications, satellite-based navigation and APNT, and scalable surveillance and situational awareness. CNS integration, consolidation and miniaturization requirements are also important to support the explosive growth in small UAS deployment. Air Traffic Management (ATM) must also be accommodated to support critical Command and Control (C2) for Air Traffic Controllers (ATC). This document therefore presents UAS CNS requirements that will guide the architecture.

Templin, Fred L.↗

Security Risk Assessment Process for UAS in the NAS CNPC Architecture

This informational paper discusses the risk assessment process conducted to analyze Control and Non-Payload Communications (CNPC) architectures for integrating civil Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS). The assessment employs the National Institute of Standards and Technology (NIST) Risk Management framework to identify threats, vulnerabilities, and risks to these architectures and recommends corresponding mitigating security controls. This process builds upon earlier work performed by RTCA Special Committee (SC) 203 and the Federal Aviation Administration (FAA) to roadmap the risk assessment methodology and to identify categories of information security risks that pose a significant impact to aeronautical communications systems. A description of the deviations from the typical process is described in regards to this aeronautical communications system. Due to the sensitive nature of the information, data resulting from the risk assessment pertaining to threats, vulnerabilities, and risks is beyond the scope of this paper

data links↗

Security Risk Assessment Process for UAS in the NAS CNPC Architecture

This informational paper discusses the risk assessment process conducted to analyze Control and Non-Payload Communications (CNPC) architectures for integrating civil Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS). The assessment employs the National Institute of Standards and Technology (NIST) Risk Management framework to identify threats, vulnerabilities, and risks to these architectures and recommends corresponding mitigating security controls. This process builds upon earlier work performed by RTCA Special Committee (SC) 203 and the Federal Aviation Administration (FAA) to roadmap the risk assessment methodology and to identify categories of information security risks that pose a significant impact to aeronautical communications systems. A description of the deviations from the typical process is described in regards to this aeronautical communications system. Due to the sensitive nature of the information, data resulting from the risk assessment pertaining to threats, vulnerabilities, and risks is beyond the scope of this paper.

Iannicca, Dennis C.↗

PAAV Tabletop 4 Results – Integrating m:N Remotely Piloted Operations

NASA's Pathfinding for Airspace with Autonomous Vehicles (PAAV) sub-project is investigating procedures and technologies to facilitate seamless integration of future UAS operations into the NAS. The Tabletop 4 activity solicited subject matter expertise to identify solutions to the potential challenges expected when the remote pilot-to-vehicle ratio scales from 1:1 to m:N, where one or more ground-based pilots control multiple uncrewed aircraft. This presentation details the method and high-level results of the PAAV Tabletop 4 activity.

m:N↗