AD/ARRIEL/31 - Reduction Gear Box Intermediate Pinion

The AD rests on a small set of tightly defined technical and regulatory concepts stated in the source text. Those concepts are:

• Applicability: The AD applies to the Turboméca Arriel 1B, 1D and 1D1 turboshaft engines, all serial numbers (Applicability; Note 1). The text expressly cautions that these engines are installed on, but not limited to, specific Eurocopter AS 350 model helicopters. The scope is component‑level: the Reduction Gear Box Intermediate Pinion (P/N 0 292 70 779 0) is the object of the directive (Requirement).

• Mandatory replacement: The AD requires replacement of the existing intermediate pinions with pinions that incorporate Turboméca modification TU 232. The method of compliance is prescribed: in accordance with Turboméca Mandatory Service Bulletin 292 72 0276 Version B dated 6 November 2008 or later approved revision (Requirement; Note 2). The AD therefore delegates the technical work specification to the OEM service bulletin.

• Timing and effective dates: The AD has two temporal anchors. It "becomes effective" on 12 March 2009, and it specifies a compliance deadline of no later than 28 February 2011 (Compliance). These dates establish the window for operators to plan and carry out the replacement.

• Safety causal chain: The AD sets out a causal finding: ruptures were reported and traced to initiation at the teeth root due to increased vibratory stresses, primarily caused by teeth wear over service life (Background). It then links the hardware failure to operational consequences, including power turbine overspeed, uncommanded in‑flight shutdown, and potential emergency autorotation on single‑engine helicopters (Background).

• Technical remedy: Turboméca modification TU 232 is described in the AD as incorporating a damping ring below the teeth and shot peening of the teeth roots to reduce vibratory stresses and improve tooth resistance, thereby reducing risk of fatigue cracks (Background). The AD makes the TU 232 modification the required configuration.

• Cross‑reference to other regulatory action: The AD references EASA AD 2009‑0002 dated 7 January 2009, signalling alignment with or recognition of parallel regulatory action outside Australia (Note 2).

• Delegation and authority: The signature block identifies the issuing authority as the Civil Aviation Safety Authority, with the AD signed by a delegate, James Coyne, on 27 January 2009. The AD thus presents as a CASA instrument (signature block).

Each of these concepts determines a specific decision node for operators and maintainers: identification of affected engines, procurement or sourcing of TU 232 pinions, scheduling of maintenance within the compliance window, execution in accordance with the OEM service bulletin, and record keeping to demonstrate compliance by the deadline. The AD’s text also defines the technical content that must be followed rather than leaving the technical remedy to operator discretion.

The affected parties are identified explicitly and implicitly in the AD text.

• Primary affected entities: Owners and operators of Turboméca Arriel 1B, 1D and 1D1 turboshaft engines, all serial numbers (Applicability). The AD notes that these engines are known to be installed on, but not limited to, Eurocopter AS 350 series helicopters (AS 350 B, AS 350 BA, AS 350 B1 and AS 350 B2) (Applicability, Note 1). Therefore, operators of those helicopter airframes should check engine type data to determine applicability. The AD’s scope is engine‑centric and applies regardless of airframe, provided the engine model falls within the named Arriel variants.

• Maintenance organisations and technicians: The requirement to replace the Reduction Gear Box Intermediate Pinion in accordance with Turboméca Mandatory Service Bulletin 292 72 0276 Version B or an approved revision places practical obligations on certificated maintenance organisations, maintenance personnel and any third party contracted to perform the work. They must follow the service bulletin’s procedures, source the correct modified pinion, and carry out work in a manner that constitutes compliance with the AD (Requirement).

• OEM and parts suppliers: Turboméca (the OEM) is implicated as the supplier of the mandated modification TU 232 and the author of the mandatory service bulletin referenced by the AD (Requirement; Note 2; Background). The AD’s specification of a particular OEM service bulletin creates demand for TU 232‑incorporating pinions and for approved revisions of the service bulletin. Parts suppliers and distributors will be engaged in supplying the modified pinions and in managing inventories.

• Regulators and oversight bodies: The Civil Aviation Safety Authority is the issuing authority, with the AD signed by a CASA delegate (signature block). The AD also refers to EASA AD 2009‑0002 dated 7 January 2009 (Note 2). While the AD itself is a CASA instrument, operators and their compliance functions will need to coordinate with CASA and may consider the related EASA document for harmonisation or importation of certified parts.

