AD/A320/209 - Cargo Compartment Fire Extinguisher Wiring

The directive rests on a few tightly defined technical and procedural concepts drawn from the text.

• Applicability scope. The AD targets Airbus A318, A319, A320 and A321 aeroplanes delivered before 28 February 2007 that have a cargo compartment fire extinguisher bottle installed either during production or retrofitted in service in accordance with an Airbus Service Bulletin. Aircraft on which specified MRBR tasks (26.23.00/03 or 26.23.00/07) have been performed are excluded from the requirement (see "Applicability").

• One-time inspection and continuity check. The mandatory action is a single inspection and continuity check of the cargo firing circuit continuity. The AD specifies that the inspection must be carried out "in accordance with Airbus SB A320-26A1068 dated 19 March 2007 or later revision approved by the European Aviation Safety Agency (EASA)" (see "Requirement 1"). The term "continuity check" in the AD refers to confirming electrical continuity of the firing circuits and that the dedicated wiring correctly connects the discharge pushbutton switches to the respective cargo bottles, as explained in the Background.

• Rectification duty. If the inspection identifies any discrepancies, those discrepancies must be rectified. The AD requires rectification of any discrepancies "found during the Requirement 1 inspection and check" and prescribes that rectification be completed "before the next flight after the Requirement 1 inspection and check" (see "Requirement 2" and "Compliance").

• Alternative method of compliance. The AD recognises that the accomplishment of MRBR task 26.23.00/03 or 26.23.00/07 serves as an acceptable alternative means of compliance with the AD. That creates a compliance pathway that avoids performing the one-time SB-based inspection where the MRBR tasks have already been done (see "Requirement" text).

• Link to EASA materials. The AD cross-references EASA AD 2007-0249 and limits acceptable SB revisions to those approved by EASA. The AD therefore conditions acceptable procedural documents on EASA approval rather than leaving revision choice to operators (see "Requirement" and "Note").

• Timing metric. Compliance is specified by aircraft hours time in service: inspection within 600 hours time in service after the AD effective date, rectification before the next flight following inspection (see "Compliance").

These concepts define the mechanical change the AD imposes: a targeted, one-off electrical verification and mandatory remedy of wiring errors that could cause incorrect discharge of cargo extinguisher bottles, executed under the technical instructions of a specific Airbus Service Bulletin or via an MRBR task.

The instrument identifies a narrow population of affected actors and leaves others outside its scope by explicit exclusion.

• Operators and owners of Airbus A318, A319, A320 and A321 aeroplanes delivered prior to 28 February 2007 are potentially affected, but only if their aeroplane is "fitted with a cargo compartment fire extinguisher bottle installed during production, or whilst in service, in accordance with an Airbus Service Bulletin (SB)" (see "Applicability"). The delivery date threshold in the Applicability clause distinguishes aircraft delivered before that date from later deliveries.

• Maintenance organisations, licensed maintenance engineers and technical staff who carry out inspections and continuity checks in accordance with Airbus Service Bulletin A320-26A1068 are operationally affected because the AD prescribes the means and method of the inspection (see "Requirement 1").

• Operators or maintainers that have already accomplished MRBR task 26.23.00/03 or 26.23.00/07 are excluded from having to perform the SB-based inspection, because the AD lists those MRBR tasks as "an acceptable alternative method of compliance with the requirements of this Directive" (see "Requirement" text and "Applicability" exception).

• The Civil Aviation Safety Authority (CASA) is the issuing agency, represented by the Delegate who signed the AD. The AD becomes effective on a specified date and therefore will be part of CASA’s airworthiness directives that operators must follow in the Australian regulatory environment (see signature and effective date). The AD also incorporates by reference materials approved by the European Aviation Safety Agency; this affects operators who must use EASA-approved revisions of the Service Bulletin.

• Aircraft that do not meet the delivery-date threshold, that were not fitted with the extinguisher bottle per the referenced Airbus SB, or that have had the specified MRBR tasks completed are not required by this directive to perform the inspection. That exclusion is explicit and must be established by reference to the aircraft’s delivery records, modification records and MRBR task history.

Who pays and who schedules. The source does not specify funding or cost-recovery mechanisms. The operational burden therefore falls on the affected operators or their contracted maintenance providers to schedule and perform the inspection and any required rectification within the time limits specified in the AD. The AD does not allocate costs, financing or compensation.

