AD/A330/100 - Fire Extinguishing System - Replacement/Modification

This AD is structured around a small set of technical and procedural concepts drawn from the supplied text. The central technical objects and terms are:

• Halon dual-filter assembly: the assembly in the flow metering fire extinguishing system that contains a water absorbing filter element (P/N QA06123) and is identified by part numbers QA06753, QA06753-01 and QA06753-02. The AD requires modification or replacement of these assemblies where fitted in the affected aeroplanes (Requirement 1, Compliance, Note 2).

• Flow Metering Compact Unit (FMCU) P/N QA07907-03 and Flow Metering System (FMS): the FMCU is the prototype unit whose supplier-site qualification tests revealed partial blockage of the water absorbing filter element. The FMS is the cargo compartment fire extinguishing system component in which the Halon dual-filter assembly and water absorbing filter element are fitted (Background).

• Water absorbing filter element P/N QA06123: the filter element that experienced partial blockage during tests, caused by carbon debris from the cartridge and from the burst disc of the Halon bottle; the blockage can reduce Halon outflow and potentially create incapacity to maintain fire extinguishing agent concentration (Background).

• Airbus Service Bulletin A330-26-3040 Revision 02.2: the mandatory technical instructions referenced in Requirement 1, which define the replacement or modification actions. The AD also states that embodiment in production or in service of the SB at original issue or a revision is acceptable to comply with Requirement 1 (Requirement 1; Note 1).

• Aircraft configurations and compartments: the AD distinguishes installation locations and system types , Lower Deck Cargo Compartment (LDCC) and Bulk Cargo Rest Compartment (BCRC) , and requires action in the forward cargo compartment for aeroplanes fitted with LDCC and in the bulk cargo compartment for aeroplanes fitted with BCRC (Background).

Operational and administrative concepts in the AD include:

• Applicability and exceptions: the AD lists specific Airbus A330 model variants (for example -201, -202, -203, -301, -302, -303, -321, -322, -323, -341, -342, -343 and others) and expressly excludes aeroplanes on which Airbus modification 55590 has been embodied in production (Applicability).

• Compliance timing tied to part numbers and SB embodiment: the Compliance section prescribes different time windows conditional on which part number is fitted, and references an additional 60-day timing linked to a notional SB embodiment date (Compliance).

• Reporting obligation: the AD requires operators to report accomplishment of the replacement or modification to Airbus (Requirement 1). The AD does not specify the content of that report in the provided text.

• Cross-reference to EASA AD: the AD points to EASA AD 2009-0064 dated 12 March 2009, indicating coordination or common technical basis with the EASA action (Note 1).

The AD blends a physical-technical corrective action with a paper trail requirement. The technical mitigation (replace or modify the dual-filter assemblies) addresses a specific failure mode (carbon-debris-induced blockage of the water absorbing element) observed in qualification testing. The procedural component requires operators both to perform the SB-specified modifications and to report back to Airbus.

The text expressly identifies aircraft types and configurations to which the AD applies. Affected subjects are:

• Operators and owners of AIRBUS (formerly AIRBUS INDUSTRIE) A330 models listed in the Applicability table: -201, -202, -203, -223, -243, -301, -302, -303, -321, -322, -323, -341, -342 and -343 aeroplanes, all serial numbers, except those on which AIRBUS modification 55590 has been embodied in production (Applicability). The AD text does not extend applicability to Airbus A340 models in its Applicability clause even though the Background notes that the water absorbing filter element is part of equipment used in both A330 and A340 aeroplanes; therefore, on the text supplied, the mandatory obligation is limited to the listed A330 variants.

• Maintenance providers and certifying staff contracted or employed by those operators, because the AD requires physical replacement or modification of Halon dual-filter assemblies in specific cargo compartments as prescribed by Airbus SB A330-26-3040 Rev 02.2 (Requirement 1). The work must be accomplished in the forward cargo compartment for aeroplanes fitted with LDCC and in the bulk cargo compartment for aeroplanes fitted with BCRC (Background).

