AD/B747/168 Amdt 3 - Engine Pylon Aft Torque Bulkhead

The AD is built on a small number of discrete concepts stated in the source text and by reference to external documents. The primary concepts and the text in which they appear are:

• Applicability by reference: The AD uses Boeing Alert Service Bulletin 747-54A2184, Revision 1, dated 6 May 1999, to define the set of affected aeroplanes. The AD's Applicability entry reads: "Model 747 series aircraft, as listed in Groups 1, 2, and 5 of Boeing Alert Service Bulletin (ASB) 747-54A2184, Revision 1, dated 6 May 1999." This means the AD does not list individual serial numbers in-line; the ASB is the operative list for which serial numbers or groups are included.

• Incorporation by reference of foreign regulator action: The Requirement states: "Action in accordance with the technical requirements of FAA AD 2000-12-16 Amdt 39-11794." The AD therefore imports the FAA AD's technical inspection criteria, corrective actions and any terminating action that the FAA AD specifies. The AD document itself does not restate those technical steps.

• Compliance timing: The Compliance field points to a revised effective date for the Requirement document, stating that compliance is "as specified in the Requirement document with a revised effective date of 7 September 2000" and that "The compliance remains unchanged by issue of the Directive." Separately, the AD notes its own issuance effectivity as 30 July 2009. Both dates are captured in the AD text.

• Safety hazard identified: The Background section recounts factual reports the FAA received: two reports of cracking of the aft torque bulkhead at the number 1 and number 2 engine pylons on a Boeing model 747-200F series aircraft powered by Rolls-Royce RB211 series engines. The hazard summarised in the Background is that "Cracking of the aft torque bulkhead at the engine pylons, if not detected and corrected in a timely manner, could result in failure of a pylon and consequent separation of the engine from the wing."

• Amendment history as mechanism: The Background summarises the evolution of the AD through Amendments 1-3. It identifies drivers for amendments (new cracking reports, availability of new service instructions), changes made (expanded applicability, removal of certain aircraft, introduction of a new terminating action), and administrative correction (Amendment 3 corrected the issue date of the Boeing ASB). These are presented as the reasons for successive ADs.

These concepts structure how the instrument operates: the AD compels operators of the specifically referenced aircraft to follow a foreign regulator's AD and a manufacturer ASB for the detailed technical requirements, dates for compliance are set by reference, and the AD is grounded in reported fatigue cracking risks that could lead to pylon failure.

The text identifies a narrowly defined class of affected parties. The Applicability provision states the instrument applies to "Model 747 series aircraft, as listed in Groups 1, 2, and 5 of Boeing Alert Service Bulletin (ASB) 747-54A2184, Revision 1, dated 6 May 1999." Therefore the direct, named obligation falls on the operators and owners of those specific Boeing 747 airframes that the ASB groups include. Because the AD imports the "technical requirements of FAA AD 2000-12-16 Amdt 39-11794," any person responsible for maintenance, airworthiness, and continued operation of those aeroplanes must follow the FAA AD requirements as the CASA instrument requires.

Maintenance organisations, licensed engineers, and providers of inspection and repair services to those operators are implicated indirectly because they will supply the inspections, non-destructive testing, repairs or terminating actions referenced by the FAA AD. The Background explicitly references a 747-200F series aircraft powered by Rolls-Royce RB211 series engines as the model in which initial cracking reports were made, so operators of similarly configured aircraft (for example, those with RB211 engines) would need to check ASB Group listing to confirm applicability. However the AD as issued does not limit applicability to engines or subtypes beyond the ASB groupings; the ASB itself governs the granular bounds.

Regulatory and administrative actors are also involved: the AD is issued under the authority of the Civil Aviation Safety Authority (CASA), signed by a CASA delegate, David Villiers. The AD does not set out other stakeholders such as lessors, insurers or airworthiness authorities in other jurisdictions; their involvement would follow from contractual or regulatory relationships, not from explicit text in this AD.

Finally, since the AD incorporates FAA AD 2000-12-16, the FAA and Boeing are functional actors: the FAA AD provides the technical remediation steps and Boeing ASB provides the aircraft groupings and service instructions that determine whether an aeroplane falls within the AD. Those external documents are referred to concretely in the AD text.

The AD sets a single, clear duty: perform the actions specified in the referenced FAA AD for the aeroplanes identified by the referenced Boeing ASB. The Requirement provision states: "Action in accordance with the technical requirements of FAA AD 2000-12-16 Amdt 39-11794." The Compliance provision then frames the timing relationship, stating that compliance is "as specified in the Requirement document with a revised effective date of 7 September 2000" and that "The compliance remains unchanged by issue of the Directive." The AD itself becomes effective on 30 July 2009.

From the text the primary duties are:

• Determine applicability by cross-referencing Boeing ASB 747-54A2184 Rev 1 (6 May 1999), specifically Groups 1, 2 and 5. The AD’s Applicability entry is the operative starting point.

• For those aeroplanes that fall within those ASB groups, carry out the technical actions required by FAA AD 2000-12-16 Amdt 39-11794, observing any timing and inspection intervals set out in that FAA AD.

• Follow the Compliance timing as specified by the FAA AD subject to the revised effective date noted in the Compliance entry.

The AD text does not enumerate exemptions, alternative means of compliance, approval pathways or rights of review. The Background notes that Amendment 2 "required accomplishment of a new terminating action," which implies that the FAA AD (as adopted) may contain a terminating action that, once accomplished, changes ongoing inspection obligations. The AD document itself does not specify the nature of the terminating action, any acceptance criteria, or whether CASA accepts alternative procedures; those details are left to the FAA AD and the Boeing ASB as cited.

The AD does not articulate procedural rights such as review, appeal or waiver within its text. It does identify the issue and effective dates and records the issuing delegate and date, which provides administrative context for the AD but not statutory procedural routes. Any rights to seek alternative compliance or relief would need to be located in CASA regulations or administrative processes outside the four corners of this AD; they are not described in the source text.

The AD document as supplied does not include any express penalty or enforcement clause. It records that the Directive is issued by the Civil Aviation Safety Authority (delegate David Villiers) on 18 June 2009 and that the Amendment becomes effective on 30 July 2009. Beyond recording the authority and effective date, the AD does not state specific sanctions, fines, suspension prospects, or enforcement mechanisms.

Because the AD is an instrument issued by a national civil aviation authority and it incorporates an FAA AD's technical requirements, the document creates an operational airworthiness obligation for the identified aeroplanes. However the AD text itself gives no procedural description of how CASA will monitor compliance, what corrective actions CASA could mandate beyond the FAA AD's technical remedies, how CASA will record compliance, or what penalties would be applied for non-compliance. The AD likewise contains no administrative guidance about enforcement processes, audit frequency, or certification consequences.

The only enforcement-related material present in the source is the formal signature block: "David Villiers, Delegate of the Civil Aviation Safety Authority" with date "18 June 2009." That identifies the issuing authority but does not enumerate enforcement steps. Therefore, from the supplied instrument alone, one must conclude that the AD specifies required technical action and effective dates, but leaves enforcement details unspecified in the AD text. Any statutory penalties or enforcement pathways would be found in CASA’s governing statutes, regulations, or enforcement policies rather than in this AD as presented.

This AD operates by explicit cross-reference to other regulatory and manufacturer documents. The AD makes clear that CASA's requirement is to "Action in accordance with the technical requirements of FAA AD 2000-12-16 Amdt 39-11794." That means the FAA AD is incorporated functionally as the source of the technical compliance pathway. The AD also relies on Boeing Alert Service Bulletin 747-54A2184, Revision 1, dated 6 May 1999, to determine which aeroplanes are affected by the CASA directive, through the Applicability clause. The Background references changes that resulted from Boeing service instructions and FAA actions.

These references create two direct interactions:

• Imported technical standard: The CASA AD defers to the FAA AD to define inspections, corrective action and any terminating action. Practically, that makes compliance with the FAA AD the means of satisfying CASA’s directive for the listed aeroplanes. The AD’s Compliance clause further ties effective timing to a revised date for the Requirement document.

• Manufacturer service bulletin as determinative of scope: By listing the ASB and specific revision and date, CASA uses the manufacturer’s grouping and service instructions to define affected aircraft. The AD notes that Amendment 3 "is issued to correct the issue date of the related Boeing ASB," indicating the accuracy of the ASB reference is material to the AD’s operation.

No other statutory instruments, regulations, or jurisdictional conflicts are mentioned in the source text. The AD does not discuss interaction with leasing contracts, insurance policies, or civil liability regimes. The document likewise does not state whether compliance with the FAA AD and Boeing ASB creates any presumption of compliance with other CASA requirements or whether operators must obtain CASA approval for any repair or terminating action. Any such interactions must be inferred from the broader CASA regulatory framework; they are not articulated in the supplied text.

