AD/ARRIEL/32 Amdt 2 - Engine - Module M04 Power Turbine Blades

Module M04 (Power Turbine) is the separable section of the Arriel turboshaft engine that contains the power turbine blades. It is a line-replaceable module, meaning it can be removed and replaced as a unit rather than requiring a full engine overhaul. The AD applies only to modules whose serial numbers are listed in Figure 1 of the respective Turbomeca MSBs. The AD notes that serial numbers of PT wheel assemblies and modules are the "confirmed location of affected PT blades", with engine serial numbers provided for information only. If conflicts arise between serial numbers, the operator must contact Turbomeca directly for resolution. This places a burden on operators to maintain accurate traceability of modules and to verify against the MSB lists.

Total PT Cycle is the measure of usage that triggers the life limit. A PT cycle is not defined in the AD itself, but in turbine engine practice it typically corresponds to a full start, run, and shutdown of the power turbine, or a flight cycle on the helicopter. The limit of 5,000 total PT cycles is a life limit rather than an on-condition inspection. This means the blades must be removed regardless of their apparent condition at that point.

Geometric non-conformities on blade fir-tree roots refers to manufacturing defects in the shape or dimensions of the dovetail-shaped root that attaches each turbine blade to the disk. The fir-tree design distributes centrifugal load through multiple serrations. If the geometry is off-specification, the stress distribution changes, potentially reducing fatigue life. The background notes that this could lower fatigue resistance "to a lower level than their authorized in service use limit", implying that the normal design life assumed a certain geometric tolerance that these blades do not meet. The AD is effectively a corrective action to impose a shortened life limit until the blades are replaced.

Blade release is the catastrophic failure mode where a turbine blade detaches from the disk during operation. In a gas turbine, blade release typically causes severe imbalance, leading to immediate engine damage, often a hull loss of the engine. The AD notes the consequence is "an uncommanded in-flight shut-down" and, on a single-engine helicopter, "an emergency autorotation landing". This is a survivable but high-risk event, requiring pilot skill and luck.

Mandatory Service Bulletin (MSB) is a manufacturer's document that, when mandated by an AD, becomes a legally binding instruction. Here, Turbomeca issued MSBs A292 72 0827 (Arriel 1) and A292 72 2833 (Arriel 2) in multiple versions (original, B, C). The AD references version C but allows later approved revisions. Operators must check which version is current. The MSB likely contains the list of affected serial numbers, detailed removal and installation procedures, and possibly instructions for updating log cards.

EASA AD 2009-0112R1 is the European Aviation Safety Agency's equivalent directive. The CASA AD supersedes it for Australian operations, but the reference indicates coordination with European regulators. Because Turbomeca is a French manufacturer, the original defect discovery and MSB likely arose through EASA's system. CASA adopted the EASA AD with amendments. Operators with international fleets need to reconcile multiple ADs.

Autorotation landing is the emergency manoeuvre used in single-engine helicopters when engine power is lost: the rotor system freewheels and the pilot uses the kinetic energy of the blades to slow the descent and land. It is a required skill but not always successful, especially at low altitude or in adverse conditions. The AD's background makes clear that the defect could trigger exactly this emergency.

The AD also introduces a temporal sequence: Requirement 2a (log card update) must be done before Requirement 2b (replacement). This ensures that the life limit is documented in the maintenance records even if replacement is not yet due. Failure to update the log card before replacement could complicate future traceability and compliance verification.

The AD directly imposes obligations on several categories of persons and organisations.

First, operators of Australian-registered helicopters powered by Turbomeca Arriel 1B, 1D, 1D1, 2B, 2B1, or 2B1A engines, where the engine's Module M04 falls within the serial number ranges listed in the referenced MSBs. The applicability note states these engines are known to be installed on Eurocopter AS350 B, BA, BB, B1, B2, B3, EC130 B4, and Changhe Z11 helicopters. However, the AD is not limited to those airframes; it applies wherever the engine is installed. Operators of other helicopter types with these engines must still comply.

