LETTER OF AGREEMENT BETWEEN NORWAY FIR AND SWEDEN FIR

Similar documents
LETTER OF AGREEMENT BETWEEN NORWAY FIR AND DENMARK FIR

LETTER OF AGREEMENT BETWEEN POLISH VACC AND SWEDEN FIR

LETTER OF AGREEMENT BETWEEN NORWAY FIR AND DENMARK FIR

LETTER OF AGREEMENT BETWEEN NORWAY FIR AND DENMARK FIR

LETTER OF AGREEMENT BETWEEN DENMARK FIR AND SWEDEN FIR. VATSIM Scandinavia 4 April 2013

Denmark FIR and Sweden FIR

LETTER OF AGREEMENT BETWEEN BODØ FIR AND MURMANSK FIR

LETTER OF AGREEMENT. Between

GENERAL OPERATING PROCEDURES FINLAND(GOP)

International Virtual Aviation Organisation. Letter of Agreement. between. and. Effective: 15/05/2017 Edition: 2

Letter of Agreement. between. and

International Virtual Aviation Organisation. Letter of Agreement. between. and. Effective: 15/05/2017 Edition: 1

Object: LoA between the Barcelona FIR (LECB) and the Bordeaux FIR (LFBB)

Letter of Agreement. between. and. Effective: 01-OCT-2016 / 1610 Edition: 3.0

Standard Operating Procedures (SOPs) for UAE Centre (OMAE)

ALTIMETER SETTING PROCEDURES

VATUSA-VATNZ-VATPAC OCEANIC PARTNERSHIP OAKLAND OCEANIC FSS GENERAL SOP 1 OCT 2012

Standard Operating Procedures (SOPs) for Arabian Control (OGCC)

International Civil Aviation Organization COMMON FORMAT LOA BETWEEN ATS UNITS. (Presented by United Arab Emirates) SUMMARY

1.2 An Approach Control Unit Shall Provide the following services: c) Alerting Service and assistance to organizations involved in SAR Actions;

LETTER OF AGREEMENT. between. and

LETTER OF AGREEMENT. 1. General. VACC-AUSTRIA and VACC-CZ Purpose Operational Status Validity. Between

THE AREA CONTROL CENTRE (CTR) POSITION

LETTER OF AGREEMENT. between. The purpose of this Letter of Agreement is to define the coordination procedures to be applied

Letter of Agreement. IVAO German & France Divisions. 1. Purpose. 2. General procedures

SECTION 4 - APPROACH CONTROL PROCEDURES

ZTL ARTCC. Asheville Regional. Air Traffic Control Tower. Standard Operating Procedures AVL B. Effective: May 1, 2011

ATM REGIONAL CONTINGENCY PLAN FOR.. CTA/UTA/FIR

Burlington ATCT Standard Operating Procedures

Letter of Agreement. IVAO Switzerland & France Divisions. 1. Purpose. 2. General procedures

Letter of Agreement. IVAO Division France. 1. Purpose. 2. General procedures

Greenville Spartanburg International

SECTION 6 - SEPARATION STANDARDS

Letter of Agreement. IVAO United Kingdom and Ireland & France Divisions. 1. Purpose. 2. General procedures

ERIE ATCT STANDARD OPERATING PROCEDURES

INDICE. 1. Purpose 2 2. General procedures 2 3. ATC units description 2 4. Coordination procedures En-route coordination 6

USE OF RADAR IN THE APPROACH CONTROL SERVICE

Letter of Agreement. between

ZTL ARTCC. Augusta Regional

AIP ENR JORDAN 12 DEC 2013 RADAR SERVICES AND PROCEDURES

LETTER OF AGREEMENT. between. and

Avinor. Southern Norway Airspace Project SNAP. Flyoperativt Forum. Per Arnt Auen, project manager. Gardermoen,

Standard Operating Procedures (SOPs) for BAGHDAD (ORBI)

