Advisory Circular (AC) No. 561-004

From: Transport Canada

Subject: Acceptance of Type 2 Aeronautical Database Providers

Issuing Office: Civil Aviation, Standards
Document No.: AC 561-004
File Classification No.: Z 5000-34
Issue No.: 01
RDIMS No.: 16146905-V11
Effective Date: 2022-10-18

Table of contents

1.0 Introduction

  • (1) This Advisory Circular (AC) is provided for information and guidance purposes. It describes an example of an acceptable means, but not the only means, of demonstrating compliance with regulations and standards. This AC on its own does not change, create, amend or permit deviations from regulatory requirements, nor does it establish minimum standards.

1.1 Purpose

  • (1) The purpose of this document is to provide information and guidance for obtaining or amending a Transport Canada Civil Aviation (TCCA) Letter of Acceptance (LOA) for the production of Type 2 aeronautical databases for aeronautical products manufactured under a manufacturer certificate issued pursuant to Subpart 561 of the Canadian Aviation Regulations (CARs).
  • (2) This AC also provides recognition of Radio Technical Commission for Aeronautics (RTCA) DO-200B and European Organization for Civil Aviation Equipment (EUROCAE) ED-76A standards, for the purposes of producing Type 2 aeronautical databases under a CAR 561 manufacturer certificate.

1.2 Applicability

  • (1) This document applies to holders of a CAR 561 manufacturer certificate, TCCA personnel, delegates and the aviation industry.
  • (2) While this AC is considered guidance, the expectation is that applicants for a TCCA Type 2 aeronautical database provider (ADP) LOA who choose to utilise this AC as the means of compliance with RTCA DO-200B or EUROCAE ED-76A standard for the purpose of producing Type 2 aeronautical databases should do so in its entirety.

1.3 Description of Changes

  • (1) Not applicable.

2.0 References and requirements

2.1 Reference Documents

  • (1) It is intended that the following reference materials be used in conjunction with this document:
    • (a) Aeronautics Act (R.S.C., 1985, c. A-2);
    • (b) Part I, Subpart 1 of the Canadian Aviation Regulations (CARs) — Interpretation;
    • (c) Part V, Subpart 61 of the CARs — Manufacture of Aeronautical Products;
    • (d) Standard 561 of the CARs — Approved Manufacturers;
    • (e) Advisory Circular (AC) 700-038 — Performance-based Navigation (PBN) — Enroute;
    • (f) International Civil Aviation Organization (ICAO) Annex 15 to the Convention on International Civil Aviation, Sixteenth Edition, July 2018 — Aeronautical Information Services;
    • (g) ICAO Doc 8126 AN/872, Sixth Edition, 2003 — Aeronautical Information Services Manual;
    • (h) ICAO Doc 9613 AN/937, Fourth Edition, 2013 — Performance-based Navigation (PBN) Manual;
    • (i) Federal Aviation Administration (FAA) AC 20-153B — Acceptance of Aeronautical Data Processes and Associated Databases;
    • (j) Commission Implementing Regulation (EU) 2017/373, 2017-03-01 — Requirements for providers of air traffic management/air navigation services and other air traffic management network functions and their oversight;
    • (k) European Organisation for Civil Aviation Equipment (EUROCAE) ED-76A — Standards for Processing Aeronautical Data;
    • (l) Radio Technical Commission for Aeronautics, Incorporated (RTCA, Inc.) DO-200B — Standards for Processing Aeronautical Data; and
    • (m) RTCA, Inc. DO-330 — Software Tool Qualification Considerations.

2.2 Cancelled Documents

  • (1) Not applicable.

