AD/ARRIUS/12 - Check-Valve Piston O-Ring

The AD centres on a single technical component: the check‑valve piston o‑ring located inside the lubrication unit check valve of Turbomeca ARRIUS 2 series turboshaft engines. The o‑ring can undergo “excessive swelling” that may produce oil passage blockage within the check valve, interrupting lubrication flow to the engine (Background). The potential operational hazard identified is interruption of lubrication and the related risk that both engines on a twin‑engine rotorcraft could suffer simultaneous shutdown, described in the Directive as a possible “double uncommanded in‑flight shutdown” (Background).

Two oil classifications are material to the AD’s mechanics: STD class oil and HTS class oil. The Directive states that the amount of o‑ring swelling is dependent upon which class of oil is, or was, used, together with engine operating time (Background). The compliance timings change according to whether the engine operates with HTS‑class oil, has an unknown oil history, has previously operated with HTS oil but no longer does, or has operated exclusively with STD‑class oil since introduction into service (Compliance). The Directive treats unknown or HTS histories conservatively, applying the shorter interval associated with HTS exposure (Compliance).

The technical remedy is replacement of the o‑ring following a specific procedure, namely paragraph 2 of the relevant Alert Service Bulletin (ASB No. A319 79 2832 for 2B1/2B1A/2B2 engines, or ASB No. A319 79 2833 for 2K1/2K2 engines). The AD explicitly allows later DGAC‑approved revisions of those ASBs to be used (Requirement). The Directive also requires a recurring action: after the initial replacement has been carried out, operators must repeat the replacement at the specified engine operating‑hour intervals (Requirement, Compliance).

The Directive identifies the population of affected engines and the typical rotorcraft applications, but it uses inclusive language. Applicability lists models ARRIUS 2B1/2B1A, 2B2, 2K1 and 2K2, and notes that these engines are fitted, but not limited to, Eurocopter EC135 TI and T2, and Agusta A109 Power and A109 LUH rotorcraft (Applicability). That phrasing signals that other installations of the same engines, beyond the models listed, fall within the AD’s scope.

Finally, the AD points to related regulatory artefacts. It refers to DGAC AD F‑2005‑159 and an EASA approval number (2005‑6223), which the Directive indicates as related approvals or references (Requirement, Background). The Directive itself is dated and signed by a CASA delegate on 6 October 2005 and states the effective date as 24 November 2005 (Background, Compliance).

Primary economic actors directly affected are operators and owners of aircraft that use the listed Turbomeca ARRIUS engine models 2B1, 2B1A, 2B2, 2K1 and 2K2. The AD explicitly notes that these engines are installed, but not limited to, Eurocopter EC135 TI and T2, and Agusta A109 Power and A109 LUH rotorcraft, which means the named helicopter operators are directly implicated where those engine types are installed (Applicability). The “not limited to” phrasing extends the AD’s reach to operators of other airframes fitted with these engines.

Maintenance organisations that perform engine maintenance for affected engines bear responsibility to execute the replacement task in accordance with the referenced ASB paragraph 2 and any later DGAC‑approved revision (Requirement). Parts suppliers and logistics chains that provide the correct o‑ring parts and the tooling or consumables necessary for the replacement will experience demand as operators schedule initial and recurring replacements.

Regulatory actors are implicated in an administrative and approval role. The AD itself is issued by a delegate of the Civil Aviation Safety Authority, and it explicitly accepts ASB revisions that carry DGAC approval. The instrument also references DGAC AD F‑2005‑159 and EASA approval No. 2005‑6223, which ties it into international certification and approval processes between French and European regulators (Requirement, Background).

Financially, operators pay for parts, labour and any downtime required to perform the replacement and the recurring work. The Directive assigns the physical action of replacement to those responsible for maintenance, which in practice will be either the operator’s own maintenance organisation or contracted repair stations. The AD does not specify cost recovery, funding mechanisms, subsidies, or parts provision; therefore operators are the residual payers for compliance costs implied by the mandated replacement and re‑replacement schedule.

