Search NASA⌕ Search

SEARCH · Search NASA

Results for “RTCA”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

Investigating the Impacts of a Separation Standard for UAS Operations in Enroute and Transition Airspace

Unmanned aircraft systems will be required to equip with a detect and avoid system in order to satisfy the federal aviation regulations to remain well clear of other aircraft. To comply with regulations in today’s operations manned aircraft must “see and avoid” other aircraft and use subjective judgment to determine whether those aircraft are well clear. For a detect-and- avoid (DAA) system to satisfy the requirement to stay well clear, a quantitative definition of well clear needs to be defined and evaluated. Definitions for the boundary of well clear have been proposed by the Unmanned Aircraft System (UAS) Executive Committee Science and Research Panel (SaRP) and the Radio Technical Commission for Aeronautics (RTCA) Special Committee 228 on Detect and Avoid Systems. This study investigates the interoperability implications of UAS using proposed well clear definitions as a separation standard for conducting operations in the national airspace system. The first analysis in the study focuses on the effect of variations in well clear definition parameters on the rate of losses of well clear per flight hour. The second analysis considers three well clear definitions and presents the relative state conditions of intruder aircraft as they encroach upon the well clear boundary. The third analysis focuses on the definition of the alerting criteria needed to inform the UAS operator of a potential loss of well clear. All three analyses are conducted in a NAS-wide fast-time simulation environment using UAS aircraft models, proposed UAS missions, and historical air defense radar data to populate the background traffic operating under visual flight rules. The results from the three analyses presented in this study inform the safety case, requirements development, and the operational environment for the DAA minimum operational performance standards.

UAS Seperation Standard↗
NASA NTRS2016

Simulation and Flight Test Data Collection Review for Supporting Phase 1 Detect and Avoid MOPS

RTCA Special Committee 228 is a consortium of government, industry, and academic organizations tasked to develop minimum operational performance standards for UAS detect and avoid systems. The UAS in the NAS (National Airspace System) project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. Over the past 3 years, the project has executed a series of fast-time simulation, human-in-the-loop experiments, and flight tests in support of this effort. The purpose of this briefing is to summarize the models developed and data collected to overcome UAS integration barriers, so UAS can remain well clear of all traffic.

Santiago, Confesor↗
NASA NTRS2017

Validation of Minimum Display Requirements for a UAS Detect and Avoid System

The full integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS), a prerequisite for enabling a broad range of public and commercial UAS operations, presents several technical challenges to UAS developers, operators and regulators. A primary barrier is the inability for UAS pilots (situated at a ground control station, or GCS) to comply with Title 14 Code of Federal Regulations sections 91.111 and 91.113, which require pilots to “see and avoid” other aircraft in order to maintain well clear. UAS pilots’ removal from the flight deck of the aircraft necessitates the development of a UAS-specific system for detecting nearby traffic and displaying traffic information to the pilot to support their ability to maintain an objectively defined “DAA well clear” threshold from other aircraft. This new UAS-specific function of remaining DAA well clear is called traffic avoidance. The resulting Detect and Avoid (DAA) system, however, will be subject to a collection of requirements that manufacturers will be obligated to meet in order to certify their equipment. RTCA Special Committee 228 (SC-228), a consortium of representatives from government, industry and academia, is responsible for developing and documenting the Minimum Operational Performance Standards (MOPS) for UAS DAA systems. The present study is the final in a series of human-in-the-loop (HITL) experiments designed to explore and test the various display and alerting requirements being incorporated into the DAA MOPS. Whereas the prior DAA HITLs examined a wide variety of DAA display features and concepts, the current experiment aims to validate the latest minimum display requirements for Phase 1 of the DAA MOPS. Rather than test different display concepts, this study tests two configurations of a MOPS-compatible DAA display: a version that is integrated into the primary navigation and control display of the GCS and a version that is physically separated from the primary display. This manipulation tests the draft minimum requirement that allows the DAA traffic display to be a separate, or standalone, configuration. This type of configuration is a more achievable near-term technology solution since it does not stipulate additional certification or integration requirements on UAS manufacturers. However, a standalone display configuration has the potential to result in pilot performance issues resulting from the cognitive costs of switching between the primary DAA display and the primary navigation and control display. This configuration is also particularly susceptible to errors if the displays are in different orientations (e.g., north-up versus track-up). Both the integrated and standalone display configurations were presented to 16 active UAS pilots in a medium-fidelity simulation, which included confederate air traffic controllers and pseudo pilots operating simulated manned traffic. Pilots were tasked with navigating two different mission routes while maintaining DAA well clear with scripted conflicts. Pilot response times (i.e., measured response) and ability to remain DAA well clear are reported. Primary results indicate that both display configurations resulted in favorable response times and well clear rates. While there were clear trends of pilots objectively performing better in the integrated display condition, with several measured response metrics reaching statistical significance, the differences between the two displays were typically moderate. While the primary variable of DAA display location did not have an especially large impact on pilot performance on its own, when examined alongside the type of DAA threat the pilot was facing (a caution-level versus a warning-level alert), the response time benefits associated with the integrated display were amplified. The implications of these American Institute of Aeronautics and Astronautics 2 results on the Phase 1 DAA MOPS and the connection of this data to previous studies is also discussed.

