AD/A320/211 - Stand-By Instruments - Emergency Lighting

This AD is built around a small set of concrete technical and administrative concepts that determine when it applies and what it requires.

• Applicability based on equipment and modification history. The AD applies to A318-A321 series aeroplanes that have classical standby instruments installed by specific Airbus production modifications or service bulletin actions (Airbus modification 20011, 21999 or SB A320-34-1280). The AD expressly excludes aeroplanes equipped with an Integrated Standby Instrument System (ISIS) installed by Airbus modification 27620 or by specified SBs, and excludes aeroplanes that have already received Airbus modification 37329 or 37330 or been modified by SB A320-33-1057 (Applicability). That structure makes applicability a function of the aeroplane configuration and maintenance history rather than the serial number alone.

• Electrical supply logic and the battery hot bus. The operative technical measure is to modify "the electrical supply logic of the under glare shield flood lighting" by adding a back-up supply from the battery hot bus (Requirement; Directive text). The AD targets the under-glare-shield flood lighting specifically; it does not, in its text, mandate changes to other lighting or to the standby instruments themselves.

• Interaction of AC and essential buses in failure scenarios. The Background section identifies the failure chain that motivated the AD: reported losses of AC BUS 1 leading to loss of AC ESS BUS and DC ESS BUS, loss of five upper Display Units and loss of integral lighting; when DOME lights were selected OFF, crews had difficulty reading the standby instruments (Background). The AD therefore addresses lighting survivability on the battery hot bus when certain AC and essential DC buses are lost.

• Compliance method by reference to a manufacturer SB and EASA approval. The AD requires the modification be done "in accordance with the instructions in SB A320-33-1057 or later EASA approved revision" (Requirement). That linkage makes the SB the operative normative technical source, and it introduces a dependency on EASA approval for later revisions.

• Timing. The AD contains two timing points: the AD's effective date, 13 March 2008, and the compliance deadline, no later than 27 May 2011 (Compliance). The AD also bears a CA S A delegate signature dated 23 January 2008.

• Reference to EASA AD. The AD contains a parenthetical note that EASA AD 2007-0286 is referred to, but does not reproduce that AD (Note).

These concepts determine the administrative edge of the AD: it is equipment- and configuration-triggered, it prescribes a method of compliance by reference to a manufacturer SB and to EASA approval, and it targets a particular failure mode (loss of specific buses causing display and lighting failures) by strengthening the lighting power feed via the battery hot bus.

The AD's primary addressees are the operators and owners of the listed Airbus aeroplane types whose aeroplanes meet the applicability criteria. The AD applies to A318, A319, A320 and A321 series aeroplanes "fitted with classical standby instruments installed by Airbus modification 20011 or 21999 during production or by Airbus Service Bulletin (SB) A320-34-1280 whilst in service" unless they fall into the stated exceptions (Applicability). That language places the onus on operators and maintenance organisations to determine each aeroplane's configuration history and whether the AD applies.

The AD excludes aircraft that already have alternate systems or prior modifications that address the issue. Specifically, aircraft fitted with ISIS installed by Airbus modification 27620 or by SB A320-34-1261 or SB A320-34-1372 are excluded, and aircraft that have received Airbus modification 37329 or 37330 during production or by SB A320-33-1057 whilst in service are also excluded (Applicability). Those exclusions reduce the pool of affected aircraft to those with classical standby instruments and without those other alterations.

Who decides. The AD is issued under the authority of the Civil Aviation Safety Authority as evidenced by the signature block, where Charles Lenarcic, "Delegate of the Civil Aviation Safety Authority", signs and dates the Directive (23 January 2008). That identifies CASA, through its delegate, as the issuing decision-maker for this instrument.

Who pays and who acts. The instrument itself does not include an express statement allocating costs, but the Requirement makes the modification mandatory "unless already accomplished" and prescribes the method of accomplishment (Requirement). Practically, this places the operational and financial responsibility for accomplishing the mandated modification on the operator or the entity responsible for maintenance of the aeroplane, because they must arrange for the SB-directed modification. The AD does not identify any direct financial support, subsidy or cost-sharing mechanism.

Flight crew and operational effect. The Background describes flight crew concerns about reading the standby instruments when the DOME lights are selected OFF during the failure condition (Background). That links the AD to the flight crew's ability to use standby instruments under certain failure and lighting states; the AD thereby implicates both flight operations safety and maintenance activity.

