AD/BEECH 77/16 - Circuit Breaker Toggle Switches

Applicability and parts: The Directive applies to Beechcraft 77 model aeroplanes serial WA-1 through WA-312 that have any circuit breaker toggle switch with P/N 35-380132-1 through 35-380132-53 installed (see "Applicability: Aeroplane models and serial numbers listed in Table 1 that have any circuit breaker toggle switch with a part number (P/N) 35-380132-1 through 35-380132-53 installed"). The core technical swap is a one-for-one replacement of those older part numbers with "improved" circuit breaker toggle switches, P/N 35-380132-61 through 35-380132-113, "as specified in Raytheon Aircraft Company (RAC) Recommended Service Bulletin SB 24-3735, Issued: August 2005."

Requirement structure: There are two discrete operative requirements. Requirement 1 is the mandatory replacement, subject to "Unless previously accomplished" (which preserves credit for earlier compliance). Requirement 2 is a prohibition on installing the older P/Ns either as initial fits or as replacement spares. The Directive also allows procedural flexibility: "Later revisions of the above SB, approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2008-13-17, are considered acceptable for compliance with the equivalent Requirements of this Directive." The AD therefore ties compliance documents to the RAC SB and to FAA AMOC approvals.

Timing and effective date: The Directive "becomes effective on 25 September 2008" and sets the compliance period for Requirement 1 as "within the next 24 months after the effective date of this Directive." That establishes a final compliance deadline of 25 September 2010. The Directive explicitly notes that this extends the FAA's final compliance time (which it states was 6 August 2009) by 13 months.

Safety rationale and scope: The background text states the FAA "has received reports of certain circuit breaker toggle switches ... overheating" across a set of Beech models including the 77, and that "Failure of the circuit breaker toggle switch could result in smoke in the cockpit and the inability to turn off the switch." The Directive follows the FAA intent but modifies timing and acknowledges prior accomplishment possibilities. The linkage to FAA AD 2008-13-17 is explicit ("FAA AD 2008-13-17 Amdt 39-15580 refers"), so the Directive positions itself as a national implementation that references and accepts FAA documentation and AMOCs.

Document provenance: The Directive records that a draft was posted on CASA's internet site on 9 July 2008 and "no comments or objections have been received by CASA" as of the date the Directive was made. It is signed by the CASA delegate on 8 August 2008 and made effective 25 September 2008.

Aircraft and operators: The immediate, named class of persons affected are those who operate or maintain Beechcraft 77 (Skipper) series aeroplanes with serial numbers WA-1 through WA-312 that "have any circuit breaker toggle switch with a part number (P/N) 35-380132-1 through 35-380132-53 installed." Owners, operators, maintenance organisations and certifying staff who are responsible for the continued airworthiness of those specified aeroplanes will need to determine whether the listed P/Ns are present and, if so, arrange replacement with the specified improved P/Ns.

Parts suppliers and maintenance facilities: The ban on installation of the older P/Ns as "an initial fit or as a replacement spare" means parts suppliers, spares managers and line maintenance organisations holding stocks of P/N 35-380132-1 to -53 need to update procurement and stocking practices to avoid using those parts on affected aeroplanes. Where the older P/Ns remain in inventory, facilities must ensure they are not fitted to applicable aeroplanes.

Manufacturers and service bulletin authors: Raytheon Aircraft Company's Recommended Service Bulletin SB 24-3735 (Issued August 2005) is the technical document specified for carrying out the required replacement. The Directive accepts "later revisions" of that SB only if they are "approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2008-13-17." That places the FAA's AMOC approval process as the gatekeeper for acceptable technical variations to the RAC SB in relation to compliance.

Regulatory bodies: Civil Aviation Safety Authority (CASA) is the issuing authority; the Directive expressly follows the intent of the FAA AD and references FAA AD 2008-13-17. CASA posted a draft for comment and recorded no objections. CASA's delegate signed the Directive on 8 August 2008 and set the effective date. The Directive therefore binds relevant parties under CASA's regulatory framework, at least in the operational sense that the Directive prescribes mandatory action; the Directive itself does not, in the text supplied, enumerate enforcement steps or penalties.

