AD/PA-31/96 Amdt 1 - Engine Baffle Seals

This AD rests on several interlocking regulatory and technical concepts. The primary technical concept is the function and integrity of engine baffle seals. The AD identifies an unsafe condition: ill-fitting and blown-back baffle seals that have been reported as causing engine overheating. The AD therefore targets the baffle seals as the locus of corrective action and delegates the procedural detail to a manufacturer service bulletin, Piper Service Bulletin No 693. The AD separates procedure into Instructions A (inspection) and Instructions B (reinforcement), making inspection the default recurring control and reinforcement an optional, terminating corrective modification.

The principal regulatory concept is the AD as a delegated instrument under subregulation 39.1(1) of the Civil Aviation Regulations 1998 (CAR 1998). The AD states it revokes the earlier AD/PA-31/96 and issues this AD under that subregulation; it is therefore an exercise of the CASA delegate’s corrective power to require action deemed necessary to correct an unsafe condition. The AD sets the circumstances and timing for the required action (Inspection within 55 hours TIS and thereafter not to exceed 55 hours TIS, with reinforcement optional), and it specifies that actions are to be performed in accordance with the instructions set out in the Requirement section. The AD also signals that a reinforcement procedure can be approved by a CASA-authorised person under CAR 35, introducing a regulatory approval pathway for alternatives.

Another key concept is the use of a terminating action. Requirement 2 is described as providing "terminating action for this inspection." That makes the reinforcement an explicit trade-off mechanism: carry out the one-time reinforcement and the recurring inspection obligation is relieved. This creates a choice for operators between ongoing operational burden (regular inspections) and a one-off modification that may have upfront costs, availability and approval considerations.

A further concept is reliance on external normative material. The AD does not reproduce the inspection or reinforcement steps; instead it requires compliance "in accordance with Instructions A/B of Piper Service Bulletin No 693." Thus the efficacy of the AD depends on that Service Bulletin’s contents and on operators’ access to and implementation of those instructions. The AD also references FAA Airworthiness Directive 93-23-13, showing cross-acceptance or alignment with an FAA determination of the same unsafe condition; the AD states it "reflects the issue" of that FAA AD.

Finally, the AD demonstrates interplay between operational discretion and regulatory command. The inspection schedule is a mandatory, prescriptive timing requirement. The reinforcement is optional (at the operator’s discretion) but when performed as specified, it changes the operator’s ongoing regulatory obligations. Approval mechanisms under CAR 35 introduce discretion for CASA-authorised personnel to accept alternate reinforcement actions.

Taken together, the main concepts are: a manufacturer-prescribed inspection routine made mandatory by regulator; an optional terminating modification; procedural reliance on an external service bulletin; and regulatory authority and approval routed through CAR 1998 subreg 39.1(1) and CAR 35 approvals as noted in the AD text.

The AD explicitly affects operators and owners of Piper PA-31, PA31-325, PA31-300 Navajo and PA31-350 Chieftain aircraft whose serial numbers fall within the range identified in Piper Service Bulletin No 693. The Applicability section ties affected aircraft to serial numbers as detailed in that Service Bulletin, so the set of affected aircraft is not merely model-based but serial-number-specific. Aircraft not listed in the Service Bulletin are not named in the applicability paragraph and therefore are not within the AD’s scope as stated.

Primary parties who bear obligations and costs are aircraft operators and maintainers for the listed aircraft. Requirement 1 requires inspections to be performed "in accordance with Instructions A of Piper Service Bulletin No 693," which imposes a procedural and scheduling obligation on operators to implement those instructions and record compliance in maintenance logs as applicable under standard practice. The Compliance section prescribes timing: an initial inspection within 55 hours time in service and thereafter at intervals not to exceed 55 hours time in service, so operators must schedule maintenance accordingly and ensure aircraft are available for the inspections.

Secondary parties include maintenance organisations, licensed engineers and approved maintenance organisations who will carry out the inspections and any reinforcement. The AD does not itself specify who must perform the actions, but the requirement to follow the service bulletin instructions creates demand for persons competent to implement Instructions A and B, or to follow an approved alternative under CAR 35.

