AD/DHC-8/148 - Elevator Power Control Unit

An airworthiness directive (AD) is a legally enforceable notification issued by the national aviation authority to correct an unsafe condition in an aircraft, engine, propeller, or appliance. Under the Civil Aviation Act 1988 and the Civil Aviation Safety Regulations (CASR) Part 39, ADs are mandatory. Non-compliance can ground the aircraft and attract enforcement action.

The component in question is the elevator power control unit (PCU), part number 390600-1007. Each elevator surface on the DHC-8-400 series is driven by three PCUs, each powered by a separate independent hydraulic system. This triple redundancy means that failure of a single PCU shaft may not produce any immediate symptom - it can remain dormant. The AD’s justification notes that such a dormant loss of redundancy, combined with the potential for a broken shaft to damage adjacent hydraulic lines, could degrade controllability.

The suspect PCU population is defined by serial number. The AD lists 88 specific serial numbers (e.g., 238, 698, 783 through 788, 790, 793, 795, 802, 806, 807, 810, 820 through 823, 826 through 828, 831, 835, 838, 840, 886 through 889, and 898 through 955). Any PCU bearing one of these numbers is presumed to contain the material defect unless it has already been reworked and marked with a suffix “A”. The suffix “A” after the serial number is strong evidence that a magnetic particle inspection has been passed.

The escalation logic is important. If after the initial inspection all six PCUs are either outside the suspect range or carry suffix “A”, the directive is fully satisfied immediately. Only if a suspect PCU is found does the operator become subject to the ongoing daily check. That daily check is not a permanent burden; it ends once the suspect PCU is replaced. Replacement may be accomplished using Bombardier SB 84-27-32, which provides instructions for removal, replacement, and subsequent rigging of the elevators.

The applicability is limited to 15 aeroplanes: serial numbers 4135 through 4149. That range is unusually narrow, suggesting either that only those airframes were delivered with the suspect batch of PCUs, or that the defect was contained to a specific production run. Operators of other DHC-8-400/401/402 aircraft are not affected, which is a material point for any compliance programme.

Compliance times are specified in days and flight hours. The 30-day deadline for the initial identification check is relatively short and may require prompt access to hangars and records. The 2000-hour or 12-month replacement window allows operational planning, but the earlier of the two periods binds the operator. An aircraft that flies 2000 hours in, say, 8 months must replace the PCUs within 8 months.

The primary group affected is operators and lessees of Bombardier DHC-8-400, 401, and 402 aeroplanes with manufacturer serial numbers 4135 through 4149. Based on the serial number range, this is at most 15 airframes worldwide. In Australia, the number is likely very small - possibly zero, one, or a handful. The AD is issued by CASA, but the aircraft are designed and certified by Transport Canada (Canada being the state of design). Operators anywhere operating these specific serial numbers must comply if they are within CASA’s regulatory jurisdiction, i.e., aircraft on the Australian register or operated by Australian operators.

Maintenance organisations that manage or work on these aircraft are affected. They must be familiar with the AD, carry out the inspection, perform the daily checks (if required), and execute the PCU replacement per the service bulletin. The AD does not mandate a particular maintenance provider, but the work requires appropriate ratings under CASR Part 145.

Manufacturers and suppliers of the PCU (Bombardier, formerly de Havilland Canada, and its vendors) are indirectly affected. They must supply replacement PCUs that are either new or reworked (with suffix “A”). The AD does not prescribe a price or availability, but the limited population (88 suspect units) and the need to replace up to six per aircraft (for the affected fleet) may put pressure on the supply chain.

Passengers and the public have an indirect interest. The AD addresses a latent safety risk that could affect controllability. By mandating replacement, the regulator aims to prevent a potential accident. However, the cost of compliance - inspection labour, daily checks, component procurement, replacement labour, and potential downtime - is borne by operators and will be reflected in operating costs and ultimately ticket prices or charter fees.