In sum, the AD interacts explicitly with the FAA AD and Boeing ASB by incorporation. Other legal interactions that typically arise in airworthiness contexts (for example, continuing airworthiness recordkeeping obligations, approved maintenance organisation roles, or enforcement procedures) are not specified in this AD text and would be located in separate CASA instruments or regulations.

The AD text itself records an amendment history in the Background paragraph. Those recorded steps are the only amendment-related information present in the supplied text:

• Original AD and Amendment 1: The Background states the FAA initially received two reports of aft torque bulkhead cracking at engine pylons on a Boeing 747-200F with Rolls-Royce RB211 engines. It says "Amendment 1 was prompted by a report of cracking found in the aft torque bulkheads of the outboard nacelle struts, and by the availability of new service instructions for detecting fatigue cracking." That indicates Amendment 1 broadened the response to include outboard nacelle strut bulkheads and adjusted the detection procedures in light of new service instructions.

• Amendment 2: The Background records that "Amendment 2 expanded applicability to include additional aircraft while removing certain other aircraft from applicability. This amendment also required accomplishment of a new terminating action." This describes a change to the set of aircraft covered and introduction of a terminating action as a modification or repair option intended to end ongoing inspection requirements. The AD does not record which specific aircraft were added or removed, nor does it define the terminating action; those specifics are left to the referenced FAA AD and Boeing ASB.

• Amendment 3 (this instrument): The AD states that "Amendment 3 is issued to correct the issue date of the related Boeing ASB." This Amendment 3 is administrative in nature, correcting the issue date of the related Boeing ASB, and it becomes effective on 30 July 2009. The AD carries the signatory block and date 18 June 2009, which records the date of the delegation signature.

Additionally, the Compliance field records that the Requirement document has "a revised effective date of 7 September 2000" and that "The compliance remains unchanged by issue of the Directive." That suggests that earlier material established a separate effective date for the FAA AD or related actions and that this AD maintains that compliance schedule. The AD does not show incremental revision texts, tracked amendments or redlines, nor does it reproduce previous AD versions. It summarises the drivers for amendment activity (reports of additional cracking, availability of revised service instructions) and the administrative correction made in Amendment 3.

Anyone relying on this AD should therefore consult the referenced FAA AD and Boeing ASB for the detailed amendment chronology, the exact content of prior amendments, and the precise technical and scope changes introduced by Amendment 1 and Amendment 2, because the AD text here provides an explanatory summary but not the full amendment documents.

The supplied AD contains no litigation history. It does not reference any court decisions, administrative appeals, or adjudicated disputes. The Background and other fields describe factual bases for action (reports of cracking, service instruction availability) and administrative amendment rationales, but they do not mention any legal challenges, stays, reconsiderations, or precedential rulings.

Therefore, from the text provided, there is no record within this AD of:

• Judicial challenges to the AD or to any prior or subsequent amendment.
• Administrative appeals lodged against the AD in CASA or elsewhere.
• Enforcement actions, penalties imposed, or remedial orders issued as a result of non-compliance.
• Any case law that interprets the scope, validity, or application of this AD.

If a practitioner needs to understand whether this AD has been subject to legal challenge or applied in contested proceedings, that information will not be found in the AD itself and must be sourced from external legal databases, CASA enforcement records, or court registries. The AD as presented records only the factual and administrative rationale for the directive and its effective dates.

The AD contains several points that can cause confusion or operational risk if they are overlooked. These are facts taken directly from the text and implications that flow from those facts as stated.

• Applicability via external document and grouped lists: The AD does not list individual serial numbers. Instead it ties applicability to "Groups 1, 2, and 5 of Boeing Alert Service Bulletin (ASB) 747-54A2184, Revision 1, dated 6 May 1999." The practical consequence is that an operator must obtain that exact ASB revision to determine whether their aeroplane sits in one of those groups. Use of the wrong ASB revision or an inexact group listing could lead to mistaken non-compliance.

• Incorporation of a foreign AD: The Requirement imports FAA AD 2000-12-16 Amdt 39-11794 by reference. Practitioners must obtain that FAA AD text to know inspection intervals, methods, and corrective measures. The CASA AD does not reproduce or summarise the technical steps, so failure to consult the FAA AD risks omission of required inspections or missing a terminating action.

• Multiple effective dates: The Compliance field states: "As specified in the Requirement document with a revised effective date of7 September 2000. The compliance remains unchanged by issue of the Directive." The AD itself is effective on 30 July 2009. That creates a small, potentially confusing temporal framework: the technical Requirement document has an earlier revised effective date (7 September 2000) while this Amendment is issued and effective in 2009. Practitioners must follow the compliance timing set out in the FAA AD (as modified by the revised effective date) rather than assuming the CASA AD’s own issuance date governs initial compliance timing.