2.3 Definitions and Abbreviations

  • (1) The following definitions are used in this document:
    • (a) Aeronautical data: A representation of aeronautical facts, concepts or instructions used for aeronautical applications such as navigation, flight planning, flight simulators, terrain awareness, and other purposes (e.g., navigation data, terrain and obstacle data, and airport mapping data);
    • (b) Aeronautical data chain: A conceptual representation of the processing path that a set or element of aeronautical data takes from its origination to its end-use;
    • (c) Aeronautical database: A collection of aeronautical data organised and arranged as a structured data set, stored electronically, valid for a defined period and subject to update;
    • (d) Aeronautical Information Publication (AIP): A publication issued by or with the authority of a State and containing aeronautical information of a lasting character essential to air navigation;
    • (e) Aeronautical Information Service (AIS): A service established within the defined area of coverage responsible for the provision of aeronautical data and aeronautical information necessary for the safety, regularity and efficiency of air navigation;
    • (f) Applicant: A CAR 561 manufacturer certificate applicant or holder applying for a Type 2 Aeronautical Database Provider (ADP) LOA from TCCA;
    • (g) Compatibility list: A list of the aeronautical products for which a compatible aeronautical database is produced;
    • (h) Data element: A term used to describe any component of a data set (e.g., a feature, an attribute, an object, an entity, or a value);
    • (i) Data Quality Requirements (DQR): A degree or level of confidence that the data provided meets the requirements of the user. The quality requirements may include levels of accuracy, resolution, assurance level, traceability, timeliness, completeness, and format;
    • (j) Data Service Provider (DSP): A person or organisation providing aeronautical database services;
    • (k) Data set: An identifiable collection of data;
    • (l) Delegate: Any person or class of persons authorized under the authority of Subsection 4.3(1) of the Aeronautics Act to perform functions on behalf of the Minister, in the context of this AC, who are subject to the requirements in Chapter 505 of the Airworthiness Manual (AWM);
    • (m) Finding of Compliance (FoC): A Ministerial determination that the applicant’s compliance demonstration satisfies the objectives specified in RTCA DO-200B or EUROCAE ED-76A standard;
    • (n) Letter of Acceptance (LOA): The letter from the FAA or TCCA signifying the regulatory authority’s acceptance of a database provider’s aeronautical data processes. A TCCA Type 2 ADP LOA confirms that the Type 2 ADP meets the RTCA DO-200B or EUROCAE ED-76A standard;
    • (o) Manufacturer: The holder of a type certificate for an aeronautical product or, where no type certificate has been issued by the Minister, the maker of the aeronautical product;
    • (p) Manufacturer certificate: A certificate issued under Subpart 561 of the CARs;
    • (q) Policy Manual: Refers to the manual approved by TCCA under section 561.07 of the CARs;
    • (r) Reportable service difficulty: A service difficulty that affects or, if not corrected, is likely to affect the safety of an aircraft, its occupants or any other person;
    • (s) Service difficulty: A failure or malfunction of, or defect in, an aeronautical product;
    • (t) Statement of Compliance (SoC): A statement from a delegate that a Finding of Compliance has been made;
    • (u) System: A group of inter-dependent processes and people working together to achieve a defined result. A system comprises policies, processes and procedures. It is through systems that enterprises achieve a state of compliance to the regulatory requirements.
    • (v) Type 1 Aeronautical Database Provider (Type 1 ADP): A provider that processes aeronautical data for use on aircraft and provides an aeronautical database meeting the Data Quality Requirements (DQRs), under controlled conditions, for which no specific corresponding airborne application/equipment compatibility has been determined. Examples are EASA Type 1 DAT and FAA Type 1 LOA;
    • (w) Type 2 Aeronautical Database Provider (Type 2 ADP):
      • (i) A provider that processes aeronautical data and provides an aeronautical database for use on certified aircraft application/equipment meeting the DQRs, for which compatibility with that application/equipment has been determined; and
      • (ii) The holder of a LOA from TCCA as a provider of Type 2 aeronautical databases who:
        • (A) Holds a CAR 561 manufacturer certificate for an aeronautical product which the database(s) can be installed in; and
        • (B) Processes aeronautical data and provides an aeronautical database:
          • (I) For use on certified aircraft systems or equipment;
          • (II) That meets the DQRs; and
          • (III) For which compatibility with an aircraft system or equipment has been determined; and
        • (C) Complies with the standard in RTCA DO-200B or EUROCAE ED-76A.
  • (2) The following abbreviations are used in this document:
    • (a) AC: Advisory Circular;
    • (b) ADP: Aeronautical Database Provider, either Type 1 or Type 2 ADP;
    • (c) AIP: Aeronautical Information Publication;
    • (d) DAT: EASA acronym for data provider;
    • (e) DQR: Data Quality Requirements;
    • (f) EASA: European Union Aviation Safety Agency;
    • (g) EU: European Union;
    • (h) EUROCAE: European Organization for Civil Aviation Equipment;
    • (i) FAA: Federal Aviation Administration;
    • (j) FoC: Finding of Compliance;
    • (k) ICAO: International Civil Aviation Organization;
    • (l) LOA: Letter of Acceptance;
    • (m) RNP: Required Navigation Performance;
    • (n) RTCA: Radio Technical Commission for Aeronautics;
    • (o) SoC: Statement of Compliance;
    • (p) TCCA: Transport Canada Civil Aviation;

3.0 Background

3.1 International Civil Aviation Organization (ICAO)

  • (1) ICAO Annex 15 describes that an aeronautical information service (AIS) is required to collect and distribute information needed to ensure the safety, regularity and efficiency of air navigation. Such information, which includes the availability of air navigation facilities and services and the procedures associated with them, must be provided to flight operations personnel, as well as the air traffic services unit responsible for flight information service and the services responsible for pre-flight information.
  • (2) ICAO Annex 15 requires that each Contracting State ensures that the aeronautical data and aeronautical information provided are of the required quality.
  • (3) Since corrupt or erroneous aeronautical information/data may affect air navigation safety, ICAO Member States must ensure that data service providers have a quality system and acceptable quality management procedures at all stages of the aeronautical information/data process (receiving and/or originating, collating or assembling, editing, formatting, publishing, storing and distributing).
  • (4) Data service providers receive, assemble, translate, select, format, distribute and/or integrate aeronautical data and information for use in aeronautical databases to be fed into certified aircraft systems or equipment for the purpose of safety critical air navigation. These providers are typically either accepted or approved by their civil aviation authority.
  • (5) ICAO issued Doc 9613 - Performance-based Navigation (PBN) Manual, which provides further information on data processes for aeronautical data.

