Home' RTCA Documents for Review : DO-201B User Requirements for Navigation Data Contents ED-77A/DO-201BforOpenConsultation/FRAC
© EUROCAE, 2018
procedures, navaids, and landing system infrastructure. It excludes terrain, obstacle,
and cultural data (e.g., geopolitical borders, water features, etc.) .
Operational data is data that is not required for navigation, but used for navigation
operations. It includes, but is not limited to, airspace, communication, and aerodrome
The data requirements included in this standard have been compiled in order to support
the functions and applications listed in Appendix A; however, this document does not
define requirements for the applications themselves.
DEFINITION OF TERMS AND CONVENTIONS
In the aviation community, the terms "course" and "track" are often used synonymously.
Course is usually considered the intended direction of flight in the horizontal plane,
measured in degrees from north. Track is usually considered a projection on the earth's
surface of the path of an aircraft the direction of which path at any point is usually
expressed in degrees from North (true, magnetic, or grid). In this document, track has
been used in referring to the paths of route segments except where course is an integral
part of a State, Industry, or ICAO term or concept such as ”course reversal” (U.S .) or
In addition, the following conventions have been adopted:
The term “shall” is used to identify requirements within this standard
The term “should” is used identify recommendations within this standard
Requirements are specified in Sections 2 and 3 and are uniquely numbered to support
requirements traceability procedures. Requirements (“shall” statements) are
enumerated with identifiers in the format [NAV-RXXX] at the end of a sentence (prior to
the period), where XXX is an identifier (ID) unique across all requirements in the
document. The letter ‘R’ specifies this as a requirement.
Recommendations (“should” statements) are enumerated with an ID formatted as
[NAV-DXXX] at the end of a sentence, where XXX is an ID unique across all
recommendations in the document. The letter ‘D’ specifies this as a recommendation
Each ID is specific to the version of the document in which it appears. However, an ID
number associated with a requirement or recommendation does not change from one
version to another unless the intent of the requirement changes. Requirement IDs do
not change due to editorial or clarification modifications, or due to moving requirements
to a different place in the document.
If the intent of a requirement or recommendation changes, the ID used in the previous
version is eliminated and never reused. A new ID is assigned for the new document
version. For example, if the requirement, “The metric system shall be used for all linear
measurements (e.g., runway length)” were modified to state, “Imperial units shall be
used for all linear measurements (e.g., feet for runway length)”, the requirement ID
would not be changed, since the intent of the requirement is still to specify the type of
units that are used for linear measurements.
However, if it were modified to state, “All measurements shall identify the units in which
they are measured,” the requirement ID would change, since the scope of the
requirement expanded to include all measurements, and the concept of having to
include the units with the measurement was introduced.
Requirements that are deleted or deprecated never have their identifiers reused.
Graphic illustrations appearing in different Sections and Appendices of this document
are conceptual and were developed strictly to support textual discussions. They are not
intended to be used for developing cartographic charting criteria or standards.
Illustrations contain graphic symbols copyrighted by Jeppesen, which have been
reproduced with permission. The equivalent graphic symbols to be used by States are
specified in ICAO Annex 4.
Links Archive Navigation Previous Page Next Page