Ambiguous numbering and presentation: The Requirement and Compliance text uses numbered and lettered subparagraphs with uneven numbering (for example, Requirement lists “1.” then “(a)” then later “3.” while Compliance lists “1.” then “(a).” then “2.” and “3.”). The format suggests editorial compression or typographical errors in numbering. Operators should not rely on paragraph numbering alone for the substantive obligation; instead they should read the textual content carefully: inspections are required, leakage triggers AOW instructions, and modifications are mandated for identified engine models and serial numbers.
Serial number cutoff detail: The modification mandate for V2500‑A5 engines applies only to engines “having a Serial Number lower than V11375” (Requirement). Engines with serial numbers at or above V11375 are not placed under the same modification obligation by this AD as printed. Operators must therefore ensure accurate serial number tracking for each engine to determine applicability. Confusion can arise where serial numbers are transcribed incorrectly or where maintenance records are incomplete; misclassification can lead to non‑compliance or unnecessary work.
Applicability beyond Airbus A319/A320/A321: The Applicability clause states the engines are “installed in, but not limited to, Airbus A319, A320 and A321 series aircraft.” The phrasing makes the AD apply to the engine models themselves irrespective of airframe. A “gotcha” here is treating the AD as only affecting the named Airbus types; owners of other aircraft types with these engines must check whether their engines are V2500‑A1 or V2500‑A5 and, if so, comply.
“Unless previously accomplished” caveat: The Compliance table provides a 500 flight‑hour inspection window “Unless previously accomplished” (Compliance: 1). That implies that prior work done in accordance with the referenced SBs or equivalent DGAC‑approved revisions may negate the need for a fresh inspection. However, the AD does not state how prior work is to be verified or documented within the AD text. Operators relying on prior maintenance actions should ensure they have documentary evidence that prior inspections or modifications were performed to the standard required by the SBs or approved revisions.
Interaction between immediate action and scheduled modification windows: The AD mandates immediate action “before further flight” if leakage is observed and separately mandates modification no later than 31 December 2005 or at the next removal of the FCOC. Operators must manage both contingencies: immediate corrective measures in a leakage event (as per AOW 1048.2) and scheduled modification plans for non‑leakage engines. Failure to coordinate these obligations could produce operational disruption or missequenced maintenance work.
Strict AMM procedures on every opening: Note 2 under Requirement instructs that at every other opening of the fuel filter cover “strictly apply the procedures detailed in the Aircraft Maintenance Manual (AMM).” The word “strictly” elevates the AMM procedures to a high standard of compliance; a possible gotcha is performing a quick or improvised access without following the AMM detail , the AD explicitly forbids that. Operators must ensure that line and base maintenance staff have access to and are trained in the AMM procedures.
Dependence on external documents not reproduced in the AD: The AD requires compliance with SBs, an AOW and the AMM, but does not reproduce their content. Practical compliance thus requires retrieving and following those documents exactly. A potential pitfall is assuming what the SBs or AOW require without consulting them; the AD’s legal requirement is to follow the SBs/AOW/AMM as specified.
Dates and deadlines: The AD becomes effective 1 September 2005 and sets a “no later than 31 December 2005” modification deadline (Compliance: items 2 and 3), while the inspection is due within 500 flight hours after the effective date (Compliance: 1). Operators should not confuse calendar dates and flight‑hour windows; both are operative and must be tracked. For operators close to the serial number cut‑off or approaching the calendar deadline, planning is necessary to ensure timely removal and modification.
Scope of DGAC approval: The AD permits “later DGAC approved revision[s]” of the SBs to be used for the required modification (Requirement). A practical gotcha is assuming that any later manufacturer SB will be acceptable; the AD requires the later revision to be DGAC approved. Operators must confirm the approval status of later SB revisions before using them for compliance.
AOW 1048.2 content is decisive in leakage events: The AD requires compliance with AOW 1048.2 when leakage is observed and mandates that action “before further flight.” The AD does not summarise the AOW’s content. The AOW may contain specific steps that affect minimising downtime or part replacement; operators need to procure and interpret that AOW immediately when leakage is found.
No penalty text in the AD: The AD contains no explicit penalties for non‑compliance. That absence can mislead operators into underestimating the regulatory consequences of ignoring ADs. In practice, AD non‑compliance can affect airworthiness and regulatory standing; operators should treat the AD as mandatory despite the absence of a printed penalty clause.
Recordkeeping and proof of compliance not specified: The AD does not set out documentation requirements. Operators should nonetheless document inspections, findings, corrective actions, and modifications to demonstrate compliance in the event of oversight or audit. Failure to keep adequate records is a practical compliance risk.
Redundancy in header text: The document repeats headings (AD/V2500/2, Fuel Filter Cover, 9/2005) multiple times. That is an editorial quirk but not substantive; however it may cause confusion if relying solely on headers for quick reference.