AD/SD3-60/23 Amdt 2 - Rudder Gust Lock

The AD rests on a few tightly defined concepts that determine its scope and operational effect.

• Applicability by serial number and model. For SB SD360-27-16 (Part 1) the AD applies to “all models S/Nos SH3601 to SH3715 as applicable.” For SB SD360-27-21 (Part 2) the AD applies to “all models.” The AD therefore distinguishes between a serial-number-limited cohort (Part 1) and a universal cohort for Part 2. Those precise applicability lines are the primary determinant of whether an individual aeroplane falls within the AD’s reach.

• Action by reference to manufacturer documentation. The AD’s requirement is expressed as “Action in accordance with: Part 1: Shorts SB SD360-27-16 and Part 2: Shorts SB SD360-27-21.” The AD does not set out the technical corrections within its text, it makes performance of the manufacturer’s procedures the compulsory mechanism for achieving compliance.

• Compliance deadlines. The AD fixes two separate deadlines: actions required under Part 1 must be completed “Prior to 31 January 1988,” while actions required under Part 2 must be completed “Prior to 30 September 1988.” The dual deadlines create a temporal staging for compliance tasks, and indicate urgency differences recognised by the issuing authority.

• Problem identification and causal pointer. The AD sets out the background factual justification: prior damage to the rudder control system from wind gust and jet blast led to the initial directive, and further reports of unsolicited gust-lock engagement were attributed to inaccurate adjustment of microswitch WM2. The AD therefore connects two failure modes , external aerodynamic/propulsive input and an internal component adjustment error , to the need for the mandated corrective work.

• Scope of remedy. While the AD requires action, it leaves the technical remedy to the content of the service bulletins. That means the AD’s remedial scope is only as detailed as those SBs. The AD’s text does not specify whether the actions are inspections, re-adjustments, replacements, modifications, or other engineering changes. The reader must consult SB SD360-27-16 and SB SD360-27-21 to see the specific interventions.

These concepts show that the AD is a compliance-by-reference instrument targeted at a defined subset of Short SD3-60 aeroplanes, with prescribed deadlines and a clear technical justification focusing on the rudder gust lock and microswitch WM2 adjustments.

The AD’s applicability language identifies the physical objects to which it applies, and, by necessary implication for regulatory effect, the persons and entities who must act.

• Aircraft operators and owners of the specified Short SD3-60 series aeroplanes. The AD’s Applicability clause covers “All models S/Nos SH3601 to SH3715 as applicable” for Part 1 and “All models” for Part 2. That means each aeroplane with a serial number falling within the stated range, and each aeroplane of the covered models in the Part 2 cohort, is subject to the directive. In practical terms, legal responsibility for ensuring compliance will fall on whichever party bears regulatory obligations for the airworthiness of the aircraft at the time , typically the registered owner, operator, or maintenance organisation authorised to certify the aircraft’s airworthiness.

• Maintenance organisations and licensed engineers. Because the AD requires actions “in accordance with” specified Shorts service bulletins, those carrying out the work will need access to the relevant SBs and the personnel or organisation licensed to implement them. The AD presumes the technical competence and procedural authority to perform whatever adjustments, inspections, modifications, or replacements the SBs require.

• Fleet managers and compliance officers. For entities operating multiple Short SD3-60 aircraft, the AD imposes discrete scheduling obligations tied to the compliance deadlines. Fleet-level tracking systems, maintenance planning, and record-keeping will be affected to ensure each applicable aeroplane has the AD action completed before the applicable date.

• Aviation regulators and oversight bodies. Although the AD itself does not detail enforcement mechanisms, it is issued under the Civil Aviation Regulations 1998, Part 39. That places the AD within the regulatory architecture the Civil Aviation Safety Authority administers. Regulators will therefore be concerned with ensuring compliance records and audit trails are produced for the affected fleet.

• Third-party stakeholders. Less directly affected but still implicated are lessors, insurers and purchasers who rely on the aircraft’s airworthiness status. An aircraft subject to an outstanding AD is not compliant with the specific regulatory requirement until the mandated action is carried out, which may affect commercial transactions, insurance coverage, or leasing conditions.

The AD does not identify individual persons by name; rather it addresses classes of legal actors linked to the aircraft. The core burden lies with whoever is responsible to maintain the aircraft’s airworthiness and to order, supervise, or perform the referenced service-bulletin actions before the set deadlines.

