AD/CF34/4 Amdt 1 - Main Fuel Control

The directive operates through a few technical and administrative primitives:

• Applicability by engine model and installation. The AD applies to General Electric CF34-1A, -3A, -3A1, -3A2, -3B and -3B1 series engines installed on, but not limited to, specified Bombardier/Canadair aircraft models CL-600-2A12, -2B16 and -2B19 (Applicability). The phrasing "installed on but not limited to" signals that the listed aircraft are examples and that the AD applies to affected engines regardless of aircraft type when the engine/part combination falls within the AD scope.

• Part-number and serial-number gating. The obligations are triggered by specific MFC part numbers (P/Ns 6078T55P02 through P10 inclusive) and by particular O-ring P/Ns (Buna-N P/Ns R1307P020 and R1307P141). Certain actions are also restricted to engines with serial numbers within specified ranges (for example CF34-3A1 engines SNs 807001 and up; CF34-3B and -3B1 engines SNs 872001 and up; CF34-1A, -3A and -3A2 engines SNs 350003 thru 350525) (Requirement 1 and 2).

• Dual compliance pathways. Where specified MFCs with particular O-rings are present, the AD offers two alternative corrective pathways: an O-ring material swap to Viton O-rings in accordance with ASBs (Requirement 1(a)), or,where applicable,installation of an MFC with an improved flange vent groove per ASB specifications (Requirement 1(b)). This creates a choice for operators between a part-substitution fix and a reworked or improved MFC assembly.

• Mandatory upgrade to improved overspeed protection. Regardless of the path chosen for the flange groove or O-ring replacement, the AD mandates installation of a "serviceable MFC" that incorporates improved overspeed protection modifications, or rework per GE ASBs, for a range of engine variants and aircraft installations. The AD provides precise ASB references and step sequences to follow (Requirement 3 and following paragraphs).

• Definition of terminating action and exclusion list. The AD expressly states that replacing an MFC with a serviceable MFC constitutes terminating action for the AD. It defines "serviceable MFC" functionally and then lists part numbers that are not serviceable and therefore cannot be relied upon to terminate obligations (Requirement, paragraph defining serviceable MFC and the non-serviceable P/Ns list).

• Reference to manufacturer service literature. Compliance is tied to the Accomplishment Instructions of specified GE Alert Service Bulletins or Service Bulletins and their revisions, with dates provided. The AD therefore delegates technical specification of how to perform the modification to manufacturer-issued ASBs.

• Temporal compliance triggers. The AD sets several compliance deadlines tied to calendar dates, engine removal events, MFC removal events, and inspection cycles: before 6 January 2000 for some items; at next engine or MFC removal for Others; at the next hot section inspection or within 53 months after effective date for specified items; within 4000 hours TIS or within 17 months after effective date for other items (Compliance).

• Regulatory provenance. The AD is issued under CAR 1998 Part 39 authorities (subregulation 39.1(1) cited in the preamble) and notes that it supersedes AD/CF34/3, incorporating FAA AD corrections per FAA AD 99-23-26R1 (Preamble and Background).

Those concepts create a ruleset where technical compliance depends on a combination of component identity, engine serial number, maintenance events, and adherence to narrowly referenced manufacturer instructions. The AD couples prescriptive technical fixes with precise compliance windows and an explicit terminating condition tied to installing specified "serviceable" hardware.

The AD designates responsibilities tied to aircraft and aeronautical products within its Applicability paragraph. Practically, the parties directly affected are:

• Aircraft operators and owners that have General Electric CF34 series engines installed on aircraft, specifically CF34-1A, -3A, -3A1, -3A2, -3B and -3B1 series engines, including but not limited to Bombardier/Canadair models CL-600-2A12, -2B16 and -2B19 (Applicability). The AD applies to affected engines irrespective of aircraft class when the specified engine and part conditions are met.

• Maintenance organisations and engineering departments that perform engine and fuel control maintenance, inspections and modifications. The AD requires actions to be performed "in accordance with the Accomplishment Instructions" of specified GE ASBs, which places technical execution on the maintenance provider responsible for conforming to those instructions (Requirement).