Operational effects fall on flight scheduling and maintenance planning: engines must be taken into maintenance at particular operating‑hour thresholds (Compliance). Aircraft with engines exceeding the thresholds at the effective date have a short compliance window for initial replacement (50 operating hours from the effective date for engines exceeding defined hour limits), which will affect near‑term maintenance workloads (Compliance).

Finally, the AD affects safety management and risk registers for operators using the listed engines, as it addresses a known failure mode that could cause an in‑flight double shutdown. That safety risk is identified in the Directive as arising from o‑ring swelling and potential oil passage blockage (Background).

Duties

• Replace the check‑valve piston o‑ring in accordance with paragraph 2 of the applicable Turbomeca Alert Service Bulletin: ASB No. A319 79 2832 (ARRIUS 2B1/2B1A/2B2) dated 21 June 2005, or ASB No. A319 79 2833 (ARRIUS 2K1/2K2), or later DGAC‑approved revisions. The Directive’s Requirement section states this as the operative action (Requirement).
• Perform an initial replacement within the specified windows for engines that exceeded certain operating hours as at the Directive’s effective date, unless replacement was already performed prior to the AD’s issue. Specifically, unless previously accomplished, an initial replacement must be accomplished within 50 operating hours from the effective date for engines that exceed:
  • 300 operating hours at the effective date for engines operating with HTS‑class oil, for engines with no available oil history, or for engines which used to operate with HTS‑class oil and which no longer do; or
  • 450 operating hours at the effective date for engines operating with STD‑class oil since their introduction into service (Compliance).
• Repeat the replacement at recurring intervals not to exceed:
  • 300 operating hours for engines operating with HTS‑class oil, engines with unknown oil history, or engines which used to operate with HTS oil and which no longer do; or
  • 500 operating hours for engines operating with STD‑class oil since introduction into service (Compliance).

Rights and permissible methods

• The AD authorises use of later revisions of the referenced ASBs provided those revisions carry DGAC approval; the Requirement explicitly allows the operator to rely on DGAC‑approved later revisions of ASB No. A319 79 2832 or ASB No. A319 79 2833 (Requirement).
• The Directive identifies the precise procedural source for the technical task , paragraph 2 of the relevant ASB , which means operators and maintenance organisations have a prescribed compliance procedure to follow rather than an open‑ended technical mandate (Requirement).

What the Directive does not state

• The AD text does not provide further rights such as reimbursement, parts provision, or alternative repair methods beyond the DGAC‑approved ASB revisions. It also does not prescribe record‑keeping formalities or reporting obligations in the excerpt provided, beyond the replacement and interval requirements (the text contains no such provisions).
• The AD text does not state who pays explicitly, but the obligation to perform the replacement falls on those responsible for maintenance of the affected engines, which in practice will be the operator or their contracted maintenance provider (Requirement, Compliance).

Decision points for operators and maintainers

• Determine engine applicability: verify the engine model against the Applicability list and confirm whether the engine is one of the ARRIUS 2 series models named (Applicability).
• Determine oil history and current oil classification: the compliance timing depends on whether the engine has operated with HTS oil, has an unknown oil history, used to operate with HTS oil but no longer does, or has operated with STD oil since new (Background, Compliance).
• Confirm operating hours at the Directive’s effective date and calculate the 50‑hour initial window if thresholds were exceeded (Compliance).
• Use the specified ASB paragraph 2 procedure or a later DGAC‑approved revision to perform each required replacement (Requirement).

The text of the AD/ARRIUS/12 provided does not specify penalty provisions, civil or criminal sanctions, or the exact enforcement mechanism for non‑compliance. The document sets out mandatory technical actions and timings: replacement of the check‑valve piston o‑ring according to paragraph 2 of the specified Alert Service Bulletins, and repeat replacement at prescribed operating‑hour intervals (Requirement, Compliance). It also states an effective date, 24 November 2005, and is signed by a delegate of the Civil Aviation Safety Authority (Background, Compliance). The AD language indicates a regulatory instruction, but it contains no express penalty schedule within the text supplied.

