Unmanned Aircraft Systems (UAS) Controller Acceptability Study 3 (CAS3): Collision Avoidance, Self Separation, and Alerting Times (CASSAT): Combined PER/FER
No abstract available
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.
No abstract available
Just a year ago we laid out the UTM challenges and NASA's proposed solutions. During the past year NASA's goal continues to be to conduct research, development and testing to identify airspace operations requirements to enable large-scale visual and beyond visual line-of-sight UAS operations in the low-altitude airspace. Significant progress has been made, and NASA is continuing to move forward.
No abstract available
Conduct research, development and testing to identify airspace operations requirements to enable large-scale visual and beyond visual line of sight UAS operations in the low-altitude airspace. Use build-a-little-test-a-little strategy remote areas to urban areas Low density: No traffic management required but understanding of airspace constraints. Cooperative traffic management: Understanding of airspace constraints and other operations. Manned and unmanned traffic management: Scalable and heterogeneous operations. UTM construct consistent with FAAs risk-based strategy. UTM research platform is used for simulations and tests. UTM offers path towards scalability
The primary activity for the UAS-NAS Human Systems Integration (HSI) sub-project in Phase 1 was support of RTCA Special Committee 228 Minimum Operational Performance Standards (MOPS). We provide data on the effect of various Detect and Avoid (DAA) display features with respect to pilot performance of the remain well clear function in order to determine the minimum requirements for DAA displays.
The Phase 1 DAA Minimum Operational Performance Standards (MOPS) provided requirements for two classes of DAA equipment: equipment Class 1 contains the basic DAA equipment required to assist a pilot in remaining well clear, while equipment Class 2 integrates the Traffic Alert and Collision Avoidance (TCAS) II system. Thus, the Class 1 system provides RWC functionality only, while the Class 2 system is intended to provide both RWC and Collision Avoidance (CA) functionality, in compliance with the Minimum Aviation System Performance (MASPS) for the Interoperability of Airborne Collision Avoidance Systems. The FAAs TCAS Program Office is currently developing Airborne Collision Avoidance System X (ACAS X) to support the objectives of the Federal Aviation Administrations (FAA) Next Generation Air Transportation System Program (NextGen). ACAS X has a suite of variants with a common underlying design that are intended to be optimized for their intended airframes and operations. ACAS Xu being is designed for UAS and allows for new surveillance technologies and tailored logic for platforms with different performance characteristics. In addition to Collision Avoidance (CA) alerting and guidance, ACAS Xu is being tuned to provide RWC alerting and guidance in compliance with the SC 228 DAA MOPS. With a single logic performing both RWC and CA functions, ACAS Xu will provide industry with an integrated DAA solution that addresses many of the interoperability shortcomings of Phase I systems. While the MOPS for ACAS Xu will specify an integrated DAA system, it will need to show compliance with the RWC alerting thresholds and alerting requirements defined in the DAA Phase 2 MOPS. Further, some functional components of the ACAS Xu system such as the remote pilots displayed guidance might be mostly references to the corresponding requirements in the DAA MOPS. To provide a seamless, integrated, RWC-CA system to assist the pilot in remaining well clear and avoiding collisions, several issues need to be addressed within the Phase 2 SC-228 DAA efforts. Interoperability of the RWC and CA alerting and guidance, and ensuring pilot comprehension, compliance and performance, will be a primary research area.
This presentation is a review of detect and avoid (DAA) research conducted over the last five years in support of RTCCA SC 228.
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.
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 discussion will highlight general human factors problem areas in design, with the hope that future UAS designers will be better equipped with knowledge of best practices.
No abstract available
No abstract available
This presentation is a high level overview for the UAS community of current operations.
Overview of UAS Traffic Management and CN (Communications and Navigation) RTT (Research Transition Team) working group.
This is a presentation for a Cisco Internet of Things (IoT) Systems Engineering Virtual Training (SEVT) event. The presentation provides an overview of the UTM concept, architecture, flight test events, and lessons learned. Networking hardware used in support of flight tests is also described.
No abstract available
UAS demand slides discuss the purpose, scope, and assumptions of the UAS Demand Forecast Study. It discusses some operational environments and market research study, this information is broad knowledge in the UAS community.
A significant level of debate and confusion has surrounded the meaning of the terms "autonomy" and "automation". Automation is a multi-dimensional concept, and we propose that RPAS automation should be described with reference to the specific system and task that has been automated, the context in which the automation functions, and other relevant dimensions. In this paper, we present a definition of "automation". We recommend that autonomy and autonomous operations are out of the scope of the RPAS panel. WG7 proposes to develop, in consultation with other workgroups, a taxonomy of "Levels of Automation" for RPAS.