• Parts suppliers and MFC manufacturers. The AD specifies replacement parts by part number, including Viton O-rings P/Ns M83485-1-020 and 37B201714P130, and lists MFC part numbers that do not qualify as "serviceable." Suppliers that provide compliant MFCs, reworked units or the specified O-rings are the channels through which operators will obtain conformity.

• Civil Aviation Safety Authority and its delegate. The AD was issued by a CASA delegate as authority under CAR 1998 subregulation 39.1(1). The delegate's signature and the Gazette notification indicate CASA’s role in setting the compliance obligation and enforcing it under Part 39 rules (preamble and signature block).

• Potential downstream users of affected aircraft: passengers and airlines that rely on aircraft availability may be indirectly affected through downtime, inspection intervals and repair scheduling required by the AD.

Costs and decision authority fall primarily on aircraft operators and owners. The AD requires that the corrective action be taken "in relation to the aircraft or aeronautical product mentioned in the applicability section" and "in accordance with the instructions set out in the requirement section" and "at the time mentioned in the compliance section" (preamble). This places both the obligation to execute and the responsibility for timing and record-keeping on the operator and maintenance provider.

The instrument’s scope is determined by part numbers and serial numbers, so affected parties need technical records to determine if their engines/MFCs fall within the AD. Where the AD refers to serial number thresholds (for example CF34-3A1 SN 807001 and up), operators must check engine serial number registers to establish applicability for each airframe.

The AD’s referenced terminating action provision affects procurement decisions. Operators contemplating future purchases, exchanges or overhauls of MFCs must ensure that units meet the defined "serviceable" criteria; those supplying or selling non-serviceable P/Ns listed (6078T55P02 thru P10 inclusive, 6047T74P07, 6047T74P09, 6091T07P01) cannot claim relief under the AD.

Finally, because the AD references GE Alert Service Bulletins with specific dates and revisions, maintenance organisations performing compliance work must have access to those technical publications and ensure they follow the correct revision cited in the AD.

Duties

• Mandatory compliance. The AD imposes mandatory duties on operators to perform the specified actions. The preamble states the AD "requires that the action set out in the requirement section... be taken" in relation to affected aircraft or aeronautical products, "in the circumstances mentioned... in accordance with the instructions... and at the time mentioned in the compliance section." This historic wording places an affirmative obligation on operators to carry out the corrective work described.

• Component inspection and identification. Operators must inspect records and physical components to determine whether MFC P/Ns 6078T55P02 thru P10 are installed and whether the MFCs have Buna-N preformed packings P/Ns R1307P020 and R1307P141 (Requirement 1). This duty includes confirming engine and component serial numbers where the AD ties actions to specific SN ranges (Requirement 1 and 2).

• Perform one of alternative corrective actions. Where the triggering parts are present, operators must either replace the specified Buna-N O-rings with the specified Viton O-rings in accordance with the GE ASB instructions, or,for specified engine serial numbers,install an MFC with a flange vent groove conforming to the relevant ASBs (Requirement 1(a) and 1(b)).

• Install serviceable MFC with improved overspeed protection. For the listed engine models and installations, operators must install a serviceable MFC incorporating the improved overspeed protection or rework an existing MFC per GE ASBs. The AD prescribes the exact steps or ASB revisions for compliance for each engine/airframe combination (Requirement 3 and subsequent subparagraphs).

• Adhere to compliance timing. Operators must meet the timing requirements in the Compliance section: specific hard dates, "next time the engine is removed", "next time the MFC is removed", "next hot section inspection", or within stated months or hours in service after the effective date of the AD.

• Record-keeping and proof of compliance. Although the AD text does not set out a specific paperwork regime beyond its requirements, the preamble and normal Part 39 practice imply that operators must document completed work and maintain evidence that they complied with the AD within the mandated windows.

Rights and definitional protections

• Choice of compliance path. Where the AD provides alternate corrective actions (for example between O-ring replacement and installing an MFC with an improved flange vent groove), operators have the right to choose the path that better suits their operational or economic circumstances, provided they follow the relevant ASB instructions and meet any serial-number-based eligibility constraints.

