Search NASA⌕ Search

SEARCH · Search NASA

Results for “TCL3”

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.

TCL3 UTM (UAS Traffic Management) Flight Tests, Airspace Operations Laboratory (AOL) Report

The Technology Capability Level-3 (TCL3) flight tests were conducted at six different test sites located across the USA from March to May of 2018. The campaign resulted in over 830 data collection flights using 28 different aircraft and involving 20 flight crews. Flights not only varied in duration, but also in the environments and terrains over which they flew. The TCL3 tests highlighted four different types of tests: three tests focused on Communication, Navigation and Surveillance (CNS); six tests focused on Sense and Avoid (SAA) technologies; six tests focused on USS Data and Information Exchange (DAT); and five tests focused on exploring fundamental Concepts of the project (CON). This document presents data collected during the TCL3 tests that informed the operator’s experiences—the quality of the unmanned aerial system (UAS) Service Supplier (USS) information that the operator was provided with, the usefulness of this information, and the usability of the automation, both while airborne and on the ground. It is intended to complement the reports written by the test sites and the quantitative reports and presentations of the UAS Traffic Management (UTM) project. With the goal of instructing what the minimum information requirements and/or best practices might be in TCL3 operations, the driving enquiry was: How do you get the information you need, when you need it, to successfully fly a UAS in UTM airspace? This enquiry touches on two requirements for displays, which are to provide adequate situation awareness (SA) and to share information through a USS. The six test sites participating in the TCL3 tests flew a subset of the 20 tests (outlined above), with most sites working on a subset of each of the four types: Communications, Navigation and Surveillance (CNS); DAT; CON; and Sense and Avoid (SAA). The, mainly qualitative, data addressed in this report was collected by the AOL (Airspace Operations Laboratory) both on-site and remotely for each test. The data consists of the contents of end-of-day debriefs, end-of-day surveys, observer notes, and flight test information, all submitted as part of the Data Management Plan (DMP).

Martin, Lynne↗

Use of UAS Reports (UREPs) during TCL3 Field Testing

During the NASA Unmanned Aircraft System (UAS) Traffic Management (UTM) Project’s Technical Capability Level 3 (TCL3) demonstration, a service for stakeholders to share weather and aircraft observations was tested. The overall goal was to increase awareness of airspace and weather activity to increase a pilot’s ability to fly safely. To achieve this goal, a mechanism to share data was created, called “UAS Reports” or UREPs, which were generated by client systems and sent to a central data service. The data service provided subscriptions and allowed for data requests to share the reports that had been sent in by stakeholders. To execute this functionality, four FAA (Federal Aviation Administration)-designated UAS test sites performed UREP testing as part of TCL3. NASA provided the centralized service and test site partners flew missions and simulated activity at the test sites to generate data to send to the service. The loop was closed by having other clients (usually other small UAS operators) request those data from the service or subscribe to feeds from the service. Overall, the tests demonstrated the utility of such a service. In this report, the testing setup, data collection, and analysis of results are presented. The concept of UREPs has since been incorporated as a service within NASA’s Conflict Mitigation Model for UTM. The concept will continue to be tested in NASA’s TCL4 activities.

UTM↗

Effectiveness of Redundant Communications Systems in Maintaining Operational Control of Small Unmanned Aircraft

