AD/CESSNA 400/117 - Powerplant Electrical Wiring

Applicability: The Directive applies only to Cessna Model 441 aeroplanes with serial numbers in the range 441-0001 through 441-0109 (Applicability). That is the complete scope as stated; aircraft outside that serial number block are not listed as affected by this instrument.

Two-stage compliance approach: The AD separates the obligation into an initial records inspection and a contingent physical corrective action. Requirement 1 mandates checking the aircraft records to determine whether Cessna Propjet Service Information Letter PJ79-27 dated 30 July 1979 or Revision 1 dated 13 September 1979 has been complied with. If the records do not show compliance, Requirement 2 mandates rewiring of the engine control wiring in accordance with SIL PJ79-27 Revision 1 (Requirement). Note 1 explicitly states that compliance with FAA AD 79-19-12 Amdt 39-3574 is considered acceptable evidence of compliance with this Directive (Requirement, Note 1).

Temporal staging and effective date: The Directive sets separate timing rules for the two requirements. Requirement 1 must be completed at the next scheduled maintenance but in any event no later than 25 September 2009. Requirement 2, where applicable, must be completed before further flight after the Requirement 1 inspection (Compliance). The AD’s stated effective date is 25 September 2008 (Compliance).

Reference to external documents and cross-jurisdictional acceptance: The Directive refers to the Cessna Propjet SILs and the FAA AD 79-19-12 Amdt 39-3574. It accepts prior accomplishment of the FAA AD (or appropriate SIL compliance) as meeting the Directive’s requirement (Requirement, Note 1). It also observes that the FAA AD was originally issued to preclude an unplanned engine stoppage (Background).

Regulatory provenance and rationale: The Background records that the AD follows an internal CASA review which found that an Australian AD had not previously been issued in response to the FAA AD. CASA notes there have been no reported incidents of a similar nature in Australia and that 14 affected aeroplanes are on the Australian register; despite that, CASA states it is required to publish State of design ADs which may affect Australian aircraft and therefore issued this Directive (Background). CASA also extended the FAA’s original compliance timing (which required action prior to the next flight) to a later deadline tied to scheduled maintenance, explaining the extension by reference to the passage of time since the FAA AD and the limited number of affected aircraft in Australia (Background).

Practical focus: The Directive targets engine control wiring within the powerplant electrical wiring area (title and Requirement). It prescribes the method of compliance by reference to the manufacturer’s Service Information Letter and cross-references the FAA AD for background and acceptability of prior compliance (Requirement, Note 2). The AD’s operative obligations are therefore interoperable with existing maintenance records and prior US-regulatory compliance if evidenced in the aircraft’s records.

Registered owners and operators of Cessna Model 441 aeroplanes, serial numbers 441-0001 through 441-0109, are the parties directly affected, because the AD’s applicability is explicitly limited to that model and serial-number block (Applicability). The AD’s instructions create immediate responsibilities for those owners/operators to inspect maintenance records and possibly undertake rewiring work on the engine control wiring. The AD also implicitly affects aircraft maintenance organisations and maintenance personnel authorised to carry out inspections and rewiring work in accordance with the prescribed Service Information Letter (Requirement).

Aircraft on the Australian register are specifically mentioned in the Background: CASA records show 14 of the affected aeroplanes are currently on the Australian register (Background). Those registered in Australia will therefore face the AD’s compliance timeline and must either document prior compliance or implement the rewiring instructions to meet the Directive’s requirements.

Maintenance record-holders and certifying engineers: The Requirement 1 action is a records check. This places the immediate procedural burden on whoever maintains the aircraft’s technical log and records: the operator, maintenance organisation, or maintenance release holder must confirm whether SIL PJ79-27 (original or Revision 1) has been complied with. If the records show compliance via the SIL or the FAA AD (Note 1), no further physical work is required under this Directive; if not, an authorised maintenance organisation must perform the rewiring in accordance with SIL PJ79-27 Revision 1 (Requirement).

Regulators and delegates: The Directive is issued by the Civil Aviation Safety Authority (CASA), signed by a CASA delegate (Charles Lenarcic) on 15 August 2008, with an effective date stated as 25 September 2008 (Background; signature block). CASA’s internal processes and obligations are implicated: the Background explains the Directive followed an internal review and asserts CASA’s obligation to publish State of design ADs which may affect Australian aircraft.