• Termination of obligations by installing serviceable MFC. The AD explicitly states that "Replacing an MFC with a serviceable MFC, constitutes terminating action for the requirements of this AD." That gives operators a clear compliance pathway whose completion ends the AD obligations for that engine as defined in the AD.

• Technical acceptance tied to ASBs. The AD defers to manufacturer ASBs for the technical content of the modification or rework. Compliance with the Accomplishment Instructions of the cited ASBs is the prescribed method of meeting the AD; adherence to those instructions provides technical legitimacy to the work (Requirement references ASBs).

Constraints and exclusions

• Certain P/Ns do not qualify as serviceable. The AD defines serviceable MFCs functionally but lists P/Ns that are excluded from being serviceable and therefore cannot be used to terminate the AD: 6078T55P02 thru P10 inclusive, or 6047T74P07, 6047T74P09, or 6091T07P01.

• Timetable constraints. Some deadlines are expressed as fixed dates that, depending on when the AD became effective and the era of issuance, may have already passed for some operators. The Compliance section contains specific date triggers that operators must interpret in light of their maintenance history.

Delegation and enforcement context

• Issuance by CASA delegate under CAR 1998. The AD is issued under the authority of a CASA delegate pursuant to CAR 1998 subregulation 39.1(1), which supplies the legal authority to impose the duties set out. The AD is notified in the Commonwealth Gazette and bears the delegate’s signature and date.

In sum, the AD creates a regime where operators must inspect for defined part numbers and serial numbers and then either install replacement O-rings or modify/replace MFCs to the standards set in specified GE ASBs within prescribed maintenance events or calendar windows. Completion of the serviceable MFC installation terminates the AD obligations for that engine, provided the installed hardware is not one of the excluded P/Ns.

The AD itself is issued under the powers granted by the Civil Aviation Regulations 1998 (preamble referencing subregulation 39.1(1) of CAR 1998 and Part 39). The AD document does not set out a specific penalty schedule within its text. Instead, the regulatory framework for airworthiness directives implies that failure to comply with a CASA AD may render an aircraft not in compliance with applicable regulatory airworthiness requirements and subject the operator to enforcement action under the Civil Aviation regulatory system.

Enforcement mechanism and authority

• Issuing authority. The AD is promulgated by a CASA delegate and notified in the Commonwealth of Australia Gazette. The delegate’s signature (Eugene Paul Holzapfel) and the notification date are recorded in the AD document, establishing the administrative authority and effective dates for enforcement.

• Compliance as a regulatory requirement. The preamble states that the AD "requires" specified actions "in relation to the aircraft or aeronautical product mentioned in the applicability section." Under the CAR regime, compliance with ADs forms part of maintaining the aircraft in an airworthy condition. Non-compliance can therefore have regulatory consequences, including restrictions on operation, grounding of non-compliant aircraft, or enforcement proceedings for operating an unairworthy aircraft.

• Reliance on ASBs for methods. The AD prescribes compliance by reference to specific GE Alert Service Bulletins and their revisions. From an enforcement standpoint, performing the work in accordance with the cited ASB Accomplishment Instructions is the AD-prescribed method. Failure to follow the cited procedure could be used as the basis to find non-compliance, depending on the facts of a case.

Prescriptive vs. penal content

• No explicit fines or criminal penalties stated in the AD. This document does not itself list civil penalties, fines, or criminal sanctions for breach. These enforcement responses exist within the broader CAR enforcement framework but are not enumerated in the AD text. The AD’s role is to create a mandatory technical obligation; the consequences for breach are administered under broader aviation safety enforcement mechanisms.

• Terminating action reduces enforcement exposure. The AD states that installing a serviceable MFC constitutes terminating action for the requirements of this AD. Where operators have completed the terminating action and documented compliance per the AD and applicable maintenance regulation, the grounds for enforcement regarding this AD should be satisfied, subject to verification.

Practical enforcement implications

• On-site inspections and records review. Enforcement is typically effected through surveillance, audits and inspections. The AD’s P/N and SN specificity means enforcement officers or auditors can check maintenance records and inspect components to verify compliance. The AD references specific P/Ns and ASBs, which creates objective criteria for compliance assessment.

