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.

X plane 10 store