AD/A330/88 Amdt 1 - Intermediate Pressure Turbine Overspeed Protection

The document combines a narrow technical remedy with operational-documentation obligations and scope adjustments. The central technical concept is activation of an Intermediate Pressure Turbine Overspeed protection function (IPTOS) through reprogramming of the Data Entry Plug (DEP) on both engines (Requirement). The DEP reprogramming implements logic that limits IPT speed, described in the AD as "limiting the IPT speed (Engine Thrust) when overheat is detected in IPT" (Background). The stated causal chain the AD addresses is: HP/IP oil vent tube degradation or damage can permit fire inside or outside the vent tube, that fire can result in IPT disc drive arm fracture, which in turn can cause IPT disc overspeed and lead to uncontained engine failures such as multiple turbine blade loss or HP/IP turbine disc burst (Background). The AD therefore treats IPTOS activation as a preventive control to avoid progression from vent-tube failure modes to overspeed and uncontained events.

The AD ties technical implementation to a specified service bulletin: Airbus SB A330-73-3049 Revision 01 dated 13 November 2008 (Requirement). It allows compliance by carrying out the SB original issue dated 14 November 2007 if that work was done prior to the AD effective date (Requirement). The AD is explicit that only revisions to the SB that are approved by EASA meet the requirement (Requirement), thereby making EASA approval an acceptance condition for any later SB revision.

Compatibility and fleet applicability are second-order technical concepts. The original AD had limited applicability because of Flight Warning Computer compatibility with aircraft not equipped with Multi Mode Receivers; Airbus developed a new Flight Warning Computer standard T2 whose embodiment is possible on A330 aircraft fitted with RR Trent 700 engines not equipped with Multi Mode Receivers; the Amendment retains the original Directive requirement and extends applicability to all A330 aeroplanes fitted with RR Trent 700 engines (Background). The AD therefore mixes a software/configuration change (DEP reprogramming) with hardware/avionics considerations (Flight Warning Computer standard T2, Multi Mode Receiver presence).

Operational-documentation and procedural concepts are also present. The AD states that "the accomplishment of SB A330-73-3049 instructions has an operational consequence, the operator must contact Airbus to get the associated operational documentation" (Requirement). This requires operators to obtain and integrate operational changes resulting from the reprogramming, not merely do the software change.

Finally, the AD references an external airworthiness authority action: "Note: EASA AD 2009-0075 refers" (Requirement/Note). This places the technical requirement within a multi-jurisdictional regulatory context where the SB revisions must be EASA-approved and EASA issuing an AD is relevant.

These concepts together structure the directive: a defined hazard; a defined technical mitigant; compatibility and fleet-scope conditions; a requirement to update operational documentation; cross-reference to EASA approval; and explicit dates for effectiveness and compliance.

The AD identifies operators and aircraft by model, engine family, and modification status. The Applicability statement is specific: "A330-243, -341, -342 and -343 models, all manufacturing serial numbers (MSN) except those on which Airbus modification 56722 has been embodied during production" (Applicability). The Requirement and Background further link the directive to aircraft fitted with Rolls-Royce Trent 700 series engines; the Background narratives and subsequent paragraphs repeatedly refer to RR Trent 700 engines and the original incident involving a RR Trent 772 B engine. The AD therefore affects:

• Operators of Airbus A330 models listed in the Applicability (A330-243, -341, -342 and -343).
• Among those aircraft, the AD excludes MSNs with Airbus modification 56722 embodied during production; such aircraft are explicitly outside the directive's scope (Applicability).
• Aircraft fitted with RR Trent 700 engines are the focus of the extension of applicability; the Background explains the original issue targeted aircraft equipped with Multi Mode Receivers and RR Trent 700 engines, and the Amendment extends to all A330 aeroplanes fitted with RR Trent 700 engines after resolving Flight Warning Computer compatibility concerns (Background).

Cost and operational effect fall on the operator, because the Requirement prescribes that the operator must "Perform a reprogramming of Data Entry Plug on both engines to activate Intermediate Pressure Turbine Overspeed protection function in accordance with the instructions of Airbus SB A330-73-3049 Revision 01 dated 13 November 2008 or later revision approved by the European Aviation Safety Agency (EASA)" and that the "operator must contact Airbus to get the associated operational documentation" (Requirement). The AD does not describe any obligations on third parties beyond following the SB and EASA-approved revisions; it presumes interaction between operator and Airbus for operational documentation.

