AD/B747/34 Amdt 4 - Supplemental Structural Inspection Program

The instrument explicitly affects owners and operators of the listed Boeing 747 models because the Applicability section names the model series subject to the Requirement: 747-100, -100B, -100B SUD, -200B, -200C, -200F, -300, -400, -400D, -400F, 747SR, and 747SP series aircraft. Anyone responsible for the airworthiness of those registered aeroplanes within the regulator’s jurisdiction will therefore be directly affected because the AD imposes a mandatory action requirement (Requirement; Compliance).

Indirectly affected parties include maintenance organisations and technical personnel who must plan and perform the inspections and any follow-on corrective actions mandated in the FAA AD that this instrument adopts by reference. The Background indicates the action is framed around the Supplemental Structural Inspection Document (SSID): the SSID “has been produced to ensure the continued structural integrity of older Model 747 aircraft,” and Amendment 3 “required additional and expanded inspections, and expanded applicability” (Background). That signals that maintenance programmes for older airframes and any contract maintenance providers engaged by operators will need to incorporate those inspection tasks if the operator’s aeroplane is within scope.

Regulatory decision-makers are affected insofar as the AD aligns domestic requirements with the FAA AD; the instrument was issued by a delegate of the Civil Aviation Safety Authority (Background). The instrument does not specify crew, passenger, or third-party obligations; its purpose relates to continuing structural integrity, and the named audience in practical terms will be airworthiness managers, operators, maintenance control, and possibly leasing/asset managers who must ensure regulatory compliance.

Those who may believe their aircraft are not covered should note Amendment 4’s stated rationale: a revision to the related FAA AD clarified applicability because “certain new variants that have not yet been certified would have been subject” without the clarification (Background). That indicates a particular risk for owners/operators of variants near certification boundaries to reassess applicability in light of the clarified FAA AD. The instrument itself requires an operator to determine whether their specific aircraft falls within the listed models and then to comply with the referenced Requirement document.

Duties imposed by the instrument are expressed succinctly and are primarily procedural: perform the action “in accordance with the technical requirements of FAA AD 2004-07-22 R1 Amdt 39-15326” (Requirement). The Compliance line states adherence must be “As specified in the Requirement document.” Those two clauses together create the operative duty: where an aircraft is within the Applicability list, the responsible party must carry out the inspections, intervals and corrective actions described by the FAA AD referenced.

The instrument does not contain detail within its text about the exact inspection items, intervals, or corrective measures. Therefore the duty’s content and the timing obligations are functions of the FAA AD text that is incorporated by reference. Practically, this creates two immediate obligations for a responsible person: (1) to identify whether a particular aeroplane falls within Applicability, and (2) to obtain and follow the FAA AD/Requirement document to implement the technical tasks and compliance schedule required.

Rights are not expressed in the instrument. The text does not state processes for requesting alternative means of compliance, seeking exemptions, appealing the AD, or varying compliance timelines. The instrument likewise does not spell out a right to relief or transitional arrangements beyond the single effective date. Because the instrument relies on the FAA AD for technical detail, any procedural rights set out within that FAA AD (appeal mechanisms, AMOCs, or equivalent means of compliance) are not recited here; the Australian AD simply directs action in accordance with that FAA AD (Requirement). The Background’s account of earlier amendments implies an evolving requirement: Amendment 2 “introduced the latest revision of the Requirement document” and Amendment 3 “required additional and expanded inspections, and expanded applicability,” so operators must track amendments (Background).

Decision-making authority in the instrument is vested in CASA via a delegate who issued the AD (Background). The instrument makes clear who decides that action is required and the effective date. The instrument does not contain a discrete administrative process for dispute or for CASA to issue individual exemptions; none of those rights or processes appear in the text provided.

The text of this AD does not specify penalties, sanctions, or enforcement procedures. The AD records an obligation (perform the action in accordance with the referenced FAA AD) and an effective date (13 March 2008), and it is signed by a delegate of the Civil Aviation Safety Authority (Background; Compliance). However, the instrument itself contains no statement of fines, suspension, revocation of certificates, or other disciplinary measures.

