AD/CESSNA 400/116 - Dual Battery Switch

The AD is focused on a single aircraft system risk and a single remediation pathway. The risk identified in the Background is a possible wiring error of the dual battery switch that could contribute to thermal runaway in nickel‑cadmium batteries. The AD does not introduce design changes directly; instead it mandates application of a pre‑existing manufacturer Service Information Letter (SIL PJ83‑9 Revision 1) as the corrective method where records do not show prior compliance.

The central regulatory concept is conversion of a State‑of‑design airworthiness action into an Australian AD. The document states that the FAA originally issued AD 83‑12‑03 and that CASA is "required to publish State of design ADs which may affect Australian aircraft" (Background). CASA’s implementation therefore follows an "internal review of Australian Airworthiness Directives" that identified the absence of an earlier Australian AD corresponding to FAA AD 83‑12‑03. The AD references the FAA AD in Note 3 ("FAA AD 83‑12‑03 Amdt 39‑4669 refers") and explicitly accepts compliance with the FAA AD as satisfying the Australian AD (Note 2).

Operationally the AD uses three technical instruments: (1) maintenance records as evidence, (2) the manufacturer’s SIL PJ83‑9 Revision 1 as the procedural standard for modification, and (3) serial‑number‑based applicability, including a carve‑out for aircraft fitted with a later revision of a Service Kit (SK441‑37 Revision 1 or later) that the AD states are not affected (Note 1). The AD also makes a timing distinction between an administrative check (check records) and a physical modification. The records check is permitted a longer compliance window ("next scheduled maintenance but no later than 25 September 2009"); the modification, if needed, is required "before further flight" (Compliance).

The document contains several cross‑references to service paperwork and prior regulatory action, notably SIL PJ83‑9 and FAA AD 83‑12‑03. Those cross‑references create two pathways for compliance: documentary evidence (existing maintenance records showing SIL or FAA AD compliance) or affirmative hardware modification per the SIL. The AD does not itself specify technical steps beyond mandating conformance with SIL PJ83‑9 Revision 1, and it leaves the technical execution to maintenance personnel following that SIL.

The primary direct legal addressees are operators and owners of Cessna Model 441 aeroplanes within the serial number ranges listed in the Applicability clause: serial numbers 441‑0001 through 441‑0172 (with Service Kit SK441‑37 incorporated) and serial numbers 441‑0173 through 441‑0311 (Applicability). The AD text also records that 31 of the affected aeroplanes are "currently on the Australian register" (Background). That numeric statement indicates the set of aircraft in Australia which must take the AD’s required steps, while other affected serial numbers may be located outside Australia.

Secondary affected parties include maintenance organisations, engineers and certifying staff who must inspect maintenance records and, where required, perform the modification to the dual battery switch installation in accordance with the manufacturer’s SIL PJ83‑9 Revision 1 (Requirement 2). The AD treats prior compliance with the FAA AD as acceptable (Note 2), so those who can demonstrate compliance with FAA AD 83‑12‑03 satisfy the recording/check obligation without further physical modification.

The AD expressly excludes aeroplanes that have incorporated Service Kit SK441‑37 Revision 1 or a later revision (Note 1: "Aeroplanes incorporating SK441‑37 Revision 1 or later revision are not affected by this Directive"). This creates a division within the serial number block: some aircraft may already be compliant by virtue of later kit incorporation and therefore are outside the AD’s obligations. Owners or maintainers therefore need to determine both serial number applicability and the exact revision of any SK441‑37 incorporation as part of the records check.

Administratively, CASA (represented in the document by the Delegate, Charles Lenarcic) is the issuing authority; the AD records the date of issue (15 August 2008) and the AD effective date (25 September 2008). The AD does not identify inspectors, penalty regimes or enforcement processes within the text provided, so the immediate practical actors are the operators/owners who must check records and maintenance providers who must perform modifications where required.

Finally, the AD notes that "The requirements of this Directive were most likely accomplished prior to the aircraft’s arrival in Australia" (Requirement, Note 2). That implies that aircraft imported after original FAA action may commonly already comply, but the formal onus remains on the Australian operator to verify recorded compliance.

