AD/RB211/46 - State of Design Airworthiness Directives - 1

This Directive rests on a small number of discrete legal and technical concepts that determine operator obligations and the scope of the measure.

Applicability, as set out in the Applicability heading, narrowly defines the population of engines and installations covered: RB211‑524 B2, C2, D4, G2, H and H‑36 engines installed in Boeing 747 and 767 aircraft, "as specified in the requirement documents." The Directive therefore operates by reference to both engine variant and installation on specific airframes, not by a blanket brand or family identifier.

The Requirement paragraphs establish a two‑stage duty structure. Stage one is a duty of inquiry, to "Determine the applicability of the Rolls‑Royce Service Bulletin(s) listed in Table 1." Stage two is a conditional corrective duty: "If it is determined that a Service Bulletin listed in Table 1 is applicable and has not been previously accomplished, perform the actions required by that Service Bulletin at the nominated date or later approved version." The Directive thus imports Rolls‑Royce Service Bulletins as the substantive technical instruments that define the maintenance and modification actions required, while retaining CASA’s authority to require the operator to use either the nominated date in the listed SB or a later approved version.

Table 1 performs the mapping function between UK CAA AD references and Rolls‑Royce Service Bulletin identifiers, together with the SB dates and terse titles that identify the systems affected. The three entries are presented as discrete, once‑only actions, each tied to a specific SB number and a historical publication date. The Background paragraph makes explicit that these are "once‑only actions for which the compliance date and/or period has passed." In legal terms, the AD therefore imposes retroactive obligations to perform maintenance tasks whose originally stated compliance windows have already closed.

The Compliance provision sets a strict temporal enforcement point: "Before further flight after the effective date of this Directive." The effective date is specified as 8 June 2012. That formulation converts the once‑only requirements into an immediate ground for operational grounding unless the work has been completed, or was already completed, prior to the effective date.

Administrative provenance is recorded: the instrument is a CASA Airworthiness Directive, signed by a named delegate, Mike Higgins, on 25 May 2012. The Background shows the AD is a domestic instrument implementing or "explicitly mandating" state‑of‑design (UK) ADs for Australian aircraft, not merely an advisory notice.

Finally, the Directive contemplates "later approved version[s]" of the Service Bulletins as acceptable means of compliance. The document does not specify the approver or approval process, but it expressly allows for versions subsequent to the nominated SB issue date to be used if they are approved. That mechanism creates an avenue for using updated technical instructions while maintaining the AD’s mandatory character.

The Directive explicitly affects operators and maintainers of aircraft fitted with specified Rolls‑Royce RB211‑524 engine variants, as stated in the Applicability heading. The listed engine variants are RB211‑524 B2, C2, D4, G2, H and H‑36. The installation context is equally specific: engines installed in Boeing 747 and Boeing 767 airframes "as specified in the requirement documents." The cross‑reference to "requirement documents" indicates that the precise installations, and any qualifications or exceptions, are determined by reference to the text of the Service Bulletins and the state‑of‑design ADs cited in Table 1.

Primary affected parties are therefore:

• Aircraft operators who operate Boeing 747 or 767 aircraft fitted with the RB211‑524 variants listed. These are the parties that must determine applicability, carry out the Service Bulletin actions if applicable and not already done, and ensure compliance before further flight after 8 June 2012.
• Maintenance organisations responsible for accomplishing Rolls‑Royce Service Bulletin work, since the AD prescribes technical work defined in Service Bulletins and those organisations will typically perform or supervise the required maintenance actions.
• Continuing airworthiness managers and records custodians, who must be able to demonstrate whether the specified Service Bulletin actions have already been accomplished, and to record actions performed under this AD.