Because the AD incorporates the FAA AD’s technical requirements and schedules, compliance obligations are defined by that referenced document; the domestic AD requires action “as specified in the Requirement document” (Requirement; Compliance). What this AD does, therefore, is place a mandatory technical requirement on the listed aircraft by reference, rather than enumerating enforcement mechanisms in the AD text.

Practitioners should note that absence of penalty language in the AD does not mean there are no enforcement consequences under Australia’s broader civil aviation regulatory regime, but the AD itself makes no such references. The AD identifies CASA as the issuer via a delegate, which establishes regulatory provenance (Background). For anyone concerned about enforcement, the procedural and sanctioning framework that would apply in case of non-compliance is not set out in this instrument; it would be necessary to consult the broader statutory and regulatory framework administered by CASA and any domestic enforcement policies or instruments outside this AD to identify the specific penalties or administrative actions that could flow from failure to comply.

In short, this document imposes a mandatory technical duty by reference and sets an effective date, but it does not enumerate penalties or the enforcement process within the instrument’s text.

This AD interacts directly with at least one foreign regulatory instrument by reference: FAA AD 2004-07-22 R1 Amdt 39-15326. The Requirement clause explicitly directs action “in accordance with the technical requirements of FAA AD 2004-07-22 R1 Amdt 39-15326.” That means the domestic AD incorporates or imports the FAA AD’s technical tasks, schedules and corrective actions for the specified Model 747 aircraft. The Background further explains that Amendment 4 is issued “in response to a revision of the related FAA AD, which clarifies the applicability of the existing AD” (Background). Mechanically, the AD aligns domestic obligations with the current posture of the FAA AD on which it relies.

Within the text provided there are no express references to other Australian statutes, regulations, or directorates. The instrument is issued by a delegate of the Civil Aviation Safety Authority, which situates it within the administrative authority of CASA (Background). Nevertheless, the AD’s legal effect in Australia depends on whatever statutory/regulatory powers empower CASA and delegate action; those statutory sources are not reproduced in this document and are not stated in the text provided.

The AD also references the Supplemental Structural Inspection Document (SSID) in the Background as the technical document produced to ensure structural integrity of older Model 747 aircraft and as the basis for follow-on action to maintain fleet airworthiness (Background). The AD’s inspection mandate therefore ties into the SSID’s technical programme. The text indicates that previous amendments updated the Requirement document and inspection scope (Amendment 2 and Amendment 3), and Amendment 4 was prompted by a clarifying FAA revision. This shows an interaction chain: SSID and FAA AD -> domestic AD via incorporation -> operator obligations.

Because the AD incorporates an FAA AD, operators and maintainers must work with a foreign technical standard as the instrument’s substantive source. The AD does not state how conflicts between the FAA AD and any domestic technical standards are to be resolved; the instrument simply requires compliance with the FAA AD’s technical requirements for the named models. Practitioners should therefore treat the FAA AD and the SSID as primary technical sources referenced by this domestic instrument.

The document itself is labelled AD/B747/34 Amendment 4 (Amdt 4) and displays the date 3/2008. The Background paragraph provides a concise chronology of prior amendment activity relevant to the Requirement document:

• Amendment 2: “introduced the latest revision of the Requirement document.” The text does not specify the date of Amendment 2 or the content of the revision, only that Amendment 2 updated the Requirement document to a new revision.

• Amendment 3: “required additional and expanded inspections, and expanded applicability to include additional aircraft.” That indicates Amendment 3 materially broadened the inspection programme and the class of aircraft subject to the AD, though the AD text does not enumerate which additional inspections or which additional aircraft were added.

• Amendment 4 (this instrument): “is issued in response to a revision of the related FAA AD, which clarifies the applicability of the existing AD by specifying which Model 747 aircraft are affected, because certain new variants that have not yet been certified would have been subject to the requirements of this Directive.” Amendment 4 therefore responds to an FAA clarification to refine applicability, and the Compliance paragraph states: “This Amendment becomes effective on 13 March 2008.”

