LOP - OSLO TMA & GARDERMOEN TWR Local operating procedures for: Gardermoen Delivery, Ground and Tower Oslo Approach, Director and Final

Similar documents
LOCAL OPERATING PROCEDURES (LOP) LANDVETTER TWR (ESGG)

Pilot Briefing Stockholm/Arlanda

Procedures Oslo TMA. Scandinavian Virtual Area Control Center (VACCSCA)

LOCAL OPERATING PROCEDURES FOR NORWAY ACC, OSLO

Training program for S2 (TWR) rating

Pilot Briefing for Helsinki-Vantaa Real Flight Event

WHICH AIR TRAFFIC CONTROLLER TO CONTACT

You ll soon be arriving in Paris, thank you for choosing our airport for your arrival. This briefing was made to make your arrival as flawless and

Amsterdam Schiphol. Real Flight Event 21 st of May Introduction. This document is provided by IVAO-NL Flight Operations Department.

Stockholm Control Requirements

United Arab Emirates Division of IVAO Rev. 1.1 May 13, 2016 Dubai Pilot Guide. Page 1 of 16. Dubai Pilot Guide. Dubai_PilotGuide_rev.1.1.

Pilot Information. Vienna int. Airport LOWW

Departures to the south from Runways 16L and 16R.

PF3 ATC at its best Version History

Airport Guide to Greenland

Pilot Briefing Manual. Εγχειρίδιο Ενημέρωσης Πιλότων

CHAPTER 7. AIRSPACE 7.1 AFFECTED ENVIRONMENT

LETTER OF AGREEMENT BRATISLAVA / BUDAPEST APPROVED BY ISSUED ON VALID FROM VERSION NR. 1.3 ( ) VALID UNTIL WITHDRAWAL

ICAO Standard Phraseology A Quick Reference Guide for Commercial Air Transport Pilots

IFR Operators Briefing Pack. May 2013

For Flight Simulation purposes only on the VATSIM Network.

Düsseldorf RG Airports

CHICAGO MIDWAY INTERNATIONAL AIRPORT (KMDW) STANDARD OPERATING PROCEDURES

LOWS - EPWA ONLINE FLIGHT TUTORIAL. CHILD.COM Page 1 CONTENTS. Air-Child Virtual Airlines ONLINE FLIGHT TUTORIAL

Information to VFR pilots

NAMIBIAN RADIO LICENSE VALIDATION

UK AIRSPACE Introduction

IFR Communication Procedure

Real Time Simulation Oslo ASAP

MANUAL OF S1 CLEARANCE DELIVERY AND GROUNG SERVICE

Do you know exactly how the communication with an aerodrome controller in a foreign country should look like? No? If not, this list might help you.

SECTION 2 - GENERAL. Callsign. Tower Control Service Tower _TWR Active Runway(s) & ATZ/CTR. Approach or Departure or Radar Area or Radar

User Forum EUROCONTROL s Brussels HQ. 18 January 2011 CDM@CDG

FINAL REPORT. Radio call sign: Date and time: Sunday 23 October 2005, at time 2110 Oslo Airport Gardermoen (ENGM) Norway

AIRSPACE EXPLAINED. Separation of Traffic

LONDON SOUTHEND AIRPORT CLASS D CONTROLLED AIRSPACE GUIDE

AD 2-LGML-1 GREECE 12 NOV 2015 LGML AD 2.1 AERODROME LOCATION INDICATOR AND NAME LGML - MILOS

Oostwold Airshow 2015

2014 NIFA CRM Contestant Briefing Guide San Diego, California

AIRCRAFT NOISE ABATEMENT OPERATING PROCEDURES AND RESTRICTIONS

SANTOS DUMONT ENGLISH ASSESSMENT IDENTIFICATION

Airways New Zealand submission to the Civil Aviation Authority's 2016 Manawatu Airspace Review

Radio Communications in Class D Airspace by Russell Still, Master CFI

Chapter 15. Airports Authority of India Manual of Air Traffic Services Part EMERGENCY PROCEDURES

VATSIM CODE OF CONDUCT

