Denmark FIR and Sweden FIR

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

LETTER OF AGREEMENT BETWEEN POLISH VACC AND SWEDEN FIR

LETTER OF AGREEMENT BETWEEN NORWAY FIR 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 NORWAY FIR AND DENMARK FIR

GENERAL INFORMATION The aerodrome consists of three runways (04L-22R, 04R-22L, 12-30) and four aprons.

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

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

THE AREA CONTROL CENTRE (CTR) POSITION

SECTION 4 - APPROACH CONTROL PROCEDURES

PRE-FLIGHT BULLETIN FLIGHT FOLDER GBG SAR ISSUED BY FLIGHT PLANNING CENTRE SWEDEN

LETTER OF AGREEMENT. Between

LETTER OF AGREEMENT BETWEEN BODØ FIR AND MURMANSK FIR

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

ALTIMETER SETTING PROCEDURES

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

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

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

IVAO Switzerland Division

Greenville Spartanburg International

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

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

Burlington ATCT Standard Operating Procedures

Information to VFR pilots

THE TOWER CONTROL POSITION (TWR)

NATS Edinburgh / BGA LOA effective 24 November 2005

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

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

AIP ENR JORDAN 12 DEC 2013 RADAR SERVICES AND PROCEDURES

LETTER OF AGREEMENT. between. and

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

Piedmont Triad International Airport

Albany ATCT Standard Operating Procedures

ZTL ARTCC. Augusta Regional

As of Nov. 17th 2011 Sweden and Denmark implemented the concept of Free Route Airspace (FRA). This will be described in the section below.

Standard Operational Procedures

Standard Operating Procedures (SOPs) for BAGHDAD (ORBI)

Denver ARTCC Colorado Springs ATCT & TRACON STANDARD OPERATING PROCEDURES

LETTER OF AGREEMENT LETTER OF AGREEMENT BETWEEN LONDON SOUTHEND AIRPORT AND STOKE AIRFIELD

AIP PORTUGAL ENR JAN-2012

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

LETTER OF AGREEMENT. between. and

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

FLIGHT STRIP MANAGEMENT - APPROACH LEVEL

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

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

ATC Training Syllabus Philippines vacc Version 1.1 September 25, 2016

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

Letter of Agreement. between

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

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

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

IVAO Flight Operations Department Indonesia (ID) Division Procedures

Providence ATCT Standard Operating Procedures

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

Letter of Agreement (LOA)

- Updated formatting - Re-drawn airspace delegation diagram

ENR 2. AIR TRAFFIC SERVICES AIRSPACE

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

ATMM. Air Traffic Management Manual. Air Traffic Management Manual VACC AUSTRIA LOVV ATMM Air Traffic Management Manual

USE OF RADAR IN THE APPROACH CONTROL SERVICE

Cape Area Airports Standard Operating Procedures

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

Temporary Radio Mandatory Zone

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

NUAC Programme Definition Phase Final Report. Appendix 7. Airspace Design OCTOBER Third Draft

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

INFORMATION TO VFR PILOTS

Appendix 7 Airspace Design

ATC BRIEFING March 7th 2009 Event time: 1200z-2200z

SECTION 6 - SEPARATION STANDARDS

Northern Regional Training Scheme. EGNT Newcastle Aerodrome Pilot s Guide. REVISION 2 (Wednesday, 03 August 2011 at 15:51)

Information for VFR Pilots

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

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

ZAGREB FIR SECTOR MANUAL

IFR SEPARATION USING RADAR

Standard Operational Procedures

Letter of Agreement by and between Jacksonville ARTCC and Miami ARTCC

Pilot ATC RT Phraseology

AIP PORTUGAL ENR NOV-2007

Standard Operating Procedures

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

RALEIGH-DURHAM ATCT/TRACON STANDARD OPERATING PROCEDURES

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

San Juan CERAP. Standard Operation Procedures. Version 2.2 May 5th, Welcome to San Juan CERAP (ZSU ARTCC, TJZS FIR)

Airspace Namibia 2017/18. Released Version

VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT

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

PILOT BRIEFING GENEVA RFE 2018

PRE-FLIGHT BULLETIN FLIGHT FOLDER GBG SAR ISSUED BY FLIGHT PLANNING CENTRE SWEDEN

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

OPERATIONS MANUAL PART A

RWY 24. Designator Route Remarks. All traffic shall initially climb to 4000FT QNH with climb gradient 3.3% MNM, unless instructed otherwise by ATC.

VATUSA Approval 3/21/18

VFR PHRASEOLOGY. The word IMMEDIATELY should only be used when immediate action is required for safety reasons.

Transcription:

Letter of Agreement between VACCSCA December 2010 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. 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 16/12/2010 and supersedes the Letter of Agreement between Denmark AoR and Sweden AoR dated 20/09/2007. Martin Loxbo Director Sweden FIR Lars Toftlund Director Denmark FIR 2 Areas of Responsibility and Sectorisation 2.1 Areas of Responsibility 2.1.1 Denmark FIR 2.1.2 Sweden FIR Copenhagen FIR/UIR GND UNL Sweden FIR/UIR GND UNL 2.2 Sectorisation 2.2.1 Denmark FIR North of point Copenhagen AoR Sector V (EKDK-V) 5620N 01201E EKDK_V_CTR 126.050 (2 NM south of MADAG): (EKDK_C_CTR 128.220, EKDK_A_CTR/EKDK_CTR 135.270) Traffic on L621 transfers to Sector V Callsign COPENHAGEN CONTROL Between Copenhagen AoR Sector C (EKDK-C) EKDK-A & EKDK-V: EKDK_C_CTR 128.220 (EKDK_A_CTR/EKDK_CTR 135.270) Traffic on N872 transfers to Sector C Callsign COPENHAGEN CONTROL South of point Copenhagen AoR Sector A (EKDK-A) 5551N 01225E EKDK_A_CTR/EKDK_CTR 135.270 (5 NM north of GOLMI): Traffic on N850 transfers to Sector A Callsign COPENHAGEN CONTROL 2

GND FL195: Within Copenhagen Copenhagen TMA Sector East (EKCH-E) TMA: EKCH_E_APP 118.450 (EKCH_APP 119.800) Callsign COPENHAGEN APPROACH 2.2.2 Sweden FIR GND FL285: Copenhagen TMA Sector West (EKCH-W) EKCH_W_APP 119.800 Callsign COPENHAGEN APPROACH South of point 553101N 125032E: Malmö AoR Sector L (ESMM-L) ESMS_APP 134.970 (ESMM_K_CTR 124.850, ESMM_E_CTR 128.050, ESMM_CTR 124.400, ESOS_CTR 118.400) Between 553101N Malmö AoR Sector K (ESMM-K) 125032E and ESMM_K_CTR 124.850 (ESMM_W_CTR/ESMM_CTR Göteborg TMA: 124.400, ESOS_CTR 118.400) North of Malmö AoR Area West (ESMM-W) Göteborg TMA: ESMM_W_CTR/ESMM_CTR 124.400 (ESOS_CTR 118.400) GND FL245: Within the lateral limits Göteborg TMC Sector W (GG-APP-W) of Göteborg TMA: ESGG_W_APP 124.200 (ESGG_APP 124.670, ESMM_W_CTR/ESMM_CTR 124.400, ESOS_CTR 118.400) Callsign GÖTEBORG CONTROL FL285 UNL: South of point 553101N 125032E: Malmö AoR Sector 8 (ESMM-8) ESMM_8_CTR 128.170 (ESMM_E_CTR 128.050, ESMM_CTR 124.400, ESOS_CTR 118.400) North point Malmö AoR Area West (ESMM-W) 553101N 125032E: ESMM_W_CTR/ESMM_CTR 124.400 (ESOS_CTR 118.400) Note 1: Secondary frequencies within parenthesis ( ). Note 2: Callsign for all ESMM and ESOS sectors is SWEDEN CONTROL. 3

2.2.3 Sectorisation map 4

3 Delegated Airspace 3.1 Airspace delegated from Denmark FIR to Sweden FIR 3.1.1 Delegation of ATS from Copenhagen FIR/UIR (EKDK) to Malmö AoR (ESMM) 3.1.1.1 Area C 565908N 0114558E 561253N 0122205E FIR/UIR boundary 560951N 0122624E 560923N 0122446E 560433N 0120806E 565908N 0114558E FL95 FL660 C 3.1.1.2 Area H1 560951N 0122624E FIR/UIR boundary 553356N 0124651E 560433N 0120806E 560923N 0122446E 560951N 0122624E FL195 FL660 C 3.1.1.3 Area L1 560951N 0122624E FIR boundary 560158N 0123925E 560158N 0123156E 560923N 0122446E 560951N 0122624E FL65 FL195 C 3.2 Airspace delegated from Sweden FIR to Denmark FIR 3.2.1 Delegation of ATS from Malmö AoR (ESMM) to Copenhagen FIR/UIR (EKDK) 3.2.1.1 Area H2 3.2.1.2 Area L2 553356N 0124651E 552201N 0130137E 551458N 0125956E 545500N 0130000E 545500N 0125100E FIR boundary 553356N 0124651E FL195 UNL C FL195 FL660, G FL660 UNL 560158N 0123925E 560158N 0124046E 555958N 0124356E 555834N 0125156E 554358N 0130656E 551458N 0125956E 551402N 0124132E FIR boundary 560158N 0123925E 2500 ft MSL FL195 C 5

