local operating procedures efes acc - vatsim...

27
[Nyckelord] 2013 LOCAL OPERATING PROCEDURES (LOP) TAMPERE ACC (EFES)

Upload: doanh

Post on 24-Mar-2018

244 views

Category:

Documents


5 download

TRANSCRIPT

Page 1: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

[Nyckelord]

2013

LOCAL OPERATING PROCEDURES (LOP) TAMPERE ACC (EFES)

Page 2: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

1

1 Position list

Tampere ACC

VATSIM name Callsign Frequency Abbreviation Remarks

EFES_1_CTR Tampere Radar 132.670 EFES-1

EFES_2_CTR Tampere Radar 121.300 EFES-2

EFES_3_CTR Tampere Radar 127.100 EFES-3

EFES_4_CTR Tampere Radar 132.320 EFES-4

EFES_5_CTR Tampere Radar 135.520 EFES-5

EFES_6_CTR Tampere Radar 124.200 EFES-6

EFES_7_CTR Tampere Radar 126.100 EFES-7

EFES_X_CTR Tampere Radar 132.720 EFES-X Spare frequency for sectors 1-5

EFES_Y_CTR Tampere Radar 123.850 EFES-Y Spare frequency for sectors 6-7

EFES_L_APP Tampere Radar 124.070 EFES-L LAKUT feeder

EFES_O_APP Tampere Radar 123.770 EFES-O OKLOR feeder

EFES_P_APP Tampere Radar 127.500 EFES-P PEXEN feeder

Other Finland FIR APP and TWR positions

VATSIM name Callsign Frequency Abbreviation Remarks

EFET_I_TWR Enontekiö Flight Information 122.450 ET-AFIS

EFHA_APP Halli Radar 124.550 HA-APP

EFHA_TWR Halli Tower 128.900 HA-TWR

EFHF_TWR Malmi Tower 131.250 HF-TWR

EFHK_E_APP Helsinki Radar 119.100 HK-APP-E

EFHK_W_APP Helsinki Radar 129.850 HK-APP-W

EFHK_E_TWR Helsinki Tower 118.600 HK-TWR-E

EFHK_W_TWR Helsinki Tower 118.850 HK-TWR-W

EFIV_TWR /

EFIV_I_TWR

Ivalo Tower /

Ivalo Flight Information 118.000

IV-TWR /

IV-AFIS

EFJO_TWR Joensuu Tower 120.900 JO-TWR

EFJY_APP Jyväskylä Radar 127.000 JY-APP

EFJY_TWR Jyväskylä Tower 118.000 JY-TWR

EFKA_APP Kauhava Radar 130.100 KA-APP

EFKA_TWR Kauhava Tower 122.800 KA-TWR frequency same as UNICOM

EFKE_TWR Kemi Tower 119.400 KE-TWR

EFKI_I_TWR Kajaani Flight Information 118.100 KI-AFIS

EFKK_TWR Kruunu Tower 120.100 KK-TWR

EFKS_TWR /

EFKS_I_TWR

Kuusamo Tower /

Kuusamo Flight Information 118.650 KS-TWR /

KS-AFIS

Page 3: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

2

VATSIM name Callsign Frequency Abbreviation Remarks

EFKT_TWR /

EFKT_I_TWR

Kittilä Tower /

Kittilä Flight Information 118.950

KT-TWR /

KT-AFIS

EFKU_APP Kuopio Radar 130.600 KU-APP

EFKU_TWR Kuopio Tower 120.150 KU-TWR

EFLP_TWR Lappeenranta Tower 120.200 LP-TWR

EFMA_TWR Mariehamn Tower 119.600 MA-TWR

EFMI_I_TWR Mikkeli Flight Information 123.000 MI-AFIS

EFOU_APP Oulu Radar 118.150 OU-APP

EFOU_TWR Oulu Tower 124.400 OU-TWR

EFPO_APP Pori Radar 128.650 PO-APP

EFPO_TWR Pori Tower 119.250 PO-TWR

EFRO_APP Rovaniemi Radar 129.900 RO-APP

EFRO_TWR Rovaniemi Tower 118.700 RO-TWR

EFSA_I_TWR Savonlinna Flight Information 118.800 SA-AFIS