Aircraft maintenance organisations, avionics shops, and engineers doing DEP reprogramming are affected functionally because they must execute the SB instructions and ensure both engines are reprogrammed. The Requirement explicitly states the action is to be done "on both engines", indicating a fleet-level, per-aircraft dual-engine technical change rather than a single-engine selective fix.

Finally, the AD refers to an EASA AD (EASA AD 2009-0075), and it conditions acceptance of SB revisions on EASA approval, so entities that authorise or record compliance (maintenance organisations, continuing airworthiness managers) will need to track EASA-approved SB revisions to validate compliance. The AD also records effective and compliance dates that govern when the obligation is binding: effective 4 June 2009 and compliance required no later than 31 July 2009 (Compliance).

Duties

• Perform DEP reprogramming on both engines of each affected aeroplane in accordance with Airbus SB A330-73-3049 Revision 01 dated 13 November 2008, or a later revision that is approved by EASA (Requirement). The AD is prescriptive about both the procedure (DEP reprogramming) and the applicable written standard (SB revision and EASA approval).
• Contact Airbus to obtain associated operational documentation because the reprogramming "has an operational consequence" and the "operator must contact Airbus to get the associated operational documentation" (Requirement). This is an explicit duty to update or receive operational material in addition to performing the on-aircraft work.
• Ensure compliance by the stated deadline: "No later than 31 July 2009" (Compliance). The AD sets a firm calendar deadline for operators to complete the required work and operational documentation update.
• Where the operator had already complied prior to the AD effective date, ensure that the modification was done "in accordance with the instructions of SB A330-73-3049 original issue dated 14 November 2007" because that is accepted to comply with this Amendment (Requirement). This creates a conditional retrospective compliance pathway.

Rights and conditions available to operators

• The AD permits compliance by relying on an earlier SB action: modification done before the effective date per the SB original issue dated 14 November 2007 "is acceptable to comply with the requirements of this Amendment" (Requirement). This gives operators who acted earlier a right to treat those prior actions as satisfying the AD, subject to the SB being the SB original issue stated.
• Operators may use a later revision of SB A330-73-3049 provided that later revision is approved by EASA. The AD explicitly requires that any later revision must be EASA-approved (Requirement).
• The AD sets an applicability carve-out: aircraft with Airbus modification 56722 embodied during production are excluded from the Applicability and therefore are not required by this AD to carry out the DEP reprogramming specified (Applicability).

Procedural implications implicit in the AD text

• The AD ties technical compliance to documentation from Airbus and to EASA approval processes. Operators are required to contact Airbus for operational documentation and to ensure any SB revision applied is EASA-approved (Requirement; Note). These are procedural preconditions that create coordination tasks and record-keeping duties for operators and their maintenance organisations.
• The AD retains the original technical requirement while extending applicability due to Flight Warning Computer standardisation (Background). Operators should interpret the AD as both a technical fix and a systems-compatibility instruction: even where an aircraft previously lacked a required avionics fit (Multi Mode Receiver), the AD now expects the operator either to have T2 Flight Warning Computer standard embodied or otherwise meet the applicability conditions.

What the AD does not state as a duty

• The AD does not set out any penalty or enforcement mechanism within its text. It provides effective and compliance dates and the technical instructions to be followed but does not itself specify civil or criminal penalties or the manner of enforcement in this document (Compliance; Requirement). Any enforcement or penalty regime is not included in the text provided.

Operators, maintenance organisations, and continuing airworthiness managers are therefore duty-bearers for executing DEP reprogramming, updating operational documentation with Airbus, documenting compliance relative to SB versions and EASA approvals, and observing the compliance timeline.

The AD as provided sets procedural obligations and dates but does not itself contain expressed penalties, fines, or enforcement mechanisms. The document records administrative markers: the Amendment becomes effective on 4 June 2009 and requires compliance "No later than 31 July 2009" (Compliance), and it is signed by James Coyne, Delegate of the Civil Aviation Safety Authority, dated 24 April 2009 (signature block). Those elements establish the AD as an issuing action with an effective date and a compliance deadline.

What the AD states