The AD establishes two specific duties and associated timing obligations for affected aircraft operators/owners, expressed as Requirement 1 and Requirement 2 in the text.

Duty 1 , Records check. Operators must "check the aircraft records to determine if Cessna Conquest Service Information Letter (SIL) PJ83‑9 dated 22 April 1983 or Revision 1 dated 3 June 1983 has been complied with" (Requirement 1). The Compliance section sets the deadline for this check as "At the next scheduled maintenance but no later than 25 September 2009." The AD also explicitly accepts compliance with FAA AD 83‑12‑03 as equivalent evidence for meeting Requirement 1 (Requirement: "the aircraft’s maintenance records may indicate compliance with United States Federal Aviation Administration (FAA) AD 83‑12‑03, this is considered acceptable for compliance with this Directive").

Duty 2 , Modification where necessary. If Requirement 1 shows no compliance with the SIL or the FAA AD, operators must "modify the dual battery switch installation in accordance with SIL PJ83‑9 Revision 1" (Requirement 2). The Compliance timing for Requirement 2 is "Before further flight after the Requirement 1 determination." In other words, if records do not show compliance, the operator cannot return the aeroplane to service until the modification required by the SIL Revision 1 has been carried out.

Rights and procedural options in the AD text are narrow and defined by equivalence: the only recognised alternative to performing the SIL modification is documentary proof that the FAA AD 83‑12‑03 has already been complied with. The AD does not set out any appeal, variation or alternate‑means‑of‑compliance procedure within the provided text. It does, however, provide an exception by reference: aircraft incorporating SK441‑37 Revision 1 or later revisions are "not affected by this Directive" (Note 1), which functions as a de‑facto right to be outside the AD’s obligations where that specific kit revision is present.

The AD does not enumerate any other rights , for example, there is no stated right to a deferred compliance plan or an express mechanism for seeking approval for alternative corrective actions in the text provided. The Directive also provides contextual guidance that compliance was likely already accomplished before Australian arrival for many aircraft (Requirement, Note 2). That guidance can be used by operators to prioritise the records check.

Finally, the AD sets a formal effective date (25 September 2008) (Compliance), establishing the date from which the stated duties operate; the records check deadline and the "before further flight" requirement for modifications create a two‑stage compliance regime that combines an administrative verification duty with an immediate corrective action obligation where non‑compliance is discovered.

The AD text supplied does not include any express penalty provisions, enforcement mechanisms, or administrative sanctioning procedures. It states the obligations to check records and to perform a modification where necessary and provides the AD effective date (Compliance: "This Airworthiness Directive becomes effective on 25 September 2008") and deadlines for compliance, but it does not specify fines, suspension mechanisms, or the process by which CASA will monitor or enforce compliance within the document itself.

Because the AD is presented as a formal directive issued by the Civil Aviation Safety Authority (CASA) , signed by a Delegate (Charles Lenarcic) on 15 August 2008 (signature block and date) , it functions as an instrument requiring the listed actions. However, the text does not describe who will verify compliance, what records CASA will inspect, or what administrative steps CASA will take in the event of failure to comply. There is no on‑its‑face description of legal or disciplinary sanctions in this Directive as published.

The AD does reference equivalence of FAA AD compliance for satisfying the requirement (Requirement, Note 2), which indicates an evidentiary standard for documentary compliance. The practical enforcement implication built into the text is that operators must either have documentary proof of compliance with the SIL or the FAA AD, or must perform the SIL‑mandated modification before further flight where no such proof exists. The AD also places a clear timing obligation on the records check (by next scheduled maintenance but no later than 25 September 2009) and an immediate grounding effect for aircraft where the modification is required before further flight, in the sense that return to service is conditioned on completing the modification (Compliance: "For Requirement 2 - Before further flight after the Requirement 1 determination").

Absent from the text are descriptions of penalties, prosecution, or certificate action. The document likewise does not set out compliance monitoring procedures or timelines for CASA‑initiated inspections. Those enforcement aspects may be governed by other regulatory instruments, but such instruments are not included or referenced with penalty details in the AD text provided.

