AD/B737/235 Amdt 1 - Fuselage Skin Area at the Dorsal Fin Assembly

The instrument focuses on a narrow set of structural and sealing components in the dorsal fin area of certain Boeing 737 Classic series airframes. The source uses specific technical phrases that are the core compliance concepts:

• Applicability: the instrument applies to “All Model 737-300, -400, and -500 series aircraft” (Applicability line). That is the explicit fleet scope the instrument addresses.

• Dorsal fin landing and nose cap blade seals: the Background locates the problem “in the fuselage skin area under the blade seals of the nose cap of the dorsal fin.” The “dorsal fin landing” is the area at issue where abrasion resistant coating and fuselage skin may experience chafing.

• Damage modes called out: the instrument specifies inspection for “chafing or cracking in the fuselage skin and abrasion resistant coating at the dorsal fin landing,” and inspection for “damage to the dorsal fin seals, attach clip, and seal retainer” (Background). The primary structural risk described is fatigue cracking developing from prior wear damage, driven by cabin pressurisation cycles, with the worst-case safety consequence being “rapid in-flight decompression” (Background).

• Replacement of previous inspection regime: Amendment 1 is explicitly stated to “end the need for the existing repetitive inspections” and to do so by introducing the new inspection and corrective-action requirements (Background). Mechanically, that means the AD both prescribes new tasks and removes prior repetitive obligations for the same damage pathway.

• Incorporation by reference: The Requirement directs compliance with “FAA AD 2009-07-11 Amdt 39-15870.” The Note references Boeing Alert Service Bulletin 737-53A1266 and Boeing Message 1-QX035 dated 13 October 2004. The instrument therefore relies on external technical material for the technical scope and instructions, rather than reproducing detailed inspection thresholds, intervals or repair instructions in the text of the Australian AD itself.

Those concepts are the operational building blocks: a defined fleet scope, a set of specific inspection targets and damage modes, a set of corrective actions to follow if damage is found, and the importation of FAA and manufacturer documents as the technical source for the inspections and corrective actions. The document is limited in text; it does not reproduce inspection intervals, pass/fail criteria or repair procedures, but points operators to the FAA AD and the named Boeing documents for those technical details.

The instrument applies explicitly to “All Model 737-300, -400, and -500 series aircraft” (Applicability line). That statement determines the primary group of affected parties: any owner, operator, lessor, or maintenance organisation that has control of an aircraft of those models registered or operated under the jurisdiction to which the AD applies.

The Requirement clause directs action “in accordance with the technical requirements of FAA AD 2009-07-11 Amdt 39-15870.” That choice of wording means that the persons responsible for continuing airworthiness and maintenance decisions must obtain and apply the FAA AD’s specified inspections and corrective actions. The Note identifies Boeing Alert Service Bulletin 737-53A1266 (original issue or later FAA approved revision) and Boeing Message Number 1-QX035 dated 13 October 2004 as relevant documents. In practice, the people who must consult and apply these documents are the aircraft maintenance planners, licensed engineers and certificated maintenance organisations tasked with structural inspections and repairs for the affected fleet.

The Background information highlights where the technical risk is located and the safety consequence: a reported 18-inch crack beneath the nose cap blade seals of the dorsal fin, with potential for fatigue cracking caused by cabin pressurisation and resultant rapid in-flight decompression of the fuselage. That description identifies groups within operators who must pay attention: aircraft structures specialists, maintenance control, and safety and engineering departments. It also affects the supply chain for parts, because inspections may find component damage requiring replacement or repair of dorsal fin seals, attach clips, or seal retainers; the instrument references manufacturer service information which operators and maintainers will need to source.

The instrument is issued by CASA (signed by the Delegate), and therefore it binds aircraft subject to CASA’s regulatory remit. The AD’s effective date is 4 June 2009; organisations operating the listed models must be able to demonstrate compliance with the FAA AD and the referenced Boeing material from that date. The instrument does not itself allocate costs, nor does it describe enforcement or penalties in this text, but by naming the fleet and instructing actions it imposes obligations that those operating or maintaining the specified 737-300/400/500 aircraft must meet.

