AD/B737/293 - Master Dim and Test System Wiring

Master Dim and Test System. This is an electrical subsystem on the flight deck that controls the dimming of panels and provides a test function to verify that indicator lights and displays are functioning. The wiring concerned carries the test ground signal for redundant communications equipment. The directive addresses a lack of physical or electrical separation between those test‑ground wires, meaning a single fault (e.g., a chafed wire or a short) could inadvertently trigger the test mode on both primary and standby communications panels. The concept of redundant equipment is central: the test ground signal is meant to be isolated so that a fault on one channel does not cascade to the other. Without separation, a single fault could cause the communications panels to display test patterns rather than the assigned radio frequencies. That would prevent the flight crew from seeing, for example, which air‑traffic‑control frequency they had tuned, even though the radio may still be operating. The directive does not require replacement of units; it requires rerouting, shielding, or otherwise modifying the wiring harness to achieve separation.

Service Bulletins as Means of Compliance. The directive does not specify every wiring detail; instead it incorporates by reference the Accomplishment Instructions from Boeing Special Attention Service Bulletins. Two primary bulletins are used: SB 737‑33‑1132 for the Classic series (‑300/‑400/‑500) and SB 737‑33‑1133 for the Next Generation series (‑600/‑700/‑800/‑900). Table 2 of the directive identifies earlier revisions of those bulletins (original, Revision 1, Revision 2 for SB 1133; original and Revision 1 for SB 1132) as acceptable for compliance if the work was done before the directive’s effective date. This creates a safe harbour for operators who proactively acted on earlier Boeing recommendations. Later revisions of those service bulletins, when approved by the FAA as an Alternate Method of Compliance (AMOC) to the equivalent FAA AD, are also considered acceptable for the Australian directive. This cross‑acceptance mechanism avoids double‑approval but places reliance on FAA determinations.

Group Numbers and Prior/Concurrent Actions. The affected fleet is subdivided into groups (e.g., Group 57, Group 37, Group 46, Group 2, Group 39, Group 59) based on the original equipment configuration or previously incorporated modifications. Each group has additional mandatory tasks that must be performed before or at the same time as the master‑dim‑test wiring change. For example, Group 57 aeroplanes require an engine instrument system (EIS) installation from 1989. Those group numbers are defined in the service bulletins, so an operator must cross‑reference its aircraft’s serial number against the bulletin’s group list. Notably, some of the prior actions refer to service bulletins that are over a decade older than the directive (e.g., SB 737‑77‑1022 from 1989). This suggests that the master‑dim‑test modification may be incompatible with certain older configurations unless those earlier upgrades are already in place. The concept of concurrency ensures that the wiring change does not produce a partial solution: without the related system installations, the test‑mode isolation benefit may be negated or the new wiring may create additional integration problems.

Alternate Method of Compliance. The directive explicitly states that later revisions of the primary service bulletins, when approved by the FAA as an AMOC, are acceptable. This acknowledges that technology or materials may improve after publication and that operators can implement superior methods subject to FAA oversight. However, there is no express provision for CASA‑only AMOCs independent of FAA approval; the text ties the AMOC to the FAA AD. For Australian operators that hold only an Australian certificate of airworthiness, this may create a procedural gap if the FAA has not yet approved a revision that CASA would be willing to accept. The directive also notes that actions accomplished before the effective date in accordance with earlier service‑bulletin revisions (listed in Table 2) are acceptable. This provides a grace period for those who already acted.

The directive directly imposes duties on aircraft operators and registered owners of any Boeing 737 series aeroplane captured by the applicability clause: Model 737‑300, ‑400 and ‑500 series identified in Boeing Special Attention SB 737‑33‑1132, Revision 2, and Model 737‑600, ‑700, ‑700C, ‑800 and ‑900 series identified in Boeing SB 737‑33‑1133, Revision 3. In practice, this includes Australian airlines that operate these variants (for example, legacy 737‑300/‑400 freighters or the later 737‑800/‑900 fleets used by mainline and low‑cost carriers), charter operators, leasing companies that have placed aircraft on the Australian register, and private owners of corporate 737 airframes. Because the directive requires engineering modifications to the airframe wiring, the most immediate burden falls on maintenance, repair and overhaul (MRO) organisations and licensed aircraft maintenance engineers who must physically execute the task. Those organisations must have access to the service bulletins (which are proprietary Boeing documents, typically purchased) and must be authorised under their CASA‑approved maintenance organisation exposition to perform such major changes.

