AD/SD3-30/49 - Engine and Landing Gear Control Cables

The AD rests on a small set of concrete technical and regulatory concepts drawn from the source text.

• Applicability: limited to Short Brothers PLC SD3‑30 aeroplanes (Applicability). The AD does not purport to cover other Short Brothers types or derivatives; the scope is the SD3‑30 fleet specifically.

• Affected component: cable assembly end fittings of type MS21260 fitted to cable‑operated control systems, including propeller RPM and LP fuel lever cables as explicitly reported (Background). The failure mode was first identified on these end fittings.

• Failure mechanism: Bombardier Shorts’ examinations are cited as the source’s root‑cause finding: stress corrosion cracking of SAE‑AISI 303 stainless steel, initiated by pitting corrosion on the surface, with the stress corrosion resulting from sustained tensile stress in a corrosive (warm, humid and salty) atmosphere (Background). The AD links the observed cracking and pitting to an environmental and load condition common to the fleet.

• Safety rationale: the AD asserts that “a number of potentially unsafe conditions” have been identified across cable‑operated control systems that use MS21260 end fittings, and that these could result from a common‑mode cause (Background). The technical finding and the potential for multiple failures are advanced as the safety justification for the mandated inspections and replacements.

• Reference documents and authority: the inspection and replacement tasks are to be performed in accordance with Short Brothers PLC Service Bulletin SD330‑76‑A09 Revision 1 (or later EASA‑approved revisions) for initial inspections, and SB SD360‑76‑A09 Revision 1 (or later EASA‑approved revisions) for inspections of new cable assemblies (Requirements 1 and 4). The AD also refers to an EASA Emergency AD 2007‑0039‑E dated 16 February 2007 (Note).

• Timing and intervals: the AD sets a short initial compliance deadline (no later than 9 March 2007) for the first inspection (Compliance 1), mandates recurring inspections at intervals not to exceed 12 months where no defect is found (Compliance 2), requires replacement before further flight if defects are found (Compliance 3), and sets a repeat interval for any new cable assembly end fittings of “after replacement at intervals not to exceed 15 years” (Compliance 4). These intervals create a mixed cadence of short‑term (annual) and very long‑term (15 year) inspection obligations.

• Regulatory provenance: the AD is issued under the authority of the Civil Aviation Safety Authority (CASA) in Australia and signed by a CASA delegate (David Punshon) on 20 February 2007; it becomes effective 23 February 2007.

These concepts map technical findings into concrete mandated maintenance actions, tie the actions to manufacturer service bulletins and EASA approvals, and establish explicit timing constraints.

The AD names a narrow class of regulated parties and a broader set of stakeholders who will be affected by the directive’s requirements.

• Operators of Short Brothers PLC SD3‑30 aeroplanes: the core duty‑bearers are aircraft operators who have SD3‑30 aeroplanes in their fleet. The Applicability section explicitly limits the AD to Short Brothers PLC SD3‑30 aeroplanes; all other duties and compliance dates apply to those operators.

• Maintenance organisations and licensed engineers: persons and organisations responsible for performing inspections and replacements must apply the procedures specified in the referenced Short Brothers service bulletins (Requirement 1 and Requirement 4). The AD presumes technical capability to inspect MS21260 end fittings for pitting, corrosion and cracking and to perform replacement where defects are found.

• Parts suppliers and manufacturers: Bombardier Shorts (referred to in the Background) supplied the examinations and service bulletins. The AD requires compliance with the manufacturer’s SBs or later EASA‑approved revisions; thus Bombardier Shorts and any authorised repair organisations are affected because supply of replacement cable assemblies and the content of service bulletins determine practicable compliance.

• Civil Aviation Safety Authority (CASA): CASA is the issuing authority; the AD was signed by a CASA delegate and sets the effective date. Although the AD text does not set out enforcement provisions, CASA’s role is implicit as regulator issuing the directive.

• Flight operations planners and scheduling: the Compliance requirements can affect aircraft availability. If an inspection reveals pitting/corrosion/cracking, the affected cable assembly must be replaced “before further flight” (Requirement 3; Compliance 3), which can impose ground time and parts logistics for operators.

• Insurers and lessors: while not mentioned in the AD, any party with an economic stake in the airframe’s operability (lessors, insurers) will be affected by mandated inspections and the risk of prolonged grounding if replacement parts are not available. The AD text, however, does not state any obligations for insurers or lessors.

• EASA and European oversight: the AD references an EASA Emergency AD and conditions compliance on “EASA approved revision” of service bulletin revisions. This makes EASA’s approvals relevant to Australian operators if they adopt later SB revisions.

