AD/B767/231 - Inspections of Wire Bundles

The AD revolves around a small number of tightly defined concepts and cross-references. These are the operative items that determine scope, method, and compliance:

• Applicability. The AD explicitly applies to "All Model 767-200, -300, -300F and -400ER series aeroplanes" (Applicability). That is the universe of operators required to comply. No serial number carve-outs or owner/operator exemptions appear in the text provided.

• Inspected items. The inspections must target "wire bundles, power drive unit (PDU) wiring and wire attaching hardware, supports and sleeving located in the forward and aft lower lobe cargo compartments" (Requirement 1). The AD identifies both wiring and associated attachments and protective features, so the inspection scope extends beyond conductor condition to ancillary components that affect wiring integrity.

• Method of inspection. The AD does not prescribe a bespoke inspection protocol within the text itself; instead it mandates compliance with the Accomplishment Instructions of two Boeing Service Bulletins: SB 767-25-0376 Revision 1 for 767-200/300/300F and SB 767-25-0377 Revision 1 for 767-400ER (Requirement 1). Those service bulletin instructions therefore become the required procedural standard for inspection technique, extent, and reporting where this AD applies.

• Recurrence and timing. The AD sets a two-step timing regime. First inspections are required "Within 36 months after the effective date of this Directive" and subsequent inspections are required "at intervals not to exceed 24,000 hours time in service or 72 months, whichever occurs first" (Compliance). This ties recurrence both to flight hours and to calendar time.

• Corrective action and flight-status consequence. Any damage or deficiencies discovered during inspection must be rectified, and rectification is required "Before further flight after the Requirement 1 inspections" (Requirement 2). That makes discovered defects a pre-flight grounding condition until fixed.

• Prior and later revisions acceptance. The AD accepts actions done before the effective date using earlier Boeing SBs dated 17 November 2005 as satisfying the requirements. It also accepts "Later revisions of the above SB(s), approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2007-16-18" as equivalent for compliance (Requirements/Notes). This creates a mechanism to rely on FAA AMOC approvals for alternative technical means.

• Cross-reference to FAA rule. The AD explicitly refers to "FAA AD 2007-16-18 Amdt 39-15157" and uses FAA AMOC approval as the acceptance route for later SB revisions. The AD therefore incorporates, by reference and cross-acceptance, a foreign regulator's certification actions into its compliance regime.

These core concepts define the compliance perimeter: which aeroplanes, what to inspect, what instructions to follow, when to do it, how often thereafter, what to do about defects, and what prior or alternative documentation is acceptable.

Directly affected parties are operators and maintainers of Boeing 767 aircraft within the AD's applicability: "All Model 767-200, -300, -300F and -400ER series aeroplanes" (Applicability). This group includes commercial airlines, freight operators (notably operators of the -300F freighter variant), leasing companies that place these airframes within Australian jurisdiction, and maintenance organisations responsible for airworthiness compliance.

Specific roles and responsibilities are implied by the AD text:

• Registered operators and owners. Operators must ensure the inspections occur within the specified 36-month window from the AD effective date, and that subsequent inspections occur at the stated intervals ("Within 36 months after the effective date ... and thereafter repeat the inspections at intervals not to exceed 24,000 hours time in service or 72 months, whichever occurs first" , Compliance). Operators ultimately bear the financial costs of planning, labour, parts, and downtime.

• Maintenance organisations and certificated engineers. The AD requires inspections "in accordance with the Accomplishment Instructions of Boeing Service Bulletin ... Revision 1" (Requirement 1). Maintenance providers must have access to those SBs, and the technical capability to carry out the "detailed inspections" and the corrective actions identified. The AD creates a mandatory work scope that maintenance personnel must implement and document.

• Civil Aviation Safety Authority (CASA). CASA is the issuing authority for this AD, and a CASA delegate signed the directive (Charles Lenarcic, Delegate of the Civil Aviation Safety Authority, 7 September 2007). CASA is the regulator that has converted the Boeing SBs and FAA AD into a compulsory requirement in the Australian regulatory environment. The AD itself does not include an enforcement penalties schedule, but CASA is the regulator responsible for oversight.

• United States Federal Aviation Administration (FAA). The AD makes explicit cross-jurisdictional reference to FAA AD 2007-16-18 and accepts FAA-approved AMOCs to that FAA AD as acceptable for compliance with this AD. That makes FAA approvals relevant to affected Australian operators relying on later SB revisions approved by the FAA.

