Contact

Post:

AERONAUTICAL INFORMATION SERVICES
CIVIL AVIATION AUTHORITY OF MALAYSIA
NO. 27, PERSIARAN PERDANA
LEVEL 1-4, PODIUM BLOCK, PRECINCT 4,
62618 PUTRAJAYA
MALAYSIA

Tel: 6-03-8871 4000

Fax: 6-03-8881 0530

AFS: WMKKYAYS

Email: ais@dca.gov.my

URL: aip.dca.gov.my

AIP Supplement for Malaysia

AIP SUP

08/2018

Effective from 03 JAN 2019

to PERM

Published on 25 OCT 2018

  KUALA LUMPUR FLIGHT INFORMATION REGION
IMPLEMENTATION OF PERFORMANCE-BASED
COMMUNICATION AND SURVEILLANCE (PBCS)

1  INTRODUCTION

1.1  This AIP Supplement is to notify the aviation industry of the implementation of Performance-Based Communication and Surveillance (PBCS) in the Bay of Bengal area within Kuala Lumpur FIR in accordance with the ICAO provisions to support Performance-Based reduced horizontal separation minima application using data link with effect from 3 January 2019 0000UTC.

1.2  PBCS is a concept that enables the management of communication and surveillance capabilities by prescription of Required Communication Performance (RCP) and Required Surveillance Performance (RSP) specifications in Future Air Navigation System (FANS 1/A) data link operations using the Automatic Dependent Surveillance-Contract (ADS-C) and Controller Pilot Data-link Communications (CPDLC).

1.3  Pursuant to the ICAO Provisions and amendments to Annexes 4, 6 (Parts I, II, III), 10 (Volumes II, III), 11, 15, PANS-ATM (Doc 4444) and PANS-ABC (Doc 8400) on PBCS, including new Standards and Recommended Practices (SARPS) and related guidance material, Performance-Based Communication and Surveillance (PBCS) Manual (Doc 9869 2nd Edition) and Global Operational Data Link (GOLD) Manual (Doc 10037 1st Edition), are applicable from 10 November 2016.

2  PBCS FRAMEWORK

2.1  The PBCS concept provides a framework to apply RCP and RSP specifications to ensure the acceptable communication and surveillance capabilities and performance of an operational system.

2.2  The main components that involve the joint participation from States, ANSPs and aircraft operators under the PBCS implementation framework consists of the following:

  1. To prescribe RCP and RSP specifications, for aircraft operators, aircraft systems and infrastructure supporting datalink operations, when applying separations predicated on such performance;

  2. Operational approval of aircraft operators for a communication and / or surveillance capability including aircraft equipage for operations where RCP and / or RSP specifications will have to be prescribed;

  3. Indication of an aircraft’s communication and surveillance performance capability in the form of RCP / RSP specifications in the flight plan; and

  4. Monitoring programmes to assess actual communication and surveillance performance against RCP and RSP specifications and to determine corrective action to report, analyse and resolve problems.

3  OPERATOR AND AIRCRAFT SYSTEMS

3.1  Operator should continue to use CPDLC and ADS−C in accordance with policies established by the State of Registry or State of the Operator.

3.2  Operator obtaining approval in accordance with National regulations (State of the Operator or State of Registry) should ensure that the procedures, system and services in operations and maintenance programs meet the allocated criteria interoperability standards and RCP / RSP specifications.

3.3  Establish the necessary training and qualification programs for flight crews and flight operations officers / dispatchers in preparation for PBCS implementation that is consistent with ICAO Annex 1 and Annex 6.

3.4  Initial compliance to the PBCS requirements would be beneficial to establish the confidence that Air Traffic Management (ATM) operations could be provided only to eligible aircraft. The PBCS concept will enhance the safety on Performance-Based reduced horizontal separation minima application using data link in Air Traffic Service (ATS) operations.

4  SEPARATION MINIMA