The AD expressly references and builds on prior regulatory and manufacturer materials rather than creating broad new legal relationships. It cross‑references a United States FAA AD (FAA AD 83‑12‑03, Amdt 39‑4669) and a manufacturer Service Information Letter (SIL PJ83‑9 and its Revision 1). The document states that the FAA AD was originally issued to detect and correct a possible error in battery switch wiring that may contribute to thermal runaway of nickel‑cadmium batteries (Background). CASA notes that an Australian AD was not previously issued in response to FAA AD 83‑12‑03 and that, because CASA is "required to publish State of design ADs which may affect Australian aircraft", it is issuing this Directive (Background).

Practically, the AD sets up direct equivalence between compliance with FAA AD 83‑12‑03 and compliance with this Australian AD: "the aircraft’s maintenance records may indicate compliance with United States Federal Aviation Administration (FAA) AD 83‑12‑03, this is considered acceptable for compliance with this Directive" (Requirement, Note 2). That creates a specific legal interaction: an operator who can demonstrate compliance with the FAA AD satisfies the Australian AD’s documentary requirement without needing to repeat the SIL‑mandated modification. The AD thereby recognises FAA regulatory actions as an acceptable compliance pathway for Australian operators in this instance.

The AD also interacts with manufacturer technical documentation: the operative corrective action is an instruction to "modify the dual battery switch installation in accordance with SIL PJ83‑9 Revision 1" (Requirement 2). The AD therefore imposes a legally mandated obligation to implement a manufacturer's service instruction when that instruction has not already been complied with and recorded.

There is also an interaction with aircraft configuration control and modification history: aircraft that have incorporated Service Kit SK441‑37 Revision 1 or later revisions are expressly out of scope ("not affected by this Directive" , Note 1). That means prior modification actions at the component/kit level alter the aircraft's legal status under the AD.

The AD does not reference any domestic civil aviation regulations, certificate conditions, or administrative sanctioning provisions. It likewise does not spell out inter‑jurisdictional enforcement mechanisms beyond recognising FAA AD compliance as acceptable. Any broader legal consequences or cross‑references to Australian Civil Aviation Regulations or enforcement procedures are not present in the text provided and therefore cannot be asserted on the basis of this document alone.

The AD text supplies a limited but specific amendment and documentary history relevant to its requirements. Key dates and references appearing in the AD are:

• The Cessna Conquest Service Information Letter (SIL) PJ83‑9 dated 22 April 1983 and its Revision 1 dated 3 June 1983 are the technical documents to be checked or implemented (Requirement 1). The AD explicitly instructs compliance with SIL PJ83‑9 Revision 1 where records do not show prior compliance.

• The FAA action referenced is FAA AD 83‑12‑03, as amended by Amdt 39‑4669 (Requirement, Note 3: "FAA AD 83‑12‑03 Amdt 39‑4669 refers"). The AD recognises compliance with that FAA AD as acceptable evidence.

• The AD itself was issued on 15 August 2008, as evidenced by the delegate's signature block (Charles Lenarcic, Delegate of the Civil Aviation Safety Authority, 15 August 2008). The AD states an effective date of 25 September 2008 ("This Airworthiness Directive becomes effective on 25 September 2008") and sets compliance deadlines that extend into 2009 (Compliance: Requirement 1 due "at the next scheduled maintenance but no later than 25 September 2009").

• The Applicability clause references Service Kit SK441‑37 and adds a proviso that aircraft incorporating SK441‑37 Revision 1 or later are not affected by the Directive (Note 1). The Applicability also identifies serial numbers 441‑0001 through 441‑0172 "with Service Kit SK441‑37 incorporated" and serial numbers 441‑0173 through 441‑0311.

Beyond these dates and cross‑references, the AD text contains no further amendment history. There is no indication in the provided text of subsequent amendments, replacements, revocations, or corrective errata to this Australian AD. The document does not include an explicit "amendments" section or any list of prior Australian ADs other than the internal review that triggered issuance. Any later changes, superseding ADs, or revocation actions are not recorded in the text supplied.