The instrument sets out a single principal duty: carry out “action in accordance with the technical requirements of FAA AD 2009-07-11 Amdt 39-15870” for the aircraft in scope (Requirement). That duty is framed as an obligation to follow the FAA AD’s technical requirements; the Australian instrument does not recapitulate the detailed steps but imports them by reference.

From the Background, the specific technical inspections required by the FAA AD and therefore by this instrument include:

• Inspection for any chafing or cracking in the fuselage skin and in the abrasion resistant coating at the dorsal fin landing; and

• Inspection for damage to the dorsal fin seals, attach clip, and seal retainer.

The Background adds that “other specified and corrective actions as necessary” are part of the new requirements, and that these requirements “will end the need for the existing repetitive inspections.” These statements create operational duties in two forms: (1) perform the new inspections (and any required coating and structural checks), and (2) perform corrective actions if damage is found, following the technical directions in the FAA AD and the referenced Boeing documents.

The instrument prescribes a compliance framework by date: “This Amendment becomes effective on 4 June 2009” and Compliance is stated as “As specified in the Requirement document, with a revised effective date of 4 June 2009.” Practically, that fixes the point from which operators must be able to demonstrate they have completed the tasks required by the incorporated FAA AD and related Boeing documents.

The instrument does not list statutory rights, appeals, or variations in its text. It similarly does not state processes for approval of alternative methods of compliance within its own wording. The Requirement Note does, however, point to Boeing Alert Service Bulletin 737-53A1266 “original issue, or later FAA approved revision,” which implies that only FAA-approved revisions of the service bulletin are endorsed by the Requirement text. The instrument therefore ties the operator’s duty to the status of those external FAA approvals.

In summary, the actionable duties arising from the instrument are: identify affected airframes; obtain and follow FAA AD 2009-07-11 Amdt 39-15870 and the referenced Boeing documents; carry out the inspections for chafing/cracking and for seal/clip/retainer damage; perform corrective actions as required by those documents; and make those changes effective by and after 4 June 2009. The instrument does not set out rights such as appeals or alternative compliance mechanisms in its own text.

The text supplied contains no explicit penalty provisions, monetary fines, or criminal sanctions. The displayed content does not set out an enforcement regime or describe the sanctions for non-compliance. The instrument is framed as an airworthiness directive issued by CASA (signed by a Delegate), and it identifies what actions must be taken and when (“This Amendment becomes effective on 4 June 2009” and “Compliance: As specified in the Requirement document, with a revised effective date of 4 June 2009”), but it does not within the reproduced text specify enforcement mechanisms or penalty levels.

Because the instrument delegates technical obligations to compliance with FAA AD 2009-07-11 and references Boeing service documents, the enforcement consequence implicit in the text is that the holder of the airworthiness or the operator must carry out the prescribed inspections and corrective actions. The document does not say whether the referenced FAA AD contains its own compliance enforcement or whether CASA will treat non-compliance in a particular manner. The absence of penalty detail in the instrument indicates that those seeking the exact enforcement regime or penalties will need to consult the broader CASA regulatory framework and enforcement policy, or other Australian regulatory instruments not reproduced here.

The instrument itself records an effective date and a formal signature by the CASA Delegate, which establishes the directive’s formal status within CASA processes, but again no enforcement procedures are set out in this text. The Background notes the safety consequences of the described defect,specifically the potential for rapid in-flight decompression,which is the safety rationale an enforcement authority would rely upon when prioritising compliance. Within the scope of this document, the only concrete enforcement-related elements are therefore: (a) the naming of the technical standard to be followed (the FAA AD and specified Boeing documents), and (b) the effective date from which compliance is required. The AD does not specify who enforces or how enforcement will be carried out in the material provided.

The instrument expressly incorporates external regulatory and manufacturer material by reference rather than containing detailed technical steps itself. The key cross-references in the source are:

• FAA AD 2009-07-11 Amdt 39-15870, which is named as the technical requirement to be followed (Requirement), and

• Boeing Alert Service Bulletin 737-53A1266 (original issue, or later FAA approved revision) and Boeing Message Number 1-QX035 dated 13 October 2004, which are identified in the Note as related manufacturing guidance.

