Results for “Traffic Management Initiatives” — Page 7

NASA NTRS2017

Hyper-Spectral Communications, Networking and ATM as Foundation for Safe and Efficient Future Flight: Transcending Aviation Operational Limitations with Diverse and Secure Multi-Band, Multi-Mode, and mmWave Wireless Links: Project Overview, Aviation Communications and New Signaling

NASA's Aeronautics Research Mission Directorate (ARMD) has recently solicited proposals and awarded funds for research and development to achieve and exceed the goals envisioned in the ARMD Strategic Implementation Plan (SIP). The Hyper-Spectral Communications and Networking for Air Traffic Management (ATM) (HSCNA) project is the only University Leadership Initiative (ULI) program to address communications and networking (and to a degree, navigation and surveillance). This paper will provide an overview of the HSCNA project, and specifically describe two of the project's technical challenges: comprehensive aviation communications and networking assessment, and proposed multi-band and multimode communications and networking. The primary goals will be described, as will be research and development aimed to achieve and exceed these goals. Some example initial results are also provided.

aeronautics↗

NASA NTRS2022

National Campaign (NC)-1 Strategic Conflict Management Simulation (X4) Final Report

Urban Air Mobility (UAM) enables highly automated, cooperative, passenger or cargo-carrying air transportation services in and around urban areas. UAM is a subset of the Advanced Air Mobility (AAM) concept under development by the National Aeronautics and Space Administration (NASA), the Federal Aviation Administration (FAA), and industry. The Strategic Conflict Management (SCM) Simulation, dubbed “X4”, was conducted between July 2021 and June 2022 by NASA with the FAA and industry to evolve the Provider of Services for UAM (PSU) that will be needed to ensure initial UAM operations can scale in the National Airspace System (NAS). The FAA UAM Concept of Operations (ConOps) v1 [1] served as an initial guiding document for the X4 airspace management system design to ensure the architecture supports testing of services provided by third-party service providers. To that end, the X4 architecture leveraged concepts and technologies developed for Unmanned Aircraft System (UAS) Traffic Management (UTM) while also developing and testing new capabilities and services needed for UAM. The architecture included an initial prototype of the FAA-Industry Exchange Protocol (FIDXP), third-party services such as the PSUs, and Discovery and Synchronization Service (DSS), and other new services such as Demand-Capacity Balancing (DCB) to facilitate UAM strategic conflict management. During X4, NASA led discussions and collaborated with seven industry airspace partners to develop initial airspace management concepts for UAM that drove what would be tested and evaluated during the simulations. The initial capabilities defined for PSU leveraged UTM UAS Service Supplier (USS) as a starting point and evolved to meet UAM requirements. These discussions were also an opportunity for NASA to collaborate with industry to develop a set of initial Community-Based Rules (CBRs). These CBRs enabled how UAM traffic would be cooperatively managed among UAM operators. The collaborative, iterative process of developing CBRs with industry during X4 provided insight into the challenges involved and identified the need for a suitable and effective forum for future CBR development. In parallel with these discussions, NASA conducted a series of seven software sprints and two collaborative simulations with the airspace partners that built up in complexity. Over the course of the year, all seven partners successfully completed all the sprints by demonstrating the required capabilities. They also participated in the two collaborative simulations to demonstrate how multiple PSUs could work together in a collaborative, more complex environment with higher traffic density. The X4 simulation accomplished NASA's objectives and helped advance the development of the seven participating PSUs. The lessons learned provided insight into key elements of the UAM Notional Architecture from the FAA ConOps v1 [1] and UTM technologies when applied to UAM: - Having a Concept of Use (ConUse) defined prior to the activity would accelerate the time and effort from concept development to testing. - While the UAM Notional Architecture provided a starting point for a federated architecture that support services provided by third-party providers, the USS and PSU differed in their capability definitions for operational intent submission and sharing, conformance monitoring, airspace authorization, strategic conflict management, airspace constraints and dynamic replanning. - While existing DSS developed for UTM provided a way for PSU and other UAM services (such as DCB) to discover relevant operations from each other, additional complexity and challenges were found during X4 testing and illuminated the need for a more suitable solution for UAM. Industry can leverage the results of this demonstration to accelerate UAM requirements, CBRs, and standards development. The FAA and other government municipalities and agencies will be able to leverage results to inform future policies and identify additional gaps that require further analysis, moving toward operationalization of UAM.