The AD imposes a clear set of duties by making performance of specific manufacturer service bulletin actions mandatory and by fixing compliance dates. The AD text itself specifies neither discretionary exemptions nor rights such as appeals in its brief wording; it therefore functions as a precise directive with a small number of explicit duties and implied procedural effects.

Duties

• Perform actions in accordance with the referenced Shorts service bulletins. The central duty is to carry out the actions described in SB SD360-27-16 (Part 1) and SB SD360-27-21 (Part 2). The AD does not paraphrase these actions, it makes adherence to the SBs the required route to compliance.

• Observe applicability constraints. Operators must determine whether their aeroplane falls within the AD’s stated applicability , for Part 1 by serial number range (SH3601 to SH3715, “as applicable”) and for Part 2 by model (all models). Determining applicability is an upstream duty affecting whether the AD applies.

• Meet the compliance-by dates. For relevant aircraft, the duty is to complete the Part 1 action before 31 January 1988 and the Part 2 action before 30 September 1988. Those deadlines are absolute in the AD text; the AD does not provide transitional or phase-in arrangements beyond the two dates.

Implied procedural duties

• Obtain and follow the service bulletins. Because the AD references the SBs for technical detail, the duty includes acquiring those SBs, ensuring personnel understand them, and executing their instructions.

• Maintain records demonstrating compliance. Although the AD text does not expressly require record-keeping, regulatory practice (and the AD’s placement in the schedule) implies that operators will need to show the AD action has been completed to satisfy oversight or commercial requirements.

Rights and limitations

• The AD text does not state rights of appeal, deferral, or alternative method of compliance within the document. It likewise does not set out remedial obligations beyond executing the SBs. Any formal rights to seek an alternative method of compliance, extension, or review are not contained in this instrument and would, if available, be found in the broader regulatory framework (Civil Aviation Regulations 1998, Part 39) or in the regulator’s procedural rules rather than in the AD text.

• The AD does not specify who pays; it prescribes technical action but not cost allocation. Cost liability therefore remains a commercial and contractual matter among owners, operators, lessors, and maintainers. The AD creates a compliance cost to the responsible parties but does not itself assign that cost.

In sum, the AD’s operative content is focused and duty-driven: if an aeroplane falls within the stated applicability, its responsible parties must carry out the SB-specified work before the dates set out. The text does not elaborate procedural rights or alternative compliance mechanisms.

The AD itself does not include any penalty provisions or an enforcement schedule in its text. The instrument is a Schedule entry under “COMMONWEALTH OF AUSTRALIA (Civil Aviation Regulations 1998), PART 39 , CIVIL AVIATION SAFETY AUTHORITY SCHEDULE OF AIRWORTHINESS DIRECTIVES,” which places the directive within the regulatory regime that gives rise to enforceable airworthiness requirements. The AD sets mandatory technical requirements and compliance-by dates but does not, in the document provided, identify sanctions, infringement notices, or the specific enforcement measures that will be applied for non-compliance.

What is present in the document

• Mandatory corrective action and dates. The AD prescribes actions “in accordance with” Shorts SB SD360-27-16 and SB SD360-27-21, and it fixes deadlines (prior to 31 January 1988 for Part 1; prior to 30 September 1988 for Part 2). Those firm specifications convert the SB instructions into regulatory obligations for the affected aeroplanes.

What is absent from the document

• No express penalty clause. The AD does not specify fines, grounding directives, licence consequences, or criminal sanctions for non-compliance in the text provided.

• No explicit enforcement procedure. The AD does not set out how compliance will be audited, who will inspect aircraft records, nor does it name the administrative mechanism for enforcement action.

Implications and practical enforcement considerations

• Enforcement will be exercised within the broader civil aviation regulatory framework under which the AD is issued. Because the AD appears in the CAR 1998 Part 39 schedule, enforcement, sanctions, and processes are likely governed by the Civil Aviation Regulations and the Civil Aviation Safety Authority’s enforcement policy and powers, but the AD text does not specify those links.

• Operators and owners should treat the AD as a mandatory regulatory instrument notwithstanding the absence of penalty language in the AD text. The presence of compliance dates and the AD’s scheduling within the Part 39 framework indicate that non-compliance would place an aircraft outside the AD’s required airworthiness actions.