CASA and its delegate are decision-makers in the regulatory chain. The AD was issued by a CASA delegate under subregulation 39.1(1) of CAR 1998. CASA-authorised persons under CAR 35 are empowered to approve reinforcement procedures as an alternative to Instructions B of the Service Bulletin; thus CASA-authorised approvers will be involved where operators seek non-standard reinforcement approvals.

Owners and financiers of affected aircraft bear indirect economic impacts. Inspections and possible reinforcement generate maintenance expenditure that owners and charter operators must fund, and scheduled downtime that affects utilisation and revenue. Where reinforcement is chosen, owners must weigh a one-off cost and possible parts lead times against the ongoing labour and downtime costs of recurring inspections.

Insurance underwriters and lessors may also be affected practically, because AD compliance is a standard condition for operation and may be required by lease or insurance conditions, although the AD text itself does not specify contractual consequences. Finally, the AD references FAA AD 93-23-13; operators engaged in international operations or aircraft registered in other jurisdictions might face parallel obligations under foreign authorities, so internationally active operators should take note of the cross-reference.

In sum, the AD directly alters maintenance obligations for listed PA-31 series aircraft identified by serial number in Piper Service Bulletin No 693. Operators, maintainers and CASA-authorised personnel are the primary actors who decide and pay for inspections or reinforcement, and owners and financiers bear the economic consequences of those choices.

The AD creates specific duties for operators of the affected aircraft and identifies procedural rights regarding approved alternatives. The core duties are found in the Requirement and Compliance sections.

Duty to inspect: Operators must inspect engine baffle seals "in accordance with Instructions A of Piper Service Bulletin No 693" as Requirement 1 prescribes. The Compliance section fixes the inspection timing: perform an initial inspection within 55 hours time in service and thereafter at intervals not to exceed 55 hours time in service. These requirements together constitute a mandatory, recurring obligation to inspect at those intervals.

Duty to reinforce where chosen: Requirement 2 requires reinforcement "in accordance with Instructions B of Piper Service Bulletin No 693 or as approved by a person authorised by CASA (CAR 35)." That means if an operator chooses to perform the reinforcement, it must be done according to the manufacturer instructions or an alternative approved by a CASA-authorised person under CAR 35. The AD does not mandate that reinforcement be performed, it makes it available as an option.

Right to elect reinforcement: The AD expressly states "Reinforcement: At the operator’s discretion." That is a regulatory right to choose between continuing routine inspections and performing a one-time reinforcement. The AD also stipulates that the reinforcement "provides terminating action for this inspection." Practically, an operator may choose the reinforcement pathway to remove the ongoing inspection duty specified in Requirement 1, but must do so in the manner prescribed or approved.

Right to seek CASA-authorised approval: Requirement 2 embeds a right to obtain regulatory approval for alternative reinforcement procedures from a person authorised by CASA under CAR 35. That creates a procedural pathway for operators or approved maintenance organisations to propose and have accepted alternate technical means of compliance, subject to CASA authorisation.

Duty to follow the Service Bulletin: The AD directs compliance in accordance with the instructions set out in the Requirement section; both inspection and reinforcement are expressly linked to Instructions A and B of Piper Service Bulletin No 693. Operators therefore are obliged to obtain and implement the Service Bulletin instructions as part of compliance.

Duty to observe applicability: The Applicability paragraph confines obligations to aircraft specified by serial number in the Service Bulletin. Operators must therefore check serial-number applicability against the Service Bulletin to determine whether their aircraft are within scope.

Regulatory duty origin and revocation of prior directive: The AD states it revokes AD/PA-31/96 and issues this AD under subregulation 39.1(1) of CAR 1998. That establishes the legal provenance of the duties and signals that the previous AD has been superseded.

Administrative duty to comply on schedule: The Compliance section makes the timing mandatory (effective 18 April 2002, inspection within 55 hours and thereafter within that interval), so operators have a scheduling duty to ensure inspections occur within the stipulated time window.

The AD does not set out rights to compensation, appeal procedures or penalty provisions within its text. It does, however, create an approval right under CAR 35 for CASA-authorised persons to accept alternative reinforcement procedures. Operators have the practical right to choose not to carry out reinforcement, but doing so leaves them subject to recurring inspection obligations. The AD’s structure therefore creates a specific compliance duty, an optional terminating modification, and an approval route for alternate technical solutions through CASA authorisation.