EFSI_I_TWR Seinäjoki Flight Information 123.600 SI-AFIS

EFTP_APP Pirkkala Radar 126.200 TP-APP

EFTP_TWR Pirkkala Tower 118.700 TP-TWR

EFTU_APP Turku Radar 120.470 TU-APP

EFTU_TWR Turku Tower 118.300 TU-TWR

EFUT_TWR Utti Tower 130.800 UT-TWR

EFVA_APP Vaasa Radar 125.850 VA-APP

EFVA_TWR Vaasa Tower 120.950 VA-TWR

EFVR_I_TWR Varkaus Flight Information 120.400 VR-AFIS

Tallinn FIR

VATSIM name Callsign Frequency Abbreviation Remarks

EETT_W_CTR Tallinn Control 132.500 EETT-W

BALT_CTR Baltic Control 132.320 BALT covers area if EETT not online

EETT_F_APP Tallinn Control 126.700 EETT-F INTOR feeder

EETN_APP Tallinn Radar 127.900 EETN-APP

EETN_TWR Tallinn Tower 120.600 EETN-TWR

EEKA_I_TWR Kärdla Aerodrome Information 130.400 EEKA

Sweden FIR Malmö AoR

VATSIM name Callsign Frequency Abbreviation Remarks

ESMM_5_CTR Sweden Control 128.620 ESMM-5

ESMM_6_CTR Sweden Control 128.050 ESMM-6

ESMM_7_CTR Sweden Control 124.150 ESMM-7

ESMM_Y_CTR Sweden Control 134.450 ESMM-Y

Page 4: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

3

Sweden FIR Stockholm AoR

VATSIM name Callsign Frequency Abbreviation Remarks

ESOS_1_CTR Sweden Control 118.400 ESOS-1

ESOS_3_CTR Sweden Control 131.120 ESOS-3

ESOS_4_CTR Sweden Control 118.200 ESOS-4

ESOS_6_CTR Sweden Control 132.470 ESOS-6

ESOS_F_CTR Sweden Control 124.420 ESOS-F

ESOS_K_CTR Sweden Control 131.050 ESOS-K

ESOS_N_CTR Sweden Control 132.150 ESOS-N

ESSA_E_APP Stockholm Control 126.650 ESSA

ESNU_TWR Umeå Tower 119.800 ESNU see EFES-3 LOP

ESUP_TWR Pajala Tower 118.370 ESUP

Norway FIR

VATSIM name Callsign Frequency Abbreviation Remarks

ENBD_C_CTR Bodø Control 118.550 ENBD-C

ENBD_E_CTR Bodø Control 126.700 ENBD-E

ENBD_N_CTR Bodø Control 126.450 ENBD-N

ENOR_CTR Norway Control 125.500 ENOR covers area if ENBD not online

ENKR_APP Kirkenes Approach 120.350 ENKR-APP

ENKR_TWR Kirkenes Tower 118.100 ENKR-TWR

St.Peterburg FIR

VATSIM name Callsign Frequency Abbreviation Remarks

ULLL_E_CTR Peterburg Control 135.600 ULLL-E

ULLL_N_CTR Peterburg Control 133.600 ULLL-N

ULLL_W_CTR Peterburg Control 126.900 ULLL-W

RU-NWC_FSS Northwest Russia Control 135.620 RU-NWC covers area if ULLL not online

Murmansk FIR

VATSIM name Callsign Frequency Abbreviation Remarks

ULMM_CTR Murmansk Control 132.100 ULMM

RU-NWC_FSS Northwest Russia Control 135.620 RU-NWC covers area if ULMM not online

Page 5: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

4

2 Local Operating Procedures for ACC sectors

EFES-1 Tampere ACC Sector 1

EFES_1_CTR 132.670 (EFES_2_CTR 121.300)

Sector area chart

Covered airports

EFHF and EFHK

General

The sector is bordered by ULLL to the east, EETT to the south, ESOS and ESMM to the west and sectors 2, 3,

4 and 5 to the north. The main flows of traffic are east- and westbound departures from and southwesterly

arrivals to Helsinki TMA, as well as some overflights.

Holding

The holding below is mainly used for sequencing arriving traffic to Helsinki TMA. If online, the feeder sector