• Parts suppliers and OEM. If rectification includes parts replacement, suppliers of wiring, harnesses, supports, sleeving, and PDUs may be impacted by increased demand. The AD does not allocate procurement responsibilities, but operators will need to source parts compliant with the Boeing SB instructions.

Indirectly affected parties include insurers and lessors who must ensure their aircraft remain airworthy and may impose compliance covenants; flight and dispatch planners who must account for potential grounded aircraft until rectification is completed; and safety management and compliance teams required to retain records showing when inspections and rectifications were completed.

The AD’s requirements to rectify defects "Before further flight" impose operational consequences most directly on operators and maintenance organisations, since undetected or unrectified damage will lead to aircraft being unserviceable. The initial and recurring inspection windows create ongoing obligations that transform what may otherwise be discretionary manufacturer guidance into mandated regulatory work for all affected 767 operators within the AD’s geographic reach.

This AD establishes mandatory duties for operators and maintenance organisations and sets out limited acceptance rights relating to prior actions and FAA AMOC approvals. The principal duties and rights are:

Duties

• Conduct mandated inspections. Operators must "Carry out detailed inspections for damage to the wire bundles, power drive unit (PDU) wiring and wire attaching hardware, supports and sleeving located in the forward and aft lower lobe cargo compartments" following the Boeing SB Accomplishment Instructions applicable to their model (Requirement 1).

• Timing obligations. Operators must perform the initial inspection "Within 36 months after the effective date of this Directive" and then repeat the inspections "at intervals not to exceed 24,000 hours time in service or 72 months, whichever occurs first" (Compliance). Maintaining accurate hours-in-service and calendar schedules is thereby required.

• Rectify deficiencies before further flight. Any damage or deficiencies discovered must be rectified, with rectification completed "Before further flight after the Requirement 1 inspections" (Requirement 2). This makes detected defects a pre-flight grounding condition.

• Follow Boeing SB Accomplishment Instructions. The inspections are to be performed "in accordance with the Accomplishment Instructions" of the specified Boeing SBs (Requirement 1). The operator is obliged to use those SB procedures unless an accepted AMOC applies.

Rights and acceptances

• Acceptance of prior work. The AD expressly accepts actions "accomplished before the effective date of this Directive in accordance with Boeing SB 767-25-0376, dated 17 November 2005 (for Model 767-200, -300 and-300F series aeroplanes) or Boeing SB 767-25-0377, dated 17 November 2005 (for Model 767-400ER series aeroplanes); are considered acceptable for compliance with the corresponding actions specified in this Directive." That allows operators that already carried out the earlier SB inspections and rectifications before 25 October 2007 to treat that work as compliant for those particular actions.

• Acceptance of FAA-approved AMOCs. The AD states that "Later revisions of the above SB(s), approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2007-16-18, are considered acceptable for compliance with the equivalent Requirements of this Directive." This provides a defined route to use later Boeing SB revisions, but only where those revisions have FAA AMOC approval to the referenced FAA AD.

Delegated decision-making and documentation

• The AD ties the technical standard to Boeing SB Accomplishment Instructions and FAA AMOC approvals, rather than creating a bespoke technical standard within the AD text. That delegates technical detail to the OEM documents and the FAA's AMOC process, while the AD requires conformity to those documents.

• The text mandates rectification "Before further flight" but does not set out record-keeping formats. Standard regulatory practice would require operators keep evidence of compliance, though the AD itself does not specify the exact form or filing procedure for records.

Constraints and lack of express options

• The AD does not provide alternative inspection methods except through the FAA AMOC route for later SB revisions. There is no express provision in the AD text permitting local deviations from the SB method except where a later SB revision has FAA AMOC approval and is therefore "considered acceptable."

• The AD does not state processes for requesting exemptions or relief from CASA in the text provided. Rights to seek relief under other regulatory mechanisms or to use other AMOC channels are not detailed in this document.

In summary, the AD creates mandatory inspection and rectification duties tied to Boeing SB procedures and sets two specific acceptance routes (pre-effective compliant work and FAA-approved AMOCs for later SB revisions) as the limited "rights" to treat certain alternative actions as compliant.

The text of AD/B767/231 itself sets out mandated technical obligations but does not include an express penalties schedule or an enforcement clause within the document provided. The AD states the actions required, the timing for compliance, and the authority issuing the directive, but it does not specify fines, administrative penalties, or civil or criminal sanctions for non-compliance within the text supplied.

What the AD does show about enforcement and authority:

