AD/TBM 700/51 - Wiring Harness Inspection

The AD is built around a small set of operational and normative concepts that determine how an operator implements it.

• Applicability. The AD is limited to "Model TBM700 N aeroplanes serial numbers 434 to 478 inclusive." The AD also provides a nomenclature clarification: "Note 1: TBM 850 is the commercial designation of the TBM700 N." This confines the directive to a specific production run and avoids ambiguity about the commercial model name.

• Normative technical document. The AD makes compliance contingent on following EADS SOCATA Service Bulletin 70‑163‑92 dated November 2008, or "later revision approved by the European Aviation Safety Agency (EASA)." The SB is the technical instrument that contains the inspection and repair procedure; the AD itself does not reproduce those technical steps but makes the SB the binding technical reference (Requirement 1).

• Inspection scope and location. The inspection is narrowly located: "at frame C14 and between frames C16 and C17." The AD’s required inspection addresses both "condition and routing" of the electrical wiring harness in these areas (Requirement 1), signalling two separate failure modes: physical damage (chafing, overheating) and incorrect routing that could permit interference with structural or furnishing elements.

• Corrective action and timing. If "any discrepancy in the harness routing or any chafed wire is found," the AD mandates repair and re‑routing "as instructed in the SB 70‑163‑92 or later revision approved by the EASA." The timing is strict: the inspection must occur "within 100 hours time in service or 12 months" after the AD effective date; any repairs required as a result of the inspection must be completed "before further flight" (Compliance).

• Safety rationale. The Background records the causal chain observed in service: damaged wiring harness produced an air conditioning circuit breaker trip and local overheating; the damage was traced to interference with under‑floor attachment fittings of the cabin partition net caused by incorrect production routing; the AD links that damage to the hazard of an electrical short and "potential loss of several functions essential for the safety of flight."

• Cross‑reference to EASA. The AD refers to EASA AD 2009‑0006, and it conditions the permissive use of later SB revisions on EASA approval. This links the Australian AD to European regulatory actions and to the manufacturer's SB revision process (Note 2; Requirement).

These concepts set the operational constraints an affected operator must observe: determine applicability by serial number; obtain and apply the specified SB (or an EASA‑approved later revision); inspect the defined zones within the stated time window; and remediate any defects prior to further flight.

The AD explicitly affects owners and operators of Aerospatiale (Socata) TBM700 N aircraft with serial numbers 434 to 478 inclusive. Those parties must ensure compliance within the specified inspection window and, where necessary, effect repairs before further flight (Applicability; Compliance; Requirement 2). The AD also affects maintenance organisations and certificated maintenance personnel who carry out inspections and repairs, because the AD makes the EADS SOCATA SB 70‑163‑92 (Nov 2008) or later EASA‑approved revision the normative technical reference for the work to be performed (Requirement 1).

The Australian Civil Aviation Safety Authority (CASA) is the issuing regulator here; the AD is published under the authority of a delegate (James Coyne), and it becomes effective on a stated date (signed 27 January 2009; "This Airworthiness Directive becomes effective on 12 March 2009"). As an instrument issued by CASA, the AD places a regulatory obligation on affected operators within CASA’s jurisdiction.

The manufacturer, EADS SOCATA, is implicated because the AD mandates use of its SB as the compliance document. EASA is implicated through the AD’s conditional approval language,later revisions of the SB are allowable if approved by EASA,and through the explicit cross‑reference to EASA AD 2009‑0006 (Requirement; Note 2). That creates an operational interaction where operators must track EASA approvals and the manufacturer’s SB revisions.

Indirectly affected parties include operators’ customers and third‑party service providers who rely on availability of aircraft: the AD’s requirement to repair before further flight may impose immediate grounding where defects are found. The AD does not list insurers, registries, or other overseas regulators, but by referencing EASA instruments it presumes cross‑jurisdictional coordination between CASA, EADS SOCATA, and EASA.

Who pays and acts. The AD does not state who bears the financial cost; operationally, the owner/operator must arrange and pay for the inspection and any necessary repairs performed in compliance with the SB. Maintenance organisations supply skilled labour and facilities to execute the SB procedures. CASA, through its delegate, is the decision maker for issuing the AD and determining its effective date; EASA remains a decision authority for approving SB revisions referenced as permissible alternatives.

Duties imposed by the AD are specific and time‑limited.

