Search NASA⌕ Search

SEARCH · Search NASA

Results for “Traffic Data Manager”

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 55 records · Page 3

Initial Approach to Collect Small Unmanned Aircraft System Off-Nominal Operational Situations Data

NASA is developing the Unmanned Aircraft System Traffic Management research platform to safely integrate small unmanned aircraft operations in large-scale at low-altitudes. As a part of this effort, small unmanned aircraft system off-nominal operational situations data collection process has been developed to take lessons learned and to reinforce operational compliance. In this paper, descriptions of variables used for digital data collection and an online report form for collection of observational data from the operators (contextual data) are provided. They are used to collect off-nominal data from the Unmanned Aircraft System Traffic Management National Campaign in 2017. The digital data show that 2 out of 118 campaign operations (1.7%) encountered loss of navigation. Since the campaign aircraft used Global Positioning System for navigation, it is likely that unobstructed view of the sky at the campaign locations contributed to this small number. Also, 4 out of 47 operations (8.5%) encountered loss of communications. A relatively short distance between ground control system and aircraft, ranging from 2300 feet to 4200 feet, likely contributed to this small number. There was no data to identify the loss of communications condition, aircraft received signal strength, for the remaining 71 operations suggesting that some operators may not be monitoring unmanned aircraft communications system performance or monitoring it with different parameters. For the contextual data, due to the low number of total reports during the campaign, no significant trends emerged. This is an initial attempt to collect contextual data from small unmanned aircraft operators about off-nominal situations, and changes will be made to the future data collection to improve the amount and quality of the information.

unmanned aviation systems traffic management (UTM)↗

Initial Approach to Collect Small Unmanned Aircraft System Off-Nominal Operational Situations Data

NASA is developing the Unmanned Aircraft System Traffic Management research platform to safely integrate small unmanned aircraft operations in large-scale at low-altitudes. As a part of this effort, small unmanned aircraft system off-nominal operational situations data collection process has been developed to take lessons learned and to reinforce operational compliance. In this paper, descriptions of variables used for digital data collection and an online report form for collection of observational data from the operators (contextual data) are provided. They are used to collect off-nominal data from the Unmanned Aircraft System Traffic Management National Campaign in 2017. The digital data show that 2 out of 118 campaign operations (1.7%) encountered loss of navigation. Since the campaign aircraft used Global Positioning System for navigation, it is likely that unobstructed view of the sky at the campaign locations contributed to this small number. Also, 4 out of 47 operations (8.5%) encountered loss of communications. A relatively short distance between ground control system and aircraft, ranging from 2300 feet to 4200 feet, likely contributed to this small number. There was no data to identify the loss of communications condition, aircraft received signal strength, for the remaining 71 operations suggesting that some operators may not be monitoring unmanned aircraft communications system performance or monitoring it with different parameters. For the contextual data, due to the low number of total reports during the campaign, no significant trends emerged. This is an initial attempt to collect contextual data from small unmanned aircraft operators about off-nominal situations, and changes will be made to the future data collection to improve the amount and quality of the information.

Jung, Jaewoo↗

Ames Contrail Simulation Model: Modeling Aviation Induced Contrails and the Computation of Contrail Radiative Forcing Using Air Traffic Data