• Issuing authority. The AD is issued by the Civil Aviation Safety Authority as indicated by the signature block: "Charles Lenarcic, Delegate of the Civil Aviation Safety Authority" (signature dated 7 September 2007). This identifies CASA as the responsible regulator for issuing the directive and thus the body that would oversee compliance.

• Compliance deadlines and operational consequences. The AD establishes clear compliance obligations and timing: initial inspection "Within 36 months after the effective date" and repeat intervals "not to exceed 24,000 hours time in service or 72 months" (Compliance), and rectification "Before further flight" (Requirement 2). These provisions create an operational standard that CASA will expect operators to meet.

• Cross-reference to FAA AD. The AD explicitly references FAA AD 2007-16-18 Amdt 39-15157. It accepts FAA-approved AMOCs for later SB revisions as acceptable for compliance. That cross-reference shows a regulatory coordination element but does not itself create enforcement mechanisms.

Missing enforcement detail within the text

• No fines or sanctions are specified. The AD text does not list specific monetary penalties, licence consequences, or enforcement procedures for non-compliance.

• No stated inspection/audit or reporting regime. The AD mandates inspections and rectifications but does not specify how compliance is to be reported to CASA, how CASA will audit or verify compliance, or whether operators must submit a compliance report. The AD does not provide timeframes or formats for notifying CASA of completed work.

Practical enforcement implications for affected parties

• Although the AD does not state penalties, the issuing regulator (CASA) retains enforcement tools under the broader aviation regulatory framework outside the specific text of this AD. Those tools may include administrative enforcement action, suspension of operations, or other measures permitted under the Civil Aviation Act or related legislation, none of which are detailed in this document.

• The requirement that defects be rectified "Before further flight" imposes an operational enforcement mechanism in that an aircraft with unrectified findings cannot legally continue operations under the terms of the AD. That imposes an immediate practical sanction,aircraft downtime,until rectification is completed.

• Acceptance of FAA AMOC approvals implies that reliance on certain FAA decisions will be treated as adequate for compliance. If operators use later SB revisions or AMOCs and those are later found not to meet the AD's expectations, the AD text does not outline a remediation path; such matters would be resolved by the regulator.

In summary, AD/B767/231 sets mandatory technical and timing obligations but does not itself enumerate penalties or describe enforcement mechanics. Enforcement would therefore proceed under the broader regulatory and administrative powers of the Civil Aviation Safety Authority, and non-compliance has at least the immediate operational consequence of preventing further flight of aircraft with unrectified defects.

This AD explicitly cross-references and integrates other regulatory and OEM documents into its compliance regime, producing direct interactions with foreign regulatory instruments and with Boeing service documentation. The AD’s interactions with other rules and documents are limited to the text shown, and those interactions are as follows.

Integration with Boeing service documentation

• The AD makes Boeing service bulletins the operative inspection standards: inspections must be "in accordance with the Accomplishment Instructions of Boeing Service Bulletin (SB) 767-25-0376, Revision 1, dated 9 February 2007 (for Model 767-200, -300 and -300F series aeroplanes) or Boeing SB 767-25-0377, Revision 1, dated 9 February 2007 (for Model 767-400ER series aeroplanes); as applicable" (Requirement 1). By doing so, the AD embeds OEM technical instructions into the regulatory compliance framework. That interaction means operators must obtain and follow those SB Accomplishment Instructions to meet their regulatory obligations under this AD.

Cross-acceptance with FAA AD and AMOC process

• The AD references "FAA AD 2007-16-18 Amdt 39-15157" and accepts FAA AMOC approvals as an acceptance path for later SB revisions: "Later revisions of the above SB(s), approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2007-16-18, are considered acceptable for compliance with the equivalent Requirements of this Directive." This creates a cross-acceptance mechanism whereby an FAA AMOC for the referenced FAA AD makes a later Boeing SB revision acceptable under this AD.

• The practical legal effect is that FAA regulatory action and certification approvals become relevant evidence of compliance for Australian operators subject to this AD. That reduces the need for separate CASA technical approvals for every later SB revision where the FAA has already approved an AMOC for the FAA AD.

Interaction with prior OEM SB actions

• The AD accepts work done before the effective date using earlier Boeing SBs: "Actions accomplished before the effective date of this Directive in accordance with Boeing SB 767-25-0376, dated 17 November 2005 ... or Boeing SB 767-25-0377, dated 17 November 2005 ... are considered acceptable for compliance" (Requirements). That treats prior OEM-initiated work, done before the AD became effective, as compliant with the AD. It avoids duplicative rework obligations for operators who already implemented the earlier SB instructions.

