Search NASA⌕ Search

SEARCH · Search NASA

Results for “Detect And Avoid”

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 325 records · Page 18

A Cognitive Systems Engineering Approach to Developing HMI Requirements for New Technologies

This document examines the challenges inherent in designing and regulating to support human-automation interaction for new technologies that will deployed into complex systems. A key question for new technologies, is how work will be accomplished by the human and machine agents. This question has traditionally been framed as how functions should be allocated between humans and machines. Such framing misses the coordination and synchronization that is needed for the different human and machine roles in the system to accomplish their goals. Coordination and synchronization demands are driven by the underlying human-automation architecture of the new technology, which are typically not specified explicitly by the designers. The human machine interface (HMI) which is intended to facilitate human-machine interaction and cooperation, however, typically is defined explicitly and therefore serves as a proxy for human-automation cooperation requirements with respect to technical standards for technologies. Unfortunately, mismatches between the HMI and the coordination and synchronization demands of the underlying human-automation architecture, can lead to system breakdowns. A methodology is needed that both designers and regulators can utilize to evaluate the expected performance of a new technology given potential human-automation architectures. Three experiments were conducted to inform the minimum HMI requirements a detect and avoid system for unmanned aircraft systems (UAS). The results of the experiments provided empirical input to specific minimum operational performance standards that UAS manufacturers will have to meet in order to operate UAS in the National Airspace System (NAS). These studies represent a success story for how to objectively and systematically evaluate prototype technologies as part of the process for developing regulatory requirements. They also provide an opportunity to reflect on the lessons learned from a recent research effort in order to improve the methodology for defining technology requirements for regulators in the future. The biggest shortcoming of the presented research program was the absence of the explicit definition, generation and analysis of potential human-automation architectures. Failure to execute this step in the research process resulted in less efficient evaluation of the candidate prototypes technologies in addition to the complete absence of different approaches to human-automation cooperation. For example, all of the prototype technologies that were evaluated in the research program assumed a human-automation architecture that relied on serial processing from the automation to the human. While this type of human-automation architecture is typical across many different technologies and in many different domains, it ignores different architectures where humans and automation work in parallel. Defining potential human-automation architectures a priori also allows regulators to develop scenarios that will stress the performance boundaries of the technology during the evaluation phase. The importance of adding this step of generating and evaluating candidate human-automation architectures prior to formal empirical evaluation is discussed.

human systems integration↗

AIAA Aviation UAS DAA Demonstration-Mini HITL Week 2 Stats

The UAS-NAS Project demo will showcase recent research efforts to ensure the interoperability between proposed UAS detect and avoid (DAA) human machine interface requirements (developed within RTCA SC-228) and existing collision avoidance displays. Attendees will be able to view the current state of the art of the DAA pilot traffic, alerting and guidance displays integrated with Traffic advisory and Collision Avoidance (TCAS) II in the UAS-NAS Project's research UAS ground control station (developed in partnership with the Air Force Research Laboratory). In addition, attendees will have the opportunity to interact with the research UAS ground control station and "fly" encounters, using the DAA and TCAS II displays to avoid simulated aircraft. The display of the advisories will be hosted on a laptop with an external 30" monitor, running the Vigilant Spririt system. DAA advisories will be generated by the JADEM software tool, connected to the system via the LVC Gateway. A repeater of the primary flight display will be shown on a 55" tv/monitor mounted on a stand at the back of the booth to show the pilot interaction to the passersby.

UAS↗

UAS in the NAS Flight Test Series 4 Overview