FLIGHT STRIP MANAGEMENT - APPROACH LEVEL

1. SUBJECT: PROCEDURES RELATING TO THE COORDINATION OF AIR TRAFFIC BETWEEN KINGSTON FIR AND HAVANA FIR

c) Advisory service to IFR flights operating within advisory airspace.

VIRTUAL AIR TRAFFIC SIMULATION NETWORK NORTH AMERICA REGION - USA DIVISION vzkc KANSAS CITY ARTCC

Traffic shall be handed over as soon as practical and, whenever possible, at latest 3000 ft before reaching the cleared flight level.

IFR SEPARATION USING RADAR

Object: LoA between the Reims FIR (LFEE) and the Geneva FIR (LSAG)

RALEIGH-DURHAM ATCT/TRACON STANDARD OPERATING PROCEDURES

LETTER OF AGREEMENT. Between. and RELATING TO

RELEASE RECORD. Version Date Author Notes Dec 2006 SK Initial Release

Eastern Caribbean PIARCO Virtual FIR. PIARCO Control Zone (CTR)

Albany ATCT Standard Operating Procedures

Official Journal of the European Union L 186/27

REPUBLIC OF SEYCHELLES CIVIL AVIATION AUTHORITY AERONAUTICAL INFORMATION SERVICE P.O.BOX 181, VICTORIA SEYCHELLES

CHAPTER 5 SEPARATION METHODS AND MINIMA

VIRTUAL AIR TRAFFIC SIMULATION NETWORK UNITED STATES DIVISION. SUBJ: Phoenix (PHX) Air Traffic Control Tower (ATCT) Standard Operating Procedures

AIRSPACE STRUCTURE. In aeronautics, airspaces are the portion of the atmosphere controlled by a country above its territory.

Any queries about the content of the attached document should be addressed to: ICAO EUR/NAT Office:

AIP PORTUGAL ENR NOV-2007

IVAO Switzerland Division

Virtual Jacksonville Air Route Traffic Control Center Tallahassee ATCT Standard Operating Procedures

IFR SEPARATION WITHOUT RADAR

Luxembourg TMA Contingency measures. Clear the sky procedure & Agreement on service continuity

JACKSONVILLE CENTER AND SAVANNAH TRACON. LETTER OF AGREEMENT EFFECTIVE: December 22, 2006

Letter of Agreement. IVAO United Kingdom and Ireland & France Divisions. 1. Purpose. 2. General procedures

VATUSA PHOENIX TRACON and VATUSA PHOENIX ATCT LETTER OF AGREEMENT. SUBJECT: Interfacility Coordination Procedures

In order to start practical Tower controller training at Oslo Gardermoen, a student must meet the following requirements:

SULAYMANIYAH INTERNATIONAL AIRPORT MATS CHAPTER 11

PBN Airspace Concept. ATS requirements

Letter of Agreement (LOA)

IVAO Flight Operations Department Indonesia (ID) Division Procedures

GENERAL REPORT. Reduced Lateral Separation Minima RLatSM Phase 2. RLatSM Phase 3

Cape Area Airports Standard Operating Procedures

Standard Operational Procedures

Northern Regional Training Scheme. EGBB Birmingham Airport Pilot s Guide. REVISION 1 (Monday, 30 January 2012)

Safety Brief. 21st March Operations in Somali Airspace

Letter of Agreement by and between Jacksonville ARTCC and Miami ARTCC

Piedmont Triad International Airport

AIRPROX REPORT No Date/Time: 27 Aug Z. (5nm NE Coventry Airport) Airspace: London FIR (Class: G)

EASA NPA on SERA Part ENAV Response sheet. GENERAL COMMENTS ON NPA PACKAGE Note: Specific comments are provided after the General Comments

A Letter of Agreement Between: Robin Hood Airport Doncaster Sheffield and British Gliding Association

