AD/DHC-8/126 - Spoiler Cable Disconnect Sensing System

The AD introduces three central engineering and regulatory concepts: Modsum, Service Bulletin and Airworthiness Limitations.

A Modsum (modification summary) is Bombardier’s internal designation for a packaged set of design changes. Each Modsum number (8Q100898, 8Q101443, 8Q101445) identifies a particular engineering change that must be physically incorporated into the aircraft. The AD does not reproduce the detailed instructions; it relies on the corresponding Bombardier Service Bulletin as the approved data. A Service Bulletin is a manufacturer‑issued document that provides step‑by‑step instructions for performing a modification, repair or inspection. While service bulletins are ordinarily advisory, the AD makes compliance with specific revisions mandatory. Operators cannot substitute an earlier revision unless the AD explicitly grandfathers it (which it does for installations performed before the effective date). The concept of “later revisions approved by the Chief, Continuing Airworthiness, Transport Canada” gives the Canadian regulator (Transport Canada) the ongoing authority to approve changes to the method, but only if those changes are formally adopted by CASA. The AD does not delegate that approval power to CASA itself.

The third concept is Airworthiness Limitations (AWL). These are mandatory tasks that must be performed at defined intervals to maintain the aircraft’s type‑certificate validity. The AD references Temporary Revisions AWL‑88, AWL 2‑28 and AWL‑3‑95, all dated 5 August 2004, which introduced a recurring operational check (Task 2760/14) for the spoiler cable disconnect system. That task became permanent with Revision 17 of the Series 100 Maintenance Program Manual. The distinction between a one‑time modification (incorporation of the sensing device and circuit rework) and a repetitive operational check is important for compliance planning. Operators must schedule both the initial retrofit within 24 months and then follow the ongoing check regimen.

The AD also introduces technical terms specific to the DHC‑8 roll spoiler system. “Roll spoiler” refers to a flight‑control surface on the wing that assists with roll control. A “spoiler cable disconnect” occurs when one of the cables linking the cockpit controls to the spoiler fails. The background section explains that a failure could cause unacceptable roll spoiler deflection, reducing controllability. The sensing device is designed to detect such a disconnect and illuminate caution lights. However, after initial installation, Bombardier discovered that the caution light logic differed depending on whether the aircraft was above or below 135 knots. Modsum 8Q101445 reworks the circuit so that both lights (inboard and outboard) illuminate consistently irrespective of speed. That rework applies to all aircraft in the applicability range, meaning even aircraft that already had the disconnect sensing device must be retrofitted again if the circuit rework has not been done. This sequential modification history imposes a double compliance burden on earlier serial numbers.

The directive applies to operators, owners and maintenance organisations responsible for Bombardier DHC‑8 aeroplanes of models 102, 103, 106, 201, 202, 301, 311, 314 and 315, with serial numbers 003 through 599 inclusive. That covers two broad production ranges: the initial production batch from S/N 003 up to S/N 561, and then the first 37 aircraft of the next batch (S/N 562 to 599, which already had Modsum 8Q100898 installed in production but still require the circuit rework). Aircraft with serial numbers 600 and later are not affected because the circuit rework (Modsum 8Q101445) was incorporated in production from that point.

Within the applicability range, the AD divides aircraft into three groups based on serial number, each subject to different modification sets:

• Group 1 (S/N 124, 131, 137, 140‑561): require only Modsum 8Q100898 (disconnect sensing device) plus the universal circuit rework (Modsum 8Q101445). They do not require the interference‑fix mod (8Q101443).

• Group 2 (S/N 003‑123, 125‑130, 132‑136, 138‑139): require all three mods: the sensing device, the interference correction and the circuit rework. The background notes that these early aircraft do not yet have a spoiler cable tension regulator (Mod 8/0708), which may have contributed to the cable interference condition.

• Group 3 (S/N 003‑599): all aircraft require the circuit rework mod (8Q101445). Crucially, if the sensing device mod has not yet been installed, the circuit rework must be done simultaneously. That synchronisation requirement affects logistics and scheduling.

The AD also indirectly affects manufacturers (Bombardier) by mandating that only the latest approved service bulletin revisions are acceptable for future installations. It affects component suppliers who provide the sensing device or circuit‑rework parts, and maintenance facilities that must acquire tooling and training. Insurance underwriters may take compliance with ADs into account when determining hull and liability premiums; non‑compliance can void coverage or worsen claims outcomes. The operational check (Task 2760/14) adds a recurring burden for continuing‑airworthiness management organisations and flight crews.

The compliance population is finite: 597 aircraft at most (S/N 003 to 599). Many of those aircraft are likely still in service worldwide, so the AD has a direct economic impact on commercial operators, regional airlines, government operators and lessors. Smaller operators with fewer aircraft may face disproportionately higher per‑unit compliance costs because they lack scale to spread engineering, parts‑procurement and downtime costs. There is no small‑operator exemption or extended compliance timetable in the AD.

The central duty imposed by the directive is to incorporate the specified modifications within 24 months of 3 August 2006. That compliance period is a single calendar deadline for all three modification sets; there is no phased schedule for different serial number groups. Operators cannot defer certain mods because the circuit rework is mandatory for every aircraft, and for early serial numbers the interference fix is also required. The duty extends to using only Bombardier Service Bulletin 8‑27‑89 Revision E (or later Transport‑Canada‑approved revision) for the sensing device and interference fix, and Service Bulletin 8‑27‑103 Revision A (or later approved revision) for the circuit rework. Using an earlier revision is acceptable only if the modification was completed before the effective date of the directive. After 3 August 2006, any new installation must follow the latest approved revision.

A related duty is to incorporate the recurring operational check (Task 2760/14) into the aircraft’s maintenance program. The AD does not specify a due date for first performance of that check, but it cross‑references Temporary Revisions from August 2004, indicating that the check already existed as a requirement for aircraft that had already incorporated the sensing device. For aircraft that had not yet done so, the initial performance would logically be triggered upon completion of the modification. Operators must update their Maintenance Program Manual accordingly.

Operators also have a duty to document compliance in the aircraft’s maintenance records, showing each mod’s installation date, the service bulletin revision used and the serial number of affected components. While the AD does not explicitly say so, standard CASA practice under Civil Aviation Regulation (CAR) 1988 requires logbook entries for all mandatory modifications.

Rights under the directive are limited but real. An operator has the right to rely on previous installations done in accordance with earlier service bulletin revisions (original issues, Rev A, B, C or D) as acceptable for compliance with Modsum 8Q100898; and for Modsum 8Q101443 if installed per Rev C or D; and for Modsum 8Q101445 if installed per the original issue of SB 8‑27‑103. This grandfathering reduces the burden for aircraft that already had some of the work done, avoiding the need to redo modifications that were performed to a technically adequate, but now superseded, standard. Operators also have the right to use later Transport‑Canada‑approved revisions of the service bulletins, provided those revisions are formally recognised by CASA (the AD says “or later revisions approved by the Chief, Continuing Airworthiness, Transport Canada”). The AD does not grant operators the right to propose alternative methods of compliance without CASA approval; if a different technical solution becomes available, a separate application for an alternative means of compliance would be required under the general regulatory framework.

The AD itself does not list penalties, but it derives its force from the Civil Aviation Act 1988 and the Civil Aviation Regulations 1988 (CAR 1988). Under that framework, failure to comply with an airworthiness directive is a breach of the operator’s continuing‑airworthiness obligations. The legal consequences can include:

• Civil penalties: Under the Act, CASA can issue infringement notices or seek civil penalty orders in the Federal Court. The maximum penalty for a body corporate can be substantial (many penalty units, each indexed). Individual operators face lower but still significant fines.

• Criminal prosecution: Wilful or reckless failure to comply could theoretically attract criminal sanctions, though this is rare for non‑fatal AD non‑compliance.

• Suspension or cancellation of the aircraft’s certificate of airworthiness: An aircraft that does not comply with an applicable AD is not in a condition for safe operation. CASA can issue an airworthiness directive compliance notice; continued operation without compliance may result in grounding.

