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

The <Approach> , <Arrival> and <Departure> elements would go inside of the <Airport> element, and you can (and normally would) define multiple approaches, arrivals, and departures in a single airport.

<Approach>#

This element is used to add an approach to an <Airport>, 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. <Approach>
2. <ApproachLegs>
3. <Transition>

The attributes used when defining an approach are as follows:

<ApproachLegs>#

This sub-element of <Approach> is used to add approach legs to an airport approach. The <ApproachLegs> element has no attributes and is used as a container to hold a list of <Leg /> elements which describe the individual segments of the approach. You normally have multiple <ApproachLegs> sub-elements in a single <Approach> definition.

<MissedApproachLegs>#

This sub-element of <Approach> is used to add legs for a missed approach path to an airport approach. The <MissedApproachLegs> element has no attributes and is used as a container to hold a list of <Leg /> elements which describe the individual segments of the approach. You normally have multiple <MissedApproachLegs> sub-elements in a single <Approach> definition.

<Transition>#

This sub-element of <Approach> is used to add transitions to an airport approach. A <Transition> element contains a list of <DmeArc /> and/or <TransitionLegs> sub-elements, and if both are present the <DmeArc> must be entered first. The <Leg /> and <DmeArc> elements describe the individual segments of the transition. The attributes you can apply to this element are as follows:

<DmeArc />#

This sub-element of <Transition> is used to add a DME arc to an approach transition. Note that this is a self-closing element and has the following attributes:

<TransitionLegs>#

This sub-element of <Transition> is used to add legs for a transition during an airport approach. The <TransitionLegs> element has no attributes and is used as a container to hold a list of <Leg /> elements which describe the individual segments of the transition.

<Arrival>#

This element is used to add an arrival route to an <Airport>, 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. <EnrouteTransitions>
2. <CommonRouteLegs>
3. <RunwayTransitions>

The only required attribute when defining an arrival is as follows:

<Departure>#

This element is used to add an arrival route to an <Airport>, 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. <RunwayTransitions>
2. <CommonRouteLegs>
3. <EnrouteTransitions>

The only required attribute when defining an arrival is as follows:

<EnrouteTransitions>#

This is a sub-element of both the <Arrival> and <Departure> elements. This is a required element, although if you have no transitions you can make this a simple self-closing element, eg: <EnrouteTransitions />. This element has no attributes and is a container element for <EnrouteTransitionLegs>.

<EnrouteTransitionLegs>#

This is a sub-element of the <EnrouteTransitions> container, and is used to list the various legs that comprise the transition route. This element should contain multiple <Leg /> elements and has a single attribute:

<CommonRouteLegs>#

This is a sub-element of both the <Arrival> and <Departure> elements. This is a required element, although if you have no common routes you can make this a simple self-closing element, eg: <CommonRouteLegs />. This element has no attributes and is a container element for multiple <Leg /> elements.

<RunwayTransitions>#

This is a sub-element of both the <Arrival> and <Departure> elements. This is a required element, has no attributes and is a container element for one or more <RunwayTransitionLegs>.

<RunwayTransitionLegs>#

This is a sub-element of the <RunwayTransitions> container, and is used to list the various legs that comprise the runway transition. This element should contain multiple <Leg /> elements and has the following attributes:

<Leg />#

This element is used to add legs to the following elements:

1. <EnrouteTransitionLegs>
2. <CommonRouteLegs>
3. <RunwayTransitionLegs>
4. <TransitionLegs>
5. <ApproachLegs>
6. <MissedApproachLegs>

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):

Leg Type Information#

The table below describes each of the different type acronyms available for the element.

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:

The following table shows the different Leg types and their associated Required and Optional attributes: