https://wiki.flightgear.org/w/api.php?action=feedcontributions&feedformat=atom&user=InetukaFlightGear wiki - User contributions [en]2026-04-10T18:00:06ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=122922OpenRadarGuide2020-04-04T22:32:31Z<p>Inetuka: /* Java V7 */</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently and require almost no training. The ATC has other things to do than to fight the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as in speech (Radio). You soon will discover that using a Radio-application makes it much easier to communicate for you ''(who hopefully will control many pilots at the same time)'' *as well for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "itpns.ddns.net"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least version 7 of Java. Verify and/or download the installation packages from: http://www.java.com/en/download/index.jsp<br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see https://sourceforge.net/projects/openradar/files/<br />
* Download "Latest Release" for the latest version prior to the new "Flight-Strip-Bay" version<br />
* Download "Next Release" for the really newest version.<br />
Prior to extracting move the ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''itpns.ddns.net'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''not use''' runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''use''' runway 18 for "Starts" only --> thus enable "Starts" only<br />
:::'''use''' runway 07L and 25R for "Landings" only --> thus enable only "Landing"<br />
:::<small>(Compare the picture "The Runway Manager" on the right: The left marks enable the function - the right ones enable the SID/STAR functions)<br />
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="keytable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[sourceforge.net/projects/openradar/files|'''Download''' OpenRadar]]<br />
* [[OpenRadar_FGFS_ORCAM|'''ORCAM''' = View the targets as model]]<br />
* [[OpenRadar:_Transponder|Using '''Transponder'''-Codes]]<br />
* [[OpenRadar: Editing routes|Editing '''STAR/SID''' routes]]<br />
* [[OpenRadar:_Flightstrip|'''Flightstrips''']]<br />
* [[OpenRadar:_Flightstrips-Bay|'''Flightstrips-Bay''']]<br />
* [[OpenRadar:_Chat_aliases|'''Chat_aliases''']]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadarFeatureWishlist|OpenRadarFeatureWishlist]]<br />
[[Category:OpenRadar|Guide]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=122921OpenRadarGuide2020-04-04T22:31:18Z<p>Inetuka: /* Communication */</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently and require almost no training. The ATC has other things to do than to fight the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as in speech (Radio). You soon will discover that using a Radio-application makes it much easier to communicate for you ''(who hopefully will control many pilots at the same time)'' *as well for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "itpns.ddns.net"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see https://sourceforge.net/projects/openradar/files/<br />
* Download "Latest Release" for the latest version prior to the new "Flight-Strip-Bay" version<br />
* Download "Next Release" for the really newest version.<br />
Prior to extracting move the ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''itpns.ddns.net'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''not use''' runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''use''' runway 18 for "Starts" only --> thus enable "Starts" only<br />
:::'''use''' runway 07L and 25R for "Landings" only --> thus enable only "Landing"<br />
:::<small>(Compare the picture "The Runway Manager" on the right: The left marks enable the function - the right ones enable the SID/STAR functions)<br />
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="keytable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[sourceforge.net/projects/openradar/files|'''Download''' OpenRadar]]<br />
* [[OpenRadar_FGFS_ORCAM|'''ORCAM''' = View the targets as model]]<br />
* [[OpenRadar:_Transponder|Using '''Transponder'''-Codes]]<br />
* [[OpenRadar: Editing routes|Editing '''STAR/SID''' routes]]<br />
* [[OpenRadar:_Flightstrip|'''Flightstrips''']]<br />
* [[OpenRadar:_Flightstrips-Bay|'''Flightstrips-Bay''']]<br />
* [[OpenRadar:_Chat_aliases|'''Chat_aliases''']]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadarFeatureWishlist|OpenRadarFeatureWishlist]]<br />
[[Category:OpenRadar|Guide]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=122920OpenRadarGuide2020-04-04T22:28:25Z<p>Inetuka: /* Preface */</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently and require almost no training. The ATC has other things to do than to fight the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "itpns.ddns.net"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see https://sourceforge.net/projects/openradar/files/<br />
* Download "Latest Release" for the latest version prior to the new "Flight-Strip-Bay" version<br />
* Download "Next Release" for the really newest version.<br />
Prior to extracting move the ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''itpns.ddns.net'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''not use''' runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''use''' runway 18 for "Starts" only --> thus enable "Starts" only<br />
:::'''use''' runway 07L and 25R for "Landings" only --> thus enable only "Landing"<br />
:::<small>(Compare the picture "The Runway Manager" on the right: The left marks enable the function - the right ones enable the SID/STAR functions)<br />
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="keytable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[sourceforge.net/projects/openradar/files|'''Download''' OpenRadar]]<br />
* [[OpenRadar_FGFS_ORCAM|'''ORCAM''' = View the targets as model]]<br />
* [[OpenRadar:_Transponder|Using '''Transponder'''-Codes]]<br />
* [[OpenRadar: Editing routes|Editing '''STAR/SID''' routes]]<br />
* [[OpenRadar:_Flightstrip|'''Flightstrips''']]<br />
* [[OpenRadar:_Flightstrips-Bay|'''Flightstrips-Bay''']]<br />
* [[OpenRadar:_Chat_aliases|'''Chat_aliases''']]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadarFeatureWishlist|OpenRadarFeatureWishlist]]<br />
[[Category:OpenRadar|Guide]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=OpenRadarGuide&diff=122919OpenRadarGuide2020-04-04T22:26:36Z<p>Inetuka: /* Preface */</p>
<hr />
<div>[[OpenRadar|Back to mainpage]]<br />
<br />
=='''''Preface'''''==<br />
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear. <br />
<br />
Some words to our project targets:<br />
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation. <br />
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.<br />
<br />
We hope that we met your needs and are happy to get feedback!<br />
<br />
'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...<br />
<br /><br /><br />
----<br />
<br />
=='''''Prerequisites'''''==<br />
===Internet===<br />
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!<br />
<br />
===Communication===<br />
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).<br />
You will soon discover, that using a Radio-application makes it much easier to communicate<br />
*as well for you ''(who hopefully will control many pilots at the same time)''<br />
*as also for the pilots ''(who need both hands to control their plane)''.<br />
<br />
Typically available ways of communication are:<br />
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.<br />
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:<br />
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.<br />
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone". <br />
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.<br />
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.<br />
:::To activate it see http://mumble.sourceforge.net/Mumbleguide<br />
:::The most used Mumble-server is "itpns.ddns.net"<br />
<br />
=== Java V7 ===<br />
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp <br />
<br />
=== OpenRadar ===<br />
For the latest stable version of OpenRadar see https://sourceforge.net/projects/openradar/files/<br />
* Download "Latest Release" for the latest version prior to the new "Flight-Strip-Bay" version<br />
* Download "Next Release" for the really newest version.<br />
Prior to extracting move the ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.<br />
<br /><br /><br />
If you did already work with an OpenRadar installation you may want to<br />
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")<br />
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")<br />
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"<br />
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories<br />
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!<br />
<br />
== '''''Startup''''' ==<br />
Inside the downloaded OpenRadar base-directory you will find start-scripts. See<br />
* for Windows: OpenRadar.bat<br />
* for Linux: OpenRadar.sh<br />
* for OSX: OpenRadar.jar<br />
<br clear=all><br />
=== OpenRadar-Welcome - Select Airport ===<br />
[[File:OpenRadar - Welcome-Linux.png|thumb|right|Welcome - Select Airport]] <br />
OpenRadar will always start with this Window in which you define the airport on which you want to operate:<br />
* '''If this is the first time you work with OpenRadar you first must check/set your options also in all the other tabs!'''<br />
* If the wanted airport is not yet listed:<br />
** type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"<br />
*** if that ICAO code is available, then OpenRadar will add it to the list<br />
*** then a single mouseclick onto one of the listed airports will activate that selection<br />
*** and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session <small>(ref. chapter [[#Status_Informations]])</small><br />
** then you can review all settings prior you click onto Start<br />
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''<br />
** a double-click on it will order OpenRadar to search and load all the required data <small>(into your local file "OpenRadar/Data/ICAO")</small><br />
** that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"<br />
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"<br />
<br />
<br clear=all><br />
=== Settings (Communication) ===<br />
[[File:OpenRadar- Settings-linux.png|thumb|right|Settings - Communication]]<br />
This window lets you define your communication settings:<br />
<br />
==== ''FGCom (Radio/Voice Communication)'' ====<br />
:OpenRadar can support up to 4 instances of FGcom in 2 ways:<br />
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)<br />
:#or just control manually started FgCom-sessions.<br />
<br />
:You select these modes of operation by the “'''FgComMode'''” selection:<br />
<br /><br />
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar<br />
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:<br />
::'''Path:''' Here you define where your FGcom is installed.<br />
:::In the following some examples:<br />
<small><br />
:::{| class="wikitable" style="text-align:center"<br />
!type<br />
!Windows<br />
!Linux<br />
!OSX<br />
|-<br />
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)<br />
|-<br />
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)<br />
|- <br />
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)<br />
|}<br />
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''<br />
</small><br />
::'''Executable:''' Here you define the program-name that shall be started<br />
:::*For Windows: "fgcom.exe" or "anyName.bat"<br />
:::*for Linux: "fgcom" or "anyName.sh"<br />
:::*OSX: ''again for OSX this does not apply, see 1b''<br />
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)<br />
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org<br />
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''<br />
::'''Client:''' must always be “localhost”<br />
::'''FGcom Ports:''' The here defined values are crucial for the operation because: <br />
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!<br />
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar<br />
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!<br />
:::::e.g. 16661,16662<br />
<br /><br />
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.<br />
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:<br />
::*'''Client:''' localhost<br />
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,<br />
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" </small><br />
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''<br />
<br /><br />
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)<br />
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. <br />
<br />
==== ''Alternative Radios (e.g. '''Mumble''')'' ====<br />
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.<br />
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation<br />
<br />
==== ''FG Multiplayer'' ====<br />
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.<br />
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". <br />
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.<br />
<br />
==== ''Multiplayer Chat'' ====<br />
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.<br />
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").<br />
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".<br />
<br />
==== ''METAR'' ====<br />
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.<br />
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!<br />
<br />
<br clear=all><br />
=== Flightplans ===<br />
[[File:OpenRadar-Flightplans-Linux.png|thumb|tight|Flightplans]]<br />
In order to exchange information’s about targets with other OpenRadar-locations, You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:<br />
<br>http://h2281805.stratoserver.net/FgFpServer/<br />
<br>Under this address you can also check where ATC's are offering services right now.<br />
<br />
Please click on the "Check Settings" button to have your settings checked prior to continue:<br />
<br />
<br clear=all><br />
=== Tweaks ===<br />
[[File:OpenRadar - Tweaks.png|thumb|right|Tweaks]] <br />
Select/enable according to the descriptions.<br />
<br />Be aware that these option may influence the responstimes of your PC drastically!<br />
<br />
<br clear=all><br />
=== FGFS ORCAM ===<br />
[[File:OpenRadar_-_FGFS_ORCAM.png|thumb|right|FGFS ORCAM]]<br />
This is an additive feature to OpenRadar, that enables you to view OpenRadar targets as Models - e.g. while they are taxiing on GND or are approaching/departing your airport. For this you can position your "Viewpoint" where you want and watch from there.<br />
<br />
For details on how to install and operate see: [[OpenRadar_FGFS_ORCAM]]<br />
<br />
<br clear=all><br />
== '''''Operating''''' ==<br />
[[File:OpenRadar Prototype.png|right|270px]]<br />
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''<br />
<br />
The OpenRadar main screen is divided into four regions:<br />
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.<br />
#At the bottom of that Radar Map there is a line for '''Radar Options'''<br />
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature<br />
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are <br />
##'''Status Information'''<br />
##'''Radios for Communication''' <small>''(only if you have defined one or more in chapter [[#Settings]] )''</small><br />
##'''Runway Manager''' to set up runways used <br />
##the '''Flight Strip Manager''', where you can manage your radar targets.<br />
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.<br />
==== Radar Map ====<br />
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:<br />
* zoom in and out using your mouse wheel <small>''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''</small><br />
* adjust the map-center by dragging it with your mouse (click-hold left and drag)<br />
* a double mouse-click onto the scope will move that point into the center of the scope<br />
* a double right mouse-click will center the scope back to your location<br />
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly <br />
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.<br />
<br />
<br /><br />
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]<br />
The standard '''''Radar-targets''''' <br />
*do have a label attached with the following informations:<br />
::<small>''(See also the chapter [[#Flight-management]])''</small><br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|UID||heading direction<br />
|-<br />
|Airplane type||Flightplan||controlling ATC <small>(if not you)</small><br />
|-<br />
|Flight Level||Airspeed<br />
|}<br />
*and are displayed in 6 different colors: <br />
:{| class="wikitable"<br />
|-<br />
|align="middle"|blue||That are all targets that you controll<br />
<small>see e.g. "KL-666" on approach and "B777-20" ready for TakeOff<br />
<br>their Flightstrips are placed to the left</small><br />
|-<br />
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages<br />
<small>see e.g. "G-MNKY" who just gets his taxi-instructions from you<br />
<br>his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) </small><br />
|-<br />
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!<br />
<small>their Flightstripes are placed into the middle</small><br />
|-<br />
|align="center"|green||targets who are not controlled by you<br />
<small>see e.g. "CEMI198" just crossing in high altitude - outside your control<br />
<br>their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially</small><br />
|-<br />
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.<br />
|}<br />
<br />
==== ''Radar-Options'' ====<br />
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]<br />
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:<br />
<br /><br />
[[File:OpenRadar-Radar-Options.png|250px]]<br />
<br /><br /><br />
'''''a) map:'''''<br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', <small>an attachment to the mousepointer, showing<br />
*the direction from the "active target" to the mouse-position (and reverse)<br />
*and the distance and the calculated time for the target to get there|</small><br />
|-<br />
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | FIX || Show/NoShow FIX's <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures <small>(those will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | NDB || Show/NoShow NDB's<br />
|-<br />
| style="text-align:center;" | VOR || Show/NoShow VOR's<br />
|-<br />
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout <small>(You may double-click onto a wanted airport and zoom in to see the layout)</small><br />
|-<br />
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!<br />
|-<br />
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. <small>(They will automatically be set "NoShow" above distinct scale-settings!)</small><br />
|-<br />
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. <small>Try it and notice the differences in the Target-tags and Flightstrips.</small><br />
|-<br />
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture<br />
|-<br />
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target<br />
|-<br />
| style="text-align:center;" | layers || lets you select to add overlays to the radar:<br />
*landmass = costlines and similar<br />
*taramacs = the GND-shape of airports<br />
|}<br />
<br /><br />
'''''b) sounds:'''''<br />
<br>Here you can select which "happenings" will produce an additional sound <small>(This list may change in further releases)</small><br />
<br /><br /><br />
'''''c) STP:'''''<br />
<br><br />
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' <small>(Same as in table above - just for faster access)</small><br />
<br /><br /><br />
'''''d) STAR/SID:'''''<br />
<br><br />
Show/NoShow the unique Waypoints defined in the STAR/SID's<br />
<br /><br /><br />
'''''e) PPN:'''''<br />
<br><br />
Show/NoShow Parking/Gate names <small>(Same as in table above)</small><br />
<br />
<br /><br /><br />
==== MPchat area ====<br />
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]<br />
This area allows you to enter chat messages, view the chat history and filter it.<br />
<br /><br />
In the '''''entry-line''''' atop you define your messages to any radar-target by:<br />
*Manually typing a message:<br />
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line<br />
**Then you may type or copy/past anything behind that - and send it out by ENTER<br />
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.<br />
*Generate a standard message:<br />
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click<br />
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER<br />
*Repeat a message:<br />
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.<br />
<br />
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. <br />
<br />
Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".<br />
<br />
You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!<br />
<br />
==== Service Area ====<br />
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.<br />
<br />
=====Status Informations===== <br />
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]<br />
<br />
This area shows in 4 lines the status-informations of your session <small>''(compare the picture)''</small>:<br />
* The first line contains several informations:<br />
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" <small>''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''</small><br />
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:<br />
:::* 5000 gives the "Transition Altitude" in feet when climbing<br />
:::* TL055 gives the "Transition Level" when descending into that area <small>''(in FlightLevels: 1 FL = 100 feet))''</small><br />
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury<br />
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. <small>(ref. chapter [[#Startup]])</small><br />
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport. <br />
* The last 2 lines show the current '''[[Weather_reports]]''' <small>(also called ATIS or METAR)</small>: <br />
::* At the begining there will be placed a short summary of the flight-conditions:<br />
::::{| class="wikitable" style="text-align:center"<br />
!Code<br />
!Meaning<br />
!Cloud Ceiling<br />
!Visibility<br />
|-<br />
|LIFR||Limited IFR||<500 ft|| visibility <1 nm<br />
|-<br />
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm<br />
|-<br />
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm<br />
|-<br />
|VFR||Visual Flight Rules||>3000 ft||>5 nm<br />
|}<br />
::* With a mouse-click on the upper line only that line will be sent to the target <br />
::* A mouse-click to the lower line will send both lines to the target<br />
<br />
====='''COM-Radios'''=====<br />
'''''if FGCOM'''''<br />
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]<br />
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may<br />
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field<br />
:*or empty the field by a right mouseclick and enter any other frequency wanted.<br />
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.<br />
::{| class="wikitable" style="text-align:center"<br />
!COMx<br />
!left on keyboard<br />
!right on keyboard<br />
|-<br />
|COM0||Ctrl||NumOff+Num0<br />
|-<br />
|COM1||SHIFT||NumOff+Num1<br />
|-<br />
|COM2|| ||NumOff+Num2<br />
|-<br />
|COM3|| ||NumOff+Num7<br />
|}<br />
:Please watch the color change of the PTT buttons to know, when you can speak. <br />
<br />
:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode <small>(compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]])</small>, then<br />
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)<br />
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.<br />
<br /><br />
'''''if e.g. MUMBLE'''''<br />
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:<br />
::: '''itpns.ddns.net'''<br />
<br />
====='''Runway Settings'''=====<br />
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]<br />
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]<br />
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:<br />
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':<br />
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings.<br />
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may <br />
:::'''not use''' runway 36 at all --> thus disable both lines: All data for that runway disappear<br />
:::'''use''' runway 18 for "Starts" only --> thus enable "Starts" only<br />
:::'''use''' runway 07L and 25R for "Landings" only --> thus enable only "Landing"<br />
:::<small>(Compare the picture "The Runway Manager" on the right: The left marks enable the function - the right ones enable the SID/STAR functions)<br />
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small><br />
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!<br />
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.<br />
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.<br />
<br><br />
Finally your picture will look similar to the right/above shown "The Runway Manager"!<br />
*In that one you see from left to right the following informations for each runway:<br />
:*The runway-name <br />
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)<br />
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>.<br />
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!<br />
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])</small><br />
:*To the right follows<br />
::*in the upper line the exact runway heading (as needed for older type autopilots)<br />
::*in the lower line the length and width of the runway in feet! <br />
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.<br />
<br />
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways.<br />
<br />
====='''Flight Strip Manager'''=====<br />
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]<br />
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:<br />
:{| class="wikitable" style="text-align:center"<br />
|-<br />
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC<br />
|-<br />
|distance to it||IAS+GND speed||Altitude (FL)||current heading<br />
|}<br />
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data <small>''(see ../OpenRadar/Settings/atcComments.xml)''</small> and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:<br />
:"ILS VOR FGC NRW || and personal remark"<br />
:<small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark</small> <br />
<br />
You are absolutely free to define your own codes and whatever. To do so:<br />
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''<small>(Mac: Alt + right mouse-click)</small>'' onto the stripe. There you have several areas to add unique informations: <br />
:* At the top of this editor you can<br />
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target<br />
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''<br />
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints. <br />
:<small>''The above data may be distributed to all ATC's.''</small><br />
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.<br />
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]<br />
* exit the Flight-Stripe-Editor clicking into any area outside of it.<br />
<br><br />
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:<br />
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)<br />
* You can move the stripes in vertical order by drag and drop<br />
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''<br />
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!<br />
* The radar-targets will change their color according to the horizontal position of their stripe:<br />
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them<br />
** the radar-targets for stripes in the center will be '''yellow'''<br />
** the radar-targets for stripes at the left side will be '''cyan'''<br />
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!<br />
<br />
You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:<br />
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)<br />
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.<br />
:'''''cyan''''' = left = under my control.<br />
Again: That is a proposal - you can define your on meanings!<br />
<br />
You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:<br />
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition<br />
**its listed messages in the MPchat-list become colored cyan<br />
**<span style="background: lightblue;">and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer<br />
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!</span><br />
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)<br />
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact<br />
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.<br />
<br />
=='''''Flight-Plan & Flight-Management'''''==<br />
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!<br />
<br /><br /><br />
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".<br />
<br />
==='''Define/Edit a Flight-Plan:'''===<br />
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]<br />
<br />
You open the Flight-Plan for a target by clicking with the “center mouse-button”<br />
*onto the Flight-Strip of the target<br />
*or the target on the radar-screen<br />
*You can also open the "active" target by the '''^'''-key<br />
<br />
'''Before''' you start defining a new plan <br />
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system<br />
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"<br />
<br />
'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server<br />
<br />
'''Controlling the ownership:'''<br><br />
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field<br />
“Controlled/Uncontrolled" must state “controlled by me”!<br />
<br />
* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change<br />
<br />
*If it is “'''Controlled by …..'''”<br />
**you must wait till the ATC controlling it now will<br />
***either remove his “ownership” by <br />
****clicking onto “Handover to” and selecting <br />
*****another ATC for takeover <br />
*****or the “blank” for just removing his control. <br />
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")<br />
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically<br />
**or you send the controlling ATC a mail asking him to release the target<br />
<br />
*If it shows “'''Controlled by me'''” you can release the target<br />
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover <br />
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)<br />
**or you move the Flight-Strip all the way to the right – that will just remove your ownership <br />
<br />
'''Mandatory fields of the OR-Flight-Plan:'''<br />
*'''Contact''' is the FGFS-UID of the target (will be set automatically)<br />
*'''Radio''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> to indicate that the target can use Radio (FGCom or Mumble or ..)<br />
*'''Aircraft''' is the model-code of the target (will be set automatically)<br />
*'''Assgnd RWY''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”<br />
*'''SID/STAR''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the name of the SID/STAR, if requested by the pilot<br />
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)<br />
*'''Destination''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the ICAO-code of the destination (e.g. EDDF for Frankfurt)<br />
*'''Crsg Alt''' <span style="font-weight: bold; font-style: italic; color: rgb(255,0,0)">needs</span> the planned (initial) cruising altitude for that flight (usually in FL)<br />
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)<br />
<br />
'''Optional fields of the OR-Flight-Plan:'''<br />
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” <br />
*'''Squawk''' shows the Squawk-Code you assigned to the target <small>(for details see [[Transponder]])</small><br />
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)<br />
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))<br />
*'''Code''' will be used in future when given by a more professional Flight-Planning system<br />
*'''IFR/VFR''' may be defined by the PullDown<br />
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)<br />
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport <br />
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route<br />
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.<br />
<br />
==='''Flight-management:'''===<br />
Open the wanted Flight-Plan<br />
* by a center-mouse-click onto the radar-target or the FlightStrip<br />
* you can also use the '''^'''-key to open the FlightPlan of the active target. <br />
Then continue as described in the following scenarios:<br />
<small>''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''</small><br />
<br />
'''''1. A target appears on your airport'''''<br />
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]<br />
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus<br />
:*the text in the tag-color is “green” - i.e. you did not yet take control<br />
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it<br />
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).<br />
<br />
'''''2. You define a new Flight Plan'''''<br />
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''<br />
*'''Generate the Flight-Plan:''' <br />
:Compare the Informations given in the target-label and the stripe:<br />
::<small>''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''</small><br />
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]<br />
::{| class="wikitable"<br />
|-<br />
|jomo<br />
|the pilot FGFS-UID<br />
|-<br />
|160°<br />
|the current heading (now on ramp!)<br />
|-<br />
|HeadSet-sign<br />
|that pilot uses radio (FGCom or Mumble)<br />
|-<br />
|CONC<br />
|the FGFS-model is the Concorde<br />
|-<br />
|KJFK<br />
|is the planned destination<br />
|-<br />
|260°<br />
|is the straight heading EDDF<small> (departure)</small> to KJFK<small> (destination)</small><br />
|-<br />
|BIBTI<br />
|is the SID planned for departure (on arrival here would be the STAR)<br />
|-<br />
|RW25C<br />
|is the runway assigned for departure (or for arrival)<br />
|-<br />
|0400*<br />
|is the current altitude (on GND in EDDF!)<br />
|-<br />
|00<br />
|is the speed (still parking!)<br />
|}<br />
<br><br />
*'''Departing:'''<br />
**GND will use the data as shown above, to bring the plane to the HoldingPoint<br />
**TWR will take over <br />
**The runway-assignment will be removed automatically after Take-Off<br />
<br><br />
*'''Transfer Control to next ATC (or blank) '''<br />
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]<br />
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.<br />
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.<br />
*the FlightStrip will indicate the pending transfer by showing <br />
:::“current ATC” => “next ATC”<br />
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!<br />
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!<br />
<br />
'''''3. A target appears in your airspace:'''''<br />
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if<br />
:* there is no ATC assigned yet<br />
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' <small>''(see above “current ATC” => “next ATC” indication)''</small><br />
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.<br />
* If the target lands on your airport:<br />
** assign a RW and optional a STAR <br />
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''<br />
<br />
'''''4. A ATC forgets to “reassign” or “free” a target:'''''<br />
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.<br />
* or you contact that ATC and require to release that target out of his control<br />
<br><br />
==='''Summery of Flight-Strips and Target-Tags'''===<br />
Depending on what you selected in "map" -> "data mode" ''<small>(see the menu above the MPchat entry-line, at the very left)</small>'' the Radar labels may look different. See the summary in the following table:<br />
{| class="wikitable"<br />
|+<br />
!width="30%"|<small>Status</small><br />
!width="30%"|<small>FlightStrip</small><br />
!width="20%"|<small>Traditional<br />
(no transponder interaction)</small><br />
!width="20%"|<small>Simulation<br />
(Transponder enabled)</small><br />
!width="20%"|<small>Pure Simulation<br />
(Transponder enforced)</small><br />
|-<br />
|<small>'''''Target appears on EDDF airport:'''''<br />
no ATC and no Flight-Data are assigned yet</small><br />
|align="center"|[[File:OpenRadar-target-lables-10.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-11.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-12.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-13.png]]<br />
|-<br />
|<small>'''''jomoATC inputs a Flightplan:'''''<br />
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250<br />
Rw for TakeOff 25C</small><br />
|align="center"|[[File:OpenRadar-target-lables-20.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-21.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-22.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-23.png]]<br />
|-<br />
|<small>'''''After TakeOff:'''''<br />
notice that RW25C has been canceled</small><br />
|align="center"|[[File:OpenRadar-target-lables-30.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-31.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-32.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-33.png]]<br />
|}<br />
<small>'''''EDDF forwards the target to EDDK:'''''</small><br />
{| class="wikitable"<br />
|-<br />
|<small>'''in EDDK''' it appears with a yellow background to enforce attantion<br />
after ATC-EDDK has taken over, that yellow will disappear <br />
and the "lastATC ==> "newATC" will be replaced by "currentATC"<br />
and the "private Notes" will be replaced with those of the newATC (if he has some)</small><br />
|align="center"|[[File:OpenRadar-target-lables-41.png]]<br />
|-<br />
|<small>'''in EDDF''' that private notes remain,<br />
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”</small><br />
|align="center"|[[File:OpenRadar-target-lables-42.png]]<br />
|align="center"|[[File:OpenRadar-target-lables-43.png]]<br />
|}<br />
<br />
== '''''Functional Keys''''' ==<br />
'''Radar Map'''<br />
* On contact<br />
:* '''left''' click '''selects''' and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click opens the '''ATC messages''' selection box<br />
<br />
* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)<br />
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)<br />
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...<br />
<br />
'''Flight Strip Area'''<br />
* On flight strip<br />
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field<br />
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)<br />
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box<br /><br />
<br />
:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)<br />
:* '''CTRL+left''' click sets the contact to be '''neglected'''<br />
<br />
* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)<br />
<br />
'''Runway area'''<br />
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings<br />
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)<br />
<br />
'''Radios'''<br />
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself<br />
<br />
<br />
''' Shortcuts '''<br />
{| class="keytable"<br />
|-<br />
! Shortcut !! Action<br />
|-<br />
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)<br />
<br />
|-<br />
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact<br />
<br />
|-<br />
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)<br />
<br />
|-<br />
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)<br />
|-<br />
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)<br />
|-<br />
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)<br />
|-<br />
| {{key press|F1}} || Zoom Level GROUND<br />
|-<br />
| {{key press|F2}} || Zoom Level TOWER<br />
|-<br />
| {{key press|F3}} || Zoom Level APP<br />
|-<br />
| {{key press|F4}} || Zoom Level SECTOR<br />
|-<br />
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)<br />
|-<br />
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)<br />
|-<br />
| {{key press|Shift|F12}} || Reload and update standard route<br />
definitions and texts (for development)<br />
|}<br />
<br />
== Related content ==<br />
* [[sourceforge.net/projects/openradar/files|'''Download''' OpenRadar]]<br />
* [[OpenRadar_FGFS_ORCAM|'''ORCAM''' = View the targets as model]]<br />
* [[OpenRadar:_Transponder|Using '''Transponder'''-Codes]]<br />
* [[OpenRadar: Editing routes|Editing '''STAR/SID''' routes]]<br />
* [[OpenRadar:_Flightstrip|'''Flightstrips''']]<br />
* [[OpenRadar:_Flightstrips-Bay|'''Flightstrips-Bay''']]<br />
* [[OpenRadar:_Chat_aliases|'''Chat_aliases''']]<br />
* [[OpenRadarKnownIssues|FAQ / Known Issues]]<br />
* [[OpenRadar|The Design-Rules for OpenRadar]]<br />
* [[OpenRadarFeatureWishlist|OpenRadarFeatureWishlist]]<br />
[[Category:OpenRadar|Guide]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=Zeppelin_LZ_121_Nordstern&diff=119187Zeppelin LZ 121 Nordstern2019-06-24T14:18:35Z<p>Inetuka: </p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
<br />
''Nordstern'' was the second of two small passenger airships built by Luftschiffbau Zeppelin in 1919 and 1920. ''Nordstern'' was designed to carry about 25 passengers on a Friedrichshafen - Berlin - Stockholm route but this route was never opened. The older sister ship LZ 120 ''Bodensee'' did run a regular passenger service between Friedrichshafen and Berlin during autumn 1919. In compliance with the terms of the peace treaty after WW I both airships were grounded early in 1920. ''Nordstern'' was handed over to France in 1921 where she remained in (sparse) service with the french military until 1926 under the name ''Méditerranée''. ''Bodensee'' was handed over to Italy and remained in service there until 1928 under the name ''Esperia''.<br />
<br />
== Important controls / keys ==<br />
<br />
=== Aerodynamic flight controls ===<br />
<br />
* Rudder<br />
* Elevator<br />
<br />
In the most recent versions (FlightGear release 2016.3.1 and higher) there is a hidden crew "autopilot" system providing a virtual helmsman and elevator man. It can be activated by setting the properties<br />
/fdm/jsbsim/crew/helmsman/enabled<br />
/fdm/jsbsim/crew/elevatorman/enabled<br />
to 1 (e.g. using the property browser). The helmsman is directed by the heading bug on the magnetic compass while the target altitude for the elevator man is set by the property<br />
/fdm/jsbsim/crew/elevatorman/altitude-cmd-ft<br />
<br />
Currently both channels use true references to guide their control rather than those provided by the aircraft instrumentation.<br />
<br />
=== Engine controls ===<br />
<br />
The side engines (engine 0 and 1) can be reversed by stopping the engine and starting it in the other direction.<br />
<br />
* R - Switch the running direction for the selected engine(s). The engine(s) have to be stopped before switching direction.<br />
* Shift+1 - Select the port side engine (engine 0).<br />
* Shift+2 - Select the starboard side engine (engine 1).<br />
* ~ - Select all engines.<br />
<br />
The engines are Maybach MB IVa high altitude engines that can easily be oversped on lower altitudes due to their construction - their rated output of 245 hp @ 1400 RPM is reached well before the throttle is fully open up to an altitude of 1800 m. At emergency power engine speed may go up to 1460 RPM.<br />
<br />
=== Gas valve controls ===<br />
<br />
* F/f - Open/close the gas valves of the fore gas cells.<br />
* G/g - Open/close the gas valves of the aft gas cells.<br />
<br />
Rigid airships like ''Nordstern'' take-off light in a static maneuver and normally land in balance to slightly heavy in a static maneuver. The primary use for the gas valves is to reduce static lightness when needed.<br />
<br />
=== Ballast controls ===<br />
<br />
* w - Show current on-ground weight. Only works when on the ground.<br />
* W - Weigh off to neutral by adding/removing ballast. Takes about 10 seconds and is only applicable when on the ground.<br />
* e/d - Shift trim ballast fore/aft.<br />
* E/D - Drop one quick-release (a.k.a. emergency) ballast bag fore/aft. There are 6 bags fore and 4 aft.<br />
* Ctrl+W - Refill the quick-release ballast bags from the trim ballast.<br />
<br />
Use the "Fuel and payload" dialog to replenish the ballast tanks. Realistically this can only be done while moored.<br />
<br />
[[File:Nordstern-elevator-station.jpg|thumb|600px|center|''Nordstern'''s elevator control station. The black toggles release emergency ballast, while the red toggles control the maneuvering gas valves. Below are the pitch inclinometers, the altimeter and, to the right, the variometer.]]<br />
<br />
=== Ground crew / Mooring mast ===<br />
<br />
* Y - Release mooring mast connection or wire.<br />
* U - Attach mooring wire. Only possible when close to a mooring mast.<br />
* y/u - Play out/winch in mooring wire.<br />
* Alt + click on terrain - Place the mooring mast.<br />
<br />
The real ''Nordstern'' never used a mooring mast. All ground handling was done manually with the ground crew manning yaw lines fore and aft and, once within reach, holding on to the handling rails on the control car and the aft engine car.<br />
<br />
<br />
[[File:Nordstern.jpg|thumb|600px|center|The control car of ''Nordstern''.]]<br />
<br />
<br />
[[File:Nordstern-interior.jpg|thumb|600px|center|The interior of ''Nordstern'''s control car.]]<br />
<br />
== Installation and Dependencies ==<br />
<br />
* LZ 121 Nordstern (Development version for [http://github.com/andgi/FlightGear-Nordstern FG/git], click "Download ZIP".)<br />
<br />
This aircraft depends on instruments from some other aircraft. Install a matching version of these too.<br />
<br />
* [[Superwal]]<br />
* [[ZLT-NT]]<br />
<br />
== Known problems ==<br />
<br />
* The anachronistic mast truck is invisible in 2.10.0. The problem has been fixed in subsequent versions of FlightGear.<br />
<br />
* Under some conditions at low or negative airspeed the airship can suffer from undamped yaw oscillations. This seems to be an interaction between the added mass simulation and the dynamic aerodynamic coefficients. (old)<br />
<br />
* Real weather fetch sometimes cause NaN problems.<br />
<br />
* Before FlightGear 2016.1.1 the mooring force calculations were sensitive to long frame times (i.e. very low fps), which could cause FlightGear to crash during startup or make the airship start in a bad state.<br />
'''Workaround''': Try setting /sim/max-simtime-per-frame to 0.1 seconds or less. This can be done in preferences.xml by modifying the line<br />
<max-simtime-per-frame>1.0</max-simtime-per-frame><br />
to<br />
<max-simtime-per-frame>0.1</max-simtime-per-frame><br />
<br />
== External links ==<br />
<br />
* [http://www.gidenstam.org/FlightGear/Airships/ Download page with other lighter-than-air aircraft for FlightGear.] Requires the LTA support available in FlightGear 1.9.0 or later. '''Note: The most up to date version of the Zeppelin LZ 121 Nordstern is available in FlightGear/git.'''<br />
<br />
{{Aerostat}}<br />
<br />
[[Category:Historical aircraft]]<br />
[[Category:Airships]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=Zeppelin_LZ_121_Nordstern&diff=119186Zeppelin LZ 121 Nordstern2019-06-24T14:17:19Z<p>Inetuka: </p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
<br />
''Nordstern'' was the second of two small passenger airships built by Luftschiffsbau Zeppelin in 1919 and 1920. ''Nordstern'' was designed to carry about 25 passengers on a Friedrichshafen - Berlin - Stockholm route but this route was never opened. The older sister ship LZ 120 ''Bodensee'' did run a regular passenger service between Friedrichshafen and Berlin during autumn 1919. In compliance with the terms of the peace treaty after WW I both airships were grounded early in 1920. ''Nordstern'' was handed over to France in 1921 where she remained in (sparse) service with the french military until 1926 under the name ''Méditerranée''. ''Bodensee'' was handed over to Italy and remained in service there until 1928 under the name ''Esperia''.<br />
<br />
== Important controls / keys ==<br />
<br />
=== Aerodynamic flight controls ===<br />
<br />
* Rudder<br />
* Elevator<br />
<br />
In the most recent versions (FlightGear release 2016.3.1 and higher) there is a hidden crew "autopilot" system providing a virtual helmsman and elevator man. It can be activated by setting the properties<br />
/fdm/jsbsim/crew/helmsman/enabled<br />
/fdm/jsbsim/crew/elevatorman/enabled<br />
to 1 (e.g. using the property browser). The helmsman is directed by the heading bug on the magnetic compass while the target altitude for the elevator man is set by the property<br />
/fdm/jsbsim/crew/elevatorman/altitude-cmd-ft<br />
<br />
Currently both channels use true references to guide their control rather than those provided by the aircraft instrumentation.<br />
<br />
=== Engine controls ===<br />
<br />
The side engines (engine 0 and 1) can be reversed by stopping the engine and starting it in the other direction.<br />
<br />
* R - Switch the running direction for the selected engine(s). The engine(s) have to be stopped before switching direction.<br />
* Shift+1 - Select the port side engine (engine 0).<br />
* Shift+2 - Select the starboard side engine (engine 1).<br />
* ~ - Select all engines.<br />
<br />
The engines are Maybach MB IVa high altitude engines that can easily be oversped on lower altitudes due to their construction - their rated output of 245 hp @ 1400 RPM is reached well before the throttle is fully open up to an altitude of 1800 m. At emergency power engine speed may go up to 1460 RPM.<br />
<br />
=== Gas valve controls ===<br />
<br />
* F/f - Open/close the gas valves of the fore gas cells.<br />
* G/g - Open/close the gas valves of the aft gas cells.<br />
<br />
Rigid airships like ''Nordstern'' take-off light in a static maneuver and normally land in balance to slightly heavy in a static maneuver. The primary use for the gas valves is to reduce static lightness when needed.<br />
<br />
=== Ballast controls ===<br />
<br />
* w - Show current on-ground weight. Only works when on the ground.<br />
* W - Weigh off to neutral by adding/removing ballast. Takes about 10 seconds and is only applicable when on the ground.<br />
* e/d - Shift trim ballast fore/aft.<br />
* E/D - Drop one quick-release (a.k.a. emergency) ballast bag fore/aft. There are 6 bags fore and 4 aft.<br />
* Ctrl+W - Refill the quick-release ballast bags from the trim ballast.<br />
<br />
Use the "Fuel and payload" dialog to replenish the ballast tanks. Realistically this can only be done while moored.<br />
<br />
[[File:Nordstern-elevator-station.jpg|thumb|600px|center|''Nordstern'''s elevator control station. The black toggles release emergency ballast, while the red toggles control the maneuvering gas valves. Below are the pitch inclinometers, the altimeter and, to the right, the variometer.]]<br />
<br />
=== Ground crew / Mooring mast ===<br />
<br />
* Y - Release mooring mast connection or wire.<br />
* U - Attach mooring wire. Only possible when close to a mooring mast.<br />
* y/u - Play out/winch in mooring wire.<br />
* Alt + click on terrain - Place the mooring mast.<br />
<br />
The real ''Nordstern'' never used a mooring mast. All ground handling was done manually with the ground crew manning yaw lines fore and aft and, once within reach, holding on to the handling rails on the control car and the aft engine car.<br />
<br />
<br />
[[File:Nordstern.jpg|thumb|600px|center|The control car of ''Nordstern''.]]<br />
<br />
<br />
[[File:Nordstern-interior.jpg|thumb|600px|center|The interior of ''Nordstern'''s control car.]]<br />
<br />
== Installation and Dependencies ==<br />
<br />
* LZ 121 Nordstern (Development version for [http://github.com/andgi/FlightGear-Nordstern FG/git], click "Download ZIP".)<br />
<br />
This aircraft depends on instruments from some other aircraft. Install a matching version of these too.<br />
<br />
* [[Superwal]]<br />
* [[ZLT-NT]]<br />
<br />
== Known problems ==<br />
<br />
* The anachronistic mast truck is invisible in 2.10.0. The problem has been fixed in subsequent versions of FlightGear.<br />
<br />
* Under some conditions at low or negative airspeed the airship can suffer from undamped yaw oscillations. This seems to be an interaction between the added mass simulation and the dynamic aerodynamic coefficients. (old)<br />
<br />
* Real weather fetch sometimes cause NaN problems.<br />
<br />
* Before FlightGear 2016.1.1 the mooring force calculations were sensitive to long frame times (i.e. very low fps), which could cause FlightGear to crash during startup or make the airship start in a bad state.<br />
'''Workaround''': Try setting /sim/max-simtime-per-frame to 0.1 seconds or less. This can be done in preferences.xml by modifying the line<br />
<max-simtime-per-frame>1.0</max-simtime-per-frame><br />
to<br />
<max-simtime-per-frame>0.1</max-simtime-per-frame><br />
<br />
== External links ==<br />
<br />
* [http://www.gidenstam.org/FlightGear/Airships/ Download page with other lighter-than-air aircraft for FlightGear.] Requires the LTA support available in FlightGear 1.9.0 or later. '''Note: The most up to date version of the Zeppelin LZ 121 Nordstern is available in FlightGear/git.'''<br />
<br />
{{Aerostat}}<br />
<br />
[[Category:Historical aircraft]]<br />
[[Category:Airships]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=List_of_developed_airports&diff=117350List of developed airports2019-02-11T09:45:37Z<p>Inetuka: </p>
<hr />
<div>This is an incomplete '''list of developed airports''' in the FlightGear [[TerraSync]] scenery.<br />
<br />
Airports can be listed here if these two conditions are fulfilled:<br />
* At least one building or [[Signs|taxi signs]] have been placed<br />
* Objects are represented in the [[FlightGear Scenery Database]].<br />
<br />
Every improvement listed here should be possible to download using TerraSync. These improvements will also be included in the next [[World Scenery]] release.<br />
<br />
A visual representation of the developed airports in FlightGear can be found at [http://www.iveze.nl/fgmap/ iveze.nl/fgmap/].<br />
<br />
__TOC__<br />
<br />
== For airport developers ==<br />
If you are currently developing an airport, please feel free to add it to [[Airports under construction]]. For a list of currently ongoing scenery related projects, please check out [[Current Scenery Projects]].<br />
<br />
== List of airports ==<br />
The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the [[FlightGear Scenery Database]]. On a map, you will see:<br />
* The current airport layout with runways, taxiways and aprons<br />
* Red dots: static objects in the scenery database made especially for this airport<br />
* Dark red dots: shared models in the scenery database placed at this airport<br />
* Green dots: [[Signs|taxi signs]] placed at the airport<br />
<br />
{{inote|You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.}}<br />
<br />
{| class="wikitable sortable" border="0" cellspacing="0" <br />
|-<br />
! ICAO !! Name !! Country !! Continent !! class="unsortable" | Comment<br />
<br />
|-<br />
| CYGK || [[Kingston Norman Rogers]] || Canada || North America || Custom objects for all major buildings, including public terminal. (Buildings may not align with taxiways in default scenery, until it starts using the newest recommended airport data from X-Plane.)<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 EDDC] || [[Dresden Airport]] || Germany || Europe || Fully modeled with tower, terminal, animated hangars etc.<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=8.56293&lat=50.03795&z=13 EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique skyscrapers downtown<br />
<br />
|-<br />
| ED03 || Pohlheim Viehheide || Germany || Europe || Tower and buildings. Gliders often start from here. <br />
<br />
|-<br />
| EDDG || [[Münster Osnabrück]] || Germany || Europe || 1 static + 100 shared objects<br />
<br />
|-<br />
| EDDH || [[Hamburg Airport]] || Germany || Europe || Fully modeled, plus unique buildings downtown<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=13.40379&lat=52.47502&z=13 EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled<br />
<br />
|-<br />
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Fully modeled, many shared objects<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=11.78609&lat=48.35378&z=13 EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=12.23603&lat=51.42262&z=13 EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]<br />
<br />
|-<br />
| EDDS || [[Stuttgart Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]<br />
<br />
|-<br />
| EDDW || Bremen Airport || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=13.28992&lat=52.55917&z=13 EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown<br />
<br />
|-<br />
| EDFB || Reichelsheim Airport || Germany || Europe || Tower and buildings done<br />
<br />
|-<br />
| EDFE || Frankfurt Egelsbach || Germany || Europe || Tower,buildings,shared-models and incl. [[Signs]]<br />
<br />
|-<br />
| EDFM || [[Mannheim City Airport]] || Germany || Europe || Basic models of tower, terminals and hangars<br />
<br />
|-<br />
| EDFO || Michelstadt Odenwald || Germany || Europe || Tower and buildings done<br />
<br />
|-<br />
| EDFQ || Allendorf-Eder || Germany || Europe || Tower and buildings done<br />
<br />
|-<br />
| EDGS || Siegerland Airport || Germany || Europe || Tower,buildings,shared-models and signs done<br />
<br />
|-<br />
| EDXW || [[Sylt Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=10.71706&lat=53.80496&z=13 EDHL] || [[Lübeck Blankensee Airport]] || Germany || Europe || Almost complete, home of the [[Piper PA34-200T Seneca II|Seneca]] used to model the FlightGear version. A modified tile is available at [http://www.t3r.de/fg/scenery/ Torsten's scenery site]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=7.16278&lat=50.76767&z=13 EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe || <br />
<br />
|-<br />
| EDLW || [[Flughafen Dortmund]] || Germany || Europe || Fully modelled<br />
<br />
|-<br />
| EDVE || [[Braunschweig Airport]] || Germany || Europe || Fully modelled<br />
<br />
|-<br />
| EEKE || Kuressaare Airport || Estonia || Europe || <br />
<br />
|-<br />
| EETN || Lennart Meri Tallinn Airport || Estonia || Europe || <br />
<br />
|-<br />
| EETU || Tartu Airport || Estonia || Europe || <br />
<br />
|-<br />
| EBBR || Brussels Airport || Belgium || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=25.04487&lat=60.25318&z=13 EFHF] || Helsinki-Malmi Airport || Finland || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=24.95253&lat=60.3206&z=13 EFHK] || Helsinki-Vantaa Airport || Finland || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=22.26281&lat=60.51412&z=13 EFTU] || Turku Airport || Finland || Europe || Tower and terminal modelled<br />
<br />
|-<br />
| EGFF || Cardiff Airport || United Kingdom || Europe || One building: British Airways Maintenance Facility<br />
<br />
|-<br />
| EGGP || Liverpool John Lennon Airport || United Kingdom || Europe || <br />
<br />
|-<br />
| EGGW || London Luton Airport || United Kingdom || Europe || <br />
<br />
|-<br />
| EGKA || Shoreham Airport || United Kingdom || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-0.19224&lat=51.14869&z=13 EGKK] || [[London Gatwick]] || United Kingdom || Europe || Complete and fully modeled to highest level of detail with day and night textures; AI parking and ground network<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-0.46095&lat=51.47139&z=13 EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only<br />
<br />
|-<br />
| EGPH || Edinburgh Airport || United Kingdom || Europe || Tower, terminal, park deck, and some shared models<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=1.28469&lat=52.67713&z=13 EGSH] || Norwich Airport || United Kingdom || Europe || <br />
<br />
|-<br />
| EH01 || [[VU University Medical Center]] || Netherlands || Europe || Complete hospital building including on-roof heli platform.<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=4.75487&lat=52.31296&z=13 EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, busiest AI airport currently<br />
<br />
|-<br />
| EHEH || Eindhoven Airport || Netherlands || Europe || Basic development only<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=5.51885&lat=52.45717&z=13 EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled<br />
<br />
|-<br />
| EHVK || [[Volkel Air Base]] || Netherlands || Europe || Shelters and detailed airport layout.<br />
<br />
|-<br />
| EIDW || [[Dublin Airport]] || Ireland || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=6.11017&lat=62.56037&z=13 ENAL] || Ålesund Airport || Norway || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=6.10949&lat=61.83027&z=13 ENSD] || Sandane Airport || Norway || Europe || <br />
<br />
|-<br />
| ENVA || Trondheim Værnes Airport || Norway || Europe || <br />
<br />
|-<br />
| ESGP || Göteborg Airport || Sweden || Europe || Basic development only<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-106.60912&lat=35.04021&z=13 KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-84.42809&lat=33.63672&z=13 KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&z=13 KAKR] || [[Akron-Fulton International Airport]], OH || USA || America || Fully modelled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&z=13 KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled<br />
<br />
|-<br />
| KAUS || Austin-Bergstrom Airport, TX || USA || America || <br />
<br />
|-<br />
| KBOS || Boston Logan || USA || America || Fully modeled, plus unique buildings downtown <br />
<br />
|-<br />
| KFNT || Bishop Intl, MI || USA || America || Fully modelled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-76.66833&lat=39.17535&z=13 KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lat=37.9858289&lon=-122.05529346000002&z=15 KCCR] || Buchanan Field Airport, Concord, CA || USA || America || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-76.92254&lat=38.98062&z=13 KCGS] || College Park Airport, MD || USA || America || <br />
<br />
|-<br />
| KCVG || Cincinnati/Northern Kentucky International Airport, KY || USA || America || Terminals, Concourses, Towers, Signs, DHL Hub, and Other Buildings (Almost Fully Modeled)<br />
<br />
|-<br />
| KDCA || Reagan National Airport, VA || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-104.67318&lat=39.86166&z=13 KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled<br />
<br />
|-<br />
| KDTW || Detroit Metropolitan Wayne County Airport, MI || USA || America || Basic development only<br />
<br />
|-<br />
| KEQY || Charlotte-Monroe Executive Airport, NC || USA || America || Some buildings and aircraft using shared models<br />
<br />
|-<br />
| KFHR || Friday Harbor Airport, WA || USA || America || <br />
<br />
|-<br />
| KIND || Indianapolis Airport, IN || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-90.07589&lat=32.31118&z=13 KJAN] || Jackson-Evers Airport, MS || USA || America || <br />
<br />
|-<br />
| KJFK || [[John F. Kennedy International Airport]], NY || USA || America || <br />
<br />
|-<br />
| KLAS || Las Vegas McCarran Airport, NV || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-118.40809&lat=33.9425&z=13 KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled<br />
<br />
|-<br />
| KLSV || [[Nellis Air Force Base]], NV || USA || America || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-109.4667&lat=47.04924&z=13 KLWT] || Lewistown Municipal Airport, MT || USA || America || <br />
<br />
|-<br />
| KMCI || Kansas City Airport, MO || USA || America || Basic development only<br />
<br />
|-<br />
| KMPI || Mariposa-Yosemite Airport, CA || USA || America || Hangars and FBO.<br />
<br />
|-<br />
| KMTN || Martin State Airport, MD || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-117.69181&lat=35.68565&z=13 KNID] || China Lake Naval Air Weapons Station, CA || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-122.04918&lat=37.4162&z=13 KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-122.22062&lat=37.7214&z=13 KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance<br />
<br />
|-<br />
| KORD || Chicago [[O'Hare International Airport]], IL || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-88.55704&lat=43.98436&z=13 KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-75.12398&lat=38.31045&z=13 KOXB] || Ocean City Municipal Airport, MD || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-122.59751&lat=45.58871&z=13 KPDX] || Portland Airport, OR || USA || America || <br />
<br />
|-<br />
| KPHX || Phoenix Sky Harbor Airport, AZ || USA || America || <br />
<br />
|-<br />
| KRNO || Reno/Tahoe Airport, NV || USA || America || <br />
<br />
|-<br />
| KSEA || [[Seattle-Tacoma International Airport]], WA || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-122.3749&lat=37.61897&z=13 KSFO] || [[San Francisco International Airport]], CA || USA || America || FlightGear's default airport, terminal buildings, airport lights and airport train.<br />
<br />
|-<br />
| KSLC || Salt Lake City International Airport, UT || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lat=33.80112251&lon=-118.34134126&z=15 KTOA] || Zamperini Field, Torrance, CA || USA || America || Fully modeled<br />
<br />
|-<br />
| KXTA || Edwards Airforce Base Detachment 3 (Homey Airport, or Area 51), NV || USA || America || Fully modelled<br />
<br />
<br />
|-<br />
| KVUO || Pearson Field Airport, Vancouver, WA || USA || America || <br />
<br />
|-<br />
| LDSP || Split Airport || Croatia || Europe || Basic development only<br />
<br />
|-<br />
| LEBB || Bilbao || Spain || Europe || Fully modeled<br />
<br />
|-<br />
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.19889&lat=47.32611&z=13 LFEA] || Belle-Ile || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.10167&lat=47.48139&z=13 LFEQ] || Quiberon || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.66479&lat=48.05247&z=13 LFES] || Guiscriff Scaër || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.35465&lat=49.04626&z=13 LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=4.8264&lat=45.25226&z=13 LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=0.08816&lat=49.53404&z=13 LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=5.36736&lat=43.50499&z=13 LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.60632&lat=48.89629&z=13 LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.622793&lat=48.822237&z=13 LFPL] || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.359443&lat=48.72551&z=13 LFPO] || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.073197&lat=48.810622&z=13 LFPZ] || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-4.41785&lat=48.44413&z=13 LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-4.167981&lat=47.97553&z=13 LFRQ] || Quimper || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.816762&lat=48.601247&z=13 LFRU] || Morlaix || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-2.736754&lat=47.717558&z=13 LFRV] || Vannes || France || Europe || Airport fitted with shared models<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFRH] || Lorient - Bretagne Sud || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of terminal<br />
<br />
|-<br />
| LILN || Venegono Airport || Italy || Europe || Developed airport<br />
<br />
|-<br />
| LILQ || Massa Cinquale Airport || Italy || Europe || <br />
<br />
|-<br />
| LILV || Valbrembo Airport || Italy || Europe || <br />
<br />
|-<br />
| LIMC || Milano-Malpensa Airport || Italy || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=9.70741&lat=45.66952&z=13 LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=9.27521&lat=45.44776&z=13 LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=7.36789&lat=45.73857&z=13 LIMW] || Aosta Airport || Italy || Europe || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=14.26&lat=50.100833&z=13 LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled<br />
<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=11.34397&lat=47.26023&z=13 LOWI] || [[Innsbruck Airport]] || Austria || Europe || <br />
<br />
|-<br />
| LROP || Bucharest Otopeni || Romania || Europe || <br />
<br />
|-<br />
| LSGG || Geneve (Cointrin) Airport || Switzerland || Europe || Fully modelled. OSM2city available on https://github.com/FGMEMBERS-SCENERY/LSGG-fg-CustomScenery<br />
<br />
|-<br />
| LSGS || Sion Airport || Switzerland || Europe || Basic development only<br />
<br />
|-<br />
| LSZB || Bern-Belp Airport || Switzerland || Europe || Basic development only<br />
<br />
|-<br />
| PANC || Ted Stevens Anchorage International Airport || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=136.80541&lat=34.85841&z=13 RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=139.78114&lat=35.5533&z=13 RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=126.45051&lat=37.46909&z=13 RKSI] || Seoul Incheon Airport || South Korea || Asia || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=121.01349&lat=14.51024&z=13 RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals<br />
<br />
|-<br />
<br />
| SAEZ || Aeropuerto Internacional Ministro Pistarini || Argentina || America || Several static buildings<br />
<br />
|-<br />
<br />
| [[SVMI]] || Aeropuerto Internacional Simon Bolivar || Venezuela || America || Several static buildings<br />
<br />
|-<br />
<br />
| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America || <br />
<br />
|-<br />
| TDPD || Melville Hall Airport || Dominica || America || <br />
<br />
|-<br />
| TFFF || Martinique Aimé Césaire International Airport || Martinique, France || America || <br />
<br />
|-<br />
| TFFG || Grand Case Airport || St. Maarten, Netherlands || America || <br />
<br />
|-<br />
| TIST || Cyril E. King Airport || US Virgin Islands || America || <br />
<br />
|-<br />
| TJSJ || Luis Muñoz Marín International Airport || Puerto Rico || America || <br />
<br />
|-<br />
| TKPK || Robert L. Bradshaw International Airport || St. Kitts || America || <br />
<br />
|-<br />
| TNCM || [[Princess Juliana International Airport]] || St. Maarten, Netherlands || America || Fully modeled, customized terrain<br />
<br />
|-<br />
| TNCS || Juancho E. Yrausquin Airport || Saba || America || Fully modeled<br />
<br />
|-<br />
| TQPF || Clayton J. Lloyd International Airport || Anguilla || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-49.17201&lat=-25.53101&z=13 SBCT] || Afonso Pena International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-46.65768&lat=-23.62558&z=13 SBSP] || Congonhas Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-46.46864&lat=-23.43351&z=13 SBGR] || Guarulhos International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-48.54304&lat=-27.6685&z=13 SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]<br />
<br />
<br />
|-<br />
| SKRG || Jose Maria Cordoba International Airport, Rionegro, Antioquia || Colombia || South America || Fully modelled<br />
<br />
<br />
|-<br />
| VIDP || Indira Gandhi International Airport || India || Asia || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=89.42272&lat=27.39994&z=13 VQPR] || [[Paro Airport]] || Bhutan || Asia || Terminal, buildings, reference points and other POIs<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=91.50917&lat=27.25961&z=13 VQ10] || [[Yongphulla Airport]] || Bhutan || Asia || Terminal, some other buildings <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=113.9183&lat=22.308&z=13 VHHH] || Hong Kong International Airport || China || Asia || Terminals, control towers, some other buildings <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&z=13 1G3] || Kent State University Airfield, OH || USA || America || <br />
<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&z=13 1G5] || [[Medina Municipal Airport]], OH || USA || America || <br />
<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&z=13 29G] || Portage Co, OH || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-90.13769&lat=43.83872&z=13 82C] || Mauston-New Lisbon Union Airport, WI || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-89.02545&lat=44.50485&z=13 68C] || Iola Central County Airport, WI || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-123.00815977&lat=43.93009927&z=13 77S] || Hobby Field, Creswell, OR || USA || America || Nearly complete: Hangars (one accidently missing), fuel pump, GA aircraft, cars, trees, bushes (shared models)<br />
<br />
|}<br />
<br />
== Authors ==<br />
<br />
Airports by HerbyW in Yakutia, Irkutsk and Krasnoyarsk:<br />
UIBB UEEE UEST UEMS UEBN UEBT UEWD UEMA UERR UEMT UEEA UEMU UIII UITT UEBB UEVV UENW UEMO UERL UERT UEMH UERO UERP UNAA UIUN UENN UIBV UNCC UEMJ<br />
<br />
Airports by D-ABBA:<br />
EDXW,EDFE,EDGS,EDFQ,EDFH,EDFL,EDFO,ED03<br />
<br />
Airports by [[User:Laserman]]:<br />
EDDG,EDLM,EDLB,EDLK,EDLN,EDLV,EDLW,LJLJ,LJAJ,LJSG,LJCE,LJPZ <br />
<br />
<br />
== External links ==<br />
* [http://iveze.nl/fgmap/ Builtup airports in Flightgear] – Interactive world map by KL-666. ''See also related forum topic [http://forum.flightgear.org/viewtopic.php?f=5&t=23613 Map of airports with buildings in terrasync].''<br />
<br />
{{Suggested}}<br />
<br />
[[Category:Lists]]<br />
[[Category:Airports]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=List_of_developed_airports&diff=117349List of developed airports2019-02-11T09:11:38Z<p>Inetuka: </p>
<hr />
<div>This is an incomplete '''list of developed airports''' in the FlightGear [[TerraSync]] scenery.<br />
<br />
Airports can be listed here if these two conditions are fulfilled:<br />
* At least one building or [[Signs|taxi signs]] have been placed<br />
* Objects are represented in the [[FlightGear Scenery Database]].<br />
<br />
Every improvement listed here should be possible to download using TerraSync. These improvements will also be included in the next [[World Scenery]] release.<br />
<br />
A visual representation of the developed airports in FlightGear can be found at [http://www.iveze.nl/fgmap/ iveze.nl/fgmap/].<br />
<br />
__TOC__<br />
<br />
== For airport developers ==<br />
If you are currently developing an airport, please feel free to add it to [[Airports under construction]]. For a list of currently ongoing scenery related projects, please check out [[Current Scenery Projects]].<br />
<br />
== List of airports ==<br />
The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the [[FlightGear Scenery Database]]. On a map, you will see:<br />
* The current airport layout with runways, taxiways and aprons<br />
* Red dots: static objects in the scenery database made especially for this airport<br />
* Dark red dots: shared models in the scenery database placed at this airport<br />
* Green dots: [[Signs|taxi signs]] placed at the airport<br />
<br />
{{inote|You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.}}<br />
<br />
{| class="wikitable sortable" border="0" cellspacing="0" <br />
|-<br />
! ICAO !! Name !! Country !! Continent !! class="unsortable" | Comment<br />
<br />
|-<br />
| CYGK || [[Kingston Norman Rogers]] || Canada || North America || Custom objects for all major buildings, including public terminal. (Buildings may not align with taxiways in default scenery, until it starts using the newest recommended airport data from X-Plane.)<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 EDDC] || [[Dresden Airport]] || Germany || Europe || Fully modeled with tower, terminal, animated hangars etc.<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=8.56293&lat=50.03795&z=13 EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique skyscrapers downtown<br />
<br />
|-<br />
| ED03 || Pohlheim Viehheide || Germany || Europe || Tower and buildings. Gliders often start from here. <br />
<br />
|-<br />
| EDDG || [[Münster Osnabrück]] || Germany || Europe || 1 static + 100 shared objects<br />
<br />
|-<br />
| EDDH || [[Hamburg Airport]] || Germany || Europe || Fully modeled, plus unique buildings downtown<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=13.40379&lat=52.47502&z=13 EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled<br />
<br />
|-<br />
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Fully modeled, many shared objects<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=11.78609&lat=48.35378&z=13 EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=12.23603&lat=51.42262&z=13 EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]<br />
<br />
|-<br />
| EDDS || [[Stuttgart Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]<br />
<br />
|-<br />
| EDDW || Bremen Airport || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=13.28992&lat=52.55917&z=13 EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown<br />
<br />
|-<br />
| EDFB || Reichelsheim Airport || Germany || Europe || Tower and buildings done<br />
<br />
|-<br />
| EDFE || Frankfurt Egelsbach || Germany || Europe || Tower,buildings,shared-models and incl. [[Signs]]<br />
<br />
|-<br />
| EDFM || [[Mannheim City Airport]] || Germany || Europe || Basic models of tower, terminals and hangars<br />
<br />
|-<br />
| EDFO || Michelstadt Odenwald || Germany || Europe || Tower and buildings done<br />
<br />
|-<br />
| EDFQ || Allendorf-Eder || Germany || Europe || Tower and buildings done<br />
<br />
|-<br />
| EDGS || Siegerland Airport || Germany || Europe || Tower,buildings,shared-models and signs done<br />
<br />
|-<br />
| EDXW || [[Sylt Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=10.71706&lat=53.80496&z=13 EDHL] || [[Lübeck Blankensee Airport]] || Germany || Europe || Almost complete, home of the [[Piper PA34-200T Seneca II|Seneca]] used to model the FlightGear version. A modified tile is available at [http://www.t3r.de/fg/scenery/ Torsten's scenery site]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=7.16278&lat=50.76767&z=13 EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe || <br />
<br />
|-<br />
| EDLW || [[Flughafen Dortmund]] || Germany || Europe || Fully modelled<br />
<br />
|-<br />
| EDVE || [[Braunschweig Airport]] || Germany || Europe || Fully modelled<br />
<br />
|-<br />
| EEKE || Kuressaare Airport || Estonia || Europe || <br />
<br />
|-<br />
| EETN || Lennart Meri Tallinn Airport || Estonia || Europe || <br />
<br />
|-<br />
| EETU || Tartu Airport || Estonia || Europe || <br />
<br />
|-<br />
| EBBR || Brussels Airport || Belgium || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=25.04487&lat=60.25318&z=13 EFHF] || Helsinki-Malmi Airport || Finland || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=24.95253&lat=60.3206&z=13 EFHK] || Helsinki-Vantaa Airport || Finland || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=22.26281&lat=60.51412&z=13 EFTU] || Turku Airport || Finland || Europe || Tower and terminal modelled<br />
<br />
|-<br />
| EGFF || Cardiff Airport || United Kingdom || Europe || One building: British Airways Maintenance Facility<br />
<br />
|-<br />
| EGGP || Liverpool John Lennon Airport || United Kingdom || Europe || <br />
<br />
|-<br />
| EGGW || London Luton Airport || United Kingdom || Europe || <br />
<br />
|-<br />
| EGKA || Shoreham Airport || United Kingdom || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-0.19224&lat=51.14869&z=13 EGKK] || [[London Gatwick]] || United Kingdom || Europe || Complete and fully modeled to highest level of detail with day and night textures; AI parking and ground network<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-0.46095&lat=51.47139&z=13 EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only<br />
<br />
|-<br />
| EGPH || Edinburgh Airport || United Kingdom || Europe || Tower, terminal, park deck, and some shared models<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=1.28469&lat=52.67713&z=13 EGSH] || Norwich Airport || United Kingdom || Europe || <br />
<br />
|-<br />
| EH01 || [[VU University Medical Center]] || Netherlands || Europe || Complete hospital building including on-roof heli platform.<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=4.75487&lat=52.31296&z=13 EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, busiest AI airport currently<br />
<br />
|-<br />
| EHEH || Eindhoven Airport || Netherlands || Europe || Basic development only<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=5.51885&lat=52.45717&z=13 EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled<br />
<br />
|-<br />
| EHVK || [[Volkel Air Base]] || Netherlands || Europe || Shelters and detailed airport layout.<br />
<br />
|-<br />
| EIDW || [[Dublin Airport]] || Ireland || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=6.11017&lat=62.56037&z=13 ENAL] || Ålesund Airport || Norway || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=6.10949&lat=61.83027&z=13 ENSD] || Sandane Airport || Norway || Europe || <br />
<br />
|-<br />
| ENVA || Trondheim Værnes Airport || Norway || Europe || <br />
<br />
|-<br />
| ESGP || Göteborg Airport || Sweden || Europe || Basic development only<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-106.60912&lat=35.04021&z=13 KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-84.42809&lat=33.63672&z=13 KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&z=13 KAKR] || [[Akron-Fulton International Airport]], OH || USA || America || Fully modelled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&z=13 KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled<br />
<br />
|-<br />
| KAUS || Austin-Bergstrom Airport, TX || USA || America || <br />
<br />
|-<br />
| KBOS || Boston Logan || USA || America || Fully modeled, plus unique buildings downtown <br />
<br />
|-<br />
| KFNT || Bishop Intl, MI || USA || America || Fully modelled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-76.66833&lat=39.17535&z=13 KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lat=37.9858289&lon=-122.05529346000002&z=15 KCCR] || Buchanan Field Airport, Concord, CA || USA || America || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-76.92254&lat=38.98062&z=13 KCGS] || College Park Airport, MD || USA || America || <br />
<br />
|-<br />
| KCVG || Cincinnati/Northern Kentucky International Airport, KY || USA || America || Terminals, Concourses, Towers, Signs, DHL Hub, and Other Buildings (Almost Fully Modeled)<br />
<br />
|-<br />
| KDCA || Reagan National Airport, VA || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-104.67318&lat=39.86166&z=13 KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled<br />
<br />
|-<br />
| KDTW || Detroit Metropolitan Wayne County Airport, MI || USA || America || Basic development only<br />
<br />
|-<br />
| KEQY || Charlotte-Monroe Executive Airport, NC || USA || America || Some buildings and aircraft using shared models<br />
<br />
|-<br />
| KFHR || Friday Harbor Airport, WA || USA || America || <br />
<br />
|-<br />
| KIND || Indianapolis Airport, IN || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-90.07589&lat=32.31118&z=13 KJAN] || Jackson-Evers Airport, MS || USA || America || <br />
<br />
|-<br />
| KJFK || [[John F. Kennedy International Airport]], NY || USA || America || <br />
<br />
|-<br />
| KLAS || Las Vegas McCarran Airport, NV || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-118.40809&lat=33.9425&z=13 KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled<br />
<br />
|-<br />
| KLSV || [[Nellis Air Force Base]], NV || USA || America || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-109.4667&lat=47.04924&z=13 KLWT] || Lewistown Municipal Airport, MT || USA || America || <br />
<br />
|-<br />
| KMCI || Kansas City Airport, MO || USA || America || Basic development only<br />
<br />
|-<br />
| KMPI || Mariposa-Yosemite Airport, CA || USA || America || Hangars and FBO.<br />
<br />
|-<br />
| KMTN || Martin State Airport, MD || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-117.69181&lat=35.68565&z=13 KNID] || China Lake Naval Air Weapons Station, CA || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-122.04918&lat=37.4162&z=13 KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-122.22062&lat=37.7214&z=13 KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance<br />
<br />
|-<br />
| KORD || Chicago [[O'Hare International Airport]], IL || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-88.55704&lat=43.98436&z=13 KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-75.12398&lat=38.31045&z=13 KOXB] || Ocean City Municipal Airport, MD || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-122.59751&lat=45.58871&z=13 KPDX] || Portland Airport, OR || USA || America || <br />
<br />
|-<br />
| KPHX || Phoenix Sky Harbor Airport, AZ || USA || America || <br />
<br />
|-<br />
| KRNO || Reno/Tahoe Airport, NV || USA || America || <br />
<br />
|-<br />
| KSEA || [[Seattle-Tacoma International Airport]], WA || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-122.3749&lat=37.61897&z=13 KSFO] || [[San Francisco International Airport]], CA || USA || America || FlightGear's default airport, terminal buildings, airport lights and airport train.<br />
<br />
|-<br />
| KSLC || Salt Lake City International Airport, UT || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lat=33.80112251&lon=-118.34134126&z=15 KTOA] || Zamperini Field, Torrance, CA || USA || America || Fully modeled<br />
<br />
|-<br />
| KXTA || Edwards Airforce Base Detachment 3 (Homey Airport, or Area 51), NV || USA || America || Fully modelled<br />
<br />
<br />
|-<br />
| KVUO || Pearson Field Airport, Vancouver, WA || USA || America || <br />
<br />
|-<br />
| LDSP || Split Airport || Croatia || Europe || Basic development only<br />
<br />
|-<br />
| LEBB || Bilbao || Spain || Europe || Fully modeled<br />
<br />
|-<br />
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.19889&lat=47.32611&z=13 LFEA] || Belle-Ile || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.10167&lat=47.48139&z=13 LFEQ] || Quiberon || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.66479&lat=48.05247&z=13 LFES] || Guiscriff Scaër || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.35465&lat=49.04626&z=13 LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=4.8264&lat=45.25226&z=13 LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=0.08816&lat=49.53404&z=13 LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=5.36736&lat=43.50499&z=13 LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.60632&lat=48.89629&z=13 LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.622793&lat=48.822237&z=13 LFPL] || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.359443&lat=48.72551&z=13 LFPO] || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=2.073197&lat=48.810622&z=13 LFPZ] || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-4.41785&lat=48.44413&z=13 LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-4.167981&lat=47.97553&z=13 LFRQ] || Quimper || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.816762&lat=48.601247&z=13 LFRU] || Morlaix || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-2.736754&lat=47.717558&z=13 LFRV] || Vannes || France || Europe || Airport fitted with shared models<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFRH] || Lorient - Bretagne Sud || France || Europe ||<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of terminal<br />
<br />
|-<br />
| LILN || Venegono Airport || Italy || Europe || Developed airport<br />
<br />
|-<br />
| LILQ || Massa Cinquale Airport || Italy || Europe || <br />
<br />
|-<br />
| LILV || Valbrembo Airport || Italy || Europe || <br />
<br />
|-<br />
| LIMC || Milano-Malpensa Airport || Italy || Europe || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=9.70741&lat=45.66952&z=13 LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=9.27521&lat=45.44776&z=13 LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=7.36789&lat=45.73857&z=13 LIMW] || Aosta Airport || Italy || Europe || Fully modeled<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=14.26&lat=50.100833&z=13 LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled<br />
<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=11.34397&lat=47.26023&z=13 LOWI] || [[Innsbruck Airport]] || Austria || Europe || <br />
<br />
|-<br />
| LROP || Bucharest Otopeni || Romania || Europe || <br />
<br />
|-<br />
| LSGG || Geneve (Cointrin) Airport || Switzerland || Europe || Fully modelled. OSM2city available on https://github.com/FGMEMBERS-SCENERY/LSGG-fg-CustomScenery<br />
<br />
|-<br />
| LSGS || Sion Airport || Switzerland || Europe || Basic development only<br />
<br />
|-<br />
| LSZB || Bern-Belp Airport || Switzerland || Europe || Basic development only<br />
<br />
|-<br />
| PANC || Ted Stevens Anchorage International Airport || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=136.80541&lat=34.85841&z=13 RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=139.78114&lat=35.5533&z=13 RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=126.45051&lat=37.46909&z=13 RKSI] || Seoul Incheon Airport || South Korea || Asia || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=121.01349&lat=14.51024&z=13 RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals<br />
<br />
|-<br />
<br />
| SAEZ || Aeropuerto Internacional Ministro Pistarini || Argentina || America || Several static buildings<br />
<br />
|-<br />
<br />
| [[SVMI]] || Aeropuerto Internacional Simon Bolivar || Venezuela || America || Several static buildings<br />
<br />
|-<br />
<br />
| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America || <br />
<br />
|-<br />
| TDPD || Melville Hall Airport || Dominica || America || <br />
<br />
|-<br />
| TFFF || Martinique Aimé Césaire International Airport || Martinique, France || America || <br />
<br />
|-<br />
| TFFG || Grand Case Airport || St. Maarten, Netherlands || America || <br />
<br />
|-<br />
| TIST || Cyril E. King Airport || US Virgin Islands || America || <br />
<br />
|-<br />
| TJSJ || Luis Muñoz Marín International Airport || Puerto Rico || America || <br />
<br />
|-<br />
| TKPK || Robert L. Bradshaw International Airport || St. Kitts || America || <br />
<br />
|-<br />
| TNCM || [[Princess Juliana International Airport]] || St. Maarten, Netherlands || America || Fully modeled, customized terrain<br />
<br />
|-<br />
| TNCS || Juancho E. Yrausquin Airport || Saba || America || Fully modeled<br />
<br />
|-<br />
| TQPF || Clayton J. Lloyd International Airport || Anguilla || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-49.17201&lat=-25.53101&z=13 SBCT] || Afonso Pena International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-46.65768&lat=-23.62558&z=13 SBSP] || Congonhas Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-46.46864&lat=-23.43351&z=13 SBGR] || Guarulhos International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-48.54304&lat=-27.6685&z=13 SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]<br />
<br />
<br />
|-<br />
| SKRG || Jose Maria Cordoba International Airport, Rionegro, Antioquia || Colombia || South America || Fully modelled<br />
<br />
<br />
|-<br />
| VIDP || Indira Gandhi International Airport || India || Asia || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=89.42272&lat=27.39994&z=13 VQPR] || [[Paro Airport]] || Bhutan || Asia || Terminal, buildings, refernce points and other POIs<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=91.50917&lat=27.25961&z=13 VQ10] || [[Yongphulla Airport]] || Bhutan || Asia || Terminal, some other buildings <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=113.9183&lat=22.308&z=13 VHHH] || Hong Kong International Airport || China || Asia || Terminals, control towers, some other buildings <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&z=13 1G3] || Kent State University Airfield, OH || USA || America || <br />
<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&z=13 1G5] || [[Medina Municipal Airport]], OH || USA || America || <br />
<br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&z=13 29G] || Portage Co, OH || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-90.13769&lat=43.83872&z=13 82C] || Mauston-New Lisbon Union Airport, WI || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-89.02545&lat=44.50485&z=13 68C] || Iola Central County Airport, WI || USA || America || <br />
<br />
|-<br />
| [https://scenery.flightgear.org/map/?lon=-123.00815977&lat=43.93009927&z=13 77S] || Hobby Field, Creswell, OR || USA || America || Nearly complete: Hangars (one accidently missing), fuel pump, GA aircraft, cars, trees, bushes (shared models)<br />
<br />
|}<br />
<br />
== Authors ==<br />
<br />
Airports by HerbyW in Yakutia, Irkutsk and Krasnoyarsk:<br />
UIBB UEEE UEST UEMS UEBN UEBT UEWD UEMA UERR UEMT UEEA UEMU UIII UITT UEBB UEVV UENW UEMO UERL UERT UEMH UERO UERP UNAA UIUN UENN UIBV UNCC UEMJ<br />
<br />
Airports by D-ABBA:<br />
EDXW,EDFE,EDGS,EDFQ,EDFH,EDFL,EDFO,ED03<br />
<br />
Airports by [[User:Laserman]]:<br />
EDDG,EDLM,EDLB,EDLK,EDLN,EDLV,EDLW,LJLJ,LJAJ,LJSG,LJCE,LJPZ <br />
<br />
<br />
== External links ==<br />
* [http://iveze.nl/fgmap/ Builtup airports in Flightgear] – Interactive world map by KL-666. ''See also related forum topic [http://forum.flightgear.org/viewtopic.php?f=5&t=23613 Map of airports with buildings in terrasync].''<br />
<br />
{{Suggested}}<br />
<br />
[[Category:Lists]]<br />
[[Category:Airports]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=Suggested_airports&diff=117324Suggested airports2019-02-09T14:52:17Z<p>Inetuka: </p>
<hr />
<div>Here you will find Airports that are well developed and/or have an outstanding scenery. Thus they are "suggested" especially to be visited and/or used for Multi-player events like FlyIns, TGA, ATC, etc..<br />
<br /><br /><br />
If you are searching for the '''development-status of Airports''' see the wiki [[Developed Airports]].<br />
<br />For further suggestions see [[Suggested Scenery]] and [[Suggested Flights]]<br />
<br /><br /><br />
The overall Airport-Rating (column "R") is based on the TerraSync-Status of the following characteristics:<br />
{| border="0" <br />
|-<br />
! style="text-align:center"| * !!style="text-align:left"| &nbsp;&nbsp;&nbsp; superior surrounding landscape - although the airport itself is not (yet) developed accordingly<br />
|-<br />
! style="text-align:center"| ** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; complex modeling of buildings<br />
|-<br />
! style="text-align:center"| *** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; complex modeling of buildings, taxiways, and aprons<br />
|-<br />
! style="text-align:center"| **** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; extensive modeling of airport and landscape and/or city<br />
|}<br />
<br /><br />
Further columns to watch for are:<br />
* '''S = Size:''' L= all aircraft, M= midium size aircraft, S= for small aircraft<br />
* '''FGCOM:''' If available one FGCOM frequency is given, followed by the amount of the total available FGCOM frequencies<br />
* '''Parking:''' amount of pre-defined Parking-Lots (otherwise see: [[Initial Starting Positions]])<br />
* '''R/I:''' amount of runways and ILS (e.g. KROC has 3 runway: 04/22 has each 1 ILS, 10/28 has only one ILS on 28, 07/25 has no ILS)<br />
<br /><br />
{| class="wikitable sortable" border="0" cellspacing="0"<br />
! width="40" | ICAO <br />
! width="130" | Name<br />
! width="80" | Country<br />
! width="80" | Continent<br />
! width="30" | R<br />
! width="30" | S<br />
! width="100" | FGCOM<br />
! width="50" | Parking<br />
! width="40" | R/I<br />
! class="unsortable" style="background:#efefef" | Comment<br />
|-<br />
| LKKB || Praha-Kbely || Czech republic || Europe ||align="center"| *** ||align="center"| M ||align="center"| 120.87 ||align="center"| -- ||align="center"| 1/1 || request for develop it - Military Airport<br />
|-<br />
|-<br />
| BKPR || Pristina || Kosovo || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 || very nice scenery<br />
|- <br />
| CYVR || [[Vancouver International Airport|Vancouver]] || Canada || America ||align="center"| * ||align="center"| L ||align="center"| 125.650 (6) ||align="center"| many ||align="center"| 5/5 || nice area<br />
|-<br />
| EDDC || [[Dresden Airport|Dresden Airport]] || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| - ||align="center"| 2/4 || Terminal, Tower, GA Hangars and many more<br />
|- <br />
| EDDF || [[Frankfurt am Main Airport|Frankfurt am Main]] || Germany || Europe || align="center" | **** || align="center" | L || align="center" | 127.320 (6) || align="center" | many ||align="center"| 4/6 || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique skyscrapers downtown<br />
|-<br />
| EDDH || [[Hamburg Airport|Hamburg]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 126.850 (7) ||align="center"| -- ||align="center"| 2/4 || Fully modeled, plus unique buildings downtown|-<br />
|-<br />
| EDDI || [[EDDI|Berlin Tempelhof]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 118.100 (10) ||align="center"| 1 ||align="center"| 2/0 || Fully modeled, especially also the City<br />
|-<br />
| EDDK || [[EDDK|Köln/Bonn]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 124.97 (5) ||align="center"| -- ||align="center"| 3/3 || Fully modeled airport and surroundings<br />
|-<br />
| EDDL || [[Düsseldorf International Airport|Düsseldorf]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (4) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled<br />
|-<br />
| EDDP || [[Leipzig/Halle Airport|Leipzig/Halle]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 121.100 (5) ||align="center"| 2 ||align="center"| 2/4 || Tower, terminals B and C, large DHL-area modeled, inclusive [[Signs]]<br />
|-<br />
| EDDS || Stuttgart || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (8) ||align="center"| -- ||align="center"| 1/2 || Tower, terminal and [[Signs]] are fully modeled<br />
|-<br />
| EDDT || [[Berlin Tegel Airport|Berlin Tegel]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.700 (11) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]<br />
|-<br />
| EDDV || [[EDDV|Hannover]] || Germany || Europe ||align="center"| * ||align="center"| L ||align="center"| 120.170 (3)) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled<br />
|-<br />
| EDDW || Bremen || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.500 (7) ||align="center"| -- ||align="center"| 2/2 || very nicely modeled<br />
|-<br />
| EDFH || Frankfurt Hahn || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.65 (7) ||align="center"| -- ||align="center"| 1/2 || very nicely modeled (use Terrasync)<br />
|-<br />
| EDLN || Mönchengladbach || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| - || very nicely modeled<br />
|-<br />
| EDVE || [[Braunschweig Airport|Braunschweig]] || Germany || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.350 (2) ||align="center"| -- ||align="center"| 2/1 || <br />
|-<br />
| EDXW || Westerland Sylt || Germany || Europe ||align="center"| *** ||align="center"| M ||align="center"| 119.75 (2) ||align="center"| -- ||align="center"| 2/1 || very nicely modeled famous sea-resort (use Terrasync)<br />
|-<br />
| EEKE || Kuressaare || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 || <br />
|-<br />
| EFHF || Helsinki-Malmi || Finland || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 || <br />
|-<br />
| EFHK || Helsinki || Finland || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.700 (5) ||align="center"| -- ||align="center"| 3/5 || Nice terminal and city landmarks<br />
|-<br />
| EEPU || Parnu || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EETN || Tallinn || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/2 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EETU || Tartu || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EGFF || Cardiff || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 125.00 (3) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGGP || Liverpool || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.350 (4) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGGW || Luton || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.720 (6) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGKA || Shoreham || UK || Europe ||align="center"| *** ||align="center"| S ||align="center"| 125.400 (3) ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| EGKK || [[London Gatwick Airport|London-Gatwick]] || UK || Europe ||align="center"| **** ||align="center"| M ||align="center"| 124.220 (8) ||align="center"| 6 ||align="center"| 1/2 ||<br />
|-<br />
| EGLL || London-Heathrow || UK || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.500 (14) ||align="center"| 3 ||align="center"| 2/4 ||<br />
|-<br />
| EGPH || Edinburgh || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (4) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| EGSH || Norwich || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 124.250 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| EGUN || RAF Mildenhall || UK || Europe ||align="center"| ** ||align="center"| L ||align="center"| 122.550 (5) ||align="center"| -- ||align="center"| 1/1 || USAF base for tankers and cargo planes near other military air bases like EGUL, EGYM, EGXH,... will have buildings soon. ATC is also provided.<br />
|-<br />
| EHAM || [[Amsterdam Airport Schiphol|Amsterdam]] || Netherlands || Europe ||align="center"| **** ||align="center"| L ||align="center"| 119.220 (1) ||align="center"| many ||align="center"| 6/6 ||One of the best modeled airports in the FlightGear world; most dense AI traffic.<br />
|-<br />
| EHEH || Eindhoven || Netherlands || Europe ||align="center"| ** ||align="center"| M ||align="center"| 131.000 (6) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EHLE || [[Lelystad Airport|Lelystad]] || Netherlands || Europe ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| 1 ||align="center"| 2/1 || Basic scenery models, home of [[FSweekend]].<br />
|-<br />
| EHVK || [[Volkel Air Base|Volkel]] || Netherlands || Europe ||align="center"| ** ||align="center"| L ||align="center"| 123.170 (1) ||align="center"| many ||align="center"| 2/2 ||<br />
|-<br />
| EIDW || [[Dublin Airport|Dublin]] || Ireland || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.600 (7) ||align="center"| -- ||align="center"| 3/3 ||<br />
|-<br />
| ELLX || Luxembourg || Luxembourg || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 || very nicely modeled (use Terrasync)<br />
|-<br />
| ENAL || Alesund || Norway || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.100 (4) ||align="center"| -- ||align="center"| 1/1 ||<br />
|-<br />
| ENSD || Alesund || Norway || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| ENVA || Trondheim || Norway || Europe ||align="center"| *** ||align="center"| L ||align="center"| 122.100 (6) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| ESGP || Göteborg || Sweden || Europe ||align="center"| ** ||align="center"| M ||align="center"| 129.100 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| FACT || Cape Town || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/2 ||nice area<br />
|-<br />
| FAJS || Johannisburg || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 121.900 (3) ||align="center"| many ||align="center"| 2/3 ||high (5000), in mountains<br />
|-<br />
| FHAW || RAF Ascension Island AUX AF || Ascension Island || Africa ||align="center"| * ||align="center"| L ||align="center"| 126.200 (2) ||align="center"| -- ||align="center"| 1/0 ||RAF and USAF auxiliary base. Developed layout, in the middle of the Atlantic Ocean, great place for military flights.<br />
|-<br />
| GCFV || Fuerteventura || Gran Canaria || Africa ||align="center"| * ||align="center"| L ||align="center"| 119.200 (4) ||align="center"| 9 ||align="center"| 1/1 ||nice island area<br />
|-<br />
| KABQ || Albuquerque || USA NM || America ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 ||<br />
|-<br />
| HECA || Cairo || Egypt || Africa ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 || near pyramids<br />
|-<br />
| KATL || Atlanta || USA GA || America ||align="center"| * ||align="center"| L ||align="center"| 119.550 (4) ||align="center"| many ||align="center"| 3/4 ||<br />
|-<br />
| KAUS || Austin || USA TX || America ||align="center"| *** ||align="center"| L ||align="center"| 121.00 (10) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| KBWI || Baltimore || USA MD || America ||align="center"| *** ||align="center"| L ||align="center"| 119.400 (10) ||align="center"| -- ||align="center"| 4/6 ||<br />
|-<br />
| KCGS || College Park || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| 119.850 (3) ||align="center"| -- ||align="center"| 2/0 ||<br />
|-<br />
| KDCA || Reagan National || USA VA || America ||align="center"| *** ||align="center"| M ||align="center"| 120.750 (7) ||align="center"| -- ||align="center"| 3/2 ||<br />
|-<br />
| KDEN || [[Denver International Airport|Denver]] || USA CO || America ||align="center"| ** ||align="center"| L ||align="center"| 133.300 (16) ||align="center"| -- ||align="center"| 6/12 ||<br />
|-<br />
| KDTW || Detroit || USA MI || America ||align="center"| ** ||align="center"| L ||align="center"| 118.400 (15) ||align="center"| -- ||align="center"| 6/8 ||<br />
|-<br />
| KFHR || Friday Harbor || USA WA || America ||align="center"| * ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| KHAF || Half Moon Bay || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 122.800 (2) ||align="center"| 4 ||align="center"| 1/0 ||nice area - near KSFO<br />
|-<br />
| KHWD || Hayward || USA CA || America ||align="center"| ** ||align="center"| S ||align="center"| 122.500 (10) ||align="center"| 9 ||align="center"| 2/1 ||nice area - near KSFO<br />
|-<br />
| KIAD || Washington-Dulles || USA VA || America ||align="center"| * ||align="center"| L ||align="center"| 120.100 (14) ||align="center"| many ||align="center"| 4/3 ||<br />
|-<br />
| KIND || Indianapolis || USA IN || America ||align="center"| *** ||align="center"| L ||align="center"| 127.820 (7) ||align="center"| -- ||align="center"| 3/6 ||<br />
|-<br />
| KJAN || Jackson-Evers || USA MS || America ||align="center"| *** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| KJFK || [[John F. Kennedy International Airport|John F. Kennedy]] || USA NY || America ||align="center"| *** ||align="center"| L ||align="center"| 119.100 (18) ||align="center"| many ||align="center"| 4/5 ||<br />
|-<br />
| KLAS || Las Vegas || USA NV || America ||align="center"| **** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 4/3 || terminal and some casinos modeled<br />
|-<br />
| KLAX || [[Los Angeles International Airport|Los Angeles]] || USA CA || America ||align="center"| *** ||align="center"| L ||align="center"| 133.900 (7) ||align="center"| many ||align="center"| 4/8 ||<br />
|-<br />
| KLSV || [[Nellis Air Force Base|Nellis Air Force]] || USA NV || America ||align="center"| *** ||align="center"| L ||align="center"| 132.550 (6) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| KLWD || Lewistown || USA MT || America ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| KMTN || Martin State || USA MD || America ||align="center"| ** ||align="center"| M ||align="center"| 121.300 (4) ||align="center"| -- ||align="center"| 2/2 || airport and terrain modeled<br />
|-<br />
| KNID || China Lake Naval || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 120.150 (2) ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| KNUQ || Moffett Federal AFLD || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 119.550 (6) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| KOAK || Oakland || USA CA || America ||align="center"| ** ||align="center"| L ||align="center"| 127.200 (7) ||align="center"| many ||align="center"| 4/3 ||<br />
|-<br />
| KORD ||[[O'Hare International Airport|Chicago O'Hare]] || USA IL || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| many ||align="center"| 7/14 ||<br />
|-<br />
| KOSH || Wittman Rgl. || USA WI || America ||align="center"| ** ||align="center"| M ||align="center"| 118.500 (4) ||align="center"| -- ||align="center"| 4/1 ||<br />
|-<br />
| KOXB || Ocean City Muni. || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||<br />
|-<br />
| KPDX || Portland || USA OR || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 3/5 ||<br />
|-<br />
| KPHX || Phoenix || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 120.900 (6) ||align="center"| -- ||align="center"| 3/5 || most skyscrapers modeled<br />
|-<br />
| KRDU || Raleigh || USA NC || America ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (12) ||align="center"| many ||align="center"| 3/4 ||nice for flying east-coast<br />
|-<br />
| KRNO || Reno/Tahoe || USA NZ || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (7) ||align="center"| -- ||align="center"| 3/2 ||High in clouds<br />
|-<br />
| KSAN || San Diego || USA AZ || America ||align="center"| * ||align="center"| M ||align="center"| 118.300 (7) ||align="center"| many ||align="center"| 1/2 ||Interesting area at border to Mexico<br />
|-<br />
| KSEA || [[Seattle-Tacoma International Airport|Seattle Tacoma]] || USA WA || America ||align="center"| ** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 3/5 || basic terminal model, some skyscrapers modeled<br />
|-<br />
| KSFO || [[San Francisco International Airport|San Francisco]] || USA CA || America ||align="center"| **** ||align="center"| L ||align="center"| 120.500 (7) ||align="center"| many ||align="center"| 4/3 ||FGFS Default -- overcrowded<br />
|-<br />
| KSLC || Salt Lake City || USA UT || America ||align="center"| * ||align="center"| L ||align="center"| 118.300 (13) ||align="center"| -- ||align="center"| 4/6 ||very high in clouds (4227 ft, 1290 m)<br />
|-<br />
| KSJC || [[San Jose International Airport|San Jose]] || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 124.00 (7) ||align="center"| 14 ||align="center"| 3/2 ||Bay-area near KSFO<br />
|-<br />
| LDSP || Split || Croatia || Europe ||align="center"| ** ||align="center"| M ||align="center"| unknown ||align="center"| -- ||align="center"| 1/1 ||Small civil airport with awesome scenery neighboring.<br />
|-<br />
| LDZU || Udbina || Croatia || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||interesting airport high in Mountains - no ILS<br />
|-<br />
| LFFE || Enghien Moisselles || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| --- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just north of Paris<br />
|-<br />
| LFML || Marseille || France || Europa ||align="center"| * ||align="center"| M ||align="center"| 118.370 (4) ||align="center"| many ||align="center"| 2/2 ||Mediterranean coast<br />
|-<br />
| LFPG || Paris Charles de Gaulle || France || Europa ||align="center"| **** ||align="center"| L ||align="center"| 123.600 (23) ||align="center"| -- ||align="center"| 4/8 ||very detailed city of Paris near by<br />
|-<br />
| LFPH || Chelles Le Pin || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just south of Paris<br />
|-<br />
| LFPL || Lognes Emerainville || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||nice little airport just south of Paris<br />
|-<br />
| LFPO || Paris Orly || France || Europa ||align="center"| **** ||align="center"| M ||align="center"| 120.500 (13) ||align="center"| -- ||align="center"| 3/5 ||the older airport at Paris<br />
|-<br />
| LFPZ || St-Cyr l'Ecole || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little airport just west of Paris, near Versailles Castle<br />
|-<br />
| LFRJ || Landivisiau || France || Europa ||align="center"| ** ||align="center"| M ||align="center"| 119.700 (2) ||align="center"| -- ||align="center"| 1/1 ||Naval Base<br />
|-<br />
| LFSB || [[EuroAirport_Basel-Mulhouse-Freiburg|Basel-Mulhouse]] || Swiss || Europa ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (7) ||align="center"| 5 ||align="center"| 2/1 || Nice modeling of Terminal.<br />
|-<br />
| LHBP || Budapest || Hungaria || Europa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/4 ||in-midst the typical Puszta-area<br />
|-<br />
| LILN || Venegono || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| 128.550 (1) ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| LILV || Valbrembo || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||recreation area: Mountains, tennis, pool, etc.<br />
|-<br />
| LIMC || Milano Malpensa || Italy || Europa ||align="center"| *** ||align="center"| L ||align="center"| 119.000 (11) ||align="center"| -- ||align="center"| 2/3 ||<br />
|-<br />
| LIME || Bergamo-Orio al Serio || Italy || Europa ||align="center"| ** ||align="center"| M ||align="center"| 120.500 (5) ||align="center"| -- ||align="center"| 2/1 ||nice mountain area<br />
|-<br />
| LIML || Milano Limate || Italy || Europa ||align="center"| *** ||align="center"| M ||align="center"| 119.250 (5) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| LIMW || Aosta || Italy || Europa ||align="center"| * ||align="center"| M ||align="center"| 119.950 (1) ||align="center"| -- ||align="center"| 1/0 ||in a valley in high mountain area, fully modeled<br />
|-<br />
| LIPA || [[Aviano Air Base]] || Italy || Europe ||align="center"| * ||align="center"| L ||align="center"| 122.100 ||align="center"| -- ||align="center"| 1/1 ||Military airport with various scenery neighboring: Carnic Alps, Po Valley and the Adriatic Sea.<br />
|-<br />
| LJCE || Cerklje || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || Military airport with civilian part near Croatia<br />
|-<br />
| LJLJ || Ljubljana Brnik || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || capital of Slovenia<br />
|-<br />
| LJPZ || Portorož || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || at the adriatic sea<br />
|-<br />
| LPLA || [[Lajes Field]] || Azores, Portugal || Europe ||align="center"| * ||align="center"| L ||align="center"| 122.100 ||align="center"| -- ||align="center"| 1/1 ||Military-Civil airport with various small islands neighboring.<br />
|-<br />
| LQSA || Sarajewo || Bosnia || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.250 (3) ||align="center"| -- ||align="center"| 1/1 ||very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| LOWI || [[Innsbruck Airport|Innsbruck]] || Austria || Europe ||align="center"| **** ||align="center"| S ||align="center"| 120.100 (3) ||align="center"| -- ||align="center"| 1/1 || very nice and difficult approach, wonderful scenery<br />
|-<br />
| LROP || Bucharest || Romania || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.850 (3) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| LSGS || Sion || Swiss || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.217 (5) ||align="center"| -- ||align="center"| 1/1 ||Wonderful surrounded by high mountains<br />
|-<br />
| LSZH || Zürich-Kloten || Swiss || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.800 ||align="center"| many ||align="center"| 3/4 ||very nice mountain/lake area<br />
|-<br />
| LSZB|| Bern-Belp || Swiss || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.020 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| LSZS|| Samedan || Swiss || Europe ||align="center"| *** ||align="center"| M ||align="center"| 135,320 (3) ||align="center"| -- ||align="center"| 1/0 || Very nice high mountain region, AP at 5600 ft (1700 m)<br />
|-<br />
| PANC|| Anchorage || USA Alaska || America ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (9) ||align="center"| -- ||align="center"| 3/3 ||interesting area<br />
|-<br />
| LYBE || Belgrad || Serbia || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| LYPG || Podgorica || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.200 (2) ||align="center"| -- ||align="center"| 2/1 || very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| LYTV || Tivat || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.000 (1) ||align="center"| -- ||align="center"| 1/1 || very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| MUHA || Havana || Cuba || America ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 1/1 ||nice for island-hopping<br />
|-<br />
| NZAA || Auckland || New Zealand || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.700 ||align="center"| many ||align="center"| 2/2 ||nice for island-hopping<br />
|-<br />
| OMAA || Abu Dahbi || United AE || Asia ||align="center"| * ||align="center"| L ||align="center"| 119.200 ||align="center"| many ||align="center"| 1/2 ||interesting area<br />
|-<br />
| OOMS || Seeb || United AE || Asia ||align="center"| * ||align="center"| M ||align="center"| 118.400 (5) ||align="center"| many ||align="center"| 2/2 ||nice sea/mountain area<br />
|-<br />
| PHNL || Honolulu || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| 123.900 (5) ||align="center"| many ||align="center"| 4/2 ||wonderful island scenery<br />
|-<br />
| PHOG || Kahului || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| ||align="center"| ||align="center"| 2/1 ||wonderful island scenery<br />
|-<br />
| RJTT || [[Tokyo Haneda International Airport|Tokyo]] || Japan || Asia ||align="center"| *** ||align="center"| L ||align="center"| 126.200 (6) ||align="center"| -- ||align="center"| 3/3 ||interesting area<br />
|-<br />
| RKSI || Seoul || South Korea || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (6) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| RPLL || Manila || Philipines || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| TDPD || Melville Hall || Dominica || America ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||nice area<br />
|-<br />
| TFFF || Le Lamentin || Martinique || America ||align="center"| *** ||align="center"| M ||align="center"| 118.500 (5) ||align="center"| -- ||align="center"| 1/1 ||nice area<br />
|-<br />
| TFFG || Grand Case || Anguilla || America ||align="center"| ** ||align="center"| S ||align="center"| 128.940 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| TIST || Cyril E King || Virgin Islands || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 ||nice area<br />
|-<br />
| TJSJ || San Juan || Puerto Rico || America ||align="center"| *** ||align="center"| M ||align="center"| 132.050 (6) ||align="center"| -- ||align="center"| 2/2 ||nice area<br />
|-<br />
| TKPK || Saint Kitts || Guadeloupe || America ||align="center"| ** ||align="center"| M ||align="center"| 118.300 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| TNCM || [[Princess Juliana International Airport|Princess Juliana]] || ST Maarten || America ||align="center"| *** ||align="center"| M ||align="center"| 118.700 (2) ||align="center"| -- ||align="center"| 1/0 ||very nice area<br />
|-<br />
| TQPF || Wallblake || Anquilla || America ||align="center"| ** ||align="center"| S ||align="center"| 18.500 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| VIDP || New Dehli || India || Asia ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (5) ||align="center"| many ||align="center"| 2/3 ||nice area<br />
|-<br />
| VHHH || Hong Kong || China || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.400 (16) ||align="center"| many ||align="center"| 2/4 ||very nice mountain/sea area<br />
|-<br />
| WSSS || [[Singapore Changi International Airport|Singapore Changi]] || Singapore || Asia ||align="center"| **** ||align="center"| L ||align="center"| 118.600 (8) ||align="center"| many ||align="center"| 2/3 ||Very nice modeled from TheOmegaHangar one. Best in FlightGear<br />
|-<br />
| YBAS || Alice Springs || Australia NT || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.300 (2) ||align="center"| 26 ||align="center"| 3/1 ||Australian Back-Country<br />
|-<br />
| YBBN || Brisbane || Australia NSW || Oceania ||align="center"| *** ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||<br />
|-<br />
| YPDN || Darwin || Australia NT || Oceania ||align="center"| * ||align="center"| M ||align="center"| 133.100 (8) ||align="center"| many ||align="center"| 2/1 ||<br />
|-<br />
| YSCB || Canberra || Australia NSW || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.700 (5) ||align="center"| many ||align="center"| 2/1 ||High Mountain region (1800 ft, 550 m)<br />
|-<br />
| YSSY || [[Sydney International Airport|Sydney]] || Australia NSW || Oceania ||align="center"| * ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||<br />
|-<br />
|}<br />
<br />
{{suggested}}<br />
<br />
[[Category:Airports]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=Suggested_airports&diff=117323Suggested airports2019-02-09T14:46:47Z<p>Inetuka: </p>
<hr />
<div>Here you will find Airports that are well developed and/or have an outstanding scenery. Thus they are "suggested" especially to be visited and/or used for Multi-player events like FlyIns, TGA, ATC, etc..<br />
<br /><br /><br />
If you are searching for the '''development-status of Airports''' see the wiki [[Developed Airports]].<br />
<br />For further suggestions see [[Suggested Scenery]] and [[Suggested Flights]]<br />
<br /><br /><br />
The overall Airport-Rating (column "R") is based on the TerraSync-Status of the following characteristics:<br />
{| border="0" <br />
|-<br />
! style="text-align:center"| * !!style="text-align:left"| &nbsp;&nbsp;&nbsp; superior surrounding landscape - although the airport itself is not (yet) developed accordingly<br />
|-<br />
! style="text-align:center"| ** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; complex modeling of buildings<br />
|-<br />
! style="text-align:center"| *** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; complex modeling of buildings, taxiways, and aprons<br />
|-<br />
! style="text-align:center"| **** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; extensive modeling of airport and landscape and/or city<br />
|}<br />
<br /><br />
Further columns to watch for are:<br />
* '''S = Size:''' L= all aircraft, M= midium size aircraft, S= for small aircraft<br />
* '''FGCOM:''' If available one FGCOM frequency is given, followed by the amount of the total available FGCOM frequencies<br />
* '''Parking:''' amount of pre-defined Parking-Lots (otherwise see: [[Initial Starting Positions]])<br />
* '''R/I:''' amount of runways and ILS (e.g. KROC has 3 runway: 04/22 has each 1 ILS, 10/28 has only one ILS on 28, 07/25 has no ILS)<br />
<br /><br />
{| class="wikitable sortable" border="0" cellspacing="0"<br />
! width="40" | ICAO <br />
! width="130" | Name<br />
! width="80" | Country<br />
! width="80" | Continent<br />
! width="30" | R<br />
! width="30" | S<br />
! width="100" | FGCOM<br />
! width="50" | Parking<br />
! width="40" | R/I<br />
! class="unsortable" style="background:#efefef" | Comment<br />
|-<br />
| LKKB || Praha-Kbely || Czech republic || Europe ||align="center"| *** ||align="center"| M ||align="center"| 120.87 ||align="center"| -- ||align="center"| 1/1 || request for develop it - Military Airport<br />
|-<br />
|-<br />
| BKPR || Pristina || Kosovo || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 || very nice scenery<br />
|- <br />
| CYVR || [[Vancouver International Airport|Vancouver]] || Canada || America ||align="center"| * ||align="center"| L ||align="center"| 125.650 (6) ||align="center"| many ||align="center"| 5/5 || nice area<br />
|-<br />
| EDDC || [[Dresden Airport|Dresden Airport]] || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| - ||align="center"| 2/4 || Terminal, Tower, GA Hangars and many more<br />
|- <br />
| EDDF || [[Frankfurt am Main Airport|Frankfurt am Main]] || Germany || Europe || align="center" | **** || align="center" | L || align="center" | 127.320 (6) || align="center" | many ||align="center"| 4/6 || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique skyscrapers downtown<br />
|-<br />
| EDDH || [[Hamburg Airport|Hamburg]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 126.850 (7) ||align="center"| -- ||align="center"| 2/4 || Fully modeled, plus unique buildings downtown|-<br />
|-<br />
| EDDI || [[EDDI|Berlin Tempelhof]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 118.100 (10) ||align="center"| 1 ||align="center"| 2/0 || Fully modeled, especially also the City<br />
|-<br />
| EDDK || [[EDDK|Köln/Bonn]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 124.97 (5) ||align="center"| -- ||align="center"| 3/3 || Fully modeled airport and surroundings<br />
|-<br />
| EDDL || [[Düsseldorf International Airport|Düsseldorf]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (4) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled<br />
|-<br />
| EDDP || [[Leipzig/Halle Airport|Leipzig/Halle]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 121.100 (5) ||align="center"| 2 ||align="center"| 2/4 || Tower, terminals B and C, large DHL-area modeled, inclusive [[Signs]]<br />
|-<br />
| EDDS || Stuttgart || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (8) ||align="center"| -- ||align="center"| 1/2 || Tower, terminal and [[Signs]] are fully modeled<br />
|-<br />
| EDDT || [[Berlin Tegel Airport|Berlin Tegel]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.700 (11) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]<br />
|-<br />
| EDDV || [[EDDV|Hannover]] || Germany || Europe ||align="center"| * ||align="center"| L ||align="center"| 120.170 (3)) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled<br />
|-<br />
| EDDW || Bremen || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.500 (7) ||align="center"| -- ||align="center"| 2/2 || very nicely modeled<br />
|-<br />
| EDFH || Frankfurt Hahn || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.65 (7) ||align="center"| -- ||align="center"| 1/2 || very nicely modeled (use Terrasync)<br />
|-<br />
| EDLN || Mönchengladbach || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| - || very nicely modeled<br />
|-<br />
| EDVE || [[Braunschweig Airport|Braunschweig]] || Germany || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.350 (2) ||align="center"| -- ||align="center"| 2/1 || <br />
|-<br />
| EDXW || Westerland Sylt || Germany || Europe ||align="center"| *** ||align="center"| M ||align="center"| 119.75 (2) ||align="center"| -- ||align="center"| 2/1 || very nicely modeled famous sea-resort (use Terrasync)<br />
|-<br />
| EEKE || Kuressaare || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 || <br />
|-<br />
| EFHF || Helsinki-Malmi || Finland || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 || <br />
|-<br />
| EFHK || Helsinki || Finland || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.700 (5) ||align="center"| -- ||align="center"| 3/5 || Nice terminal and city landmarks<br />
|-<br />
| EEPU || Parnu || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EETN || Tallinn || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/2 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EETU || Tartu || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EGFF || Cardiff || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 125.00 (3) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGGP || Liverpool || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.350 (4) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGGW || Luton || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.720 (6) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGKA || Shoreham || UK || Europe ||align="center"| *** ||align="center"| S ||align="center"| 125.400 (3) ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| EGKK || [[London Gatwick Airport|London-Gatwick]] || UK || Europe ||align="center"| **** ||align="center"| M ||align="center"| 124.220 (8) ||align="center"| 6 ||align="center"| 1/2 ||<br />
|-<br />
| EGLL || London-Heathrow || UK || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.500 (14) ||align="center"| 3 ||align="center"| 2/4 ||<br />
|-<br />
| EGPH || Edinburgh || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (4) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| EGSH || Norwich || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 124.250 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| EGUN || RAF Mildenhall || UK || Europe ||align="center"| ** ||align="center"| L ||align="center"| 122.550 (5) ||align="center"| -- ||align="center"| 1/1 || USAF base for tankers and cargo planes near other military air bases like EGUL, EGYM, EGXH,... will have buildings soon. ATC is also provided.<br />
|-<br />
| EHAM || [[Amsterdam Airport Schiphol|Amsterdam]] || Netherlands || Europe ||align="center"| **** ||align="center"| L ||align="center"| 119.220 (1) ||align="center"| many ||align="center"| 6/6 ||One of the best modeled airports in the FlightGear world; most dense AI traffic.<br />
|-<br />
| EHEH || Eindhoven || Netherlands || Europe ||align="center"| ** ||align="center"| M ||align="center"| 131.000 (6) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EHLE || [[Lelystad Airport|Lelystad]] || Netherlands || Europe ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| 1 ||align="center"| 2/1 || Basic scenery models, home of [[FSweekend]].<br />
|-<br />
| EHVK || [[Volkel Air Base|Volkel]] || Netherlands || Europe ||align="center"| ** ||align="center"| L ||align="center"| 123.170 (1) ||align="center"| many ||align="center"| 2/2 ||<br />
|-<br />
| EIDW || [[Dublin Airport|Dublin]] || Ireland || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.600 (7) ||align="center"| -- ||align="center"| 3/3 ||<br />
|-<br />
| ELLX || Luxembourg || Luxembourg || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 || very nicely modeled (use Terrasync)<br />
|-<br />
| ENAL || Alesund || Norway || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.100 (4) ||align="center"| -- ||align="center"| 1/1 ||<br />
|-<br />
| ENSD || Alesund || Norway || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| ENVA || Trondheim || Norway || Europe ||align="center"| *** ||align="center"| L ||align="center"| 122.100 (6) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| ESGP || Göteborg || Sweden || Europe ||align="center"| ** ||align="center"| M ||align="center"| 129.100 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| FACT || Cape Town || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/2 ||nice area<br />
|-<br />
| FAJS || Johannisburg || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 121.900 (3) ||align="center"| many ||align="center"| 2/3 ||high (5000), in mountains<br />
|-<br />
| FHAW || RAF Ascension Island AUX AF || Ascension Island || Africa ||align="center"| * ||align="center"| L ||align="center"| 126.200 (2) ||align="center"| -- ||align="center"| 1/0 ||RAF and USAF auxiliary base. Developed layout, in the middle of the Atlantic Ocean, great place for military flights.<br />
|-<br />
| GCFV || Fuerteventura || Gran Canaria || Africa ||align="center"| * ||align="center"| L ||align="center"| 119.200 (4) ||align="center"| 9 ||align="center"| 1/1 ||nice island area<br />
|-<br />
| KABQ || Albuquerque || USA NM || America ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 ||<br />
|-<br />
| HECA || Cairo || Egypt || Africa ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 || near pyramids<br />
|-<br />
| KATL || Atlanta || USA GA || America ||align="center"| * ||align="center"| L ||align="center"| 119.550 (4) ||align="center"| many ||align="center"| 3/4 ||<br />
|-<br />
| KAUS || Austin || USA TX || America ||align="center"| *** ||align="center"| L ||align="center"| 121.00 (10) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| KBWI || Baltimore || USA MD || America ||align="center"| *** ||align="center"| L ||align="center"| 119.400 (10) ||align="center"| -- ||align="center"| 4/6 ||<br />
|-<br />
| KCGS || College Park || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| 119.850 (3) ||align="center"| -- ||align="center"| 2/0 ||<br />
|-<br />
| KDCA || Reagan National || USA VA || America ||align="center"| *** ||align="center"| M ||align="center"| 120.750 (7) ||align="center"| -- ||align="center"| 3/2 ||<br />
|-<br />
| KDEN || [[Denver International Airport|Denver]] || USA CO || America ||align="center"| ** ||align="center"| L ||align="center"| 133.300 (16) ||align="center"| -- ||align="center"| 6/12 ||<br />
|-<br />
| KDTW || Detroit || USA MI || America ||align="center"| ** ||align="center"| L ||align="center"| 118.400 (15) ||align="center"| -- ||align="center"| 6/8 ||<br />
|-<br />
| KFHR || Friday Harbor || USA WA || America ||align="center"| * ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| KHAF || Half Moon Bay || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 122.800 (2) ||align="center"| 4 ||align="center"| 1/0 ||nice area - near KSFO<br />
|-<br />
| KHWD || Hayward || USA CA || America ||align="center"| ** ||align="center"| S ||align="center"| 122.500 (10) ||align="center"| 9 ||align="center"| 2/1 ||nice area - near KSFO<br />
|-<br />
| KIAD || Washington-Dulles || USA VA || America ||align="center"| * ||align="center"| L ||align="center"| 120.100 (14) ||align="center"| many ||align="center"| 4/3 ||<br />
|-<br />
| KIND || Indianapolis || USA IN || America ||align="center"| *** ||align="center"| L ||align="center"| 127.820 (7) ||align="center"| -- ||align="center"| 3/6 ||<br />
|-<br />
| KJAN || Jackson-Evers || USA MS || America ||align="center"| *** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| KJFK || [[John F. Kennedy International Airport|John F. Kennedy]] || USA NY || America ||align="center"| *** ||align="center"| L ||align="center"| 119.100 (18) ||align="center"| many ||align="center"| 4/5 ||<br />
|-<br />
| KLAS || Las Vegas || USA NV || America ||align="center"| **** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 4/3 || terminal and some casinos modeled<br />
|-<br />
| KLAX || [[Los Angeles International Airport|Los Angeles]] || USA CA || America ||align="center"| *** ||align="center"| L ||align="center"| 133.900 (7) ||align="center"| many ||align="center"| 4/8 ||<br />
|-<br />
| KLSV || [[Nellis Air Force Base|Nellis Air Force]] || USA NV || America ||align="center"| *** ||align="center"| L ||align="center"| 132.550 (6) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| KLWD || Lewistown || USA MT || America ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| KMTN || Martin State || USA MD || America ||align="center"| ** ||align="center"| M ||align="center"| 121.300 (4) ||align="center"| -- ||align="center"| 2/2 || airport and terrain modeled<br />
|-<br />
| KNID || China Lake Naval || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 120.150 (2) ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| KNUQ || Moffett Federal AFLD || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 119.550 (6) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| KOAK || Oakland || USA CA || America ||align="center"| ** ||align="center"| L ||align="center"| 127.200 (7) ||align="center"| many ||align="center"| 4/3 ||<br />
|-<br />
| KORD ||[[O'Hare International Airport|Chicago O'Hare]] || USA IL || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| many ||align="center"| 7/14 ||<br />
|-<br />
| KOSH || Wittman Rgl. || USA WI || America ||align="center"| ** ||align="center"| M ||align="center"| 118.500 (4) ||align="center"| -- ||align="center"| 4/1 ||<br />
|-<br />
| KOXB || Ocean City Muni. || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||<br />
|-<br />
| KPDX || Portland || USA OR || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 3/5 ||<br />
|-<br />
| KPHX || Phoenix || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 120.900 (6) ||align="center"| -- ||align="center"| 3/5 || most skyscrapers modeled<br />
|-<br />
| KRDU || Raleigh || USA NC || America ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (12) ||align="center"| many ||align="center"| 3/4 ||nice for flying east-coast<br />
|-<br />
| KRNO || Reno/Tahoe || USA NZ || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (7) ||align="center"| -- ||align="center"| 3/2 ||High in Clouds<br />
|-<br />
| KSAN || San Diego || USA AZ || America ||align="center"| * ||align="center"| M ||align="center"| 118.300 (7) ||align="center"| many ||align="center"| 1/2 ||Interesting area at boarder to mexico<br />
|-<br />
| KSEA || [[Seattle-Tacoma International Airport|Seattle Tacoma]] || USA WA || America ||align="center"| ** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 3/5 || basic terminal model, some skyscrapers modeled<br />
|-<br />
| KSFO || [[San Francisco International Airport|San Francisco]] || USA CA || America ||align="center"| **** ||align="center"| L ||align="center"| 120.500 (7) ||align="center"| many ||align="center"| 4/3 ||FGFS Default -- overcrowded<br />
|-<br />
| KSLC || Salt Lake City || USA UT || America ||align="center"| * ||align="center"| L ||align="center"| 118.300 (13) ||align="center"| -- ||align="center"| 4/6 ||very high in clouds (4227 ft, 1290 m)<br />
|-<br />
| KSJC || [[San Jose International Airport|San Jose]] || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 124.00 (7) ||align="center"| 14 ||align="center"| 3/2 ||Bay-area near KSFO<br />
|-<br />
| LDSP || Split || Croatia || Europe ||align="center"| ** ||align="center"| M ||align="center"| unknown ||align="center"| -- ||align="center"| 1/1 ||Small civil airport with awesome scenery neighboring.<br />
|-<br />
| LDZU || Udbina || Croatia || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||interesting airport high in Mountains - no ILS<br />
|-<br />
| LFFE || Enghien Moisselles || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| --- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just north of Paris<br />
|-<br />
| LFML || Marseille || France || Europa ||align="center"| * ||align="center"| M ||align="center"| 118.370 (4) ||align="center"| many ||align="center"| 2/2 ||Mediterranean coast<br />
|-<br />
| LFPG || Paris Charles de Gaulle || France || Europa ||align="center"| **** ||align="center"| L ||align="center"| 123.600 (23) ||align="center"| -- ||align="center"| 4/8 ||very detailed city of Paris near by<br />
|-<br />
| LFPH || Chelles Le Pin || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just south of Paris<br />
|-<br />
| LFPL || Lognes Emerainville || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||nice little airport just south of Paris<br />
|-<br />
| LFPO || Paris Orly || France || Europa ||align="center"| **** ||align="center"| M ||align="center"| 120.500 (13) ||align="center"| -- ||align="center"| 3/5 ||the older airport at Paris<br />
|-<br />
| LFPZ || St-Cyr l'Ecole || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little airport just west of Paris, near Versailles Castle<br />
|-<br />
| LFRJ || Landivisiau || France || Europa ||align="center"| ** ||align="center"| M ||align="center"| 119.700 (2) ||align="center"| -- ||align="center"| 1/1 ||Naval Base<br />
|-<br />
| LFSB || [[EuroAirport_Basel-Mulhouse-Freiburg|Basel-Mulhouse]] || Swiss || Europa ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (7) ||align="center"| 5 ||align="center"| 2/1 || Nice modelling of Terminal.<br />
|-<br />
| LHBP || Budapest || Hungaria || Europa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/4 ||in-midst the typical Puszta-area<br />
|-<br />
| LILN || Venegono || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| 128.550 (1) ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| LILV || Valbrembo || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||recreation area: Mountains, tennis, pool, etc.<br />
|-<br />
| LIMC || Milano Malpensa || Italy || Europa ||align="center"| *** ||align="center"| L ||align="center"| 119.000 (11) ||align="center"| -- ||align="center"| 2/3 ||<br />
|-<br />
| LIME || Bergamo-Orio al Serio || Italy || Europa ||align="center"| ** ||align="center"| M ||align="center"| 120.500 (5) ||align="center"| -- ||align="center"| 2/1 ||nice mountain area<br />
|-<br />
| LIML || Milano Limate || Italy || Europa ||align="center"| *** ||align="center"| M ||align="center"| 119.250 (5) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| LIMW || Aosta || Italy || Europa ||align="center"| * ||align="center"| M ||align="center"| 119.950 (1) ||align="center"| -- ||align="center"| 1/0 ||in a valley in high mountain area, fully modeled<br />
|-<br />
| LIPA || [[Aviano Air Base]] || Italy || Europe ||align="center"| * ||align="center"| L ||align="center"| 122.100 ||align="center"| -- ||align="center"| 1/1 ||Military airport with various scenery neighboring: Carnic Alps, Po Valley and the Adriatic Sea.<br />
|-<br />
| LJCE || Cerklje || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || Military airport with civilian part near Croatia<br />
|-<br />
| LJLJ || Ljubljana Brnik || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || capital of Slovenia<br />
|-<br />
| LJPZ || Portorož || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || at the adriatic sea<br />
|-<br />
| LPLA || [[Lajes Field]] || Azores, Portugal || Europe ||align="center"| * ||align="center"| L ||align="center"| 122.100 ||align="center"| -- ||align="center"| 1/1 ||Military-Civil airport with various small islands neighboring.<br />
|-<br />
| LQSA || Sarajewo || Bosnia || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.250 (3) ||align="center"| -- ||align="center"| 1/1 ||very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| LOWI || [[Innsbruck Airport|Innsbruck]] || Austria || Europe ||align="center"| **** ||align="center"| S ||align="center"| 120.100 (3) ||align="center"| -- ||align="center"| 1/1 || very nice and difficult approach, wonderful scenery<br />
|-<br />
| LROP || Bucharest || Romania || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.850 (3) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| LSGS || Sion || Swiss || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.217 (5) ||align="center"| -- ||align="center"| 1/1 ||Wonderful surrounded by high mountains<br />
|-<br />
| LSZH || Zürich-Kloten || Swiss || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.800 ||align="center"| many ||align="center"| 3/4 ||very nice mountain/lake area<br />
|-<br />
| LSZB|| Bern-Belp || Swiss || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.020 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| LSZS|| Samedan || Swiss || Europe ||align="center"| *** ||align="center"| M ||align="center"| 135,320 (3) ||align="center"| -- ||align="center"| 1/0 || Very nice high mountain region, AP at 5600 ft (1700 m)<br />
|-<br />
| PANC|| Anchorage || USA Alaska || America ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (9) ||align="center"| -- ||align="center"| 3/3 ||interesting area<br />
|-<br />
| LYBE || Belgrad || Serbia || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| LYPG || Podgorica || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.200 (2) ||align="center"| -- ||align="center"| 2/1 || very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| LYTV || Tivat || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.000 (1) ||align="center"| -- ||align="center"| 1/1 || very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| MUHA || Havana || Cuba || America ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 1/1 ||nice for island-hopping<br />
|-<br />
| NZAA || Auckland || New Zealand || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.700 ||align="center"| many ||align="center"| 2/2 ||nice for island-hopping<br />
|-<br />
| OMAA || Abu Dahbi || United AE || Asia ||align="center"| * ||align="center"| L ||align="center"| 119.200 ||align="center"| many ||align="center"| 1/2 ||interesting area<br />
|-<br />
| OOMS || Seeb || United AE || Asia ||align="center"| * ||align="center"| M ||align="center"| 118.400 (5) ||align="center"| many ||align="center"| 2/2 ||nice sea/mountain area<br />
|-<br />
| PHNL || Honolulu || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| 123.900 (5) ||align="center"| many ||align="center"| 4/2 ||wonderful island scenery<br />
|-<br />
| PHOG || Kahului || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| ||align="center"| ||align="center"| 2/1 ||wonderful island scenery<br />
|-<br />
| RJTT || [[Tokyo Haneda International Airport|Tokyo]] || Japan || Asia ||align="center"| *** ||align="center"| L ||align="center"| 126.200 (6) ||align="center"| -- ||align="center"| 3/3 ||interesting area<br />
|-<br />
| RKSI || Seoul || South Korea || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (6) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| RPLL || Manila || Philipines || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| TDPD || Melville Hall || Dominica || America ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||nice area<br />
|-<br />
| TFFF || Le Lamentin || Martinique || America ||align="center"| *** ||align="center"| M ||align="center"| 118.500 (5) ||align="center"| -- ||align="center"| 1/1 ||nice area<br />
|-<br />
| TFFG || Grand Case || Anguilla || America ||align="center"| ** ||align="center"| S ||align="center"| 128.940 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| TIST || Cyril E King || Virgin Islands || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 ||nice area<br />
|-<br />
| TJSJ || San Juan || Puerto Rico || America ||align="center"| *** ||align="center"| M ||align="center"| 132.050 (6) ||align="center"| -- ||align="center"| 2/2 ||nice area<br />
|-<br />
| TKPK || Saint Kitts || Guadeloupe || America ||align="center"| ** ||align="center"| M ||align="center"| 118.300 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| TNCM || [[Princess Juliana International Airport|Princess Juliana]] || ST Maarten || America ||align="center"| *** ||align="center"| M ||align="center"| 118.700 (2) ||align="center"| -- ||align="center"| 1/0 ||very nice area<br />
|-<br />
| TQPF || Wallblake || Anquilla || America ||align="center"| ** ||align="center"| S ||align="center"| 18.500 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| VIDP || New Dehli || India || Asia ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (5) ||align="center"| many ||align="center"| 2/3 ||nice area<br />
|-<br />
| VHHH || Hong Kong || China || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.400 (16) ||align="center"| many ||align="center"| 2/4 ||very nice mountain/sea area<br />
|-<br />
| WSSS || [[Singapore Changi International Airport|Singapore Changi]] || Singapore || Asia ||align="center"| **** ||align="center"| L ||align="center"| 118.600 (8) ||align="center"| many ||align="center"| 2/3 ||Very nice modeled from TheOmegaHangar one. Best in FlightGear<br />
|-<br />
| YBAS || Alice Springs || Australia NT || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.300 (2) ||align="center"| 26 ||align="center"| 3/1 ||Australian Back-Country<br />
|-<br />
| YBBN || Brisbane || Australia NSW || Oceania ||align="center"| *** ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||<br />
|-<br />
| YPDN || Darwin || Australia NT || Oceania ||align="center"| * ||align="center"| M ||align="center"| 133.100 (8) ||align="center"| many ||align="center"| 2/1 ||<br />
|-<br />
| YSCB || Canberra || Australia NSW || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.700 (5) ||align="center"| many ||align="center"| 2/1 ||High Mountain region (1800 ft, 550 m)<br />
|-<br />
| YSSY || [[Sydney International Airport|Sydney]] || Australia NSW || Oceania ||align="center"| * ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||<br />
|-<br />
|}<br />
<br />
{{suggested}}<br />
<br />
[[Category:Airports]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=Suggested_airports&diff=117322Suggested airports2019-02-09T14:42:04Z<p>Inetuka: </p>
<hr />
<div>Here you will find Airports that are well developed and/or have an outstanding scenery. Thus they are "suggested" especially to be visited and/or used for Multi-player events like FlyIns, TGA, ATC, etc..<br />
<br /><br /><br />
If you are searching for the '''development-status of Airports''' see the wiki [[Developed Airports]].<br />
<br />For further suggestions see [[Suggested Scenery]] and [[Suggested Flights]]<br />
<br /><br /><br />
The overall Airport-Rating (column "R") is based on the TerraSync-Status of the following characteristics:<br />
{| border="0" <br />
|-<br />
! style="text-align:center"| * !!style="text-align:left"| &nbsp;&nbsp;&nbsp; superior surrounding landscape - although the airport itself is not (yet) developed accordingly<br />
|-<br />
! style="text-align:center"| ** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; complex modeling of buildings<br />
|-<br />
! style="text-align:center"| *** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; complex modeling of buildings, taxiways, and aprons<br />
|-<br />
! style="text-align:center"| **** !!style="text-align:left"| &nbsp;&nbsp;&nbsp; extensive modeling of airport and landscape and/or city<br />
|}<br />
<br /><br />
Further columns to watch for are:<br />
* '''S = Size:''' L= all aircraft, M= midium size aircraft, S= for small aircraft<br />
* '''FGCOM:''' If available one FGCOM frequency is given, followed by the amount of the total available FGCOM frequencies<br />
* '''Parking:''' amount of pre-defined Parking-Lots (otherwise see: [[Initial Starting Positions]])<br />
* '''R/I:''' amount of runways and ILS (e.g. KROC has 3 runway: 04/22 has each 1 ILS, 10/28 has only one ILS on 28, 07/25 has no ILS)<br />
<br /><br />
{| class="wikitable sortable" border="0" cellspacing="0"<br />
! width="40" | ICAO <br />
! width="130" | Name<br />
! width="80" | Country<br />
! width="80" | Continent<br />
! width="30" | R<br />
! width="30" | S<br />
! width="100" | FGCOM<br />
! width="50" | Parking<br />
! width="40" | R/I<br />
! class="unsortable" style="background:#efefef" | Comment<br />
|-<br />
| LKKB || Praha-Kbely || Czech republic || Europe ||align="center"| *** ||align="center"| M ||align="center"| 120.87 ||align="center"| -- ||align="center"| 1/1 || request for develop it - Military Airport<br />
|-<br />
|-<br />
| BKPR || Pristina || Kosovo || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 || very nice scenery<br />
|- <br />
| CYVR || [[Vancouver International Airport|Vancouver]] || Canada || America ||align="center"| * ||align="center"| L ||align="center"| 125.650 (6) ||align="center"| many ||align="center"| 5/5 || nice area<br />
|-<br />
| EDDC || [[Dresden Airport|Dresden Airport]] || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| - ||align="center"| 2/4 || Terminal, Tower, GA Hangars and many more<br />
|- <br />
| EDDF || [[Frankfurt am Main Airport|Frankfurt am Main]] || Germany || Europe || align="center" | **** || align="center" | L || align="center" | 127.320 (6) || align="center" | many ||align="center"| 4/6 || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique skyscrapers downtown<br />
|-<br />
| EDDH || [[Hamburg Airport|Hamburg]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 126.850 (7) ||align="center"| -- ||align="center"| 2/4 || Fully modeled, plus unique buildings downtown|-<br />
|-<br />
| EDDI || [[EDDI|Berlin Tempelhof]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 118.100 (10) ||align="center"| 1 ||align="center"| 2/0 || Fully modeled, especially also the City<br />
|-<br />
| EDDK || [[EDDK|Köln/Bonn]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 124.97 (5) ||align="center"| -- ||align="center"| 3/3 || Fully modeled airport and surroundings<br />
|-<br />
| EDDL || [[Düsseldorf International Airport|Düsseldorf]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (4) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled<br />
|-<br />
| EDDP || [[Leipzig/Halle Airport|Leipzig/Halle]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 121.100 (5) ||align="center"| 2 ||align="center"| 2/4 || Tower, terminals B and C, large DHL-area modeled, inclusive [[Signs]]<br />
|-<br />
| EDDS || Stuttgart || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (8) ||align="center"| -- ||align="center"| 1/2 || Tower, terminal and [[Signs]] are fully modeled<br />
|-<br />
| EDDT || [[Berlin Tegel Airport|Berlin Tegel]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.700 (11) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]<br />
|-<br />
| EDDV || [[EDDV|Hannover]] || Germany || Europe ||align="center"| * ||align="center"| L ||align="center"| 120.170 (3)) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled<br />
|-<br />
| EDDW || Bremen || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.500 (7) ||align="center"| -- ||align="center"| 2/2 || very nicely modeled<br />
|-<br />
| EDFH || Frankfurt Hahn || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.65 (7) ||align="center"| -- ||align="center"| 1/2 || very nicely model (use Terrasync)<br />
|-<br />
| EDLN || Mönchengladbach || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| - || very nicely modeled<br />
|-<br />
| EDVE || [[Braunschweig Airport|Braunschweig]] || Germany || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.350 (2) ||align="center"| -- ||align="center"| 2/1 || <br />
|-<br />
| EDXW || Westerland Sylt || Germany || Europe ||align="center"| *** ||align="center"| M ||align="center"| 119.75 (2) ||align="center"| -- ||align="center"| 2/1 || very nicely model famous sea-resort (use Terrasync)<br />
|-<br />
| EEKE || Kuressaare || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 || <br />
|-<br />
| EFHF || Helsinki-Malmi || Finland || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 || <br />
|-<br />
| EFHK || Helsinki || Finland || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.700 (5) ||align="center"| -- ||align="center"| 3/5 || Nice terminal and city landmarks<br />
|-<br />
| EEPU || Parnu || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EETN || Tallinn || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/2 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EETU || Tartu || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU<br />
|-<br />
| EGFF || Cardiff || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 125.00 (3) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGGP || Liverpool || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.350 (4) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGGW || Luton || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.720 (6) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EGKA || Shoreham || UK || Europe ||align="center"| *** ||align="center"| S ||align="center"| 125.400 (3) ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| EGKK || [[London Gatwick Airport|London-Gatwick]] || UK || Europe ||align="center"| **** ||align="center"| M ||align="center"| 124.220 (8) ||align="center"| 6 ||align="center"| 1/2 ||<br />
|-<br />
| EGLL || London-Heathrow || UK || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.500 (14) ||align="center"| 3 ||align="center"| 2/4 ||<br />
|-<br />
| EGPH || Edinburgh || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (4) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| EGSH || Norwich || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 124.250 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| EGUN || RAF Mildenhall || UK || Europe ||align="center"| ** ||align="center"| L ||align="center"| 122.550 (5) ||align="center"| -- ||align="center"| 1/1 || USAF base for tankers and cargo planes near other military air bases like EGUL, EGYM, EGXH,... will have buildings soon. ATC is also provided.<br />
|-<br />
| EHAM || [[Amsterdam Airport Schiphol|Amsterdam]] || Netherlands || Europe ||align="center"| **** ||align="center"| L ||align="center"| 119.220 (1) ||align="center"| many ||align="center"| 6/6 ||One of the best modeled airports in the FlightGear world; most dense AI traffic.<br />
|-<br />
| EHEH || Eindhoven || Netherlands || Europe ||align="center"| ** ||align="center"| M ||align="center"| 131.000 (6) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| EHLE || [[Lelystad Airport|Lelystad]] || Netherlands || Europe ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| 1 ||align="center"| 2/1 || Basic scenery models, home of [[FSweekend]].<br />
|-<br />
| EHVK || [[Volkel Air Base|Volkel]] || Netherlands || Europe ||align="center"| ** ||align="center"| L ||align="center"| 123.170 (1) ||align="center"| many ||align="center"| 2/2 ||<br />
|-<br />
| EIDW || [[Dublin Airport|Dublin]] || Ireland || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.600 (7) ||align="center"| -- ||align="center"| 3/3 ||<br />
|-<br />
| ELLX || Luxembourg || Luxembourg || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 || very nicely model (use Terrasync)<br />
|-<br />
| ENAL || Alesund || Norway || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.100 (4) ||align="center"| -- ||align="center"| 1/1 ||<br />
|-<br />
| ENSD || Alesund || Norway || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| ENVA || Trondheim || Norway || Europe ||align="center"| *** ||align="center"| L ||align="center"| 122.100 (6) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| ESGP || Göteborg || Sweden || Europe ||align="center"| ** ||align="center"| M ||align="center"| 129.100 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| FACT || Cape Town || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/2 ||nice area<br />
|-<br />
| FAJS || Johannisburg || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 121.900 (3) ||align="center"| many ||align="center"| 2/3 ||high (5000), in mountains<br />
|-<br />
| FHAW || RAF Ascension Island AUX AF || Ascension Island || Africa ||align="center"| * ||align="center"| L ||align="center"| 126.200 (2) ||align="center"| -- ||align="center"| 1/0 ||RAF and USAF auxiliary base. Developed layout, in the middle of the Atlantic Ocean, great place for military flights.<br />
|-<br />
| GCFV || Fuerteventura || Gran Canaria || Africa ||align="center"| * ||align="center"| L ||align="center"| 119.200 (4) ||align="center"| 9 ||align="center"| 1/1 ||nice island area<br />
|-<br />
| KABQ || Albuquerque || USA NM || America ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 ||<br />
|-<br />
| HECA || Cairo || Egypt || Africa ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 || near pyramids<br />
|-<br />
| KATL || Atlanta || USA GA || America ||align="center"| * ||align="center"| L ||align="center"| 119.550 (4) ||align="center"| many ||align="center"| 3/4 ||<br />
|-<br />
| KAUS || Austin || USA TX || America ||align="center"| *** ||align="center"| L ||align="center"| 121.00 (10) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| KBWI || Baltimore || USA MD || America ||align="center"| *** ||align="center"| L ||align="center"| 119.400 (10) ||align="center"| -- ||align="center"| 4/6 ||<br />
|-<br />
| KCGS || College Park || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| 119.850 (3) ||align="center"| -- ||align="center"| 2/0 ||<br />
|-<br />
| KDCA || Reagan National || USA VA || America ||align="center"| *** ||align="center"| M ||align="center"| 120.750 (7) ||align="center"| -- ||align="center"| 3/2 ||<br />
|-<br />
| KDEN || [[Denver International Airport|Denver]] || USA CO || America ||align="center"| ** ||align="center"| L ||align="center"| 133.300 (16) ||align="center"| -- ||align="center"| 6/12 ||<br />
|-<br />
| KDTW || Detroit || USA MI || America ||align="center"| ** ||align="center"| L ||align="center"| 118.400 (15) ||align="center"| -- ||align="center"| 6/8 ||<br />
|-<br />
| KFHR || Friday Harbor || USA WA || America ||align="center"| * ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| KHAF || Half Moon Bay || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 122.800 (2) ||align="center"| 4 ||align="center"| 1/0 ||nice area - near KSFO<br />
|-<br />
| KHWD || Hayward || USA CA || America ||align="center"| ** ||align="center"| S ||align="center"| 122.500 (10) ||align="center"| 9 ||align="center"| 2/1 ||nice area - near KSFO<br />
|-<br />
| KIAD || Washington-Dulles || USA VA || America ||align="center"| * ||align="center"| L ||align="center"| 120.100 (14) ||align="center"| many ||align="center"| 4/3 ||<br />
|-<br />
| KIND || Indianapolis || USA IN || America ||align="center"| *** ||align="center"| L ||align="center"| 127.820 (7) ||align="center"| -- ||align="center"| 3/6 ||<br />
|-<br />
| KJAN || Jackson-Evers || USA MS || America ||align="center"| *** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| KJFK || [[John F. Kennedy International Airport|John F. Kennedy]] || USA NY || America ||align="center"| *** ||align="center"| L ||align="center"| 119.100 (18) ||align="center"| many ||align="center"| 4/5 ||<br />
|-<br />
| KLAS || Las Vegas || USA NV || America ||align="center"| **** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 4/3 || terminal and some casinos modeled<br />
|-<br />
| KLAX || [[Los Angeles International Airport|Los Angeles]] || USA CA || America ||align="center"| *** ||align="center"| L ||align="center"| 133.900 (7) ||align="center"| many ||align="center"| 4/8 ||<br />
|-<br />
| KLSV || [[Nellis Air Force Base|Nellis Air Force]] || USA NV || America ||align="center"| *** ||align="center"| L ||align="center"| 132.550 (6) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| KLWD || Lewistown || USA MT || America ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| KMTN || Martin State || USA MD || America ||align="center"| ** ||align="center"| M ||align="center"| 121.300 (4) ||align="center"| -- ||align="center"| 2/2 || airport and terrain modeled<br />
|-<br />
| KNID || China Lake Naval || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 120.150 (2) ||align="center"| -- ||align="center"| 3/0 ||<br />
|-<br />
| KNUQ || Moffett Federal AFLD || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 119.550 (6) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| KOAK || Oakland || USA CA || America ||align="center"| ** ||align="center"| L ||align="center"| 127.200 (7) ||align="center"| many ||align="center"| 4/3 ||<br />
|-<br />
| KORD ||[[O'Hare International Airport|Chicago O'Hare]] || USA IL || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| many ||align="center"| 7/14 ||<br />
|-<br />
| KOSH || Wittman Rgl. || USA WI || America ||align="center"| ** ||align="center"| M ||align="center"| 118.500 (4) ||align="center"| -- ||align="center"| 4/1 ||<br />
|-<br />
| KOXB || Ocean City Muni. || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||<br />
|-<br />
| KPDX || Portland || USA OR || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 3/5 ||<br />
|-<br />
| KPHX || Phoenix || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 120.900 (6) ||align="center"| -- ||align="center"| 3/5 || most skyscrapers modeled<br />
|-<br />
| KRDU || Raleigh || USA NC || America ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (12) ||align="center"| many ||align="center"| 3/4 ||nice for flying east-coast<br />
|-<br />
| KRNO || Reno/Tahoe || USA NZ || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (7) ||align="center"| -- ||align="center"| 3/2 ||High in Clouds<br />
|-<br />
| KSAN || San Diego || USA AZ || America ||align="center"| * ||align="center"| M ||align="center"| 118.300 (7) ||align="center"| many ||align="center"| 1/2 ||Interesting area at boarder to mexico<br />
|-<br />
| KSEA || [[Seattle-Tacoma International Airport|Seattle Tacoma]] || USA WA || America ||align="center"| ** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 3/5 || basic terminal model, some skyscrapers modeled<br />
|-<br />
| KSFO || [[San Francisco International Airport|San Francisco]] || USA CA || America ||align="center"| **** ||align="center"| L ||align="center"| 120.500 (7) ||align="center"| many ||align="center"| 4/3 ||FGFS Default -- overcrowded<br />
|-<br />
| KSLC || Salt Lake City || USA UT || America ||align="center"| * ||align="center"| L ||align="center"| 118.300 (13) ||align="center"| -- ||align="center"| 4/6 ||very high in clouds (4227 ft, 1290 m)<br />
|-<br />
| KSJC || [[San Jose International Airport|San Jose]] || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 124.00 (7) ||align="center"| 14 ||align="center"| 3/2 ||Bay-area near KSFO<br />
|-<br />
| LDSP || Split || Croatia || Europe ||align="center"| ** ||align="center"| M ||align="center"| unknown ||align="center"| -- ||align="center"| 1/1 ||Small civil airport with awesome scenery neighboring.<br />
|-<br />
| LDZU || Udbina || Croatia || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||interesting airport high in Mountains - no ILS<br />
|-<br />
| LFFE || Enghien Moisselles || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| --- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just north of Paris<br />
|-<br />
| LFML || Marseille || France || Europa ||align="center"| * ||align="center"| M ||align="center"| 118.370 (4) ||align="center"| many ||align="center"| 2/2 ||Mediterranean coast<br />
|-<br />
| LFPG || Paris Charles de Gaulle || France || Europa ||align="center"| **** ||align="center"| L ||align="center"| 123.600 (23) ||align="center"| -- ||align="center"| 4/8 ||very detailed city of Paris near by<br />
|-<br />
| LFPH || Chelles Le Pin || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just south of Paris<br />
|-<br />
| LFPL || Lognes Emerainville || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||nice little airport just south of Paris<br />
|-<br />
| LFPO || Paris Orly || France || Europa ||align="center"| **** ||align="center"| M ||align="center"| 120.500 (13) ||align="center"| -- ||align="center"| 3/5 ||the older airport at Paris<br />
|-<br />
| LFPZ || St-Cyr l'Ecole || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little airport just west of Paris, near Versailles Castle<br />
|-<br />
| LFRJ || Landivisiau || France || Europa ||align="center"| ** ||align="center"| M ||align="center"| 119.700 (2) ||align="center"| -- ||align="center"| 1/1 ||Naval Base<br />
|-<br />
| LFSB || [[EuroAirport_Basel-Mulhouse-Freiburg|Basel-Mulhouse]] || Swiss || Europa ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (7) ||align="center"| 5 ||align="center"| 2/1 || Nice modelling of Terminal.<br />
|-<br />
| LHBP || Budapest || Hungaria || Europa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/4 ||in-midst the typical Puszta-area<br />
|-<br />
| LILN || Venegono || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| 128.550 (1) ||align="center"| -- ||align="center"| 1/0 ||<br />
|-<br />
| LILV || Valbrembo || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||recreation area: Mountains, tennis, pool, etc.<br />
|-<br />
| LIMC || Milano Malpensa || Italy || Europa ||align="center"| *** ||align="center"| L ||align="center"| 119.000 (11) ||align="center"| -- ||align="center"| 2/3 ||<br />
|-<br />
| LIME || Bergamo-Orio al Serio || Italy || Europa ||align="center"| ** ||align="center"| M ||align="center"| 120.500 (5) ||align="center"| -- ||align="center"| 2/1 ||nice mountain area<br />
|-<br />
| LIML || Milano Limate || Italy || Europa ||align="center"| *** ||align="center"| M ||align="center"| 119.250 (5) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| LIMW || Aosta || Italy || Europa ||align="center"| * ||align="center"| M ||align="center"| 119.950 (1) ||align="center"| -- ||align="center"| 1/0 ||in a valley in high mountain area, fully modelled<br />
|-<br />
| LIPA || [[Aviano Air Base]] || Italy || Europe ||align="center"| * ||align="center"| L ||align="center"| 122.100 ||align="center"| -- ||align="center"| 1/1 ||Military airport with various scenery neighboring: Carnic Alps, Po Valley and the Adriatic Sea.<br />
|-<br />
| LJCE || Cerklje || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || Military airport with civilian part near Croatia<br />
|-<br />
| LJLJ || Ljubljana Brnik || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || capital of Slovenia<br />
|-<br />
| LJPZ || Portorož || Slovenia || Europe ||align="center"| * ||align="center"| L ||align="center"| - ||align="center"| -- ||align="center"| 1/1 || at the adriatic sea<br />
|-<br />
| LPLA || [[Lajes Field]] || Azores, Portugal || Europe ||align="center"| * ||align="center"| L ||align="center"| 122.100 ||align="center"| -- ||align="center"| 1/1 ||Military-Civil airport with various small islands neighboring.<br />
|-<br />
| LQSA || Sarajewo || Bosnia || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.250 (3) ||align="center"| -- ||align="center"| 1/1 ||very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| LOWI || [[Innsbruck Airport|Innsbruck]] || Austria || Europe ||align="center"| **** ||align="center"| S ||align="center"| 120.100 (3) ||align="center"| -- ||align="center"| 1/1 || very nice and difficult approach, wonderful scenery<br />
|-<br />
| LROP || Bucharest || Romania || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.850 (3) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| LSGS || Sion || Swiss || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.217 (5) ||align="center"| -- ||align="center"| 1/1 ||Wonderful surrounded by high mountains<br />
|-<br />
| LSZH || Zürich-Kloten || Swiss || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.800 ||align="center"| many ||align="center"| 3/4 ||very nice mountain/lake area<br />
|-<br />
| LSZB|| Bern-Belp || Swiss || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.020 (3) ||align="center"| -- ||align="center"| 2/1 ||<br />
|-<br />
| LSZS|| Samedan || Swiss || Europe ||align="center"| *** ||align="center"| M ||align="center"| 135,320 (3) ||align="center"| -- ||align="center"| 1/0 || Very nice high mountain region, AP at 5600 ft (1700 m)<br />
|-<br />
| PANC|| Anchorage || USA Alaska || America ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (9) ||align="center"| -- ||align="center"| 3/3 ||interesting area<br />
|-<br />
| LYBE || Belgrad || Serbia || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 ||<br />
|-<br />
| LYPG || Podgorica || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.200 (2) ||align="center"| -- ||align="center"| 2/1 || very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| LYTV || Tivat || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.000 (1) ||align="center"| -- ||align="center"| 1/1 || very nice mountain region: LQSA, LYTV, LYPG<br />
|-<br />
| MUHA || Havana || Cuba || America ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 1/1 ||nice for island-hopping<br />
|-<br />
| NZAA || Auckland || New Zealand || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.700 ||align="center"| many ||align="center"| 2/2 ||nice for island-hopping<br />
|-<br />
| OMAA || Abu Dahbi || United AE || Asia ||align="center"| * ||align="center"| L ||align="center"| 119.200 ||align="center"| many ||align="center"| 1/2 ||interesting area<br />
|-<br />
| OOMS || Seeb || United AE || Asia ||align="center"| * ||align="center"| M ||align="center"| 118.400 (5) ||align="center"| many ||align="center"| 2/2 ||nice sea/mountain area<br />
|-<br />
| PHNL || Honolulu || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| 123.900 (5) ||align="center"| many ||align="center"| 4/2 ||wonderful island scenery<br />
|-<br />
| PHOG || Kahului || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| ||align="center"| ||align="center"| 2/1 ||wonderful island scenery<br />
|-<br />
| RJTT || [[Tokyo Haneda International Airport|Tokyo]] || Japan || Asia ||align="center"| *** ||align="center"| L ||align="center"| 126.200 (6) ||align="center"| -- ||align="center"| 3/3 ||interesting area<br />
|-<br />
| RKSI || Seoul || South Korea || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (6) ||align="center"| -- ||align="center"| 2/4 ||<br />
|-<br />
| RPLL || Manila || Philipines || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||<br />
|-<br />
| TDPD || Melville Hall || Dominica || America ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||nice area<br />
|-<br />
| TFFF || Le Lamentin || Martinique || America ||align="center"| *** ||align="center"| M ||align="center"| 118.500 (5) ||align="center"| -- ||align="center"| 1/1 ||nice area<br />
|-<br />
| TFFG || Grand Case || Anguilla || America ||align="center"| ** ||align="center"| S ||align="center"| 128.940 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| TIST || Cyril E King || Virgin Islands || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 ||nice area<br />
|-<br />
| TJSJ || San Juan || Puerto Rico || America ||align="center"| *** ||align="center"| M ||align="center"| 132.050 (6) ||align="center"| -- ||align="center"| 2/2 ||nice area<br />
|-<br />
| TKPK || Saint Kitts || Guadeloupe || America ||align="center"| ** ||align="center"| M ||align="center"| 118.300 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| TNCM || [[Princess Juliana International Airport|Princess Juliana]] || ST Maarten || America ||align="center"| *** ||align="center"| M ||align="center"| 118.700 (2) ||align="center"| -- ||align="center"| 1/0 ||very nice area<br />
|-<br />
| TQPF || Wallblake || Anquilla || America ||align="center"| ** ||align="center"| S ||align="center"| 18.500 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area<br />
|-<br />
| VIDP || New Dehli || India || Asia ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (5) ||align="center"| many ||align="center"| 2/3 ||nice area<br />
|-<br />
| VHHH || Hong Kong || China || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.400 (16) ||align="center"| many ||align="center"| 2/4 ||very nice mountain/sea area<br />
|-<br />
| WSSS || [[Singapore Changi International Airport|Singapore Changi]] || Singapore || Asia ||align="center"| **** ||align="center"| L ||align="center"| 118.600 (8) ||align="center"| many ||align="center"| 2/3 ||Very nice modelled from TheOmegaHangar one. Best in FlightGear<br />
|-<br />
| YBAS || Alice Springs || Australia NT || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.300 (2) ||align="center"| 26 ||align="center"| 3/1 ||Australian Back-Country<br />
|-<br />
| YBBN || Brisbane || Australia NSW || Oceania ||align="center"| *** ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||<br />
|-<br />
| YPDN || Darwin || Australia NT || Oceania ||align="center"| * ||align="center"| M ||align="center"| 133.100 (8) ||align="center"| many ||align="center"| 2/1 ||<br />
|-<br />
| YSCB || Canberra || Australia NSW || Oceania ||align="center"| * ||align="center"| M ||align="center"| 118.700 (5) ||align="center"| many ||align="center"| 2/1 ||High Mountain region (1800 ft, 550 m)<br />
|-<br />
| YSSY || [[Sydney International Airport|Sydney]] || Australia NSW || Oceania ||align="center"| * ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||<br />
|-<br />
|}<br />
<br />
{{suggested}}<br />
<br />
[[Category:Airports]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2017&diff=108009FlightGear Newsletter May 20172017-06-06T12:08:55Z<p>Inetuka: /* MapGear is out! */</p>
<hr />
<div><br />
{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community.<br>You can read the latest newsletter at [[FlightGear Newsletter May 2017]].}}<br />
<br />
{{Newsletter-header|May 2017}} <!-- change month and year as required--><br />
<div style="border-bottom:3px double #BBB;"><br />
{| width="100%" |<br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Development news}}<br><br />
{{Newsletter-cover-header|In the hangar}}<br><br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Scenery Corner}}<br><br />
{{Newsletter-cover-header|Community News}}<br><br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Contributing}}<br><br />
[[#Translators required|Translators required]]<br><br />
[[#FlightGear logos|FlightGear logos]]<br><br />
[[#Screenshots|Screenshots]]<br><br />
<small>[[#Screenshot of the Month|Screenshot of the Month]]</small><br />
|}</div><br />
<br />
== Development news ==<br />
===MapGear is out!===<br />
<br />
MapGear.py is a mapping tool for FlightGear that saves the flight path as an animated .GIF.<br />
<br />
The aim is to create a nice map projection/animation for any log file submitted. For this to happen a <br />
good degree of numerical tuning is required so the more feedback the project has from users the better.<br />
Feedback would be greatly appreciated! <br />
<br />
So far the program seems to be stable enough, so it is worth publishing here in the FlightGear Newsletter.<br />
<br />
It consists of a small python script and a few Geo information data files taken from NaturalEarth. <br />
<br />
Stay tuned via the announcement page:<br />
https://forum.flightgear.org/viewtopic.php?f=6&t=31741<br />
<br />
Screenshot:<br />
[img]http://i.imgur.com/cUuza9l.gif[/img]<br />
<br />
Licensed under the GPLv2+<br />
<br />
== In the hangar ==<br />
<br />
== Scenery corner ==<br />
=== USA airports ===<br />
{{usr|Catalanoic}} has added buildings and 3D objects to Boston Logan Intl Airport (KBOS) for next default airport shipped under new [[Changelog 2017.2|FlightGear 2017.2]]. Some other recently developed airports include Norfolk Intl (KORF) and Portland Jetport (KPWM).<br />
<br />
== Community news ==<br />
<br />
== Contributing ==<br />
=== Translators required ===<br />
{|<br />
| [[File:en.gif]]<br />
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].<br />
|-<br />
| [[File:fr.gif]]<br />
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].<br />
|-<br />
| [[File:de.gif]]<br />
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
| [[File:nl.gif]]<br />
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
| [[File:es.gif]]<br />
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|-<br />
| [[File:cat.gif]]<br />
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].<br />
|-<br />
| [[File:pt.gif]]<br />
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].<br />
|-<br />
| [[File:zh.gif]]<br />
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].<br />
|}<br />
<br />
=== FlightGear logos ===<br />
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.<br />
<br />
=== Screenshots ===<br />
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].<br />
<br />
==== Screenshot of the Month ====<br />
Entries for this month's best screenshot can be submitted to [https://forum.flightgear.org/viewtopic.php?f=19&t=32163 this] <!-- link to SOTM topic --> forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=32163#p310086 first post] <!-- link to first post of SOTM topic --> for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented on this page. <!-- Edit this when the SOTM topic for this month has been created --><br />
<br />
<!-- FlightGear's Screenshot of the Month May 2017 is ''TITLE'' by AUTHOR<br />
[[File:|900px|center|TITLE]] --> <!-- Uncomment/edit this when the winner is chosen --><br />
<br />
<br />
<!-- If you want to participate in the screenshot contest of *NEXTMONTH*, you can submit your candidate to [ this] forum topic. Be sure to see the [ first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter edition of *NEXTMONTH*. --> <!-- Uncomment/edit this when the SOTM topic for the following month has been created --><br />
<br />
<!-- [[Category:FlightGear Newsletter|2017 5]] change year and month as necessary --><br />
<!-- [[Category:Changes after 3.6]] change version as necessary --><br />
<br />
[[De:FlightGear Newsletter Mai 2017]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2017&diff=108008FlightGear Newsletter May 20172017-06-06T12:05:18Z<p>Inetuka: /* MapGear is out! */</p>
<hr />
<div><br />
{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community.<br>You can read the latest newsletter at [[FlightGear Newsletter May 2017]].}}<br />
<br />
{{Newsletter-header|May 2017}} <!-- change month and year as required--><br />
<div style="border-bottom:3px double #BBB;"><br />
{| width="100%" |<br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Development news}}<br><br />
{{Newsletter-cover-header|In the hangar}}<br><br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Scenery Corner}}<br><br />
{{Newsletter-cover-header|Community News}}<br><br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Contributing}}<br><br />
[[#Translators required|Translators required]]<br><br />
[[#FlightGear logos|FlightGear logos]]<br><br />
[[#Screenshots|Screenshots]]<br><br />
<small>[[#Screenshot of the Month|Screenshot of the Month]]</small><br />
|}</div><br />
<br />
== Development news ==<br />
===MapGear is out!===<br />
<br />
MapGear.py is a mapping tool for FlightGear that saves the flight path as an animated .GIF.<br />
<br />
The aim is to create a nice map projection/animation for any log file submitted. For this to happen a <br />
good degree of numerical tuning is required so the more feedback the project has from users the better.<br />
Feedback would be greatly appreciated! <br />
<br />
So far, the program seems to be stable enough so it is worth of publishing here in the FlightGear Newsletter.<br />
<br />
It consists of a small python script and a few Geo information data files taken from NaturalEarth. <br />
<br />
Stay tuned via the announcement page:<br />
https://forum.flightgear.org/viewtopic.php?f=6&t=31741<br />
<br />
Screenshot:<br />
[img]http://i.imgur.com/cUuza9l.gif[/img]<br />
<br />
Licensed under the GPLv2+<br />
<br />
== In the hangar ==<br />
<br />
== Scenery corner ==<br />
=== USA airports ===<br />
{{usr|Catalanoic}} has added buildings and 3D objects to Boston Logan Intl Airport (KBOS) for next default airport shipped under new [[Changelog 2017.2|FlightGear 2017.2]]. Some other recently developed airports include Norfolk Intl (KORF) and Portland Jetport (KPWM).<br />
<br />
== Community news ==<br />
<br />
== Contributing ==<br />
=== Translators required ===<br />
{|<br />
| [[File:en.gif]]<br />
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].<br />
|-<br />
| [[File:fr.gif]]<br />
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].<br />
|-<br />
| [[File:de.gif]]<br />
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
| [[File:nl.gif]]<br />
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
| [[File:es.gif]]<br />
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|-<br />
| [[File:cat.gif]]<br />
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].<br />
|-<br />
| [[File:pt.gif]]<br />
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].<br />
|-<br />
| [[File:zh.gif]]<br />
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].<br />
|}<br />
<br />
=== FlightGear logos ===<br />
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.<br />
<br />
=== Screenshots ===<br />
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].<br />
<br />
==== Screenshot of the Month ====<br />
Entries for this month's best screenshot can be submitted to [https://forum.flightgear.org/viewtopic.php?f=19&t=32163 this] <!-- link to SOTM topic --> forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=32163#p310086 first post] <!-- link to first post of SOTM topic --> for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented on this page. <!-- Edit this when the SOTM topic for this month has been created --><br />
<br />
<!-- FlightGear's Screenshot of the Month May 2017 is ''TITLE'' by AUTHOR<br />
[[File:|900px|center|TITLE]] --> <!-- Uncomment/edit this when the winner is chosen --><br />
<br />
<br />
<!-- If you want to participate in the screenshot contest of *NEXTMONTH*, you can submit your candidate to [ this] forum topic. Be sure to see the [ first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter edition of *NEXTMONTH*. --> <!-- Uncomment/edit this when the SOTM topic for the following month has been created --><br />
<br />
<!-- [[Category:FlightGear Newsletter|2017 5]] change year and month as necessary --><br />
<!-- [[Category:Changes after 3.6]] change version as necessary --><br />
<br />
[[De:FlightGear Newsletter Mai 2017]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=EuroAirport_Basel-Mulhouse-Freiburg&diff=106575EuroAirport Basel-Mulhouse-Freiburg2017-01-03T15:01:59Z<p>Inetuka: /* ATC */</p>
<hr />
<div>{{infobox Airport<br />
|name = EuroAirport Basel-Mulhouse-Freiburg<br />
|image = LFSB.png<br />
|iata = BSL/MLH/EAP<br />
|icao = LFSB (LSZM)<br />
|type = Public<br />
|owner = Several<br />
|city = Saint-Louis, Haut-Rhin, Alsace, France<br />
|website = http://www.euroairport.com/en/<br />
|runway = 15/33<br />
|length =3900 m<br />
|material = Concrete<br />
|runway2 = 26/08<br />
|length2= 1820 m <br />
|material2 = Concrete<br />
|runway3 = 15R/33L<br />
|length3= 630 m<br />
|material3 = Grass<br />
}}<br />
<br />
'''EuroAirport Basel-Mulhouse-Freiburg''' (de: Flughafen Basel-Mülhausen-Freiburg; fr: Aéroport de Bâle-Mulhouse Fribourg), also known as '''EuroAirport''' or simply '''Basel-Mulhouse''' is the international airport that serves the city of Basel (CH), Mulhouse (F) and Freiburg (D). It's 6Km (3.7mi) North-west of Basel, 30Km (18Mi) South-east of Mulhouse and 77Km (47mi) South-west of Freiburg.<br />
<br />
Basel-Mulhouse-Freiburg is the only developed airport in [[FlightGear]] that is operated by 2 countries (Switzerland and France), hence the name "EuroAirport". The Airport lies completely on French soil (with public transport connections from Switzerland operated by SBB <nowiki>[Swiss Federal Railworks]</nowiki> and a local bus line from Basel), but the airport is categorized as a Swiss airport. The reason why is due to a 1949 treaty with France which allowed Switzerland to build the airport on French soil.<br />
<br />
Because of the EuroAirport being bi-national, it has 3 [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATAs]: BSL (The Swiss code for Basel), MLH (The French code for Mulhouse) and EAP (international code for EuroAirport). This airport has a state similar to [[LSGG|Geneva's Airport]], excluding the multiple [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATAs]. Its [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO] code is LFSB.<br />
<br />
== Navigation ==<br />
=== Start-up ===<br />
{{note|The grass runways are ''merely'' for special events/recreation, or can be requested in the pilot's behalf, if one wishes according to its aircraft.}}<br />
<br />
There are 5 start-up positions, which are the 5 [http://en.wikipedia.org/wiki/Helipad helipads], the actual gates have to be added, so we ask you to start-up here. Then push back to a gate of choice on Terminal 1 (the currently only developed one, although 2 exist). After that, you can ask the tower for start up and other normal procedures.<br />
<br />
LFSB has "6" runways, tough only 4 are used (as cited above). <br />
<br />
=== Runway 15/33 ===<br />
{{caution|High terrain in the area (the Jura mountains). Maintain at least FL050.}}<br />
<br />
[[Instrument_Landing_System|ILS cat IIIb]] runway approach and landing is available for runway 15 with SSALR - PAPI-4L lights. This is the main landing runway (GS=3.00°). <br />
<br />
Tune your navigation radio 1 to 111.55MHz with a heading of 153° (MH).<br />
<br />
[[Instrument_Landing_System|ILS cat I/DME]] runway approach and landing is available for runway 33 with SSALR - PAPI-4L lights. This is mainly used for take-off's in low traffic situations, but in case of bad weather, can be used to land as well (GS=3.50°).<br />
<br />
Tune your navigation radio 1 to 109.35MHz with a heading of 333° (IBLU) and your navigation radio 2 to DME 117.45 (BLM). Use the charts for approach (see below).<br />
<br />
=== Runway 08/26 ===<br />
[[Instrument_Landing_System|ILS]] runway approach and landing is NOT available for runway 08. No landings are made on runway 08, because it has only Calvert lightning. Used for small planes take-off only.<br />
<br />
[[Instrument_Landing_System|ILS]] runway approach and landing is NOT available for runway 26. This runway is mainly used for landings for small planes. In case of intense traffic it can be used for take-off's as well. Do a manual approach, Calvert - PAPI-4L lights available.<br />
<br />
=== ATC ===<br />
ATC tower is served irregularly, most likely on Fridays, Saturdays and Sundays. Vacation times are most likely to have full time (night) service. You can book a flight and check when is the controller online [http://flightgear-atc.alwaysdata.net here]. ATC serviced provided by [[User:Thefan|LFSB-Tower]].<br />
<br />
Mumble is used as main [http://en.wikipedia.org/wiki/Voice_over_IP VoIP] communication method, look [http://www.emmerich-j.de/Mumble/mumble.html here] for instructions. [[FGCom]] is no longer supported. For [http://en.wikipedia.org/wiki/Automatic_Terminal_Information_Service ATIS], tune to 127.87MHz. For more frequencies, look bellow.<br />
<br />
== See also ==<br />
* [[Suggested_Airports|Suggested Airports]]<br />
<br />
== External links ==<br />
* [http://flightgear-atc.alwaysdata.net/ See future upcoming ATC events]<br />
* [http://www.vatroute.net/web_showfp.php?dest=LFSB Arriving] and [http://www.vatroute.net/web_showfp.php?dep=LFSB departing] LFSB<br />
* [http://www.vacc.ch/en/airports_and_charts/LFSB Charts]<br />
* [http://mpserver12.flightgear.org/tracker/airport/LFSB/ Airport details at mpserver12]<br />
<br />
[[Category:Airports in France]]<br />
[[Category:Airports in Switzerland]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=EuroAirport_Basel-Mulhouse-Freiburg&diff=106574EuroAirport Basel-Mulhouse-Freiburg2017-01-03T14:57:56Z<p>Inetuka: </p>
<hr />
<div>{{infobox Airport<br />
|name = EuroAirport Basel-Mulhouse-Freiburg<br />
|image = LFSB.png<br />
|iata = BSL/MLH/EAP<br />
|icao = LFSB (LSZM)<br />
|type = Public<br />
|owner = Several<br />
|city = Saint-Louis, Haut-Rhin, Alsace, France<br />
|website = http://www.euroairport.com/en/<br />
|runway = 15/33<br />
|length =3900 m<br />
|material = Concrete<br />
|runway2 = 26/08<br />
|length2= 1820 m <br />
|material2 = Concrete<br />
|runway3 = 15R/33L<br />
|length3= 630 m<br />
|material3 = Grass<br />
}}<br />
<br />
'''EuroAirport Basel-Mulhouse-Freiburg''' (de: Flughafen Basel-Mülhausen-Freiburg; fr: Aéroport de Bâle-Mulhouse Fribourg), also known as '''EuroAirport''' or simply '''Basel-Mulhouse''' is the international airport that serves the city of Basel (CH), Mulhouse (F) and Freiburg (D). It's 6Km (3.7mi) North-west of Basel, 30Km (18Mi) South-east of Mulhouse and 77Km (47mi) South-west of Freiburg.<br />
<br />
Basel-Mulhouse-Freiburg is the only developed airport in [[FlightGear]] that is operated by 2 countries (Switzerland and France), hence the name "EuroAirport". The Airport lies completely on French soil (with public transport connections from Switzerland operated by SBB <nowiki>[Swiss Federal Railworks]</nowiki> and a local bus line from Basel), but the airport is categorized as a Swiss airport. The reason why is due to a 1949 treaty with France which allowed Switzerland to build the airport on French soil.<br />
<br />
Because of the EuroAirport being bi-national, it has 3 [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATAs]: BSL (The Swiss code for Basel), MLH (The French code for Mulhouse) and EAP (international code for EuroAirport). This airport has a state similar to [[LSGG|Geneva's Airport]], excluding the multiple [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATAs]. Its [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO] code is LFSB.<br />
<br />
== Navigation ==<br />
=== Start-up ===<br />
{{note|The grass runways are ''merely'' for special events/recreation, or can be requested in the pilot's behalf, if one wishes according to its aircraft.}}<br />
<br />
There are 5 start-up positions, which are the 5 [http://en.wikipedia.org/wiki/Helipad helipads], the actual gates have to be added, so we ask you to start-up here. Then push back to a gate of choice on Terminal 1 (the currently only developed one, although 2 exist). After that, you can ask the tower for start up and other normal procedures.<br />
<br />
LFSB has "6" runways, tough only 4 are used (as cited above). <br />
<br />
=== Runway 15/33 ===<br />
{{caution|High terrain in the area (the Jura mountains). Maintain at least FL050.}}<br />
<br />
[[Instrument_Landing_System|ILS cat IIIb]] runway approach and landing is available for runway 15 with SSALR - PAPI-4L lights. This is the main landing runway (GS=3.00°). <br />
<br />
Tune your navigation radio 1 to 111.55MHz with a heading of 153° (MH).<br />
<br />
[[Instrument_Landing_System|ILS cat I/DME]] runway approach and landing is available for runway 33 with SSALR - PAPI-4L lights. This is mainly used for take-off's in low traffic situations, but in case of bad weather, can be used to land as well (GS=3.50°).<br />
<br />
Tune your navigation radio 1 to 109.35MHz with a heading of 333° (IBLU) and your navigation radio 2 to DME 117.45 (BLM). Use the charts for approach (see below).<br />
<br />
=== Runway 08/26 ===<br />
[[Instrument_Landing_System|ILS]] runway approach and landing is NOT available for runway 08. No landings are made on runway 08, because it has only Calvert lightning. Used for small planes take-off only.<br />
<br />
[[Instrument_Landing_System|ILS]] runway approach and landing is NOT available for runway 26. This runway is mainly used for landings for small planes. In case of intense traffic it can be used for take-off's as well. Do a manual approach, Calvert - PAPI-4L lights available.<br />
<br />
=== ATC ===<br />
ATC tower is served irregularly, most likely on Fridays, Saturdays and Sundays. Vacation times are most likely to have full time (night) service. You can book a flight and check when is the controller online [http://flightgear-atc.alwaysdata.net/V4/index.php5 here]. ATC serviced provided by [[User:Thefan|LFSB-Tower]].<br />
<br />
Mumble is used as main [http://en.wikipedia.org/wiki/Voice_over_IP VoIP] communication method, look [http://www.emmerich-j.de/Mumble/mumble.html here] for instructions. [[FGCom]] is no longer supported. For [http://en.wikipedia.org/wiki/Automatic_Terminal_Information_Service ATIS], tune to 127.87MHz. For more frequencies, look bellow.<br />
<br />
== See also ==<br />
* [[Suggested_Airports|Suggested Airports]]<br />
<br />
== External links ==<br />
* [http://flightgear-atc.alwaysdata.net/ See future upcoming ATC events]<br />
* [http://www.vatroute.net/web_showfp.php?dest=LFSB Arriving] and [http://www.vatroute.net/web_showfp.php?dep=LFSB departing] LFSB<br />
* [http://www.vacc.ch/en/airports_and_charts/LFSB Charts]<br />
* [http://mpserver12.flightgear.org/tracker/airport/LFSB/ Airport details at mpserver12]<br />
<br />
[[Category:Airports in France]]<br />
[[Category:Airports in Switzerland]]</div>Inetukahttps://wiki.flightgear.org/w/index.php?title=EuroAirport_Basel-Mulhouse-Freiburg&diff=106573EuroAirport Basel-Mulhouse-Freiburg2017-01-03T14:54:33Z<p>Inetuka: </p>
<hr />
<div>{{infobox Airport<br />
|name = EuroAirport Basel-Mulhouse-Freiburg<br />
|image = LFSB.png<br />
|iata = BSL/MLH/EAP<br />
|icao = LFSB (LSZM)<br />
|type = Public<br />
|owner = Several<br />
|city = Saint-Louis, Haut-Rhin, Alsace, France<br />
|website = http://www.euroairport.com/en/<br />
|runway = 15/33<br />
|length =3900 m<br />
|material = Concrete<br />
|runway2 = 26/08<br />
|length2= 1820 m <br />
|material2 = Concrete<br />
|runway3 = 15R/33L<br />
|length3= 630 m<br />
|material3 = Grass<br />
}}<br />
<br />
'''EuroAirport Basel-Mulhouse-Freiburg''' (de: Flughafen Basel-Mülhausen-Freiburg; fr: Aéroport de Bâle-Mulhouse Fribourg), also known as '''EuroAirport''' or simply '''Basel-Mulhouse''' is the international airport that serves the city of Basel (CH), Mulhouse (F) and Freiburg (D). It's 6Km (3.7mi) North-west of Basel, 30Km (18Mi) South-east of Mulhouse and 77Km (47mi) South-west of Freiburg.<br />
<br />
Basel-Mulhouse-Freiburg is the only developed airport in [[FlightGear]] that is operated by 2 countries (Switzerland and France), hence the name "EuroAirport". The Airport lies completely in French soil (with public transport connections from Switzerland operated by SBB <nowiki>[Swiss Federal Railworks]</nowiki> and a local Bus line from Basel), but the airport is categorized as a Swiss airport. The reason why is due to a 1949 treaty with France which allowed Switzerland to build the airport in French soil.<br />
<br />
Because of the EuroAirport being bi-national, it has 3 [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATAs]: BSL (The Swiss code for Basel), MLH (The French code for Mulhouse) and EAP (international code for EuroAirport). This airport has a similar state to [[LSGG|Geneva's Airport]], excluding the multiple [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATAs]. Its [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO] code is LFSB.<br />
<br />
== Navigation ==<br />
=== Start-up ===<br />
{{note|The grass runways are ''merely'' for special events/recreation, or can be requested in the pilot's behalf, if one wishes according to its aircraft.}}<br />
<br />
There are 5 start-up positions, which are the 5 [http://en.wikipedia.org/wiki/Helipad helipads], the actual gates have to be added, so we ask you to start-up here. Then push back to a gate of choice on Terminal 1 (the currently only developed one, although 2 exist). After that, you can ask the tower for start up and other normal procedures.<br />
<br />
LFSB has "6" runways, tough only 4 are used (as cited above). <br />
<br />
=== Runway 15/33 ===<br />
{{caution|High terrain in the area (the Jura mountains). Maintain at least FL050.}}<br />
<br />
[[Instrument_Landing_System|ILS cat IIIb]] runway approach and landing is available for runway 15 with SSALR - PAPI-4L lights. This is the main landing runway (GS=3.00°). <br />
<br />
Tune your navigation radio 1 to 111.55MHz with a heading of 153° (MH).<br />
<br />
[[Instrument_Landing_System|ILS cat I/DME]] runway approach and landing is available for runway 33 with SSALR - PAPI-4L lights. This is mainly used for take-off's in low traffic situations, but in case of bad weather, can be used to land as well (GS=3.50°).<br />
<br />
Tune your navigation radio 1 to 109.35MHz with a heading of 333° (IBLU) and your navigation radio 2 to DME 117.45 (BLM). Use the charts for approach (see below).<br />
<br />
=== Runway 08/26 ===<br />
[[Instrument_Landing_System|ILS]] runway approach and landing is NOT available for runway 08. No landings are made on runway 08, because it has only Calvert lightning. Used for small planes take-off only.<br />
<br />
[[Instrument_Landing_System|ILS]] runway approach and landing is NOT available for runway 26. This runway is mainly used for landings for small planes. In case of intense traffic it can be used for take-off's as well. Do a manual approach, Calvert - PAPI-4L lights available.<br />
<br />
=== ATC ===<br />
ATC tower is served irregularly, most likely on Fridays, Saturdays and Sundays. Vacation times are most likely to have full time (night) service. You can book a flight and check when is the controller online [http://flightgear-atc.alwaysdata.net/V4/index.php5 here]. ATC serviced provided by [[User:Thefan|LFSB-Tower]].<br />
<br />
Mumble is used as main [http://en.wikipedia.org/wiki/Voice_over_IP VoIP] communication method, look [http://www.emmerich-j.de/Mumble/mumble.html here] for instructions. [[FGCom]] is no longer supported. For [http://en.wikipedia.org/wiki/Automatic_Terminal_Information_Service ATIS], tune to 127.87MHz. For more frequencies, look bellow.<br />
<br />
== See also ==<br />
* [[Suggested_Airports|Suggested Airports]]<br />
<br />
== External links ==<br />
* [http://flightgear-atc.alwaysdata.net/ See future upcoming ATC events]<br />
* [http://www.vatroute.net/web_showfp.php?dest=LFSB Arriving] and [http://www.vatroute.net/web_showfp.php?dep=LFSB departing] LFSB<br />
* [http://www.vacc.ch/en/airports_and_charts/LFSB Charts]<br />
* [http://mpserver12.flightgear.org/tracker/airport/LFSB/ Airport details at mpserver12]<br />
<br />
[[Category:Airports in France]]<br />
[[Category:Airports in Switzerland]]</div>Inetuka