NASA is developing traffic flow management strategies to reduce the impact of aviation on climate and improve efficiency of aircraft routes in the presence of limited airport and airspace capacity constraints, which are partly due to convective weather and natural calamities. Development of Strategic Traffic Flow Management (STFM) requires models of aircraft emissions and contrails, and models of their effect on climate. There is extensive literature on the modeling of contrails and the Radiative Forcing (RF) associated with contrails. This report captures the latest NASA developments in this research area and describes the integrated modeling, analysis, and software development to support STFM. Aircraft contrails are long, thin and often linear clouds triggered by aircraft engine exhausts in the high-altitude ice-saturated atmosphere. Contrails, similar to that of natural cirrus clouds, can impact global climate by reflecting shortwave radiation and trapping longwave radiation. Recent studies from the Intergovernmental Panel on Climate Change (IPCC) have shown that aircraft contrails are estimated to have greater impact on global warming than aircraft CO 2 emissions. The Ames Contrail Simulation Model (ACSM) presented in this report simulates the full life cycle of aircraft contrails, including their formation, dynamic evolution, and dissipation, and calculates the associated RF with actual meteorological and air traffic data. ACSM combines models from previous studies that focus on contrail formation and persistence based on the Schmidt-Appleman theoretical criteria, and it incorporates elements of cloud dynamics, microphysics, and climate modeling found in other surveyed contrail models, while also making adjustment for improved computational efficiency. In addition, ACSM is integrated with NASA's state-of-the-art flight simulation software for rapid assessment of aircraft contrail impacts. Applications include assessments of long-term global climate impact resulting from aviation-induced contrails and the design of optimal contrail-mitigation aircraft operation strategies.

aviation contrails↗

NASA/FAA North Texas Research Station Overview

NTX Research Staion: NASA research assets embedded in an interesting operational air transport environment. Seven personnel (2 civil servants, 5 contractors). ARTCC, TRACON, Towers, 3 air carrier AOCs(American, Eagle and Southwest), and 2 major airports all within 12 miles. Supports NASA Airspace Systems Program with research products at all levels (fundamental to system level). NTX Laboratory: 5000 sq ft purpose-built, dedicated, air traffic management research facility. Established data links to ARTCC, TRACON, Towers, air carriers, airport and NASA facilities. Re-configurable computer labs, dedicated radio tower, state-of-the-art equipment.

Borchers, Paul F.↗

Expanding the Operational Use of Total Lightning Ahead of GOES-R

NASA's Short‐term Prediction Research and Transition Center (SPoRT) has been transitioning real‐time total lightning observations from ground‐based lightning mapping arrays since 2003. This initial effort was with the local Weather Forecast Offices (WFO) that could use the North Alabama Lightning Mapping Array (NALMA). These early collaborations established a strong interest in the use of total lightning for WFO operations. In particular the focus started with warning decision support, but has since expanded to include impact‐based decision support and lightning safety. SPoRT has used its experience to establish connections with new lightning mapping arrays as they become available. The GOES‐R / JPSS Visiting Scientist Program has enabled SPoRT to conduct visits to new partners and expand the number of operational users with access to total lightning observations. In early 2014, SPoRT conducted the most recent visiting scientist trips to meet with forecast offices that will used the Colorado, Houston, and Langmuir Lab (New Mexico) lightning mapping arrays. In addition, SPoRT met with the corresponding Center Weather Service Units (CWSUs) to expand collaborations with the aviation community. These visits were an opportunity to learn about the forecast needs of each office visited as well as to provide on‐site training for the use of total lightning, setting the stage for a real‐time assessment during May‐July 2014. With five lightning mapping arrays covering multiple geographic locations, the 2014 assessment has demonstrated numerous uses of total lightning in varying situations. Several highlights include a much broader use of total lightning for impact‐based decision support ranging from airport weather warnings, supporting fire crews, and protecting large outdoor events. The inclusion of the CWSUs has broadened the operational scope of total lightning, demonstrating how these data can support air traffic management, particularly in the Terminal Radar Approach Control Facilities (TRACON) region around an airport. These collaborations continue to demonstrate, from the operational perspective, the utility of total lightning and the importance of continued training and preparation in advance of the Geostationary Lightning Mapper.

GLM↗

Autonomous System Technologies for Resilient Airspace Operations

