AD/PA-36/20 Amdt 2 - Engine Mount Attach Brackets - Inspection and Modification

The instrument directly affects registered operators, owners, maintenance organisations and maintenance release authorities for Model PA‑36‑285 aeroplanes whose serial numbers fall within 36‑736001 to 36‑7660135 and that do not already incorporate Piper Engine Mount Attachment Modification Kit No. 763877 (see "Applicability"). Those parties are the ones who must perform, arrange or ensure the specified inspections and, if defects are discovered, implement the Kit or an equivalent prior to further flight.

Stakeholders and roles implied by the text:

• Owner/operator: The owner/operator is the economic actor who will bear inspection and modification costs, and who must ensure the aircraft is not dispatched for flight contrary to the AD if cracks are present. The requirement to install the Kit "prior to further flight" places a direct operational constraint on the owner/operator.

• Maintenance organisations and certifying staff: The inspections are required "at each scheduled inspection for issue of a maintenance release" (see "Compliance"), which places a recurring duty on maintenance providers who conduct scheduled inspections and who issue maintenance releases. During installation of the Kit, an inspection of the forward side of the gussets is also required, again implicating maintenance personnel and certifying engineers.

• Supply chain for parts and kits: The corrective requirement names a specific manufacturer kit (Piper Engine Mount Attachment Modification Kit No. 763877) or an equivalent. Suppliers, parts providers and any alternative modification designers are relevant because operators may procure the Kit or seek an equivalent approved modification.

• Regulatory authority: The AD is issued by the Civil Aviation Safety Authority (CASA), via its delegate (David Punshon), and is effective 12 March 2009. The regulator sets the legal requirement and identifies the related USA AD and the relevant service bulletin; the AD is the instrument by which CASA directs compliance.

• Excluded parties: Aircraft that already incorporate Piper Kit No. 763877 are expressly excluded from the applicability, and therefore are not required under this AD to carry out the specified inspections or modification (see "Applicability").

Indirectly affected parties include insurers (policy conditions may reference regulatory compliance), operations reliant on the affected aircraft (agricultural operators using Pawnee Braves), and inspection equipment providers (dye check, fluorescent penetrant supplies and operators).

The text does not identify any other categories of persons (for example, third‑party maintenance auditors or overseas regulators) as subject to obligations under the AD beyond those implied above. It also does not specify any exemptions other than the stated kit exclusion or provide an approval process for "equivalent" measures; the word "equivalent" is used but the AD does not set out the approval mechanism for equivalence.

The AD imposes concrete duties and references particular procedural rights or options only to the limited extent the text describes.

Primary duties

• Inspect aft‑side welds: Operators must inspect welds for cracks on the aft side of the gussets on the fuselage where the engine mount is attached, as shown in Piper Service Bulletin No. 615 (see "Requirement").

• Inspection method: The inspection must use dye check or fluorescent penetrant inspection procedures or an equivalent method (see "Requirement"). The choice of those two non‑destructive test techniques is mandated unless an "equivalent" is applied.

• Remedial action if cracks found: If cracks are found, the operator must install Piper Engine Mount Attachment Modification Kit No. 763877 or an equivalent prior to further flight (see "Requirement"). The AD makes the installation a condition precedent to further flight.

• Inspect forward side during kit installation: When installing the Kit, the installer must also inspect the welds for cracks on the forward side of the gussets, as shown in Piper SB No. 615, using the same inspection procedures (see "Requirement").

• Compliance timing: Inspections are to be performed "at each scheduled inspection for issue of a maintenance release" (see "Compliance"). Thus the inspection obligation recurs at the scheduled maintenance events that produce a maintenance release.

Rights, options and latent discretion in the text

• Exclusion for modified aircraft: Aircraft already incorporating Piper Kit No. 763877 are excluded from the AD’s applicability (see "Applicability"). This operates as a de facto right not to follow the AD’s inspection/modification regimen if the aircraft already has the specified kit.

• Use of an "equivalent": The AD allows substitution of "equivalent" inspection procedures and an "equivalent" modification in place of the named items (see "Requirement"). The AD does not define "equivalent" or set out the approval pathway, but it creates scope for operators and maintenance organisations to propose alternative inspection techniques or modification designs that achieve the same objective.

• Reliance on Piper Service Bulletin No. 615: The AD directs inspectors to the service bulletin for visual/locational guidance. The service bulletin is used as the illustrative authority for locating the gusset welds requiring inspection.

• Relationship to previous amendments: The AD states that "Compliance with Amendment 1 of this AD constitutes compliance with this Amendment" (see "Compliance"). That phrasing allows operators who complied with Amendment 1 to consider themselves compliant with Amendment 2 insofar as the requirements overlap.

