# Approach, Arrival, And Departure XML Properties This page lists the different elements and attributes required to generate properly formed XML for approaches, arrivals, and departures into and from airports. The information on this page is used along with the information for creating an Airport - since approaches are specifically for airports - which can be found here: - [Airport XML Properties](airport-xml-properties/)   The `` , `` and `` elements would go inside of the `` element, and you can (and normally would) define multiple approaches, arrivals, and departures in a single airport. {{< callout context="note" title="NOTE" icon="outline/bulb" >}} Editing Approach, Arrival and Departure data may prevent the simulation performing further automatic updates to the navigation data for the airport. Please see the following section for more information: [Note On Navigation Data](airports-and-facilities/#note-on-navigation-data) {{< /callout >}}     ### <Approach> This element is used to add an approach to an ``, and you can have multiple approach elements for each airport. Approaches are made up of three components, which must occur in the following order: 1. `` 2. `` 3. ``   The attributes used when defining an approach are as follows:  
AttributeDescriptionTypeRequired
typeThe type of approach.

Enum:

  1. GPS
  2. ILS
  3. LDA
  4. LOCALIZER
  5. LOCALIZER_BACKCOURSE
  6. NDB
  7. NDBDME
  8. RNAV
  9. SDF
  10. VOR
  11. VORDME
Yes
runwayThe runway number the approach is attached to. Note that you do not suffix the designator onto this value, but instead define it separately in the designator attribute.

Integer:

  1. 1 - 36

or Enum:

  1. EAST
  2. NORTH
  3. NORTHEAST
  4. NORTHWEST
  5. SOUTH
  6. SOUTHEAST
  7. SOUTHWEST
  8. WEST
No
designator Designator of the runway being added.

Enum:

  1. NONE
  2. C
  3. CENTER
  4. L
  5. LEFT
  6. R
  7. RIGHT
  8. W
  9. WATER
  10. A
  11. B
No
suffixSingle character identifier.

String

No
gpsOverlay Whether it has a has a GPS overlay or not.BoolNo
fixTypeThe type of FAF.

Enum:

  1. NDB
  2. TERMINAL_NDB
  3. TERMINAL_WAYPOINT
  4. VOR
  5. WAYPOINT
Yes
fixRegionThe station region of the FAF (maximum 3 characters, based on iso-3166-2).StringYes
fixIdentThe station identity of the FAF (maximum 5 characters).

String

Yes
altitudeAltitude for final approach in meters.

Float

Yes
headingThe final course heading start, from 0.0° to 360.0°.FloatYes
missedAltitudeMissed approach altitude in meters.

Float

Yes
lnavRNAV approach has LNAV category.BoolNo
lnavvnavRNAV approach has LNAV/VNAV category.BoolNo
lpvRNAV approach has LPV category.BoolNo
lpRNAV approach has localiser precision category.BoolNo
rnpArRNAV approach requires authorisation.BoolNo
rnpArMissedMissed approach requires authorisation (can be non-RNAV approach type).BoolNo
    #### <ApproachLegs> This sub-element of `` is used to add approach legs to an airport approach. The `` element has no attributes and is used as a container to hold a list of `` elements which describe the individual segments of the approach. You normally have multiple `` sub-elements in a single `` definition.     #### <MissedApproachLegs> This sub-element of `` is used to add legs for a missed approach path to an airport approach. The `` element has no attributes and is used as a container to hold a list of `` elements which describe the individual segments of the approach. You normally have multiple `` sub-elements in a single `` definition.     #### <Transition> This sub-element of `` is used to add transitions to an airport approach. A `` element contains a list of `` and/or `` sub-elements, and if both are present the `` must be entered *first*. The `` and `` elements describe the individual segments of the transition. The attributes you can apply to this element are as follows:  
AttributeDescriptionTypeRequired
transitionTypeThe transition type.

Enum:

  1. FULL
  2. DME
No
fixTypeThe type of IAF.

Enum:

  1. NDB
  2. TERMINAL_NDB
  3. TERMINAL_WAYPOINT
  4. VOR
  5. WAYPOINT
