AD/BELL 427/6 - Disc Assemblies - Tail Rotor Driveshaft

This AD operates by mandating inspection and removal rules tied to a specific part number and manufacturing-date band. The central technical requirements are threefold: verify assemblies per a manufacturer Alert Service Bulletin; remove assemblies with thickness outside a defined tolerance; and remove assemblies that are incorrectly indexed. The AD’s technical reference is BHTC ASB-427-07-17 dated 28 March 2007, with later approved revisions accepted as satisfying the ASB requirement (Requirement 1; Requirement 4). The thickness tolerance is explicit: 0.115-0.127 inch (2.921-3.225 mm) (Requirement 2).

Applicability is tightly circumscribed by airframe serial numbers and the installed part number. It applies only to BHTC Model 427 helicopters S/N up to 56056 and S/N 58001 through 58002 fitted with disc assemblies P/N 407-340-340-103 (Applicability). The Background states the safety concern: discs manufactured between 1 November 2005 and 30 November 2006 may have improper thickness or incorrect indexing, making the date band a key triage tool during verification (Background).

The AD establishes procedural and record-keeping obligations. If verification shows no action is required, or the manufacturing date falls outside the suspect band, the AD requires an "appropriate log book entry" to that effect and no further action (Requirement 1). The AD also imposes a preventive restriction on future installations: do not install any disc assembly P/N 407-340-340-103 into any helicopter unless it is compliant with the specified ASB or later approved revision (Requirement 4). This creates an ongoing traceability obligation for replacement parts.

The AD relies on a manufacturer’s ASB as the normative compliance manual rather than embedding technical measurement methods in the AD. The ASB is the operative source for the inspection method and the criteria for "proper indexing" and "proper thickness" verification; the AD requires adherence to the ASB procedures (Requirement 1; Requirement 4). The AD also cross-references a Transport Canada AD, indicating coordination with a foreign regulator on this technical issue (Note).

The AD directly affects owners and operators of Bell Helicopter Textron Canada Model 427 helicopters within the specified serial number ranges when the identified disc assemblies (P/N 407-340-340-103) are fitted (Applicability). Those parties must schedule and perform the verification procedures, make required log book entries, and arrange removal and replacement of non‑compliant parts in the timeframes set by the AD (Requirements; Compliance).

Maintenance organisations, aircraft maintenance engineers (licensed mechanics), and approved maintenance facilities are affected because they will perform the inspections, measurements and removals specified by the ASB and this AD. They are bound to use the ASB-427-07-17 instructions or later approved revisions as the method of verification (Requirement 1). The obligation to prevent installation of non-compliant P/N 407-340-340-103 parts after the effective date also affects parts storers, supply chains and installers who must ensure replaced or incoming parts are traceable to ASB compliance (Requirement 4).

Parts suppliers and rebuilders that handle or supply disc assemblies P/N 407-340-340-103 will be affected to the extent that their stock may fall within the suspect manufacturing dates. Even if a supplier’s inventory is not installed in affected helicopters, the prohibition on installing non‑ASB‑compliant P/N parts into any helicopter after the effective date places an onus on suppliers to verify and document compliance before sale or release for installation (Requirement 4).

Regulatory and oversight bodies, including CASA and potentially correlated foreign authorities, are implicated insofar as the AD cites the Transport Canada AD CF-2007-14. The AD itself was signed by a CASA delegate, David Villiers, indicating an internal delegation mechanism for issuing ADs (signature block; Note). Finally, end-users who operate the helicopter commercially (air taxi, emergency services, charters) will face potential operational interruptions while verifications and removals are completed within the AD timelines (Compliance).

Duties