Particular characteristics of the affected group: the AD affects all SD3‑30 operators regardless of operation size; the cost of compliance will be borne by those operators and the maintenance chain. The AD applies irrespective of whether the specific aircraft have previously exhibited symptoms; the initial inspection deadline applies fleet‑wide for the type specified.

The AD imposes specific duties on operators and maintenance personnel; it does not set explicit rights beyond following the prescribed procedures.

Duties (explicit in the AD text)

• Conduct the initial inspection: Operators must inspect the affected cable assembly end fittings in accordance with Short Brothers PLC SB SD330‑76‑A09 Revision 1 or later EASA‑approved revision. The compliance deadline is “no later than 9 March 2007” (Requirement 1; Compliance 1).

• Repeat inspection when no defects found: If the initial inspection reveals no pitting, corrosion or cracking, the operator must repeat the inspection “within 12 months of the original inspection and thereafter at intervals not to exceed 12 months” (Requirement 2; Compliance 2). This creates an annual inspection duty for fittings that pass inspection.

• Replace if defects are found: If pitting, corrosion or cracking is found during any inspection, the operator must “replace the affected cable assembly with a new cable assembly.” The Compliance section requires replacement “before further flight after the effective date of this AD” (Requirement 3; Compliance 3). This establishes a before‑flight grounding obligation for aircraft with defective fittings.

• Inspect new assemblies: After replacement, operators must “repeat the inspection of any new cable assembly end fittings in accordance with Short Brothers PLC SB SD360‑76‑A09 Revision 1 or later EASA approved revision” (Requirement 4). The Compliance text adds that this is to occur “after replacement at intervals not to exceed 15 years” (Compliance 4).

• Use approved SB revisions: The AD ties required work to the named service bulletin revisions or later EASA‑approved revisions. Compliance is conditional on the SB revision being EASA‑approved.

Rights and practical constraints (as derived from the AD text)

• Right to follow a later EASA‑approved SB revision: the AD allows operators to comply with either the specified SB revision or a later revision provided it is EASA‑approved. This provides a controlled route for operators to use updated procedures developed by the manufacturer, subject to EASA approval.

• Implicit operating constraint: replacement is required “before further flight” when defects are found; therefore operators have no discretion to defer replacement beyond returning the aircraft to service.

• No express alternative methods of compliance (AMOCs) are stated in the AD: the text does not provide a process for gaining an alternate compliance method; operators must use the referenced SB or later EASA‑approved revisions. The AD also does not specify a waiver or special flight permit mechanism in its text; the only operational remedy in the instrument itself is replacement before further flight.

• No express instruction on recordkeeping or reporting in the AD text: the AD does not spell out reporting obligations, logbook entries, or retention periods for inspection records. Where operators must fulfil other statutory recordkeeping duties, those would depend on the broader regulatory regime, but they are not set by the AD itself.

Operational consequences of the duties

• Inspection cadence imposes recurrent maintenance planning (annual inspections when fittings are clear, immediate replacement when defects are found).

• Replacement obligations potentially create immediate grounding costs and parts procurement needs; the AD requires replacement before further flight without providing a deferred compliance option in the text.

• Compliance is tied to manufacturer documentation and EASA approval, which means operators cannot unilaterally change procedures without resort to EASA‑approved revisions or implicit CASA directions outside of this AD.

The AD text itself contains no explicit penalty clauses, fines, or enforcement mechanisms. The document records the issuing authority and effective date, but it does not set out sanctions or specify enforcement steps in this text.

What the source does state

• Issuing authority and delegate: The AD is signed and dated by David Punshon, Delegate of the Civil Aviation Safety Authority, on 20 February 2007, and it states that the AD becomes effective 23 February 2007. This assigns regulatory provenance to CASA and indicates that the directive is an enforceable regulatory instrument issued by that authority.

• Mandatory nature: By the AD’s wording,commands such as “Inspect”, “replace”, and set compliance deadlines,the obligation is presented as compulsory for the identified applicability. The AD format and phrasing conventionally indicate a mandatory regulatory obligation rather than guidance.

What is not in the source

• Specific penalties: The AD contains no provisions specifying civil penalties, criminal offences, administrative sanctions, or infringement notice amounts for non‑compliance. It does not specify a process for CASA enforcement actions, suspension of operations, or imposition of conditions.

• Compliance monitoring or reporting: The AD does not describe a reporting mechanism back to CASA, nor does it set out audit or inspection arrangements by CASA staff.

What to infer (bounded to the source)

• The presence of an AD issued by CASA, combined with its mandatory language and effective date, signals that compliance is expected by the regulator; however, the AD text does not itself specify enforcement instruments. Where enforcement exists, it is not recorded in this AD and would derive from the broader regulatory framework under which CASA operates, which is not reproduced in this text.

