329
edits
ATC tutorial: Difference between revisions
Jump to navigation
Jump to search
Added rewrite notice, rewritten introduction, first section
Fusionstream (talk | contribs) (Adjust wind heading under lesson 3. Erroneously described Wind reading as direction wind is going to. Fixed to say it describes where winds are coming from.) |
(Added rewrite notice, rewritten introduction, first section) |
||
| Line 1: | Line 1: | ||
{{ATC-navbar}} | {{ATC-navbar}} | ||
{{WIP|Complete rewrite in progress by [[User:elgaton|elgaton]]}} | |||
{{Main article|Air Traffic Control}} | {{Main article|Air Traffic Control}} | ||
[[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, written for controllers and pilots alike, will teach you that procedure and will hopefully help you to enjoy controlled areas and airports on the FlightGear multiplayer servers. | |||
== How do I know if an airport is controlled? == | |||
Check the Pilot List in FlightGear or the [[MPMap|Multiplayer map]]. Usually, controllers: | |||
* have a callsign ''XXXX_DE'', ''XXXX_GN'', ''XXXX_TW'' or ''XXXX_AP'' (where ''XXXX'' is the ICAO code of the airport they are manning); each callsign has a specific meaning (see "Controller roles" below); | |||
* use the ''[[OpenRadar]]'', ''ATC-TOWER'', ''[[ATC-aircraft|ATC]]'' (or similarly named) aircraft. | |||
== Lesson 1 == | == Lesson 1 == | ||