AD/B737/10 Amdt 2 - Aft Lower Cargo Doorway Frame

The AD rests on a small set of concepts, each present in the text and each carrying operational implications.

Applicability: The directive targets specific airframes, defined by model and range of line numbers: "Model 737-200 and -300 series aircraft, line numbers 6 through 1204" (Applicability). That is a precise fleet cut: aircraft with line numbers inside that range are squarely within scope; aircraft outside that range are not mentioned.

Imported technical requirement: The AD does not include procedural detail. Instead it requires action "in accordance with the technical requirements of FAA AD 93-14-10Amdt 39-8634" (Requirement). The AD therefore functions as an adopting instrument; the technical standard, inspection intervals, and accepted repairs/modifications are contained in the referenced FAA AD and in the Boeing Service Bulletin identified by note.

Service Bulletin linkage and revision control: The Note states that "Boeing Service Bulletin 737-53-1096 original issue, or later FAA approved revision, refers." That ties allowed compliance work to a specific manufacturer service document and limits acceptable revisions to those approved by the FAA. In practice, compliance requires verification that the specific revision used is FAA approved.

Terminating action versus continuing inspections: The Background records that an earlier amendment (Amendment 1) had treated only particular modifications at a specified improved standard (Revision 1 to the Service Bulletin) as terminating action. Amendment 2 updates the Directive to mirror the current FAA AD position that "requires repetitive inspections to continue after installation of the optional terminating modification" (Background). Conceptually, that means that installation of the optional modification does not, under the current FAA standard, remove the ongoing inspection obligation.

Risk and causation statement: The Background explains the safety trigger: "Frame cracking is attributed to fatigue from pressurisation loads" and left unchecked may lead to "severing of the frames and cracking of the adjacent fuselage skin" with the result that it would "seriously reduce the strength of the fuselage in this area, and present a high risk of a rapid decompression" (Background). That statement supplies the causal mechanism linking operations (pressurisation cycles) to degradation (fatigue cracks) to an identified hazard (rapid decompression).

Administrative effect and date: The AD makes an administrative decision to adopt and adapt the FAA AD and fixes an effective date for the requirement: 22 December 2005 (Compliance; "This Amendment becomes effective on 22 December 2005.").

Delegation and signatory: The instrument is signed by "David Villiers, Delegate of the Civil Aviation Safety Authority" with a date of 8 November 2005 on the face of the AD (signature block). That identifies the issuing authority within CASA but does not in the text provide further detail on decision-making criteria or appeal pathways.

In short, the main concepts are: defined applicability, incorporation by reference of FAA AD and Boeing SB technical requirements, revision control by FAA approval, continuation of repetitive inspections despite optional modification, articulation of the safety risk and causal mechanism for the AD, and a fixed effective date endorsed by a CASA delegate.

The text identifies a narrow set of directly affected parties and allows reasonable, source-grounded inference about other stakeholders who will experience consequences.

Directly affected operators and owners: The plain applicability clause names "Model 737-200 and -300 series aircraft, line numbers 6 through 1204" (Applicability). Aircraft owners, lessees, or operators of those specific line-numbered airframes are the primary obligors to implement the actions required by the FAA AD as adopted in the Requirement. They will bear the direct costs of inspections and any modifications.

Maintenance organisations and engineers: Because compliance is "in accordance with the technical requirements of FAA AD 93-14-10Amdt 39-8634" and references Boeing Service Bulletin 737-53-1096 (Requirement; Note), maintenance organisations authorised to perform structural inspections and modifications on 737 airframes will be the providers of the required work. They must ensure work is done in conformity with the FAA-approved procedures and revisions.

Regulator and its delegate: The instrument is issued by the Civil Aviation Safety Authority via its delegate, David Villiers (signature block). CASA, through this AD, determines the content and timing of the obligation for the specified fleet segment.