3.2 Standards

  • (1) RTCA DO-200B and EUROCAE ED-76A are documents describing the minimum standards for the processing of aeronautical data. They are industry consensus standards used to develop, assess change, and support implementation of data quality management.
  • (2) The RTCA DO-200B and EUROCAE ED-76A standards are considered to be equivalent. Although this AC may refer to the EUROCAE ED-76A document time to time, this AC only provides references to the standard in RTCA DO-200B.

3.3 Foreign Civil Aviation Authorities

  • (1) European Union (EU) Regulation 2017/373 stipulates that starting January 1, 2019, data service providers meeting the requirements of their regulation would require a certificate by the European Union Aviation Safety Agency (EASA). This certificate approves the company as a data service provider but does not confirm compliance with RTCA DO-200B or EUROCAE ED-76A. However, EASA accepts RTCA DO-200B or EUROCAE ED-76A as a means, but not the only means to meet some of the requirements of EU Regulation 2017/373.
  • (2) The FAA issued AC 20-153B about the acceptance of aeronautical data processes and associated databases. The FAA AC can be used to verify and assess compliance regarding aeronautical data processing to RTCA DO-200B. It also explains how data service providers can apply for and obtain airworthiness approval from the FAA. Applicants who comply will receive a Letter of Acceptance (LOA) from the FAA acknowledging their aeronautical data process meets the objectives of the FAA AC. An FAA LOA confirms compliance with RTCA/DO-200B.

3.4 Transport Canada Civil Aviation (TCCA)

  • (1) Transport Canada implemented the ICAO recommendations in AC 700-038 – Performance-based Navigation (PBN) – Enroute.
  • (2) Section 602.60 of the CARs requires that any aircraft operated in instrument flight rules (IFR), in visual flight rules (VFR) over the top (OTT) or in night VFR under Subpart 4 of Part VI or Subpart 2, 3, 4 or 5 of Part VII and using database-dependent navigation equipment must have a current database.
  • (3) In order for Part VII Air Operators and Subpart 604 private operators to receive the special authorization required to operate in designated Required Navigation Performance (RNP) 2 continental airspace, they must meet the applicable operational and aircraft requirements, including navigation database standards. TP 4711 describes the requirements and procedures to obtain RNP2 approval which references AC 700-038. The AC states that operators obtain navigation databases for their aircraft GNSS receivers from a supplier complying with RTCA DO-200 or EUROCAE ED 76 document, Standards for Processing Aeronautical Data, and that the database is compatible with the intended function of the equipment.
  • (4) TCCA’s goal is to harmonise its processes for the acceptance of Type 2 ADP with those of EASA and FAA. For instance, TCCA will issue or amend a CAR 561 manufacturer certificate, and issue a Type 2 ADP LOA, like the FAA, as part of the manufacturer certificate limitations.
  • (5) The manufacturer certificate, together with the TCCA Type 2 ADP LOA, will recognize the approved manufacturer as a Type 2 ADP to process and distribute aeronautical databases for the products they are authorized to manufacture. In addition, the Type 2 ADP LOA will confirm that the Type 2 ADP meets the standard of RTCA DO-200B or EUROCAE ED-76A.
  • (6) Although the Type 2 ADP will hold a CAR 561 manufacturer certificate, it only confirms that the Type 2 ADP meets the requirements of Subpart 561 of the CARs for the aeronautical product they are producing on which an aeronautical database can be installed. The issuance of a Type 2 ADP LOA will add a limitation to the CAR 561 manufacturer certificate allowing the CAR 561 manufacturer certificate holder to process and distribute databases for the products for which they are approved to manufacture. Aeronautical databases are not aeronautical products and are not required to be issued an airworthiness release such as an Authorized Release Certificate.
  • (7) TCCA considers a CAR 561 manufacturer certificate together with an LOA as equivalent to an FAA Type 2 LOA and EASA Type 2 DAT certificate.

4.0 Requirements for Type 2 ADP LOA

  • (1) When applying for a Type 2 ADP LOA, all applicants will need to demonstrate that they:

    • (a) Are the holder of a CAR 561 manufacturer certificate;
    • (b) Are approved to manufacture an aeronautical product on which an aeronautical database can be installed; and
    • (c) Meet the standard in RTCA DO-200B.

  • (2) The application process is as follows:

    • (a) Applicants submit the documents and policy manual to demonstrate compliance to requirements in Subpart 561of the CARs and to the standard in RTCA DO-200B to their responsible TCCA regional office;
    • (b) TCCA regional office and TCCA National Aircraft Certification branch review the documents and policy manual; and
    • (c) TCCA Regional office and TCCA National Aircraft Certification branch conduct an on-site visit to verify implementation of the procedures in the submitted policy manual, and the standard in RTCA DO-200B.

  • (3) An applicant who meets the requirements and standards will receive either a CAR 561 manufacturer certificate, or an amended CAR 561 manufacturer certificate, and a TCCA Type 2 ADP LOA.

    Note: A template of the TCCA Type 2 ADP LOA is available in Appendix A of this AC.

  • (4) The TCCA Type 2 ADP LOA will remain in effect until the CAR 561 manufacturer certificate has been surrendered, suspended or cancelled.

  • (5) The CAR 561 manufacturer certificate, including the TCCA Type 2 ADP LOA, are not transferable.

  • (6) In accordance with section 561.16 of the CARs, the CAR 561 manufacturer certificate holder with a Type 2 ADP LOA must notify TCCA within 30 days of the permanent cessation of the manufacture of an aeronautical database specified in their TCCA Type 2 ADP LOA.