Second, maintenance organisations (Part 145 or equivalent) that perform work on these engines or modules. They must have access to the MSB, follow its procedures, and properly document the replacement and log card updates. Their certifications are required for the AD's completion.

Third, owners and lessors of the aircraft. Even if operations are contracted out, the owner remains ultimately responsible for airworthiness. A failure to comply could ground the aircraft and affect its value and insurability.

Fourth, Turbomeca S.A. and its Australian representatives are indirectly affected. The AD relies on their MSB for technical instructions. Turbomeca must support operators with parts availability, technical support, and serial number resolution. The note that "in case of conflicts between serial numbers Turboméca should be contacted for resolution" imposes a duty on the manufacturer to provide timely responses, though there is no legal penalty on Turbomeca under this AD.

Fifth, regulatory staff at CASA who must administer compliance, issue exemptions if necessary, and enforce the AD.

The cost burden falls disproportionately on operators with high-utilisation engines already near or above 5,000 cycles at the effective date. For such operators, the AD creates an immediate grounding risk. The economic impact includes not only replacement parts and labour but also revenue loss from aircraft downtime. Helicopters used in commercial passenger transport, emergency medical services, or aerial work (mustering, surveying) could face significant operational disruption. The AD does not provide any transition period for engines above 5,000 cycles; it mandates replacement "before further flight". This is typical of safety-critical airworthiness directives but imposes a sharp immediate cost.

For operators with modules well below 5,000 cycles, the cost is deferred but not eliminated. They must still perform the log card update (a modest administrative cost) and plan for eventual replacement. The 5,000-cycle limit may be significantly shorter than the expected life of the module absent the AD, so the AD reduces the useful life of the affected blades, increasing the per-cycle cost of operation.

The AD does not affect operators of Arriel 1E, 2C, 2S, or other Arriel variants not listed, nor does it affect modules that are not identified in the MSB figures. However, operators should verify that their modules are not included; the AD does not require action if the module serial number is not listed. This puts the burden of checking on the operator.

The AD creates specific duties but also certain rights and flexibilities.

Duty to verify applicability. Every operator of an affected engine type must determine whether their Module M04 serial number appears in Figure 1 of the relevant MSB. This is not explicitly stated as a requirement, but it is a necessary predicate to compliance. The AD assumes operators will conduct this audit.

Duty to replace or retire before further flight applies to any module that has already accumulated 5,000 or more total PT cycles at the effective date (14 August 2009). This is an absolute duty with no grace period. The replacement must follow the procedures in MSB version C or later approved revisions. The operator cannot choose to continue flying with a placard or reduced power; replacement is the only option.

Duty to update log cards (Requirement 2a) applies to modules with fewer than 5,000 cycles. The operator must "update the module M04 log card and the engine log book to enter the 5,000 PT Cycle life-limit of the PT blades" as instructed in the MSB. This is a documentation requirement that must be accomplished before the replacement of Requirement 2b. In practice, this means the operator must record the life limit even if replacement is not due for years. This duty creates a permanent record that will be checked during future audits or at time of sale.

Duty to replace before exceeding 5,000 cycles (Requirement 2b) applies to all modules below 5,000 cycles at the effective date. The operator must ensure the module is replaced before it reaches 5,000 total PT cycles. This is a forward-looking duty that requires ongoing cycle tracking. If a module is at 4,500 cycles at the effective date, replacement is due within 500 cycles. The AD does not specify a minimum remaining cycles threshold for initiating replacement; the operator must plan accordingly.

Right to use later approved revisions of the MSB. The AD states that "the use of later approved revisions of these documents is acceptable for compliance". This gives operators flexibility if Turbomeca issues version D or later. However, the operator must ensure the revision is "approved", which likely means approved by EASA, CASA, or the manufacturer under its design organisation approval. If a later revision introduces different procedures or changes the list of affected serial numbers, the operator may rely on it. This right reduces the risk that the AD becomes obsolete if the MSB is updated.