3.2.1.3 Area L3 3.2.1.4 Area SUNDET 551458N 0125956E 545500N 0130000E 545500N 0125100E FIR boundary 551402N 0124132E 551458N 0125956E 3500 ft MSL FL195 E 3500 ft MSL FL95, C FL95 FL195 555329N 0124042E 555128N 0124956E 554458N 0125356E 554028N 0130326E 553343N 0125356E 552628N 0125156E 552248N 0123735E FIR boundary 555329N 0124042E 1500 ft MSL 2500 ft MSL C Note: Area SUNDET is the part of Copenhagen TMA which is located in Sweden FIR. 3.2.1.5 Area KASTRUP 553649N 0125249E 552858N 0124356E 552858N 0124212E FIR boundary 553649N 0125249E GND 1500 ft MSL D Note: Area KASTRUP is the part of Kastrup CTR which is located in Sweden FIR. 3.3 Special Areas 3.3.1 Rønne 3.3.1.1 Rønne TMA Sector A 3500 ft MSL FL95: 551726N 0141828E 551534N 0142453E then clockwise along an arc of a circle, radius 16.2 NM centred at 550404N 0144448E to 545500N 0142127E 545500N 0141000E 551033N 0141000E 551726N 0141828E Sector B 1500 ft MSL 3500 ft MSL: A circle, radius 16.2 NM, centred at 550404N 0144448E Description: 1500 ft MSL FL95 D 1500 ft MSL 4500 ft MSL, E 4500 ft MSL FL95 Rønne (EKRN) is in Danish territory but the aerodrome and Rønne TMA is situated in Sweden FIR. Danish ATC is responsible for Rønne TMA up to and including 4500 ft MSL. Rønne TMA is only established when EKRN is controlled, i.e. when EKRN_TWR or EKDK_E_CTR/EKDK_CTR is providing service for EKRN. At other times Rønne TMA is uncontrolled airspace. 6

ATS units and sectorisation: Rønne TMA sector A (part of ESMM-L) ESMS_APP 134.970 (ESMM_K_CTR 124.850, ESMM_E_CTR 128.050, ESMM_CTR 124.400, ESOS_CTR 118.400) Rønne TMA sector B (EKRN TWR) EKRN_TWR 118.320 (EKDK_A_CTR/EKDK_CTR 135.270) Coordination: EKRN TWR informs ESMM-L and ESMM-8 about runway in use and when opening and closing. 4 Procedures for Coordination For departing IFR flights, EKRN TWR requests clearance from ESMM-L. Arriving IFR flights are given inbound clearance by ESMM-L or ESMM-8 via ROE VOR and advised of runway in use. The traffic is given descent clearance to 5000 ft (ESMS QNH), unless otherwise coordinated with EKRN TWR. Transfer of communications and transfer of control to EKRN TWR should normally take place not later than at the lateral limit of Rønne TMA. The traffic is released to EKRN TWR for turn and further descent. Controlled VFR flights are subject to prior coordination. 4.1 ATS Routes and Flight Level Allocation Standard flight level allocation is to be used on all routes, except those routes listed under 4.1.1. Note: Standard flight level allocation (in RVSM airspace) means that aircraft on eastbound routes (magnetic track 360-179 ) are to use odd flight levels and westbound flights (magnetic track 180-359 ) are to use even flight levels. 4.1.1 ATS Routes with Non-standard Flight Level Allocation 4.1.1.1 Flights from Malmö AoR (ESMM) to Copenhagen FIR/UIR (EKDK) N850: Flights from ESMM to EKDK may use all flight levels. 4.1.1.2 Flights from Copenhagen FIR/UIR (EKDK) to Malmö AoR (ESMM) N851: Flights from EKDK to ESMM may use all flight levels. 7