• Aircraft configuration managers and continuing airworthiness personnel, because compliance timing is dependent on the specific part number fitted (P/N QA06753, QA06753-01, QA06753-02) and on whether certain production modifications have already been embodied (Note 2; Compliance). They must identify the installed dual-filter assembly P/N and check aircraft modification status against mod 55590 and other production modifications (Note 2).

• Airbus as recipient of completion reports, because the AD requires operators to report the accomplishment of the replacement or modification to Airbus (Requirement 1).

• Regulators and delegated authorities, implicitly. The AD was issued by the Civil Aviation Safety Authority via a named delegate (James Coyne) and has an effective date (7 May 2009). While the supplied text does not set out enforcement mechanisms or penalties, regulators are the bodies that typically supervise AD compliance and continuing airworthiness; the AD’s issuance by the CASA delegate is the regulatory action initiating mandatory compliance (signature and effective date).

Excluded or unaffected subsets per the supplied wording:

• Aeroplanes on which Airbus modification 55590 has been embodied in production are expressly excluded (Applicability). The text does not explain the technical reason for this exclusion within the supplied extract, but the effect is to remove those serial-numbered aeroplanes from the AD's mandatory scope.

• The supplied extract does not list A340 model numbers in the Applicability clause, so A340 operators are not covered by this AD on the face of the supplied text, despite a reference to the A340 in the Background.

Who pays and who decides: the AD places the operational obligation on aircraft operators to carry out the modifications and to report to Airbus; therefore, operators and their maintenance organisations bear the direct cost and operational disruption. The CASA delegate issued the AD and set the effective date, which is the point at which the compliance clock starts (effective date 7 May 2009; signature 27 March 2009).

The supplied AD creates a narrow set of operator duties and administrative expectations. The duties are explicit in the Requirement and Compliance text; rights (or procedural flexibilities) are limited and expressly delineated.

Primary duties placed on operators, owners and their maintenance organisations:

• Replace or modify the Halon dual-filter assemblies of the flow metering fire extinguishing system in the forward and bulk cargo compartments in accordance with instructions defined in AIRBUS Service Bulletin A330-26-3040 Revision 02.2 (Requirement 1). The Requirement covers both replacement and modification as acceptable technical remedies.

• Report the accomplishment of the replacement or modification to AIRBUS (Requirement 1). The AD requires reporting, but the supplied text does not specify the format, addressee details beyond "AIRBUS", or the content of the required report.

• Meet specified compliance timeframes tied to installed part numbers. For aeroplanes fitted with Halon dual-filter assembly P/N QA06753 the task must be done within 18 months from the effective date. For aeroplanes fitted with P/N QA06753-01 or QA06753-02 the task must be done within 24 months from the effective date (Compliance).

• Comply with an additional timing requirement described in the Compliance text for "Requirement 2": "Within 60 days after SB embodiment date, as defined in Requirement 1 of this AD." The supplied extract contains this compliance timing but does not include a labelled Requirement 2 describing the act that the 60-day period governs. Consequently, operators are duty-bound under the AD to meet the 60-day timing if Requirement 2 is applicable, but the supplied instrument text lacks the specific substantive content of Requirement 2.

Rights and flexibilities expressly recognised in the text:

• Acceptable pre-existing compliance: "Modification of an aeroplane, prior to the effective date of this AD, in accordance with the instructions of SB A330-26-3040 at Original issue or Revision is acceptable to comply with requirement 1 of this AD." This gives operators who have already performed the SB work prior to the AD effective date a right to be considered compliant for Requirement 1, provided the prior work followed the SB instructions at original issue or a revision that conforms to Requirement 1 (Requirement 1; Note 1).

• SB revision flexibility: the AD specifies SB A330-26-3040 Revision 02.2 as the instructions to follow, but explicitly states that embodiment at the SB's original issue or a revision is acceptable to comply with Requirement 1. That provides operational flexibility for earlier conforming SB work (Requirement 1; Note 1).

• Part-number-specific compliance windows: the AD distinguishes compliance windows by P/N, which allows operators to identify their compliance timing based on the part fitted (Compliance).

Unspecified matters and limits to rights in the supplied text:

• The AD does not specify the reporting format or recipient details beyond "AIRBUS", nor does it set out how regulators will verify or accept the report; the reporting duty is stated but administrative handling is undefined in the supplied extract (Requirement 1).

