AD/B717/25 - Power Conversion Distribution Unit

Several technical and regulatory concepts are central to understanding this directive. Power Conversion Distribution Unit (PCDU) is the component at issue. It is an electrical unit that converts and distributes power to various aircraft systems. The directive identifies a specific part number threshold (762904E) as the cut-off; units with a part number at or above that threshold are considered acceptable without modification. The concept of part number determination is critical: the AD allows a records review in lieu of physical inspection if the part number "can be conclusively determined" from maintenance records. This reflects a regulatory trust in documentary evidence, but the operator bears the risk if the record is erroneous. Service Bulletins (SBs) are manufacturer-issued instructions for modifications or inspections. This AD references two tiers: Boeing Alert Service Bulletin 717-24A0028, which is the primary modification instruction, and a series of Hamilton Sundstrand Service Bulletins (40EGS22P-24-3 through -9) that provide the detailed procedures for subtasks such as reworking the Transformer Rectifier Unit (TRU), modifying printed wiring board assemblies, adding ground wires, and installing new firmware. The concept of an Alternate Method of Compliance (AMOC) is important. The AD states that later revisions of the Hamilton Sundstrand SBs, if approved by the FAA as an AMOC to FAA AD 2007-19-03, are acceptable for compliance with the Australian AD. This creates a cross-jurisdictional delegation: an operator may use a revision that the FAA has approved, even if that revision is not explicitly listed in the AD table. However, the operator must confirm that the FAA approval exists and that the revision is indeed an AMOC. The compliance time is defined as 20 months after the effective date for stages 1 and 2.a, and "before or concurrently with" 2.a for stage 2.b. This is a dual deadline: the (b) actions have no independent deadline but must be done no later than when the ASB modification is performed. Another key concept is effective date: the AD "becomes effective on 25 October 2007". This is the trigger date from which the 20-month clock starts. The instrument does not create a grace period before that date; rather, it sets a future date after which compliance is measured. The delegated legislation nature of the AD is also relevant: it is issued by a delegate of the Civil Aviation Safety Authority (CASA) under the Civil Aviation Act 1988 (Cth) and the Civil Aviation Safety Regulations 1998. It has the force of law, distinct from a manufacturer’s recommendation. The concept of regulatory incorporation by reference applies: the AD incorporates the Boeing ASB and the Hamilton Sundstrand SBs as mandatory instructions. These documents are not reproduced in the AD; operators must obtain them separately. Finally, the background identifies a specific failure mode: loss of an electrical bus and burning odour leading to potential loss of all flight displays and an emergency landing. This frames the risk the AD aims to mitigate.

The primary persons and entities affected are the registered operators of Boeing 717-200 aeroplanes on the Australian register. The applicability section states "Model 717-200 aeroplanes" without qualification; all such aircraft on the register are subject to the AD if they have a PCDU below part number 762904E. This affects airline operators, charter operators, and any entity that holds the certificate of registration for the aircraft. Maintenance organisations that perform work on these aircraft are directly affected because they must be capable of performing the modification in accordance with the specified service bulletins. They must also ensure their staff are trained on the Hamilton Sundstrand SBs and that they have access to the correct revisions. The AD does not specify which maintenance approvals are required, but under Australian regulations, only appropriately authorised maintenance organisations (such as those holding a Part 145 approval or equivalent) can perform airworthiness directive compliance work. Engineering and planning staff at the operator must track the compliance deadline, schedule the modification, and ensure the concurrent requirement (2.b with 2.a) is managed. Lessors and financiers may also be affected indirectly: an aircraft that is not compliant with mandatory ADs may not be airworthy, which can affect lease agreements, insurance, and asset value. Suppliers of parts and service bulletins may see increased demand for the required parts (e.g., new firmware, spacers, wiring harnesses). The directive affects a limited population: only Boeing 717-200s, which is a relatively small fleet. However, the cost per aircraft could be significant depending on labour hours and parts. The AD does not exempt aircraft used in charter or private operations; all are caught equally. The Civil Aviation Safety Authority itself is affected in that it must monitor compliance and enforce the directive, which consumes regulatory resources. Overseas operators who fly into Australia under foreign registration are not directly affected by this CASA AD unless the aircraft is on the Australian register; however, the equivalent FAA AD would apply to US-registered aircraft. The AD also affects firms that produce or sell the Hamilton Sundstrand service bulletins; they become required reading for Australian maintenance organisations. There is no provision for phasing or exemptions for operators with low utilisation; the 20-month deadline is absolute. The compliance burden falls most heavily on operators with multiple aircraft, who must coordinate the work across the fleet to avoid simultaneous grounding.