Other Beech models and cross-jurisdictional operators: The background notes that FAA reports of overheating concerned multiple Beech models beyond the 77, and the FAA AD referenced covers a broader set. Operators of other Beech models should note the linkage to FAA reporting, but this particular Directive is explicitly limited to model 77 serial WA-1 through WA-312 with the specified P/Ns.

Timing and prior accomplishment: The Directive explicitly allows "Unless previously accomplished" when requiring replacements. That means owners/operators who implemented RAC SB 24-3735 earlier (including its 2005 issue) may be credited and will not be required to re-do an already-completed replacement. Parties with prior records will need to demonstrate that the replacement was completed in accordance with the RAC SB or an FAA-approved AMOC.

Who bears practical cost: The Directive prescribes physical replacement of parts in individual aircraft; it does not allocate funding. As the mandatory action applies to each affected aeroplane, operators or owners will bear the direct costs of parts and labour to accomplish replacement, and parts suppliers will bear the commercial costs of ceasing supply of the older P/Ns as replacement spares for affected aeroplanes. The Directive itself does not provide for compensation or supplier reimbursement.

Duties set by the Directive: The Directive imposes two clear duties. Duty 1 (Requirement 1) is to replace "all circuit breaker toggle switches P/N 35-380132-1 through 35-380132-53" with the improved P/Ns "35-380132-61 through 35-380132-113, as applicable," following the procedure in RAC Recommended Service Bulletin SB 24-3735 (Issued August 2005), "unless previously accomplished." Duty 2 (Requirement 2) is a flat prohibition: "Circuit breaker toggle switches P/N 35-380132-1 through 35-380132-53 may not be installed on any aeroplane as an initial fit or as a replacement spare." The compliance timing duty is also explicit: Requirement 1 must be done "within the next 24 months after the effective date of this Directive," and Requirement 2 must be met "before further flight after the circuit breaker toggle switch has been replaced in accordance with Requirement 1."

Rights and compliance flexibility: The Directive affords two limited flexibilities. First, it recognises "Unless previously accomplished" which allows credit for prior completion of the RAC SB replacement. Second, it permits use of "Later revisions of the above SB" provided those revisions have been "approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2008-13-17." Thus, while the Directive prescribes a specific RAC SB and part numbers, it accepts FAA-AMOC-approved variations to the technical method.

Document reliance: The Directive explicitly ties the required technical actions to an external document: "as specified in Raytheon Aircraft Company (RAC) Recommended Service Bulletin SB 24-3735, Issued: August 2005." This creates a duty to use that SB (or an FAA-AMOC-approved revision) as the procedural source for the replacement. Operators therefore have a duty to ensure that the work is performed "as specified" by that SB or an acceptable AMOC.

Evidence and record implications: The Directive allows prior accomplishment; therefore operators who claim credit must be able to show records demonstrating that replacement was done previously in accordance with the RAC SB or an FAA-approved AMOC. The Directive itself does not stipulate the form of evidence, but the recognition of prior accomplishment creates an implicit duty to retain and produce maintenance records showing the earlier work.

Interaction with FAA approvals: Duty-holders may elect to comply using later revisions of the RAC SB only if those revisions are FAA-AMOC-approved in the context of FAA AD 2008-13-17. That channels requests for alternative compliance methods through the FAA AMOC process rather than through CASA in this Directive. The Directive therefore links CASA compliance acceptance to FAA AMOC outcomes for permissive technical deviations.

No penalties enumerated in the text: The Directive does not, in the supplied text, state specific sanctions or penalties for non-compliance. It sets mandatory actions and dates and records that it "becomes effective on 25 September 2008," but does not itself append an enforcement or penalty schedule in the reproduced text.

Obligations on parts inventory: The prohibition in Requirement 2 creates an immediate duty for parts managers and maintenance organisations not to fit older P/Ns as initial fits or replacement spares on affected aeroplanes. That duty applies both to future installations and to removal/stocking practices.

What the Directive states and what it does not: The text of the Directive sets mandatory technical and timing requirements and specifies an effective date and compliance windows, but the supplied text does not set out any penalties, civil enforcement procedures, or criminal sanctions. The Directive includes operational requirements (replacement and non-installation of specified P/Ns) and notes effective and compliance dates, but in the reproduced content there is no explicit enforcement clause, penalty schedule, or reference to administrative sanctions.