Airport Charges and Handling Fees. AIRPORT DEBRECEN Kft.

NOTAM. Pilots from Aboard. Flight Information Service

SESAR Air Traffic Management Modernization. Honeywell Aerospace Advanced Technology June 2014

National Transportation Safety Board Washington, DC 20594

AVIATION TRAINING ACADEMY

Contents VoxATC Reference... 31

VATSIM CODE OF CONDUCT

Airport Modelling: Capacity Analysis of Schiphol Airport in 2015

Tauranga, Bay of Plenty

NORWAY AIP AIRAC SUP 14/15 EFF 20 AUG TEL:...(+47)

ENR 0.6 TABLE OF CONTENTS TO PART 2 - ENR

International Civil Aviation Organization. The Third Meeting of the Regional ATM Contingency Plan Task Force (RACP/TF/3)

EGTR ELSTREE EGTR AD 2.1 AERODROME LOCATION INDICATOR AND NAME EGTR AD 2.2 AERODROME GEOGRAPHICAL AND ADMINISTRATIVE DATA

A-CDM from an airport perspective Oslo Airport

Selfbriefing for Operational Procedures

Aircraft incident at Helsinki-Vantaa airport on

AN AIRCRAFT TAXI SIMULATION MODEL FOR THE UNITED PARCEL SERVICE LOUISVILLE AIR PARK. W. Swain Ottman Angela C. Ford Gregory R.

Airspace. Chapter 14. Introduction

This section includes performance data on the King Air B200. Information consists of:

Southwest Texas Regional Advisory Council Air Medical Provider Advisory Group (AMPAG)

CTAF PROCEDURES GUIDE

Familiarisation Briefing for Jet and Multiengine Aircraft Crews.

Background on Airspace

Airspace Change Communications and Consultation Protocol Protocol

Setting up VRC. Getting started with the Virtual Radar Client (VRC)

TLPL VIEUXFORT/ Hewanorra/ST. LUCIA

ASTIS ONE ALFA (ASTIS 1A) [ASTI1A] ASTIS ONE BRAVO (ASTIS 1B) [ASTI1B] ATLAN ONE ALFA (ATLAN 1A) [ATLA1A] ARRIVALS ASTIS 1A ASTIS 1B SNI SANTORINI

Tours Reporting System (Divisional) English version

Breakdown of separation near Melbourne Airport, Victoria 5 December 2010

AVIATION INVESTIGATION REPORT A07A0025 LOSS OF SEPARATION

Melbourne city area noise information pack

years in the community

Multi-Engine Training And The PTS

Airspace classification change

Ms. Jarrette reported that operations at OEA, with inquiries/complaints. These approaches to runways 07 and

AIRSPACE INFRINGEMENTS

8-1 Chapter 8 Radio Operations: Aviation Spoken Here

This is the fourth of a series of Atlantic Sun Airways CAT B pilot procedures and checklists for our fleet. Use them with good judgment.

1.1 The circumstances of each aircraft emergency can vary to such an extent that detailed instructions cannot be given for every situation.

The Mayor of London s Submission:

A Flight Bodo Mo i Rana with Wideroe of Norway

TP 308 IMPACT STUDY TORONTO BILLY BISHOP/TORONTO CITY AIRPORT. for

ILS Replacement. ACI World Safety Seminar November 2008 Kempinski Hotel Beijing Lufthansa Centre

SPECIAL RULES ZONE (SRZ) ON BEHALF OF THE TEXEL AIRSHOW 2007

Checklist MS FSX incl. Wilco E-Jet Series

MASTER PLAN PREPARATION

Page 2 of 7 SPKT FIGURE CHANGES

EKBI. Runways: Runway 09 Takeoff length: 3100, Landing length: 2950 Runway 27 Takeoff length: 2950, Landing length: 2950

IBAC Bulletin B00-2 Pacific Implementation of RVSM and RNP 10/50NM Lateral

Airspace E. update. Controlled airspace in which IFR and VFR traffic is permitted

Part 150: Records of Approval

on a dark night departure

