AD/A330/101 - Cable Loom 9R Routing

This Directive rests on a small number of linked technical and regulatory concepts drawn directly from the AD text.

• Applicability by production mods and serial numbers. The AD is not levied by broad model designation alone. It applies to specified A330 model codes and then further restricts coverage to aeroplanes "on which both Airbus modification 40379 and either Airbus modification 49894 or 51304 or 52048 or 52712 or 53559 or 53732 or 54115 or 55632 or 55722 have been embodied during production," while excluding aeroplanes on which "Airbus modification 57744 has been embodied during production." The AD therefore uses production embodiment records (modifications embodied during production) as the gating criterion for regulatory obligation.

• Prescribed engineering action. The mandated hardware and routing change is narrowly specified: "install a stirrup on the terminal block 5507VT between frame (FR) 53.9 and FR54 and modify wiring route 9R." The AD ties the required method to a manufacturer-issued service bulletin, identifying "Airbus Service Bulletin A330-92-3080 dated 12 November 2008 or later revision approved by the European Aviation Safety Agency (EASA)" as the controlling technical document. That makes compliance method-specific: the SB (or an EASA-approved later revision) is the avenue of compliance.

• Safety mechanism identified. The Background links a physical proximity issue (route 9R of the In‑Flight Entertainment system too close to the Lower Deck-Mobile Crew Rest harness) to component-level chafing (between harness 6581VB and harness 5495VB or 6938VB). The chain of possible harm is explicit: chafing could cause a short circuit of wires "dedicated to oxygen," which in an emergency could prevent "a large number of passenger oxygen masks" from supplying oxygen, thereby creating a risk of personal injury. The AD therefore defines a causal chain from routing geometry to impaired emergency oxygen deployment.

• Regulatory cross-reference and approval control. The AD "refers" to EASA AD 2009-0076 and specifically requires EASA approval for later revisions of the Airbus service bulletin to be acceptable for compliance. In practical terms, this anchors technical acceptance to EASA's approval process rather than leaving it to the operator or manufacturer alone.

• Temporal enforcement: effective date and compliance window. The document sets an effective date ("This Airworthiness Directive becomes effective on 4 June 2009") and a compliance deadline ("Within 24 months after the effective date of this Directive"). The combination defines both when regulatory force commences and the maximum permissible delay to complete the work.

These core elements together structure the Directive as a targeted, time-bound engineering mandate tied to aircraft production records and executed via a manufacturer service bulletin supervised by EASA approval. Each of these points above is stated, or directly implied, in the AD text.

The AD's direct addressees are the operators and custodians of the specific A330 aeroplanes described in the Applicability block. The AD lists the affected model variants explicitly: "A330-201, A330-202, A330-203, A330-223, A330-243, A330-301, A330-302,A330-303, A330-321, A330-322, A330-323, A330-341, A330-342 and A330-343 model aeroplanes, all manufacturer serial numbers (MSN)," but the obligation is further narrowed to those MSNs "on which both Airbus modification 40379 and either Airbus modification 49894 or 51304 or 52048 or 52712 or 53559 or 53732 or 54115 or 55632 or 55722 have been embodied during production," and excepting those on which "Airbus modification 57744 has been embodied during production." This creates a duty tied to aircraft identity (MSN) and documented production configuration (which production modifications were embodied).

Consequently, the following parties will be affected in practical, record-driven ways:

• Airlines and other operators who possess, operate or lease the affected MSNs. They carry the operational obligation to ensure the required modification is scheduled and performed within the 24‑month window. The AD text places the requirement on the aeroplane, and operators are the usual custodians responsible for maintaining airworthiness records and effecting AD compliance.

• Lessors and owners. Where an aircraft is leased, the owner/lessor must be aware of AD applicability because the work may be an owner responsibility under lease contracts, depending on contractual allocation of maintenance and modification obligations. The AD’s gating by MSN and production modifications means owners must verify the embodied mods for each serial number in their fleet.

• Continuing airworthiness and maintenance organisations. Approved maintenance organisations and certifying engineers who perform the work must follow "Airbus Service Bulletin A330-92-3080 dated 12 November 2008 or later revision approved by the European Aviation Safety Agency (EASA)," so maintenance providers will need to obtain the SB and any later EASA‑approved revision used for compliance, and document the work performed.

