AD/A330/94 - Engine Fire Extinguishing Bottle Connection

Scope and applicability: The AD applies to a defined subset of AIRBUS A330 models and a specific set of airframe serial numbers. The applicability block lists models -201, -202, -203, -223, -243, -301, -302, -303, -321, -322, -323, -341, -342 and -343 and then enumerates specific serial numbers. The AD therefore targets airframes with those serial numbers rather than all A330s as a class.

Defect and part identification: The unsafe condition is traced to a manufacturing orientation error on the assembly nut, P/N A2621005000200. The AD explains the nut’s role: it connects the extinguisher discharge head with the piping; its lugs prevent untwisting once hand‑tightened to the correct torque. The defect is inversion of the lugs (wrong orientation of the braking pin), which can falsely indicate correct torque while the connection is not secure.

Failure mode and safety consequence: The AD sets out the failure chain it aims to interrupt. Inverted lugs can permit a loose connection that undermines the fire‑extinguishing system’s integrity and prevents achievement of the required agent concentration. In combination with an engine fire event, this could cause a temporary uncontrolled engine fire. The AD treats that chain as an “unsafe condition” and uses the inspection as the mitigation.

Required action and method: The mandated action is a general visual inspection of the fire‑extinguisher bottle nut assembly of both engines, coupled with corrective actions per AIRBUS Service Bulletin A330‑26‑3043.2. The AD explicitly makes the SB the technical reference for corrective actions, and it additionally mandates that inspection results, whatever they are, must be reported to AIRBUS.

Timing and reporting: There are two compliance timelines. The inspection must be completed within 900 flight hours after the AD’s effective date (unless previously accomplished). Following inspection, the results must be reported to AIRBUS within 30 days of the accomplishment date of the inspection. The AD became effective on 18 December 2008.

Regulatory provenance and cross‑references: The AD references EASA AD 2008‑0196 (27 October 2008), indicating parallel action in European oversight, and relies on an AIRBUS Service Bulletin as the technical standard for inspection and correction. The directive is issued under CASA authority (signed by a CASA delegate).

Single‑event remedy: The AD is framed as a one‑time inspection and correction to “restore connection integrity” , there is no recurring inspection interval or ongoing monitoring requirement specified in the AD text.

Primary obligated parties: The AD imposes mandatory actions on holders of the affected A330 airframes and the organisations who conduct their maintenance. The text requires the inspection and the application of corrective actions “in accordance with AIRBUS Service Bulletin (SB) A330‑26‑3043.2” and requires reporting the inspection results to AIRBUS. That places the operational and administrative burden on the entity responsible for aircraft maintenance and continuing airworthiness, typically the aircraft operator or an approved maintenance organisation acting for the operator.

Fleet segmentation: The applicability is limited to enumerated serial numbers and specific A330 models. Only airframes listed in the AD’s applicability block are within the directive’s mandatory scope. Operators of A330s not listed are not covered by this AD as written, while operators whose tail numbers appear in the list are explicitly included.

Component suppliers and manufacturers: The factual background locates the error at the supplier level , lugs of the assembly nut had been inverted during the supplier’s manufacturing process. That factual attribution identifies the supplier/manufacturer as the upstream origin of the nonconforming part. The AD does not assign liability, but it documents the manufacturing origin of the defect, which could be relevant to contractual, warranty or indemnity relations between Airbus, the supplier, and operators.

Maintenance organisations and line stations: The AD requires a “general visual inspection” of the extinguisher bottle nut assembly on both engines. Maintenance personnel or organisations carrying out scheduled checks, pre‑flight or base maintenance will be the actors who physically execute the inspection and corrective actions. The AD therefore affects maintenance planning, parts provisioning (replacement nuts if defects are found) and reporting workflows.

Regulatory authority and coordination: CASA is the issuing authority in Australia; the AD references EASA AD 2008‑0196, which signals cross‑jurisdictional recognition of the defect. AIRBUS is a recipient of the required reports, and the Service Bulletin named in the AD supplies the technical procedure. Thus the statutory regulator (CASA), the OEM (AIRBUS), the supplier (manufacturer of the nut P/N A2621005000200) and the operator/maintainer all appear in the AD’s operational chain.

