AD/PC-6/31 - Wing Strut Internal Corrosion - Inspection

Primary affected parties are operators, owners and maintenance providers associated with Pilatus Porter PC-6 series aeroplanes, except those built under Fairchild Hiller production. The Applicability clause,"All models except Fairchild Hiller production",defines the set of aircraft that bear the inspection duty. That typically means the registered operator or owner of each applicable airframe must ensure the inspections are carried out in the prescribed timeframe.

Maintenance organisations and aircraft maintenance engineers who carry out structural inspections will be operationally affected because they must perform or supervise the internal inspection of the wing strut per Pilatus SB No. 105 and meet the 100-hour cadence. The directive’s reliance on a manufacturer service bulletin as the operative technical document creates a direct role for those who hold or can access Pilatus SB No. 105.

Registrars, continuing airworthiness managers and operators’ maintenance planners will also be affected because they must schedule recurring inspections measured in hours time in service and ensure that the first inspection occurred within the window defined relative to 31 August 1971. The historical effective date means that the requirement is intended to be applied retrospectively from that date, so parties responsible for historical maintenance records and logbooks need to verify compliance from that point forward.

Indirectly affected parties include any lessees, hirers, or future purchasers of affected aircraft. Prospective buyers, for example, will need to verify that the inspection cadence has been observed. The AD does not set out who bears the monetary cost, but the natural economic incidence is on the registered owners and operators who must procure inspection labour, any required access equipment, and any remedial work that arises from inspection findings. The source does not allocate costs or identify funding mechanisms; it simply prescribes the maintenance action and interval to be observed by those responsible for the airworthiness of the applicable aircraft.

The AD’s core duty is an inspection obligation: conduct the wing strut internal corrosion inspection "within 100 hours time in service after 31 August 1971 and thereafter at intervals not exceeding 100 hours time in service" (Compliance). That duty is framed temporally and recurringly. The AD further directs the obligated parties to use the manufacturer’s service bulletin as the technical means by which to carry out the inspection, by naming "Pilatus SB No. 105" as the Document.

Within the supplied source text there are no other explicit duties such as mandatory repair methods, mandatory reporting to the regulator, or recordkeeping obligations. The AD does not, in the provided material, articulate rights of appeal, relief, alternative compliance methods, or exemptions. Accordingly, the only express duty recorded in the AD as supplied is to perform the inspection at the specified interval following the procedures in Pilatus SB No. 105.

Because the AD refers to an external service bulletin for technical content, a practical duty for affected parties is to obtain and apply Pilatus SB No. 105. The AD does not state whether deviation from the service bulletin is permissible, nor whether approved alternative procedures or equivalent levels of safety will be considered acceptable. Those considerations will typically be governed by broader regulatory frameworks or by approvals issued by the competent authority, but no such mechanisms or rights are set out in the supplied AD text.

Rights to contest, seek relief, or rely on alternative compliance are not mentioned in the document excerpt provided. Any such rights would need to be sought in the broader Civil Aviation Regulations or through administrative processes of the Civil Aviation Safety Authority or other competent bodies; they are not found within the AD text as presented.

The supplied text for AD/PC-6/31 contains no penalties, monetary fines, suspension clauses, or enforcement procedures. The AD sets out the inspection requirement and the referenced technical document, but it does not specify what enforcement measures will follow non-compliance, nor does it enumerate civil or criminal penalties within the document itself.

The header indicates the AD is published in the Civil Aviation Safety Authority portion of the Schedule of Airworthiness Directives under the Civil Aviation Regulations framework. That placement signals that enforcement, certification consequences, or other regulatory follow-up would be governed by the broader statutory and administrative mechanisms that apply to airworthiness directives and continuing airworthiness in that regulatory framework. However, those enforcement mechanisms, penalty schedules, or procedural steps are not articulated in the AD excerpt supplied, so no specific enforcement steps can be attributed to the AD text itself.

Practically, the absence of explicit penalties in the AD text means that interested parties must look to the overarching regulatory scheme for enforcement detail. Records or audit findings showing failure to perform required inspections could result in administrative consequences (such as grounding, regulatory notices, or certificate actions) under other provisions of the Civil Aviation Regulations, but those outcomes are not specified in this AD’s text. The AD’s content focuses narrowly on technical compliance timing and the technical reference; it does not, on its face, address enforcement modalities.

The AD appears in a schedule associated with the Civil Aviation Regulations and the Civil Aviation Safety Authority. This situates it within the broader statutory framework governing aircraft airworthiness, maintenance, and continuing airworthiness obligations. The AD’s explicit reference to Pilatus SB No. 105 integrates manufacturer technical guidance into the regulatory requirement, creating a linkage between regulatory obligations and manufacturer-prescribed maintenance procedures.

