Engineering topics

Conrad Gabriel

Publications and source records attributed to Conrad Gabriel.

3 records

NASA NTRSDate not supplied

Demonstrating the Early Adopter Benefits of Submitting Multiple Trajectory Options for Airlines

Integrated Demand Management (IDM), is a NASA developed Traffic Flow Management (TFM) concept that uses Collaborative Trajectory Options Program (CTOP) to precondition traffic flows into the Time Based Flow Management (TBFM) region, helping traffic planners manage imbalances between demand and capacity in the National Airspace (NAS). A workshop held at NASA was conducted to demonstrate how individual airlines can be impacted by using Trajectory Options Sets (TOS) during IDM operations. A primary concern that was specifically addressed in a part-task Human-in-the-Loop simulation was who received the greater benefit, TOS participating or non-TOS participating airlines? The results showed that TOS participating airlines received greater benefit in terms of ground delay, number of reroute options, and additional flight time, than non-TOS participating airlines. However, this result was dependent on the number and location of flights. Therefore, it was advantageous for airlines to equip TOS. In addition, we found that non-TOS participating airlines also benefitted from other airlines participating in TOS, because the total system-wide ground delay was reduced as more TOS were introduced into the system. The evidence suggests that the benefits were distributed fairly, and there were no unfair disadvantages for airlines who did not equip TOS.

Integrated Demand Management↗

NASA NTRSDate not supplied

Demonstration of Airline-Based Airborne Reroute Operations using Trajectory Option Sets and Third-Party Tools

A concept that enables advanced airborne reroute operations is proposed, built on NextGen capabilities called Airborne Reroute (ABRR) and Trajectory Option Set (TOS). The concept introduces new third-party services / tools for the airline dispatchers to generate airline-preferred trajectories in response to convective weather events. The airborne TOS routes are sent to the traffic flow managers, who can evaluate the feasibility of the trajectory options with the help of their own third-party services / tools which have been built for this concept. A virtual demonstration study was conducted to elicit feedback from air traffic and airline subject-matter-experts. The feedback was generally positive, both in the benefits of the concept and the feasibility / need for the new tools to enable the concept but their feedback was mixed on the feasibility of the new tools to be third-party services instead of being integrated into their core tools. Nevertheless, this concept explores and demonstrates an evolutionary pathway toward a service-oriented future that shifts the responsibilities and the capabilities of air traffic operations from the air traffic service providers to the airline industry and third-party vendors.

airborne reroutes↗

NASA NTRSDate not supplied

Identifying Common Coordination Procedures across Extensible Traffic Management (xTM) to Integrate xTM Operations into the National Airspace System

New categories of missions and vehicle types, such as drone delivery services, on-demand air taxi, and high-altitude long-endurance (HALE) vehicles are being proposed to operate using a novel, highly automated information exchange infrastructure and a community-based, cooperative traffic management concept. Collectively, these new operations are called Extensible Traffic Management (xTM). As these xTM vehicles become more prevalent, their operations will increasingly overlap with existing conventional aircraft and with each other. In order to seamlessly co-exist with current conventional aircraft operations, new coordination procedures, tools and services will be needed to integrate xTM into the future National Airspace System (NAS). In our prior work, we have identified a set of use cases for xTM interactions with air traffic control (ATC), categorized across different xTM operations based on trigger events. Events consisted of ones such as nominal xTM vehicle transition into the ATC environment or an off-nominal emergency landing situation. In this paper, we have extended the prior work to identify commonalities in the coordination procedures across xTM, as well as differences that are specific to the individual xTM operations. The overall results showed that two types of xTM-ATC interactions were prevalent: 1) xTM vehicles transitioning between xTM and ATC operational environments; 2) xTM vehicles being allowed to continue xTM operations in areas that are normally controlled by ATC. The results also suggested that emergency and rare off-nominal events may need specialized procedures for each vehicle type. The overall results suggest that there is a pathway to define a common method of handling and integrating diverse xTM operations in the future NAS, but there need to be procedures for individualized handling of xTM vehicles in infrequent, safety-critical events.

Extensible Traffic Management (xTM)↗