AD/PC-12/52 - Elevator Control Stick-Pusher Servo-Cable Tension and Cable Clamp Bolts

The AD rests on a handful of tightly specified concepts and dependencies that determine how obligations are triggered and implemented.

Applicability: The AD applies only to a defined population of Pilatus PC‑12 airframes: MSN 101 up to MSN 888 inclusive, but expressly excludes MSN 545 (Applicability). That limits both the universe of regulated owners/operators and the set of aircraft for which the service bulletin is converted into mandatory obligations.

Reference to manufacturer service instructions and NAA approvals: Each required action is expressed as an instruction to follow specific paragraphs of Pilatus PC‑12 Service Bulletin No. 27‑018, or a later NAA approved revision (Requirement 1-4). This makes the service bulletin the operative technical standard, while permitting later revisions but only those approved by the relevant National Airworthiness Authority (NAA). The AD therefore creates a legal requirement whose technical content is located in a separate document and is subject to NAA approval for revisions.

Conditional triggers and branching remedial paths: The AD is structured around a preliminary inspection (Requirement 1) that then branches into three possible subsequent paths depending on inspection findings (Requirements 2-4). The branching logic is:

• If installation or positioning is incorrect, adjust tension (Req 2).
• If incorrect tension and/or indications of cable movement in clamps, replace affected parts per para 3.B.(4) (Req 3).
• If no signs of cable movement in the clamps, replace affected parts per para 3.B.(5) (Req 4).

Timing and flight‑limiting language: The compliance provision imposes a short horizon for the inspection (within 20 flight hours or by a calendar date) and "before further flight" language for corrective actions (Compliance). The "before further flight" phrase imposes an immediate operational constraint: affected aircraft must not be flown until the corrective measure indicated by the inspection outcome has been completed.

Causation and safety rationale in the Background: The Background states that "some operators have reported occurrences where the rear stick‑pusher cable clamp shifted forward on the elevator cable," and that the condition, if uncorrected, "may reduce the effectiveness of the stick‑pusher and/or limit elevator control movement" (Background). The AD therefore links the inspection and remedial work to a specific potential degradation of flight control effectiveness.

Reference to other regulatory instruments: The AD includes an explicit cross‑reference to EASA AD 2008‑0047 dated 28 February 2008 (Note). That indicates contemporaneous recognition of the issue by another regulatory authority and situates the AD within an international set of airworthiness actions.

Authority and signature: The AD is issued and signed by a CASA delegate, David Punshon, dated 3 March 2008. The AD itself becomes effective on 7 March 2008 (Signature; Effective date).

Together, these concepts create a mandatory, time‑bounded inspection and remediation regime for a defined aircraft fleet, the technical detail of which is delegated to a manufacturer service bulletin subject to NAA approval.

This AD directly affects owners, operators, registered keepers, and maintenance organisations responsible for the specified Pilatus PC‑12 aircraft. The applicability clause limits the regulated set to Pilatus PC‑12, PC‑12/45 and PC‑12/47 aeroplanes with Manufacturer Serial Numbers 101 through 888, excluding MSN 545 (Applicability). Any person or entity operating one of those airframes must comply with the AD’s inspection and remedial requirements.

Maintenance personnel and organisations are affected in their practical role. The AD requires an inspection in accordance with paragraph 3.B.(1) of Pilatus Service Bulletin No. 27‑018, followed where applicable by adjustment or replacement actions following specific SB paragraphs (Requirements 1-4). Because the technical steps are defined in the manufacturer’s service bulletin, the personnel performing the work must have access to, and apply, that document (or a later NAA approved revision). The text therefore creates a dependency: maintenance shops must either hold the SB or an NAA‑approved revision and be competent to apply the specified paragraphs.

Aircraft utilisation and operators’ planning are affected by the AD’s timing language. Requirement 1 must be completed within the next 20 flight hours after the AD’s effective date or by 7 April 2008, whichever is earlier (Compliance). Requirements 2-4 are all conditioned to be completed "before further flight" if their triggers arise during the inspection (Compliance). Operators must therefore plan downtime, arrange access to parts and authorised maintenance resources, and potentially accept immediate grounding until remedial actions are complete.

Parts suppliers and Pilatus as manufacturer are indirectly affected because the AD instructs replacement and adjustment per SB procedures (Requirements 2-4). The SB‑based instructions, together with the "or later NAA approved revision" phrase, create a demand for whatever parts and repair procedures the SB prescribes, and for any later NAA‑approved revisions.