Indirectly, Boeing is affected as the manufacturer that generated the service bulletins. The directive essentially compels operators to purchase and follow Boeing’s engineering, reinforcing Boeing’s market position as the sole source of approved data for this modification. The prior‑action requirements reference other Boeing service bulletins (e.g., SB 737‑77‑1022, SB 737‑77‑1023, SB 737‑33‑1121, SB 737‑26A1083, SB 737‑23‑1102), so operators must also procure those documents if the tasks have not already been performed. Smaller operators with single‑aircraft fleets may be disproportionately affected: the fixed cost of obtaining multiple bulletins and scheduling specialised labour can exceed the per‑aircraft pro‑rata benefit for a one‑off job, especially if the aircraft is near the end of its economic life. Lessors may also be affected because modifications to an aircraft returned at lease end may need to be reversed or documented, adding transactional friction.

The regulator, CASA, is affected in its enforcement role. The directive was issued by a delegate (James Coyne) on 14 August 2006, becoming effective 28 September 2006. CASA must monitor compliance through its surveillance program, review maintenance records, and potentially take enforcement action against operators who miss the 48‑month deadline. The FAA is also involved because the directive incorporates the FAA AD by reference and allows AMOCs approved by the FAA. This creates a cross‑border regulatory dependency: an Australian operator seeking to use a later revision of a service bulletin may need to obtain FAA approval first, which introduces delay and cost. The directive does not say that CASA will independently approve alternative methods; it only accepts FAA‑approved ones. This reduces administrative duplication but leaves Australian operators exposed to FAA administrative procedures and backlogs.

Duty to Modify Wiring (Requirement 1). Every operator of an affected aeroplane must modify the wiring for the master dim test system strictly in accordance with the Accomplishment Instructions of the applicable service bulletin. This is not a “best efforts” obligation; the regulation mandates a specific engineering outcome. The operator is responsible for ensuring that the modification is performed by an appropriately authorised maintainer and that the work is properly documented.

Duty to Accomplish Prior or Concurrent Actions (Requirement 2). For aircraft falling within the group numbers listed in Table 1, the operator must complete all associated actions specified in that table before or at the same time as Requirement 1. These actions are not optional. If, for example, a Group 57 aeroplane has never had the EIS installation from 1989 performed, the operator must do that before or concurrently with the master‑dim‑test wiring change. This cascade of mandatory work may force the operator to execute multiple modifications simultaneously, increasing downtime and parts procurement risk. The directive does not offer relief for operators who consider the prior actions unrelated or excessive; they are deemed necessary for the wiring change to be effective.

Rights to Use Earlier or Later Service‑Bulletin Revisions. The directive provides two grandfathering mechanisms. First, actions accomplished before the effective date using the earlier revisions listed in Table 2 (Original or Revision 1 of SB 737‑33‑1133; Original or Revision 1 of SB 737‑33‑1132) are accepted as compliant. This gives operators who did proactive work a credit. Second, later revisions of those bulletins, when approved by the FAA as an AMOC, are also accepted for the Australian directive. This gives operators a path to use improved data without seeking separate CASA approval. However, the rights are qualified: the AMOC must be specific to FAA AD 2006‑15‑18. If a later revision has not been vetted by the FAA, or if the FAA has not granted AMOC status, the operator cannot unilaterally rely on it. The directive does not grant operators the right to design their own alternative means of compliance; it only recognises the FAA’s line of approval.

Record‑keeping and Reporting. While the directive does not explicitly state a separate duty to report compliance, standard Australian airworthiness regulation (under Civil Aviation Act 1988 and the Civil Aviation Safety Regulations 1998) requires that each AD be recorded in the aircraft’s continuing airworthiness records and that a statement of compliance be submitted to CASA upon completion. The operator should anticipate that the MRO will issue a release to service referencing this AD. Without that paper trail, the aircraft’s certificate of airworthiness could be affected.

