Several practical and interpretive risks arise from the AD’s wording and structure that operators and maintainers should note. These are drawn strictly from the text provided.
Limited applicability window by serial number. The AD applies only to DHC-8 Series 400 aircraft serial numbers 4003 through 4089. Aircraft outside that serial range are not covered by the directive as written. An operator who overlooks the specific serial-number limitation may either overapply compliance requirements to unaffected aircraft or, conversely, fail to apply the AD to an in-range aircraft. The AD does not provide flexibility on applicability beyond those serial numbers.
Two different compliance windows contingent on prior modifications. The AD sets two different time-in-service deadlines: 500 hours for aircraft without SYD 84-28-002/SYD 84-29-006 or Modsum 4-184079/4-184081, and 4,000 hours for aircraft with those incorporations. Operators must verify historical incorporation of the specified SYDs or Modsum numbers to determine the correct compliance window. Ambiguity or gaps in maintenance records could cause misclassification, leading to missed deadlines or unnecessarily accelerated work.
The AD requires use of a Service Bulletin subject to Transport Canada approval. The directive prescribes Bombardier SB 84-54-09 dated 23 January 2004, or "later revisions approved by Transport Canada." That phrase creates a dependency: an operator cannot rely on a later SB revision unless it has been approved by Transport Canada. Using an unapproved revision could fail to meet the AD requirement as written. Operators must check the approval status of any later SB revision; the AD text itself does not provide the approval status, only the condition.
Overlap with temporary rework. Bombardier issued System Drawings SYD 84-28-002 and SYD 84-29-006 as temporary rework instructions to enlarge tolerance holes. The AD treats those as existing mitigations but still requires installation of Modsum 4-113438 within the AD-prescribed windows. An operator who relies on earlier SYD work must note that the AD nevertheless mandates the Modsum installation within 4,000 hours TIS. Temporary fixes are not treated as full compliance with the AD.
No enforcement or penalty specifics in text. The AD does not state penalties, so operators cannot find enforcement procedures or remedial paths within the document. If an operator seeks to understand consequences for non-compliance, that information is not in the supplied AD and must be sought in other regulatory materials.
Potential for confusion over numbering and wording. The Requirement section repeats closely similar phrasing for "For aircraft without..." and "For aircraft with..." and then lists the same Modsum and SB requirement for each. Readers may be tempted to read the first as the only requirement; careful reading is required to map each requirement to its corresponding compliance timeframe. The Compliance section separates two time windows numerically (1 and 2), but does not explicitly restate which window applies to which Requirement paragraph. The intended mapping appears to be: Requirement paragraph 1 corresponds to Compliance item 1 (500 hours) and Requirement paragraph 2 corresponds to Compliance item 2 (4,000 hours). Operators should confirm that mapping when planning.
Timing between issue and effective date. The AD was signed on 21 February 2006 and "becomes effective on 13 April 2006." That gap means that the compliance clock is measured from 13 April 2006; operators must schedule work in reference to that effective date. Misreading the effective date as the issue or sign date could lead to scheduling errors.
No alternative methods of compliance in the text. The AD does not list acceptable equivalent modifications or specific procedures for seeking alternative compliance; if an operator believes an alternative measure addresses the unsafe condition, the mechanism for approval is not included in the directive text. The only expressly permitted alternative is using a later SB revision if approved by Transport Canada.
Transport Canada linkage may create cross-jurisdictional steps. The AD conditions SB revision acceptability on Transport Canada approval and references a Transport Canada AD. Operators may need to consult or coordinate with Transport Canada records to confirm approved SB revisions. This cross-reference is a gotcha for those who assume CASA alone governs acceptable SB revisions.
In sum, the key operational traps are: precise serial-number applicability; the need to determine prior Modsum/SYD incorporation to select the correct compliance window; reliance on a Service Bulletin only when it is Transport Canada-approved for later revisions; potential record-keeping gaps; and absence of enforcement details in the AD text.