GEN | General Operating Instructions

Required knowledge

1.     ANNEX 2
2.  ANNEX 11
3.  DOC 4444
4.   DOC 7030

CHAPTER 1 Altimeter Setting Procedures

1.1 Altimeter Setting Procedures

1.1.1 Departing Aircraft

Departing aircraft should state the ATIS INFO letter on first contact with DEL or the relevant controller. If they don't, it should be
issued by the DEL or the relevant controller. Aircraft should be informed of any subsequent change to the
QNH at the earliest opportunity.

1.1.2 Arriving / Transiting Aircraft

At or below the Transition Altitude, an aircraft’s vertical position will be controlled by
reference to the Ben Gurion QNH. Aircraft will be issued the QNH once cleared to descend to
an altitude by Tel Aviv or Ben Gurion APP. Aircraft should be informed of any subsequent change to the QNH at the earliest opportunity.

1.1.3 Transition Altitude/Level

The Transition Altitude (in the LLLL FIR) is 18,000 feet AMSL.
When flying above land, the transition altitude is set to 35,000ft.

Note: From here on, unless otherwise specified, vertical references are measured in ft are to be assumed as altitudes AMSL.

CHAPTER 2 All Weather Operations

2.1 Low Visibility Procedures (LVP)

2.1.1 Enforcement

Pilots will be informed when these procedures are in operation by ATIS or by R/T. 

ATC Low Visibility Procedures must be applied when the RVR is less than 800m (or visibility below 1200 meters).

2.1.2 Runway Visual Range (RVR)

The RVR is measured at three points along each runway: at the touchdown zone, mid-point,
and stop-end. The minimum RVR that can be measured is 50 m, and the maximum is 1500 m.

Only the touchdown zone RVR value is published in METARs; the remaining two RVR
values are ‘unknown’ to VATSIM network controllers. When LVP is in force, pilots should be
informed of the reported RVR and any subsequent updates.

CHAPTER 3 Description of Airfield

3.1 Aerodrome Geographical Data

3.2 ATC Communication Facilities

3.2.1 Aerodrome Control (ADC)

3.2.2 Approach Control (APC)

3.3 Logon Order

3.3.1 Aerodrome Control

TWR DEP is the primary tower and should be opened in the first instance. Before TWR is split,
RWY 21 must be in use, and there must not be a single RWY OP active.

GND West is the primary position, and after that, GND East may open, and only then BGN DEL.

3.3.2 Approach Control

APP may be staffed at any time.
When APP is staffed, TMA may split
DEP may open only when TMA is staffed, and the following configuration is not active: 08/08,26/12,12/12

TMA is last in priority to be staffed

3.4 Radio Navigation and Landing Aids

CHAPTER 4 Use of Runways

4.1 Preferential Runway System

Runway 26 is the preferred runway for departure.

Runway 21 is the preferred runway for arrival during the day, but due to Noise abatement procedures & winds, there is a rotation between RWY30, RWY21, and RWY12.

At night, RWY12 is the preferred runway for ARR due to noise-abatement procedures

Tailwind at or above 5KTS shall initiate a change of active ARR runway.

4.2 Change of Runway Configuration

When there is a change of runway configuration, TWR DEP shall initiate contact with DEP to agree on a last arrival and time for the runway change. DEP shall confirm with all APC stations about the change of configuration.

Based on this time, TWR DEP shall coordinate with GND\DEL as to the last departure. GND\DEL will re-clear any previously cleared aircraft that will now depart on the new runway.

TWR DEP shall inform DEP of the intended last 3 (if appropriate) departures before, and the first departure after, the runway change (callsign and routing).

DEP will inform TWR DEP when the runway change is completed.

4.3 Use of the Non-Duty Runway

Aircraft can land on the departure runway if technical or safety reasons preclude using the
nominated arrival runway or to try and avoid a missed approach.

Opposite-direction departures and approaches are not permitted except in an emergency.

CHAPTER 5 Use of STOP-BAR

Each controller shall use the system in the following procedure 

TWR - The controller will turn on or off the STOP-BARS of the active runways

GND EAST\GND WEST - The controller will turn on or off the STOP-BARS of the taxiways in his Area of control or of the active runways if he has permission to cross or enter said runways.

CHAPTER 6 Priority of traffic

Controllers at BGN airport shall follow the following sequence of priority:

1. Emergency - If the controller will accept the emergency
2. Plane in Final approach (Instrument approach) or in Final leg in VFR approach
3. Ambulance\red arrow (Military ambulance)\SAR (Search and rescue) - That traffic is not committed to CRM limitation
4. Firefighting traffic - Orange Arrow
5. Operational Police flights - Blue Arrow
6. VIP flights  - That traffic is not committed to CRM limitation
7. Commercial Passengers or Cargo flights
8. Non-operational Police flights
9. Electrical Arrow
10. Test Flight
11. Agriculture Flight
12. Green Arrow
13. General Aviation flight
14. Training Flight
15. Any other type

Note: When a higher-priority flight crosses a cruising flight, there shall be considered a change of altitude for the lower-priority flight.

CHAPTER 7 Relief of controller

When a controller shift change is in motion the relieving controller shall connect as relief callsign (for example LLLL__CTR instead of LLLL_CTR). When the relieving controller is connected, the relieved controller shall initiate the briefing  in the following format:

	Weather conditions (Alerts, ATIS, Pilots reports)
	NOTAM and special information
	Runway configuration and sector management
	Runway conditions (Open\Close\Occupied)
	System status (ILS,GNSS,VOR)
	Traffic management and Traffic limitations
	Special Activity in the sector
	Traffic (Airborne, Ground, Expected)