1,414
edits
(Departure added + minor fixes) |
(→Approaching the destination airport: correct info) |
||
(20 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{ATC-navbar}} | {{ATC-navbar}} | ||
{{Main article|Air traffic control}} | |||
{{Main article|Air | |||
[[Air traffic control|Air Traffic Control]] is an agreed procedure and process which keeps the [[aircraft]] separated to ensure that they don't crash into each other or are affected by turbulence when passing through the same air space. | [[Air traffic control|Air Traffic Control]] is an agreed procedure and process which keeps the [[aircraft]] separated to ensure that they don't crash into each other or are affected by turbulence when passing through the same air space. This article, probably more directly useful for pilots, will teach you that procedure and will hopefully help you to enjoy controlled areas and airports on the FlightGear multiplayer servers. | ||
This article, | |||
== Controller roles == | == Controller roles == | ||
Line 29: | Line 21: | ||
| xxxx_TW | | xxxx_TW | ||
| Tower | | Tower | ||
| Controls the runways and the airspace up to 10 NM (nautical miles) from the airport; chooses the runways to use; clears planes for takeoff and landing, making sure that they are at least 10 NM or three minutes apart. | | Controls the ''active'' runways and the airspace up to 10 NM (nautical miles) from the airport; chooses the runways to use; clears planes for takeoff and landing, making sure that they are at least 10 NM or three minutes apart. | ||
|- | |- | ||
| xxxx_AP | | xxxx_AP | ||
Line 44: | Line 36: | ||
|} | |} | ||
The "xxxx" in the table replace a code used to identify the area that controller is using; these are known as ''ICAO codes'' and can be found on the [http://www.airport-technology.com/icao-codes/ Airport Codes list]. For example, London Gatwick is "EGKK" so a Gatwick Tower Controller would log-in as ''EGKK_TW''. | * The "xxxx" in the table replace a code used to identify the area that controller is using; these are known as ''ICAO codes'' and can be found on the [http://www.airport-technology.com/icao-codes/ Airport Codes list]. For example, London Gatwick is "EGKK" so a Gatwick Tower Controller would log-in as ''EGKK_TW''. | ||
* Center controllers also have ICAO identifiers, but they are not for one airport, but for a larger area. For example, ''LFFF_CT'' is France Center, and ''LFFF_FS'' is the France Flight Service Station. | |||
* At large airports, multiple controllers may man the same positions. | |||
Center controllers also have ICAO identifiers, but they are not for one airport, but for a larger area. For example, ''LFFF_CT'' is France Center, and ''LFFF_FS'' is the France Flight Service Station. | |||
=== Controller roles in FlightGear === | === Controller roles in FlightGear === | ||
Line 61: | Line 51: | ||
{{Main article|Flight rules}} | {{Main article|Flight rules}} | ||
A distinction you should know for flying in controlled areas is the one between IFR and VFR flights, as flight planning and some phraseology are different. | A distinction you should know for flying in controlled areas is the one between IFR and VFR flights, as flight planning and some phraseology are different. | ||
* VFR (Visual Flight Rules) can apply when a pilot is able to orientate and recognize other aircraft and obstacles visually (that means | * VFR (Visual Flight Rules) can apply when a pilot is able to orientate and recognize other aircraft and obstacles visually (that means, for example, the sky should be clear of clouds at low altitudes near the airport when taking off and landing, light must be sufficient, and there must be little or no fog at all); they are used mainly in general aviation; | ||
* IFR (Instrument Flight Rules) apply in all | * IFR (Instrument Flight Rules) apply in all other cases. | ||
== Getting and reading charts == | == Getting and reading charts == | ||
Line 94: | Line 84: | ||
==== Getting the departure clearance ==== | ==== Getting the departure clearance ==== | ||
We start on the airport apron at terminal T1, stand | We start on the airport apron at terminal T1, stand 221. | ||
The first thing we need to do is to check the current air pressure and which runway is being used; as a general rule, planes should be heading into the wind for takeoff and landing. To accomplish this, we need to listen to the ''ATIS'' (Automatic Terminal Information Service), a prerecorded message describing weather information, the runways in use and other important information for pilots | The first thing we need to do is to check the current air pressure and which runway is being used; as a general rule, planes should be heading into the wind for takeoff and landing. To accomplish this, we need to listen to the ''ATIS'' (Automatic Terminal Information Service), a prerecorded message describing weather information, the runways in use and other important information for pilots; it's transmitted continuously on a dedicated radio channel. The frequency to use is written in the Airport information chart and can also be found by clicking on ''AI -> ATC Services in Range -> LEBL'': in our case, it's 121.970 MHz. | ||
We open the Radio panel, set the COM1 frequency to 121.97 and listen to the ATIS message: | We open the Radio panel, set the COM1 frequency to 121.97 and listen to the ATIS message: | ||
Line 103: | Line 93: | ||
# We're going to depart from runway 25L. | # We're going to depart from runway 25L. | ||
# We need to set the altimeter to 1018 hPa<ref>European airports generally use hPa (hectopascals) for the QNH while American ones use inHg (inches of mercury). Some airplanes allow you to enter QNH values using both units; if that is not the case, you will need to use a converter.</ref> and set it back to standard pressure (STD) at the transition level (FL050, or 5000 feet). | # We need to set the altimeter to 1018 hPa<ref>European airports generally use hPa (hectopascals) for the QNH while American ones use inHg (inches of mercury). Some airplanes allow you to enter QNH values using both units; if that is not the case, you will need to use a converter.</ref> and set it back to standard pressure (STD) at the transition level (FL050, or 5000 feet). | ||
# Every ATIS broadcast is identified by a progressive letter of the [http://en.wikipedia.org/wiki/NATO_phonetic_alphabet NATO phonetic alphabet]; we'll need to tell the delivery controller that we have information "Alpha" so that (s)he can | # Every ATIS broadcast is identified by a progressive letter of the [http://en.wikipedia.org/wiki/NATO_phonetic_alphabet NATO phonetic alphabet]; we'll need to tell the delivery controller that we have information "Alpha" so that (s)he can check whether we have the latest information or not. | ||
Note also that numbers are spelled out for clarity - this will be done in all further communication. | Note also that numbers are spelled out for clarity - this will be done in all further communication. | ||
Line 120: | Line 110: | ||
# The controller corrects any mistakes we've made and then hands us off to the Ground controller. | # The controller corrects any mistakes we've made and then hands us off to the Ground controller. | ||
* '''BAW1542:''' El Prat Delivery, this is Speedbird one five four, requesting delivery to Frankfurt, flight level two five zero, we have information Alpha. | * '''BAW1542:''' El Prat Delivery, this is Speedbird one five four two, requesting delivery to Frankfurt, flight level two five zero, we have information Alpha. | ||
* '''El Prat Delivery:''' Speedbird one five four two, Alpha is current, cleared to Frankfurt via OKABI three Whiskey, initial altitude five hundred feet, expect flight level two five zero after ten minutes, squawk four zero zero zero. | * '''El Prat Delivery:''' Speedbird one five four two, Alpha is current, cleared to Frankfurt via OKABI three Whiskey, initial altitude five hundred feet, expect flight level two five zero after ten minutes, squawk four zero zero zero. | ||
* '''BAW1542:''' Cleared to Frankfurt via OKABI three Whiskey, initial altitude five hundred feet, expect flight level two five zero after ten minutes, squawk four zero zero zero, Speedbird one five four two. | * '''BAW1542:''' Cleared to Frankfurt via OKABI three Whiskey, initial altitude five hundred feet, expect flight level two five zero after ten minutes, squawk four zero zero zero, Speedbird one five four two. | ||
Line 133: | Line 123: | ||
Before pushing back (being pushed away from the stand with a tug) and starting up, we need to get appropriate clearances from the Ground controller. This ensures we won't block taxiways unnecessarily. | Before pushing back (being pushed away from the stand with a tug) and starting up, we need to get appropriate clearances from the Ground controller. This ensures we won't block taxiways unnecessarily. | ||
* '''BAW1542:''' El Prat Ground, Speedbird one five four two at stand two two | * '''BAW1542:''' El Prat Ground, Speedbird one five four two at stand two two one, request pushback. | ||
* '''El Prat Ground:''' Speedbird one five four two, El Prat Ground, pushback approved, facing | * '''El Prat Ground:''' Speedbird one five four two, El Prat Ground, pushback approved, facing south. | ||
* '''BAW1542:''' Pushback approved, facing | * '''BAW1542:''' Pushback approved, facing south, Speedbird one five four two. | ||
We then push back, making sure the aircraft is turned towards ("facing") | We then push back, making sure the aircraft is turned towards ("facing") south at the end of the maneuver, and ask for permission to start our engines. | ||
[[File:LEBL-stand220-pushback.png|thumb | [[File:LEBL-stand220-pushback.png|center|thumb|800px|Our aircraft's position after pushback (noon and night view). Note that the taxiway centerlines are not lit in proximity of stands.]] | ||
* '''BAW1542:''' Speedbird one five four two, request startup. | * '''BAW1542:''' Speedbird one five four two, request startup. | ||
Line 166: | Line 156: | ||
* '''BAW1542:''' Speedbird one five four two, we're holding short Echo two. | * '''BAW1542:''' Speedbird one five four two, we're holding short Echo two. | ||
* '''El Prat Ground:''' Speedbird one five four two, cleared to cross runway zero two, taxi to holding point Golf one via Echo one and Kilo. | * '''El Prat Ground:''' Speedbird one five four two, cleared to cross runway zero two, taxi to holding point Golf one via Echo one and Kilo. | ||
* '''BAW1542:''' | * '''BAW1542:''' Cleared to cross runway zero two and taxi to holding point Golf one via Echo one and Kilo, Speedbird one five four two. | ||
We then cross the runway without delay and turn left on K. Near K2 you can notice a ''CAT II/III holding point'' (marked by an empty yellow rectangle with vertical lines, equipped with ''fixed'' lights) - that's where we would stop if visibility was reduced or if another aircraft was landing using ILS; since that's not the case and we were cleared to G1, just proceed. | We then cross the runway without delay and turn left on K. Near K2 you can notice a ''CAT II/III holding point'' (marked by an empty yellow rectangle with vertical lines, equipped with ''fixed'' lights) - that's where we would stop if visibility was reduced or if another aircraft was landing using ILS; since that's not the case and we were cleared to G1, just proceed. | ||
Line 176: | Line 166: | ||
We stop at G1 while the ground controller instructs us to contact the tower: | We stop at G1 while the ground controller instructs us to contact the tower: | ||
* '''El Prat Ground:''' Speedbird one five four two, contact Tower on one one eight decimal three two zero, goodbye! | * '''El Prat Ground:''' Speedbird one five four two, contact El Prat Tower on one one eight decimal three two zero, goodbye! | ||
* '''BAW1542:''' Contact Tower on one one eight decimal three two zero, Speedbird one five four two, bye! | * '''BAW1542:''' Contact El Prat Tower on one one eight decimal three two zero, Speedbird one five four two, bye! | ||
==== Lining up and taking off ==== | ==== Lining up and taking off ==== | ||
Line 206: | Line 196: | ||
* '''BAW1542:''' Resuming our own navigation, frequency change approved, Speedbird one five four two, bye! | * '''BAW1542:''' Resuming our own navigation, frequency change approved, Speedbird one five four two, bye! | ||
We're now free to follow our flightplan - it's a good practice to keep an eye on the multiplayer map to check for traffic, | We're now free to follow our flightplan - it's a good practice to keep an eye on the multiplayer map to check for traffic and to announce altitude changes/turns on text chat if other pilots are nearby.<ref>In real world flying, we would be handed off to center controllers and we would report our position over special points, marked as black triangles in the charts. Since center controllers are not common in FlightGear, this is not usually done.</ref> | ||
==== Approaching the destination airport ==== | ==== Approaching the destination airport ==== | ||
We start descending on our own so as to reach FL150 approximately 100 NM from the destination airport. When we're about 80 NM from EDDF we check the ATIS for the destination airport, just like we did at LEBL - in this case the frequency is 118.02. We tune in the COM1 radio to that frequency and listen: | |||
* '''EDDF ATIS:''' ''This is Frankfurt information Echo. Landing runway zero seven right. Departure runway zero seven center. Transition level five zero. Wind zero two zero degrees, four knots. Visibility one zero km or more, few four thousand eight hundred feet. Temperature one niner<ref>"Niner" is used instead of "nine" to avoid confusion between the similarly sounding "nine" and "nein", the German word for "no".</ref>, dewpoint zero seven. QNH one zero one eight. No significant change. On initial contact advise controller you have information Echo.'' | |||
We then contact the approach controller (in this case Langen Radar, 118.45 MHz): | |||
* '''BAW1542:''' Langen Radar, Speedbird one five four two at flight level one five zero, we have information Echo. | |||
* '''Langen Radar:''' Speedbird one five four two, radar contact, Echo is current, descend and maintain five thousand feet, proceed direct UNOKO. | |||
* '''BAW1542:''' Descend and maintain five thousand feet, proceed direct UNOKO, Speedbird one five four two. | |||
We proceed to the UNOKO waypoint and descend to 5000 ft, as instructed. At 5000 ft we set the altimeter to the local QNH (1018 hPa). | |||
When we're near UNOKO the approach controller will contact us and assign us a STAR (standard arrival route): | |||
'' | * '''Langen Radar:''' Speedbird one five four two, cleared UNOKO one Mike arrival. | ||
* '''BAW1542:''' Cleared UNOKO one Mike arrival, Speedbird one five four two. | |||
Now we follow the altitudes and route in the STAR – in this case, we fly over UNOKO, IBVIL, MANUV, RAMOB and proceed to TAU. | |||
We hold (circle) over TAU until the controller instructs us to continue the approach: | |||
* '''Langen Radar:''' Speedbird one five four two, turn right heading one four zero, descend and maintain three thousand feet, reduce speed to two five zero knots. | |||
* '''BAW1542:''' Turn right heading one four zero, descend and maintain three thousand feet, reducing speed to two five zero knots, Speedbird one five four two. | |||
We now engage the autopilot's heading select mode, fly the given heading, reduce our speed and continue our descent as cleared. After a couple of minutes, the controller calls us and instructs us to use the [[Instrument Landing System]] to get towards the runway: | |||
''' | * '''Langen Radar:''' Speedbird one five four two, cleared ILS approach runway zero seven right. | ||
''' | * '''BAW1542:''' Cleared ILS approach runway zero seven right, Speedbird one five four two. | ||
As soon as the localizer is alive we engage the autopilot's localizer mode and, as soon as the glideslope is alive, we switch to approach mode and descend on the glide. The controller will call us one last time to hand us over to Frankfurt Tower: | |||
''' | * '''Langen Radar:''' Speedbird one five four two, contact Frankfurt Tower on one one niner decimal niner zero. | ||
* '''BAW1542:''' Contact Frankfurt Tower on one one niner decimal niner zero, Speedbird one five four two. | |||
==== Landing ==== | |||
We switch to 119.90 MHz and/or join the Frankfurt Tower channel on Mumble, then contact the tower controller to get the landing clearance. It will include: | |||
# the wind direction and speed; | |||
# wind gusts, if any; | |||
# warnings (like wake turbulence, rain...), if any; | |||
# the runway number; | |||
# the words ''cleared to land''. | |||
* | * '''BAW1542:''' Frankfurt Tower, Speedbird one five four two, ILS approach runway zero niner right. | ||
* | * '''Frankfurt Tower:''' Speedbird one five four two, Frankfurt Tower, wind zero one zero degrees, five knots, runway zero seven right, cleared to land. | ||
* | * '''BAW1542:''' Cleared to land, runway zero seven right, Speedbird one five four two. | ||
<gallery widths=400px mode=packed> | |||
File:EDDF-finalapproach.png|Short final to runway 07R. | |||
File:EDDF-landing-07R.png|Landing on 07R. | |||
</gallery> | |||
We land on 07R and ''vacate'' (exit) the runway at the earliest opportunity, making sure not to block other aircraft and not to enter a taxiway marked with a ''NO ENTRY'' sign; in this case, we vacate on the left, since the terminal is on the left. (On occasion, the controller will ask us to vacate on a specific side or to use a specific exit). We are now asked to switch to Ground: | |||
* '''Frankfurt Tower:''' Speedbird one five four two, contact Frankfurt Ground on one two one decimal eight zero. | |||
* '''BAW1542:''' Contact Frankfurt Ground on one two one decimal eight zero, Speedbird one five four two. | |||
==== Taxiing to the stand and shutting down ==== | |||
We switch the transponder to ground mode and check the ground chart to get the name of the taxiway we are on; in our case, we have vacated the runway on taxiway M15. We then contact the ground controller: | |||
* '''BAW1542:''' Frankfurt Ground, Speedbird one five four two on Mike one five, runway zero seven right vacated. | |||
* '''Frankfurt Ground:''' Speedbird one five four two, Frankfurt Ground, taxi to holding point Mike one four via Mike, hold short of Mike one four. | |||
* '''BAW1542:''' Taxi to holding point Mike one four via Mike, hold short of Mike one four, Speedbird one five four two. | |||
We taxi to holding point M14, stop and report our position to the controller, so that (s)he can coordinate with Tower and clear us to cross the active runway 07C. | |||
* '''BAW1542:''' Speedbird one five four two, holding short Mike one four. | |||
* '''Frankfurt Ground:''' Speedbird one five four two, standby. ''(The controller will ask Tower for crossing clearance – it might take a bit.)'' | |||
* '''Frankfurt Ground:''' Speedbird one five four two, cleared to cross zero seven center, taxi to Lima via Lima niner. | |||
* '''BAW1542:''' Cleared to cross zero seven center, taxi to Lima via Lima niner, Speedbird one five four two. | |||
At this point, we resume taxiing, making sure to cross the runway expeditiously. | |||
Since the taxiways and the apron are managed by two different controllers, the ground controller will hand us off to the apron controller: | |||
* '''Frankfurt Ground:''' Speedbird one five four two, contact Apron East on one two one decimal niner five. | |||
* '''BAW1542:''' Contact Apron East on one two one decimal niner five, Speedbird one five four two. | |||
We switch to the new frequency and report: | |||
* '''BAW1542:''' Apron East, Speedbird one five four two on Lima nine, request taxi to the stand. | |||
* '''Apron South:''' Speedbird one five four two, Apron East, taxi to stand Delta five via Lima and November one. | |||
* '''BAW1542:''' Taxi to stand Delta five via Lima and November one, Speedbird one five four two. | |||
<gallery widths=400px mode=packed> | |||
File:EDDF-M15.png|Taxiing on M15. | |||
File:EDDF-crossing-07C.png|Approaching holding point M14 and preparing to cross runway 07C. Note that the stop bar is not lit, only the ground sign tells you to hold short of the runway – so be careful. | |||
File:EDDF-L.png|Taxiing on L. | |||
</gallery> | |||
' | We taxi to the stand and shut down, also switching the transponder off – there's no need to ask a clearance for that. Our flight is now finished. | ||
==== This tutorial in video format ==== | |||
The departure and arrival presented in this tutorial have also been recorded. Some interactions were simplified, the result should however be more close to what you usually experience on the multiplayer network. Closed captions are available. | |||
{{#ev:youtube|dA-UXATCHuI|400}} | |||
{{#ev:youtube|E3yfeWjlyic|400}} | |||
=== A sample VFR flight === | |||
[http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=12953 de profundis] has written a VFR tutorial that takes you for a sample flight from KRNO (Reno Tahoe) to KBIH (Eastern Sierra Regional) and covers VFR flight planning, phraseology and tips in great detail. You can get his ''Cross Country Tutorial'' from the [http://forum.flightgear.org/viewtopic.php?f=72&t=19600 dedicated forum thread]. | |||
== Tips == | |||
* This tutorial, for the sake of simplicity and brevity, assumed no other aircraft was present. On multiplayer servers you might be instructed to hold your position, give way to other aircraft or hold (make circles) over a point to remain separate from other aircraft; check the [[ATC phraseology]] page for the specific phraseology used in those situations. | |||
* Follow the guidelines detailed in [[ATC best practices]] to make the experience enjoyable for everyone. | |||
* When practicing controlled flying, make sure you know your aircraft well (you should be able to maintain an assigned speed, altitude and heading), go to a less trafficked airport and tell the controller it's your first time interacting via ATC. | |||
* '''Remember to read back (repeat) the clearances; it is the only way for the controller to know whether you received them correctly or not.''' | |||
* Execute the clearances while reading them back. | |||
== Notes == | == Notes == |
edits