• The AD does not set out enforcement measures or penalties in the supplied text; obligations are prescribed but the text does not include statutory sanctioning language (the instrument is an AD, effective as of 7 May 2009).

• The supplied AD does not include the substance of an apparent Requirement 2, though it references a 60-day compliance period tied to SB embodiment date. The absence of a labelled Requirement 2 in the supplied text creates a gap as to what additional duty that 60-day timing attaches to.

Procedural implications for operators:

• Operators must inspect records or physical installations to establish which Halon dual-filter assembly P/N is fitted and whether Airbus modification 55590 is embodied in production, to determine applicability and the correct compliance window (Applicability; Note 2; Compliance).

• If the SB work has already been performed before the effective date in accordance with the SB at original issue or revision, operators can treat Requirement 1 as satisfied without repeating the action, but they still must report the accomplishment to Airbus if that reporting obligation remains (Requirement 1; Note 1).

In short, the AD imposes a narrow set of technical duties with a reporting obligation, allows prior-conforming SB work to satisfy the primary requirement, and sets differing compliance deadlines by part number. The supplied text leaves open administrative details about reporting and lacks the substantive text for a referenced Requirement 2.

The supplied AD text contains no express penalty provisions, fines, or administrative sanctions within the extract. It is presented and signed as an Airworthiness Directive by a delegate of the Civil Aviation Safety Authority (signature block: James Coyne, Delegate of the Civil Aviation Safety Authority, 27 March 2009) and specifies an effective date (7 May 2009), which makes the directive operative as of that date. The AD, by its nature as a regulatory instrument requiring corrective action, prescribes mandatory obligations (replacement/modification and reporting). However, the supplied text does not describe the regulator’s enforcement process, the consequences of non-compliance, or appeal rights.

What the supplied text does provide relevant to enforcement is:

• The duty to act: Requirement 1 mandates replacement or modification in accordance with Airbus SB A330-26-3040 Rev 02.2 and reporting to Airbus. The Compliance section specifies the time frames within which operators must perform the actions depending on the part number fitted (Compliance).

• Effective date and issuing authority: the AD “becomes effective on 7 May 2009”, and it bears the delegate’s signature dated 27 March 2009. The fact of signature and effective date indicates that the directive was issued by the CASA delegate, which is the regulatory act initiating a compliance obligation (signature block; effective date).

What the supplied text does not state and therefore must not be inferred from this extract alone:

• The specific enforcement mechanisms CASA or other authorities will use to secure compliance, including any administrative penalties, suspension of certificates, grounding orders or civil penalties, are not described in the supplied text.

• Any procedural steps for notification of compliance to the regulator, or for verification/audit of the reported accomplishment by Airbus or CASA, are not provided in the extract.

• Appeal or objection procedures against the AD in the supplied text are not stated.

Operationally, the absence of explicit penalties or enforcement detail in the AD as supplied means that an operator reading only this document will know their mandatory technical obligations and deadlines, but will not obtain from this extract the regulatory follow-up process or potential sanctions for non-compliance. The AD does, however, create an obligation that must be satisfied in practice; enforcement and penalties commonly exist in the broader statutory and regulatory framework under which ADs are issued, but such mechanisms are not set out in the supplied instrument.

For practitioners advising operators, the immediate compliance priorities from this AD as supplied are (1) determine applicability, (2) perform or confirm required SB-compliant modifications within the relevant windows, and (3) report accomplishment to Airbus in the manner required by Airbus and/or the regulator , while seeking regulator guidance where the AD language is unclear (for example, the missing substantive text of the referenced Requirement 2 and the format/recipients for reporting).

The supplied AD text contains several cross-references to other regulatory and technical instruments but does not expressly set out interactions with broader statutes or administrative law. The text indicates coordination with a European regulator and references multiple Airbus production modifications and service bulletins that determine applicability and compliance pathways. From the supplied material the concrete interactions are these:

• Reference to EASA AD: The AD contains a Note (Note 1) stating that "EASA AD 2009-0064 dated 12 March 2009 refers." That shows the AD is cognisant of a similarly themed action by the European Aviation Safety Agency. The supplied extract does not set out the content of that EASA AD, nor does it state whether the CASA AD is identical, complementary, or more or less stringent. The explicit referral is the only text-based interaction with EASA contained in the extract.