• Duty to inspect within a set interval. Requirement 1 obliges affected operators to "Inspect for condition and routing of the electrical wiring harness at frame C14 and between frames C16 and C17" in accordance with SB 70‑163‑92 (Nov 2008) or later EASA‑approved revision. The Compliance paragraph fixes the inspection deadline as "within 100 hours time in service or 12 months, whichever occurs first, after the effective date of this Directive." The Effective date is 12 March 2009.

• Duty to repair before further flight if defects are found. Requirement 2 mandates that "If any discrepancy in the harness routing or any chafed wire is found, repair and re‑route the electrical harness as instructed in the SB 70‑163‑92 or later revision approved by the EASA," and the Compliance provision requires that the repairs be completed "before further flight" after the Requirement 1 inspection.

• Duty to use the specified normative document. The AD makes adherence to the manufacturer's SB 70‑163‑92 (Nov 2008) or an EASA‑approved later revision the means of compliance. The AD does not itself provide the technical inspection or repair steps; those are located in the SB and must be followed as the approved method of compliance (Requirement 1; Requirement 2).

Privileges and permitted alternatives.

• Permitted use of later approved SB revisions. The AD explicitly allows compliance by following "later revision[s] approved by the European Aviation Safety Agency (EASA)." That gives operators the right to use an amended SB if and only if the revision has EASA approval. The AD therefore recognises manufacturer updates but conditions them on EASA approval (Requirement).

• No explicit authorisation for alternative methods of compliance (AMOCs) within the AD text. The AD does not set out an AMOC process or delegate authority to CASA or another body to accept alternative inspection or repair procedures. The only normative permissive clause is the EASA approval of later SB revisions. Operators seeking to use a method other than the SB as approved by EASA would need to pursue regulatory approval outside the text of this AD.

Operational consequences of the duties.

• Time pressure and flight scheduling. The inspection deadline (100 hours TIS or 12 months) imposes a deadline that operators must measure against aircraft utilisation. If a defect is found, the "before further flight" requirement creates an immediate operational constraint: the aircraft cannot be flown until the prescribed repair and re‑routing are carried out in accordance with the SB.

• Technical dependency on manufacturer and EASA. Because the SB contains the required technical work and later revisions are only acceptable if EASA approves them, operators’ compliant actions depend on obtaining the SB and checking the EASA approval status of any revision.

Documentary duties. The AD text does not itself list maintenance recording or logbook entries. It does, however, implicitly require that the inspection and any corrective action be performed in accordance with the SB, which typically will require appropriate maintenance records. The AD does not, within its text, create or describe specific documentary requirements.

The AD text as supplied does not specify particular penalties, fines or detailed enforcement procedures. The instrument records that it is issued by a CASA delegate and includes an effective date ("This Airworthiness Directive becomes effective on 12 March 2009," signed by James Coyne, Delegate of the Civil Aviation Safety Authority, 27 January 2009), but it does not set out enforcement mechanisms such as monetary penalties, suspension powers, or administrative sanctions within the AD itself.

This absence is material for two reasons. First, the AD establishes a mandatory safety requirement (inspection within a fixed interval and repair before further flight where defects are identified), but it does not itself state how non‑compliance will be detected or penalised. Second, the AD ties compliance to an external technical document (EADS SOCATA SB 70‑163‑92 or later EASA‑approved revision). Any practical enforcement therefore depends on the broader aviation regulatory framework and CASA’s generic enforcement powers and procedures rather than on penalties embedded in this AD.

Practical enforcement implications that follow from the AD’s text:

• CASA as issuer. The AD’s issuance by a CASA delegate establishes it as a regulatory instrument of the Australian aviation authority. While the AD does not list sanctions, CASA’s status as issuer signals that failure to comply would be a breach of a CASA directive; enforcement action, if any, would proceed under CASA’s general regulatory powers rather than under text specific to this AD.

• Immediate flight prohibition where defects are found. The AD’s "before further flight" requirement effectively prohibits flight of an affected aircraft that has defects identified by the inspection until the prescribed repairs are completed in accordance with the SB. Operationally, this has the immediate effect of grounding the aircraft pending repair, irrespective of whether the AD lists a fine for non‑compliance.

• Dependence on other regulatory instruments for enforcement. The AD references EASA approval for SB revisions and EASA AD 2009‑0006, which creates an administrative ecosystem of compliance. The AD itself provides no enforcement checklist, audit schedule or record retention requirement. Detection of non‑compliance therefore depends on typical surveillance mechanisms: maintenance inspections by approved organisations, logbook review, repair invoices, and any CASA audits or surveillance activities (none of which are specified in the AD text).

Because the AD does not include explicit penalty language, parties seeking clarity about enforcement consequences should consult CASA’s wider regulatory rules and enforcement policies, and any statutory provisions governing breach of airworthiness directives. The AD, however, makes the safety obligation unambiguous: inspection within a set interval and mandatory repair before further flight where defects are found.

The AD’s text expressly cross‑references external regulatory and technical material and thereby creates an interaction with those instruments.

• Relationship to manufacturer service documentation. The AD makes EADS SOCATA Service Bulletin 70‑163‑92 dated November 2008 (SB 70‑163‑92) the normative method of compliance ("in accordance with the accomplishment instructions of EADS SOCATA Service Bulletin (SB) 70‑163‑92 dated November 2008 or later revision approved by the European Aviation Safety Agency (EASA)"). This means the AD does not itself contain the technical steps; compliant action requires following the manufacturer’s SB as approved for the purposes of the AD.

• Linkage to EASA approvals and ADs. The AD requires that later revisions of the SB be "approved by the European Aviation Safety Agency (EASA)" to be acceptable as a method of compliance. Additionally, the AD includes "Note 2: EASA AD 2009‑0006 refers." These cross‑references create two layers of interaction: first, a dependency on EASA’s approval process for SB revisions; second, a pointer to an EASA AD that operators should consult. The AD therefore sits within an international regulatory dialogue where CASA’s directive refers to and relies upon decisions and approvals made by EASA.

• Interaction with airworthiness obligations. The AD prescribes inspection and repair requirements that relate directly to the airworthiness of affected aircraft. While the AD does not itself recite the statutory airworthiness provisions it enforces, its issuance by CASA implies an interaction with the national airworthiness regulatory regime (for example, obligations of registered aircraft owners and operators to maintain airworthiness). The AD does not set out how the maintenance will be recorded or approved, but by requiring compliance with the SB it implicitly engages established maintenance approval processes (approved maintenance organisations and certificated personnel).

• No other legislative cross‑references within the AD text. The supplied instrument contains no express references to other Australian statutes, regulations, or administrative penalty regimes. Its legal force and the consequences of non‑compliance would therefore be determined through CASA’s broader regulatory powers and procedures, and any statutory provisions governing the making and enforcement of airworthiness directives.

• International practicalities. Because the AD references EASA approvals and an EASA AD, operators with aircraft registered outside Australia but operating in Australian jurisdiction should be attentive to potential overlapping or divergent directives from other national authorities. The AD itself does not address conflict resolution between national directives, nor does it indicate whether alternative approvals from other authorities would be acceptable.

Operational conclusion from the text: compliance requires conjunction of action under the manufacturer's SB, confirmation of EASA approvals where a later SB revision is used, and observance of CASA’s AD effective date and timings. The AD does not provide a stand‑alone technical method or a domestic statutory enforcement mechanism in the body of the instrument; rather, it integrates manufacturer technical material and EASA approvals into CASA’s regulatory directive.

The AD document supplied does not record any prior amendments to AD/TBM 700/51 itself. It sets an effective date and contains references to external documents that may be revised:

• Effective date and signing. The AD is signed by a CASA delegate, James Coyne, on 27 January 2009, and the AD "becomes effective on 12 March 2009." There is no text within the AD that indicates any subsequent amendment, revocation, supersession or reissue of the AD.

• Dependence on SB revisions. The AD expressly permits compliance using "later revision[s] approved by the European Aviation Safety Agency (EASA)" of EADS SOCATA SB 70‑163‑92 (Requirement). That clause anticipates that the technical service bulletin may be revised after November 2008; however, the AD does not itself list any subsequent SB revisions nor record dates of approval by EASA. The AD therefore contemplates amendment of the technical method of compliance via the manufacturer and EASA without requiring amendment to the AD text. In practice, this approach decouples the AD’s longevity from the SB’s technical evolution.

• Cross‑reference to EASA AD 2009‑0006. The AD states "Note 2: EASA AD 2009‑0006 refers." This suggests that EASA issued its own directive(s) closely aligned in time with the CASA AD. The AD does not indicate whether it was issued in parallel, in response, or independently; nor does it list any subsequent CASA amendments linked to developments in EASA ADs.

