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.

136 records · Page 8
All sourcesNASA NTRSDOE OSTI
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↗
NASA NTRS2023

m:N Working Group Annual Status Report

This document serves as an annual report of m:N Unmanned Aircraft Systems (UAS) subgroup activities, addressed challenges, and roadmaps for the future. The subgroups consist of small Unmanned Aircraft Systems (sUAS), Large UAS, High Altitude Platform Systems (HAPS), and Urban Air Mobility (UAM). Also included in this report are participant lists for each subgroup (Appendix B) and future roadmap and outreach plans.The subgroups meet in a virtual format multiple times throughout the year. Twice a year, participants from all the subgroups come together as part of the m:N working group to brief each other in person on progress, challenges, and path forward ideas for successful incorporation of UAS into the airspace. Recent m:N in person meetings include: - November 29-30, 2022 at the NASA Ames Research Center in Mountain View, CA - May 9 & 11, 2023 at AUVSI’s Xponential conference in Denver, CO - The next in person working group meeting is planned for November 28-30, 2023 at NASA Langley in Hampton, Virginia 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 Federal Aviation Administration (FAA) and Radio Technical Commission for Aeronautics (RTCA’s) SC-228 Detect and Avoid committee.

multi-vehicle↗
NASA NTRS2024

m:N Working Group Meeting Summary November 2023

From November 28th to 30th, 2023 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 Langley Research Center in Hampton, VA 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 in person to further identify and discuss 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, RTCA, and ASTM. Each subgroup is run by a government/industry team (see below). sUAS Subgroup Garrett Sadler (NASA) Scott Scheff (HF Designworks) Large UAS Subgroup Conrad Rory (NASA) Brandon Suarez (Reliable Robotics) HAPS Subgroup Andy Thurling (Thurling Aero Consulting) Jeff Homola (NASA) UAM Subgroup Mike Politowicz (NASA) Scott Scheff (HF Designworks), member-at-large

m:N operations↗
NASA NTRS2024

m:N Working Group: Meeting Summary March 2024

From March 26th to 28th, 2024 the m:N UAS working group and its subgroups (Evaluation Methodologies, Exceptions/Interventions, and Initial Operating Capability for Airspace Integration) met at SAIC in Washington, D.C. for an in-person meeting. The subgroups meet virtually throughout the year, and twice a year participants from all the subgroups come together to further identify and discuss challenges and paths forward for incorporating UAS into the airspace. The m:N UAS working group is run by Jay Shively (Adaptive Aerospace) and Andy Thurling (DroneUp) and is comprised of members from government, industry, and academia in an effort to identify and reduce barriers to m:N operations. This includes identifying requirements, use cases, metrics, and the development of white papers to support organizations including the FAA, RTCA, and ASTM. A change from last year, the Large UAS and HAPS sub working groups have disbanded while the sUAS working group continues independently, currently working on a white paper titled Personnel Selection, Roles, and Training for sUAS. For 2024 the m:N sub working groups have been refocused to cover evaluation methodologies, interventions/exceptions, and initial operating capability for airspace integration; with the premise that the outcomes from these subgroups will be white papers. These white papers can inform one another to ultimately become a master whitepaper. Each subgroup lead is called out below: Evaluation Methodologies Subgroup Jay Shively, Adaptive Aerospace Interventions/Exceptions Subgroup Andy Thurling, DroneUp (Lead) Initial Operating Capability for Airspace Integration Subgroup Andy Lacher, NASA (Lead)

m:N operations↗
NASA NTRSDate not supplied

Pathfinding for Airspace with Autonomous Vehicles (PAAV) ACAS Xr Terminal Area Simulation Overview

This presentation provides an overview of an upcoming human-in-the-loop simulation planned by the Pathfinding for Airspace with Autonomous Vehicles (PAAV) subproject, as part of the Air Traffic Management eXploration project. The study will investigate Detect and Avoid (DAA) concepts in and around the DAA terminal area (DTA). The DTA has received little investigation in real-time, pilot-in-the-loop simulation. This study proposes to use current remotely piloted aircraft system (RPAS) pilots to investigate the effectiveness of current DTA requirements using the FAA's Airborne Collision Avoidance System X for Rotorcraft (ACAS Xr) as the DAA system under test. The findings of this stufy will be used to inform DTA and ACAS Xr standards development. This presentation will be provided to RTCA Special Committee 228 as an overview and as an opportunity to collect feedback from the larger RPAS/DAA community on the study design and key scenarios and metrics. The presentation provides a brief overview of open areas of research with ACAS Xr, the experimental design, the simulation environment and the simulation schedule.

advanced air mobility↗