The AD identifies its legal basis as an instrument issued under subregulation 39.1(1) of the Civil Aviation Regulations 1998 (CAR 1998) and indicates it is an action the CASA delegate "considers necessary to correct the unsafe condition." The AD sets mandatory requirements and compliance timing for inspections and supplies an optional reinforcement pathway that alters ongoing obligations. The AD text itself does not specify civil or criminal penalties or the enforcement mechanisms that will be used for non-compliance. The AD does, however, provide the legal grounding in CAR 1998 for CASA to require action.

Because the AD is issued under CAR 1998, enforcement and penalty provisions that apply to failure to comply with a CAR-based requirement are a matter of the broader regulatory framework. The AD references CAR subregulation 39.1(1) as the source of authority and CAR 35 as the basis for authorising alternative reinforcement procedures. The AD does not reproduce the content of those CAR provisions and does not include discrete penalty amounts, remedial enforcement orders or administrative sanction processes within its text.

Practically, the AD imposes mandatory maintenance and inspection duties; failure to undertake the inspection at the prescribed intervals or to implement the reinforcement where it has been chosen would mean an operator has not complied with the AD’s requirements. The AD also notes that the delegate revokes an earlier AD and issues this AD, so the AD replaces prior regulatory direction and becomes the operative regulatory requirement for affected aircraft.

The document records the effective date and notification steps: it became effective 18 April 2002, was signed on 10 March 2002, and was notified in the Commonwealth of Australia Gazette on 27 March 2002. Those administrative steps establish public notice of the AD’s requirements.

Because the AD text does not specify penalties, readers should consult the Civil Aviation Regulations 1998 and relevant CASA enforcement policies for the applicable enforcement powers and penalty regimes that attach to non-compliance with CAR-derived ADs. The AD itself signals that non-compliance would be a failure to follow a regulatory direction issued under CAR 1998, but the AD does not set out the sanctions. Where an operator seeks clarification about enforcement or the consequences of non-compliance, they will need to refer to CAR 1998 provisions and CASA enforcement guidance, or seek specific advice from CASA or legal counsel.

Finally, the AD provides procedural discretion by allowing reinforcement "as approved by a person authorised by CASA (CAR 35)." That approval process gives CASA a degree of control over acceptable alternative actions; the AD thereby embeds an enforcement gate where non-standard reinforcement must be authorised to have the terminating effect. This approval gateway is a point at which CASA exercise of regulatory judgement can alter obligations, and failure to obtain such approval would mean the reinforcement does not satisfy the AD’s terminating-action condition.

The AD explicitly situates itself within the Civil Aviation regulatory structure by stating it is issued under subregulation 39.1(1) of the Civil Aviation Regulations 1998. It also references CAR 35 as the legal basis for authorisation of alternative reinforcement procedures. Those cross-references mean the AD operates as a CAR-derived instrument: its force rests on CAR 1998 powers, and it interacts with other CAR provisions that define authorisations, approvals, and enforcement.

The AD revokes the earlier AD/PA-31/96 and replaces it. That revocation and replacement show direct interaction with the previous AD regime for the same aircraft. The AD states the original issue of the Airworthiness Directive became effective on 31 December 1980; Amendment 1 revises the earlier directive’s terms. Operators must therefore regard AD/PA-31/96 Amdt 1 as the operative AD and not the original AD that it replaces.

The AD also references an FAA Airworthiness Directive, FAA AD 93-23-13, stating that this amendment "reflects the issue" of that FAA AD. This cross-reference indicates regulatory coordination across jurisdictions: the CASA delegate has taken into account the FAA directive when crafting the amendment, and operators who are subject to FAA jurisdiction or who operate internationally should be aware that the FAA issued a parallel AD. The AD does not create obligations under FAA law, but it signals equivalence or alignment with FAA regulatory findings.

Because the AD requires actions "in accordance with Instructions A/B of Piper Service Bulletin No 693," it interacts with manufacturer-issued technical publications. The AD incorporates those instructions by reference, so the Service Bulletin’s content becomes normative for compliance with the AD. That creates an interaction between statutory/regulatory obligations and private technical documentation. Operators must obtain and follow the Service Bulletin to meet the AD’s mandates.

