AD/BEECH 36/53 - Chafing of Wire Harness/Connector and Fuel Line

The AD sets out a small set of tightly framed technical concepts and compliance mechanics. The principal technical objects are the P60 / J60 electrical connector, the associated wiring harness, and an adjacent fuel line. The AD identifies two failure modes: (1) “improper installation” of the connector/wiring/fuel line assembly, and (2) “chafing damage” of the wiring or fuel line. The operational hazard linked to those modes is fuel ingress and combustion risk: the AD warns that chafing “could lead to fuel leaking into the cockpit and fire in the cockpit if wiring arcs through the fuel line.”

On compliance mechanics the AD anchors inspection content to an external manufacturer's mandatory service bulletin: Hawker Beechcraft Mandatory Service Bulletin SB 28-3967, dated June 2009. The AD does not reproduce the inspection checklist or the repair instructions; it mandates adherence to that service bulletin for both the inspection and the corrective actions. It accepts later revisions of that SB only when those later revisions have been approved by the US FAA as an AMOC to FAA AD 2009-15-01. Thus the AD delegates technical detail to the SB and delegates a limited form of equivalence determination for later SB editions to FAA AMOC approvals. The AD explicitly references FAA AD 2009-15-01 Amdt 39-15964.

The AD is narrowly scoped by aircraft identity. The Applicability clause lists Model G36 aeroplanes and specific serial numbers (for example, serial numbers E-3630, E-3636 through E-3817, and several non-contiguous ranges). The AD therefore is not a class-wide mandate for all Bonanza or all G36 aircraft, but targeted to aircraft whose serial numbers are listed.

Timing is a core concept: an initial inspection must be performed “Within 10 hours time-in-service ... or 6 calendar months ... whichever occurs first.” This creates a short operational window for busy aeroplanes but may impose a strict deadline on low-utilisation aeroplanes because the calendar cap will apply. Further, the AD makes corrective work an absolute pre-flight requirement: if discrepancies are found, replacement, repair, or correction “must” be done “Before further flight after the Requirement inspection.”

The directive is issued by the Civil Aviation Safety Authority (CASA) and signed by James Coyne, Delegate of CASA. The AD identifies itself by code “AD/BEECH 36/53” and is dated “9/2009 DM” in its header. It shows an effective date (27 July 2009) and a signature date (17 July 2009). The AD thereby communicates regulator authorship and dates that determine compliance windows.

Finally, the AD contains a cross-jurisdictional acceptance mechanism: it accepts FAA-approved AMOCs to FAA AD 2009-15-01 as meeting the AD’s equivalent requirements. That is a limited form of external recognition rather than a wholesale delegation: it requires that FAA approval be of the AMOC to the FAA AD referenced, and it applies to “later revisions of the above SB” only if the FAA has approved them as an AMOC.

All of these concepts are stated explicitly in the AD document: the Applicability serial ranges, the Requirement steps pointing to SB 28-3967, the Compliance timing clause, the AMOC acceptance clause, the Background hazard statement, and the signature/effective date information.

The AD’s Applicability clause identifies the direct population affected: “Model G36 aeroplanes, serial numbers E- 3630, E-3636 through E-3817, E-3819 through E-3834, E-3836 through E-3887, E-3889 through E-3896, E-3898 and E-3899.” Owners and operators of those specific aeroplanes are the primary parties who must act under the AD because the directive prescribes mandatory inspections and corrective actions for those airframes.

Maintenance organisations and certificated maintenance personnel who service those Model G36 aeroplanes are a second-tier group affected in practice. The AD requires inspections “in accordance with Hawker Beechcraft Mandatory Service Bulletin SB 28-3967, dated June 2009,” and corrective actions “in accordance with SB28-3967.” Thus the work must be performed to the technical standard set out in that service bulletin; maintenance providers must have access to and comply with its procedures and parts specifications.

Pilots and operators are affected operationally because the AD conditions continued flight. The AD requires that any corrective action identified by the inspection be carried out “Before further flight after the Requirement inspection.” That creates an operational constraint: if the inspection reveals defects, the aircraft cannot be flown until the mandated repairs or replacements are completed in accordance with the SB. This affects flight planning, scheduling, and potential commercial operations.