Third‑party stakeholders: In the event of an actual engine fire or of a defect resulting in service interruption, other stakeholders could be affected (aircrew, passengers, insurers, lessors). The AD itself does not address compensation, insurance or contractual arrangements; it focuses on inspection and remediation.

Mandatory duty to inspect and correct: The AD’s central duty is the performance of a one‑time general visual inspection of the fire‑extinguishing bottle nut assembly on both engines. If incorrect lug orientation is found, corrective actions must be applied in accordance with AIRBUS Service Bulletin A330‑26‑3043.2. The AD text states this requirement plainly.

Duty to report results to AIRBUS: The AD requires that the inspection results, “whatever they are,” must be reported to AIRBUS. The AD sets a temporal requirement: the report must be submitted within 30 days from the accomplishment date of the inspection. The AD therefore imposes both an inspection duty and an administrative reporting duty.

Timing duty: The inspection must be completed within 900 flight hours after the AD’s effective date, unless previously accomplished. The AD became effective on 18 December 2008. The 900‑flight‑hour window creates a scheduling obligation that operators must incorporate into their maintenance planning.

Method reference duty: The AD prescribes the method for corrective action by reference to AIRBUS Service Bulletin A330‑26‑3043.2. Compliance therefore requires adherence to that SB’s procedures where corrective action is necessary; the AD makes the SB the technical means to meet the AD duty.

Scope limitation and absence of recurring duties: The AD is expressed as a one‑time action to “restore connection integrity”. It does not create an ongoing inspection cycle or recurring monitoring duty in the AD text. Once the one‑time inspection and any corrections are completed and reported, the AD does not specify further mandatory AD‑level follow‑up.

Rights and implicit operational choices: The AD does not enumerate “rights” in the sense of appeals or exemptions within its text. It does, however, implicitly allow that work may have been “previously accomplished,” in which case the 900‑flight‑hour compliance window does not apply. The text does not specify how previously accomplished work is to be documented or accepted; operators will need to maintain evidence of prior compliance. The AD also does not specify a required qualification level for the inspector, but by referencing the AIRBUS SB it implicitly requires that inspection and corrective actions conform to the SB’s criteria and thereby to standard maintenance competence expectations.

Record‑keeping and traceability: The AD mandates reporting to AIRBUS but does not set out additional record‑keeping requirements in the text. Operators should therefore assume a need to retain documentation of inspection and correction to evidence compliance for audits or regulatory review, although the AD itself leaves the content and retention of those records to standard maintenance practice rather than detailing them.

The AD text does not specify statutory penalties: The document contains no express civil or criminal penalty provisions, fines, or specified enforcement procedures. It sets out mandatory technical actions and timelines but does not include an enforcement clause or penalty schedule within the AD text itself.

Issuing authority and effective date: The AD is issued under the authority of the Civil Aviation Safety Authority (CASA), and it is signed by a CASA delegate (James Coyne). The AD became effective on 18 December 2008. As an instrument published by the regulator, non‑compliance would typically be actionable under the regulator’s broader enforcement powers rather than by penalties contained within the AD text. The AD does not itself identify which CASA enforcement mechanisms will be applied in the event of non‑compliance.

Reporting requirement as compliance metric: The AD mandates reporting the inspection results to AIRBUS within 30 days of the inspection. Failure to report would leave the operator without the specific administrative completion the AD requires. The AD treats the reporting obligation as integral to compliance; the AD text does not specify the consequences for failure to report, but absence of the required report would be evidence of non‑compliance.

Practical enforcement levers: Although the AD does not set penalties, it establishes clear, measurable actions and timeframes (inspection within 900 flight hours; report within 30 days). These measurable steps provide enforcement authorities with objective criteria to determine compliance. The AD’s reference to an AIRBUS Service Bulletin for corrective action also creates a concrete technical standard against which regulators and auditors can assess whether remedial measures were adequate.

