AD/B737/251 - Smiths Industries Aerospace Flight Management Computers

The Directive rests on a small set of technical and regulatory concepts anchored in aircraft continuing airworthiness management. Applicability is narrow and precise: it is triggered by the intersection of airframe model, the presence of two Smiths FMCs with the particular part numbers 171497-05-01 or 176200-01-01, and the installed OPS version being one of U10.3, U10.4, U10.4A or U10.5. The Directive therefore operates as a configuration-specific mandate, not a blanket fleet requirement (Applicability).

The required technical remedy is software maintenance and verification. The core software items referenced are the FMC OPS, the model/engine database (MEDB) software where applicable, the navigational database (NDB) software, and the software options database (OPC). When complying via the optional SB route, the common display system (CDS) OPC software for the left and right display electronic units may also be required. The Directive specifies installation into both left and right FMCs and then mandates configuration checks to ensure the correct items are installed; if a configuration check finds incorrect software, reinstallation is required before further flight (Requirements 1a, 1b, 2; optional SB paragraphs).

Regulatory coordination is explicit: the Directive incorporates by reference Boeing Alert Service Bulletins (ASBs) as the Accomplishment Instructions that set out the technical steps. It also recognises later revisions of those ASBs or SBs as acceptable for compliance, provided they are approved by the United States Federal Aviation Administration as an Alternate Method of Compliance (AMOC) to FAA AD 2005-19-19 (Later revisions accepted as AMOC; Note 3). Thus, the Directive links CASA’s regulatory mandate to FAA technical findings and to manufacturer service instructions.

Timing and operational effect are concrete concepts. Requirement 1 must be completed within 180 days of the Directive’s effective date; Requirement 2 imposes an operational constraint, because where incorrect software is found on a configuration check, the aircraft must not fly until the reinstall is completed. The Directive therefore creates both a planning window and an immediate operational stop-gap for affected aeroplanes (Compliance; Requirement 2).

In short, the main regulatory mechanism is a prescriptive, software-focused continuing airworthiness instruction, tied to specific service documents and cross-referenced to an FAA airworthiness action, with defined compliance timing and an explicit before-flight constraint where incorrect software is discovered.

Primary legal and operational obligations fall on certificated operators of the specified Boeing 737 models that have two Smiths FMCs of part number 171497-05-01 or 176200-01-01, and where the installed OPS is one of the listed versions (Applicability). The Directive is technology- and configuration-specific; therefore, only aeroplanes that meet all listed criteria are in scope. Maintenance organisations, licensed aircraft engineers and other personnel who perform software installs and configuration checks on FMCs will have hands-on duties under the Directive, because installation and verification are performed by maintenance action “in accordance with” Boeing ASBs or SBs (Requirement statements).

There are downstream effects for operational personnel. Flight crews and flight operations managers face an operational constraint where Requirement 2 applies, because the Directive states that if incorrect software is found on any FMC during the required configuration checks, the software must be reinstalled before further flight. That creates an immediate “no further flight” condition until the reinstall is done for the affected aeroplane (Requirement 2; Compliance for Requirement 2).

Manufacturers and suppliers are implicated as well. Boeing ASBs and SBs are identified as the prescriptive technical documents; Smiths Industries Aerospace is the FMC supplier identified by part number. Navigational database suppliers and entities that provide model/engine databases may be involved because the Directive requires the installation of MEDB and NDB software where applicable (Requirements 1 and optional SB paragraphs).

Regulators and their delegates are an affected administrative audience. This Directive was issued by a CASA delegate (signature block), and it explicitly refers to FAA AD 2005-19-19 and FAA-approved AMOCs; thus, CASA, the FAA and their delegated engineering/continuing airworthiness staff are participants in the compliance validation and in considering later revisions and AMOCs (Note 3; signature).