Because the AD is an Airworthiness Directive issued by a CASA delegate, it operates as a regulatory instrument within aviation safety oversight, and operators can reasonably expect that compliance will be monitored through normal regulatory surveillance, continuing airworthiness obligations, and maintenance audits. However, the Directive itself does not in the excerpt set out enforcement pathways, such as notices of non‑compliance, suspension of certificates, administrative fines, or prosecution provisions. The Directive also does not include an explicit compliance declaration or sign‑off form, nor does it state which authority is to be notified upon completion of the work.

The AD refers to DGAC AD F‑2005‑159 and EASA approval No. 2005‑6223, indicating that the measure is coordinated with other regulatory authorities (Requirement, Background). Any enforcement action tied to those instruments would be governed by those authorities’ frameworks, but the AD text does not set out how such cross‑jurisdictional enforcement would operate, nor does it impose enforcement mechanisms beyond the technical prescription.

In practice, for operators subject to Australian civil aviation oversight, failure to comply with an Airworthiness Directive is likely to be addressed through the regulator’s standard oversight tools. The AD text does not provide the explicit list of those tools, nor does it set fines or sanctions. Users of this Directive should therefore treat the AD as a mandatory maintenance requirement in planning and assure that their regulatory compliance and continuing airworthiness processes align with CASA expectations, but any enforcement consequences or penalty regimes must be verified against the regulator’s broader regulatory instruments and enforcement policies, which are not included within the AD text itself.

The AD identifies and cross‑references foreign regulatory material and approvals, which establishes connections to other regulatory instruments and approvals. The Requirement states that replacements must be carried out in accordance with the specified Turbomeca Alert Service Bulletins, or later DGAC‑approved revisions. The AD text also explicitly “refers” to DGAC AD F‑2005‑159 and cites an EASA approval number, EASA approval No. 2005‑6223 dated 6 September 2005 (Requirement, Background). Those references signal that the Directive aligns its technical solution with approvals and directives issued by the French DGAC and EASA, and that operators may rely on DGAC‑approved ASB revisions as acceptable compliance methods.

Within the text supplied, the Directive is issued by a delegate of the Civil Aviation Safety Authority, thereby situating it within Australian aviation regulatory administration (Background). The AD does not state the specific statutory provision under which CASA issued the Directive, nor does it quote any enabling Act or broader civil aviation regulation. Therefore, the AD’s legal force and enforcement mechanisms should be read together with the broader statutory and regulatory framework that governs CASA’s issuance of airworthiness directives, which is not reproduced in the AD text.

The AD’s reference to DGAC and EASA approvals creates a practical interaction: maintenance work done under a DGAC‑approved ASB revision is explicitly accepted by this AD as compliant. That means maintenance actions approved under those foreign authorities’ processes are incorporated as acceptable methods for satisfying the AD, and this reduces the need for parallel Australian‑only approvals for the specific ASB revisions (Requirement). The Directive does not, however, state whether alternative methods of compliance require CASA approval, nor does it provide a mechanism to submit or accept alternative repair methods within the AD text.

Because the AD does not specify record‑keeping or reporting requirements, interactions with other laws that require certain documentation, such as mandatory maintenance log entries, continuing airworthiness records, or civil aviation safety management obligations, are not detailed in the Directive text. Operators must therefore integrate the AD’s replacement and interval obligations into their broader regulatory record‑keeping and continuing airworthiness processes under the applicable Australian civil aviation regulatory regime, but the AD does not itself provide the schema for that integration.

Finally, the AD’s cross‑reference to DGAC and EASA may affect importation or parts conformity questions, insofar as replacement parts or ASB revisions approved by the DGAC are accepted. The AD does not address customs, trade, or supplier warranty issues, and it does not set standards for procurement beyond the ASB procedural reference.

