Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Trajectory Based Operations”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

An Examination of Selected Datacom Options for the Near-Term Implementation of Trajectory Based Operations

A primary feature of the Next Generation Air Transportation System (NextGen) is trajectory based operations (TBO). Under TBO, aircraft flight plans are known to computer systems on the ground that aid in scheduling and separation. The Future Air Navigation System (FANS) was developed to support TBO, but relatively few aircraft in the US are FANSequipped. Thus, any near-term implementation must provide TBO procedures for non-FANS aircraft. Previous research has explored controller clearances, but any implementation must also provide procedures for aircraft requests. The work presented here aims to surface issues surrounding TBO communication procedures for non-FANS aircraft and for aircraft requesting deviations around weather. Three types of communication were explored: Voice, FANS, and ACARS,(Aircraft Communications Addressing and Reporting System). ACARS and FANS are datacom systems that differ in that FANS allows uplinked flight plans to be loaded into the Flight Management System (FMS), while ACARS delivers flight plans as text that must be entered manually via the Control Display Unit (CDU). Sixteen pilots (eight two-person flight decks) and four controllers participated in 32 20-minute scenarios that required the flight decks to navigate through convective weather as they approached their top of descents (TODs). Findings: The rate of non-conformance was higher than anticipated, with aircraft off path more than 20% of the time. Controllers did not differentiate between the ACARS and FANS datacom, and were mixed in their preference for Voice vs. datacom (ACARS and FANS). Pilots uniformly preferred Voice to datacom, particularly ACARS. Much of their dislike appears to result from the slow response times in the datacom conditions. As a result, participants frequently resorted to voice communication. These results imply that, before implementing TBO in environments where pilots make weather deviation requests, further research is needed to develop communication procedures that integrate voice and datacom.

trajectory based operations↗
NASA NTRS2012

Challenges in Achieving Trajectory-Based Operations

In the past few years much of the global ATM research community has proposed advanced systems based on Trajectory-Based Operations (TBO). The concept of TBO uses four-dimensional aircraft trajectories as the base information for managing safety and capacity. Both the US and European advanced ATM programs call for the sharing of trajectory data across different decision support tools for successful operations. However, the actual integration of TBO systems presents many challenges. Trajectory predictors are built to meet the specific needs of a particular system and are not always compatible with others. Two case studies are presented which examine the challenges of introducing a new concept into two legacy systems in regards to their trajectory prediction software. The first case describes the issues with integrating a new decision support tool with a legacy operational system which overlap in domain space. These tools perform similar functions but are driven by different requirements. The difference in the resulting trajectories can lead to conflicting advisories. The second case looks at integrating this same new tool with a legacy system originally developed as an integrated system, but diverged many years ago. Both cases illustrate how the lack of common architecture concepts for the trajectory predictors added cost and complexity to the integration efforts.

Cate, Karen Tung↗
NASA NTRS2017

Towards Designing Graceful Degradation into Trajectory Based Operations: A Human-Systems Integration Approach

One of the most fundamental changes to the air traffic management system in NextGen is the concept of trajectory based operations (TBO). With the introduction of such change, system safety and resilience is a critical concern, in particular, the ability of systems to gracefully degrade. In order to design graceful degradation into a TBO envrionment, knowledge of the potential causes of degradation, and appropriate solutions, is required. In addition, previous research has predominantly explored the technological contribution to graceful degradation, frequently neglecting to consider the role of the human operator, specifically, air traffic controllers (ATCOs). This is out of step with real-world operations, and potentially limits an ecologically valid understanding of achieving graceful degradation in an air traffic control (ATC) environment. The following literature review aims to identify and summarize the literature to date on the potential causes of degradation in ATC and the solutions that may be applied within a TBO context, with a specific focus on the contribution of the air traffic controller. A framework of graceful degradation, developed from the literature, is presented. It is argued that in order to achieve graceful degradation within TBO, a human-system integration approach must be applied.

human-system integration↗
NASA NTRS2017

Towards Designing Graceful Degradation into Trajectory Based Operations: A Human-Machine System Integration Approach

