AD/HU 269/103 - Lower Coupling Drive Shaft

The AD is structured around a small set of concrete regulatory concepts: applicability, requirement, compliance timing, and the reported safety background. Applicability identifies the machines subject to the AD: Model 269A, TH55A, 269A-1, 269B and 269C helicopters (AD/HU 269/103, Applicability). Requirement converts a manufacturer's service action into the mandatory action by reference, stating: "Unless previously carried out action in accordance with Schweizer SB B-257-1" (AD/HU 269/103, Requirement). The compliance provision translates the requirement into temporal constraints: initial action to occur within 100 hours time in service from a stated baseline date (15 January 1994) or by a calendar date (15 April 1994), whichever occurs first; and thereafter reinspections at intervals not exceeding 300 hours time in service, with the inspection to be performed "in accordance with Part I of the requirement document" (AD/HU 269/103, Compliance). The Background entry identifies the operational failure mode prompting the AD , lower coupling drive shaft damage from engine overspeed during start up , establishing the safety rationale that underpins the directive (AD/HU 269/103, Background). Ancillary notes signal inter-jurisdictional coordination and prior action: the AD notes that Model 269C helicopters S/N 1628 and subsequent were delivered with Part I already incorporated, and that the FAA AD 93-17-13 Amdt 39-8684 is referred to (AD/HU 269/103, Note). Conceptually, the AD operates by mandating inspections aimed at identifying cracking in a specified component, using a manufacturer-provided inspection procedure as the normative method; it imposes a schedule that combines an accelerated initial compliance window with longer-term periodic surveillance. The AD’s mechanics therefore convert a specific failure risk , drive shaft cracking from overspeed , into a recurring maintenance duty with a clearly defined technical reference (Schweizer SB B-257-1 and Part I of the requirement document) and explicit temporal parameters.

The AD directly affects owners, operators, maintenance organisations and certificated maintenance personnel responsible for the listed Schweizer (Hughes) 269 series helicopters in the Australian jurisdiction. The Applicability clause names the specific helicopter models: 269A, TH55A, 269A-1, 269B and 269C (AD/HU 269/103, Applicability). Practically, the obligation to "carry out action in accordance with Schweizer SB B-257-1" and to "reinspect the drive shaft for cracking in accordance with Part I of the requirement document" falls on the party who holds responsibility for maintenance and continuing airworthiness of the aircraft; that will be the registered operator or an agent acting under their authority. The AD also distinguishes a sub-set of aircraft by serial number: Model 269C helicopters serial number 1628 and subsequent "were delivered from the factory with Part I of the Requirement document incorporated," which means those airframes may already have received the design or installation change contemplated in the requirement document and therefore may not need the initial action (AD/HU 269/103, Note). Entities that source spare parts, perform maintenance planning, maintain maintenance records, or certify aircraft as serviceable will need to incorporate the inspection and record-keeping steps the AD implies; the AD requires an initial inspection within a tight window linked to flight hours or a calendar date, and ongoing reinspections at not more than 300-hour intervals, which will affect scheduling of maintenance visits and aircraft availability (AD/HU 269/103, Compliance). The AD also affects procurement and logbook review processes that maintenance organisations or purchasers use to establish compliance histories, because the Requirement clause is conditional on whether the Schweizer SB B-257-1 action has "previously [been] carried out" (AD/HU 269/103, Requirement), so prior maintenance actions must be established in the aircraft’s records to determine whether the AD’s mandates are owed.

Duties

• Perform initial action: The AD requires that, unless already done, action be carried out "in accordance with Schweizer SB B-257-1" (AD/HU 269/103, Requirement). The AD makes the manufacturer’s Service Bulletin the operative method for the required work.
• Meet the initial deadline: The AD imposes a time-limited initial duty: "Within 100 hours time in service from 15 January 1994 or by 15 April 1994, whichever occurs first" (AD/HU 269/103, Compliance). The initial check therefore cannot be deferred beyond either the flight-hour threshold or the calendar date.
• Reinspect at fixed intervals: The AD requires subsequent reinspections "at intervals not exceeding 300 hours time in service" and specifies that inspections are to look for cracking of the drive shaft "in accordance with Part I of the requirement document" (AD/HU 269/103, Compliance).

Rights and conditional exemptions set out in the text