EFES-P is responsible for the holding area between FL95 and FL245.

Point Inbound track

(magnetic) Turn direction Max IAS

Minimum

holding level Time

PEXEN 059° Right 230 kt FL100 1 min

Page 6: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

5

Traffic

Traffic to ESOS

- See Finland-Sweden LoA

Traffic to Helsinki TMA

- Traffic arriving at EFHF is informed of the runway in use, cleared to KUDOP and to leave KUDOP on

heading 065°.

- Traffic arriving at EFHK are informed of the runway in use and cleared for the STAR for the arrival

runway. Traffic unable to follow the STAR is cleared to KUDOP and to leave KUDOP on heading

065°.

Clearances during parallel approaches (replace “x” with the current STAR designator number):

Arrival runway STAR Clearance for non-P-RNAV aircraft APP sector

04L (1) KUDOP x B KUDOP, and leave KUDOP on heading 015° HK-APP-W

04R PEXEN x R KUDOP, and leave KUDOP on heading 065° HK-APP-E

22L PEXEN x A KUDOP, and leave KUDOP on heading 065° HK-APP-E

22R (1) KUDOP x V KUDOP, and leave KUDOP on heading 015° HK-APP-W

Note 1: the KUDOP STAR must be manually assigned.

- Traffic shall be sequenced to a flow with minimum 5 nm separation. Separate coordination is

required if this cannot be achieved.

- Traffic is transferred (normally to HK-APP-E, for parallel approaches see the above table) at or

descending to FL100 or cruise level if lower, released for turns, descent and speed control unless

otherwise coordinated.

Traffic from Helsinki TMA

- HK-APP transfers traffic direct TMA exit point, at or climbing to FL240 or cruise level if lower,

released for turns, climb and speed control unless otherwise coordinated.

Traffic to/from Turku TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via RUS VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- TU-TWR requests clearance for departing traffic into sector 1 from EFES-1.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Page 7: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

6

EFES-2 Tampere ACC Sector 2

EFES_CTR / EFES_2_CTR 121.300

Note: When no other ACC sector is online, EFES-2 covers all ACC-sectors. If no other ATC position is online,

EFES-2 covers the entire Finland FIR/UIR.

Sector area chart

Covered airports

EFMA and EFTU

General

The sector is bordered by sector 1 to the south, ESOS to the west and sector 3 to the north. The main flows

of traffic are westerly and northwesterly arrivals to Helsinki TMA.

Holding

The holding below is mainly used for sequencing arriving traffic to Helsinki TMA. If online, the feeder sector

EFES-L is responsible for the holding area between FL95 and FL245.

Point Inbound track

(magnetic) Turn direction Max IAS

Minimum

holding level Time

LAKUT 075° Left 230 kt FL70 1 min

Page 8: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

7

Traffic

Traffic from Stockholm ACC to EFMA

- Traffic is coordinated with and transferred to MA-TWR

Traffic from Stockholm TMA

- See Finland-Sweden LoA

Traffic to Helsinki TMA from sector 3

- Sector 3 transfers traffic at or descending to FL210 or cruise level if lower, released for descent

unless otherwise coordinated.

Traffic to Helsinki TMA

- Traffic arriving at EFHF is informed of the runway in use, cleared to MAROM and to leave MAROM

on heading 080°.

- Traffic arriving at EFHK are informed of the runway in use and cleared for the STAR for the arrival

runway. Traffic unable to follow the STAR is cleared to MAROM and to leave MAROM on heading

080°.

Clearances during parallel approaches (replace “x” with the current STAR designator number):

Arrival runway STAR Clearance for non-P-RNAV aircraft

04L (1) MAROM x B MAROM, and leave MAROM on heading 080°

04R (2) LAKUT x R MAROM, and leave MAROM on heading 080°

22L (2) LAKUT x A MAROM, and leave MAROM on heading 080°

22R LAKUT x V MAROM, and leave MAROM on heading 080°

Note 1: the MAROM STAR must be manually assigned.

Note 2: runway 04R/22L is not normally assigned to traffic from LAKUT.

- Traffic shall be sequenced to a flow with minimum 5 nm separation. Separate coordination is

required if this cannot be achieved.

- Traffic is transferred (to HK-APP-W if not otherwise coordinated) at or descending to FL100 or