In short, the AD connects with French and European regulatory approvals for the technical remedy, it is issued by an Australian regulator’s delegate, and it requires operators to perform parts replacement as set out in the referenced ASBs. The AD text does not include express statements about how it interacts with other specific Australian statutes or enforcement rules; those interactions must be inferred by placing the AD in the wider regulatory framework outside the text supplied.

The material supplied contains a single published text block for AD/ARRIUS/12 dated 12/2005 and indicates an effective date, 24 November 2005. The Directive as provided shows a signature block dated 6 October 2005 by “Jayaprakashan Ambali, Delegate of the Civil Aviation Safety Authority” (Background, Compliance). The Requirement section allows the use of later DGAC‑approved revisions of the referenced Alert Service Bulletins, but the AD text itself does not contain or list any subsequent amendments or revisions to AD/ARRIUS/12 within the supplied material (Requirement).

The AD explicitly states which ASBs to follow, and it permits later DGAC‑approved ASB revisions to be relied upon as compliant means of satisfying the Directive (Requirement). That provision effectively allows for technical amendments through approved ASB updates without the need to re‑issue the AD each time an ASB revision receives DGAC approval. However, the AD text does not list any specific ASB revisions beyond the dates given for the original ASBs (ASB No. A319 79 2832 dated 21 June 2005 for ARRIUS 2B1/2B1A/2B2) and does not provide a recorded chronology of further ASB revisions or AD amendments.

There is a cross‑reference to DGAC AD F‑2005‑159 and EASA approval No. 2005‑6223 dated 6 September 2005, which the AD “refers” to (Requirement, Background). The presence of those references indicates contemporaneous regulatory activity in other jurisdictions, but the AD text does not state whether those foreign instruments have been amended subsequently or whether such amendments automatically alter the AD’s requirements, other than the explicit acceptance of DGAC‑approved ASB revisions.

Therefore, based solely on the AD text presented, the amendment history is: original AD/ARRIUS/12 issued and signed on 6 October 2005, becoming effective on 24 November 2005, with a permissive provision for later DGAC‑approved ASB revisions. No further amendments or revision entries are recorded in the supplied document.

The supplied AD/ARRIUS/12 text includes no information about litigation, disputes, judicial review, administrative appeals, or enforcement actions related to the Directive. The document contains technical requirements, compliance schedules, references to ASBs and foreign approvals, and a signature by a CASA delegate (Requirement, Compliance, Background), but it does not record any legal challenges, case citations, or decisions.

Because the text does not supply litigation data, one cannot, from this document alone, identify whether any operator or party has disputed the AD, sought relief from its application, or been the subject of regulatory sanctions tied to this AD. The AD does reference other regulators’ instruments (DGAC AD F‑2005‑159 and EASA approval No. 2005‑6223), but it does not provide information about any litigation connected to those instruments either (Requirement, Background).

For any party seeking litigation history or precedent relating to this AD, the AD text itself does not provide that record; further research in CASA enforcement records, tribunal or court databases, or public records of airline/operator disputes would be required. Such sources are outside the AD text provided here and therefore are not reported in this note.

The Directive contains several concrete technical and procedural features that can be operationally important and which merit attention to avoid inadvertent non‑compliance.

1. Oil‑history sensitivity and categorisation. The compliance schedule depends on the engine’s oil class history. Engines operating with HTS‑class oil, engines for which the historical record of oils used is not available, and engines that previously used HTS‑class oil but no longer do are grouped together and subject to the shorter initial and recurring intervals (initial threshold 300 hours at effective date and recurring 300‑hour interval). Engines that have operated with STD‑class oil since introduction into service are treated differently (initial threshold 450 hours and recurring 500‑hour interval) (Background, Compliance). Operators with incomplete maintenance histories should treat the history as “not available”, which the AD groups with HTS exposure for compliance timing. That categorisation shortens the compliance window for engines with uncertain histories.