Increasing autonomous systems within the aircraft cockpit begins with an effort to understand what autonomy is and developing the technology that encompasses it. Autonomy allows an agent, human or machine, to act independently within a circumscribed set of goals; delegating responsibility to the agent(s) to achieve overall system objective(s). Increasingly Autonomous Systems (IAS) are the highly sophisticated progression of current automated systems toward full autonomy. Working in concert with humans, these types of technologies are expected to improve the safety, reliability, costs, and operational efficiency of aviation. IAS implementation is imminent, which makes the development and the proper performance of such technologies, with respect to cockpit operation efficiency, the management of air traffic and data communication information, vital. A prototype IAS agent that attempts to optimize the identification and distribution of "relevant" air traffic data to be utilized by human crews during complex airspace operations has been developed.

Houston, Vincent E.↗

Airspace Technology Demonstration 2 (ATD-2) Integrated Surface and Airspace Simulation - Experiment Plan

This presentation describes the objectives and high level setup for the human-in-the-loop simulation of the integrated surface and airsapce simulation of the ATD-2 Integrated Arrival, Departure, Surface (IADS) system. The purpose of the simulation is to evaluate the functionality of the IADS system, including tactical surface scheduler, negotiation of departure times for the flights under Traffic Management Initiatives (TMIs), and data exchange between ATC Tower and airline Ramp. The same presentation was presented to serve the experiment review prior to the simulation.

Surface↗

Ramp Traffic Console (RTC) Ramp Manager Traffic Console (RMTC) User Manual

This document serves as a user manual for the Ramp Traffic Console (RTC) in the Ramp Control Tower. It describes the elements of the RTC interface and provides explanations for how to utilize the RTC to manage ramp traffic. The RTC provides live data for all flights including Earliest Off-Block Times (EOBT) and Traffic Management Initiatives (TMI). The RTC augments management of ramp traffic by providing notifications of runway configurations, and lists flight arrivals, near arrivals and departures as additional sources of information. If applicable, this document also provides instructions for use of the Ramp Manager Traffic Console (RMTC) for ramp manager functions of adjusting the priority flight list, and setting ramp status. The RTC/RMTC ramp tool are components of Airspace Technology Demonstration-2.

ATD-2 RMTC↗

Discovery and Synchronization Service Architectural Notes

This is a short architectural note for a critical component of safely scaling drone operations. The primary motivation for this note is to collect language and terminology around the Discovery and Synchronization Service (DSS) as it is currently implemented for Uncrewed Aircraft System (UAS) Traffic Management. The major driver for this document was frequent miscommunication about DSS. Often there have been multiple informed and invested stakeholders in the same room making statements about “multiple DSSs” and each of them meaning something slightly different.

uas traffic management↗

Departure Approval Request Compliance Effects on Overhead Stream Insertion

Integrated Arrival-Departure-Surface (IADS) air traffic management relies on information sharing and integration between automation systems for efficiency, predictability, and throughput improvements throughout the National Airspace System (NAS). The NASA Airspace Technology Demonstration 2 (ATD-2) project supports this effort by integrating SWIM (System Wide Information Management) information and evaluating and refining potential TFDM (Terminal Flight Data Manager) functionality in a surface traffic management system fielded at Charlotte-Douglas International Airport (CLT). Among the IADS areas under study during ATD-2 is the use of electronically negotiated departure times for efficiently inserting flights into overhead traffic streams. Stream-insertion accuracy is important for reducing excessive vectoring that negatively impacts the NAS by increasing controller workload along with aircraft fuel burn and emissions. Departure-time approval requests (APREQs) provide center-approved departure times to allow for smooth stream insertion. In this presentation, TBFM (Time-Based Flow Management) and ATD-2 flight summary data are used to empirically show that APREQ compliance leads to improved stream insertion.

Overhead-Stream Insertion↗

Generic Airspace Concepts and Research

