AD/HU 369/117 - Tail Rotor Blade Root Fitting

The AD rests on a small set of operationally significant concepts, each of which is defined or referenced in the text and the attached service bulletin material. These concepts determine scope, procedure, and the regulatory constraint:

• Applicability: The AD is limited to specified helicopter models of the 369 family when they are equipped with any dash variant of the listed tail rotor blade part numbers (369A1613, 369D21606, 369D21613, 369D21615, 421-088). The instrument uses the phrase "all dash numbers" to capture sub-variants of those part numbers (Applicability). Operators must check both model and installed tail rotor blade PN to determine whether the AD applies.

• Removal and Accomplishment Instructions: The AD requires removal of the tail rotor blade assembly by following the Accomplishment Instructions, paragraphs 2.B.(1) through 2.B.(3), Part 2, of the applicable MD Helicopters service bulletin, as applicable to each model (Requirement). The AD does not reproduce the removal steps; compliance is achieved only by following those referenced steps.

• Inspection for a "smooth radius": The substantive inspection requirement is a visual inspection "using a bright light" of the bore of the tail rotor blade root fitting, referencing paragraphs 2.B.(4) and 2.B.(5), Part 2, and Figures 1 and 2 of the applicable service bulletin (Requirement). The AD does not supply a numerical tolerance or an alternative inspection technique; it mandates the specified visual inspection method within the referenced service bulletin.

• Replacement: If the inspection shows that the blade assembly does not have a smooth radius, the AD requires replacement of that blade assembly before further flight, by following the service bulletin paragraphs 2.B.(6) and 2.B.(7), Part 2, and Figure 2 (Requirement). The AD therefore creates a binary decision: pass the visual inspection or replace the blade assembly.

• Identification: After inspection or replacement, the AD requires identification of the serviceable tail rotor blade assembly "with the applicable model of helicopter" by following the Identification instructions, paragraphs 3.(1) through 3.(4) of the applicable service bulletin (Requirement). The AD thus incorporates the manufacturer's marking/identification procedure as part of compliance.

• Timing and permissibility: The AD sets a temporal constraint , compliance must be achieved "before further flight after 1 May 2007" , and explicitly disallows special flight permits (Compliance; Note 1). This converts the inspection/replacement from a scheduled maintenance action into an immediate operational restriction for in-scope aircraft.

• Cross-reference to FAA Emergency AD: The AD notes that FAA Emergency AD 2007-09-51 is referred to (Requirement, Note 2), indicating regulatory alignment or common cause with a parallel FAA directive, though the AD does not reproduce the FAA text.

These concepts allocate responsibility for detailed methods to the manufacturer’s service bulletins (specific SB numbers dated 26 April 2007) and anchor legal obligation to compliance with that manufacturer's Accomplishment and Identification instructions. The AD couples an immediate compliance deadline with an absolute prohibition on ferrying under a special flight permit, thereby narrowing options for operators who discover a non-compliant condition to on-site replacement before further flight (Requirement; Compliance; Note 1).

The primary regulated parties in the text are the owners, operators and maintenance providers of the listed Model 369 series helicopters that are fitted with the enumerated tail rotor blade part numbers. The AD's "Applicability" clause names the affected models and part numbers precisely: Model 369, 369A, 369H, 369HM, 369HS, 369HE, 369D, 369E, 369F, and 369FF helicopters, equipped with tail rotor blade PN 369A1613, 369D21606, 369D21613, 369D21615, or 421-088, all dash numbers. Operators must check their aircraft records or physical parts to determine whether their aircraft fall within this scope.

Regulatory decision-makers are represented explicitly: the AD is signed by a Delegate of the Civil Aviation Safety Authority (David Villiers) and dated 30 April 2007. The inclusion of the delegate’s name and signature indicates the authority under which the AD is issued and provides the administrative imprimatur for enforcement (signature block and date). The AD makes no express differentiation between private, commercial, or corporate operators , the obligation applies to any operator of affected aircraft within the jurisdiction of the issuing authority.

Maintenance organisations and maintenance personnel are directly implicated because the AD requires removal of the assembly, a specified inspection using a bright light, and replacement where necessary, all by following the MD Helicopters Service Bulletins identified in the Requirement. The AD therefore binds maintenance providers to use the referenced service bulletin Accomplishment Instructions and Identification procedures (Requirement).