One of the most fundamental changes to the air traffic management system in NextGen is the concept of trajectory based operations (TBO). With the introduction of such change, system safety and resilience is a critical concern, in particular, the ability of systems to gracefully degrade. In order to design graceful degradation into a TBO envrionment, knowledge of the potential causes of degradation, and appropriate solutions, is required. In addition, previous research has predominantly explored the technological contribution to graceful degradation, frequently neglecting to consider the role of the human operator, specifically, air traffic controllers (ATCOs). This is out of step with real-world operations, and potentially limits an ecologically valid understanding of achieving graceful degradation in an air traffic control (ATC) environment. The following literature review aims to identify and summarize the literature to date on the potential causes of degradation in ATC and the solutions that may be applied within a TBO context, with a specific focus on the contribution of the air traffic controller. A framework of graceful degradation, developed from the literature, is presented. It is argued that in order to achieve graceful degradation within TBO, a human-system integration approach must be applied.

trajectory based operations↗
NASA NTRS2017

Towards Designing Graceful Degradation into Trajectory Based Operations: A Human-Machine System Integration Approach

One of the most fundamental changes to the air traffic management system in NextGen is the concept of trajectory based operations (TBO). With the introduction of such change, system safety and resilience is a critical concern, in particular, the ability of systems to gracefully degrade. In order to design graceful degradation into a TBO envrionment, knowledge of the potential causes of degradation, and appropriate solutions, is required. In addition, previous research has predominantly explored the technological contribution to graceful degradation, frequently neglecting to consider the role of the human operator, specifically, air traffic controllers (ATCOs). This is out of step with real-world operations, and potentially limits an ecologically valid understanding of achieving graceful degradation in an air traffic control (ATC) environment. The following literature review aims to identify and summarize the literature to date on the potential causes of degradation in ATC and the solutions that may be applied within a TBO context, with a specific focus on the contribution of the air traffic controller. A framework of graceful degradation, developed from the literature, is presented. It is argued that in order to achieve graceful degradation within TBO, a human-system integration approach must be applied.

human-system integration↗
NASA NTRS2017

Flight Deck Surface Trajectory-Based Operations (STBO): A Four-Dimensional Trajectory (4DT) Simulation

Within human factors there is burgeoning interest in the Human-Autonomy Teaming (HAT) concept as away to address the challenges of interacting with complex, increasingly autonomous systems. The HAT concept comes out of an aspiration to interact with increasingly autonomous automation as a team member, rather than simply use automation as a tool. The authors, and others, have proposed core tenets for HAT that include bi-directional communication, automation and system transparency, and advanced coordination between human and automated teammates via predefined, dynamic task sequences known as plays (Shively et al., 2017). It is believed that, with proper implementation, HAT should foster appropriate teamwork, thus increasing trust and reliance on the system, which in turn will reduce workload, increase situation awareness, and improve performance. To this end, HAT has been demonstrated and/or studied in multiple applications including search and rescue operations (Nourbakhsh et al., 2005), healthcare and medicine (Tsui Yanco, 2007), autonomous vehicles (Parasuraman, Barnes, Cosenzo, Mulgund, 2007), photography (Lachter, Brandt, Sadler, Shively, in press), and aviation (Shively et al., in press). The current paper presents one such effort to apply HAT. It details the design of a R-HAT Agent developed as part of a NASA Research Agreement awarded to Human-Autonomy Teaming Solutions Inc. (HATS Inc), and developed in collaboration with the Human-Autonomy Teaming Laboratory at NASA Ames Research Center. The role of this Agent is to mediate interaction between the automation and the human operator of an advanced ground dispatch station, with this mediation based upon previously mentioned core tenets for HAT and the many lessons learned from the HAT research literature. This dispatch station was developed to support a NASA project investigating a concept called Reduced Crew Operations (RCO; Lachter, Brandt, Battiste, Matessa, Johnson, in press). Part of the RCO concept involves a ground operator providing enhanced support to a large number of aircraft with a single pilot on the flight deck. When assisted by the Agent, operators can monitor and support or manage a large number of aircraft and use plays to respond in real-time to complicated, workload-intensive events (e.g., an airport closure). A play is a plan that encapsulates goals, tasks, and a task allocation strategy appropriate for a particular situation. In the current implementation, when a play is initiated by a user, the Agent determines what tasks need to be done and has the ability to autonomously execute them (e.g., determining diversion options and uplinking new routes to aircraft) when it is safe and appropriate. The R-HAT Agent has been designed to both support end users and research in RCO and HAT. Additionally, the Agent and its underlying architecture were developed with generalizability in mind as a modular piece of software applicable outside of RCO aviation in domains such as those mentioned above. This paper will also discuss future further development and testing of the R-HAT Agent.