Manufacturer (Boeing): The Boeing Service Bulletin is cited as the service information reference (Note). Boeing as the SB author provides the technical procedures that operators can follow; it is therefore materially involved in how compliance is achieved. The AD also notes that only "frame modifications to the improved standard of Revision 1 to the related SB" were formerly considered terminating; Amendment 2 updates that position to match the FAA AD (Background). That history affects the interaction between manufacturer-recommended work and regulatory effect.

Cross-jurisdictional regulator (FAA): Because the AD imports FAA AD 93-14-10Amdt 39-8634 as its technical requirement (Requirement), the FAA is a de facto co-author of the technical standard applied to Australian-registered aeroplanes in this case. The AD also explicitly requires that later Service Bulletin revisions be FAA approved (Note), which places the FAA at the centre of revision control.

Aircraft certification and continuing airworthiness administrators: Entities responsible for maintaining an aircraft's airworthiness records (operator quality assurance, continuing airworthiness management organisations) will need to document compliance with the FAA AD and the Boeing Service Bulletin revision relied upon. The AD ties compliance to the Requirement document's schedule and procedures (Compliance).

Passengers and insurers: While not named in the text, passengers derive the safety benefit identified in the Background (prevention of a rapid decompression). Insurers may be affected indirectly through changes in maintenance schedules and perceived risk profiles of the fleet, but the AD does not address insurance directly.

Less affected or excluded parties: Aircraft outside the stated line number range, or different 737 variants not explicitly included, are not addressed by this instrument. The AD does not claim to apply beyond the line numbers given.

Who pays and who decides: From the text, costs of inspections and any modifications will fall primarily on the owners/operators of the listed aircraft (Applicability; Requirement). The decision about what actions satisfy the Directive is made by reference to the FAA AD and FAA-approved Service Bulletin revisions; CASA’s delegate issued the Directive, but the substantive technical standard is imported from the FAA and Boeing documents (Requirement; Note; signature block).

The AD creates a set of duties that are framed by incorporation by reference and a precise applicability band. The text also leaves some matters implicit because the technical content is not reproduced in full in the instrument.

Primary duty to perform specified action: Operators of the covered aircraft must "Action in accordance with the technical requirements of FAA AD 93-14-10Amdt 39-8634" (Requirement). The Duty is to follow the technical requirements of the referenced FAA AD, including inspections and any repair or modification steps detailed there.

Duty to comply by the effective date: The instrument fixes its operational timing. Compliance is required "As specified in the Requirement document, with a revised effective date of 22 December 2005" and the amendment "becomes effective on 22 December 2005" (Compliance; "This Amendment becomes effective on 22 December 2005."). The duty to meet whatever compliance timelines are set in the FAA AD therefore commences from that effective date, subject to the specific compliance provisions contained in the FAA AD.

Duty to follow FAA-approved revisions of the service bulletin: The Note links acceptable service bulletin reference to FAA approval: "Boeing Service Bulletin 737-53-1096 original issue, or later FAA approved revision, refers" (Note). The duty to use an FAA-approved revision means operators cannot unilaterally adopt later manufacturer revisions unless those revisions have FAA approval.

Ongoing duty for repetitive inspections despite modification: The Background records that Amendment 2 aligns the AD with the current FAA AD "which requires repetitive inspections to continue after installation of the optional terminating modification" (Background). That establishes a duty to continue periodic inspections even where an operator carries out the optional modification that might previously have been described as terminating action.

Implication for documentation and maintenance records: While the AD text does not set out paperwork rules, the directive's reliance on the FAA AD and the service bulletin implies that an operator's proof of compliance will be the records demonstrating that the FAA AD steps and SB revisions were implemented. The AD’s Compliance entry states actions are "As specified in the Requirement document" (Compliance), which will include those procedural and recordkeeping steps in the FAA AD.

