Search NASA⌕ Search

SEARCH · Search NASA

Results for “Tactics”

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.

At least 271 records · Page 15

Large-Scale V/STOL Experimental Investigations of an Ejector-Lift Fighter and a Twin Tilt-Nacelle Transport

In the 1980s NASA Aeronautics was actively involved in full-scale wind tunnel testing of promising VSTOL aircraft concepts. This presentation looks at two, a multi-role fighter and a subsonic tactical transport. Their strengths and weaknesses are discussed with some of the rationale that ultimately led to the selection of competing concepts for production, namely the V-22 Osprey and the F-35 Lightning. The E7-A STOVL multi-role fighter was the product of an aircraft development program in the late 1980s by NASA, the Defense Advanced Research Projects Agency (DARPA), the Canadian Department of Industry Science and Technology (DIST), and industry partners General Dynamics and Boeing Dehavilland. The program was conducted an in response to increasing US-UK interest in supersonic STOVL fighters. The objective was to design an aircraft that could replace most existing close air support-air combat fighters with a single aircraft that had some of the qualities of an air superiority fighter and the deployment flexibility of a VSTOL aircraft. The resulting E7-A concept was a delta-wing supersonic fighter that used a fuselage-mounted thrust augmenting ejector and a ventral deflecting jet nozzle for vertical lift. The Grumman Aircraft Company, the Navy, and NASA developed the Design-698 (D-698) subsonic tactical transport in response to the Navy's Type A VSTOL utility aircraft requirement. The objective was to develop a subsonic utility transport with the operational flexibility of a helicopter, but with greater speed and range. The D-698 employs two high-bypass turbofan engines mounted on a dumbbell that rotates through ninety degrees for vertical takeoff and cruise flight. Movable vanes positioned in the exhaust flow provide control in hover with the need for reaction control jets. The presentations concluding comments suggest that technology advances in the last thirty-years may justify the value of revisiting some of these concepts.

Powered Lift↗

Characterization of Metering, Merging and Spacing Requirements for Future Trajectory-Based Operations

Trajectory-Based Operations (TBO) is one of the essential paradigm shifts in the NextGen transformation of the National Airspace System. Under TBO, aircraft are managed by 4-dimensional trajectories, and airborne and ground-based metering, merging, and spacing operations are key to managing those trajectories. This paper presents the results of a study of potential metering, merging, and spacing operations within a future TBO environment. A number of operational scenarios for tactical and strategic uses of metering, merging, and spacing are described, and interdependencies between concurrent tactical and strategic operations are identified.

Johnson, Sally↗

Efficient Planning of Wind-Optimal Routes in North Atlantic Oceanic Airspace

The North Atlantic oceanic airspace (NAT) is crossed daily by more than a thousand flights, which are greatly affected by strong jet stream air currents. Several studies devoted to generating wind-optimal (WO) aircraft trajectories in the NAT demonstrated great efficiency of such an approach for individual flights. However, because of the large separation norms imposed in the NAT, previously proposed WO trajectories induce a large number of potential conflicts. Much work has been done on strategic conflict detection and resolution (CDR) in the NAT. The work presented here extends previous methods and attempts to take advantage of the NAT traffic structure to simplify the problem and improve the results of CDR. Four approaches are studied in this work: 1) subdividing the existing CDR problem into sub-problems of smaller sizes, which are easier to handle; 2) more efficient data reorganization within the considered time period; 3) problem localization, i.e. concentrating the resolution effort in the most conflicted regions; 4) applying CDR to the pre-tactical decision horizon (a couple of hours in advance). Obtained results show that these methods efficiently resolve potential conflicts at the strategic and pre-tactical levels by keeping the resulting trajectories close to the initial WO ones.

Rodionova, Olga↗

Impact of Different Trajectory Option Set Participation Levels within an Air Traffic Management Collaborative Trajectory Option Program