No
fixRegionThe station region of the IAF (maximum 3 characters, based on iso-3166-2).StringNo
fixIdentThe station identity of the IAF (maximum 5 characters).

String

No
altitudeAltitude of the first leg of the transition in meters.

Float

No
nameThe name of the transition.StringNo
    ##### <DmeArc /> This sub-element of `` is used to add a {{< glossterm >}}dme{{< /glossterm >}} arc to an approach transition. Note that this is a self-closing element and has the following attributes:   {{< table-wrapper >}} | Attribute | Description | Type | Required | |-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|--------|:--------:| | `radial` | The angle of the arc from the transmitter, from 1.0° to 360.0°. | Float | No | | `distance` | {{< glossterm >}}dme{{< /glossterm >}} distance. | Float | No | | `dmeRegion` | {{< glossterm >}}dme{{< /glossterm >}} station region (maximum 3 characters, based on [iso-3166-2](https://en.wikipedia.org/wiki/ISO_3166-2)). | String | No | | `dmeIdent` | {{< glossterm >}}dme{{< /glossterm >}} station identity of the associated navaid (maximum 5 characters). | String | No | {{< /table-wrapper >}}     ##### <TransitionLegs> This sub-element of `` is used to add legs for a transition during an airport approach. The `` element has no attributes and is used as a container to hold a list of `` elements which describe the individual segments of the transition.       ### <Arrival> This element is used to add an arrival route to an ``, and you can have multiple arrival elements for each airport. Arrival routes are made up of multiple components, which must occur in the following order: 1. `` 2. `` 3. ``   The only required attribute when defining an arrival is as follows:   {{< table-wrapper >}} | Attribute | Description | Type | Required | |-----------|---------------------------------------------------------------------------------------|--------|:--------:| | `Name` | The name of the arrival route as defined by the official airport charts, eg: "LIBER4" | String | Yes | | `rnpAr` | {{< glossterm >}}rnav{{< /glossterm >}} approach requires authorisation. | Bool | No | {{< /table-wrapper >}}     ### <Departure> This element is used to add an arrival route to an ``, and you can have multiple arrival elements for each airport. Arrival routes are made up of multiple components, which must occur in the following order: 1. `` 2. `` 3. ``   The only required attribute when defining an arrival is as follows:   {{< table-wrapper >}} | Attribute | Description | Type | Required | |-----------|-----------------------------------------------------------------------------------------|--------|:--------:| | `Name` | The name of the departure route as defined by the official airport charts, eg: "GLEEN7" | String | Yes | | `rnpAr` | {{< glossterm >}}rnav{{< /glossterm >}} approach requires authorisation. | Bool | No | {{< /table-wrapper >}}     ### <EnrouteTransitions> This is a sub-element of both the `` and `` elements. This is a *required* element, although if you have no transitions you can make this a simple self-closing element, eg: ``. This element has no attributes and is a container element for ``.     #### <EnrouteTransitionLegs> This is a sub-element of the `` container, and is used to list the various legs that comprise the transition route. This element should contain multiple `` elements and has a single attribute:   {{< table-wrapper >}} | Attribute | Description | Type | Required | |-----------|-----------------------------------------------------------------------------------------|--------|:--------:| | `Name` | The name of the route transition as defined by the official airport charts, eg: "PUYVO" | String | Yes | {{< /table-wrapper >}}     ### <CommonRouteLegs> This is a sub-element of both the `` and `` elements. This is a *required* element, although if you have no common routes you can make this a simple self-closing element, eg: ``. This element has no attributes and is a container element for multiple `` elements.     ### <RunwayTransitions> This is a sub-element of both the `` and `` elements. This is a *required* element, has no attributes and is a container element for one or more ``.     #### <RunwayTransitionLegs> This is a sub-element of the `` container, and is used to list the various legs that comprise the runway transition. This element should contain multiple `` elements and has the following attributes:  
AttributeDescriptionTypeRequired
numberNumber of the runway the transition legs belongs to. Note that you do not suffix the designator onto this value, but instead define it separately in the designator attribute.
  1. Integer:
  2. 1 - 36