Where the AD notes that "the requirements of this Directive were most likely accomplished prior to the aircraft’s arrival in Australia" (Requirement, Note 2), it implicitly recognises a historical sequence: original FAA action and manufacturer technical notices dating from 1983 preceded this 2008 Australian AD. The AD formalises that historical chain by making the SIL Revision 1 or the FAA AD compliance the operative standard for Australian‑registered affected aircraft.

The AD text contains no references to litigation, court decisions, challenges, or legal proceedings. It does not mention any appeals against the Directive, nor does it identify any disputes or judicial interpretations. The signature block and the AD narrative are administrative in form and do not include or cite case law.

Because the text does not record litigation or judicial review, there is no litigation history to summarise from this source. The absence of recorded litigation in the document does not itself indicate whether litigation occurred elsewhere or subsequently; it simply reflects that the AD as published contains no mention of cases or legal challenges. The AD is an administrative instrument issued by the Civil Aviation Safety Authority and, as presented, is a standalone regulatory directive without appended adjudicative narrative.

Practically for operators and advisers, the absence of litigation references in the AD means that any questions about interpretation, enforceability, or the scope of the Directive must be addressed to the issuing authority (CASA) or by consulting other legal documents and administrative guidance outside this AD. The AD does not set out dispute resolution routes, appeal mechanisms, or processes for applying for exemptions or alternative means of compliance within the text provided.

In short, on the basis of the supplied material, there is no recorded litigation history attached to AD/CESSNA 400/116: the document itself contains no litigation citations, case law references, or records of judicial proceedings.

The AD contains several practical pitfalls and tight details that can be missed if readers scan rather than read carefully.

1. Serial number nuance and kit incorporation. Applicability lists two serial‑number ranges and attaches an incorporation qualifier to the first range: "441‑0001 through 441‑0172 with Service Kit SK441‑37 incorporated, and 441‑0173 through 441‑0311." That wording means some aeroplanes in the earlier serial range are only in scope if SK441‑37 is incorporated. Separately, Note 1 states that aeroplanes incorporating SK441‑37 Revision 1 or later are not affected. Operators must therefore check both the serial number and the exact revision of any SK441‑37 incorporation. A simple check of serial number alone is insufficient to determine applicability.

2. Documentary equivalence with FAA AD. The AD declares that compliance with FAA AD 83‑12‑03 is "considered acceptable for compliance with this Directive" (Requirement, Note 2). Operators relying on this pathway must ensure that their documentary evidence specifically demonstrates compliance with FAA AD 83‑12‑03 , generic or ambiguous maintenance entries may not suffice. The Directive allows for acceptance of the FAA AD, but it does not describe the form or content of acceptable evidence.

3. Two‑stage timing. The records check (Requirement 1) has a relatively generous window: at the next scheduled maintenance but no later than 25 September 2009. However, if that records check reveals non‑compliance, the physical correction (Requirement 2) must be completed "before further flight". That creates a potential operational "gotcha" where aircraft that are airborne and not found to have recorded compliance must be grounded until the SIL‑specified modification is completed.

4. Historical compliance assumption. The AD notes that the requirements "were most likely accomplished prior to the aircraft’s arrival in Australia" (Requirement, Note 2). Operators who assume compliance without documentary support risk overlooking a missing or incorrectly recorded modification. The AD requires a records check , absence of a record requires the modification.

5. No description of the modification in the AD text. The AD mandates modification "in accordance with SIL PJ83‑9 Revision 1", but it does not reproduce the technical steps. Operators therefore need access to the SIL Revision 1 content and must ensure maintenance personnel follow the SIL precisely. Lack of access to that SIL or misinterpretation of revision status is a practical risk.

6. Effective and issuance dates. The AD became effective on 25 September 2008 and was issued on 15 August 2008. The record‑check deadline extends to 25 September 2009. Operators should ensure their scheduling captures these dates and does not treat the later deadline as optional.

7. No penalty or enforcement detail in the AD. The AD does not include penalties or enforcement mechanisms in the text given. This is a "gotcha" insofar as operators may expect a penalty schedule or explicit enforcement process in the AD itself; they will not find one here and must look to other CASA instruments or regulatory frameworks for enforcement details.