• Effective date: "This Amendment becomes effective on 4 June 2009" (Compliance).
• Compliance date: "No later than 31 July 2009" (Compliance).
• Acceptance of certain prior work: "Modification of an aeroplane, prior to the effective date of this Amendment, in accordance with the instructions of SB A330-73-3049 original issue dated 14 November 2007 is acceptable to comply with the requirements of this Amendment" (Requirement).

What the AD does not state

• The AD text supplied does not specify sanctions, penalty amounts, or the enforcement authority’s discretionary powers, and it does not describe procedural steps for enforcement such as notices, hearings, suspension, or grounding. The directive records a mandatory technical and documentation action and sets dates, but it does not contain an enforcement schedule or penalty clause within the supplied text.

Implications for operators

• Because the AD prescribes mandatory corrective action and a compliance date, operators must treat the AD as an actionable continuing airworthiness requirement. The absence of explicit penalties in the AD document does not remove compliance risk; it does, however, mean that any enforcement or sanction mechanism is external to the AD text provided and would require reference to other authority documents or regulations for detail. The AD does make clear the criteria for compliance (SB revision and EASA-approved later revisions, DEP reprogramming on both engines, and contact with Airbus for operational documentation) and establishes a temporal requirement.

Record-keeping and verification

• Operators should document the DEP reprogramming actions and the operational documentation obtained from Airbus, and should record whether the work was performed in accordance with SB A330-73-3049 revision 01 or an EASA-approved later revision, or in accordance with the original SB dated 14 November 2007 for actions completed prior to the AD effective date. The AD itself identifies these documentation standards as the means of demonstrating compliance (Requirement).

Cross-reference

• The AD notes "EASA AD 2009-0075 refers" (Requirement/Note), indicating that EASA has issued or referenced corresponding action. Any enforcement practice may therefore involve coordination with or reliance on EASA determinations, and operators should preserve records that show conformity with the EASA-approved SB revision referenced by the AD.

In short, the AD mandates action and dates but does not detail penalties or enforcement processes within the text provided; operators must therefore manage compliance and documentation in anticipation of external enforcement mechanisms not set out in this document.

Within the supplied text, the AD explicitly references and conditions compliance on technical materials and actions issued by Airbus and EASA. The AD instructs compliance with Airbus SB A330-73-3049 Revision 01 dated 13 November 2008 or later revisions "approved by the European Aviation Safety Agency (EASA)" (Requirement). The AD further notes "EASA AD 2009-0075 refers" (Note). These references create explicit points of interaction:

• Service Bulletin linkage: The AD is not a standalone technical manual; it ties operative compliance to Airbus SB A330-73-3049. Compliance is thereby calibrated to the technical instructions in that SB, and to later SB revisions only if EASA has approved them (Requirement). The AD thus interacts with Airbus publication processes and with EASA’s approval authority for SB revisions.
• EASA AD cross-reference: By stating that EASA AD 2009-0075 refers, the AD positions itself within parallel or complementary regulatory actions taken by EASA (Note). That cross-reference implies that conformity with EASA-approved SB revisions has regulatory significance for meeting this AD’s requirements.

Interactions not in the text

• The AD does not expressly reference domestic aviation statutes, regulations, enforcement processes, or how compliance with this AD constitutes compliance with other national regulatory instruments. It does not articulate how this AD interfaces with civil penalties, aircraft certification records, or air operator certificate conditions. The supplied text confines its interactions to Airbus SBs and EASA approvals.

Technical interplay

• The AD explains that the original issue had limited applicability "due to Flight Warning Computer compatibility issue with aircraft not equipped with Multi Mode Receivers" and that Airbus developed a "new Flight Warning Computer standard T2" whose embodiment is possible on affected aircraft, enabling extension of applicability (Background). This means the AD’s applicability and practical ability to implement the mandated DEP reprogramming depends on, and therefore interacts with, avionics standards and retrofits embodied on individual aircraft.

Pre-existing modifications

• The AD excludes aircraft on which Airbus modification 56722 has been embodied during production (Applicability). Aircraft with that modification are outside the AD’s scope, which creates a direct interaction with the state of production modifications recorded on an MSN. Operators must therefore check their aircraft configuration records against that modification to determine applicability.

Operational documentation