The source imposes several clear duties and creates a few limited rights. The primary duty is on the registered operator: to ensure compliance with Requirements 1 and 2 within the specified timeframes. This includes the duty to inspect or review records to determine the PCDU part number. If the part number is below 762904E, there is a duty to modify the PCDU per Boeing ASB 717-24A0028 Rev 1 and to accomplish the Table 1 actions per the specific Hamilton Sundstrand SBs. The duty to carry out Requirement 2.b "before or concurrently with" Requirement 2.a imposes a scheduling obligation: the operator cannot perform the ASB modification and defer the rework or firmware updates to a later time. The duty also includes ensuring that any prior modification (before the effective date) meets the standard set out in Note 1: it must have been done in accordance with Boeing ASB 717-24A0028 dated 24 November 2004 (the earlier revision). The operator has a right to rely on maintenance records to determine the part number, provided the part number can be conclusively concluded from that review. This is a significant concession because it avoids physical disassembly. However, if the record is ambiguous, physical inspection is required. The operator also has a right to use later revisions of the Hamilton Sundstrand SBs that have been approved by the FAA as an AMOC to the equivalent FAA AD. This right is conditional: the revision must be specifically approved as an AMOC, and the operator should hold evidence of that approval. The AD does not give CASA the power to approve alternative methods directly; it merely accepts FAA-approved AMOCs. This limits the operator's flexibility: if the FAA has not approved a later revision, the operator must use the exact revision listed in the table. The duty to perform the modification within 20 months is absolute; there is no provision for extension based on parts availability or scheduling difficulties. The operator also has a duty to maintain records of compliance, as would be expected under general airworthiness regulation, although the AD itself does not specify record-keeping requirements. The right to operate the aircraft before the compliance deadline is not a right conferred by the AD; it is a default position: the AD does not ground the aircraft immediately, so operation during the compliance period is lawful as long as the AD is not being breached. The AD does not create any right to compensation from CASA for the cost of compliance. The operator's right to choose a maintenance organisation is not restricted by the AD, but the organisation must be capable of following the manufacturer's procedures and holding the required parts. There is no right to a hearing before the AD takes effect; it is a legislative instrument.

The AD itself does not contain a penalty clause. The source document is a legislative instrument made under the Civil Aviation Act 1988 (Cth) and the Civil Aviation Safety Regulations 1998 (CASR). Under that regulatory framework, failure to comply with an airworthiness directive is an offence. The relevant penalty provisions are not in this AD but are found, for example, in regulation 42.15 of the Civil Aviation Safety Regulations (or the applicable sections at the time). Typically, operating an aircraft that does not comply with an applicable airworthiness directive is a strict liability offence that can attract substantial fines for individuals and corporations. Additionally, CASA can issue infringement notices (on-the-spot fines) for less serious breaches. The AD does not specify the monetary amount, but CASR provides for maximum penalties that can be hundreds of penalty units for corporations (a penalty unit is currently $313, so 500 units would be $156,500). For more serious or repeated breaches, CASA may seek criminal prosecution, though that is rare. Beyond financial penalties, CASA has enforcement powers including the ability to issue a direction to ground the aircraft, suspend or cancel the airworthiness certificate, or impose conditions on the certificate of registration. The AD's enforcement relies on the operator's self-reporting and on CASA's surveillance activities, such as ramp inspections and maintenance record audits. A detected non-compliance could also affect the operator's maintenance organisation approvals or lead to increased scrutiny. The AD does not provide for a defence of ignorance or parts unavailability; the only way to lawfully operate after the compliance deadline is to have completed the required work. If an operator cannot obtain the necessary parts or schedule the modification in time, the aircraft must be grounded or a ferry permit obtained (which CASA may grant under certain conditions). The AD does not mention amnesty periods or late compliance. The enforcement burden is on the operator to prove compliance if audited, since the AD imposes a duty. The AD also has an international dimension: because it mirrors an FAA AD, Australian operators who also operate in the US or under FAA oversight may be subject to enforcement by the FAA for the same non-compliance. The spectre of enforcement is a strong incentive to comply, but the costs of compliance (labour, parts, downtime) are immediate and certain, while the risk of detection is probabilistic. This creates an incentive for operators to assess the likelihood of being caught against the cost, though safety-conscious operators will comply regardless.