Third-party suppliers and parts providers: Because the AD may require rewiring work in accordance with a specific Service Information Letter, suppliers of approved wiring components, harnesses, and relevant parts may see demand from affected owners/operators. The AD itself does not specify replacement parts or suppliers, only the required method of compliance by reference to the manufacturer’s SIL (Requirement).

Who does not bear a direct obligation: Owners of Cessna Model 441 aircraft outside the serial-number range 441-0001 to 441-0109 are not listed as affected by this AD and therefore are not subject to the stated requirements under this instrument (Applicability). The Background notes no incidents in Australia and that only 14 aircraft within the affected serial range are on the Australian register, indicating a small domestic cohort subject to the AD (Background).

Key duties

• Records inspection duty: Owners/operators must check aircraft records to determine whether compliance with Cessna Propjet SIL PJ79-27 (30 July 1979) or Revision 1 (13 September 1979) has been accomplished (Requirement 1). The AD specifies that the check is to occur at the next scheduled maintenance but no later than 25 September 2009 (Compliance).

• Rewiring duty if records do not evidence compliance: If Requirement 1 does not indicate compliance with the relevant SIL or Revision 1, the operator must rewire the engine control wiring in accordance with the instructions provided by SIL PJ79-27 Revision 1 (Requirement 2). The AD requires this rework to be completed before further flight after the Requirement 1 inspection (Compliance).

• Temporal compliance obligations: The AD sets discrete timing obligations. Requirement 1 is bounded by scheduled maintenance or the specified deadline, and Requirement 2 must be done before further flight (Compliance). The Directive becomes effective on 25 September 2008, which frames the start of the compliance period (Compliance).

• Record-evidence duty regarding FAA AD compliance: Where maintenance records indicate compliance with FAA AD 79-19-12 Amdt 39-3574, that evidence is considered acceptable for this Directive (Requirement, Note 1). That imposes a duty to identify and preserve any FAA AD compliance documentation in the aircraft records, since it discharges the need for rewiring under this AD.

Rights and procedural expectations

• Right to rely on prior compliance evidence: The AD explicitly allows reliance on past compliance with FAA AD 79-19-12 Amdt 39-3574 as satisfying Requirement 1. This creates a right for the operator to avoid further action if the records demonstrably show that earlier work was completed in accordance with the FAA AD (Requirement, Note 1).

• Right to perform work in line with SIL Revision 1: Where rewiring is required, the AD specifies the required method , SIL PJ79-27 Revision 1. The operator has the right to have the corrective work performed in accordance with that documented method; the AD does not prescribe alternative methods (Requirement).

• Expectation of maintenance-based scheduling: The AD delays the initial records check to a maintenance context (next scheduled maintenance), giving operators a scheduling window that is larger than the FAA AD’s original ‘prior to next flight’ requirement; CASA’s Background provides the explicit rationale for this timing change (Background).

Delegation and certification: The AD implies that authorised maintenance organisations and certifying engineers must execute the inspection and rework tasks and sign off compliance, because the actions require records inspection and technical rewiring. The AD does not explicitly set certification formats, but the Requirement prescribes the method of compliance via the SIL, implying approved maintenance procedures and sign-off are expected.

No express penalty or enforcement subsection: The text does not set out penalties, sanctions, or enforcement mechanisms in the body of the Directive itself (the Directive contains no penalty clause). The Directive does, however, set mandatory requirements and dates; compliance is framed as necessary by the instrument (Requirement; Compliance). Any enforcement consequences beyond the Directive’s requirements are not specified in this text.

Presumptions against additional discretionary deviations: The Directive references a specific service instruction (SIL PJ79-27 Revision 1) as the compliance method. It does not provide for alternative methods, waivers, or deviations in the text; operators must follow the SIL if rewiring is required (Requirement). The acceptance of FAA AD compliance as satisfying this AD suggests limited discretion to accept prior equivalent work, but that discretion is expressed only in terms of documented FAA AD compliance (Requirement, Note 1).

