Engineering topics

Koteskey, Robert W.

Publications and source records attributed to Koteskey, Robert W..

4 records

NASA NTRS2018

Flight Deck Implications for the Implementation of an Integrated Arrival, Departure, and Surface (IADS) Traffic Management System

NASA's Airspace Technical Demonstration-2 (ATD-2) Integrated Arrival, Departure, and Surface (IADS) traffic management system integrates strategic and tactical scheduling tools for traffic sequencing from the gate to the overhead stream and back again for multi-airport, metroplex environments. The system is expected to increase airport efficiency, predictability, and throughout while improving information sharing among all airport operators. A series of knowledge elicitation sessions were conducted with commercial airline pilots and general aviation pilots to characterize airport operations and procedures. This presentation describes ATD-2 IADS-enabled Information Sharing impacts on the Flight Deck, benefits of that Information Sharing, pilot procedural changes, our pilot engagement/outreach efforts, use of a Mobile App to faciliate information flow in GA operations, and future IADS efforts at other airports/metroplexes.

IADS↗

NASA NTRS2017

Predicted Weather Display and Decision Support Interface for Flight Deck

A system and method for providing visual depictions of a predictive weather forecast for in-route vehicle trajectory planning. The method includes displaying weather information on a graphical display, displaying vehicle position information on the graphical display, selecting a predictive interval, displaying predictive weather information for the predictive interval on the graphical display, and displaying predictive vehicle position information for the predictive interval on the graphical display, such that the predictive vehicle position information is displayed relative to the predictive weather information, for in-route trajectory planning.

Johnson, Walter W.↗

NASA NTRS2016

System and Method for Providing a Real Time Audible Message to a Pilot

A system and method for providing information to a crew of the aircraft while in-flight. The system includes a module having: a receiver for receiving a message while in-flight; a filter having a set of screening parameters and operative to filter the message based on the set of screening parameters; and a converter for converting the message into an audible message. The message includes a pilot report having at least one of weather information, separation information, congestion information, flight deviation information and destination information. The message is sent to the aircraft by another aircraft or an air traffic controller.

Johnson, Walter W.↗

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↗