Urban Air Mobility↗

NASA NTRS2017

Subject Matter Expert Evaluation of Multi-Flight Common Route Advisories

Traffic flow management seeks to balance the demand for National Airspace System (NAS) flight resources, such as airspace and airports, with the available supply. When forecasted weather blocks nominal air traffic routes, traffic managers must re-route affected flights for weather avoidance. Depending on the nature and scope of the weather, traffic managers may use pre-coordinated re-routes such as Playbook Routes or Coded Departure Routes, or may design ad hoc local re-routes. The routes of affected flights are modified accordingly. These weather avoidance routes will, of course, be less efficient than the nominal routes due to increased flight time and fuel burn. In current traffic management operations, the transition into a weather avoidance re-routing initiative is typically implemented more aggressively than the transition out of that initiative after the weather has dissipated or moved away. For example, strategic large-scale Playbook re-routes are sometimes left in place (as initially implemented) for many hours before being lifted entirely when the weather dissipates. There is an opportunity to periodically modify the re-routing plan as weather evolves, thereby attenuating its adverse impact on flight time and fuel consumption; this is called delay recovery. Multi-Flight Common Routes (MFCR) is a NASA-developed operational concept and associated decision support tool for delay recovery, designed to assist traffic managers to efficiently update weather avoidance traffic routes after the original re-routes have become stale due to subsequent evolution of the convective weather system. MFCR groups multiple flights to reduce the number of advisories that the traffic manager needs to evaluate, and also merges these flights on a common route segment to provide an orderly flow of re-routed traffic. The advisory is presented to the appropriate traffic manager who evaluates it and has the option to modify it using MFCRs graphical user interface. If the traffic manager finds the advisory to be operationally appropriate, he or she would coordinate with the Area Supervisor(s) of the sectors that currently control the flights in the advisory. When the traffic manager accepts the MFCR advisory via the user interface, the corresponding flight plan amendments would be sent to the displays of the appropriate sector controllers, using the Airborne Re-Routing (ABRR) capability which is scheduled for nationwide operation in 2017. The sector controllers would then offer this time-saving route modification to the pilots of the affected flights via datalink (or voice), and implement the corresponding flight plan amendment if the pilots accept it. MFCR is implemented as an application in the software environment of the Future Air traffic management Concepts Evaluation Tool (FACET). This paper focuses on an initial subject matter expert (SME) evaluation of MFCR. The evaluation covers MFCRs operational concept, algorithm, and user interface.

Traffic flow management↗

NASA NTRS2017

Subject Matter Expert Evaluation of Multi-Flight Common Route Advisories