The AD text that has been provided does not set out specific statutory penalties, fines, or enforcement mechanisms within the body of the Directive itself. The Directive establishes mandatory obligations by describing required actions and deadlines: an initial records check (Requirement 1), possible rewiring per SIL PJ79-27 Revision 1 (Requirement 2), and firm timing (Compliance). The effective date is stated as 25 September 2008 (Compliance). The instrument is issued and signed by a CASA delegate (Charles Lenarcic, 15 August 2008), which identifies CASA as the issuing authority (Background; signature).

Because the supplied text contains no express penalty clause or enforcement procedure, the Directive should be read as setting technical and operational obligations that owners/operators must meet; enforcement details and sanctions for non-compliance, if any, are not contained in the document excerpt. The Directive’s language is prescriptive and sets compliance dates and conditions. In practice, airworthiness directives of this form are regulatory instruments that typically carry obligatory effect, thereby creating obligations for certificate holders and operators; however, any consequences for failing to comply, and the mechanisms by which CASA or other authorities would enforce the Directive, are not recorded in the text provided.

The Directive does, in its Background, state an administrative rationale for the timing of the requirements: CASA extended the FAA AD’s compliance interval from ‘Prior to the next flight’ to ‘At the next scheduled maintenance but no later than 25 September 2009’ (Background). That extension is a notation of enforcement discretion about timing rather than a statement of enforcement mechanics. The document does not describe inspection regimes, audit frequency, reporting obligations for compliance, or follow-up actions that CASA will take to confirm compliance for the 14 affected aeroplanes on the Australian register (Background).

Where the Directive accepts evidence of prior compliance (for example via FAA AD 79-19-12 Amdt 39-3574), that acceptance operates as a compliance verification mechanism for this AD (Requirement, Note 1). In other words, documented evidence in maintenance records that the FAA AD work has been done discharges the operator from further action under this Directive, per the AD text.

To summarise what is in the text: the AD imposes mandatory technical requirements and dates, identifies the authority issuing the Directive, accepts certain prior compliance evidence as meeting its requirements, and sets an effective date. It does not enumerate specific penalties or describe the practical enforcement process in the excerpt provided.

Reference to FAA AD and manufacturer SILs: The Directive explicitly cross-references the United States FAA AD 79-19-12 Amdt 39-3574 and Cessna Propjet Service Information Letter PJ79-27 (original and Revision 1). Note 1 states that compliance with FAA AD 79-19-12 Amdt 39-3574 is considered acceptable for compliance with this Directive, and Note 2 simply notes the FAA AD refers (Requirement, Notes). That creates an avenue for prior US-regulatory compliance to discharge the Australian AD’s obligations, provided the work is documented in the aircraft records.

State-of-design obligations and domestic implementation: The Background states CASA is required to publish State of design ADs which may affect Australian aircraft, and that this Directive follows an internal CASA review which found an Australian AD had not been issued in response to the FAA AD (Background). That situates this AD as CASA’s implementation of a State-of-design (US-design) safety requirement into Australian regulatory practice. The Directive thereby interacts with the international norm that national aviation authorities adopt or reference airworthiness directives issued by the State of design or the FAA.

Interaction with maintenance regulation and scheduling: The Directive ties the record inspection to the next scheduled maintenance but allows a deadline up to 25 September 2009 (Compliance). That places the AD in direct operational interaction with maintenance scheduling frameworks for aircraft on the Australian register. The AD’s timing choice effectively defers initial compliance actions into routine maintenance cycles, which may interact with operators’ maintenance programmes, maintenance schedules required by the Civil Aviation Safety Regulations or operator-approved maintenance control manuals, although those specific regulations are not quoted in the AD text.

Records and evidence regimes: The AD recognises maintenance records as the primary evidence for prior compliance (Requirement). This interacts with existing obligations on operators to maintain and retain maintenance records; the AD itself does not set the record-keeping rules but relies on them. Where FAA AD compliance is recorded, that documentation is accepted as satisfying the Directive (Requirement, Note 1).

