AD/CESSNA 400/114 - Fuel Flow Transducer

The AD operates by identifying a single component type, a fuel flow transducer, by part numbers and serial-number range, then imposing identification and selective replacement obligations. Key concepts and mechanisms in the text are:

• Applicability by airframe model and airframe serial number. The AD applies only to explicitly listed Cessna Model 402C, 404, 414 and 421C aeroplanes with particular airframe serial numbers set out in the table. The AD’s applicability is therefore limited to a defined subset of the 400 series rather than being fleet-wide.

• Component-specific identification. The subject component is identified narrowly by Cessna P/N 9910395-9 and Aerosonics Corp P/N 33184-2. The AD instructs inspection of that specific P/N on each engine to determine the transducer serial number (Requirement 1). The AD therefore targets a single supplier/part configuration by part and manufacturer reference.

• Serial-number based defect criterion. The defect trigger is a discrete serial-number block: transducers with serial numbers in the block 2364 through 2930 are the items to be replaced (Requirement 2). The AD does not identify a failure mode in technical detail beyond the FAA background statement that the FAA AD was issued to detect and replace possibly defective transducers which may cause fuel leaks in the engine compartment.

• Two-step compliance sequence with timing differentiation. The AD separates inspection timing from replacement timing. CASA extended the inspection timing from the FAA’s ‘before further flight’ to ‘at the next scheduled maintenance but no later than 8 May 2009’ for Requirement 1. Requirement 2, by contrast, retains a before-further-flight constraint: if an inspected transducer falls within the serial-number block, replacement must be done before further flight after the inspection. Thus the instrument creates a staggered compliance rhythm: deferred identification, immediate grounding-for-replacement where defective items are found during that later inspection.

• Acceptance of prior State-of-design action. The AD expressly accepts that compliance with FAA AD 80-13-14 prior to arrival in Australia is probative and may be relied on for CASA compliance (Note 1). The instrument therefore creates an evidentiary pathway using maintenance records, linking local enforcement to prior State-of-design actions.

• Regulatory provenance and rationale. CASA’s Background statement explains the AD was published because an internal review showed Australia had not previously issued an AD corresponding to FAA AD 80-13-14 and CASA is required to publish State-of-design ADs which may affect Australian aircraft. CASA also records limited Australian exposure (two affected aeroplanes on the Australian register and no incidents reported) and uses that as the operational rationale for a relaxed inspection deadline relative to the FAA.

These concepts together establish a narrow, component-by-serial AD that relies on maintenance inspection, selective replacement, record evidence of prior FAA action, and a CASA-determined compliance timetable. The instrument creates a compliance-staging mechanism (deferred inspection, immediate replacement where necessary), ties conformity to maintenance records, and references the FAA AD as the originating corrective action.

The AD affects specific stakeholders by name and by implication. Directly affected parties are:

• Owners and operators of Cessna Model 402C, 404, 414 and 421C aeroplanes that are listed by airframe serial number in the AD table. The AD lists the precise serial numbers for each model; the operators of those aircraft are within the instrument’s applicability.

• Maintenance providers and certificated maintenance organisations who perform scheduled maintenance and recordkeeping for the affected aircraft. Requirement 1 directs inspection “on each engine” of the specified transducer P/N to determine serial numbers; executing that inspection is a maintenance task usually carried out by licensed maintenance personnel and their organisations. The AD notes that FAA AD 80-13-14 compliance recorded in maintenance records is acceptable evidence, which places recordkeeping obligations and evidentiary weight on maintenance documentation.

• CASA as regulator. The AD is issued by CASA and signed by its delegate, David Punshon. CASA’s Background statement explains that the AD was promulgated because an internal review indicated Australia had not issued a corresponding AD after the FAA action; CASA therefore exercised its role of publishing State-of-design ADs potentially affecting Australian-registered aircraft.

• Part suppliers and inventory managers. Requirement 2 mandates replacement of transducers with serial numbers in the block 2364 through 2930 by transducers whose serial numbers are not in that block. Suppliers and parts managers who manage inventories of P/N 9910395-9 (Aerosonics 33184-2) will therefore be implicated when replacement is required.

Indirectly affected parties include insurers and lessors, to the extent they have operational control or require evidence of compliance in their covenants, and flight operations managers, because the sequencing of inspection and replacement can affect aircraft availability. The AD acknowledges an Australian register footprint of only two affected aeroplanes and states that no similar incidents have been reported in Australia, facts that reduce the immediate pool of directly impacted Australian operators. However the AD’s applicability language is not geographically limited; it applies to those aircraft on the Australian register with the listed airframe serial numbers, and it accepts prior FAA compliance as proof of CASA compliance when documented.