• For contractual and insurance purposes, the lack of explicit penalties in the AD does not remove commercial or contractual consequences that may attach to an aircraft operating without required AD work being done. The AD’s mandatory nature, the deadlines, and the technical justification create risk for operators who do not perform the specified actions.

In short, the AD mandates compliance but, within its own words, does not articulate enforcement or penalty mechanisms; those will be situated in the regulatory framework that produced the AD rather than in the AD entry itself.

The AD is presented as a schedule entry under the Commonwealth Civil Aviation Regulations 1998, Part 39, and is issued by the Civil Aviation Safety Authority. That placement signals the AD’s role as a regulatory instrument within the statutory aviation safety framework. The AD does not, however, reference other statutes, regulations, or instruments beyond identifying the regulatory context (Civil Aviation Regulations 1998, Part 39) in its header.

Direct interactions apparent from the text

• Regulatory source. The AD’s header explicitly ties it to the Civil Aviation Regulations 1998, Part 39. That links the directive to the statutory and regulatory regime governing airworthiness directives, implying that obligations arising from the AD should be interpreted alongside Part 39 obligations and the CSA’s administrative processes. The AD itself does not restate Part 39 provisions; it simply appears as a Schedule entry.

• Manufacturer documentation as binding technical norm. By prescribing action “in accordance with” specified Shorts service bulletins, the AD converts the content of those SBs into a regulatory obligation. The effect is to align manufacturer-prescribed technical standards with regulatory requirements. The AD therefore functions as a legal bridge that brings manufacturer maintenance instructions within the regulatory compliance universe.

Absent or unstated interactions

• No cross-reference to other ADs or regulatory instruments. The AD does not cite other airworthiness directives, no other CAR sections, and it does not indicate supersession, amendment, or interaction with other ADs in the schedule. If there are pre-existing ADs affecting the same systems or aircraft, those relationships are not set out in this text.

• No express link to licensing or civil liability provisions. The AD does not mention pilot licensing, operator certification, or civil liability regimes. Any effect the AD has on operator approvals, maintenance release authority, or insurance is not articulated in the AD; it would arise through the wider regulatory and contractual framework.

Operational consequences for compliance

• Compliance with the AD will require alignment of maintenance practice with the SBs named. Organisations must therefore ensure that their maintenance procedures, certificates of release to service, and record-keeping reflect the AD obligations. That alignment can affect other regulatory obligations, such as continuing airworthiness management, but these interactions are not detailed in the AD itself.

• Because the AD is cast as a schedule entry under Part 39, the natural legal interaction is that the AD’s command becomes an enforceable expectation within the CAR 1998 framework. The AD’s absence of detailed enforcement language does not isolate it from the regulatory system; rather it relies on the underlying regulatory architecture to supply the enforcement and compliance oversight mechanisms.

In summary, the AD interacts with other laws principally by being an instrument within the Civil Aviation Regulations 1998, Part 39 regime and by making manufacturer service bulletins compulsory for affected aircraft. Specific cross-references, enforcement provisions, or interactions with other statutory regimes are not specified in the document itself.

The AD carries the label “AD/SD3-60/23 Amdt 2” and the title line includes “Rudder Gust Lock 8/88.” Those elements in the document provide the limited history visible within the text.

• Amendment numbering. The presence of “Amdt 2” indicates this entry is the second amendment to the AD identified as AD/SD3-60/23. The AD text does not reproduce the prior amendment language, nor does it reproduce the original AD in full. The mere fact of amendment two signals at least one prior modification to the directive.

• Date indicator. The title includes “8/88,” which appears to function as a dating convention (month/year) commonly used in airworthiness directive schedules. The AD’s compliance dates likewise reference calendar dates in 1988. Taken together these imply the AD and its amendments were issued and/or updated in 1988.

• Stated reason for amendment. The AD provides a concise narrative of why the amendment was promulgated. It states that the original Requirement (Part 1) was prompted by damage to the rudder control system from wind gust and jet blast. It then records that, subsequently, there were reports of unsolicited engagement of the rudder gust lock; investigation attributed those incidents to inaccurate adjustment of microswitch WM2. The amendment therefore responds to new incident reports and an identified root cause (WM2 adjustment) not apparently covered, or not fully resolved, by the original action. The amendment form suggests the second amendment updates the AD to require additional or revised action (Part 2 SB SD360-27-21) to address the microswitch issue.