• Regulatory compliance and airworthiness inspectors. The Civil Aviation Safety Authority, represented by a delegate ("James Coyne, Delegate of the Civil Aviation Safety Authority"), issued the AD. While the AD text itself does not set out inspector roles or enforcement steps, the Directive will be a material compliance item for any airworthiness audit or inspection of affected MSNs after the effective date.

• Aircraft records and engineering teams. Proper determination of applicability requires production and modification records (evidence that specific Airbus modifications were embodied during production). The AD therefore affects engineers and records-management personnel who must confirm whether mod 40379 and one of the listed later mods (or mod 57744) were embodied.

• Potentially training and planning teams. Because the AD prescribes a physical alteration in a specific fuselage area ("between frame (FR) 53.9 and FR54") and concerns harness routing, airlines and maintainers must plan man-hours, access procedures, and possibly spare parts for the "stirrup on the terminal block 5507VT" called for by the SB.

The AD’s exception for aeroplanes with Airbus mod 57744 embodied in production creates a class of the affected population who do not have to comply, so the burdens and actions described apply only where the production-modification profile matches the AD’s criteria. The AD thereby places the practical burden of configuration verification, work planning, and execution on operators, owners, and maintenance providers in the supply chain for the affected A330 MSNs.

The Directive states a small number of discrete duties and establishes a limited set of rights by implication from its content.

Duties (explicit in the AD text)

• Perform the mandated modification. Operators of affected aeroplanes must "install a stirrup on the terminal block 5507VT between frame (FR) 53.9 and FR54 and modify wiring route 9R in accordance with Airbus Service Bulletin A330-92-3080 dated 12 November 2008 or later revision approved by the European Aviation Safety Agency (EASA)." That sentence establishes the substantive work obligation and ties the compliance method to the specified service bulletin or an EASA‑approved later revision.

• Comply within the stated timeframe. The AD sets a temporal duty: compliance "Within 24 months after the effective date of this Directive." The effective date is given as "4 June 2009." Therefore, the duty is to complete the SB‑specified work on each applicable aeroplane by 4 June 2011 (24 months after the effective date), using the SB or an EASA‑approved later revision.

• Determine applicability accurately. The AD requires operators to consider the production-mod embodiment profile. Applicability is limited to aeroplanes with "both Airbus modification 40379 and either Airbus modification 49894 or 51304 or 52048 or 52712 or 53559 or 53732 or 54115 or 55632 or 55722" embodied during production, excluding those with mod 57744 embodied. While the AD does not prescribe a specific record-checking process, the obligation to comply only applies to aeroplanes meeting that configuration test; therefore, an implied duty is to examine production and modification records to determine whether the AD applies to a given MSN.

Duties (procedural/practical)

• Use an EASA-approved revision if not using the dated SB. The AD permits reliance on "later revision[s] approved by the European Aviation Safety Agency (EASA)," therefore any deviation from the dated SB requires EASA approval of the later revision.

Rights and limitations (as implied by the AD text)

• Right to rely on the named SB or an EASA-approved later revision. The AD does not require bespoke engineering alternatives. It explicitly permits a later EASA-approved revision of the Airbus SB, which gives operators the right to use a newer procedure provided EASA has approved it. The AD does not, however, state that other methods of compliance are acceptable; the statement confines acceptable compliance methods to the specified SB or EASA‑approved later revisions.

• Right to non‑application where exclusion present. Aeroplanes "on which Airbus modification 57744 has been embodied during production" are excepted from the applicability statement. Those aircraft therefore have a right not to comply under this AD, as per the explicit exclusion.

What the AD does not state

• The Directive contains no text setting out any rights to financial assistance, no mechanism for deferral beyond the 24‑month window, and no process for requesting alternative methods of compliance within the AD itself. Any such processes, if available, would fall outside the text as printed and must be inferred or sought from the issuing authority or through the EASA approval mechanism for revised service bulletins. The AD also does not provide a procedural framework for record acceptance or audit; it simply prescribes the technical measure and the acceptable technical references.

In short, the AD places concrete duties on operators of the identified production‑configured MSNs: to determine applicability from production records, to obtain and follow Airbus Service Bulletin A330‑92‑3080 (dated 12 November 2008) or an EASA‑approved later revision, and to complete installation and routing changes within 24 months of 4 June 2009. It grants a de facto right to rely on EASA-approved SB revisions and grants an explicit exception for aeroplanes with mod 57744 embodied in production.