• Suspension of the operator’s air operator’s certificate (AOC) or maintenance organisation approval. For a commercial operator, even a temporary grounding can cause fleet‑wide grounding if CASA determines that the operator has systemic non‑compliance.

• In civil litigation, non‑compliance with an AD can be used as evidence of negligence or breach of statutory duty in claims for property damage or personal injury.

Enforcement actions are within CASA’s discretion, but the AD gives no indication that CASA intended leniency. The compliance period of 24 months is generous by aviation standards, suggesting that the regulator considered the modification complex and required time for parts procurement and scheduling. However, once that deadline passes, unmodified aircraft are technically unairworthy. The delegate’s signature (James Coyne) confirms the AD was made under proper authority. There is no provision for extension or waiver in the text; any relief would require a separate application under the regulations.

The AD also interacts with enforcement powers of the Australian Transport Safety Bureau (ATSB) if an accident or incident occurs involving a non‑compliant aircraft. However, the ATSB does not enforce compliance; it investigates safety occurrences. Non‑compliance with an AD would be a significant finding in any such investigation and could lead to recommendations for stronger regulatory action.

The directive sits within a hierarchy of regulatory instruments. It is issued under the Civil Aviation Act 1988 and the Civil Aviation Regulations 1988 (CAR 1988), specifically under provisions that empower CASA to issue airworthiness directives. As a legislative instrument, it has the force of law. It does not create new criminal offences independently; rather, it imposes conditions that are enforceable through existing provisions.

The AD interacts with the aircraft’s type certificate data sheet and the approved maintenance program. The Airworthiness Limitations (AWL) referenced in the AD are part of the maintenance program required by CAR 1988 and Civil Aviation Order (CAO) 100.7. Operators must ensure that the recurring operational check (Task 2760/14) is included in their maintenance program and performed at the correct interval. Failure to do so would be a breach not only of the AD but also of the broader maintenance‑approval conditions.

The AD also references Transport Canada AD CF‑2006‑13 (Note 5). This is the Canadian equivalent directive; Bombardier is a Canadian manufacturer, and Transport Canada is the primary certification authority for the DHC‑8. CASA’s adoption of the same requirements ensures consistency with the state of design. However, Australian operators must comply with CASA’s AD specifically; compliance with Transport Canada’s AD alone does not automatically satisfy Australian law, though in practice the content is identical. Operators with aircraft on the Australian register but maintained overseas must ensure that the maintenance organisation complies with the CASA directive, not just the Canadian one.

The AD may also interact with other CASA directives applicable to the DHC‑8 fleet. For example, if another AD imposes a competing deadline or requires access to the same components, operators must prioritise and sequence modifications. No such conflict is apparent in this text, but operators must manage the cumulative workload.

For lease agreements, non‑compliance with an AD can constitute a breach of the lessee’s obligation to maintain the aircraft in an airworthy condition. Lessors typically require copies of AD compliance records. The AD imposes no direct duties on lessors, but they have an indirect interest in ensuring compliance to protect asset value.

The source text is the original issue of AD/DHC‑8/126, dated 22 June 2006, effective 3 August 2006. It is marked “8/2006”, indicating it is the eighth CASA airworthiness directive issued for DHC‑8 aircraft in that year. There is no indication in the text of any earlier version or subsequent amendment. However, the AD incorporates by reference several earlier service bulletin revisions and temporary revisions, which themselves have amendment histories:

• Bombardier Service Bulletin 8‑27‑89 went through original issue and Revisions A, B, C, D and E. The AD mandates Revision E for new installations, but grandfathers earlier revisions.

• Bombardier Service Bulletin 8‑27‑103 went through original issue and Revision A. Only Revision A is specified for future installations; original issue is grandfathered.

• The Temporary Revisions (AWL‑88, AWL 2‑28, AWL‑3‑95) were subsequently incorporated into the permanent Maintenance Program Manual Revision 17 (dated 19 April 2005). That revision post‑dates the temporary revisions but pre‑dates the AD itself. The AD does not require operators to use a specific revision of the maintenance program manual; it only requires that the operational check task be performed as described.