Regulatory interface. The AD references an EASA AD (EASA AD 2007-0286) and requires the SB or later EASA-approved revision as the method of compliance (Requirement; Note). Those cross-references mean that affected operators must coordinate corporate technical records, Airbus SB availability, and EASA approvals when planning work.

Maintenance organisations and line maintenance. Because the work is a change to electrical supply logic and requires SB instructions, maintenance organisations authorised to carry out Airbus SBs will be the entities undertaking the modification. The AD does not itself name approved maintenance organisations, but it prescribes compliance with Airbus SB A320-33-1057 or later EASA-approved revisions as the means to satisfy the AD.

The AD creates a specific duty to modify certain aeroplanes' electrical supply logic for the under-glare-shield flood lighting and prescribes the method and deadline for doing so.

Primary duty. The operative duty is expressed in the Requirement: "Unless already accomplished, modify the electrical supply logic of the under glare shield flood lighting in accordance with the instructions in SB A320-33-1057 or later EASA approved revision." That is a compulsory duty for aeroplanes within the applicability scope unless the modification has already been accomplished (Requirement). The wording "Unless already accomplished" creates a negative condition for the duty; if the work has already been performed in a manner consistent with the SB or equivalent, the duty is not triggered.

Method obligation. The AD confines the method of compliance to the instructions in a specific Service Bulletin or a later EASA-approved revision of that SB. That means the duty is not an open-ended obligation simply to "improve lighting reliability"; it is a duty to implement the technical solution set out in SB A320-33-1057 or any later revision that has EASA approval (Requirement). The AD therefore hands normative technical detail to the SB text and to the EASA approval process for any subsequent revisions.

Timing duty. The AD specifies the compliance deadline "No later than 27 May 2011" and an effective date "This Airworthiness Directive becomes effective on 13 March 2008" (Compliance). Operators therefore have a finite interval in which to perform the modification, absent earlier regulatory or operational constraints.

Rights by exclusion and prior accomplishment. The AD provides two ways an operator may lawfully avoid taking the mandated action. First, the AD excludes from its applicability aeroplanes that already have alternate equipment or prior modifications (Applicability a and b). Second, it includes the phrase "Unless already accomplished" in the Requirement. Together, those provisions operate as a right to non-action where the aeroplane's configuration or records show the exclusion criteria are met or the work has already been done in the required manner.

Documentation and proof. The AD itself does not set out documentation steps, but because the obligation is contingent on configuration and prior accomplishment, operators who claim the exclusion or prior accomplishment will need to rely on maintenance records, modification tags, SB compliance sheets and similar evidence to demonstrate that the AD does not apply to a particular aeroplane or has been complied with. The AD’s structure therefore makes accurate maintenance and modification records operationally material.

Absence of other rights or compensatory provisions. The AD text provides no procedural right of appeal, no cost-recovery mechanism, and no express provision for deviations or alternative methods of compliance in the text provided. The only procedural lever shown in the AD is the conditional allowance for a later EASA-approved revision of the referenced SB to be used as the compliance method (Requirement). The AD does not itself articulate a mechanism within its text for an operator to propose an alternative fix; the only route indicated by the text is to follow the SB or later EASA-approved revisions.

Interdependence with SB and EASA approvals. Because the AD requires the SB instructions or "later EASA approved revision," an operator’s rights to adopt a revised SB will depend on whether that revised SB has received EASA approval. The AD therefore links the operator duty to the EASA approval process for revisions to the SB.

The instrument, as provided, does not set out specific penalties or a detailed enforcement regime within its text. The AD contains an effective date and a compliance deadline and is endorsed by the Delegate of the Civil Aviation Safety Authority (signature block), but it does not include penalty clauses, infringement schedules, or administrative penalty amounts in the printed text supplied.

What the AD does set. The AD establishes mandatory technical compliance obligations: the modification must be accomplished in accordance with SB A320-33-1057 or a later EASA-approved revision, and compliance must be completed no later than 27 May 2011 (Requirement; Compliance). The AD also defines its applicability and exclusions, thereby identifying which aircraft are subject to the duty and which are not (Applicability).

What the AD does not state. The AD text does not state who will enforce compliance, what the enforcement process looks like, how compliance will be audited, or what penalties will apply for non-compliance. The AD is silent on any administrative or criminal penalties, infringement notices, grounding powers, or remedial directions that might be used to compel compliance. The AD also does not set out any formal process for demonstrating compliance to a regulator within its text, nor does it state a process for seeking an alternative method of compliance.