The AD text as supplied contains no express penalty provisions, sanctioning language, or enforcement procedures beyond the issuance of the directive itself. The document records the issuing authority and the effective date but does not specify fines, administrative penalties, or criminal sanctions. The only enforcement-related facts present in the AD are these:

• Issuer identification. The AD is signed by "James Coyne, Delegate of the Civil Aviation Safety Authority," dated 17 April 2009, and records the effective date, "This Airworthiness Directive becomes effective on 4 June 2009." That establishes the regulatory provenance and the moment from which the compliance deadline runs.

• Compliance requirement and timeframe. The AD makes compliance mandatory by stating the action required and the deadline: "Install a stirrup ... and modify wiring route 9R ... Within 24 months after the effective date of this Directive."

What the AD does not state (and therefore cannot be assumed from the AD text)

• The AD does not enumerate any specific penalties for failure to comply within the stated timeframe. It does not set out the enforcement mechanisms that the Civil Aviation Safety Authority (or any other body) would use to address non‑compliance, nor does it specify who will monitor or certify compliance, how documentation of compliance must be lodged, or any appeal or relief process.

Practical consequence of the absence of penalty text in the AD

• Because the AD itself is silent on penalties and enforcement procedures, compliant entities should treat the AD as a binding technical regulatory instrument whose verification and enforcement are likely to be handled through the broader regulatory and oversight framework maintained by the issuing authority. The AD, however, does not in its text provide procedural instructions for demonstrating compliance. Operators and maintainers facing an AD that does not specify enforcement steps will typically (as apparent from the AD’s references) need to rely on standard records management, certificate-of-completion documentation from the maintenance organisation, and communications with the regulator for audit and verification. None of those steps are prescribed in the AD text; they are implications operators must operationalise.

Because the AD does not itself set fines or specify enforcement procedures, a practitioner should not infer particular penalty amounts or enforcement processes from this AD alone. Any inquiry into enforcement practice, potential sanctions for non‑compliance, or processes for documentation and acceptance of compliance will require consultation of the Civil Aviation Safety Authority’s broader regulatory instruments and guidance, which are outside the AD text provided.

The AD text contains only a narrow set of cross‑references and does not purport to be a general statement about its interaction with the wider regulatory framework. Nevertheless, the AD explicitly connects to one external regulatory instrument and implicitly relies on authorities outside the AD for technical approvals.

Direct cross-reference

• EASA AD reference. The AD states "Note: EASA AD 2009-0076 refers." This is an explicit cross-reference to an EASA Airworthiness Directive. The AD therefore situates itself relative to EASA action, indicating that the safety issue and the remedial action have been the subject of EASA regulatory attention. The text does not reproduce the contents of EASA AD 2009‑0076; it only notes the reference.

• EASA approval of service bulletin revisions. The AD allows compliance via "Airbus Service Bulletin A330-92-3080 dated 12 November 2008 or later revision approved by the European Aviation Safety Agency (EASA)." This creates an operational link between CASA’s AD and EASA’s approval process: later revisions of the Airbus Service Bulletin will be acceptable only if EASA has approved them. The AD therefore defers to EASA on technical acceptance of future SB revisions.

Implicit interactions

• Aircraft continuing airworthiness regime. The AD is an instrument that modifies continuing airworthiness obligations for the affected aeroplanes. While the AD does not specify how it interacts with other domestic laws or regulations governing maintenance, certification, or operations, a practitioner must read it as an element of the continuing airworthiness regime that affects maintenance programmes, aircraft records, and release-to-service procedures for the affected MSNs. The AD itself does not set out those interactions in statutory language.

• Production modification records as determinative. The AD’s applicability criterion hinges on whether certain Airbus modifications were "embodied during production." This makes production engineering records and modification embodiment documentation decisive legal facts for determining the AD’s applicability to a given aeroplane. The AD therefore interacts with any law or regulation that governs amplication, preservation and evidentiary status of such production records,though the AD does not name those laws.

What the AD text does not do