SULAYMANIYAH INTERNATIONAL AIRPORT MATS CHAPTER 19. April 2012 Prepared By Fakhir.F. Mohammed Civil Aviation Consultant

This is the third of a series of Atlantic Sun Airways CAT B pilot procedures and checklists for our fleet. Use them with good judgment.

AVIATION INVESTIGATION REPORT A02P0004 OPERATING IRREGULARITY

Transcription:

2015 LOP - OSLO TMA & GARDERMOEN TWR Local operating procedures for: Gardermoen Delivery, Ground and Tower Oslo Approach, Director and Final

LOP Oslo TMA/Gardermoen MAJOR AIRPORT REQUIREMENTS GLOBAL RATING POLICY From 1st Of January 2010 the new Global Rating Policy was enforced on the VATSIM network. In this policy all ratings on VATSIM are listed and described. We have the controller ratings (S1, S2, S3, C1 and C3), administrative ratings (INS1, INS2, INS3, SUP and ADM). On top of these comes the Major Airport and Special Center endorsement. These endorsements are needed to operate on a Major Airport or Special Center positions in some VACC s. An airport is classified as Major Airport by the local VACC, these airports have more complex procedures and do also have more and constant traffic then the normal airports. Usually Major Airports are the capital airports. MAJOR AIRPORT ENDORSEMENT (MAE) In Norway, a Major Airport endorsement is needed to operate on Oslo Airport Gardermoen regardless of which controller rating you possess. To accomplish MAE for Gardermoen you need to request this through the Training Department. You will be given a mentor/instructor, who will do the training with you and when all aspect are covered this will be fulfilled with a MAE Checkout. When the MAE checkout is passed you will be allowed to operate at Gardermoen alone. We have Tower MAE and Approach MAE. You need Tower MAE to begin on Approach MAE. Tower MAE is needed to man the following positions: Gardermoen Tower Gardermoen Ground Gardermoen Delivery Approach MAE is needed to man the following positions Oslo Approach Oslo Director Oslo Final Oslo Control The Global Rating Policy is found here: http://vatsim.net/ec/grp2.pdf

GARDERMOEN AIRPORT PROCEDURES This section will cover the procedures applied in Gardermoen Tower. The tower is divided into three main positions, some which can be divided further: Gardermoen Tower (handles runways and Gardermoen CTR) Can be divided into Tower West/East Gardermoen Ground (Handles movement on ground except runways and GA park.) Can be divided into Ground West/East Gardermoen Delivery (Handles clearances) Position description - Delivery Gardermoen Clearance Delivery, hereby called DEL, issues departure clearance to all IFR traffic at Oslo airport. On request by pilots, DEL can also issue engine startup, however the aircraft is usually instructed to report ready for Push and start to Gardermoen Ground, hereby called GND. DEL is responsible for transfering traffic to the correct GND frequency when GND is divided into West and East. A new terminal is under construction at Gardermoen. Freeware and payware scenery with the new scenery is available, so we have started to use these changes on VATSIM. Traffic west of the construction area shall be transferred to GND West Traffic east of the construction area shall be transferred to GND East Traffic on the GA Parking west of 01L/19R is transferred directly to TWR West.

Log-on information Delivery shall log on as ENGM_DEL with frequency 121.67 Runway configuration for departures DEL/GND/TWR shall issue SID-clearances according to the tables below: RUNWAY 01L/R Jet aircraft and propeller aircraft with 4 engines or more: SID ENDPOINT RWY SID NUVSA 01L/R NUVSA xa/yb MASEV 01L/R MASEV xa/yb OKSAT 01L/R OKSAT xa/yb TOR 01L/R TOR xa/yb ATLAP 01L ATLAP xa EVTOG 01L EVTOG xa Propeller aircraft with less than 4 engines: SID ENDPOINT RWY SID NUVSA 01L NUVSA xa MASEV 01R MASEV yb OKSAT 01R OKSAT yb TOR 01L VEMIN xa-tor Transition/ TOR yb ATLAP 01L VEMIN xa-atlap transition EVTOG 01L VEMIN xa-evtog transition