No conflict clauses or variance provisions in the text: The AD does not contain express conflict resolution clauses or provisions for alternative methods of compliance, nor does it provide a waiver process in the text provided. It is silent on how to resolve potential conflicts between this AD and other regulatory instruments. The only explicit interaction is the acceptance of prior FAA AD compliance as adequate evidence, which is a form of cross-recognition (Requirement, Note 1).

International operator and registry effects: For aircraft that have complied with the FAA AD prior to operating in Australia, the Directive’s acceptance of FAA AD compliance removes the need for duplicated work, as evidenced in the aircraft records (Requirement, Note 1). Conversely, for aircraft on the Australian register that have not evidence of FAA or SIL compliance, CASA requires rewiring per the SIL (Requirement 2), thereby imposing domestic regulatory effect where international compliance is not documented.

No stated amendment to other laws: The Directive does not purport to amend or override existing statutes; it operates as a prescriptive airworthiness directive aimed at ensuring a particular safety standard regarding engine control wiring is met for the listed aircraft. The AD itself does not reference or modify the Civil Aviation Safety Regulations or other instruments in the text provided.

The AD text supplied includes references to historical documents but does not include a multi-entry amendment log for the AD itself. The document identifies the following key dated items that constitute the Directive’s provenance and the technical sources it relies on:

• Cessna Propjet Service Information Letter (SIL) PJ79-27, dated 30 July 1979, and SIL PJ79-27 Revision 1, dated 13 September 1979. The AD requires inspection for compliance with either the original SIL or Revision 1, and prescribes rewiring in accordance with SIL PJ79-27 Revision 1 where required (Requirement).

• FAA AD 79-19-12 Amdt 39-3574. The AD refers to the FAA AD and states that compliance with that FAA AD is considered acceptable for compliance with this Australian Directive (Requirement, Note 1; Note 2).

• The AD itself is dated in the header as 10/2008 and is signed by CASA’s delegate on 15 August 2008, with an effective date stated as 25 September 2008 (Background; signature). The Compliance statement also specifies the date 25 September 2009 as the latest permissible date for completing Requirement 1 (Compliance).

There is no record within the supplied text of prior iterations of AD/CESSNA 400/117 or subsequent amendments to the AD. The AD references an earlier FAA action from 1979 and accepts that prior work done under that FAA AD satisfies the Australian requirement, but it does not document any prior Australian AD version for this serial-number block. The Background states the AD follows an internal CASA review which indicated an Australian AD was not previously issued in response to FAA AD 79-19-12, implying this AD is the first Australian AD on the matter (Background).

The Directive does not include an “Amendments” table or list of versions within the text provided. It does not state that it supersedes any earlier Australian ADs, nor does it record later amendments, revocations, or corrections. The only historical items explicitly referenced are the two dated versions of the manufacturer’s SIL and the FAA AD.

Where the AD adopts or recognises earlier work, it does so by referencing the dates and identifiers of those instruments (SIL dates and FAA AD identifier), and by expressly stating that such prior compliance is acceptable (Requirement, Note 1). The AD’s effective date and the compliance deadlines are clearly stated; however, there is no further internal update history in the supplied text.

The supplied text contains no references to litigation, disputes, court decisions, or legal challenges related to AD/CESSNA 400/117, the referenced SILs, or FAA AD 79-19-12 Amdt 39-3574. The Background notes administrative facts and regulatory obligations (for example that CASA is required to publish State of design ADs and that there have been no incidents of a similar nature reported in Australia), but it does not reference any judicial proceedings or contested enforcement actions (Background).

Because the document excerpt does not include any lawsuits, appeals, enforcement proceedings, or case citations, there is no litigation history to report based on the provided text. If users require a record of legal challenges, judicial review applications, or enforcement actions relating to this Directive, those items are not present in this instrument and would need to be sourced from external records, court databases, or CASA enforcement logs, none of which are included in the supplied material.

In short, within the boundaries of the text provided, the Directive has no litigation history recorded.

Narrow applicability , serial numbers only: The AD applies strictly to Model 441 aeroplanes with serial numbers 441-0001 through 441-0109 (Applicability). Owners/operators must not assume a broader model-class or type coverage; an aircraft outside that serial-number range is not listed as affected by this Directive. If a registrant misreads applicability and treats the AD as covering other 400-series variants or different serial-number ranges, they may perform unnecessary work or, conversely, fail to apply required actions to an affected aircraft.