• Airworthiness management and continuing airworthiness personnel: Personnel responsible for continuing airworthiness of affected helicopters and engines,airworthiness managers, accountable managers, safety managers,must schedule the mandated replacement by the compliance deadline and ensure records of compliance are maintained. This includes updating maintenance programmes and ensuring the replacement is incorporated into airworthiness documentation in the specified timeframe.

The AD’s applicability to "all serial numbers" broadens the affected population to include engines of all ages within the Arriel 1B/1D/1D1 family. The AD therefore imposes an obligation on any operator with those engines, not only those with high time engines. Operators who believe they have already accomplished an equivalent modification or replacement must be able to demonstrate it, because the compliance clause gives an option of "unless previously accomplished" (Compliance). The AD’s reference to the OEM service bulletin means that technically competent organisations, not just airframe operators, will hold responsibility for ensuring the mandated work is performed in an approved manner.

The AD creates a precise, limited set of duties and triggers a small bundle of procedural rights by reference.

Duties

• Mandatory replacement: The explicit duty is to replace the Reduction Gear Box Intermediate Pinion (P/N 0 292 70 779 0) with pinions incorporating Turboméca modification TU 232 (Requirement). The AD leaves no alternative remedy within its text; replacement with TU 232 pinions in accordance with the specified service bulletin is the prescribed action.

• Method of compliance: The duty is to accomplish the replacement in accordance with Turboméca Mandatory Service Bulletin 292 72 0276 Version B dated 6 November 2008 or a later approved revision (Requirement; Note 2). This ties the required method and technical standard to the OEM’s service instructions and any later approved revision of that bulletin. Compliance requires adherence to the procedures and possibly the acceptance and approval processes for later revisions.

• Timing: The duty is time‑bounded: replacement must be completed no later than 28 February 2011, unless previously accomplished (Compliance). The AD also states it becomes effective on 12 March 2009, establishing the period for regulatory effect (Compliance).

• Applicability scope: The duty applies to all engines of the specified Arriel 1 variants, all serial numbers, as listed in the applicability text (Applicability). That means there is an affirmative duty on operators with affected engines to check serial numbers and arrange replacement.

Rights and procedural implications implicit in the text

• "Unless previously accomplished": The compliance clause recognises that if an operator has already completed the TU 232 modification or equivalent before the compliance deadline, the operator is not required to re‑perform the work. This creates a right to rely on prior compliant work being accepted as satisfying the AD, provided the prior work is demonstrably equivalent to the AD requirement (Compliance).

• Reliance on OEM documentation: The AD prescribes the service bulletin as the method of compliance. Operators have the right to follow that document and any later "approved revision" of it as the route to compliance (Requirement; Note 2). The term "approved revision" implies a process by which later revisions of the service bulletin must receive approval to be an acceptable method of compliance; however the AD text does not specify the approval authority or process for such approval.

• Cross‑reference to EASA AD: The AD’s reference to EASA AD 2009‑0002 suggests operators may consult that instrument in a parallel regulatory environment. The text does not define any rights arising from that cross‑reference but signals harmonisation considerations (Note 2).

Prescriptive vs discretionary elements

• The AD is prescriptive on the what, how and when: what component to replace, how to do it (per Turboméca MSB Version B or approved later revision), and when to complete the work (by 28 February 2011). The AD does not grant discretion to substitute a different technical fix within its own text nor does it describe a pathway for obtaining an alternative method of compliance; such pathways, if they exist, are not set out in the source text.

• The AD does not set out record‑keeping, reporting, or approval procedures in its text. The AD’s signature and effective date indicate CASA issuance, but the AD does not detail CASA’s enforcement actions, penalty regime, or approval procedures for later service bulletin revisions. Those matters are therefore outside the AD’s explicit scope as presented in the source.

In sum, the AD conveys a clear duty to replace a named part with one incorporating a named modification, by a set date, using a named OEM service procedure. It recognises prior compliance as an exception but does not describe administrative processes for approval, reporting or enforcement within the text provided.

The AD text supplied does not specify penalties, enforcement mechanisms, or the administrative consequences of non‑compliance. The instrument sets the mandatory technical requirement, an effective date (12 March 2009) and a compliance deadline (no later than 28 February 2011), and is signed by a CASA delegate (signature block). Beyond those elements, the AD does not itself enumerate sanctions, enforcement procedures, or the remedies available to the regulator.

What the source does state that has enforcement implications

