DAT.OR.100 Aeronautical data and information

GENERAL

(a)Aeronautical data and information in this context should consist of:

(1)Integrated Aeronautical Information Package (IAIP); and/or

(2)obstacle data; and/or

(3)terrain data; and/or

(4)Aerodrome Mapping Data (AMD); and/or

(5)other data and information that is validated by the DAT provider for the purpose of provision of its services.

(b)Aeronautical databases should be databases, used on certified aircraft application/equipment, that support the flight operation where incorrect data leads to failures having at least minor or higher failure effect.

(c)The scope should not include databases that are approved as part of the type design of the aircraft or engine (e.g. engine power settings (take-off, climb, maximum continuous thrust (MCT), cruise) and aircraft performance data (e.g. take-off distance, V speeds)).

GENERAL

(a)In the context of this Regulation, aeronautical databases should include databases, used on certified aircraft applications, that support the flight operation of aircraft for the purpose of primary communication, navigation and surveillance (CNS) or supplementing CNS.

(1)Database used in primary CNS applications (e.g. flight management system (FMS)).

(2)Database used in supplementary CNS applications including but not limited to systems generating alerts and used for awareness having the following databases:

(i)database for synthetic vision systems;

(ii)terrain database (TAWS);

(iii)obstacle database (TAWS);

(iv)aerodrome mapping database (AMDB);

(v)brake assistance to vacate; and

(vi)surface indication and alert system.

(b)Databases for which the DAT provider is not required to be certified in accordance with this Regulation include but are not limited to:

(1)databases provided and/or used by the operator of the aircraft that are monitored under the operator’s responsibility and not loaded into certified aircraft applications (e.g. airport moving map used in electronic flight bags (EFBs), take-off and landing performance used in EFBs);

(2)databases not having any safety affect (e.g. used for passenger in-flight entertainment (IFE) systems outside the flight deck, etc.); and

(3)databases for systems applications/equipment installed on aircraft certified for visual flight rules (VFR) operation only, except those used for primary navigation to meet the airspace usage requirements.

DATA SOURCE The DAT provider should use data coming from authoritative sources. If such data is not formally made available by an authoritative source or does not meet the applicable data quality requirements, but is required by end users, the DAT provider may use data from other (non-authoritative) sources, provided these have been verified and validated by the DAT provider itself and/or other DAT providers to conform with the relevant standards and data quality requirements. If a non-authoritative source is used for the data release, the DAT provider should issue a statement at its discretion.

VALIDATION OF AERONAUTICAL DATA The processes of validating the aeronautical data by DAT provider should meet the standards specified in EUROCAE ED-76A/RTCA DO-200B ‘Standards for Processing Aeronautical Data’, dated June 2015, especially Section 2.4.1 (6) and Appendix C, in particular points C.2.1 and C.2.2. EUROCAE ED-76/RTCA DO-200A may be also used for the demonstration of compliance.

GENERAL

(a)The full responsibility for the origination and provision of tailored data and its subsequent updates, as required, should lie with the aircraft operator.

(b)The origination and provision of tailored data by an aircraft operator or on the aircraft operator’s behalf for the purpose of air operation is not part of the DAT provider’s scope of activities and this Regulation does not cover its oversight.

(c)The use of tailored data is related and limited to the operational purposes of the aircraft operator that requested the insertion of the tailored data.