4.1 Application, Issuance, and Amendment

  • (1) The application is submitted to the applicable TCCA Regional Office closest to the applicant.
  • (2) Although this is not necessary, a delegate meeting the requirements of Subchapter C or E of Chapter 505 of the Airworthiness Manual (AWM) and with a scope of authorisation for aeronautical databases may be involved in the application process as follows:
    • (a) To make a Finding of Compliance (FoC) against the objectives specified in RTCA DO-200B with the exception of the requirements in Subpart CAR 561 of the CARs which remains the sole responsibility of the Minister;
    • (b) To document the FoC through TCCA’s standard form for Statement of Compliance (SoC) (26-0757); and
    • (c) To provide the Statement of Compliance (SoC) to the applicant.
  • (3) The application for issuance or amendment is made in accordance with section 561.03 of the CARs and should include the following:
    • (a) A letter to the Minister;
    • (b) A copy of the proposed policy manual or an amendment to the policy manual required by section 561.07 of the CARs, that includes the elements in section 4.4 of this AC and a copy of the Appendix C of this AC duly completed;
    • (c) A copy of the compliance plan as described in RTCA DO-200B, subsection 2.2.1;

      Note: a matrix is available in Appendix B of this AC and should be submitted as part of the application.

    • (d) A draft compatibility list; and
    • (e) If a delegate was involved in the process as per subsection 4.1(2), a copy of the SoC.
  • (4) In addition to the requirements of section 561.03 of the CARs, the letter to the Minister should include the following:
    • (a) A request for a Type 2 ADP LOA;
    • (b) The type of aeronautical database (e.g. navigation, terrain, obstacle, etc.) the applicant wants to add to its scope of work;
    • (c) The aeronautical products associated with the database; and
    • (d) The standard used (e.g. RTCA DO-200B/EUROCAE ED-76A) to produce and distribute aeronautical databases.
  • (5) TCCA may request additional information supporting the application.
  • (6) Following successful review of the policy manual or policy manual amendment required by section 561.07 of the CARs, TCCA will perform an on-site visit to verify compliance with the requirements in Subpart 561 of the CARs and standard RTCA DO-200B.
  • (7) Any changes affecting the CAR 561 manufacturer certificate, the LOA, or the policies in the policy manual are sent to the TCCA regional office for review and approval as applicable. The types of changes may include:
    • (a) Adding or removing an aeronautical product on the compatibility list:
      • (i) A delegate may be involved in the process. In this case, the delegate will follow the procedures in the approved company policy manual;
      • (ii) The Type 2 ADP LOA might have to be amended;
      • (iii) Send a copy of the new compatibility list showing the new aeronautical product; and
      • (iv) TCCA may request additional documents supporting the request.
    • (b) Adding a new aeronautical database to the applicant’s scope of work:
      • (i) Application request for approval to add a new aeronautical database to the scope of work including the following details:
        • (A) The type of aeronautical database (e.g. navigation, terrain, obstacle, etc.) the applicant wants to add to its scope of work;
        • (B) The aeronautical products associated with the database; and
        • (C) The standard used (e.g. RTCA DO-200B or EUROCAE ED-76A) to produce and distribute aeronautical databases.
      • (ii) Send a copy of the amended compatibility list showing the new aeronautical product the new aeronautical database will be installed on;
      • (iii) Send a copy of the policy manual amendment showing the change of scope of work and any other changes due to the request;
      • (iv) TCCA may request additional documents supporting the request; and
      • (v) The TCCA Regional Office will review the request and approve the change of scope of work as applicable.
    • (c) Removing an aeronautical database to the applicant’s scope of work:
      • (i) Application for amendment informing TCCA of the removal of an aeronautical database from the scope of work including the following details:
        • (A) The type of aeronautical database (e.g. navigation, terrain, obstacle, etc.) the applicant wants to remove from its scope of work; and
        • (B) The aeronautical products associated with the database.
      • (ii) Send a copy of the policy manual amendment showing the change of scope of work and any other changes due to the request;
      • (iii) TCCA may request additional documents supporting the request;
      • (iv) If there is a change in the type of database (i.e. navigation, terrain, obstacle, etc.), the LOA will have to be amended to reflect this change; and
      • (v) TCCA Regional Office will review the request and approve the change of scope of work and amend the LOA as applicable.

4.2 Management Personnel

  • (1) The Type 2 ADP should appoint a person to manage the aeronautical database activities.
  • (2) The responsibility for the management of the aeronautical database activities may be assigned to someone in the organization other than the person appointed as per section 561.04 of the CARs to be responsible for the manufacturing activities.
  • (3) The person assigned responsibility for the management of the aeronautical database activities will carry out a management review as per RTCA DO-200B, subsection 2.5.6.