Regulatory decision-makers are affected insofar as the AD sets a clause about accepting “Later revisions of the above SB, approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2009-15-01,” as acceptable for compliance. That clause engages cross-authority coordination: CASA (the issuing authority) has chosen to accept FAA AMOC approvals to the referenced FAA AD as satisfying the AD’s equivalence requirement for later SB revisions. The resulting practical effect is that operators seeking to use a later SB revision must ensure FAA AMOC approval to the FAA AD 2009-15-01 in order to rely on that revision under this AD.

Insurers and lessors may be indirectly affected because the AD imposes a compliance obligation with operational consequences. If an aircraft subject to the AD is operated without meeting the inspection and corrective-action requirements, insurance coverage or lease covenants could be implicated, though the AD text itself does not address contractual consequences.

Finally, the AD affects fleet managers or owners keeping maintenance logs. The AD’s stated compliance timeline and pre-flight repair requirement mean that the mandated inspections and repairs become part of the aircraft’s airworthiness record. The AD identifies the hazard and the remedial documents (SB 28-3967 and FAA AD 2009-15-01) which must be referenced in maintenance records to demonstrate compliance.

All of these affected parties and the mechanisms by which they are affected are set out or implied by the AD’s Applicability, Requirements, Compliance and AMOC clauses, and by the Background hazard description in the AD text.

Duties imposed by the AD are precise and limited to what the text prescribes. Duty 1: perform an inspection “in accordance with Hawker Beechcraft Mandatory Service Bulletin SB 28-3967, dated June 2009,” specifically to check for (a) “Improper installation of the P60 / J60 electrical connector, associated wiring and fuel line,” and (b) “Chafing damage of the electrical wiring and fuel line.” Duty 2: if the inspection reveals any of the specified discrepancies, carry out the corrective actions “in accordance with SB28-3967.” The corrective actions are described in the AD as: correct the P60 / J60 installation where improper, and “replace or repair the damaged parts” where chafing damage is present. Timing duties: the inspection must be completed “Within 10 hours time-in-service ... or 6 calendar months ... whichever occurs first,” and any required corrective action must be accomplished “Before further flight after the Requirement inspection.”

The AD also sets a duty regarding the source of the inspection and repair instructions: the prescribed standard is the Hawker Beechcraft Mandatory Service Bulletin SB 28-3967 dated June 2009 (or later SB revisions only if FAA AMOC-approved to FAA AD 2009-15-01). Practically, that means operators must obtain and follow that SB’s procedures for the inspection and any corrective work.

Rights and allowances in the AD are narrow. The principal right the AD grants is a route to compliance via FAA-approved later revisions of the service bulletin. The AD explicitly states that “Later revisions of the above SB, approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2009-15-01 are considered acceptable for compliance with the equivalent Requirements of this Directive.” That creates a right to rely on a later SB revision only if it has FAA AMOC approval to the FAA AD referenced. The AD does not state any other alternative compliance pathways, waivers, or appeals process within the text.

The AD confers no express entitlement to compensation, cost-sharing, or delay relief. It does not allocate funds nor identify any administrative remedy for operators unable to comply. The AD is prescriptive: inspection and corrective action are required within the prescribed timeframes, and corrective work must be carried out prior to further flight if discrepancies are found. The only conditional flexibility offered is acceptance of FAA-approved AMOCs for later SB revisions as described above.

The AD also does not recite specific record-keeping form or wording to confirm compliance; it references the SB for technical compliance and gives explicit timing constraints. Therefore the operator’s de facto duties include obtaining the SB, completing the inspection within the deadline, performing any repairs specified by SB 28-3967, and ensuring the aircraft is not flown until those repairs are done. Those duties are established by the Requirements and Compliance clauses of the AD.

Each duty and allowance above is stated in the AD text: the Requirements clause specifying inspection and corrective actions; the Compliance clause setting the 10 hours TIS or 6 months timing and the “Before further flight” rule for repairs; and the AMOC clause permitting FAA-approved later SB revisions as acceptable.

The AD text itself does not set out monetary penalties, criminal sanctions, or an enforcement procedure. The document records the mandatory actions, the effective date, and who issued the AD, but it does not include an express enforcement or penalty schedule within the text provided. The AD’s Compliance section sets mandatory timeframes: the inspection must occur “Within 10 hours time-in-service ... or 6 calendar months ... whichever occurs first,” and corrective actions “must” be carried out “Before further flight after the Requirement inspection.” The AD also states it “becomes effective on 27 July 2009.” Beyond those operative requirements and the effective date, the AD contains no text within this document describing the regulatory enforcement mechanism or penalties for non-compliance.