• Timing and retrospective scrutiny. Because the AD contains hard compliance dates and event-based triggers (e.g., "before 6 January 2000", "at the next hot section inspection", "within 4000 hours TIS or within 17 months after the effective date"), inspectors can assess whether operators met those deadlines. The AD’s statement that it supersedes a previous AD (AD/CF34/3) indicates a progression of obligations that enforcement authorities may examine over time.

• Interaction with foreign directives. The AD references corrections made in FAA AD 99-23-26R1 in its Background. In practice, CASA may coordinate enforcement or accept certain proofs of compliance consistent with related FAA AD actions, but the AD retains domestic authority and prescriptive content.

In summary, this AD establishes mandatory technical obligations enforceable under CAR 1998 Part 39. The AD text does not list specific monetary penalties, but by establishing technical requirements and compliance triggers and by stating that certain hardware constitutes terminating action, it creates objective criteria which CASA may use in regulatory enforcement and safety oversight, with standard aviation enforcement tools and consequences available under the broader regulatory statute.

This AD is issued under the Civil Aviation Regulations 1998 framework and interacts with other regulatory instruments and manufacturer directives as follows, based on the source text:

• CAR 1998 Part 39 authority. The AD is issued under subregulation 39.1(1) of the Civil Aviation Regulations 1998, Part 39. The preamble explicitly references the delegate’s authority under CAR 1998 Part 39, which is the statutory routing for airworthiness directives. That statutory basis supplies both the power to require corrective action and the linkage to the broader regulatory system that governs airworthiness and enforcement.

• Supersession of earlier AD. The AD explicitly states that it supersedes AD/CF34/3, which has been cancelled. It also notes that "Engines in compliance with AD/CF34/3 may be affected by the requirements of this AD" (Background). Thus, there is a temporal sequence: AD/CF34/3 was in force, then replaced by AD/CF34/4, and this Amendment 1 revises AD/CF34/4. The operator must therefore track the history of ADs relevant to these engines to ensure they are in compliance with the current AD rather than relying solely on compliance with a prior AD.

• Reference to FAA AD. The Background states "Note: FAA AD 99-23-26R1 refers" and that the Amendment "reflects corrections to the FAA AD as detailed in FAA AD 99-23-26R1." This establishes a cross-reference and harmonisation intent with a corresponding FAA AD. The AD thereby interacts with equivalent foreign regulatory materials; operators who have complied with the FAA AD may need to check whether their actions satisfy the CASA AD, using the specific ASBs and definitions stipulated here.

• Deference to manufacturer service bulletins. The AD mandates compliance "in accordance with the Accomplishment Instructions" of specified GE Alert Service Bulletins or Service Bulletins and their listed revisions. These ASBs are not law in themselves but become binding for operators under this AD. The AD therefore converts selected manufacturer-recommended procedures into regulatory requirements, establishing a legal overlay onto the manufacturer remediation steps.

• Compliance timing vis-à-vis effective dates. The AD contains dates and event-based compliance triggers, including a compliance requirement "before 6 January 2000" for Requirement 1, and states the amendment becomes effective on 13 July 2000. It also records that the original issue became effective on 22 December 1999 and that the AD was notified in the Gazette on 14 June 2000. The document therefore sits in a sequence of notices, and operators must interpret compliance obligations in the context of the AD’s issuance history and the effective dates of the earlier and current instruments.

• Interaction with aircraft operational and maintenance regulations. While the AD itself is a directive under Part 39, compliance actions implicate maintenance scheduling, release to service, and continuing airworthiness record-keeping obligations under other parts of the regulatory system. The AD does not recite those obligations but, by setting maintenance actions as mandatory, it interacts with the operator’s continuing airworthiness management duties under the CAR framework.

• Record and certification interplay. The AD’s requirements to perform modifications in accordance with specified ASBs imply that maintenance releases and logbook entries must reflect actions taken for airworthiness certification. These entries and any certificates issued when returning the aircraft to service must be consistent with other statutory obligations under CAR 1998.