Right to Schedule Within 48 Months. The compliance time for Requirement 1 is 48 months from the effective date (28 September 2006). This gives operators a window of just over four years to plan the work, source parts, and coordinate with maintenance cycles. This is a relatively generous timeline for a wiring modification, reflecting that the risk is not imminent but could materialise over the fleet’s lifetime. However, the operator does not have the right to delay beyond the deadline; the directive is not a recommendation. The prior‑concurrent‑actions requirement has no separate deadline; it must be done before or concurrently with Requirement 1, which effectively compels the operator to schedule the prior actions within the same 48‑month window.

The Airworthiness Directive is a legally enforceable regulatory instrument issued by CASA under powers delegated under the Civil Aviation Act 1988 (Cth) and the Civil Aviation Regulations 1988 (now largely subsumed by the Civil Aviation Safety Regulations 1998). Breach of an AD is a breach of a condition of the aircraft’s certificate of airworthiness. The specific penalty provisions are not recited in the directive itself, but standard Australian aviation law applies. Under reg 39.1 of the Civil Aviation Safety Regulations 1998 (or the transitional provisions if using the older CAR 1988), failure to comply with an AD can result in civil penalties of up to $13,750 per contravention for an individual and up to $27,500 for a body corporate, with additional daily penalties for continuing breaches. Criminal prosecution is also possible for reckless or intentional breach, carrying potential imprisonment for up to five years under the Criminal Code for offences involving aviation safety. CASA can also suspend or cancel the aircraft’s certificate of airworthiness, effectively grounding the aeroplane until compliance is demonstrated. Airworthiness directive compliance is a universal pre‑condition for any flight.

Enforcement is retrospective: CASA may audit maintenance records during routine surveillance or after an incident. The directive itself does not require the operator to report compliance to CASA proactively, but standard practice is to record the AD in the aircraft’s logbook and, for imported or newly‑registered aircraft, to provide evidence of compliance during the airworthiness review. CASA has wide powers of inspection under s 20A of the Civil Aviation Act, and can require production of documents. Non‑compliance with the 48‑month deadline would likely lead to an immediate grounding notice (a “show cause” or “no‑fly” direction). Operators may also face civil liability if a failure of the master‑dim‑test system causes an accident attributable to non‑compliance. Under Part IV of the Civil Aviation Act, the operator’s duty of care extends to third parties; a breach of an AD could be used as evidence of negligence in tort.

Because the directive is a domestic reflection of a US FAA AD, there may be additional consequences for Australian operators who fly internationally. If the aircraft visits US airspace, the US Federal Aviation Regulations (14 CFR 39) require compliance with FAA AD 2006‑15‑18. Non‑compliance could result in FAA enforcement including fines and detention of the aircraft. Even if the Australian AD is satisfied, it reinforces that the standards are essentially identical, so compliance with one is likely compliance with the other; but the converse is not guaranteed.

This directive is a specific instrument issued under the broader framework of Australian aviation safety regulation. It interacts with the Civil Aviation Act 1988 (Cth), the Civil Aviation Regulations 1988 (CAR 1988) (particularly Part 4A dealing with airworthiness), and the Civil Aviation Safety Regulations 1998 (CASR 1998) (Parts 21, 42, 43, and 145). Under the regulation hierarchy, an AD is a legally binding directive that overrides any operator’s internal procedures if they conflict. It does not, however, override exemptions or authorisations issued by CASA. If an operator has a CAR 39A or CASR 21.027 exemption that specifically addresses the master dim test system, that exemption would take precedence, but no such exemption is mentioned in the source.

The directive is explicitly based on FAA AD 2006‑15‑18 (Amdt 39‑14699). This is stated in the note at the bottom of the document. The use of FAA AD is common in Australian ADs because many Boeing 737s are type‑certificated in the US and the FAA is the primary design authority. The directive does not cross‑reference any European (EASA) or other national AD, but for Australian‑registered aircraft that are also operated under a foreign maintenance approval, the operator must satisfy the applicable regulation of the state of the operator, which may be different. The directive’s acceptance of FAA‑approved AMOCs implies a reciprocity that may not extend to approvals from other regulators.

