AD/A320/166 - Elevator and Aileron Computer

The instrument rests on a few tightly defined technical and procedural concepts drawn from the AD text. First, ELAC 1 refers to the Elevator and Aileron Computer number 1, a flight control computer. The AD is triggered when the aircraft is operating "under MMEL with ELAC 1 inoperative or ELAC 1 PITCH FAULT cautions displayed" (Requirement; Background). That MMEL condition is the operational state in which the aircraft is allowed to be dispatched with certain systems inoperative subject to MEL limitations. Second, the operational limitation itself is expressed as a crew-control action: "Above FL 200, the use of speed brakes lever is limited to its half position" when the ELAC 1 MMEL condition applies (Requirement). The limitation is therefore altitude-contingent and conditional on a specific MEL dispatch configuration.

Third, the AD identifies a mechanical and hydraulic chain of events as the safety hazard. The DGAC investigation found that when the aircraft is under the stated MMEL condition, "the loss of SEC 1 (Spoiler and Elevator Computer) in descent when speed brakes are deflected will lead to: - the automatic retraction of speed brakes 3 and 4, - the loss of the double hydraulic pressurisation on elevators" (Background). In manual mode and at high speed, the retraction of speed brakes 3 and 4 from full extension "will induce a pitch down effect that cannot be counteracted by the elevator controlled by a single actuator causing the aircraft to pitch down and accelerate" (Background). The operational limitation aims to prevent full deflection of the speed brakes in the critical phase, thereby reducing the probability that the chain of events (SEC 1 loss, automatic retraction of spoilers 3 and 4, loss of double hydraulic pressurisation, uncontrollable pitch-down) will occur.

Fourth, applicability exemptions are concrete: the AD does not apply to aeroplanes that have incorporated Airbus modification 33317 during production or Airbus Service Bulletin A320-27-1149 whilst in service (Applicability). Fifth, compliance mechanics are administrative: the means of compliance is amendment of the operator’s MEL by insertion of the specified TR (Requirement). The AD expressly allows later revisions of the MMEL TR, provided those revisions are approved by the DGAC (Requirement). Sixth, the regulatory provenance and cross-acceptance: CASA issued the AD but refers to DGAC AD F-2005-013 and EASA approval 2005-496, and accepts DGAC-approved revisions for compliance (Note; Requirement).

These concepts show that the AD is not a design-modification mandate, it is an operational/administrative constraint that applies to specific degraded dispatch states, and it provides an applicability carve-out for aircraft that have incorporated a specific Airbus modification or service bulletin. The AD thus converts a technical failure mode into a procedural mitigation embedded in the MEL regime.

The AD identifies specific categories of actors and the effect on them. Primary affected parties are operators of Airbus A318/A319/A320/A321 series aeroplanes certified in the relevant jurisdiction, except those aeroplanes that have incorporated Airbus modification 33317 during production or Airbus Service Bulletin A320-27-1149 whilst in service (Applicability paragraph). For affected operators, the immediate administrative obligation is to amend the operator MEL by insertion of TR No 01-27/01H issue 01 of the MMEL (Requirement paragraph). That obligation typically falls on the operator's continuing airworthiness/maintenance and flight operations departments, who control MEL content and crew operating procedures.

Flight crews are secondarily affected because the TR prescribes a crew action: limiting speed brake lever use to its half position above FL 200 when the aeroplane is under MMEL ELAC 1 (Requirement). Pilots will therefore have a conditional procedural constraint to follow during normal or abnormal operations when the stated ELAC condition exists. Dispatchers and flight operations control are affected because they decide or approve dispatch under MEL conditions; they must be aware that MMEL ELAC 1 imposes an altitude-limited speed-brake restriction which may influence dispatch decisions, cruise level choices, fuel planning, or the decision to defer maintenance rather than dispatch under the MMEL.

Maintenance organisations and engineers are affected indirectly as they must ensure that aircraft with the relevant modification or service bulletin incorporated are properly identified as excluded from the AD (Applicability). They must also update technical records to show whether Airbus modification 33317 or SB A320-27-1149 have been incorporated, because that determines whether the operator is within the AD’s applicability scope.