Runway 19L/R Jet aircraft and propeller aircraft with 4 engines or more: SID ENDPOINT RWY SID NUVSA 19L/R NUVSA xc/yd MASEV 19L/R MASEV xc/yd OKSAT 19L/R OKSAT xc/yd TOR 19L/R TOR xc/yd ATLAP 19R ATLAP yd EVTOG 19R EVTOG yd Propeller aircraft with less than 4 enigines: SID ENDPOINT RWY SID NUVSA 19L/R VIBUK xc-nuvsa transition VEMIN yd-nuvsa transition MASEV 19L/R VIBUK xc-masev transition MASEV yd OKSAT 19L/R VIBUK xc-oksat transition OKSAT yd TOR 19L/R TOR xc VEMIN yd-tor transition ATLAP 19R VEMIN yd-atlap transition EVTOG 19R VEMIN yd-evtog transition

Omni-direcitonal departures Traffic unable to follow a SID shall be issued the following departures: RWY 01L: Climb RWY track to 1700ft, turn left to track 340 degrees, climb to 4000ft. RWY 01R: Climb RWY track to 1700ft, turn right to track 070 degrees, climb to 4000ft. RWY 19L: Climb RWY track to 1700ft, turn left to track 160 degrees, climb to 4000ft. RWY 19R: Climb RWY track to 1700ft, turn right to track 240 degrees, climb to 4000ft. Note: Any deviation from the standard SID assignment or Omni directional deparures is subject to approval from Oslo Approach. Night restrictions Local time Jet arrivals Jet departures Prop arrivals Prop departures 2230-2400 01R/19R 01L/19L 01L/19R 01L/19R 2400-0630 01L/19R 01L/19R 01L/19R 01L/19R Note: Propeller aircraft with 4 engines or more shall be handled as jet a/c VFR Departures All VFR departures are handled by TWR. Position Description Ground Gardermoen ground is responsible for startup, pushback and all movements on the ground, except the GA area. When an aircraft is ready for taxi, taxi clearance shall be issued to the respective runway, when the a/c is entering the taxiway paralell to the runway, it shall be transferred to the correct tower controller, either TWR W (01L/19R) or TWR E (01R/19L) Log-on information The primary ground position is ENGM_W_GND (or just ENGM_GND) on 121.600 Even though you do not expect a split, it is concidered good practice to use _W_ in your callsign, to be ready for a potential split up. The second ground controller logging on, shall log on as ENGM_E_GND on 121.900

Ground area of responsibility Ground West is responsible for traffic west of the construction area. Ground East is responsible for traffic east of the construction area. Tower is responsible for Traffic on the GA Parking west of 01L/19R. Stands and parking Gardermoen has got one terminal (one more terminal is under construction) with two piers. The western pier is domestic and the eastern is international. Cargo traffic parks at the cargo apron found southwest of the terminal, east of taxiway November. Military aircraft parks at the MIL area found north of the terminal, east of November. General aviation traffic is parked at the GA Area west of runway 01L/19R. Domestic stands Domestic traffic on Gardermoen is usually operated by Widerøe, Scandinavian SAS and Norwegian. There are no airline-specific stands; all stands can be operated by anyone. The stand assignment is done by stand availability and size of the aircraft. Stands without jet-bridges: Code CP aircraft (commuter propeller, max D Q400) Stand:2,3,7 Code C aircraft (max B-737-900) Stand:9, 10, 12, 76, 80, 84,, 88, 92, 172, 173, 174, 175, 176, 177, 178 and 179 Code D aircraft (max MD11 / B-767-400) Stand: 171 CODE E aircraft (max B 747-400) Stand: 171L Stands with jet-bridges: Code C aircraft (max B 737-900) Stand: 11, 13, 14, 15, 16, 18, 20, 22 and 30 Code C aircraft including B 757-200 without winglets: Stand 24 and 26 International stands International traffic on Gardermoen is operated by several airliners and there is no point of listing them all up. The stand assignment is done by stand availability, size of the aircraft and also schengen vs. non-schengen. Stands without jet-bridges: Code C aircraft (max B-737-900) Stand: 181, 182, 183, 184 and 187 Code D aircraft (max MD11 / B-767-400) Stand: 185 CODE E aircraft (max B 747-400) Stand: 186