Right to contact Turbomeca for serial number resolution. If there is a conflict or ambiguity in serial number traceability, the operator should contact Turbomeca. This is a procedural right, but it is not a guarantee of a timely response. Operators may face delays if they have missing records.

Right to choose replacement method. The AD allows replacement of "the module M04, or PT wheel assembly, or PT blades". These are three different levels of repair: replacing the entire module (most expensive but simplest), replacing only the PT wheel assembly (moderate cost), or replacing only the PT blades (most labour-intensive but possibly lowest parts cost). The operator can choose based on availability, cost, and capability. However, the MSB procedures may prescribe certain methods; the operator must follow them.

No right to defer for economic reasons. The AD is absolute; there is no provision for extensions based on cost or part availability. Operators of engines above 5,000 cycles must ground the aircraft immediately even if replacement parts are on backorder. This can lead to pressure on the supply chain and disputes with lessors or customers.

Interaction with maintenance release. After completing the AD, the aircraft must have a maintenance release (Certificate of Release to Service) before return to service. The AD does not require a separate release, but the maintenance organisation performing the work must certify compliance.

The AD does not itself specify penalty figures, but it is issued under the Civil Aviation Act 1988 and the Civil Aviation Safety Regulations 1998. Breach of an airworthiness directive is a serious violation. The primary enforcement mechanisms are regulatory action by CASA and potential criminal prosecution.

Under regulation 39 of the Civil Aviation Safety Regulations (CASR) Part 39, airworthiness directives are mandatory. Failure to comply with an AD renders the aircraft unairworthy. Operating an aircraft that does not conform to its approved design or applicable ADs is an offence under section 20A of the Civil Aviation Act, carrying penalties of up to 200 penalty units for an individual (currently $44,000 per offence as of July 2024, but the penalty unit amount in 2009 was lower, approximately $110 per unit, so about $22,000 at the time) and higher for corporations (up to 1,000 penalty units, about $110,000). Each flight constitutes a separate offence. Willful or reckless non-compliance could lead to more severe penalties, including imprisonment under section 22 for endangering the safety of an aircraft.

CASA can also take administrative action: issuing a direction to ground the aircraft, suspending or cancelling an Air Operator's Certificate or maintenance organisation approval, or imposing conditions on operations. For repeat or flagrant violations, CASA may seek civil penalties or injunctions.

Enforcement depends on detection. Operators are required to maintain accurate records of AD compliance. During a routine maintenance audit, airworthiness review, or incident investigation, CASA inspectors will check for compliance with applicable ADs. If an operator is discovered to have falsified log card entries or continued flying beyond the cycle limit, that could lead to prosecution for fraud as well as safety offences.

The AD does not provide for self-reporting amnesty. An operator who discovers they have already exceeded 5,000 cycles without replacement must ground the aircraft and report the non-compliance to CASA. This may trigger an investigation.

The practical risk for operators is that non-compliance with a safety-critical AD on a single-engine helicopter type could be directly linked to a fatal accident. In that event, enforcement would be the least of the consequences; criminal negligence charges and civil liability from victims' families are possible.

For maintenance organisations, incorrectly certifying compliance with this AD (e.g., performing the log card update but not the replacement) could lead to loss of their maintenance certificate and personal liability for licensed engineers.

Because the AD was issued in 2009, most affected modules have by now either been replaced or the aircraft retired. However, the AD remains in force for any aircraft still operating with these modules that have been overhauled or had replacement blades installed after the AD. The penalty framework continues to apply.

This AD interacts with several layers of Australian and international aviation law.

Civil Aviation Act 1988 and Civil Aviation Safety Regulations 1998 (CASR). The AD is issued under Part 39 of CASR, which governs airworthiness directives. Part 39 ADs are binding on all Australian aircraft operators and maintenance organisations. They override any less restrictive operating limitations. If a manufacturer's maintenance manual does not specify a life limit for these blades, the AD imposes one. Operators must incorporate the AD into their continuing airworthiness management system.

