Access and inspection logistics: the inspection target is the structure around four bolts on the engine mount attachment at the firewall, but the Directive recognises access may be restricted and provides specific panel removal instructions , remove the upper panels of the firewall bulkhead, right side totally and left side partially, to inspect via the engine bay (Requirement 1). That means the inspection may require partial disassembly and associated downtime; operators should not assume a quick cockpit‑level check will be sufficient where access is restricted.
Ambiguities in re‑inspection wording: Requirement 1 contains two subparagraphs (1.a and 1.b) that both instruct operators whose aircraft were previously inspected under the original issue to "carry out the Requirement 1 inspection" whether the aircraft has accumulated 100 or more flight hours since the original inspection (1.a) or less than 100 flight hours (1.b). Practically, the effect is that all aircraft previously inspected must be reinspected under Amendment 1, but the text’s conditional structure can cause confusion about timing. The Compliance section attempts to resolve timing by preserving the original initial inspection deadline and setting repeat intervals, but readers should note the wording and check flight‑hour records to interpret which aircraft require immediate inspection (Requirement 1; Compliance).
Inspection interval framing: the Directive prescribes repeat inspections "at intervals not to exceed 100 flight hours" unless the aircraft has had a repair accomplished that specifies an alternate interval (Compliance; Requirement 2). However, where Gomolzig Modification 15328 is applied, the Directive explicitly permits extension of the repeat inspection interval to 500 flight hours (Requirement 3). That creates a clear incentive to adopt that specific approved repair if available and practicable; operators should confirm the Gomolzig repair’s availability, cost and compliance paperwork before relying on the extended interval.
Repair approvals and documentation: repairs must be EASA‑approved to be acceptable under the Directive (Requirement 3.a and 3.b). If a repair other than the Gomolzig modification is used, the repeat inspection interval depends entirely on the approved repair documents (Requirement 3.b). Operators must therefore obtain and retain the repair approval documentation and the corresponding inspection schedule. Failure to align with the repair document’s inspection interval will create compliance risk.
Grounding triggers recordkeeping and communications: if cracking is detected and an approved repair is not immediately implemented, operators must ground the aircraft and contact EASA (Requirement 3.c). Grounding has operational and commercial consequences and requires immediate administrative contact with EASA. That can create service interruptions, route cancellations and heads of regulatory correspondence.
Cross‑authority coordination: the Directive references EASA AD 2008‑0015 and lists EASA and ENAC contacts (Notes 1-3). Operators must be prepared to liaise with multiple authorities to resolve technical questions or to obtain further direction when grounding is required. This is an administrative burden that can lengthen return‑to‑service time.
Initial compliance dates preserved: the Amendment explicitly states the initial Requirement 1 inspection compliance time remains unchanged by this issue of the Directive (Compliance). Operators must not assume the Amendment replaces the original initial deadline; review of the original directive timing is necessary to avoid late compliance.
No penalties listed in the text: the Directive mandates inspections and repairs but does not itself state civil penalties or the enforcement process in the provided text (Compliance). Operators should therefore confirm with the Civil Aviation Safety Authority how compliance is enforced domestically and whether failure to comply has specified administrative or civil consequences.
Email contacts are public in the text: the Directive provides direct email addresses for AD enquiries (ADs@easa.europa.eu) and technical content (ad@enac.rupa.it) (Notes 1 and 2). Operators should use these contacts for clarifications but should also keep records of such correspondence to evidence attempts to comply.