Regulatory bodies are affected in the sense that the AD binds the regulated parties to the instructions and timing it sets. The AD is signed by a CASA delegate and becomes effective on 7 March 2008 (Signature; Effective date). The inclusion of a Note referring to EASA AD 2008‑0047 dated 28 February 2008 also signals coordination or parallel action with another authority (Note).

The primary payers of direct costs are the aircraft owners/operators who must fund inspection labour, possible adjustments, and the replacement parts and associated labour where required. Maintenance organisations incur labour and scheduling responsibilities. The AD does not specify funding, subsidies, or allocations; it simply imposes the inspection and corrective obligations upon the relevant parties.

Duties imposed by the AD are precise and conditional. The central duty is to carry out the inspection specified in Requirement 1: check the stick‑pusher servo‑cables for correct installation, position and tension in accordance with paragraph 3.B.(1) of Pilatus PC‑12 Service Bulletin No. 27‑018, or a later NAA approved revision (Requirement 1). That inspection must be performed within the compliance window set out in the AD (Compliance).

Subsequent duties depend on inspection findings:

• Where "incorrectly installed or positioned stick‑pusher servo‑cables are found," the obligation is to adjust the servo‑cable tension in accordance with paragraph 3.B.(2) of the SB (Requirement 2). The compliance timing for this is "before further flight after the effective date of this AD" (Compliance).
• Where the inspection finds "stick‑pusher servo‑cables... with incorrect tension and/or indications that the cables have moved in the cable clamps," the duty is to replace the affected parts in accordance with paragraph 3.B.(4) of the SB (Requirement 3), again "before further flight" (Compliance).
• Where the inspection finds "no signs... that the stick‑pusher servo‑cables have moved in the cable clamps," the duty is nevertheless to replace the affected parts but in accordance with paragraph 3.B.(5) of the SB (Requirement 4). That replacement too is required "before further flight" (Compliance).

Rights and limits implicit in the AD:

• Use of updated service instructions is permitted, but only if the revision is NAA approved. Each requirement is expressly tied to "Pilatus PC‑12 Service Bulletin No. 27‑018 or later NAA approved revision" (Requirement 1-4). This grants regulated parties the right to use later approved revisions, but not unapproved changes.
• The AD’s language does not create discretionary exemptions or alternative methods of compliance within the text. It prescribes the SB paragraphs as the method of compliance, and does not set out an in‑text mechanism for applying alternate means of compliance (for example, no AMOC provision is included in the AD text itself). Absent additional CASA guidance or established administrative pathways (not set out in this AD), the specified SB paragraphs are the required method.
• The AD stipulates specific timing windows and "before further flight" constraints. Those phrases operate as operational rights constraints: affected aircraft cannot be lawfully flown beyond the point set by the compliance language without having performed the mandated actions. The AD does not, within its text, provide temporary relief or operational exemptions.

Authority and enforcement metadata in the AD: The document is issued by CASA, signed by a CASA delegate, and contains an effective date (Signature; Effective date). The AD also contains a Note referencing an EASA AD (Note), which does not change duties but indicates related regulatory action by another authority.

In sum, the AD places direct duties on operators and maintenance organisations to inspect and then to adjust or replace parts according to specific SB paragraphs and within specific timeframes, and it confines permissible technical revisions to those approved by an NAA.

The text of this AD does not state specific penalty amounts, enforcement procedures, or administrative sanctioning mechanisms. What is present in the source is the instrument itself, signed by a CASA delegate, that converts particular maintenance inspections and corrective actions into mandatory regulatory obligations for the specified aircraft (Signature; Effective date; Requirements). As an instrument titled Airworthiness Directive, it functions as a regulatory command: affected parties must comply with the actions and timing described (Requirements; Compliance).

The AD uses timing language that creates immediate operational constraints. Requirement 1 must be completed within the next 20 flight hours after the effective date or by 7 April 2008, whichever occurs first; Requirements 2-4 must be completed "before further flight" when their conditions are triggered by the inspection (Compliance). Those time constraints give rise to a compliance boundary: aircraft subject to the AD are not to continue operations beyond those points without having completed the mandated actions. Although the AD text does not enumerate enforcement measures, breaching these obligations would, by the nature of an AD, expose the operator to regulatory non‑compliance proceedings under the broader aviation regulatory framework administered by CASA, as indicated by the issuing authority being CASA's delegate (Signature). The AD itself does not define or limit CASA’s enforcement powers or processes.

Enforcement implications drawn from the AD’s structure:

• Immediate operational grounding potential: The "before further flight" requirement effectively requires operators to ground an aircraft if the inspection reveals the specified conditions until corrective actions are completed. The AD text therefore creates a compliance trigger that, if not met, would leave the aircraft non‑compliant with the directive’s requirements.
• Reliance on SB as compliance standard: Because the AD prescribes compliance with specific paragraphs of the Pilatus SB (or later NAA approved revision), enforcement would focus on whether the inspection and corrective actions were carried out in accordance with those SB paragraphs.
• Interplay with other authorities: The AD includes a Note referring to EASA AD 2008‑0047 dated 28 February 2008 (Note). This indicates parallel action by another authority and may be relevant in cross‑jurisdictional enforcement contexts, but the AD text does not specify coordination mechanisms or enforcement arrangements with EASA.

Readers should therefore understand that the AD establishes mandatory work and timing requirements. The AD text itself does not list fines, suspension processes, or court referral procedures; any concrete penalty or enforcement action would arise from the broader regulatory system that CASA operates, rather than from provisions inside this AD. The AD serves as the regulatory standard against which compliance will be assessed.

The AD references and incorporates external technical material and situates itself alongside at least one other regulator’s action, creating a limited set of cross‑document interactions.

Primary interaction with manufacturer documentation: The AD makes mandatory specific procedures that appear in Pilatus PC‑12 Service Bulletin No. 27‑018 by explicitly requiring that inspections, adjustments and replacements be done "in accordance with" identified paragraphs of that SB (Requirement 1-4). It also permits later revisions, but only if those revisions are "NAA approved." This creates a legal relationship in which a regulatory directive delegates the detailed technical standard to a manufacturer’s service bulletin, but constrains any updates to those service instructions by a requirement of NAA approval. The AD thereby binds regulated parties to the technical content of the SB, subject to formal airworthiness authority endorsement for subsequent revisions.

Reference to another authority’s AD: The AD contains a Note that "EASA AD 2008‑0047 dated 28 February 2008 refers" (Note). That indicates contemporaneous regulatory action by the European Aviation Safety Agency. The AD does not elaborate the legal consequences of that EASA AD or harmonisation mechanisms, but the reference provides regulators, operators and maintainers a cross‑reference to a parallel instrument that addresses the same technical issue.

Operational law interaction , flight rules and airworthiness compliance: The AD imposes "before further flight" requirements for corrective actions (Compliance). That phrase operates within the operational domain: regulatory compliance with airworthiness directives is typically a condition of lawful flight. While this AD text does not quote other statutes or regulations, it functions as a binding airworthiness requirement for the affected aircraft and therefore interacts with the broader body of airworthiness and operating rules administered by CASA. The AD itself, being issued by CASA (Signature; Effective date), is part of that regulatory framework.

Interaction with NAA approval processes: The AD permits application of "later NAA approved revision" of the Pilatus SB (Requirement 1-4). That embeds NAA approval as a gatekeeper for any change to the technical method of compliance. The AD therefore interacts procedurally with National Airworthiness Authority processes that assess and approve SB revisions.

Absence of explicit alternative methods clause: The AD does not include an explicit alternative means of compliance (AMOC) clause within its text. It therefore sets the manufacturer SB paragraphs as the prescriptive compliance path without, within the AD itself, authorising alternative approved methods. Interaction with any administrative processes that permit exemptions or AMOCs would depend on CASA’s broader regulatory mechanisms, not on language contained within this AD.

In sum, the AD integrates the Pilatus SB into its compliance standard, references an EASA AD as related authority, and relies on NAA approval as the mechanism for accepting later SB revisions. It thereby creates a tightly coupled relationship between the regulator’s directive and manufacturer technical documentation, and situates the AD alongside other regulators’ instruments without specifying cross‑jurisdictional enforcement detail in the AD text itself.

The AD text provided does not include an internal amendment history. It identifies a single instrument, AD/PC‑12/52: "Elevator Control Stick‑Pusher Servo‑Cable Tension and Cable Clamp Bolts," issued as 5/2008 DM, and specifies that it "becomes effective on 7 March 2008" (Heading; Effective date). The document bears a signature block attributing it to David Punshon, Delegate of the Civil Aviation Safety Authority, dated 3 March 2008 (Signature). No later amendments, supersessions, cancellations, or historical versions are recorded in the supplied text.

The AD does, however, reference the possibility of using "later NAA approved revision" of Pilatus Service Bulletin No. 27‑018 for the technical procedures listed in Requirements 1-4. That provision implicitly acknowledges that the referenced SB may be revised after the AD’s issue and that such later revisions, if NAA approved, would be acceptable means of compliance. This creates an external channel for technical amendments to the compliance method without changing the AD’s text: the AD itself need not be amended for an NAA‑approved SB revision to alter the technical steps operators must apply, because the AD expressly allows later NAA approved revisions.

