ENR 1.8  REGIONAL SUPPLEMENTARY PROCEDURES (ICAO DOC 7030)

1.8.1.  Implementation FANS 1 A Services in the SAL OCENIC FIR / UIR airspace

1.8.1.1 Introduction

On 11 / 09 / 22 FANS 1 / A services were implemented over the SAL OCENIC FIR / UIR according with the procedures and limitation described hereafter.

1.8.1.2 FANS 1 / A current limitations
1.8.1.2.1 Only a reduced set of standard CPDLC uplink messages is available (see 1.8.1.6.2). When using CPDLC the following will be observed by controllers:

  1. ATC clearances will be only provided using the standard pre - formatted messages;

  2. Multiple clearances on a single uplink pre - formatted message (e.g. level change plus direct to) are not possible. The second clearance will be provided after the reception of the WILLCO / UNABLE response to the first clearance;

  3. No conditional clearances (e.g. level change including speed restriction) will be provided by ATC;

  4. Free text messages will only be used to provide information to pilots. A ROGER response to the free text message is expected.

1.8.1.2.2 Sal FANS 1 / A system is able to accept automatic transfers of FANS 1 / A services coming from its equipped adjacent ACC‘s. Nevertheless, as the standard CPDLC message UM 160, “Next Data Authority” (NDA) is not available, pilots should not expect automatic transfers of FANS services from SAL ACC to its adjacent ACC‘s.
1.8.1.3 Safety consideration about FANS 1 / A implementation

  1. ADS - C data will never be used for operational purposes such as application of ADS - C separations between aircraft or aircraft and terrain. The application of ADS - C based separations would require extensive evaluations and agreements with adjacent ACC‘s

  2. ADS - C monitoring has to be understood as the use of ADS - C for the purpose of monitoring deviations from the nominal flight path or from the terms of ATC clearances and detecting emergencies and inconsistencies between flight plan data on board and flight plan on ground.

  3. Pilot are not released from maintaining and monitoring voice VHF / HF communication.

  4. Pilot request and controller instructions via CPDLC are only in the circumstances described on item 1.8.1.6.

  5. Requirements and operational procedures adopted are defined for reaching the highest point of compliance with FANS Operations Manual (FOM) version 6.0.

1.8.1.4 Flight planning procedures
1.8.1.4.1 The operator is responsible for correctly inserting items 10 and 18 of the ICAO flight plan according to the FANS procedures.
1.8.1.4.2 The flight plan identification used for logon must be exactly the same as the filed in the ATS flight plan.
1.8.1.5 Procedures for connection (logon) to Sal FANS 1 / A system.
1.8.1.5.1 The aircraft and operators shall be approved either by the State of operator or the State of registration prior to any ADS - C / CPDLC operation.

To avoid an automatic rejection of the logon, pilots shall ensure that the identification and registration number contained in the FN_CON message (logon), are exactly the same as the identification and registration numbers filed in the flight plan.

1.8.1.5.2 Traffic entering or overflying SAL OCENIC FIR / UIR coming from CANARIES, DAKAR and SANTA MARIA ACC‘S.

  1. For aircraft coming from airspace where FANS 1 / A services have been provided, ADS - C and CPDLC will be transferred automatically to SAL ACC (GVSC) by the ACC responsible for the adjacent FIR.

  2. If 10 minutes before reaching the common boundary point the automatic log - on with SAL ACC has not been successful, pilots shall start a manual log - on to SAL ACC, sending an AFN Contact message (FN_CON) containing the 4 character ICAO code of SAL OCENIC FIR / UIR (GVSC).

  3. Once the log - on is accepted, the controller shall established the CPDLC connection, which will remain inactive until the CPDLC connection with the transferring ACC is terminated.

  4. Immediately after the reception of the log - on, SAL ACC will established the ADS - C connection setting a 15 minutes reporting rate periodic contract and a waypoint change event contract.

  5. The transferring ACC will terminate its CPDLC connection 5 minutes prior to the common boundary point.

  6. For aircraft coming from airspace where FANS 1 / A services have not been provided, pilots are requested to perform a manual log - on to Sal FANS 1 / A system using the FN_CON message with the 4 character ICAO code of SAL OCENIC FIR / UIR (GVSC) between 15 and 45 MIN before the common boundary point.

  7. Once the log - on is accepted, the controller shall establish the CPDLC and ADS - C connections, requesting a 15 MIN reporting rate periodic contract and a waypoint change event contract.

1.8.1.5.3 Traffic departing from SAL OCENIC FIR / UIR towards CANARIES, DAKAR and SANTA MARIA ACC‘s.

  1. Traffic departing from airports inside SAL OCENIC FIR / UIR inbound to CANARIES, DAKAR and SANTA MARIA ACC‘s are requested to logon to SAL ACC FANS system before the departure using the FN_CON message containing the 4 letter ICAO code of SAL OCENIC FIR / UIR (GVSC).

  2. Once the log - on is accepted, the controller shall established the CPDLC and the ADS - C connections, requesting a 15 MIN reporting rate periodic contract and a waypoint change event contract.