The AD itself is a single‑issue instrument. In the years after 2006, CASA may have superseded AD/DHC‑8/126 with a later directive that cancels and replaces it, or it may have issued amendments. The source text does not contain such amendments. An operator researching compliance today would need to check CASA’s current airworthiness directive database to see if this AD remains in force or has been superseded. For the purpose of this deep dive, the only amendment history available from the source is that the directive references versions of service bulletins that themselves had revision histories. The AD does not state that it amends any prior AD; it stands alone.

The source text contains no reference to any litigation concerning this AD or its subject matter. There is no mention of court cases, administrative appeals, or legal challenges. This is typical for a routine safety‑focused airworthiness directive. ADs are rarely litigated directly because they are issued under delegated legislative power and are subject to limited merits review. An operator who disagreed with the technical basis of the AD would have limited grounds: they could argue the AD was beyond the delegate’s power, that it was procedurally invalid, or that it was unreasonable in the extreme sense (e.g., arbitrary). No such challenge is recorded in the text.

In the broader aviation regulatory context, disputes about airworthiness directives sometimes arise when an operator seeks an alternative means of compliance or an extension, and CASA refuses. Those administrative decisions can be challenged in the Administrative Appeals Tribunal (AAT) or the Federal Court, but the AD itself would be the subject of review only if its legality were in question. There is no indication in the source that any such proceedings took place.

Aircraft‑failure litigation involving the spoiler cable system may exist as a result of the condition the AD was meant to address, but the AD does not refer to any specific accident or incident. The background states that Bombardier “identified” the failure mode; it does not say a crash or serious incident occurred. Therefore, any litigation arising from actual spoiler cable failure would be product‑liability or negligence claims against the manufacturer, not litigation about the AD itself.

For practical purposes, operators should assume the AD has not been the subject of judicial interpretation. The absence of litigation means there is no case law clarifying ambiguous terms or limiting the scope of the directive. Compliance should therefore follow the text strictly.

Several aspects of this directive could trap an unwary operator or compliance manager who relies on a quick reading.

First, the two separate groups for the sensing device and interference mods require careful serial‑number verification. An operator with a fleet of DHC‑8s must treat each aircraft individually. An aircraft at S/N 139, for example, requires all three mods (sensing device, interference fix and circuit rework), whereas S/N 140 needs only the sensing device and circuit rework. A misclassification would lead to incomplete compliance. The background note about the spoiler cable tension regulator (Mod 8/0708) also means that some aircraft in the Group 2 range might already have that regulator, potentially eliminating the need for the interference mod. The AD does not list which serial numbers have that regulator; the operator must check aircraft records or Bombardier data.

Second, the circuit rework (Requirement 3) applies to all aircraft S/N 003‑599, including those that already had the sensing device installed in production (S/N 562‑599). An operator of a relatively new DHC‑8 (say S/N 580) might think it is unaffected because the sensing device is already there. It still needs the circuit rework to fix the caution‑light logic. That rework is not optional; it is a standalone requirement.

Third, the compliance deadline of 24 months is measured from the effective date (3 August 2006). That means the absolute compliance deadline is 3 August 2008. An operator reading the AD after 2006 would have a diminishing window. The AD does not provide for prorating based on when the AD was published or received; the clock starts uniformly.

Fourth, the grandfathering provisions apply only to installations performed “prior to the effective date of the Directive”. If an operator had installed a mod between 22 June 2006 (date of signature) and 2 August 2006 (day before effective date), that installation is acceptable. Any work done after 3 August 2006 must use the latest approved revision. So work cannot begin using an old revision even if it was ordered before the effective date; the physical installation must be complete before that date to benefit from grandfathering.

Fifth, the operational check (Task 2760/14) is a separate ongoing obligation. The AD does not explicitly say when the first check must be performed after modification. It refers to temporary revisions from August 2004, meaning the check already existed for aircraft with the sensing device. An operator who installs the device as a new retrofit must start the check interval from that point. Failing to incorporate the operational check into the maintenance program is a compliance failure, even if the mod is installed.