The AD also creates an approval pathway under CAR 35 for alternative reinforcement methods: Requirement 2 allows reinforcement "or as approved by a person authorised by CASA (CAR 35)." That integrates the AD with the broader approval framework in CAR 1998 for alternate methods or materials, and gives CASA-authorised personnel the ability to accept deviations from the manufacturer’s Instructions B while still achieving the AD’s terminating effect.

The AD’s notification in the Commonwealth of Australia Gazette is an administrative interaction with statutory publication requirements for regulatory instruments. The AD records it was notified on 27 March 2002, meeting public-notice expectations.

The AD does not reference other statutes, common law duties, contractual obligations, insurance conditions or international treaties directly. Nevertheless, because ADs are mandatory regulatory instruments in the aviation safety framework, operators’ compliance obligations will interact practically with contractual obligations in leases or charter agreements, insurance conditions, and operational approvals. The AD itself, however, confines its legal cross-references to CAR 1998, CAR 35, FAA AD 93-23-13 and Piper Service Bulletin No 693.

The AD document contains a brief amendment history within its text. The original Airworthiness Directive AD/PA-31/96 was first issued and became effective on 31 December 1980. The present document is Amendment 1 to AD/PA-31/96, and it revokes the earlier AD/PA-31/96 and replaces it with the new requirements set out in this amendment.

This Amendment 1 was signed by Eugene Paul Holzapfel, a delegate of the Civil Aviation Safety Authority, on 10 March 2002. The document states the amendment becomes effective on 18 April 2002. The AD was notified in the Commonwealth of Australia Gazette on 27 March 2002. The Compliance section reiterates the effective date and defines the operational timing for inspections and the discretionary reinforcement option coincident with that effective date.

The Background section explains the rationale for the original AD: it "was originally issued to require the inspection and reinforcement of the engine baffle seals" in response to reports of engines overheating from ill-fitting and blown-back baffle seals. Amendment 1 is presented as reflecting the issue of FAA Airworthiness Directive 93-23-13 and introduces an extension of the inspection interval.

The AD therefore documents three stages: the original AD in 1980, the intervening regulatory history (not detailed in the text beyond revocation), and the issuance of Amendment 1 in 2002 that both incorporates the influence of FAA AD 93-23-13 and changes the inspection interval. The AD text does not provide a detailed sequence of prior amendments between 1980 and 2002; it only states that the original AD became effective on 31 December 1980 and that this document revokes AD/PA-31/96 and issues AD/PA-31/96 Amdt 1.

This Amendment 1 has two substantive mechanical changes compared with the original AD as described: it references FAA AD 93-23-13 in its rationale, and it "introduces an extension of the inspection interval." The AD does not reproduce the prior inspection interval, so the extent of the extension relative to the prior requirement is not stated in the text. The amendment also formalises the inspection timing as "within 55 hours time in service and thereafter at intervals not to exceed 55 hours time in service" and clarifies that reinforcement remains available as terminating action at the operator’s discretion, implemented as per the Service Bulletin or CASA approval under CAR 35.

No later amendments or revocations are recorded in the AD text provided. The AD’s administrative metadata , signature date, effective date and Gazette notification date , are stated, forming the formal amendment history contained within the instrument itself.

The AD text supplied contains no record of litigation. It does not reference any court proceedings, appeals, tribunal decisions, or enforcement actions arising from AD/PA-31/96 or its Amendment 1. The document is an administrative instrument: it records issuance by a CASA delegate under subregulation 39.1(1) of CAR 1998, but it does not recount any subsequent or prior litigation related to the AD.

The AD does reference an FAA Airworthiness Directive (FAA AD 93-23-13), but that is an administrative action in another jurisdiction and the AD text does not mention any legal challenges to that FAA AD nor any transnational litigation or disputes arising from conflicting obligations. The AD also states it revokes the prior AD and issues this amendment but does not record any appeals or objections to that revocation or replacement.

Because the AD contains no litigation history, readers seeking precedent about how courts or tribunals have treated compliance with ADs, enforcement actions under CAR 1998, or disputes over service bulletin obligations would need to consult external legal materials beyond this instrument. The AD itself provides no record of such cases.

If litigation or administrative review had occurred and been relevant to the AD’s content or enforceability, the AD text would typically indicate that as background or in an explanatory memorandum. In its absence, the instrument stands as an administrative regulatory direction with no litigation annotations in the supplied text.