Cleveland ARTCC and Boston Virtual ARTCC Letter of Agreement

BOSTON ARTCC (vzbw) STANDARD OPERATING PROCEDURE KALB) ALBANY APPROACH (ALB

AIP PORTUGAL ENR JAN-2012

NATS Edinburgh / BGA LOA effective 24 November 2005

SPECIAL PROCEDURES FOR IN-FLIGHT CONTINGENCIES IN OCEANIC AIRSPACE OF SEYCHELLES FIR

Denver ARTCC Colorado Springs ATCT & TRACON STANDARD OPERATING PROCEDURES

- Updated formatting - Re-drawn airspace delegation diagram

ENR 1.7 ALTIMETER SETTING PROCEDURES

Northern RTS. EGNT and EGNV vmats Part 2. REVISION 1 (Saturday, 19 February 2011 at 22:29) Newcastle and Durham Tees Valley

IVAO Switzerland Division

Jordan Airspace Manual. Prepared by: Aboud Horani & Mahmoud Odeh XM-AOC / XM-ADIR

Southern California TRACON and Lindbergh Tower LETTER OF AGREEMENT SUBJECT: INTER-FACILITY COORDINATION AND CONTROL PROCEDURES

The following flights always take priority over all other air traffic and airspace structures:

Guide to the Faroe Islands

FRENCH GUIANA ATM CONTINGENCY PLAN FOR ROCHAMBEAU FIR

International Civil Aviation Organization REVIEW OF STATE CONTINGENCY PLANNING REQUIREMENTS. (Presented by the Secretariat) SUMMARY

Transcription:

2014 LETTER OF AGREEMENT BETWEEN NORWAY FIR AND SWEDEN FIR VATSIM Scandinavia 11/12/2014

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. 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 11/12/2014 and supersedes the Letter of Agreement between dated 14/11/2013. Martin Loxbo Director Sweden FIR Daniel Klepp Director Norway FIR 2

2 Areas of Responsibility and Sectorisation 2.1 Areas of Responsibility 2.1.1 Norway FIR 2.1.2 Sweden FIR Norway FIR/UIR GND UNL Sweden FIR GND UNL 2.2 Sectorisation Note 1: Secondary sectors in this section are listed in order of priority. 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). 2.2.1 Norway FIR A fictional sector (Norway ontrol) has been created to be able to control the entire Norway FIR in off-peak periods: The Fictional Norway ontrol Positions: Area Sector Name Remarks Whole border to Sweden N063.26.27.000 N058.29.60.000 Norway ontrol NOR_TR 125.500 Norway ontrol South NOR_S_TR 121.550 ontrols Entire Norway FIR. ontrols: NOR TR, NOR_E_TR East of ENVA to Border Denmark 3

Norway has 3 ATs, one in Oslo, one in Stavanger and one in Bodø. As a way of simplifying the administration, there is now a process of making it administratively as 1 AT with 3 localisations. All AT sectors from ENVA and south are now known as Norway AT Sector 1 to 19. As a part of adapting to the new Norway ontrol concept, we are changing our callsigns from the old ENOS/ENSV/ENBD_TR to NOR_TR with different possibilities of splitting. The sectors in Oslo and Stavanger + Bodø South has got the numbers 1-19, while Bodø entral, North and East keeps NOR_/N/E_TR N069.03.48.010 N067.15.00.000 N067.15.00.000 N063.26.27.000 N063.26.27.000 N062.00.00.000 N062.00.00.000 N059.53.40.000 N059.53.40.000 N058.29.60.000 Area Sector Name Secondary Sectors Remarks Bodø ontrol Sector North NOR_N_TR 126.450 Bodø ontrol Sector entral NOR TR 118.550 Norway AT S19 NOR_19_TR 131.100 Norway AT Sector 6 NOR_6_TR 120.370 Oslo ontrol Sector 4 NOR_4_TR 118.870 NOR_TR 125.500 Finnish Border NOR_N_TR 126.450 NOR_TR 125.500 NOR_18_TR 125.700 NOR_N_TR 126.450 NOR_S_TR 121.550 NOR_TR 125.500 NOR_4_TR 118.870 NOR_S_TR 121.550 NOR_TR 125.500 NOR_6_TR 120.370 NOR_S_TR 121.550 ENOR_TR 125.500 East of ENBO East of ENBO East of ENVA East of ENVA Border Oslo/Bodø Border Oslo/Bodø Border Stockholm/Malmö Border Norway/Sweden/ Denmark Note: allsign for all Norwegian A sectors is NORWAY ONTROL. 4