• Operators should therefore treat the AD as a mandatory requirement for the specified aeroplanes and assume that failure to comply may expose them to regulatory consequences under applicable aviation law, even though this particular instrument does not itemise those consequences.

Readers should note the absence of explicit enforcement detail in the AD and not assume any specific penalty amounts or processes from this text alone.

The AD references external regulatory and manufacturer documents and thus interacts with other instruments by incorporating or deferring to them.

Direct references in the AD text

• EASA Emergency AD 2007‑0039‑E dated 16 February 2007: The AD includes a note stating that the EASA Emergency AD 2007‑0039‑E dated 16 February 2007 is referred to. That establishes a cross‑jurisdictional linkage where the Australian AD recognises an EASA emergency measure as relevant background (Requirement note).

• Service Bulletins and EASA approval: The AD requires compliance with Short Brothers PLC Service Bulletin SD330‑76‑A09 Revision 1 for initial inspections, and SB SD360‑76‑A09 Revision 1 for inspections of new assemblies, and in both cases allows “or later EASA approved revision.” This makes effective compliance contingent on the content of service bulletins and any later EASA approvals. In practice, this ties the AD’s technical requirements to manufacturer documents and to EASA’s approval process.

Implications for regulatory interaction

• The AD does not attempt to displace EASA’s role; rather, it incorporates EASA approval as the gating condition for later SB revisions. This means that any updated procedures that the manufacturer publishes must be EASA‑approved before they become acceptable under this AD text, linking Australian compliance to a European approval process for SB revisions.

• The AD’s cross‑reference to an EASA Emergency AD suggests harmonisation or mutual recognition on technical safety issues; operators with internationally registered aircraft or those operating across jurisdictions should take both the CASA AD and the referenced EASA AD into account.

• No mention of other domestic statutory instruments: The AD does not reference other Australian aviation statutes, civil penalties regimes, or recordkeeping laws. It also does not provide an explicit mechanism for alternative methods of compliance or approval by CASA within the text.

Practical consequences for operators

• Operators must source and use the specified Short Brothers SBs and check whether later revisions have EASA approval in order for those later revisions to be acceptable under this AD. That creates dependence on the manufacturer and on EASA’s revision approvals.

• Because the AD refers to EASA documentation, operators who are accustomed to relying only on domestic documentation should ensure they track EASA ADs and SB approvals.

Limitations in the instrument’s cross‑references

• The AD does not provide copies of the EASA AD or the SBs, nor does it spell out what to do if there is an inconsistency between the SB and the AD. It does not specify an alternative process for CASA to approve an alternate method of compliance where the SB is not followed.

In short, the AD explicitly interacts with EASA emergency measures and with Short Brothers’ service bulletins, making EASA approval a condition for using later SB revisions under the AD, but it does not otherwise codify how it sits within wider domestic regulatory enforcement regimes.

The AD text contains a limited, specific amendment and identification record. The source documents the following items relevant to history and versioning:

• AD identification: AD/SD3‑30/49, listed as 4/2007 TX. The AD appears as a single instrument referencing that number and date.

• Issue and signature: The AD is signed by David Punshon, Delegate of the Civil Aviation Safety Authority, and dated 20 February 2007.

• Effective date: The AD becomes effective on 23 February 2007 (explicit statement in the table under Compliance).

• Service bulletin revisions referenced: The AD mandates compliance with Short Brothers PLC Service Bulletin SD330‑76‑A09 Revision 1 for initial inspections and SD360‑76‑A09 Revision 1 for inspections of new cable assembly end fittings, while allowing “or later EASA approved revision.” This provides a mechanism for amendment of the practical inspection procedure without amending the AD itself, subject to EASA approval of later SB revisions.

• Cross‑reference to EASA Emergency AD: The AD expressly refers to EASA Emergency AD 2007‑0039‑E dated 16 February 2007 as a related document.

What the AD does not contain about amendments

• The AD text does not record any prior versions of the AD; it presents a single issuance dated February 2007. No subsequent revisions, supersessions, cancellations, or amendment entries are included in the provided text.

• The AD does not include a formal amendment or revocation clause for future modification by CASA, nor does it specify how operators will be notified of AD amendments. It simply allows later EASA‑approved SB revisions to be used for compliance.

Practical effect

• The AD’s reliance on SB revisions being EASA‑approved provides a pathway for the technical content of required actions to change without the AD being reissued, because later EASA‑approved SB revisions are automatically acceptable. That is the only embedded amendment mechanism visible in the text.