4.2 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. Unless otherwise noted all releases are subject to known traffic and the boundaries of other ATC sectors. 4.2.1 Flights from Sweden FIR to Denmark FIR 4.2.1.1 Flights from Malmö AoR (ESMM) to Copenhagen FIR/UIR (EKDK) EKCH arrivals via SVD: EKCH APP shall inform ESMM-K: - of runway in use for landing and STAR in use at EKCH; - when increased spacing between arrivals is required; - if EKCH APP is unable to accept traffic from ESMM. ESMM-K will give clearance to FL100 or flight planned level if lower, and inbound clearance via active STAR. The traffic is regarded as one flow of traffic, with a minimum distance of 10 NM between succeeding aircraft. This distance may be reduced to 5 NM with prior coordination. The traffic is released to EKCH APP for descent and turn after SVD. If any of the above cannot be achieved, ESMM-K shall coordinate with EKCH APP. EKCH arrivals via ALM: EKCH APP shall inform ESMM-L: - of runway in use for landing and STAR in use at EKCH; - when increased spacing between arrivals is required; - if EKCH APP is unable to accept traffic from ESMM. ESMM-L will give clearance to 5000 ft (ESMS QNH) or flight planned level if lower, and inbound clearance via active STAR. The traffic is regarded as one flow of traffic, with a minimum distance of 10 NM between succeeding aircraft. This distance may be reduced to 5 NM with prior coordination. The traffic is released to EKCH APP for descent and turn after VENOM (RWY 04/22) / DESAS (RWY 12) / VEGUD (RWY 30). If any of the above cannot be achieved, ESMM-L shall coordinate with EKCH APP. Note: When runway 04L/R or 22L/R is in use, ESMM gives inbound clearance for runway 04 or 22 as appropriate. Actual landing runway (L/R) will be determined by EKCH APP. EKRK arrivals: Each flight is coordinated individually between ESMM and EKCH APP. Flights from ESMS to EKCH: Each flight is coordinated individually between ESMM-L and EKCH APP. N866/M852: Flights departing from ESGG, ESGP, ESGT, ESIB and ESGL are cleared by ESGG APP to FL240 or flight planned level if lower, and flights from ESGT, ESIB and ESGL shall pass DETNA/VADIN at this level. The traffic is released to EKDK for turn and speed control 15 NM before the FIR boundary. 8

L621: Flights departing from ESMK and ESMS are cleared by ESMM to FL240 or flight planned level if lower, and shall pass MADAG at this level. L621, Z703, Z32: Flights departing from ESMT and ESTA are cleared by ESMM to FL140 or flight planned level if lower, and shall pass MADAG/ADVOP/TOBMI at this level. T508: ESMS departures are cleared by ESMM to FL110 or flight planned level if lower, and shall pass DISGO at this level. The traffic is released to EKDK for turn, climb to max FL280 and speed control 10 NM before MALIV. M611, L983: Flights departing from ESMT, ESTA, ESMK and EKRN are cleared by ESMM to FL280 or flight planned level if lower, and shall pass MALIV/KOSMO at this level. 4.2.2 Flights from Denmark FIR to Sweden FIR 4.2.2.1 Flights from Copenhagen FIR/UIR (EKDK) to Malmö AoR (ESMM) EKCH departures: EKCH APP/DEP may clear departing traffic direct ASTOS, BALOX, KEMAX, NOVPO or SIMEG. The traffic is released to ESMM for climb. - Traffic on ASTOS or BALOX SID (prop SID) will be cleared by EKCH DEP to FL140, or flight planned level if lower. - Traffic on KEMAX, VEDAR or SIMEG SID (jet SID) will be cleared by EKCH DEP to FL190, or flight planned level if lower. EKRK departures: Each flight is coordinated individually between EKCH APP and ESMM. Flights from EKCH to ESMS: Each flight is coordinated individually between EKCH APP and ESMM-L. 9

N607, N873: Göteborg TMA arrivals via MAKUR/LOBBI: ESGG APP shall inform EKDK of: - runway in use for landing at ESGG and ESGP - STAR in use at ESGG. EKDK will give clearance to FL90 or flight planned level if lower and flights with destination in Göteborg TMA (destination ESGG, ESGP, ESGT, ESIB or ESGL) shall cross MAKUR/LOBBI at or below FL240. EKDK will give inbound clearance as follows: To ESGG via active STAR. To ESGP via NOL and will advise the pilot of runway in use. Other destination in Göteborg TMA: Direct BAK The traffic is released to ESGG APP for turn, descent and speed control 15 NM before the FIR boundary. L621/Z32: Flights with destination ESMS, ESMK, ESTA and ESMT will by EKDK be given clearance to FL200 or flight planned level if lower, and shall pass MADAG/TOBMI at this level. L983: ESMS arrivals via DETUS: ESMM shall inform EKDK of runway in use for landing and STAR in use at ESMS. EKDK will give clearance to FL90 or flight planned level if lower and flights with destination ESMS shall cross DETUS at or below FL110. EKDK will give inbound clearance via active STAR. The traffic is released for turn, descent and speed control after passing (abeam) CDA VOR. P605/M611: Flights with destination ESMK are cleared by EKDK to FL290 or flight planned level if lower, and shall pass MALIV at this level. 4.3 VFR Flights Controlled VFR flights are subject to prior coordination. 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 5.2.1 Flights from Malmö AoR (ESMM) to Copenhagen FIR/UIR (EKDK) Transfer of communications shall take place not later than the transfer of control. 10

5.2.2 Flights from Copenhagen FIR/UIR (EKDK) to Malmö AoR (ESMM) Transfer of communications shall take place not later than the transfer of control. 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. 11