In short, the AD is a Part 39 regulatory instrument that incorporates, by reference, specified manufacturer ASBs and aligns with related FAA directives. Its legal force is domestic, but it is part of a cross-jurisdictional patchwork of airworthiness directives and maintenance literature that together determine continuing airworthiness obligations for operators of the affected engine types.

The AD document itself records a concise amendment and issuance timeline which must be taken as authoritative for the purposes of the AD. The relevant chronology and amendment points in the source text are:

• AD/CF34/3. The Background states that AD/CF34/3 was cancelled and that the requirements of the current AD supersede AD/CF34/3. The AD also notes that engines previously in compliance with AD/CF34/3 might nevertheless be affected by the new requirements.

• Original AD/CF34/4 issuance. The AD text records "The original issue of this Airworthiness Directive became effective on 22 December 1999." That indicates the first iteration of AD/CF34/4 came into force on 22 December 1999.

• FAA corrections. The Background notes that this Amendment reflects corrections to the FAA AD as detailed in FAA AD 99-23-26R1. That indicates that changes made by the FAA AD, including any corrections or revisions, were taken into account in issuing this Amendment.

• AD/CF34/4 Amendment 1 issuance and effective dates. The top matter and the Compliance section provide dates for the Amendment. The AD states: "This Amendment becomes effective on 13 July 2000." The signature block shows the delegate signed on 31 May 2000, and the AD was notified in the Commonwealth of Australia Gazette on 14 June 2000. The document therefore records three dates relevant to the amendment: signature date 31 May 2000; Gazette notification 14 June 2000; effective date 13 July 2000.

• References to ASB revisions. The Requirement cites specific ASBs and their revisions, with dates spanning 1997 through 1999. For example, CF34 ASB No. A73-33 dated 21 November 1997, Revision 1 dated 29 May 1998, Revision 2 dated 9 March 1999; CF34BJ 73-A0033 Revision 3 dated 9 September 1999, Revision 4 dated 1 November 1999; and multiple ASBs dated 7 July 1999 and 12 August 1999, with some Rev 1 on 1 November 1999. These ASB revision references are part of the amendment’s technical history, showing which versions of manufacturer instructions the AD recognises for compliance.

• Cancellation notice. The preamble states the delegate "revokes Airworthiness Directive (AD) AD/CF34/4 and issues the following AD under subregulation 39.1 (1) of CAR 1998." That language indicates that Amendment 1 is presented as a revocation of a prior version followed by issuance of an amended instrument.

The AD therefore documents a short chain of succession: AD/CF34/3 was cancelled; AD/CF34/4 was originally issued and became effective 22 December 1999; this Amendment 1 was signed 31 May 2000, notified 14 June 2000, and made effective 13 July 2000, with the Amendment incorporating corrections aligned with FAA AD 99-23-26R1. Operators and maintainers must therefore pay attention to the particular ASB revisions and the dates stipulated in the AD’s text, and ensure that compliance is assessed against the most current AD text and the ASB revisions specified.

The AD document contains no references to litigation, judicial review, or case law. It records administrative steps: cancellation of an earlier AD, issuance of AD/CF34/4 and this Amendment 1, and cross-reference to FAA AD 99-23-26R1 for corrections. The source material does not mention any judicial proceedings, appeals, or enforcement actions taken in relation to this AD.

Implications of the absence of litigation references

• No recorded challenges in the AD text. The AD itself is silent on disputes or court cases. Where an AD contains no litigation history, the enforcement and compliance questions will typically be resolved administratively within CASA’s oversight and through established enforcement mechanisms under the Civil Aviation Regulations, rather than via litigation recorded in the AD text.

• Practical significance for operators. In the absence of recorded litigation outcomes or precedent, operators must rely on the AD text, the CAR regulatory framework, and CASA guidance for understanding legal obligations. Disputes over enforcement, compliance method, or timelines,if they arise,would be resolved using the standard administrative and legal routes available under the CAR regime and administrative law, but the AD itself provides no further detail on such avenues.

