AD/PA-31/102 Amdt 2 - Flap Travel Restriction and Wing Flap Flexible Drive Shaft

The AD operates through a small set of interlocking administrative and technical concepts. First, it is an airworthiness directive tied to a manufacturer Service Bulletin. The AD text states the Requirement as "Action in accordance with Piper SB No. 741." That converts a manufacturer-issued technical instruction into a mandatory regulatory action for the specified fleet subset.

Second, applicability is defined by model type and serial number references. The AD lists "Piper PA-31 Series Aeroplanes" and then specifies "All models PA-31T Cheyenne" and related PA-31 family variants, qualified by serial numbers "referenced in Piper SB No. 741 or ... subsequent issues of that SB." Therefore applicability is not simply by model name alone; it is model plus the serial numbers identified in the Service Bulletin and its later revisions. The AD text explicitly links the serial number list to the Service Bulletin and to subsequent issues of the Service Bulletin.

Third, the AD creates an operational constraint tied to a particular remedial state. The AD contemplates that the required SB action may restrict maximum flap travel to "15`". Where that restriction applies, the AD prescribes two concrete operational adjustments: increase landing distances in the Australian Flight Manual by 15% and increase approach speeds by 5 knots. The AD then requires that the AFM be formally amended "in accordance with the appropriate Department of Aviation approved flight manual amendment." That introduces a regulator-approved documentation step in addition to the physical modification.

Fourth, the AD establishes a compliance date: "with effect from 30 June 1982." The Requirement phrase "In accordance with the Requirement document" ties the timing and technical content of compliance to the Service Bulletin as the technical Requirement document.

Fifth, the AD records the safety rationale in a Background paragraph. The AD identifies the failure mode as "failures of the wing flap flexible shaft assemblies" reported in the field and links Amendment 2's purpose to introducing flight manual amendments "to cover performance changes introduced by the Service Bulletin."