4.3 Resources

  • (1) The expectation is that the resources required for the aeronautical database activities meet the requirements of section 561.05 of the CARs.
  • (2) In addition to the resources required as per section 561.05 of the CARs, the Type 2 ADP should have appropriate resources to perform and manage all aeronautical database activities, including, but not limited to:
    • (a) Tools and test equipment;
    • (b) Competent, trained and authorized personnel; and
    • (c) Access to the applicable standards documentation (e.g., RTCA DO-200B, RTCA DO-330, etc.).

4.4 Policy Manual

  • (1) The Type 2 ADP should establish, maintain, and require the use of policies and procedures described in a policy manual that meets the requirements of section 561.07 of the CARs.
  • (2) The expectation is that the policies remain in the CAR 561 manufacturer policy manual.
  • (3) The policy manual may incorporate other documents by reference provided the policies and procedures for controlling these documents are incorporated into the policy manual (e.g., amendment, approval, distribution, etc.).
  • (4) Unless the Type 2 ADP has policies and procedures to manage changes (other than changes to policies) that are approved by TCCA, any changes to any of its aeronautical database service and/or production control system are to be approved by TCCA prior to their implementation.

    Note: Any changes to the Type 2 ADP’s policy manual are approved by TCCA as per subsection 561.07(5) of the CARs prior to their implementation.

  • (5) The compliance plan described in RTCA DO-200B may be incorporated by reference in the policy manual.
  • (6) Additional guidance is provided in Appendix C of this AC.

4.5 Production Control System

  • (1) The expectation of a Type 2 ADP’s production control system for the aeronautical database activities is that it meets the requirements of section 561.08 of the CARs to ensure that aeronautical databases produced comply with the requirements throughout the production process.
  • (2) In addition, the person assigned responsibility for the management of the aeronautical database activities is responsible for ensuring that:
    • (a) RTCA DO-200B standard is used;
    • (b) A compliance plan is maintained and meets RTCA DO-200B, subsection 2.2.1;
    • (c) DQRs are defined as per RTCA DO-200B, section 2.3;
    • (d) Data processing meets RTCA DO-200B, subsection 2.4.1, as well as the following elements:
      • (i) Data alterations are managed as per RTCA DO-200B, subsection 2.4.2;
      • (ii) Data configuration is managed as per RTCA DO-200B, subsection 2.4.3;
      • (iii) Competencies are defined, maintained, and controlled as per RTCA DO-200B, subsection 2.4.4;
      • (iv) Tool qualification standards are met and procedures followed as per RTCA DO-200B, subsection 2.4.5; and

        Note: RTCA DO-200B, Appendix D provides guidance on tool qualification requirements.

      • (v) Data security standards are met as per RTCA DO-200B, subsection 2.4.6.

        Note: Additional information on data security is available in RTCA DO-200B, Appendix C, section C.8.

    • (e) Verification and validation of the data is performed throughout the entire process to ensure data quality standards are met as per RTCA DO-200B, subsection 2.4.1; and

      Note: Additional information can be found in RTCA DO-200B, Appendix C.2.

    • (f) There is a system in place to detect and report within 72 hours of detection/knowledge:
      • (i) To the operators and/or end-users, any error that could occur during the transmission and/or storage of aeronautical data;
        • (A) The selection of error detection scheme is predicated upon the DQRs as well as the risk of corruption posed by the storage and transmission; and

        Note: RTCA DO-200B Appendix C.2, paragraph C.2.2.1 provides additional information on digital error detection techniques.

      • (ii) To TCCA, operators and/or end-users, suppliers, and design approval holders (as applicable), any database deficiency, error, failure, malfunction that affects or that, if not corrected, is likely to affect the safety of an aircraft, its occupants or any other person;
        • (A) These deficiencies, errors, failures, and/or malfunction should also be reported as per Division IX of subpart 521 of the CARs.
  • (3) The Type 2 ADP should manage, assess and, if necessary, mitigate the impact of changes to its aeronautical database services and production control system. This includes any changes to:
    • (a) The supply of new data type by a known or new supplier;
    • (b) Type 2 ADP’s procedures;
    • (c) Human resources;
    • (d) Tools and equipment used in the making and distribution of aeronautical databases.

    Note: As per RTCA DO-200B, paragraph 2.5.3.1, the Type 2 ADP should have acceptable procedures in place before receiving the new data.

  • (4) The Type 2 ADP should notify its customers, operators and/or end-users of any changes to the LOA status before the users implement the next data update.
  • (5) The Type 2 ADP should inform its responsible TCCA regional office of any changes that impact the LOA, the aeronautical database services it provides, or its production control system.
  • (6) The DQRs are characterized as follows:
    • (a) Accuracy, meaning the degree of conformance between the estimated or measured value and the true value;
    • (b) Resolution, meaning the number of units or digits to which a measured or calculated value is expressed and used;
    • (c) Integrity (of data), meaning the degree of assurance that an aeronautical data and its value has not been lost or altered since the data origination or authorized amendment;
    • (d) Timeliness, meaning the degree of confidence that the data is applicable to the period of its intended use;
    • (e) Completeness, meaning the degree of confidence that all of the data needed to support the intended use is provided;
    • (f) Traceability, meaning the ability of a system or data product to provide a record of the changes made to that product and thereby enables an audit trail to be followed from the end-user to the data originator; and
    • (g) Format, meaning the structure of data elements, records and files arranged to meet standards, specifications or data quality requirements;

      Note: RTCA DO-200B Appendix B provides additional information on defining DQRs.