This paper presents the methodology and results of a Human-In-The-Loop (HITL) simulation study conducted in the Airspace Operations Laboratory at NASA Ames Research Center. This study is a part of NASA's ongoing research into developing an Integrated Demand Management (IDM) concept, whose aim is to improve traffic flow management (TFM) by coordinating the FAA's strategic Traffic Flow Management System (TFMS) with its more tactical Time-Based Flow Management (TBFM) system. The purpose of TFM is to regulate air traffic demand so that it is delivered efficiently through constrained airspace resources without exceeding their capacity limits. The IDM concept leverages a new TFMS capability called the Collaborative Trajectory Options Program (CTOP) to strategically pre-condition traffic demand flowing into a TBFM-managed arrival environment, where TBFM is responsible for managing traffic tactically by generating precise arrival schedules. Unlike other TFM tools, CTOP gives flight operators the option of submitting a set of user-preferred alternative trajectories for each flight. CTOP can then use these trajectory option sets (or TOSs) to find user-preferred alternative routes to reduce demand on an overloaded resource. CTOP's effectiveness in redistributing demand is limited, however, by the availability of flights with alternative routes. The research presented in this paper focuses on evaluating the impact on TFM operations by varying the percentage of flights that submit a multiple-option TOS ('TOS participation levels'). Results show the impact on overall system performance and on the rerouted flights themselves. The simulation used a Newark (EWR) airport arrival scenario, with en route weather affecting traffic inbound from the west. Participants were asked to control each of the three arrival flows (north, west, and south) to meet their individual capacity constraints while simultaneously ensuring efficient utilization of the capacity at the destination airport. A large, permeable convective weather cell located southeast of Chicago severely reduced the capacity of the west flow. The study evaluated the impact of five different TOS participation levels on CTOP's ability to re-allocate traffic from the west and improve TFM performance in terms of delay assignment and traffic delivery rate to the airport. Overall, the results showed that increasing TOS submissions allowed the overall system delays to be reduced and fairly distributed among the three arrival flows, at the same time achieving the airport throughput rate. Moreover, it was found that aircraft who submitted a TOS saw a greater reduction in delay, even when they were assigned longer routes. This was particularly true when fewer aircraft submitted a TOS. The results confirm that the CTOP operations with higher TOS participation levels helped utilize the overall National Airspace System (NAS) resources as well as benefited the users who participated.

Yoo, Hyo-Sang↗

Evolution of Electronic Approval Request Procedures at Charlotte Douglas International Airport

At many major U.S. airports, a departure approval request, or 'APREQ,' establishes a later runway departure time for a flight, allowing it to absorb tactical delay on the ground. APREQ times are traditionally coordinated by a process known as 'call-for-release' whereby an airport surface traffic manager calls an airspace traffic manager on the telephone. This research examines new electronic APREQ coordination enabled by the NASA Airspace Technology Demonstration-2 system and compares it to the call-for-release method of coordination. During the initial deployment period, electronic APREQ coordination was used for more than half of eligible flights. A majority of electronic requests were approved in less than one minute on average. Data suggest that both the average tactical delay and compliance with the electronically coordinated departure times did not differ significantly from departure times coordinated using call-for-release.

APREQ↗

Evolution of Electronic Approval Request Procedures at Charlotte Douglas International Airport

A departure approval request, or APREQ, establishes a later runway departure time for a flight, allowing it to absorb tactical delay on the ground. APREQ times are traditionally coordinated by a process known as "call-for-release" whereby an airport surface traffic manager calls an airspace traffic manager on the telephone. This research examines new electronic APREQ coordination enabled by the NASA Airspace Technology Demonstration-2 system and compares it to the traditional call-for-release method of coordination. During the initial deployment period, electronic APREQ coordination was used for more than half of eligible flights. A majority of electronic requests were approved in less than one minute on average. Both the average tactical delay and compliance with the electronically coordinated departure times did not differ significantly from departure times coordinated using call-for-release.

APREQ↗

Benefit Assessment of the Integrated Demand Management Concept for Multiple New York Metroplex Airports