or Enum:

  1. EAST
  2. NORTH
  3. NORTHEAST
  4. NORTHWEST
  5. SOUTH
  6. SOUTHEAST
  7. SOUTHWEST
  8. WEST
Yes
designatorDesignator of the runway the transition legs are being added to.

Enum:

  1. NONE
  2. C
  3. CENTER
  4. L
  5. LEFT
  6. R
  7. RIGHT
  8. W
  9. WATER
  10. A
  11. B
  12. E
  13. N
  14. NE
  15. NW
  16. S
  17. SE
  18. SW
  19. W
Yes
clearanceAltitudeJetThe initial altitude clearance used by ATC for jet aircraft on this runway transition. Only used when the transition is part of a <Departure> procedure.FloatNo
clearanceAltitudePropThe initial altitude clearance used by ATC for propeller aircraft on this runway transition. Only used when the transition is part of a <Departure> procedure.FloatNo
    ### <Leg /> This element is used to add legs to the following elements: 1. `` 2. `` 3. `` 4. `` 5. `` 6. ``   The specific information required to define the leg depends on the **type**. Note that this is a self-closing element and has the following attributes (a table of *required* and *optional* attributes is included further down the page):  
AttributeDescriptionTypeRequired
typeThe type of leg. The meaning of each 2-letter approach leg code is defined in the 424-16 specification document maintained by ARINC Incorporated and is a standard used in navigation databases and flight management systems. You can order the complete specification, which includes complete definitions and illustrations of each type, from the ARINC web site. For additional information on this parameter please see the Leg Type Information section.

Enum:

AF CA CD CF CI CR DF FA FC FD FM HA HF HM IF PI RF TF VA VD VI VM VR

No
fixTypeThe type of fix.

Enum:

  1. NDB
  2. TERMINAL_NDB
  3. TERMINAL_WAYPOINT
  4. VOR
  5. WAYPOINT
No
fixRegionThe fix region code (maximum 3 characters, based on iso-3166-2).StringNo
fixIdentThe fix identity (maximum 5 characters).

String

No
flyOverThis indicates whether the leg is intended to fly over (TRUE) the given point, or fly by (FALSE) the given pointBoolNo
turnDirectionTurn direction supplied for this leg, which can be L (Left), R (Right) or E (Either), where the default is E.

Enum:

  1. L
  2. R
  3. E
No
recommendedTypeType of "target" for this leg.

Enum:

  1. NDB
  2. TERMINAL_NDB
  3. TERMINAL_WAYPOINT
  4. VOR
  5. WAYPOINT
  6. RUNWAY
  7. LOCALIZER
No
recommendedRegion2 or 3 character region code, based on iso-3166-2.StringNo
recommendedIdent5 character (max) identity codeStringNo
thetaThe heading, from 0.0° to 360.0°.FloatNo
rhoDistance, in meters. You may suffix the value with "N" to get nautical miles, eg: "34N"StringNo
trueCourseTrue North course, from 0.0° to 360.0°. If used, then do not enter a value for magneticCourse.FloatNo
magneticCourseMagnetic North course, from 0.0° to 360.0°. If used, then do not enter a value for trueCourse.FloatNo
distanceDistance, in meters. You may suffix the value with "N" to get nautical miles, eg: "34N". If used, then do not enter a value for time.StringNo
timeTime, in minutes. If used, then do not enter a value for distance.FloatNo
altitudeDescriptorValue that describes how altitude1 and altitude2 are interpreted. For additional information on this parameter please see the Leg Type Information section.StringNo
altitude1First altitude level, in meters.FloatNo
altitude2First altitude level, in meters.FloatNo
speedLimit IntegerNo
verticalAngle FloatNo
arcCenterFixTypeThe arc center fix for RF legs.

Enum:

  1. AIRPORT
  2. LOCALIZER
  3. NDB
  4. RUNWAY
  5. TERMINAL_NDB
  6. TERMINAL_WAYPOINT
  7. VOR
  8. WAYPOINT