• Interaction with Airbus Service Bulletins: The AD’s substantive technical requirement is to follow AIRBUS Service Bulletin A330-26-3040 Revision 02.2. The AD also notes that embodiment of SB A330-26-3040 at original issue or revision prior to the effective date is acceptable to comply with Requirement 1. Consequently, operational compliance is achieved by carrying out an Airbus SB procedure rather than by reference to a CASA-specific technical amendment. The AD therefore uses industry technical material (the SB) as the means of compliance, which is a standard regulatory mechanism for ADs but is explicitly stated here (Requirement 1; Note 1).

• Relationship to Airbus production modifications and other SBs: Note 2 details how the relevant Halon dual-filter P/Ns are embodied: QA06753 is embodied in production via modification 40041; QA06753-01 is only embodied in service through SB A330-26-3030; QA06753-02 is embodied in production through modifications 47197, 47883, 50108 (BCRC), and 51065 or 51329 (LDCC) or in service through SB A330-26-3030. The AD therefore interacts functionally with Airbus production configuration records and with separate SB A330-26-3030 for some embodiments, meaning that conformity assessment for applicability and compliance requires reference to Airbus production/modification records and previous SB implementations (Note 2).

• Exclusion via aircraft configuration modification: The Applicability clause excludes aeroplanes on which Airbus modification 55590 has been embodied in production. That creates a direct interaction between this AD’s applicability and the aircraft’s production-modification status; operators must check whether mod 55590 has been incorporated to determine whether the AD applies to their aeroplane (Applicability).

What the supplied text does not specify about interactions with other laws:

• The AD does not, in the supplied extract, describe how reporting to Airbus interacts with regulatory reporting obligations to CASA or other national authorities, nor does it specify whether reporting to Airbus satisfies any regulator-directed reporting requirement.

• The AD does not state whether the AD pre-empts or supplements existing contractual obligations between operators and maintenance providers or between operators and Airbus warranty/contract arrangements.

• The broader statutory foundation that empowers the issuance of ADs, including any appeal rights or administrative processes under Australian aviation law, is not provided in the supplied extract.

In practice, the AD’s operative interactions are with Airbus technical documents (SBs and production modification records) and with EASA’s corresponding AD as a referenced instrument. Operational compliance requires review of aircraft modification status, SB embodiment, and parts P/Ns to map obligations; reading the AD in isolation leaves unanswered the regulator-level enforcement and inter-authority reporting modalities, which would be governed by the broader aviation regulatory framework outside the supplied text.

The supplied extract contains limited chronological detail and references to revisions of service bulletins and related documents. The AD itself includes the following dated and revision-level references that constitute the record in the provided text:

• Signature and date: The AD was signed by James Coyne, Delegate of the Civil Aviation Safety Authority, on 27 March 2009. The AD states that it "becomes effective on 7 May 2009" (signature block; effective date).

• Reference to Airbus Service Bulletin A330-26-3040 Revision 02.2: Requirement 1 instructs operators to perform the replacement or modification in accordance with SB A330-26-3040 Revision 02.2. The AD also explicitly indicates that embodiment of SB A330-26-3040 at original issue or any revision is acceptable to comply with Requirement 1; that language establishes that prior embodiments of the SB may be treated as compliant (Requirement 1; Note 1).

• Cross-reference to EASA AD 2009-0064 dated 12 March 2009: The AD includes Note 1 highlighting that EASA AD 2009-0064 dated 12 March 2009 refers. This provides a proximate European regulatory action with an earlier date than the CASA effective date (Note 1).

• Production modification numbers and SB references used to describe how part numbers are embodied: Note 2 lists modification numbers and SBs associated with the different Halon dual-filter assembly part numbers. Specifically:

  • Halon Dual-Filter Assembly P/N QA06753 is embodied in production through modification 40041.
  • Halon Dual-Filter Assembly P/N QA06753-01 is only embodied in service through SB A330-26-3030.
  • Halon Dual-Filter Assembly P/N QA06753-02 is embodied in production through modifications 47197 or 47883 or 50108 (BCRC) and 51065 or 51329 (LDCC) or in service through SB A330-26-3030 (Note 2).

