AD/B727/217 - Fuel Tank Safety

The Directive is structured around three core concepts: hardware modification, maintenance-program binding, and reliance on manufacturer service instructions subject to FAA AMOC approval.

1. Hardware modification

   • The primary technical action is replacement/installation of ground fault interrupter (GFI) relays for the main and auxiliary fuel pump systems, together with other specified actions set out in Boeing ASB 727-28A0128 (Requirement 1). For a defined subset of aeroplanes (Groups 5-18 in that ASB) additional physical modifications to the GFI relay panel in the electronic equipment bay and to panels in the flight compartment are required (Requirement 2(a) and 2(b)). The ASBs are the detailed engineering instructions referenced for how to perform those changes.

2. Maintenance programme binding

   • Operators must revise their approved maintenance programme to incorporate two specific Airworthiness Limitations, 28-AWL-16 and 28-AWL-17, from Boeing Document D6-8766-AWL Revision August 2007 (Requirement 3). Once those AWLs are incorporated, the Directive expressly forbids using alternative inspections or inspection intervals unless the FAA approves an AMOC to paragraph (h) of FAA AD 2009-05-03. That makes the AWLs mandatory for the aircraft covered, subject to FAA AMOC.

3. Deference to FAA and Boeing ASBs

   • The AD ties compliance to Boeing ASBs and to FAA approvals. The Directive instructs operators to follow the Accomplishment Instructions of Boeing ASB 727-28A0128 and, if applicable, ASB 727-28A0130 (Requirement 1 and Requirement 2). It also states that later revisions of those ASBs, if approved by the FAA as AMOCs to FAA AD 2009-05-03, are acceptable for compliance with this Directive (Note). Additionally, the Directive identifies FAA AD 2009-05-03 as a cross-reference. The manufacturer performed the "fuel system reviews" that gave rise to the Directive (Background).

Conceptually, the AD converts a manufacturer-detected safety hazard into mandatory physical modification and maintenance obligations for operators of affected Boeing 727s. The safety focus is on eliminating two ignition sources: electrical arcing/burnthrough in fuel pump connectors/end caps, and increased pump temperature from uncommanded pump operation that could ignite fuel-tank fumes. The Directive enforces both a one-off modification state (install hardware) and an ongoing compliance state (mandatory AWLs with restricted ability to vary intervals or inspections absent FAA approval). The document makes the FAA the gatekeeper for any alternate compliance route, and uses Boeing ASBs as the prescriptive method for performing the work.

The Directive’s applicability field is precise and operator-facing. It applies to "Model 727, 727C, 727-100, 727-100C, 727-200, and 727-200F series aeroplanes, certificated in any category; as identified in Boeing Alert Service Bulletin (ASB) 727-28A0128, dated 4 April 2008" (Applicability). That phrasing means any Boeing 727 in those model lines is in scope if it is listed in the Boeing ASB specified. The inclusion of "certificated in any category" covers transport, freight, private, or other civil categories, subject to the ASB-identification step.

Stakeholders who bear the direct operational burden include:

• Aircraft owners and operators of affected Boeing 727 variants, since they must accomplish the modifications and maintenance-program revisions set out in Requirements 1-3 within the specified timeframe (Compliance).
• Maintenance organisations and technicians responsible for carrying out the ASB Accomplishment Instructions, because the AD directs work to be accomplished "by accomplishing all the applicable actions specified in the Accomplishment Instructions" of the ASBs (Requirement 1; Requirement 2).
• Those responsible for approved maintenance programmes, because the operator must incorporate the specified AWLs into the approved programme (Requirement 3).
• The manufacturer (Boeing) and the FAA in a regulatory role: Boeing supplied the ASBs and conducted the fuel-system reviews cited in the Background; the FAA acts as the authority able to approve AMOCs and later ASB revisions as acceptable for compliance (Note; Background).

Who pays and who decides

• The Directive itself does not state who pays for parts and labour. Operational logic within the AD indicates the operator/owner is the party responsible for accomplishing the required actions and revising the maintenance programme, so they will incur the cost of parts, labour, and downtime.
• Decision-making is split: CASA issued the Directive and fixed the compliance obligations and timing; the FAA is identified as the authority that may approve AMOCs and later ASB revisions for alternative compliance. Boeing provides the ASBs and the Airworthiness Limitations to be incorporated.