cruise level if lower, released for turns, descent and speed control unless otherwise coordinated.

Traffic from Helsinki TMA

- HK-APP-W transfers traffic direct TMA exit point, at or climbing to FL80 or cruise level if lower,

released for turns, climb and speed control unless otherwise coordinated.

Traffic to/from Mariehamn TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via MAR VOR

Page 9: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

8

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns

and descent unless otherwise coordinated.

- MA-TWR requests clearance for departing traffic from EFES-2.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Turku TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via RUS VOR

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns, descent and speed control unless otherwise coordinated.

- TU-TWR requests clearance for departing traffic into sector 2 from EFES-2. - Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Page 10: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

9

EFES-3 Tampere ACC Sector 3

EFES_3_CTR 127.100 (EFES_2_CTR 121.300)

Sector area chart

Covered airports

EFKA, EFKK, EFPO, EFSI, EFTP and EFVA

Page 11: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

10

General

The sector is bordered by sector 4 to the east, sectors 1 and 2 to the south, ESOS to the west and sector 6

to the north. The traffic is a mix of overflights and departures and arrivals to/from the underlying airports.

Delegated Airspace

In area KVARKEN (striped area on the map) the responsibility for providing air traffic services has been

delegated to Stockholm ACC (ESOS) between FL95 and FL660.

Traffic

Traffic between VAS/VAVOS and UME at or below FL95

- Traffic is coordinated and transferred between VA-TWR/VA-APP and ESNU.

Traffic to/from Halli TMA

- Arriving traffic is informed of the runway in use.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- HA-TWR requests clearance for departing traffic into sector 3 from EFES-3.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to Helsinki TMA

- Traffic is transferred to sector 2 at or descending to FL210 or cruise level if lower, released for

descent unless otherwise coordinated.

Traffic from Helsinki TMA

- HK-APP-W transfers traffic direct TMA exit point, at or climbing to FL240 or cruise level if lower,

released for turns, climb and speed control unless otherwise coordinated.

Traffic to/from Jyväskylä TMA

- Arriving traffic is informed of the runway in use.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- JY-TWR requests clearance for departing traffic into sector 3 from EFES-3.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Page 12: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

11

Traffic to/from Kauhava TMA

- Arriving traffic is informed of the runway in use.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- KA-TWR requests clearance for departing traffic from EFES-3.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Kruunupyy TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or NDB)

via the initial approach route if available, otherwise direct to the IAF (01:ESS, 19:KRU).

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns

and descent unless otherwise coordinated.

- KK-TWR requests clearance for departing traffic from EFES-3.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Pirkkala TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via PIR VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- TP-TWR requests clearance for departing traffic into sector 3 from EFES-3.

- Departing traffic is transferred on SID or direct TMA exit point, at or climbing to the coordinated

level.

Traffic to/from Pori TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via PRI VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- PO-TWR requests clearance for departing traffic from EFES-3.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Seinäjoki FIZ

- Arriving traffic is informed of the preferred runway.

- Arriving traffic is given clearance “Cleared for descent on Seinäjoki QNH xxxx, transition level xx”.

- SI-AFIS requests clearance for departing traffic from EFES-3.

- Departing traffic is transferred direct FIZ exit point, at or climbing to the coordinated level.

Page 13: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

12

Traffic to/from Turku TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via RUS VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- TU-TWR requests clearance for departing traffic into sector 3 from EFES-3.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Vaasa TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via VAS VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- VA-TWR requests clearance for departing traffic from EFES-3.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Page 14: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

13

EFES-4 Tampere ACC Sector 4

EFES_4_CTR 132.320 (EFES_5_CTR 135.520, EFES_3_CTR 127.100, EFES_2_CTR 121.300)

Sector area chart

Covered airports

EFHA and EFJY

Page 15: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

14

General

The sector is bordered by sector 5 to the east, sector 1 to the south, sector 3 to the west and sector 6 to

the north. The main flow of traffic is overflights in the north-south direction.

Traffic

Traffic to/from Halli TMA

- Arriving traffic is informed of the runway in use.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- HA-TWR requests clearance for departing traffic into sector 4 from EFES-4.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to Helsinki TMA

