Search NASA⌕ Search

SEARCH · Search NASA

Results for “STBO”

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 19 records
All sourcesNASA NTRSDOE OSTI
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 NTRS2019

STBO Client User Manual

This document serves as a user manual for the STBO Client utilized by ATC in the Tower. It describes the elements of the STBO Client and provides explanations for how to interact with the interface. STBO Client functionality includes the display of live flight information and management of traffic restrictions. The STBO Client is a component of the NASA Airspace Technology Demonstration 2 (ATD-2) sub-project.

Surface Decision Support Tool↗
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 NTRS2014

A Concept of Operations for Far-Term Surface Trajectory-Based Operations (STBO)

The goal of this far-term STBO (Surface Trajectory-Based Operations) ConOps (Concept of Operations) is to increase the efficiency and predictability of airport surface operations, and reduce the environmental impact, by incorporating a time-based component to surface operations. In the far-term NextGen timeframe, airport surface operations will transition from current-day first-come, first-served operations, to strategically scheduled operations in which pilots are recruited as active participants in meeting the precise time-based goals of NextGen surface operations. The far-term STBO concept includes two-phases. Phase 1 introduces time-based traffic flow constraint points, which divide the taxi route into segments with an assigned Required Time of Arrival (RTA). This Phase 1 approach provides temporal certainty only near the traffic flow constraint points, but not in between. Minimal augmentations to the flight deck are required to support required time of arrival (RTA) management. Phase 2 further increases precision and efficiency by introducing full four-dimensional (4D) trajectories, with an x-y location for all times t. This phase assumes adoption of advanced flight deck equipage enabling higher temporal precision sufficient to support aircraft conformance to 4D trajectories. This allows more precision and less temporal uncertainty at all times along the route.

Surface Trajectory-Based Operations (STBO)↗
NASA NTRS2018

Surface Trajectory Based Operations (STBO) Client User Manual

This document serves as a user manual for the STBO Client in Charlotte Douglas International Airport Air Traffic Control Tower. It describes the elements of the full interface and provides explanations for how to interact with the interface. The document also provides instructions for entering Traffic Management Initiatives, scheduling runway utilization changes, and closing runways. There are also detailed instructions for how to negotiate Approval Request (APREQ) release times using the STBO Client.

Stevens, Lindsay↗
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 NTRS2017

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

In four-dimensional trajectory (4DT) Surface Trajectory-Based Operations (STBO), aircraft are assigned a conflict-free 4DT which defines an expected location (x,y coordinates) at all times, t, along the taxi route (with altitude, being fixed). These 4DTs afford the highest temporal certainty at all points along the taxi route, and at the departure runway. In the present study, a 4DT flight deck display was presented on the Airport Moving Map (AMM) to support pilot conformance to a 4DT clearance while taxiing under manual control. This pilot-in-the-loop simulation compared the effect of 4DT flight deck display formats on distance from the expected 4DT location, conformance to the displayed tolerance band, eyes-out time, and pilot ratings of safety and workload. In the defined-tolerance display format, a graphical representation of the expected 4DT location, with a distance-based allowable-tolerance band, was depicted on the AMM. Two defined-tolerance band sizes were tested: plus or minus 164 feet and plus or minus 405 feet. In the undefined-tolerance display format, the expected 4DT location was displayed graphically on the AMM, with no indicated allowable-tolerance bounds. Each taxi trial included 4DT speed changes (two or five, per trial) and a range of 4DT taxi speeds. Results showed that the larger (plus or minus 405 feet) defined-tolerance band yielded higher conformance levels than the smaller (plus or minus 164 feet) band, with pilots staying within the specified and displayed conformance bounds more in the larger (99.71%) than the smaller defined-tolerance band (93.37 percent). However, in terms of being able to predict the location of the aircraft compared to the expected 4DT location, the smaller defined-tolerance band resulted in pilots keeping their aircraft closer to the 4DT location, for both average distance and for a given confidence interval (e.g., 95 percent), than either the larger defined-tolerance band or the undefined-tolerance display format. The larger tolerance band yielded more “eyes-out-the-window” time than the smaller tolerance band. Pilots also rated taxing with the larger tolerance band as safer than the smaller tolerance band.

STBO↗
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 NTRS2016

Conducting Safe and Efficient Airport Surface Operations in a NextGen Environment

The Next Generation Air Transportation System (NextGen) vision proposes many revolutionary operational concepts, such as surface trajectory-based operations (STBO) and technologies, including display of traffic information and movements, airport moving maps (AMM), and proactive alerts of runway incursions and surface traffic conflicts, to deliver an overall increase in system capacity and safety. A piloted simulation study was conducted at the National Aeronautics and Space Administration (NASA) Langley Research Center to evaluate the ability of a flight crew to conduct safe and efficient airport surface operations while utilizing an AMM. Position accuracy of traffic was varied, and the effect of traffic position accuracy on airport conflict detection and resolution (CD&R) capability was measured. Another goal was to evaluate the crew's ability to safely conduct STBO by assessing the impact of providing traffic intent information, CD&R system capability, and the display of STBO guidance to the flight crew on both head-down and head-up displays (HUD). Nominal scenarios and off-nominal conflict scenarios were conducted using 12 airline crews operating in a simulated Memphis International Airport terminal environment. The data suggest that all traffic should be shown on the airport moving map, whether qualified or unqualified, and conflict detection and resolution technologies provide significant safety benefits. Despite the presence of traffic information on the map, collisions or near-collisions still occurred; when indications or alerts were generated in these same scenarios, the incidents were averted. During the STBO testing, 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 conflicting 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 conflicting 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 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 NTRS2017

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↗
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↗