The AD does not set out an approval or appeal process for contesting equivalence or relief, nor does it enumerate documentation required to demonstrate compliance beyond the linkage to the maintenance release. The AD also does not itself provide procedural instructions for certifying an "equivalent" modification, leaving that process to the regulator or maintenance certification practice outside the text.

The text of the AD itself does not specify monetary penalties, criminal sanctions or a step‑by‑step enforcement regime. What the instrument does establish in the text is a regulatory requirement issued by the Civil Aviation Safety Authority (via its delegate) that prescribes mandatory inspections and a required corrective modification where defects exist, and it states an effective date, 12 March 2009 (see opening paragraphs and "Compliance"). The directive names the responsible delegate (David Punshon) and identifies the legal instrument as an AD, but it omits operational enforcement language such as infringement notices, fines, suspension powers or explicit consequences for non‑compliance in the text supplied.

From the practical perspective set out in the AD:

• The AD makes certain maintenance and modification acts mandatory for the aircraft to be considered airworthy in this respect, because it requires the Kit to be installed "prior to further flight" if cracks are found (see "Requirement"). That creates an operational constraint: aircraft with identified cracked welds must not be flown until the remedial work is completed.

• The compliance schedule links inspections to the issue of a maintenance release (see "Compliance"). Maintenance release procedures and checks are the customary mechanism by which the airworthiness state is recorded; failure to comply with the AD would therefore manifest in the maintenance release process and be visible to operators and regulators through maintenance records and certification practices.

Because the AD text does not enumerate enforcement mechanisms, readers must not infer specific penalty amounts or administrative procedures from this instrument alone. The AD does reference related documents (Piper SB No. 615; USA AD 79‑12‑09) and records its own amendment history, but it leaves unspecified any formal penalty schedule or the procedural pathway that CASA would follow to enforce non‑compliance. Any enforcement consequences, administrative notices or prosecutions must therefore be sought in the wider regulatory framework or in separate CASA enforcement instruments not included in this text.

The AD explicitly engages with other aviation‑safety instruments and with manufacturer guidance; the text itself mentions two specific cross‑references and records its relationship to previous ADs. Based solely on the AD text:

• Cross‑reference to a USA AD: The instrument "identifies USA AD 79‑12‑09 (amdt 39‑3494)" as related (see "Requirement" and the Note). The AD also restricts the serial number applicability "to the serial number range specified in USA AD 79‑12‑09" (see Background). That creates a direct substantive link between the Australian AD and the earlier US directive; the Australian AD aligns its applicability with the U.S. AD’s serial range.

• Reliance on a manufacturer service bulletin: The AD requires portions of the inspection to be "as shown in Piper SB No. 615" (see "Requirement"). The service bulletin is therefore incorporated by reference for illustrative and locational detail. The AD does not republish the service bulletin but mandates actions that are to be performed according to its illustrations and locations.

• Relationship to prior Australian AD amendments: The Background paragraph records that the original AD issued in 1978 specified the same applicability and requirements as Piper SB No. 615, and that Amendment 1 (1983) extended applicability to all PA‑36 models in response to reports of cracked engine mount brackets outside the SB serial number applicability (see "Background"). Amendment 2, the present instrument, reverses part of that broadening by excluding aircraft incorporating Kit No. 763877 and by restricting serial number applicability to that in the USA AD. The AD therefore modifies the previous AD regime and declares that compliance with Amendment 1 constitutes compliance with this Amendment (see "Compliance").

• Interaction with maintenance and certification processes: The AD ties inspection timing to each scheduled inspection that results in the issue of a maintenance release (see "Compliance"). That embeds the AD’s requirements into routine maintenance certification processes and therefore into the broader legal framework governing maintenance releases, airworthiness certifications and operational authorisations.

• "Equivalent" methods and modifications: The AD permits dye check or fluorescent penetrant inspection procedures, "or equivalent", and allows the Kit to be replaced by an "equivalent" modification (see "Requirement"). The AD does not lay out formal criteria for equivalence or the approval body, which implies that determining equivalence will rely on regulatory practice and possibly on CASA guidance or approval processes external to the text.

The AD does not purport to amend primary aviation statutes or to displace them; instead it operates as a regulatory instrument that sits within a body of airworthiness directives, interacts with a manufacturer service bulletin, and aligns its applicability with a U.S. AD. The precise legal effect of non‑compliance with this AD in terms of statutory penalties is not set out in the instrument itself and would depend on the broader aviation regulatory framework.

The AD text itself tracks a concise amendment history in the "Background" and opening paragraphs. The chronology and mechanical changes recorded in the instrument are:

• Original AD (1978): The original issue of this AD in 1978, according to the Background paragraph, "specified the same applicability and requirements as Piper SB No. 615." That establishes that the initial direction mirrored the manufacturer’s service bulletin for scope and action.