• No recorded domestic amendments. The supplied instrument does not contain a history section, footnotes about amendments, or an "as amended" line. If CASA later amended, superseded, or revoked the AD, those changes are not contained in the text provided.

Operational inference from the AD’s wording. The only pathways for change described in the AD are external: (a) manufacturer SB revisions that are approved by EASA and (b) EASA AD actions referenced by the AD. The AD itself appears to be a single, dated directive with an effective date and no internal amendment history recorded in the supplied text. Parties needing to know whether the AD has been amended must consult CASA’s official AD records and the EASA approvals for SB revisions and EASA AD 2009‑0006.

The supplied AD contains no litigation history, case references, or notes of judicial testing. It cites no judicial or administrative decisions, and it does not name any cases. The text contains a technical finding (Background) and the prescriptive Requirements and Compliance provisions, but it does not record any disputes, appeals or judicial challenges against the AD, the SB, or the underlying technical premises.

Where litigation or appeals might arise in practice, they would typically concern one of a small number of factual or legal issues: the factual sufficiency of the safety finding, the scope of applicability to particular aircraft or serial numbers, the validity of the regulatory process used to issue the AD, or disputes about whether particular corrective work performed meets the AD’s requirements. None of these matters appear in the supplied instrument.

Because the instrument cross‑references EASA AD 2009‑0006 and depends on EASA‑approved SB revisions, any litigation history relevant to the corresponding EASA AD or the SB (for example, disputes about the technical content of the SB or EASA’s approval procedure) would not be recorded in this CASA AD unless CASA subsequently amended or annotated the AD with such a record. The supplied text contains no such additions.

Parties seeking to determine whether any litigation or administrative review exists in relation to this AD should consult CASA’s official records and EASA’s files for EASA AD 2009‑0006 and for any EASA decisions approving later revisions of SB 70‑163‑92. The AD itself provides no litigation history to analyse.

The AD contains a number of practical traps for the unwary that flow directly from its wording.

• Narrow serial‑number applicability. The AD applies only to "Model TBM700 N aeroplanes serial numbers 434 to 478 inclusive." Operators of TBM 700 variants outside these serial numbers, or owners who refer only to the commercial designation (TBM 850), may misread applicability without checking serial numbers. Note 1 clarifies that "TBM 850 is the commercial designation of the TBM700 N," but operators must still verify the exact serial number range.

• Reliance on an external SB that must be EASA‑approved if revised. Compliance requires following EADS SOCATA SB 70‑163‑92 (Nov 2008) or a "later revision approved by the European Aviation Safety Agency (EASA)." The AD does not itself include the step‑by‑step technical instructions. If an operator uses a later SB revision, the AD requires that that later revision be approved by EASA. Failure to confirm EASA approval of a later SB revision could render a maintenance action non‑compliant with the AD.

• Timing calculation. The Compliance provision fixes inspection timing as "within 100 hours time in service or 12 months, whichever occurs first, after the effective date of this Directive." Because the effective date is 12 March 2009, operators must calculate 100 TIS from that date or 12 months from that date. Miscalculation of the start date or the TIS hours could result in late inspections.

• Immediate grounding risk if defects found. The AD requires that any necessary repairs be completed "before further flight" after the inspection. That language means that discovering a discrepancy or chafed wire triggers an immediate prohibition against further flight until the SB‑mandated repair and re‑routing are completed. The AD does not provide grace or ferry flight exemptions within its text.

• Lack of AMOC language. The AD does not set out a domestic alternative methods of compliance process or delegate authority to accept other technical methods. The only permitted alternative in the AD text is a later SB revision approved by EASA. Operators wishing to pursue a different repair or inspection method must not assume the AD implicitly permits it without separate regulatory approval.

• Dependence on EASA AD 2009‑0006. The AD includes "Note 2: EASA AD 2009‑0006 refers." The note signals that EASA issued a corresponding or relevant directive. Operators who do not consult the referenced EASA AD and any related documentation risk missing additional instructions or clarifications relevant to compliance.

• No specific recordkeeping or audit instructions in the AD. The AD does not explicitly state how maintenance actions should be recorded for proof of compliance. While standard industry practice will require logbook entries and maintenance release documentation, the AD itself does not list documentary requirements; operators must rely on general maintenance and regulatory recordkeeping obligations to demonstrate compliance to CASA.