• It does not claim to supersede or amend other legislative instruments. The AD does not state that compliance with it alters the operation of other aviation laws or regulations. Nor does it set out any interface with contractual arrangements between lessors and lessees, insurance policies, or commercial obligations; the AD simply prescribes a technical action for specified aircraft.

• It does not provide a mechanism for seeking a national-specific alternative to EASA approval. Rather, the AD anchors acceptability of later SB revisions to "EASA" approval, indicating a reliance on the European regulator’s technical acceptance as a condition of compliance.

In short, the AD explicitly interacts with EASA’s regulatory output and approval processes as the technical gatekeeper for SB revisions, and implicitly interacts with the domestic continuing airworthiness framework through its content-based obligations and modality of determining applicability by production modifications. The AD does not itself spell out the procedural or statutory consequences for other domestic laws; those interactions must be navigated by affected parties in the broader regulatory compliance context.

The AD text provided contains limited temporal metadata and does not show any subsequent amendments or revisions within the document itself. The information available in the AD about timing and issuance is as follows:

• Issuance date and signatory. The bottom of the document is signed "James Coyne, Delegate of the Civil Aviation Safety Authority" and carries the date "17 April 2009." That indicates when the AD was signed by a CASA delegate.

• Effective date. The AD explicitly states "This Airworthiness Directive becomes effective on 4 June 2009." That gives a clear start point for regulatory force and for the 24‑month compliance window to begin.

• Compliance deadline. The AD prescribes completion "Within 24 months after the effective date of this Directive." Taking the effective date at face value, the compliance deadline is 24 months after 4 June 2009.

• Relationship to EASA service bulletin revisions. The AD allows compliance by reference to "Airbus Service Bulletin A330-92-3080 dated 12 November 2008 or later revision approved by the European Aviation Safety Agency (EASA)." This clause contemplates that the controlling SB may be revised in the future and provides a path for such revisions to be accepted for compliance, but it makes acceptance contingent on EASA approval. The AD itself does not list any later revision nor record any follow-on amendments to the AD text.

• Note referencing EASA AD. The AD includes the note "EASA AD 2009-0076 refers." That indicates contemporaneous EASA action but does not represent an amendment to the CASA AD.

What is not present in the AD text

• No subsequent amendment record. The supplied AD does not include any record of amendment, supersession or cancellation. It does not say that it amends any earlier CASA AD, nor does it indicate later CASA amendments or revocations.

• No version history for the AD itself. The document does not show version numbers or revision dates beyond the effective date and the SB date referenced.

Conclusion on amendment history drawn from the text

Based solely on the AD text provided, the act’s amendment history is that it was signed on 17 April 2009 and became effective on 4 June 2009, with no subsequent amendments or revisions recorded in the supplied material. The text does invite later SB revisions approved by EASA to be used for compliance, but such SB changes are external to the AD itself; the AD’s own text does not show amendments or successive editions.

A practitioner or records keeper requiring a complete amendment trail should therefore assume that any further history (superseding ADs, cancellations, or amendments) would need to be sought from the Civil Aviation Safety Authority or EASA records outside the AD text as supplied.

The AD text contains no references to litigation, judicial review, or administrative appeals relating to AD/A330/101. It does not recount any legal challenges or outcomes. The document is administrative in nature and limited to the following procedural and documentary elements that are present:

• Issuating authority and authorising signature. The AD is signed by "James Coyne, Delegate of the Civil Aviation Safety Authority" and dated "17 April 2009." The presence of a delegate’s signature indicates the AD was issued under delegated authority but the AD provides no record of any legal proceedings associated with its issuance.

• Cross-reference to EASA AD. The AD notes "EASA AD 2009-0076 refers," but it does not report litigation or dispute associated with that EASA AD.

Absent content

• No cases named. The AD does not cite or name any court decisions, tribunal findings, or administrative determinations.

• No dispute record. There is no indication in the AD text of objections, petitions for reconsideration, requests for alternative compliance, or any adjudicated controversy.

What this means for research or practice

• The supplied AD contains no litigation history; therefore the only authoritative source for any past disputes, appeals, or legal challenges would be external to the AD text. Practitioners seeking litigation history must consult tribunal and court databases, CASA records of petitions or objections, and EASA records that fall outside of this document.

• Because the AD does not describe any adjudicative history, one should not presume from the AD alone that there were no challenges; the AD simply does not record them. Verification of litigation history requires further inquiry to the issuing authority and to the judicial/administrative record.