Enforcement implications that follow from the Directive text: Because the Directive is issued by the Civil Aviation Safety Authority and is framed as an Airworthiness Directive with specific required actions and compliance deadlines (for example, Requirement 1 "Within the next 24 months after the effective date"), the practical effect is to create mandatory maintenance obligations for the identified aeroplanes. Parties required to ensure continued airworthiness will need to treat the Directive as a compliance obligation from the effective date. The Directive itself, however, does not enumerate how CASA will verify compliance, whether through audits, airworthiness inspections, mandatory reporting, or airworthiness certificate action. The text also does not spell out remedies for non-compliance.

Absence of penalty language in this text: Because the source document does not include enforcement mechanisms or sanctions, a reader should not assume particular penalty regimes from this Directive text alone. Any enforcement procedures or penalties that apply in practice would be those available under the broader regulatory framework administered by CASA or under civil aviation law, but those frameworks are not reproduced in this Directive text and therefore are not invoked or described here.

Administrative discretion and AMOC gateway: The Directive does expressly allow for alternative compliance method acceptance through FAA AMOC approval: "Later revisions of the above SB, approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2008-13-17, are considered acceptable for compliance with the equivalent Requirements of this Directive." That specifies a permissions pathway for technical variations, but the text does not identify any CASA-administered AMOC or CASA discretion in approving alternative technical methods; it defers to FAA AMOC approvals as the acceptable mechanism for later SB revisions.

Practical enforcement considerations implied by the text: Because the Directive accepts prior accomplishment ("Unless previously accomplished"), operators who claim credit will need to demonstrate that prior work was performed in accordance with the RAC SB or an FAA AMOC-approved revision. The burden of proof for prior accomplishment logically falls on the operator, but the Directive text does not prescribe the evidentiary standard or the process for CASA to assess credit. In the absence of enforcement text, operators should preserve maintenance records showing compliance to satisfy any oversight or audit enquiries.

Public consultation and signature: The Directive records that a draft was posted for public comment and "no comments or objections have been received by CASA," and it is signed by the CASA delegate. That procedural record is included in the Directive but does not alter the absence of specific enforcement terms in the Directive text itself.

Relationship to FAA AD and RAC SB: The Directive explicitly follows the intent of the FAA Directive AD 2008-13-17 and references it: "FAA AD 2008-13-17 Amdt 39-15580 refers." The Directive ties the technical method to Raytheon Aircraft Company Recommended Service Bulletin SB 24-3735 (Issued: August 2005) and makes later revisions acceptable only if they are "approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2008-13-17." That creates an explicit cross-reference and dependency: compliance under this CASA Directive must use RAC SB 24-3735 or an FAA-AMOC-approved revision, which embeds FAA AMOC outcomes into the Australian compliance pathway for this item.

National versus foreign regulatory timelines: The Directive states that it "follows the intent of the FAA Directive" but has been revised in two material ways relative to the FAA AD: (1) allowance for prior accomplishment, and (2) extension of the compliance time by 13 months relative to the FAA final compliance time. The text records the FAA's final compliance time as 6 August 2009, while CASA's Directive sets an effective date of 25 September 2008 and a 24-month compliance window, i.e. final compliance by 25 September 2010. This produces a divergence in timing between FAA and CASA obligations for operators of affected aircraft in different jurisdictions.

Acceptance of FAA AMOC as compliance device: By effectively saying that RAC SB later revisions that are FAA-AMOC-approved are "considered acceptable for compliance with the equivalent Requirements of this Directive," CASA is importing FAA AMOC outcomes into the Australian compliance regime for this matter. That reduces the need for a separate CASA AMOC process in respect of later RAC SB revisions, insofar as the FAA has granted AMOC for those revisions in connection with FAA AD 2008-13-17.

No explicit cross-reference to other Australian statutes in the text: The reproduced Directive does not cite specific Australian aviation statutes, regulations, or enforcement provisions, nor does it quote CASA's enabling legislation. The only external documents expressly referenced are the RAC Service Bulletin SB 24-3735 and FAA AD 2008-13-17. Therefore, readers should treat this Directive as a stand-alone technical mandatory instrument whose broader legal enforcement under Australian aviation law would be determined by statutory and regulatory frameworks not included in the text supplied.