Finally, because Requirement 2 imposes a “before further flight” replacement obligation where defective serial numbers are found, any operator who discovers an affected serial must ensure the aircraft is not flown until the replacement is carried out, directly affecting flight operations and scheduling for those aircraft.

The AD creates specific duties and establishes limited evidentiary rights. Key duties:

• Duty to inspect: Operators or maintenance organisations must inspect the fuel flow transducer identified as Cessna P/N 9910395-9 (Aerosonics P/N 33184-2) on each engine to determine the transducer serial number (Requirement 1). The AD does not specify the person or licence category required to carry out the inspection; it prescribes the action in terms of maintenance scheduling and timing.

• Duty to replace defective items: If the identified P/N 9910395-9 transducer has a serial number in the block 2364 through 2930, it must be replaced with a transducer whose serial number is not included in that block (Requirement 2). The AD does not prescribe specific replacement procedures beyond the serial-number exclusion criterion.

• Duty to meet CASA compliance timings: For Requirement 1 the inspection must be done at the next scheduled maintenance but no later than 8 May 2009. For Requirement 2 the replacement, where required, must be done before further flight after the Requirement 1 inspection. Therefore operators must schedule the inspection within the extended window and must ensure immediate replacement prior to any further flight if the serial is within the defective block.

Key rights and procedural recognition:

• Right to use prior FAA compliance as evidence: Note 1 gives operators a procedural right , maintenance records demonstrating compliance with FAA AD 80-13-14 are considered acceptable for compliance with this CASA AD. That provides an evidentiary route to show compliance without repeating work where the FAA action has already been carried out and documented.

• Right to select replacement transducers outside the specified serial block: The AD requires replacement with a transducer whose serial number is not included in the defective block, but does not mandate a particular supplier, manufacturer batch or serial-generation method beyond that exclusion. This grants flexibility to choose any P/N 9910395-9 transducer (or acceptable alternative) provided its serial number falls outside the listed defective range.

What the AD does not specify (and thus creates practical duties by omission):

• It does not set out who must carry out the inspection and replacement (for instance it does not state a licence level). The duty therefore falls into the practical sphere of accepted maintenance practice and regulatory expectations, but the AD text itself is silent on the required authorisation for the person performing the tasks.

• It does not specify documentation format for demonstrating compliance beyond the general statement that FAA AD compliance records are acceptable. Operators must therefore rely on standard maintenance records practices to evidence completion.

• It does not prescribe penalties, enforcement steps, or follow-up audit actions in the text of the AD. The AD sets the obligations and timing, but does not provide enforcement details in this document.

In sum, the core operative duties are inspection of the identified P/N and replacement where serials fall within the defined defective block, with CASA-imposed deadlines and acceptance of FAA-compliant maintenance records as proof. The practical burden of who performs the work and how it is recorded is allocated to operators and their maintenance providers through existing maintenance regimes rather than by detailed prescription in the AD.

The AD text supplied does not include express penalty clauses or a detailed enforcement regime. The document sets out the mandatory inspection and replacement requirements, the compliance deadlines and an effective date, but does not specify civil or criminal penalties, infringement notices, monetary fines, or administrative sanctioning procedures within the body of this AD.

What the AD does provide relevant to enforcement is:

• A clear effective date: “This Airworthiness Directive becomes effective on 8 May 2008.” That date anchors the compliance timetable and signals the point at which CASA’s regulatory requirement is in force.

• Compliance timeframes: The AD prescribes when Requirement 1 and Requirement 2 must be done: Requirement 1 at the next scheduled maintenance but no later than 8 May 2009; Requirement 2 before further flight after Requirement 1 inspection. These timing instructions are the primary compliance-control mechanism built into the AD.

• An evidentiary pathway: Note 1 states that compliance with FAA AD 80-13-14 prior to the aircraft’s arrival in Australia and maintenance records evidencing that compliance “is considered acceptable for compliance with this Directive.” This provides operators a documented basis for demonstrating compliance rather than technical substitution or rework.

What is not in the AD text that a reader must notice:

• There are no specified penalties or enforcement steps, no administrative process for CASA to record compliance within the AD itself, no reference to contravention provisions, and no sanctions framework stated within this document. The AD therefore sets the substantive obligations and timing but leaves enforcement mechanisms implicit or to be applied under CASA’s general regulatory powers and enforcement practices rather than by provisions in the AD text.

• Because the AD does not specify the authorised person to perform the inspection or replacement, the AD does not itself prescribe the certification mechanics for compliance entries in maintenance records.