Bakowski, Deborah L.↗
NASA NTRS2020

Surface Trajectory-Based Operations (STBO) Client User Manual

This document serves as a user manual for the ATD-2 Surface Trajectory-Based Operations (STBO) Client (version 5.11) utilized by Air Traffic Control in the Tower. It describes the elements of the STBO Client interface and provides step-by-step instructions for using the tool. STBO Client functionality includes the display of live flight information, management of traffic restrictions, and prediction of expected traffic demand. The STBO Client is a component of the NASA Airspace Technology Demonstration 2 (ATD‑2) sub-project.

Louise Kay Morgan Ruszkowski↗
NASA NTRS2013

Flight Deck Surface Trajectory-based Operations (STBO): Results of Piloted Simulations and Implications for Concepts of Operation (ConOps)

The results offour piloted medium-fidelity simulations investigating flight deck surface trajectory-based operations (STBO) will be reviewed. In these flight deck STBO simulations, commercial transport pilots were given taxi clearances with time and/or speed components and required to taxi to the departing runway or an intermediate traffic intersection. Under a variety of concept of operations (ConOps) and flight deck information conditions, pilots' ability to taxi in compliance with the required time of arrival (RTA) at the designated airport location was measured. ConOps and flight deck information conditions explored included: Availability of taxi clearance speed and elapsed time information; Intermediate RTAs at intermediate time constraint points (e.g., intersection traffic flow points); STBO taxi clearances via ATC voice speed commands or datal ink; and, Availability of flight deck display algorithms to reduce STBO RTA error. Flight Deck Implications. Pilot RTA conformance for STBO clearances, in the form of ATC taxi clearances with associated speed requirements, was found to be relatively poor, unless the pilot is required to follow a precise speed and acceleration/deceleration profile. However, following such a precise speed profile results in inordinate head-down tracking of current ground speed, leading to potentially unsafe operations. Mitigating these results, and providing good taxi RTA performance without the associated safety issues, is a flight deck avionics or electronic flight bag (EFB) solution. Such a solution enables pilots to meet the taxi route RTA without moment-by-moment tracking of ground speed. An avionics or EFB "error-nulling" algorithm allows the pilot to view the STBO information when the pilot determines it is necessary and when workload alloys, thus enabling the pilot to spread his/her attention appropriately and strategically on aircraft separation airport navigation, and the many other flight deck tasks concurrently required. Surface Traffic Management (STM) System Implications. The data indicate a number of implications regarding specific parameters for ATC/STM algorithm development. Pilots have a tendency to arrive at RTA points early with slow required speeds, on time for moderate speeds, and late with faster required speeds. This implies that ATC/STM algorithms should operate with middle-range speeds, similar to that of non-STBO taxi performance. Route length has a related effect: Long taxi routes increase the earliness with slow speeds and the lateness with faster speeds. This is likely due to the" open-loop" nature of the task in which the speed error compounds over a longer time with longer routes. Results showed that this may be mitigated by imposing a small number oftime constraint points each with their own RTAs effectively tuming a long route into a series of shorter routes - and thus improving RTA performance. STBO ConOps Implications. Most important is the impact that these data have for NextGen STM system ConOps development. The results of these experiments imply that it is not reasonable to expect pilots to taxi under a "Full STBO" ConOps in which pilots are expected to be at a predictable (x,y) airport location for every time (t). An STBO ConOps with a small number of intermediate time constraint points and the departing runway, however, is feasible, but only with flight deck equipage enabling the use of a display similar to the "error-nulling algorithm/display" tested.

Foyle, David C.↗
NASA NTRS2012

DataComm in Flight Deck Surface Trajectory-Based Operations

The purpose of this pilot-in-the-loop aircraft taxi simulation was to evaluate a NextGen concept for surface trajectory-based operations (STBO) in which air traffic control (ATC) issued taxi clearances with a required time of arrival (RTA) by Data Communications (DataComm). Flight deck avionics, driven by an error-nulling algorithm, displayed the speed needed to meet the RTA. To ensure robustness of the algorithm, the ability of 10 two-pilot crews to meet the RTA was tested in nine experimental trials representing a range of realistic conditions including a taxi route change, an RTA change, a departure clearance change, and a crossing traffic hold scenario. In some trials, these DataComm taxi clearances or clearance modifications were accompanied by preview information, in which the airport map display showed a preview of the proposed route changes, including the necessary speed to meet the RTA. Overall, the results of this study show that with the aid of the RTA speed algorithm, pilots were able to meet their RTAs with very little time error in all of the robustness-testing scenarios. Results indicated that when taxi clearance changes were issued by DataComm only, pilots required longer notification distances than with voice communication. However, when the DataComm was accompanied by graphical preview, the notification distance required by pilots was equivalent to that for voice.