Operational effects on different operator types

• Commercial carriers and freight operators will need to schedule the hardware installations and maintenance-program changes to meet the 60-month window, and the Directive’s prohibition on alternative intervals unless an FAA AMOC is obtained will constrain local discretion on inspection regimes once the AWLs are adopted.
• Smaller operators, private owners, or those operating in specialised categories are included where their aircraft are "certificated in any category" and are identified in the ASB. Those operators will need to source parts and technical competence to perform the specified modifications or contract maintenance organisations that can do so.

Geographic and regulatory cross-border effect

• The AD is an Australian instrument issued by CASA, referencing Boeing ASBs and an FAA AD (FAA AD 2009-05-03). The text explicitly accepts later ASB revisions only if the FAA approves them as AMOCs, so the FAA’s determinations have de facto cross-jurisdictional effect for this Directive (Note). The practical implication is that operators worldwide with affected Boeing 727s will need to coordinate with both CASA and, for AMOCs or ASB revisions, the FAA and Boeing.

Duties

1. Installations and Accomplishment Instructions

   • Operators must "install new ground fault interrupter (GFI) relays for the main fuel tanks and the auxiliary fuel tank pumps" and perform "all the other specified actions" specified in the Accomplishment Instructions of Boeing ASB 727-28A0128 (Requirement 1). This is a mandatory duty delineated by the AD.

2. Group-specific hardware

   • For aeroplanes identified as Groups 5 through 18 in ASB 727-28A0128, operators must also perform the actions in Boeing ASB 727-28A0130, which include installation of new ground blocks, track, switch mounting bracket, relay mounting bracket, toggle switches, relays and changes to wire bundles in the GFI relay panel in the electronic equipment bay, and installation of new circuit breakers and lights plus wire-bundle changes on the third crewman's P6 and P4 panels (Requirement 2(a) and 2(b)).

3. Approved maintenance programme revision

   • Operators must revise the approved maintenance programme by incorporating Airworthiness Limitations 28-AWL-16 and 28-AWL-17 from Section D of Boeing Document D6-8766-AWL Revision August 2007 (Requirement 3). The Directive explicitly states that after accomplishing this revision, "no alternative inspections or inspection intervals may be used, unless the inspections or intervals are approved by the United States Federal Aviation Administration (FAA) as an alternative means of compliance (AMOC) to paragraph (h) of FAA AD 2009-05-03." That makes the AWLs binding unless an FAA AMOC is obtained.

4. Timing

   • Requirement 1 must be completed "within 60 months after the effective date of this Directive." Requirements 2 and 3 are to be completed "concurrently with Requirement 1" (Compliance). The AD became effective 7 May 2009 (Compliance).

Rights and limited flexibility

1. AMOCs through FAA

   • The AD provides a limited pathway for alternatives: operators may use "later revisions of ASB 727-28A0128 or 727-28A0130, approved by the FAA as AMOCs to FAA AD 2009-05-03," and such FAA-approved revisions "are considered acceptable for compliance with the equivalent Requirements of this Directive" (Note). The right to pursue an AMOC rests with the operator and requires FAA approval.

2. Scope of applicability

   • The AD’s obligations apply only to aeroplanes identified in the specified Boeing ASB. If an operator’s aeroplane is not identified in ASB 727-28A0128, the AD’s requirements will not apply to that specific aircraft. Determining applicability requires referencing the ASB and the aircraft’s serial and configuration data.

Delegations and roles

1. CASA as issuer

   • The Directive was issued by the Civil Aviation Safety Authority (CASA), and a CASA delegate signed the document on 26 March 2009. CASA sets the compliance obligation and effective date for Australian operators.

2. Boeing as technical source

   • Boeing authored the ASBs and the Airworthiness Limitations which the AD relies on for technical detail and inspection intervals. The AD directly instructs operators to follow Boeing’s Accomplishment Instructions.