The AD sets out a limited set of duties and identifies a single explicitly stated alternative route for compliance. It does not specify broader rights or procedural appeal mechanisms within its text.

Duties established by the AD text

• Identify applicability. Operators must determine whether each aeroplane is within the scope defined by the "Applicability" clause: delivered before 28 February 2007, fitted with a cargo compartment fire extinguisher bottle installed during production or in service according to an Airbus Service Bulletin, and not already subject to MRBR task 26.23.00/03 or 26.23.00/07 (see "Applicability").
• Perform inspection. For applicable aeroplanes, the operator must "Perform an inspection and continuity check of the cargo firing circuit continuity, in accordance with Airbus SB A320-26A1068 dated 19 March 2007 or later revision approved by the European Aviation Safety Agency (EASA)" (see "Requirement 1").
• Rectify discrepancies. If any discrepancies are found during that inspection, operators must "Rectify any discrepancies found during the Requirement 1 inspection and check" (see "Requirement 2").
• Meet timing requirements. The inspection must be performed "Within the next 600 hours time in service after the effective date of this Directive" and any rectification must be completed "Before the next flight after the Requirement 1 inspection and check" (see "Compliance").

Alternative method of compliance

• MRBR tasks as acceptable alternative. The AD explicitly states that "Accomplishment of MRBR task 26.23.00/03 or 26.23.00/07 is an acceptable alternative method of compliance with the requirements of this Directive." That is the only alternative compliance route identified in the Directive text (see "Requirement").

Implied operational responsibilities

• Use of EASA-approved Service Bulletin revisions. The AD confines the acceptable Service Bulletin to the one dated 19 March 2007 or later revisions approved by EASA, therefore requiring operators to ensure the technical data they use is an EASA-approved revision (see "Requirement 1").

Rights and procedural protections

• The AD text does not assert any explicit rights of appeal, request for extension, or cost recovery. It also does not set out a process for approval of alternative methods of compliance other than the stated MRBR tasks being an acceptable alternative. The AD does not provide procedural details for demonstrating compliance beyond the prescription of the inspection method and timing.

Operational consequence of duties

• Because rectification must be completed before the next flight after inspection, the AD creates a potential immediate grounding risk for any aeroplane where discrepancies are found; the AD requires correction prior to further flight (see "Compliance"). The AD does not itself provide exceptions or stay provisions.

In sum, the AD places a narrowly framed, time-bound operational duty on operators to verify and, where necessary, repair cargo extinguisher circuit wiring, subject to a specified technical method and a single listed alternative compliance route.

The AD text does not include express statutory penalty provisions or a detailed enforcement mechanism within its own content. The document records that it is an Airworthiness Directive issued by the Civil Aviation Safety Authority (CASA), signed by the Delegate, and states the AD "becomes effective on 22 November 2007" (see signature block and "Compliance"). Beyond that, the AD sets mandatory actions and compliance deadlines but does not, within the text provided, prescribe fines, suspension powers, or criminal sanctions.

What the AD does specify that is relevant to enforcement

• Mandatory actions and deadlines. The AD prescribes mandatory actions (inspection and rectification) and fixed compliance windows (inspection within 600 hours time in service after the effective date; rectification before next flight after inspection). These prescribed actions and timelines create objective compliance requirements that would be enforceable under the broader regulatory framework to which CASA ADs normally belong, even though the AD text itself does not specify enforcement mechanisms (see "Requirement" and "Compliance").

• Delegation and signature. The AD is signed by "David Punshon, Delegate of the Civil Aviation Safety Authority", which identifies the issuing authority and an authorised delegate (see signature block). That appearance identifies the AD as coming from CASA, the regulator that in practice is responsible for monitoring and enforcing compliance with ADs. The AD does not set out enforcement procedures or penalties; those would typically be found in the governing aviation safety statutes and regulatory instruments beyond the AD text but those instruments are not included in this source and are not stated here.

Absence of penalties in the text

• No penalties. The AD contains no clause describing monetary penalties, administrative sanctions, or criminal liability for non-compliance. It does not set out processes for CASA inspections, notices to fix, grounding orders, or aviation safety enforcement remedies.

Practical implication for operators and maintainers

• The AD creates mandatory technical obligations with firm timing that, if not complied with, could expose operators to enforcement action under the broader regulatory system administered by CASA. The AD itself does not detail how CASA will detect non-compliance, nor does it set out the specific sanctions that may follow non-compliance, since those matters are not provided in the AD text.