From the information provided, at least four amendment stages have occurred (the original AD and Amendments 1 through 4, implicitly). The Background shows an iterative approach: initial SSID-based requirement, then revisions to the Requirement document (Amendment 2), then expansion of inspections and applicability (Amendment 3), and then a clarification-driven realignment with a revised FAA AD (Amendment 4). The AD’s title line, table header rows and the repeated headings indicate the document’s administrative identity and that Amendment 4 is the operative iteration as of the stated effective date.

The instrument does not provide dates for Amendment 2 or Amendment 3, nor does it include the text of prior amendments. It also does not supply a revision history log beyond the summary sentences in the Background. To reconstruct the full legislative or directive timeline (dates, textual diffs, which additional aircraft were added, or the specific inspection tasks introduced at Amendment 3), a practitioner must obtain the referenced Requirement document and any prior AD amendment texts; the domestic AD itself directs the reader to that Requirement document for technical content.

The text of this AD contains no reference to litigation, court decisions, judicial review, or administrative appeals. It does not report any judicial challenges to the AD or to earlier amendments, nor does it reference legal precedent or litigation outcomes. The Background is focused on technical rationale and amendment triggers rather than legal contestation.

Accordingly, within the instrument there is no recorded litigation history to analyse. The AD is a regulatory directive issued by a CASA delegate and framed around technical compliance by reference to an FAA AD and the SSID; any litigation or dispute records would not appear in this document unless specifically noted. For those seeking litigation history or judicial interpretation relevant to this AD, the provided text does not supply that material and therefore external sources would need to be consulted.

It is also notable that the instrument supplies only the AD text and a short background; it does not reproduce correspondence, enforcement records, or appeals associated with prior amendments. The absence of litigation references in the AD does not imply that none exist in practice, but it does mean the instrument itself contains no litigation narrative or case citations.

The AD includes several practical features that can produce traps for the unwary if a compliance exercise relies solely on this document:

• Incorporation by reference of an external document: The AD does not reproduce the FAA AD’s technical content; it directs action “in accordance with the technical requirements of FAA AD 2004-07-22 R1 Amdt 39-15326” and states compliance is “As specified in the Requirement document” (Requirement; Compliance). Anyone who assumes this AD alone contains the full compliance detail will miss inspection tasks, intervals, and corrective actions. The actionable obligations reside in the FAA AD/Requirement document, which must be obtained and read.

• Applicability clarification risk: Amendment 4 was prompted because the revised FAA AD “clarifies the applicability of the existing AD by specifying which Model 747 aircraft are affected, because certain new variants that have not yet been certified would have been subject to the requirements of this Directive” (Background). That indicates a specific gotcha: aircraft variants near certification/variant boundaries may have ambiguous applicability unless the FAA AD’s clarified language is checked. Operators of less common or newly developed variants need to verify whether their variant is included.

• Prior amendment changes: Amendment 3 expanded inspections and applicability. If an operator used an old compliance programme based on an earlier iteration of the AD, that programme may be insufficient,prior amendments materially changed scope (Background). Relying on memories or outdated maintenance manuals without checking the latest FAA AD/Requirement document risks non-compliance.

• Effective date lag: The AD bears a signature date of 30 January 2008 but states the Amendment becomes effective on 13 March 2008 (Background; Compliance). Practitioners must note the effective date for scheduling compliance tasks and not assume immediate effect on the signature date.

• No enforcement detail in text: The AD contains no penalties or enforcement provisions. That absence can mislead those seeking assurance about administrative consequences; the AD creates the technical duty but leaves enforcement detail unstated (Penalties and enforcement). Operators should not infer procedural rights or enforcement pathways from silence in the AD.

• SSID as underlying technical basis: The Background says the Supplemental Structural Inspection Document has been produced “to ensure the continued structural integrity of older Model 747 aircraft” and that follow-on action aims to maintain fleet airworthiness (Background). Where an operator’s structural inspection programmes differ from the SSID, they must reconcile those differences with the Requirement document and any domestic maintenance obligations.