Flight Test Series 4 (FT4) provides the researchers with an opportunity to expand on the data collected during the first flight tests. Following Flight Test Series 3, additional scripted encounters with different aircraft performance and sensors will be conducted. FT4 is presently planned for Spring of 2016 to ensure collection of data to support the validation of the final RTCA Phase 1 DAA (Detect and Avoid) Minimum Operational Performance Standards (MOPS). There are three research objectives associated with this goal: Evaluate the performance of the DAA system against cooperative and non-cooperative aircraft encounters Evaluate UAS (Unmanned Aircraft Systems) pilot performance in response to DAA maneuver guidance and alerting with live intruder encounters Evaluate TCAS/DAA (Traffic Alert and Collision Avoidance System/Detect and Avoid) interoperability. This flight test series will focus on only the Scripted Encounters configuration, supporting the collection of data to validate the interoperability of DAA and collision avoidance algorithms.

flight test↗

DAIDALUS Observations From UAS Integration in the NAS Project Flight Test 4

In order to validate the Unmanned Aerial System (UAS) Detect-and-Avoid (DAA) solution proposed by standards body RTCA Inc., the National Aeronautics and Space Administration (NASA) UAS Integration in the NAS project, alongside industry members General Atomics and Honeywell, conducted the fourth flight test in a series at Armstrong Flight Research Center in Edwards, California. Flight Test 4 (FT4) investigated problems of interoperability with the TCAS collision avoidance system with a DAA system as well as problems associated with sensor uncertainty. A series of scripted flight encounters between the NASA Ikhana UAS and various "intruder" aircraft were flown while alerting and guidance from the DAA algorithm were recorded to investigate the timeliness of the alerts and correctness of the guidance triggered by the DAA system. The results found that alerts were triggered in a timely manner in most instances. Cases where the alerting and guidance was incorrect were investigated further.

Vincent, Michael J.↗

Moon Age and Regolith Explorer (MARE) Mission Design and Performance

On December 11, 1972, Apollo 17 marked the last controlled U.S. lunar landing and was followed by an absence of methodical in-situ investigation of the lunar surface. The Moon Age and Regolith Explorer (MARE) proposal provides scientific measurement of the age and composition of a relatively young portion of the lunar surface near Aristarchus Plateau and the first post-Apollo U.S. soft lunar landing. It includes the first demonstration of a crew survivability-enhancing autonomous hazard detection and avoidance system. This report focuses on the mission design and performance associated with the MARE robotic lunar landing subject to mission and trajectory constraints.

Condon, Gerald L.↗

ICAROUS: Integrated Configurable Architecture for Unmanned Systems

NASA's Unmanned Aerial System (UAS) Traffic Management (UTM) project aims at enabling near-term, safe operations of small UAS vehicles in uncontrolled airspace, i.e., Class G airspace. A far-term goal of UTM research and development is to accommodate the expected rise in small UAS traffic density throughout the National Airspace System (NAS) at low altitudes for beyond visual line-of-sight operations. This video describes a new capability referred to as ICAROUS (Integrated Configurable Algorithms for Reliable Operations of Unmanned Systems), which is being developed under the auspices of the UTM project. ICAROUS is a software architecture comprised of highly assured algorithms for building safety-centric, autonomous, unmanned aircraft applications. Central to the development of the ICAROUS algorithms is the use of well-established formal methods to guarantee higher levels of safety assurance by monitoring and bounding the behavior of autonomous systems. The core autonomy-enabling capabilities in ICAROUS include constraint conformance monitoring and autonomous detect and avoid functions. ICAROUS also provides a highly configurable user interface that enables the modular integration of mission-specific software components.

Consiglio, Maria C.↗

Unmanned Aircraft Systems Minimum Operations Performance Standards End-to-End Verification and Validation (E2-V2) Simulation