Interplay with contractual and tort remedies: The AD documents that the defect originated at the supplier’s manufacturing process. While the AD itself does not adjudicate liability, operators or insurers that suffer loss because of failure to detect or remedy the defect might pursue commercial or tort claims against suppliers, manufacturers or maintenance providers. The AD’s factual findings and mandatory reporting regime could be used as evidence in such proceedings, but the AD text contains no directions on how civil claims would be pursued or resolved.

Cross‑reference to EASA AD and AIRBUS SB: The AD explicitly refers to EASA AD 2008‑0196 dated 27 October 2008 and to AIRBUS Service Bulletin A330‑26‑3043.2 as the technical standard for inspection and corrective action. The EASA reference indicates contemporaneous regulatory action in the European jurisdiction, and the SB reference sets the method for remedial mechanics. The AD therefore operates in coordination with OEM technical guidance and parallel foreign oversight.

Regulatory overlay rather than substitution: The AD imposes a CASA requirement that incorporates the AIRBUS SB by reference. It does not purport to replace contractual obligations between operators and manufacturers, nor does it attempt to settle civil liability; it prescribes a safety action within the regulatory instrument. Therefore, the AD supplements but does not supplant private law arrangements.

Reporting to AIRBUS and regulatory transparency: The AD requires that inspection results be reported to AIRBUS within 30 days. That creates a flow of information from operators to the OEM that sits alongside any reporting to CASA. The AD does not specify confidentiality or data handling requirements for those reports; those matters will be governed by other legal instruments or commercial agreements, not by the AD text.

Material traceability and continuing airworthiness obligations: Although the AD itself is a standalone directive, it interacts operationally with continuing airworthiness procedures and maintenance record obligations that operators already maintain. The AD’s requirement to inspect and report will likely be recorded in the operator’s maintenance records and used to evidence compliance under broader regulatory surveillance frameworks. The AD does not set those record‑keeping rules itself.

No express amendment or derogation clauses: The AD does not contain provisions that modify or derogate from any other law. It is a discrete safety directive referencing an OEM service bulletin and an EASA AD, and it must be read alongside any other applicable national or international aviation safety obligations.

Interaction with procurement and supply chains: The AD identifies a supplier manufacturing error as the root cause. While the AD does not create contractual rights, it can affect downstream commercial relationships , operators may demand replacement parts, warranty remedies, or corrective work from OEMs or suppliers. The AD itself does not adjudicate those commercial claims, but it supplies a regulatory basis for remedial action and for claims that might be pursued under separate contracts.

Single issuance and effective date: The AD contains dates and identifiers that indicate a single issuance during 2008. It is styled AD/A330/94 and bears the identifier 13/2008. The AD is dated 6 November 2008 and states an effective date of 18 December 2008. The text does not include any subsequent amendments, supersessions, or revocations.

No amendment schedule recorded in the AD text: There is no amendment history block, no superseding AD number recorded in this document, and no notation of revisions to the compliance times or the scope. The AD is expressed as a single, one‑time action requiring inspection and reporting and does not include later modification within the text provided.

Relationship to EASA AD: The AD notes that “EASA AD 2008‑0196 dated 27 October 2008 refers.” That notation suggests parallel regulatory action by EASA that preceded this CASA AD by a few weeks. The AD text does not state whether CASA’s AD is a verbatim adoption of EASA’s AD or whether it contains any substantive differences; it simply cites the EASA AD as a reference. No later CASA amendments are recorded here.

No recorded bulletin replacement: The AD directs reliance on AIRBUS Service Bulletin A330‑26‑3043.2 but the AD text does not indicate any changes or later versions of that SB. The AD does not specify alternative procedures or authorise deviations; therefore, compliance as stated in the AD would be with the SB version named in the AD.

Implication for operators: Because there is no amendment history recorded in this text, operators should treat this AD as the controlling instrument until a formal superseding AD or amendment is issued by CASA. Any changes to the SB or further regulatory directions would need to be checked against CASA publications for updates beyond the scope of this document.