Records-based compliance can conceal non-compliance: Requirement 1 relies on the operator’s maintenance records to show whether SIL PJ79-27 or its Revision 1 has been complied with (Requirement 1). If records are incomplete, ambiguous, or lack explicit reference to the requisite SIL or FAA AD, the operator must treat that as non-compliance and proceed to Requirement 2. The AD does not authorise reliance on informal notations; the text requires a check of the aircraft records for evidence of compliance.

Acceptance of FAA AD compliance is conditional on documentation: Note 1 states FAA AD compliance is considered acceptable for this Directive (Requirement, Note 1). That acceptance is predicated on the existence of demonstrable record evidence; absence, loss, or unclear documentation of FAA AD compliance will not satisfy the AD and will trigger the rewiring requirement (Requirement).

Timing difference from FAA AD: CASA extended the timing for the initial action relative to the FAA AD. The FAA AD originally required action ‘Prior to the next flight’ whereas CASA’s Directive permits Requirement 1 to be completed at the next scheduled maintenance but no later than 25 September 2009 (Background; Compliance). Operators who are used to the FAA’s more immediate timing must note the Australian Directive’s different deadline and not assume equivalence in scheduling. However, Requirement 2 (rewiring) must be completed before further flight after the Requirement 1 inspection, which imposes a strict short-term limitation if non-compliance is found at inspection (Requirement; Compliance).

No alternative methods of compliance provided in the text: The AD prescribes rewiring "in accordance with the instructions provided by SIL PJ79-27 Revision 1" if Requirement 1 shows non-compliance (Requirement 2). The Directive does not set out alternative methods of compliance or a process for obtaining an alternative; consequently, operators should not assume flexibility not stated in the text.

Small domestic fleet but binding effect: CASA notes there have been no incidents of a similar nature in Australia and that only 14 of the affected aeroplanes are on the Australian register (Background). Despite that small domestic presence and lack of reported local incidents, CASA considers itself required to publish State of design ADs and issued this Directive (Background). Operators may therefore find the AD’s imposition is driven by regulatory duty rather than local incident history.

No enforcement details in the document: The Directive sets requirements and deadlines but contains no penalty or enforcement description in the text provided (see Penalties and enforcement). Operators should not expect explicit enforcement processes or sanction schedules in this document; any enforcement regime would be found in external regulatory or statutory texts, not in the AD as supplied.

Effective date precedes some compliance deadlines: The AD becomes effective on 25 September 2008 (Compliance), but Requirement 1’s latest completion date is 25 September 2009 (Compliance). Operators must note that the Directive’s operative force begins in 2008; however, the AD allows a 12-month window for the records inspection tied to scheduled maintenance. Failure to treat the effective date as the start of an enforceable obligation could lead to non-compliance.

Rewiring must be done before further flight after inspection: If the records check reveals non-compliance, the AD imposes a tight constraint: rewiring must be completed before the aircraft’s next flight after the inspection (Requirement 2; Compliance). This means that an operator who discovers non-compliance during a pre-flight check or at a scheduled maintenance event must not return the aircraft to service until the rewiring is completed.

Reference materials may be dated: The manufacturer’s SILs referred to are dated 1979 (Requirement). Operators must ensure they access the correct documentation, specifically SIL PJ79-27 Revision 1 dated 13 September 1979, because that Revision 1 is the operative instruction for corrective rewiring (Requirement 2).

Step 1 , Identify affected aircraft: Confirm whether the aircraft is a Cessna Model 441 and whether its serial number falls within 441-0001 through 441-0109. The AD’s Applicability is limited to that model and serial-number range; only those aircraft are subject to this Directive’s requirements (Applicability).

Step 2 , Timing for record check: Schedule a records review to determine whether the aircraft’s maintenance records show compliance with Cessna Propjet SIL PJ79-27 dated 30 July 1979 or SIL PJ79-27 Revision 1 dated 13 September 1979. This Requirement 1 check must be carried out at the aircraft’s next scheduled maintenance but in any event no later than 25 September 2009 (Requirement 1; Compliance). Ensure the records check is logged with date, person conducting the review, and the exact entry in the records relied upon.

