How should I, as a DOA holder, setup the interface with a Maintenance organisation for the first installation of a design change?
Please refer to the good practices published on EASA website.
Why should I, as a DOA holder - having been granted the privilege to approve compliance documents, submit any compliance document to the Agency?
In accordance with 21.A.257(b) the DOA holder shall allow the Agency to review any compliance document and make any inspection (also in terms of tests witnessing) to check the validity of the final declaration of compliance submitted by the DOA holder at the end of a certification process.
Nevertheless, the Agency is involved at an early stage in the certification process, and can use the Certification Programme for establishing its “level of involvement”. The Agency can agree with the DOA holder that certain compliance documents are accepted, without further verification, under the DOA privilege.
How can I learn about the Agency's activities regarding design organisations?
For Agency's structure dealing with Design Organisations, please visit https://www.easa.europa.eu/the-agency/agency-organisation-structure.
For Agency's activities regarding Design Organisations, please visit the design organisations page on EASA website.
For different applications related to Design Organisations, please visit https://www.easa.europa.eu/document-library/application-forms.
For being notified about the Agency's activities regarding Design Organisations, please subscribe to EASA Updates.
Queries related to Design Organisations can be sent to: doa [at] easa.europa.eu (doa[at]easa[dot]europa[dot]eu).
Do I, as a DOA holder, need to obtain confirmation from the maintenance organisation that my design change has been incorporated on a specific product?
No. After the design change is approved, there is no requirement on a design organisation to keep managing the configuration control of the product(s) on which its design changes are installed. Thus, it is not mandatory to collect confirmation records from the organisations performing the installation of the design changes.
Can a Type Certificate Holder (TCH) Split Part-21 Responsibilities Between Its Own DOA and Another DOA Holder (DOAH) on a Project-by-Project Basis?
No, the regulatory framework does not permit the discharging of the obligations of the TCH to be divided between different DOAs on a project-by-project basis.
When a TCH has obtained their own DOA and they decide to fulfil the obligations as TCH using this DOA they need to do so in full.
As a result, a TCH cannot apply a mixed compliance model whereby:
- for certain projects, it discharges its obligations under point 21.A.44 directly through its own DOA; and
- for other projects under the same TC, it contracts another organisation to discharge those same obligations on its behalf under point 21.A.2.
A project-based allocation of the same TC responsibilities between different organisations is not permitted, as it would undermine the clear assignment of accountability required by Part-21 and could give rise to safety concerns. The single DOA in charge will be able to maintain a 100% overview and be responsible for the Continued Airworthiness, configuration control and other matters concerning airworthiness.