Effect on parts supply chains and maintenance contracts: The prohibition on installation of older P/Ns as initial fits or replacement spares will interact with contractual arrangements between operators and maintenance/parts suppliers. The Directive therefore imposes an operational constraint that must be incorporated into maintenance contracts and procurement practices; however, the Directive text does not itself amend contract law or procurement statutes , it imposes a technical obligation that those contracts must respect.

Interaction with continuing airworthiness records practice: The Directive accepts prior accomplishment, which interacts with maintenance recordkeeping norms. Operators will need to rely on maintenance records as the mechanism to prove prior compliance. The Directive does not, however, state any specific format or documentary standard for proving prior accomplishment; the interaction with recordkeeping law or guidance is therefore consequential but not detailed in the Directive text.

Documents and dates recorded in the Directive: The Directive cites RAC Recommended Service Bulletin SB 24-3735, Issued: August 2005, as the technical document for the replacement. It also notes that a draft version of the CASA Directive was posted for public comment on 9 July 2008 and that "no comments or objections have been received by CASA" as of the date the Directive was made. The delegate of CASA signed the Directive on 8 August 2008, and the Directive is stated to "become effective on 25 September 2008."

Changes relative to the FAA AD as recorded: The Directive says it "follows the intent of the FAA Directive" but has been revised in two respects. First, it allows "prior accomplishment" because "the RAC service bulletin was issued in 2005 and may have already been accomplished." Second, it extends compliance "by 13 months until 25 September 2010," noting that "the final compliance time required by the FAA was 6 August 2009." The Directive therefore records an explicit departure from the FAA-determined compliance deadline.

Acceptance of later revisions: The Directive accepts "Later revisions of the above SB, approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2008-13-17," and treats those revisions as "acceptable for compliance with the equivalent Requirements of this Directive." That is an ongoing mechanism for amendment of the technical compliance method subject to FAA AMOC approvals.

No subsequent amendments recorded in the text supplied: The source text does not include any later amendments to AD/BEECH 77/16 beyond those described at the time of issue. There is no record in the reproduced content of subsequent CASA amendments, superseding ADs, revocations, or changes to the applicability or requirements after the effective date. The text does not state that the Directive was amended post-issue.

Versioning and traceability: The Directive ties required actions to specific P/N ranges and to a service bulletin issue date (SB 24-3735, Issued: August 2005). Traceability for compliance therefore depends on operators referencing that SB issue and any FAA-AMOC-approved later revisions. If operators rely on later revisions, those revisions must have FAA AMOC approval relative to FAA AD 2008-13-17 to be "considered acceptable" under this Directive.

Public consultation record: The Directive records that a draft was publicly posted and that no comments were received. That record forms part of the administrative provenance for this Directive as issued; the text does not record follow-up consultation or stakeholder-driven amendment after the final issue.

Litigation and case law references in the Directive: The reproduced Directive contains no references to litigation, court decisions, or judicial review concerning AD/BEECH 77/16. The Directive does not name any cases, and the public comment record included in the text states that "no comments or objections have been received by CASA" following the draft posting on 9 July 2008. There is no mention of appeals, enforcement proceedings, or judicial outcomes in the text supplied.

Absence of litigation does not imply absence of enforcement action: The Directive records administrative steps (draft posting, no comments, delegate signature) but does not disclose any subsequent enforcement actions, prosecutions, or disputes. Where litigation or proceedings may have occurred, such material is not present in the provided text.

Types of disputes that could arise (procedural observation only): While the Directive text does not describe litigation, practical disputes that could arise in analogous AD contexts (not asserted as present here) include disagreement over whether a prior accomplishment met the required standard, contestation of applicability to a particular serial-numbered aeroplane or P/N variant, or disagreement about whether a later SB revision constitutes an FAA AMOC. The Directive itself forecloses none of those dispute types, but the text does not record any resolution or adjudication of such matters. This paragraph does not assert that any of those disputes occurred; it notes the kinds of issues that might arise and that the Directive text provides no litigation history.

