AD/BELL 430/12 - Disc Assemblies - Tail Rotor Driveshaft

The AD is constructed around four numbered Requirements and a compliance schedule. The core regulatory mechanism is prescriptive inspection and removal obligations linked to a specific BHTC Alert Service Bulletin (ASB-430-07-40). The AD’s scope is narrowly defined by aircraft type, serial-number ceiling (S/N up to 49120) and by the specific part numbers of the tail rotor driveshaft disc assemblies (P/N 36300-1, 37855-1, C048354-1). The AD identifies a manufacturing-date cohort (1 November 2005 to 30 November 2006) as the risk window for machining or indexing errors.

Requirement 1 directs verification: verify manufacturing date, confirm total thickness and check indexing in accordance with BHTC ASB-430-07-40 or later approved revisions. The text provides for two different downstream outcomes following verification. If verification finds no nonconformity, or the manufacturing date is outside the suspect window, the AD requires an appropriate log book entry and states “No further action is required.” If verification identifies a nonconformity, the AD’s Requirements 2 and 3 prescribe removal of assemblies that fail thickness limits or indexing checks.

The AD sets out explicit quantitative limits for total thickness by P/N. These numerical tolerances are the decisive criteria for removal under Requirement 2. For indexing defects, Requirement 3 is categorical: remove any disc assembly which is not properly indexed. Requirement 4 creates a forward-looking installation prohibition: no installation of the listed disc assemblies into any helicopter is permitted unless the assembly is compliant with the ASB dated 28 March 2007 or later approved revisions.

Compliance timing is tiered. Verification must be completed “no later than 25 flight hours or 30 days from the effective date,” while removal for thickness issues must be done “within 10 flight hours” after completing verification. Removal for indexing issues has a longer window: “within 300 flight hours or at next scheduled inspection, whichever comes first,” after completion of verification. The installation prohibition applies from the AD’s effective date. The AD also cross-references Transport Canada AD CF-2007-15, signposting alignment with another regulator’s directive.

Conceptually, the AD operates as a technical hygiene intervention targeted at a discrete production window and discrete part numbers. It uses the manufacturer’s ASB as the operative technical standard. The AD requires concrete maintenance actions (measurements, indexing checks, removals), documentation (log book entries), and an instalment restriction tied to ASB compliance. The document does not elaborate broader enforcement mechanisms or penalties, nor does it detail the precise contents of the ASB; it requires compliance with that ASB or its later approved revisions.

The AD directly affects operators and owners of Bell 430 helicopters with serial numbers up to 49120 that are fitted with disc assemblies P/N 36300-1, 37855-1 or C048354-1. Those aircraft are specified in the AD’s Applicability block: “Bell Helicopter Textron Canada (BHTC) Model 430 helicopters S/N up to 49120 fitted with disc assemblies part number (P/N) 36300-1, 37855-1 and C048354-1.” The practical group that must act includes maintenance organisations, licensed aircraft engineers and inspectors who perform the verification, measurement and indexing checks required by the AD in accordance with BHTC ASB-430-07-40.

The AD’s requirements impose actions on the holders of the aircraft maintenance logs since the AD requires “make an appropriate log book entry” where verification indicates no further action or where the manufacture date is not within the suspect window. While the AD does not name who must sign log book entries, the obligation to record results falls on the operator or the certifying maintenance agent who performs or certifies the maintenance action, because only those parties normally hold and maintain aircraft log books. The AD itself is issued by a CASA delegate (David Villiers) and references Transport Canada AD CF-2007-15; therefore, it also implicates regulatory staff responsible for oversight and any organisations that provide approved revisions to the ASB.

Suppliers and parts sellers are affected by the installation prohibition in Requirement 4. From the AD’s effective date, “Do not install any of the disc assemblies P/N 36300-1, 37855-1 and C048354-1 into any helicopter unless it is compliant to the ASB-430-07-40 dated 28 March 2007 or later approved revisions.” That provision puts an obligation on maintenance shops and parts procurement functions to verify ASB compliance before installing these part numbers into aircraft.

The AD identifies a manufacturing-date cohort (manufactured between 01 November 2005 and 30 November 2006) as containing potentially defective assemblies; these date-stamped parts and any stock held by operators, spares pools or distributors must be checked. The AD therefore affects inventory managers who must verify manufacturing dates and either quarantine, inspect or make records for the stock.

