GEN | BGN ADC <-> BGN APC LoA

1. Method

1.1 Directioning after takeoff or go-around

1.1.1 Shall be given to the plane as clearance before departure/go-around or after departure/go-around

1.1.1.1 The heading will be given by the TWR controller with the instruction of the APC controller

1.1.1.1.1 If the heading is given for safety reasons, the TWR controller will do so at his discretion and update the APC controller about the details of the clearance as soon as possible.

1.1.1.2 Directioning is approved in the following situations:

1.1.1.2.1 Safety

1.1.1.2.2 Weather bypassing

1.1.1.2.3 Bypassing of non-RNAV-capable plane

1.1.1.2.4 Optimize routing of prop-based planes, business jets, and helicopters

1.1.1.2.5 Optimize routing of regional traffic.

1.1.1.2.6 Go Around

1.1.2 Conditions for Directioning

1.1.2.1 When departing from RWY 30 or 26, the left turn will be limited to 1000ft

1.1.2.2 When departing from RWY 30 or 26, the right turn will be limited to 600ft

1.1.2.3 When departing from RWY 08, 12, or 08, the right turn will be limited to 1000ft

1.1.2.4 When departing from RWY 08, 12, or 08, the left turn will be limited to 600ft

1.1.2.5 When the visibility is 5 km or more, and the ceiling is 1,600 ft or greater

1.1.2.5.1 The turn is approved from each runway and to each sector

1.1.2.6 When the visibility is less than 5 km or/and the ceiling is below 1,600 ft 

1.1.2.6.1 The directioning is approved when departing/Go-Around from runway 30 or 26 only.

1.1.2.6.2 The turn from the extended centerline (of the DEP RWY) to the right until heading 330

1.2 Release

1.2.1 TWR will request a release from DEP before the departure of the plane.

1.2.1.1 Section 1.3 specifies the types of traffic that require a release before departure

1.2.2 TWR may take off traffic that got a release under the following conditions:

1.2.2.1 Wake turbulence (WT) limitations are followed (Further information at ADC sections)

1.2.2.2 Section 1.3 is followed - Minimum separation between planes departing to APC and at section 1.6 Responsibilities of following separation

1.2.2.3 Maintaining legal separation as published in (DOC 444 - Chapter 7 - Procedures for Aerodrome control service, section 7.9.12 - separation of departing aircraft, Section 7.9.3 Take-off clearance)

1.3 Stop Automatic Release, Automatic Release

1.3.1 The aerodrome shall be managed either in Stop Automatic Release or in Automatic Release

1.3.2 Unless APC advises otherwise to TWR, the aerodrome will be managed in Automatic Release in the following configurations: 08/08, 12/12, 26/12, 26/21, 26/26, 26/30, 30/30.

1.3.3 In the condition of Automatic Release, no Release is required for departing planes to APC except for:

1.3.3.1 Plane with different IFR (ALTITUDE and\or SID and\or after takeoff vectors) from the clearances written in section 1.12 Clearance Prior Taxi

1.3.3.2 Plane with VFR for climb above 2000 ft'

1.3.3.3 Plane departing with its preceding plane slower than it, a prop plane, or a plane that didn't follow SID.

1.3.3.3.1 If the preceding plane crossed the coastline or crossed 4000 ft, there is no requirement to request release from APC

1.3.3.4 Plane with clearance for heavy takeoff (See section 1.3.3.3.1)

1.3.3.5 Bedek flight

1.3.3.6 Plane that departs from "non-active" runway, except that the rule is for a plane departing from 30 when the airport is active at 26\30 configuration

1.3.3.7 The first plane departing after change of runway for departures

1.3.3.7.1 If 10 minutes have passed since the change of departure runway, no release is required

1.3.3.8 Plane departing on SID RIPUD when runway 21 is in use for landing or when RNP-X\ILS via LIMKO is in use 

1.3.3.9 International flight going to south ACC with separation lower than required in the LOA (10 min for same destination, 5 min for LLER)

1.4 Minimum separation between two departing Traffic to APC from the same RWY unless approved otherwise by APC

1.5 VFR flight

1.6 Responsibilities of following separation

1.7 Reduction of separation minima between departing and arriving aircraft at 26/12

1.8 Roles of TWR to APC

1.8.1 Will advise on the runway configuration

1.8.2 Will advise on any delay (On CRM conditions) or rejected takeoff

1.8.3 Will advise on go-around and report the clearance the plane received and/or will ask for further clearance

1.8.4 Will coordinate Clearance for IFR plane who isn't departing on SID

1.8.5 Will coordinate Departure of planes in reduced separation than written above

1.8.6 Will advise on taxi of ambulance flight or VIP

1.8.7 Will advise when runway closure is in effect

1.9 Roles of APC to TWR

1.9.1 Will annonce "Stop\Resume Automatic Release"

1.9.2 Will approve\reject Release request

1.9.3 Will coordinate landing on a non-active runway

1.9.4 Will advise landing on a non-active approach (As published in ATIS)

1.9.5 Will advise on entry of VFR flights to LLBG

1.9.6 Will provide clearance to IFR traffic who isn't departing on SID

1.10 Roles of DEL to APC

1.10.1 Will pass information about BEDEK flight (From BEDEK HELIPAD/APPRON only!) and will get clearance for the flight

1.10.1.1 The actual clearance will be given to the pilot only after APC approves the flight

1.10.2 Will update on the plane that requests ASSIF/BIRIM

1.10.3 Will update about planes that cannot follow SID requests

1.10.4 Will update about changes in the QNH and changes to the landing runway in the ATIS

1.11 Roles of APC to DEL

1.11.1 Will provide SSQ codes for VFR planes departing from LLBG

1.11.2 Will advice about start\ending of usage in Q30 (BIRIM) or T80/T84/T85 (ASSIF)

1.11.3 Will advise when BEDEK flight is (From BEDEK HELIPAD/APPRON only!)

1.11.4 Will pass the details of irregular departures from LLBG