The only cross‑reference to another AD in the AD text is the Note referring to EASA AD 2008‑0047 dated 28 February 2008 (Note). That is not an amendment history entry, but it is a contemporaneous related instrument that may have its own amendment history independent of this AD. The supplied material does not include EASA AD 2008‑0047 or any subsequent tracking of revisions.

Therefore, based solely on the supplied AD text:

• No internal amendments or revisions of AD/PC‑12/52 are recorded in the document.
• The AD accepts later NAA‑approved revisions of the referenced service bulletin as permissible technical updates for compliance.
• Any amendment history would need to be sought in CASA records or subsequent ADs; the present AD does not provide such a history.

The supplied AD contains no record of litigation, appeals, judicial review, or administrative disputes arising from AD/PC‑12/52. It is a single regulatory instrument consisting of applicability, requirements, compliance timing, background, a note referring to an EASA AD, an effective date, and a signature by the CASA delegate (Applicability; Requirement 1-4; Compliance; Note; Effective date; Signature; Background).

Because the document itself contains no mention of legal challenges, case names, or proceedings, the AD provides no source‑grounded litigation history to report. Any litigation or review activity that may have occurred after issuance of the AD would not be captured in this text and therefore cannot be asserted here.

For practitioners seeking any litigation record, the AD’s absence of litigation references means the next step, not contained in the AD, is to consult CASA administrative records, court or tribunal databases, or legal reporting services to determine whether this AD was subsequently challenged, appealed or cited in judicial decisions. The AD itself gives no indication of such events.

The AD contains several features and drafting choices that create practical traps for operators, maintainers and compliance advisers if read or implemented superficially.

Narrow applicability with a single exception: The AD applies to MSNs 101 to 888 inclusive but expressly excludes MSN 545 (Applicability). Operators and registrants must check serial numbers carefully; mistakenly assuming the AD applies to all PC‑12s or failing to recognise the single exclusion could lead to unnecessary work or, conversely, non‑compliance if a covered aircraft is overlooked.

Dual‑threshold timing for the initial inspection: Requirement 1 must be performed "within the next 20 Flight Hours (FH) but not later than 7 April 2008, whichever occurs first after the effective date of this AD" (Compliance). The AD’s effective date is 7 March 2008 (Effective date). The two‑part deadline mixes flight hours with a hard calendar cut‑off. Operators must therefore track both flight hours remaining and elapsed calendar days from the effective date to determine the actual deadline. Failure to do so could mean missing a shorter flight‑hour deadline even if the calendar date is still forthcoming, or vice versa.

"Before further flight" creates immediate grounding risk: Requirements 2-4 state corrective actions must be performed "before further flight after the effective date of this AD" where their triggers arise (Compliance). Practically, if the inspection under Requirement 1 reveals any of the specified faults, the operator cannot lawfully fly the aircraft again until the adjustment or replacement specified by the SB paragraph is carried out. This can produce immediate operational disruption if parts or qualified maintenance personnel are not available.

Apparent overlap between Requirements 3 and 4: Both Requirement 3 and Requirement 4 direct replacement of "affected parts" but reference different SB paragraphs (3.B.(4) and 3.B.(5) respectively). Requirement 3 triggers where there are incorrect tension and/or indications of cable movement; Requirement 4 triggers where "no signs are detected that the stick‑pusher servo‑cables have moved in the cable clamps." Taken literally, both scenarios require replacement but with different SB procedures. Careful reading of the SB paragraphs is necessary to understand which parts or procedures each paragraph prescribes. Misreading could result in either unnecessary replacement or incomplete remedial work.

Dependence on the Pilatus Service Bulletin with NAA approval caveat: The AD directs compliance "in accordance with" specific paragraphs of Pilatus SB No. 27‑018, or a later NAA approved revision (Requirement 1-4). That creates two operational nit‑picks:

• The SB is external to the AD and must be located and matched to the cited paragraph numbers. Maintenance personnel must have the correct SB revision and ensure any later revision used is NAA approved.
• The AD does not itself provide the content of the SB paragraphs. Mis‑installation, misinterpretation or use of an unapproved SB revision could create compliance gaps.

Note referencing EASA AD: The AD includes "Note: EASA AD 2008‑0047 dated 28 February 2008 refers." (Note). The note does not explain differences or equivalence between the two ADs. Operators with aircraft registered in multiple jurisdictions need to ensure they meet the applicable obligations of each authority; the note is only a cross‑reference, not an instruction on how to reconcile potentially differing requirements.