Finally, the AD cross-references Transport Canada’s AD. That linkage means that certificating authorities, cross-border maintenance operations and any parties relying on Transport Canada directives for compliance will need to account for consistency between CASA’s directive and Transport Canada’s CF-2007-15. The document itself does not specify enforcement bodies beyond the CASA delegate but, by invoking the ASB and Transport Canada AD, it draws in manufacturer-authorised procedures and inter-jurisdictional regulatory alignment.

Duties imposed by the AD are prescriptive and procedural. The primary duties are:

• Verification duty (Requirement 1): Operators or maintenance personnel must verify disc assemblies P/N 36300-1, 37855-1 and C048354-1 for manufacturing date, proper thickness and indexing, in accordance with BHTC ASB-430-07-40 dated 28 March 2007 or later approved revisions. The AD specifies this verification as the starting point for all subsequent actions.

• Documentation duty: Where verification shows no further action is required, or where the manufacturing date is outside the suspect period, the AD requires “make an appropriate log book entry to this effect.” That is a positive record-keeping obligation tied directly to the inspection outcome.

• Removal duties: If discs are outside the prescribed thickness limits, Requirement 2 requires removal of any disc assembly not within the specified total thickness ranges. Requirement 3 requires removal of any disc assembly which is not properly indexed. The AD sets the quantitative thickness thresholds for each P/N in the table; noncompliance with those thresholds triggers mandatory removal.

• Installation prohibition (Requirement 4): From the effective date of the AD, no installation of the listed disc assemblies into any helicopter is permitted unless the part is compliant with ASB-430-07-40 or later approved revisions.

Timing duties: The AD sets distinct compliance windows for the duties above. Verification (Requirement 1) must be completed no later than 25 flight hours or 30 days from the AD’s effective date, unless already accomplished. Removal for thickness nonconformity must be completed within 10 flight hours after the completion of Requirement 1. Removal for indexing nonconformity must be done within 300 flight hours or at the next scheduled inspection, whichever comes first, after completion of Requirement 1. The installation prohibition applies immediately from the AD’s effective date.

Rights and procedural allowances under the AD are limited. The AD permits compliance using the manufacturer’s ASB or later approved revisions, which gives operators some flexibility if an approved ASB revision is issued after the AD. The AD also provides a “no further action” outcome where discs and dates are compliant, and requires only a log book entry in that case. The AD does not set out appeal or review rights, nor does it specify any waiver or alternative means of compliance within the text; it simply mandates actions and references the ASB and Transport Canada AD.

Who decides: The AD prescribes actions to be performed “in accordance with” the BHTC ASB. That places the technical method under the manufacturer’s ASB procedures, subject to approval of later revisions. The AD itself was issued by a CASA delegate, indicating regulatory initiation; the maintenance decision to measure, remove or reinstall parts follows from the AD’s technical criteria and the ASB methods. The AD text does not describe mechanisms for seeking a formal alternative means of compliance or exemptions within the document itself.

Costs and burdens are implicit in the duties. The document requires inspections, measurements, log book entries and potential removals and non-routine replacements. Those work-hours, parts and administrative tracking are obligations borne by operators, maintenance organisations and inventory holders of the specified P/Ns. The AD does not quantify the cost but shifts the operational burden to the persons and organisations maintaining the affected helicopters.

The AD text itself does not set out penalties, fines, or enforcement procedures. It is an Airworthiness Directive that becomes effective on 3 October 2007 and prescribes mandatory actions and compliance times; however, the AD document contains no express penalty clauses, civil sanction schedules or criminal sanctions within its text. The AD’s issuance is signed by a CASA delegate, but the instrument as provided stops at specification of technical requirements, timing and cross-references to the BHTC ASB and Transport Canada AD CF-2007-15.

Because the AD does not specify enforcement mechanisms in the text, the AD leaves unspecified within the document who enforces compliance and through what sanctioning framework. The AD does implicitly require record-keeping (log book entries) and prescriptive maintenance actions; absence of such records or failure to perform the required inspections and removals would, in practice, be discoverable in maintenance oversight, audits or occurrences. The AD does not, however, contain language such as “non-compliance is an offence” or identify specific enforcement bodies or procedures.

The AD does explicitly set compliance windows and the effective date, which create measurable obligations. These time-limited obligations allow regulators and oversight bodies to detect whether required actions were completed within the stated hours and days. The AD’s cross-reference to Transport Canada Airworthiness Directive CF-2007-15 suggests regulatory alignment between jurisdictions, but the AD does not itself state whether non-compliance will be referred to Transport Canada or another authority.