3. FAA as approver of alternatives

   • The FAA is the approving authority for AMOCs and for acceptance of later ASB revisions as equivalent means of compliance. The AD cross-references FAA AD 2009-05-03 and makes FAA approval the gate to alternative inspections or intervals and revised ASB acceptance.

Documentation and recordkeeping implications

• Operators must update their approved maintenance programmes to include AWLs 28-AWL-16 and 28-AWL-17 from the specified Boeing document. That revision will need to be documented and submitted where required by the operator’s regulatory framework, and thereafter the aircraft will be subject to the inspection regimes and intervals mandated by those AWLs unless an FAA AMOC overrides them (Requirement 3).

The Directive does not state compensation, cost recovery mechanisms, or grant waivers other than AMOCs through the FAA. The instrument makes clear that compliance is mandatory within the specified timeframe, with FAA involvement as the sole channel for alternate compliance.

The text of the Directive does not set out specific civil or criminal penalties for non-compliance, nor does it detail the enforcement mechanisms that CASA would apply. What the AD does establish are mandatory compliance obligations and a compliance timeframe, which are enforceable by CASA under its statutory powers and regulatory processes outside the text of this Directive. The document itself specifies what must be done and when, but does not include a penalty schedule, infringement notices, or prosecution provisions.

Enforcement mechanisms implied by the Directive’s structure

• The Directive imposes mandatory work (installations per ASBs and maintenance-programme revision) and a compliance deadline. In practical regulatory systems, failure to comply with an AD can affect an aircraft’s continuing airworthiness and its legal ability to be flown. The AD’s clear linkage of required modifications and maintenance limitations means that an aircraft that has not complied within the 60-month period for Requirement 1 (and concurrently for Requirements 2 and 3) may be considered non-compliant with its continuing airworthiness obligations. The Directive therefore creates regulatory risk to the operator if actions are not completed.

Role of AMOCs in enforcement flexibility

• The only pathway for approved deviation from the mandated inspections or intervals is an FAA-approved AMOC to paragraph (h) of FAA AD 2009-05-03, or acceptance of later ASB revisions by the FAA as AMOCs for the relevant FAA AD (Requirement 3; Note). That centralised approval mechanism acts as a controlled avenue for relief, which regulators can consider when assessing compliance and enforcement discretion.

Practical enforcement consequences to expect (inferred from Directive mechanics)

• CASA may require evidence of compliance as part of maintenance records or regulatory oversight activities. Since the AD requires incorporation of specific AWLs into the approved maintenance programme and installation of specified hardware, inspectors would typically check maintenance records, modified part numbers, work-order completion forms, and updated maintenance-program documentation to verify compliance.
• The Directive’s effectiveness date (7 May 2009) and the 60-month compliance window provide a clear timeline for enforcement action after the deadline, and CASA could reasonably treat continued operation of an affected aeroplane past that date without accomplishment of the AD as a breach of continuing airworthiness obligations.

Absence of penalties in the text

• Because the AD text does not state penalties or an enforcement process, any specific fines, grounds for grounding an aircraft, licence consequences for responsible engineers, or criminal liabilities would derive from the broader regulatory regime under which CASA operates and not from this Directive’s text itself. The Directive’s practical enforcement weight comes from its incorporation into ongoing continuing-airworthiness oversight rather than from internal penalty clauses.

Operators should therefore treat the AD’s requirements as compulsory compliance obligations subject to regulatory verification and potential regulatory action if not met, and should plan to obtain FAA AMOCs if they seek approved alternatives to the specified inspections or intervals.

The Directive explicitly cross-references and integrates with other regulatory instruments and manufacturer documents. The key external legal and normative instruments named in the text are Boeing Alert Service Bulletins ASB 727-28A0128 (dated 4 April 2008) and ASB 727-28A0130 (dated 30 April 2008), Boeing Document D6-8766-AWL Revision August 2007 (Airworthiness Limitations), and United States Federal Aviation Administration AD 2009-05-03 (Amdt 39-15827).

Binding effect of non-regulatory documents

• The AD makes Boeing’s ASB Accomplishment Instructions the prescriptive technical procedure for carrying out the required modifications (Requirement 1; Requirement 2). While ASBs themselves are manufacturer-issued service information and are not regulatory instruments, this AD converts those ASB instructions into mandatory regulatory obligations for operators to accomplish the specified actions. The Directive therefore elevates Boeing’s technical instructions into enforceable regulatory requirements for affected aircraft in Australia.