The AD does not exist in isolation. It is made under the Civil Aviation Act 1988 (Cth) and the Civil Aviation Safety Regulations 1998 (CASR). It is a form of delegated legislation specific to airworthiness. Other Commonwealth laws that intersect include the Competition and Consumer Act 2010 (Cth), which may apply if the modification requires parts that are subject to anti-competitive conduct, but that is peripheral. The AD interacts with the Australian Maintenance Regulations (especially CASR Part 42 and Part 145) which govern continuing airworthiness and maintenance organisation approvals. The AD effectively mandates a modification that must be recorded in the aircraft's maintenance records as a mandatory directive. The AD also interacts with foreign airworthiness directives. The source explicitly references FAA AD 2007-19-03 and states that later revisions of the Hamilton Sundstrand SBs approved as AMOC to that FAA AD are acceptable for this Australian AD. This creates a cross-recognition framework: an operator may rely on FAA regulatory action to satisfy Australian requirements without separate CASA approval. However, the AD does not incorporate the FAA AD itself; it only borrows the AMOC mechanism for the SBs. If the FAA later supersedes or revokes its AD, the Australian AD remains in force unless amended. The interaction with the Boeing 717 maintenance manual and the aircraft's approved maintenance program (AMP) is also relevant: the modifications may require updates to the AMP or changes to scheduled maintenance tasks. The AD does not override the aircraft type certificate or other design approvals; it is an addition to the existing airworthiness limitations. The AD also interacts with state or territory laws only to the extent that workers' compensation or occupational health and safety laws apply to the maintenance work itself (e.g., safe handling of electrical components). The AD has no direct interaction with privacy, telecommunications, or financial services laws. If the aircraft is leased or financed, the lease or loan agreement may require compliance with all mandatory ADs. The AD's effect on the aircraft's export airworthiness status should also be considered: an aircraft without AD compliance cannot be issued an Australian export certificate of airworthiness. Finally, the AD interacts with CASA's enforcement policy which guides how non-compliance is handled. In sum, the AD adds a layer of mandatory modification to a web of existing regulatory obligations.

The source document as provided contains no explicit textual history of amendments. The AD number is AD/B717/25 and the issue number is 11/2007. The instrument is signed on 14 September 2007 and becomes effective on 25 October 2007. There is no indication that this AD itself is an amendment to an earlier AD; rather, it appears to be the original issue for this subject. However, the existence of Notes 1, 2, and 3 suggests that the AD's requirements were influenced by earlier versions of service bulletins and the corresponding FAA AD. Specifically, Note 1 references a prior version of Boeing ASB 717-24A0028 dated November 2004, and Note 2 references an earlier revision of the Hamilton Sundstrand SB. This indicates that the manufacturer's instructions evolved, and the AD adopted Revision 1 of the Boeing ASB. The AD also contemplates that later revisions of the Hamilton Sundstrand SBs may be used under FAA AMOC approval, which is a dynamic element. But the AD itself has not been amended; it is a snapshot in time. Since the effective date in 2007, CASA may have subsequently amended or superseded this AD through later directives. The source does not show any such amendments. As a legislative instrument, any amendment would be published as a separate document (e.g., an AD/B717/25 Amendment 1) or a superseding AD. The absence of amendment history in the source does not mean none occurred; it means this copy is the original. For operators, it is critical to check the current CASA website or database for any amendments or superseded status. The AD references FAA AD 2007-19-03, which was issued on 5 September 2007, close in time to this AD. The FAA AD may have since been superseded by newer amendments, but that does not automatically affect the Australian AD unless CASA takes action. The AD's cross-reference to later revisions of Hamilton Sundstrand SBs via FAA AMOC means that the effective content of the compliance instructions can change without a formal amendment to the AD itself, as long as the FAA approves a new revision. This is a form of ambulatory incorporation. The AD's wording does not allow for other forms of informal amendment. In summary, the source shows no textual amendment history; the AD was issued as a final instrument in 2007.

