Home' RTCA Documents for Review : DO-201B User Requirements for Navigation Data Contents ED-77A/DO-201BforOpenConsultation/FRAC
© EUROCAE, 2018
SIS: If using GNSS, the aircraft navigation equipment shall [NAV-R004] provide an
alert if the probability of Signal in Space (SIS) errors causing a lateral position error
greater than 2 nm exceeds 10–7 per hour.
Expressions such as RNP type and RNP value that were associated with the RNP
concept (as referred to in Doc 9613, Second Edition, formerly titled Manual on Required
Navigation Performance (RNP)) are not used under the PBN concept and are to be
deleted in all ICAO material.
Navigation Database Management for PBN
DO-201B/ED-77A aims at supporting the implementation of navigation specifications by
being the “User Requirements for Navigation Data” document covering operational and
system’s needs. From systems and operational perspectives the document defines the
scope of navigation data, supports PBN operations with database integrity needs, and
considers data contribution to criticality. It addresses increasing levels of rigor for higher
integrity requirements of PBN and other related functions. The DQRs have greater detail
while consistency with other relevant standards (i.e ., DO-272/ED-99, DO-276/ED-98) is
The new ICAO PANS-AIM Data Catalogue has been a starting point for the DQR in DO-
201B/ED-77A; ICAO Annex 15 has been used as reference for terminology.
RNAV and RNP applications depend on navigation data therefore the performance of
the application is contingent upon the accuracy, resolution and integrity of the data.
The ICAO PBN Manual refers to DO-200/ED-76, DO-201/ED-77 for ensuring the
navigation database conforms to the data quality requirements, and that the applicable
data process conforms to the DO-200 processes.
A Letter of Acceptance (LOA) or supplier certificate issued by the appropriate regulatory
authority to each of the participants in the data chain demonstrates compliance with this
Some RNAV navigation specifications do not require the use of a navigation database
(example) RNAV 5. On the other hand, RNP APCH and in particular RNP AR APCH
have more stringent data quality requirements.
The PBN Manual requires that if a navigation database is carried and used, it must be
current and appropriate for the region of intended operation and must include the
navaids and waypoints required for the route. The RNP system should [NAV-D004]
automatically retrieve and set the navigation accuracy for each leg segment of a route
or procedure from the on-board navigation database. When a change occurs to a
smaller navigation accuracy (e.g., from RNP 1.0 to RNP 0.3), the change must be
complete by the first fix defining the leg with the smaller navigation accuracy
requirement. The timing of this change must also consider any latency in alerting from
the RNP system. When the RNP system cannot automatically set the navigation
accuracy for each leg segment, any operational procedures necessary to accomplish
this must be identified.
The RNP system provides an indication to the flight crew if the manual setting is greater
than the default or database-defined RNP value.
Short description of each PBN navigation specification together with specific database
requirements (if any) are listed below.
RNAV 10 (Designated and Authorised as RNP 10)
This PBN specification is intended to support operations in oceanic and remote
airspace. It accepts low performances in terms of accuracy (i.e., 10 nm) and does not
require on-board monitoring and alerting systems. A navigation database is not
RNP 4 specification is required for operations in oceanic and remote airspace. It does
not require any ground-based navaid infrastructure. GNSS is the primary navigation
Links Archive Navigation Previous Page Next Page