Users needing to know enforcement detail must consult the broader regulatory instruments and enforcement provisions of the Civil Aviation Safety Authority, which are not reproduced in this AD text. The AD functions as the technical directive and compliance schedule; it does not set out penalties or enforcement steps within the document provided.

The AD explicitly references and integrates certain external technical and regulatory documents; it does not itself reproduce broader legal rules but prescribes compliance methods that reference internationally developed materials.

Referenced external instruments and interplay

• Airbus Service Bulletin A320-26A1068. The AD requires the inspection and continuity check "in accordance with Airbus SB A320-26A1068 dated 19 March 2007 or later revision approved by the European Aviation Safety Agency (EASA)" (see "Requirement 1"). That ties the AD’s technical prescription to a manufacturer-issued Service Bulletin and further conditions acceptable revisions on EASA approval. The AD therefore imports, by reference, the technical content and revision control regime governed by Airbus and EASA. Operators must ensure they use the EASA-approved revision of the SB where relevant.

• EASA AD 2007-0249. The AD contains a "Note: EASA AD 2007-0249 refers." That indicates that CASA’s AD is related to or informed by an EASA airworthiness directive, and that operators may need to consult or otherwise be aware of the EASA AD’s content. The AD does not reproduce the EASA AD but acknowledges its existence and relevance.

• MRBR tasks as alternative compliance. The AD recognises that completing MRBR task 26.23.00/03 or 26.23.00/07 provides an acceptable alternative method of compliance. MRBR tasks are entries in the operator/aircraft maintenance programme; by recognising MRBR work as an alternative, the AD integrates with existing maintenance programme tasking rather than imposing an additional compulsory SB action for aircraft where the MRBR item has already been accomplished.

Implication for regulatory hierarchy and approval

• The AD requires use of an SB "or later revision approved by EASA". That places a requirement that the technical data used for the inspection and check be approved by a recognised certification authority (EASA), integrating CASA’s AD with international certification practice and EASA revision control. The AD does not specify CASA approval of SB revisions. It therefore creates a link where the acceptable technical reference is defined by EASA approvals.

Absent cross-references

• The text of the AD does not incorporate other Australian statutes, regulations or enforcement provisions by reference; nor does it refer to Civil Aviation Regulations, maintenance record-keeping rules, or administrative appeal processes. The AD’s compliance mechanics and timelines stand alone in the document and rely on referenced technical documents for the procedural method.

Net effect on operators

• Operators will need to reconcile their maintenance records and practices with the AD’s explicit references: establish whether the aircraft are within scope (delivery date, SB installation), whether the MRBR tasks have been done, and which EASA-approved SB revision applies. The AD, by importing EASA approval and the MRBR alternative, requires operators to align their domestic maintenance compliance with these external technical documents and earlier MRBR work, rather than leave the method solely to local discretion.

The AD text supplied contains only the original issuance information and does not show subsequent amendments, revisions or cancellations. The document records the following historical items:

• Issue date and signatory. The AD is signed by "David Punshon, Delegate of the Civil Aviation Safety Authority" and is dated "2 October 2007" in the signature block (see signature block).

• Effective date. The AD text states that it "becomes effective on 22 November 2007." The "Compliance" clause also frames the timing for the required inspection as "Within the next 600 hours time in service after the effective date of this Directive" (see "Compliance").

• Reference to EASA AD and Service Bulletin dates. The AD prescribes Airbus SB A320-26A1068 dated 19 March 2007 as the baseline technical document for the inspection and allows later revisions only if approved by EASA. The AD also notes that "EASA AD 2007-0249 refers." These references situate the AD in a specific regulatory and technical moment in 2007.

• No listed amendments. The AD text as provided does not include any marked subsequent amendments, re-issuances, corrigenda, superseding ADs, or cancellation notices. There is no text indicating revisions or a history table of updates.

• No transitional provisions beyond compliance deadlines. The only temporal mechanics are the effective date and the 600 hours time in service compliance window. There are no listed extension mechanisms, re-issue dates, or later modifications in the supplied text.

If users require the complete amendment history or any later superseding AD, they will need to consult CASA records, EASA AD listings or Airbus communications outside the text provided here. The AD as supplied records a single issuance and an effective date, and references to the EASA AD and Service Bulletin for method and timing but does not itself document later changes.

The AD text contains no mention of any litigation, appeals, legal challenges, injunctions, or judicial review proceedings related to the directive. The document is a technical directive and includes technical and compliance instructions but does not document any history of disputes or court proceedings.