1.8.1.5.4 Traffic existing from SAL ACC towards CANARIES, DAKAR and SANTA MARIA ACC‘s

  1. Between 15 and 45 MIN before reaching the common boundary point, pilots overflying or departing SAL OCENIC FIR / UIR towards CANARIES, DAKAR and SANTA MARIA ACC‘s are requested to manually logon (FN_CON) to GCCC, GOOO or LPPO respectively.

  2. SAL ACC will manually terminate the CPDLC connection to Sal FANS 1 / A system 5 MIN before reaching the common boundary point.

  3. The flight crew shall ensure that there is no active connection with SAL ACC after crossing the boundary point.

1.8.1.6 CPDLC procedures
1.8.1.6.1 CPDLC is to be used as primary mean of communication in the portion of the SAL OCENIC FIR / UIR airspace between TUTLO and the route UN 741. However, on the route UN 741 pilots connected CPDLC will be advised by controllers as soon as the flight is entering in areas were suitable VHF radio communications can be established with the ATC. The assigned VHF / HF are to be used as a secondary. In the remaining portion of SAL OCENIC FIR / UIR airspace VHF is to be used as primary mean of communication. CPDLC / HF are to be used as secondary.
1.8.1.6.2 Pilots shall only expect the following set of controller uplink CPDLC pre - formatted messages;
ROGER-CLIMB TO (Altitude)
AFFIRM-DESCENT TO (Altitude)
NEGATIVE-PROCEED DIRECT TO (Position)
STAND BY-INCREASE SPEED TO (Speed) OR GREATER
MAINTAIN (Altitude)-REDUCE SPEED TO (Speed) OR LESS
RESUME OWN NAVIGATION-PROCEED BACK ON ROUTE
CONFIRM ALTITUDE-OFFSET (Distance offset / direction) OF ROUTE
CONFIRM SPEED-REPORT PASSING (Position)
CONFIRM POSITION-CHECK STUCK MICROPHONE (Frequency)
CONFIRM HEADING-REQUEST DEFERRED
1.8.1.6.3 When using “free Test” uplink messages to provide information to pilots the following will be observed by controllers:

  1. Format and phraseology will be in accordance with the ATC standard;

  2. Non - essential words and sentences will be avoided;

  3. Abbreviations will only be included if they are in accordance with the standard ATC Phraseology.

1.8.1.6.4 Except in cases of emergency, when controller or pilot communicates via CPDLC, the response shall be via CPDLC.
1.8.1.6.5 If pilots voice response confirms the availability and quality of the voice VHF communications, from that moment, all communications will be performed by voice.
1.8.1.6.6 If pilots or controllers detect situations of poor voice communications, these communications must be performed using CPDLC.
1.8.1.6.7 In cases where CPDLC is used and, in order to avoid a potential ambiguity, pilots should avoid sending downlink multiple clearance request messages.
1.8.1.7 ADS - C procedures
1.8.1.7.1 Aircraft departing from airports inside Sal airspace or entering in SAL OCENIC FIR / UIR coming from its adjacent ACC‘s must follow the FANS connection / disconnection procedures described in 1.8.1.5.
1.8.1.7.2 In order to minimize the cost of the data communications, the amount of the ADS - C data exchange will kept to the minimum required for operational purposes.
1.8.1.7.3 The following contracts will be always established:

  1. A 15 MIN periodic contract requesting;

    1. Basic data

    2. Earth Reference Group

    3. Predicted Route Group

  2. Waypoint Change Event contract.

1.8.1.7.4 Apart from the contracts indicated above, additional event or demand contracts, as well as changes on the reporting rate of the periodic contract, can be established or modified in case of operational need.

1.8.2.  Visual flights rules (VFR) (ICAO Annex 2, 4.8)

VFR flights to be operated within a control zone established at an aerodrome serving international flights and specified portions of the associated terminal control area shall:

  1. have a two - way radio communication;

  2. obtain permission from the appropriate area traffic control unit; and

  3. report positions, as required.

Note: The phrase “specified” portions of the associated terminal control area is intended to signify at least those portions of the TMA used by international IFR flights in association with approach, holding, departure and noise abatement procedures.

1.8.3.  Special application of instrument flight rules

NIL

1.8.4.  Air traffic advisory service (PANS - RAC, Part VI, 1.4)

NIL

1.8.5.  Adherence to ATC approved route (ICAO Annex 2, 3.6.2.2)

If an aircraft has inadvertently deviated from the route specified in its ATC clearance, it shall forthwith take action to regain such route within 100 NM from the position at which the deviation was observed.