The absence of explicit penalty language in the AD does not mean there are no regulatory consequences under the broader statutory or regulatory framework, but the AD itself does not describe those consequences. The AD is signed by James Coyne, Delegate of the Civil Aviation Safety Authority, and carries an effective date and directive number, which signals it is an official CASA instrument. The AD’s language , setting mandatory inspections and pre-flight repair requirements , places definite obligations on affected operators and maintenance entities; non-compliance would, in practice, carry regulatory risk in the context of oversight regimes administered by aviation authorities. However, any precise statement about civil penalties, certificate action, or criminal liability would go beyond what this AD text records and is not stated in the document itself.

For practitioners advising affected parties, the AD’s enforcement-relevant facts to note from the document are: it prescribes mandatory inspections and mandatory corrective work within set timeframes; it becomes effective on a fixed date (27 July 2009); and it references external documents (SB 28-3967 and FAA AD 2009-15-01) which define technical compliance. The AD does not specify the consequences for failing to meet those obligations or who will assess compliance; those details are not contained in this text.

All of the above about penalties and enforcement, including the observation of silence on penalties, is drawn from the AD text as provided.

The AD explicitly cross-references and incorporates external aviation safety instruments rather than other statutes. The principal external document is Hawker Beechcraft Mandatory Service Bulletin SB 28-3967, dated June 2009. The AD requires inspections and corrective actions “in accordance with” that SB. The AD also cross-references and accepts a particular FAA process: “Later revisions of the above SB, approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2009-15-01 are considered acceptable for compliance with the equivalent Requirements of this Directive.” In other words, the AD establishes a specific point of interaction: it will accept FAA AMOC approvals made against FAA AD 2009-15-01 as fulfilling this AD’s equivalence test for later SB revisions.

The AD also explicitly “refers” to FAA AD 2009-15-01 Amdt 39-15964 (the text says “Note: FAA AD 2009-15-01 Amdt 39-15964 refers”). That indicates the AD’s remedial design is aligned to a matching FAA action, and that operators who follow the FAA AD’s AMOC processes can achieve acceptance under this AD for later SB revisions where the FAA has granted an AMOC.

The AD does not, within this text, expressly reference Australian statutes, regulations, or specific CASA enforcement provisions. It does, however, carry the signature of a CASA Delegate (James Coyne), which identifies CASA as the issuing regulator. The AD’s wording therefore creates a vertical relationship: CASA mandates action, but CASA also recognises FAA AMOC approvals to FAA AD 2009-15-01 as satisfying the AD’s equivalence requirement for later SB revisions of SB 28-3967. This is a targeted cross-authority recognition rather than a general statement of legal supremacy, and it is confined to “later revisions of the above SB” that have FAA AMOC approval to the referenced FAA AD.

The AD does not reference certification, registry, customs, insurance or other non-airworthiness statutes. It does not provide for delegated approvals apart from the FAA AMOC clause. Therefore, from the text provided, the AD’s interactions with other law are restricted to technical and administrative recognition of FAA actions and to the incorporation of the manufacturer’s service bulletin as the technical standard.

All of the interaction points set out above , the incorporation of SB 28-3967, the FAA AMOC acceptance clause, and the note referring to FAA AD 2009-15-01 , are explicit in the AD text.

The provided document contains limited concrete information about amendment history. The header lists the AD identifier “AD/BEECH 36/53” and repeats “9/2009 DM,” which indicates the AD’s issuance in 2009 and a docket or document marker DM 9/2009; however, the text contains no record of prior or subsequent amendments to this particular AD. The AD itself specifies the service bulletin by edition: “Hawker Beechcraft Mandatory Service Bulletin SB 28-3967, dated June 2009.” The AD also permits the use of “Later revisions of the above SB” but only where those revisions have FAA AMOC approval to FAA AD 2009-15-01. The AD does not record any later revision approvals or amendments to the AD itself.

The document includes an effective date (27 July 2009) and a signature date (17 July 2009) from James Coyne, Delegate of the Civil Aviation Safety Authority. Those dates establish the AD’s entry into force but do not indicate any changes made after issue. The AD contains a “Note: FAA AD 2009-15-01 Amdt 39-15964 refers,” but the AD text does not say whether subsequent revisions to the FAA AD or to SB 28-3967 occurred after this AD was signed, nor does it list any formal amendments to the AD number AD/BEECH 36/53 itself.