Commercial consequences fall on operators and maintenance providers. Operators bear scheduling and labour costs to install updated OPS and related software and to perform configuration checks within the 180-day window; they also bear the operational costs when an aircraft is grounded pending reinstall under Requirement 2. Maintenance providers will need to allocate technical labour, possibly order updated software or databases, and follow Boeing ASB/SB Accomplishment Instructions to deliver a compliant outcome (Requirements 1, 2; optional SBs).

The Directive does not identify other categories such as lessors, insurers or third-party suppliers explicitly, but the requirement’s nature means these stakeholders may be engaged through contractual, operational and regulatory compliance channels.

Duties

• Identify applicability. Operators must determine whether each aeroplane meets the Directive’s Applicability criteria, that is, the specified 737 models with two Smiths FMCs bearing part number 171497-05-01 or 176200-01-01 and installed with OPS version U10.3, U10.4, U10.4A or U10.5 (Applicability).

• Implement the installation actions. Requirement 1 requires, in accordance with the Accomplishment Instructions of Boeing ASB 737-34A1801 or ASB 737-34A1821 as applicable, installation of: the updated OPS, a compatible MEDB software if applicable, the current NDB software, and the OPC software in both left and right FMCs (Requirement 1a).

• Perform configuration checks. Requirement 1b requires configuration checks of both FMCs to confirm that the updated OPS, compatible MEDB (where applicable) and OPC software are correctly installed.

• Reinstall if incorrect software found. Requirement 2 requires that if a configuration check finds incorrect OPS, MEDB or OPC software on any FMC, the operator must reinstall the applicable software in accordance with the ASB before further flight.

• Optional SB compliance route. The Directive allows an alternate technical route: installation of OPS version U10.6 and associated items via Boeing SB 737-34-1768 or SB 737-34-1879 is acceptable to comply with the corresponding Requirements, provided the SB Accomplishment Instructions and the Directive’s required sub-paragraphs are followed, including installation of CDS OPC software where applicable and the same obligation to reinstall before further flight if incorrect software is found (optional SB paragraphs).

• Timing obligations. The Directive prescribes specific timing: Requirement 1 is to be met within 180 days of the Directive’s effective date; Requirement 2 must be met before further flight following a configuration check that reveals incorrect software (Compliance).

Rights and decision nodes

• Use of FAA-approved AMOC. The Directive expressly recognises that later revisions of the ASBs or SBs, if approved by the FAA as an Alternate Method of Compliance to FAA AD 2005-19-19, are acceptable for compliance with the equivalent Requirements of the Directive. That provides operators and maintenance organisations with an explicit right to rely on FAA-approved updates to the service documents as alternative, acceptable means to meet CASA’s Directive (later revisions as AMOC; Note 3).

• Choice between ASB and SB path where specified. The Directive identifies the ASBs as the required Accomplishment Instructions but allows, as optional and acceptable, the alternative SBs installing U10.6, thereby creating a choice for operators able to satisfy the SB sub-paragraph conditions. That choice matters operationally because the SBs prescribe a later OPS version (U10.6) and potentially additional software items such as CDS OPC (optional SB paragraphs).

• Delegation and decision authority. The Directive shows regulatory decision-making resides with CASA’s delegate who issued it, and the FAA has an explicit role in approving later revisions of manufacturer service bulletins as AMOCs (signature; Note 3).

Summary of obligations: operators must identify applicability, install the required updated software and databases in both FMCs as prescribed by the Boeing ASB or accepted SB path, perform and act on configuration checks, and meet the timing requirements. The Directive gives operators a regulated right to use FAA-approved ASB/SB revisions as AMOCs as the means of compliance.

The text of this Directive does not state specific statutory penalties, fines or remedial enforcement procedures. The instrument is an Airworthiness Directive issued by a Civil Aviation Safety Authority delegate and sets mandatory compliance actions and timeframes: Requirement 1 is required within 180 days of the Directive’s effective date, and Requirement 2 requires reinstallation of incorrect software found during configuration checks before further flight (Compliance; Requirements 1 and 2). The Directive’s operational language therefore creates direct compliance constraints, including an express “before further flight” condition that operates as an immediate limitation on an aeroplane’s lawfully permitted operation until the specified maintenance action is completed (Requirement 2).