No recorded challenges to the Directive in the supplied text: The Directive's own record shows a public consultation period with "no comments or objections" and the Directive being signed and made effective. The document does not include mention of any requests for review, administrative appeals, or legal arguments directed at CASA in relation to this specific AD.

Narrow applicability by serial and part number: The Directive applies only to Beechcraft 77 aeroplanes in the serial range "WA-1 through WA-312" and only where "any circuit breaker toggle switch with a part number (P/N) 35-380132-1 through 35-380132-53 [is] installed." Operators must take care not to assume the AD applies to all Beech 77s or to other models; it applies only to that serial block and those P/Ns. Mistakes in serial-number identification or misreading of part numbers can lead to unnecessary work or non-compliance.

Prior accomplishment credit requires documentary proof: The Directive allows "Unless previously accomplished," but it does not specify how prior accomplishment is to be demonstrated. Operators claiming credit will need internally to preserve and be prepared to produce maintenance records showing that replacement was done in accordance with RAC SB 24-3735 or an FAA-AMOC-approved variant. The absence of specified evidentiary standards in the text means operators should retain clear logbook entries, parts invoices showing the improved P/Ns, and any service-release documentation.

Exact interpretation of Requirement 2 timing: Requirement 2 is a prohibition,"Circuit breaker toggle switches P/N 35-380132-1 through 35-380132-53 may not be installed on any aeroplane as an initial fit or as a replacement spare",and the Compliance note for Requirement 2 says "Before further flight after the circuit breaker toggle switch has been replaced in accordance with Requirement 1." That wording can be misread. The intended operational effect is that, once compliance action occurs, the older P/Ns must not thereafter be installed as initial fits or replacement spares. Maintenance personnel should interpret the prohibition as an ongoing ban on using those older P/Ns on the affected fleet, not as a transient requirement tied only to the immediate post-replacement flight. Clarify in internal maintenance instructions that the older P/Ns are to be excluded from future installations on affected aeroplanes.

Dependence on RAC SB and FAA AMOC approvals: The Directive requires replacement "as specified in" RAC SB 24-3735 (Aug 2005) but accepts later SB revisions only if the FAA has approved them as AMOCs to FAA AD 2008-13-17. Operators wishing to use a modified procedure must ensure that the RAC SB revision they intend to use has the relevant FAA AMOC approval; using an unapproved revision could mean non-compliance with the Directive.

Inventory and procurement traps: If parts managers or suppliers hold stock of P/N 35-380132-1 through -53, there is a risk that such parts will be used inadvertently as replacement spares or initial fits unless stocks are quarantined or re-identified. The Directive's blanket bar on installing those P/Ns as new spares on affected aeroplanes requires active inventory management to prevent mistakes.

Timing mismatch with FAA: The Directive delays the final compliance date relative to the FAA AD (CASA: 24 months from 25 September 2008 = 25 September 2010; FAA final compliance time noted as 6 August 2009). Operators working across jurisdictions or on internationally registered aircraft may face different deadlines. They should not assume that compliance with the FAA AD timing satisfies CASA's deadline without verifying cross-jurisdictional obligations.

No enforcement details in the text: The Directive contains no penalty language or enforcement processes in the supplied text. That absence may lead to uncertainty about how CASA will monitor compliance and what documentary evidence will be required. Operators should not rely on the absence of enforcement language as permissive; they should treat the Directive's requirements as mandatory operational obligations.

Records and traceability for parts: Given the prohibition on installing the older P/Ns and the allowance for prior accomplishment, it is important to preserve parts traceability records showing the P/Ns removed and installed, including serial numbers of replacement parts where applicable. Failure to do so can make later regulatory interaction or audits more difficult.

Identify affected aeroplanes and parts: Check the aircraft register and maintenance records to identify Beechcraft 77 aeroplanes with serial numbers WA-1 through WA-312. For each aircraft, inspect wiring and breaker panels and/or review maintenance logs to determine whether any circuit breaker toggle switch with P/N 35-380132-1 through 35-380132-53 is installed. The Directive's "Applicability" statement is the operative trigger: the AD applies where those P/Ns are present.

