Engineering topics
Publications and source records attributed to Joseph Rios.
In order for UTM to support safe multiple UAS operations within and beyond visual line of sight, data related to weather, 3D structures, other aircraft, etc. must be made available. To support safe operations data must be collected and maintained considering security and resilience.
NASA’s Unmanned Aircraft Systems (UAS) Traffic Management (UTM) project introduced a new Air Traffic Management (ATM) architecture that utilizes industry’s ability to supply industry-developed, third-party services that work complementarily with the FAA-provided Air Traffic Service (ATS) to exchange relevant air vehicle information among the UAS operations and between the UTM and the conventional ATM system. The UTM architecture was used to successfully demonstrate the feasibility of safe, efficient, and scalable small UAS operations in low altitudes below 400 feet above ground level. Following the success and adoption of UTM architecture, the foundational UTM requirements and core properties were generalized to become Extensible Traffic Management (xTM) requirements to support operations of new entrants beyond small UAS, such as operations in high altitudes over 60,000 feet, designated as upper Class E in the United States National Airspace System (NAS). In this paper, the generalization of UTM to xTM and NASA’s approach for developing an xTM system for upper Class E Traffic Management (ETM) are discussed. The paper also discusses the planned research to examine the potential xTM-Air Traffic Control (ATC) interactions across multiple xTM systems and identify common coordination procedures, ATC roles/responsibilities, and data exchange requirements. This work is one of the steps for improving interoperability between the xTM systems and ATS, which is critical for safe and efficient sharing of the airspace among the new entrants served by the xTM systems and conventional ATS-serviced operations.
The UAM Airspace research roadmap defined herein is expected to be an important tool for the execution of NASA’s research over the next ten years, with the goal of evolving UAM airspace to UML-4. It provides a basis for prioritizing and coordinating research efforts, and for integrating results that build towards NASA’s research goals. The roadmap also has the potential to serve as a focal point for ongoing and continuous deliberation, as has been the case during its development. It naturally attracts questions and feedback that are beneficial to overall understanding, which is key to NASA’s leadership in defining the airspace of the future.
Overview of UTM Concepts and Architecture presented to JARUS as they discuss UAS safety.
Many applications of small Unmanned Aircraft System (sUAS) have been envisioned. These include surveillance of key assets such as pipelines, rail, or electric wires, deliveries, search and rescue, traffic monitoring, videography, and precision agriculture. These operations are likely to occur in the same airspace in presence of many static and dynamic constraints such as airports, and high wind areas. Therefore, small UAS, typically 55 pounds and below, operations need to be managed to ensure safety and efficiency of operations is maintained. This paper will describe the Concept of Operations (ConOps) for NASA's UAS Traffic Management (UTM) research initiative. The UTM ConOps is focused on safely enabling large-scale small UAS (sUAS) operations in low altitude airspace. The UTM construct supports large-scale visual line of sight and beyond visual line of sight operations. It is based on two primary mantras: (1) flexibility where possible and structure where necessary (2) a risk-based approach where geographical needs and use case indicate the airspace performance requirements. Preliminary stakeholder feedback and initial UTM tests conducted by NASA show promise of UTM to enable large-scale low altitude UAS operations safely.
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.
The objective of this presentation is to share insights into the research conducted, lessons learned, and next steps toward the future of UTM by providing an overview and history of the UTM project.
This presentation is an overview of the NASA UTM Project’s efforts on the architecture and data exchanges related to UTM. It covers the evolution of the overall system, a walk through of the current architecture, a summary of impacts of the work, and several references to relevant UTM publications.
Overview of PSU presented to NASA’s Advanced Air Mobility (AAM) Ecosystem Working Groups (AEWG).
Explore the source record for details and available documents.
NASA’s Unmanned Aircraft Systems (UAS) Traffic Management (UTM) project introduced a new Air Traffic Management (ATM) architecture that utilizes industry’s ability to supply industry-developed, third-party services that work complementarily with the FAA-provided Air Traffic Service (ATS) to exchange relevant air vehicle information among the UAS operations and between the UTM and the conventional ATM system. The UTM architecture was used to successfully demonstrate the feasibility of safe, efficient, and scalable small UAS operations in low altitudes below 400 feet above ground level. Following the success and adoption of UTM architecture, the foundational UTM requirements and core properties were generalized to become Extensible Traffic Management (xTM) requirements to support operations of new entrants beyond small UAS, such as operations in high altitudes over 60,000 feet, designated as upper Class E in the United States National Airspace System (NAS). In this paper, the generalization of UTM to xTM and NASA’s approach for developing an xTM system for upper Class E Traffic Management (ETM) are discussed. The paper also discusses the planned research to examine the potential xTM-Air Traffic Control (ATC) interactions across multiple xTM systems and identify common coordination procedures, ATC roles/responsibilities, and data exchange requirements. This work is one of the steps for improving interoperability between the xTM systems and ATS, which is critical for safe and efficient sharing of the airspace among the new entrants served by the xTM systems and conventional ATS-serviced operations.
Concepts for the management of Uncrewed Aircraft Systems (UAS) at scale rely on the exchange of data amongst multiple stakeholders. Even as these concepts vary from State to State and company to company as of today, the movement of data between different entities is a common theme. While there is universal agreement on the necessity of appropriate cybersecurity applied to the various systems involved in communicating these data, there has been little focus on a feasible implementation of non-repudiation in these systems. This paper highlights the current and future need for non-repudiation, supported by references to multiple international organizations, and an approach to implementing non-repudiation leveraging open standards.
This is a slide deck for use by NASA personnel when discussing NASA's Federated Airspace Management Framework (Freddie) facility. An overview of the capabilities, current work, and past accomplishments.
Satellite constellations that employ on-spacecraft flight dynamics and conjunction assessment (CA) approaches face particular challenges. First, they must arrange to obtain and upload to the constellation satellite close approach information, such as Conjunction Data Messages, so that their on-board systems will have the data they need to make informed CA decisions. Second, given current latencies in obtaining CA screening information, such systems often cannot obtain dedicated screenings of their proposed maneuvers before they are executed. Third, they usually cannot engage in real time with owner/operators (O/Os) with whom they may come into conjunction, relying instead on pre-arranged courses of action that may or may not fit a given situation well. Despite these difficulties, it is nonetheless possible, as operators such as SpaceX have demonstrated, to operate safely using on-board CA calculations, in the presence of a largely collaborative operating environment. The situation breaks down, however, when two constellations that operate with such a paradigm are placed in the same orbital region and will experience conjunctions with each other. Each may have a vague idea of where the other’s satellites are, or perhaps even a somewhat precise idea if they exchange O/O ephemerides, but neither will know the other’s more immediate maneuver intentions, especially for situations in which they are in a high-risk conjunction with each other and a mitigation maneuver is required. As there is no formalized way for these automated systems to ascertain each other’s intentions for this type of conjunction, it is quite possible that each spacecraft may choose a maneuver that results in the two objects’ colliding. An opportunity to develop a solution to this problem was presented by the NASA “Starling” project, a small experimental constellation developed to demonstrate autonomous satellite control and constellation reconfiguration and for which a launch was obtained that, serendipitously, will place this constellation close to the SpaceX Starlink constellation. Because the NASA constellation is experimental, an extended mission part of the mission has been negotiated to implement and test mechanisms for resolving the problem of co-located constellations with on-board flight dynamics control. For the last eighteen months, a consortium among NASA Ames (the Starling satellite providers), NASA CARA (the Agency organization responsible for conjunction assessment), Space X, and the Department of Commerce (in observer status) has met regularly to assemble a concept of operations for a robust solution to this problem and has developed a prototype ground node that will serve as a needed CA screening and information dispensary. The approach and methods, as well as the active employment of the developed ground node, will be tested both in simulation before actual use and then in actual spacecraft operations, which are anticipated to begin in January 2024. This paper will describe the co-located autonomously-controlled constellation problem and the developed solution in detail, outlining what ground node (i.e., government) infrastructure and features are required, what particular capabilities are needed by the constellations themselves in order to make use of this deconfliction paradigm, and the migration path forward to allow such a capability set to be incorporated by the Department of Commerce’s space traffic coordination system.
Explore the source record for details and available documents.
The NASA Agile Community of Practice recently hosted the first NASA Agile Technical Interchange Meeting (TIM). The TIM provided an opportunity for Agile practitioners across the Agency to share their successes, challenges, and recommendations from Agile transformations. NASA has increasingly turned to private industry for collaborative efforts in space exploration, satellite deployment, and other missions. Embracing Agile principles, NASA is adapting its project management strategies to foster more flexible, efficient, and collaborative relationships with commercial partners. This paper provides highlights from the projects presented at the Agile TIM on how those teams have been able to iterate rapidly, respond to changing requirements, and deliver value more effectively.