Because the AD is limited in text to a required inspection and a referenced service bulletin, operators must treat this directive as an additional, model-specific continuing airworthiness obligation to be honoured alongside any general maintenance, inspection or airworthiness duties found elsewhere in the Civil Aviation Regulations or related regulatory instruments. The AD does not replace broader maintenance duties; it sets a specific discrete duty applicable to the defined aircraft cohort that sits alongside other regulatory obligations.

The AD’s exclusion of "Fairchild Hiller production" models creates a point of interaction with aircraft identification and certification records. Determining whether a particular airframe falls within the AD’s applicability requires cross-referencing production lineage, type certification data, or manufacturer designation. That determination will, in practice, involve interactions between the AD and records or certifications maintained under other statutory or administrative requirements.

Because the AD relies on Pilatus SB No. 105 for technical content, any conflicts, gaps, or inconsistencies between that service bulletin and other technical documents (for example, maintenance manuals, structural repair manuals, or airworthiness limitations) will need to be resolved by reference to the governing regulatory rules on acceptable data and approved maintenance procedures. The AD itself does not resolve such potential conflicts; it simply points to the SB as the operative reference for the inspection task it prescribes.

The supplied material gives a date marker "7/71" associated with the AD number AD/PC-6/31 and specifies a compliance trigger relative to "31 August 1971". The AD’s wording indicates an initial inspection deadline "within 100 hours time in service after 31 August 1971", which implies the AD was issued or intended to be effective in 1971. The only explicit historical data in the source is that 31 August 1971 date and the AD identifier with the 7/71 notation.

No subsequent amendments, superseding directives, or revocation language are present in the supplied text. The AD does not contain any amendment history lines, amendment dates, or references to later ADs that modify or withdraw it. To establish whether the directive has been amended, superseded, or revoked after the date shown would require consulting the consolidated Schedule of Airworthiness Directives or later regulatory records; such material is not included in the supplied text.

Therefore, as provided, the AD stands as a single directive with an initial effective timeframe tied to 31 August 1971 and a recurring inspection interval. The absence of amendment notes in the text supplied should be treated as an absence of amendment information, not as confirmation that none exists elsewhere. Any current legal status, amendments, or supersessions must be verified against the authoritative maintained record of airworthiness directives, which is not part of the supplied document.

The supplied AD/PC-6/31 text contains no references to litigation, court decisions, administrative appeals, or precedent. There are no mentions of any disputes, enforcement actions, or contested proceedings related to this directive in the provided material. The directive itself is a short, operational safety prescription and does not include any litigation-related content.

Because no litigation history is included in the document, one cannot infer from this text whether the AD has been subject to challenge, whether its legal validity was tested, or whether interpreting issues around applicability, compliance timing, or the content of Pilatus SB No. 105 have been litigated. Any such litigation or administrative determinations would need to be identified by consulting case law databases, tribunal records, or regulator enforcement archives. Those materials are not part of the supplied source and therefore cannot be reported on here.

In the absence of litigation details, readers should treat the AD as a regulatory instrument whose operational reach is confined to the inspection duty expressed in the supplied text and whose enforcement and contested history, if any, must be researched in external legal or regulatory records.

Several practical and interpretive traps arise from the AD’s terse drafting and reliance on an external service bulletin. First, the applicability phrase "All models except Fairchild Hiller production" can be ambiguous in application when an aircraft’s production lineage is not clear from available records or when modifications have been made. Determining whether a specific airframe is within scope may require examination of manufacturing records, type certificates, or chassis serial numbers, none of which are provided or specified in the AD text.

Second, the AD refers to "Pilatus SB No. 105" as the Document. The AD supplies no content from the service bulletin itself and does not summarise inspection procedures, pass/fail criteria, or mandated corrective actions. Operators must obtain and follow SB No. 105 to understand how to inspect and what to do if corrosion is found. Without that bulletin, the AD provides only timing instructions and a pointer to the procedure, which is an incomplete compliance picture.

Third, the timing formulation raises operational questions. The AD requires inspection "Within 100 hours time in service after 31 August 1971 and thereafter at intervals not exceeding 100 hours time in service." The AD prescribes a first inspection relative to a historical date. For aircraft that accumulated more than 100 hours after that date prior to the operator reviewing the AD, it will be necessary to determine whether the first inspection was already overdue as of that date and, if so, to take remedial action consistent with the SB or regulatory guidance. The AD does not provide grace periods or transitional arrangements.