Traffic flow management seeks to balance the demand for National Airspace System (NAS) flight resources, such as airspace and airports, with the available supply. When forecasted weather blocks nominal air traffic routes, traffic managers must re-route affected flights for weather avoidance. Depending on the nature and scope of the weather, traffic managers may use pre-coordinated re-routes such as Playbook Routes or Coded Departure Routes, or may design ad hoc local re-routes. The routes of affected flights are modified accordingly. These weather avoidance routes will, of course, be less efficient than the nominal routes due to increased flight time and fuel burn. In current traffic management operations, the transition into a weather avoidance re-routing initiative is typically implemented more aggressively than the transition out of that initiative after the weather has dissipated or moved away. For example, strategic large-scale Playbook re-routes are sometimes left in place (as initially implemented) for many hours before being lifted entirely when the weather dissipates. There is an opportunity to periodically modify the re-routing plan as weather evolves, thereby attenuating its adverse impact on flight time and fuel consumption; this is called delay recovery. Multi-Flight Common Routes (MFCR) is a NASA-developed operational concept and associated decision support tool for delay recovery, designed to assist traffic managers to efficiently update weather avoidance traffic routes after the original re-routes have become stale due to subsequent evolution of the convective weather system. MFCR groups multiple flights to reduce the number of advisories that the traffic manager needs to evaluate, and also merges these flights on a common route segment to provide an orderly flow of re-routed traffic. The advisory is presented to the appropriate traffic manager who evaluates it and has the option to modify it using MFCRs graphical user interface. If the traffic manager finds the advisory to be operationally appropriate, he or she would coordinate with the Area Supervisor(s) of the sectors that currently control the flights in the advisory. When the traffic manager accepts the MFCR advisory via the user interface, the corresponding flight plan amendments would be sent to the displays of the appropriate sector controllers, using the Airborne Re-Routing (ABRR) capability which is scheduled for nationwide operation in 2017. The sector controllers would then offer this time-saving route modification to the pilots of the affected flights via datalink (or voice), and implement the corresponding flight plan amendment if the pilots accept it. MFCR is implemented as an application in the software environment of the Future Air traffic management Concepts Evaluation Tool (FACET). This paper focuses on an initial subject matter expert (SME) evaluation of MFCR. The evaluation covers MFCRs operational concept, algorithm, and user interface.

Human-in-the-loop Evaluation↗

NASA NTRSDate not supplied

Investigation of Intelligent Resource Management for Aviation Communications

The emergence of new aerial vehicles into the airspace as part of new initiatives, such as Advanced Air Mobility (AAM), will place growing demand for spectrum resources to support airspace operations. The traditional approach of using fixed channel allocations within standard service volumes will not allow for dynamic and efficient distribution of resources based on airspace demand; consequently, a new approach to aviation spectrum management will be required to meet the anticipated needs of airspace users. The National Aeronautics and Space Administration (NASA) is investigating the application of advanced concepts to implement a novel spectrum management approach that allows for the intelligent utilization of aviation spectrum throughout the airspace while maintaining the quality of service prescribed by aeronautical standards. This technical investigation evaluates the dynamic assignment of resources for both air-ground and air-air communication links applicable to both the emerging AAM initiative as well as the existing air traffic management system. The performance of the proposed spectrum management concepts will be evaluated using a custom modeling and simulation capability that is currently under development. The implementation of these approaches is anticipated to facilitate increased spectrum utilization efficiency and enhanced airspace capacity, which will better serve the needs of future applications.

Aeronautics↗

NASA NTRSDate not supplied

Investigation of Intelligent Resource Management for Aviation Communications

The emergence of new aerial vehicles into the airspace as part of new initiatives, such as Advanced Air Mobility (AAM), will place growing demand for spectrum resources to support airspace operations. The traditional approach of using fixed channel allocations within standard service volumes will not allow for dynamic and efficient distribution of resources based on airspace demand; consequently, a new approach to aviation spectrum management will be required to meet the anticipated needs of airspace users. The National Aeronautics and Space Administration (NASA) is investigating the application of advanced concepts to implement a novel spectrum management approach that allows for the intelligent utilization of aviation spectrum throughout the airspace while maintaining the quality of service prescribed by aeronautical standards. This technical investigation evaluates the dynamic assignment of resources for both air-ground and air-air communication links applicable to both the emerging AAM initiative as well as the existing air traffic management system. The performance of the proposed spectrum management concepts will be evaluated using a custom modeling and simulation capability that is currently under development. The implementation of these approaches is anticipated to facilitate increased spectrum utilization efficiency and enhanced airspace capacity, which will better serve the needs of future applications.

Eric Knoblock↗

NASA NTRSDate not supplied

Usability Evaluation of Fleet Management Interface for High Density Vertiplex Environments