Several practical hazards and points of potential misunderstanding arise from the AD’s wording and structure. These are matters operators and maintainers should note when interpreting obligations and planning compliance.

Serial-number-based applicability: The Applicability section ties affected aircraft to serial numbers "as detailed by serial number in Piper Service Bulletin Number 693." That means simply owning a PA-31 series airframe is not, on face value, sufficient to determine whether the AD applies; operators must obtain Piper Service Bulletin No 693 and cross-check serial numbers. Missing that discrete serial-number check could lead an operator either to assume wrongly that their aircraft is unaffected or to unnecessarily perform work on an unaffected aircraft.

Reliance on Service Bulletin instructions: The AD requires compliance "in accordance with Instructions A/B of Piper Service Bulletin No 693." The AD does not reproduce the technical steps, acceptance criteria or parts lists. Operators must secure the correct Service Bulletin and ensure the maintenance actions are executed exactly as specified or as approved under CAR 35. Misinterpretation of the Service Bulletin or reliance on incomplete copies could result in non-compliance.

Inspection timing and operational downtime: The inspection timing is prescriptive: initial inspection within 55 hours TIS and thereafter at intervals not to exceed 55 hours TIS. For operators used to different scheduling regimes, this requires close attention to Hobbs or tachometer logs and to maintenance planning. The relatively short interval could impose recurring operational downtime and labour costs, especially for high-utilisation aircraft. Operators might mistakenly calculate intervals based on calendar days instead of hours time in service, but the AD specifies hours time in service, so minute deviations could cause non-compliance.

Operator discretion and terminating action nuance: The AD makes reinforcement "At the operator’s discretion" and adds that Requirement 2 provides terminating action for the inspection. A gotcha is assuming reinforcement need not be approved or documented. If an operator elects to reinforce using Instructions B, they must do so in accordance with the Service Bulletin or as approved by a CASA-authorised person. If an operator implements an alternative reinforcement technique without CAR 35 approval, the AD’s terminating action may not apply and the operator could still be required to comply with recurring inspections.

Approval under CAR 35: Requirement 2 permits alternative reinforcement "as approved by a person authorised by CASA (CAR 35)." The gotcha here is administrative: securing CAR 35 approval may require technical substantiation, lead time, and interaction with CASA. Operators who assume alternative methods will be accepted without prior approval risk a post-hoc determination that their reinforcement does not terminate inspection requirements.

FAA reference: The AD "reflects the issue of FAA Airworthiness Directive 93-23-13." Operators should not assume that following the FAA AD alone is sufficient for CASA compliance. The AD incorporates Piper Service Bulletin No 693 by reference; inspectors should verify that the remedial steps correspond and that serial-number applicability is matched. If an operator is registered in a jurisdiction other than Australia or operates internationally, parallel obligations may exist, but the AD stands on CAR authority for Australian-registered aircraft.

No penalty text in AD: The AD does not set out penalties or enforcement mechanisms within its text. Operators might misread that omission as implying informal or discretionary enforcement; the AD is nevertheless issued under CAR 1998 authority. The procedural reality of enforcement and any sanctions will be governed by the broader regulatory framework and CASA practice, not by this AD text, which is a possible source of misapprehension.

Record-keeping expectations: The AD does not explicitly spell out maintenance sign-off or logbook entry requirements, but common maintenance practice requires recording compliance. Failing to document inspections or reinforcement properly could impede evidence of compliance, a risk not stated in the AD but a practical gotcha for operators relying on record-keeping practices.

Timing of effectiveness and transition: The AD states it becomes effective 18 April 2002 and that the initial inspection must be within 55 hours TIS from that effective date. Operators should confirm how to calculate time-in-service from the effective date, especially if aircraft were in storage or had low utilisation, to avoid late initial inspections.

In sum, the primary practical pitfalls are misreading applicability, failing to implement or document Service Bulletin instructions precisely, misunderstanding the approval process under CAR 35 for alternatives, underestimating inspection scheduling burden, and assuming the AD contains enforcement details that it does not. Each of these can be managed by obtaining and following Piper Service Bulletin No 693, confirming serial-number applicability, planning for the 55-hour inspection cadence, and engaging CASA early if alternative reinforcement actions are contemplated.

