AMC 21.A.95 Requirements for the approval of a minor change

• ED Decision 2019/018/R found in: Initial Airworthiness and Environmental Protection (748/2012) Part-21 Part-21L (Jul 2024)

AMC 21.A.95 Requirements for the approval of a minor change ED Decision 2019/018/R (a)     Applicability of point [21.A.95](#_DxCrossRefBm1649097048) Point [21.A.95](#_DxCrossRefBm1649097049) has to be complied with by applicants for the approval of a minor change to a type certificate (TC), and by design organisation approval (DOA) holders that approve minor changes under their own privileges. Point [21.A.95](#_DxCrossRefBm1649097008)(e), however, only applies to projects for which an application is submitted to EASA. For DOA holders that approve minor changes under their privileges, the substantiating data and the statement of compliance required by point [21.A.95](#_DxCrossRefBm1649096961)(e) should be produced but do not need to be submitted to EASA. They should be, however, kept on record and submitted to EASA on request during its DOA continued surveillance process. (b)     The approval process The approval process comprises the following steps: Note:   Steps 1, 2 and 5 should be followed only by applicants for minor changes approved by EASA. DOA holders that approve minor changes under their privileges should refer to AMC No 1 to 21.A.263(c)(2) or AMC No 2 to 21.A.263(c)(2), as applicable to their approval process. (1)     Application When the minor change is approved by EASA, an application should be submitted to EASA as described in point [21.A.93](#_DxCrossRefBm1649097008)(a) and (b) and in [AMC 21.A.93(a)](#_DxCrossRefBm1649097045). (2)     Certification programme The certification programme should consist of the information defined in points [21.A.93](#_DxCrossRefBm1649097008)(b)(1) and [21.A.93](#_DxCrossRefBm1649097008)(b)(2). Please refer to [AMC 21.A.93(b)](#_DxCrossRefBm1649096960) for further information. (3)     Certification basis (4)     Demonstration of compliance (5)     Statement of compliance (c)      Certification basis The certification basis for a minor change consists of a subset of the elements of the product’s certification basis ‘incorporated by reference in the type certificate’ (see also the additional guidance below on the meaning of certification specifications that became applicable after those ‘incorporated by reference in the type certificate’), which have been identified in accordance with point [21.A.93](#_DxCrossRefBm1649097008)(b)(2) due to a reinvestigation of compliance being necessary because compliance was affected by the minor change (see also additional guidance below on the meaning of ‘specific configurations’). The certification basis ‘incorporated by reference in the type certificate’ is the certification basis for the product as recorded in the type certificate data sheet (TCDS) for the product type/model in the configuration(s) identified in accordance with point [21.A.93](#_DxCrossRefBm1649096851)(b)(1)(i). The certification basis contains the applicable airworthiness and (for aircraft only) operational suitability data certification specifications (CS‑OSD), environmental protection requirements specified by reference to their amendment level, as complemented by special conditions, equivalent safety findings, deviations, an ‘elect to comply’, etc., as applicable. See also the additional guidance below on the meaning of ‘Minor changes affecting OSD constituents’. By derogation from the above, CSs that became applicable after those incorporated by reference in the TC may be used for the approval of a minor change (see the guidance below on certification specifications that became applicable after those ‘incorporated by reference in the type certificate’). If other changes are required for the embodiment of the minor change, the certification basis corresponding to the product modified by these other changes should also be considered when determining the certification basis for the minor change. (d)     Demonstration of compliance required by point [21.A.95](#_DxCrossRefBm1649096851)(b)(1) and (2) The applicant needs to demonstrate compliance with the certification basis established for the minor change for all areas that are either physically changed or functionally affected by the minor change. (1)     Means of compliance: the applicant should define and record the means (calculation, test or analysis, etc.) by which compliance is demonstrated. [Appendix A to AMC 21.A.15(b)](#_DxCrossRefBm1649096851) may be used to describe how compliance is demonstrated. (2)     Compliance documents: the compliance demonstration should be recorded in compliance documents. For minor changes, one comprehensive compliance document may be sufficient, provided that it contains evidence of all aspects of the compliance demonstration. [AMC 21.A.20(c)](#_DxCrossRefBm1649096851) can also be used, where applicable. See also the additional guidance in item (e). (3)     Aircraft manuals: where applicable, supplements to manuals (e.g. aircraft flight manual (AFM), aircraft maintenance manual (AMM), etc.) may be issued. See also additional guidance below on embodiment/installation instructions (item (f)). (e)     Definition of the change to the type certificate The change to the type certificate should be defined in accordance with [GM 21.A.90A](#_DxCrossRefBm1649097008). (f)      Embodiment/installation instructions The instructions for the embodiment/installation of the change (e.g. service bulletin, modification bulletin, production work order, etc.) should be defined. This may include the installation procedure, the required material, etc. (g)     Minor changes affecting OSD constituents (i.e. master minimum equipment list (MMEL)) Some minor changes to the type design may only have an effect on the MMEL (see [GM No 1 to 21.A.93(b)(1)(iii)](#_DxCrossRefBm1649097054)). In such cases, [GM No 2 to 21.A.93(b)(1)(iii)](#_DxCrossRefBm1649096959) is also applicable. This also means that a dedicated assessment of the effects of the minor type design change on the other OSD constituents is not needed. (h)     Meaning of ‘specific configurations’ in point [21.A.95](#_DxCrossRefBm1649096851)(f) These ‘specific configurations’ are defined as the combination of the product type/model (on which the minor change will be installed) with (if applicable) the list of those already approved changes (minor, major, supplemental type certificate (STC)) that are required for the installation of the minor change. (i)      Certification specifications that became applicable after those incorporated by reference in the type certificate (1)     Minor changes are those changes that do not affect the airworthiness of the product and thus are, by definition, non-significant as per point [21.A.101](#_DxCrossRefBm1649096998). This means that the certification basis for the minor change may consist of the items of the certification basis incorporated by reference in the TCDS of the product type/model, and normally it should not be necessary for a minor change to use certification specifications that became applicable after those that are incorporated by reference in the type certificate. (2)     On the other hand, the applicant may elect to use later amendments of the affected certification specifications for the compliance demonstration. This does not affect the classification of the change; however, the applicant should also comply with any other certification specifications that EASA considers to be directly related. (3)     If other changes are required for the installation of the minor change (as explained in ‘specific configurations’), the certification basis for the minor change should also take into account the corresponding certification basis. (j)      Meaning of ‘no feature or characteristics’ in point [21.A.95](#_DxCrossRefBm1649096851)(b)(4) See [GM 21.A.20(d)](#_DxCrossRefBm1649097030). ##### AMC 21.A.95 Requirements for the approval of a minor change *ED Decision 2019/018/R* (a) Applicability of point [21.A.95](#_DxCrossRefBm485230539) Point [21.A.95](#_DxCrossRefBm485230540) has to be complied with by applicants for the approval of a minor change to a type certificate (TC), and by design organisation approval (DOA) holders that approve minor changes under their own privileges. Point [21.A.95](#_DxCrossRefBm485230499)(e), however, only applies to projects for which an application is submitted to EASA. For DOA holders that approve minor changes under their privileges, the substantiating data and the statement of compliance required by point [21.A.95](#_DxCrossRefBm485230452)(e) should be produced but do not need to be submitted to EASA. They should be, however, kept on record and submitted to EASA on request during its DOA continued surveillance process. (b) The approval process The approval process comprises the following steps: Note: Steps 1, 2 and 5 should be followed only by applicants for minor changes approved by EASA. DOA holders that approve minor changes under their privileges should refer to AMC No 1 to 21.A.263(c)(2) or AMC No 2 to 21.A.263(c)(2), as applicable to their approval process. (1) Application When the minor change is approved by EASA, an application should be submitted to EASA as described in point [21.A.93](#_DxCrossRefBm485230499)(a) and (b) and in [AMC 21.A.93(a)](#_DxCrossRefBm485230536). (2) Certification programme The certification programme should consist of the information defined in points [21.A.93](#_DxCrossRefBm485230499)(b)(1) and [21.A.93](#_DxCrossRefBm485230499)(b)(2). Please refer to [AMC 21.A.93(b)](#_DxCrossRefBm485230451) for further information. (3) Certification basis (4) Demonstration of compliance (5) Statement of compliance (c) Certification basis The certification basis for a minor change consists of a subset of the elements of the product’s certification basis ‘incorporated by reference in the type certificate’ (see also the additional guidance below on the meaning of certification specifications that became applicable after those ‘incorporated by reference in the type certificate’), which have been identified in accordance with point [21.A.93](#_DxCrossRefBm485230499)(b)(2) due to a reinvestigation of compliance being necessary because compliance was affected by the minor change (see also additional guidance below on the meaning of ‘specific configurations’). The certification basis ‘incorporated by reference in the type certificate’ is the certification basis for the product as recorded in the type certificate data sheet (TCDS) for the product type/model in the configuration(s) identified in accordance with point [21.A.93](#_DxCrossRefBm485230341)(b)(1)(i). The certification basis contains the applicable airworthiness and (for aircraft only) operational suitability data certification specifications (CS‑OSD), environmental protection requirements specified by reference to their amendment level, as complemented by special conditions, equivalent safety findings, deviations, an ‘elect to comply’, etc., as applicable. See also the additional guidance below on the meaning of ‘Minor changes affecting OSD constituents’. By derogation from the above, CSs that became applicable after those incorporated by reference in the TC may be used for the approval of a minor change (see the guidance below on certification specifications that became applicable after those ‘incorporated by reference in the type certificate’). If other changes are required for the embodiment of the minor change, the certification basis corresponding to the product modified by these other changes should also be considered when determining the certification basis for the minor change. (d) Demonstration of compliance required by point [21.A.95](#_DxCrossRefBm485230341)(b)(1) and (2) The applicant needs to demonstrate compliance with the certification basis established for the minor change for all areas that are either physically changed or functionally affected by the minor change. (1) Means of compliance: the applicant should define and record the means (calculation, test or analysis, etc.) by which compliance is demonstrated. [Appendix A to AMC 21.A.15(b)](#_DxCrossRefBm485230341) may be used to describe how compliance is demonstrated. (2) Compliance documents: the compliance demonstration should be recorded in compliance documents. For minor changes, one comprehensive compliance document may be sufficient, provided that it contains evidence of all aspects of the compliance demonstration. [AMC 21.A.20(c)](#_DxCrossRefBm485230341) can also be used, where applicable. See also the additional guidance in item (e). (3) Aircraft manuals: where applicable, supplements to manuals (e.g. aircraft flight manual (AFM), aircraft maintenance manual (AMM), etc.) may be issued. See also additional guidance below on embodiment/installation instructions (item (f)). (e) Definition of the change to the type certificate The change to the type certificate should be defined in accordance with [GM 21.A.90A](#_DxCrossRefBm485230499). (f) Embodiment/installation instructions The instructions for the embodiment/installation of the change (e.g. service bulletin, modification bulletin, production work order, etc.) should be defined. This may include the installation procedure, the required material, etc. (g) Minor changes affecting OSD constituents (i.e. master minimum equipment list (MMEL)) Some minor changes to the type design may only have an effect on the MMEL (see [GM No 1 to 21.A.93(b)(1)(iii)](#_DxCrossRefBm485230545)). In such cases, [GM No 2 to 21.A.93(b)(1)(iii)](#_DxCrossRefBm485230450) is also applicable. This also means that a dedicated assessment of the effects of the minor type design change on the other OSD constituents is not needed. (h) Meaning of ‘specific configurations’ in point [21.A.95](#_DxCrossRefBm485230341)(f) These ‘specific configurations’ are defined as the combination of the product type/model (on which the minor change will be installed) with (if applicable) the list of those already approved changes (minor, major, supplemental type certificate (STC)) that are required for the installation of the minor change. (i) Certification specifications that became applicable after those incorporated by reference in the type certificate (1) Minor changes are those changes that do not affect the airworthiness of the product and thus are, by definition, non-significant as per point [21.A.101](#_DxCrossRefBm485230489). This means that the certification basis for the minor change may consist of the items of the certification basis incorporated by reference in the TCDS of the product type/model, and normally it should not be necessary for a minor change to use certification specifications that became applicable after those that are incorporated by reference in the type certificate. (2) On the other hand, the applicant may elect to use later amendments of the affected certification specifications for the compliance demonstration. This does not affect the classification of the change; however, the applicant should also comply with any other certification specifications that EASA considers to be directly related. (3) If other changes are required for the installation of the minor change (as explained in ‘specific configurations’), the certification basis for the minor change should also take into account the corresponding certification basis. (j) Meaning of ‘no feature or characteristics’ in point [21.A.95](#_DxCrossRefBm485230341)(b)(4) See [GM 21.A.20(d)](#_DxCrossRefBm485230521).