🔵 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 VIA SID 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 OR use the De-icing Web Application (instructions at the end of this page). 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
- 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 send the Deice-request via 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.
- Pilots can also view the holdover times for the fluid types used at Helsinki (only if Precipitation exists)
