Home' RTCA Documents for Review : DO-201B User Requirements for Navigation Data Contents ED-77A/DO-201BforOpenConsultation/FRAC
© EUROCAE, 2018
more enroute transitions from the termination fix of the departure to the enroute
Some arrivals begin from a fix that is not attached to the enroute structure or terminate
a departure at a fix that is not located in the enroute structure. In these cases, the
enroute transition may be used to link the arrival or departure to the enroute airways.
Arrivals and departures that do not begin or end at a navigation position in the enroute
structure create data discontinuities. These discontinuities may be resolved by a data
provider with created route segments that link the enroute structure to the arrival or
Enroute Transition Names
Enroute transitions used on arrivals and departures should [NAV-D069] be identified
by the name of the navaid or fix where the transition begins on an arrival or ends on a
departure, refer to Section 5.2.4 .1 .
Runway Transitions Used on Arrivals and Departures
The airborne navigation database has the capability to provide multiple paths from
runway ends to join a departure or to connect arrivals with the IAFs of approaches.
These route segments are known as runway transitions. Procedure designers need to
be aware that this capability exists so that procedures can be designed with this
Note: Runway transitions are quite distinct from enroute transitions discussed in Section
18.104.22.168. Runway transitions join individual runways to the common arrival or departure
and are not named. Enroute transitions join the common arrival or departure to different
airways or to waypoints in the enroute structure. Enroute transitions are named, refer to
An arrival designed to serve more than one runway should [NAV-D070] end at a fix in
the terminal environment where a transition can be made to the initial approach fix for
each respective runway.
A departure designed to serve more than one runway, should [NAV-D071] include a
runway transition route segment from each runway to a common fix or navaid in the
terminal environment. From this common fix, the track follows the departure to the
ending departure fix or navaid.
Commentary: It is common practice in many regions to design both arrival and departure
procedures to serve a single specific runway at an aerodrome. In other regions, it is
customary to design common arrival and departure procedures to serve an entire
aerodrome. To use these common procedures effectively, specific routes or runway
transitions are often added to connect individual runways to the common departure or
Eliminate the Practice of Duplicating Airway Segments as Part of the Arrival or
The practice of duplicating airway route segments on existing and future arrivals and
departures should [NAV-D072] be eliminated except where there is an overriding
procedural or air traffic control need for the duplication. Many arrivals and departures
are designed with an airway segment as a route segment on the arrival or departure,
duplicating the airway segment bearings, distances, and altitudes.
While it is desired to use continuous PBN routes, it is common for air traffic control to
use radar vectors for maintaining air traffic flow. This creates a discontinuity that impacts
aircraft performance predictions and flyability in PBN systems. To support PBN
operations, procedures should [NAV-D073] be designed to provide continuous PBN
paths irrespective of the possible use of radar vectors.
Links Archive Navigation Previous Page Next Page