VACC Estonia - Letter of Agreements. ATCC Tallinn - APP Helsinki/ACC Finland. Letter of Agreement ATCC Tallinn - APP Helsinki/ACC Finland

Transcription

1 Letter of Agreement

2 1. General 1.1 Purpose The purpose of the Letter of Agreement is to define the coordination procedures to be applied between ATCC Tallinn and APP Helsinki/ACC Finland when providing ATS to General Air Traffic (IFR/VFR) and/or Operational Air Traffic. These procedures are supplementary to those specified in ICAO, Eurocontrol and/or National documents. 1.2 Definitions for General Air Traffic and Operational Air Traffic General Air Traffic All flights which are conducted in accordance with the rules and provisions of ICAO and/or the national civil aviation regulations and legislation Operational Air Traffic Flights which do not comply with the provisions stated for GAT and for which rules and procedures have been specified by appropriate authorities. 1.3 Operational Status Both Centres shall keep each other adviced of any changed in the operational status of their facilities and navigational aids which may affect the procedures specified in this Letter of Agreement. 1.4 Distribution All operationally significant information and procedures specified in this Letter of Agreement shall be distributed by the appropriate means to all concerned controllers. 1.5 Validity This letter of agreement becomes effective on Mark-Julius Pikat Director Estonia VACC Magnus Gustafsson Director Finland FIR of VATSIM Scandinavia

3 2. Areas of Responsibility and Delegation of the Responsility for the Provision of ATS 2.1 Areas of Responsibility The lateral and vertical limits of the respective areas of responsibility as as follows: ATCC Tallinn Lateral limits: Ref. AIP ESTONIA Vertical limits: Ref. AIP ESTONIA ICAO airspace classification for the area of responsibility of ATCC Tallinn along the common boundary of the areas of responsibility of ATCC Tallinn and APP Helsinki/ACC Finland, is described in Part 3 to this Letter of Agreement ACC Finland/APP Helsinki Lateral limits: Ref. AIP FINLAND Vertical limits: Ref. AIP FINLAND ICAO airspace classification for the area of responsibility of APP Helsinki/ACC Finland along the common boundary of the areas of responsibility of APP Helsinki/ACC Finland and ATCC Tallinn, is described in Part 3 to this Letter of Agreement. 2.2 Delegation of the Responsibility for the Provision of ATS Delegation for ATS from ACC Tallinn to APP Tallinn Within the lateral limits of Tallinn TMA between FL95 and FL115 the provision of ATS is delegated from ACC Tallinn to APP Tallinn.

4 3. Area of Common Interest 3.1 Airspace Structure within the Area of Common Interest Tallinn FIR * Note: Airspace between FL95-FL115 delegated from EETT ACC to EETN APP Finland FIR Area Vertical limits Airspace Classification FIR FL660 UNL G FL95 FL660 GND FL95 CTA FL95 FL 660 C INTOR FEEDER FL 95 * FL245 C EETN TMA (20NM) 1700 FT FL 95 C EETN TMA (20NM+) 3500 FT FL 95 * C Area Vertical limits Airspace Classification FIR FL660 UNL G FL95 FL660 GND FL95 EFHK TMA UPPER 2500 FT FL285 C EFHK TMA LOWER 1300 FT FT C 3.2 Special Areas within the Area of Common Interest Special areas in Finland FIR which are situated close to the border to Tallinn FIR: EF R21, 30, 35, 37, 64A, 64B, 65, 66, 67, 75, 76, 77, 101, 102, 103, 104, 105, 106, 107 EF D101, 102, 103, 104, 105, 106, 107, 139A, 139B The lateral and vertical limits are published in the AIP Finland. The planned activation times of the danger areas are published by NOTAM. 3.3 Non-published COPs: HELTN N E C G C G

5 4. Procedures for Coordination 4.1 ATS-Routes, Coordination Points and Flight Level Allocation Available ATS-routes, COPs to be used and flight level allocation to be applied, unless otherwise described in para Flights from ACC/APP Tallinn to ACC Finland ATS-Route COP Flight Level Allocation Special Conditions L732 M612 P855 Y95 M611 M857 P854 M854 M983 P733 Q22 Y119 Y267 L77 N609 Y96 Y121 Y158 P608 Y97 DOBAN BALTI MOHNI PETOT OSTOT ODD Flights from ACC/APP Tallinn to APP Helsinki ATS-Route COP Flight Level Allocation Special Conditions L732 M612 P855 Y95 DOBAN M611 M857 P854 BALTI ODD Not available ADES EFHK/EFHF

6 L56 M611 M857 P171 M854 M983 P733 Q22 Y119 Y267 INTOR MOHNI ODD Mandatory for: All traffic with ADES EFHK/EFHF Traffic departing from EETN/EEEI TLL DCT HEL HELTN ODD See Note Flights from ACC Finland to ACC/APP Tallinn ATS-Route COP Flight Level Allocation Special Conditions L732 P855 P870 DOBAN ODD P739 M611 M857 P854 M854 M983 BALTI Not available ADES EETN MOHNI ODD Not available ADEP EFHK M851 OSTOT ODD N609 PETOT ODD Flights from APP Helsinki to ACC/APP Tallinn ATS-Route COP Flight Level Allocation P855 DOBAN ODD L732 P739 P870 M611 M857 P854 DOBAN BALTI M854 MOHNI ODD Special Conditions Mandatory for EFHF/EFHK directing to Tallinn FIR Not available for ADES EETN

7 EFHK/EFHF to EETN/EEEI RENKU Mandatory for EFHK/EFHF with ADES EETN/EEEI HEL DCT TLL HELTN See Note1 Note1: COP HELTN to be used only after verbal coordination.

8 4.2 Special Procedures Flights from ACC/APP Tallinn to ACC Finland/APP Helsinki Traffic departing from EETN or EEEI Flights departing from EETN and EEEI are given clearance to FL 280, or requested flight level if lower. Flights departing from EETN or EEEI with destination EFHK or EFHF, are given clearance to FL 110 or requested flight level if lower. Traffic with destination EFHK or EFHF Flights with destination EFHK or EFHF and cruising level above FL 120 shall be given clearance to descend to FL 120 by ACC Tallinn, unless otherwise requested. Traffic with destination EFHK or EFHF shall not be allowed to cross EFHK TMA boundary above FL 280. If the air situation does not permit the aircraft to follow the rule, additional coordination with ACC Finland shall be conducted for entering the AoR of ACC Finland. Flights departing from EETN and entering EFHK TMA are given clearance to FL 110 or requested flight level if lower. During parallel operations at EFHK, APP/ACC Tallinn shall clear the aircraft to RWY 04R or 22L. ACC/APP Tallinn clears P-RNAV-capable aircraft arriving in EFHK to follow RNAV STAR route serving the runway in use. ACC/APP Tallinn clears the Non-P-RNAV capable aircraft to leave IAF INTOR on heading 015, if not otherwise informed by EFHK APP. If RNAV STAR s are not available due to technical or such reasons, aircraft are cleared as Non-P-RNAV capable aircraft. In case of holding pattern or linear holding at IAF INTOR and the IAS of the aircraft is below 230 kts, ACC/APP Tallinn shall clear aircraft to leave INTOR with IAS 230 kts, depending on the performance of the aircraft. In case the arriving aircraft has been assigned IAS kts, it is not necessary to coordinate the assigned speed with EFHK APP.