Therefore, based solely on the document provided, there is no recorded internal amendment history listed in the AD beyond the initial issuance and its stated acceptance of FAA AMOCs for later SB revisions. The AD’s own operative clauses permit later SB revisions to be used for compliance conditional on FAA AMOC approval to the FAA AD referenced, but the AD does not itself record any amendment, supersession, re-issuance, or withdrawal within the text presented here.

All of the above statements about amendment history are drawn strictly from the content and omissions of the supplied AD text.

The supplied AD document contains no litigation history. It does not reference any court decisions, administrative appeals, adjudications, or disputes related to this AD. The AD is a single regulatory instrument describing applicability, requirements and compliance timing; it contains no record of challenges, judicial review, enforcement proceedings, or case law citations.

Because the AD text does not include any litigation material, there are no named cases, no judgment dates, and no administrative tribunal decisions to summarise from the provided source. Any statement about litigation, precedent, or contested enforcement arising from this AD would require external sources beyond the AD text supplied.

Accordingly, the litigation history section for this AD, as drawn exclusively from the provided document, is a statement of absence: the document supplies no litigation history, no references to legal challenges, and no records of adjudication in relation to AD/BEECH 36/53.

The AD contains several operational and compliance pitfalls that arise directly from its language and structure.

1. Narrow applicability and uneven serial-number ranges. The Applicability list names specific serial numbers and ranges (for example, E-3630, E-3636 through E-3817, E-3819 through E-3834, etc.). The list is non-contiguous and specific. Operators must verify exact serial numbers against the AD’s list. Missing or misreading a serial number (for example confusing E-3635 with the adjacent range) could lead to inadvertent non-compliance or unnecessary work. The AD itself provides the precise serial-number list in its Applicability clause.

2. Tight dual-trigger compliance window. The inspection must be accomplished “Within 10 hours time-in-service (TIS) after 27 July 2009 ... or 6 calendar months after 27 July 2009, whichever occurs first.” For high-utilisation aeroplanes the 10 TIS threshold will be reached quickly; for low-utilisation aeroplanes the six-month calendar cap becomes binding. Operators must track both flight hours and the calendar deadline. Failure to perform the inspection within that dual-limited window would run contrary to the AD’s Compliance clause.

3. Absolute pre-flight repair requirement if defects are found. The AD mandates that if discrepancies are found during the inspection, corrective actions “must” be accomplished “Before further flight.” Practically, that means an aircraft found to have improper installation or chafed wiring/fuel line cannot legally or permissibly fly until the repairs or replacement are completed in accordance with SB 28-3967. This creates immediate grounding risk until appropriate parts and competent maintenance personnel are available.

4. Technical dependency on an external service bulletin. The AD delegates substantive technical procedures to Hawker Beechcraft Mandatory Service Bulletin SB 28-3967, dated June 2009. The AD does not include the SB text, so operators must obtain the SB and ensure they follow its inspection and repair procedures. Misalignment between the SB and actual maintenance performed creates compliance risk. The AD’s AMOC clause only accepts later SB revisions that are FAA-AMOC-approved to FAA AD 2009-15-01, so not every later SB edition will be acceptable unless it has the specific FAA AMOC approval.

5. Limited pathway for alternative compliance. The AD permits only one explicit alternative compliance path: later SB revisions are acceptable only when “approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2009-15-01.” There is no express CASA AMOC clause or alternative approval mechanism in the AD text. Operators seeking to rely on non-SB procedures or local engineering solutions will need to consider whether the AD text allows it; the AD itself limits acceptance to FAA AMOC approvals for later SB revisions.

6. Cross-jurisdiction reliance requirement. The AD’s allowance for later SB revisions depends on FAA AMOC approval; that imports another authority’s approval standard into compliance. Operators must verify that the FAA has granted an AMOC to FAA AD 2009-15-01 for the particular SB revision before relying on that revision under this AD. The AD text states that such FAA AMOC approval will be “considered acceptable for compliance with the equivalent Requirements of this Directive,” which makes FAA AMOC the yardstick for acceptable later SB changes.

7. Hazards described point to immediate safety consequences. The Background warns that chafing “could lead to fuel leaking into the cockpit and fire in the cockpit if wiring arcs through the fuel line.” That language implies severe consequence if chafing is present, which is why the AD requires immediate pre-flight repairs where defects are found. The severity described in the Background increases the operational consequence of finding defects and the urgency of obtaining parts/repairs.

