Search NASA⌕ Search

SEARCH · Search NASA

Results for “Tcl”

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.

49 records · Page 3

Remote ID for Rapid Assessment of Flight and Vehicle Information

The ability to rapidly identify UAS (Unmanned Aircraft Systems) in the field has emerged as a critical need for the integration of small UASs into the national airspace and counter-UAS operations. This paper proposes an architecture for rapid retrieval of UAS information leveraging NASA's current Unmanned Aircraft System (UAS) Traffic Management (UTM) system. The proposed architecture utilizes UTM components: FIMS (Flight Information Management System), USS (UAS Service Supplier), and vehicle registration and model database in order to provide assessment of the UAS reported in the field including the ability to distinguish between participating and non- participating UTM actors. Detailed system descriptions are provided and preliminary results from field tests conducted during UTM TCL (Technical Capability Level) 3 are discussed. It is found that 94 percent of the remote ID look-ups were successful. The average time of a look-up is found to be 1.2 seconds. Failure cases are examined and recommendations on next steps to advance UAS remote identification are provided.

USS (UAS Service Supplier)↗

Remote ID for Rapid Assessment of Flight and Vehicle Information

The ability to rapidly identify UAS in the field has emerged as a critical need for the integration of small UASs into the national airspace and counter-uas operations. This paper proposes an architecture for rapid retrieval of UAS information leveraging NASA's current Unmanned Aircraft System (UAS) Traffic Management (UTM) system. The proposed architecture utilizes UTM components: FIMS (Flight Information Management System), USS (UAS Service Supplier), and vehicle registration and model database in order to provide assessment of the UAS reported in the field including the ability to distinguish between participating and non- participating UTM actors. Detailed system descriptions are provided and preliminary results from field tests conducted during UTM TCL (Technical Capability Level) 3 are discussed. It is found that 94% of the remote ID look-ups were successful. The average time of a look-up is found to be 1.2 seconds. Failure cases are examined and recommendations on next steps to advance UAS remote identification are provided.

Ishihara, Abraham K.↗

Onboard Decision-Making for Nominal and Contingency sUAS Flight

This study presents an onboard decision-making architecture for small unmanned aerial systems (sUAS). The decision-maker is part of NASA's SAFE50 project that is working under the UAS Traffic Management (UTM) Technical Capability Level (TCL) 4 to provide autonomous point-to-point UAV flight in BVLOS, high-density urban environments. The decision-maker monitors various metrics to determine the safety and feasibility of the mission and categorizes flight states as Nominal, Off-Nominal, Alternate Land, and Land Now in a finite state machine. Changes in the monitored metrics serve as transitions in the state machine and trigger replanning. Navigation degradation and communication failure are simulated to show the feasibility of the decision-maker framework in appropriately switching the flight state.

Baculi, Joshua↗

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↗

UAS Service Supplier Network Performance

This report summarizes the performance of Unmanned Aircraft System (UAS) Service Suppliers (USS) in the Technical Capability Level 4 (TCL4) flight test performed by NASA and its partners in support of the UAS Traffic Management (UTM) concept. TCL4 is the final in a series of TCL demonstrations of a traffic management system for small UAS (sUAS). All demonstrations have been executed in collaboration with industry partners. The [FAA 2018] UTM Concept of Operations document describes UTM as:...the manner in which the FAA will support operations for predominantly sUAS operating in low altitude airspace. UTM utilizes industry’s ability to supply services under FAA’s regulatory authority where these services do not currently exist. It is a community-based traffic management system, where the Operators are responsible for the coordination, execution, and management of operations, with rules of the road established by FAA. UTM is designed to support the demand and expectations for a broad spectrum of operations with ever-increasing complexity and risk. UTM should be considered a collection of services rather than a monolithic application. The following section describes the architecture at a high level. For further insight, the FAA’s concept document [FAA 2018] or NASA’s earlier concept publication [NASA 2016] should be consulted.

Rios, Joseph L.↗

UAS Traffic Management Conflict Management Model

Version 2 of the UAS Traffic Management (UTM) Conflict Management Model. This document is a concept overview paper that describes the conflict mitigation methodology that supports the use cases described in TCL 4 operating environments (urban BVLOS operations). The general conflict mitigation model values the use of redundant mitigation technologies that operate over different time horizons to reach a target level of safety for the operation. Separation provision contributes to the safety of the overall separation, and each participant (USS, UAS, other airspace users) is responsible for ensuring separation is maintained between aircraft. The intent of this document is to capture the minimum level of separation provisions that are necessary for safe operations in the airspace. Additional equipage and capability can be seen as a mechanism to enhance safety but may not be the minimum need for entry into the airspace.

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↗

SERFE Ground Unit EVA Series After Three Year Spacesuit Stowage Period