• Amendment 2's scope changes and terminating action: The Background notes Amendment 2 "expanded applicability to include additional aircraft while removing certain other aircraft from applicability" and "required accomplishment of a new terminating action." The AD does not state which aircraft were added or removed, or what the terminating action comprises. Operators who were removed from applicability may nonetheless be uncertain about their status unless they cross-check the ASB and FAA AD; operators who may benefit from a terminating action must identify the relevant FAA AD text to determine whether they can rely on it.

• Narrow factual basis for the safety hazard: The Background records that initial cracking reports were from a 747-200F with Rolls-Royce RB211 engines. While the AD applies to aircraft listed in the ASB groups cited, if an operator assumes the risk only applies to RB211-powered aircraft they may misread the scope. The AD’s applicability is the governing criterion.

• Administrative correction: Amendment 3 is expressly "issued to correct the issue date of the related Boeing ASB." While this appears administrative, using the wrong ASB issue date may lead to misidentifying affected aircraft and missing required actions.

• No enforcement or compliance process described in-document: The AD gives the obligation but does not set out CASA’s enforcement pathway, record-keeping expectations, or documentation to be filed. Operators should not assume that fulfilling the FAA AD alone suffices for all administrative reporting obligations in CASA; the AD text does not address that procedural intersection.

• Reliance on external documents: All detailed obligations, intervals, and the nature of terminating actions are located in the FAA AD and Boeing ASB, not in this AD. Missing or outdated versions of those documents are a practical risk.

Addressing these gotchas requires deliberately fetching and verifying the precise ASB revision and the text of FAA AD 2000-12-16 Amdt 39-11794, confirming whether a terminating action applies to a particular aeroplane and ensuring timing obligations are observed in accordance with the revised effective date noted in the Compliance field.

The AD prescribes a clear compliance pathway by reference. To comply with AD/B747/168 Amdt 3 as recorded in the supplied text, perform the following steps, grounded only in the AD’s stated requirements:

1. Confirm applicability: Obtain Boeing Alert Service Bulletin 747-54A2184, Revision 1, dated 6 May 1999, and determine whether the aeroplane in question is listed in Groups 1, 2, or 5. The AD’s Applicability clause makes this ASB the definitive source for whether the aeroplane is covered.

2. Obtain the FAA AD text: Retrieve FAA AD 2000-12-16 Amdt 39-11794. The AD’s Requirement clause makes the FAA AD’s "technical requirements" the mandatory steps to be followed. The FAA AD will contain the detailed inspection procedures, inspection intervals, non-destructive testing methods, any required repairs, and any specified terminating action.

3. Observe timing references: Note the Compliance clause which says compliance is "as specified in the Requirement document with a revised effective date of 7 September 2000." Confirm the timing and deadlines in the FAA AD and treat the revised effective date as authoritative for scheduling those actions, because the CASA AD states the compliance schedule remains unchanged by the issuance of this Directive. Also record that this AD became effective on 30 July 2009.

4. Perform required work and document it: Carry out inspections, repairs or terminating actions exactly as set out in the FAA AD (and any Boeing service information that the FAA AD references). Maintain airworthiness records documenting the inspections, findings, remedial steps and any terminating action accomplished, consistent with standard continuing airworthiness recordkeeping practice. While the CASA AD does not set out record formats, the AD’s authority implies the operator must be able to demonstrate compliance; therefore contemporaneous, traceable records keyed to the FAA AD actions are prudent.

5. If in doubt, use the FAA AD and ASB as the controlling technical and scope sources: Because this CASA AD does not reproduce technical methods, do not attempt to substitute an alternative procedure without confirmation that such an alternative is accepted by the FAA AD or by CASA in accordance with its administrative processes. The AD itself contains no statement of alternative acceptability or CASA-approved equivalent procedures.

6. Monitor for further amendments: The Background summarises prior amendments and states Amendment 3 corrects the issue date of the Boeing ASB. Operators should monitor CASA, FAA and Boeing communications for any additional amendments that could change applicability, inspection intervals or terminating action requirements.

These steps follow directly from the AD’s text. The AD does not provide procedural guidance for how to seek a formal alternative means of compliance or to request relief; such processes, if available, would be contained in CASA’s broader regulatory framework rather than in this AD. Practically, compliance will require coordination between the aircraft operator, maintenance organisation and any approved design or engineering authority responsible for carrying out the FAA AD’s technical instructions.