If previously accomplished, retain evidence: The Directive expressly allows credit for prior accomplishment: "Unless previously accomplished, replace all circuit breaker toggle switches ..." Operators who completed RAC SB 24-3735 (Issued August 2005) prior to this Directive must retain and be prepared to produce records that demonstrate the work complied with the RAC SB or an FAA-AMOC-approved revision. Practical compliance steps include documenting the SB reference, notation of replaced part numbers in the logbook, a maintenance release certifying conformity to the SB, invoices for parts installed showing improved P/Ns, and any ancillary test or bench records.

Carry out replacement per RAC SB or FAA-AMOC revision: For aircraft requiring action, carry out the replacement "as specified in Raytheon Aircraft Company (RAC) Recommended Service Bulletin SB 24-3735, Issued: August 2005." If relying on a later revision of the SB, ensure that revision is "approved by the United States Federal Aviation Administration (FAA) as an Alternate Method of Compliance (AMOC) to FAA AD 2008-13-17," because the Directive accepts only FAA-AMOC-approved later revisions as acceptable for compliance. Record the edition of the SB used and any AMOC reference.

Observe the compliance window: Requirement 1 must be completed "Within the next 24 months after the effective date of this Directive" (the Directive "becomes effective on 25 September 2008"), so replacements must be completed by 25 September 2010 unless previously accomplished. Plan work scheduling and parts procurement to meet that deadline. Where aircraft cross international jurisdictions or operate under foreign ADs with different deadlines, reconcile those obligations with this Directive’s timeline; do not assume equivalence without checking the specific AD texts.

Do not install older P/Ns as initial fit or spare: Requirement 2 is a continuing prohibition: "Circuit breaker toggle switches P/N 35-380132-1 through 35-380132-53 may not be installed on any aeroplane as an initial fit or as a replacement spare." Institute a parts-control measure to prevent inadvertent use of those P/Ns on affected Beech 77s. Quarantine or re-tag any inventory of the older P/Ns and update procurement specifications to source only the improved P/N range (35-380132-61 through -113) for the affected fleet.

Document each replacement comprehensively: Create or update a maintenance entry/logbook entry for each aeroplane recording the replacement, including date, aircraft serial number, removed P/Ns, installed P/Ns, RAC SB reference (including issue date), the name of the maintenance organisation or engineer performing the work, and any FAA AMOC cross-reference if a later SB revision was used. Even though the Directive does not prescribe a records format, the Directive’s allowance for prior accomplishment makes good traceability essential.

Coordinate with parts suppliers and maintenance providers: Provide suppliers and contracted maintenance organisations with a copy of the Directive and the RAC SB reference so they understand the prohibition on older P/Ns and the acceptable replacement P/Ns. Confirm availability of P/N 35-380132-61 through -113 and lead times for procurement. If a maintenance provider proposes an alternative technical method, ensure the proposed method is authorised by an FAA AMOC to FAA AD 2008-13-17 before relying on it as compliant.

Verify compliance and readiness before flight: The Compliance note for Requirement 2 specifies "Before further flight after the circuit breaker toggle switch has been replaced in accordance with Requirement 1." Practically, ensure that after replacement and before the aircraft's next flight, maintenance release, functional checks and any necessary inspections have been completed and recorded in the aircraft’s maintenance documentation.

Monitor for later SB revisions and AMOC approvals: If a later RAC SB revision becomes available, check whether the FAA has approved that revision as an AMOC to FAA AD 2008-13-17. If so, that revision is "considered acceptable" under this Directive. Maintain a process to monitor FAA AD and AMOC publications to capture any acceptable procedural updates.

Retain records for future oversight: Given the Directive’s allowance of prior accomplishment and the absence of specified enforcement mechanisms in the text, retain comprehensive records demonstrating compliance for the foreseeable period. Good records reduce the risk of administrative uncertainty if CASA queries an aircraft’s compliance status.

Plan for cross-jurisdictional operations: If an aeroplane operates under or into jurisdictions where the FAA AD timing differs, operators should ensure that they meet all applicable AD timelines. The CASA Directive’s timing differs from the FAA’s; reconcile multi-jurisdiction compliance in operational planning and maintenance scheduling.