Third parties are indirectly affected in two ways that the AD makes explicit. First, the AD references manufacturer service bulletins (SB369H-247, SB369D-204, SB369E-099, SB369F-084, dated 26 April 2007) and incorporates specific paragraph and figure references; operators must obtain and use those documents. Second, the AD notes a cross-reference to FAA Emergency AD 2007-09-51 (Note 2). This indicates correspondence with the FAA’s regulatory action, so operators and maintainers operating across jurisdictions or with import/export relationships may need to coordinate compliance documentation and parts sourcing accordingly.

Finally, the AD’s prohibition on special flight permits (Note 1) affects operational decision-makers because it removes the option of flying an aircraft to another location for inspection or repair under a special permit. Where an aircraft is in a location without immediate repair capacity, the operator must make arrangements consistent with the AD’s constraints. The AD does not identify compensation mechanisms, exemptions or appeals processes; the text contains no express carve-outs or alternative methods of compliance other than following the specified service bulletin instructions (Requirement; Compliance).

The AD prescribes a set of mandatory duties for persons responsible for affected helicopters. The duties are concrete and procedural:

• Duty to determine applicability: Owners/operators must identify whether their aircraft is within the AD’s scope by checking both helicopter model and installed tail rotor blade part number, including all dash-number variations listed under Applicability.

• Duty to remove the tail rotor blade assembly: The AD requires removal of each affected tail rotor blade assembly in accordance with the Accomplishment Instructions, paragraphs 2.B.(1) through 2.B.(3), Part 2, of the appropriate MD Helicopters service bulletin (Requirement). This is a preparatory duty that must be performed prior to the mandated inspection.

• Duty to inspect the bore of the tail rotor blade root fitting: Using a bright light, the person performing the maintenance must inspect the bore by following the Accomplishment Instructions, paragraphs 2.B.(4) and 2.B.(5), Part 2, and Figures 1 and 2 of the relevant service bulletin (Requirement). The inspection standard in the AD is the presence of a "smooth radius"; the AD mandates the inspection technique referenced in the service bulletin.

• Duty to replace non-compliant blades before further flight: If an assembly "does not have a smooth radius", it must be replaced before the helicopter's next flight, following the applicable service bulletin paragraphs 2.B.(6) and 2.B.(7), Part 2, and Figure 2 (Requirement).

• Duty to identify serviceable assemblies: After compliance, identification of the serviceable tail rotor blade assembly must be done "with the applicable model of helicopter" by following the Identification instructions, paragraphs 3.(1) through 3.(4) of the service bulletin (Requirement). The AD therefore requires completion of the manufacturer’s identification steps.

• Duty on timing and permissibility: Compliance must be achieved before further flight after 1 May 2007 (Compliance). The AD also contains the explicit duty not to use special flight permits to ferry an aircraft for compliance: "Special Flight permits will not be allowed" (Requirement, Note 1).

The AD does not set out express rights such as an administrative appeal route, alternative methods of compliance, or timelines for exemptions. The text does not provide an express provision for seeking approval of alternative inspection techniques or temporary relief; it mandates following the manufacturer’s specified Accomplishment and Identification instructions. Where rights or remedies would exist under broader aviation law or administrative law, those are not articulated in the AD text. Equally, the AD does not prescribe who pays for inspections or replacements; it does not provide funding or reimbursement, and it does not contain indemnities or contractor obligations.

The AD delegates method detail to the manufacturer’s service bulletins. Compliance therefore necessarily involves adherence to specified paragraphs and figures in those bulletins. The AD’s requirements are immediate in time: they come into force on 1 May 2007 and require action "before further flight after 1 May 2007". This timing removes routine scheduling flexibility and imposes a near-term operational duty on operators of affected aircraft.

In sum, the AD converts manufacturer maintenance instructions into mandatory regulatory duties with definitive timing and a categorical prohibition on special flight permits; it does not set out administrative remedies, alternative compliance mechanisms, or payment arrangements within its text.

The AD text contains a formal directive and an effective date, but it does not set out express penalty clauses, fine amounts, or enforcement procedures within the body of the instrument provided. The document records the issuing authority , a Delegate of the Civil Aviation Safety Authority (David Villiers), dated 30 April 2007 , and the AD identifier (AD/HU 369/117; 7/2007 TX), and states that "This Airworthiness Directive becomes effective on 1 May 2007" (Compliance). Those elements establish the directive’s formal status and its entry into force.

What the AD does provide that bears on enforcement are operational constraints that limit operator options. In particular, it explicitly disallows special flight permits: "Special Flight permits will not be allowed" (Requirement, Note 1). The prohibition on special flight permits functions as an operational enforcement mechanism: an affected aircraft may not lawfully be flown under a special permit to effect compliance, so the practical enforcement of the AD includes grounding until inspectors and maintenance personnel can remove, inspect and, if required, replace the blade assembly in accordance with the referenced service bulletin.