Compliance with AD/PA-31/96 Amdt 1 requires a sequence of documented, scheduled actions keyed to the AD text and to the referenced Piper Service Bulletin No 693. The AD prescribes two technical paths: recurring inspections (mandatory unless terminated) and a one-time reinforcement (optional but terminating). The following steps describe how an operator should approach compliance, strictly based on the AD’s text.

1. Determine applicability precisely. Obtain Piper Service Bulletin No 693 and check the serial-number list it contains. The AD’s Applicability section makes the affected population dependent on the serial numbers "as detailed by serial number in Piper Service Bulletin Number 693." If the aircraft’s serial number is not listed in that bulletin, the AD does not apply to that aircraft as per this instrument.

2. If the aircraft is applicable, plan and schedule the initial inspection. Requirement 1 mandates inspection "in accordance with Instructions A of Piper Service Bulletin No 693." The Compliance section sets the initial timing: perform the inspection within 55 hours time in service. Operators should calculate time in service accurately from the aircraft’s logbook or Hobbs/tachometer records and ensure the initial inspection occurs no later than 55 hours TIS after the effective date or entry into the required regime.

3. Implement recurring inspection cadence. Once the initial inspection is complete, continue inspections at intervals "not to exceed 55 hours time in service." Establish maintenance tracking to ensure inspections occur within those intervals. This scheduling must be integrated into maintenance planning so that aircraft availability and operator scheduling reflect recurring inspections at the specified hours-based frequency.

4. Review Instructions A thoroughly. The AD requires the inspection be performed "in accordance with Instructions A of Piper Service Bulletin No 693." Obtain a complete, current copy of the Service Bulletin, ensure maintenance personnel understand the inspection procedure, acceptance criteria and any parts or special tools required, and follow the manufacturer’s specified technique and sign-off requirements.

5. Decide on reinforcement. The AD allows reinforcement under Requirement 2 "in accordance with Instructions B of Piper Service Bulletin No 693 or as approved by a person authorised by CASA (CAR 35)." The reinforcement is at the operator’s discretion and, if carried out as specified or approved, provides terminating action for the recurring inspection requirement. Operators should undertake a cost-benefit analysis: compare the recurring inspection costs, labour and downtime against the one-off reinforcement cost, parts availability and any operational outage.

6. If electing reinforcement, follow Instructions B or obtain CAR 35 approval for alternatives. If installing the reinforcement as per Instructions B, ensure the installation conforms exactly to the Service Bulletin instructions. If proposing an alternative reinforcement procedure, submit the proposal to a person authorised by CASA under CAR 35 and obtain approval prior to implementing the alternate method; without such approval the AD’s terminating action may not apply.

7. Maintain records. Although the AD text does not specify the precise form of record-keeping, standard aviation maintenance practice requires entries in maintenance logs and records to show compliance with ADs. Record the date, aircraft serial number, total time in service at the time of inspection or reinforcement, reference to Piper Service Bulletin No 693 Instructions A or B, sign-off by the authorised maintenance personnel, and any CAR 35 approvals obtained. Documentation will be evidence of compliance in the event of regulatory queries.

8. Coordinate with CASA where needed. If there is any doubt about serial-number applicability, interpretation of Service Bulletin instructions, or acceptance of alternative reinforcement methods, engage with CASA-authorised personnel under CAR 35 for guidance and prior approval. Requirement 2 explicitly allows "as approved by a person authorised by CASA (CAR 35)" as an alternative compliance route.

9. Factor in operational scheduling and parts lead times. The inspection interval may impose frequent returns to maintenance, so planning must account for parts, tooling and personnel. If reinforcement parts are required, obtain them in advance to avoid prolonged grounding when the operator elects the terminating action.

10. Observe effective dates. The AD became effective 18 April 2002. For historical compliance or retrospective audits, confirm that inspections were scheduled in accordance with the AD’s compliance schedule from that effective date forward.

By following these steps , check serial-number applicability, perform and document inspections per Instructions A within the 55-hour cadence, elect reinforcement if appropriate and perform it per Instructions B or pursuant to CASA approval, and keep records , operators will implement the corrective regime mandated by AD/PA-31/96 Amendment 1. The AD binds operators through CAR 1998 authority, so adherence to the specified instructions and approval processes is the required route to regulatory compliance.