258
edits
ATC best practices: Difference between revisions
→Additional best practices: Linking to relevant airport wiki pages
m (lenny's website for pilots) |
(→Additional best practices: Linking to relevant airport wiki pages) |
||
| Line 34: | Line 34: | ||
# '''Disable [[Interactive traffic|AI traffic]]''' (but leave AI models on). | # '''Disable [[Interactive traffic|AI traffic]]''' (but leave AI models on). | ||
# If you have planned your flight, '''consider using [http://flightgear-atc.alwaysdata.net/ Lenny's website] to file your flightplan'''. | # If you have planned your flight, '''consider using [http://flightgear-atc.alwaysdata.net/ Lenny's website] to file your flightplan'''. | ||
# If you are using a recent version of FlightGear (2 | # If you are using a recent version of FlightGear (3.2 or later), '''use the transponder''' if the controller requests it. | ||
# If you're flying into an uncontrolled area, use the multiplayer chat to advise nearby traffic of your intentions. | # If you're flying into an uncontrolled area, use the multiplayer chat to advise nearby traffic of your intentions. | ||
# Check the wiki to get more information about the scenery existing at your destination | |||
## The list of [[Developed Airports]] gives a good overview of well modelled airports published on TerraSync. | |||
## Regularly controlled Airports like [[Amsterdam Airport Schiphol|Amsterdam]], [[LIME|Bergamo]], [[Frankfurt am Main Airport|Frankfurt]], [[Leipzig/Halle Airport|Leipzig/Halle]] or [[LKPR - Vaclav Havel Airport Prague|Praque]] are well documented here. | |||
== Best practices for controllers == | == Best practices for controllers == | ||