The purpose of this study was to evaluate methods for reducing the training and memorization required to manage air traffic in mid-term, Next Generation Air Transportation System (NextGen) airspace. We contrasted the performance of controllers using a sector information display and NextGen automation tools while working with familiar and unfamiliar sectors. The airspace included five sectors from Oakland and Salt Lake City Centers configured as a "generic center" called "West High Center." The Controller Information Tool was used to present essential information for managing these sectors. The Multi Aircraft Control System air traffic control simulator provided data link and conflict detection and resolution. There were five experienced air traffic controller participants. Each was familiar with one or two of the five sectors, but not the others. The participants rotated through all five sectors during the ten data collection runs. The results addressing workload, traffic management, and safety, as well as controller and observer comments, supported the generic sector concept. The unfamiliar sectors were comparable to the familiar sectors on all relevant measures.

Mogford, Richard H.↗

Traffic Management for Satellite-ATM Networks

Various issues associated with "Traffic Management for Satellite-ATM Networks" are presented in viewgraph form. Specific topics include: 1) Traffic management issues for TCP/IP based data services over satellite-ATM networks; 2) Design issues for TCP/IP over ATM; 3) Optimization of the performance of TCP/IP over ATM for long delay networks; and 4) Evaluation of ATM service categories for TCP/IP traffic.

Goyal, Rohit↗

Future of Fuel Savings

Using automation to free up controllers for more strategic management of air traffic is one approach being studied by NASA as it seeks to boost airspace system capacity and efficiency, thereby saving fuel. Heinz Erzberger, a NASA Ames Research Center senior scientist, says the Advanced Airspace Concept (AAC) has been studied for several years. It could increase efficiency 15% by providing optimal routes that cut airlines direct operating costs. A 25% increase in landings on existing runways could follow an important benefit. AAC is one of the efforts to be reviewed by the Joint Planning and Development Organization, an FAA-led initiative by six federal agencies to redesign the U.S. air transportation system by 2025. The main goal is to triple air traffic capacity within 20 years to avert the sort of gridlock that would make fuel consumption only one of many travel nightmares. The automated system approach would allow aircraft to fly optimal trajectories. A trajectory would be defined in the standard three dimensions and eventually include the fourth, time. The management of air traffic by the data-linked exchange of trajectories would start at high altitude and eventually move down to lower altitudes. The automated concept is an outgrowth of the type of tools developed by NASA for use by FAA controllers in managing traffic flows over the years, including ones that optimize routings for the best fuel burn. But AAC would push automation further to reduce workload so controllers can focus on "solving strategic control problems, managing traffic flow during changing weather and ... other unusal events." One key component, the automated trajectory server (ATS), is a ground systems that would rely on software to manage flight path requests from aircrews and controllers. But, Erzberger acknowledges, "The FAA's current plan for upgrades to air traffic services does not include [allowing] the future ground system to issue separation-critical clearances of trajectory changes autonomously to aircraft via data link without explicit approval of a controller," as the AAC proposes. The AAC enables pilots or controllers to data link requests for a trajectory change to the ATS for approval after they are deconflicted with the paths of other aircraft. To divert around storms, for example, pilots could data link their trajectory preference to the ATS. Since several aircraft might request similar routes, the computer would then have to suggest alternatives. This could be accomplished without pilot-controller radio calls, a big bottleneck now. The ATS would have a built-in conflict monitor to call for a resolution (turn, climb or descend), when loss of separation is likely in 1-20 min. The AAC system would reduce controller errors by 90%, according to NASA Ames estimates. The AAC would have a back-up program to assure separation-Tactical Separation Assurance (TSAFE). It s designed to detect short-term traffic conflicts within 3-4 min. of loss of separation. The last line of defense would still be provided by traffic alert & collision avoidance systems (TCAS).

Hughes, David↗

Air Traffic Management-eXploration Testbed for Urban Air Mobility Research and Development

