AD/PA-31/51 Amdt 1 - Flap Transmission - Inspection

The directive rests on a small set of concepts that structure operator obligations and available compliance paths. First, applicability: the directive specifies the exact models and serial number ranges to which it applies, and it expressly carves out aircraft that have incorporated a named service letter, Piper SL 959 (Applicability; Background). The list of affected models and serial numbers is precise in the text, and the exclusion is categorical: aircraft incorporating SL 959 are not within the directive’s scope.

Second, normative technical instructions: the directive does not itself set out inspection steps, it directs operators to follow one of two named manufacturer publications, Piper SB No. 494B Instruction No. 1 or Piper SL No. 764A Instruction No. 1 (Documents). These references are normative for compliance. The directive therefore functions as a regulatory bridge that makes compliance contingent on adherence to specified manufacturer procedures.

Third, timing and periodicity: there is a short-term initial deadline and an ongoing inspection interval. The initial inspection must be performed within 25 hours time in service after 28 October 1976, with subsequent inspections no more than every 100 hours time in service (Compliance). The directive also contains a cross-credit provision: if Section 2 of AD/PA-31/44 has been complied with within the past 100 hours time in service, that satisfies the 25-hour initial requirement here (Note). That creates a limited substitution rule between directives for the early compliance window.

Fourth, an optional modification pathway: the Background states that Piper SL 959 introduces an optional flap control system which restores 40 degree flap movement and relieves the specific inspections on some aircraft. The directive’s applicability explicitly excludes aircraft that have incorporated Piper SL 959. That makes incorporation of a manufacturer modification a formal compliance alternative to repeated inspections for aircraft owners and operators.

Fifth, delegation of technical detail and the locus of decision: the Civil Aviation Safety Authority heading indicates the issuing regulator, and the directive places technical decision-making on the content of the referenced Piper documents rather than embedding technical steps into the directive text. The operator’s duty is therefore to execute the named documents’ instructions at the stated interval, or to install the optional modification to be exempted.

These concepts combine to create a compliance architecture where operator behaviour choices are: conduct periodic inspections to a manufacturer procedure, obtain credit via compliance with a related AD within a recent time band, or incorporate a specified optional modification to avoid the inspections. The directive is prescriptive about timing and document-based process, but it delegates technical content and the mechanics of exemption to external Piper publications and the optional modification named in the Background.

The directive’s applicability clause identifies precisely which aircraft are subject to the inspection requirement. It applies to Piper PA-31 models including PA-31, PA-31-300 and PA-31-325 with serial numbers 31-2 through 31-7812129; PA-31-350 with serial numbers 31-5001 through 31-7852171; PA-31P with serial numbers 31P-1 through 31P-7730012; PA-31T with serial numbers 31T-7400002 through 31T-7820092; and PA31T1 with serial numbers 31T-7804001 through 31T-7804011, subject to the exception for aircraft that have incorporated Piper SL 959 (Applicability). The directive thus targets a defined cohort of airframes by model and narrow serial number ranges, rather than all PA-31-type aircraft.

Primary parties who bear duties under the directive are therefore registered owners and operators of the listed aircraft that have not incorporated the named optional modification. Those owners/operators must ensure the inspections are performed within the prescribed timing windows and must follow the specific Piper documents named in the directive. Maintenance organisations and certificated maintenance engineers who perform the work will be operationally involved, because the directive requires adherence to the procedures in Piper SB No. 494B Instruction No. 1 or Piper SL No. 764A Instruction No. 1 (Documents). Where owners have installed Piper SL 959, the aircraft are expressly excepted from the directive’s applicability, so installation status is a determinative fact for whether obligations apply.

The directive’s Note creates an additional affected group dynamic: an operator who has complied with Section 2 of AD/PA-31/44 within the past 100 hours time in service will be treated as having satisfied the 25-hour initial requirement here. That makes prior compliance activity with a different AIRWORTHINESS DIRECTIVE relevant to the temporal obligations under this directive. Consequently, record-keepers and inspectors who evaluate compliance will need to review maintenance records for evidence of Section 2 compliance with AD/PA-31/44 within the specified recent operating time.