8. Scope because of SK441‑37 Revision 1. Note 1 disqualifies aeroplanes incorporating SK441‑37 Revision 1 or later revisions, but the AD does not explain how to identify or prove the revision in all maintenance records. Operators must examine modification records, stamps, or historical maintenance data to verify the specific revision incorporated.

9. The AD is narrow in remedy. The only alternate compliance route stated is FAA AD compliance. There is no stated procedure for applying an alternative method of compliance within the AD text. Operators seeking an alternative must look elsewhere for procedural avenues.

Reading the AD precisely and confirming the exact maintenance entries, kit revisions, and access to the SIL are critical to avoid non‑compliance surprises.

The AD sets out a clear, two‑step compliance pathway. Follow the steps below, referencing the AD text for deadlines.

Step 1 , Records inspection (Requirement 1)

• Determine whether the aeroplane is within the Applicability serial‑number ranges in the AD: 441‑0001 through 441‑0172 (with Service Kit SK441‑37 incorporated) and 441‑0173 through 441‑0311 (Applicability).
• If the aircraft incorporates Service Kit SK441‑37 Revision 1 or later, note that the AD states such aircraft are "not affected by this Directive" (Note 1), and no further action under this AD is required.
• Check the aircraft maintenance records to determine whether Cessna SIL PJ83‑9 dated 22 April 1983 or SIL PJ83‑9 Revision 1 dated 3 June 1983 has been complied with (Requirement 1).
• Alternatively, confirm whether the maintenance records show compliance with FAA AD 83‑12‑03 (Amdt 39‑4669), which the AD states is acceptable proof of compliance (Requirement, Note 2).
• Complete this records inspection at the next scheduled maintenance, but no later than 25 September 2009 (Compliance).

Step 2 , Modification where records are deficient (Requirement 2)

• If the records inspection does not show compliance with SIL PJ83‑9 or Revision 1, arrange for modification of the dual battery switch installation in accordance with SIL PJ83‑9 Revision 1 (Requirement 2).
• Ensure maintenance personnel have access to the exact SIL Revision 1 technical instructions and follow them precisely. The AD does not include technical steps; compliance requires implementing the SIL.
• Do not return the aeroplane to flight until the modification is complete; the AD requires completion "before further flight after the Requirement 1 determination" (Compliance).

Practical compliance checklist items

• Verify serial number and kit revision status. The AD’s applicability depends on both serial number and the incorporation/revision state of SK441‑37 (Applicability; Note 1).
• Obtain and retain documentary evidence that either (a) SIL PJ83‑9 Revision 1 compliance has been performed and recorded, or (b) FAA AD 83‑12‑03 compliance is documented, because the AD accepts FAA AD compliance as equivalent (Requirement, Note 2).
• If modification is required, maintain records showing who performed the modification, the date, parts used, and the specific SIL revision followed, so that a future records check will clearly show compliance.
• Coordinate scheduling: perform the records check at the next scheduled maintenance (or sooner) and ensure that, if a modification is needed, the aircraft is not released to fly until the SIL‑specified work is completed.

Who should perform the work

• A suitably authorised maintenance organisation or certifying maintenance personnel should perform the modification per usual aviation maintenance certification practices. The AD prescribes the standard (SIL PJ83‑9 Revision 1) but leaves technical execution to qualified maintenance staff.

Document retention

• Retain records of the check and any modification in the aircraft maintenance log in a form that unambiguously evidences compliance with the SIL or FAA AD, since the AD relies on those records for compliance verification.

Timing summary

• AD effective date: 25 September 2008 (Compliance).
• Records check deadline (Requirement 1): at the next scheduled maintenance but no later than 25 September 2009.
• Modification (Requirement 2): if required, must be completed before further flight after the records check reveals non‑compliance.

By following these steps and keeping clear records that map to the AD’s stated acceptable evidence (SIL PJ83‑9 Revision 1 or FAA AD 83‑12‑03), operators will meet the AD’s documented requirements as set out in the Directive.