Skip to main content

Tower

Keflavik Tower is responsible for BIKF’s runways, and for providing air traffic control service within the Keflavik Control Zone (BIKF CTR).

Runway Configuration

Preferred Runway

At BIKF, RWY 01/19 is preferred for noise abatement. Therefore, if the tailwind component for RWY 01 or 19 is less than 10 knots, TWR may designate RWY 01 or 19 as the active runway.

For similar reasons, landing on RWY 10 & departing on RWY 28 may be approved (traffic permitting) for noise abatement.

Dual Runway Operations

During periods of heavy traffic, Keflavik Tower may, in coordination with Keflavik Approach, implement dual runway operations at BIKF. There are two variations of dual runway operations:

  • Upon Request: Designating one runway as the active runway, but permitting departures/arrivals on the other runway on request.
  • Dual Operations: Using one runway for all arrivals, and the other for all departures.

During such operations, Keflavik Tower & Keflavik Ground shall keep in mind the following:

  • Whenever both runways are active (whether for a one-off departure or arrival, or indefinitely), any blanket crossing clearances automatically become invalid. GND must not instruct aircraft to cross any runway if TWR has not cleared that individual aircraft to do so.
  • Departing aircraft must not be cleared to take off until any landing aircraft on the intersecting runway have cleared the departing runway fully.
    • TWR may verify this visually without coordinating with GND.

Traffic Circuit

The standard traffic circuit for BIKF is east of RWY 01/19, and south of RWY 10/28. In other words, the turn direction of the circuit is Left for RWY 01 & 28, and Right for RWY 10 & 19.

The standard circuit altitude is 1200ft.

Keflavik Control Zone (BIKF CTR)

Screenshot 2023-09-13 at 9.12.09 PM.png

The BIKF CTR ranges from GND – 3000ft. It is directly bordered by the Reykjavik Control Zone (BIRK CTR) to the east, and is surrounded by the Faxi TMA above and to the sides.

VFR Route 6

There is only one VFR route in the BIKF CTR for single-engine aircraft – route 6 to/from BIRK (named “Straumsvik”) at 1000ft. It follows the routing Patterson – Seltjorn – Kuagerdi – Aluminium Factory – Church. The route is bidirectional.

image.png

While the route is named "Straumsvik," it is typically referred to as "route 6" in radio communications.

ForTWR should instruct aircraft leaving BIRK CTR via the VFR departuresroutes onto routereport 6,passing onceKuagerdi. Once airborne, Keflavik TowerTWR should coordinate such aircraft with Reykjavik Tower (BIRK_TWR) to notify them ofbefore the inboundaircraft aircraft, before they reachreaches Kuagerdi.

VFR departures not on a VFR route should be coordinated with either Reykjavik Tower or KeflavikKeflavik/Reykjavik Approach if they will be entering the BIRKBIKF CTR or Faxi TMA, including the TMA buffer zones (see the chapter below).

If an aircraft will not enter the BIRKBIKF CTR, and will remain below the Faxi TMA, it may be released to UNICOM without coordination.

Overlying Airspace: The Faxi TMA

The airspace directly overlying the BIKF CTR is the Faxi TMA – specifically, its Keflavik (KF) sector. The Faxi TMA has “collars” (formerly known as "buffer zones") next to the BIKF CTR which extend down to 1000ft and 2000ft respectively – see the image below:

image.png

Keflavik Tower should coordinate VFR aircraft leaving the CTR into these buffer zones with Keflavik Approach. If a departing aircraft will only briefly enter the buffer zone without entering the TMA itself, and there is no conflicting IFR traffic, Keflavik Approach may simply have Tower release the aircraft to UNICOM.

Neighboring Airspace Areas

Neighboring restricted & training areas include BIR2 (Vestursvaedi), BIR3 (Midsvaedi), Sandskeid, and Sletta. When there is activity in these areas, Tower should add appropriate text to their ATIS NOTAMs, e.g., “GLIDERS OPERATING AT SANDSKEID” or “LIGHT AIRCRAFT OPERATING AT SLETTA.”

See the VFR Guide for more information about these areas.

Next ATS Unit for Departures

All IFR departures should be transferred to Keflavik Approach (BIKF_APP), or whoever is covering it top-down.

Back to top