Finnish Airports & Charts
- 🟢 Links & Phraseology Guide
- 🔵 EFHK - Helsinki
- 🔵 EFIV - Ivalo
- 🔵 EFJY - Jyväskylä
- 🔵 EFKT - Kittilä
- 🔵 EFKU - Kuopio
- 🔵 EFOU - Oulu
- 🔵 EFRO - Rovaniemi
- 🔵 EFTP - Tampere-Pirkkala
- 🔵 EFTU - Turku
- 🟠 Aerodromes with AFIS
- 🔴 V-LARA Airspace Reservation
🟢 Links & Phraseology Guide
Useful links, Sceneries and Phraseology Examples for Pilots in Finland
📝 Useful links and notes
Charts
Active maps
- Flyk map (interactive map of Finnish airspace)
- Vatglasses (Vatsim ATC sectors)
Flight planning
Official documents
Notes
IFR flight
Please create a valid route using a flight planner.
As a general rule, traffic inbound or outbound to EFHK shall be planned via airways, otherwise airways are rarely used. Please refer to the AIP ENR 3.3: open link
VFR flight
PDF guide: VFR_Guide_to_Finland.pdf
🗺️ Airport sceneries
EFHK - Helsinki
MSFS
P3D
X-Plane
Other aerodromes
You can find sceneries for Finnish airports from the following websites:
MSFS
- Flightsim.to
- fsaddons.fi
- EFMI,EFVR,EFKA,EFTP,EFSI,EFKS,EFVA
- Flightsim.to - Tatu
- Flightsim.to - EFKT
- Flightsim.to - EFJY (NEW)
- fsaddons.fi - Medical helipads
P3D
- Some sceneries for P3D are listed here: freewarescenery.com
- EFRO - MK Studios
- fsnordic.net
X-Plane
- Fly X - EFRO
- PH20 - EFOU
- Other sceneries can be found from forums.x-plane.org
🎧 IFR flight from A to B
English is the only allowed language to be used for ATC clearances and instructions at Helsinki airport and above FL 95 when in contact with Area Control. Regardless of this rule, the Finnish version of phraseology is displayed below.
EFHK - EFOU
1. Initial contact with ground, en-route clearance
| 👨✈️ | Helsinki ground, Finnair 4MW, Airbus 320, stand 22, information H, QNH 1011, request clearance to Oulu. Helsingin rullaus, Finnair 4MW, Airbus 320, paikka 22, tiedotus H, QNH 1011, pyydän selvitystä Ouluun. |
| 🎧 | Finnair 4MW, cleared to Oulu, runway 22 right, Tevru 3N departure, climb to 4000 feet, squawk 2520, target start-up time 41. Finnair 4MW, selvä Ouluun, kiitotie 22 oikea, Tevru 3N lähtöreitti, nouse 4000 jalkaan, koodaa 2520, TSAT 41. |
| 👨✈️ | Cleared to Oulu, runway 22 right, Tevru 3N departure, climb to 4000 feet, squawk 2520, TSAT 41, Finnair 4MW. Selvä Ouluun, kiitotie 22 oikea, Tevru 3N lähtöreitti, 4000 jalkaa, koodaa 2520, TSAT 41, Finnair 4MW. |
| 🎧 | Finnair 4MW, clearance correct, for pushback and start-up contact ground 121.8. Finnair 4MW, selvitys oikein, työntöä ja käynnistystä varten, ota yhteys rullaukseen 121.8. |
| 👨✈️ | 121.8, Finnair 4MW. 121.8, Finnair 4MW. |
2. Start-up and push back instructions
| 👨✈️ | Helsinki ground, Finnair 4MW, stand 22, request push back and start-up. Helsingin rullaus, Finnair 4MW, paikka 22, pyydän käynnistää ja työntää. |
| 🎧 | Finnair 4MW, behind company ATR from left to right, start-up and push back approved, facing northwest. Finnair 4MW, vasemmalta rullaavan ATR:n jälkeen saat käynnistää ja työntää, nokka kohti luodetta. |
| 👨✈️ | Behind company ATR, push back and start-up approved, facing northwest, Finnair 4MW. ATR:n jälkeen käynnistän ja työnnän, nokka luoteeseen, Finnair 4MW. |
3. Taxi
| 👨✈️ | Finnair 4MW, request taxi. Finnair 4MW, pyydän rullata. |
| 🎧 | Finnair 4MW, taxi via AD to ZD, hold short of runway 22 left. Finnair 4MW, rullaa AD pitkin ZD:lle, pysy selvästi erossa kiitotiestä 22 vasen. |
| 👨✈️ | Taxi via AD to ZD, hold short of runway 22 left, Finnair 4MW. Rullaan AD pitkin ZD:lle, pysyn selvästi erossa kiitotiestä 22 vasen, Finnair 4MW. |
4. Transfer to tower
| 🎧 | Finnair 4MW, contact tower, 118.6. Finnair 4MW, ota yhteys torniin, 118.6. |
| 👨✈️ | 118.6, Finnair 4MW. 118.6, Finnair 4MW. |
5. Initial contact with tower, runway crossing and taxi
| 👨✈️ | Helsinki tower, Finnair 4MW, approaching ZD. Helsingin torni, Finnair 4MW, lähestyn ZD:aa. |
| 🎧 | Finnair 4MW, behind landing Boeing 737, cross runway 22 left via ZD and taxi to holding point WD, behind. Finnair 4MW, saapuvan Boeing 737 jälkeen, ylitä kiitotie 22 vasen ZD:n kautta ja rullaa odotuspaikalle WD, jälkeen. |
| 👨✈️ | Behind landing Boeing 737, cross runway 22 left via ZD and taxi to holding point WD, behind, Finnair 4MW. Saapuvan Boeing 737 jälkeen, ylitä kiitotie 22 vasen ZD:n kautta ja rullaa odotuspaikalle WD, jälkeen, Finnair 4MW. |
6. Transfer to tower west
| 🎧 | Finnair 4MW, contact tower 118.850. Finnair 4MW, ota yhteys torniin 118.850. |
| 👨✈️ | 118.850, Finnair 4MW |
7. Initial contact with tower west and take-off
| 👨✈️ | Helsinki tower, Finnair 4MW, taxiway D Helsingin torni, Finnair 4MW, rullaustiellä D |
| 🎧 | Finnair 4MW |
| 🎧 | Finnair 4MW, via WD lineup runway 22 right Finnair 4MW, WD kautta siirry kiitotielle 22 oikea |
| 👨✈️ | Via WD, lineup runway 22 right, Finnair 4MW WD kautta siirryn kiitotielle 22 oikea, Finnair 4MW |
| 🎧 | Finnair 4MW, wind variable 2 knots, runway 22 right, cleared for take-off Finnair 4MW, tuuli vaihtelevaa 2 solmua, kiitotie 22 oikea, selvä lentoonlähtöön |
| 👨✈️ | Cleared for take-off, runway 22 right, Finnair 4MW Selvä lentoonlähtöön, kiitotie 22 oikea, Finnair 4MW |
8. Initial contact with Approach Control
| 👨✈️ | Helsinki radar, Finnair 4MW, passing 1700 feet, Tevru 3N Helsingin tutka, Finnair 4MW, läpäi 1700 jalkaa, Tevru 3N |
| 🎧 | Finnair 4MW, Helsinki radar, radar contact, climb to flight level 280 Finnair 4MW, Helsingin tutka, tutkayhteys, nouse lentopinnalle 280 |
| 👨✈️ | Climb to flight level 280, Finnair 4MW Nousen lentopinnalle 280, Finnair 4MW |
| 🎧 | Finnair 4MW, proceed direct Tevru Finnair 4MW, hakeudu suoraan Tevru |
| 👨✈️ | Direct Tevru, Finnair 4MW Suoraan Tevru, Finnair 4MW |
9. Transfer to Area Control
| 🎧 | Finnair 4MW, contact Helsinki control, 132.325 Finnair 4MW, ota yhteys Helsingin alueeseen, 132.325 |
| 👨✈️ | 132.325, Finnair 4MW |
10. Initial contact with Area Control, assignment of arrival runway
| 👨✈️ | Helsinki Control, Finnair 4MW, passing flight level 198 for flight level 280, inbound Tevru Helsinki Control, Finnair 4MW, läpäisen lentopinnan 198 lentopinnalle 280, suuntaan Tevru |
| 🎧 | Finnair 4MW, Helsinki Control, radar contact, proceed direct Suvib, climb to flight level 360, expect runway 12 Finnair 4MW, Helsinki Control, tutka yhteys, hakeudu suoraan Suvib, nouse lentopinnalle 360, odota kiitotietä 12 |
| 👨✈️ | Direct Suvib, climb to flight level 360, runway 12, Finnair 4MW Suoraan Suvib, nousen lentopinnalle 360, kiitotie 12, Finnair 4MW |
11. Arrival clearance and top-of-descent
| 🎧 | Finnair 4MW, when ready descend to flight level 100, cleared Suvib 4C arrival, proceed direct Tegbo Finnair 4MW, kun valmis laskeudu lentopinnalle 100, selvä Suvib 4C tuloreitti, hakeudu suoraan Tegbo |
| 👨✈️ | When ready descend to flight level 100, Suvib 4C, direct Tegbo, Finnair 4MW Kun valmis laskeudun lentopinnalle 100, Suvib 4C, suoraan Tegbo, Finnair 4MW |
12. Transfer to combined Aerodrome- and Approach Control
| 🎧 | Finnair 4MW, contact Oulu tower, 124.4 Finnair 4MW, ota yhteys Oulun torniin, 124.4 |
| 👨✈️ | 124.4, Finnair 4MW |
13. Initial contact and approach clearance
| 👨✈️ | Oulu tower, Finnair 4MW, passing flight level 202 for flight level 100, Airbus 320, information Q Oulun torni, Finnair 4MW, läpäisen lentopinnan 202 lentopinnalle 100, Airbus 320, tiedotus Q |
| 🎧 | Finnair 4MW, Oulu tower, radar contact, continue descent to 2300 feet, QNH 1032, cleared ILS Z approach runway 12, right circuit, report established on localizer, for information next 20 miles below flight level 95 uncontrolled airspace Finnair 4MW, Oulun torni, tutkayhteys, jatka laskeutumista 2300 jalkaan, QNH 1032, selvä ILS Z lähestymiseen kiitotie 12, oikea kierros, ilmoita suuntasäteessä, tiedoksi seuraavat 20 mailia alle lentopinnan 95 valvomatonta ilmatilaa |
| 👨✈️ | Continue descent to 2300 feet, QNH 1032, cleared ILS Z approach runway 12, right circuit, wilco, Finnair 4MW Jatkan laskeutumista 2300 jalkaan, QNH 1032, selvä ILS Z lähestymiseen kiitotie 12, oikea kierros, ilmoitan, Finnair 4MW |
14. Reporting on approach and landing
| 👨✈️ | Finnair 4MW, localizer established Finnair 4MW, suuntasäteessä |
| 🎧 | Finnair 4MW, wind 210 degrees 5 knots, runway 12, cleared to land Finnair 4MW, tuuli 210 astetta 5 solmua, kiitotie 12, selvä laskuun |
| 👨✈️ | Cleared to land, runway 12, Finnair 4MW Selvä laskuun, kiitotie 12, Finnair 4MW |
15. Taxi (no picture)
| 🎧 | Finnair 4MW, taxi to apron, stand 14 Finnair 4MW, rullaa asematasolle, paikka 14 |
| 👨✈️ | Taxi to apron, stand 14, Finnair 4MW Rullaan asematasolle, paikka 14, Finnair 4MW |
EFOU - EFHK
1. Initial contact, en-route clearance, start-up and push back
| 👨✈️ | Oulu tower, Finnair 2PD, Airbus 320, stand 14, information P, request clearance to Helsinki Oulun torni, Finnair 2PD, Airbus 320, paikka 14, tiedotus P, pyydän selvitystä Helsinkiin |
| 🎧 | Finnair 2PD, Oulu tower, cleared to Helsinki, runway 12, Miknu 4A departure, Y86, flight level 330, squawk 0224 Finnair 2PD, Oulun torni, selvä Helsinkiin, kiitotie 12, Miknu 4A lähtöreitti, Y86, lentopinta 330, koodaa 0224 |
| 👨✈️ | Cleared to Helsinki, runway 12, Miknu 4A departure, Y86, flight level 330, squawk 0224, Finnair 2PD Selvä Helsinkiin, kiitotie 12, Miknu 4A lähtöreitti, Y86, lentopinta 330, koodaa 0224, Finnair 2PD |
| 👨✈️ | Finnair 2PD, stand 14, request startup and pushback Finnair 2PD, paikka 14, pyydän käynnistää ja työntää |
| 🎧 | Finnair 2PD, startup and pushback approved, QNH 1032, runway 12 for departure Finnair 2PD, saat käynnistää ja työntää, QNH 1032, kiitotie 12 lähtöön |
| 👨✈️ | Startup and pushback approved, QNH 1032, runway 12, Finnair 2PD Saan käynnistää ja työntää, QNH 1032, kiitotie 12, Finnair 2PD |
| 🎧 | Oulu |
2. Taxi
| 👨✈️ | Finnair 2PD, request taxi Finnair 2PD, pyydän rullata |
| 🎧 | Finnair 2PD, taxi to holding point A, runway 12 Finnair 2PD, rullaa odotuspaikalle A, kiitotie 12 |
| 👨✈️ | Taxi to holding point A, runway 12, Finnair 2PD Rullaan odotuspaikalle A, kiitotie 12, Finnair 2PD |
3. Take-off
| 👨✈️ | Finnair 2PD, ready Finnair 2PD, valmis |
| 🎧 | Finnair 2PD, lineup runway 12 Finnair 2PD, siirry kiitotielle 12 |
| 👨✈️ | Lineup runway 12, Finnair 2PD Siirryn kiitotielle 12, Finnair 2PD |
| 🎧 | Finnair 2PD, wind 120 degrees, 5 knots, runway 12, cleared for takeoff Finnair 2PD, tuuli 120 astetta, 5 solmua, kiitotie 12, selvä lentoonlähtöön |
| 👨✈️ | Cleared for takeoff, runway 12, Finnair 2PD Selvä lentoonlähtöön, kiitotie 12, Finnair 2PD |
4. Altitude verification
| 🎧 | Finnair 2PD, radar contact, report altitude passing Finnair 2PD, tutkayhteys, ilmoita korkeus läpi |
| 👨✈️ | Passing 2100 feet, Finnair 2PD Läpäisen 2100 jalkaa, Finnair 2PD |
| 🎧 | Finnair 2PD |
5. Transfer to Area Control
| 🎧 | Finnair 2PD, contact Helsinki control, 132.325 Finnair 2PD, ota yhteys Helsingin alueeseen 132.325 |
| 👨✈️ | 132.325, Finnair 2PD |
7. Initial contact with Area Control
| 👨✈️ | Helsinki Control, Finnair 2PD, passing flight level 102 for flight level 330 Helsinki Control, Finnair 2PD, läpäisen lentopinnan 102 lentopinnalle 330 |
| 🎧 | Finnair 2PD, Helsinki control, radar contact, runway 22 left Finnair 2PD, Helsinki control, tutkayhteys, kiitotie 22 vasen |
| 👨✈️ | 22 left, Finnair 2PD 22 vasen, Finnair 2PD |
8. Arrival clearance and top of descent
| 🎧 | Finnair 2PD, when ready descend to flight level 100, cleared Lusep 4A arrival, proceed direct Kukka Finnair 2PD, kun valmis laskeudu lentopinnalle 100, selvä Lusep 4A tuloreitti, hakeudu suoraan Kukka |
| 👨✈️ | When ready descend to flight level 100, Lusep 4A arrival, direct Kukka, Finnair 2PD Kun valmis laskeudun lentopinnalle 100, Lusep 4A tuloreitti, suoraan Kukka, Finnair 2PD |
9. Trasnfer to Helsinki Approach Control
| 🎧 | Finnair 2PD, contact Helsinki radar, 119.1 Finnair 2PD, ota yhteys Helsingin tutkaan, 119.1 |
| 👨✈️ | 119.1, Finnair 2PD |
10. Initial contact with Approach Control
| 👨✈️ | Helsinki radar, Finnair 2PD, Airbus 320, passing flight level 155 for flight level 100, information M Helsingin tutka, Finnair 2PD, Airbus 320, läpäisen lentopinnan 155 lentopinnalle 100, tiedotus M |
| 🎧 | Finnair 2PD, Helsinki radar, radar contact, descend to 5000 feet, QNH 1025, runway 22 left Finnair 2PD, Helsingin tutka, tutkayhteys, laskeudu 5000 jalkaan, QNH 1025, kiitotie 22 vasen |
| 👨✈️ | Descend to 5000 feet, QNH 1025, runway 22 left, Finnair 2PD Laskeudun 5000 jalkaan, QNH 1025, kiitotie 22 vasen, Finnair 2PD |
11. Transfer of control and initial contact with Arrival
| 🎧 | Finnair 2PD, contact arrival 119.9 Finnair 2PD, ota yhteys tuloon 119.9 |
| 👨✈️ | 119.9, Finnair 2PD |
| 👨✈️ | Arrival, Finnair 2PD Tulo, Finnair 2PD |
| 🎧 | Finnair 2PD, via Kukka, Bifix cleared ILS approach, runway 22 left, report established on localizer Finnair 2PD, Kukan ja Bifix:in kautta selvä ILS lähestymiseen kiitotie 22 vasen, ilmoita suuntasäteessä |
| 👨✈️ | Via Kukka, Bifix cleared ILS approach, runway 22 left, wilco, Finnair 2PD Kukan ja Bifix:in kautta selvä ILS lähestymiseen, kiitotie 22 vasen, ilmoitan, Finnair 2PD |
12. Reporting on approach and transfer to Aerodrome Control
| 👨✈️ | Finnair 2PD, localizer established Finnair 2PD, suuntasäteessä |
| 🎧 | Finnair 2PD, contact tower 118.6 Finnair 2PD, ota yhteys torniin 118.6 |
| 👨✈️ | 118.6, Finnair 2PD |
14. Initial Contact with Aerodrome Control and landing
| 👨✈️ | Helsinki tower, Finnair 2PD, ILS runway 22 left Helsingin torni, Finnair 2PD, ILS kiitotie 22 vasen |
| 🎧 | Finnair 2PD, Helsinki tower, continue approach, wind calm Finnair 2PD, Helsingin torni, jatka lähestymistä, tuuli tyyntä |
| 👨✈️ | Continue approach, Finnair 2PD Jatkan lähestymistä, Finnair 2PD |
| 🎧 | Finnair 2PD, wind variable 1 knot, runway 22 left cleared to land, ZG available Finnair 2PD, tuuli vaihtelevaa 1 solmu, kiitotie 22 vasen, selvä laskuun, ZG vapaa |
| 👨✈️ | Cleared to land, runway 22 left, Finnair 2PD Selvä laskuun, kiitotie 22 vasen, Finnair 2PD |
15. Initial contact with Ground and taxi instructions
Pilot should contact ground without ATC initiated transfer according to EFHK AIP.
| 👨✈️ | Helsinki ground, Finnair 2PD, ZG Helsingin rullaus, Finnair 2PD, ZG |
| 🎧 | Finnair 2PD, taxi via VG and AC, stand 26 Finnair 2PD, rullaa VG ja AC kautta, paikka 26 |
| 👨✈️ | via VG and AC, stand 26, Finnair 2PD, Finnair 2PD VG ja AC kautta, paikka 26, Finnair 2PD, Finnair 2PD |
🎧 VFR flight from A to B
More specific phraseologies for VFR flights can be found in Standard Operating Procedures.
EFKS - EFOU - EFAH
Flight plan
(FPL-OHCME-VM
-C172/L-FOV/C
-EFKS0800
-N0100VFR RAITO TASKI EFOU UNILO
-EFAH0125
-DOF/210511 RMK/TGL EFOU0010 PIC TEL 010 123 156 EFOU)
A flight according to the flight plan with a C172 aircraft from Kuusamo via Oulu to Ahmosuo. According to the RMK field, the intention of the flight is touch-and-go landings in Oulu for approximately 10 minutes. Ahmosuo is an uncontrolled airfield located below the Oulu approach control area. Kuusamo and Oulu are served by local air traffic control (TWR).
Phraseology
1. Initial contact, taxi and clearance to leave Control Zone
| 👨✈️ | OH-CME, at apron, information November, request taxi OH-CME, asematasolla, tiedotus India, pyydän rullata |
| 🎧 | O-ME, taxi to holding point Alfa, leave control zone via Raito, 2000 feet or below, QNH 1014, squawk 3676 O-ME, rullaa odotuspaikalle Alfa, jätä lähialue Raidon kautta, 2000 jalkaa tai alapuolella, QNH 1014, koodaa 3676 |
| 👨✈️ | Taxi to holding point Alfa, leave control zone via Raito, 2000 feet or below, QNH 1014, squawk 3676, O-ME Rullaan odotuspaikalle Alfa, jätän lähialueen Raidon kautta, 2000 jalkaa tai alapuolella, QNH 1014, koodaan 3676, O-ME |
2. Take-off
| 🎧 | O-ME, via Alfa backtrack and lineup runway 30 O-ME, Alfan kautta rullaa takaisinpäin kiitotietä 30 |
| 👨✈️ | Via Alfa backtrack and lineup runway 30, O-ME Alfan kautta rullaan takaisinpäin kiitotietä 30, O-ME |
| 🎧 | O-ME, wind 290 degrees 10 knots, runway 30, cleared for take-off, (left turn) O-ME, tuuli 290 astetta 10 solmua, kiitotie 30, selvä lentoonlähtöön (vasen kaarto) |
| 👨✈️ | Cleared for take-off runway 30, (left turn), O-ME Selvä lentoonlähtöön kiitotie 30, (vasen kaarto), O-ME |
3. Crossing VRP and leaving the Control Zone
| 👨✈️ | O-ME, Raito outbound, 1900 feet O-ME, Raito ulos, 1900 jalkaa |
| 🎧 | O-ME O-ME |
Aircraft will continue flight in uncontrolled airspace and may contact Area Control for flight information services (FIS). Next radio contact is made with Oulu Radar.
4. Initial contact to Approach Control, clearance to Terminal Area
| 👨✈️ | Oulu radar, OH-CME Oulun tutka, OH-CME |
| 🎧 | O-ME, Oulu radar O-ME, Oulun tutka |
| 👨✈️ | O-ME, Cessna 172, OUK radial 045, 28 miles, at 4000 feet, QNH 997, information Quebec, request clearance to terminal area O-ME, Cessna 172, OUK radiaali 045 astetta, 28 mailia, 4000 jalkaa, QNH 997, tiedotus Quebec, pyydän selvitystä lähestymisalueelle |
| 🎧 | O-ME, cleared to Oulu terminal area, 4000 feet or below, QNH 997 O-ME, selvä Oulun lähestymisalueelle, 4000 jalkaa tai alapuolella, QNH 997 |
| 👨✈️ | Cleared to terminal area, 4000 feet or below, QNH 997, O-ME Selvä Oulun lähestymisalueelle, 4000 jalkaa tai alapuolella, QNH 997, O-ME |
5. Clearance to Control Zone and transfer to Tower
Oulu Radar and Oulu Tower will coordinate a suitable clearance to Control Zone which will be given to the aircraft before transfer to Tower.
| 🎧 | O-ME, join downwind runway 12, direct, 4000 feet or below O-ME, liity myötätuuleen kiitotie 12, suoraan, 4000 jalkaa tai alapuolella |
| 👨✈️ | Join downwind runway 12, direct, 4000 feet or below, O-ME Liityn myötätuuleen kiitotie 12, suoraan, 4000 jalkaa tai alapuolella, O-ME |
Aircraft is now cleared direct towards the downwind leg.
| 🎧 | O-ME, contact Oulu tower, 124.4 O-ME, ota yhteyttä Oulun torniin, 124.4 |
| 👨✈️ | Contact Oulu tower, 124.4, O-ME Otan yhteyttä Oulun torniin 124.4, O-ME |
6. Initial contact to Tower, clearance for touch-and-go and leaving Control Zone
| 👨✈️ | Oulu tower, OH-CME, 10 miles north east of airfield, 2100 feet Oulun torni, OH-CME, 10 mailia koiliseen kentästä, 2100 jalkaa |
| 🎧 | O-ME, Oulu tower, descend to 1300 feet or below, (report downwind) O-ME, Oulun torni, laskeudu 1300 jalkaan tai alapuolella, (ilmoita myötätuuli) |
| 👨✈️ | O-ME, downwind runway 12, touch and go O-ME, myötätuuli kiitotie 12, läpilasku |
| 🎧 | O-ME, number 2, follow Diamond 42 on base leg runway 12 O-ME, vuoro 2, seuraa Diamond 42 perusosalla kiitotie 12 |
| 👨✈️ | Number 2, following Diamond 42 on base leg runway 12, O-ME Vuoro 2, seuraan Diamond 42 perusosalla kiitotie 12, O-ME |
| 🎧 | O-ME, wind 120 degrees, 4 knots, runway 12, cleared for touch and go, which after leave control zone via Unilo, 1300 feet or below, (left turn) O-ME, tuuli 120 astetta, 4 solmua, kiitotie 12, selvä läpilaskuun, jonka jälkeen jätä lähialue Unilon kautta, 1300 jalkaa tai alapuolella, (vasen kaarto) |
| 👨✈️ | Cleared for touch and go, runway 12, which after leave control zone via Unilo, 1300 feet or below, (left turn), O-ME Selvä läpilaskuun, kiitotie 12, jonka jälkeen jätän lähialueen Unilon kautta, 1300 jalkaa tai alapuolella, (vasen kaarto), O-ME |
| 👨✈️ | O-ME, Unilo outbound, 1200 feet O-ME, Unilo ulos, 1200 jalkaa |
| 🎧 | O-ME O-ME |
After this the aircraft will continue in uncontrolled airspace and land at Ahmosuo airfield.
🔵 EFHK - Helsinki
EFHK pilot briefing
Helsinki Airport is the main international airport of the city of Helsinki, and the entire country. The airport is located north of Helsinki in the neighboring city of Vantaa. The airport is operated by state-owned Finavia.
The airport is by far the busiest in Finland and the fourth busiest in the Nordic countries in terms of passenger numbers. About 90% of Finland's international air traffic passes through Helsinki Airport. On average, the airport handles around 350 departures a day.
The airport is the main hub for Finnair, the flag carrier of Finland, and its subsidiary Nordic Regional Airlines.
| IATA | ICAO | Charts | NOTAMs |
|---|---|---|---|
| HEL | EFHK | Finland AIP - EFHK | Bulletins: EFHK |
Air Traffic Control positions
Due to the size of Helsinki airport and the increased amount of operations, there is a possibility to provide service from two tower positions, two radar positions and two arrival positions:
| Login code | Call sign | Frequency | Responsibility |
|---|---|---|---|
| EFHK_DEL | HELSINKI GROUND | 118.125 | - All en-route clearances (DCL/PDC: EFHK) - Ground movement on aprons 1S and 9 |
| EFHK_GND | HELSINKI GROUND | 121.800 | - Ground movement |
| EFHK_E_TWR | HELSINKI TOWER | 118.600 | - Primary Tower position - Runways 04R/22L and 15/33 - FATO H16/H34 |
| EFHK_W_TWR | HELSINKI TOWER | 118.850 | - Opened according to traffic demand - Runways 04L/22R |
| EFHK_E_APP | HELSINKI RADAR | 119.100 | - Primary Radar position - East sector |
| EFHK_E_APP | HELSINKI RADAR | 129.850 | - Opened according to traffic demand - West sector |
| EFHK_R_APP | HELSINKI ARRIVAL | 119.900 | - Primary arrival position - Sequencing arriving traffic below 5000 FT |
| EFHK_A_APP | HELSINKI ARRIVAL | 124.325 | - Opened only during parallel IFR approaches - Sequencing arriving traffic below 5000 FT |
Listen carefully to the frequency given when being transferred to another controller. Do not try and guess the next frequency, as TWR and APP units may be divided to smaller sectors with similar frequencies.
Ground movement responsibilities:
| EFHK_DEL 118.125 |
EFHK_GND 121.800 |
EFHK_E_TWR 118.600 |
EFHK_W_TWR 118.850 |
DE-ICING |
Currently available stands
Stand allocation
Fun fact! Most of the stand numbers starts with the apron number.
| Type | Stand location |
|---|---|
| Schengen | stands 12-32 and remote stands |
| Non-Schengen | stands W34-W48, S49-S55 and remote stands |
| Cargo | aprons 2, 4 and 9 |
| General Aviation / VIP | apron 3 |
| Stands reserved for de-icing during winter season | aprons 6 and 8 |
Taxi procedures
Taxiing on the apron is always subject to instructions. If you are unsure where to go, please ask for detailed taxi instructions.
Note that the main taxiways have only one letter, e.g. "Y" or "Z", but most taxiways are named with two letters, e.g. "AD" or "AC". Listen carefully to the taxi instructions given by ATC.
Do not cross a runway without a specific clearance from ATC.
Keep the transponder active (squawk mode C) at all times when moving on the runways, taxiways and aprons.
Taxi procedures for departing aircraft
When runway 22R is in use for departure, expect to hold short of runway 22L before you are given clearance to taxi to holding point runway 22R.
By default, ATC will use these holding points:
| Runway | Holding point | Remarks |
|---|---|---|
| 04L | WZ | ... |
| 04R | ZR, (ZS, ZT) | Aircraft from Apron 8: ZS, ZT |
| 15 | Z, YA | Turboprop aircraft DEP from Z |
| 33 | CN, YN | Aircraft from Apron 4: CN |
| 22L | Y, ZD, ZB | Turboprop/QJet aircraft DEP from Y/ZD |
| 22R | WG, WD | WL may be used for traffic from taxiway S |
Taxi procedures for arriving aircraft
ATC will often use minimum spacing on final approach. It is important to vacate the runway quickly in order to achieve maximum runway capacity and minimize the occurance of go-arounds.
When landing on runway 22L, vacate via ZH or later. Do not vacate via Y, ZD or ZG without prior approval from Helsinki Tower.
When landing on runway 04R/22L or 15/33, contact Helsinki Ground 121.8 after vacating the runway. No handoff will be given.
Preferential runway system
When ATC is online, the runway is selected according to the following wind limits when possible. Note that runways may differ from real life due different traffic amount and type. Controllers on VATSIM will select the most suitable runway according to the traffic needs on VATSIM.
| Preference order: | 1 | 2 | 3 | 4 | 5 | 6 |
|---|---|---|---|---|---|---|
| Arrival runway: | 15 | 22L | 04L | 04R | 22R | 33 |
| Departure runway: | 22R | 22L | 04R | 33 | 04L | 15 |
As a general rule, the first available preferential runway will be used until the crosswind component on a dry runway exceeds 20 KT and/or the tailwind component exceeds 5 KT. If the runway is contaminated, the respective restrictions are 15 KT and 5 KT.
Mandatory departure routes
Pilots are requested NOT to include SID in their flight plan as this will be assigned by ATC.
IFR-flights departing from Helsinki above FL 95 shall use these mandatory routes after the SID:
| EFHK TMA Boundary Point | EFHK Departure Connecting Point | Flight Plan |
|---|---|---|
| NUNTO | REKDO | NUNTO-Y369-REKDO-DCT |
| NUNTO | OLPED | NUNTO-Y367-OLPED-DCT |
| KUVEM | USITU | KUVEM-Y366-USITU-DCT |
| ADIVO | POGOK | ADIVO-Y365-POGOK-DCT |
| NEPEK | NISVI | NEPEK-Y361-NISVI-DCT |
| TEVRU | USUPO | TEVRU-Y75-USUPO-DCT |
| IDEPI | ADOPO | IDEPI-Y232-ADOPO-DCT |
| IDEPI | ROKVI | IDEPI DCT ROKVI DCT |
| ARVEP | RATMU | ARVEP-T82-RATMU-DCT |
| NEPEK | EVLIT | NEPEK-Y357-EVLIT-DCT |
| NEPEK | UXADA | NEPEK-Y375-UXADA-DCT |
After the last point of the mandatory departure route, pilots have mostly free hands to plan their flights with DCT routes.
RENKU is only available and mandatory for departures to EETN or EEEI. Maximum cruise level is FL 100.
En-route clearance
En-route clearance can be requested with DCL (datalink) or with VOICE over the ground or tower frequency depending on which ATC position is online.
If using DCL, pilots shall send the pre-dep request to identifier EFHK or EFIN, depending on which station is online. Frequency 118.125 shall be monitored when requesting clearance via DCL.
On initial contact, state aircraft type, received ATIS and QNH.
| 👨✈️ | FASTAIR 312, AIRBUS 320, INFORMATION M, QNH 1011, REQUEST CLEARANCE TO OULU |
Departure with SID:
| 🎧 | FASTAIR 312, CLEARED TO OULU, RUNWAY 22R, TEVRU 3N DEPARTURE, CLIMB TO 4000 FEET, SQUAWK 5542 |
Departure with heading:
| 🎧 | FASTAIR 312, CLEARED TO OULU, RUNWAY 22R, AFTER DEPARTURE FLY HEADING 270, CLIMB TO 4000 FEET, EXPECT RADAR VECTORS TO TEVRU, SQUAWK 5542. |
If you prefer to use a different runway due performance, you may ask it prior to receiving the en-route clearance. Runways 22L and 15 are often approved for turboprop or quiet aircraft.
If unable to follow RNAV SID, inform ATC when requesting clearance.
| 👨✈️ | FASTAIR 312, AIRBUS 320, INFORMATION M, QNH 1011, REQUEST CLEARANCE TO OULU, NEGATIVE RNAV |
Your en-route clearance will include the destination, departure runway, SID or heading and the initial climb which is usually 4000 feet. You will also receive an SSR-code which shall be selected and activated prior to taxi.
Take-off and climb
When cleared for take-off, pilots are expected to start rolling within 10 seconds of take-off clearance. Pilots unable to comply with this requirement shall notify ATC before entering the runway.
Radio transfer procedures
After take-off aircraft shall remain on tower frequency until passing 1500 FT, then contact Helsinki Radar 119.100 or 129.850, depending on your SID route.
You will find the correct radar frequency on your SID-chart. If the primary frequency is not online, contact Radar on the other frequency or Helsinki Control on 121.300.
Pilots shall automatically change to radar frequency after departure!
Initial contact with Radar after departure
When contacting Helsinki Radar, state your altitude and assigned SID. If you are assigned a heading, report the heading to Radar on initial contact.
| 👨✈️ | HELSINKI RADAR, FASTAIR 312, PASSING 1900 FEET, TEVRU 3N |
If no further climb is given, pilot shall maintain 4000 FT.
Mandatory arrival routes
Pilots are requested to not include STAR in their flight plan route.
Arriving IFR flights with cruising level above FL 95 shall use the following routes:
| EFHK Arrival Connecting Point | EFHK STAR Initial Waypoint | Flight Plan |
|---|---|---|
| EVADI | DIVAM | DCT to EVADI-Y370-DIVAM |
| RIRIP | LAKUT | DCT to RIRIP-Y364-LAKUT |
| IBVUT | LAKUT | DCT to IBVUT-Y363-LAKUT |
| OTKIL | LAKUT | DCT to OTKIL-Y368-LAKUT |
| UXADA | AMROT | DCT to UXADA-Y349-AMROT-Y362-LAKUT |
| ENETI | LAKUT | DCT to ENETI-Y362-LAKUT |
| IBOSU | LUSEP | DCT to IBOSU-Y86-LUSEP |
| NAPRU | LUSEP | DCT to NAPRU-T83-LUSEP |
| ROKVI | VEPIN | DCT to ROKVI-Y358-VEPIN |
| ARLOM | VEPIN | DCT to ARLOM-Y359-VEPIN |
Radio procedures for arrivals
Arriving traffic is informed of the runway in use and cleared for the appropriate STAR serving the arrival runway. This information is given by Area Control (EFIN/EETT) when online.
Initial contact with Helsinki Radar
| Call sign | HELSINKI RADAR, FINNAIR 6 |
|---|---|
| Aircraft type | AIRBUS 330 |
| “HEAVY” or “SUPER” if necessary | HEAVY |
| Current flight level | FLIGHT LEVEL 154 |
| Speed (only if assigned by ATC) | SPEED 240 KNOTS |
| Last received ATIS broadcast | INFORMATION SIERRA |
Initial contact with Helsinki Arrival
Say your Call sign only on initial contact with Helsinki Arrival
| Call sign | HELSINKI ARRIVAL, FINNAIR 6 |
|---|
Initial contact with Helsinki Tower
| Call sign | HELSINKI TOWER, FINNAIR 6 |
|---|---|
| Runway | RUNWAY 22 LEFT |
Clearance for Approach
There are 2 ways to be cleared for the approach:
All STARs at Helsinki are so-called Open STARs. If ATC has not given approach clearance, the pilot shall continue present heading after the last waypoint on the STAR:
When aircraft is cleared for approach via own navigation, pilot shall plan a direct (DCT) instead of a vector after the last waypoint on the STAR.
| 🎧 | SPEEDBIRD 794H, VIA KENON BIFIX CLEARED ILS APPROACH RUNWAY 22 LEFT |
Visual approach
ILS is the primary approach type. Upon pilot request, ATC may give clearance for a visual approach.
ATC may advise to “maintain own separation from preceding”, if there are other aircraft approaching the airport. In that case, the separation responsibility will transfer from ATC to the pilot performing the visual approach.
| 🎧 | SPEEDBIRD 794H, DESCEND 2000 FEET, CLEARED VISUAL APPROACH RUNWAY 15, RIGHT CIRCUIT, QNH 1011, MAINTAIN OWN SEPARATION WITH PRECEDING AIRBUS 330 HEAVY, CAUTION WAKE TURBULENCE |
Aircraft on visual approach shall maintain at least 2000 FT until established on final approach course. ATC may give permission “you may leave 2000 feet before final”.
Simultaneous IFR approaches
During periods of heavy inbound traffic, dependent or independent simultaneous approaches may be used on runways 04L/R or 22L/R.
- Pilots are informed when parallel approaches are in force via ATIS:
- "SIMULTANEOUS DEPENDENT/INDEPENDENT IFR APPROACHES IN PROGRESS"
Area control will inform the landing runway as early as possible; however, pilots should plan on landing on either runway when parallel approaches are in progress.
Ground Movement & A380
Taxiway and Stand Limitations
APDC limitations_08_AUG_2024.pdf
WEF 08 AUG 2024: Introduction of stand 404B and stand 407B on Apron 4
Code F Operations (A380)
Parking
- Parking will happen primarily on stands W48 and 905A.
- When Remote 8 is not in use for de-icing, Code-F aircraft may also be parked on stand 815 or on intermediate holding point VS1.
- When runway 15/33 is not in use, Code-F aircraft may also be parked on:
- Intermediate holding point Y7 facing nort-west. Taxi in via Runway 15 and YL.
- Intermediate holding point Y8 facing south-east. Taxi out via YL and Runway 33. Runway 22L shall be closed until Code-F aircraft has vacated Runway 15 due to absence of Runway 22L holding point markings on runway 15.
Arriving Code-F aircraft waiting for a parking position may need to absorb delay on an intermediate holding point on Taxiway Z until the parking stand is available. Other traffic may use taxiway AV instead of Z to get around the aircraft.
VFR traffic
Parking
General VFR traffic will normally be parked at Apron 3.
- Light aircraft pilots will usually get to choose their parking spot after landing. ATC will instruct the pilot to taxi to apron 3 via DL or AD.
- At rare occasions stand 351 or 352 may be blocked by a larger aircraft. Taxi to these stands is performed via taxiway DM.
Local restrictions
- VFR flights are restricted during peak hours and during simultaneous IFR approaches to parallel runways (04L/R or 22L/R). Check ATIS prior to flight!
- VFR flights shall not climb above 1000 FT without explicit clearance from ATC.
Helsinki Control Zone is ATS airspace classification D with vertical limits SFC - 1300 FT.
- VFR traffic is not separated from other traffic in the Control Zone
- Traffic information is given by Helsinki Tower
- VFR pilots are expected to maintain sufficient separation to other IFR or VFR traffic when traffic information is provided
Visual Reporting Point OGELI may be used only used for SAR flights.
Visual Reporting Points DEGER, NOKKA and RASTI shall not be used for any VFR traffic leaving or entering the Control Zone.
- Find the Visual Approach Chart HERE.
Departing VFR
- Request start-up and clearance on initial contact with ATC
- State any requests such as the use of a specific runway for departure
- ATC clearance is usually given on stand
| 🧑🏻✈ | HELSINKI GROUND, OH-CME, CESSNA 172, APRON 3, INFORMATION MIKE, QNH 1011, REQUEST START-UP |
| 🎧 | O-ME, HELSINKI GROUND. START-UP APPROVED, RUNWAY 15, LEAVE CONTROL ZONE VIA LILJA, 1000 FT OR BELOW, SQUAWK 0355 |
| 🧑🏻✈ | START-UP APPROVED, RUNWAY 15, LEAVE CONTROL ZONE VIA LILJA, 1000 FT OR BELOW, SQUAWK 0355, O-ME |
- When ready for departure, ATC may give departure restrictions. Please follow all clearances given by ATC.
- Pilots are requested to report when leaving the Control Zone.
- If cleared via VRP: "O-ME, LILJA OUTBOUND"
- If cleared direct en-route: "O-ME, CONTROL ZONE BOUNDARY OUTBOUND"
Arriving VFR
- Report your position and intentions on initial contact with Helsinki Tower when approaching the Control Zone boundary.
- Helsinki tower will normally give clearance to a part of the traffic circuit serving the runway in use.
- During peak hours VFR flights might be cleared to visual holdings or to absorb delay with other means such as orbitting.
| 🧑🏻✈ | HELSINKI TOWER, OH-CME, CESSNA 172, RADIAL 360, 20 MILES FROM HELSINKI, 1000 FT, INFORMATION MIKE, QNH 1011 FOR LANDING |
| 🎧 | O-ME, HELSINKI TOWER, VIA TURFI JOIN RIGHT BASE LEG RUNWAY 22 LEFT, 1000 FT OR BELOW |
| 🧑🏻✈ | VIA TURFI JOIN RIGHT BASE LEG 1000 FT OR BELOW, O-ME |
- Pilots are requested to report once established on the downwind leg
- Pilots shall report on final if Tower has not given a clearance to use the runway (landing, touch-and-go, low approach etc.)
Traffic Circuit
- Local VFR flights (normally training flights) may be cleared for a traffic circuit.
| 🧑🏻✈ | HELSINKI GROUND, OH-CME, CESSNA 172, REQUEST START-UP |
| 🎧 | O-ME, HELSINKI GROUND, START-UP APPROVED, CLEARED TRAFFIC CIRCUIT RUNWAY 15, 1000 FT OR BELOW, SQUAWK 0422 |
| 🧑🏻✈ | START-UP APPROVED, CLEARED TRAFFIC CIRCUIT RUNWAY 15, 1000 FT OR BELOW, O-ME |
- Pilots are requested to report once established on the downwind leg
- Pilots shall report on final if Tower has not given a clearance to use the runway (landing, touch-and-go, low approach etc.)
Delaying VFR traffic
-
Tower may delay VFR traffic when traffic information is not sufficient
-
Examples of delay action:
- orbit left/right
- make three-sixty left/right
- extend downwind
- join holding ...
-
Please follow the clearances given by Helsinki Tower
Flight Plan instructions
Flight planning is an essential phase of your flight. A good flight plan will give Air Traffic Control sufficient information regarding your intentions and reduces the need to ask intentions during the flight.
Traffic circuit
Traffic circuit is marked with TC in the ROUTE field.
TC can be further specified in FPL field-18 ('remarks field') as follows:
- Conducting one spot landing:
- RMK/1SL
- Conducting a practiced forced landing after which the flight continues to two training areas:
- RMK/PFL 2TA
- Conducting two spot landings after which the flight continues to a training area:
- RMK/2SL TA
| Most common abbreviations | |
|---|---|
| FS | Full Stop (Ladning) |
| LA | Low Approach |
| TA | Training Area |
| AP | Approaches |
| TGL | Touch and Go Landing |
| TC | Traffic Circuit |
| SL | Spot Landing |
| PFL | Practiced Forced Landing |
| PFLR | Practiced Forced Landing back to Runway |
En-route flights
- It is highly recommended to plan via Visual Reporting Points. These points are indicated on the Visual Approach Chart.
- Unless otherwise specified in a flight plan, ATC will assume the aircraft will fly straight from the departure aerodrome to the destination aerodrome as filed.
- If this is to be significantly deviated from, the planned flight route must be shown in the FPL. In such a case the route can, when required, also be inserted using the plain-language place names.
- Example: (EFHK) LINTU NUMMELA VIILA (EFTP)
- If you wish to join the traffic circuit at Helsinki, add "TC" to the route and mark your requested approaches in the remarks section, e.g. "RMK/EFHK 2TGL"
Example flight plan
VFR flight leaving Control Zone and re-entry for traffic circuit performing 2 touch-and-go landings, 2 spot landings and 1 full-stop landing:
Helicopter flights
VFR helicopters may choose the take-off or landing location.
| Take-off and landing locations | ||
|---|---|---|
| Location | Within Maneuvering Area? | Remarks |
| Runways | YES | |
| FATO H16/H34 | YES | Serving traffic to Apron 4 |
| Helipad Y | YES | Serving traffic to Apron 3 |
| FATO FH10 | YES | Medical helicopter FinnHEMS 10 |
Example phraseology:
| 🚁 | HELSINKI TOWER, OH-HEH, ROBINSON 44, EAST OF HELSINKI, 1200 FT, ESTIMATING LILJA IN 4 MINUTES FOR LANDING, APRON 3 |
| 🎧 | O-EH, HELSINKI TOWER, CLEARED HELSINKI CONTROL ZONE VIA LILJA, DIRECT HELIPAD Y, 1000 FT OR BELOW, QNH 1011 |
| 🚁 | CLEARED HELSINKI CONTROL ZONE VIA LILJA, DIRECT HELIPAD Y, 1000 FT OR BELOW, QNH 1011, O-EH |
| 🚁 | O-EH, LILJA INBOUND |
| 🎧 | O-EH |
| 🎧 | O-EH, WIND VARIABLE 4 KNOTS, HELIPAD Y CLEARED TO LAND, CLEARED TO CROSS RUNWAY 33 |
| 🚁 | HELIPAD Y CLEARED TO LAND, CLEARED TO CROSS RUNWAY 33, O-EH |
| 🎧 | O-EH, AIR-TAXI VIA DL TO APRON 3 |
| 🚁 | AIR-TAXI VIA DL TO APRON 3, O-EH |
Outside Maneuvering Area
When departing or landing outside of the Maneuvering Area, pilots are requested to report airborne or to report on ground. No take-off or landing clearance will be issued.
- You can view the Maneuvering Area boundaries from the Aerodrome Charts (APDC). The Area is marked with a gray line called "ATC SER BDRY" on the charts in AIP Finland.
| 🎧 | O-EH, WIND CALM, MAKE APPROACH TO APRON 7, REPORT ON GROUND, CLEARED TO CROSS RUNWAY 04L |
| 🚁 | MAKE APPROACH TO APRON 7, CLEARED TO CROSS RUNWAY 04L, WILCO, O-EH |
Special VFR
VMC Conditions
| Airspace class | Minimum visibility | Minimum cloud ceiling |
|---|---|---|
| D (Control Zone) | 5 km | BKN or OVC 1000 ft |
When the visibility is less than 5 km and/or when the cloud ceiling is below 1000 ft, ATC may give clearance for Special VFR, and the minima may be reduced to:
- minimum visibility 1500 m
- minimum cloud ceiling 600 ft
Special VFR traffic is separated from all other traffic by ATC
Geographical Restrictions for Separation
ATC may restrict a VFR flight to remain outside of the IFR Approach Funnel in order to separate a Special VFR aircraft from other aircraft.
| 🎧 | O-BC, leave control zone via Kitka, special VFR, after departure remain outside of IFR approach funnel. O-BC, jätä lähialue Kitkan kautta, erityis-VFR, lähdön jälkeen pysy pois IFR-lähestymisen suojaalueelta. |
| 🎧 | O-BC, report when outside of IFR approach funnel. O-BC, ilmoita kun pois IFR-lähestymisen suoja-alueelta. |
| 🎧 | O-BC, LEAVE CONTROL ZONE VIA LINTU, SPECIAL VFR, AFTER DEPARTURE REMAIN OUTSIDE OF IFR APPROACH FUNNEL |
| 🎧 | O-BC, REPORT WHEN OUTSIDE OF IFR APPROACH FUNNEL |
ATC may give a warning when a possibility of IMC conditions is present, especially during a change from IFR to VFR.
| 🎧 | O-BC, INSTRUMENT METEOROLOGICAL CONDITIONS REPORTED / FORECASTED IN THE VICINITY OF HELSINKI |
| 👨✈️ | ROGER, MAINTAINING IFR, O-BC |
De-icing procedures
At Helsinki Airport we are delighted to provide proper de-icing services for your needs! Helsinki is known for its smooth winter operations, so why not bring it here to Vatsim! To make your experience better, we recommend using GSX PRO to simulate remote de-icing.
The following positions can be manned during winter season:
| Logon code | Call sign | Frequency |
|---|---|---|
| EFHK_C_GND | Remote De-icing Supervisor | 133.850 |
| EFHK_D_GND | De-icing (operator) | 121.675 |
The positions above may be used during Welcome to HEL or other events.
Pilots may request for de-icing even if the positions above are not manned. In that case Helsinki Ground or Tower will handle the communications.
Pilot procedures
Before start-up
- Order de-icing from Remote De-icing Supervisor 133.850 before start-up. You need to receive en-route clearance from EFHK_DEL before requesting de-icing:
| 🧑🏻✈ | HELSINKI DE-ICING, FINNAIR 1, REQUEST DEICING FOR WINGS AND TAIL |
| 🎧 | FINNAIR 1, DE-ICING ON REMOTE APRON 6 |
- After the request you may switch back to previous frequency
Operations at remote de-icing apron
- ATC will give you taxi instructions to an intermediate holding point
- Apron 6: DC1 or GC1
- Apron 8: AV1 or VS1
- ATC will advise you to contact Remote De-icing Supervisor:
| 🎧 | FINNAIR 1, CONTACT REMOTE DE-ICING SUPERVISOR 133.850 |
| 🧑🏻✈ | 133.850, FINNAIR 1 |
- You will receive taxi instructions to de-icing stand
| 🧑🏻✈ | FINNAIR 1, APPROACHING DC1 |
| 🎧 | FINNAIR 1, TAXI TO STAND 603 |
| 🧑🏻✈ | TAXI TO STAND 603, FINNAIR 1 |
- De-icing Supervisor may advise you to contact de-icing operator when parking brake is set
| 🎧 | FINNAIR 1, WHEN PARKING BRAKE SET, CONTACT DE-ICING 121.675 |
| 🧑🏻✈ | WHEN PARKING BRAKE SET, 121.675, FINNAIR 1 |
- Contact De-icing operator and request the de-icing procedure you want
- General tip: request 2-step de-icing only when it is snowing
| 🧑🏻✈ | DE-ICING, FINNAIR 1, PARKING BRAKE SET, REQUESTING ONE STEP DE- ICING FOR WINGS AND STABILIZER, YOU MAY START SPRAYING |
| 🎧 | FINNAIR 1 ON STAND 603, DE-ICING, STARTING ONE STEP PROCEDURE FOR WINGS AND STABILIZER, REPORT WHEN DE-ICING COMPLETED |
| 🧑🏻✈ | WILCO, FINNAIR 1 |
- Now you will wait until the de-icing in your simulator is completed. When de-icing is finished, the de-icing operator will give you the end report which should be read back:
| 🧑🏻✈ | FINNAIR 1, STAND 601, DE-ICING COMPLETED |
| 🎧 | FINNAIR 1 ON STAND 601, DE-ICING COMPLETED FOR WINGS AND TAIL WITH TYPE 1 FLUID, MIXTURE 40%, HOLDOVER TIME STARTED AT 55, POST DE- AND ANTI-ICING CHECKS ARE COMPLETED |
| 🧑🏻✈ | TYPE 1, MIXTURE 40%, HOLD OVER TIME 55, FINNAIR 1 |
| 🎧 | FINNAIR 1, CORRECT, FOR TAXI CONTACT TOWER 118.850 |
| 🧑🏻✈ | 118.850, FINNAIR 1 |
- The de-icing process is now completed, and you will receive taxi instructions towards the departure runway – Have a nice flight! 🙂
Map of de-icing areas
REMOTE 6 map
REMOTE 8 map
DEICE Application for EFHK
This app is still work in progress.
- Link to application: ice.lusep.fi
You need to be connected on VATSIM network as a pilot and send the flight plan with departure EFHK before connecting to the application!
- Pilots may request the deice treatment from the application before start-up!
- If the request is not approved within a few minutes, please revert back to voice procedures, as it is not mandatory for ATC to use the application in any way.
- Pilots can also view the holdover times for the fluid types used at Helsinki
🔵 EFIV - Ivalo
Located in the pristine landscapes of northern Lapland, Ivalo Airport serves as one of Finland's key entry points to the Arctic wonders. Situated approximately 9 kilometers from the Ivalo village and in close proximity to the popular Saariselkä ski resort, this airport welcomes travelers and aviators eager to experience the mesmerizing northern lights, vast tundra expanses, and thrilling winter adventures that only this unique region can offer.
Ivalo Airport has a single asphalt runway capable of accommodating a variety of aircraft, ranging from small private planes to larger commercial airliners.
| IATA | ICAO | Charts |
|---|---|---|
| IVL | EFIV | Finland AIP - EFIV |
ATC positions
Ivalo is a controlled airport with aerodrome control- and approach control service. The service is combined to one Air Traffic Controller (tower-radar).
During low traffic, Ivalo airport can also be operated with AFIS (Aerodrome Flight Information Service).
Pilots can identify the level of service provided from the Vatsim logon code (or by the ATC information text):
| Logon code | Call sign | Frequency | Responsibilities |
|---|---|---|---|
| EFIV_R_TWR | IVALO TOWER | 118.000 | Ground movement, Ivalo Control Zone & Terminal Area |
| EFIV_I_TWR | IVALO INFORMATION | 118.000 | Ground movement, Ivalo Upper- and Lower Flight Information Zones |
Ground layout
- The main apron is located next to the Control Tower southeast of the runway
- Access the main apron via B or E
- The general aviation apron can be accessed via taxiway C
Runways
Ivalo is equipped with one runway 04/22. When the wind direction and weather conditions allows, the runway is usually selected to suit the traffic needs. Runway 04 is often used which allows for a shorter arrival route and eliminates the need of backtracks.
Take-offs from runway intersections can be performed upon the pilot's request the traffic situation permitting.
Currently available stands
Stand restrictions & push back procedures
- All stands on the main apron can fit airplanes up to A321/B739
- In low traffic levels ATC will assign stands in order to eliminate the need of push back
En-route clearance
Please, do not include the SID in your flight plan route.
By default the local tower controller will give clearance to requested cruise flight level.
Departure with SID:
| 🎧 | Fastair 312, cleared to Helsinki, runway 22, Sotit 2D departure, flight level 350, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 22, Sotit 2D lähtöreitti, lentopinta 350, koodaa 5542 |
Departure with direct route:
| 🎧 | Fastair 312, cleared to Helsinki, runway 22, direct Ibosu, flight level 350, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 22, lähdöstä suoraan Ibosu, lentopinta 350, koodaa 5542 |
Approach
Please, do not include the STAR in your flight plan route.
Runway 22 is the only runway with an ILS approach system. This makes runway 22 the preferred runway in Low Visibility conditions.
When approaching runway 04, pilots may expect to be cleared for RNP approach (or visual approach upon pilot request).
Arriving aircraft may be cleared for the approach already on initial contact with the local controller. Please be ready to copy any clearance and instructions.
Phraseology example:
- On initial contact with approach control, please include the following:
- Call sign
- Current flight level
- Assigned flight level
- Aircraft type (and wake turbulence category if necessary)
- Received ATIS broadcast
- Other restrictions given by previous controller
| 👨✈️ | Ivalo tower, Finnair 639, passing flight level 192, descending flight level 100, Airbus 321, information L Ivalon torni, Finnair 639, läpi lentopinta 192, laskeudutaan lentopinnalle 100, Airbus 321, tiedotus L |
| 🎧 | Finnair 639, Ivalo tower, radar contact, continue descent to 3500 feet, QNH 1014, cleared RNP approach runway 04, report final approach course, for information next 15 miles below flight level 95 uncontrolled airspace Finnair 639, Ivalon torni, tutkayhteys, jatka laskeutumista 3500 jalkaan, QNH 1014, selvä RNP lähestymiseen kiitotie 04, ilmoita loppulähestymissuunnassa, tiedoksi seuraavat 15 mailia alle lentopinnan 95 valvomatonta ilmatilaa |
| 👨✈️ | Continue descent to 3500 feet, QNH 1014, cleared RNP approach runway 04, wilco, Finnair 639 Jatkan laskeutumista 3500 jalkaan, QNH 1014, selvä RNP lähestymiseen kiitotie 04, ilmoitan, Finnair 639 |
If EFIV_I_TWR is online, please check the AFIS pilot guide: AFIS (Aerodrome Flight Information Service).
Reduced Radar Coverage
Due to high terrain and location of the nearest SSR radar, aircraft flying at low altitudes are not visible on ATC radar screen.
Arriving aircraft may expect to hear "radar service terminated" prior reaching the initial approach fix. This can just be acknowledged by the pilot and it does not affect the flight crew in any way.
Departing aircraft are requested to report their passing flight level by ATC when the aircraft is visible on the radar screen and radar service is established.
Map of reduced radar coverage
Work in progress
Operations in Low Visibility Conditions
Take-offs are allowed when the reported RVR is between 550 meters and 400 meters, provided that only one aircraft at a time is in the manoeuvring area.
Ivalo has only ILS CAT I approach available for runway 22 with the following minimas OCA (H):
- Category A: 616 (152)
- Category B: 627 (163)
- Category C: 638 (174)
- Category D: 651 (187)
There are also LPV approaches available for both runways (Lateral Precision with Vertical Guidance Approach). See the RNP approach charts for more information.
🔵 EFJY - Jyväskylä
Image: kallerna. Wikimedia Commons, CC-BY-SA-4.0.
Jyväskylä Airport is situated in central Finland, around 20 kilometers north of Jyväskylä city center. It serves as a hub for both commercial and general aviation activities, though it primarily handles charter and training flights rather than regular commercial passenger services.
The airport is also home to a Finnish Air Force base, where the Air Force Academy conducts flight training and various military operations.
| IATA | ICAO | Charts |
|---|---|---|
| JYV | EFJY | Finland AIP - EFJY |
ATC positions
Jyväskylä is a controlled airport with aerodrome control- and approach control service. This service can be combined (tower-radar), or separate. Jyväskylä Arrival and/or Ground can also be opened according to the demand.
| Logon code | Call sign | Frequency | Responsibilities |
|---|---|---|---|
| EFJY_GND | JYVÄSKYLÄ GROUND | 121.850 | ATC Clearance & Ground Movement |
| EFJY_TWR | JYVÄSKYLÄ TOWER | 118.000 | Jyväskylä Control Zone |
| EFJY_R_TWR | JYVÄSKYLÄ TOWER | 118.000 | Jyväskylä Control Zone & Terminal Area |
| EFJY_APP | JYVÄSKYLÄ RADAR | 127.000 | Jyväskylä Terminal Area |
| EFJY_R_APP | JYVÄSKYLÄ ARRIVAL | 128.800 | Jyväskylä Terminal Area - arrivals below 5000 FT |
Ground layout
- The main apron is located next to the Control Tower north-east of the runway
- Stands 1, 2, 3 and 4 may be used for passenger flights
- All stands are designed so that push back is not necessary
- General aviation aircraft are usually parked on the apron next to taxiway V
The area south of the runway is for military only. There are also taxiways north of taxiway T leading to aprons for military traffic and QRA flights.
Runways
Jyväskylä airport has one runway, 12/30.
The ILS (Instrument Landing System) is in use for runway 30 only. The ILS system is used to conduct approaches under normal circumstances and in limited visibility conditions. The flight routes near the airport and the choice of runway direction are influenced by external conditions, such as wind speed and direction, cloud base, visibility, runway conditions, available approach procedures, and traffic situation.
Take-offs from runway intersections can be performed upon the pilot's request the traffic situation permitting
Currently available stands
Stand restrictions
- Stands 1, 2, 3 and 4 on the Civil Apron can fit up to Code C aeroplanes. Use caution when moving on the apron, especially if the other stand is blocked
- Military aircraft will not be assigned a stand after arrival. ATC will only give "taxi to Apron"
En-route clearance
Please, do not include the SID in your flight plan route.
By default the local tower controller will give clearance to requested cruise flight level.
There are no SID routes at Jyväskylä. Pilots may expect a DCT route or vector after departure.
- Please check the OMNIDIRECTIONAL DEPARTURES chart for the turning altitude:
- RWY 12: Climb straight ahead until 850 FT, then turn towards cleared waypoint or heading
- RWY 30: Climb straight ahead until 1130 FT, then turn towards cleared waypoint or heading
Departure with direct route:
| 🎧 | Fastair 312, cleared to Helsinki, runway 12, direct Xelma, flight level 100, expect radar climb, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 12, lähdöstä suoraan Xelma, lentopinta 100, odota tutka nousua, koodaa 5542 |
Departure with vector:
| 🎧 | Fastair 312, cleared to Helsinki, runway 12, after departure fly heading 090, climb to flight level 190, expect vectoring to Xelma, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 12, lähdön jälkeen lennä ohjaussuuntaan 090, nouse lentopinnalle 190, odota tutkavektorointia Xelmalle, koodaa 5542 |
Approach
Please, do not include the STAR in your flight plan route.
Runway 30 is the only runway with an ILS approach system. This makes runway 30 the preferred runway during Low Visibility Operations.
- ILS Z approach is used for RNAV capable aircraft
- ILS Y approach is used for non-RNAV aircraft (based on VOR navigation)
When runway 12 is in use, pilots may expect to be cleared for RNP approach.
Arriving aircraft may be cleared for the approach already on initial contact with the local controller. Please be ready to copy any clearance and instructions.
Phraseology example:
- On initial contact with approach control, please include the following:
- Call sign
- Current flight level
- Assigned flight level
- Aircraft type (and wake turbulence category if necessary)
- Received ATIS broadcast
- Other restrictions given by previous controller
| 👨✈️ | Jyväskylä tower, Finnair 285, flight level 190, when ready descending flight level 100, ATR 72, information L Jyväskylän torni, Finnair 285, lentopinta 190, kun valmis laskeudutaan lentopinnalle 100, ATR 72, tiedotus L |
| 🎧 | Finnair 285, Jyväskylä tower, radar contact, when ready descent to 2900 feet, QNH 998, via Etnup cleared RNP approach runway 12, report final approach course, for information next 20 miles below flight level 95 uncontrolled airspace Finnair 285, Jyväskylän torni, tutkayhteys, jatka laskeutumista 2900 jalkaan, QNH 998, Etnupin kautta selvä RNP lähestymiseen kiitotie 12, ilmoita loppulähestymissuunnassa, tiedoksi seuraavat 20 mailia alle lentopinnan 95 valvomatonta ilmatilaa |
| 👨✈️ | Continue descent to 2900 feet, QNH 998, via Etnup cleared RNP approach runway 12, wilco, Finnair 285 Jatkan laskeutumista 2900 jalkaan, QNH 998, Etnupin kautta selvä RNP lähestymiseen kiitotie 12, ilmoitan, Finnair 285 |
Operations in Low Visibility Conditions
Take-offs are allowed when the reported RVR is between 400 meters and 300 meters, provided that only one aircraft at a time is in the manoeuvring area.
The Low Visibility Procedures for Take-offs (LVPTO) procedure will be taken in force gradually as follows:
- RVR is 800 - 550 M
- RVR is less than 550 M
- Procedure will be in force when Touchdown zone (TDZ) or Midpoint or Stop End RVR-value falls below 550 M.
ATC will give the real RVR value(s) on frequency prior take-off or landing or whenever requested by the pilot.
The application of LVP procedures will be informed to the pilots by ATIS or ATC: "LOW VISIBILITY TAKE OFF PROCEDURES IN OPERATION".
Jyväskylä has only ILS CAT 1 approach available for runway 30.
There are also LPV approaches available for both runways (Lateral Precision with Vertical Guidance Approach). See the RNP approach charts for more information.
VFR Traffic Restrictions
If necessary, the number of aircraft cleared to fly in the aerodrome traffic circuit is restricted by ATC. The number of aircraft is determined by e.g. weather conditions or other traffic.
VFR traffic will normally be cleared via Visual Reporting Points (VRP) marked on the Visual Approach Chart in order to reduce noise impact and to better control the flow in and out of the Control Zone.
🔵 EFKT - Kittilä
Located in the heart of Lapland, Kittilä Airport is the gateway to a winter wonderland, serving as one of the busiest winter-season airports in Finland. Approximately 5 kilometers from Kittilä town center and 35 kilometers from the Levi ski resort, it is the perfect starting point for travelers and pilots drawn to the captivating northern lights, untouched wilderness, and winter sports activities this region offers.
Kittilä Airport has a single asphalt runway capable of accommodating a variety of aircraft, ranging from small private planes to larger commercial airliners.
| IATA | ICAO | Charts |
|---|---|---|
| KTT | EFKT | Finland AIP - EFKT |
ATC positions
Kittilä is a controlled airport with aerodrome control- and approach control service. The service is combined to one Air Traffic Controller (tower-radar).
During low traffic, Kittilä airport can also be operated with AFIS (Aerodrome Flight Information Service).
Pilots can identify the level of service provided from the Vatsim logon code (or by the ATC information text):
| Logon code | Call sign | Frequency | Responsibilities |
|---|---|---|---|
| EFKT_DEL | KITTILÄ DELIVERY | 123.100 | Clearance delivery during peak hours |
| EFKT_R_TWR | KITTILÄ TOWER | 120.150 | Ground movement, Kittilä Control Zone & Terminal Area |
| EFKT_I_TWR | KITTILÄ INFORMATION | 120.150 | Ground movement, Kittilä Upper- and Lower Flight Information Zones |
Ground layout
- The main apron is located next to the Control Tower east of the runway
- The main apron has recently been enlargened and the main taxiway T has been extended to holding point L.
Runways
Kittilä is equipped with one runway 16/34. The preferred runway is considered to be runway 16 for departures and runway 34 for arrivals.
Take-offs from runway intersections can be performed upon the pilot's request the traffic situation permitting.
Currently available stands
Stand restrictions & push back procedures
- All stands on the main apron can fit airplanes up to A321/B739
- Stands 11B, 13B and 14B are used when possible to eliminate the need of push back
- These stands are often used during summer season when traffic levels are lower
- When these stands are occupied, stands 11, 12, 13, 14 and 15 can not be used
- All other stands (7 - 18) require push back for Code C aircraft and bigger.
En-route clearance
Please, do not include the SID in your flight plan route.
By default the local tower controller will give clearance to requested cruise flight level.
Departure with SID:
| 🎧 | Fastair 312, cleared to Helsinki, runway 16, Tugpu 1C departure, flight level 350, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 16, Tugpu 1C lähtöreitti, lentopinta 350, koodaa 5542 |
Departure with direct route:
| 🎧 | Fastair 312, cleared to Helsinki, runway 16, direct Tugpu, flight level 350, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 15, lähdöstä suoraan Tugpu, lentopinta 350, koodaa 5542 |
Approach
Please, do not include the STAR in your flight plan route.
Runway 34 is the only runway with an ILS approach system. This makes runway 34 the preferred runway during Low Visibility Operations.
- ILS Z or LOC Z approach is used for RNAV capable aircraft
- ILS Y or LOC Y approach is used for non-RNAV aircraft (ADF and DME required)
When approaching runway 16, pilots may expect to be cleared for LOC or RNP approach.
Arriving aircraft may be cleared for the approach already on initial contact with the local controller. Please be ready to copy any clearance and instructions.
Phraseology example:
- On initial contact with approach control, please include the following:
- Call sign
- Current flight level
- Assigned flight level
- Aircraft type (and wake turbulence category if necessary)
- Received ATIS broadcast
- Other restrictions given by previous controller
| 👨✈️ | Kittilä tower, Finnair 8LD, passing flight level 192, descending flight level 100, Embraer 190, information L Kittilän torni, Finnair 8LD, läpi lentopinta 192, laskeudutaan lentopinnalle 100, Embraer 190, tiedotus L |
| 🎧 | Finnair 8LD, Kittilä tower, radar contact, continue descent to 3800 feet, QNH 1014, cleared LOC-Z approach runway 16, right circuit, report established on localizer, for information next 17 miles below flight level 95 uncontrolled airspace Finnair 8LD, Kittilän torni, tutkayhteys, jatka laskeutumista 3800 jalkaan, QNH 1014, selvä LOC-Z lähestymiseen kiitotie 16, oikea kierros, ilmoita suuntasäteessä, tiedoksi seuraavat 16 mailia alle lentopinnan 95 valvomatonta ilmatilaa |
| 👨✈️ | Continue descent to 3800 feet, QNH 1014, cleared LOC-Z approach runway 16, right circuit, wilco, Finnair 8LD Jatkan laskeutumista 3800 jalkaan, QNH 1014, selvä LOC-Z lähestymiseen kiitotie 16, oikea kierros, ilmoitan, Finnair 8LD |
Reduced Radar Coverage
Due to high terrain and location of the nearest SSR radar, aircraft flying at low altitudes are not visible on ATC radar screen.
Approaching aircraft for runway 16 may expect to hear "radar service terminated" prior reaching the initial approach fix. This can just be acknowledged by the pilot and it does not affect the flight crew in any way.
Departing aircraft are requested to report their passing flight level by ATC when the aircraft is visible on the radar screen and radar service is established.
Map of reduced radar coverage
Operations in Low Visibility Conditions
Take-offs are allowed when the reported RVR is between 550 meters and 400 meters, provided that only one aircraft at a time is in the manoeuvring area.
Kittilä has only ILS CAT I approach available for runway 34 with the following minimas OCA (H):
- Category A: 844 (200)
- Category B: 858 (214)
- Category C: 875 (231)
- Category D: 895 (251)
There is also LPV approaches available for both runways (Lateral Precision with Vertical Guidance Approach). See the RNP approach charts for more information.
🔵 EFKU - Kuopio
Kuopio Airport is located in the heart of Finland's northern Lakeland district, approximately 14 kilometers north of Kuopio city center. It is the seventh busiest airport in Finland, serving both commercial and general aviation flights.
Kuopio also has a Finnish Air Force base, with the Karelia Air Command making use of the airport for various training and operational purposes.
| IATA | ICAO | Charts |
|---|---|---|
| KUO | EFKU | Finland AIP - EFKU |
ATC positions
Kuopio is a controlled airport with aerodrome control- and approach control service. This service can be combined (tower-radar), or separate. Kuopio Arrival position can also be opened when arrival rate is high.
| Logon code | Call sign | Frequency | Responsibilities |
|---|---|---|---|
| EFKU_TWR | KUOPIO TOWER | 120.150 | Ground movement, Kuopio Control Zone |
| EFKU_R_TWR | KUOPIO TOWER | 120.150 | Ground movement, Kuopio Control Zone & Terminal Area |
| EFKU_APP | KUOPIO RADAR | 130.600 | Kuopio Terminal Area |
| EFKU_R_APP | KUOPIO ARRIVAL | 122.850 | Kuopio Terminal Area - arrivals below 5000 FT |
Ground layout
- The main apron is located next to the Control Tower south of the runway
- Stands 1, 2, 3 and 4 can be used for passenger flights
- All stands are designed so that push back is not necessary
- General aviation aircraft are usually parked on the apron next to taxiway H
There is a military apron south of the runway next to taxiways L and G. There are also two aprons north of the runway used for military traffic and QRA flights.
Runways
Kuopio is equipped with one runway 15/33. The preferred runway is considered to be runway 15 for departures and runway 33 for arrivals.
Take-offs from runway intersections can be performed upon the pilot's request the traffic situation permitting
Currently available stands
Stand restrictions
- Stands 1, 2, 3 and 4 can fit up to Code C aeroplanes. Use caution when moving on the apron, especially if the other stand is blocked
- There are two additional unmarked parking stands A and B that can fit Code E aeroplanes. These stands shall not be used for smaller aeroplanes
When stand A is in use, the main taxiway between B and C cannot be used. Additionally stand 4 shall be empty.
When stand B is in use, stands 3 and 4 shall be empty.
Code E aeroplanes
| Code | ICAO | Aircraft type | Wingspan M |
|---|---|---|---|
| 🔵 E | B77W, B77L | Boeing 777-300ER, -200LR, -F | 64.8 |
| 🔵 E | A359, A35K | Airbus A350-900, A350-1000 | 64.75 |
| 🔵 E | B744 | Boeing 747-400 | 64.44 |
| 🔵 E | A345, A346 | Airbus A340-500, -600 | 63.45 |
| 🔵 E | B772, B773 | Boeing 777-300, -200 | 60.93 |
| 🔵 E | A332, A333, A342, A343 | Airbus A330-200, -300, Airbus A340-200, -300 | 60.3 |
| 🔵 E | B788, B789, B78X | Boeing Dreamliner 787-8, 787-9, 787-10 | 60.12 |
| 🔵 E | IL96 | Iljushin IL-96 | 60.11 |
| 🔵 E | B742, B743 | Boeing 747-200, -300 | 59.6 |
En-route clearance
Please, do not include the SID in your flight plan route.
By default the local tower controller will give clearance to requested cruise flight level.
Departure with SID:
| 🎧 | Fastair 312, cleared to Helsinki, runway 15, Astux 3C departure, flight level 230, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 15, Astux 3C lähtöreitti, lentopinta 230, koodaa 5542 |
Departure with direct route:
| 🎧 | Fastair 312, cleared to Helsinki, runway 15, direct Astux, flight level 100, expect radar climb, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 15, lähdöstä suoraan Astux, lentopinta 100, odota tutka nousua, koodaa 5542 |
Approach
Please, do not include the STAR in your flight plan route.
Runway 33 is the only runway with an ILS approach system. This makes runway 33 the preferred runway during Low Visibility Operations.
- ILS Z approach is used for RNAV capable aircraft
- ILS Y approach is used for non-RNAV aircraft (based on VOR navigation)
When approaching runway 15, pilots may expect to be cleared for RNP approach.
Arriving aircraft may be cleared for the approach already on initial contact with the local controller. Please be ready to copy any clearance and instructions.
Phraseology example:
- On initial contact with approach control, please include the following:
- Call sign
- Current flight level
- Assigned flight level
- Aircraft type (and wake turbulence category if necessary)
- Received ATIS broadcast
- Other restrictions given by previous controller
| 👨✈️ | Kuopio tower, Finnair 42T, flight level 190, when ready descending flight level 100, ATR 72, information L Kuopion torni, Finnair 42T, lentopinta 190, kun valmis laskeudutaan lentopinnalle 100, ATR 72, tiedotus L |
| 🎧 | Finnair 42T, Kuopio tower, radar contact, when ready descent to 2700 feet, QNH 998, via Giluv cleared ILS-Z approach runway 33, report established on localizer, for information next 20 miles below flight level 95 uncontrolled airspace Finnair 42T, Kuopion torni, tutkayhteys, jatka laskeutumista 2700 jalkaan, QNH 998, Giluvin kautta selvä ILS-Z lähestymiseen kiitotie 33, ilmoita suuntasäteessä, tiedoksi seuraavat 20 mailia alle lentopinnan 95 valvomatonta ilmatilaa |
| 👨✈️ | Continue descent to 2700 feet, QNH 998, via Giluv cleared ILS-Z approach runway 33, wilco, Finnair 42T Jatkan laskeutumista 2700 jalkaan, QNH 998, Giluvin kautta selvä ILS-Z lähestymiseen kiitotie 33, ilmoitan, Finnair 42T |
Operations in Low Visibility Conditions
Take-offs are allowed when the reported RVR is between 550 meters and 400 meters, provided that only one aircraft at a time is in the manoeuvring area.
Kuopio has only ILS CAT 1 approach available for runway 33 with the following minimas OCA (H):
- Category A: 469 (153)
- Category B: 479 (163)
- Category C: 491 (175)
- Category D: 503 (187)
There is also LPV approaches available for both runways (Lateral Precision with Vertical Guidance Approach). See the RNP approach charts for more information.
🔵 EFOU - Oulu
Oulu Airport is not only the second busiest in Finland, but also serves as a significant gateway to Northern Scandinavia. Situated approximately 11 kilometers west of the Oulu city center, this airport plays an instrumental role in connecting the Northern part of the country with the rest of Finland.
The airport, operated by Finavia, handled over a million passengers in 2019 and serves as a hub for diverse types of air traffic. While it primarily serves commercial airlines, it also supports a variety of other aircraft including general aviation, parachute jump flights, private jets and medical helicopter service.
| IATA | ICAO | Charts |
|---|---|---|
| OUL | EFOU | Finland AIP - EFOU |
ATC positions
Oulu is a controlled airport with aerodrome control- and approach control service. This service can be combined (tower-radar), or separate.
| Logon code | Call sign | Frequency | Responsibilities |
|---|---|---|---|
| EFOU_TWR | OULU TOWER | 124.400 | Ground movement, Oulu Control Zone |
| EFOU_R_TWR | OULU TOWER | 124.400 | Ground movement, Oulu Control Zone & Terminal Area |
| EFOU_APP | OULU RADAR | 118.150 | Oulu Terminal Area |
Ground layout
- The main apron is located north of runway 30 threshold
- Stands 13 to 16 are equipped with jetbridges
- General aviation aircraft are usually parked at Apron 3 (taxiway G)
- Medical helicopter base is located at the end of taxiway V
Military apron is located south of the runway at taxiway M.
Runways
Oulu is equipped with one runway 12/30. The preferred runway is considered to be runway 12 for arrivals and runway 30 for departures.
Take-offs from the runway intersections can be performed upon the pilot's request the traffic situation permitting 0500-2000 UTC (0400-1900 UTC).
Currently available stands
Stand restrictions
En-route clearance
Please, do not include the SID in your flight plan route.
By default the local tower controller will give clearance to requested cruise flight level.
Departure with SID:
| 🎧 | Fastair 312, cleared to Helsinki, runway 12, Miknu 4A departure, flight level 350, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 12, Miknu 4A lähtöreitti, lentopinta 350, koodaa 5542 |
SID route is mandatory for jet aircraft with sufficient equipment from runway 12 due noise abatement.
Departure with direct route:
| 🎧 | Fastair 312, cleared to Helsinki, runway 12, direct Ibosu, flight level 150, expect radar climb, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 12, lähdöstä suoraan Ibosu, lentopinta 150, odota tutka nousua, koodaa 5542 |
Approach
Please, do not include the STAR in your flight plan route.
Runway 12 is the only runway with an ILS approach system. This makes runway 12 the preferred runway during Low Visibility Operations.
- ILS Z approach is used for RNAV capable aircraft
- ILS Y approach is used for non-RNAV aircraft (based on VOR navigation)
When approaching runway 30, pilots may expect to be cleared for RNP approach.
Arriving aircraft may be cleared for the approach already on initial contact with the local controller. Please be ready to copy any clearance and instructions.
Phraseology example:
- On initial contact with approach control, please include the following:
- Call sign
- Current flight level
- Assigned flight level
- Aircraft type (and wake turbulence category if necessary)
- Received ATIS broadcast
- Other restrictions given by previous controller
| 👨✈️ | Oulu tower, Finnair 4MW, passing flight level 202 for flight level 100, Airbus 320, information Q Oulun torni, Finnair 4MW, läpäisen lentopinnan 202 lentopinnalle 100, Airbus 320, tiedotus Q |
| 🎧 | Finnair 4MW, Oulu tower, radar contact, continue descent to 2300 feet, QNH 1032, cleared ILS Z approach runway 12, right circuit, report established on localizer, for information next 20 miles below flight level 95 uncontrolled airspace Finnair 4MW, Oulun torni, tutkayhteys, jatka laskeutumista 2300 jalkaan, QNH 1032, selvä ILS Z lähestymiseen kiitotie 12, oikea kierros, ilmoita suuntasäteessä, tiedoksi seuraavat 20 mailia alle lentopinnan 95 valvomatonta ilmatilaa |
| 👨✈️ | Continue descent to 2300 feet, QNH 1032, cleared ILS Z approach runway 12, right circuit, wilco, Finnair 4MW Jatkan laskeutumista 2300 jalkaan, QNH 1032, selvä ILS Z lähestymiseen kiitotie 12, oikea kierros, ilmoitan, Finnair 4MW |
Operations in Low Visibility Conditions
Runways 12 and 30 are approved for Low Visibility Procedures for Take-offs (LVPTO).
- LVPTO is used when the RVR value is 550 M or less.
Runway 12 is approved for ILS CAT II approaches. The approach procedure has the following minimas OCA (H):
- Category A: 112 (65)
- Category B: 124 (77)
- Category C: 136 (89)
- Category D: 152 (105)
There is also LPV approaches available for both runways (Lateral Precision with Vertical Guidance Approach). See the RNP approach charts for more information.
LVP initiation
Low Visibility Procedures for all air traffic will become effective when the RVR value decreases to 550 M.
Medical helicopter
Note! The base of medical helicopter is located at the airport. The call sign of the medical helicopter is “Finnhems”.
General information
| ICAO call sign | FIH 50 |
| SSR code | 0005 |
| Agreed route | DCT, MAX 1300 FT |
| base flight rules | VFR (IFR visual take-off and landing approved) |
Medical helicopter pilot shall select transponder code 0005 prior to contacting Oulu Tower.
Departure from base
- VTOL PC1 take-off from FATO
- Initial climb in runway direction H110 or H290 (picture)
ATC will give VFR clearance (normally direct en-route, 1300 feet or below) and ask pilot to report when airborne. No take-off clearance is given when departing directly from apron.
Arrival to base
- Final approach in runway direction H110 or H290
- Aimpoint FIH FATO
- VTOL PC1 landing
ATC will normally give a clearance for approach to own base and ask the pilot to report on ground. No landing clearance is given when arriving directly to apron.
🔵 EFRO - Rovaniemi
Rovaniemi Airport holds the record of being the third busiest airport in Finland and the official airport of Santa Claus 🎅🏻. It is situated just 10 kilometers north of Rovaniemi city center and about 8 kilometers from Santa Claus Village at the Arctic Circle, making it a famous destination, especially during the holiday season.
Rovaniemi Airport's location presents unique challenges and opportunities in air traffic control due to its proximity to the Arctic Circle. It handles a diverse array of air traffic, including commercial, general aviation, private, and seasonal charter flights as well as medical helicopter service. It is equipped with a single runway, yet it efficiently manages the volume of air traffic.
| IATA | ICAO | Charts |
|---|---|---|
| RVN | EFRO | Finland AIP - EFRO |
ATC positions
Rovaniemi is a controlled airport with aerodrome control- and approach control service. This service can be combined (tower-radar), or separate. Rovaniemi Delivery and Arrival positions are opened only when necessary due high traffic levels.
| Logon code | Call sign | Frequency | Responsibilities |
|---|---|---|---|
| EFRO_DEL | ROVANIEMI DELIVERY | 118.525 | En-route clearance, (ground movement) |
| EFRO_TWR | ROVANIEMI TOWER | 118.700 | Ground movement, Rovaniemi Control Zone |
| EFRO_R_TWR | ROVANIEMI TOWER | 118.700 | Ground movement, Rovaniemi Control Zone and Terminal Area |
| EFRO_APP | ROVANIEMI RADAR | 129.900 | Rovaniemi Terminal Area |
| EFRO_R_APP | ROVANIEMI ARRIVAL | 118.600 | Rovaniemi Terminal Area - arrivals below 5000 FT |
Ground layout
- Main apron is located south of the runway next to taxiways B and H
- General aviation aircraft can park on the main apron General Aviation Parking Area
- Medical helicopter base is located at Q
Military apron is located north of runway 03/21
Runways
Rovaniemi is equipped with one runway 03/21. The preferred runway is considered to be runway 03 for departures and runway 21 for arrivals.
Civil aviation must use runway 21 as the primary landing runway at night 2000-0500 UTC (1900-0400 UTC).
Take-offs from the runway intersections can be performed upon the pilot's request the traffic situation permitting.
Currently available stands
Stand restrictions and push back
When stand 5B is occupied by a code F aeroplane, stands 3 to 5 and 13 to 15 shall be clear of traffic.
Code E and F aeroplanes
| Code | ICAO | Aircraft type | Wingspan M |
|---|---|---|---|
| 🔴 F | A388 | Airbus A380-800 | 79.8 |
| 🔴 F | A124 | Antonov AN-124-100 | 73.3 |
| 🔴 F | B748 | Boeing 747-8 | 68.5 |
| 🔴 F | C5M | Lockheed C-5 Super Galaxy | 67.9 |
| 🔵 E | B77W, B77L | Boeing 777-300ER, -200LR, -F | 64.8 |
| 🔵 E | A359, A35K | Airbus A350-900, A350-1000 | 64.75 |
| 🔵 E | B744 | Boeing 747-400 | 64.44 |
| 🔵 E | A345, A346 | Airbus A340-500, -600 | 63.45 |
| 🔵 E | B772, B773 | Boeing 777-300, -200 | 60.93 |
| 🔵 E | A332, A333, A342, A343 | Airbus A330-200, -300, Airbus A340-200, -300 | 60.3 |
| 🔵 E | B788, B789, B78X | Boeing Dreamliner 787-8, 787-9, 787-10 | 60.12 |
| 🔵 E | IL96 | Iljushin IL-96 | 60.11 |
| 🔵 E | B742, B743 | Boeing 747-200, -300 | 59.6 |
Push back procedures
| Stands | Push back procedure |
|---|---|
| 3B, 4B, 5B, 6B, 6C, 8B, 13, 14 and 16 | Push back is normally not required but provided by pilot request |
| 1, 2, 3, 4, 5, 6, 7, 8, 9 | Push back is required |
| 7B, 8C, 23 | No push back |
En-route clearance
Please, do not include the SID in your flight plan route.
By default the local tower controller will give clearance to requested cruise flight level.
Departure with SID:
| 🎧 | Fastair 312, cleared to Helsinki, runway 21, Renvi 3A departure, flight level 350, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 21, Renvi 3A lähtöreitti, lentopinta 350, koodaa 5542 |
Departure with direct route:
| 🎧 | Fastair 312, cleared to Helsinki, runway 21, direct Renvi, flight level 350, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 21, lähdöstä suoraan Renvi, lentopinta 350, koodaa 5542 |
Approach
Please, do not include the STAR in your flight plan route.
Runway 21 is the only runway with an ILS approach system. This makes runway 21 the preferred runway during Low Visibility Operations.
- ILS Z approach is used for RNAV capable aircraft
- ILS Y approach is used for non-RNAV aircraft (based on VOR navigation)
When approaching runway 03, pilots may expect to be cleared for RNP approach.
Arriving aircraft may be cleared for the approach already on initial contact with the local controller. Please be ready to copy any clearance and instructions.
Phraseology example:
- On initial contact with approach control, please include the following:
- Call sign
- Current flight level
- Assigned flight level
- Aircraft type (and wake turbulence category if necessary)
- Received ATIS broadcast
- Other restrictions given by previous controller
| 👨✈️ | Rovaniemi tower, Golden 332, passing flight level 202 for flight level 100, Airbus 320, information E Rovaniemen torni, Golden 332, läpäisen lentopinnan 202 lentopinnalle 100, Airbus 320, tiedotus E |
| 🎧 | Golden 332, Rovaniemi tower, radar contact. Continue descent to 2500 feet, qnh 1011, cleared RNP approach runway 03, right circuit, number 1 in traffic. Report on final approach course Golden 332, Rovaniemen torni, tutka yhteys, jatka laskeutumista 2500 jalkaan, qnh 1011, selvä RNP lähestymiseen kiitotie 03, oikea kierros, vuoro yksi, ilmoita loppulähestymissuunnassa |
| 👨✈️ | Descend 2500 feet, qnh 1011, cleared RNP approach runway 03, right circuit, wilco, Golden 332 Jatkan laskeutumista 2500 jalkan, qnh 1011, selvä RNP lähestymiseen kiitotie 03, oikea kierros, ilmoitan, Golden 332 |
Operations in Low Visibility Conditions
Runways 03 and 21 are approved for Low Visibility Procedures for Take-offs (LVPTO).
- LVPTO is used when the RVR value is 550 M or less.
Runway 21 is approved for ILS CAT II approaches. The approach procedure has the following minimas OCA (H):
- Category A: 688 (79)
- Category B: 699 (90)
- Category C: 712 (103)
- Category D: 727 (118)
There is also LPV approaches available for both runways (Lateral Precision with Vertical Guidance Approach). See the RNP approach charts for more information.
LVP initiation
Low Visibility Procedures for all air traffic will become effective when the RVR value decreases to 550 M.
Medical helicopter
Note! The base of medical helicopter is located at the airport. The call sign of the medical helicopter is “Finnhems”.
General information
| ICAO call sign | FIH51 |
| SSR code | 0004 |
| Agreed route | DCT, MAX 1500 FT |
| base flight rules | VFR (IFR visual take-off and landing approved) |
Medical helicopter pilot shall select transponder code 0004 prior to contacting Rovaniemi Tower.
FATO located within ATC service boundary. Take-off and landing clearance required.
Nearest hospitals
- EFLR - Lapin keskussairaala
- EFLR is inside IFR approach funnel
- Not operational UFN. Ambulance transport from FIH base to hospital
Tango 03 and Tango 21
T03/T21 is a defined area on taxiway T between taxiway P and main apron border (picture below).
- FinnHEMS will take-off and land from/to T03 or T21 according to wind direction
- FinnHEMS hangar is located at Apron next to Q
Departure from EFRO base
- Air taxi to T03 or T21
- Clear heliport PC take-off from T03 or T21
- Initial climb in runway direction H025 or H205
| 🎧 | FIH51, AIR TAXI TANGO 03, CLEARED DIRECT EN-ROUTE 15000 FEET OR BELOW, QNH 1013 FIH51, ILMARULLAA TANGO 03, SELVÄ SUORAAN REITILLE 1500 JALKAA TAI ALAPUOLELLA, QNH 1013 |
| 🎧 | FIH51, WIND VARIABLE 3 KNOTS, CLEARED FOR TAKE-OFF TANGO 03, CLEARED TO CROSS RUNWAY FIH51, TUULI VAHTELEE 3 SOLMUA, SELVÄ LENTOONLÄHTÖÖN TANGO 03, SOPII YLITTÄÄ KIITOTIE |
Arrival to EFRO base
- Final approach in runway direction H025 or H205
- Aimpoint T03 or T21 according to wind direction
- Clear heliport PC1 landing to T03 or T21
- Landing clearance includes permission to taxi via Q to base, pilot will report on ground
| 👨✈️ | TOWER, FIH51, SOUTH OF CONTROL ZONE, 1300 FEET, NON-URGENT FLIGHT BACK TO BASE, INFORMATION M, QNH 1012 TORNI, FIH51, LÄHIALUEEN ETELÄPUOLELLA, 1300 JALKAA, KIIREETÖN PALUULENTO KENTÄLLE, TIEDOTUS M, QNH 1012 |
| 🎧 | FIH51, CLEARED DIRECT TOWARDS OWN BASE, 1500 FEET OR BELOW FIH51, SELVÄ SUORAAN KOHTI TUKIKOHTAA, 1500 JALKAA TAI ALAPUOLELLA |
| 🎧 | FIH51, WIND VARIABLE 2 KNOTS, CLEARED TO LAND TANGO 03 FIH51, TUULI VAHTELEE 2 SOLMUA, SELVÄ LASKUUN TANGO 03 |
🔵 EFTP - Tampere-Pirkkala
Tampere-Pirkkala Airport is located in the town of Pirkkala, approximately 13 kilometers south-west of the city of Tampere. As the third busiest airport in Finland according to passenger count, it serves as a crucial transport hub, offering both domestic and international flights. Finnair, Air Baltic and Ryanair are the most active airlines in Pirkkala.
The airport is split into two terminals:
- Terminal 1 (domestic), and
- Terminal 2 (international).
Tampere-Pirkkala Airport sees a diverse array of aircraft, from small private planes to larger commercial jets. Notably, it is also the home base for the Finnish Air Force's Satakunta Air Command, making it a shared civil-military aerodrome.
| IATA | ICAO | Charts |
|---|---|---|
| TMP | EFTP | Finland AIP - EFTP |
ATC positions
Tampere-Pirkkala is a controlled airport with aerodrome control- and approach control service. This service can be combined (tower-radar), or separate. Pirkkala Ground and Arrival positions are opened only when necessary due high traffic levels.
| Logon code | Call sign | Frequency | Responsibilities |
|---|---|---|---|
| EFTP_GND | PIRKKALA GROUND | 124.275 | En-route clearance, ground movement |
| EFTP_TWR | PIRKKALA TOWER | 118.700 | Ground movement, Pirkkala Control Zone |
| EFTP_R_TWR | PIRKKALA TOWER | 118.700 | Ground movement, Pirkkala Control Zone and Terminal Area |
| EFTP_APP | PIRKKALA RADAR | 126.200 | Tampere Terminal Area |
| EFTP_R_APP | PIRKKALA ARRIVAL | 120.250 | Tampere Terminal Area - arrivals below 5000 FT |
Ground layout
- Main apron is located north of the runway next to taxiways H and G
- General aviation aircraft can park on the main apron General Aviation Parking Area, or on Apron 3, which is located next to taxiway P
- Medical helicopter base is located east of taxiway G
There is a military apron south of runway 06/24
Taxi routes for the aircraft with code letter E and F are presented in Finland AIP on the AGMC chart.
Runways
Tampere-Pirkkala is equipped with one runway 06/24. The preferred runway is considered to be runway 24 for departures and runway 06 for arrivals.
Civil aviation must use runway 06 as the primary landing runway at night 2000-0500 UTC (1900-0400 UTC) and runway 24 as the primary take-off runway, unless otherwise dictated by air traffic safety.
Currently available stands
Stand restrictions
- Stands A1-A4 are used for domestic flights (terminal 1)
- Stands B1-B5 may be used for international flights (terminal 2)
- Stand B1 is the only stand that can accomodate Code E or F aeroplanes:
When stand B1 is occupied by a Code E or F aeroplane, stands A5, B2 and B3 are also blocked. Additionaly taxiway S cannot be used by other traffic.
Code E and F aeroplanes
| Code | ICAO | Aircraft type | Wingspan M |
|---|---|---|---|
| 🔴 F | A388 | Airbus A380-800 | 79.8 |
| 🔴 F | A124 | Antonov AN-124-100 | 73.3 |
| 🔴 F | B748 | Boeing 747-8 | 68.5 |
| 🔴 F | C5M | Lockheed C-5 Super Galaxy | 67.9 |
| 🔵 E | B77W, B77L | Boeing 777-300ER, -200LR, -F | 64.8 |
| 🔵 E | A359, A35K | Airbus A350-900, A350-1000 | 64.75 |
| 🔵 E | B744 | Boeing 747-400 | 64.44 |
| 🔵 E | A345, A346 | Airbus A340-500, -600 | 63.45 |
| 🔵 E | B772, B773 | Boeing 777-300, -200 | 60.93 |
| 🔵 E | A332, A333, A342, A343 | Airbus A330-200, -300, Airbus A340-200, -300 | 60.3 |
| 🔵 E | B788, B789, B78X | Boeing Dreamliner 787-8, 787-9, 787-10 | 60.12 |
| 🔵 E | IL96 | Iljushin IL-96 | 60.11 |
| 🔵 E | B742, B743 | Boeing 747-200, -300 | 59.6 |
En-route clearance
Please, do not include the SID in your flight plan route.
By default the local tower controller will give clearance to requested cruise flight level.
Departure with SID:
| 🎧 | Fastair 312, cleared to Turku, runway 24, Nebab 3E departure, flight level 100, squawk 5542 Fastair 312, selvä Turkuun, kiitotie 24, Nebab 3E lähtöreitti, lentopinta 100, koodaa 5542 |
Departure with direct route:
| 🎧 | Fastair 312, cleared to Turku, runway 24, direct Nebab, flight level 100, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 21, lähdöstä suoraan Nebab, lentopinta 100, koodaa 5542 |
Approach
Please, do not include the STAR in your flight plan route.
Runway 24 is the only runway with an ILS approach system. This makes runway 24 the preferred runway during Low Visibility Operations.
- ILS Z approach is used for RNAV capable aircraft
- ILS Y approach is used for non-RNAV aircraft (based on VOR navigation)
When approaching runway 06, pilots may expect to be cleared for RNP approach.
Arriving aircraft may be cleared for the approach already on initial contact with the local controller. Please be ready to copy any clearance and instructions.
Phraseology example:
- On initial contact with approach control, please include the following:
- Call sign
- Current flight level
- Assigned flight level
- Aircraft type (and wake turbulence category if necessary)
- Received ATIS broadcast
- Other restrictions given by previous controller
| 👨✈️ | Pirkkala tower, Golden 332, passing flight level 204 for flight level 100, Airbus 320, information F Pirkkalan torni, Golden 332, läpäisen lentopinnan 204 lentopinnalle 100, Airbus 320, tiedotus F |
| 🎧 | Golden 332, Pirkkala tower, radar contact. Continue descent to 2700 feet, qnh 1011, cleared ILS-Z approach runway 24, left circuit, number 1 in traffic. For information, next 20 miles below flight level 95 uncontrolled airspace. Golden 332, Pirkkalan torni, tutka yhteys, jatka laskeutumista 2700 jalkaan, qnh 1011, selvä ILS-Z lähestymiseen kiitotie 24, vasen kierros, vuoro yksi, tiedoksi seuraavat 20 mailia alle lentopinnan 95 valvomatonta ilmatilaa. |
| 👨✈️ | Descend 2700 feet, qnh 1011, cleared ILS-Z approach runway 24, left circuit, roger, Golden 332 Jatkan laskeutumista 2700 jalkan, qnh 1011, selvä ILS-Z lähestymiseen kiitotie 24, vasen kierros, selvä, Golden 332 |
Operations in Low Visibility Conditions
Runways 06 and 24 are approved for Low Visibility Procedures for Take-offs (LVPTO).
- LVPTO will be taken to effect when the RVR value is 550 M or less.
- Pilots will be informed by ATIS or ATC: "LOW VISIBILITY TAKE OFF PROCEDURES IN OPERATION"
- Only one aircraft is allowed on the manoeuvring area when LVPTO is in effect
Low Visibility Procedures for Take-off are not allowed below RVR 300 meters due to the absence of RCLL.
Tampere-Pirkkala airport is only equipped with ILS CAT I approach for runway 24. The approach minimas are OCA (H):
- Category A: 524 (157)
- Category B: 534 (167)
- Category C: 546 (179)
- Category D: 559 (192)
There is also LPV approaches available for both runways (Lateral Precision with Vertical Guidance Approach). See the RNP approach charts for more information.
VFR local procedures
Preferred VFR cicuit south of aerodrome:
When cleared to leave or enter the Control Zone via PUPPA Visual Reporting Point, pilots shall follow the published VFR route within the Control Zone:
Medical helicopter
Note! The base of medical helicopter is located at the airport. The call sign of the medical helicopter is “Finnhems”.
General information
| ICAO call sign | FIH30 |
| SSR code | 0003 |
| Agreed route | DCT, MAX 1500 FT |
| base flight rules | VFR only |
FinnHEMS hanagr and three FATO areas are located outside of ATC service boundary.
Nearest hospitals
- EFPT - Tampereen Yliopistollinen keskussairaala (“TAYS”)
- Note! EFPT is inside IFR approach funnel
Departure from EFTP base
- Pilot will select one of the 3 FATO areas according to wind direction
- VTOL PC1 take-off from FATO
- Initial climb according to FATO (picture below)
Arrival to EFTP base
- Final approach according to FATO (see picture above)
- Note! Headings are radials from FATO
- Aimpoint FIH FATO 1, 2 or 3
- VTOL PC1 landing
🔵 EFTU - Turku
Turku Airport is the fourth busiest airport in Finland according to passenger numbers, located approximately 8 kilometers north of Turku city center. The airport is an integral part of the Scandinavian and Baltic aviation network and serves as an important hub for both commercial and private flights. Turku airport is highly accessible and strategically positioned.
One should note that Turku Airport is open 24 hours a day and offers ATC services during its operational hours. It is surrounded by flat terrain, and pilots should be aware of the weather conditions, especially during the winter months when heavy snow can be expected.
| IATA | ICAO | Charts |
|---|---|---|
| TKU | EFTU | Finland AIP - EFTU |
ATC positions
Turku is a controlled airport with aerodrome control- and approach control service. This service can be combined (tower-radar), or separate.
| Logon code | Call sign | Frequency | Responsibilities |
|---|---|---|---|
| EFTU_TWR | TURKU TOWER | 118.300 | Ground movement, Turku Control Zone |
| EFTU_R_TWR | TURKU TOWER | 118.300 | Ground movement, Turku Control Zone & Terminal Area |
| EFTU_APP | TURKU RADAR | 120.475 | Turku Terminal Area |
Ground layout
- The main apron serving passenger airlines is located next to the Control Tower
- Cargo flights are usually parked on the cargo apron next to taxiway D
- General aviation aircraft are parked on the Apron next to taxiway Y or B
- Medical helicopter base is located next to taxiway B south of the main taxiway
Frontier Guard apron is located next to taxiway A. There is also one hangar for Air Force QRA missions.
Runways
Turku is equipped with one runway 08/26. The preferred runway is considered to be runway 08.
Currently available stands
Stand restrictions
- Stands 5B and 8 can accomodate Code E and F aeroplanes (see table below)
- Stands 4, 5, 6 and 7 can accomodate Jet aircraft up to A321 / B739
- Cargo aircraft are parked on stands 9, 10, 12 and 12
When stand 5B is occupied, stands 5, 6 and 7 shall not be in use. Stand 5B is only used for Code E or F aeroplanes.
| Code | ICAO | Aircraft type | Wingspan M |
|---|---|---|---|
| 🔴 F | A388 | Airbus A380-800 | 79.8 |
| 🔴 F | A124 | Antonov AN-124-100 | 73.3 |
| 🔴 F | B748 | Boeing 747-8 | 68.5 |
| 🔴 F | C5M | Lockheed C-5 Super Galaxy | 67.9 |
| 🔵 E | B77W, B77L | Boeing 777-300ER, -200LR, -F | 64.8 |
| 🔵 E | A359, A35K | Airbus A350-900, A350-1000 | 64.75 |
| 🔵 E | B744 | Boeing 747-400 | 64.44 |
| 🔵 E | A345, A346 | Airbus A340-500, -600 | 63.45 |
| 🔵 E | B772, B773 | Boeing 777-300, -200 | 60.93 |
| 🔵 E | A332, A333, A342, A343 | Airbus A330-200, -300, Airbus A340-200, -300 | 60.3 |
| 🔵 E | B788, B789, B78X | Boeing Dreamliner 787-8, 787-9, 787-10 | 60.12 |
| 🔵 E | IL96 | Iljushin IL-96 | 60.11 |
| 🔵 E | B742, B743 | Boeing 747-200, -300 | 59.6 |
En-route clearance
Please, do not include the SID in your flight plan route.
By default the local tower controller will give clearance to requested cruise flight level.
Departure with SID:
| 🎧 | Fastair 312, cleared to Helsinki, runway 08, Ipmot 3B departure, flight level 140, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 08, Ipmot 3B lähtöreitti, lentopinta 140, koodaa 5542 |
Departure with direct route:
| 🎧 | Fastair 312, cleared to Helsinki, runway 12, direct Ipmot, flight level 100, expect radar climb, squawk 5542 Fastair 312, selvä Helsinkiin, kiitotie 12, lähdöstä suoraan Ipmot, lentopinta 100, odota tutka nousua, koodaa 5542 |
Approach
Please, do not include the STAR in your flight plan route.
Runway 26 is the only runway with an ILS approach system. This makes runway 26 the preferred runway during Low Visibility Operations.
- ILS approach is used for RNAV capable aircraft
- Visual approaches are used for Non-RNAV capable aircraft
When approaching runway 08, pilots may expect to be cleared for RNP approach.
Arriving aircraft may be cleared for the approach already on initial contact with the local controller. Please be ready to copy any clearance and instructions.
Phraseology example:
- On initial contact with approach control, please include the following:
- Call sign
- Current flight level
- Assigned flight level
- Aircraft type (and wake turbulence category if necessary)
- Received ATIS broadcast
- Other restrictions given by previous controller
| 👨✈️ | Turku tower, Quality 4KU, flight level 100, Boeing 738, information B Turun torni, Quality 4KU, lentopinnalla 100, Boeing 738, tiedotus B |
| 🎧 | Quality 4KU, Turku tower, radar contact, continue descent to 2200 feet, QNH 1010, cleared ILS Z approach runway 26, report established on localizer, for information next 15 miles below flight level 95 uncontrolled airspace Quality 4KU, Turun torni, tutkayhteys, jatka laskeutumista 2200 jalkaan, QNH 1010, selvä ILS Z lähestymiseen kiitotie 26, ilmoita suuntasäteellä, tiedoksi seuraavat 15 mailia alle lentopinnan 95 valvomatonta ilmatilaa |
| 👨✈️ | Continue descent to 2200 feet, QNH 1010, cleared ILS Z approach runway 26, wilco, Quality 4KU Jatkan laskeutumista 2200 jalkaan, QNH 1010, selvä ILS Z lähestymiseen kiitotie 26, ilmoitan, Quality 4KU |
Operations in Low Visibility Conditions
Runways 08 and 26 are approved for Low Visibility Procedures for Take-offs (LVPTO).
- Procedures will be in force when the RVR value is 550 M or less.
- Pilots will be informed by ATIS or ATC: "LOW VISIBILITY TAKE OFF PROCEDURES IN OPERATION"
- Only one aircraft is allowed on the manoeuvring area when LVPTO is in effect
Low Visibility Procedures for Take-off are not allowed below RVR 300 meters due to the absence of RCLL.
Turku airport is only equipped with ILS CAT I approach for runway 26. The approach minimas are OCA (H):
- Category A: 300 (159)
- Category B: 310 (169)
- Category C: 322 (181)
- Category D: 335 (194)
There is also LPV approaches available for both runways (Lateral Precision with Vertical Guidance Approach). See the RNP approach charts for more information.
Medical helicopter
Note! The base of medical helicopter is located at the airport. The call sign of the medical helicopter is “Finnhems”.
General information
| ICAO call sign | FIH20 |
| SSR code | 0002 |
| Agreed route | DCT, MAX 1200 FT |
| base flight rules | VFR only |
Medical helicopter pilot shall select transponder code 0002 prior to contacting Turku Tower.
Nearest hospitals
- EFTV - Turun yliopistollinen keskussairaala (TYKS)
Departure from EFTU base
- VTOL PC1 take-off from FATO (see Appendix 2)
- Initial climb in directions between H070 - H235 and H120 - H200 (red area):
ATC will give VFR clearance (normally direct en-route, 1200 feet or below) and ask pilot to report when airborne. No take-off clearance is given when departing directly from apron.
- Alternative: clear heliport PC1 take-off only between H355 and H055 from FATO (northbound, crossing runway)
Arrival to EFTU base
- Final approach in same directions as departure sectors (towards FATO between H055 - H250 and H020 - H300)
- Aimpoint FIH FATO
- VTOL PC1 landing
ATC will normally give a clearance for approach to own base and ask the pilot to report on ground. No landing clearance is given when arriving directly to apron.
When Quick Reaction Alert (QRA) is in force
- ATCO may give clearance “ONE MIKE”
- VTOL PC1 Take-off and landing only in directions between H140 - H180 and H320 - H005 from FATO (only northbound or southbound departure and landing)
- If procedure is not possible due to wind direction, take-off and landing shall be conducted to runway 08 or 26
| 🎧 | FIH20, SELVÄ 1-MIKE MENETELMÄN MUKAAN, QNH 1013, TUULI TYYNTÄ, ILMOITA ILMASSA, SAA YLITTÄÄ KIITOTIE FIH20, CLEARED 1-MIKE PROCEDURE, QNH 1013, WIND CALM, REPORT AIRBORNE, CLEARED TO CROSS RUNWAY |
Frontier Guard flights
General information
Two Frontier Guard aircraft have their base at Turku airport. These aircraft are parked on the Frontier Guard apron south of runway 26 threshold.
| ICAO call sign | Radio call sign | Aircraft type | SSR code |
|---|---|---|---|
| FNG 8 | FINNGUARD 8 | Dornier 228 (D228) | 0010 |
| FNG 100 | FINNGUARD 100 | AS-332 Super Puma (AS32) helicopter | 0011 |
Frontier Guard pilots shall select the predetermined transponder code according to the table above prior contacting Turku Tower.
Flight planning
Frontier Guard flights are usually operated under VFR rules when weather allows. Departure and arrival can be peformed directly from/to apron, or on the active runway, whichever is preferred.
Maritime patrol flights shall include OPR/FNG RMK/MARITIME PATROL in the flight plan.
- The above information denotes a flight by the Guard Squadron near the maritime borders of Finland.
- The route section can include lighthouses or islands to better represent the route of the flight
- In IMC conditions, the route usually consists of RNAV waypoints or coordinates to represent the planned route as close as possible
🟠 Aerodromes with AFIS
Aerodromes with AFIS service in Finland are:
- EFET - Enontekiö
- EFKI - Kajaani
- EFMI - Mikkeli
- EFSA - Savonlinna
- EFSI - Seinäjoki
At Ivalo (EFIV), Kuusamo (EFKS) and Kittilä (EFKT) the controller may choose to provide AFIS instead of aerodrome control service.
When AFIS is provided, the controller is connected with EFXX_I_TWR logon code.
Pilots shall be in contact with AFIS Officers (AFISO) when operating on the maneouvering area or when flying within the FIZ Upper and FIZ Lower airspaces.
What is AFIS?
AFIS is the term used to describe the provision of information useful for the safe and efficient conduct of aerodrome traffic at those aerodromes where the provision of aerodrome control service is not justified or is not justified on a 24-hour basis.
AFIS is not an air traffic control unit! An AFIS unit will provide flight information service and alerting service to aerodrome traffic.
AFIS Officers (AFISO) will relay IFR en-route clearances from Area Control, pass information and warnings to pilots. Pilots are therefore wholly responsible for maintaining proper spacing in conformity with the rules of the air.
- This means that pilots shall report their intentions to AFIS instead of receiving clearances
Phraseology examples
Start-up procedures
AFIS in Finland will control start-up.
| 👨✈️ | SAVONLINNA INFORMATION, GAO 332, REQUEST START-UP, INFORMATION CHARLIE SAVONLINNAN TIEDOTUS, GAO 332, PYYDÄN KÄYNNISTÄÄ, TIEDOTUS CHARLIE |
| 🎧 | GAO 332, SAVONLINNA INFORMATION, (ATC ADVICES) START-UP APPROVED GAO 332, SAVONLINNAN TIEDOTUS, SAAT KÄYNNISTÄÄ |
| 👨✈️ | GAO 332, REQUEST PUSHBACK GAO 332, PYYDÄN TYÖNTÖÄ |
| 🎧 | GAO 332, PUSHBACK AT OWN DISCRETION GAO 332, TYÖNNÄ HARKINTASI MUKAAN |
IFR en-route clearance
| 🎧 | GAO 332, HELSINKI CONTROL CLEARS TO HELSINKI, FLIGHT PLAN ROUTE, FLIGHT LEVEL 220, SQUAWK 3466 GAO 332, HELSINGIN ALUE SELVITTÄÄ HELSINKIIN, LENTOSUUNNITELMAN MUKAINEN REITTI, LENTOPINTA 220, KOODAA 3466 |
| 👨✈️ | CLEARED TO HELSINKI, FLIGHT PLAN ROUTE, FLIGHT LEVEL 220, SQUAWK 3466, GAO 332 SELVÄ HELSINKIIN, LENTOSUUNNITELMAN MUKAINEN REITTI, LENTOPINTA 220, KOODAAN 3466, GAO 332 |
| 🎧 | GAO 332, (THAT IS) CORRECT GAO 332, OIKEIN |
Taxi
| 👨✈️ | GAO 332, READY TO TAXI, STAND 2 GAO 332, VALMIINA RULLAAMAAN, PAIKKA 2 |
| 🎧 | GAO 332, NO REPORTED TRAFFIC GAO 332, EI TIEDOSSA OLEVAA LIIKENNETTÄ |
| 👨✈️ | TAXIING TO HOLDING POINT ALPHA RUNWAY 12, GAO 332 RULLAAN ODOTUKSEEN ALPHA KIITOTIE 12, GAO 332 |
Take-off
| 🎧 | GAO 332, REPORT READY GAO 332, ILMOITA KUN VALMIS |
| 👨✈️ | GAO 332, READY FOR DEPARTURE GAO 332, VALMIINA LÄHTÖÖN |
| 🎧 | GAO 332, WIND CALM, NO REPORTED TRAFFIC RUNWAY 12 GAO 332, TUULI TYYNTÄ, EI TIEDOSSA OLEVAA LIIKENNETTÄ KIITOTIE 12 |
| 👨✈️ | GAO 332, TAKING OFF RUNWAY 12 GAO 332, SUORITAN LENTOONLÄHDÖN KIITOTIE 12 |
| 🎧 | SAVONLINNA SAVONLINNA |
If runway is occupied:
| 🎧 | GAO 332, RUNWAY 12 OCCUPIED BY AIRCRAFT FINNAIR ATR 72 (REPORT INTENTIONS) GAO 332, KIITOTIE VARATTU, FINNAIR ATR 72 (ILMOITA AIKEESI) |
| 👨✈️ | GAO 332, HOLDING SHORT RUNWAY 12 GAO 332, PYSYN SELVÄSTI EROSSA KIITOTIE 12 |
Climb
Normally the handoff from AFIS to Area Control occurs 3 minutes after departure, or prior to passing FL 95.
| 🎧 | GAO 332, NEXT FREQUENCY IS 132.325, YOU MAY LEAVE THIS FREQUENCY GAO 332, SEURAAVA TAAJUUS ON 132.325, VOIT JÄTTÄÄ TÄMÄN TAAJUUDEN |
| 👨✈️ | 132.325, GAO 332 |
Approach
| 👨✈️ | SAVONLINNA INFORMATION, GAO 332, PASSING FLIGHT LEVEL 170, DESCENDING TO FLIGHT LEVEL 100, INFORMATION CHARLIE SAVONLINNAN TIEDOTUS, GAO 332, LÄPI LENTOPINTA 170, LASKEUDUN PINNALLE 100, TIEDOTUS CHARLIE |
| 🎧 | GAO 332, SAVONLINNA INFORMATION, NO REPORTED TRAFFIC, PREFERRED RUNWAY 12, INFORMATION DELTA, QNH 1010, RUNWAY 12 SURFACE CONDITION CODE 4, DRY SNOW, 1 MILLIMETER GAO 332, SAVONLINNAN TIEDOTUS, EI TIEDOSSA OLEVAA LIIKENNETTÄ, SUOSITELTAVA KIITOTIE 12, TIEDOTUS DELTA, QNH 1010, KIITOTIE 12 KIITOTIEOLOSUHTEET KOODI 4, KUIVAA LUNTA, 1 MILLIMETRI |
| 👨✈️ | INFORMATION DELTA, ABMAX 3A ARRIVAL, DESCENDING TO 2400 FEET, QNH 1010, EXPECTING ILS-Z APPROAH RUNWAY 12, GAO 332 TIEDOTUS DELTA, ABMAX 3A TULOREITTI, JATKAN LASKEUTUMISTA 2400 JALKAAN, QNH 1010, ODOTAN ILS-Z LÄHESTYMISTÄ KIITOTIE 12 GAO 332 |
| 🎧 | GAO 332, REPORT ESTABLISHED ON LOCALIZER GAO 332, ILMOITA SUUNTASÄTEESSÄ |
| 👨✈️ | WILCO, GAO 332 ILMOITAN, GAO 332 |
| 👨✈️ | GAO 332, ESTABLISHED ON (ILS) LOCALIZER RUNWAY 12 GAO 332, (ILS) SUUNTASÄTEESSÄ KIITOTIE 12 |
Landing
| 🎧 | GAO 332, NO REPORTED TRAFFIC RUNWAY 12, WIND 140 DEGREES 7 KNOTS, VARIABLE BETWEEN 100 AND 170 DEGREES, MINIMUM 3 KNOTS, MAXIMUM 17 KNOTS GAO 332, EI TIEDOSSA OLEVAA LIIKENNETTÄ KIITOTIE 12, TUULI 140 ASTETTA 7 SOLMUA, VAIHTELEE VÄLILLÄ 100 JA 170 ASTETTA, MINIMI 3 SOLMUA, MAKSIMI 17 SOLMUA |
| 👨✈️ | GAO 332, LANDING RUNWAY 12 GAO 332, SUORITAN LASKUN KIITOTIELLE 12 |
| 🎧 | SAVONLINNA SAVONLINNA |
If runway is occupied:
| 🎧 | O-ME, RUNWAY 30 OCCUPIED O-ME, KIITOTIE 30 KÄYTÖSSÄ |
| 👨✈️ | O-ME, WILL MAKE THREE-SIXTY RIGHT O-ME, TEEN KOLMEKUUSIKYMMENTÄ OIKEALLE |
VFR flight
| 👨✈️ | SAVONLINNA INFORMATION, OH-CME, CESSNA 172, 15 MILES NORTH OF AIRFIELD, 1800 FEET, INFORMATION CHARLIE, FOR LANDING SAVONLINNAN TIEDOTUS, OH-CME, CESSNA 172, 15 MAILIA KENTÄSTÄ POHJOISEEN, 1800 JALKAA, TIEDOTUS CHARLIE, LASKUA VARTEN |
| 🎧 | O-ME, SAVONLINNA INFORMATION, RIGHT CIRCUIT RUNWAY 30, QNH 1010, TRAFFIC FINNAIR ATR 72 ON 7 MILES FINAL RUNWAY 30 O-ME, SAVONLINNAN TIEDOTUS, OIKEA KIERROS KÄYTÖSSÄ KIITOTIE 30, QNH 1010, LIIKENNE FINNAIR ATR 72 7 MAILIN LOPPUOSALLA KIITOTIE 30 |
| 👨✈️ | O-ME, VIA HANHI JOINING RIGHT DOWNWIND RUNWAY 30, 1100 FEET, QNH 1010 O-ME, HANHEN KAUTTA LIITYTÄÄN OIKEAAN MYÖTÄTUULEEN KIITOTIE 30, 1100 JALKAA, QNH 1010 |
| 🎧 | SAVONLINNA SAVONLINNA |
| 👨✈️ | O-ME, HANHI INBOUND, FINNAIR ATR 72 IN SIGHT, JOINING FINAL RUNWAY 30 AS NUMBER 2 O-ME, HANHI SISÄÄN, FINNAIR ATR 72 NÄKYVISSÄ, LIITYTÄÄN LOPPUOSALLE KIITOTIE 30 VUOROLLA 2 |
| 🎧 | O-ME, REPORT FINAL O-ME, ILMOITA LOPPUOSA |
| 👨✈️ | WILCO, O-ME ILMOITAN, O-ME |
| 👨✈️ | O-ME, FINAL RUNWAY 30 O-ME, LOPPUOSA KIITOTIE 30 |
| 🎧 | O-ME, WIND CALM, NO REPORTED TRAFFIC RUNWAY 30 O-ME, TUULI TYYNTÄ, EI TIEDOSSA OLEVAA LIIKENNETTÄ KIITOTIE 30 |
| 👨✈️ | O-ME, WILL LAND RUNWAY 30 O-ME, SUORITAN LASKUN KIITOTIELLE 30 |
🔴 V-LARA Airspace Reservation
V-LARA site is not yet released for public use.
Record of Amendments
| Version | Issue Date | Reason for Change |
|---|---|---|
| 0.1 d1 | 28 DEC 2024 | Initial draft |
V-LARA Booking Client - Pilot Guide
| Link to LARA Web Booking Client |
|---|
| coming soon... |
1. INTRODUCTION
The V-LARA Web Booking Client can be used to make airspace reservations in Finland on VATSIM network. Pilots or organizations can view all upcoming airspace reservations in Finland and add their own reservations.
It is currently possible to make reservations for all TSA, TRA and Local TRA areas in Finland either for Civil or Military operations. Pilots and organizations are kindly requested to familiarize themselves with the procedures for operations in Reserved Areas (including flight planning and phraseology).
Check the Basic Use Case and Useful Links & Phraseology at the end of this page!
2. LOGIN PAGE
When the page loads, you will be automatically shown the login page. The V-LARA application uses VATSIM OAuth2 login for authenticating users. The PilotView will be opened automatically after successful authentication.
2.1 LOGIN ERRORS
If the login process fails, the error message will be displayed below the login button.
-
Login Failed. If problems presist, please contact your system administrator.
3. MAIN PAGE
The main page is broken up into three main sections: the Reservations Display, the Actions Display, and the Map Display.
-
Notification Icon- (currently only in use for AMC/ATC) -
Status Icon- displays the connectivity between the Web Client and the server -
Help Button- links to this user guide -
Logout Button- log the currently logged in user out of V-LARA
4. RESERVATION DISPLAY
The reservations are displayed in a simple table to the top left of the screen showing all airspace reservations in Finland. The table is automatically updated without the need for any page refreshes.
The background of the status field is automatically changed to match the reservation’s current status:
- Status RESERVED
- Status PENDING
- Status ACTIVE
- Status CANCELLED
4.1 GANTT CHART
To open the Gantt Chart, click on the "Chart" title text on the top of the page.
The Gantt Chart is used for the visualisation of reservations in the LARA Web Client. Areas are represented by rows in the chart and reservations are placed on the chart as rectangular slots at the times they are for.
The time range visible in the chart is displayed on the timescale at the top of the chart.
5. ACTIONS DISPLAY
The actions table displays all actions relevant to the user logged in and is updated
automatically without the need for a page refresh. To perform an action, click on the row in the table to open the Reservation Editor and then click on the button for that action at the bottom of the editor.
Pilots and organizations will only see their own reservations listed in the Actions Display. Pilots can edit their reservations up to 30 minutes prior start-time. After that the reservation will go to "Pending" state and only AMC/ATC can make modifications to the reservation.
The background of each row is automatically changed to match the reservation’s current status:
- Status RESERVED (reservation can be edited by pilot)
- Status PENDING (from here on reservation can only be edited by AMC/ATC)
- Status ACTIVE
- Status CANCELLED
6. MAP DISPLAY
The map displays boundaries for all reservable airspace blocks in Finland. Additionally the map displays the airspace reservations with the following color coding:
- Status RESERVED (blue outline)
- Status PENDING (orange outline)
- Status ACTIVE (red fill)
- Cancelled reservations are not shown on the map
The map works like any other browser-based map which can be navigated by clicking and dragging the map, and zooming in and out by double-clicking or using the mouse-wheel.
7. RESERVATION EDITOR
The Reservation Editor is a form which allows users to view, create, edit reservations as well as perform actions such as approving and cancelling reservations.
To open the Reservation Editor, click on a table row in Actions Display, or click on the Add reservation -button in the top-menu to start creating a new reservation.
Create only a reservation if intending to use the airspace. The reservations will be visible to ATC in real time.
Pilots can edit their reservations up to 30 minutes prior reservation start time.
7.1 BASIC SECTION
The basic section of the reservation editor contains fields for displaying and setting the creator, point of contact, and callsigns associated with the reservation editor.
The user creating the reservation is always in charge of the reservation and will be the Point of Contact for AMC/ATC if coordination or changes to the reservation needs to be made.
The callsign editor is a special form field with aids to help create and remove callsigns. To add a callsign, type the callsign and either click somewhere outside of the callsign field, if finished editing, or type a comma (,) to add a callsign and continue editing.
To remove a callsign, click on the x next to the callsign to remove.
7.2 ACTIVITY SECTION
The activity section allows for the configuration of booking type, responsible agency, permeability/segregation, activity type, priority, and number of aircraft. All form fields work as with forms outside of V-LARA. To quickly set the priority or number of aircraft, the value can also be typed into the field.
7.3 TIME SECTION
The time section of the form allows for the configuration of the start and end times of a reservation. To edit these fields, click the button next to the field and use the calendar or time pickers to choose the time. It is also possible to type the desired values directly into the text boxes, but they must use the same format as use to display the value.
The time values are in UTC timezone.
The following rules are checked automatically when validating the Start- and End Time by the system:
- No overlapping reservation times using the same airspace blocks
- Start time must be at least 30 minutes from now
- Minimum reservation endurance is 30 minutes
- Maximum reservation endurance is 8 hours
- Reservation cannot be made more than 7 days in advance
7.4 AIRSPACE SECTION
The airspace section allows for the configuration of the areas in a reservation. To configure an area, select the name from the dropdown and configure the level values. The level value fields can also be typed directly in the field.
Always Flight Levels when adding a Lower or Upper value. Use 0 in the Lower-field to indicate SFC (surface). Use 999 in the Upper-field to indicate UNL (unlimited).
To add another area to the reservation, click the plus (+) button to add a new row and configure the same fields. To remove an added row, click the red button alongside the row.
Pilots shall check the area specifications from Finland AIP prior reservation. There might be listed important Remarks or Flight Level limitations. AMC/ATC has the possibility to modify the reservation if required (e.g. due other traffic).
- ENR 5.2 MILITARY EXERCISE AND TRAINING AREAS
- ENR 6 ENROUTE AND INDEX CHARTS
- LOCAL TRA CHARTS
-
AIRSPACE MANAGEMENT (ASM) OPERATIONS MANUAL
- Includes a map of Defence Forces priority areas and TRAs over international waters.
7.5 REMARKS SECTION
The remarks section contains the remarks for a reservation. To add a remark, type into the
Add remark field. When submitting the reservation, the remark will be added to the reservation.
7.6 ACTION BUTTONS
Depending on the user role and the status of the reservation, different Action Buttons may be shown.
- EDIT RESERVATION - this button will confirm the changes and publish the edited reservation
- CANCEL RESERVATION - this button will prompt the user to give a
Cancellation Reason. The reason must be at least 3 characters long. After giving the reason, user can confirm the cancellation. - CLOSE - this button will close the
Reservation Editor. Changes will not be saved.
Basic Use Case
Review the Procedures
Familiarize yourself with the Local TRA, TRA and TSA areas and the flight procedures related to training area flights in Finland.
Add your reservation to V-LARA
Once you have chosen your training area including the upper and lower limits, go ahead and make a new reservation in V-LARA at least 30 minutes before your flight. Double check the content before submitting the reservation.
Make a Flight Plan
Generate a Flight Plan with the correct information in order for ATC to know what you are going to do. For local TRA flights, use the XXTA code in the route section (replace XX with the last two characters of the airport ICAO code). For TSA flights, please check Military Procedures (links are listed below)
Editing and Cancelling Reservations
Pilots can edit their reservation until 30 minutes before the reservation starts. After that, only ATC is able to make changes to your reservation.
Please cancel the reservation if you are not intending to use the airspace. ATC will normally cancel your reservation once the activity in your reserved area has ended.
Useful Links & Phraseology
A. LOCAL TRA AND TRA FLIGHTS
Flight Plan content
- The general IFR training area code XXTA is inserted to the Route for Local Training area flights
- for example
JYTA(the code for Jyväskylä training area)
- for example
- You may insert your Training Area request to the RMK field
- for example
RMK/TRAJY04
- for example
See Local TRA areas for each Aerodrome: https://www.ais.fi/localtra/localtra.htm
Phraseology
🎧 ATC phrases:
| O-BC, cleared training area 72 and 73, upper limit 8000 feet O-BC, selvä harjoitusalue 72 ja 73, yläraja 8000 jalkaa |
|
| O-BC, maintain 3000 feet or below until training area O-BC, säilytä 3000 jalkaa tai alapuolella kunnes harjoitusalueella |
Example of clearance to TRA area:
| 👨✈️ | Tower, T21, apron M request taxi and clearance to Training Area, information Mike Torni, T21, asematasolla M, pyydän rullata ja selvitystä harjoitusalueelle, tiedotus Mike |
| 🎧 | T21, tower, cleared to training area G11, maintain 5000 feet or below until training area T21, torni, selvä harjoitusalueelle G11, säilytä 5000 jalkaa tai alapuolella kunnes harjoitusalueella |
| 👨✈️ | Cleared to training area G11, maintain 5000 feet or below until training area, T21 Selvä harjoitusalueelle G11, säilytän 5000 jalkaa tai alapuolella kunnes harjoitusalueella, T21 |
| 🎧 | T21, wind 300 degrees, 4 knots, runway 24 cleared for takeoff, right turn T21, tuuli 300 astetta, 4 solmua, kiitotie 24 selvä lentoonlähtöön, oikea kaarto |
| 👨✈️ | Cleared for takeoff, right turn, T21 Selvä lentoonlähtöön, oikea kaarto, T21 |
B. MILITARY FLIGHTS TO TSA AREAS
Flight Plan content
- Use tactical points instead of the area name in the Flight Plan route
- for example
C/H13C/N0440F230F250(area TSAH51, point is located in the center of the TSA area, requested flight level block 230-250)
- for example
Tactical points are not defined in the charts. The points are based on coordinates located on the resective TSA area.
- W = WEST
- N = NORTH
- S = SOUTH
- E = EAST
- C = CENTER
When choosing your TSA area, pilots are requested to use the Defense Force primary TSA areas. More information here:
- ASM Operations Manual version 2.3 (map on page 16)
- Principles governing the use of airspace by the Finnish defence forces
Area groups SAVU, RUKA, MERI, KIURU, KOLI, KIUKO, POKA, HAKA, KAIRA, KURU and SAIMA are available in V-LARA! Please check the remarks and area limitations in the links above.
Area groups ITÄKAIRA, CENTRAL FINLAND, OSTROBOTHNIA and PIPO are not reservable in V-LARA.
- Block altitudes or flight levels are usually used in formation flights
- DO NOT include tactical or military Remarks in the ATC Flight Plan, as civil ATC is not responsible for military traffic within TSA areas. Aircraft registrations and other data not relevant for civil ATC may be omitted.
- Add only necessary information such as
RMK/TSAH13 OKorFOR/MASTER1+MASTER2for formation flights in the FPL remarks section.
- Add only necessary information such as
Phraseology
Military aircraft may start-up and taxi without taxi instructions on military aprons. Departing aircraft will receive the Runway Holding Point from ATC. Arriving aircraft will be instructed to "taxi to apron".
SSR codes are given to every aircraft in formation.
| 👨✈️ | Oulu tower, MASTER 1, two-ship, taxiing to holding point M, departure in standard formation, information A, QNH 1013 Oulun torni, MASTER 1, kahdella, rullaan odotukseen M, lähtö tiiviissä osastossa, tiedotus A, QNH 1013 |
| 🎧 | MASTER 1, Oulu tower, cross runway from M to B, taxi to holding point A runway 12, clearance available MASTER 1, Oulun torni, ylitä kiitotie M kautta, rullaa odotukseen A kiitotie 12, selvitys saatavilla |
| 👨✈️ | Cross runway from M to B, taxiing to holding point A, ready to copy, MASTER 1 Ylitän kiitotien M kautta ja rullaan odotukseen A, valmiina kopioimaan, MASTER1 |
| 🎧 | MASTER 1, cleared to point H51C, climb to block 11 thousand to 12 thousand feet, QNH 1013, squawk 3411 MASTER 1, selvä pisteelle H51C, nouse korkeusalueelle 11 tuhatta, 12 tuhatta jalkaa, QNH 1013, koodaa 3411 |
| 👨✈️ | Cleared to point H51C, climb to block 11 thousand to 12 thousand feet, QNH 1013, squawk 3411, MASTER 1 Selvä pisteelle H51C, nousen korkeusalueelle 11 tuhatta, 12 tuhatta jalkaa, QNH 1013, koodaan 3411, MASTER 1 |
| 🎧 | MASTER 2, squawk 3412 MASTER 2, koodaa 3412 |
| 👨✈️ | Squawk 3412, MASTER 2 Koodaan 3412, MASTER 2 |
| 🎧 | MASTER 1, clearance correct MASTER 1, selvitys oikein |
| 👨✈️ | MASTER 1 MASTER 1 |