Benefits of the Integrated Demand Management (IDM) concept were assessed utilizing a newly developed automated simulation capability called ‘Traffic Management Initiative Automated Simulation (TMIAutoSim).’ The IDM concept focuses on improving traffic flow management (TFM) by coordinating the FAA’s strategic Traffic Flow Management System (TFMS) with its more tactical Time-Based Flow Management (TBFM) system. The IDM concept leverages a new TFMS capability called Collaborative Trajectory Options Program (CTOP) to strategically pre-condition traffic demand flowing into a TBFM-managed arrival environment, where TBFM is responsible for tactically managing traffic by generating precise arrival schedules. The IDM concept was developed over a multi-year effort, focusing on solving New York metroplex airport arrival problems. TMIAutoSim closely mimics NASA’s high-fidelity simulation capabilities while enabling more data to be collected at higher speed. Using this new capability, the IDM concept was evaluated using realistic traffic across various weather scenarios. Six representative weather days were selected after clustering three months of historical data. For those selected six days, Newark Liberty International Airport (EWR) and LaGuardia Airport (LGA) arrival traffic scenarios were developed. For each selected day, the historical data were analyzed to accurately simulate actual operations and the weather impact of the day. The current day operations and the IDM concept operations were simulated for the same weather scenarios and the results were compared. The selected six days were categorized into two groups: ‘clear weather’ for days without Ground Delay Programs (GDP) and ‘convective weather’ for days with GDP and significant weather around New York metroplex airports. For the clear weather scenarios, IDM operations reduced last minute, unanticipated departure delays for short-haul flights within TBFM control boundaries with minimal to no impact on throughput and total delay. For the convective weather scenarios, IDM significantly reduced delays and increased throughput to the destination airports.

Traffic Management Initiative Automated Simulation↗

Strategic Surface Metering at Charlotte Douglas International Airport

NASA is conducting a field test of the Airspace Technology Demonstration2 (ATD-2) to evaluate an Integrated Arrival, Departure, and Surface (IADS) traffic management system. The IADS system was deployed to Charlotte Douglas International Airport (CLT) in 2017 for a three-year field evaluation. The Phase 1 field evaluation included tactical surface metering, which manages departure excess taxi time by tactically assigning gate holds. Phase 2 built upon the lessons learned from Phase 1 to extend surface metering into the strategic metering timeframes. In this paper, we describe the strategic metering capabilities of the ATD-2 IADS system and the operational results from CLT.

Airspace Technology Demonstration 2↗

Urban Air Mobility Airspace Dynamic Density

Airspace safety must be assured for Urban Air Mobility (UAM) to become reality. Emerging operations need to safely integrate with existing and future air traffic. UAM is anticipated to evolve in stages. Early stages, characterized by low-density operations, may be accommodated by traditional air traffic management approaches. However, to enable the scale of UAM operations necessary to reach ubiquitous integration into daily life, new paradigms that utilize collaborative and automated systems are being considered. Correspondingly, traditional approaches for determining a safe number of simultaneous operations in an airspace must be adapted to suit evolving traffic management paradigms. In this paper, we examine dynamic density as an approach to determine when an airspace is excessively populated, and safety may become compromised. We review previous work on dynamic density as it relates to air traffic controller workload and propose factors that may be more fitting for UAMs. Rather than considering controller workload, we propose factors that suggest increased likelihood of loss of separation and may lead to conflicts that require tactical avoidance maneuvers. In addition to monitoring dynamic density for tactical decision making, we endeavor to predict airspace dynamic density with adequate look-ahead to allow for strategic route selection.

UAM↗

Concept of Operations for OSIRIS-REx Optical Navigation Image Planning