Regulatory bodies and enforcement personnel named in the heading, namely the Civil Aviation Safety Authority as the issuing authority, are the public actors responsible for promulgation and oversight, although the directive text itself does not enumerate enforcement steps (header; Compliance). In short, the directive affects a geographically and numerically limited set of aircraft, their owners/operators, and the maintenance providers who execute the specified Piper procedures; it provides an alternative compliance pathway by incorporating an optional manufacturer modification, which in turn reallocates who pays and who acts.

The directive imposes discrete duties on affected aircraft owners and operators and simultaneously provides narrow, document-based rights or exemptions. The central duty is to perform the inspection of the flap transmission in accordance with one of the two referenced Piper documents: Piper Service Bulletin No. 494B, Instruction No. 1, or Piper Service Letter No. 764A, Instruction No. 1 (Documents). The directive leaves the technical method to those documents, but makes compliance with them mandatory for covered aircraft that have not incorporated the identified optional modification.

Timing duties are explicit. Operators must carry out an initial inspection within 25 hours time in service after 28 October 1976, and thereafter perform inspections at intervals not exceeding 100 hours time in service (Compliance). The 25-hour initial window is subject to substitution where the operator has complied with Section 2 of AD/PA-31/44 within the past 100 hours time in service; in that case, such compliance satisfies the 25-hour requirement of this directive (Note). This creates a definable right to credit for prior work done under a specified related directive, thereby reducing duplication of inspection effort within the stated recent operating-time band.

An explicit right of exclusion is granted to aircraft which have incorporated Piper SL 959, an optional flap control system which, the Background states, restores 40 degree flap movement and relieves the specific inspections on some aircraft (Applicability; Background). The directive therefore recognises a choice-based right: installation of the named optional modification is an available pathway for an owner to avoid the inspection obligations imposed by the directive. The directive does not specify eligibility criteria for relief beyond incorporation of SL 959, so the practical scope of the exemption will depend on whether an aircraft can be shown to have incorporated the modification.

Record-keeping and proof obligations are implicit in the structure: operators who rely on the AD/PA-31/44 credit or on incorporation of SL 959 will need documentary evidence to establish entitlement to the exceptions or credits. The directive itself references the precise documents that must be followed for inspection, which focuses compliance assessment on whether the named procedures were followed at the stated intervals.

The directive does not itself articulate any appeal process or procedural rights against enforcement within the text provided. It therefore establishes duties of periodic action and limited rights of credit or exemption, while delegating technical content and the procedural mechanics of relief to the manufacturer documents and the fact of incorporation of the optional service letter.

The directive text sets out mandatory inspection timing and prescriptive documentary references, but it does not include explicit penalty provisions or enforcement mechanisms within the four main labelled sections (Applicability; Documents; Compliance; Note; Background). There is a regulatory heading indicating the Civil Aviation Safety Authority and that the instrument is part of the schedule of airworthiness directives under the Civil Aviation Regulations 1998, Part 39. However, no fines, licence consequences, or procedural enforcement steps are spelt out in the directive itself. The absence of penalties in the text means the directive operates as a prescriptive rule that must be read in the regulatory context provided by the parent Civil Aviation Regulations and any enforcement instruments that sit outside this specific entry.

In practice, enforcement of an airworthiness directive like the one presented typically relies on the broader regulatory framework for airworthiness and operation of aircraft, including administrative oversight, airworthiness certification checks, and possible sanctions under the overarching civil aviation regulations. The directive does not identify those mechanisms, nor does it describe inspection or audit procedures to be performed by the regulator. It also does not specify who is responsible for verifying compliance at the point of aircraft operation, beyond the implicit duty on operators and the named maintenance documents that must be followed.

The directive does include a compliance schedule that can be used as the basis for enforcement action, namely the initial 25-hour deadline after 28 October 1976 and recurring inspections every 100 hours thereafter (Compliance). The Note’s credit for compliance with Section 2 of AD/PA-31/44 creates a documented substitution that regulators and audited operators may rely upon when assessing compliance status. The exclusion for aircraft incorporating Piper SL 959 similarly creates a documentary test: an operator asserting the exemption would be expected to show evidence that SL 959 was incorporated.