• Operators and maintainers must verify disc assemblies P/N 407-340-340-103 for manufacturing date, proper thickness and proper indexing in accordance with BHTC ASB-427-07-17 dated 28 March 2007 or later approved revisions (Requirement 1). The AD makes the ASB the operative method of compliance.
• If verification shows no further action is required, or the manufacturing date is not between 1 November 2005 and 30 November 2006, the operator must make an "appropriate log book entry" to record that finding (Requirement 1).
• Remove any disc assembly that is not within the required thickness of 0.115-0.127 inch (2.921-3.225 mm) (Requirement 2).
• Remove any disc assembly that is not properly indexed (Requirement 3).
• Do not install any disc assembly P/N 407-340-340-103 into any helicopter unless it is compliant with ASB-427-07-17 dated 28 March 2007 or later approved revisions (Requirement 4). This is a continuing installation prohibition effective after the AD’s effective date (Compliance).

Timing duties

• The initial verification (Requirement 1) must be completed no later than 25 flight hours or 30 days from the AD’s effective date, whichever comes first (Compliance).
• Removal for thickness non‑conformance (Requirement 2) must be done within 10 flight hours after completion of Requirement 1 (Compliance).
• Removal for indexing non‑conformance (Requirement 3) must be done within 300 flight hours or at the next scheduled inspection, whichever occurs first, after completion of Requirement 1 (Compliance).
• The installation prohibition (Requirement 4) is effective after the AD’s effective date (Compliance).

Rights and entitlements

• If, after following the ASB verification procedure, a disc assembly does not require further action or is outside the stated manufacturing date window, the operator’s right is to record that finding in the log book and cease further action under the AD (Requirement 1). The AD explicitly states "No further action is required" in that circumstance.
• The AD accepts "later approved revisions" of the ASB as compliant methods. That offers maintainers some flexibility to comply with an updated ASB that might include improved procedures or clarifications, provided the revision is approved (Requirement 1; Requirement 4).
• The AD does not, in its text, set out exemptions or alternative methods of compliance beyond compliance with the ASB or later approved revisions. Any such alternative method would need to be consistent with regulatory practice, but the AD itself conditions compliance on the ASB (Requirement 1; Requirement 4).

Documentary obligations

• The AD requires a log book entry where verification shows no further action or where the manufacturing date is not in the suspect range. The AD uses the phrase "appropriate log book entry", making the form of recordkeeping an explicit duty (Requirement 1).

Decision-makers and accountability

• The AD was issued and signed by a CASA delegate, identified by name (David Villiers), who acts as the issuing authority for this instrument (signature block). The AD does not specify the appeal or review mechanism within its text.

The AD text supplied does not state specific civil or criminal penalties, monetary fines, or administrative sanction mechanisms. The document sets mandatory technical and record-keeping actions (verification, removal, log book entry, and an installation prohibition) and specifies compliance timeframes, but it does not itself describe enforcement steps, penalty rates or infringement procedures.

Enforcement implications that can be drawn directly from the AD text

• The AD prescribes mandatory safety actions and time limits; as such the operator and maintenance organisation are bound to perform them in accordance with the AD’s Requirements and Compliance section. The AD’s effective date is 22 November 2007, after which the installation prohibition is operative (Compliance; Effective date).
• The AD requires an "appropriate log book entry" where verification shows no further action is required, creating a documentary record that can be relied upon for compliance audits (Requirement 1). Failure to create that entry would mean the operator has not complied with the AD’s stated duties.

What the text does not supply

• The AD does not specify the enforcement agency actions, penalty structure, or administrative review procedures. It does not include wording about suspension of operations, revocation of certificates, or fines. The AD also does not describe a process for waivers or alternative means of compliance outside the ASB beyond stating compliance to "later approved revisions" of the ASB.

Practical enforcement consequences implied by the AD

• Because the AD sets mandatory technical steps and records, regulators performing oversight or audits will use the log book entries, maintenance records and part traceability to assess compliance. The AD cross-references an ASB and a Transport Canada AD, implying alignment with broader regulatory expectations for airworthiness, but the AD text itself does not specify sanction mechanisms (Requirement 1; Note).

Users seeking clarity on enforcement consequences or remedies will need to consult the issuing authority’s broader regulatory framework and enforcement policies outside this AD text, because the AD document provided contains no penalty or enforcement matrix.