Civil aviation regulators and oversight bodies are implicated. CASA issued the AD through its delegate, and the AD expressly refers to the DGAC and EASA approval; the AD accepts later DGAC-approved MMEL revisions for compliance. Regulators will therefore be involved in monitoring compliance and the acceptance of revisions.

Finally, passengers and third parties are affected indirectly through any operational consequences. The MEL amendment imposes a constraint that may necessitate operational mitigations (such as operating at lower than planned cruise altitude, additional maintenance, or dispatch restrictions). The AD text frames these effects as safety measures to "ensure the aeroplane remains under control" in the identified degraded state (Background).

The AD creates a single express duty: amend the operator MEL by inserting TR No 01-27/01H issue 01 of the MMEL A318/A319/A320/A321, which introduces the operational limitation restricting speed brake lever use to half above FL 200 when the aircraft is under MMEL ELAC 1 (Requirement paragraph). This duty is framed as a mandatory amendment required by the Directive. The compliance deadline is specified, "Before 31 January 2005," and the Directive became effective on 28 January 2005 (Compliance paragraph). The AD allows operators to comply by inserting later revisions of the same MMEL TR provided those revisions are approved by the DGAC, which creates a procedural right to use DGAC-approved updates in lieu of the original TR (Requirement).

The AD also creates implicit duties arising from the MEL regime. Operators must ensure their MEL accurately reflects the Temporary Revision and that flight crews and dispatchers operate in accordance with that MEL item whenever the ELAC 1 MMEL condition applies. The MEL process typically requires operators to promulgate MEL changes internally, train crews where necessary, and retain records of MEL amendments; the AD requires insertion of the TR but the text does not enumerate the precise administrative steps, approvals, or record-keeping processes required beyond the insertion itself.

Rights in the AD are limited and procedural. Operators whose aeroplanes have incorporated Airbus modification 33317 during production or Airbus Service Bulletin A320-27-1149 whilst in service are outside the AD’s applicability and therefore do not have the duty to insert the TR (Applicability). Operators may also rely on later DGAC-approved revisions to the MMEL TR, giving them an avenue to adopt refinements without contravening the Directive (Requirement). The AD does not confer rights to deviate from the TR once it is in the MEL and active; the operational limitation is the specified mitigation.

The AD text does not set out sanctions, exemptions beyond the applicability carve-out, or appeal procedures in the document itself. It references DGAC and EASA approval processes by permitting DGAC-approved revisions, but it does not describe a mechanism for dispute or exception to a CASA-issued AD within the text provided. The document is silent on detailed procedural interfaces such as how CASA will accept evidence of MEL insertion or the formality required to show compliance for audit or oversight.

The AD text itself does not articulate civil or criminal penalties, nor does it specify enforcement mechanisms or schedules for inspections. The document is issued by the Civil Aviation Safety Authority through a delegate and states that the AD "becomes effective on 28 January 2005" with compliance required before 31 January 2005 (Compliance paragraph). As a CASA-issued Airworthiness Directive, the instrument is presented as a mandatory regulatory act, however the text contains no express penalty provisions or enforcement procedures such as infringement notices, suspension of certificates, or civil penalties within the four corners of the directive.

Enforcement and oversight will therefore be a matter of aviation regulatory practice external to the text. The AD references DGAC AD F-2005-013 and EASA approval 2005-496, and accepts DGAC-approved MMEL revisions as compliant (Note; Requirement). That cross-reference signals regulatory alignment with the issuing State of Design authority, but the document does not convert that into a specific enforcement regime within its text. The authority issuing the AD is the Civil Aviation Safety Authority delegate, James Coyne, which indicates that CASA is the relevant enforcement agency for compliance monitoring (signature block). The AD places the onus on operators to effect the MEL amendment by the compliance date; monitoring and enforcement actions, and any sanctions for non-compliance, would be drawn from the broader regulatory powers and enforcement instruments available to CASA, but those instruments are not specified in the AD text provided.