Optical navigation (OpNav) is a critical subsystem of the OSIRIS-REx asteroid sample return mission, which operated in the vicinity of near-Earth asteroid (101955) Bennu from August 2018 through April 2021. A substantial amount of mission resources across multiple subsystems and institutions is required to ensure that the OpNav data are successfully acquired. The KinetX OpNav team, part of the Flight Dynamics System (FDS), is responsible for performing required analysis to develop the OpNav operations plans; requesting, reviewing and verifying the plans; and ultimately using the image data for critical navigation operations. The FDS team, responsible for the mission navigation, is operated by KinetX Aerospace with management and operations support from NASA’s Goddard Space Flight Center. The Science Processing and Operations Center (SPOC), located at the University of Arizona’s Lunar and Planetary Laboratory, is responsible for generating the planning products for all science and most OpNav data. These plans are integrated into the spacecraft sequences, tested, and commanded by the Mission Support Area (MSA) at Lockheed Martin Space. To ensure mission-critical navigation image data are successfully acquired, the plan is developed through a waterfall of planning cycles over the course of 3 months prior to onboard plan execution. During the initial strategic planning for a mission phase, detailed analysis is performed by the OpNav team to conceptualize the concept of operations (ConOps) for image data collection. This phase OpNav Narrative is included along with other strategic planning documents for the key ground segment stakeholders to review and provide feedback. The detailed OpNav plans get defined in the tactical planning cycle, which spans 8 to 3 weeks before the week-long integrated sequence is executed on-board the spacecraft. During the tactical cycle, the initial OpNav Request is submitted along with the science requests, kicking off development of the science and OpNav plans. Once the initial plan is drafted, interfaces are exercised so that the plan can be reviewed and iterated, if necessary. A rigorous schedule is followed by the planning teams during the implementation cycle, spanning the last 18 days before uplink, to ensure all the necessary integration, testing, and reviewing can occur on time. The development of the OpNav planning ConOps, including responsibilities, interfaces, timelines, and procedures, took extensive collaboration across mission elements and institutions. The process was robust throughout the 137 weeks of continuous Optical Navigation Operations at Bennu, which concluded on April 9th, 2021.

Coralie D. Adam↗

Monitoring Airspace Complexity and Determining Contributing Factors