Rights or options signalled in the text: The AD notes an "optional terminating modification," which the FAA AD treats as optional (Background). However, the current FAA AD position requires continued inspections post-installation, so the "option" is limited to whether to install the modification, not to whether inspections are required. The Note gives operators the right to use later FAA-approved revisions of Boeing Service Bulletin 737-53-1096, subject to FAA approval.

Absence of explicit exemptions or defences in the text: The AD itself does not include any explicit exemption provisions, alternate means of compliance, deferral regimes, or penalty avoidance clauses. It does not set out a process for seeking relief or alternative methods of compliance in the text provided. The only procedural nuance recorded is that the AD references FAA-approved revisions of the service bulletin (Note) and updates prior statements about terminating action (Background). Any rights to seek alternative methods or exemptions are not articulated in this instrument.

Delegation and authority: The AD is issued by CASA via its delegate, David Villiers, suggesting the legal authority to make the directive is exercised through delegation. The instrument does not specify appeal routes or review opportunities within the text.

In summary, duties are: identify whether a given aircraft is within line numbers 6-1204 (Applicability); perform the actions set out in FAA AD 93-14-10Amdt 39-8634 and any FAA-approved Boeing SB revision that applies (Requirement; Note); and maintain repetitive inspections even after installing the optional terminating modification (Background). The AD does not, in its text, set rights to exemptions or alternate compliance paths.

The text provided does not specify monetary penalties, civil sanctions, criminal offences, or the enforcement mechanisms that CASA will use in the event of non-compliance. The notice focuses on stating the technical obligation, applicability, and effective date but omits any explicit enforcement or penalty provisions.

What the instrument does show about enforcement presence and mechanism: The AD is issued by the Civil Aviation Safety Authority through its delegate, which indicates the instruction is an official regulatory instrument (signature block: "David Villiers, Delegate of the Civil Aviation Safety Authority"). That institutional provenance implies enforceability as an airworthiness directive within CASA’s regulatory remit, but the AD text here does not reproduce the statutory enforcement pathways, inspection powers, or penalty schedules that CASA may have available under broader aviation law.

Absence of penalty text: There is no clause in the AD that details fines, licence suspensions, prohibition on flight, or other specific enforcement steps. There is also no statement on administrative compliance processes such as notices to produce maintenance records, grounding orders, or remedial directions. The instrument simply records the mandatory actions and the effective date (Compliance; "This Amendment becomes effective on 22 December 2005").

Evidence and audit implications: Because the AD imports the FAA AD and the Boeing Service Bulletin as the technical standard (Requirement; Note), an inspector or regulator seeking to enforce the Directive would, in practice, compare an operator’s maintenance records and inspection reports against the referenced documents. The AD’s statement that compliance is "As specified in the Requirement document" (Compliance) suggests that the FAA AD contains the detailed compliance schedule and likely the testing/inspection criteria that an auditor would use to assess conformity.

Implementation risk and compliance uncertainty: The AD’s lack of explicit local enforcement steps in the text could create implementation uncertainty for operators about how CASA will verify compliance or what procedural steps are required to evidence compliance to CASA specifically. The AD does not define reporting obligations to CASA, nor does it specify whether CASA considers completion of the Boeing SB work a completion of the AD requirement absent the FAA AD’s documentation. The only clear administrative point is the effective date and the issuing delegate.

Implications of continuing inspections post-modification: The Background’s statement that the FAA AD "requires repetitive inspections to continue after installation of the optional terminating modification" (Background) means that an operator cannot treat the optional modification as a definitive way to remove ongoing obligations. This has enforcement implications: even if an operator has installed the optional modification, an inspector could still require records of the repetitive inspections to demonstrate compliance.

Practical enforcement behaviours left unspecified: The AD does not instruct whether CASA will perform random audits, spot inspections, or require submission of compliance forms. Nor does it provide guidance on the consequences if an operator uses a Boeing Service Bulletin revision that is not FAA approved. The Note explicitly ties acceptable revisions to FAA approval, so a non-FAA-approved revision would not, on the face of this AD, satisfy the Note’s criteria.