Bakowski, Deborah L.↗
NASA NTRS2013

NextGen Flight Deck Surface Trajectory-Based Operations (STBO): Contingency Holds

The purpose of this pilot-in-the-loop taxi simulation was to investigate a NextGen Surface Trajectory-Based Operations (STBO) concept called "contingency holds." The contingency-hold concept parses a taxi route into segments, allowing an air traffic control (ATC) surface traffic management (STM) system to hold an aircraft when necessary for safety. Under nominal conditions, if the intersection or active runway crossing is clear, the hold is removed, allowing the aircraft to continue taxiing without slowing, thus improving taxi efficiency, while minimizing the excessive brake use, fuel burn, and emissions associated with stop-and-go taxi. However, when a potential traffic conflict exists, the hold remains in place as a fail-safe mechanism. In this departure operations simulation, the taxi clearance included a required time of arrival (RTA) to a specified intersection. The flight deck was equipped with speed-guidance avionics to aid the pilot in safely meeting the RTA. On two trials, the contingency hold was not released, and pilots were required to stop. On two trials the contingency hold was released 15 sec prior to the RTA, and on two trials the contingency hold was released 30 sec prior to the RTA. When the hold remained in place, all pilots complied with the hold. Results also showed that when the hold was released at 15-sec or 30-sec prior to the RTA, the 30-sec release allowed pilots to maintain nominal taxi speed, thus supporting continuous traffic flow; whereas, the 15-sec release did not. The contingency-hold concept, with at least a 30-sec release, allows pilots to improve taxiing efficiency by reducing braking, slowing, and stopping, but still maintains safety in that no pilots "busted" the clearance holds. Overall, the evidence suggests that the contingency-hold concept is a viable concept for optimizing efficiency while maintaining safety.

NextGen↗
NASA NTRS2012

DataComm in Flight Deck Surface Trajectory-Based Operations

The purpose of this pilot-in-the-loop aircraft taxi simulation was to evaluate a NextGen concept for surface trajectory-based operations (STBO) in which air traffic control (ATC) issued taxi clearances with a required time of arrival (RTA) by Data Communications (DataComm). Flight deck avionics, driven by an error-nulling algorithm, displayed the speed needed to meet the RTA. To ensure robustness of the algorithm, the ability of 10 two-pilot crews to meet the RTA was tested in nine experimental trials representing a range of realistic conditions including a taxi route change, an RTA change, a departure clearance change, and a crossing traffic hold scenario. In some trials, these DataComm taxi clearances or clearance modifications were accompanied by 'preview' information, in which the airport map display showed a preview of the proposed route changes, including the necessary speed to meet the RTA. Overall, the results of this study show that with the aid of the RTA speed algorithm, pilots were able to meet their RTAs with very little time error in all of the robustness-testing scenarios. Results indicated that when taxi clearance changes were issued by DataComm only, pilots required longer notification distances than with voice communication. However, when the DataComm was accompanied by graphical preview, the notification distance required by pilots was equivalent to that for voice.

NextGen↗
NASA NTRS2014

Safely Conducting Airport Surface Trajectory-Based Operations

A piloted simulation study was conducted at the National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) to evaluate the ability to safely conduct surface trajectory-based operations (STBO) by assessing the impact of providing traffic intent information, conflict detection and resolution (CD&R) system capability, and the display of STBO guidance to the flight crew on both head-down and head-up displays (HUD). Nominal and off-nominal conflict scenarios were conducted using 12 airline crews operating in a simulated Memphis International Airport terminal environment. The flight crews met their required time-of-arrival at route end within 10 seconds on 98 percent of the trials, well within the acceptable performance bounds of 15 seconds. Traffic intent information was found to be useful in determining the intent of conflict traffic, with graphical presentation preferred. The CD&R system was only minimally effective during STBO because the prevailing visibility was sufficient for visual detection of incurring traffic. Overall, the pilots indicated STBO increased general situation awareness but also negatively impacted workload, reduced the ability to watch for other traffic, and increased head-down time.

Jones, Denise R.↗
NASA NTRS2016

