652
edits
OpenRadarGuide: Difference between revisions
Jump to navigation
Jump to search
m
→Runway Settings: reworded according to new design
m (→MPchat area: update to newest design) |
m (→Runway Settings: reworded according to new design) |
||
| Line 252: | Line 252: | ||
====='''Runway Settings'''===== | ====='''Runway Settings'''===== | ||
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The | [[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]] | ||
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 values to support your | [[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager]] | ||
*From top to bottom OpenRadar lists all runways | 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 findings and/or informations pilots may ask you about. See e.g. the picture on the right: | ||
*From left to right you see the following informations (if available): | *From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. See the picture "OpenRadar-Runway-Settings", e.g. see the 07C <small>''(you open that by a right mouseclick onto the runway-name (07C))''</small>: | ||
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well "Starting" as also "Landing". In the given example for EDDF there is a complication: Per Law you are forbidden | |||
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear | |||
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears | |||
:::<small>''(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> | |||
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' 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"! | |||
:*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!)''. | |||
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways. | |||
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow! | |||
*From left to right you see the following informations for each runway (if available): | |||
:*The runway-name | :*The runway-name | ||
:*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) | :*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) | ||
:* | :*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! | ||
:* | :*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> | ||
:* | :*To the right follows | ||
::*in the upper line the exact runway heading (as needed for older type autopilots) | ::*in the upper line the exact runway heading (as needed for older type autopilots) | ||
::*in the lower line the length and width of the runway in feet! | ::*in the lower line the length and width of the runway in feet! | ||
:* | :*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. | ||
====='''Flight Strip Manager'''===== | ====='''Flight Strip Manager'''===== | ||