As Unmanned Aircraft Systems (UAS) make their way to mainstream aviation operations within the National Airspace System (NAS), research efforts are underway to develop a safe and effective environment for their integration into the NAS. Detect and Avoid (DAA) systems are required to account for the lack of "eyes in the sky" due to having no human on-board the aircraft. The current NAS relies on pilot's vigilance and judgement to remain Well Clear (CFR 14 91.113) of other aircraft. RTCA SC-228 has defined DAA Well Clear (DAAWC) to provide a quantified Well Clear volume to allow systems to be designed and measured against. Extended research efforts have been conducted to understand and quantify system requirements needed to support a UAS pilot's ability to remain well clear of other aircraft. The efforts have included developing and testing sensor, algorithm, alerting, and display requirements. More recently, sensor uncertainty and uncertainty mitigation strategies have been evaluated. This paper discusses results and lessons learned from an End-to-End Verification and Validation (E2-V2) simulation study of a DAA system representative of RTCA SC-228's proposed Phase I DAA Minimum Operational Performance Standards (MOPS). NASA Langley Research Center (LaRC) was called upon to develop a system that evaluates a specific set of encounters, in a variety of geometries, with end-to-end DAA functionality including the use of sensor and tracker models, a sensor uncertainty mitigation model, DAA algorithmic guidance in both vertical and horizontal maneuvering, and a pilot model which maneuvers the ownship aircraft to remain well clear from intruder aircraft, having received collective input from the previous modules of the system. LaRC developed a functioning batch simulation and added a sensor/tracker model from the Federal Aviation Administration (FAA) William J. Hughes Technical Center, an in-house developed sensor uncertainty mitigation strategy, and implemented a pilot model similar to one from the Massachusetts Institute of Technology's Lincoln Laboratory (MIT/LL). The resulting simulation provides the following key parameters, among others, to evaluate the effectiveness of the MOPS DAA system: severity of loss of well clear (SLoWC), alert scoring, and number of increasing alerts (alert jitter). The technique, results, and lessons learned from a detailed examination of DAA system performance over specific test vectors and encounter cases during the simulation experiment will be presented in this paper.

Ghatas, Rania W.↗

Mitigating the Impact of Sensor Uncertainty on Unmanned Aircraft Operations

Without a pilot onboard an aircraft, a Detect-and-Avoid (DAA) system, in conjunction with surveillance sensors, must be used to provide the remotely-located Pilot-in-Command sufficient situational awareness in order to keep the Unmanned Aircraft (UA) safely separated from other aircraft. To facilitate safe operations of UA within the U.S.' National Airspace System, the uncertainty associated with surveillance sensors must be accounted for. An approach to mitigating the impact of sensor uncertainty on achievable separation has been developed to support technical requirements for DAA systems.

Jack, Devin P.↗

Considerations for RTCA Phase 2 Low Size, Weight, and Power (SWAP) Surveillance Requirements

RTCA (Radio Technical Commission for Aeronautics) Special Committee 228 has initiated a second phase for the development of minimum operational performance standards (MOPS) for UAS (Unmanned Aircraft Systems) detect and avoid (DAA) systems. Technologies to enable UAS with less available Size, Weight, and Power (SWaP) will be considered. A white paper is in development for what topics and issues need to be addressed to develop DAA requirements for low SWAP surveillance systems. This briefing will document the issues to be investigated in SC-228. It will also serve as a review with the committee to get feedback so the white paper can be written and finalized. These topics and issues are not necessarily all the things that NASA will contribute to SC-228 during Phase 2, but what the overall committee needs to accomplish. A portion of the work will be in NASA's UAS in the NAS (National Airspace System) project plan.

Santiago, Confesor↗

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project

Over the past 5 years, the UAS integration into the NAS project has worked to reduce technical barriers to integration. A major focus of this work has been in support of RTCA SC-228. This committee has recently published the first UAS integration minimum performance standards (MOPS). This work has spanned detect and avoid (DAA) as well as command and control comm datalinks. I will discuss DAA efforts with focus on the human systems work. I will discuss how automation was discussed and addressed within this context. ICAO stood up a remotely piloted aircraft systems (RPAS) panel in 2014. They have developed an RPAS manual and are now working to revise existing annexes and standards and recommended practices. The Human In The System (HITS) has worked to infuse human factors guidelines into those documents. I will discuss that effort as well as how ICAO has defined and address autonomy. There is a great deal of interest in the control of multiple vehicles by a single operator. The UAS EXCOM Science and Research Panel (SARP) is holding a workshop on this topic in late June. I will discuss research performed on this topic when I worked for the Army and on-going work within the division and a NATO working group on Human-Autonomy Teaming.