No litigation referenced in the AD: The AD text contains no mention of any litigation, legal proceedings, or court decisions relating to the defect, the part, the supplier, AIRBUS, or CASA. It does not summarise prior enforcement actions, contested compliance matters, or adjudicated disputes.

Potential litigation topics implied by the facts: While the AD does not record litigation, the factual narrative it contains could create fertile ground for civil claims in separate forums. The AD documents (1) a manufacturing defect at the supplier, (2) a safety‑critical connection that may appear correctly torqued while being insecure, and (3) the potential for temporary uncontrolled engine fire. In the event of an incident where the fire‑extinguishing system failed due to an inverted lug, affected parties (operators, passengers, insurers, lessors) might bring claims against manufacturers, suppliers or maintenance providers, using the AD and the associated SB as evidence of knowledge and standard of care. The AD itself neither initiates nor resolves such litigation.

Evidentiary role of ADs: Although the AD contains no litigation history, regulators’ formal findings in an AD are often cited in subsequent liability disputes as evidence of a recognised unsafe condition and of the technically appropriate remedial action. The AD’s factual findings about P/N A2621005000200 and the nature of the defect could therefore appear in pleadings or expert reports in related civil cases, but the AD text does not itself determine civil liability.

No recorded challenges to the AD: The document includes no record of challenges to the AD’s content, validity, or necessity. If a party wished to contest an AD, that contest would proceed through administrative or judicial channels under applicable aviation legislation; nothing in this AD text records such contestation.

Suggested avenues for researching litigation history: To identify whether litigation ever followed from this AD, a researcher would need to consult court databases, regulatory enforcement records, insurer claim files, and industry incident reports. The AD itself provides the operative facts and dates that would support a search (P/N number, AIRBUS SB reference, EASA AD number and dates, effective date 18 December 2008), but the AD text does not provide post‑issuance legal history.

Narrow applicability may mask wider exposure: The AD is confined to specified A330 models and a discrete list of serial numbers. Operators whose airframes are not listed might nevertheless have the same part fitted as a replacement or during maintenance swaps. The AD does not spell out procedures for parts traceability across fleets. Practically, absence from the serial number list does not guarantee the part cannot be present on other airframes; operators should check parts records and maintenance histories to determine exposure, because the AD as written only mandates action for the enumerated serial numbers.

“General visual inspection” is the required technique: The AD prescribes a general visual inspection rather than a detailed nondestructive test or functional test. A general visual inspection may miss defects that are not externally apparent or that require disassembly. The AD ties corrective action to AIRBUS Service Bulletin A330‑26‑3043.2, so the SB’s detailed procedures will determine whether the SB requires any disassembly or torque verification beyond visual assessment. Operators who rely only on superficial checks risk noncompliance if the SB requires more.

Obligation to report “whatever they are”: The AD requires that the results of the inspection, “whatever they are,” must be reported to AIRBUS within 30 days. That language leaves no de minimis exception; even findings of “no defect found” must be reported. Failure to make the report would leave the compliance record incomplete. Operators must ensure administrative workflows capture and transmit the information within the 30‑day window.

Timing risk relative to flight hours: The inspection deadline is within 900 flight hours after the effective date. Depending on an operator’s utilisation profile (high‑utilisation aircraft could exceed 900 flight hours in a short period), the inspection must be scheduled promptly to avoid non‑compliance. The AD permits prior accomplishment to satisfy the requirement, but operators must have documentary evidence of earlier inspections to rely on that exemption.

Reporting recipient is the OEM, not the regulator: The AD requires reporting to AIRBUS rather than to CASA in the text. Operators should therefore ensure they follow the SB’s or OEM’s reporting channels and keep evidence of submission. The AD does not relieve operators from any additional reporting obligations to CASA that may be required under other regulations.

Single‑event remedy: The AD is a one‑time action to restore connection integrity. It does not impose ongoing monitoring or recurring inspections. If operators later discover evidence of a wider systemic manufacturing problem, they will need to rely on subsequent ADs or regulatory action; this AD does not create continuing surveillance obligations beyond the one inspection and report.