Implication for operators. Although the AD itself does not specify penalties, the AD’s issuance and required compliance period create operational obligations that operators must address. In practice, operators facing an AD typically treat the AD as binding and act to comply to maintain airworthiness certification and avoid regulatory action. The AD’s lack of penalty language in the text provided means the instrument must be read together with the broader statutory and regulatory framework governing CASA’s regulatory enforcement powers. That broader framework is not reproduced in the AD text supplied here. Therefore, within the boundaries of the source text, the AD mandates the technical work and timing but does not itself describe enforcement or penalty procedures.

The AD explicitly cross-references and depends on other regulatory and manufacturer instruments rather than enacting an isolated technical requirement. The AD refers to an EASA AD and mandates compliance by reference to a manufacturer Service Bulletin, creating a direct interaction with those instruments.

Reference to EASA AD. The AD includes a note stating "Note: EASA AD 2007-0286 refers." That is the only explicit external legislative or regulatory reference included in the text. The AD therefore flags that the European Aviation Safety Agency has issued a related AD, and that operators should be aware of that EASA instrument. The content of EASA AD 2007-0286 is not reproduced in the supplied text; the AD gives only the reference (Note).

Dependency on Airbus Service Bulletin and EASA approval. The Requirement conditions compliance on following "the instructions in SB A320-33-1057 or later EASA approved revision." This creates an operational dependency: the AD’s legal prescription is to carry out the SB instructions, and if the SB is revised, only a revision that has EASA approval qualifies as an alternative. In effect, compliance is to a manufacturer document that must also be approved by EASA. The AD therefore intersects with Airbus SBs and EASA approval processes; operators must source the SB and ensure the revision used carries the requisite EASA approval.

Relation to Airbus production modifications and other SBs. The AD’s Applicability and exclusions are framed by reference to particular Airbus modification numbers and SB identifiers: Airbus modification 20011, 21999, 27620, 37329, 37330 and SBs A320-34-1280, A320-34-1261, A320-34-1372 and A320-33-1057. That creates a cross-reference matrix between the AD and Airbus production and service-documentation regimes. Operators and maintainers must therefore use aircraft modification and SB records to determine whether the AD applies.

No express interaction clauses. The AD text supplied does not include express provisions on supersession, priority or conflict resolution with other Australian laws, nor does it specify how contradictions between the AD and other technical documents are to be handled. It likewise does not reproduce CASA’s general rulemaking or enforcement statutes. As a result, the primary interactions spelled out in the AD are with Airbus SBs and the EASA AD referenced; anything beyond that requires reference to the broader aviation regulatory framework, which is not included in the AD text.

Operationally material interactions. The AD’s reliance on the SB and EASA approval means that an operator updating technical data or following a revised approved SB will be operating within the AD’s contemplated compliance envelope. Conversely, absence of EASA approval for an alternate fix or for an unapproved SB revision would, on the face of the AD’s text, make such alternatives non-compliant with the AD. The AD’s structure therefore channels operators into using manufacturer-approved and EASA-approved technical data.

The AD as presented contains minimal explicit amendment history within its text. The primary historical details included in the instrument are dates of signature, effective date and compliance deadline.

Dates and identifiers present in the AD. The AD carries a signature block dated 23 January 2008, signed by Charles Lenarcic as "Delegate of the Civil Aviation Safety Authority." The AD states that it "becomes effective on 13 March 2008" and carries the compliance deadline "No later than 27 May 2011" (Applicability; Compliance). The AD identifier appears as "AD/A320/211" and it is dated "3/2008" in the header (table header). The document also includes repeated headings and title lines mirroring the AD identifier and subject matter.

No recorded amendments or revisions in the text. The AD text supplied does not include any explicit record of amendments, earlier versions, supersessions, revocations, or later updates to the AD itself. The AD does, however, permit compliance using "SB A320-33-1057 or later EASA approved revision," thereby acknowledging the potential for future technical revisions approved by EASA to be used to comply with the AD (Requirement). The AD does not record any history of changes to that SB or to itself.

Relation to EASA AD 2007-0286. The AD notes that EASA AD 2007-0286 is referred to (Note). That reference implies that an authoritative earlier or parallel European AD exists, but the AD does not reproduce any amendment sequence relative to that EASA AD; it simply references it.

Implication for records. Because the AD does not record subsequent amendments in the text provided, parties seeking to track the AD’s amendment history should consult the CASA files and EASA publications outside the text supplied here. The AD as printed contains no internal amendment log or history beyond the issuance and effective dates and the compliance deadline.

The supplied AD text contains no litigation history, judicial citations, or references to court proceedings. The directive lists no cases, appeals, or legal challenges; it does not mention any disputes about its content, its legal validity or its technical basis.