The AD explicitly cross-references other safety instruments and a manufacturer’s service directive; those references govern how the AD operates in practice:

• Manufacturer’s service information is the operative compliance tool. The AD requires verification "in accordance with the instructions provided in BHTC Alert Service Bulletin (ASB) ASB-427-07-17 dated 28 March 2007 or later approved revisions" and conditions installation on compliance with the same ASB (Requirement 1; Requirement 4). This makes the ASB a normative document incorporated by reference into the AD’s duties.
• The AD notes Transport Canada Airworthiness Directive CF-2007-14 dated 24 August 2007 as a referenced instrument (Note). That indicates coordination or parallel regulatory action by a foreign authority, but the AD text does not elaborate on the legal effect of that foreign AD within the Australian regulatory framework. The AD simply records the existence of that Transport Canada AD for reference.
• The AD requires a log book entry where no further action is required or where manufacturing dates are outside the identified window (Requirement 1). That creates an evidentiary record that will interact with national maintenance and record-keeping obligations; however, the AD text does not state or reproduce those national maintenance regulations. The AD’s instruction to make a log book entry intersects with ordinary maintenance log book duties but does not modify them in text.
• The AD’s installation prohibition (Requirement 4) creates an operational constraint on parts management and installation practice. It requires that no disc assembly P/N 407-340-340-103 be installed unless compliant with the ASB or an approved revision. That will interact with contractual obligations for parts suppliers and with internal quality assurance procedures for maintenance organisations, but such contractual and regulatory relationships are not set out in the AD text.
• The AD becomes effective on a specific date (22 November 2007), after which the installation prohibition is operative and compliance timeframes commence. The AD does not provide transitional rules that would otherwise amend or suspend other statutes or regulations; it functions as a standalone mandatory direction within the aviation safety regulatory regime.

In short, the AD incorporates a manufacturer’s ASB by reference, requires record-keeping that will be relevant to broader maintenance oversight, and notes a corresponding foreign AD. It does not purport to amend other legislation, nor does it describe its operation in the context of the broader statutory enforcement regime; those interactions must be assessed against the general aviation regulatory framework outside this AD’s four corners.

The AD text itself contains limited material about amendments. It identifies the specific BHTC Alert Service Bulletin to be used for verification and explicitly permits "later approved revisions" of that ASB as acceptable for compliance (Requirement 1; Requirement 4). That language is the only mechanism in the AD for accepting future technical updates without reissuing the AD.

Key timeline entries visible in the AD:

• The BHTC Alert Service Bulletin identified is ASB-427-07-17 dated 28 March 2007. The AD mandates compliance with that ASB or later approved revisions (Requirement 1; Requirement 4).
• The AD references Transport Canada Airworthiness Directive CF-2007-14 dated 24 August 2007 (Note).
• The AD provides its own effective date: it became effective on 22 November 2007 (Compliance; Effective date).
• The AD is dated and signed 28 September 2007 by a CASA delegate, but the AD's stated effective date is 22 November 2007, which is the date by which the compliance timeframes are measured (signature block; Effective date).

What the AD does not include about amendment mechanics

• The AD does not contain an explicit amendment log, prior versions, or later amendments to the AD itself. It contains only the single version presented and references the ASB with acceptance of later approved revisions.
• The AD does not specify how formal approvals of later ASB revisions will be documented within CASA or how operators should determine whether a later revision is "approved" for the purpose of this AD. The instrument assumes the existence of an approval process for ASB revisions, but the AD text does not detail it.

Practical implication

• The only explicit mechanism for future change embedded in the document is acceptance of "later approved revisions" of the BHTC ASB. Any other amendment to the AD, or formal record of approval of a revised ASB, is not set out in the AD text and would need to be managed by CASA’s usual administrative processes outside this text.

The provided AD text contains no information about litigation, appeals, or judicial review relating to this directive. It does not reference any judicial decisions, enforcement proceedings, or disputes arising from its issuance, nor does it name any parties who have challenged or complied under contested circumstances.

What is present in the document