detect and avoid↗
NASA NTRS2019

Terminal Area Test Vector Development

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.

terminal area↗
NASA NTRS2019

UAS Integration in the NAS Detect and Avoid Subproject: Kitty Hawk - NASA Collaboration Discussion

NASA is conducting research under the UAS Integration in the NAS Project to develop standards that will enable mid-size and large unmanned aircraft to fly unrestricted in the National Airspace System. As these efforts move into its second phase, NASA is planning a series of flight tests and demonstrations, integrating industry partners' technologies. These events will not only provide valuable data to inform the RTCA Special Committee 228 DAA and C2 MOPS, but also provide an opportunity for the UAS community to test their technologies in a realistic environment. An overview of NASA UAS-NAS research will be presented touching on human systems integration, modeling and simulation and guidance and control. Plans for Flight Test 6 and Systems Integration Operationalization (SIO) will also be presented. The purpose of this meeting is to share with Kitty Hawk, at a high level, UAS-NAS research and discuss potential future collaboration between NASA and Kitty Hawk.

Shively, Jay↗
NASA NTRS2018

Sensor Uncertainty Mitigation and Dynamic Well Clear Volumes in DAIDALUS

This paper presents recent updates to DAIDALUS (Detect & Avoid Alerting Logic for Unmanned Systems), a detect and avoid (DAA) software package for the integration of civil UAS into the airspace. DAIDALUS is the reference implementation of detect and avoid for unmanned aircraft systems chosen by RTCA Special Committee 228 (SC-228), and it is included in its corresponding Minimum Operational Performance Standards (MOPS) document, DO-365. This paper reports on the integration into DAIDALUS of two new capabilities, namely dynamic well clear volumes and sensor uncertainty mitigation.'

Narkawicz, Anthony↗
NASA NTRS2020

Detect-and-Avoid: Flight Test 6 Scripted Encounters Data Analysis

The Unmanned Aircraft System (UAS) in the National Airspace System (NAS) project conducted Flight Test 6 (FT6) in 2019. The ultimate goal of this flight test was to produce data to inform RTCA SC-228's Phase II Minimum Operational Performance Standards (MOPS) for Detect and Avoid (DAA) and Low Size, Weight, and Power Sensors. This report documents the analysis of scripted encounters' data. Scripted encounters own were analyzed and categorized based on the outcome of alert, maneuver guidance, and effectiveness of pilots' maneuver in resolving conflicts. Results indicate that UAS pilots' decisions as well as intruder maneuvers are leading factors that contribute to ineffective DAA maneuvers. Results also show that adding buffers to the DAA's suggested minimum turn angle improves effectiveness of the DAA maneuvers.

Wang, Wei-Ching↗
NASA NTRS2020

UAS Integration in the NAS Project: Overview of Flight Test Series 6