EASA AD 2009-0112R1. The CASA AD explicitly notes that it supersedes the EASA AD of the same number. For Australian operators, the CASA AD is the governing instrument. However, if an aircraft is operated internationally or imported from Europe, the operator must ensure that the Australian AD is applied, which may differ from the European version. The CASA AD has a later effective date (14 August 2009) and a higher cycle limit (5,000) than the earlier EASA versions. An operator who complied with the EASA AD's earlier 1,000-cycle limit would have already replaced blades; those who waited for the later limits may have avoided unnecessary replacement. The interaction shows that operators must track both Australian and foreign ADs if they fly internationally or use foreign-maintained modules.

Maintenance regulations (CASR Part 145 and Part 66). The actual replacement work required by the AD must be carried out by an appropriately authorised maintenance organisation under Part 145, with licensed engineers (Part 66) certifying the work. The AD does not grant any exemption from normal maintenance requirements; it imposes an additional task that must be incorporated into the scheduled maintenance plan. The log card update is a form of maintenance data amendment, which must be done in accordance with the manufacturer's instructions.

Aircraft registration and airworthiness certificates. An aircraft that does not comply with all applicable ADs is not eligible for a Certificate of Airworthiness or a Special Flight Permit (except for the purpose of flying to a location for compliance). Operators must ensure that AD compliance is recorded in the aircraft's continuing airworthiness records.

Part 42 (Continuing Airworthiness) regulations. Operators must have a system to track ADs, including due dates and compliance status. This AD imposes a cycle-based requirement, so the operator must track engine cycles, not just calendar time.

Foreign regulations. If an Australian-registered helicopter operates in another country's airspace, it must comply with that country's ADs as well. However, the home-state AD (CASA) is primary. Some countries may require compliance with their own version. The EASA AD reference means that European operators would use EASA's directive, but this AD is for Australian operators.

Insurance implications. Non-compliance with an AD may void hull and liability insurance. Insurers typically require airworthiness compliance as a condition of coverage. An accident involving an aircraft that was operating in breach of an AD could result in denial of coverage, leaving the operator or owner personally liable for damages.

Lessor and lease agreements. Aircraft held under lease often contain covenants requiring compliance with all airworthiness directives. This AD must be complied with at the lessee's cost, unless otherwise agreed. A lessor may demand proof of compliance.

No interaction with privacy or consumer law is apparent from the source.

The key practical interaction is that this AD sits within a hierarchy: the AD is specific and mandatory; the manufacturer's instructions are the method; the general regulations are the enforcement framework. An operator cannot rely on a general maintenance manual that does not address the defect; the AD overrides.

The source provides a clear amendment history within the AD text itself. The original issue of AD/ARRIEL/32 became effective on 27 March 2009. This first issue required a restriction of the cyclic use limit of PT blades to 1,000 flight cycles. For blades having reached 1,000 or more cycles, removal was required before further flight. This was a highly restrictive limit, likely causing significant operational disruption and costs for operators of high-utilisation helicopters.

Amendment 1, effective 1 June 2009, revised the reference documents from version A to version B of the MSBs. Version B included additional modules that were affected, expanding the population of engines subject to the AD. However, the amendment also increased the cyclic limit from 1,000 to 2,000 cycles, based on additional testing. This was a partial relaxation that reduced the immediate compliance burden for some operators but extended the applicability to more modules. The trade-off for operators was that more engines needed action, but those with moderate cycles got more time.

Amendment 2, effective 14 August 2009, is the current version. It further revised the reference documents to version C of the MSBs. Version C incorporated even more testing data, which allowed increasing the cyclic limit to 5,000 cycles. This was a substantial relaxation from the original 1,000-cycle limit. Amendment 2 supersedes EASA AD 2009-0112R1 (the European version effective 30 July 2009). The CASA AD thus became aligned with the latest EASA version but went further by adopting the 5,000-cycle limit at the same time or shortly after.