• Content changes implied by amendment. The AD’s two-part structure , Part 1 referencing SB SD360-27-16, Part 2 referencing SB SD360-27-21 , suggests the amendment added or clarified the Part 2 requirement. The wording indicates that Part 1 was the original requirement and that further action (Part 2) was introduced after reports about microswitch WM2. The AD text, however, does not reproduce the pre-amendment wording, so precise textual differences between the original AD and Amdt 2 are not available in the document.

• Lack of detailed amendment chronology. The AD does not include a full amendment log, amendment dates, or a revision table. It simply identifies itself as Amendment 2 and gives the two service-bulletin references and compliance dates. To reconstruct a more granular amendment timeline would require consulting prior versions of the AD schedule or records held by the issuer, which are not part of the provided text.

In short, the AD’s amendment history as presented is succinct: it is Amendment 2, dated in 1988, and it responds to new safety reports pointing to an adjustment problem with microswitch WM2 that required action beyond the original directive.

The AD contains no information about litigation, appeals, prosecutions, or judicial review related to its issuance, content, or enforcement. The document is a schedule entry and includes only the directive text, applicability, required actions by reference to two Shorts service bulletins, the compliance deadlines, and a brief background describing the safety events that motivated the requirement.

What the document shows

• No cases named. The AD does not cite judicial decisions, tribunal determinations, or precedent.

• No recorded disputes or appeals. There is no mention in the text of formal challenges to the AD, requests for alternative means of compliance, or any administrative appeals process specific to this directive.

What to infer from the absence

• Absence of litigation history in the AD does not necessarily mean there were no legal proceedings associated with the AD in practice. The AD simply does not record litigation or disputes. Any litigation involving the AD would be recorded in external legal or administrative records, not within the AD entry itself.

• For readers seeking whether this AD has been subject to court consideration or enforcement action, the AD text provides no material. Any such litigation history must be obtained from external legal databases, CSA records, or court archives.

Therefore the document itself contains no litigation history or references to judicial matters; it is a regulatory instruction without embedded legal proceeding information.

The instrument’s brevity and reliance on external service bulletins create a number of practical and legal pitfalls that the AD text itself reveals or implies. These are concrete implementation, compliance, and administrative issues an affected party should note.

• Compliance-by dates are historical and absolute. The AD sets actions “Prior to 31 January 1988” for Part 1 and “Prior to 30 September 1988” for Part 2. Those are absolute dates in the AD. Operators must verify records to demonstrate whether the actions were completed before those dates. For aircraft still in service or changing hands, the historical compliance status is a material fact. Failure to have completed the work by the specified dates places the aircraft in the state the AD identified as unsafe, and the AD text does not specify remedial grace periods.

• Applicability language requires precise serial-number verification. Part 1 applies to “All models S/Nos SH3601 to SH3715 as applicable.” That phrase requires the operator to determine if their specific airframe configuration or modification state makes the SB applicable. There is a risk of misreading “as applicable” and incorrectly concluding the AD does not apply. Operators should not rely solely on model descriptions without verifying serial numbers and the SB applicability criteria.

• Two different service bulletins, two different scopes. The AD makes compliance contingent on two SBs identified as Part 1 and Part 2. Without the SB texts attached, an operator cannot know from the AD whether the required work is an inspection, adjustment, replacement, or modification, nor whether the SBs contain optional or conditional steps. The AD’s instruction to “Action in accordance with” the SBs means compliance is only as effective as the operator’s interpretation and execution of those SBs.

• Root cause points to an adjustment issue. The AD’s background identifies inaccurate adjustment of microswitch WM2 as a cause of unsolicited engagement of the gust lock. That narrows the technical locus of the problem to an adjustable component. The gotcha here is that microswitch adjustment is a calibration task that can be sensitive to tooling, technician skill, and measurement tolerances. The AD does not specify acceptable tolerance bands or verification procedures in its text; those details live in the SBs. If maintenance records do not document the calibration method and final settings for WM2, later operators cannot verify the adequacy of the remedy.

• No express follow-up or monitoring requirement in the AD text. The AD does not set periodic inspections or recurring checks; it mandates the SB actions by the dates given. If the SBs implement a one-off fix, the AD does not require verification audits or recurring monitoring in its own text. This creates an implementation risk where a one-off corrective action may not be sufficient if the adjustment drifts over time, but that question is not addressed in the AD itself.