• Pre-completed work exception: The Requirement clause is explicit: the AD’s action requirement applies "Unless previously carried out action in accordance with Schweizer SB B-257-1" (AD/HU 269/103, Requirement). If operators can demonstrate that the SB action has already been completed, the immediate action will not be required.
• Factory incorporation exception for certain serial numbers: The AD specifically notes that "Model 269C helicopters S/N 1628 and subsequent were delivered from the factory with Part I of the Requirement document incorporated" (AD/HU 269/103, Note). For those airframes, the distributor/manufacturer modification may already exist, which changes the application of the Requirement and Compliance steps for that subset.

Practical duties that follow from the document

• Record-keeping: While the AD does not specify record formats, the Requirement and Compliance text make a practical duty to maintain sufficient maintenance records to show whether Schweizer SB B-257-1 has been previously carried out and to demonstrate completion of initial and recurring inspections in accordance with Part I.
• Use of specified procedure: The AD makes the specified Service Bulletin and Part I of the requirement document the controlling procedural references; compliance should be demonstrated by following those procedures as they are the ones named by the AD (AD/HU 269/103, Requirement; Compliance).

The AD text itself does not state rights of appeal or alternative methods of compliance. It frames the duty by direct reference to the manufacturer’s bulletin and the requirement document, and it makes the temporal parameters for compliance mandatory.

The AD text supplied does not include provision for penalties or a description of enforcement mechanisms. The document is an entry in the Commonwealth of Australia Civil Aviation Safety Authority Schedule of Airworthiness Directives (AD/HU 269/103), and it sets mandatory technical and temporal requirements , the Requirement and Compliance clauses specify what action must be taken and when , but the AD content as provided contains no express section describing sanctions for non-compliance, no administrative enforcement process, and no criminal penalties. The AD also does not specify mechanisms for seeking an alternative means of compliance, exemptions, approvals, or relief from the nominal requirements; it simply states the required action and intervals, with narrow conditional language for previously completed manufacturer action and a serial-number-based factory incorporation exception (AD/HU 269/103, Requirement; Note; Compliance). Because the AD text is silent on enforcement and sanctions, an operator or maintenance organisation reading the AD should treat the Requirement and Compliance clauses as mandatory instructions to be met, but the AD itself offers no statutory wording about fines, certificate suspension, or specific enforcement steps. The only enforceable content in the document as presented is the technical obligation and its timing. For regulators or third parties seeking to know enforcement consequences, the AD does not state them; any enforcement procedure or penalty would have to be identified from other regulatory authorities or instruments outside the text provided. The AD’s silence on enforcement is therefore a practical limitation in the document: it prescribes duties and timings but does not describe the sanctioning framework or an explicit administrative path for approvals of alternative compliance approaches.

The AD is explicitly presented as part of the Commonwealth of Australia Civil Aviation Regulations 1998 administrative framework; the header identifies it as an entry in the "SCHEDULE OF AIRWORTHINESS DIRECTIVES" under the Civil Aviation Safety Authority (AD/HU 269/103). It therefore operates as a regulatory instrument within that administrative domain. The AD itself references an equivalent United States authority action, stating "FAA AD 93-17-13 Amdt 39-8684 refers" (AD/HU 269/103, Note). That reference indicates coordination or equivalence with a foreign regulator’s airworthiness directive, and suggests the AD’s content is aligned with the FAA’s prior determination concerning the same failure mode on the same equipment. The AD also embeds a manufacturer’s Service Bulletin into its operative requirement: the Requirement clause compels action "in accordance with Schweizer SB B-257-1" and the Compliance clause requires reinspections "in accordance with Part I of the requirement document" (AD/HU 269/103, Requirement; Compliance). The document thereby creates an interaction where regulatory compliance is achieved by following manufacturer-issued technical instructions. The AD’s reference to factory incorporation for certain serial numbers (269C S/N 1628 and subsequent) also creates an interaction between the aircraft’s production configuration and the AD’s applicability in practice (AD/HU 269/103, Note). The AD as provided does not identify or define how it interacts with other statutory provisions, such as administrative penalty regimes, alternative means of compliance processes, or continuing airworthiness obligations beyond the scope of the named requirement; those interactions must be determined by reference to other instruments and statutory provisions not included in the text supplied. In short, the AD links regulatory obligation to a manufacturer service bulletin and references an FAA AD for congruence, but it does not explicitly state how it modifies, supersedes, or co-exists with other statutory penalty or approval mechanisms in the regulatory corpus within the text supplied.