- Traffic arriving at EFHF is informed of the runway in use, cleared to KUVAK and to leave KUVAK on

heading 215°. During parallel approaches at EFHK, traffic is cleared to VAKAT and to leave VAKAT

on heading 170°.

- Traffic arriving at EFHK are informed of the runway in use and cleared for the STAR for the arrival

runway. Traffic unable to follow the STAR is cleared to KUVAK and to leave KUVAK on heading 215°.

Clearances during parallel approaches (replace “x” with the current STAR designator number):

Arrival runway STAR Clearance for non-P-RNAV aircraft APP sector

04L (1) KUVAK x B KUVAK, and leave KUVAK on heading 240° HK-APP-W

04R OKLOR x R KUVAK, and leave KUVAK on heading 185° HK-APP-E

22L OKLOR x A VAKAT, and leave VAKAT on heading 170° HK-APP-E

22R OKLOR x V OKLOR, and leave OKLOR on heading 230° HK-APP-W

Note 1: the KUVAK STAR must be manually assigned.

- Traffic shall be sequenced to a flow with minimum 5 nm separation. Separate coordination is

required if this cannot be achieved.

- Traffic is transferred (normally to HK-APP-E, for parallel approaches see the above table) at or

descending to FL100 or cruise level if lower, released for turns, descent and speed control unless

otherwise coordinated.

Traffic from Helsinki TMA

- HK-APP-W transfers traffic at or climbing to FL240 or cruise level if lower, released for turns, climb

and speed control unless otherwise coordinated.

Page 16: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

15

Traffic to/from Jyväskylä TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via LNE VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- JY-TWR requests clearance for departing traffic into sector 4 from EFES-4.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Pirkkala TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via PIR VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- TP-TWR requests clearance for departing traffic into sector 4 from EFES-4.

- Departing traffic is transferred on SID or direct TMA exit point, at or climbing to the coordinated

level.

Page 17: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

16

EFES-5 Tampere ACC Sector 5

EFES_5_CTR 135.520 (EFES_4_CTR 132.320, EFES_3_CTR 127.100, EFES_2_CTR 121.300)

Sector area chart

Covered airports

EFJO, EFKU, EFLP, EFMI, EFSA, EFUT and EFVR

Page 18: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

17

General

The sector is bordered by ULLL to the east, sector 1 to the south, sector 4 to the west and sector 6 to the

north. The traffic is a mix of overflights and departures and arrivals to/from the underlying airports.

Holding

The holding below is mainly used for sequencing arriving traffic to Helsinki TMA. If online, the feeder sector

EFES-O is responsible for the holding area between FL95 and FL245.

Point Inbound track

(magnetic) Turn direction Max IAS

Minimum

holding level Time

OKLOR 210° Right 230 kt FL100 1 min

Traffic

Traffic to Helsinki TMA

- Traffic arriving at EFHF is informed of the runway in use, cleared to KUVAK and to leave KUVAK on

heading 215°. During parallel approaches at EFHK, traffic is cleared to VAKAT and to leave VAKAT

on heading 170°.

- Traffic arriving at EFHK are informed of the runway in use and cleared for the STAR for the arrival

runway. Traffic unable to follow the STAR is cleared to KUVAK and to leave KUVAK on heading 215°.

Clearances during parallel approaches (replace “x” with the current STAR designator number):

Arrival runway STAR Clearance for non-P-RNAV aircraft APP sector

04L (1) KUVAK x B KUVAK, and leave KUVAK on heading 240° HK-APP-W

04R OKLOR x R KUVAK, and leave KUVAK on heading 185° HK-APP-E

22L OKLOR x A VAKAT, and leave VAKAT on heading 170° HK-APP-E

22R OKLOR x V OKLOR, and leave OKLOR on heading 230° HK-APP-W

Note 1: the KUVAK STAR must be manually assigned.

- Traffic shall be sequenced to a flow with minimum 5 nm separation. Separate coordination is

required if this cannot be achieved.

- Traffic is transferred (normally to HK-APP-E, for parallel approaches see the above table) at or

descending to FL100 or cruise level if lower, released for turns, descent and speed control unless

otherwise coordinated.

Traffic from Helsinki TMA