4.6 Quality Assurance Program

  • (1) The expectation is that the quality assurance program meets the requirements of section 561.09 of the CARs and should be responsive to any changes to the Type 2 ADP that could affect the policy manual or the scope of work under the CAR 561 manufacturer certificate.
  • (2) The Type 2 ADP should ensure that all aeronautical database activities controlled by the policy manual are audited by the quality assurance program, including, but not limited to:
    • (a) Compliance plan;
    • (b) DQRs process and documentation;
    • (c) Data alteration process and documentation;
    • (d) Data configuration process and documentation;
    • (e) Personnel competencies, including training and authorizations;
    • (f) Tool qualification process and documentation;
    • (g) Data security and documentation;
    • (h) Error reporting process and documentation;
    • (i) Data validation and verification process and documentation;
    • (j) Database release statement issuance and records;
    • (k) Control of suppliers process;
    • (l) Records management process.
  • (3) The audit conducted under the quality assurance program should ensure that the standards defined in RTCA DO-200B section 3 are met. The objectives defined in the matrix in Appendix B of this AC may be used as part of the audit.

    Note: The standard defined in RTCA DO-200B can be verified by utilizing the compliance matrix in Appendix F of RTCA/DO-200B.

  • (4) The Type 2 ADP is expected to conduct periodic audits to verify compliance with items (1) to (3) above at intervals not to exceed one year as per RTCA DO-200B, section 3.3.
  • (5) In addition to the procedures required under section 561.09 of the CARs, the Type 2 ADP should ensure the audit procedures defined in RTCA DO-200B section 3.3 are followed.
  • (6) The audit report is expected to meet the standard in section 3.4 of RTCA DO-200B.
  • (7) The quality assurance program should ensure that the aeronautical data, while taking into consideration its intended use, meets the DQRs listed in subsection 4.5(6) of this AC.
  • (8) The quality assurance program should ensure that any deficiencies, errors, failures, and malfunctions that are detected in use or during production are analysed, the root cause identified, and once corrected, the correction is communicated to the affected users. Refer to RTCA DO-200B, subsection 1.5.5.7 and 2.5.3.

    Note: This can be facilitated by the use of metadata, so the Type 2 ADP is able to trace any issue with the aeronautical data throughout the aeronautical information data chain, as required.

  • (9) Changes to a Type 2 ADP’s aeronautical database service and/or production control system should be assessed through the quality assurance program.
  • (10) The quality assurance program should ensure that changes to DQRs, including the identification of non-compliant data elements, are properly assessed before signing the database release statement and distributing the database as required in RTCA DO-200B, subsection 2.3.5:
    • (a) RTCA DO-200B, Appendix C, section C.2 provides an acceptable method to assess changes to the DQRs and for the identification of non-compliant data elements.
    • (b) Data with non-compliant elements that do not meet the assurance levels identified in RTCA DO-200B, Appendix B, subsection B.1.3, should be identified as assurance level 4, indicating it may not satisfy safety objectives.
    • (c) Level 4 data should be distinguishable from any compliant data through means acceptable to TCCA.
    • (d) The operator / end-user is ultimately responsible for ensuring level 4 data meets the quality requirements for its intended use.
  • (11) The quality assurance program should include provisions for immediate reaction to an unsafe condition.

    Note: An unsafe condition is any database deficiency, error, failure, or malfunction that affects or that, if not corrected, is likely to affect the safety of an aircraft, its occupants or any other person, including but not limited to:

    • Aircraft deviation from a published procedure;
    • Erroneous warning (red colour) in the cockpit (e.g. PULL UP, TERRAIN, RWY TOO SHORT);
    • Pilot workload increase due to presentation of misleading or conflicting data in the primary flight display; and
    • Malfunction or defect of an indication system at a critical phase of the flight, etc.
  • (12) Information to correct an unsafe condition is expected to be communicated to each user, owner and operator within 72 hours of the Type 2 ADP’s becoming aware of the unsafe condition.