Takeaway: The instrument establishes mandatory technical obligations by reference and fixes an effective date, but the text itself is silent on specific penalties and enforcement procedures. Enforcement will depend on CASA’s broader regulatory framework and practices, which are not reproduced in this AD text.

This AD explicitly integrates external regulatory and manufacturer instruments into its operation. The text shows cross-references and an alignment that creates a network of prescriptive sources rather than a standalone technical regimen.

Primary cross-reference to FAA AD: The AD’s Requirement explicitly adopts "the technical requirements of FAA AD 93-14-10Amdt 39-8634" (Requirement). That means the Australian Directive’s substantive technical obligations are defined by the FAA instrument. The CASA AD therefore interacts directly with US federal aviation regulation as embodied in the FAA AD. The FAA AD's text, compliance schedules, inspection procedures, and any AMOCs (alternative methods of compliance) that the FAA AD contemplates will be relevant to Australian operators subject to this CASA Directive.

Manufacturer Service Bulletin integration: The Note names Boeing Service Bulletin 737-53-1096, "original issue, or later FAA approved revision" (Note). That integrates the manufacturer’s technical instructions and adds a revision control mechanism tied to FAA approval. The AD’s interaction with Boeing documents means that changes Boeing makes to the SB only change the CASA AD’s operative content to the extent the FAA approves those revisions.

Relationship between terminating action language and continuing FAA requirements: The Background explains that Amendment 1 previously identified a specific modification standard (Revision 1 to the SB) as terminating action. Amendment 2 "is issued to update this Directive to the current FAA AD, which requires repetitive inspections to continue after installation of the optional terminating modification" (Background). That shows a temporal interaction: CASA’s AD is aligned to the current FAA position; when the FAA position changes, CASA updated its own directive to mirror that change. For regulated parties, this creates a dynamic where compliance obligations in Australia may shift as the FAA AD's stance changes, because the CASA AD imports the FAA AD technical requirements.

Implications for airworthiness certification and continuing airworthiness regimes: The AD operates within the continuing airworthiness regime by imposing inspection and modification obligations that must be carried out to maintain structural integrity. While the instrument does not explicitly cite domestic continuing airworthiness statutes, it functions as an airworthiness directive that imposes continuing airworthiness requirements by reference to the FAA and Boeing documents.

Interplay with maintenance approvals and personnel qualifications: The AD’s reliance on FAA-approved SB revisions suggests that technical acceptability of work will be measured against FAA-approved criteria. This may interact with local approvals for maintenance organisations and certifying staff, though the AD does not itself state those interactions. The practical effect is that maintenance tasks performed to comply must meet the technical standard as set in the FAA AD and an FAA-approved SB revision.

Cross-border regulatory coordination: The AD evidences a coordination mechanism where CASA adopts FAA technical standards for a particular structural issue. That reduces duplication of technical assessment but implies that changes made by a foreign regulator (the FAA) can alter domestic obligations.

Lack of explicit conflict resolution clauses: The AD does not address what happens if there is a discrepancy between Australian regulation or CASA guidance and the FAA AD or Boeing SB. The text simply updates to match the "current FAA AD." Where conflicts could arise (for example, an Australian interpretation different from FAA), the AD provided does not resolve them internally.

Net effect: The AD acts as a local enforcement node that operationalises foreign technical standards and manufacturer instructions within the Australian regulatory environment. It relies on those external instruments for technical content and revision control, and it updates local obligations to align with the FAA AD’s current requirements, including the requirement that repetitive inspections continue after an optional terminating modification.

The AD document contains an explicit amendment history narrative in the Background and header entries, and records the timing of the current amendment.

Original and amendment numbering: The AD is titled "AD/B737/10 Amdt 2" and the header also contains "13/2005" (top line and repeated elsewhere). This indicates the AD is the second amendment to AD/B737/10 and that it is catalogue-numbered as 13/2005 for administrative reference.