The prior/concurrent actions table references Boeing service bulletins that themselves may have been subject to earlier Australian or foreign ADs. For example, SB 737‑26A1083 concerning the cargo‑compartment smoke detection system may have been mandated by a separate FAA or EASA AD. If that is the case, compliance with this AD’s requirement to install that system is not additional work, only confirmation that it exists. But if the aircraft had been exempted from that earlier requirement under an Australian operating rule, this AD would now independently mandate it for the sub‑group. This layered interaction can create unexpected retrospective obligations.

The directive also interacts with contractual law between lessor and lessee. Leases often require the lessee to maintain the aircraft in compliance with all applicable ADs. This AD, including its prior‑action components, would become a contractual obligation. The cost of compliance (engineering, parts, downtime) would likely fall on the lessee, but if the lessor had previously installed an alternative system, the group classification may change and the prior actions might be already satisfied. The directive does not offer any insight into who pays; that is left to private contract.

Finally, the directive interacts with workers’ compensation and occupational health and safety legislation. The wiring modification must be performed safely; any injury to a maintainer would be governed by state OHS laws. The directive itself does not impose OHS requirements beyond standard aviation maintenance practices.

The source text is the original issue of AD/B737/293, dated 14 August 2006, effective 28 September 2006. The directive number “10/2006” indicates it was the tenth AD issued for Boeing 737 series in 2006. The directive references service bulletins that themselves have revision histories. Boeing SB 737‑33‑1132 went through an original issue (20 March 2003), Revision 1 (4 March 2004), and Revision 2 (8 September 2005). Boeing SB 737‑33‑1133 went through original (19 December 2002), Revision 1 (17 April 2003), Revision 2 (4 December 2003), and Revision 3 (8 September 2005). The directive expressly accepts earlier revisions of these bulletins (up to the ones listed in Table 2) as acceptable for prior compliance. It also states that later revisions, when approved by the FAA as an AMOC to FAA AD 2006‑15‑18, are acceptable for the Australian directive. This provides a built‑in mechanism for evolution without requiring re‑issue of the AD itself. Therefore, the AD/B737/293 will not appear to have multiple Australian revisions; rather, the underlying service bulletins can be updated.

Because the source only contains this single issue, there is no evidence of any subsequent CASA amendment to AD/B737/293. However, it is likely that after 2006, the FAA may have revised its AD or allowed further service bulletin revisions. Australian operators would need to check whether later FAA‑approved AMOCs exist. If no CASA amendment was issued, the original directive remains in force as the sole binding requirement, though its practical content has been updated via the AMOC path. This is a common feature of Australian ADs that incorporate FAA ADs: the Australian version may become a “zombie” directive that stays on the books unchanged while the technical standard moves. Operators must stay informed about FAA actions to know whether a later service‑bulletin revision is acceptable. The source does not list any Australian amendment number or date of revision, so we must infer that the directive has not been formally revised by CASA; rather, it relies on the FAA’s dynamic system. This creates a compliance challenge: the regulatory text appears static, but the acceptable means of compliance can shift.

The source makes no mention of any legal challenge or court decision concerning AD/B737/293 or its underlying FAA AD. This is unsurprising. Airworthiness directives are administrative decisions made by a technical regulator and are rarely litigated directly. Operators may challenge CASA’s refusal to grant an extension or exemption under the Administrative Decisions (Judicial Review) Act 1977 (Cth) or seek merits review before the Administrative Appeals Tribunal, but no such cases are recorded in the source. The absence of litigation may suggest that the industry accepted the directive’s technical basis without formal dispute. The background note says the FAA received a report about the wiring issue; it does not identify any accident or incident that triggered the investigation. Without a crash or publicised safety event, litigation incentives are low. The 48‑month compliance window also gave operators ample time to digest costs without resorting to court.

