AD/B737/278 Amdt 1 - Elevator Input Torque Tube Assembly

The AD deploys a small set of interlocking legal and technical concepts to effect the safety intervention. First, applicability: the AD identifies affected aeroplanes as “Boeing Model 737 aeroplanes as listed in Table 1,” and the table breaks the fleet into two groups (737‑100 through ‑500 series; and 737‑600 through ‑900 series) with a specific Boeing Alert Service Bulletin identified for each group (737‑27A1274 dated 17 February 2005, or later FAA‑approved revision; and 737‑27A1271 dated 16 December 2004, or later FAA‑approved revision). The phrase “or later FAA approved revision” is central to the AD’s flexibility and is explicitly preserved by the amendment.

Second, mandated action: the Requirement clause compels modification of the elevator input torque tube assembly “by doing all the actions in accordance with the Accomplishment Instructions of the applicable service bulletin in Table 1.” This ties the legal obligation directly to the manufacturer’s Accomplishment Instructions in the identified ASB, making those instructions the operative technical method that demonstrates compliance.

Third, compliance timing: the AD fixes a compliance period , “Within 60 months after 16 March 2006.” That is a temporal obligation that converts the safety requirement into a firm operational deadline (60 months measured from the reference date specified). The AD also states that “The compliance time remains unchanged by this issue of the Directive,” signalling that Amendment 1 did not alter the original deadline.

Fourth, amendment mechanism and alternate method of compliance: Amendment 1 is described as “issued to allow use of a later FAA approved Boeing Alert Service Bulletin, as specified in Table 1, as an alternate method of compliance.” That is a procedural concept: the AD both prescribes a specific ASB and also allows, by amendment, the use of later FAA‑approved revisions of that ASB as acceptable alternatives.

Fifth, safety rationale: in Background the AD records the factual predicate that a restriction in the pilot’s elevator input control system was reported, and that a design review “discovered possible failure modes that could lead to a jam” of the elevator control system. The AD therefore frames its action as preventative,“intended to prevent loss of elevator control and consequent reduced controllability of the aeroplane.”

Sixth, cross‑jurisdictional referencing: the AD refers to FAA AD 2005‑26‑03 Amdt 39‑14424. The AD therefore sits in a regulatory network: it relies on (and accepts) FAA‑issued technical material and approvals as part of the Australian airworthiness regime.

These core concepts,applicability, mandated action tied to Accomplishment Instructions, time-limited compliance, acceptance of later FAA‑approved ASB revisions, recited safety history, and cross‑reference to FAA ADs,compose the AD’s structure and determine how operators, maintenance providers and regulators must act to meet the directive.

The AD affects the operators and owners of the Boeing 737 models listed in Table 1. Specifically, Table 1 lists two groups:

• Boeing 737‑100, ‑200, ‑200C, ‑300, ‑400 and ‑500 series aeroplanes, for which the applicable ASB is 737‑27A1274, dated 17 February 2005, or later FAA‑approved revision.
• Boeing 737‑600, ‑700, ‑700C, ‑800 and ‑900 series aeroplanes, for which the applicable ASB is 737‑27A1271, dated 16 December 2004, or later FAA‑approved revision.

That language makes clear that the class of affected parties is defined by aircraft model and the ASB applicable to that model. The Requirement directs that the modification be done “in accordance with the Accomplishment Instructions of the applicable service bulletin,” which means that whoever has operational responsibility for an affected airframe (the operator, owner or their agent) must ensure the work is completed. The AD does not name particular operators or maintenance organisations; it binds the aircraft by model.

Operational stakeholders affected include:

• Aircraft owners/operators who must allocate funds, schedule the modification within the compliance window, and ensure the prescribed actions are completed on each affected aircraft.
• Maintenance providers and workshops that will perform the modification, to the extent their customers require their services; they will need access to the referenced Boeing ASB and any later FAA‑approved revisions permitted by the amendment.
• Regulatory compliance teams within airlines and maintenance organisations that must track AD applicability against their fleets and manage scheduling to meet the deadline “Within 60 months after 16 March 2006.”
• Supply chain actors that supply parts, tooling or technical support needed to carry out the Accomplishment Instructions in the ASBs.