The Directive’s Background explains CASA's motive to "explicitly mandate" the UK ADs for Australian aircraft, because the actions are once‑only and their original compliance dates or periods have passed. That framing principally affects operators who had not complied with the UK ADs when they fell due, since those operators will now be required to complete the once‑only actions to remain compliant with CASA requirements. The AD establishes a domestic legal requirement where previously the technical requirements may have been treated as state‑of‑design obligations; in short, it converts the state‑of‑design ADs into a mandatory domestic AD for the affected Australian aircraft.

The Directive is silent about third parties such as lessors, insurers, or passengers. However, because the AD creates an obligation that must be satisfied before further flight, it will affect operational planning and aircraft availability; the entity that bears the direct cost is the operator or the party contractually responsible for airworthiness maintenance. The AD does not specify exemptions or alternative means of compliance other than the allowance to use a "later approved version" of a listed Service Bulletin, so any party seeking relief would need to rely on record evidence of prior accomplishment or on an alternate approval process not specified in this document.

Key duties

• Determine applicability: Operators must "Determine the applicability of the Rolls‑Royce Service Bulletin(s) listed in Table 1," as stated in Requirement 1. That is a positive duty to assess whether each listed SB applies to their specific engine/installation configuration.
• Perform required actions if applicable and not already done: Requirement 2 conditions the duty to act on the determination of applicability and whether the work has already been accomplished; if a listed SB is applicable and not previously done, the operator must "perform the actions required by that Service Bulletin at the nominated date or later approved version."
• Comply before flying: The Compliance clause mandates that the required actions be completed "Before further flight after the effective date of this Directive." The effective date is specified as 8 June 2012.

These duties are framed as once‑only obligations, per the Background paragraph which confirms CASA reviewed state‑of‑design ADs and "decided these UK ADs should be explicitly mandated for Australian aircraft" because "They require once‑only actions for which the compliance date and/or period has passed."

Rights and procedural flexibilities recorded in the Directive

• Reliance on prior accomplishment: The Directive explicitly conditions required action on whether the Service Bulletin work "has not been previously accomplished." This affords operators a right to establish compliance retrospectively by producing maintenance records showing the SB actions were completed prior to the AD’s effective date.
• Use of later approved versions: The Directive permits performance "at the nominated date or later approved version." That language recognises the possibility that Rolls‑Royce or the state of design may have issued later SB revisions; operators may comply using those later approved versions rather than being restricted to the historical SB edition listed in Table 1. The Directive does not define who must approve later versions, but the phrase indicates an acceptance of updated technical instructions where formally approved.

Delegation and authority

• The AD is signed by "Mike Higgins, Delegate of the Civil Aviation Safety Authority," dated 25 May 2012. That indicates the instrument is issued under CASA’s delegate authority; however the Directive text does not set out the statutory delegation framework or appeal rights.

What the duty structure implies operationally

• The Requirement creates a proactive compliance obligation: operators must not only perform work where necessary, but must make a record‑based determination of applicability. The "determine applicability" step thus imposes a records and assessment duty prior to deciding whether the physical work is required.
• The "before further flight" compliance timetable suspends normal operations for any aircraft whose engines are subject to an applicable SB that has not already been done; the operator must resolve the matter prior to the next flight.

What the Directive does not specify

• The document does not enumerate permit processes, alternate methods of compliance, or appeals. It also does not state penalties for non‑compliance, nor does it identify the approving authority for "later approved version" beyond the phrase itself. These absences mean that, in practice, operators must rely on CASA’s standard administrative processes or seek clarifying direction from CASA for matters not covered by the AD text.

The text of AD/RB211/46 does not set out any explicit penalties or fines for non‑compliance within the document itself. The instrument communicates compliance obligations and an effective date, but there is no penalties paragraph, no stated enforcement process, and no reference to specific sections of overarching statutes or criminal sanctions in the AD text provided.

Enforcement signals present in the document