Practical implications of this design:

• The AD’s compliance deadlines and the “before further flight” replacement rule create operational leverage , an aircraft with a transducer found to have a serial in the defective block cannot lawfully be flown before replacement according to the AD. That operational prohibition functions as an enforcement lever even though the AD text does not specify sanctions.

• Operators seeking to rely on prior FAA AD compliance must ensure maintenance records are accessible and demonstrative; the AD’s Note 1 indicates CASA will accept such records as satisfying the AD.

• Enforcement or penalty activity for failure to comply will depend on CASA’s general enforcement authorities, oversight processes and existing aviation safety enforcement frameworks outside this AD document; those frameworks are not included in the AD text and are not described here.

Therefore, the AD sets mandatory obligations and deadlines but leaves the formal sanctions and compliance-administration mechanisms outside the AD’s text. Parties should therefore treat the AD as creating enforceable safety duties while recognising that specifics of enforcement action and penalties are not articulated in this instrument.

The AD expressly interacts with other regulatory action, and by omission it interfaces with established maintenance and safety record regimes. Direct interactions recorded in the AD text are:

• FAA AD 80-13-14: The AD explicitly references FAA AD 80-13-14. Note 2 states “FAA AD 80-13-14 Amdt 39-3844 refers,” and Note 1 recognises that the requirements of this Directive were likely accomplished prior to arrival in Australia and that maintenance records indicating compliance with FAA AD 80-13-14 “is considered acceptable for compliance with this Directive.” That creates a direct evidential and substantive interaction: CASA’s AD imports the FAA corrective action as relevant State-of-design action and allows prior FAA compliance to discharge the CASA requirement.

• State-of-design AD duty: CASA’s Background statement says that CASA is required to publish State-of-design ADs which may affect Australian aircraft. The AD therefore sits as a domestic manifestation of a State-of-design duty to consider and publish corrective airworthiness action that relates to foreign-origin aircraft systems. The AD is framed as CASA acting on such an obligation after an internal review showed Australia had not issued an AD corresponding to FAA AD 80-13-14.

Interactions implied but not spelled out in the AD text:

• Maintenance record regimes: The AD’s acceptance of FAA maintenance records as satisfying the AD implies interaction with the civilian maintenance recordkeeping system applicable to Australian-registered aircraft. Operators who rely on prior FAA compliance must ensure that the relevant maintenance records are retained and presented in a form acceptable to CASA.

• Operational law: The “before further flight” requirement for replacement where defective serial numbers are found is an operational restriction imposing a pre-flight safety condition. Although the AD does not cite a specific Act or regulation that criminalises or sanctions flight with unresolved AD non-compliance, in practice flight operations are governed by aviation safety law and regulations that require compliance with airworthiness directives. The AD therefore interacts operationally with flight release and continuing airworthiness obligations under the general regulatory framework, even though those instruments are not quoted in the AD.

• International regulatory co-ordination: By referencing FAA action and by stating CASA’s duty to publish State-of-design ADs, the AD demonstrates the mechanism by which foreign-state airworthiness findings are translated into domestic regulatory obligations. The AD creates a cross-reference network where State-of-design corrective action is recognised and incorporated into domestic obligations through an explicit note.

No other statutory or regulatory cross-references, exemptions or suspension mechanisms are included in the AD text. There is no textual mention of modification to other Acts, taxation, import controls for replacement parts, or contractual consequences with lessors or insurers. The AD therefore interacts positively and specifically with FAA AD 80-13-14 and more generally with maintenance recordkeeping and flight operations regimes, but details about administrative or enforcement cross-links lie outside the text of this Directive.

The AD text supplied contains a single issuance record and does not record any formal amendments to the AD itself within the document. Relevant chronology and amendment-related items in the AD include:

• Issue date and signature: The AD is signed and dated in the body of the document by David Punshon, Delegate of the Civil Aviation Safety Authority, on 6 March 2008. That identifies the issuing authority and the date of signature.

• Effective date: The AD states “This Airworthiness Directive becomes effective on 8 May 2008.” That furnishes a temporal anchor for compliance and indicates the required action is in force from that date.

• Compliance timeline modification relative to FAA: The AD explicitly alters the timing of compliance relative to the FAA AD. The Background explains CASA extended the inspection compliance from “Before further flight” under the FAA AD to “At the next scheduled maintenance but no later than 8 May 2009” for Requirement 1. For Requirement 2 the AD retains the FAA-like constraint that replacement must be done “Before further flight after the Requirement 1 inspection.” This is a substantive timing adjustment when compared to the FAA standard; it is recorded as CASA’s chosen compliance window rather than as an amendment after issue.

