Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lost command and control link”

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.

Initial Assessment of Lost Command and Control Link Procedures

This paper presents an initial assessment of lost command and control (LC2L) procedures for large Uncrewed Aircraft Systems (UAS) in a simulated representative airspace environment using real airspace procedures. The experiment matrix consists of nine different flight routes: four nominal, four following current LC2L procedures, and one that routes the UAS more conservatively through less-busy airspace. For each route, eleven simulated UAS flights – in ten-minute increments – were flown into Fort Worth Alliance Airport following a real Instrument Approach Procedure. The simulated UAS flew amongst real recorded tracks of approximately 4,700 flights on January 18, 2022. The analysis focused primarily on the number of aircraft with which each UAS lost separation and where the losses occurred. This work presents a significant increase in testing capability and provides the foundation for further verification and validation of LC2L procedures using additional analysis metrics.

Uncrewed aircraft↗

Initial Assessment of Lost Command and Control Link Procedures

This paper presents an initial assessment of lost command and control (LC2L) procedures for large Uncrewed Aircraft Systems (UAS) in a simulated representative airspace environment using real airspace procedures. The experiment matrix consists of nine different flight routes: four nominal, four following current LC2L procedures, and one that routes the UAS more conservatively through less-busy airspace. For each route, eleven simulated UAS flights – in ten-minute increments – were flown into Fort Worth Alliance Airport following a real Instrument Approach Procedure. The simulated UAS flew amongst real recorded tracks of approximately 4,700 flights on January 18, 2022. The analysis focused primarily on the number of aircraft with which each UAS lost separation and where the losses occurred. This work presents a significant increase in testing capability and provides the foundation for further verification and validation of LC2L procedures using additional analysis metrics.

uncrewed aircraft↗

PAAV Concept Document

The Pathfinding for Airspace with Autonomous Vehicles (PAAV) Concept Document, version 1.0, lays out the key challenges and potential solutions for the use of uncrewed aircraft (UA) technology for future regional air cargo operations. The challenges and solutions described in this document were informed by communications with the UA industry community (e.g., RTCA, the Federal Aviation Administration, and regional air cargo business operators), as well as the PAAV team’s research activities during the last two years including four tabletop exercises, a human-in-the-loop simulation study, a numerical simulation study, a functional allocation study, and flight data analysis (Appendix A). This document first describes the expected operational context of PAAV (Section 2), such as the flight mission, baseline UAS components, nominal operations, m:N operations (i.e., "m" remote pilots per "N" aircraft), and off-nominal operations. This context sets the scope for the PAAV concept development work. PAAV concept development assumes that UA operations will be increasingly autonomous. Thus, near- and far-term assumptions are defined (Section 3). PAAV identified seven key challenges for UA operations (Section 4): - Flight route planning - Separation and flow management - Traffic pattern integration - Contingency management - Taxi, takeoff, and landing - m:N operations - Communications operations The following 13 potential solutions to these challenges are then described (Section 5): - Scalable communications architecture - Data link - Designated UAS corridors - Crew planning for m:N operations - Flight route optimization - Traffic load-level control - Trajectory solutions with data link - Automated hazard avoidance for m:N operations - Traffic pattern integration (TPI) tool - Standard lost command and control (C2) link (LC2L) procedures - Automated hazard avoidance under LC2L - Auto-taxi, auto-takeoff, and auto-land - Ground control station (GCS) user interface for m:N operations The document attempts to link each of these solutions to one or more of the challenge areas. Novel solutions involving numerous automation technologies are needed to mitigate traffic and airspace management challenges, especially for realizing m:N operations and ensuring safety under LC2L conditions. The purpose of this document is to help understand alternatives and tradeoffs among potential solutions and provide a foundation for a cohesive PAAV concept that will be described and refined in subsequent concept versions.

Unmanned aircraft, uncrewed aircraft, regional air↗

A Framework for Dynamic Architecture and Functional Allocations for Increasing Airspace Autonomy

To enable scalability of air travel for use cases such as cargo delivery, it is anticipated that future air traffic operations will involve unmanned aircraft operated by remote pilots. Of particular interest are schemes where a small number of pilots operate a large number of vehicles, mitigating high cost and pilot shortage issues. Such architectures require increased levels of automation and supervisory control modes. They also require ensuring safe operations when the command and control link to the vehicle is degraded or lost completely, rendering the vehicle autonomous. To evaluate these variable and dynamic architectures, this paper will present a framework for decomposing the functions necessary to ensure safe, orderly, and expeditious air travel, assessing the agents in the system, and classifying the levels of autonomy. Then, an example allocation to agents of roles for the function of separation assurance is presented, highlighting the dependency of the allocation on three main factors: time criticality of a potential separation violation, the ratio of pilots to vehicles, and the loss of the command and control link.