To meet the rising demand for an Advanced Air Mobility (i.e. urban and rural unmanned aircraft systems) ecosystem, NASA Aeronautics Research Mission Directorate (ARMD) is hosting a series of simulations and flight tests under the High Density Vertiplex sub-project (HDV). HDV aims to develop an integrated automation architecture to support terminal area flight operations. The HDV simulations and flight tests address safety, integration, and operational challenges, while integrated systems and software demonstrate design readiness, robustness, and interoperability. During the initial HDV simulation in 2021, a prototype traffic management tool developed by NASA called Fleet Management Interface (FMI) was tested. FMI was designed to introduce an advanced level of human-automation interaction to aid both Ground Control Station Operators (GCSOs) and Fleet Managers (FMs) in remotely managing flights under their ownership. In a human-in-the-loop simulation, a usability study was conducted with FMI to identify optimal approaches for displaying information for human operators using subjective measures of usability, workload, situation awareness, risk, and trust, along with qualitative feedback. This study consisted of task analysis in which GCSO and FM subjects used an Urban Air Mobility (UAM) environment to develop and execute a plan for two different traffic scenarios of remotely controlled vehicles. In each scenario, a controlled vehicle completed a takeoff, active flight, and landing sequence while automated traffic flew in the background at a rate of 20 operations per hour. In the first scenario, the controlled vehicle flew a nominal route with takeoff and landing at the same vertiport. In the second scenario, the controlled vehicle started on the nominal route, then diverted to an unplanned location mid-flight. Results showed that self-reported performance, usability, trust, and situation awareness ratings of FMI were moderately to strongly high. There were small differences between scenarios, with Scenario 2 being perceived as more unstable, complex, variable, risky, and potentially harmful than Scenario 1. Furthermore, participants described improvements that could be made to create a better user experience. For example, users would like greater configurability of the interface based on their personal information requirements, and they would like the opportunity to review routes before assigning them. The results from this study will inform future development of the FMI with the end goal of creating a reference automation tool for airspace management procedures in AAM. The FMI could be introduced as a potential way to reduce dependency on traditional air navigation services through increased automation in high density vertiplex environments.

vertiplex↗

NASA NTRS2016

Safely Enabling Low-Altitude UAS Operations: Unmanned Aircraft System Traffic Management

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.

Low-altitude UTM↗

NASA NTRSDate not supplied

Usability Evaluation of Fleet Management Interface for High Density Vertiplex Environments

To meet the rising demand for an Advanced Air Mobility (AAM) (i.e. urban and rural unmanned aircraft systems) ecosystem, the NASA Aeronautics Research Mission Directorate (ARMD) is hosting a series of simulations and flight tests under the High Density Vertiplex sub-project (HDV) to prototype and study the effectiveness AAM capabilities under various operational contexts. HDV aims to develop an integrated automation architecture to support terminal area flight operations. The HDV simulations and flight tests address safety, integration, and operational challenges, while integrated systems and software demonstrate design readiness, robustness, and interoperability. During the initial HDV simulation in 2021, a prototype traffic management tool developed by NASA called the Fleet Management Interface (FMI) was tested. FMI was designed to introduce an advanced level of human-automation interaction to aid both Ground Control Station Operators (GCSOs) and Fleet Managers (FMs) in remotely managing flights under their ownership. In a human-in-the-loop simulation, a usability study was conducted with the FMI to identify optimal approaches for displaying information to human operators using subjective measures of usability, workload, situation awareness, risk, and trust, along with qualitative feedback. This study consisted of task analysis in which GCSO and FM subjects used an Urban Air Mobility (UAM) environment to develop and execute a plan for two different traffic scenarios of remotely controlled vehicles. In each scenario, a remotely controlled vehicle completed a takeoff, active flight, and landing sequence while simulated traffic flew in the background at a rate of 20 operations per hour. In the first scenario, the controlled vehicle flew a nominal route with takeoff and landing at the same vertiport. In the second scenario, the controlled vehicle started on the nominal route, then diverted to an unplanned location mid-flight. Results showed that self- reported performance, usability, trust, and situation awareness ratings of FMI were moderately to strongly high. There were small differences between scenarios, with Scenario 2 being perceived as more unstable, complex, variable, risky, and potentially harmful than Scenario 1. Furthermore, participants described improvements that could be made to create a better user experience. For example, users suggested customizable interfaces to accommodate information display preferences, and the ability to review routes before assigning them. The results from this study will inform future development of the FMI with the end goal of creating a reference automation tool for airspace management procedures in AAM. The FMI could serve to reduce dependency on traditional air navigation services through increased automation in high density vertiplex environments.