Because the Directive itself does not specify enforcement mechanisms, the document is silent on how CASA would proceed administratively or what penalties may attach to non-compliance. The logical enforcement levers implicit in the Directive’s form are procedural and operational: CASA or its delegated inspectors can assess continued airworthiness via maintenance records, logbooks and evidence of compliance with the ASB/SB instructions referenced by the Directive, and operational control can be exercised in practice through the “before further flight” constraint that makes a non-compliant aeroplane practically unairworthy for operations requiring compliance. However, those enforcement practices and any statutory penalty provisions that CASA might invoke are not described in the Directive’s text.

Given the absence of penalty provisions in the Directive itself, affected entities will need to treat the Directive as a mandatory continuing airworthiness measure and assume that regulatory oversight (for example, airworthiness inspections and acceptance of maintenance accomplishment forms) will be the practical mechanism by which compliance is verified. The Directive’s cross-reference to FAA AD 2005-19-19 and to the Boeing ASBs and SBs embeds the compliance actions in established manufacturer and foreign regulatory guidance, which will typically be used by regulators and auditors to evaluate conformity, but the precise enforcement steps and sanctions remain outside the text of this Directive.

The Directive explicitly cross-references and relies on external technical and regulatory instruments. It cites FAA AD 2005-19-19 Amdt 39-14284 (Note 3; Background) and states that later revisions of Boeing ASBs or SBs approved by the FAA as an Alternate Method of Compliance to that FAA AD are acceptable for compliance with the equivalent Requirements of the Directive. Thus, the Directive creates a direct regulatory interaction by treating FAA approvals of manufacturer document revisions as valid AMOCs for CASA’s Directive purposes. That makes a foreign regulator’s approval a recognised compliance pathway inside the Australian regulatory instrument.

The Directive makes Boeing Alert Service Bulletins 737-34A1801 and 737-34A1821 the required Accomplishment Instructions for the required installations and configuration checks. This makes manufacturer-issued service documents a de facto prescriptive element of national continuing airworthiness regulation: following those ASBs is the specified means to comply. Likewise, the Directive accepts certain Boeing Service Bulletins (SB 737-34-1768 and SB 737-34-1879) as an optional route to compliance where their sub-paragraph conditions are met. The effect is that manufacturer technical guidance interacts directly with CASA’s regulatory obligations for continuing airworthiness.

There is a modal interaction between operational regulatory constraints and technical service instructions. The Directive imposes a “before further flight” constraint where incorrect software is found during configuration checks, which interacts with operational safety requirements that typically prevent aircraft carrying passengers or operating commercially if required continuing airworthiness actions have not been completed. While the Directive itself does not reproduce the broader statutory aviation safety legislation or its enforcement provisions, it forms part of the corpus of continuing airworthiness instruments that together determine whether an aeroplane is in an airworthy condition.

The Directive does not reference other domestic statutes, criminal provisions, or economic regulatory instruments in its text. It therefore primarily interacts with external technical documents (Boeing ASBs/SBs) and with an identified foreign regulator’s airworthiness directive (the FAA AD), creating a regulatory interplay where CASA accepts manufacturer instructions and FAA approvals as the mechanisms by which the mandated changes are to be implemented and by which later revisions may be accepted.

Finally, because the Directive imposes specific maintenance actions and timing requirements, it will intersect in practice with contractual arrangements between operators, lessors and maintenance providers: the Directive’s technical prescriptions will determine maintenance scope, timing and cost allocation among contract parties, although those contractual outcomes are not addressed in the Directive itself.

