FlightGear wiki - User contributions [en]

Historic navigation

2025-11-26T14:50:19Z

Www2:

== Navaids historic ==

=== Beacon ===

=== Radio ===
MLS

=== Hyperbolic navigation ===
* Gee
* Omega
* Decca Navigator
* LORAN
* LORAN-C
* Alpha

== Navaids current ==

=== Radio ===
* NDB
* ILS
* VOR/DME/TACAN
* Marker

=== Rnav ===
* GLS/GBAS/SBAS
* GPS/NAVSTAR
* GLONASS
* Galileo
* BeiDou

== Airports canidates ==
This is a list
=== Close ===
For foaling is a list of airports that are close that are good candidates for this project.
* Kai Tak Hong Kong (VHHX/VHXX)
* Tempelhof Berlin Germany (EDDI)

=== Open ===
==== Test area ====
This are a list of airport that can be use for testing.
* Homey Airport Nevada USA (KXTA)
This airport is also known as area 51 and is a good place to testing the navaids.

==== Current ====

==== Addons ====

Historic navigation

2025-11-25T19:52:00Z

Www2:

Historic navigation

2025-11-25T19:46:34Z

Www2: add some list of for navaids support

== Navaids historic ==

=== Beacon ===

=== Radio ===

=== Hyperbolic navigation ===
Gee
Omega
Decca Navigator
LORAN
LORAN-C
Alpha

== Navaids current ==

=== Radio ===
NDB
ILS
VOR/DME/TACAN
Marker

=== Rnav ===
GPS/GLS/GBAS/SBAS

Historic navigation

2025-11-25T18:46:28Z

Www2: create a stub page for later use

This plage is a stub

Howto:Develop an aircraft transponder in Nasal

2025-09-07T20:35:29Z

Www2: update source to the original article

{{Stub}}

Status: Planning

Last updated: 12/2010

Authors: Algernon, Hooray

References: {{forum link|t=6395|text=Transponder}} thread (FlightGear forum).

This tutorial will document all the steps involved in developing a multiplayer-enabled aircraft transponder system in [[Nasal]], FlightGear's scripting language.

This tutorial involves processing multiplayer properties under /ai/models/multiplayer - you may want to refer to [[Howto: Working with AI and MP properties]] for an introduction.

* http://en.wikipedia.org/wiki/Transponder_%28aviation%29
* http://www.aeroelectric.com/articles/Altitude_Encoding/modec.htm

[[Category:Multiplayer]]
[[Category:Nasal howto|Transponder, Develop an aircraft in Nasal]]

Howto:Develop an aircraft transponder in Nasal

2025-08-03T16:16:55Z

Www2: add back www.airsport-corp.com/modec.htm but using internet archive wayback machine

{{Stub}}

Status: Planning

Last updated: 12/2010

Authors: Algernon, Hooray

References: {{forum link|t=6395|text=Transponder}} thread (FlightGear forum).

This tutorial will document all the steps involved in developing a multiplayer-enabled aircraft transponder system in [[Nasal]], FlightGear's scripting language.

This tutorial involves processing multiplayer properties under /ai/models/multiplayer - you may want to refer to [[Howto: Working with AI and MP properties]] for an introduction.

* http://en.wikipedia.org/wiki/Transponder_%28aviation%29
* https://web.archive.org/web/20080623202136/http://www.airsport-corp.com/modec.htm

[[Category:Multiplayer]]
[[Category:Nasal howto|Transponder, Develop an aircraft in Nasal]]

FlightGear Newsletter July 2025

2025-07-06T18:23:12Z

Www2: Newsletter creation, automatic preload from here for July 2025