If litigation were to occur, the likely grounds would be: (1) the directive is ultra vires the enabling regulations because it mandates prior actions that were not part of the original FAA AD; (2) the group‑specific Table 1 actions are arbitrary or not rationally connected to the master‑dim‑test risk; (3) the cost of the earlier EIS modifications (for Group 57) is grossly disproportionate to the safety benefit. However, courts typically defer to regulators on technical airworthiness matters unless there is Wednesbury unreasonableness or procedural unfairness. The directive follows the FAA AD closely, which would be strong evidence that CASA acted on credible foreign regulatory analysis. The directive also included a consultation note? None is stated, but Australian ADs generally go through a drafting and comment process with industry. No legal challenge is known, so the directive has stood unchallenged. For historical completeness, it is worth noting that ADs from the 2006 period rarely attracted litigation; the aviation industry tends to comply rather than fight, partly because grounding is a more immediate threat than a fine. The directive’s impact on liability in tort (negligence per se) could arise in a civil suit after an incident, but that is not “litigation history” of the directive itself.

Group Classification Can Change Compliance Scope. The directive’s applicability references the service bulletins for specific groups. The group numbers are not self‑evident from the AD text; the operator must obtain the bulletin and identify which group its aircraft’s serial number falls into. A seemingly small error in grouping can lead to mandatory prior actions that were not budgeted for (e.g., a Group 57 Classic may require an EIS installation from 1989 that the operator never performed, adding tens of thousands of dollars in parts and labour). Operators should not assume that all aircraft of the same model are treated identically.

Concurrent Actions Must Happen Before or With the Wiring Change. The phrasing “prior to or concurrently with” means the prior actions cannot be postponed beyond the wiring modification. If the operator schedules the wiring change for month 47, but the prior actions require a part with a 50‑week lead time, the operator may breach the compliance deadline. The prior actions themselves may not have an explicit 48‑month tail, but because they must accompany Requirement 1, the entire package of work must be completed within the 48‑month window. This can catch operators who think they can do master‑dim‑test on its own first and the prior actions later.

AMOC Relies on FAA Approval, Not CASA. The directive does not allow an operator to obtain an AMOC directly from CASA for a later service bulletin revision. It only accepts FAA‑approved AMOCs. Australian operators are therefore dependent on the FAA’s processing time and any administrative bottlenecks. If the FAA is slow to approve a revision that an Australian operator wishes to use, the operator must either use the original bulletin (with its higher cost or obsolete parts) or wait, possibly missing the 48‑month deadline. There is no fallback for unilateral Australian acceptance.

Cost of Obsolete Service Bulletins. The prior‑action references date back to 1989 and 1999. Those bulletins may be out of print, require a fee from Boeing, or contain parts that are no longer manufactured. The operator may need to engage Boeing directly or a third‑party engineering house to determine an equivalent means. The directive provides no relief if the service bulletin is unavailable.

48 Months from Effective Date, Not Publication Date. The effective date is explicitly 28 September 2006. The directive was signed on 14 August 2006, giving operators only about six weeks’ notice before the clock started. Any operator that missed this detail and assumed the clock started from the date of service (e.g., when the AD was published in the CASA AD register) would have inadvertently lost time.

Record‑keeping for Prior Actions. If a prior action (e.g., installing an EIS in 1989) was performed before the directive’s effective date, it is acceptable only if it was done according to the service bulletin listed. But if the operator’s records show a different part or a different modification, CASA may not credit it as compliant. The operator would then have to re‑do or verify the work, incurring cost. The directive does not require proof that the prior action was originally performed under a mandatory directive; any installation per the SB counts, but the burden of proof is on the operator.

Interaction with Leases. If the aircraft is leased, the lessee may be contractually required to pay for AD compliance, but the prior actions could unlock a chain of obligations (e.g., if the EIS installation was never done, the lessor may claim it is a capital improvement, leading to a cost allocation dispute). The directive itself is silent on these commercial implications.

The “Test Patterns” Risk. The background explains that a test pattern could replace radio frequencies on communications panels. However, the directive does not require any temporary operating limitation pending compliance. The fault is latent: the aircraft can fly for up to 48 months without the modification. This implies that the regulator assessed the risk as acceptable in the interim, but if an incident occurred before the deadline, the operator could face questions about whether it should have implemented an earlier fix. The directive’s 48‑month timeline is not a safe harbour for negligence.

