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.
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
This presentation offers an overview of the Advanced Capabilities for Emergency Response Operations (ACERO) project, highlighting key accomplishments in FY24 and outlining the plan for the first Technical Challenge, which is scheduled for completion by FY30.
The Technology Capability Level-2 National Campaign (TCL2nc) was conducted at six different test-sites located across the USA, during May and June of 2017. The campaign resulted in over 240 data collection flights using 24 different aircraft and involving 23 flight crews. Flights not only varied in duration, but also in the environments and terrains over which they flew. The TCL2nc highlighted beyond visual line of sight (BVLOS) and altitude-stratified operations, and saw five partners bring their own, independently built, UAS Service Supplier (USS) for use during the flight tests. This document presents data collected during the TCL2nc that informs the 'Operator' section of the 'Requirements/Best Practices' from the UTM Technical Capability Matrix and Guidelines to Operate (Rios, version as of March 2017). A review of the data collected indicated that although teams were well qualified on paper (in terms of both completing training and having experience with flying UAS vehicles), greater consideration should be given to the unique perspectives and backgrounds of future UAS operators. Overall, teams looked at a variety of sources for information, including USS client-displays, and participants became more mindful of the need to be aware of other vehicles, highlighting the value of reporting information. Observations found that flight crews' time to respond to a UTM issue depended heavily on the team structure, communication efficiency, and crew procedures. These points are discussed in more detail below.
Concept of operations; Roles, responsibilities, implications on who pays; Information architecture paved way for FAA's (Federal Aviation Administration's) RFI (Request for Information); Demonstrated initial feasibility of architecture, application-protocol-interface-based approach, and overall construct; Data exchange and protocols; Demonstration of UTM (Unmanned Aerial Systems Traffic Management) TCL1 (Tuscaloosa, AL Airport Terminal 1) with all 6 test sites; Initial demonstration of UTM TCL2 for BVLOS (Beyond Visual Line-of-Sight) requirements.
Agenda - Wildfire Impacts - Needs Assessment - Prior and Current Research - ACERO Approach - Summary and Discussion
The Discovery and Synchronization service (DSS) has implemented some reasonable technical controls that help improve security and there are very few technical findings. The use of Docker and Kubernetes helps simplify the deployment process, and the DSS uses mutual TLS (mTLS) to connect. Much of the security risk across the DSS is a factor of its nature, a distributed environment that relies on all members to secure their parts correctly. As such, the DSS team should attempt to emphasize security controls that reduce complexity for securing entities’ Cockroach DB (CRDB) instances properly and improve coordination among DSS members for things like security patching, incident response, detecting, and removing bad actors. The DSS team must recognize that operating a DSS instance securely will require a combination of technical and procedural controls. Each DSS entity must configure their instance properly and follow standard operating procedures to ensure that the DSS service is secure.
This is a slide set for presentation at the 4th Federal UAS Workshop jointly hosted by NASA and USGS. The contents of the slide cover the work currently being performed with respect to the Upper Class E Traffic Management (ETM) concept, which addresses the needs and gaps in the management of high altitude airspace operations. This concept leverages elements developed through the UAS Traffic Management project with respect to a cooperative, service-based approach that provides services and capabilities in areas (e.g., Upper E airspace) that currently receive no or limited service from Air Traffic Control. This concept is meant to provide a safe, fair, and scalable approach to management of Upper E operations that reduces the burden on ATC while providing the flexibility and access desired by current and new users of the airspace. This set of slides includes an overview and rationale of the ETM concept, a recap of the progress made, the road ahead, and the place of ETM within its parent project: Air Traffic Management-eXploration (ATM-X).
The present study investigated the effects of remotely piloted unmanned aircraft (UA) voice communication delay on air traffic management operations with different background sector traffic-volume levels. Three one-way UA voice delay lengths of 400, 900, and 2,000 milliseconds (ms) were tested, representing the currently estimated transmission delays for terrestrial, satellite communication (SATCOM), and long SATCOM Command and Control Link System, respectively. All delay values exceeded 390 ms, the FAA’s current requirement for the maximum communication latency in the National Airspace System. Eight retired en route air traffic controllers (ATCs) and eight remote pilots (RPs) participated in a human-inthe-loop simulation study, where a simulated UA flight transitioned through an Oakland en route low-altitude sector to a local non-towered airport. The results showed that, when the 2,000-ms voice delay was present, radio transmission step-ons and detect-and-avoid (DAA) alert level elevations increased. In addition, ATC workload, ATC acceptability for the UA, and RP acceptability for the DAA were negatively affected only when the UA had a 2,000-ms voice delay under the high traffic-volume condition, but not in the other conditions.
The present study investigated the effects of remotely piloted unmanned aircraft (UA) voice communication delay on air traffic management operations with different background sector traffic-volume levels. Three one-way UA voice delay lengths of 400, 900, and 2,000 milliseconds (ms) were tested, representing the currently estimated transmission delays for terrestrial, satellite communication (SATCOM), and long SATCOM Command and Control Link System, respectively. All delay values exceeded 390 ms, the FAA’s current requirement for the maximum communication latency in the National Airspace System. Eight retired en route air traffic controllers (ATCs) and eight remote pilots (RPs) participated in a human-in-the-loop simulation study, where a simulated UA flight transitioned through an Oakland en route low-altitude sector to a local non-towered airport. The results showed that, when the 2,000-ms voice delay was present, radio transmission step-ons and detect-and-avoid (DAA) alert level elevations increased. In addition, ATC workload, ATC acceptability for the UA, and RP acceptability for the DAA were negatively affected only when the UA had a 2,000-ms voice delay under the high traffic-volume condition, but not in the other conditions.
Communications, Navigation and Surveillance (CNS) requirements must be developed in order to establish a CNS architecture supporting Unmanned Air Systems integration in the National Air Space (UAS in the NAS). These requirements must address cybersecurity, future communications, satellite-based navigation and APNT, and scalable surveillance and situational awareness. CNS integration, consolidation and miniaturization requirements are also important to support the explosive growth in small UAS deployment. Air Traffic Management (ATM) must also be accommodated to support critical Command and Control (C2) for Air Traffic Controllers (ATC). This document therefore presents UAS CNS requirements that will guide the architecture.
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.
The Air Traffic Management eXploration project, or ATM-X, is transforming air traffic management to accommodate new air vehicles and improve the efficiency of existing aviation operations – from commercial aircraft to autonomous aircraft and urban air taxis.
As a result of the FAA Modernization and Reform Act of 2012, Unmanned Aerial Systems (UAS) are expected to be integrated into the National Airspace System (NAS) by 2015. Several human factors challenges need to be addressed before UAS can safely and routinely fly in the NAS with manned aircraft. Perhaps the most significant challenge is for the UAS to be non-disruptive to the air traffic management system. Another human factors challenge is how to provide UAS pilots with intuitive traffic information in order to support situation awareness (SA) of their airspace environment as well as a see-and-avoid capability comparable to manned aircraft so that a UAS pilot could safely maneuver the aircraft to maintain separation and collision avoidance if necessary. A simulation experiment was conducted to examine baseline compliance of UAS operations in the current airspace system. Researchers also examined the effects of introducing a Cockpit Situation Display (CSD) into a UAS Ground Control Station (GCS) on UAS pilot performance, workload and situation awareness while flying in a positively controlled sector. Pilots were tasked with conducting a highway patrol police mission with a Medium Altitude Long Endurance (MALE) UAS in L.A. Center airspace with two mission objectives: 1) to reroute the UAS when issued new instructions from their commander, and 2) to communicate with Air Traffic Control (ATC) to negotiate flight plan changes and respond to vectoring and altitude change instructions. Objective aircraft separation data, workload ratings, SA data, and subjective ratings regarding UAS operations in the NAS were collected. Results indicate that UAS pilots were able to comply appropriately with ATC instructions. In addition, the introduction of the CSD improved pilot SA and reduced workload associated with UAS and ATC interactions.
Environment-based disasters, such as wildfire, can cause substantial loss of life and loss of property and are costing billions of dollars annually. Existing disaster response operations are complex, with many challenges. The aim of the Scalable Traffic management for Emergency Response Operations (STEReO) system is to demonstrate the application of technologies that will enable small, low-altitude Unmanned Aerial System operations to safely take place in the airspace above a disaster event, increasing the effectiveness of the response. As a first step, the project aims to build a small prototype to demonstrate and test the core functions of this system based on user needs and requirements that were gathered from experts in the field during discussions and walkthroughs.
An overview of UTM (UAS (Unmanned Aircraft Systems) Traffic Management) and UAM (Urban Air Mobility).
NASA is exploring a proposed new operating mode called digital flight, a complement to VFR and IFR. Under digital flight rules, the aircraft operator would use automation, traffic awareness, information services, and cooperative practices to ensure separation from other flights in VMC and IMC. The presentation describes how digital flight safely increases airspace access and operating flexibility for qualified operators, and its harmonizing approach to emerging future operations.
As technology has improved, operators have sought to use cubesats, as well as smallsats more generally, to perform increasingly more ambitious and sophisticated functions. Despite this, practical concerns associated with cubesat infant mortality, conjunctions, limited maneuverability, and debris generation have been relatively muted because most cubesats have been launched to lower orbits that limit both their orbital lifetime and consequences should a collision occur. NASA ARC has developed a concept for a highly-automated and distributed space traffic management (STM) architecture, drawing on similar work done to provide traffic management for small unmanned aerial systems (UAS) operating at low altitudes. The system proposes a strategy to accommodate growing space traffic volume safely, as well as pave the way for a transition of civil STM authority to a civilian governmental entity. The architecture envisions an open-access software platform architecture of data and service suppliers, consumers, and regulators, connected via a set of application programming interfaces (APIs). The platform would build on, rather than replicate existing integration and coordination efforts within the space situational awareness ecosystem, using existing standards for data message formats from organizations like the Consultative Committee for Space Data Systems and wrapping, rather than replacing existing integrations. We will present an initial STM architecture in this presentation, with a few examples showing how stakeholders can interact structurally, but flexibly, within this architecture.