The progressive increase in the cycle limit reflects an iterative process of testing and risk assessment. The supplier Turbomeca had detected geometric non-conformities but initially had limited data on the actual effect on fatigue life. Conservative initial limits are standard in aviation safety; they protect against unknown worst-case scenarios but impose costs. As testing generated more data, authorities relaxed the limits. Operators who complied early (under the 1,000- or 2,000- cycle limits) may have incurred costs that are now arguably unnecessary in hindsight. Those who waited for later amendments saved money but took a risk that the AD might not be relaxed. This is a classic regulatory timing risk.

The AD also notes that Amendment 1 had already increased the limit from 1,000 to 2,000 cycles, and Amendment 2 to 5,000. There is no indication of any further amendments or supersedures. The AD appears to be final, though the possibility of a later revision to higher limits or new issues cannot be ruled out based on this text.

The effective date of Amendment 2 is 14 August 2009, and it is signed by James Coyne, Delegate of CASA, on 12 August 2009.

For current research, the key point is that this AD is now 15 years old. Most modules that existed in 2009 have likely been replaced or the aircraft retired. However, if a module was overhauled and rebuilt with new blades after the AD, the 5,000-cycle limit would apply to the new blades from their first installation. Any such rebuilt module would need to have its log card updated with the life limit, and its cycle count reset. The AD does not specify if the 5,000-cycle limit applies to replacement blades; logically, replacement blades would be non-conforming only if they are from the same production batch. However, the AD applies to "modules M04 as identified in figure 1 of the MSB". If Turbomeca issued a later MSB that includes additional affected serial numbers, that could expand the scope again. Operators must always check the latest version of the MSB.

The source text contains no reference to any litigation, court cases, or tribunal proceedings related to this AD. No cases are mentioned, and no judicial review or appeal is referenced. Given the nature of airworthiness directives, litigation is rare for several reasons.

First, ADs are mandatory regulatory instruments. They are routinely issued by CASA under delegated authority from the Minister. Judicial review is possible but unlikely to succeed unless the AD is ultra vires or procedurally defective. The grounds for challenging an AD would be narrow: the authority must have acted within its powers, considered relevant matters, and not been irrational. Because ADs are based on safety assessments by the manufacturer and foreign regulators, courts typically defer to the technical expertise of the regulator. There is no public record of a successful challenge to a CASA airworthiness directive.

Second, the cost of litigation would likely exceed the cost of compliance for most operators. An operator who disputes the AD would first seek an exemption or alternative means of compliance through CASA, not a court. The AD's own text allows use of later MSB revisions, which already provides some flexibility.

Third, tort litigation could arise if a blade release occurred and caused damage. Plaintiffs might argue that the AD was insufficiently protective, or that Turbomeca knew of the defect earlier. However, the AD itself would not be the subject of a lawsuit; rather, the manufacturer's design or the operator's compliance would be at issue. The AD would be evidence of the standard of care, but not a source of liability.

Fourth, there could be contract disputes between lessors and lessees or between operators and maintenance providers regarding who bears the cost of compliance. These would be litigated under contract law, not administrative law. The AD's history of increasing the cycle limit could give rise to claims that operators who replaced blades under the original 1,000-cycle limit suffered economic loss that could have been avoided if they had delayed. However, doing so would have risked operating with a known defect. A court would likely find that compliance with the AD as it stood at the time was reasonable.

Fifth, the AD is from 2009, and any litigation would likely have been concluded by now. A search of Australian legal databases for "AD/ARRIEL/32" or "CASA Turbomeca Arriel" would show if any cases exist, but the source provided does not include them. As the instruction requires me to only name cases the source names, I cannot speculate about unreported cases.

Overall, the litigation history is either absent or minimal. The directive is straightforward, technical, and safety-critical, making it an unlikely candidate for dispute. The only potential ground for legal action would be if CASA made an error in the serial number identification or the scope of the AD, but that would likely be resolved through administrative channels. For the purposes of this deep dive, there is no known litigation.