These concepts create a chain of authority and action: manufacturer technical guidance (SB No. 741 and its subsequent issues) is made mandatory for the affected serial-numbered aeroplanes by the AD; the physical or operational outcomes of that guidance (in particular any restriction to 15` flap travel) must be reflected in AFM performance data, via a Department of Aviation approved amendment available through Regional Offices; and all of this must be completed by the specified effective date.

The AD names a narrow set of primary obligated parties, and it imposes consequential duties on ancillary actors involved in operations, maintenance, and regulatory authorisation.

Primary affected parties

• Owners and operators of Piper PA-31 series aeroplanes whose serial numbers are listed in Piper SB No. 741 or in subsequent issues of that Service Bulletin. The AD’s Applicability description ties obligation to model and to serial numbers referenced in the SB: "Applicability: All models PA-31T Cheyenne ... with S/Nos. referenced in Piper SB No. 741 or ... subsequent issues of that SB." That language makes the owner/operator of an aeroplane with an affected serial number the direct target of the Requirement.

Maintenance and maintenance organisations

• Organisations or individuals responsible for performing the actions set out in Piper SB No. 741 will be engaged. The AD makes the SB the operative technical Requirement: "Action in accordance with Piper SB No. 741." That makes maintainers the executing parties for the mechanical work, parts replacement, inspections or limits set out in the SB.

Pilots and flight operations personnel

• Where the SB results in a maximum flap travel restriction to "15`", pilots and flight operations personnel must apply the altered performance parameters: "Australian Flight Manual landing distances shall be increased by 15% and approach speeds shall be increased by 5 knots." Those changes affect dispatch decisions, performance calculations, and possibly weight and balance or route planning.

Regulator and Department of Aviation

• The AD requires Australian Flight Manual amendments "in accordance with the appropriate Department of Aviation approved flight manual amendment." The Department is therefore the approving authority for the AFM amendment referred to. The AD also notes that "Appropriate amendments will be available from Regional Offices," implicating the Department’s regional infrastructure as the distributor of approved material.

Manufacturer (Piper)

• Piper is implicated as author of SB No. 741, which forms the technical basis of the AD. The AD’s Background specifically says "field reports have been received by the manufacturer" and directs action "in accordance with Piper SB No. 741."

Third parties and commercial consequences

• Aircraft lessors, insurers, and operators that plan aircraft utilisation are indirectly affected because performance and availability may change. The AD prescribes concrete AFM performance adjustments that will feed into operations planning, insurance underwriting and scheduling decisions. The AD’s Background explains these measures respond to field-reported failures of "wing flap flexible shaft assemblies," a technical failure mode that can influence operational risk assessments.

In short, the AD imposes obligations on operators and maintenance providers to follow a manufacturer Service Bulletin, requires regulators to approve AFM amendments and supply them via Regional Offices, and creates operational impacts for pilots and commercial stakeholders through mandated changes to landing distances and approach speeds where flap travel is restricted.

The AD sets out discrete duties and the associated administrative steps that affected parties must take. It also implies certain limited rights of access to approved material.

Primary duties

• Implement the Requirement: The AD commands "Action in accordance with Piper SB No. 741" for aeroplanes within the AD’s applicability. That places a duty on owners/operators and their maintenance organisations to obtain and execute the procedures, inspections, repairs or modifications set out in the Service Bulletin and any subsequent issues referenced. The text makes the SB the operative technical requirement.

• Update the Australian Flight Manual where flap travel is restricted: The AD specifies that "when the maximum flap travel is restricted to 15` Australian Flight Manual landing distances shall be increased by 15% and approach speeds shall be increased by 5 knots." This is a twofold duty: apply the altered performance parameters operationally, and reflect them in the AFM.

• Obtain regulator-approved AFM amendments: The AD requires that Australian Flight Manuals "are to be amended in accordance with the appropriate Department of Aviation approved flight manual amendment." That is a formal documentation and approval duty and, by the AD’s terms, necessitates seeking the Department-approved amendment.

• Use approved distribution channels: The AD states "Appropriate amendments will be available from Regional Offices." Affected parties therefore have a duty to obtain the authorised AFM amendment from the Department’s Regional Offices rather than relying on non‑approved substitutes.

Timing duty

• Comply by the effective date: "Compliance: In accordance with the Requirement document, with effect from 30 June 1982." This imposes a temporal obligation to complete the required work and documentation by that effective date in accordance with the SB’s instructions.

Implied administrative duties

• Confirm serial number applicability: Because the AD ties applicability to serial numbers "referenced in Piper SB No. 741 or ... subsequent issues of that SB," an affected owner/operator bears the duty of checking whether their aeroplane’s serial number appears in the SB or its later issues before deciding which obligations apply.

Rights and access

• Right to obtain approved amendments: The AD explicitly states that the Department of Aviation approved flight manual amendments will be available and directs affected parties to Regional Offices. That gives operators a right of access to approved AFM amendment material through specified channels.

• Right to follow the Requirement document as the compliance standard: By making "Action in accordance with Piper SB No. 741" the Requirement, the AD identifies the SB as the compliance standard. This provides a clear technical benchmark for maintenance work, insofar as the SB text is obtainable and is authoritative for satisfying the AD.

What the AD does not state as rights or duties

• The AD text does not enumerate any administrative appeal rights, compensation entitlements, or waivers. It also does not spell out record-keeping requirements, who pays for the work, or the process for seeking alternative compliance methods. Those matters are not addressed in the AD text and therefore are not express duties or rights within this instrument.

All duties and stated access channels above are grounded in the AD text: "Requirement: Action in accordance with Piper SB No. 741"; the flap travel and AFM instructions; the Department approval requirement; and the compliance date "with effect from 30 June 1982."

The AD text provided does not set out explicit penalties, sanctioning mechanisms, or an enforcement regime. The document specifies the technical Requirement, the AFM amendment obligations, where approved amendments will be available, and a compliance effective date, but it contains no express penalty clause or description of enforcement actions.

What is explicit in the AD

• Required actions: "Action in accordance with Piper SB No. 741."
• AFM amendments and performance changes: "Australian Flight Manual landing distances shall be increased by 15% and approach speeds shall be increased by 5 knots" where flap travel is restricted, and those AFM amendments "are to be amended in accordance with the appropriate Department of Aviation approved flight manual amendment."
• Compliance timing: "with effect from 30 June 1982."

What the AD does not specify

• The AD does not list fines, suspension of certificates, aircraft grounding orders, or administrative sanctions in its text. It does not describe which agency office enforces compliance beyond indicating that AFM amendments will be available from Department of Aviation Regional Offices. There is no express process for enforcement notices, compliance checks, or escalation in the event of non-compliance stated within the AD text itself.

Practical implications for affected parties

• Because the AD makes manufacturer actions mandatory and ties AFM changes to Department-approved material, failure to implement the Requirement and to install the AFM amendment as required would leave an operator in a position where the aircraft’s operational documentation and physical configuration are inconsistent with the AD. The AD’s own language requires action; the text thereby creates a regulatory obligation, even though it does not articulate the remedial or punitive steps for non-compliance in this document.

• The AD also ties the technical compliance standard to Piper SB No. 741 and to its subsequent issues where serial numbers are referenced. That means the absence of an explicit penalty clause in this AD does not eliminate the practical legal or operational consequences of failing to implement the mandatory technical requirement or to update the AFM as required.

Because the AD does not include an enforcement or penalty framework in its text, any enforcement consequences or penalty mechanisms are not stated and cannot be identified from this AD alone. The AD does, however, create clear mandatory actions and an effective date that place a compliance obligation on affected operators and maintainers.

The AD is framed as a regulatory instrument that requires the incorporation of manufacturer guidance into mandatory aeroplane configuration and flight documentation. Within the text itself, the AD identifies specific interactions with administrative approval processes and with the Australian Flight Manual regime. The AD does not explicitly reference other statutes or rules; instead it specifies interactions by instructing the incorporation of Department-of-Aviation-approved material into the Flight Manual and by making a manufacturer Service Bulletin mandatory.

Interaction with flight manual approval process

• The AD requires that Australian Flight Manuals "are to be amended in accordance with the appropriate Department of Aviation approved flight manual amendment." That indicates an interaction between the AD’s technical requirement and the Department of Aviation’s approval function for AFM changes. The AD therefore presumes a regulatory approval channel for AFM amendments and directs operators to use that channel: "Appropriate amendments will be available from Regional Offices." This creates a procedural dependency: operators must obtain the regulator’s approved change rather than unilaterally altering the AFM.

Interaction with manufacturer documentation and revisions

• The AD makes "Action in accordance with Piper SB No. 741" the Requirement and explicitly extends applicability to serial numbers listed in "subsequent issues of that SB." That sets up a direct interaction where subsequent manufacturer revisions to SB No. 741 can affect applicability and the precise technical steps required by the AD. The AD therefore concretely integrates manufacturer technical revisions into the regulatory obligation by reference.

Interaction with aircraft configuration and operational documentation

• The AD links a physical or maintenance action to operational performance data. When the SB's implementation results in maximum flap travel being "restricted to 15`", the AD mandates specific AFM performance changes: "landing distances shall be increased by 15% and approach speeds shall be increased by 5 knots." This means the AD bridges maintenance/configuration change and operational procedures/documentation, so that one regime (maintenance action per SB) directly triggers changes in another (AFM performance data).

Limits of the AD text on legal interplay

• The AD does not expressly set out how it interacts with other regulatory instruments such as certification processes, air operator certificates, maintenance data approvals, or enforcement provisions. It similarly does not state whether it displaces or supplements any other existing ADs or regulatory requirements for these aircraft. The AD does not provide cross-references to other statutes or regulations within its text.

Operational takeaway

• From the AD text, the crucial interactions are: (1) the elevation of a Piper Service Bulletin to a mandatory Requirement for certain serial-numbered aeroplanes; (2) the procedural necessity of obtaining Department-of-Aviation-approved AFM amendments; and (3) the direct linkage of a maintenance outcome (a flap travel restriction) to discrete operational performance changes that must be recorded in the AFM. Any further or broader legal interactions with other aviation laws, enforcement regimes, or certification processes are not specified in this AD text.

The document provided is explicitly an amendment: AD/PA-31/102 Amdt 2. The AD itself records that Amendment 2 introduces flight manual amendments to reflect performance changes caused by the relevant Service Bulletin. The AD includes a short Background paragraph that says: "Amendment 2 introduces flight manual amendments to cover performance changes introduced by the Service Bulletin."

What is recorded in the text

• Title and amendment number: "AD/PA-31/102 Amdt 2" indicates this is the second amendment to the AD identified as PA-31/102. The AD heading includes "Amdt 2" and a date marker "6/82", suggesting June 1982 as the issuing month/year.

• Change introduced by this amendment: The Background ties Amendment 2 specifically to flight manual changes. The text notes that "recent field reports" to the manufacturer identified flap system malfunctions due to "failures of the wing flap flexible shaft assemblies" and that Amendment 2 "introduces flight manual amendments to cover performance changes introduced by the Service Bulletin."

References to prior or subsequent documents

• The AD links applicability and technical Requirement to Piper SB No. 741 and explicitly allows subsequent issues of that Service Bulletin to be referenced: "with S/Nos. referenced in Piper SB No. 741 or with S/Nos. referenced in ... subsequent issues of that SB." That language provides a mechanism for the AD to remain tied to later SB revisions without issuing a new AD each time the SB is revised for serial-number applicability or technical detail.

What the AD does not say about amendment history

• The AD does not reproduce the prior version(s) of AD/PA-31/102 or describe the content of Amdt 1 or the original AD. It does not include a redline or tracked changes, nor does it list a sequence of prior amendments. The text only identifies itself as Amendment 2 and explains the functional purpose of that amendment (flight manual amendments to reflect performance changes introduced by the SB).

Practical inference from the AD’s amendment mechanics

• Because the AD expressly permits applicability to serial numbers referenced in "subsequent issues" of SB No. 741, the AD’s updating mechanism is to rely on manufacturer SB revisions for clarifying serial-number applicability. Amendment 2’s additional formalisation of AFM amendments indicates the regulator chose to add the operational/documentation component to the existing technical Requirement at this amendment stage.

All statements in this section are taken from the AD text: the title line "AD/PA-31/102 Amdt 2"; the date marker "6/82"; and the Background sentence "Amendment 2 introduces flight manual amendments to cover performance changes introduced by the Service Bulletin."

The AD text supplied contains no litigation history, judicial decisions, or references to legal proceedings. It is a regulatory instrument that sets technical and documentation requirements and states its rationale; it does not record any legal challenges, appeals, or court cases.

What the AD does provide

• Administrative facts: model applicability tied to serial numbers referenced in Piper SB No. 741 or its subsequent issues; a Requirement to act in accordance with Piper SB No. 741; AFM amendment requirements and distribution through Department of Aviation Regional Offices; and a compliance effective date of 30 June 1982.

What it does not provide

• The AD does not include references to any appeals process that has been invoked in respect of this AD, nor does it cite any precedent or litigation that has interpreted or tested the AD. There is no mention of litigation outcomes, no citation of judicial review, and no record of disputes within the text provided.

Consequences for legal research or compliance due diligence

• If a practitioner needs litigation or interpretative history for AD/PA-31/102, that material is not contained in this AD text and would need to be sought from external sources (regulatory records, tribunal or court databases, or Department of Aviation archival materials). The text itself cannot be used to assert there has been judicial engagement with the AD, because no such material is included.

All of the above is derived from the absence of any litigation references in the supplied AD text.

The AD’s brevity and reliance on cross-referenced documents create several practical pitfalls that operators, maintainers and regulators should be alert to. The following points are drawn directly from the AD text and highlight places where misunderstandings or implementation missteps are likely.

1. Applicability depends on serial numbers listed in a separate document

• The AD ties applicability to aeroplanes with serial numbers "referenced in Piper SB No. 741 or ... subsequent issues of that SB." That means an operator cannot determine applicability purely from the AD’s model names. Affected parties must obtain the relevant Service Bulletin and check the serial number list. Failure to consult the SB may lead to incorrect determinations about whether the AD applies to a given aeroplane.

2. The Requirement is external to the AD and may be updated

• The AD makes "Action in accordance with Piper SB No. 741" the binding Requirement and preserves applicability to serial numbers listed in "subsequent issues." Operators must ensure they are acting to the version of the SB and any of its later issues that the AD contemplates. There is a risk of working to an out-of-date SB version or misinterpreting which issue is current for compliance.

3. Ambiguity in the textual representation of the flap restriction

• The AD uses the notation "15`" to describe maximum flap travel where the restriction applies. That notation in the AD text may be interpreted as 15 (units implicit). The AD itself does not spell out the unit (for example, degrees) within its text. Operators should consult the Service Bulletin and the Department-approved AFM amendment to clarify the exact numeric and unit specifications to be adopted. Relying on the AD text alone may leave room for interpretative error.

4. Mandatory AFM changes are tied to Department approval and distribution channels

• The AD requires that AFM amendments be "in accordance with the appropriate Department of Aviation approved flight manual amendment" and that "Appropriate amendments will be available from Regional Offices." A gotcha is to assume an operator can prepare a local AFM amendment without Department approval. The AD requires use of Department-approved material and specifies the approved material is available from Regional Offices.

5. Operational performance consequences are non-trivial

• The AD prescribes that, where the flap travel is restricted to 15`, "landing distances shall be increased by 15% and approach speeds shall be increased by 5 knots." These are fixed percentages and values; operators must ensure that these numeric adjustments are inserted in AFM performance tables and that flight crews apply them in planning and dispatch. Failure to perform conservative recalculations could affect safety and regulatory compliance.

6. Compliance date may be historic, but the AD remains binding for affected serial numbers

• The AD sets a compliance date: "with effect from 30 June 1982." While the date is historical in the AD text, the practical consequence is that affected aeroplanes were required to comply from that date. If an operator has not implemented the Requirement, the AD’s text gives no retroactive waiver; however the document does not set out how to remedy legacy non-compliance. Operators should not assume that a historical compliance date obviates the obligation if the aircraft remains in service without the required action.

7. No explicit penalty or enforcement detail in the AD text

• The AD does not specify penalties, enforcement procedures, or administrative remedies. That omission can create uncertainty for operators who wish to understand the consequences of non-compliance. The AD nonetheless imposes mandatory actions; absence of penalty detail in the AD itself should not be read as absence of regulatory consequences more broadly.

8. Potential for mismatch between physical configuration and AFM data

• If maintenance action per the SB is performed but the AFM is not appropriately amended via Department-approved material, an aeroplane could be physically modified yet have operational documentation that does not reflect the new limits or performance. The AD requires both the maintenance action and the AFM amendment; failing one or the other creates a regulatory and operational mismatch.

Each of these "gotchas" arises directly from the wording and structure of the AD: the serial-number linkage to SB No. 741 and its subsequent issues; the Requirement phrasing; the flap travel restriction notation; the specific AFM percentage and speed adjustments; the Department approval and Regional Office distribution instruction; and the AD’s omission of explicit penalties or enforcement detail.

Below is a concise compliance checklist and recommended steps, grounded solely in the AD text and arranged as an actionable sequence for owners/operators, maintenance organisations and flight operations personnel. Every step references or flows from language in the AD: "Requirement: Action in accordance with Piper SB No. 741"; AFM amendment obligations; Department of Aviation approval; Regional Office availability; and the compliance date.

1. Confirm applicability by serial number

• Obtain Piper SB No. 741 and any subsequent issues of that SB referenced by the AD. The AD ties applicability to serial numbers "referenced in Piper SB No. 741 or ... subsequent issues of that SB." Cross-check the aeroplane’s serial number against the SB’s list to determine whether the AD’s Requirement applies.

2. Obtain the Requirement document and interpret its instructions

• The AD requires "Action in accordance with Piper SB No. 741." Secure the SB and carefully identify the specific actions required for the serial-numbered aircraft,inspections, repairs, replacements, limits, or configuration changes,and any tolerances, parts lists or procedural steps the SB sets out.

3. Plan and execute maintenance or modification work

• Arrange for qualified maintenance personnel or a certified maintenance organisation to carry out the SB’s instructions. Perform the work in accordance with the SB’s procedural detail to satisfy the AD’s Requirement. Where the SB limits flap travel, ensure the physical configuration confirms the limit and that hardware or mechanical constraints are installed as described in the SB.

4. Determine whether the SB’s action results in maximum flap travel restricted to "15`"

• The AD specifies additional operational obligations "in addition, when the maximum flap travel is restricted to 15`." After the SB work, determine whether the aircraft’s maximum flap travel is restricted to the specified value. Use the SB and any physical checks or measurements to confirm.

5. If the flap travel is restricted to 15`, apply the mandated AFM performance changes

• The AD mandates that in such cases "Australian Flight Manual landing distances shall be increased by 15% and approach speeds shall be increased by 5 knots." Amend operational calculations and flight planning procedures accordingly so that flight crews apply the increased landing distance and higher approach speed in dispatch and performance computations.

6. Obtain Department of Aviation approved AFM amendment

• The AD requires AFM changes "in accordance with the appropriate Department of Aviation approved flight manual amendment" and states that "Appropriate amendments will be available from Regional Offices." Contact the Department of Aviation Regional Office to obtain the approved AFM amendment and incorporate it into the aircraft’s Australian Flight Manual.

7. Document compliance and retain records

• Although the AD itself does not specify record-keeping requirements in the text provided, good practice aligned with the AD’s obligations is to document: the serial number check against the SB; copies of the SB and the issue used; maintenance records showing work performed in accordance with the SB; physical verification of flap travel limits after the work; copies of the Department-approved AFM amendment obtained from the Regional Office; and dates of compliance relative to the AD’s effective date ("with effect from 30 June 1982").

8. Verify operational procedures and crew briefing

• Ensure flight crews receive updated AFM pages and a formal briefing explaining the AFM performance changes, including the 15% landing distance increase and the 5-knot approach speed increase where applicable. Update checklists and dispatch guidance to ensure consistent operational application.

9. Ensure ongoing conformity with subsequent SB issues if relevant

• The AD’s applicability language covers serial numbers "referenced in Piper SB No. 741 or ... subsequent issues of that SB." If Piper issues further SB revisions that alter serial‑number applicability or technical instruction, check whether those subsequent issues change the aircraft’s compliance status or require additional action.

10. Observe the effective date language

• The AD states compliance must be "in accordance with the Requirement document, with effect from 30 June 1982." Ensure that records demonstrate when the SB action and AFM amendment were completed, and note that the AD’s effective date is the compliance benchmark recorded in the AD text.

The steps above are derived from the AD’s operative language: "Requirement: Action in accordance with Piper SB No. 741"; the flap travel conditional sentence; the AFM amendment approval and Regional Office availability lines; and the compliance date. Operators should rely on the SB and the Department-approved AFM amendment for the technical and wording specifics required to implement and document compliance.