Insurers may require proof of AD compliance as a condition of hull and liability coverage. An aircraft found with an overdue AD could see its insurance voided or premiums increased.

Regulators in other jurisdictions (Transport Canada, FAA, EASA) are also affected in that they may either adopt the same directive or require equivalent action. The AD notes that it references Transport Canada AD CF-2009-16. Operators with aircraft on multiple registers must comply with each authority’s version, though the requirements are usually identical.

The narrow applicability means the overall economic impact on the aviation industry is minimal. For the few operators who do operate one of these 15 aircraft, the burden can be significant relative to their fleet size. A small regional operator with a single DHC-8-400 in the affected range may face unplanned maintenance costs, possible aircraft downtime, and the need to source replacement PCUs quickly after the 30-day inspection window opens.

The AD imposes a strict sequence of duties on the operator. No discretion is given to depart from the requirements or timelines. The duties are as follows.

Duty to inspect serial numbers (within 30 days). The operator must determine the serial number of each of the six installed elevator PCUs. This requires physical access to the aircraft and the ability to read the serial number stamps on the PCUs. The duty is absolute - there is no exception for aircraft that are undergoing maintenance or out of service at the effective date. If the aircraft is not accessible, the operator may need to defer the inspection until it is, but the 30-day clock runs from 2 July 2009.

Duty to conduct daily operational checks. Only activated if a suspect PCU (without suffix “A”) is found. The daily check must be performed before the first flight of each day, or at intervals specified in the approved procedures. The AD does not specify consequences if a check is missed, but the aircraft would likely be unairworthy for subsequent flights.

Duty to replace suspect PCUs. Within 2000 flight hours or 12 months from the effective date, whichever comes first. The operator must install a PCU that either is outside the suspect serial range or has suffix “A”. The duty extends to all six PCUs that are suspect; the AD does not permit partial replacement.

The operator also has certain rights. The operator may use alternative procedures for the daily check if they are equivalent to those in Bombardier AOM 217B. However, the AD does not explicitly grant a right to alternative means of compliance beyond what is referenced. The operator may rely on previous accomplishment of Bombardier SB 84-27-32 (original issue or Revision A) as meeting the replacement requirement, provided the work was done correctly and recorded.

The operator has the right to challenge the AD through the Administrative Appeals Tribunal or the Federal Court under the Administrative Decisions (Judicial Review) Act 1977, but that right would be practically limited. An AD is a safety directive; a challenge would need to demonstrate that the AD is unreasonable, not based on evidence, or procedurally flawed. Given that the AD is based on a confirmed failure and a Transport Canada directive, the scope for challenge is narrow.

The AD does not confer a right to compensation or cost recovery. The operator bears all compliance costs. The AD also does not mention any right to an extension of the compliance time. If the operator cannot source replacement PCUs within the 2000-hour or 12-month window, they would need to seek a variation from CASA under CASR Part 39, which may or may not be granted.

The AD is issued under the Civil Aviation Act 1988 and the Civil Aviation Safety Regulations 1998 (CASR). Part 39 of CASR governs the issuance, amendment, and compliance with airworthiness directives. Non-compliance is a breach of the regulations and can attract enforcement action.

Civil penalties under the Civil Aviation Act for non-compliance with an AD can be significant. For an individual, the maximum penalty may be up to $11,100 (indexed) per contravention; for a body corporate, up to $55,500. Contraventions are strict liability, meaning the regulator does not need to prove fault, only that the requirement was not met.

Administrative action is more likely to be the immediate consequence. CASA may issue a Notice of Proposed Suspension or Cancellation of the aircraft’s certificate of airworthiness. An aircraft that does not comply with an AD cannot be considered airworthy, and operating it would be unlawful. CASA may also issue a direction to ground the aircraft until compliance is achieved.

Criminal proceedings are possible if non-compliance is deliberate or reckless, or if the aircraft is operated in a manner that creates a serious risk to safety. The Civil Aviation Act provides for imprisonment in serious cases, but that is rare in the context of AD compliance failures.

