1994
DOI: 10.1016/s1474-6670(17)45781-8
|View full text |Cite
|
Sign up to set email alerts
|

The Final Approach Spacing Tool

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
13
0

Year Published

1997
1997
2021
2021

Publication Types

Select...
3
3
3

Relationship

0
9

Authors

Journals

citations
Cited by 54 publications
(13 citation statements)
references
References 1 publication
0
13
0
Order By: Relevance
“…Later, a prototype system known as passive FAST was developed and operationally tested at DFW TRACON. 10 Passive FAST advises landing sequence and runway assignment to balance runway loading and reduce inter-arrival spacing. Further NASA efforts are focused on the development of an enhanced version known as active FAST (aFAST).…”
Section: Previous Research and Developmentmentioning
confidence: 99%
“…Later, a prototype system known as passive FAST was developed and operationally tested at DFW TRACON. 10 Passive FAST advises landing sequence and runway assignment to balance runway loading and reduce inter-arrival spacing. Further NASA efforts are focused on the development of an enhanced version known as active FAST (aFAST).…”
Section: Previous Research and Developmentmentioning
confidence: 99%
“…A number of researchers and air navigation service providers hypothesize that the inclusion of CDR tools into air traffic control systems will reduce or transform controller workload by decreasing the amount of time and mental effort that air traffic controllers spend resolving conflicts [6]- [9]. Unfortunately, many of the CDR algorithms attempt to replace air traffic controllers, moving them from their current tactical role to a more strategic traffic flow management role.…”
Section: Introductionmentioning
confidence: 99%
“…At the core of these concepts is the Center TRACON Automation System (CTAS), which is comprised of legacy software that has had many successes. 1,2,3,4 Unfortunately, this legacy software has become increasingly difficult to maintain and extend. For example, in order to rapidly prototype the initial en route conflict detection functionality, developers reused runway sequencing software written for the terminal area.…”
Section: Introductionmentioning
confidence: 99%
“…For example, in order to rapidly prototype the initial en route conflict detection functionality, developers reused runway sequencing software written for the terminal area. 4 At that time, software efficiency was a high priority due to limitations in computer hardware performance, while data integrity and software maintenance issues had less importance. 5 As the next generation air traffic management (ATM) research requirements are being defined however, it is clear that the CTAS en route conflict detection and resolution software must handle increased algorithmic complexity without sacrificing software reliability if it is to form the basis for future technologies.…”
Section: Introductionmentioning
confidence: 99%