- HK-APP-E transfers traffic at or climbing to FL240 or cruise level if lower, released for turns, climb

and speed control unless otherwise coordinated.

Page 19: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

18

Traffic to/from Joensuu TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via JNS VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns

and descent unless otherwise coordinated.

- JO-TWR requests clearance for departing traffic from EFES-5.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Kuopio TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via VEH VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- KU-TWR requests clearance for departing traffic from EFES-5.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Lappeenranta TMA

- Arriving traffic is informed of the runway in use.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns

and descent unless otherwise coordinated.

- LP-TWR requests clearance for departing traffic from EFES-5.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Mikkeli FIZ

- Arriving traffic is informed of the preferred runway.

- Arriving traffic is given clearance “Cleared for descent on Mikkeli QNH xxxx, transition level xx”.

- MI-AFIS requests clearance for departing traffic from EFES-5.

- Departing traffic is transferred direct FIZ exit point, at or climbing to the coordinated level.

Traffic to/from Utti TMA

- Arriving traffic is informed of the runway in use.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns

and descent unless otherwise coordinated.

- UT-TWR requests clearance for departing traffic from EFES-5.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Page 20: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

19

Traffic to/from Savonlinna FIZ

- Arriving traffic is informed of the preferred runway.

- Arriving traffic is given clearance “Cleared for descent on Savonlinna QNH xxxx, transition level xx”.

- SA-AFIS requests clearance for departing traffic from EFES-5.

- Departing traffic is transferred direct FIZ exit point, at or climbing to the coordinated level.

Traffic to/from Varkaus FIZ

- Arriving traffic is informed of the preferred runway.

- Arriving traffic is given clearance “Cleared for descent on Varkaus QNH xxxx, transition level xx”.

- VR-AFIS requests clearance for departing traffic from EFES-5.

- Departing traffic is transferred direct FIZ exit point, at or climbing to the coordinated level.

Page 21: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

20

EFES-6 Tampere ACC Sector 6

EFES_6_CTR 124.200 (EFES_3_CTR 127.100, EFES_2_CTR 121.300)

Sector area chart

Covered airports

EFKE, EFKI, EFKS, EFOU and EFRO

Page 22: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

21

General

The sector is bordered by ULLL to the east, sectors 3, 4 and 5 to the south, ESOS to the west and sector 7 to

the north. The traffic is mostly departures and arrivals to/from the underlying airports.

Area SANTA

Area SANTA (shaded light grey area west of EFRO on the map) can be delegated to another unit (EFES-7,

EFES-Y or RO-APP) if the traffic situation requires.

Traffic

Traffic to/from Stockholm ACC

- See Finland-Sweden LoA

Traffic to/from Kajaani FIZ

- Arriving traffic is informed of the preferred runway.

- Arriving traffic is given clearance “Cleared for descent on Kajaani QNH xxxx, transition level xx”.

- KI-AFIS requests clearance for departing traffic from EFES-6.

- Departing traffic is transferred direct FIZ exit point, at or climbing to the coordinated level.

Traffic to/from Kuusamo TMA/FIZ

- TWR open:

o Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival

runway. Traffic unable to follow the STAR is cleared to the IAF for the conventional

approach (ILS or VOR) via the initial approach route if available, otherwise via KLA VOR.

o Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for

turns and descent unless otherwise coordinated.

- AFIS open:

o Arriving traffic is informed of the preferred runway.

o Arriving traffic is given clearance “Cleared for descent on Kuusamo QNH xxxx, transition

level xx”.

- KS-TWR/AFIS requests clearance for departing traffic from EFES-6.

- Departing traffic is transferred direct TMA/FIZ exit point, at or climbing to the coordinated level.

Page 23: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

22

Traffic to/from Kemi TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or NDB)

via the initial approach route if available, otherwise direct to the IAF (18:KEM, 36:AS).

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns

and descent unless otherwise coordinated.

- KE-TWR requests clearance for departing traffic from EFES-6.

- Departing traffic is transferred direct TMA exit point, at or climbing to the coordinated level.

Traffic to/from Oulu TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via OUK VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- OU-TWR requests clearance for departing traffic from EFES-6.

- Departing traffic is transferred on SID or direct TMA exit point, at or climbing to the coordinated

level.