4.1  A Performance-Based Longitudinal Separation minima of 50NM may be applied between RNP10 approved aircraft on ATS routes N571, P574, P627, L645, P628 and L510 which either LOGON to CPDLC or are within VHF radio range as the primary means of communication.

4.2  RCP240 and RSP180 performance specifications shall be required for the application of the Performance-Based Longitudinal Separation minima in Para 4.1 which is in accordance with PANS-ATM (Doc 4444) paragraph 5.4.2.9.2.

4.3  Otherwise, longitudinal separation of 10 minutes between RNAV equipped aircraft applying Mach Number Technique (MNT) separation minima may be applied between aircraft in situation where RCP240 / RSP180 performance requirement could not be complied.

5  FLIGHT PLAN REQUIREMENTS

5.1  Existing requirement for aircraft using data link communications to annotate in their ICAO flight plan according to AIP Malaysia page ENR 1.1.13.8 paragraph 1.1.13.8.1 remain unchanged.

5.2  Operators conducting flights in airspace where separations are dependent on PBCS should start using RCP / RSP indicators in the flight plan and to adhere to the provisions stated in Appendix 2 of PANS-ATM (Doc 4444).

5.3  Aircraft planning to utilise PBCS operation within the designated area stipulated in this AIP Supplement must annotate in their ICAO flight plan as follows:

  1. In Item 10a of the flight plan, the operator should insert one or more of the CPDLC equipment and capabilities descriptors, as appropriate, listed in Table 1 to identify an aircraft’s data link equipment and capabilities:

    CPDLC equipment and capabilitiesDescriptor
    CPDLC ATN VDL Mode 2 (ATN B1)J1
    CPDLC FANS 1/A HFDLJ2
    CPDLC FANS 1/A VDL Mode 0/AJ3
    CPDLC FANS 1/A VDL Mode 2J4
    CPDLC FANS 1/A SATCOM (INMARSAT)J5
    CPDLC FANS 1/A SATCOM (MTSAT)J6
    CPDLC FANS 1/A SATCOM (Iridium)J7

    Table 1: CPDLC equipment and capabilities descriptor

  2. In Item 10a of the flight plan also, the aircraft operator should insert one or more descriptors, as appropriate, listed in Table 2, to identify an aircraft’s RCP capability:

    Aircraft’s RCP capabilityDescriptor
    CPDLC RCP 400P1
    CPDLC RCP 240P2
    SATVOICE RCP 400P3

    Table 2: Aircraft’s RCP capability descriptor

  3. In Item 10b of the flight plan, the operator should insert one or more of the ADS-C equipment and capabilities descriptors, as appropriate, listed in Table 3 to identify an aircraft’s data link equipment and capabilities:

    ADS-C equipment and capabilitiesDescriptor
    ADS-C with FANS 1/A capabilitiesD1
    ADS-C with ATN capabilitiesG1

    Table 3: ADS-C equipment and capabilities descriptor

  4. In Item 18 of the flight plan, the aircraft operator should file the RSP capability by inserting the indicator SUR/ followed by the appropriate designator, WITH NO SPACES, for the RSP specification (e.g. SUR/RSP400 or SUR/RSP180).

  5. In Item 18 of the flight plan also, the operator should insert the following other information relevant to CPDLC and ADS-C equipment and capabilities:

    1. the indicator REG/ followed by the aircraft registration, WITH NO SPACES; and

    2. the indicator CODE/ followed by the aircraft address, WITH NO SPACES expressed in the form of an alphanumerical code of six hexadecimal characters.

5.4  Guidance material on the application of performance-based communication and performance-based surveillance, which prescribes RCP / RSP to an air traffic service in a specific area, is contained in the Performance-Based Communication and Surveillance (PBCS) Manual (Doc 9869 2nd Edition).

6  CONSULTATIONS

6.1  All enquiries to be address to nasuruddin@caam.gov.my.

7  CANCELLATION

7.1  This AIP Supplement will remain current until the information is published in AIP Malaysia.

7  - END -