FAA AIXM Data to AIXM 5.2

Required roles: AIS Navigation Data via Cloud — Roles
Base endpoint: none
Reference documents: AIXM 5.2 schema set (aixm.aero)
Attribution: show ibonav.aero wherever this data is displayed
Data sources: FAA
Last updated: 27 OCT 2026

About the reference documents: Related Documents and Resources

FAA NASR data is added as published by the FAA: the Airport, Navigation Aid and Airway subscriber files (AIXM 5.1 with FAA extensions) and the Special Use Airspace files (AIXM 5.0 with SAA/SUA extensions). The data is converted to AIXM 5.2 when it is added to the database. The rules of Data Coding Policies › AIXM 5.1 Sources apply; the FAA-specific rules are below.

General

Rule Application
Identifier The subscriber files carry no gml:identifier. Each feature gets a UUID derived from its natural key (for example FAA location identifier and runway designator); the same key gives the same UUID in every file, so references between the files (an ILS to its runway direction) are kept. The Special Use Airspace files keep their own UUIDs
References References written as XPath expressions are converted to urn:uuid: references
Coordinates The subscriber files are in NAD83 (longitude latitude). They are converted to WGS 84 (EPSG:4326, latitude longitude) with the default EPSG:4269 → EPSG:4326 transformation. This transformation has no parameters: the coordinate values do not change; the difference between the two datums (about 1–2 m) is within its stated accuracy. The Special Use Airspace files are already in WGS 84 (CRS84); only the axis order is changed
FAA extension properties Not kept as extensions. Each value is written as a line property: value to the DESCRIPTION annotation of the nearest object that can carry an annotation. A value converted to an AIXM 5.2 property (below) is not repeated there. Labels used instead of the FAA property name: GNSS MEA, DME/DME/IRU MEA, Reverse MEA
Time slice metadata The FAA survey/source note of a feature is moved to its DESCRIPTION annotation (timeSliceMetadata: …)
Annotations FAA notes carry a property name but no purpose; they are coded with purpose REMARK
Not added Unit, air traffic control service, radio communication channel, information service and airport supplies service features

Aerodromes

Rule Application
Designator The ICAO location indicator. Without one: the ICAO region letter followed by the FAA location identifier, the same rule as EUROCONTROL EAD SDO — K contiguous United States, P Alaska, Hawaii and the Pacific islands, T Puerto Rico and the Virgin Islands, N American Samoa (e.g. K00AR); at most 6 characters. An aerodrome with neither an ICAO location indicator nor a state is not added
Local code The FAA location identifier in designatorLocal, designatorLocalAuthority = FAA (see Data Coding Policies › Aerodromes)
Runways and runway directions The FAA codes each runway end also as a runway (05, 23 beside 05/23). These end features are not added; references to them point to the runway. The runway direction designator is taken from its runway end. On a single-ended runway (most helipads) a runway direction that refers to a non-existing opposite end is not added
Touchdown and lift-off areas The FAA codes one for every runway end; not added
Glide path (airport file) Runway-end glide path angles, not navigation equipment; not added
Threshold The threshold position of a runway direction → RunwayCentrelinePoint with role THR. Take-off run, take-off distance, accelerate-stop distance and landing distance → RunwayDeclaredDistance TORA, TODA, ASDA, LDA of that point. Without a threshold position the distances stay in the description; no position is assumed
Pavement classification The combined FAA PCN/PCR properties → the AIXM 5.2 …PCN or …PCR properties, according to the type given by the FAA
Runway length and width The FAA runway length and width (FAA mapping: "Runway Length", "Runway Width" → runway length, width) are published in the strip properties of the FAA file; they are coded as nominalLength / nominalWidth

ATS

Rule Application
Airway points The airway file repeats every point and navaid for each airway. The copies are merged into one feature; a navaid is linked to the record of the navigation aid file
Waypoints coded as navaids Airway points coded by the FAA as navaids of type OTHER:WAY_PT (RNAV waypoints) or OTHER:CN (Canadian fixes), whose code is in the name → designated point, type OTHER, designator = name
Border points Points without a position (U.S. MEXICAN BORDER, U.S. CANADIAN BORDER) and the route segments ending at them are not added
Segment end reference The airway file always refers to the end point of a segment as a designated point; when the point at that position is a navaid, the reference is corrected to the navaid
Segment geometry The FAA airway file gives no geometry for a route segment. curveExtent is generated as a single geodesic line between the positions of the start and end points (NAD83 → WGS84). It is not written when either end point has no position
Minimum en-route altitude The AIXM 5.1 value → AIXM 5.2 AltitudeIndication. GNSS, DME/DME/IRU and reverse MEA stay in the description
Change-over points → ChangeOverPoint: the navaid given by the FAA, the distance (NM) from the start of the route segment, and the route segment as route portion
ILS navaids The FAA gives no type, designator or position for the ILS navaid. Type from the FAA facility type (table below); designator from the localizer identifier without the hyphen (I-ANB → IANB)
Navaid frequency and channel The FAA gives the transmit frequency and channel of a navaid in a radio communication channel linked to the navaid (FAA mapping: "Frequency Navaid Transmit On", "Channel Navaid Transmit On"). They are coded on the equipment: frequency → VOR (navaid types VOR, VOR_DME, VORTAC, OTHER:VOT) and NDB (NDB, NDB_DME, OTHER:MARINE_NDB); channel → TACAN (TACAN, VORTAC) and DME (DME, VOR_DME, NDB_DME, when the DME has no channel of its own). A value with no matching equipment stays in the description. The FAA publishes NDB frequencies with the unit MHZ although the values are in kHz (NDB band 190–1750 kHz); they are coded in KHZ
Locator frequency The FAA gives the frequency of a compass locator on the marker beacon (FAA mapping: "Frequency Of Marker Locator Beacon" → marker beacon frequency); it is kept there. The locator NDB of an ILS has no frequency of its own
Equipment authority The owning/operating organisation of an equipment is written to the description
Equipment elevation The ILS file gives the antenna site elevations without a unit; every unit stated in the ILS file is feet, so the elevations are coded in FT
FAA facility type AIXM navaid type
ILS, LOC/GS ILS
ILS/DME ILS_DME
LOCALIZER LOC
LOC/DME LOC_DME
LDA ILS with a glide path, otherwise LOC
LDA/DME ILS_DME with a glide path, otherwise LOC_DME
SDF, SDF/DME SDF

Special Use Airspaces

Rule Application
Type RA → R, PA → P, WA → W, AA → A, MOA → MOA, NSA (National Security Area) → OTHER:NSA
Activation The FAA airspace usage (a separate feature in AIXM 5.0, not in AIXM 5.2) → activation of the airspace: one activation for each layer and schedule, with activity, status, levels and timesheets. The FAA time offset → timeReference UTC±n; daylight saving → daylightSavingAdjust; working hours and allowed traffic → description
Arcs and circles Kept as published (GML arc by centre point, circle by centre point). The GeoPackage polygon is calculated from them
Overlapping sources Jeppesen prohibited, restricted, danger, alert and warning areas and MOAs whose centre is inside the FIRs of the FAA (KZ…, PAZA, PAZN, TJZS) are not published; these areas come from the FAA

Merging

Data set Application
Aerodrome An FAA aerodrome, runway, runway direction and threshold replaces the EUROCONTROL EAD SDO record with the same designators
ATS FAA route segments, designated points and navaids replace the EUROCONTROL EAD SDO records published for the FAA. Navaids and designated points of other EAD originators and of Jeppesen within 1 NM with the same designator are also replaced. Route segments are replaced segment by segment, as with the other AIP sources
Airspace Added; see Overlapping sources above