SEARCH · Search NASA
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.
This presentation is an overview of the UAS-NAS Project and how flight testing is used to collect data to provide inputs in validating the RTCA MOPS.
Mid-air collision risk continues to be a concern for manned aircraft operations, especially near busy non-towered airports. The use of Detect and Avoid (DAA) technologies and draft standards developed for unmanned aircraft systems (UAS), either alone or in combination with other collision avoidance technologies, may be useful in mitigating this collision risk for manned aircraft. This paper describes a NASA research effort known as DANTi (DAA iN The Cockpit), including the initial development of the concept of use, a software prototype, and results from initial flight tests conducted with this prototype. The prototype used a single Automatic Dependent Surveillance - Broadcast (ADS-B) traffic sensor and the own aircraft's position, track, heading and air data information, along with NASA-developed DAA software to display traffic alerts and maneuver guidance to manned aircraft pilots on a portable tablet device. Initial flight tests with the prototype showed a successful DANTi proof-of-concept, but also demonstrated that the traffic separation parameter set specified in the RTCA SC-228 Phase I DAA MOPS may generate excessive false alerts during traffic pattern operations. Several parameter sets with smaller separation values were also tested in flight, one of which yielded more timely alerts for the maneuvers tested. Results from this study may further inform future DANTi efforts as well as Phase II DAA MOPS development.
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 technique, results, and lessons learned from a detailed 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), based on specific test vectors and encounter cases, will be presented in this paper.
The topics discussed are the UAS-NAS project life-cycle and ARMD thrust flow down, as well as the UAS environments and how we operate in those environments. NASA's Armstrong Flight Research Center at Edwards, CA, is leading a project designed to help integrate unmanned air vehicles into the world around us. The Unmanned Aircraft Systems Integration in the National Airspace System project, or UAS in the NAS, will contribute capabilities designed to reduce technical barriers related to safety and operational challenges associated with enabling routine UAS access to the NAS. The project falls under the Integrated Systems Research Program office managed at NASA Headquarters by the agency's Aeronautics Research Mission Directorate. NASA's four aeronautics research centers - Armstrong, Ames Research Center, Langley Research Center, and Glenn Research Center - are part of the technology development project. With the use and diversity of unmanned aircraft growing rapidly, new uses for these vehicles are constantly being considered. Unmanned aircraft promise new ways of increasing efficiency, reducing costs, enhancing safety and saving lives 460265main_ED10-0132-16_full.jpg Unmanned aircraft systems such as NASA's Global Hawks (above) and Predator B named Ikhana (below), along with numerous other unmanned aircraft systems large and small, are the prime focus of the UAS in the NAS effort to integrate them into the national airspace. Credits: NASA Photos 710580main_ED07-0243-37_full.jpg The UAS in the NAS project envisions performance-based routine access to all segments of the national airspace for all unmanned aircraft system classes, once all safety-related and technical barriers are overcome. The project will provide critical data to such key stakeholders and customers as the Federal Aviation Administration and RTCA Special Committee 203 (formerly the Radio Technical Commission for Aeronautics) by conducting integrated, relevant system-level tests to adequately address safety and operational challenges of national airspace access by unmanned aircraft systems, or UAS. In the process, the project will work with other key stakeholders to define necessary deliverables and products to help enable such access. Within the project, NASA is focusing on five sub-projects. These five focus areas include assurance of safe separation of unmanned aircraft from manned aircraft when flying in the national airspace; safety-critical command and control systems and radio frequencies to enable safe operation of UAS; human factors issues for ground control stations; airworthiness certification standards for UAS avionics and integrated tests and evaluation designed to determine the viability of emerging UAS technology. Five Focus Areas of the UAS Integration in the NAS Project Separation Assurance Provide an assessment of how planned Next Generation Air Transportation System (NextGen) separation assurance systems, with different functional allocations, perform for UAS in mixed operations with manned aircraft Assess the applicability to UAS and the performance of NASA NextGen separation assurance systems in flight tests with realistic latencies and uncertain trajectories Assess functional allocations ranging from today's ground-based, controller-provided aircraft separation to fully autonomous airborne self-separation Communications Develop data and rationale to obtain appropriate frequency spectrum allocations to enable safe and efficient operation of UAS in the NAS Develop and validate candidate secure safety-critical command and control system/subsystem test equipment for UAS that complies with UAS international/national frequency regulations, standards and recommended practices and minimum operational and aviation system performance standards for UAS Perform analysis to support recommendations for integration of safety-critical command and control systems and air traffic control communications to ensure safe and efficient operation of UAS in the NAS Human Systems Integration Develop a research test bed and database to provide data and proof of concept for GCS - ground control station - operations in the NAS Coordinate with standards organizations to develop human-factors guidelines for GCS operation in the NAS Certification Define a UAS classification scheme and approach to determining Federal Aviation Regulation airworthiness requirements applicable to all UAS digital avionics Provide hazard and risk-related data to support development of type design criteria and best development practices Integrated Tests and Evaluation Integrate and test mature concepts from technical elements to demonstrate and test viability Evaluate the performance of technology development in a relevant environment (full-mission, human-in-the-loop simulations and flight tests)
This presentation contains the analysis results of NAS-wide fast-time simulations with UAS and VFR traffic for a single day for evaluating the performance of Detect-and-Avoid (DAA) alerting and guidance systems. This purpose of this study was to help refine and validate MOPS alerting and guidance requirements. In this study, we generated plots of all performance metrics that are specified by RTCA SC-228 Minimum Operational Performance Standards (MOPS): 1) to evaluate the sensitivity of alerting parameters on the performance metrics of each DAA alert type: Preventive, Corrective, and Warning alerts and 2) to evaluate the effect of sensor uncertainty on DAA alerting and guidance performance.
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.
This presentation covers the primary results of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project Terminal Operations Foundational Human-in-the-Loop (HITL) simulation. The study tasked 16 pilots (half with manned piloting experience, and the other half with unmanned piloting experience) with maintaining "well clear" from other traffic while performing three different types of approaches into the Santa Rosa airport. A detect and avoid (DAA) system was provided to pilots to assist their ability to manage separation. The DAA system used in this test conformed to the criteria defined by RTCA Special Committee 228 (SC-228) in their Phase 1 Minimum Operational Performance Standards (MOPS) for UAS intending to operate in the NAS. The Phase 1 system was not designed to account for terminal operations, focusing instead on en route operations. To account for this, three different alerting and guidance configurations were presently tested in order to determine their effect on pilots operating the system in the terminal area. Results indicated that pilots with the alerting and guidance condition that provided the least amount of assistance (fewer alert levels and guidance types) experienced slightly increased pilot response times and rates of losses of separation. Additional data is presented on the effects of approach type and descriptive data on pilot maneuver preferences and ATC interoperability.
This presentation summarizes the simulation work conducted by the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. It focuses on the contribution of that research to the development of RTCA Special Committee 228's (SC-228) Minimum Operational Performance Standards (MOPS) for UAS. The research objectives and primary findings from four different human-in-the-loop simulations are discussed, along with the specific requirements these studies led to in the final MOPS document.
NASA's Unmanned Aerial Systems (UAS) integration into the National Air Space (NAS) project has been working closely with the FAA and RTCA Special Committee 228 to identify and break down barriers to UAS integration. A focus of this work is on detect and avoid (DAA) technologies. A pilot has responsibility to see and avoid other aircraft and to remain "well clear," using their best judgment (Federal Aviation Regulations (FAR) Sec. 91.113). For UAS to perform this function, the see function is replaced by sensors to detect the other aircraft. Secondly, the pilot judgment of well clear has to be replaced by a mathematical expression. For Phase 1 of this effort, a well clear violation was defined if all three of these conditions are true: a) the horizontal clearance is less than 4000 ft., and b) the vertical clearance is less than 450 ft., and c) the time to loss of well clear is less than 35 seconds. This definition was developed with a great deal of community input and testing to ensure interoperability with Air Traffic Control (ATC) and pilots of manned aircraft. Appropriate guidance, alerting and displays were developed to allow UAS, with the appropriate sensors, to effectively maintain well clear. This work contributed to FAA Technical Standard Orders: TSO-C211, Detect and Avoid and TSO-C212, ATAR for Traffic Surveillance. Phase 2 of this work extends the operational environment to include the terminal area and lesser capable aircraft that might not have the payload capability to carry the RADAR defined in Phase 1. This session reports on work from Phase 1 and initial work in Phase 2.
NASA's Unmanned Aerial Systems (UAS) integration into the National Air Space (NAS) project has been working closely with the FAA and RTCA Special Committee 228 to identify and break down barriers to UAS integration. A focus of this work is on detect and avoid (DAA) technologies. A pilot has responsibility to see and avoid other aircraft and to remain "well clear," using their best judgment (Federal Aviation Regulations (FAR) Sec. 91.113). For UAS to perform this function, the see function is replaced by sensors to detect the other aircraft. Secondly, the pilot judgment of well clear has to be replaced by a mathematical expression. For Phase 1 of this effort, a well clear violation was defined if all three of these conditions are true: a) the horizontal clearance is less than 4000 ft., and b) the vertical clearance is less than 450 ft., and c) the time to loss of well clear is less than 35 seconds. This definition was developed with a great deal of community input and testing to ensure interoperability with Air Traffic Control (ATC) and pilots of manned aircraft. Appropriate guidance, alerting and displays were developed to allow UAS, with the appropriate sensors, to effectively maintain well clear. This work contributed to FAA Technical Standard Orders: TSO-C211, Detect and Avoid and TSO-C212, ATAR for Traffic Surveillance. Phase 2 of this work extends the operational environment to include the terminal area and lesser capable aircraft that might not have the payload capability to carry the RADAR defined in Phase 1. This session reports on work from Phase 1 and initial work in Phase 2.
This presentation covers the results of a human-in-the-loop simulation that examined the effect of caution versus warning-level alerting in the context of Unmanned Aircraft System (UAS) operations in civil airspace. Minimum Operational Performance Standards (MOPS) are currently being developed by RTCA Special Committee 228 for UAS Detect-and-Avoid (DAA) systems. Input from subject matter experts and multiple research studies have informed display requirements for DAA systems aimed at supporting timely and appropriate pilot responses to collision hazards. DAA alerting is designed to inform pilots of potential threats to DAA "well clear"; the two highest alert levels - caution and warning - indicate how soon pilot action is required and whether there is adequate time to coordinate with the air traffic controller (ATC). Additional empirical support is needed to clarify the extent to which warning-level alerting impacts DAA task performance. The present study explores the differential effects of the auditory and visual cues provided by the DAA Warning alert, and performance implications compared to caution-only alerting are discussed.
This document contains a list of human factors guidelines for remote pilot stations (RPS) arranged within an organizing structure. The guidelines are intended for the remote pilot stations (RPSs) of remotely piloted aircraft (RPA) that are capable of operating beyond visual line-of-sight in all airspace classes of the United States National Airspace System (NAS). Numerous human factors guidelines and standards for technological systems have been published by standards agencies and regulatory authorities. In compiling this document, the intent was not to reproduce or re-state existing human factors material. Instead, this document focuses on the unique issues of civilian RPAS, and contains guidelines specific to this sector. As a result, it should be seen as a supplement to existing aviation human factors standards and guidance material. Two constraints were used to focus the scope of this document. First, the assumptions contained in the FAA (2013a) UAS roadmap were used to define the responsibilities that will be assigned to the pilot of a RPAS operating beyond visual line-of-sight in the NAS. This in turn, helped to define the tasks that the remote pilot must perform via the RPS, and thereby the required features and characteristics of the RPS. Second, the points of difference between RPAS and conventional aviation were used to further focus the guidelines on the considerations that make piloting a RPA significantly different to piloting a conventional aircraft. Five broad categories of guidelines are identified. These are (1) performance-based descriptions of pilot tasks that must be accomplished via the RPS, (2) information content of displays, (3) descriptions of control inputs, (4) properties of the interface, and (5) high-level design considerations. Some of the guidelines in this document have been adapted from existing RPAS human factors material from several sources, including RTCA publications and Standardization Agreements (STANAGs) published by the North Atlantic Treaty Organization (NATO).
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 technique, results, and lessons learned from a detailed End-to-End Verification and Validation (E2-V2) simulation study of a DAA system representative of RTCA Special Committee(SC)-228’s proposed Phase I DAA Minimum Operational Performance Standards (MOPS), based on specific test vectors and encounter cases, will be presented in this paper.
In support of NASA’s Unmanned Aircraft Systems Integration in the National Airspace System project and RTCA Special Committee 228, an analysis has been performed to provide insight in to the trade space between unmanned aircraft speed and turn capability and detect and avoid sensor range requirements. The work was done as an initial part of the effort to understand low size, weight, and power sensor requirements for aircraft that have a limited speed envelope or can limit the envelope for portions of their mission and may be able to turn at higher than “standard rate.” Range and timeline reductions coming from limiting speed range and from increasing available turn rate in some speed ranges are shown.
In support of NASA’s Unmanned Aircraft Systems Integration in the National Airspace System project and RTCA Special Committee 228, an analysis has been performed to provide insight in to the trade space between detect and avoid (DAA) Well Clear definition threshold variations, which could affect DAA sensor range and alerting requirements.
This is a HSI (Horizontal Situation Indicator) display evaluation overview presented to the RTCA (Radio Technical Commission for Aeronautics) SC-228 Detect and Avoid Working group. The goal of the presentation is to provide data on the effect of various Detect and Avoid (DAA) display and guidance features with respect to pilot performance of the self-separation function in order to determine the minimum information requirements for DAA displays.
New technical standards for Unmanned Aircraft Systems (UAS) detect and avoid (DAA) systems mark recent progress toward realizing the goal of full integration of UAS into the National Airspace System (NAS). The DAA system is intended to provide a means of compliance with operating regulations that required pilots on board manned aircraft to remain "well clear" of other aircraft which is accomplished through out-the-window visual acquisition of other aircraft and application of a subjective judgment of safe separation. The requirements for the DAA system, including the specification of a DAA well clear threshold as well as functional requirements for detecting, tracking, alerting and guidance processing, and displays, are specified in DO-365, Minimum Operational Performance Standards (MOPS) for DAA Systems developed within RTCA (Radio Technical Commission for Aeronautics) Special Committee 228 (SC-228). Intended as the first in a series of phased versions, these requirements are frequently referred to as the "Phase 1" DAA system. The Phase 1 DAA system is limited for use by aircraft transitioning to and from Class A or special use airspace, through Class D, E, and G airspace. In particular, the Phase 1 DAA MOPS are not intended for terminal airspace operations, a critical gap for enabling a full range of UAS operations. The application of the Phase 1 DAA system and DAA well clear threshold within the terminal area is predicted to result in a high number of unnecessary alerts when the UAS is safely separated from other traffic. The goal of the present study was to examine pilot performance and operational issues related to the operation of the Phase 1 DAA system in a terminal area. This experiment was intended as an exploratory study that would be used to inform the development of a new terminal area-specific DAA well clear definition, and associated alerting and guidance requirements. The two main objectives of this study were to: 1) characterize pilot behavior in the terminal environment with the Phase 1 DAA system, and 2) investigate the effect of modifications to the Phase 1 DAA alerting and guidance structure. In particular, the authors were interested in determining whether the removal of specific alerting and guidance levels, without changing the DAA well clear definition or alerting thresholds, would impact pilot performance while conducting terminal operations. The results indicate that the Phase 1 well clear definition and alerting and guidance resulted in frequent alerting that degraded pilots' ability to discriminate between encounters where another aircraft was safely separated versus when a maneuver was necessary. The resulting impact on pilot performance was slower response times and higher frequency and severity of losses of DAA well clear compared to those observed for experiments examining pilot performance in the en route environment. There was no significant effect of alerting and guidance display configuration on pilot performance.
New technical standards for Unmanned Aircraft Systems (UAS) detect and avoid (DAA) systems mark recent progress toward realizing the goal of full integration of UAS into the National Airspace System (NAS). The DAA system is intended to provide a means of compliance with operating regulations that required pilots on board manned aircraft to remain "well clear" of other aircraft which is accomplished through out-the-window visual acquisition of other aircraft and application of a subjective judgment of safe separation. The requirements for the DAA system, including the specification of a DAA well clear threshold as well as functional requirements for detecting, tracking, alerting and guidance processing, and displays, are specified in DO-365, Minimum Operational Performance Standards (MOPS) for DAA Systems developed within RTCA Special Committee 228 (SC-228). Intended as the first in a series of phased versions, these requirements are frequently referred to as the "Phase 1" DAA system. The Phase 1 DAA system is limited for use by aircraft transitioning to and from Class A or special use airspace, through Class D, E, and G airspace. In particular, the Phase 1 DAA MOPS are not intended for terminal airspace operations, a critical gap for enabling a full range of UAS operations. The application of the Phase 1 DAA system and DAA well clear threshold within the terminal area is predicted to result in a high number of unnecessary alerts when the UAS is safely separated from other traffic. The goal of the present study was to examine pilot performance and operational issues related to the operation of the Phase 1 DAA system in a terminal area. This experiment was intended as an exploratory study that would be used to inform the development of a new terminal area-specific DAA well clear definition, and associated alerting and guidance requirements. The two main objectives of this study were to: 1) characterize pilot behavior in the terminal environment with the Phase 1 DAA system, and 2) investigate the effect of modifications to the Phase 1 DAA alerting and guidance structure. In particular, the authors were interested in determining whether the removal of specific alerting and guidance levels, without changing the DAA well clear definition or alerting thresholds, would impact pilot performance while conducting terminal operations. The results indicate that the Phase 1 well clear definition and alerting and guidance resulted in frequent alerting that degraded pilots' ability to discriminate between encounters where another aircraft was safely separated versus when a maneuver was necessary. The resulting impact on pilot performance was slower response times and higher frequency and severity of losses of DAA well clear compared to those observed for experiments examining pilot performance in the en route environment. There was no significant effect of alerting and guidance display configuration on pilot performance.