Annex I: Navigation Databases (NavDB)

1. General

1.1 This annex provides advisory material for establishing the appropriate NavDB support arrangements.

2. Rationale and Guidance

2.1 The Operational Airworthiness Authority (OAA) identifies the following avionics database requirements in the RCAF Flight Operations Manual, Chapter 2 (reference 3.2.2.l), paragraph 2.3.6.2 titled RNAV (GNSS) Operation Approval Requirements:

‘2. Database Requirement. The avionics database must be current. The RNAV system must include a manufacturer supplied electronic database that can be updated, normally on 28- or 56-day cycles. The updating service is usually purchased under subscription from the avionics manufacturers or database suppliers.

1. As database errors do occur, crews must verify that the retrieved data is correct. Prior to using the database for primary navigation, crews must verify the integrity of their database in accordance with the procedures outlined in GPH 204A. Additional verification should be accomplished by comparing waypoint co-ordinates found in the navigation database with a WGS-84 based chart. Crews can also check bearings and distances between waypoints found in the FMS against enroute charts. Any discrepancies shall be reported to the avionics database supplier.’

NOTES:  
1. Not all nations use a reference datum of WGS-84 when determining the coordinates for navigation waypoints (this includes RNAV waypoints and NAVAIDs). While many host nation products (including those produced by Jeppesen) may display coordinates utilizing a variety of reference datums, all U.S. DoD navigation products (and most RAF and RAAF products) are printed with WGS-84 coordinates.
2. All approaches must be retrieved from the avionics database. While it is acceptable to use pilot-generated waypoints en-route, it is not permitted for approach procedures as any database or waypoint coordinate errors could have serious consequences.

2.2 The general operating procedures section in the PBN Manual (ICAO Doc 9613 Ed 4, section 3.3.4.2) prohibits civil aircraft from manually entering, or creating new waypoints by manual entry, of latitude and longitude or rho/theta values for RNAV 1, RNAV 2, RNP 1 and RNP 2. The creation of new waypoints by manual entry into the RNAV system by the flight crew would invalidate the route and is not permitted.

2.3 The Technical Airworthiness Authority (TAA) identifies the following NavDB requirements in the ADSM, section 3.3.5, para 31 (regulatory reference 3.2.1.b), which states:

‘As part of the Technical Airworthiness Clearance (TAC) process, it will be required to demonstrate that an aeronautical data support arrangement meets the objectives of DO-200B, that the NavDB is compatible with the equipment, and that it is suitable for the intended use. In addition, the TAC will require the Type Certificate Holder organization to have a quality procedure that ensures DO-200B requirements will continue to be met once the NavDB is in service.’

2.4 During the PBN Design Certification Process, the NavDB requirements will be addressed as part of the ‘Instructions for Continued Airworthiness’ certification requirement. The applicant will be required to provide a NavDB Support Plan that addresses the following requirements:

1. How the NavDB is, or will be, produced and delivered to the aircraft, including the responsibilities of each organization in the data chain of the NavDB, beginning with authoritative data sources (usually a State), and finishing with the organization(s) that install the NavDB on the aircraft.

NOTES:  
1. For additional information about the types and sources of NavDBs acceptable to the TAA, see the ADSM, Part 3, Chapter 3, Section 3.3.5, paras 29 – 33 (regulatory reference 3.2.1.b). This reference also identifies the TAA-accepted NavDB design standards.
2. If the NavDB data source does not have a Civil Airworthiness Authority (CAA)/ Military Airworthiness Authority (MAA) recognition for providing aeronautical data, the certification activities will have to include the recognition of the data source provider. The recognition or acceptability of the data source provider will be performed by DTAES 4 and 6 staff.

2. Identify the navigation data process, i.e., receive, assemble, etc., that will need to be performed by DND upon reception of the NavDB, and the support provided for the performance of these processes by the vendor or acceptable support organization.
3. Identify any validation activities that are passed to the end user, and any data elements that are not covered by CAA/MAA recognition (referred to as ‘tailored data’).
4. Address the following in the NavDB in-service support arrangements and procedures:
   1. Identification of the DND/CAF organization(s) responsible for managing the NavDB;
   2. Documented procedures for validating the navigation databases and installing new/updated databases into aircraft to maintain currency. This includes procedures for any navigation data processes performed by DND;
   3. Maintenance of the NavDB quality requirements to ensure the availability of an accurate and up-to-date navigation database;
   4. Monitoring and control of the release and authorized use of the data;
   5. Monitoring and control of any in-service NavDB updates and changes, including changes to aeronautical data chain management processes;
   6. Monitoring and control of any NavDB update or amendment processes performed by DND or DND support organizations;
   7. Verification and reporting of errors to the navigation database supplier; and
   8. Control of the NavDB part numbers/version numbers and the associated aeronautical data support equipment.

2.5 Additional guidance material for developing the NavDB support plan is available in FAA Advisory Circular (AC) 20-153 (reference 3.2.2.m). This AC provides guidance material for showing compliance with FAA’s airworthiness requirements for equipment with an installed aeronautical database. The FAA’s target audience for this AC is the aeronautical data suppliers (e.g., data providers, application integrators, etc.), aircraft manufacturers, avionics manufacturers, and operators/end-users.