The AD document itself contains limited internal amendment metadata. It is titled and dated as "AD/HU 269/103 Lower Coupling Drive Shaft 1/94," which indicates the AD’s issuance within the period associated with 1994 and marks it as the first AD in that year for this subject (AD/HU 269/103 Lower Coupling Drive Shaft 1/94). The Compliance clause sets baseline dates for inspection timing referencing 15 January 1994 and a calendar deadline of 15 April 1994 (AD/HU 269/103, Compliance). The AD also includes a cross-reference to a United States Federal Aviation Administration action: "FAA AD 93-17-13 Amdt 39-8684 refers" (AD/HU 269/103, Note). Within the AD text, the only internal modification recognition is the note that certain Model 269C helicopters with serial number 1628 and subsequent "were delivered from the factory with Part I of the Requirement document incorporated," which functions as an in-effect change in applicability for those serial numbers because the factory action relieves those airframes from the AD’s initial action requirement insofar as Part I is already incorporated (AD/HU 269/103, Note). The AD makes no explicit statement about subsequent amendments, rescissions, supersessions, or revisions to the AD itself. It also does not include a record of prior versions or earlier AD numbers other than the FAA reference. Therefore, the only amendment-relevant facts recorded within the provided text are the AD identifier and issuance year, the compliance baseline dates, the manufacturer SB reference, and the FAA cross-reference. Any formal amendment history, such as later updates or revocations, is not recorded within the supplied AD text and would need to be verified against an external AD register or the Civil Aviation Safety Authority's published AD history.

The AD as supplied contains no reference to litigation, court decisions, appeals, or disputes. The document is a procedural safety directive: it specifies a maintenance action, inspection intervals, and related notes, and it records the safety background and a cross-reference to an FAA AD (AD/HU 269/103, Background; Note). There is no mention of administrative reviews, judicial challenges, civil suits, enforcement actions or case law within the text provided. Consequently, the AD does not supply any litigation history that could inform legal arguments or challenge strategies. Any legal disputes arising from the AD’s application, such as disagreements about whether prior work satisfies the "previously carried out action" exception, disagreements as to compliance methods, or enforcement proceedings, are outside the scope of the AD text as supplied. To establish a litigation record, an analyst would need to consult external legal databases or the regulator’s administrative records; the AD document itself contains no litigation references or outcomes.

Several practical traps and points of potential ambiguity are visible directly in the AD text and are important for operational compliance and legal certainty.

1. Dual-trigger initial deadline. The Compliance clause sets two alternative triggers for the initial inspection: "Within 100 hours time in service from 15 January 1994 or by 15 April 1994, whichever occurs first" (AD/HU 269/103, Compliance). Operators must apply the earlier of a flight-hours threshold measured from a baseline date and a hard calendar deadline. Misreading this could lead to missing the earlier obligation.

2. Dependency on manufacturer documents. The Requirement and Compliance clauses make compliance contingent on following external documents: Schweizer SB B-257-1 and "Part I of the requirement document" (AD/HU 269/103, Requirement; Compliance). The AD does not reproduce those documents, so compliance requires obtaining and following the correct editions and parts. Uncertainty about which revision of the SB or which version of Part I applies is a practical compliance risk, because the AD names them but does not give version dates or document identifiers beyond the SB number.

3. Proof of prior compliance. The AD exempts aircraft where the specified SB action has "previously [been] carried out" (AD/HU 269/103, Requirement). Operators must be able to demonstrate that earlier work met the SB’s requirements. Incomplete or ambiguous maintenance records could leave an aircraft technically non-compliant even if a relevant action was performed.

4. Serial-number carve-out nuances. The AD notes that "Model 269C helicopters S/N 1628 and subsequent were delivered from the factory with Part I of the Requirement document incorporated" (AD/HU 269/103, Note). For any Model 269C, verifying the airframe serial number and whether the factory incorporation actually addressed the same Part I content becomes a precise factual question. Misinterpretation of the serial number range or reliance on incorrect delivery records may lead to unnecessary work or compliance risk.

5. No express alternative compliance pathway in the text. The AD does not set out an administrative process for obtaining an alternate method of compliance or a waiver in the supplied text. If an operator believes a different inspection technique is equivalent, the AD does not provide the procedure to record an approved alternative within the document itself.

6. Lack of enforcement detail. The AD does not state enforcement mechanisms or penalties in the supplied text. Operators cannot rely on the AD alone to understand possible sanctions or administrative outcomes for non-compliance; such information must be sought from separate regulatory instruments.

