This AD contains a number of potential practical pitfalls and points of ambiguity that operators and maintenance organisations should note carefully and manage, based strictly on the AD text.
Serial-number scope gap: The Applicability lists serial numbers 7003 through 7067, and 7069 through 7947 (Applicability). That listing omits serial number 7068. The AD does not explain whether omission of 7068 is deliberate (e.g., a different configuration) or clerical; operators must confirm the applicability of the AD to any airframe near that boundary rather than assume inclusion.
Per-nozzle termination: Completion of Requirement 3 is explicitly a terminating action only for the applicable engine exhaust nozzle (Requirement 3). That creates a scenario where one nozzle on an aircraft can be upgraded and removed from the inspection cycle while the other nozzle remains subject to recurring inspections until its replacement. Operators must track compliance status at the nozzle level, not only at the aircraft level, to avoid missing continuing inspection obligations.
Immediate grounding trigger: Requirement 1.a requires replacement before further flight if a bolt is missing or fractured. The AD therefore creates an immediate no-fly condition for affected nozzles until the replacement is completed. Failure to understand this could lead to inadvertent flight with an identified defect. The AD does not provide any interim ferry or special flight permission within its text.
Dependency on SB version and NAA approval: The AD mandates the use of Part A and Part B of SB 601R-78-021 dated 2 June 2006, or later NAA approved revisions (Requirement 1; Requirement 3). Using a later SB revision requires NAA approval. Operators who adopt a later SB revision without confirming NAA approval risk non-compliance. The AD does not specify how NAA approval is to be evidenced in maintenance records.
Flight-hour counting and compliance windows: The compliance obligations are expressed in flight hours after the AD’s effective date (initial inspection within 1,500 flight hours; replacement within 4,000 flight hours; recurring inspections at intervals not to exceed 1,500 flight hours) (Compliance). Operators must be careful in counting flight hours from the AD’s effective date (30 August 2007) and in accounting for any flight hours already accrued since that date to calculate remaining time to compliance. The AD text does not address alternative time metrics (calendar days, cycles), only flight hours.
Parts availability and lead time: The AD requires replacement with new attachment hardware in accordance with Part B of the SB (Requirement 3). The AD contains no provision for parts supply, nor does it include any allowance for extended lead times. If the replacement hardware is not immediately available, the operator faces potential unscheduled removal from service if inspection reveals a missing or fractured bolt. The AD provides no exception for supply-chain issues.
Record-keeping expectations not specified: The AD does not specify the form of records required to demonstrate compliance. While operators will typically record AD compliance in maintenance logs, the AD text does not set out a required form or retention period. That omission means operators must apply usual maintenance record practices under the broader regulatory framework to prove compliance.
No explicit penalty or relief mechanism in the AD text: The AD does not state penalty amounts or the process for seeking exemptions or alternative methods of compliance (the AD does allow later NAA-approved SB revisions). Operators should not assume the AD provides procedural avenues for relief; any such mechanisms will be in the regulator’s broader administrative framework and are not described here.
Reference to foreign regulator AD: The AD notes Transport Canada AD CF-2006-19 (Note). Differences between jurisdictions’ ADs might exist; the AD does not reconcile any differences or address how to prioritise multiple authorities if an operator is subject to several regimes.
Ambiguity about partial compliance: If an operator has already performed actions under the Bombardier SB before the AD date, the AD states initial inspection is required “within 1,500 flight hours … unless previously accomplished” (Compliance 1). The AD does not specify how to document or validate prior accomplishment for the purposes of counting down to replacement or verifying terminating action. Operators must maintain and be able to produce records proving prior accomplishment to avoid duplicate work or disputed compliance.
In practice, these “gotchas” mean operators must be meticulous about serial-number applicability, per-nozzle record-keeping, flight-hour calculations, use of NAA-approved SB revisions, parts procurement lead times, and documentation of any work performed before the AD’s effective date.