Sixth, the AD does not address parts availability, engineering resources or the need for ferry flights to a maintenance base. The 24‑month period may be tight if many aircraft require the same modification simultaneously, especially for smaller maintenance organisations. There is no allowance for phased compliance.

Finally, the AD references “later revisions approved by the Chief, Continuing Airworthiness, Transport Canada”. That creates regulatory uncertainty: if Transport Canada approves a new revision of a service bulletin after the AD is issued, is it automatically acceptable in Australia? The AD says yes, but the operator must verify that the revision has been so approved and that CASA does not issue a separate directive. An operator using a revision not yet approved by Transport Canada would be non‑compliant even if it were technically superior.

Compliance requires a step‑by‑step process, but the AD itself does not prescribe a compliance method beyond citing the relevant service bulletins. An operator should take the following actions:

1. Identify affected aircraft. Compile a list of all DHC‑8 aircraft on the Australian register (or operated by the operator) that fall within the applicability: models 102, 103, 106, 201, 202, 301, 311, 314 and 315 with S/N 003 to 599. Confirm each aircraft’s serial number from the type certificate data plate or maintenance records.

2. Determine modification requirements per aircraft. For each serial number, apply the grouping rules:

   • S/N 124, 131, 137 and 140‑561: require Modsums 8Q100898 and 8Q101445.
   • S/N 003‑123, 125‑130, 132‑136, 138‑139: require Modsums 8Q100898, 8Q101443 and 8Q101445.
   • S/N 562‑599: require only Modsum 8Q101445 (the sensing device is already installed in production). Also check whether the spoiler cable tension regulator (Mod 8/0708) is already installed on early serial numbers; if it is, Modsum 8Q101443 may not be required, but the AD does not provide an exemption , clarification from Bombardier or CASA may be needed.

3. Obtain the correct service bulletins. Order Bombardier Service Bulletin 8‑27‑89 Revision E (or later Transport‑Canada‑approved revision) and Service Bulletin 8‑27‑103 Revision A (or later approved revision). Do not use earlier revisions for new installations after the effective date. For Modsum 8Q101443, the instructions are within SB 8‑27‑89 Revision E.

4. Plan the retrofit. The 24‑month compliance period runs from 3 August 2006 to 3 August 2008. Schedule modification work to avoid conflicts with other scheduled maintenance. If the aircraft already has the sensing device (Modsum 8Q100898) installed, it may still require the circuit rework (Modsum 8Q101445) , do not assume partial compliance. For aircraft that need both sensing device and circuit rework, the AD requires that if the sensing device has not yet been installed, the circuit rework must be done concurrently. That means ordering all parts together and ensuring single maintenance access.

5. Perform the modifications. Follow the service bulletin instructions precisely. Use only approved parts. Ensure that any approved later revision is used if the revision was issued after the bulletin date referenced in the AD. Document the work in the aircraft logbook, including the Modsum numbers, service bulletin revision, and date of installation.

6. Update the maintenance program. Incorporate the recurring operational check (Task 2760/14) into the applicable Maintenance Program Manual or equivalent document. The check was initially introduced by Temporary Revisions AWL‑88, AWL 2‑28 and AWL‑3‑95. The permanent content is now in Revision 17 of the Series 100 manual. For Series 200 and 300, the operator should ensure the check is reflected in the approved airworthiness limitations section.

7. Report compliance. CASA may require evidence of compliance during a surveillance audit or inspection. Keep a compliance matrix linking each aircraft serial number to the date each Modsum was completed and the service bulletin revision used. Retain copies of the service bulletins and logbook entries.

8. Verify future revisions. If Transport Canada approves a later revision of either service bulletin after the AD is issued, the operator must decide whether to adopt it. The AD automatically makes that later revision acceptable, but using it may require additional parts or procedures. An operator who has already completed the modification to an earlier revision is not required to redo it; the grandfathering clause protects that installation. However, for any aircraft that has not yet been modified, the latest approved revision must be used.