• Amendment 1 (1983): The Background paragraph notes that "Amendment 1 in 1983 extended the applicability to all PA‑36 in response to reports of cracked engine mount brackets outside the serial number applicability of Piper SB No. 615." Thus Amendment 1 broadened the class of affected aircraft beyond the serial‑number-restricted set in the service bulletin.

• Amendment 2 (this instrument) (2009): The present document is labelled "AD/PA‑36/20 Amendment 2" dated 3/2009 and becoming effective 12 March 2009. The AD records the mechanical changes effected by Amendment 2: it "excludes aircraft incorporating Piper Kit No. 763877; restricts serial number applicability to the serial number range specified in USA AD 79‑12‑09; identifies USA AD 79‑12‑09; and specifies compliance period in terms of issue of a maintenance release" (see Background and the explanatory paragraph following it). The AD also states that compliance with Amendment 1 constitutes compliance with this Amendment (see "Compliance").

• Note and cross‑reference: The Requirement paragraph includes a Note: "USA AD 79‑12‑09 (amdt 39‑3494) refers." This reiterates the link to the U.S. AD that sets the serial number range.

Mechanically, Amendment 2 narrows the net of affected aircraft relative to Amendment 1 by returning applicability to the serial range aligned with the USA AD and by excluding aircraft already incorporating the named modification Kit. It also formalises inspection timing as tied to scheduled inspections that issue maintenance releases, which is a change in the compliance rhythm compared with unspecified prior timing in earlier versions. The AD does not supply the full texts of prior amendments or the original 1978 text, but it records the direction of change: original alignment with the SB, broadening in 1983, and narrowing and clarification in 2009.

The document supplied contains no litigation history. It does not record any judicial or administrative proceedings, appeals, or disputes arising from the original AD, Amendment 1, or this Amendment 2. The text lists background facts about prior amendments and cross‑references to a USA AD and a Piper service bulletin, but it does not mention any court decisions, tribunal findings, or contested enforcement actions. Therefore, on the basis of the supplied instrument alone, there is no documented litigation history to report.

If parties require evidence of enforcement actions, judicial review, or appeals related to this AD, that information is not present in the AD text and would need to be obtained from separate CASA records, court files, or administrative archives not included here.

This AD contains several technical and procedural details that can cause compliance traps if misread or overlooked. The following points are grounded in the instrument’s text and identify specific practical pitfalls.

• Narrow serial‑number applicability with an exclusion: The applicability is confined to Model PA‑36‑285 serial numbers 36‑736001 to 36‑7660135, but aircraft incorporating Piper Kit No. 763877 are expressly excluded (see "Applicability"). Failure to check both serial number and modification status could lead to unnecessary inspections or missed obligations. Operators of aircraft outside the serial range or already modified may incorrectly assume they are affected, or conversely, operators may fail to realise their aircraft sits inside the range.

• Compliance timing tied to maintenance release: The inspections must be performed "at each scheduled inspection for issue of a maintenance release" (see "Compliance"). That is a maintenance‑event trigger, not a calendar or flight‑hour interval. If an operator’s maintenance scheduling practice does not equate scheduled inspections with maintenance releases in the expected way, inspections could be missed. Organisations that rely on different periodicities (for example, calendar checks or engine hours) need to map their routine to the "maintenance release" trigger.

• Equivalence left undefined: The AD permits "equivalent" inspection procedures and "equivalent" modifications (see "Requirement"). The AD does not define "equivalent" or explain how equivalence is approved. Operators and maintenance organisations seeking to rely on an equivalent method or modification will need to ensure they have an approved or otherwise acceptable equivalence pathway, or choose to apply the named procedures and Kit to avoid ambiguity.

• Requirement to inspect forward side during kit installation: The AD requires inspection of the forward side of the gussets "during installation of the Kit", as well as the aft side in routine inspections (see "Requirement"). If installers treat the kit installation as purely mechanical without inspecting the forward side, they will miss a specified duty.

• Link to Piper SB No. 615: The AD refers inspectors to Piper Service Bulletin No. 615 for locations ("as shown in Piper SB No. 615") (see "Requirement"). Not having that bulletin to hand, or misinterpreting its illustrations, could lead to incomplete inspections. The AD does not reproduce the figures, so the service bulletin must be consulted.

• Ambiguous phrase on compliance with Amendment 1: The AD states that "Compliance with Amendment 1 of this AD constitutes compliance with this Amendment" (see "Compliance"). That could be read to mean that any operator who complied with the broader Amendment 1 need take no further action for Amendment 2, but the present Amendment also narrows applicability and excludes aircraft with the Kit. Operators should verify their factual situation (serial number and modification status) rather than rely solely on prior compliance.

