GM 21.A.21(b), 21.A.95(c), 21.A.97(c), 21.A.115(c), 21.B.103(b), 21.B.107(b) and 21.B.111(b) Approval of operational suitability data (OSD)

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

GM 21.A.21(b), 21.A.95(c), 21.A.97(c), 21.A.115(c), 21.B.103(b), 21.B.107(b) and 21.B.111(b) Approval of operational suitability data (OSD) ED Decision 2019/018/R It is acknowledged that it may not always be possible to have the OSD available on the date of the issue of the (restricted) type certificate ((R)TC), change approval or supplemental type certificate (STC). The derogation provided by [21.A.21](#_DxCrossRefBm1649096866)(b), [21.A.95](#_DxCrossRefBm1649097008)(c), [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b) and [21.B.111](#_DxCrossRefBm1649097006)(b) is intended for that case. The (R)TC, change approval or STC can be issued before compliance with the OSD certification basis has been demonstrated. However, the OSD needs to be approved before the data is used by a training organisation for the purpose of obtaining a European Union (EU) licence, rating or attestation, or by an EU operator. This is normally done before the entry into service of the first aircraft by an EU operator but it could also be done later for some of the OSD constituents, such as the definition of the scope of validation source data to support the objective qualification of a simulator, which should only be available when a simulator has to be qualified. The derogation provided in points [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b), and [21.B.111](#_DxCrossRefBm1649097006)(b) is applicable to all major changes to a TC, so it is also applicable to minor design changes when triggering a major master minimum equipment list (MMEL) change, as well as to changes in which at least one of the OSD constituent changes is major. GM 21.A.21(b), 21.A.95(c), 21.A.97(c), 21.A.115(c), 21.B.103(b), 21.B.107(b) and 21.B.111(b) Approval of operational suitability data (OSD) ED Decision 2019/018/R It is acknowledged that it may not always be possible to have the OSD available on the date of the issue of the (restricted) type certificate ((R)TC), change approval or supplemental type certificate (STC). The derogation provided by [21.A.21](#_DxCrossRefBm1649096866)(b), [21.A.95](#_DxCrossRefBm1649097008)(c), [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b) and [21.B.111](#_DxCrossRefBm1649097006)(b) is intended for that case. The (R)TC, change approval or STC can be issued before compliance with the OSD certification basis has been demonstrated. However, the OSD needs to be approved before the data is used by a training organisation for the purpose of obtaining a European Union (EU) licence, rating or attestation, or by an EU operator. This is normally done before the entry into service of the first aircraft by an EU operator but it could also be done later for some of the OSD constituents, such as the definition of the scope of validation source data to support the objective qualification of a simulator, which should only be available when a simulator has to be qualified. The derogation provided in points [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b), and [21.B.111](#_DxCrossRefBm1649097006)(b) is applicable to all major changes to a TC, so it is also applicable to minor design changes when triggering a major master minimum equipment list (MMEL) change, as well as to changes in which at least one of the OSD constituent changes is major. GM 21.A.21(b), 21.A.95(c), 21.A.97(c), 21.A.115(c), 21.B.103(b), 21.B.107(b) and 21.B.111(b) Approval of operational suitability data (OSD) ED Decision 2019/018/R It is acknowledged that it may not always be possible to have the OSD available on the date of the issue of the (restricted) type certificate ((R)TC), change approval or supplemental type certificate (STC). The derogation provided by [21.A.21](#_DxCrossRefBm1649096866)(b), [21.A.95](#_DxCrossRefBm1649097008)(c), [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b) and [21.B.111](#_DxCrossRefBm1649097006)(b) is intended for that case. The (R)TC, change approval or STC can be issued before compliance with the OSD certification basis has been demonstrated. However, the OSD needs to be approved before the data is used by a training organisation for the purpose of obtaining a European Union (EU) licence, rating or attestation, or by an EU operator. This is normally done before the entry into service of the first aircraft by an EU operator but it could also be done later for some of the OSD constituents, such as the definition of the scope of validation source data to support the objective qualification of a simulator, which should only be available when a simulator has to be qualified. The derogation provided in points [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b), and [21.B.111](#_DxCrossRefBm1649097006)(b) is applicable to all major changes to a TC, so it is also applicable to minor design changes when triggering a major master minimum equipment list (MMEL) change, as well as to changes in which at least one of the OSD constituent changes is major. GM 21.A.21(b), 21.A.95(c), 21.A.97(c), 21.A.115(c), 21.B.103(b), 21.B.107(b) and 21.B.111(b) Approval of operational suitability data (OSD) ED Decision 2019/018/R It is acknowledged that it may not always be possible to have the OSD available on the date of the issue of the (restricted) type certificate ((R)TC), change approval or supplemental type certificate (STC). The derogation provided by [21.A.21](#_DxCrossRefBm1649096866)(b), [21.A.95](#_DxCrossRefBm1649097008)(c), [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b) and [21.B.111](#_DxCrossRefBm1649097006)(b) is intended for that case. The (R)TC, change approval or STC can be issued before compliance with the OSD certification basis has been demonstrated. However, the OSD needs to be approved before the data is used by a training organisation for the purpose of obtaining a European Union (EU) licence, rating or attestation, or by an EU operator. This is normally done before the entry into service of the first aircraft by an EU operator but it could also be done later for some of the OSD constituents, such as the definition of the scope of validation source data to support the objective qualification of a simulator, which should only be available when a simulator has to be qualified. The derogation provided in points [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b), and [21.B.111](#_DxCrossRefBm1649097006)(b) is applicable to all major changes to a TC, so it is also applicable to minor design changes when triggering a major master minimum equipment list (MMEL) change, as well as to changes in which at least one of the OSD constituent changes is major. GM 21.A.21(b), 21.A.95(c), 21.A.97(c), 21.A.115(c), 21.B.103(b), 21.B.107(b) and 21.B.111(b) Approval of operational suitability data (OSD) ED Decision 2019/018/R It is acknowledged that it may not always be possible to have the OSD available on the date of the issue of the (restricted) type certificate ((R)TC), change approval or supplemental type certificate (STC). The derogation provided by [21.A.21](#_DxCrossRefBm1649096866)(b), [21.A.95](#_DxCrossRefBm1649097008)(c), [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b) and [21.B.111](#_DxCrossRefBm1649097006)(b) is intended for that case. The (R)TC, change approval or STC can be issued before compliance with the OSD certification basis has been demonstrated. However, the OSD needs to be approved before the data is used by a training organisation for the purpose of obtaining a European Union (EU) licence, rating or attestation, or by an EU operator. This is normally done before the entry into service of the first aircraft by an EU operator but it could also be done later for some of the OSD constituents, such as the definition of the scope of validation source data to support the objective qualification of a simulator, which should only be available when a simulator has to be qualified. The derogation provided in points [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b), and [21.B.111](#_DxCrossRefBm1649097006)(b) is applicable to all major changes to a TC, so it is also applicable to minor design changes when triggering a major master minimum equipment list (MMEL) change, as well as to changes in which at least one of the OSD constituent changes is major. GM 21.A.21(b), 21.A.95(c), 21.A.97(c), 21.A.115(c), 21.B.103(b), 21.B.107(b) and 21.B.111(b) Approval of operational suitability data (OSD) ED Decision 2019/018/R It is acknowledged that it may not always be possible to have the OSD available on the date of the issue of the (restricted) type certificate ((R)TC), change approval or supplemental type certificate (STC). The derogation provided by [21.A.21](#_DxCrossRefBm1649096866)(b), [21.A.95](#_DxCrossRefBm1649097008)(c), [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b) and [21.B.111](#_DxCrossRefBm1649097006)(b) is intended for that case. The (R)TC, change approval or STC can be issued before compliance with the OSD certification basis has been demonstrated. However, the OSD needs to be approved before the data is used by a training organisation for the purpose of obtaining a European Union (EU) licence, rating or attestation, or by an EU operator. This is normally done before the entry into service of the first aircraft by an EU operator but it could also be done later for some of the OSD constituents, such as the definition of the scope of validation source data to support the objective qualification of a simulator, which should only be available when a simulator has to be qualified. The derogation provided in points [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b), and [21.B.111](#_DxCrossRefBm1649097006)(b) is applicable to all major changes to a TC, so it is also applicable to minor design changes when triggering a major master minimum equipment list (MMEL) change, as well as to changes in which at least one of the OSD constituent changes is major. GM 21.A.21(b), 21.A.95(c), 21.A.97(c), 21.A.115(c), 21.B.103(b), 21.B.107(b) and 21.B.111(b) Approval of operational suitability data (OSD) ED Decision 2019/018/R It is acknowledged that it may not always be possible to have the OSD available on the date of the issue of the (restricted) type certificate ((R)TC), change approval or supplemental type certificate (STC). The derogation provided by [21.A.21](#_DxCrossRefBm1649096866)(b), [21.A.95](#_DxCrossRefBm1649097008)(c), [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b) and [21.B.111](#_DxCrossRefBm1649097006)(b) is intended for that case. The (R)TC, change approval or STC can be issued before compliance with the OSD certification basis has been demonstrated. However, the OSD needs to be approved before the data is used by a training organisation for the purpose of obtaining a European Union (EU) licence, rating or attestation, or by an EU operator. This is normally done before the entry into service of the first aircraft by an EU operator but it could also be done later for some of the OSD constituents, such as the definition of the scope of validation source data to support the objective qualification of a simulator, which should only be available when a simulator has to be qualified. The derogation provided in points [21.A.97](#_DxCrossRefBm1649096997)(c), [21.A.115](#_DxCrossRefBm1649096857)(c), [21.B.103](#_DxCrossRefBm1649097007)(b), [21.B.107](#_DxCrossRefBm1649096850)(b), and [21.B.111](#_DxCrossRefBm1649097006)(b) is applicable to all major changes to a TC, so it is also applicable to minor design changes when triggering a major master minimum equipment list (MMEL) change, as well as to changes in which at least one of the OSD constituent changes is major.