• The Compliance requirement is unambiguous, stating that required actions must be completed "Before further flight after the effective date of this Directive." That phrasing converts the AD into an operational prerequisite: absence of compliance at the relevant time would, at minimum, render continued flight contrary to the written Directive.
• The AD is issued by CASA and signed by a named delegate, Mike Higgins. That administrative provenance indicates the requirement is an official CASA instrument, and CASA is the agency that would, under its general regulatory powers, monitor and enforce airworthiness compliance. The Directive itself does not, however, describe the enforcement mechanisms CASA will use.

What is not in the Directive text

• No specific enforcement mechanisms are described, such as suspension of certificates, directions to ground aircraft, administrative fines, or criminal penalties. The AD does not note inspections, audits, or reporting mechanisms that CASA will use to verify compliance.
• The AD does not specify an appeals or review process in respect of determinations of applicability, nor does it record how operators might seek alternative methods of compliance or approvals to deviate from the listed Service Bulletins.

Practical enforcement implications, drawn from what the AD says

• Because compliance is required "Before further flight," the most immediate enforcement lever is operational: an aircraft found to have an applicable SB outstanding after the effective date would be non‑compliant with the AD and therefore would not be in the condition for safe flight as prescribed by CASA. Operational personnel and inspectors can therefore prevent the aircraft from operating until compliance is demonstrably achieved.
• The AD’s acceptance of earlier accomplishment as satisfying the requirement gives operators a clear evidentiary route to avoid enforcement action, by producing maintenance records showing the SB work was already completed.

Limitations on analysis

• The Directive makes no express reference to monetary penalties or to any enforcement timetable beyond the effective date. The AD therefore provides the mandatory requirement and the temporal trigger for compliance, but leaves the enforcement modalities and sanctions to CASA’s broader regulatory framework, which is not articulated in this document.

The Directive expressly imports state‑of‑design action into the domestic airworthiness regime. The Background paragraph states that CASA "has reviewed state‑of‑design ADs applicable to RB211 engines and decided these UK ADs should be explicitly mandated for Australian aircraft." That statement reveals the interactional mechanism: CASA is adopting, or mandating, requirements that originally emanated from the state of design, in this case the UK CAA ADs shown in Table 1.

Interaction with state‑of‑design requirements

• Table 1 maps CAA AD identifiers to Rolls‑Royce Service Bulletin numbers and dates. The AD therefore functions to domesticate those state‑of‑design SBs/ADs by incorporating them into a CASA AD for Australian aircraft. Practically, this creates legal parity between the state‑of‑design directives and CASA’s domestic airworthiness rules for the affected aircraft/engines, at least with respect to the once‑only items listed.

Interaction with operator maintenance records and prior compliance

• The Requirement clause conditions mandatory work on whether the Service Bulletin "has not been previously accomplished." That creates an interaction with existing maintenance record regimes. Operators must be able to demonstrate prior accomplishment through their maintenance records to avoid repeating the prescribed actions. Thus the AD assumes the existence of recordkeeping practices and makes compliance contingent on those records.

Temporal interaction with elapsed compliance windows

• The Background expressly notes the actions were once‑only and that "the compliance date and/or period has passed." By mandating these once‑only actions now and setting an effective date, CASA is effectively imposing obligations on operators to complete work that was previously due. That creates a retroactive operational effect relative to the original SB dates in Table 1.

Permissible technical updates and interaction with SB revisions

• The Requirement permits performing the actions "at the nominated date or later approved version." This allows operators to comply using later versions of the Service Bulletins, provided those later versions are "approved." The AD therefore interacts with the process by which SB revisions are issued and approved, enabling the use of updated technical guidance rather than limiting compliance strictly to the historical edition listed.

Gaps and unspecified interactions

• The AD text does not spell out how CASA’s AD interacts with any broader statutory enforcement mechanisms, exemptions, or alternative means of compliance. It also does not specify the authority that approves later SB versions, nor does it provide processes for seeking exemptions or variations. Those gaps mean that interactions with broader regulatory instruments, such as approvals for alternative methods of compliance or enforcement procedures, are left to CASA’s ordinary administrative processes rather than being specified in the Directive.