• AD identifier and issue number: The heading shows "AD/A330/100" and date "5/2009" which ties the directive to a numbered AD and a month/year of issuance in the title block. The header table indicates the AD identifier and "5/2009" as the date or edition indicator.

What the supplied text does not provide in terms of amendment history:

• The AD extract does not include any prior versions of this CASA AD or any later amendments or revocations. The only revision-level item explicitly present is the SB revision A330-26-3040 Revision 02.2 and the acceptability of original issue or revisons for compliance.

• There is no internal text in the supplied extract indicating that the AD itself has been amended, superseded, or updated after the effective date within the extract. No amendment chronology for the AD beyond the signature date and effective date is present.

For practitioners tracking the lifecycle of this directive, the immediately available historical touchpoints from the supplied text are the CASA signature date (27 March 2009), the AD effective date (7 May 2009), the SB revision required (A330-26-3040 Rev 02.2), and the referenced EASA AD dated 12 March 2009. The AD also contains detailed internal references to Airbus production modifications and another SB (A330-26-3030) that determine how parts were embodied in production or service. Beyond those references, no further amendment history is present in the provided material.

The supplied AD extract does not contain any information about litigation, dispute, judicial review, administrative appeals, or court or tribunal decisions relating to the AD. There are no case citations, no references to challenges to the AD’s validity, nor any mention of enforcement actions brought in court or settled disputes. The document is limited to the AD text, technical instructions, applicability, compliance timings, notes, and background narrative.

Given the absence of any litigation material in the supplied text, an accurate statement from this source is that no litigation history is recorded in the extract. If a practitioner requires information on whether this AD was the subject of litigation, administrative review, or other dispute proceedings, that information is not present in the document supplied and would need to be sought from external sources such as regulator records, court filings, or subsequent public notices , none of which are included in this extract.

The only judicial or administrative facts available in the supplied text are the identity of the issuing delegate, the dates of signature and effect, and the cross-reference to an EASA AD. These are administrative facts, not litigation outcomes.

The supplied AD text contains several features that create potential operational pitfalls or points of ambiguity for practitioners and operators. These are matters that can cause non-obvious compliance issues if not read carefully:

• Applicability exception for mod 55590: The AD applies to the listed A330 model variants "all serial numbers, except those on which AIRBUS modification 55590 has been embodied in production" (Applicability). Operators must verify production records to confirm whether mod 55590 applies to their aeroplane. Failing to check for mod 55590 may lead to unnecessary work or, conversely, to missed compliance obligations if an aircraft’s modification status is misread. The AD does not explain the technical reason for the exclusion.

• A330-only applicability despite A340 mention: The Background notes the water absorbing filter element is part of the FMS used in both A330 and A340 aeroplanes, but the Applicability clause lists only A330 models. That could cause confusion for operators of A340 aeroplanes who read the Background and expect applicability. The supplied AD, on its face, mandates action only for the A330 variants listed in the Applicability clause.

• Different compliance windows by part number: The Compliance timing depends on which Halon dual-filter assembly part number is fitted: P/N QA06753 must be addressed within 18 months; QA06753-01 and QA06753-02 within 24 months (Compliance). Operators must correctly identify the installed P/N to calculate the correct deadline; errors in identification could result in missed deadlines or premature action.

• Part-number embodiment paths: Note 2 shows that the same P/Ns can be embodied through different mechanisms (production modifications or service bulletin Sb A330-26-3030). For example, QA06753-01 is "only embodied in service through SB A330-26-3030", while QA06753-02 can be embodied via multiple production mod numbers or via SB A330-26-3030. Operators must check both production modification records and SB embodiment records to correctly determine which P/N is present and thus which compliance window applies (Note 2).

• Missing substantive text for Requirement 2: The Compliance table includes "For Requirement 2 - Within 60 days after SB embodiment date, as defined in Requirement 1 of this AD." However, the supplied extract contains no labelled Requirement 2 that explains what action that 60-day window governs. The absence of the substantive text for Requirement 2 creates an ambiguity as to the content of that requirement and leaves operators uncertain what, specifically, must be completed within 60 days after SB embodiment date. This is a material drafting gap within the supplied instrument and requires clarification from the issuer or Airbus.

