# APC | Approach\Departure Control
## 1. Area of responsibility
1.1 If ILS 08 is in use, the "PIE" Area is also under the control of APP
1.2 If ILS--30\\RNP-Z--30\\RNP--26\\ILS--26 and after coordination with PLUTO (LLPT\_E), the sector below 6000 ft in the STAR+APP is under the control of BGN APC (further information about that in PLUTO LO)
1.3 When APC is divided into APP and DEP, the area of control is as published in the annexes and in the APC | GEN
1.4 When Tel-Aviv ACC is offline, LLBG\_APP will take control over the triangle area (at LCCC)
## 2. Method of control
2.1 The APC controller will provide RADAR services to traffic in his Area of responsibility
2.2 The APC controller will issue a clearance to accept planes into BGN to Tel-Aviv or South or Pluto or Jordan when there is no Automatic Arrival
2.2.1 Automatic Arrival: when Approach can receive inbound Traffic
2.2.2 Stop Automatic Arrival: when Approach is unable to receive inbound Traffic; in that situation, APP will issue clearances to ACC to send inbound traffic to him or when APP is declaring SAA (BGN-TLV loa is disregarded)
2.3 The APC controller will issue a clearance to TWR when Stop Automatic Release is in effect.
2.3.1 Automatic Release: When A traffic is departing BGN and is in the range of pre-approved types of traffic
2.3.2 Stop Automatic Release: When A traffic is departing BGN isn't in the pre-approved types of traffic or if there has been a go-around or when the DEP (or APC) is declaring SAR. When SAR is in effect, each release is valid for 10 minutes.
2.4 The APC controller will perform TMA Roles and responsibilities when those aren't active
### 2.5 Roles regarding APC TMA
APP\\DEP will inform TMA when there is a holding pattern active in GODED or BGN VOR
### 2.6 Roles and responsibilities when Split is in ACT (irregular due to regular split will include TMA)
#### 2.6.1 APP controller
- Will perform TMA duties in the area of KANER-NAT
#### 2.6.2 DEP controller
1. Is responsible for the departing traffic from BGN
2. Will perform TMA duties (except as mentioned above)
## 3. Standing Agreements
#### 3.1 Tel-Aviv (control)
##### 3.2.1 From Ben Gurion to Tel-Aviv
**STAR allocation:** Tel Aviv control will allocate STAR to Ben Gurion.
**Altitude agreement:**
| From
| Agreement
| Conditions
|
| LLBG SID
| ↑8000ft
| Clear of conflict
|
**Transfer of control:**
| Position
| Conditions
|
| Airborne passing 3500ft
| VIA SID
|
##### 3.2.2 From Tel-Aviv to Ben Gurion
**Altitude agreement:**
| TO
| Agreement
| Conditions
|
| LLBG
| ↓5000ft
| RWY26/21/12/08
|
| ↓6000ft
| RWY30 (VETEK1A)
|
**Transfer of control:**
| Position
| Conditions
|
| 2NM before AMMOS
| RWY26/30/21
|
| 2NM before PURLA
| RWY08
|
| 2NM before NINET
| RWY12
|
#### 3.1 Pluto (control)
**Minimal Segregation zone:** Both Pluto Control and Ben-Gurion will maintain a segregation zone of 2.5 NM from the north border of Ben Gurion TMA
**WT separation from the segregation zone:** When traffic requires WT radar separation, each station will maintain half the required separation from the North border of Ben Gurion TMA
**Arrival Corridor:** When ILS30 \\ RNPZ30 \\ RNP26 \\ ILS26 is in use, and after coordination between Pluto and APC (APP) a corridorof 5NM for each side around the STAR\\APP is transferred to BGN APC (APP).
**Note:** VFR (AZAM) south to MEHLAF EYAL will remain under PLUTO control
## 4. Logon Identification
4.1 Approach controller (APP)
Standard C\\S: LLBG\_APP
Relif C\\S: LLBG\_\_APP
4.2 Departure controller (DEP)
Standard C\\S: LLBG\_DEP
Relif C\\S: LLBG\_\_DEP