2013 LETTER OF AGREEMENT BETWEEN NORWAY FIR AND DENMARK FIR VATSIM Scandinavia July 2013 Version 2
1 General 1.1 Purpose The purpose of this Letter of Agreement (LoA) is to define the coordination procedures to be applied between when providing ATS on the VATSIM network. 1.2 Distribution All operationally significant information and procedures contained in this Letter of Agreement shall be distributed by the appropriate means to all concerned controllers. 1.3 Validity This Letter of Agreement becomes effective 08/08/2013. Morten Jelle Director Denmark FIR Daniel Klepp Director Norway FIR 2 Areas of Responsibility and Sectorisation 2.1 Areas of Responsibility 2.1.1 Norway FIR Lateral limits: Vertical limits: 2.1.2 Denmark FIR Lateral limits: Vertical limits: Norway FIR/UIR GND UNL Denmark FIR/UIR GND UNL 2.2 Sectorisation 2.2.1 Norway FIR A fictional ACC sector has been made to be able to control the whole Norway FIR in off-peak periods. The sectorization is as follows: Border to Denmark Norway Control (ENOR_CTR) ENOR_CTR 125.500 (ENOR_S_CTR 121.550) 2
Norway FIR (ENOR) is divided in several AoRs. If one of these is online they have higher priority than Norway Control. AoRs concerning Denmark are Oslo (ENOS) and Stavanger (ENSV). These are situated as follows along the Danish border: West of 5700N 00600E From 5700N 00600E To 5802N 00931E From 5802N 00931E To 582960N Area Sector Name Secondary Sectors Comments Stavanger Control Sector South ENSV_S_CTR 120.650 Oslo Control Sector 8 ENOS_8_CTR 134.350 Oslo Control Sector 4 ENOS_CTR/ ENOS_4_CTR 118.875 ENSV_CTR 124.700 ENOR_S_CTR 121.550 ENOR_CTR 125.500 ENOS_CTR/ ENOS_4_CTR 118.875 ENOS_1_CTR 118.825 ENOR_S_CTR 121.550 ENOR_CTR 125.500 ENOS_1_CTR 118.825 ENOR_S_CTR 121.550 ENOR_CTR 125.500 Border Oslo/Stavanger Border Norway/Denmark/ Sweden 2.2.2 Denmark FIR Area Sector Name Secondary Sectors Comments From 5720N 0042958E To 57N 00730E From 57N 00730E To Swedish Border EKDK_N_CTR 134.675 EKDK_V_CTR 126.055 EKDK_CTR 135.270 EKDK_CTR 135.270 Including North Sea High Area Is not split in V/UV on Vatsim Note 1: Secondary frequencies within parenthesis ( ). Note 2: For frequencies where the sixth digit is 5 (e.g. 128.625), the final 5 shall on VATSIM be substituted with a 0 (zero) due to technical limitations (e.g. 128.620). 3
3 Delegated Airspace Not Applicable 4 Procedures for Coordination 4.1 ATS Routes, Coordination Points and Flight Level Allocation Standard flight level allocation is to be used on all routes, unless otherwise described below. Note: Standard flight level allocation (in RVSM airspace) means that aircraft on eastbound routes (magnetic track 360-179 ) shall use odd flight levels and westbound flights (magnetic track 180-359 ) shall use even flight levels. 4.2 Flights from Denmark FIR to Norway FIR 4.2.1 Flights from ACC Copenhagen to ATCC Stavanger. ATS-Route Coordination Point Level Allocation P603 KARLI may be routed: LARGA dct ZOL* P613/T505 - KARLI KARLI Odd FL's Even FL's KY05 (Heli route) NORSO Odd FL's KY04 (Heli route) NOREM Even FL's KY80 (Heli route) DANOR *Provided the relevant waypoint is in the FPL-route of the aircraft, the direct track in the table may be used without prior approval request. 4
4.2.2 Flights from ACC Copenhagen to ATCC Oslo ATS-Route Coordination point Flight Level Allocation P615/Z128 P601 TR10 (tacan route) ARTOR NIROD KOTAK Direct Tracks P622/Z137 RETKA Direct tracks: T600 NERDO PIPEX to (ENGM see note 1) P621 GUNPA/VALDI/ M725 LAVKO Even FL's Westbound ORVIK/ IPTON (see note 1) P602 (CDR) AMSEV ETNOR (to ENBR Odd FL's Eastbound see note1) L621 ISVIG/GUNPA (for P990 (CDR) KOVIK traffic from ACC sector N) M609/Z704 (CDR) RASVI P614 (CDR) TB1 P992 (CDR) M604/P850 RAMUD TEKVO LINVI DANKO P619 MITSI Note 1: Direct tracks to PIPEX, GUNPA, VALDI, ORVIK, IPTON and ETNOR may be used in respect of EN D153 and OAK 5A/B (when active). 4.3 Flights from Norway FIR to Denmark FIR 4.3.1 Flights from ATCC Stavanger to ACC Copenhagen P603 KARLI may be routed: dct TIPAN* P613 ATS-Route Coordination Point KARLI Flight Level Allocation - Even FL's Odd FL's KY05 (Heli Route) NORSO Even FL's KY04 (Heli Route) NOREM KY06/KY07/KY80 DANOR (Heli Routes) * If TIPAN is in flightplan **Flights with VES in flightplan may be cleared direct VES Odd FL's 5
4.3.2 Flights from ATCC Oslo to ACC Copenhagen. ATS-Route Coordination Point Flight Level Allocation Direct Tracks P615 ARTOR T551 BINRO P601 NIROD TR10 P622 T600 P621 M725 KOTAK RETKA NERDO LAVKO Even FL's westbound Direct tracks AAL (see note 1) LOKSA (to EKBI see note 2) VES TNO L621 P990 M609/Z705 P614 / N603 AMSEV KOVIK RASVI RAMUD Odd FL's eastbound TB1 TEKVO Direct tracks P992 TIPAN (see note 1) LINVI LOKSA (to EKBI see note 2) VES L39 M604/P850 P619 Note 1: Note 2: DANKO MITSI Direct tracks to AAL and TIPAN may be used in respect of TSA Hanstholm A/B and EK D389 (when active). Direct tracks to LOKSA may be used in respect of TSA Hanstholm A/B. Aircraft coordinated via COP RAMUD shall pass the AoR-boundary via/north of RAMUD. For arriving aircraft to EKBI with FPL route via P992-LINVI, the use of direct LOKSA is subject to FPL-update. 6
4.4 Special Procedures Note: A release is an authorization for the accepting unit to climb, descend or turn (by not more than 45 ) a specific aircraft before the transfer of control. 4.4.1 ACC Copenhagen ATCC Oslo Arriving aircraft to ENSN/ENTO/ENRY via ARTOR Arriving aircraft to ENSN/ENTO/ENRY with FPL route via ARTOR will by ACC Copenhagen be given descent clearance to FL200 if cruise level is above FL205 These aircraft are when north of a line east/west 15 NM south of ARTOR, and in respect of known traffic released to ATCC Oslo for a) turn in respect of Sweden FIR, and b) descent Arriving aircraft to ENCN via DANKO/RASVI/AMSEV Arriving aircraft to ENCN with FPL route via DANKO/RASVI/AMSEV will by ACC Copenhagen be given descent clearance to FL200 if cruise level is above FL205. Unless otherwise coordinated, these aircraft are - within 15 NM from the AoR-boundary and in respect of known traffic - released to ATCC Oslo for: a) turn in respect ACC Copenhagen Sector N and TSA Hanstholm A/B (when active) b) descent. Traffic via TR10. For traffic via TR10, ATCC Oslo Sector 4 is receiving sector and responsible for coordination with ATCC Oslo Sector 8. 4.4.2 ATCC Oslo ACC Copenhagen Departing aircraft from ENSN/ENTO/ENRY via NIROD/BINRO Departing aircraft from ENSN/ENTO/ENRY with FPL route via NIROD/BINRO shall be given clearance to FL280 or cruising level, if lower. These aircraft are - within 15 NM from the AoR-boundary and in respect of known traffic - released to ACC Copenhagen for climb. 7
Departing aircraft from ENCN via RASVI/AMSEV Departing aircraft from ENCN with FPL route via RASVI/AMSEV shall be given clearance to FL280 or cruising level, if lower. These aircraft are - within 15 NM from the AoR-boundary and in respect of known traffic - released to ACC Copenhagen for climb. Traffic via TR10. For traffic via TR10, ATCC Oslo Sector 4 is transferring sector and responsible for coordination with ACC Copenhagen. 4.4.3 ACC Copenhagen ATCC Stavanger Conflict resolution Even levels. For aircraft coordinated at even levels, ACC Copenhagen shall coordinate the conflict resolution between north and southbound flights with ATCC Stavanger if the coordinated ETOs for KARLI differ with less than 10 minutes. Release for traffic from ACC Copenhagen Sector N towards ATCC Stavanger. Traffic from ACC Copenhagen Sector N towards ATCC Stavanger is - when within 25 NM from the AoR-boundary and in respect of known traffic, the ACC Scottish AoR and the ATCC Oslo AoR - released to ATCC Stavanger for turn. 4.4.4 ATCC Stavanger ACC Copenhagen Conflict resolution Odd Levels For aircraft coordinated at odd levels, ATCC Stavanger shall coordinate the conflict resolution between south and northbound flights with ACC Copenhagen if the coordinated ETO's for KARLI differ with less than 10 minutes. Release for traffic from ATCC Stavanger towards ACC Copenhagen Sector N. Traffic from ATCC Stavanger towards ACC Copenhagen Sector N is - when within 25 NM from the AoR-boundary and in respect of known traffic, the ACC Scottish AoR and the ATCC Oslo AoR - released to ACC Copenhagen for turn. 4.5 VFR Flights Controlled VFR flights are subject to prior coordination. 8
5 Transfer of Control and Transfer of Communications 5.1 Transfer of Control Transfer of control takes place at the AoR boundary. 5.2 Transfer of Communications The transfer of communications shall take place before the transfer of control but not earlier than 30 NM before the AoR-boundary, unless otherwise coordinated. 6 Radar Based Coordination Procedures 6.1 SSR Code Assignment Both ATS units shall transfer aircraft on verified discrete SSR codes. Any change of SSR code by the accepting ATS unit may only take place after the transfer of control point. 6.2 Radar Coordination Procedures 6.2.1 Transfer of Radar Control Transfer of radar control may be effected after prior verbal coordination provided the minimum distance between the aircraft does not fall below 5 NM. 6.2.2 Silent Transfer of Radar Control Transfer of radar control may be effected without prior verbal coordination provided the minimum distance between successive aircraft about to be transferred is 10 NM and constant or increasing. Note: When using mach-number speed control, pilots concerned shall be instructed to report their assigned mach-number to the accepting ATS unit upon initial contact. 6.2.3 Transfer of Radar Label Transfer of radar label (aircraft tag) shall be initiated when initiating transfer of communications. Note 1: Ownership and transfer of the radar label must not be confused with responsibility for control and transfer of control. Note 2: Transfer of communications must not be delayed as a result of delays or difficulties when transferring the radar label. 9