Document ID: chunk:federal_register_of_legislation:F2018C00889:reg:5:p2
Version: federal_register_of_legislation:F2018C00889
Segment Type: reg
Provision Reference: reg 5 (pt 2/51)
Character Range: 30270–33241

flight crew members.
       13.3 A navigation database for PBN operations must be valid. To be valid, a navigation database must be:
(a) obtained from a supplier who complies with:
           (i) Radio Technical Commission for Aeronautics (RTCA) DO 200A; or
           (ii) European Organisation for Civil Aviation Equipment (EUROCAE) document ED-76, Standards for Processing Aeronautical Data; and
(b) compatible with the intended function of the equipment in accordance with ICAO Annex 6, Part 1, Chapter 7.
       Note 1   Annex 6, Part 1, Chapter 7 states that an operator shall not employ electronic navigation data products that have been processed for application in the air and on the ground unless the State regulatory authority has approved the operator's procedures for ensuring that the process applied and the products delivered have met acceptable standards of integrity and that the products are compatible with the intended function of the equipment that will use them. The State regulatory authority shall ensure that the operator continues to monitor both process and products.
       Note 2   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 Agency Opinion 01/2005 and the associated "Conditions for the issuance of Letters of Acceptance for Navigation Database Suppliers by the Agency".
       Note 3   A Type 1 LOA provides recognition of a data supplier's compliance with RTCA/DO-200A/EUROCAE ED-76 with no identified compatibility with an aircraft system. A Type 1 LOA ensures the processes for producing the aeronautical data comply with the documents identified in Note 1 and the documented data quality requirements (DQRs).
       Note 4   A Type 2 LOA provides recognition of a data supplier's compliance with RTCA/DO-200A/EUROCAE ED-76 and the compatibility of its delivered data with particular avionic systems that are identified in the LOA letter.
       Note 5   A CASR Part 175 approval equates to an EASA or FAA Type 1 LOA.
(c) current for the present AIRAC cycle.
       13.4 Operators carrying out RNP APCH, Baro-VNAV, Advanced RNP, RNP 0.3 or RNP AR approach operations must obtain their navigation databases from suppliers holding a Type 2 LOA.
       13.5 An operator who has a navigation authorisation from CASA must periodically check the navigation database for database integrity.
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 against a current navigation data source.
       13.6 Any discrepancy in data in the operator's navigation database must be:
(a) reported as soon as practicable to the navigation database supplier; and
(b) resolved, before further operational use,