Because penalties and enforcement processes are not specified here, compliance assessment will require cross-referencing regulatory enforcement provisions external to this text. The directive itself supplies the substantive obligations and exemptions, but not the enforcement toolkit or sanctioning language. Parties seeking to understand enforcement consequences for non-compliance therefore must consult the broader Civil Aviation Regulations or regulatory guidance issued by the Civil Aviation Safety Authority, material not contained within this directive text.

This directive sits within the Commonwealth framework for civil aviation regulation by its heading, which identifies the Civil Aviation Regulations 1998, Part 39, and the Civil Aviation Safety Authority schedule of airworthiness directives. The document explicitly cross-references at least one other airworthiness directive, AD/PA-31/44, by providing a crediting mechanism: compliance with Section 2 of AD/PA-31/44 within the past 100 hours time in service satisfies the 25-hour initial requirement of this directive (Note). This is a concrete interaction within the airworthiness directive corpus, creating a formal substitute for the initial inspection timing based on prior compliance with a related AD.

The directive also anchors technical compliance to manufacturer publications by mandating that inspections be carried out in accordance with Piper Service Bulletin No. 494B, Instruction No.1, or Piper Service Letter No. 764A, Instruction No.1 (Documents). Those documents are external technical sources but become normative by reference when the directive is applied, which means that compliance with the directive requires compliance with the content of those manufacturer documents. The directive therefore operates by reference, making manufacturer maintenance instructions integral to the regulatory obligation.

The Background references a further manufacturer modification, Piper SL 959, which it identifies as an optional flap control system. That service letter is a compliance interaction point in two respects: firstly, incorporation of SL 959 is an express exemption to the directive’s applicability, and secondly, the Background describes the modification as relieving specific inspections on some aircraft. The directive thus creates a direct legal-technological interaction between regulatory obligations and optional manufacturer modifications.

The directive does not, within its text, reference other statutory instruments, administrative rules, or enforcement provisions. It therefore leaves the relationship to enforcement law, pilot licensing, operational rules, and property or contract law outside the document. The necessary inferences are limited to what is explicitly stated: that compliance timing may be satisfied by prior compliance under AD/PA-31/44, and that compliance procedures must follow specific Piper documents. Any further interaction with the Civil Aviation Regulations’ enforcement, certification, or operational rules will depend on those external instruments and is not contained in the directive’s text.

In practice, the directive’s cross-references mean that operators must track multiple instruments together: the AD/PA-31/51 Amendment 1 entry itself, the referenced Piper SB or SL documents for technical detail, AD/PA-31/44 for potential credit, and the record of whether Piper SL 959 is incorporated for exemption status. The directive therefore compels coordination across manufacturer documentation and the corpus of ADs, while leaving procedural enforcement and sanctioning to the broader regulatory framework.

The document is titled AD/PA-31/51 Amendment 1, with the notation "Amdt 1" and the date 10/83, indicating this text is an amendment to an existing airworthiness directive identified as AD/PA-31/51. The amendment label and date are the only amendment history elements provided in the text. The presence of the Note that references AD/PA-31/44 indicates interaction with prior directives, and suggests that the directive series includes at least AD/PA-31/44 and AD/PA-31/51, with this entry recorded as Amendment 1 to AD/PA-31/51. Beyond the amendment number and date, the document does not provide a legislative or amendment history narrative, redline, or comparative text showing what was changed by Amendment 1.

The instrument’s header places it under the Civil Aviation Regulations 1998, Part 39 schedule of airworthiness directives, which establishes the formal administrative context. No effective-dates section is provided beyond the compliance timing anchored to the historical date of 28 October 1976 for the initial 25-hour window, and the subsequent recurring inspection interval of 100 hours time in service (Compliance). The directive’s formatting as an amendment suggests it was intended to modify or clarify an earlier AD/PA-31/51 entry; however, the text does not state whether the amendment added the list of serial numbers, changed compliance intervals, introduced the crediting note, or added the SL 959 exemption. The only explicit temporal marker is the issuance label "10/83" tied to the amendment.