2.2.2 Sweden FIR South of: N059.34.44.000 N059.53.44.000 N061.21.23.000 N061.21.23.000 N064.38.36.000 North of N064.38.36.000 Area Sector Name Secondary Sectors Remarks GND-FL285 Malmö AoR Sector 5 ESMM_5_TR/ ESMM_TR 128.625 FL285-UNL Malmö AoR Sector 4 ESMM_4_TR 124.405 Stockholm AoR Sector 3 ESOS_3_TR 131.125 Stockholm AoR Sector N ESOS_N_TR 132.150 Stockholm AoR Sector K ESOS_K_TR 131.050 ESOS_TR 118.400 ESMM_5_TR/ ESMM_TR 128.625 ESOS_TR 118.400 ESOS_TR 118.400 ESOS_3_TR 131.125 ESOS_TR 118.400 ESOS_N_TR 132.150 ESOS_3_TR 131.125 ESOS_TR 118.400 Note: allsign for all ESMM and ESOS sectors is SWEDEN ONTROL. 5

3 Delegated Airspace 3.1 Airspace delegated from Norway FIR to Sweden FIR 3.1.1 Delegation of ATS from Norway A Bodø to Stockholm AoR (ESOS) 3.1.1.1 Area BORGE 3.1.1.2 Area NORLI Within area 653057N 0142956E 645033N 0135724E along the Swedish border to 653057N 0142956E FL195 FL660 Within area 643320N 0134403E 640447N 0132234E along the Swedish border to 643320N 0134403E FL195 FL660 See Appendix 1 3.1.2 Delegation of ATS from Norway A Oslo to Malmö AoR (ESMM) 3.1.2.1 Area OSLOB 585607N 0114020E 593006N 0113035E 593706N 0113508E 593835N 0114647E along Swedish/Norwegian FIR-border to 585607N 0114020E FL285 FL660 3.2 Airspace delegated from Sweden FIR to Norway FIR 3.2.1 Delegation of ATS from Stockholm AoR (ESOS) to Norway A Bodø 3.2.1.1 Area SILVER The portion of Sweden FIR/UIR west of a line parallel 6 NM east of T65 within the coordinates 680504N 0172652E 660509N 0153014E 660913N 0150208E FL125 FL660 north of 6700N FL95 FL660 south of 6700N 6