In sum, the Directive operates by domestication of state‑of‑design requirements, reliance on maintenance records to determine prior accomplishment, and conditional acceptance of later SB revisions, while leaving enforcement modalities and approval processes for SB revisions to the wider CASA framework rather than the text of the AD itself.

The document provided, AD/RB211/46, contains no amendment or revision history within its text. The material records the following temporal metadata:

• Signature and date: Mike Higgins, Delegate of the Civil Aviation Safety Authority, signed the Directive on 25 May 2012.
• Effective date: The Directive "becomes effective on 8 June 2012," as stated in the Compliance paragraphs.
• Document label: The header includes the identifier AD/RB211/46, repeated headings, and the classification "State of Design Airworthiness Directives - 1" with a date marker "11/2012."

There is no separate "Amendments" or "Revision history" section in this AD that lists prior versions, supersessions or amendments. The Directive incorporates Rolls‑Royce Service Bulletins by reference in Table 1, and it permits the use of "later approved version[s]" of those Service Bulletins, but it does not itself record any past amendments to the AD text or provide a change log.

What the absence of an amendment history in the AD means operationally

• The operator should treat this document as the controlling CASA AD for the matters specified in Table 1, with the stated effective date. If CASA issues any subsequent amendments, cancellations or superseding ADs, those would appear in later instruments; however, such changes are not present in the text supplied here.
• Because the AD allows "later approved version[s]" of the Rolls‑Royce Service Bulletins to be used to satisfy the requirements, technical amendments or revisions to the SBs do not require amendment of this AD to be effective, provided the later versions are approved. The AD therefore anticipates technical evolution without itself being amended.

Administrative identifiers and repeated headings

• The supplied document repeats the AD number and title lines several times and shows the table of SB mappings. There is no indication within the text that an earlier CASA AD has been superseded, nor is there any signature recording a previous version. The solitary signature is dated 25 May 2012, which is the only provenance marker in the document.

Recommendation implicit in the document

• In the absence of an amendment history, affected parties must assume the AD in front of them is current as of the effective date, and must consult CASA or the CASA AD register for any later amendments or variations beyond 8 June 2012. The AD text itself does not make that cross‑reference, but the effective date and signature provide the necessary administrative anchors for determining contemporaneity.

The AD/RB211/46 text supplied does not contain any information about litigation, appeals, judicial review, enforcement actions, or disputes arising from this specific Directive. There are no references in the document to court decisions, tribunal outcomes, or examples of contested enforcement related to the AD.

What is in the document

• The AD contains administrative metadata, a Background statement explaining CASA’s decision to mandate state‑of‑design ADs for Australian aircraft because the actions are once‑only and the compliance dates had passed, a signed delegate name and date, and the substantive requirements and compliance timing. It does not mention legal proceedings.

Operational implications of the lack of litigation history in the text

• Absent any litigation history recorded in the Directive itself, operators and advisers must look to external records, such as CASA registers, court or tribunal databases, or agency correspondence, to learn whether the AD has been subject to legal challenge. The supplied instrument gives no indication that it has been litigated, nor does it provide procedural guidance about challenging CASA ADs.

What the AD does not say about dispute pathways

• The AD does not set out appeal rights, dispute resolution pathways or internal review procedures specific to this instrument. That silence does not necessarily indicate a lack of available remedies under broader administrative law, but those remedies fall outside the text of this Directive and are not documented here.

For practical purposes, stakeholders that require knowledge of any litigation history must consult CASA records or public judicial registries. The Directive itself supplies no litigation narrative, precedential citations, or references to contested cases.

The Directive contains several practical features and small textual elements that can create implementation traps if they are overlooked. These are drawn directly from the AD text and its structure.

Narrow and specific applicability

• The Applicability paragraph lists specific RB211‑524 subvariants and specifies installations on Boeing 747 and 767 aircraft "as specified in the requirement documents." The potential trap is assuming that all RB211 engines or all RB211‑524 engines are covered. Operators must confirm that their exact engine variant and installation are those referenced in the Service Bulletins or requirement documents, otherwise the AD’s obligations may not apply.