• Issuing authority: The AD carries the signature of James Coyne, Delegate of the Civil Aviation Safety Authority, dated 27 January 2009. The signature indicates the AD is a CASA instrument (signature block). The presence of an issuing regulator implies that regulatory oversight and enforcement capacity exist, but the AD text does not state how CASA will enforce compliance, inspect compliance, or respond to non‑compliant operators.

• Compliance clause: The AD requires replacement "no later than 28 February 2011, unless previously accomplished" (Compliance). The presence of an explicit compliance deadline and the absence of alternative methods in the text create a discrete obligation that regulated parties would be expected to meet.

Matters not addressed in the AD text

• No penalties specified: The AD does not specify civil, administrative, or criminal penalties for failure to comply. It does not set out a fine schedule, suspension provisions, or other sanctions.

• No inspection or reporting procedure specified: The AD does not prescribe how operators must demonstrate compliance, what records must be kept, whether reporting to CASA is required upon completion, or whether CASA will audit or inspect compliance.

• No alternative means of compliance: The AD does not detail a process for seeking approval of alternative methods of compliance, nor does it state which authority should approve any alternative.

Practical implications for affected parties

• Absence of explicit penalties in the AD text does not mean that regulatory consequences do not exist. The AD’s status as a CASA instrument strongly implies that consequences for non‑compliance will be governed by the broader regulatory framework administered by CASA or other applicable aviation law, but the AD text itself does not provide those statutory or procedural links.

• Operators and maintenance organisations facing this AD should treat it as mandatory within the specified timeframe and plan to document the replacement and retention of records necessary to demonstrate compliance, because the AD fixes what must be done and when. Any questions about specific enforcement processes, sanctions or approval pathways for alternatives are not addressed in the AD text and would need to be resolved with the issuing authority or through reference to the broader statutory framework, which is not reproduced in the source.

In short, the AD defines the mandatory technical corrective action and the deadline but does not, in the text provided, define the enforcement mechanisms or penalty regimes by which compliance will be assured or enforced.

The AD text provides two explicit points of interaction and leaves other potential legal intersections unstated in the instrument itself.

Express cross‑references in the AD

• Reference to Turboméca Mandatory Service Bulletin: The AD requires replacement "in accordance with Turboméca Mandatory Service Bulletin 292 72 0276 Version B dated 6 November 2008 or later approved revision" (Requirement; Note 2). This creates an operational interaction between the AD and the OEM’s technical instructions. The AD thus makes compliance contingent on adherence to an OEM document, and any legal or contractual obligations attached to that service bulletin (warranty, technical acceptance, parts certification) will interact with the AD compliance requirement.

• Reference to EASA AD: The AD contains a note stating "EASA AD 2009‑0002 dated 7 January 2009 refers" (Note 2). That reference points to parallel regulatory action by the European Union Aviation Safety Agency. The AD text itself does not state the legal effect of that reference, but it signals alignment with or recognition of regulatory action occurring under another jurisdiction’s airworthiness authority. Operators who are also subject to foreign regulatory regimes may therefore have to coordinate compliance and documentation between CASA and EASA requirements.

What the AD does not state

• No reference to broader legislation: The AD does not cite the enabling statute, regulations, or penalties under which CASA issued the AD. It does not cite the Civil Aviation Act, Civil Aviation Safety Regulations, or other enabling instruments within the text provided. Therefore the AD does not itself delineate the statutory powers used to issue it, nor how it integrates with those instruments.

• No mention of approvals, alternative methods, or delegated approvals: The AD requires compliance with a later "approved revision" of the service bulletin but does not specify who approves such revisions or how operators may seek approval for alternative methods of compliance. Those administrative interfaces are therefore not covered by the AD text.

Operational and contractual interactions

• Maintenance contracts and capabilities: Because the AD delegates technical method to the OEM service bulletin, operators will interact contractually with maintenance providers for execution. The AD will therefore influence maintenance scheduling, parts procurement, and possibly warranty and spare parts arrangements with Turboméca and parts suppliers.

• International operators and import/export of parts: The AD’s reference to EASA AD 2009‑0002 suggests that for operators with cross‑jurisdictional operations, there may be overlapping obligations. The AD text does not clarify how to resolve any differences between CASA requirements and EASA requirements; it merely notes the EASA AD.

• Safety reporting frameworks: The AD describes a causal chain based on "several events" reported in service (Background). While the AD itself does not specify reporting obligations, the background indicates interaction with safety reporting systems that feed regulator action. The AD does not specify whether operators must report completion or residual issues to CASA.

