Unmanned Aircraft Systems (UAS) Integration in the National Airspace (NAS) Project Briefing
This presentation is a high level overview for the UAS community of current operations.
SEARCH · Engineering Papers
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 a high level overview for the UAS community of current operations.
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 provides an overview of the primary results from the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project's second Terminal Operations human-in-the-loop simulation. This talk covers the background of this follow-on experiment, which includes an overview of the first Terminal Operations HITL performed by the project. The primary results include a look at the number and durations of detect and avoid (DAA) alerts issued by the two DAA systems under test. It also includes response time metrics and metrics on the ability of the pilot-in-command (PIC) to maintain sufficient separation. Additional interoperability metrics are included to illustrate how pilots interact with the tower controller. Implications and conclusions are covered at the end.
Phase 1 of the UAS-NAS (Unmanned Aircraft Systems-National Airspace System) project focused on MOPS (Minimum Operational Performance Standards) development for large UAS transitioning through Class D, E, and G airspace. Phase 2 activities are currently focused on extended UAS operations in Class D, E, and G airspace, as well as sensors and architectures that will enable DAA (Detect and Avoid) equipment to be installed on a wider range of UAS. Encounters with non-cooperative intruders in low altitude airspace under 10,000 feet will be explored for UAS with a low Size, Weight, and Power (SWaP) radar. New sensors for detecting non-cooperative intruder aircraft will have a more limited detection range and field of regard; therefore, the analysis of non-cooperative encounter geometries may help in developing the requirements for an onboard low SWaP radar (and electro-optical sensor). The current simulation, led by HSI (Human Systems Integration Division at NASA Ames Research Center) as part of the DAA subproject, will support efforts toward developing a modified DAA Well Clear (DWC) definition that would be more appropriate for UAS equipped with limited surveillance and aircraft performance capabilities compared to the Phase 1 DAA system. The findings will inform Phase 2 display requirements for alternative surveillance use cases.
This presentation is a high level overview of the flight testing that took place in 2015 for the UAS-NAS project. All topics in the presentation discussed at a high level and no technical details are provided.
This presentation was presented to the Integrated Aviation Systems Program at the FY17 Annual Review of the UAS-NAS project. The presentation captures the overview of the work completed by the UAS-NAS project and its subprojects.
This report addresses a deliverable to the UAS-in-the-NAS project for recommendations for integration of CNPC and ATC communications based on analysis results from modeled radio system and NAS-wide UA communication architecture simulations. For each recommendation, a brief explanation of the rationale for its consideration is provided with any supporting results obtained or observed in our simulation activity.
This presentation provides an overview of a recently completed human-in-the-loop simulation, conducted as part of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. This study examined how to present resolution advisories (RAs) issued by Airborne Collision Avoidance System (ACAS) Xu, which can be in the vertical dimension, the horizontal dimension, or both (i.e., "blended"). The study varied the location of the ACAS Xu traffic information - it was either presented within an 'integrated' display or a 'standalone' display, where the traffic information was separated from the vehicle control interfaces and navigational information. The presentation covers the test set-up, scenario design, and facilities utilized in this experiment. The primary dependent variables are listed, but no detailed results are included in this outbrief since data analysis is still underway. Goal: assess ACAS Xu Run 5 in a HITL setting to measure pilot & system performance – RWC alerting and guidance – RA alerting and guidance • Horizontal-only, vertical-only, and blended RAs • Strengthening RAs, reversals and added/removed RAs during blended maneuvers – Incorporate realistic sensor noise into the simulation environment – Compare pilot and DAA system performance back to NASA’s Phase 1 DAA MOPS V&V HITL • We leveraged the findings of an engineering analysis conducted in March to help inform how to implement the Xu logic – Part 1 focused on how to display horizontal-only, vertical-only and blended RAs – Part 2 focused on how to display automated RA responses Xu Engineering Analysis Results Part 1 objectives: – Characterize pilot responses to (canned) ACAS Xu RAs in a variety of display configurations • With vs. Without text accompaniment • Simple vs. ‘Advanced’ aural alerting • Results – Pilots struggled to meet 5 seconds initial response requirement • Particularly against horizontal and blended RAs – Pilots failed to respond more quickly to secondary RAs • Expected response time to subsequent RAs = 2.5 seconds No clear effect of the different alerting conditions on response times – Response times primarily driven by RA type • Pilots demonstrated high level of compliance with RAs and self-reported Xu alerting and guidance as being acceptable – 1/5 reported text as being necessary – 4/5 wanted the aural alert to retain the original RA sequence (i.e., issue a follow-on RA second rather than first) – 4/5 wanted to retain the “Maintain Heading/Vertical Speed” aural alert in the event that the pilot reached their target response at the time of secondary RA Based on these results, we decided on the following for the HITL experimental design: – Incorporated an ‘auto-fill’ feature in Vigilant Spirit that removes the need for pilots to manually enter a heading or altitude for RAs • Pilots only have to click ‘Send’ to upload the RA target heading/altitude – Did not include an RA ‘text box’ • The auto-fill feature largely replaces the purpose of the text box – Using a combination of the ‘Basic’ and ‘Advanced’ aural alerting • In case of blended maneuvers will issue “Maintain Heading/Vertical Rate” if pilot has reached 1st RA target at the time the 2nd RA is issued • Integration and testing with Xu Run 5 also resulted in us adding display logic to modify how horizontal RAs are presented – Target heading was shown to update at approx. 1 Hz making it difficult for pilots to implement – Display logic limited horizontal RA strengthening to once every 5 seconds • Did not impact timing of reversals, new RAs (i.e., blended), or CoC Engineering Analysis Results
This presentation provides an overview of the results from a two-part engineering analysis conducted as part of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. Part one of this analysis examined how to present resolution advisories (RAs) issued by Airborne Collision Avoidance System (ACAS) Xu, which can be in the vertical dimension, the horizontal dimension, or both (i.e., "blended"). The study varied the appearance of the alerting and the verbiage used in the aural alerts. Results revealed high acceptability ratings for the appearance of the RA guidance. Part two of the analysis assessed pilot acceptability of varying levels of automation in the collision avoidance (CA) task. Pilots experienced conditions in which ACAS Xu RAs were executed either manually or automatically (i.e., auto-Collision Avoidance). In some conditions the return to a previously filed course was also executed automatically (auto-Return to Course). Results indicated that improvements are needed to how the state of the automation is presented. Implications of these findings are also discussed.
NASA is sponsoring research and data collection with the FAA UAS Test Sites pertaining to sensor and integration of Ground Based Detect and Avoid (GBDAA). This talk will highlight the objectives of the working being conducted and data collection plans.
This presentation provides an overview of a recently completed human-in-the-loop simulation, conducted as part of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. This study explored the differential effects of four low size, weight, and power radar declaration ranges on pilot and system performance. Pilots were to avoid DAA well clear against cooperative and non-cooperative aircraft under 1.5, 2, 2.5, and 3 nautical mile non-cooperative detection ranges. Results revealed that pilot performance was primarily influenced by warning-level alert duration, with sufficient alerting time being most prevalent at 2.5 nautical miles and above.
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.
The "Unmanned Aircraft System (UAS) Integration into the National Airspace System (NAS)" Project conducted flight test program, referred to as Flight Test 3, at Armstrong Flight Research Center from June - August 2015. Four flight test days were dedicated to the NASA Ames-developed Detect and Avoid (DAA) System referred to as Autoresolver. The encounter scenarios, which involved NASA's Ikhana UAS and a manned intruder aircraft, were designed to collect data on DAA system performance in real-world conditions and uncertainties with four different surveillance sensor systems. Resulting flight test data and analysis results will be used to evaluate the DAA system performance (e.g., trajectory prediction accuracy, threat detection) and to add fidelity to simulation models used to inform Minimum Operating Performance Standards (MOPS) for integrating UAS into routine NAS operations.
There is an increasing need to fly Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) to perform missions of vital importance to national security and defense, emergency management, science, and to enable commercial applications. However, routine access by UAS into the NAS remains unrealized. The UAS community needs routine access to the global airspace for all classes of UAS. Based upon that need, the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD) Integrated Aviation Systems Program (IASP) UAS Integration in the NAS Project identified the following goal: To Provide research findings, utilizing simulation and flight tests, to support the development and validation of Detect and Avoid (DAA) and Command and Control (C2) technologies necessary for integrating UAS into the NAS. Because this is such a broad reaching challenge facing the UAS community, the UAS-NAS Project recognizes the importance of working together with others in Industry and Other Government Agencies to overcome the technical, operational, and public perception barriers.
There is an increasing need to fly Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) to perform missions of vital importance to national security and defense, emergency management, science, and to enable commercial applications. However, routine access by UAS into the NAS remains unrealized. The UAS community needs routine access to the global airspace for all classes of UAS. Based upon that need, the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD) Integrated Aviation Systems Program (IASP) UAS Integration in the NAS Project identified the following goal: To Provide research findings, utilizing simulation and flight tests, to support the development and validation of Detect and Avoid (DAA) and Command and Control (C2) technologies necessary for integrating UAS into the NAS. Because this is such a broad reaching challenge facing the UAS community, the UAS-NAS Project recognizes the importance of working together with others in Industry and Other Government Agencies to overcome the technical, operational, and public perception barriers.
This presentation gives insight into the research activities and efforts being executed in order to integrate unmanned aircraft systems into the national airspace system. This briefing is to inform others of the UAS-NAS FY16 progress and future directions.
Unmanned Aircraft Systems need to be able to comply with manned aviation ‘see and avoid’ separation requirements. A Detect and Avoid (DAA) System includes sensors, a tracker, and alerting and guidance algorithms that assist a remote pilot in maintaining separation from airborne traffic. To date, DAA system requirements development has focused on operations transiting to and from Class A or special use airspace. Current efforts are defining DAA system requirements for operations in and around terminal airspace. As a contribution to the current efforts, this paper highlights results from a Human in the Loop (HiTL) experiment comparing methods of changing from the transit-specific alerting and guidance criteria to proposed terminal-specific alerting and guidance criteria. It discusses operational considerations that are beyond the HiTL.