Interaction with FAA airworthiness directives and AMOC process

• The AD explicitly cites FAA AD 2009-05-03 and cross-references the FAA’s AMOC process. It makes FAA-approved AMOCs the exclusive route to use alternative inspections or inspection intervals after incorporation of the specified AWLs ("no alternative inspections or inspection intervals may be used, unless the inspections or intervals are approved by the United States Federal Aviation Administration (FAA) as an alternative means of compliance (AMOC) to paragraph (h) of FAA AD 2009-05-03") (Requirement 3). The Directive also accepts later revisions of the Boeing ASBs as acceptable for compliance only if those revisions are "approved by the FAA as AMOCs to FAA AD 2009-05-03" (Note). That establishes a specific reliance on FAA determinations for alternative compliance even though this is an Australian AD. The FAA thus serves as the adjudicator for acceptable technical variations or later service-document incorporation.

Implications for operators across jurisdictions

• Because the AD ties its acceptance of alternative technical documents and inspection deviations to FAA approvals, operators who seek to propose alternate means of compliance will need to engage the FAA processes, even if the aircraft is operated in Australia. That creates an interaction where an Australian regulator defers on technical equivalence or alternatives to a US regulator’s approval process. The document frames FAA AMOCs as the authorised mechanism for deviation from the AD’s strict requirements.

Maintenance programme governance

• Requirement 3 mandates the incorporation of specified AWLs from Boeing Document D6-8766-AWL into the approved maintenance programme. Once incorporated, those AWLs govern inspection tasks and intervals, and the AD prohibits alternative regimes unless an FAA AMOC is obtained. The AWLs are therefore elevated into the regulatory maintenance schedule for affected aircraft, again linking manufacturer-prescribed limits with regulatory compliance.

No internal conflicts or exemptions stated

• The AD does not indicate any exceptions to its application other than AMOCs approved by the FAA or later ASB revisions approved by FAA as AMOCs. It does not reference any other Australian statutory provisions that would override or modify its requirements, nor does it provide a domestic AMOC pathway through CASA within the text. That absence means the operator’s domestic regulatory interaction is effectively bound to the options set out in the Directive: comply per Boeing ASBs and the AWLs, or seek FAA AMOC approval to deviate.

Summary of interaction mechanics

• Manufacturer service documents (ASBs and AWLs) are made regulatory via the AD.
• FAA AD 2009-05-03 and the FAA AMOC process are central to any acceptable deviation or adoption of later ASB revisions.
• CASA issued the AD and set the compliance date and obligations, but placed the avenue for alternate methods of compliance through FAA approvals.
• Operators must therefore coordinate technical implementation with Boeing service instructions and with FAA processes where an alternative to the AD’s requirements is sought.

The Directive includes several explicit dates and references that constitute its amendment and provenance history as recorded in the instrument.

Issuance and effective dates

• The AD is signed by James Coyne as a delegate of the Civil Aviation Safety Authority on 26 March 2009 ("James Coyne, Delegate of the Civil Aviation Safety Authority, 26 March 2009") and the AD becomes effective on 7 May 2009 ("This Airworthiness Directive becomes effective on 7 May 2009.").

Referenced FAA action

• The AD notes "FAA AD 2009-05-03 Amdt 39-15827 refers." That cross-reference indicates that this CASA AD aligns with or follows a related FAA AD action (the FAA AD number and amendment are given in the instrument).

Boeing service documents and revision notes

• The AD requires compliance with Boeing ASB 727-28A0128 dated 4 April 2008 (Applicability; Requirement 1). For certain groups, it requires actions "in accordance with the Accomplishment Instructions of Boeing ASB 727-28A0130, dated 30 April 2008" (Requirement 2). The AD also requires incorporation of AWLs 28-AWL-16 and 28-AWL-17 of Section D of "Boeing 727-100/200 Airworthiness Limitations (AWLs)," Document D6-8766-AWL, Revision August 2007 (Requirement 3).

Acceptance of later revisions

