The AD contains several precise, potentially easily overlooked features that create operational and compliance risk if not handled exactly as drafted.
Short compliance window: The AD requires compliance "within 14 days after the effective date of this AD." The AD states the effective date is 6 October 2008. That gives a tight timeline for aircraft operators to obtain, approve, and insert the required AFM TR into every AFM, to insert a copy of the AD, to advise all flight crews, and to review and update pilot checklists. Operational staff should note the brief interval between signature (30 September 2008) and effectiveness (6 October 2008), and between effective date and the 14‑day compliance deadline.
Document identity and approval: The AD mandates insertion of "Temporary Revision (TR) RJ/155‑5, dated 7 August 2008 or later approved revision." The qualifier "or later approved revision" means only an approved later revision will satisfy the directive. Care must be taken to confirm whether a later revision exists and whether it carries the necessary approval. Operators must ensure they insert the correct and approved TR number and date, not merely any TR with similar content.
Mandatory insertion of the AD: The requirement to "Insert a copy of this Airworthiness Directive in the AFM" is a discrete administrative step. It may be conflated with the AFM TR amendment step, but the AD is explicit that a copy of the AD itself must be placed into the AFM. Failure to physically place a copy of the AD into the AFM at aircraft level may result in an inspector finding non‑compliance despite an AFM TR being in place.
Alignment of checklist and AFM Limitations: The AD does not merely require a change to the AFM; it requires a review of the Operators' Pilot’s checklist "to ensure that the instructions regarding selection of the wing anti‑ice system to 'ON', as specified in the AFM Limitations Section, are incorporated." This creates a consistency obligation. Operators who update the AFM but fail to update the cockpit checklists risk a mismatch between AFM limitations and actionable checklist flows. That misalignment is precisely what the AD seeks to avoid.
Crew advisories and training: The AD requires operators to "advise all flight crews on the changes introduced through the AFM TR." The AFM revision also "requires specific pilot training with regard to enhanced take‑off procedures and winter operations." The AD does not set content, form, or recordkeeping standards for those advisories or training, but operators should not assume a verbal shoptalk suffices where the training requirement in the AFM implies structured training. Coordination between training and operations departments is necessary to ensure compliance that meets inspector expectations.
Scope limitation vs background references: The AD’s Applicability box lists only Model CL‑600‑2B19. The background refers to events involving CL‑600‑2B19 and CL‑600‑2B16. Operators of models other than CL‑600‑2B19 should note that the AD as drafted applies only to the stated model; the background reference to CL‑600‑2B16 is informational, not an expansion of applicability. Conversely, operators of CL‑600‑2B19 cannot rely on the text about other models to dilute obligations.
No express enforcement or recordkeeping instructions: The AD sets duties but does not specify how compliance is to be demonstrated to the regulator. Operators should not assume absence of explicit recordkeeping means absence of enforcement interest. The instruction to insert the AD into the AFM does create documentary evidence local to the aircraft, but operators should consider how to evidence crew advisories and checklist reviews to satisfy any subsequent inspection.
Inter‑regulatory reference: The AD's Note points to Canadian AD CF‑2008‑15R1. Operators should not assume that the Canadian AD text is identical or that compliance with a Canadian AD will automatically discharge an Australian AD requirement. The Australian AD prescribes a specific TR and a specific set of steps.
Administrative coordination: The AD requires multiple discrete actions (AFM TR insertion, AD insertion, crew advisories, checklist review) that may be owned by different departments. Failure to coordinate could result in partial compliance. For example, AFM insertion might be completed while a fleet‑wide pilot checklist remains unchanged.
In short, the AD’s precise document references, short clock, multiple discrete deliverables and the embedded training requirement are the principal "gotchas" likely to generate compliance gaps if treated as a single paperwork fix rather than as a coordinated operational and training implementation project.