Light
Dark
System
Log In
Loading...
Compare / EASA/
Incorporated Amendments
/
Compare & Highlight Differences
AMC1 DAT.OR.100 Aeronautical data and information
Available versions for ERULES-1963177438-3530
ED Decision 2017/001/R
found in: ATM/ANS Provision of Services (2017/373) (Mar 2025)
From
ATM/ANS Provision ... (Mar 2025)
ATM/ANS Provision ... (Feb 2023)
From section
To
ATM/ANS Provision ... (Mar 2025)
ATM/ANS Provision ... (Feb 2023)
To section
No visible text changes
0 removals
0 additions
View
Rich
Plain
Sync scrolling
Share
From
Show details
Hide details
To
Show details
Hide details
Version
Show side by side
AMC1 DAT.OR.100 Aeronautical data and information ED Decision 2017/001/R 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)).
AMC1 DAT.OR.100 Aeronautical data and information ED Decision 2017/001/R 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)).