• The AD states the operator must contact Airbus to get associated operational documentation because the SB instructions have "an operational consequence" (Requirement). That creates an interaction between technical modification and operations manuals, checklists, or procedures that operators must update to reflect the DEP reprogramming and IPTOS activation.

EASA approval as a condition precedent

• The AD conditions the use of any later SB revision on EASA approval. This means that the AD’s technical standard is not merely Airbus-issued text but is tied to EASA’s acceptance process; operators must ensure that any SB revision used for compliance bears EASA approval.

In short, within the provided text, the AD operates by referencing Airbus technical materials and EASA approvals, by depending on aircraft-specific embodied modifications such as mod 56722 and Flight Warning Computer standard T2, and by requiring updates to operational documentation. The instrument does not, in the supplied text, describe how it meshes with national enforcement statutes or other domestic regulatory instruments.

The supplied text provides an explicit chronology and relational statements tying the current Amendment to an original Directive and to Airbus SB issue dates. Key items in the amendment history recorded in the AD text include:

• Original SB issuance: The SB original issue is dated 14 November 2007. The AD states that "Modification of an aeroplane, prior to the effective date of this Amendment, in accordance with the instructions of SB A330-73-3049 original issue dated 14 November 2007 is acceptable to comply with the requirements of this Amendment" (Requirement). This establishes that earlier SB work is a valid compliance pathway.
• SB Revision 01: The AD prescribes compliance with Airbus SB A330-73-3049 Revision 01 dated 13 November 2008 or later EASA-approved revisions (Requirement). Revision 01 is therefore the primary prescriptive technical standard referenced in this Amendment.
• Original AD effective date: The document notes that "The original issue of this Directive became effective on 28 August 2008" (Background). This situates the present Amendment relative to that earlier Directive.
• This Amendment effectiveness and compliance extension: The Amendment itself "becomes effective on 4 June 2009" (Compliance) and extends the compliance timeframe to "No later than 31 July 2009" (Compliance). The text says that "At the same time compliance is extended to 31 July 2009" in the context of extending the applicability to all A330 aeroplanes fitted with RR Trent 700 engines (Background).
• Rationale for amendment and scope extension: The AD explains that the original issue required IPTOS activation by DEP reprogramming but had a limited applicability because of a Flight Warning Computer compatibility issue connected to the absence of Multi Mode Receivers. Airbus developed a new Flight Warning Computer standard T2 that can be embodied on A330 aeroplanes fitted with RR Trent 700 engines not equipped with Multi Mode Receivers. Consequently, "this Amendment retains the requirement of the original issue of this Directive and extends the applicability to all A330 aeroplanes fitted with RR Trent 700 engines" (Background).
• External reference: The AD includes a cross-reference noting "EASA AD 2009-0075 refers" (Note). This implies that the Amendment is in dialog with EASA regulatory materials contemporaneous to the Amendment.

What the Amendment history shows in the supplied text

• The Amendment preserves the technical remedy of the original Directive but broadens fleet applicability following an avionics standard development (Flight Warning Computer T2). It formalises that the technical standard for compliance is SB A330-73-3049 Revision 01 (13 November 2008) and allows prior compliant work under the SB original issue dated 14 November 2007 to count. It adjusts the timeline by making the Amendment effective 4 June 2009 and extending the deadline to 31 July 2009.

Items not present

• The supplied text does not list any further subsequent amendments, revocations, or superseding actions beyond Amdt 1 and the references cited. There is no record here of later ADs, rescissions, or further updates beyond those explicit dates and the revision history noted.

The Amendment chain in the supplied text therefore runs: SB original issue (14/11/2007) → original Directive effective 28/08/2008 → SB Revision 01 (13/11/2008) → Amendment AD/A330/88 Amdt 1 effective 04/06/2009 with compliance extended to 31/07/2009 and cross-reference to EASA AD 2009-0075.

The AD text supplied contains no references to litigation, court proceedings, appeals, or administrative review related to this Directive or to SB A330-73-3049. It records factual background, technical requirements, amendment chronology, and the issuing signature, but it does not mention any disputes, judicial challenges, determinations, or case names.

What the AD explicitly provides

