AD/RB211/40 - Low Pressure Turbine Casing

The AD is organised around a small set of concepts drawn from engine maintenance practice and a single external service bulletin. The main concepts in the instrument are:

• Applicability: The AD is limited to RB211‑524C2‑19 and RB211‑524C2‑B‑19 engine models, all serial numbers (Applicability). The AD expressly records that these engines are known to be installed on Boeing 747 series aircraft, but it does not limit the requirement to that airframe type.

• Reference to Manufacturer Instruction: Requirement 1 delegates the technical details of the inspections and corrective actions to Section 3 of Rolls‑Royce NMSB No. 72‑AG076.2. The AD does not reproduce the NMSB; it makes compliance with that NMSB mandatory for affected engines.

• Cycles‑based compliance thresholds: The AD uses engine life counts, specifically Cycles Since New (CSN) and cycles since last full Fluorescent Penetrant Inspection (FPI), as the operational triggers. The number 4,500 cycles is the central threshold that determines scheduling and repetition (Compliance; Requirement 2).

• Record‑dependence and conditional timing: The required timing for initial inspection depends on whether the LPT casing life is known and whether the number of cycles since last full FPI is known. Four mutually exclusive record scenarios are set out, each mapping to a specific compliance timing: before reaching 4,500 CSN; at the next shop visit; before reaching 4,500 cycles since last full FPI; or at the next shop visit if certain records are unknown (Compliance).

• Repetitive inspection frequency: The AD requires repetition of Requirement 1 actions at intervals not exceeding 4,500 cycles (Requirement 2). This creates an ongoing maintenance schedule.

• Safety rationale linked to containment capability: The Background explains the safety risk in narrow technical terms: cracked LPT casings reduce the ability to contain debris in a stage 1 blade failure and thus can permit release of uncontained high energy debris if a blade fails while the casing is cracked (Background).

• Cross‑reference to another regulator: The document references EASA AD 2009‑0083, signalling that the AD aligns with or takes into account an action by the European regulator (Note 2).

These concepts structure the compliance decision tree for operators. The AD is not a design change; it is an inspection and corrective maintenance directive that leverages existing manufacturer instructions. Because the AD does not reproduce Section 3 of the NMSB, compliance requires an operator to obtain and follow that external technical document. The AD places emphasis on record‑keeping (knowing CSN and cycles since last full FPI) by making the inspection schedule conditional on those records.

The AD affects operators and maintainers of RB211‑524C2‑19 and RB211‑524C2‑B‑19 engines, including but not limited to operators of Boeing 747 series aircraft where these engines are known to be installed (Applicability). The phrase "all serial numbers" removes serial number‑based carve outs; every engine of those two models is in scope regardless of build or serial history.

Primary affected parties are:

• Aircraft operators and owners who use aircraft fitted with the specified RB211 variants. They must identify affected engines in their fleets and implement the inspection and maintenance schedule mandated by the AD.

• Maintenance organisations and shops that perform inspections, FPIs (fluorescent penetrant inspections), and corrective actions. The AD requires actions defined in a Rolls‑Royce NMSB and contemplates shop visits as a compliance moment; therefore, shops performing engine work will be operationally involved.

• Continuing airworthiness managers and records personnel. The compliance timing is contingent on whether the life of the LPT casing (CSN) and the time since last full FPI are "known" or not. The AD therefore imposes an administrative obligation on those who maintain maintenance records to determine the correct compliance window.

• Rolls‑Royce and parts suppliers by implication, to the extent the NMSB prescribes parts replacement or repair actions; the AD makes the manufacturer instruction mandatory, so any corrective actions specified by the NMSB will create demand for parts and repair services.

• Regulators and delegating authorities in safety oversight roles: the AD was issued by the Civil Aviation Safety Authority and signed by an authorised delegate, James Coyne; the AD is effective from a fixed date and is part of the regulator's continuing airworthiness oversight.

Who does not appear to be directly affected: other engine types and aircraft not fitted with the RB211‑524C2‑19 or RB211‑524C2‑B‑19 engines, since the Applicability clause is specific.

Note on geographical reach: the AD is an Australian instrument issued by CASA. It references an EASA AD but does not itself specify cross‑jurisdictional enforcement or recognition. The document does not limit applicability by aircraft registration jurisdiction; the plain text lists engine models as the determinant.

In terms of financial incidence, the AD delegates the operational burden,inspections, FPIs, corrective maintenance, possible part replacement and shop visits,to operators and maintenance organisations. The AD does not provide funding, exemptions, or alternate compliance methods in the text supplied.

The AD imposes the following duties on affected parties and sets out limited administrative rights by implication.

Core duties:

• Perform the actions in Section 3. Accomplishment Instructions of Rolls‑Royce NMSB No. 72‑AG076.2 for each affected engine, as required by Requirement 1. The AD makes these manufacturer instructions mandatory; the AD itself does not describe the specific inspection or corrective steps (Requirement 1).

• Repeat the Requirement 1 actions at intervals not exceeding 4,500 cycles, as set out in Requirement 2. This creates an on‑going duty to monitor cycles and schedule repetitive inspections.

• Comply with the timing matrix in the Compliance paragraph. The Compliance language creates specific deadlines based on record states:

  • If the life of the LPT Casing is known and less than 4,500 CSN, the inspection actions must be done before the life reaches 4,500 CSN.
  • If the life is known and greater than or equal to 4,500 CSN and the life since last full FPI is known and greater than 4,500 cycles or not known, the inspection must be carried out at the next shop visit.
  • If the life is known and greater than or equal to 4,500 CSN and the life since last full FPI is known and less than 4,500 cycles, the inspection must be done before the life of the LPT casing reaches 4,500 cycles since last full FPI.
  • If the life is not known and the life since last full FPI is not known or greater than or equal to 4,500 cycles, inspect at the next shop visit.
  • If the life is not known and the life since last full FPI is known and less than 4,500 cycles, inspect before the life of the LPT casing reaches 4,500 cycles since the last full FPI. (Compliance)

• Take corrective actions where inspections reveal defects. The AD states that corrective actions are required depending on findings but does not detail those actions; those details are to be found in the referenced Rolls‑Royce NMSB and, potentially, in the maintenance organisation’s engine repair procedures (Background; Requirement 1).

Administrative and procedural duties implied:

• Maintain and verify accurate engine life and inspection history records, specifically CSN and cycles since last full FPI, because the timing for mandatory inspections depends on those records (Compliance).

• Obtain and maintain access to the referenced Rolls‑Royce NMSB No. 72‑AG076.2, Section 3, to know exactly what inspections and corrective actions are required (Requirement 1).

Rights and delegations implied by the AD:

• The AD does not enumerate appeal rights, exemptions, or alternate methods of compliance within the text provided. The AD does, however, recognise the manufacturer's NMSB and EASA AD as normative references (Requirement 1; Note 2). Any formal rights to seek exemptions, alternative means of compliance, or to challenge the AD are not specified in the document supplied.

• The signature block identifies the decision authority as a CASA delegate, James Coyne, indicating that the AD is a regulator‑issued directive and that enforcement and any administrative functions around compliance will fall under CASA’s delegations (signature block).

Practical implications of duties:

• Operators must invest in record verification and scheduling to meet the conditional deadlines. The AD ties inspection timing to shop visits in some cases, which creates a coordination point between operating schedules and maintenance planning.

• Because the AD mandates following the manufacturer’s NMSB, operators and maintenance organisations must ensure they have the current version of the NMSB and must follow it precisely as part of compliance.

The AD thus imposes mandatory, cyclical obligations for inspection and corrective action, makes compliance conditional on existing operational records, and assigns responsibility to the operators and maintenance organisations without specifying procedural rights in the document itself.

The AD text supplied does not include express penalty provisions, fines, or enforcement procedures. It sets out a mandatory maintenance requirement and an effective date,2 July 2009,but does not specify the legal or administrative sanctions for non‑compliance within the document itself (Effective date). The signature block identifies the issuer as the Civil Aviation Safety Authority (CASA), signed by a delegate, James Coyne, indicating the directive is an instrument of the regulator (signature block).

What the AD does provide that is relevant to enforcement:

• A clear set of actions and timings that are made mandatory for the affected engines: carry out Section 3 of NMSB No. 72‑AG076.2 and repeat at intervals not exceeding 4,500 cycles (Requirement 1; Requirement 2). The AD format and signature signal regulatory force.

• Conditional compliance triggers that can be audited: whether the life of the LPT casing is known, whether life since the last full FPI is known, the CSN totals, and shop visit dates are all recordable facts that an inspector or auditor can check against the AD’s requirements (Compliance).

What the AD does not state, and therefore must be obtained elsewhere:

• The text does not state which agency action, penalty, or remedial enforcement will follow for failure to comply. For example, it does not specify licence action, grounding authority, monetary penalties, administrative enforcement steps, or criminal offences. The AD does not state whether non‑compliance constitutes an immediate unairworthiness for an aircraft that could be enforced by an inspector.

• The AD does not specify a process for seeking an alternative means of compliance (AMOC) or a deferral, nor does it set out an appeal mechanism. The AD also does not describe record retention periods, required evidence of compliance, or documentation standards.

Operationally, the absence of stated penalties in the text supplied means readers must treat the AD as a mandatory directive and consult the issuing authority (CASA) and their regulatory framework for details on enforcement, sanctions, and possible alternative compliance routes. The presence of a clear effective date provides a temporal marker against which compliance can be judged. The AD's alignment with an EASA AD is an additional indicator of harmonised regulatory expectations, but the instrument itself does not expand on enforcement steps that EASA might take under its jurisdiction (Note 2).

In practice, enforcement mechanisms likely exist elsewhere in the regulator’s legal framework; however, the AD document provided does not reproduce or summarise them. Parties required to comply should therefore treat the AD as mandatory and should seek authoritative guidance from CASA about enforcement, evidence of compliance, and any administrative processes related to the AD.

The AD makes a direct normative cross‑reference to a manufacturer service bulletin and to a European regulator's AD, indicating interaction with other prescriptive documents rather than with statutory provisions quoted in the text. The interaction points in the AD are:

• Manufacturer guidance: The AD makes compliance with Section 3 of Rolls‑Royce NMSB No. 72‑AG076.2 mandatory for the specified engines (Requirement 1). The NMSB is thus incorporated by reference as the technical standard for inspection and corrective actions. The AD therefore interacts functionally with private technical documentation produced by Rolls‑Royce, elevating that document to a regulatory requirement for affected engines.

• International regulatory alignment: The AD explicitly notes EASA AD 2009‑0083 dated 16 April 2009 (Note 2). That mention signals that the CASA AD is aligned with or cognisant of an EASA action. The AD does not reproduce EASA’s text nor state whether it departs from it; it only identifies the EASA AD as a reference. The interaction is therefore informational within this AD.

• Record‑keeping and maintenance regimes: The AD’s compliance rules depend on knowledge of Cycles Since New and cycles since last full FPI. Those data are typically maintained under continuing airworthiness regulations and maintenance record obligations. Although the AD does not restate those statutory record obligations, it interacts operationally with the maintenance record framework by conditioning compliance timing on the availability and content of those records (Compliance).

What the AD does not do within its own text:

• It does not cite or modify other statutory provisions, regulations, or administrative codes; it does not provide a transitional regime or temporary exemptions; it does not set out its relationship to, for example, flight release procedures, airworthiness certificates, or other administrative instruments. Any such interactions are left implicit.

Practical consequences of these interactions:

• By making a manufacturer NMSB mandatory, the AD imposes an obligation on operators to follow a private technical document. That can affect supply chains, because parts and services specified by the NMSB become compliance necessities.

• Reference to an EASA AD suggests that operators with international operations may face parallel obligations in other jurisdictions. The AD itself does not explain how duplicate requirements are to be reconciled, but it signals that the issue has regulatory attention beyond Australia.

• The AD’s reliance on record availability creates an operational interaction with maintenance record regimes. Operators lacking adequate records will fall into the compliance paths that require action at the next shop visit or before a 4,500 cycle threshold is reached since the last full FPI.

In sum, within the document supplied the AD interacts substantively with manufacturer technical instructions and with international ADs. The AD does not reproduce or alter other statutory texts; it relies on the existing maintenance and regulatory ecosystem and requires operators to coordinate compliance across those existing obligations.

The supplied document contains limited information about amendment history. What is present in the text is:

• Issue date and signature: The AD text is dated 19 May 2009 and bears the signature line "James Coyne, Delegate of the Civil Aviation Safety Authority" (signature block). The AD becomes effective on 2 July 2009 (Effective date). These dates are the only chronological markers in the document itself.

• Cross‑reference to an external AD: The AD references EASA AD 2009‑0083 dated 16 April 2009 (Note 2). This suggests contemporaneous regulatory action by EASA but is not an internal amendment history.

• No express previous versions or amendments are listed in the supplied text. The document contains duplicate headings and repeated lines (for example, "AD/RB211/40 AD/RB211/40", repeated titles and "Low Pressure Turbine Casing" and "7/2009"), which appear to be formatting artefacts rather than amendment markers. There is no "supersedes" statement, no "amends AD number X", and no "this AD replaces" clause present in the supplied material.

• The AD does not record any later amendment, cancellation, or revision. There is no notation of revision dates, no errata, and no references to subsequent NMSBs or revised service instructions.

Because the document supplied is self‑contained and limited to the initial issuance, readers seeking a complete amendment history must consult the regulator’s AD register or official publications for any modifications or superseding directives after the effective date of 2 July 2009. The presence of a signature and an effective date establishes the initial issuance but does not preclude later amendments; those later changes are simply not documented in the text provided.

In practical terms, operators should treat this text as the initial release version of AD/RB211/40 dated 7/2009, effective 2 July 2009, and should verify with CASA whether any subsequent amendments, supersessions, or related ADs have been issued since that effective date.

The supplied AD contains no litigation history. There are no references to court decisions, tribunal rulings, administrative appeals, or disputes that relate to this AD in the text provided. The only judicial or dispute‑resolution related text present is the signature block and the procedural content of the AD itself.

What the document does include that is relevant to potential litigation or administrative review:

• A clear set of mandatory technical directives and compliance timeframes that could be used in an enforcement or liability context. The Compliance matrix and the references to the Rolls‑Royce NMSB provide specific points that could be examined in any dispute about whether an operator complied.

• A cross‑reference to EASA AD 2009‑0083 and a requirement to follow a Rolls‑Royce NMSB. Those external documents, if invoked in a dispute, would need to be obtained and assessed for their content and applicability.

Because the AD provides no information on litigation, readers wishing to know whether the AD has been the subject of legal challenge or administrative appeal must consult court records, tribunal registries, or the regulator’s public records. The absence of litigation information in the text is not evidence of the absence of litigation; it is simply a non‑presence in this particular document.

Operators and counsel should therefore treat the AD as a regulatory requirement in force from the effective date and should, if concerned about potential enforcement or liability, review contemporaneous regulatory records and legal databases for any cases or formal disputes involving AD/RB211/40 or related actions.

The AD contains several operational and interpretive pitfalls that can affect compliance timing, documentation, and maintenance planning. These "gotchas" arise from phrasing in the Compliance paragraph, the incorporation of an external NMSB, and the AD’s silence on enforcement detail.

Key practical pitfalls:

• Record dependency: The AD’s timing depends on whether the "life of the LPT Casing is known" and whether the "life of the LPT casing since last full FPI is known" (Compliance). If an operator lacks complete records, the AD routes them to different compliance timings. Operators with incomplete records may be obliged to carry out inspections at the "next shop visit" or before an upper threshold is reached, depending on which record is missing. Therefore poor record keeping can force earlier or less flexible actions.

• Ambiguity of "next shop visit": The AD repeatedly uses "at the next shop visit" as a compliance point for certain record states (Compliance). The AD does not define "shop visit" in this text. Different operators may interpret "shop visit" variably,e.g. a scheduled heavy maintenance visit, an engine change, or a shop visit for other reasons. This ambiguity can create disagreement between an operator and an inspector about whether compliance timing was met.

• Undefined content of required actions: Requirement 1 mandates actions from Section 3 of Rolls‑Royce NMSB No. 72‑AG076.2 but the AD does not reproduce those instructions (Requirement 1). Operators must obtain the NMSB and ensure they are following precisely Section 3. There is a risk of non‑compliance if the wrong revision of the NMSB is used, if the NMSB has been superseded, or if the operator misinterprets the NMSB.

• Corrective actions unspecified in the AD: The AD states that corrective actions are required "depending on findings" but does not list what those corrective actions are (Background; Requirement 1). Corrective actions may be repair, modification or removal and replacement. Because the AD does not specify them, the operator must consult the NMSB and may incur additional downtime, parts costs or shop work whose scale is unknown from the AD alone.

• Repetition interval large: The repeat interval is "at intervals not exceeding 4,500 Cycles" (Requirement 2). That is a long interval in terms of potential engine operation. If cycles are high usage, an operator could reach a significant exposure window between mandated inspections. The AD does not offer interim checks or risk‑based variations.

• All serial numbers included: The Applicability covers "all serial numbers" for the two engine models (Applicability). There is no serial‑number carve‑out for known non‑affected subpopulations, which can cause operators to assume erroneously that a particular serial build is excluded if they do not read the "all serial numbers" phrase carefully.

• Cross‑jurisdictional coordination: The AD references EASA AD 2009‑0083 (Note 2) but does not explain whether compliance with the EASA AD is sufficient or whether separate steps must be taken for Australia. Operators flying across jurisdictions will need to verify parallel obligations.

• Lack of enforcement details: The AD does not contain enforcement or penalty language. This absence creates uncertainty about the consequences of non‑compliance and about procedural mechanisms like alternative means of compliance or appeals. Operators should not interpret silence as permissive; instead they should proactively consult CASA for enforcement protocols.

• Effective date lead time: The AD was signed 19 May 2009 and became effective 2 July 2009. Operators must check whether their maintenance schedules provide enough lead time to obtain the NMSB, schedule shop visits, and carry out the required inspections before the effective date window or before the 4,500 cycles thresholds are reached.

Each of these items creates potential for an operational or compliance misstep. The common mitigation themes are: verify and centralise engine life and inspection records; obtain the exact NMSB Section 3 and its revision history; interpret "shop visit" in coordination with CASA or through established maintenance agreements; and budget for corrective actions that the AD does not quantify.

The AD sets a clear, record‑dependent compliance pathway. The following steps are a practical checklist for operators and maintenance organisations to implement the AD’s requirements in the order and manner the AD prescribes. Each step is grounded in the AD text and points to the specific compliance language.

1. Identify affected engines

   • Confirm which engines in the fleet are RB211‑524C2‑19 or RB211‑524C2‑B‑19, all serial numbers (Applicability). Do not assume limited applicability because the AD notes the engines are known to be installed on Boeing 747 series aircraft but not limited to that airframe.

2. Assemble and verify records

   • Determine for each affected engine whether the "life of the LPT Casing" (Cycles Since New, CSN) is known and whether the "life of the LPT casing since last full FPI" is known (Compliance). These two binary determinations drive the subsequent timing requirements.

