AD/AL 250/90 - Turbine Wheel Event Thresholds and Maximum Overspeed Transients

The AD is built around several tightly defined technical and procedural concepts drawn from the RRC Alert CEBs and the AD text. These are the working concepts an operator must translate into maintenance practice.

• Applicability by engine model and by turbine wheel part number. The AD applies to specific RRC 250 variants and to wheels with discrete part numbers: third‑stage P/N 6898663 or 23065843, and fourth‑stage P/N 6892764 or 23066744. The AD explicitly notes installation on particular helicopter types but does not limit applicability to those types: “These engines are installed on, but not limited to,” followed by model examples.

• Event threshold and maximum overspeed transient. The AD’s trigger for logging and retirement is a speed window defined as the range “between ‘Event Threshold’ and ‘Maximum Overspeed Transient’.” The AD delegates the numerical identification of those thresholds to the manufacturer’s CEBs, directing use of specific paragraphs and figures in the combined CEB document, Revision 2, dated 27 June 2006. Thus the AD does not itself publish numerical RPM limits; compliance depends on following the RRC figures and instructions.

• Recording of events. The first mandatory duty is a recordkeeping obligation: “Record each time the third‑ and fourth‑stage turbine wheels enter into the speed range.” The AD ties the mechanics of detection to the RRC CEBs (paragraph 2.A. through 2.A.(5) and Figures 1-5).

• Retirement after multiple excursions. The AD establishes a cumulative‑exposure retirement rule: remove and retire any third‑ or fourth‑stage turbine wheel before further flight after the sixth time the wheel has entered the defined speed range. This is an event‑count threshold separate from conventional hour/cycle life limits.

• Additionality of retirement criteria. The AD explicitly states that the event‑count retirement criteria are “in addition to the existing third‑ and fourth‑stage turbine wheel hour and cycle life limits,” with the specific proviso that wheels must be retired when they exceed any published life limit, whether due to transient speed excursions, hours, or cycles.

• Temporal compliance windows. The AD requires initial recording to begin within 30 days after the AD’s effective date, and the retirement action to occur as an immediate flight safety constraint after the sixth event (i.e., before any further flight).

• Manufacturer service guidance as normative for detection. The AD makes the RRC Alert CEBs an incorporated technical reference for determining the speed‑range events, thereby placing practical reliance on the manufacturer’s figures and accomplishment instructions.

These concepts together mean the AD operates as a monitoring plus mandatory retirement rule set: operators must monitor and log excursions as defined by the manufacturer, count events per individual wheel, and remove/retire wheels that hit the cumulative event threshold, while continuing to honour existing hour/cycle limits.

The AD names its applicability precisely and therefore narrows the set of obligated parties to specific operators, maintainers, and supply chain participants.

• Aircraft operators and owners. Any operator with an aircraft fitted with the listed RRC model 250 engines and with the specified third‑ or fourth‑stage turbine wheels installed is directly affected. The AD lists engines “rolls‑Royce Corporation (RRC) models 250‑C30, ‑C30G, ‑C30G/2, ‑C30M, ‑C30P, ‑C30R, ‑C30R/1, ‑C30R/3, ‑C30R/3M, ‑C30S, ‑C30U, ‑C40B, ‑C47B, and ‑C47M turboshaft engines” with the third‑stage and fourth‑stage wheel P/Ns specified. It further notes the engines are installed on particular helicopter makes and models including Bell and Sikorsky types. Where those wheels are present on an airframe, the operator is required to comply.

• Maintenance organisations and independent MROs. The AD requires recording, detection and removal actions that are typically executed by maintenance organisations. They must adopt the RRC CEB procedures as part of their maintenance planning and carry out removals/retirements when the event count is reached. Independent MROs servicing the listed engines must adopt the AD’s requirements in their workpacks and ensure records reflect compliance.

• Fleet managers and aircraft registrants. Because the AD requires per‑wheel event counting and retirement, registrants and fleet managers who consolidate maintenance data across multiple airframes will need to track wheel histories, especially where wheels may move between engines or aircraft. The AD’s retirement trigger applies per wheel, so tracking ownership and movement of wheels matters.

• Parts suppliers and the manufacturer. The requirement to remove and retire wheels will create demand for replacement third‑ and fourth‑stage wheels, and possibly for surplus spares. Suppliers and the manufacturer face potential concentrated demand from affected fleets, and MROs will need approved replacement parts.

• Regulators and safety auditors. CASA is the issuing authority, and the AD’s effective date and signature are within the AD. Safety auditors and CASA inspectors will use the AD’s recording and retirement requirements as compliance checkpoints.

• Operators of other engine/wheel permutations. The AD is limited to particular P/Ns and models. Operators of other 250 series variants or wheels with different P/Ns are not covered by this AD text, though they may wish to evaluate similarities. The AD explicitly restricts scope by listing part numbers and models.

The AD thus creates obligations that fall most heavily on operators, MROs and parts suppliers associated with the listed model/purchase‑part combinations. The AD does not purport to create obligations for aircraft that do not have those P/Ns installed.

The AD establishes a small set of compulsory duties and leaves other matters to existing rules or manufacturer guidance. The text specifies duties rather than rights; rights are implicit (for example, to follow the referenced RRC CEBs as compliance method).

Duties:

• Applicability identification duty. Operators must determine whether engines on their aircraft have the specified third‑ or fourth‑stage turbine wheels installed (P/Ns listed). The AD’s “Applicability” section lists the engine models and wheel part numbers; determining applicability is a precondition to compliance.

• Event monitoring and recording duty. The AD requires that operators “Record each time the third‑ and fourth‑stage turbine wheels enter into the speed range between ‘Event Threshold’ and ‘Maximum Overspeed Transient’.” The AD prescribes the measurement method: use paragraph 2.A through 2.A.(5) and Figures 1-5 of the combined RRC CEBs Rev 2 dated 27 June 2006 to determine the speed range. The duty has a timing element: initial recording must commence “within 30 days after the effective date of this AD.”

• Retirement duty upon cumulative excursions. The AD requires removal and retirement of any third‑ or fourth‑stage turbine wheel “before further flight after the sixth time the wheel enters into the speed range.” That duty is an immediate operational restriction: once a wheel reaches the sixth recorded event it must be removed and retired before any next flight of the aircraft that contains it.

• Conformance with published life limits. The AD clarifies that its retirement criteria are additional to existing published life limits. It requires wheels be retired whenever they “exceed any published life limit (transient speed excursions, hours, or cycles).” That is an affirmative duty to monitor and enforce existing life‑limit rules in addition to the event count.

• Use of specific manufacturer technical material. The AD directs operators to use specified parts of RRC Alert CEBs Rev 2 (specific CEB numbers and paragraph/figures) as the method for determining when an event has occurred. Following those instructions is a duty in the sense of the AD’s explicit prescription of the technical standard for detection.

Rights and operational implications (implicit):

• Right to rely on the CEB method for compliance. The AD makes the RRC CEBs the operative technical method. An operator who follows those specified parts of the CEBs is complying, as the AD references those instructions directly.

• Right to retire parts rather than repair/continue use. The AD mandates removal and retirement of wheels after the event count or published life limit is exceeded; it does not contemplate continued use beyond those triggers.

• Recordkeeping as evidence of compliance. While the AD does not specify retention duration, the recording duty gives operators a practical evidentiary tool to demonstrate to CASA inspectors that they commenced monitoring within 30 days and are correctly counting events and retiring wheels when required.

The AD contains no procedural exemption language, no process for alternative methods of compliance (AMOCs), and does not in this text articulate appeal rights; it does, however, reference the manufacturer’s CEBs as the compliance method and cross‑references an FAA AD. The AD’s commands are technical and operational rather than discretionary.

The AD text itself does not set out specific penalty provisions or enforcement mechanisms such as infringement notice fines, criminal sanctions, or administrative penalties. The document is an Airworthiness Directive and bears the authority of CASA, indicated by the signature line: “James Coyne, Delegate of the Civil Aviation Safety Authority” (13 October 2006). It states the AD became effective on 23 November 2006. The AD instructs operators to comply with its requirements and to use specified RRC CEBs to determine event thresholds and to retire wheels after defined counts.

From the source text, the following enforcement‑relevant facts are explicit:

• The AD is mandatory for the named applicability set: engines and part numbers listed. The AD’s requirements are framed in mandatory language (“Record each time...,” “Remove and retire any...,” “Within 30 days...,” and “Before further flight after the sixth time...”).

• The AD provides a precise compliance schedule: initial recording within 30 days of the effective date and retirement prior to further flight after the sixth event. This timing creates immediate operational obligations that would be relevant in any regulatory compliance check by CASA.

• The AD cross‑references FAA AD 2006‑20‑07, but does not adopt or restate FAA enforcement text.

What the AD does not include (and so cannot be asserted from the source):

• The AD does not specify statutory penalties, monetary fines, or criminal sanctions for non‑compliance within the text provided. It does not specify enforcement procedures, audit or records‑retention periods, or administrative review mechanisms.

• The AD does not set out an explicit alternative method of compliance process, nor does it provide instructions for seeking relief from the requirements within the AD text.

Practical enforcement implication based on the AD’s form and signature: CASA, as issuer, would be the enforcing authority in the Australian civil aviation regulatory environment; inspectors would assess compliance with the AD’s recording and retirement rules. The AD itself, however, contains only the technical and timing prescriptions, not the regime of administrative penalties or specific enforcement steps.

Readers should therefore treat the AD’s recorded duties as regulatory obligations under CASA’s airworthiness framework, while recognising that this AD text does not itself detail the sanctioning mechanism for breaches.

The AD explicitly interacts with a small set of existing technical and regulatory materials. The source text identifies those interactions; it does not incorporate broader law.

• Interaction with manufacturer‑published life limits. The AD explicitly states the retirement criteria it prescribes are “in addition to the existing third‑ and fourth‑stage turbine wheel hour and cycle life limits.” It adds: “Wheels must be retired when they exceed any published life limit (transient speed excursions, hours, or cycles).” Thus operators must observe both the AD’s event‑count retirement rule and any pre‑existing published life limits for those parts. The AD therefore creates a conjunctive compliance requirement: satisfy both the new event-count rule and existing life‑limit rules.

• Interaction with RRC Alert CEBs. The AD makes the specified RRC CEBs Rev 2 dated 27 June 2006 a normative determination tool for what constitutes an event. It directs the use of paragraph 2.A. through 2.A.(5) and Figures 1-5 of CEBs No. A‑72‑3272, A‑72‑5048, and A‑72‑6054 (combined in one document). That is a direct substantive interaction: the AD’s monitoring duty can only be executed by applying the manufacturer’s CEB guidance.

• Cross‑reference to FAA AD. The AD contains a reference: “Note 3: FAA AD 2006‑20‑07 Amdt 39‑14776 dated 20 September 2006 refers.” This indicates the CASA AD anticipates alignment or correspondence with an FAA action on the same technical subject. The AD itself does not import the FAA AD’s provisions, but it signals cross‑jurisdictional coordination on the safety issue.

• Interaction with airworthiness certification and maintenance frameworks. While the AD does not cite enabling legislation or CASA enforcement provisions, its status as an AD implies it functions within the CASA airworthiness oversight regime. The source text does not set out other legal instruments (for example, standard maintenance regulations), so any interaction beyond the AD and the RRC CEBs is not specified in the provided text.

• No stated conflicts or supersessions in the text. The AD does not state that it supersedes any prior CASA AD or relaxes any existing rule. It adds to existing life‑limit obligations.

Because the AD prescribes a technical method tied to manufacturer CEBs and cross‑references an FAA AD, the practical legal interaction is with manufacturer service guidance and parallel FAA action, and with existing published life limits for turbine wheels. The AD does not purport to modify other regulatory instruments within the text provided.

The source document provides only the issuance, signature and effective date information for this particular AD and references a Rev 2 of the manufacturer CEBs and an FAA AD. The AD text itself does not include a record of any earlier or subsequent CASA amendments to AD/AL 250/90 within the supplied material.

Explicitly present items relevant to amendment history:

• AD identifier and date: AD/AL 250/90, dated 12/2006, signed 13 October 2006 by James Coyne as Delegate of CASA. The AD states: “This Airworthiness Directive becomes effective on 23 November 2006.”

• Manufacturer document revision referenced: the AD directs use of RRC Alert Commercial Engine Bulletins No. CEB A‑72‑3272, No. CEB A‑72‑5048, and No. CEB A‑72‑6054 “(combined in one document), all Revision 2, dated 27 June 2006.” That indicates the AD incorporates a specific revision level of the CEBs.

• Cross‑jurisdictional reference: “FAA AD 2006‑20‑07 Amdt 39‑14776 dated 20 September 2006 refers.” That indicates the FAA had issued a related AD prior to this CASA AD’s effective date.

What the source does not include:

• No earlier or later CASA amendment entries are supplied in the text. The AD does not indicate that it replaces a prior CASA AD, nor does it include post‑issuance modification notes within the provided material.

• No explicit record of subsequent revisions, supersessions or withdrawal of the AD is present in the supplied text.

Accordingly, if a reader requires amendment history beyond the issuance and effectiveness details and the manufacturer CEB revision the AD references, they will need to consult CASA’s AD registry or subsequent publications. The AD itself records only its original signature and effective date and the reliance on RRC CEBs Revision 2.

The supplied AD text contains no litigation‑related material. It does not report any legal challenges, appeals, enforcement actions, or court decisions referring to AD/AL 250/90.

What the document does contain that is pertinent to litigation risk and evidence:

• The AD sets clear technical requirements and timing: record events and retire wheels after six recorded events, plus comply with published life limits. If a dispute or litigation arose from an incident, an operator’s maintenance records showing whether the recording began within 30 days of the effective date and whether removal occurred before further flight after the sixth event would be central evidentiary matter. The AD’s textual clarity on these points provides a concrete compliance standard.

• The AD ties the technical determination of an event to specific paragraphs and figures in RRC CEBs Rev 2 dated 27 June 2006. In any subsequent enforcement or litigation context the content of those CEB paragraphs and figures (the AD explicitly incorporates them for event determination) would be material. Again, the AD supplies the reference but not the CEB text itself.

• The AD notes a safety purpose: “This AD results from analysis by RRC of failures of third‑stage turbine wheels. The issuing of this AD is to prevent loss of power possible engine shutdown, or uncontained failure.” That statement of regulatory purpose could be relevant in any administrative review or litigation context about the reasonableness of the AD’s measures, but the AD supplies only the purpose statement, not the analytical data.

Because the document does not include case names, enforcement notices, or appeals, the supplied material contains no litigation history to report. Any litigation or administrative challenge subsequent to the AD would need to be researched outside this text.

Several practical and legal details in the AD are potential compliance pitfalls; these are drawn directly from the AD language and from the operational implications of that language.

• Per‑wheel counting is required. The AD requires you to “Record each time the third‑ and fourth‑stage turbine wheels enter into the speed range ...” and to remove and retire a wheel “before further flight after the sixth time the wheel enters into the speed range.” The trigger is per wheel, not per engine or per aircraft. If wheels are swapped between engines or aircraft, history must travel with the wheel. Failure to track wheels at part‑number/serial‑number granularity will defeat compliance and could lead to inadvertently overusing a wheel that has reached the sixth event.

• The AD delegates the event definition to manufacturer CEBs. The AD instructs operators to “use paragraph 2.A. through 2.A.(5) of the Accomplishment Instructions and the applicable Figures 1 through 5 of RRC Alert Commercial Engine Bulletins ... Revision 2, dated 27 June 2006 to determine the speed range.” The AD does not itself state numerical thresholds. Operators must obtain and correctly apply the specified CEB paragraphs and figures; failure to follow the correct revision or paragraph/figure could lead to incorrect event counting.

• Timing of initial recording. The AD requires recording to begin “within 30 days after the effective date of this AD.” The effective date is 23 November 2006. That creates a short lead time for affected fleets to update maintenance procedures and record systems to capture the required data. The AD does not provide an alternative compliance timetable within the text.

• Immediate grounding risk upon reaching six events. Once a wheel reaches six recorded events it “must” be removed and retired “before further flight.” That creates an immediate operational constraint: an aircraft may be grounded until an approved replacement wheel is installed. If multiple wheels across a fleet reach the threshold in a short window, spare availability and maintenance capacity may be tested.

• Retirement is mandatory, not repair. The AD uses the term “retire,” and it requires removal and retirement of the wheel after the trigger. The AD does not provide for re‑service or repair in lieu of retirement for wheels that have hit the count.

• Retirement criteria are additional to life limits. The AD emphasises that these criteria are “in addition to the existing third‑ and fourth‑stage turbine wheel hour and cycle life limits.” An operator cannot rely on hours or cycles alone; they must also monitor transient excursions and event counts.

• Applicability narrowness can mislead. The AD applies only to specific wheel P/Ns and named engine models. Wheels with different P/Ns or different engines are not covered by this AD text, but operators with other 250 series variants should not assume immunity; similar issues may exist but are not addressed here.

• No specified record retention period in the AD text. The AD requires recording but does not state how long records must be kept. That omission leaves ambiguity for audit expectations; in practice operators should retain records as long as necessary to demonstrate compliance, especially across wheel life and resale or refurbishment events.

• Dependence on external documents. Since the AD requires use of specific CEB paragraphs and figures, any errors, ambiguities or updates in those CEBs could create implementation uncertainties. The AD references CEB Revision 2 dated 27 June 2006; operators must ensure they use that revision and the specified parts.

• Cross‑reference to FAA AD. The AD notes FAA AD 2006‑20‑07 refers. Operators who fly internationally or interact with US regulation may need to reconcile CASA’s AD duties with FAA expectations, but the AD text itself does not specify how to treat any differences.

These are concrete operational and administrative pitfalls flagged by the AD’s specific wording. Operators should take them into account when implementing procedures to avoid inadvertent non‑compliance.

The AD sets a compact compliance pathway: identify applicability, start recording, and retire wheels after the trigger or when life limits are exceeded. The following steps map the AD’s text to practical actions; each step derives from or is consistent with the AD language and the referenced CEB requirements.

1. Confirm applicability precisely. Check engines on each aircraft against the AD’s “Applicability” list: RRC models 250‑C30, ‑C30G, ‑C30G/2, ‑C30M, ‑C30P, ‑C30R, ‑C30R/1, ‑C30R/3, ‑C30R/3M, ‑C30S, ‑C30U, ‑C40B, ‑C47B, and ‑C47M, and confirm that the third‑stage turbine wheel P/N is 6898663 or 23065843 or the fourth‑stage wheel P/N is 6892764 or 23066744. If the wheel P/Ns are not one of these listed, the AD text does not apply to that wheel.

2. Obtain and familiarise maintenance staff with the referenced CEBs. The AD mandates use of specific parts of RRC Alert CEBs Revision 2 dated 27 June 2006 (CEBs A‑72‑3272, A‑72‑5048, A‑72‑6054 combined). Acquire the combined document and ensure maintenance personnel read paragraph 2.A through 2.A.(5) and Figures 1-5 , those elements define the “Event Threshold” and “Maximum Overspeed Transient” speed range. The AD specifically directs use of those paragraphs and figures to determine when an entry into the speed range has occurred.

3. Implement per‑wheel event logging. Create or adapt maintenance logs to record each time a third‑ or fourth‑stage wheel enters the defined speed range. The AD requires “Record each time the third‑ and fourth‑stage turbine wheels enter into the speed range between ‘Event Threshold’ and ‘Maximum Overspeed Transient’.” Logs must be at per‑wheel granularity (by part number and serial number) so that if a wheel is moved between engines or aircraft the event history travels with the wheel.

4. Commence recording within the AD’s 30‑day window. The AD requires initial recording “within 30 days after the effective date of this AD” (effective date 23 November 2006). Implement the logging process and train relevant staff within that timeframe. Keep a dated record showing when the recording process started to evidence compliance with the AD’s timing requirement.

5. Monitor event counts and retire at six. Maintain running counts for each wheel. Once any wheel is recorded to have entered the defined speed range for the sixth time, remove and retire that wheel before that aircraft’s next flight: the AD requires removal “before further flight after the sixth time the wheel enters into the speed range.”

6. Continue to monitor and retire per published life limits. The AD explicitly states retirement criteria are “in addition to the existing third‑ and fourth‑stage turbine wheel hour and cycle life limits.” Continue to monitor hours and cycles and retire wheels when published life limits are exceeded, including if published limits count transient speed excursions.

7. Use compliant replacements and manage spares. When removing and retiring wheels, use approved replacement wheels that conform to the engine’s parts‑catalogue requirements. Anticipate potential spare part supply needs, especially across fleets that may approach the six‑event threshold simultaneously.

8. Document compliance for audit. Although the AD does not prescribe a record retention period, maintain complete records showing: (a) how applicability was determined for each engine/wheel, (b) the maintenance procedure used (the RRC CEB paragraph and figure references), (c) the date recording commenced (within 30 days of the effective date), (d) per‑wheel event counts, and (e) removal and retirement actions including dates and replacement part details. Keep serial numbers with the logs to show per‑wheel histories.

9. Coordinate with MROs and manufacturer where ambiguous. If the RRC CEBs contain technical ambiguities in determining whether a particular transient qualifies as an entry into the defined speed range, consult RRC or an authorised representative for clarification. The AD directs specific CEB paragraphs and figures; rely on manufacturer technical support for interpretation where necessary.

10. Reconcile with any applicable FAA requirements for international operations. The AD notes “FAA AD 2006‑20‑07 ... refers.” Operators who must satisfy FAA oversight in addition to CASA should review the FAA AD text to ensure any cross‑jurisdictional obligations are harmonised in practice.

Following these steps will map the AD’s textual requirements into an auditable compliance regime: precise applicability checks, using the RRC CEB technical method, per‑wheel event logging started within the 30‑day window, mandatory retirement at the sixth event or when published life limits are exceeded, and record retention sufficient to demonstrate compliance to CASA.