The national airspace has evolved over many years to accommodate increased traffic demand [1] while simultaneously maintaining one of the safest forms of transportation [2], [3]. One of the reasons for this success is the ability of the system and the operators to adapt and accommodate to situations that routinely disrupt optimal operations. These situations may include: adverse weather, delays, early arrivals, equipment outages, and other factors that are outside the operators ability to control. These factors can lead to states where automation is unable to properly handle these issues and therefore air traffic controllers and pilots have to intervene, ultimately increasing communication between operators resulting in higher workload. As controller workload increases to handle sub-optimal operating conditions this can be viewed as an increase in complexity. The reasoning for this is because humans are now required to make tactical decisions in response to external factors, resulting in a departure from the strategic plan where operations would be more efficiently managed. Human operators control airspace complexity under rigid regulations that are constantly changing. The airspace is divided into sectors and the number of aircraft assigned to each controller is limited for safe handling. There has been past work that devised airspace complexity metrics in commercial aviation and related these metrics to controller workload (e.g., [4],[5]). The upper bounds on the system load are pre-determined. Such bounds on complexity make for a safe system, but the system cannot scale and adapt to autonomous, dense, and heterogeneous traffic, including the many types of Unmanned Aerial Vehicles (UAVs) envisioned to be added to the operations. We hypothesize that, as traffic density and heterogeneity grow, and other key metrics change, there will be phase transitions at which the way traffic should be managed changes significantly [6]. We offer a method for in-time detection of contributing factors that lead to phase transitions, characterized by increased complexity. To the best of our knowledge, there is no tool similar to our proposed effort that identifies such contributing factors or precursor patterns. To define the scope we are proposing to measure complexity from the viewpoint of the Terminal Radar Approach Control Facilities (TRACON) controller’s perspective. In particular we are analyzing arrivals into KSFO. With safety as the top concern for airspace operators, it is important to recognize that as density and heterogeneity grow, the focus of the system will change. Times of the day when the airspace has low density and heterogeneity, the flights will follow more efficient paths where the aircraft move on established routes that are more or less directly to the destination. However, when density and heterogeneity increases, the system will begin changing focus to avoiding conflicts and collisions and route the flights in a more flexible way. Higher flexibility requires more communication and coordination between controllers and pilots which the current automation is unable to handle. This paper proposes a novel approach that monitors airspace complexity at multiple scales, uses a Machine Learning-based tool that predicts when operations will transition to a regime of greater complexity, and identifies actions that can reduce the complexity while still maintaining efficient and safe operations. We demonstrate our proposed approach using data from multiple complementary sources. This includes, but is not limited to: historical aircraft surveillance data from NASA’s Sherlock Data Warehouse [7], METAR weather data, and airport configuration data from Aviation System Performance Metrics (ASPM). The surveillance data flight paths are sampled at a variable sample rate — increasing as the aircraft approaches the airport. This is due to how Sherlock manages flight track stitching between different radar facilities which have different sampling rates. The weather and performance data are logged at defined intervals throughout the day at a courser refresh rate. In addition to the logged data and metrics, we leverage pre-defined Standard Terminal Arrival Routes (STARs) procedures to characterize the path of each flight. Each flight files for one of these routes in the flight plan well before entering the terminal airspace, and approximately follows the route until it leaves the STAR, typically on the final fix of a runway transition. However, most flights do not always fly the full STAR procedure to completion [8], but the majority do adhere to the fixes within the common route of the procedure. Our approach leverages fixes in the common route of each of the STARs to build a reference path to the airport. This allows us to characterize the flight paths in what we are defining as the “maneuvering area” (the airspace between the STAR and before the flight is lined up on the runway’s final approach) to determine how off nominal the flights are to calculate its complexity score. Determining airspace complexity is a concept that does not have a concrete answer. In designing this metric, we consider what increases the workload for the air traffic controllers. Consequently more specialized vectoring maneuvers results in higher workload. Accordingly, we start with a theory: each flight has a direct path it takes from the STAR’s common route to the final approach’s outer marker fix for the flight’s landing runway. It is important to note that the direct path is only used as a reference. If the majority of the flights have a large consistent offset as compared to other routes it does not necessarily mean that those flights have higher complexity. We are merely building a distribution based on this direct path for that particular STAR and runway pair to determine the normal mode of operations for that route. Flights that are in the upper tail of these distributions will result in higher complexity scores and flights that fly in the median will represent the normal mode of operations and therefore will have lower complexity scores. Since flights following each STAR route take different paths to the airport, we have a different distribution for each STAR route and therefore can model these distributions to compute a complexity score from their respective normalized distributions. To evaluate the effectiveness of our proposed airspace complexity metric we will compare against an established approach based on trajectory clustering [9]. This unsupervised learning technique consists of the following steps: (1) identify the general maneuvering areas (waypoints) by performing $\kappa$-means or DBSCAN clustering on locations where aircraft frequently turn based on the surveillance radar track data, (2) map flight trajectories onto sequences of waypoints, and (3) cluster the sequences based on their common subsequences. From a high-level perspective, this baseline model learns nominal operations in the airspace through the sequence of waypoints that are representative of where aircraft change direction and defines deviations from the nominal operations as “complex.” Therefore, more deviations from the nominal operations correspond to higher complexity values. For our validation, we re-implemented this technique and tune model hyper-parameters to correctly detect waypoints for the arrival traffic into the San Francisco bay area. We will compute the complexity measure over a one-year period using our proposed technique as well as the baseline. Our validation will be based on each technique’s ability to detect a set of undesirable outcomes (e.g., go-arounds, holding patterns, average time in the airspace, etc.). Since our current complexity metric is derived from the offset from the direct reference path, it’s important to understand what causes these offsets. In many of the flights with high offset distance, flights performing holding patterns and S turns can be observed. These maneuvering tactics are utilized to add distance between the aircraft and the destination runway to prevent multiple flights from having conflicting arrival times. In order to predict a rise in complexity (or the precursor to complexity), it’s necessary to be able to identify these potential conflicts (which in turn, result in higher offsets). To do this, we define a “representative flight” for each STAR route and runway pair. This flight is approximately the path the flight would take if there was a clear path with no other flights in the airspace — including the time remaining to the airport. We first identify the flights for a given STAR runway pair using the offset to the reference path distributions that fall between the 44-55 percentiles. This yields the flights that conform to the most normal mode of operation. Each of these flights is partitioned based on the percent complete from the entry point into the maneuvering areas from 0\% – 100\% complete. Then for each percent “bin”, we take the median value of the flight’s latitude/longitude coordinates, airspeed, and (non causal) time remaining to the airport to construct a lookup table for each percent complete bin on a given route. As a flight enters the maneuvering area, we can find the estimated arrival time of a flight to the airport by finding the closest point to the representative path’s percent complete bin (relative to the flight’s current position at any snapshot in the airspace) and therefore retrieve the corresponding remaining time left on the “representative path”. We assume that the flight will follow the representative path to completion when deriving these estimates. We can then compare these estimated arrival times against other flights for the same snapshot in time to identify potential conflicts. If more flights are estimated to arrive within a tolerance window than there are runways available, then we have a potential conflict. We can use this derived measure along with other factors expected to add disruption to the operation such as weather and runway configuration changes as an input to machine learning tools to detect precursors that increases in our complexity measure. This novel method will assist in uncovering insights into the contributing factors that lead to increased complexity that may allow for in-time responses to avoid reaching a high complexity state in the airspace.