• No subsequent amendments recorded: The supplied text does not indicate any later amendments, revocations, supersessions, or corrigenda to AD/CESSNA 400/114. The AD itself makes no reference to later AD numbers, updates, or revision history. It does, however, refer to the FAA AD amendment designation Amdt 39-3844 in Note 2, but that is a reference to the FAA instrument rather than an amendment to the CASA AD.

• No legislative amendment trace: The document does not show or reference amendments to underlying legislation or to CASA’s rulemaking powers. It contains no amendment history table or footnote logging changes to the AD text.

Accordingly, based solely on the instrument text provided, the AD comprises a single issuance with signature dated 6 March 2008, effective 8 May 2008, with a CASA-determined extension of the inspection period to 8 May 2009 for Requirement 1. There is no appended or embedded record of later amendments in the supplied text.

The supplied AD text contains no information about litigation, appeals, judicial review, prosecutions, or administrative disputes arising from AD/CESSNA 400/114. The document does not reference any cases, court decisions, tribunal outcomes, or enforcement proceedings. The Background statement notes that “no incidents of a similar nature [have] been reported in Australia” and that only two affected aeroplanes were on the Australian register at the time; those factual statements reduce, within the text, the immediate factual seeds for litigation stemming from incidents in Australia.

Because the AD does not include any enforcement or penalty provisions within its text, and because no litigation history is stated, there is no litigation record for this AD in the supplied instrument. If stakeholders require information about subsequent legal disputes, enforcement action or administrative outcomes arising from this AD, that material would need to be obtained from CASA case records, administrative enforcement reports, or court databases; those sources are not included in the AD text and are outside the scope of the supplied document.

In short, the instrument as provided contains no litigation history or references to judicial or administrative proceedings related to AD/CESSNA 400/114.

The AD contains several practical and interpretative points where operators and maintenance providers must take care; each is grounded in the AD text.

• Narrow applicability but precise serial lists. The AD applies only to particular Cessna 400-series models and to specific airframe serial numbers listed in the AD table. Operators of other 400-series airframes must not assume applicability; conversely, operators of aircraft with the listed serial numbers must not assume exemption. Misreading the table or using an incorrect serial number could lead to non-compliance. The AD lists serial numbers for Models 402C, 404, 414 and 421C; verification against the aircraft’s logbooks and plate data is therefore necessary.

• Component identification must match both P/Ns. The AD requires inspection of Cessna P/N 9910395-9, which the AD equates to Aerosonics Corp P/N 33184-2. Failure to inspect the correctly identified P/N could result in either false negatives (missing a defective transducer) or unnecessary replacement. Maintenance personnel should confirm both the P/N and the serial number on the installed transducer.

• Serial-number block interpretation. The AD requires replacement where the transducer’s serial number is “included in the block 2364 through 2930.” Operators must interpret this as inclusive of both end points unless their maintenance authority instructs otherwise. The AD does not provide a serial-number formatting instruction; therefore maintainers should match serials precisely as recorded on the component.

• Timing trade-off and operational impact. CASA extended the inspection deadline for Requirement 1 to “at the next scheduled maintenance but no later than 8 May 2009,” relaxing FAA timing. However Requirement 2 mandates replacement “before further flight after the Requirement 1 inspection” if the transducer is in the defective serial block. Practically, that means an aircraft that is inspected at its next scheduled maintenance and found to have an affected transducer cannot fly until it is replaced. Operators who take advantage of the relaxed inspection timing must nevertheless plan for possible immediate grounding if a defective serial is found, and they should have a parts and labour plan to avoid extended downtime.

• Prior FAA compliance evidence. Note 1 states compliance with FAA AD 80-13-14, performed prior to arrival in Australia and evidenced in maintenance records, “is considered acceptable” for compliance with the CASA AD. That creates a recordkeeping demand: operators must retain and present clear maintenance documentation if relying on previous FAA action. The AD does not specify the form or content of acceptable records beyond this statement.

• Replacement requirement is by exclusion, not positive specification. Requirement 2 specifies replacement “with a transducer whose serial number is not included in that block.” The AD does not state that the replacement must be newly manufactured, have a warranty, or be sourced from a particular supplier. Operators must confirm the replacement part’s serial number prior to installation. The AD also does not state whether multiple transducers of the same P/N but with acceptable serial numbers require any additional inspection post-installation.