The AD also cross-references FAA Emergency AD 2007-09-51 (Note 2), which implies regulatory alignment with a parallel FAA measure; the AD itself does not reproduce enforcement measures from the FAA text within this document. The AD does not specify the administrative route for non-compliance, for example notices, suspension of certificates, civil penalties, or prosecutions; none of those enforcement mechanisms are described in the provided text.

Because the AD does not contain explicit penalty provisions, identifying enforcement consequences requires reference to the broader regulatory framework under which the Civil Aviation Safety Authority operates. The AD itself does not lay out that framework; it simply places a mandatory obligation on operators. The presence of the delegate's signature and the effective date supports the argument that the AD is binding; however, no specific enforcement steps, monitoring regimes or civil/criminal penalty schedules are stated in this instrument.

In short, the AD mandates actions and imposes an absolute prohibition on special flight permits, but it contains no explicit penalty schedule or detailed enforcement procedures in its text. Enforcement will therefore be through the AD’s mandatory compliance requirements and any enforcement tools that exist under the issuing authority’s broader regulatory powers, none of which are described within this AD.

The AD interacts explicitly with manufacturer service bulletins and with a corresponding FAA emergency AD, and implicitly with the operator’s obligations under aviation safety regulation. The AD incorporates by reference specific MD Helicopters service bulletins and binds compliance to the Accomplishment Instructions and Identification procedures in those documents: SB369H-247, SB369D-204, SB369E-099, and SB369F-084, all dated 26 April 2007 (Requirement). That creates a direct regulatory link between the AD and the manufacturer’s maintenance procedures; compliance with the AD necessarily requires following those manufacturer-prescribed procedures.

The AD also explicitly references FAA Emergency AD 2007-09-51 (Note 2). The cross-reference signals that the condition addressed by the AD has been the subject of regulatory action by the United States Federal Aviation Administration and that the issuing authority has aligned its directive with that FAA action. The AD does not reproduce the FAA text or state whether the FAA AD’s content differs; it simply notes the FAA AD reference.

The AD contains no text about interaction with national statutes or subordinate legislation beyond the authority to issue ADs implicit in the signature of a CASA delegate. The instrument does not itself cite enabling legislation, nor does it describe appeals, review mechanisms, or statutory penalty provisions. Insofar as interactions with other laws (for example, administrative law remedies, civil liability, or criminal sanctions for non-compliance) may exist, those are not set out in the AD document.

Operationally, the AD’s prohibition on special flight permits (Note 1) interacts with the regulatory regime under which special flight permits are granted; the AD removes the availability of that regulatory mechanism for the specific condition. The AD therefore overrides any fact-specific allowance to ferry an affected helicopter under a special permit for the purpose of achieving compliance, at least insofar as the AD has legal effect.

Finally, by making compliance dependent on a manufacturer’s service bulletin, the AD integrates regulatory obligation with the manufacturer’s instructions for safe operation and maintenance. This produces a regulatory dependency: compliance with the AD is satisfied by following the service bulletin paragraphs and figures referenced in the AD. The AD does not create or modify intellectual property rights, supply obligations, or contractual arrangements between operators and manufacturers; any such interactions would lie outside the text of the AD and are not addressed here.

The text provided contains a single dated issuance and an effective date; it does not present any subsequent amendments, revocations, supersessions, or modification history within the document. The AD is identified as AD/HU 369/117 and 7/2007 TX, signed by David Villiers, Delegate of the Civil Aviation Safety Authority, dated 30 April 2007, and states that the AD becomes effective on 1 May 2007 (signature block; Compliance). The service bulletins that the AD references are dated 26 April 2007.

No earlier ADs, no amendment entries, and no later modification clauses are present in the supplied text. The instrument therefore appears as a stand-alone issuance with the following concrete documentary elements:

• AD identifier: AD/HU 369/117; second identifying notation 7/2007 TX (header).
• Issuer and signature: David Villiers, Delegate of the Civil Aviation Safety Authority (signature block).
• Date of signature: 30 April 2007 (signature block).
• Date the referenced manufacturer service bulletins were issued: 26 April 2007 (Requirement).
• Effective date for the AD: 1 May 2007 (Compliance).

