AMC2 NCO.GEN.105 Pilot-in-command responsibilities and authority

• ED Decision 2016/018/R found in: Air Operations (965/2012) Part-ARO Part-ORO Part-CAT Part-SPA Part-NCC Part-NCO Part-SPO (Feb 2025)

AMC2 NCO.GEN.105 Pilot-in-command responsibilities and authority ED Decision 2016/018/R DATABASE SUITABILITY (a) The pilot-in-command 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 pilot-in-command should follow procedures established by the pilot-in-command 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 pilot-in-command 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, where available, are observed; and (5) the database has expired by no more than 28 days. AMC2 NCO.GEN.105 Pilot-in-command responsibilities and authority ED Decision 2016/018/R DATABASE SUITABILITY (a) The pilot-in-command 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 pilot-in-command should follow procedures established by the pilot-in-command 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 pilot-in-command 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, where available, are observed; and (5) the database has expired by no more than 28 days. ##### AMC2 NCO.GEN.105 Pilot-in-command responsibilities and authority *ED Decision 2016/018/R* **DATABASE SUITABILITY** (a) The pilot-in-command 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 pilot-in-command should follow procedures established by the pilot-in-command 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 pilot-in-command 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, where available, are observed; and (5) the database has expired by no more than 28 days.