The AD does not specify an alternative population (for example, it does not purport to affect non‑listed models, nor does it identify equipment serial ranges, registration numbers, or operators by name). The AD’s binding reach is therefore model-limited, and compliance turns on matching an airframe to the Table 1 listing and then performing the ASB actions on that airframe.

The amendment language also affects the behaviour of those parties: it allows use of a later FAA‑approved revision of the identified ASBs as an alternate method of compliance. That creates decision space for operators and maintainers to adopt an updated ASB revision approved by the FAA rather than strictly the ASB revision date printed in Table 1, which may affect procurement of parts or the scope of work.

Duties:

• Modification duty: The central legal duty imposed by the AD is to “Modify the elevator input torque tube assembly by doing all the actions in accordance with the Accomplishment Instructions of the applicable service bulletin in Table 1 of this AD.” This is an obligation incumbent on the responsible party for each affected aeroplane.
• Timing duty: The AD sets a mandatory time window: complete the mandated modification “Within 60 months after 16 March 2006.” That converts the technical instruction into a time‑limited statutory duty.
• Use of specified ASBs: Operators must base the modification on the Accomplishment Instructions contained in the Boeing Alert Service Bulletin identified for their model in Table 1, or use a later FAA‑approved revision where permitted by the amendment.

Rights and procedural provisions:

• Alternate method allowance: Amendment 1 explicitly allows use of a later FAA‑approved Boeing Alert Service Bulletin “as an alternate method of compliance.” That is a limited right of operators and maintainers to comply using later FAA‑approved revisions of the ASB rather than the exact printed revision date in Table 1.
• Reference to FAA AD: The AD notes that “FAA AD 2005‑26‑03 Amdt 39‑14424 refers.” This inclusion signals that the FAA AD and associated approvals are relevant technical material; operators therefore have a right to rely on FAA approvals where the amendment allows.

What the text does not do (express omissions in the instrument):

• The AD does not specify procedural steps for documenting compliance (no recordkeeping clause appears in the provided text).
• The AD does not set out approval pathways beyond the “later FAA approved revision” language; it does not, for example, provide for CASA‑issued alternative methods of compliance in the text provided.
• The AD does not specify who must perform the modification (for example, it does not mandate use of CASA‑approved maintenance organisations or specific licences). It simply requires the actions be carried out in accordance with the Accomplishment Instructions.

Operational implications of duties and rights:

• The duty to follow Accomplishment Instructions ties the legal obligation to the manufacturer’s technical procedure. In practical terms, compliance requires obtaining the relevant Boeing ASB (or its later FAA‑approved revision) and executing the specified sequence of inspections, removals, replacements and installations specified in the Accomplishment Instructions.
• The amendment’s acceptance of later FAA‑approved revisions entitles operators to use updated procedures approved by the FAA, potentially reducing rework if Boeing issues an improved ASB after the ASB dates in Table 1.

All duties and rights cited above are stated in the AD text (Requirement; Table 1; Compliance; Amendment note; Background reference to FAA AD). The AD’s legal force is to convert a technical service instruction into a compulsory maintenance obligation with a fixed completion date and a narrow allowance for later FAA‑approved revisions.

The AD text provided does not contain explicit penalty clauses, monetary fines, or enforcement procedures. The document sets out a mandatory technical requirement (“Modify the elevator input torque tube assembly … in accordance with the Accomplishment Instructions of the applicable service bulletin in Table 1 of this AD”) and a compliance timeline (“Within 60 months after 16 March 2006”), and it records Amendment 1 and its effective date. It does not, within the supplied text, specify sanctions for non‑compliance, nor does it detail the specific enforcement mechanisms CASA will deploy to verify compliance.

What is explicit in the instrument and therefore relevant to enforcement inference:

• A time‑limited prescription: the AD converts a safety concern into an obligation with a specified deadline. That deadline (60 months after 16 March 2006) is an objective compliance metric the regulator can check against maintenance records and airworthiness status.
• Cross‑reference to FAA materials: the AD references FAA AD 2005‑26‑03 and ties compliance to the Accomplishment Instructions of specific Boeing ASBs (or later FAA‑approved revisions). This creates a technical benchmark for inspectors and auditors to compare actual maintenance work against the required ASB methods.

What the text does not say and what that implies for enforcement planning:

• The AD does not include an enforcement clause spelling out penalties or licensing consequences; it also does not prescribe a process for seeking exemptions or approved deviations within the text supplied. Therefore, any enforcement actions or penalties would arise from the broader statutory framework governing aviation safety (not contained in this AD text). Regulators, operators and their legal advisers must look to the enabling legislation and CASA enforcement policies outside this AD for the concrete penalty mechanics.
• Because the AD is explicit about the corrective actions and the compliance deadline but silent about recordkeeping and certification paperwork, operators should assume that maintaining documentary proof of the modification, and the ASB revision used, will be essential when dealing with CASA inspections or audits. The AD itself does not require these records, but the presence of an objective technical standard and deadline implies they will be material.

In short, the AD imposes a mandatory technical duty and a deadline, but the specific penalties and enforcement process do not appear in the supplied text. The AD does, however, create verifiable compliance criteria (work in accordance with specific ASB Accomplishment Instructions, completed within a stated time window), which regulatory inspectors can use to assess whether an aeroplane meets the Directive. Reference to FAA ADs and FAA‑approved ASB revisions further supplies comparative technical standards that will inform any enforcement review.

The AD explicitly interacts with material produced by the United States Federal Aviation Administration. The instrument refers to “FAA AD 2005‑26‑03 Amdt 39‑14424” and lists Boeing Alert Service Bulletins that are acceptable in their stated revision or “later FAA approved revision.” Amendment 1 is issued to allow “use of a later FAA approved Boeing Alert Service Bulletin, as specified in Table 1, as an alternate method of compliance.” Those passages show that this CASA AD imports FAA technical approvals as part of its compliance architecture.

Consequences of that cross‑referencing:

• Technical import: By specifying FAA ASBs and accepting later FAA‑approved revisions, the AD relies on another jurisdictional regulator’s technical approvals to define acceptable methods of compliance. The AD therefore operates in technical conjunction with FAA determinations; the FAA’s approval of a later ASB revision is treated as dispositive for the limited purpose of constituting an alternate method of compliance under this AD.
• Regulatory network: The AD sits within an international regulatory network where CASA can adopt or reference FAA safety directives and manufacturer ASBs rather than reproducing technical instructions in full. The AD’s text makes FAA materials part of the operative compliance regime for the listed Australian‑registered aircraft.

What the AD does not state explicitly:

• The AD does not, in the supplied text, reference specific provisions of Australian aviation statutes that give CASA authority to issue ADs, nor does it cite administrative law provisions concerning alternative methods of compliance beyond the explicit allowance for FAA‑approved ASB revisions. The instrument does not itself set out the legal basis for sanctions or appeals.
• The AD does not displace other ADs or maintenance requirements except by stating the compliance window “remains unchanged by this issue of the Directive.” That suggests continuity with an earlier Directive, and that this amendment is procedural (allowing later FAA‑approved ASBs) rather than substantive (it did not extend or shorten the compliance period).

Practical implications for affected parties:

• Operators should treat the FAA AD and the Boeing ASBs named in Table 1 as directly relevant to meeting CASA’s requirements. The AD’s text makes clear that later FAA‑approved revisions are acceptable, so operators should verify FAA approval status when selecting which ASB revision to use.
• For legal and compliance teams, the AD’s cross‑referencing means that reading the CASA AD alone is insufficient; one must also obtain and review the relevant Boeing ASB and the FAA AD referenced in the AD text to determine the exact scope of work and any FAA‑approved changes.

All interactions described here are grounded in the AD text’s references to the FAA AD and the “FAA approved revision” language set out in Table 1 and in the amendment note.

The AD text provided contains limited but concrete amendment history information. Key items in the amendment trail are:

• Reference and starting point: The compliance period is measured “Within 60 months after 16 March 2006,” which implicitly ties the original AD’s compliance clock to the 16 March 2006 reference date. The AD states that “The compliance time remains unchanged by this issue of the Directive,” indicating that the amendment did not change the original deadline.
• Amendment 1 purpose: The separate line under the table and the prefatory note both explain the substantive purpose of Amendment 1: “Amendment 1 is issued to allow use of a later FAA approved Boeing Alert Service Bulletin, as specified in Table 1, as an alternate method of compliance.” That is the principal change effected by this amendment.
• Dates and signatures: The AD notes that “This Amendment becomes effective on 7 August 2009,” and it bears the signature block “David Villiers, Delegate of the Civil Aviation Safety Authority, 4 August 2009.” The header also shows “10/2009 DM,” denoting the administrative or document marking for this amendment.
• Effective content: The AD explicitly states that, apart from allowing later FAA‑approved ASB revisions, “The compliance time remains unchanged by this issue of the Directive.” That indicates the amendment is limited in scope to procedural acceptance of later FAA‑approved ASBs, rather than materially changing the mandatory work scope or the deadline.