Implicit interaction with national aviation law and CASA's enforcement regime

• While the AD itself does not state the enforcement mechanisms or penalties, by virtue of being issued by CASA, it operates within the Civil Aviation regulatory framework. The AD imposes binding obligations that CASA will expect operators to meet under whatever enforcement powers CASA has under applicable aviation legislation; those broader legal instruments are not reproduced in the AD text, but their existence is implicit in CASA issuing a compulsory directive.

No explicit interaction with other Australian statutes in the AD text

• The AD does not reference other Australian Acts, regulations, or administrative procedures in the provided text, apart from the CASA signature. It therefore relies on CASA’s authority and on the operator’s pre-existing obligations under the aviation regulatory regime without specifying those instruments.

Limitations of cross-jurisdictional acceptance

• The AD accepts FAA AMOCs, but it does not state whether CASA will accept AMOC approvals from other authorities or whether CASA has an independent AMOC process. The specific cross-acceptance is limited to FAA AMOC approvals to FAA AD 2007-16-18.

Overall, the AD functions as a point where manufacturer service bulletins, an FAA AD and its AMOC mechanism, and CASA regulatory authority intersect. The AD imports technical content from Boeing SBs, recognises prior SB actions, and creates legal effect for FAA-approved AMOCs in the Australian compliance context, while leaving enforcement mechanics to CASA’s broader regulatory powers.

The AD text itself contains limited explicit amendment history. What it does record is the effective date, references to prior versions of the Boeing service bulletins, and acceptance of later SB revisions approved by the FAA as AMOCs. The specific amendment-relevant items recorded in the document are:

• Effective date. The AD states "This Airworthiness Directive becomes effective on 25 October 2007" (Compliance). That is the instrument-wide effective date for the mandatory obligations contained in this AD.

• Signature and date. The directive bears the signature block "Charles Lenarcic, Delegate of the Civil Aviation Safety Authority" dated "7 September 2007." That provides the issuance date and the delegated signatory.

• Prior Boeing SB versions accepted. The AD recognises actions accomplished before the AD’s effective date if they were performed in accordance with earlier Boeing SBs dated 17 November 2005: "Actions accomplished before the effective date of this Directive in accordance with Boeing SB 767-25-0376, dated 17 November 2005 (for Model 767-200, -300 and-300F series aeroplanes) or Boeing SB 767-25-0377, dated 17 November 2005 (for Model 767-400ER series aeroplanes); are considered acceptable for compliance with the corresponding actions specified in this Directive." This records an explicit retrospective acceptance for specified earlier OEM documents.

• Acceptance of later SB revisions via FAA AMOC. The AD provides a forward-looking acceptance rule: "Later revisions of the above SB(s), approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2007-16-18, are considered acceptable for compliance with the equivalent Requirements of this Directive." That sets an approval path for later SB revisions, subject to FAA AMOC approval.

• Cross-reference to FAA AD record. The AD includes a note: "Note: FAA AD 2007-16-18 Amdt 39-15157 refers." That links this AD to the FAA's corresponding AD and thereby records a regulatory lineage to that FAA action.

No explicit subsequent amendments recorded

• The text provides no record of subsequent amendments to AD/B767/231 itself. There are no later AD revision numbers, addenda, supersessions, or cancellation notices included in the provided document.

Implications for operators tracking changes

• Operators must treat this AD as effective from 25 October 2007 and must account for the initial 36-month window from that date for the first inspection. Where operators implemented the Boeing SBs dated 17 November 2005 before the effective date, those earlier actions are treated as compliant for the corresponding requirements.

• For later Boeing SB revisions, the AD’s mechanism for acceptance is limited to FAA AMOC approval to FAA AD 2007-16-18. Operators must monitor the FAA AMOC process and the FAA AD history if they intend to rely on later SB revisions as compliant under this AD.

In sum, the amendment history contained in the AD is limited to the effective date, acceptance of specified prior SB versions, and a defined pathway for accepting later SB revisions conditioned on FAA AMOC approval. The AD itself does not record later changes or amendments to the directive in the supplied text.

The document AD/B767/231 provided contains no reference to litigation, disputes, appeals, or judicial or administrative reviews. It does not cite any legal proceedings, nor does it record any challenges to the directive, the Boeing service bulletins it references, or the FAA AD it cross-refers to.

What the AD does include relevant to potential disputes

