Light
Dark
System
Log In
Loading...
Compare / EASA/
Incorporated Amendments
/
Compare & Highlight Differences
AMC2 NCC.GEN.106 Pilot-in-command responsibilities and authority
Available versions for ERULES-1963177438-13219
ED Decision 2013/021/R
found in: Air Operations (965/2012) Part-ARO Part-ORO Part-CAT Part-SPA Part-NCC Part-NCO Part-SPO (Sep 2023)
From
Air Operations Rev... (Mar 2026)
Air Operations (96... (Feb 2025)
Air Operations (96... (Sep 2023)
From section
To
Air Operations Rev... (Mar 2026)
Air Operations (96... (Feb 2025)
Air Operations (96... (Sep 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
AMC2 NCC.GEN.106 Pilot-in-command responsibilities and authority ED Decision 2013/021/R DATABASE SUITABILITY (a) The flight crew should check that any navigational database required for PBN operations includes the routes and procedures required for the flight. DATABASE CURRENCY (b) The database validity (current AIRAC cycle) should be checked before the flight. (c) Navigation databases should be current for the duration of the flight. If the AIRAC cycle is due to change during flight, the flight crew should follow procedures established by the operator to ensure the accuracy of navigation data, including the suitability of navigation facilities used to define the routes and procedures for the flight. (d) An expired database may only be used if the following conditions are satisfied: (1) the operator has confirmed that the parts of the database which are intended to be used during the flight and any contingencies that are reasonable to expect are not changed in the current version; (2) any NOTAMs associated with the navigational data are taken into account; (3) maps and charts corresponding to those parts of the flight are current and have not been amended since the last cycle; (4) any MEL limitations are observed; and (5) the database has expired by no more than 28 days.
AMC2 NCC.GEN.106 Pilot-in-command responsibilities and authority ED Decision 2013/021/R DATABASE SUITABILITY (a) The flight crew should check that any navigational database required for PBN operations includes the routes and procedures required for the flight. DATABASE CURRENCY (b) The database validity (current AIRAC cycle) should be checked before the flight. (c) Navigation databases should be current for the duration of the flight. If the AIRAC cycle is due to change during flight, the flight crew should follow procedures established by the operator to ensure the accuracy of navigation data, including the suitability of navigation facilities used to define the routes and procedures for the flight. (d) An expired database may only be used if the following conditions are satisfied: (1) the operator has confirmed that the parts of the database which are intended to be used during the flight and any contingencies that are reasonable to expect are not changed in the current version; (2) any NOTAMs associated with the navigational data are taken into account; (3) maps and charts corresponding to those parts of the flight are current and have not been amended since the last cycle; (4) any MEL limitations are observed; and (5) the database has expired by no more than 28 days.
##### AMC2 NCC.GEN.106 Pilot-in-command responsibilities and authority *ED Decision 2013/021/R* **DATABASE SUITABILITY** (a) The flight crew should check that any navigational database required for PBN operations includes the routes and procedures required for the flight. **DATABASE CURRENCY** (b) The database validity (current AIRAC cycle) should be checked before the flight. (c) Navigation databases should be current for the duration of the flight. If the AIRAC cycle is due to change during flight, the flight crew should follow procedures established by the operator to ensure the accuracy of navigation data, including the suitability of navigation facilities used to define the routes and procedures for the flight. (d) An expired database may only be used if the following conditions are satisfied: (1) the operator has confirmed that the parts of the database which are intended to be used during the flight and any contingencies that are reasonable to expect are not changed in the current version; (2) any NOTAMs associated with the navigational data are taken into account; (3) maps and charts corresponding to those parts of the flight are current and have not been amended since the last cycle; (4) any MEL limitations are observed; and (5) the database has expired by no more than 28 days.
Contact support