3. Map each engine into the AD’s compliance matrix

   • If life (CSN) is known and less than 4,500 CSN, schedule the actions required by Requirement 1 "before the life of the LPT casing has reached 4,500 CSN" (Compliance).
   • If life is known and greater than or equal to 4,500 CSN and cycles since last full FPI is known and greater than 4,500 cycles, or cycles since last full FPI is not known, schedule the actions "at the next shop visit" (Compliance).
   • If life is known and greater than or equal to 4,500 CSN and cycles since last full FPI is known and less than 4,500 cycles, schedule the actions "before the life of the LPT casing has reached 4,500 cycles since last full FPI" (Compliance).
   • If life is not known and cycles since last full FPI is not known or greater than or equal to 4,500 cycles, schedule the actions "at the next shop visit" (Compliance).
   • If life is not known and cycles since last full FPI is known and less than 4,500 cycles, schedule the actions "before the life of the LPT casing has reached 4,500 cycles since last full FPI" (Compliance).

4. Obtain the mandatory instructions

   • Acquire Sections 1-3 of Rolls‑Royce NMSB No. 72‑AG076.2 and ensure you have the correct revision. The AD makes Section 3 the required "Accomplishment Instructions" for the inspections and corrective actions (Requirement 1). Confirm whether the NMSB has serviceable parts lists, special tools, or specific technique requirements for FPI.

5. Perform inspections and FPIs as directed

   • At the scheduled compliance point for each engine, carry out the actions specified in Section 3 of the NMSB. The AD requires these actions as mandatory (Requirement 1). Ensure the FPI is performed to the level described in the NMSB and that results are documented.

6. Take corrective actions where required

   • If the inspection finds cracking or other defects, follow the corrective action instructions in the NMSB, since the AD requires corrective actions depending on findings but does not specify them in text (Background; Requirement 1). Document all repairs, parts fitted and post‑repair inspections.

7. Schedule repetitive inspections

   • After the initial inspection, implement a repeat schedule so that Requirement 1 actions are repeated "at intervals not exceeding 4,500 Cycles" (Requirement 2). Record each repeat inspection date, cycles at inspection, and the outcomes.

8. Document compliance

   • Maintain dated records showing engine CSN, cycles since last FPI, the date and result of each inspection mandated by this AD, details of corrective actions and parts replaced, and any shop visit references. Because compliance timing depends on these records, accurate documentation is essential (Compliance).

9. Coordinate shop visits

   • For engines routed to inspection "at the next shop visit," coordinate with your maintenance provider to align shop visit timings so inspections are carried out within the AD requirement window. Clarify the definition of "shop visit" internally and, if necessary, with CASA.

10. Liaise with CASA where ambiguous

    • If there is uncertainty about interpretation,such as the definition of "shop visit," acceptable NMSB revisions, or the applicability to a particular airframe,seek clarification from CASA. The AD does not include appeal or AMOC language; therefore, early regulator engagement reduces enforcement risk.

11. Consider cross‑jurisdictional obligations

    • Because the AD references EASA AD 2009‑0083 (Note 2), operators with international operations should check whether parallel action is required in other jurisdictions and whether coordinated compliance documentation will satisfy multiple regulators.

12. Review maintenance and budgeting impacts

    • Plan for potential corrective action costs and shop downtime. The AD does not quantify repair requirements or parts; those costs will depend on NMSB remediation steps and inspection findings.

13. Verify effective date and timing

    • Note the AD is effective 2 July 2009 (Effective date). For historical compliance or audit purposes, verify actions that were performed before or after that date to ensure records align with the AD’s effective timeline.

Following these steps aligns operational practice with the AD’s mandatory content. The two operational pillars are strict record verification to select the correct compliance path and faithful execution of Section 3 of the Rolls‑Royce NMSB No. 72‑AG076.2. Because the AD relies on external technical material for the specifics of inspection and corrective action, ensuring access to and strict adherence to the NMSB is a necessary compliance step.