Enforcement history is not provided in the source. No specific cases or penalties are mentioned. The AD itself is the only enforcement action described - it is the regulator’s response to a safety issue. It is reasonable to infer that CASA expects compliance within the required timeframes. An operator who delays the initial inspection beyond 30 days would be in breach even if no safety incident occurs.

The practical risk for operators is that an aircraft found with an overdue AD could be grounded during a ramp check or routine surveillance audit. This could lead to lost revenue, reputational damage, and possible follow-up enforcement.

The AD is signed by a delegate of CASA on 22 May 2009 and becomes effective on 2 July 2009. This 41-day gap between signing and effectiveness gives operators some lead time to prepare for the initial inspection.

The AD does not exist in isolation. It interacts with several layers of aviation regulation.

Transport Canada AD CF-2009-16. The source notes that Transport Canada issued its own directive on 20 April 2009. CASA’s AD is a direct adoption of that foreign directive. This is common under the bilateral agreements between Australia and Canada regarding acceptance of airworthiness approvals. For operators with aircraft on both the Canadian and Australian registers, compliance with one AD will generally satisfy the other, provided the actions are the same. However, the CASA AD is a separate legal instrument, and an operator must ensure compliance specifically with the Australian version if the aircraft is on the Australian register.

Civil Aviation Safety Regulations Part 39 (Airworthiness Directives). Part 39 sets out the legal framework for ADs. It provides the authority for CASA to issue ADs, sets the requirements for operators to comply, and provides mechanisms for requesting variations or alternative means of compliance. This AD is issued under that Part. Operators should be aware that Part 39 also requires that AD compliance records be kept in the aircraft’s continuing airworthiness records system.

Maintenance regulations. The removal and replacement of PCUs must be performed in accordance with approved maintenance data. The AD references Bombardier SB 84-27-32 as approved data. However, the underlying maintenance must also comply with Part 145 (maintenance organisations) and Part 66 (licensing of maintenance personnel). A Part 145 organisation with appropriate ratings for the DHC-8-400 would normally be required.

Service bulletins and manufacturer’s instructions. The AD gives legal force to certain manufacturer documents: Bombardier All Operator Message No. 217B (for the daily check) and SB 84-27-32 (for replacement). Those documents become mandatory only by virtue of the AD. If the AD were withdrawn, the service bulletins would revert to being advisory. The AD ties the operator’s obligations to specific revisions and notes that alternatives may be accepted if approved by the Chief, Continuing Airworthiness of Transport Canada.

Other CASA ADs for the same aircraft type. There may be other ADs applicable to the DHC-8-400 that address other components. Compliance with this AD does not relieve the operator from complying with any other AD. Operators must manage all applicable ADs as part of their continuing airworthiness programme.

International reciprocity. Under the Chicago Convention and bilateral aviation safety agreements, ADs issued by the state of design (Transport Canada) are typically adopted by other states. CASA has chosen to issue its own AD rather than simply refer to the Canadian one. This ensures the directive is enforceable under Australian law and aligns with Australian regulatory procedures.

The source document is the original issuance of AD DHC-8/148. It does not reference any prior AD on the same subject, nor does it mention any amendments to itself. The effective date is 2 July 2009, and it was signed on 22 May 2009.

No amendment history is available from the source. The AD does not contain a serial number of an earlier revision or note that it supersedes another directive. It appears to be the first CASA directive addressing the elevator PCU shaft issue for DHC-8-400 aircraft with serial numbers 4135-4149.

The background section states there was “one case reported” of tailstock shaft failure. That case presumably occurred after the aircraft entered service, and Transport Canada, as the design authority, conducted the investigation. The sequence of events likely involved: (1) discovery of the failure; (2) Bombardier issuing an All Operator Message (AOM 217B) in April 2007, which is referenced for the daily check; (3) Bombardier issuing a service bulletin (SB 84-27-32) in May 2007; (4) Transport Canada issuing AD CF-2009-16 in April 2009; and (5) CASA issuing this AD in May 2009, effective July 2009.

