Air Traffic Management Concept Baseline Definition - The Boeing ...
Air Traffic Management Concept Baseline Definition - The Boeing ... Air Traffic Management Concept Baseline Definition - The Boeing ...
defined and quantified, a critical question to be asked is: how must the roles and responsibilities be changed to assure the maximum likelihood that the future mission needs will be met Traffic Flow Management S ystem T raffic Manager Sector Controller Controller Decision Support S ystem ATC Airline Airline Operational C ontrol S ystem Dispatcher Work System Flight Crew Flight Management System Figure 2.10 Primary System Agents The basic air traffic management services of the system include: air traffic control, air traffic flow management, airspace management, flight information services, navigation services and search and rescue. We have assumed, in the mission analysis, that satisfaction of system demand is the key driver on system modernization needs. Central to the air traffic control function is separation assurance. Separation minima, as enforced between IFR flights, are the primary determinants of the realized safety and theoretical throughput of a given air traffic system. The correct sizing of the long term system needs is a central modernization issue. Section 3 of this report examines implications of operating roles and responsibilities, given the postulated system needs, and focuses on research issues central to the development of a system whose capacity, safety, efficiency and productivity levels meet projected user needs over the system life. 2.3.4 System Technical Requirements Boeing believes that the separation assurance function is key to realizing fundamental system capacity and safety long range needs. In support of this thesis, Boeing has postulated a concept, Required System Performance (RSP), intended to characterize airspace and/or aircraft operating in airspace, and the level of separation service applicable. In 1996, a white paper was prepared for the RTCA Technical Management Committee on RSP (Nakamura and Schwab, 1996). This paper was endorsed by the RTCA group, and was the basis for the coordinated development of RSP across several existing RTCA 20
Special Committees. The paper, with minor modifications, was also submitted to the International Civil Aviation Organization (ICAO) Separation Panel meeting later in 1996. The paper states that the definition of required air navigation system performance should encompass navigation, communications and monitoring (or surveillance) performance and provide a related, high level characterization of the air navigation environment, RSP. The thesis of the paper is that RSP is best characterized by the traditional airspace attribute of separation minima. The paper asserts that the concept of separation minima is the primary airspace performance determinant. As indicated in Figure 2.11, for procedural environments, this separation standard is primarily related to navigation performance. In radar environments, however, with direct controller-pilot voice communications, each of the communications, navigation and surveillance (or monitoring) factors becomes important in a complex interaction of aircraft navigation, air-ground communications, radar surveillance and air traffic service-airplane interaction. Thus the concept of RSP necessarily contains elements of navigation, communications and surveillance performance. These RSP components establish the basis for an environment in which operational access approval is explicitly performance-based, in place of current practice in which the basis of approval is indirect and implicitly related to capability, based on equipage sets including navigation sensors used. 95% Navigation Performance (nm) 20 16 12 8 Procedural Environments Oceanic Base Operation NATS MNPS Proposed RNP 4 Standard RNP 4 with Proven Containment Standard RADAR Standard 4 100 80 60 40 20 0 LATERAL SEPARATION MINIMA (nm) Figure 2.11 System Performance and Separations A key element to the successful definition of system performance is that the rare- and nonnormal system performance will fundamentally drive system safety-related performance. Thus, required navigation performance (RNP) must address 95% accuracy for navigation availability and navigation system integrity level supported. Similarly, for communications and monitoring, the normal, rare-normal, and non-normal (both detected and undetected failure rates) must be specified, to insure system design that will support the future mission capacity, safety and efficiency levels. 21
- Page 1 and 2: Air Traffic Management Concept Base
- Page 3 and 4: Executive Summary This report prese
- Page 5 and 6: Table of Contents 1 Introduction...
- Page 7 and 8: List of Figures 2.1 System Developm
- Page 9 and 10: Acronyms AAS AATT ACARS ACP ADF ADF
- Page 11 and 12: KIAS LAAS LAHSO LLWAS MAC MCP MDCRS
- Page 13 and 14: 1 Introduction This report presents
- Page 15 and 16: unknown technology, and thus the co
- Page 17 and 18: 2 The NAS ATM System Development Pr
- Page 19 and 20: System Requirements & Objectives Va
- Page 21 and 22: technologies needed for initial tra
- Page 23 and 24: • The goals of various users are
- Page 25 and 26: considerations are key to evaluatin
- Page 27 and 28: Free Flight White Paper on System C
- Page 29 and 30: 4.5 4.3 4 3.7 Current NAS Future NA
- Page 31: elated component will increase with
- Page 35 and 36: efficiency-constraints model that i
- Page 37 and 38: • Problem Statement • Alternati
- Page 39 and 40: • The highly peaked nature of air
- Page 41 and 42: • Sector-level flow planning Each
- Page 43 and 44: • Flow managers Figure 3.3 shows
- Page 45 and 46: traffic situation as it currently a
- Page 47 and 48: • It is probable that the process
- Page 49 and 50: 3.3. Event-based trajectory deviati
- Page 51 and 52: egion takes on the order of years t
- Page 53 and 54: The answer to this question is like
- Page 55 and 56: Flight Schedule Flight Planning Fil
- Page 57 and 58: 4 Human Factors This section addres
- Page 59 and 60: 4.2.3 Human Factors Support For Imp
- Page 61 and 62: “System designers, regulators, an
- Page 63 and 64: arbitrating wherever intents confli
- Page 65 and 66: aircraft-to-aircraft separation res
- Page 67 and 68: 5 Available and Emerging Technology
- Page 69 and 70: function of all the ICPs of element
- Page 71 and 72: A key concept in the definition of
- Page 73 and 74: contrast, the older radars have azi
- Page 75 and 76: Broadcast (ADS-B), V6.0). Individua
- Page 77 and 78: is needed to develop cockpit displa
- Page 79 and 80: ATC Voice Procedures Waypoint Repor
- Page 81 and 82: CPC = Controller Pilot Communicatio
defined and quantified, a critical question to be asked is: how must the roles and<br />
responsibilities be changed to assure the maximum likelihood that the future mission needs<br />
will be met<br />
<strong>Traffic</strong> Flow<br />
<strong>Management</strong><br />
S ystem<br />
T raffic<br />
Manager<br />
Sector<br />
Controller<br />
Controller<br />
Decision<br />
Support<br />
S ystem<br />
ATC<br />
<strong>Air</strong>line<br />
<strong>Air</strong>line<br />
Operational<br />
C ontrol<br />
S ystem<br />
Dispatcher<br />
Work<br />
System<br />
Flight<br />
Crew<br />
Flight<br />
<strong>Management</strong><br />
System<br />
Figure 2.10 Primary System Agents<br />
<strong>The</strong> basic air traffic management services of the system include: air traffic control, air<br />
traffic flow management, airspace management, flight information services, navigation<br />
services and search and rescue. We have assumed, in the mission analysis, that satisfaction<br />
of system demand is the key driver on system modernization needs. Central to the air<br />
traffic control function is separation assurance. Separation minima, as enforced between<br />
IFR flights, are the primary determinants of the realized safety and theoretical throughput<br />
of a given air traffic system. <strong>The</strong> correct sizing of the long term system needs is a central<br />
modernization issue. Section 3 of this report examines implications of operating roles and<br />
responsibilities, given the postulated system needs, and focuses on research issues central<br />
to the development of a system whose capacity, safety, efficiency and productivity levels<br />
meet projected user needs over the system life.<br />
2.3.4 System Technical Requirements<br />
<strong>Boeing</strong> believes that the separation assurance function is key to realizing fundamental<br />
system capacity and safety long range needs. In support of this thesis, <strong>Boeing</strong> has<br />
postulated a concept, Required System Performance (RSP), intended to characterize<br />
airspace and/or aircraft operating in airspace, and the level of separation service<br />
applicable.<br />
In 1996, a white paper was prepared for the RTCA Technical <strong>Management</strong> Committee on<br />
RSP (Nakamura and Schwab, 1996). This paper was endorsed by the RTCA group, and<br />
was the basis for the coordinated development of RSP across several existing RTCA<br />
20
Change language