Mechanically, the Australian AD imports the FAA AD’s technical requirements. That is a formal interaction between CASA’s directive and foreign regulator material: the CASA instrument requires actions “in accordance with the technical requirements” of the named FAA AD. This creates a regulatory dependency: the Australian AD’s substantive tasks are defined by a foreign regulator’s documented directive and by manufacturer service information whose status is tied to FAA approval.

The Background also states that the new FAA AD “introduces an inspection” and “other specified and corrective actions as necessary,” and that these new requirements “will end the need for the existing repetitive inspections.” That indicates that this Amendment alters the pre-existing domestic inspection obligations by substituting the new FAA-led regime for the prior repetitive inspections. In effect, the instrument changes the domestic interaction with earlier domestic AD requirements by terminating a prior repetitive inspection regime and replacing it with the FAA-aligned tasks.

The instrument does not state how it interacts with other Australian statutory instruments, civil liability rules, or certification processes in the text shown. It likewise does not spell out how to obtain or document FAA approvals for later revisions of the Boeing service bulletin, or whether Australian regulatory acceptance is required for FAA-approved revisions. It does, however, implicitly require operators to reconcile their maintenance procedures and records with the FAA AD and Boeing documents, since the AD imports those materials as the source of the inspection and repair tasks to be carried out.

In short, the instrument aligns domestic airworthiness obligations with a specific FAA AD and with certain Boeing service documents, displacing prior domestic repetitive inspection obligations. The operator or maintenance organisation affected must therefore manage compliance with a framework that spans CASA’s directive, the FAA AD, and the manufacturer’s service information as referenced.

The instrument as supplied is identified as AD/B737/235 Amendment 1. The text reports that “Amendment 1 is issued in response to a new FAA AD,” and that the Amendment becomes effective on 4 June 2009 (Background; Compliance). The document records the date of signing as 17 April 2009 by David Villiers, Delegate of the Civil Aviation Safety Authority. It further indicates that the Compliance provision incorporates the FAA AD with “a revised effective date of 4 June 2009.”

The Note attached to the Requirement references Boeing Alert Service Bulletin 737-53A1266 “original issue, or later FAA approved revision,” and Boeing Message Number 1-QX035 dated 13 October 2004. That reference indicates that the Amendment’s technical content is linked to specific manufacturer notices and to the FAA AD that post-dates or updates prior domestic requirements. The Background describes that Amendment 1 introduces inspections for chafing/cracking and for damage to specific seal and clip components, and that the new requirements will end the previous repetitive inspections. From the text we can therefore read the sequence: an initial repetitive inspection regime existed; an FAA AD was issued (FAA AD 2009-07-11 Amdt 39-15870); CASA issued Amendment 1 to align with that FAA AD, effective 4 June 2009, and noted that this replaces the prior repetitive inspections.

The document includes a date associated with Boeing Message 1-QX035: 13 October 2004. That date identifies a manufacturer communication that is relevant to the issue, and the FAA AD number indicates a 2009 FAA action. The domestic Amendment is dated 17 April 2009 and given an effective date of 4 June 2009. The instrument therefore shows a chain of manufacturer and FAA communications culminating in a CASA Amendment that revises domestic inspection obligations as of 4 June 2009.

No other amendment versions or historical AD numbers are reproduced in the supplied text beyond AD/B737/235 and Amendment 1. The text does not show any later amendments, revocations or supersessions beyond this Amendment 1 material. For a full regulatory history beyond the lines shown here, operators would need to consult CASA’s official AD database or archives, but within the provided instrument the Amendment history is restricted to reporting that Amendment 1 replaces prior repetitive inspection requirements and sets the effective date.

The provided instrument contains no references to litigation, court proceedings, administrative appeals or judicial review. The text reproduces the AD content, the technical references (FAA AD and Boeing documents), the applicability and compliance instructions, and the formal signing by the CASA Delegate on 17 April 2009. It does not cite any judicial decisions, contested enforcement actions, or precedential matters.