In summary, this AD prescribes mandatory technical duties and record-keeping but provides no internal description of penalties or enforcement steps. Any enforcement or penalty consequences would therefore arise from the wider regulatory framework applicable to airworthiness directives and maintenance obligations, which are not contained in the AD text provided.

Within the document, the AD explicitly interacts with two external regulatory/technical instruments. First, it mandates that verification, measurement and indexing checks be performed “in accordance with the instructions provided in BHTC Alert Service Bulletin (ASB) ASB-430-07-40 dated 28 March 2007 or later approved revisions.” The AD therefore imports the ASB as its operative technical standard, making the ASB’s procedural content integral to compliance. Operators must follow the ASB’s instructions; if later approved revisions exist, those are acceptable for compliance.

Second, the AD expressly refers to Transport Canada Airworthiness Directive CF-2007-15 dated 24 August 2007, by way of a Note: “Transport Canada Airworthiness Directive CF-2007-15 dated 24 August 2007 refers.” That cross-reference indicates that Transport Canada issued a similar or related directive and that the CASA AD should be read in the context of that Transport Canada AD. The AD itself does not quote Transport Canada’s AD text nor does it set out any mechanism for reconciling differences, but the reference creates an inter-jurisdictional linkage.

Beyond those two specific instruments, the AD does not identify or cite any statutory provisions, regulatory Part, or administrative rules under which it is issued, nor does it specify how it interacts with broader aviation safety law or maintenance rules. The AD’s text does not specify whether alternative methods of compliance may be approved or who would approve them. It does not specify record-retention periods for the log book entries it requires, nor does it instruct how the verification results are to be reported to the regulator.

Practically, the AD makes the BHTC ASB the technical compliance standard and establishes parallel direction to Transport Canada’s AD. For organisations operating across jurisdictions, the AD’s reference to an ASB and a Transport Canada AD means that maintenance policies, parts procurement and inventory release procedures must accommodate the ASB’s methods and the Transport Canada instruction. The AD does not address other possible intersecting instruments such as maintenance organisation approvals, continuing airworthiness management exposition requirements, or international ICAO standards. Those interactions are therefore outside the scope of the AD text as published.

The AD contains limited internal amendment history. It was issued and signed on 28 September 2007 by David Villiers, a delegate of the Civil Aviation Safety Authority, and it became effective on 3 October 2007. The AD refers to BHTC ASB-430-07-40 dated 28 March 2007 and permits later approved revisions of that ASB to be used for compliance, which implicitly allows for future technical revisions to the ASB to supersede or supplement the original ASB’s procedures for verification and corrective action.

No subsequent amendments to the AD itself are recorded within the document provided. The text does not list any superseding ADs, revocations or follow-up amendments issued by CASA. It does, however, explicitly allow compliance in accordance with later approved revisions of the BHTC ASB, and that is the only mechanism within the AD that contemplates change without issuing a new AD text.

The AD also includes a reference to Transport Canada AD CF-2007-15 dated 24 August 2007. The AD does not state whether changes to Transport Canada’s AD would automatically affect the CASA AD; it simply notes the Transport Canada AD as a related document. There is no chronology of prior versions of the CASA AD in the document, nor does the text include an amendment log, revision number or internal history.

In short, the AD’s own amendment footprint in the provided text is limited to: (a) the permitting of “later approved revisions” of the manufacturer’s ASB for technical compliance, and (b) the original issuance date (28 September 2007) and effective date (3 October 2007). Any further amendment history or revocations would need to be sourced from CASA or other external records; they are not contained in the AD text supplied.

The provided AD includes no litigation history. The document does not reference any court decisions, administrative appeals, disputes, or precedent concerning this AD or the underlying parts. There are no citations to legal cases, no description of challenges to the AD, and no mention of any judicial review proceedings or enforcement litigation.

Because the AD is a technical safety directive focusing on discrete inspection and removal actions, the AD text itself restricts content to applicability, requirements, compliance times, a thickness table, procedural cross-reference to the BHTC ASB, and a reference to Transport Canada AD CF-2007-15. It does not purport to summarise or list any litigation that may have arisen from the production defect window or from actions taken to implement the AD.