• The AD does not enumerate the exact inspection criteria in the AD text. The SB contains the "accomplishment instructions" but is not reproduced. Operators without immediate access to SB 70‑163‑92 (Nov 2008) cannot determine the required technical steps from the AD alone.

• Potential for multi‑jurisdictional confusion. Because the AD references EASA approvals and EASA AD 2009‑0006, operators in other jurisdictions or aircraft that move between registries should be careful to reconcile the CASA AD with any corresponding directives from other national authorities. The AD offers no cross‑jurisdictional reconciliation guidance.

These "gotchas" arise directly from the AD’s language and structure. They point to practical actions operators should take: confirm serial numbers, obtain the exact SB text and any EASA approvals for revisions, compute compliance windows from the AD effective date, and anticipate possible grounding and the need to secure maintenance slots to complete required repairs.

The AD prescribes a concise, stepwise means of compliance; operators must perform those steps exactly as described in the AD, using the referenced SB as the technical instrument.

1. Confirm applicability. Verify the aircraft is a Model TBM700 N whose serial number is within 434-478 inclusive. Note that "TBM 850 is the commercial designation of the TBM700 N" (Applicability; Note 1). If the aircraft is outside this serial range, the AD does not apply.

2. Obtain the normative technical document. Acquire EADS SOCATA Service Bulletin 70‑163‑92 dated November 2008. The AD permits use of later revisions only if they are "approved by the European Aviation Safety Agency (EASA)." Therefore, before relying on a later SB revision, verify that EASA has formally approved that revision.

3. Schedule and perform the inspection within the compliance window. The AD requires inspection "for condition and routing of the electrical wiring harness at frame C14 and between frames C16 and C17" per the accomplishment instructions in SB 70‑163‑92 or a later EASA‑approved revision (Requirement 1). The inspection must be completed "within 100 hours time in service or 12 months, whichever occurs first, after the effective date of this Directive." The AD’s effective date is 12 March 2009. Ensure the aircraft is made available to maintenance personnel to complete the inspection within that time window.

4. Implement corrective actions prescribed by the SB if defects are found. If "any discrepancy in the harness routing or any chafed wire is found," the AD requires repair and re‑routing "as instructed in the SB 70‑163‑92 or later revision approved by the EASA" (Requirement 2). The AD further requires that such repairs be completed "before further flight." Accordingly, if the inspection finds routing errors or chafed wiring, arrange for the corrective work immediately and do not return the aircraft to service until the SB procedures have been fully executed.

5. Verify personnel and approvals. Ensure that the inspection and any repairs are carried out by certificated maintenance personnel or organisations authorised under applicable maintenance regulations. The AD conditions compliance on following the SB instructions; it does not itself specify who may perform the work, but practical compliance will require use of appropriately authorised maintenance resources.

6. Cross‑check EASA AD 2009‑0006 and the EASA approval status of any SB revision. The AD includes "Note 2: EASA AD 2009‑0006 refers." Consult EASA AD 2009‑0006 for any additional instructions, differences, or clarifications. If relying on a later SB revision, confirm EASA approval documentation for that revision.

7. Document the work in accordance with standard maintenance and regulatory practice. Although the AD does not specify recordkeeping requirements, operators should create and retain maintenance records and logbook entries that demonstrate the inspection was completed within the AD’s time window and that any required repairs were made "before further flight." Such documentation will be necessary to demonstrate compliance to CASA during audits or surveillance.

8. Plan for operational disruption. Because the AD mandates repair before further flight where defects are found, plan maintenance slots and potential aircraft downtime. An immediate grounding may be required if chafed wiring or routing discrepancies are discovered.

9. Seek regulatory guidance where uncertain. The AD does not state an AMOC procedure or provide an internal CASA contact. If an operator seeks to use an alternative method of compliance, or if there is doubt about whether a later SB revision is EASA‑approved, obtain confirmation from the appropriate authority (EASA for SB approvals; CASA for Australian regulatory acceptance) before returning the aircraft to service under a non‑prescribed method.

To summarise the concrete compliance actions mandated by the AD: determine applicability by serial number; obtain SB 70‑163‑92 (Nov 2008) or a later EASA‑approved revision; perform the mandated inspection at frames C14 and between C16 and C17 within the stated hours/months window; and, where discrepancies or chafed wires are found, perform the SB‑prescribed repairs and re‑routing before any further flight. The AD’s Note 2 and the SB’s revision status must be checked and confirmed to establish an acceptable method of compliance.