The National Aeronautics and Space Administration (NASA) Unmanned Aircraft Systems Integration in the National Airspace System (UAS-NAS) Project has conducted a series of flight test campaigns intended to support the reduction of barriers that prevent unmanned aircraft from flying without the required waivers from the Federal Aviation Administration (FAA). The 2019 Flight Test Series 6 (FT6) campaign furthered this path and supported three test configurations: 1) Radar Characterization, 2) Scripted Encounters and 3) Full Mission. Radar Characterization assessed the performance of Honeywell’s low size, weight, and power (low SWaP) radar system; Scripted Encounters investigated the timing of Detect and Avoid (DAA) alerting thresholds using a Department of Defense (DoD) Group 3 unmanned aircraft system (UAS) equipped with low SWaP sensors and three different live intruder aircraft flown at varying encounter geometries; and Full Mission validated human-in-the-loop simulations by collecting pilot performance data from a ground control station while controlling a live unmanned aircraft on a mission in both virtual and live air traffic controlled airspace. The subject pilot observed a research display that presented DAA advisories to maintain separation from live and virtual aircraft. The test was conducted over a twenty-week period within the R-2508 special use airspace located near Edwards Air Force Base (EAFB), CA. Over 240 encounters were flown during the test series and FT6 proved to be invaluable for the purposes of planning, managing, and executing this type of integrated flight test in both live and virtual environments. Data collected from FT6 was provided to the RTCA Special Committee 228 (SC-228) to help inform the Phase 2 Minimum Operational Performance Standards (MOPS). FT6 was the final test series for the UAS-NAS project that began in 2012. This paper provides an overview of FT6 and its success can be directly attributed to the diligent work of the men and women who supported this effort.

UAS in the NAS↗
NASA NTRS2021

UAS Integration in the NAS Flight Test 6: Full Mission Results

Recent standards development efforts for the integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) such as those in RTCA Inc. Special Committee 228 (SC-228) have focused on relatively large UAS transitioning to and from Class A airspace. In an effort to expand the range of vehicle classes that can access the NAS, the NASA UAS Integration in the NAS project has investigated Low Size, Weight, and Power (Low SWaP) technologies that would allow smaller UAS to detect-and-avoid (DAA) traffic. Through batch and human in the loop (HITL) simulation studies, the UAS Integration in the NAS DAA subproject have identified candidate performance standards that would contribute to enabling extended Low SWaP, UAS operations under 10,000 feet. These candidate performance standards include minimum field of regard (FOR) values for Low SWaP air surveillance sensors as well as a DAA well-clear (DWC) definition which can be applied to non-cooperative traffic to reduce the required maneuver initiation range. To test the assumptions of the project’s simulation studies and validate the candidate performance standards, a live flight research event was executed at NASA Armstrong Flight Research Center. The UAS Integration in the NAS Project Flight Test 6 Full Mission sought to characterize UAS pilot responses to traffic conflicts using a representative Low SWAP DAA system in an operational NAS environment. To achieve this, live, virtual and constructive distributed environment (LVC-DE) elements were combined to simulate a sector of Oakland center airspace and induce encounters with a live, manned aircraft. A Navmar Applied Sciences Tigershark XP was used as the UAS ownship and was integrated into the test architecture to enable it to be controlled from a Vigilant Spirit Control Station (VSCS) research ground control station. Qualified UAS pilots were recruited to act as subject pilots under test (SPUT) to control the Tigershark XP in a simulated mission while coordinating with a participating air traffic controller in simulated airspace. The intruder speed, intruder equipage and encounter geometry were varied between six scripted encounters per SPUT. Various metrics were collected including pilot reaction time from the onset of DAA alert, ATC coordination rate, probability and severity of losses of DAA well clear, and subjective ratings of system acceptability. The implications of these results on the development of standards for Low SWAP DAA systems will be discussed.

UAV↗
NASA NTRSDate not supplied

Detect-and-Avoid Maneuver Planning: Benefits of Including Route Recapture