• Reliance on declared terminating action. The AD clarifies that replacing an MFC with a serviceable MFC "constitutes terminating action for the requirements of this AD." That explicit administrative statement reduces a common source of dispute,whether a particular modification ends AD obligations,because the AD declares the terminating condition. If a dispute arose over whether a particular installed unit met the AD’s definition of "serviceable", that would be a factual determination potentially subject to administrative or judicial review, but no such cases are recorded in the AD.

• Cross-jurisdictional harmonisation. The AD notes corrections in FAA AD 99-23-26R1. Where cross-border issues arise between CASA and FAA directives, operators sometimes face queries over equivalence and acceptance of compliance actions performed under a foreign AD. The AD references the FAA AD for corrections, indicating an attempt to align with FAA determinations, but the AD itself does not record any litigation or formal agreements addressing cross-jurisdictional disputes.

Because the source contains no litigation history, readers should not infer the absence of disputes in practice; they should understand only that this particular AD record does not include any litigation notes or adjudicative history. Any legal challenges or enforcement proceedings that may have occurred outside the scope of the AD text are not documented in the source provided.

The AD text contains several precise technical and temporal details that create potential traps for operators and maintenance providers. The following items are grounded in the AD text and merit careful attention.

Part numbers and serial numbers are the triggers

• Narrow P/N windows. The AD hinges on specific MFC part numbers 6078T55P02 thru P10 inclusive and specified O-ring P/Ns R1307P020 and R1307P141 (Requirement 1). Failure to correctly identify installed P/Ns can lead to a false understanding of whether the AD applies to a particular engine.

• Serial-number cutoffs. Certain compliance paths apply only to engines with serial numbers at or above specified thresholds (e.g., CF34-3A1 SNs 807001 and up; CF34-3B and -3B1 SNs 872001 and up; CF34-1A, -3A, -3A2 SNs 350003 thru 350525). Misreading serial ranges or applying them to incorrect variants could lead to non-compliance or unnecessary work.

Compliance timing complexities

• Multiple timing triggers. The AD uses several different timing triggers: fixed calendar dates ("before 6 January 2000"), event-based triggers ("at the next time the engine is removed" or "the next time the MFC is removed"), inspection-based triggers ("at the next hot section inspection" or "within 53 months after the effective date of this AD, whichever occurs first"), and flight-hours-based triggers ("within 4000 hours TIS after the effective date... or within 17 months... whichever occurs first"). Operators must map each requirement to their maintenance schedules to avoid missing a deadline.

• Apparent chronological overlap. The AD’s Compliance section includes a requirement to complete an action "before 6 January 2000" while the Amendment becomes effective on 13 July 2000 and the original AD was effective 22 December 1999. This sequencing means some compliance windows may predate the Amendment’s effective date. Operators must carefully reconcile prior AD versions, the original AD effective date, and this Amendment to determine whether an action was already required or remains outstanding.

Definition of "serviceable MFC" and excluded P/Ns

• Serviceable vs non-serviceable P/Ns. The AD defines "serviceable MFC" as one that incorporates improved overspeed protection or has been reworked per the applicable GE ASB; it then lists part numbers that are not serviceable and cannot be used as terminating action (6078T55P02 thru P10 inclusive, or 6047T74P07, 6047T74P09, or 6091T07P01). Replacing an MFC with another MFC that uses one of the excluded P/Ns does not terminate AD obligations. Operators must obtain documentary proof that a replacement MFC is serviceable as defined.

• Manufacturer ASB revision specificity. The AD ties compliance to specific ASB versions and revisions with dates, for example CF34 ASB No. A73-33 dated 21 November 1997, or Revision 1 dated 29 May 1998, or Revision 2 dated 9 March 1999, and CF34BJ 73-A0033 Revision 3 dated 9 September 1999, or Revision 4 dated 1 November 1999. Using an incorrect ASB revision or omitting required steps within an Accomplishment Instruction could undermine compliance.

Scope language: "installed on but not limited to"

• Broader applicability. The Applicability line states affected engines are "installed on but not limited to Bombardier, Inc. Canadair model CL-600-2A12, -2B16 and -2B19 aircraft." That phrasing means the listed airframes are examples and the AD could apply to those engines when installed on other aircraft models as well. Operators must check engines irrespective of airframe type.

Terminating action mechanics