Because no amendment history is included in the document, a reader seeking to know whether the AD was later varied, extended, or revoked would need to check external repositories or subsequent AD issuances; that material is not in the supplied text. The AD itself contains no transitional provisions, no re-issue wording, and no language indicating it replaces or is replaced by another AD. The absence of amendment history in the text provided should therefore be read as an absence of such entries in this document, not evidence about actions that may have been taken subsequently outside the supplied instrument.

The supplied AD contains no references to litigation, judicial review, stays, injunctions, appeals, or any past or pending court proceedings arising from this AD. There are no case citations, no notices of legal challenge, and no mention of administrative appeals within the document. The only legal-administrative datum present is the signature of a CASA delegate and the AD’s effective date.

Given that absence, the AD as supplied does not record any litigation history. The text does not indicate whether any party sought judicial or administrative review of the AD’s content, whether enforcement actions were litigated, or whether any orders stayed the AD’s effect. It similarly contains no mention of settlements, compliance negotiations, or recorded disputes.

For a person researching litigation implications or disputes arising from this AD, the document provides no internal evidence; any such history would need to be sought outside the AD text from court records, tribunal decisions, or administrative files. The AD itself makes no provision for preservation of evidence or procedures in the event of adjudication. The only procedural references in the AD are to manufacturer service bulletins and to the FAA Emergency AD 2007-09-51. No legal proceedings or adjudicative outcomes are recorded in the material provided.

Several practical traps for compliance and potential sources of confusion are visible directly from the AD text. These are matters that operators and maintenance providers should attend to because the AD’s mandatory structure, timing and references constrain choices and create narrow compliance pathways.

• Scope hinges on part numbers and dash variants. The Applicability clause lists part numbers and then adds "all dash numbers". That phrasing catches any dash-suffix variants; an operator who looks only at the base part number and ignores dash variants risks missing applicability. The AD thus requires careful verification of the exact installed part number, including any dash suffix.

• Manufacturer procedures are incorporated by reference and specified by paragraph numbers. The AD does not reproduce removal, inspection, replacement, or identification steps; instead it mandates following precise paragraph ranges and figures in the service bulletin (Accomplishment Instructions, paragraphs 2.B.(1)-(7), Part 2; Identification paragraphs 3.(1)-3.(4), and Figures 1-2). If an operator follows a different procedure, or an incorrectly dated or incorrect-model service bulletin, the AD’s textual command may not be satisfied. Compliance requires locating and using the applicable service bulletin for the helicopter model.

• Subjectivity of the required inspection. The mandated inspection method is a visual inspection "using a bright light" to determine whether the bore of the tail rotor blade root fitting has a "smooth radius" (Requirement). The AD sets the criterion but does not quantify it. This may produce inconsistent inspection outcomes if different technicians have different interpretations. Because the AD binds compliance to the service bulletin figures and paragraph guidance, operators should ensure the inspection is carried out in accordance with the referenced images and text rather than relying on an informal visual check.

• No special flight permits permitted. The AD explicitly states "Special Flight permits will not be allowed" (Note 1). The practical effect is that an aircraft which, upon inspection, is found non-compliant cannot be ferried under a special permit to another location for repair. Operators with limited onsite maintenance capability must therefore make arrangements to perform the required removal, inspection and possible replacement at the aircraft’s current location or relocate by non-flight means. This can pose logistic and cost issues but is an explicit constraint in the AD.

• Timing is immediate and absolute. The Compliance clause requires action "before further flight after 1 May 2007". That creates an immediate operational constraint and narrows the window for scheduled maintenance planning. The AD’s effective date is 1 May 2007, signed 30 April 2007; there is therefore minimal lead time from signature to effect. Operators should not assume a grace period exists.

• Reliance on the manufacturer for identification after compliance. The AD requires identification of the serviceable tail rotor blade assembly by following the Identification paragraphs 3.(1)-3.(4) of the service bulletin. If a maintenance provider replaces a blade assembly, they must apply the identification steps specified by the manufacturer. Failure to perform that identification step as specified could render the maintenance non-compliant with the AD even if the physical inspection/replacement was performed.

• Cross-reference to FAA Emergency AD. The AD notes FAA Emergency AD 2007-09-51. While that cross-reference signals parallel regulatory activity, the AD does not reproduce any FAA enforcement provisions or alternative compliance methods that might appear there. Operators cannot assume that FAA procedures substitute for or supplement the AD unless the AD text explicitly allows it.

• Absence of penalty language in the AD. The document does not set out enforcement or penalty particulars. That absence does not mean non-compliance is without consequence; rather, the AD itself lacks express enforcement mechanics. Parties should be cautious in interpreting this gap and should not treat it as waiver of compliance obligations.