The Directive’s own text memorialises key dates and the source materials’ versions, and it sets out how later revisions may be incorporated. The headline metadata shows the document title AD/B737/251 and an edition indication 12/2005. The Directive was signed by a CASA delegate, Jayaprakashan Ambali, on 12 October 2005, and it became effective on 24 November 2005 (signature block; effective date). The Boeing Alert Service Bulletins referenced as the required Accomplishment Instructions are dated 15 July 2004 (ASB 737-34A1801 for Models 737-600, -700, -700C, -800 and -900; ASB 737-34A1821 for Models 737-300, -400 and -500). The Boeing Service Bulletins identified as optional routes are dated 11 August 2005 (SB 737-34-1768 for the -600/-700/-700C/-800/-900 group and SB 737-34-1879 for the -300/-400/-500 group) (ASB and SB dates).

The Directive explicitly contemplates future technical revisions: it states that later revisions of the above ASBs or SBs, approved by the FAA as an Alternate Method of Compliance to FAA AD 2005-19-19, are considered acceptable for compliance with the equivalent Requirements of the Directive. That clause provides a formal mechanism by which subsequent technical updates to the manufacturer’s guidance, once approved by the FAA as AMOCs to the FAA AD, become acceptable means to satisfy CASA’s Directive. In practice this creates a delegated amendment pathway that ties CASA acceptance to FAA approval of ASB/SB revisions.

There is also an embedded cross-reference to FAA AD 2005-19-19 Amdt 39-14284, which is the foreign regulatory action the Directive relies upon (Note 3). The Directive does not itself list any subsequent amendments to its own text beyond the AMOC acceptance mechanism and the dates and service bulletin references already noted. No further internal amendment entries or later CASA amendment numbers are included in the provided text.

Operationally, the implication of the amendment mechanism is that the technical content of the required work can be updated through the normal manufacturer/FAA route and thereafter be relied upon as acceptable by CASA, without the need for a fresh CASA Directive for each minor revision, provided the FAA approves those revisions as AMOCs to the cited FAA AD. The Directive therefore incorporates a standing process by which later, FAA-approved technical changes to the ASBs/SBs will be treated as acceptable compliance means within the life of this Directive.

The text of this Directive does not include any litigation history, references to court decisions, or records of legal challenges. No cases are named in the source material. Therefore, from the provided document alone there is no recorded litigation history to report.

Absent a concrete litigation record in the source text, it is still possible to identify where disputes might arise as a matter of legal risk and administrative review, based solely on the Directive’s content. Potential dispute areas,grounded in the Directive’s own prescriptions,include: whether an aeroplane meets the strict Applicability criteria, particularly where part numbers and OPS versions must both align; whether the ASB Accomplishment Instructions were followed precisely where the Directive requires installation “in accordance with” the ASBs; the interpretation of the Directive’s optional SB pathway and whether all its sub-paragraph conditions, such as installing CDS OPC software “if applicable,” have been satisfied; and the meaning and practical effect of the “before further flight” requirement in situations where an operator disputes the necessity or scope of a reinstall.

Commercial disputes between operators and maintenance organisations or manufacturers could arise over who bears the cost or operational loss arising from the mandated updates, because the Directive prescribes work but does not allocate commercial responsibility for parts, labour or aircraft downtime. Likewise, disagreements could arise over the acceptability of later ASB/SB revisions as AMOCs where the FAA approval status is contested or where CASA’s acceptance of that FAA approval is in dispute; the Directive expressly makes FAA-approved later revisions acceptable, so a timing mismatch between FAA approval and CASA recognition could be a locus of contention.

From an administrative-law perspective, challenges might focus on whether the Directive properly followed regulatory processes, though the Directive itself shows a CASA delegate signature and cites FAA ADs and Boeing service documents; any administrative review would turn on process and justification matters not detailed in the text. The Directive is silent on appeal or review pathways in its own terms.

Because no litigation is recorded in the source, the above observations do not allege the existence of disputes or court challenges; they merely identify, based on the Directive’s structure and content, the kinds of legal or contractual disagreements that can arise in the lifecycle of such continuing airworthiness mandates.

Several practical pitfalls and attention points are embedded in the Directive’s specific wording and in its interaction with ASBs/SBs.