air traffic management, function allocation, auton↗

A Framework for Dynamic Architecture and Functional Allocations for Increasing Airspace Autonomy

To enable scalability of air travel for use cases such as cargo delivery, it is anticipated that future air traffic operations will involve unmanned aircraft operated by remote pilots. Of particular interest are schemes where a small number of pilots operate a large number of vehicles, mitigating high cost and pilot shortage issues. Such architectures require increased levels of automation and supervisory control modes. They also require ensuring safe operations when the command and control link to the vehicle is degraded or lost completely, rendering the vehicle autonomous. To evaluate these variable and dynamic architectures, this paper will present a framework for decomposing the functions necessary to ensure safe, orderly, and expeditious air travel, assessing the agents in the system, and classifying the levels of autonomy. Then, an example allocation to agents of roles for the function of separation assurance is presented, highlighting the dependency of the allocation on three main factors; time criticality of a potential separation violation, the ratio of pilots to vehicles, and the loss of the command and control link.

air traffic management↗

C2-Related Incidents Reported by UAS Pilots

It has been estimated that aviation accidents are typically preceded by numerous minor incidents arising from the same causal factors that ultimately produced the accident. Accident databases provide in-depth information on a relatively small number of occurrences, however incident databases have the potential to provide insights into the human factors of Remotely Piloted Aircraft System (RPAS) operations based on a larger volume of less-detailed reports. Currently, there is a lack of incident data dealing with the human factors of unmanned aircraft systems. An exploratory study is being conducted to examine the feasibility of collecting voluntary critical incident reports from RPAS pilots. Twenty-three experienced RPAS pilots volunteered to participate in focus groups in which they described critical incidents from their own experience. Participants were asked to recall (1) incidents that revealed a system flaw, or (2) highlighted a case where the human operator contributed to system resilience or mission success. Participants were asked to only report incidents that could be included in a public document. During each focus group session, a note taker produced a de-identified written record of the incident narratives. At the end of the session, participants reviewed each written incident report, and made edits and corrections as necessary. The incidents were later analyzed to identify contributing factors, with a focus on design issues that either hindered or assisted the pilot during the events. A total of 90 incidents were reported. This presentation focuses on incidents that involved the management of the command and control (C2) link. The identified issues include loss of link, interference from undesired transmissions, voice latency, accidental control transfer, and the use of the lost link timer, or lost link OK features.

unmanned aircraft systems↗

Best Practices Identified Through the Completion of UAS Flight Demonstrations

After several years of research into Detect and Avoid (DAA) and Command and Control (C2) systems for Unmanned Aircraft Systems (UAS), the National Aeronautics and Space Administration’s (NASA) UAS Integration into the National Airspace System project initiated a focused two-year effort along with the Federal Aviation Administration (FAA) and three industry partners to investigate remaining issues in the specification, test, certification and airspace integration to allow UAS operations in non-segregated airspace. The approach taken had the industry partners propose a flight demonstration approximating a commercial operation, while NASA helped, as needed, the partners through design and test phases and NASA observed interactions with the FAA. During this effort NASA collected best practices intended to be of value to similar UAS endeavors. These best practices can be divided into different sets, including practices that describe the relationship between business considerations to UAS design or describe several UAS development challenges. Another set includes best practices focused on navigating the UAS design and type certification processes. A third set includes best practices that relate to the design of the DAA system. Deploying DAA systems in this timeframe posed unique challenges. Commercial off-the-shelf DAA systems do not exist, necessitating custom development and, for two of the partners, the use of low-size, -weight, and -power (SWaP) sensors not completely specified for DAA. A fourth set of best practices relates to lost-link contingency planning. The final set of best practices relates to the design and testing of C2 systems and obtaining spectrum licenses. The UAS demonstrations were piloted remotely, and for all aspects of flight safety, a C2 system was required to communicate DAA and other UAS subsystem data to the remote pilot and to allow the pilot to issue commands to the vehicle. Throughout the course of this effort, the partners integrated prototype DAA and C2 systems into unmanned aircraft, tested those systems, and laid the groundwork for type certification programs that are expected to continue.

NASA↗