In sum, the AD interacts directly with OEM service documentation and is framed in the context of parallel EASA regulatory activity. It does not, within the provided text, articulate the broader statutory basis or enforcement architecture, nor does it set out procedures for approvals, appeals, or alternative compliance methods. Those legal interactions therefore occur outside the AD’s text and require consultation with CASA and the OEM to resolve in practice.

The source AD text contains limited material relevant to amendment history. What the text records directly is as follows:

• Issuance and signature: The AD is signed by James Coyne, Delegate of the Civil Aviation Safety Authority, dated 27 January 2009 (signature block).

• Effective date: The AD states it "becomes effective on 12 March 2009" (Compliance). The signing date precedes the effective date by some weeks.

• Compliance deadline: The AD sets the mandatory completion date as "No later than 28 February 2011, unless previously accomplished" (Compliance).

• Service bulletin version and revision path: The AD prescribes compliance "in accordance with Turboméca Mandatory Service Bulletin 292 72 0276 Version B dated 6 November 2008 or later approved revision" (Requirement; Note 2). The explicit allowance for "later approved revision" creates an internal revision pathway for the technical document that may result in amended methods of compliance, provided those later revisions are approved. The AD text does not name the approving authority or set a procedure for such approval.

• Cross‑reference to EASA AD: The AD notes that EASA AD 2009‑0002 dated 7 January 2009 refers (Note 2). This indicates contemporaneous international regulatory action but does not itself constitute an amendment to the Australian AD.

Matters not contained in the AD

• No recorded amendments to the AD itself: The source does not record any subsequent amendments to the AD, revocations, supersessions, or extension of compliance deadlines. The AD as provided appears as a single issuance with its defined effective and compliance dates.

• No historical trace of prior actions: The AD includes the text setting out the safety background and remedial requirement but does not include references to prior CASA instruments amending the AD or to follow‑up ADs that supersede it. The AD does not present a version history beyond the prescribed service bulletin Version B and allowance for later approved revisions of that bulletin.

• No record of approvals for later revisions: Although the AD allows later approved revisions of the Turboméca service bulletin as a method of compliance, the AD text does not include any record of later approved revisions having been approved or incorporated.

Practical consequence for readers

• To determine whether the AD has been amended, superseded or otherwise varied since the signature date, users must consult authoritative CASA records beyond the AD text provided, because the AD itself contains no post‑issuance amendment details. The AD sets out initial issuance data and an explicit route for compliance via the OEM service bulletin, but not a subsequent amendment trail.

The AD text contains no references to litigation, legal challenges, judicial decisions, appeals, or disputes arising from the issuance or content of the AD. The source does not cite any cases, does not set out any contested administrative proceedings, nor does it record any judicial review actions. The only legal‑style elements present in the source are the issuance by CASA (signature block), the effective and compliance dates, and references to an EASA AD and an OEM service bulletin.

What the absence of litigation references means in the document

• No litigation recorded: The absence of any litigation history within the AD text indicates that, as far as this document is concerned, there are no appended notes or corrections that report legal challenges or outcomes. The AD makes no claim about whether it has been or might be contested; it simply sets out the technical requirement and effective/compliance dates.

• No precedent or case law embedded: The AD does not rely on or cite case law or past tribunal decisions as the basis for its content. There are no judicial interpretations or binding legal authorities quoted in the instrument.

Practical steps for researchers and practitioners

• To establish whether litigation has occurred in relation to this AD, whether any orders or stays were obtained, or whether any judicial clarification has been provided about its application, one must consult court records, tribunal records, or CASA’s public records beyond the AD text. The AD itself provides no litigation trail.

• For compliance risk assessment, because the AD contains the safety rationale and mandatory action but no litigation record, operators should assume the AD was issued as an operative safety measure and consider the operational and contractual implications described earlier. Any legal history affecting enforceability, interpretation, or validity cannot be derived from the source AD text.

In short, the supplied AD contains zero litigation history and provides no internal pointer to disputes or judicial outcomes.

The AD text is concise but contains several elements that may produce practical pitfalls or points of misinterpretation for an operator, maintainer or compliance officer. The following items draw attention to specific lines in the source and explain what to watch for.