• The AD records that "Later revisions of ASB 727-28A0128 or 727-28A0130, approved by the FAA as AMOCs to FAA AD 2009-05-03, are considered acceptable for compliance with the equivalent Requirements of this Directive." That clause provides a formal mechanism within the AD for accepting later manufacturer revisions, but only where the FAA has approved them as AMOCs to the FAA AD.

No domestic amendment provisions in text

• The AD text does not itself set out a procedure for domestic amendment or CASA grant of exemptions; instead it provides a pathway for compliance via FAA AMOC approval or following the ASBs as issued. The AD imposes fixed obligations and an effective date, and provides acceptance of future documents only on FAA approval.

Record of change

• The instrument as supplied does not list prior versions of the AD or show any amendments to the CASA Directive itself beyond the acceptance clause for later FAA-approved ASB revisions. The AD as presented appears to be the CASA instrument issued on the dates specified with the compliance schedule set relative to the effective date.

Implication for operators tracking changes

• Operators must track Boeing ASB revisions and FAA AMOC approvals because the AD specifically accepts later ASB revisions only if the FAA has approved them as AMOCs to the FAA AD. Any change to the technical instructions that an operator seeks to rely on will therefore require FAA approval to be accepted under this AD.

The text of the Directive does not identify any litigation history, court proceedings, or disputes arising from the Directive itself. It records the issuing delegate and dates but contains no references to legal challenges, appeals, or judicial review proceedings.

What the absence of litigation references means for a practitioner

• Because the AD text contains no litigation history, there is no source-grounded record here of any legal disputes over the Directive’s content, interpretation, enforcement, or application. Any inquiries about litigation would require search outside the AD text provided. The Directive itself is an administrative regulatory instrument; if disputes were to arise , for example, about the scope of applicability, the adequacy of Boeing ASBs, or the availability of alternative means of compliance , those would take place in fora outside this document and the AD does not set out any history of such events.

Practical consequence for counsel and compliance officers

• Legal advisers and compliance officers dealing with affected aircraft should not infer the existence of precedent or litigation outcomes from this AD text. The only authoritative follow-on material in the AD is the FAA AD cross-reference and the acceptance of FAA-approved ASB revisions as AMOCs; any case law or litigation precedent relevant to the AD’s interpretation would need to be sourced separately. The AD itself provides the obligations and the administrative framework for AMOCs but no litigation narrative.

The AD contains multiple specific wording points and cross-references that can create practical compliance pitfalls if overlooked. Below are concrete, source-grounded risks and traps for operators and maintainers.

1. Applicability depends on the ASB-identification step

   • The AD applies to the enumerated 727 model series "as identified in Boeing Alert Service Bulletin (ASB) 727-28A0128, dated 4 April 2008" (Applicability). Operators must check the ASB to determine whether a specific airframe (based on serial number, configuration, modifications) is listed. A common operational mistake is assuming model-level applicability without verifying the aircraft is expressly identified in the ASB. If an aircraft is not identified in the ASB, the AD’s requirements do not apply as written.

2. Group-specific scope for Requirement 2

   • Requirement 2 applies only to aircraft identified as Groups 5 through 18 in ASB 727-28A0128. Misidentifying the group can lead to overwork or under-compliance. Operators must use the ASB’s grouping definitions to determine whether Requirement 2 applies to a given aircraft.

3. Concurrent timing requirement

   • The AD sets a 60-month deadline for Requirement 1 and requires Requirements 2 and 3 to be done "concurrently with Requirement 1" (Compliance). That means an operator cannot delay the maintenance-program revision or the Group 5-18 hardware work beyond the 60-month window. Treat the 60 months as the latest date by which all three requirements must be completed when applicable.

4. No alternative inspection or interval unless FAA AMOC to a specific FAA AD paragraph

   • After incorporating the AWLs, "no alternative inspections or inspection intervals may be used, unless the inspections or intervals are approved by the United States Federal Aviation Administration (FAA) as an alternative means of compliance (AMOC) to paragraph (h) of FAA AD 2009-05-03" (Requirement 3). The AD ties the acceptability of alternate inspection regimes to a specific paragraph (h) of FAA AD 2009-05-03. Operators seeking alternatives must ensure any AMOC sought specifically addresses that FAA AD paragraph; an AMOC referencing some other paragraph or another FAA AD might not satisfy this Directive.