Fleet manager↗

NASA NTRS1998

Steps Towards the Integration of Conflict Resolution with Metering and Scheduling

NASA Ames Research Center is developing decision support tool technology for air traffic controllers to improve the efficiency and capacity of National Airspace System. The goal is to provide technology, tools and procedures that result in the highest possible level of user preferred trajectories whenever possible with safe and efficient traffic management when necessary. The work is being conducted under the NASA Advanced Air Transportation Technology Program in cooperation with the FAA through the Inter-Agency Integrated Product Team. The objective is to develop technology and procedures that lead towards a seamless integration of conflict resolution with metering and scheduling for arrival aircraft and en route aircraft that are under metering restrictions. A requirement is that the integration incorporate user preferred trajectories. The ultimate goal is the implementation and validation of the Descent Advisor (DA) concept which provides clearance advisories to a sector controller that simultaneously meet metering constraints, are conflict free, incorporate a user preferred (e.g., minimum fuel) descent profile, and generally require no further corrective clearance as the aircraft transitions from en route cruise into the TRACON. The DA concept may also be applied to en route aircraft under metering constraints, e.g., miles-in-trail. To achieve the DA concept a stepwise development and field evaluation is anticipated. This paper addresses the initial steps towards implementation of the DA. The Traffic Management Advisor (TMA) computes arrival time sequence and required delay information for display to the sector controller during periods when arrivals must be metered due to landing rate restrictions at the airport. The Initial Conflict Probe (ICP) compares trajectory predictions for all aircraft and alerts the controller when any two aircraft are predicted to violate separation standards (5 mi. and 2000 ft. in en route airspace). ICP also includes a trial planning function allowing the controller to develop and check a separate "what if" trajectory for conflict resolution. TMA and ICP currently operate independent of one another and have separate controller displays. The TMA meter list is on the radar controller's plan view display. The ICP is still under development, but the current concept calls for a list of predicted conflicts at the data controller position. The research described herein address two steps towards the implementation of DA. The first is to develop a concept for integrated display of conflict and metering information on a controller's display. The objective is to provide the controller with situational awareness of one problem while he develops a solution to the other. The next step is to expand the concept for display of automated clearance advisories for one problem (e.g., metering) which take into account the other problems (e.g., conflicts). Information to be communicated between TMA and ICP to facilitate' manual or automated advisories is being identified as the concept matures. In order to study the ICP/TMA integration concept the CTAS conflict probe capability has been adapted to Ft. Worth Center. The system is being validated in the laboratory with all-track data and for non -interference with TMA, TMA is already running as a daily use prototype at Ft. Worth Center. A laboratory prototype system has been developed under the CTAS baseline which combines conflict and metering information on a common user interface. Elements of the user interface are shown in Figure 1. In this simple illustration the user sees the simultaneous effect of a trial plan on meter fix delay and conflict status. Delay information is shown in the aircraft flight data block, the meter list, and the TMA timeline. Experience during Descent Advisor development and observations at Ft. Worth Center high and low attitude arrival sectors during metering suggests that manual trial planning will be unworkable during rush periods due to high controller workload.

McNally, B. David↗

NASA NTRS2019

Unmanned Autonomous Systems (UAS) Traffic Management