Traffic to/from Rovaniemi TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via ROI VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- RO-DEL requests clearance for departing traffic into sector 6 from EFES-6.

- Departing traffic is transferred on SID or direct TMA exit point, at or climbing to the coordinated

level.

Page 24: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

23

EFES-7 Tampere ACC Sector 7

EFES_7_CTR 126.100 (EFES_6_CTR 124.200, EFES_3_CTR 127.100, EFES_2_CTR 121.300)

Sector area chart

Covered airports

EFET, EFIV and EFKT

Page 25: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

24

General

The sector is bordered by ULMM to the east, sector 6 to the south, ESOS to the west and ENBD to the

north. The traffic is mostly departures and arrivals to/from the underlying airports.

Delegated Airspace

In area HALTI (western striped area on the map) the responsibility for providing air traffic services has been

delegated to Bodø ACC (ENBD) between FL95 and FL660.

In area MANTO (eastern striped area on the map) the responsibility for providing air traffic services has

been delegated to Bodø ACC (ENBD) between FL65 and FL660.

Holding

The en-route holdings below are mainly used for sequencing arriving traffic to Kittilä (EFKT).

Point Inbound track

(magnetic) Turn direction Max IAS

Minimum

holding level Time

BISRO 332° Right 230 kt FL100 1 min

OBIRO 346° Right 230 kt FL100 1 min

Traffic

Traffic to/from Bodø ACC

- See Finland-Bodø LoA

Traffic to/from Stockholm ACC

- See Finland-Sweden LoA

Traffic to/from Enontekiö FIZ

- Arriving traffic is informed of the preferred runway.

- Arriving traffic is given clearance “Cleared for descent on Enontekiö QNH xxxx, transition level xx”.

- ET-AFIS requests clearance for departing traffic from EFES-7.

- Departing traffic is transferred direct FIZ exit point, at or climbing to the coordinated level.

Page 26: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

25

Traffic to/from Ivalo TMA/FIZ

- TWR open:

o Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival

runway. Traffic unable to follow the STAR is cleared to the IAF for the conventional

approach (ILS or NDB) via the initial approach route if available, otherwise direct to the IAF

(04:TOL, 22, AKU).

o Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for

turns and descent unless otherwise coordinated.

- AFIS open:

o Arriving traffic is informed of the preferred runway.

o Arriving traffic is given clearance “Cleared for descent on Ivalo QNH xxxx, transition level

xx”.

- IV-TWR/AFIS requests clearance for departing traffic from EFES-7.

- Departing traffic is transferred direct TMA/FIZ exit point, at or climbing to the coordinated level.

Traffic to/from Kittilä TMA/FIZ

- TWR open:

o Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival

runway. Traffic unable to follow the STAR is cleared to the IAF for the conventional

approach (ILS or LOC) via the initial approach route if available, otherwise direct KIT NDB.

o Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for

turns and descent unless otherwise coordinated.

- AFIS open:

o Arriving traffic is informed of the preferred runway.

o Arriving traffic is given clearance “Cleared for descent on Kittilä QNH xxxx, transition level

xx”.

- KT-TWR/AFIS requests clearance for departing traffic from EFES-7.

- Departing traffic is transferred direct TMA/FIZ exit point, at or climbing to the coordinated level.

Traffic to/from Rovaniemi TMA

- Arriving traffic is informed of the runway in use and cleared for the STAR for the arrival runway.

Traffic unable to follow the STAR is cleared to the IAF for the conventional approach (ILS or VOR)

via the initial approach route if available, otherwise via ROI VOR.

- Arriving traffic is transferred at or descending to FL100 or cruise level if lower, released for turns,

descent and speed control unless otherwise coordinated.

- RO-DEL requests clearance for departing traffic into sector 7 from EFES-7.

- Departing traffic is transferred on SID or direct TMA exit point, at or climbing to the coordinated

level.

Page 27: Local Operating Procedures EFES ACC - Vatsim …vatsim-scandinavia.org/wp-content/uploads/2012/12/Vatsim... · EFES_CTR / EFES_2_CTR 121.300 Note: When no other ACC sector is online,

Local Operating Procedures (LOP)

Tampere ACC (EFES)

26

3 Revision history

Date Amendment

5.12.2013 first release