The source does not mention any litigation or court decisions concerning this specific AD. Airworthiness directives are rarely litigated directly because they are legislative instruments that usually do not give rise to private rights of action against the regulator. Challenges to the validity of an AD would be limited to judicial review under the Administrative Decisions (Judicial Review) Act 1977 (Cth) or the common law, but the grounds for such a challenge are narrow. The AD's background refers to FAA reports of failed PCDUs, which would have been investigated technically, not litigated. There is no reference to any accident or incident investigation report, although the background strongly implies that the issued AD was prompted by in-service events. It is possible that those events led to litigation between operators and Boeing or Hamilton Sundstrand under contract or tort law, but that would be separate from this AD. The AD itself has not, to public knowledge, been the subject of appeal to the Administrative Appeals Tribunal or the Federal Court. There is also no indication that the Australian Human Rights Commission or the Office of the Australian Information Commissioner has been involved. Enforcement actions for non-compliance with this AD may have occurred, but those would be individual matters, not challenges to the AD. The lack of litigation history is typical for a technical safety directive that restricts operations; operators generally comply rather than litigate because the cost of challenge is high and the safety rationale is strong. Moreover, the AD is a time-limited instrument: it required compliance within 20 months, so any dispute about its validity would likely have been resolved or become moot within that period. In the absence of any mention in the source, we must conclude there is no known litigation history. This does not preclude the existence of private disputes, but the source does not evidence them. For the purposes of this deep dive, we report none.

Several aspects of the AD could trap the unwary operator. First, the part number threshold: the AD states that if the part number is "762904E or higher, no further work is required." The term "higher" in a part number context could be ambiguous. Part numbers are alphanumeric; a number like "762904F" would clearly be higher, but what about "762904D"? The operator must know the correct ordering. Boeing's parts catalogue should clarify, but the AD does not define the hierarchy. Second, the compliance period for Requirement 2.b is deceptively simple: it must be done "before or concurrently with" Requirement 2.a. If an operator does the 2.a modification but delays the 2.b tasks, they are non-compliant from the moment 2.a is completed. This creates a trap for those who might schedule the modifications in separate hangar visits. Third, the AD allows reliance on maintenance records for part number determination only if the part number "can be conclusively determined" from those records. If the record is ambiguous (e.g., shows multiple part numbers or is missing a suffix), the operator must physically inspect. The cost of an unnecessary inspection could be avoided by careful record analysis. Fourth, Note 1 allows acceptance of a modification done before the effective date using the earlier Boeing ASB (November 2004). But the operator must have evidence that the work was done using that specific bulletin, not some other method. If the records show only "PCDU modified per Boeing bulletin" without the date, the AD does not accept it. Fifth, the table of Hamilton Sundstrand SBs includes specific dates. The AD then says that later revisions approved by FAA as AMOC are acceptable. But the operator must verify that FAA approval exists. The AMOC approval applies to the equivalent FAA AD (2007-19-03), not necessarily to the Australian AD. The AD states it is acceptable "for compliance with the equivalent Requirements of this Directive." That is a close linkage, but if the FAA later revokes the AMOC or issues a different AMOC, the Australian status becomes uncertain. Sixth, the AD covers multiple discrete tasks, each with its own SB. An operator might miss one of the less obvious tasks, such as "check and apply torque seal to fasteners on the TRU assembly and to PCDU internal fasteners." That is easily overlooked if the engineer focuses only on the major modifications. Seventh, the AD does not state a specific date by which the Table 1 actions must be completed beyond "before or concurrently with" Requirement 2.a. If an operator performs Requirement 2.a on day 599 of the 20-month period, the Table 1 actions must be done by that day. But if the operator defers the ASB modification, they also defer the Table 1 actions, which may delay the overall compliance. Eighth, the AD may be superseded by later CASA directives that reference newer SB revisions. Operators must check current CASA records for any amendments. Ninth, the AD is silent on what happens if the PCDU has been previously modified by an STC or a different manufacturer's SB that also affects the PCDU. The AD does not provide for credit for equivalent modifications; only the specific Boeing ASB and Hamilton Sundstrand SBs are accepted. Tenth, the AD uses the term "rework" and "modify" without defining exactly what constitutes completion. The SB must be followed step by step.