• The AD is an administrative instrument issued by CASA, signed by its delegate, David Villiers, with a date stamp of 28 September 2007 and an effective date of 22 November 2007 (signature block; Effective date).
• The AD references Transport Canada AD CF-2007-14 dated 24 August 2007 (Note), but does not report litigation connected to that AD.

Absence of litigation data

• Because the AD text supplied includes no litigation history or references to cases or proceedings, the AD does not provide evidence of legal challenges or court interpretation. Any inquiry into litigation history would require consulting judicial records, enforcement records or CASA administrative files external to this AD document.

Several practical pitfalls and potential sources of confusion arise from the AD’s text and structure; these are set out precisely as the AD provides instructions and dates.

1. Applicability is narrow and serial-numbered

• The AD applies only to BHTC Model 427 helicopters S/N up to 56056 and 58001 through 58002 fitted with disc assemblies P/N 407-340-340-103 (Applicability). Operators must check both helicopter serial numbers and the installed part number. Missing either check could lead to unnecessary action or failure to act where required.

2. Manufacturing-date triage and the log book entry

• The AD focuses attention on discs manufactured between 1 November 2005 and 30 November 2006 (Background). Requirement 1 instructs verification of manufacturing date, thickness and indexing per the ASB. If, after verification, the manufacturing date is not between those dates, the AD states "make an appropriate log book entry to this effect. No further action is required." This means a clear record must be made even when no defect is found. Operators should ensure the log book entry is sufficiently detailed to show the ASB verification was performed and that the manufacturing date was outside the suspect range.

3. Different compliance windows for different defects

• Removal for thickness non‑conformance must be completed within 10 flight hours after completion of Requirement 1 (Compliance; Requirement 2). Removal for indexing non‑conformance must be completed within 300 flight hours or at the next scheduled inspection, whichever comes first, after completion of Requirement 1 (Compliance; Requirement 3). These two windows differ by two orders of magnitude; operators must track which defect applies and apply the correct timeline. Confusing or conflating the two could lead to non‑compliance.

4. What "proper indexing" means is defined by the ASB, not by the AD

• The AD requires verification "in accordance with" the ASB; it does not define how to assess "proper indexing" or the measurement technique for thickness (Requirement 1). Practitioners must obtain and follow ASB-427-07-17 (or later approved revisions) for procedurally acceptable inspection steps. Relying on ad hoc or non‑ASB methods would not meet the AD’s explicit requirement.

5. Installation prohibition is absolute unless ASB-compliant

• Requirement 4 prohibits installing any disc assembly P/N 407-340-340-103 into any helicopter unless it is compliant with the ASB or later approved revisions. This is not limited to the suspect serial-numbered helicopters; it is an across‑the‑fleet installation prohibition. Parts inventory and supply chain controls must therefore ensure traceability to an ASB compliance status before release for installation.

6. Timing between AD signing and effective date

• The AD is signed 28 September 2007 but states an effective date of 22 November 2007. Different actions are tied to that effective date. Operators must not assume the signatory date is the compliance trigger; the AD specifies the effective date explicitly (signature block; Effective date).

7. The AD references a foreign AD but does not import it

• The AD references Transport Canada AD CF-2007-14 (Note). That note signals related action by another regulator but the AD does not incorporate the foreign AD’s text or obligations. Users should be careful to treat the Transport Canada AD as a cross-reference rather than a substitute for this AD’s own requirements.

8. Recordkeeping precision

• The AD requires an "appropriate log book entry" but does not prescribe the contents of that entry. Aircraft record-keepers must ensure entries are sufficiently detailed to demonstrate compliance in any future audit: date of ASB procedure, part P/N, part manufacturing date, measurement results, and action taken (if any).

9. Scope of "later approved revisions"

• The AD allows compliance with "later approved revisions" of the ASB but does not identify the approval authority or process in the AD text. Parties should confirm, through CASA or the BHTC ASB administration, which ASB revisions are considered "approved" for compliance purposes.

10. Replacement parts traceability