Oceanic Flights and Airspace: Improving Efficiency by Trajectory-Based Operations

Oceanic operations suffer from multiple inefficiencies, including pre-departure planning that does not adequately consider uncertainty in the proposed trajectory, restrictions on the routes that a flight operator can choose for an oceanic crossing, time-consuming processes and procedures for amending en route trajectories, and difficulties exchanging data between Flight Information Regions (FIRs). These inefficiencies cause aircraft to fly suboptimal trajectories, burning fuel and time that could be conserved. A concept to support integration of existing and emerging capabilities and concepts is needed to transition to an airspace system that employs Trajectory Based Operations (TBO) to improve efficiency and safety in oceanic operations. This paper describes such a concept and the results of preliminary activities to evaluate the concept, including a stakeholder feedback activity, user needs analysis, and high level benefits analysis.

Fernandes, Alicia Borgman↗
NASA NTRS2011

Dynamic Weather Routes: A Weather Avoidance Concept for Trajectory-Based Operations

The integration of convective weather modeling with trajectory automation for conflict detection, trial planning, direct routing, and auto resolution has uncovered a concept that could help controllers, dispatchers, and pilots identify improved weather routes that result in significant savings in flying time and fuel burn. Trajectory automation continuously and automatically monitors aircraft in flight to find those that could potentially benefit from improved weather reroutes. Controllers, dispatchers, and pilots then evaluate reroute options to assess their suitability given current weather and traffic. In today's operations aircraft fly convective weather avoidance routes that were implemented often hours before aircraft approach the weather and automation does not exist to automatically monitor traffic to find improved weather routes that open up due to changing weather conditions. The automation concept runs in real-time and employs two keysteps. First, a direct routing algorithm automatically identifies flights with large dog legs in their routes and therefore potentially large savings in flying time. These are common - and usually necessary - during convective weather operations and analysis of Fort Worth Center traffic shows many aircraft with short cuts that indicate savings on the order of 10 flying minutes. The second and most critical step is to apply trajectory automation with weather modeling to determine what savings could be achieved by modifying the direct route such that it avoids weather and traffic and is acceptable to controllers and flight crews. Initial analysis of Fort Worth Center traffic suggests a savings of roughly 50% of the direct route savings could be achievable.The core concept is to apply trajectory automation with convective weather modeling in real time to identify a reroute that is free of weather and traffic conflicts and indicates enough time and fuel savings to be considered. The concept is interoperable with today's integrated FMS/datalink. Auxiliary(lat/long) waypoints define a minimum delay reroute between current position and a downstream capture fix beyond the weather. These auxiliary waypoints can be uplinked to equipped aircraft and auto-loaded into the FMS. Alternatively, for unequipped aircraft, auxiliary waypoints can be replaced by nearby named fixes, but this could reduce potential savings. The presentation includes an overview of the automation approach and focuses on several cases in terms of potential savings, reroute complexity, best auxiliary waypoint solution vs. named fix solution, and other metrics.

McNally, B. David↗
NASA NTRSDate not supplied

Trajectory Based Operations (TBO)

Today, the FAA is fully engaged in the development and deployment of TBO for the NAS. To realize TBO, the FAA and NAS user community recognize the importance of systems-of-systems thinking and of greater integration across systems, programs, teams, and between research and the field. The ATD-1 Operational Integration Assessment (OIA), helped blaze the trail for this important transition while moving TBFM Terminal Sequencing and Spacing (TSAS) down the path to deployment. Only a few years later, a comprehensive flight test of Flight Deck Interval Management (FIM) capabilities was executed, complementary and interoperable with traffic flow capabilities that were then emerging for TBO. Together, the ATD-1 tech transfers helped pave the way for the highly integrated systems-of-systems development and acquisition being undertaken for TBO. This session will chart that path to where we are today, and where we are going in the future.

ATD-1, TSAS, FIM, trajectory based operations↗
NASA NTRS2016

Understanding Current Safety Issues for Trajectory Based Operations

Increases in procedural complexity were investigated as a possible contributor to flight path deviations in airline operations. Understanding current operational issues and their causes must be embraced to maintain current safety standards while increasing future functionality. ASRS data and expert narratives were used to discover factors relating to pilot deviations. Our investigation pointed to ATC intervention, automation confusion, procedure design, and mixed equipment as primary issues. Future work will need to include objective data and mitigation strategies.

RNAV STAR↗