{{User:Skybike/Template:Newsletter-header-translate|2025-06}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==






== In the hangar ==









== Scenery corner ==




















== Community news ==









== Multiplayer events ==









== Screenshot of the Month ==

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 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.

{{Appendix}}

[[Category:Changes after 2024.1]]
[[Category:FlightGear Newsletter|2025 06]]

FlightGear Newsletter May 2025

2025-07-06T18:20:35Z

Www2: Add No news letter nodification for May 2025

{{User:Skybike/Template:Newsletter-header-translate|2025-05}}
{{TOC_right|limit=2}}

No News letter for May 2025

''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==






== In the hangar ==









== Scenery corner ==




















== Community news ==









== Multiplayer events ==









== Screenshot of the Month ==

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 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.

{{Appendix}}

[[Category:Changes after 2024.1]]
[[Category:FlightGear Newsletter|2025 05]]

FlightGear Newsletter May 2025

2025-07-06T18:17:13Z

Www2: Newsletter creation, automatic preload from here

{{User:Skybike/Template:Newsletter-header-translate|2025-05}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==






== In the hangar ==









== Scenery corner ==




















== Community news ==









== Multiplayer events ==









== Screenshot of the Month ==

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 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.

{{Appendix}}

[[Category:Changes after 2024.1]]
[[Category:FlightGear Newsletter|2025 05]]

Aircraft properties reference

2024-04-18T00:26:34Z

Www2: /* Instrumentation */

{{PropertyTree}}

This is a generic '''aircraft properties reference'''. There are many properties that are very common in aircraft, and many of them are present even in a very simple aircraft. However, a complete description that matches all the properties is very unlikely to be written, as aircraft can be very different from each other.

{{TOC limit|2}}

== What are properties? ==
{{main article|Property tree}}
=== The property tree ===
Most parts of FlightGear communicate with each other through key-value pair properties in the [[property tree]]. The properties represent both the input from the pilot, the values determining the position and velocity of the aircraft, the values used for animating the aircraft, and pretty much anything else.

While many properties will be common between most aircraft, many properties will also be different between aircraft. This becomes obvious if one consider the many different configurations (aircraft/helicopter/car, control surface and landing gear layout, number and locations of engines, etc) and propulsions systems (types of engines, types of fuels etc.) an aircraft can have. There are also different flight dynamic models (FDMs) that have different needs. In addition many properties will by necessity be aircraft specific, though developers should make a conscious effort to have properties map to more common ones if that is possible.

=== Where are the properties defined? ===
There are a couple ways that the properties are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties. One is in the aircraft files, starting from the aircraft specific [[aircraft-set.xml]] file, another is the [[Nasal]] files, and the last place (and often most useful!) is "grepping" (searching) through the C++ code.

To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better

== Annunciators [draft] ==
!! This section is work in progress !!

The /instrumentation/annunciators section shall provide a central place for

* aircrafts to write annunciator status data
* 3D aircraft models and external devices (like joysticks, yokes, throttle quadrants or custom made cockpit hardware) to read such data and drive status lights etc.

Some of the props are automatically calculated by property rules in $FGDATA/Aircraft/Generic/generic-annunciators.xml other properties have to be calculated by the actual aircraft.

The aircraft.nas module provides aircraft.light which allows easy implementation of blinking lights. Such lights have a bool property 'state' which tells if the light is on or off.<pre>
/instrumentation/annunciators/doors
/instrumentation/annunciators/master-caution/state # aircraft.light
/instrumentation/annunciators/master-warning/state # aircraft.light

/instrumentation/annunciators/ap/enabled
/instrumentation/annunciators/ap/mode/alt
/instrumentation/annunciators/ap/mode/apr
/instrumentation/annunciators/ap/mode/hdg
/instrumentation/annunciators/ap/mode/ias
/instrumentation/annunciators/ap/mode/nav
/instrumentation/annunciators/ap/mode/rev
/instrumentation/annunciators/ap/mode/vs

/instrumentation/annunciators/engines/
/instrumentation/annunciators/engines/apu
/instrumentation/annunciators/engines/fire
/instrumentation/annunciators/engines/oil-pressure-low
/instrumentation/annunciators/engines/starter
# for <gear-name> in {nose, left, right}
/instrumentation/annunciators/gear/<gear-name>/down
/instrumentation/annunciators/gear/<gear-name>/in-transition
/instrumentation/annunciators/gear/<gear-name>/unsafe
/instrumentation/annunciators/gear/<gear-name>/up

/instrumentation/annunciators/gear/parking-brake

/instrumentation/annunciators/systems/anti-ice/enabled
/instrumentation/annunciators/systems/fuel/aux-pump
/instrumentation/annunciators/systems/fuel/pressure-low
/instrumentation/annunciators/systems/hyd/pressure-low
/instrumentation/annunciators/systems/vacuum

</pre>

== Consumables ==
:''See also [[#Fuel]]
<pre>
/consumables/fuel/tank[%d]/level-lb
/consumables/fuel/tank[%d]/level-lbs
/consumables/fuel/tank[%d]/level-gal_us
/consumables/fuel/tank[%d]/capacity-gal_us
/consumables/fuel/tank[%d]/density-ppg
/consumables/fuel/total-fuel-lbs
/consumables/fuel/total-gal_us
</pre>

== Controls ==
These properties should, and usually do correspond to how various cockpit controls are set. Consider these the pilot input.

=== Anti-ice ===
These properties control the various anti-ice properties that may be present in an aircraft.

<pre>
/controls/anti-ice/wing-heat
/controls/anti-ice/pitot-heat
/controls/anti-ice/wiper
/controls/anti-ice/window-heat
/controls/anti-ice/engine[%d]/carb-heat
/controls/anti-ice/engine[%d]/inlet-heat
</pre>
TODO - section notes

=== APU ===
These properties control any auxiliary power unit, in essence a small turbine engine driving generators, hydraulic pumps etc. before and after the aircraft's engines are up an running.

<pre>
/controls/APU/off-start-run
/controls/APU/fire-switch
</pre>
TODO - section notes

=== Armament ===
TODO - explain of section
<pre>
/controls/armament/master-arm
/controls/armament/station-select
/controls/armament/release-all
/controls/armament/station[%d]/stick-size
/controls/armament/station[%d]/release-stick
/controls/armament/station[%d]/release-all
/controls/armament/station[%d]/jettison-all
</pre>
TODO - section notes

=== Autoflight ===
These properties control the autopilot on certain airplanes. For [[IT-AUTOFLIGHT]] based systems, see [[IT-AUTOFLIGHT#Interface_Reference|here]].

TODO - explain of section
<pre>
/controls/autoflight/autopilot[%d]/engage
/controls/autoflight/autothrottle-arm
/controls/autoflight/autothrottle-engage
/controls/autoflight/heading-select
/controls/autoflight/altitude-select
/controls/autoflight/bank-angle-select
/controls/autoflight/vertical-speed-select
/controls/autoflight/speed-select
/controls/autoflight/mach-select
/controls/autoflight/vertical-mode
/controls/autoflight/lateral-mode
</pre>
TODO - section notes

=== Electric ===
TODO - explain of section
<pre>
/controls/electric/battery-switch
/controls/electric/external-power
/controls/electric/APU-generator
/controls/electric/engine[%d]/generator
/controls/electric/engine[%d]/bus-tie
</pre>
TODO - section notes

=== Engines ===
Engines are numbered engine[0] for a single engine to engine[0] to engine[3] for a 747 for example. (The model allows for up to 12 engines rumour has it ;-)

<pre>
/controls/engines/throttle_idle
/controls/engines/engine[%d]/throttle
/controls/engines/engine[%d]/starter
/controls/engines/engine[%d]/fuel-pump
/controls/engines/engine[%d]/fire-switch
/controls/engines/engine[%d]/fire-bottle-discharge
/controls/engines/engine[%d]/cutoff
/controls/engines/engine[%d]/mixture
/controls/engines/engine[%d]/propeller-pitch
/controls/engines/engine[%d]/magnetos
/controls/engines/engine[%d]/boost
/controls/engines/engine[%d]/WEP
/controls/engines/engine[%d]/cowl-flaps-norm
/controls/engines/engine[%d]/feather
/controls/engines/engine[%d]/ignition
/controls/engines/engine[%d]/augmentation
/controls/engines/engine[%d]/afterburner
/controls/engines/engine[%d]/reverser
/controls/engines/engine[%d]/water-injection
/controls/engines/engine[%d]/condition
</pre>
TODO - section notes

=== Flight controls ===
These properties control the flight controls surfaces, though often through a mechanical, analog or digital flight control system (FCS) that may or may not be modeled.

<pre>
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/flight/flaps
/controls/flight/slats
/controls/flight/BLC // Boundary Layer Control
/controls/flight/spoilers
/controls/flight/speedbrake
/controls/flight/wing-sweep
/controls/flight/wing-fold
/controls/flight/drag-chute
</pre>

The positions of the controls are usually put in <code>/surface-positions/</code> at the discretion of the aircraft designer. These usually drive the animations of the control surfaces. They are either normalized (like <code>/surface-positions/elevator-pos-norm</code>) or in degrees, and sometimes the aileron is split left/right.

=== Fuel ===
TODO - explain of section
<pre>
/controls/fuel/dump-valve
/controls/fuel/tank[%d]/fuel_selector
/controls/fuel/tank[%d]/to_engine
/controls/fuel/tank[%d]/to_tank
/controls/fuel/tank[%d]/boost-pump[%d]
</pre>
TODO - section notes

=== Gear ===
TODO - explain of section
<pre>
/controls/gear/brake-left
/controls/gear/brake-right
/controls/gear/brake-parking
/controls/gear/steering // Used if rudder is not sufficient for control of steering
/controls/gear/gear-down
/controls/gear/antiskid // Deprecated?
/controls/gear/tailhook
/controls/gear/tailwheel-lock
/controls/gear/wheel[%d]/alternate-extension
</pre>
TODO - section notes

=== Hydraulics ===
TODO - explain of section
<pre>
/controls/hydraulic/system[%d]/engine-pump
/controls/hydraulic/system[%d]/electric-pump
</pre>
TODO - section notes

=== Lights ===
TODO - explain of section
<pre>
/controls/lighting/landing-lights
/controls/lighting/turn-off-lights
/controls/lighting/formation-lights
/controls/lighting/taxi-light
/controls/lighting/logo-lights
/controls/lighting/nav-lights
/controls/lighting/beacon
/controls/lighting/strobe
/controls/lighting/panel-norm
/controls/lighting/instruments-norm
/controls/lighting/dome-norm
</pre>
TODO - section notes

=== Pneumatic ===
TODO - explain of section
<pre>
/controls/pneumatic/APU-bleed
/controls/pneumatic/engine[%d]/bleed
</pre>
TODO - section notes

=== Pressurization ===
TODO - explain of section
<pre>
/controls/pressurization/mode
/controls/pressurization/dump
/controls/pressurization/outflow-valve
/controls/pressurization/pack[%d]/pack-on
</pre>
TODO - section notes

=== Seat ===
TODO - explain of section
<pre>
/controls/seat/vertical-adjust
/controls/seat/fore-aft-adjust
/controls/seat/cmd_selector_valve
/controls/seat/eject[%d]/initiate
/controls/seat/eject[%d]/status
</pre>
TODO - section notes

== Engines ==
Status of engines. See also: /controls/engines/
=== Common ===
<pre>
/engines/engine[%d]/fuel-flow-gph
/engines/engine[%d]/fuel-flow_pph
/engines/engine[%d]/thrust_lb
/engines/engine[%d]/running
/engines/engine[%d]/starter
/engines/engine[%d]/cranking
/engines/engine[%d]/fire
</pre>

=== Turbine ===
<pre>
/engines/engine[%d]/n1
/engines/engine[%d]/n2
/engines/engine[%d]/epr
/engines/engine[%d]/augmentation
/engines/engine[%d]/water-injection
/engines/engine[%d]/ignition
/engines/engine[%d]/nozzle-pos-norm
/engines/engine[%d]/inlet-pos-norm
/engines/engine[%d]/reversed
/engines/engine[%d]/cutoff
</pre>

=== Piston ===
<pre>
/engines/engine[%d]/mp-osi
/engines/engine[%d]/egt-degf
/engines/engine[%d]/oil-temperature-degf
/engines/engine[%d]/oil-pressure-psi
/engines/engine[%d]/cht-degf
/engines/engine[%d]/rpm
</pre>

=== Propeller ===
<pre>
/engines/engine[%d]/rpm
/engines/engine[%d]/pitch
/engines/engine[%d]/torque
</pre>
TODO - section notes

== Flight Dynamics Model ==
=== Position ===
This will return the current position of the aircraft within FlightGear. This is also the stuff that is transmitted in [[Howto:Multiplayer|multiplayer]].

<pre>
/position/
/position/altitiude-ft ()
/position/altitude-agl-ft (22.46983965)
/position/altitude-ft (28.24368289)
/position/ground-elev-ft (-0.43513529)
/position/ground-elev-m (-0.1326292364)
/position/latitude-deg (37.61371436)
/position/latitude-string (37*36 49.4N)
/position/longitude-deg (-122.3576508)
/position/longitude-string (-122*21 27.5W)
/position/sea-level-radius-ft (20899648.76)
</pre>

=== Orientation ===
TODO - explain of section
<pre>
/orientation/roll-deg
/orientation/pitch-deg
/orientation/heading-deg

/orientation/roll-rate-degps
/orientation/pitch-rate-degps
/orientation/yaw-rate-degps

/orientation/side-slip-rad
/orientation/side-slip-deg
/orientation/alpha-deg
</pre>
TODO - section notes

=== Velocities ===
TODO - explain of section
<pre>
/velocities/airspeed-kt
/velocities/mach
/velocities/speed-north-fps
/velocities/speed-east-fps
/velocities/speed-down-fps

/velocities/uBody-fps
/velocities/vBody-fps
/velocities/wBody-fps

/velocities/vertical-speed-fps
/velocities/glideslope
</pre>
TODO - section notes

=== Acceleration ===
TODO - explain of section
<pre>
/accelerations/nlf

/accelerations/ned/north-accel-fps_sec
/accelerations/ned/east-accel-fps_sec
/accelerations/ned/down-accel-fps_sec

/accelerations/pilot/x-accel-fps_sec
/accelerations/pilot/y-accel-fps_sec
/accelerations/pilot/z-accel-fps_sec
</pre>
TODO - section notes

== Gear ==
<pre>
/gear/serviceable
/gear/gear[%d]/cast-angle-deg // The angle of the wheel where 0 is pointing straight forward
/gear/gear[%d]/compression-m
/gear/gear[%d]/compression-norm
/gear/gear[%d]/ground-friction-factor
/gear/gear[%d]/ground-is-solid
/gear/gear[%d]/has-brake
/gear/gear[%d]/rollspeed-ms // Speed of the wheel's rotation in meters per second
/gear/gear[%d]/wow // Weight-on-wheel
/gear/gear[%d]/xoffset-in
/gear/gear[%d]/yoffset-in
/gear/gear[%d]/zoffset-in
</pre>

== Instrumentation ==
<pre>
/instrumentation/adf[%d]/
/instrumentation/airspeed-indicator/
/instrumentation/altimeter/
/instrumentation/annunciator/
/instrumentation/attitude-indicator/
/instrumentation/clock/
/instrumentation/comm[%d]/
/instrumentation/dme/
/instrumentation/efis/
/instrumentation/encoder/
/instrumentation/flightdirector/
/instrumentation/gps/
/instrumentation/gps-annunciator/
/instrumentation/heading-indicator/
/instrumentation/heading-indicator-fg/
/instrumentation/magnetic-compass/
/instrumentation/marker-beacon/
/instrumentation/nav[%d]/
/instrumentation/radar/
/instrumentation/slip-skid-ball/
/instrumentation/tacan[%d]/
/instrumentation/transponder/
/instrumentation/turn-indicator/
/instrumentation/vertical-speed-indicator/
/instrumentation/wxradar/
</pre>

=== Instrumentation ADF ===
<pre>
/instrumentation/adf[%d]/adf-btn
/instrumentation/adf[%d]/bro-btn
/instrumentation/adf[%d]/display-mode
/instrumentation/adf[%d]/enroute-timer/running
/instrumentation/adf[%d]/enroute-timer/start-time
/instrumentation/adf[%d]/enroute-timer/time
/instrumentation/adf[%d]/error-deg
/instrumentation/adf[%d]/flight-timer/running
/instrumentation/adf[%d]/flight-timer/start-time
/instrumentation/adf[%d]/flight-timer/time
/instrumentation/adf[%d]/flt-btn
/instrumentation/adf[%d]/frequencies/dial-1-khz
/instrumentation/adf[%d]/frequencies/dial-100-khz
/instrumentation/adf[%d]/frequencies/selected-khz
/instrumentation/adf[%d]/frequencies/standby-khz
/instrumentation/adf[%d]/frq-btn
/instrumentation/adf[%d]/ident
/instrumentation/adf[[%d]/ident-audible
/instrumentation/adf[%d]/in-range
/instrumentation/adf[%d]/indicated-bearing-deg
/instrumentation/adf[%d]/mode
/instrumentation/adf[%d]/model
/instrumentation/adf[%d]/operable
/instrumentation/adf[%d]/power-btn
/instrumentation/adf[%d]/right-display
/instrumentation/adf[%d]/rotation-deg
/instrumentation/adf[%d]/serviceable
/instrumentation/adf[%d]/set-btn
/instrumentation/adf[%d]/volume
/instrumentation/adf[%d]/volume-norm
</pre>

=== Instrumentation comm radio ===
See [[Aircraft_properties_reference/Instrumentation/COMM]]

=== Instrumentation NAV radio ===

<pre>
/instrumentation/nav[%d]/audio-btn
/instrumentation/nav[%d]/back-course-btn
/instrumentation/nav[%d]/cdi/serviceable
/instrumentation/nav[%d]/crosstrack-error-m
/instrumentation/nav[%d]/crosstrack-heading-error-deg
/instrumentation/nav[%d]/data-is-valid
/instrumentation/nav[%d]/dme-in-range
/instrumentation/nav[%d]/filtered-cdiNAV0-deflection
/instrumentation/nav[%d]/filtered-gsNAV0-deflection
/instrumentation/nav[%d]/frequencies/dial-khz
/instrumentation/nav[%d]/frequencies/dial-mhz
/instrumentation/nav[%d]/frequencies/is-localizer-frequency
/instrumentation/nav[%d]/frequencies/selected-mhz
/instrumentation/nav[%d]/frequencies/selected-mhz-fmt
/instrumentation/nav[%d]/frequencies/standby-mhz
/instrumentation/nav[%d]/frequencies/standby-mhz-fmt
/instrumentation/nav[%d]/from-flag
/instrumentation/nav[%d]/frq-swap-btn
/instrumentation/nav[%d]/gs/serviceable
/instrumentation/nav[%d]/gs-direct-deg
/instrumentation/nav[%d]/gs-distance
/instrumentation/nav[%d]/gs-in-range
/instrumentation/nav[%d]/gs-needle-deflection
/instrumentation/nav[%d]/gs-needle-deflection-deg
/instrumentation/nav[%d]/gs-needle-deflection-norm
/instrumentation/nav[%d]/gs-rate-of-climb
/instrumentation/nav[%d]/gs-rate-of-climb-fpm
/instrumentation/nav[%d]/has-gs
/instrumentation/nav[%d]/heading-deg
/instrumentation/nav[%d]/heading-needle-deflection
/instrumentation/nav[%d]/heading-needle-deflection-norm
/instrumentation/nav[%d]/ident
/instrumentation/nav[%d]/ident-audible
/instrumentation/nav[%d]/in-range
/instrumentation/nav[%d]/nav-distance
/instrumentation/nav[%d]/nav-id
/instrumentation/nav[%d]/nav-id_asc1
/instrumentation/nav[%d]/nav-id_asc2
/instrumentation/nav[%d]/nav-id_asc3
/instrumentation/nav[%d]/nav-id_asc4
/instrumentation/nav[%d]/nav-loc
/instrumentation/nav[%d]/operable
/instrumentation/nav[%d]/power-btn
/instrumentation/nav[%d]/radials/actual-deg
/instrumentation/nav[%d]/radials/reciprocal-radial-deg
/instrumentation/nav[%d]/radials/selected-deg
/instrumentation/nav[%d]/radials/target-auto-hdg-deg
/instrumentation/nav[%d]/radials/arget-radial-deg
/instrumentation/nav[%d]/serviceable
/instrumentation/nav[%d]/signal-quality-norm
/instrumentation/nav[%d]/slaved-to-gps
/instrumentation/nav[%d]/time-to-intercept-sec
/instrumentation/nav[%d]/to-flag
/instrumentation/nav[%d]/to-from/serviceable
/instrumentation/nav[%d]/volume
</pre>

=== Instrumentation Tacan ===

<pre>
/instrumentation/tacan[%d]/display/channel
/instrumentation/tacan[%d]/display/x-shift
/instrumentation/tacan[%d]/display/y-shift
/instrumentation/tacan[%d]/frequencies/selected-channel
/instrumentation/tacan[%d]/frequencies/selected-channel[1]
/instrumentation/tacan[%d]/frequencies/selected-channel[2]
/instrumentation/tacan[%d]/frequencies/selected-channel[3]
/instrumentation/tacan[%d]/frequencies/selected-channel[4]
/instrumentation/tacan[%d]/frequencies/selected-mhz
/instrumentation/tacan[%d]/ident
/instrumentation/tacan[%d]/in-range
/instrumentation/tacan[%d]/indicated-bearing-true-deg
/instrumentation/tacan[%d]/indicated-distance-nm
/instrumentation/tacan[%d]/indicated-ground-speed-kt
/instrumentation/tacan[%d]/indicated-time-min
/instrumentation/tacan[%d]/name
/instrumentation/tacan[%d]/serviceable
/instrumentation/tacan[%d]/switch-position
</pre>

== Rotors (YASim only) ==
<pre>
/rotors/gear/torque-sound-filtered // Unused?
/rotors/gear/total-torque
/rotors/{name}/balance
/rotors/{name}/blade[%d]/flap-deg
/rotors/{name}/blade[%d]/incidence-deg
/rotors/{name}/blade[%d]/position-deg // Position relative to model
/rotors/{name}/bladesvisible // Used for animations
/rotors/{name}/cone%d-deg //e.g. cone-deg or cone2-deg
/rotors/{name}/roll-deg
/rotors/{name}/rpm
/rotors/{name}/stall
/rotors/{name}/stall-filtered
/rotors/{name}/tilt
/rotors/{name}/torque
/rotors/{name}/yaw-deg
</pre>

For how to animate rotors using these properties, see [[Howto:Animate helicopters]].

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Multiplayer protocol]]
* [[Property browser]]
* [[PropertyList XML files]]
* [[Property tree]]

=== Readme files ===
* {{readme file|properties}}

=== Source code ===
==== Consumables ====
* {{flightgear file|src/FDM/TankProperties.hxx}}
* {{flightgear file|src/FDM/TankProperties.cxx}}

==== Controls ====
* {{flightgear file|src/Aircraft/controls.hxx}}
* {{flightgear file|src/Aircraft/controls.cxx}}

==== Flight Dynamics Model ====
* {{flightgear file|src/FDM/flightProperties.hxx}}
* {{flightgear file|src/FDM/flightProperties.cxx}}

==== Instrumentation ====
* {{flightgear file|src/Instrumentation}}

[[Category:Property Tree]]
[[Category:Aircraft enhancement]]

Aircraft properties reference/Instrumentation/COMM

2024-04-18T00:25:21Z

Www2: Move to a separate page for properties reference for the COMM radio

<pre>
/instrumentation/comm[%d]/add-noise
/instrumentation/comm[%d]/airport-id
/instrumentation/comm[%d]/atis
/instrumentation/comm[%d]/channel-button
/instrumentation/comm[%d]/chanel-mode-selector
/instrumentation/comm[%d]/cutoff-signal-quality
/instrumentation/comm[%d]/frequencies
/instrumentation/comm[%d]/frequencies/dial-khz
/instrumentation/comm[%d]/frequencies/dial-mhz
/instrumentation/comm[%d]/frequencies/selected-channel
/instrumentation/comm[%d]/frequencies/selected-channel-width-khz
/instrumentation/comm[%d]/frequencies/selected-mhz
/instrumentation/comm[%d]/frequencies/selected-mhz-fmt
/instrumentation/comm[%d]/frequencies/selected-real-frequency-mhz
/instrumentation/comm[%d]/frequencies/standby-channel
/instrumentation/comm[%d]/frequencies/standby-channel-width-khz
/instrumentation/comm[%d]/frequencies/standby-mhz
/instrumentation/comm[%d]/frequencies/standby-mhz-fmt
/instrumentation/comm[%d]/frequencies/standby-real-frequency-mhz
/instrumentation/comm[%d]/frq-swap-btn
/instrumentation/comm[%d]/height-above-station-ft
/instrumentation/comm[%d]/operable
/instrumentation/comm[%d]/power-btn
/instrumentation/comm[%d]/ptt
/instrumentation/comm[%d]/servicable
/instrumentation/comm[%d]/signal-quality-norm
/instrumentation/comm[%d]/slant-distance-m
/instrumentation/comm[%d]/station-name
/instrumentation/comm[%d]/station-type
/instrumentation/comm[%d]/test-btn
/instrumentation/comm[%d]/track-distance-m
/instrumentation/comm[%d]/true-bearing-from-deg
/instrumentation/comm[%d]/true-bearing-to-deg
/instrumentation/comm[%d]/volume
/instrumentation/comm[%d]/volume-selected
</pre>

Aircraft properties reference

2024-04-15T22:40:13Z

Www2: /* Instrumentation */ Add Instrumentation NAV

{{PropertyTree}}

This is a generic '''aircraft properties reference'''. There are many properties that are very common in aircraft, and many of them are present even in a very simple aircraft. However, a complete description that matches all the properties is very unlikely to be written, as aircraft can be very different from each other.

{{TOC limit|2}}

== What are properties? ==
{{main article|Property tree}}
=== The property tree ===
Most parts of FlightGear communicate with each other through key-value pair properties in the [[property tree]]. The properties represent both the input from the pilot, the values determining the position and velocity of the aircraft, the values used for animating the aircraft, and pretty much anything else.

While many properties will be common between most aircraft, many properties will also be different between aircraft. This becomes obvious if one consider the many different configurations (aircraft/helicopter/car, control surface and landing gear layout, number and locations of engines, etc) and propulsions systems (types of engines, types of fuels etc.) an aircraft can have. There are also different flight dynamic models (FDMs) that have different needs. In addition many properties will by necessity be aircraft specific, though developers should make a conscious effort to have properties map to more common ones if that is possible.

=== Where are the properties defined? ===
There are a couple ways that the properties are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties. One is in the aircraft files, starting from the aircraft specific [[aircraft-set.xml]] file, another is the [[Nasal]] files, and the last place (and often most useful!) is "grepping" (searching) through the C++ code.

To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better

== Annunciators [draft] ==
!! This section is work in progress !!

The /instrumentation/annunciators section shall provide a central place for

* aircrafts to write annunciator status data
* 3D aircraft models and external devices (like joysticks, yokes, throttle quadrants or custom made cockpit hardware) to read such data and drive status lights etc.

Some of the props are automatically calculated by property rules in $FGDATA/Aircraft/Generic/generic-annunciators.xml other properties have to be calculated by the actual aircraft.

The aircraft.nas module provides aircraft.light which allows easy implementation of blinking lights. Such lights have a bool property 'state' which tells if the light is on or off.<pre>
/instrumentation/annunciators/doors
/instrumentation/annunciators/master-caution/state # aircraft.light
/instrumentation/annunciators/master-warning/state # aircraft.light

/instrumentation/annunciators/ap/enabled
/instrumentation/annunciators/ap/mode/alt
/instrumentation/annunciators/ap/mode/apr
/instrumentation/annunciators/ap/mode/hdg
/instrumentation/annunciators/ap/mode/ias
/instrumentation/annunciators/ap/mode/nav
/instrumentation/annunciators/ap/mode/rev
/instrumentation/annunciators/ap/mode/vs

/instrumentation/annunciators/engines/
/instrumentation/annunciators/engines/apu
/instrumentation/annunciators/engines/fire
/instrumentation/annunciators/engines/oil-pressure-low
/instrumentation/annunciators/engines/starter
# for <gear-name> in {nose, left, right}
/instrumentation/annunciators/gear/<gear-name>/down
/instrumentation/annunciators/gear/<gear-name>/in-transition
/instrumentation/annunciators/gear/<gear-name>/unsafe
/instrumentation/annunciators/gear/<gear-name>/up

/instrumentation/annunciators/gear/parking-brake

/instrumentation/annunciators/systems/anti-ice/enabled
/instrumentation/annunciators/systems/fuel/aux-pump
/instrumentation/annunciators/systems/fuel/pressure-low
/instrumentation/annunciators/systems/hyd/pressure-low
/instrumentation/annunciators/systems/vacuum

</pre>

== Consumables ==
:''See also [[#Fuel]]
<pre>
/consumables/fuel/tank[%d]/level-lb
/consumables/fuel/tank[%d]/level-lbs
/consumables/fuel/tank[%d]/level-gal_us
/consumables/fuel/tank[%d]/capacity-gal_us
/consumables/fuel/tank[%d]/density-ppg
/consumables/fuel/total-fuel-lbs
/consumables/fuel/total-gal_us
</pre>

== Controls ==
These properties should, and usually do correspond to how various cockpit controls are set. Consider these the pilot input.

=== Anti-ice ===
These properties control the various anti-ice properties that may be present in an aircraft.

<pre>
/controls/anti-ice/wing-heat
/controls/anti-ice/pitot-heat
/controls/anti-ice/wiper
/controls/anti-ice/window-heat
/controls/anti-ice/engine[%d]/carb-heat
/controls/anti-ice/engine[%d]/inlet-heat
</pre>
TODO - section notes

=== APU ===
These properties control any auxiliary power unit, in essence a small turbine engine driving generators, hydraulic pumps etc. before and after the aircraft's engines are up an running.

<pre>
/controls/APU/off-start-run
/controls/APU/fire-switch
</pre>
TODO - section notes

=== Armament ===
TODO - explain of section
<pre>
/controls/armament/master-arm
/controls/armament/station-select
/controls/armament/release-all
/controls/armament/station[%d]/stick-size
/controls/armament/station[%d]/release-stick
/controls/armament/station[%d]/release-all
/controls/armament/station[%d]/jettison-all
</pre>
TODO - section notes

=== Autoflight ===
These properties control the autopilot.

TODO - explain of section
<pre>
/controls/autoflight/autopilot[%d]/engage
/controls/autoflight/autothrottle-arm
/controls/autoflight/autothrottle-engage
/controls/autoflight/heading-select
/controls/autoflight/altitude-select
/controls/autoflight/bank-angle-select
/controls/autoflight/vertical-speed-select
/controls/autoflight/speed-select
/controls/autoflight/mach-select
/controls/autoflight/vertical-mode
/controls/autoflight/lateral-mode
</pre>
TODO - section notes

=== Electric ===
TODO - explain of section
<pre>
/controls/electric/battery-switch
/controls/electric/external-power
/controls/electric/APU-generator
/controls/electric/engine[%d]/generator
/controls/electric/engine[%d]/bus-tie
</pre>
TODO - section notes

=== Engines ===
Engines are numbered engine[0] for a single engine to engine[0] to engine[3] for a 747 for example. (The model allows for up to 12 engines rumour has it ;-)

<pre>
/controls/engines/throttle_idle
/controls/engines/engine[%d]/throttle
/controls/engines/engine[%d]/starter
/controls/engines/engine[%d]/fuel-pump
/controls/engines/engine[%d]/fire-switch
/controls/engines/engine[%d]/fire-bottle-discharge
/controls/engines/engine[%d]/cutoff
/controls/engines/engine[%d]/mixture
/controls/engines/engine[%d]/propeller-pitch
/controls/engines/engine[%d]/magnetos
/controls/engines/engine[%d]/boost
/controls/engines/engine[%d]/WEP
/controls/engines/engine[%d]/cowl-flaps-norm
/controls/engines/engine[%d]/feather
/controls/engines/engine[%d]/ignition
/controls/engines/engine[%d]/augmentation
/controls/engines/engine[%d]/afterburner
/controls/engines/engine[%d]/reverser
/controls/engines/engine[%d]/water-injection
/controls/engines/engine[%d]/condition
</pre>
TODO - section notes

=== Flight controls ===
These properties control the flight controls surfaces, though often through a mechanical, analog or digital flight control system (FCS) that may or may not be modeled.

<pre>
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/flight/flaps
/controls/flight/slats
/controls/flight/BLC // Boundary Layer Control
/controls/flight/spoilers
/controls/flight/speedbrake
/controls/flight/wing-sweep
/controls/flight/wing-fold
/controls/flight/drag-chute
</pre>

The positions of the controls are usually put in <code>/surface-positions/</code> at the discretion of the aircraft designer. These usually drive the animations of the control surfaces. They are either normalized (like <code>/surface-positions/elevator-pos-norm</code>) or in degrees, and sometimes the aileron is split left/right.

=== Fuel ===
TODO - explain of section
<pre>
/controls/fuel/dump-valve
/controls/fuel/tank[%d]/fuel_selector
/controls/fuel/tank[%d]/to_engine
/controls/fuel/tank[%d]/to_tank
/controls/fuel/tank[%d]/boost-pump[%d]
</pre>
TODO - section notes

=== Gear ===
TODO - explain of section
<pre>
/controls/gear/brake-left
/controls/gear/brake-right
/controls/gear/brake-parking
/controls/gear/steering // Used if rudder is not sufficient for control of steering
/controls/gear/gear-down
/controls/gear/antiskid // Deprecated?
/controls/gear/tailhook
/controls/gear/tailwheel-lock
/controls/gear/wheel[%d]/alternate-extension
</pre>
TODO - section notes

=== Hydraulics ===
TODO - explain of section
<pre>
/controls/hydraulic/system[%d]/engine-pump
/controls/hydraulic/system[%d]/electric-pump
</pre>
TODO - section notes

=== Lights ===
TODO - explain of section
<pre>
/controls/lighting/landing-lights
/controls/lighting/turn-off-lights
/controls/lighting/formation-lights
/controls/lighting/taxi-light
/controls/lighting/logo-lights
/controls/lighting/nav-lights
/controls/lighting/beacon
/controls/lighting/strobe
/controls/lighting/panel-norm
/controls/lighting/instruments-norm
/controls/lighting/dome-norm
</pre>
TODO - section notes

=== Pneumatic ===
TODO - explain of section
<pre>
/controls/pneumatic/APU-bleed
/controls/pneumatic/engine[%d]/bleed
</pre>
TODO - section notes

=== Pressurization ===
TODO - explain of section
<pre>
/controls/pressurization/mode
/controls/pressurization/dump
/controls/pressurization/outflow-valve
/controls/pressurization/pack[%d]/pack-on
</pre>
TODO - section notes

=== Seat ===
TODO - explain of section
<pre>
/controls/seat/vertical-adjust
/controls/seat/fore-aft-adjust
/controls/seat/cmd_selector_valve
/controls/seat/eject[%d]/initiate
/controls/seat/eject[%d]/status
</pre>
TODO - section notes

== Engines ==
Status of engines. See also: /controls/engines/
=== Common ===
<pre>
/engines/engine[%d]/fuel-flow-gph
/engines/engine[%d]/fuel-flow_pph
/engines/engine[%d]/thrust_lb
/engines/engine[%d]/running
/engines/engine[%d]/starter
/engines/engine[%d]/cranking
/engines/engine[%d]/fire
</pre>

=== Turbine ===
<pre>
/engines/engine[%d]/n1
/engines/engine[%d]/n2
/engines/engine[%d]/epr
/engines/engine[%d]/augmentation
/engines/engine[%d]/water-injection
/engines/engine[%d]/ignition
/engines/engine[%d]/nozzle-pos-norm
/engines/engine[%d]/inlet-pos-norm
/engines/engine[%d]/reversed
/engines/engine[%d]/cutoff
</pre>

=== Piston ===
<pre>
/engines/engine[%d]/mp-osi
/engines/engine[%d]/egt-degf
/engines/engine[%d]/oil-temperature-degf
/engines/engine[%d]/oil-pressure-psi
/engines/engine[%d]/cht-degf
/engines/engine[%d]/rpm
</pre>

=== Propeller ===
<pre>
/engines/engine[%d]/rpm
/engines/engine[%d]/pitch
/engines/engine[%d]/torque
</pre>
TODO - section notes

== Flight Dynamics Model ==
=== Position ===
This will return the current position of the aircraft within FlightGear. This is also the stuff that is transmitted in [[Howto:Multiplayer|multiplayer]].

<pre>
/position/
/position/altitiude-ft ()
/position/altitude-agl-ft (22.46983965)
/position/altitude-ft (28.24368289)
/position/ground-elev-ft (-0.43513529)
/position/ground-elev-m (-0.1326292364)
/position/latitude-deg (37.61371436)
/position/latitude-string (37*36 49.4N)
/position/longitude-deg (-122.3576508)
/position/longitude-string (-122*21 27.5W)
/position/sea-level-radius-ft (20899648.76)
</pre>

=== Orientation ===
TODO - explain of section
<pre>
/orientation/roll-deg
/orientation/pitch-deg
/orientation/heading-deg

/orientation/roll-rate-degps
/orientation/pitch-rate-degps
/orientation/yaw-rate-degps

/orientation/side-slip-rad
/orientation/side-slip-deg
/orientation/alpha-deg
</pre>
TODO - section notes

=== Velocities ===
TODO - explain of section
<pre>
/velocities/airspeed-kt
/velocities/mach
/velocities/speed-north-fps
/velocities/speed-east-fps
/velocities/speed-down-fps

/velocities/uBody-fps
/velocities/vBody-fps
/velocities/wBody-fps

/velocities/vertical-speed-fps
/velocities/glideslope
</pre>
TODO - section notes

=== Acceleration ===
TODO - explain of section
<pre>
/accelerations/nlf

/accelerations/ned/north-accel-fps_sec
/accelerations/ned/east-accel-fps_sec
/accelerations/ned/down-accel-fps_sec

/accelerations/pilot/x-accel-fps_sec
/accelerations/pilot/y-accel-fps_sec
/accelerations/pilot/z-accel-fps_sec
</pre>
TODO - section notes

== Gear ==
<pre>
/gear/serviceable
/gear/gear[%d]/cast-angle-deg // The angle of the wheel where 0 is pointing straight forward
/gear/gear[%d]/compression-m
/gear/gear[%d]/compression-norm
/gear/gear[%d]/ground-friction-factor
/gear/gear[%d]/ground-is-solid
/gear/gear[%d]/has-brake
/gear/gear[%d]/rollspeed-ms // Speed of the wheel's rotation in meters per second
/gear/gear[%d]/wow // Weight-on-wheel
/gear/gear[%d]/xoffset-in
/gear/gear[%d]/yoffset-in
/gear/gear[%d]/zoffset-in
</pre>

== Instrumentation ==
<pre>
/instrumentation/adf[%d]/
/instrumentation/airspeed-indicator/
/instrumentation/altimeter/
/instrumentation/annunciator/
/instrumentation/attitude-indicator/
/instrumentation/clock/
/instrumentation/comm[%d]/
/instrumentation/dme/
/instrumentation/efis/
/instrumentation/encoder/
/instrumentation/flightdirector/
/instrumentation/gps/
/instrumentation/gps-annunciator/
/instrumentation/heading-indicator/
/instrumentation/heading-indicator-fg/
/instrumentation/magnetic-compass/
/instrumentation/marker-beacon/
/instrumentation/nav[%d]/
/instrumentation/radar/
/instrumentation/slip-skid-ball/
/instrumentation/tacan[%d]/
/instrumentation/transponder/
/instrumentation/turn-indicator/
/instrumentation/vertical-speed-indicator/
/instrumentation/wxradar/
</pre>

=== Instrumentation ADF ===
<pre>
/instrumentation/adf[%d]/adf-btn
/instrumentation/adf[%d]/bro-btn
/instrumentation/adf[%d]/display-mode
/instrumentation/adf[%d]/enroute-timer/running
/instrumentation/adf[%d]/enroute-timer/start-time
/instrumentation/adf[%d]/enroute-timer/time
/instrumentation/adf[%d]/error-deg
/instrumentation/adf[%d]/flight-timer/running
/instrumentation/adf[%d]/flight-timer/start-time
/instrumentation/adf[%d]/flight-timer/time
/instrumentation/adf[%d]/flt-btn
/instrumentation/adf[%d]/frequencies/dial-1-khz
/instrumentation/adf[%d]/frequencies/dial-100-khz
/instrumentation/adf[%d]/frequencies/selected-khz
/instrumentation/adf[%d]/frequencies/standby-khz
/instrumentation/adf[%d]/frq-btn
/instrumentation/adf[%d]/ident
/instrumentation/adf[[%d]/ident-audible
/instrumentation/adf[%d]/in-range
/instrumentation/adf[%d]/indicated-bearing-deg
/instrumentation/adf[%d]/mode
/instrumentation/adf[%d]/model
/instrumentation/adf[%d]/operable
/instrumentation/adf[%d]/power-btn
/instrumentation/adf[%d]/right-display
/instrumentation/adf[%d]/rotation-deg
/instrumentation/adf[%d]/serviceable
/instrumentation/adf[%d]/set-btn
/instrumentation/adf[%d]/volume
/instrumentation/adf[%d]/volume-norm
</pre>

=== Instrumentation comm radio ===

<pre>
/instrumentation/comm[%d]/add-noise
/instrumentation/comm[%d]/airport-id
/instrumentation/comm[%d]/atis
/instrumentation/comm[%d]/channel-button
/instrumentation/comm[%d]/chanel-mode-selector
/instrumentation/comm[%d]/cutoff-signal-quality
/instrumentation/comm[%d]/frequencies
/instrumentation/comm[%d]/frequencies/dial-khz
/instrumentation/comm[%d]/frequencies/dial-mhz
/instrumentation/comm[%d]/frequencies/selected-channel
/instrumentation/comm[%d]/frequencies/selected-channel-width-khz
/instrumentation/comm[%d]/frequencies/selected-mhz
/instrumentation/comm[%d]/frequencies/selected-mhz-fmt
/instrumentation/comm[%d]/frequencies/selected-real-frequency-mhz
/instrumentation/comm[%d]/frequencies/standby-channel
/instrumentation/comm[%d]/frequencies/standby-channel-width-khz
/instrumentation/comm[%d]/frequencies/standby-mhz
/instrumentation/comm[%d]/frequencies/standby-mhz-fmt
/instrumentation/comm[%d]/frequencies/standby-real-frequency-mhz
/instrumentation/comm[%d]/frq-swap-btn
/instrumentation/comm[%d]/height-above-station-ft
/instrumentation/comm[%d]/operable
/instrumentation/comm[%d]/power-btn
/instrumentation/comm[%d]/ptt
/instrumentation/comm[%d]/servicable
/instrumentation/comm[%d]/signal-quality-norm
/instrumentation/comm[%d]/slant-distance-m
/instrumentation/comm[%d]/station-name
/instrumentation/comm[%d]/station-type
/instrumentation/comm[%d]/test-btn
/instrumentation/comm[%d]/track-distance-m
/instrumentation/comm[%d]/true-bearing-from-deg
/instrumentation/comm[%d]/true-bearing-to-deg
/instrumentation/comm[%d]/volume
/instrumentation/comm[%d]/volume-selected
</pre>

=== Instrumentation NAV radio ===

<pre>
/instrumentation/nav[%d]/audio-btn
/instrumentation/nav[%d]/back-course-btn
/instrumentation/nav[%d]/cdi/serviceable
/instrumentation/nav[%d]/crosstrack-error-m
/instrumentation/nav[%d]/crosstrack-heading-error-deg
/instrumentation/nav[%d]/data-is-valid
/instrumentation/nav[%d]/dme-in-range
/instrumentation/nav[%d]/filtered-cdiNAV0-deflection
/instrumentation/nav[%d]/filtered-gsNAV0-deflection
/instrumentation/nav[%d]/frequencies/dial-khz
/instrumentation/nav[%d]/frequencies/dial-mhz
/instrumentation/nav[%d]/frequencies/is-localizer-frequency
/instrumentation/nav[%d]/frequencies/selected-mhz
/instrumentation/nav[%d]/frequencies/selected-mhz-fmt
/instrumentation/nav[%d]/frequencies/standby-mhz
/instrumentation/nav[%d]/frequencies/standby-mhz-fmt
/instrumentation/nav[%d]/from-flag
/instrumentation/nav[%d]/frq-swap-btn
/instrumentation/nav[%d]/gs/serviceable
/instrumentation/nav[%d]/gs-direct-deg
/instrumentation/nav[%d]/gs-distance
/instrumentation/nav[%d]/gs-in-range
/instrumentation/nav[%d]/gs-needle-deflection
/instrumentation/nav[%d]/gs-needle-deflection-deg
/instrumentation/nav[%d]/gs-needle-deflection-norm
/instrumentation/nav[%d]/gs-rate-of-climb
/instrumentation/nav[%d]/gs-rate-of-climb-fpm
/instrumentation/nav[%d]/has-gs
/instrumentation/nav[%d]/heading-deg
/instrumentation/nav[%d]/heading-needle-deflection
/instrumentation/nav[%d]/heading-needle-deflection-norm
/instrumentation/nav[%d]/ident
/instrumentation/nav[%d]/ident-audible
/instrumentation/nav[%d]/in-range
/instrumentation/nav[%d]/nav-distance
/instrumentation/nav[%d]/nav-id
/instrumentation/nav[%d]/nav-id_asc1
/instrumentation/nav[%d]/nav-id_asc2
/instrumentation/nav[%d]/nav-id_asc3
/instrumentation/nav[%d]/nav-id_asc4
/instrumentation/nav[%d]/nav-loc
/instrumentation/nav[%d]/operable
/instrumentation/nav[%d]/power-btn
/instrumentation/nav[%d]/radials/actual-deg
/instrumentation/nav[%d]/radials/reciprocal-radial-deg
/instrumentation/nav[%d]/radials/selected-deg
/instrumentation/nav[%d]/radials/target-auto-hdg-deg
/instrumentation/nav[%d]/radials/arget-radial-deg
/instrumentation/nav[%d]/serviceable
/instrumentation/nav[%d]/signal-quality-norm
/instrumentation/nav[%d]/slaved-to-gps
/instrumentation/nav[%d]/time-to-intercept-sec
/instrumentation/nav[%d]/to-flag
/instrumentation/nav[%d]/to-from/serviceable
/instrumentation/nav[%d]/volume
</pre>

=== Instrumentation Tacan ===

<pre>
/instrumentation/tacan[%d]/display/channel
/instrumentation/tacan[%d]/display/x-shift
/instrumentation/tacan[%d]/display/y-shift
/instrumentation/tacan[%d]/frequencies/selected-channel
/instrumentation/tacan[%d]/frequencies/selected-channel[1]
/instrumentation/tacan[%d]/frequencies/selected-channel[2]
/instrumentation/tacan[%d]/frequencies/selected-channel[3]
/instrumentation/tacan[%d]/frequencies/selected-channel[4]
/instrumentation/tacan[%d]/frequencies/selected-mhz
/instrumentation/tacan[%d]/ident
/instrumentation/tacan[%d]/in-range
/instrumentation/tacan[%d]/indicated-bearing-true-deg
/instrumentation/tacan[%d]/indicated-distance-nm
/instrumentation/tacan[%d]/indicated-ground-speed-kt
/instrumentation/tacan[%d]/indicated-time-min
/instrumentation/tacan[%d]/name
/instrumentation/tacan[%d]/serviceable
/instrumentation/tacan[%d]/switch-position
</pre>

== Rotors (YASim only) ==
<pre>
/rotors/gear/torque-sound-filtered // Unused?
/rotors/gear/total-torque
/rotors/{name}/balance
/rotors/{name}/blade[%d]/flap-deg
/rotors/{name}/blade[%d]/incidence-deg
/rotors/{name}/blade[%d]/position-deg // Position relative to model
/rotors/{name}/bladesvisible // Used for animations
/rotors/{name}/cone%d-deg //e.g. cone-deg or cone2-deg
/rotors/{name}/roll-deg
/rotors/{name}/rpm
/rotors/{name}/stall
/rotors/{name}/stall-filtered
/rotors/{name}/tilt
/rotors/{name}/torque
/rotors/{name}/yaw-deg
</pre>

For how to animate rotors using these properties, see [[Howto:Animate helicopters]].

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Multiplayer protocol]]
* [[Property browser]]
* [[PropertyList XML files]]
* [[Property tree]]

=== Readme files ===
* {{readme file|properties}}

=== Source code ===
==== Consumables ====
* {{flightgear file|src/FDM/TankProperties.hxx}}
* {{flightgear file|src/FDM/TankProperties.cxx}}

==== Controls ====
* {{flightgear file|src/Aircraft/controls.hxx}}
* {{flightgear file|src/Aircraft/controls.cxx}}

==== Flight Dynamics Model ====
* {{flightgear file|src/FDM/flightProperties.hxx}}
* {{flightgear file|src/FDM/flightProperties.cxx}}

==== Instrumentation ====
* {{flightgear file|src/Instrumentation}}

[[Category:Property Tree]]
[[Category:Aircraft enhancement]]

Aircraft properties reference

2024-04-15T22:23:56Z

Www2: /* Instrumentation ADF */ fix some typo

{{PropertyTree}}

This is a generic '''aircraft properties reference'''. There are many properties that are very common in aircraft, and many of them are present even in a very simple aircraft. However, a complete description that matches all the properties is very unlikely to be written, as aircraft can be very different from each other.

{{TOC limit|2}}

== What are properties? ==
{{main article|Property tree}}
=== The property tree ===
Most parts of FlightGear communicate with each other through key-value pair properties in the [[property tree]]. The properties represent both the input from the pilot, the values determining the position and velocity of the aircraft, the values used for animating the aircraft, and pretty much anything else.

While many properties will be common between most aircraft, many properties will also be different between aircraft. This becomes obvious if one consider the many different configurations (aircraft/helicopter/car, control surface and landing gear layout, number and locations of engines, etc) and propulsions systems (types of engines, types of fuels etc.) an aircraft can have. There are also different flight dynamic models (FDMs) that have different needs. In addition many properties will by necessity be aircraft specific, though developers should make a conscious effort to have properties map to more common ones if that is possible.

=== Where are the properties defined? ===
There are a couple ways that the properties are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties. One is in the aircraft files, starting from the aircraft specific [[aircraft-set.xml]] file, another is the [[Nasal]] files, and the last place (and often most useful!) is "grepping" (searching) through the C++ code.

To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better

== Annunciators [draft] ==
!! This section is work in progress !!

The /instrumentation/annunciators section shall provide a central place for

* aircrafts to write annunciator status data
* 3D aircraft models and external devices (like joysticks, yokes, throttle quadrants or custom made cockpit hardware) to read such data and drive status lights etc.

Some of the props are automatically calculated by property rules in $FGDATA/Aircraft/Generic/generic-annunciators.xml other properties have to be calculated by the actual aircraft.

The aircraft.nas module provides aircraft.light which allows easy implementation of blinking lights. Such lights have a bool property 'state' which tells if the light is on or off.<pre>
/instrumentation/annunciators/doors
/instrumentation/annunciators/master-caution/state # aircraft.light
/instrumentation/annunciators/master-warning/state # aircraft.light

/instrumentation/annunciators/ap/enabled
/instrumentation/annunciators/ap/mode/alt
/instrumentation/annunciators/ap/mode/apr
/instrumentation/annunciators/ap/mode/hdg
/instrumentation/annunciators/ap/mode/ias
/instrumentation/annunciators/ap/mode/nav
/instrumentation/annunciators/ap/mode/rev
/instrumentation/annunciators/ap/mode/vs

/instrumentation/annunciators/engines/
/instrumentation/annunciators/engines/apu
/instrumentation/annunciators/engines/fire
/instrumentation/annunciators/engines/oil-pressure-low
/instrumentation/annunciators/engines/starter
# for <gear-name> in {nose, left, right}
/instrumentation/annunciators/gear/<gear-name>/down
/instrumentation/annunciators/gear/<gear-name>/in-transition
/instrumentation/annunciators/gear/<gear-name>/unsafe
/instrumentation/annunciators/gear/<gear-name>/up

/instrumentation/annunciators/gear/parking-brake

/instrumentation/annunciators/systems/anti-ice/enabled
/instrumentation/annunciators/systems/fuel/aux-pump
/instrumentation/annunciators/systems/fuel/pressure-low
/instrumentation/annunciators/systems/hyd/pressure-low
/instrumentation/annunciators/systems/vacuum

</pre>

== Consumables ==
:''See also [[#Fuel]]
<pre>
/consumables/fuel/tank[%d]/level-lb
/consumables/fuel/tank[%d]/level-lbs
/consumables/fuel/tank[%d]/level-gal_us
/consumables/fuel/tank[%d]/capacity-gal_us
/consumables/fuel/tank[%d]/density-ppg
/consumables/fuel/total-fuel-lbs
/consumables/fuel/total-gal_us
</pre>

== Controls ==
These properties should, and usually do correspond to how various cockpit controls are set. Consider these the pilot input.

=== Anti-ice ===
These properties control the various anti-ice properties that may be present in an aircraft.

<pre>
/controls/anti-ice/wing-heat
/controls/anti-ice/pitot-heat
/controls/anti-ice/wiper
/controls/anti-ice/window-heat
/controls/anti-ice/engine[%d]/carb-heat
/controls/anti-ice/engine[%d]/inlet-heat
</pre>
TODO - section notes

=== APU ===
These properties control any auxiliary power unit, in essence a small turbine engine driving generators, hydraulic pumps etc. before and after the aircraft's engines are up an running.

<pre>
/controls/APU/off-start-run
/controls/APU/fire-switch
</pre>
TODO - section notes

=== Armament ===
TODO - explain of section
<pre>
/controls/armament/master-arm
/controls/armament/station-select
/controls/armament/release-all
/controls/armament/station[%d]/stick-size
/controls/armament/station[%d]/release-stick
/controls/armament/station[%d]/release-all
/controls/armament/station[%d]/jettison-all
</pre>
TODO - section notes

=== Autoflight ===
These properties control the autopilot.

TODO - explain of section
<pre>
/controls/autoflight/autopilot[%d]/engage
/controls/autoflight/autothrottle-arm
/controls/autoflight/autothrottle-engage
/controls/autoflight/heading-select
/controls/autoflight/altitude-select
/controls/autoflight/bank-angle-select
/controls/autoflight/vertical-speed-select
/controls/autoflight/speed-select
/controls/autoflight/mach-select
/controls/autoflight/vertical-mode
/controls/autoflight/lateral-mode
</pre>
TODO - section notes

=== Electric ===
TODO - explain of section
<pre>
/controls/electric/battery-switch
/controls/electric/external-power
/controls/electric/APU-generator
/controls/electric/engine[%d]/generator
/controls/electric/engine[%d]/bus-tie
</pre>
TODO - section notes

=== Engines ===
Engines are numbered engine[0] for a single engine to engine[0] to engine[3] for a 747 for example. (The model allows for up to 12 engines rumour has it ;-)

<pre>
/controls/engines/throttle_idle
/controls/engines/engine[%d]/throttle
/controls/engines/engine[%d]/starter
/controls/engines/engine[%d]/fuel-pump
/controls/engines/engine[%d]/fire-switch
/controls/engines/engine[%d]/fire-bottle-discharge
/controls/engines/engine[%d]/cutoff
/controls/engines/engine[%d]/mixture
/controls/engines/engine[%d]/propeller-pitch
/controls/engines/engine[%d]/magnetos
/controls/engines/engine[%d]/boost
/controls/engines/engine[%d]/WEP
/controls/engines/engine[%d]/cowl-flaps-norm
/controls/engines/engine[%d]/feather
/controls/engines/engine[%d]/ignition
/controls/engines/engine[%d]/augmentation
/controls/engines/engine[%d]/afterburner
/controls/engines/engine[%d]/reverser
/controls/engines/engine[%d]/water-injection
/controls/engines/engine[%d]/condition
</pre>
TODO - section notes

=== Flight controls ===
These properties control the flight controls surfaces, though often through a mechanical, analog or digital flight control system (FCS) that may or may not be modeled.

<pre>
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/flight/flaps
/controls/flight/slats
/controls/flight/BLC // Boundary Layer Control
/controls/flight/spoilers
/controls/flight/speedbrake
/controls/flight/wing-sweep
/controls/flight/wing-fold
/controls/flight/drag-chute
</pre>

The positions of the controls are usually put in <code>/surface-positions/</code> at the discretion of the aircraft designer. These usually drive the animations of the control surfaces. They are either normalized (like <code>/surface-positions/elevator-pos-norm</code>) or in degrees, and sometimes the aileron is split left/right.

=== Fuel ===
TODO - explain of section
<pre>
/controls/fuel/dump-valve
/controls/fuel/tank[%d]/fuel_selector
/controls/fuel/tank[%d]/to_engine
/controls/fuel/tank[%d]/to_tank
/controls/fuel/tank[%d]/boost-pump[%d]
</pre>
TODO - section notes

=== Gear ===
TODO - explain of section
<pre>
/controls/gear/brake-left
/controls/gear/brake-right
/controls/gear/brake-parking
/controls/gear/steering // Used if rudder is not sufficient for control of steering
/controls/gear/gear-down
/controls/gear/antiskid // Deprecated?
/controls/gear/tailhook
/controls/gear/tailwheel-lock
/controls/gear/wheel[%d]/alternate-extension
</pre>
TODO - section notes

=== Hydraulics ===
TODO - explain of section
<pre>
/controls/hydraulic/system[%d]/engine-pump
/controls/hydraulic/system[%d]/electric-pump
</pre>
TODO - section notes

=== Lights ===
TODO - explain of section
<pre>
/controls/lighting/landing-lights
/controls/lighting/turn-off-lights
/controls/lighting/formation-lights
/controls/lighting/taxi-light
/controls/lighting/logo-lights
/controls/lighting/nav-lights
/controls/lighting/beacon
/controls/lighting/strobe
/controls/lighting/panel-norm
/controls/lighting/instruments-norm
/controls/lighting/dome-norm
</pre>
TODO - section notes

=== Pneumatic ===
TODO - explain of section
<pre>
/controls/pneumatic/APU-bleed
/controls/pneumatic/engine[%d]/bleed
</pre>
TODO - section notes

=== Pressurization ===
TODO - explain of section
<pre>
/controls/pressurization/mode
/controls/pressurization/dump
/controls/pressurization/outflow-valve
/controls/pressurization/pack[%d]/pack-on
</pre>
TODO - section notes

=== Seat ===
TODO - explain of section
<pre>
/controls/seat/vertical-adjust
/controls/seat/fore-aft-adjust
/controls/seat/cmd_selector_valve
/controls/seat/eject[%d]/initiate
/controls/seat/eject[%d]/status
</pre>
TODO - section notes

== Engines ==
Status of engines. See also: /controls/engines/
=== Common ===
<pre>
/engines/engine[%d]/fuel-flow-gph
/engines/engine[%d]/fuel-flow_pph
/engines/engine[%d]/thrust_lb
/engines/engine[%d]/running
/engines/engine[%d]/starter
/engines/engine[%d]/cranking
/engines/engine[%d]/fire
</pre>

=== Turbine ===
<pre>
/engines/engine[%d]/n1
/engines/engine[%d]/n2
/engines/engine[%d]/epr
/engines/engine[%d]/augmentation
/engines/engine[%d]/water-injection
/engines/engine[%d]/ignition
/engines/engine[%d]/nozzle-pos-norm
/engines/engine[%d]/inlet-pos-norm
/engines/engine[%d]/reversed
/engines/engine[%d]/cutoff
</pre>

=== Piston ===
<pre>
/engines/engine[%d]/mp-osi
/engines/engine[%d]/egt-degf
/engines/engine[%d]/oil-temperature-degf
/engines/engine[%d]/oil-pressure-psi
/engines/engine[%d]/cht-degf
/engines/engine[%d]/rpm
</pre>

=== Propeller ===
<pre>
/engines/engine[%d]/rpm
/engines/engine[%d]/pitch
/engines/engine[%d]/torque
</pre>
TODO - section notes

== Flight Dynamics Model ==
=== Position ===
This will return the current position of the aircraft within FlightGear. This is also the stuff that is transmitted in [[Howto:Multiplayer|multiplayer]].

<pre>
/position/
/position/altitiude-ft ()
/position/altitude-agl-ft (22.46983965)
/position/altitude-ft (28.24368289)
/position/ground-elev-ft (-0.43513529)
/position/ground-elev-m (-0.1326292364)
/position/latitude-deg (37.61371436)
/position/latitude-string (37*36 49.4N)
/position/longitude-deg (-122.3576508)
/position/longitude-string (-122*21 27.5W)
/position/sea-level-radius-ft (20899648.76)
</pre>

=== Orientation ===
TODO - explain of section
<pre>
/orientation/roll-deg
/orientation/pitch-deg
/orientation/heading-deg

/orientation/roll-rate-degps
/orientation/pitch-rate-degps
/orientation/yaw-rate-degps

/orientation/side-slip-rad
/orientation/side-slip-deg
/orientation/alpha-deg
</pre>
TODO - section notes

=== Velocities ===
TODO - explain of section
<pre>
/velocities/airspeed-kt
/velocities/mach
/velocities/speed-north-fps
/velocities/speed-east-fps
/velocities/speed-down-fps

/velocities/uBody-fps
/velocities/vBody-fps
/velocities/wBody-fps

/velocities/vertical-speed-fps
/velocities/glideslope
</pre>
TODO - section notes

=== Acceleration ===
TODO - explain of section
<pre>
/accelerations/nlf

/accelerations/ned/north-accel-fps_sec
/accelerations/ned/east-accel-fps_sec
/accelerations/ned/down-accel-fps_sec

/accelerations/pilot/x-accel-fps_sec
/accelerations/pilot/y-accel-fps_sec
/accelerations/pilot/z-accel-fps_sec
</pre>
TODO - section notes

== Gear ==
<pre>
/gear/serviceable
/gear/gear[%d]/cast-angle-deg // The angle of the wheel where 0 is pointing straight forward
/gear/gear[%d]/compression-m
/gear/gear[%d]/compression-norm
/gear/gear[%d]/ground-friction-factor
/gear/gear[%d]/ground-is-solid
/gear/gear[%d]/has-brake
/gear/gear[%d]/rollspeed-ms // Speed of the wheel's rotation in meters per second
/gear/gear[%d]/wow // Weight-on-wheel
/gear/gear[%d]/xoffset-in
/gear/gear[%d]/yoffset-in
/gear/gear[%d]/zoffset-in
</pre>

== Instrumentation ==
<pre>
/instrumentation/adf[%d]/
/instrumentation/airspeed-indicator/
/instrumentation/altimeter/
/instrumentation/annunciator/
/instrumentation/attitude-indicator/
/instrumentation/clock/
/instrumentation/comm[%d]/
/instrumentation/dme/
/instrumentation/efis/
/instrumentation/encoder/
/instrumentation/flightdirector/
/instrumentation/gps/
/instrumentation/gps-annunciator/
/instrumentation/heading-indicator/
/instrumentation/heading-indicator-fg/
/instrumentation/magnetic-compass/
/instrumentation/marker-beacon/
/instrumentation/nav[%d]/
/instrumentation/radar/
/instrumentation/slip-skid-ball/
/instrumentation/tacan[%d]/
/instrumentation/transponder/
/instrumentation/turn-indicator/
/instrumentation/vertical-speed-indicator/
/instrumentation/wxradar/
</pre>

=== Instrumentation ADF ===
<pre>
/instrumentation/adf[%d]/adf-btn
/instrumentation/adf[%d]/bro-btn
/instrumentation/adf[%d]/display-mode
/instrumentation/adf[%d]/enroute-timer/running
/instrumentation/adf[%d]/enroute-timer/start-time
/instrumentation/adf[%d]/enroute-timer/time
/instrumentation/adf[%d]/error-deg
/instrumentation/adf[%d]/flight-timer/running
/instrumentation/adf[%d]/flight-timer/start-time
/instrumentation/adf[%d]/flight-timer/time
/instrumentation/adf[%d]/flt-btn
/instrumentation/adf[%d]/frequencies/dial-1-khz
/instrumentation/adf[%d]/frequencies/dial-100-khz
/instrumentation/adf[%d]/frequencies/selected-khz
/instrumentation/adf[%d]/frequencies/standby-khz
/instrumentation/adf[%d]/frq-btn
/instrumentation/adf[%d]/ident
/instrumentation/adf[[%d]/ident-audible
/instrumentation/adf[%d]/in-range
/instrumentation/adf[%d]/indicated-bearing-deg
/instrumentation/adf[%d]/mode
/instrumentation/adf[%d]/model
/instrumentation/adf[%d]/operable
/instrumentation/adf[%d]/power-btn
/instrumentation/adf[%d]/right-display
/instrumentation/adf[%d]/rotation-deg
/instrumentation/adf[%d]/serviceable
/instrumentation/adf[%d]/set-btn
/instrumentation/adf[%d]/volume
/instrumentation/adf[%d]/volume-norm
</pre>
=== Instrumentation comm radio ===

<pre>
/instrumentation/comm[%d]/add-noise
/instrumentation/comm[%d]/airport-id
/instrumentation/comm[%d]/atis
/instrumentation/comm[%d]/channel-button
/instrumentation/comm[%d]/chanel-mode-selector
/instrumentation/comm[%d]/cutoff-signal-quality
/instrumentation/comm[%d]/frequencies
/instrumentation/comm[%d]/frequencies/dial-khz
/instrumentation/comm[%d]/frequencies/dial-mhz
/instrumentation/comm[%d]/frequencies/selected-channel
/instrumentation/comm[%d]/frequencies/selected-channel-width-khz
/instrumentation/comm[%d]/frequencies/selected-mhz
/instrumentation/comm[%d]/frequencies/selected-mhz-fmt
/instrumentation/comm[%d]/frequencies/selected-real-frequency-mhz
/instrumentation/comm[%d]/frequencies/standby-channel
/instrumentation/comm[%d]/frequencies/standby-channel-width-khz
/instrumentation/comm[%d]/frequencies/standby-mhz
/instrumentation/comm[%d]/frequencies/standby-mhz-fmt
/instrumentation/comm[%d]/frequencies/standby-real-frequency-mhz
/instrumentation/comm[%d]/frq-swap-btn
/instrumentation/comm[%d]/height-above-station-ft
/instrumentation/comm[%d]/operable
/instrumentation/comm[%d]/power-btn
/instrumentation/comm[%d]/ptt
/instrumentation/comm[%d]/servicable
/instrumentation/comm[%d]/signal-quality-norm
/instrumentation/comm[%d]/slant-distance-m
/instrumentation/comm[%d]/station-name
/instrumentation/comm[%d]/station-type
/instrumentation/comm[%d]/test-btn
/instrumentation/comm[%d]/track-distance-m
/instrumentation/comm[%d]/true-bearing-from-deg
/instrumentation/comm[%d]/true-bearing-to-deg
/instrumentation/comm[%d]/volume
/instrumentation/comm[%d]/volume-selected
</pre>

=== Instrumentation Tacan ===

<pre>
/instrumentation/tacan[%d]/display/channel
/instrumentation/tacan[%d]/display/x-shift
/instrumentation/tacan[%d]/display/y-shift
/instrumentation/tacan[%d]/frequencies/selected-channel
/instrumentation/tacan[%d]/frequencies/selected-channel[1]
/instrumentation/tacan[%d]/frequencies/selected-channel[2]
/instrumentation/tacan[%d]/frequencies/selected-channel[3]
/instrumentation/tacan[%d]/frequencies/selected-channel[4]
/instrumentation/tacan[%d]/frequencies/selected-mhz
/instrumentation/tacan[%d]/ident
/instrumentation/tacan[%d]/in-range
/instrumentation/tacan[%d]/indicated-bearing-true-deg
/instrumentation/tacan[%d]/indicated-distance-nm
/instrumentation/tacan[%d]/indicated-ground-speed-kt
/instrumentation/tacan[%d]/indicated-time-min
/instrumentation/tacan[%d]/name
/instrumentation/tacan[%d]/serviceable
/instrumentation/tacan[%d]/switch-position
</pre>

== Rotors (YASim only) ==
<pre>
/rotors/gear/torque-sound-filtered // Unused?
/rotors/gear/total-torque
/rotors/{name}/balance
/rotors/{name}/blade[%d]/flap-deg
/rotors/{name}/blade[%d]/incidence-deg
/rotors/{name}/blade[%d]/position-deg // Position relative to model
/rotors/{name}/bladesvisible // Used for animations
/rotors/{name}/cone%d-deg //e.g. cone-deg or cone2-deg
/rotors/{name}/roll-deg
/rotors/{name}/rpm
/rotors/{name}/stall
/rotors/{name}/stall-filtered
/rotors/{name}/tilt
/rotors/{name}/torque
/rotors/{name}/yaw-deg
</pre>

For how to animate rotors using these properties, see [[Howto:Animate helicopters]].

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Multiplayer protocol]]
* [[Property browser]]
* [[PropertyList XML files]]
* [[Property tree]]

=== Readme files ===
* {{readme file|properties}}

=== Source code ===
==== Consumables ====
* {{flightgear file|src/FDM/TankProperties.hxx}}
* {{flightgear file|src/FDM/TankProperties.cxx}}

==== Controls ====
* {{flightgear file|src/Aircraft/controls.hxx}}
* {{flightgear file|src/Aircraft/controls.cxx}}

==== Flight Dynamics Model ====
* {{flightgear file|src/FDM/flightProperties.hxx}}
* {{flightgear file|src/FDM/flightProperties.cxx}}

==== Instrumentation ====
* {{flightgear file|src/Instrumentation}}

[[Category:Property Tree]]
[[Category:Aircraft enhancement]]

Aircraft properties reference

2024-04-15T22:18:33Z

Www2: /* Instrumentation */ Add Instrumentation ADF

{{PropertyTree}}

This is a generic '''aircraft properties reference'''. There are many properties that are very common in aircraft, and many of them are present even in a very simple aircraft. However, a complete description that matches all the properties is very unlikely to be written, as aircraft can be very different from each other.

{{TOC limit|2}}

== What are properties? ==
{{main article|Property tree}}
=== The property tree ===
Most parts of FlightGear communicate with each other through key-value pair properties in the [[property tree]]. The properties represent both the input from the pilot, the values determining the position and velocity of the aircraft, the values used for animating the aircraft, and pretty much anything else.

While many properties will be common between most aircraft, many properties will also be different between aircraft. This becomes obvious if one consider the many different configurations (aircraft/helicopter/car, control surface and landing gear layout, number and locations of engines, etc) and propulsions systems (types of engines, types of fuels etc.) an aircraft can have. There are also different flight dynamic models (FDMs) that have different needs. In addition many properties will by necessity be aircraft specific, though developers should make a conscious effort to have properties map to more common ones if that is possible.

=== Where are the properties defined? ===
There are a couple ways that the properties are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties. One is in the aircraft files, starting from the aircraft specific [[aircraft-set.xml]] file, another is the [[Nasal]] files, and the last place (and often most useful!) is "grepping" (searching) through the C++ code.

To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better

== Annunciators [draft] ==
!! This section is work in progress !!

The /instrumentation/annunciators section shall provide a central place for

* aircrafts to write annunciator status data
* 3D aircraft models and external devices (like joysticks, yokes, throttle quadrants or custom made cockpit hardware) to read such data and drive status lights etc.

Some of the props are automatically calculated by property rules in $FGDATA/Aircraft/Generic/generic-annunciators.xml other properties have to be calculated by the actual aircraft.

The aircraft.nas module provides aircraft.light which allows easy implementation of blinking lights. Such lights have a bool property 'state' which tells if the light is on or off.<pre>
/instrumentation/annunciators/doors
/instrumentation/annunciators/master-caution/state # aircraft.light
/instrumentation/annunciators/master-warning/state # aircraft.light

/instrumentation/annunciators/ap/enabled
/instrumentation/annunciators/ap/mode/alt
/instrumentation/annunciators/ap/mode/apr
/instrumentation/annunciators/ap/mode/hdg
/instrumentation/annunciators/ap/mode/ias
/instrumentation/annunciators/ap/mode/nav
/instrumentation/annunciators/ap/mode/rev
/instrumentation/annunciators/ap/mode/vs

/instrumentation/annunciators/engines/
/instrumentation/annunciators/engines/apu
/instrumentation/annunciators/engines/fire
/instrumentation/annunciators/engines/oil-pressure-low
/instrumentation/annunciators/engines/starter
# for <gear-name> in {nose, left, right}
/instrumentation/annunciators/gear/<gear-name>/down
/instrumentation/annunciators/gear/<gear-name>/in-transition
/instrumentation/annunciators/gear/<gear-name>/unsafe
/instrumentation/annunciators/gear/<gear-name>/up

/instrumentation/annunciators/gear/parking-brake

/instrumentation/annunciators/systems/anti-ice/enabled
/instrumentation/annunciators/systems/fuel/aux-pump
/instrumentation/annunciators/systems/fuel/pressure-low
/instrumentation/annunciators/systems/hyd/pressure-low
/instrumentation/annunciators/systems/vacuum

</pre>

== Consumables ==
:''See also [[#Fuel]]
<pre>
/consumables/fuel/tank[%d]/level-lb
/consumables/fuel/tank[%d]/level-lbs
/consumables/fuel/tank[%d]/level-gal_us
/consumables/fuel/tank[%d]/capacity-gal_us
/consumables/fuel/tank[%d]/density-ppg
/consumables/fuel/total-fuel-lbs
/consumables/fuel/total-gal_us
</pre>

== Controls ==
These properties should, and usually do correspond to how various cockpit controls are set. Consider these the pilot input.

=== Anti-ice ===
These properties control the various anti-ice properties that may be present in an aircraft.

<pre>
/controls/anti-ice/wing-heat
/controls/anti-ice/pitot-heat
/controls/anti-ice/wiper
/controls/anti-ice/window-heat
/controls/anti-ice/engine[%d]/carb-heat
/controls/anti-ice/engine[%d]/inlet-heat
</pre>
TODO - section notes

=== APU ===
These properties control any auxiliary power unit, in essence a small turbine engine driving generators, hydraulic pumps etc. before and after the aircraft's engines are up an running.

<pre>
/controls/APU/off-start-run
/controls/APU/fire-switch
</pre>
TODO - section notes

=== Armament ===
TODO - explain of section
<pre>
/controls/armament/master-arm
/controls/armament/station-select
/controls/armament/release-all
/controls/armament/station[%d]/stick-size
/controls/armament/station[%d]/release-stick
/controls/armament/station[%d]/release-all
/controls/armament/station[%d]/jettison-all
</pre>
TODO - section notes

=== Autoflight ===
These properties control the autopilot.

TODO - explain of section
<pre>
/controls/autoflight/autopilot[%d]/engage
/controls/autoflight/autothrottle-arm
/controls/autoflight/autothrottle-engage
/controls/autoflight/heading-select
/controls/autoflight/altitude-select
/controls/autoflight/bank-angle-select
/controls/autoflight/vertical-speed-select
/controls/autoflight/speed-select
/controls/autoflight/mach-select
/controls/autoflight/vertical-mode
/controls/autoflight/lateral-mode
</pre>
TODO - section notes

=== Electric ===
TODO - explain of section
<pre>
/controls/electric/battery-switch
/controls/electric/external-power
/controls/electric/APU-generator
/controls/electric/engine[%d]/generator
/controls/electric/engine[%d]/bus-tie
</pre>
TODO - section notes

=== Engines ===
Engines are numbered engine[0] for a single engine to engine[0] to engine[3] for a 747 for example. (The model allows for up to 12 engines rumour has it ;-)

<pre>
/controls/engines/throttle_idle
/controls/engines/engine[%d]/throttle
/controls/engines/engine[%d]/starter
/controls/engines/engine[%d]/fuel-pump
/controls/engines/engine[%d]/fire-switch
/controls/engines/engine[%d]/fire-bottle-discharge
/controls/engines/engine[%d]/cutoff
/controls/engines/engine[%d]/mixture
/controls/engines/engine[%d]/propeller-pitch
/controls/engines/engine[%d]/magnetos
/controls/engines/engine[%d]/boost
/controls/engines/engine[%d]/WEP
/controls/engines/engine[%d]/cowl-flaps-norm
/controls/engines/engine[%d]/feather
/controls/engines/engine[%d]/ignition
/controls/engines/engine[%d]/augmentation
/controls/engines/engine[%d]/afterburner
/controls/engines/engine[%d]/reverser
/controls/engines/engine[%d]/water-injection
/controls/engines/engine[%d]/condition
</pre>
TODO - section notes

=== Flight controls ===
These properties control the flight controls surfaces, though often through a mechanical, analog or digital flight control system (FCS) that may or may not be modeled.

<pre>
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/flight/flaps
/controls/flight/slats
/controls/flight/BLC // Boundary Layer Control
/controls/flight/spoilers
/controls/flight/speedbrake
/controls/flight/wing-sweep
/controls/flight/wing-fold
/controls/flight/drag-chute
</pre>

The positions of the controls are usually put in <code>/surface-positions/</code> at the discretion of the aircraft designer. These usually drive the animations of the control surfaces. They are either normalized (like <code>/surface-positions/elevator-pos-norm</code>) or in degrees, and sometimes the aileron is split left/right.

=== Fuel ===
TODO - explain of section
<pre>
/controls/fuel/dump-valve
/controls/fuel/tank[%d]/fuel_selector
/controls/fuel/tank[%d]/to_engine
/controls/fuel/tank[%d]/to_tank
/controls/fuel/tank[%d]/boost-pump[%d]
</pre>
TODO - section notes

=== Gear ===
TODO - explain of section
<pre>
/controls/gear/brake-left
/controls/gear/brake-right
/controls/gear/brake-parking
/controls/gear/steering // Used if rudder is not sufficient for control of steering
/controls/gear/gear-down
/controls/gear/antiskid // Deprecated?
/controls/gear/tailhook
/controls/gear/tailwheel-lock
/controls/gear/wheel[%d]/alternate-extension
</pre>
TODO - section notes

=== Hydraulics ===
TODO - explain of section
<pre>
/controls/hydraulic/system[%d]/engine-pump
/controls/hydraulic/system[%d]/electric-pump
</pre>
TODO - section notes

=== Lights ===
TODO - explain of section
<pre>
/controls/lighting/landing-lights
/controls/lighting/turn-off-lights
/controls/lighting/formation-lights
/controls/lighting/taxi-light
/controls/lighting/logo-lights
/controls/lighting/nav-lights
/controls/lighting/beacon
/controls/lighting/strobe
/controls/lighting/panel-norm
/controls/lighting/instruments-norm
/controls/lighting/dome-norm
</pre>
TODO - section notes

=== Pneumatic ===
TODO - explain of section
<pre>
/controls/pneumatic/APU-bleed
/controls/pneumatic/engine[%d]/bleed
</pre>
TODO - section notes

=== Pressurization ===
TODO - explain of section
<pre>
/controls/pressurization/mode
/controls/pressurization/dump
/controls/pressurization/outflow-valve
/controls/pressurization/pack[%d]/pack-on
</pre>
TODO - section notes

=== Seat ===
TODO - explain of section
<pre>
/controls/seat/vertical-adjust
/controls/seat/fore-aft-adjust
/controls/seat/cmd_selector_valve
/controls/seat/eject[%d]/initiate
/controls/seat/eject[%d]/status
</pre>
TODO - section notes

== Engines ==
Status of engines. See also: /controls/engines/
=== Common ===
<pre>
/engines/engine[%d]/fuel-flow-gph
/engines/engine[%d]/fuel-flow_pph
/engines/engine[%d]/thrust_lb
/engines/engine[%d]/running
/engines/engine[%d]/starter
/engines/engine[%d]/cranking
/engines/engine[%d]/fire
</pre>

=== Turbine ===
<pre>
/engines/engine[%d]/n1
/engines/engine[%d]/n2
/engines/engine[%d]/epr
/engines/engine[%d]/augmentation
/engines/engine[%d]/water-injection
/engines/engine[%d]/ignition
/engines/engine[%d]/nozzle-pos-norm
/engines/engine[%d]/inlet-pos-norm
/engines/engine[%d]/reversed
/engines/engine[%d]/cutoff
</pre>

=== Piston ===
<pre>
/engines/engine[%d]/mp-osi
/engines/engine[%d]/egt-degf
/engines/engine[%d]/oil-temperature-degf
/engines/engine[%d]/oil-pressure-psi
/engines/engine[%d]/cht-degf
/engines/engine[%d]/rpm
</pre>

=== Propeller ===
<pre>
/engines/engine[%d]/rpm
/engines/engine[%d]/pitch
/engines/engine[%d]/torque
</pre>
TODO - section notes

== Flight Dynamics Model ==
=== Position ===
This will return the current position of the aircraft within FlightGear. This is also the stuff that is transmitted in [[Howto:Multiplayer|multiplayer]].

<pre>
/position/
/position/altitiude-ft ()
/position/altitude-agl-ft (22.46983965)
/position/altitude-ft (28.24368289)
/position/ground-elev-ft (-0.43513529)
/position/ground-elev-m (-0.1326292364)
/position/latitude-deg (37.61371436)
/position/latitude-string (37*36 49.4N)
/position/longitude-deg (-122.3576508)
/position/longitude-string (-122*21 27.5W)
/position/sea-level-radius-ft (20899648.76)
</pre>

=== Orientation ===
TODO - explain of section
<pre>
/orientation/roll-deg
/orientation/pitch-deg
/orientation/heading-deg

/orientation/roll-rate-degps
/orientation/pitch-rate-degps
/orientation/yaw-rate-degps

/orientation/side-slip-rad
/orientation/side-slip-deg
/orientation/alpha-deg
</pre>
TODO - section notes

=== Velocities ===
TODO - explain of section
<pre>
/velocities/airspeed-kt
/velocities/mach
/velocities/speed-north-fps
/velocities/speed-east-fps
/velocities/speed-down-fps

/velocities/uBody-fps
/velocities/vBody-fps
/velocities/wBody-fps

/velocities/vertical-speed-fps
/velocities/glideslope
</pre>
TODO - section notes

=== Acceleration ===
TODO - explain of section
<pre>
/accelerations/nlf

/accelerations/ned/north-accel-fps_sec
/accelerations/ned/east-accel-fps_sec
/accelerations/ned/down-accel-fps_sec

/accelerations/pilot/x-accel-fps_sec
/accelerations/pilot/y-accel-fps_sec
/accelerations/pilot/z-accel-fps_sec
</pre>
TODO - section notes

== Gear ==
<pre>
/gear/serviceable
/gear/gear[%d]/cast-angle-deg // The angle of the wheel where 0 is pointing straight forward
/gear/gear[%d]/compression-m
/gear/gear[%d]/compression-norm
/gear/gear[%d]/ground-friction-factor
/gear/gear[%d]/ground-is-solid
/gear/gear[%d]/has-brake
/gear/gear[%d]/rollspeed-ms // Speed of the wheel's rotation in meters per second
/gear/gear[%d]/wow // Weight-on-wheel
/gear/gear[%d]/xoffset-in
/gear/gear[%d]/yoffset-in
/gear/gear[%d]/zoffset-in
</pre>

== Instrumentation ==
<pre>
/instrumentation/adf[%d]/
/instrumentation/airspeed-indicator/
/instrumentation/altimeter/
/instrumentation/annunciator/
/instrumentation/attitude-indicator/
/instrumentation/clock/
/instrumentation/comm[%d]/
/instrumentation/dme/
/instrumentation/efis/
/instrumentation/encoder/
/instrumentation/flightdirector/
/instrumentation/gps/
/instrumentation/gps-annunciator/
/instrumentation/heading-indicator/
/instrumentation/heading-indicator-fg/
/instrumentation/magnetic-compass/
/instrumentation/marker-beacon/
/instrumentation/nav[%d]/
/instrumentation/radar/
/instrumentation/slip-skid-ball/
/instrumentation/tacan[%d]/
/instrumentation/transponder/
/instrumentation/turn-indicator/
/instrumentation/vertical-speed-indicator/
/instrumentation/wxradar/
</pre>

=== Instrumentation ADF ===
<pre>
/instrumentation/adf[[%d]/adf-btn
/instrumentation/adf[[%d]/bro-btn
/instrumentation/adf[[%d]/display-mode
/instrumentation/adf[[%d]/enroute-timer/running
/instrumentation/adf[[%d]/enroute-timer/start-time
/instrumentation/adf[[%d]/enroute-timer/time
/instrumentation/adf[[%d]/error-deg
/instrumentation/adf[[%d]/flight-timer/running
/instrumentation/adf[[%d]/flight-timer/start-time
/instrumentation/adf[[%d]/flight-timer/time
/instrumentation/adf[[%d]/flt-btn
/instrumentation/adf[[%d]/frequencies/dial-1-khz
/instrumentation/adf[[%d]/frequencies/dial-100-khz
/instrumentation/adf[[%d]/frequencies/selected-khz
/instrumentation/adf[[%d]/frequencies/standby-khz
/instrumentation/adf[[%d]/frq-btn
/instrumentation/adf[[%d]/ident
/instrumentation/adf[[%d]/ident-audible
/instrumentation/adf[[%d]/in-range
/instrumentation/adf[[%d]/indicated-bearing-deg
/instrumentation/adf[[%d]/mode
/instrumentation/adf[[%d]/model
/instrumentation/adf[[%d]/operable
/instrumentation/adf[[%d]/power-btn
/instrumentation/adf[[%d]/right-display
/instrumentation/adf[[%d]/rotation-deg
/instrumentation/adf[[%d]/serviceable
/instrumentation/adf[[%d]/set-btn
/instrumentation/adf[[%d]/volume
/instrumentation/adf[[%d]/volume-norm
</pre>
=== Instrumentation comm radio ===

<pre>
/instrumentation/comm[%d]/add-noise
/instrumentation/comm[%d]/airport-id
/instrumentation/comm[%d]/atis
/instrumentation/comm[%d]/channel-button
/instrumentation/comm[%d]/chanel-mode-selector
/instrumentation/comm[%d]/cutoff-signal-quality
/instrumentation/comm[%d]/frequencies
/instrumentation/comm[%d]/frequencies/dial-khz
/instrumentation/comm[%d]/frequencies/dial-mhz
/instrumentation/comm[%d]/frequencies/selected-channel
/instrumentation/comm[%d]/frequencies/selected-channel-width-khz
/instrumentation/comm[%d]/frequencies/selected-mhz
/instrumentation/comm[%d]/frequencies/selected-mhz-fmt
/instrumentation/comm[%d]/frequencies/selected-real-frequency-mhz
/instrumentation/comm[%d]/frequencies/standby-channel
/instrumentation/comm[%d]/frequencies/standby-channel-width-khz
/instrumentation/comm[%d]/frequencies/standby-mhz
/instrumentation/comm[%d]/frequencies/standby-mhz-fmt
/instrumentation/comm[%d]/frequencies/standby-real-frequency-mhz
/instrumentation/comm[%d]/frq-swap-btn
/instrumentation/comm[%d]/height-above-station-ft
/instrumentation/comm[%d]/operable
/instrumentation/comm[%d]/power-btn
/instrumentation/comm[%d]/ptt
/instrumentation/comm[%d]/servicable
/instrumentation/comm[%d]/signal-quality-norm
/instrumentation/comm[%d]/slant-distance-m
/instrumentation/comm[%d]/station-name
/instrumentation/comm[%d]/station-type
/instrumentation/comm[%d]/test-btn
/instrumentation/comm[%d]/track-distance-m
/instrumentation/comm[%d]/true-bearing-from-deg
/instrumentation/comm[%d]/true-bearing-to-deg
/instrumentation/comm[%d]/volume
/instrumentation/comm[%d]/volume-selected
</pre>

=== Instrumentation Tacan ===

<pre>
/instrumentation/tacan[%d]/display/channel
/instrumentation/tacan[%d]/display/x-shift
/instrumentation/tacan[%d]/display/y-shift
/instrumentation/tacan[%d]/frequencies/selected-channel
/instrumentation/tacan[%d]/frequencies/selected-channel[1]
/instrumentation/tacan[%d]/frequencies/selected-channel[2]
/instrumentation/tacan[%d]/frequencies/selected-channel[3]
/instrumentation/tacan[%d]/frequencies/selected-channel[4]
/instrumentation/tacan[%d]/frequencies/selected-mhz
/instrumentation/tacan[%d]/ident
/instrumentation/tacan[%d]/in-range
/instrumentation/tacan[%d]/indicated-bearing-true-deg
/instrumentation/tacan[%d]/indicated-distance-nm
/instrumentation/tacan[%d]/indicated-ground-speed-kt
/instrumentation/tacan[%d]/indicated-time-min
/instrumentation/tacan[%d]/name
/instrumentation/tacan[%d]/serviceable
/instrumentation/tacan[%d]/switch-position
</pre>

== Rotors (YASim only) ==
<pre>
/rotors/gear/torque-sound-filtered // Unused?
/rotors/gear/total-torque
/rotors/{name}/balance
/rotors/{name}/blade[%d]/flap-deg
/rotors/{name}/blade[%d]/incidence-deg
/rotors/{name}/blade[%d]/position-deg // Position relative to model
/rotors/{name}/bladesvisible // Used for animations
/rotors/{name}/cone%d-deg //e.g. cone-deg or cone2-deg
/rotors/{name}/roll-deg
/rotors/{name}/rpm
/rotors/{name}/stall
/rotors/{name}/stall-filtered
/rotors/{name}/tilt
/rotors/{name}/torque
/rotors/{name}/yaw-deg
</pre>

For how to animate rotors using these properties, see [[Howto:Animate helicopters]].

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Multiplayer protocol]]
* [[Property browser]]
* [[PropertyList XML files]]
* [[Property tree]]

=== Readme files ===
* {{readme file|properties}}

=== Source code ===
==== Consumables ====
* {{flightgear file|src/FDM/TankProperties.hxx}}
* {{flightgear file|src/FDM/TankProperties.cxx}}

==== Controls ====
* {{flightgear file|src/Aircraft/controls.hxx}}
* {{flightgear file|src/Aircraft/controls.cxx}}

==== Flight Dynamics Model ====
* {{flightgear file|src/FDM/flightProperties.hxx}}
* {{flightgear file|src/FDM/flightProperties.cxx}}

==== Instrumentation ====
* {{flightgear file|src/Instrumentation}}

[[Category:Property Tree]]
[[Category:Aircraft enhancement]]

Aircraft properties reference

2024-04-15T22:06:42Z

Www2: /* Instrumentation */ Add tacan

{{PropertyTree}}

This is a generic '''aircraft properties reference'''. There are many properties that are very common in aircraft, and many of them are present even in a very simple aircraft. However, a complete description that matches all the properties is very unlikely to be written, as aircraft can be very different from each other.

{{TOC limit|2}}

== What are properties? ==
{{main article|Property tree}}
=== The property tree ===
Most parts of FlightGear communicate with each other through key-value pair properties in the [[property tree]]. The properties represent both the input from the pilot, the values determining the position and velocity of the aircraft, the values used for animating the aircraft, and pretty much anything else.

While many properties will be common between most aircraft, many properties will also be different between aircraft. This becomes obvious if one consider the many different configurations (aircraft/helicopter/car, control surface and landing gear layout, number and locations of engines, etc) and propulsions systems (types of engines, types of fuels etc.) an aircraft can have. There are also different flight dynamic models (FDMs) that have different needs. In addition many properties will by necessity be aircraft specific, though developers should make a conscious effort to have properties map to more common ones if that is possible.

=== Where are the properties defined? ===
There are a couple ways that the properties are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties. One is in the aircraft files, starting from the aircraft specific [[aircraft-set.xml]] file, another is the [[Nasal]] files, and the last place (and often most useful!) is "grepping" (searching) through the C++ code.

To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better

== Annunciators [draft] ==
!! This section is work in progress !!

The /instrumentation/annunciators section shall provide a central place for

* aircrafts to write annunciator status data
* 3D aircraft models and external devices (like joysticks, yokes, throttle quadrants or custom made cockpit hardware) to read such data and drive status lights etc.

Some of the props are automatically calculated by property rules in $FGDATA/Aircraft/Generic/generic-annunciators.xml other properties have to be calculated by the actual aircraft.

The aircraft.nas module provides aircraft.light which allows easy implementation of blinking lights. Such lights have a bool property 'state' which tells if the light is on or off.<pre>
/instrumentation/annunciators/doors
/instrumentation/annunciators/master-caution/state # aircraft.light
/instrumentation/annunciators/master-warning/state # aircraft.light

/instrumentation/annunciators/ap/enabled
/instrumentation/annunciators/ap/mode/alt
/instrumentation/annunciators/ap/mode/apr
/instrumentation/annunciators/ap/mode/hdg
/instrumentation/annunciators/ap/mode/ias
/instrumentation/annunciators/ap/mode/nav
/instrumentation/annunciators/ap/mode/rev
/instrumentation/annunciators/ap/mode/vs

/instrumentation/annunciators/engines/
/instrumentation/annunciators/engines/apu
/instrumentation/annunciators/engines/fire
/instrumentation/annunciators/engines/oil-pressure-low
/instrumentation/annunciators/engines/starter
# for <gear-name> in {nose, left, right}
/instrumentation/annunciators/gear/<gear-name>/down
/instrumentation/annunciators/gear/<gear-name>/in-transition
/instrumentation/annunciators/gear/<gear-name>/unsafe
/instrumentation/annunciators/gear/<gear-name>/up

/instrumentation/annunciators/gear/parking-brake

/instrumentation/annunciators/systems/anti-ice/enabled
/instrumentation/annunciators/systems/fuel/aux-pump
/instrumentation/annunciators/systems/fuel/pressure-low
/instrumentation/annunciators/systems/hyd/pressure-low
/instrumentation/annunciators/systems/vacuum

</pre>

== Consumables ==
:''See also [[#Fuel]]
<pre>
/consumables/fuel/tank[%d]/level-lb
/consumables/fuel/tank[%d]/level-lbs
/consumables/fuel/tank[%d]/level-gal_us
/consumables/fuel/tank[%d]/capacity-gal_us
/consumables/fuel/tank[%d]/density-ppg
/consumables/fuel/total-fuel-lbs
/consumables/fuel/total-gal_us
</pre>

== Controls ==
These properties should, and usually do correspond to how various cockpit controls are set. Consider these the pilot input.

=== Anti-ice ===
These properties control the various anti-ice properties that may be present in an aircraft.

<pre>
/controls/anti-ice/wing-heat
/controls/anti-ice/pitot-heat
/controls/anti-ice/wiper
/controls/anti-ice/window-heat
/controls/anti-ice/engine[%d]/carb-heat
/controls/anti-ice/engine[%d]/inlet-heat
</pre>
TODO - section notes

=== APU ===
These properties control any auxiliary power unit, in essence a small turbine engine driving generators, hydraulic pumps etc. before and after the aircraft's engines are up an running.

<pre>
/controls/APU/off-start-run
/controls/APU/fire-switch
</pre>
TODO - section notes

=== Armament ===
TODO - explain of section
<pre>
/controls/armament/master-arm
/controls/armament/station-select
/controls/armament/release-all
/controls/armament/station[%d]/stick-size
/controls/armament/station[%d]/release-stick
/controls/armament/station[%d]/release-all
/controls/armament/station[%d]/jettison-all
</pre>
TODO - section notes

=== Autoflight ===
These properties control the autopilot.

TODO - explain of section
<pre>
/controls/autoflight/autopilot[%d]/engage
/controls/autoflight/autothrottle-arm
/controls/autoflight/autothrottle-engage
/controls/autoflight/heading-select
/controls/autoflight/altitude-select
/controls/autoflight/bank-angle-select
/controls/autoflight/vertical-speed-select
/controls/autoflight/speed-select
/controls/autoflight/mach-select
/controls/autoflight/vertical-mode
/controls/autoflight/lateral-mode
</pre>
TODO - section notes

=== Electric ===
TODO - explain of section
<pre>
/controls/electric/battery-switch
/controls/electric/external-power
/controls/electric/APU-generator
/controls/electric/engine[%d]/generator
/controls/electric/engine[%d]/bus-tie
</pre>
TODO - section notes

=== Engines ===
Engines are numbered engine[0] for a single engine to engine[0] to engine[3] for a 747 for example. (The model allows for up to 12 engines rumour has it ;-)

<pre>
/controls/engines/throttle_idle
/controls/engines/engine[%d]/throttle
/controls/engines/engine[%d]/starter
/controls/engines/engine[%d]/fuel-pump
/controls/engines/engine[%d]/fire-switch
/controls/engines/engine[%d]/fire-bottle-discharge
/controls/engines/engine[%d]/cutoff
/controls/engines/engine[%d]/mixture
/controls/engines/engine[%d]/propeller-pitch
/controls/engines/engine[%d]/magnetos
/controls/engines/engine[%d]/boost
/controls/engines/engine[%d]/WEP
/controls/engines/engine[%d]/cowl-flaps-norm
/controls/engines/engine[%d]/feather
/controls/engines/engine[%d]/ignition
/controls/engines/engine[%d]/augmentation
/controls/engines/engine[%d]/afterburner
/controls/engines/engine[%d]/reverser
/controls/engines/engine[%d]/water-injection
/controls/engines/engine[%d]/condition
</pre>
TODO - section notes

=== Flight controls ===
These properties control the flight controls surfaces, though often through a mechanical, analog or digital flight control system (FCS) that may or may not be modeled.

<pre>
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/flight/flaps
/controls/flight/slats
/controls/flight/BLC // Boundary Layer Control
/controls/flight/spoilers
/controls/flight/speedbrake
/controls/flight/wing-sweep
/controls/flight/wing-fold
/controls/flight/drag-chute
</pre>

The positions of the controls are usually put in <code>/surface-positions/</code> at the discretion of the aircraft designer. These usually drive the animations of the control surfaces. They are either normalized (like <code>/surface-positions/elevator-pos-norm</code>) or in degrees, and sometimes the aileron is split left/right.

=== Fuel ===
TODO - explain of section
<pre>
/controls/fuel/dump-valve
/controls/fuel/tank[%d]/fuel_selector
/controls/fuel/tank[%d]/to_engine
/controls/fuel/tank[%d]/to_tank
/controls/fuel/tank[%d]/boost-pump[%d]
</pre>
TODO - section notes

=== Gear ===
TODO - explain of section
<pre>
/controls/gear/brake-left
/controls/gear/brake-right
/controls/gear/brake-parking
/controls/gear/steering // Used if rudder is not sufficient for control of steering
/controls/gear/gear-down
/controls/gear/antiskid // Deprecated?
/controls/gear/tailhook
/controls/gear/tailwheel-lock
/controls/gear/wheel[%d]/alternate-extension
</pre>
TODO - section notes

=== Hydraulics ===
TODO - explain of section
<pre>
/controls/hydraulic/system[%d]/engine-pump
/controls/hydraulic/system[%d]/electric-pump
</pre>
TODO - section notes

=== Lights ===
TODO - explain of section
<pre>
/controls/lighting/landing-lights
/controls/lighting/turn-off-lights
/controls/lighting/formation-lights
/controls/lighting/taxi-light
/controls/lighting/logo-lights
/controls/lighting/nav-lights
/controls/lighting/beacon
/controls/lighting/strobe
/controls/lighting/panel-norm
/controls/lighting/instruments-norm
/controls/lighting/dome-norm
</pre>
TODO - section notes

=== Pneumatic ===
TODO - explain of section
<pre>
/controls/pneumatic/APU-bleed
/controls/pneumatic/engine[%d]/bleed
</pre>
TODO - section notes

=== Pressurization ===
TODO - explain of section
<pre>
/controls/pressurization/mode
/controls/pressurization/dump
/controls/pressurization/outflow-valve
/controls/pressurization/pack[%d]/pack-on
</pre>
TODO - section notes

=== Seat ===
TODO - explain of section
<pre>
/controls/seat/vertical-adjust
/controls/seat/fore-aft-adjust
/controls/seat/cmd_selector_valve
/controls/seat/eject[%d]/initiate
/controls/seat/eject[%d]/status
</pre>
TODO - section notes

== Engines ==
Status of engines. See also: /controls/engines/
=== Common ===
<pre>
/engines/engine[%d]/fuel-flow-gph
/engines/engine[%d]/fuel-flow_pph
/engines/engine[%d]/thrust_lb
/engines/engine[%d]/running
/engines/engine[%d]/starter
/engines/engine[%d]/cranking
/engines/engine[%d]/fire
</pre>

=== Turbine ===
<pre>
/engines/engine[%d]/n1
/engines/engine[%d]/n2
/engines/engine[%d]/epr
/engines/engine[%d]/augmentation
/engines/engine[%d]/water-injection
/engines/engine[%d]/ignition
/engines/engine[%d]/nozzle-pos-norm
/engines/engine[%d]/inlet-pos-norm
/engines/engine[%d]/reversed
/engines/engine[%d]/cutoff
</pre>

=== Piston ===
<pre>
/engines/engine[%d]/mp-osi
/engines/engine[%d]/egt-degf
/engines/engine[%d]/oil-temperature-degf
/engines/engine[%d]/oil-pressure-psi
/engines/engine[%d]/cht-degf
/engines/engine[%d]/rpm
</pre>

=== Propeller ===
<pre>
/engines/engine[%d]/rpm
/engines/engine[%d]/pitch
/engines/engine[%d]/torque
</pre>
TODO - section notes

== Flight Dynamics Model ==
=== Position ===
This will return the current position of the aircraft within FlightGear. This is also the stuff that is transmitted in [[Howto:Multiplayer|multiplayer]].

<pre>
/position/
/position/altitiude-ft ()
/position/altitude-agl-ft (22.46983965)
/position/altitude-ft (28.24368289)
/position/ground-elev-ft (-0.43513529)
/position/ground-elev-m (-0.1326292364)
/position/latitude-deg (37.61371436)
/position/latitude-string (37*36 49.4N)
/position/longitude-deg (-122.3576508)
/position/longitude-string (-122*21 27.5W)
/position/sea-level-radius-ft (20899648.76)
</pre>

=== Orientation ===
TODO - explain of section
<pre>
/orientation/roll-deg
/orientation/pitch-deg
/orientation/heading-deg

/orientation/roll-rate-degps
/orientation/pitch-rate-degps
/orientation/yaw-rate-degps

/orientation/side-slip-rad
/orientation/side-slip-deg
/orientation/alpha-deg
</pre>
TODO - section notes

=== Velocities ===
TODO - explain of section
<pre>
/velocities/airspeed-kt
/velocities/mach
/velocities/speed-north-fps
/velocities/speed-east-fps
/velocities/speed-down-fps

/velocities/uBody-fps
/velocities/vBody-fps
/velocities/wBody-fps

/velocities/vertical-speed-fps
/velocities/glideslope
</pre>
TODO - section notes

=== Acceleration ===
TODO - explain of section
<pre>
/accelerations/nlf

/accelerations/ned/north-accel-fps_sec
/accelerations/ned/east-accel-fps_sec
/accelerations/ned/down-accel-fps_sec

/accelerations/pilot/x-accel-fps_sec
/accelerations/pilot/y-accel-fps_sec
/accelerations/pilot/z-accel-fps_sec
</pre>
TODO - section notes

== Gear ==
<pre>
/gear/serviceable
/gear/gear[%d]/cast-angle-deg // The angle of the wheel where 0 is pointing straight forward
/gear/gear[%d]/compression-m
/gear/gear[%d]/compression-norm
/gear/gear[%d]/ground-friction-factor
/gear/gear[%d]/ground-is-solid
/gear/gear[%d]/has-brake
/gear/gear[%d]/rollspeed-ms // Speed of the wheel's rotation in meters per second
/gear/gear[%d]/wow // Weight-on-wheel
/gear/gear[%d]/xoffset-in
/gear/gear[%d]/yoffset-in
/gear/gear[%d]/zoffset-in
</pre>

== Instrumentation ==
<pre>
/instrumentation/adf/
/instrumentation/airspeed-indicator/
/instrumentation/altimeter/
/instrumentation/annunciator/
/instrumentation/attitude-indicator/
/instrumentation/clock/
/instrumentation/comm[%d]/
/instrumentation/dme/
/instrumentation/efis/
/instrumentation/encoder/
/instrumentation/flightdirector/
/instrumentation/gps/
/instrumentation/gps-annunciator/
/instrumentation/heading-indicator/
/instrumentation/heading-indicator-fg/
/instrumentation/magnetic-compass/
/instrumentation/marker-beacon/
/instrumentation/nav[%d]/
/instrumentation/radar/
/instrumentation/slip-skid-ball/
/instrumentation/tacan[%d]/
/instrumentation/transponder/
/instrumentation/turn-indicator/
/instrumentation/vertical-speed-indicator/
/instrumentation/wxradar/
</pre>

=== Instrumentation comm radio ===

<pre>
/instrumentation/comm[%d]/add-noise
/instrumentation/comm[%d]/airport-id
/instrumentation/comm[%d]/atis
/instrumentation/comm[%d]/channel-button
/instrumentation/comm[%d]/chanel-mode-selector
/instrumentation/comm[%d]/cutoff-signal-quality
/instrumentation/comm[%d]/frequencies
/instrumentation/comm[%d]/frequencies/dial-khz
/instrumentation/comm[%d]/frequencies/dial-mhz
/instrumentation/comm[%d]/frequencies/selected-channel
/instrumentation/comm[%d]/frequencies/selected-channel-width-khz
/instrumentation/comm[%d]/frequencies/selected-mhz
/instrumentation/comm[%d]/frequencies/selected-mhz-fmt
/instrumentation/comm[%d]/frequencies/selected-real-frequency-mhz
/instrumentation/comm[%d]/frequencies/standby-channel
/instrumentation/comm[%d]/frequencies/standby-channel-width-khz
/instrumentation/comm[%d]/frequencies/standby-mhz
/instrumentation/comm[%d]/frequencies/standby-mhz-fmt
/instrumentation/comm[%d]/frequencies/standby-real-frequency-mhz
/instrumentation/comm[%d]/frq-swap-btn
/instrumentation/comm[%d]/height-above-station-ft
/instrumentation/comm[%d]/operable
/instrumentation/comm[%d]/power-btn
/instrumentation/comm[%d]/ptt
/instrumentation/comm[%d]/servicable
/instrumentation/comm[%d]/signal-quality-norm
/instrumentation/comm[%d]/slant-distance-m
/instrumentation/comm[%d]/station-name
/instrumentation/comm[%d]/station-type
/instrumentation/comm[%d]/test-btn
/instrumentation/comm[%d]/track-distance-m
/instrumentation/comm[%d]/true-bearing-from-deg
/instrumentation/comm[%d]/true-bearing-to-deg
/instrumentation/comm[%d]/volume
/instrumentation/comm[%d]/volume-selected
</pre>

=== Instrumentation Tacan ===
<pre>
/instrumentation/tacan[%d]/display/channel
/instrumentation/tacan[%d]/display/x-shift
/instrumentation/tacan[%d]/display/y-shift
/instrumentation/tacan[%d]/frequencies/selected-channel
/instrumentation/tacan[%d]/frequencies/selected-channel[1]
/instrumentation/tacan[%d]/frequencies/selected-channel[2]
/instrumentation/tacan[%d]/frequencies/selected-channel[3]
/instrumentation/tacan[%d]/frequencies/selected-channel[4]
/instrumentation/tacan[%d]/frequencies/selected-mhz
/instrumentation/tacan[%d]/ident
/instrumentation/tacan[%d]/in-range
/instrumentation/tacan[%d]/indicated-bearing-true-deg
/instrumentation/tacan[%d]/indicated-distance-nm
/instrumentation/tacan[%d]/indicated-ground-speed-kt
/instrumentation/tacan[%d]/indicated-time-min
/instrumentation/tacan[%d]/name
/instrumentation/tacan[%d]/serviceable
/instrumentation/tacan[%d]/switch-position
</pre>

== Rotors (YASim only) ==
<pre>
/rotors/gear/torque-sound-filtered // Unused?
/rotors/gear/total-torque
/rotors/{name}/balance
/rotors/{name}/blade[%d]/flap-deg
/rotors/{name}/blade[%d]/incidence-deg
/rotors/{name}/blade[%d]/position-deg // Position relative to model
/rotors/{name}/bladesvisible // Used for animations
/rotors/{name}/cone%d-deg //e.g. cone-deg or cone2-deg
/rotors/{name}/roll-deg
/rotors/{name}/rpm
/rotors/{name}/stall
/rotors/{name}/stall-filtered
/rotors/{name}/tilt
/rotors/{name}/torque
/rotors/{name}/yaw-deg
</pre>

For how to animate rotors using these properties, see [[Howto:Animate helicopters]].

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Multiplayer protocol]]
* [[Property browser]]
* [[PropertyList XML files]]
* [[Property tree]]

=== Readme files ===
* {{readme file|properties}}

=== Source code ===
==== Consumables ====
* {{flightgear file|src/FDM/TankProperties.hxx}}
* {{flightgear file|src/FDM/TankProperties.cxx}}

==== Controls ====
* {{flightgear file|src/Aircraft/controls.hxx}}
* {{flightgear file|src/Aircraft/controls.cxx}}

==== Flight Dynamics Model ====
* {{flightgear file|src/FDM/flightProperties.hxx}}
* {{flightgear file|src/FDM/flightProperties.cxx}}

==== Instrumentation ====
* {{flightgear file|src/Instrumentation}}

[[Category:Property Tree]]
[[Category:Aircraft enhancement]]

Aircraft properties reference

2024-04-12T02:09:43Z

Www2: /* Instrumentation */ small remove duplicate enterys and replace with /entery/name[%d]/ as the format

{{PropertyTree}}

This is a generic '''aircraft properties reference'''. There are many properties that are very common in aircraft, and many of them are present even in a very simple aircraft. However, a complete description that matches all the properties is very unlikely to be written, as aircraft can be very different from each other.

{{TOC limit|2}}

== What are properties? ==
{{main article|Property tree}}
=== The property tree ===
Most parts of FlightGear communicate with each other through key-value pair properties in the [[property tree]]. The properties represent both the input from the pilot, the values determining the position and velocity of the aircraft, the values used for animating the aircraft, and pretty much anything else.

While many properties will be common between most aircraft, many properties will also be different between aircraft. This becomes obvious if one consider the many different configurations (aircraft/helicopter/car, control surface and landing gear layout, number and locations of engines, etc) and propulsions systems (types of engines, types of fuels etc.) an aircraft can have. There are also different flight dynamic models (FDMs) that have different needs. In addition many properties will by necessity be aircraft specific, though developers should make a conscious effort to have properties map to more common ones if that is possible.

=== Where are the properties defined? ===
There are a couple ways that the properties are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties. One is in the aircraft files, starting from the aircraft specific [[aircraft-set.xml]] file, another is the [[Nasal]] files, and the last place (and often most useful!) is "grepping" (searching) through the C++ code.

To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better

== Annunciators [draft] ==
!! This section is work in progress !!

The /instrumentation/annunciators section shall provide a central place for

* aircrafts to write annunciator status data
* 3D aircraft models and external devices (like joysticks, yokes, throttle quadrants or custom made cockpit hardware) to read such data and drive status lights etc.

Some of the props are automatically calculated by property rules in $FGDATA/Aircraft/Generic/generic-annunciators.xml other properties have to be calculated by the actual aircraft.

The aircraft.nas module provides aircraft.light which allows easy implementation of blinking lights. Such lights have a bool property 'state' which tells if the light is on or off.<pre>
/instrumentation/annunciators/doors
/instrumentation/annunciators/master-caution/state # aircraft.light
/instrumentation/annunciators/master-warning/state # aircraft.light

/instrumentation/annunciators/ap/enabled
/instrumentation/annunciators/ap/mode/alt
/instrumentation/annunciators/ap/mode/apr
/instrumentation/annunciators/ap/mode/hdg
/instrumentation/annunciators/ap/mode/ias
/instrumentation/annunciators/ap/mode/nav
/instrumentation/annunciators/ap/mode/rev
/instrumentation/annunciators/ap/mode/vs

/instrumentation/annunciators/engines/
/instrumentation/annunciators/engines/apu
/instrumentation/annunciators/engines/fire
/instrumentation/annunciators/engines/oil-pressure-low
/instrumentation/annunciators/engines/starter
# for <gear-name> in {nose, left, right}
/instrumentation/annunciators/gear/<gear-name>/down
/instrumentation/annunciators/gear/<gear-name>/in-transition
/instrumentation/annunciators/gear/<gear-name>/unsafe
/instrumentation/annunciators/gear/<gear-name>/up

/instrumentation/annunciators/gear/parking-brake

/instrumentation/annunciators/systems/anti-ice/enabled
/instrumentation/annunciators/systems/fuel/aux-pump
/instrumentation/annunciators/systems/fuel/pressure-low
/instrumentation/annunciators/systems/hyd/pressure-low
/instrumentation/annunciators/systems/vacuum

</pre>

== Consumables ==
:''See also [[#Fuel]]
<pre>
/consumables/fuel/tank[%d]/level-lb
/consumables/fuel/tank[%d]/level-lbs
/consumables/fuel/tank[%d]/level-gal_us
/consumables/fuel/tank[%d]/capacity-gal_us
/consumables/fuel/tank[%d]/density-ppg
/consumables/fuel/total-fuel-lbs
/consumables/fuel/total-gal_us
</pre>

== Controls ==
These properties should, and usually do correspond to how various cockpit controls are set. Consider these the pilot input.

=== Anti-ice ===
These properties control the various anti-ice properties that may be present in an aircraft.

<pre>
/controls/anti-ice/wing-heat
/controls/anti-ice/pitot-heat
/controls/anti-ice/wiper
/controls/anti-ice/window-heat
/controls/anti-ice/engine[%d]/carb-heat
/controls/anti-ice/engine[%d]/inlet-heat
</pre>
TODO - section notes

=== APU ===
These properties control any auxiliary power unit, in essence a small turbine engine driving generators, hydraulic pumps etc. before and after the aircraft's engines are up an running.

<pre>
/controls/APU/off-start-run
/controls/APU/fire-switch
</pre>
TODO - section notes

=== Armament ===
TODO - explain of section
<pre>
/controls/armament/master-arm
/controls/armament/station-select
/controls/armament/release-all
/controls/armament/station[%d]/stick-size
/controls/armament/station[%d]/release-stick
/controls/armament/station[%d]/release-all
/controls/armament/station[%d]/jettison-all
</pre>
TODO - section notes

=== Autoflight ===
These properties control the autopilot.

TODO - explain of section
<pre>
/controls/autoflight/autopilot[%d]/engage
/controls/autoflight/autothrottle-arm
/controls/autoflight/autothrottle-engage
/controls/autoflight/heading-select
/controls/autoflight/altitude-select
/controls/autoflight/bank-angle-select
/controls/autoflight/vertical-speed-select
/controls/autoflight/speed-select
/controls/autoflight/mach-select
/controls/autoflight/vertical-mode
/controls/autoflight/lateral-mode
</pre>
TODO - section notes

=== Electric ===
TODO - explain of section
<pre>
/controls/electric/battery-switch
/controls/electric/external-power
/controls/electric/APU-generator
/controls/electric/engine[%d]/generator
/controls/electric/engine[%d]/bus-tie
</pre>
TODO - section notes

=== Engines ===
Engines are numbered engine[0] for a single engine to engine[0] to engine[3] for a 747 for example. (The model allows for up to 12 engines rumour has it ;-)

<pre>
/controls/engines/throttle_idle
/controls/engines/engine[%d]/throttle
/controls/engines/engine[%d]/starter
/controls/engines/engine[%d]/fuel-pump
/controls/engines/engine[%d]/fire-switch
/controls/engines/engine[%d]/fire-bottle-discharge
/controls/engines/engine[%d]/cutoff
/controls/engines/engine[%d]/mixture
/controls/engines/engine[%d]/propeller-pitch
/controls/engines/engine[%d]/magnetos
/controls/engines/engine[%d]/boost
/controls/engines/engine[%d]/WEP
/controls/engines/engine[%d]/cowl-flaps-norm
/controls/engines/engine[%d]/feather
/controls/engines/engine[%d]/ignition
/controls/engines/engine[%d]/augmentation
/controls/engines/engine[%d]/afterburner
/controls/engines/engine[%d]/reverser
/controls/engines/engine[%d]/water-injection
/controls/engines/engine[%d]/condition
</pre>
TODO - section notes

=== Flight controls ===
These properties control the flight controls surfaces, though often through a mechanical, analog or digital flight control system (FCS) that may or may not be modeled.

<pre>
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/flight/flaps
/controls/flight/slats
/controls/flight/BLC // Boundary Layer Control
/controls/flight/spoilers
/controls/flight/speedbrake
/controls/flight/wing-sweep
/controls/flight/wing-fold
/controls/flight/drag-chute
</pre>

The positions of the controls are usually put in <code>/surface-positions/</code> at the discretion of the aircraft designer. These usually drive the animations of the control surfaces. They are either normalized (like <code>/surface-positions/elevator-pos-norm</code>) or in degrees, and sometimes the aileron is split left/right.

=== Fuel ===
TODO - explain of section
<pre>
/controls/fuel/dump-valve
/controls/fuel/tank[%d]/fuel_selector
/controls/fuel/tank[%d]/to_engine
/controls/fuel/tank[%d]/to_tank
/controls/fuel/tank[%d]/boost-pump[%d]
</pre>
TODO - section notes

=== Gear ===
TODO - explain of section
<pre>
/controls/gear/brake-left
/controls/gear/brake-right
/controls/gear/brake-parking
/controls/gear/steering // Used if rudder is not sufficient for control of steering
/controls/gear/gear-down
/controls/gear/antiskid // Deprecated?
/controls/gear/tailhook
/controls/gear/tailwheel-lock
/controls/gear/wheel[%d]/alternate-extension
</pre>
TODO - section notes

=== Hydraulics ===
TODO - explain of section
<pre>
/controls/hydraulic/system[%d]/engine-pump
/controls/hydraulic/system[%d]/electric-pump
</pre>
TODO - section notes

=== Lights ===
TODO - explain of section
<pre>
/controls/lighting/landing-lights
/controls/lighting/turn-off-lights
/controls/lighting/formation-lights
/controls/lighting/taxi-light
/controls/lighting/logo-lights
/controls/lighting/nav-lights
/controls/lighting/beacon
/controls/lighting/strobe
/controls/lighting/panel-norm
/controls/lighting/instruments-norm
/controls/lighting/dome-norm
</pre>
TODO - section notes

=== Pneumatic ===
TODO - explain of section
<pre>
/controls/pneumatic/APU-bleed
/controls/pneumatic/engine[%d]/bleed
</pre>
TODO - section notes

=== Pressurization ===
TODO - explain of section
<pre>
/controls/pressurization/mode
/controls/pressurization/dump
/controls/pressurization/outflow-valve
/controls/pressurization/pack[%d]/pack-on
</pre>
TODO - section notes

=== Seat ===
TODO - explain of section
<pre>
/controls/seat/vertical-adjust
/controls/seat/fore-aft-adjust
/controls/seat/cmd_selector_valve
/controls/seat/eject[%d]/initiate
/controls/seat/eject[%d]/status
</pre>
TODO - section notes

== Engines ==
Status of engines. See also: /controls/engines/
=== Common ===
<pre>
/engines/engine[%d]/fuel-flow-gph
/engines/engine[%d]/fuel-flow_pph
/engines/engine[%d]/thrust_lb
/engines/engine[%d]/running
/engines/engine[%d]/starter
/engines/engine[%d]/cranking
/engines/engine[%d]/fire
</pre>

=== Turbine ===
<pre>
/engines/engine[%d]/n1
/engines/engine[%d]/n2
/engines/engine[%d]/epr
/engines/engine[%d]/augmentation
/engines/engine[%d]/water-injection
/engines/engine[%d]/ignition
/engines/engine[%d]/nozzle-pos-norm
/engines/engine[%d]/inlet-pos-norm
/engines/engine[%d]/reversed
/engines/engine[%d]/cutoff
</pre>

=== Piston ===
<pre>
/engines/engine[%d]/mp-osi
/engines/engine[%d]/egt-degf
/engines/engine[%d]/oil-temperature-degf
/engines/engine[%d]/oil-pressure-psi
/engines/engine[%d]/cht-degf
/engines/engine[%d]/rpm
</pre>

=== Propeller ===
<pre>
/engines/engine[%d]/rpm
/engines/engine[%d]/pitch
/engines/engine[%d]/torque
</pre>
TODO - section notes

== Flight Dynamics Model ==
=== Position ===
This will return the current position of the aircraft within FlightGear. This is also the stuff that is transmitted in [[Howto:Multiplayer|multiplayer]].

<pre>
/position/
/position/altitiude-ft ()
/position/altitude-agl-ft (22.46983965)
/position/altitude-ft (28.24368289)
/position/ground-elev-ft (-0.43513529)
/position/ground-elev-m (-0.1326292364)
/position/latitude-deg (37.61371436)
/position/latitude-string (37*36 49.4N)
/position/longitude-deg (-122.3576508)
/position/longitude-string (-122*21 27.5W)
/position/sea-level-radius-ft (20899648.76)
</pre>

=== Orientation ===
TODO - explain of section
<pre>
/orientation/roll-deg
/orientation/pitch-deg
/orientation/heading-deg

/orientation/roll-rate-degps
/orientation/pitch-rate-degps
/orientation/yaw-rate-degps

/orientation/side-slip-rad
/orientation/side-slip-deg
/orientation/alpha-deg
</pre>
TODO - section notes

=== Velocities ===
TODO - explain of section
<pre>
/velocities/airspeed-kt
/velocities/mach
/velocities/speed-north-fps
/velocities/speed-east-fps
/velocities/speed-down-fps

/velocities/uBody-fps
/velocities/vBody-fps
/velocities/wBody-fps

/velocities/vertical-speed-fps
/velocities/glideslope
</pre>
TODO - section notes

=== Acceleration ===
TODO - explain of section
<pre>
/accelerations/nlf

/accelerations/ned/north-accel-fps_sec
/accelerations/ned/east-accel-fps_sec
/accelerations/ned/down-accel-fps_sec

/accelerations/pilot/x-accel-fps_sec
/accelerations/pilot/y-accel-fps_sec
/accelerations/pilot/z-accel-fps_sec
</pre>
TODO - section notes

== Gear ==
<pre>
/gear/serviceable
/gear/gear[%d]/cast-angle-deg // The angle of the wheel where 0 is pointing straight forward
/gear/gear[%d]/compression-m
/gear/gear[%d]/compression-norm
/gear/gear[%d]/ground-friction-factor
/gear/gear[%d]/ground-is-solid
/gear/gear[%d]/has-brake
/gear/gear[%d]/rollspeed-ms // Speed of the wheel's rotation in meters per second
/gear/gear[%d]/wow // Weight-on-wheel
/gear/gear[%d]/xoffset-in
/gear/gear[%d]/yoffset-in
/gear/gear[%d]/zoffset-in
</pre>

== Instrumentation ==
<pre>
/instrumentation/adf/
/instrumentation/airspeed-indicator/
/instrumentation/altimeter/
/instrumentation/annunciator/
/instrumentation/attitude-indicator/
/instrumentation/clock/
/instrumentation/comm[%d]/
/instrumentation/dme/
/instrumentation/efis/
/instrumentation/encoder/
/instrumentation/flightdirector/
/instrumentation/gps/
/instrumentation/gps-annunciator/
/instrumentation/heading-indicator/
/instrumentation/heading-indicator-fg/
/instrumentation/magnetic-compass/
/instrumentation/marker-beacon/
/instrumentation/nav[%d]/
/instrumentation/radar/
/instrumentation/slip-skid-ball/
/instrumentation/tacan/
/instrumentation/transponder/
/instrumentation/turn-indicator/
/instrumentation/vertical-speed-indicator/
/instrumentation/wxradar/
</pre>

=== Instrumentation comm radio ===

<pre>
/instrumentation/comm[%d]/add-noise
/instrumentation/comm[%d]/airport-id
/instrumentation/comm[%d]/atis
/instrumentation/comm[%d]/channel-button
/instrumentation/comm[%d]/chanel-mode-selector
/instrumentation/comm[%d]/cutoff-signal-quality
/instrumentation/comm[%d]/frequencies
/instrumentation/comm[%d]/frequencies/dial-khz
/instrumentation/comm[%d]/frequencies/dial-mhz
/instrumentation/comm[%d]/frequencies/selected-channel
/instrumentation/comm[%d]/frequencies/selected-channel-width-khz
/instrumentation/comm[%d]/frequencies/selected-mhz
/instrumentation/comm[%d]/frequencies/selected-mhz-fmt
/instrumentation/comm[%d]/frequencies/selected-real-frequency-mhz
/instrumentation/comm[%d]/frequencies/standby-channel
/instrumentation/comm[%d]/frequencies/standby-channel-width-khz
/instrumentation/comm[%d]/frequencies/standby-mhz
/instrumentation/comm[%d]/frequencies/standby-mhz-fmt
/instrumentation/comm[%d]/frequencies/standby-real-frequency-mhz
/instrumentation/comm[%d]/frq-swap-btn
/instrumentation/comm[%d]/height-above-station-ft
/instrumentation/comm[%d]/operable
/instrumentation/comm[%d]/power-btn
/instrumentation/comm[%d]/ptt
/instrumentation/comm[%d]/servicable
/instrumentation/comm[%d]/signal-quality-norm
/instrumentation/comm[%d]/slant-distance-m
/instrumentation/comm[%d]/station-name
/instrumentation/comm[%d]/station-type
/instrumentation/comm[%d]/test-btn
/instrumentation/comm[%d]/track-distance-m
/instrumentation/comm[%d]/true-bearing-from-deg
/instrumentation/comm[%d]/true-bearing-to-deg
/instrumentation/comm[%d]/volume
/instrumentation/comm[%d]/volume-selected
</pre>

== Rotors (YASim only) ==
<pre>
/rotors/gear/torque-sound-filtered // Unused?
/rotors/gear/total-torque
/rotors/{name}/balance
/rotors/{name}/blade[%d]/flap-deg
/rotors/{name}/blade[%d]/incidence-deg
/rotors/{name}/blade[%d]/position-deg // Position relative to model
/rotors/{name}/bladesvisible // Used for animations
/rotors/{name}/cone%d-deg //e.g. cone-deg or cone2-deg
/rotors/{name}/roll-deg
/rotors/{name}/rpm
/rotors/{name}/stall
/rotors/{name}/stall-filtered
/rotors/{name}/tilt
/rotors/{name}/torque
/rotors/{name}/yaw-deg
</pre>

For how to animate rotors using these properties, see [[Howto:Animate helicopters]].

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Multiplayer protocol]]
* [[Property browser]]
* [[PropertyList XML files]]
* [[Property tree]]

=== Readme files ===
* {{readme file|properties}}

=== Source code ===
==== Consumables ====
* {{flightgear file|src/FDM/TankProperties.hxx}}
* {{flightgear file|src/FDM/TankProperties.cxx}}

==== Controls ====
* {{flightgear file|src/Aircraft/controls.hxx}}
* {{flightgear file|src/Aircraft/controls.cxx}}

==== Flight Dynamics Model ====
* {{flightgear file|src/FDM/flightProperties.hxx}}
* {{flightgear file|src/FDM/flightProperties.cxx}}

==== Instrumentation ====
* {{flightgear file|src/Instrumentation}}

[[Category:Property Tree]]
[[Category:Aircraft enhancement]]

Aircraft properties reference

2024-04-12T02:07:51Z

Www2: /* Instrumentation comm radio */

{{PropertyTree}}

This is a generic '''aircraft properties reference'''. There are many properties that are very common in aircraft, and many of them are present even in a very simple aircraft. However, a complete description that matches all the properties is very unlikely to be written, as aircraft can be very different from each other.

{{TOC limit|2}}

== What are properties? ==
{{main article|Property tree}}
=== The property tree ===
Most parts of FlightGear communicate with each other through key-value pair properties in the [[property tree]]. The properties represent both the input from the pilot, the values determining the position and velocity of the aircraft, the values used for animating the aircraft, and pretty much anything else.

While many properties will be common between most aircraft, many properties will also be different between aircraft. This becomes obvious if one consider the many different configurations (aircraft/helicopter/car, control surface and landing gear layout, number and locations of engines, etc) and propulsions systems (types of engines, types of fuels etc.) an aircraft can have. There are also different flight dynamic models (FDMs) that have different needs. In addition many properties will by necessity be aircraft specific, though developers should make a conscious effort to have properties map to more common ones if that is possible.

=== Where are the properties defined? ===
There are a couple ways that the properties are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties. One is in the aircraft files, starting from the aircraft specific [[aircraft-set.xml]] file, another is the [[Nasal]] files, and the last place (and often most useful!) is "grepping" (searching) through the C++ code.

To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better

== Annunciators [draft] ==
!! This section is work in progress !!

The /instrumentation/annunciators section shall provide a central place for

* aircrafts to write annunciator status data
* 3D aircraft models and external devices (like joysticks, yokes, throttle quadrants or custom made cockpit hardware) to read such data and drive status lights etc.

Some of the props are automatically calculated by property rules in $FGDATA/Aircraft/Generic/generic-annunciators.xml other properties have to be calculated by the actual aircraft.

The aircraft.nas module provides aircraft.light which allows easy implementation of blinking lights. Such lights have a bool property 'state' which tells if the light is on or off.<pre>
/instrumentation/annunciators/doors
/instrumentation/annunciators/master-caution/state # aircraft.light
/instrumentation/annunciators/master-warning/state # aircraft.light

/instrumentation/annunciators/ap/enabled
/instrumentation/annunciators/ap/mode/alt
/instrumentation/annunciators/ap/mode/apr
/instrumentation/annunciators/ap/mode/hdg
/instrumentation/annunciators/ap/mode/ias
/instrumentation/annunciators/ap/mode/nav
/instrumentation/annunciators/ap/mode/rev
/instrumentation/annunciators/ap/mode/vs

/instrumentation/annunciators/engines/
/instrumentation/annunciators/engines/apu
/instrumentation/annunciators/engines/fire
/instrumentation/annunciators/engines/oil-pressure-low
/instrumentation/annunciators/engines/starter
# for <gear-name> in {nose, left, right}
/instrumentation/annunciators/gear/<gear-name>/down
/instrumentation/annunciators/gear/<gear-name>/in-transition
/instrumentation/annunciators/gear/<gear-name>/unsafe
/instrumentation/annunciators/gear/<gear-name>/up

/instrumentation/annunciators/gear/parking-brake

/instrumentation/annunciators/systems/anti-ice/enabled
/instrumentation/annunciators/systems/fuel/aux-pump
/instrumentation/annunciators/systems/fuel/pressure-low
/instrumentation/annunciators/systems/hyd/pressure-low
/instrumentation/annunciators/systems/vacuum

</pre>

== Consumables ==
:''See also [[#Fuel]]
<pre>
/consumables/fuel/tank[%d]/level-lb
/consumables/fuel/tank[%d]/level-lbs
/consumables/fuel/tank[%d]/level-gal_us
/consumables/fuel/tank[%d]/capacity-gal_us
/consumables/fuel/tank[%d]/density-ppg
/consumables/fuel/total-fuel-lbs
/consumables/fuel/total-gal_us
</pre>

== Controls ==
These properties should, and usually do correspond to how various cockpit controls are set. Consider these the pilot input.

=== Anti-ice ===
These properties control the various anti-ice properties that may be present in an aircraft.

<pre>
/controls/anti-ice/wing-heat
/controls/anti-ice/pitot-heat
/controls/anti-ice/wiper
/controls/anti-ice/window-heat
/controls/anti-ice/engine[%d]/carb-heat
/controls/anti-ice/engine[%d]/inlet-heat
</pre>
TODO - section notes

=== APU ===
These properties control any auxiliary power unit, in essence a small turbine engine driving generators, hydraulic pumps etc. before and after the aircraft's engines are up an running.

<pre>
/controls/APU/off-start-run
/controls/APU/fire-switch
</pre>
TODO - section notes

=== Armament ===
TODO - explain of section
<pre>
/controls/armament/master-arm
/controls/armament/station-select
/controls/armament/release-all
/controls/armament/station[%d]/stick-size
/controls/armament/station[%d]/release-stick
/controls/armament/station[%d]/release-all
/controls/armament/station[%d]/jettison-all
</pre>
TODO - section notes

=== Autoflight ===
These properties control the autopilot.

TODO - explain of section
<pre>
/controls/autoflight/autopilot[%d]/engage
/controls/autoflight/autothrottle-arm
/controls/autoflight/autothrottle-engage
/controls/autoflight/heading-select
/controls/autoflight/altitude-select
/controls/autoflight/bank-angle-select
/controls/autoflight/vertical-speed-select
/controls/autoflight/speed-select
/controls/autoflight/mach-select
/controls/autoflight/vertical-mode
/controls/autoflight/lateral-mode
</pre>
TODO - section notes

=== Electric ===
TODO - explain of section
<pre>
/controls/electric/battery-switch
/controls/electric/external-power
/controls/electric/APU-generator
/controls/electric/engine[%d]/generator
/controls/electric/engine[%d]/bus-tie
</pre>
TODO - section notes

=== Engines ===
Engines are numbered engine[0] for a single engine to engine[0] to engine[3] for a 747 for example. (The model allows for up to 12 engines rumour has it ;-)

<pre>
/controls/engines/throttle_idle
/controls/engines/engine[%d]/throttle
/controls/engines/engine[%d]/starter
/controls/engines/engine[%d]/fuel-pump
/controls/engines/engine[%d]/fire-switch
/controls/engines/engine[%d]/fire-bottle-discharge
/controls/engines/engine[%d]/cutoff
/controls/engines/engine[%d]/mixture
/controls/engines/engine[%d]/propeller-pitch
/controls/engines/engine[%d]/magnetos
/controls/engines/engine[%d]/boost
/controls/engines/engine[%d]/WEP
/controls/engines/engine[%d]/cowl-flaps-norm
/controls/engines/engine[%d]/feather
/controls/engines/engine[%d]/ignition
/controls/engines/engine[%d]/augmentation
/controls/engines/engine[%d]/afterburner
/controls/engines/engine[%d]/reverser
/controls/engines/engine[%d]/water-injection
/controls/engines/engine[%d]/condition
</pre>
TODO - section notes

=== Flight controls ===
These properties control the flight controls surfaces, though often through a mechanical, analog or digital flight control system (FCS) that may or may not be modeled.

<pre>
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/flight/flaps
/controls/flight/slats
/controls/flight/BLC // Boundary Layer Control
/controls/flight/spoilers
/controls/flight/speedbrake
/controls/flight/wing-sweep
/controls/flight/wing-fold
/controls/flight/drag-chute
</pre>

The positions of the controls are usually put in <code>/surface-positions/</code> at the discretion of the aircraft designer. These usually drive the animations of the control surfaces. They are either normalized (like <code>/surface-positions/elevator-pos-norm</code>) or in degrees, and sometimes the aileron is split left/right.

=== Fuel ===
TODO - explain of section
<pre>
/controls/fuel/dump-valve
/controls/fuel/tank[%d]/fuel_selector
/controls/fuel/tank[%d]/to_engine
/controls/fuel/tank[%d]/to_tank
/controls/fuel/tank[%d]/boost-pump[%d]
</pre>
TODO - section notes

=== Gear ===
TODO - explain of section
<pre>
/controls/gear/brake-left
/controls/gear/brake-right
/controls/gear/brake-parking
/controls/gear/steering // Used if rudder is not sufficient for control of steering
/controls/gear/gear-down
/controls/gear/antiskid // Deprecated?
/controls/gear/tailhook
/controls/gear/tailwheel-lock
/controls/gear/wheel[%d]/alternate-extension
</pre>
TODO - section notes

=== Hydraulics ===
TODO - explain of section
<pre>
/controls/hydraulic/system[%d]/engine-pump
/controls/hydraulic/system[%d]/electric-pump
</pre>
TODO - section notes

=== Lights ===
TODO - explain of section
<pre>
/controls/lighting/landing-lights
/controls/lighting/turn-off-lights
/controls/lighting/formation-lights
/controls/lighting/taxi-light
/controls/lighting/logo-lights
/controls/lighting/nav-lights
/controls/lighting/beacon
/controls/lighting/strobe
/controls/lighting/panel-norm
/controls/lighting/instruments-norm
/controls/lighting/dome-norm
</pre>
TODO - section notes

=== Pneumatic ===
TODO - explain of section
<pre>
/controls/pneumatic/APU-bleed
/controls/pneumatic/engine[%d]/bleed
</pre>
TODO - section notes

=== Pressurization ===
TODO - explain of section
<pre>
/controls/pressurization/mode
/controls/pressurization/dump
/controls/pressurization/outflow-valve
/controls/pressurization/pack[%d]/pack-on
</pre>
TODO - section notes

=== Seat ===
TODO - explain of section
<pre>
/controls/seat/vertical-adjust
/controls/seat/fore-aft-adjust
/controls/seat/cmd_selector_valve
/controls/seat/eject[%d]/initiate
/controls/seat/eject[%d]/status
</pre>
TODO - section notes

== Engines ==
Status of engines. See also: /controls/engines/
=== Common ===
<pre>
/engines/engine[%d]/fuel-flow-gph
/engines/engine[%d]/fuel-flow_pph
/engines/engine[%d]/thrust_lb
/engines/engine[%d]/running
/engines/engine[%d]/starter
/engines/engine[%d]/cranking
/engines/engine[%d]/fire
</pre>

=== Turbine ===
<pre>
/engines/engine[%d]/n1
/engines/engine[%d]/n2
/engines/engine[%d]/epr
/engines/engine[%d]/augmentation
/engines/engine[%d]/water-injection
/engines/engine[%d]/ignition
/engines/engine[%d]/nozzle-pos-norm
/engines/engine[%d]/inlet-pos-norm
/engines/engine[%d]/reversed
/engines/engine[%d]/cutoff
</pre>

=== Piston ===
<pre>
/engines/engine[%d]/mp-osi
/engines/engine[%d]/egt-degf
/engines/engine[%d]/oil-temperature-degf
/engines/engine[%d]/oil-pressure-psi
/engines/engine[%d]/cht-degf
/engines/engine[%d]/rpm
</pre>

=== Propeller ===
<pre>
/engines/engine[%d]/rpm
/engines/engine[%d]/pitch
/engines/engine[%d]/torque
</pre>
TODO - section notes

== Flight Dynamics Model ==
=== Position ===
This will return the current position of the aircraft within FlightGear. This is also the stuff that is transmitted in [[Howto:Multiplayer|multiplayer]].

<pre>
/position/
/position/altitiude-ft ()
/position/altitude-agl-ft (22.46983965)
/position/altitude-ft (28.24368289)
/position/ground-elev-ft (-0.43513529)
/position/ground-elev-m (-0.1326292364)
/position/latitude-deg (37.61371436)
/position/latitude-string (37*36 49.4N)
/position/longitude-deg (-122.3576508)
/position/longitude-string (-122*21 27.5W)
/position/sea-level-radius-ft (20899648.76)
</pre>

=== Orientation ===
TODO - explain of section
<pre>
/orientation/roll-deg
/orientation/pitch-deg
/orientation/heading-deg

/orientation/roll-rate-degps
/orientation/pitch-rate-degps
/orientation/yaw-rate-degps

/orientation/side-slip-rad
/orientation/side-slip-deg
/orientation/alpha-deg
</pre>
TODO - section notes

=== Velocities ===
TODO - explain of section
<pre>
/velocities/airspeed-kt
/velocities/mach
/velocities/speed-north-fps
/velocities/speed-east-fps
/velocities/speed-down-fps

/velocities/uBody-fps
/velocities/vBody-fps
/velocities/wBody-fps

/velocities/vertical-speed-fps
/velocities/glideslope
</pre>
TODO - section notes

=== Acceleration ===
TODO - explain of section
<pre>
/accelerations/nlf

/accelerations/ned/north-accel-fps_sec
/accelerations/ned/east-accel-fps_sec
/accelerations/ned/down-accel-fps_sec

/accelerations/pilot/x-accel-fps_sec
/accelerations/pilot/y-accel-fps_sec
/accelerations/pilot/z-accel-fps_sec
</pre>
TODO - section notes

== Gear ==
<pre>
/gear/serviceable
/gear/gear[%d]/cast-angle-deg // The angle of the wheel where 0 is pointing straight forward
/gear/gear[%d]/compression-m
/gear/gear[%d]/compression-norm
/gear/gear[%d]/ground-friction-factor
/gear/gear[%d]/ground-is-solid
/gear/gear[%d]/has-brake
/gear/gear[%d]/rollspeed-ms // Speed of the wheel's rotation in meters per second
/gear/gear[%d]/wow // Weight-on-wheel
/gear/gear[%d]/xoffset-in
/gear/gear[%d]/yoffset-in
/gear/gear[%d]/zoffset-in
</pre>

== Instrumentation ==
<pre>
/instrumentation/adf/
/instrumentation/airspeed-indicator/
/instrumentation/altimeter/
/instrumentation/annunciator/
/instrumentation/attitude-indicator/
/instrumentation/clock/
/instrumentation/comm/
/instrumentation/comm[1]/
/instrumentation/dme/
/instrumentation/efis/
/instrumentation/encoder/
/instrumentation/flightdirector/
/instrumentation/gps/
/instrumentation/gps-annunciator/
/instrumentation/heading-indicator/
/instrumentation/heading-indicator-fg/
/instrumentation/magnetic-compass/
/instrumentation/marker-beacon/
/instrumentation/nav/
/instrumentation/nav[1]/
/instrumentation/radar/
/instrumentation/slip-skid-ball/
/instrumentation/tacan/
/instrumentation/transponder/
/instrumentation/turn-indicator/
/instrumentation/vertical-speed-indicator/
/instrumentation/wxradar/
</pre>

=== Instrumentation comm radio ===

<pre>
/instrumentation/comm[%d]/add-noise
/instrumentation/comm[%d]/airport-id
/instrumentation/comm[%d]/atis
/instrumentation/comm[%d]/channel-button
/instrumentation/comm[%d]/chanel-mode-selector
/instrumentation/comm[%d]/cutoff-signal-quality
/instrumentation/comm[%d]/frequencies
/instrumentation/comm[%d]/frequencies/dial-khz
/instrumentation/comm[%d]/frequencies/dial-mhz
/instrumentation/comm[%d]/frequencies/selected-channel
/instrumentation/comm[%d]/frequencies/selected-channel-width-khz
/instrumentation/comm[%d]/frequencies/selected-mhz
/instrumentation/comm[%d]/frequencies/selected-mhz-fmt
/instrumentation/comm[%d]/frequencies/selected-real-frequency-mhz
/instrumentation/comm[%d]/frequencies/standby-channel
/instrumentation/comm[%d]/frequencies/standby-channel-width-khz
/instrumentation/comm[%d]/frequencies/standby-mhz
/instrumentation/comm[%d]/frequencies/standby-mhz-fmt
/instrumentation/comm[%d]/frequencies/standby-real-frequency-mhz
/instrumentation/comm[%d]/frq-swap-btn
/instrumentation/comm[%d]/height-above-station-ft
/instrumentation/comm[%d]/operable
/instrumentation/comm[%d]/power-btn
/instrumentation/comm[%d]/ptt
/instrumentation/comm[%d]/servicable
/instrumentation/comm[%d]/signal-quality-norm
/instrumentation/comm[%d]/slant-distance-m
/instrumentation/comm[%d]/station-name
/instrumentation/comm[%d]/station-type
/instrumentation/comm[%d]/test-btn
/instrumentation/comm[%d]/track-distance-m
/instrumentation/comm[%d]/true-bearing-from-deg
/instrumentation/comm[%d]/true-bearing-to-deg
/instrumentation/comm[%d]/volume
/instrumentation/comm[%d]/volume-selected
</pre>

== Rotors (YASim only) ==
<pre>
/rotors/gear/torque-sound-filtered // Unused?
/rotors/gear/total-torque
/rotors/{name}/balance
/rotors/{name}/blade[%d]/flap-deg
/rotors/{name}/blade[%d]/incidence-deg
/rotors/{name}/blade[%d]/position-deg // Position relative to model
/rotors/{name}/bladesvisible // Used for animations
/rotors/{name}/cone%d-deg //e.g. cone-deg or cone2-deg
/rotors/{name}/roll-deg
/rotors/{name}/rpm
/rotors/{name}/stall
/rotors/{name}/stall-filtered
/rotors/{name}/tilt
/rotors/{name}/torque
/rotors/{name}/yaw-deg
</pre>

For how to animate rotors using these properties, see [[Howto:Animate helicopters]].

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Multiplayer protocol]]
* [[Property browser]]
* [[PropertyList XML files]]
* [[Property tree]]

=== Readme files ===
* {{readme file|properties}}

=== Source code ===
==== Consumables ====
* {{flightgear file|src/FDM/TankProperties.hxx}}
* {{flightgear file|src/FDM/TankProperties.cxx}}

==== Controls ====
* {{flightgear file|src/Aircraft/controls.hxx}}
* {{flightgear file|src/Aircraft/controls.cxx}}

==== Flight Dynamics Model ====
* {{flightgear file|src/FDM/flightProperties.hxx}}
* {{flightgear file|src/FDM/flightProperties.cxx}}

==== Instrumentation ====
* {{flightgear file|src/Instrumentation}}

[[Category:Property Tree]]
[[Category:Aircraft enhancement]]

Aircraft properties reference

2024-04-11T20:03:03Z

Www2: /* Instrumentation */ add properties reference for comm radio

{{PropertyTree}}

This is a generic '''aircraft properties reference'''. There are many properties that are very common in aircraft, and many of them are present even in a very simple aircraft. However, a complete description that matches all the properties is very unlikely to be written, as aircraft can be very different from each other.

{{TOC limit|2}}

== What are properties? ==
{{main article|Property tree}}
=== The property tree ===
Most parts of FlightGear communicate with each other through key-value pair properties in the [[property tree]]. The properties represent both the input from the pilot, the values determining the position and velocity of the aircraft, the values used for animating the aircraft, and pretty much anything else.

While many properties will be common between most aircraft, many properties will also be different between aircraft. This becomes obvious if one consider the many different configurations (aircraft/helicopter/car, control surface and landing gear layout, number and locations of engines, etc) and propulsions systems (types of engines, types of fuels etc.) an aircraft can have. There are also different flight dynamic models (FDMs) that have different needs. In addition many properties will by necessity be aircraft specific, though developers should make a conscious effort to have properties map to more common ones if that is possible.

=== Where are the properties defined? ===
There are a couple ways that the properties are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties. One is in the aircraft files, starting from the aircraft specific [[aircraft-set.xml]] file, another is the [[Nasal]] files, and the last place (and often most useful!) is "grepping" (searching) through the C++ code.

To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better

== Annunciators [draft] ==
!! This section is work in progress !!

The /instrumentation/annunciators section shall provide a central place for

* aircrafts to write annunciator status data
* 3D aircraft models and external devices (like joysticks, yokes, throttle quadrants or custom made cockpit hardware) to read such data and drive status lights etc.

Some of the props are automatically calculated by property rules in $FGDATA/Aircraft/Generic/generic-annunciators.xml other properties have to be calculated by the actual aircraft.

The aircraft.nas module provides aircraft.light which allows easy implementation of blinking lights. Such lights have a bool property 'state' which tells if the light is on or off.<pre>
/instrumentation/annunciators/doors
/instrumentation/annunciators/master-caution/state # aircraft.light
/instrumentation/annunciators/master-warning/state # aircraft.light

/instrumentation/annunciators/ap/enabled
/instrumentation/annunciators/ap/mode/alt
/instrumentation/annunciators/ap/mode/apr
/instrumentation/annunciators/ap/mode/hdg
/instrumentation/annunciators/ap/mode/ias
/instrumentation/annunciators/ap/mode/nav
/instrumentation/annunciators/ap/mode/rev
/instrumentation/annunciators/ap/mode/vs

/instrumentation/annunciators/engines/
/instrumentation/annunciators/engines/apu
/instrumentation/annunciators/engines/fire
/instrumentation/annunciators/engines/oil-pressure-low
/instrumentation/annunciators/engines/starter
# for <gear-name> in {nose, left, right}
/instrumentation/annunciators/gear/<gear-name>/down
/instrumentation/annunciators/gear/<gear-name>/in-transition
/instrumentation/annunciators/gear/<gear-name>/unsafe
/instrumentation/annunciators/gear/<gear-name>/up

/instrumentation/annunciators/gear/parking-brake

/instrumentation/annunciators/systems/anti-ice/enabled
/instrumentation/annunciators/systems/fuel/aux-pump
/instrumentation/annunciators/systems/fuel/pressure-low
/instrumentation/annunciators/systems/hyd/pressure-low
/instrumentation/annunciators/systems/vacuum

</pre>

== Consumables ==
:''See also [[#Fuel]]
<pre>
/consumables/fuel/tank[%d]/level-lb
/consumables/fuel/tank[%d]/level-lbs
/consumables/fuel/tank[%d]/level-gal_us
/consumables/fuel/tank[%d]/capacity-gal_us
/consumables/fuel/tank[%d]/density-ppg
/consumables/fuel/total-fuel-lbs
/consumables/fuel/total-gal_us
</pre>

== Controls ==
These properties should, and usually do correspond to how various cockpit controls are set. Consider these the pilot input.

=== Anti-ice ===
These properties control the various anti-ice properties that may be present in an aircraft.

<pre>
/controls/anti-ice/wing-heat
/controls/anti-ice/pitot-heat
/controls/anti-ice/wiper
/controls/anti-ice/window-heat
/controls/anti-ice/engine[%d]/carb-heat
/controls/anti-ice/engine[%d]/inlet-heat
</pre>
TODO - section notes

=== APU ===
These properties control any auxiliary power unit, in essence a small turbine engine driving generators, hydraulic pumps etc. before and after the aircraft's engines are up an running.

<pre>
/controls/APU/off-start-run
/controls/APU/fire-switch
</pre>
TODO - section notes

=== Armament ===
TODO - explain of section
<pre>
/controls/armament/master-arm
/controls/armament/station-select
/controls/armament/release-all
/controls/armament/station[%d]/stick-size
/controls/armament/station[%d]/release-stick
/controls/armament/station[%d]/release-all
/controls/armament/station[%d]/jettison-all
</pre>
TODO - section notes

=== Autoflight ===
These properties control the autopilot.

TODO - explain of section
<pre>
/controls/autoflight/autopilot[%d]/engage
/controls/autoflight/autothrottle-arm
/controls/autoflight/autothrottle-engage
/controls/autoflight/heading-select
/controls/autoflight/altitude-select
/controls/autoflight/bank-angle-select
/controls/autoflight/vertical-speed-select
/controls/autoflight/speed-select
/controls/autoflight/mach-select
/controls/autoflight/vertical-mode
/controls/autoflight/lateral-mode
</pre>
TODO - section notes

=== Electric ===
TODO - explain of section
<pre>
/controls/electric/battery-switch
/controls/electric/external-power
/controls/electric/APU-generator
/controls/electric/engine[%d]/generator
/controls/electric/engine[%d]/bus-tie
</pre>
TODO - section notes

=== Engines ===
Engines are numbered engine[0] for a single engine to engine[0] to engine[3] for a 747 for example. (The model allows for up to 12 engines rumour has it ;-)

<pre>
/controls/engines/throttle_idle
/controls/engines/engine[%d]/throttle
/controls/engines/engine[%d]/starter
/controls/engines/engine[%d]/fuel-pump
/controls/engines/engine[%d]/fire-switch
/controls/engines/engine[%d]/fire-bottle-discharge
/controls/engines/engine[%d]/cutoff
/controls/engines/engine[%d]/mixture
/controls/engines/engine[%d]/propeller-pitch
/controls/engines/engine[%d]/magnetos
/controls/engines/engine[%d]/boost
/controls/engines/engine[%d]/WEP
/controls/engines/engine[%d]/cowl-flaps-norm
/controls/engines/engine[%d]/feather
/controls/engines/engine[%d]/ignition
/controls/engines/engine[%d]/augmentation
/controls/engines/engine[%d]/afterburner
/controls/engines/engine[%d]/reverser
/controls/engines/engine[%d]/water-injection
/controls/engines/engine[%d]/condition
</pre>
TODO - section notes

=== Flight controls ===
These properties control the flight controls surfaces, though often through a mechanical, analog or digital flight control system (FCS) that may or may not be modeled.

<pre>
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/flight/flaps
/controls/flight/slats
/controls/flight/BLC // Boundary Layer Control
/controls/flight/spoilers
/controls/flight/speedbrake
/controls/flight/wing-sweep
/controls/flight/wing-fold
/controls/flight/drag-chute
</pre>

The positions of the controls are usually put in <code>/surface-positions/</code> at the discretion of the aircraft designer. These usually drive the animations of the control surfaces. They are either normalized (like <code>/surface-positions/elevator-pos-norm</code>) or in degrees, and sometimes the aileron is split left/right.

=== Fuel ===
TODO - explain of section
<pre>
/controls/fuel/dump-valve
/controls/fuel/tank[%d]/fuel_selector
/controls/fuel/tank[%d]/to_engine
/controls/fuel/tank[%d]/to_tank
/controls/fuel/tank[%d]/boost-pump[%d]
</pre>
TODO - section notes

=== Gear ===
TODO - explain of section
<pre>
/controls/gear/brake-left
/controls/gear/brake-right
/controls/gear/brake-parking
/controls/gear/steering // Used if rudder is not sufficient for control of steering
/controls/gear/gear-down
/controls/gear/antiskid // Deprecated?
/controls/gear/tailhook
/controls/gear/tailwheel-lock
/controls/gear/wheel[%d]/alternate-extension
</pre>
TODO - section notes

=== Hydraulics ===
TODO - explain of section
<pre>
/controls/hydraulic/system[%d]/engine-pump
/controls/hydraulic/system[%d]/electric-pump
</pre>
TODO - section notes

=== Lights ===
TODO - explain of section
<pre>
/controls/lighting/landing-lights
/controls/lighting/turn-off-lights
/controls/lighting/formation-lights
/controls/lighting/taxi-light
/controls/lighting/logo-lights
/controls/lighting/nav-lights
/controls/lighting/beacon
/controls/lighting/strobe
/controls/lighting/panel-norm
/controls/lighting/instruments-norm
/controls/lighting/dome-norm
</pre>
TODO - section notes

=== Pneumatic ===
TODO - explain of section
<pre>
/controls/pneumatic/APU-bleed
/controls/pneumatic/engine[%d]/bleed
</pre>
TODO - section notes

=== Pressurization ===
TODO - explain of section
<pre>
/controls/pressurization/mode
/controls/pressurization/dump
/controls/pressurization/outflow-valve
/controls/pressurization/pack[%d]/pack-on
</pre>
TODO - section notes

=== Seat ===
TODO - explain of section
<pre>
/controls/seat/vertical-adjust
/controls/seat/fore-aft-adjust
/controls/seat/cmd_selector_valve
/controls/seat/eject[%d]/initiate
/controls/seat/eject[%d]/status
</pre>
TODO - section notes

== Engines ==
Status of engines. See also: /controls/engines/
=== Common ===
<pre>
/engines/engine[%d]/fuel-flow-gph
/engines/engine[%d]/fuel-flow_pph
/engines/engine[%d]/thrust_lb
/engines/engine[%d]/running
/engines/engine[%d]/starter
/engines/engine[%d]/cranking
/engines/engine[%d]/fire
</pre>

=== Turbine ===
<pre>
/engines/engine[%d]/n1
/engines/engine[%d]/n2
/engines/engine[%d]/epr
/engines/engine[%d]/augmentation
/engines/engine[%d]/water-injection
/engines/engine[%d]/ignition
/engines/engine[%d]/nozzle-pos-norm
/engines/engine[%d]/inlet-pos-norm
/engines/engine[%d]/reversed
/engines/engine[%d]/cutoff
</pre>

=== Piston ===
<pre>
/engines/engine[%d]/mp-osi
/engines/engine[%d]/egt-degf
/engines/engine[%d]/oil-temperature-degf
/engines/engine[%d]/oil-pressure-psi
/engines/engine[%d]/cht-degf
/engines/engine[%d]/rpm
</pre>

=== Propeller ===
<pre>
/engines/engine[%d]/rpm
/engines/engine[%d]/pitch
/engines/engine[%d]/torque
</pre>
TODO - section notes

== Flight Dynamics Model ==
=== Position ===
This will return the current position of the aircraft within FlightGear. This is also the stuff that is transmitted in [[Howto:Multiplayer|multiplayer]].

<pre>
/position/
/position/altitiude-ft ()
/position/altitude-agl-ft (22.46983965)
/position/altitude-ft (28.24368289)
/position/ground-elev-ft (-0.43513529)
/position/ground-elev-m (-0.1326292364)
/position/latitude-deg (37.61371436)
/position/latitude-string (37*36 49.4N)
/position/longitude-deg (-122.3576508)
/position/longitude-string (-122*21 27.5W)
/position/sea-level-radius-ft (20899648.76)
</pre>

=== Orientation ===
TODO - explain of section
<pre>
/orientation/roll-deg
/orientation/pitch-deg
/orientation/heading-deg

/orientation/roll-rate-degps
/orientation/pitch-rate-degps
/orientation/yaw-rate-degps

/orientation/side-slip-rad
/orientation/side-slip-deg
/orientation/alpha-deg
</pre>
TODO - section notes

=== Velocities ===
TODO - explain of section
<pre>
/velocities/airspeed-kt
/velocities/mach
/velocities/speed-north-fps
/velocities/speed-east-fps
/velocities/speed-down-fps

/velocities/uBody-fps
/velocities/vBody-fps
/velocities/wBody-fps

/velocities/vertical-speed-fps
/velocities/glideslope
</pre>
TODO - section notes

=== Acceleration ===
TODO - explain of section
<pre>
/accelerations/nlf

/accelerations/ned/north-accel-fps_sec
/accelerations/ned/east-accel-fps_sec
/accelerations/ned/down-accel-fps_sec

/accelerations/pilot/x-accel-fps_sec
/accelerations/pilot/y-accel-fps_sec
/accelerations/pilot/z-accel-fps_sec
</pre>
TODO - section notes

== Gear ==
<pre>
/gear/serviceable
/gear/gear[%d]/cast-angle-deg // The angle of the wheel where 0 is pointing straight forward
/gear/gear[%d]/compression-m
/gear/gear[%d]/compression-norm
/gear/gear[%d]/ground-friction-factor
/gear/gear[%d]/ground-is-solid
/gear/gear[%d]/has-brake
/gear/gear[%d]/rollspeed-ms // Speed of the wheel's rotation in meters per second
/gear/gear[%d]/wow // Weight-on-wheel
/gear/gear[%d]/xoffset-in
/gear/gear[%d]/yoffset-in
/gear/gear[%d]/zoffset-in
</pre>

== Instrumentation ==
<pre>
/instrumentation/adf/
/instrumentation/airspeed-indicator/
/instrumentation/altimeter/
/instrumentation/annunciator/
/instrumentation/attitude-indicator/
/instrumentation/clock/
/instrumentation/comm/
/instrumentation/comm[1]/
/instrumentation/dme/
/instrumentation/efis/
/instrumentation/encoder/
/instrumentation/flightdirector/
/instrumentation/gps/
/instrumentation/gps-annunciator/
/instrumentation/heading-indicator/
/instrumentation/heading-indicator-fg/
/instrumentation/magnetic-compass/
/instrumentation/marker-beacon/
/instrumentation/nav/
/instrumentation/nav[1]/
/instrumentation/radar/
/instrumentation/slip-skid-ball/
/instrumentation/tacan/
/instrumentation/transponder/
/instrumentation/turn-indicator/
/instrumentation/vertical-speed-indicator/
/instrumentation/wxradar/
</pre>

=== Instrumentation comm radio ===

<pre>
/instrumentation/comm/add-noise
/instrumentation/comm/airport-id
/instrumentation/comm/atis
/instrumentation/comm/channel-button
/instrumentation/comm/chanel-mode-selector
/instrumentation/comm/cutoff-signal-quality
/instrumentation/comm/frequencies
/instrumentation/comm/frequencies/dial-khz
/instrumentation/comm/frequencies/dial-mhz
/instrumentation/comm/frequencies/selected-channel
/instrumentation/comm/frequencies/selected-channel-width-khz
/instrumentation/comm/frequencies/selected-mhz
/instrumentation/comm/frequencies/selected-mhz-fmt
/instrumentation/comm/frequencies/selected-real-frequency-mhz
/instrumentation/comm/frequencies/standby-channel
/instrumentation/comm/frequencies/standby-channel-width-khz
/instrumentation/comm/frequencies/standby-mhz
/instrumentation/comm/frequencies/standby-mhz-fmt
/instrumentation/comm/frequencies/standby-real-frequency-mhz
/instrumentation/comm/frq-swap-btn
/instrumentation/comm/height-above-station-ft
/instrumentation/comm/operable
/instrumentation/comm/power-btn
/instrumentation/comm/ptt
/instrumentation/comm/servicable
/instrumentation/comm/signal-quality-norm
/instrumentation/comm/slant-distance-m
/instrumentation/comm/station-name
/instrumentation/comm/station-type
/instrumentation/comm/test-btn
/instrumentation/comm/track-distance-m
/instrumentation/comm/true-bearing-from-deg
/instrumentation/comm/true-bearing-to-deg
/instrumentation/comm/volume
/instrumentation/comm/volume-selected
</pre>

== Rotors (YASim only) ==
<pre>
/rotors/gear/torque-sound-filtered // Unused?
/rotors/gear/total-torque
/rotors/{name}/balance
/rotors/{name}/blade[%d]/flap-deg
/rotors/{name}/blade[%d]/incidence-deg
/rotors/{name}/blade[%d]/position-deg // Position relative to model
/rotors/{name}/bladesvisible // Used for animations
/rotors/{name}/cone%d-deg //e.g. cone-deg or cone2-deg
/rotors/{name}/roll-deg
/rotors/{name}/rpm
/rotors/{name}/stall
/rotors/{name}/stall-filtered
/rotors/{name}/tilt
/rotors/{name}/torque
/rotors/{name}/yaw-deg
</pre>

For how to animate rotors using these properties, see [[Howto:Animate helicopters]].

== Related content ==
=== Wiki articles ===
* [[Aircraft-set.xml]]
* [[Multiplayer protocol]]
* [[Property browser]]
* [[PropertyList XML files]]
* [[Property tree]]

=== Readme files ===
* {{readme file|properties}}

=== Source code ===
==== Consumables ====
* {{flightgear file|src/FDM/TankProperties.hxx}}
* {{flightgear file|src/FDM/TankProperties.cxx}}

==== Controls ====
* {{flightgear file|src/Aircraft/controls.hxx}}
* {{flightgear file|src/Aircraft/controls.cxx}}

==== Flight Dynamics Model ====
* {{flightgear file|src/FDM/flightProperties.hxx}}
* {{flightgear file|src/FDM/flightProperties.cxx}}

==== Instrumentation ====
* {{flightgear file|src/Instrumentation}}

[[Category:Property Tree]]
[[Category:Aircraft enhancement]]

User:Www2/NextNav

2022-10-27T21:39:55Z

Www2:

== Introduction ==
As we know is that one of the current weakness of FlightFear is that our NavAids database is out of date and don't support things as airspace, GBAS, GLS, LAAS, HF comm, etc.
The goal of the NextNav project is for closing the gap between flight gear and other flight sims as MSFS2020 and xp12 in the area of navigation data set.
This is not to replace our current data-set (in the rest of this document i call this data-set GPL data-set) but the new data-set is an optional data-set that need be enable by the user by downloading demo datasets from FlightGear servers or the current datasets navigraph.

== NextNav Database ==
The NextNav database is call sim424 this name come from airnic 424 standard.
The database it self is an set of sqlite database that is using that are locate in $FGHOME/NavData/NextNav, $FGROOT/NavData/NextNav/ and $scenery/NavData/NextNav.

* NavDB_navdata_earth.nndb
This is the general datasets from Navigraph and is the key for enable flightgear NextNav dataset mode instate of the GPL datasets.
Other files that is include in this dataset is cycle.json is use for displaying the AIRAC cycle that the dataset are using.
fileformat: sqlite

* NavDB_Legacy_earth.nndb
This file contain Procedures for Legacy airports as Kai Tak (VHHX/VHXX) Hong Kong and Berlin Templehof (EDDI) and routs as Concorde NAT routes.
fileformat: sqlite

* NavDB_patch_earth.txt
this is an patch file that is use to add/modified navaids in navdata for use in a custom scenery.
fileformat: json

* NavDB_user_earth.nndb
This are custom Navdata that are create by the user.
fileformat: sqlite

* Alias_earth.csv
This file is use for airports that have multiple ICAO codes or two airports that share runways.
e.g. Kai Tak (VHHX/VHXX) for a airport with 2 icao code and Daniel K. Inouye International Airport (PHNL)/Hickam Air Force Base (PHIK) as an airports that share runways.
fileformat: CSV

{| class="wikitable"
|+ NextNav file Name and locations
|-
! Header text !! $FGROOT/NavData/NextNav/ !! $FGHOME/NavData/NextNav !! $scenery/NavData/NextNav
|-
| NavDB_navdata_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_Legacy_earth.nndb || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_patch_earth.txt || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || [[File:Tick 32px.png]]
|-
| NavDB_user_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| Alias_earth.cvs ||[[File:Tick 32px.png]] || [[File:Tick 32px.png]] || [[File:Tick 32px.png]]
|}

== block diagram ==
[[File:NextNAV current situation.png|600px|This is the current situation of flightgear database.]]
[[File:NextNAV newSituation.png|600px|This is the new Situation after NextNAV is implementation]]

== tools ==
The foaling list are tools needed to be create for this project.

=== Navigraph tools (low priority) ===
This is the tool that generate the Navdata form Navigraph database.

=== Standalone Test tool (high priority) ===
This tool is create for helping testing the new data format and helping to create better models for navigation equipment.

=== editor (medium priority) ===
The editor that is use for helping creating custom scenery and add/remove navaids.

User:Www2/NextNav

2022-10-27T21:29:45Z

Www2: /* tools */

== Introduction ==
As we know is that one of the current weakness of FlightFear is that our NavAids database is out of date and don't support things as airspace, GBAS, GLS, LAAS, HF comm, etc.
The goal of the NextNav project is for closing the gap between flight gear and other flight sims as MSFS2020 and xp12 in the area of navigation data set.
This is not to replace our current data-set (in the rest of this document i call this data-set GPL data-set) but the new data-set is an optional data-set that need be enable by the user by downloading demo datasets from FlightGear servers or the current datasets navigraph.

== NextNav Database ==
The NextNav database is call sim424 this name come from airnic 424 standard.
The database it self is an set of sqlite database that is using that are locate in $FGHOME/NavData/NextNav, $FGROOT/NavData/NextNav/ and $scenery/NavData/NextNav.

* NavDB_navdata_earth.nndb
This is the general datasets from Navigraph and is the key for enable flightgear NextNav dataset mode instate of the GPL datasets.
Other files that is include in this dataset is cycle.json is use for displaying the AIRAC cycle that the dataset are using.
fileformat: sqlite

* NavDB_Legacy_earth.nndb
This file contain Procedures for Legacy airports as Kai Tak (VHHX/VHXX) Hong Kong and Berlin Templehof (EDDI) and routs as Concorde NAT routes.
fileformat: sqlite

* NavDB_patch_earth.txt
this is an patch file that is use to add/modified navaids in navdata for use in a custom scenery.
fileformat: json

* NavDB_user_earth.nndb
This are custom Navdata that are create by the user.
fileformat: sqlite

* Alias_earth.csv
This file is use for airports that have multiple ICAO codes or two airports that share runways.
e.g. Kai Tak (VHHX/VHXX) for a airport with 2 icao code and Daniel K. Inouye International Airport (PHNL)/Hickam Air Force Base (PHIK) as an airports that share runways.
fileformat: CSV

{| class="wikitable"
|+ NextNav file Name and locations
|-
! Header text !! $FGROOT/NavData/NextNav/ !! $FGHOME/NavData/NextNav !! $scenery/NavData/NextNav
|-
| NavDB_navdata_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_Legacy_earth.nndb || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_patch_earth.txt || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || [[File:Tick 32px.png]]
|-
| NavDB_user_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| Alias_earth.cvs ||[[File:Tick 32px.png]] || [[File:Tick 32px.png]] || [[File:Tick 32px.png]]
|}

== block diagram ==
[[File:NextNAV current situation.png|600px|This is the current situation of flightgear database.]]
[[File:NextNAV newSituation.png|600px|This is the new Situation after NextNAV is implementation]]

== tools ==
The foaling list are tools needed to be create for this project.

=== Navigraph tools (low priority) ===
This is the tool that generate the Navdata form navigraph database.

=== Standalone Test tool (high priority) ===
TBA
=== editor (medium priority) ===
The editor that is use for helping creating custom scenery and add/remove navaids.

User:Www2/NextNav

2022-10-27T19:47:25Z

Www2: /* block diagram */

== Introduction ==
As we know is that one of the current weakness of FlightFear is that our NavAids database is out of date and don't support things as airspace, GBAS, GLS, LAAS, HF comm, etc.
The goal of the NextNav project is for closing the gap between flight gear and other flight sims as MSFS2020 and xp12 in the area of navigation data set.
This is not to replace our current data-set (in the rest of this document i call this data-set GPL data-set) but the new data-set is an optional data-set that need be enable by the user by downloading demo datasets from FlightGear servers or the current datasets navigraph.

== NextNav Database ==
The NextNav database is call sim424 this name come from airnic 424 standard.
The database it self is an set of sqlite database that is using that are locate in $FGHOME/NavData/NextNav, $FGROOT/NavData/NextNav/ and $scenery/NavData/NextNav.

* NavDB_navdata_earth.nndb
This is the general datasets from Navigraph and is the key for enable flightgear NextNav dataset mode instate of the GPL datasets.
Other files that is include in this dataset is cycle.json is use for displaying the AIRAC cycle that the dataset are using.
fileformat: sqlite

* NavDB_Legacy_earth.nndb
This file contain Procedures for Legacy airports as Kai Tak (VHHX/VHXX) Hong Kong and Berlin Templehof (EDDI) and routs as Concorde NAT routes.
fileformat: sqlite

* NavDB_patch_earth.txt
this is an patch file that is use to add/modified navaids in navdata for use in a custom scenery.
fileformat: json

* NavDB_user_earth.nndb
This are custom Navdata that are create by the user.
fileformat: sqlite

* Alias_earth.csv
This file is use for airports that have multiple ICAO codes or two airports that share runways.
e.g. Kai Tak (VHHX/VHXX) for a airport with 2 icao code and Daniel K. Inouye International Airport (PHNL)/Hickam Air Force Base (PHIK) as an airports that share runways.
fileformat: CSV

{| class="wikitable"
|+ NextNav file Name and locations
|-
! Header text !! $FGROOT/NavData/NextNav/ !! $FGHOME/NavData/NextNav !! $scenery/NavData/NextNav
|-
| NavDB_navdata_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_Legacy_earth.nndb || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_patch_earth.txt || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || [[File:Tick 32px.png]]
|-
| NavDB_user_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| Alias_earth.cvs ||[[File:Tick 32px.png]] || [[File:Tick 32px.png]] || [[File:Tick 32px.png]]
|}

== block diagram ==
[[File:NextNAV current situation.png|600px|This is the current situation of flightgear database.]]
[[File:NextNAV newSituation.png|600px|This is the new Situation after NextNAV is implementation]]

== tools ==
The foaling list are tools needed for this project

=== Navigraph tools ===
This is the tool that generate the Navdata form navigraph.

=== editor ===

User:Www2/NextNav

2022-10-27T19:41:11Z

Www2: add block diagrams

== Introduction ==
As we know is that one of the current weakness of FlightFear is that our NavAids database is out of date and don't support things as airspace, GBAS, GLS, LAAS, HF comm, etc.
The goal of the NextNav project is for closing the gap between flight gear and other flight sims as MSFS2020 and xp12 in the area of navigation data set.
This is not to replace our current data-set (in the rest of this document i call this data-set GPL data-set) but the new data-set is an optional data-set that need be enable by the user by downloading demo datasets from FlightGear servers or the current datasets navigraph.

== NextNav Database ==
The NextNav database is call sim424 this name come from airnic 424 standard.
The database it self is an set of sqlite database that is using that are locate in $FGHOME/NavData/NextNav, $FGROOT/NavData/NextNav/ and $scenery/NavData/NextNav.

* NavDB_navdata_earth.nndb
This is the general datasets from Navigraph and is the key for enable flightgear NextNav dataset mode instate of the GPL datasets.
Other files that is include in this dataset is cycle.json is use for displaying the AIRAC cycle that the dataset are using.
fileformat: sqlite

* NavDB_Legacy_earth.nndb
This file contain Procedures for Legacy airports as Kai Tak (VHHX/VHXX) Hong Kong and Berlin Templehof (EDDI) and routs as Concorde NAT routes.
fileformat: sqlite

* NavDB_patch_earth.txt
this is an patch file that is use to add/modified navaids in navdata for use in a custom scenery.
fileformat: json

* NavDB_user_earth.nndb
This are custom Navdata that are create by the user.
fileformat: sqlite

* Alias_earth.csv
This file is use for airports that have multiple ICAO codes or two airports that share runways.
e.g. Kai Tak (VHHX/VHXX) for a airport with 2 icao code and Daniel K. Inouye International Airport (PHNL)/Hickam Air Force Base (PHIK) as an airports that share runways.
fileformat: CSV

{| class="wikitable"
|+ NextNav file Name and locations
|-
! Header text !! $FGROOT/NavData/NextNav/ !! $FGHOME/NavData/NextNav !! $scenery/NavData/NextNav
|-
| NavDB_navdata_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_Legacy_earth.nndb || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_patch_earth.txt || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || [[File:Tick 32px.png]]
|-
| NavDB_user_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| Alias_earth.cvs ||[[File:Tick 32px.png]] || [[File:Tick 32px.png]] || [[File:Tick 32px.png]]
|}

== block diagram ==
[[File:NextNAV current situation.png|thumb|This is the current situation of flightgear database.]]
[[File:NextNAV newSituation.png|thumb|This is the new Situation after NextNAV is implementation]]

== tools ==
The foaling list are tools needed for this project

=== Navigraph tools ===
This is the tool that generate the Navdata form navigraph.

=== editor ===

File:NextNAV newSituation.png

2022-10-27T19:40:29Z

Www2: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=This is the new Situation after NextNAV is implementation}}
|date=2022-10-27
|source={{own}}
|author=[[User:Www2|Www2]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-zero}}

File:NextNAV current situation.png

2022-10-27T19:40:29Z

Www2: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=This is the current situation of flightgear database.}}
|date=2022-10-27
|source={{own}}
|author=[[User:Www2|Www2]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-zero}}

User:Www2/NextNav

2022-10-27T19:31:11Z

Www2: /* NextNav Database */

== Introduction ==
As we know is that one of the current weakness of FlightFear is that our NavAids database is out of date and don't support things as airspace, GBAS, GLS, LAAS, HF comm, etc.
The goal of the NextNav project is for closing the gap between flight gear and other flight sims as MSFS2020 and xp12 in the area of navigation data set.
This is not to replace our current data-set (in the rest of this document i call this data-set GPL data-set) but the new data-set is an optional data-set that need be enable by the user by downloading demo datasets from FlightGear servers or the current datasets navigraph.

== NextNav Database ==
The NextNav database is call sim424 this name come from airnic 424 standard.
The database it self is an set of sqlite database that is using that are locate in $FGHOME/NavData/NextNav, $FGROOT/NavData/NextNav/ and $scenery/NavData/NextNav.

* NavDB_navdata_earth.nndb
This is the general datasets from Navigraph and is the key for enable flightgear NextNav dataset mode instate of the GPL datasets.
Other files that is include in this dataset is cycle.json is use for displaying the AIRAC cycle that the dataset are using.
fileformat: sqlite

* NavDB_Legacy_earth.nndb
This file contain Procedures for Legacy airports as Kai Tak (VHHX/VHXX) Hong Kong and Berlin Templehof (EDDI) and routs as Concorde NAT routes.
fileformat: sqlite

* NavDB_patch_earth.txt
this is an patch file that is use to add/modified navaids in navdata for use in a custom scenery.
fileformat: json

* NavDB_user_earth.nndb
This are custom Navdata that are create by the user.
fileformat: sqlite

* Alias_earth.csv
This file is use for airports that have multiple ICAO codes or two airports that share runways.
e.g. Kai Tak (VHHX/VHXX) for a airport with 2 icao code and Daniel K. Inouye International Airport (PHNL)/Hickam Air Force Base (PHIK) as an airports that share runways.
fileformat: CSV

{| class="wikitable"
|+ NextNav file Name and locations
|-
! Header text !! $FGROOT/NavData/NextNav/ !! $FGHOME/NavData/NextNav !! $scenery/NavData/NextNav
|-
| NavDB_navdata_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_Legacy_earth.nndb || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_patch_earth.txt || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || [[File:Tick 32px.png]]
|-
| NavDB_user_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| Alias_earth.cvs ||[[File:Tick 32px.png]] || [[File:Tick 32px.png]] || [[File:Tick 32px.png]]
|}

== block diagram ==

TBA

== tools ==
The foaling list are tools needed for this project

=== Navigraph tools ===
This is the tool that generate the Navdata form navigraph.

=== editor ===

User:Www2/NextNav

2022-09-15T00:30:19Z

Www2: /* Navigraph tools */

== Introduction ==
As we know is that one of the current weakness of FlightFear is that our NavAids database is out of date and don't support things as airspace, GBAS, GLS, LAAS, HF comm, etc.
The goal of the NextNav project is for closing the gap between flight gear and other flight sims as MSFS2020 and xp12 in the area of navigation data set.
This is not to replace our current data-set (in the rest of this document i call this data-set GPL data-set) but the new data-set is an optional data-set that need be enable by the user by downloading demo datasets from FlightGear servers or the current datasets navigraph.

== NextNav Database ==
The NextNav database is call sim424 this name come from airnic 424 standard.
The database it self is an set of sqlite database that is using that are locate in $FGHOME/NavData/NextNav, $FGROOT/NavData/NextNav/ and $scenery/NavData/NextNav.

* NavDB_navdata_earth.nndb
This is the general datasets from Navigraph and is the key for enable flightgear NextNav dataset mode instate of the GPL datasets.
Other files that is include in this dataset is cycle.json is use for displaying the AIRAC cycle that the dataset are using.
fileformat: sqlite

* NavDB_Legacy_earth.nndb
This file contain Procedures for Legacy airports as Kai Tak (VHHX/VHXX) Hong Kong and Berlin Templehof (EDDI) and routs as Concorde NAT routes.
fileformat: sqlite

* NavDB_patch_earth.txt
this is an patch file that is use to add/modified navaids in navdata for use in a custom scenery.
fileformat: json

* NavDB_user_earth.nndb
This are custom Navdata that are create by the user.
fileformat: sqlite

* Alias_earth.csv
This file is use for airports that have multiple ICAO codes or two airports that share runways.
e.g. Kai Tak (VHHX/VHXX) for a airport with 2 icao code and Daniel K. Inouye International Airport (PHNL)/Hickam Air Force Base (PHIK) as an airports that share runways.
fileformat: CSV

{| class="wikitable"
|+ NextNav file Name and locations
|-
! Header text !! $FGROOT/NavData/NextNav/ !! $FGHOME/NavData/NextNav !! $scenery/NavData/NextNav
|-
| NavDB_navdata_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_Legacy_earth.nndb || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_patch_earth.txt || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || [[File:Tick 32px.png]]
|-
| NavDB_user_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| Alias_earth.txt || [[File:Tick 32px.png]] || [[File:Tick 32px.png]] || [[File:Tick 32px.png]]
|}

== block diagram ==

TBA

== tools ==
The foaling list are tools needed for this project

=== Navigraph tools ===
This is the tool that generate the Navdata form navigraph.

=== editor ===

User:Www2/NextNav

2022-09-11T02:56:52Z

Www2:

== Introduction ==
As we know is that one of the current weakness of FlightFear is that our NavAids database is out of date and don't support things as airspace, GBAS, GLS, LAAS, HF comm, etc.
The goal of the NextNav project is for closing the gap between flight gear and other flight sims as MSFS2020 and xp12 in the area of navigation data set.
This is not to replace our current data-set (in the rest of this document i call this data-set GPL data-set) but the new data-set is an optional data-set that need be enable by the user by downloading demo datasets from FlightGear servers or the current datasets navigraph.

== NextNav Database ==
The NextNav database is call sim424 this name come from airnic 424 standard.
The database it self is an set of sqlite database that is using that are locate in $FGHOME/NavData/NextNav, $FGROOT/NavData/NextNav/ and $scenery/NavData/NextNav.

* NavDB_navdata_earth.nndb
This is the general datasets from Navigraph and is the key for enable flightgear NextNav dataset mode instate of the GPL datasets.
Other files that is include in this dataset is cycle.json is use for displaying the AIRAC cycle that the dataset are using.
fileformat: sqlite

* NavDB_Legacy_earth.nndb
This file contain Procedures for Legacy airports as Kai Tak (VHHX/VHXX) Hong Kong and Berlin Templehof (EDDI) and routs as Concorde NAT routes.
fileformat: sqlite

* NavDB_patch_earth.txt
this is an patch file that is use to add/modified navaids in navdata for use in a custom scenery.
fileformat: json

* NavDB_user_earth.nndb
This are custom Navdata that are create by the user.
fileformat: sqlite

* Alias_earth.csv
This file is use for airports that have multiple ICAO codes or two airports that share runways.
e.g. Kai Tak (VHHX/VHXX) for a airport with 2 icao code and Daniel K. Inouye International Airport (PHNL)/Hickam Air Force Base (PHIK) as an airports that share runways.
fileformat: CSV

{| class="wikitable"
|+ NextNav file Name and locations
|-
! Header text !! $FGROOT/NavData/NextNav/ !! $FGHOME/NavData/NextNav !! $scenery/NavData/NextNav
|-
| NavDB_navdata_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_Legacy_earth.nndb || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || [[File:Cross 32px.png]]
|-
| NavDB_patch_earth.txt || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || [[File:Tick 32px.png]]
|-
| NavDB_user_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]]
|-
| Alias_earth.txt || [[File:Tick 32px.png]] || [[File:Tick 32px.png]] || [[File:Tick 32px.png]]
|}

== block diagram ==

TBA

== tools ==
The foaling list are tools needed for this project

=== Navigraph tools ===

=== editor ===

User:Www2/NextNav

2022-09-10T23:24:21Z

Www2: WIP proposle

== Introduction ==
As we know is that one of the current weakness of FlightFear is that our NavAids database is out of date and don't support things as airspace, GBAS, GLS, LAAS, HF comm, etc.
The goal of the NextNav project is for closing the gap between flight gear and other flight sims as MSFS2020 and xp12 in the area of navigation data set.
This is not to replace our current data-set (in the rest of this document i call this data-set GPL data-set) but the new data-set is an optional data-set that need be enable by the user by downloading demo datasets from FlightGear servers or the current datasets navigraph.

== NextNav Database ==
The NextNav database is call sim424 this name come from airnic 424 standard.
The database it self is an set of sqlite database that is using that are locate in $FGHOME/NavData/NextNav, $FGROOT/NavData/NextNav/ and $scenery/NavData/NextNav.

* NavDB_navdata_earth.nndb
This is the general datasets from Navigraph and is the key for enable flightgear NextNav dataset mode instate of the GPL datasets.
Other files that is include in this dataset is cycle.json is use for displaying the AIRAC cycle that the dataset are using.

* NavDB_Legacy_earth.nndb
This file contain Procedures for Legacy airports as Kai Tak (VHHX/VHXX) Hong Kong and Berlin Templehof (EDDI) and routs as Concorde NAT routes.

* NavDB_patch_earth.txt
this is an patch file that

*

{| class="wikitable"
|+ NextNav file Name and locations
|-
! Header text !! $FGROOT/NavData/NextNav/ !! $FGHOME/NavData/NextNav !! $scenery/NavData/NextNav !! notes
|-
| NavDB_navdata_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || Navigraph dataset
|-
| NavDB_Legacy_earth.nndb || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || NavData for Legacy airports asd KaiTak (VHHX/VHXX), TempelHof (EDDI) and NAT Concorde Routes
|-
| NavDB_patch_earth.txt || [[File:Cross 32px.png]] || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || Fix for custom scenerys
|-
| NavDB_user_earth.nndb || [[File:Cross 32px.png]] || [[File:Tick 32px.png]] || [[File:Cross 32px.png]] || Custom navdata generate by the user
|-
| Alias_earth.txt || [[File:Tick 32px.png]] || [[File:Tick 32px.png]] || [[File:Tick 32px.png]] || List of airports that have more that one ICAO code or two airports that combine runways e.g. Kai Tak (VHHX/VHXX) and Daniel K. Inouye International Airport (PHNL)/Hickam Air Force Base (PHIK)
|}

Property Tree/Sockets

2022-09-07T10:39:34Z

Www2: Fix what looks like an copy and pace error

{{PropertyTree}}
It should be pretty straightforward to use FG to playback a real flight. With FG you can slave multiple instances to one master instance of FG in real time. Slaving a copy of FG to a recorded data stream should be also very similar.

I have instances of FG talking to other copies of FG as well as an external FDM talking to FG using the same structure. There can be packing differences between compilers, but we were pretty careful with the current structure (all values are 4 or 8 bytes) and we don't know of any compilers that pack the structure differently from any other compilers.

You can overwrite most properties using a custom protocol, however you have to ensure that the data you are trying to overwrite isn't being written to by any other subsystems or parts of FlightGear.

This could for example be the FDM, which uses so called "tied properties" - basically, the properties tied by the FDM are not owned by the property tree, they are owned by the FDM and the property tree merely holds references/pointers to the FDM properties.

In a sense, you have to differentiate between input and output properties.

The easiest thing to avoid such problems is to completely disable the corresponding subsystem. In the case of the FDM this can be done by configuring the --fdm=null switch. So that no FDM is instantiated, that might cause conflicts.

On the other hand there are a number of subsystems that cannot currently be directly disabled, these would need to be patched in the source code.

Also, any property which is updated in a hard coded fashion could possibly conflict with your UDP packets. For example, some properties are updated each frame, and while overwriting these properties will not yield an error or warning, your updates would be invalidated due to these hard coded updates in the main loop.

<pre>
The following fgfs parameters will create the control sockets:
--native-ctrls=socket,in,10,127.0.0.1,5600,udp
--native-ctrls=socket,out,10,127.0.0.1,5700,udp

You will likely also need FDM data:
--native-fdm=socket,out,10,127.0.0.1,5500,udp
</pre>

== Getting started ==
One big question is what language/platform are you connecting to?

The easiest thing to do would be to write the other application in C/C++ and just use the exact same structure. If you look at the socket calls you will see that you provide a buffer and a length and it will fill it in with the network data.

You may have to worry about endianess if you are communicating between two different architectures, but in this case, the code converts to/from network byte order so that shouldn't be a problem.

If you want to know the size of different structures such as bool or int or double, there is a function in C/C++ called sizeof(). So you
could do something like "cout << sizeof(bool) << endl;"

== FlightGear vs. WideFS ==
FlightGear can do all that already. You can set up one copy to be a master, and any number of additional copies to be slaves. For each display channel you can specify view offset direction and fov. You can set up anything from a simple 3 monitor display system to some huge convoluted mess if you want to
gang up 20 machines.

== Hardware in the loop ==
Our solution has been to use the FGNetCtrls interface to FG and write a gateway application that would interface our UAV flight control computer (via serial port) to FG (via TCP). This allows us to do hardware-in-the-loop testing of the autopilot system. If preferable, you could also implement the flight control laws in a PC application and "fly" the FG model via a TCP connection.

Actually, flightgear has proven to be a versatile tool for our project. It is also good as a visualization system (either live during flight or for post-mission replay). Once you figure it out, communication with FG is pretty easy. I've just created a C# class to handle all I/O to FG, and can drop it in where needed.

== UAV Visualization ==

This use case is utilized in [https://wiki.paparazziuav.org/wiki/FlightGear Paparazzi autopilot]

And if you are using FlightGear as a visualization system for your UAV (either live or replaying the data) you can turn on multiplayer mode and inject yourself into the multiplayer system. I'm doing that right now. If you want to see my university's UAV in action, go to
mpmap01.flightgear.org right now and click the checkbox next to the Rascal-1 call sign. I'm looping the data and will probably continue looping it for the rest of the day. We don't have a wireless internet connection that available at our flying field, but someday if we are
able to rig something up, we'll be able to inject our live flight data into the multiplayer system which and others could come fly [virtually]
with us. That would be kind of a neat trick.

== Using Proprietary/External FDMs ==
Take a look at net_fdm.* and native_ctrls.* in the FlightGear/src/Network directory. Those are the one you want to use.

Also look at Docs/README.IO

You can turn off the built in flight dynamics engine with the --fdm=null option. Then specify the --native-fdm= and --native-ctrls= options with appropriate parameters. That sets up FlightGear to receive data from an external source. Then all you have to do is look at the UDP packet structure and send data packets from your external software. There maybe some trickier details if you've never done socket communication before, but it's been done many times and there are many examples to look at including the FlightGear code itself. You can configure one "master" copy of FlightGear to control one (or more) other copies of FlightGear in this same way -- this is one way to achieve a multi-screen cockpit display if you don't want to plug multiple monitors into a single computer.

Look in net_fdm.hxx for the variable type and units, as in radians and meters.

The goal is to also include in that subdir some stand along FDM wrapper apps that interface to FlightGear via the ExternalNet interface. These would act as examples for people interested in integrating other FDM codes this way.

I also removed the External fdm because it is replaced by a better named NullFDM fdm. The --fdm=external option is stull supported for backwards compatibility but maps to --fdm=null (which does the same thing.)

So the only command line change would be to go from
<pre>
--native=socket,in,30,,5500,udp --fdm=external
</pre>
to
<pre>
--native=socket,in,30,,5500,udp --fdm=null
</pre>
--fdm=external still works even though --fdm=null is now the 'official' way to do it.

Some of the benefits of running the FDM portion as a standalone app separate from flight gear are:

* you can kill and restart the fdm portion without restarting FG.
* you can change/recompile/rerun the fdm portion without restarting FG.
* when developing the fdm portion, you don't need to spend the overhead of compiling/linking with FG and starting FG from scratch.
* you can interface non-GPL'd flight dynamics code via this mechanism.
* you can run the FDM on a separate machine/OS, separate CPU, you could even develop it in a different computer language.

Almost all if not all of the FGNetFDM values are getting filled in by the fdm. But it is likely that not all fdm's will generate entirely the same output fields, and not all of them will care about entirely the same inputs.

Out of necessity this structure is extended as new needs are discovered. We include a version number in the structure so software on either end can verify they are passing the same version of the contents.

The included source code that can take an instance of NetFDM and translate it into FG properties as well as the code that can build an instance of NetFDM from the current state of the property tree can optionally do it's work in network byte order.

When the structure does change, it is literally trivial to upgrade the other end. Copy over the new structure, see if you care about any of the new fields (usually not) and recompile your software.

If they want the ultimate in flexibility they should use Eric's "generic" output facility because there you can define exactly what output you want via an xml config file and it only changes when you want it to change.

== FlightGear as a Scenery Generator ==
FlightGear has exactly what you are looking for.

Look in src/Network/net_fdm.hxx ... this defines a structure that you can pass to FG. If you run FG with the --fdm=null option you will disable the internal flight dynamics and you will get whatever you pass in with the net_fdm.hxx structure.

Additionally we have a net_ctrls.hxx structure which you can also pass to FG. That will enable the controls (ailerons, flaps, gear, etc.) to be animated in the external views.

FlightGear has been used as an image generator on an FAA Level 3 FTD certified simulator. I've seen people post questions who are also working on leveraging FG as an image generator in one way or another ... either interfacing it to an existing simulator, or trying to import the FG scenery into their existing image generation software, or trying to import their existing image generation scenery back into FG.

There are a couple things to keep in mind that you will run into soon enough.

* You need the airport runway and navaid database to match between FlightGear and PS1. If they don't, you are going to be perfectly lined up on your approach in PS1, and may pop out of the clouds to find yourself severely misaligned with the runway.

* You need PS1 and FG to agree on the ground elevation. FG can be configured to send export the elevation of the ground in the FG world at the current spot, but you'd need to find a way to import that back into PS1. If you can pull that off, then you can properly taxi on FG's non-flat runways, you won't be able to fly underground, you won't crash into mystery terrain that is in PS1, but not if FG, etc. etc.

* You will want to pass along weather parameters to FG so that the wind socks are blowing the right way, the cloud layers are in the right place, etc. etc. And if you use multiple displays, you want them all configured the same way and synced with time so they all draw the sun/moon/ stars in the same place, and have the same shading, coloring, and lighting of the scene.

* On good hardware, FG can run at 60+ fps. If I recall, PS1 updates on the DOS interrupt which is 18.2 hz I think. You will get "jittery" video if you don't sync FG exactly to the PS1 clock, or some multiple of that. I'm not sure if it's possible to run your monitor refresh at an exact multiple of 18.2 so you might just have to live with jittery video which you probably don't mind if you are using MSFS as your reference point. :-)

So for the most part, it is all very doable, and you should be able to get something up and running very quickly, especially if you have some socket networking experience, but there are some things that you'll need to consider and handle to really make it work well.

== FGNetFDM & FGNetCtrl ==
What we did with the FGNetFDM and FGNetCtrls structures was to write separate header files outside the scope of the FlightGear project and put these into the public domain.

There is no problem with including these files in a GPL program such as FlightGear, and also no problem including these files in some other proprietary software.

This is not to be seen as an attempt to circumvent the GPL. It's just a convenience to make communication easier and make FG usable for a larger set of tasks.

It's a good idea to think in terms of a "data" channel and a "command" channel. The data channel would be the NetFDM structure that would get blasted over via UDP at a fast rate (i.e. 60 hz) If you drop a packet, don't spend time trying to resend old data, just send the new data and keep going.

The "command" channel (props/telnet) is a lower bandwidth, high reliablity channel. You are guaranteed that every message gets to the reciever once (and only once.) This is great for setting up weather conditions, time of day, camera parameters, and anything else that might have an impact on the visuals. We have a convenient "telnet" interface to all the internal properties and built in commands. Anything you can set from the keyboard, or mouse, or gui, you can do from a remote program or script. It's much lower bandwidth, but very convenient.

You can use the net-ctrls and native-ctrl structures in the Network directory to modify the properties to set radio/nav frequencies but that
takes a bit of work to hack the code. Some of which may not be applicable for general use. Approach would be to add the frequency variables to the
network packet and modify the source to load the values from the received packet into the appropriate properties in FG. Then you'll need to create the
network program on the "simulated radio stack" client to build the packet, create the socket connection, and establish network communications. At least
that's the approach I've taken for my 747 project. If you're modestly fluent in C++, the existing code serves as a good example and base to expand to
meet your needs.

One big problem ;-) The network packet loads at whatever rate you select via the socket options and overwrites any and all the property values called out
in the net-ctrls data structure and that includes all the controls for flying. Which is fine if you plan to also control FG with an external machine. I suppose you could "turn off" updating those properties you don't want to update in FGNetCtrls2Props, but that's a messy hack.

I'm assuming you don't need a lot of bandwidth. There are other options less envasive and unless you plan to expand your hardware at some future date
those might meet your needs

The two native protocols compliment each other. Originally they were designed to communicate with an external FDM. FlightGear would send native-ctrls to the remote FDM module, and it would reply with native-fdm data.

You can sync up visuals by only using native-fdm= since that contains all the position and orientation information.

If you also want to syncronize the control inputs (i.e. for animating the external model) you can add that. This comes in really handy if you are running the wright flyer on a 5 projector wrap around visual system. You want to see that big elevator waggling in front of you as you struggle to stay alive for just a few more seconds.

The slaves should use --fdm=null so they don't try to compute their own positional information.

It really depends on what you are trying to do.

I think you'll find most of the information you need in
* src/Network/net_fdm.hxx
and (if you also send control movements)
* src/Network/net_ctrls.hxx
but some processing (like byte order swapping) most likely is in
* src/Network/native_fdm.{hxx,cxx}
and
* src/Network/native_ctrls.{hxx,cxx}

By default, everything that is transferred is done so in network format (big-endian). Sending data in any other format is asking for trouble (i.e., how can I send data from my PowerPC to my x86 box if it is not in network format). Look at source/src/Network/native_ctrls.cxx to see how the data is processed. The sizes are:

* Boolean = 8-bits
* Integer = 32-bits
* Float = 32-bits
* Double = 64-bits

Don't forget data aligment. The C/C++ compiler will pad data so that is alighed per the processor's architecture. This means that an array of three bytes that is followed by an integer will *MOST LIKELY* have a hidden fourth byte applied after the array and before the integer. The compiler will align data on its native boundary (i.e., 32-bit numbers will start on a 32-bit boundary).

Most compilers have a set of switches you can use to control structure padding and alignment. But indeed, there's nothing in the spec that
says what the proper alignment should be.

FWIW, every compiler I know stores each element in order, and pads it up to its "natural" alignment. So this struct takes 8 bytes in memory
on all platforms I know:

struct { int8_t a; int8_t b; int32_t c; }

But this one takes at least 12 (word-size padding is added at the end on most or all compiler):

struct { int8_t a; int32_t b; int8_t c; }

So long as the structure honors those rules, you should be more or less portable. Other options are, obviously, to store everything as a
int32_t and do the bit packing yourself. You'll need to do this in any case if you want endian compatibility. This is one of the many
reasons that dumping structures from memory to I/O is considered
problematic.

In general, You must never send a binary stucture across a network. Even if you get the sizes correct, you'll have endian problems when running different
architectures (PC vs Mac). You must manually ship the data bytes in a defined order and reconstruct it at the other end. At that point, it doesn't matter what the padding or for different compilers (or the order) is because you won't be sending the padding - just the data.

Never block transfer a structure by providing a pointer and size, there is simply no way for that to work cross-platform.

If deciding to use a binary interface, I'd recommend using XDR (RFC 1014) throughout (already used by the MP system).

It's not too far away from what FG currently has (for the more common platforms at least) but has the advantage of being well-defined.

<stdint.h> is indeed a standard C header but *not* in C++ (though it might be included in the future under the name <cstdint>). AFAIK even if <stdint.h> defines the number of bits for the individual types, it does *not* imply anything about where the individual bits live in memory.
Others have brought up issues like alignment, etc.

The net_fdm.hxx and net_ctrls.hxx files are from Flightgear and define two data structures that can be sent and received by fgfs. In your
program you can receive the FGNetCtrls structure, change the parameters you want to control, and send it back.

== Native Socket ==
Before we interface with FlightGear on a socket, consider this demonstration using the native protocol. TODO: explain native protocol
--native=socket,direction,hz,machine,port,type
direction = in, out or bi
hz = number of times per second
machine = machine name or ip address if client (leave empty if server)
port = port, leave empty to let system choose
type = tcp or udp
eg
--native=socket,out,10,,5444,udp
^ no machine so binds to localhost
--native=socket,in,1,192.5.22.33 ,6789,tcp
//**Important**. space = fail ^

An example of slaving two instances of flight gear together on seperate machines
fgfs1: --native=socket,out,30,seattle.com,5500,udp
fgfs2: --native=socket,in,30,tolouse.net,5500,udp --fdm=external

This instructs the first copy of fgfs to send UDP packets in the
native format to a machine called seattle.com on port 5500.

The second copy of fgfs will accept UDP packets (from anywhere) on port 5500.
Note the additional --fdm=external option. This tells the second copy of fgfs to not run
the normal flight model, but instead set the FDM values based on an external source, the network in this case.

[[Category:Property Tree]]

User:Www2/Sim424

2021-06-28T21:21:21Z

Www2: /* Road Map */

=Introduction=

Current flightgear use a outdate navigation database.
This is not bad due to the license.
The other side of the coin is that we are frozen in time (around September/October 2013) with the navigation database.

A other problem is that that we have no SID, STAR and arrival procedure that is connect to the navaids database.
The rest of the documents describe my view and roadmap to improve this.

=Project=
==Project sim424==

The first part of this project is creating a new database format base on sqlite.
The dataset is split in five parts: GPL, Navigraph(as a replasment of the GPL database, Community, add-ons scenery, and user datasets:

GPL dataset
The classic database is the current navigation database that we using in flightgear convert to the new format.

# Navigraph dataset
This is a optional database with the data source from navigraph that add things as SID, STAR, airways (e.g. trans alantic Concorde Routes), on route ATC and more.
This is release as a optional dataset that the user need to download from the site or as a optional package from the Linux distribution.

# <li value="2"> Community add-on dataset
The community database is the a add-on database for Navigraph or GPL
datasets to add data for close airports (Berlin Tempelhof Airport,
Meigs Field and Kai Tak Hong Kong (This one is include navigraph)) and navigation as Concorde Tracks and provide data for older navigation systems as Low-frequency radio range[1] and LORAN.</li>

# <li value="3"> Add-ons 
This are patches that makes of add-ons scenery's can make to the datasets describe here above as fixing or adding navaids and airport to the database.</li>

# <li value="4"> User
This is use for holdings and fix that are create by the user.</li>

[img database design]

The plan improvements that i have for sim424 and the xp10 database that we
current use is that we get support for example support for Airspace and Air
Traffic Control areas outside airport airspace.
And more data to simulate navigation beacons more accurate than the current
model(see also Next Navigation and Virtual Ether).

==Next Navigation==

The Next navigation project is the to refactor the navigation subsysteems and
include new navigation modes as fully simulate global navigation satellite
system (GNSS) as GOS/Navstar and Glonass systems and older systems like Omega,
LORAN and Low-frequency radio range.

==Virtual Ether==
Virtual Ether project is a continue of the Next Navigation project with the
focuse to crate mathematical models for simulate radio transmission and audio
artifacts.
This is spesial for simulate voice commulication over HF freqentions.

==Road Map==

===Project Sim424===
Database specification {{progressbar|10}} 
Tools {{progressbar|0}} 

===Next Navigation===
Non-directional beacons {{progressbar|0}} 
VHF omnidirectional range/TACAN {{progressbar|0}} 
ILS {{progressbar|0}} 
MLS {{progressbar|0}} 
GPS {{progressbar|0}} 
GBAS/GLS {{progressbar|0}} 
===Virtual Ether===

==FAQ==

User:Www2/Sim424

2021-05-03T01:45:50Z

Www2:

=Introduction=

Current flightgear use a outdate navigation database.
This is not bad due to the license.
The other side of the coin is that we are frozen in time (around September/October 2013) with the navigation database.

A other problem is that that we have no SID, STAR and arrival procedure that is connect to the navaids database.
The rest of the documents describe my view and roadmap to improve this.

=Project=
==Project sim424==

The first part of this project is creating a new database format base on sqlite.
The dataset is split in five parts: GPL, Navigraph(as a replasment of the GPL database, Community, add-ons scenery, and user datasets:

GPL dataset
The classic database is the current navigation database that we using in flightgear convert to the new format.

# Navigraph dataset
This is a optional database with the data source from navigraph that add things as SID, STAR, airways (e.g. trans alantic Concorde Routes), on route ATC and more.
This is release as a optional dataset that the user need to download from the site or as a optional package from the Linux distribution.

# <li value="2"> Community add-on dataset
The community database is the a add-on database for Navigraph or GPL
datasets to add data for close airports (Berlin Tempelhof Airport,
Meigs Field and Kai Tak Hong Kong (This one is include navigraph)) and navigation as Concorde Tracks and provide data for older navigation systems as Low-frequency radio range[1] and LORAN.</li>

# <li value="3"> Add-ons 
This are patches that makes of add-ons scenery's can make to the datasets describe here above as fixing or adding navaids and airport to the database.</li>

# <li value="4"> User
This is use for holdings and fix that are create by the user.</li>

[img database design]

The plan improvements that i have for sim424 and the xp10 database that we
current use is that we get support for example support for Airspace and Air
Traffic Control areas outside airport airspace.
And more data to simulate navigation beacons more accurate than the current
model(see also Next Navigation and Virtual Ether).

==Next Navigation==

The Next navigation project is the to refactor the navigation subsysteems and
include new navigation modes as fully simulate global navigation satellite
system (GNSS) as GOS/Navstar and Glonass systems and older systems like Omega,
LORAN and Low-frequency radio range.

==Virtual Ether==
Virtual Ether project is a continue of the Next Navigation project with the
focuse to crate mathematical models for simulate radio transmission and audio
artifacts.
This is spesial for simulate voice commulication over HF freqentions.

==Road Map==

===Project Sim424===
Database specification {{progressbar|0}}
Tools
===Next Navigation===

===Virtual Ether===

==FAQ==

User:Www2/Sim424

2021-04-28T16:15:08Z

Www2: New project whitepaper

=Introduction=

Current flightgear use a outdate navigation database.
This is not bad due to the license.
The other side of the coin is that we are frozen in time (around September/October 2013) with the navigation database.

A other problem is that that we have no SID, STAR and arrival procedure that is connect to the navaids database.
The rest of the documents describe my view and roadmap to improve this.

=Project=
==Project sim424==

The first part of this project is creating a new database format base on sqlite.
The dataset is split in five parts: GPL, Navigraph(as a replasment of the GPL database, Community, add-ons scenery, and user datasets:

GPL dataset
The classic database is the current navigation database that we using in flightgear convert to the new format.

# Navigraph dataset
This is a optional database with the data source from navigraph that add things as sid, stars, airways, on route ATC and more.
This is release as a optional dataset that the user need to download from the site or as a optional package from the Linux distribution.

# <li value="2"> Community add-on dataset
The community database is the a add-on database for Navigraph or GPL
datasets to add data for close airports (Berlin Tempelhof Airport,
Meigs Field and Kai Tak Hong Kong (This one is include navigraph)) and navigation as Concorde Tracks and provide data for older navigation systems as Low-frequency radio range[1] and LORAN.</li>

# <li value="3"> Add-ons 
This are patches that makes of add-ons scenery's can make to the datasets describe here above as fixing or adding navaids and airport to the database.</li>

# <li value="4"> User
This is use for holdings and fix that are create by the user.</li>

[img database design]

The plan improvements that i have for sim424 and the xp10 database that we
current use is that we get support for example support for Airspace and Air
Traffic Control areas outside airport airspace.
And more data to simulate navigation beacons more accurate than the current
model(see also Next Navigation and Virtual Ether).

==Next Navigation==

The Next navigation project is the to refactor the navigation subsysteems and
include new navigation modes as fully simulate global navigation satellite
system (GNSS) as GOS/Navstar and Glonass systems and older systems like Omega,
LORAN and Low-frequency radio range.

==Virtual Ether==
Virtual Ether project is a continue of the Next Navigation project with the
focuse to crate mathematical models for simulate radio transmission and audio
artifacts.
This is spesial for simulate voice commulication over HF freqentions.

User:Www2

2021-04-28T01:51:14Z

Www2:

project sim424 [[User:www2/Sim424]]

-----
FG python docs
[[User:www2/fgpython]]
X-Plane 11 Data Specification [[User:www2/XP11 Data Specification]] 
X-plane Object libary [[User:www2/XP11 object libary]] 
Little Nav Map Database Specification [[User:www2/Little Nav Map/Database]] 
Proposal advancedProtocol [[User:www2/Advanced Protocol]] 
Property tree [[User:www2/Property]]

User:Www2/Property/instrumentation/comm

2020-09-30T11:02:12Z

Www2: put informat data

add-noise bool 
airport-id string 
atis string 
cutoff-signal-quality double 
(+) frequencies array 
height-above-station-ft double 
operable bool 
power-btn bool 
serviceable bool 
signal-quality-norm double 
slant-distance-m double 
station-name string 
station-type string 
track-distance-m double 
true-bearing-from-deg double 
true-bearing-to-deg double 
volume double 
volume-selected double 
 
 
 
selected-channel int 
selected-channel-width-khz double 
selected-mhz double 
selected-mhz-fmt string 
selected-real-frequency-mhz double 
standby-channel int 
standby-channel-width-khz double 
standby-mhz double 
standby-mhz-fmt string 
standby-real-frequency-mhz double

User:Www2/Property

2020-09-28T00:13:02Z

Www2:

Current the Property tree nodes are undocumented

==instrumentation==
===Radio===
[[User:www2/Property/instrumentation/comm|comm]] 
[[User:www2/Property/instrumentation/nav|nav(vor/ils)]] 
[[User:www2/Property/instrumentation/adf|adf(ndb)]] 
[[User:www2/Property/instrumentation/tcan|TCAN]] 
[[User:www2/Property/instrumentation/transponder|Transponder]]

User:Www2/Property

2020-09-27T22:48:47Z

Www2: Created page with "Current the Property tree nodes are undocumented ==instrumentation== ===Radio== comm User:www2/Property/instrumentation/nav|..."

Current the Property tree nodes are undocumented

==instrumentation==
===Radio==
[[User:www2/Property/instrumentation/comm|comm]] 
[[User:www2/Property/instrumentation/nav|nav(vor/ils)]] 
[[User:www2/Property/instrumentation/adf|adf(ndb)]] 
[[User:www2/Property/instrumentation/tcan|TCAN]] 
[[User:www2/Property/instrumentation/transponder|Transponder]]

User:Www2

2020-09-27T21:19:41Z

Www2:

FG python docs
[[User:www2/fgpython]]

X-Plane 11 Data Specification [[User:www2/XP11 Data Specification]] 
X-plane Object libary [[User:www2/XP11 object libary]] 
Little Nav Map Database Specification [[User:www2/Little Nav Map/Database]] 
Proposal advancedProtocol [[User:www2/Advanced Protocol]] 
Property tree [[User:www2/Property]]

User:Www2

2020-09-27T21:19:04Z

Www2:

User:Www2

2020-09-27T21:18:53Z

Www2:

User:Www2/XP11 Data Specification

2020-08-23T22:30:44Z

Www2:

== APT ==
[[User:www2/apt.dat]]

== FIX ==

Waypoint type:

ENROUTE WAYPOINT
{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| Combined Named Intersection and RNAV || C || ||
|-
| Unnamed, Charted Intersection || I || ||
|-
| NDB Navaid as Waypoin || N || [1] || [2]
|-
| Named Intersection || R || ||
|-
| VFR Waypoint || V || [4] ||
|-
| RNAV Waypoint || W || ||
|-
| Final Approach Fix || || A ||
|-
| Initial and Final Approach Fix || || B ||
|-
| Final Approach Course Fix || || C ||
|-
| Intermediate Approach Fix || || D ||
|-
| Off-Route intersection in the FAA National Reference System || || E ||
|-
| Off-Route Intersection || || F ||
|-
| Initial Approach Fix || || I ||
|-
| Final Approach Course Fix at Initial Approach Fix || || K ||
|-
| Final Approach Course Fix at Intermediate Approach Fix || || L ||
|-
| Missed Approach Fix || || M ||
|-
| Initial Approach Fix and Missed Approach Fix || || N ||
|-
| Oceanic Entry/Exit Waypoint || || O ||
|-
| Pitch and Catch Point in the FAA High Altitude Redesign || || P ||
|-
| AACAA and SUA Waypoints in the FAA High Altitude Redesign || || S ||
|-
| FIR/UIR or Controlled Airspace Intersection || || U ||
|-
| Latitude/Longitude Intersection, Full Degree of Latitude || || V ||
|-
| Latitude/Longitude Intersection, Half Degree of Latitude || || W ||
|}

TERMINAL WAYPOINT

{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| ARC Center Fix Waypoint || A || [3] || [3]
|-
| Combined Named Intersection and RNAV || C || ||
|-
| Unnamed, Charted Intersection || I || ||
|-
| Middle Marker as Waypoint || M || ||
|-
| NDB Navaid as Waypoin || N || [1] || [2]
|-
| Outer Marker as Waypoint || O || ||
|-
| Named Intersection || R || ||
|-
| VFR Waypoint || V || [4] ||
|-
| RNAV Waypoint || W || ||
|-
| Final Approach Fix || || A ||
|-
| Initial and Final Approach Fix || || B ||
|-
| Final Approach Course Fix || || C ||
|-
| Intermediate Approach Fix || || D ||
|-
| Initial Approach Fix || || I ||
|-
| Final Approach Course Fix at Initial Approach Fix || || K ||
|-
| Final Approach Course Fix at Intermediate Approach Fix || || L ||
|-
| Missed Approach Fix || || M ||
|-
| Initial Approach Fix and Missed Approach Fix || || N ||
|-
| Unnamed Stepdown Fix || || P ||
|-
| AACAA and SUA Waypoints in the FAA High Altitude Redesign || || S ||
|-
| Named Stepdown Fix || || U ||
|}

ENROUTE AND TERMINAL WAYPOINT
{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| SID || || || D
|-
| STAR || || || E
|-
| Approach || || || F
|-
| Multiple || || || Z
|}
[1] Column 28 of the Enroute and Terminal
Waypoint Types will always be blank when
column 27 carries the “N” for NDB or Terminal
NDB produced as Waypoints.
[2] Possible codes for column 29 are identical for
both Enroute and Terminal Waypoints and are
those carried in the third portion of the table.
Column 29 will always be blank when column
27 carries the “N” for NDB or Terminal NDB
produced as Waypoints.
[3] When column 27 equals “A” for ARC Center
Fix Waypoint, columns 28 and 29 will always
be blank.
[4] The code V in column 27 for VFR Waypoints is
not used in conjunction with any codes from
column 28 and 29.

== NAV ==

== CIFP ==
=== SID/STAR/APPCH ===
{| class="wikitable"
|-
! Collem !! Field !! Reference !! Name !! Length
|-
| 1 || 4.1.9.1.27-29 || 5.12 || header and Sequence Number ||
|-
| 2 || 4.1.9.1.20 || 5.7 || Route Type ||
|-
| 3 || 4.1.9.1.14-19 || 5.9&5.10 || SID/STAR/APPROACH Route Identifier ||
|-
| 4 || 4.1.9.1.21-25 || 5.11 || Transition Identifier ||
|-
| 5 || 4.1.9.1.30-34 || 5.13 || Fix Identifier ||
|-
| 6 || 4.1.9.1.35-36 || 5.14 || ICAO Code ||
|-
| 7 || 4.1.9.1.37 || 5.4 || Section Code ||
|-
| 8 || 4.1.9.1.38 || 5.5 || Subsection Code ||
|-
| 9 || 4.1.9.1.40-43 || 5.17 || Waypoint Description Code ||
|-
| 10 || 4.1.9.1.44 || 5.20 || True Direction Valid ||
|-
| 11 || 4.1.9.1.45-47 || 5.211 || RNP ||
|-
| 12 || 4.1.9.1.48-49 || 5.21 || Path And Termination ||
|-
| 13 || 4.1.9.1.50 || 5.22 || Turn Direction Valid ||
|-
| 14 || 4.1.9.1.51-54 || 5.23 || Recommended Navaid ||
|-
| 15 || 4.1.9.1.55-56 || 5.14 || ICAO Code ||
|-
| 16 || 4.1.9.1.79 || 5.4 || RECD NAV Section ||
|-
| 17 || 4.1.9.1.80 || 5.5 || RECD NAV Subsection ||
|-
| 18 || 4.1.9.1.57-62 || 5.204 || Arc Radius ||
|-
| 19 || 4.1.9.1.63-66 || 5.24 || Theta ||
|-
| 20 || 4.1.9.1.67-70 || 5.25 || Rho ||
|-
| 21 || 4.1.9.1.71-74 || 5.26 || Magnetic Course ||
|-
| 22 || 4.1.9.1.75-78 || 5.27 || Route Distance/Holding Distance or time ||
|-
| 23 || 4.1.9.1.83 || 5.29 || Altitude Description ||
|-
| 24 || 4.1.9.1.85-89 || 5.30 || Altitude ||
|-
| 25 || 4.1.9.1.90-94 || 5,3 || Altitude ||
|-
| 26 || 4.1.9.1.95-99 || 5.53 || Transition Altitude ||
|-
| 27 || 4.1.9.1.118 || 5261 || Speed Limit Description ||
|-
| 28 || 4.1.9.1.100-102 || 5.72 || Speed Limit ||
|-
| 29 || 4.1.9.1.103-106 || 5.70 || Vertical Angle ||
|-
| 30 || 4.1.9.1.121-123 || 5.293 || TBA ||
|-
| 31 || 4.1.9.1.107-111 || 5.144/5.271 || Center Fix or TAA Procedure Turn ||
|-
| 32 || 4.1.9.1.113-114 || 5.14 || ICAO Code ||
|-
| 33 || 4.1.9.1.115 || 5.4 || Section Code ||
|-
| 34 || 4.1.9.1.116 || 5.5 || Subsection Code ||
|-
| 35 || 4.1.9.1.112 || 5.130/5.272 || Multiple Code or TAA Sector Identifier ||
|-
| 36 || 4.1.9.1.117 || 5.222 || GPS/FMS Indication ||
|-
| 37 || 4,1.9.1.119 || 5.7 || Apch Route Qualifier 1 ||
|-
| 38 || 4.1.9.1.120 || 5.7 || Apch Route Qualifier 2 ||
|}

=== RWY ===
<code>
RWY:RW13 ,+0200, ,00001, ,FOO ,1, ;N22191800,E114114600,134;
</code>

{| class="wikitable"
|-
! Collem !! Field !! Reference !! Name !! Length
|-
| 1 || 4.1.10.1.14-18 || 5.46 || Runway ID || 5
|-
| 2 || 4.1.10.1.52-56 || 5.212 || Runway Gradient || 5
|-
| 3 || 4.1.10.1.61-66 || 5.225 || Ellipsoidal Height || 6
|-
| 4 || 4.1.10.1.76-71 || 5.68 || Threshold Crossing Height || 5
|-
| 5 || 4.1.10.1.81 || 5.270 || TCH Value Indicator || 1
|-
| 6 || 4.1.10.1.82-85 || 5.44 || Localizer/MLS/GLS Identifier || 4 max
|-
| 7 || 4.1.10.1.86 || 5.80 || ILS/MLS/GLS Category || 1
|-
| 8 || 4.1.10.1.96-98 || 5.67 || Threshold Crossing Height || 3
|-
| 9 || 4.1.10.1.33-41 || 5.36 || Runway Latitude || 9
|-
| 10 || 4.1.10.1.42-51 || 5.37 || Runway Longitude || 10
|-
| 11 || 4.1.10.1.72-75 || 5.69 || Displaced Threshold Distance || 4
|}

Table rwnILSmode:
{| class="wikitable"
|-
! Mode !! info
|-
| <blank> || No ILS for the runway
|-
| 0 || LOC
|-
| 1 || ILS CAT I
|-
| 2 || ILS CAT II
|-
| 3 || ILS CAT III
|-
| L || LDA with Glideslope
|-
| A || LDA, No Glideslope
|-
| S || SDF with Glideslope
|-
| F || SDF, No Glideslope
|-
| I || IGS
|}

=== PRDAT ===
TBA

== Examples ==

== Apendix ==

User:Www2/apt.dat

2020-08-21T09:00:34Z

Www2: Delete the cleanup tag this are only some notes that i have made about the apt.dat lines.

==Painted lines==
{| class="wikitable"
|-
! Line Type Code !! Painted lines !!
|-
| 0 || Nothing. ||
|-
| 1 || Solid yellow line ||
|-
| 2 || Broken yellow line ||
|-
| 3 || Broken yellow line ||
|-
| 4 || Two broken yellow lines and two solid yellow lines. Broken line on left of string. ||
|-
| 5 || Broken yellow line with parallel solid yellow line. Broken line on left of string. ||
|-
| 6 || Yellow cross-hatched line. ||
|-
| 7 || Solid yellow line with broken yellow line on each side. ||
|-
| 8 || Widely separated, broken yellow line. ||
|-
| 9 || Widely separated, broken double yellow line. ||
|-
| 51-59 || Line types 1-9 above with a black border. ||
|-
| Wide markings
|-
| 10 || Single Taxi Wide. ||
|-
| 11 || Taxi Hold Wide. ||
|-
| 12 || Double Taxi Hold Wide. ||
|-
| 13 || Other Hold Wide. ||
|-
| 14 || ILS Hold Wide. ||
|-
| 60-64 || Line types 10-14 above with a black border. ||
|-
| Road markings
|-
| 20 || Solid white line ||
|-
| 21 || White chequerboard pattern ||
|-
| 22 || Broken white line ||
|-
| 23 || Road Dash ||
|-
| 24 || Road Edge Wide ||
|-
| 25 || Road Dash Wide ||
|-
| 70-75 || Line types 20-25 above with a black border. ||
|-
| Other markings
|-
| 30 || Red line ||
|-
| 31 || Red Dash Line ||
|-
| 80-81 || Line types 30-31 above with a black border. ||
|-
| 40 || Orange Line ||
|-
| 41 || Blue Line ||
|-
| 42 || Green Line ||
|-
| 90-92 || Line types 40-42 above with a black border. ||
|-
|}

User:Www2/Advanced Protocol

2019-06-15T22:29:29Z

Www2: /* file layout */

'''<big>proposal</big>''' 

The advanced communication protocall for FlightGear provides a more powerful
way than generic communication protocol of adding ASCII base or binary
input/output ptorocall for socket, websockets, Sireal or USB communication,
just by defining an XML encoded configuration file and placing it in the
$FG_ROOT/Protocol/Advaneds or $FG_AIRCRAFT/Protocol directory.

== file layout ==
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<PropertyList>
<advancedProtocol>
<setup>
<type></type>
<endian></endian>
<line_separator></line_separator>
<var_separator></var_separator>
</setup>

<statemachine>
<state>
... first state spec ...
</state>

<state>
... another state etc. ...
</state>
</statemachine>

<periodic>
<block>
... First block spec. ...
</block>
<block>
... another block etc. ...
</block>
</periodic>

</advancedProtocol>
</PropertyList>
</syntaxhighlight>

<syntaxhighlight lang="xml">
</syntaxhighlight>

User:Www2/Advanced Protocol

2019-06-10T03:17:23Z

Www2: Created page with "'''<big>proposal</big>''' The advanced communication protocall for FlightGear provides a more powerful way than generic communication p..."

'''<big>proposal</big>''' 

The advanced communication protocall for FlightGear provides a more powerful
way than generic communication protocol of adding ASCII base or binary
input/output ptorocall for socket, websockets, Sireal or USB communication,
just by defining an XML encoded configuration file and placing it in the
$FG_ROOT/Protocol/Advaneds or $FG_AIRCRAFT/Protocol directory.

== file layout ==
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<PropertyList>
<advancedProtocol>
<setup>
<type></type>
<endian></endian>
<line_separator></line_separator>
<var_separator></var_separator>
</setup>

<statemachine>
<state>
... first state spec ...
</state>

<state>
... another state etc. ...
</state>
</stateMachine>

<periodic>
<block>
... First block spec. ...
</block>
<block>
... another block etc. ...
</block>
</periodic>

</advancedProtocol>
</PropertyList>
</syntaxhighlight>

<syntaxhighlight lang="xml">
</syntaxhighlight>

User:Www2

2019-06-10T02:06:06Z

Www2:

User:Www2

2019-06-10T02:05:51Z

Www2:

FG python docs
[[User:www2/fgpython]]

X-Plane 11 Data Specification [[User:www2/XP11 Data Specification]] 
X-plane Object libary [[User:www2/XP11 object libary]] 
Little Nav Map Database Specification [[User:www2/Little Nav Map/Database]]
Proposal advancedProtocol [[User:www2/Advanced Protocol]]

User:Www2

2018-12-25T18:48:41Z

Www2:

User:Www2/apt.dat

2018-12-21T00:56:56Z

Www2: Make a list of current X-Plane Markings types

User:Www2/XP11 Data Specification

2018-12-21T00:25:03Z

Www2: /* APT */

== APT ==
[[www2/apt.dat]]

== FIX ==

Waypoint type:

ENROUTE WAYPOINT
{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| Combined Named Intersection and RNAV || C || ||
|-
| Unnamed, Charted Intersection || I || ||
|-
| NDB Navaid as Waypoin || N || [1] || [2]
|-
| Named Intersection || R || ||
|-
| VFR Waypoint || V || [4] ||
|-
| RNAV Waypoint || W || ||
|-
| Final Approach Fix || || A ||
|-
| Initial and Final Approach Fix || || B ||
|-
| Final Approach Course Fix || || C ||
|-
| Intermediate Approach Fix || || D ||
|-
| Off-Route intersection in the FAA National Reference System || || E ||
|-
| Off-Route Intersection || || F ||
|-
| Initial Approach Fix || || I ||
|-
| Final Approach Course Fix at Initial Approach Fix || || K ||
|-
| Final Approach Course Fix at Intermediate Approach Fix || || L ||
|-
| Missed Approach Fix || || M ||
|-
| Initial Approach Fix and Missed Approach Fix || || N ||
|-
| Oceanic Entry/Exit Waypoint || || O ||
|-
| Pitch and Catch Point in the FAA High Altitude Redesign || || P ||
|-
| AACAA and SUA Waypoints in the FAA High Altitude Redesign || || S ||
|-
| FIR/UIR or Controlled Airspace Intersection || || U ||
|-
| Latitude/Longitude Intersection, Full Degree of Latitude || || V ||
|-
| Latitude/Longitude Intersection, Half Degree of Latitude || || W ||
|}

TERMINAL WAYPOINT

{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| ARC Center Fix Waypoint || A || [3] || [3]
|-
| Combined Named Intersection and RNAV || C || ||
|-
| Unnamed, Charted Intersection || I || ||
|-
| Middle Marker as Waypoint || M || ||
|-
| NDB Navaid as Waypoin || N || [1] || [2]
|-
| Outer Marker as Waypoint || O || ||
|-
| Named Intersection || R || ||
|-
| VFR Waypoint || V || [4] ||
|-
| RNAV Waypoint || W || ||
|-
| Final Approach Fix || || A ||
|-
| Initial and Final Approach Fix || || B ||
|-
| Final Approach Course Fix || || C ||
|-
| Intermediate Approach Fix || || D ||
|-
| Initial Approach Fix || || I ||
|-
| Final Approach Course Fix at Initial Approach Fix || || K ||
|-
| Final Approach Course Fix at Intermediate Approach Fix || || L ||
|-
| Missed Approach Fix || || M ||
|-
| Initial Approach Fix and Missed Approach Fix || || N ||
|-
| Unnamed Stepdown Fix || || P ||
|-
| AACAA and SUA Waypoints in the FAA High Altitude Redesign || || S ||
|-
| Named Stepdown Fix || || U ||
|}

ENROUTE AND TERMINAL WAYPOINT
{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| SID || || || D
|-
| STAR || || || E
|-
| Approach || || || F
|-
| Multiple || || || Z
|}
[1] Column 28 of the Enroute and Terminal
Waypoint Types will always be blank when
column 27 carries the “N” for NDB or Terminal
NDB produced as Waypoints.
[2] Possible codes for column 29 are identical for
both Enroute and Terminal Waypoints and are
those carried in the third portion of the table.
Column 29 will always be blank when column
27 carries the “N” for NDB or Terminal NDB
produced as Waypoints.
[3] When column 27 equals “A” for ARC Center
Fix Waypoint, columns 28 and 29 will always
be blank.
[4] The code V in column 27 for VFR Waypoints is
not used in conjunction with any codes from
column 28 and 29.

== NAV ==

== CIFP ==
=== SID/STAR/APPCH ===
{| class="wikitable"
|-
! Collem !! Field !! Reference !! Name !! Length
|-
| 1 || 4.1.9.1.27-29 || 5.12 || header and Sequence Number ||
|-
| 2 || 4.1.9.1.20 || 5.7 || Route Type ||
|-
| 3 || 4.1.9.1.14-19 || 5.9&5.10 || SID/STAR/APPROACH Route Identifier ||
|-
| 4 || 4.1.9.1.21-25 || 5.11 || Transition Identifier ||
|-
| 5 || 4.1.9.1.30-34 || 5.13 || Fix Identifier ||
|-
| 6 || 4.1.9.1.35-36 || 5.14 || ICAO Code ||
|-
| 7 || 4.1.9.1.37 || 5.4 || Section Code ||
|-
| 8 || 4.1.9.1.38 || 5.5 || Subsection Code ||
|-
| 9 || 4.1.9.1.40-43 || 5.17 || Waypoint Description Code ||
|-
| 10 || 4.1.9.1.44 || 5.20 || True Direction Valid ||
|-
| 11 || 4.1.9.1.45-47 || 5.211 || RNP ||
|-
| 12 || 4.1.9.1.48-49 || 5.21 || Path And Termination ||
|-
| 13 || 4.1.9.1.50 || 5.22 || Turn Direction Valid ||
|-
| 14 || 4.1.9.1.51-54 || 5.23 || Recommended Navaid ||
|-
| 15 || 4.1.9.1.55-56 || 5.14 || ICAO Code ||
|-
| 16 || 4.1.9.1.79 || 5.4 || RECD NAV Section ||
|-
| 17 || 4.1.9.1.80 || 5.5 || RECD NAV Subsection ||
|-
| 18 || 4.1.9.1.57-62 || 5.204 || Arc Radius ||
|-
| 19 || 4.1.9.1.63-66 || 5.24 || Theta ||
|-
| 20 || 4.1.9.1.67-70 || 5.25 || Rho ||
|-
| 21 || 4.1.9.1.71-74 || 5.26 || Magnetic Course ||
|-
| 22 || 4.1.9.1.75-78 || 5.27 || Route Distance/Holding Distance or time ||
|-
| 23 || 4.1.9.1.83 || 5.29 || Altitude Description ||
|-
| 24 || 4.1.9.1.85-89 || 5.30 || Altitude ||
|-
| 25 || 4.1.9.1.90-94 || 5,3 || Altitude ||
|-
| 26 || 4.1.9.1.95-99 || 5.53 || Transition Altitude ||
|-
| 27 || 4.1.9.1.118 || 5261 || Speed Limit Description ||
|-
| 28 || 4.1.9.1.100-102 || 5.72 || Speed Limit ||
|-
| 29 || 4.1.9.1.103-106 || 5.70 || Vertical Angle ||
|-
| 30 || 4.1.9.1.121-123 || 5.293 || TBA ||
|-
| 31 || 4.1.9.1.107-111 || 5.144/5.271 || Center Fix or TAA Procedure Turn ||
|-
| 32 || 4.1.9.1.113-114 || 5.14 || ICAO Code ||
|-
| 33 || 4.1.9.1.115 || 5.4 || Section Code ||
|-
| 34 || 4.1.9.1.116 || 5.5 || Subsection Code ||
|-
| 35 || 4.1.9.1.112 || 5.130/5.272 || Multiple Code or TAA Sector Identifier ||
|-
| 36 || 4.1.9.1.117 || 5.222 || GPS/FMS Indication ||
|-
| 37 || 4,1.9.1.119 || 5.7 || Apch Route Qualifier 1 ||
|-
| 38 || 4.1.9.1.120 || 5.7 || Apch Route Qualifier 2 ||
|}

=== RWY ===
<code>
RWY:RW13 ,+0200, ,00001, ,FOO ,1, ;N22191800,E114114600,134;
</code>

{| class="wikitable"
|-
! Collem !! Field !! Reference !! Name !! Length
|-
| 1 || 4.1.10.1.14-18 || 5.46 || Runway ID || 5
|-
| 2 || 4.1.10.1.52-56 || 5.212 || Runway Gradient || 5
|-
| 3 || 4.1.10.1.61-66 || 5.225 || Ellipsoidal Height || 6
|-
| 4 || 4.1.10.1.76-71 || 5.68 || Threshold Crossing Height || 5
|-
| 5 || 4.1.10.1.81 || 5.270 || TCH Value Indicator || 1
|-
| 6 || 4.1.10.1.82-85 || 5.44 || Localizer/MLS/GLS Identifier || 4 max
|-
| 7 || 4.1.10.1.86 || 5.80 || ILS/MLS/GLS Category || 1
|-
| 8 || 4.1.10.1.96-98 || 5.67 || Threshold Crossing Height || 3
|-
| 9 || 4.1.10.1.33-41 || 5.36 || Runway Latitude || 9
|-
| 10 || 4.1.10.1.42-51 || 5.37 || Runway Longitude || 10
|-
| 11 || 4.1.10.1.72-75 || 5.69 || Displaced Threshold Distance || 4
|}

Table rwnILSmode:
{| class="wikitable"
|-
! Mode !! info
|-
| <blank> || No ILS for the runway
|-
| 0 || LOC
|-
| 1 || ILS CAT I
|-
| 2 || ILS CAT II
|-
| 3 || ILS CAT III
|-
| L || LDA with Glideslope
|-
| A || LDA, No Glideslope
|-
| S || SDF with Glideslope
|-
| F || SDF, No Glideslope
|-
| I || IGS
|}

=== PRDAT ===
TBA

== Examples ==

== Apendix ==

User:Www2/XP11 Data Specification

2018-11-10T03:09:01Z

Www2: /* FIX */

== APT ==

== FIX ==

Waypoint type:

ENROUTE WAYPOINT
{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| Combined Named Intersection and RNAV || C || ||
|-
| Unnamed, Charted Intersection || I || ||
|-
| NDB Navaid as Waypoin || N || [1] || [2]
|-
| Named Intersection || R || ||
|-
| VFR Waypoint || V || [4] ||
|-
| RNAV Waypoint || W || ||
|-
| Final Approach Fix || || A ||
|-
| Initial and Final Approach Fix || || B ||
|-
| Final Approach Course Fix || || C ||
|-
| Intermediate Approach Fix || || D ||
|-
| Off-Route intersection in the FAA National Reference System || || E ||
|-
| Off-Route Intersection || || F ||
|-
| Initial Approach Fix || || I ||
|-
| Final Approach Course Fix at Initial Approach Fix || || K ||
|-
| Final Approach Course Fix at Intermediate Approach Fix || || L ||
|-
| Missed Approach Fix || || M ||
|-
| Initial Approach Fix and Missed Approach Fix || || N ||
|-
| Oceanic Entry/Exit Waypoint || || O ||
|-
| Pitch and Catch Point in the FAA High Altitude Redesign || || P ||
|-
| AACAA and SUA Waypoints in the FAA High Altitude Redesign || || S ||
|-
| FIR/UIR or Controlled Airspace Intersection || || U ||
|-
| Latitude/Longitude Intersection, Full Degree of Latitude || || V ||
|-
| Latitude/Longitude Intersection, Half Degree of Latitude || || W ||
|}

TERMINAL WAYPOINT

{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| ARC Center Fix Waypoint || A || [3] || [3]
|-
| Combined Named Intersection and RNAV || C || ||
|-
| Unnamed, Charted Intersection || I || ||
|-
| Middle Marker as Waypoint || M || ||
|-
| NDB Navaid as Waypoin || N || [1] || [2]
|-
| Outer Marker as Waypoint || O || ||
|-
| Named Intersection || R || ||
|-
| VFR Waypoint || V || [4] ||
|-
| RNAV Waypoint || W || ||
|-
| Final Approach Fix || || A ||
|-
| Initial and Final Approach Fix || || B ||
|-
| Final Approach Course Fix || || C ||
|-
| Intermediate Approach Fix || || D ||
|-
| Initial Approach Fix || || I ||
|-
| Final Approach Course Fix at Initial Approach Fix || || K ||
|-
| Final Approach Course Fix at Intermediate Approach Fix || || L ||
|-
| Missed Approach Fix || || M ||
|-
| Initial Approach Fix and Missed Approach Fix || || N ||
|-
| Unnamed Stepdown Fix || || P ||
|-
| AACAA and SUA Waypoints in the FAA High Altitude Redesign || || S ||
|-
| Named Stepdown Fix || || U ||
|}

ENROUTE AND TERMINAL WAYPOINT
{| class="wikitable"
|-
! Waypoint type !! Col 27 !! Col 28 !! Col 29
|-
| SID || || || D
|-
| STAR || || || E
|-
| Approach || || || F
|-
| Multiple || || || Z
|}
[1] Column 28 of the Enroute and Terminal
Waypoint Types will always be blank when
column 27 carries the “N” for NDB or Terminal
NDB produced as Waypoints.
[2] Possible codes for column 29 are identical for
both Enroute and Terminal Waypoints and are
those carried in the third portion of the table.
Column 29 will always be blank when column
27 carries the “N” for NDB or Terminal NDB
produced as Waypoints.
[3] When column 27 equals “A” for ARC Center
Fix Waypoint, columns 28 and 29 will always
be blank.
[4] The code V in column 27 for VFR Waypoints is
not used in conjunction with any codes from
column 28 and 29.

== NAV ==

== CIFP ==
=== SID/STAR/APPCH ===
{| class="wikitable"
|-
! Collem !! Field !! Reference !! Name !! Length
|-
| 1 || 4.1.9.1.27-29 || 5.12 || header and Sequence Number ||
|-
| 2 || 4.1.9.1.20 || 5.7 || Route Type ||
|-
| 3 || 4.1.9.1.14-19 || 5.9&5.10 || SID/STAR/APPROACH Route Identifier ||
|-
| 4 || 4.1.9.1.21-25 || 5.11 || Transition Identifier ||
|-
| 5 || 4.1.9.1.30-34 || 5.13 || Fix Identifier ||
|-
| 6 || 4.1.9.1.35-36 || 5.14 || ICAO Code ||
|-
| 7 || 4.1.9.1.37 || 5.4 || Section Code ||
|-
| 8 || 4.1.9.1.38 || 5.5 || Subsection Code ||
|-
| 9 || 4.1.9.1.40-43 || 5.17 || Waypoint Description Code ||
|-
| 10 || 4.1.9.1.44 || 5.20 || True Direction Valid ||
|-
| 11 || 4.1.9.1.45-47 || 5.211 || RNP ||
|-
| 12 || 4.1.9.1.48-49 || 5.21 || Path And Termination ||
|-
| 13 || 4.1.9.1.50 || 5.22 || Turn Direction Valid ||
|-
| 14 || 4.1.9.1.51-54 || 5.23 || Recommended Navaid ||
|-
| 15 || 4.1.9.1.55-56 || 5.14 || ICAO Code ||
|-
| 16 || 4.1.9.1.79 || 5.4 || RECD NAV Section ||
|-
| 17 || 4.1.9.1.80 || 5.5 || RECD NAV Subsection ||
|-
| 18 || 4.1.9.1.57-62 || 5.204 || Arc Radius ||
|-
| 19 || 4.1.9.1.63-66 || 5.24 || Theta ||
|-
| 20 || 4.1.9.1.67-70 || 5.25 || Rho ||
|-
| 21 || 4.1.9.1.71-74 || 5.26 || Magnetic Course ||
|-
| 22 || 4.1.9.1.75-78 || 5.27 || Route Distance/Holding Distance or time ||
|-
| 23 || 4.1.9.1.83 || 5.29 || Altitude Description ||
|-
| 24 || 4.1.9.1.85-89 || 5.30 || Altitude ||
|-
| 25 || 4.1.9.1.90-94 || 5,3 || Altitude ||
|-
| 26 || 4.1.9.1.95-99 || 5.53 || Transition Altitude ||
|-
| 27 || 4.1.9.1.118 || 5261 || Speed Limit Description ||
|-
| 28 || 4.1.9.1.100-102 || 5.72 || Speed Limit ||
|-
| 29 || 4.1.9.1.103-106 || 5.70 || Vertical Angle ||
|-
| 30 || 4.1.9.1.121-123 || 5.293 || TBA ||
|-
| 31 || 4.1.9.1.107-111 || 5.144/5.271 || Center Fix or TAA Procedure Turn ||
|-
| 32 || 4.1.9.1.113-114 || 5.14 || ICAO Code ||
|-
| 33 || 4.1.9.1.115 || 5.4 || Section Code ||
|-
| 34 || 4.1.9.1.116 || 5.5 || Subsection Code ||
|-
| 35 || 4.1.9.1.112 || 5.130/5.272 || Multiple Code or TAA Sector Identifier ||
|-
| 36 || 4.1.9.1.117 || 5.222 || GPS/FMS Indication ||
|-
| 37 || 4,1.9.1.119 || 5.7 || Apch Route Qualifier 1 ||
|-
| 38 || 4.1.9.1.120 || 5.7 || Apch Route Qualifier 2 ||
|}

=== RWY ===
<code>
RWY:RW13 ,+0200, ,00001, ,FOO ,1, ;N22191800,E114114600,134;
</code>

{| class="wikitable"
|-
! Collem !! Field !! Reference !! Name !! Length
|-
| 1 || 4.1.10.1.14-18 || 5.46 || Runway ID || 5
|-
| 2 || 4.1.10.1.52-56 || 5.212 || Runway Gradient || 5
|-
| 3 || 4.1.10.1.61-66 || 5.225 || Ellipsoidal Height || 6
|-
| 4 || 4.1.10.1.76-71 || 5.68 || Threshold Crossing Height || 5
|-
| 5 || 4.1.10.1.81 || 5.270 || TCH Value Indicator || 1
|-
| 6 || 4.1.10.1.82-85 || 5.44 || Localizer/MLS/GLS Identifier || 4 max
|-
| 7 || 4.1.10.1.86 || 5.80 || ILS/MLS/GLS Category || 1
|-
| 8 || 4.1.10.1.96-98 || 5.67 || Threshold Crossing Height || 3
|-
| 9 || 4.1.10.1.33-41 || 5.36 || Runway Latitude || 9
|-
| 10 || 4.1.10.1.42-51 || 5.37 || Runway Longitude || 10
|-
| 11 || 4.1.10.1.72-75 || 5.69 || Displaced Threshold Distance || 4
|}

Table rwnILSmode:
{| class="wikitable"
|-
! Mode !! info
|-
| <blank> || No ILS for the runway
|-
| 0 || LOC
|-
| 1 || ILS CAT I
|-
| 2 || ILS CAT II
|-
| 3 || ILS CAT III
|-
| L || LDA with Glideslope
|-
| A || LDA, No Glideslope
|-
| S || SDF with Glideslope
|-
| F || SDF, No Glideslope
|-
| I || IGS
|}

=== PRDAT ===
TBA

== Examples ==

== Apendix ==

User:Www2

2018-08-18T22:01:46Z

Www2: fix, add , br

FG python docs
[[User:www2/fgpython]]

X-Plane 11 Data Specification [[User:www2/XP11 Data Specification]] 
Little Nav Map Database Specification [[User:www2/Little Nav Map/Database]]