Pilot Briefing for Helsinki-Vantaa Real Flight Event

Transcription

1 Pilot Briefing for Helsinki-Vantaa Real Flight Event

2 INTRODUCTION It is finally time for the Helsinki Real Flight Event. This event will simulate the real operations and flights that go on every day at Helsinki-Vantaa International Airport. A lot of traffic is expected and participating pilots are therefore asked to be well prepared for this event. The purpose of this briefing is to do just that prepare all interested pilots for the busy airspace around Helsinki- Vantaa during the event. Before we dive into the specifics of the procedures at the airport, we will go through some practical information below. Please note that although this briefing attempts to be as thorough and relevant as possible, it does not include every detail about the airport and procedures. Furthermore, it assumes pilots are familiar with the normal procedures on IVAO. If anything is unclear, do not hesitate to ask. PRACTICAL INFORMATION Below you will find some practical information regarding the event; Charts: The frequencies will be busy and ATC will not have time to explain your taxirouting, missed approach procedure etc. to you because you don t have your charts with you. Do yourself, ATC and your fellow pilots a favour and bring charts. Real pilots always use charts why shouldn t you? Booking: Pilots are urged to book one (or more) of the available flights using the booking system. This is where the realism of the Real Flight Event comes in. Priority will be given to pilots who have booked a flight but we do accept also non-booked flights (see Non- Booked Flights below). Parking Positions: Please use the stand/gate which is indicated on your booking. Choosing a different stand/gate will cause confusion and will create a mess on the ground. Logging On/Off: Due to the amount of traffic expected we kindly ask pilots to log on no earlier than 15 minutes prior to their scheduled departure time. If arriving into Helsinki- Vantaa, please disconnect as soon as possible after reaching your designated stand/gate. Non-Booked Flights: Although booked flights will have priority, non-booked flights are also welcome. If you are departing Helsinki-Vantaa, please use any of the following gates: , cargo apron or GA apron. All other gates will have been assigned to booked flights.

3 GENERAL INFORMATION ICAO: EFHK IATA: HEL Runways:22R/04L, 22L/04R & 15/33 L A Y O U T As with any major international airport, Helsinki- Vantaa has a complex layout that may require some study before arriving/departing there. The airport has three runways as mentioned above. The airport utilises a preferential runway system. The exact details are quite complicated, however, a short explanation follows outlining the main points. Depending on weather and the traffic situation the following combination may be used: Southerly/Westerly Winds Northerly/Easterly Winds DEP 22R 04R ARR 22L/15 04L/R In general, runway 15 is not used for departures and runway 33 is not used for arrivals or departures. This is for noise purposes and the departures/arrivals would fly right over the city of Helsinki. However, during strong northerly or southerly winds 15/33 may be used. The actual runway combination is the responsibility of the Tower Controller. Note: Due to maintenance, RWY 04R/22L will be closed in real life. This will be simulated during the event. Layout Terminal 1. Domestic Flights + Schengen Region. Remote stands for turboprops Terminal 2. International flights within Schengen Region International Flights outside Schengen Region + Heavy Stands 4 Cargo Apron Remote stands 5 Schengen and Non Schengen 6 GA Terminal

4 IFR DEPARTURE AERODROME CONTROL When connecting to the network, please ensure you connect on the stand which is assigned to your booking. In your flight plan please use the route provided in your booking. If you decide to use a different routing, ensure that you plan to use one of the following TMA Exit points; ADIVO ARVEP DOBAN IDEPI KUVEM NEPEK NUNTO RENKU TEVRU As you may have noticed, none of these waypoints have SIDs associated with them. This is because each runway has a differently named SID to minimise the risk of pilots choosing the wrong one. Routing to your exit point will be included in your departure clearance. See example below. The first controller you will talk to is Helsinki Delivery ( ). Your initial call should be as follows; What to include Callsign Aircraft type ATIS received Example SAS123: Helsinki Delivery, Finnair 123, A321, Information G, request clearance to Oslo DEL: Finnair 123, RWY22R, VAGIP 1N, ADIVO, QNH 1009, squawk 2242 Note that the initial climb is not mentioned in the clearance, however, it can be found in the chart and is usually Note also that the clearance includes the instruction to fly direct ADIVO after completing the VAGIP1N departure. If you do not have charts with you or do not understand the clearance, this is the time to inform the controller! The controller will either explain the clearance to you or issue you with a new clearance. All SIDs are based on DME/DME or GNSS and therefore require RNAV capability. If you are unable RNAV, inform Helsinki Delivery on first contact who will issue you with an omni-directional departure. Contact Helsinki Ground ( ) for push and start when you are fully ready. Once push and start has been completed you may request taxi from the ground controller. The controller will then issue taxi instructions to the runway for departure or any intermediate point. For example; if RWY22R is in use for departures you can expect to be instructed to taxi to VG or ZG and hold short of RWY22L before being handed over to Helsinki Tower ( or ). Pay attention to the frequency; there may be two tower controllers online at any one time. Tower will then instruct you to cross a runway and give you further taxi instructions if required.