• It sets mandatory technical requirements and acceptance mechanisms (e.g., acceptance of FAA AMOCs). That creates a regulatory framework within which disputes could theoretically arise about compliance sufficiency, scope of "detailed inspections," adequacy of rectification, or whether a given later SB revision and FAA AMOC adequately address the AD's requirements.

• The AD accepts prior actions performed in accordance with Boeing SBs dated 17 November 2005. That acceptance clause could be relevant in any dispute concerning whether earlier actions were performed in strict conformity with the earlier SBs; again, the AD itself does not record any such disputes.

Absence of litigation record in the text

• Because the supplied AD does not reference court decisions, administrative rulings, or other litigation-related documents, there is no litigation history to summarise from the source. Any litigation involving the AD, CASA, Boeing, or the FAA would fall outside the text provided.

Consequences for legal research

• If a practitioner needs to know whether this AD was subsequently litigated, challenged, amended through court order, or the subject of enforcement proceedings, that information is not contained here and would require searching administrative and judicial records outside the AD text.

In short, the AD as presented records no litigation history. It establishes mandatory obligations but does not document any legal disputes about those obligations within the text supplied.

The AD text contains specific features and implicit operational consequences that can create compliance traps if not properly managed. Below are concrete "gotchas" rooted in the AD wording and structure.

1. Scope is model-based, not serial-number filtered

• The AD applies to "All Model 767-200, -300, -300F and -400ER series aeroplanes" (Applicability). There is no carve-out by serial number, configuration, or modification history in the text. Operators cannot assume inapplicability simply because a given aircraft has a modified cargo compartment unless that modification is reflected in a later SB/AMOC explicitly accepted by the FAA and thus acceptable under this AD.

2. The AD delegates the inspection method to Boeing SBs

• The AD requires inspections "in accordance with the Accomplishment Instructions" of the specified Boeing SBs (Requirement 1). The AD does not itself specify what "detailed inspection" means. If an operator diverges from the SB technique or scope, the AD offers only the FAA AMOC acceptance route for later SB revisions. Reliance on an alternate inspection method without an accepted AMOC risks non-compliance.

3. Two-part timing regime, both hours and months

• Repeat intervals are "not to exceed 24,000 hours time in service or 72 months, whichever occurs first" (Compliance). Operators must track both flight hours and calendar time. Missing either metric can produce an inadvertent overrun. Record-keeping systems must capture hours-in-service and calendar compliance windows precisely.

4. Rectification is a pre-flight requirement

• Any defects identified "must be rectified" and that rectification is required "Before further flight" (Requirement 2). This elevates many inspection findings from maintenance work that can be deferred to an entry that grounds the aircraft until fixed. That can lead to unexpected AOG costs and schedule disruption.

5. Acceptance of prior SB work is limited

• The AD accepts work performed before the AD effective date only if it followed Boeing SBs dated 17 November 2005. Work done earlier or to other standards may not be accepted. Operators relying on earlier or informal inspections must verify that the prior work was done to those exact SB versions.

6. Reliance on FAA AMOC approvals has limits

• Later revisions of the SBs are acceptable only if "approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2007-16-18" (Requirements). The AD does not state whether CASA will independently approve different AMOCs, nor does it accept AMOCs from authorities other than the FAA within the text. Operators wanting to rely on later SB revisions must check the FAA AMOC status for the FAA AD and ensure the AMOC covers the revision as framed.

7. The AD does not spell out reporting or record-keeping formats

• The directive does not set out how or when to report compliance to CASA, or what documentation is required to evidence compliance. Operators must apply standard maintenance record practices, but that leaves room for different interpretations about sufficiency. Prepare to retain Boeing SB compliance records, inspection findings, rectification actions, and dates in a clear audit trail.

8. Potential coordination issues between manufacturers and regulators

• The AD uses Boeing SBs as the technical source and the FAA AMOC process as the route for acceptance of later SB revisions. That means an operator relying on a later SB revision must check FAA actions, not just Boeing publications, which can complicate multi-jurisdictional compliance planning.

9. No penalties detailed in the AD

• The AD does not contain explicit penalty clauses, but non-compliance will create operational risk and potential regulatory action through CASA’s broader enforcement powers. Operators should not assume lack of express penalties equates to lax enforcement.

10. Operational and logistical burdens underestimated

• The inspections are "detailed" and cover forward and aft lower lobe cargo compartments, including wire bundles, PDUs, attaching hardware, supports and sleeving. Access to these areas can be time-consuming, require removal of cargo compartment liners, and necessitate qualified electrical maintenance staff. Parts and labour for rectification may not be quickly available, increasing downtime risk.