• Replacing MFC constitutes terminating action, but only if serviceable. The AD clarifies that replacing an MFC with a serviceable MFC is terminating action. However, the unit must satisfy the AD’s serviceable definition and not be an excluded P/N. Replacements that are nominally "new" but match excluded P/Ns will not satisfy the terminating action condition.

Documentation and traceability requirements implied

• Evidence of compliance with ASBs. While the AD does not elaborate a specific record format, the ASBs’ Accomplishment Instructions typically require documentation. Operators should ensure that maintenance entries, parts tags and certificates unambiguously demonstrate that the ASB steps were followed and that the installed parts meet the AD’s P/N and modification criteria.

Cross-reference to FAA AD corrections

• Corrections adopted from FAA AD may change technical specifics. The Background states the Amendment reflects corrections to the FAA AD as detailed in FAA AD 99-23-26R1. Operators who relied entirely on a previous understanding of FAA AD content or of the earlier domestic AD should re-check the adopted corrections to ensure their maintenance actions align with the updated requirements.

In summary, the AD’s technical specificity, multiple timing triggers, dependency on ASB revision status, and narrow definitions of "serviceable" create several concrete points where misinterpretation or incomplete execution could produce non-compliance. Operators and maintainers should verify P/Ns and SNs carefully, use the exact ASB revisions cited, document actions and ensure that any replacement MFC actually meets the AD’s serviceable definition.

The AD ties compliance to specific, manufacturer-defined Accomplishment Instructions and sets precise timing triggers. The following is a practical, source-grounded compliance checklist derived from the AD’s text.

1. Identify affected engines and components

• Check engine models. Confirm whether installed engines are General Electric CF34-1A, -3A, -3A1, -3A2, -3B or -3B1 series engines. The AD applies to these engine series irrespective of aircraft type (Applicability).

• Check part numbers. Inspect MFC part numbers. The AD specifically targets MFC P/Ns 6078T55P02 thru P10 inclusive. Also inspect whether the MFC contains Buna-N preformed packings O-rings, P/Ns R1307P020 and R1307P141 (Requirement 1).

• Check engine serial numbers. For certain mandatory actions, confirm engine serial numbers match the ranges in the AD (for example CF34-3A1 engines SNs 807001 and up; CF34-3B and -3B1 engines SNs 872001 and up; CF34-1A, -3A and -3A2 engines SNs 350003 thru 350525) (Requirement 1 and 2).

2. Choose an appropriate corrective path where multiple options are provided

• Option A (O-ring replacement). If an affected MFC with Buna-N O-rings is installed, you may replace the Buna-N O-rings P/Ns R1307P020 and R1307P141 with Viton O-rings P/Ns M83485-1-020 (M83485/1-020) and 37B201714P130. Perform the replacement "in accordance with the Accomplishment Instructions, paragraph 3.A., of alert service bulletin (ASB) CF34AL 73-A0025, dated July 7, 1999 or ASB CF34BJ 73-A0040, dated July 7, 1999" (Requirement 1(a)).

• Option B (install MFC with flange vent groove). For engines meeting the serial-number thresholds in Requirement 1(b) or for engines in Requirement 2 where applicable, install an MFC with a flange vent groove conforming to the requirements of the specified GE ASBs: CF34 ASB CF34AL S/B 73-0026 dated 12 August 1999, or CF34BJ S/B 73-0041 dated 12 August 1999 or Revision 1 dated 1 November 1999 (Requirement 1(b) and 2).

3. Install improved overspeed protection (serviceable MFC)

• For CF34-1A, -3A and -3A2 series engines, install a serviceable MFC "in accordance with step 2A thru step 2G of the Accomplishment Instructions of CF34 ASB No. A73-33, dated November 21, 1997, or Revision 1 dated May 29, 1998 or Revision 2 dated March 9, 1999, or in accordance with step 3A(1) thru step 3A(7) of the Accomplishment Instructions of CF34 ASB No. CF34BJ 73-A0033, Revision 3 dated September 9, 1999, or Revision 4 dated November 1, 1999" (Requirement 3(a)).