1. "All serial numbers" applicability scope (Applicability)

   • The AD applies to Arriel 1B, 1D and 1D1 engines "all serial numbers." That language removes a serial‑number or batch carve‑out. Operators cannot assume the AD only applies to older engines; it applies across the entire population of those model variants. Failure to check serial numbers against the model designation only risks missing an affected engine.

2. "Known to be installed on, but not limited to" airframes (Applicability, Note 1)

   • The AD lists Eurocopter AS 350 variants as known installations but expressly says the list is not exhaustive. Operators of other helicopter types that might carry Arriel 1 series engines must check engine type data. Treat the airframe list as illustrative, not exhaustive.

3. Exact part number replacement and modification designation (Requirement; Background)

   • The AD names P/N 0 292 70 779 0 as the Reduction Gear Box Intermediate Pinion to be replaced and mandates the TU 232 modification as the required enhancement. Using an incorrect replacement part, or a pinion that lacks TU 232, would not satisfy the AD. Verification that the replacement pinion indeed incorporates TU 232 is therefore crucial.

4. Method of compliance fixed to a specific OEM document and version (Requirement; Note 2)

   • Compliance must be "in accordance with Turboméca Mandatory Service Bulletin 292 72 0276 Version B dated 6 November 2008 or later approved revision." Operators must obtain the exact version B or an approved later revision. Relying on an earlier version of the bulletin or on informal OEM guidance risks non‑compliance.

5. "Later approved revision" is undefined in the AD text (Requirement; Note 2)

   • The AD allows later approved revisions but does not identify the authority or process for approval. Operators should seek clarity from CASA and/or the OEM about which later revisions are "approved" for the purposes of the AD, and obtain documentary evidence of approval to justify reliance.

6. Compliance timing window (Compliance)

   • The AD becomes effective on 12 March 2009 and mandates replacement by no later than 28 February 2011. That is an approximately two‑year window from the effective date. Operators must plan for parts procurement lead times, maintenance scheduling, and potential grounding time if necessary.

7. "Unless previously accomplished" caveat (Compliance)

   • If the modification has already been completed before the AD’s compliance deadline, the operator may claim compliance. However the AD provides no test for equivalence,operators should retain documentation proving that the prior action conforms to TU 232 and the Turboméca service bulletin to avoid disputes.

8. Safety rationale tying wear to vibratory stresses (Background)

   • The AD attributes ruptures mainly to increased teeth wear over engine life causing increased vibratory stresses. This suggests heightened attention when engines approach or exceed typical wear thresholds. Operators should not assume that low hours engines are safe without verifying the pinion configuration and condition.

9. Reference to EASA AD but no harmonisation instructions (Note 2)

   • The AD notes EASA AD 2009‑0002 refers, but the Australian AD does not explain how to treat any differences between the two instruments. For operators subject to both CASA and EASA oversight, managing potential discrepancies in wording, compliance pathways or documentation will require proactive coordination.

10. Lack of penalties or procedural detail in the AD text (Penalties and enforcement)

    • The AD does not state penalties, nor procedural details for reporting completion or for requesting alternative means of compliance. Operators should not assume absence of consequences and should document compliance carefully and engage with CASA for any approval of alternatives.

11. Technical detail about TU 232 remedies (Background)

    • The AD summarises TU 232 as adding a damping ring below the teeth and shot peening of the teeth roots. Maintenance organisations must ensure that the pinion they fit includes both elements, as the AD’s safety rationale is premised on both measures reducing vibratory stresses and fatigue risk.

12. Parts procurement and supply chain timing

    • The AD's text implies demand for modified pinions. Operators should plan for parts lead times and consider supply chain disruptions; the AD gives a fixed deadline, not a rolling compliance mechanism.

13. Record keeping and audit readiness

    • The AD does not set out reporting procedures. Operators should nonetheless maintain contemporaneous records (service bulletin used, part numbers, serial numbers, date of installation, maintenance release) to demonstrate compliance in the event of regulatory inquiry.

Each of these items arises directly from specific language in the AD and may generate operational risk or compliance friction if not proactively managed. The AD’s narrow technical scope and reliance on OEM documentation mean that attention to part numbers, service bulletin versions, dates, and documentary proof of accomplishment are the levers for avoiding non‑compliance exposure.

The AD provides a concise, prescriptive path to compliance. The steps below are drawn from the AD’s text and from direct operational logic implicit in the requirement to replace the named pinion in accordance with the named service bulletin by the stated deadline. The AD itself prescribes the what, how and when; the following elaborates the practical sequence that an operator or maintenance organisation should follow to meet the AD.