Several aspects of this AD can trip up operators, maintainers, or those conducting due diligence on an aircraft.

First, the compliance timing is deceptive. Requirement 1 applies to engines with "5,000 Total Power Turbine Cycles or more at the effective date of this AD". The effective date is 14 August 2009. If an operator misreads this as "5,000 cycles from now" or assumes a grace period, they may inadvertently operate an engine that must be grounded. The AD does not define "effective date" clearly in the body, but the compliance section states "Before further flight after the effective date of the AD". That means immediately upon the AD becoming effective, any engine at or over 5,000 cycles must not be flown again until the module is replaced. An operator who flies one leg after the effective date before checking cycles would be in breach. This is a common trap in ADs.

Second, the note about serial numbers: "In case of conflicts between serial numbers Turboméca should be contacted for resolution." This is not a free pass. If an operator cannot determine whether their module is affected because records are missing or ambiguous, they cannot simply assume it is not affected. The AD places the burden on the operator to resolve the conflict. Contacting Turbomeca may take time, during which the aircraft should be considered potentially non-compliant. An operator who continues operating without resolution is taking a risk.

Third, the requirement to update log cards (2a) must be done before the replacement (2b). Operators might think they can replace the module first and then update records, but the AD explicitly says otherwise. If an inspector audits compliance, they will look for evidence of the log card entry before the replacement date. Doing it in reverse order technically constitutes non-compliance with the AD, even if the end result is the same.

Fourth, the use of "later approved revisions" is a trap for the unwary. It allows operators to use MSB version D or later, but only if that revision is "approved". The operator must verify that the later revision has been approved by CASA, EASA, or the design organisation. Using an unapproved revision could void compliance. Also, a later revision might add more modules to the affected list. An operator who used version C and missed version D might later discover that their module is actually affected by a broader list.

Fifth, the AD applies only to modules "as identified in figure 1 of the referenced MSB". The figure is not included in the AD text. Operators must obtain the full MSB from Turbomeca or an authorised distributor. Relying on the AD text alone is insufficient. The AD requires referencing the MSB, which is a separate document. Failure to obtain and follow the MSB is non-compliance.

Sixth, the AD says "For engines with a Module M04 which has accumulated less than 5,000 Total PT Cycles at the effective date of this AD", the operator must do requirements 2a and 2b. But what if the engine reaches 5,000 cycles on the effective date itself? There could be ambiguity about coincidence. Strictly, "at the effective date" means on that date. If the module is exactly at 5,000 cycles, it falls into requirement 1 (immediate grounding). An operator must be precise.

Seventh, record-keeping: The log card update must include the 5,000-cycle life limit. If the operator later replaces the module with a new or different module, the log card for the new module must also reflect the AD if that module is affected. The AD does not specify how to handle that, but good practice is to document the new module's compliance status.

Eighth, the AD does not address what happens if an engine has been overhauled since the AD's effective date and the PT blades were replaced with non-affected blades. In that case, the module would no longer be the one identified in the MSB, and the AD would no longer apply to that module. However, the operator must have proof of the replacement and the part numbers of the new blades. If the new blades are from the same suspect batch or if records are lost, the AD may still be considered applicable.

Ninth, the AD is written assuming the engine is installed on a single-engine helicopter. But if the engine is used in a twin-engine application (unlikely for these models but possible in some experimental installations), the safety case is different. The AD does not differentiate; it applies to the engine regardless of installation.

Tenth, the AD supersedes an EASA AD. An operator who holds an Australian-registered aircraft but uses EASA-compliant maintenance (e.g., a foreign Part 145 organisation) must ensure that the CASA AD is followed, not the EASA one. The supersession might be overlooked.

A step-by-step guide for an operator receiving this AD in 2009 or retroactively for current record review:

1. Obtain the correct MSB. Request from Turbomeca or their distributor a copy of MSB A292 72 0827 version C (Arriel 1) or A292 72 2833 version C (Arriel 2), or any later approved revision. Ensure the version is indeed approved. If in doubt, contact CASA or the manufacturer.