The AD packs several practical and procedural pitfalls that flow directly from its narrow text. These are operational cautions drawn from the AD language.

1. Applicability depends on production embodied modifications, not on aftermarket changes. The AD applies to aeroplanes "on which both Airbus modification 40379 and either [a listed set of mods] have been embodied during production" and excludes those "on which Airbus modification 57744 has been embodied during production." That language refers specifically to modifications embodied during production, not to retrofit or maintenance shop actions. Operators must therefore check production records (manufacturer serial and mod‑embodiment documentation) rather than simply checking the current physical configuration or maintenance history. Failure to recognise the production-based criterion could result in unnecessary work or failure to comply when applicable.

2. Multiple listed mods create a combinatorial check. The applicability requires mod 40379 plus at least one of the enumerated list (49894, 51304, 52048, 52712, 53559, 53732, 54115, 55632, 55722). Operators must check for the presence of mod 40379 and any one of the alternatives. That requires robust record validation against the manufacturer's production/modification list for each MSN.

3. Exception clamps downess on some aircraft only. Aircraft with mod 57744 embodied during production are specifically excluded. Operators must be careful not to conflate post-production embodiment with production embodiment. The AD’s exclusion is narrow; a failure to correctly identify whether mod 57744 was embodied during production may cause misapplication or non‑compliance.

4. The AD prescribes a specific SB and defers to EASA for later revisions. The work must be done "in accordance with Airbus Service Bulletin A330-92-3080 dated 12 November 2008 or later revision approved by the European Aviation Safety Agency (EASA)." If an operator attempts to apply an internal modification procedure or a manufacturer revision that lacks EASA approval, that route is not authorised by the AD text.

5. Timing flexibility is limited to a two‑year window. The compliance period is "Within 24 months after the effective date of this Directive." That is a finite window that must be tracked against maintenance schedules. While 24 months allows operational planning flexibility, the AD provides no text for extension, deferral or alternative compliance, so operators must plan to finish the work within the window or seek clarifying guidance from the regulator.

6. The hazard identified is specific and consequential. The Background links chafing between harnesses to potential short circuits affecting oxygen-dedicated wires, which "could result in a large number of passenger oxygen masks not being supplied with oxygen." That risk underscores why operators should prioritise accurate applicability determinations and timely completion of the SB work. The consequence described is operationally critical in an emergency.

7. The AD is narrow in substance but not in implied administrative impact. Although the physical task is specific (installing a stirrup and re-routing), it implicates record checks, engineering oversight, parts availability for "stirrup on the terminal block 5507VT," maintenance scheduling in a narrow fuselage area (between FR 53.9 and FR54), and the need to document completion consistent with continuing airworthiness practices. The AD itself does not prescribe documentation form,operators must ensure they preserve maintenance release records aligned with standard practice.

8. No penalties or enforcement details in the AD text. The AD contains no explicit penalties or enforcement mechanisms; operators should not assume absence of enforcement. Rather, they must treat the AD as a binding airworthiness requirement and address compliance and record-retention proactively because enforcement practice, audit expectations, and penalty frameworks are not described in the AD.

9. External dependencies. Acceptance of later SB revisions requires EASA approval. If an operator relies on an updated SB, they must check and confirm EASA approval status. The AD’s reference to EASA AD 2009‑0076 also means that cross-jurisdictional regulatory materials may be relevant.

10. Confusion risk from shorthand and identification numbers. The AD uses many numeric identifiers (terminal block 5507VT, harness 6581VB, 5495VB, 6938VB, multiple Airbus mod numbers). Errors in transcribing or cross-referencing these numbers during planning can result in the wrong work being performed or the wrong applicability determination.

Each of the above points follows directly from the AD text and the way its requirements are framed. Operators, maintainers, lessors and owners should mitigate these gotchas by establishing clear workflows for verifying production mod embodiment, confirming EASA approvals for SB revisions, scheduling work within the 24‑month window, and keeping contemporaneous records of completed work.

Compliance with this AD requires a sequence of verifiable steps that can be executed by operators, owners and authorised maintenance organisations. The AD text itself prescribes the required action, acceptable reference materials, applicability test, and timeframe. Below is a practical, source‑grounded compliance checklist and recommended procedural steps derived strictly from the AD wording.