9 4.2.2 Flights from ACC Finland/APP Helsinki to ACC/APP Tallinn Traffic with destination EETN or EEEI Flights with destination EETN or EEEI cruising level above FL100 shall be given clearance to descend to FL100. Traffic from EFHK TMA Flights with destination EETN shall not be allowed to cross Tallinn/Finland FIR boundary above FL110. If the air situation does not permit the aircraft to follow the rule, additional co-ordination with ACC Tallinn shall be conducted for entering the AoR of ACC Tallinn. APP Tallinn shall inform EFHK APP the runway in use in Tallinn. APP Helsinki clears P-RNAV capable aircraft arriving in EETN to follow RNAV STAR route serving the runway in use. If RNAV STAR s are not available due to technical or such reasons, aircraft are cleared as Non-P-RNAV capable aircraft. EFHK APP shall clear without coordination Non-P-RNAV capable aircraft with destination EETN to leave: DOBAN: heading 180, if RWY 08 is in use, RENKU: heading 180, heading 120, if RWY 26 is in use, if not otherwise instructed by EETN APP. Flights departing from EFHK or EFHF are given clearance to FL 280, except flights with destination EETN or EEEI to FL100, or requested flight level if lower. Flights departing from EFHF or EFHF with destination not EETN or EEEI, shall not be allowed to cross Tallinn/Finland FIR boundary below FL120, except the traffic with requested FL110 or below. If the air situation does not permit the aircraft to follow the rule, additional co-ordination with APP Tallinn shall be conducted for entering the AoR of APP Tallinn. Flights departing from EFHK or EFHF shall not be allowed to cross Tallinn/Finland FIR boundary above FL280. If the air situation does not permit the aircraft to follow the rule, additional co-ordination with ACC Finland shall be conducted for entering the AoR of ACC Finland.

10 4.3 Coordination of Status of Special Areas in the Area of Common Interest APP Helsinki shall inform ATCC Tallinn the actual activation times of the following areas: EF R21, 30, 35, 37, 64A, 64B, 65, 66, 67, 75, 76, 77, 101, 102, 103, 104, 105, 106, 107 EF D101, 102, 103, 104, 105, 106, 107, 139A, 139B. Tallinn ATCC will be notified the activation of a Special Areas by NOTAM.

11 5. Transfer of Control and Communications The transfer of control takes place at the AoR-boundary. The transfer of communications shall take place not later than the transfer of control. Unit Sector Callsign Frequency ACC Finland Sector A Sector B EFES_A_CTR EFES_D_CTR EFES_B_CTR EFES_C_CTR EFES_D_CTR Unit Sector Callsign Frequency EFHK_APP APP Helsinki EFHK_W_APP EFES_A_CTR EFES_D_CTR Unit Sector Callsign Frequency ACC Tallinn Sector W EETT_W_CTR EETT_E_CTR Kärdla AFIS* EEKA_I_TWR Sector E EETT_E_CTR EETT_W_CTR EETT_F_APP INTOR Feeder EETT_W_CTR EETT_E_CTR Unit Sector Callsign Frequency EETN_APP APP Tallinn EETT_W_CTR EETT_E_CTR *Kärdla AFIS is located in Sector W. Airspace is Class G+ (Two-way communication)

12 6. Radar Based Coordination Procedures 6.1 SSR Code Assignment Both Centres shall transfer aircraft on verified discrete SSR codes. Any change of SSR code by the accepting Centre may only take place after the transfer of control point. 6.2 General Radar Coordination Procedures If it becomes necessary to reduce or suspend radar transfers, a 5 minutes prior notification will be observed, except in emergency situations. Radarvectoring may take place without coordination between units provided the distance to the boundary of the AoR/FIR is never less than 2,5 NM, except 5 NM to the boundary of INTOR Feeder sector. ACC Tallinn may vector aircraft inside IAF INTOR Feeder sector to the boundary. 6.3 Transfer of Radar Control Transfer of radar control may be effected after prior coordination provided the minimum distance between the aircraft does not fall below 5 NM between ACC Tallinn or APP Tallinn and ACC Finland or APP Helsinki APP Helsinki shall apply 5NM radar separation minima in Tallinn FIR 6.4 Silent Transfer of Radar Control Transfer of radar control may be effected after prior coordination provided the minimum distance between the aircraft is 6 NM between aircraft from APP/ACC Tallinn to APP Helsinki and the ground speed (GS) or the succeeding aircraft is no more than 30 kts faster than the ground speed of the first aircraft, 7 NM between aircraft from APP EFHK to APP/ACC Tallinn and is constant or increasing, or 10 NM between aircraft from APP EFHK to APP/ACC Tallinn and the ground speed (GS) of the succeeding aircraft is no more than 30 kts faster than the ground speed of the first aircraft 10 NM between ACC/APP Tallinn and ACC Finland and the ground speed (GS) of the succeeding aircraft is no more than 30 kts faster than the ground speed of the first aircraft.