complexity↗

Testing Mars Exploration Rover-Inspired Operational Strategies for Semi-Autonomous Rovers on the Moon Ii: the GeoHeuristic Operational Strategies Test in Alaska

We used MER-derived semi-autonomous rover science operations strategies to determine best practices suitable for remote semi-autonomous lunar rover geology. Two field teams studied two glacial moraines as analogs for potential ice-bearing lunar regolith. At each site a Rover Team commanded a human rover to execute observations based on common MER sequences; the resulting data were used to identify and characterize targets of interest. A Tiger Team followed the Rover Team using traditional terrestrial field methods, and the results of the two teams were compared. Narrowly defined goals that can be addressed using cm-scale or coarser resolution may be met sufficiently by the operational strategies adapted from MER survey mode. When reconnaissance is the primary goal, the strategies tested are necessary but not sufficient. Further, there may be a set of optimal observations for such narrowly defined, hypothesis-driven science goals, such that collecting further data would result in diminishing returns. We confirm results of previous tests that indicated systematic observations might improve efficiency during strategic planning, and improve science output during data analysis. This strategy does not markedly improve the rate at which a science team can ingest data to feed back into tactical decision-making. Other methods should be tested to separate the strategic and tactical processes, and to build in time for data analysis.

MER↗

New Rover Conops with High-Performance Onboard Computing: Give Up Raw Data to Reduce Ops Cost and Do More Science