• Record evidence burden. Because the AD sets past dates, proving compliance now depends on maintainers’ historical records. The AD does not specify the form those records must take. Missing or ambiguous records create legal and operational exposure for owners and operators.

• Lack of enforcement detail may be misleading. The AD contains no penalty provisions or explicit enforcement mechanics, which might lead some to underestimate the regulatory consequences of non-compliance. The directive is nonetheless a regulatory instrument under Part 39, and absence of penalty wording in the AD does not equate to absence of enforcement under the wider regulatory framework.

• Potential commercial impacts. For transactions involving affected aircraft (sales, leases), the AD’s requirements and their compliance status materially affect marketability and warranties. The AD does not address how compliance status should be transferred or certified on sale or lease, so parties must handle that as a separate contractual and regulatory matter.

Overall, the main operational gotchas are (1) the need to verify precise applicability and historic compliance dates, (2) the necessity of obtaining and following the exact SBs cited, and (3) ensuring calibration/adjustment work on microswitch WM2 was performed, recorded and verified to the standards required by the SBs, none of which are reproduced in the AD text.

The AD prescribes compliance by reference to two manufacturer service bulletins and sets firm completion dates. Compliance therefore consists of a sequence of practical steps grounded in the AD’s text.

1. Determine applicability precisely. Check the aircraft’s serial number against the Part 1 range, SH3601 to SH3715, to see whether Part 1 applies, and confirm whether Part 2 applies (the AD states Part 2 applies to “All models”). The AD’s Applicability clause is the starting point for compliance.

2. Acquire the referenced service bulletins. The AD requires action “in accordance with” Shorts SB SD360-27-16 (Part 1) and SB SD360-27-21 (Part 2). Compliance requires possession of those specific SBs and any associated manufacturer drawings or amendments that inform the SBs’ procedures. The AD itself does not reproduce the technical instructions, so operators must obtain the SBs from Shorts (the manufacturer) or the regulatory library.

3. Implement the SB procedures before the stated deadlines. The AD makes the SB actions compulsory and sets two deadlines: SB SD360-27-16 work must be completed before 31 January 1988 and SB SD360-27-21 work must be completed before 30 September 1988. Where an aircraft falls within either or both parts’ applicability, the corresponding SB instructions must be executed prior to the relevant date.

4. Ensure qualified personnel and authorised maintenance. Because the AD’s actions are technical and involve components such as microswitch WM2, perform the work using personnel, tooling and facilities authorised by applicable regulatory licences and approvals. The AD’s technical remediation will generally require maintenance personnel capable of making precise adjustments and issuing maintenance release documentation.

5. Document the work comprehensively. The AD’s requirements will be evidenced by maintenance records. Document the SB revision used, the date of completion, the identity and qualifications of the person performing the work, the specific actions taken (including settings, measurements, part numbers installed or replaced), and any certification or release-to-service statements made. Since the AD sets historic deadlines, robust records are necessary to prove compliance.

6. Verify microswitch WM2 adjustment. The AD background identifies inaccurate adjustment of microswitch WM2 as a cause of unsolicited engagement. Ensure that the SB procedures for WM2 adjustment have been followed, that the final settings are recorded, and that any functional tests specified by the SBs are completed and recorded.

7. Audit and retain evidence for regulatory and commercial purposes. Given that the AD contains no enforcement text, enforcement will be effected within the civil aviation framework. Keep records available for inspection, and ensure transfer documents on aircraft sale or lease reflect the AD compliance status.

8. If information gaps exist, obtain clarification from the regulator or manufacturer. The AD does not include the SB content; if an operator cannot locate the SBs or if the SBs leave technical uncertainties, the operator should obtain authoritative clarification from the manufacturer or the regulator. The AD itself does not provide alternative compliance routes or extensions.

9. Consider fleet-wide tracking. For operators with multiple Short SD3-60 aircraft, integrate this AD’s requirements into maintenance management software and compliance tracking to ensure no airframe is overlooked.

These steps flow directly from the AD’s language: applicability by serial number and model, the requirement to perform actions “in accordance with” two named Shorts service bulletins, and the need to meet the two specified compliance dates. The AD places the technical detail and verification burden on the SBs and on the entity performing the work.