8. The AD text does not specify enforcement mechanics or a penalty schedule. The AD is prescriptive and mandates actions but does not set out enforcement steps or penalties within this document. Operators cannot rely on the AD text here to learn how non-compliance will be enforced; that information, if required, must be sought in the broader regulatory framework administered by CASA.

All of the above gotchas follow directly from the AD’s Applicability, Requirements, Compliance, AMOC clause, and Background paragraphs as provided in the document.

The AD itself prescribes the mandatory steps; compliance requires following them precisely and documenting the work. Use the AD text as a procedural checklist and follow the referenced service bulletin for technical execution. The AD’s required steps, read from the document, are as follows.

1. Confirm applicability. Verify the aeroplane’s model and serial number against the AD’s Applicability list: Model G36 aeroplanes, serial numbers E-3630, E-3636 through E-3817, E-3819 through E-3834, E-3836 through E-3887, E-3889 through E-3896, E-3898 and E-3899. Only aircraft with those exact serial numbers are covered by this AD as written.

2. Obtain the service bulletin. Acquire Hawker Beechcraft Mandatory Service Bulletin SB 28-3967, dated June 2009. The AD requires inspections “in accordance with” that SB, and prescribes corrective actions “in accordance with SB28-3967.” Follow the SB’s detailed inspection procedures, torque/clearance specs, part numbers and repair instructions rather than improvising.

3. Schedule and perform the inspection within the AD’s timeframe. The AD requires the inspection “Within 10 hours time-in-service (TIS) after 27 July 2009 ... or 6 calendar months after 27 July 2009, whichever occurs first.” Ensure maintenance planning accounts for both the flight-hour trigger and the calendar trigger. Execute the inspection in accordance with the SB, specifically checking for (a) improper installation of the P60 / J60 electrical connector and associated wiring and fuel line, and (b) chafing damage to the wiring or fuel line.

4. If discrepancies are found, carry out corrective actions immediately and before flight. The AD requires that if the inspection identifies improper installation the operator must “correct the installation of the P60 / J60 electrical connector, associated wiring and fuel line,” and if chafing damage is present, “replace or repair the damaged parts.” The AD specifies that corrective actions are to be accomplished “in accordance with SB28-3967.” Because the AD requires corrections “Before further flight after the Requirement inspection,” the aircraft must be grounded pending completion of the SB-compliant repairs or replacements.

5. For operators wishing to use a later revision of the SB, verify FAA AMOC approval. The AD accepts “Later revisions of the above SB, approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2009-15-01” as acceptable for compliance. If you intend to rely on a later SB edition, confirm that the FAA has approved that later revision as an AMOC to FAA AD 2009-15-01. Maintain documentation of the FAA AMOC approval to justify using the later revision for compliance under this AD.

6. Document the inspection and any corrective actions in maintenance records. The AD itself does not stipulate record-keeping language, but because it is a mandatory airworthiness instruction with an explicit effective date and compliance timetable, record entries should reference: the AD identifier (AD/BEECH 36/53), the SB used (SB 28-3967, dated June 2009 or later FAA-AMOC-approved revision), dates and times of inspection and repairs, nature of discrepancies found, parts replaced or repairs done, and sign-off by certifying maintenance personnel. Those entries will be the evidence of compliance with the AD’s Requirements and Compliance clauses.

7. Consider operational planning contingencies. Because corrective actions are required before further flight if defects are present, plan for potential grounding: ensure access to parts, qualified maintenance staff, and any special tooling the SB specifies. The AD’s Background highlights the severity of the hazard , fuel leaking into the cockpit and possible fire , which justifies immediate and thorough corrective work where defects exist.

8. Keep a copy of the AD on file and monitor any FAA AMOC updates for later SB revisions. The AD contains a note referencing FAA AD 2009-15-01 Amdt 39-15964. If later SB revisions are released and FAA AMOCs are granted, document the FAA AMOC approval as the AD expressly conditions acceptability of later SB revisions upon that approval.

All of the steps above are derived from the AD’s Applicability, Requirements, Compliance, AMOC clause, and Background paragraphs. Operators should follow the SB’s technical content for the detailed inspection and repair methodology because the AD mandates SB compliance rather than prescribing the detailed technical steps within the AD text itself.