• Because the AD conditions installation on compliance with the ASB, replacement parts must come with documentation of compliance. Operators who accept a part without traceable ASB compliance documentation will be unable to lawfully install it under the AD.

The AD outlines a stepwise compliance procedure; the following is a practical reading of those steps, strictly grounded in the AD’s text and the ASB reference it mandates.

1. Determine applicability

• Check each helicopter’s serial number against the AD’s applicability: BHTC Model 427 S/N up to 56056 and S/N 58001 through 58002 (Applicability).
• Check whether disc assembly P/N 407-340-340-103 is fitted to the helicopter. The AD applies only where that P/N is installed (Applicability).

2. Obtain the ASB and any later approved revisions

• Acquire BHTC Alert Service Bulletin ASB-427-07-17 dated 28 March 2007 and confirm whether any later approved revision exists. The AD requires verification in accordance with the ASB or a later approved revision (Requirement 1; Requirement 4). Do not attempt to substitute other procedures unless they are an approved ASB revision.

3. Perform the verification per the ASB within the AD timeline

• Complete the ASB verification no later than 25 flight hours or 30 days from the AD’s effective date, whichever comes first (Compliance). The AD makes the ASB the procedural norm for verifying manufacturing date, thickness and indexing.

4. Record the result if no action needed

• If the verification shows the assembly does not require further action, or if the assembly’s manufacturing date is outside 1 November 2005 to 30 November 2006, make an "appropriate log book entry" recording that finding and no further action is required (Requirement 1). Ensure the log book entry records the ASB used, the part P/N, the manufacturing date and the inspector’s identification.

5. Remove non‑compliant discs according to defect type and timeframe

• Thickness non‑conformance: Remove any disc assembly not within the specified thickness range of 0.115-0.127 inch (2.921-3.225 mm) within 10 flight hours after completion of Requirement 1 (Requirement 2; Compliance).
• Indexing non‑conformance: Remove any disc assembly not properly indexed within 300 flight hours or at the next scheduled inspection, whichever occurs first, after completion of Requirement 1 (Requirement 3; Compliance).
• Document removal, replacement, and disposition of removed parts in maintenance records consistent with the "appropriate log book entry" standard in the AD.

6. Prevent installation of non‑ASB‑compliant P/N parts

• Do not install any disc assembly P/N 407-340-340-103 into any helicopter unless it is compliant with ASB-427-07-17 dated 28 March 2007 or a later approved revision (Requirement 4). Maintain part traceability and hold supplier documentation showing that any replacement parts have been verified to the ASB’s standards.

7. Maintain records for audit and future reference

• Keep the log book entries and maintenance records that evidence the ASB verification, measurements, removal actions, parts replaced, and the provenance of replacement parts. The AD’s explicit recordkeeping duty for effectively negative findings suggests regulators will look for documentary proof of the verification process.

8. Coordinate with supply chain and parts managers

• Ensure spare parts inventory is segregated and identified by manufacturing date and ASB compliance status to prevent inadvertent installation of non‑compliant parts. Because the AD conditions installation on ASB compliance, parts managers must verify and document ASB conformity prior to release.

9. Cross‑reference Transport Canada AD where helpful

• The AD notes Transport Canada AD CF-2007-14 dated 24 August 2007. Consult that AD for additional technical background or corroborating actions, but comply with this CASA AD’s specific requirements and timelines (Note).

10. Seek clarification where the ASB approval status is uncertain

• If there is uncertainty about whether a later ASB revision is "approved" for compliance with this AD, request confirmation from the CASA delegate or relevant CASA office. The AD allows later approved revisions to the ASB but does not describe how approval is to be ascertained within its text (Requirement 1; Requirement 4).

By following these steps , confirm applicability, follow the ASB procedure in the prescribed timeframes, remove non‑conforming parts within the stated intervals, make and retain the required log book entries, and ensure replacement parts are ASB‑compliant before installation , an operator will have implemented the actions this AD prescribes. The AD’s explicit time limits and the ASB cross-reference determine the operative compliance obligations.