What the AD does state relevant to legal process

• Issuance by CASA delegate. The AD is issued by a named Delegate of the Civil Aviation Safety Authority, which identifies the administrative origin of the directive. The AD does not, however, record any legal contestation of its issuance or implementation.

• Reference to EASA AD. The AD notes that "EASA AD 2007-0249 refers." While this cross-reference indicates an upstream or parallel regulatory action by EASA, the AD contains no account of litigation stemming from the EASA action.

Absence of litigation detail

• No cases named. The AD does not name any judicial decisions, administrative appeals, tribunal outcomes, or statutory challenges. There are no references to precedent or to contested enforcement actions.

Practical consequence

• Because the AD does not present any litigation history, practitioners looking for litigation outcomes related to these measures will not find them within this text. Any litigation history would need to be located in external legal databases, CASA enforcement records or court files, none of which are reproduced here.

The AD is short and precise but contains several practical traps and potential sources of operator confusion that are explicit in the text.

1. Narrow applicability criteria , delivery date and installation traceability. The AD applies only to aircraft "delivered before 28 February 2007" that are "fitted with a cargo compartment fire extinguisher bottle installed during production, or whilst in service, in accordance with an Airbus Service Bulletin (SB)" (see "Applicability"). Operators must be able to demonstrate both the delivery date and that the extinguisher bottle installation was performed in accordance with an Airbus SB. If maintenance records do not clearly show whether the bottle installation followed the SB, operators cannot assume exclusion. The AD does not provide guidance on resolving ambiguous records.

2. MRBR task exclusion requires proof of completion. The AD excepts aircraft "on which Maintenance Review Board Report (MRBR) task 26.23.00/03 or 26.23.00/07 has been performed" (see "Applicability" and "Requirement"). Operators whose MRBR documentation does not clearly show those specific task references cannot rely on the exclusion. The AD does not set out what constitutes satisfactory evidence that the MRBR task has been completed.

3. Timing measured in hours time in service, not calendar days. The inspection must occur "Within the next 600 hours time in service after the effective date of this Directive" (see "Compliance"). That technical metric requires operators to convert the effective date to the fleet utilisation profile to determine the deadline. Operators with high utilisation could have less calendar time to comply than those with low utilisation. The AD does not provide an alternative calendar deadline.

4. Rectification before next flight can require immediate AOG actions. The AD requires rectification "Before the next flight after the Requirement 1 inspection and check" (see "Compliance"). If an inspection reveals a discrepancy, the aircraft cannot operate further until rectified. That could create immediate aircraft on ground exposure and associated commercial disruption if parts, test equipment or qualified personnel are not immediately available. The AD supplies no grace period or interim operational measure.

5. Mandatory use of a specific SB revision or later EASA-approved revision. The AD prescribes Airbus SB A320-26A1068 dated 19 March 2007 or later revision approved by EASA (see "Requirement 1"). Operators must ensure they use an EASA-approved revision. Using an unapproved revision or a different technical procedure risks non-compliance with the AD. The AD does not specify how to obtain confirmation of EASA approval status in the text.

6. Only a single alternative method is listed. The AD explicitly allows accomplishment of MRBR task 26.23.00/03 or 26.23.00/07 as an acceptable alternative method of compliance (see "Requirement"). It does not identify any other alternative compliance pathways, nor does it set out a process for CASA approval of alternative methods besides the MRBR tasks. Operators wishing to pursue a different method would need to look beyond the AD text for CASA procedures on alternative method approvals.

7. No penalties or enforcement details within the AD. The AD imposes mandatory action and timing but does not list enforcement mechanisms or penalties in the text (see "Penalties and enforcement"). Operators should not construe that absence as implying non-enforceability; it merely means the AD does not itself state enforcement procedures.

8. Cross-reference to an EASA AD. The AD states "Note: EASA AD 2007-0249 refers." Operators must determine what, if any, additional obligations arise from the EASA AD. The supplied AD does not reproduce EASA AD 2007-0249, so reliance on the CASA AD alone may overlook relevant technical or compliance details included in the EASA AD.

9. Single-event inspection. The AD is a one-time check. If an operator misses the 600-hour window, the AD text does not state an extension or an alternative compliance mechanism within the document. The AD requires the inspection within the specified window; failure to perform within that window is not addressed in the text itself.