A major portion of time during the tactical operation of Mars rovers is spent for selecting, prioritizing, and coordinating sciences and engineering activities such that they fit within resource constraints, including the downlink data volume, energy, and time. In particular, the downlink data volume constraint is getting particularly tighter in recent missions because modern instruments produce increasingly high data volume while the communication bandwidth is essentially bounded by the law of physics. Tactical operation would be substantially simplified, hence the operation cost could be reduced, if the data volume constraint is relaxed or even removed. In this abstract, we propose a new operation paradigm for achieving this goal. The key observation is that, both in science and engineering applications, the bit size of raw data is typically much greater than the volume of processed information that is needed for scientific or engineering analysis. For example, a full-resolution image from Mastcam-Z, the main science camera on Perseverance, is about 700 kB in volume and we downlinked 29,685 images up to Sol 243, totaling ~20 GB of data. But of course, scientists do not use every pixel of these images; what they really look for in the images are geological features, typically represented by specific geometric configurations or textures. An end product after processing hundreds of Mascam-Z images could be a single geological map summarizing the spatial distribution of the features. For another example, a 100-meter drive of Perseverance produces 7-12 MB of drive telemetry, which records every detail of the rover's motion at 8 Hz, including position, attitude, steering angles, encoder readings, motor currents and many other information. But what the ground engineers eventually pay attention to is the signs of anomaly, such as excessive motor currents or high slip; if a drive is nominal, the vast majority of this data is unused. What if, then, we process the raw data onboard and only downlink the processed data that is relevant to scientific or engineering analyses, such as a list of detected science features (with cropped images) or a list of potential signs of anomaly while driving? A major roadblock for such onboard, high-level information processing has been the onboard computational resource. RAD750, the main onboard computer of Perseverance, is obviously not sufficient for performing complex image or signal processing such as object detection, semantic segmentation, or anomaly detection. Interestingly, RAD750 is not the best processor that Perseverance has; Qualcomm's Snapdragon 801, a modern mobile processor, is on her Heli Base Station, a device for communicating with Mars Helicopter Ingenuity; also, Intel's Atom E3845 processors are on engineering cameras. In the reminder of this paper, we will introduce two particular uses cases of these high-performance co-processors (meaning auxiliary CPU, GPU, or other types of processors that are separate from the main processor that runs the main flight software) for lowering operation cost and accommodating more science activities for a given communication constraint.

Didier, A.↗

A Human-In-The-Loop Simulation for Urban Air Mobility in the Terminal Area

In this paper researchers propose a human-in-the-loop experiment to study human performance when tasked with tactical deconfliction in terminal area air taxi operations. The air taxi operations being considered herein are an advanced air transportation concept called Urban Air Mobility (UAM). The UAM concept aims to support not only air taxi operations, but also package delivery and emergency response among other use cases. The key innovation over current air transportation lies with the introduction of highly automated aircraft and air traffic management systems. Development of the UAM system will include transitional midterm phases where some operational services will be provided by a mixture of automation and human actors. Midterm operations present a unique challenge, since the scope of responsibility of automated systems is largely undefined, suggesting the need for direct human participation with little to inform how much human intervention is necessary. Here it is assumed that traffic management responsibilities require coordination between human actors and automated systems and focus on arrival flows for midterm operations. In the proposed human-in-the-loop simulation, virtual UAM traffic is strategically deconflicted by a Provider of Services for UAM at departure, then tactically managed by a human at the arrival facility. Generated traffic consists of UAM participants flying in UAM exclusive airspace structures, thus isolated from traditional traffic. The human operator is tasked with managing spacing of arrival traffic and executing speed adjustments as deemed necessary. Researchers propose the investigation of three levels of automation assistance: 1) no assistance; 2) spacing violation detection; 3) spacing violation detection and speed adjustment recommendations. Quantitative measures like throughput and delay are used to assess the human's capacity for accommodating airborne delays. Qualitative evaluations such as surveys and open-ended feedback are used to gain insight into human factors. These factors could introduce additional capacity constraints on traffic, independent of physical or technical constraints. Although findings for this study will not be reported as the study has not yet been executed, the authors conclude with potential outcomes informed by previous simulations in the literature and suggestions for the structure and procedures of midterm human-automation air traffic management.

UAM↗

A Human-In-The-Loop Simulation for Urban Air Mobility in the Terminal Area