Content of Amendment 1 as summarised: The Background recounts that "Amendment 1 made reference to the related FAA AD, and the fact that only frame modifications to the improved standard of Revision 1 to the related SB constitute terminating action." That places Amendment 1 as having limited what repair or modification would be considered terminating action, specifically tying terminating status to a particular improved standard in Revision 1 of Boeing Service Bulletin 737-53-1096.

Reason for Amendment 2: The Background then explains the rationale for Amendment 2: "Amendment 2 is issued to update this Directive to the current FAA AD, which requires repetitive inspections to continue after installation of the optional terminating modification. This action was prompted by a structural reassessment of the Model 737 series aircraft." That statement records the trigger for the amendment: a structural reassessment of the fleet led the FAA to require continued inspections post-modification, and CASA mirrored that change via Amendment 2.

Timing and effective date: The signature block is dated "8 November 2005" under the delegate's name. The Compliance entry and a separate line state that "This Amendment becomes effective on 22 December 2005." The Compliance entry also notes "As specified in the Requirement document, with a revised effective date of 22 December 2005." The timeline therefore shows the AD was signed on 8 November 2005 and set to take effect on 22 December 2005.

Administrative labelling: The top of the document shows "AD/B737/10 Amdt 2 | Aft Lower Cargo Doorway Frame | 13/2005" followed by the tabular applicability/requirement/compliance/background block. The AD label is repeated multiple times in the provided text. The repetition suggests formal record-keeping identifiers for the directive and its amendment.

No further amendment history recorded: The provided text does not list any subsequent amendments, revocations, or supersessions beyond the statement that Amendment 2 updates the Directive to align with the current FAA AD. The AD does not provide earlier dates for Amendment 1, nor does it provide cross-references to other amendments or to the original AD text beyond the summarised content.

Summary: The amendment history, as recorded in the AD, is concise: Amendment 1 had limited terminating action to Revision 1 of the SB; Amendment 2 modifies that position to reflect the FAA AD’s requirement for ongoing repetitive inspections even after the optional terminating modification, following a structural reassessment. The AD was signed by the CASA delegate on 8 November 2005 and became effective on 22 December 2005.

The AD text contains no references to litigation, court decisions, appeals, or precedent. There are no named cases, legal challenges, or dispute resolutions recorded in the provided document. The instrument is a regulatory safety directive, and the text supplied is limited to applicability, required action by reference, compliance timing, background explanation, and the issuing delegate’s signature.

Implication of silence: Because the AD does not include any litigation history, one must proceed on the basis that the document itself does not record any judicial consideration for this particular directive. The absence of litigation references does not indicate that no litigation exists in the broader administrative or judicial record; it merely reflects that this instrument does not contain a litigation history section.

What the document does provide that is relevant for potential litigation: The AD sets out explicit technical obligations by reference to the FAA AD and Boeing Service Bulletin, identifies the aircraft applicability (line numbers 6-1204), and records the effective date. Any legal challenge or enforcement action that arose would therefore hinge on whether the operator complied with the FAA AD technical requirements, whether the correct aircraft were captured by the applicability clause, whether the FAA-approved SB revision used for compliance was indeed FAA approved, and whether the operator followed the requirement that repetitive inspections continue post-modification.

Elements litigation might scrutinise (based on the AD text alone): the clarity of the applicability clause (line numbers specification), the incorporation by reference mechanics (i.e., how the FAA AD is adopted into the CASA AD), the status and interpretation of "optional terminating modification" vis-a-vis the FAA AD requirement for repetitive inspections, and the effective date. None of those issues are addressed with judicial outcomes in this AD text.

Practical observation for researchers: To identify any litigation related to this AD, one would need to consult administrative tribunal or court records, enforcement notices, or CASA internal files, none of which are reproduced in the instrument. The AD itself contains no litigation history or references.