2. Tight initial compliance window for some engines. For engines already exceeding the thresholds at the effective date, the AD requires initial replacement within 50 operating hours from the effective date of the Directive. That creates a near‑term logistics demand for parts, maintenance slots, and downtime planning for affected engines (Compliance).

3. Two separate ASBs by engine family. The Directive does not provide a single universal procedure; it specifies two ASBs by engine variant: A319 79 2832 for ARRIUS 2B1/2B1A/2B2, and A319 79 2833 for ARRIUS 2K1/2K2 (Requirement). Using the wrong ASB or the wrong paragraph could produce a technical non‑conformance with the AD. The AD does permit later DGAC‑approved revisions, but only if they carry DGAC approval (Requirement).

4. “Fitted but not limited to” language. The Applicability states the engines are “fitted but not limited to Eurocopter EC135 TI, T2, and Agusta A109 Power and A109 LUH rotorcraft.” That means operators should not assume the AD applies only to the named rotorcraft types. Any installation of the listed engine models is subject to the AD, regardless of airframe model (Applicability).

5. No penalty text included. The AD does not state enforcement mechanisms or penalties in the excerpt provided (Penalties and enforcement). Operators should not treat the absence of penalty language as an absence of regulatory consequence. The AD is an instruction from CASA and must be integrated into continuing airworthiness processes even though enforcement details are not set out here.

6. International approvals referenced. The AD accepts DGAC‑approved ASB revisions and refers to DGAC AD F‑2005‑159 and EASA approval No. 2005‑6223 (Requirement, Background). If operators rely on foreign‑issued ASB revisions, they need to confirm the DGAC approval status, because the AD accepts only DGAC‑approved revisions as compliant.

7. Recurrence intervals differ. After the initial replacement event, the recurrence interval is 300 operating hours for HTS or unknown history engines, but 500 operating hours for STD‑class‑oil engines. That difference can be a source of scheduling error if maintenance planners assume a single interval for all engines (Compliance).

8. The AD does not prescribe documentation or reporting specifics. The AD requires the physical replacement, but does not itself mandate the exact form of maintenance log entries, certification of work, or notification to the regulator in the provided text. Operators should ensure that whatever recordkeeping and certification their maintenance system requires is completed, but that is not specified in the AD excerpt (the AD contains no such provision).

9. Interplay with prior maintenance. The AD repeatedly notes “unless previously accomplished”, meaning that if the o‑ring replacement has already been done in accordance with the referenced ASBs prior to the AD taking effect, the initial requirement may be satisfied. Operators must be able to demonstrate that prior replacements complied with the specified ASB paragraph and revision status to rely on that exception (Requirement).

10. Potential supply or scheduling bottlenecks. The short 50‑hour initial window for engines already above the threshold and the recurring intervals may create concentrated demand for parts and maintenance capacity in a short period after the AD becomes effective. The AD itself does not address parts supply, lead times, or alternative compliance pathways.

These are concrete operational pitfalls embedded in the AD’s mechanics. The AD text provides the specific numerical thresholds and ASB references; avoiding these “gotchas” depends on careful assessment of oil history, accurate operating‑hour accounting, timely procurement of the correct o‑ring parts, and strict adherence to the correct ASB paragraph and any applicable DGAC approvals.

Follow these steps derived from the AD text to meet the Directive’s requirements precisely:

1. Confirm applicability. Verify that each engine in your fleet is an ARRIUS 2B1, 2B1A, 2B2, 2K1 or 2K2 model, whether fitted to an EC135 TI/T2, Agusta A109 Power/A109 LUH, or any other type of aircraft. The AD’s Applicability applies to those engine models regardless of airframe (Applicability).