Compliance with AD/B717/25 requires a systematic approach. Step 1: Identify the affected fleet. Locate all Boeing 717-200 aeroplanes on the operator's Australian register and confirm they are within the applicability. Step 2: Determine PCDU part number. For each aircraft, inspect the PCDU nameplate or review maintenance records to find the part number. The AD allows a records review only if the part number can be "conclusively determined". If the record is unclear, perform a physical inspection. Document the method used and the result. Step 3: Assess threshold. If the part number is 762904E or higher (assuming alphanumeric ordering), stop; no further action is required for that aircraft. Document that the aircraft is compliant. If below, proceed. Step 4: Obtain the required service bulletins. Obtain Boeing Alert Service Bulletin 717-24A0028, Revision 1, dated 20 December 2005. Also obtain the following Hamilton Sundstrand Service Bulletins: 40EGS22P-24-3 dated 30 June 2000; 40EGS22P-24-4 Rev 1 dated 2 January 2002; 40EGS22P-24-6 dated 25 July 2002; 40EGS22P-24-7 dated 3 September 2003; 40EGS22P-24-8 dated 4 September 2003; 40EGS22P-24-9 dated 19 November 2003. Check whether any later revisions of these SBs have been approved by the FAA as an AMOC to FAA AD 2007-19-03. If so, the later revision may be used instead. Keep documentation of the FAA approval. Step 5: Plan the modification. The 20-month deadline starts from 25 October 2007. Schedule the aircraft for modification within that period. Note that Requirement 2.b must be performed before or concurrently with Requirement 2.a. Therefore, coordinate the hangar visit so that all tasks in the Boeing ASB and all Table 1 tasks are accomplished in one event, or ensure the Table 1 tasks are done before the Boeing ASB modification. Step 6: Perform the work. The work must be carried out by an appropriately authorised maintenance organisation. The engineer must follow the instructions in the service bulletins precisely. The Table 1 tasks include: reworking the transformer rectifier unit (TRU), reworking the W3 wiring harness, adding a ground wire to the TRU transformer, adding an insulated spacer to the PCDU top cover, installing new PCDU 186 firmware per two different SBs, modifying the top cover of the PCDU, modifying printed wiring board assemblies A4 and A5, and checking and applying torque seal to fasteners on the TRU assembly and PCDU internal fasteners. The SB for each task must be used. Document each task completed, including the SB revision used. Step 7: Verify compliance. After modification, confirm that the PCDU now meets the AD requirements. There is no retest requirement specified, but the manufacturer's bulletin may call for functional checks. Step 8: Update maintenance records. Record the AD number, the compliance date, the part number after modification (if changed), and the SBs used. Enter the AD in the aircraft's continuing airworthiness record system. Step 9: Report compliance. CASA may not require a direct report, but the records must be available for inspection. Operators should also consider notifying CASA if using an FAA-approved later SB revision, though the AD does not require prior approval. Step 10: Monitor for amendments. Check CASA's website periodically for any amendments to AD/B717/25 or replacement directives. Also monitor FAA AD 2007-19-03 for any changes to AMOC approvals that might affect Australian compliance. Cost considerations: The operator must budget for parts, labour, and possible rental of replacement aircraft during downtime. The AD does not provide for cost recovery. Risk management: If parts are unavailable, contact Boeing and Hamilton Sundstrand early. If the 20-month deadline is at risk, seek a ferry permit or, in extreme cases, apply to CASA for an individual exemption, though that is unlikely to be granted without compelling reasons.