• Stakeholders needing to know whether procedures have been amended must therefore monitor both the manufacturer’s SB revision history and EASA approvals; the AD itself does not track those revisions beyond naming the revision numbers current at issuance.

The supplied AD text contains no litigation history, court decisions, internal appeals, or challenges. It does not cite any judicial or administrative proceedings concerning the AD, the manufacturer, or the technical findings.

What the source records

• No cases: The AD does not name any court cases or legal challenges.

• No appeals process described: The AD does not include an administrative appeals mechanism or describe any process for disputing the AD’s requirements within the text.

What to read from the absence

• The absence of litigation history in this text means there is no record, within this document, of legal disputes about the AD’s validity, interpretation, or enforcement. It is silent on whether any affected party sought review.

• If a practitioner requires information about litigation arising from this AD, they must consult external legal databases, CASA records, or court registries because the AD itself provides no history.

Readers should treat the AD as a regulatory instrument with no litigation context contained in this source document.

The AD contains several features and textual inconsistencies that can create compliance risk, confusion, or implementation overhead if not noticed and clarified.

1. Apparent typographical inconsistency in SB numbering

• Requirement 1 references Short Brothers PLC Service Bulletin SD330‑76‑A09 Revision 1, while Requirement 4 references SB SD360‑76‑A09 Revision 1. The AD uses SD330 in one place and SD360 in another. The AD text does not explain whether this is an intentional reference to two different bulletins or a typographical error. Operators must verify which SB applies for initial inspections and which applies for inspections of replacement assemblies with the manufacturer or CASA before acting (Requirement 1; Requirement 4). Relying on the wrong SB could lead to non‑conforming inspections.

2. Mixed inspection intervals that can appear inconsistent

• The AD requires annual repeat inspections where no defect is found (Compliance 2: “within 12 months … and thereafter at intervals not to exceed 12 months”), but sets a very long interval for new cable assemblies (“after replacement at intervals not to exceed 15 years,” Compliance 4). This creates a potential interpretive issue: does Compliance 4 mean that the first inspection of a new assembly is at once and then again only every 15 years, or that a special inspection regime applies after replacement? The AD itself does not clarify how annual inspections under Compliance 2 interact with the 15‑year interval in Compliance 4 for new assemblies. Operators should seek clarification in writing from CASA or the manufacturer to establish the intended cadence for replaced assemblies.

3. “Before further flight” replacement obligation

• If pitting, corrosion or cracking is found, the AD requires replacement “before further flight” (Requirement 3; Compliance 3). That phrase leaves little operational flexibility and implies aircraft grounding until the replacement is effected. Operators must therefore have logistical plans to obtain replacement assemblies quickly and competent maintenance resources available.

4. Reliance on EASA approval for later SB revisions

• The AD permits compliance with “later EASA approved revision[s]” of the SBs. Operators must check whether a later SB revision exists and whether it is EASA‑approved. Where the manufacturer issues a new revision that has not yet been EASA‑approved, the AD’s allowance for later revisions will not apply. That creates an administrative burden: tracking EASA approvals as well as SB issuance.

5. Limited detail on inspection method in the AD text

• The AD requires inspection “in accordance with” the named SBs but does not reproduce or summarise the inspection techniques, acceptance criteria, or tooling requirements. Operators who do not have immediate access to the SBs cannot perform the inspections based on the AD text alone.

6. No express reporting requirement for findings

• The AD does not require operators to report findings of pitting, corrosion or cracking to CASA or the manufacturer. However, the Background shows Bombardier Shorts received reports and conducted examinations. Operators should note the absence of a reporting obligation in the AD text and check other regulatory obligations or manufacturer instructions about reporting occurrences.

7. Applicability is limited to SD3‑30

• The AD explicitly limits applicability to Short Brothers PLC SD3‑30 aeroplanes. Operators of other SD3 variants should not assume coverage. Conversely, operators should confirm that the installed fittings on their SD3‑30 variants are indeed the MS21260 type listed as the problem part.

8. Material and environmental description is technical and narrow

• The Background identifies the material (SAE‑AISI 303 stainless steel) and the contributory environment (warm, humid and salty). Operators in dry climates should nevertheless comply because the AD does not provide exemptions based on operating environment, and earlier instances were identified during ground maintenance.

9. Timing pressure from short initial compliance deadline

• The AD’s effective date is 23 February 2007 and the initial inspection deadline is “no later than 9 March 2007,” giving operators a short window. Practically, this can create supply chain and scheduling pressure, particularly where operators have multiple aircraft or limited maintenance capacity.

