Name:
ICAO 9869 PDF
Published Date:
01/01/2017
Status:
[ Active ]
Publisher:
International Civil Aviation Organization
SCOPE AND PURPOSE
This manual provides guidance and information concerning PBCS operations and is intended to facilitate the uniform application of the SARPs contained in Annex 6, Annex 11, Annex 15, PANS-ATM (Doc 4444), PANS-ABC (Doc 8400) and, when necessary, the Regional Supplementary Procedures (Doc 7030).
This guidance material is also intended to improve safety and maximize operational benefits by promoting the PBCS concept and its general application to diverse and emerging technologies for communication and surveillance supporting ATM operations. The PBCS concept provides a framework for managing communication and surveillance performance in accordance with globally accepted RCP and RSP specifications.
The RCP and RSP specifications included are intended initially for automatic dependent surveillance — contract (ADS-C), controller-pilot data link communications (CPDLC) and satellite voice (SATVOICE) communications supporting ATM operations in airspace, where procedural separations are being applied. However, the PBCS concept allows for new RCP and RSP specifications for other purposes. For example, the manual could be updated to include a new RSP specification that is intended for automatic dependent surveillance – broadcast (ADS-B) supporting an ATM operation.
This second edition, formerly the Manual on Required Communication Performance (RCP), was restructured as follows:
a) Background information, purpose of the manual and explanation of terms was moved from Chapter 1 to the “Foreword”.
b) Chapter 1 was renamed from “Introduction” to “Performance-based communication and surveillance (PBCS) concept”. This chapter provides information on the PBCS concept, including differences with performance-based navigation (PBN); the relationship of the PBCS concept to State safety management responsibilities; the PBCS framework; RCP and RSP specifications supporting ATM operations; and developing, applying and complying with an RCP/RSP specification.
c) Chapter 2 was renamed from “Overview of RCP” to “Developing an RCP/RSP specification”. This chapter provides guidance on developing an RCP/RSP specification, which includes operational criteria in terms of RCP/RSP times; RCP/RSP continuity; RCP/RSP availability; RCP/RSP integrity and associated functional and safety requirements; and allocations to different components of the system.
d) Chapter 3 was renamed from “Determining an RCP type” to “Applying an RCP/RSP specification”. This chapter provides guidance on applying an RCP/RSP specification, which includes the prescription of the communication and surveillance capability supporting specific ATM operations in specific airspace, associated operational approvals, and post-implementation monitoring.
e) Chapter 4 was renamed from “Prescribing an RCP type” to “Complying with an RCP/RSP specification”. This chapter provides guidance on establishing policies, procedures and criteria for State approvals and on complying with an RCP/RSP specification, which includes: initial compliance determination and State approvals for aircraft systems; air navigation services provider (ANSP) systems and aircraft operators; flight plan requirements; and continued operational compliance — PBCS monitoring programmes.
f) Chapter 5, which was entitled “Complying with an RCP type”, was incorporated into the abovementioned Chapter 4.
g) Appendix A was renamed from “Glossary of terms” to “PBCS Implementation Plan — Checklist”. The glossary of terms was moved to the preliminary portion of the manual. Appendix A now includes guidance — and a checklist—that lists tasks and other aspects for consideration in the development of a local or regional PBCS implementation plan.
h) Appendix B was renamed from “Checklist for RCP application” to “RCP specifications”. The checklist was replaced by a new checklist that is contained in Appendix A. Appendix B now contains a “merged” version of the RCP specifications taken from the regional guidance material (GOLD and SVGM), Appendix B in each document. These specifications are considered a requirement when they are prescribed or guidance if applied only to PBCS monitoring programmes.
i) Appendix C was renamed from “Example of determining an RCP type” to “RSP specifications”. The example was deleted. Appendix C now contains a “merged” version of the RSP specifications taken from the regional guidance material (GOLD and SVGM), Appendix C in each document. These specifications are considered a requirement when they are prescribed or guidance if applied only to PBCS monitoring programmes.
j) A new Appendix D, “Post-implementation monitoring and corrective action (CPDLC and ADS-C),” was added. Appendix D contains the guidance on post-implementation monitoring at ANSP, regional and inter-regional levels, taken from GOLD, Appendix D. The material was simplified and is structured differently from that provided in the GOLD.
k) A new Appendix E, “Post-implementation monitoring and corrective action (SATVOICE),” was added. Appendix E contains the guidance on post-implementation monitoring at ANSP, regional and interregional levels, taken from the SVGM, Appendix D.
The following personnel and organizations should be familiar with relevant aspects of its contents: regulators, airspace planners, aircraft operators, flight operations officers/flight dispatchers, ANSPs, aeronautical stations, communication services providers (CSPs), satellite service providers (SSPs), radio operators, training organizations, regional/local monitoring entities, automation specialists and radio facilities, aircraft manufacturers and equipment suppliers.
The guidance supports the following activities:
a) States’ roles and responsibilities in relation to the following:
1) safety oversight of air navigation services;
2) operational approval (e.g. flight crew training and qualifications); and
3) design approval of aircraft data link systems;
b) development of agreements and/or contractual arrangements between ANSPs and aircraft operators and their respective CSPs;
c) development of operational procedures; and
d) operational monitoring, analysis, and exchange of operational data among appropriate entities, such as regional monitoring entities, States, ANSPs, and CSPs.
| Edition : | 2 |
| Number of Pages : | 212 |
| Published : | 01/01/2017 |