X plane 11 a320 code#

XPNAV1100, 11, as explained further down.ARINC 424 supplements 18 up to 20, with the exceptions noted in the FAA/Aeronautical Information Services CIFP Readme.

X-Plane 11 and 12 support two formats in which the global database can be provided: X-Plane enforces integrity of this unique index, because it is needed to build the graph of the airway network. Only then it is possible to build the layered structure. See ICAO document No 7910 for details.īy classification into terminal vs global items and assigning the correct parent terminal area or ICAO region, each item in the database is addressable by a globally unique identifier. Note especially the seven regions defined for the continental United States.

X plane 11 a320 code#

All fixes and navaids must specify the region ICAO code according to the 424.20 5.14 ICAO code. Terminal fixes and navaids must specify the arpt/heli ident of their terminal area, according to the 424.20 5.6 Airport/Heliport Identifier. X-Plane 11 and 12 distinguish between global and terminal fixes and navaids.

If you find an airport with these values missing or incorrect, use WED 1.5 or later to add/edit these values and upload your change to the scenery gateway.Īs of X-Plane 12, the airport data is located in $X-Plane/Global Scenery/Global Airports/Earth nav data/apt.dat and is the one and only source for both scenery and GPS data, so what you see is what you get. Note that this data is already populated for most airports in the scenery gateway.

transition_level, this must specify the transition level in feet.

transition_alt, this must specify the transition altitude in feet.

datum_lat, datum_lon, those specify the location of the airport reference point (ARP) in decimal degrees, North and East positive.

region_code, this must specify the region according to ICAO document No 7910.

The following key-value pairs are part of the apt.dat 1050 specification and are used in X-Plane 11: Now all this information is taken from apt.dat, which uses the 1302 row code for key-value pairs, which can be edited in WED. Previously, a separate airports.txt was used to hold information like transition level, longest runway length, etc. No more duplicate airport informationįurthermore, all data about airports and runways is taken from the apt.dat, which has been extended so it can carry information necessary for the avionics. X-Plane 12 loads navdata conforming to the 11.50 or later spec, for supporting all features, navdata conforming to the 12 spec is preferred. Note that the format is not backwards-compatible to any of the old datasets, X-Plane 11 will only load data in the X-Plane 11 format. X-Plane 11 has a redesigned navdata hierarchy and new formats, that strongly enforce referential integrity and correctness. This lack of data integrity is no longer possible.

In X-Plane 10, it was possible to have a discrepancy between what you saw in the X-Plane world and what was available for GPS navigation. All items defined in this common database will be used for the scenery, the map, ATC, AI and the GPS/FMS and radio navigation avionics. In X-Plane 11 and later, one single database is used for all purposes of navigational data in the simulator.