3.2.2 Delegation of ATS from Stockholm AoR (ESOS) to Norway A Oslo 3.2.2.1 Area TEKVA 600458N 0122918E - 600000N 0132539E - 593944N 0131817E - 594500N 0121920E - 595323N 0121027E - along national border to 600458N 0122918E FL95 FL285 Regulations: Area TEKVA is delegated to Norway A Oslo, only when holding at holding point TEKVA. Norway A Oslo shall notify A Stockholm at least 5 minutes in advance when requiring the area. TEKVA holding may only be used by traffic from Sweden FIR/UIR with destination ENGM. 3.2.2.2 Area NOR 2 6200N 01214E 6132N 01237E along the national border 6200N 01214E FL95 FL660 Regulations: A Stockholm may resume responsibility for provision of ATS with a notification time of 10 minutes. 3.2.2.3 Area FINNSKOGEN 1 603833.5N 0123045.0E along national border to 610337.3N 0124059.1E - 603833.5N 0123045.0E FL95 FL660 Regulations: Area FINNSKOGEN 1 is delegated to Norway A Oslo to facilitate sequencing via feeder fix INREX. ESOS may resume responsibility of provision of ATS in Area FINNSKOGEN 1 with a notification time of 10 minutes. 3.2.2.4 Area FINNSKOGEN 2 610337.3N 0124059.1E along national border to 612125.0N 0125217.2E - 612004.5N 0125355.8E - 604851.0N 0125117.7E -603045.0N 0123625.0E along national border to 603833.5N 0123045.0E - 610337.3N 0124059.1E FL95 FL660 Regulations: Area FINNSKOGEN 2 is delegated to Norway A Oslo, only when holding at holding point INREX. Norway A Oslo shall notify A Stockholm at least 5 minutes in advance when requiring the area. INREX holding may only be used by traffic with destination ENGM. 7

3.2.3 Delegation of ATS from Malmö AoR (ESMM) to Norway A Oslo 3.2.3.1 Area ÖRJE 1 3.2.3.2 Area ÖRJE 2 595326N 0120556E - 593740N 0115340E - 593105N 0114331E along Swedish/Norwegian FIR border to 595326N 0120556E 6500 ft AMSL FL215 595326N 0120556E - 593740N 0115340E - 593105N 0114331E along Swedish/Norwegian FIR border to 595326N 0120556E 6500 ft AMSL FL215 3.2.3.3 Area BOHUS 595327N 0120557E - 594649N 0120631E 592920N 0115430E 590419N 0115144E 585300N 0114130E 585029N 0110921E 585600N 0104950E - along national border to 595327N 0120557E 6500ft AMSL/FL95/FL215 FL285 Note: A Malmö can on request resume provision of ATS in area BOHUS. 3.2.3.4 Area KOSTER Lateral Limits: 585318N 0112722E - along the national border 585332N 0103820E - 584149N 0103413E 584233N 0103853E - 584358N 0104203E 585050N 0104347E - 585345N 0111525E (585318N 0112722E) Vertical Limits: 4500 ft AMSL FL 115. Farris APP or Norway A Oslo may clear arriving traffic within the area for descend to 6000 ft AMSL on Farris TMA QNH. Airspace lassification: Regulations: Area KOSTER is delegated to Norway A Oslo. The purpose of the area is to maintain the traffic regulation system to ENTO and ENRY. At night IFR separation shall be provided between all aircraft (IFR/VFR) in airspace of classification, according to Swedish regulations. A Malmö can resume responsibility of provision of ATS in Area KOSTER. A notification time of 10 minutes is required. 8

3.3 Special Areas 3.3.1 Delegation of ATS from Tampere AoR (EFES) to Norway A Bodø 3.3.1.1 Area HALTI oordination: The portion of Finland FIR/UIR west of a parallel line 6 NM east of N150 between OGLAV and GAPRO. FL95 FL660 All messages concerning traffic on N150 will be exchanged between A Stockholm and A Bodø. A Bodø is responsible for coordination with A Tampere. 3.4 Other Areas 3.4.1 Release area TANUM 585607N0114020E 585300N0114130E 583000N0114700E 583000N0103000E along the AoR-boundary between ESMM and Norway A Oslo to 585607N0114020E. Regulations: FL95 FL660 Release area TANUM is applicable for traffic via BOMGU and REGMA and with destination in Farris TMA or Oslo TMA. Such traffic is, with regard to known traffic, released to Norway A Oslo for descent when inside release area TANUM. 9