What the AD’s amendment history does not include (in the provided text):

• The AD does not reproduce the original AD text in full or list earlier amendment numbers other than the present “Amdt 1” notation. It does not include an explicit bibliographic history of the original AD’s issue date or the content of the original instrument beyond the compliance start date embedded in the compliance clause.
• The AD does not provide a version history of ASB revisions or a list of FAA approvals by date beyond the two ASB revision dates quoted in Table 1 (“dated 17 February 2005” and “dated 16 December 2004”) and the general allowance for later FAA‑approved revisions.

Taken together, the supplied text establishes a narrow amendment history: an initial AD with a compliance deadline measured from 16 March 2006, and an Amendment 1 effective 7 August 2009 issued to permit later FAA‑approved revisions of the specified Boeing ASBs to be accepted as alternative methods of compliance, while keeping the original compliance deadline unchanged.

The provided AD text contains no litigation history, case citations, or references to court decisions. The document mentions FAA AD 2005‑26‑03 Amdt 39‑14424 but does not record any disputes, appeals, or judicial review incidents connected to this CASA AD or the FAA AD. It does not name any litigants, arbitration outcomes, or prosecutorial actions.

For users seeking litigation context:

• The instrument itself supplies no record of litigation; it does not identify any challenges to the AD, nor does it summarise any court rulings about the AD’s validity or enforcement.
• Absent further documents or external records, the AD as provided stands as an administrative safety directive without attached litigation material.

Accordingly, the AD’s litigation history , within the scope of the supplied text , is empty. Any inquiry into enforcement cases, appeals against CASA ADs, or legal disputes over the Boeing ASB modifications would require consulting sources not contained in the AD document provided here.

Several practical and legal “gotchas” arise from the AD’s precise wording and its linkage to external technical material. These are matters that may catch operators, maintenance providers or compliance officers unprepared if they rely on an incomplete reading of the AD.

1. Applicability tied to Table 1 rather than a simple model list. The AD lists model groups and specific ASB references in Table 1. Operators must match their aircraft to the correct model grouping and the corresponding ASB. Misreading the table or applying the wrong ASB revision to the wrong model group would risk non‑compliance because the Requirement ties the legal duty to the “applicable service bulletin in Table 1.”

2. The instrument ties legal compliance to manufacturer Accomplishment Instructions. The Requirement mandates doing “all the actions in accordance with the Accomplishment Instructions of the applicable service bulletin in Table 1.” That makes the Accomplishment Instructions the operative technical benchmark; partial compliance with an ASB is not obviously acceptable under the AD’s plain text. Operators must therefore ensure they follow the full Accomplishment Instructions.

3. “Or later FAA approved revision” versus exact ASB dates. Table 1 lists specific ASB dates (737‑27A1274 dated 17 February 2005; 737‑27A1271 dated 16 December 2004) but appends “or later FAA approved revision.” Amendment 1 explicitly allows use of a later FAA‑approved ASB as an alternate method of compliance. The gotcha here is that not every later Boeing ASB revision is effective for compliance unless it is FAA‑approved. Operators must therefore verify FAA approval status of any later ASB revision they intend to use.

4. Compliance deadline arithmetic and the unchanged time. The AD requires completion “Within 60 months after 16 March 2006.” That yields a compliance deadline of 16 March 2011 for affected aircraft (60 months measured from the specified date). The AD also states “The compliance time remains unchanged by this issue of the Directive.” A gotcha is assuming that the Amendment extended or restarted the compliance window; it did not. Operators relying on the amendment to defer work beyond the original window would be mistaken.

5. No express documentation procedure in the AD text. The AD does not set out what documentary proof of compliance is required in the supplied text. The absence of an explicit recordkeeping clause is a practical pitfall: operators should not assume that documentation is unnecessary. Regulators will expect that the modification was done and be able to verify it; therefore, retaining work cards and the ASB revision used is prudent even though the AD does not say so.

