Turku Airport

Turku Airport (EFTU) is located in Turku, Finland, north of the city area. Turku is the fourth busiest airport in Finland by the number of passengers. The airport is also operated by cargo carriers, making it the second busiest airport by the amount of cargo. Charts for EFTU can be found here.

ATS Positions

Login Frequency Callsign Area of Responsibility
EFTU_TWR 118.300 Turun Torni
Turku Tower
Taxiway & runway movement, Turku CTR
EFTU_APP 120.475 Turkun Tutka
Turku Radar
Turku TMA & CTA

Turku Airport is usually operated by one controller, Turku Tower, who is also responsible for the TMA and CTA when Turku Radar is offline. Turku Radar is activated when the traffic amount requires.

Runway use

The aerodrome has one runway (12/30). There are no environmental restrictions for the choice of runway in use, however some civil aviation training activities are restricted during night time. Intersection takeoffs can be performed upon the pilot-in-command's request the traffic situation permitting. Note that runway 08 is not equipped with an ILS approach. In low visibility conditions, runway 26 (ILS-Z approach) shall be used the surface wind permitting. Arriving IFR traffic on runway 08 shall primarily be cleared for the RNP approach.

Finnhems medical helicopter

A medical helicopter base is located at the airport, south of runway intersection B. In case of status flight (medical/HOSP) it has a priority to other traffic! The call-sign of the medical helicopter is "Finnhems 20" (ICAO: FIH20). The medical helicopter will perform approach directly to its base. When the mission requires to cross the runway overhead or over the approach path, a runway crossing clearance must be given. The medical helicopter will transport patients to Turun Yliopistollinen keskussairaala (EFTV) helipad.

Finnhems 20 squawk code: 0002.

Finnhems 20, Cleared direct en-route, 5000ft or below, QNH 1013, wind 220 degrees 2 knots, cleared for takeoff. Report airborne. Cleared to cross runway.

Finnhems 20, selvä menetelmän mukaan, QNH 1013. Tuulet 220 astetta 2 solmua, selvä lentoonlähtöön. Ilmoita ilmassa. Selvä ylittää kiitotie.

Finnish Border Guard

A Finnish Border Guard base is also located at the airport on the Frontier Guard Apron south of runway holding point A. There are two FO-228 airplanes and three AS-332 Super Puma sea rescue helicopters based at EFTU.

Low visibility procedures

The airport is approved for low visibility procedures (LVP). Low visibility procedures for takeoffs (LVPTO) are used when the RVR value is 400 M or less. Note: LVPTO are not allowed below RVR 300 M (CAT D aircraft) and below RVR 250 M (CAT C aircraft). LVP for all air traffic will become effective when the RVR value decreases to 550 M. Note: Runway 26 is only approved for CAT1 approaches.

The readiness to take the procedures in use at a certain time will be informed to the pilots by ATIS or ATC:

"Low visibility take off procedures available prior to 5 min notice".

The application of procedures will be informed to the pilots by ATIS or on the frequency by ATC:

"Low visibility take off procedures in operation".

IFR clearance

The IFR clearance is issued by Turku Tower. Traffic shall be instructed to follow a standard departure (SID), or cleared direct to the TMA exit point. Coordination is required with Helsinki Control if a longer direct (DCT) clearance is preferred. The next flight-planned airway or point, initial altitude and the squawk code shall also be included in the IFR clearance. The initial cleared altitude will be the final requested flight level, if not restricted by Helsinki Control (ACC).

Scandinavian 85E, cleared to Arlanda, runway 26, LIVLU2A departure, N85, FL180, squawk 1277.

Ground movements & parking

Departing traffic does not necessarily need push back from stands 4-7. Traffic can be cleared to start up on the stand and taxi out with a right turn.

Wizzair 1338, time 12, startup approved. Information M, 1014.

Wizzair 1338, taxi to holding point A.

The table below can be used as a general guideline for assigning parking positions at the airport.

Stand Usage Example of airlines and types
4-7 Medium jets, turboprop FIN, SAS, WZZ, BTI
9-12 Cargo NPT, TAY
Apron Y General aviation  
Frontier Guard Apron Frontier guard FNG ("Finnguard")

Airspace

Turku Control Zone (CTR) is class D airspace with an upper limit of 1700 ft MSL. Service to traffic in the CTR shall be provided in accordance with the airspace classification. If Turku Radar is online, coordination is required for VFR traffic exiting the CTR for traffic information purposes.

Turku Terminal Area (TMA) is also class D airspace. The TMA extends from 1700 ft up to FL95. Service to traffic in the TMA shall be provided in accordance with the airspace classification. If Tower and Radar is separate units, it is recommended to coordinate inbound VFR traffic direct to the traffic circuit from the TMA. If this is the case, no separate clearance is required to enter the CTR. A radio transfer shall be made before the CTR border.

Inbound IFR traffic will enter the TMA via EXUPA, IPMOT, UVOPA, NIRPU, OTKIL, EMPOM or UPAPU. Traffic will be cleared to FL100 by Helsinki Control, and cleared for RNAV STAR serving the runway in use. Military traffic not able to follow the STAR, will usually be cleared direct RUS VOR and expect vectors or visual/VOR approach serving the runway in use.

Turku Tower, Finnair 29W, ATR72, maintaining FL120, when ready cleared to FL100, information M, 1011. IPMOT 2C arrival.

Finnair 29W, Turku Tower, radar contact. When ready descend to 2200 ft, QNH 1011. Cleared ILS-Z approach runway 26. Number 1 in traffic. Report established on the localizer.

If the inbound aircraft is cleared direct to the "T-bar" by Helsinki Control, it is suggested to state the track miles or minutes to the TMA border. This information can be given with or after the initial descent clearance.

Wizzair 6389, for your information, next 2 minutes below FL95, uncontrolled airspace. No reported traffic.

Departing traffic shall be transferred to Helsinki Control when passing FL95.

 

This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.
I agree