5. Later ASB revisions accepted only if approved by FAA as AMOCs

   • The AD accepts "later revisions of ASB 727-28A0128 or 727-28A0130, approved by the FAA as AMOCs to FAA AD 2009-05-03" for compliance (Note). An operator cannot simply implement the latest Boeing ASB revision and presume compliance; the FAA must have approved that ASB revision as an AMOC to the FAA AD for it to be acceptable under this CASA AD.

6. Maintenance-program incorporation is binding

   • Incorporating the specified AWLs into the approved maintenance programme converts them into mandatory inspection tasks and intervals. Operators should not assume they can continue with previous inspection intervals or substitute local maintenance practices unless an FAA AMOC is obtained as required by the AD.

7. Potential work in flight compartment and electronic bay

   • Requirement 2 mandates work that includes "install new ground blocks, track, switch mounting bracket, relay mounting bracket, toggle switches, and relays, and make changes to the wire bundles in the GFI relay panel in the electronic equipment bay" and "install new circuit breakers and lights and make changes to wire bundles on the third crewman's P6 and P4 panels in the flight compartment" (Requirement 2(a) and 2(b)). Those are not purely underfloor access tasks; they involve wiring and cockpit panel modifications that may require specific approvals for electrical work and functional tests. Failing to account for necessary parts, certified technicians, and testing time is a practical risk.

8. Documentation and record‑keeping

   • The AD requires incorporation of AWLs into the approved maintenance programme but does not set out the paperwork process. Operators must ensure their maintenance-programme change control, records, and regulatory submissions reflect that incorporation. Absent clear documentation, an operator may struggle to evidence compliance.

9. Costs and downtime implicit, not specified

   • The AD does not provide any cost allowances or timelines for scheduling the required installations beyond the 60-month window. Operators who wait may face concentrated demand for certified parts and maintenance slots near the deadline. The AD’s silence on costs makes proactive scheduling prudent.

10. Reliance on FAA approvals

• The AD’s acceptance of alternatives and later ASB revisions depends on FAA approvals. For operators outside the United States, this presents an administrative burden and potential delay in securing AMOCs if the FAA’s processes are busy or if technical substantiation is required.

Identifying these gotchas from the AD text should guide operators to review ASB 727-28A0128 for group definitions and applicability, to plan for both electronic-bay and flight-deck wiring work, to prepare approvals for maintenance programme changes, to file AMOC requests in a timely way if alternatives are desired, and to keep comprehensive records demonstrating compliance with the AD and with Boeing’s Accomplishment Instructions.

Below is a stepwise, source-grounded compliance roadmap based solely on the Directive’s text. It is an operational checklist framed by the AD’s explicit requirements and cross-references.

1. Verify applicability

   • Obtain Boeing ASB 727-28A0128 (dated 4 April 2008) and check whether the specific airframe (serial number/configuration) is listed in the ASB. The AD applies only to the enumerated 727 models "as identified in Boeing Alert Service Bulletin (ASB)727-28A0128" (Applicability).

2. Identify group classification

   • If the aircraft is listed in ASB 727-28A0128, determine whether it is identified as part of Groups 5 through 18 inclusive. Requirement 2 applies only to those groups. Use the ASB’s grouping criteria to classify the aircraft correctly.

3. Plan for Requirement 1 (mandatory for all applicable aircraft)

   • Schedule the installation of new GFI relays for the main fuel tanks and auxiliary fuel tank pumps and complete "all the other specified actions" by following the Accomplishment Instructions of Boeing ASB 727-28A0128 (Requirement 1). The AD sets a compliance window: "Within 60 months after the effective date of this Directive" (Compliance). The AD became effective on 7 May 2009; therefore operators should have completed Requirement 1 within the 60-month window following that date.