What the AD does include. The AD contains a Background section that recounts reported occurrences and flight crew concerns as the factual basis for the mandated corrective action, and it references an EASA AD (EASA AD 2007-0286) for further context (Background; Note). It also contains the issuing officer's signature and dates, but includes no account of any adjudication or dispute resolution concerning the AD.

Implication. Within the boundaries of the document supplied, there is no litigation history to report. Any judicial or administrative challenges, appeals or case law that might have arisen in relation to this AD are not contained in the text provided and therefore cannot be described here.

A small number of textual features in this AD can produce practical pitfalls if an operator, maintenance organisation or compliance officer reads the AD too quickly. These are the concrete "gotchas" that emerge from the AD text itself.

1. Exclusions and the method are the same SB in one instance. The AD excludes aircraft that "have received Airbus modification 37329 or 37330 during production or by Airbus SB A320-33-1057 whilst in service" (Applicability b). The Requirement, however, mandates modifying electrical supply logic "in accordance with the instructions in SB A320-33-1057 or later EASA approved revision" (Requirement). That means SB A320-33-1057 acts in one place as a trigger for exclusion (if already applied) and in another place as the method to be used where the AD does apply. Operators must not misread the effect: if SB A320-33-1057 has already been applied to an aeroplane, that aeroplane falls within the AD’s exclusion; if it has not been applied and the aeroplane otherwise meets applicability criteria, SB A320-33-1057 is the required fix.

2. Applicability depends on detailed modification and SB history. The AD’s applicability is defined by specific Airbus production modification numbers and SB identifiers. To determine applicability an operator must check maintenance and modification logs for Airbus modification 20011, 21999, 27620, 37329, 37330 and SBs A320-34-1280, A320-34-1261, A320-34-1372 and A320-33-1057. A failure to track or misread those records could lead to either an unnecessary modification or non-compliance.

3. "Unless already accomplished" requires demonstrable evidence. The Requirement’s opening words are "Unless already accomplished." Because the AD does not specify what evidence suffices, operators who claim prior accomplishment will need traceable records demonstrating that the SB or equivalent work was previously done in a manner consistent with the AD. Absent clear records, a regulator or an inspector might treat the work as outstanding.

4. The AD targets under-glare-shield flood lighting only. The AD’s technical prescription is narrowly focused on the under-glare-shield flood lighting and the addition of a battery-hot-bus back-up for that lighting. The AD does not require modification to other lighting circuits, to the standby instruments themselves, or to other displays. Assuming broader changes are required could misallocate resources; conversely, assuming that only the under-glare-shield lighting matters could miss other safety actions that might be prudent but are not required by this AD.

5. Time between effective date and compliance date. The AD became effective on 13 March 2008 and sets a compliance deadline of 27 May 2011 (Compliance). That interval is finite and must be managed. Operators who delay planning until the last minute risk difficulties securing parts, maintenance capacity or EASA-approved SB revisions, particularly if they have fleets to modify.

6. Reliance on EASA-approved SB revisions. The Requirement allows the use of "later EASA approved revision[s]" of the SB. Operators must ensure any later SB revision used is EASA-approved, not merely issued by Airbus. Using an unapproved SB revision would, on the face of the AD, not satisfy the textual requirement.

7. The AD is silent on enforcement and documentation procedures. The AD does not state how compliance is to be demonstrated to the regulator, nor does it specify an approval or acceptance process for accomplished work. That silence creates practical risk: operators must develop their own internal compliance evidence (records of SB completion, modification tags, test reports) to be prepared for any regulatory verification.

8. The AD references EASA AD 2007-0286 without reproducing it. Operators might need to consult the referenced EASA AD for context or additional technical or procedural information. Relying solely on the text of the CASA AD without consulting EASA AD 2007-0286 might miss relevant details that informed the CASA AD.

9. Narrow scope of the expressed remedy relative to the reported failure modes. The Background describes failures that include loss of display units and loss of integral lighting; the AD prescribes a back-up feed to the under-glare-shield flood lighting. Operators should avoid assuming that the AD addresses all aspects of the reported failure chain; it prescribes a specific mitigation for crew ability to read standby instruments in a particular lighting state. Any additional mitigations remain outside the AD unless separately mandated.

10. Multiple document identifiers and repetition in the AD header. The AD text contains repeated headings and identifiers (AD/A320/211 appears multiple times, as does the title and date). Operators and record-keeping staff must ensure they reference the correct AD identifier and date when recording compliance; confusion can arise if multiple similar ADs are in circulation.

