Keflavik APP

Keflavik Approach (BIKF_APP) provides approach control service to all aircraft within the Keflavik (KF) sector of the Faxi TMATMA, (asand wellarea ascontrol bandboxingservice to aircraft transiting the KF sector of the TMA. Keflavik APP also bandboxes the RK sector ifof the TMA when Reykjavik ApproachAPP is offline – see Chapter 5.)offline.

Arrivals

Overview of STARs

INITIAL FIX	RUNWAY
	01	10	19	28
DEVUD	4N	4M	2K	1H
NASBU	4N	2M	3K	1H
ASRUN	3N	2M	2K	1H
BASLU	3N	3M	2K	2H
BIRNA	2N	3M	3K	2H
ELDIS	3N	3M	3K	3H
GIRUG	3N	3M	2K	2H
INGAN	5N	3M	2K	2H

Procedure

Reykjavik Control clears aircraft ontofor the STAR & descends them to FL100. If Reykjavik Control is offline, then APP may contact aircraft early (3-5 mins before they reach the first waypoint of the STAR) to issue this STAR clearance and descent.

WhenThe standard approach for all runways is the ILS Z approach. APP shall descend aircraft issuch approachingthat they reach the last waypoint of the STAR,STAR APP should descend them toat 3000ft  (when RWY 10/19 is in use)use, or 3500ft  (when RWY 01/28 is in use)use. andThe clearlast themwaypoint of the STAR will also be an IAF for the ILS Z approach. The ILS Z approach is the standard approach for all runways.

Traffic permitting, it is common practice during low-moderate traffic for APP to cancel the STAR and route aircraft directly to the last waypoint of the STAR, i.e., the ILS Z approach IAFs.

To ensure that no aircraft violates the minimum horizontal separation of 3 NM in the TMA, APP shall aim to establish aircraft onto the ILS with no less than 5 NM separation. During single runway operations, itAPP is recommended toshould aim for at least 7 NM of separation between arrivals, to ensure sufficient gaps/buffer timegaps for departures.

The ILS Z approaches have a published minimum speed of 160kts until 4 NM from the airport. APP may issue a higher/lower speed requirement, or cancel this speed restriction, ifas necessary for trafficseparation separation/and sequencing.

Arrivals on the ILS Z or RNP approaches may be transferred to TWR as soon as they have crossedpassed the IAF. AllFor any other arrivalsapproach, APP should bewait transferreduntil oncethe aircraft is established on the ILS/final approach.approach track/course.

Non-Standard Arrivals and Approaches

If aircraft are unable to accept the ILS Z approach, then alternative approaches should be offered in order of precision.

RNP & LOC Z Approaches

The published RNP & LOC Z approaches largely mirror the ILS Z approaches, and share the same published minimum speed of 160kts until 4 NM from the airport. Handling them is thus similar to an ILS Z approach, simply substituting “RNP” or “LOC Z” for “ILS Z” in the approach clearance.

Vectored ILS Approaches

Aircraft on a vectored ILS approach into BIKF should be established no closer than 10 NM from the airport at no greater than 30° from runway heading.out.

ILS Y / VOR Approaches

The ILS Y and VOR approaches at BIKF are non-RNAV ILS procedures. They are teardrop-shaped procedures commencing from KFV VOR. Aircraft flyingrequesting these approaches mayshould be routedcleared direct to KFV as soon as practical. Upon approachingAfter KFV, Approach should clear the aircraft for the ILS Y approach. The aircraft should then report beacon outbound, and then established on the ILS/final approach course (as appropriate.)

Due to the added difficulty of sequencing aircraft on these procedures while the ILS Z/RNP approaches are also in use, it is preferred to vector aircraft onto the ILS instead of using these procedures.

Since aircraft on the ILS Y and VOR approaches willrequires needthe aircraft to descend below 3000ft (i.e., into the BIKF CTR), as a part of the approach, Keflavik ApproachAPP should coordinate with Keflavik TowerTWR to make them aware of any aircraft on such approaches.

NDB Approach (RWY 10)

The NDB approach for RWY 10 is a racetrack procedure.procedure Thecommencing IAF is thefrom KF (Keflavik)NDB. NDB – aircraftAircraft may be routedcleared direct KF as soon as practical. The aircraft should be asked to report on final approach course, at which point it may be transferred to Tower.TWR.

Like the ILS Y and VOR approaches, sinceSince the NDB approach requires the aircraft to descend below 3000ft (into the BIKF CTR,CTR), Keflavik ApproachAPP should coordinate with Keflavik TowerTWR to notifymake them aware of any aircraft on such approaches.

Departures

Traffic permitting, it is common practice for Approach to issue a direct to the last waypoint of the SID immediately after radar identifying the aircraft, even if said waypoints lie outside the TMA This does not require coordination with Reykjavik Control.

LVP Operations

When BIKF is in LVP, Keflavik Approach and Keflavik Tower should coordinate to revise the runway configuration so that the arrival runway is either RWY 10 or 19, as those are the only two CAT II equipped runways at BIKF. Approach should ensure additional spacing (at least +2 NM on top of usual minima) between aircraft.

Final Approach Position (BIKF_F_APP)

The Final Approach position (BIKF_F_APP) is intended to relieve the workload of the primary Approach position during high traffic. The coordination name of BIKF_F_APP is Keflavik Final, and its radio callsign is “Keflavik Approach.”

Final controls the airspace immediately surrounding the extended centreline of BIKF’s active arrival runway. Final’s airspace ranges from 3000 – 7000ft. For RWY 01, 10, and 19, Final’s airspace is a large box, roughly 40 NM on each side, around the extended centreline. See the images below for reference.

RWY 01	RWY 10
RWY 19	RWY 28

When both Keflavik Approach and Keflavik Final are online, their division of responsibility is as follows:

• Approach establishes the arrival sequence and descends aircraft to 7000ft.
  • Approach will hand the aircraft over to Final when the aircraft reaches 7000ft and enters Final’s lateral boundaries.
  • If holding is necessary, Approach will initiate and manage the holds.
• Final fine-tunes the sequence and directs aircraft onto final approach (the ILS).

Keflavik Final does not control departures, or control BIKF top-down.