29Navigation database — standards and discrepancies

29 Navigation database — standards and discrepancies

General

29.1Subject to this clause, management of the navigation databases must be in accordance with the requirements of ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 6, Implementing RNP AR APCH.

29.2A navigation database for RNP AR operations:

(ii) European Organisation for Civil Aviation Equipment (EUROCAE) document ED-76, Standards for Processing Aeronautical Data; and

Note An LOA, issued by an appropriate regulatory authority to each of the participants in the data chain, demonstrates compliance with this requirement, for example, FAA LOA issued in accordance with FAA AC 20-153 or EASA LOA issued in accordance with EASA Implementing Rule (IR) 21, Subpart G.

Data updates

29.3 Data management and procedure validation for RNP AR procedures must be in accordance with:

(a) the provisions of ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 6, Implementing RNP AR APCH relating to data updates; or

(b) subclauses 29.4 to 29.9.

Alternative data updates — cyclic data checks

29.4 For paragraph 29.3 (b), the operator must:

(a) implement procedures for the continued validity and integrity of navigation data at each data cycle; and

(b) periodically check the RNP AR navigation database for database integrity; and

Note While an LOA provides assurance of minimum standards for the supply of a navigation database, errors may still occur. All operators must conduct periodic checks to ensure database integrity.

(c) ensure that any discrepancy in data is resolved before operational use by:

(i) reissue of the navigation database; or

(ii) withdrawal of the approach or departure procedure; or

(iii) appropriate instructions to flight crew.

Flight validation

29.5 For paragraph 29.3 (b), where a certificated procedure designer has not conducted a flight validation in an aircraft of the type and configuration to be used for the RNP AR operation, the operator is required to conduct a flight validation for each such aircraft type and configuration to verify that:

(a) the aircraft navigation, flight control, cockpit display and other systems function correctly; and

(b) the procedure is flyable.

Note It is the responsibility of the operator to ensure that a validation is conducted in the aircraft type/configuration to be operated. However, that responsibility may be discharged if the operator has documentary evidence that the required validation has been conducted by the aircraft manufacturer or another RNP AR qualified operator.