10. Lack of administrative procedural detail. The AD does not explain how to notify CASA of compliance, what records must be produced, or how CASA will verify compliance. Those administrative procedures are not in the AD text and must be sought elsewhere.

Each of these "gotchas" flows directly from specific language in the AD. Operators should treat the AD as a technical requirement with tight applicability, precise timing, and a limited set of acceptable technical compliance methods.

The AD prescribes a compact set of compliance steps and timing. The following is an operational sequencing strictly drawn from the AD text.

1. Establish applicability for each aeroplane

   • Confirm the aeroplane is an Airbus A318, A319, A320 or A321 model and that it was delivered before 28 February 2007 (see "Applicability").
   • Confirm whether the aeroplane is "fitted with a cargo compartment fire extinguisher bottle installed during production, or whilst in service, in accordance with an Airbus Service Bulletin (SB)." If the extinguisher bottle was installed but records do not show the SB reference, treat the aircraft as potentially within scope until records are clarified (see "Applicability").

2. Check for MRBR task completion

   • Determine whether MRBR task 26.23.00/03 or 26.23.00/07 has been performed on the aeroplane. If either MRBR task has been accomplished, the AD states that accomplishment "is an acceptable alternative method of compliance with the requirements of this Directive" and the SB-based one-time inspection is not required for that aeroplane (see "Requirement" and "Applicability").

3. Schedule and perform the required inspection

   • For aeroplanes that are within scope and have not had the MRBR tasks performed, schedule a one-time "inspection and continuity check of the cargo firing circuit continuity" in accordance with Airbus Service Bulletin A320-26A1068 dated 19 March 2007 or a later revision that has been approved by EASA (see "Requirement 1"). The AD makes EASA-approved SB revisions the acceptable technical baseline.
   • Ensure the inspection is completed "Within the next 600 hours time in service after the effective date of this Directive." The AD’s effective date is 22 November 2007 and the 600 hours time-in-service metric is the stated compliance clock (see "Compliance").

4. React to inspection findings

   • If the Requirement 1 inspection and continuity check reveals any discrepancies, the AD requires operators to "Rectify any discrepancies found during the Requirement 1 inspection and check" (see "Requirement 2").
   • The AD is explicit that rectification must be completed "Before the next flight after the Requirement 1 inspection and check" (see "Compliance"). Therefore, operators must be prepared to ground the aircraft until rectification is carried out if discrepancies are found.

5. Use the correct technical data version

   • The inspection must follow Airbus SB A320-26A1068 dated 19 March 2007 or a later revision approved by EASA. Confirm the revision you plan to use is EASA-approved, as the AD makes EASA approval the condition for later revisions (see "Requirement 1").

6. Consider MRBR completion as an alternative

   • For aeroplanes that have not yet had the MRBR tasks performed, operators may consider accomplishing MRBR task 26.23.00/03 or 26.23.00/07 as an alternative method of compliance, if that operational approach is available and consistent with their maintenance programme. The AD explicitly recognises MRBR task accomplishment as an acceptable alternative (see "Requirement").

7. Coordinate maintenance resources and parts availability

   • Because the AD requires rectification before the next flight, operators should plan for access to qualified maintenance personnel, test equipment for continuity checks, and spare parts or wiring repair capability to avoid extended ground time if discrepancies are found. The AD does not provide an interim flight allowance.

8. Cross-check related EASA AD

   • The AD notes that "EASA AD 2007-0249 refers." Operators should read and consider the EASA AD to ensure no additional technical steps or contextual requirements apply, since the CASA AD references that EASA action (see "Note").

9. Record-keeping and proof of compliance

   • The AD does not specify administrative procedures for submission of compliance records or notification to CASA within the text provided. Nevertheless, operators should be prepared to demonstrate that the inspection and any rectification were accomplished in accordance with the AD and the Airbus SB specified because the AD establishes mandatory technical obligations and timing.

10. Follow-up

• The AD is a one-time directive. After performing the inspection and any rectification, no further AD-mandated recurring action is specified in the text. If MRBR tasks are later performed, the AD identifies those MRBR tasks as an alternative compliance means, but does not require additional action beyond the one-time check unless other directives or EASA materials impose further obligations.

These steps reflect the AD’s text: identify the affected aircraft, confirm MRBR completion status, perform the SB-specified continuity inspection within 600 hours time in service of the AD effective date, and rectify any discrepancies before the next flight. The operator’s practical scheduling and risk management choices are driven by the AD’s timing metrics and the pre-flight rectification requirement.