If parties require information on whether the AD was the subject of any appeals, administrative challenges, or court litigation, that material is not in the AD. Any litigation history would need to be obtained from external records, court databases, CASA administrative records, or Transport Canada correspondence. The AD as supplied contains no such history.

Several practical pitfalls and points of possible misinterpretation arise directly from the AD’s wording.

• Narrow applicability language: The AD applies only to Bell 430 helicopters S/N up to 49120 fitted with P/N 36300-1, 37855-1, C048354-1. Helicopters with higher serial numbers, or with different disc assembly P/Ns, are outside the AD on its face. Operators must check both the aircraft serial number and the installed disc assembly part number and manufacturing date to determine applicability. The AD does not instruct what to do where serial-number records are incomplete; it simply states the applicability criteria.

• Manufacturing-date cohort: The AD singles out disc assemblies manufactured between 01 November 2005 and 30 November 2006 as the suspect cohort. If a part lacks a clear manufacturing date stamp, the AD requires verification “for manufacturing date,” but does not give a fallback method for determining date. The AD requires that if the manufacturing date is not between the stated dates, and verification confirms no other issue, the operator is to make a log book entry and no further action is required. That creates an operational requirement to be able to show the manufacturing date or perform the measurement/indexing checks in lieu.

• ASB dependency: All verification is to be done “in accordance with” BHTC ASB-430-07-40 dated 28 March 2007 or later approved revisions. The AD does not reproduce the ASB’s procedural steps or acceptance criteria beyond the thickness table, so compliance requires access to the ASB. Operators must ensure they have the correct ASB version or a later approved revision and follow its procedures precisely. If an operator follows an earlier or non-approved revision, the AD does not state that this satisfies the AD.

• Timing sequencing: The AD sets different compliance windows for the numbered Requirements. Verification (Requirement 1) is to be done “no later than 25 flight hours or 30 days from the effective date.” Removal for thickness nonconformity (Requirement 2) must occur “within 10 flight hours, after the completion of requirement 1.” Removal for indexing nonconformity (Requirement 3) has a longer window: “within 300 flight hours or at next scheduled inspection, whichever comes first, after the completion of requirement 1.” This sequencing can create confusion in operational planning because removal for indexing defects may be deferred to the next scheduled inspection or up to 300 flight hours later, whereas thickness defects require much quicker removal. Operators must track the completion time of Requirement 1 carefully to calculate the downstream deadlines.

• Log book entry specifics not stated: The AD requires “make an appropriate log book entry” where no further action is required. The AD does not specify the form, detail or the person who must make that entry. Absent guidance in the AD text, operators should ensure the log entry contains the date, the P/N and S/N checked, the measurement results and the ASB reference, but the AD itself does not prescribe those particulars.

• Installation prohibition takes effect immediately: Requirement 4 forbids installation of the listed P/Ns into any helicopter unless compliant with ASB-430-07-40 dated 28 March 2007 or later approved revisions, “after the effective date of this Airworthiness Directive.” That means parts in stock, supply chains and maintenance shops must verify ASB compliance before installing these parts. The AD does not state how compliance of a stock part is to be demonstrated beyond ASB conformity.

• Inter-jurisdictional cross-reference: The AD’s Note referencing Transport Canada AD CF-2007-15 suggests parallel actions required under another regulator’s AD. Operators that move helicopters or parts across jurisdictions should ensure coordination. The AD itself does not explain how to reconcile any procedural differences that might exist between the CASA AD and the Transport Canada AD.

• No penalty text: Because the AD contains no statement of penalties or enforcement mechanisms, operators should not assume absence of sanction. The AD’s mandatory obligations create a compliance expectation enforceable under the broader aviation regulatory regime, though that enforcement framework is not described in the AD text.

• Serial-number ceiling: The S/N cap (“up to 49120”) must be interpreted exactly as written. If an operator’s aircraft has a S/N just above that threshold, the AD does not apply on its face. That can lead to differences in operational treatment for otherwise materially identical aircraft, making accurate S/N records important.

The AD prescribes discrete steps; operators and maintenance organisations should follow them precisely and document outcomes. The compliance steps, read directly from the AD, are:

1. Determine applicability. Confirm aircraft type is BHTC Model 430 and that the serial number is up to 49120. Confirm whether the helicopter is fitted with disc assemblies P/N 36300-1, 37855-1 or C048354-1. If not fitted with those part numbers or if serial number is above the stated ceiling, the AD does not apply on its face.