Immediate effective date window and signature date: The AD is signed on 3 March 2008 and becomes effective on 7 March 2008 (Signature; Effective date). That is a short administrative lead time. Operators and maintainers should not assume extended notice.

Ambiguity over "affected parts": The AD repeatedly refers to replacing "the affected parts" without defining those parts within the AD text (Requirement 3-4). The definition of which parts are "affected" is located in the SB paragraphs. Failure to consult the SB could result in replacing an incorrect component set.

In short, the AD’s reliance on an external SB, its conditional branching logic, mixed timing triggers, the single MSN exclusion and its "before further flight" language are all practical gotchas that require careful administrative and technical handling.

This AD sets out a concise compliance pathway anchored to Pilatus Service Bulletin No. 27‑018. The steps, read directly from the AD text and its compliance windows, are as follows.

1. Verify applicability

   • Confirm the aircraft’s Manufacturer Serial Number is within MSN 101 to MSN 888 inclusive and that it is not MSN 545 (Applicability). Only those aircraft are subject to this AD.

2. Obtain the required service information

   • Obtain Pilatus PC‑12 Service Bulletin No. 27‑018. The AD ties each required action to paragraph references in that SB: paragraph 3.B.(1) for the inspection, 3.B.(2) for tension adjustment, 3.B.(4) and 3.B.(5) for replacement procedures (Requirement 1-4).
   • If using a revision later than SB No. 27‑018, ensure that the revision is NAA approved, because the AD permits compliance using "later NAA approved revision" only (Requirement 1-4).

3. Perform the initial inspection within the required time window

   • Execute the inspection required in Requirement 1 "within the next 20 Flight Hours but not later than 7 April 2008, whichever occurs first after the effective date of this AD" (Compliance). The AD’s effective date is 7 March 2008 (Effective date). The inspection must follow paragraph 3.B.(1) of the SB.

4. Interpret inspection findings and apply the corresponding corrective action

   • If the inspection shows incorrectly installed or positioned stick‑pusher servo‑cables, apply the tension adjustment procedure in paragraph 3.B.(2) of the SB (Requirement 2). The adjustment must be completed before further flight (Compliance).
   • If the inspection shows incorrect cable tension and/or indications that the cables have moved in the cable clamps, replace the affected parts per paragraph 3.B.(4) of the SB (Requirement 3). The replacement must be completed before further flight (Compliance).
   • If the inspection shows no signs that the stick‑pusher servo‑cables have moved in the cable clamps, replace the affected parts per paragraph 3.B.(5) of the SB (Requirement 4). That replacement, too, must be completed before further flight (Compliance).

5. Document work and retain records

   • Although the AD text does not set out record‑keeping requirements, good practice and the structure of the AD imply that maintainers should document the inspection findings, which SB revision and paragraph were used as the compliance method, any tension adjustments made, parts replaced (with part numbers and SB paragraph references), and the date and signature of the certifying maintenance person or organisation. This documentation will be necessary to evidence compliance with the AD if inspected by CASA or another authority.

6. Plan logistics and parts

   • Because corrective actions may include replacement "of the affected parts" (Requirement 3-4), operators should plan for potential parts procurement, and availability of authorised maintenance personnel capable of performing the prescribed SB procedures. Time constraints ("before further flight") mean that parts and labour availability can create operational downtime.

7. Use only NAA‑approved SB revisions where applicable

   • If a later revision of SB No. 27‑018 is available and is NAA approved, that revision may be used for compliance. Ensure formal evidence of NAA approval accompanies the SB revision applied to demonstrate the revision’s acceptance under the AD’s terms (Requirement 1-4).

8. Consider jurisdictional cross‑references

   • The AD notes that "EASA AD 2008‑0047 dated 28 February 2008 refers" (Note). If the aircraft operates across jurisdictions, confirm any additional obligations that might arise under EASA or other authorities, and ensure documentation shows compliance with all applicable directives.

9. Maintain conservative operational posture

   • Given the "before further flight" language for corrective action, do not return the aircraft to service until the specified adjustment or replacement has been completed per the SB paragraph cited for that condition.

10. Seek CASA guidance where uncertainty exists

• The AD does not provide an alternative‑means‑of‑compliance procedure within its text. If a maintainer or operator believes an alternative method is necessary or preferable, they should seek formal guidance or approval from CASA or the relevant NAA, as the AD allows only the SB paragraphs or later NAA‑approved revisions as the prescribed method (Requirement 1-4).

Following these steps will align the operator’s maintenance actions with the AD’s mandatory inspection and remedial pathways and satisfy the AD’s timing constraints as stated in the Compliance provision.