No
arcCenterFixIdent StringNo
arcCenterFixRegion StringNo
isIAFDefines whether this is an initial approach fix, ie: the fix depicted on instrument approach procedure charts that identify the beginning of the initial approach segment(s).BoolNo
isIFDefines whether this is an intermediate fix, ie: the segment between the intermediate fix or point and the final approach fix.BoolNo
isFAFDefines whether this is a final approach fix, ie: the segment between the final approach fix or point and the runway, airport, or missed approach point.BoolNo
isMAPDefines whether this is part of the missed approach procedure, ie: the segment between the missed approach point or the point of arrival at decision height and the missed approach fix at the prescribed altitudeBoolNo
arcRadius FloatNo
requiredNavigationPerformance FloatNo
speedLimitDescriptorDefines how thespeedLimit should be interpreted for the leg.

Enum:

  1. "+" - Speed constraint at or above speedLimit.
  2. "-" - Speed constraint at or below speedLimit.
  3. "@" - Speed constraint at speedLimit.
No
    #### Leg Type Information The table below describes each of the different type acronyms available for the element.   {{< table-wrapper >}} | Type | Name | Description | |--------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **AF** | Arc to a Fix Leg | This defines a track over ground at specified constant distance from a database {{< glossterm >}}dme{{< /glossterm >}} navaid. | | **CA** | Course to an Altitude Leg | This defines a specified course to a specific altitude at an unspecified position. | | **CD** | Course to a {{< glossterm >}}dme{{< /glossterm >}} Distance Leg | This defines a specified course to a specific {{< glossterm >}}dme{{< /glossterm >}} Distance which is from a specific database {{< glossterm >}}dme{{< /glossterm >}} navaid. | | **CF** | Course to a Fix Leg | This defines a specified course to a specific database fix. Note that TF legs are preferred over CF to avoid magnetic variation issues. | | **CI** | Course to an Intercept Leg | This defines a specified course to intercept a subsequent leg. | | **CR** | Course to a Radial termination Leg | This defines a course to a specified radial from a specific database {{< glossterm >}}vor{{< /glossterm >}} navaid. | | **DF** | Direct to a Fix Leg | This defines an unspecified track starting from an undefined position to a specified fix. | | **FA** | Fix to an Altitude Leg | This defines a specified track over ground from a database fix to a specified altitude at an unspecified position. | | **FC** | Track from a Fix to a Distance Leg | This defines a specified track over ground from a database fix for a specific distance. | | **FD** | Track from a Fix to a {{< glossterm >}}dme{{< /glossterm >}} Distance Leg | This defines a specific track from a database fix to a specific {{< glossterm >}}dme{{< /glossterm >}} Distance from a DME Navaid. | | **FM** | From a Fix to a Manual termination Leg | This defines a specified track over ground from a database fix until Manual termination of the leg. | | **HA** | HA leg | This defines racetrack pattern or course reversals at a specified database fix terminating at an altitude. | | **HF** | HF leg | This defines racetrack pattern or course reversals at a specified database fix terminating at the fix after a single pattern. | | **HM** | HM leg | This defines racetrack pattern or course reversals at a specified database fix with a manual termination | | **IF** | The Initial Fix Leg | This defines a database fix as a point in space. This is only required to define the beginning of a route or procedure. | | **PI** | Procedure Turn leg | This defines a course reversal starting at a specific fix, includes outbound leg followed by 180 degree turn to intercept the next leg. | | **RF** | Constant Radius Arc Leg | This defines a constant radius turn between two database fixes, lines tangent to the arc and a centre fix. | | **TF** | Track to a Fix | This defines a great circle track over ground between two known databases fixes. Preferred type for straight legs. | | **VA** | Heading to an Altitude termination Leg | This defines a specified heading to a specific Altitude termination at an unspecified position. | | **VD** | Heading to a DME Distance termination Leg | This defines a specified heading terminating at a specified {{< glossterm >}}dme{{< /glossterm >}} distance from a specific database {{< glossterm >}}dme{{< /glossterm >}} navaid. | | **VI** | Heading to an Intercept Leg | This defines a specified heading to intercept the subsequent leg at an unspecified position. | | **VM** | Heading to a Manual termination Leg | This defines a specified heading until a Manual termination. | | **VR** | Heading to a Radial termination Leg | This defines a specified heading to a specified radial from a specific database {{< glossterm >}}vor{{< /glossterm >}} navaid. | {{< /table-wrapper >}}   All of the leg types either require, or can take as optional, an altitude code letter (the `altitudeDescriptor` field) and either one or two altitude values. The following table shows the range of values and how they are interpreted:   {{< table-wrapper >}} | altitudeDescriptor | altitude1 Required | altitude2 Required | Description | |--------------------|:----------------------------------------------------------------------------------------------------------------------------------------------:|:----------------------------------------------------------------------------------------------------------------------------------------------:|-----------------------------------------------------| | \+ | | \- | Fly at or above altitude1 | | \- | | \- | Fly at or below altitude1 | | (space) | | \- | Fly at altitude1 | | A | \- | \- | | | B | | | Fly at or above altitude1 and at or below altitude2 | | C | \- | | Fly at or above altitude2 | | G | \- | \- | | | H | \- | \- | | | I | \- | \- | | | J | \- | \- | | | V | \- | \- | | {{< /table-wrapper >}}   The following table shows the different Leg `type`s and their associated Required and Optional attributes:   {{< table-wrapper >}} | Attribute | AF | CA | CD | CF | CI | CR | DF | FA | FC | FD | FM | HA | HF | HM | IF | PI | RF | TF | VA | VD | VI | VM | VR | |----------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------:| | `fixType` | | | | | | | | | | | | | | | | | | | | | | | | | `fixRegion` | | | | | | | | | | | | | | | | | | | | | | | | | `fixIdent` | | | | | | | | | | | | | | | | | | | | | | | | | `flyOver` | | | | | | | | | | | | | | | | | | | | | | | | | `turnDirection` | | | | | | | | | | | | | | | | | | | | | | | | | `recommendedType` | | | | | | | | | | | | | | | | | | | | | | | | | `recommendedRegion` | | | | | | | | | | | | | | | | | | | | | | | | | `recommendedIdent` | | | | | | | | | | | | | | | | | | | | | | | | | `theta` | | | | | | | | | | | | | | | | | | | | | | | | | `rho` | | | | | | | | | | | | | | | | | | | | | | | | | `trueCourse` | | | | | | | | | | | | | | | | | | | | | | | | | `magneticCourse` | | | | | | | | | | | | | | | | | | | | | | | | | `distance` | | | | | | | | | | | | | | | | | | | | | | | | | `time` | | | | | | | | | | | | | | | | | | | | | | | | | `altitudeDescriptor` | | | | | | | | | | | | | | | | | | | | | | | | | `altitude1` | | | | | | | | | | | | | | | | | | | | | | | | | `altitude2` | | | | | | | | | | | | | | | | | | | | | | | | | `speedLimit` | | | | | | | | | | | | | | | | | | | | | | | | | `verticalAngle` | | | | | | | | | | | | | | | | | | | | | | | | | `arcCenterFixType` | | | | | | | | | | | | | | | | | | | | | | | | | `arcCenterFixIdent` | | | | | | | | | | | | | | | | | | | | | | | | | `arcCenterFixRegion` | | | | | | | | | | | | | | | | | | | | | | | | | `isIAF` | | | | | | | | | | | | | | | | | | | | | | | | | `isIF` | | | | | | | | | | | | | | | | | | | | | | | | | `isFAF` | | | | | | | | | | | | | | | | | | | | | | | | | `isMAP` | | | | | | | | | | | | | | | | | | | | | | | | | `arcRadius` | | | | | | | | | | | | | | | | | | | | | | | | | `requiredNavigationPerformance` | | | | | | | | | | | | | | | | | | | | | | | | | `speedLimitDescriptor` | | | | | | | | | | | | | | | | | | | | | | | | {{< /table-wrapper >}}