Because the document does not address litigation or specify dispute-resolution procedures, no litigation history can be identified from the supplied text. Where an operator or other interested party sought to challenge the AD, there is no record of such proceedings in these pages. Similarly, there is no mention of prior litigation influencing the change from repetitive inspections to the new FAA-adopted regime.

Given the absence of litigation references, the practical implication for readers is that the instrument itself is a directive to comply with the stated technical requirements and does not record any court challenges or administrative disputes. Any party seeking public records of legal challenges connected to this AD would need to consult court databases or CASA archives external to the text supplied. Within the instrument itself, the only procedural record is the Amendment, its effective date and the signature of the CASA Delegate; the document does not document any litigation history.

The instrument is short and technical in focus, but several practical pitfalls and traps for operators and maintainers are implicit in the text. These are points that operational teams must explicitly manage because the AD’s wording relies on external documents and replaces prior obligations.

1. Narrow applicability but wide consequences. The AD applies only to “All Model 737-300, -400, and -500 series aircraft” (Applicability). Organisations with mixed fleets must ensure they identify precisely which airframes are within scope; an aircraft incorrectly treated as out of scope may miss required inspections.

2. The AD imports an external FAA AD. The Requirement mandates action “in accordance with the technical requirements of FAA AD 2009-07-11 Amdt 39-15870.” The AD text does not reproduce the inspection intervals, exact inspection methods, or repair criteria. Operators must therefore obtain the FAA AD and any FAA-approved revisions to Boeing SB 737-53A1266 to know the precise tasks to be performed. Failure to reference the correct revision or the FAA-approved revision of the Boeing service bulletin could lead to incomplete compliance.

3. Reference to an FAA-approved revision only. The Note references Boeing Alert Service Bulletin 737-53A1266 “original issue, or later FAA approved revision.” That language means that later manufacturer revisions are only acceptable if FAA approval has been given. Operators should not assume that any later Boeing revision automatically satisfies the Requirement; they must confirm FAA approval status for the revision they intend to rely on.

4. Existing repetitive inspections are ended. The Background states the new requirements “will end the need for the existing repetitive inspections.” That requires careful maintenance-program management. If previous maintenance schedules included repetitive inspections tied to the old AD, maintenance planners must update inspection intervals, work packs, and records to show the switch from repetitive inspections to the new inspection and corrective-action regime. Failure to update maintenance programmes and records can create audit discrepancies.

5. Technical scope includes coating and small parts. The Background mentions inspection of “the abrasion resistant coating at the dorsal fin landing” and of “dorsal fin seals, attach clip, and seal retainer.” These are relatively small-scale items compared to primary structure; inspections may require skin access, removal of fairings, or specialised techniques to inspect coatings and seal retainers. Maintenance planning must account for access times and possible repair or replacement lead times for small parts.

6. The background identifies a significant defect. The instrument references an 18-inch crack “found in the fuselage skin area under the blade seals of the nose cap of the dorsal fin.” That is substantial damage and underscores that if the inspection finds similar cracks, operators must be prepared to address potentially large repairs or aviation lifts out of service. The AD text does not provide repair instructions in full, so operators must rely on FAA AD and Boeing documents to determine allowable repair actions.

7. No penalties or enforcement mechanism stated. The instrument does not give enforcement detail in the text provided. Operators must not assume a lack of penalties; instead they should treat the AD as a binding compliance requirement and coordinate with CASA where uncertainty exists.

8. Date management. The effective date is fixed at 4 June 2009 in this instrument. For operators taking on aircraft or changing registration around that time, accurate documentation of compliance by that date is important. The AD text requires compliance “as specified in the Requirement document, with a revised effective date of 4 June 2009.” That explicit revision must be tracked.

9. Recordation and traceability. The instrument’s brevity leaves record-keeping obligations unspecified. Operators should ensure they document which revision of the FAA AD and which revision of the Boeing SB they used, and the date and results of inspections and corrective actions, because the instrument imports those external documents as the standard to which compliance will be judged.

10. Dependency on foreign regulator and manufacturer approvals. Because the AD ties compliance to FAA AD and to FAA-approved revisions of Boeing service information, any subsequent FAA action or manufacturer revision that is not FAA-approved could create ambiguity as to the acceptable method of compliance under this instrument. Operators should monitor FAA and Boeing notices to remain aligned with the referenced standards.