Stands with jet-bridges - schengen: Code C aircraft (max B-737-900) Stand: 39, 40, 41, 42, 44, 45, and 47 Code C aircraft including B 757-200 without winglets: Stand 38 and 43 Code C aircraft including B 757-200 with winglets: 46 Code E aircraft (max wingspan 61m, max length 64m) Stand: 48 and 49 Code E aircraft (max B 747-300) Stand: 46R Stands with jet-bridges non-schengen: Code E aircraft (max wingspan 61m, max length 64m) Stand 51 Code E aircraft (max B 747-400) Stand: 50 and 53 Cargo stands DHL, UPS, FedEx, TNT, Korean Air, SAS, KLM, Lufthansa and many more operates at the cargo facilities at Oslo Gardermoen. Five heavy stands is available at the Cargo apron. Code C aircraft (Max 737-900): Stand: 201, 202, 203, 204 Code D aircraft (max MD11 / B-767-400) Stand: 205, 206, 207 and 208 Code E aircraft (max B 747-400) Stand: 208R Code F aircraft (747-8, A380) Stand: 203L GA and MIL stands Traffic is not given specific parking slots, taxi to GA or taxi to MIL is commonly used. Position description Tower Gardermoen Tower, hereby called TWR, is responsible for movements on the runways, GA-area and also within Gardermoen CTR. TWR issues takeoff and landing clearances, and is also responsible for separation of departing traffic, and arriving traffic after transferred from Oslo Approach. TWR uses radar, and is responsible of checking that departing traffic is squawking the assigned code and that the transponder is turned on, before transfering the traffic to Oslo Approach. Log-on information The primary tower position is ENGM_W_TWR (or just ENGM_TWR) on 118.300 Even though you do not expect a split, it is concidered good practice to use _W_ in your callsign, to be ready for a potential split up. The second tower controller logging on, shall log on as ENGM_E_TWR on 120.100

Departure separation Departures shall be transfered to Oslo Approach, separated in accordance with the table below: 3NM constant or increasing 5NM constant or increasing RWY Succeding departures on different SIDs Succeding departures on the same SID Departures on any SID behind TORyB, ATLAPyB, EVTOGyB Succeding departures on NUVSAyD, MASEVyD, OKSATyD 01L/R 19L/R 01R 19R Note: VEMINxA, VEMINyD and VIBUKxC shall be considered to be the same SID regardless of transition. Coordination Handoffs to TWR: Departing traffic is handed over by GND at the earliest when entering the taxiway paralell to the runway, latest when reaching the holding point. For arriving IFR traffic radio communications shall be handed over as early as practicable after the aircraft is established on final approach, and no later than at 6 NM final. Arriving VFR traffic should be cleared to a CTR entry point by APP. Tower will give clearance to enter the CTR. Handoffs from TWR: TWR is responsible to check that departing aircraft are squawking mode C and the assigned code, and correct it if necessary. TWR is responsible to ensure that departures are correctly separated before handoff. Radar control for Departures shall be transferred as soon as practicable and no later than; DME 6 (GRM), 5000 FT or cleared altitude, if this is lower whichever comes first Radar control for Missed Approaches shall be transferred as soon as practicable and no later than DME 6 (GRM) Landing aircraft will be transferred to GND as soon as practicable.

OSLO TMA - PROCEDURES