The AD contains several specific features and linguistic points that can produce practical traps or misunderstandings if read without careful attention to its text.

Assuming the optional terminating modification ends inspections: The AD explicitly records that the current FAA AD "requires repetitive inspections to continue after installation of the optional terminating modification" (Background). A common misconception would be to assume that installing a modification described as "terminating" in earlier material stops inspection obligations. Here Amendment 2 reverses that reading: the modification is optional and does not obviate the requirement for repetitive inspections under the current FAA AD.

Relying on the wrong revision of the Boeing Service Bulletin: The Note states the SB reference as "original issue, or later FAA approved revision" (Note). Using a later Boeing SB revision that has not been FAA approved would not meet the Note’s condition. Operators must therefore confirm FAA approval status for any non-original revision before relying on it for compliance.

Applicability by line number: The Applicability line restricts the AD to "line numbers 6 through 1204" (Applicability). Aircraft with line numbers outside that range are not captured by this text. A gotcha is misidentifying an aircraft’s line number or assuming all 737-200 and -300 variants are included. Operators must verify the specific aircraft line number to confirm applicability.

Compliance timing and the Requirement document: The Compliance entry defers the concrete schedule to the "Requirement document" (the FAA AD). The AD itself does not restate inspection intervals or compliance windows. A practical trap is to overlook that timing is defined elsewhere and therefore to miss deadlines specified in the FAA AD.

Confusion about what constitutes "termination": Amendment 1 had tied terminating action to "frame modifications to the improved standard of Revision 1 to the related SB" (Background). Amendment 2 states a different position. Relying on older amendment wording or older SB revisions without cross-checking the current FAA AD and the current amendment could lead to non-compliance.

Record-keeping expectations not stated: The AD does not specify the recordkeeping or reporting steps an operator must take to evidence compliance to CASA; operators who assume that merely completing work per the SB meets all administrative requirements may later face queries if CASA expects documented proof in a particular format. The AD says compliance is "As specified in the Requirement document" (Compliance), but the actual administrative proof required by CASA is not set out here.

Potential ambiguity over who validates FAA-approved revisions: The AD requires later revisions to be "FAA approved" but does not specify whether CASA independently accepts that FAA approval or whether additional Australian acceptance steps are needed. The Note binds acceptable revisions to FAA approval but is silent on whether CASA requires further steps to accept a revision domestically.

Assuming uniform global effect: Because the CASA AD imports the FAA AD, operators might assume that every aspect of the FAA AD , including AMOCs and local FAA practices , automatically transpose to domestic effect. The AD imports the technical requirements, but the text does not comment on whether domestic alternative methods of compliance or other local regulatory mechanisms apply.

Effective date versus signing date: The AD is signed on 8 November 2005 but the effective date is 22 December 2005 (signature block; Compliance). Mistaking the signing date for the effective date could cause premature enforcement action or missed deadlines. Operators should plan around the stated effective date.

In sum, careful attention is needed to line-number applicability, the exact FAA AD and SB revision status, the continuing nature of inspections after modifications, and the fact that the AD incorporates but does not restate detailed inspection schedules. Confirmation of FAA approval and precise identification of the aircraft are essential to avoid compliance gaps.

The AD’s operative duty is to carry out the technical actions specified in FAA AD 93-14-10Amdt 39-8634, using Boeing Service Bulletin 737-53-1096 original issue or a later FAA-approved revision; the effective date of the obligation is 22 December 2005. The following steps are a source-grounded, practical checklist derived from the AD text.

1. Establish applicability for each airframe:

   • Confirm the aircraft model and line number. The AD applies to Model 737-200 and -300 series aircraft with line numbers 6 through 1204 (Applicability). Do not assume inclusion; verify the aircraft’s line number against that range.