Step 1: Determine Applicability. Obtain the complete list of airframes on the Australian register by manufacturer serial number that fall within the scope of Boeing Special Attention SB 737‑33‑1132, Revision 2 (for Classic models) and SB 737‑33‑1133, Revision 3 (for Next Generation models). This requires access to the service bulletins, which must be procured from Boeing or an authorised distributor. Cross‑reference the serial numbers against the group definitions in the bulletins. Document which group number each aircraft belongs to (e.g., Group 57, Group 2, Group 39, Group 59, etc.).

Step 2: Assess Prior/Concurrent Actions. For each aircraft, examine Table 1 of the directive and the applicable service bulletin group. Determine whether the referenced prior actions have already been accomplished. For Group 57 aircraft, check if Boeing SB 737‑77‑1022 (EIS installation) and SB 737‑77‑1023 (EIS advisory system modification) are recorded in the aircraft’s maintenance history. For Group 37/46, check SB 737‑33‑1121 (audio control panel lamp test wiring). For Group 2, check SB 737‑26A1083 (splice SP896). For Group 39, check SB 737‑26A1083 (cargo compartment smoke detection). For Group 59, check SB 737‑23‑1102 (VHF/HF panel replacement). If any of these have not been done, they must be planned and completed before or concurrently with the main wiring modification. If they were done before the directive’s effective date using the exact service bulletin revision listed (or earlier revisions per Table 2), they are accepted. Verify that the documentation matches the revision numbers.

Step 3: Plan the Modification. Obtain the Accomplishment Instructions from the applicable service bulletin. This typically involves a wiring‑reroute, possibly with new terminals, splices, and support brackets. Identify the required parts and specialised tooling. Order any Boeing‑supplied kits early; lead times can be long. Schedule the work to occur within the 48‑month window from 28 September 2006. Coordinate with the prior actions to ensure both can be completed in the same maintenance visit.

Step 4: Execute the Work. Utilise a CASA‑approved MRO (for Australian operators) with personnel holding appropriate aircraft‑maintenance engineer licences for Boeing 737 airframe and electrical systems. Perform the modification strictly per the service bulletin step‑by‑step. After completion, perform any required functional test to verify that the master dim test system no longer allows test patterns to appear on communications panels. For the prior actions, accomplish the tasks per their respective bulletins. Ensure all modifications are entered in the aircraft’s logbook and maintenance records, referencing AD/B737/293 and the specific service bulletin numbers and revisions used.

Step 5: If Using a Later Revision. Determine if a later revision of SB 737‑33‑1132 or SB 737‑33‑1133 has been issued and approved by the FAA as an AMOC to FAA AD 2006‑15‑18. Obtain a copy of the FAA approval letter or the revised bulletin. This approval may be listed in FAA’s AD docket. If the later revision is not yet FAA‑approved, the operator must use the Revision 2 or Revision 3 specified in the directive, or wait for FAA action. Document that the AMOC is accepted per the directive’s clause.

Step 6: Record and Report. After completion, update the aircraft’s continuing airworthiness record. Under regulation 42.237 (CASR), the operator must ensure that an Airworthiness Directive Compliance Record is created and kept. Standard practice is to sign off the AD in the aircraft’s logbook with the date, hours, and maintenance release. No specific reporting to CASA is mandated in this AD, but operators should retain records for at least the life of the aircraft. If CASA requests evidence during an audit, the operator must produce the service bulletins, work orders, parts certificates, and sign‑offs.

Step 7: Ongoing Monitoring. Periodically check whether FAA‑approved AMOCs have been issued that could allow use of newer service bulletins, potentially reducing maintenance burden in future if parts are superseded. Monitor any revision to the FAA AD itself. If the FAA AD is superseded or terminated, that may affect this directive’s continued applicability. However, the source directive remains in force until CASA withdraws it. Operators should check the current CASA AD database for any superseding AD on the same subject.