5 After take-off remain on the tower frequency until passing 1500 before switching to the frequency mentioned on the chart. Tower will not hand you over. If you are in doubt as to what departure frequency to use, ask the tower controller. DEPARTURE CONTROL Departure Control is in most cases provided by Helsinki Radar ( ). On initial contact with Helsinki Rada report your routing (SID or heading) and your passing altitude. Radar will give you further climb and directs or radar vectors to expedite traffic flow. IFR ARRIVAL All flights arriving Helsinki-Vantaa shall be planned via the following TMA entry points; INTOR LAKUT LUSEP ROPAM VEPIN DIVAM Before passing overhead these points, the en-route controller will give you your inbound clearance which will usually include the STAR to follow (or possibly a heading) and a cleared flight level. All STARs to Helsinki-Vantaa begin at one of the entry points and are based on DME/DME or GNSS and therefore require RNAV. If you are unable to follow an RNAV STAR please inform ATC as early as possible. The relevant ATC unit will then issue radar vectors to final approach. In all other cases, ATC will expect pilots to follow the arrival route to final approach. However, ATC may also elect to use radar vectors to final approach during busy periods or at any time ATC deems it necessary. Please note that the altitudes published on the STAR charts are minimum altitudes/levels only; actual descent will be by ATC. However, the speed restrictions on the charts must be followed unless otherwise instructed. Furthermore, pilots are required to maintain a maximum speed of 250kts within 30DME of HEL VOR/DME. APPROACH CONTROL Approach Control at Helsinki-Vantaa is provided by Helsinki Radar ( ). On initial contact with approach control, state the following:

6 Callsign, ATIS, Aircraft Type, Cleared Level, and Routing (STAR/heading) Example SAS123: Helsinki Radar, Finnair 123, information G, A321, descending FL100, LAKUT 2A Please make sure that you read the entire ATIS as it may contain important information with regards to your arrival into Helsinki-Vantaa. When you mention the ATIS letter, the air traffic controller will assume that you have all the information and act accordingly. As mentioned above, Helsinki Radar will either expect you to follow the STAR to final approach or issue radar vectors. ATC may also give you a direct routing to waypoints along the STAR. Furthermore, Helsinki Radar will attempt to issue descent clearance in accordance with a continuous descent profile. Pilots are requested to attempt to maintain a constant descent until established on the approach an estimated track mileage to touchdown may be requested from the controller to aid the pilot in descent planning. During busy periods Helsinki Arrival ( ) may be online. To avoid frequency congestion, please mention your callsign only on initial contact with Helsinki Arrival. It is his/her job to issue the last vectors to final approach. Radar vectors and speed control will be used to ensure a safe and efficient flow of traffic. Please ensure you maintain the speed you are assigned do not just reduce when you think it is necessary. Inform ATC if you are unable to maintain the assigned speed. Once established on the approach, maintain 150kts until 4DME unless otherwise instructed. For traffic sequencing it is vital to follow this instruction. If unable, inform ATC as soon as possible. AERODROME CONTROL Once established on final approach you will be handed over to the Helsinki Tower ( or ). On initial contact state callsign and the runway you are on approach to. For example; Helsinki Tower, Finnair 123, 22R When appropriate the controller will clear you to land. If he doesn t and instructs you to go around, carry out a missed approach and follow the procedure stated on the chart ATC will only say standard missed approach. The controller will expect you to follow the procedure on the chart. Failure to do so may cause conflictions with other traffic at the aerodrome. Following a successful landing, vacate the runway as soon as possible as aircraft may be on approach behind you. Once vacated contact Helsinki Ground unless you land on 04L/22R in which case you remain with tower.

7 NOTE: Do NOT vacate RWY 22L at ZG unless approved by tower because there may be outbound traffic waiting for crossing clearance! Helsinki Ground will give you taxi instructions to your assigned gate. When you have parked please disconnect as soon as possible to make room for the next aircraft requiring your gate. Also, please do NOT report on blocks. The controller can see you have parked and it is therefore not necessary to inform him that you have parked. VFR AT HELSINKI-VANTAA VFR flights are allowed at Helsinki-Vantaa, however, prior permission is required. During quiet periods this will most likely not be a problem. During busy periods like the Real Flight Event, however, tower may decide to refuse VFR flights due to the traffic load. The control zone at EFHK is of airspace classification C. VFR flights are required to use the CTR Entry/Exit points as show on the Visual Approach Chart. Please study this chart carefully before attempting a VFR flight in the Helsinki-Vantaa Control Zone. ATC will expect you to know the location of all the reporting points and the various holdings on the chart. Furthermore, please note that there is a noise abatement area to the south of the control zone. Do not overly this area below 2000 MSL. Finally, please note the proximity to Helsinki-Malmi Airport. Flying VFR within the Helsinki CTR can be a tricky ordeal. There is a lot to look out for so please be prepared!