Operators and maintainers should therefore pay close attention to installed part numbers (including dashes), obtain and follow the correct and dated MD Helicopters service bulletin applicable to their model, perform the bright-light inspection as described, replace any non-conforming blades before flight, and ensure identification steps in the service bulletin are completed. They should also note that they cannot use special flight permits to move aircraft for compliance and that the AD takes effect immediately on 1 May 2007.

The AD sets out a clear, stepwise compliance pathway by reference to the manufacturer’s service bulletins. The following checklist translates the AD’s textual requirements into procedural steps in the order required by the AD. Each step cites the AD text it implements.

1. Confirm applicability:

   • Check helicopter model against the list in the Applicability clause: Model 369, 369A, 369H, 369HM, 369HS, 369HE, 369D, 369E, 369F, and 369FF.
   • Check the installed tail rotor blade part number. If the blade is PN 369A1613, 369D21606, 369D21613, 369D21615, or 421-088, including any dash-number variants, the AD applies (Applicability).

2. Obtain the correct service bulletin:

   • Locate the applicable MD Helicopters service bulletin for the model: SB369H-247, SB369D-204, SB369E-099, or SB369F-084, dated 26 April 2007 (Requirement).
   • Use the service bulletin for the specific helicopter model, and ensure it is the version dated 26 April 2007 as cited in the AD.

3. Remove the tail rotor blade assembly:

   • Follow the Accomplishment Instructions, paragraphs 2.B.(1) through 2.B.(3), Part 2, of the applicable service bulletin to remove the blade assembly (Requirement). Do not substitute another removal procedure unless an authorised alternative is issued by the regulator; the AD itself mandates following these paragraphs.

4. Inspect the bore of the blade root fitting:

   • Using a bright light, perform the inspection following Accomplishment Instructions, paragraphs 2.B.(4) and 2.B.(5), Part 2, and consult Figures 1 and 2 of the service bulletin for the correct inspection technique and pass/fail imagery (Requirement).
   • The inspection criterion in the AD is whether the bore has a "smooth radius". Apply the method described in the service bulletin paragraphs and figures to determine whether the assembly passes.

5. Replace non-conforming blade assemblies:

   • If the inspection shows the bore does not have a smooth radius, replace that blade assembly before further flight by following Accomplishment Instructions, paragraphs 2.B.(6) and 2.B.(7), Part 2, and Figure 2 (Requirement).
   • Ensure replacement parts conform to applicable part numbers and are properly installed per the service bulletin.

6. Identify the serviceable blade assembly:

   • After inspection and, where required, replacement, perform identification of the serviceable tail rotor blade assembly by following Identification paragraphs 3.(1) through 3.(4) of the applicable service bulletin (Requirement). Complete any tagging, marking or logbook entries the identification instructions require.

7. Timing and flight prohibition:

   • Do not operate the helicopter unless the inspection and any required replacement and identification have been completed. Compliance must be achieved before further flight after 1 May 2007 (Compliance).
   • Do not attempt to ferry the helicopter under a special flight permit to effect compliance; the AD explicitly disallows special flight permits (Requirement, Note 1).

8. Cross-reference FAA AD if relevant:

   • Note that the AD refers to FAA Emergency AD 2007-09-51 (Requirement, Note 2). Where operators are subject to multiple jurisdictions or have international operational considerations, consult the FAA AD text in addition to this AD to ensure aligned compliance.

9. Document the work:

   • While the AD itself requires following the Identification paragraphs in the service bulletin (Identification paragraphs 3.(1)-3.(4)), and the service bulletin will set out any identification marks or logbook requirements, ensure that records reflect completion of removal, inspection method used ("bright light" inspection), the inspection result, any replacement performed, and identification completed per the service bulletin.

10. Seek clarification if necessary:

• If the operator cannot locate the correct service bulletin, if the helicopter model is not clearly one of the listed models, or if there is uncertainty about the installed part number (including dash variants), do not presume non-applicability. Instead verify model and PN and obtain the referenced service bulletin to ensure the AD’s requirements are properly implemented.

This AD leaves little procedural flexibility: compliance is achieved only by following the specified Accomplishment and Identification instructions in the identified MD Helicopters service bulletins and by ensuring any failing assembly is replaced before any further flight beyond the AD’s effective date. The prohibition of special flight permits means operators must plan for on-site inspection and, if necessary, replacement before any subsequent flight.