Parts identification and replacement logistics: The AD identifies the part number (P/N A2621005000200). If corrective action requires replacement, operators must source approved replacement parts. The AD does not specify whether Airbus will supply replacement parts or the supplier will issue a recall; procurement and costs will therefore fall to existing commercial arrangements unless the OEM or supplier announces remedial support.

No penalties specified within the AD: The AD does not state penalties for non‑compliance. That does not mean non‑compliance is without consequence; it merely means the AD text does not spell out enforcement consequences. Operators should not interpret the absence of explicit penalties as permissive.

Follow the AIRBUS Service Bulletin named in the AD: The AD mandates corrective actions “in accordance with AIRBUS Service Bulletin (SB) A330‑26‑3043.2.” To comply with the AD’s technical requirement, maintenance personnel must obtain and follow that SB for the precise inspection method, any disassembly, acceptance criteria for lug orientation, and corrective procedures if incorrect orientation is found. The SB will also specify report formats and required technical data for any corrective work; the AD ties compliance to that SB.

Perform the general visual inspection on both engines within 900 flight hours: The AD requires a one‑time general visual inspection of the fire‑extinguishing bottle nut assembly of both engines. This inspection must be completed within 900 flight hours after the AD’s effective date (18 December 2008), unless the inspection has already been accomplished. Where the inspection was previously performed, operators should retain documentary proof to demonstrate they met the AD before the effective date.

Report the inspection results to AIRBUS within 30 days: Regardless of outcome, the AD requires the results be reported to AIRBUS within 30 days of the inspection’s accomplishment date. Operators should follow the reporting procedure set out in the AIRBUS SB or in OEM guidance to ensure the report reaches the correct Airbus inbox and to retain proof of submission. Include serial numbers, part numbers (P/N A2621005000200), inspection dates, findings and any corrective actions taken.

If incorrect lug orientation is found, apply corrective action per the SB: The AD directs that any required corrective actions be applied in accordance with AIRBUS SB A330‑26‑3043.2. That will likely include reorientation or replacement of the assembly nut and verification of connection integrity. Do not improvise technical fixes outside the SB’s instructions unless authorised by the regulator or OEM through an approved deviation process.

Document and retain evidence of compliance: While the AD does not specify internal record‑keeping durations, operators should record the inspection and any corrective action in the aircraft’s maintenance log and retain supporting documentation (inspection report, parts replaced, work orders, photos if helpful). Keep copies of the report submitted to AIRBUS and any acknowledgements. These records serve as evidence of compliance during audits or any follow‑up by CASA.

Check parts traceability beyond listed serial numbers: Given the manufacturing origin of the defect, compliance for listed serial numbers does not preclude the same part being fitted elsewhere. Operators should review parts manifestation and maintenance history to confirm whether P/N A2621005000200 is present on other airframes. If that is the case, consider voluntarily performing the inspection on other airframes or seek advice from Airbus/CASA on whether additional action is required.

Coordinate with maintenance scheduling to meet flight‑hour deadline: Integrate the inspection into planned maintenance to ensure completion within the 900‑flight‑hour window. For high‑utilisation aircraft, this may require immediate scheduling in the next available maintenance opportunity. If operators rely on third‑party maintenance providers, confirm scope and timing in work orders.

Confirm reporting details and communication channels with AIRBUS: The AD obliges reporting to AIRBUS. Operators should confirm the exact reporting address or portal referenced by the SB or by Airbus communications, include required technical details (P/N, serial numbers, inspection date, findings, corrective action), and keep a record of what was sent.

Prepare for corrective parts procurement: If corrective action requires replacement nuts, arrange procurement of approved parts in accordance with the SB and standard parts procurement rules. Verify part numbers and traceability to avoid circular compliance issues.

Retain readiness for regulator queries: Even though the AD does not specify penalties, CASA issued the AD; CASA may enquire about compliance as part of oversight activities. Be prepared to present inspection and reporting evidence to CASA on request.