Development of Detect-and-avoid (DAA) systems’ maneuver guidance requirements at RTCA has centered on tactical maneuvers away from the intruder. Recapturing the flight-plan route the initial maneuver is not directly taken into account by most DAA maneuver guidance algorithms. This work demonstrates potential challenges and inefficiencies that can arise in recapturing the route after resolving a conflict. Horizontal resolution trajectories for a test matrix of encounters with varying aircraft speeds and geometries are computed by minimizing either flight time or deviation to serve as a baseline. Turn directions computed from a reference DAA algorithm coupled with a pilot selection model and a second algorithm called Autoresolver (AR) are compared to these baseline resolution trajectories. Baseline results show that turning into the intruder yields favorable cost for most encounters. Additional analysis of pilot response data shows that only three-fourths of pilots’ horizontal maneuvers turn into intruders, a percentage much lower than the baseline results. Improvement to a DAA guidance algorithm based on findings in this work is discussed.

Route Recapture↗
NASA NTRSDate not supplied

Detect-and-Avoid Maneuver Planning: Benefits of Including Route Recapture

Development of Detect-and-avoid (DAA) systems’ maneuver guidance requirements at RTCA has centered on tactical maneuvers away from the intruder. Recapturing the flight-plan route the initial maneuver is not directly taken into account by most DAA maneuver guidance algorithms. This work demonstrates potential challenges and inefficiencies that can arise in recapturing the route after resolving a conflict. Horizontal resolution trajectories for a test matrix of encounters with varying aircraft speeds and geometries are computed by minimizing either flight time or deviation to serve as a baseline. Turn directions computed from a reference DAA algorithm coupled with a pilot selection model and a second algorithm called Autoresolver (AR) are compared to these baseline resolution trajectories. Baseline results show that turning into the intruder yields favorable cost for most encounters. Additional analysis of pilot response data shows that only three-fourths of pilots’ horizontal maneuvers turn into intruders, a percentage much lower than the baseline results. Improvement to a DAA guidance algorithm based on findings in this work is discussed.

Route Recapture↗
NASA NTRS2021

Retrospectively Documenting Satisfaction of the Overarching Properties: An Exploratory Prototype

Software-intensive aviation systems are typically developed in accordance with recognized development process, safety analysis, and software development standards such as SAE ARP4754A, SAE ARP4761, and RTCA DO-178C. Efforts to streamline assurance processes and make them flexible enough to handle future assurance challenges have produced the Overarching Properties (OPs) for airworthiness approval. Each of the three OPs is a property systems must possess to be certifiable. There is no mandated means of documenting possession of the OPs. To explore possible means, we have prepared retrospective documentation showing that a specimen software system possesses the OPs. The specimen system, Safeguard, enforces geofencing restrictions on unmanned aerial vehicles. Our OP-possession case for its airborne component comprises eight arguments in the Goal Structuring Notation (GSN): a main argument for each OP and five cross-cutting auxiliary arguments. We present this argument as an example for discussion and further research, e.g., into means of assessing OP possession.

safety case↗
NASA NTRS2021

Detect-and-Avoid Surveillance Range Requirements for Electro-Optical/Infra-Red Sensors

A detect-and-avoid (DAA) system provides surveillance, alerting, and maneuver guidance (referred to as guidance in this report) that are critical to an unmanned aircraft system’s (UAS) ability to maintain separation from manned aircraft and other unmanned aircraft. The last decade has seen significant progress in the development of DAA requirements, spearheaded by RTCA Special Committee 228 (SC228) and subsequently by other standards organizations such as EUROCAE and ASTM. SC-228’s development of DAA requirements assumes the UAS follows instrument flight rules (IFR) and has a remote pilot or operator in the loop. As of the publication of this document, the SC-228’s latest Minimum Operational Performance Standards (MOPS) for DAA, versioned as DO-365B [1], DAA systems use onboard and/or ground surveillance systems to detect traffic. The surveillance systems must detect both cooperative and non-cooperative air traffic. Cooperative traffic are vehicles that have a broadcasting transponder, while non-cooperative traffic do not, and so must be detected via radar or other sensors. A DAA system’s alerting and guidance functions alert the pilot/operator in the loop of potential hazards, such as intruder aircraft, and provide maneuver solutions which help the pilot/operator avoid or mitigate observed hazards. A UAS pilot is expected to coordinate with air traffic control (ATC) before executing a conflict avoidance maneuver if the type of alert is not urgent enough to require an immediate maneuver.

uncrewed aviation systems↗
NASA NTRS2022

PAAV Concept Document