Unmanned Aircraft Systems (UAS)↗

Evolution of A Distributed Live, Virtual, Constructive Environment for Human in the Loop Unmanned Aircraft Testing

NASA's Unmanned Aircraft Systems Integration in the National Airspace System Project is conducting human in the loop simulations and flight testing intended to reduce barriers associated with enabling routine airspace access for unmanned aircraft. The primary focus of these tests is interaction of the unmanned aircraft pilot with the display of detect and avoid alerting and guidance information. The projects integrated test and evaluation team was charged with developing the test infrastructure. As with any development effort, compromises in the underlying system architecture and design were made to allow for the rapid prototyping and open-ended nature of the research. In order to accommodate these design choices, a distributed test environment was developed incorporating Live, Virtual, Constructive, (LVC) concepts. The LVC components form the core infrastructure support simulation of UAS operations by integrating live and virtual aircraft in a realistic air traffic environment. This LVC infrastructure enables efficient testing by leveraging the use of existing assets distributed across multiple NASA Centers. Using standard LVC concepts enable future integration with existing simulation infrastructure.

UAS in the NA↗

Evolution of A Distributed Live, Virtual, Constructive Environment for Human in the Loop Unmanned Aircraft Testing

NASA's Unmanned Aircraft Systems Integration in the National Airspace System Project is conducting human in the loop simulations and flight testing intended to reduce barriers associated with enabling routine airspace access for unmanned aircraft. The primary focus of these tests is interaction of the unmanned aircraft pilot with the display of detect and avoid alerting and guidance information. The project's integrated test and evaluation team was charged with developing the test infrastructure. As with any development effort, compromises in the underlying system architecture and design were made to allow for the rapid prototyping and open-ended nature of the research. In order to accommodate these design choices, a distributed test environment was developed incorporating Live, Virtual, Constructive, (LVC) concepts. The LVC components form the core infrastructure support simulation of UAS operations by integrating live and virtual aircraft in a realistic air traffic environment. This LVC infrastructure enables efficient testing by leveraging the use of existing assets distributed across multiple NASA Centers. Using standard LVC concepts enable future integration with existing simulation infrastructure.

LVC↗

Operational Overview for UAS Integration in the NAS Project Flight Test Series 3

The National Aeronautics and Space Administration Unmanned Aircraft Systems Integration in the National Airspace System Project has conducted a series of flight tests intended to support the reduction of barriers that prevent unmanned aircraft from flying without the required waivers from the Federal Aviation Administration. The 2015 Flight Test Series 3, supported two separate test configurations. The first configuration investigated the timing of Detect and Avoid alerting thresholds using a radar equipped unmanned vehicle and multiple live intruders flown at varying encounter geometries.

UAS in the NAS↗

ADS-B Mixed sUAS and NAS System Capacity Analysis and DAA Performance

Automatic Dependent Surveillance-Broadcast (ADS-B) technology was introduced more than twenty years ago to improve surveillance within the US National Airspace Space (NAS) as well as in many other countries. Via the NextGen initiative, implementation of ADS-B technology across the US is planned in stages between 2012 and 2025. ADS-B's automatic one second epoch packet transmission exploits on-board GPS-derived navigational information to provide position information, as well as other information including vehicle identification, ground speed, vertical rate and track angle. The purpose of this technology is to improve surveillance data accuracy and provide access to better situational awareness to enable operational benefits such as shorter routes, reduced flight time and fuel burn, and reduced traffic delays, and to allow air traffic controllers to manage aircraft with greater safety margins. Other than the limited amount of information bits per packet that can be sent, ADS-B's other hard-limit limitation is capacity. Small unmanned aircraft systems (sUAS) can utilize limited ADS-B transmission power, in general, thus allowing this technology to be considered for use within a combined NAS and sUAS environment, but the potential number and density of sUAS predicted for future deployment calls into question the ability of ADS-B systems to meet the resulting capacity requirement. Hence, studies to understand potential limitations of ADS-B to fulfill capacity requirements in various sUAS scenarios are of great interest. In this paper we, validate/improve on, previous work performed by the MITRE Corporation concerning sUAS power and capacity in a sUAS and General Aviation (GA) mixed environment. In addition, we implement its inherent media access control layer capacity limitations which was not shown in the MITRE paper. Finally, a simple detect and avoid (DAA) algorithm is implemented to display that ADS-B technology is a viable technology for a mixed NAS/sUAS environment even in proposed larger mixed density environments.