The presentation will describe the architecture, current capabilities and some future enhancements of the testbed that is being developed at the National Aeronautics and Space Administration (NASA) to enable benefit, impact, safety and cost assessments for accelerating the deployment of air traffic management concept and technologies in the national airspace system. The testbed will support analysis of operational feasibility of urban air mobility operations, a part of NASA's Air Traffic Management eXploration project, and provide the data needed by regulatory agencies charged with public safety. Introduction of concepts and technologies, especially new concepts and technologies, is difficult and often takes decades because of the inability to assess the operational impact of the interaction between the proposed concept and technology and operationally deployed systems in terms of system-wide safety, traffic flow efficiency, roles and workload of controllers and traffic managers, and impact on airlines and other operators. To overcome these limitations, the testbed is developing infrastructure to enable mathematical modeling, human-in-the-loop evaluations and testing with operational systems in a simulated environment. In addition to the difficulty of establishing communications between geographically distributed systems, downloading/installing software, and management of startup, error-handling and shutdown, a major impediment for conducting simulations and human-in-the-loop testing with operational systems is the tedious manual scenario generation process. Several of these difficulties have been addressed in the current state of the testbed. The testbed can be described in terms of the following elements- (1) web-based frontend and backend, (2) Testbed Builder, (3) Data Distribution Service, (4) Component Library, (5) Simulation Management, and (6) Scenario Generation. The web-based frontend and backend enable the user to interact with the testbed for tasks such as composing a simulation, running a simulation and retrieving output data. The Testbed Builder application launched from the web frontend is a graphical user interface for the user to drag-and-drop and connect predefined blocks for composing a simulation/scenario generation task. The Builder writes a set of instructions for Simulation Management based on the links between the blocks and the block properties such as the component (executable) associated with a particular block. Management of the distributed simulation is accomplished by Execution and Component Managers. Execution Manager interprets the instructions provided by the Builder to instruct the Component Managers to download components from the Component Library to specified computers and to start them up. Once started, the components communicate with each other by publishing messages and subscribing to messages that are delivered by the Data Distribution Service. The Scenario Generation capability can be used for creating traffic scenarios for Multi-Aircraft Control System, which has been used extensively at NASA for human-in-the-loop-based concept evaluations. The presentation will provide a testbed enabled example scenario of Multi-Aircraft Control System based simulation in which the urban air mobility pilot using the conflict detection and resolution system would interact with the air traffic controllers for resolving conflicts with other aircraft during terminal area operations.

Simulation↗

ISS Operations Cost Reductions Through Automation of Real-Time Planning Tasks

In 2008 the Johnson Space Center s Mission Operations Directorate (MOD) management team challenged their organization to find ways to reduce the costs of International Space station (ISS) console operations in the Mission Control Center (MCC). Each MOD organization was asked to identify projects that would help them attain a goal of a 30% reduction in operating costs by 2012. The MOD Operations and Planning organization responded to this challenge by launching several software automation projects that would allow them to greatly improve ISS console operations and reduce staffing and operating costs. These projects to date have allowed the MOD Operations organization to remove one full time (7 x 24 x 365) ISS console position in 2010; with the plan of eliminating two full time ISS console support positions by 2012. This will account for an overall 10 EP reduction in staffing for the Operations and Planning organization. These automation projects focused on utilizing software to automate many administrative and often repetitive tasks involved with processing ISS planning and daily operations information. This information was exchanged between the ground flight control teams in Houston and around the globe, as well as with the ISS astronaut crew. These tasks ranged from managing mission plan changes from around the globe, to uploading and downloading information to and from the ISS crew, to even more complex tasks that required multiple decision points to process the data, track approvals and deliver it to the correct recipient across network and security boundaries. The software solutions leveraged several different technologies including customized web applications and implementation of industry standard web services architecture between several planning tools; as well as a engaging a previously research level technology (TRL 2-3) developed by Ames Research Center (ARC) that utilized an intelligent agent based system to manage and automate file traffic flow, archiving f data, and generating console logs. This technology called OCAMS (OCA (Orbital Communication System) Management System), is now considered TRL level 9 and is in daily use in the Mission Control Center in support of ISS operations. These solutions have not only allowed for improved efficiency on console; but since many of the previously manual data transfers are now automated, many of the human error prone steps have been removed, and the quality of the planning products has improved tremendously. This has also allowed our Planning Flight Controllers more time to focus on the abstract areas of the job, (like the complexities of planning a mission for 6 international crew members with a global planning team), instead of being burdened with the administrative tasks that took significant time each console shift to process. The resulting automation solutions have allowed the Operations and Planning organization to realize significant cost savings for the ISS program through 2020 and many of these solutions could be a viable