• A narrative background of an incident involving an A330 fitted with Rolls-Royce Trent 772 B engines that experienced an "engine #1 uncontained multiple turbine blade failure" and investigative findings linking HP/IP oil vent tube degradation to IPT disc drive arm fracture and IPT disc overspeed (Background). This is investigative and causal material, not litigation material.
• Administrative facts including dates, SB references, the effective/compliance dates, and the name and signature of the issuing delegate, James Coyne, dated 24 April 2009.

What is not in the AD

• There is no mention in the supplied text of any appeals against the AD, of compliance disputes that reached adjudicative forums, or of precedent-setting litigation. There are no instructions referencing dispute-resolution mechanisms or legal challenges.

Implication for researchers

• The absence of litigation references in the AD means that, within the supplied document, there is no recorded case law or adjudicative history tied to this Directive. If litigation history exists in external sources, it is not captured in the text provided.

Researchers and practitioners seeking litigation history will therefore need to consult external records or case databases, but those materials lie outside the scope of the supplied AD text, which contains no litigation material.

The AD text contains several specific conditions and narrowly worded elements that can create practical traps if overlooked. The following are concrete points taken directly from the AD that operators, maintainers and compliance staff should note.

Applicability carve-out and modification tracking

• The Applicability clause excludes aircraft "on which Airbus modification 56722 has been embodied during production" (Applicability). Operators who assume the AD applies to all listed A330 subtypes without checking MSN production records may mistakenly undertake unnecessary work or fail to recognise legitimate inapplicability. Maintenance records must be checked for embodiment of mod 56722.

Both engines

• The Requirement specifies DEP reprogramming "on both engines" (Requirement). Partial compliance by reprogramming a single engine would not meet the text of the AD.

Technical documentation specificity

• The AD ties the required work to Airbus SB A330-73-3049 Revision 01 dated 13 November 2008, or "later revision approved by the European Aviation Safety Agency (EASA)" (Requirement). That conditions compliance on both (a) following the SB and (b) ensuring any later SB revision used is EASA-approved. Using a later SB revision not yet approved by EASA would, per the AD text, not satisfy the stated requirement.

Prior work acceptance conditional on SB issue

• The AD accepts prior modifications "in accordance with the instructions of SB A330-73-3049 original issue dated 14 November 2007" as satisfying the Amendment (Requirement). Operators must ensure their prior work exactly matches the original SB issue as cited; assertion of prior compliance needs documentary support showing the specific SB issue used.

Operational-documentation obligation

• The AD states "As the accomplishment of SB A330-73-3049 instructions has an operational consequence, the operator must contact Airbus to get the associated operational documentation" (Requirement). It is therefore insufficient to carry out the DEP reprogramming mechanically; operators must also obtain and integrate any operational documentation and presumably revise operating procedures or manuals as necessary. Failure to obtain or implement operational documentation could leave the operator non-compliant even if the DEP reprogramming were completed.

Flight Warning Computer compatibility nuance

• The Background explains the original AD had limited applicability because of Flight Warning Computer compatibility with aircraft not equipped with Multi Mode Receivers, and that a new Flight Warning Computer standard T2 can be embodied on those aircraft so applicability could be extended (Background). An operator whose aircraft lacks the T2 standard or Multi Mode Receiver must verify how embodiment or retrofit interacts with the reprogramming requirement. The AD does not list the embodiment process for T2; operators must verify whether their aircraft meet the avionics preconditions to activate IPTOS.

Cross-authority approvals

• The AD requires EASA approval for later SB revisions. The AD also refers to EASA AD 2009-0075. Operators must ensure the SB revision they rely upon is EASA-approved and be aware that EASA documents referenced may affect the acceptable pathways for compliance. Assuming Airbus approval alone without confirming EASA approval for later revisions is a trap.

Dates

• The AD sets a compliance deadline "No later than 31 July 2009" and an effective date 4 June 2009 (Compliance). These dates are binding in the AD text and may be overlooked. The AD also allows prior compliance under the original SB dated 14 November 2007, but only if performed prior to the effective date. Operators must document timing.

Narrow description of the hazard

• The Background links HP/IP oil vent tube carbon deposits and damage to fire and subsequent IPT disc failures, laying out a causal chain (Background). The DEP reprogramming is a software/configuration mitigation that limits IPT speed on overheat detection. This is a mitigation for a specific failure progression; operators should not assume broader engine issues are covered by this AD.

No penalties stated in the AD text

