Beek Approach

Position Information

ATC CallsignBeek Approach
FRA RequirementAS3
Airspace classD
Minimum Radar Vectoring Altitudeslink

Area of Responsibility:

Beek approach is responsible for arriving and departing traffic which pass through the EHBK TMA. When Beek tower is offline, approach will take over those responsibilities as well.

General Procedures


The main responsibility for Approach is to separate inbound and outbound IFR from each other and depending on the airspace classification separate IFR from VFR or inform IFR and VFR about each other. For approach separation should be at least 3nm or 1000ft.

Delaying traffic

Inbound IFR traffic can be delayed in three ways:

  1. Holdings, ideally use published holdings, for non published holdings the inbound leg and turn direction have to be issued, one holding should take 4 minutes

  2. Vectors, for steering behind a preceding aircraft or to delay by having the aircraft fly more miles

  3. Speed control, most useful to create little amounts of additional separation or to maintain separation, this should not be used to generate a lot of separation

Arriving traffic

Arrivals shall either by flying a full procedural approach or by vectors be guided to a point from where to intercept the instrument approach or a point from where to fly a visual approach. When vectoring for an instrument approach traffic should be on a 30* intercept angle when cleared for the approach, a maximal angle of 45* is allowed if required but shall not be made standard.

Before being cleared for the approach the traffic shall be:

  • ILS: below the glideslope

  • NDB/VOR: at or descending to the published descend profile altitude in such way this altitude is reached in time.

  • ILS/NDB/VOR: On an intercept angle of ideally 30 and maximum 45 degrees.

Once traffic reports either established on the ILS, localizer, inbound course or inbound radial traffic shall be transferred to tower.

Departing traffic

Departing traffic shall at soon as practicable be cleared to climb, without coordination approach shall not clear aircraft above the highest level of is TMA. Approach may clear traffic to leave his SID for safety however the traffic should be put back on the SID before the transfer to ACC, if coordinated with ATC traffic may deviate from the SID direct to a waypoint.

Local Procedures


Beek Approach is responsible for the following airspace:

  • EHBK TMA (1500ft-FL095)


Traffic on the following SID's shall be transferred at or climbing to either FL070 (PESER) or FL090 (OSGOS, BAGSU, RUMER, TENLI) or regarding the LoA's. If the requested cruise level is lower, then on or climbing to cruise level. free of conflict in order of writing:

Rapcon South (EHVK_R_APP), Dutchmil (EHMC_S_CTR), Dutchmil (EHMC_CTR), Amsterdam Radar, EHAA_SW_CTR, EHAA_CTR) or UNICOM

Langen Radar (see LoA) or UNICOM

Brussels control (see LoA) or UNICOM

R/T Examples

Pilot ATC

Departure from Beek:

Beek Approach, TRA779, passing 1800ft, Osgos 1B Departure

TRA779, identified passing 2000ft, climb FL 090

Climb FL 090, TRA779

TRA779, Contact Rapcon South on 123.175

123.175, TRA779

Arrival for Beek:

Beek Approach, PHABC, information Y, 5NM to Osgos, at FL 070

PHABC, information Z, after Osgos direct NW for ILS Runway 21

After Osgos direct NW, for ILS Runway 21, PHABC

PBC, descend to 2000ft QNH 1015

descend to 2000ft QNH 1015, PBC

PBC, cleared ILS approach runway 21

cleared ILS approach runway 21, PBC

PBC, established ILS runway 21

PBC,  contact Beek tower on 119.480

119.480, PBC