The AD does not mention any subsequent amendments, such as a revision to extend compliance times, add serial numbers, or change the suspect PCU list. It is possible that later amendments were issued after the source date, but they are not part of this deep dive.

The lack of amendment history means the operator must rely on the original text. Over time, operators should check CASA’s AD database (https://www.casa.gov.au/aircraft/airworthiness-directives) for any later amendments or superseding directives. A directive may be amended if more suspect PCUs are discovered, if the replacement timeline proves too short, or if new information changes the risk assessment.

The source does not mention any litigation related to AD DHC-8/148. This is not surprising. Airworthiness directives are rarely litigated, for several reasons.

First, the cost of challenging an AD in the Administrative Appeals Tribunal (AAT) or the Federal Court often outweighs the compliance cost, especially given the narrow applicability (15 aircraft). Operators of such a small fleet are unlikely to spend money on legal proceedings when they can simply comply.

Second, the courts give substantial deference to aviation safety regulators on technical matters. A challenge would need to demonstrate that the AD was irrational, based on no evidence, or procedurally unfair. The AD is grounded in a confirmed failure and a material defect, so the evidentiary basis is solid.

Third, compliance with an AD is a condition of the aircraft’s certificate of airworthiness. Non-compliance effectively grounds the aircraft, which imposes its own economic penalty. An operator who challenges the AD must continue to comply or seek a stay, which is rarely granted in safety matters.

No reported cases in Australian aviation law databases name AD DHC-8/148. There is no indication that any affected operator sought review. It is likely that the AD was complied with by the relevant parties without dispute.

If litigation had arisen, it would likely involve an operator claiming that the AD was too burdensome or that the suspect PCU list was inaccurate, or that CASA had failed to consider alternatives such as enhanced inspections instead of replacement. Alternatively, an operator might have argued that the AD was not necessary because the risk was adequately mitigated by the triple redundancy. However, the AD itself acknowledges the redundancy but argues that the collateral damage risk, including potential hydraulic line damage, makes replacement necessary.

In summary, the litigation history is nil. This deep dive does not invent cases or speculate beyond the source. The absence of litigation is itself notable: it suggests the AD was accepted by operators and that compliance was achieved without court involvement.

Several aspects of this AD could catch an operator or maintenance organisation off guard.

The narrow applicability does not reduce compliance complexity. Because the AD applies to only 15 serial numbers, an operator must be absolutely certain that their aircraft is not one of them. Mistakenly assuming the AD does not apply could lead to non-compliance. The aircraft serial number, not the registration, determines applicability. A change in registration does not change the obligation.

The inspection deadline is only 30 days. The operator must physically access the PCUs and read their serial numbers. If the aircraft is in a heavy maintenance check, in storage, or overseas, the operator must still meet the deadline. Extensions are not mentioned. If the aircraft cannot be accessed in time, the operator should contact CASA to request a variation or alternative means of compliance before the deadline expires.

The daily check is onerous. Requiring a check before each day’s flying imposes a recurring operational burden. It requires trained personnel to perform the check each day, which adds time and cost, especially for aircraft that operate multiple sectors per day or are based at outstations. The AD says the check can be done per AOM 217B, but the operator must have that document and train staff.

The replacement timeline is the earlier of 2000 flight hours or 12 months. An operator who flies 2000 hours in, say, 10 months must replace the PCUs in 10 months, not 12. That may be a surprise if the operator assumes the full year is always available. Also, the 2000-hour count runs from the effective date, not from the date of the initial inspection. An aircraft that flies 2000 hours within the first 6 months would need replacement within 6 months.

Replacement PCUs may not be readily available. The suspect list covers 88 PCUs. Each of the 15 aircraft requires up to 6 replacements, for a potential demand of 90 PCUs. The supply chain may be strained. An operator who delays ordering may be unable to obtain a compliant PCU before the deadline.

The AD does not specify record-keeping requirements. But under Part 39, the operator must keep records of compliance, including serial numbers inspected, daily check logs, and replacement details. Failure to keep adequate records could make it difficult to prove compliance during an audit.

The service bulletin revisions matter. The AD accepts SB 84-27-32, original issue dated 1 May 2007, and Revision A dated 18 January 2008. It also accepts later revisions approved by Transport Canada. An operator relying on a later revision must ensure it is approved by Transport Canada; otherwise, the work may not be accepted.

The AD applies to all six elevator PCUs, not just the ones found with suspect serial numbers. Even if only one PCU is suspect, all six that are suspect (i.e., in the range without “A”) must be replaced. If some are not suspect, they can remain. But it would be inefficient to replace only the suspect ones and leave others, because the non-suspect units may later fail from the same defect if they are within the suspect range but have been reworked. The AD does not require replacement of non-suspect units unless they are individually suspect.

The AD does not address cost recovery or warranty. Bombardier may provide replacement PCUs under warranty, but the AD is silent. The operator must negotiate with the manufacturer.

Compliance involves a structured, documented process that can be integrated into the operator’s continuing airworthiness management system.

Step 1: Determine applicability. Obtain the manufacturer serial number of each DHC-8-400/401/402 operated. If any falls between 4135 and 4149 inclusive, the AD applies. The aircraft must be on the Australian register or operated by an Australian operator. If no aircraft matches, no action is required, but the operator should document this determination for audit purposes.

Step 2: Identify PCU serial numbers. Within 30 days after 2 July 2009 (i.e., by 1 August 2009), gain access to the six elevator PCUs (P/N 390600-1007). Record each PCU serial number. For each, note whether it bears suffix “A”. If all six PCUs lack a suspect serial number (i.e., none matches the list in requirement 1.a.) or all have suffix “A”, compliance is complete. Record this finding and retain the record.

Step 3: If suspect PCUs are found. If one or more PCUs has a serial number in the suspect range without “A”, the operator must begin the daily operational check. Obtain Bombardier Q400 All Operator Message No. 217B, dated 26 April 2007. Follow the procedures in Appendix A, B, or C for the daily check. The check must be performed before the first flight of each day. Keep a log of each check, including date, time, personnel, and result. Continue these checks until the suspect PCUs are replaced.

Step 4: Plan and execute replacement. Order replacement PCUs that are either outside the suspect serial range or have suffix “A”. Obtain Bombardier Service Bulletin 84-27-32, Revision A (or later Transport Canada-approved revision). Arrange for a Part 145 maintenance organisation with DHC-8-400 capability to remove each suspect PCU and install a compliant unit. The work must include subsequent rigging of the elevators per the SB. The replacement must be completed no later than 2000 flight hours after 2 July 2009 or 2 July 2010, whichever comes first.

Step 5: Record compliance. Enter the AD compliance in the aircraft’s continuing airworthiness records. Include: the AD number, the effective date of compliance, serial numbers of PCUs before and after replacement, date of daily check commencement and cessation, and references to the service bulletin used. Retain all records for at least the life of the aircraft.

Step 6: Post-replacement. After all suspect PCUs are replaced, the daily check duty ceases. No further action is required unless the AD is later amended to cover additional serial numbers or to require recurring actions.

Practical tips. Start the replacement planning immediately after the initial inspection, even if the check reveals suspect PCUs. The 2000-hour or 12-month window can be consumed rapidly. Contact Bombardier or local distributor early to secure replacement parts. For aircraft that fly few hours, the 12-month limit may be the binding constraint; for high-utilisation aircraft, the flight hour limit may expire sooner. Monitor both.

If the operator cannot meet the replacement deadline due to parts unavailability, they should apply to CASA under CASR 39.044 for an extension or alternative means of compliance. The application should include evidence of efforts to source parts and a plan for continued safe operation (e.g., increased inspection frequency). CASA may grant an extension if safety is not compromised, but it is not guaranteed.