A compensatory algorithm for the slow-down effect on constant-time-separation approaches

In seeking methods to improve airport capacity, the question arose as to whether an electronic display could provide information which would enable the pilot to be responsible for self-separation under instrument conditions to allow for the practical implementation of reduced separation, multiple glide path approaches. A time based, closed loop algorithm was developed and simulator validated for in-trail (one aircraft behind the other) approach and landing. The algorithm was designed to reduce the effects of approach speed reduction prior to landing for the trailing aircraft as well as the dispersion of the interarrival times. The operational task for the validation was an instrument approach to landing while following a single lead aircraft on the same approach path. The desired landing separation was 60 seconds for these approaches. An open loop algorithm, previously developed, was used as a basis for comparison. The results showed that relative to the open loop algorithm, the closed loop one could theoretically provide for a 6 pct. increase in runway throughput. Also, the use of the closed loop algorithm did not affect the path tracking performance and pilot comments indicated that the guidance from the closed loop algorithm would be acceptable from an operational standpoint. From these results, it is concluded that by using a time based, closed loop spacing algorithm, precise interarrival time intervals may be achievable with operationally acceptable pilot workload

An Overview of a Trajectory-Based Solution for En Route and Terminal Area Self-Spacing: Seventh Revision

This paper presents an overview of the seventh revision to an algorithm specifically designed to support NASA's Airborne Precision Spacing concept. This paper supersedes the previous documentation and presents a modification to the algorithm referred to as the Airborne Spacing for Terminal Arrival Routes version 13 (ASTAR13). This airborne self-spacing concept contains both trajectory-based and state-based mechanisms for calculating the speeds required to achieve or maintain a precise spacing interval. The trajectory-based capability allows for spacing operations prior to the aircraft being on a common path. This algorithm was also designed specifically to support a standalone, non-integrated implementation in the spacing aircraft. This current revision to the algorithm adds the state-based capability in support of evolving industry standards relating to airborne self-spacing

An Overview of a Trajectory-Based Solution for En Route and Terminal Area Self-Spacing to Include Parallel Runway Operations

This paper presents an overview of an algorithm specifically designed to support NASA's Airborne Precision Spacing concept. This airborne self-spacing concept is trajectory-based, allowing for spacing operations prior to the aircraft being on a common path. This implementation provides the ability to manage spacing against two traffic aircraft, with one of these aircraft operating to a parallel dependent runway. Because this algorithm is trajectory-based, it also has the inherent ability to support required-time-of-arrival (RTA) operation

An Overview of a Trajectory-Based Solution for En Route and Terminal Area Self-Spacing: Third Revision

This paper presents an overview of the third major revision to an algorithm specifically designed to support NASA's Airborne Precision Spacing concept. This algorithm is referred to as the Airborne Spacing for Terminal Arrival Routes version 11 (ASTAR11). This airborne self-spacing concept is trajectory-based, allowing for spacing operations prior to the aircraft being on a common path. Because this algorithm is trajectory-based, it also has the inherent ability to support required time-of-arrival (RTA) operations. This algorithm was also designed specifically to support a standalone, non-integrated implementation in the spacing aircraft

An Overview of a Trajectory-Based Solution for En Route and Terminal Area Self-Spacing: Fifth Edition

This paper presents an overview of the fifth revision to an algorithm specifically designed to support NASA's Airborne Precision Spacing concept. This algorithm is referred to as the Airborne Spacing for Terminal Arrival Routes version 12 (ASTAR12). This airborne self-spacing concept is trajectory-based, allowing for spacing operations prior to the aircraft being on a common path. Because this algorithm is trajectory-based, it also has the inherent ability to support required-time-of- arrival (RTA) operations. This algorithm was also designed specifically to support a standalone, non-integrated implementation in the spacing aircraft. This current revision to the algorithm includes a ground speed feedback term to compensate for slower than expected traffic aircraft speeds based on the accepted air traffic control tendency to slow aircraft below the nominal arrival speeds when they are farther from the airport

Functional categories for future flight deck designs

With the addition of each new system on the flight deck, the danger of increasing overall operator workload while reducing crew understanding of critical mission information exists. The introduction of more powerful onboard computers, larger databases, and the increased use of electronic display media may lead to a situation of flight deck 'sophistication' at the expense of losses in flight crew capabilities and situational awareness. To counter this potentially negative impact of new technology, research activities are underway to reassess the flight deck design process. The fundamental premise of these activities is that a human-centered, systems-oriented approach to the development of advanced civil aircraft flight decks will be required for future designs to remain ergonomically sound and economically competitive. One of the initial steps in an integrated flight deck process is to define the primary flight deck functions needed to support the mission goals of the vehicle. This would allow the design team to evaluate candidate concepts in relation to their effectiveness in meeting the functional requirements. In addition, this would provide a framework to aid in categorizing and bookkeeping all of the activities that are required to be performed on the flight deck, not just activities of the crew or of a specific system. This could then allow for a better understanding and allocation of activities in the design, an understanding of the impact of a specific system on overall system performance, and an awareness of the total crew performance requirements for the design. One candidate set of functional categories that could be used to guide an advanced flight deck design are described

Effects of combining vertical and horizontal information into a primary flight display

A ground-based aircraft simulation study was conducted to determine the effects of combining vertical and horizontal flight information into a single display. Two display configurations were used in this study. The first configuration consisted of a Primary Flight Display (PFD) format and a Horizontal Situation Display (HSD) with the PFD displayed conventionally above the HSD. For the second display configuration, the HSD format was combined with the PFD format. Four subjects participated in this study. Data were collected on performance parameters, pilot-control inputs, auditory evoked response parameters (AEP), oculometer measurements (eye-scan), and heart rate. Subjective pilot opinion was gathered through questionnaire data and scorings for both the Subjective Workload Assessment Technique (SWAT) and the NASA Task Load Index (NASA-TLX). The results of this study showed that, from a performance and subjective standpoint, the combined configuration was better than the separate configuration. Additionally, both the eye-transition and eye-dwell times for the separate HSD were notably higher than expected, with a 46% increase in available visual time when going from double to single display configuration