4 Procedures for oordination LoA between 4.1 ATS Routes 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 Special Procedures Note: A release is an authorisation for the accepting unit to climb, descend or turn (by not more than 45 ) a specific aircraft before the transfer of control. 4.2.1 Flights from Sweden FIR to Norway FIR 4.2.1.1 Flights from Stockholm AoR (ESOS) to Norway A Bodø OGLAV/N150: Flights with destination inside Norway A Bodø are released to Norway A Bodø for descent 12 NM before OGLAV. The release can be suspended by A Stockholm for a specific flight, a group of flights or a specific period of time. Destination ENVA: All flights with destination ENVA via OSKOK with cruising level above FL260 shall be cleared descend to FL260 to cross OSKOK at FL290 or below. These flights are released for further descend 20NM before OSKOK Flights to ENVA, or flying through ENVA TMA via other OP than OSKOK shal be coordinated with Norway A for transfer information. Other: Traffic with destination ENRO, ENBO, ENEV or flying through these TMAs shall e coordinated with Norway A for transfer information. 4.2.1.2 Flights from Stockholm AoR (ESOS) to Norway A Oslo Via ESEBA: Traffic above FL225 with destination ENGM, ENTO, ENRY and ENSN shal be cleared for descent to FL220 before transfer of communication. Such flights are released to Norway A for descent, change of speed and right turn at long 013300E, and for left turn after passing/abeam TEKVA All westbound flights are released for the turns mentioned above TEKVA holding: Traffic with destination ENGM, ENSN, ENRY or ENTO at or above FL220 shall be coordinated with Norway A Oslo and transferred at cruising level or descending to a coordinated level. 10

Traffic in TEKVA holding above FL285 will be handled by ESOS. Norway A Oslo shall inform A Stockholm of RWY in use at ENGM, and expected time to leave TEKVA holding for each flight in TEKVA holding above FL285. Via XELVI: Via MASEV/P850: Direct Routings: Traffic with destination ENGM conducted above FL305 will be cleared by A Stockholm for descent to FL300. The traffic is released to Norway A Oslo for further descent and turn 20 NM before XELVI. These releases are subject to northbound traffic via EGAGO/XELVI. Norway A Oslo is responsible for coordination if turn affect ESOS sector 3. Flights shall be FL300 or above unless otherwise coordinated. ESOS may clear westbound traffic with FPL via M996 direct VAGBU ESOS may clear westbound traffic with via Z267 direct INGAL and via P996 direct IPTON. This traffic shall not pass the AoR boundary north of ROVPA. 4.2.1.3 Flights from Malmö AoR (ESMM) to Norway A Oslo Via REGMA: Flights with destination ENGM, with cruising level above FL255, will by A Malmö be given descent clearance to FL250 before transfer of communication, and are released to Norway A Oslo for descent, speed change and turn when inside release area TANUM. ESMM may issue clearance direct LUNIP. Via REPKU/REGMA: Flights with destination ENSN, ENRY or ENTO, with cruising level above FL125 will by A Malmö be given descent clearance to FL120 before transfer of communication, and are released to Farris APP for descent, speed change and turnwhen inside release area TANUM. Traffic via REGMA with destination ENRY shall be transferred to Farris APP E (124.350). Traffic via REPKU with destination ENTO/ENSN shall be transferred to Farris APP W (134.050). Note: Flights via REPKU shall cross REPKU at or below FL140 according to STAR procedures. Via VATEX: For traffic arriving in Farris TMA, flight level shall be coordinated with Norway A Oslo sector 3. 11