2. Obtain and follow the BHTC ASB. Acquire BHTC Alert Service Bulletin ASB-430-07-40 dated 28 March 2007 or any later approved revision. The AD requires verification “in accordance with the instructions provided” in that ASB. Do not attempt ad hoc measurement procedures that diverge from the ASB without prior approval.

3. Perform verification (Requirement 1). Unless already accomplished, perform verification of manufacturing date, total thickness and indexing of each applicable disc assembly no later than 25 flight hours or 30 days from the AD’s effective date, whichever comes first. Record the completion of this verification and identify whether each disc assembly was manufactured between 01 November 2005 and 30 November 2006.

4. If verification shows no action required or if the manufacturing date is not between 01 November 2005 and 30 November 2006, make an appropriate log book entry to that effect. The AD states “No further action is required.” The AD itself does not prescribe the content of the log entry, so ensure the log book entry captures the work performed, the ASB reference, the P/Ns and the result of the measurements to create an auditable trail.

5. If a disc assembly is outside the published thickness limits, remove the assembly (Requirement 2). The thickness limits are:

• P/N 36300-1: minimum 0.174 inch (4.42 mm); maximum 0.186 inch (4.75 mm).
• P/N 37855-1: minimum 0.126 inch (3.20 mm); maximum 0.138 inch (3.50 mm).
• P/N C048354-1: minimum 0.046 inch (1.16 mm); maximum 0.051 inch (1.29 mm).

Removal action for thickness nonconformity must be completed within 10 flight hours after the completion of Requirement 1. Follow the ASB’s removal, replacement and inspection procedures when carrying out the work.

6. If a disc assembly is not properly indexed, remove the assembly (Requirement 3). Removal for indexing defects must be completed within 300 flight hours or at the next scheduled inspection, whichever comes first, after completion of Requirement 1. Again, follow the ASB’s procedures for indexing verification and removal or correction.

7. Do not install listed P/Ns unless compliant (Requirement 4). From the AD’s effective date, do not install disc assemblies P/N 36300-1, 37855-1 or C048354-1 into any helicopter unless the part is compliant with ASB-430-07-40 dated 28 March 2007 or later approved revisions. For parts in inventory, parts distributors and maintenance procurement personnel must verify the ASB compliance status before allowing installation.

8. Make and retain records. The AD requires a log book entry where no further action is required. For all inspections, removals and installations, record the work done, the ASB revision used, the part numbers and serial numbers of removed and installed parts, measurement results and dates. The AD does not prescribe retention periods or the exact log content; retention must follow standard regulatory record practices applicable to operators and maintenance organisations rather than the AD text itself.

9. Coordinate with Transport Canada AD CF-2007-15. The AD’s Note references Transport Canada’s AD. Operators or maintenance organisations should obtain and review CF-2007-15 to ensure any cross-jurisdictional or procedural requirements are aligned. The AD supplied does not state whether compliance with Transport Canada’s AD is a substitute or an additive obligation; therefore operators should consider both documents.

10. Track compliance timeframes relative to Requirement 1 completion. Because Requirement 2’s 10-flight-hours and Requirement 3’s 300-flight-hours deadlines are measured “after the completion of requirement 1,” careful tracking of the date or flight-hour at which verification finished is necessary to calculate downstream deadlines. Implement administrative controls to ensure tasks are scheduled and completed within those windows.

11. Use later approved ASB revisions if available. The AD permits use of “later approved revisions” of ASB-430-07-40 for compliance. If a later approved ASB revision exists, ensure it is approved and follow that revision’s procedures. The AD does not set out who approves revisions; operators should confirm approval status with the relevant authority or the manufacturer’s authorised agent.

12. If in doubt, seek clarification from CASA or the manufacturer. The AD does not describe procedures for alternative means of compliance, appeals, or enforcement. If an operator faces a situation not covered by the AD text (for example, indeterminate manufacturing date stamps, parts with ambiguous labelling, or conflict with another regulatory requirement), the operator should seek direction from the Civil Aviation Safety Authority or the manufacturer. The AD text itself does not provide an internal route for waivers or alternative compliance paths.

Following the AD requires access to the manufacturer ASB, an ability to measure and assess disc thickness and indexing, appropriate log book practices and administrative tracking of the AD’s specified flight-hour and day deadlines. The AD is prescriptive; compliance requires that each of the numbered Requirements and its compliance timeframe be satisfied and documented.