Fourth, the AD contains no guidance about corrective action or acceptable corrosion levels. If corrosion is detected, the AD does not set out mandatory repair standards or re-inspection intervals following repair. That absence obliges operators to rely on Pilatus SB No. 105, other approved data, or regulator direction to determine appropriate follow-up work, which can create uncertainty if Pilatus SB No. 105 itself is silent on certain details.

Fifth, the AD does not specify reporting obligations. If the regulator expects defect reports or service difficulty reports following inspections, that expectation is not articulated in the AD excerpt. Operators should not assume that no reporting is required; they should check broader regulatory reporting obligations and the content of Pilatus SB No. 105.

Sixth, the AD does not mention allowable methods of compliance or whether alternative means of compliance require prior approval. The absence of explicit alternative compliance pathways requires operators who seek to deviate from Pilatus SB No. 105 to consult the regulator or the applicable regulatory framework for permitted alternatives.

Finally, the AD’s age and dated compliance trigger suggest that historical compliance verification will rely heavily on archival maintenance logs and records. For older aircraft, records may be incomplete or lost, potentially complicating determination of compliance and the demonstration of continuing airworthiness. The AD’s terse text provides no assistive procedures for retrospective compliance verification.

The AD’s compliance steps are narrowly defined in the supplied text. A workable compliance process based on the AD and its references would include the following concrete actions.

1. Identify applicability. Review the aircraft’s type and production lineage to confirm whether it is a Pilatus Porter PC-6 series airframe and whether it is excluded by the AD as "Fairchild Hiller production". This identification should be made from manufacturer data plates, type certification information, and production records. The AD’s Applicability clause controls this step.

2. Obtain Pilatus SB No. 105. The AD names Pilatus SB No. 105 as the Document. Acquire the specific service bulletin and review its inspection procedures, tooling, acceptance criteria, and any stated corrective actions. The AD does not reproduce SB No. 105, so compliance requires access to that bulletin.

3. Schedule and perform the first inspection. The AD requires the inspection "Within 100 hours time in service after 31 August 1971". Practically, ascertain the aircraft’s time-in-service cumulative hours as at 31 August 1971 and ensure the first inspection occurred within the 100-hour window after that date, or arrange for an inspection as soon as possible if the first inspection was not conducted as required. In all future operations, schedule inspections at intervals "not exceeding 100 hours time in service". That is, once the first inspection is completed, the next inspection should be at or before a further 100 hours of time in service elapses.

4. Perform inspections per Pilatus SB No. 105. Follow the procedures, access methods, inspection tools and non-destructive testing processes set out in the service bulletin. If the SB specifies pass/fail criteria, apply those criteria; if it specifies mandatory repairs, apply them or seek regulator-approved alternatives.

5. Decide and execute remedial actions. If internal corrosion is identified, carry out remedial actions in accordance with Pilatus SB No. 105 or other approved repair data. If the SB leaves discretion to the engineer, then record the basis for any repair decisions and ensure repairs are done to an approved standard.

6. Document actions. Although the AD text does not specify recordkeeping, good continuing airworthiness practice requires maintaining entries in the aircraft maintenance logbooks recording the inspection dates, hours time in service at inspection, who performed the inspection, findings, and any corrective actions undertaken. These records will be necessary to demonstrate compliance in audits and to prospective buyers or lessors.

7. Verify future compliance scheduling. Implement tracking controls in maintenance planning systems to flag inspections at or before the 100-hour interval so that inspections are not missed. Since the AD requires intervals "not exceeding 100 hours time in service", schedule inspections conservatively to allow for operational variability.

8. Consult the regulator for ambiguities. For questions about applicability, acceptable alternative procedures, reporting obligations, or remedial actions not spelled out in the AD or SB No. 105, seek clarification or approval from the Civil Aviation Safety Authority or the applicable national competent authority because the AD itself does not address alternative compliance methods.

Who pays and who decides. The registered owner/operator is economically responsible for procuring inspections and repairs; maintenance organisations and engineers decide and perform the technical inspection and repairs in accordance with Pilatus SB No. 105 and any applicable approvals. Any decision to adopt an alternative means of compliance or to seek exemptions must be taken through the regulator’s established processes, as the AD itself does not grant such alternatives.

Timing and operational impact. The 100-hour recurring interval will impose recurring maintenance windows. Operators should plan for the labour, access equipment and potential downtime associated with internal strut inspections and any follow-up repairs. If the inspection uncovers significant corrosion necessitating structural repair, expect longer grounding times. The AD offers no mitigation for those operational impacts; managing them is part of continuing airworthiness planning.

In sum, compliance requires: correctly identifying applicability, obtaining and following Pilatus SB No. 105, performing the initial and recurring 100-hour inspections, executing repairs per the SB or approved data, and maintaining appropriate records to document that the inspection cadence has been observed.