Spotting these gotchas and resolving ambiguities (SB numbering, interval interplay, and treatment of later SB revisions) with CASA and the manufacturer is necessary to minimise legal and operational risk.

This section provides a step‑by‑step, source‑grounded checklist drawn from the AD text. Follow the AD’s Requirements and Compliance statements exactly, and resolve ambiguities with CASA or the manufacturer where indicated.

1. Confirm applicability

• Verify that the aircraft is a Short Brothers PLC SD3‑30 aeroplane (Applicability). If the aircraft is not an SD3‑30, this AD does not apply.

2. Obtain the required service bulletins and approvals

• Obtain Short Brothers PLC Service Bulletin SD330‑76‑A09 Revision 1 and Short Brothers PLC Service Bulletin SD360‑76‑A09 Revision 1 (as referenced). Also determine whether any later SB revisions exist and if those later revisions are EASA‑approved because the AD permits use of later “EASA approved revision[s]” (Requirement 1; Requirement 4). If there is any uncertainty about SB numbering (see Gotchas), confirm with Bombardier Shorts and CASA which SB applies to initial and post‑replacement inspections.

3. Schedule and perform the initial inspection by the AD deadline

• The initial inspection must be performed “no later than 9 March 2007” (Compliance 1). Conduct the inspection of the affected cable assembly end fittings in accordance with SB SD330‑76‑A09 Revision 1 or an applicable later EASA‑approved revision (Requirement 1). The inspection should specifically look for pitting, corrosion or cracking of the MS21260 end fittings as described in the Background.

4. Follow the AD’s defect actions

• If the inspection finds pitting, corrosion or cracking, replace the affected cable assembly with a new cable assembly. The AD requires replacement “before further flight after the effective date of this AD” (Requirement 3; Compliance 3). Do not return the aircraft to service with the defective part installed.

5. Repeat inspections as required

• If no defects are found on initial inspection, repeat inspections must occur within 12 months of the original inspection and thereafter at intervals not to exceed 12 months (Requirement 2; Compliance 2). If you replace an assembly, perform inspections of the new cable assembly end fittings in accordance with SB SD360‑76‑A09 Revision 1 or later EASA‑approved revision (Requirement 4). Note the AD’s Compliance 4 wording that these repeats occur “after replacement at intervals not to exceed 15 years”; seek clarification if there is potential conflict with the annual interval requirement for other fittings.

6. Use only EASA‑approved later SB revisions where specified

• If you plan to comply using a later revision of either SB, confirm that the revision is EASA‑approved. The AD only allows “later EASA approved revision[s]” for the SBs it names (Requirement 1; Requirement 4). Do not assume that a later manufacturer revision is acceptable unless it has EASA approval as required by the AD.

7. Plan for parts procurement and maintenance capacity

• Because replacement is required before further flight if defects are found, maintain inventory or supply channels for MS21260‑fitted cable assemblies or authorised replacement parts. Ensure maintenance personnel are trained on the SB inspection procedures. The AD’s Background indicates failures were identified during ground maintenance; however, inspections must be carried out as required by the AD schedule.

8. Resolve textual ambiguities proactively

• Two potential ambiguities in the AD require confirmation: a) SB numbering: SD330 versus SD360 discrepancy (Requirement 1 vs Requirement 4). Confirm which SB is the correct reference for initial and replacement inspections. b) Inspection interval interplay: reconcile Compliance 2 (annual) with Compliance 4 (15‑year interval for replaced assemblies). Obtain written clarification from CASA or the manufacturer about the intended inspection cadence for replaced assemblies.

9. Document compliance actions in aircraft maintenance records

• While the AD does not specify reporting or record requirements, standard maintenance practice dictates making logbook entries and retaining inspection and replacement records. Operators should document the inspection dates, findings (no defects or description of pitting/corrosion/cracking), the SB revision used for inspection, and details of any replacement part installed (part number, serial number if applicable).

10. Monitor EASA and manufacturer communications

• Track EASA ADs (including the referenced EASA Emergency AD 2007‑0039‑E) and Bombardier Shorts’ SB revision history, as later EASA‑approved SB revisions are acceptable under this AD. Ensure any revised procedures are EASA‑approved before using them for compliance.

11. Seek regulatory advice where necessary

• For any uncertainties about acceptable inspection methods, deviation requests, or interaction with operational scheduling, obtain written guidance from CASA or an authorised delegate. The AD’s mandatory language and “before further flight” replacement requirement make written regulatory confirmation advisable in contested scenarios.

Following these steps will satisfy the specific, source‑stated obligations of the AD as it appears in the provided text. If practitioners require further legal certainty about enforcement or interactions with other regulatory obligations, consult CASA directly and preserve written approvals.