2. Determine oil class history. Establish whether each engine has operated with HTS‑class oil, STD‑class oil since introduction, whether its oil history is unknown, or whether it previously operated with HTS oil but no longer does. The AD groups HTS exposure, unknown history, and previous HTS use (now discontinued) together for the purpose of the compliance schedule (Background, Compliance).

3. Record operating hours at the AD effective date. The AD requires calculation of operating hours as at the effective date for the thresholds that trigger the 50‑hour initial replacement window. The AD’s effective date is 24 November 2005, and engines that exceeded specified hours at that effective date face the short initial window (Compliance).

4. Determine whether the initial replacement is already satisfied. If the check‑valve piston o‑ring has already been replaced in accordance with paragraph 2 of the relevant ASB prior to the AD taking effect, the “unless previously accomplished” clause applies and no immediate further action is required for the initial replacement (Requirement).

5. If the initial replacement is required, schedule it within the AD’s time window. For engines that exceeded the thresholds at the effective date and have not already had the o‑ring replaced per the ASB, accomplish the initial replacement within 50 operating hours from the AD’s effective date. The thresholds are:

   • 300 operating hours at the effective date for engines that have operated with HTS oil, have no available oil history, or used to operate with HTS oil and no longer do; or
   • 450 operating hours at the effective date for engines that have operated with STD‑class oil since introduction into service (Compliance).

6. Use the correct ASB procedure. Perform the replacement in accordance with paragraph 2 of the applicable ASB:

   • ASB No. A319 79 2832, ARRIUS 2B1/2B1A/2B2 dated 21 June 2005; or
   • ASB No. A319 79 2833 for ARRIUS 2K1/2K2. The AD allows the use of later DGAC‑approved revisions of those ASBs (Requirement). Ensure that the particular ASB revision used is DGAC‑approved when relying on a later revision.

7. Schedule and perform recurring replacements. After the initial replacement, repeat the replacement at intervals not exceeding:

   • 300 operating hours for engines operating with HTS‑class oil, engines with unknown oil history, or engines that used to operate with HTS oil and no longer do; or
   • 500 operating hours for engines operating with STD‑class oil since introduction into service (Compliance).

8. Maintain traceability of the work done. The AD text itself does not prescribe specific record formats, but in practice operators should record the work, the ASB revision used, the serial number of the engine, the operating hours at the time of replacement, and the identity of the person or organisation performing the maintenance so that the replacement can be demonstrated in future audits or inspections. The AD’s “unless previously accomplished” provision means demonstrable evidence of prior compliant replacement may be necessary to avoid duplicative work (Requirement).

9. Confirm DGAC approvals when using later ASB revisions. If using a later ASB revision, verify that the revision has DGAC approval before treating it as compliant with this AD. The AD explicitly limits acceptable ASB revisions to those carrying DGAC approval (Requirement).

10. Integrate the AD into continuing airworthiness planning. Use the AD’s operating‑hour intervals to update maintenance schedules and ensure replacements occur before the hour limits are exceeded. For engines near the threshold at the effective date, plan for the 50‑hour initial window promptly to avoid non‑compliance (Compliance).

11. Coordinate supply and maintenance capacity. Given the potential for concentrated work in the initial compliance window and recurring intervals, plan parts procurement and maintenance slots in advance to avoid operational disruption.

12. Where doubt exists, contact the regulator or the engine manufacturer. The AD references DGAC approvals and EASA approval numbers; for interpretive questions or to confirm the status of ASB revisions or acceptable compliance methods, contact the relevant regulator or Turbomeca support. The AD itself does not provide a helpdesk or contact details; the signature indicates CASA delegation (Requirement, Background).

By following these procedural steps derived directly from the AD’s Requirement and Compliance provisions and using the referenced ASB paragraph 2 procedures, operators and maintainers can align physical maintenance work with the Directive. The AD permits DGAC‑approved ASB revisions as alternatives to the original ASB issue dates, but it does not list other alternative methods or exemptions within the text provided, so reliance should be on the ASBs or on regulatory confirmation if a different method is proposed (Requirement).