• Narrow applicability requires careful verification. The Directive applies only where the aeroplane has two Smiths FMCs with the specified part numbers and specific OPS versions (Applicability). Operators should not assume fleet-wide applicability; a misread of the part numbers or OPS version could lead to unnecessary work or missed compliance obligations.

• Both left and right FMCs must be updated and checked. The Directive repeatedly specifies installation and configuration checks for the left and right FMCs. A common mistake would be to update only one unit or to treat a single-unit check as sufficient; the requirement concerns dual-FMC installations and mandates that both be corrected and verified (Requirement 1a, 1b).

• The “before further flight” constraint is operationally binding. If a configuration check uncovers an incorrect OPS, MEDB or OPC, the Directive requires reinstall before further flight (Requirement 2). That creates immediate operational downtime risk; operators cannot assume temporary operational continuance without completing the reinstall.

• Choice of technical document matters by airframe group. The Directive directs different ASBs depending on model groups: ASB 737-34A1801 for Model 737-600, -700, -700C, -800 and -900 series; ASB 737-34A1821 for Model 737-300, -400 and -500 series (Requirement 1). Using the wrong ASB could produce non-compliant maintenance actions.

• Optional SB path has tighter or additional requirements. The optional SB route installs OPS version U10.6 and may require installing CDS OPC software in display electronic units “if applicable.” The SB paragraph also requires configuration checks and the same reinstall-before-flight rule if incorrect software is found. Failing to follow the SB Accomplishment Instructions to the letter could render the optional path non-compliant (optional SB paragraphs).

• MEDB, NDB and CDS OPC are “as applicable” items. The Directive requires installation of MEDB and CDS OPC only “if applicable,” which creates a decision point for maintenance personnel. Errors in assessing applicability, or omission of a database component because of misinterpretation, can produce incomplete compliance. The Directive requires that compatible versions are installed and verified (Requirement 1; optional SB paragraphs).

• Later revisions accepted only with FAA approval as AMOC. The Directive accepts later ASB/SB revisions only if approved by the FAA as an AMOC to FAA AD 2005-19-19. Relying on a later ASB/SB revision that lacks that specific FAA-approved AMOC status may leave the operator non-compliant with the Directive (later revisions as AMOC; Note 3).

• No explicit record-keeping or documentation language is contained in the Directive. The Directive mandates actions and timing but does not set out required maintenance records or forms in its text. Practitioners should note the Directive’s silence here and prepare to demonstrate compliance through maintenance accomplishment records consistent with normal continuing airworthiness practice, because the Directive itself provides no evidentiary prescriptions.

• Timing mismatch risk. Requirement 1 must be completed within 180 days of the effective date (Compliance). Operators who do not plan resources or parts in time risk concentrated workload and possible aircraft unavailability close to the deadline.

• Cross-jurisdictional reliance may complicate acceptance. The Directive’s reliance on FAA AD and FAA AMOC approvals means that changes in FAA approval status, or delays in obtaining FAA AMOC, could affect the availability of the later-revision means of compliance recognised by the Directive.

These “gotchas” derive from the Directive’s precise language and its reliance on manufacturer and FAA technical instruments. Each point is a concrete mechanism by which operational, compliance and contractual risk can arise.

Follow these steps, using the Directive’s language and the referenced Boeing ASBs/SBs as the technical authorities for the work. Each step points back to the Directive’s relevant provision.

1. Confirm applicability. For each aeroplane, verify: model is one of 737-300, -400, -500, -600, -700, -700C, -800 or -900; the aircraft is equipped with two Smiths FMCs having part number 171497-05-01 or 176200-01-01; and the installed OPS is U10.3, U10.4, U10.4A or U10.5. Only aeroplanes meeting all three criteria fall within the Directive (Applicability).