The Pathfinding for Airspace with Autonomous Vehicles (PAAV) Concept Document, version 1.0, lays out the key challenges and potential solutions for the use of uncrewed aircraft (UA) technology for future regional air cargo operations. The challenges and solutions described in this document were informed by communications with the UA industry community (e.g., RTCA, the Federal Aviation Administration, and regional air cargo business operators), as well as the PAAV team’s research activities during the last two years including four tabletop exercises, a human-in-the-loop simulation study, a numerical simulation study, a functional allocation study, and flight data analysis (Appendix A). This document first describes the expected operational context of PAAV (Section 2), such as the flight mission, baseline UAS components, nominal operations, m:N operations (i.e., "m" remote pilots per "N" aircraft), and off-nominal operations. This context sets the scope for the PAAV concept development work. PAAV concept development assumes that UA operations will be increasingly autonomous. Thus, near- and far-term assumptions are defined (Section 3). PAAV identified seven key challenges for UA operations (Section 4): - Flight route planning - Separation and flow management - Traffic pattern integration - Contingency management - Taxi, takeoff, and landing - m:N operations - Communications operations The following 13 potential solutions to these challenges are then described (Section 5): - Scalable communications architecture - Data link - Designated UAS corridors - Crew planning for m:N operations - Flight route optimization - Traffic load-level control - Trajectory solutions with data link - Automated hazard avoidance for m:N operations - Traffic pattern integration (TPI) tool - Standard lost command and control (C2) link (LC2L) procedures - Automated hazard avoidance under LC2L - Auto-taxi, auto-takeoff, and auto-land - Ground control station (GCS) user interface for m:N operations The document attempts to link each of these solutions to one or more of the challenge areas. Novel solutions involving numerous automation technologies are needed to mitigate traffic and airspace management challenges, especially for realizing m:N operations and ensuring safety under LC2L conditions. The purpose of this document is to help understand alternatives and tradeoffs among potential solutions and provide a foundation for a cohesive PAAV concept that will be described and refined in subsequent concept versions.

Unmanned aircraft, uncrewed aircraft, regional air↗
NASA NTRS2023

m:N Working Group Spring Meeting Summary

On May 9th and 11th, 2023, the NASA-led MultiVehicle (m:N) Working Group and its subgroups [small Unmanned Aircraft Systems (sUAS), Large UAS, High Altitude Pseudo Satellite (HAPS), and Urban Air Mobility (UAM)] met in Denver, CO at XPONENTIAL 2023, co-hosted by the Association for Uncrewed Vehicle Systems International (AUVSI) and Messe Düsseldorf North America (MDNA), for an in-person meeting. The subgroups meet multiple times throughout the year, virtually. Twice a year, however, participants from all the subgroups come together to brief each other on progress, challenges, and path forward ideas for incorporating UAS into the airspace. The m:N working group is co-chaired by Jay Shively (Adaptive Aerospace) and Andy Thurling (Thurling Aero Consulting) and is comprised of members from government, industry, and academia in an effort to identify and reduce barriers to m:N operations. This effort also includes identifying requirements, use cases, and metrics to support organizations and groups, including the FAA and RTCA’s SC-228 Detect and Avoid.

multi-vehicle↗
NASA NTRS2022

m:N Working Group

On November 29th and 30th, 2022, the m:N UAS working group and its subgroups [small Unmanned Aircraft Systems (sUAS), Large UAS, High Altitude Platform Systems (HAPS), and Urban Air Mobility (UAM)] met at the NASA Ames Research Center in Mountain View, CA for an in person meeting. The option to dial in remotely and use Conference.IO to engage with questions was offered as well. The subgroups meet multiple times throughout the year, virtually. Twice a year however, participants from all the subgroups come together to brief each other on progress, challenges, and path forward ideas for incorporating UAS into the airspace. The m:N UAS working group is run by Jay Shively (Adaptive Aerospace) and Andy Thurling (Thurling Aero Consulting) and is comprised of members from government, industry, and academia in an effort to identify and reduce barriers to m:N operations. This effort also includes identifying requirements, use cases, and metrics to support organizations and groups including the FAA and RTCA’s SC-228 Detect and Avoid. Each subgroup is run by a government/industry team.

multi-vehicle↗