# APC | Approach Control

## <span style="color: rgb(35, 111, 161);">**Chapter 1: Area of Responsibility and Sector Organisation:**</span>

### <span style="color: rgb(35, 111, 161);">**1.1 General**</span>

<span style="color: rgb(0, 0, 0);">In this section, the following conventions for the naming of the Ben Gurion Group sector  
positions is adopted:</span>

<span style="color: rgb(0, 0, 0);">A or D - Departure or arrival</span>

<span style="color: rgb(0, 0, 0);">T - TMA Controller</span>

#### <span style="color: rgb(35, 111, 161);">**1.1.1 Area of Responsibility**</span>

<span data-path-to-node="3,0">The primary area of responsibility for Ben Gurion Approach is the Ben Gurion Terminal Movement Area (TMA)</span><span data-path-to-node="3,1"><sup class="superscript"></sup></span><span data-path-to-node="3,2">. The TMA is defined as a Terminal Control Area centered around the aerodrome, utilised by the approach controller to safely sequence and manoeuvre arriving, departing, and transiting aircraft</span><span data-path-to-node="3,3"><sup class="superscript"></sup></span><span data-path-to-node="3,4">.</span><bdi class="source-title"></bdi>

<span style="color: rgb(35, 111, 161);"></span>

- <span data-path-to-node="4,0,0,0">**Vertical Limits:** The TMA extends from the specified lower limits up to a maximum altitude of 10,000 feet AMSL at its peak</span><span data-path-to-node="4,0,0,1"><sup class="superscript"></sup></span><span data-path-to-node="4,0,0,2">.</span>
    
    <div _ngcontent-ng-c3713862721="" class="source-inline-chip-container luminous-sources hide-from-message-actions ng-star-inserted">  
    <button aria-label="View source details. Opens side panel." class="button multiple-button ng-star-inserted"></button></div>
- <span data-path-to-node="4,1,0,0">**Airspace Boundaries:** The TMA altitudes are strictly defined to separate different airspace jurisdictions</span><span data-path-to-node="4,1,0,1"><sup class="superscript"></sup></span><span data-path-to-node="4,1,0,2">. Below the TMA, the airspace accommodates local aerodromes and CVFR routes</span><span data-path-to-node="4,1,0,3"><sup class="superscript"></sup></span><span data-path-to-node="4,1,0,4">. Above the TMA lies the airspace of Tel Aviv Control (LLLL\_CTR) and military (IAF) sectors</span><span data-path-to-node="4,1,0,5"><sup class="superscript"></sup></span><span data-path-to-node="4,1,0,6">. Controllers must exercise caution to ensure aircraft do not exceed the vertical limits of the TMA</span><span data-path-to-node="4,1,0,7"><sup class="superscript"></sup></span><span data-path-to-node="4,1,0,8">.</span>
- **Top-Down Responsibilities:**
    
    
    - <span data-path-to-node="4,2,1,0,0,0">**Tel Aviv traingle Airspace:** When Tel Aviv Control (LLLL\_CTR) is offline, Ben Gurion Approach assumes responsibility for the Tel Aviv maritime airspace, strictly limited to traffic departing from or arriving at Ben Gurion</span><button aria-label="View source details. Opens side panel." class="button multiple-button ng-star-inserted"></button>
    - <span data-path-to-node="4,2,1,1,0,0">**Herzliya (LLHZ):** When Herzliya Tower or Pluto Control are offline, Ben Gurion Approach assumes top-down control over Herzliya aerodrome</span><span data-path-to-node="4,2,1,1,0,1"><sup class="superscript"></sup></span><span data-path-to-node="4,2,1,1,0,2">.</span>

[![image.png](https://wiki.vatil.org.il/uploads/images/gallery/2026-05/scaled-1680-/74eimage.png)](https://wiki.vatil.org.il/uploads/images/gallery/2026-05/74eimage.png)

### <span style="color: rgb(35, 111, 161);">**1.2 Function**</span>

<span style="color: rgb(0, 0, 0);">BGN radar position provides services as specified in Israel AIP part "א", sections 1, 7, 5, 2, 3, for both IFR and CVFR traffic within controlled airspace.</span>

#### <span style="color: rgb(35, 111, 161);">**1.2.1 Responsibility of Approach controllers (D\\A APP)**</span>

##### <span style="color: rgb(35, 111, 161);">**1.2.1.1 D APP**</span>

- <span style="color: rgb(0, 0, 0);">Receiving departing aircraft from Aerodrome Control (ADC) and controlling them until transfer of control to the appropriate radar/en-route sector.</span>
- <span style="color: rgb(0, 0, 0);">Provided Runway 21 is not in use, receiving arriving traffic from the radar sector and managing the sequence and radar vectoring to the active approach.</span>
- <span style="color: rgb(0, 0, 0);">Coordinating with ADC regarding the required Minimum Arrival Interval (MAI) and Minimum</span>

##### <span style="color: rgb(35, 111, 161);">**1.2.1.2 A APP**</span>

- <span style="color: rgb(0, 0, 0);">Providing radar vectors or managing the sequence for ILS, Visual, or RNP approaches for Runway 21.</span>
- <span style="color: rgb(0, 0, 0);">Coordinating with ADC regarding the required separation between aircraft on Runway 21.</span>

#### <span style="color: rgb(35, 111, 161);">**1.2.2 Responsibility of TMA controllers (T APP)**</span>

- <span style="color: rgb(0, 0, 0);">Sequencing, separating, and managing the TMA airspace for crossing or departing traffic.</span>
- <span style="color: rgb(0, 0, 0);">Managing Herzliya aerodrome (LLHZ) and all low-level traffic.</span>
- <span style="color: rgb(0, 0, 0);">Sequencing and separating traffic arriving from the east into the main arrival sequence.</span>

### <span style="color: rgb(35, 111, 161);">**1.3 BGN RADAR Bandbox/Splitting Procedures** </span>

#### <span style="color: rgb(35, 111, 161);">**1.3.1 Opening Order**</span>

<span style="color: rgb(0, 0, 0);">D-APP may be staffed at all times</span>

<span style="color: rgb(0, 0, 0);">A-APP may be staffed only when RWY21 is in use for arrival and while there is no single RWY ops active</span>

<span style="color: rgb(0, 0, 0);">T-APP may be staffed after A-APP\\D-APP split, or after the opening of D-APP, when RWY21 is not in use.</span>

#### <span style="color: rgb(35, 111, 161);">**1.3.2 Procedure for Bandboxing/Splitting D APP and A APP**</span>

## <span style="color: rgb(35, 111, 161);">**Chapter 2: Radar Directors – General Operational Procedures:**</span>

## <span style="color: rgb(35, 111, 161);">**Chapter 3: Inbound Procedures:**</span>

## <span style="color: rgb(35, 111, 161);">**Chapter 4: Procedures for Intermediate and Final Approach:**</span>

## <span style="color: rgb(35, 111, 161);">**Chapter 5: Outbound Procedures:**</span>

## <span style="color: rgb(35, 111, 161);">**Chapter 6: Holding &amp; Emergencies:**</span>