Home' RTCA Documents for Review : DO-201B User Requirements for Navigation Data Contents ED-77A/DO-201BforOpenConsultation/FRAC
© EUROCAE, 2018
Note; Most legs except those with an “A” as a terminator (second character) can be used
for climb or descent.
ARRIVAL AND DEPARTURE INSTRUMENT PROCEDURE REQUIREMENTS AND
Arrival and departure procedures should [NAV-D044] be designed to take advantage
of the benefits that can accrue from the use of RNAV equipment.
The lateral procedure track followed by an aircraft with an automated system is guided
by the sequence of route segments coded into the navigation database of the automated
system. These coded route segments permit automated systems to emulate the
procedure route segments presented by a procedure designer in AIP documents. Each
route segment of a non-RNAV procedure is interpreted by a data preparation agency
and then coded with path terminators for use in the navigation database (refer to the
discussion of path terminators in Section 3.1). Because of the interpretation involved,
some procedures flown by RNAV aircraft may not totally emulate the procedure as
designed. See example 5.3 .6 “Procedure Turns Inside of Final Approach”.
Route segments should [NAV-D045] be designed so that a continuous and complete
flight path can be programmed in the navigation database. For example, a departure
should [NAV-D046] be designed with properly defined and linked route segments from
take-off through the departure routing to the fix in the enroute structure. Likewise, an
arrival should [NAV-D047] include defined and linked route segments from a fix in the
enroute structure through the arrival to a fix on the instrument approach procedure.
Arrivals and departures should [NAV-D048] be developed using tracks between fixes
rather than headings. Heading segments, when defined as part of a procedure, cannot
The availability of complete flight path data between the runway and enroute structure
not only supports navigation but will permit users of computer-based navigation systems
Accurately compute trip time, distance and fuel;
Predict reliable fix altitudes in the climb and descent;
Determine cost-effective speed schedules;
Maximize vertical flight management; and
Extend existing technology to predict and control time of arrival.
Note: Multiple runway transitions and enroute transitions are permitted in the design and
coding of departures and arrivals. However, multiple common routes cannot be
accommodated and should [NAV-D049] never exist in a single departure or arrival
procedure. Where multiple common routes are required, separate arrivals or departures
should [NAV-D050] be developed.
See example 5.3 .10 “Preferable missed approach coding”.
Requirements Unique to Arrival Procedures
Arrival Name and Coded Designator Standards
International standards for assigning arrival names and coded designators are included
in ICAO Annex 11, Appendix 3. ICAO specifies that an arrival name consist of a basic
indicator, a validity identifier, and when required, a route indicator. The basic indicator
is the name of the significant point where the arrival begins such as navaid or a fix. The
validity identifier is a numeral from one to nine specifying the current edition of the arrival
procedure. The route indicator is an alpha character added as a suffix as necessary.
Links Archive Navigation Previous Page Next Page