Record dependence for prior compliance

• Requirement 2 conditions action on whether the Service Bulletin "has not been previously accomplished." The operator therefore bears the evidential burden of proving prior accomplishment via maintenance records. Poor recordkeeping will not absolve an operator from needing to perform the SB actions, and the AD’s acceptance of prior accomplishment is only effective if demonstrable in records.

Once‑only actions with elapsed compliance windows

• The Background explicitly states these are "once‑only actions for which the compliance date and/or period has passed." This creates an immediate compliance pressure point: if an operator has not already done the once‑only action, it now must do it "before further flight after the effective date." Operators who relied on a past window and took no action will face an immediate operational requirement, which may necessitate unplanned maintenance.

"Later approved version" ambiguity

• The Requirement permits performing actions "at the nominated date or later approved version." The AD does not specify who grants approval for later versions, or by what process. Operators must ascertain which authority approves later versions, and ensure any later SB they rely on is properly approved. Failure to confirm approval may leave them non‑compliant despite performing the physical work.

Minimal technical detail in the AD itself

• Table 1 lists SB numbers, dates and terse titles, but does not reproduce the technical content of the Service Bulletins. The AD therefore requires operators to obtain and follow the full Rolls‑Royce Service Bulletins to understand the exact scope of work, parts, and procedures. Assuming the terse Table 1 titles suffice is a practical error.

Strict temporal compliance phrasing

• The Compliance clause requires action "Before further flight after the effective date of this Directive." The effective date is 8 June 2012. That language creates a cliff: if the SB work has not been done and is required, the aircraft cannot legally undertake further flight without compliance. Operators must plan to have the work completed by that date or rely on proof of prior completion.

Discrepancies and typographical artifacts in the table

• The table as supplied contains minor typographical artifacts, for example a split date "9 Oct 1992" appears broken in fragments across HTML spans in the source, and headings are repeated. Care must be taken when reading the table to ensure correct SB numbers and dates are recorded, rather than importing typographical errors. Rely on the SB identifiers (72‑6847, 71‑9546, 72‑9764) rather than a potentially garbled date string.

No penalties or remediation pathways in the AD text

• The AD does not specify penalties or an explicit remediation process for non‑compliance. Operators should not assume the absence of specified penalties means non‑enforcement; it means the AD delegates enforcement and sanction detail to CASA’s broader regulatory framework, which is not spelled out in this instrument.

Administrative timing mismatch

• The AD is signed 25 May 2012 but becomes effective 8 June 2012. Operators need to note this window when arranging work or seeking guidance. The two‑week gap may be insufficient for planning major maintenance if the SB work is extensive.

Use of "requirement documents"

• The Applicability refers to engines "installed in Boeing 747 and 767 as specified in the requirement documents." The AD does not itself include the full requirement documents. Operators must locate those requirement documents to understand the precise installation scope, rather than relying on the terse Applicability statement alone.

The Directive sets out a compact compliance path. Below is a stepwise, source‑grounded checklist based solely on the AD text, together with practical tasks implied by the language of the Directive.

1. Identify affected aircraft and engines

   • Confirm whether your fleet contains RB211‑524 engines of variants B2, C2, D4, G2, H or H‑36 installed in Boeing 747 or Boeing 767 airframes, as the Applicability clause states. Because the AD refers to "requirement documents" for installation specifics, retrieve the relevant Service Bulletins and state‑of‑design ADs cited in Table 1 to check installation applicability.