• Reporting to Airbus vs regulatory reporting: Requirement 1 requires operators to "Report the accomplishment to AIRBUS." The AD does not specify whether that reporting to Airbus also satisfies any reporting obligation to the regulator (CASA), nor does it specify the required report content, address, or format in the supplied text. Operators should not assume that a single report to Airbus satisfies regulator reporting unless that is explicitly stated elsewhere.

• Definition of "SB embodiment date": The Compliance text references "SB embodiment date, as defined in Requirement 1 of this AD." Requirement 1 (as supplied) requires replacement or modification in accordance with SB A330-26-3040 Rev 02.2 and accepts prior embodiment of the SB at original issue or revision, but the supplied extract does not offer a clear operational definition for the SB embodiment date (for example, whether it is the date on the SB, the date of physical embodiment on an aircraft, or the date recorded in Airbus service records). The 60-day timing that refers to that SB embodiment date therefore hinges on an operative definition that is not explicit in the supplied text.

• Unspecified reporting content and timelines: The AD requires reporting the accomplishment but does not state deadlines for that reporting apart from the ambiguous Requirement 2 reference, nor does it define the content. Operators risk non-compliance in administrative terms if they report incorrectly or to the wrong recipient.

• Potential parts or scheduling constraints: While not explicitly stated, the AD requires replacement or modification of physical assemblies. Practical constraints such as parts availability, maintenance scheduling, and aircraft downtime are real-world considerations that could complicate meeting the prescribed windows. The AD sets fixed time windows (18 or 24 months) that may create incentives to schedule work; however, the supplied text does not discuss authorisations for extensions or relief for logistical issues.

• Reliance on SB embodiment at original issue or revision for prior compliance: The AD accepts prior SB embodiment at original issue or revision as satisfying Requirement 1. Operators who performed previous work must retain accurate records and be able to demonstrate that the prior work was done to the SB instructions at original issue or a revision that satisfies Requirement 1 to rely on that acceptance (Requirement 1; Note 1).

In sum, the main "gotchas" arise from definitional and drafting lacunae (missing Requirement 2 substance, unclear SB embodiment date), from configuration-management complexity (multiple P/Ns and multiple embodiment routes), and from the reporting requirements that lack procedural detail. Addressing these requires careful review of aircraft production and maintenance records and, likely, direct clarification from Airbus and/or the issuing regulator.

The supplied AD prescribes a specific technical path and timing. The following steps, grounded in the AD text, identify the practical actions an operator must take to achieve compliance as the AD describes. Note that some administrative definitions and procedural details are absent in the supplied text; where the AD is incomplete in the extract, the steps highlight the ambiguity and prescribe seeking clarification from Airbus or the regulator.

Step 1 , Determine applicability

• Confirm the aeroplane's model is one of the listed AIRBUS A330 variants in the Applicability clause (-201, -202, -203, -223, -243, -301, -302, -303, -321, -322, -323, -341, -342 and -343) and that the aeroplane is not excluded by having Airbus modification 55590 embodied in production (Applicability).

Step 2 , Establish which Halon dual-filter assembly P/N is fitted

• Inspect maintenance and production records or the physical assembly to determine whether the installed Halon dual-filter assembly is P/N QA06753, QA06753-01, or QA06753-02. Note 2 sets out how these P/Ns are typically embodied (production mods or SB A330-26-3030) and may assist in tracing how the part came to be installed.

Step 3 , Identify applicable compliance window

• If P/N QA06753 is fitted, the AD requires replacement or modification within 18 months from the effective date (effective date 7 May 2009). If P/N QA06753-01 or QA06753-02 is fitted, the AD requires replacement or modification within 24 months from the effective date (Compliance). Record the specific due date against the aircraft’s maintenance planning calendar.

Step 4 , Use Airbus Service Bulletin A330-26-3040 Revision 02.2