1. Identify affected engines and airframes

   • Confirm whether any engines in your fleet are Turboméca Arriel 1B, 1D or 1D1 models, "all serial numbers" (Applicability). Do not rely solely on airframe type; verify the engine model and serial number on the engine data plate and maintenance records. The AD warns that these engines are known to be installed on, but not limited to, Eurocopter AS 350 B, AS 350 BA, AS 350 B1 and AS 350 B2 helicopters (Applicability, Note 1), so operators of other airframes must also check.

2. Review maintenance records for prior accomplishment

   • Check whether the TU 232 modification or an equivalent pinion replacement has already been completed. The compliance clause states the replacement must be done "No later than 28 February 2011, unless previously accomplished" (Compliance). If the modification has already been performed, retain documentary evidence demonstrating that the prior work incorporated TU 232 (damping ring and shot peening) and that it was carried out in a manner that aligns with Turboméca service instructions.

3. Obtain the prescribed service bulletin

   • Acquire Turboméca Mandatory Service Bulletin 292 72 0276 Version B dated 6 November 2008, or a later approved revision, which the AD prescribes as the method of compliance (Requirement; Note 2). Ensure you obtain the full, official version B or a later edition that has been formally approved. Do not rely on draft or informal guidance.

4. Confirm part numbers and configuration

   • The AD identifies the pinion to be replaced as P/N 0 292 70 779 0 and requires replacement with pinions incorporating TU 232 (Requirement). When procuring parts, verify that the replacement pinion explicitly incorporates TU 232 features (damping ring below the teeth and shot peening of teeth roots) and that the supplier provides traceable documentation confirming the TU 232 modification.

5. Plan maintenance scheduling and procure parts

   • Schedule the replacement within the available compliance window, ensuring parts are ordered in time to meet maintenance slots and avoid exceeding the compliance deadline of 28 February 2011 (Compliance). Account for lead times, logistics and potential need to ground the aircraft or engine for the replacement.

6. Execute the replacement per the service bulletin

   • Have certificated maintenance personnel or an approved maintenance organisation perform the replacement strictly in accordance with the Turboméca Mandatory Service Bulletin 292 72 0276 Version B or later approved revision (Requirement). Follow every procedural step, use the specified tools and techniques, and apply the service bulletin’s acceptance criteria.

7. Document completion comprehensively

   • Record the work performed, including engine serial numbers, the removed pinion P/N, the replacement pinion P/N and serial (if applicable), reference to the exact service bulletin revision used (including revision date), the date of the work, the identity and certificate details of the personnel or organisation that performed it, and any necessary test or run‑in data. Retain invoices, parts certificates and any OEM statements confirming TU 232 incorporation.

8. Retain documentary evidence for regulatory inspection

   • Although the AD does not prescribe a reporting form, keep records readily available to demonstrate the AD was complied with by the 28 February 2011 deadline or that the work had been previously accomplished. The AD’s compliance clause creates the obligation; documentation is the practical means of proving fulfilment.

9. Clarify "later approved revision" status if using a different bulletin revision

   • If relying on a later revision of the Turboméca service bulletin, obtain evidence of approval for that revision and ensure the approval covers the replacement as an acceptable method of compliance under the AD (Requirement; Note 2). Seek confirmation from CASA or via the OEM channels as needed.

10. Coordinate with CASA or regulatory desk as required

    • The AD is a CASA instrument signed by a CASA delegate (signature block). If there is any uncertainty,about whether a previously performed modification qualifies as satisfying the AD, about the approval status of a later service bulletin revision, or about documentation formats,seek guidance from CASA to avoid disputes.

11. Consider supply and contractual implications

    • Engage procurement and maintenance contracting teams early. The AD’s reliance on OEM parts and instructions means commercial arrangements with Turboméca or authorised parts suppliers may be necessary. Include AD compliance timelines in contract and maintenance planning.

12. Monitor for related directives

    • The AD references EASA AD 2009‑0002 (Note 2). If operating internationally or under multiple authorities, review related ADs to ensure consistent compliance and documentation across jurisdictions.

Executing these steps will align practical maintenance and administrative actions with the AD’s text: replace the named pinion with one incorporating TU 232, follow the named service bulletin Version B or later approved revision, and complete the work no later than 28 February 2011 unless the modification had already been performed. Maintain robust documentation to demonstrate compliance evidence in case of regulatory inquiry.