2. Obtain and read the exact FAA AD text referenced:

   • The Requirement requires "action in accordance with the technical requirements of FAA AD 93-14-10Amdt 39-8634" (Requirement). Obtain the full FAA AD text, including compliance times, detailed inspection procedures, and any specified repairs or modifications. The AD’s Compliance entry states compliance is "As specified in the Requirement document" (Compliance), so the FAA AD contains the operative schedule and procedures.

3. Confirm the Boeing Service Bulletin revision status:

   • The Note specifies Boeing Service Bulletin 737-53-1096 original issue, "or later FAA approved revision" (Note). If planning to use a later SB revision, confirm that the FAA has approved that specific revision. Keep documentary proof of FAA approval.

4. Schedule and perform inspections and any required modifications:

   • Follow the inspection intervals, techniques, and repair/modification procedures contained in the FAA AD. The Background emphasises that frame cracking is attributed to fatigue from pressurisation loads and carries a serious safety hazard (Background), so adhere to the technical steps precisely.

5. Maintain repetitive inspections even after modification:

   • The Directive notes that the current FAA AD "requires repetitive inspections to continue after installation of the optional terminating modification" (Background). Therefore, do not treat the optional terminating modification as removing the need for future inspections. Build repetitive inspection cycles into maintenance planning.

6. Document all work and approvals:

   • Although the AD text does not specify recordkeeping formats, compliance will be demonstrated through maintenance records showing the FAA AD steps and the SB revision used. Record dates, part numbers, work scopes, signatures of certifying engineers, and reference to the FAA AD and SB revision. Keep evidence that any later SB revision relied upon was FAA-approved.

7. Coordinate with maintenance providers and CASA contact points:

   • Ensure that the maintenance organisation carrying out inspections and modifications is aware of the FAA AD requirements and the need for FAA-approved SB revisions. Retain contact information for CASA or the delegate should confirmation of compliance or discussion of any unusual corrective actions be required; the AD was issued by a CASA delegate (signature block).

8. Verify compliance against the effective date:

   • The AD becomes effective on 22 December 2005 (Compliance; "This Amendment becomes effective on 22 December 2005."). Ensure that compliance timelines and initial inspection windows specified in the FAA AD are calculated relative to that effective date as required.

9. Monitor for further amendments:

   • Because CASA adopted the FAA AD by reference and Amendment 2 tracks the FAA AD’s current position, monitor the FAA AD and Boeing SB for later revisions or further FAA guidance that may be incorporated into CASA directives. The Background records a past instance of Amendment 2 updating the Directive to match the FAA AD; future changes may likewise be mirrored.

10. If uncertain, seek regulatory clarification:

    • The AD does not specify alternative methods of compliance or a process for seeking approval of different procedures in the text provided. If an operator proposes an alternative repair or an alternative compliance schedule, they should seek formal clarification or acceptance from CASA, noting that the AD ties acceptable SB revisions to FAA approval.

Who pays and who decides in the compliance steps: Owners/operators pay for inspections, repairs, and any optional modifications. The technical decision about what actions satisfy the AD is defined by the FAA AD and any FAA-approved Boeing SB revision; CASA’s delegate issued the Directive, and CASA will require evidence of compliance consistent with the Requirement document (Applicability; Requirement; Note; Compliance; signature block).

Record retention and audit readiness: Although the AD does not state explicit retention periods or audit forms, maintain comprehensive maintenance records that correlate actions to the FAA AD section numbers and SB revision used. This will allow CASA or its delegate to verify compliance promptly should enforcement or inspection occur.

Practical scheduling: Because the AD requires repetitive inspections (Background), incorporate inspection intervals into the aircraft’s continuing airworthiness plan and track upcoming inspections rigorously. Do not treat the optional modification as a one-off absolution of inspection duties.

In short, compliance under this AD requires verifying applicability (line number), following the FAA AD technical requirements exactly, using only FAA-approved SB revisions where applicable, continuing repetitive inspections post-modification, documenting every step, and ensuring all deadlines tied to the AD’s effective date are met.