Each of these gotchas flows directly from the AD wording. Operators should map them to internal compliance, maintenance planning, spare parts provisioning, and record-keeping systems to reduce the risk of inadvertent non-compliance or operational disruption.

The AD sets out a clear, constrained compliance pathway. The following steps convert the textual requirements into an actionable checklist operators and maintenance organisations can follow, grounded in the AD’s own instructions.

1. Confirm applicability to your fleet

• Verify that the aircraft in your fleet are within the AD’s scope: "All Model 767-200, -300, -300F and -400ER series aeroplanes" (Applicability). Document which tail numbers will be subject to this AD.

2. Obtain and review the referenced Boeing Service Bulletins

• Acquire the applicable Boeing SB: SB 767-25-0376 Revision 1 dated 9 February 2007 for 767-200, -300 and -300F, or SB 767-25-0377 Revision 1 dated 9 February 2007 for 767-400ER (Requirement 1). The AD mandates inspections "in accordance with the Accomplishment Instructions" of those SBs; review those instructions in full before planning maintenance.

3. Schedule the first inspection within the required window

• The AD requires the initial inspection "Within 36 months after the effective date of this Directive" (Compliance). Since the AD became effective on 25 October 2007, the first inspection was due within 36 months of that date for each affected aircraft. For present-day retrospective compliance work, confirm whether the aircraft in question had the earlier SB actions done prior to the effective date and whether those actions are recorded as per the AD’s acceptance clause.

4. Prepare for recurring inspections

• Set up a monitoring mechanism to ensure inspections recur "at intervals not to exceed 24,000 hours time in service or 72 months, whichever occurs first" (Compliance). Ensure your maintenance tracking system alerts on both hours and calendar thresholds to avoid inadvertent overruns.

5. Execute the detailed inspections per the SB Accomplishment Instructions

• Carry out the inspections on "wire bundles, PDU wiring and wire attaching hardware, supports and sleeving located in the forward and aft lower lobe cargo compartments" as the SB Accomplishment Instructions specify (Requirement 1). Ensure personnel performing the inspections are trained to the level required by the SB and maintain records of the exact inspection scope performed.

6. Rectify any defects before further flight

• If the inspection reveals damage or deficiencies, perform the corrective actions mandated by the Boeing SBs, and complete rectification "Before further flight after the Requirement 1 inspections" (Requirement 2). Plan to have replacement parts, wire harnesses, sleeving, and appropriate consumables on hand or available on short notice, as rectifications will ground the aircraft until completed.

7. Document work thoroughly

• Maintain records showing the date of each inspection, the hours-in-service and calendar status at the time of inspection, the findings, and the corrective actions taken. Although the AD does not specify a reporting format, retain Boeing SB workcards, signed accomplishment records, and parts invoices as evidence for audit or regulatory inspection.

8. Check for prior compliance acceptance

• If work was performed before the AD effective date using Boeing SBs dated 17 November 2005, document and retain the records that show the prior work followed those exact SB versions. The AD accepts such prior actions as compliant: "Actions accomplished before the effective date ... in accordance with Boeing SB ... dated 17 November 2005 ... are considered acceptable" (Requirements).

9. If relying on later SB revisions, confirm FAA AMOC approval

• Where intending to follow a later Boeing SB revision rather than Revision 1, confirm that the later revision has been "approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2007-16-18" because only such FAA AMOC approvals are "considered acceptable for compliance with the equivalent Requirements of this Directive" (Requirements). Maintain documentation of the FAA AMOC approval to support reliance.

10. Coordinate with CASA if in doubt

• The AD is issued by the Civil Aviation Safety Authority and signed by its delegate. If there is any uncertainty,for example, whether a particular AMOC or alternate inspection process will be accepted,engage CASA through the normal regulatory contact channels to obtain clarity before deviating from the SB Accomplishment Instructions.

11. Prepare operational contingencies

• Because rectification is a pre-flight requirement, ensure flight planners and dispatchers are aware of the grounding risk and that commercial and contractual parties are briefed on potential AOG outcomes resulting from inspection findings. This reduces scheduling and contractual surprises.

12. Maintain supply chain readiness

• Given that inspections may identify wiring, attaching hardware, supports or sleeving that require replacement, establish procurement lines for the parts likely to be needed and verify lead times to reduce downtime.

By following these steps and keeping the required Boeing SB Accomplishment Instructions and FAA AMOC documentation available as the primary technical references, operators can align their maintenance planning and records to the express terms of AD/B767/231.