NASA has been researching prototype technologies for an Unmanned Aircraft System (UAS) Traffic Management (UTM) system to facilitate enabling of safe and efficient civilian low-altitude airspace and UAS operations, in a series of Technical Capability Levels (TCL) activities that are increasingly complex. In TCL1, completed in 2015, visual line-of-sight operations such as agriculture, firefighting and infrastructure monitoring were addressed with a focus on geofencing and operations scheduling. Technologies and requirements needed for beyond visual line-of-sight (BVLOS) operations in sparsely populated areas were examined in TCL2 in 2016, and those for operations over moderately populated areas in TCL3 in 2017 and 2018. TCL4 will build on the earlier TCLs and focus on technologies and requirements for operations in higher-density urban areas for tasks such as news gathering, package delivery and for managing large-scale contingencies. This paper describes a communications test conducted in TCL3 and discusses insights gained from the test. In the test, operators were directed to equip UAS with redundant Command and Control (C2) communications systems, send a maneuver command to Unmanned Aircraft (UA) via the primary system, then verify execution of the sent command. This exercise was repeated with each redundant system. The test was designed to assess effectiveness of redundant C2 systems in maintaining operational control of UA. Several UAS were configured with varying arrangements to achieve redundancy, including two identical radio modems using the same frequency band, WiFi and Long-Term Evolution (LTE) cellular modems, etc. From the test, digital data such as time maneuver command sent, time maneuver verified, etc., were collected. Descriptions of methods to detect loss of C2 communications and contingency steps for such event were collected and assessed. The final paper will include a detailed analysis of the collected data leading to the following insights. First, effectiveness of redundant C2 systems depends on several factors, such as operational environment and communications service availability. For example, use of two identical point-to-point radio to connect operator and UA on the same frequency band can be effective in mitigating radio malfunction when operating in an environment where possibility of Radio Frequency (RF) interference is low, such as over open plains. However, the same arrangement may not be effective where high level of RF transmissions in broad spectrum ranges can be expected, such as over or near urban areas. For redundant systems that consist of external communications services, such as cellular and satellite communications network, redundancy is maintained only in the areas where more than one services are available. Therefore, UAS operators should have the means to plan for and monitor the performance of external communications services they are relying on to control UA. Second, communications performance needs, such as the minimum data transfer rate and the maximum tolerable latency, should be assessed to reflect the potential hazard that can come from loss of UA control. For example, UA operations over desolate area pose less hazard to people than operations over densely populated area and performance need for the former would be less than the latter.

Jung, Jaewoo↗

Unmanned Aircraft System Traffic Management (UTM) Research Transition Team (RTT) Concept Working Group - Concept & Use Cases Package #2 Addendum: Technical Capability Level 3

This document is a product of the joint NASA and FAA Research Transition Team's (RTT) Concept Working Group (CWG) as part of the UAS Traffic Management (UTM) project. The scope of the document covers Technical Capability Level (TCL) 3 of the UTM research path and presents the 1) Terms and Definitions, 2) Foundational Principles, 3) Concept Narratives, 4) Use Cases, 5) Operational Views (OVs), and 6) Roles and Responsibilities of actors interacting within a TCL3 environment. The document includes additional use cases to accompany the RTT CWG Package #2 document.

UTM↗

TCL4 UTM (UAS Traffic Management) Nevada 2019 Flight Tests, Airspace Operations Laboratory (AOL) Report

The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) research project has been developing and testing concept ideas for enabling small UAS (sUAS) operations in low altitude airspace (ground to 400 feet). To do this, NASA has organized a series of flight test demonstrations. Technology Capability Level-4 (TCL4) flight tests were conducted at a Nevada, USA test site, during June 2019. The testing resulted in over 300 data collection flights using eight live rotorcraft, 15 simulated vehicles, involving six flight crews and five Unmanned Aerial System (UAS) Service Suppliers (USS). The TCL4 approach was designed to demonstrate five scenarios that set up five diverse sets of UAS events and activities. The Nevada test site focused on three of these scenarios: an incoming weather front, a concert event with an incident requiring an emergency response, and a scenario where multiple vehicles experienced Communication, Navigation, and Surveillance (CNS) issues. The test site created their scenarios to each have three phases and were required to complete three executions of each scenario, for a total of nine missions per Nevada vehicle per scenario. This document presents data collected from participants during the TCL4-Nevada flight test that provides information about how much and how well operators were able to make use of UTM functions and information, with the goal of exploring what the minimum information requirements and/or best practices might be in TCL4 operations. The driving enquiry was: how do UTM tools and features support (human) operators leading to safe and effective conduct of large-scale beyond visual line of sight (BVLOS) sUAS operations in “urban canyon” environments? As with the data collected during previous similar tests (e.g., TCL3, Martin et al., 2019), the quality of the UTM information exchanged, and the meaningfulness and therefore usefulness of this information, were all focal points of the questions asked and the data collected. Data aligned with five human-system attributes to indicate that UTM provided information that contributed to users’ ability to operate safely and effectively within UTM, but that information was not always complete and was sometimes unclear.

UTM↗

Automated Management of Small Unmanned Aircraft System Communications and Navigation Contingency