4. Plan for Requirement 2 (Group 5-18 only)

   • For aircraft in Groups 5-18, schedule and perform the additional actions in Boeing ASB 727-28A0130 (dated 30 April 2008), specifically: a) Install new ground blocks, track, switch mounting bracket, relay mounting bracket, toggle switches, and relays, and make changes to wire bundles in the GFI relay panel in the electronic equipment bay (Requirement 2(a)). b) Install new circuit breakers and lights and make changes to wire bundles on the third crewman's P6 and P4 panels in the flight compartment (Requirement 2(b)).
   • Execute these works concurrently with Requirement 1 as required by the Directive (Compliance).

5. Revise the approved maintenance programme (Requirement 3)

   • Incorporate Airworthiness Limitations 28-AWL-16 and 28-AWL-17 from Section D of Boeing Document D6-8766-AWL, Revision August 2007, into the approved maintenance programme (Requirement 3).
   • After incorporation, do not use alternative inspections or intervals unless you obtain an FAA AMOC specifically addressing paragraph (h) of FAA AD 2009-05-03, as the AD disallows alternative inspections absent FAA approval.

6. Obtain FAA AMOC if alternatives are required

   • If you intend to use alternative methods, inspection tasks, or intervals instead of those specified in the AWLs or ASBs, prepare and submit an AMOC request to the FAA that addresses paragraph (h) of FAA AD 2009-05-03 (Requirement 3). The AD makes FAA approval the required pathway for alternate inspection regimes. Also, if you intend to rely on later revisions of ASB 727-28A0128 or 727-28A0130, those revisions must be "approved by the FAA as AMOCs to FAA AD 2009-05-03" to be acceptable under this AD (Note).

7. Use trained personnel and documented compliance evidence

   • Perform the installations and wiring changes per the ASB Accomplishment Instructions, using appropriately certificated maintenance organisations and technicians able to sign the work off per regulatory requirements. Keep detailed work orders, parts lists, and test results showing the GFI relays, ground blocks, brackets, panel modifications and circuit breaker/light installations were completed as required.

8. Update maintenance records and approved programme documents

   • Once AWLs are incorporated into the approved maintenance programme, document the revision and retain evidence that 28-AWL-16 and 28-AWL-17 have been added. Ensure the approved maintenance programme reflects the new tasks and intervals, and that records of completed tasks are maintained to demonstrate continuing compliance.

9. Coordinate with Boeing and regulatory authorities

   • For technical clarifications, refer to the specified Boeing ASBs and the Boeing Airworthiness Limitations document. For any acceptance of alternate means or later ASB revisions, liaise with the FAA for AMOC approvals as the Directive specifies FAA approval as the required source for acceptable deviations.

10. Monitor for later ASB revisions and FAA actions

    • The AD allows "later revisions of ASB 727-28A0128 or 727-28A0130, approved by the FAA as AMOCs to FAA AD 2009-05-03," to serve as compliant means (Note). Track Boeing’s ASB releases and FAA AMOC decisions to determine whether new ASB revisions are acceptable under this AD.

11. Treat the AD’s deadlines as firm

    • Requirement 1 must be done within 60 months of the AD effective date, and Requirements 2 and 3 are to be done concurrently with Requirement 1 (Compliance). Operators should plan forward maintenance and downtime to ensure these works are completed within the specified period.

12. Evidence for regulatory oversight

    • Expect CASA or other oversight bodies to request evidence of: (a) ASB applicability determination; (b) completion of installations per the ASB Accomplishment Instructions; (c) maintenance-programme revision incorporating the specified AWLs; and (d) any FAA AMOC approvals relied upon. Make sure to retain all relevant documentation to support these points.

Compliance summary

• Follow the Boeing ASB Accomplishment Instructions for hardware installations (ASB 727-28A0128; ASB 727-28A0130 where applicable).
• Incorporate AWLs 28-AWL-16 and 28-AWL-17 into the approved maintenance programme and do not substitute inspections or intervals without an FAA AMOC to paragraph (h) of FAA AD 2009-05-03.
• Complete Required actions within 60 months of the AD effective date, with group-specific additional work done concurrently.
• Use FAA AMOCs as the authorized mechanism for any proposed alternative compliance or for acceptance of later ASB revisions.

Operators should treat this AD as an enforceable continuing-airworthiness obligation and plan resources and documentation accordingly to meet the AD’s prescriptive technical actions and maintenance-programme constraints.