2. Obtain the listed Service Bulletins and CAA AD references

   • Table 1 provides the Rolls‑Royce SB numbers and brief titles:
     • R‑R SB 72‑6847, dated 24 Feb 1989, "Engine - IP and LP Compressor Location Bearings" (CAA AD G‑012‑05‑84).
     • R‑R SB 71‑9546, dated 9 Oct 1992, "Power Plant - Engine Front Mount" (CAA AD G‑003‑07‑92).
     • R‑R SB 72‑9764, dated 23 Jan 1998, "Engine - Combustion Section" (CAA AD G‑009‑01‑98).
   • Obtain the full text of each Rolls‑Royce Service Bulletin and the corresponding state‑of‑design ADs to determine the precise tasks, parts, and procedures required.

3. Determine applicability of each Service Bulletin to each engine/installation

   • Perform the duty mandated in Requirement 1: "Determine the applicability of the Rolls‑Royce Service Bulletin(s) listed in Table 1." This requires reviewing the SB applicability paragraphs, configuration tables, and serial number ranges, and comparing them to each engine and aircraft installation in your custody.

4. Check maintenance records for prior accomplishment

   • For each SB determined to be applicable, check whether the SB actions "has been previously accomplished." The AD explicitly conditions action on prior accomplishment, so documentary proof that the SB work was previously done will satisfy the AD without further physical work. Ensure maintenance records are complete, dated, and signed by authorised personnel.

5. If an SB is applicable and not previously accomplished, plan and perform the SB actions

   • Requirement 2 mandates that where a listed SB is applicable and not previously accomplished, the operator must "perform the actions required by that Service Bulletin at the nominated date or later approved version." Plan maintenance tasks in accordance with the SB and the nominated compliance details, or obtain and use a later approved version where appropriate.
   • Ensure performance is carried out by appropriately authorised maintenance organisations or personnel and in accordance with the technical procedures and parts lists in the SB.

6. Confirm approval for later SB versions if used

   • If you intend to comply using a later revision of a listed Service Bulletin, confirm that the later version is an "approved version" as permitted by the Requirement clause. The AD does not specify the approving authority; obtain written confirmation of approval from the relevant authority before relying on a later SB version to demonstrate compliance.

7. Complete the work before further flight after the effective date

   • The Compliance clause is explicit: required actions must be completed "Before further flight after the effective date of this Directive," with the AD’s effective date being 8 June 2012. Ensure that, if the SB actions are outstanding as of the effective date, they are completed and recorded prior to any subsequent flight of the affected aircraft.

8. Document actions clearly in maintenance records

   • Record the SB reference number, SB revision or version used, date of accomplishment, personnel and organisation performing the work, and any parts installed. Where prior accomplishment is relied upon, ensure the prior record is available and legible to demonstrate compliance.

9. Retain and make available records for inspection

   • Although the AD does not specify an inspection regime, CASA’s authority to mandate the AD implies that operators must be able to demonstrate compliance to regulatory inspectors. Retain records in accordance with normal airworthiness recordkeeping practices and make them available to CASA upon request.

10. If uncertain, contact CASA for clarification

• The AD does not set out appeal or alternative compliance procedures. If there is ambiguity around applicability, approval of later SB versions, or the sufficiency of prior records, seek clarification from CASA. The AD is signed by a CASA delegate, and CASA is the body that has mandated the AD; operators should use CASA channels for questions about interpretation or for seeking approval for alternatives.

Practical checklist summary tied to the AD text

• Retrieve Table 1 SBs and read full SBs (Table 1).
• Verify engine model/installation against SB applicability language (Applicability; Requirement 1).
• Check maintenance records for prior completion (Requirement 2).
• If not previously accomplished and applicable, perform SB actions per SB or later approved version (Requirement 2).
• Complete and document work before further flight after 8 June 2012 (Compliance).
• Keep records demonstrating prior accomplishment or completion under this AD (Requirement 2; Compliance).

The Directive itself is compact, but compliance requires accessing the full Rolls‑Royce Service Bulletins and any state‑of‑design ADs referenced, and ensuring that later SB revisions used for compliance are approved. The AD provides the mandatory obligation and the temporal trigger, while technical execution and recordkeeping are left to operators and maintenance organisations following the SB content.