4.2.2 Flights from Norway FIR to Sweden FIR 4.2.2.1 Flights from Norway A Bodø to Stockholm AoR (ESOS) N150/OGLAV: Traffic departing ENAT is considered climbing to coordinated level when passing OGLAV. P600: Traffic departing ENEV, ENDU and ENT may be cleared direct LIVLI and is considered climbing to coordinated level. Traffic southbound on P600 may be in conflict with northbound traffic on T65. Transfer of communications for traffic on P600 will therefore be no later than point LIVLI. T63: Traffic departing ENBO is considered climbing to coordinated level when passing the FIR boundary. Traffic departing ENVA: All flights departing ENVA with FPL route in Sweden FIR shall be cleared SOLKA and climb to FL290 or cruising level if lower. Note: ENVA APP can hand the aircraft over directly to A Stockholm when Norway A Bodø is offline. 4.2.2.2 Flights from Norway A Oslo to Stockholm AoR (ESOS) Via MASEV: Departing traffic from ENGM, ENSN, ENRY or ENTO with planned cruise level FL290 or above will be cleared by Norway A Oslo to FL290. The traffic is released to A Stockholm for further climb. Via EGAGO: Departing traffic will be cleared by Norway A Oslo to cruising level. Traffic departing from Oslo AoR is considered climbing to the flight level stated above. Direct Routings: Norway A Oslo may clear all eastbound traffic, with FPL via ELTOK, and via SUVAR/ROVPA/ROGED/MASEV direct ELTOK. This traffic shall not pass the AoR boundary south of MASEV, and not north of SUVAR. Norway A Oslo may clear all eastbound traffic via L24 direct EVLAN, and via N873 direct UXETI. This traffic shall not pass the AoR boundary south of MASEV, and not north of SUVAR. 12

4.2.2.3 Flights from Norway A Oslo to Malmö AoR (ESMM) Via OKSAT: Departing traffic from ENGM will be cleared by Norway A Oslo to cruising level. Relevant flights may be routed direct KELIN. Via MOGLU/VATEX: Departing traffic from ENSN, ENRY or ENTO will be cleared by Norway A Oslo to FL210 or cruising level if lower. Relevant flights may be routed direct KELIN Via BOMGU: Other: Departing traffic from ENSN or ENTO will be cleared by Norway A Oslo to FL210 or cruising level if lower. Departures from ENGM not via OKSAT, to be cleared via TUMGU to FL210 or cruising level if lower. A Malmö will consider all traffic departing from Oslo AoR as climbing to the flight level stated above. 4.3 VFR Flights ontrolled VFR flights are subject to prior coordination. 13

5 Transfer of ontrol and Transfer of ommunications 5.1 Transfer of ontrol Transfer of control takes place at the AoR boundary. 5.2 Transfer of ommunications 5.2.1 Flights from Sweden FIR to Norway FIR 5.2.1.1 Flights from Stockholm AoR (ESOS) to Norway A Bodø Transfer of communications shall normally take place not less than 3 minutes before the transfer of control point. 5.2.1.2 Flights from Stockholm AoR (ESOS) to Norway A Oslo Transfer of communications shall normally take place 10 NM prior to, and not later than at the transfer of control point. ESOS shall transfer southbound flights via XELVI to Norway A Oslo not later than 20 NM before XELVI. 5.2.1.3 Flights from Malmö AoR (ESMM) to Norway A Oslo Transfer of communications shall take place not later than the transfer of control. 5.2.2 Flights from Norway FIR to Sweden FIR 5.2.2.1 Flights from Norway A Bodø to Stockholm AoR (ESOS) Transfer of communications shall normally take place not later than the transfer of control point, except for southbound traffic on P600. Transfer of communications on P600 shall be no later than point LIVLI. 5.2.2.2 Flights from Norway A Oslo to Stockholm AoR (ESOS) Transfer of communications shall normally take place 10 NM prior to, and not later than at the transfer of control point, except as described below. Norway A Oslo will retain radio communications for traffic via MASEV (Z183 and L24) until traffic is clear of westbound traffic via N623. Transfer of communication will always be done west of long. 0133000E. 5.2.2.3 Flights from Norway A Oslo to Malmö AoR (ESMM) Transfer of communications shall take place not later than the transfer of control. 14

6 Radar Based oordination Procedures 6.1 SSR ode 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 oordination Procedures 6.2.1 Transfer of Radar ontrol 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 ontrol 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. Note 3: ontrollers in A Malmö/Stockholm will not assume radar label until communications with aircraft is established. 15