6. Cross‑jurisdictional dependency. The AD imports FAA approvals into its compliance regime. A potential surprise is that a fleet operator may hold an Australian airworthiness registry but need to consult FAA approval records for later ASB revisions. If an operator uses a later ASB not actually FAA‑approved, the AD’s alternate‑method allowance would not apply.

7. Insufficient specificity about who must perform the work. The AD requires the actions be performed per the ASB but does not in the supplied text mandate a class of maintenance organisation or licence. Operators must therefore ensure that whoever performs the work is competent and authorised under applicable Australian maintenance regulations; failure by an unqualified party could produce non‑compliance or airworthiness approval problems.

8. Background factual uncertainty. The Background states that a restriction was reported and that design review “discovered possible failure modes” but that “the cause of the incident was indeterminate.” The gotcha for risk managers is that the AD prescribes a preventative modification without a concluded causal finding; the AD therefore imposes obligations to address possible failure modes even in the absence of a definitive root cause.

These points are all traceable to the AD text: Table 1 entries and their ASB dates and “or later FAA approved revision,” the Requirement clause tying compliance to Accomplishment Instructions, the Compliance clause specifying 60 months after 16 March 2006 and the unchanged compliance time, the Background paragraph about the reported restriction and indeterminate cause, and the amendment note allowing later FAA‑approved ASBs.

The AD sets a specific technical and temporal path for compliance. Compliance steps, drawn precisely from the AD text and the operative implications of its wording, are as follows:

1. Identify affected aeroplanes. Compare your fleet to Table 1. If your aeroplane is one of the 737 models listed in Table 1 (737‑100 through ‑500 group, or 737‑600 through ‑900 group), the AD applies to that airframe.

2. Obtain the applicable Boeing Alert Service Bulletin. For 737‑100 to ‑500 series: ASB 737‑27A1274 dated 17 February 2005 (or a later FAA‑approved revision). For 737‑600 to ‑900 series: ASB 737‑27A1271 dated 16 December 2004 (or a later FAA‑approved revision). Amendment 1 allows you to use a later FAA‑approved Boeing ASB as an alternate method of compliance; therefore, verify FAA approval status before adopting any later revision.

3. Use the ASB Accomplishment Instructions as the compliance method. The Requirement mandates performing “all the actions in accordance with the Accomplishment Instructions of the applicable service bulletin in Table 1.” That means each step, inspection, replacement or torque/adjustment specified in the Accomplishment Instructions must be completed.

4. Schedule and carry out the modification within the compliance window. The AD requires completion “Within 60 months after 16 March 2006,” which equates to completion by 16 March 2011. Ensure planning, parts procurement, and maintenance slots are arranged so the full work scope per the ASB is completed by that date.

5. Confirm the ASB revision and FAA approval status. If you intend to use a later ASB revision rather than the revision date printed in Table 1, confirm that the FAA has approved that revision (the AD’s amendment permits later FAA‑approved revisions to be used as alternate compliance). Document the FAA approval that authorises the revision used.

6. Execute the work using appropriate maintenance capability. The AD requires the technical work be done per the Accomplishment Instructions. While the AD does not specify required maintenance licences in the supplied text, operators should ensure the performing maintenance organisation and personnel are authorised under applicable Australian maintenance rules to perform structural and control‑system work.

7. Retain documentary evidence demonstrating the actions performed and the ASB revision used. Although the AD text does not specify recordkeeping in the provided text, the AD sets an objective standard that inspectors will verify against; therefore, retain work cards, sign‑offs, parts serial numbers, and the ASB revision/FAA‑approval documentation to demonstrate compliance.

8. Note the FAA cross‑reference. The AD references FAA AD 2005‑26‑03 Amdt 39‑14424. Consult that FAA AD and any related FAA documentation to understand any additional context or technical clarifications, particularly if relying on FAA‑approved ASB revisions as the alternate compliance method.

9. Treat the AD as a binding directive. The Requirement and Compliance clauses form a mandatory obligation under the AD as issued by CASA. Ensure your airworthiness management processes incorporate the AD and that affected aircraft are not released to service without completion of the specified actions per the ASB.

These steps are drawn from the AD’s Requirement, Table 1, Compliance clause, Amendment note, and Background references. They are operational instructions consistent with the AD text: identify applicability, obtain the ASB, perform all Accomplishment Instructions, meet the deadline, and verify any FAA approvals for later ASB revisions used.