7. Narrow technical focus. The AD targets the lower coupling drive shaft and specifically "cracking" due to "engine overspeed during start up" (AD/HU 269/103, Background). Other related failure modes or associated components are not addressed in the AD; operators should not infer broader obligations from this narrowly worded directive.

8. Inter-jurisdictional reference. The mention of the FAA AD (FAA AD 93-17-13 Amdt 39-8684) provides a cross-reference but does not automatically import FAA provisions. Users must avoid assuming that the FAA AD’s text or compliance mechanisms are embedded in this AD unless corroborated by the Australian regulator.

These gotchas show that compliance requires careful document control, serial-number verification, maintenance record review and a precise application of the temporal triggers in the Compliance clause.

The AD specifies a narrow, document-linked compliance path. Follow these steps, using the AD language as the operative guide.

1. Establish applicability. Confirm whether the aircraft is one of the listed models: 269A, TH55A, 269A-1, 269B or 269C (AD/HU 269/103, Applicability). Record the aircraft model and serial number to determine whether the serial-number note applies for 269C airframes.

2. Check maintenance history for prior SB compliance. Determine whether Schweizer SB B-257-1 has "previously [been] carried out" on the aircraft (AD/HU 269/103, Requirement). If proof of proper completion of SB B-257-1 exists in the approved maintenance logs and matches the SB content, the initial mandatory action may be satisfied. Keep documentary evidence linking the performed work to the SB and the specific Part I content referenced by the AD.

3. Obtain the controlling documents. Obtain Schweizer SB B-257-1 and Part I of the requirement document referred to by the AD. The AD makes those documents the authoritative procedural references for the required inspections and remedial actions (AD/HU 269/103, Requirement; Compliance). Ensure the correct revision of the SB and Part I is used; if the AD does not specify a revision, use the edition that corresponds to the time of the AD or the edition referenced by regulators, and keep a record of the exact document used.

4. Perform the initial action within the AD window. If the SB action has not been previously completed, perform the work "in accordance with Schweizer SB B-257-1" within the AD’s initial time limits: "Within 100 hours time in service from 15 January 1994 or by 15 April 1994, whichever occurs first" (AD/HU 269/103, Compliance). Document the date, aircraft Hobbs or tachometer time, and the particulars of the inspection/repair performed per the SB and Part I.

5. Implement the recurring inspection regime. After the initial compliance action, reinspect the drive shaft for cracking "at intervals not exceeding 300 hours time in service" and in the method specified by Part I of the requirement document (AD/HU 269/103, Compliance). Incorporate this interval into the aircraft’s maintenance schedule and ensure maintenance planners account for the 300-hour interval as an ongoing item.

6. Record outcomes precisely. Log each inspection, findings, corrections, part replacements, and the technician signature and certifying authority. The AD’s exemption for prior work and the tight initial deadline make documentary proof essential to demonstrate contemporaneous compliance.

7. For Model 269C S/N 1628 and subsequent, verify factory incorporation. For those serial-numbered aircraft, confirm that Part I of the requirement document was indeed incorporated at delivery as the AD records (AD/HU 269/103, Note). Establish in the records the factory incorporation documentation to avoid redundant work.

8. Coordinate with organisational maintenance control. Ensure maintenance control and continuing airworthiness management incorporate the AD’s inspection intervals into the preventative maintenance programmes so aircraft are not flown past the 300-hour inspection interval.

9. Cross-reference the FAA AD. The AD notes that FAA AD 93-17-13 Amdt 39-8684 refers; operators seeking additional technical detail may consult that FAA AD for comparative guidance, while relying on the Australian AD as the binding local requirement (AD/HU 269/103, Note). When using external material, document the local AD as the source of mandatory obligation.

10. Retain evidence for regulator engagement. Because the AD itself does not set out enforcement or alternative compliance procedures in the supplied text, if operators anticipate needing an alternative method or relief, they should prepare a documented technical case showing equivalency to the SB and Part I inspection methods so that engagement with the regulator or its authorised delegates can be supported by explicit evidence.

Adherence to these steps follows strictly from the AD’s Requirement and Compliance clauses and the AD’s note about serial-number factory incorporation. The AD makes the manufacturer’s SB and Part I the controlling methods; compliance therefore consists of obtaining and executing those precise documents within the timeframes the AD sets and keeping contemporaneous records.