Hall, Timothy A.↗

Air Traffic Management-eXploration Testbed for Urban Air Mobility Research and Development

The presentation will describe the architecture, current capabilities and some future enhancements of the testbed that is being developed at the National Aeronautics and Space Administration (NASA) to enable benefit, impact, safety and cost assessments for accelerating the deployment of air traffic management concept and technologies in the national airspace system. The testbed will support analysis of operational feasibility of urban air mobility operations, a part of NASA's Air Traffic Management eXploration project, and provide the data needed by regulatory agencies charged with public safety. Introduction of concepts and technologies, especially new concepts and technologies, is difficult and often takes decades because of the inability to assess the operational impact of the interaction between the proposed concept and technology and operationally deployed systems in terms of system-wide safety, traffic flow efficiency, roles and workload of controllers and traffic managers, and impact on airlines and other operators. To overcome these limitations, the testbed is developing infrastructure to enable mathematical modeling, human-in-the-loop evaluations and testing with operational systems in a simulated environment. In addition to the difficulty of establishing communications between geographically distributed systems, downloading/installing software, and management of startup, error-handling and shutdown, a major impediment for conducting simulations and human-in-the-loop testing with operational systems is the tedious manual scenario generation process. Several of these difficulties have been addressed in the current state of the testbed. The testbed can be described in terms of the following elements (1) web-based frontend and backend, (2) Testbed Builder, (3) Data Distribution Service, (4) Component Library, (5) Simulation Management, and (6) Scenario Generation. The web-based frontend and backend enable the user to interact with the testbed for tasks such as composing a simulation, running a simulation and retrieving output data. The Testbed Builder application launched from the web frontend is a graphical user interface for the user to drag-and-drop and connect predefined blocks for composing a simulation/scenario generation task. The Builder writes a set of instructions for Simulation Management based on the links between the blocks and the block properties such as the component (executable) associated with a particular block. Management of the distributed simulation is accomplished by Execution and Component Managers. Execution Manager interprets the instructions provided by the Builder to instruct the Component Managers to download components from the Component Library to specified computers and to start them up. Once started, the components communicate with each other by publishing messages and subscribing to messages that are delivered by the Data Distribution Service. The Scenario Generation capability can be used for creating traffic scenarios for Multi-Aircraft Control System, which has been used extensively at NASA for human-in-the-loop-based concept evaluations. The presentation will provide a testbed enabled example scenario of Multi-Aircraft Control System based simulation in which the urban air mobility pilot using the conflict detection and resolution system would interact with the air traffic controllers for resolving conflicts with other aircraft during terminal area operations.

Testbed↗

Reduced cost alternatives to premise wiring using ATM and microcellular technologies

The cost of premises wiring keeps increasing due to personnel moves, new equipment, capacity upgrades etc. It would be desirable to have a wireless interface from the workstations to the fixed network, so as to minimize the wiring changes needed. New technologies such as microcellular personal communication systems are promising to bring down the cost of wireless communication. Another promising technology is Code Division Multiple Access (CDMA), which could dramatically increase the bandwidth available for wireless connections. In addition, Asynchronous Transfer Mode (ATM) technology is emerging as a technique for integrated management of voice, data, and video traffic on a single network. The focus of this investigation will be to assess the future utility of these new technologies for reducing the premise wiring cost at KSC. One of the issues to be studied is the cost comparison of 'old' versus 'new,' especially as time and technology progress. An additional issue for closer study is a feasible time-line for progress in technological capability.

Gejji, Raghvendra R.↗

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