The number of small Unmanned Aircraft System (sUAS) operating in the low-altitude of the National Airspace System (NAS) has been rapidly increasing in the past few years and this number is expected to grow in the future. However, aside from a few special cases, all sUAS must fly within visual line-of-sight (VLOS) of their operators and this limitation is blocking highly anticipated beyond visual line-of-sight (BVLOS) sUAS applications such as package delivery from practice. To enable routine low-altitude BVLOS operations, there needs to be a traffic management ecosystem that complements the FAA’s Air Traffic Management (ATM) system, which does not provide air traffic services under 400 feet above ground level (AGL). NASA has been pioneering research and development of this ecosystem under UAS Traffic Management (UTM) project since 2015 in a series of Technical Capability Levels (TCL) activities that are increasingly complex. In TCL1, completed in 2015, visual line-of-sight operations such as agriculture, firefighting, and infrastructure monitoring were addressed with a focus on geofencing and operations scheduling. Technologies and requirements needed for BVLOS operations in sparsely populated areas were examined in TCL2 in 2016, and those for operations over moderately populated areas in TCL3 in 2017 and 2018. TCL4 is building on the earlier TCLs and focuses on technologies and requirements for operations in higher-density urban areas for tasks such as newsgathering and package delivery and for managing large-scale contingencies. To coordinate and facilitate the incremental implementation of the UTM ecosystem in the NAS, a Research Transition Team (RTT) has been formed between the FAA, NASA, and industry. The RTT is divided into four subgroups, concept and use case development, data exchange and information architecture, sense and avoid, and communications and navigation (C&N). This paper focuses on C&N subgroup activities, in particular about the development of automated sUAS communications and navigation contingency management. The goal of this development is to prepare sUAS to display predictable behavior while handling C&N off-nominal events. It is expected that the adoption of the presented automated contingency management by the sUAS community will accommodate and inform rulemaking towards governing low-altitude BVLOS operations.

Unmanned Aviation System (UAS) Traffic Management↗

Automated Management of Small Unmanned Aircraft System (UAS) Communications and Navigation Contingency

The number of small Unmanned Aircraft System (sUAS) operating in the low-altitude of the National Airspace System (NAS) has been rapidly increasing in the past few years and this number is expected to grow in the future. However, aside from a few special cases, all sUAS must fly within visual line-of-sight (VLOS) of their operators and this limitation is blocking highly anticipated beyond visual line-of-sight (BVLOS) sUAS applications such as package delivery from practice. To enable routine low-altitude BVLOS operations, there needs to be a traffic management ecosystem that complements the FAA’s Air Traffic Management (ATM) system, which does not provide air traffic services under 400 feet above ground level (AGL). NASA has been pioneering research and development of this ecosystem under UAS Traffic Management (UTM) project since 2015 in a series of Technical Capability Levels (TCL) activities that are increasingly complex. In TCL1, completed in 2015, visual line-of-sight operations such as agriculture, firefighting, and infrastructure monitoring were addressed with a focus on geofencing and operations scheduling. Technologies and requirements needed for BVLOS operations in sparsely populated areas were examined in TCL2 in 2016, and those for operations over moderately populated areas in TCL3 in 2017 and 2018. TCL4 is building on the earlier TCLs and focuses on technologies and requirements for operations in higher-density urban areas for tasks such as newsgathering and package delivery and for managing large-scale contingencies. To coordinate and facilitate the incremental implementation of the UTM ecosystem in the NAS, a Research Transition Team (RTT) has been formed between the FAA, NASA, and industry. The RTT is divided into four subgroups, concept and use case development, data exchange and information architecture, sense and avoid, and communications and navigation (C&N). This paper focuses on C&N subgroup activities, in particular about the development of automated sUAS communications and navigation contingency management. The goal of this development is to prepare sUAS to display predictable behavior while handling C&N off-nominal events. It is expected that the adoption of the presented automated contingency management by the sUAS community will accommodate and inform rulemaking towards governing low-altitude BVLOS operations.

Unmanned Aviation Systems (UAS) Traffic Management↗

UTM RTT CWG Concept & Use Cases Package #2

The Concept & Use Cases Package #2: Technical Capability Level 3 document represents the collaborative research efforts between the FAA and NASA as joint members of the Unmanned Aircraft System Traffic Management (UTM) Research Transition Team (RTT). Contained in this document are the 1) Terms and Definitions, 2) Foundational Principles, 3) Concept Narratives, 4) Use Cases, 5) Operational Views, and 6) Roles and Responsibilities of actors interacting within what is considered to be encompassed by Technical Capability Level 3 UTM operating environments. The contents of Package #2 should NOT be considered established policy or construed as regulatory in nature. What is presented is meant to communicate the current, agreed upon understanding between the FAA and NASA on particular features of UTM as exemplified through use cases and concept narratives for the purposes of supporting joint NASA/Industry Demonstrations and the UTM Pilot Program. It is also meant to foster discussion and refinement of the concepts and approaches being pursued by the other RTT working groups.

RTT↗