Users seeking a complete amendment trace must therefore look beyond this single document text to the administrative record or repository that contains the original AD/PA-31/51 and any prior amendments or related ADs such as AD/PA-31/44. The directive itself provides a limited amendment history: it is Amendment 1 to AD/PA-31/51 dated October 1983, and it cross-references a prior directive for the purposes of crediting early compliance. No further amendment chronology, rationale for amendment, or comparison to prior text is included in the directive entry.

The directive text contains no litigation history, case citations, or references to judicial or administrative determinations. There are no reported disputes, appeals, or precedent recorded within the document. Consequently, the instrument does not itself identify any litigation arising from its application, nor does it document any challenges to its technical content, applicability, or enforcement. The absence of litigation material is a factual characteristic of the document as provided.

While the document does not report litigation, the content nonetheless contains elements that could, in practice, give rise to disputes, because the instrument ties compliance to external documents and factual predicates. Two possible sources of procedural or evidentiary contention suggested by the text are the exemption for aircraft that have incorporated Piper SL 959, and the credit for compliance with Section 2 of AD/PA-31/44 within the past 100 hours time in service. Determination of whether an aircraft has incorporated SL 959 will require maintenance records or other documentary proof; disputes could arise over sufficiency of proof, interpretation of incorporation, or whether the specific installation meets the exemption’s terms. Similarly, whether Section 2 of AD/PA-31/44 was complied with within the relevant 100-hour window is a matter of recordation and interpretation of what constitutes compliance under that other directive, which could be contested.

The directive’s dependence on external Piper documents for the inspection procedure can also create fact-specific questions about what work was done and whether it followed the required instructions, which is a common locus for compliance or enforcement disputes. The directive itself does not provide adjudicative mechanisms or dispute-resolution steps, so any litigation or administrative review would appear in other records not included here.

In sum, this document contains no litigation history. The text does, however, create concrete factual issues,record evidence of SL 959 incorporation and proof of compliance with AD/PA-31/44,that are foreseeable points of contention in compliance assessments. Because this directive does not include enforcement or dispute-resolution particulars, any litigation record would be located in the Civil Aviation Safety Authority records, tribunal files, or court dockets, none of which are part of the supplied text.

The directive contains a number of technical and procedural features that can be sources of operational friction or misinterpretation if not carefully handled. First, the applicability is specified by model and detailed serial-number ranges. A gotcha for operators and maintenance personnel is strict reliance on exact serial number ranges; an aircraft whose serial number falls even slightly outside the listed ranges will not be covered by this directive as written, while an aircraft inside the range will be covered unless it can be shown to have incorporated SL 959. Meticulous verification of the serial number against the list in the (Applicability) clause is therefore necessary to determine whether obligations apply.

Second, the directive excludes aircraft which have incorporated Piper SL 959, but the document does not elaborate on how incorporation must be proved. The Background states that SL 959 introduces an optional flap control system and relieves specific inspections on some aircraft. A practical gotcha is the lack of detail about what constitutes incorporation, whether a field modification, retrofit, or partial incorporation is sufficient, and what documentary evidence is required. Operators relying on the exemption will need to preserve clear maintenance records evidencing installation and the date of incorporation, because the directive itself adjudicates exemption status solely by reference to incorporation of SL 959 without further procedural detail.

Third, the timing regime includes a historically dated initial window: the initial inspection must be done within 25 hours time in service after 28 October 1976. Because that date is historical and the directive permits credit where Section 2 of AD/PA-31/44 has been complied with within the past 100 hours, operators or auditors working with the legacy fleet must take care when reconstructing historical compliance, particularly where records are incomplete. The Note’s crediting mechanism can relieve the pressure of the 25-hour initial window, but it requires clear documentation of compliance with AD/PA-31/44 Section 2 within the prior 100 hours, which is another evidentiary requirement.