In practice, the AD’s mandatory phrasing and the fixed compliance date create a clear standard against which an operator’s compliance can be measured during oversight or audit. The absence of specified penalties in the AD should not be read as an absence of enforcement; the AD itself prescribes a required technical/administrative action and sets a date. The text does not set out any process for seeking a dispensation, alternative means of compliance, or appeal within the AD document.

The AD explicitly references foreign and regional airworthiness instruments and approvals. It notes "DGAC AD F-2005-013 (EASA Approval 2005-496) refers" (Requirement/Note). The AD also permits compliance via later revisions of the specified MMEL TR, provided those revisions are approved by the DGAC (Requirement). This creates an interaction between CASA’s directive and the State of Design authority’s (France/DGAC) AD and associated EASA approval. In plain terms, CASA is adopting a mitigation measure that aligns with a DGAC AD and allows DGAC-approved MMEL updates to satisfy the CASA requirement.

The AD does not explicitly reference domestic statutes, regulations, or the power under which CASA issued the AD; the text stands as the CASA airworthiness directive itself, signed by a CASA delegate. The document therefore functions as a direct regulatory instruction to affected operators while acknowledging and deferring to the DGAC’s MMEL revision approvals. The practical effect is a coordination of regulatory action across authorities rather than a unilateral divergence.

Because the AD prescribes insertion of a Temporary Revision to the MMEL, it interacts with the MEL/MMEL regulatory framework as administered by operators and approved by the relevant authority. The AD allows later DGAC-approved revisions to be used for compliance, which creates deference to DGAC decisions on MMEL content. The AD’s applicability carve-out for aeroplanes that have incorporated Airbus modification 33317 or SB A320-27-1149 establishes an interaction between design-change interventions (manufacturer modifications and service bulletins) and the regulatory obligation; incorporation of those design changes removes the need to comply with the MEL insertion mandated by the AD (Applicability paragraph).

The AD does not describe interactions with other domestic instruments like operations regulations, air operator certificates, or safety management system obligations. It likewise does not specify whether alternative means of compliance accepted by DGAC or EASA are automatically accepted by CASA,only that DGAC-approved revisions of the identified MMEL TR are acceptable. The text therefore creates a limited, explicit cross-acceptance (DGAC-approved MMEL TRs) while leaving broader cross-acceptance questions to regulatory practice outside the document.

The directive itself is dated and numbered: AD/A320/166, 3/2005 TX, with signature dated 25 January 2005 and the AD effective on 28 January 2005 (title and Compliance paragraph; signature block). The text requires insertion of TR No 01-27/01H issue 01 of the MMEL A318/A319/A320/A321 (Requirement). The AD permits later revisions of that TR to be used for compliance provided they are approved by the DGAC (Requirement). Beyond that permissive statement there is no further amendment history recorded within the document. The AD does not record prior ADs amending it, nor does it list supersessions or revocations.

The document does include a cross-reference to DGAC AD F-2005-013 and EASA Approval 2005-496 (Note). That cross-reference suggests that related DGAC/EASA instruments exist contemporaneously, but the AD text does not incorporate those instruments by amendment or state that they supersede or are superseded by AD/A320/166. The only recorded change that the AD itself prescribes is the obligation to insert TR No 01-27/01H issue 01 into operator MELs.

The AD provides an applicability carve-out for aeroplanes that have incorporated Airbus modification 33317 during production or Airbus Service Bulletin A320-27-1149 whilst in service (Applicability). That carve-out functions like an amendment in practice because it exempts aeroplanes with certain changes from the required MEL insertion, but it is recorded as an initial condition of applicability rather than a subsequent amendment. No later changes to applicability are recorded in the text.

If operators or regulators need to trace the lineage of the requirement, the document supplies the TR number, issue number, the DGAC reference, and the date/effective date. It does not provide an internal record of subsequent revisions adopted by CASA or later CASA ADs that modify AD/A320/166. The AD’s allowance for DGAC-approved TR revisions means that, in practice, amendment history concerning the TR may reside with DGAC documentation rather than within CASA’s AD text.