• Note referencing USA AD: The AD contains the Note "USA AD 79‑12‑09 (amdt 39‑3494) refers" (see "Requirement"). That USA AD is identified as relevant, but the AD does not reproduce its content. Operators who wish to rely on the serial‑number alignment or any other detail in the USA AD must review that instrument in addition to this AD.

• No penalties described: The AD contains no penalties section (see "Penalties and enforcement"). Parties seeking certainty about enforcement consequences must consult the broader legal framework; the AD standing alone does not spell out enforcement steps.

• Effective date and administrative repeats: The AD becomes effective 12 March 2009 (see "Compliance" opening line). The instrument also contains repetition in its header text (multiple repeats of the AD title and lines such as "3/2009"), which is purely administrative but could cause confusion when filing or referencing the AD.

Owners, maintainers and certifying staff should therefore perform a due diligence checklist: confirm serial number and Kit incorporation; obtain Piper SB No. 615; plan inspection timing around maintenance release events; specify test techniques (dye or fluorescent penetrant) or secure approval for equivalents; and ensure forward‑side inspection is completed during any Kit installation.

The AD sets out a concise, stepwise set of actions an operator or maintenance organisation must take. The following compliance checklist is a direct reading of the AD’s requirements and timing.

1. Establish applicability:

   • Confirm the aircraft is a Model PA‑36‑285.
   • Confirm the serial number is within 36‑736001 to 36‑7660135 (see "Applicability").
   • Confirm whether Piper Engine Mount Attachment Modification Kit No. 763877 is already incorporated. If the Kit is present, the aircraft is excluded from the AD’s applicability (see "Applicability").

2. Obtain the referenced material:

   • Acquire Piper Service Bulletin No. 615 and consult the illustrations for the exact locations of the gusset welds to be inspected, because the AD requires inspection "as shown in Piper SB No. 615" (see "Requirement").

3. Inspection procedure:

   • At each scheduled inspection that results in the issue of a maintenance release, inspect the welds for cracks on the aft side of the fuselage gussets where the engine mount attaches (see "Compliance" and "Requirement").
   • Perform the inspection using dye check or fluorescent penetrant inspection procedures, or an equivalent non‑destructive inspection technique (see "Requirement").
   • Record the inspection in maintenance logs so the inspection aligns with the maintenance release issuance.

4. If cracks are found:

   • Do not permit further flight. The AD requires that if cracks are found, the operator must install Piper Engine Mount Attachment Modification Kit No. 763877 or an equivalent "prior to further flight" (see "Requirement").
   • Arrange for procurement and installation of the Kit or an approved equivalent. Ensure the supplier and installer can document the modification as required for airworthiness records.

5. During Kit installation:

   • While installing the Kit, inspect the welds for cracks on the forward side of the gussets, again as shown in Piper SB No. 615, using dye check or fluorescent penetrant or equivalent techniques (see "Requirement").
   • Complete and record any remedial work resulting from forward‑side inspection.

6. Recordkeeping and certification:

   • Maintain maintenance records demonstrating inspection at scheduled maintenance releases, any crack findings, and any Kit installations or equivalent modifications.
   • Ensure that the maintenance release documents accurately reflect the inspection and any remedial action so airworthiness certification processes capture compliance with the AD.

7. Equivalents and approvals:

   • If you intend to use an "equivalent" inspection method or an "equivalent" modification in place of the techniques or Kit named in the AD, secure the necessary approvals or demonstrate equivalence pursuant to applicable regulatory practice. The AD permits "equivalent" methods but does not define the approval pathway (see "Requirement"); prudent practice is to obtain documented regulatory or approved engineering authority acceptance before relying on an equivalent.

8. Liaise with regulator and supplier as needed:

   • Given the AD’s cross‑reference to USA AD 79‑12‑09 and the use of a manufacturer service bulletin, coordinate with CASA, Piper, or approved maintenance organisations to ensure the Kit’s installation conforms to the required design and that the inspections use accepted non‑destructive techniques.

9. Operational planning:

   • Plan maintenance schedules to align inspections with scheduled maintenance releases. Consider the operational impact of potential Kit installation, which must be completed prior to further flight if cracks are found.

10. Verify final compliance status:

• If Amendment 1 was previously complied with, understand that the AD states "Compliance with Amendment 1 of this AD constitutes compliance with this Amendment" (see "Compliance"); nonetheless, verify current serial number, modification status, and that the prior compliance covers the current requirements as written.

Costs and resourcing implied by the AD: perform dye check or fluorescent penetrant inspections (requires consumables and qualified personnel), and, if defects are discovered, install a manufacturer Kit or an equivalent modification (requires parts, labour and possible temporary grounding). The AD does not provide waivers, alternative intervals, or a compliance relief process within its text, so operators should treat it as a mandatory regulatory duty and document compliance in maintenance records tied to maintenance releases.