Step 3 , Evidence of prior FAA AD compliance: If records indicate that FAA AD 79-19-12 Amdt 39-3574 was complied with, that documentation is considered acceptable evidence of compliance with this Directive (Requirement 1 Note 1). When relying on FAA AD compliance, preserve the specific maintenance entries, work orders, AD compliance stamps, or equivalent documentation that explicitly references FAA AD 79-19-12 or its amendment number, because the AD accepts FAA compliance only when documented (Requirement, Note 1).

Step 4 , If records do not evidence compliance, rewire: If Requirement 1 does not indicate compliance with SIL PJ79-27 or Revision 1, the operator must rewire the engine control wiring in accordance with the instructions provided by SIL PJ79-27 Revision 1 (Requirement 2). Arrange for an appropriately authorised maintenance organisation or engineer to perform the rewiring work in accordance with the SIL’s procedures.

Step 5 , Timing for the rewiring: Where rewiring is required following a records check, the operator must not return the aircraft to flight until the rewiring has been completed , Requirement 2 must be satisfied before further flight after the Requirement 1 inspection (Compliance). Plan maintenance slots, parts procurement, and authorisation accordingly to avoid grounding delays.

Step 6 , Documentation and sign-off: After completion of either the records check (if it shows compliance) or the rewiring work, ensure that the maintenance records are updated to show the works performed, the method used (for example, SIL PJ79-27 Revision 1 or FAA AD compliance citation), the date of completion, the identity and authorisation details of the person or organisation carrying out the work, and any certification or release to service. The AD relies on maintenance records as the evidence of compliance (Requirement).

Step 7 , Access the correct technical material: Obtain the specific Cessna Propjet SIL PJ79-27 Revision 1 dated 13 September 1979, because that is the revision expressly cited for rewiring instructions (Requirement 2). Ensure the maintenance personnel follow the SIL’s instructions precisely, because the AD prescribes compliance in accordance with that document.

Step 8 , Liaise with CASA if in doubt: Although the AD itself does not set out processes for alternative methods of compliance or waivers, if there is uncertainty about whether the recorded FAA AD compliance meets the Directive’s requirement, or if access to SIL Revision 1 is problematic, operators should raise the issue with CASA or their nominated aviation regulatory advisors. The Background notes CASA’s role in issuing State-of-design ADs, and the AD is signed by a CASA delegate; CASA is therefore the relevant authority for clarifying compliance queries (Background).

Step 9 , Be mindful of scheduling consequences: The AD permits the records check to be deferred to the next scheduled maintenance but no later than 25 September 2009. Do not assume indefinite deferral; schedule the records check within that window to avoid non-compliance. If the records check reveals non-compliance, do not return the aircraft to service until rewiring is complete (Requirement; Compliance).

Step 10 , Maintain traceable evidence for future audits: Because the AD accepts FAA AD compliance when recorded (Requirement, Note 1), and because maintenance records are the compliance evidence, keep a clear and traceable audit trail showing either the earlier FAA AD compliance or the SIL-based rewiring work. This includes work orders, parts used, sign-off by the authorised maintenance engineer, and entries in the aircraft’s maintenance log.

Who pays and who decides operationally: The operator/owner bears the direct costs of the records check and, if necessary, the rewiring work required by SIL PJ79-27 Revision 1. Decisions about scheduling, selection of maintenance provider, parts procurement, and return-to-service certification rest with the operator and their authorised maintenance organisation; CASA sets the requirement and the compliance dates (Requirement; Compliance; Background).

Signature and effective date: Note that the AD is signed by a CASA delegate (Charles Lenarcic) on 15 August 2008 and becomes effective on 25 September 2008 (Background; signature; Compliance). Compliance planning should therefore assume the AD’s obligations were operative from that effective date onwards.

Final practical note: The AD text provides no alternative methods of compliance within its body. Compliance is therefore achieved by documented evidence of prior FAA AD work or by performing the rewiring in accordance with SIL PJ79-27 Revision 1 and documenting that completion before further flight following inspection (Requirement; Note 1; Compliance).