1. Identify affected aircraft by MSN and production embodiment

   • For each A330 in the fleet, determine the manufacturer serial number (MSN).
   • Check production records to determine whether the aeroplane had "Airbus modification 40379" embodied during production.
   • Check whether, during production, the aeroplane also had embodied any one of: 49894, 51304, 52048, 52712, 53559, 53732, 54115, 55632, or 55722.
   • Exclude aeroplanes on which "Airbus modification 57744 has been embodied during production." The AD’s applicability condition is literal: the AD applies only where both 40379 and one of the listed mods were embodied during production, and not where 57744 was embodied during production.

2. Confirm applicability status and document conclusion

   • Record the production‑mod embodiment evidence for each MSN and the conclusion (applicable / not applicable) with supporting documents. The AD’s applicability hinges on these production‑embodiment facts, so contemporaneous evidentiary records (manufacturer build sheets, production change logs) should be retained.

3. Obtain the controlling Service Bulletin or an EASA‑approved later revision

   • Obtain "Airbus Service Bulletin A330-92-3080 dated 12 November 2008" and check for any later revisions.
   • If a later revision is to be used, confirm that it is "approved by the European Aviation Safety Agency (EASA)" as required by the AD text. Retain evidence of EASA approval if a later revision is used.

4. Plan maintenance action

   • Schedule the physical work within the compliance window: "Within 24 months after the effective date of this Directive" (effective date: 4 June 2009; compliance deadline runs 24 months from that date).
   • Plan access to the fuselage area "between frame (FR) 53.9 and FR54" and ensure resources for installing "a stirrup on the terminal block 5507VT" and adjusting "wiring route 9R" as specified.
   • Where necessary, secure any parts inventory (the stirrup and any harness supports) and ensure personnel qualified to work on electrical harness routing and oxygen-related wiring perform the work.

5. Execute work strictly in accordance with the SB or EASA‑approved revision

   • Perform the installation and wiring modification in accordance with the steps, inspections and torque/clearance tolerances documented in the Service Bulletin.
   • Do not substitute an alternative method of compliance unless separately authorised by a competent regulatory authority; the AD text authorises only the named SB or an EASA‑approved later revision.

6. Verify electrical separation and perform required checks

   • After routing modifications and installation of the stirrup, perform any functional tests, continuity checks and inspection items specified in the SB to verify that harness chafing risk has been removed and that oxygen-dedicated wiring remains intact and functionally isolated from the In-Flight Entertainment harness.

7. Record completion and retain evidence

   • Record completion of the SB action in the aircraft’s maintenance records, identifying the SB revision used, date of completion, maintenance organisation and certifying engineer.
   • Keep evidence of EASA approval if a later SB revision was used, copies of the SB pages showing applicable steps, and test/inspection results required by the SB.

8. Communicate with lessors/owners where relevant

   • If the operator is a lessee, confirm with the lessor whether the AD work is the operator’s responsibility or the lessor’s, and ensure contractual obligations are met. The AD does not resolve contractual allocation; it simply imposes the technical requirement on the aeroplane.

9. Prepare for audits and inspections

   • Because the AD prescribes a continuing airworthiness action, be ready to present records of applicability determination and completion to inspectors or auditors. The AD itself does not specify the documentation format; operators should use standard maintenance release and logbook entries consistent with their regulatory environment.

10. Monitor for later EASA-approved SB revisions

• While the AD permits later EASA‑approved SB revisions, ensure that any subsequent revision relied upon for compliance has the required EASA approval and retain that approval documentation with maintenance records.

All steps above derive directly from the AD wording: the prescriptive action, the SB reference and EASA‑approval caveat, the applicability test by production embodiment, the 24‑month compliance timeframe and the effective date. The AD does not specify the forms of evidence, approvals for alternative methods, or enforcement steps; practitioners must therefore use standard aviation maintenance recordkeeping practices and liaise with the regulatory authority where necessary to document compliance or seek clarification.

For legal and compliance teams, ensure that your internal maintenance control processes can demonstrate: (1) correct identification of MSNs to which the AD applies, (2) SB revision and EASA approval status at the time of compliance, (3) completion evidence conforming to maintenance certification practice, and (4) retention of production‑embodiment documentation that underpins the applicability determination.