Those practical “gotchas” are all implicit in the AD text provided and stem from the AD’s design as an incorporation-by-reference instrument that changes prior domestic inspection obligations and relies on external technical material for the operational detail.

The instrument’s text identifies the concrete steps an operator must take if they manage affected aircraft, subject to the limits of the document’s brevity. The compliance pathway, as set out by the AD, is:

1. Confirm applicability. Verify which aircraft in your fleet are “Model 737-300, -400, and -500 series aircraft” as stated under Applicability. Only those aircraft are within scope of this AD.

2. Obtain the referenced technical documents. The Requirement directs action “in accordance with the technical requirements of FAA AD 2009-07-11 Amdt 39-15870.” The Note identifies Boeing Alert Service Bulletin 737-53A1266 original issue or a later FAA-approved revision, and Boeing Message Number 1-QX035 dated 13 October 2004, as related documents. Obtain copies of the FAA AD and the specified Boeing documents (ensuring the Boeing service bulletin revision has FAA approval if relying on a later revision).

3. Read the FAA AD and Boeing documents for inspection scope and procedures. The Australian AD text does not set out inspection intervals, pass/fail criteria, repair procedures or allowable deferred-action criteria; those technical specifications are contained in the FAA AD and the referenced Boeing service information. Use those documents to determine exactly how to inspect the fuselage skin, the abrasion-resistant coating at the dorsal fin landing, and how to inspect dorsal fin seals, attach clips and seal retainers.

4. Schedule and perform the inspections. Conduct the inspections for chafing or cracking in the fuselage skin and the abrasion resistant coating at the dorsal fin landing, and for damage to the dorsal fin seals, attach clip, and seal retainer, following the methods and intervals set out in the FAA AD and in the Boeing materials. Ensure inspection access arrangements are planned, as parts of the dorsal fin installation may require fairing removal or other access work.

5. Execute corrective actions. If the inspections reveal damage, follow the corrective actions specified in the FAA AD and the Boeing documents. The AD’s Background explicitly records “other specified and corrective actions as necessary,” so corrective measures should conform to the FAA- and Boeing-approved repairs or approved methods of compliance.

6. Update maintenance programmes. Because the AD states the new requirements “will end the need for the existing repetitive inspections,” adjust the maintenance programme and planned maintenance system to remove superseded repetitive inspection tasks and to incorporate the new inspection and corrective-action regimen. Ensure that the maintenance control manual and scheduled maintenance intervals reflect the change.

7. Record compliance and retain evidence. The AD requires action as specified in the FAA AD and notes the effective date of 4 June 2009. Maintain a record showing which FAA AD revision and which Boeing SB revision were used, the dates inspections were performed, the findings and corrective actions taken, and that compliance was achieved by the effective date or in accordance with the timing required by the FAA AD.

8. Verify regulatory conformity where ambiguous. The instrument itself does not outline approval processes for alternative methods of compliance or how to document FAA-approved revisions of Boeing SBs. Where ambiguity arises, consult with CASA or the nominated CASA delegate for clarification on acceptable methods and for confirmation that the chosen repair or inspection approach satisfies the AD’s Requirement.

9. Inventory parts and logistics. Inspections may reveal damage to seals, attach clips or retainers. Ensure spare parts supply, procurement lead times and approved repair sources are available so inspections do not become extended maintenance events that affect operations.

10. Monitor for further updates. The AD ties Australian obligations to the FAA AD and to manufacturer documents. Monitor FAA AD bulletins and Boeing service communications for any FAA-approved revisions to the Boeing service bulletin or further FAA actions that may change the technical requirements to which this Australian AD refers.

These steps follow directly from the Applicability, Requirement, Note and Background text in the source. The AD’s effective date is explicit: “This Amendment becomes effective on 4 June 2009.” Compliance must therefore be undertaken in line with the dates and technical documents specified in the AD. Where the AD text does not provide a procedural detail, the FAA AD and the referenced Boeing documents are the operative technical authorities.