• Multiple document sources to reconcile: The AD ties domestic obligation to a foreign AD and an SSID. Practically, that requires cross-referencing three sources (this AD, the FAA AD, and the SSID) to form a complete compliance picture. Absent a single consolidated domestic manual reproduction, there is room for misinterpretation.

In short, the main practical hazards are omission of the technical content in the domestic AD, potential ambiguity over variant applicability (which was the reason for Amendment 4), and the need to reconcile prior amendment changes with current obligations.

The AD prescribes compliance by reference. A practical compliance route, grounded in the instrument’s text, would include the following steps:

1. Confirm Applicability: Check whether the aeroplane’s model appears in the Applicability list (747-100, -100B, -100B SUD, -200B, -200C, -200F, -300, -400, -400D, -400F, 747SR, and 747SP series aircraft). If the aircraft is one of the listed models, proceed; if not, document the determination and retain records of the applicability assessment (Applicability).

2. Obtain the Requirement document: Acquire a copy of FAA AD 2004-07-22 R1 Amdt 39-15326 and any related service bulletins or Supplemental Structural Inspection Document references that the FAA AD mandates. The AD explicitly requires action “in accordance with the technical requirements” of the FAA AD and states compliance is “As specified in the Requirement document”, so the FAA AD is the operative source for inspection tasks, intervals and corrective actions (Requirement; Compliance).

3. Identify applicable tasks and intervals: From the FAA AD/Requirement document, extract the specific inspection items, repetitive intervals, threshold times, and any specified non-destructive testing, follow-on inspections, or required structural repairs.

4. Integrate into maintenance planning: Update the operator’s maintenance control or continuing airworthiness management documentation to reflect the inspection schedule from the FAA AD, ensure maintenance engineers have the necessary procedures and access to any referenced SSID material, and allocate resources (man-hours, specialised inspection tools, NDT capability) consistent with the inspection requirements. The Background indicates the SSID underpins the structural inspection programme, so ensure that the SSID tasks are available to personnel (Background).

5. Record compliance actions: Record completed inspections and any corrective actions in the aircraft maintenance records in accordance with domestic record-keeping practices and the Requirement document’s directions. Although the AD does not specify record formats, documentation will be necessary to evidence compliance.

6. Track amendments and variants: Note that Amendment 3 expanded inspections and applicability and that Amendment 4 aligns domestic applicability with a clarified FAA AD (Background). Maintain a process to check for further AD amendments or FAA AD revisions and to re-assess applicability, especially for aircraft variants near certification boundaries.

7. Verify effective dates: The AD becomes effective on 13 March 2008 (Compliance). Ensure that inspection scheduling accounts for any compliance deadlines in the FAA AD relative to this effective date.

8. Engage maintenance providers early: If inspections require specialised capabilities, schedule them with qualified maintenance organisations and inspectors. The Background’s focus on older airframes suggests inspections may be specialised or extensive.

9. Retain evidence of obtaining and following the Requirement document: Because the AD incorporates the FAA AD by reference rather than restating the content, it will be important to retain records that the FAA AD was obtained, the relevant revision was followed, and that the inspections were conducted as required.

10. Seek clarification if needed: The AD does not describe appeal procedures or alternative methods of compliance; if an operator believes an alternative inspection method applies, or if there is uncertainty about applicability for a particular variant, the practical step is to seek clarification from CASA or the delegate who issued the AD. The AD itself supplies no procedural rule for alternatives; it only mandates action in accordance with the FAA AD and makes the AD effective on a stated date (Requirement; Compliance; Background).

These steps follow directly from the AD’s text: determine applicability, obtain and follow FAA AD 2004-07-22 R1 Amdt 39-15326, and ensure inspection programmes and records reflect the Requirement document’s mandates. The AD’s Background and amendment notes make clear that previous amendments have altered scope and that the AD was revised to match an FAA clarification, so ongoing monitoring of the FAA AD and domestic amendments is a necessary compliance task.