Educating California's Transportation Dept. (Caltrans) about Urban Air Mobility: what it is, how NASA is involved in this initiative, and plans for demonstrations (grand challenge).

UAM (Urban Air Mobility)↗

NASA NTRS1997

A Cognitive System Model for Human/Automation Dynamics in Airspace Management

NASA has initiated a significant thrust of research and development focused on providing the flight crew and air traffic managers automation aids to increase capacity in en route and terminal area operations through the use of flexible, more fuel-efficient routing, while improving the level of safety in commercial carrier operations. In that system development, definition of cognitive requirements for integrated multi-operator dynamic aiding systems is fundamental. In order to support that cognitive function definition, we have extended the Man Machine Integrated Design and Analysis System (MIDAS) to include representation of multiple cognitive agents (both human operators and intelligent aiding systems) operating aircraft, airline operations centers and air traffic control centers in the evolving airspace. The demands of this application require representation of many intelligent agents sharing world-models, and coordinating action/intention with cooperative scheduling of goals and actions in a potentially unpredictable world of operations. The MIDAS operator models have undergone significant development in order to understand the requirements for operator aiding and the impact of that aiding in the complex nondeterminate system of national airspace operations. The operator model's structure has been modified to include attention functions, action priority, and situation assessment. The cognitive function model has been expanded to include working memory operations including retrieval from long-term store, interference, visual-motor and verbal articulatory loop functions, and time-based losses. The operator's activity structures have been developed to include prioritization and interruption of multiple parallel activities among multiple operators, to provide for anticipation (knowledge of the intention and action of remote operators), and to respond to failures of the system and other operators in the system in situation-specific paradigms. The model's internal representation has been be modified so that multiple, autonomous sets of equipment will function in a scenario as the single equipment sets do now. In order to support the analysis requirements with multiple items of equipment, it is necessary for equipment to access the state of other equipment objects at initialization time (a radar object may need to access the position and speed of aircraft in its area, for example), and as a function of perception and sensor system interaction. The model has been improved to include multiple world-states as a function of equipment am operator interaction. The model has been used -1o predict the impact of warning and alert zones in aircraft operation, and, more critic-ally, the interaction of flight-deck based warning mechanisms and air traffic controller action in response to ground-based conflict prediction and alerting systems. In this operation, two operating systems provide alerting to two autonomous, but linked sets of operators, whose view of the system and whose dynamics in response are radically different. System stability and operator action was predicted using the MIDAS model.

Corker, Kevin M.↗

NASA NTRS1997

Empirical and Analytic Studies Human/Automation Dynamics in Airspace Management for Free Flight

NASA and the FAA have initiated programs of research and development to provide flight crew, airline operations and air traffic managers with automation aids to increase capacity in en route and terminal area to support the goals of free flight for safe, flexible, predictable, and efficient operations. To support the development of those aiding systems human performance in automated aiding has been examined in empirical and computationally analytic studies. This paper presents a set of those studies in full mission simulation and the development of a predictive computational model of human performance. We have found that the combination of methodologies provide a powerful design-aiding process. We will describe three research programs in support of Free Flight Operations from the perspective of human performance requirements. We have examined procedures and communications in the use of voice and data-link operation at the transition between unconstrained (enroute) and constrained (terminal) airspace operations. We have examined the timing and form of Center TRACON Automation System (CTAS) advisories in descent. We have investigated the shape and dimensions of an 'alert zone' for air-based separation in unconstrained operations. Finally, we have examined the interaction of a ground-based conflict detection/resolution aiding system, as it interacts with a cockpit-based conflict alerting mechanism. Additional information is contained in the original extended abstract.

Corker, Kevin M.↗

NASA NTRS2005

Airborne Management of Traffic Conflicts in Descent With Arrival Constraints