Traffic in Oslo TMA is controlled by Oslo Approach. The reason it is not called Gardermoen Approach is because it is not situated at the airport itself, but at Norway ACC, Oslo. Oslo approach can be divided into 4 smaller sectors: Oslo APP West (Covers the west side of the TMA) Oslo APP East (Covers the east side of the TMA) Oslo Director (Covers the sequencing fans) Oslo Final (Covers traffic from when they leave the sequencing fans until established on approach) Log-on information The primary approach position is ENGM_W_APP (or just ENGM_APP) on 120.450 Even though you do not expect a split, it is concidered good practice to use _W_ in your callsign, to be ready for a potential split up. You can not split into West/East before you have a director. So the next logical split would be to log in as director with ENGM_D_APP on (119.970) The next logical split is to open the east approach sector with ENGM_E_APP on 118.470 Finally you can open the Final position with ENGM_F_APP on 128.900 Position Description Approach Handoffs to Approach: Handoffs from tower: See handoffs from tower in the tower section. Norway ACC, Oslo will transfer all arrivals to APP, cleared for their respective STAR, descending FL120. Arrivals may also be cleared by Norway ACC, Oslo direct to the relevant fix on the TMA border. Separation between traffic on same STAR shall be 10nm constant or increasing, unless otherwise coordinated. Traffic on the short STARS (from the north when 19 in use, from the south when 01 in use) shall be handed off directly to Director if online. Note: Traffic with cruising lower than FL120, and traffic not able to follow STAR, is subject to coordination. Handoffs from approach: From approach to tower: See handoffs to tower in the tower section. Oslo approach shall transfer all departures to Norway ACC, Oslo, climbing to FL210 or crusing level if lower.

Oslo approach may give direct routings to departing traffic, according to the table below: ENGM SID RWY 01 SID TMA-Sector Direct routing Receiving ACC-sector NUVSA xa* EAST PEMUS NUVSA yb EAST LILBA MASEV xa* / MASEV yb EAST MASEV S6 OKSAT xa* / OKSAT yb EAST OKSAT S4 TOR xa / VEMIN xa WEST NANON TOR yb EAST KUBUB S4/(Farris WEST/EAST) ATLAP xa / VEMIN xa WEST ATLAP yb EAST ATLAP S6 EVTOG xa / VEMIN xa WEST EVTOG yb EAST EVTOG * Flights on these SIDs enter TMA WEST after departure, but is released to TMA EAST for climb and right turn

ENGM SID RWY 19 SID TMA-Sector Direct routing Receiving ACC-Sector NUVSA xc / VIBUK xc EAST LILBA NUVSA yd / VEMIN yd WEST GM443 MASEV xc / VIBUK xc EAST S6 MASEV yd WEST MASEV OKSAT xc / VIBUK xc EAST OKSAT OKSAT yd WEST GM608 S4 TOR xc EAST KUBUB TOR yd / VEMIN yd EAST NANON S4/(Farris West/East) ATLAP yd / VEMIN yd ATLAP xc* WEST WEST ATLAP EVTOG yd / VEMIN yd WEST S6 EVTOG xc* WEST EVTOG * Flights on these SIDs enter TMA EAST after departure, but is released to TMA WEST for climb and right turn Procedures for arrivals Runway assignment for arrivals Domestic arrivals should be assigned to the western runway (01L/19R) International arrivals (except military traffic and GA traffic parking on the GA area) should be assigned to the eastern runway (01R/19L) Coordination between APP, DIR and FIN APP will descend traffic to the correct altitude according to what STAR they are following. (see illustrations on next page).

When the aircraft is clear of any conflicting departing traffic, and before entering the sequencing fans, APP shall transfer the traffic to DIR. The traffic is concidered fully released when transfered. DIR will, when traffic allows, clear traffic direct to the merge point, descending to 7000ft. The traffic is then handed off to FIN. FIN does the last sequencing and vectoring for approach. Altitudes and Coordination points for inbound traffic - runway 01

Altitudes and Coordination points for inbound traffic - runway 19

Night restrictions Local time Jet arrivals Jet departures Prop arrivals Prop departures 2230-2400 01R/19R 01L/19L 01L/19R 01L/19R 2400-0630 01L/19R 01L/19R 01L/19R 01L/19R Note: Prop aircraft with 4 propellers or more shall be handeled as jet a/c. Procedures for coordination between Oslo APP and Farris APP. Traffic to ENTO and ENRY from the north will by Norway ACC, Oslo be cleared to route PIVAT-BAMIX and descend to FL220 if cruising level is above FL215. Oslo APP will clear the traffic for descend to FL100, and clearance for the correct STAR. Last updated: 27.01.2015 ACCSCA4 DIRECTOR OF NORWAY FIR DANIEL KLEPP