4.7 Database Release Statement

  • (1) The Type 2 ADP is expected to provide a database release statement with each database distribution. The database release statement should meet the standard in subsection 2.3.5 of RTCA DO-200B.
  • (2) An Authorized Release Certificate – TCCA Form One is not used as a release statement as the database is not aeronautical product and does not require airworthiness release. The database release statement is used as a certificate of compliance attesting that the subject database has been produced in compliance with Subpart 561 of the CARs and the standard in RTCA DO-200B. It is signed by an authorized person under the CAR 561 manufacturer certificate.
  • (3) There is no specified format for the database release statement and may be in an electronic format including electronically signed. However, the database release statement should include the following elements:
    • (a) LOA status;
    • (b) LOA issued date;
    • (c) Name and address of the manufacturer;
    • (d) TCCA manufacture certificate approval number;
    • (e) Compliance statement;

      Note: An acceptable compliance statement is: “databases released and distributed by [Type 2 ADP’s name] are produced in compliance with CAR 561 manufacturer certificate approval and generated in accordance with the standards in RTCA DO-200B [or EUROCAE ED-76A]”.

    • (f) Standard used (e.g. RTCA DO-200B/EUROCAE ED-76A);
    • (g) Data compatibility (e.g. list of products the database could be used with);
    • (h) Any deviations to the agreed DQRs;
    • (i) Any data alterations;
    • (j) Name and signature of authorized person; and
    • (k) Date of signature.
  • (4) The person signing the database release statement should be authorized as per the Type 2 ADP’s policies and procedures and be trained in accordance with the training program.
  • (5) The database release statement is only issued for a product specified on the compatibility list in accordance with the CAR 561 manufacturer certificate approval.

4.8 Training Program

  • (1) A Type 2 ADP should have a training program that meets the requirements of section 561.11 of the CARs to ensure continued qualification of personnel.
  • (2) The Type 2 ADP should ensure through the initial training that persons performing functions and persons supervising the performance of any function in the aeronautical database activities, including persons authorized to sign a database release statement, are aware of their technical, administrative, and regulatory responsibilities as per RTCA DO-200B, subsection 2.4.4 and Subpart 561 of the CARs.
  • (3) The Type 2 ADP should ensure through the update training that persons performing functions and persons supervising the performance of any function in the aeronautical database activities are made aware of any change to their area of responsibility as per RTCA DO-200B, subsection 2.4.4.
  • (4) The Type 2 ADP should ensure through additional training that persons performing functions and persons supervising the performance of any function in the aeronautical database activities are made aware of any changes to the CARs and associated Standards, RTCA DO-200B, and the Type 2 ADP’s policies and procedures with regards to RTCA DO-200B activities.
  • (5) The training program should include provisions to ensure that persons authorized to sign the database release statement have the required competencies as per subparagraph 4.5(2)(d)(iii), have received proper training as per items (2), (3), and (4) above, and authorized as per the Type 2 ADP’s policies and procedures.
  • (6) The training program should include training for personnel involved in the auditing of the Type 2 ADP’s aeronautical database activities.
  • (7) The training update cycle should not exceed three years.
  • (8) The Type 2 ADP should keep a record of the personnel training as per section 4.10 of this AC.

4.9 Control of Suppliers

  • (1) The expectation is that the control of suppliers meets the requirements of section 561.13 of the CARs. This includes data suppliers.
  • (2) The end-user is ultimately responsible for ensuring data meets the quality for its intended use. However, there is a shared responsibility at all levels of the aeronautical data chain to ensure that the data or service provided meet the standard in RTCA DO-200B [refer to DO-200B, section 1.5 and paragraph 2.3.3 (3)]. Examples of suppliers may include Type 1 aeronautical database providers or tool providers.
  • (3) The Type 2 ADP should establish a process to control suppliers which includes a written agreement with suppliers that specifies the work to be performed.
  • (4) The written agreement between the Type 2 ADP and its suppliers should include a statement that the Minister may have access to and inspect the supplier’s facilities and records to ensure compliance with the applicable regulations.
  • (5) The Type 2 ADP should have a process to evaluate and monitor its supplier’s capability to perform the contracted work.
  • (6) The Type 2 ADP should ensure contracted work is done under its supervision and is subject to its quality assurance program.
  • (7) The Type 2 ADP should verify and validate data sourced from a non-authoritative source, or from a supplier with a foreign LOA that complies with a standard predating RTCA DO-200B.

    Note: RTCA DO-200B, Appendix C, section C.2 provides an acceptable method to verify and validate the data integrity and quality.

4.10 Records

  • (1) The Type 2 ADP should maintain a record-keeping system that meets the requirements of sections 561.12 of the CARs for personnel records and 561.14 of the CARs for product records.
  • (2) Documents should be controlled as per RTCA DO-200B, subsection 2.5.4.
  • (3) Records for data set or element set should meet the data configuration management standard as per RTCA DO-200B, paragraph 2.4.3.2.
  • (4) Records of all data alterations should be kept as per RTCA DO-200B, subsection 2.4.2. These records must also be made available to all subsequent users upon their request.
  • (5) Records related to the implementation of data security provisions as required by RTCA DO-200B, subsection 2.4.1, items 1, 3, and 12, should be maintained as per RTCA DO-200B, subsection 2.4.6.
  • (6) In addition, appropriate records should be established and maintained for:
    • (a) Initial and periodic audits of all aeronautical database activities, including records of compliance and non-compliance, findings, corrective actions, and follow-ups;
    • (b) Database deficiencies, errors, failures, and malfunctions identified, and reported;
    • (c) Qualifications, training, and authorization of all personnel involved in the aeronautical database activities;
    • (d) Any changes assessed as part of the production control system; and
    • (e) Any management review as per RTCA DO-200B, subsection 2.5.6.
  • (7) Records should show the procedure, personnel, and tools used during production of each delivery of data to a user as per RTCA DO-200B, subsection 2.5.2.
  • (8) Records may be of physical or electronic nature.
  • (9) Records should be protected by appropriate means against inadvertent loss or destruction and against tampering, and kept for at least three years.