• The AD does not specify penalties or enforcement mechanisms in the supplied text (Compliance; Requirement). Operators should not infer the absence of enforcement risk from that omission; they must preserve records and confirm compliance procedures against any applicable enforcement rules outside this document.

In sum, the primary gotchas are failure to check embodiment of mod 56722, failure to reprogramme both engines, reliance on the wrong SB issue or a later SB lacking EASA approval, failure to obtain required operational documentation from Airbus, and overlooking avionics compatibility conditions (Flight Warning Computer T2 and Multi Mode Receiver presence).

The AD lays out a concise compliance pathway; below are the steps, as stated in the AD text, with practical items to record and verify.

1. Determine applicability for each aeroplane

   • Check whether the aircraft is an A330-243, -341, -342 or -343, and confirm the manufacturing serial number (MSN) (Applicability).
   • Verify whether Airbus modification 56722 was embodied during production on that MSN. If mod 56722 is embodied, the AD excludes that aircraft from the Requirement (Applicability).

2. Verify engine fit and avionics compatibility

   • Confirm the aircraft is fitted with Rolls-Royce Trent 700 series engines, as the Amendment extended applicability to all A330 aeroplanes fitted with RR Trent 700 engines following Flight Warning Computer T2 standard developments (Background).
   • Where Flight Warning Computer compatibility or Multi Mode Receiver fitment is an issue, confirm whether Flight Warning Computer standard T2 has been embodied. The AD notes the T2 standard makes embodiment possible for aircraft not equipped with Multi Mode Receivers (Background).

3. Plan and execute technical work per the SB

   • Perform reprogramming of the Data Entry Plug (DEP) on both engines to activate the IPTOS protection function in accordance with Airbus SB A330-73-3049 Revision 01 dated 13 November 2008, or a later revision only if that later revision has been approved by the European Aviation Safety Agency (EASA) (Requirement).
   • Ensure the work scope, steps, and acceptance checks match the SB instructions used for the work.

4. Obtain operational documentation from Airbus

   • Contact Airbus to obtain the "associated operational documentation" because the SB instructions "have an operational consequence" (Requirement). This may include amended procedures, checklists, or operations manual content necessary to operate correctly with IPTOS active.

5. Record and verify compliance

   • Record the SB issue or revision used, the EASA approval status if a later revision is used, the DEP reprogramming actions on both engines (including work-order references, dates, signatures), and receipt and incorporation of any operational documentation from Airbus.
   • If the modification was already done prior to the AD effective date, verify that it was done "in accordance with the instructions of SB A330-73-3049 original issue dated 14 November 2007", and retain documentary evidence of that SB edition and the date the work was completed (Requirement).

6. Meet the deadline

   • Ensure that the DEP reprogramming and operational documentation updates are completed "No later than 31 July 2009" for aircraft subject to the Amendment (Compliance). For prior modifications, confirm they were completed before the AD effective date and per the original SB issue to qualify as acceptable compliance (Requirement).

7. Cross-reference EASA materials where applicable

   • Confirm the SB revision in use is EASA-approved if it is later than Revision 01, and be aware that the AD references EASA AD 2009-0075 (Note). Maintain records of EASA approvals that validate the chosen SB revision.

8. Communicate with maintenance organisations and crews

   • Inform maintenance providers that both engines require DEP reprogramming and supply them with the applicable SB revision and any relevant operational documentation obtained from Airbus.
   • Ensure flight crew and operations staff receive and implement the operational documentation changes required after DEP reprogramming, so that operations comply with the functional changes introduced by IPTOS activation.

9. Documentation retention

   • Keep records that link the MSN, mod 56722 embodiment status, SB edition/revision used, EASA approval references for any later revisions, work completion dates, and operational documentation obtained from Airbus. The AD makes these elements the basis for demonstrating compliance (Applicability; Requirement).

10. If unsure, seek Airbus confirmation

• The AD explicitly instructs operators to contact Airbus for operational documentation. Where there is ambiguity about SB revisions, avionics compatibility, or whether prior work qualifies, obtain written confirmation from Airbus and retain it.

Following the AD text precisely involves both carrying out a technical software reprogramming on both engines per a specified SB revision and ensuring operational materials are updated via Airbus contact, with records demonstrating compliance by the stated date.