NASA’s spacesuit government reference design for returning to the Moon is called the Exploration Extravehicular Mobility Unit (xEMU). The xEMU subassembly that provides life support, such as oxygen and thermal control, is the Portable Life Support System (PLSS). Inside the PLSS is a new technology that NASA wanted to test to provide cooling to the crew during EVAs (ExtraVehicular Activity). This technology is called the Spacesuit Water Membrane Evaporator (SWME). In order to test SWME in an improved thermal control loop (TCL) both on Earth and in Space, the Spacesuit Evaporation Rejection Flight Experiment (SERFE) was created. The Ground unit, or testbed at Johnson Space Center (JSC), tested the cooling technology in Earth’s gravity, while the Flight unit, or payload on the International Space Station (ISS), tested the cooling technology in micro-gravity. Since fluids flow differently in micro-gravity, testing in both environments would provide important data for improving cooling performance during EVAs. Both units completed 25 simulated EVAs with the same settings so SWME performance on the ground could be compared to the ISS. The Flight unit was completed first and performed EVAs on the ISS between 2020 and 2022. The Ground unit performed EVAs between 2021 and 2022. When the Flight unit came back from the ISS, it was taken apart for analysis. This analysis looked at how well SWME was able to maintain its heat rejection capability after various dwell times, such as a 90 day Airlock Coolant Loop Recovery (ALCLR) cycle, when the Extravehicular Mobility Unit (EMU) currently on the ISS would normally need maintenance. After a three year simulated spacesuit dwell, the Ground unit performed another EVA series in 2025 to test SWME’s shelf life. The results from this test series will inform mission planning as NASA plans to go back to the Moon and beyond.

Michael Lewandowski↗

SERFE Ground Unit EVA Series After Three Year Spacesuit Stowage Period

NASA’s spacesuit government reference design for returning to the Moon is called the Exploration Extravehicular Mobility Unit (xEMU). The xEMU subassembly that provides life support, such as oxygen and thermal control, is the Portable Life Support System (PLSS). Inside the PLSS is a new technology that NASA wanted to test to provide cooling to the crew during EVAs (ExtraVehicular Activity). This technology is called the Spacesuit Water Membrane Evaporator (SWME). In order to test SWME in an improved thermal control loop (TCL) both on Earth and in Space, the Spacesuit Evaporation Rejection Flight Experiment (SERFE) was created. The Ground unit, or testbed at Johnson Space Center (JSC), tested the cooling technology in Earth’s gravity, while the Flight unit, or payload on the International Space Station (ISS), tested the cooling technology in micro-gravity. Since fluids flow differently in micro-gravity, testing in both environments would provide important data for improving cooling performance during EVAs. Both units completed 25 simulated EVAs with the same settings so SWME performance on the ground could be compared to the ISS. The Flight unit was completed first and performed EVAs on the ISS between 2020 and 2022. The Ground unit performed EVAs between 2021 and 2022. When the Flight unit came back from the ISS, it was taken apart for analysis. This analysis looked at how well SWME was able to maintain its heat rejection capability after various dwell times, such as a 90 day Airlock Coolant Loop Recovery (ALCLR) cycle, when the Extravehicular Mobility Unit (EMU) currently on the ISS would normally need maintenance. After a three year simulated spacesuit dwell, the Ground unit performed another EVA series in 2025 to test SWME’s shelf life. The results from this test series will inform mission planning as NASA plans to go back to the Moon and beyond.

SWME↗

Flight Demonstration of Unmanned Aircraft System (UAS) Traffic Management (UTM) at Technical Capability Level 4

The NASA Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Project executed the fourth and final UTM Technical Capability Level demonstration between May and August 2019. Two Federal Aviation Administration (FAA)-designated UAS test sites managed the range, partners, and operations to meet the requirements set forth by the UTM Project. All stakeholders supported the execution of the flight testing through close collaboration. Results of the demonstration indicate the viability of the UTM concept to manage large scale operations and contingencies in an urban environment. The demonstration also provided insight into key technological gaps that must be addressed before such operations are routine, safe, and efficient. Standardization efforts related to UTM and the industry participants of those efforts can leverage the results and experiences of this flight activity to accelerate and more firmly ground forthcoming standards. The FAA and other regulators will be able to leverage results to inform future rule-making and identify additional gaps that require further analysis.

Unmanned Aircraft System Traffic Management↗

Small Unmanned Aircraft System Communications and Navigation Performance

NASA performed research and development of technologies and requirements for traffic management of small Unmanned Aircraft Systems (UAS). In this effort, four measures of performance (MOPs) were developed to understand the performance of small UAS communications and navigation systems in urban operations. This Technical Memorandum (TM) describes UAS Traffic Management (UTM) operational architecture, UTM Technical Capability Level 4 (TCL4) flight tests that took place in two different urban settings, the four MOPs, and the TCL4 MOP results.

Unmanned Aviation Systems Traffic Management↗