Home' RTCA Documents for Review : DO-201B User Requirements for Navigation Data Contents ED-77A/DO-201BforOpenConsultation/FRAC
© EUROCAE, 2018
Note The intent is to develop airborne systems and navigation database procedures
that result in the automated flight operation being the same or better than hand flown.
This is best accomplished if the procedure designer understands the requirements of
computer-based navigation systems and incorporates this understanding into the
thinking process of procedure design.
General Design Rules
There are several standard design rules that should [NAV-D030] be applied when
designing route segments regardless of the RNP status of the airspace or navigation
system that will use the procedures. These general rules assure that flight paths are
accurate, reliable, and repeatable for computer-based navigation systems.
Complete and Continuous Data
Complete and continuous flight path data between the runway and the enroute structure
using SIDs, STARs and Approaches should [NAV-D031] be provided. A departure
should [NAV-D032] always be designed as a continuous flight path with specifically
described route segments, linked together with specific fixes, from take-off through the
departure procedure to a fix or a navaid in the enroute structure. Likewise, an arrival
should [NAV-D033] be defined as a continuous path from a fix or navaid in the enroute
structure, through the specified arrival fixes, to the fix that begins an approach
Commonality of fixes that link arrivals to approaches should [NAV-D034] be assured;
e.g., the terminating fix of the arrival and the beginning fix of the approach should [NAV-
D035] be the same. All fixes should [NAV-D036] be named in accordance with ICAO
SARPs. The minimum distance between waypoints, as specified in ICAO Doc 8168, is
When initial departure flight paths are designed to an altitude, the altitude should [NAV-
D037] be a minimum ("at or above") altitude whenever possible rather than a mandatory
("hard") altitude. Multiple conditions related to the altitude should [NAV-D038] be
avoided such as turns at an altitude but not before a specific distance.
See example 5.3 .2 “Double Conditions on Departure Procedures.”
No lateral course change should [NAV-D039] be made after departure until reaching
400 ft above airport elevation.
A complete arrival or departure procedure navigation route should [NAV-D040] be
provided by ATC to support computer navigation system operations, even when ATC
radar vectoring is planned. If radar vectors are required, the procedure should [NAV-
D041] be redesigned to better fit the radar vector pattern.
Graphic and textual depiction/description of departures must coincide and be
unambiguous. Unclear textual descriptions and mismatches between text and chart can
cause incorrect coding.
Bank Angle Requirement
Bank angle requirements should [NAV-D042] not be part of procedure design because
they cannot be coded in the navigation database. Procedure design should [NAV-
D043] take into consideration bank angle limits for different aircraft types and categories
Links Archive Navigation Previous Page Next Page