NASA is studying far-term air traffic management concepts that may increase operational efficiency through a redistribution of decisionmaking authority among airborne and ground-based elements of the air transportation system. One component of this research, En Route Free Maneuvering, allows trained pilots of equipped autonomous aircraft to assume responsibility for traffic separation. Ground-based air traffic controllers would continue to separate traffic unequipped for autonomous operations and would issue flow management constraints to all aircraft. To evaluate En Route Free Maneuvering operations, a human-in-the-loop experiment was jointly conducted by the NASA Ames and Langley Research Centers. In this experiment, test subject pilots used desktop flight simulators to resolve conflicts in cruise and descent, and to adhere to air traffic flow constraints issued by test subject controllers. Simulators at NASA Langley were equipped with a prototype Autonomous Operations Planner (AOP) flight deck toolset to assist pilots with conflict management and constraint compliance tasks. Results from the experiment are presented, focusing specifically on operations during the initial descent into the terminal area. Airborne conflict resolution performance in descent, conformance to traffic flow management constraints, and the effects of conflicting traffic on constraint conformance are all presented. Subjective data from subject pilots are also presented, showing perceived levels of workload, safety, and acceptability of autonomous arrival operations. Finally, potential AOP functionality enhancements are discussed along with suggestions to improve arrival procedures.

Doble, Nathan A.↗

NASA NTRSDate not supplied

Introduction to Air Traffic Management

The presentation introduces students and faculty to air traffic management with focus on air traffic data for data-science. Starting with the common attributes of transportation systems — highway transportation, air transportation and data transportation, the initial set of slides discuss the purpose of data-science in air traffic management, reasons why air traffic management is challenging, and the multidisciplinary nature of air traffic management research. The history of flight from 1903 — Wright Flyer — to 1987 — formation of the National Air Traffic Controllers Association — is briefly discussed. The national airspace system is described in terms of airports in the U. S., air traffic control facilities (flight service stations, terminal, enroute and system command center), airspace geometry (sectors, airways and navaids), governing regulations and directives, airspace classification (Class A through G), special use airspace, visual flight rules and instrument flight rules. The contents of a flight-plan are described. Weather briefing is discussed. The surveillance equipment used for surface, terminal area and enroute are described, and the aircraft states obtained using the surveillance data are listed. Airline operations control functions — schedule development, flight planning, resource scheduling and flight following — are noted. Next, the roles and responsibilities of air traffic controllers and traffic flow managers are discussed. Separation standards and conflict resolution techniques are outlined. Finally, traffic flow management techniques are reviewed with an illustrative example.

Air Traffic Management↗

NASA NTRSDate not supplied

Introduction to Air Traffic Management

The presentation introduces students and faculty to air traffic management with focus on air traffic data for data-science. Starting with the common attributes of transportation systems — highway transportation, air transportation and data transportation, the initial set of slides discuss the purpose of data-science in air traffic management, reasons why air traffic management is challenging, and the multidisciplinary nature of air traffic management research. The history of flight from 1903 — Wright Flyer — to 1987 — formation of the National Air Traffic Controllers Association — is briefly discussed. The national airspace system is described in terms of airports in the U. S., air traffic control facilities (flight service stations, terminal, enroute and system command center), airspace geometry (sectors, airways and navaids), governing regulations and directives, airspace classification (Class A through G), special use airspace, visual flight rules and instrument flight rules. The contents of a flight-plan are described. Weather briefing is discussed. The surveillance equipment used for surface, terminal area and enroute are described, and the aircraft states obtained using the surveillance data are listed. Airline operations control functions — schedule development, flight planning, resource scheduling and flight following — are noted. Next, the roles and responsibilities of air traffic controllers and traffic flow managers are discussed. Separation standards and conflict resolution techniques are outlined. Finally, traffic flow management techniques are reviewed with an illustrative example.

Air Traffic Management↗

NASA NTRS2018

UTM UAS Serivce Supplier Development: Sprint 1 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid.

UAS service supplier↗

NASA NTRS2018

UTM UAS Service Supplier Development: Sprint 2 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability.

software engineering↗