Fourth, the directive mandates compliance with one of two named Piper documents for the inspection procedure. A gotcha is selecting the correct document and the correct Instruction No.1 within that document. If a maintenance provider follows an incorrect or an outdated revision of the named SB or SL, whether that satisfies the directive is an evidentiary and interpretive issue. The directive does not specify revision levels, so compliance may depend on showing that the specific Instruction No.1 was followed as contemporaneously issued.

Fifth, the Background uses the phrase "relieves the specific inspections on some aircraft," which is non-specific. There is potential ambiguity about which "specific inspections" are relieved and whether any follow-up or alternative inspection regimen is required for aircraft with SL 959. The directive does not enumerate those specifics, so operators must rely on the content of SL 959 or the referenced SB/SL documents to determine whether additional work is required.

Finally, the directive does not set out enforcement penalties or corrective actions. This absence can be a gotcha when operators seek clarity about the consequences of non-compliance. While the directive imposes mandatory inspection timing, it defers enforcement detail to the broader regulatory framework, so parties must not assume the directive itself contains the full compliance-and-penalty picture.

Taken together, these points mean that careful record management, precise serial-number checking, confirmation of the correct technical documents and their revision status, and clarity about what constitutes incorporation of SL 959 are concrete compliance priorities for operators and maintenance organisations acting under this directive.

Compliance under this directive is a matter of executing the inspection at the specified times and following the named manufacturer instructions, or installing the optional modification identified in the Background. The directive prescribes two parallel compliance pathways.

First pathway, inspection cycle: For affected aircraft that have not incorporated Piper SL 959, perform the flap transmission inspection in accordance with either Piper Service Bulletin No. 494B, Instruction No. 1, or Piper Service Letter No. 764A, Instruction No. 1 (Documents). The initial inspection must be completed within 25 hours time in service after 28 October 1976, unless compliance with Section 2 of AD/PA-31/44 within the past 100 hours time in service can be demonstrated, in which case that earlier compliance satisfies the 25-hour requirement (Compliance; Note). Thereafter, schedule and carry out the same inspection at intervals not exceeding 100 hours time in service. Maintain contemporaneous, verifiable records that show the inspection date, time in service at inspection, the identity of the maintenance organisation or certifying engineer, and the reference to the Instruction No. 1 of the named Piper document used to perform the inspection.

Second pathway, optional modification: If an operator chooses to incorporate Piper SL 959, which the directive’s Background states restores 40 degree flap movement and relieves the specific inspections on some aircraft, document the incorporation thoroughly. Ensure there is an unambiguous maintenance record or logbook entry showing the SL 959 incorporation, the date, the work package performed, and any certification or sign-off required by the operator’s maintenance organisation or the applicable regulatory maintenance certification regime. Once incorporation is demonstrably completed, the aircraft is excepted from the applicability of this directive as written (Applicability; Background).

Practical steps to reduce compliance risk: confirm whether the aircraft’s serial number falls within one of the listed ranges in the (Applicability) clause; if so, determine whether SL 959 is installed; if not installed, obtain and follow the correct version of one of the two named Piper documents and document each inspection against the 25-hour/100-hour schedule; if credit is being claimed under the Note, retain the maintenance records that evidence Section 2 compliance with AD/PA-31/44 within the specified recent 100-hour window.

Maintenance providers should verify they have the correct Instruction No. 1 from the named Piper SB or SL, and record which document and which instruction set was followed. Operators should treat the directive’s timing windows as mandatory and retain documentary proof to present to any regulatory inspector or auditor. If there is uncertainty about whether an aircraft’s installation of SL 959 meets the exemption or whether a particular maintenance action satisfies Section 2 of AD/PA-31/44 for credit purposes, obtain written confirmation from the maintenance organisation or a regulatory authority, and preserve that confirmation in the aircraft’s maintenance records.

The directive itself does not describe remedial action or enforcement penalties, so complying parties should also maintain an awareness of broader regulatory obligations under the Civil Aviation Regulations and ensure that inspections and modifications are performed by appropriately certificated personnel and recorded in accordance with standard airworthiness record-keeping practices.