Each of these gotchas flows directly from language in the supplied AD text. They are practical risks and compliance traps to be managed through careful records checks, verification of SB approvals and clear documentation of accomplished work.

The AD prescribes a limited set of concrete compliance steps by reference; the following is a structured translation of those textual requirements into a practical compliance workflow that follows the AD text.

1. Confirm applicability. Review the aeroplane’s configuration and modification history against the AD’s Applicability language. The AD applies to A318, A319, A320 and A321 series aeroplanes fitted with classical standby instruments installed by Airbus modification 20011 or 21999 during production or by Airbus SB A320-34-1280 whilst in service (Applicability). If the aeroplane has ISIS installed by Airbus modification 27620 or by SB A320-34-1261 or SB A320-34-1372, or if the aeroplane has already received Airbus modification 37329 or 37330 during production or by SB A320-33-1057 whilst in service, the aeroplane is excluded (Applicability a and b). Maintain documentary evidence for this determination.

2. Determine whether the work has "already [been] accomplished." The Requirement begins "Unless already accomplished." If records show that the modification to the under-glare-shield flood lighting has already been completed in accordance with SB A320-33-1057 (or an earlier EASA-approved equivalent), then no further action is required under this AD. Retain maintenance records, modification tags, SB compliance sheets and test reports that demonstrate the prior accomplishment.

3. Obtain the correct Service Bulletin and ensure EASA approval where required. The AD requires compliance "in accordance with the instructions in SB A320-33-1057 or later EASA approved revision." Obtain SB A320-33-1057 from Airbus or the operator technical library. If using a later revision of the SB, confirm that the later revision carries EASA approval. Document the SB revision used and any approval references as part of compliance evidence.

4. Plan and schedule the modification. If the aeroplane is within the AD’s applicability and the work has not been accomplished, plan to perform the modification according to the SB instructions. This will include sourcing any parts, scheduling maintenance slots, and ensuring appropriately authorised maintenance personnel perform the work. Note the AD’s compliance deadline "No later than 27 May 2011" and schedule accordingly.

5. Perform modification strictly as per the SB instructions. Implement the electrical supply logic changes for the under-glare-shield flood lighting, adding the required back-up supply on the battery hot bus, following the SB’s procedural, wiring and test instructions. The AD relies on the SB for technical specifics; the AD text does not provide those technical details.

6. Test and verify. After accomplishment of the SB work, perform any functional or operational tests specified by the SB to verify the new electrical supply logic and the battery hot bus back-up supply to under-glare-shield flood lighting function as intended.

7. Record compliance. Although the AD text does not prescribe documentation procedures, operators should create a compliance package that includes: the aircraft modification/serial number, the maintenance release evidencing the SB work, the SB revision and approval references used (particularly any EASA approval), test reports, sign-offs by authorised maintenance staff, and any updated configuration records showing the modification. These records serve as the evidence that the AD has been complied with and support any claim that the AD is not applicable or that the work is "already accomplished."

8. Retain evidence for inspection. Given that the AD itself does not set out enforcement steps or evidentiary standards, retain the compliance package in the aircraft technical records for regulator inspection. Evidence will be required to demonstrate that the aircraft either fell within the AD’s exclusions, had the modification already performed, or has had the SB work performed in accordance with the AD before the compliance deadline.

9. Check related EASA AD and associated documents. The AD notes that "EASA AD 2007-0286 refers." Consult the referenced EASA AD and any accompanying technical or explanatory material to ensure there are no additional related requirements or clarifications that bear on compliance.

10. Monitor for further revisions. The AD allows a later EASA-approved revision of the SB to be used; operators should monitor Airbus service information and EASA approvals in case later SB revisions clarify procedural steps or change parts lists. Ensure that any revision used is EASA-approved as required by the AD.

11. Manage fleet-wide compliance. If an operator has multiple affected aeroplanes, create a compliance plan that identifies which aeroplanes are affected, the status of SB A320-33-1057 on each aircraft, the planned dates for completion, and the documentation trail for each aeroplane. Prioritise aircraft with the classical standby configuration and without ISIS or the other excluded modifications.

12. Internal audit and quality control. Perform an internal audit or quality check after completion to ensure that the SB instructions were followed and the testing produced expected results. Document the audit findings and any corrective actions.

These steps are derived from the AD’s Requirement, Applicability and Compliance provisions. The AD’s text provides the mandatory legal hook and the SB as the technical implementer; the compliance workflow above translates those textual obligations into practical actions and record-keeping practices that will evidence compliance by the AD’s compliance deadline.