2. Identify affected engines. Compile a list of all engines by serial number and the serial numbers of their attached Module M04. Compare these against the list in Figure 1 of the MSB. Note that the AD says engine serial numbers are provided for information when available, but the module serial numbers are the confirmed location. The search should prioritise module serial numbers.

3. Determine total PT cycles for each affected module. Use engine log books, maintenance records, and cycle counters. For modules with missing cycle history, conservative assumptions may be needed (e.g., assume the highest plausible cycle count based on aircraft utilisation). Contact Turbomeca if records are incomplete.

4. Classify each module into one of two buckets:

   • Bucket A: Modules with 5,000 or more total PT cycles at the effective date (14 August 2009).
   • Bucket B: Modules with fewer than 5,000 cycles.

5. For Bucket A modules: Immediately ground the aircraft. Do not start the engine until the module is replaced. Arrange for replacement of either the entire Module M04, or the PT wheel assembly, or the PT blades, following the instructions in the MSB. Complete the replacement. Once replaced, ensure the maintenance records reflect compliance. The aircraft may return to service only after a Certificate of Release to Service.

6. For Bucket B modules: First, update the Module M04 log card and the engine log book to record the 5,000-cycle life limit. This entry should be dated before any replacement. Enter the cycle limit and reference the AD number. Second, continue to track cycles. Plan for replacement before the module reaches 5,000 total PT cycles. Replacement can be done at any convenient maintenance opportunity, but must be completed before the cycle limit is exceeded. Use the same replacement options as in step 5.

7. Document everything. Create an AD compliance matrix listing engine serial number, module serial number, cycles at effective date, date of log card update, date of replacement, and part numbers of new components. Keep this in the aircraft continuing airworthiness records.

8. Verify MSB revision currency. The AD allows later approved revisions. Periodically check if Turbomeca has issued any later revision to the MSB. If a later revision adds more modules to the affected list, those additional modules must be brought into compliance. If a later revision increases the cycle limit further, operators may have additional time but should ensure they have the revised limit documented.

9. Train maintenance personnel. Ensure engineers and record keepers understand the distinction between requirement 1 and 2, and the order of log card update before replacement. Misordering is a common error.

10. Audit. Include a check of AD/ARRIEL/32 Amdt 2 in any airworthiness review or pre-purchase inspection. For a used engine, verify that the AD has been complied with by reviewing log book entries and part number traceability.

11. Contact Turbomeca for serial number conflicts. If any engine or module serial number is missing, illegible, or ambiguous, contact Turbomeca promptly. Do not operate without resolution.

12. Plan for supply chain. Replacement parts may have long lead times. For Bucket A engines, the aircraft is grounded until parts arrive. Consider requesting ship-ahead or pooling. For Bucket B, ensure parts are ordered well before the cycle limit.

13. Review insurance and lease obligations. Notify lessors or insurers of the AD status. Ensure compliance is documented to avoid coverage disputes.

14. Record in CASA's AD management system (if applicable). Operators should log compliance in whatever system they use to track ADs, such as a computerised maintenance management system.

15. Retain records permanently. Even after replacement, keep records of compliance for the life of the engine or aircraft. Future owners or regulators may request evidence.

The key is not to underestimate the immediate grounding risk for high-cycle modules. An operator who fails to check cycles on the effective date could inadvertently operate illegally. The log card update requirement is easy to overlook but is a specific requirement. And the use of later MSB revisions is a benefit only if the operator proactively checks for them.

Given the AD is now 15 years old, current compliance is likely a matter of ensuring that any replacement modules (installed after the AD's effective date) are themselves not affected by the AD. New modules from Turbomeca after 2009 should have corrected the geometric non-conformities, but an operator must verify the part numbers and have documentation. If a module was rebuilt using legacy blades, the AD could remain applicable. Therefore, continuing airworthiness managers should include this AD in their legacy AD review.