• Carry out the replacement or modification "in accordance with instructions defined in AIRBUS Service Bulletin A330-26-3040 Revision 02.2" (Requirement 1). The AD also states that a modification performed prior to the effective date in accordance with the SB at original issue or a revision is acceptable to comply with Requirement 1; if that is the case, confirm the prior work records and retain supporting documentation (Requirement 1; Note 1).

Step 5 , Reporting to Airbus

• After completion of the replacement or modification, report the accomplishment to Airbus as required by Requirement 1. The AD does not specify the required content or address for the report in the supplied text; therefore, operators should follow Airbus’s standard SB accomplishment reporting requirements or contact Airbus to confirm the reporting recipient, format, and required data to ensure the AD’s reporting obligation is satisfied (Requirement 1).

Step 6 , Address the Requirement 2 timing ambiguity

• The Compliance text includes "For Requirement 2 - Within 60 days after SB embodiment date, as defined in Requirement 1 of this AD." The supplied extract lacks the substantive text of Requirement 2. Practically, operators should:
  • Review their SB embodiment records to identify an SB embodiment date (for example, the date when SB A330-26-3040 was physically embodied on the aircraft).
  • Seek immediate clarification from CASA or Airbus about the substance and expectations of Requirement 2 and the operative definition of "SB embodiment date," and obtain written guidance so that the operator can comply with any additional duty that the 60-day period governs.

Step 7 , Preserve documentary evidence

• Keep records showing the installed P/N, the work performed in compliance with SB A330-26-3040 Rev 02.2 (or prior acceptable SB embodiment), the completion date, and the report submitted to Airbus. Because the AD accepts prior SB embodiment at original issue or revision as acceptable, such records are necessary to demonstrate compliance.

Step 8 , Check configuration-related notes (Note 2)

• Use Note 2 to corroborate whether the part was embodied in production (via listed modification numbers) or in service (via SB A330-26-3030). For example, if an aircraft shows incorporation of mod 40041 in production, that identifies QA06753 as the embodiment route. For QA06753-02, check production modifications 47197, 47883, 50108 (BCRC), 51065, 51329 (LDCC), or service SB A330-26-3030. Accurate tracing avoids misclassification of P/N and deadline errors.

Step 9 , Plan maintenance scheduling and parts procurement

• The AD requires physical replacement or modification. Operators should plan maintenance slots and parts procurement within the compliance windows, taking account of operational schedules, ferry flight constraints, and maintenance certifications. The AD sets absolute windows (18 or 24 months) from the effective date; ensure scheduling allows completion within those windows.

Step 10 , Seek clarifications where the AD is silent

• Because the supplied AD text omits the substance of Requirement 2 and does not define the SB embodiment date or reporting details, operators should request clarifications in writing from Airbus and/or CASA. In particular, confirm:
  • The exact acts tied to the 60-day Requirement 2 window and the operative meaning of SB embodiment date;
  • The recipient(s) and required content for the "report the accomplishment to AIRBUS" obligation;
  • Whether reporting to Airbus satisfies any regulatory filing requirements to CASA, or whether separate regulatory notification is required.

Step 11 , Monitor related authorities

• Note 1 refers to EASA AD 2009-0064 dated 12 March 2009. Operators should check whether the EASA AD contains complementary instructions or different deadlines affecting multinational fleets, and confirm that following the CASA AD and the SB meets all applicable jurisdictional obligations for their operating certificates.

Summary of essential compliance facts from the AD:

• Technical action: replace or modify Halon dual-filter assemblies in forward and bulk cargo compartments per SB A330-26-3040 Rev 02.2 and report to Airbus (Requirement 1).
• Deadlines: P/N QA06753 within 18 months of effective date; P/N QA06753-01 or -02 within 24 months of effective date (Compliance).
• Acceptable prior compliance: SB embodiment at original issue or revision prior to effective date acceptable for Requirement 1 (Requirement 1; Note 1).
• Note 2 provides how the P/Ns are typically embodied by production mods or service bulletin A330-26-3030.
• The supplied text contains an unresolved reference to a Requirement 2 tied to a 60-day window that must be clarified.

Operators and maintenance providers should treat these steps as the minimum compliance pathway based on the supplied AD text and obtain written clarifications where the AD is silent or ambiguous.