In this presentation we propose a human-in-the-loop experiment to study the potential impact of human engagement in tactical mitigation of delay in terminal area air taxi operations. The air taxi operations being considered herein is an advanced air transportation concept called Urban Air Mobility (UAM). The UAM concept aims to support not only air taxi operations, but also package delivery and emergency response among other use cases. The key innovation over current air transportation lies with the introduction of autonomous aircraft and autonomous air traffic management systems. Development of the UAM system will include transitional midterm phases where some operational services will be provided by a mixture of automation and human actors. Midterm operations present a unique challenge, since the scope of responsibility of automated systems is largely undefined, suggesting the need for direct human participation with little to inform how much human intervention is necessary. Here we assume that traffic management responsibilities require coordination between human actors and automated systems and focus on arrival flows for midterm operations. In the proposed human-in-the-loop simulation, virtual UAM traffic is strategically deconflicted by a Provider of Services for UAM at departure, then tactically managed by a human at the arrival facility. Generated traffic consists of UAM participants flying in UAM exclusive airspace structures, thus isolated from traditional traffic. The human operator is tasked with managing spacing of arrival traffic and executing speed adjustments as deemed necessary. We propose the investigation of three levels of automation assistance: 1) no assistance; 2) spacing violation detection; 3) spacing violation detection and speed adjustment recommendations. Quantitative measures like throughput and delay are used to assess the human's capacity for accommodating airborne delays. Qualitative evaluations such as surveys and open-ended feedback are used to gain insight into human factors. These factors could introduce additional capacity constraints on traffic, independent of physical or technical constraints. Although findings for this study will not be reported as the study has not yet been executed, we conclude with potential outcomes informed by previous simulations in the literature and suggestions for the structure and procedures of midterm human-automation air traffic management.

UAM↗

A Comparison of Declarative and Hybrid Declarative-Procedural Models for Rover Operations

The MAPGEN [2] (Mixed-initiative Activity Plan GENerator) planning system is a great example of a hybrid procedural/declarative system where the advantages of each are leveraged to produce an effective planner/scheduler for Mars Exploration Rover tactical planning. We explore the adaptation of the same domain to an entirely declarative planning system (ASPEN [4] Activity Scheduling and Planning ENvironment), and demonstrate that, with some translation, much of the procedural knowledge encoding is amenable to a declarative knowledge encoding.

declarative domain representations↗

Charlotte - EDC Evaluation and Demonstration (CEED) Human-in-the-Loop Results Briefing to ATD-2 FAA Partners

The Charlotte EDC Evaluation and Demonstration (CEED) was the first Human-In-The-Loop experiment under the Air Traffic Management Technology Demonstration-2 (ATD-2) project. The purpose of the study was fourfold: 1) to establish a simulation environment (Charlotte) for airspace operations for ATD-2 technology, 2) to simulate current-day departures and arrival operations, 3) to assess the impact of current Traffic Management Initiatives (TMI) on Charlotte (CLT) departure flows and en route operations in Washington (ZDC) and Atlanta Centers (ZTL), and 4) to assess the impact of departure takeoff time compliance on airspace operations. The experimental design compared 3 TMIs and 2 compliance levels. Fourteen FAA retired controllers participated in the simulation. In addition, two Traffic Management Coordinators from ZTL and ZDC managed traffic flows. Surface and airborne delays, control efficiency, throughput, realism, workload, and acceptability were assessed and will be compared across the experimental conditions. Participants rated the simulation as very realistic. Results indicate that different TMIs have different impacts on surface and airspace delay. Departure compliance indicates partial benefits to sector complexity and controller workload. This simulation will provide an initial assessment of the tactical scheduling problems that the ATD-2 technology will address in the near term.

airspace technology demonstration 2↗

Comparison of Taxi Time Prediction Performance Using Different Taxi Speed Decision Trees

In the STBO modeler and tactical surface scheduler for ATD-2 project, taxi speed decision trees are used to calculate the unimpeded taxi times of flights taxiing on the airport surface. The initial taxi speed values in these decision trees did not show good prediction accuracy of taxi times. Using the more recent, reliable surveillance data, new taxi speed values in ramp area and movement area were computed. Before integrating these values into the STBO system, we performed test runs using live data from Charlotte airport, with different taxi speed settings: 1) initial taxi speed values and 2) new ones. Taxi time prediction performance was evaluated by comparing various metrics. The results show that the new taxi speed decision trees can calculate the unimpeded taxi-out times more accurately.

taxi time prediction↗