• For CF34-3A1 and -3B series on Canadair CL 601 or CL 604, follow the same ASB pathways described in 3(a) (Requirement 3(b)).

• For CF34-3A1 and -3B1 series installed on CL 601RJ Regional Jet, follow the Accomplishment Instructions of CF34 ASB No. A73-19, Revision 1 dated 20 February 1998, or Revision 2 dated 9 March 1999, or steps 3A(1) thru 3A(7) of CF34 ASB CF34AL 73-A0019 Revision 3 dated 9 September 1999 (Requirement 3(c)).

4. Verify terminating action criteria if replacing MFC

• Determine whether an MFC replacement qualifies as terminating action. The AD states that "Replacing an MFC with a serviceable MFC, constitutes terminating action for the requirements of this AD."

• Confirm the replacement MFC meets the definition of "serviceable MFC" in the AD: it must incorporate improved overspeed protection modifications or have been reworked to provide those modifications as provided in the applicable GE ASB.

• Ensure the replacement MFC is not one of the P/Ns explicitly excluded from being serviceable: 6078T55P02 thru P10 inclusive, or 6047T74P07, 6047T74P09, or 6091T07P01 (Requirement, paragraph defining serviceable MFC).

5. Meet the compliance timelines

• Requirement 1: "Unless accomplished previously, before 6 January 2000." Confirm whether the affected work has already been performed. If not, investigate documentation and engage maintenance resources to reconcile any outstanding obligations in light of the dates recorded.

• Requirement 2: "Unless accomplished previously, at the next time the engine is removed or the next time the MFC is removed." Schedule this work to coincide with the next appropriate event.

• Requirement 3: For different engine/aircraft combinations, set schedules as per subparagraphs: next hot section inspection or within 53 months after the effective date of this AD (whichever occurs first) for some models; within 4000 hours TIS after the effective date or within 17 months after the effective date (whichever occurs first) for others. Map these to your maintenance planner.

6. Document completion and parts provenance

• Maintain maintenance records showing steps taken and the ASB revision used. Record MFC and O-ring P/Ns, serial numbers, and any work-order references to the specific GE ASB steps cited in the AD.

• Retain evidence that a replacement MFC satisfies the AD’s serviceable definition. Where a supplier provides MFCs claimed as serviceable, obtain signed certification or parts-tagging that indicates compliance with the specified ASB rework procedures.

7. Coordinate with parts suppliers and obtain required ASBs

• Obtain the specified Viton O-ring P/Ns (M83485-1-020 and 37B201714P130) if pursuing the O-ring replacement pathway.

• Source serviceable MFCs or arrange rework per the GE ASBs if using the replacing MFC terminating action. Ensure supplier documentation references compliance with the exact ASB steps and revision cited.

8. Consider interaction with prior ADs and FAA AD

• If work was performed under a prior AD (for example AD/CF34/3 or earlier versions of AD/CF34/4), verify whether that work satisfies the current AD requirements or whether additional action is required per the Amendment and its ASB cross-references.

• Note that the AD reflects corrections made in FAA AD 99-23-26R1. If compliance actions were performed under FAA direction, confirm that they align with the ASB revisions and the AD’s definitions.

9. Practical verification and audit readiness

• Prepare for possible CASA inspection by ensuring records clearly demonstrate the P/Ns and SNs examined, the ASB revision used, the work performed, the parts installed (including their P/Ns and serial numbers where available), and the date and signature of the certifying maintenance engineer.

• If claiming terminating action for an engine by installing a serviceable MFC, ensure the documentation explicitly states that the installed unit meets the AD’s serviceable criteria and is not an excluded P/N.

10. Keep track of AD and ASB revisions

• Because the AD lists specific ASB revisions and ASBs may have subsequent revisions, ensure that the version used for compliance is one of those cited in the AD. If a newer ASB revision is available, consult CASA guidance or the AD issuer for whether the newer revision is acceptable for compliance.

Following these steps, grounded in the AD’s text, will align maintenance practice with the AD’s prescriptive requirements and the AD’s declared terminating action. Operators should synchronise these steps with their continuing airworthiness management and maintenance planning to minimise downtime and ensure regulatory compliance.