The text of the AD contains no reference to any litigation, appeals, court decisions, or administrative review concerning AD/A320/166. There is no recorded challenge to the AD, no mention of injunctions, and no description of contested enforcement actions in the document supplied. The AD is presented as an administrative safety measure issued by the Civil Aviation Safety Authority delegate and signed by James Coyne on 25 January 2005; it simply prescribes the MEL amendment and the compliance deadline.

Because the AD does not document any litigation, there is nothing in the source to rely on when assessing judicial interpretation, precedent, or administrative appeals related to this instrument. For readers seeking litigation history, the AD directs attention externally: the AD references DGAC AD F-2005-013 and EASA approval 2005-496, which are potential sources of related administrative history and any proceedings in the issuing authority’s jurisdiction, but the supplied text does not provide those documents nor any account of disputes related to them. The absence of litigation references in this AD means that any assessment of legal challenges would require consulting court or tribunal records and the DGAC/EASA instruments that the AD cites.

Several details in the AD can be overlooked or mishandled, creating compliance gaps or operational risk.

• Narrow applicability carve-out. The AD applies to "A320 all certified models, all manufactured serial numbers" but excludes aeroplanes that "have incorporated Airbus modification 33317 during production or Airbus Service Bulletin A320-27-1149 whilst in service" (Applicability paragraph). Operators must verify incorporation status of modification 33317 or SB A320-27-1149 in their fleet and document that status in maintenance records. Failure to accurately identify exempt aeroplanes could lead to unnecessary MEL changes or to non-compliance for aircraft that are not actually modified.

• Precise TR identification. Compliance requires insertion of TR No 01-27/01H issue 01 of the MMEL A318/A319/A320/A321 (Requirement). The AD allows later revisions approved by the DGAC, but operators must ensure they insert the correct TR number and issue or an approved later revision. Insertions of incorrect TRs or incorrect issue numbers may not satisfy compliance in oversight.

• Conditional and altitude-contingent requirement. The limitation applies "Above FL 200" and only when the aeroplane is "under MMEL ELAC 1" (Requirement). Operators must ensure that flight crew, dispatch and MEL documentation convey the precise conditionality: it is not a blanket prohibition on speed brake use, it is a limitation triggered only in a specific MMEL configuration. Misunderstanding that nuance could cause inappropriate operational restrictions or could leave crews unaware of the applicable constraint.

• Tight compliance timeline. The AD became effective on 28 January 2005 and required compliance before 31 January 2005 (Compliance paragraph). The short interval between effectiveness and the compliance deadline is a practical gotcha for operators that must promulgate MEL changes, brief crews and update dispatch procedures. Historical compliance timing is material for audits covering that period.

• Reliance on DGAC approvals. The AD permits use of later revisions "approved by the DGAC" (Requirement). Operators outside France must ensure they understand whether their national authority accepts DGAC-approved TR revisions as compliant with the CASA AD, or whether additional formal acceptance steps are required. The AD text itself states that DGAC-approved later revisions are acceptable for compliance, but it does not describe a process for showing that acceptance to CASA or for documenting reliance on a DGAC-approved revision.

• Technical chain of hazard. The safety hazard described involves the loss of SEC 1 in descent when speed brakes are deflected, automatic retraction of speed brakes 3 and 4, and loss of double hydraulic pressurisation on elevators, leading to an unrecoverable pitch down in manual mode with a single elevator actuator (Background). The AD’s mitigation is operational rather than design-based. Operators and engineers may misinterpret the AD as requiring hardware fixes rather than the specified MEL insertion. The AD does not require immediate hardware modification; it requires an MEL restriction unless the aeroplane has already incorporated the specified modification or service bulletin.

• No penalties stated. The AD does not state penalties or enforcement procedures in the text. Operators cannot rely on that omission as an indication of lax enforcement. The AD establishes a required standard and a deadline; compliance should be documented.