Matheou, Konstantin J.↗

ADS-B Mixed sUAS and NAS System Capacity Analysis and DAA Performance

Automatic Dependent Surveillance-Broadcast (ADS-B) technology was introduced more than twenty years ago to improve surveillance within the US National Airspace Space (NAS) as well as in many other countries. Via the NextGen initiative, implementation of ADS-B technology across the US is planned in stages between 2012 and 2025. ADS-B's automatic one second epoch packet transmission exploits on-board GPS-derived navigational information to provide position information, as well as other information including vehicle identification, ground speed, vertical rate and track angle. The purpose of this technology is to improve surveillance data accuracy and provide access to better situational awareness to enable operational benefits such as shorter routes, reduced flight time and fuel burn, and reduced traffic delays, and to allow air traffic controllers to manage aircraft with greater safety margins. Other than the limited amount of information bits per packet that can be sent, ADS-B's other hard-limit limitation is capacity. Small unmanned aircraft systems (sUAS) can utilize limited ADS-B transmission power, in general, thus allowing this technology to be considered for use within a combined NAS and sUAS environment, but the potential number and density of sUAS predicted for future deployment calls into question the ability of ADS-B systems to meet the resulting capacity requirement. Hence, studies to understand potential limitations of ADS-B to fulfill capacity requirements in various sUAS scenarios are of great interest. In this paper we, validate/improve on, previous work performed by the MITRE Corporation concerning sUAS power and capacity in a sUAS and General Aviation (GA) mixed environment. In addition, we implement its inherent media access control layer capacity limitations which was not shown in the MITRE paper. Finally, a simple detect and avoid (DAA) algorithm is implemented to display that ADS-B technology is a viable technology for a mixed NAS/sUAS environment even in proposed larger mixed density environments.

Matheou, Konstantin↗

UTM UAS Serivce Supplier Development: Sprint 1 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid.

UAS service supplier↗

UTM UAS Service Supplier Development: Sprint 2 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability.

software engineering↗

Unmitigated ACES Simulation Supporting Draft DAA MOPS Alerting

Realization of the expected proliferation of Unmanned Aircraft System (UAS) operations in the National Airspace System (NAS) depends on the development and validation of performance standards for UAS Detect and Avoid (DAA) Systems. The RTCA Special Committee 228 is charged with leading the development of draft Minimum Operational Performance Standards (MOPS) for UAS DAA Systems. NASA, as a participating member of RTCA SC-228 is committed to supporting the development and validation of draft requirements for DAA alerting system performance. A recent study conducted using NASA's ACES (Airspace Concept Evaluation System) simulation capability begins to address questions surrounding the development of draft MOPS for DAA alerting systems. ACES simulations were conducted to study the performance of an alerting scheme proposed by the SC-228 DAA Alerting sub-group. Analysis included but was not limited to: 1) correct alert (and their timeliness), 2) false alert (and their severity and duration), 3) missed alert, and 4) probability of an alert type at the time of loss of well clear. The results will be used by SC-228 to inform decisions about the alerting aspect of UAS DAA systems and future requirements development and validation efforts.

alerting↗