2. Select the correct Boeing service document. If the aeroplane is a 737-600, -700, -700C, -800 or -900 series, use Boeing ASB 737-34A1801, dated 15 July 2004, as the Accomplishment Instructions. If the aeroplane is a 737-300, -400 or -500 series, use Boeing ASB 737-34A1821, dated 15 July 2004 (Requirement 1).

3. Consider the optional SB path if operationally preferable. If you prefer to install OPS version U10.6 and consolidate updates, use Boeing SB 737-34-1768 (for -600/-700/-700C/-800/-900) or SB 737-34-1879 (for -300/-400/-500), dated 11 August 2005, provided you follow the SB Accomplishment Instructions and the Directive’s SB sub-paragraphs exactly (optional SB paragraphs). Note that the SB path includes a requirement to install the CDS OPC software in left and right display electronic units if applicable, and requires configuration checks as well.

4. Procure updated software and databases. Obtain the updated OPS software specified in the chosen ASB or SB, the compatible MEDB software where applicable, the current navigational database (NDB) software, and the OPC software. If using SBs, obtain the CDS OPC software when applicable (Requirement 1a; optional SB paragraphs).

5. Schedule and perform installations for both FMCs. Perform the installation of the updated OPS and associated software in both the left and right FMCs in accordance with the Accomplishment Instructions of the applicable ASB or SB. Ensure licensed maintenance personnel follow the manufacturer-prescribed steps. The Directive requires both units to be addressed as the action is specified for left and right FMCs (Requirement 1a).

6. Execute configuration checks. After installation, conduct configuration checks of both FMCs to ensure the updated OPS, compatible MEDB where applicable, and OPC software are correctly installed, in accordance with the ASB/SB Accomplishment Instructions (Requirement 1b).

7. Reinstall if incorrect software is found, before further flight. If any configuration check reveals incorrect OPS, MEDB or OPC software on any FMC, reinstall the applicable software in accordance with the ASB or SB as applicable, and complete that reinstall before further flight of the aeroplane (Requirement 2).

8. Meet the timing requirement. Complete Requirement 1 within 180 days after the Directive’s effective date (Compliance). Treat Requirement 2 as an immediate operational constraint that must be satisfied before further flight following a configuration check that finds incorrect software.

9. Use FAA-approved later revisions where applicable. If a later revision of an ASB or SB exists and has been approved by the FAA as an AMOC to FAA AD 2005-19-19, that later revision is acceptable for compliance with the equivalent Requirements of the Directive. Confirm FAA AMOC approval status before relying on a later ASB or SB revision as the compliance method (later revisions as AMOC; Note 3).

10. Follow manufacturer instructions precisely and document work. Although the Directive itself is silent on a specific records regime, comply with standard continuing airworthiness record-keeping practice, and ensure that maintenance log entries, work orders and copies of the ASB/SB Accomplishment Instructions and any FAA AMOC approvals are retained and available for regulator verification. The Directive mandates actions “in accordance with” the ASBs/SBs, so maintain documentation that demonstrates strict conformity to those Accomplishment Instructions (Requirement statements).

11. Plan operational impacts. Because Requirement 2 requires reinstall before further flight if incorrect software is found, plan for possible aircraft downtime during configuration checks and for the worst-case reinstall duration. Schedule updates to spread workload and avoid last-minute concentration close to the 180‑day deadline.

12. Liaise with manufacturer and regulator where uncertainties arise. For technical ambiguities about applicability, database compatibility, or whether a software item is “applicable,” consult Boeing’s Accomplishment Instructions and, where necessary, seek clarification or an FAA AMOC if intending to rely on a later ASB/SB revision. The Directive accepts FAA-approved AMOCs as the mechanism for later revisions to be treated as acceptable compliance means (Note 3).

These steps are drawn directly from the Directive’s requirements and from the ASB/SB references the Directive prescribes. Completing the full sequence,identification, correct-service-document selection, procurement of updated software and databases, full installation in both FMCs, configuration checks, reinstall-before-flight where required, and timely completion within 180 days,meets the Directive’s stated obligations.