• Record-keeping and proof of compliance. The AD instructs insertion of the TR but does not specify the form of documentary proof of compliance. Operators should ensure their MEL update records, maintenance releases, and internal approvals clearly show the TR insertion and update dates to demonstrate compliance in any subsequent oversight activity.

The AD sets a single, concrete compliance action and ancillary practical steps flow from that requirement. Follow these steps closely and document everything.

1. Confirm applicability for each airframe. Check the production and in-service modification status of each A318/A319/A320/A321 in your fleet. The AD excludes aeroplanes that "have incorporated Airbus modification 33317 during production or Airbus Service Bulletin A320-27-1149 whilst in service" (Applicability). If either the modification or the service bulletin has been incorporated on an aeroplane, that aeroplane is outside the AD’s applicability.

2. Obtain the specified TR. Acquire Temporary Revision TR No 01-27/01H issue 01 of the MMEL A318/A319/A320/A321 referenced in the AD (Requirement). The AD permits later revisions approved by the DGAC as acceptable for compliance; if relying on a later DGAC-approved revision, obtain written confirmation of the DGAC approval and the revision details.

3. Amend the operator MEL. Insert the TR into the operator’s MEL so that the MEL contains the operational limitation: "Above FL 200, the use of speed brakes lever is limited to its half position" when the aeroplane is under MMEL ELAC 1 (Requirement). Ensure the MEL amendment is made in the format and with the internal approvals required by the operator’s MEL change control processes.

4. Update operating documentation and crew briefings. Convey the limitation to flight crews, dispatchers, and engineering staff. Update any relevant Quick Reference Handbook notes, crew checklists, Standard Operating Procedures and dispatch release instructions so that the conditional restriction (above FL 200, when under MMEL ELAC 1) is clear.

5. Train or brief flight crews. Provide formal briefings or training bulletins to pilots explaining the new MEL limitation, the conditions that trigger it (operating under MMEL ELAC 1 or ELAC 1 PITCH FAULT cautions), and the required crew action (limit speed brake lever to half position above FL 200). Retain records of briefings.

6. Adjust operational planning and dispatch processes. Because the limitation is altitude dependent, consider its impact on cruise level selection, fuel planning, and dispatch decisions when an aeroplane is to be operated under MMEL ELAC 1. If necessary, establish dispatch restrictions or guidance that reduce the chance of encountering the constrained condition in situations where it would create operational difficulty.

7. Document compliance. Record the MEL amendment insertion date, the TR issue number or DGAC-approved revision relied upon, and internal approvals. If compliance occurred around the AD’s compliance window, preserve dated records proving the MEL amendment was in place before the compliance deadline ("Before 31 January 2005" and AD effective 28 January 2005).

8. Monitor for DGAC/EASA updates. The AD explicitly references DGAC AD F-2005-013 and EASA approval 2005-496 and accepts DGAC-approved later TR revisions (Note; Requirement). Keep track of DGAC or EASA follow-up documents that amend the MMEL TR or propose design corrective actions. If and when Airbus modification 33317 or SB A320-27-1149 are incorporated on an aeroplane, update the applicability status.

9. Coordinate maintenance records. Ensure maintenance control and continuing airworthiness records reflect whether modification 33317 or SB A320-27-1149 have been incorporated, because this determines whether the AD applies to each airframe (Applicability).

10. Prepare for oversight. Although the AD does not specify penalties, regulators will expect evidence of MEL insertion and crew awareness. Keep documentation readily available for CASA inspections or audits. If the operator intends to use a DGAC-approved later revision, maintain the DGAC approval documentation alongside the MEL entry.

These steps implement the AD’s single required change, document the decision-making chain, and create an auditable trail showing compliance. The AD’s mitigation is operational, not a mandatory hardware mod for affected (non-exempt) aeroplanes. If operators subsequently incorporate the identified Airbus modification or service bulletin, they should update MEL entries and records to reflect exemption from the TR.