• Small Australian population but unqualified requirement. The Background acknowledges only two affected aeroplanes on the Australian register and no reported incidents in Australia. Those facts may reduce immediate operational exposure, but the AD imposes the same obligations on affected aircraft regardless of population. Operators should not assume CASA will relax requirements further for small fleet counts absent a formal amendment.

• No stated enforcement detail in the AD text. The AD sets obligations and timing but does not specify how CASA will enforce compliance or what penalties might follow non-compliance. The operational consequence of the “before further flight” replacement requirement is clear, but the AD itself leaves enforcement mechanics to CASA’s general powers, which are not set out here.

• Reference to FAA AD amendment identifier. Note 2 contains the reference “FAA AD 80-13-14 Amdt 39-3844 refers.” Operators relying on cross-references should ensure they consult the FAA AD text and any FAA amendment information as part of interpreting the defect and prior-compliance evidence.

These are concrete points of interpretative and operational risk which the AD text itself raises. Operators should plan inspections, parts sourcing, record review and contingency scheduling around these practical edge cases to avoid procedural non-compliance or unexpected grounding.

The AD sets out discrete, documentable steps. The procedure below translates the AD’s Requirements and Notes into an ordered compliance workflow, strictly grounded on the AD text.

1. Confirm applicability. Verify aircraft model and airframe serial number against the AD table. The AD applies only to the specifically listed serial numbers for Models 402C, 404, 414 and 421C. Do not proceed if the aircraft is not listed; if in doubt, check the aircraft’s builder plates and logbook entries to confirm exact model and serial number.

2. Plan the inspection. For aircraft on the Australian register with the listed serial numbers, schedule inspection of the fuel flow transducer P/N 9910395-9 (Aerosonics P/N 33184-2) “on each engine” at the next scheduled maintenance but no later than 8 May 2009, per the AD’s compliance instruction for Requirement 1. Document the scheduled maintenance date in the aircraft maintenance plan.

3. Conduct the inspection. At maintenance, inspect the fuel flow transducer on each engine and record the transducer part number and the transducer serial number. The AD requires inspection specifically of P/N 9910395-9; ensure the physical part marking corresponds to either Cessna P/N 9910395-9 or Aerosonics Corp P/N 33184-2 as indicated in the AD.

4. Determine replacement need. For each installed P/N 9910395-9 transducer, check whether its serial number is within the block 2364 through 2930. Where the serial number falls within that inclusive block, the AD requires replacement with a transducer whose serial number is not included in that block.

5. Execute replacement where required. If a transducer is within the defective serial block, replace it with a transducer whose serial number falls outside the 2364-2930 block. The AD requires that replacement must be performed “before further flight after the Requirement 1 inspection.” Ensure installation work is signed off and documented according to standard maintenance recordkeeping practice.

6. Use prior FAA compliance where available. If the transducer inspection and/or replacement was already accomplished prior to the aircraft’s arrival in Australia under FAA AD 80-13-14, record evidence of that FAA compliance in the maintenance records. Note 1 states such records are considered acceptable for compliance with this CASA AD. Ensure maintenance records explicitly reference FAA AD 80-13-14 actions taken, dates, and part serial numbers to facilitate acceptance.

7. Document completion. Record in the aircraft maintenance records the inspection date, the transducer part numbers and serial numbers inspected, the replacement part numbers and serial numbers installed (if any), and the signature and licence or organisational acceptance of the person who performed or certified the work. Although the AD does not prescribe a particular signatory, maintenance records are the AD’s evidentiary mechanism and should comply with standard civil aviation maintenance record requirements.

8. Plan for contingencies. Because replacement where required must be completed before further flight, operators scheduling the extended inspection window must nonetheless ensure they have access to acceptable replacement transducers or an approved supply pathway to avoid extended aircraft grounding if a defective serial is found. The AD does not mandate a particular source for replacement transducers; confirm serial numbers prior to installation.

9. Retain records for CASA verification. Keep maintenance records showing inspection and any necessary replacement, or evidence of FAA AD compliance if relying on prior action. The AD’s Note 1 makes FAA AD compliance records acceptable evidence, so authorities should be able to verify the work from standard maintenance logs.

10. Monitor for further CASA instructions. The AD text does not record later amendments or follow-up instructions. Operators should maintain regular contact with CASA and consult the CASA AD database or notices to ensure no subsequent amendments, superseding ADs, or additional guidance have been issued after the effective date stated in the AD.

By following these steps , verify applicability, inspect P/N 9910395-9 on each engine, replace any transducer with a serial in 2364-2930 before further flight, and document maintenance or prior FAA AD compliance , operators will effect the obligations set out in AD/CESSNA 400/114 as recorded in the supplied instrument.