5.0 Surveillance Activities

5.1 Surveillance of Type 2 ADP Activities

  • (1) TCCA’s surveillance program includes assessments, Program Validation Inspections (PVIs) and Process Inspections (PIs). The surveillance program verifies that Type 2 ADPs are complying with regulatory requirements and that they have effective systems in place to ensure they comply with regulatory requirements on an on-going basis.
  • (2) TCCA’s surveillance program also focuses on verifying that the Type 2 ADP meets the requirements of CAR 561 as well as RTCA DO-200B/EUROCAE ED-76A.

6.0 Information Management

  • (1) Not applicable.

7.0 Document History

  • (1) Not applicable.

8.0 Contact us

For more information, please contact:
Jeffrey Phipps
Chief, Operational Airworthiness (AARTM)
Telephone: 613-952-4386
E-mail: jeff.phipps@tc.gc.ca

We invite suggestions for amendment to this document. Submit your comments to:
AART Documentation Services:
E-mail: AARTDocServices-ServicesdocAART@tc.gc.ca

Document approved by

Charles Lanning
A/Director, Standards Branch
Civil Aviation

Appendix A — Sample of a Transport Canada Civil Aviation Type 2 ADP LOA

[Add Date]

[Name of the Accountable Executive]
Accountable Executive
[Company Name]
[Address]

Transport Canada Civil Aviation
Type 2 Aeronautical Database Provider Letter of Acceptance
for [Company Name]’ Aeronautical Data Process

Dear [Name of the Accountable Executive]

This Type 2 Aeronautical Database Provider (ADP) Letter of Acceptance (LOA) is issued to [Company Name], holder of CAR 561 manufacturer certificate [Approval Number], based on [Company Name]’s Aeronautical Database Process meeting standards of RTCA DO-200B. [Company Name] is now recognized as a TCCA Type 2 ADP.

This letter and its reference in [Company Name] CAR 561 manufacturing certificate provide [Company Name] the authority to process [add the type of database, i.e.: navigation, terrain, obstacle, etc…] databases for the products listed as part of their certificate approval.

For this Type 2 ADP LOA, compatibility has been established with

“the product lines enumerated in document [Add document name and reference] Revision "-" or later approved revision”,

(or)

“the following product line: [list the specific products]”

TCCA continues to retain oversight authority and surveillance over the process.

The CAR 561 manufacturer certificate [issuance or amendment] together with this LOA is not transferable and remains effective until surrendered by the holder, suspended or otherwise cancelled by TCCA.

The following terms and conditions form an integral part of this LOA:

  1. This LOA remains in effect until the CAR 561 manufacturer certificate is surrendered, suspended, or cancelled, or the CAR 561 manufacturer certificate has been surrendered, suspended or cancelled.
  2. [Company Name] adheres to the procedures identified in its RTCADO-200B compliance plan – [Add document name and reference] – with regards to DQRs and data processing, and to [Company Name]’s CAR 561 approved manufacturer’s policy manual.
  3. [Company Name] reports to TCCA any failure, malfunction, or defect of the aeronautical data produced under this LOA having a potential safety effect on operational use of the data.
  4. [Company Name] provides a database release statement with each database distribution to broadcast LOA status, state their compliance, and provide information on known deviations and modifications.
  5. [Company Name] performs periodic internal audits as described in RTCA DO-200B section 3, and in accordance with [Company Name]'s [Add document name and reference], at least once every twelve months. Any major non-conformity as described in RTCA DO-200B section 3.4 is reported to TCCA. Additionally, [Company Name] supports TCCA surveillance activities.
  6. [Company Name] advises their customers of the status of the TCCA LOA as well as any change in status of LOAs (or foreign acceptance, including designation of the foreign authority that acknowledges the foreign source's compliance to RTCA DO-200B and the means of approval or acceptance) for all previous chain participants up to, but not including, a State's Aeronautical Information Publication (AIP). The method of notification is timely to ensure that customers can react to changes in the status of its LOA.

If further information concerning this letter is needed, please contact your TCCA regional office.

For the Minister,

[Name and position of the Manager],
Airworthiness and Manufacturing
[Name of region]

Appendix B — Objectives Matrix

Appendix C — Guidance on Policy Manual Requirements

  • (1) The following guidance is in addition to the information provided in section 4.4 of this AC.
  • (2) This appendix represents the minimum expected content that is to be included in the required policy manual under section 4.4 of this AC.

AC 561-004 - Acceptance of Type 2 Aeronautical Database Providers
(PDF, 588 KB)

 

Report a problem with this page

Date modified: